Heroku's Procfile still cached even after redeployment
zaidaldabbagh
PROOP

a year ago

My initial deployment failed, as I had forgotten to remove my Procfile which had Heroku instructions in it. However, when I pushed up mode code to my connected repo, I seem to have hit the same error even though the Procfile is no longer there. I tried to redeploy hoping that the error would go away, however it still seem to execute that Procfile! Am I missing a step? Do I need to recreate the Project?

/bin/bash: line 1: vendor/bin/heroku-php-apache2: No such file or directory
Solved

4 Replies

brody
EMPLOYEE

a year ago

Are you building with a Dockerfile or nixpacks?


zaidaldabbagh
PROOP

a year ago

I looked into the instance's settings, and noted that it automatically got added as a`Custom Start Command. I have now removed and will re-test this :)


Just checking in, is this resolved after you removed it from the start command?


Status changed to Awaiting User Response Railway over 1 year ago


zaidaldabbagh
PROOP

a year ago

Yes it has, please mark as resolved.


Status changed to Awaiting Railway Response Railway over 1 year ago


Status changed to Solved brody over 1 year ago


Loading...