Hello, I'd like to know what would be the best way to put an application into maintenance state.
I want to deploy a major update (code + db structure + data migration) on a Production app, and I'd like to be sure that users don't use the app while I'm deploying and testing. As far as I know, as soon as I run 'git push heroku', the app is deployed and the users are able to access it. The problem is that I haven't run 'heroku rake db:migrate' yet, so the app that is online right now doesn't work. Also, once I've run 'heroku rake db:migrate', I'd like to be able to test the app to be really sure everything is ok. But the users are already using the app and if I made a mistake and I want to rollback, I can't, since users are already using the new DB structure. I know I have to test the app so it doesn't happen, I also have a Staging app to test everything, but, you know, sometimes things still go wrong. So, what would be the best approach to achieve an application 'maintenance' state? Thanks for your suggestions. Best, Thomas. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
