Repository navigation
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The runbook still presents a completed verification as outstanding and needs to include the September completion evidence while distinguishing it from the November local re-audit.
1 open issue
What changed in this PR
This documentation-only PR aligns smaug’s NAS and media-stack guidance with the recorded deployment and November audit. It changes no runtime configuration.
Changes:
- Adds golem’s NFS access and its security implications to the inbound-access documentation.
- Corrects stale rule counts, SMART guidance, switch-port references, and collector status.
- Documents pinned-commit deployment through
smaug-fetch.shand the existing SSH backup access.
| File | Description |
|---|---|
stacks/media/README.md |
Updates deployment guidance, inbound access, and NFS consumers. |
stacks/media/compose.yaml |
Corrects deployment instructions in the header comment only. |
docs/security.md |
Adds golem’s NFS trust and recovery limits; removes a stale rule count. |
docs/runbooks/build-the-nas.md |
Refreshes NAS procedures, hardware references, and completion notes. |
docs/architecture.md |
Points readers to the authoritative current inbound-rule count. |
Review effort: Balanced
Comment on lines
+1782
to
+1787
| > **Steps 1–3 done, read on `smaug` 2026-11-13; step 4 not yet read.** The | ||
| > cron job `homelab truenas-version (#616)` exists at 08:40 daily, and | ||
| > `truenas-version.prom` carries `truenas_version_info` for `25.10.7`, with | ||
| > `node_textfile_scrape_error` 0 on the exporter. The `check-versions` | ||
| > reading from the monitoring host still goes here, and | ||
| > [#616](https://github.com/Gerrrt/HomeLab/issues/616) closes on it. |
Owner
Author
There was a problem hiding this comment.
6.7 now records the 2026-09-23 completion (both smaug PASS lines, linked to #616 closing comment) and keeps the 2026-11-13 local re-read as a separate note that says check-versions was not re-run.
…the 2026-11-13 re-read
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

What changed
Docs only. Corrects the smaug text that a read-only audit on 2026-11-13 found stale or self-contradictory. Nothing on the running lab changes.
golem's2049pass (Allow NFS from golem to smaug, 2026-10-03) was missing from three of the places that list smaug's inbound rules. It is now inbuild-the-nas.md§0.5's table, in thestacks/mediaREADME's What is published table and consumer list, and insecurity.md's CasaBonita paragraph, with its residual.network.md's nine:security.mdsaid "six" and now names no count;architecture.mdsaid "the four inbound rules" and now points atnetwork.md.build-the-nas.md:check-versionsreading is still open.ether17on the CRS326 instead of port 15 onneo.curllines" now points at §6'ssmaug-fetch.shblock.stacks/mediacompose header and README:main".Why
A read-only audit of smaug on 2026-11-13 found these against the box: the cron jobs, the done sections, the switch port and the export to
golemall exist, and the docs said otherwise or left them out.network.mdis the authority for the rule count. Refs #616.Blast radius
None at runtime: prose and a YAML comment. A wrong sentence here would misdirect the next person running
build-the-nas.md.secrets/*.sops.yamlVerification
python3 scripts/check_docs.py:docs OK — 161 Prometheus + 21 Loki rules, 8 dashboards, 156 panels, 13 assertions./scripts/lint.sh: passed, but 14 checks were skipped and not run: yamllint, markdownlint-cli2, shellcheck, ruff ×2, actionlint, zizmor, packer ×2, tofu ×3, ansible-lint, editorconfig-checker. This checkout has no Docker daemon or pipx; CI runs them with--require-all.make validatewas not run:makeis not installed where this was authored.git diff --check: clean.make validatepassesDeployed to the lab and confirmed working (not applicable: docs only)
Docs updated (
docs/, service README, ordocs/roadmap.md)🤖 Generated with Claude Code