feat(m3-hermes): T3 Code cockpit — t3 serve systemd service, mesh-only
Three-lane agent setup (interactive cockpit / autonomous workers / Hermes control lane): T3 Code server runs on m3-hermes as a systemd service under the m3tam3re user, reachable only from the NetBird mesh (direct pairing, no T3 Connect cloud relay). - hosts/m3-hermes/services/t3code.nix: t3 serve on port 3773 (port registry), User=m3tam3re, keyless m3ta-gateway opencode config for harnesses, claude-code/opencode2 in service PATH - ports.nix: t3code = 3773 - fix netbirdRange in ai-memory.nix + hermes-dashboard.nix: the fleet mesh actually runs in 100.81.0.0/16 (wt0 kernel route), the previous 100.64.0.0/16 rules never matched any real peer One-time steps after deploy (documented in the module header): sudo -u m3tam3re claude auth login; t3 pair for client devices.
This commit is contained in:
1 parent
e965490e66
commit
c310ce57f4
5 files changed
+115
-2
No files matched your search
@@ -6,7 +6,7 @@
|
||||
}: let
|
||||
# Netbird mesh VPN range — dashboard only accessible from mesh peers.
|
||||
# m3-atlas Traefik proxies to this port over Netbird.
|
||||
netbirdRange = "100.64.0.0/16";
|
||||
netbirdRange = "100.81.0.0/16";
|
||||
apiPort = config.m3ta.ports.get "hermes-api";
|
||||
dashboardPort = config.m3ta.ports.get "hermes-dashboard";
|
||||
|
||||
|
||||
Reference in new issue
Block a user