Sources and documentation maintenance
This repository is the maintained, public view of this installation. The source register below explains where its dated baseline came from. Public sources are linked; private repositories and the internal roadmap are named without links, so this site remains useful without a Forgejo account. The old wiki is historical context, not the place for new instance updates.
| Source | What it established | Access / caveat |
|---|---|---|
| Homelab/Documentation | Public architecture, status and procedures for this instance | Public; dated claims still need their own evidence. |
| Final Architecture, revision viewed 2026-09-24 | Node and ingress boundaries, DNS decision, VIPs, legacy edge | Contains older conceptual and unresolved wording; use later owner evidence where it conflicts. |
| Owner version confirmation, 2026-10-14 | Installed Core v1.13.1 and newly installed operator CLI v0.39.0 | Owner-reported current versions; no fresh health audit or Actions tool upgrade. See platform versions. |
| UDS Core readiness | RKE2/Core/MetalLB/CSI baseline | Historical prerequisite gate, not a current health check. |
| Homelab Operations Status | Actual, GitchAlerts, runner and managed-credential acceptance | Dated owner reports and CI runs; individual negative/restore tests remain separate. |
| Application migration plan | Placement, hostnames, TrueNAS-retained services and handoff | Planning inventory is not the live NPM allowlist. |
| Homelab/platform | Shared deployable configuration and detailed platform runbooks | Private; some component docs contain historical preparation sections. |
| Homelab/workflows | Reusable security, artifact and deployment controls | Public; callers pin releases, which may differ from main. |
| Homelab/actual-budget, Homelab/GitchAlerts, Homelab/Comfy-UI | App-specific source, runbooks and acceptance | Private; each app has a separate deployment state. |
| Homelab/base-images | OCI base definitions and manual publication flow | Private; a build/scan result is not a published registry digest. |
| Homelab Roadmap | Cross-repository planning view | Internal project board; the owning issue and live verification determine completion. |
Publishing and maintenance
- Update the relevant page here when instance topology, versions, decisions, operational status or cross-repository procedure changes. Leave the wiki as generic research and historical background. If a detailed component runbook also changes, update its owning repository and link to it when public; otherwise cite its repository and path without a link.
- Record the observation date, reporter or CI run, exact state (planned, prepared, tested, deployed), and limits of the evidence. A manifest merge or dry run does not prove a live rollout. Reconcile stale text instead of accumulating contradictory “current” sections. The owner clarified on 2026-10-15 that inaccurate or stale documentation blocks publication in this repository: passing checks and source approval do not establish factual accuracy. Align related present-tense status statements before merging; retain historical records with their original dates and limits.
- For service migration or DNS/routing changes, include previous state, intended cutover, internal/external validation and rollback. Do not claim data recovery from a route rollback.
- Inspect the public diff for passwords, access tokens, private keys, kubeconfigs, unseal shares, real Secret values, credential-bearing URLs, copied logs and screenshots. A secret name or non-secret contract may be documented, but never its value. Gitignore is not a security boundary.
- Run the repository's documentation link/build checks and review the rendered pages. Track implementation in the owning repository issue and keep the Roadmap current when work changes state.
The public roadmap snapshot is a dated summary of the private board. Update its columns, counts and active cards together when publishing a new snapshot; do not present it as a live feed.
When a source is private, give its repository name and issue or run number as a reference, but do not link to a page public readers cannot open. Explain the decision and evidence limit here without copying credentials or operational payloads.