Cutlery/gravity-sync
1
0
Fork 0
mirror of https://github.com/vmstan/gravity-sync.git synced 2025-07-09 02:34:06 -04:00
Code Issues Packages Projects Releases Wiki Activity

Updated Changelog (markdown)

Michael Stanclift 2021-04-26 11:39:49 -05:00
parent e0c53ed6ec
commit e34932c84c
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Changelog.md

@ -18,6 +18,11 @@ This release was initially supposed to just be 3.3.3, but eventually became a to
- Performs an automated SQLITE3 integrity check on the Domain Database backup that is taken on the remote (or local) Pi-hole, prior to replication.
- Clarifies the wording that made it look like backups were being performed twice on the remote configuration during a push operation. The remote backups are actually just being copied to the local Gravity Sync for retention.
#### 3.4.4
- 3.4.3? Where we’re going we don’t need 3.4.3.
- Adds backup deletion step after a failed SQLITE3 integrity check, to prevent backup folders from filling up bad data on the secondary Pi-hole.
## 3.3 - The Podman Release
For this release, "beta" support for [Podman](https://podman.io) based container deployments has been added. (Thanks to work by [@mfschumann](https://github.com/vmstan/gravity-sync/pull/138)) This is marked as beta because at the moment, Gravity Sync may not be regularly tested with this container engine and so regular support may be limited. Use of the official Pi-hole container image is still required.