📝 Infrastructure: How to provision and deploy the self-hosted sandbox orchestr...

Date: 2026-03-05
Time: 04:08:25 UTC
Session: gspace1-177.3
Agent: orchestrator
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

How to provision and deploy the self-hosted sandbox orchestrator on Hetzner?

Task: Provision and deploy self-hosted sandbox infrastructure on Hetzner server

🎯 Decision Made

Chosen:

Ran provision-server.sh (Firecracker, Node, nginx, bridge networking, SSL), installed Docker, built rootfs image, fixed NestJS DI bug (NetworkService not exported from SandboxModule), deployed orchestrator, enabled SANDBOX_SERVER_URL in .env.local

Options Considered:

• No alternatives documented

💭 Reasoning

Server was purchased in Session 150 but never provisioned. All scripts existed but hadn't been executed. The DI bug (MetricsCollector needing NetworkService which wasn't exported) was a latent issue never caught because the orchestrator was never deployed before.

📁 Files Involved

• tools/scripts/sandbox/provision-server.sh
• tools/scripts/sandbox/setup-network.sh
• deployment/sandbox-orchestrator/build-rootfs.sh
• deployment/sandbox-orchestrator/Dockerfile.rootfs
• APIs/sandbox-orchestrator/src/app/sandbox/sandbox.module.ts
• .env.local

🔗 Related

• Decision ID: dev_1772683701998_hmjzgi5
• Session: 177
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation