C0: clone blumeops via tailnet on ringtail provision
Switch ringtail.yml from forge.eblu.me (Fly proxy, WAN) to forge.ops.eblu.me (Caddy on indri, tailnet). Ringtail is always on the tailnet — the WAN round-trip was overhead and made provision-ringtail fail any time Fly was slow or down.
This commit is contained in:
parent
c00d7db507
commit
4e25180b0a
2 changed files with 2 additions and 1 deletions
1
docs/changelog.d/+ringtail-clone-via-tailnet.infra.md
Normal file
1
docs/changelog.d/+ringtail-clone-via-tailnet.infra.md
Normal file
|
|
@ -0,0 +1 @@
|
|||
Switch the ringtail provisioning playbook's blumeops clone URL from `forge.eblu.me` (public, via Fly proxy) to `forge.ops.eblu.me` (tailnet, direct via Caddy on indri). Ringtail is always on the tailnet, so the WAN round-trip is pure overhead — it also made `provision-ringtail` brittle whenever the Fly proxy was slow or down.
|
||||
Loading…
Add table
Add a link
Reference in a new issue