Repository navigation
Add automated backup tooling and documentation #48
Description
Problem
Data persistence relies on Docker volumes with no backup automation. WAL and Parquet files in /var/lib/inputlayer/data need an external backup strategy, but none is documented or provided.
Action
- Document backup/restore procedures for the data directory
- Consider a built-in
inputlayer backupCLI command for consistent snapshots - Provide example cron job or script for automated backups
- Document recovery procedures from WAL + Parquet files
Generated from production readiness audit
Activity
jsam commentedon Oct 1, 2026
Still valid. Step 1: document offline backup and restore, with a warning against copying a live data dir. Step 2: a consistent
.backup <path>checkpoint (flush plus hardlink under lock) with a restore test. This matters for per-user voice memory.feat(storage): restore-tested offline backup tool and runbook
feat(storage): consistent online checkpoint export (.backup)