Raw YAML - Releases: latest, v26.04, v26.03, v25.11, v25.10
1# Network-specific config options
2network:
3 # Proxy to use for all Twitter connections.
4 proxy: null
5 # Alternative to proxy: an HTTP endpoint that returns the proxy URL to use for Twitter connections.
6 get_proxy_url: null
7
8 # Displayname template for Twitter users.
9 # {{ .DisplayName }} is replaced with the display name of the Twitter user.
10 # {{ .Username }} is replaced with the username of the Twitter user.
11 displayname_template: "{{ .DisplayName }} (Twitter)"
12
13 # Maximum number of conversations to sync on startup
14 conversation_sync_limit: 20
15
16 # Should the bridge cache sessions instead of resyncing chats on every restart?
17 cache_session: true
18
19 # Should the bridge use "X" instead of "Twitter" in certain places,
20 # such as the management room welcome message and MSC2346 bridge info?
21 x: false
22
23
24# Config options that affect the central bridge module.
25bridge:
26 # The prefix for commands. Only required in non-management rooms.
27 command_prefix: '!twitter'
28 # Should the bridge create a space for each login containing the rooms that account is in?
29 personal_filtering_spaces: true
30 # Whether the bridge should set names and avatars explicitly for DM portals.
31 # This is only necessary when using clients that don't support MSC4171.
32 private_chat_portal_meta: true
33 # Should events be handled asynchronously within portal rooms?
34 # If true, events may end up being out of order, but slow events won't block other ones.
35 # This is not yet safe to use.
36 async_events: false
37 # Should every user have their own portals rather than sharing them?
38 # By default, users who are in the same group on the remote network will be
39 # in the same Matrix room bridged to that group. If this is set to true,
40 # every user will get their own Matrix room instead.
41 # SETTING THIS IS IRREVERSIBLE AND POTENTIALLY DESTRUCTIVE IF PORTALS ALREADY EXIST.
42 split_portals: false
43 # Should the bridge resend `m.bridge` events to all portals on startup?
44 resend_bridge_info: false
45 # Should `m.bridge` events be sent without a state key?
46 # By default, the bridge uses a unique key that won't conflict with other bridges.
47 no_bridge_info_state_key: false
48 # Should bridge connection status be sent to the management room as `m.notice` events?
49 # These contain the same data that can be posted to an external HTTP server using homeserver -> status_endpoint.
50 # Allowed values: none, errors, all
51 bridge_status_notices: errors
52 # How long after an unknown error should the bridge attempt a full reconnect?
53 # Must be at least 1 minute. The bridge will add an extra ±20% jitter to this value.
54 unknown_error_auto_reconnect: null
55 # Maximum number of times to do the auto-reconnect above.
56 # The counter is per login, but is never reset except on logout and restart.
57 unknown_error_max_auto_reconnects: 10
58
59 # Should leaving Matrix rooms be bridged as leaving groups on the remote network?
60 bridge_matrix_leave: false
61 # Should `m.notice` messages be bridged?
62 bridge_notices: false
63 # Should room tags only be synced when creating the portal? Tags mean things like favorite/pin and archive/low priority.
64 # Tags currently can't be synced back to the remote network, so a continuous sync means tagging from Matrix will be undone.
65 tag_only_on_create: true
66 # List of tags to allow bridging. If empty, no tags will be bridged.
67 only_bridge_tags: [m.favourite, m.lowpriority]
68 # Should room mute status only be synced when creating the portal?
69 # Like tags, mutes can't currently be synced back to the remote network.
70 mute_only_on_create: true
71 # Should the bridge check the db to ensure that incoming events haven't been handled before
72 deduplicate_matrix_messages: false
73 # Should cross-room reply metadata be bridged?
74 # Most Matrix clients don't support this and servers may reject such messages too.
75 cross_room_replies: false
76 # If a state event fails to bridge, should the bridge revert any state changes made by that event?
77 revert_failed_state_changes: false
78 # In portals with no relay set, should Matrix users be kicked if they're
79 # not logged into an account that's in the remote chat?
80 kick_matrix_users: true
81 # Should the bridge listen to com.beeper.state_request events?
82 # This is not necessary for anything outside of Beeper.
83 enable_send_state_requests: false
84 # Should the com.beeper.bridge.identifiers list in global ghost profiles include phone numbers?
85 phone_numbers_in_profile: false
86
87 # What should be done to portal rooms when a user logs out or is logged out?
88 # Permitted values:
89 # nothing - Do nothing, let the user stay in the portals
90 # kick - Remove the user from the portal rooms, but don't delete them
91 # unbridge - Remove all ghosts in the room and disassociate it from the remote chat
92 # delete - Remove all ghosts and users from the room (i.e. delete it)
93 cleanup_on_logout:
94 # Should cleanup on logout be enabled at all?
95 enabled: false
96 # Settings for manual logouts (explicitly initiated by the Matrix user)
97 manual:
98 # Action for private portals which will never be shared with other Matrix users.
99 private: nothing
100 # Action for portals with a relay user configured.
101 relayed: nothing
102 # Action for portals which may be shared, but don't currently have any other Matrix users.
103 shared_no_users: nothing
104 # Action for portals which have other logged-in Matrix users.
105 shared_has_users: nothing
106 # Settings for credentials being invalidated (initiated by the remote network, possibly through user action).
107 # Keys have the same meanings as in the manual section.
108 bad_credentials:
109 private: nothing
110 relayed: nothing
111 shared_no_users: nothing
112 shared_has_users: nothing
113
114 # Settings for relay mode
115 relay:
116 # Whether relay mode should be allowed. If allowed, the set-relay command can be used to turn any
117 # authenticated user into a relaybot for that chat.
118 enabled: false
119 # Should only admins be allowed to set themselves as relay users?
120 # If true, non-admins can only set users listed in default_relays as relays in a room.
121 admin_only: true
122 # Should default relays be preferred when an explicit login ID isn't specified even if the user is logged in?
123 # This applies to the set-relay and bridge commands sent by any user, including admins.
124 prefer_default: true
125 # Should non-admins be allowed to use the bridge and sync-chat commands via default relays specified below?
126 allow_bridge: true
127 # List of user login IDs which anyone can set as a relay, as long as the relay user is in the room.
128 default_relays: []
129 # The formats to use when sending messages via the relaybot.
130 # Available variables:
131 # .Sender.UserID - The Matrix user ID of the sender.
132 # .Sender.Displayname - The display name of the sender (if set).
133 # .Sender.RequiresDisambiguation - Whether the sender's name may be confused with the name of another user in the room.
134 # .Sender.DisambiguatedName - The disambiguated name of the sender. This will be the displayname if set,
135 # plus the user ID in parentheses if the displayname is not unique.
136 # If the displayname is not set, this is just the user ID.
137 # .Message - The `formatted_body` field of the message.
138 # .Caption - The `formatted_body` field of the message, if it's a caption. Otherwise an empty string.
139 # .FileName - The name of the file being sent.
140 message_formats:
141 m.text: "<b>{{ .Sender.DisambiguatedName }}</b>: {{ .Message }}"
142 m.notice: "<b>{{ .Sender.DisambiguatedName }}</b>: {{ .Message }}"
143 m.emote: "* <b>{{ .Sender.DisambiguatedName }}</b> {{ .Message }}"
144 m.file: "<b>{{ .Sender.DisambiguatedName }}</b> sent a file{{ if .Caption }}: {{ .Caption }}{{ end }}"
145 m.image: "<b>{{ .Sender.DisambiguatedName }}</b> sent an image{{ if .Caption }}: {{ .Caption }}{{ end }}"
146 m.audio: "<b>{{ .Sender.DisambiguatedName }}</b> sent an audio file{{ if .Caption }}: {{ .Caption }}{{ end }}"
147 m.video: "<b>{{ .Sender.DisambiguatedName }}</b> sent a video{{ if .Caption }}: {{ .Caption }}{{ end }}"
148 m.location: "<b>{{ .Sender.DisambiguatedName }}</b> sent a location{{ if .Caption }}: {{ .Caption }}{{ end }}"
149 # For networks that support per-message displaynames (i.e. Slack and Discord), the template for those names.
150 # This has all the Sender variables available under message_formats (but without the .Sender prefix).
151 # Note that you need to manually remove the displayname from message_formats above.
152 displayname_format: "{{ .DisambiguatedName }}"
153
154 # Filter for automatically creating portals.
155 portal_create_filter:
156 # The mode for filtering, either `deny` or `allow`
157 mode: deny
158 # The list of portal IDs to deny or allow depending on the mode config.
159 # Items here can either be the plain portal ID as a string, or an object with `id` and `receiver` fields.
160 # The receiver field is necessary if you want to target a specific DM portal for example.
161 list: []
162 # A list of user login IDs from which to always deny creating portals.
163 # This is meant to be used with default relays, such that the relay bot
164 # being added to a group wouldn't automatically trigger portal creation.
165 always_deny_from_login: []
166
167 # Permissions for using the bridge.
168 # Permitted values:
169 # relay - Talk through the relaybot (if enabled), no access otherwise
170 # commands - Access to use commands in the bridge, but not login.
171 # user - Access to use the bridge with puppeting.
172 # admin - Full access, user level with some additional administration tools.
173 # Permitted keys:
174 # * - All Matrix users
175 # domain - All users on that homeserver
176 # mxid - Specific user
177 permissions:
178 "*": relay
179 "example.com": user
180 "@admin:example.com": admin
181
182# Config for the bridge's database.
183database:
184 # The database type. "sqlite3-fk-wal" and "postgres" are supported.
185 type: postgres
186 # The database URI.
187 # SQLite: A raw file path is supported, but `file:<path>?_txlock=immediate` is recommended.
188 # https://github.com/mattn/go-sqlite3#connection-string
189 # Postgres: Connection string. For example, postgres://user:password@host/database?sslmode=disable
190 # To connect via Unix socket, use something like postgres:///dbname?host=/var/run/postgresql
191 uri: postgres://user:password@host/database?sslmode=disable
192 # Maximum number of connections.
193 max_open_conns: 5
194 max_idle_conns: 1
195 # Maximum connection idle time and lifetime before they're closed. Disabled if null.
196 # Parsed with https://pkg.go.dev/time#ParseDuration
197 max_conn_idle_time: null
198 max_conn_lifetime: null
199
200# Homeserver details.
201homeserver:
202 # The address that this appservice can use to connect to the homeserver.
203 # Local addresses without HTTPS are generally recommended when the bridge is running on the same machine,
204 # but https also works if they run on different machines.
205 address: http://example.localhost:8008
206 # The domain of the homeserver (also known as server_name, used for MXIDs, etc).
207 domain: example.com
208
209 # What software is the homeserver running?
210 # Standard Matrix homeservers like Synapse, Dendrite and Conduit should just use "standard" here.
211 software: standard
212 # The URL to push real-time bridge status to.
213 # If set, the bridge will make POST requests to this URL whenever a user's remote network connection state changes.
214 # The bridge will use the appservice as_token to authorize requests.
215 status_endpoint:
216 # Endpoint for reporting per-message status.
217 # If set, the bridge will make POST requests to this URL when processing a message from Matrix.
218 # It will make one request when receiving the message (step BRIDGE), one after decrypting if applicable
219 # (step DECRYPTED) and one after sending to the remote network (step REMOTE). Errors will also be reported.
220 # The bridge will use the appservice as_token to authorize requests.
221 message_send_checkpoint_endpoint:
222 # Does the homeserver support https://github.com/matrix-org/matrix-spec-proposals/pull/2246?
223 async_media: false
224
225 # Should the bridge use a websocket for connecting to the homeserver?
226 # The server side is currently not documented anywhere and is only implemented by mautrix-wsproxy,
227 # mautrix-asmux (deprecated), and hungryserv (proprietary).
228 websocket: false
229 # How often should the websocket be pinged? Pinging will be disabled if this is zero.
230 ping_interval_seconds: 0
231
232# Application service host/registration related details.
233# Changing these values requires regeneration of the registration (except when noted otherwise)
234appservice:
235 # The address that the homeserver can use to connect to this appservice.
236 # Like the homeserver address, a local non-https address is recommended when the bridge is on the same machine.
237 # If the bridge is elsewhere, you must secure the connection yourself (e.g. with https or wireguard)
238 # If you want to use https, you need to use a reverse proxy. The bridge does not have TLS support built in.
239 address: http://localhost:29327
240 # A public address that external services can use to reach this appservice.
241 # This is only needed for things like public media. A reverse proxy is generally necessary when using this field.
242 # This value doesn't affect the registration file.
243 public_address: https://bridge.example.com
244
245 # The hostname and port where this appservice should listen.
246 # For Docker, you generally have to change the hostname to 0.0.0.0.
247 hostname: 127.0.0.1
248 port: 29327
249
250 # The unique ID of this appservice.
251 id: twitter
252 # Appservice bot details.
253 bot:
254 # Username of the appservice bot.
255 username: twitterbot
256 # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty
257 # to leave display name/avatar as-is.
258 displayname: Twitter bridge bot
259 avatar: mxc://maunium.net/HVHcnusJkQcpVcsVGZRELLCn
260
261 # Whether to receive ephemeral events via appservice transactions.
262 ephemeral_events: true
263 # Should incoming events be handled asynchronously?
264 # This may be necessary for large public instances with lots of messages going through.
265 # However, messages will not be guaranteed to be bridged in the same order they were sent in.
266 # This value doesn't affect the registration file.
267 async_transactions: false
268
269 # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify.
270 as_token: "This value is generated when generating the registration"
271 hs_token: "This value is generated when generating the registration"
272
273 # Localpart template of MXIDs for remote users.
274 # {{.}} is replaced with the internal ID of the user.
275 username_template: twitter_{{.}}
276
277# Config options that affect the Matrix connector of the bridge.
278matrix:
279 # Whether the bridge should send the message status as a custom com.beeper.message_send_status event.
280 message_status_events: false
281 # Whether the bridge should send a read receipt after successfully bridging a message.
282 delivery_receipts: false
283 # Whether the bridge should send error notices via m.notice events when a message fails to bridge.
284 message_error_notices: true
285 # Whether the bridge should update the m.direct account data event when double puppeting is enabled.
286 sync_direct_chat_list: true
287 # Whether created rooms should have federation enabled. If false, created portal rooms
288 # will never be federated. Changing this option requires recreating rooms.
289 federate_rooms: true
290 # The threshold as bytes after which the bridge should roundtrip uploads via the disk
291 # rather than keeping the whole file in memory.
292 upload_file_threshold: 5242880
293 # Should the bridge set additional custom profile info for ghosts?
294 # This can make a lot of requests, as there's no batch profile update endpoint.
295 ghost_extra_profile_info: false
296
297# Segment-compatible analytics endpoint for tracking some events, like provisioning API login and encryption errors.
298analytics:
299 # API key to send with tracking requests. Tracking is disabled if this is null.
300 token: null
301 # Address to send tracking requests to.
302 url: https://api.segment.io/v1/track
303 # Optional user ID for tracking events. If null, defaults to using Matrix user ID.
304 user_id: null
305
306# Settings for provisioning API
307provisioning:
308 # Shared secret for authentication. If set to "generate" or null, a random secret will be generated,
309 # or if set to "disable", the provisioning API will be disabled. Must be at least 16 characters.
310 shared_secret: generate
311 # Whether to allow provisioning API requests to be authed using Matrix access tokens.
312 # This follows the same rules as double puppeting to determine which server to contact to check the token,
313 # which means that by default, it only works for users on the same server as the bridge.
314 allow_matrix_auth: true
315 # Enable debug API at /debug with provisioning authentication.
316 debug_endpoints: false
317 # Enable session transfers between bridges. Note that this only validates Matrix or shared secret
318 # auth before passing live network client credentials down in the response.
319 enable_session_transfers: false
320
321# Some networks require publicly accessible media download links (e.g. for user avatars when using Discord webhooks).
322# These settings control whether the bridge will provide such public media access.
323public_media:
324 # Should public media be enabled at all?
325 # The public_address field under the appservice section MUST be set when enabling public media.
326 enabled: false
327 # A key for signing public media URLs.
328 # If set to "generate", a random key will be generated.
329 signing_key: generate
330 # Number of seconds that public media URLs are valid for.
331 # If set to 0, URLs will never expire.
332 expiry: 0
333 # Length of hash to use for public media URLs. Must be between 0 and 32.
334 hash_length: 32
335 # The path prefix for generated URLs. Note that this will NOT change the path where media is actually served.
336 # If you change this, you must configure your reverse proxy to rewrite the path accordingly.
337 path_prefix: /_mautrix/publicmedia
338 # Should the bridge store media metadata in the database in order to support encrypted media and generate shorter URLs?
339 # If false, the generated URLs will just have the MXC URI and a HMAC signature.
340 # The hash_length field will be used to decide the length of the generated URL.
341 # This also allows invalidating URLs by deleting the database entry.
342 use_database: false
343
344# Settings for converting remote media to custom mxc:// URIs instead of reuploading.
345# More details can be found at https://docs.mau.fi/bridges/go/discord/direct-media.html
346direct_media:
347 # Should custom mxc:// URIs be used instead of reuploading media?
348 enabled: false
349 # The server name to use for the custom mxc:// URIs.
350 # This server name will effectively be a real Matrix server, it just won't implement anything other than media.
351 # You must either set up .well-known delegation from this domain to the bridge, or proxy the domain directly to the bridge.
352 server_name: discord-media.example.com
353 # Optionally a custom .well-known response. This defaults to `server_name:443`
354 well_known_response:
355 # Optionally specify a custom prefix for the media ID part of the MXC URI.
356 media_id_prefix:
357 # If the remote network supports media downloads over HTTP, then the bridge will use MSC3860/MSC3916
358 # media download redirects if the requester supports it. Optionally, you can force redirects
359 # and not allow proxying at all by setting this to false.
360 # This option does nothing if the remote network does not support media downloads over HTTP.
361 allow_proxy: true
362 # Matrix server signing key to make the federation tester pass, same format as synapse's .signing.key file.
363 # This key is also used to sign the mxc:// URIs to ensure only the bridge can generate them.
364 server_key: generate
365
366# Settings for backfilling messages.
367# Note that the exact way settings are applied depends on the network connector.
368# See https://docs.mau.fi/bridges/general/backfill.html for more details.
369backfill:
370 # Whether to do backfilling at all.
371 enabled: false
372 # Maximum number of messages to backfill in empty rooms.
373 # If this is zero or negative, backfill will be disabled in new rooms.
374 max_initial_messages: 50
375 # Maximum number of missed messages to backfill after bridge restarts.
376 max_catchup_messages: 500
377 # If a backfilled chat is older than this number of hours,
378 # mark it as read even if it's unread on the remote network.
379 unread_hours_threshold: 720
380 # Settings for backfilling threads within other backfills.
381 threads:
382 # Maximum number of messages to backfill in a new thread.
383 max_initial_messages: 50
384 # Settings for the backwards backfill queue. This only applies when connecting to
385 # Beeper as standard Matrix servers don't support inserting messages into history.
386 queue:
387 # Should the backfill queue be enabled?
388 enabled: false
389 # Should manual calls to backfill queue tasks be allowed?
390 manual: false
391 # Number of messages to backfill in one batch.
392 batch_size: 100
393 # Delay between batches in seconds.
394 batch_delay: 20
395 # Maximum number of batches to backfill per portal.
396 # If set to -1, all available messages will be backfilled.
397 max_batches: -1
398 # Optional network-specific overrides for max batches.
399 # Interpretation of this field depends on the network connector.
400 max_batches_override: {}
401
402# Settings for enabling double puppeting
403double_puppet:
404 # Servers to always allow double puppeting from.
405 # This is only for other servers and should NOT contain the server the bridge is on.
406 servers:
407 anotherserver.example.org: https://matrix.anotherserver.example.org
408 # Whether to allow client API URL discovery for other servers. When using this option,
409 # users on other servers can use double puppeting even if their server URLs aren't
410 # explicitly added to the servers map above.
411 allow_discovery: false
412 # Shared secrets for automatic double puppeting.
413 # See https://docs.mau.fi/bridges/general/double-puppeting.html for instructions.
414 secrets:
415 example.com: as_token:foobar
416
417# End-to-bridge encryption support options.
418#
419# See https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html for more info.
420encryption:
421 # Whether to enable encryption at all. If false, the bridge will not function in encrypted rooms.
422 allow: false
423 # Whether to force-enable encryption in all bridged rooms.
424 default: false
425 # Whether to require all messages to be encrypted and drop any unencrypted messages.
426 require: false
427 # Whether to use MSC3202/MSC4203 instead of /sync long polling for receiving encryption-related data.
428 # This is an experimental option, see the docs for more info.
429 # Changing this option requires updating the appservice registration file.
430 appservice: false
431 # Whether to use MSC4190 instead of appservice login to create the bridge bot device.
432 # Requires the homeserver to support MSC4190 and the device masquerading parts of MSC3202.
433 # Only relevant when using end-to-bridge encryption, required when using encryption with next-gen auth (MSC3861).
434 msc4190: false
435 # Whether to encrypt reactions and reply metadata as per MSC4392.
436 # This is not supported by most clients.
437 msc4392: false
438 # Should the bridge bot generate a recovery key and cross-signing keys and verify itself?
439 # Note that without the latest version of MSC4190, this will fail if you reset the bridge database.
440 # The generated recovery key will be saved in the kv_store table under `recovery_key`.
441 self_sign: false
442 # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
443 # You must use a client that supports requesting keys from other users to use this feature.
444 allow_key_sharing: true
445 # Pickle key for encrypting encryption keys in the bridge database.
446 # If set to generate, a random key will be generated.
447 pickle_key: generate
448 # Options for deleting megolm sessions from the bridge.
449 delete_keys:
450 # Beeper-specific: delete outbound sessions when hungryserv confirms
451 # that the user has uploaded the key to key backup.
452 delete_outbound_on_ack: false
453 # Don't store outbound sessions in the inbound table.
454 dont_store_outbound: false
455 # Ratchet megolm sessions forward after decrypting messages.
456 ratchet_on_decrypt: false
457 # Delete fully used keys (index >= max_messages) after decrypting messages.
458 delete_fully_used_on_decrypt: false
459 # Delete previous megolm sessions from same device when receiving a new one.
460 delete_prev_on_new_session: false
461 # Delete megolm sessions received from a device when the device is deleted.
462 delete_on_device_delete: false
463 # Periodically delete megolm sessions when 2x max_age has passed since receiving the session.
464 periodically_delete_expired: false
465 # Delete inbound megolm sessions that don't have the received_at field used for
466 # automatic ratcheting and expired session deletion. This is meant as a migration
467 # to delete old keys prior to the bridge update.
468 delete_outdated_inbound: false
469 # What level of device verification should be required from users?
470 #
471 # Valid levels:
472 # unverified - Send keys to all device in the room.
473 # cross-signed-untrusted - Require valid cross-signing, but trust all cross-signing keys.
474 # cross-signed-tofu - Require valid cross-signing, trust cross-signing keys on first use (and reject changes).
475 # cross-signed-verified - Require valid cross-signing, plus a valid user signature from the bridge bot.
476 # Note that creating user signatures from the bridge bot is not currently possible.
477 # verified - Require manual per-device verification
478 # (currently only possible by modifying the `trust` column in the `crypto_device` database table).
479 verification_levels:
480 # Minimum level for which the bridge should send keys to when bridging messages from the remote network to Matrix.
481 receive: unverified
482 # Minimum level that the bridge should accept for incoming Matrix messages.
483 send: unverified
484 # Minimum level that the bridge should require for accepting key requests.
485 share: cross-signed-tofu
486 # Options for Megolm room key rotation. These options allow you to configure the m.room.encryption event content.
487 # See https://spec.matrix.org/v1.10/client-server-api/#mroomencryption for more information about that event.
488 rotation:
489 # Enable custom Megolm room key rotation settings. Note that these
490 # settings will only apply to rooms created after this option is set.
491 enable_custom: false
492 # The maximum number of milliseconds a session should be used
493 # before changing it. The Matrix spec recommends 604800000 (a week)
494 # as the default.
495 milliseconds: 604800000
496 # The maximum number of messages that should be sent with a given a
497 # session before changing it. The Matrix spec recommends 100 as the
498 # default.
499 messages: 100
500 # Disable rotating keys when a user's devices change?
501 # You should not enable this option unless you understand all the implications.
502 disable_device_change_key_rotation: false
503
504# Prefix for environment variables. All variables with this prefix must map to valid config fields.
505# Nesting in variable names is represented with a dot (.).
506# If there are no dots in the name, two underscores (__) are replaced with a dot.
507#
508# e.g. if the prefix is set to `BRIDGE_`, then `BRIDGE_APPSERVICE__AS_TOKEN` will set appservice.as_token.
509# `BRIDGE_appservice.as_token` would work as well, but can't be set in a shell as easily.
510#
511# If this is null, reading config fields from environment will be disabled.
512env_config_prefix: null
513
514# Logging config. See https://github.com/tulir/zeroconfig for details.
515logging:
516 min_level: debug
517 writers:
518 - type: stdout
519 format: pretty-colored
520 - type: file
521 format: json
522 filename: ./logs/bridge.log
523 max_size: 100
524 max_backups: 10
525 compress: false