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

Created Frequent Questions (markdown)

Michael Stanclift 2020-10-21 13:33:37 -05:00
parent deffb97f46
commit 5fbda7f878
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
Frequent-Questions.md Normal file

@ -0,0 +1,19 @@
These are frequent questions about Gravity Sync implementations. In addition to any known issues outlined here, please review the [GitHub Issues](https://github.com/vmstan/gravity-sync/issues) page for real time user submitted bugs, enhancements or active/past discussions.
### Do you support DietPi, Unraid, LXD, Something Else?
- Yes and no.
- Gravity Sync is designed to work on Linux systems that the main Pi-hole project [is designed to work on](https://docs.pi-hole.net/main/prerequisites/#supported-operating-systems). This is what I test the code against.
- It is possible for Pi-hole to run on systems other than those listed on their project page. Chances are if Pi-hole will run on it, so will Gravity Sync. However, it's impossible for me to test every possible configuration, so if you run into issues you may be on your own unless they can either be replicated on a supported install or generate enough concern to address.
- Specifically to DietPi, yes Gravity Sync will work, but you must enable OpenSSH instead of the default Dropbear server. (Dropbear was supported for a time in older releases of Gravity Sync, but was problematic.)
### Can Gravity Sync run inside of a Docker container?
- No.
- Gravity Sync is designed to work with Docker deployments of Pi-hole, but it is expected that Gravity Sync itself will run on the container host operating system. It is a bash script that needs access to the commands and components of the host OS filesystem.
### Can I sync to a Pi-hole server in AWS? (or another cloud provider)
- Yes.
- Gravity Sync just needs to be able to connect to the remote server via SSH (port 22 by default) -- if you have a Pi-hole running within your LAN, and one in the public cloud, then the easiest way is to install Gravity Sync on the LAN based Pi-hole and use it to `push` the configuration out to the cloud based instance. The cloud instance will likely have it's own public IP address, with access to SSH already enabled.
- The alternative would be to put Gravity Sync on your cloud instance and use it to `pull` the configuration over, but this would require you to open the SSH port on your local firewall and then NAT this traffic to your internal Pi-hole device.