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

Updated Alternatives (markdown)

Michael Stanclift 2022-04-03 23:48:30 -05:00
parent 2155c802ef
commit 7168b75c7b
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Alternatives.md

@ -1,8 +1,8 @@
Not sure if Gravity Sync is right for you? Here are some alternatives you should consider.
## Pi-Hole Cloud-sync
## Pi-Hole Cloudsync
* **Project:** [https://github.com/stevejenkins/pihole-cloudsync](https://github.com/stevejenkins/pihole-cloudsync)
* **Developer:** [Steve Jenkins](https://www.stevejenkins.com/blog/)
Cloud-Sync performs many of the same functions as Gravity Sync, the fundamental difference is that Cloud-Sync uses the cloud (hence the name) to be the authoritative source for multiple Pi-hole instances. Where Gravity Sync is designed to function in a peer model, with both instances either on the same network or accessible through a VPN or other tunnel, Cloud-Sync pushes changes GitHub to store them and then multiple Pi-hole instances can connect to GitHub and pull them.
Cloudsync performs many of the same functions as Gravity Sync, the fundamental difference is that Cloudsync uses the cloud (hence the name) to be the authoritative source for multiple Pi-hole instances. Where Gravity Sync is designed to function in a peer model, with both instances either on the same network or accessible through a VPN or other tunnel, Cloudsync pushes changes GitHub to store them and then multiple Pi-hole instances can connect to GitHub and pull them.