gravity-sync/README.md

# Gravity Sync

For more information visit [https://vmstan.com/gravity-sync/](https://vmstan.com/gravity-sync/)

The scripts assumes you have one "master" Pihole as the primary place you make all your configuration changes, such as whitelist, blacklist, group management, and blocklist settings. After the script executes it will copy the gravity.db from the master to any secondary nodes you configure it to run on.

### Prereqs

You will need to make sure your secondary Pihole is setup to authenticate to your primary Pihole via certificates. 

```
ssh-keygen -t rsa
ssh-copy-id -i ~/.ssh/id_rsa.pub USERNAME@PRIMARYPI
```

### Installation

From your *secondary* Pi, login via SSH and copy the gravity-sync.sh script to your user. In this example we will use git to keep the latest copy of the script on your server.

```
cd ~
git clone https://github.com/vmstan/gravity-sync.git
cd gravity-sync
```

Please note the script **must** be run from a folder in your user home directory (ex: /home/pi/gravity-sync)

### Configuration

After you clone the base configuration, you will need to create a configuration file called `gravity-sync.conf` in the same folder.

```
vim gravity-sync.conf
```

If you don't like VIM, use NANO or your text editor of choice.

Paste the following into your file, making sure to change the IP (or DNS name) and user account to authenticate to the master Pi.

```
REMOTE_HOST='192.168.7.5'
REMOTE_USER='pi'
```

Now test the script. I suggest making a subtle change to a whitelist/blacklist on your primary Pihole, such as a description field, and then seeing if the change propagates to your secondary.

```
./gravity-sync.sh pull
```

If you do a `git pull` while in this directory you should update to the latest copy of the script. Your changes to the .conf file, logs and backups should be uneffected by this.