6 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
Kevin Veen-BirkenbachandClaude Fable 5	f9776ac47a	feat(backup)!: exact --images-* matching and --hard-restart-projects ... Match --images-no-stop-required and --images-no-backup-required against the container's exact .Config.Image instead of a substring, so callers pass full repo:tag references (registry prefix included) and near-miss image names no longer flip the stop/skip decision. Rename the opt-in --hard-compose-restart flag to --hard-restart-projects. The e2e suite pins a SPOT for the DB images and in-container data dirs (postgres:alpine at /var/lib/postgresql, mariadb:latest at /var/lib/mysql) and passes exact image refs to the --images-* flags. BREAKING CHANGE: --images-* now require exact image references, not substrings; --hard-compose-restart is renamed to --hard-restart-projects. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-12 18:19:20 +02:00
Kevin Veen-BirkenbachandClaude Fable 5	79214e64e8	test(unit): mock is_swarm_task in the requires_stop tests ... requires_stop now probes is_swarm_task per container, which runs a real docker inspect; the unit CI container has no docker socket, so the three whitelist tests died with BackupException. Mock the probe to False so they assert the unchanged whitelist logic, and add a swarm case proving a task container never triggers a stop and skips the image check entirely. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-11 08:35:23 +02:00
Kevin Veen-Birkenbach	6adafe6b1f	fix(backup): log missing db config instead of raising ... - Use module logger in backup/db.py - Skip db dump when no databases.csv entry is present - Apply black/formatting cleanup across backup/restore/tests https://chatgpt.com/share/69519d45-b0dc-800f-acb6-6fb8504e9b46	2025-12-28 22:12:31 +01:00
Kevin Veen-Birkenbach	c30b4865d4	refactor: migrate to src/ package + add DinD-based E2E runner with debug artifacts ... - Replace legacy standalone scripts with a proper src-layout Python package (baudolo backup/restore/configure entrypoints via pyproject.toml) - Remove old scripts/files (backup-docker-to-local.py, recover-docker-from-local.sh, databases.csv.tpl, Todo.md) - Add Dockerfile to build the project image for local/E2E usage - Update Makefile: build image and run E2E via external runner script - Add scripts/test-e2e.sh: - start DinD + dedicated network - recreate DinD data volume (and shared /tmp volume) - pre-pull helper images (alpine-rsync, alpine) - load local baudolo:local image into DinD - run unittest E2E suite inside DinD and abort on first failure - on failure: dump host+DinD diagnostics and archive shared /tmp into artifacts/ - Add artifacts/ debug outputs produced by failing E2E runs (logs, events, tmp archive) https://chatgpt.com/share/694ec23f-0794-800f-9a59-8365bc80f435	2025-12-26 18:13:26 +01:00
Kevin Veen-Birkenbach	2d2376eac8	Implemented new parameters to make it more flexibel for cymais	2025-07-14 18:47:25 +02:00