Clark Boylan 2ac695f628 Manage jitsi-meet meet.conf as a template input for the container ... The jitsi meet containers want to generate configuration from the templates found in /defaults on the container to config files in the bind mounted /config (/var/jitsi-meet/ on the host side). This means that the configs ansible is writing to /var/jitsi-meet are complete ignored and overwritten by the container using its templating system and env vars. This is causing us problems because we would like to use a different etherpad prxoy config in nginx to ensure the Host header is set properly. To make this happen we bind mount in our own template file so that the container can template what we want rather than what is found in the image. Change-Id: Ifdde66a01bb7e632fc19ca0a512216584f1ea9f0		2021-03-17 13:03:09 -07:00
..
jvb-env.j2	Manage jitsi-meet meet.conf as a template input for the container	2021-03-17 13:03:09 -07:00
meet-env.j2	Manage jitsi-meet meet.conf as a template input for the container	2021-03-17 13:03:09 -07:00