Does anybody else have the problem that running "cap deploy:migrations" doesn't run "deploy:after_update", but "cap deploy" does? I have after_update it make some symlinks to the shared directory and set some permission. Am I using it wrong? Thanks, Mike
on 15.08.2008 21:48
on 16.08.2008 17:06
Mike,
I think (haven't checked the code) deploy:migrations doesn't
update the code. Then after_update should not be triggered... If there
is no new release folder, a new symlinks should not be required, also
you could use:
after "deploy:symlink", "whatevertask"
Best regards,
--
Aníbal Rojas
http://hasmanydevelopers.com
http://rubycorner.com
http://anibal.rojas.com.ve
On Aug 16, 2:48 pm, Mike Nicholaides <ruby-forum-incom...@andreas-
on 19.08.2008 07:35
Actually, these are what "cap deploy:migrations" runs: deploy:migrations deploy:update_code deploy:finalize_update deploy:migrate deploy:symlink deploy:restart This is from looking at the output when I run it.