explewd/npm-statuspage
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
0711a7f7ad1dcb8296c5ba4f952113ba1d1499f8
npm-statuspage/package.json

23 lines
492 B
JSON
Raw Normal View History

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
{
"name": "status",
"version": "0.1.0",
Add MIT license
2026-07-09 19:55:08 +02:00
"license": "MIT",
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
"type": "module",
"scripts": {
Fix: .env was never actually loaded for local dev README said cp .env.example .env then npm run dev, but nothing ever read the file into process.env — no dotenv, no --env-file. This predates the admin UI work; just surfaced by actually trying to run it. Fixed with Node's native --env-file flag on both dev and start (no new dependency). Doesn't affect Docker, which gets its config from docker-compose's environment: block directly, bypassing npm scripts entirely (CMD calls node dist/index.js directly). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-10 15:49:56 +02:00
"dev": "tsx watch --env-file=.env src/index.ts",
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
"build": "tsc",
Fix: .env was never actually loaded for local dev README said cp .env.example .env then npm run dev, but nothing ever read the file into process.env — no dotenv, no --env-file. This predates the admin UI work; just surfaced by actually trying to run it. Fixed with Node's native --env-file flag on both dev and start (no new dependency). Doesn't affect Docker, which gets its config from docker-compose's environment: block directly, bypassing npm scripts entirely (CMD calls node dist/index.js directly). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-10 15:49:56 +02:00
"start": "node --env-file=.env dist/index.js"
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
},
"dependencies": {
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
"express": "^4.19.2",
"better-sqlite3": "^11.3.0"
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
},
"devDependencies": {
"@types/express": "^4.17.21",
"@types/node": "^22.0.0",
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
"@types/better-sqlite3": "^7.6.11",
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
"tsx": "^4.15.0",
"typescript": "^5.5.0"
}
}
Reference in New Issue Copy Permalink