micw
micw
@joedragons Hello. If possible, please include this PR in the same nexus release as PR #31 (in 3.14 release?) so that the release has a consistent API. Regards, Michael.
@joedragons could you please look into this which is a follow-up to complete what was started in #31?
@joedragons Any news about this? Thank you, Michael.
I added myself too. Would like to support any progress to https://github.com/Mailu/helm-charts but got no time in the last months :-/
If you play around with it, please consider to use the yamls based on the helm chart (https://github.com/Mailu/helm-charts/tree/gh-pages/yaml/)
Hello, I do not exactly understand the purpose of this PR. If you want dynamic address resolution (which absolutely makes sense), just set `*_ADDRESS` raher than `HOST_*` - that's it....
Hello, you are right, the HOST_* brings a lot of issues (that's why I added *_ADDRESS and use it in the k8s helm chart). There had been reasons to keep...
I have read through the PR. What bothers me is that this is a breaking change that would instantly make a lot of installations fail as soon as a new...
In discussion we found another objection. At the moment, hostnames are resolved at system level, so service names and full qualified hostnames are both OK. With the change, we always...