mirror of
https://github.com/vmstan/gravity-sync.git
synced 2025-08-30 22:59:58 -04:00
Updated Alternatives (markdown)
parent
ce33e47db2
commit
b962314f2b
@ -1 +1,12 @@
|
||||
## Gravity Sync vs Pi-Hole Cloud-sync
|
||||
Not sure if Gravity Sync is right for you? Here are some alternatives you should consider.
|
||||
|
||||
## Pi-Hole Cloud-sync
|
||||
|
||||
**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.
|
||||
|
||||
✅ Better support for more than 2 Pi-hole than Gravity Sync
|
||||
✅ Doesn't require direct network connections between instances
|
||||
⚠️ Requires cloud/GitHub repo to store configuration data
|
Loading…
x
Reference in New Issue
Block a user