Environments¶
Status: Current | Last reviewed: 2026-09-18
Run TrueServe outside production.
Contents¶
| Doc | Purpose |
|---|---|
| Vanguard on Codespaces | The simplest dev path |
| Vanguard on EC2 | The shared EC2 dev box |
| City dev environments | rome / kyiv / istanbul / richmond / macau / shimla |
| Laptop access to Dev and QA | Mac/Windows WireGuard relay setup, scoped DNS and per-device bundles |
| Mac laptop setup | Laptop-only instructions with explanations for each step |
| Windows laptop setup | Laptop-only instructions with explanations for each step |
| Windows OpenVPN pilot | Shimla companion relay and Windows setup when another VPN client is needed |
| Windows OpenVPN laptop setup | Import, connect, test and disconnect using OpenVPN Community GUI |
| City relay rollout | Installed release, per-city endpoints and acceptance results |
| Official Dev/QA debugging | Tunnel/API access, Grafana logs and the correct Git source ref |
| City Grafana credentials | Token setup in the correct OS account, verification and rotation |
| Update flow | How a Vanguard commit propagates to the cities |
| Happy fleet control | Mobile monitoring + control of Claude/Codex sessions across all environments |
Quick context¶
Both "Vanguard" flavors run the same devcontainer. The difference is the host:
- Codespaces: GitHub Codespaces creates a fresh devcontainer on demand. Use for quick iteration, demos, anything you don't need to keep.
- EC2: A long-lived
g4dnrunning the same devcontainer image, branded by its hostname (rome, kyiv, istanbul, richmond, macau, shimla). Each city is a city-tagged feature branch ofvanguard.
A cluster-deployed environment (Sentinel, customer EKS, etc.) is documented in 05-deployment, not here.