A slight fix (though not for the root issue) would be to deploy just the migration commit, (assuming the migration doesn't affect old schema, just adds to it) and migrate that. Then when you deploy the app code the DB is ready for it.
Though, I would like to see a proper explanation of that short gap between push and migrate. On Aug 10, 1:40 pm, 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 -~----------~----~----~----~------~----~------~--~---
