7

Every time I push a new version to my staging heroku app, the RACK_ENV and RAILS_ENV variables are changed to "production", instead of "staging" which is the value I manually assigned. This started happening a couple of hours ago. A line like this is logged on the activity page on the heroku site on every deploy: v741 app_owner@gmail.com: Add RAILS_ENV, RACK_ENV, PATH, LANG, GEM_PATH config 6 minutes ago

I should talk to heroku support, but it seems that now the only place where questions can be asked is here, they remove the site support...

pb2q
  • 58,613
  • 19
  • 146
  • 147
Sonny
  • 71
  • 1
  • 1
    They have support here https://help.heroku.com/tickets/new. After you search in the Help section, the "open a support ticket" option is located at the bottom. I just submitted a ticket regarding this for my app – Jonathan Mui Oct 03 '12 at 09:47
  • Thanks! the open a new ticket link is pretty hidden, is good to force people to search first, but... – Sonny Oct 03 '12 at 16:12

1 Answers1

6

Same here. Fortunately, it does not happen after a rollback.

Fortunately a deploy on production does not set the variables to staging !

EDIT:

Heroku answer on a ticket: Hi, looks like a bug on our end. I'm notifying our ruby team

EDIT 2:

They said the bug was fixed yesterday, and yes, it was. But… the bug has just happened again right now……

ronnieonrails
  • 2,129
  • 1
  • 14
  • 13