Backup pattern: tangled-knot now, sturdy size-based rotation later #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-05-23T01:42:23Z - https://github.com/coilysiren/infrastructure/issues/291
Tangled knot backup (immediate need)
The Tangled knot at tangled.coilysiren.me (deployed via #280, fronted via Traefik in #288) has no backup. Its data is
/var/lib/tangled-knot- git repos plus the SQLiteknotserver.db. Cheap to back up: a tar or snapshot of one directory.For now, a knot-specific backup script or timer that tars
/var/lib/tangled-knot. Naturally pairs with the autodeploy timer's backup-before-deploy sandwich (so deploys are safe) and a periodic backup independent of deploys.Future: sturdy file-size-based backup pattern
The eventual goal is a really sturdy backup pattern across the homelab, but not today.
Direction: file-size-based rotation, not last-in-based. Instead of "keep last N backups," keep backups until the total backup directory size hits a threshold, then rotate the oldest out. Bounds disk use predictably across services with very different backup sizes.
When the general pattern lands, the tangled-knot backup and Forgejo's (see #269) both align to it. Until then, each service can ship a working-but-simple per-service backup script.