I gotta go with Andrew on this one. I use Digital Ocean for my servers and Capistrano to deploy my rails apps. With next to zero config I can deploy an update to any of my apps with zero downtime and if anything was to go wrong with a deployment cap has a built in method to rollback to a previous deployment.
Maybe a maintenance mode could be needed for a different framework but I really can't see anyone needing to put their Rails app into maintenance mode to deploy an update.
I have a use case for turnout. It involves performing a changeover upgrade on a database while still ensuring that certain paths, such as webhooks, remain accessible. Heroku maintenance mode can't do that if I'm not mistaken.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I gotta go with Andrew on this one. I use Digital Ocean for my servers and Capistrano to deploy my rails apps. With next to zero config I can deploy an update to any of my apps with zero downtime and if anything was to go wrong with a deployment cap has a built in method to rollback to a previous deployment.
Maybe a maintenance mode could be needed for a different framework but I really can't see anyone needing to put their Rails app into maintenance mode to deploy an update.
Yeah, Capistrano is great, Zero-Downtime is great and Blue/Green too. Keep using what fits your needs ✌️
I have a use case for turnout. It involves performing a changeover upgrade on a database while still ensuring that certain paths, such as webhooks, remain accessible. Heroku maintenance mode can't do that if I'm not mistaken.