The deployment is based on the git repository for this site stored on git.library.cornell.edu. You have to make sure the repository accurately reflects your development environment before deploy.
cd mysite cul_capistrano/update_enabled_modules_list.sh |
This script ends showing the differences between an automatically generated drush make file and your local.make.
Be sure the versions of contributed modules match between these two files. Edit the versions in drupal_config/local.make to make them match.
(The generated make use * for the drupal core version. You should use a specific core version in your local.make)
cd mysite cul_capistrano/do_make.sh |
git status git add --all git commit drupal_config/ -m 'my enabled modules, themes and make files' git commit public/ -m 'my new drupal core, module, and theme changes' git commit --all -m 'anything else, like maybe config/ changes' |
In real life you'll be committing each change as you go with an informative message attached to each commit, right?
git status git push |
git status should return something like:
# On branch master
nothing to commit, working directory clean
You can specify as many target remote machines as you like in your cinfig/deploy.rb set :stages directive, but normally there'll be staging (victoria02) and production (victoria01). Normally staging is set as the :default_stage so you don't have to specify anything on the cap command to target the staging server.
cap deploy |
cap production deploy |