Comments on: Late night capistrano

By: Paul Goscicki

Paul Goscicki — Thu, 17 May 2007 17:46:05 +0000

This is only a workaround that does not fix the described underlying problem.

By: Robertas Aganauskas

Robertas Aganauskas — Thu, 17 May 2007 16:47:29 +0000

Just define :after_deploy_with_migrations task in your recipes file.

There is one caveat (feature?) though: (at least for me) after_deploy_with_migrations seems not to be executed if cap_deploy_with_migrations task fails at some point. Other that it works just fine.

By: Paul Goscicki

Paul Goscicki — Fri, 23 Mar 2007 09:36:02 +0000

I’m glad to hear I’m not alone in my pain.

By: Luis de la Rosa

Luis de la Rosa — Fri, 23 Mar 2007 03:13:38 +0000

I just opened a ticket for this exact problem because it is causing me the same grief. The ticket is over at http://dev.rubyonrails.org/ticket/7897

I’ll try to keep you updated. I have 3 solutions to this and waiting to hear back from Jamis or whomever wants to look into it before submitting a patch.

By: Paul Goscicki

Paul Goscicki — Wed, 21 Feb 2007 10:16:53 +0000

Evan: there is no default "after_deploy" task. There is, however, a default "after_deploy" hook. You use it like that:

task :after_deploy, :roles => :app do
  custom_functions
  (...)
end

What I was gripping about is that it does not get executed after deploy_with_migrations, which is kind of weird. Since I have important tasks executed at after_deploy I cannot use deploy_with_migrations as this code will not be executed.

By: Evan

Evan — Wed, 21 Feb 2007 06:22:17 +0000

i don’t think there’s a default after_deploy task even with the normal `cap deploy`. after_update_code sure, but after_deploy? after_migrate? those doesn’t exist out of the box. you can use after_update_code to do some more extra tasks after deploying, but what do you need to do after migration anyway?