Is Zero-downtime possible with a wordpress deployment + persistent disk?

Im using Render right now and in thier "disk limitations" section it says: * Adding a disk to a service prevents zero-downtime deploys. This is because: * When you redeploy your service, Render stops the existing instance before bringing up the new instance. * This instance swap takes a few seconds, during which your service is unavailable. * This is a necessary safeguard to prevent data corruption that can occur when different versions of an app read and write to the same disk simultaneously. Is this the same for Railway? I just need a Wordpress site, where my themes dir is in my repo, CI/CD, and thats it. Right now I cant continue using Render because when I deploy its down for ~5 seconds and that sucks each time I deploy there is a 502 error. I want to know if I use Railway if I would have this same situation?

Solution:

exact same situation on railway unfortunately, though if you never plan to edit the wordpress site live on railway and the wordpress site (while live) will only ever modify data in the database, then i dont think you would strictly need a volume

Jump to solution