The script failed for me when I initially ran it and needed to reprovision the UDM. Hopefully, this saves someone else the headache of the script failing.
* AdGuardHome: fix order of operations
Fix the initial order of operations that causes initial setup issues.
fixes#107.
* AdGuardHome: clean up some info with formatting
* AdGuardHome: add troubleshooting info
Hopefully this will help folks in #107 solve their issues.
* 10-dns: always write out the symlinks
Skip spitting an error about the fact that the symlinks already exist.
Just write them anyway.
* Store install-cni-plugins.sh once
* Newlines in on-boot-script
* Update example on_boot.sh for directory
* Update README.md examples
* Store 20-dns.conflist once
* Add modularized nextdns config w/IPv6 support
* Make nextdns script more generic
* Use common setup script for each dns service
* Add missing newlines
* Readme updates and ipv6 support
* Readme updates and ipv6 support
* Final updates and Ipv6
Co-authored-by: exodious <exodious@users.noreply.github.com>
The docker creation points to adguardhome and is case sensitive. So either changing the docker example or this line will allow the script to launch adguard on boot successfully.
