Why production setup differs in Django - See It in Action

Understanding Why Production Setup Differs in Django

📖 Scenario: You are preparing a Django web application for deployment. You need to understand how the production setup differs from the development setup to ensure your app runs safely and efficiently on a real server.

🎯 Goal: Build a simple Django settings configuration that shows the key differences between development and production setups.

📋 What You'll Learn

Create a basic Django settings dictionary with DEBUG set to true

Add a variable to hold allowed hosts for production

Use an if statement to switch DEBUG off and set allowed hosts for production

Complete the settings with a secure secret key for production

💡 Why This Matters

🌍 Real World

Web developers must configure Django apps differently for development and production to keep apps secure and performant.

💼 Career

Understanding production setup is essential for deploying Django apps safely in real jobs and avoiding common security mistakes.

1

Create basic development settings

Create a dictionary called settings with the key DEBUG set to true to represent development mode.

Django

# Create the settings dictionary with DEBUG true
# Your code here

Hint

Use a Python dictionary with the key 'DEBUG' and value true.

2

Add allowed hosts for production

Add a variable called allowed_hosts and set it to a list containing 'example.com' and 'www.example.com' to represent production allowed hosts.

Django

settings = {
    'DEBUG': True
}

# Add allowed_hosts list for production
# Your code here

Hint

Create a list with the two domain strings exactly as shown.

3

Switch settings for production

Use an if statement that checks if settings['DEBUG'] is false. Inside it, set settings['ALLOWED_HOSTS'] to the allowed_hosts list and set settings['DEBUG'] to false to simulate production mode.

Django

settings = {
    'DEBUG': True
}

allowed_hosts = ['example.com', 'www.example.com']

# Add if statement to switch to production settings
# Your code here

Hint

Use if not settings['DEBUG']: to check production mode.

4

Add production secret key

Add a key SECRET_KEY to the settings dictionary with the value 'prod-secret-key-123' to represent a secure production secret key.

Django

settings = {
    'DEBUG': True
}

allowed_hosts = ['example.com', 'www.example.com']

if not settings['DEBUG']:
    settings['ALLOWED_HOSTS'] = allowed_hosts
    settings['DEBUG'] = False

# Add SECRET_KEY to settings
# Your code here

Hint

Add the 'SECRET_KEY' key with the exact string value inside the settings dictionary.

Practice

1. Why should DEBUG be set to False in a Django production setup?

easy

A. To speed up the development process

B. To enable automatic database migrations

C. To allow Django to serve static files directly

D. To prevent detailed error messages from being shown to users

Solution

1. Step 1: Understand the role of DEBUG in Django

   When DEBUG is True, Django shows detailed error pages with sensitive information.

2. Step 2: Consider security implications in production

   Showing detailed errors publicly can expose security risks, so DEBUG must be False in production.

3. Final Answer:

   To prevent detailed error messages from being shown to users -> Option D

4. Quick Check:

   DEBUG False hides errors [OK]

Hint: Remember: DEBUG False hides errors from users [OK]

Common Mistakes:

• Thinking DEBUG False speeds development
• Believing DEBUG controls static file serving
• Confusing DEBUG with database migrations

2. Which of the following is the correct way to specify allowed hosts in Django's settings.py for production?

easy

A. ALLOWED_HOSTS = ['yourdomain.com', 'www.yourdomain.com']

B. ALLOWED_HOSTS = ['localhost', '127.0.0.1']

C. ALLOWED_HOSTS = []

D. ALLOWED_HOSTS = '*'

Solution

1. Step 1: Understand ALLOWED_HOSTS purpose

   ALLOWED_HOSTS lists domain names your Django app can serve to prevent host header attacks.

2. Step 2: Choose correct production domains

   In production, you must list your real domain names, not localhost or empty list.

3. Final Answer:

   ALLOWED_HOSTS = ['yourdomain.com', 'www.yourdomain.com'] -> Option A

4. Quick Check:

   Production domains in ALLOWED_HOSTS [OK]

Hint: Use real domain names in ALLOWED_HOSTS for production [OK]

Common Mistakes:

• Leaving ALLOWED_HOSTS empty disables host checking
• Using '*' is insecure and not allowed
• Including only localhost for production

3. Given this production setting snippet:

DEBUG = False
ALLOWED_HOSTS = ['example.com']
STATIC_ROOT = '/var/www/static/'

What happens when you run python manage.py collectstatic?

medium

A. Static files are copied to '/var/www/static/' directory

B. Static files are served automatically by Django

C. An error occurs because DEBUG is False

D. Static files remain in app folders without change

Solution

1. Step 1: Understand collectstatic command

   It gathers all static files from apps and copies them to STATIC_ROOT for serving.

2. Step 2: Check STATIC_ROOT setting

   STATIC_ROOT is set to '/var/www/static/', so files copy there on collectstatic.

3. Final Answer:

   Static files are copied to '/var/www/static/' directory -> Option A

4. Quick Check:

   collectstatic copies files to STATIC_ROOT [OK]

Hint: collectstatic copies files to STATIC_ROOT folder [OK]

Common Mistakes:

• Thinking Django serves static files in production automatically
• Believing DEBUG affects collectstatic behavior
• Assuming static files stay in app folders

4. You deployed your Django app with DEBUG = False and ALLOWED_HOSTS = []. When accessing the site, you get a 400 Bad Request error. What is the likely cause?

medium

A. DEBUG must be True to allow requests

B. ALLOWED_HOSTS is empty, so Django blocks all hosts

C. Static files are not collected

D. Database settings are incorrect

Solution

1. Step 1: Analyze ALLOWED_HOSTS effect

   An empty ALLOWED_HOSTS means no hosts are allowed, causing 400 errors.

2. Step 2: Understand DEBUG role

   DEBUG False is correct for production; it does not cause 400 errors by itself.

3. Final Answer:

   ALLOWED_HOSTS is empty, so Django blocks all hosts -> Option B

4. Quick Check:

   Empty ALLOWED_HOSTS causes 400 error [OK]

Hint: Empty ALLOWED_HOSTS blocks all requests [OK]

Common Mistakes:

• Thinking DEBUG True fixes 400 errors
• Blaming static files for 400 errors
• Assuming database issues cause 400 Bad Request

5. In production, why is it recommended to serve static files using a web server like Nginx instead of Django's development server?

hard

A. Because Django cannot serve static files at all

B. Because Nginx automatically sets DEBUG to False

C. Because Django's server is not optimized for static file delivery and can slow down the app

D. Because static files are not needed in production

Solution

1. Step 1: Understand Django's development server purpose

   Django's built-in server is for development only and is not efficient at serving static files.

2. Step 2: Recognize production server advantages

   Web servers like Nginx are optimized to serve static files quickly without slowing the app.

3. Final Answer:

   Because Django's server is not optimized for static file delivery and can slow down the app -> Option C

4. Quick Check:

   Use Nginx for static files in production [OK]

Hint: Use Nginx or similar for static files in production [OK]

Common Mistakes:

• Believing Django cannot serve static files at all
• Thinking Nginx changes DEBUG setting
• Assuming static files are unnecessary in production