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.

Sign up for GitHub

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

environment template file #60

Open

bbelderbos opened this issue Dec 6, 2023 · 0 comments

Assignees

Collaborator

bbelderbos commented Dec 6, 2023

I would commit an .env-template (.env is already gitignored = good) to communicate which env variables to set ..

See https://pybit.es/articles/how-to-handle-environment-variables-in-python/

What I usually do is commit an empty .env-example (or .env-template) file so other developers know what they should set (see examples here and here). So a new developer (or me checking out the repo on another machine) can do a cp .env-template .env and populate the variables. As the (checked out) .gitignore file contains .env, git won’t show it as a file to be staged for commit.

bbelderbos assigned jwjacobson

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