dj-serve 1.1.0

Serve SPAs (Vue, React, Angular, vanilla HTML) directly from Django

dj-serve

Serve SPAs (Vue, React, Angular, Svelte, or vanilla HTML) directly from Django — no separate static server needed.

from dj_serve import dj_serve

urlpatterns = [
    dj_serve("/", "dist/", "index.html", "dist/400.html", "dist/500.html"),
]

Why?

Traditional Django + SPA setups require either:

• A separate static file server (nginx, Apache, CDN) — adds deployment complexity.
• django.contrib.staticfiles — not designed for SPAs; no client-side routing fallback, no custom error pages per frontend.

dj-serve solves both:

Feature	staticfiles	dj-serve
SPA fallback (client-side routing)	❌	✅
Custom 400/500 pages per SPA	❌	✅
Isolated error handling (no global handlers)	❌	✅
Path traversal protection	❌	✅
Correct MIME types	✅	✅
Works with any prefix	✅	✅

Installation

pip install dj-serve

Requires Django ≥ 4.0 and Python ≥ 3.10.

Usage

Basic SPA

from django.urls import include, path
from dj_serve import dj_serve

urlpatterns = [
    path("admin/", admin.site.urls),
    path("api/", include("myapi.urls")),
    dj_serve("/", "dist/"),
]

dj_serve("/", "dist/") will:

1. Serve files from dist/ (e.g., dist/style.css at /style.css).
2. For any other route under /, serve dist/index.html — this enables client-side routing (Vue Router, React Router, etc.).
3. Return 404 if neither the file nor index.html exists.

With custom error pages

dj_serve("/", "dist/", error_400="dist/400.html", error_500="dist/500.html")

Error pages are served only for routes under this prefix — your API and admin endpoints keep their default error handling.

With a prefix

dj_serve("/app", "dist/", "index.html")

Serves the SPA at /app/, /app/about, /app/dashboard, etc.

Vanilla HTML site

dj_serve("/", "site/", entry_point="index.html")

Works the same way — SPA fallback just means unknown routes serve index.html.

Cache-Control headers

dj_serve("/", "dist/", cache_control="public, max-age=3600")

Apply the same value to all responses, or use a dict with glob patterns:

dj_serve("/", "dist/", cache_control={
    "*.html": "no-cache",
    "*.css":  "public, max-age=31536000, immutable",
    "*.js":   "public, max-age=31536000, immutable",
    "*":      "public, max-age=3600",
})

cache_control	Behaviour
None (default)	No Cache-Control header
str	Same value for every response
dict[str, str]	Glob patterns matched against the filename; first match wins

API

def dj_serve(
    prefix: str,
    dist_dir: str,
    entry_point: str = "index.html",
    error_400: str | None = None,
    error_500: str | None = None,
    cache_control: str | dict[str, str] | None = None,
    async_mode: bool = False,
) -> URLPattern:

Argument	Default	Description
prefix	—	URL prefix (e.g., /, /app)
dist_dir	—	Path to the directory with static files
entry_point	"index.html"	HTML file to serve for SPA fallback (client-side routing)
error_400	None	Path to a custom 400 error page
error_500	None	Path to a custom 500 error page
cache_control	None	Cache-Control header value. str for all files, dict for per-pattern (glob)
async_mode	False	Use async I/O with aiofiles. Requires pip install dj-serve[async]

How it works

1. Django resolves the URL through the re_path pattern.
2. The view looks for the requested file in dist_dir.
3. If found → served with the correct MIME type.
4. If not found → serves entry_point (SPA fallback).
5. If the entry point is missing → serves the custom error_400 page, or 404.
6. If an exception occurs → serves the custom error_500 page, or 500.

All error handling is contained within the view — no global handler400/handler500 configuration needed.

ASGI Support

dj-serve works with both WSGI and ASGI servers (uvicorn, daphne, hypercorn).

Synchronous mode (default)

dj_serve("/", "dist/")

Uses synchronous I/O. Django runs the view in a threadpool under ASGI.

Async mode

dj_serve("/", "dist/", async_mode=True)

Uses non-blocking I/O with aiofiles. Best for ASGI servers under high concurrency.

Install the async extra:

pip install dj-serve[async]

Production Deployment

For production, dj-serve provides dj_serve_middleware() which wraps your Django application with production-grade static file serving:

• WSGI (gunicorn, waitress, uwsgi, etc.) → uses WhiteNoise
• ASGI (uvicorn, daphne, hypercorn, etc.) → uses WhiteSnout

Installation

# For WSGI deployments
pip install dj-serve[wsgi]

# For ASGI deployments
pip install dj-serve[asgi]

# For both
pip install dj-serve[wsgi,asgi]

WSGI Deployment

In your wsgi.py:

from django.core.wsgi import get_wsgi_application
from dj_serve import dj_serve_middleware

application = get_wsgi_application()
application = dj_serve_middleware(application, "dist/")

ASGI Deployment

In your asgi.py:

from django.core.asgi import get_asgi_application
from dj_serve import dj_serve_middleware

application = get_asgi_application()
application = dj_serve_middleware(application, "dist/", async_mode=True)

Advanced Configuration

Pass additional options to the underlying middleware:

# WSGI with WhiteNoise options
application = dj_serve_middleware(
    application,
    "dist/",
    max_age=86400,  # 1 day cache
    allow_all_origins=True,
)

# ASGI with WhiteSnout options
application = dj_serve_middleware(
    application,
    "dist/",
    async_mode=True,
    cache_max_age=86400,
    security_headers=True,
)

How It Works

The middleware and URL pattern work together:

1. Middleware intercepts requests for static files (CSS, JS, images) and serves them with compression, caching, and security headers
2. dj_serve() URL pattern handles SPA routing — when a file isn't found, it serves index.html for client-side routing

# urls.py — SPA fallback (always needed)
from dj_serve import dj_serve

urlpatterns = [
    dj_serve("/", "dist/"),
]

# wsgi.py or asgi.py — production static file serving
from dj_serve import dj_serve_middleware

application = dj_serve_middleware(application, "dist/", async_mode=True)

Backend Comparison

Feature	Builtin	WhiteNoise (WSGI)	WhiteSnout (ASGI)
SPA fallback	✅	❌ (needs dj-serve)	❌ (needs dj-serve)
Compression	❌	gzip + brotli	gzip + brotli
ETag / 304	❌	✅	✅
Async native	❌	❌ (WSGI)	✅
Rust acceleration	❌	❌	✅
Best for	Development	WSGI production	ASGI production

Development vs Production

• Development (DEBUG=True): Use dj_serve() URL pattern only — no warning
• Production (DEBUG=False): Configure dj_serve_middleware() in wsgi.py or asgi.py — otherwise a warning is logged

Testing locally

pip install -e ".[dev]"
pytest

License

MIT