This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'selective-env'
For a long time now Nesta has prevented you from spreading your settings between `config.yml` and the environment. If you set a single `NESTA_...` environment variable, Nesta would expect all your configuration to come from the environment. This behaviour was added back in commit 4ffa508, on the "heroku" branch. I have a sneaky suspicion that members of the community persuaded me that having a config file on Heroku was just not the done thing. It seems insane now, and the blog post where the idea was put forward (and in whose comments the debate was held) no longer exists. With the benefit of hindsight, this limitation seems insane! As Glenn has pointed out, anybody who wants to use the environment to configure their apps can use Erb tags within `config.yml` to read values from `ENV`, and insert them at run time. In the future, I'd like to remove all the code that reads the environment variables directly, and just recommend that people who want to use the environment do that. Nice one, Mr Gillen. :-)
- Loading branch information
Showing 2 changed files with 4 additions and 4 deletions.