Skip to content

Add dotenv for local development #366

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

Closed
wants to merge 1 commit into from

Conversation

pietroalbini
Copy link
Member

dotenv allows configuring environment variables loaded by the program in a text file, removing the need to set them manually every time or to add them to a bashrc (or similar). It has no side effects if the .env file is not present.

The use case for it is local development, not production.

dotenv allows configuring environment variables loaded by the program in
a text file, removing the need to set them manually every time or to add
them to a bashrc (or similar). It has no side effects if the .env file
is not present.
@pietroalbini pietroalbini mentioned this pull request Jun 4, 2019
@QuietMisdreavus
Copy link
Member

I'm generally in favor. We already use environment files in production, but they're loaded via systemd. This allows someone to run the project outside of systemd, without using a weird copy/paste in the bash profile to set the environment for all their sessions. I've been considering putting this configuration in a file of some kind, and this is probably easier than manually parsing some TOML file or the like.

@pietroalbini
Copy link
Member Author

We're going to switch to docker-compose instead of vagrant, so this won't be needed anymore.

@pietroalbini pietroalbini deleted the dotenv branch August 22, 2019 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants