Deploying to production - aavedula/how-to-notes GitHub Wiki
The branch in your current working directory is what is deployed to production.
git remote add connect [email protected]:careport-production/connect.git
- Add environment variables to .bash_profile
export SLACK_DEPLOY_WEBHOOK_URL="https://hooks.slack.com/services/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"
export APPSIGNAL_PUSH_API_KEY_FOR_DEPLOY="abc"
-
Look up the slack hook in the Slack website under the Careport profile.
-
The appsignal key needs to be gotten from Sean.
-
Add ssh key to aptible
pbcopy < ~/.ssh/id_rsa.pub
Add here: https://dashboard.aptible.com/settings/ssh
- Login into aptible if necessary
aptible login
- Checkout master. Ensure it has no local changes and that it matches the source in Github.
- Pull from all repositories.
git fetch --all
git pull
git log --format='%h %s <%an>' master...connect/master|pbcopy
-
Paste the log output into the
connect-development
Slack channel and ask if it is alright to deploy. -
When approved, deploy:
bin/deploy connect master
- Or deploy up to a commit
bin/deploy connect <hash>