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
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://anibal.rojas.com.ve
On Aug 16, 2:48 pm, Mike Nicholaides <ruby-forum-incom…@andreas-
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.