Aide-mémoire NGINX
Directives de configuration et opérations CLI NGINX : blocs server, en-têtes de proxy inverse, WebSockets, TLS, mise en cache, compression et limitation de débit.
Comment ça fonctionne
NGINX resolves `server { listen; server_name; }` first, then picks the most specific `location` block, forwarding or serving static files; always validate with `nginx -t` before `reload`.
Kit de survie
Les quelques commandes à apprendre en premier.
40 commandes
CLI Check, Reload & Logs
Validate syntax, reload without dropping connections, and inspect runtime config.
- Essentiel
Test all included nginx configuration files for syntax and path errors
nginx -tQuand l'utiliser
Never reload NGINX without testing first; broken config aborts reload safely only if checked.
Décomposition
- -t
- Parse config and test validity without applying
Exemple
sudo nginx -tRésultat
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful
Server Blocks, Locations & Static Files
Understand location matching precedence, SPA fallbacks, and clean redirects.
Reverse Proxy, Upstreams & WebSockets
Forward client IPs, HTTP/1.1 keepalives, WebSocket upgrades, and timeouts.
TLS, Security Headers & Rate Limits
Enforce HTTPS, TLS 1.2/1.3, security headers, and per-IP rate/size caps.
Compression, Caching & Tuning
Enable gzip, cache-control headers, worker limits, and proxy microcaching.