Heroku: manage INT env

[danconte72]

Requirements:

• Heroku CLI
• Be logged in heroku: $ heroku login
• Two projects on same heroku account: $ heroku create --remote appname

  To-do

  1. Update your remote heroku url name to herokuprod:

     $ git remote rename heroku herokuprod
     $ git remote -v

  2. Add remote heroku new app: 'enigmatic-spire-11550.git' in this case

     $ git remote add herokuint git@heroku.com:enigmatic-spire-11550.git

     Environments to Push

     $ git push herokuint master
     $ git push herokuprod master 

     Important!

     Don't forget to set your Config Variables:

     $ heroku config:set APP_DEBUG=true --remote herokuint
     $ heroku config:set APP_DEBUG=false --remote herokuprod

[vdias38]

Same codebase running as two separate Heroku apps – one staging and one production

Multiple remotes

I add integration remote env w/ $ git remote add staging git@heroku.com:enigmatic-spire-11550.git and rename heroku to production $ git remote rename heroku production

Then I can push to production with $ git push production master command.

Use your git config to specify a default app

By default, the heroku CLI creates projects with a heroku git remote (thus the normal git push heroku master). As we change our remote names we need to use --remote option of heroku CLI to define in which remote we are working. $ heroku config:set GITHUB_USERNAME=joesmith --remote staging To make things easier, you can use your git config (.git/config) to specify a default app. $ git config heroku.remote staging Now all heroku commands will default to the staging app.

Source: Heroku - multiple environments

My .git/config

[remote "production"]
        url = https://git.heroku.com/limitless-sea-32755.git
        fetch = +refs/heads/*:refs/remotes/production/*
[remote "staging"]
        url = https://git.heroku.com/enigmatic-spire-11550.git
        fetch = +refs/heads/*:refs/remotes/staging/*
[heroku]
        remote = staging