4.6 KiB
4.6 KiB
hosts/
One NixOS configuration file per managed machine, plus hardware configs and host-specific scripts.
Structure
hosts/
├── <hostname>.nix # Host configuration (packages, services, options)
├── <hostname>.hardware-configuration.nix # Generated by nixos-generate-config — DO NOT EDIT
├── <hostname>.disko.nix # Optional: declarative disk layout for `skyg remote install` (nixos-anywhere).
│ # Only present for hosts installed/reinstalled this way (currently: hl-fws1)
└── scripts/
├── fwbook/ # fwbook-specific shell scripts
│ ├── functions.sh # ZSH functions sourced at shell startup
│ └── functions.nu # NuShell helpers (k8s namespace/secret listing, secret decoding)
├── fw1/
│ └── gs.sh # gamescope/Steam launch wrapper (VRR, HDR, mangoapp overlay)
└── hl-minipc1/
└── buzz-manage.sh # Buzz stack management CLI (wired as `buzz-manage`)
Managed Hosts
| File | Host | Role |
|---|---|---|
fwbook.nix |
fwbook | Framework 13 AMD — personal laptop / daily driver |
hl-fwdesk.nix |
hl-fwdesk | Framework Desktop AI Max 300 — AI workstation |
hl-fws1.nix |
hl-fws1 | Framework 11th Intel — K3s server node |
hl-bigbox1.nix |
hl-bigbox1 | AI/compute server (NVIDIA + AMD) |
hl-bigbox2.nix |
hl-bigbox2 | NFS storage server |
hl-minipc1.nix |
hl-minipc1 | Core infra: Gitea, nix-serve, registry, Buzz (docker, buzz-manage CLI) |
hl-minipc2.nix |
hl-minipc2 | Container/media server |
hl-minipc3.nix |
hl-minipc3 | K3s worker node |
hl-pi1.nix |
hl-pi1 | Raspberry Pi CM4 (aarch64) — headless server, SSH only. Also buildable as a bootable SD image via the hl-pi1-sd-image nixosConfiguration (skyg build-pi-sd-image) |
hl-pi2.nix |
hl-pi2 | Raspberry Pi 4 (aarch64) — headless server, SSH only. Also buildable as a bootable SD image via the hl-pi2-sd-image nixosConfiguration |
hl-terra1.nix |
hl-terra1 | NFS storage + Jellyfin backup |
iso.nix |
iso | Bootable NixOS installer image |
Rules
- Do not add
imports = [...]to host files — module composition happens inflake.nixviamodules/main.nix - Do not edit
*.hardware-configuration.nix— these are generated and will be overwritten - Hosts with a
<hostname>.disko.nixown theirfileSystemsvia disko; if a generatedhardware-configuration.nixstill contains its ownfileSystemsstanzas for the same host, that's a conflict the machine's owner needs to resolve by hand (regenerating or trimming it) — not something to script around - Host-specific packages and one-off settings belong here; anything reused across hosts belongs in
modules/ - See
docs/hosts/README.mdfor full per-host service/port/package reference