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.

Practice

1. What is the main reason to use environment-based settings in a Django project?

easy

A. To keep sensitive data like passwords out of the code

B. To make the app run faster

C. To reduce the number of files in the project

D. To avoid using databases

Solution

1. Step 1: Understand environment-based settings purpose

   They help keep sensitive information like passwords and keys out of the codebase.

2. Step 2: Identify the main benefit

   This improves security and allows easy changes per environment without code edits.

3. Final Answer:

   To keep sensitive data like passwords out of the code -> Option A

4. Quick Check:

   Security = Keep secrets out [OK]

Hint: Environment settings protect secrets outside code [OK]

Common Mistakes:

• Thinking environment settings speed up the app
• Confusing environment settings with file count
• Believing environment settings remove database use

2. Which of the following is the correct way to get an environment variable named SECRET_KEY in Django settings?

easy

A. SECRET_KEY = os.get('SECRET_KEY')

B. SECRET_KEY = os.environ['SECRET_KEY']()

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

D. SECRET_KEY = getenv('SECRET_KEY')

Solution

1. Step 1: Recall correct function to read environment variables

   Use os.getenv('VAR_NAME') to safely get environment variables.

2. Step 2: Check syntax correctness

   SECRET_KEY = os.getenv('SECRET_KEY') uses correct syntax without extra parentheses or wrong function names.

3. Final Answer:

   SECRET_KEY = os.getenv('SECRET_KEY') -> Option C

4. Quick Check:

   Use os.getenv() for environment variables [OK]

Hint: Use os.getenv('VAR') to read environment variables [OK]

Common Mistakes:

• Adding parentheses after os.environ['VAR']
• Using non-existent os.get() function
• Calling getenv() without os prefix

3. Given this code in settings.py:

import os
DEBUG = os.getenv('DEBUG', 'False') == 'True'

What will be the value of DEBUG if the environment variable DEBUG is not set?

medium

A. Raises an error

B. True

C. None

D. False

Solution

1. Step 1: Understand default value in os.getenv()

   If DEBUG is not set, os.getenv('DEBUG', 'False') returns string 'False'.

2. Step 2: Evaluate comparison to string 'True'

   'False' == 'True' is False, so DEBUG becomes False (boolean).

3. Final Answer:

   False -> Option D

4. Quick Check:

   Unset DEBUG defaults to 'False' string, so boolean False [OK]

Hint: Default string 'False' != 'True' means DEBUG is False [OK]

Common Mistakes:

• Assuming default 'False' string converts to boolean True
• Expecting None when variable is missing
• Thinking code raises error if env var missing

4. You wrote this in settings.py:

import os
SECRET_KEY = os.getenv('SECRET_KEY')
DEBUG = os.getenv('DEBUG', False)

But DEBUG is always True even when you set DEBUG=False in the environment. What is the problem?

medium

A. os.getenv returns strings, so DEBUG is the string 'False', which is truthy

B. os.getenv cannot read boolean environment variables

C. SECRET_KEY must be set before DEBUG

D. You must import dotenv to use os.getenv

Solution

1. Step 1: Understand os.getenv returns strings

   Environment variables are strings, so os.getenv('DEBUG', False) returns string 'False' if set.

2. Step 2: Recognize string 'False' is truthy in Python

   Non-empty strings are True in boolean context, so DEBUG is always True.

3. Final Answer:

   os.getenv returns strings, so DEBUG is the string 'False', which is truthy -> Option A

4. Quick Check:

   Env vars are strings; 'False' string is True in boolean [OK]

Hint: Remember env vars are strings, not booleans [OK]

Common Mistakes:

• Assuming os.getenv returns boolean type
• Thinking import order affects env var reading
• Believing dotenv is required for os.getenv

5. You want to set different database settings for development and production using environment variables. Which approach correctly applies environment-based settings in settings.py?

hard

A. Use if os.environ['ENV'] == 'production' without default and catch exceptions

B. Use os.getenv('ENV') == 'production' to load production DB settings, else development settings

C. Set all DB settings to default values and never change them

D. Hardcode production DB settings and ignore environment variables

Solution

1. Step 1: Use environment variable to detect environment

   Check os.getenv('ENV') to decide if running in production or development.

2. Step 2: Load DB settings conditionally

   Load production DB settings if ENV is 'production', else load development settings.

3. Final Answer:

   Use os.getenv('ENV') == 'production' to load production DB settings, else development settings -> Option B

4. Quick Check:

   Conditional DB config based on ENV variable [OK]

Hint: Use ENV variable to switch settings safely [OK]

Common Mistakes:

• Hardcoding production settings in code
• Not providing default for os.environ access
• Ignoring environment variables for config