How to avoid timing problems when running db:migrate on multiple nodes

[Ofer Nave]

I've skimmed half a dozen tutorials on using Capistrano to deploy Rails apps to production (including the Deploying Rails book), but I still haven't seen this issue address.  I've written up an explanation and my best proposed solution here:

http://stackoverflow.com/questions/27969490/how-to-avoid-timing-problems-when-running-dbmigrate-on-multiple-nodes

-ofer

[Lee Hambley]

You shouldn't be having any timing issues, since your migrations (Ruby/Rails) should be run by one, and only one server which connects to the database server(s) to run the migrations there. You don't run the migrations on every Ruby host, and let them race to "win" at committing their changes first.

Lee Hambley

http://lee.hambley.name/

+49 (0) 170 298 5667

--
You received this message because you are subscribed to the Google Groups "Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email to capistrano+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/44d451fe-d0c6-4e68-9d3e-5f9b47932da3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ofer Nave]

That wasn't at all clear to me from the docs, but with some help from IRC and after digging into the actual code, I finally figured that out.

-ofer

[Lee Hambley]

The docs for `capistrano/rails` are just the README, perhaps make the contribution you feel was missing, if you have the time and save the next person a little grief :)

Lee Hambley

http://lee.hambley.name/

+49 (0) 170 298 5667

To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/5b73d497-1254-453b-90ea-dc5c9ab03353%40googlegroups.com.