One Nix flake for every machine I use: NixOS hosts, macOS through nix-darwin, and plain Arch, Gentoo and Proxmox hosts that only run standalone home-manager. System configuration and user dotfiles live in the same repo, and each host deploys its own part.
| Path | What it is |
|---|---|
nixos/ |
NixOS system modules. Per-host modules are under nixos/<host>/ and services under nixos/services/ |
darwin/ |
nix-darwin system config for macOS |
home-manager/ |
User environment. home-manager/home.nix is the entry point, and every host shares it |
overlays/, pkgs/, lib/ |
Package overrides, custom packages and flake helpers. lib/helpers.nix builds the configurations, and lib/caches.nix lists the LAN caches |
secrets/ |
sops-encrypted secrets |
shell/ |
Dev shells: nix develop .#hm, .#rust, .#kernel (x86_64-linux only) |
yazi/, zellij/, wezterm/, tmux/ |
App configs, symlinked into place by home-manager |
Every host runs home-manager standalone for the user configuration, so
nixos-rebuild and darwin-rebuild only manage the system side.
darwin/default.nix does not import the home-manager darwin module, because
the same dotfiles and launchd agents would otherwise be managed twice. A NixOS
or macOS host therefore takes two commands, and a plain Linux host takes only
the second one. The deploy-rs targets below keep the system and user
configurations separate in the same way.
sudo nixos-rebuild switch --flake .#vm-nix # or wsl, wsl-mini, work-laptop
home-manager switch --flake .#chin39@vm-nixdarwin-rebuild switch --flake .#macos
home-manager switch --flake .#chin39@macoshome-manager switch --flake .#chin39@archlinuxdeploy-rs deploys the NixOS configuration on aliyun, nixos-ci, nixos-lxc and
media-lxc, and standalone Home Manager on nixos-ci, nixos-lxc,
vm-nix, media-lxc, proxmox and aliyun. Run it from an x86_64 Linux
checkout, such as vm-nix. Most targets need SSH key access as chin39,
trusted host keys, and passwordless sudo. aliyun connects as root so its
system profile can create chin39 before Home Manager activation.
The nix run .#deploy-rs-ci entry point sends builds for every target, including
its automatic checks, to nixos-ci (192.168.0.230). Cached outputs can still be
downloaded directly. It allows one remote build at a time, using CI's Nix
configuration for parallelism within that build, and disables local builds for
those commands. If an uncached build needs CI while it is unavailable,
deployment fails before activation.
The local Nix daemon must be able to read your unencrypted
$HOME/.ssh/id_ed25519, and that key must authenticate as chin39 on CI. The
builder's public host key is pinned in pkgs/default.nix.
Leave deploy-rs's --remote-build option unset, because it makes the
deployment target the builder. Other Nix commands keep their usual build
settings. These settings take effect only after nix run has prepared the CLI
and its launcher.
| Target | Configuration |
|---|---|
aliyun.system |
nixosConfigurations.aliyun |
aliyun.home |
homeConfigurations."chin39@aliyun" |
nixos-ci.system |
nixosConfigurations.nixos-ci |
nixos-ci.home |
homeConfigurations."chin39@nixos-ci" |
nixos-lxc.system |
nixosConfigurations.nixos-lxc |
nixos-lxc.home |
homeConfigurations."chin39@nixos-lxc" |
media-lxc.system |
nixosConfigurations.media-lxc |
media-lxc.home |
homeConfigurations."chin39@media-lxc" |
vm-nix.home |
homeConfigurations."chin39@vm-nix" |
proxmox.home |
homeConfigurations."chin39@proxmox" |
Before the first activation, record the current generation and keep a console recovery path available. The previous native generation lacks deploy-rs's rollback script, so the first deployment may require manual recovery. Once a known working deploy-rs generation is installed, later deployments can recover to it automatically.
Check the configuration and preview the changes for the chosen target:
nix run .#deploy-rs-ci -- --dry-activate .#nixos-ci.systemActivate the chosen target with its explicit profile:
nix run .#deploy-rs-ci -- .#nixos-ci.system
nix run .#deploy-rs-ci -- .#nixos-lxc.system
nix run .#deploy-rs-ci -- .#vm-nix.homeRun one activation per target at a time, and coordinate with anyone else
working on that target. Once a host uses these profiles, activate it with
deploy-rs from then on. nixos-rebuild switch replaces the NixOS rollback
wrapper, and home-manager switch advances the native generation without
updating the deploy-rs wrapper. If you use either native command for recovery,
deploy once more with deploy-rs before relying on automatic rollback again.
deploy-rs confirms a deployment only by checking that SSH still connects, so check the target's services yourself afterwards.
shell/home-manager.nix provides a dev shell with the matching version:
nix develop .#hm| System configuration | Machine |
|---|---|
nixosConfigurations.aliyun |
Small Alibaba Cloud server |
nixosConfigurations.nixos-ci |
Proxmox LXC that refreshes flake.lock and prebuilds the cache (see below) |
nixosConfigurations.nixos-lxc |
Proxmox LXC for coding agents |
nixosConfigurations.media-lxc |
Proxmox LXC that runs the home services |
nixosConfigurations.vm-nix |
x86_64-linux server |
nixosConfigurations.wsl |
WSL2 with NVIDIA GPU |
nixosConfigurations.wsl-mini |
WSL2 with AMD GPU |
nixosConfigurations.work-laptop |
ThinkPad T14p Gen 2 with the niri desktop and the disk layout in nixos/t14p-gen2/disko.nix |
darwinConfigurations.macos |
Apple Silicon macOS |
All user configurations (homeConfigurations) share home-manager/home.nix,
and flags in flake.nix (isServer, isPublic, noGUI, smallNode,
localCaches) shape each one. Optional pieces such as restic, syncthing or
atuin sync are turned on per host through features. lib/helpers.nix lists
the valid feature names and rejects unknown ones. proxy and gitProxy set the
shell and git proxies.
For a small server, set smallNode on both its system and user configurations.
The user configurations are:
chin39@aliyun, chin39@macos, chin39@desktop, chin39@vm-nix, chin39@wsl,
chin39@wsl-mini, chin39@work, chin39@vm-work, chin39@archlinux,
chin39@arch-lxc, chin39@arch-vm, chin39@proxmox, chin39@nixos-lxc,
chin39@media-lxc, chin39@gentoo-server, chin39@vm-gentoo, ruowen@ringo
The ThinkPad pairs nixosConfigurations.work-laptop with
homeConfigurations."chin39@work", and nixos/services/shell-config-updater.nix
prebuilds exactly those two outputs for it.
work-laptop uses disko, and the disk in the config is a placeholder. Pass the
real device at install time (see nixos/t14p-gen2/disko.nix):
disko-install --flake .#work-laptop --disk main /dev/disk/by-id/nvme-...Nothing reads the placeholder after installation, because every generated
mount goes through /dev/disk/by-partlabel/* or /dev/mapper/cryptroot.
Secrets are encrypted with sops and age. The age key lives at
~/.config/sops/age/keys.txt and must have no password, because hosts decrypt
it during activation with nobody there to type one
(home-manager/programs/sops.nix).
- Each machine has its own age key in that file.
.sops.yamlmakes a machine a recipient only of the files it reads. The admin key is a recipient of every file and is kept off the machines. - Home-manager reads
secrets/common.yaml. Hosts flaggedisPublicreadsecrets/public/hosts.yamlinstead. System secrets for one host live insecrets/hosts/<host>.yaml. Files for a single service, such assecrets/xray.conforsecrets/hermes.env, are declared next to the service that reads them.secrets/archive.yamlholds values no host reads. - Edit a file on the admin machine with the admin key loaded, for example
sops secrets/common.yaml. After adding a machine's key to.sops.yaml, runsops updatekeyson each file it should read.
flake.nix sets extra-substituters and extra-trusted-public-keys. It uses
the appending extra-* form because the replacing keys would overwrite the
settings in each host's nix.conf. Besides chinrw.cachix.org and the USTC
mirror, a host can use LAN caches by naming them in localCaches. An unknown
name fails the build and prints the known ones, which are listed in
lib/caches.nix.
Every eight hours nixos-ci runs nixos/services/shell-config-updater.nix. It
clones this repo and runs nix flake update. It builds the deployment CLI,
checks and profiles, along with the additional Linux system and home outputs,
and archives the flake's input sources. It retains and uploads these paths to
Cachix before pushing main, so other machines can fetch both deployment
outputs and evaluation sources from the caches instead of building or fetching
upstream sources.
nix fmt # nixfmt-tree, the flake's formatter
nix develop .#rust # Rust dev shell
git submodule update --init --recursive # tmux, qemu-script, yazi pluginsHome Manager writes the dsh profile manifests and default preferences. Web
preferences remain writable: activation adds missing defaults and preserves
existing settings and locally added bundles. To restore the saved defaults for
a setting, remove its row from ~/.dsh/profiles/web/cordis.patch.yml before the
next activation.
Plugin installation stays explicit. After the first activation or a change to the declared dependencies, install the packages for each profile:
dsh plugin --profile web install
dsh plugin --profile headless installIf the host runs the Web user service, restart it after installing packages:
systemctl --user restart dsh-webThe live shell config is generated from home-manager/programs/zsh/ on every
host:
~/.config/zsh/.zshrc(programs.zsh.dotDirmoves zsh's dot dir here, so a hand-written~/.zshrcis never read)~/.config/zsh/plugins/powerlevel10k-config/p10k.zsh
Do not symlink or edit these by hand. Do not rely on ~/.p10k.zsh either,
because nothing on these hosts sources it. The p10k theme only sources its own
internal/p10k.zsh, and ~/.p10k.zsh is just the path p10k configure writes
to.
The zshrc and p10k.zsh files at the repository root are a matched pair kept
for a machine with no Nix at all (see the legacy section below). They have
drifted from the home-manager copies, and editing them changes nothing on any
host in this flake. That includes the Arch, Gentoo and Proxmox hosts, which
already get zsh from standalone home-manager.
This section only applies to a host that runs neither NixOS, nix-darwin nor
home-manager. Link the two files into place. zshrc sources ~/.p10k.zsh
itself.
ln -s $PWD/zshrc ~/.zshrc
ln -s $PWD/p10k.zsh ~/.p10k.zshgit pull --recurse-submodulessh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"git clone --depth=1 https://github.com/romkatv/powerlevel10k.git ${ZSH_CUSTOM:-$HOME/.oh-my-zsh/custom}/themes/powerlevel10k
git clone https://github.com/zsh-users/zsh-autosuggestions ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-autosuggestions
git clone https://github.com/zsh-users/zsh-syntax-highlighting.git ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-syntax-highlighting
git clone https://github.com/Aloxaf/fzf-tab ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/fzf-tab
git clone https://github.com/Pilaton/OhMyZsh-full-autoupdate.git ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/ohmyzsh-full-autoupdatecargo install exa atuin tealdeer du-dust fd-find ripgrep bat zoxide topgrade bandwhich
pacman -Sy exa atuin tealdeer dust fd ripgrep bat zoxide bandwhich- zsh-completions.
- fzf-tab: clone it with
git clone https://github.com/Aloxaf/fzf-tab, then addfzf-tabto the plugin list. - zsh-autocomplete is an alternative that this setup does not use.