Developer systems / reproducibility

A reproducible NixOS workstation.

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

Combine the configuration before activating it.

Pinned inputs feed the host, home, and secret modules. Checks run before the system changes.

Case study

A workstation as a dependency graph

01 / Problem

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.

02 / System

Keep the configuration in modules

A flake pins the inputs and brings together hosts, reusable modules, Home Manager state, and sops-nix secrets.

03 / Artifact

Configuration and recovery documentation

The repository contains host definitions, modules, the flake lock, the encrypted-secret policy, checks, and recovery documentation.

Configuration detail

From pinned inputs to activation

  1. Pin inputs

    Record the exact upstream revisions so the same source graph resolves consistently.

  2. Compose modules

    Keep machine-specific configuration separate from reusable system and user configuration.

  3. Decrypt at runtime

    Store ciphertext in Git. sops-nix materializes the secrets only on the target host.

  4. Check and activate

    Evaluate the flake and scan for leaks before switching atomically. Keep the prior generation available for recovery.

Evidence boundary

The running configuration, with secrets excluded.

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.