mirror of
https://github.com/vmstan/gravity-sync.git
synced 2024-08-30 18:22:11 +00:00
41ecce4b5a
* 4.0.0
* drop .sh
* chmod +x
* change pull locations
* push
* change folders
* cleanup extensions
* error with cname push
* backup purge redone
* back to the CORE!
* remove references to backup folder
* rename pihole container image variable
* rename pihole binary variables
* rename docker binary variables
* rename pihole dir variables
* data names
* remote and local
* DNSMASQ folders
* remove dnsmasq
* more variable renames
* fix config location
* fix import path
* validate gs folder fix
* remove references to LOCAL_FOLDR
* updater moving into place
* create update script
* "
* change context?
* remove git check
* add ( back
* Fix automation path
* replace standalone SQLite with FTL
* remote
* adjust docker folder locations
* fix remote location
* remove sqlite validation
* remove all references to cron
* config rewrite
* soruce config file
* remote file not dir
* hidden figures
* config file
* remove references to dropbear
* remove backup cleanup from most tasks
* remove gs folder validation
* remove ssh detection
* static set ssh
* id_rsa
* extra line
* echo lines
* retain previous config file
* isolinear
* ∞
* rearrange info
* remove bash path
* check replication status
* check timer instead
* dev mode against new repo location
* rewrite purge
* path
* add default file owner back
* simpler
* /usr/bin/bash
* fix ftl binary location
* whoami
* remote FTL
* don't delete from remote
* purge it
* remove path not name
* sudo tee
* tee off instead of echo out
* sudo sudo sudo
* sudo all the things
* Even more sudo
* how much more can you sudo
* change keyfile permissions
* remote/local
* all the sudo
* sudo in your rsync
* pull to tmp
* sudo copied
* silence tee
* New keyfile creation method
* send hash to the other side
* saving hashes
* directions are hard
* reverse hash for the other side
* remote ping test from config
* further randomize replication times
* rerandom
* fix bash call to update.sh
* Remove now-unused UI code
* remove legacy distro check code
* UI FILE PERMISSION spelling
* read -r
* GS_INTENT_VALIDATE
* remove intent validation from push
* cleanup tasks
* remove cname opt-out
* remove DNS options
* rename validation and set functions
* import_gs
* replace primary/local
* relocate file owner variables
* set variable for /tmp
* just set file permissions don't bother checking
* set file permissions
* remove extra message
* md5 variable renames
* replacing pri/sec variable names in smart sync
* .gsbackup replaced
* cleanup then
* removing compensation
* More primary and secondary references removed
* README update
* Update README.md
* new md5 variable
* multiple md5 hash logs
* gravity db listed twice
* md52 deletion at remote
* rename on sync
* move after send
* try try again
* this should work
* force it
* now for something completely different
* remove ;
* KISS
* KISS2
* fix hashing lookups
* set remote hash permissions
* vary info output
* remove unused functions
* new docs uploaded for publishing to wiki
* new system requirements
* words
* host
* rewrite install instructions
* rewrite install instructions
* rewrite all the thing
* massive variable renames
* building out dockerfile
* switch to photon
* change all if then style to single line
* cd || exit
* reformat math
* ${SSHPASSWORD} references removed
* OS_SSH_CMD set in variables
* cleanup function calls
* remove old root_check function
* cleaning up more variables
* more variable cleanup
* Line
* rewrite all of pihole detection
* echo_good
* >/dev/null 2>&1
* detecting local message
* sed?
* | sed 's/\s.*$//'
* fix sed
* no more whiches
* 2>/dev/null some more
* massive config rewrite for advanced workflow
* fix prompt
* output remote images
* echo again
* remote again
* cats?
* detect container locations
* fix space
* rewrite remote detection
* remote not local
* don't delete remote
* exec then rsync
* move lines
* enclose
* dont var
* daft
* quotes
* remove variable
* run you booger
* REMOTE
* remove echo_lines
* no config for more commands
* no config again
* shellcheck
* comment cleanup
* spell check is wonderful
* change docker container name output
* escape more quotes
* simpler command for remote side
* scape that?
* maybe less, i dunno
* try both lists again
* change spacing and line breaks
* streamline status icons for configuration
* retrieving remote settings
* error_validate
* disable task
* fix disable task
* detect_gs_peer
* task_purge doesn't use config
* remote message
* fallback
* " "
* comments
* add monitor mode
* Adds .sh script back as upgrader
* upgrader in old script
* reverse logic
* pretty upgrade script
* migration complete
* change template directory
* check for crontab hash
* user not host
* silence hash for crontab check
* warn
* warning
* reword config ending
* missing "
* os-release
* blue
* disable automation doesn't require config
* move stop
* signing off on 4.0
|
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| templates | ||
| .gitignore | ||
| Dockerfile | ||
| gravity-sync | ||
| gravity-sync.sh | ||
| LICENSE | ||
| README.md | ||
| update.sh | ||
| VERSION | ||
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 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 resolver settings, which includes:
- Adlist 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.
- Local DNS Records.
- Local CNAME Records.
Limitations
Gravity Sync will not:
- 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
- Review System Requirements
- Install Gravity Sync
- Configure Gravity Sync
- Execute Gravity Sync
- 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: