I’ve got an after_deploy task in my cap script. If I cap deploy, the
task executes. If I do cap deploy_with_migrations, it doesn’t. Do I
have to define the deploy_with_migrations task to include this
after_deploy task?
Pat
I’ve got an after_deploy task in my cap script. If I cap deploy, the
task executes. If I do cap deploy_with_migrations, it doesn’t. Do I
have to define the deploy_with_migrations task to include this
after_deploy task?
Pat
You might try the capistrano mailing list. Due to the heavy traffic
here, the people who know a lot about capistrano might not see your post
here.
Pat-
On Mar 16, 2007, at 1:12 PM, Pat M. wrote:
I’ve got an after_deploy task in my cap script. If I cap deploy, the
task executes. If I do cap deploy_with_migrations, it doesn’t. Do I
have to define the deploy_with_migrations task to include this
after_deploy task?Pat
Does the task you have really need to run after deploy? You could
use after_restart and it will work in basically the exact same way
but it will apply to either deploy or deploy_with_migrations
Cheers-
– Ezra Z.
– Lead Rails Evangelist
– [email protected]
– Engine Y., Serious Rails Hosting
– (866) 518-YARD (9273)
On 3/16/07, Ezra Z. [email protected] wrote:
Pat
Does the task you have really need to run after deploy? You could
use after_restart and it will work in basically the exact same way
but it will apply to either deploy or deploy_with_migrations
Yeah that’s what I decided to do. Partly I was just curious why it
acted differently with deploy_with_migrations.
Pat
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs