Guide to Bringing Appwrite to Production

copy thank you

What's the recommended way of setting up appwrite on a subdomain? I have my appwrite server setup, and I have it working, but only at my servers IP address, and I can't figure out using Cloudflare + Nginx how to reverse proxy it

@D5 I used the lazy way of backup and restore, removed my Appwrite docker instance on my server temporarily to restore it, and there was no docker-compose.yaml or .env files created, so docker compose up -d doesn't work. It created a directory called docker-compose.yml but I also don't know how to fix it

Hosting offered by Digitalocean marketplace offers only node-16.0 version. I started to use docker-compose.yaml file and planning to host on my own because of that. Needed node-18.0 version and did not know how to change that. Expanding collection of runtimes is not well documented.

Add and configure it as if it was a domain, no needed to setup any reverse proxy or anything else

I'm not sure how does it works, other users managed to make it that way

In the one installed by digitalocean marketplace, If I'm not wrong, you can setup node 18 by changing as others, the corresponding variable located at docker-compose.yml file

i have a doman registered as example.com pointed to the public IP of my VPS.

I created a subdomain called appwrite.example.com and added an A record pointing to the public IP of the VPS as well.

On my server, I've got NGINX setup with server blocks for each subdomain. requests to appwrite.example.com get reverse proxied to the port that's running appwrite (80 for http and 443 for https by default)

if you need any help, feel free to tag me and ask away

I've started to put together my own guide for this on my Notion one second

https://zachhandley.notion.site/Getting-Appwrite-to-Production-04d8d5ba27a048daa01564afff497f67

Oh that looks cool @ZachHandley

👀 This is an interesting discussion. We can put some of this information into the docs, for sure.

Self-hosting and scaling to production is a very high-level effort, those who do it usually have a lot of opinions on how their infrastructure should be managed.

I really love they you posted a Notion page, maybe even bring this to Dev.to.

I think these resources are a missing part of the ecosystem, where people discuss how they're managing their self-hosted instances. Everyone on the team that hosts Appwrite for production does it slightly differently, and resources like this would make it easier for everyone else down the road.

Thanks for your contribution ❤️

In fact we've had this PR sitting stale for a while now... Which addresses many of the isseus here. Let me push for this to be merged 😬
https://github.com/appwrite/docs/pull/279

Amazing I’ll update my notion more too!

Reviewed and added few comments

I’ll update it with my notion notes after as well, is there any chance to get an official AppWrite way to transfer DB’s? Like maybe a websocket between the self hosted instance and the web instance or I’m not sure

Could I in theory open my IP address to the world and then use an API key from my server and create a function to list everything and bring it in?

Currently there's not any official way, but they commented that the team is working on building a migration tool

Gotcha. I think a connection could be useful tbh

🤔 This is something we've thought about a lot

I have heard rumors

this might come true

Eldad confiremed that there was going to be a tool to transfer/migrate between appwrite instances and cloud

Meanwhile, @ZachHandley give this issue a 👍 https://github.com/appwrite/appwrite/issues/390