Cutlery/gravity-sync
1
0
Fork 0
mirror of https://github.com/vmstan/gravity-sync.git synced 2025-08-05 08:39:48 -04:00
Code Issues Packages Projects Releases Wiki Activity

Updated System Requirements (markdown)

Michael Stanclift 2021-02-12 10:17:24 -06:00
parent b9b368927f
commit 5709e77db5
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
System-Requirements.md

@ -6,12 +6,17 @@ The main requirement is Gravity Sync requires two at least separate Pi-hole 5.0
- If you're not using the `root` account, make sure that the account is a member of either the `sudo` or `wheel` group on both the primary and secondary Pi-hole. Most of the pre-built images available for the Raspberry Pi already have this configured, as does Ubuntu.
- During installation, this non-root user will be given [passwordless sudo](https://linuxize.com/post/how-to-run-sudo-command-without-password/) permissions to the system.
#### Docker Pi-hole Installs
#### Docker Pi-hole
- As of Gravity Sync 3.1, your Pi-hole installs can be a Docker container deployment.
- 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.
#### Podman Containers
- As of Gravity Sync 3.3, beta support for Podman as a container engine has been introduced.
- The same restrictions as above for Docker, apply to Podman.
### 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. If they are missing you will have an opportunity to use whatever package manager is available on your system to correct the missing dependencies.