70d3019a1c
Add deployments/kanrisha: a phased, self-contained deploy.sh for a custom app that runs on a ScoutFS filesystem. Alma/Rocky (RHEL family) only for now. Phase 1 (host prep) is complete and automated: EPEL + the host package set (git tar sparse mt-st mtx sg3_utils pciutils mbuffer wget curl zstd jq bash-completion sos lsof), Docker, and ScoutFS via setup-scoutfs.sh with a prompted-or-globals license key. It then prints a handoff: create + mount a ScoutFS filesystem, then re-run with SCOUTFS_PATH set. Phase 2 (deploy the stack behind Caddy/TLS) is wired but its compose/Caddyfile content is a clearly-marked STUB pending the real Kanrisha compose file. The script auto-selects the phase from whether SCOUTFS_PATH is a live ScoutFS mount; idempotent and re-runnable. Wiring: register kanrisha in automations.sh (DEPLOYMENTS + ask_deployment_vars), add SCOUTFS_LICENSE to globals.env.example, and document it in README (deployments table + Alma/Rocky-only note). No oslib.sh change needed -- os_detect already folds rocky into the rhel family. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>