Self-hosting builder

[MOZGIII]

Self hosting builder for production is "not recommended".

Is it possible though?

---

By "production" I mean:

• deployment with containers to Kubernetes (which is clearly either possible today, or will be possible after the builder app is containerized)
• proper data persistence & backups for projects (i.e. use with production-level database like postgres, redis, and etc as opposed to local filesystem or in-memory data)
• authentication via custom oauth provider
• export of the websites artifacts manually and via API for the purposes of self-hosting

In my view, integration of various ways to directly host the websites right from the builder can be out of scope - as I'll be integrating a custom deployment system either way (back to k8s where the builder itself is hosted essentially).

---

Refs:

• Improve self-hosting the Builder webstudio#3966

[kof]

it is

[TrySound]

[MOZGIII]

I may be misunderstanding your documentation page structure - but it seems that there are two sections there "Builder" and "Projects" - and the "Builder" projects is empty besides the note "not recommending" self hosting builder for production and linking to the documentation page on running it for development.

So, literally no instructions?

[TrySound]

https://docs.webstudio.is/contributing/contributing-for-developers

[MOZGIII]

That's instructions for development. I mean, yes, those are definitely there.

There is a difference though. You guys don't host https://webstudio.is/ via vscode / dev containers, right?

Or do you guys actually think this is what I'm asking for, given my clarifications in the previous messages and all that?

[MOZGIII]

Just to clarify, what I'd expect from production instructions:

1. A list of required external parts, like "you'll need a postgres database, s3, local filesystem" - etc.
2. A list of components of the project that would needed to be deployed and scaled - like "you only need to run the builder process" or "builder + a dedicated trpc server", etc
3. A list of configuration parameters or a place that documents them in the code - like a link to https://github.com/webstudio-is/webstudio/blob/main/apps/builder/.env
4. A couple words on how to do the maintenance: "to backup do postgresql dump and copy over the contents of the s3 bucket", etc
5. How to use other oauth providers besides github (this could be just one of the features that admins can configure - and I don't even know how many are there, but docs for all of them might be great)

Also nice to have would be to share how you guys run your own stack. That usually works better as a one-off blog post every year or two - so there is no need to maintain it in the up-to-date state like the docs.

An example of nicely written doc for similar-in-kind open source project: https://www.ory.sh/docs/hydra/self-hosted/install