Environment variables for secrets in Django - Step-by-Step Execution

Concept Flow - Environment variables for secrets

Start Django app

↓

Read .env file or OS env

↓

Load secrets into environment variables

↓

Django settings.py reads env variables

↓

Use secrets in app securely

↓

App runs without secrets in code

Django app starts, reads environment variables from .env or OS, loads secrets into settings, then uses them securely without hardcoding.

Execution Sample

Django

import os
from dotenv import load_dotenv

load_dotenv()
SECRET_KEY = os.getenv('SECRET_KEY')

Load environment variables from .env file and assign SECRET_KEY from environment to Django settings.

Execution Table

Step	Action	Environment Variable Read	Variable Value	Effect
1	Start app	None	None	App starts, no env read yet
2	Call load_dotenv()	.env file read	SECRET_KEY=abc123	Env vars loaded into OS environment
3	Read SECRET_KEY	SECRET_KEY	abc123	SECRET_KEY variable set in settings
4	Use SECRET_KEY in app	SECRET_KEY	abc123	App uses secret without hardcoding
5	End	N/A	N/A	App runs securely with secrets from env

💡 All secrets loaded from environment variables, no secrets in code.

Variable Tracker

Variable	Start	After load_dotenv()	After os.getenv() call	Final
SECRET_KEY	None	abc123	abc123	abc123

Key Moments - 2 Insights

Why don't we hardcode the SECRET_KEY directly in settings.py?

Hardcoding secrets risks exposing them in code repositories. Using environment variables keeps secrets outside code, as shown in execution_table step 3.

What happens if the .env file is missing or SECRET_KEY is not set?

os.getenv('SECRET_KEY') returns None, so SECRET_KEY will be None, which can cause app errors. See execution_table step 3 where value would be None.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of SECRET_KEY after load_dotenv() is called?

A "abc123"

B None

C "secret"

D Empty string

💡 Hint

Check execution_table row 2 and variable_tracker column 'After load_dotenv()'

At which step does the Django app read the SECRET_KEY from environment variables?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at execution_table where SECRET_KEY is assigned from os.getenv

If the .env file is missing, what will SECRET_KEY be after os.getenv('SECRET_KEY')?

A Empty string

B "abc123"

C None

D Error thrown

💡 Hint

os.getenv returns None if variable not found, see key_moments explanation

Concept Snapshot

Use environment variables to store secrets like SECRET_KEY.
Load them with load_dotenv() or from OS environment.
Access with os.getenv('VAR_NAME') in settings.py.
Avoid hardcoding secrets in code for security.
If missing, os.getenv returns None.
Keep .env file out of version control.

Full Transcript

This visual trace shows how a Django app loads secrets securely using environment variables. The app starts, then calls load_dotenv() to read a .env file. This loads secrets like SECRET_KEY into the environment. Then settings.py reads SECRET_KEY using os.getenv. The secret is stored in a variable without hardcoding it in code. The app uses this secret securely. If the .env file or variable is missing, os.getenv returns None, which can cause errors. This method keeps secrets out of code repositories and improves security.