Easy self-hosting support about vrite HOT 4 CLOSED

The work for self-hosting is almost completed on the feature/self-hosting branch. Many changes were made to simplify the process and fix issues like the ones you're experiencing.

I'm still working on documentation and a proper build pipeline, but docker-compose.yml and Dockerfiles are already available there.

I'd recommend you wait until it's all ready and merged (hopefully sometime this week), but feel free to check it out if you're interested.

from vrite.

Self-hosting is now supported with v0.2.0, using Docker and Docker Compose. Check out the official guide here: https://docs.vrite.io/self-hosting/docker/

Will close this one, but please report any self-hosting problems as separate issues.
Thanks!

from vrite.

Hey,
Self-hosting isn't officially supported right now.

The thing is, Vrite originally started as a closed-source service, and I decided a bit later in the development that open-source is the best way for such a CMS to evolve (as you've said, there are many COSS projects with viable business models).

That's why it wasn't optimized for that from the start and needs some work to do so. Now, with updates and bug fixes coming pretty often, it's not currently prioritized as the hosted platform allows me to iterate a bit quicker.

That said, self-hosting is a must-have for a stable version and I'm working on a data migration system as well to make it really simple for those who do want to move over.

More details on all that are here: https://docs.vrite.io/self-hosting/

from vrite.

Hi,

I'm trying to get this to work, but I have some trouble.

For example, there are two similar/same lines, which seem to cause some problems ("address already in use"):

https://github.com/vriteio/vrite/blob/main/apps/backend/app/src/index.ts#L8
https://github.com/vriteio/vrite/blob/main/apps/backend/api/src/index.ts#L19

Any help, please?

from vrite.