Follow-up to #6. That PR removed variables.nix's deployedTargets because a manually-maintained file cannot track live infrastructure state and drifted stale more than once. The Hosts table in README.md had the identical problem in prose form -- "(real, deployed)" annotations that need a manual edit on every migration and are not enforced against anything.
Strips deployment-status claims out of the table, keeping only what does not rot: what each target is for, and stable naming history (e.g. "previously the flat nix-cache target"). Points readers at the live Proxmox node or /etc/flake-target instead for actual current deployment status.
Follow-up to #6. That PR removed variables.nix's deployedTargets because a manually-maintained file cannot track live infrastructure state and drifted stale more than once. The Hosts table in README.md had the identical problem in prose form -- "(real, deployed)" annotations that need a manual edit on every migration and are not enforced against anything.
Strips deployment-status claims out of the table, keeping only what does not rot: what each target is for, and stable naming history (e.g. "previously the flat nix-cache target"). Points readers at the live Proxmox node or /etc/flake-target instead for actual current deployment status.
Same problem as the deployedTargets removal, just in markdown instead of
Nix: which variant of a buildtype is actually deployed is live
infrastructure state, and a committed table can't stay accurate as that
changes -- it already required a manual edit on every migration and had
drifted before. Keep only what doesn't rot: what each target is for, and
stable naming history. Point at the live node / /etc/flake-target instead
for actual deployment status.
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.
Follow-up to #6. That PR removed variables.nix's deployedTargets because a manually-maintained file cannot track live infrastructure state and drifted stale more than once. The Hosts table in README.md had the identical problem in prose form -- "(real, deployed)" annotations that need a manual edit on every migration and are not enforced against anything.
Strips deployment-status claims out of the table, keeping only what does not rot: what each target is for, and stable naming history (e.g. "previously the flat nix-cache target"). Points readers at the live Proxmox node or /etc/flake-target instead for actual current deployment status.
f43de81a0bto97ede62f6d