d605b219a2
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).
1.3 KiB
Jitsi
The playbook can install the Jitsi video-conferencing platform and integrate it with Riot.
Jitsi installation is not enabled by default, because it's not a core component of Matrix services.
The setup done by the playbook is very similar to docker-jitsi-meet.
Prerequisites
Before installing Jitsi, make sure you've created the jitsi.DOMAIN DNS record. See Configuring DNS.
You may also need to open the following ports to your server:
udp/10000- RTP media over UDPtcp/4443- RTP media fallback over TCP
Installation
Add this to your inventory/host_vars/matrix.DOMAIN/vars.yml configuration:
matrix_jitsi_enabled: true
# We only need this temporarily - until Jitsi integration in riot-web is finalized.
# Remove this line in the future, to switch back to a stable riot-web version.
matrix_riot_web_docker_image: "vectorim/riot-web:develop"
Then re-run the playbook: ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
.. and fully reload your riot-web page (at riot.DOMAIN).
Starting a video-conference in a room with more than 2 members should then create a Jitsi widget which utilizes your self-hosted Jitsi server.