Skip to content

docs(nas): snapshot task and backup pull done; port 22 stops being inert everywhere it was said (#484) - #563

Merged
Gerrrt merged 1 commit into
mainfrom
gerrrt/nas-snapshot-task-done
Sep 20, 2026
Merged

Gerrrt merged 1 commit into
mainfrom
gerrrt/nas-snapshot-task-done

Conversation

@Gerrrt

@Gerrrt Gerrrt commented Sep 20, 2026

Copy link
Copy Markdown
Owner

What changed

Documentation only. The three "not yet done" blocks in build-the-nas.md that the snapshot task and the backup pull owed become Done blocks with the evidence the checklist asked for, §4's status block stops saying the backed-up row is not yet true, and the five sentences across security.md, network.md, roadmap.md and the runbook that said port 22 is inert become past tense with the date — §6.2 step 9, in the one commit it asked for.

Why

The task was created and run on 2026-09-19 at 23:00 PDT, the first pull landed as 20260920T060234Z with jellyfin.db present and hashed on oracle, and make verify-backups re-read it beside the six observability sets. Everything the Done blocks state was read from smaug and morpheus today, not assumed: the dataset's ACL lines and frodo's inherited entry, the creation epoch of the snapshot against the script's parse of its name (equal), and the igc0.40 tripwire at 0 packets with the pull done. Refs #484.

Blast radius

None. Nothing on smaug, morpheus or this host changes.

  • No change to network segmentation or firewall rules
  • No new port published to a VLAN that could not already reach the service
  • No credential added outside secrets/*.sops.yaml

Verification

  • make lint and scripts/check_docs.py pass
  • Deployed to the lab and confirmed working — not applicable, documentation only
  • Docs updated

🤖 Generated with Claude Code

…2 stops being inert in every document that said so (#484)

§4.1 was created 2026-09-19 23:00 PDT and run once by hand; the pull read
its snapshot minutes later. The Done blocks record what the checklist asked
for: the ACL lines step 2 read off erebor/apps, frodo's inherited read entry,
the step 5 cross-check (zfs creation and the script's parse of the name both
1789884000, so the zone is right), the first set 20260920T060234Z with
jellyfin.db present and hashed on oracle, the timer installed, and the igc0.40
tripwire at 0 packets afterwards. §4's status block stops saying the backed-up
row is not yet true.

Step 9 of §6.2, in the same commit as it said: the five sentences that called
port 22 inert — security.md, network.md, roadmap.md, §0.5 and §2 — become
past tense with the date, and security.md now states the accepted residual
where the pull is described rather than deferring it to the runbook.

Refs #484.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant