This repository has been archived by the owner on Jan 26, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 209
add python-decouple for handling the environment variables #580
Labels
Category: Coding
Changes to code base or refactored code that doesn't fix a bug.
Type: Enhancement
New feature or request.
Comments
sakshi1499
added
the
Status: Available
Issue was approved and available to claim or abandoned for over 3 days.
label
Jul 10, 2020
@sakshi1499 Can I try this. |
@saideepesh000 go for it 👍 |
theyashshahs
added
Category: Coding
Changes to code base or refactored code that doesn't fix a bug.
Type: Enhancement
New feature or request.
and removed
Status: Available
Issue was approved and available to claim or abandoned for over 3 days.
labels
Jul 13, 2020
@yashshah2820 @sakshi1499, For now, what should I keep in the .env file |
@saideepesh000 you can use the env variables used in the README like |
@yashshah2820 Ok, what should I keep the database password in env. And a small doubt, why are we not updating production.py with python-decouple, because that's going to be on the hosted part. |
@saideepesh000 it's all in the README |
1 task
SanketDG
pushed a commit
that referenced
this issue
Aug 20, 2020
SanketDG
pushed a commit
that referenced
this issue
Aug 20, 2020
4 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Category: Coding
Changes to code base or refactored code that doesn't fix a bug.
Type: Enhancement
New feature or request.
Description
As a member,
I need to add python-decouple to manage the DJANGO SECRET KEY and other sensitive env variables,
so that I can easily set up the project.
Acceptance Criteria
Update [Required]
Definition of Done
Estimation
1 hour
The text was updated successfully, but these errors were encountered: