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 wrote:
> This isn't something that has affected myself but in selling Herok
Sounds like Heroku could make this available for apps that don't use a
[SQL?] DB.
On Aug 30, 11:13 pm, Peter van Hardenberg wrote:
> This totally sucks. I see no reason we can't write software which can help
> take care of this and provide superior versioning in the system. Ultimately
> the lesso
This totally sucks. I see no reason we can't write software which can help
take care of this and provide superior versioning in the system. Ultimately
the lesson here is that all cloud services need to be capable of being in
intermediate states (or reverting part way through!) during all deploys.
T
In a sufficiently large/complex environment db and code changes
necessarily happen at different times, even if you try to make them
happen together. So one of the changes (code or db) needs to be
backwards compatible each release - push the backwards compatible
change first and then the other. Turn
Hey guys,
We have a lot of interest on this subject at Heroku, if anything
because we use the product every time we can and we understand that
having to put the app on maintenance mode every time you deploy a
migration is not acceptable.
That said, the problem with migrations like Mike said goes
We're thinking about having a migrations branch where we put all migrations.
They get merged to master first, then pushed and run, and then after those
complete we merge the new code to master and push again.
It does mean that you have to spend more time and effort dealing with data
model cha
That only half solves it by forcing downtime you'd be taking anyway because
your app is likely to crash if started before the migrations run, as you are
forced to do. Having to take downtime just to add a field is pretty lame.
We're looking at running our migrations from an EC2 server since we u
You could try a script like Kumade and patch it so that it always does
a restart after migrating:
https://github.com/thoughtbot/kumade
On Mon, Aug 8, 2011 at 2:42 PM, John Beynon wrote:
> This isn't something that has affected myself but in selling Heroku to the
> other devs at my workplace one
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
w
