Update README: all planned modules and integrations are now built

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
bobbanandClaude Sonnet 5 committed 2026-09-15 00:35:50 +02:00
1 parent a83a4b3b11
commit afc920e96e
1 file changed
+21 -15
+21 -15
View File
@@ -11,7 +11,7 @@ Authentik (OIDC), with local admin/operator/viewer roles.
## Status ## Status
Built so far: All modules from the original plan are built:
- Monorepo scaffold, Tabler-themed app shell/navigation - Monorepo scaffold, Tabler-themed app shell/navigation
- Authentik OIDC login, roles (first user to sign in becomes admin), audit log - Authentik OIDC login, roles (first user to sign in becomes admin), audit log
@@ -24,29 +24,35 @@ Built so far:
via a lightweight push agent (`agent/linux/`), plus manual entries for via a lightweight push agent (`agent/linux/`), plus manual entries for
things an agent can't see (Docker jobs, backups) things an agent can't see (Docker jobs, backups)
- **Integrations → Tailscale** — device list with online/authorized status, - **Integrations → Tailscale** — device list with online/authorized status,
and authorize/deauthorize/remove actions; a live device-count widget on and authorize/deauthorize/remove actions; a live device-count widget.
the Dashboard.
- **Integrations → Gitea** — repo list with each repo's last CI run status, - **Integrations → Gitea** — repo list with each repo's last CI run status,
and re-running just the failed jobs in a run; a live repo-count widget and re-running just the failed jobs in a run; a live repo-count widget
(with a failing-build warning) on the Dashboard. (with a failing-build warning).
- **Integrations → Dockhand** — container status across every Docker host - **Integrations → Dockhand** — container status across every Docker host
Dockhand manages (one credential covers all of them), with Dockhand manages (one credential covers all of them), with
start/stop/restart actions; a live running/total widget on the Dashboard. start/stop/restart actions; a live running/total widget.
- **Integrations → Semaphore** — Ansible run status per template across - **Integrations → Semaphore** — Ansible run status per template across
every project, with a "Run" action to trigger a template; a live every project, with a "Run" action to trigger a template; a live
template-count widget (with a last-failed warning) on the Dashboard. template-count widget (with a last-failed warning).
- **Integrations → Proxmox** — VM/LXC status across every node in the - **Integrations → Proxmox** — VM/LXC status across every node in the
cluster, with start/stop/restart actions; a live running/total widget on cluster, with start/stop/restart actions; a live running/total widget.
the Dashboard. Supports self-signed certificates (common in homelab Supports self-signed certificates (common in homelab Proxmox setups).
Proxmox setups). - **Integrations → Synology** — volume and disk health (read-only by
design). Supports self-signed certificates.
All five integrations follow the same config-in-UI + encrypted-credentials All six integrations follow the same config-in-UI + encrypted-credentials
pattern as DNS providers, so the remaining one slots into the same pattern, added through **Integrations → Manage integrations**.
"Add integration" form once built.
Not yet built (see `.claude/plans` for the full delivery plan): **What's been verified for real** vs. **what still needs your network**:
Authentik login and Gitea were both tested against the user's actual live
- Remaining live integration: Synology services. Tailscale, Dockhand, Semaphore, Proxmox, and Synology were built
against each service's real published API spec/source (not guesswork) and
verified with scripted HTTP tests against a bogus/unreachable config, since
those instances are LAN-only and not reachable from where this was built —
their route wiring, validation, and role gating are confirmed correct, but
real data and the write actions (start/stop/restart, trigger-a-run) haven't
been exercised against the user's actual homelab yet. Worth going through
each one after deploying, per integration.
## Requirements ## Requirements