55f38141c5
This removes an unused letsencrypt dir bind mount for jitsi-meet web that was causing confusion (we run letsencrypt out of band and put the certs in the correct dir so we don't need this specific bind mount). We also remove the now unused config.js config file from the role. We stop managing the default nginx config and instead rely on the container provided template. To properly configure http redirects we set the ENABLE_HTTP_REDIRECT flag in the env var file. Finally we update the README file with a bit more info on how this all works. Change-Id: Iecb68c9855b5627d25f8bb586b0e6f366f1c80ab
13 lines
568 B
ReStructuredText
13 lines
568 B
ReStructuredText
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.
|
|
|