Hey Donovan. Yeah, that was the subject of my post, but I went into more
detail in the body. What I'm trying to do is have a custom task execute
regardless of whether I'm deploying using "cap production deploy" or "cap
production deploy:migrations".
Right now, I have this:
after 'deploy:update', 'notify:email'
Is it necessary to change that from deploy:update to deploy:update_code ?
Thanks,
Nick
On Wednesday, 20 June 2012 21:14:59 UTC-4, dbray wrote:
>
> You asked the question: How to trigger tasks after deploy:update when
> running migrations
>
> Which implied to me that you ONLY want to run the extra task when you do a
> deploy:migrations; and NOT when you do a plain deploy.
>
> If you want to do it on any kind of deploy then all you need is:
>
> after "deploy:update_code", "the:other:thing"
>>
>
--
* 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
