Skip to content

v1.1.1 — 2026-04-21

Documentation refinement closing the persistence audit from v1.1.0. No code, no schema, no compose changes — just docs.

What landed

The v1.1.0 release prep produced a persistence audit with ten action items. Four HIGH-priority items shipped in v1.1.0 itself (docs corrections for manual cert DR + the boot reconciler code). The remaining MEDIUM/LOW items land here:

  • Persistence — new page. Single-source-of-truth for "what persists, what's in backups, how to do DR":
    • Full volume matrix for all 8 named volumes (compose name + host name + contents + backup scope + loss impact + recovery path).
    • Backup-scope breakdown: what the tar.gz captures, what it doesn't, how off-site replication fits, why ARGOS_MASTER_KEY must be kept out of band.
    • Step-by-step disaster recovery checklist for the fresh-infra rebuild scenario.
    • Volume lifecycle operations: inspect, size, move between hosts, reset.
    • Integrity verification with sha256 baselines and a ready-to-run cron script for caddy_manual_certs drift detection.
  • Bind-mount production layout — added as a section in the persistence page. Full override template for replacing any or all of the named volumes with host paths (/srv/argos-edge/...) so external backup tooling works directly against the filesystem. Includes the uid/gid setup, SELinux note, NFS caveat, and a migration recipe for converting a running stack from named volumes to bind mounts.
  • name: override rationale — short explanatory subsection added to Running multiple instances. Explains why the shipped compose hardcodes volume names, why -p <project> alone doesn't scope them, and the intentional trade-off: one compose.yml = one set of volumes; a second instance = one deliberate override file.

Upgrade

cd argos-edge
git pull

That's it. Nothing runtime-level changed.

Audit item status

  • D1–D4 shipped in v1.1.0.
  • D5 (new persistence page) — this release.
  • D6 (down -v warning in upgrading + restore) — shipped in v1.1.0.
  • D7 (ARGOS_MASTER_KEY out-of-band warning) — shipped in v1.1.0, reinforced in the new persistence page.
  • D8 (bind-mount deployment guide) — this release.
  • D9 (name: override rationale) — this release.
  • D10 (sha256 integrity checks) — this release, integrated in the persistence page.

The audit is closed.