overmind
/
matrix-docker-ansible-deploy
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy
1
0
Fork 0
Code Issues 0 Releases 0 Wiki Activity
Matrix Docker Ansible eploy
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
12007 Commits
5 Branches
1.4 GiB
 
 
 
Tree: edc8236a5e
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'edc8236a5e'
${ noResults }
matrix-docker-ansible-deploy/docs/configuring-playbook-liveki...

2.5 KiB
Raw Blame History

Setting up LiveKit JWT Service (optional)

The playbook can install and configure LiveKit JWT Service for you.

This is a helper component which is part of the Matrix RTC stack that allows Element Call to integrate with LiveKit Server.

💡 LiveKit JWT Service is automatically installed and configured when either Element Call or the Matrix RTC stack is enabled, so you don’t need to do anything extra.

Take a look at:

  • roles/custom/matrix-livekit-jwt-service/defaults/main.yml for some variables that you can customize via your vars.yml file
  • roles/custom/matrix-livekit-jwt-service/templates/env.j2 for the component’s default configuration.

Federated calls and trusted homeservers

Since LiveKit JWT Service 0.7.0, only users from homeservers listed in matrix_livekit_jwt_service_environment_variable_livekit_full_access_homeservers_list may publish audio, video, or screen shares on your SFU. The list defaults to your matrix_domain. Other federated users receive media here and publish on their own homeserver’s SFU, using clients with multi-SFU support. See upstream’s explanation.

Current Element Call supports this in its compatibility mode using the existing JWT endpoint. Older clients, clients configured to use a single SFU, and callers without their own SFU may join but be unable to publish media.

If you intentionally provide SFU access to another trusted homeserver, add its Matrix server name to your inventory/host_vars/matrix.example.com/vars.yml file:

matrix_livekit_jwt_service_environment_variable_livekit_full_access_homeservers_list_custom:
  - example.org

This lets all users of that homeserver publish and trigger room creation on your SFU, including outside your calls. Using '*' grants these permissions to every homeserver.

To temporarily retain the previous behavior while updating clients or arranging SFU access:

matrix_livekit_jwt_service_version: 0.6.0
matrix_livekit_jwt_service_container_healthcheck_enabled: false

Remove both overrides when ready to upgrade. The healthcheck must remain disabled on 0.6.0 because it is broken in that image.