From de681f33dad7bc38876fbcb782510c3f8c9a9a9b Mon Sep 17 00:00:00 2001 From: Jack O'Sullivan Date: Sun, 2 Aug 2026 21:20:53 +0100 Subject: [PATCH] docs: Note container deploy targets Co-Authored-By: Claude Opus 4.8 --- AGENTS.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 65afaaa..29ae9cb 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -46,7 +46,10 @@ Common ones: Pass the flake-qualified node, e.g. `deploy .#git`. The deploy node name is **always** the system name (`deploy-rs.nix` keys nodes directly off `nixos.systems` / `home-manager.homes`); a system is only a deploy target when `config.my.deploy.enable` is true (defaults true; auto-disabled for dev - VMs and containers). Pass `--boot` to stage a config as the boot default **without** live-switching + VMs and containers). A container is **not** its own deploy node — it is generated as a + `container-` profile on its **host** node. So `deploy .#` deploys the host's `system` + profile and every one of its containers, whereas `deploy .#.container-` targets a + single container (e.g. `deploy .#shill.container-middleman`). Pass `--boot` to stage a config as the boot default **without** live-switching (`deploy --boot .#`) — the box keeps running its current generation until it reboots. Use this when a live `switch` would break connectivity mid-change (e.g. a router's WAN VLAN rework), then reboot to cut over.