.env.example

IMAGE=registry.example.com/youruser/status:latest
PORT=3035
NPM_BASE_URL=http://proxy.example.com:81
NPM_EMAIL=api@example.com
NPM_SECRET=
# Comma-separated regex patterns for which domains to include
NPM_INCLUDE_PATTERNS=\.example\.com$,\.dev\.example\.com$

# Gates the /admin UI (host visibility overrides, manual targets). Leave
# unset to disable /admin entirely.
ADMIN_PASSWORD=change-me
Initial commit — status checker service Polls Nginx Proxy Manager API for proxy hosts matching configurable domain patterns (NPM_INCLUDE_PATTERNS), HTTP-checks each every 60s, serves results as JSON (/api/status) and a terminal-aesthetic HTML page (/). Port 3035. NPM connection and domain filter patterns are fully configurable via environment variables — see README and .env.example. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> 2026-07-07 21:36:43 +02:00			`IMAGE=registry.example.com/youruser/status:latest`
			`PORT=3035`
			`NPM_BASE_URL=http://proxy.example.com:81`
			`NPM_EMAIL=api@example.com`
			`NPM_SECRET=`
			`# Comma-separated regex patterns for which domains to include`
			`NPM_INCLUDE_PATTERNS=\.example\.com$,\.dev\.example\.com$`
Add admin UI: per-host visibility overrides and manual targets NPM stays the source of truth for which domains exist; this adds an optional enrichment layer on top of the existing NPM_INCLUDE_PATTERNS filtering, gated behind ADMIN_PASSWORD (disabled entirely if unset). - Force-show/force-hide any NPM-discovered host regardless of what the include pattern would otherwise decide - Per-host display name and check path overrides - Manually add targets that aren't proxied through NPM at all - Every override falls back to the NPM-derived default when unset — a host with no override behaves exactly as before this existed Host overrides and manual targets live in SQLite (better-sqlite3, WAL mode) and are re-read on every 60s check tick, so admin changes take effect within one cycle with no restart. NPM host discovery keeps its original 10-minute cadence — only the local override reads happen every tick. The core merge (NPM hosts + overrides + manual targets -> final check list) is a pure function in targets.ts, kept separate from the checker's I/O for testability. Verified end-to-end against a local mock NPM server (auth, force-show/hide, rename, custom check path, manual targets, reset-to-default all propagate correctly) and against the actual Docker build/runtime (better-sqlite3's native addon builds and loads correctly in the Alpine image). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> 2026-07-10 15:40:57 +02:00
			`# Gates the /admin UI (host visibility overrides, manual targets). Leave`
			`# unset to disable /admin entirely.`
			`ADMIN_PASSWORD=change-me`