Cloud, Platform & Infrastructure · Checklist
Go-live checklist for a Django + Celery app
The checklist I used to take NXG from testing to launch: settings, boot, Celery, files and backups, alerts, speed, email, payments and the launch-day order. For any Django monolith with workers.
Celery
DevOps
Django
PostgreSQL
Redis
Go-live checklist for a Django + Celery app
I built this while taking NXG Collective from early testing to launch. It's the list I wish I'd had at the start: what to check before you let real users and real money through a Django monolith with Celery workers, Redis and Postgres. Tick every box, or write down why you're skipping it.
1. Settings
- [ ]
DEBUG = False, andALLOWED_HOSTSlists only your real domains. - [ ]
SECRET_KEYcomes from the environment and has never been committed. - [ ] HTTPS is enforced:
SECURE_SSL_REDIRECT,SESSION_COOKIE_SECURE,CSRF_COOKIE_SECURE. - [ ] HSTS is on (start with a short
SECURE_HSTS_SECONDS, raise it once you're sure). - [ ]
SECURE_PROXY_SSL_HEADERis set if you sit behind a proxy (Railway, Heroku, a load balancer). - [ ] You read the real visitor IP from the proxy header, or every rate limit treats all users as one visitor.
- [ ]
python manage.py check --deployshows no warnings you haven't decided on. - [ ] Placeholder values in
.env.examplecan't crash startup if someone copies them by mistake.
2. Install and boot
- [ ] Production installs only production requirements, and a CI job proves it boots with them (import every module, reach the broker). Dev-only packages hide missing dependencies.
- [ ] The container runs as a normal user, not root.
- [ ] Web, worker and beat each have their own start command and health check.
- [ ] Migrations run once per deploy (a pre-deploy step), not in every web process.
- [ ] Database connections stay within your plan's limit: (web workers × threads) + worker concurrency + beat + migrations.
3. Celery
- [ ] Every beat entry names a task the worker has actually registered. If it doesn't, the worker silently drops the message and the job never runs. Add a test for it.
- [ ] Every scheduled task can be called with the arguments beat sends (no datetimes, no required args).
- [ ] Task results aren't stored unless you read them (
task_ignore_result). - [ ] External calls (email, payments, AI, GitHub) run in tasks with timeouts and retries, never inside a web request.
- [ ] Something tells you when beat stops (for example, a smoke check on the last run time).
4. Files and data
- [ ] Uploads live in object storage (S3 or R2), not on the server's disk.
- [ ] Private files are served through permission-checked views or signed links.
- [ ] Signed links are cache-friendly (the same link for a while), or browsers re-download every image.
- [ ] Picture metadata (location, device) is stripped on upload.
- [ ] Nightly encrypted backups go somewhere other than the database's own host.
- [ ] You have restored a backup into a scratch database at least once and counted the rows. An untested backup is a guess.
- [ ] You've rehearsed a rollback and written down how long it took.
5. Errors and alerts
- [ ] Sentry (or similar) covers both web and the Celery worker.
- [ ] Personal data is scrubbed before events leave your server.
- [ ] You've sent a deliberate test error from web and from the worker, and the alert reached your phone within minutes.
- [ ] Someone reads the error feed every day for the first two weeks.
6. Speed
- [ ] Measure before you optimise: server time, query count, page weight, time to first byte from where your users actually are.
- [ ] Key pages stay under a fixed query budget, with tests that fail if they grow (
assertNumQueries). - [ ] HTML is compressed (gzip or Brotli). Static files are compressed and cached forever with hashed names.
- [ ] Fonts are served from your own domain: one less origin, and no visitor data sent to a third party.
- [ ] Images in long lists load lazily.
7. Email
- [ ] SPF, DKIM and DMARC pass for your sending domain.
- [ ] A real test email lands in the inbox, not spam.
- [ ] Marketing emails have one-click unsubscribe. Transactional ones don't need it.
- [ ] Test and sample accounts can never receive email.
8. Payments (if you take money)
- [ ] Webhooks are signature-checked, stored, and processed idempotently.
- [ ] A payment only counts when the amount and currency charged match what you asked for.
- [ ] Sandbox records are cleared before live keys go in.
- [ ] One real low-value payment has been made and refunded on the live keys.
- [ ] Paid features sit behind feature flags you can switch off in seconds.
9. Launch day, in order
- Take a backup.
- Put in the live payment keys and the webhook.
- Remove sample or demo data, and check real accounts by hand afterwards.
- Switch the feature flags on in a set order, with each change logged.
- Run a smoke test of your critical flows on production (in a transaction you roll back).
- Tag the release on the exact commit that's running.
- Watch errors, payments and queues daily for 14 days, and fix money bugs the same day.
Built for NXG Collective's own launch. Copy it, change it, make it yours.