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.
 
 

203 regels
9.2 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_signal_homeserver_address }}
  6. # The domain of the homeserver (for MXIDs, etc).
  7. domain: {{ matrix_mautrix_signal_homeserver_domain }}
  8. # Whether or not to verify the SSL certificate of the homeserver.
  9. # Only applies if address starts with https://
  10. verify_ssl: true
  11. asmux: false
  12. # Application service host/registration related details
  13. # Changing these values requires regeneration of the registration.
  14. appservice:
  15. # The address that the homeserver can use to connect to this appservice.
  16. address: {{ matrix_mautrix_signal_appservice_address }}
  17. # When using https:// the TLS certificate and key files for the address.
  18. tls_cert: false
  19. tls_key: false
  20. # The hostname and port where this appservice should listen.
  21. hostname: 0.0.0.0
  22. port: 29328
  23. # The maximum body size of appservice API requests (from the homeserver) in mebibytes
  24. # Usually 1 is enough, but on high-traffic bridges you might need to increase this to avoid 413s
  25. max_body_size: 1
  26. # The full URI to the database. Only Postgres is currently supported.
  27. database: {{ matrix_mautrix_signal_database_connection_string }}
  28. # Provisioning API part of the web server for automated portal creation and fetching information.
  29. # Used by things like mautrix-manager (https://github.com/tulir/mautrix-manager).
  30. provisioning:
  31. # Whether or not the provisioning API should be enabled.
  32. enabled: true
  33. # The prefix to use in the provisioning API endpoints.
  34. prefix: /_matrix/provision/v1
  35. # The shared secret to authorize users of the API.
  36. # Set to "generate" to generate and save a new token.
  37. shared_secret: generate
  38. # The unique ID of this appservice.
  39. id: signal
  40. # Username of the appservice bot.
  41. bot_username: {{ matrix_mautrix_signal_appservice_bot_username|to_json }}
  42. # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty
  43. # to leave display name/avatar as-is.
  44. bot_displayname: Signal bridge bot
  45. bot_avatar: mxc://maunium.net/wPJgTQbZOtpBFmDNkiNEMDUp
  46. # Community ID for bridged users (changes registration file) and rooms.
  47. # Must be created manually.
  48. #
  49. # Example: "+signal:example.com". Set to false to disable.
  50. community_id: false
  51. # Authentication tokens for AS <-> HS communication.
  52. as_token: "{{ matrix_mautrix_signal_appservice_token }}"
  53. hs_token: "{{ matrix_mautrix_signal_homeserver_token }}"
  54. # Prometheus telemetry config. Requires prometheus-client to be installed.
  55. metrics:
  56. enabled: false
  57. listen_port: 8000
  58. signal:
  59. # Path to signald unix socket
  60. socket_path: /signald/signald.sock
  61. # Directory for temp files when sending files to Signal. This should be an
  62. # absolute path that signald can read. For attachments in the other direction,
  63. # make sure signald is configured to use an absolute path as the data directory.
  64. outgoing_attachment_dir: /signald/attachments
  65. # Directory where signald stores avatars for groups.
  66. avatar_dir: /signald/avatars
  67. # Directory where signald stores auth data. Used to delete data when logging out.
  68. data_dir: /signald/data
  69. # Whether or not message attachments should be removed from disk after they're bridged.
  70. remove_file_after_handling: true
  71. # Bridge config
  72. bridge:
  73. # Localpart template of MXIDs for Signal users.
  74. # {userid} is replaced with an identifier for the Signal user.
  75. username_template: "signal_{userid}"
  76. # Displayname template for Signal users.
  77. # {displayname} is replaced with the displayname of the Signal user, which is the first
  78. # available variable in displayname_preference. The variables in displayname_preference
  79. # can also be used here directly.
  80. displayname_template: "{displayname} (Signal)"
  81. # Whether or not contact list displaynames should be used.
  82. # Using this isn't recommended on multi-user instances.
  83. allow_contact_list_name_updates: false
  84. # Available variables: full_name, first_name, last_name, phone, uuid
  85. displayname_preference:
  86. - full_name
  87. - phone
  88. # Whether or not to create portals for all groups on login/connect.
  89. autocreate_group_portal: true
  90. # Whether or not to create portals for all contacts on login/connect.
  91. autocreate_contact_portal: false
  92. # Whether or not to use /sync to get read receipts and typing notifications
  93. # when double puppeting is enabled
  94. sync_with_custom_puppets: true
  95. # Whether or not to update the m.direct account data event when double puppeting is enabled.
  96. # Note that updating the m.direct event is not atomic (except with mautrix-asmux)
  97. # and is therefore prone to race conditions.
  98. sync_direct_chat_list: false
  99. # Allow using double puppeting from any server with a valid client .well-known file.
  100. double_puppet_allow_discovery: false
  101. # Servers to allow double puppeting from, even if double_puppet_allow_discovery is false.
  102. double_puppet_server_map: {}
  103. # Shared secret for https://github.com/devture/matrix-synapse-shared-secret-auth
  104. #
  105. # If set, custom puppets will be enabled automatically for local users
  106. # instead of users having to find an access token and run `login-matrix`
  107. # manually.
  108. # If using this for other servers than the bridge's server,
  109. # you must also set the URL in the double_puppet_server_map.
  110. login_shared_secret_map:
  111. {{ matrix_mautrix_signal_homeserver_domain }}: {{ matrix_mautrix_signal_login_shared_secret|to_json }}
  112. # Whether or not created rooms should have federation enabled.
  113. # If false, created portal rooms will never be federated.
  114. federate_rooms: true
  115. # End-to-bridge encryption support options. These require matrix-nio to be installed with pip
  116. # and login_shared_secret to be configured in order to get a device for the bridge bot.
  117. #
  118. # Additionally, https://github.com/matrix-org/synapse/pull/5758 is required if using a normal
  119. # application service.
  120. encryption:
  121. # Allow encryption, work in group chat rooms with e2ee enabled
  122. allow: false
  123. # Default to encryption, force-enable encryption in all portals the bridge creates
  124. # This will cause the bridge bot to be in private chats for the encryption to work properly.
  125. default: false
  126. # Options for automatic key sharing.
  127. key_sharing:
  128. # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
  129. # You must use a client that supports requesting keys from other users to use this feature.
  130. allow: false
  131. # Require the requesting device to have a valid cross-signing signature?
  132. # This doesn't require that the bridge has verified the device, only that the user has verified it.
  133. # Not yet implemented.
  134. require_cross_signing: false
  135. # Require devices to be verified by the bridge?
  136. # Verification by the bridge is not yet implemented.
  137. require_verification: true
  138. # Whether or not to explicitly set the avatar and room name for private
  139. # chat portal rooms. This will be implicitly enabled if encryption.default is true.
  140. private_chat_portal_meta: false
  141. # Whether or not the bridge should send a read receipt from the bridge bot when a message has
  142. # been sent to Signal. This let's you check manually whether the bridge is receiving your
  143. # messages.
  144. # Note that this is not related to Signal delivery receipts.
  145. delivery_receipts: false
  146. # Whether or not delivery errors should be reported as messages in the Matrix room. (not yet implemented)
  147. delivery_error_reports: false
  148. # Set this to true to tell the bridge to re-send m.bridge events to all rooms on the next run.
  149. # This field will automatically be changed back to false after it,
  150. # except if the config file is not writable.
  151. resend_bridge_info: false
  152. # The prefix for commands. Only required in non-management rooms.
  153. command_prefix: "!signal"
  154. # Permissions for using the bridge.
  155. # Permitted values:
  156. # user - Use the bridge with puppeting.
  157. # admin - Use and administrate the bridge.
  158. # Permitted keys:
  159. # * - All Matrix users
  160. # domain - All users on that homeserver
  161. # mxid - Specific user
  162. permissions:
  163. '{{ matrix_mautrix_signal_homeserver_domain }}': user
  164. # Python logging configuration.
  165. #
  166. # See section 16.7.2 of the Python documentation for more info:
  167. # https://docs.python.org/3.6/library/logging.config.html#configuration-dictionary-schema
  168. logging:
  169. version: 1
  170. formatters:
  171. colored:
  172. (): mautrix_signal.util.ColorFormatter
  173. format: "[%(asctime)s] [%(levelname)s@%(name)s] %(message)s"
  174. normal:
  175. format: "[%(asctime)s] [%(levelname)s@%(name)s] %(message)s"
  176. handlers:
  177. console:
  178. class: logging.StreamHandler
  179. formatter: colored
  180. loggers:
  181. mau:
  182. level: {{ matrix_mautrix_signal_log_level }}
  183. aiohttp:
  184. level: INFO
  185. root:
  186. level: {{ matrix_mautrix_signal_log_level }}
  187. handlers: [console]