WhiteNoise for static files in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import WhiteNoise middleware in Django settings.

Django

MIDDLEWARE = [
    'django.middleware.security.SecurityMiddleware',
    '[1]',
    'django.contrib.sessions.middleware.SessionMiddleware',
]

Drag options to blanks, or click blank then click option'

A'django.middleware.csrf.CsrfViewMiddleware'

B'django.middleware.common.CommonMiddleware'

C'whitenoise.middleware.WhiteNoiseMiddleware'

D'django.middleware.clickjacking.XFrameOptionsMiddleware'

Attempts:

3 left

💡 Hint

Common Mistakes

Using other middleware names instead of WhiteNoiseMiddleware.

Not adding WhiteNoise middleware at all.

You add WhiteNoise by including 'whitenoise.middleware.WhiteNoiseMiddleware' in the MIDDLEWARE list.

2fill in blank

medium

Complete the code to set the static files storage to WhiteNoise's compressed manifest storage.

Django

STATICFILES_STORAGE = '[1]'

Drag options to blanks, or click blank then click option'

A'whitenoise.storage.CompressedManifestStaticFilesStorage'

B'django.contrib.staticfiles.storage.StaticFilesStorage'

C'django.contrib.staticfiles.storage.ManifestStaticFilesStorage'

D'whitenoise.storage.StaticFilesStorage'

Attempts:

3 left

💡 Hint

Common Mistakes

Using default Django staticfiles storage which lacks compression.

Using wrong WhiteNoise storage class names.

WhiteNoise recommends using CompressedManifestStaticFilesStorage for better caching and compression.

3fill in blank

hard

Fix the error in the code to correctly wrap the Django WSGI application with WhiteNoise.

Django

from django.core.wsgi import get_wsgi_application
from whitenoise import WhiteNoise

application = get_wsgi_application()
application = [1](application, root='/path/to/static')

Drag options to blanks, or click blank then click option'

AWhiteNoiseApplication

BWhiteNoiseMiddleware

CWhiteNoiseWrapper

DWhiteNoise

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect class names like WhiteNoiseMiddleware.

Not wrapping the application at all.

The WhiteNoise class wraps the WSGI application to serve static files.

4fill in blank

hard

Fill both blanks to configure WhiteNoise to add custom headers and enable max-age caching.

Django

application = WhiteNoise(application, root='/static')
application.add_headers('/static', [1])
application.max_age = [2]

Drag options to blanks, or click blank then click option'

A{'Cache-Control': 'max-age=31536000, public'}

B{'Cache-Control': 'no-cache'}

C31536000

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using string instead of dictionary for headers.

Setting max_age to zero disables caching.

WhiteNoise can add headers like Cache-Control for caching. max_age sets the cache duration in seconds.

5fill in blank

hard

Fill all three blanks to create a WhiteNoise middleware setup that compresses files, serves static files from 'staticfiles', and sets max-age to one day.

Django

MIDDLEWARE = [
    'django.middleware.security.SecurityMiddleware',
    [1],
]

STATICFILES_STORAGE = [2]

application = get_wsgi_application()
application = WhiteNoise(application, root='[3]')
application.max_age = 86400

Drag options to blanks, or click blank then click option'

A'whitenoise.middleware.WhiteNoiseMiddleware'

B'whitenoise.storage.CompressedManifestStaticFilesStorage'

Cstaticfiles

D'django.middleware.common.CommonMiddleware'

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong middleware or storage strings.

Incorrect static root path.

This setup adds WhiteNoise middleware, uses compressed manifest storage, and serves static files from the 'staticfiles' directory with a one-day cache.

Practice

1. What is the main purpose of using WhiteNoise in a Django project?

easy

A. To handle user authentication and sessions

B. To manage database migrations automatically

C. To serve static files directly without needing a separate web server

D. To optimize Django's template rendering speed

Solution

1. Step 1: Understand WhiteNoise's role

   WhiteNoise is designed to serve static files like CSS and JavaScript directly from Django without needing extra servers like Nginx.

2. Step 2: Compare with other options

   Other options relate to database, authentication, or templates, which are unrelated to WhiteNoise's purpose.

3. Final Answer:

   To serve static files directly without needing a separate web server -> Option C

4. Quick Check:

   WhiteNoise serves static files = A [OK]

Hint: WhiteNoise is about static files, not databases or auth [OK]

Common Mistakes:

• Confusing WhiteNoise with database or auth tools
• Thinking WhiteNoise speeds up templates
• Assuming WhiteNoise manages migrations

2. Which of the following is the correct way to add WhiteNoise middleware in Django's settings.py?

easy

A. "MIDDLEWARE = ['django.middleware.security.SecurityMiddleware', 'whitenoise.middleware.WhiteNoiseMiddleware'] + MIDDLEWARE"

B. "MIDDLEWARE = MIDDLEWARE + ['whitenoise.middleware.WhiteNoiseMiddleware']"

C. "MIDDLEWARE = ['whitenoise.middleware.WhiteNoiseMiddleware'] + MIDDLEWARE"

D. "MIDDLEWARE = ['whitenoise.middleware.WhiteNoiseMiddleware']"

Solution

1. Step 1: Identify middleware order

   WhiteNoise middleware should be placed just after SecurityMiddleware to work properly.

2. Step 2: Check the options

   "MIDDLEWARE = ['django.middleware.security.SecurityMiddleware', 'whitenoise.middleware.WhiteNoiseMiddleware'] + MIDDLEWARE" correctly adds WhiteNoise after SecurityMiddleware and before other middleware.

3. Final Answer:

   "MIDDLEWARE = ['django.middleware.security.SecurityMiddleware', 'whitenoise.middleware.WhiteNoiseMiddleware'] + MIDDLEWARE" -> Option A

4. Quick Check:

   WhiteNoise after SecurityMiddleware = A [OK]

Hint: WhiteNoise goes right after SecurityMiddleware in MIDDLEWARE list [OK]

Common Mistakes:

• Adding WhiteNoise at the end of MIDDLEWARE
• Replacing entire MIDDLEWARE with only WhiteNoise
• Adding WhiteNoise before SecurityMiddleware

3. Given this settings.py snippet:

STATICFILES_STORAGE = 'whitenoise.storage.CompressedManifestStaticFilesStorage'

What happens when you run python manage.py collectstatic?

medium

A. Static files are collected but not compressed or hashed

B. Static files are collected and compressed with hashed names for caching

C. Static files are ignored and not collected

D. An error occurs because the storage class is invalid

Solution

1. Step 1: Understand CompressedManifestStaticFilesStorage

   This storage compresses static files and adds hashes to filenames for better caching.

2. Step 2: Effect of collectstatic

   Running collectstatic collects all static files, compresses them, and renames with hashes.

3. Final Answer:

   Static files are collected and compressed with hashed names for caching -> Option B

4. Quick Check:

   CompressedManifestStaticFilesStorage compresses and hashes = C [OK]

Hint: CompressedManifestStaticFilesStorage compresses and hashes files on collectstatic [OK]

Common Mistakes:

• Thinking files are not collected
• Assuming no compression or hashing happens
• Believing the storage class causes errors

4. You added WhiteNoise middleware but your static files are not served in production. Which is the most likely cause?

medium

A. You did not install Django

B. You added WhiteNoise middleware at the end of the MIDDLEWARE list

C. You set DEBUG = True in production

D. You forgot to run python manage.py collectstatic

Solution

1. Step 1: Check static files preparation

   WhiteNoise serves static files from the collected directory, so collectstatic must be run.

2. Step 2: Analyze other options

   Middleware order matters but usually won't stop serving completely; DEBUG True affects debug server; not installing Django is unrelated if app runs.

3. Final Answer:

   You forgot to run python manage.py collectstatic -> Option D

4. Quick Check:

   Missing collectstatic = D [OK]

Hint: Always run collectstatic before deploying with WhiteNoise [OK]

Common Mistakes:

• Ignoring collectstatic step
• Misplacing middleware but not running collectstatic
• Confusing DEBUG setting with static serving
• Assuming Django is not installed if app runs

5. You want to serve static files efficiently with WhiteNoise and also enable long-term caching. Which combination of settings is best?

hard

A. Add WhiteNoise middleware after SecurityMiddleware and set STATICFILES_STORAGE to 'whitenoise.storage.CompressedManifestStaticFilesStorage'

B. Add WhiteNoise middleware at the start of MIDDLEWARE and set STATICFILES_STORAGE to 'django.contrib.staticfiles.storage.StaticFilesStorage'

C. Do not add WhiteNoise middleware and set STATICFILES_STORAGE to 'whitenoise.storage.CompressedStaticFilesStorage'

D. Add WhiteNoise middleware after SessionMiddleware and set STATICFILES_STORAGE to 'django.contrib.staticfiles.storage.StaticFilesStorage'

Solution

1. Step 1: Middleware placement for WhiteNoise

   WhiteNoise middleware must be placed immediately after SecurityMiddleware for proper static file serving.

2. Step 2: Choosing STATICFILES_STORAGE for caching

   'CompressedManifestStaticFilesStorage' compresses files and adds hashes for long-term caching, which is best practice.

3. Step 3: Evaluate other options

   Other options either place middleware incorrectly or use storage classes that don't support long-term caching well.

4. Final Answer:

   Add WhiteNoise middleware after SecurityMiddleware and set STATICFILES_STORAGE to 'whitenoise.storage.CompressedManifestStaticFilesStorage' -> Option A

5. Quick Check:

   Correct middleware order + caching storage = B [OK]

Hint: Middleware after SecurityMiddleware + CompressedManifestStaticFilesStorage for caching [OK]

Common Mistakes:

• Placing middleware too early or late
• Using default storage without hashing
• Skipping middleware but setting storage
• Using storage without compression or hashing