This is going to be a problem wherever you deploy your application to. And what "happens" during that gap is really up to you.
Once the push completes the old version of your codebase is no longer running. If the migration changes the database schema radically odds are you're going to see a lot of broken pages because presumably you have updated your code for those changes. If the migration does something minor, then you probably won't see a lot of breaking. The point being that handling this is left to you as the developer to handle. One option is to have a maintenance flag in your database or config var that you can toggle to display a maintenance page. This is probably the easiest to do and could be used for a large set of use cases. Another option would be to have code that can work around your schema changes, this is probably the most difficult for most to implement but it is an option. -- Ricardo On Aug 10, 5:40 am, Chap <[email protected]> wrote: > Between the push to heroku (which will automatically launch the app) > and heroku rake db:migrate what happens? > > I know it's only a few seconds, but potentially the site would be > broke right? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
