Django on Kubernetes
The web framework for perfectionists, served by Gunicorn.
larakube django:newdjango:new starts a Django project with Django's own tooling and prepares it to run as a production service: Gunicorn with Uvicorn workers, migrations, a health check and the services you pick.
django:new creates the app and its Kubernetes manifests, but there's no production image for it yet: it warns No production image template for Django yet and skips the Dockerfile. With no image, larakube up has nothing to run and cloud:deploy has nothing to ship. NestJS is the first framework through this path, and the rest follow one at a time.
🚀 Create a project
larakube django:new portal
LaraKube CLI runs django-admin startproject inside a python:3.12-slim container, so you don't need Python on your machine, then asks:
| Choice | Options | With --fast |
|---|---|---|
| Database | PostgreSQL (recommended), MySQL, MariaDB | PostgreSQL |
| Cache | Redis (recommended), Memcached, Database | Redis |
| Object storage | None (local filesystem), MinIO (recommended), SeaweedFS, Garage | MinIO |
| Search | None, Meilisearch, Typesense | None |
🧱 What your app is set up for
| Piece | Detail |
|---|---|
| Server | Gunicorn with Uvicorn workers, listening on port 8000 |
| Migrations | python manage.py migrate — set up in the project, not yet run on deploy |
| Health check | /healthz |
| Commands | larakube art and larakube run proxy to python manage.py |
🏘️ Plex Commons
Django apps will join the shared Plex Commons for their database, cache and storage once this scaffolder is verified.