anonpenguin23 92428df7e9 fix(cli): node restart restores the caddy/coredns frontend
caddy/coredns declare Requires=orama-node.service, so stopping orama-node
cascade-stops them; Requires propagates STOP but not START, and
StartServicesOrdered only starts the orama services — so a bare
'orama node restart' left caddy dead and the node's :443 HTTPS frontend
offline until the next reboot. Capture the active frontend units before the
stop and restart exactly those after the gateway is healthy. Adds
ServiceUnitExists helper + selectFrontendToRestore policy test.
2026-06-15 21:57:29 +03:00
..
2026-03-26 18:24:47 +02:00
2026-06-11 11:45:12 +03:00