Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

config with heroku #17

pivotalcommon opened this Issue Aug 9, 2011 · 2 comments


None yet
2 participants

We recently have been using a gem on a project and ran into a problem with it loading heroku config (#load_options_from_heroku). The problem occurs when we have the gem heroku install in our Gemfile, but have no configured heroku yet, as we are only developing locally -- not deploying.

The function (#load_options_from_heroku) does not take into account that someone has not typed in their credentials yet into heroku, so it waits for email and password credentials. Since its piping all of STDOUT to dev/null this was obvious to us when we were running our specs.

Can this be fixed, or made optional?


rtyler commented May 25, 2012

Hey @pivotalcommon, I know it's been forever since you opened this ticket, but do you think you could try the SAUCE_HEROKU_APP environment variable that @jodell has added to the latest code for the gem?


rtyler commented Dec 10, 2012

I'm going to close this out.

I am working on a side-project called heroku-sauce which might be of interest, the goal is to integrate more tightly with the Heroku CLI and provide easy Sauce testing from that angle.

@rtyler rtyler closed this Dec 10, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment