- Nix 100%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
|
||
| .forgejo/workflows | ||
| hosts/ai-coding-box | ||
| installer | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| AGENTS.md | ||
| ai-coding-box-devbox.json | ||
| flake.lock | ||
| flake.nix | ||
| global-AGENTS.md | ||
| INSTALL.md | ||
| README.md | ||
| SETUP.md | ||
| tailscale-policy.hujson | ||
ai-coding-box
NixOS configuration for the Intel NUC5i5RHY coding station (headless, Tailscale-SSH-only, isolated VLAN) plus the custom installer ISO that provisions it.
- Install/reinstall: see INSTALL.md
- Post-install verification: SETUP.md §6–7
Updating the box
All changes flow through this repo — edit hosts/ai-coding-box/ (or
ai-coding-box-devbox.json for agent tooling), merge via PR, then on the box.
All repos live in ~/wip on both machines — on the box the clone is at
~/wip/ai-coding-box:
cd ~/wip/ai-coding-box
git pull
sudo nixos-rebuild switch --flake .#ai-coding-box
Never rebuild from /etc/nixos — the configuration.nix there is an unused
leftover from nixos-generate-config and does not describe this system.
Latest package versions — bump the flake lock, then rebuild:
cd ~/wip/ai-coding-box
git pull
nix flake update
sudo nixos-rebuild switch --flake .#ai-coding-box
git add flake.lock && git commit -m ":arrow_up: chore: bump flake lock"
git push forge-pi <branch> # via PR, as usual
Agent toolchain (ai-coding-box-devbox.json): devbox update in ~, then
commit the updated devbox.lock via PR.
Next NixOS release (e.g. 26.11) — repoint the input at the new channel, update the lock, rebuild:
- In
flake.nix, changenixpkgs.urlfromgithub:NixOS/nixpkgs/nixos-26.05togithub:NixOS/nixpkgs/nixos-26.11. nix flake update nixpkgssudo nixos-rebuild switch --flake .#ai-coding-box
Leave system.stateVersion in hosts/ai-coding-box/default.nix at "26.05" —
it is a migration marker for state layout, not the release the system tracks.
Read the NixOS release notes and the manual's upgrading section before the
rebuild, and keep the old generation around until you have verified the new
one (the previous generation remains bootable from the systemd-boot menu).