Cutlery/gravity-sync
1
0
Fork 0
mirror of https://github.com/vmstan/gravity-sync.git synced 2025-07-09 02:34:06 -04:00
Code Issues Packages Projects Releases Wiki Activity

Updated Engaging (markdown)

Michael Stanclift 2022-04-13 10:04:02 -05:00
parent 498707b979
commit cf777141bd
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Engaging.md

@ -18,7 +18,7 @@ You must now pick the Pi-hole instance that currently has the "authoritative" li
gravity-sync push gravity-sync push
``` ```
If you do not follow this step, especially if one of your Pi-hole instances is a fresh install, you run the risk of overwriting your current configuration with a default setup or something else less desirable. ([More on Push vs Pull](https://github.com/vmstan/gravity-sync/wiki/Pull-vs-Push)) If you do not follow this step, especially if one of your Pi-hole instances is a fresh install, you run the risk of overwriting your current configuration with a default setup or something else less desirable.
## Standard Orbit ## Standard Orbit
@ -34,4 +34,6 @@ Gravity Sync will perform some checks to help ensure success and then stop befor
In the event there are configuration changes to the same element (example, `custom.list` changes at both sides) then Gravity Sync will attempt to determine based on timestamps on what side the last changed happened, in which case the latest changes will be considered authoritative and overwrite the other side. Gravity Sync **does not** merge the contents of the files. In the event there are configuration changes to the same element (example, `custom.list` changes at both sides) then Gravity Sync will attempt to determine based on timestamps on what side the last changed happened, in which case the latest changes will be considered authoritative and overwrite the other side. Gravity Sync **does not** merge the contents of the files.
If the execution completes, you will now have a synchronized copy of your running `gravity.db`, `custom.list` and `05-pihole-custom-cname.conf` on both Pi-hole. If the execution completes, you will now have a synchronized copy of your running `gravity.db`, `custom.list` and `05-pihole-custom-cname.conf` on both Pi-hole.
[More on Push vs Pull](https://github.com/vmstan/gravity-sync/wiki/Pull-vs-Push).