> On Sep 18, 2018, at 6:19 AM, Florian Ebeling <florian.ebeling@gmail.com> wrote:
>
> Is there a common practice how to apply migrations for staging systems running various feature branches?
>
> Assume there is a db of significant size, and feature branches including migrations are pushed to this server instance.
>
> Just calling `rake db:migrate` won't be enough, as often it will be the situation that a feature branch introduced a schema change, and the subsequently deployed branch doesn't work with it. So at deployment, I'd need to roll back one or more migration steps.
>
> I know this can be done by invoking `db:migrate VERSION=v`.
>
> But how would you establish what to pass as `v` here from the new branch?
>
> (Or is loading a nightly db dump and uniformly migrate upwards still the best idea?)
The we we manage this is to have a separate staging database, cloned monthly from the production database (to get a useful sample of data to play with) and then run migrations up and down in that database as we check things out for review. Does that help?
Walter
>
> Florian
>
> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/23939ea5-cd1c-4780-8a16-fa43d2e2e704%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/11363694-F895-405E-A3D2-2C62E1A80123%40wdstudio.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment