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 Frequent Questions (markdown)

Michael Stanclift 2020-10-21 13:56:09 -05:00
parent 4cd98c53a0
commit 65f29f14b5
1 changed files with 15 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
Frequent-Questions.md

@ -46,4 +46,18 @@ These are frequent questions about Gravity Sync implementations. In addition to
- Not recommended.
- Gravity Sync already moves data in both directions. If you have it running from both Pi-hole against each other then you could probably get into a condition where they are both trying to push/pull at the same time, causing them to get confused, or possibly resulting in data loss.
- If you have a third Pi-hole, perhaps at a remote/cloud site, that you want to sync with your first to, you should install Gravity Sync on a second of the three and use it only to pull data from one of the first two Pi-hole.
- If you have a third Pi-hole, perhaps at a remote/cloud site, that you want to sync with your first to, you should install Gravity Sync on a second of the three and use it only to pull data from one of the first two Pi-hole.
### Does Gravity Sync work with Pi-hole 4?
- No.
- Pi-hole 5 implemented a new database called `gravity.db` that contains all the active blocklist settings. Gravity Sync was written specifically for Pi-hole 5.
### Does Gravity Sync work with Pi-hole v5.x?
- Probably.
- I am pretty good about tracking their releases, and expect that if there are breaking changes I would adapt to those quickly, but I do anticipate any issues.
### Why doesn't the Pi-hole project support replication?
- Ask them.