Browse Source

bridge-mautrix-telegram: add option for creating non-federated rooms

pull/1676/head
László Várady 4 years ago
parent
commit
5789b3bbab
2 changed files with 5 additions and 1 deletions
  1. +4
    -0
      roles/matrix-bridge-mautrix-telegram/defaults/main.yml
  2. +1
    -1
      roles/matrix-bridge-mautrix-telegram/templates/config.yaml.j2

+ 4
- 0
roles/matrix-bridge-mautrix-telegram/defaults/main.yml View File

@@ -40,6 +40,10 @@ matrix_mautrix_telegram_appservice_public_external: 'https://{{ matrix_server_fq

matrix_mautrix_telegram_appservice_bot_username: telegrambot

# Whether or not created rooms should have federation enabled.
# If false, created portal rooms will never be federated.
matrix_mautrix_telegram_federate_rooms: true

# Controls whether the matrix-mautrix-telegram container exposes its HTTP port (tcp/8080 in the container).
#
# Takes an "<ip>:<port>" or "<port>" value (e.g. "127.0.0.1:9006"), or empty string to not expose.


+ 1
- 1
roles/matrix-bridge-mautrix-telegram/templates/config.yaml.j2 View File

@@ -160,7 +160,7 @@ bridge:
parallel_file_transfer: false
# Whether or not created rooms should have federation enabled.
# If false, created portal rooms will never be federated.
federate_rooms: true
federate_rooms: {{ matrix_mautrix_telegram_federate_rooms|to_json }}
# Settings for converting animated stickers.
animated_sticker:
# Format to which animated stickers should be converted.


Loading…
Cancel
Save