a year ago
Each time we deploy, our users think our services is down.
How does it work by default? Are you doing rolling updates or recreating deployments?
I essentially want the new replica set up and running before the old set is scaled down.
3 Replies
a year ago
Hey Nikki!
Sounds like you probably want to configure healthchecks
https://docs.railway.com/reference/healthchecks
Do you have them configured already?
Status changed to Awaiting User Response Railway • over 1 year ago
a year ago
Can you elaborate on how on the order of operations re: applying migrations and then deploying the code. We have health checks, but the errors we're getting are showing discrepancies with the code and what's available in the DB
Status changed to Awaiting Railway Response Railway • over 1 year ago
a year ago
Sorry I'm not sure I understand? You should setup your migrations such that they run either in your build, or in your start command
You should then make sure your health checks
do not pass before your migrations are complete if your migrations cause downtime.
Finally if you're seeing discrepancies with the code and what's available in the DB, I would say that's an application level thing because we don't handle anything in your DB (beyond hosting it)
Status changed to Awaiting User Response Railway • over 1 year ago
7 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 7 months ago