deploy: ship Accounts panel to Kamatera; fix .deploy.conf HEALTH_URL to :9662 (was pointing at vendor-scrapers on 9661)

fa0d1c14da5882a2639cbc8266651f24245225c1 · 2026-07-14 11:46:01 -0700 · Steve

Files touched

M .deploy.conf

Diff

commit fa0d1c14da5882a2639cbc8266651f24245225c1
Author: Steve <steve@designerwallcoverings.com>
Date:   Tue Jul 14 11:46:01 2026 -0700

    deploy: ship Accounts panel to Kamatera; fix .deploy.conf HEALTH_URL to :9662 (was pointing at vendor-scrapers on 9661)
---
 .deploy.conf | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/.deploy.conf b/.deploy.conf
index 7d71535..a4a572b 100644
--- a/.deploy.conf
+++ b/.deploy.conf
@@ -1,6 +1,12 @@
 PROJECT_NAME=marketing-command-center
 DEPLOY_PATH=/root/DW-Agents/marketing-command-center
-HEALTH_URL=http://127.0.0.1:9661/api/health
+# The MCC listens on 9662 (nginx marketing.agentabrams.com → :9662). 9661 is a
+# DIFFERENT app (vendor-scrapers) — pointing here made the smoke test probe the
+# wrong service. NOTE: every route is basic-auth fail-closed, so this returns 401
+# (the DW-fleet "401 = healthy gate" convention), not 2xx — a 401 HERE means the
+# MCC is up + auth is working. Verify live with:
+#   curl -u admin:$MCC_PASS http://127.0.0.1:9662/api/health
+HEALTH_URL=http://127.0.0.1:9662/api/health
 # Protect gitignored runtime data from rsync --delete / overwrite on deploy.
 # follow-counts history accumulates one real row/day on the remote once IG creds
 # land; the local copy is only the dev/seed snapshot — never let it clobber the

← 3b13d2e Add Accounts panel: Amazon-style social-account filter rail · back to Marketing Command Center · Add Sounds & Assets panel: curated free/royalty-free music + 8bb0bc5 →