Why production setup differs in Django - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is DEBUG set to False in production?

In Django, what is the main reason to set DEBUG = False in a production environment?

A To prevent detailed error pages from showing sensitive information to users.

B To enable automatic database migrations on every request.

C To allow Django to serve static files directly in production.

D To disable the admin interface for security reasons.

💡 Hint

Think about what information you want to keep private from users.

Setting DEBUG = False stops Django from showing detailed error pages that can reveal sensitive data. This protects your app from exposing internal details to users.

❓ component_behavior

intermediate

Effect of ALLOWED_HOSTS in production

What happens if the ALLOWED_HOSTS setting in Django is empty when running in production with DEBUG = False?

A Django will serve static files instead of dynamic pages.

B Django will raise a <code>DisallowedHost</code> error and refuse to serve requests.

C Django will automatically add the current host to <code>ALLOWED_HOSTS</code>.

D Django will accept requests from any host without restriction.

💡 Hint

Consider what happens when a request comes from a host not listed in ALLOWED_HOSTS.

When DEBUG is False, Django checks ALLOWED_HOSTS to prevent HTTP Host header attacks. If empty, it raises DisallowedHost error.

❓ lifecycle

advanced

Static files handling difference in production

In Django, why do we run collectstatic during production setup but not usually in development?

A Because development servers do not support static files at all.

B Because <code>collectstatic</code> compiles Python code into bytecode for faster execution.

C Because in production, static files must be gathered in one place for the web server to serve efficiently.

D Because <code>collectstatic</code> deletes all static files to save disk space.

💡 Hint

Think about how static files like images and CSS are served differently in production.

In production, static files are collected into a single directory so a web server like Nginx can serve them efficiently. Development server serves them automatically without collecting.

📝 Syntax

advanced

Correct way to configure database in production

Which of the following Django DATABASES settings is correctly configured for a PostgreSQL production database?

A {'default': {'ENGINE': 'django.db.backends.postgresql', 'NAME': '', 'USER': '', 'PASSWORD': '', 'HOST': '', 'PORT': ''}}

B {'default': {'ENGINE': 'django.db.backends.sqlite3', 'NAME': 'prod_db.sqlite3'}}

C {'default': {'ENGINE': 'django.db.backends.mysql', 'NAME': 'prod_db', 'USER': 'admin', 'PASSWORD': 'securepass'}}

D {'default': {'ENGINE': 'django.db.backends.postgresql', 'NAME': 'prod_db', 'USER': 'admin', 'PASSWORD': 'securepass', 'HOST': 'db.example.com', 'PORT': '5432'}}

💡 Hint

Look for the correct engine and filled connection details for PostgreSQL.

Option D correctly uses the PostgreSQL engine and provides all necessary connection details for production.

🔧 Debug

expert

Diagnosing a production error with static files

A Django app in production shows broken CSS and images. The developer forgot to run collectstatic. What error or behavior will the browser most likely show?

A 404 Not Found errors for static file URLs.

B 500 Internal Server Error on every page load.

C CSS and images load normally without any errors.

D Django raises a DisallowedHost error.

💡 Hint

Think about what happens when static files are missing on the server.

If static files are not collected, the web server cannot find them, causing 404 errors when the browser requests CSS or images.

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