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 System Requirements (markdown)

Michael Stanclift 2021-04-06 16:17:32 -05:00
parent 69d931e330
commit c07224a7be
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
System-Requirements.md

@ -14,6 +14,12 @@ The main requirement is Gravity Sync requires at least two separate Pi-hole 5.x
- Only the [official Pi-hole Docker image](https://hub.docker.com/r/pihole/pihole) is supported. - Only the [official Pi-hole Docker image](https://hub.docker.com/r/pihole/pihole) is supported.
- In addition to the officially supported Linux distributions as outlined above, when using a container engine, host OS deployments on more container oriented distributions such as [VMware Photon OS](https://vmware.github.io/photon/) may be used, so long as they’re able to run the Gravity Sync specific requirements below. - In addition to the officially supported Linux distributions as outlined above, when using a container engine, host OS deployments on more container oriented distributions such as [VMware Photon OS](https://vmware.github.io/photon/) may be used, so long as they’re able to run the Gravity Sync specific requirements below.
### Storage Performance
Pi-hole on its own can be abusive to SD card installs on a Raspberry Pi, due to its constant writes of logging to the disk. Gravity Sync introduces some additional storage overhead to a traditional Pi-hole environment. The replication process of the Domain Database involves performing an MD5 hash of the running database, taking a backup of the running configuration, performing an SQL integrity check, transferring it across the network to a secondary Pi-hole where it is then hashed again after it's put into production to make sure the process completed successfully. Larger databases will also increase the time and increase the risk of failed replication.
It is suggested, that you place your Pi-hole instance on resilient, well performing storage media. If you have failed or inconsistent Gravity Sync replication sessions, this is often the root cause.
## Required Components ## Required Components
The installer will perform checks to make sure the required components to use Gravity Sync (such as OpenSSH, etc) are available on both the primary and secondary Pi-hole during installation. The installer will perform checks to make sure the required components to use Gravity Sync (such as OpenSSH, etc) are available on both the primary and secondary Pi-hole during installation.