Matrix Docker Ansible eploy
選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。
 
 

265 行
11 KiB

  1. # Endpoint URL that Draupnir uses to interact with the matrix homeserver (client-server API),
  2. # set this to the pantalaimon URL if you're using that.
  3. homeserverUrl: {{ matrix_bot_draupnir_homeserver_url | to_json }}
  4. # Endpoint URL that Draupnir could use to fetch events related to reports (client-server API and /_synapse/),
  5. # only set this to the public-internet homeserver client API URL, do NOT set this to the pantalaimon URL.
  6. rawHomeserverUrl: {{ matrix_bot_draupnir_raw_homeserver_url | to_json }}
  7. # Matrix Access Token to use, Draupnir will only use this if pantalaimon.use is false.
  8. accessToken: {{ matrix_bot_draupnir_access_token | to_json }}
  9. {% if matrix_bot_draupnir_pantalaimon_use %}
  10. # Options related to Pantalaimon (https://github.com/matrix-org/pantalaimon)
  11. pantalaimon:
  12. # Whether or not Draupnir will use pantalaimon to access the matrix homeserver,
  13. # set to `true` if you're using pantalaimon.
  14. #
  15. # Be sure to point homeserverUrl to the pantalaimon instance.
  16. #
  17. # Draupnir will log in using the given username and password once,
  18. # then store the resulting access token in a file under dataPath.
  19. use: true
  20. # The username to login with.
  21. username: {{ matrix_bot_draupnir_pantalaimon_username | to_json }}
  22. # The password Draupnir will login with.
  23. #
  24. # After successfully logging in once, this will be ignored, so this value can be blanked after first startup.
  25. password: {{ matrix_bot_draupnir_pantalaimon_password | to_json }}
  26. {% endif %}
  27. # The path Draupnir will store its state/data in, leave default ("/data/storage") when using containers.
  28. dataPath: "/data"
  29. # If true (the default), Draupnir will only accept invites from users present in managementRoom.
  30. autojoinOnlyIfManager: true
  31. # If `autojoinOnlyIfManager` is false, only the members in this space can invite
  32. # the bot to new rooms.
  33. #acceptInvitesFromSpace: "!example:example.org"
  34. # Whether Draupnir should report ignored invites to the management room (if autojoinOnlyIfManager is true).
  35. recordIgnoredInvites: false
  36. # The room ID (or room alias) of the management room, anyone in this room can issue commands to Draupnir.
  37. #
  38. # Draupnir has no more granular access controls other than this, be sure you trust everyone in this room - secure it!
  39. #
  40. # This should be a room alias or room ID - not a matrix.to URL.
  41. #
  42. # Note: By default, Draupnir is fairly verbose - expect a lot of messages in this room.
  43. # (see verboseLogging to adjust this a bit.)
  44. managementRoom: {{ matrix_bot_draupnir_management_room | to_json }}
  45. # Deprecated and will be removed in a future version.
  46. # Running with verboseLogging is unsupported.
  47. # Whether Draupnir should log a lot more messages in the room,
  48. # mainly involves "all-OK" messages, and debugging messages for when draupnir checks bans in a room.
  49. #verboseLogging: false
  50. # The log level of terminal (or container) output,
  51. # can be one of DEBUG, INFO, WARN and ERROR, in increasing order of importance and severity.
  52. #
  53. # This should be at INFO or DEBUG in order to get support for Draupnir problems.
  54. logLevel: "INFO"
  55. # Whether or not Draupnir should synchronize policy lists immediately after startup.
  56. # Equivalent to running '!draupnir sync'.
  57. syncOnStartup: true
  58. # Whether or not Draupnir should check moderation permissions in all protected rooms on startup.
  59. # Equivalent to running `!draupnir verify`.
  60. verifyPermissionsOnStartup: true
  61. # Whether or not Draupnir should actually apply bans and policy lists,
  62. # turn on to trial some untrusted configuration or lists.
  63. noop: false
  64. # Whether or not Draupnir should apply `m.room.server_acl` events.
  65. # DO NOT change this to `true` unless you are very confident that you know what you are doing.
  66. disableServerACL: {{ matrix_bot_draupnir_disable_server_acl | to_json }}
  67. # Whether Draupnir should check member lists quicker (by using a different endpoint),
  68. # keep in mind that enabling this will miss invited (but not joined) users.
  69. #
  70. # Turn on if your bot is in (very) large rooms, or in large amounts of rooms.
  71. fasterMembershipChecks: false
  72. # A case-insensitive list of ban reasons to have the bot also automatically redact the user's messages for.
  73. #
  74. # If the bot sees you ban a user with a reason that is an (exact case-insensitive) match to this list,
  75. # it will also remove the user's messages automatically.
  76. #
  77. # Typically this is useful to avoid having to give two commands to the bot.
  78. # Advanced: Use asterisks to have the reason match using "globs"
  79. # (f.e. "spam*testing" would match "spam for testing" as well as "spamtesting").
  80. #
  81. # See here for more info: https://www.digitalocean.com/community/tools/glob
  82. # Note: Keep in mind that glob is NOT regex!
  83. automaticallyRedactForReasons:
  84. - "spam"
  85. - "advertising"
  86. # A list of rooms to protect. Draupnir will add this to the list it knows from its account data.
  87. #
  88. # It won't, however, add it to the account data.
  89. # Manually add the room via '!draupnir rooms add' to have it stay protected regardless if this config value changes.
  90. #
  91. # Note: These must be matrix.to URLs
  92. #protectedRooms:
  93. # - "https://matrix.to/#/#yourroom:example.org"
  94. # Whether or not to add all joined rooms to the "protected rooms" list
  95. # (excluding the management room and watched policy list rooms, see below).
  96. #
  97. # Note that this effectively makes the protectedRooms and associated commands useless
  98. # for regular rooms.
  99. #
  100. # Note: the management room is *excluded* from this condition.
  101. # Explicitly add it as a protected room to protect it.
  102. #
  103. # Note: Ban list rooms the bot is watching but didn't create will not be protected.
  104. # Explicitly add these rooms as a protected room list if you want them protected.
  105. protectAllJoinedRooms: false
  106. # Increase this delay to have Draupnir wait longer between two consecutive backgrounded
  107. # operations. The total duration of operations will be longer, but the homeserver won't
  108. # be affected as much. Conversely, decrease this delay to have Draupnir chain operations
  109. # faster. The total duration of operations will generally be shorter, but the performance
  110. # of the homeserver may be more impacted.
  111. backgroundDelayMS: 500
  112. # Server administration commands, these commands will only work if Draupnir is
  113. # a global server administrator, and the bot's server is a Synapse instance.
  114. admin:
  115. # Whether or not Draupnir can temporarily take control of any eligible account from the local homeserver who's in the room
  116. # (with enough permissions) to "make" a user an admin.
  117. #
  118. # This only works if a local user with enough admin permissions is present in the room.
  119. enableMakeRoomAdminCommand: false
  120. # Misc options for command handling and commands
  121. commands:
  122. # Whether or not the `!draupnir` prefix is necessary to submit commands.
  123. #
  124. # If `true`, will allow commands like `!ban`, `!help`, etc.
  125. #
  126. # Note: Draupnir can also be pinged by display name instead of having to use
  127. # the !draupnir prefix. For example, "my_moderator_bot: ban @spammer:example.org"
  128. # will address only my_moderator_bot.
  129. allowNoPrefix: false
  130. # Any additional bot prefixes that Draupnir will listen to. i.e. adding `mod` will allow `!mod help`.
  131. additionalPrefixes:
  132. - "draupnir-bot"
  133. - "draupnir_bot"
  134. - "draupnir"
  135. # Whether or not commands with a wildcard (*) will require an additional `--force` argument
  136. # in the command to be able to be submitted.
  137. confirmWildcardBan: true
  138. # The default reasons to be prompted with if the reason is missing from a ban command.
  139. ban:
  140. defaultReasons:
  141. - "spam"
  142. - "brigading"
  143. - "harassment"
  144. - "disagreement"
  145. # Configuration specific to certain toggle-able protections
  146. #protections:
  147. # # Configuration for the wordlist plugin, which can ban users based if they say certain
  148. # # blocked words shortly after joining.
  149. # wordlist:
  150. # # A list of case-insensitive keywords that the WordList protection will watch for from new users.
  151. # #
  152. # # WordList will ban users who use these words when first joining a room, so take caution when selecting them.
  153. # #
  154. # # For advanced usage, regex can also be used, see the following links for more information;
  155. # # - https://www.digitalocean.com/community/tutorials/an-introduction-to-regular-expressions
  156. # # - https://regexr.com/
  157. # # - https://regexone.com/
  158. # words:
  159. # - "LoReM"
  160. # - "IpSuM"
  161. # - "DoLoR"
  162. # - "aMeT"
  163. #
  164. # # For how long (in minutes) the user is "new" to the WordList plugin.
  165. # #
  166. # # After this time, the user will no longer be banned for using a word in the above wordlist.
  167. # #
  168. # # Set to zero to disable the timeout and make users *always* appear "new".
  169. # # (users will always be banned if they say a bad word)
  170. # minutesBeforeTrusting: 20
  171. # Options for advanced monitoring of the health of the bot.
  172. health:
  173. # healthz options. These options are best for use in container environments
  174. # like Kubernetes to detect how healthy the service is. The bot will report
  175. # that it is unhealthy until it is able to process user requests. Typically
  176. # this means that it'll flag itself as unhealthy for a number of minutes
  177. # before saying "Now monitoring rooms" and flagging itself healthy.
  178. #
  179. # Health is flagged through HTTP status codes, defined below.
  180. healthz:
  181. # Whether the healthz integration should be enabled (default false)
  182. enabled: false
  183. # The port to expose the webserver on. Defaults to 8080.
  184. port: 8080
  185. # The address to listen for requests on. Defaults to all addresses.
  186. address: "0.0.0.0"
  187. # The path to expose the monitoring endpoint at. Defaults to `/healthz`
  188. endpoint: "/healthz"
  189. # The HTTP status code which reports that the bot is healthy/ready to
  190. # process requests. Typically this should not be changed. Defaults to
  191. # 200.
  192. healthyStatus: 200
  193. # The HTTP status code which reports that the bot is not healthy/ready.
  194. # Defaults to 418.
  195. unhealthyStatus: 418
  196. # Options for exposing web APIs.
  197. #web:
  198. # # Whether to enable web APIs.
  199. # enabled: false
  200. #
  201. # # The port to expose the webserver on. Defaults to 8080.
  202. # port: 8080
  203. #
  204. # # The address to listen for requests on. Defaults to only the current
  205. # # computer.
  206. # address: localhost
  207. #
  208. # # Alternative setting to open to the entire web. Be careful,
  209. # # as this will increase your security perimeter:
  210. # #
  211. # # address: "0.0.0.0"
  212. #
  213. # # A web API designed to intercept Matrix API
  214. # # POST /_matrix/client/r0/rooms/{roomId}/report/{eventId}
  215. # # and display readable abuse reports in the moderation room.
  216. # #
  217. # # If you wish to take advantage of this feature, you will need
  218. # # to configure a reverse proxy, see e.g. test/nginx.conf
  219. # abuseReporting:
  220. # # Whether to enable this feature.
  221. # enabled: false
  222. # Whether or not to actively poll synapse for abuse reports, to be used
  223. # instead of intercepting client calls to synapse's abuse endpoint, when that
  224. # isn't possible/practical.
  225. pollReports: false
  226. # Whether or not new reports, received either by webapi or polling,
  227. # should be printed to our managementRoom.
  228. displayReports: false