opendev/system-config
Code Issues Proposed changes
master
system-config/playbooks/roles/jitsi-meet
History
Jeremy Stanley 4f0bed6998 Explicitly down Jitsi-Meet containers on upgrade 
We've been running into problems with Jitsi-Meet processes not
restarting cleanly if we only docker-compose up after image pulls.
Instead, check for whether the pull resulted in new image downloads
and then cleanly down and up the containers, which seems to address
the problem based on manual testing on the servers.

Change-Id: Id551767e72102a4b8667aa9dacc81755f332a278
2024-09-26 17:52:29 +00:00
..
defaults Allow overriding of meetpad PUBLIC_URL 2024-05-02 13:41:47 -05:00
files Update colibri for all the JVBs 2022-09-16 12:10:00 -07:00
tasks Explicitly down Jitsi-Meet containers on upgrade 2024-09-26 17:52:29 +00:00
templates Allow overriding of meetpad PUBLIC_URL 2024-05-02 13:41:47 -05: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.