Skip to content

Latest commit

 

History

History
24 lines (19 loc) · 1.63 KB

HEROKU_HOWTO.md

File metadata and controls

24 lines (19 loc) · 1.63 KB
Raw

How to Deploy CuttingEdge on Heroku

Note: on Heroku, CuttingEdge uses heroku.config.rb instead of config.rb.

Note: if you will be using a public GitHub or GitLab repo to host your CuttingEdge configuration, make sure not to put any secrets in heroku.config.rb or projects.yaml. Instead, use environment variables (for instance to set authentication tokens).

Steps:

  1. Fork and clone this repository locally
  2. Move Procfile from the heroku subdirectory into the repository root and commit.
  3. Move the sample heroku.config.rb from the heroku subdirectory into the repository.
  4. Edit heroku.config.rb to suit your needs and commit.
  5. Edit projects.yml to suit your needs and commit it to the repo.
  6. gem install bundler && bundle install
  7. `git add Gemfile.lock && git commit -m "Commit Gemfile.lock for use on Heroku"
  8. heroku create my-cuttingedge
  9. heroku config:add HEROKU_APP_NAME=my-cuttingedge
  10. heroku addons:create heroku-redis:hobby-dev -a my-cuttingedge (using Redis is highly recommended on Heroku)
  11. git push heroku master
  12. Optional, if you want to receive email notifications:
  • heroku addons:create mailgun:starter
  • heroku config:add CUTTING_EDGE_MAIL_TO=mydependencies@mydependencymonitoring.com

You may also want to set some Heroku config variables, for instance to use authentication tokens in heroku.config.rb.