|
- #jinja2: lstrip_blocks: "True"
- # Homeserver details.
- homeserver:
- # The address that this appservice can use to connect to the homeserver.
- address: {{ matrix_mautrix_slack_homeserver_address | to_json }}
- # The domain of the homeserver (for MXIDs, etc).
- domain: {{ matrix_mautrix_slack_homeserver_domain | to_json }}
-
- # What software is the homeserver running?
- # Standard Matrix homeservers like Synapse, Dendrite and Conduit should just use "standard" here.
- software: standard
- # The URL to push real-time bridge status to.
- # If set, the bridge will make POST requests to this URL whenever a user's slack connection state changes.
- # The bridge will use the appservice as_token to authorize requests.
- status_endpoint: null
- # Endpoint for reporting per-message status.
- message_send_checkpoint_endpoint: null
- # Does the homeserver support https://github.com/matrix-org/matrix-spec-proposals/pull/2246?
- async_media: false
-
- # Application service host/registration related details.
- # Changing these values requires regeneration of the registration.
- appservice:
- # The address that the homeserver can use to connect to this appservice.
- address: {{ matrix_mautrix_slack_appservice_address | to_json }}
-
- # The hostname and port where this appservice should listen.
- hostname: 0.0.0.0
- port: 8080
-
- # Database config.
- database:
- # The database type. "sqlite3-fk-wal" and "postgres" are supported.
- type: {{ matrix_mautrix_slack_appservice_database_type|to_json }}
- # The database URI.
- # SQLite: A raw file path is supported, but `file:<path>?_txlock=immediate` is recommended.
- # https://github.com/mattn/go-sqlite3#connection-string
- # Postgres: Connection string. For example, postgres://user:password@host/database?sslmode=disable
- # To connect via Unix socket, use something like postgres:///dbname?host=/var/run/postgresql
- uri: {{ matrix_mautrix_slack_appservice_database_uri|to_json }}
- # Maximum number of connections. Mostly relevant for Postgres.
- max_open_conns: 20
- max_idle_conns: 2
- # Maximum connection idle time and lifetime before they're closed. Disabled if null.
- # Parsed with https://pkg.go.dev/time#ParseDuration
- max_conn_idle_time: null
- max_conn_lifetime: null
-
- # The unique ID of this appservice.
- id: slack
- # Appservice bot details.
- bot:
- # Username of the appservice bot.
- username: {{ matrix_mautrix_slack_appservice_bot_username|to_json }}
- # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty
- # to leave display name/avatar as-is.
- displayname: Slack bridge bot
- avatar: mxc://maunium.net/pVtzLmChZejGxLqmXtQjFxem
- # Whether or not to receive ephemeral events via appservice transactions.
- # Requires MSC2409 support (i.e. Synapse 1.22+).
- # You should disable bridge -> sync_with_custom_puppets when this is enabled.
- ephemeral_events: true
-
- # Should incoming events be handled asynchronously?
- # This may be necessary for large public instances with lots of messages going through.
- # However, messages will not be guaranteed to be bridged in the same order they were sent in.
- async_transactions: false
-
- # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify.
- as_token: {{ matrix_mautrix_slack_appservice_token | to_json }}
- hs_token: {{ matrix_mautrix_slack_homeserver_token | to_json }}
-
- # Bridge config
- bridge:
- # Localpart template of MXIDs for Slack users.
- # {{ '{{.}}' }} is replaced with the internal ID of the Slack user.
- username_template: "{{ 'slack_{{.}}' }}"
- # Displayname template for Slack users.
- # TODO: document variables
- displayname_template: "{{ '{{.RealName}} (S)' }}"
- bot_displayname_template: "{{ '{{.Name}} (bot)' }}"
- channel_name_template: "{{ '#{{.Name}} ({{.TeamName}})' }}"
-
- portal_message_buffer: 128
-
- # Should the bridge send a read receipt from the bridge bot when a message has been sent to Slack?
- delivery_receipts: true
- # Whether the bridge should send the message status as a custom com.beeper.message_send_status event.
- message_status_events: false
- # Whether the bridge should send error notices via m.notice events when a message fails to bridge.
- message_error_notices: true
-
- # Should the bridge sync with double puppeting to receive EDUs that aren't normally sent to appservices.
- sync_with_custom_puppets: false
- # 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.
- sync_direct_chat_list: false
-
- # Servers to always allow double puppeting from
- double_puppet_server_map:
- "{{ matrix_mautrix_slack_homeserver_domain }}": {{ matrix_mautrix_slack_homeserver_address }}
- # Allow using double puppeting from any server with a valid client .well-known file.
- double_puppet_allow_discovery: false
- # Shared secrets for https://github.com/devture/matrix-synapse-shared-secret-auth
- #
- # If set, double puppeting will be enabled automatically for local users
- # instead of users having to find an access token and run `login-matrix`
- # manually.
- login_shared_secret_map: {{ matrix_mautrix_slack_bridge_login_shared_secret_map|to_json }}
-
- message_handling_timeout:
- # Send an error message after this timeout, but keep waiting for the response until the deadline.
- # This is counted from the origin_server_ts, so the warning time is consistent regardless of the source of delay.
- # If the message is older than this when it reaches the bridge, the message won't be handled at all.
- error_after: 10s
- # Drop messages after this timeout. They may still go through if the message got sent to the servers.
- # This is counted from the time the bridge starts handling the message.
- deadline: 60s
-
- # The prefix for commands. Only required in non-management rooms.
- command_prefix: "{{ matrix_mautrix_slack_command_prefix }}"
- # Messages sent upon joining a management room.
- # Markdown is supported. The defaults are listed below.
- management_room_text:
- # Sent when joining a room.
- welcome: "Hello, I'm a Slack bridge bot."
- # Sent when joining a management room and the user is already logged in.
- welcome_connected: "Use `help` for help."
- # Sent when joining a management room and the user is not logged in.
- welcome_unconnected: "Use `help` for help, or `login-token` or `login-password` to log in."
- # Optional extra text sent when joining a management room.
- additional_help: ""
-
- backfill:
- # Allow backfilling at all? Requires MSC2716 support on homeserver.
- enable: false
-
- # If a backfilled chat is older than this number of hours, mark it as read even if it's unread on Slack.
- # Set to -1 to let any chat be unread.
- unread_hours_threshold: 720
-
- # Number of messages to immediately backfill when creating a portal.
- immediate_messages: 10
-
- # Settings for incremental backfill of history.
- incremental:
- # Maximum number of messages to backfill per batch.
- messages_per_batch: 100
- # The number of seconds to wait after backfilling the batch of messages.
- post_batch_delay: 20
- # The maximum number of messages to backfill per portal, split by the chat type.
- # If set to -1, all messages in the chat will eventually be backfilled.
- max_messages:
- # Channels
- channel: -1
- # Group direct messages
- group_dm: -1
- # 1:1 direct messages
- dm: -1
-
- # End-to-bridge encryption support options.
- #
- # See https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html for more info.
- encryption:
- # Allow encryption, work in group chat rooms with e2ee enabled
- allow: {{ matrix_mautrix_slack_bridge_encryption_allow|to_json }}
- # Default to encryption, force-enable encryption in all portals the bridge creates
- # This will cause the bridge bot to be in private chats for the encryption to work properly.
- default: {{ matrix_mautrix_slack_bridge_encryption_default|to_json }}
- # Whether to use MSC2409/MSC3202 instead of /sync long polling for receiving encryption-related data.
- appservice: false
- # Require encryption, drop any unencrypted messages.
- require: false
- # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
- # You must use a client that supports requesting keys from other users to use this feature.
- allow_key_sharing: {{ matrix_mautrix_slack_bridge_encryption_key_sharing_allow|to_json }}
- # What level of device verification should be required from users?
- #
- # Valid levels:
- # unverified - Send keys to all device in the room.
- # cross-signed-untrusted - Require valid cross-signing, but trust all cross-signing keys.
- # cross-signed-tofu - Require valid cross-signing, trust cross-signing keys on first use (and reject changes).
- # cross-signed-verified - Require valid cross-signing, plus a valid user signature from the bridge bot.
- # Note that creating user signatures from the bridge bot is not currently possible.
- # verified - Require manual per-device verification
- # (currently only possible by modifying the `trust` column in the `crypto_device` database table).
- verification_levels:
- # Minimum level for which the bridge should send keys to when bridging messages from WhatsApp to Matrix.
- receive: unverified
- # Minimum level that the bridge should accept for incoming Matrix messages.
- send: unverified
- # Minimum level that the bridge should require for accepting key requests.
- share: cross-signed-tofu
- # Options for Megolm room key rotation. These options allow you to
- # configure the m.room.encryption event content. See:
- # https://spec.matrix.org/v1.3/client-server-api/#mroomencryption for
- # more information about that event.
- rotation:
- # Enable custom Megolm room key rotation settings. Note that these
- # settings will only apply to rooms created after this option is
- # set.
- enable_custom: false
- # The maximum number of milliseconds a session should be used
- # before changing it. The Matrix spec recommends 604800000 (a week)
- # as the default.
- milliseconds: 604800000
- # The maximum number of messages that should be sent with a given a
- # session before changing it. The Matrix spec recommends 100 as the
- # default.
- messages: 100
-
- # Settings for provisioning API
- provisioning:
- # Prefix for the provisioning API paths.
- prefix: /_matrix/provision
- # Shared secret for authentication. If set to "generate", a random secret will be generated,
- # or if set to "disable", the provisioning API will be disabled.
- shared_secret: generate
-
- # Permissions for using the bridge.
- # Permitted values:
- # relay - Talk through the relaybot (if enabled), no access otherwise
- # user - Access to use the bridge to chat with a Slack account.
- # admin - User level and some additional administration tools
- # Permitted keys:
- # * - All Matrix users
- # domain - All users on that homeserver
- # mxid - Specific user
- permissions: {{ matrix_mautrix_slack_bridge_permissions|to_json }}
-
- logging:
- directory: ./logs
- file_name_format: ''
- file_date_format: "2006-01-02"
- file_mode: 384
- timestamp_format: Jan _2, 2006 15:04:05
- print_level: {{ matrix_mautrix_slack_logging_level | to_json }}
- print_json: false
- file_json: false
|