Learn web development with step-by-step guides
From beginner to advanced — Django, Python, REST APIs, JavaScript, Bootstrap, and more
A calm, repeatable checklist for when the Django site is slow: read vmstat, iostat, ss and PSI with the USE method, trace stuck gunicorn workers with strace and py-spy, and prove whether the bottleneck is the app or PostgreSQL.
Turn an RCE in your Django app into a contained, unprivileged, read-only process: a digest-pinned multi-stage Dockerfile, a hardened Compose stack with dropped capabilities and an isolated database, file-based secrets, and Trivy scanning with SBOMs in CI.
Stop logs filling your disk: cap journald and logrotate, emit JSON from Django with a request ID shared with nginx, ship everything to Loki with Alloy, and query, retain and alert on it without leaking personal data.
Replace noisy CPU alerts with symptom-based paging for Django: blackbox uptime and TLS checks, django-prometheus metrics, a 99.5% SLO with multi-window burn-rate rules, and a complete Alertmanager config with grouping, inhibition and a watchdog.
The fastest request is the one your server never sees. Get Cache-Control right, use ETags without lying, cache pages for logged-in users safely, and purge by tag instead of by URL.
Stop configuring servers by hand. Provision with Terraform, configure with Ansible, keep secrets out of state, and rebuild any environment from an empty account in under an hour.
Run your own S3-compatible storage without fooling yourself about durability: bucket policies and least privilege, presigned URLs, direct browser uploads, why a single node is not a backup, mirroring, lifecycle rules, and when a managed provider wins.
Run several Django applications on a single machine without them taking each other down: label-driven routing, automatic certificates, network and resource isolation, independent deploys, per-app backups, and knowing when one server is no longer enough.
Sending mail is easy; arriving is not. Authentication records explained properly, the alignment rule most guides omit, why fresh servers cannot send, asynchronous delivery, bounce handling, and the headers that keep you out of the spam folder.
DNS treated as the distributed system it is: which records matter, what TTL really controls, why propagation is the wrong word, negative caching, CAA to restrict certificate issuance, and how to move a domain without a gap in service.
Everything a Django deployment needs to survive losing a server: consistent database dumps, media and secrets, encrypted offsite copies with restic, retention that survives ransomware, point-in-time recovery, and the restore drill nobody runs.
A complete playbook for moving a running Django site to a new server: inventory, runtime parity, database and media transfer, certificates before DNS, the delta-sync window, the IPv6 trap that breaks TLS issuance, and how to keep a working fallback.
These tutorials are written from real production work, and the best ideas come from readers. Got a suggestion, a correction, or a subject you keep searching for and never find properly explained? Tell us — we read every message, and requested topics move to the front of the queue.
Check out our premium Django packages and SaaS templates to jumpstart your project.