From d27bb9209b79af9f3fc6faa5b2c1fcab5ce8c914 Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Tue, 28 Apr 2026 16:01:06 -0700 Subject: [PATCH] README: document scripts/fork-fleet.sh in Common tasks --- README.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/README.md b/README.md index 529b3bb..76d832d 100644 --- a/README.md +++ b/README.md @@ -127,6 +127,27 @@ scripts/deploy-stack.sh scripts/sync-stacks.sh all ``` +**Bootstrap a new fleet repo from this one:** +```bash +scripts/fork-fleet.sh ~/development/-management +# optional: override the fleet-name baked into the skeleton CLAUDE.md / README +scripts/fork-fleet.sh ~/development/ +``` + +Mirrors the reusable tooling (everything under `scripts/`, the +generic playbook templates, `.gitignore`, conventions section of +`CLAUDE.md`) into the destination dir, strips fleet-specific content +(`servers/`, `stacks/`, `configs/`, fleet-named playbooks +(`deploy-*`, `decouple-*`), `docs/orientation.md`, `docs/runbooks/`, +`docs/pfi/`, `STATUS.md`, host-pinned helper scripts), regenerates +skeleton `CLAUDE.md` / `README.md` / `STATUS.md` with the new fleet +name, and initializes a fresh git history with one "Initial commit". + +The script does **not** create a gitea remote or push — namespace + +repo name are an explicit manual step. The "next steps" output prints +the exact `tea repo create` + `git remote add` + `git push` commands +to wire it up when ready. + ## Backup pipeline Backups are driven by per-host `resticprofile` configs under `configs/restic//`, scheduled via systemd timers on each host: