Evaluate Long-Term Backup Strategy for LedgerBase Deployments

[williaby]

Overview

The current deploy.yml workflow creates compressed backup tarballs for:

• Docker volumes (e.g., ledgerbase_data)
• Docker images (e.g., ghcr.io/williaby/ledgerbase:latest)

These backups are stored locally on the Unraid runner but not currently uploaded or retained externally.

---

Goals

• Determine if GitHub Artifacts should be enabled for short-term access (90-day expiry)
• Evaluate external long-term storage options:
  • AWS S3
  • Backblaze B2
  • Google Drive via Rclone
• Identify any compliance, retention, or recovery requirements
• Decide whether to implement automated pruning of local tarballs (e.g., >7 days)
• Add SHA256 checksums to each backup for integrity tracking

---

Optional Enhancements

• Slack or Discord webhook notification after successful backup
• Archive metadata to a backups/ directory inside the repo or external dashboard

---

Reference

This issue follows the deployment automation upgrade in deploy.yml and continues backup planning as discussed.

---

Milestone: v1.0 Deployment Finalization
Labels: infra, enhancement, backup, deployment