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 Installing (markdown)

Michael Stanclift 2021-04-27 10:35:25 -05:00
parent f6f340a61b
commit cc9ffc145f
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Installing.md

@ -57,7 +57,7 @@ Now, test Gravity Sync. You can run a comparison between primary and secondary d
Assuming Gravity Sync runs successfully, it will indicate if there are changes pending between the two databases. 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. **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, run `./gravity-sync.sh pull` to bring all of the settings from the primary over to the secondary. You should do this before you run a standard sync, as it may see the default secondary Pi-hole configuration as newer and overwrite them on the primary.
### The Sync ### The Sync