Back
Regarding using the docker compose file in the master branch
Hello, i am using appwrite with custom setup(added my own oauth service) and currently using the docker-compose.yaml file to run it on my server. File has a warning saying it is not secure to use it. Is there another example docker-compose file that i can use, using my own builds? If not i will manually do them adding build tags to the services like :
TypeScript
appwrite:
container_name: appwrite
<<: *x-logging
image: my-namespace/appwrite-dev
build:
context: .
args:
DEBUG: false
TESTING: true
VERSION: dev
But i am also not sure about which ports i can leave open.
TL;DR
The user is asking for an alternative docker-compose file for their custom setup with Appwrite. They mention that they have their own OAuth service and want to change the image name for the "appwrite" service. They also mention that the current docker-compose.yaml file has a security warning. The user suggests manually adding build tags to the services. They are also unsure about which ports to leave open.
Solution: The user can manually add build tags to the services in the docker-compose.yaml file, as they have suggested. They can change the image name for the "appwrite" service and add their own OAuth service. As for which ports to
Take it : https://appwrite.io/install/compose
ah thx i just realized all services using the same image, i just change the image name of "appwrite" service to mine. Should be enough for custom oauth2 provider, i guess. Other services dont use those files i assume
