Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add support for .env file

See original GitHub issue

Requirement

Pre-requisite

Elementary knowledge of Python

Dependencies

None

Description

Typically, the part that’s given in config.py should actually be set as environment variables in a separate .env file. A sample file example.env is checked into git, whereas the .env file is gitignore-d. I think it’d be better to follow this practice and move away from config.py.

Issue Analytics

State:
Created 4 years ago
Comments:22 (21 by maintainers)

Top GitHub Comments

2reactions

chttrjeankrcommented, Mar 20, 2020

What is import dotenv?

This is a module in Python that can be looked up here. This is a really easy way of loading the environment variables from .env files and makes the code look a lot cleaner. To support this, requirements.txt needs to have another line appended.

1reaction

Varshney200commented, Mar 20, 2020

You need to add a template .env so that users can refer to it and create their own .env with their API keys and DB passwords ?

.env files are to be gitignored so should this template be a text file and the user should be asked to make changes into it and rename it as .env in their local repo?