bugclerk
bd1a704013
Upgraded catalog item(s) (#3091)
|
hai 6 meses | |
|---|---|---|
| .. | ||
| charts | hai 1 ano | |
| ci | %!s(int64=2) %!d(string=hai) anos | |
| migrations | %!s(int64=2) %!d(string=hai) anos | |
| templates | %!s(int64=2) %!d(string=hai) anos | |
| Chart.lock | hai 1 ano | |
| Chart.yaml | hai 6 meses | |
| README.md | %!s(int64=2) %!d(string=hai) anos | |
| app-readme.md | %!s(int64=2) %!d(string=hai) anos | |
| item.yaml | hai 1 ano | |
| metadata.yaml | %!s(int64=2) %!d(string=hai) anos | |
| questions.yaml | hai 1 ano | |
| upgrade_info.json | %!s(int64=2) %!d(string=hai) anos | |
| upgrade_strategy | %!s(int64=2) %!d(string=hai) anos | |
| values.yaml | hai 6 meses | |
README.md
AdGuard Home
During the setup wizard, AdGuard Home presents an option to select on which port the web interface will be available. (Defaults to 80. Which is a privileged port and also usually the TrueNAS SCALE UI uses that port) Because of that, App will force the webUI to listen to port 30000 (or the port selected by user in the TrueNAS SCALE UI).
If you select a different port in the wizard, the Dashboard will not work initially but after a couple of minutes container will automatically restart and the Dashboard will be available on the port you selected on the TrueNAS SCALE UI.
- AdGuard runs as
rootuser.- AdGuard runs with host networking enabled.