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:49:36 -05:00
parent 09cdac09a1
commit 4cd98c53a0
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Frequent-Questions.md

@ -15,7 +15,7 @@ These are frequent questions about Gravity Sync implementations. In addition to
### How come you don't support DHCP syncing?
- If I’m being honest, it’s because I don’t use Pi-hole for DHCP in my own environment and it’s hard for me to support something I’m not actively using. This is the same reason why it took me until version 3.1 to get around to making Docker work properly.
- I’ve also not been confident in my ability to make it work reliability. I find DNS settings change so infrequently in most environments that even polling the sync every 15 minutes is probably overkill. DHCP device leases tend to be a lot more fluid. It’s not just a matter of taking this entire database from this side and putting it over here instead, if a device gets a lease from one server or the other then it disappears.
- I’ve also not been confident in my ability to make it work reliability. I find DNS settings change so infrequently in most environments that even polling the sync every 15 minutes is probably overkill. DHCP device leases tend to be a lot more fluid. It’s not just a matter of taking this entire database from this side and putting it over here instead, if a device gets a lease from one server or the other then it disappears, problems arise. This also doesn't even begin to get into the dynamic DNS addresses that the devices register.
### Do you support DietPi, Unraid, LXD, Something Else?