`.deploy.conf`

21 lines
# ai-workforce — LOCAL-ONLY (Mac2). NOT deployed to Kamatera.
#
# STALE-CONFIG FIX (2026-08-25): the previous values
#   PROJECT_NAME=ai-workforce
#   DEPLOY_PATH=/root/public-projects/ai-workforce
#   HEALTH_URL=http://127.0.0.1:9791/   PORT=9791
# were wrong + dangerous on Kamatera:
#   • There is NO pm2 process named `ai-workforce` on Kamatera (verified: pm2 describe
#     returns nothing, reload → "Process or Namespace not found").
#   • Kamatera :9791 is owned by a DIFFERENT app — /root/Projects/costa-rica/server.js
#     (verified via /proc/<pid>/cmdline). So HEALTH_URL would smoke-test costa-rica,
#     and a "successful" deploy would health-check the wrong app.
# ai-workforce runs Mac2-local (server.mjs default PORT=9791 — a Mac2 port, not Kamatera).
# The creds-safe fetch guard is applied + committed to public/index.html and serves the
# moment the app runs locally. Empty PROJECT_NAME makes deploy.sh abort immediately
# ("PROJECT_NAME required") instead of rsyncing to a phantom path / clobbering costa-rica.
# If it ever needs a Kamatera home: pick a VERIFIED-FREE port and set its OWN target.
PROJECT_NAME=""
DEPLOY_PATH=""
HEALTH_URL=""