studio/docs - docs - Gitea: Git with a cup of tea

studio/docs

Archived

Fork 0

Commit Graph

Author	SHA1	Message	Date
Richard Jones	f2e54308d2	🐛(helm) charts generate invalid YAML for collaboration API / WS Closes #890 Remove the service blocks outside the conditionals in the collaboration API and WS templates. Signed-off-by: Richard Jones <rich@linuxplicable.org>	2025-07-18 14:22:03 +02:00
Dominik Kaminski	3e5f27c1d5	🔧(helm) add option to disable default tls setting Sets an option for those who uses impress with a different secretName in ingress.	2024-12-19 15:16:16 +01:00
Anthony LC	a902e31521	🔧(helm) add ingress collaboration api We need to keep the stickyness between the collaboration api and the ws server, to do so, we will use "upstream-hash-by: $arg_room", meaning that the stickyness will be based on the room query. We need to ahve 2 ingress to handle the "collaboration_auth", only the ws routes has to use the "collaboration_auth" subrequest.	2024-12-11 14:54:41 +01:00

Author

SHA1

Message

Date

Richard Jones

f2e54308d2

🐛(helm) charts generate invalid YAML for collaboration API / WS

Closes #890

Remove the service blocks outside the conditionals in the collaboration
API and WS templates.

Signed-off-by: Richard Jones <rich@linuxplicable.org>

2025-07-18 14:22:03 +02:00

Dominik Kaminski

3e5f27c1d5

🔧(helm) add option to disable default tls setting

Sets an option for those who uses impress
with a different secretName in ingress.

2024-12-19 15:16:16 +01:00

Anthony LC

a902e31521

🔧(helm) add ingress collaboration api

We need to keep the stickyness between the
collaboration api and the ws server, to do so,
we will use "upstream-hash-by: $arg_room", meaning
that the stickyness will be based on the room query.
We need to ahve 2 ingress to handle the
"collaboration_auth", only the ws routes has to
use the "collaboration_auth" subrequest.

2024-12-11 14:54:41 +01:00

3 Commits