# lucasdillmann/nginx-ignition

An user interface for the nginx web server, aimed at developers and enthusiasts that don't want to manage configuration files manually

Repository: https://github.com/lucasdillmann/nginx-ignition
Canonical: https://ross.abutalabs.com/products/nginx-ignition
Language: Go
License: MIT
License Family: permissive
Topics: golang, nginx, nginx-proxy, proxy, react, ui, gui, user-interface
Last push: 2026-08-15T18:31:22+00:00

## Health v2 (maintenance only)
Score: 83/100 (v2, computed 2026-09-03T02:39:23.370411+00:00)
- activity 97, release rhythm 86, longevity 47
- inputs: {"age_days": 669, "days_push": 18, "days_rel": 18, "gap_med": 5, "n_releases_24m": 78}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2135, forks 149 (observed 2026-08-28T04:06:17.495241+00:00)

## What it is
nginx ignition is a self-hosted web UI for managing the nginx web server, letting users configure virtual hosts, streams, SSL certificates, and server settings without editing config files manually. It can either run nginx itself or just generate configuration files, and includes integrations with Docker, Docker Swarm, Tailscale, NetBird, and TrueNAS.

## Use cases
- manage nginx virtual hosts through a web interface instead of editing config files
- set up a reverse proxy with automatic Let's Encrypt SSL certificates for my homelab
- proxy TCP and UDP streams with SNI routing and load balancing
- configure nginx caching, timeouts, and upload limits without touching nginx.conf
- secure my nginx admin panel with two-factor authentication and access control
- view real-time traffic statistics per host and upstream server
- generate nginx config files for Docker containers automatically

## When to choose
- you run a homelab or small server and want nginx managed through a GUI
- you need common reverse-proxy features like SSL, redirects, caching, and streams without manual config
- you want Docker or VPN integrations to auto-discover and route services
- you prefer generating nginx config files rather than running nginx through the tool

## When to avoid
- you operate large, highly complex enterprise nginx environments needing advanced fine-grained control
- you already have mature infrastructure-as-code or config management for nginx
- you need a proxy manager for non-nginx servers

## Facets
- artifact type: application
- maturity: active
- function: gui, proxy, http-server, auth, caching, monitoring, configuration-management
- domain: web-development, self-hosted, networking
- platform: self-hosted
- tags: nginx, reverse-proxy, lets-encrypt, ssl-certificates, homelab, virtual-hosts, tcp-udp-streaming, docker-integration, react-frontend, golang-backend, devops, docker, linux, web-server

## Member repositories
- lucasdillmann/nginx-ignition (main) score 83

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:17.495241+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:51:54.734217+00:00, confidence not recorded.
  - readme: https://github.com/lucasdillmann/nginx-ignition (fetched 2026-08-28T04:06:17.495241+00:00, sha 32a7efa58c72)
- Data as of 2026-08-30T08:39:29.467469+00:00.