Gravity Sync Versions Save

• Reverts version detection change made in 3.6.2

• Changes the way the version variable is determined.
• Removes the prep folder from this repo, so gs-install.sh is no longer part of the installation bundle. The code can be found at https://github.com/vmstan/gs-install allowing me to iterate faster on it outside of the standard Gravity Sync releases.

In celebration of this GitHub repo reaching 1000 ⭐, here is a major rewrite of the ./gravity-sync.sh config wizard. You are no longer prompted to go into advanced mode as soon as you run the wizard. Most users who have standard installs of Pi-hole on both the local and remote sides will just need to plug in the IP of the remote system, and the SSH username. The guidance for advanced mode has been cleaned up, to hopefully be clearer. Some really advanced settings have been removed from even the advanced part of the wizard. This includes changing the SSH ports, performing ICMP tests, or using a custom RSA keyfile. While these options remain available to users, they now require hand editing the .conf file instead of using the configuration wizard. Instructions for such setups can be found on the Wiki.

If the wizard detects you are running Docker or Podman binaries on the local Pi-hole, it will automatically engage the advanced setup. Even if you're not running Pi-hole in a container. This is by design.

There is now an additional way to enable replication of CNAME Records, if you forget to do so in the when running the configuration wizard. ./gravity-sync.sh cname will enable this flag. If you decide at a later date you turn this off, you can manually edit the configuration file or create a new configuration using the ./gravity-sync.sh config wizard.

• The ✓ ✗ e ! ? status iconography introduced in 3.0 has been changed slightly to remove the brackets around them, as well as using ∞ » and › to draw more attention to instructions.
• Lots of references to backup/restore features that were removed in 3.5 have been deleted. The code for restores is now completely removed.
• Some language has been changed around the script being aborted when it actually exits successfully. Hopefully this is clearer and less, harsh.
• Remote command timeouts for data copies, integrity checks, and other operation have all been increased to a default of 240 seconds from a variety of different times. This can be customized in your .conf file. This should help with folks who have really large databases or really slow storage.
• Variety of minor bug fixes and interface cleanup.

Full Changelog: https://github.com/vmstan/gravity-sync/compare/v3.5.0...v3.6.0

This release changes the backup retention behavior of Gravity Sync. After successful execution of any replication command, Gravity Sync will now wipe out any files from the backup folder. To be clear, this means Gravity Sync will no longer intentionally retain any backups of the Domain Database, Local DNS Records, CNAME Records, after a successful replication.

For a subset of users, the issues of drives filling up because it doesn't properly prune outweigh both the perceived value and my ability to troubleshoot and sort out why this is happening in every instance.

Consequently, the ./gravity-sync.sh backup and ./gravity-sync.sh restore functions have been removed. Any references to backup or restore functions should be removed. Most references in the UI have been changed from backup to copy operations, although variable names and such still reference backup functions.

Folks who have been relying on Gravity Sync to keep historical configuration backups should look for another solution.

Full Changelog: https://github.com/vmstan/gravity-sync/compare/v3.4.8...v3.5.0

• Fixes Pihole update lists command to not cause cache to flush after push/pull operation.

• Remove deprecated/commented code from prior versions.
• Cleanup SSH validation UI

• Add removal of .push and .pull files in backup folder during backup cleanup.
• Setting BACKUP_REMAIN value in configuration to 0 will now purge all .backup files.
• Running manual backup will no longer purge old backup files.
• Undo hiding of revalidation steps, as it was working inconsistently.
• Default backup timeout increased from 60 to 240 seconds.
• Add Gravity Sync folder location and backup directory size to ./gravity-sync.sh info output.
• Added BACKUP_INTEGRITY_WAIT variable to control pause (default 5 seconds) before integrity checks are run on new backup files.
• Various cleanup of some long standing bugs. Sorry for the delay.

• Add the addition of an Environment Path variable in Crontab (#212)
• Add detection of missing path components and addition of path to crontab
• Fix bug where \n is inserted literally
• Fix find command invoke (Issue #220) (#223)

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

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