Enable docker-report (Trilium) sync and atticd alerts on vega #230
Labels
No labels
area:authentication
area:flake-utilities
area:performance
area:tbd
host:chaos
host:electra
host:fleet
host:lyra
host:nova
host:vega
investigation
phase:cutover
phase:deploy
phase:mcp
phase:module
phase:packaging
phase:prep
phase:validation
priority:high
priority:medium
project:attic-postgres-lyra-rollout
project:auto-update-reliability
project:auto-update-remediation
project:declarative-purity-cleanup
project:external-review
project:fleet-boundary-cleanup
project:host-facts-refactor
project:lyra-nixos-deploy
project:lyra-service-stack-migration
project:nebula-mesh-network
project:nixos-build-deployment-pipeline
project:security-hardening
project:service-stack-migration
project:vega-sillytavern-cutover
project:wiki-rebuild
repo:numtide/flake-utils
repo:numtide/nix-auth
repo:numtide/nixos-passthru-cache
repo:numtide/nix-relay
service:auto-update
service:mem0
service:nix
service:sillytavern
service:slskd
service:synthseek
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
nimmo/nixos-config#230
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
Vega currently lacks two service-coverage items that lyra already has:
/srv/stacksare not documented in Trilium; lyra already runs this.atticdis not in the ntfy service-failure monitor (nor was it on lyra yet).Scope
modules/services/docker-report.nixon vega so its/srv/stacksdocument under the shared Trilium tree (option a: shared ETAPI token + parent note + stacks dir).secrets/docker-report.yamland update the.sops.yamlcreation rule for that secret.atticdtoservices.serviceFailureMonitor.serviceson vega and lyra —atticd.nix(unlike most service modules, e.g. jellyfin/immich/tdarr) does not self-register./srv/services/docker-reporton vega (cloned fromnimmo/docker-report);config.jsonrenders from sops at activation (vega can now decrypt it).Completion criteria
nix flake checkgreen (all 6 hosts)secrets/docker-report.yaml(verified against the canonical.sops.yamlkey)nimmo:users 755,config.jsondeferred to sops)sudo nixos-rebuild test --flake .#vega(secret decrypts on vega; service + timer active)# TRILIUM METADATAinjected into/srv/stacks/*.yml)mainvia auto-updateRisk / blast radius
The first Trilium sync is a live write (creates/updates Trilium notes and injects headers into vega's compose files under
/srv/stacks). Vega is pull-only frommain, so none of this is live on vega until the associated PR merges. Vega's canary is a non-persistentnixos-rebuild testwith an auto-update hold, per AGENTS.md.