Date: Tue, 3 Jan 2012 08:36:12 -0800 (PST)
From: Matt <matt.rog...@gmail.com>
Reply-To: capistrano@googlegroups.com
To: capistrano@googlegroups.com
Message-ID: <24538407.482.1325608572978.JavaMail.geo-discussion-forums@vbgw2>
Subject: Why doesn't `deploy` run migrations?
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_480_26301171.1325608572976"

------=_Part_480_26301171.1325608572976
Content-Type: multipart/alternative; 
	boundary="----=_Part_481_31263960.1325608572976"

------=_Part_481_31263960.1325608572976
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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

------=_Part_481_31263960.1325608572976
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,<div><br></div><div>Just curious - why is the default for `cap deploy` t=
o *not* run migrations?&nbsp;</div><div><br></div><div>I accept that there =
may be some circumstances in which you'd want to skip migrations on a deplo=
y (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.</div><div><br></div><div>Indeed=
, whenever I start a new rails project I use RailsMachine's excellent "moon=
shine" which runs migrations automagically. I don't even know if there's a =
way to disable migration running on moonshine?&nbsp;</div><div><br></div><d=
iv>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?</div><div><br></div><div>Thanks,</=
div><div><br></div><div>--</div><div>Matt</div>
------=_Part_481_31263960.1325608572976--

------=_Part_480_26301171.1325608572976--