Hi,
I want to have multiple working appwrite instances on one vm. E.g. I want to have a stage and a production parallel on one vm. Is this possbile? If yes, is there a suggestion from your side on how to achieve this? What I have tried was using the .env variable COMPOSE_PROJECT_NAME, which would auto prefix the names, but this would not work on the containers. Then I removed all container_names of the docker-compose file. Now the appwrite services starts without problems, but in the startup I saw a bunch of problems (screenshot attached), but appwrite is still working. The messages would only occur on the very first run. Now when using docker compose up, I am not receiving any error messages. But the problem is now when the stage docker is running, the production system is not reachable anymore ๐ฆ
You can, suggest you to look at docker networking
Depends if you want to duplicate all services needed by appwrite (mariadb, telegraf, etc..) or use same for twice appwrite
Quick answer : have 2 docker-compose with differents network/container name/port, remove traefik from them to have only one wich switch between appwrite1 & appwrite2 depends of confiuration need
Recommended threads
- Can't really use the S3 storage device
hi, I've linked my local MinIO Instance (it's just for testing, not for prod.) to my appwrite instance, when i'm uploading a file it's getting uploaded to the S...
- Next.js SSR Site Times Out on First Visi...
Hey everyone, I'm running a Next.js SSR site on a self-hosted Appwrite server (v1.9.0), and I've noticed a strange behavior that I'm hoping someone can help me...
- Appwrite migration stuck on pending
Migration an existing self hosted 1.9.0 to a new VPS tuning self hosted 1.9.0.. import data recognises the api url, project id and api and then when I create, i...