4 Commits

Include renames

Author	SHA1	Message	Date
libretech	9eefece320	feat(backup): add rsync --link-dest off-host transport, restore docs ... backup.sh now supports BACKUP_REMOTE_RSYNC alongside BACKUP_REMOTE. The rsync path writes <root>/YYYY-MM-DD/<archive> on the target with --link-dest pointing at the previous day's directory, so unchanged archives become hard links and daily snapshots cost almost zero extra bytes. BACKUP_REMOTE_SSH_KEY routes the rsync ssh leg to a dedicated identity (e.g. rsync.net restricted accounts). Timer moved to 03:00 Europe/Berlin (was 03:17 UTC) per #41. docs/operations.md: full restore procedure (parallel stack first, then atomic swap) plus the rsync vs rclone trade-off. Closes most of #41 — the only remaining task is the operator's choice of off-host target.	2026-04-29 14:47:42 +02:00
libretech	4ba7572565	ci(deploy): switch to libretech/runner-image:v1 and consolidate ... The deploy workflow is now a single job that builds, pushes, and deploys in one runner. Tag computation moved to docker/metadata-action, the per-deploy .env perl rewrite is gone (host pins LIBRENOTES_IMAGE once; main pushes update :main rolling, releases pin to :vX.Y.Z by manual edit), and both jobs run in our bespoke runner image whose runner user already has socket access via group membership. ci.yml moves to the same image so go/make/node are all available without per-step apt installs. Drops compose.prod.yaml (unused, redundant with compose.netcup.yaml).	2026-04-29 12:44:39 +02:00
libretech	c261a23da8	docs(ops): document registry secrets, rollback, Gitea runner image ... operations.md lists the full secret/variable matrix the deploy workflow expects, the new compose.yaml + compose.netcup.yaml invocation, and a note on why both workflow jobs pin catthehacker/ubuntu:runner-latest. self-hosting.md updates the example LIBRENOTES_IMAGE value to the Gitea Packages path and switches the quick-start to compose.netcup.yaml.	2026-04-29 02:00:29 +02:00
libretechandClaude Opus 4.7	bcccba92f7	Add deploy workflow and backup tooling ... CI deployment (.gitea/workflows/deploy.yml): - Two jobs (build, deploy) gated on the repo variable DEPLOY_ENABLED=true so the workflow exists but does nothing until secrets and host are configured. - Build pushes two image tags per run: rolling :main + the short SHA on main, or vX.Y.Z + :latest on tag pushes. Immutable per commit/tag tags make rollback trivial. - Deploy SSHes to DEPLOY_HOST, runs docker compose pull && up -d in DEPLOY_PATH, then polls HEALTH_URL for up to a minute. A failed health check fails the workflow, which is the alert. - Required secrets and the rollback procedure are documented in docs/operations.md. Backup tooling (scripts/): - backup.sh: SQLite online .backup snapshot + tarball of the per-tenant data dir + info.txt header, all wrapped into a single librenotes-YYYYMMDD-HHMMSS.tar.gz. Optional BACKUP_REMOTE triggers an rclone copy for off-site storage. - backup-prune.sh: enforces retention "30 daily + 12 monthly". Sorts archives by filename (date is in the name so lex order matches chronological) and keeps the newest 30 plus the newest archive for each of the most recent 12 months. - backup-restore-test.sh: extracts the most recent archive into a tmpdir, runs sqlite3 .schema (proves DB readability), and asserts the notes tar has at least one entry. Failure is the alert. Wired into a separate weekly timer. - librenotes-backup.{service,timer}: systemd units for the daily 03:17 UTC run with 5min jitter; ProtectSystem=strict, only /var/backups/librenotes is writable. - librenotes-backup-verify.{service,timer}: weekly Monday 04:00 UTC restore test. Closes #26 and #27. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-28 22:49:40 +02:00