Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Feature request - Support different env configs #1343
By default (if custom config does not exist) read env variables from
dotenv is using for config parsing.
Not sure about
But according to dotenv FAQ
Should I commit my .env file?
No. We strongly recommend against committing your .env file to version control. It should only include environment-specific values such as database passwords or API keys. Your production database should have a different password than your development database.
Should I have multiple .env files?
No. We strongly recommend against having a "main" .env file and an "environment" .env file like .env.test. Your config should vary between deploys, and you should not be sharing values between environments.
Update issues according to latest PR updates
What .env* files are used?
Files priority (file is skipped if does not exist):
Priority from left to right.