Repository navigation
Move events from after deploy:update #67
Description
bower install runs after deploy:update alongside genesis:permissions and a few other commands, but these should be ran after deploy:update_code and deploy:finalize_update, respectively.
The reason being, the site is live once deploy:create_symlink is ran, which means that we don't want any more changes made to the codebase after this happens.
$ cap staging deploy
triggering load callbacks
* 2013-11-19 11:20:48 executing `staging'
triggering start callbacks for `deploy'
* 2013-11-19 11:20:48 executing `multistage:ensure'
* 2013-11-19 11:20:48 executing `deploy'
* 2013-11-19 11:20:48 executing `deploy:update'
triggering before callbacks for `deploy:update'
* 2013-11-19 11:20:48 executing `deploy:setup'
** transaction: start
* 2013-11-19 11:21:03 executing `deploy:update_code'
* 2013-11-19 11:23:10 executing `deploy:finalize_update'
* 2013-11-19 11:23:11 executing `deploy:create_symlink'
** transaction: commit
triggering after callbacks for `deploy:update'
* 2013-11-19 11:23:20 executing `genesis:permissions'
* 2013-11-19 11:23:37 executing `deploy:restart'
triggering after callbacks for `deploy:restart'
* 2013-11-19 11:23:37 executing `genesis:restart'
triggering after callbacks for `deploy'
Activity