Skip to content

Sensitive tier: Homepage as the entry point to the estate #137

Closed

Description

@Gerrrt

Sub-issue of #102. Last of the nine — it is the one that only makes sense once there is something to link to.

What and why

Homepage by gethomepage GPL-3.0 Docker/Nodejs — awesome-selfhosted README.md:1699.

YAML-configured, so the dashboard lives in the repository rather than in a database — the same property ADR-0004 insisted on for Grafana ("No dashboard exists only in a database"). It also has widgets that read service APIs, so it can show real state rather than a wall of bookmarks.

Alternatives, both in the list: Glance (:1695, AGPL-3.0, also file-configured, lighter) and Dashy (:1694, MIT, richer UI, heavier). Any of the three satisfies the ADR; Homepage is the default here because its widget coverage for the services in this tier is the broadest.

The household angle

This is the one service on the sensitive tier with a non-technical audience, which makes it worth more than it looks. #124 is open because docs/ has no entry point for a successor operator — a landing page that says what exists and where it lives is a partial answer to the same problem for the people who live here, and it costs almost nothing.

Keep it honest about what it is: a directory, not a status page. Uptime lives in Grafana and in #91; a green tile on a homepage that is really just a hyperlink is worse than no tile.

What it needs

  • services.yaml, settings.yaml and widgets.yaml in the stack directory, mounted read-only, in the repository.
  • Any widget API tokens in secrets/*.sops.yaml — several widgets want read access to the service they display, and those are credentials.
  • Scope every token to read-only where the target supports it.
  • Decide whether it links to the observability stack on prometheus as well. It should; two dashboards with no link between them is how one of them gets forgotten.

Which VLAN this touches

🔴 99 — Winterfell (management)

Security review

  • Does not weaken the default-deny posture between VLANs — reached from Hicks under the existing 50→99; no new rule
  • Any new credential goes in secrets/*.sops.yaml — widget tokens count
  • Any new device is added to docs/network.md with an OUI-truncated MAC — n/a

Depends on

#129 (Caddy), the mini PC in #102, and enough of #131–#136 existing to be worth linking to. Related: #124.


Corrected 2026-09-20

"The mini PC in #102" → #404; the box is trinity, in hand. #124 closed 2026-09-04 — docs/runbooks/successor-handover.md is the successor's entry point now — so the household-angle paragraph's "#124 is open" is stale, though its point stands: this would be the entry point for the people who live here, which docs/ is not. Not authored; last in the tier's order by design, seq/8.

Activity

  1. added this to the Wave 1 — trinity milestone on Sep 11, 2026
  2. Gerrrt commented on Sep 29, 2026

    @Gerrrt
    OwnerAuthor

    Done. Homepage is live at https://home.matrix.elysium on trinity, deployed 2026-09-29 from main (#701, #717, #721, #725).

    What it is: a directory, not a status page. There are no status dots, and uptime stays in Grafana, which is linked from the page. Household comes first. Every other tile sits under its VLAN, in docs/network.md's order.

    Live numbers: eight tiles read real data, each with a read-only credential or none:

    • Immich and Paperless read their own APIs with scoped tokens.
    • Prometheus, the UPS, the firewall, the iLO and the NAS are read from Prometheus. It already scrapes them and needs no credential (Authenticate the Prometheus and Loki ingest ports #182).
    • Weather comes from Open-Meteo, which needs no key. The location is rounded to about 10 km.

    Measured after deploy: 458 photos, UPS at 100%, 970 firewall states, 109 W on the iLO, 17.8 TB free on the NAS, 58 °F. All 13 containers on the tier are healthy.

    Security review

    Not done here: a negative probe confirming each token can do nothing beyond reading statistics. The tokens were minted to that scope, following the steps in secrets/sensitive.example.yaml, but no one has checked it against the live services.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureA new capability or a changesensitivestacks/sensitive on trinity (VLAN 99)

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions