Go to file
Aleksey Dmitrevskiy ceaa1e4ebf [fix] control: fix json decode for upstream config 2019-03-06 15:35:22 +03:00
client * client: upstream form 2019-03-06 14:45:21 +03:00
dhcpd * use new logger - AdguardTeam/golibs/log 2019-02-27 15:02:11 +03:00
dnsfilter [change] control: Handle upstream config with JSON 2019-02-28 13:01:41 +03:00
dnsforward [change] dnsforward: Add comments for public fields 2019-02-28 13:40:40 +03:00
openapi [change] control, openapi: Handle upstreams test with JSON 2019-03-05 12:29:52 +03:00
scripts Added Traditional Chinese 2019-01-04 21:22:22 +03:00
.codecov.yml Added codecov, goreport 2019-01-25 20:13:57 +03:00
.gitattributes fix gh language 2018-10-17 13:14:45 +03:00
.gitignore add temporary packr output to gitignore 2019-02-15 16:28:28 +03:00
.golangci.yml ingnore Shutdown by golangci 2019-02-07 13:52:14 +03:00
.gometalinter.json Fix review comments 2019-02-11 14:22:36 +03:00
.travis.yml Fix docker build 2019-02-25 19:15:27 +03:00
Dockerfile Add exposed ports 2019-02-12 11:54:40 +03:00
Dockerfile.travis Add exposed ports 2019-02-12 11:54:40 +03:00
LICENSE.txt Initial commit 2018-08-30 17:25:33 +03:00
Makefile Makefile -- no need for go get -d . anymore 2019-02-07 18:24:42 +03:00
README.md Added guides to readme 2019-02-24 20:13:58 +03:00
app.go * use new logger - AdguardTeam/golibs/log 2019-02-27 15:02:11 +03:00
build_docker.sh Build latest from tag branch, edge from master 2019-02-11 15:10:36 +03:00
config.go Merge branch 'fix/542' into fix/596 2019-02-28 11:16:03 +03:00
control.go [fix] control: fix json decode for upstream config 2019-03-06 15:35:22 +03:00
dhcp.go pointer is unuseful for httpError func 2019-02-27 16:50:19 +03:00
dns.go Merge branch 'fix/542' into fix/596 2019-02-28 11:16:03 +03:00
filter.go * use new logger - AdguardTeam/golibs/log 2019-02-27 15:02:11 +03:00
go.mod * use dnsproxy v0.11.2 2019-02-27 18:28:09 +03:00
go.sum * use dnsproxy v0.11.2 2019-02-27 18:28:09 +03:00
helpers.go Added install methods to openapi.yaml 2019-02-22 17:59:42 +03:00
helpers_test.go * use new logger - AdguardTeam/golibs/log 2019-02-27 15:02:11 +03:00
i18n.go * use new logger - AdguardTeam/golibs/log 2019-02-27 15:02:11 +03:00
issue_template.md Fix some UI issues, rename DNS->Home 2018-10-14 17:49:07 +03:00
release.sh Bump version to v0.93 2019-02-25 19:04:41 +03:00
service.go * use new logger - AdguardTeam/golibs/log 2019-02-27 15:02:11 +03:00
syslog_others.go service properties to constants 2019-02-05 14:21:07 +03:00
syslog_windows.go service properties to constants 2019-02-05 14:21:07 +03:00
upgrade.go Merge branch 'master' into fix/542 2019-02-27 18:47:01 +03:00
upgrade_test.go [change] upgrade_test: rework tests 2019-03-01 11:27:15 +03:00
version.json Bump version to v0.93 2019-02-25 19:04:41 +03:00

README.md

 

AdGuard Home

Privacy protection center for you and your devices

Free and open source, powerful network-wide ads & trackers blocking DNS server.

AdGuard.com | Wiki | Reddit | Twitter | Telegram

Build status Code Coverage Go Report Card GolangCI Latest release



AdGuard Home is a network-wide software for blocking ads & tracking. After you set it up, it'll cover ALL your home devices, and you don't need any client-side software for that.

It operates as a DNS server that re-routes tracking domains to a "black hole," thus preventing your devices from connecting to those servers. It's based on software we use for our public AdGuard DNS servers -- both share a lot of common code.

Getting Started

Please read the Getting Started article on our Wiki to learn how to install AdGuard Home, and how to configure your devices to use it.

Alternatively, you can use our official Docker image.

Guides

How to build from source

Prerequisites

You will need:

You can either install it via the provided links or use brew.sh if you're on Mac:

brew install go node

Building

Open Terminal and execute these commands:

git clone https://github.com/AdguardTeam/AdGuardHome
cd AdGuardHome
make

Contributing

You are welcome to fork this repository, make your changes and submit a pull request — https://github.com/AdguardTeam/AdGuardHome/pulls

How to update translations

If you want to help with AdGuard Home translations, please learn more about translating AdGuard products here: https://kb.adguard.com/en/general/adguard-translations

Here is a direct link to AdGuard Home project: http://translate.adguard.com/collaboration/project?id=153384

Before updating translations you need to install dependencies:

cd scripts/translations
npm install

Create file oneskyapp.json in scripts/translations folder.

Example of oneskyapp.json

{
    "url": "https://platform.api.onesky.io/1/projects/",
    "projectId": <PROJECT ID>,
    "apiKey": <API KEY>,
    "secretKey": <SECRET KEY>
}

Upload translations

node upload.js

Download translations

node download.js

Reporting issues

If you run into any problem or have a suggestion, head to this page and click on the New issue button.

Acknowledgments

This software wouldn't have been possible without:

You might have seen that CoreDNS was mentioned here before — we've stopped using it in AdGuardHome. While we still use it on our servers for AdGuard DNS service, it seemed like an overkill for Home as it impeded with Home features that we plan to implement.

For a full list of all node.js packages in use, please take a look at client/package.json file.