← back to Api Token Dashboard

.deploy.conf

26 lines

# api-token-dashboard — LOCAL-ONLY internal admin dashboard. NOT deployed to Kamatera.
#
# STALE-CONFIG FIX (2026-08-13, TK-10525 nav-agent rollout): the previous values
#   DEPLOY_PATH=/root/public-projects/api-token-dashboard
#   HEALTH_URL=http://127.0.0.1:9791/
# were BOTH wrong and dangerous:
#   • /root/public-projects/api-token-dashboard does NOT exist on Kamatera
#     (verified: no dir, no pm2 process, no nginx vhost) — there is no remote target.
#   • port 9791 is held by a DIFFERENT live app, ai-workforce
#     (server.mjs default PORT=9791 collides with it) — the health check + a
#     standalone boot both hit / squat ai-workforce, not this app.
#
# This dashboard is a Mac2-local-only, basic-auth (admin/DW2024!) status viewer of
# API-key / OAuth-token connections. It is dormant (no launchd job, no pm2 entry,
# referenced by no hub). The nav-agent grid-controls drop-in is applied + committed
# and serves 200 locally the moment the app runs on any free port (verified on a
# scratch port). The empty PROJECT_NAME below makes deploy.sh abort immediately
# ("PROJECT_NAME required") instead of rsyncing to the phantom path.
#
# If it ever needs to run persistently: pick a VERIFIED-FREE port (9883-9890 were
# all free 2026-08-13), e.g. `PORT=9884 node server.mjs`, and set values below to
# ITS OWN target — never reuse 9791 (that's ai-workforce's).
PROJECT_NAME=""
DEPLOY_PATH=""
HEALTH_URL=""