Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: ability to override RAILS_ENV for figaro only #244

Open
marienfressinaud opened this issue Aug 4, 2016 · 0 comments
Open

Comments

@marienfressinaud
Copy link

Hi,

we have two very similar instances of our application (staging and production) which are both based on the production environment.

Problem is we have to set different env variables for these two instances. As explain in https://devcenter.heroku.com/articles/deploying-to-a-custom-rails-environment, it is not recommended to create a staging environment since we want to keep production and staging environments as close as possible and it adds complexity.

My suggestion would be to consider an additional env variable such as FIGARO_ENV for the application.yml file so we can have:

production:
  S3_BUCKET: 'my-bucket-production'

staging:
  S3_BUCKET: 'my-bucket-staging'

But only one Rails environment. What do you think about this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant