cronekorkn/left4me
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

doc(deploy): clarify ckn-bw verbatim-sync workflow for shipped files

Browse source 
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 <noreply@anthropic.com>
This commit is contained in:
mwiegand 2026-05-14 23:57:31 +02:00
parent e4101de7a5
commit f231ebcb0d
No known key found for this signature in database
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
deploy/README.md
View file

@ -19,6 +19,12 @@
> ckn-bw** — the two would fight over file ownership, sudoers, and unit > ckn-bw** — the two would fight over file ownership, sudoers, and unit
> definitions. The script remains useful as concrete documentation of the > definitions. The script remains useful as concrete documentation of the
> install steps the bundle now performs declaratively. > 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) ## What lives here (and what corresponds to it in ckn-bw)