Skip to content

docs: Maestro server + Trusted-Hub gateway deployment runbook - #171

Open
subhangR wants to merge 1 commit into
stagingfrom
chore/deployment-runbook
Open

docs: Maestro server + Trusted-Hub gateway deployment runbook#171
subhangR wants to merge 1 commit into
stagingfrom
chore/deployment-runbook

Conversation

@subhangR

Copy link
Copy Markdown
Owner

Adds docs/DEPLOYMENT.md — a single end-to-end runbook for building, deploying, and operating the Maestro stack on the EC2/Tailscale VPS.

Covers

  • Architecture: the two stacks (maestro-server :4570, maestro-gateway :4580) and how they relate.
  • Prereqs & access: box specs, tooling, public-IP rotation, TCC key gotcha, swap.
  • Building: build:server / build:gateway / build:web vs build:web:gateway, the node-pty linux-binary check, and the web-build heap (NODE_OPTIONS=6144).
  • maestro-server: /etc/maestro/maestro.env, systemd unit, verify.
  • Claude auth: initial login, CLAUDE_CONFIG_DIR pooled subscription, the onboarding-seed gotcha. Codex: optional, off by default.
  • Tailscale: serve mappings, and account-switch recovery steps.
  • Gateway (Trusted Hub): Phase 1 dev-header → Phase 2 Firebase login + allowlist + separate dist-gateway build + RTDB presence dashboard + side-port test → domain flip; the hub auth/routing flow.
  • Firebase: SA key, authorized domains, RTDB rules deploy.
  • Update/rollback + a troubleshooting table of every issue hit in the real deploy (node-pty, OOM, duplicate const, CORS Origin, unauthorized-domain, startup-race 401, tailscaled stale state after account switch, IP rotation, TCC).

Grounded in maestro-gateway/deploy/DEPLOY.md, gateway.env.example, the systemd units, database.rules.json, and the actual on-box deployment. No secrets inlined.

🤖 Generated with Claude Code

…runbook

Covers building (node-pty linux binary + web-build heap gotchas), maestro-server
systemd/env, Claude/Codex pooled auth, Tailscale serve + account-switch recovery,
the full gateway Phase 1/2 (dev-header -> Firebase login + allowlist + RTDB presence
dashboard), the hub auth/routing flow, update/rollback, and a troubleshooting table
of issues seen in the real deploy.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant