-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add AdGuard Home docs #515
Conversation
DietPi-Software | AdGuard Home - add new software title
DietPi-Software | AdGuard Home - add new software title
small correction
I'll merge it, so we can prepare a dev => master PR. |
I need to revert my statement a little bit. It seems there is an automatic update function. However it's not working with our implementation as the updater expect the executable on same directory as the config file
🙄 |
Oh, that is bad. I guess it expects it to be located in the working directory then, as this is all that we change. Strange that the related CLI option exists, when it expectedly breaks the updater 🤔. Probably something we should report to AdGuard guys, to derive the install dir form the location of the currently running executable, rather than assuming that it's located in the working directory. Not sure how to deal with this for our release. Leave everything in |
basically we would have 3 option
Currently AGH devs are working on v0.107 and it might be released short after our release. Means, we will have user reporting issues using the internal update function right after. For the time being, we could go with option 1, as this is similar to using AGH installation method and in parallel check with AGH developer if this intended or if they plan to split working dir from running executable. I mean you are right, using |
DietPi-Software | AdGuard Home - add new software title