mirror of
https://github.com/vmstan/gravity-sync.git
synced 2025-07-09 02:34:06 -04:00
Updated Installing (markdown)
parent
d754d8ccd8
commit
270d51c372
@ -45,7 +45,11 @@ Now, test Gravity Sync. You can run a comparison between primary and secondary d
|
|||||||
./gravity-sync.sh compare
|
./gravity-sync.sh compare
|
||||||
```
|
```
|
||||||
|
|
||||||
Assuming Gravity Sync runs successfully, it will indicate if there are changes pending between the two databases. If not, make a subtle change to a allow/block list on your primary Pi-hole, such as changing a description field or disabling a allow list item, and then running `./gravity-sync.sh compare` again to validate your installation is working correctly.
|
Assuming Gravity Sync runs successfully, it will indicate if there are changes pending between the two databases.
|
||||||
|
|
||||||
|
**Important!** If you have just performed a fresh install of your secondary Pi-hole (where Gravity Sync is now installed) and it's list configurations do not already match your primary, make a subtle change to a allow/block list on your _primary_ Pi-hole (such as changing a description field or disabling a allow list item) before running your first sync.
|
||||||
|
|
||||||
|
Failure to do so may overwrite your primary configuration with the secondary's default/generic Pi-hole configuration.
|
||||||
|
|
||||||
### The Sync
|
### The Sync
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user