🏗️ Architecture: What is the deploy process for sandbox-orchestrator on Hetzn...

Date: 2026-03-20
Time: 18:22:35 UTC
Session: gspace1-246.7
Agent: orchestrator
Confidence: 98%
Status: ✅ Documented

📋 Decision Context

Question:

What is the deploy process for sandbox-orchestrator on Hetzner dedicated servers?

Task: Not specified

🎯 Decision Made

Chosen:

Build locally on Mac (nx build sandbox-orchestrator), scp main.js to /var/lib/sandbox-orchestrator/ on server, SSH to restart systemd service. Script: deployment/sandbox-orchestrator/deploy-orchestrator-host.sh. The monorepo is NOT cloned on the server — only the built binary.

Options Considered:

1. Clone repo on server + build there (original script, wrong assumption)
2. Build locally + scp + restart (chosen, matches actual setup)
3. Docker container on server
4. Railway deployment

💭 Reasoning

The original deploy script assumed the monorepo was cloned on the Hetzner server (git pull + yarn install + nx build on host). Investigation revealed the server only has the built binary at /var/lib/sandbox-orchestrator/main.js managed by a systemd unit. Script was rewritten to match reality: build local → scp → restart. Verified working: health check returns ok, dashboard-summary returns host metrics.

📁 Files Involved

• deployment/sandbox-orchestrator/deploy-orchestrator-host.sh
• /var/lib/sandbox-orchestrator/main.js

🔗 Related

• Decision ID: dev_1774030955292_locgmpx
• Session: 246
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation