[CLOSED] Adding new containers to docker-compose file

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

TL;DR

The user wanted to add new containers to their docker-compose file, specifically a webhook proxy and a frontend container. They initially thought they needed the webhook proxy for Stripe webhooks, but later realized it wasn't necessary. They use Vercel for the frontend but want to keep the entire application on a single machine. Another user suggested using a front end hosting provider like Cloudflare pages or Vercel instead. The user also expressed concerns about potential issues with network settings or Appwrite migration scripts. The thread has been closed after the user resolved their query. No specific solution or recommendation was provided.

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

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more

Recommended threads

Need support?

Join our Discord

Get premium support