mirror of
https://github.com/vmstan/gravity-sync.git
synced 2025-07-09 02:34:06 -04:00
Updated Changelog (markdown)
parent
222ff7be23
commit
334014e11d
10
Changelog.md
10
Changelog.md
@ -19,6 +19,16 @@ There is now an additional way to enable replication of CNAME Records, if you fo
|
||||
- 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.6.2
|
||||
|
||||
- Reverts version detection change in 3.6.2
|
||||
|
||||
#### 3.6.3
|
||||
|
||||
- Adds logic to SMART task to only restart the Pi-hole DNS service if replication of Local DNS or CNAMEs take place within a replication task.
|
||||
- Adds local environment $PATH to the crontab when automation tasks are enabled to make sure that Pi-hole services can properly restart.
|
||||
- If you are running into issues with your Pi-hole storage filling up, it's likely due to the Pi-hole DNS service not restarting and the script failing, please update to 3.6.3 and recreate your automation task using `./gravity-sync.sh auto`
|
||||
|
||||
## 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.
|
||||
|
Loading…
x
Reference in New Issue
Block a user