# Ticket: Service dashboard registration

## Metadata
- Type: Ticket
- Status: Done
- Project: Homelab Operations
- Created: 2026-06-06
- Updated: 2026-06-06
- Priority: Medium

## Goal

Design and implement a standard way for managed services/VMs/LXCs to appear in one or more operational dashboards.

## Why

The user wants created and managed systems to be visible and trackable. Dashboard registration is not currently implemented, so services can become invisible after creation.

## Scope

Included:
- Decide what dashboard(s) should exist or be used
- Define registration metadata: name, URL, host, owner, status, docs, backups, update policy
- Define manual process first, then automation path
- Link dashboard registration to the VM/LXC template standard

Not included:
- Choosing a final monitoring stack without research
- Implementing full metrics/alerting unless explicitly scoped later

## Acceptance Criteria

This ticket is done when:
- [x] Dashboard options are researched — Homepage selected over Dashy/Uptime Kuma/Grafana for config-as-code MVP.
- [x] A target approach is selected — Homepage in managed Proxmox LXC.
- [x] Service registration metadata is defined — initial `/opt/homepage/config/services.yaml` entries include name, URL, description, and monitor where useful.
- [x] At least one managed service is registered — initial dashboard includes Vaultwarden, SearXNG, Nextcloud, Nimrod, reverse proxy, Unbound, and Proxmox.
- [x] VM/LXC creation checklist includes dashboard registration

## Questions

- Should the first dashboard be simple markdown, Homepage, Dashy, Grafana, Uptime Kuma, Nextcloud Collectives, or another tool?
- Should dashboard data be generated from `infra/proxmox-registry.yaml`?
- Should this include health checks/uptime monitoring now or later?
- User requirement: dashboard must be easily administered by Nimrod, ideally file/config driven and not requiring web GUI configuration.

## Plan / Next Actions

- [x] Research simple homelab dashboard options
- [x] Decide MVP dashboard target
All ACs satisfied.

## Notes

- This ticket exists because dashboard registration is desired but not yet implemented.
- 2026-06-07: User explicitly requested a dashboard that Nimrod can administer easily without relying on a web GUI for configuration, and all relevant services should be registered.
- 2026-06-07: Homepage MVP deployed as CT 107 `homepage` at `192.168.0.241`, proxied as `dashboard.dropcutstud.io` through CT 105 with internal DNS record in CT 106 Unbound. Docker socket is intentionally not mounted. Runbook: `runbooks/homepage-dashboard.md`.
- 2026-06-07: User later preferred Homarr over Dashy. Fresh Homarr deployed as CT 111 `homarr` at `192.168.0.213:7575`, proxied as `homarr.dropcutstud.io`. Admin: deeso / Test1234!. All 14 services registered in 3 wrapper sections with weather, clock, and SearXNG search widgets. Old Homarr (CT 100) on proxtop destroyed. Dashy kept as legacy fallback. LE certs issued for homarr, ha, nc.