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
772 Commits 2 Branches 86 Tags 1.6 MiB
Shell 99.8%
Dockerfile 0.2%
ad783f1385
Go to file
Michael Stanclift ad783f1385
4.0.5 (#400) 
* Simple fix for podman to work; whitespace clean up (#396)

* Fix set_pihole_exec to match full container names (#390)

Fix set_pihole_exec to match full container names, rather
than their substrings, by adding begin and end anchors to
the 'docker ps -qf name=PATTERN' being used.

Signed-off-by: William Blew <william@kulian.org>

* Fix the detect_xxx_pihole routines. (#389)

Fix the detect_xxx_pihole routines to respect the configurable
PIHOLE_CONTAINER_IMAGE variable.

The ghcr.io/pi-hole/pihole image is also released by the Pi-hole
project, just as the pihole/pihole image.

This commit enables ghcr.io image usage by adding the following
to the /etc/gravity-sync.conf file:

PIHOLE_CONTAINER_IMAGE='ghcr.io/pi-hole/pihole'

Signed-off-by: William Blew <william@kulian.org>
Co-authored-by: Michael Stanclift <mx@vmstan.com>

* Make check for sudo privileges more accurate (#375)

* Make check for sudo privileges more accurate

The existing method of checking if the Gravity Sync user has sudo rights is flawed, in that it will break if the user is not in the `sudo` group (on Debian based distros) or the `wheel` group (on CentOS/RHEL distros).

A more accurate way of checking if a user has sudo privileges is using `sudo --validate` or `sudo -n true`; both of which return `0` if the user has sudo privileges.

This commit updates the `validate_sudo_status` function to use `sudo --validate` so that Gravity Sync is actually checking if a user has sudo privileges, rather than just checking group memberships.

* Fix bug in patch

---------

Co-authored-by: llamalump <29816026+llamalump@users.noreply.github.com>

* Fix: GS_SSH_PORT can be changed now via  'gravity-sync config <NEW_PORT>' when already set in gravity-sync.conf. Fix: Initial sync of static DHCP and CNAME to 'empty pihole' now works. Enhancement: Various settings now settable via ENV vars (for Docker) (#384)

* SSH custom port: Fixed bug, where GS_SSH_PORT is overwritten by gravity-sync.conf (if set) when calling 'gravity-sync config NEW_SSH_PORT'. Docker enhancements: Made many config-variables settable via ENV vars

* Fixing initial push of CNAME and Static DHCP entries to an 'empty' remote (fixes https://github.com/vmstan/gravity-sync/issues/377)

* Removing unecessary 'export' keyword

* Fixed 'md5_recheck' for the bug https://github.com/vmstan/gravity-sync/issues/377

* Adding ENV documentation

* Fixing typo

* Fixed type and nicely formatted tables with emacs

---------

Co-authored-by: Michael Stanclift <mx@vmstan.com>

* Update VERSION

* Update gravity-sync

---------

Signed-off-by: William Blew <william@kulian.org>
Co-authored-by: Matt Woodson <mwoodson@gmail.com>
Co-authored-by: William Blew <william@kulian.org>
Co-authored-by: Seb Thomson <29816026+rst-ack@users.noreply.github.com>
Co-authored-by: llamalump <29816026+llamalump@users.noreply.github.com>
Co-authored-by: Klaus Zipfel <30482165+systemofapwne@users.noreply.github.com>
2023-07-10 11:46:11 -05:00
.github Create FUNDING.yml 2022-04-14 12:39:47 -05:00
templates 4.0.0 (#317) 2022-04-11 17:06:09 -05:00
.gitignore 4.0.0 (#317) 2022-04-11 17:06:09 -05:00
Dockerfile 4.0.0 (#317) 2022-04-11 17:06:09 -05:00
ENV.md 4.0.5 (#400) 2023-07-10 11:46:11 -05:00
gravity-sync 4.0.5 (#400) 2023-07-10 11:46:11 -05:00
gravity-sync.sh 4.0.3 (#341) 2022-04-29 09:56:28 -05:00
LICENSE Initial commit 2020-05-21 12:57:19 -05:00
README.md 4.0.4 (#343) 2022-05-03 10:50:05 -05:00
update.sh 4.0.0 (#317) 2022-04-11 17:06:09 -05:00
VERSION 4.0.5 (#400) 2023-07-10 11:46:11 -05:00

README.md

Gravity Sync

Gravity Sync

Find out what's new in version 4.0!

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 redundant 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. Setup should only take a few minutes.

Features

Gravity Sync replicates the core of Pi-hole's ad/telemetry blocking settings, which includes:

  • Adlist settings with status and comments.
  • Domain/RegEx whitelists and blacklist along with status and comments.
  • Clients and group assignments, along with status and descriptions.

Gravity Sync also replicates local network DNS/DHCP settings, which includes:

  • Local DNS Records.
  • Local CNAME Records.
  • Static DHCP Assignments.

Limitations

Gravity Sync will not:

  • Modify or sync the individual Pi-hole's upstream DNS resolvers.
  • Merge query logs, statistics, long-term data, caches, or other resolution information.
  • Sync individual Pi-hole DHCP scoping information or leases.

Setup Steps

  1. Review System Requirements
  2. Install Gravity Sync
  3. Configure Gravity Sync
  4. Execute Gravity Sync
  5. Automate Gravity Sync

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: