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.

Sign up for GitHub

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

Jump to bottom

Drop the support for configuring Nesta with environment variables #165

Closed
gma opened this issue Nov 13, 2015 · 0 comments
Closed

Drop the support for configuring Nesta with environment variables #165

gma opened this issue Nov 13, 2015 · 0 comments
Milestone
1.0.0

Comments

@gma
Copy link
Owner

gma commented Nov 13, 2015

It was a daft thing to do in the first place, and since Glenn pointed out that the config file can be parsed with Erb (i.e. you can put <%= ENV.fetch('NESTA_TITLE') %> in your config file), there's no point keeping the extra code in Nesta.
@gma gma changed the title Drop the support for config via environment variables Drop the support for configuring Nesta with environment variables Nov 13, 2015
@gma gma added this to the 1.0.0 milestone Nov 14, 2015
gma added a commit that referenced this issue Mar 13, 2023
@gma
Drop support for config in environment variables
71fc37a 
Should anybody still want to configure Nesta with environment variables,
you can use Erb in `config.yml`, like this:

    some_value: <%= ENV.fetch('NESTA_VARIABLE') %>

Fixes #165
@gma gma closed this as completed in b5a228f Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
1 participant
@gma