Matrix Docker Ansible eploy
25'ten fazla konu seçemezsiniz Konular bir harf veya rakamla başlamalı, kısa çizgiler ('-') içerebilir ve en fazla 35 karakter uzunluğunda olabilir.
 
 

222 satır
12 KiB

  1. #jinja2: lstrip_blocks: "True"
  2. # Homeserver details.
  3. homeserver:
  4. # The address that this appservice can use to connect to the homeserver.
  5. address: {{ matrix_mautrix_discord_homeserver_address | to_json }}
  6. # The domain of the homeserver (for MXIDs, etc).
  7. domain: {{ matrix_mautrix_discord_homeserver_domain | to_json }}
  8. # Is the homeserver actually mautrix-asmux?
  9. asmux: false
  10. # The URL to push real-time bridge status to.
  11. # If set, the bridge will make POST requests to this URL whenever a user's discord connection state changes.
  12. # The bridge will use the appservice as_token to authorize requests.
  13. status_endpoint: null
  14. # Endpoint for reporting per-message status.
  15. message_send_checkpoint_endpoint: null
  16. # Does the homeserver support https://github.com/matrix-org/matrix-spec-proposals/pull/2246?
  17. async_media: false
  18. # Application service host/registration related details.
  19. # Changing these values requires regeneration of the registration.
  20. appservice:
  21. # The address that the homeserver can use to connect to this appservice.
  22. address: {{ matrix_mautrix_discord_appservice_address | to_json }}
  23. # The hostname and port where this appservice should listen.
  24. hostname: 0.0.0.0
  25. port: 8080
  26. # Database config.
  27. database:
  28. # The database type. "sqlite3" and "postgres" are supported.
  29. type: {{ matrix_mautrix_discord_appservice_database_type|to_json }}
  30. # The database URI.
  31. # SQLite: File name is enough. https://github.com/mattn/go-sqlite3#connection-string
  32. # Postgres: Connection string. For example, postgres://user:password@host/database?sslmode=disable
  33. # To connect via Unix socket, use something like postgres:///dbname?host=/var/run/postgresql
  34. uri: {{ matrix_mautrix_discord_appservice_database_uri|to_json }}
  35. # Maximum number of connections. Mostly relevant for Postgres.
  36. max_open_conns: 20
  37. max_idle_conns: 2
  38. # Maximum connection idle time and lifetime before they're closed. Disabled if null.
  39. # Parsed with https://pkg.go.dev/time#ParseDuration
  40. max_conn_idle_time: null
  41. max_conn_lifetime: null
  42. # The unique ID of this appservice.
  43. id: discord
  44. # Appservice bot details.
  45. bot:
  46. # Username of the appservice bot.
  47. username: {{ matrix_mautrix_discord_appservice_bot_username|to_json }}
  48. # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty
  49. # to leave display name/avatar as-is.
  50. displayname: Discord bridge bot
  51. avatar: mxc://maunium.net/nIdEykemnwdisvHbpxflpDlC
  52. # Whether or not to receive ephemeral events via appservice transactions.
  53. # Requires MSC2409 support (i.e. Synapse 1.22+).
  54. ephemeral_events: true
  55. # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify.
  56. as_token: {{ matrix_mautrix_discord_appservice_token | to_json }}
  57. hs_token: {{ matrix_mautrix_discord_homeserver_token | to_json }}
  58. # Bridge config
  59. bridge:
  60. # Localpart template of MXIDs for Discord users.
  61. # {{ '{{.}}' }} is replaced with the internal ID of the Discord user.
  62. username_template: "{{ 'discord_{{.}}' }}"
  63. # Displayname template for Discord users. This is also used as the room name in DMs if private_chat_portal_meta is enabled.
  64. # Available variables:
  65. # {{ '{{.ID}}' }} - Internal user ID
  66. # {{ '{{.Username}}' }} - User's displayname on Discord
  67. # {{ '{{.Discriminator}}' }} - The 4 numbers after the name on Discord
  68. # {{ '{{.Bot}}' }} - Whether the user is a bot
  69. # {{ '{{.System}}' }} - Whether the user is an official system user
  70. displayname_template: "{{ '{{.Username}} {{if .Bot}} (bot){{end}}' }}"
  71. # Displayname template for Discord channels (bridged as rooms, or spaces when type=4).
  72. # Available variables:
  73. # {{ '{{.Name}}' }} - Channel name, or user displayname (pre-formatted with displayname_template) in DMs.
  74. # {{ '{{.ParentName}}' }} - Parent channel name (used for categories).
  75. # {{ '{{.GuildName}}' }} - Guild name.
  76. # {{ '{{.NSFW}}' }} - Whether the channel is marked as NSFW.
  77. # {{ '{{.Type}}' }} - Channel type (see values at https://github.com/bwmarrin/discordgo/blob/v0.25.0/structs.go#L251-L267)
  78. channel_name_template: "{{ '{{if or (eq .Type 3) (eq .Type 4)}}{{.Name}}{{else}}#{{.Name}}{{end}}' }}"
  79. # Displayname template for Discord guilds (bridged as spaces).
  80. # Available variables:
  81. # {{ '{{.Name}}' }} - Guild name
  82. guild_name_template: "{{ '{{.Name}}' }}"
  83. # Should the bridge explicitly set the avatar and room name for DM portal rooms?
  84. # This is implicitly enabled in encrypted rooms.
  85. private_chat_portal_meta: false
  86. portal_message_buffer: 128
  87. # Number of private channel portals to create on bridge startup.
  88. # Other portals will be created when receiving messages.
  89. startup_private_channel_create_limit: 5
  90. # Should the bridge send a read receipt from the bridge bot when a message has been sent to Discord?
  91. delivery_receipts: false
  92. # Whether the bridge should send the message status as a custom com.beeper.message_send_status event.
  93. message_status_events: true
  94. # Whether the bridge should send error notices via m.notice events when a message fails to bridge.
  95. message_error_notices: true
  96. # Should the bridge use space-restricted join rules instead of invite-only for guild rooms?
  97. # This can avoid unnecessary invite events in guild rooms when members are synced in.
  98. restricted_rooms: {{ matrix_mautrix_discord_bridge_restricted_rooms|to_json }}
  99. # Should the bridge update the m.direct account data event when double puppeting is enabled.
  100. # Note that updating the m.direct event is not atomic (except with mautrix-asmux)
  101. # and is therefore prone to race conditions.
  102. sync_direct_chat_list: false
  103. # Set this to true to tell the bridge to re-send m.bridge events to all rooms on the next run.
  104. # This field will automatically be changed back to false after it, except if the config file is not writable.
  105. resend_bridge_info: false
  106. # Should the bridge attempt to completely delete portal rooms when a channel is deleted on Discord?
  107. # If true, the bridge will try to kick Matrix users from the room. Otherwise, the bridge only makes ghosts leave.
  108. delete_portal_on_channel_delete: false
  109. # Whether or not created rooms should have federation enabled.
  110. # If false, created portal rooms will never be federated.
  111. federate_rooms: {{ matrix_mautrix_discord_federate_rooms|to_json }}
  112. # Servers to always allow double puppeting from
  113. double_puppet_server_map:
  114. "{{ matrix_mautrix_discord_homeserver_domain }}": {{ matrix_mautrix_discord_homeserver_address }}
  115. # Allow using double puppeting from any server with a valid client .well-known file.
  116. double_puppet_allow_discovery: false
  117. # Shared secrets for https://github.com/devture/matrix-synapse-shared-secret-auth
  118. #
  119. # If set, double puppeting will be enabled automatically for local users
  120. # instead of users having to find an access token and run `login-matrix`
  121. # manually.
  122. login_shared_secret_map: {{ matrix_mautrix_discord_bridge_login_shared_secret_map|to_json }}
  123. # The prefix for commands. Only required in non-management rooms.
  124. command_prefix: "{{ matrix_mautrix_discord_command_prefix }}"
  125. # Messages sent upon joining a management room.
  126. # Markdown is supported. The defaults are listed below.
  127. management_room_text:
  128. # Sent when joining a room.
  129. welcome: "Hello, I'm a Discord bridge bot."
  130. # Sent when joining a management room and the user is already logged in.
  131. welcome_connected: "Use `help` for help."
  132. # Sent when joining a management room and the user is not logged in.
  133. welcome_unconnected: "Use `help` for help or `login` to log in."
  134. # Optional extra text sent when joining a management room.
  135. additional_help: ""
  136. # End-to-bridge encryption support options.
  137. #
  138. # See https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html for more info.
  139. encryption:
  140. # Allow encryption, work in group chat rooms with e2ee enabled
  141. allow: {{ matrix_mautrix_discord_bridge_encryption_allow|to_json }}
  142. # Default to encryption, force-enable encryption in all portals the bridge creates
  143. # This will cause the bridge bot to be in private chats for the encryption to work properly.
  144. default: {{ matrix_mautrix_discord_bridge_encryption_default|to_json }}
  145. # Require encryption, drop any unencrypted messages.
  146. require: false
  147. # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
  148. # You must use a client that supports requesting keys from other users to use this feature.
  149. allow_key_sharing: {{ matrix_mautrix_discord_bridge_encryption_key_sharing_allow|to_json }}
  150. # What level of device verification should be required from users?
  151. #
  152. # Valid levels:
  153. # unverified - Send keys to all device in the room.
  154. # cross-signed-untrusted - Require valid cross-signing, but trust all cross-signing keys.
  155. # cross-signed-tofu - Require valid cross-signing, trust cross-signing keys on first use (and reject changes).
  156. # cross-signed-verified - Require valid cross-signing, plus a valid user signature from the bridge bot.
  157. # Note that creating user signatures from the bridge bot is not currently possible.
  158. # verified - Require manual per-device verification
  159. # (currently only possible by modifying the `trust` column in the `crypto_device` database table).
  160. verification_levels:
  161. # Minimum level for which the bridge should send keys to when bridging messages from WhatsApp to Matrix.
  162. receive: unverified
  163. # Minimum level that the bridge should accept for incoming Matrix messages.
  164. send: unverified
  165. # Minimum level that the bridge should require for accepting key requests.
  166. share: cross-signed-tofu
  167. # Options for Megolm room key rotation. These options allow you to
  168. # configure the m.room.encryption event content. See:
  169. # https://spec.matrix.org/v1.3/client-server-api/#mroomencryption for
  170. # more information about that event.
  171. rotation:
  172. # Enable custom Megolm room key rotation settings. Note that these
  173. # settings will only apply to rooms created after this option is
  174. # set.
  175. enable_custom: false
  176. # The maximum number of milliseconds a session should be used
  177. # before changing it. The Matrix spec recommends 604800000 (a week)
  178. # as the default.
  179. milliseconds: 604800000
  180. # The maximum number of messages that should be sent with a given a
  181. # session before changing it. The Matrix spec recommends 100 as the
  182. # default.
  183. messages: 100
  184. # Settings for provisioning API
  185. provisioning:
  186. # Prefix for the provisioning API paths.
  187. prefix: /_matrix/provision
  188. # Shared secret for authentication. If set to "generate", a random secret will be generated,
  189. # or if set to "disable", the provisioning API will be disabled.
  190. shared_secret: generate
  191. # Permissions for using the bridge.
  192. # Permitted values:
  193. # relay - Talk through the relaybot (if enabled), no access otherwise
  194. # user - Access to use the bridge to chat with a Discord account.
  195. # admin - User level and some additional administration tools
  196. # Permitted keys:
  197. # * - All Matrix users
  198. # domain - All users on that homeserver
  199. # mxid - Specific user
  200. permissions: {{ matrix_mautrix_discord_bridge_permissions|to_json }}
  201. logging:
  202. directory: ./logs
  203. file_name_format: ''
  204. file_date_format: "2006-01-02"
  205. file_mode: 384
  206. timestamp_format: Jan _2, 2006 15:04:05
  207. print_level: {{ matrix_mautrix_discord_logging_level | to_json }}
  208. print_json: false
  209. file_json: false