Fold four pages into the pages they belong to; add a Backups menu group
Dependencies become a view of the Map (graph with the editor under it), Sessions the 'Signed in now' tab of Users, the Audit Log the 'Raw audit log' tab of the Change log, and the Diagnostic Log the 'Call log' tab of Integrations (admins). Backup coverage and Proxmox Backup move to a new Backups group. Old addresses redirect; a shared ViewTabs component does the tabs. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
4e0c6927b2
commit
1432b148e9
19 files changed
+177
-102
No files matched your search
@@ -16,7 +16,7 @@ Authentik (OIDC), with local admin/operator/viewer roles.
|
||||
|
||||
All modules from the original plan are built:
|
||||
|
||||
- Monorepo scaffold, Tabler-themed app shell with a grouped sidebar (Infrastructure, Network, Monitoring, Automation, Operations, Administration; groups open on demand, the one holding the current page is always open, and what you leave open is remembered)
|
||||
- Monorepo scaffold, Tabler-themed app shell with a grouped sidebar (Infrastructure, Backups, Network, Monitoring, Automation, Operations, Administration; groups open on demand, the one holding the current page is always open, and what you leave open is remembered)
|
||||
- Authentik OIDC login, roles (first user to sign in becomes admin), audit log
|
||||
(changes made in the app, sign-ins and sign-outs with the IP they came from, new accounts, and the log's own
|
||||
automatic trimming — attributed to "system"; settings changes show what changed, but never credentials)
|
||||
@@ -47,7 +47,7 @@ All modules from the original plan are built:
|
||||
stored snapshots have failed verification or were never verified.
|
||||
The osTicket widget shows how many tickets are open, overdue, and awaiting
|
||||
a staff reply.
|
||||
- **Diagnostic Log** (admin-only) — every call this app makes to a DNS
|
||||
- **Diagnostic Log** (admin-only; Administration → Integrations → *Call log*) — every call this app makes to a DNS
|
||||
provider or integration (Tailscale, Proxmox, Synology, Semaphore, Gitea,
|
||||
Dockhand, Uptime Kuma, Proxmox Backup Server, osTicket), success or failure, with latency and the error message if it
|
||||
failed — the last 500 calls, filterable by source/result, for
|
||||
@@ -254,7 +254,7 @@ audit log (as `session` / `login_failed`, with the address and a short reason),
|
||||
Every response carries `frame-ancestors 'none'`, `X-Frame-Options`, `nosniff` and a no-referrer-to-other-sites policy. In production the app
|
||||
refuses to start without a `SESSION_SECRET`, and warns if it is still the placeholder from `.env.example`.
|
||||
Things to know: the first account to sign in becomes admin, so sign in yourself first on a new install. A session lasts up to 7 days after last use,
|
||||
and disabling someone in Authentik does not end it — delete them on the Users page (or revoke the session on the Sessions page) and it ends at once.
|
||||
and disabling someone in Authentik does not end it — delete them on the Users page (or end the session under Users → *Signed in now*) and it ends at once.
|
||||
If Authentik uses a certificate from an internal CA, point Node at the CA with `NODE_EXTRA_CA_CERTS=/path/to/ca.pem` rather than turning verification
|
||||
off with `NODE_TLS_REJECT_UNAUTHORIZED=0`.
|
||||
|
||||
@@ -402,7 +402,7 @@ devices, Uptime Kuma monitors, Gitea repositories or Semaphore templates, a
|
||||
click (or Enter) on a row opens a panel with everything known about it, without
|
||||
leaving the table.
|
||||
|
||||
**Map** (Infrastructure → Map) draws how things connect: which Proxmox host each
|
||||
**Map** (Infrastructure → Map) has two views, *Connections* and *Dependencies* (see below). *Connections* draws how things connect: which Proxmox host each
|
||||
linked server runs on, which DNS names point at it (an A or AAAA record holding
|
||||
one of the server's own addresses — nothing is guessed from names), and which
|
||||
Uptime Kuma monitors watch it. Hover or tab to a box to light up its
|
||||
@@ -445,9 +445,9 @@ kept, `/metrics` has each subject's age and result, and everything is in the cha
|
||||
**The change log** (Operations → Change log, operators and administrators) is one list of what has changed, newest first and grouped by day: agents updated,
|
||||
settings changed (with what to what), maintenance started and ended, dependencies edited, hardware added, endpoint checks and restore tests, alerts raised and cleared —
|
||||
each as a sentence. Narrow it by kind of change, by server, by how far back (a day to everything kept), or by a word; "Show older" goes on from where it stopped; CSV
|
||||
export. A server's Activity card links to its slice of it. Sign-ins and people's own data exports aren't changes and are left out. The Audit Log remains the raw table.
|
||||
export. A server's Activity card links to its slice of it. Sign-ins and people's own data exports aren't changes and are left out. The raw audit log is the other tab of the same page (Change log → *Raw audit log*).
|
||||
|
||||
**Dependencies beyond servers** (Infrastructure → Dependencies). Say that Gitea needs the server it is installed on, or that a server
|
||||
**Dependencies beyond servers** (Infrastructure → Map → *Dependencies*, which draws the graph with the editor under it). Say that Gitea needs the server it is installed on, or that a server
|
||||
needs Proxmox to answer. When what is needed is down, the alert of what needs it is folded under the first one exactly like a
|
||||
guest under its host — shown, labelled "caused by …", left out of notifications and tickets — and the root cause says what else it
|
||||
takes down. It follows chains and the "runs on" links of servers; something needing two things is explained by whichever is down;
|
||||
@@ -597,7 +597,7 @@ every few hours, with each day as an all-day event and maintenance with its star
|
||||
calendar; *with names* also gives the name and a link back. Like any share link the address is shown once and can be removed. Tailscale keys are asked for at most every
|
||||
ten minutes, and only those the integration reports as expiring soon are listed.
|
||||
|
||||
**Backup coverage** (Infrastructure → Backup coverage) answers "what isn't backed
|
||||
**Backup coverage** (Backups → Backup coverage) answers "what isn't backed
|
||||
up?" for every Proxmox guest: is a backup job covering it, when was it last backed up
|
||||
(from the newest snapshot on a Proxmox Backup Server, or the last successful Proxmox
|
||||
backup task that names the guest), and did that go well — Recent backup, Stale (older
|
||||
|
||||
Reference in new issue
Block a user