Production Nginx Config Generator for Apps

How to generate and install an Nginx configuration

Enter the public hostname and choose either a static document root or a private application port. The generator validates every value before it emits Nginx syntax. It then pairs the file with commands that install Nginx, write the exact configuration through a non-expanding heredoc, test the complete installed setup, reload safely, and request HTTPS only when selected.

1. Select Static website for HTML files or App / API for Node.js and Python.
2. Enter the domain, then set the root directory or private application port.
3. Open Advanced Production Settings to edit HTTPS, headers, cache, proxy, timeout, and rate-limit behavior.
4. Click Generate production config and review every production note.
5. Copy the file or download the .conf, then run deployment steps 1 through 4 in order.
6. Do not reload Nginx unless sudo nginx -t reports a successful syntax test.

What a production Nginx server block needs

A deployable site file connects a public server_name to either a filesystem root or an upstream proxy_pass. This generator also emits request limits, logs, compression, response headers, hidden-file protection, and explicit forwarding headers. For app mode, the upstream URL has no trailing URI, so Nginx preserves the original request path instead of replacing it.

Nginx defines proxy_pass as setting “the protocol and address of a proxied server.” See the officialproxy module reference.

Nginx defaults client_max_body_size to 1 MB; this tool chooses 10 MB so common forms and JSON uploads do not fail unexpectedly with HTTP 413. The app preset keeps the documented 60-second proxy read and send timeouts, while the connect timeout is reduced to 10 seconds so a dead local process fails promptly. All three remain editable.

Worked Nginx configuration examples

Static and application deployments differ at the final routing decision. Both still share the domain, port 80 listener, size limit, logs, headers, compression, and optional Certbot flow.

root /var/www/portfolio.example.com/html;
index index.html index.htm;

location / {
    try_files $uri $uri/ =404;
}

location / {
    proxy_pass http://127.0.0.1:8000;
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-For
                     $proxy_add_x_forwarded_for;
}

Production settings reference

These defaults avoid speculative tuning. Each one maps directly to generated Nginx syntax or a deployment command, so turning a control off removes its output rather than hiding it in comments.

Frequently asked questions