Probing the live Debian VPS turned up three mismatches between what it serves and what this config declares: - git.mgaction.town had no vhost at all. Gitea's web UI and HTTPS clones are public today; only its SSH side (the :2222 socat forward) had been ported, so a deploy would have taken the web side offline. - Audiobookshelf is served as abs.mgaction.town, not the longer audiobookshelf.mgaction.town this config used. The mobile app is configured with the short name. - The apex returns 200 from Caddy. Left unserved deliberately, so it now gets Caddy's default 404; noted in a comment so it doesn't look like an oversight next time. Gitea's ROOT_URL was http:// while Caddy terminates TLS for that name. Gitea builds absolute URLs from it, so clone buttons, redirects and webhooks were handing out downgraded links. Also record that defaultGateway6 is confirmed rather than assumed -- `ip -6 route show default` on the VPS gives "default via fe80::1 dev eth0 metric 1024 onlink". Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
homelab
Flake-based NixOS config. Hosts: jupiter (ZimaBlade, NAS + services),
neptun (netcup VPS: public reverse proxy, Authentik, headscale),
mercury (Raspberry Pi 3B+, DNS/DHCP), terra (desktop).
Structure
flake.nix # inputs + nixosConfigurations (jupiter, neptun, kexec, ...)
common.nix # shared base: user, ssh, nix, firewall, timezone
services/ # one reusable module per service, by category
media/ jellyfin, audiobookshelf, the *arrs, sabnzbd, seerr, ...
network/ caddy, samba, avahi, pihole, unbound
vpn/ tailscale, headscale (control server), headplane (its web UI)
identity/ authentik (OIDC provider, from the authentik-nix flake)
dev/ gitea
desktop/ hyprland
containers.nix # podman backend, shared across categories
hosts/
jupiter/ # ZimaBlade NAS
configuration.nix # host bits + imports common + the services it runs
disk-config.nix # disko: eMMC partitions
hardware-configuration.nix
secrets.nix # sops-nix wiring
vm.nix # VirtualBox test image (jupiter-vbox)
neptun/ # netcup public reverse proxy + tailnet node
configuration.nix disk-config.nix hardware-configuration.nix secrets.nix
secrets/ # age-encrypted sops files (jupiter.yaml, neptun.yaml)
scripts/ # deploy, edit_secrets
Hosts compose by importing common.nix + whichever services/* modules they
run. Each service module opens its own firewall ports.
Test in VirtualBox (no hardware needed)
nix build .#nixosConfigurations.jupiter-vbox.config.system.build.virtualBoxOVA
VBoxManage import result/*.ova --vsys 0 --vmname jupiter-vbox
VBoxManage startvm jupiter-vbox --type headless
Login darman / test. Forward ports with VBoxManage modifyvm ... --natpf1.
First install on the ZimaBlade — nixos-anywhere + disko
Wipes the OS disk and installs the flake over SSH. No USB needed if the box already runs Linux (ZimaOS) reachable by root SSH — nixos-anywhere kexecs into an installer, partitions via disko, installs.
⚠️ The OS disk in
disk-config.nixis WIPED. Setdeviceto the OS disk ONLY (by-id). Back up / physically identify the NAS data disk first — it must NOT appear in disko.lsblk -o NAME,SERIAL,SIZE,MODELto identify.
- Set the real OS disk id in
hosts/jupiter/disk-config.nix(ls -l /dev/disk/by-id), and the data-disk mount inconfiguration.nix. - Add your login SSH pubkey to
users.users.darman.openssh.authorizedKeys.keys. - Set the real samba password:
export SOPS_AGE_KEY_FILE=~/.config/sops/age/keys.txt nix shell nixpkgs#sops -c sops secrets/jupiter.yaml # edit, commit - Stage the pre-generated host key so sops can decrypt on boot #1
(private key lives off-repo in
~/.config/homelab/jupiter/):install -Dm600 ~/.config/homelab/jupiter/ssh_host_ed25519_key \ /tmp/extra/etc/ssh/ssh_host_ed25519_key install -Dm644 ~/.config/homelab/jupiter/ssh_host_ed25519_key.pub \ /tmp/extra/etc/ssh/ssh_host_ed25519_key.pub - Run from your laptop:
nix run github:nix-community/nixos-anywhere -- \ --flake .#jupiter \ --extra-files /tmp/extra \ --generate-hardware-config nixos-generate-config ./hosts/jupiter/hardware-configuration.nix \ --target-host root@<zimablade-ip>--extra-filesplants the host key before first boot (its age identity is already a recipient in.sops.yaml, so/run/secrets/samba_passworddecrypts on boot #1).--generate-hardware-configpulls the target's real kernel modules into the placeholder. Commit the result. Reboot into NixOS.
Manual alternative (USB ISO): boot installer, disko the disk, then
nixos-install --flake .#jupiter.
Deploy (the ./deploy wrapper)
All arguments mandatory — no default host, no default config.
./deploy kexec <host> # headless kexec into a RAM installer (RO-root box)
./deploy install <config> <host> # first install; wipes OS disk, ships host key
./deploy switch <config> <host> # rebuild + activate on a running host
./deploy boot|test <config> <host> # stage for next boot / activate without boot entry
<config> is a nixosConfigurations name (jupiter, neptun). Its pre-generated
SSH host key lives at ~/.config/homelab/<config>/ssh_host_ed25519_key.
Examples:
./deploy switch jupiter jupiter.sol
./deploy install neptun 159.195.64.117
Rollback: nixos-rebuild switch --rollback on the host, or pick a prior
generation at boot.
Adding a service
Copy the whoami block in oci-containers.containers, swap image/ports/volumes.
Native NixOS module exists for many apps (Nextcloud, Jellyfin, Grafana...) —
prefer services.<app> over a container when available. Add a caddy
virtualHosts block to expose it.
Notes
- Backend is Podman with
dockerCompat—dockerCLI works, no daemon. - Samba keeps its own password DB.
services.sambanever sets it; a systemd oneshot (samba-smbpasswd) provisions it. Host reads the password from/run/secrets/samba_password(sops-nix); the VM falls back to plaintext/etc/samba/smb-password. - Secrets:
secrets/jupiter.yamlis age-encrypted (safe to commit) to two recipients in.sops.yaml— the admin key (edit on laptop,~/.config/sops/age/keys.txt) and the jupiter host key (derived from its SSH host key viassh-to-age, decrypts at runtime). Private keys live off-repo and are gitignored. Rotate/add recipients withsops updatekeys. - Data disk: plain
fileSystems."/mnt/data"in configuration.nix — kept out of disko so it is never formatted. Reference byby-id/by-uuid. system.stateVersion=26.05, install-time schema. Do NOT bump on upgrades.- Terraform is not used: a single bare-metal box has no provider API. disko + nixos-anywhere cover provisioning natively.