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

Load Development & Testing Environment Variables from ".env" #73

Open
billdybas opened this issue Jan 31, 2018 · 0 comments
Open

Load Development & Testing Environment Variables from ".env" #73

billdybas opened this issue Jan 31, 2018 · 0 comments

Comments

@billdybas
Copy link
Member

Currently we have nconf set up to read in environment variables. This works fine in production because we use Docker Swarm Secrets.

However, when developing locally or running tests, it's becoming annoying to have to set these environment variables on top of remembering which there are and which ones are set.

We could use dotenv to read in environment variables from a ".env" file, but my personal preference is envalid which is a wrapper around dotenv that allows you to define what type the vars should be and give them default values.

This task is complete when envalid is integrated into the API and there is a .env-sample file defined with the necessary env vars (but with blank values) to run the API.

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

No branches or pull requests

1 participant