report configured containers Docker never lists as stopped
A name in SERVICES_ALIASES with no matching container (typo or deleted) produced no `docker ps -a` line, so it silently vanished from the dashboard instead of showing as a problem. Track which configured names were seen and append the leftovers as stopped, logging edge-triggered so a persistent typo doesn't reprint every 2s poll. Also corrects the kcmonitor container name and refreshes the README service list. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -70,7 +70,7 @@ Pushes a JSON object every 2 seconds with real system metrics from `psutil`:
|
||||
- `cpu_pct`, `mem_pct`, `mem_used_mb`, `disk_pct`
|
||||
- `cpu_temp` (reads `/sys/class/thermal/` as fallback)
|
||||
- `uptime_hrs`, `net_rx_kbps`, `net_tx_kbps` (values are in kB/s despite the field names)
|
||||
- `services` — live Docker container statuses via `docker ps -a`, with a ternary status model (`running`, `warning`, `stopped`). Monitored containers: gitea, samba, pihole, qbittorrent, frpc (ny), pinepods, frpc (ssh), jellyfin.
|
||||
- `services` — live Docker container statuses via `docker ps -a`, with a ternary status model (`running`, `warning`, `stopped`). Monitored containers: gitea, samba, pihole, qbittorrent, frpc (ny), pinepods, frpc (ssh), jellyfin, kc-start2, kc-monitor. A configured container Docker doesn't report at all (deleted, or a typo in `SERVICES_ALIASES`) is reported as `stopped` and logged once to stdout.
|
||||
- `local_time` fields for RTC sync (`y`, `mo`, `d`, `h`, `m`, `s`)
|
||||
|
||||
### contents_server.py -- port 8766
|
||||
|
||||
Reference in New Issue
Block a user