Environment-based settings in Django - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of using environment-based settings in Django?

To separate configuration for different environments like development, testing, and production, making the app more secure and easier to manage.

beginner

How can you load environment variables in a Django project?

By using packages like python-decouple or django-environ, or by accessing os.environ directly in your settings file.

beginner

Why should sensitive information like secret keys and database passwords be stored in environment variables?

To avoid exposing them in the codebase, which improves security and prevents accidental leaks when sharing or publishing code.

intermediate

What is a common pattern to organize Django settings for multiple environments?

Create a base settings file with common settings, then create separate files for development, testing, and production that import from base and override specific values.

beginner

How does using environment-based settings help when deploying a Django app to different servers?

It allows each server to have its own configuration without changing the code, making deployment smoother and reducing errors.

Which Python module is commonly used to access environment variables in Django settings?

A random

B sys

C json

D os

The os module provides access to environment variables via os.environ.

What is the benefit of separating settings into base, development, and production files?

A To allow different configurations for each environment

B To make the code run faster

C To keep all settings in one file

D To avoid using environment variables

Separating settings helps manage different configurations for development, testing, and production environments.

Which of these should NOT be hardcoded in your Django settings file?

A DEBUG mode

B Installed apps list

C Database password

D Static files path

Sensitive data like database passwords should be stored in environment variables, not hardcoded.

What package can help manage environment variables easily in Django?

A django-debug-toolbar

B python-decouple

C django-rest-framework

D pytest

python-decouple helps load environment variables and keep settings clean.

How do environment-based settings improve security?

A By hiding sensitive info from the codebase

B By making the app run faster

C By reducing the number of files

D By disabling debug mode automatically

Storing secrets outside the code prevents accidental exposure and improves security.

Explain how you would set up environment-based settings in a Django project.

Think about separating common and environment-specific settings.

Why is it important to avoid hardcoding secrets in Django settings, and how do environment-based settings help?

Consider security and deployment needs.

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