Environment-based settings in Django - Step-by-Step Execution

Concept Flow - Environment-based settings

Start Django app

↓

Read environment variables

↓

Load base settings

↓

Override with env-specific settings

↓

Apply final settings

↓

Run app with these settings

Django reads environment variables first, then loads base settings, overrides them with environment-specific values, and finally applies these settings to run the app.

Execution Sample

Django

import os
from pathlib import Path

BASE_DIR = Path(__file__).resolve().parent.parent
SECRET_KEY = os.getenv('DJANGO_SECRET_KEY', 'default-secret')
DEBUG = os.getenv('DJANGO_DEBUG', 'False') == 'True'

This code loads Django settings using environment variables with defaults.

Execution Table

Step	Action	Environment Variable Read	Value Used	Setting Updated
1	Start app	None	None	None
2	Read DJANGO_SECRET_KEY	DJANGO_SECRET_KEY	supersecret123	SECRET_KEY = 'supersecret123'
3	Read DJANGO_DEBUG	DJANGO_DEBUG	True	DEBUG = True
4	Load base settings	None	Defaults	SECRET_KEY = 'default-secret' if no env, DEBUG = False if no env
5	Override with env values	DJANGO_SECRET_KEY, DJANGO_DEBUG	supersecret123, True	SECRET_KEY and DEBUG updated
6	Apply final settings	None	SECRET_KEY='supersecret123', DEBUG=True	Settings ready for app run

💡 All environment variables read and settings applied; app ready to run with these settings.

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
SECRET_KEY	None	supersecret123	supersecret123	supersecret123
DEBUG	None	None	True	True

Key Moments - 2 Insights

Why do we use os.getenv with a default value?

Using os.getenv with a default ensures the app has a fallback setting if the environment variable is missing, as shown in step 4 of the execution_table.

Why is DEBUG compared to the string 'True'?

Environment variables are strings, so we compare to 'True' to convert the string to a boolean, as seen in step 3 where DEBUG becomes True.

Visual Quiz - 3 Questions

Look at the execution_table, what value does SECRET_KEY have after step 2?

A default-secret

B None

C supersecret123

D False

💡 Hint

Check the 'Value Used' column in row for step 2.

At which step does DEBUG become True?

A Step 3

B Step 4

C Step 2

D Step 5

💡 Hint

Look at the 'Setting Updated' column for DEBUG in the execution_table.

If DJANGO_DEBUG was not set in environment, what would DEBUG be after step 4?

A True

B False

C None

D Error

💡 Hint

Refer to step 4 where defaults are loaded if env vars are missing.

Concept Snapshot

Environment-based settings in Django:
- Use os.getenv('VAR', default) to read env variables
- Convert strings to correct types (e.g., 'True' to True)
- Load base settings first, then override with env values
- Ensures flexible config for dev, test, production
- Keeps secrets out of code
- Enables easy config changes without code edits

Full Transcript

In Django, environment-based settings mean the app reads configuration values from environment variables. The app starts by reading these variables using os.getenv, providing default values if they are missing. For example, SECRET_KEY is read from DJANGO_SECRET_KEY or uses a default secret. The DEBUG setting is read as a string and converted to a boolean by comparing to 'True'. After reading these, Django loads base settings and overrides them with environment values. This approach keeps sensitive info like secret keys out of the code and allows easy changes for different environments like development or production. The execution table shows each step: starting the app, reading variables, loading defaults, overriding, and applying final settings. Variables like SECRET_KEY and DEBUG update step-by-step, ensuring the app runs with correct configuration.