vh
87d7555fcf
A zsh glob failure in the staging step of91bda3cmeant 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 from17586abdid not stage either. Same content, just the half that got dropped.
42 lines
1.2 KiB
YAML
42 lines
1.2 KiB
YAML
---
|
|
# https://gethomepage.dev/latest/configs/docker/
|
|
#
|
|
# All four Docker hosts expose the engine on port 2375. This is plaintext
|
|
# and works fine on a trusted LAN; if any host is ever exposed or shared,
|
|
# switch to a TLS socket (examples commented below).
|
|
|
|
esh-vm-docker:
|
|
host: 10.0.50.45
|
|
port: 2375
|
|
|
|
ana-pfi-docker:
|
|
host: 10.250.50.70
|
|
port: 2375
|
|
|
|
nh3-pfi-docker:
|
|
host: 10.100.50.40
|
|
port: 2375
|
|
|
|
# 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.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
|
|
# esh-docker-vm via the mesh (10.6.110.50:2375 verified OPEN 2026-09-07).
|
|
irv-ml1-docker:
|
|
host: 10.6.110.50
|
|
port: 2375
|
|
|
|
# Example TLS socket (if/when a host moves off plaintext 2375):
|
|
# ana-pfi-docker:
|
|
# host: 10.250.50.70
|
|
# port: 2376
|
|
# tls:
|
|
# keyFile: docker-tls/ana-docker/key.pem
|
|
# caFile: docker-tls/ana-docker/ca.pem
|
|
# certFile: docker-tls/ana-docker/cert.pem
|