Configuring uWSGI for Production: The defaults are all wrong
summary
Recommends a concrete uWSGI baseline: keep master on, enable threads, turn on strict-config-parsing and vacuum; set need-app=true so a syntax-error process fails to start; disable noisy default logging but log 4xx/5xx. Use worker recycling (e.g. max-requests=1000, resident memory limit ~2GB or hourly recycle) and harakiri 60s to kill stuck workers; enable signal delivery and auto-procname for observability. Also uses uWSGI cache, mules, cron/timers and dynamic scaling across many processes (often 96–128) — these settings cut incidents and simplify recovery.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:43Why are we here
- 4:15Master process
- 13:27Worker Recycling
- 16:54Hard Timeouts
- 21:00Prefix API
- 22:40cron and timer
- 26:09I am hiring
- 26:44Questions
