Roland e51e5fb2fb controller: group services into Core vs Optional & Maintenance ... The Controller listed every wrolpi-* service in one flat table, which was confusing for new users who couldn't tell always-on infrastructure from one-off/dev/maintenance units. Services are now split into two groups computed once in the backend and exposed as `service.group`: * Core Services - persistent services enabled at boot (api, app, caddy, kiwix, ...), the normal running system. * Optional & Maintenance - one-off/dev/maintenance tasks (bootstrap, repair, upgrade, *-dev, discovered wrolpi-*), plus persistent services the user has disabled at boot (e.g. Samba with no shares configured). Rule: core iff kind == "persistent" and enabled; otherwise optional. Group membership only changes when the user toggles Boot, never on start/stop or polling, so rows stay put. Within each group, failed/stopped services sort first so problems stay visible. Feature parity across all three render paths: the React ControllerPage, the server-side Jinja template, and the client-side poll refresh. Docker containers have no group field and fall back to a single ungrouped list. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-07-22 19:46:13 -06:00
..
index.html	controller: group services into Core vs Optional & Maintenance	2026-07-22 19:46:13 -06:00