From Docs: https://appwrite.io/docs/getting-started-for-web I've follow the instructions at https://github.com/appwrite/demo-todo-with-react To deploy to my DigitalOcean account, as my static hosting provider, using the "Deploy to DigitalOcean" button, which link is: https://cloud.digitalocean.com/apps/new?repo=https://github.com/appwrite/todo-with-react/tree/main
I've configured the 3 env vars to point to my appwriter endpoint, as well the project and collection IDs, running inside a docker (from DigitalOcean Appwrite marketplace)
But the DigitalOcean deploy failed. Attached, the log message. Any one could, please, help me?
Deploying Todo example at DigitalOcean
If you're only testing it out, you don't need to deploy it on DigitalOcean 🧐 you can run it locally
Thank you for the prompt response. I Understand your point and I agree. I have already tested an APP running locally in development mode (the front end being served at localhost:3000) on the same VM from DigitalOcean where appwrite is installed inside the docker. It works great!
But, I would like to test the process of deploying the App into a real production environment. That is why I tryed to follow the github readme instructions to do that using DigitalOcean, as it is my actual cloud plataform where I have an active account.
I would also like to test deploying the frontend in the same VM at DigitalOcean where the appwrite is running. Is there any tutorial for that? I mean, having the frontend served at mydomain.com and the appwrite at appwrite.mydomain.com.
Then the problem might be the node version on the server. It was a little hard to read but the error looked like it had to do with dependencies.
Honestly, for a single page application, I would deploy to something like cloudflare pages, vercel, or netlify. There's no need for it to run on your Appwrite server. And those providers I shared have global CDNs for better global coverage.
That said, if you want to run multiple things on a single server exposed with different domains, you'll need a reverse proxy. Nginx proxy manager (NPM) is a nice easy GUI for this. If you need help setting up NPM, check out https://medium.com/@stnguyen90/how-to-run-appwrite-behind-nginx-19348ed34243
Thanks once more. I will take your suggestions...
Recommended threads
- 500 Server Error after migrating to 1.8....
Upgraded as per docs and ran migration. Everything went smoothly. I am able to log into the appwrite console however cant access any service i.e., auth, databas...
- Console not showing Site screenshot
Image link broken for self-hosted 1.8.0 (updated from 1.7.4), was working fine in older Console version (6.0.43, updated to 7.4.10).
- Storage usage keeps going up
I have a self-hosted instance running in production for over a year now. The deployment has seen multiple updates and migrations of Appwrite versions. What I ha...