AUTO_BACKUP_ALL is here!

stack-back now has one environment variable to back up all volumes and databases. Due to the new inclusion of databases, the previous auto-detection variable will be soft-deprecated and replaced with AUTO_BACKUP_ALL for less confusion. To maintain backward compatibility, INCLUDE_ALL_VOLUMES will continue to function in the same way as AUTO_BACKUP_ALL if it is defined instead.

To automate the detection of databases, stack-back examines the image of running containers to check if it is an official database image (mysql, mariadb, or postgres).

When database images are auto-detected and added to the backup configuration, their default data volume mount is excluded from volume backups to prevent duplicate backups (volume and database dump). Excluded mount destinations are /var/lib/mysql for MySQL and MariaDB and /var/lib/postgres/data for Postgres.

Dev enhancements

The restic-compose-backup Python project that underpins the functionality of stack-back is now managed by uv. This will make it a lot easier for external contributors to get up and running quickly.

Various tests were also added for new and existing functionality.

What's Changed

• Update actions/attest-build-provenance digest to db473fd by @renovate in #34
• Update astral-sh/setup-uv digest to 6b9c606 by @renovate in #38
• Optional maintenance schedule by @lawndoc in #39
• Update anothrNick/github-tag-action action to v1.73.0 by @renovate in #40
• Update restic/restic Docker tag to v0.18.0 by @renovate in #27
• Update docs and tests by @lawndoc in #41
• Detect databases to enable auto backups by @lawndoc in #42

Full Changelog: v1.3.0...v1.4.0