nginx-config-builder_skill

This skill generates production-ready NGINX configurations for static sites, reverse proxies, load balancers, and PHP/Node.js apps with secure defaults.
  • TypeScript

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill ehtbanton/claudeskillsrepo --skill nginx-config-builder

  • SKILL.md11.2 KB

Overview

This skill generates production-ready NGINX configuration files for web servers, reverse proxies, load balancers, SSL termination, static sites, SPAs, and PHP-FPM apps. It outputs valid nginx.conf / site.conf fragments with security headers, logging, gzip, caching and sensible defaults. Use it to quickly produce complete, testable configuration files ready to drop into /etc/nginx/ or /etc/nginx/conf.d/.

How this skill works

When invoked it returns a complete NGINX configuration tailored to the requested scenario (static site, reverse proxy, load balancer, SPA, PHP-FPM, etc.). Each output includes listen directives, SSL settings when requested, upstream definitions for backends, security headers, rate limits, logging paths, gzip and caching rules. The result is syntactically valid NGINX config intended to pass nginx -t after adjusting paths and certificate files.

When to use it

  • Create a secure static site configuration with HTTPS and caching
  • Generate a reverse proxy for Node.js or other backend services
  • Build a load balancer config for multiple backend servers
  • Provision SPA hosting with API and websocket proxying
  • Configure PHP-FPM sites (WordPress/Laravel) with fastcgi settings and security

Best practices

  • Always verify and replace certificate and path placeholders before deployment
  • Run nginx -t after installing the config and reload nginx gracefully (nginx -s reload)
  • Use upstream keepalive and health-aware settings for high traffic backends
  • Apply rate limiting zones for login and API endpoints to mitigate abuse
  • Separate site configs into /etc/nginx/conf.d/ and keep global security rules in a shared file

Example use cases

  • Create nginx.conf for a React SPA with an API proxied to localhost:3000 and long cache for static assets
  • Generate a reverse proxy config for a Node/Express app with websocket support and client_max_body_size for uploads
  • Produce a load balancer config using least_conn with weighted backend servers and a backup node
  • Build a WordPress NGINX config with PHP-FPM fastcgi settings and rules to deny sensitive files
  • Output a security.conf with rate limits, connection caps, and simple attack-mitigation regex blocks

FAQ

Yes—templates include SSL directives and example LetsEncrypt paths, but you must replace placeholders with your actual certificate and key locations.

Are the outputs immediately safe to use in production?

Outputs follow best practices (security headers, logging, gzip, timeouts) but require validation: confirm paths, upstream servers, and run nginx -t before reloading.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
nginx-config-builder skill by ehtbanton/claudeskillsrepo | VeilStrat