mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2024-11-14 10:04:46 +08:00
fix(mautrix-discord): allow configuring the restricted_rooms option
This commit is contained in:
parent
e6ecd54e72
commit
7cc3aae041
@ -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
|
@ -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.
|
||||
|
Loading…
Reference in New Issue
Block a user