Just wondering if this is in general OK to do? I can imagine this messes with network settings or with Appwrite migration scripts.
Example containers include:
- webhook proxy
- frontend container
I do not recommend it because upgrades will wipe the docker-compose.yml file.
webhook proxy
Why do you need a webhook proxy?
frontend container
Why not use some front end hosting provider like Cloudflare pages, Vercel, etc?
Hey @Steven thanks again for your response! I needed it mainly because I thought that I needed a webhook proxy to receive Stripe webhooks (see https://github.com/Meldiron/appwrite-webhook-proxy), however I figured out this is not required. Anyway, useful to know the compose file can be wiped 🙂 I am currently using Vercel for the frontend but would prefer to keep the entire application on a single machine. Not a problem to keep it separated though.
[CLOSED] Adding new containers to docker-compose file
Recommended threads
- Clean install of 1.9.0 shows errors in a...
I just run a full clean install of Appwrite on my server following the Manual installation guide in the docs page. The console seems to work, visually there d...
- Login via GitHub Student Developer Pack ...
- [SOLVED] How many projects can I make?
I have a GitHub education plan and am using Appwrite with the same plan. How many projects can I make with the Appwrite GitHub Education?