Files
esh-pfi-infrastructure/configs/homepage/docker.yaml
T
vh 5ef502e7cc configs/homepage: re-enable irv-ml1-docker provider — host recovered 2026-04-25
Driver bump survived after all (595.58.03, kernel 6.1.0-37, both GPUs
detected and modules loaded). 5 GPU stacks back up clean (comfyui,
cosyvoice, qwen3-tts, index-tts, parakeet — all healthy). Homepage
discovery can resume polling 10.100.79.3:2375 over the WG tunnel.
2026-04-27 15:15:46 -07:00

39 lines
960 B
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
ana-ml2-docker:
host: 10.250.50.54
port: 2375
# irv-ml1 — reachable ONLY via WireGuard tunnel, so docker auto-discovery
# traffic traverses the tunnel. If WG drops, homepage will show irv-ml1
# services as offline until reconnect.
irv-ml1-docker:
host: 10.100.79.3
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