atoy3731/adguard-sync
1
1
Fork 0
mirror of https://github.com/atoy3731/adguard-sync.git synced 2024-09-20 15:06:02 +08:00
Code Issues Packages Projects Releases Wiki Activity
Sync tool for local Adguard Home DNS instances
8 commits 4 branches 4 tags 83 KiB
Python 98.7%
Dockerfile 1.3%
Go to file
Adam Toy fdf62b3296 fix entrypoint
2021-01-31 13:02:39 -05:00
.github/workflows Fix 2021-01-31 12:56:25 -05:00
src Directory updates 2021-01-31 12:54:33 -05:00
.gitignore first commit 2021-01-31 12:46:48 -05:00
docker-compose.yaml first commit 2021-01-31 12:46:48 -05:00
Dockerfile fix entrypoint 2021-01-31 13:02:39 -05:00
LICENSE Create LICENSE 2021-01-31 12:51:28 -05:00
README.md Add badge 2021-01-31 12:58:59 -05:00
requirements.txt Directory updates 2021-01-31 12:54:33 -05:00
VERSION first commit 2021-01-31 12:46:48 -05:00

README.md

AdGuard Sync

Docker

This project will sync entries between two Primary and Secondary AdGuard Home instances using the API.

This is useful if you're dependent on local DNS and want to ensure relative High Availability.

How to Run

AdGuard Sync is packaged as a Docker image and can be ran anywhere with access to your instances. You can update the docker-compose.yaml file with your values based on the following:

Variable Required Description Default
ADGUARD_PRIMARY Yes Primary base URL for the primary AdGuard instance (Ie. http://dns01.example.com) N/A
ADGUARD_SECONDARY Yes Secondary base URL for the primary AdGuard instance (Ie. http://dns02.example.com) N/A
ADGUARD_USER Yes Username to log into your AdGuard instances. N/A
ADGUARD_PASS Yes Password to log into your AdGuard instances. N/A
SECONDARY_ADGUARD_USER No Username to log into your secondary AdGuard instance. Only necessary if credentials are different between primary and secondary Value of 'ADGUARD_USER'
SECONDARY_ADGUARD_PASS No Password to log into your secondary AdGuard instance. Only necessary if credentials are different between primary and secondary Value of 'ADGUARD_PASSWORD'
REFRESH_INTERVAL_SECS No Frequency in seconds to refresh entries. 60

Once you've updated the file and ensure you have docker and docker-compose installed, run the following in the root directory:

docker-compose up -d

You can check on the status of your newly running pod with:

docker-compose logs

NOTE: The container is set to automatically restart when the docker daemon restarts.