vix - Vic's Nix Environment

My infra built using my Dendritic libs.

Inputs are extracted from modules option flake-file.inputs and pinned via npins, then loaded using with-inputs.

Hosts are defined at modules/hosts.nix with their respective den.aspects at modules/hosts/.

My den configuration has two namespaces, vix (public) for stuff that is generic enough for others to re-use. And vic (private) for everything that has to do with my user.

build
switch

Currently only vic which is applied at all hosts.

• modules/community/vix/: reusable vix.* aspects. Others can use them.
• modules/vic/: my user profile. Groups: shell, vcs, edit, dev, sys.
• modules/hosts/: one file per host, plus a folder for bigger hosts.
• modules/diagrams/: generates the diagrams.

1. Create modules/hosts/<h>.nix with the host den.aspects. Copy nargun.nix as a start.
2. Add an entry in modules/hosts.nix, for example den.hosts.x86_64-linux.<h>.users.vic = { };.
3. Boot the target machine. Generate the hardware facts there: sudo nixos-facter -o modules/hosts/<h>/_nixos/facter.json Then set hardware.facter.reportPath to that file. See frodo.nix.
4. If you use disko, point the disk to /dev/disk/by-id/.... Do not use /dev/nvme0n1. Those names can change between boots.
5. Run build for the new host before you switch.

facter.json is a snapshot. It does not update itself.

Generate it again after you change RAM, disks, or the board:

sudo nixos-facter -o modules/hosts/<h>/_nixos/facter.json

Do not trust a build until the file is fresh.

Load shell.nix using direnv .envrc or manually nix-shell.

# .envrc
use nix

Other useful commands defined at Justfile

Historical points of this repo:

• Den without flakes current
• Den with flakes + flake-parts
• Dendritic flake-parts only
• blueprint
• flake-parts
• olf m1 flake with mk-darwin-system
• other with snowfall-lib lost