This repository has been archived by the owner on Apr 17, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 48
/
sample.config.yaml
203 lines (168 loc) · 5.25 KB
/
sample.config.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
bridge:
# Port to host the bridge on
# Used for communication between the homeserver and the bridge
port: 8434
# The host connections to the bridge's webserver are allowed from
bindAddress: localhost
# Public domain of the homeserver
domain: matrix.org
# Reachable URL of the Matrix homeserver
homeserverUrl: https://matrix.org
# Optionally specify a different media URL used for the media store
#
# This is where Discord will download user profile pictures and media
# from
#mediaUrl: https://external-url.org
# Enables automatic double-puppeting when set. Automatic double-puppeting
# allows Discord accounts to control Matrix accounts. So sending a
# a message on Discord would send it on Matrix from your Matrix account
#
# loginSharedSecretMap is simply a map from homeserver URL
# to shared secret. Example:
#
# loginSharedSecretMap:
# matrix.org: "YOUR SHARED SECRET GOES HERE"
#
# See https://github.com/devture/matrix-synapse-shared-secret-auth for
# the necessary server module
#loginSharedSecretMap:
# Display name of the bridge bot
displayname: Discord Puppet Bridge
# Avatar URL of the bridge bot
#avatarUrl: mxc://example.com/abcdef12345
# Whether to create groups for each Discord Server
#
# Note that 'enable_group_creation' must be 'true' in Synapse's config
# for this to work
enableGroupSync: true
presence:
# Bridge Discord online/offline status
enabled: true
# How often to send status to the homeserver in milliseconds
interval: 500
provisioning:
# Regex of Matrix IDs allowed to use the puppet bridge
whitelist:
# Allow a specific user
#- "@user:server\\.com"
# Allow users on a specific homeserver
- "@.*:server\\.com"
# Allow anyone
#- ".*"
# Regex of Matrix IDs forbidden from using the puppet bridge
#blacklist:
# Disallow a specific user
#- "@user:server\\.com"
# Disallow users on a specific homeserver
#- "@.*:server\\.com"
relay:
# Regex of Matrix IDs who are allowed to use the bridge in relay mode.
# Relay mode is when a single Discord bot account relays messages of
# multiple Matrix users
#
# Same format as in provisioning
whitelist:
- "@.*:yourserver\\.com"
#blacklist:
#- "@user:yourserver\\.com"
selfService:
# Regex of Matrix IDs who are allowed to use bridge self-servicing (plumbed rooms)
#
# Same format as in provisioning
whitelist:
- "@.*:server\\.com"
#blacklist:
#- "@user:server\\.com"
# Map of homeserver URLs to their C-S API endpoint
#
# Useful for double-puppeting if .well-known is unavailable for some reason
#homeserverUrlMap:
#yourserver.com: http://localhost:1234
# Override the default name patterns for users, rooms and groups
#
# Variable names must be prefixed with a ':'
namePatterns:
# The default displayname for a bridged user
#
# Available variables:
#
# name: username of the user
# discriminator: hashtag of the user (ex. #1234)
user: :name
# A user's guild-specific displayname - if they've set a custom nick in
# a guild
#
# Available variables:
#
# name: username of the user
# discriminator: hashtag of the user (ex. #1234)
# displayname: the user's custom group-specific nick
# channel: the name of the channel
# guild: the name of the guild
userOverride: :displayname
# Room names for bridged Discord channels
#
# Available variables:
#
# name: name of the channel
# guild: name of the guild
# category: name of the category if existant
room: :name
# Group names for bridged Discord servers
#
# Available variables:
#
# name: name of the guide
group: :name
database:
# Use Postgres as a database backend. If set, will be used instead of SQLite3
#
# Connection string to connect to the Postgres instance
# with username "user", password "pass", host "localhost" and database name "dbname".
#
# Modify each value as necessary
#connString: "postgres://user:pass@localhost/dbname?sslmode=disable"
# Use SQLite3 as a database backend
#
# The name of the database file
filename: database.db
limits:
# Up to how many users should be auto-joined on room creation? -1 to disable
# auto-join functionality
#
# Defaults to 200
#maxAutojoinUsers: 200
# How long the delay between two auto-join users should be in milliseconds
#
# Defaults to 5000
#roomUserAutojoinDelay: 5000
logging:
# Log level of console output
#
# Allowed values starting with most verbose:
# silly, verbose, info, warn, error
console: info
# Date and time formatting
lineDateFormat: MMM-D HH:mm:ss.SSS
# Logging files
#
# Log files are rotated daily by default
files:
# Log file path
- file: "bridge.log"
# Log level for this file
#
# Allowed values starting with most verbose:
# silly, debug, verbose, info, warn, error
level: info
# Date and time formatting
datePattern: YYYY-MM-DD
# Maximum number of logs to keep.
#
# This can be a number of files or number of days.
# If using days, add 'd' as a suffix
maxFiles: 14d
# Maximum size of the file after which it will rotate.
# This can be a number of bytes, or units of kb, mb, and gb.
# If using units, add 'k', 'm', or 'g' as the suffix
maxSize: 50m