fv-ml1: the playbook + homepage body edits the rename commit missed

A zsh glob failure in the staging step of 91bda3c meant the five renamed
playbooks went in as pure renames with their bodies still saying ana-ml2 and
10.250.50.54, and the homepage docker.yaml direct-connection edit from 17586ab
did not stage either. Same content, just the half that got dropped.
This commit is contained in:
vh
2026-09-12 22:04:20 -07:00
parent 17586abb19
commit 87d7555fcf
6 changed files with 19 additions and 22 deletions
+5 -8
View File
@@ -17,15 +17,12 @@ nh3-pfi-docker:
host: 10.100.50.40
port: 2375
# fv-ml1-docker — reached via a socat proxy on ana-docker (stacks/fv-ml1-proxy).
# fv-ml1's own :2375 is up but not reachable cross-site from ESH (a return-route
# gap on fv-ml1 itself; no SSH access from the ops seats to fix its routing).
# ana-docker is on the same Anaheim subnet and IS reachable from ESH, so it
# relays 10.250.50.70:2354 -> 10.251.50.54:2375. Point back at 10.251.50.54:2375
# and `docker compose down` the proxy once fv-ml1 has a return route to ESH.
# fv-ml1-docker — direct. The socat relay on ana-docker (stacks/fv-ml1-proxy) was
# retired 2026-09-12: once FV joined the mesh and the three site gateways got
# 10.251.0.0/16 statics, ESH reaches fv-ml1:2375 directly (verified).
fv-ml1-docker:
host: 10.250.50.70
port: 2354
host: 10.251.50.54
port: 2375
# irv-ml1 — moved 10.100.79.3 -> 10.6.110.50 on 2026-09-06 (headscale cutover;
# the old wg0 tunnel IP is dormant and no longer answers). Reachable from