Speedtest Tracker, Costs, "Having trouble" on status pages, grouped Integrations and Dashboard
- Speedtest Tracker integration: charts, alerts for a slow line (median of the last three tests under a share of what is paid for) and for failing tests. - Costs page (Records): things paid for by hand plus Hetzner's estimate, totals per currency, bills rolled forward into Coming up as Renewals. - Status pages: a "Having trouble" state for things that answer but have an open alert; Speedtest reads as the internet. - Integrations page and kind picker grouped like the sidebar (one shared types file); Notifications "What to send" shown one group at a time; Dashboard integration sections follow the menu groups, with tiles for integrations that have no widget. - Docs, tests, and ROLES.md menu table brought up to date. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
78822346b1
commit
f86661f6c9
49 files changed
+18156
-238
No files matched your search
@@ -30,7 +30,9 @@ All modules from the original plan are built:
|
||||
integration — Tailscale by OS, Proxmox by node (VM/LXC counts too),
|
||||
Dockhand by container state (plus host count), Semaphore and Gitea by
|
||||
last-run status (plus private-repo count), and Synology's CPU/RAM
|
||||
alongside its disk-health breakdown. Breakdowns render as a stacked
|
||||
alongside its disk-health breakdown. The integration widgets are in sections that follow the sidebar's groups (Infrastructure, Apps, Network and so on) and show only
|
||||
the groups you have something connected in; an integration with no widget of its own (Jellyfin, Immich, Nextcloud, Hetzner, Speedtest …) gets a small tile: whether it works,
|
||||
how many alerts are open for it, and a link to its page. Breakdowns render as a stacked
|
||||
proportion bar with a legend — no charting
|
||||
library, matching the rest of the app's plain-Tabler-CSS approach.
|
||||
The Servers widget shows how many servers are online, offline, or have never
|
||||
@@ -155,11 +157,12 @@ All modules from the original plan are built:
|
||||
read-only user — the only integration here that isn't a REST API.
|
||||
Read-only, no actions.
|
||||
|
||||
The Integrations page itself is now just a list of configured
|
||||
integrations (name/type/status, visible to every role) with an
|
||||
admin-only "Add integration" button and edit/enable/disable/delete
|
||||
actions per row — the nine dedicated pages above are where you
|
||||
actually use each one.
|
||||
The Integrations page itself is a list of configured
|
||||
integrations (name/type/status, visible to every role), grouped the way the sidebar
|
||||
groups their pages (Infrastructure, Apps, Backups, Network, Monitoring, Automation),
|
||||
with an admin-only "Add integration" button — its kind picker is the same groups,
|
||||
with a search box — and edit/enable/disable/delete actions per row. The dedicated
|
||||
pages are where you actually use each one.
|
||||
- Every table in the app is click-to-sort on any column (numbers, booleans,
|
||||
and dates/text sort correctly regardless of how the column formats them)
|
||||
and has an "Export CSV" button next to it that exports whatever's
|
||||
@@ -534,7 +537,9 @@ The page also shows the users, the files and the app updates waiting. Whether it
|
||||
|
||||
**Hetzner Cloud** (Infrastructure → Hetzner Cloud). Add a project's read-only API token and the app lists its servers with their status, this month's traffic against the quota, backups, volumes and snapshots, and roughly what it costs a month. It warns when a server that was running is **off**, when one has used **80% of its traffic** (critical at 100%), when **rescue mode** is left on (the next reboot would not come back up), and when **backups** are enabled but late. A server that is also one the app knows by its agent gets a Hetzner card on its own page. Nothing at Hetzner is ever changed. See INTEGRATIONS.md and docs/MONITORING.md.
|
||||
|
||||
**NetBox** (Network → NetBox). Add a NetBox integration (its address and a read-only token): a warning when **no background worker** is running (they are a separate container in the Docker image, and can be down while the pages load), and a list on the page of **the servers you run that have no address in NetBox**. That list is
|
||||
**Speedtest** (Monitoring → Speedtest). Add a Speedtest Tracker integration (its address and an API token with the *results:read* ability) and the app charts how fast the internet has been — download, upload and ping over up to 90 days — and, if you tell it what the line is sold at, warns when **the middle of the last three tests is under 60%** of it, and when **the tests keep failing**. One slow test is not an alert. The app never starts a test. On a status page the integration reads as the internet. See INTEGRATIONS.md and docs/MONITORING.md.
|
||||
|
||||
**NetBox** (Monitoring → NetBox). Add a NetBox integration (its address and a read-only token): a warning when **no background worker** is running (they are a separate container in the Docker image, and can be down while the pages load), and a list on the page of **the servers you run that have no address in NetBox**. That list is
|
||||
not an alert; documentation that is behind is not an outage. See INTEGRATIONS.md and docs/MONITORING.md.
|
||||
|
||||
**n8n** (Automation → n8n). Add an n8n integration (its address and an API key): a warning for each **workflow that is switched on and failed on its last run** — an automation that has quietly stopped — which clears when it next succeeds. The page lists the workflows with their last run and the failures of the last day. See
|
||||
@@ -641,7 +646,7 @@ unknown token and a wrong path are answered alike. They also appear on the dashb
|
||||
|
||||
**Coming up** (Operations → Coming up, and a card on the dashboard). Everything with a date ahead in one list, nearest first: secrets, domains and certificates that
|
||||
expire (including the ones endpoint checks see), Tailscale keys that are expiring, hardware warranties and end of support, planned and **recurring** maintenance, restore
|
||||
tests that are due (when a time limit is set), and — as one line — updates that have been waiting. What has already passed in the last 30 days is shown as past, under
|
||||
tests that are due (when a time limit is set), the day a **bill** falls (Costs), and — as one line — updates that have been waiting. What has already passed in the last 30 days is shown as past, under
|
||||
*Needs attention now*. Narrow it by kind, server and how far ahead (up to a year); the filters are in the address, so a view can be linked. A schedule that repeats weekly is one line (its next time) unless
|
||||
you ask for every one. An administrator can make a **calendar feed** (Settings → Share links → *A calendar feed*): an address for a phone's calendar to subscribe to, refreshed
|
||||
every few hours, with each day as an all-day event and maintenance with its start and end. A feed made with *kinds only* says only "A secret expires", with no names, so it is fine on a shared
|
||||
@@ -777,12 +782,14 @@ removed answers the same way, and making and removing links are in the audit log
|
||||
(without the secret). It is as private as the address: remove it when it isn't
|
||||
needed.
|
||||
|
||||
**Costs** (Records → Costs). What the homelab costs, in one place: the domains, VPN, licences and subscriptions you type in (an amount per month or per year, a currency, a kind, and optionally the day it is billed) and a Hetzner project's estimate, read by itself. Each currency has its own monthly and yearly total and a split by kind — none is converted into another. A day a bill falls on is an anchor: the next time it falls (the same day next month, or next year) is worked out and shows in **Coming up** as *Renewals*. Everyone signed in sees it; an administrator changes it.
|
||||
|
||||
**Status pages** are the other thing a share link can open: a page for family or housemates
|
||||
that answers "is the movie server up?" without a sign-in and without anything that isn't
|
||||
theirs to see. Pick **A status page** when making a link, then choose what is on it and what
|
||||
each thing is called ("Movies and TV", "Family photos"): each is a server (reporting, or not
|
||||
— judged by its own limits), an integration (its latest calls work, or don't) or an Uptime
|
||||
Kuma monitor. It says *Working*, *Not working*, *Being worked on* (under a maintenance
|
||||
Kuma monitor. It says *Working*, *Having trouble* (it answers, but has an alert open that nobody has silenced, snoozed or closed — a disk filling, a stuck queue, an internet line slower than it is sold at; the alert itself is never shown), *Not working*, *Being worked on* (under a maintenance
|
||||
window) or *Can't tell right now*, with the 30-day figure where one is known, a heading and
|
||||
an optional message ("Movies are being updated tonight"). The page follows the device's
|
||||
light or dark setting and looks again every 30 seconds. Whoever has the address is given only
|
||||
|
||||
Reference in new issue
Block a user