Setting Up to Use an Existing Heroku Environment on Your Local OS X Environment

existing-heroku-setup.md

Setting Up to Use an Existing Heroku Environment on Your Local OS X Environment

Scope

These directions are for setting up a single code repo on 2 servers, staging and production. This may not be the configuration for all projects.

Prerequisites

These directions assume that you have already been added as a collaborator to a Heroku environment. If not, you will need to be. You also need to have already configured your Laravel Homestead environment and checked out the codebase from the GitHub repo. Those directions are found elsewhere.

Step-by-Step Instructions

1. If you haven't already done so, create an account at heroku.com.
2. If you haven't done so previously, install the Heroku Toolbelt on your machine.
3. Browse through the Heroku collaboration documentation (but don’t execute the command line commands given).
4. Execute these commands in your local environment, to add the Heroku remotes for promotion:

• cd ~/Code/russellkeppner.com
• heroku git:remote -a russellkeppner-staging -r staging
• heroku git:remote -a russellkeppner -r production
• git config heroku.remote staging

5. Make development code changes.
6. Commit your changes to staging via Git (command line instructions given below, but this can also be done in SourceTree):

• git add -A .
• git commit -m "I built your site."
• git push staging master

7. Share/QA the results at: http://russellkeppner-staging.herokuapp.com
8. When approved, promote the changes to production:

• heroku pipelines:promote -r staging

9. Double-check site at: http://russellkeppner.herokuapp.com
10. Profit!

Notes

1. Files specific to Heroku:

• Procfile
  Directives for Heroku environment configuration.
• nginx.conf
  Nginx configuration for the Heroku environment.