Matrix Docker Ansible eploy
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 

327 line
18 KiB

  1. # SOME DESCRIPTIVE TITLE.
  2. # Copyright (C) 2018-2026, Slavi Pantaleev, Aine Etke, MDAD community members
  3. # This file is distributed under the same license as the matrix-docker-ansible-deploy package.
  4. # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
  5. #
  6. #, fuzzy
  7. msgid ""
  8. msgstr ""
  9. "Project-Id-Version: matrix-docker-ansible-deploy \n"
  10. "Report-Msgid-Bugs-To: \n"
  11. "POT-Creation-Date: 2026-07-16 13:47+0000\n"
  12. "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
  13. "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
  14. "Language-Team: LANGUAGE <LL@li.org>\n"
  15. "MIME-Version: 1.0\n"
  16. "Content-Type: text/plain; charset=UTF-8\n"
  17. "Content-Transfer-Encoding: 8bit\n"
  18. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:10
  19. msgid "Setting up a Generic Mautrix Bridge (optional)"
  20. msgstr ""
  21. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:12
  22. msgid "The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, discord, signal, googlechat, etc.), as well as many other (non-mautrix) bridges. This is a common guide for configuring mautrix bridges."
  23. msgstr ""
  24. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:14
  25. msgid "The author of the bridges maintains [the official docs](https://docs.mau.fi/bridges/index.html), whose source code is available at [mautrix/docs](https://github.com/mautrix/docs) repository on GitHub. You may as well to refer it while configuring them."
  26. msgstr ""
  27. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:16
  28. msgid "You can see each bridge's features on the `ROADMAP.md` file in its corresponding mautrix repository."
  29. msgstr ""
  30. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:18
  31. msgid "Adjusting the playbook configuration"
  32. msgstr ""
  33. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:20
  34. msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
  35. msgstr ""
  36. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:27
  37. msgid "**Note**: for bridging to Meta's Messenger or Instagram, you would need to add `meta` with an underscore symbol (`_`) or hyphen (`-`) based on the context as prefix to each `SERVICENAME`; add `_` to variables (as in `matrix_bridge_mautrix_meta_messenger_configuration_extension_yaml` for example) and `-` to paths of the configuration files (as in `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2`), respectively."
  38. msgstr ""
  39. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:29
  40. msgid "There are some additional things you may wish to configure about the bridge before you continue. Each bridge may have additional requirements besides `_enabled: true`. For example, the mautrix-telegram bridge (our documentation page about it is [here](configuring-playbook-bridge-mautrix-telegram.md)) requires the `matrix_bridge_mautrix_telegram_api_id` and `matrix_bridge_mautrix_telegram_api_hash` variables to be defined. Refer to each bridge's individual documentation page for details about enabling bridges."
  41. msgstr ""
  42. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:31
  43. msgid "Configure bridge permissions (optional)"
  44. msgstr ""
  45. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:33
  46. msgid "By default any user on your homeserver will be able to use the mautrix bridges. To limit who can use them you would need to configure their permissions settings."
  47. msgstr ""
  48. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:35
  49. msgid "Different levels of permission can be granted to users. For example, to **configure a user as an administrator for all bridges**, add the following configuration to your `vars.yml` file:"
  50. msgstr ""
  51. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:41
  52. msgid "If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default."
  53. msgstr ""
  54. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:43
  55. msgid "**Alternatively** (more verbose, but allows multiple admins to be configured), you can do the same on a per-bridge basis with:"
  56. msgstr ""
  57. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:52
  58. msgid "This will add the admin permission to the specific user, while keeping the default permissions."
  59. msgstr ""
  60. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:54
  61. msgid "You could also redefine the default permissions settings completely, rather than adding extra permissions. You may wish to look at `roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` to find information on the permission settings and other options you would like to configure."
  62. msgstr ""
  63. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:56
  64. msgid "Enable encryption (optional)"
  65. msgstr ""
  66. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:58
  67. msgid "[Encryption (End-to-Bridge Encryption, E2BE) support](https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html) is off by default. If you would like to enable encryption, add the following configuration to your `vars.yml` file:"
  68. msgstr ""
  69. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:60
  70. msgid "**for all bridges with encryption support**:"
  71. msgstr ""
  72. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:67
  73. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:86
  74. msgid "**Alternatively**, for a specific bridge:"
  75. msgstr ""
  76. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:74
  77. msgid "Enable relay mode (optional)"
  78. msgstr ""
  79. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:76
  80. msgid "[Relay mode](https://docs.mau.fi/bridges/general/relay-mode.html) is off by default. Check [the table on the official documentation](https://docs.mau.fi/bridges/general/relay-mode.html#support-table) for bridges which support relay mode."
  81. msgstr ""
  82. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:78
  83. msgid "If you would like to enable it, add the following configuration to your `vars.yml` file:"
  84. msgstr ""
  85. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:80
  86. msgid "**for all bridges with relay mode support**:"
  87. msgstr ""
  88. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:95
  89. msgid "You can only have one `matrix_bridge_mautrix_SERVICENAME_configuration_extension_yaml` definition in `vars.yml` per bridge, so if you need multiple pieces of configuration there, just merge them like this:"
  90. msgstr ""
  91. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:109
  92. msgid "If you want to activate the relaybot in a room, send `!prefix set-relay` in the rooms where you want to use the bot (replace `!prefix` with the appropriate command prefix for the bridge, like `!signal` or `!wa`). To deactivate, send `!prefix unset-relay`."
  93. msgstr ""
  94. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:111
  95. msgid "Use `!prefix set-pl 100` to be able for the bot to modify room settings and invite others."
  96. msgstr ""
  97. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:113
  98. msgid "Allow anyone on the homeserver to become a relay user (optional)"
  99. msgstr ""
  100. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:115
  101. msgid "By default, only admins are allowed to set themselves as relay users. To allow anyone on your homeserver to set themselves as relay users, add the following configuration to your `vars.yml` file:"
  102. msgstr ""
  103. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:121
  104. msgid "Set the bot's username (optional)"
  105. msgstr ""
  106. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:123
  107. msgid "To set the bot's username, add the following configuration to your `vars.yml` file:"
  108. msgstr ""
  109. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:129
  110. msgid "Configure the logging level (optional)"
  111. msgstr ""
  112. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:131
  113. msgid "To specify the logging level, add the following configuration to your `vars.yml` file:"
  114. msgstr ""
  115. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:137
  116. msgid "Replace `warn` with one of the following to control the verbosity of the logs generated: `trace`, `debug`, `info`, `warn`, `error` or `fatal`."
  117. msgstr ""
  118. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:139
  119. msgid "If you have issues with a service, and are requesting support, the higher levels of logging (those that appear earlier in the list, like `trace`) will generally be more helpful."
  120. msgstr ""
  121. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:141
  122. msgid "Expose the bridge's API (for Mautrix Manager and similar tools)"
  123. msgstr ""
  124. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:143
  125. msgid "Each mautrix bridge runs an HTTP API which tools like [Mautrix Manager](https://github.com/mautrix/manager) can use to help you log into the bridge. This is especially handy for bridges where logging in manually is cumbersome (like [mautrix-gmessages](configuring-playbook-bridge-mautrix-gmessages.md))."
  126. msgstr ""
  127. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:145
  128. msgid "By default, the playbook exposes this API publicly at `https://matrix.example.com/bridges/SERVICENAME` (for example, `https://matrix.example.com/bridges/gmessages`). Such tools authenticate to the bridge with your own Matrix access token, so you never need to share any bridge secret with them."
  129. msgstr ""
  130. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:147
  131. msgid "To make discovery easier, the playbook also serves a `/.well-known/matrix/mautrix` file which advertises all your exposed bridges. Mautrix Manager reads this file and offers your bridges automatically, so you don't need to enter their URLs by hand."
  132. msgstr ""
  133. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:149
  134. msgid "This is all enabled by default. To **disable exposing the API for all bridges**, add the following configuration to your `vars.yml` file:"
  135. msgstr ""
  136. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:155
  137. msgid "**Alternatively**, to disable it for a specific bridge:"
  138. msgstr ""
  139. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:161
  140. msgid "If you run additional bridges on the same server which are not managed by this playbook and would like compatible tools to discover them as well, you can advertise their base URLs in the `/.well-known/matrix/mautrix` file:"
  141. msgstr ""
  142. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:168
  143. msgid "Only list bridges hosted on (and connected to) this server here, as compatible tools will send your Matrix access token to them. For bridges on other servers, take a look at the `fi.mau.external_bridge_servers` property described in the [Mautrix Manager](https://github.com/mautrix/manager) documentation, which you can add via `matrix_static_files_file_matrix_mautrix_configuration_extension_json`."
  144. msgstr ""
  145. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:170
  146. msgid "Extending the configuration"
  147. msgstr ""
  148. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:172
  149. msgid "There are some additional things you may wish to configure about the bridge."
  150. msgstr ""
  151. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:174
  152. msgid "Take a look at:"
  153. msgstr ""
  154. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:176
  155. msgid "`roles/custom/matrix-bridge-mautrix-SERVICENAME/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
  156. msgstr ""
  157. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:177
  158. msgid "`roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_bridge_mautrix_SERVICENAME_configuration_extension_yaml` variable"
  159. msgstr ""
  160. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:179
  161. msgid "Installing"
  162. msgstr ""
  163. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:181
  164. msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
  165. msgstr ""
  166. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:188
  167. msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
  168. msgstr ""
  169. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:190
  170. msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
  171. msgstr ""
  172. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:192
  173. msgid "Usage"
  174. msgstr ""
  175. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:194
  176. msgid "To use the bridge, you need to start a chat with `@SERVICENAMEbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
  177. msgstr ""
  178. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:196
  179. msgid "For details about the next steps, refer to each bridge's individual documentation page."
  180. msgstr ""
  181. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:198
  182. msgid "Send `help` to the bot to see the available commands."
  183. msgstr ""
  184. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:200
  185. msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below."
  186. msgstr ""
  187. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:202
  188. msgid "Set up Double Puppeting (optional)"
  189. msgstr ""
  190. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:204
  191. msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
  192. msgstr ""
  193. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:206
  194. msgid "To set it up, you have 2 ways of going about it."
  195. msgstr ""
  196. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:208
  197. msgid "Method 1: automatically, by enabling Appservice Double Puppet (recommended)"
  198. msgstr ""
  199. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:210
  200. msgid "To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html), you could enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook."
  201. msgstr ""
  202. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:212
  203. msgid "Appservice Double Puppet is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver."
  204. msgstr ""
  205. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:214
  206. msgid "To enable the Appservice Double Puppet service, add the following configuration to your `vars.yml` file:"
  207. msgstr ""
  208. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:220
  209. msgid "When enabled, double puppeting will automatically be enabled for all bridges that support double puppeting via the appservice method."
  210. msgstr ""
  211. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:222
  212. msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
  213. msgstr ""
  214. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:224
  215. msgid "**Notes**:"
  216. msgstr ""
  217. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:226
  218. msgid "Previously there were multiple different automatic double puppeting methods like one with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but they have been superseded by this Appservice Double Puppet method. Double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future as the older methods were completely removed in the megabridge rewrites on [the upstream project](https://docs.mau.fi/bridges/general/double-puppeting.html#automatically)."
  219. msgstr ""
  220. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:229
  221. msgid "Some bridges like [the deprecated Facebook mautrix bridge](configuring-playbook-bridge-mautrix-facebook.md) are compatible with the Shared Secret Auth service only. These bridges automatically perform Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
  222. msgstr ""
  223. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:231
  224. msgid "Method 2: manually, by asking each user to provide a working access token"
  225. msgstr ""
  226. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:233
  227. msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
  228. msgstr ""
  229. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:235
  230. msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
  231. msgstr ""
  232. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:237
  233. msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
  234. msgstr ""
  235. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:239
  236. msgid "make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature"
  237. msgstr ""
  238. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:241
  239. msgid "Troubleshooting"
  240. msgstr ""
  241. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:243
  242. msgid "For troubleshooting information with a specific bridge, please see the playbook documentation about it (some other document in in `docs/`) and the upstream ([mautrix](https://github.com/mautrix)) bridge documentation for that specific bridge."
  243. msgstr ""
  244. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:245
  245. msgid "If the bridge's bot doesn't accept the invite to a chat, refer [the official troubleshooting page](https://docs.mau.fi/bridges/general/troubleshooting.html) as well."
  246. msgstr ""
  247. #: ../../../docs/configuring-playbook-bridge-mautrix-bridges.md:247
  248. msgid "If you found bugs in mautrix bridges, they should be reported to the upstream project, in the corresponding mautrix repository, not to us."
  249. msgstr ""