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-09-29 16:13:39 -05:00
parent 008b0f4e22
commit 3bd6f907a9
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
System-Requirements.md

@ -9,7 +9,7 @@ The main requirement is Gravity Sync requires at least two separate Pi-hole 5.x
### Containerized Pi-hole
- Your Pi-hole installs can be a Docker container deployment as of Gravity Sync 3.1.
- Beta support for Podman as a container engine has been introduced starting in Gravity Sync 3.3.
- Support for Podman as a container engine has been introduced starting in Gravity Sync 3.3.
- Gravity Sync will run directly on the host OS, and not inside of the container image.
- 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.
@ -55,6 +55,12 @@ apt update && apt install sqlite3 sudo git rsync ssh
dnf install sqlite3 sudo git cronie rsync ssh
```
### Photon OS
```
tdnf install sqlite3 sudo git cronie rsync ssh
```
## Pi-hole Architecture
You will need to designate one Pi-Hole as primary and at least one as secondary.