Here is a file describing the production stage of a CUL deploy.
server "features.library.cornell.edu", :app, :web, :db, :primary => true # TODO - ssh to here
set :deploy_to, "/libweb/sites/features.library.cornell.edu/cap" # TODO - path to deployed site
#We need to use the --uri option for drush and cache clearing (see task:clear_all_caches)
#because the cache files and directries are created by the web worker process owner, (usually
#www-data for apache). Using the uri to invoke the cache clear, will invoke the cache clear
#under the web worker process, and not the user running this deployment.
set :drush_uri, "http://#{:app}/capcurrent" # TODO - top URL of site
set :app_path, "#{deploy_to}/current/public"
#Shared resources like the Boost cache, files, tmp, settings.php are located here
#and do not change across deployments. We symlink releases to these resources.
set :share_path, "#{deploy_to}"
# use :copy option to not check out from git on remote
set :deploy_via, :remote_cache