From f231ebcb0d38c7d20c1f468369c64ded7e12125a Mon Sep 17 00:00:00 2001 From: mwiegand Date: Thu, 14 May 2026 23:57:31 +0200 Subject: [PATCH] doc(deploy): clarify ckn-bw verbatim-sync workflow for shipped files MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Spell out that the deploy step for changes to verbatim-shipped files (privileged helpers, sudoers, sysctl, …) is just re-syncing the bundle's copy + bw apply. Removes ambiguity for the idmap helper change and any future edit within the same set. Co-Authored-By: Claude Opus 4.7 --- deploy/README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/deploy/README.md b/deploy/README.md index 9c371c1..7b83a77 100644 --- a/deploy/README.md +++ b/deploy/README.md @@ -19,6 +19,12 @@ > ckn-bw** — the two would fight over file ownership, sudoers, and unit > definitions. The script remains useful as concrete documentation of the > install steps the bundle now performs declaratively. +> +> **Verbatim-shipped files**: when a row in the table below says "shipped +> verbatim by the bundle," the only deploy step for changes to that file is +> to re-sync the matching path in `ckn-bw/bundles/left4me/files/…` and run +> `bw apply ovh.left4me`. No new group / user / unit work needed unless the +> change itself introduces one. ## What lives here (and what corresponds to it in ckn-bw)