123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189 |
- # Homeserver details
- homeserver:
- # The address that this appservice can use to connect to the homeserver.
- address: https://example.com
- # The domain of the homeserver (for MXIDs, etc).
- domain: example.com
- # Whether or not to verify the SSL certificate of the homeserver.
- # Only applies if address starts with https://
- verify_ssl: true
- asmux: 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: http://localhost:29328
- # When using https:// the TLS certificate and key files for the address.
- tls_cert: false
- tls_key: false
- # The hostname and port where this appservice should listen.
- hostname: 0.0.0.0
- port: 29328
- # The maximum body size of appservice API requests (from the homeserver) in mebibytes
- # Usually 1 is enough, but on high-traffic bridges you might need to increase this to avoid 413s
- max_body_size: 1
- # The full URI to the database. Only Postgres is currently supported.
- database: postgres://username:password@hostname/db
- # Provisioning API part of the web server for automated portal creation and fetching information.
- # Used by things like mautrix-manager (https://github.com/tulir/mautrix-manager).
- provisioning:
- # Whether or not the provisioning API should be enabled.
- enabled: true
- # The prefix to use in the provisioning API endpoints.
- prefix: /_matrix/provision/v1
- # The shared secret to authorize users of the API.
- # Set to "generate" to generate and save a new token.
- shared_secret: generate
- # The unique ID of this appservice.
- id: signal
- # Username of the appservice bot.
- bot_username: signalbot
- # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty
- # to leave display name/avatar as-is.
- bot_displayname: Signal bridge bot
- bot_avatar: mxc://maunium.net/wPJgTQbZOtpBFmDNkiNEMDUp
- # Community ID for bridged users (changes registration file) and rooms.
- # Must be created manually.
- #
- # Example: "+signal:example.com". Set to false to disable.
- community_id: false
- # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify.
- as_token: "This value is generated when generating the registration"
- hs_token: "This value is generated when generating the registration"
- # Prometheus telemetry config. Requires prometheus-client to be installed.
- metrics:
- enabled: false
- listen_port: 8000
- signal:
- # Path to signald unix socket
- socket_path: /var/run/signald/signald.sock
- # Bridge config
- bridge:
- # Localpart template of MXIDs for Signal users.
- # {userid} is replaced with an identifier for the Signal user.
- username_template: "signal_{userid}"
- # Displayname template for Signal users.
- # {displayname} is replaced with the displayname of the Signal user, which is the first
- # available variable in displayname_preference. The variables in displayname_preference
- # can also be used here directly.
- displayname_template: "{displayname} (Signal)"
- # Whether or not contact list displaynames should be used.
- # Using this isn't recommended on multi-user instances.
- allow_contact_list_name_updates: false
- # Available variables: full_name, first_name, last_name, phone, uuid
- displayname_preference:
- - full name
- - phone
- # Whether or not to create portals for all groups on login/connect.
- autocreate_group_portal: true
- # Whether or not to create portals for all contacts on login/connect.
- autocreate_contact_portal: false
- # Whether or not to use /sync to get read receipts and typing notifications
- # when double puppeting is enabled
- sync_with_custom_puppets: true
- # Whether or not to 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
- # Shared secret for https://github.com/devture/matrix-synapse-shared-secret-auth
- #
- # If set, custom puppets will be enabled automatically for local users
- # instead of users having to find an access token and run `login-matrix`
- # manually.
- login_shared_secret: null
- # Whether or not created rooms should have federation enabled.
- # If false, created portal rooms will never be federated.
- federate_rooms: true
- # End-to-bridge encryption support options. These require matrix-nio to be installed with pip
- # and login_shared_secret to be configured in order to get a device for the bridge bot.
- #
- # Additionally, https://github.com/matrix-org/synapse/pull/5758 is required if using a normal
- # application service.
- encryption:
- # Allow encryption, work in group chat rooms with e2ee enabled
- allow: false
- # 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: false
- # Options for automatic key sharing.
- key_sharing:
- # 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: false
- # Require the requesting device to have a valid cross-signing signature?
- # This doesn't require that the bridge has verified the device, only that the user has verified it.
- # Not yet implemented.
- require_cross_signing: false
- # Require devices to be verified by the bridge?
- # Verification by the bridge is not yet implemented.
- require_verification: true
- # Whether or not to explicitly set the avatar and room name for private
- # chat portal rooms. This will be implicitly enabled if encryption.default is true.
- private_chat_portal_meta: false
- # Whether or not the bridge should send a read receipt from the bridge bot when a message has
- # been sent to Signal.
- delivery_receipts: false
- # Whether or not delivery errors should be reported as messages in the Matrix room.
- delivery_error_reports: false
- # Set this to true to tell the bridge to re-send m.bridge events to all rooms on the next run.
- # This field will automatically be changed back to false after it,
- # except if the config file is not writable.
- resend_bridge_info: false
- # The prefix for commands. Only required in non-management rooms.
- command_prefix: "!signal"
- # Permissions for using the bridge.
- # Permitted values:
- # user - Use the bridge with puppeting.
- # admin - Use and administrate the bridge.
- # Permitted keys:
- # * - All Matrix users
- # domain - All users on that homeserver
- # mxid - Specific user
- permissions:
- "example.com": "user"
- "@admin:example.com": "admin"
- # Python logging configuration.
- #
- # See section 16.7.2 of the Python documentation for more info:
- # https://docs.python.org/3.6/library/logging.config.html#configuration-dictionary-schema
- logging:
- version: 1
- formatters:
- colored:
- (): mautrix_signal.util.ColorFormatter
- format: "[%(asctime)s] [%(levelname)s@%(name)s] %(message)s"
- normal:
- format: "[%(asctime)s] [%(levelname)s@%(name)s] %(message)s"
- handlers:
- file:
- class: logging.handlers.RotatingFileHandler
- formatter: normal
- filename: ./mautrix-signal.log
- maxBytes: 10485760
- backupCount: 10
- console:
- class: logging.StreamHandler
- formatter: colored
- loggers:
- mau:
- level: DEBUG
- aiohttp:
- level: INFO
- root:
- level: DEBUG
- handlers: [file, console]
|