feature/latest-upstream-docker-compose #2
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "feature/latest-upstream-docker-compose"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@ -17,2 +54,3 @@
- ENABLE_TCC
- ENABLE_TRANSCRIPTIONS
- DISABLE_HTTPS
- ENABLE_XMPP_WEBSOCKET
For some env vars like this one, there are no entries/descriptions in the
env.example
from upstream Jitsi repo. Using the existing.env
file will lead to default values here - but I like this preparatory step.@ -177,1 +232,4 @@
meet.jitsi:
labels:
traefik.udp.routers.jvb.entrypoints: video
traefik.udp.routers.jvb.service: jvb
What's the purpose of the service dict var?
This should define a service entity for traefik which allows e.g. for loadbalancing. I haven't tried the loadbalancing yet. On the other hand, that entrypoint
video
is not further defined here. I am not sure whether other configuration is missing here.As long as this does not break our current setup, I'm fine with having the new labels here.
@ -178,0 +233,4 @@
labels:
traefik.udp.routers.jvb.entrypoints: video
traefik.udp.routers.jvb.service: jvb
traefik.udp.services.jvb.loadbalancer.server.port: '10000'
Could that be parameterized with
${JVB_PORT}
?Good point! Yes, could be, but it makes sense to create an Ansible var to allow a config of that
JVB_PORT
which is still more or less hardcoded in the env file.To my knowledge, this variable already exists:
jitsi_bridge_udp_port
. Or do I mix up things here?Where is that? I cannot find that string in the code.
I'm sorry, got that mixed up with one of my branches where I also needed to introduce such a variable :D
Memo for myself: This creates conflicts with the upcoming PR on multitenancy.