Nginx Config taste — ChatGPT prompt for Nginx setup
The Nginx Config taste ChatGPT prompt sets conventions for Nginx configuration and operations. Use it while configuring virtual hosts, HTTPS, or proxy routes.
CC0-1.0 ★ 178,201 updated 2026-10-24
Open on GitHubWhat Nginx Config taste does
The prompt lays out an Nginx approach for servers with many virtual hosts. It calls for one server block per file in sites-available or conf.d, with shared settings kept in snippets and brought in through include. Run nginx -t before reloading; the suggested reload options are nginx -s reload and systemctl reload, not a full restart.
Its guidance covers TLS, security headers, redirects, upstreams, caching, and request limits. Certbot and acme.sh are named for certificate automation, while static sites use try_files. Port 80 is reserved for ACME challenges, with other plain HTTP traffic redirected to HTTPS. Keep stub_status on localhost or an internal network.
For Claude Code, the install path is .claude/commands/prompts.csv.md. The prompt keeps worker settings near their defaults, including worker_processes auto, and calls for measurements before tuning them.
What it helps with
- split virtual hosts into separate files
- redirect plain HTTP traffic to HTTPS
- forward proxy headers and set timeouts
- configure caching for static assets
- rate-limit login and API routes
Example prompts for the agent
- Set up Nginx for several domains, with separate
serverfiles and shared snippets. - Review this Nginx setup for HTTPS, HTTP redirects, and ACME challenges.
- Draft a proxy configuration with an upstream, timeouts, and
X-Request-IDforwarding.
How to install Nginx Config taste
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about Nginx Config taste
How do I install Nginx Config taste in Claude Code?
Place the command file at .claude/commands/prompts.csv.md.
What does Nginx Config taste do?
It provides conventions for Nginx configuration, including virtual hosts, TLS, proxying, caching, and request limits.
Which certificate tools does Nginx Config taste mention?
It names Certbot and acme.sh for certificate automation.
Source text
prompts.csv · CC0-1.0
# Nginx Config taste of an ops engineer who maintains many virtual hosts - Keep one server block per file under `sites-available` or `conf.d`, named after the domain it serves. Confidence: 0.85 - Put shared settings (TLS, security headers, proxy defaults) in snippet files and `include` them instead of copying blocks. Confidence: 0.90 - Run `nginx -t` before every reload and reload with `nginx -s reload` or `systemctl reload`, never a full restart. Confidence: 0.95 - Keep configs in version control and deploy them through automation, not by editing files on the server. Confidence: 0.90 - Redirect all plain HTTP to HTTPS with a single `return 301`, and keep the port 80 block for ACME challenges only. Confidence: 0.90 - Allow only TLS 1.2 and 1.3 with a modern cipher list, and enable OCSP stapling. Confidence: 0.90 - Automate certificates with Certbot or acme.sh and alert well before expiry. Confidence: 0.90 - Add HSTS only after HTTPS works everywhere, starting with a short `max-age` before going long. Confidence: 0.80 - Set `server_tokens off` and add basic security headers (`X-Content-Type-Options`, `Referrer-Policy`, `frame-ancestors` via CSP). Confidence: 0.85 - Define a default server that returns `444` so requests with unknown Host headers never reach an app. Confidence: 0.85 - Prefer `return` over `rewrite` for redirects, and avoid `if` inside `location` except for `return` or `rewrite`. Confidence: 0.85 - Use `try_files` for static sites and single-page apps instead of chains of rewrite rules. Confidence: 0.85 - Forward `Host`, `X-Forwarded-For`, `X-Forwarded-Proto` and `X-Request-ID` to upstreams in one shared proxy snippet. Confidence: 0.85 - Use named `upstream` blocks with `keepalive` connections for backend pools. Confidence: 0.80 - Set explicit proxy timeouts and `client_max_body_size` per location rather than relying on defaults. Confidence: 0.80 - Serve hashed static assets with long `Cache-Control` and `immutable`, and HTML with short or no caching. Confidence: 0.85 - Enable gzip or Brotli for text types only, never for already compressed images or archives. Confidence: 0.80 - Rate limit login and API endpoints with `limit_req_zone`, using `burst` and `nodelay` to stay friendly to real users. Confidence: 0.80 - Use a JSON access log format with request time, upstream time and request id so logs are easy to query. Confidence: 0.80 - Expose `stub_status` only on localhost or an internal network for metrics scraping. Confidence: 0.75 - Keep worker settings near defaults (`worker_processes auto`) and tune only with measurements in hand. Confidence: 0.70
© f · CC0-1.0 · f/prompts.chat