Updated Changelog (markdown)

Michael Stanclift 2022-03-02 09:46:01 -06:00
parent 497ed0baf5
commit 23d87af82b

@ -6,12 +6,19 @@ If the wizard detects you are running Docker or Podman binaries on the local Pi-
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.
### Other Changes
- 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.
#### 3.6.1
- 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.
## 3.5 — The Exhausted Release
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.