Heroku自动将RAILS_ENV和RACK_ENV变量改变为“生产”每次部署 [英] Heroku automatically changing RAILS_ENV and RACK_ENV variables to "production" on every deploy

查看:104
本文介绍了Heroku自动将RAILS_ENV和RACK_ENV变量改变为“生产”每次部署的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

每次我将新版本推送到我的登台heroku应用时,RACK_ENV和RAILS_ENV变量将更改为生产,而不是手动分配,这是我手动分配的值。这发生在几个小时前。
这样一行登录活动页面上Heroku的网站上的每一个部署:
v741 app_owner@gmail.com:添加RAILS_ENV,RACK_ENV,PATH,LANG,GEM_PATH配置6分钟前



我应该与heroku支持商谈,但现在看来,现在唯一可以提问的地方就是在这里,他们删除了网站支持......

解决方案

同样在这里。幸运的是,它在回滚之后不会发生。



幸运的是,在生产环境中部署并不会将变量设置为分段!



编辑:



Heroku在一张票上回答:看起来像是我们末端的一个bug。我正在通知我们的红宝石团队编辑2:他们说这个bug昨天是修正的,是的, 它是。但是......错误再次发生了......


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...

解决方案

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……

这篇关于Heroku自动将RAILS_ENV和RACK_ENV变量改变为“生产”每次部署的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆