Skip to content

docs: the NAS set is the third thing that leaves the monitoring host (#484) - #564

Merged
Gerrrt merged 1 commit into
mainfrom
gerrrt/nas-set-counted-everywhere
Sep 20, 2026
Merged

Gerrrt merged 1 commit into
mainfrom
gerrrt/nas-set-counted-everywhere

Conversation

@Gerrrt

@Gerrrt Gerrrt commented Sep 20, 2026

Copy link
Copy Markdown
Owner

What changed

Five sentences that enumerate what leaves the monitoring host, or what oracle holds, still counted two artefacts after #554 added a third. docs/observability.md, docs/architecture.md, docs/network.md and README.md now name the NAS set beside the firewall export and the volume sets, and stacks/media/README.md's published-ports table gains the row for the port-22 pull that §6.2 of the NAS runbook switches on.

Why

Found by a completeness check after #554 merged. Refs #484.

Blast radius

  • 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 validate passes
  • Docs updated — this is docs only

🤖 Generated with Claude Code

… and every list that counted two says so (#484)

#554 made `make backup-nas` copy Jellyfin's state to oracle in the same run
as the volume sets, and five sentences on main still counted two artefacts
leaving this host: observability.md's "Two outputs leave", oracle's row in
architecture.md and its bullet in network.md, the README's off-host
sentence, and the media README's published-ports table, which listed three
of the four rules and not the port-22 pull §6.2 turns on.

Refs #484.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@Gerrrt
Gerrrt merged commit 82d8293 into main Sep 20, 2026
3 checks passed
@Gerrrt
Gerrrt deleted the gerrrt/nas-set-counted-everywhere branch September 20, 2026 06:26
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