Just something else to note that we have seen, is that after running a migration we have had to *issue a restart* to correct odd behaviour with the new or changed table column.
On Tue, Aug 9, 2011 at 6:42 AM, John Beynon <j...@beynon.org.uk> wrote: > This isn't something that has affected myself but in selling Heroku to the > other devs at my workplace one thing that people dislike about the Heroku > workflow is that the application is restarted after a code push before > migrations may have been run. They are used a Capistrano style deployment > when the the code is pushed, migrations run and then the app restarted. > > What should I tell them to alleviate concerns? I'd have thought use > maintenance mode, deploy the code, do the work and then migrate it then > bring the application back up - > > Any one else have any thoughts? > > John. > > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/heroku/-/ozy2gnNXQtoJ. > To post to this group, send email to heroku@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- Shane Mingins -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
