wild-cloud/wild-pc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

deploy: fix tunnel unit name so deploy auto-reloads cloudflared

Browse Source 
_TUNNEL_NAME was "tunnel", but the deployment is named castle-tunnel, so
unit_name() produced castle-tunnel.service — a unit that doesn't exist (the
real one is castle-castle-tunnel.service). The is-active check never matched,
so deploy printed "Tunnel not running" and skipped the ingress reload. New
public: true services then 404'd until a manual tunnel restart.

Set _TUNNEL_NAME = "castle-tunnel" to match the deployment name, mirroring
_GATEWAY_NAME. Deploy now restarts cloudflared on ingress changes.
This commit is contained in:
Paul Payne
2026-07-01 16:54:27 -07:00
parent d34ff9220d
commit 25e2275999
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
core/src/castle_core/deploy.py
View File

@@ -190,7 +190,8 @@ def _acme_preflight(config: CastleConfig, messages: list[str]) -> None:
) )
_TUNNEL_NAME = "tunnel" # the cloudflared service is castle-tunnel # Tunnel service name in the registry → its systemd unit (castle-castle-tunnel).
_TUNNEL_NAME = "castle-tunnel"
def _write_tunnel_config(registry: NodeRegistry, messages: list[str]) -> None: def _write_tunnel_config(registry: NodeRegistry, messages: list[str]) -> None: