From 69d931e330792b5cc33f2f9d2703504a294fd0d4 Mon Sep 17 00:00:00 2001 From: Michael Stanclift Date: Tue, 6 Apr 2021 13:39:25 -0500 Subject: [PATCH] Updated Changelog (markdown) --- Changelog.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Changelog.md b/Changelog.md index 71c71db..21891f1 100644 --- a/Changelog.md +++ b/Changelog.md @@ -13,6 +13,11 @@ This release was initially supposed to just be 3.3.3, but eventually became a to - Adds a optional `BACKUP_TIMEOUT` variable to the `gravity-sync.conf` file to allow users to adjust the time the script will wait until marking the SQLITE3 backup operation as failed. This was previously hard coded to 15 and then raised to 60, but raising it even higher has been seen to mitigate against failed replication jobs on slower SD Cards or older Raspberry Pi's where the database backup does not complete, yet still replicates. +#### 3.4.2 + +- 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.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.