On Nov 10, 2011, at 12:48 AM, Lee Hambley wrote: > Subversion has "Externals" (which are the same as Git submodules) ---- My subversion foo is not the greatest ;-) ---- > > And you don't have to "hope" that it happens before Symlink, you can hook > into after "(deploy:)update_code" - which runs inside of the rollback > transaction, and will allow you to scrap the deploy if you can't > checkout/link/whatever your I18ns. ---- Thanks for the help Lee
Sort of why I was asking if there was more documentation than the 'Handbook' and the 'GitHub Guide' because I'm a bit vague on what is transactional among many things but I am learning as I go. I think in the final analysis, it's probably better if I just drop the 'require bundler/capistrano' and the RAILS_ROOT references in deploy.rb, then I can namespace the second deployment, invoke the second namespace with ' deploy' and just handle the RAILS symlinking and bundler executions via 'after' tasks. Still curious though, why it is that cap -T and cap -f config/deploy.rb -T produce different results ie... $ cap -T > /tmp/cap_t.txt $ cap -f config/deploy.rb -T > /tmp/cap_f_t.txt $ diff /tmp/cap_t.txt /tmp/cap_f_t.txt 1,28c1,14 < cap canada_prod # Set the target stage to `canada_prod'. < cap colo_prod # Set the target stage to `colo_prod'. < cap deploy # Deploys your project. < cap deploy:check # Test deployment dependencies. < cap deploy:cleanup # Clean up old releases. < cap deploy:cold # Deploys and starts a `cold' application. < cap deploy:migrations # Deploy and run pending migrations. < cap deploy:pending # Displays the commits since your last deploy. < cap deploy:pending:diff # Displays the `diff' since your last deploy. < cap deploy:rollback # Rolls back to a previous version and restarts. < cap deploy:rollback:code # Rolls back to the previously deployed version. < cap deploy:setup # Setup translation directory < cap deploy:symlink # Create Symbolic links to current path < cap deploy:update # Copies your project and updates the symlink. < cap deploy:update_code # Copies your project to the remote servers. < cap deploy:upload # Copy files to the currently deployed version. < cap deploy:web:disable # Present a maintenance page to visitors. < cap deploy:web:enable # Makes the application web-accessible again. < cap development # Set the target stage to `development'. < cap euro_prod # Set the target stage to `euro_prod'. < cap invoke # Invoke a single command on the remote servers. < cap libra_prod # Set the target stage to `libra_prod'. < cap mii_prod # Set the target stage to `mii_prod'. < cap multistage:prepare # Stub out the staging config files. < cap shell # Begin an interactive Capistrano session. < cap staging # Set the target stage to `staging'. < cap test1 # Set the target stage to `test1'. < cap test2 # Set the target stage to `test2'. --- > cap canada_prod # Set the target stage to `canada_prod'. > cap colo_prod # Set the target stage to `colo_prod'. > cap deploy:setup # Setup translation directory > cap deploy:symlink # Create Symbolic links to current path > cap development # Set the target stage to `development'. > cap euro_prod # Set the target stage to `euro_prod'. > cap invoke # Invoke a single command on the remote servers. > cap libra_prod # Set the target stage to `libra_prod'. > cap mii_prod # Set the target stage to `mii_prod'. > cap multistage:prepare # Stub out the staging config files. > cap shell # Begin an interactive Capistrano session. > cap staging # Set the target stage to `staging'. > cap test1 # Set the target stage to `test1'. > cap test2 # Set the target stage to `test2'. -- * 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
