project ID: e8eef74a-59dc-42cf-9b57-69bcb2f3f816

hello, the private network is not available during build, you would want to run your migrations during runtime before starting the app

hmm wouldn't that result in downtime for the app? if you run the migrations and then have to wait for the deployment to finish before your frontend references the new db schema?

it won't as long as you use a healthcheck

damn, seems like a lot of hassle to implement a healthcheck

means on each migration, you'd have to modify the healthcheck endpoint to verify the new schema?

no, just return 200 after pinging your database

alright I added an endpoint that returns 200 after connecting to the db, set the healthcheck path on Railway to /api/health, but it still fails with the same unable to connect to internal db error 😦

@Brody

have you stopped running migrations during build?

ah I think that fixes it, so is the workflow on Railway to run the migrations in Github Acitons on CI, and then check the "wait for CI" option on Railway service?

seems kind of dangerous if the build fails but migration succeeds

or if you run it locally, there would be downtime

trying to see if it's possible to have the deploy fail if the migration fails

right so as previously suggested, you run your migrations during runtime before starting your app, then use a healthcheck, this way if the migration fails the app never gets deployed

ok ok gotcha, I'll do the migrations in the start script then

thanks!

let me know if you have any troubles

have things worked out for you?

!s