that is the first and only log line from the deploy logs

complete means it has exited

oh. "deployed" is what I need?

I thought anything other than deployed was a fail

no, looks like "active" is what I want? completed with a green check mark is definitely misleading. but now I know

so how do I even debug this? I have zero logs to tell me whats happening

my build log ends here
Build time: 53.95 seconds

deploy log starts and stops with
Starting Container

not really something the platform can help you with unfortunately, its something you would have to make an educated guess on

but let me see if i can guess for you

you have a dockerfile without a CMD directive

CMD curl -f -H "Cache-Control: no-cache, no-store, must-revalidate, max-age=0" -H "Pragma: no-cache" http://localhost:${PORT}/api/health/ || exit 1

arrg. sorry

!s

lol what

I hate docker

container just stops for no reason. the worst

Running migrations:

No migrations to apply.

• exit 0

Running Django checks…

System check identified no issues (0 silenced).

Running migrations…

Stopping Container

you can close this. its definitely an issue with my docker file. the railway behavior seems different. was expected a fail, not complete green checkmark, but its ok.

its only a fail if the app exits with a non zero, zero is success after all

but will close

!s