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