Releases: lawndoc/stack-back
v1.4.5
What's Changed
Full Changelog: v1.4.4...v1.4.5
Contributors
Assets 2
v1.4.4
What's Changed
- Update astral-sh/setup-uv digest to bd01e18 by @renovate in #53
- Update docker/setup-buildx-action digest to e468171 by @renovate in #52
- chore(deps): update actions/attest-build-provenance digest to e8998f9 by @renovate in #51
- chore: honor restic retention settings by @igolman in #49
Full Changelog: v1.4.3...v1.4.4
Contributors
Assets 2
v1.4.3
What's Changed
- chore: remove obsolete docker compose version by @igolman in #45
- chore(deps): update astral-sh/setup-uv digest to f0ec1fc by @renovate in #47
- chore(deps): update docker/build-push-action digest to 2634353 by @renovate in #43
- fix: changed container hostname by @faekiva in #50
New Contributors
Full Changelog: v1.4.2...v1.4.3
Contributors
Assets 2
v1.4.2
What's Changed
- fix double log prefix during backup by @lawndoc in 39571b2
- chore: update mariadb env variables in compose file by @igolman in #46
Full Changelog: v1.4.1...v1.4.2
Contributors
Assets 2
v1.4.1
Temp fix for database backup issue
Bumping the restic base image from 0.17.3 to 0.18.0 caused database backups to fail. See #44 for details.
I'm still working on a root cause fix for the new base image. For now, the base image has been reverted back to 0.17.3 so the new features in stack-back 1.4.0 have a working release.
Full Changelog: v1.4.0...v1.4.1
v1.4.0
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
Contributors
Assets 2
v1.3.0
Contributors
Assets 2
v1.2.2
What's Changed
- chore(deps): update postgres docker tag to v17 by @renovate in #31
- chore(deps): update mariadb docker tag to v11 by @renovate in #29
- chore(deps): update actions/checkout action to v4 by @renovate in #28
- chore(deps): update anothrnick/github-tag-action action to v1.71.0 by @renovate in #25
- chore(deps): pin dependencies by @renovate in #33
- Unlock stale locks before forget and prune by @lawndoc in #32
Full Changelog: v1.2.1...v1.2.2
