2 years ago
I ran railway run with a new start command and now the application is not accessible because of this error.
Here is my railway.json
{
"$schema": "https://railway.app/railway.schema.json",
"build": {
"builder": "NIXPACKS"
},
"deploy": {
"startCommand": "sleep 3 && celery -A tibian_backend worker --loglevel=info && python manage.py migrate && gunicorn tibian_backend.wsgi --bind 0.0.0.0:$PORT",
"restartPolicyType": "NEVER",
"restartPolicyMaxRetries": 10
}
}Before it was like this and it worked perfectly
{
"$schema": "https://railway.app/railway.schema.json",
"build": {
"builder": "NIXPACKS"
},
"deploy": {
"startCommand": "sleep 3 && python manage.py migrate && python manage.py collectstatic --noinput && gunicorn --timeout 500 tibian_backend.wsgi",
"restartPolicyType": "NEVER",
"restartPolicyMaxRetries": 10
}
}I appreciate any help
0 Replies
2 years ago
What do the logs show?
2 years ago
Im not sure what your celery logs have to do with the django service?
Since the celery worker is running in my django service i think its normal to see celery logs here
I have found this article and am trying to follow it
https://dev.to/techbychoiceorg/django-celery-and-redis-on-railway-214h
2 years ago
you should be running celery as a seprate railway service
2 years ago
thats not the best guide tbh
2 years ago
it is possible, though far from ideal
Ok so I need to make an exact copy of my repository to a new service and adjust the start commands accordingly, right?
2 years ago
no copy needed, you can deploy the same repo to multiple services
2 years ago
otherwise, yes you got the idea