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 On 15 January 2015 at 19:31, Ofer Nave <odig...@gmail.com> wrote: > 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 > > -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/capistrano/44d451fe-d0c6-4e68-9d3e-5f9b47932da3%40googlegroups.com > <https://groups.google.com/d/msgid/capistrano/44d451fe-d0c6-4e68-9d3e-5f9b47932da3%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/CAN_%2BVLXh%2B9HBmxD8Bvodz%3DVc2prOpOs9UbenwLzEOHRvHLv%3DUQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
