opendev/system-config
Code Issues Proposed changes
96059d52bb
system-config/playbooks/roles/jitsi-meet
History
Jeremy Stanley 080ff3954f Pass PUBLIC_URL to jitsi-meet jvb containers 
For some reason, the JVB servers now seem to tell clients to connect
to 8443/tcp on localhost rather than the actual server. It seems it
wants to build the URL based on the PUBLIC_URL envvar, but we
previously did not pass that through to the JVB containers. Add it
to their configuration so they'll have it available.

Change-Id: I10c761105490a72c4eb9ac0b08a304b7d5d1e18c
2022-09-02 21:32:39 +00:00
..
defaults Add support for multiple jvbs behind meetpad 2020-05-20 13:41:30 -07:00
files Pass PUBLIC_URL to jitsi-meet jvb containers 2022-09-02 21:32:39 +00:00
tasks Move our jitsi-meet interface config to defaults 2022-09-02 17:31:57 +00:00
templates Pass PUBLIC_URL to jitsi-meet jvb containers 2022-09-02 21:32:39 +00:00
README.rst More jitsi meet config cleanups 2021-03-18 11:55:02 -07:00

README.rst

Install, configure, and run jitsi-meet.

Note that the Jitsi Meet docker images supply template files in /defaults on the image. These template files are used to generate configs in /config on the image (/var/jitsi-meet on the host) using the docker-compose .env file and its vars.

If we need to make changes to the configs we need to bind mount in a modified template file so that the config file generation produces what we expect. If we try to write the configs files ourselves then when jitsi meet restarts we will lose those configs until the next ansible run.