matrix-docker-ansible-deploy/roles/matrix-jitsi/tasks
Slavi Pantaleev d605b219a2 Manage Jitsi configuration by ourselves for most components
We do this for 2 reasons:

- so we can control things which are not controllable using environment
variables (for example `stunServers` in jitsi/web, since we don't wish
to use the hardcoded Google STUN servers if our own Coturn is enabled)

- so playbook variable changes will properly rebuild the configuration.
When using Jitsi environment variables, the configuration is only built
once (the first time) and never rebuilt again. This is not the
consistent with the rest of the playbook and with how Ansible operates.
We're not perfect at it (yet), because we still let the Jitsi containers
generate some files on their own, but we are closer and it should be
good enough for most things.

Related to #415 (Github Pull Request).
2020-03-24 09:35:21 +02:00
..
init.yml Add Jitsi support 2020-03-23 17:19:15 +02:00
main.yml Add Jitsi support 2020-03-23 17:19:15 +02:00
setup_jitsi_base.yml Add Jitsi support 2020-03-23 17:19:15 +02:00
setup_jitsi_jicofo.yml Manage Jitsi configuration by ourselves for most components 2020-03-24 09:35:21 +02:00
setup_jitsi_jvb.yml Manage Jitsi configuration by ourselves for most components 2020-03-24 09:35:21 +02:00
setup_jitsi_prosody.yml Add Jitsi support 2020-03-23 17:19:15 +02:00
setup_jitsi_web.yml Manage Jitsi configuration by ourselves for most components 2020-03-24 09:35:21 +02:00