Homelab / Technical documentation
Read the claim at the strength of its evidence.
Dates, labels and source keys make historical work useful without turning an incomplete record into a current installation guide.
Jump to a section
Evidence labels
Scroll within the table to see all columns.
| Label | Meaning in these pages |
|---|---|
| Observed | Terminal output or explicit result described in the supplied reconstruction. Original raw transcripts were not independently available in this review. |
| Recovered report | Conversation summary or a local deployment report describes the action; attribution and date are retained. |
| User-described | A stated setup or intended presentation, without installation proof. |
| User-confirmed | An explicitly confirmed change or layout, with confirmation date. |
| Source-verified | Behavior inspected in local application code; not automatically the deployed behavior. |
| Export-inspected | Selected fields inspected in a dated local configuration/inventory export. This verifies the file, not a fresh running state. |
| Proposed | A design or procedure without confirmed execution. |
| Unresolved | No supported final outcome in the available evidence. |
Historical source keys S01–S19 refer to the supplied reconstruction reviewed on 8 November. They are compact provenance references, not links to private chats or raw terminal files. Local-source keys L01–L05 identify this review’s code/report evidence.
How to read configuration and commands
- Historical: a command or configuration associated with a dated record. Replaced parameters are identified. It was not rerun for publication.
- Illustrative: an authored diagnostic or sanitized fragment. Angle-bracket placeholders must be replaced; fragments are not complete deployment files.
- Source-verified: code inspected locally, with no claim it ran on the current server.
- Currently verified configuration: would require a fresh read of that configuration. No current server configuration is labeled this way in this review; current topology is owner-confirmed instead.
Read-only diagnostics can still reveal private information in their output. Inspect locally and redact before sharing. State-changing historical examples are explicitly identified.
S01 · Hardware discussions · July and October 2026
Recovered HP Slim identification and older ASUS hardware; current memory/version conflicts remain unasserted.
S02 · CasaOS and storage · May–June 2025, July 2026
Older /DATA layout, external storage and stopped-container preparation.
S03 · Linux AP · 7 November 2026
Reconstructed hostapd transcript: enabled/running, AP mode/channel and client association; later device-success confirmation.
S04 · Migration · 14–15 October 2026
Recovered appdata copy scope, directories, service startups and image mismatch.
S05 · Docker / VA-API terminal record · 1–2 November 2026
Described running inventory, selected bind mounts and QP23 segment output.
S06 · Storage recovery · 27 September 2026
Recovered USB/ext4 sequence, check exit status and service recovery.
S07 · Plex incident · 17 October 2026
Recovered containment/recovery and limited transcript process/image corroboration; unknown entry route.
S08 · GPU work · October–November 2026
Recovered PCI passthrough, guest driver/render node and namespace permissions.
S09 · Encoding / Tdarr · 31 October–7 November 2026
QSV failure, VA-API tests, later whole-file comparisons, cache ideas and scheduling request.
S10 · DNS · 23 October, 2 November 2026
Successful Sonarr lookup and separately validated daemon configuration.
S11 · Earlier Command Center · 19 October 2026
Frontend compilation followed by a failed build-stage data copy; deployment not established by that record.
S12 · Scanning · 31 October 2026
Recovered scanner/PDF/manual-consume/OCR workflow, supported by S05 inventory.
S13 · Playback · 3 November 2026
Reported client stall and user-confirmed Force Direct Play workaround.
S14 · Monitoring / recovery · July, October 2026
Recovery-agent proposal and its limited restart allowlist.
S15 · Portfolio topology · 5 November 2026
User-described layout, later reaffirmed by S19.
S16 · Remote access · 2025–2026
Mixed local/tunnel checks, configuration failures and unresolved external 502 results.
S17 · Encoding/storage context · 4–7 November 2026
I/O sample and conversion progress, without verified totals.
S18 · Documentation brief · November 2026
Publication scope, design continuity and privacy requirements.
S19 · Owner update · 8 November 2026
Completed ASUS Proxmox conversion and the current two-node guest placement.
L01 · Older Command Center source · inspected 8 November 2026
Dockerfile still copies build-stage /app/data; server/index.js is the older Express/JSON implementation.
L02 · Newer Command Center source · inspected 8 November 2026
server/app.ts, server/storage.ts, server/monitor.ts, server/discovery.ts and Dockerfile: Express API, JsonStore, server-side probes, explicit discovery, optional read-only Proxmox and runtime-directory creation.
L03 · Grade-watcher source · inspected 8 November 2026
dashboard.py, scheduler.py, user_store.py and grade_watcher.py: Flask, SQLite, browser/PDF worker and notifications. Runtime user data was excluded.
L04 · Newer deployment report · dated 7 November 2026
docs/HOMESERVER_DEPLOYMENT.md: reports healthy Command Center, login/CRUD and restart persistence; empty catalog and disconnected Proxmox. Not a fresh live test in this review.
L05 · Local deployment inventory · dated 7 November 2026, inspected 8 November
Selected mount fields confirm a shared host consume source for scanservjs and Paperless, a writable scanner-side consume mount, and a separate scanner output source. Private endpoints, identifiers and full exports remain unpublished.