Mirrored_Repos/gravity-sync
1
0
Fork 0
mirror of https://github.com/vmstan/gravity-sync.git synced 2024-08-30 18:22:11 +00:00
Code Issues Packages Projects Releases Wiki Activity
752 Commits 2 Branches 86 Tags 1.6 MiB
Shell 99.8%
Dockerfile 0.2%
3a125a2e30
Go to file
Michael Stanclift 3a125a2e30
3.5.0 (#296) 
* Fixed typo (#269)

* Fix cache wipe (#282)

* Update gs-pull.sh

`restartdns          Full restart Pi-hole subsystems
                        Add 'reload' to update the lists and flush the cache without restarting the DNS server
                        Add 'reload-lists' to only update the lists WITHOUT flushing the cache or restarting the DNS server`
fixing typo

* Update gs-push.sh

fixing typo

* Update VERSION

* Update gravity-sync.sh

* new version

* Clear backup directory

* Cleanup after updating

* remove backup functions

* Remove reference to backup and restore functions

* Change backup references to copy

* Host

* Remove reference to backup retention

* Remove reference to backup retention

Co-authored-by: Philippe Ouellette <philippeouellette@protonmail.com>
Co-authored-by: djschnei21 <32646250+djschnei21@users.noreply.github.com>
2022-02-25 12:25:57 -06:00
.github/ISSUE_TEMPLATE Update bug_report.md 2021-02-05 22:24:20 -06:00
backup 3.3.1 (#164) 2021-02-13 21:11:43 -06:00
includes 3.5.0 (#296) 2022-02-25 12:25:57 -06:00
logs 3.3.1 (#164) 2021-02-13 21:11:43 -06:00
prep 3.3.0 (#161) 2021-02-09 16:05:17 -06:00
settings 3.3.1 (#164) 2021-02-13 21:11:43 -06:00
templates 3.5.0 (#296) 2022-02-25 12:25:57 -06:00
.gitignore 3.5.0 (#296) 2022-02-25 12:25:57 -06:00
gravity-sync.sh 3.5.0 (#296) 2022-02-25 12:25:57 -06:00
LICENSE Initial commit 2020-05-21 12:57:19 -05:00
README.md 3.3.3 is 3.4.0 (#185) 2021-04-01 15:16:20 -05:00
VERSION 3.5.0 (#296) 2022-02-25 12:25:57 -06:00

README.md

Gravity Sync

Gravity Sync

What is better than a Pi-hole blocking trackers, advertisements, and other malicious domains on your network? That's right, two Pi-hole blocking all that junk on your network!

But if you have more than one Pi-hole in your network you'll want a simple way to keep the list configurations and local DNS settings identical between the two. That's where Gravity Sync comes in. With proper preparation, it should only take a few minutes to install. Ideally you setup Gravity Sync and forget about it -- and in the long term, it would be awesome if the Pi-hole team made this entire script unnecessary.

Features

Gravity Sync replicates the Pi-hole Domain Database (gravity.db), which includes:

  • Blocklist settings with status and comments.
  • Domain whitelist and blacklist along with status with comments.
  • Custom RegEx whitelist and blacklists.
  • Clients and groups along with any list assignments.

Gravity Sync can also (optionally) replicate the Local DNS Records and CNAMEs configuration files.

Limitations

Gravity Sync will not:

  • Overwrite device specific Pi-hole settings specific to the local network configuration.
  • Change the Pi-hole admin/API passwords, nor does not leverage these at all.
  • Modify the individual Pi-hole's upstream DNS resolvers.
  • Sync DHCP settings or monitor device leases.
  • Merge long term data, query logs, or statistics.

Setup Steps

  1. Review System Requirements
  2. Prepare Your Pi-hole
  3. Install Gravity Sync (or Upgrade)
  4. Configure Gravity Sync
  5. Execute Gravity Sync
  6. Automate Gravity Sync
  7. Profit

Disclaimer

Gravity Sync is not developed by or affiliated with the Pi-hole project. This is project an unofficial, community effort, that seeks to implement replication (which is currently not a part of the core Pi-hole product) in a way that provides stability and value to Pi-hole users. The code has been tested across multiple user environments but there always is an element of risk involved with running any arbitrary software you find on the Internet.

Pi-hole is and the Pi-hole logo are registered trademarks of Pi-hole LLC.

Additional Documentation

Please refer to the Wiki for more information: