Manual setup drifts
Manual setup drifts over time. Installation steps become things people remember rather than record, and credentials are difficult to audit or reproduce safely.
Developer systems / reproducibility
The workstation setup lives in reviewed source, with pinned dependencies, composable host and user modules, encrypted secrets, automated checks, and atomic activation.
Interactive configuration graph
Pinned inputs feed the host, home, and secret modules. Checks run before the system changes.
Case study
Manual setup drifts over time. Installation steps become things people remember rather than record, and credentials are difficult to audit or reproduce safely.
A flake pins the inputs and brings together hosts, reusable modules, Home Manager state, and sops-nix secrets.
The repository contains host definitions, modules, the flake lock, the encrypted-secret policy, checks, and recovery documentation.
Configuration detail
Record the exact upstream revisions so the same source graph resolves consistently.
Keep machine-specific configuration separate from reusable system and user configuration.
Store ciphertext in Git. sops-nix materializes the secrets only on the target host.
Evaluate the flake and scan for leaks before switching atomically. Keep the prior generation available for recovery.
Evidence boundary
The public tree shows the structure of the running configuration, including pinning, module boundaries, and encrypted-secret wiring. Host-specific plaintext and credentials are intentionally absent.