README: document scripts/fork-fleet.sh in Common tasks
This commit is contained in:
@@ -127,6 +127,27 @@ scripts/deploy-stack.sh <host> <stack>
|
||||
scripts/sync-stacks.sh all
|
||||
```
|
||||
|
||||
**Bootstrap a new fleet repo from this one:**
|
||||
```bash
|
||||
scripts/fork-fleet.sh ~/development/<other-fleet>-management
|
||||
# optional: override the fleet-name baked into the skeleton CLAUDE.md / README
|
||||
scripts/fork-fleet.sh ~/development/<dest> <fleet-name>
|
||||
```
|
||||
|
||||
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/<host>/`, scheduled via systemd timers on each host:
|
||||
|
||||
Reference in New Issue
Block a user