docs: REPORT/CONTEXT/README for v0.57.0 Part A UI fixes
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -390,6 +390,18 @@ reach bind mounts). Auto-targeted: **prefer another registered user-data drive**
|
||||
`settings.CrossDriveBackup` and drives the "2. mentés" card. Runs daily (`tier2-backup`, 03:30) or via
|
||||
`POST /api/backup/tier2`. restic is **not** used — a plain browsable mirror.
|
||||
|
||||
**Per-app Tier-2 config panel (v0.57.0)** — `GET/POST /stacks/{name}/backup`
|
||||
(`internal/web/tier2_config_handler.go` + `templates/tier2_config.html`). The "2. mentés" row's
|
||||
**Beállítás** button links here (was the dead-end deploy page). Shows the effective off-drive target
|
||||
(pinned or auto), whether it's the size-limited internal SSD, the last-run reason, and lets the customer
|
||||
**pin a registered drive** (off physical disk) or **toggle Tier 2 off**. Always visible — single-SSD apps
|
||||
get the "csak DB/konfiguráció" note, non-HDD apps the "already in the PBS whole-guest snapshot" context.
|
||||
Two preference fields on `CrossDriveBackup` — `UserDisabled` + `PreferredTarget` (set via
|
||||
`Settings.SetTier2Preference`) — are **preserved across the runner's status writes** (`withTier2Prefs`):
|
||||
`selectTier2Target` honors a valid pin before auto-picking; `RunTier2` skips a disabled app. The runner
|
||||
re-validates the pin off-disk at run time. `Manager.Tier2Info(stackName)` is the read-only panel view
|
||||
(effective target + eligible alternative drives).
|
||||
|
||||
**Phase 1 — Database Dumps** (`internal/backup/dbdump.go`, scheduled 02:30)
|
||||
|
||||
- **Auto-discovery** of PostgreSQL and MariaDB containers via `docker ps` + `docker inspect`
|
||||
@@ -789,6 +801,15 @@ The de-privileged controller (slice 8C) sees only its own cgroup and cannot read
|
||||
|
||||
Path: `GET /api/host-metrics` → `Client.HostMetrics()` (leaf-pinned, per-guest-token agentapi client) → agent `GET /host/metrics`. Host-wide and token-authed (assumption: **one customer per host** — the home-server model). It is a **live** fetch (a fresh agent collect, not the 15-minute hub snapshot), so the page polls it every **8 s** while open. When the agent is unconfigured/unreachable the card shows a "nem elérhető" banner; the controller's own metric charts are unaffected.
|
||||
|
||||
**Storage-bar ordering + labels (v0.57.0):** the agent enumerates storages via `pvesm` in a
|
||||
non-deterministic order, so the per-storage capacity list (`#host-storage-bars`) reordered on every poll.
|
||||
`enrichHostStorageTargets` (`agent_host_metrics_handler.go`) sorts the response **server-side** —
|
||||
user-data (`usb`/`local-dir`) → system+apps (`lvmthin`/`lvm`) → builtin `local` → backup
|
||||
(`pbs`/`nfs`/`cifs`) → other, alphabetical by id within a tier — and attaches a friendly Hungarian
|
||||
`label` + one-line `purpose` per entry (rendered by `monitoring.html`, with the raw PVE id shown muted).
|
||||
**Display labels only — the PVE storage ids are never renamed** (vzdump/PBS configs reference them by
|
||||
name). This is distinct from the server-rendered, user-data-only `buildStorageBars` "Tárhely" list.
|
||||
|
||||
#### Alert System (`internal/web/alerts.go`)
|
||||
|
||||
State-based alerts displayed on all pages:
|
||||
|
||||
Reference in New Issue
Block a user