a year ago
I am experiencing an issue with my production deployment on Railway. I created the deployment by uploading my docker-compose.prod.yaml file. However, when I modify this file in my Git repository, the changes are not being automatically applied by Railway. Additionally, if I re-upload the file manually, it creates new services instead of updating the existing ones.
I require a production-specific Docker Compose configuration that is different from my development setup, and I need to ensure that updates to my docker-compose.prod.yaml are reflected in my production deployment without creating duplicated services.
Could you please provide guidance on the following:
How can I trigger an automatic update of the production Docker Compose configuration when I push changes to my Git repository?
How can I avoid creating duplicate services when re-uploading the docker-compose file manually?
Is there a recommended workflow or specific configuration in Railway for handling a production-specific docker-compose.prod.yaml that is separate from the one used in development? Or should i do it otherwise? Thank you in advance
4 Replies
Right now I believe Docker Compose only works for creating your services for the first time with drag and drop. Let me double check.
@Trunt Yes I confirmed that it only is for drag-and-drop add for services. It doesn't link with your existing github integration for each of those services.
If you want updates today you'll need to enable the github integrationi per service or setup something custom like a github action in order to railway up your code.
I'd recommend opening or searching our feedback if linking a docker-compse and getting updates on a push basis is something you're interested in on the platform long term
Status changed to Solved echohack • 11 months ago