Updated Changelog (markdown)

Michael Stanclift 2021-04-01 15:17:29 -05:00
parent b5624083e0
commit 72aa40ac82

@ -1,3 +1,14 @@
## 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](https://pi-hole.net/2021/02/16/pi-hole-ftl-v5-7-and-web-v5-4-released/#page-content), 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](https://github.com/vmstan/gravity-sync/pull/179))
## 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.