Wekan helm chart: which hostnames should go into "endpoint" and "ingress.hosts"?

[xet7]

Moved to here from https://github.com/wekan/wekan/discussions/5026

From @johanneskastl

Hi all,

I just installed wekan using the helm chart. And I am not sure if the UI displays properly, e.g. the dropdwon-menu on the right (for the current user) has strange names for the entries).

In addition, my Firefox umatrix plugin states that some resources are being loaded from wekan.local instead of the FQDN that I set in my values.yaml.

endpoint: wekan.example.org
ingress:
  enabled: false
  hosts: [ "wekan.example.org"]

(The ingress is disabled, as I am providing my own ingressroutes via Traefik, but that should not matter here)

Should wekan.local be included in the endpoint, as it seems to be used internally? I tested it, it did not improve the UI glitches but I noticed no additional breakage. So I would omit it (as it will not resolve anyway)

Thanks in advance, Johannes

@Nightreaver @szechp @jadams @salleman33 @jehutyy @luclu @varac

Do you know about this?

Or is this related to environment variables ROOT_URL and PORT https://github.com/wekan/wekan/wiki/Settings https://github.com/wekan/wekan/issues/4932 ?

[Nightreaver]

I think you have to set it in 3 places (values.yaml):

endpoint: wekan.example.org
root_url: https://wekan.example.org

ingress:
  enabled: true
  path: /
  pathtype: ImplementationSpecific
  hosts: [ wekan.example.org ]

[johanneskastl]

Thanks for the answer. Unfortunately root_url is not mentioned in the values.yaml at all, so I am not sure how a user should know this?

https://github.com/search?q=repo%3Awekan%2Fcharts%20root_url&type=code

I would prepare a PR to add this to the values.yaml and remove the default value from the deployment.yaml to address this?

[johanneskastl]

I just tested this, and setting root_url really solves the "broken" UI. I also see no more warnings from uMatrix regarding wekan.local.