system-config/playbooks/roles/jitsi-meet
Clark Boylan f64b935778 Enable jitsi-meet xmpp websockets
This switches desktop clients to using xmpp over websockets instead of
BOSH. The mobile clients continue to use BOSH. Apparently this provides
better performance and is the default expectation of the upstream docker
images. We had disabled it prior to get back to a working state when we
weren't setting this variable at all.

After looking at configs on the docker images I expect that enabling
this explicitly will work (the problem before was we neither enabled nor
disabled it and the images can't handle that case). If that isn't the
case we can always revert.

Change-Id: I59c9fe75a0860782beb8864ff3bd9622b35381c1
2021-03-18 11:59:14 -07:00
..
defaults Add support for multiple jvbs behind meetpad 2020-05-20 13:41:30 -07:00
files More jitsi meet config cleanups 2021-03-18 11:55:02 -07:00
tasks More jitsi meet config cleanups 2021-03-18 11:55:02 -07:00
templates Enable jitsi-meet xmpp websockets 2021-03-18 11:59:14 -07: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.