pub-solar/matrix-docker-ansible-deploy
5
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

fix(mautrix-discord): allow configuring the restricted_rooms option

Browse source
This commit is contained in:
Samuel Meenzen 2022-10-09 21:59:33 +02:00 committed by GitHub
parent e6ecd54e72
commit 7cc3aae041
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
roles/matrix-bridge-mautrix-discord/defaults/main.yml
View file

@ -140,3 +140,7 @@ matrix_mautrix_discord_registration: "{{ matrix_mautrix_discord_registration_yam
matrix_mautrix_discord_bridge_encryption_allow: false
matrix_mautrix_discord_bridge_encryption_default: "{{ matrix_mautrix_discord_bridge_encryption_allow }}"
matrix_mautrix_discord_bridge_encryption_key_sharing_allow: "{{ matrix_mautrix_discord_bridge_encryption_allow }}"
# On conduit this option may prevent you from joining spaces created by the bridge.
# Setting this to false fixes the issue.
matrix_mautrix_discord_restricted_rooms: true

2
roles/matrix-bridge-mautrix-discord/templates/config.yaml.j2
View file

@ -101,7 +101,7 @@ bridge:
message_error_notices: true
# Should the bridge use space-restricted join rules instead of invite-only for guild rooms?
# This can avoid unnecessary invite events in guild rooms when members are synced in.
restricted_rooms: true
restricted_rooms: {{ matrix_mautrix_discord_restricted_rooms }}
# Should the bridge update the m.direct account data event when double puppeting is enabled.
# Note that updating the m.direct event is not atomic (except with mautrix-asmux)
# and is therefore prone to race conditions.