*Update the changelog when deploying!

Deploy the application with Capistrano (Obsolete)

• cd into the root dir of your chf-sufia repository

$ bundle exec cap [staging|production] deploy

• On the first time deploying to a Solr box you must add the flag solr_restart=true to the deploy

  
  

• If this is the first deploy, you need to start web services (because before this there was no project and apache / tomcat would fail to find various directories and config files). ssh to the ec2 machine as the sudo (ubuntu) user.

$ sudo service tomcat7 restart

$ sudo service apache2 restart

Addt'l useful capistrano info

• bundle exec cap staging deploy --dry-run --trace – shows you the whole deployment with capistrano task execution info.

• hook syntax: http://capistranorb.com/documentation/getting-started/before-after/#

Our cap recipe will automatically send a slack notification IF you set in your unix env, `export SLACK_NOTIFICATION_WEBHOOK=webhook`. Get webhook from someone. 

Deploy with downtime

bundle exec cap staging maintenance:enable REASON="a test of maintenance mode" UNTIL="12pm Eastern Time"

• It'll read "The system is down for [REASON] It'll be back [UNTIL]"
• Deploy as usual / desired
• Do anything else needed on the server that required the downtime

bundle exec cap staging maintenance:disable

Set up Capistrano (first-time use)

Create an entry for the deploy user in your .ssh/config:

Host staging
 Hostname NEW.IP
 User hydep
 #IdentityFile ~/.ssh/your_key
 ForwardAgent yes

• This keeps us from publishing server names, etc, in the cap config files which live in our public repo.
• don't change the Host designation without:
  • Changing it in capistrano, e.g. deploy/staging.rb, to match
  • Clearing it with everyone who might deploy (they'll have to change their ssh config as well.
• this will use your personal ssh key – the one that matches your public key on github, which is added to the deploy user by ansible scripts.