Hi, Just curious - why is the default for `cap deploy` to *not* run migrations?
I accept that there may be some circumstances in which you'd want to skip migrations on a deploy (long-running migrations you'll run later, I guess?). But, in my years of deploying many many different rails apps, I can only think of a handful of times I've wanted to deploy but not run migrations. And even then, it was probably best done as a separate rake task. Indeed, whenever I start a new rails project I use RailsMachine's excellent "moonshine" which runs migrations automagically. I don't even know if there's a way to disable migration running on moonshine? In any rate, it seems like it would best be done the other way around - `cap deploy` does migrations, too, and `cap deploy:nomigrations` does what it says. Is there something I'm missing? Thanks, -- Matt -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
