From 7168b75c7b69fbd62466c9fac4d849ed6ff31fca Mon Sep 17 00:00:00 2001 From: Michael Stanclift Date: Sun, 3 Apr 2022 23:48:30 -0500 Subject: [PATCH] Updated Alternatives (markdown) --- Alternatives.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Alternatives.md b/Alternatives.md index 8693c47..40bbaf9 100644 --- a/Alternatives.md +++ b/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. \ No newline at end of file +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. \ No newline at end of file