Matrix Docker Ansible eploy
Nie możesz wybrać więcej, niż 25 tematów Tematy muszą się zaczynać od litery lub cyfry, mogą zawierać myślniki ('-') i mogą mieć do 35 znaków.
 
 

70 wiersze
2.8 KiB

  1. # The log level of terminal (or container) output,
  2. # can be one of DEBUG, INFO, WARN and ERROR, in increasing order of importance and severity.
  3. #
  4. # This should be at INFO or DEBUG in order to get support for Draupnir problems.
  5. logLevel: "INFO"
  6. # Whether or not Draupnir should check moderation permissions in all protected rooms on startup.
  7. # Equivalent to running `!draupnir verify`.
  8. verifyPermissionsOnStartup: true
  9. # A case-insensitive list of ban reasons to have the bot also automatically redact the user's messages for.
  10. #
  11. # If the bot sees you ban a user with a reason that is an (exact case-insensitive) match to this list,
  12. # it will also remove the user's messages automatically.
  13. #
  14. # Typically this is useful to avoid having to give two commands to the bot.
  15. # Advanced: Use asterisks to have the reason match using "globs"
  16. # (f.e. "spam*testing" would match "spam for testing" as well as "spamtesting").
  17. #
  18. # See here for more info: https://www.digitalocean.com/community/tools/glob
  19. # Note: Keep in mind that glob is NOT regex!
  20. automaticallyRedactForReasons:
  21. - "spam"
  22. - "advertising"
  23. # Whether or not to add all joined rooms to the "protected rooms" list
  24. # (excluding the management room and watched policy list rooms, see below).
  25. #
  26. # Note that this effectively makes the protectedRooms and associated commands useless
  27. # for regular rooms.
  28. #
  29. # Note: the management room is *excluded* from this condition.
  30. # Explicitly add it as a protected room to protect it.
  31. #
  32. # Note: Ban list rooms the bot is watching but didn't create will not be protected.
  33. # Explicitly add these rooms as a protected room list if you want them protected.
  34. protectAllJoinedRooms: false
  35. # Increase this delay to have Draupnir wait longer between two consecutive backgrounded
  36. # operations. The total duration of operations will be longer, but the homeserver won't
  37. # be affected as much. Conversely, decrease this delay to have Draupnir chain operations
  38. # faster. The total duration of operations will generally be shorter, but the performance
  39. # of the homeserver may be more impacted.
  40. backgroundDelayMS: 500
  41. # Misc options for command handling and commands
  42. commands:
  43. # Whether or not the `!draupnir` prefix is necessary to submit commands.
  44. #
  45. # If `true`, will allow commands like `!ban`, `!help`, etc.
  46. #
  47. # Note: Draupnir can also be pinged by display name instead of having to use
  48. # the !draupnir prefix. For example, "my_moderator_bot: ban @spammer:example.org"
  49. # will address only my_moderator_bot.
  50. allowNoPrefix: false
  51. # Any additional bot prefixes that Draupnir will listen to. i.e. adding `mod` will allow `!mod help`.
  52. additionalPrefixes:
  53. - "draupnir-bot"
  54. - "draupnir_bot"
  55. - "draupnir"
  56. # The default reasons to be prompted with if the reason is missing from a ban command.
  57. ban:
  58. defaultReasons:
  59. - "spam"
  60. - "brigading"
  61. - "harassment"
  62. - "disagreement"