Files

T

Gmer4Lfe 7332eb81e0 Add persistent partner conf backup across reboots

conf_cache_save.sh runs first on array stop — snapshots partner confs from RAM
cache to /boot/config/varaverk/conf_bak/ before anything else shuts down.

conf_cache_restore.sh runs after conf_sync.sh on array start — if partner was
unreachable and RAM cache is incomplete, loads the backup into RAM then removes
it. Normal reboots: backup written, fresh pull succeeds, backup deleted unused.
Edge case (partner down at boot): backup fills the gap so fallback.sh has the
partner vars it needs to operate correctly.

2026-06-19 17:40:46 -04:00

master.conf

Add persistent partner conf backup across reboots

2026-06-19 17:40:46 -04:00

README.md

move conf templates and conf_populate to Deployment/; add rogue-prevention rules to CLAUDE.md

2026-06-14 13:18:08 -04:00

README.md

Configurations/

Runtime home for the live conf files. These are gitignored — never committed.

File	Source
`master.conf`	Seeded from `Deployment/master.conf.template` on first install
`host1.conf`	Seeded from `Deployment/host.conf.template` on first install
`host2.conf`	Seeded from `Deployment/host.conf.template` on first install

Templates and tooling live in Deployment/:

Deployment/host.conf.template — canonical template for new host confs
Deployment/master.conf.template — canonical template for master.conf
Deployment/conf_upgrade.sh — merges schema changes into existing confs
Deployment/conf_populate.sh — auto-detects and fills arr keys on first run