Is it possible to configure Railway to deploy only after the old deploy is removed?
The project I keep deployed on the site does not allow for multiple instances running at the same time and the current deploy process causes an overlapping of about 20-30 seconds where 2 versions of the project are live concurrently (causing unneeded error logs in both instances)
Is it possible to prevent this by configuring Railway?
9 Replies
Project ID:
N/A
N/A
RAILWAY_DEPLOYMENT_OVERLAP_SECONDS=0
That's awesome, thank you! I'll give it a try
It worked like a charm
Is there a documentation page I can look into to see all the variables I could set to configure Railway to my needs?
Those are the provided ones
Does the variable RAILWAY_DEPLOYMENT_OVERLAP_SECONDS support negative values?
Let's say I want to stop my previous deploy and, after 5 seconds, I want to start the new one: can I do that setting it to -5?
It does not sadly
After we release persistent volumes this month we'll release rollout strategies
I'm looking forward to it 😄