4 Commits

Include renames

Author	SHA1	Message	Date
Kevin Veen-BirkenbachandClaude Opus 5	d4317827bd	feat(backup): capture volumes from a filesystem snapshot ... Backing up a live volume with rsync copies a moving target: a database written to mid-copy lands on disk in a state no engine ever committed. Stopping the container avoids that at the cost of downtime. A snapshot removes both. `--snapshot {btrfs,zfs}` with `--snapshot-subject` freezes the docker root once per run, and every volume copy is then read from that frozen tree while the containers keep serving. A restore of such a copy is an ordinary crash recovery, which every supported engine performs on its own at startup. An unsupported filesystem or an unknown snapshot kind fails loudly rather than degrading to a live copy, since a silent fallback would return exactly the torn backup the mode exists to prevent. `--shutdown` is rejected alongside `--snapshot` instead of being ignored: under a snapshot no container is ever stopped, so accepting the flag would promise downtime semantics the run does not deliver. Copies out of a snapshot skip rsync's --checksum verification. The source is immutable for the lifetime of the copy, so size-and-mtime cannot race, and dropping the second full read roughly halves the I/O per volume. backup/app.py grew past what one module could carry and is split into layout, policy and dumps along the lines it already had internally. Tests: unit coverage for the new snapshot, layout, policy, volume and cli units; e2e cases drive real btrfs, zfs and ext4 filesystems on loop devices in a privileged container, including a MariaDB that is written to across the snapshot and must recover from the restored copy without losing a committed row. CI installs zfs and sets E2E_REQUIRE_FILESYSTEMS so a missing kernel module fails the build instead of silently skipping a filesystem. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-07-31 13:01:43 +02:00
dependabot[bot]	286ef179da	Bump the actions group with 4 updates ... Bumps the actions group with 4 updates: [actions/checkout](https://github.com/actions/checkout), [actions/upload-artifact](https://github.com/actions/upload-artifact), [docker/login-action](https://github.com/docker/login-action) and [dependabot/fetch-metadata](https://github.com/dependabot/fetch-metadata). Updates `actions/checkout` from 4 to 7 - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](https://github.com/actions/checkout/compare/v4...v7) Updates `actions/upload-artifact` from 4 to 7 - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](https://github.com/actions/upload-artifact/compare/v4...v7) Updates `docker/login-action` from 3 to 4 - [Release notes](https://github.com/docker/login-action/releases) - [Commits](https://github.com/docker/login-action/compare/v3...v4) Updates `dependabot/fetch-metadata` from 2 to 3 - [Release notes](https://github.com/dependabot/fetch-metadata/releases) - [Commits](https://github.com/dependabot/fetch-metadata/compare/v2...v3) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions - dependency-name: actions/upload-artifact dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions - dependency-name: docker/login-action dependency-version: '4' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions - dependency-name: dependabot/fetch-metadata dependency-version: '3' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com>	2026-07-11 07:44:12 +00:00
Kevin Veen-BirkenbachandClaude Fable 5	c949f2c5cf	ci(deps): keep actions, docker base and pip deps updated automatically ... Dependabot opens weekly PRs for the three update surfaces: github-actions (grouped into one PR; the first one also clears the Node 20 deprecation warning on checkout@v4 and upload-artifact@v4), the python base image, and the pip dependencies. A companion workflow enables auto-merge for minor and patch bumps so they land on their own once the required make test check is green; major bumps stay manual. Requires two repo settings: allow auto-merge, and a branch protection rule on main with make test as required status check, which is the gate that keeps auto-merge from landing untested changes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-11 09:19:12 +02:00
Kevin Veen-Birkenbach	698d1e7a9e	ci: add Makefile-driven CI with unit, integration and e2e tests ... - add GitHub Actions CI workflow using Makefile targets exclusively - run unit, integration and e2e tests via `make test` - publish Docker image to GHCR on SemVer tags - force-update `stable` git tag after successful release - add integration test for seed CLI (CSV upsert behavior) - extend Makefile with test-unit and test-integration targets https://chatgpt.com/share/694ee54f-b814-800f-a714-e87563e538b7	2025-12-26 20:43:06 +01:00