The old proxmox-nix-cache VM was destroyed and nix-cache is being redeployed as an LXC container going forward. create-proxmox-resource.sh's duplicate-host check only reads variables.nix's static deployedTargets list (not live Proxmox state), so it kept refusing to create lxc-nix-cache even though nothing named nix-cache actually exists on the node anymore.
Updates variables.nix and README.md so lxc-nix-cache is the declared real deployment, matching the current/intended state.
The old proxmox-nix-cache VM was destroyed and nix-cache is being redeployed as an LXC container going forward. create-proxmox-resource.sh's duplicate-host check only reads variables.nix's static deployedTargets list (not live Proxmox state), so it kept refusing to create lxc-nix-cache even though nothing named nix-cache actually exists on the node anymore.
Updates variables.nix and README.md so lxc-nix-cache is the declared real deployment, matching the current/intended state.
The old proxmox-nix-cache VM was destroyed and nix-cache is being
redeployed as an LXC container going forward. Without this update,
create-proxmox-resource.sh's duplicate-host check (which only reads this
static list, not live Proxmox state) kept refusing to create
lxc-nix-cache even though nothing named nix-cache actually exists on the
node anymore.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The old proxmox-nix-cache VM was destroyed and nix-cache is being redeployed as an LXC container going forward. create-proxmox-resource.sh's duplicate-host check only reads variables.nix's static deployedTargets list (not live Proxmox state), so it kept refusing to create lxc-nix-cache even though nothing named nix-cache actually exists on the node anymore.
Updates variables.nix and README.md so lxc-nix-cache is the declared real deployment, matching the current/intended state.