I am planning to create a trafik service for my other docker containers in the same appwrite vps. I am a noob so wanted to ask should I do this? since traefik is already on 443 and 80 port (appwrite)
I highly encourage minimizing changes to the Appwrite docker-compose.yml file because, then, it'll be harder to upgrade in the future. The easiest thing to do is to have appwrite run on non-standard ports and put a reverse proxy in front of appwrite to expose it on ports 443 and 80. I don't like dealing with reverse proxies so I use Nginx Proxy Manager to easily manage my reverse proxy. If you'd like to do the same, check out https://medium.com/@stnguyen90/how-to-run-appwrite-behind-nginx-19348ed34243
to change ports
best is to edit docker compose file right?
i believe i will be asked the ports again on migration?
yes, you can just edit the compose file
But then appwrite is supposed to work on those non standard ports with custom domain right ??
yes...
It's not working even after docker compose up -d
I have allowed the ports in my firewall-
what's the output of docker ps?
ok so curl -k https://localhost:7443/v1/health/version works?
it worked now 0-0
Recommended threads
- deployment on every remote branch leads ...
Hi there, on my local appwrite instance it rebuilds my site on every deployment i make to github on every branch, even the main branch is set in the site settin...
- Migration from 1.5.11 to 1.6.2 fails
Hello fellow appwriters. I want to upgrade my appwrite system like the title suggests, but getting the following error during migration. See failure message in...
- Server error 500 in appwrite 1.8.0
jwt = users.create_jwt(res["userId"])["jwt"] I got this error 500 after changing environment variables and restarting containers export _APP_DOMAIN=server1.ava...