Page History

...

• push a tag for this release to git
• do a backup of the staging db (with the staging site offline)
• update the staging server's clone of your git repo
• check out all the stuff from the local git repo to a revision directory on staging
• change the 'current' symbolic link to point to the public directory inside new revision directory
• update symbolic links from the revision directory's public/sites/default/files
• put the site offline
• update the site's public, private, and temp files paths
• run update.php
• revert any features
• put the site back online

References

http://www.58bits.com/blog/2013/03/23/deploying-drupal-with-capistrano^{Image Added}

http://previousnext.com.au/blog/simple-and-powerful-drupal-site-deployment-capistrano^{Image Added}

http://www.metaltoad.com/blog/capistrano-drupal-deployments-made-easy-part-1^{Image Added}

http://www.zodiacmedia.co.uk/blog/professional-deployment-of-websites-using-capistrano-part-2

https://github.com/capistrano/capistrano/wiki/2.x-Default-Deployment-Behaviour^{Image Added}

https://github.com/czettnersandor/drupal-cap^{Image Added}

http://www.simonecarletti.com/blog/2009/09/capistrano-file-transfer-actions/^{Image Modified}