# Set up a production remote, pointing at your production
# heroku application. With this we can execute commands like
# `heroku restart -r production` instead of
# `heroku resetart -a some-crazy-app-name-that-i-cant-remember`
#
[remote "production"]
url = git@heroku.com:production-app-name.git
fetch = +refs/heads/*:refs/remotes/heroku/*
# Set up a similar staging remote for the same reasons
#
[remote "staging"]
url = git@heroku.com:staging-app-name.git
fetch = +refs/heads/*:refs/remotes/heroku/*
# Set up an alias so that commands that don't specify an application
# deal with staging implicitly.
# so `git push heroku master` still pushes to staging
# and `heroku scale web=0` shuts staging down
[heroku]
remote = staging
[remote "heroku"]
url = git@heroku.com:staging-app-name.git
fetch = +refs/heads/*:refs/remotes/heroku/*