3.4.1

• 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.0

3.4 — The Consistent Release

This release was initially supposed to just be 3.3.3, but eventually became a total rewrite of how text strings are generated and displayed in the script. The most noticeable is a conversion of references to things like gravity.db or custom.list and a switch towards Domain Database or Local DNS Records to make it consistent and easier to understand. Other changes are mostly cosmetic, but attempt to reduce or streamline status messages.

• The end of the script less cuter but more clearer about cleanup of existing database backups, and now also includes the size of the backup directory as part of the output. Ex: 3 days of backups remain (25M)
• The environment validation steps under regular execution (compare, push, pull, sync) are hidden from the output if they complete successfully to reduce the overall verbosity of the script output.
• The re-validation hashing steps that take place after a replication execution (push, pull, sync) are hidden from the output if they complete successfully to reduce the overall verbosity of the script output.
• Many of the status output messages have been rewritten to be more understandable, and consistent.
• Validated support for Pi-hole FTL v5.7 and Web v5.4, although the none of the new configuration settings that have been added (ex: DNS query rate limiting) are managed by Gravity Sync.
• Fixes an error where the remote system container names were not properly queried. (#179)

3.3.2

• Fixes issue where Docker Swarm change introduced in 3.3.0 was not properly implemented for remote Docker instances. #169

3.3.1

• Fixes issue with inverted Advanced Install Options selection. #163
• Changes to documentation included in the GitHub clone package.
• Moves gravity-sync.conf.example file to templates folder.
• Fixes an issue where backups in the previous year would not be deleted automatically. (Making this one less place for 2020 to haunt us all.) #167
• Provisional support for using container images other than the official Pi-hole image. #168
• Three new Star Trek references.

3.3.0

The Podman Release

For this release, "beta" support for Podman based container deployments has been added. (Thanks to work by @mfschumann) 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.

This release also removes automated nightly backups as a function of the automation script. You can still execute a manual ./gravity-sync.sh backup anytime. Automating this function was made redundant by the primary synchronization functions backing up the database files prior to execution in later versions, resulting in multiple backups or backing up unchanged data. Existing users will continue to backup each night unless you run ./gravity-sync.sh automate again to configure a new schedule, at which time the existing backup job will be deleted.

Additionally, this release focuses on making some of the prompts and messages in Gravity Sync easier to understand. Starting with the initial install and configuration wizard. As the script has grown, added features, and become more complex... more options are necessary during install and it wasn't always clear what to do. This release adds some clarification to various components and will change over time.

Configuration Changes

• The first time you execute Gravity Sync after upgrading to 3.3, your gravity-sync.conf file will be moved into a settings folder in the same directory.
• The first time you execute Gravity Sync after upgrading to 3.3, your existing gravity-sync.md5, gravity-sync.log, and gravity-sync.cron files will be moved into a logs folder in the same directory.
• The default number days for which backups are retained has been reduced from 7 to 3.

Bug Fixes

• Docker Swarm use for the Pi-hole container should be supported by a change in the execution command.

3.2.6

• Adds old backup removal tasks into push/pull/sync/compare functions.

3.2.5

• Correct error where Docker based installs would fail to restart if Docker exec commands required sudo privileges.
• Correct error where setup script would prompt twice for Local/Remote DNSMASQ directories when using Docker.

3.2.4

• Changes script startup and shutdown text format.

3.2.3

• Cleanup of the error message screen when an invalid command is run (ex: ./gravity-sync.sh wtf)

3.2.2

The ./gravity-sync.sh restore process completely revamped:

• You can now choose to ignore any of the three elements during restore.
• The prompts are clearer and more consistent with Gravity Sync script styling.
• Importantly, lack of backup files in an element will not cause the restoration to fail.