Production configuration: workers, Nginx, TLS and websockets

Sizing workers and memory limits, the reverse proxy with TLS, proxy_mode, websocket routing, and database filtering.

In this lesson

Workers and limits
Nginx, TLS, proxy_mode and websockets
Database filtering and exposure

Key points

workers ≈ CPU × 2 + 1, then check RAM; 1–2 cron threads
limit_memory_soft/hard, limit_time_cpu/real
Nginx TLS; / → 8069; /websocket → 8072 with upgrade headers; proxy_mode = True
dbfilter, list_db = False, http_interface 127.0.0.1, firewall

Real-world example

A 4-core, 16 GB server ran with workers = 0 (threaded mode); with 60 users it stalled at month-end. Switching to 9 workers with 2 GB soft/2.5 GB hard limits, 2 cron threads and the websocket proxy made month-end reports run while users kept working.

Questions and answers

What does http_interface = 127.0.0.1 achieve?

Odoo listens only locally; users must go through the proxy.

Which certbot plugin configures Nginx automatically?

certbot --nginx.

Read the full lesson, worked example and quiz