I wasted hours this week because the fix as available in 0.20.4 did not work properly. Finally found this issue again and the exact same solution above (https://wiki.postgresql.org/wiki/Fixing_Seq…
As for https, I guess you could check whether annotations.kubernetes.io/tls-acme is truish
So either adjust the template or this comment: https://kolaente.dev/vikunja/helm-chart/src/branch/main/values.yaml#L100
it would be elegant to be able to just set the domain once without all the ingress baggage as discussed in vikunja/helm-chart#10
failed to create resource: admission webhook "validate.nginx.ingress.kubernetes.io" denied the request: host "do-test.ftt.gmbh" and path "/" is already defined in ingress stackspout/vikunja-test-…
Here it is: https://open.greenhost.net/xeruf/stackspout/-/blob/main/basic/apps/do-test/vikunja-values-configmap.yaml?ref_type=heads But it looks like something is moving forward now...
I just moved it up because specifying API config options is one of the first things you usually want to do, and made the text more understandable and compact.
proxy-body-size is set to 0 to remove the body limit on file uploads
should we really remove the limit completely? Shouldn't we set something lavish like 50MB?
And we should document how to set the domain for ingress, as that is a very common task. I think it should be this?
frontend:
image:
tag: unstable
…