3 Commits

Include renames

Author	SHA1	Message	Date
beatzaplentyandClaude Sonnet 5	a5990ccf7d	Build Proxmox images directly on the node instead of transferring them ... create-proxmox-resource.sh no longer builds locally and scp's a multi-gigabyte image over -- it now clones/pulls this repo onto the Proxmox node itself (bootstrapping build tooling via the existing codex-setup.sh on first use) and runs the nix build / disko image script there, staging the result straight into the node's own import directory. host-keys/ (gitignored) is copied over separately since a git pull doesn't carry it. --image still uploads an explicit local file for the case where you don't want a build at all. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-20 13:29:45 +00:00
beatzaplentyandClaude Sonnet 5	bd8d93d890	Add sync-host-keys.sh and create-proxmox-resource.sh ... sync-host-keys.sh: generates/registers SSH host keys and their .sops.yaml/secrets/*.yaml recipients for flake targets, idempotently. --all, <target>, --remove, --regenerate-all-keys, all with --dry-run (verified zero-side-effect via a sandboxed git-status check across every mode). Only ever touches anchors with a corresponding host-keys/ file -- &admin and any hand-registered real-host anchor are never listed, removed, or regenerated. Supersedes running prepare-host-key.sh one host at a time for any target that already has a flake entry. create-proxmox-resource.sh: builds a lxc-*/proxmox-* target's tarball/disk image and creates it on a real Proxmox node, or reconfigures an existing resource's cores/memory/disk (--modify, always requires typing the VMID back to confirm). Refuses to create a new resource for a VMID that already exists, and refuses to duplicate a host identity that already has a real deployment elsewhere (variables.nix's new deployedTargets, checked by hostName so it also catches cross-platform duplicates) unless --allow-duplicate-host is passed. --dry-run throughout. scripts/env.sh centralizes the Proxmox connection config both scripts (and future ones) share. Also fixes an unrelated gap found along the way: proxmox-* Disko image builds write their .raw file straight into the repo root, and .gitignore never covered it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01La55Nsss8jZ7ZuzUV9mfot	2026-07-20 10:31:06 +10:00
beatzaplentyandClaude Sonnet 5	feee2f1679	Add Proxmox VM disk-image building; fix disko confirmation bypass ... modules/disko/proxmox.nix gains imageSize (20G default) and a per-host imageName (networking.hostName, so every proxmox-* host produces a distinctly named image instead of an identical main.raw). This is the same disko.devices config already used to format a real disk on install, so it's available for every proxmox-* target with no per-host changes needed: nix build .#nixosConfigurations.<host>.config.system.build.diskoImagesScript sudo ./result --build-memory 2048 docs/proxmox-images.md covers building, host-key pre-seeding via disko's --pre-format-files (same host-keys/ workflow as the installer and LXC tarball paths), and the qm import/attach sequence for deploying the result to Proxmox. Also fixes a real bug in auto-install.sh found while testing: the disko confirmation bypass used --yes, which disko's CLI doesn't recognize at all (the actual flag is --yes-wipe-all-disks) — so the "skip confirmation" flag was silently a no-op and the interactive prompt kept appearing regardless. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01La55Nsss8jZ7ZuzUV9mfot	2026-07-20 07:01:33 +10:00