Releases: ZettaIO/restic-compose-backup
Releases · ZettaIO/restic-compose-backup
0.7.1
0.7.0
0.6.0
0.5.0
0.4.2
- Environment variables
DOCKER_HOST
,DOCKER_TLS_VERIFY
andDOCKER_CERT_PATH
can now be used to configure how to talk to the docker service. - Volumes mounted in the backup service can now also be marked for backup
- Fixed an issue with identifying the backup process container
0.4.1
0.4.0
New Features
- We now gather stale backup process containers and purge them before every bakcup. This is to avoid filling up unnecessary disk space over time.
- Support for multiple backup containers in the same docker engine (in different projects)
- Automatically detect if a repository is initialize and initialize if this is not the case
- The crontab is now automatically generated and is configurable through env vars
- We now check the health if the repository after every backup. An alert is sent if something is wrong.
Improvements
- Alert when backup process is already running when a backup starts
- Alert when the backup process doesn't find anything to back up
- The stdin/out buffer size is now set to 64kb when doing backups from stdin
Bugfixes
- Include stdout output from commands when exit code is not 0
- Properly truncate discord embed fields so we don't exceed the filed size limit preventing alerts from being sent
- Properly error log if a backup process already running when a backup starts
0.3.3
0.3.2
0.3.1
Improvements
- The status command now displays the repository name
rcb status
now attempts to initialize the repo- Properly log exceptions with call stacks
- Bumped docker-py to 4.1.x
- Remove references to old tags
Bugfixes
- Forget and prune was never properly called after each backup
- Properly detect when forget or prune commands fails and alert the user
- Ensure the backup container is stopped before deleting it
- Detect and alert issues with running the backup container