Serving media in development in Django - Step-by-Step Execution

Concept Flow - Serving media in development

Start Django development server

↓

Request for media file received

↓

Check if DEBUG is True

↓

Serve media file

↓

Media file delivered to browser

↓

End request

When running Django in development mode, media file requests are served directly by the development server if DEBUG is True.

Execution Sample

Django

from django.conf import settings
from django.conf.urls.static import static

urlpatterns += static(settings.MEDIA_URL, document_root=settings.MEDIA_ROOT)

This code adds URL patterns to serve media files during development.

Execution Table

Step	Action	Condition	Result
1	Start Django development server	DEBUG=True	Server ready to serve requests
2	Receive request for media file	Request URL starts with MEDIA_URL	Proceed to serve media
3	Check DEBUG setting	DEBUG=True	Serve media file from MEDIA_ROOT
4	Send media file content	File exists in MEDIA_ROOT	Media file delivered to browser
5	Request ends	Media file served	Response complete
6	If DEBUG=False	Media request received	Media not served by dev server, 404 or error

💡 Execution stops after media file is served or error returned if DEBUG is False

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
DEBUG	True	True	True	True	True
Request URL	N/A	/media/image.jpg	/media/image.jpg	/media/image.jpg	/media/image.jpg
Media file found	N/A	N/A	Yes	Yes	Yes

Key Moments - 2 Insights

Why does Django serve media files only when DEBUG is True?

Because in the execution_table row 3, serving media files is conditional on DEBUG=True to avoid exposing files in production.

What happens if the requested media file does not exist?

In step 4, if the file is missing, Django returns a 404 error instead of serving content.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does Django check if DEBUG is True?

A Step 3

B Step 2

C Step 4

D Step 5

💡 Hint

Check the 'Condition' column in execution_table row 3

According to variable_tracker, what is the value of DEBUG after step 4?

A False

B Undefined

C True

D None

💡 Hint

Look at the DEBUG row under 'After Step 4' in variable_tracker

If DEBUG was set to False, what would happen when a media file is requested?

A Media file is served normally

B Django returns 404 or error

C Server crashes

D Media file is served from cache

💡 Hint

Refer to execution_table row 6 for behavior when DEBUG=False

Concept Snapshot

Serving media in development:
- Add static(settings.MEDIA_URL, document_root=settings.MEDIA_ROOT) to urlpatterns
- Works only if DEBUG=True
- Development server serves media files directly
- In production, media served by web server, not Django
- Prevents exposing media files when DEBUG=False

Full Transcript

When you run Django's development server with DEBUG set to True, it can serve media files like images or videos directly. This happens because the URL patterns include a special setup that tells Django to look for media files in the MEDIA_ROOT folder when the URL starts with MEDIA_URL. When a request for a media file comes in, Django checks if DEBUG is True. If yes, it finds the file and sends it back to the browser. If DEBUG is False, Django does not serve media files and returns an error or 404. This setup is only for development convenience. In real deployment, a web server like Nginx or Apache handles media files.