Switch to using dotenv instead of yaml configuration files #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
YAML config files are difficult to maintain and grow and present challenges with managing configuration through local development and production environments.
According to the 12 Factor Application, configuration belongs in the Environment rather than in settings files. Heroku uses environment variables as the Application-facing interface to the
heroku config
command.This PR will start us out using a gem called dotenv to load environment variables needed in development from a file called
.env
in the application directory.This file will be ignored by Git so that each individual contributor's specific development configuration is not overwritten by changes made by others.
To start off new developers a bootstrapping script will be created which sets up a local development environment in as few manual steps as possible.
Ready status 🚥
dotenv-rails
gem.env
to.gitignore
script/bootstrap
programconfig/database.yml
from repository.