Django app failing all of a sudden
I recently pushed a minor template update to my Django app and noticed the build failed. The logs show that Django is not installed which is weird because nothing in my app changed and I see Django pip install in the logs earlier.
Did something break within Railway? This is working fine locally, not sure how do debug this
48 Replies
Project ID:
24e59367-bd09-40eb-9080-7b9609b19b1224e59367-bd09-40eb-9080-7b9609b19b12
do you have a build command set In the service settings?
No but I do have a Procfile with this content
send that here please
send what?
the procfile lol
it's in the screenshot lol
bruh
release: python manage.py clear_cache && python manage.py migrate
web: gunicorn colivevalues.wsgi
what more could u want from the file
change it to just
why
manage.py doesnt like to run during build
alllrrright
let's see
show me the table at the top of the new build logs
this might mess with my heroku deploy though wouldn'tit
idk this is railway
yes
so thats all i care about lol
okay well so removing release: doesn't trigger any build to happen lol
im just confused why all of a sudden this is an issue
the commit was literally changing padding on a element
\
cancel it and try again
yeah it keeps getting stuck in initialization
show me the procfile
web: python manage.py clear_cache && python manage.py migrate && gunicorn colivevalues.wsgi
and that's the entire contents?
yes lol its just that
now railway isn't building anything at all
this is the table when it was failing earlier
its gotta be something internal
the stuck on initializing is a railway issue
but when it was actually building, and still failed, is not a railway issue
something going on w the virtual env, not recognizing django? thats like bare minimum
let me know when you have gotten it past initialization
https://discord.com/channels/713503345364697088/846875565357006878
watch this channel for updates, and try again after they say it's fixed
ok thanks
Hey Brody
still facing the same issue here :/ I checked my last successful build and it was using Nixpacks v1.5.1, something must have happened because I see new builds are on Nixpacks v1.7.0
Here's my last successful build
& the new ones
know issue and ive been talking to the team about it
the --copies flag stands out to me
current work around is to use this as your procfile, but i see from the nixpacks v1.7.0 screenshot you arent
haha yep that was our first check, but it makes no difference with or without it
ok can I put that in the Railway build command field u think
as to not disturb my procfile
or is that not a build command, sorry new to this
just rename your Procfile to Procfile.old and then create a new Procfile with
web: python manage.py clear_cache && python manage.py migrate && gunicorn colivevalues.wsgi
so that once this get this fixed, youll be able to restore your original ProcfileI can't make the edit just to railway since this repo is deployed on heroku as well
im fairly certain that even if you set that as your start command, nixpacks will still pickup the release command from the procfile, and your builds will still fail
and there is now a github issue for this
https://github.com/railwayapp/nixpacks/issues/872
nixpacks has now been rolled back to v1.5.1, and Procfiles with both release and web commands now build correctly again!
❤️
love u big time