Export CSV on every table, edit recurring maintenance, runs-on nothing, and run package checks outside the agent sandbox
- Export CSV for the small tables that had none (reads the table as shown) - Servers page shows a skeleton while loading instead of "No servers registered yet" - Recurring maintenance schedules can be edited (PUT /schedules/:id) - A server can be set to run on nothing (servers.no_parent, migration 0028) - Linux agent v3: package-manager question runs in ExecStartPre=-+ outside the sandbox, with --prepare-updates and --check-updates modes - Docs: README, DATABASE, AGENT_UPDATE Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
c17e9aa140
commit
540ab704b7
32 files changed
+3003
-66
No files matched your search
@@ -164,6 +164,11 @@ All modules from the original plan are built:
|
||||
20 rows per page by default — adjustable under Settings → Display — and
|
||||
CSV export still covers every sorted/filtered row, not just the current
|
||||
page.
|
||||
The few small tables that have no search or sorting of their own (the
|
||||
maintenance lists, tags, share links, API tokens and webhooks, the
|
||||
Backup page's job and run lists, the comparison table) have an Export CSV
|
||||
too, which writes the table as it is on screen — times as exact timestamps,
|
||||
action buttons left out.
|
||||
- **Settings** (admin-only) — notification channels (Gotify, ntfy, SMTP,
|
||||
generic webhook) with per-channel test buttons, per-event toggles (DNS
|
||||
record added/updated/deleted, daily secret-expiry reminder and daily
|
||||
@@ -411,7 +416,9 @@ alert, not counted, left out of notifications and osTicket tickets, and labelled
|
||||
uptime ribbons and "Since you last looked"), and if the host comes back while a
|
||||
guest is still down, that guest alerts then as new — an outage is never swallowed.
|
||||
Links that loop back on themselves cover nothing, and setting one that would is
|
||||
refused.
|
||||
refused. "Nothing — it runs on its own" stops the guess for a server that isn't a
|
||||
guest (a physical machine that happens to share a Proxmox node's name), so its
|
||||
alerts always stand alone.
|
||||
|
||||
**Recurring maintenance** (Maintenance → Recurring) repeats a window on the days
|
||||
and clock time you choose — "Sundays 02:00–04:00 on these servers" — in the time
|
||||
@@ -419,7 +426,10 @@ zone of the browser it was made in, so 02:00 stays 02:00 across summer and winte
|
||||
time. Each time becomes an ordinary maintenance window a week ahead (shown on the
|
||||
timeline with vertical stripes, and in Scheduled), so any single one can be
|
||||
cancelled and stays cancelled. Turning a schedule off or removing it takes back
|
||||
the windows that haven't begun.
|
||||
the windows that haven't begun. Edit changes a schedule's name, days, time, length
|
||||
or what it covers: the windows that haven't begun are made again from the new
|
||||
settings (a single one cancelled by hand comes back too), and one already under
|
||||
way keeps its times and ends on its own.
|
||||
|
||||
**Running a playbook** from an alert or a server: a server's page has a "Run a
|
||||
playbook" card, and alerts about a server have a "Run…" button, which pick a
|
||||
@@ -433,7 +443,7 @@ and where. Operators and admins only.
|
||||
installed — how many, how many are security fixes, whether a restart is due, and
|
||||
how long updates have been waiting — plus the Docker containers with a newer image.
|
||||
The Linux agent asks apt, dnf or zypper (only what they already know; nothing is
|
||||
installed or refreshed) and the Windows agent asks Windows Update (at most every six
|
||||
installed or refreshed — that one question is asked outside the agent's sandbox, which `dnf` and `zypper` need) and the Windows agent asks Windows Update (at most every six
|
||||
hours, cached under `%ProgramData%\HomelabManager`). A server whose agent hasn't
|
||||
said — an older agent, or another package manager — shows "not reported", never "up
|
||||
to date"; run its install command again to update its agent (how, and how to
|
||||
|
||||
Reference in new issue
Block a user