Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Latest commit

 

History

History
33 lines (17 loc) · 2.05 KB

deployment.md

File metadata and controls

33 lines (17 loc) · 2.05 KB
Raw

Deploying

Atom core team members can follow the instructions below to test pull requests and deploy changes to production.

Testing pull requests

Visit the atom-teletype pipeline dashboard on Heroku.

pipeline

In the left-hand column, you'll see a review application for each open pull request on this repository. Alternatively, you can also wait for a deployment notification to be displayed directly on the pull-request.

The teletype package can be instructed to use one of these servers by opening the package's settings page and assigning the base URL.

package-settings

You'll need to reload the window for the change to take effect. You should not normally need to touch the Pusher key as we use the same Pusher account on both staging and production.

Deploying

  1. Ask @as-cii, @nathansobo, @jasonrudolph, or @iolsen to grant you deploy access on https://dashboard.heroku.com/apps/atom-teletype.

  2. Visit the atom-teletype pipeline dashboard on Heroku.

  3. Whenever someone pushes to master, its contents are automatically deployed to staging. Use the instructions from the testing section above with the base URL of https://atom-teletype-staging.herokuapp.com/ if you'd like to test the Atom package against staging before deploying.

  4. Once you're satisfied with your testing, click Promote to production... on the staging app to move the staging slug to the production app.

promote-to-production

Chat-ops

You can also interact with our Heroku pipeline on Slack via ChatOps. Check out this page for more information.