4 Commits

Include renames

Author	SHA1	Message	Date
beatzaplentyandClaude Sonnet 5	532dc03cfa	Add tailscale-exit-node build type across all three platforms ... New build type dedicated to Tailscale exit-node capability, wired up for linode/proxmox/lxc like every other build type (the lxc variant is the one actually intended for deployment). Kept separate from the "server" host rather than bundling exit-node capability onto it. Trimmed modules/tailscale/exit-node.nix down to pure exit-node behavior: dropped the old --advertise-routes=${vars.lanCidr} bundling (meaningless for a Linode-hosted VPS with no path to the LAN), and switched extraUpFlags -> extraSetFlags. Confirmed against nixpkgs' tailscale.nix that extraUpFlags is only applied by tailscaled-autoconnect, which itself only runs when services.tailscale.authKeyFile is set -- nothing in this repo sets one, so the old flags would never have actually been applied. extraSetFlags runs unconditionally via tailscaled-set on every boot, so --advertise-exit-node self-reapplies once the operator has done the one-time manual `tailscale up` auth. Verified: all three new targets eval cleanly, nixpkgs-fmt/statix clean, and a dry-run build of lxc-tailscale-exit-node's tarball resolves its full closure including tailscaled-set.service. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01La55Nsss8jZ7ZuzUV9mfot	2026-07-20 13:38:39 +10:00
beatzaplentyandClaude Sonnet 5	9bfd804f7a	Resolve all statix and nixpkgs-fmt warnings repo-wide ... Zero W20 (repeated attribute keys), W10 (empty { ... }: variadic pattern, use _: instead), and W04 (a = x.a instead of inherit) warnings remain anywhere in the tree, and nixpkgs-fmt --check is clean on all 46 .nix files. Repeated-key merges go as deep as statix actually flags per file (e.g. boot.loader.* nested under boot.loader = { ... } once the outer boot.* merge exposed it as its own repeat) — every merge is a pure attribute-path restructuring with no value changes, verified by comparing config.system.build.toplevel.drvPath before/after for a representative host per changed module plus a full 19-host + 4-package eval sweep. One indentation slip caught and fixed during this pass: nesting modules/installer/common.nix's environment.etc."auto-install.sh".text under an environment = { ... } block initially normalized the script's shebang/set line indentation, which actually changes the rendered file (Nix's '' string dedent treats it as real content, not cosmetic whitespace) — reproduced the original's exact indentation and reverified the rendered script is byte-identical to before. modules/services/zfs/auto-mount-volumes.nix picked up formatting too; worth noting it isn't imported by anything in this flake at all. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01La55Nsss8jZ7ZuzUV9mfot	2026-07-20 03:47:42 +10:00
beatzaplentyandClaude Sonnet 5	6dcbae5659	Centralize shared values into variables.nix ... One file (variables.nix) holding every value that was previously hardcoded and repeated across modules: LAN domain/CIDR, home/tailnet domains, cross-host references (nix-cache substituter hostname, NFS server hostname, remote-builder user), PXE/PBS IPs, timezone, and the primary username. Wired in via flake.nix's specialArgs (and home-manager's extraSpecialArgs for the two home.nix files), so any module picks it up by just adding `vars` to its function arguments — no explicit import needed. Two hosts (nix-cache, server) now derive their own networking.hostName from the same variable other hosts use to reach them, so there's exactly one place to change either identifier. Purely mechanical: every substituted value matches what was already there, confirmed by identical toplevel .drv paths for all 17 targets before and after. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-19 14:51:37 +10:00
beatzaplenty	28ae709100	updated module directory structure	2026-07-13 00:56:19 +10:00