How to disable Dockerfile in a service?
So I have multiple services including Django and Celery. Both use the same code but their start commands should be different.
Since I am using a Dockerfile to build and start my Django service, it is automatically detected and applied to the celery service too.
I want my celery service to have a different start command but railway is forcing the dockerfile on both.
How to fix that?
17 Replies
Project ID:
643c9962-5fa0-449c-82e0-67b30f66c552643c9962-5fa0-449c-82e0-67b30f66c552
This is my docker file.
I tried removing the start commands and placing them manually in the railway dashbaord as a custom start command but it didnt deploy, the logs were empty.
I think there is an issue with paths?
Any solution to this?
simply set the needed start command in the service settings
When I do that nothing gets deployed
please go back to that and then we can debug from there
just did that
and what errors are you getting?
the deploy logs are empty
what have you set the start command to?
sleep 3 && celery -A tibian_backend worker -l INFO --concurrency=2 worker_prefetch_multiplier=1
had the same issue before wiht my other service, defining a start command causes the service not to start at all
when having a docker file
another thing i wanna mention is that i tried making 2 nixpack config files and defining them in the service settings separately, each with a different start command, however railway didnt pick up on them and decided to build on the default builder config
been a headache honestly i hope there is a solution to all this
remove the
sleep 3 &&
as long as you are on the V2 runtime there is no need for a sleepgot something this time
similar situation to my django service earlier, like i mentioned
I'll look at your project when I'm back on my computer to see if something else has been missconfigured
the last changes made to the celery service was 6 hours ago???
the django fail from ~1h ago was likely because you ran railway up from the wrong dir
i think youre looking at production and not staging
im testing on staging environment
ah my bad, I don't think an environment was mentioned? will look at staging
hey, sorry for the delay here but im not seeing any issues with the services in staging? django is running correctly and so is celery, both service logs reflect this?