Matrix Docker Ansible eploy
Du kannst nicht mehr als 25 Themen auswählen Themen müssen entweder mit einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.
 
 
 

8879 Zeilen
434 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. #: ../../../CHANGELOG.md:1
  19. msgid "2026-07-16"
  20. msgstr ""
  21. #: ../../../CHANGELOG.md:3
  22. msgid "(Backward Compatibility Break) Bridge variables have been renamed"
  23. msgstr ""
  24. #: ../../../CHANGELOG.md:5
  25. msgid "All bridge roles (`roles/custom/matrix-bridge-*`) now use a uniform variable naming scheme, where the variable prefix matches the role directory name. This adopts the naming policy proposed in [#4705](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/4705) and requested in [#5096](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5096)."
  26. msgstr ""
  27. #: ../../../CHANGELOG.md:7
  28. msgid "Previously, bridge variable prefixes were all over the place (`matrix_mautrix_telegram_*`, `matrix_heisenbridge_*`, `matrix_steam_bridge_*`, etc.). Now, they all follow the same pattern that bot roles (`matrix_bot_<name>_*`) have been using for years: the `matrix-bridge-mautrix-telegram` role uses `matrix_bridge_mautrix_telegram_*` variables, the `matrix-bridge-steam` role uses `matrix_bridge_steam_*` variables, and so on."
  29. msgstr ""
  30. #: ../../../CHANGELOG.md:9
  31. msgid "Only Ansible variables were renamed. Systemd service names, container names, `/matrix/*` directories, database names and usernames, and appservice registration contents (tokens, bot usernames) all remain the same. No data migration is necessary and bridges keep working as before, once you rename the variables in your `vars.yml` configuration file."
  32. msgstr ""
  33. #: ../../../CHANGELOG.md:11
  34. msgid "The playbook will let you know if your configuration still uses old-style variable names."
  35. msgstr ""
  36. #: ../../../CHANGELOG.md:13
  37. msgid "Here is the full rename map:"
  38. msgstr ""
  39. #: ../../../CHANGELOG.md:0
  40. msgid "Old variable prefix"
  41. msgstr ""
  42. #: ../../../CHANGELOG.md:0
  43. msgid "New variable prefix"
  44. msgstr ""
  45. #: ../../../CHANGELOG.md:0
  46. msgid "`matrix_appservice_discord_`"
  47. msgstr ""
  48. #: ../../../CHANGELOG.md:0
  49. msgid "`matrix_bridge_appservice_discord_`"
  50. msgstr ""
  51. #: ../../../CHANGELOG.md:0
  52. msgid "`matrix_appservice_irc_`"
  53. msgstr ""
  54. #: ../../../CHANGELOG.md:0
  55. msgid "`matrix_bridge_appservice_irc_`"
  56. msgstr ""
  57. #: ../../../CHANGELOG.md:0
  58. msgid "`matrix_beeper_linkedin_`"
  59. msgstr ""
  60. #: ../../../CHANGELOG.md:0
  61. msgid "`matrix_bridge_beeper_linkedin_`"
  62. msgstr ""
  63. #: ../../../CHANGELOG.md:0
  64. msgid "`matrix_heisenbridge_`"
  65. msgstr ""
  66. #: ../../../CHANGELOG.md:0
  67. msgid "`matrix_bridge_heisenbridge_`"
  68. msgstr ""
  69. #: ../../../CHANGELOG.md:0
  70. msgid "`matrix_hookshot_`"
  71. msgstr ""
  72. #: ../../../CHANGELOG.md:0
  73. msgid "`matrix_bridge_hookshot_`"
  74. msgstr ""
  75. #: ../../../CHANGELOG.md:0
  76. msgid "`matrix_mautrix_androidsms_`"
  77. msgstr ""
  78. #: ../../../CHANGELOG.md:0
  79. msgid "`matrix_bridge_mautrix_wsproxy_androidsms_`"
  80. msgstr ""
  81. #: ../../../CHANGELOG.md:0
  82. msgid "`matrix_mautrix_bluesky_`"
  83. msgstr ""
  84. #: ../../../CHANGELOG.md:0
  85. msgid "`matrix_bridge_mautrix_bluesky_`"
  86. msgstr ""
  87. #: ../../../CHANGELOG.md:0
  88. msgid "`matrix_mautrix_discord_`"
  89. msgstr ""
  90. #: ../../../CHANGELOG.md:0
  91. msgid "`matrix_bridge_mautrix_discord_`"
  92. msgstr ""
  93. #: ../../../CHANGELOG.md:0
  94. msgid "`matrix_mautrix_gmessages_`"
  95. msgstr ""
  96. #: ../../../CHANGELOG.md:0
  97. msgid "`matrix_bridge_mautrix_gmessages_`"
  98. msgstr ""
  99. #: ../../../CHANGELOG.md:0
  100. msgid "`matrix_mautrix_googlechat_`"
  101. msgstr ""
  102. #: ../../../CHANGELOG.md:0
  103. msgid "`matrix_bridge_mautrix_googlechat_`"
  104. msgstr ""
  105. #: ../../../CHANGELOG.md:0
  106. msgid "`matrix_mautrix_gvoice_`"
  107. msgstr ""
  108. #: ../../../CHANGELOG.md:0
  109. msgid "`matrix_bridge_mautrix_gvoice_`"
  110. msgstr ""
  111. #: ../../../CHANGELOG.md:0
  112. msgid "`matrix_mautrix_imessage_`"
  113. msgstr ""
  114. #: ../../../CHANGELOG.md:0
  115. msgid "`matrix_bridge_mautrix_wsproxy_imessage_`"
  116. msgstr ""
  117. #: ../../../CHANGELOG.md:0
  118. msgid "`matrix_mautrix_meta_instagram_`"
  119. msgstr ""
  120. #: ../../../CHANGELOG.md:0
  121. msgid "`matrix_bridge_mautrix_meta_instagram_`"
  122. msgstr ""
  123. #: ../../../CHANGELOG.md:0
  124. msgid "`matrix_mautrix_meta_messenger_`"
  125. msgstr ""
  126. #: ../../../CHANGELOG.md:0
  127. msgid "`matrix_bridge_mautrix_meta_messenger_`"
  128. msgstr ""
  129. #: ../../../CHANGELOG.md:0
  130. msgid "`matrix_mautrix_signal_`"
  131. msgstr ""
  132. #: ../../../CHANGELOG.md:0
  133. msgid "`matrix_bridge_mautrix_signal_`"
  134. msgstr ""
  135. #: ../../../CHANGELOG.md:0
  136. msgid "`matrix_mautrix_slack_`"
  137. msgstr ""
  138. #: ../../../CHANGELOG.md:0
  139. msgid "`matrix_bridge_mautrix_slack_`"
  140. msgstr ""
  141. #: ../../../CHANGELOG.md:0
  142. msgid "`matrix_mautrix_telegram_`"
  143. msgstr ""
  144. #: ../../../CHANGELOG.md:0
  145. msgid "`matrix_bridge_mautrix_telegram_`"
  146. msgstr ""
  147. #: ../../../CHANGELOG.md:0
  148. msgid "`matrix_mautrix_twitter_`"
  149. msgstr ""
  150. #: ../../../CHANGELOG.md:0
  151. msgid "`matrix_bridge_mautrix_twitter_`"
  152. msgstr ""
  153. #: ../../../CHANGELOG.md:0
  154. msgid "`matrix_mautrix_whatsapp_`"
  155. msgstr ""
  156. #: ../../../CHANGELOG.md:0
  157. msgid "`matrix_bridge_mautrix_whatsapp_`"
  158. msgstr ""
  159. #: ../../../CHANGELOG.md:0
  160. msgid "`matrix_mautrix_wsproxy_`"
  161. msgstr ""
  162. #: ../../../CHANGELOG.md:0
  163. msgid "`matrix_bridge_mautrix_wsproxy_`"
  164. msgstr ""
  165. #: ../../../CHANGELOG.md:0
  166. msgid "`matrix_meshtastic_relay_`"
  167. msgstr ""
  168. #: ../../../CHANGELOG.md:0
  169. msgid "`matrix_bridge_meshtastic_relay_`"
  170. msgstr ""
  171. #: ../../../CHANGELOG.md:0
  172. msgid "`matrix_mx_puppet_groupme_`"
  173. msgstr ""
  174. #: ../../../CHANGELOG.md:0
  175. msgid "`matrix_bridge_mx_puppet_groupme_`"
  176. msgstr ""
  177. #: ../../../CHANGELOG.md:0
  178. msgid "`matrix_mx_puppet_steam_`"
  179. msgstr ""
  180. #: ../../../CHANGELOG.md:0
  181. msgid "`matrix_bridge_mx_puppet_steam_`"
  182. msgstr ""
  183. #: ../../../CHANGELOG.md:0
  184. msgid "`matrix_postmoogle_`"
  185. msgstr ""
  186. #: ../../../CHANGELOG.md:0
  187. msgid "`matrix_bridge_postmoogle_`"
  188. msgstr ""
  189. #: ../../../CHANGELOG.md:0
  190. msgid "`matrix_rustpush_bridge_`"
  191. msgstr ""
  192. #: ../../../CHANGELOG.md:0
  193. msgid "`matrix_bridge_rustpush_`"
  194. msgstr ""
  195. #: ../../../CHANGELOG.md:0
  196. msgid "`matrix_sms_bridge_`"
  197. msgstr ""
  198. #: ../../../CHANGELOG.md:0
  199. msgid "`matrix_bridge_sms_`"
  200. msgstr ""
  201. #: ../../../CHANGELOG.md:0
  202. msgid "`matrix_steam_bridge_`"
  203. msgstr ""
  204. #: ../../../CHANGELOG.md:0
  205. msgid "`matrix_bridge_steam_`"
  206. msgstr ""
  207. #: ../../../CHANGELOG.md:0
  208. msgid "`matrix_wechat_`"
  209. msgstr ""
  210. #: ../../../CHANGELOG.md:0
  211. msgid "`matrix_bridge_wechat_`"
  212. msgstr ""
  213. #: ../../../CHANGELOG.md:46
  214. msgid "A few special cases beyond the prefix map:"
  215. msgstr ""
  216. #: ../../../CHANGELOG.md:48
  217. msgid "`matrix_mautrix_signal_wsproxy_syncproxy_connection_string` (a variable of the mautrix-wsproxy role, despite its name) is now `matrix_bridge_mautrix_wsproxy_syncproxy_connection_string`"
  218. msgstr ""
  219. #: ../../../CHANGELOG.md:49
  220. msgid "`matrix_playbook_migration_matrix_postmoogle_migration_validation_enabled` is now `matrix_playbook_migration_matrix_bridge_postmoogle_migration_validation_enabled`"
  221. msgstr ""
  222. #: ../../../CHANGELOG.md:51
  223. msgid "You can update your `vars.yml` file automatically with this `sed` command (on macOS, use `sed -i ''` instead of `sed -i`):"
  224. msgstr ""
  225. #: ../../../CHANGELOG.md:88
  226. msgid "The `sed` command only replaces prefixes followed by an underscore, so values that intentionally match old prefixes (like the default database names, e.g. `matrix_mautrix_telegram`) are not affected."
  227. msgstr ""
  228. #: ../../../CHANGELOG.md:90
  229. msgid "**Note**: if you have defined your own custom variables whose names embed an old prefix (e.g. `vault_matrix_postmoogle_password` referencing a secret in an Ansible Vault file), the `sed` command renames such references too. Either rename your custom variables to match (including their definitions in encrypted vault files, which `sed` cannot reach), or revert those spots manually."
  230. msgstr ""
  231. #: ../../../CHANGELOG.md:92
  232. msgid "2026-07-15"
  233. msgstr ""
  234. #: ../../../CHANGELOG.md:94
  235. msgid "Google Voice bridging"
  236. msgstr ""
  237. #: ../../../CHANGELOG.md:96
  238. msgid "The playbook can now bridge [Google Voice](https://voice.google.com/) via the [mautrix-gvoice](https://github.com/mautrix/gvoice) bridge. Text and media flow both ways, and portal rooms build themselves for your recent conversations."
  239. msgstr ""
  240. #: ../../../CHANGELOG.md:98
  241. msgid "Login is by cookie, not a paired phone: you copy the cookies from a browser signed in to voice.google.com and hand them to the bot. Google expires them on its own schedule, so expect to log in again every so often. See [Setting up Mautrix Google Voice bridging](./docs/configuring-playbook-bridge-mautrix-gvoice.md) to get started."
  242. msgstr ""
  243. #: ../../../CHANGELOG.md:100
  244. msgid "matrix-appservice-kakaotalk has been removed from the playbook"
  245. msgstr ""
  246. #: ../../../CHANGELOG.md:102
  247. msgid "The [matrix-appservice-kakaotalk](./docs/configuring-playbook-bridge-appservice-kakaotalk.md) bridge has been removed from the playbook. This component could only be installed by self-building its source code, and its upstream repository has become unreachable, which makes installation impossible. The bridge was also based on the unmaintained node-kakao library, and there have been reports that using it may get KakaoTalk accounts banned."
  248. msgstr ""
  249. #: ../../../CHANGELOG.md:104
  250. msgid "The playbook will let you know if you're using any `matrix_appservice_kakaotalk_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-bridge-appservice-kakaotalk.md#uninstalling-the-component-manually)."
  251. msgstr ""
  252. #: ../../../CHANGELOG.md:106
  253. msgid "Dedicated CAPTCHA variables for Matrix Authentication Service"
  254. msgstr ""
  255. #: ../../../CHANGELOG.md:108
  256. msgid "[Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) can now be protected with CAPTCHA (ReCaptcha v2, Cloudflare Turnstile, or hCaptcha) via dedicated variables, instead of going through `matrix_authentication_service_configuration_extension_yaml`. See the [captcha documentation](./docs/configuring-captcha.md#matrix-authentication-service) for details."
  257. msgstr ""
  258. #: ../../../CHANGELOG.md:110
  259. msgid "2026-07-14"
  260. msgstr ""
  261. #: ../../../CHANGELOG.md:112
  262. msgid "The playbook no longer ships a custom welcome page for Element Web"
  263. msgstr ""
  264. #: ../../../CHANGELOG.md:114
  265. msgid "Element Web [redesigned its welcome page](https://github.com/element-hq/element-web/pull/33211) (the screen shown at `/#/welcome` before logging in) into a built-in component and no longer loads a custom `welcome.html` file by default. Since the playbook upgraded to an Element Web version containing that change (spring 2026), the custom welcome page the playbook installed (and the variables customizing it) had silently stopped having any effect."
  266. msgstr ""
  267. #: ../../../CHANGELOG.md:116
  268. msgid "The playbook now embraces the new upstream behavior and no longer ships its own `welcome.html`. The following variables have been removed and the playbook will let you know if you're still using them: `matrix_client_element_welcome_headline`, `matrix_client_element_welcome_text`, `matrix_client_element_welcome_logo_link` and `matrix_client_element_page_template_welcome_path`."
  269. msgstr ""
  270. #: ../../../CHANGELOG.md:118
  271. msgid "Most welcome page customizations keep working, because they go through Element Web's branding configuration, which the new welcome page still honors:"
  272. msgstr ""
  273. #: ../../../CHANGELOG.md:120
  274. msgid "a custom logo, via `matrix_client_element_welcome_logo` (or `matrix_client_element_branding_auth_header_logo_url`)"
  275. msgstr ""
  276. #: ../../../CHANGELOG.md:121
  277. msgid "a custom background, via `matrix_client_element_branding_welcome_background_url`"
  278. msgstr ""
  279. #: ../../../CHANGELOG.md:123
  280. msgid "If you need a fully custom welcome page, you can self-host an HTML page and point Element Web at it, like this:"
  281. msgstr ""
  282. #: ../../../CHANGELOG.md:134
  283. msgid "BorgBackup now includes Synapse's local thumbnails"
  284. msgstr ""
  285. #: ../../../CHANGELOG.md:136
  286. msgid "For Synapse servers, the built-in [BorgBackup](./docs/configuring-playbook-backup-borg.md) integration no longer excludes the media store's `local_thumbnails` directory from backups."
  287. msgstr ""
  288. #: ../../../CHANGELOG.md:138
  289. msgid "Synapse only generates thumbnails of local media at upload time (unless `dynamic_thumbnails` is enabled, which the playbook does not do), and there is no tooling to regenerate them. Restoring a backup made with the previous exclusion list therefore left all previously uploaded local images without thumbnails. The [official Synapse backup guide](https://element-hq.github.io/synapse/latest/usage/administration/backups.html) recommends backing this directory up, and the playbook now follows that recommendation."
  290. msgstr ""
  291. #: ../../../CHANGELOG.md:140
  292. msgid "Expect your backups to grow somewhat, depending on how much image media your local users have uploaded. If you prefer the old behavior, you can redefine `backup_borg_location_exclude_patterns` in your `vars.yml`."
  293. msgstr ""
  294. #: ../../../CHANGELOG.md:142
  295. msgid "2026-07-12"
  296. msgstr ""
  297. #: ../../../CHANGELOG.md:144
  298. msgid "matrix-registration-bot has been removed from the playbook"
  299. msgstr ""
  300. #: ../../../CHANGELOG.md:146
  301. msgid "The [matrix-registration-bot](./docs/configuring-playbook-bot-matrix-registration-bot.md) service has been removed from the playbook, as it has been unmaintained."
  302. msgstr ""
  303. #: ../../../CHANGELOG.md:148
  304. msgid "The playbook will let you know if you're using any `matrix_bot_matrix_registration_bot_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-bot-matrix-registration-bot.md#uninstalling-the-component-manually)."
  305. msgstr ""
  306. #: ../../../CHANGELOG.md:150
  307. msgid "Continuwuity v26 no longer supports LDAP"
  308. msgstr ""
  309. #: ../../../CHANGELOG.md:152
  310. msgid "The playbook now installs [Continuwuity](./docs/configuring-playbook-continuwuity.md) v26, a major upgrade from the v0.5.x series which **removes LDAP authentication support** (see the [v26.6.0 release notes](https://forgejo.ellis.link/continuwuation/continuwuity/releases/tag/v26.6.0))."
  311. msgstr ""
  312. #: ../../../CHANGELOG.md:154
  313. msgid "The playbook never exposed dedicated variables for Continuwuity's LDAP support, so most people are unaffected. However, if you had enabled LDAP via `matrix_continuwuity_environment_variables_extension` or a custom configuration template, you'll need to migrate to another authentication method, such as the newly introduced [OpenID Connect support](https://continuwuity.org/guides/oidc)."
  314. msgstr ""
  315. #: ../../../CHANGELOG.md:156
  316. msgid "2026-06-29"
  317. msgstr ""
  318. #: ../../../CHANGELOG.md:158
  319. msgid "Support for running on Synology DSM"
  320. msgstr ""
  321. #: ../../../CHANGELOG.md:160
  322. msgid "Thanks to [cksit](https://github.com/cksit), the playbook can now run on [Synology DSM](https://www.synology.com/dsm) 7 and later."
  323. msgstr ""
  324. #: ../../../CHANGELOG.md:162
  325. msgid "Synology hosts are detected automatically (via `/etc/synoinfo.conf`), so other systems are unaffected. On DSM, the playbook uses the platform's native user management (`synouser`/`synogroup`), works around a Docker SDK incompatibility, and installs a small boot-fix service that handles a few DSM-specific boot quirks."
  326. msgstr ""
  327. #: ../../../CHANGELOG.md:164
  328. msgid "To get started, see the new [Configuring Synology DSM](./docs/configuring-playbook-synology.md) documentation page."
  329. msgstr ""
  330. #: ../../../CHANGELOG.md:166
  331. msgid "Mautrix bridges now expose their API (for Mautrix Manager and similar tools)"
  332. msgstr ""
  333. #: ../../../CHANGELOG.md:168
  334. msgid "The playbook now exposes the HTTP API of each [mautrix](https://github.com/mautrix) bridge, so tools like [Mautrix Manager](https://github.com/mautrix/manager) can help you log into them. This is especially useful for [mautrix-gmessages](./docs/configuring-playbook-bridge-mautrix-gmessages.md): Google has removed its QR-code login, leaving a [manual cookie-extraction flow](https://docs.mau.fi/bridges/go/gmessages/authentication.html) that tools like Mautrix Manager can streamline."
  335. msgstr ""
  336. #: ../../../CHANGELOG.md:170
  337. msgid "The API is exposed at `https://matrix.example.com/bridges/SERVICENAME` (for example, `https://matrix.example.com/bridges/gmessages`) and is advertised via a new `/.well-known/matrix/mautrix` file, so compatible tools can discover your bridges automatically. Such tools authenticate with your own Matrix access token, so no bridge secret needs to be shared with them."
  338. msgstr ""
  339. #: ../../../CHANGELOG.md:172
  340. msgid "This affects all mautrix bridges based on the new bridge framework (bluesky, gmessages, meta-instagram, meta-messenger, signal, slack, telegram, twitter and whatsapp) and is enabled by default."
  341. msgstr ""
  342. #: ../../../CHANGELOG.md:174
  343. msgid "To learn more (including how to turn it off), see the [Expose the bridge's API](./docs/configuring-playbook-bridge-mautrix-bridges.md#expose-the-bridges-api-for-mautrix-manager-and-similar-tools) section on our common mautrix bridges documentation page."
  344. msgstr ""
  345. #: ../../../CHANGELOG.md:176
  346. msgid "2026-06-28"
  347. msgstr ""
  348. #: ../../../CHANGELOG.md:178
  349. msgid "baibot now supports Venice, our recommended provider"
  350. msgstr ""
  351. #: ../../../CHANGELOG.md:180
  352. msgid "[baibot](./docs/configuring-playbook-bot-baibot.md) now ships a preset for the [Venice](./docs/configuring-playbook-bot-baibot.md#venice) provider, and it's the one we recommend. It's the most capable provider baibot supports (text generation with vision, file inputs and web search, speech-to-text, text-to-speech, and image generation and editing), and the only one that runs inference with no logging and no training on your data."
  353. msgstr ""
  354. #: ../../../CHANGELOG.md:182
  355. msgid "Enabling it takes a preset toggle and an API key:"
  356. msgstr ""
  357. #: ../../../CHANGELOG.md:190
  358. msgid "[OpenAI](https://openai.com/) and baibot's other providers remain fully supported. To get started, see the [Setting up baibot](./docs/configuring-playbook-bot-baibot.md#venice) documentation page."
  359. msgstr ""
  360. #: ../../../CHANGELOG.md:192
  361. msgid "2026-06-24"
  362. msgstr ""
  363. #: ../../../CHANGELOG.md:194
  364. msgid "Support for bridging to iMessage via RustPush"
  365. msgstr ""
  366. #: ../../../CHANGELOG.md:196
  367. msgid "Thanks to [jasonlaguidice](https://github.com/jasonlaguidice), the playbook now supports bridging to [iMessage](https://support.apple.com/messages) via a new [RustPush](https://github.com/OpenBubbles/rustpush)-based bridge ([jasonlaguidice/imessage](https://github.com/jasonlaguidice/imessage))."
  368. msgstr ""
  369. #: ../../../CHANGELOG.md:198
  370. msgid "Unlike the existing [mautrix-wsproxy](./docs/configuring-playbook-bridge-mautrix-wsproxy.md) iMessage bridge, this one talks directly to Apple's push notification service, so it needs neither a running Mac nor a wsproxy on the homeserver. Each user supplies a hardware key extracted from a Mac through the bridge bot's login flow."
  371. msgstr ""
  372. #: ../../../CHANGELOG.md:200
  373. msgid "To learn more, see our [Setting up RustPush (iMessage) bridging](./docs/configuring-playbook-bridge-rustpush.md) documentation page."
  374. msgstr ""
  375. #: ../../../CHANGELOG.md:202
  376. msgid "2026-05-24"
  377. msgstr ""
  378. #: ../../../CHANGELOG.md:204
  379. msgid "matrix-ldap-registration-proxy has been removed from the playbook"
  380. msgstr ""
  381. #: ../../../CHANGELOG.md:206
  382. msgid "The [matrix-ldap-registration-proxy](./docs/configuring-playbook-matrix-ldap-registration-proxy.md) service has been removed from the playbook, as the source code and the container image have become unavailable."
  383. msgstr ""
  384. #: ../../../CHANGELOG.md:208
  385. msgid "The playbook will let you know if you're using any `matrix_ldap_registration_proxy_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-matrix-ldap-registration-proxy.md#uninstalling-the-component-manually)."
  386. msgstr ""
  387. #: ../../../CHANGELOG.md:210
  388. msgid "2026-05-23"
  389. msgstr ""
  390. #: ../../../CHANGELOG.md:212
  391. msgid "Go-NEB has been removed from the playbook"
  392. msgstr ""
  393. #: ../../../CHANGELOG.md:214
  394. msgid "[Go-NEB](./docs/configuring-playbook-bot-go-neb.md) has been removed from the playbook, as it has been discontinued since June 2023."
  395. msgstr ""
  396. #: ../../../CHANGELOG.md:216
  397. msgid "The playbook will let you know if you're using any `matrix_bot_go_neb_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the bot manually](./docs/configuring-playbook-bot-go-neb.md#uninstalling-go-neb-manually)."
  398. msgstr ""
  399. #: ../../../CHANGELOG.md:218
  400. msgid "2026-05-19"
  401. msgstr ""
  402. #: ../../../CHANGELOG.md:220
  403. msgid "matrix-registration has been removed from the playbook"
  404. msgstr ""
  405. #: ../../../CHANGELOG.md:222
  406. msgid "The [matrix-registration](./docs/configuring-playbook-matrix-registration.md) service has been removed from the playbook, as it has been unmaintained (archived) since November, 2025."
  407. msgstr ""
  408. #: ../../../CHANGELOG.md:224
  409. msgid "The playbook will let you know if you're using any `matrix_registration_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-matrix-registration.md#uninstalling-the-component-manually)."
  410. msgstr ""
  411. #: ../../../CHANGELOG.md:226
  412. msgid "2026-05-18"
  413. msgstr ""
  414. #: ../../../CHANGELOG.md:228
  415. msgid "LiveKit Server has been upgraded to v1.12.0"
  416. msgstr ""
  417. #: ../../../CHANGELOG.md:230
  418. msgid "The playbook now ships [LiveKit Server](./docs/configuring-playbook-livekit-server.md) v1.12.0. See the [upstream release notes](https://github.com/livekit/livekit/releases/tag/v1.12.0) for details."
  419. msgstr ""
  420. #: ../../../CHANGELOG.md:232
  421. msgid "This release tightens TURN security:"
  422. msgstr ""
  423. #: ../../../CHANGELOG.md:234
  424. msgid "**TURN credentials now carry a TTL** (default: 300 seconds), exposed via `livekit_server_config_turn_ttl_seconds`."
  425. msgstr ""
  426. #: ../../../CHANGELOG.md:235
  427. msgid "**TURN no longer relays traffic to restricted peer CIDRs** (loopback, link-local, multicast, private, unspecified) by default. If your setup legitimately requires it, list the ranges in `livekit_server_config_turn_allow_restricted_peer_cidrs`."
  428. msgstr ""
  429. #: ../../../CHANGELOG.md:237
  430. msgid "For example, to allow TURN to reach the common [RFC1918](https://www.rfc-editor.org/rfc/rfc1918) private ranges, add to your `vars.yml`:"
  431. msgstr ""
  432. #: ../../../CHANGELOG.md:245
  433. msgid "Adjust the ranges to match your network. To deny specific CIDRs (taking precedence over the allow list above), use `livekit_server_config_turn_deny_peer_cidrs` in the same shape."
  434. msgstr ""
  435. #: ../../../CHANGELOG.md:248
  436. msgid "2026-05-07"
  437. msgstr ""
  438. #: ../../../CHANGELOG.md:250
  439. msgid "Tuwunel support"
  440. msgstr ""
  441. #: ../../../CHANGELOG.md:252
  442. msgid "Thanks to [Jason Volk](https://github.com/jevolk), the playbook now supports the [Tuwunel](./docs/configuring-playbook-tuwunel.md) homeserver as an optional alternative to Synapse."
  443. msgstr ""
  444. #: ../../../CHANGELOG.md:254
  445. msgid "Tuwunel is a fork of [conduwuit](./docs/configuring-playbook-conduwuit.md) written in Rust. The former conduwuit maintainer [endorses Tuwunel as conduwuit's successor](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/5200#issuecomment-4396211185). Like [Continuwuity](./docs/configuring-playbook-continuwuity.md), Tuwunel continues development on top of conduwuit's database format."
  446. msgstr ""
  447. #: ../../../CHANGELOG.md:256
  448. #: ../../../CHANGELOG.md:760
  449. #: ../../../CHANGELOG.md:973
  450. msgid "Existing installations do **not** need to be updated. **Synapse is still the default homeserver implementation** installed by the playbook."
  451. msgstr ""
  452. #: ../../../CHANGELOG.md:258
  453. msgid "People that used to run conduwuit may wish to [migrate from conduwuit to Tuwunel](./docs/configuring-playbook-tuwunel.md#migrating-from-conduwuit) via the new `tuwunel-migrate-from-conduwuit` tag, which performs an in-place binary-swap migration that reads the conduwuit database directly."
  454. msgstr ""
  455. #: ../../../CHANGELOG.md:260
  456. msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse/Conduit/Dendrite/Continuwuity to Tuwunel) without data loss. The exception is conduwuit, due to the shared database format."
  457. msgstr ""
  458. #: ../../../CHANGELOG.md:263
  459. msgid "2026-04-24"
  460. msgstr ""
  461. #: ../../../CHANGELOG.md:265
  462. msgid "Support for bridging to Meshtastic via meshtastic-matrix-relay"
  463. msgstr ""
  464. #: ../../../CHANGELOG.md:267
  465. msgid "Thanks to [luschmar](https://github.com/luschmar), the playbook now supports bridging to [Meshtastic](https://meshtastic.org/) mesh networks via [meshtastic-matrix-relay](https://github.com/jeremiah-k/meshtastic-matrix-relay) (mmrelay)."
  466. msgstr ""
  467. #: ../../../CHANGELOG.md:269
  468. msgid "To learn more, see our [Setting up a Matrix <-> Meshtastic bridge](./docs/configuring-playbook-bridge-meshtastic-relay.md) documentation page."
  469. msgstr ""
  470. #: ../../../CHANGELOG.md:271
  471. msgid "(BC Break) mautrix-telegram has been rewritten in Go (bridgev2)"
  472. msgstr ""
  473. #: ../../../CHANGELOG.md:273
  474. msgid "The [mautrix-telegram](./docs/configuring-playbook-bridge-mautrix-telegram.md) bridge has been [rewritten in Go](https://mau.fi/blog/2026-04-mautrix-release/) on top of the [bridgev2](https://docs.mau.fi/bridges/go/) architecture. See the [upstream v26.04 release notes](https://github.com/mautrix/telegram/releases/tag/v0.2604.0) for what changed in the bridge itself (shared-portal behavior, management-room state, new features, etc.)."
  475. msgstr ""
  476. #: ../../../CHANGELOG.md:275
  477. msgid "**Most users won't have to do anything.** If you use the playbook's integrated Postgres (the default) and haven't customized telegram-bridge variables beyond `matrix_mautrix_telegram_api_id` and `matrix_mautrix_telegram_api_hash`, just re-run the playbook; the bridge will migrate itself on first start. Taking a backup beforehand is still a good idea."
  478. msgstr ""
  479. #: ../../../CHANGELOG.md:277
  480. msgid "⚠️ **SQLite users: do not upgrade yet.** Upstream v0.2604.0 has a [known bug in the legacy SQLite migration](https://github.com/mautrix/telegram/releases/tag/v0.2604.0) that can corrupt your data. The playbook detects this case and will refuse to proceed. Either switch to Postgres first (set `matrix_mautrix_telegram_database_engine: postgres`; the playbook handles the pgloader migration), or wait for the next upstream release."
  481. msgstr ""
  482. #: ../../../CHANGELOG.md:279
  483. msgid "Playbook-specific things to know. The playbook will fail loudly if you're affected:"
  484. msgstr ""
  485. #: ../../../CHANGELOG.md:281
  486. msgid "Many `matrix_mautrix_telegram_*` variables have been **removed** (web-login endpoint, lottieconverter, username/alias/displayname templates, filter-mode, bot-token relaybot, Shared-Secret-Auth map). The deprecation check will tell you exactly what to rename or drop when you run the playbook."
  487. msgstr ""
  488. #: ../../../CHANGELOG.md:282
  489. msgid "**Old-style relaybot users** (`matrix_mautrix_telegram_bot_token`): switch to the common [mautrix bridge relay mode](./docs/configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional) via `matrix_mautrix_telegram_bridge_relay_enabled: true`."
  490. msgstr ""
  491. #: ../../../CHANGELOG.md:283
  492. msgid "**Shared-Secret-Auth double-puppeting users**: switch to [Appservice Double Puppet](./docs/configuring-playbook-appservice-double-puppet.md); the playbook wires it up automatically."
  493. msgstr ""
  494. #: ../../../CHANGELOG.md:284
  495. msgid "**Custom `matrix_mautrix_telegram_bridge_permissions`**: map `relaybot` to `relay`, `puppeting` to `user`, `full` to `user`. Validated at playbook time."
  496. msgstr ""
  497. #: ../../../CHANGELOG.md:286
  498. msgid "2026-04-03"
  499. msgstr ""
  500. #: ../../../CHANGELOG.md:288
  501. msgid "(BC Break) Synapse Admin (fork by etke.cc) is now Ketesa"
  502. msgstr ""
  503. #: ../../../CHANGELOG.md:290
  504. msgid "Synapse Admin has been rebranded to **[Ketesa](https://github.com/etkecc/ketesa)** — a landmark release that introduces a new identity, a full UI redesign, mobile-first layout, and deep Matrix Authentication Service (MAS) integration. For the full story behind the rename and a tour of what's new, see the [Ketesa v1.0.0 announcement](https://etke.cc/blog/introducing-ketesa/)."
  505. msgstr ""
  506. #: ../../../CHANGELOG.md:292
  507. msgid "Ketesa is a zero-configuration drop-in replacement for Synapse Admin: no server-side changes required, just update the role variables."
  508. msgstr ""
  509. #: ../../../CHANGELOG.md:294
  510. msgid "The `matrix-synapse-admin` role has been **renamed** to `matrix-ketesa`. All `matrix_synapse_admin_*` variables must be **renamed** to `matrix_ketesa_*` in your `vars.yml`."
  511. msgstr ""
  512. #: ../../../CHANGELOG.md:296
  513. msgid "Additionally, the **Docker image** changed from `ghcr.io/etkecc/synapse-admin` to `ghcr.io/etkecc/ketesa`. The default path prefix remains `/synapse-admin` for backward compatibility — updating to `/ketesa` is recommended but not required."
  514. msgstr ""
  515. #: ../../../CHANGELOG.md:298
  516. msgid "The playbook will automatically detect leftover `matrix_synapse_admin_*` variables and fail with a helpful message listing what needs to be renamed."
  517. msgstr ""
  518. #: ../../../CHANGELOG.md:300
  519. msgid "The playbook handles reverse-proxy routing for subpath deployments (e.g. `/ketesa`), including MAS-enabled setups — though OIDC auth flows on real servers still have some rough edges. Feedback is appreciated in [#ketesa:etke.cc](https://matrix.to/#/#ketesa:etke.cc)."
  520. msgstr ""
  521. #: ../../../CHANGELOG.md:302
  522. msgid "See the [Ketesa documentation](docs/configuring-playbook-ketesa.md) for details."
  523. msgstr ""
  524. #: ../../../CHANGELOG.md:304
  525. msgid "2026-04-02"
  526. msgstr ""
  527. #: ../../../CHANGELOG.md:306
  528. msgid "(BC Break) Draupnir for all Self Service Provisioning is now disabled by default"
  529. msgstr ""
  530. #: ../../../CHANGELOG.md:308
  531. msgid "💡 If you don't use [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md), then this breaking change does not concern you.."
  532. msgstr ""
  533. #: ../../../CHANGELOG.md:310
  534. msgid "[Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) now ships with `allowSelfServiceProvisioning: false` as default upstream and in this playbook."
  535. msgstr ""
  536. #: ../../../CHANGELOG.md:312
  537. msgid "This means users can no longer provision Draupnir instances by inviting the appservice bot unless you explicitly opt in."
  538. msgstr ""
  539. #: ../../../CHANGELOG.md:314
  540. msgid "Manual provisioning by administrators is now the recommended approach. You do not want to enable Self Service Provisioning unless you have additional custom safeguards like those used by asgard.chat in place."
  541. msgstr ""
  542. #: ../../../CHANGELOG.md:316
  543. msgid "If you want to enable Self Service Provisioning, add the following to your `vars.yml`:"
  544. msgstr ""
  545. #: ../../../CHANGELOG.md:323
  546. msgid "2026-03-23"
  547. msgstr ""
  548. #: ../../../CHANGELOG.md:325
  549. msgid "Migration validation system introduced"
  550. msgstr ""
  551. #: ../../../CHANGELOG.md:327
  552. msgid "Previously, when updating your setup, you had to remember to read the [CHANGELOG](CHANGELOG.md) file or risk breakage."
  553. msgstr ""
  554. #: ../../../CHANGELOG.md:329
  555. msgid "Now, the playbook includes a migration validation system that ensures you're aware of breaking changes before they affect your deployment. You're now forced to acknowledge each breaking change, unless you wish to live dangerously (see below)."
  556. msgstr ""
  557. #: ../../../CHANGELOG.md:332
  558. msgid "A new `matrix_playbook_migration_validated_version` variable has been introduced."
  559. msgstr ""
  560. #: ../../../CHANGELOG.md:334
  561. msgid "**New users** who started from the [example `vars.yml`](examples/vars.yml) file already have this variable set and do not need to do anything."
  562. msgstr ""
  563. #: ../../../CHANGELOG.md:336
  564. msgid "**Existing users** will need to add the following to their `vars.yml` file after reviewing all changelog entries up to now:"
  565. msgstr ""
  566. #: ../../../CHANGELOG.md:342
  567. msgid "Going forward, whenever a breaking change is introduced the playbook will:"
  568. msgstr ""
  569. #: ../../../CHANGELOG.md:344
  570. msgid "bump its expected version value (`matrix_playbook_migration_expected_version`), causing a discrepancy with what you validated (`matrix_playbook_migration_validated_version`)"
  571. msgstr ""
  572. #: ../../../CHANGELOG.md:346
  573. msgid "fail when you run it with a helpful message listing what changed and linking to the relevant changelog entries"
  574. msgstr ""
  575. #: ../../../CHANGELOG.md:348
  576. msgid "After reviewing and adapting your setup, you simply update the variable to the new version."
  577. msgstr ""
  578. #: ../../../CHANGELOG.md:350
  579. msgid "If you'd like to live dangerously and skip these checks (not recommended), you can set this once and be done with it:"
  580. msgstr ""
  581. #: ../../../CHANGELOG.md:356
  582. msgid "2026-03-19"
  583. msgstr ""
  584. #: ../../../CHANGELOG.md:358
  585. msgid "Matrix Authentication Service now prefers UNIX sockets for playbook-managed Postgres"
  586. msgstr ""
  587. #: ../../../CHANGELOG.md:360
  588. msgid "When [Matrix Authentication Service](docs/configuring-playbook-matrix-authentication-service.md) (MAS) uses the playbook-managed Postgres service, it now connects to it via a [UNIX socket](https://en.wikipedia.org/wiki/Unix_domain_socket) by default instead of TCP."
  589. msgstr ""
  590. #: ../../../CHANGELOG.md:362
  591. msgid "This follows the same approach [applied to Synapse](#synapse-now-prefers-unix-sockets-for-playbook-managed-postgres-and-valkey) and reduces unnecessary container-network wiring, keeping local IPC off the network stack."
  592. msgstr ""
  593. #: ../../../CHANGELOG.md:364
  594. msgid "If you use an external Postgres server for MAS, this does not change your setup."
  595. msgstr ""
  596. #: ../../../CHANGELOG.md:366
  597. #: ../../../CHANGELOG.md:382
  598. msgid "If you'd like to keep the previous TCP-based behavior, add the following configuration to your `vars.yml`:"
  599. msgstr ""
  600. #: ../../../CHANGELOG.md:372
  601. msgid "2026-03-17"
  602. msgstr ""
  603. #: ../../../CHANGELOG.md:374
  604. msgid "Synapse now prefers UNIX sockets for playbook-managed Postgres and Valkey"
  605. msgstr ""
  606. #: ../../../CHANGELOG.md:376
  607. msgid "When Synapse uses the playbook-managed Postgres and Valkey services, it now connects to them via [UNIX sockets](https://en.wikipedia.org/wiki/Unix_domain_socket) by default instead of TCP."
  608. msgstr ""
  609. #: ../../../CHANGELOG.md:378
  610. msgid "This reduces unnecessary container-network wiring and keeps local IPC off the network stack, which is a bit simpler and slightly more secure."
  611. msgstr ""
  612. #: ../../../CHANGELOG.md:380
  613. msgid "If you use an external Postgres server or external Redis/Valkey for Synapse, this does not change your setup."
  614. msgstr ""
  615. #: ../../../CHANGELOG.md:389
  616. msgid "2026-03-01"
  617. msgstr ""
  618. #: ../../../CHANGELOG.md:391
  619. msgid "(Potential BC Break) Synapse S3 media prefix is now applied consistently"
  620. msgstr ""
  621. #: ../../../CHANGELOG.md:393
  622. msgid "The `matrix_synapse_ext_synapse_s3_storage_provider_config_prefix` variable is now wired consistently for both:"
  623. msgstr ""
  624. #: ../../../CHANGELOG.md:395
  625. msgid "the Synapse `s3_storage_provider` module configuration"
  626. msgstr ""
  627. #: ../../../CHANGELOG.md:396
  628. msgid "the `matrix-synapse-s3-storage-provider-migrate` migration script (`s3_media_upload --prefix`)"
  629. msgstr ""
  630. #: ../../../CHANGELOG.md:398
  631. msgid "Previously, this variable could be set, but was not effectively applied by either of these paths."
  632. msgstr ""
  633. #: ../../../CHANGELOG.md:400
  634. msgid "**Affects**: users of [synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3-storage-provider.md) who have configured a non-empty `matrix_synapse_ext_synapse_s3_storage_provider_config_prefix` value."
  635. msgstr ""
  636. #: ../../../CHANGELOG.md:402
  637. msgid "If your bucket data was uploaded without the prefix before this fix, enabling proper prefix usage can make existing objects appear missing until data is migrated/copied to the prefixed key namespace."
  638. msgstr ""
  639. #: ../../../CHANGELOG.md:404
  640. msgid "2026-02-26"
  641. msgstr ""
  642. #: ../../../CHANGELOG.md:406
  643. msgid "Internal refactor: merged the Synapse reverse-proxy companion role into `matrix-synapse`"
  644. msgstr ""
  645. #: ../../../CHANGELOG.md:408
  646. msgid "The standalone `matrix-synapse-reverse-proxy-companion` role has been merged into the [matrix-synapse](roles/custom/matrix-synapse/) role."
  647. msgstr ""
  648. #: ../../../CHANGELOG.md:410
  649. msgid "This is not a user-facing change and does not change variable names (`matrix_synapse_reverse_proxy_companion_*` remain the same). The split looked clean on paper, but in practice both parts are tightly coupled through worker routing, tags (`setup-synapse`/`install-synapse`), and lifecycle ordering, so keeping them separate added coordination overhead with little practical benefit."
  650. msgstr ""
  651. #: ../../../CHANGELOG.md:412
  652. msgid "Compatibility note: existing companion-specific tags (`setup-synapse-reverse-proxy-companion` and `install-synapse-reverse-proxy-companion`) are still available."
  653. msgstr ""
  654. #: ../../../CHANGELOG.md:414
  655. msgid "With this change, Synapse and its reverse-proxy companion are managed in one role (`matrix-synapse`) while still keeping companion logic in dedicated task/template subdirectories for maintainability."
  656. msgstr ""
  657. #: ../../../CHANGELOG.md:416
  658. msgid "2026-02-21"
  659. msgstr ""
  660. #: ../../../CHANGELOG.md:418
  661. msgid "(BC Break) coturn is no longer auto-enabled by default"
  662. msgstr ""
  663. #: ../../../CHANGELOG.md:420
  664. msgid "By default, the [coturn](./docs/configuring-playbook-turn.md) TURN server component is no longer enabled for every deployment."
  665. msgstr ""
  666. #: ../../../CHANGELOG.md:422
  667. msgid "This reduces resources and attach surface for deployments which:"
  668. msgstr ""
  669. #: ../../../CHANGELOG.md:424
  670. msgid "either don't need calls at all"
  671. msgstr ""
  672. #: ../../../CHANGELOG.md:425
  673. msgid "or use the modern [Matrix RTC](docs/configuring-playbook-matrix-rtc.md)/[Element Call](docs/configuring-playbook-element-call.md) stack."
  674. msgstr ""
  675. #: ../../../CHANGELOG.md:427
  676. msgid "Coturn is still auto-enabled when [Jitsi](./docs/configuring-playbook-jitsi.md) is enabled (`jitsi_enabled: true`), because Jitsi still depends on TURN for legacy Matrix integration."
  677. msgstr ""
  678. #: ../../../CHANGELOG.md:429
  679. msgid "Additionally, Coturn (when enabled) now defaults to using automatic IP detection of your server's external IP address, instead of assuming your Ansible inventory (`ansible_host`) points to a public address and using it for configuring `coturn_turn_external_ip_address`."
  680. msgstr ""
  681. #: ../../../CHANGELOG.md:431
  682. msgid "To restore the old behavior (needed for legacy call setups), add the following configuration to your `vars.yml`:"
  683. msgstr ""
  684. #: ../../../CHANGELOG.md:440
  685. msgid "LiveKit TURN TLS is now automatically fronted by playbook-managed Traefik"
  686. msgstr ""
  687. #: ../../../CHANGELOG.md:442
  688. msgid "For deployments that use the playbook-managed Traefik reverse-proxy, LiveKit TURN over TCP is now SSL-terminated at Traefik and passed as plain TCP to LiveKit (`turn.external_tls = true`) by default."
  689. msgstr ""
  690. #: ../../../CHANGELOG.md:444
  691. msgid "To disable this behavior, set `livekit_server_config_turn_external_tls: false` and the playbook will revert to the old behavior - using traefik-certs-dumper to extract SSL certificates out of Traefik and pass them to LiveKit for explicit SSL termination there."
  692. msgstr ""
  693. #: ../../../CHANGELOG.md:446
  694. msgid "If you are using `other-traefik-container` or [another reverse-proxy](./configuring-playbook-own-webserver.md), this change does **not** switch behavior automatically. That mode remains using certificate files in the container (Traefik certificates dumper flow) unless you explicitly set the TURN-Traefik mode variables to opt in."
  695. msgstr ""
  696. #: ../../../CHANGELOG.md:448
  697. msgid "2026-02-17"
  698. msgstr ""
  699. #: ../../../CHANGELOG.md:450
  700. msgid "(BC Break) prometheus-nginxlog-exporter role has been relocated and variable names need adjustments"
  701. msgstr ""
  702. #: ../../../CHANGELOG.md:452
  703. msgid "The role for prometheus-nginxlog-exporter has been relocated to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization."
  704. msgstr ""
  705. #: ../../../CHANGELOG.md:454
  706. msgid "Along with the relocation, the `matrix_prometheus_nginxlog_exporter_` prefix on its variable names has been renamed to `prometheus_nginxlog_exporter_`, so you need to adjust your `vars.yml` configuration."
  707. msgstr ""
  708. #: ../../../CHANGELOG.md:456
  709. #: ../../../CHANGELOG.md:518
  710. #: ../../../CHANGELOG.md:528
  711. #: ../../../CHANGELOG.md:589
  712. #: ../../../CHANGELOG.md:611
  713. #: ../../../CHANGELOG.md:1146
  714. msgid "As always, the playbook would let you know about this and point out any variables you may have missed."
  715. msgstr ""
  716. #: ../../../CHANGELOG.md:458
  717. msgid "synapse-auto-invite-accept has been removed from the playbook"
  718. msgstr ""
  719. #: ../../../CHANGELOG.md:460
  720. msgid "[synapse-auto-invite-accept](./docs/configuring-playbook-synapse-auto-accept-invite.md) has been removed from the playbook, as the same functionality [has been integrated](https://github.com/element-hq/synapse/pull/17147) to Synapse since [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0)."
  721. msgstr ""
  722. #: ../../../CHANGELOG.md:462
  723. msgid "See [this section](./docs/configuring-playbook-synapse-auto-accept-invite.md#native-alternative) for details about how to enable the function on Synapse."
  724. msgstr ""
  725. #: ../../../CHANGELOG.md:464
  726. msgid "If you're using any `matrix_synapse_ext_synapse_auto_accept_invite_*` variables, the playbook will let you know which one you'll need to remove from `vars.yml`."
  727. msgstr ""
  728. #: ../../../CHANGELOG.md:466
  729. msgid "2026-02-16"
  730. msgstr ""
  731. #: ../../../CHANGELOG.md:468
  732. msgid "matrix-appservice-slack has been removed from the playbook"
  733. msgstr ""
  734. #: ../../../CHANGELOG.md:470
  735. msgid "[matrix-appservice-slack](./docs/configuring-playbook-bridge-appservice-slack.md) has been removed from the playbook, as it has been discontinued because the public Matrix.org Slack bridge has been decommissioned on January 14th, 2026."
  736. msgstr ""
  737. #: ../../../CHANGELOG.md:472
  738. msgid "The playbook will let you know if you're using any `matrix_appservice_slack_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-bridge-appservice-slack.md#uninstalling-the-component-manually)."
  739. msgstr ""
  740. #: ../../../CHANGELOG.md:474
  741. msgid "**Note**: Bridging to [Slack](https://slack.com) can also happen via the [mautrix-slack](./docs/configuring-playbook-bridge-mautrix-slack.md) bridge supported by the playbook."
  742. msgstr ""
  743. #: ../../../CHANGELOG.md:476
  744. msgid "2026-02-13"
  745. msgstr ""
  746. #: ../../../CHANGELOG.md:478
  747. msgid "Conditional service restart for `install-*` commands"
  748. msgstr ""
  749. #: ../../../CHANGELOG.md:480
  750. msgid "When running `install-all` or `install-service` (whether via `just` or raw `ansible-playbook`), only services whose configuration or container image actually changed during the playbook run will now be restarted. Unchanged services are left running (or get started if they were stopped). This reduces unnecessary downtime — particularly for services like Traefik (the reverse proxy), which previously caused brief connectivity interruptions on every playbook run even when nothing changed."
  751. msgstr ""
  752. #: ../../../CHANGELOG.md:482
  753. msgid "When running with `setup-*` tags (e.g. `setup-all`, `setup-synapse`), all services continue to be unconditionally restarted as before."
  754. msgstr ""
  755. #: ../../../CHANGELOG.md:484
  756. msgid "Currently, only Traefik tracks its own changes and benefits from conditional restart. All other services default to being restarted (the previous behavior). This is just the beginning — as more roles gain change-tracking support, playbook performance will improve and downtime will decrease dramatically, especially for `install-all` runs where most services haven't changed."
  757. msgstr ""
  758. #: ../../../CHANGELOG.md:486
  759. msgid "Some benchmarks for `just install-service traefik` when Traefik settings did not change:"
  760. msgstr ""
  761. #: ../../../CHANGELOG.md:488
  762. msgid "**Before**:"
  763. msgstr ""
  764. #: ../../../CHANGELOG.md:489
  765. msgid "total time: ~56 seconds 🐌"
  766. msgstr ""
  767. #: ../../../CHANGELOG.md:490
  768. msgid "Traefik restarted: yes (unnecessarily) ❌"
  769. msgstr ""
  770. #: ../../../CHANGELOG.md:491
  771. msgid "dependent services restarted: yes, all of them ❌"
  772. msgstr ""
  773. #: ../../../CHANGELOG.md:492
  774. msgid "**After**:"
  775. msgstr ""
  776. #: ../../../CHANGELOG.md:493
  777. msgid "total time: ~27 seconds ⚡"
  778. msgstr ""
  779. #: ../../../CHANGELOG.md:494
  780. msgid "Traefik restarted: no ✅"
  781. msgstr ""
  782. #: ../../../CHANGELOG.md:495
  783. msgid "dependent services restarted: no ✅"
  784. msgstr ""
  785. #: ../../../CHANGELOG.md:497
  786. msgid "This behavior can be overridden via `--extra-vars='devture_systemd_service_manager_conditional_restart_enabled=false'` to force unconditional restarts. See [Conditional service restart](docs/just.md#conditional-service-restart) for details."
  787. msgstr ""
  788. #: ../../../CHANGELOG.md:500
  789. msgid "2026-02-12"
  790. msgstr ""
  791. #: ../../../CHANGELOG.md:502
  792. msgid "Dimension integration manager has been removed from the playbook"
  793. msgstr ""
  794. #: ../../../CHANGELOG.md:504
  795. msgid "The [Dimension integration manager](./docs/configuring-playbook-dimension.md) has been removed from the playbook, as it has been unmaintained."
  796. msgstr ""
  797. #: ../../../CHANGELOG.md:506
  798. msgid "The playbook will let you know if you're using any `matrix_dimension_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-dimension.md#uninstalling-the-component-manually)."
  799. msgstr ""
  800. #: ../../../CHANGELOG.md:508
  801. msgid "(BC Break) Hydrogen role has been relocated and variable names need adjustments"
  802. msgstr ""
  803. #: ../../../CHANGELOG.md:510
  804. msgid "The role for Hydrogen has been relocated to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization."
  805. msgstr ""
  806. #: ../../../CHANGELOG.md:512
  807. msgid "Along with the relocation, the `matrix_client_hydrogen_` prefix was dropped from its variable names, so you need to adjust your `vars.yml` configuration."
  808. msgstr ""
  809. #: ../../../CHANGELOG.md:514
  810. #: ../../../CHANGELOG.md:607
  811. msgid "You need to do the following replacement:"
  812. msgstr ""
  813. #: ../../../CHANGELOG.md:516
  814. msgid "`matrix_client_hydrogen_` -> `hydrogen_`"
  815. msgstr ""
  816. #: ../../../CHANGELOG.md:520
  817. msgid "2026-02-11"
  818. msgstr ""
  819. #: ../../../CHANGELOG.md:522
  820. msgid "(BC Break) coturn role has been relocated and variable names need adjustments"
  821. msgstr ""
  822. #: ../../../CHANGELOG.md:524
  823. msgid "The role for coturn has been relocated to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization."
  824. msgstr ""
  825. #: ../../../CHANGELOG.md:526
  826. msgid "Along with the relocation, the `matrix_coturn_` prefix on its variable names has been renamed to `coturn_`, so you need to adjust your `vars.yml` configuration."
  827. msgstr ""
  828. #: ../../../CHANGELOG.md:530
  829. msgid "conduwuit has been removed from the playbook"
  830. msgstr ""
  831. #: ../../../CHANGELOG.md:532
  832. msgid "[conduwuit](./docs/configuring-playbook-conduwuit.md) has been removed from the playbook, as it has been abandoned."
  833. msgstr ""
  834. #: ../../../CHANGELOG.md:534
  835. msgid "The playbook will let you know if you're using any `matrix_conduwuit_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the service manually](./docs/configuring-playbook-conduwuit.md#uninstalling-the-service-manually)."
  836. msgstr ""
  837. #: ../../../CHANGELOG.md:536
  838. msgid "Since [Continuwuity](configuring-playbook-continuwuity.md) is a drop-in replacement for conduwuit, migration is possible. Please refer to [this section](./configuring-playbook-continuwuity.md#migrating-from-conduwuit) for details."
  839. msgstr ""
  840. #: ../../../CHANGELOG.md:538
  841. msgid "2026-02-09"
  842. msgstr ""
  843. #: ../../../CHANGELOG.md:540
  844. msgid "(BC Break) matrix-media-repo datastore IDs are now required in `vars.yml`"
  845. msgstr ""
  846. #: ../../../CHANGELOG.md:542
  847. msgid "**Affects**: users with [matrix-media-repo](docs/configuring-playbook-matrix-media-repo.md) enabled (`matrix_media_repo_enabled: true`)"
  848. msgstr ""
  849. #: ../../../CHANGELOG.md:544
  850. msgid "The `matrix_media_repo_datastore_file_id` and `matrix_media_repo_datastore_s3_id` variables are no longer auto-configured with values. They must now be explicitly defined in your `vars.yml` file. The playbook will fail with a helpful error if they are not set (when needed)."
  851. msgstr ""
  852. #: ../../../CHANGELOG.md:546
  853. msgid "These were never meant to be auto-configured. They were derived from `matrix_homeserver_generic_secret_key`, which is intended for secrets that are OK to change subsequently (and Ansible would assist in propagating these changes). matrix-media-repo datastore IDs are not secrets — they are static identifiers linking media to storage backends, and **must not change** after first use."
  854. msgstr ""
  855. #: ../../../CHANGELOG.md:548
  856. msgid "**For existing installations**, retrieve your current values from the server:"
  857. msgstr ""
  858. #: ../../../CHANGELOG.md:554
  859. msgid "Then add to your `vars.yml`:"
  860. msgstr ""
  861. #: ../../../CHANGELOG.md:563
  862. msgid "**Why do this?**: This change allows us to **remove the [passlib](https://passlib.readthedocs.io/en/stable/index.html) Python library** from the [prerequisites](docs/prerequisites.md), as it was the last component that depended on it."
  863. msgstr ""
  864. #: ../../../CHANGELOG.md:565
  865. msgid "2026-02-08"
  866. msgstr ""
  867. #: ../../../CHANGELOG.md:567
  868. msgid "Zulip bridge has been removed from the playbook"
  869. msgstr ""
  870. #: ../../../CHANGELOG.md:569
  871. msgid "Zulip bridge has been removed from the playbook, as it doesn't work, and the maintainer seems to have abandoned it. See [this issue](https://github.com/GearKite/MatrixZulipBridge/issues/23) for more context."
  872. msgstr ""
  873. #: ../../../CHANGELOG.md:571
  874. msgid "Switched to faster secret derivation for service passwords"
  875. msgstr ""
  876. #: ../../../CHANGELOG.md:573
  877. msgid "We've switched the method used for deriving service passwords (database passwords, appservice tokens, etc.) from the `matrix_homeserver_generic_secret_key` variable."
  878. msgstr ""
  879. #: ../../../CHANGELOG.md:575
  880. msgid "The old method used `password_hash('sha512', rounds=655555)` (655,555 rounds of SHA-512 hashing), which was designed for protecting low-entropy human passwords against brute-force attacks. For deriving secrets from an already high-entropy secret key, this many rounds provide no additional security - the secret key's entropy is what protects the derived passwords, not the computational cost of hashing."
  881. msgstr ""
  882. #: ../../../CHANGELOG.md:577
  883. msgid "The new method uses a single-round `hash('sha512')` with a unique salt per service. This is equally secure for this use case (SHA-512 remains preimage-resistant; brute-forcing a high-entropy key is infeasible regardless of rounds), while being dramatically faster."
  884. msgstr ""
  885. #: ../../../CHANGELOG.md:579
  886. msgid "On a fast mini PC, evaluating `postgres_managed_databases` (which references multiple database passwords) dropped from **~10.7 seconds to ~0.6 seconds**. The Postgres role evaluates this variable multiple times during a run, so the cumulative savings are significant. All other roles that reference derived passwords also benefit."
  887. msgstr ""
  888. #: ../../../CHANGELOG.md:581
  889. msgid "**What this means for users**: all derived service passwords (database passwords, appservice tokens, etc.) will change on the next playbook run. The main/superuser database password (`postgres_connection_password`) is not affected, as it is hardcoded in inventory variables rather than derived via hashing. All services will receive their new passwords as part of the same run, so this should be a seamless, non-user-impacting change."
  890. msgstr ""
  891. #: ../../../CHANGELOG.md:583
  892. msgid "(BC Break) Dynamic DNS role has been relocated and variable names need adjustments"
  893. msgstr ""
  894. #: ../../../CHANGELOG.md:585
  895. msgid "The role for Dynamic DNS has been relocated to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization."
  896. msgstr ""
  897. #: ../../../CHANGELOG.md:587
  898. msgid "Along with the relocation, the `matrix_dynamic_dns_` prefix on its variable names has been renamed to `ddclient_`, so you need to adjust your `vars.yml` configuration."
  899. msgstr ""
  900. #: ../../../CHANGELOG.md:591
  901. msgid "ma1sd has been removed from the playbook"
  902. msgstr ""
  903. #: ../../../CHANGELOG.md:593
  904. msgid "[ma1sd](./docs/configuring-playbook-ma1sd.md) has been removed from the playbook, as it has been unmaintained for a long time."
  905. msgstr ""
  906. #: ../../../CHANGELOG.md:595
  907. msgid "The playbook will let you know if you're using any `matrix_ma1sd_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-ma1sd.md#uninstalling-the-component-manually)."
  908. msgstr ""
  909. #: ../../../CHANGELOG.md:597
  910. msgid "Please note that some of the functions can be achieved with other components. For example, if you wish to implement LDAP integration, you might as well check out [the LDAP provider module for Synapse](./docs/configuring-playbook-ldap-auth.md) instead."
  911. msgstr ""
  912. #: ../../../CHANGELOG.md:599
  913. msgid "2026-02-07"
  914. msgstr ""
  915. #: ../../../CHANGELOG.md:601
  916. msgid "(BC Break) Cinny role has been relocated and variable names need adjustments"
  917. msgstr ""
  918. #: ../../../CHANGELOG.md:603
  919. msgid "The role for Cinny has been relocated to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization."
  920. msgstr ""
  921. #: ../../../CHANGELOG.md:605
  922. msgid "Along with the relocation, the `matrix_client_cinny_` prefix was dropped from its variable names, so you need to adjust your `vars.yml` configuration."
  923. msgstr ""
  924. #: ../../../CHANGELOG.md:609
  925. msgid "`matrix_client_cinny_` -> `cinny_`"
  926. msgstr ""
  927. #: ../../../CHANGELOG.md:613
  928. msgid "The Sliding Sync proxy has been removed from the playbook"
  929. msgstr ""
  930. #: ../../../CHANGELOG.md:615
  931. msgid "The [Sliding Sync proxy](./docs/configuring-playbook-sliding-sync-proxy.md) has been removed from the playbook, as it's been replaced with a different method (called Simplified Sliding Sync) integrated to newer homeservers by default (**Conduit** homeserver from version `0.6.0` or **Synapse** from version `1.114`)."
  932. msgstr ""
  933. #: ../../../CHANGELOG.md:617
  934. msgid "The playbook will let you know if you're using any `matrix_sliding_sync_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the proxy manually](./docs/configuring-playbook-sliding-sync-proxy.md#uninstalling-the-proxy-manually)."
  935. msgstr ""
  936. #: ../../../CHANGELOG.md:619
  937. msgid "2026-02-04"
  938. msgstr ""
  939. #: ../../../CHANGELOG.md:621
  940. msgid "baibot now supports OpenAI's built-in tools (Web Search and Code Interpreter)"
  941. msgstr ""
  942. #: ../../../CHANGELOG.md:623
  943. msgid "**TLDR**: if you're using the [OpenAI provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai) with [baibot](docs/configuring-playbook-bot-baibot.md), you can now enable [built-in tools](https://github.com/etkecc/baibot/blob/61d18b2/docs/features.md#%EF%B8%8F-built-in-tools-openai-only) (`web_search` and `code_interpreter`) to extend the model's capabilities."
  944. msgstr ""
  945. #: ../../../CHANGELOG.md:625
  946. msgid "These tools are **disabled by default** and can be enabled via Ansible variables for static agent configurations:"
  947. msgstr ""
  948. #: ../../../CHANGELOG.md:632
  949. msgid "Users who define agents dynamically at runtime will need to [update their agents](https://github.com/etkecc/baibot/blob/61d18b2/docs/agents.md#updating-agents) to enable these tools. See the [baibot v1.14.0 changelog](https://github.com/etkecc/baibot/blob/61d18b2/CHANGELOG.md) for details."
  950. msgstr ""
  951. #: ../../../CHANGELOG.md:634
  952. msgid "Whoami-based sync worker routing for improved sticky sessions for Synapse"
  953. msgstr ""
  954. #: ../../../CHANGELOG.md:636
  955. msgid "Deployments using [Synapse workers](./docs/configuring-playbook-synapse.md#load-balancing-with-workers) now benefit from improved sync worker routing via a new whoami-based mechanism (making use of the [whoami Matrix Client-Server API](https://spec.matrix.org/v1.17/client-server-api/#get_matrixclientv3accountwhoami))."
  956. msgstr ""
  957. #: ../../../CHANGELOG.md:638
  958. msgid "Previously, sticky routing for sync workers relied on parsing usernames from access tokens, which only worked with native Synapse tokens (`syt_<base64 username>_...`). This approach failed for [Matrix Authentication Service](docs/configuring-playbook-matrix-authentication-service.md) (MAS) deployments, where tokens are opaque and don't contain username information. This resulted in device-level stickiness (same token → same worker) rather than user-level stickiness (same user → same worker regardless of device), leading to suboptimal cache utilization on sync workers."
  959. msgstr ""
  960. #: ../../../CHANGELOG.md:640
  961. msgid "The new implementation calls Synapse's `/whoami` endpoint to resolve access tokens to usernames, enabling proper user-level sticky routing regardless of the authentication system in use (native Synapse auth, MAS, etc.). Results are cached to minimize overhead."
  962. msgstr ""
  963. #: ../../../CHANGELOG.md:642
  964. msgid "This change:"
  965. msgstr ""
  966. #: ../../../CHANGELOG.md:643
  967. msgid "**Automatically enables** when sync workers are configured (no action required)"
  968. msgstr ""
  969. #: ../../../CHANGELOG.md:644
  970. msgid "**Works universally** with any authentication system"
  971. msgstr ""
  972. #: ../../../CHANGELOG.md:645
  973. msgid "**Replaces the old implementation** entirely to keep the codebase simple"
  974. msgstr ""
  975. #: ../../../CHANGELOG.md:646
  976. msgid "**Adds minimal overhead** (one cached internal subrequest per sync request) for non-MAS deployments"
  977. msgstr ""
  978. #: ../../../CHANGELOG.md:648
  979. msgid "For debugging, you can enable verbose logging and/or response headers showing routing decisions:"
  980. msgstr ""
  981. #: ../../../CHANGELOG.md:659
  982. msgid "2025-12-09"
  983. msgstr ""
  984. #: ../../../CHANGELOG.md:661
  985. msgid "Traefik Cert Dumper upgrade"
  986. msgstr ""
  987. #: ../../../CHANGELOG.md:663
  988. msgid "The variable `traefik_certs_dumper_ssl_dir_path` was renamed to `traefik_certs_dumper_ssl_path`. Users who use [their own webserver with Traefik](docs/configuring-playbook-own-webserver.md) may need to adjust their configuration."
  989. msgstr ""
  990. #: ../../../CHANGELOG.md:665
  991. msgid "The variable `traefik_certs_dumper_dumped_certificates_dir_path` was renamed to `traefik_certs_dumper_dumped_certificates_path`. Users who use [SRV Server Delegation](docs/howto-srv-server-delegation.md) may need to adjust their configuration."
  992. msgstr ""
  993. #: ../../../CHANGELOG.md:667
  994. msgid "2025-11-23"
  995. msgstr ""
  996. #: ../../../CHANGELOG.md:669
  997. msgid "Matrix.to support"
  998. msgstr ""
  999. #: ../../../CHANGELOG.md:671
  1000. msgid "The playbook now supports [Matrix.to](https://github.com/matrix-org/matrix.to) — a simple URL redirection service which powers [matrix.to](https://matrix.to)."
  1001. msgstr ""
  1002. #: ../../../CHANGELOG.md:673
  1003. msgid "To learn more, see our [Setting up Matrix.to](docs/configuring-playbook-matrixto.md) documentation page."
  1004. msgstr ""
  1005. #: ../../../CHANGELOG.md:675
  1006. msgid "2025-11-09"
  1007. msgstr ""
  1008. #: ../../../CHANGELOG.md:677
  1009. msgid "matrix-appservice-webhooks has been removed from the playbook"
  1010. msgstr ""
  1011. #: ../../../CHANGELOG.md:679
  1012. msgid "[matrix-appservice-webhooks](./docs/configuring-playbook-bridge-appservice-webhooks.md) has been removed from the playbook, as it has been deprecated since more than several years."
  1013. msgstr ""
  1014. #: ../../../CHANGELOG.md:681
  1015. msgid "The playbook will let you know if you're using any `matrix_appservice_webhooks_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the bridge manually](./docs/configuring-playbook-bridge-appservice-webhooks.md#uninstalling-the-bridge-manually)."
  1016. msgstr ""
  1017. #: ../../../CHANGELOG.md:683
  1018. msgid "mautrix-facebook and mautrix-instagram have been removed from the playbook"
  1019. msgstr ""
  1020. #: ../../../CHANGELOG.md:685
  1021. msgid "[mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-facebook.md) and [mautrix-instagram](./docs/configuring-playbook-bridge-mautrix-instagram.md) have been removed from the playbook, as they have been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, integrated to the playbook at [2024-02-19](#2024-02-19)."
  1022. msgstr ""
  1023. #: ../../../CHANGELOG.md:687
  1024. #: ../../../CHANGELOG.md:719
  1025. msgid "The playbook will let you know if you're using any variables for those bridges:"
  1026. msgstr ""
  1027. #: ../../../CHANGELOG.md:689
  1028. msgid "`matrix_mautrix_facebook_*`"
  1029. msgstr ""
  1030. #: ../../../CHANGELOG.md:690
  1031. msgid "`matrix_mautrix_instagram_*`"
  1032. msgstr ""
  1033. #: ../../../CHANGELOG.md:692
  1034. #: ../../../CHANGELOG.md:726
  1035. msgid "You'll need to remove them from `vars.yml` and potentially uninstall them manually. Consult pages below for details:"
  1036. msgstr ""
  1037. #: ../../../CHANGELOG.md:694
  1038. msgid "[Instruction for mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-facebook.md#uninstalling-the-bridge-manually)"
  1039. msgstr ""
  1040. #: ../../../CHANGELOG.md:695
  1041. msgid "[Instruction for mautrix-instagram](./docs/configuring-playbook-bridge-mautrix-instagram.md#uninstalling-the-bridge-manually)"
  1042. msgstr ""
  1043. #: ../../../CHANGELOG.md:697
  1044. msgid "2025-11-08"
  1045. msgstr ""
  1046. #: ../../../CHANGELOG.md:699
  1047. msgid "MatrixZulipBridge support"
  1048. msgstr ""
  1049. #: ../../../CHANGELOG.md:701
  1050. msgid "Thanks to [Suguru Hirahara](https://github.com/luixxiul), the playbook now supports the [GearKite/MatrixZulipBridge](https://github.com/GearKite/MatrixZulipBridg) bridge for bridging Matrix to [Zulip](https://zulip.com/)."
  1051. msgstr ""
  1052. #: ../../../CHANGELOG.md:703
  1053. msgid "To learn more, see our [Setting up Zulip bridging](docs/configuring-playbook-bridge-zulip.md) documentation page."
  1054. msgstr ""
  1055. #: ../../../CHANGELOG.md:705
  1056. msgid "2025-11-07"
  1057. msgstr ""
  1058. #: ../../../CHANGELOG.md:707
  1059. msgid "The matrix-chatgpt-bot has been removed from the playbook"
  1060. msgstr ""
  1061. #: ../../../CHANGELOG.md:709
  1062. msgid "The [matrix-bot-chatgpt](./docs/configuring-playbook-bot-chatgpt.md) has been removed from the playbook, as it has been deprecated since September 2024."
  1063. msgstr ""
  1064. #: ../../../CHANGELOG.md:711
  1065. msgid "The playbook will let you know if you're using any `matrix_bot_chatgpt_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the bot manually](./docs/configuring-playbook-bot-chatgpt.md#uninstalling-matrix-chatgpt-bot-manually)."
  1066. msgstr ""
  1067. #: ../../../CHANGELOG.md:713
  1068. msgid "2025-11-05"
  1069. msgstr ""
  1070. #: ../../../CHANGELOG.md:715
  1071. msgid "The MX Puppet bridges for Discord, Instagram, Slack, and Twitter have been removed from the playbook"
  1072. msgstr ""
  1073. #: ../../../CHANGELOG.md:717
  1074. msgid "The MX Puppet bridges for Discord, Instagram, Slack, and Twitter have been removed from the playbook, as they have been unmaintained for more than several years and do not support important features like authenticated media. See [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3867) for the context."
  1075. msgstr ""
  1076. #: ../../../CHANGELOG.md:721
  1077. msgid "`matrix_mx_puppet_discord_*`"
  1078. msgstr ""
  1079. #: ../../../CHANGELOG.md:722
  1080. msgid "`matrix_mx_puppet_instagram_*`"
  1081. msgstr ""
  1082. #: ../../../CHANGELOG.md:723
  1083. msgid "`matrix_mx_puppet_slack_*`"
  1084. msgstr ""
  1085. #: ../../../CHANGELOG.md:724
  1086. msgid "`matrix_mx_puppet_twitter_*`"
  1087. msgstr ""
  1088. #: ../../../CHANGELOG.md:728
  1089. msgid "[Instruction for MX Puppet Discord bridge](./docs/configuring-playbook-bridge-mx-puppet-discord.md#uninstalling-the-bridge-manually)"
  1090. msgstr ""
  1091. #: ../../../CHANGELOG.md:729
  1092. msgid "[Instruction for MX Puppet Instagram bridge](./docs/configuring-playbook-bridge-mx-puppet-instagram.md#uninstalling-the-bridge-manually)"
  1093. msgstr ""
  1094. #: ../../../CHANGELOG.md:730
  1095. msgid "[Instruction for MX Puppet Slack bridge](./docs/configuring-playbook-bridge-mx-puppet-slack.md#uninstalling-the-bridge-manually)"
  1096. msgstr ""
  1097. #: ../../../CHANGELOG.md:731
  1098. msgid "[Instruction for MX Puppet Twitter bridge](./docs/configuring-playbook-bridge-mx-puppet-twitter.md#uninstalling-the-bridge-manually)"
  1099. msgstr ""
  1100. #: ../../../CHANGELOG.md:733
  1101. msgid "2025-11-04"
  1102. msgstr ""
  1103. #: ../../../CHANGELOG.md:735
  1104. msgid "The Go Skype bridge has been removed from the playbook"
  1105. msgstr ""
  1106. #: ../../../CHANGELOG.md:737
  1107. msgid "The [go-skype-bridge](./docs/configuring-playbook-bridge-go-skype-bridge.md) has been removed from the playbook, as Skype has been discontinued since the May 2025."
  1108. msgstr ""
  1109. #: ../../../CHANGELOG.md:739
  1110. msgid "The playbook will let you know if you're using any `matrix_go_skype_bridge_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the bridge manually](./docs/configuring-playbook-bridge-go-skype-bridge.md#uninstalling-the-bridge-manually)."
  1111. msgstr ""
  1112. #: ../../../CHANGELOG.md:741
  1113. msgid "2025-10-02"
  1114. msgstr ""
  1115. #: ../../../CHANGELOG.md:743
  1116. msgid "Element Admin support"
  1117. msgstr ""
  1118. #: ../../../CHANGELOG.md:745
  1119. msgid "The playbook now supports [Element Admin](./docs/configuring-playbook-element-admin.md) - a new web-based administration panel for Synapse and [Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md)."
  1120. msgstr ""
  1121. #: ../../../CHANGELOG.md:747
  1122. msgid "Deployments based on Matrix Authentication Service may find it useful to run both Synapse Admin and Element Admin at the same time."
  1123. msgstr ""
  1124. #: ../../../CHANGELOG.md:749
  1125. msgid "Deployments that don't rely on Matrix Authentication Service are unlikely to find anything useful in Element Admin right now (it's too basic in its current form)."
  1126. msgstr ""
  1127. #: ../../../CHANGELOG.md:752
  1128. msgid "2025-04-26"
  1129. msgstr ""
  1130. #: ../../../CHANGELOG.md:754
  1131. msgid "Continuwuity support"
  1132. msgstr ""
  1133. #: ../../../CHANGELOG.md:756
  1134. msgid "Thanks to [Virkkunen](https://github.com/Virkkunen), we now have optional experimental [Continuwuity](./docs/configuring-playbook-continuwuity.md) homeserver support."
  1135. msgstr ""
  1136. #: ../../../CHANGELOG.md:758
  1137. msgid "Continuwuity is a fork of [conduwuit](./docs/configuring-playbook-conduwuit.md), which the playbook also supports. It appears that conduwuit has been abandoned and various forks (like Continuwuity, [Tuwunel](https://github.com/matrix-construct/tuwunel) and possibly others) are continuing in its path."
  1138. msgstr ""
  1139. #: ../../../CHANGELOG.md:762
  1140. msgid "People that used to run conduwuit, may wish to:"
  1141. msgstr ""
  1142. #: ../../../CHANGELOG.md:764
  1143. msgid "either [migrate from conduwuit to Continuwuity](./docs/configuring-playbook-continuwuity.md#migrating-from-conduwuit)"
  1144. msgstr ""
  1145. #: ../../../CHANGELOG.md:765
  1146. msgid "or wait for some of the other forks to progress and for support for them to get added to the playbook"
  1147. msgstr ""
  1148. #: ../../../CHANGELOG.md:767
  1149. msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse/Conduit/Dendrite to Continuwuity) without data loss."
  1150. msgstr ""
  1151. #: ../../../CHANGELOG.md:770
  1152. msgid "2025-04-09"
  1153. msgstr ""
  1154. #: ../../../CHANGELOG.md:772
  1155. msgid "Element Call frontend installation is now optional"
  1156. msgstr ""
  1157. #: ../../../CHANGELOG.md:774
  1158. msgid "Because all Element clients (Element Web and Element X mobile) now embed and use their own Element Call frontend application (and not the one hosted via the playbook), it makes little sense for the playbook to self-host the Element Call frontend for you. Setting up the frontend requires an additional hostname (DNS setup) and it won't be used by Element clients anyway, so **we now recommend not installing the Element Call frontend**."
  1159. msgstr ""
  1160. #: ../../../CHANGELOG.md:776
  1161. msgid "💡 A reason you may wish to continue installing the Element Call frontend (despite Matrix clients not making use of it), is if you need to use it standalone - directly via a browser (without a Matrix client)."
  1162. msgstr ""
  1163. #: ../../../CHANGELOG.md:778
  1164. msgid "The playbook now lets you [Decide between Element Call vs just the Matrix RTC stack](./docs/configuring-playbook-element-call.md#decide-between-element-call-vs-just-the-matrix-rtc-stack)."
  1165. msgstr ""
  1166. #: ../../../CHANGELOG.md:780
  1167. msgid "If you've already installed Element Call (via `matrix_element_call_enabled: true`), you can switch to installing just the [Matrix RTC (Real-Time Communication) stack](./docs/configuring-playbook-matrix-rtc.md) (all supporting services **without the Element Call frontend**) by:"
  1168. msgstr ""
  1169. #: ../../../CHANGELOG.md:782
  1170. msgid "Adjusting your `vars.yml` configuration like this:"
  1171. msgstr ""
  1172. #: ../../../CHANGELOG.md:789
  1173. msgid "[Re-running the playbook](./docs/installing.md) with the `setup-all` Ansible tag (e.g. `just setup-all`)"
  1174. msgstr ""
  1175. #: ../../../CHANGELOG.md:791
  1176. msgid "Getting rid of the `call.element.example.com` DNS record"
  1177. msgstr ""
  1178. #: ../../../CHANGELOG.md:794
  1179. msgid "2025-03-15"
  1180. msgstr ""
  1181. #: ../../../CHANGELOG.md:796
  1182. msgid "Element Call support"
  1183. msgstr ""
  1184. #: ../../../CHANGELOG.md:798
  1185. msgid "The playbook now supports [Element Call](https://github.com/element-hq/element-call) as an optional feature. Thanks to [wjbeckett](https://github.com/wjbeckett) for getting us started via [PR#3562](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3562)."
  1186. msgstr ""
  1187. #: ../../../CHANGELOG.md:800
  1188. msgid "Element Call is a native Matrix video conferencing application developed by [Element](https://element.io/) that has the goal of replacing [Jitsi](./docs/configuring-playbook-jitsi.md) and the old WebRTC stack used in previous Element versions."
  1189. msgstr ""
  1190. #: ../../../CHANGELOG.md:802
  1191. msgid "💡 For now, Element Call is only supported with the [Synapse](docs/configuring-playbook-synapse.md) homeserver (with [federation](docs/configuring-playbook-federation.md) enabled) and [Element Web](docs/configuring-playbook-client-element-web.md) and Element X mobile clients. See the [Prerequisites](docs/configuring-playbook-element-call.md#prerequisites) section of the [Element Call documentation](docs/configuring-playbook-element-call.md) for more details."
  1192. msgstr ""
  1193. #: ../../../CHANGELOG.md:804
  1194. msgid "To get started, see the [Configuring Element Call](docs/configuring-playbook-element-call.md) documentation page."
  1195. msgstr ""
  1196. #: ../../../CHANGELOG.md:807
  1197. msgid "2025-03-08"
  1198. msgstr ""
  1199. #: ../../../CHANGELOG.md:809
  1200. msgid "6️⃣ IPv6 support enablement recommended by default"
  1201. msgstr ""
  1202. #: ../../../CHANGELOG.md:811
  1203. msgid "Our [default example configuration](./examples/vars.yml) and [Configuring DNS](./docs/configuring-dns.md) guides now recommend enabling [IPv6](https://en.wikipedia.org/wiki/IPv6) support. We recommend that everyone enables IPv6 support for their Matrix server, even if they don't have IPv6 connectivity yet."
  1204. msgstr ""
  1205. #: ../../../CHANGELOG.md:813
  1206. msgid "Our new [Configuring IPv6](./docs/configuring-ipv6.md) documentation page has more details about the playbook's IPv6 support."
  1207. msgstr ""
  1208. #: ../../../CHANGELOG.md:815
  1209. msgid "**Existing playbook users** will **need to do some manual work** to enable IPv6 support. This consists of:"
  1210. msgstr ""
  1211. #: ../../../CHANGELOG.md:817
  1212. msgid "enabling IPv6 support for the Docker container networks:"
  1213. msgstr ""
  1214. #: ../../../CHANGELOG.md:818
  1215. msgid "add `devture_systemd_docker_base_ipv6_enabled: true` to their `vars.yml` configuration file"
  1216. msgstr ""
  1217. #: ../../../CHANGELOG.md:819
  1218. msgid "stop all services (`just stop-all`)"
  1219. msgstr ""
  1220. #: ../../../CHANGELOG.md:820
  1221. msgid "delete all container networks on the server: `docker network rm $(docker network ls -q)`"
  1222. msgstr ""
  1223. #: ../../../CHANGELOG.md:821
  1224. msgid "re-run the playbook fully: `just install-all`"
  1225. msgstr ""
  1226. #: ../../../CHANGELOG.md:823
  1227. msgid "[configuring IPv6 (`AAAA`) DNS records](./docs/configuring-ipv6.md#configuring-dns-records-for-ipv6)"
  1228. msgstr ""
  1229. #: ../../../CHANGELOG.md:825
  1230. msgid "2025-02-26"
  1231. msgstr ""
  1232. #: ../../../CHANGELOG.md:827
  1233. msgid "🪦 Bye-bye, Email2Matrix"
  1234. msgstr ""
  1235. #: ../../../CHANGELOG.md:829
  1236. msgid "The [Email2Matrix](./docs/configuring-playbook-email2matrix.md) service has been superseded by the [Postmoogle](./docs/configuring-playbook-bridge-postmoogle.md) bridge for a long time now and was completely removed from the playbook today."
  1237. msgstr ""
  1238. #: ../../../CHANGELOG.md:831
  1239. msgid "If you still have the Email2Matrix component installed on your Matrix server, the playbook can no longer help you uninstall it and you will need to do it manually as described in the [Uninstalling Email2Matrix manually](./docs/configuring-playbook-email2matrix.md#uninstalling-email2matrix-manually) section of the documentation. The playbook will warn you if there are any `matrix_email2matrix_*` variables still remaining in your configuration."
  1240. msgstr ""
  1241. #: ../../../CHANGELOG.md:834
  1242. msgid "2025-02-23"
  1243. msgstr ""
  1244. #: ../../../CHANGELOG.md:836
  1245. msgid "The playbook defaults to exposing the Coturn STUN port (3478) over UDP once again"
  1246. msgstr ""
  1247. #: ../../../CHANGELOG.md:838
  1248. msgid "Recently, we made the playbook [default to exposing the Coturn STUN port (3478) only over TCP](#the-playbook-now-defaults-to-exposing-the-coturn-stun-port-3478-only-over-tcp) to reduce the severity of DDoS amplification/reflection attacks."
  1249. msgstr ""
  1250. #: ../../../CHANGELOG.md:840
  1251. msgid "It seems like old Element clients on mobile devices only support talking to the STUN port over UDP, not TCP. To accommodate such ancient clients, we're now **reversing this change** and **defaulting to exposing the Coturn STUN port (3478) over UDP once again**."
  1252. msgstr ""
  1253. #: ../../../CHANGELOG.md:843
  1254. msgid "In light of this new information, you have 2 options:"
  1255. msgstr ""
  1256. #: ../../../CHANGELOG.md:845
  1257. msgid "**If you already adapted to the previous change and would like to adapt to this change one again**:"
  1258. msgstr ""
  1259. #: ../../../CHANGELOG.md:847
  1260. msgid "make sure the `3478/udp` port is whitelisted in your external firewall (if you have one) once again."
  1261. msgstr ""
  1262. #: ../../../CHANGELOG.md:849
  1263. msgid "**If you don't care about old Element clients and wish to reduce the severity of DDoS amplification/reflection attacks**:"
  1264. msgstr ""
  1265. #: ../../../CHANGELOG.md:851
  1266. msgid "Consider closing the STUN/UDP port with the following configuration:"
  1267. msgstr ""
  1268. #: ../../../CHANGELOG.md:857
  1269. msgid "Consider keeping `3478/udp` blocked in your external firewall (if you have one)"
  1270. msgstr ""
  1271. #: ../../../CHANGELOG.md:859
  1272. msgid "2025-02-21"
  1273. msgstr ""
  1274. #: ../../../CHANGELOG.md:861
  1275. msgid "Docker daemon options are no longer adjusted when IPv6 is enabled"
  1276. msgstr ""
  1277. #: ../../../CHANGELOG.md:863
  1278. msgid "We landed [initial IPv6 support](#initial-work-on-ipv6-support) in the past via a `devture_systemd_docker_base_ipv6_enabled` variable that one had to toggle to `true`."
  1279. msgstr ""
  1280. #: ../../../CHANGELOG.md:865
  1281. msgid "This variable did **2 different things at once**:"
  1282. msgstr ""
  1283. #: ../../../CHANGELOG.md:867
  1284. msgid "ensured that container networks were created with IPv6 being enabled"
  1285. msgstr ""
  1286. #: ../../../CHANGELOG.md:868
  1287. msgid "adjusted the Docker daemon's configuration to set `experimental: true` and `ip6tables: true` (a necessary prerequisite for creating IPv6-enabled networks)"
  1288. msgstr ""
  1289. #: ../../../CHANGELOG.md:870
  1290. msgid "Since Docker 27.0.1's [changes to how it handles IPv6](https://docs.docker.com/engine/release-notes/27/#ipv6), **adjusting the Docker daemon's configuration is no longer necessary**, because:"
  1291. msgstr ""
  1292. #: ../../../CHANGELOG.md:871
  1293. msgid "`ip6tables` defaults to `true` for everyone"
  1294. msgstr ""
  1295. #: ../../../CHANGELOG.md:872
  1296. msgid "`ip6tables` is out of the experimental phase, so `experimental` is no longer necessary"
  1297. msgstr ""
  1298. #: ../../../CHANGELOG.md:874
  1299. msgid "In light of this, we're introducing a new variable (`devture_systemd_docker_base_ipv6_daemon_options_changing_enabled`) for controlling if IPv6 should be force-enabled in the Docker daemon's configuration options. Since most people should be on a modern enough Docker daemon version which doesn't require such changes, this variable defaults to `false`."
  1300. msgstr ""
  1301. #: ../../../CHANGELOG.md:877
  1302. msgid "This change affects you like this:"
  1303. msgstr ""
  1304. #: ../../../CHANGELOG.md:879
  1305. msgid "✅ if you're **not explicitly enabling IPv6** (via `devture_systemd_docker_base_ipv6_enabled` in your configuration): you're unaffected"
  1306. msgstr ""
  1307. #: ../../../CHANGELOG.md:880
  1308. msgid "❓ if you're **explicitly enabling IPv6** (via `devture_systemd_docker_base_ipv6_enabled` in your configuration):"
  1309. msgstr ""
  1310. #: ../../../CHANGELOG.md:881
  1311. msgid "✅ .. and you're on a modern enough Docker version (which you most likely are): the playbook will no longer mess with your Docker daemon options. You're unaffected."
  1312. msgstr ""
  1313. #: ../../../CHANGELOG.md:882
  1314. msgid "🔧 .. and you're on an old Docker version, you **are affected** and need to use the following configuration to restore the old behavior:"
  1315. msgstr ""
  1316. #: ../../../CHANGELOG.md:893
  1317. msgid "Support for bridging to Bluesky via mautrix-bluesky"
  1318. msgstr ""
  1319. #: ../../../CHANGELOG.md:895
  1320. msgid "Thanks to [Zepmann](https://github.com/Zepmann), the playbook now supports bridging to [Bluesky](https://bsky.app/) via [mautrix-bluesky](https://github.com/mautrix/bluesky)."
  1321. msgstr ""
  1322. #: ../../../CHANGELOG.md:897
  1323. msgid "To learn more, see our [Setting up mautrix-bluesky](./docs/configuring-playbook-bridge-mautrix-bluesky.md) documentation page."
  1324. msgstr ""
  1325. #: ../../../CHANGELOG.md:900
  1326. msgid "2025-02-19"
  1327. msgstr ""
  1328. #: ../../../CHANGELOG.md:902
  1329. msgid "The playbook now defaults to exposing the Coturn STUN port (3478) only over TCP"
  1330. msgstr ""
  1331. #: ../../../CHANGELOG.md:904
  1332. msgid "We've previously done some work to **decrease the severity** of DDoS amplification attacks done through the [Coturn](./docs/configuring-playbook-turn.md)'s STUN port (2.8x -> 1.6x) as reported in [coturn: Lower DDoS amplification/reflection factor from 2.8 to 1.6 #2592](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2592)."
  1333. msgstr ""
  1334. #: ../../../CHANGELOG.md:906
  1335. msgid "To **completely eliminate the problem** of DDoS amplification attacks done through the [Coturn](./docs/configuring-playbook-turn.md) STUN port even further (read more about this in [this article](https://stormwall.network/resources/blog/protect-against-ddos-based-on-stun-exploit)), the playbook now **disables exposure of the Coturn STUN port (`3478`) over UDP**. This is a bit heavy-handed, but is probably the only way to completely eliminate the problem."
  1336. msgstr ""
  1337. #: ../../../CHANGELOG.md:908
  1338. msgid "The playbook now **only exposes the Coturn STUN port (`3478`) over TCP by default**."
  1339. msgstr ""
  1340. #: ../../../CHANGELOG.md:910
  1341. msgid "💡 Users may wish to further remove the (now unnecessary) firewall rule allowing access to `3478/udp`."
  1342. msgstr ""
  1343. #: ../../../CHANGELOG.md:912
  1344. msgid "If you'd like the Coturn STUN port to be exposed over UDP like before, you can revert to the previous behavior by using the following configuration in your `vars.yml` file:"
  1345. msgstr ""
  1346. #: ../../../CHANGELOG.md:919
  1347. msgid "People running Coturn directly on the `host` network (using `coturn_container_network: host`) will still have the STUN port exposed over UDP, as port exposure is done directly via Coturn and not via Docker. In such cases, the playbook cannot prevent `3478/udp` port exposure and you'd need to do it in another way (separate firewall rule, etc)."
  1348. msgstr ""
  1349. #: ../../../CHANGELOG.md:922
  1350. msgid "2025-02-17"
  1351. msgstr ""
  1352. #: ../../../CHANGELOG.md:924
  1353. msgid "FluffyChat Web support"
  1354. msgstr ""
  1355. #: ../../../CHANGELOG.md:926
  1356. msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports [FluffyChat Web](https://github.com/krille-chan/fluffychat) as an additional Matrix client you can self-host."
  1357. msgstr ""
  1358. #: ../../../CHANGELOG.md:928
  1359. msgid "To learn more, see our [Setting up FluffyChat Web](docs/configuring-playbook-client-fluffychat-web.md) documentation page."
  1360. msgstr ""
  1361. #: ../../../CHANGELOG.md:931
  1362. msgid "2025-02-03"
  1363. msgstr ""
  1364. #: ../../../CHANGELOG.md:933
  1365. msgid "The mautrix-hangouts bridge has been removed from the playbook"
  1366. msgstr ""
  1367. #: ../../../CHANGELOG.md:935
  1368. msgid "The [mautrix-hangouts](./docs/configuring-playbook-bridge-mautrix-hangouts.md) bridge has been deprecated in the playbook since December 2024 and finally got completely removed from the playbook in February 2025."
  1369. msgstr ""
  1370. #: ../../../CHANGELOG.md:937
  1371. msgid "This is because Google Hangouts has been discontinued since the 1st of November 2022."
  1372. msgstr ""
  1373. #: ../../../CHANGELOG.md:939
  1374. msgid "The playbook will let you know if you're using any `matrix_mautrix_hangouts_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the bridge manually](./docs/configuring-playbook-bridge-mautrix-hangouts.md#uninstalling-the-bridge-manually)."
  1375. msgstr ""
  1376. #: ../../../CHANGELOG.md:942
  1377. msgid "2025-01-27"
  1378. msgstr ""
  1379. #: ../../../CHANGELOG.md:944
  1380. msgid "Redis and KeyDB are no longer part of the playbook"
  1381. msgstr ""
  1382. #: ../../../CHANGELOG.md:946
  1383. msgid "**TLDR**: The playbook now exclusively uses Valkey as its Redis-compatible memorystore implementation, removing support for Redis and KeyDB. Most users are unaffected by this change unless they explicitly configured Redis or KeyDB variables. Only users that were explicitly defining `redis_*` or `keydb_*` variables will need to update their configuration to use `valkey_*` variables instead."
  1384. msgstr ""
  1385. #: ../../../CHANGELOG.md:948
  1386. msgid "The playbook has gone through several iterations of memorystore implementations:"
  1387. msgstr ""
  1388. #: ../../../CHANGELOG.md:950
  1389. msgid "It initially used Redis, auto-installing it when needed by features/services"
  1390. msgstr ""
  1391. #: ../../../CHANGELOG.md:951
  1392. msgid "[Switched to KeyDB](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis) as the default, while keeping Redis support for those who wished to remain on Redis"
  1393. msgstr ""
  1394. #: ../../../CHANGELOG.md:952
  1395. msgid "[Switched to Valkey](#backward-compatibility-break-the-playbook-now-defaults-to-valkey-instead-of-keydb) due to [KeyDB issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3544), while keeping Redis and KeyDB support, for those who wished to remain on them"
  1396. msgstr ""
  1397. #: ../../../CHANGELOG.md:954
  1398. msgid "To reduce configuration complexity and maintenance overhead, we are now:"
  1399. msgstr ""
  1400. #: ../../../CHANGELOG.md:956
  1401. msgid "removing Redis and KeyDB support entirely"
  1402. msgstr ""
  1403. #: ../../../CHANGELOG.md:957
  1404. msgid "using Valkey as the sole Redis-compatible memorystore implementation"
  1405. msgstr ""
  1406. #: ../../../CHANGELOG.md:959
  1407. msgid "To update your configuration:"
  1408. msgstr ""
  1409. #: ../../../CHANGELOG.md:961
  1410. msgid "**Most users** don't need to do anything"
  1411. msgstr ""
  1412. #: ../../../CHANGELOG.md:962
  1413. msgid "**Users that were explicitly sticking to Redis/KeyDB** need to update their `vars.yml` to use `valkey_*` variables instead"
  1414. msgstr ""
  1415. #: ../../../CHANGELOG.md:965
  1416. msgid "2025-01-19"
  1417. msgstr ""
  1418. #: ../../../CHANGELOG.md:967
  1419. msgid "conduwuit support"
  1420. msgstr ""
  1421. #: ../../../CHANGELOG.md:969
  1422. msgid "Thanks to [Virkkunen](https://github.com/Virkkunen), we now have optional experimental [conduwuit](https://conduwuit.puppyirl.gay/) homeserver support for new installations."
  1423. msgstr ""
  1424. #: ../../../CHANGELOG.md:971
  1425. msgid "conduwuit is a fork of [Conduit](./docs/configuring-playbook-conduit.md), which the playbook also supports. See [Differences from upstream Conduit](https://conduwuit.puppyirl.gay/differences.html)."
  1426. msgstr ""
  1427. #: ../../../CHANGELOG.md:975
  1428. msgid "To try out conduwuit, we recommend that you **use a new server**. Refer to our [Configuring conduwuit](./docs/configuring-playbook-conduwuit.md) guide for details."
  1429. msgstr ""
  1430. #: ../../../CHANGELOG.md:977
  1431. msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse/Conduit/Dendrite to conduwuit) without data loss."
  1432. msgstr ""
  1433. #: ../../../CHANGELOG.md:980
  1434. msgid "2025-01-14"
  1435. msgstr ""
  1436. #: ../../../CHANGELOG.md:982
  1437. msgid "(Backward Compatibility Break) Synapse v1.122.0 requires Postgres v13"
  1438. msgstr ""
  1439. #: ../../../CHANGELOG.md:984
  1440. msgid "The Synapse homeserver [requires Postgres v13 or newer](https://github.com/element-hq/synapse/issues/18034)."
  1441. msgstr ""
  1442. #: ../../../CHANGELOG.md:986
  1443. msgid "If you've been maintaining your setup for a while and you haven't been doing [Postgres upgrades](docs/maintenance-postgres.md#upgrading-postgresql), you may be on an old version of Postgres. The easiest way to check is to see the contents of the `/matrix/postgres/data/PG_VERSION` file."
  1444. msgstr ""
  1445. #: ../../../CHANGELOG.md:988
  1446. msgid "If you're on a Postgres version older than v13, you need to [upgrade your Postgres setup](docs/maintenance-postgres.md#upgrading-postgresql) or Synapse will produce an error on startup."
  1447. msgstr ""
  1448. #: ../../../CHANGELOG.md:990
  1449. msgid "If you're using an external Postgres server (not installed by this playbook), you'll need to figure out how to upgrade it yourself."
  1450. msgstr ""
  1451. #: ../../../CHANGELOG.md:992
  1452. msgid "If you're not ready to upgrade your Postgres setup yet, you can temporarily remain on an old Synapse version by adding the following configuration to your `vars.yml` file:"
  1453. msgstr ""
  1454. #: ../../../CHANGELOG.md:1000
  1455. msgid "2024-11-26"
  1456. msgstr ""
  1457. #: ../../../CHANGELOG.md:1002
  1458. msgid "(Backward Compatibility Break) Synapse now defaults to enabling authenticated media"
  1459. msgstr ""
  1460. #: ../../../CHANGELOG.md:1004
  1461. msgid "**TLDR**: with this update, your Synapse homeserver will start requiring authentication for newly-uploaded media files. While the majority of the ecosystem (clients, bots, etc.) should support this, certain software may lack support for it (and you may wish to turn it off, if it's causing issues)."
  1462. msgstr ""
  1463. #: ../../../CHANGELOG.md:1006
  1464. msgid "The default configuration for the Synapse homeserver now [enforces Authenticated media by default](https://element-hq.github.io/synapse/v1.120/upgrade.html#authenticated-media-is-now-enforced-by-default)."
  1465. msgstr ""
  1466. #: ../../../CHANGELOG.md:1008
  1467. msgid "Servers like `matrix.org` have already [sunset unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) months ago."
  1468. msgstr ""
  1469. #: ../../../CHANGELOG.md:1010
  1470. msgid "Now that **various clients, bots, bridges and extra services have caught up with authenticated media support**, Synapse developers seem confident that it's time to enable authenticated media by default."
  1471. msgstr ""
  1472. #: ../../../CHANGELOG.md:1012
  1473. msgid "We're changing the playbook configuration for authenticated media to keep up with upstream defaults changing."
  1474. msgstr ""
  1475. #: ../../../CHANGELOG.md:1014
  1476. msgid "Old and unmaintained bridges (like all mx-puppet bridges, etc.) do not support authenticated media. Other software may be similarly affected. If you experience issues with some Matrix-related software, you may wish to disable authenticated media and contact the software maintainers to let them know."
  1477. msgstr ""
  1478. #: ../../../CHANGELOG.md:1016
  1479. msgid "You can disable authenticated media at any time by setting `matrix_synapse_enable_authenticated_media: false` in your `vars.yml` configuration file and re-running the playbook."
  1480. msgstr ""
  1481. #: ../../../CHANGELOG.md:1019
  1482. msgid "2024-11-23"
  1483. msgstr ""
  1484. #: ../../../CHANGELOG.md:1021
  1485. msgid "(Backward Compatibility Break) The playbook now defaults to Valkey, instead of KeyDB"
  1486. msgstr ""
  1487. #: ../../../CHANGELOG.md:1023
  1488. msgid "**TLDR**: if the playbook installed KeyDB (or Redis) as a dependency for you before, it will now replace it with [Valkey](https://valkey.io/) (a drop-in alternative). We [previously switched from Redis to KeyDB](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis), but Valkey is a better alternative, so we're switching again."
  1489. msgstr ""
  1490. #: ../../../CHANGELOG.md:1025
  1491. msgid "The playbook used to install Redis or KeyDB if services have a need for a Redis-compatible implementation ([enabling worker support for Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-workers), [enabling Hookshot encryption](docs/configuring-playbook-bridge-hookshot.md#end-to-bridge-encryption), etc.)."
  1492. msgstr ""
  1493. #: ../../../CHANGELOG.md:1027
  1494. msgid "Earlier this year, we switched from Redis to KeyDB — see [(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis)."
  1495. msgstr ""
  1496. #: ../../../CHANGELOG.md:1029
  1497. msgid "Because Valkey seems to be a better successor to Redis (than KeyDB) and likely doesn't suffer from [issues like this one](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3544), we now replace KeyDB with Valkey."
  1498. msgstr ""
  1499. #: ../../../CHANGELOG.md:1031
  1500. msgid "Valkey (like KeyDB and Redis in the past) is an implicitly enabled dependency — you don't need custom configuration in `vars.yml` to enable it."
  1501. msgstr ""
  1502. #: ../../../CHANGELOG.md:1033
  1503. msgid "Next time your run the playbook (via the `setup-all` tag), **KeyDB will be automatically uninstalled and replaced with Valkey**. Some Synapse downtime may occur while the switch happens."
  1504. msgstr ""
  1505. #: ../../../CHANGELOG.md:1035
  1506. msgid "Users on `arm32` should be aware that there's **neither a prebuilt `arm32` container image for Valkey**, nor the Valkey role supports self-building yet. Users on this architecture likely don't run Synapse with workers, etc., so they're likely in no need of Valkey (or Redis/KeyDB). If Redis is necessary in an `arm32` deployment, disabling Valkey and making the playbook fall back to Redis is possible (see below)."
  1507. msgstr ""
  1508. #: ../../../CHANGELOG.md:1037
  1509. #: ../../../CHANGELOG.md:1377
  1510. msgid "**The playbook still supports Redis** and you can keep using Redis (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:"
  1511. msgstr ""
  1512. #: ../../../CHANGELOG.md:1048
  1513. msgid "**The playbook still supports KeyDB** and you can keep using KeyDB (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:"
  1514. msgstr ""
  1515. #: ../../../CHANGELOG.md:1058
  1516. msgid "At some point in time in the future, we'll remove both KeyDB and Redis from the playbook, so we recommend that you migrate to Valkey earlier anyway."
  1517. msgstr ""
  1518. #: ../../../CHANGELOG.md:1061
  1519. msgid "2024-11-14"
  1520. msgstr ""
  1521. #: ../../../CHANGELOG.md:1063
  1522. msgid "HTTP-compression support for Traefik-based setups"
  1523. msgstr ""
  1524. #: ../../../CHANGELOG.md:1065
  1525. msgid "The playbook now **automatically enables HTTP-compression support** for major services powered by the playbook, like [Cinny](./docs/configuring-playbook-client-cinny.md), [Element Web](./docs/configuring-playbook-client-element-web.md), [Hydrogen](./docs/configuring-playbook-client-hydrogen.md), as well as for Matrix Client-Server and Federation APIs (`matrix.example.com`)."
  1526. msgstr ""
  1527. #: ../../../CHANGELOG.md:1067
  1528. msgid "Other services installed by the playbook are currently not compression-enabled, but may become so over time. This change is rolled out on a per-service basis (as opposed to doing it globally, at the Traefik entrypoint level) to allow certain services or route endpoints which do not behave well when compressed (e.g. [issue 3749](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3749)) to be excluded from compression."
  1529. msgstr ""
  1530. #: ../../../CHANGELOG.md:1069
  1531. msgid "A long time ago, various services were operating with `gzip`-compression enabled at the nginx level. Since the switch to Traefik (see [Goodbye, `matrix-nginx-proxy` 🪦](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/57c5271d9d6265a34a9d9cceb93365f685074f96/CHANGELOG.md#goodbye-matrix-nginx-proxy-)), all services (with the exception of Matrix APIs for Synapse worker-enabled setups which are powered by `nginx` via `synapse-reverse-proxy-companion`) have been operating without HTTP-compression support."
  1532. msgstr ""
  1533. #: ../../../CHANGELOG.md:1071
  1534. msgid "HTTP-compression is now done via Traefik's [compress](https://doc.traefik.io/traefik/middlewares/http/compress/) middleware. We use the default configuration for this middleware, which enables `zstd`, `br` and `gzip` support (in this order). This middleware's configuration can be configured via variables in the Traefik role (see `traefik_config_http_middlewares_compression_middleware_options`)."
  1535. msgstr ""
  1536. #: ../../../CHANGELOG.md:1073
  1537. msgid "If you're using your own Traefik reverse-proxy server ([Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)) instead of the playbook's integrated Traefik service, you can benefit from the same by:"
  1538. msgstr ""
  1539. #: ../../../CHANGELOG.md:1075
  1540. msgid "defining a [compress](https://doc.traefik.io/traefik/middlewares/http/compress/) middleware (via the [file](https://doc.traefik.io/traefik/providers/file/) or [Docker](https://doc.traefik.io/traefik/providers/docker/) providers)"
  1541. msgstr ""
  1542. #: ../../../CHANGELOG.md:1076
  1543. msgid "setting `matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled` to `true`"
  1544. msgstr ""
  1545. #: ../../../CHANGELOG.md:1077
  1546. msgid "specifying the middleware's name in `matrix_playbook_reverse_proxy_traefik_middleware_compression_name` (e.g. `matrix_playbook_reverse_proxy_traefik_middleware_compression_name: my-compression-middleware@file`)"
  1547. msgstr ""
  1548. #: ../../../CHANGELOG.md:1079
  1549. msgid "Timeout adjustments for Traefik-based setups"
  1550. msgstr ""
  1551. #: ../../../CHANGELOG.md:1081
  1552. msgid "The playbook now supports configuring various [transport.respondingTimeouts](https://doc.traefik.io/traefik/routing/entrypoints/#respondingtimeouts) timeout values (`readTimeout`, `writeTimeout`, `idleTimeout`) for the `web`, `web-secure` and `matrix-federation` entrypoints."
  1553. msgstr ""
  1554. #: ../../../CHANGELOG.md:1083
  1555. msgid "If you're using your own Traefik reverse-proxy server ([Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)) instead of the playbook's integrated Traefik service, you may wish to do similar configuration changes to your setup manually."
  1556. msgstr ""
  1557. #: ../../../CHANGELOG.md:1085
  1558. msgid "The most interesting of these is the `readTimeout` configuration value (the maximum duration for reading the entire request, including the body), which used to default to `60s`. For large and slowly progressing file uploads, `60s` would often not be enough for the transfer to finish and uploads would end up being interrupted. The playbook now raises the `readTimeout` value to 5 minutes (`300s`) to improve this use-case."
  1559. msgstr ""
  1560. #: ../../../CHANGELOG.md:1087
  1561. msgid "The `traefik_config_entrypoint_web_transport_respondingTimeouts_*` variables (for the `web` entrypoint) cascade to affecting the timeout values for the `web-secure` and `matrix-federation` entrypoints, so you can easily adjust all timeout values using them."
  1562. msgstr ""
  1563. #: ../../../CHANGELOG.md:1089
  1564. msgid "Example of the default timeout values used by the playbook:"
  1565. msgstr ""
  1566. #: ../../../CHANGELOG.md:1100
  1567. msgid "Alternatively, you may adjust the timeout values for specific entrypoints (like `web-secure` and `matrix-federation`) using dedicated variables (like `traefik_config_entrypoint_web_secure_transport_respondingTimeouts_readTimeout` and `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_readTimeout`)."
  1568. msgstr ""
  1569. #: ../../../CHANGELOG.md:1103
  1570. msgid "2024-11-08"
  1571. msgstr ""
  1572. #: ../../../CHANGELOG.md:1105
  1573. msgid "Support for synapse-admin auto-configuration via /.well-known/matrix/client"
  1574. msgstr ""
  1575. #: ../../../CHANGELOG.md:1107
  1576. msgid "You can administrate your Synapse-powered homeserver using synapse-admin hosted externally (e.g. [admin.etke.cc](https://admin.etke.cc/)) and the synapse-admin instance would still auto-configure itself correctly for your server by [reading its `/.well-known/matrix/client` file](https://github.com/etkecc/synapse-admin/pull/126)."
  1577. msgstr ""
  1578. #: ../../../CHANGELOG.md:1109
  1579. msgid "The playbook now configures the `/.well-known/matrix/client` file for this by default, injecting into it a `cc.etke.synapse-admin` section that contains the full synapse-admin configuration. This is done even if you don't enable the synapse-admin service in your configuration. The reason for always doing it is to allow users to skip the (small) overhead of self-hosting the non-core synapse-admin service, yet still be able to use it from elsewhere when needed."
  1580. msgstr ""
  1581. #: ../../../CHANGELOG.md:1111
  1582. msgid "If you don't ever plan on using synapse-admin from other servers (besides your own due to [self-hosting synapse-admin](./docs/configuring-playbook-synapse-admin.md)), you **can disable this** `/.well-known/matrix/client` configuration via `matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_enabled: false`"
  1583. msgstr ""
  1584. #: ../../../CHANGELOG.md:1114
  1585. msgid "2024-10-28"
  1586. msgstr ""
  1587. #: ../../../CHANGELOG.md:1116
  1588. msgid "(BC Break) Postmoogle's variable names need adjustments"
  1589. msgstr ""
  1590. #: ../../../CHANGELOG.md:1118
  1591. msgid "Due to the recategorization of [Postmoogle](./docs/configuring-playbook-bridge-postmoogle.md) from the bot to the bridge, its variables were renamed (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`). You need to adjust your `vars.yml` configuration accordingly."
  1592. msgstr ""
  1593. #: ../../../CHANGELOG.md:1120
  1594. msgid "2024-10-19"
  1595. msgstr ""
  1596. #: ../../../CHANGELOG.md:1122
  1597. msgid "Support for Matrix Authentication Service"
  1598. msgstr ""
  1599. #: ../../../CHANGELOG.md:1124
  1600. msgid "The playbook now supports installing and configuring [Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) (MAS)."
  1601. msgstr ""
  1602. #: ../../../CHANGELOG.md:1126
  1603. msgid "Huge thanks to [Quentin Gliech](https://github.com/sandhose) from the [Element](https://element.io/) / [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service) team for answering our numerous questions about MAS."
  1604. msgstr ""
  1605. #: ../../../CHANGELOG.md:1128
  1606. msgid "This is an **experimental service** and there are **still certain issues with it** (see [Expectations](./docs/configuring-playbook-matrix-authentication-service.md#expectations)). Matrix server administrators should only consider switching if they identify with one or more [reasons to use Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md#reasons-to-use-matrix-authentication-service). As MAS adoption improves and more services are adjusted to support it, we expect that using MAS will become the norm."
  1607. msgstr ""
  1608. #: ../../../CHANGELOG.md:1130
  1609. msgid "Our [Setting up Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) documentation page has more details about this new service, what you might expect from the switch and how you can migrate your existing (Synapse) homeserver setup to MAS."
  1610. msgstr ""
  1611. #: ../../../CHANGELOG.md:1133
  1612. msgid "2024-09-27"
  1613. msgstr ""
  1614. #: ../../../CHANGELOG.md:1135
  1615. msgid "(BC Break) Postgres & Traefik roles have been relocated and variable names need adjustments"
  1616. msgstr ""
  1617. #: ../../../CHANGELOG.md:1137
  1618. msgid "Various roles have been relocated from the [devture](https://github.com/devture) organization to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization."
  1619. msgstr ""
  1620. #: ../../../CHANGELOG.md:1139
  1621. msgid "Along with the relocation, the `devture_` prefix was dropped from their variable names, so you need to adjust your `vars.yml` configuration."
  1622. msgstr ""
  1623. #: ../../../CHANGELOG.md:1141
  1624. msgid "You need to do the following replacements:"
  1625. msgstr ""
  1626. #: ../../../CHANGELOG.md:1143
  1627. msgid "`devture_postgres_` -> `postgres_`"
  1628. msgstr ""
  1629. #: ../../../CHANGELOG.md:1144
  1630. msgid "`devture_traefik_` -> `traefik_`"
  1631. msgstr ""
  1632. #: ../../../CHANGELOG.md:1149
  1633. msgid "2024-09-12"
  1634. msgstr ""
  1635. #: ../../../CHANGELOG.md:1151
  1636. msgid "Support for baibot"
  1637. msgstr ""
  1638. #: ../../../CHANGELOG.md:1153
  1639. msgid "The playbook now supports installing [baibot](./docs/configuring-playbook-bot-baibot.md) (pronounced bye-bot) — a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖"
  1640. msgstr ""
  1641. #: ../../../CHANGELOG.md:1155
  1642. msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as well as many other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
  1643. msgstr ""
  1644. #: ../../../CHANGELOG.md:1157
  1645. msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to the now-unmaintained [matrix-chatgpt-bot](./docs/configuring-playbook-bot-chatgpt.md)."
  1646. msgstr ""
  1647. #: ../../../CHANGELOG.md:1159
  1648. msgid "To get started, see the [Setting up baibot](./docs/configuring-playbook-bot-baibot.md) documentation page."
  1649. msgstr ""
  1650. #: ../../../CHANGELOG.md:1161
  1651. msgid "Switching synapse-admin to etke.cc's fork"
  1652. msgstr ""
  1653. #: ../../../CHANGELOG.md:1163
  1654. msgid "The playbook now installs [etke.cc](https://etke.cc/)'s [fork](https://github.com/etkecc/synapse-admin) of [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin) (originally developed by [Awesome-Technologies](https://github.com/Awesome-Technologies)). This fork is a drop-in replacement for the original software."
  1655. msgstr ""
  1656. #: ../../../CHANGELOG.md:1165
  1657. msgid "The creation of the fork has been provoked by users frequently encountering issues with the original synapse-admin software, such as unintentionally deleting their one-and-only admin user account (fixed [here](https://github.com/etkecc/synapse-admin/pull/1) and also contributed upstream [here](https://github.com/Awesome-Technologies/synapse-admin/pull/608) — to no avail for now). Since its inception, [a bunch of other quality-of-life improvements](https://github.com/etkecc/synapse-admin?tab=readme-ov-file#changes) have been made to the fork."
  1658. msgstr ""
  1659. #: ../../../CHANGELOG.md:1167
  1660. msgid "If upstream synapse-admin picks up the pace and improves, the etke.cc fork may disappear and the playbook may switch to the original software again. Until that time comes, we believe that etke.cc's fork is the better software to use right now."
  1661. msgstr ""
  1662. #: ../../../CHANGELOG.md:1169
  1663. msgid "If you'd like to switch back to the original synapse-admin software, you can do so by adding the following configuration to your `vars.yml` file:"
  1664. msgstr ""
  1665. #: ../../../CHANGELOG.md:1182
  1666. msgid "2024-08-17"
  1667. msgstr ""
  1668. #: ../../../CHANGELOG.md:1184
  1669. msgid "New appservice-double-puppet service for better double-puppeting"
  1670. msgstr ""
  1671. #: ../../../CHANGELOG.md:1186
  1672. msgid "Mautrix bridges are undergoing large changes as announced in the [August 2024 releases & progress](https://mau.fi/blog/2024-08-mautrix-release/) blog post."
  1673. msgstr ""
  1674. #: ../../../CHANGELOG.md:1188
  1675. msgid "The playbook has already upgraded to the rewritten mautrix-slack ([v0.1.0](https://github.com/mautrix/slack/releases/tag/v0.1.0)) and mautrix-signal ([v0.7.0](https://github.com/mautrix/signal/releases/tag/v0.7.0)) bridges."
  1676. msgstr ""
  1677. #: ../../../CHANGELOG.md:1190
  1678. msgid "The newly rewritten bridges do not support double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) anymore, which has prompted us to switch to the new & better [appservice method](https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new) for double-puppeting. The playbook automates this double-puppeting setup for you if you enable the new [Appservice Double Puppet](./docs/configuring-playbook-appservice-double-puppet.md) service."
  1679. msgstr ""
  1680. #: ../../../CHANGELOG.md:1192
  1681. msgid "All non-deprecated mautrix bridges in the playbook have been reworked to support double-puppeting via an Appservice. Most bridges still support double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md), so the playbook supports it too. If only Shared Secret Auth is enabled, double-puppeting will be configured using that method (for the bridges that support it). That said, **Shared Secret Auth double-puppeting is being phased out and we recommend replacing it with the new Appservice method**."
  1682. msgstr ""
  1683. #: ../../../CHANGELOG.md:1194
  1684. msgid "We recommend **enabling double-puppeting via the new Appservice method** by adding the following configuration to your `vars.yml` file:"
  1685. msgstr ""
  1686. #: ../../../CHANGELOG.md:1200
  1687. msgid "You can still **keep** [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) enabled. Non-mautrix bridges and other services (e.g. [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) may still require it."
  1688. msgstr ""
  1689. #: ../../../CHANGELOG.md:1202
  1690. msgid "When both double-puppeting methods are enabled, the playbook will automatically choose the new and better Appservice method for bridges that support it."
  1691. msgstr ""
  1692. #: ../../../CHANGELOG.md:1205
  1693. msgid "2024-08-15"
  1694. msgstr ""
  1695. #: ../../../CHANGELOG.md:1207
  1696. msgid "matrix-media-repo now configured for Authenticated Media"
  1697. msgstr ""
  1698. #: ../../../CHANGELOG.md:1209
  1699. msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), our matrix-media-repo implementation now automatically [sets up signing keys](https://docs.t2bot.io/matrix-media-repo/v1.3.5/installation/signing-key/) for Authenticated Media (as per [MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916))."
  1700. msgstr ""
  1701. #: ../../../CHANGELOG.md:1211
  1702. msgid "If you had never heard of Authenticated Media before, the [Sunsetting unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) article on [matrix.org](https://matrix.org/) is a good introduction."
  1703. msgstr ""
  1704. #: ../../../CHANGELOG.md:1213
  1705. msgid "This feature is enabled for matrix-media-repo installations by default and will append an additional (matrix-media-repo-generated signing key) to your homeserver's (Synapse or Dendrite) signing key. See the [Signing keys](./docs/configuring-playbook-matrix-media-repo.md#signing-keys) and [Key backup and revoking](./docs/configuring-playbook-matrix-media-repo.md#key-backup-and-revoking) sections of the matrix-media-repo documentation for more details."
  1706. msgstr ""
  1707. #: ../../../CHANGELOG.md:1215
  1708. msgid "If you'd like to avoid this new feature, you can disable it by setting `matrix_media_repo_generate_signing_key: false` in your `vars.yml` configuration file."
  1709. msgstr ""
  1710. #: ../../../CHANGELOG.md:1218
  1711. msgid "2024-08-08"
  1712. msgstr ""
  1713. #: ../../../CHANGELOG.md:1220
  1714. msgid "(Backward Compatibility Break) matrix-corporal has been upgraded to v3"
  1715. msgstr ""
  1716. #: ../../../CHANGELOG.md:1222
  1717. msgid "The playbook now installs [matrix-corporal](https://github.com/devture/matrix-corporal) v3.0.0, which brings support for **power-level management** (thanks to [this PR](https://github.com/devture/matrix-corporal/pull/32))."
  1718. msgstr ""
  1719. #: ../../../CHANGELOG.md:1224
  1720. msgid "This upgrade necessitates configuration policy changes as described in [matrix-corporal's changelog entry](https://github.com/devture/matrix-corporal/blob/5287cb81c82cd3b951c2a099b4697c3e0b384559/CHANGELOG.md#version-300-2024-08-08)."
  1721. msgstr ""
  1722. #: ../../../CHANGELOG.md:1226
  1723. msgid "If you'd like to remain on the old (v2) version of matrix-corporal, you can do so by adding the following configuration to your `vars.yml` file:"
  1724. msgstr ""
  1725. #: ../../../CHANGELOG.md:1232
  1726. msgid "2024-07-25"
  1727. msgstr ""
  1728. #: ../../../CHANGELOG.md:1234
  1729. msgid "synapse-usage-exporter support"
  1730. msgstr ""
  1731. #: ../../../CHANGELOG.md:1236
  1732. msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) — a small [Flask](https://flask.palletsprojects.com)-based webservice which can capture usage statistics from Synapse (via HTTP `PUT`) and then make them available for Prometheus to scrape."
  1733. msgstr ""
  1734. #: ../../../CHANGELOG.md:1238
  1735. msgid "To learn more see our [Enabling synapse-usage-exporter for Synapse usage statistics](docs/configuring-playbook-synapse-usage-exporter.md) documentation page."
  1736. msgstr ""
  1737. #: ../../../CHANGELOG.md:1241
  1738. msgid "2024-07-06"
  1739. msgstr ""
  1740. #: ../../../CHANGELOG.md:1243
  1741. msgid "matrix-alertmanager-receiver support"
  1742. msgstr ""
  1743. #: ../../../CHANGELOG.md:1245
  1744. msgid "For those wishing to more easily integrate [Prometheus](https://prometheus.io/)' alerting service ([Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/)) with Matrix, the playbook can now set up [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver)."
  1745. msgstr ""
  1746. #: ../../../CHANGELOG.md:1247
  1747. msgid "See [Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](./docs/configuring-playbook-alertmanager-receiver.md) for more details."
  1748. msgstr ""
  1749. #: ../../../CHANGELOG.md:1249
  1750. msgid "Traefik v3 and HTTP/3 are here now"
  1751. msgstr ""
  1752. #: ../../../CHANGELOG.md:1251
  1753. msgid "**TLDR**: Traefik was migrated from v2 to v3. Minor changes were done to the playbook. Mostly everything else worked out of the box. Most people will not have to do any tweaks to their configuration. In addition, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is now auto-enabled for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints. If you have a firewall in front of your server and you wish to benefit from `HTTP3`, you will need to open the `443` and `8448` UDP ports in it."
  1754. msgstr ""
  1755. #: ../../../CHANGELOG.md:1253
  1756. msgid "Traefik v3"
  1757. msgstr ""
  1758. #: ../../../CHANGELOG.md:1255
  1759. msgid "The reverse-proxy that the playbook uses by default (Traefik) has recently been upgraded to v3 (see [this blog post](https://traefik.io/blog/announcing-traefik-proxy-v3-rc/) to learn about its new features). Version 3 includes some small breaking configuration changes requiring a [migration](https://doc.traefik.io/traefik/migration/v2-to-v3/)."
  1760. msgstr ""
  1761. #: ../../../CHANGELOG.md:1257
  1762. msgid "We have **updated the playbook to Traefik v3** (make sure to run `just roles` / `make roles` to get it)."
  1763. msgstr ""
  1764. #: ../../../CHANGELOG.md:1259
  1765. msgid "There were **only minor playbook changes required** to adapt to Traefik v3, and only to the Ansible role for [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) where we changed a few [`PathPrefix` instances to `PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-pathprefix-and-pathregexp), because these instances were using a regular expression instead of a fixed path. For fixed-path values, `PathPrefix` is still the preferred matcher function to use."
  1766. msgstr ""
  1767. #: ../../../CHANGELOG.md:1261
  1768. msgid "**Most people using the playbook should not have to do any changes**."
  1769. msgstr ""
  1770. #: ../../../CHANGELOG.md:1263
  1771. msgid "If you're using the playbook's Traefik instance to reverse-proxy to some other services of your own (not managed by the playbook), you may wish to review their Traefik labels and make sure they're in line with the [Traefik v2 to v3 migration guide](https://doc.traefik.io/traefik/migration/v2-to-v3/)."
  1772. msgstr ""
  1773. #: ../../../CHANGELOG.md:1265
  1774. msgid "If you've tweaked any of this playbook's `_path_prefix` variables and made them use a regular expression, you will now need to make additional adjustments. The playbook makes extensive use of `PathPrefix()` matchers in Traefik rules and `PathPrefix` does not support regular expressions anymore. To work around it, you may now need to override a whole `_traefik_rule` variable and switch it from [`PathPrefix` to `PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-pathprefix-and-pathregexp)."
  1775. msgstr ""
  1776. #: ../../../CHANGELOG.md:1267
  1777. msgid "If you're not using [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) (the only role we had to tweak to adapt it to Traefik v3), you **may potentially downgrade to Traefik v2** (if necessary) by adding `traefik_verison: v2.11.4` to your configuration. People using `matrix-media-repo` cannot downgrade this way, because `matrix-media-repo` has been adjusted to use `PathRegexp` — a [routing matcher](https://doc.traefik.io/traefik/v2.11/routing/routers/#rule) that Traefik v2 does not understand."
  1778. msgstr ""
  1779. #: ../../../CHANGELOG.md:1269
  1780. msgid "HTTP/3 is enabled by default"
  1781. msgstr ""
  1782. #: ../../../CHANGELOG.md:1271
  1783. msgid "In Traefik v3, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is no longer considered experimental now. Due to this, **the playbook auto-enables HTTP3** for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints."
  1784. msgstr ""
  1785. #: ../../../CHANGELOG.md:1273
  1786. msgid "HTTP3 uses the UDP protocol and **the playbook (together with Docker) will make sure that the appropriate ports** (`443` over UDP & `8448` over UDP) **are exposed and whitelisted in your server's firewall**. However, **if you have another firewall in front of your server** (as is the case for many cloud providers), **you will need to manually open these UDP ports**."
  1787. msgstr ""
  1788. #: ../../../CHANGELOG.md:1275
  1789. msgid "If you do not open the UDP ports correctly or there is some other issue, clients (browsers, mostly) will fall-back to [HTTP/2](https://en.wikipedia.org/wiki/HTTP/2) or even [HTTP/1.1](https://en.wikipedia.org/wiki/HTTP)."
  1790. msgstr ""
  1791. #: ../../../CHANGELOG.md:1277
  1792. msgid "Still, if HTTP/3 cannot function correctly in your setup, it's best to disable advertising support for it (and misleading clients into trying to use HTTP/3)."
  1793. msgstr ""
  1794. #: ../../../CHANGELOG.md:1279
  1795. msgid "To **disable HTTP/3**, you can use the following configuration:"
  1796. msgstr ""
  1797. #: ../../../CHANGELOG.md:1293
  1798. msgid "If you are using [your own webserver](./docs/configuring-playbook-own-webserver.md) (in front of Traefik), port binding on UDP port `8448` by default due to HTTP/3 is either unnecessary or [may get in the way](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3402). If it does, you can disable it:"
  1799. msgstr ""
  1800. #: ../../../CHANGELOG.md:1306
  1801. msgid "2024-07-01"
  1802. msgstr ""
  1803. #: ../../../CHANGELOG.md:1308
  1804. msgid "synapse-admin is now restricted to your homeserver's URL by default"
  1805. msgstr ""
  1806. #: ../../../CHANGELOG.md:1310
  1807. msgid "A new feature introduced in synapse-admin [v0.10.0](https://github.com/Awesome-Technologies/synapse-admin/releases/tag/0.10.0) (released and supported by the playbook since a a few months ago) provides the ability to [restrict its usage to a specific homeserver](https://github.com/Awesome-Technologies/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) (or multiple homeservers)."
  1808. msgstr ""
  1809. #: ../../../CHANGELOG.md:1312
  1810. msgid "The playbook has just started making use of this feature. **From now on, your synapse-admin instance will be restricted to the homeserver you're managing via the playbook**. When configured like this, the *Homeserver URL* field in synapse-admin's web UI changes from a text field to a dropdown having a single value (the URL of your homeserver). This makes usage simpler for most people, as they won't need to manually enter a *Homeserver URL* anymore."
  1811. msgstr ""
  1812. #: ../../../CHANGELOG.md:1314
  1813. msgid "If you'd like **to go back to the old unrestricted behavior**, use the following configuration:"
  1814. msgstr ""
  1815. #: ../../../CHANGELOG.md:1322
  1816. msgid "2024-06-25"
  1817. msgstr ""
  1818. #: ../../../CHANGELOG.md:1324
  1819. msgid "The URL-prefix for Hookshot generic webhooks has changed"
  1820. msgstr ""
  1821. #: ../../../CHANGELOG.md:1326
  1822. msgid "Until now, generic Hookshot webhook URLs looked like this: `https://matrix.example.com/hookshot/webhooks/:hookId`."
  1823. msgstr ""
  1824. #: ../../../CHANGELOG.md:1328
  1825. msgid "The `/hookshot/webhooks` common prefix gets stripped by Traefik automatically, so Hookshot only sees the part that comes after (`/:hookId`)."
  1826. msgstr ""
  1827. #: ../../../CHANGELOG.md:1330
  1828. msgid "[A few years ago](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1681), Hookshot started to prefer to handle webhooks at a `/webhook/:hookId` path (instead of directly at `/:hookId`)."
  1829. msgstr ""
  1830. #: ../../../CHANGELOG.md:1332
  1831. msgid "To avoid future problems, we've [reconfigured](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/4704a60718946fd469aeee7fc3ae8127c633bb6b) our Hookshot configuration to use webhook URLs that include `/webhook` in the URL suffix (e.g. `/hookshot/webhooks/webhook/:hookId`, instead of `/hookshot/webhooks/:hookId`). This means that when we strip the common prefi (`/hookshot/webhooks`), we'll end up sending `/webhook/:hookId` to Hookshot, just like recommended."
  1832. msgstr ""
  1833. #: ../../../CHANGELOG.md:1334
  1834. msgid "When generating new webhooks, you should start seeing the new URLs being used."
  1835. msgstr ""
  1836. #: ../../../CHANGELOG.md:1336
  1837. msgid "**For now**, **both** old URLs (`/hookshot/webhooks/:hookId`) and new URLs (`/hookshot/webhooks/webhook/:hookId`) **continue to work**, so your webhooks will not break just yet."
  1838. msgstr ""
  1839. #: ../../../CHANGELOG.md:1338
  1840. msgid "However, **we recommend that you update all your old webhook URLs** (configured in other systems) to include the new `/webhook` path component, so that future Hookshot changes (whenever they come) will not break your webhooks. You don't need to do anything on the Hookshot side — you merely need to reconfigure the remote systems that use your webhook URLs."
  1841. msgstr ""
  1842. #: ../../../CHANGELOG.md:1341
  1843. msgid "2024-06-22"
  1844. msgstr ""
  1845. #: ../../../CHANGELOG.md:1343
  1846. msgid "The maubot user is now managed by the playbook"
  1847. msgstr ""
  1848. #: ../../../CHANGELOG.md:1345
  1849. msgid "To make things easier and to be consistent with other roles, the [maubot](./docs/configuring-playbook-bot-maubot.md) user (`bot.maubot` by default) is [now](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3376) automatically created be the playbook."
  1850. msgstr ""
  1851. #: ../../../CHANGELOG.md:1347
  1852. msgid "If you have an existing maubot installation, you will need to specify `matrix_bot_maubot_initial_password` in your `vars.yml` file to make the playbook not complain about it being undefined. Since the bot is already registered in your installation, there's nothing for the playbook to do anyway. In case you don't remember the password you've registered your maubot user account with, you can specify any value for this variable."
  1853. msgstr ""
  1854. #: ../../../CHANGELOG.md:1349
  1855. msgid "If you've registered another username for the bot (other than the recommended default of `bot.maubot`), consider adjusting the `matrix_bot_maubot_login` variable (e.g. `matrix_bot_maubot_login: my.maubot.username`)."
  1856. msgstr ""
  1857. #: ../../../CHANGELOG.md:1352
  1858. msgid "2024-06-03"
  1859. msgstr ""
  1860. #: ../../../CHANGELOG.md:1354
  1861. msgid "WeChat bridging support"
  1862. msgstr ""
  1863. #: ../../../CHANGELOG.md:1356
  1864. msgid "Thanks to [Tobias Diez](https://github.com/tobiasdiez)'s [efforts](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3241), the playbook now supports bridging to [WeChat](https://www.wechat.com/) via the [matrix-wechat](https://github.com/duo/matrix-wechat) bridge."
  1865. msgstr ""
  1866. #: ../../../CHANGELOG.md:1358
  1867. msgid "See our [Setting up WeChat bridging](docs/configuring-playbook-bridge-wechat.md) documentation page for getting started."
  1868. msgstr ""
  1869. #: ../../../CHANGELOG.md:1361
  1870. msgid "2024-03-26"
  1871. msgstr ""
  1872. #: ../../../CHANGELOG.md:1363
  1873. msgid "(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis"
  1874. msgstr ""
  1875. #: ../../../CHANGELOG.md:1365
  1876. msgid "**TLDR**: if the playbook used installed Redis as a dependency for you before, it will now replace it with [KeyDB](https://docs.keydb.dev/) (a drop-in alternative) due to [Redis having changed its license](https://redis.com/blog/redis-adopts-dual-source-available-licensing/)."
  1877. msgstr ""
  1878. #: ../../../CHANGELOG.md:1367
  1879. msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now uses [KeyDB](https://docs.keydb.dev/) (a drop-in alternative for Redis), instead of [Redis](https://redis.io/)."
  1880. msgstr ""
  1881. #: ../../../CHANGELOG.md:1369
  1882. msgid "The playbook used to install Redis (and now installs KeyDB in its place) if services have a need for it ([enabling worker support for Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-workers), [enabling Hookshot encryption](docs/configuring-playbook-bridge-hookshot.md#end-to-bridge-encryption), etc.) or if you explicitly enabled the service (`redis_enabled: true` or `keydb_enabled: true`)."
  1883. msgstr ""
  1884. #: ../../../CHANGELOG.md:1371
  1885. msgid "This change is provoked by the fact that [Redis is now \"source available\"](https://redis.com/blog/redis-adopts-dual-source-available-licensing/). According to the Limitations of [the new license](https://redis.com/legal/rsalv2-agreement/) (as best as we understand them, given that we're not lawyers), using Redis in the playbook (even in a commercial FOSS service like [etke.cc](https://etke.cc/)) does not violate the new Redis license. That said, we'd rather neither risk it, nor endorse shady licenses and products that pretend to be free-software. Another high-quality alternative to Redis seems to be [Dragonfly](https://www.dragonflydb.io/), but the [Dragonfly license](https://github.com/dragonflydb/dragonfly?tab=License-1-ov-file#readme) is no better than Redis's."
  1886. msgstr ""
  1887. #: ../../../CHANGELOG.md:1373
  1888. msgid "Next time your run the playbook (via the `setup-all` tag), **Redis will be automatically uninstalled and replaced with KeyDB**. Some Synapse downtime may occur while the switch happens."
  1889. msgstr ""
  1890. #: ../../../CHANGELOG.md:1375
  1891. msgid "Users on `arm32` should be aware that there's **neither a prebuilt `arm32` container image for KeyDB**, nor the KeyDB role supports self-building yet. Users on this architecture likely don't run Synapse with workers, etc., so they're likely in no need of KeyDB (or Redis). If Redis is necessary in an `arm32` deployment, disabling KeyDB and making the playbook fall back to Redis is possible (see below)."
  1892. msgstr ""
  1893. #: ../../../CHANGELOG.md:1386
  1894. msgid "2024-03-24"
  1895. msgstr ""
  1896. #: ../../../CHANGELOG.md:1388
  1897. msgid "Initial work on IPv6 support"
  1898. msgstr ""
  1899. #: ../../../CHANGELOG.md:1390
  1900. msgid "Thanks to [Tilo Spannagel](https://github.com/tilosp), the playbook can now enable IPv6 for container networks for various components (roles) via [the `devture_systemd_docker_base_ipv6_enabled` variable](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L14-L31)."
  1901. msgstr ""
  1902. #: ../../../CHANGELOG.md:1392
  1903. msgid "It should be noted that:"
  1904. msgstr ""
  1905. #: ../../../CHANGELOG.md:1394
  1906. msgid "Matrix roles (`roles/custom/matrix-*`) respect this variable, but external roles (those defined in `requirements.yml` and installed via `just roles`) do not respect it yet. Additional work is necessary"
  1907. msgstr ""
  1908. #: ../../../CHANGELOG.md:1395
  1909. msgid "changing the variable subsequently may not change existing container networks. Refer to [these instructions](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L26-L30)"
  1910. msgstr ""
  1911. #: ../../../CHANGELOG.md:1396
  1912. msgid "this is all very new and untested"
  1913. msgstr ""
  1914. #: ../../../CHANGELOG.md:1398
  1915. msgid "Pantalaimon support"
  1916. msgstr ""
  1917. #: ../../../CHANGELOG.md:1400
  1918. msgid "Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the playbook can now install the [Pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you. It's already possible to integrate it with [Draupnir](docs/configuring-playbook-bot-draupnir.md) to allow it to work in E2EE rooms — see our Draupnir docs for details."
  1919. msgstr ""
  1920. #: ../../../CHANGELOG.md:1402
  1921. msgid "See our [Setting up Pantalaimon](docs/configuring-playbook-pantalaimon.md) documentation to get started."
  1922. msgstr ""
  1923. #: ../../../CHANGELOG.md:1405
  1924. msgid "2024-03-05"
  1925. msgstr ""
  1926. #: ../../../CHANGELOG.md:1407
  1927. msgid "Support for Draupnir-for-all"
  1928. msgstr ""
  1929. #: ../../../CHANGELOG.md:1409
  1930. msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now install [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) (aka multi-instance Draupnir running in appservice mode)."
  1931. msgstr ""
  1932. #: ../../../CHANGELOG.md:1411
  1933. msgid "This is an alternative to [running Draupnir in bot mode](./docs/configuring-playbook-bot-draupnir.md), which is still supported by the playbook."
  1934. msgstr ""
  1935. #: ../../../CHANGELOG.md:1413
  1936. msgid "The documentation page for [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) contains more information on how to install it."
  1937. msgstr ""
  1938. #: ../../../CHANGELOG.md:1416
  1939. msgid "2024-02-19"
  1940. msgstr ""
  1941. #: ../../../CHANGELOG.md:1418
  1942. msgid "Support for bridging to Facebook/Messenger via the new mautrix-meta bridge"
  1943. msgstr ""
  1944. #: ../../../CHANGELOG.md:1420
  1945. msgid "The [mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-facebook.md) and [mautrix-instagram](./docs/configuring-playbook-bridge-mautrix-instagram.md) bridges are being [superseded by a new bridge](https://github.com/mautrix/facebook/issues/332) — the [mautrix-meta](https://github.com/mautrix/meta) bridge."
  1946. msgstr ""
  1947. #: ../../../CHANGELOG.md:1422
  1948. msgid "The playbook now supports the new mautrix-meta bridge — a single bridge, which can run in different modes and bridge to Messenger (via [Facebook](https://facebook.com/), Facebook over [Tor](https://www.torproject.org/) or via [Messenger](https://messenger.com/)) and [Instagram](https://instagram.com/). The playbook makes this bridge available via 2 separate Ansible roles, allowing you to easily run 2 instances of mautrix-meta, for bridging to both services at the same time."
  1949. msgstr ""
  1950. #: ../../../CHANGELOG.md:1424
  1951. msgid "If you're using mautrix-facebook or mautrix-instagram right now, **you can still continue using the old bridges, but may wish to change to the new bridge implementations**. See:"
  1952. msgstr ""
  1953. #: ../../../CHANGELOG.md:1426
  1954. msgid "[Setting up Instagram bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)"
  1955. msgstr ""
  1956. #: ../../../CHANGELOG.md:1428
  1957. msgid "[Setting up Messenger bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-messenger.md)"
  1958. msgstr ""
  1959. #: ../../../CHANGELOG.md:1430
  1960. msgid "The documentation pages contain more information on how to migrate."
  1961. msgstr ""
  1962. #: ../../../CHANGELOG.md:1433
  1963. msgid "2024-02-14"
  1964. msgstr ""
  1965. #: ../../../CHANGELOG.md:1435
  1966. msgid "Much larger Synapse caches and cache auto-tuning enabled by default"
  1967. msgstr ""
  1968. #: ../../../CHANGELOG.md:1437
  1969. msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook now uses much larger caches and enables Synapse's [cache auto-tuning functionality](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values). This work and the default values used by the playbook are inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/deployment/synapse.html)."
  1970. msgstr ""
  1971. #: ../../../CHANGELOG.md:1439
  1972. msgid "The playbook has always used a very conservative cache factor (`matrix_synapse_caches_global_factor`) value of `0.5`, which may be OK for small and underactive deployments, but is not ideal for larger servers. Paradoxically, a small global cache factor value [does not necessarily decrease RAM usage as a whole](https://github.com/matrix-org/synapse/issues/3939)."
  1973. msgstr ""
  1974. #: ../../../CHANGELOG.md:1441
  1975. msgid "The playbook now uses **a 20x larger cache factor** (currently `10`), adjusts a few other cache-related variables, and **enables cache auto-tuning** via the following variables:"
  1976. msgstr ""
  1977. #: ../../../CHANGELOG.md:1443
  1978. msgid "`matrix_synapse_cache_autotuning_max_cache_memory_usage` — defaults to 1/8 of total RAM with a cap of 2GB; values are specified in bytes"
  1979. msgstr ""
  1980. #: ../../../CHANGELOG.md:1444
  1981. msgid "`matrix_synapse_cache_autotuning_target_cache_memory_usage` — defaults to 1/16 of total RAM with a cap of 1GB; values are specified in bytes"
  1982. msgstr ""
  1983. #: ../../../CHANGELOG.md:1445
  1984. msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` — defaults to `30s`"
  1985. msgstr ""
  1986. #: ../../../CHANGELOG.md:1447
  1987. msgid "These values should be good defaults for most servers, but may change over time as we experiment further."
  1988. msgstr ""
  1989. #: ../../../CHANGELOG.md:1449
  1990. msgid "Refer to our new [Tuning caches and cache autotuning](docs/maintenance-synapse.md#tuning-caches-and-cache-autotuning) documentation section for more details."
  1991. msgstr ""
  1992. #: ../../../CHANGELOG.md:1452
  1993. msgid "2024-01-31"
  1994. msgstr ""
  1995. #: ../../../CHANGELOG.md:1454
  1996. msgid "(Backward-compatibility break) Minor changes necessary for some people serving a static website at the base domain"
  1997. msgstr ""
  1998. #: ../../../CHANGELOG.md:1456
  1999. msgid "This only affects people who are [Serving a static website at the base domain](./docs/configuring-playbook-base-domain-serving.md#serving-a-static-website-at-the-base-domain), but not managing its `index.html` through the playbook."
  2000. msgstr ""
  2001. #: ../../../CHANGELOG.md:1458
  2002. msgid "That is, for people who have `matrix_static_files_file_index_html_enabled: false` in their `vars.yml` configuration, the playbook has a new default behavior. Since the playbook is not managing the `index.html` file, it will default to a more sensible way of handling the base domain — redirecting `https://example.com/` to `https://matrix.example.com/`, instead of serving a 404 page."
  2003. msgstr ""
  2004. #: ../../../CHANGELOG.md:1460
  2005. msgid "If you are managing your static website by yourself (by dropping files into `/matrix/static-files/public` somehow), then you probably don't wish for such redirection to happen. You can disable it by adding `matrix_static_files_container_labels_base_domain_root_path_redirection_enabled: false` to your `vars.yml` configuration file."
  2006. msgstr ""
  2007. #: ../../../CHANGELOG.md:1463
  2008. msgid "2024-01-20"
  2009. msgstr ""
  2010. #: ../../../CHANGELOG.md:1465
  2011. msgid "Support for more efficient (specialized) Synapse workers"
  2012. msgstr ""
  2013. #: ../../../CHANGELOG.md:1467
  2014. msgid "Thanks to [Charles Wright](https://github.com/cvwright) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook has [received support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3100) for load-balancing the Synapse workload via [specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) which are supposed to work better than our old [generic workers](./docs/configuring-playbook-synapse.md#generic-workers) implementation."
  2015. msgstr ""
  2016. #: ../../../CHANGELOG.md:1469
  2017. msgid "For now, playbook defaults remain unchanged and the `one-of-each` [workers preset](./docs/configuring-playbook-synapse.md#worker-presets) continues being the default. However, the default may change in the future. If you'd like to remain on this preset even if/when the defaults change, consider explicitly adding `matrix_synapse_workers_preset: one-of-each` to your `vars.yml` configuration."
  2018. msgstr ""
  2019. #: ../../../CHANGELOG.md:1471
  2020. msgid "Our specialized workers setup is based on recommendations found in [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). What's special about our new setup is that we try to parse information out of the request (who the user is; which room is being operated on) and try to forward similar requests to the same worker. As an example, this means that once a worker caches some room information, subsequent requests for the same room will be routed to the same worker (which supposedly still has the room's state cached)."
  2021. msgstr ""
  2022. #: ../../../CHANGELOG.md:1473
  2023. msgid "To get started, refer to our [Specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) documentation section."
  2024. msgstr ""
  2025. #: ../../../CHANGELOG.md:1476
  2026. msgid "2024-01-17"
  2027. msgstr ""
  2028. #: ../../../CHANGELOG.md:1478
  2029. msgid "Switching to Element's AGPLv3-licensed Synapse release"
  2030. msgstr ""
  2031. #: ../../../CHANGELOG.md:1480
  2032. msgid "A few months ago, the [Element](https://element.io/) company has [announced](https://element.io/blog/element-to-adopt-agplv3/) that their work on the Synapse homeserver would no longer be available under the permissive [Apache-2.0 license](https://www.apache.org/licenses/LICENSE-2.0), but only under:"
  2033. msgstr ""
  2034. #: ../../../CHANGELOG.md:1482
  2035. msgid "the [AGPLv3](https://www.gnu.org/licenses/agpl-3.0.en.html) free-software license — the same license that this Ansible playbook has always used"
  2036. msgstr ""
  2037. #: ../../../CHANGELOG.md:1483
  2038. msgid "a proprietary license, for those wishing for Element to [sell them an exception](https://gnu.org/philosophy/selling-exceptions.html) to the AGPLv3 license"
  2039. msgstr ""
  2040. #: ../../../CHANGELOG.md:1485
  2041. msgid "You can also learn more in [this post](https://matrix.org/blog/2023/11/06/future-of-synapse-dendrite/) by the Matrix Foundation."
  2042. msgstr ""
  2043. #: ../../../CHANGELOG.md:1487
  2044. msgid "The change has [already happened](https://element.io/blog/synapse-now-lives-at-github-com-element-hq-synapse/) and the first Synapse release under the new license is here: [v1.99.0](https://github.com/element-hq/synapse/releases/tag/v1.99.0)."
  2045. msgstr ""
  2046. #: ../../../CHANGELOG.md:1489
  2047. msgid "There is no up-to-date alternative Synapse fork right now and this free-software (AGPLv3-licensed) playbook is definitely not against free-software licenses, so we are now switching to the Element-maintained Synapse release."
  2048. msgstr ""
  2049. #: ../../../CHANGELOG.md:1491
  2050. msgid "**What does this mean to you?**"
  2051. msgstr ""
  2052. #: ../../../CHANGELOG.md:1493
  2053. msgid "For most home users, it doesn't mean anything. Your installation will continue working as it should and you don't need to do anything."
  2054. msgstr ""
  2055. #: ../../../CHANGELOG.md:1495
  2056. msgid "For people building commercial products on top of Synapse, they may have to either buy a license exception from Element (from what we hear, the fee depends on the number of monthly-active users on your instance) or they may need to release all related code as free-software (which is what we've been doing at [etke.cc](https://etke.cc/) ([here](https://gitlab.com/etke.cc)) all along)."
  2057. msgstr ""
  2058. #: ../../../CHANGELOG.md:1497
  2059. msgid "We're no lawyers and this changelog entry does not aim to give you the best legal advice, so please research on your own!"
  2060. msgstr ""
  2061. #: ../../../CHANGELOG.md:1499
  2062. msgid "If you'd like to continue using the old Apache-2.0-licensed Synapse (for a while longer anyway), the playbook makes it possible by introducing a new Ansible variable. You can do it like this:"
  2063. msgstr ""
  2064. #: ../../../CHANGELOG.md:1511
  2065. msgid "Notes:"
  2066. msgstr ""
  2067. #: ../../../CHANGELOG.md:1513
  2068. msgid "if you had already upgraded Synapse to `v1.99.0` by running this playbook, you will still be able to downgrade to `v1.98.0`, because both releases use the same database schema version (`SCHEMA_COMPAT_VERSION = 83` — see [here for v1.98.0](https://github.com/element-hq/synapse/blob/v1.98.0/synapse/storage/schema/__init__.py#L131-L134) and [here for v1.99.0](https://github.com/element-hq/synapse/blob/v1.99.0/synapse/storage/schema/__init__.py#L137-L140)). More details on Synapse's database schema are available [here](https://element-hq.github.io/synapse/develop/development/database_schema.html). It appears that there are no new database migrations introduced in `v1.99.0`, so going back to the older release is possible. This is not guaranteed to hold true for future Synapse releases, so if you're seeing this early-enough, consider pinning the version and organization before re-running the playbook and getting upgraded to the latest version"
  2069. msgstr ""
  2070. #: ../../../CHANGELOG.md:1515
  2071. msgid "running an outdated homeserver exposes you to security issues and incompatibilities. Only consider doing this as a short-term solution."
  2072. msgstr ""
  2073. #: ../../../CHANGELOG.md:1517
  2074. msgid "2024-01-16"
  2075. msgstr ""
  2076. #: ../../../CHANGELOG.md:1519
  2077. msgid "`Draupnir` has been relicensed to AFL-3.0"
  2078. msgstr ""
  2079. #: ../../../CHANGELOG.md:1521
  2080. msgid "As of [#204](https://github.com/the-draupnir-project/Draupnir/pull/204) Draupnir changed its licence to AFL-3.0 from the CSL licence. This change affects playbook users who could not run Draupnir under the old license restrictions. The new license is considerably less restrictive and is OSI approved. Draupnir version v1.86.0 and later are covered by this license change."
  2081. msgstr ""
  2082. #: ../../../CHANGELOG.md:1523
  2083. msgid "2024-01-15"
  2084. msgstr ""
  2085. #: ../../../CHANGELOG.md:1525
  2086. msgid "Goodbye, `matrix-nginx-proxy` 🪦"
  2087. msgstr ""
  2088. #: ../../../CHANGELOG.md:1527
  2089. msgid "**TLDR**: All traces of the `matrix-nginx-proxy` reverse-proxy component are now gone. This brought about many other internal changes (and security improvements), so setups may need minor adjustments or suffer some (temporary) breakage. People who have been on the Traefik-native setup may upgrade without much issues. Those running their own Traefik instance may need minor changes. People who have been postponing the migration away from `matrix-nginx-proxy` (for more than a year already!) will now finally need to do something about it."
  2090. msgstr ""
  2091. #: ../../../CHANGELOG.md:1529
  2092. msgid "Backstory on `matrix-nginx-proxy`"
  2093. msgstr ""
  2094. #: ../../../CHANGELOG.md:1531
  2095. msgid "We gather here today to celebrate the loss of a once-beloved component in our stack — `matrix-nginx-proxy`. It's been our [nginx](https://nginx.org/)-based reverse-proxy of choice since the [first commit](https://github.com/spantaleev/matrix-docker-ansible-deploy/tree/87f5883f2455fb115457b65f267f17de305c053c) of this playbook, 7 years ago."
  2096. msgstr ""
  2097. #: ../../../CHANGELOG.md:1533
  2098. msgid "For 6 years, `matrix-nginx-proxy` has been the front-most reverse-proxy in our setup (doing SSL termination, etc.). After [transitioning to Traefik last year](#traefik-is-the-default-reverse-proxy-now), `matrix-nginx-proxy` took a step back. Nevertheless, since it was so ingrained into the playbook, it still remained in use — even if only internally. Despite our warnings of its imminent death, many of you have indubitably continued to use it instead of Traefik. Its suffering continued for too long, because it served many different purposes and massive effort was required to transition them to others."
  2099. msgstr ""
  2100. #: ../../../CHANGELOG.md:1535
  2101. msgid "To us, `matrix-nginx-proxy` was:"
  2102. msgstr ""
  2103. #: ../../../CHANGELOG.md:1537
  2104. msgid "an [nginx](https://nginx.org/)-based reverse-proxy"
  2105. msgstr ""
  2106. #: ../../../CHANGELOG.md:1538
  2107. msgid "an Ansible role organizing the work of [certbot](https://certbot.eff.org/) — retrieving free [Let's Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-proxy` and for the [coturn TURN server](./docs/configuring-playbook-turn.md)"
  2108. msgstr ""
  2109. #: ../../../CHANGELOG.md:1539
  2110. msgid "a central component for reverse-proxying to the [long list of services](./docs/configuring-playbook.md) supported by the playbook. As such, it became a dependency that all these services had to inject themselves into during runtime"
  2111. msgstr ""
  2112. #: ../../../CHANGELOG.md:1540
  2113. msgid "an intermediary through which addons (bridges, bots) communicated with the homeserver. Going through an intermediary (instead of directly talking to the homeserver) is useful when certain components (like [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) are enabled, because it lets these services \"steal routes\" from the homeserver"
  2114. msgstr ""
  2115. #: ../../../CHANGELOG.md:1541
  2116. msgid "a webserver for serving the `/.well-known/matrix` static files (generated by the `matrix-base` role until now)"
  2117. msgstr ""
  2118. #: ../../../CHANGELOG.md:1542
  2119. msgid "a webserver [serving your base domain](./docs/configuring-playbook-base-domain-serving.md) (and also generating the `index.html` page for it)"
  2120. msgstr ""
  2121. #: ../../../CHANGELOG.md:1543
  2122. msgid "a central component providing global [HTTP Basic Auth](https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication) password-protection for all `/metrics` endpoints when metrics were exposed publicly for consumption from a remote Prometheus server"
  2123. msgstr ""
  2124. #: ../../../CHANGELOG.md:1545
  2125. msgid "Talk about a jack of all trades! The [UNIX philosophy](https://en.wikipedia.org/wiki/Unix_philosophy) (and Docker container philosophy) of \"do one thing and do it well\" had been severely violated for too long."
  2126. msgstr ""
  2127. #: ../../../CHANGELOG.md:1547
  2128. msgid "On a related note, we also had a large chain of reverse-proxies in the mix. In the worst case, it was something like this: (Traefik -> `matrix-nginx-proxy:8080` -> `matrix-nginx-proxy:12080` -> `matrix-synapse-reverse-proxy-companion:8008` -> `matrix-synapse:8008`)."
  2129. msgstr ""
  2130. #: ../../../CHANGELOG.md:1549
  2131. msgid "Due to complexity and the playbook's flexibility (trying to accommodate a mix of tens of components), many layers of indirection were necessary. We do like reverse-proxies, but… not quite enough to enjoy going through a chain of ~4 of them before reaching the target service."
  2132. msgstr ""
  2133. #: ../../../CHANGELOG.md:1551
  2134. msgid "After **a ton of work** in the last weeks (200+ commits, which changed 467 files - 8684 insertions and 8913 deletions), **we're finally saying goodbye** to `matrix-nginx-proxy`."
  2135. msgstr ""
  2136. #: ../../../CHANGELOG.md:1553
  2137. msgid "Going Traefik-native and cutting out all middlemen"
  2138. msgstr ""
  2139. #: ../../../CHANGELOG.md:1555
  2140. msgid "In our new setup, you'll see the bare minimum number of reverse-proxies."
  2141. msgstr ""
  2142. #: ../../../CHANGELOG.md:1557
  2143. msgid "In most cases, there's only Traefik and all services being registered directly with it. When [Synapse workers](./docs/configuring-playbook-synapse.md#load-balancing-with-workers) are enabled, `matrix-synapse-reverse-proxy-companion` remains as an extra reverse-proxy that requests go through (for load-balancing to the correct Synapse worker), but in all other cases services are exposed directly."
  2144. msgstr ""
  2145. #: ../../../CHANGELOG.md:1559
  2146. msgid "This reduces \"network\" hops (improving performance) and also decreases the number of components (containers). Each Ansible role in our setup is now independent and doesn't need to interact with other roles during runtime."
  2147. msgstr ""
  2148. #: ../../../CHANGELOG.md:1561
  2149. msgid "Traefik now has an extra job"
  2150. msgstr ""
  2151. #: ../../../CHANGELOG.md:1563
  2152. msgid "Previously, **Traefik had a single purpose** — being the main reverse-proxy. It was either front-most (terminating SSL, etc.) or you were [fronting Traefik with your own other reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy). In any case — it had this central (yet decentralized) job."
  2153. msgstr ""
  2154. #: ../../../CHANGELOG.md:1565
  2155. msgid "Now, **Traefik has one more role** — it serves as an intermediary which allows addon services (bridges, bots, etc.) to communicate with the homeserver. As mentioned above, such an intermediary service is not strictly necessary in all kinds of setups, but more complex setups (including [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) benefit from it."
  2156. msgstr ""
  2157. #: ../../../CHANGELOG.md:1567
  2158. msgid "To perform this new role, Traefik now has a new internal [entrypoint](https://doc.traefik.io/traefik/routing/entrypoints/) called `matrix-internal-matrix-client-api`. All homeservers (Conduit, Dendrite, Synapse and even `matrix-synapse-reverse-proxy-companion`) and homeserver-related core services ([matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md), [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md) and potentially others) register their routes (using [container labels](https://docs.docker.com/config/labels-custom-metadata/)) not only on the public entrypoints (`web-secure`, `matrix-federation`), but also on this new internal entrypoint."
  2159. msgstr ""
  2160. #: ../../../CHANGELOG.md:1569
  2161. msgid "Doing so, services can contact Traefik on this entrypoint's dedicated port (the URL defaults to `http://matrix-traefik:8008`) and reach the homeserver Client-Server API as they expect. Internally, Traefik takes care of the routing to the correct service."
  2162. msgstr ""
  2163. #: ../../../CHANGELOG.md:1571
  2164. msgid "We've also considered keeping it simple and having services talk to the homeserver over the public internet (e.g. `https://matrix.example.com`) thus reusing all existing Traefik routing labels. In this scenario, performance was incredibly poor (e.g. 70 rps, instead of 1400 rps) due to TLS and networking overhead. The need for fast internal communication (via the new internal non-TLS-enabled Traefik entrypoint) is definitely there. In our benchmarks, Traefik even proved more efficient than nginx at doing this: ~1200 rps for Traefik compared to ~900 rps for nginx (out of ~1400 rps when talking to the Synapse homeserver directly)."
  2165. msgstr ""
  2166. #: ../../../CHANGELOG.md:1573
  2167. msgid "Traefik serving this second purpose has a few downsides:"
  2168. msgstr ""
  2169. #: ../../../CHANGELOG.md:1575
  2170. msgid "Traefik becomes a runtime dependency for all homeserver-dependant container services"
  2171. msgstr ""
  2172. #: ../../../CHANGELOG.md:1576
  2173. msgid "all homeserver-dependant services now need to be connected to the `traefik` container network, even if they don't need public internet exposure"
  2174. msgstr ""
  2175. #: ../../../CHANGELOG.md:1578
  2176. msgid "Despite these downsides (which the playbook manages automatically), we believe it's still a good compromise given the amount of complexity it eliminates and the performance benefits it yields. One alternative we've [considered](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3045#issuecomment-1867327001) was adding a new intermediary service (e.g. `matrix-homeserver-proxy` powered by nginx), but this both had much higher complexity (one more component in the mix; duplication of effort to produce nginx-compatible route definitions for it) and slightly worse performance (see above)."
  2177. msgstr ""
  2178. #: ../../../CHANGELOG.md:1580
  2179. msgid "People running the default Traefik setup do not need to do anything to make Traefik take on this extra job. Your Traefik configuration will be updated automatically."
  2180. msgstr ""
  2181. #: ../../../CHANGELOG.md:1582
  2182. msgid "**People running their own Traefik reverse-proxy need to do [minor adjustments](#people-managing-their-own-traefik-instance-need-to-do-minor-changes)**, as described in the section below."
  2183. msgstr ""
  2184. #: ../../../CHANGELOG.md:1584
  2185. msgid "You may disable Traefik acting as an intermediary by explicitly setting `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_enabled` to `false`. Services would then be configured to talk to the homeserver directly, giving you a slight performance boost and a \"simpler\" Traefik setup. However, such a configuration is less tested and will cause troubles, especially if you enable more services (like `matrix-media-repo`, etc.) in the future. As such, it's not recommended."
  2186. msgstr ""
  2187. #: ../../../CHANGELOG.md:1586
  2188. msgid "People managing their own Traefik instance need to do minor changes"
  2189. msgstr ""
  2190. #: ../../../CHANGELOG.md:1588
  2191. msgid "This section is for people [managing their own Traefik instance on the Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you). Those [using Traefik managed by the playbook](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) don't need to do any changes."
  2192. msgstr ""
  2193. #: ../../../CHANGELOG.md:1590
  2194. msgid "Because [Traefik has an extra job now](#traefik-now-has-an-extra-job), you need to adapt your configuration to add the additional `matrix-internal-matrix-client-api` entrypoint and potentially configure the `matrix_playbook_reverse_proxy_container_network` variable. See the [Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you) documentation section for more details."
  2195. msgstr ""
  2196. #: ../../../CHANGELOG.md:1592
  2197. msgid "People fronting Traefik with another reverse proxy need to do minor changes"
  2198. msgstr ""
  2199. #: ../../../CHANGELOG.md:1594
  2200. msgid "We've already previously mentioned that you need to do some minor [configuration changes related to `traefik_additional_entrypoints_auto`](#backward-compatibility-configuration-changes-required-for-people-fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)."
  2201. msgstr ""
  2202. #: ../../../CHANGELOG.md:1596
  2203. msgid "If you don't do these changes (switching from `traefik_additional_entrypoints_auto` to multiple other variables), your Traefik setup will not automatically receive the new `matrix-internal-matrix-client-api` Traefik entrypoint and Traefik would not be able to perform [its new duty of connecting addons with the homeserver](#traefik-now-has-an-extra-job)."
  2204. msgstr ""
  2205. #: ../../../CHANGELOG.md:1598
  2206. msgid "Supported reverse proxy types are now fewer"
  2207. msgstr ""
  2208. #: ../../../CHANGELOG.md:1600
  2209. msgid "This section is for people using a more custom reverse-proxy setup — those having `matrix_playbook_reverse_proxy_type` set to a value different than the default (`playbook-managed-traefik`)."
  2210. msgstr ""
  2211. #: ../../../CHANGELOG.md:1602
  2212. msgid "Previously, we allowed you to set `matrix_playbook_reverse_proxy_type` to 7 different values to accommodate various reverse-proxy setups."
  2213. msgstr ""
  2214. #: ../../../CHANGELOG.md:1604
  2215. msgid "The complexity of this is too high, so we only support 3 values right now:"
  2216. msgstr ""
  2217. #: ../../../CHANGELOG.md:1606
  2218. msgid "(the default) `playbook-managed-traefik`, when you're [using Traefik managed by the playbook](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook)"
  2219. msgstr ""
  2220. #: ../../../CHANGELOG.md:1607
  2221. msgid "`other-traefik-container`, when you're [managing your own Traefik instance on the Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)"
  2222. msgstr ""
  2223. #: ../../../CHANGELOG.md:1608
  2224. msgid "`none`, when you wish for [no reverse-proxy integration to be done at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all)"
  2225. msgstr ""
  2226. #: ../../../CHANGELOG.md:1610
  2227. msgid "The `none` value is not recommended and may not work adequately, due to lack of testing and [Traefik's new responsibilities](#traefik-now-has-an-extra-job) in our setup."
  2228. msgstr ""
  2229. #: ../../../CHANGELOG.md:1612
  2230. msgid "**Previous values that are now gone** (and the playbook would report them as such) are: `playbook-managed-nginx`, `other-nginx-non-container`, `other-on-same-host` and `other-on-another-host`."
  2231. msgstr ""
  2232. #: ../../../CHANGELOG.md:1614
  2233. msgid "If you were using these values as a way to stay away from Traefik, you now have 2 options:"
  2234. msgstr ""
  2235. #: ../../../CHANGELOG.md:1616
  2236. msgid "(recommended) [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)"
  2237. msgstr ""
  2238. #: ../../../CHANGELOG.md:1617
  2239. msgid "(not recommended) [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all) and reverse-proxying to each and every service manually"
  2240. msgstr ""
  2241. #: ../../../CHANGELOG.md:1619
  2242. msgid "Container networking changes"
  2243. msgstr ""
  2244. #: ../../../CHANGELOG.md:1621
  2245. msgid "Now that `matrix-nginx-proxy` is not in the mix, it became easier to clear out some other long-overdue technical debt."
  2246. msgstr ""
  2247. #: ../../../CHANGELOG.md:1623
  2248. msgid "Since the very beginning of this playbook, all playbook services were connected to a single (shared) `matrix` container network. Later on, some additional container networks appeared, but most services (database, etc.) still remained in the `matrix` container network. This meant that any random container in this network could try to talk (or attack) the Postgres database operating in the same `matrix` network."
  2249. msgstr ""
  2250. #: ../../../CHANGELOG.md:1625
  2251. msgid "Moving components (especially the database) into other container networks was difficult — it required changes to many other components to ensure correct connectivity."
  2252. msgstr ""
  2253. #: ../../../CHANGELOG.md:1627
  2254. msgid "All the hard work has been done now. We've added much more isolation between services by splitting them up into separate networks (`matrix-homeserver`, `matrix-addons`, `matrix-monitoring`, `matrix-exim-relay`, etc). Components are only joined to the networks they need and should (for the most part) not be able to access unrelated things."
  2255. msgstr ""
  2256. #: ../../../CHANGELOG.md:1629
  2257. msgid "Carrying out these container networking changes necessitated modifying many components, so **we're hoping not too many bugs were introduced in the process**."
  2258. msgstr ""
  2259. #: ../../../CHANGELOG.md:1631
  2260. msgid "We've refrained from creating too many container networks (e.g. one for each component), to avoid exhausting Docker's default network pool and contaminating the container networks list too much."
  2261. msgstr ""
  2262. #: ../../../CHANGELOG.md:1633
  2263. msgid "Metrics exposure changes"
  2264. msgstr ""
  2265. #: ../../../CHANGELOG.md:1635
  2266. msgid "This section is for people who are exposing monitoring metrics publicly, to be consumed by an external Prometheus server."
  2267. msgstr ""
  2268. #: ../../../CHANGELOG.md:1637
  2269. msgid "Previously, `matrix-nginx-proxy` was potentially password-protecting all `/metrics/*` endpoints with the same username and password (specified as plain-text in your `vars.yml` configuration file)."
  2270. msgstr ""
  2271. #: ../../../CHANGELOG.md:1639
  2272. msgid "From now on, there are new variables for doing roughly the same — `matrix_metrics_exposure_enabled`, `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`. See the [Prometheus & Grafana](./docs/configuring-playbook-prometheus-grafana.md) docs page for details."
  2273. msgstr ""
  2274. #: ../../../CHANGELOG.md:1641
  2275. msgid "`matrix-nginx-proxy` is not acting as a \"global guardian\" anymore. Now, each role provides its own metrics exposure and protection by registering with Traefik. Nevertheless, all roles are wired (via playbook configuration in `group_vars/matrix_servers`) to obey these new `matrix_metrics_exposure_*` variables. We've eliminated the centralization, but have kept the ease of use. Now, you can also do per-service password-protection (with different credentials), should you need to do that for some reason."
  2276. msgstr ""
  2277. #: ../../../CHANGELOG.md:1643
  2278. msgid "The playbook will tell you about all variables that you need to migrate during runtime, so rest assured — you shouldn't be able to miss anything!"
  2279. msgstr ""
  2280. #: ../../../CHANGELOG.md:1645
  2281. msgid "Matrix static files"
  2282. msgstr ""
  2283. #: ../../../CHANGELOG.md:1647
  2284. msgid "As mentioned above, static files like `/.well-known/matrix/*` or your base domain's `index.html` file (when [serving the base domain via the Matrix server](./docs/configuring-playbook-base-domain-serving.md) was enabled) were generated by the `matrix-base` or `matrix-nginx-proxy` roles and put into a `/matrix/static-files` directory on the server. Then `matrix-nginx-proxy` was serving all these static files."
  2285. msgstr ""
  2286. #: ../../../CHANGELOG.md:1649
  2287. msgid "All of this has been extracted into a new `matrix-static-files` Ansible role that's part of the playbook. The static files generated by this new role still live at roughly the same place (`/matrix/static-files/public` directory, instead of `/matrix/static-files`)."
  2288. msgstr ""
  2289. #: ../../../CHANGELOG.md:1651
  2290. msgid "The playbook will migrate and update the `/.well-known/matrix/*` files automatically but not your own files in `nginx-proxy/data/matrix-domain/` you will need to back these up yourself otherwise they will be lost. It will also warn you about usage of old variable names, so you can adapt to the new names."
  2291. msgstr ""
  2292. #: ../../../CHANGELOG.md:1653
  2293. msgid "A note on performance"
  2294. msgstr ""
  2295. #: ../../../CHANGELOG.md:1655
  2296. msgid "Some of you have been voicing their concerns (for a long time) about Traefik being too slow and nginx being better."
  2297. msgstr ""
  2298. #: ../../../CHANGELOG.md:1657
  2299. msgid "Some online benchmarks support this by demonstrating slightly higher SSL-termination performance in favor of nginx. The upcoming Traefik v3 release is [said to](https://medium.com/beyn-technology/is-nginx-dead-is-traefik-v3-20-faster-than-traefik-v2-f28ffb7eed3e) improve Traefik's SSL performance by some 20%, but that still ends up being somewhat slower than nginx."
  2300. msgstr ""
  2301. #: ../../../CHANGELOG.md:1659
  2302. msgid "We believe that using Traefik provides way too many benefits to worry about this minor performance impairment."
  2303. msgstr ""
  2304. #: ../../../CHANGELOG.md:1661
  2305. msgid "The heaviest part of running a Matrix homeserver is all the slow and potentially inefficient things the homeserver (e.g. Synapse) is doing. These things affect performance much more than whatever reverse-proxy is in front. Your server will die the same way by joining the famously large **Matrix HQ** room, no matter which reverse-proxy you put in front."
  2306. msgstr ""
  2307. #: ../../../CHANGELOG.md:1663
  2308. msgid "Even our previously mentioned benchmarks (yielding ~1300 rps) are synthetic — hitting a useless `/_matrix/client/versions` endpoint. Real-use does much more than this."
  2309. msgstr ""
  2310. #: ../../../CHANGELOG.md:1665
  2311. msgid "If this is still not convincing enough for you and you want the best possible performance, consider [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) (thus having the slowest part — SSL termination — happen elsewhere) or [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all). The playbook will not get in your way of doing that, but these options may make your life much harder. Performance comes at a cost, after all."
  2312. msgstr ""
  2313. #: ../../../CHANGELOG.md:1667
  2314. msgid "Migration procedure"
  2315. msgstr ""
  2316. #: ../../../CHANGELOG.md:1669
  2317. msgid "The updated playbook will automatically perform some migration tasks for you:"
  2318. msgstr ""
  2319. #: ../../../CHANGELOG.md:1671
  2320. msgid "It will stop and remove the `matrix-nginx-proxy` systemd service and container for you. This behavior cannot be disabled. It's essential that this service gets stopped, because it remaining running (and having container labels) may confuse Traefik as to where to route HTTP requests."
  2321. msgstr ""
  2322. #: ../../../CHANGELOG.md:1673
  2323. msgid "It will delete the `/matrix/nginx-proxy` directory and all files within it. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_uninstallation_enabled: false` to your `vars.yml` configuration file. Doing so will leave its data around."
  2324. msgstr ""
  2325. #: ../../../CHANGELOG.md:1675
  2326. msgid "It will delete the `/matrix/ssl` directory and all files within it. You can disable this behavior by adding `matrix_playbook_migration_matrix_ssl_uninstallation_enabled: false` to your `vars.yml` configuration file. If you have some important certificates there for some reason, take them out or temporarily disable removal of these files until you do."
  2327. msgstr ""
  2328. #: ../../../CHANGELOG.md:1677
  2329. msgid "It will tell you about all variables (`matrix_nginx_proxy_*` and many others — even from other roles) that have changed during this large nginx-elimination upgrade. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_elimination_variable_transition_checks_enabled: false` to your `vars.yml` configuration file."
  2330. msgstr ""
  2331. #: ../../../CHANGELOG.md:1679
  2332. msgid "It will tell you about any leftover `matrix_nginx_proxy_*` variables in your `vars.yml` file. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_leftover_variable_validation_checks_enabled: false` to your `vars.yml` configuration file."
  2333. msgstr ""
  2334. #: ../../../CHANGELOG.md:1681
  2335. msgid "It will tell you about any leftover `matrix_ssl_*` variables in your `vars.yml` file. You can disable this behavior by adding `matrix_playbook_migration_matrix_ssl_leftover_variable_checks_enabled: false` to your `vars.yml` configuration file."
  2336. msgstr ""
  2337. #: ../../../CHANGELOG.md:1683
  2338. msgid "We don't recommend changing these variables and suppressing warnings, unless you know what you're doing."
  2339. msgstr ""
  2340. #: ../../../CHANGELOG.md:1685
  2341. msgid "**Most people should just upgrade as per-normal**, bearing in mind that a lot has changed and some issues may arise. The playbook would guide you through renamed variables automatically."
  2342. msgstr ""
  2343. #: ../../../CHANGELOG.md:1687
  2344. msgid "Conclusion"
  2345. msgstr ""
  2346. #: ../../../CHANGELOG.md:1689
  2347. msgid "Thousands of lines of code were changed across hundreds of files. All addons (bridges, bots) were rewired in terms of container networking and in terms of how they reach the homeserver."
  2348. msgstr ""
  2349. #: ../../../CHANGELOG.md:1691
  2350. msgid "I don't actively use all the ~100 components offered by the playbook (no one does), nor do I operate servers exercising all edge-cases. As such, issues may arise. Please have patience and report (or try to fix) these issues!"
  2351. msgstr ""
  2352. #: ../../../CHANGELOG.md:1694
  2353. msgid "2024-01-14"
  2354. msgstr ""
  2355. #: ../../../CHANGELOG.md:1696
  2356. msgid "(Backward Compatibility) Configuration changes required for people fronting the integrated reverse-proxy webserver with another reverse-proxy"
  2357. msgstr ""
  2358. #: ../../../CHANGELOG.md:1698
  2359. msgid "If you're on the default setup (using the Traefik reverse-proxy as installed by the playbook), you don't need to do anything."
  2360. msgstr ""
  2361. #: ../../../CHANGELOG.md:1700
  2362. msgid "People who are [Fronting the integrated Traefik reverse-proxy webserver with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy), as per our previous instructions are redefining `traefik_additional_entrypoints_auto` in their `vars.yml` configuration."
  2363. msgstr ""
  2364. #: ../../../CHANGELOG.md:1702
  2365. msgid "Such a full variable redefinion is intrustive, because it prevents the playbook from injecting additional entrypoints into the Traefik webserver. In the future, the playbook may have a need to do so."
  2366. msgstr ""
  2367. #: ../../../CHANGELOG.md:1704
  2368. msgid "For this reason, we no longer recommend completely redefining `traefik_additional_entrypoints_auto`. The playbook now defines [various `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_*` variables in the `defaults/main.yml` file](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-base/defaults/main.yml) of the `matrix-base` role which can be used as a safer alternative to `traefik_additional_entrypoints_auto`."
  2369. msgstr ""
  2370. #: ../../../CHANGELOG.md:1706
  2371. msgid "Adapt your configuration as seen below:"
  2372. msgstr ""
  2373. #: ../../../CHANGELOG.md:1739
  2374. msgid "Also, feel free to read the [Fronting the integrated Traefik reverse-proxy webserver with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) documentation section again for additional details."
  2375. msgstr ""
  2376. #: ../../../CHANGELOG.md:1742
  2377. msgid "2024-01-13"
  2378. msgstr ""
  2379. #: ../../../CHANGELOG.md:1744
  2380. msgid "matrix-reminder-bot update with more secure (backward-incompatible) default settings"
  2381. msgstr ""
  2382. #: ../../../CHANGELOG.md:1746
  2383. msgid "**TLDR**: your updated (to [v0.3.0](https://github.com/anoadragon453/matrix-reminder-bot/releases/tag/v0.3.0)) [matrix-reminder-bot](./docs/configuring-playbook-bot-matrix-reminder-bot.md) is now more secure. By default, like other bridges/bots managed by the playbook, it will only provide its services to users of your own server (not to anyone, even across the Matrix Federation). If that's fine, there's nothing you need to do."
  2384. msgstr ""
  2385. #: ../../../CHANGELOG.md:1748
  2386. msgid "Maintenance of [matrix-reminder-bot](./docs/configuring-playbook-bot-matrix-reminder-bot.md) has been picked up by [Kim Brose](https://github.com/HarHarLinks) and [@svierne](https://github.com/svierne)."
  2387. msgstr ""
  2388. #: ../../../CHANGELOG.md:1750
  2389. msgid "Thanks to them, a new [v0.3.0](https://github.com/anoadragon453/matrix-reminder-bot/releases/tag/v0.3.0) release is out. The new version is now available for the ARM64 architecture, so playbook users on this architecture will no longer need to wait for [self-building](./docs/self-building.md) to happen."
  2390. msgstr ""
  2391. #: ../../../CHANGELOG.md:1752
  2392. msgid "The new version also comes with new `allowlist` and `blocklist` settings, which make it possible to restrict who can use the bot. Previously anyone, even across the Matrix Federation could talk to it and schedule reminders."
  2393. msgstr ""
  2394. #: ../../../CHANGELOG.md:1754
  2395. msgid "The playbook defaults all bridges and bots (where possible) to only be exposed to users of the current homeserver, not users across federation. Thanks to the new version of this bot making such a restriction possible, we're now making use of it. The playbook (via its `group_vars/matrix_servers` file) automatically enables the `allowlist` (`matrix_bot_matrix_reminder_bot_allowlist_enabled: true`) and configures it in such a way (`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) so as to restrict the bot to your homeserver's users."
  2396. msgstr ""
  2397. #: ../../../CHANGELOG.md:1756
  2398. msgid "If you need **to undo or tweak these security improvements**, you can change your `vars.yml` file to:"
  2399. msgstr ""
  2400. #: ../../../CHANGELOG.md:1758
  2401. msgid "disable the allowlist (`matrix_bot_matrix_reminder_bot_allowlist_enabled: false`), making the bot allow usage by anyone, anywhere"
  2402. msgstr ""
  2403. #: ../../../CHANGELOG.md:1760
  2404. msgid "inject additional allowed servers or users by adding **additional** (on top of the default allowlist in `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) custom regexes in the `matrix_bot_matrix_reminder_bot_allowlist_regexes_custom` list variable (see the [syntax reference](https://github.com/anoadragon453/matrix-reminder-bot/blob/1e910c0aa3469d280d93ee7e6c6d577227a3460c/sample.config.yaml#L43-L49))"
  2405. msgstr ""
  2406. #: ../../../CHANGELOG.md:1762
  2407. msgid "override the default allowlist (in the `group_vars/matrix_servers` file) by redefining `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`"
  2408. msgstr ""
  2409. #: ../../../CHANGELOG.md:1765
  2410. msgid "2024-01-05"
  2411. msgstr ""
  2412. #: ../../../CHANGELOG.md:1767
  2413. msgid "matrix-mailer has been replaced by the exim-relay external role"
  2414. msgstr ""
  2415. #: ../../../CHANGELOG.md:1769
  2416. #: ../../../CHANGELOG.md:2407
  2417. msgid "We're continuing our effort to make [the playbook use external roles for some things](#the-playbook-now-uses-external-roles-for-some-things), so as to avoid doing everything ourselves and to facilitate code re-use."
  2418. msgstr ""
  2419. #: ../../../CHANGELOG.md:1771
  2420. msgid "The `matrix-mailer` role has been moved to its own repository ([ansible-role-exim-relay](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay)) that this playbook now includes."
  2421. msgstr ""
  2422. #: ../../../CHANGELOG.md:1773
  2423. msgid "To migrate:"
  2424. msgstr ""
  2425. #: ../../../CHANGELOG.md:1775
  2426. msgid "pull the playbook changes, as usual"
  2427. msgstr ""
  2428. #: ../../../CHANGELOG.md:1776
  2429. msgid "update your roles (run `just roles` or `make roles`)"
  2430. msgstr ""
  2431. #: ../../../CHANGELOG.md:1777
  2432. msgid "update your `vars.yml`, renaming `matrix_mailer`-prefixed variables to `exim_relay`-prefixed ones (e.g. `matrix_mailer_sender_address` -> `exim_relay_sender_address`). If you find none, it means you're using the default configuration and your migraiton job is even simpler."
  2433. msgstr ""
  2434. #: ../../../CHANGELOG.md:1778
  2435. msgid "re-run the playbook (`install-all` or `setup-all`)"
  2436. msgstr ""
  2437. #: ../../../CHANGELOG.md:1780
  2438. msgid "The playbook will take care of stopping the old `matrix-mailer` systemd service, relocating its directory and restarting it under the new name (`matrix-exim-relay.service`)."
  2439. msgstr ""
  2440. #: ../../../CHANGELOG.md:1783
  2441. msgid "2024-01-02"
  2442. msgstr ""
  2443. #: ../../../CHANGELOG.md:1785
  2444. msgid "mautrix-signal now powered by the new Go-based bridge"
  2445. msgstr ""
  2446. #: ../../../CHANGELOG.md:1787
  2447. msgid "The old Python-based [mautrix-signal](https://github.com/mautrix/signal) bridge is no longer maintained upstream. It's also known to have issues linking new devices."
  2448. msgstr ""
  2449. #: ../../../CHANGELOG.md:1789
  2450. msgid "It seems like the path forward is to switch to the new mautrix-signal bridge written in Golang, which we did thanks to [PR #3031](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3041) by [Pierre 'McFly' Marty](https://github.com/pm-McFly)."
  2451. msgstr ""
  2452. #: ../../../CHANGELOG.md:1791
  2453. msgid "The playbook should **automatically migrate your mautrix-signal installation to the new bridge code**. You will **need to relink all your devices** to continue your bridged conversations."
  2454. msgstr ""
  2455. #: ../../../CHANGELOG.md:1794
  2456. msgid "2023-10-23"
  2457. msgstr ""
  2458. #: ../../../CHANGELOG.md:1796
  2459. msgid "Enabling `allow_public_rooms_over_federation` by default for Synapse"
  2460. msgstr ""
  2461. #: ../../../CHANGELOG.md:1798
  2462. msgid "**TDLR**: if your Matrix server is federating (which it mostly likely is, unless you've [disabled federation](docs/configuring-playbook-federation.md#disabling-federation)), your public rooms will not only be joinable across federation (as they've always been), but from now on will be discoverable (made available as a list across federation). We're changing this by flipping the value for Synapse's `allow_public_rooms_over_federation` setting to `true`, going against the upstream default. Servers that disable federation are not affected. Servers that have public rooms which are not published to the room directory are also not affected."
  2463. msgstr ""
  2464. #: ../../../CHANGELOG.md:1800
  2465. msgid "We generally try to stick to the default configuration for Synapse (and all other components), unless these defaults seem wrong or harmful. One such previous case from a few months ago was us [Enabling `forget_rooms_on_leave` by default for Synapse](#enabling-forget_rooms_on_leave-by-default-for-synapse) — the default value was making Synapse more wasteful of resources by default."
  2466. msgstr ""
  2467. #: ../../../CHANGELOG.md:1802
  2468. msgid "Today, we're going against upstream defaults again and flipping the `allow_public_rooms_over_federation` configuration option to `true`. This way, public rooms on your server will be made discoverable by others via federation, using the [`GET /_matrix/federation/v1/publicRooms` of the Server-Server API](https://spec.matrix.org/v1.8/server-server-api/#get_matrixfederationv1publicrooms)."
  2469. msgstr ""
  2470. #: ../../../CHANGELOG.md:1804
  2471. msgid "The upstream Synapse default is `false` (disabled), so that public rooms are not exposed for other servers to discover (learn about their existence). Nevertheless, even if these rooms are not exposed (listed) for discovery, they are **still joinable** by anyone who knows their address or is invited to the room by an existing member."
  2472. msgstr ""
  2473. #: ../../../CHANGELOG.md:1806
  2474. msgid "**We go against the upstream default** in an effort to make Matrix federation more useful — a public room should be globally public — not only joinable, but also discoverable across federation."
  2475. msgstr ""
  2476. #: ../../../CHANGELOG.md:1808
  2477. msgid "The **historical reasoning** behind this change is as follows:"
  2478. msgstr ""
  2479. #: ../../../CHANGELOG.md:1810
  2480. msgid "`allow_public_rooms_over_federation` seems to have been enabled by default for Synapse until v1.7.0 (~2019), just like we believe it should be for a globally-federating network — rooms should be joinable and discoverable across federation."
  2481. msgstr ""
  2482. #: ../../../CHANGELOG.md:1812
  2483. msgid "In Synapse v1.7.0 (~2019), `allow_public_rooms_over_federation` [got disabled](https://github.com/element-hq/synapse/blob/e9069c9f919685606506f04527332e83fbfa44d9/docs/upgrade.md?plain=1#L1877-L1891) by default in a [security-by-obscurity](https://en.wikipedia.org/wiki/Security_through_obscurity) workaround for misconfigured servers. See the [Avoiding unwelcome visitors on private Matrix servers](https://matrix.org/blog/2019/11/09/avoiding-unwelcome-visitors-on-private-matrix-servers/) `matrix.org` blog article. We believe that people wishing for a truly private server, should [disable federation](docs/configuring-playbook-federation.md#disabling-federation), instead of having a fully-federating server and trying to hide its public rooms. We also provide other workarounds below. We (and the Synapse team, obviously) believe that Matrix should federate by default, so federating the public room list seems to make sense."
  2484. msgstr ""
  2485. #: ../../../CHANGELOG.md:1814
  2486. msgid "[etke.cc](https://etke.cc/) has been developing the free-software [Matrix Rooms Search](https://github.com/etkecc/mrs) project for a while now. One public (demo) instance of it is hosted at [matrixrooms.info](https://matrixrooms.info/). This search engine tries to go through the Matrix federation and discover & index public rooms to allow people to find them. We believe it's vital for Matrix (and any chat or social network for that matter) to be more discoverable, so that people can find communities and others to talk to. Today (on 23rd of October 2023), `matrixrooms.info` is indexing `23066` Matrix servers. Of these, only `1567` servers (7%) are making their public rooms discoverable. Who knows what wonderful communities and rooms are available on these 93% other Matrix servers that are supposedly federating, but are still gate-keeping their public room list. Indubitably, many of these servers are hosted via matrix-docker-ansible-deploy, so we feel partially responsible for making Matrix federation less useful."
  2487. msgstr ""
  2488. #: ../../../CHANGELOG.md:1816
  2489. msgid "Here are **actions you may wish to take** as a result of this change:"
  2490. msgstr ""
  2491. #: ../../../CHANGELOG.md:1818
  2492. msgid "(recommended) embrace the new default. If your Matrix server is federating, your public rooms have always been joinable across federation anyway. Exposing the list of public rooms does no harm and more-so does good by contributing to the usefulness of the Matrix network by facilitating room discovery."
  2493. msgstr ""
  2494. #: ../../../CHANGELOG.md:1820
  2495. msgid "(switch to a better way of doings things on your semi-private server) The problem that the Synapse team appears to have solved by flipping the `allow_public_rooms_over_federation` default in Synapse v1.7.0 seems to for \"mostly private\" servers, which federate and have a bunch of rooms made public (and published in their room directory) in an effort to allow people on the same homeserver to easily find and join them (self-onboarding). With the introduction of Matrix Spaces, you can reorganize your flow around spaces — you can auto-join your users to a Matrix Space (via Synapse's `auto_join_rooms` setting — controlled by our `matrix_synapse_auto_join_rooms` variable), then add a bunch of rooms to the space and make them joinable by people belonging to the space. That is to say, do not make rooms public and do not publish them to the room directory unless they are really public. Instead, use other mechanisms for semi-public rooms or private rooms. One alternative is to stick to what you're doing (public rooms published to your rooms directory) but having a `m.federate: true` flag set during creation (clients like Element Web have a nice UI checkbox for this) to explicitly disable federation for them."
  2496. msgstr ""
  2497. #: ../../../CHANGELOG.md:1822
  2498. msgid "(keeping the old behavior) if you wish to keep doing what you're doing (keeping your Matrix server federating, but hiding its public rooms list), add `matrix_synapse_allow_public_rooms_over_federation: false` to your `vars.yml` configuration. This restores the old behavior. You may also consider [disabling federation](docs/configuring-playbook-federation.md#disabling-federation) completely instead of relying on security-by-obscurity measures."
  2499. msgstr ""
  2500. #: ../../../CHANGELOG.md:1825
  2501. msgid "2023-10-18"
  2502. msgstr ""
  2503. #: ../../../CHANGELOG.md:1827
  2504. msgid "Postgres parameters are automatically tuned now"
  2505. msgstr ""
  2506. #: ../../../CHANGELOG.md:1829
  2507. msgid "The playbook has provided some hints about [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) for quite a while now."
  2508. msgstr ""
  2509. #: ../../../CHANGELOG.md:1831
  2510. msgid "From now on, the [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) automatically tunes your Postgres configuration with the same [calculation logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) that powers https://pgtune.leopard.in.ua/."
  2511. msgstr ""
  2512. #: ../../../CHANGELOG.md:1833
  2513. msgid "Our [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) documentation page has details about how you can turn auto-tuning off or adjust the automatically-determined Postgres configuration parameters manually."
  2514. msgstr ""
  2515. #: ../../../CHANGELOG.md:1835
  2516. msgid "People who [enable load-balancing with Synapse workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) no longer need to increase the maximum number of Postgres connections manually (previously done via `postgres_process_extra_arguments`). There's a new variable (`postgres_max_connections`) for controlling this number and the playbook automatically raises its value from `200` to `500` for setups which enable workers."
  2517. msgstr ""
  2518. #: ../../../CHANGELOG.md:1838
  2519. msgid "2023-08-31"
  2520. msgstr ""
  2521. #: ../../../CHANGELOG.md:1840
  2522. msgid "SchildiChat Web support"
  2523. msgstr ""
  2524. #: ../../../CHANGELOG.md:1842
  2525. msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client."
  2526. msgstr ""
  2527. #: ../../../CHANGELOG.md:1844
  2528. msgid "See our [Configuring SchildiChat Web](docs/configuring-playbook-client-schildichat-web.md) documentation to get started."
  2529. msgstr ""
  2530. #: ../../../CHANGELOG.md:1847
  2531. msgid "2023-08-23"
  2532. msgstr ""
  2533. #: ../../../CHANGELOG.md:1849
  2534. msgid "mautrix-wsproxy support"
  2535. msgstr ""
  2536. #: ../../../CHANGELOG.md:1851
  2537. msgid "Thanks to [Johan Swetzén](https://github.com/jswetzen)'s efforts (who finished what was started by [James Reilly](https://github.com/hanthor) and [Shreyas Ajjarapu](https://github.com/shreyasajj)), the playbook now supports bridging to Android SMS and Apple iMessage via the [mautrix-wsproxy](https://github.com/mautrix/wsproxy) service (in combination with a [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android phone)."
  2538. msgstr ""
  2539. #: ../../../CHANGELOG.md:1853
  2540. msgid "See our [Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](docs/configuring-playbook-bridge-mautrix-wsproxy.md) documentation page for getting started."
  2541. msgstr ""
  2542. #: ../../../CHANGELOG.md:1856
  2543. msgid "2023-07-24"
  2544. msgstr ""
  2545. #: ../../../CHANGELOG.md:1858
  2546. msgid "matrix-registration-bot usage changed"
  2547. msgstr ""
  2548. #: ../../../CHANGELOG.md:1860
  2549. msgid "[matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) got some updates and now supports password-only-based login. Therefore the bot now doesn't need any manual configuration except setting a password in your `vars.yml`. The bot will be registered as admin and access tokens will be obtained automatically by the bot."
  2550. msgstr ""
  2551. #: ../../../CHANGELOG.md:1862
  2552. msgid "**For existing users** You need to set `matrix_bot_matrix_registration_bot_bot_password` if you previously only used `matrix_bot_matrix_registration_bot_bot_access_token`. Please also remove the following deprecated settings"
  2553. msgstr ""
  2554. #: ../../../CHANGELOG.md:1864
  2555. msgid "`matrix_bot_matrix_registration_bot_bot_access_token`"
  2556. msgstr ""
  2557. #: ../../../CHANGELOG.md:1865
  2558. msgid "`matrix_bot_matrix_registration_bot_api_token`"
  2559. msgstr ""
  2560. #: ../../../CHANGELOG.md:1868
  2561. msgid "2023-07-21"
  2562. msgstr ""
  2563. #: ../../../CHANGELOG.md:1870
  2564. msgid "mautrix-gmessages support"
  2565. msgstr ""
  2566. #: ../../../CHANGELOG.md:1872
  2567. msgid "Thanks to [Shreyas Ajjarapu](https://github.com/shreyasajj)'s efforts, the playbook now supports bridging to [Google Messages](https://messages.google.com/) via the [mautrix-gmessages](https://github.com/mautrix/gmessages) bridge. See our [Setting up Mautrix Google Messages bridging](docs/configuring-playbook-bridge-mautrix-gmessages.md) documentation page for getting started."
  2568. msgstr ""
  2569. #: ../../../CHANGELOG.md:1875
  2570. msgid "2023-07-17"
  2571. msgstr ""
  2572. #: ../../../CHANGELOG.md:1877
  2573. msgid "matrix-media-repo support"
  2574. msgstr ""
  2575. #: ../../../CHANGELOG.md:1879
  2576. msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [matrix-media-repo](https://github.com/turt2live/matrix-media-repo) — an alternative way to store homeserver media files, powered by a homeserver-independent implementation which supports S3 storage, IPFS, deduplication and other advanced features."
  2577. msgstr ""
  2578. #: ../../../CHANGELOG.md:1881
  2579. msgid "To learn more see our [Storing Matrix media files using matrix-media-repo](docs/configuring-playbook-matrix-media-repo.md) documentation page."
  2580. msgstr ""
  2581. #: ../../../CHANGELOG.md:1884
  2582. msgid "2023-05-25"
  2583. msgstr ""
  2584. #: ../../../CHANGELOG.md:1886
  2585. msgid "Enabling `forget_rooms_on_leave` by default for Synapse"
  2586. msgstr ""
  2587. #: ../../../CHANGELOG.md:1888
  2588. msgid "With the [Synapse v1.84.0 update](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2698), we've also **changed the default value** of the `forget_rooms_on_leave` setting of Synapse to a value of `true`. This way, **when you leave a room, Synapse will now forget it automatically**."
  2589. msgstr ""
  2590. #: ../../../CHANGELOG.md:1890
  2591. msgid "The upstream Synapse default is `false` (disabled), so that you must forget rooms manually after leaving."
  2592. msgstr ""
  2593. #: ../../../CHANGELOG.md:1892
  2594. msgid "**We go against the upstream default** ([somewhat controversially](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2700)) in an effort to make Synapse leaner and potentially do what we believe most users would expect their homeserver to be doing."
  2595. msgstr ""
  2596. #: ../../../CHANGELOG.md:1894
  2597. msgid "If you'd like to go back to the old behavior, add the following to your configuration: `matrix_synapse_forget_rooms_on_leave: false`"
  2598. msgstr ""
  2599. #: ../../../CHANGELOG.md:1897
  2600. msgid "2023-04-03"
  2601. msgstr ""
  2602. #: ../../../CHANGELOG.md:1899
  2603. msgid "The matrix-jitsi role lives independently now"
  2604. msgstr ""
  2605. #: ../../../CHANGELOG.md:1901
  2606. msgid "**TLDR**: the `matrix-jitsi` role is now included from the [ansible-role-jitsi](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi) repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). Some variables have been renamed. All functionality remains intact."
  2607. msgstr ""
  2608. #: ../../../CHANGELOG.md:1903
  2609. msgid "The `matrix-jitsi` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project — an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Jitsi stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so."
  2610. msgstr ""
  2611. #: ../../../CHANGELOG.md:1905
  2612. msgid "As part of the extraction process of this role out of the Matrix playbook, a few other things improved:"
  2613. msgstr ""
  2614. #: ../../../CHANGELOG.md:1907
  2615. msgid "**native Traefik support** has been added"
  2616. msgstr ""
  2617. #: ../../../CHANGELOG.md:1908
  2618. msgid "**support for hosting under a subpath** has been added, although it suffers from a few minor issues listed [here](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/jitsi.md#url)"
  2619. msgstr ""
  2620. #: ../../../CHANGELOG.md:1910
  2621. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Jitsi or not."
  2622. msgstr ""
  2623. #: ../../../CHANGELOG.md:1912
  2624. msgid "If you're making use of Jitsi via this playbook, you will need to update variable references in your `vars.yml` file:"
  2625. msgstr ""
  2626. #: ../../../CHANGELOG.md:1914
  2627. msgid "`matrix_jitsi_*_docker_image_` -> `matrix_jitsi_*_container_image_`"
  2628. msgstr ""
  2629. #: ../../../CHANGELOG.md:1915
  2630. msgid "`matrix_jitsi_` -> `jitsi_`"
  2631. msgstr ""
  2632. #: ../../../CHANGELOG.md:1916
  2633. #: ../../../CHANGELOG.md:1943
  2634. msgid "some other internal variables have changed, but the playbook will tell you about them"
  2635. msgstr ""
  2636. #: ../../../CHANGELOG.md:1918
  2637. msgid "2023-03-22"
  2638. msgstr ""
  2639. #: ../../../CHANGELOG.md:1920
  2640. msgid "ntfy Web App is disabled by default"
  2641. msgstr ""
  2642. #: ../../../CHANGELOG.md:1922
  2643. msgid "ntfy provides a web app, which is now disabled by default, because it may be unknown to and unused by most users of this playbook. You can enable it by setting `ntfy_web_root: \"app\"` (see [ntfy documentation](docs/configuring-playbook-ntfy.md))."
  2644. msgstr ""
  2645. #: ../../../CHANGELOG.md:1924
  2646. msgid "This change was already applied a while before this entry, but as some users were reporting the missing web app, this entry was added (see [#2529](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2529))."
  2647. msgstr ""
  2648. #: ../../../CHANGELOG.md:1927
  2649. msgid "2023-03-21"
  2650. msgstr ""
  2651. #: ../../../CHANGELOG.md:1929
  2652. msgid "The matrix-prometheus role lives independently now"
  2653. msgstr ""
  2654. #: ../../../CHANGELOG.md:1931
  2655. msgid "**TLDR**: the `matrix-prometheus` role is now included from the [ansible-role-prometheus](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus) repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). Some variables have been renamed. All functionality remains intact."
  2656. msgstr ""
  2657. #: ../../../CHANGELOG.md:1933
  2658. msgid "The `matrix-prometheus` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project — an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Prometheus stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so."
  2659. msgstr ""
  2660. #: ../../../CHANGELOG.md:1935
  2661. msgid "Extracting the Prometheus role out of this Matrix playbook required huge internal refactoring to the way the Prometheus configuration (scraping jobs) is generated. If you notice any breakage after upgrading, let us know."
  2662. msgstr ""
  2663. #: ../../../CHANGELOG.md:1937
  2664. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Prometheus or not."
  2665. msgstr ""
  2666. #: ../../../CHANGELOG.md:1939
  2667. msgid "If you're making use of Prometheus via this playbook, you will need to update variable references in your `vars.yml` file:"
  2668. msgstr ""
  2669. #: ../../../CHANGELOG.md:1941
  2670. msgid "`matrix_prometheus_docker_image_` -> `matrix_prometheus_container_image_`"
  2671. msgstr ""
  2672. #: ../../../CHANGELOG.md:1942
  2673. msgid "`matrix_prometheus_` -> `prometheus_`"
  2674. msgstr ""
  2675. #: ../../../CHANGELOG.md:1946
  2676. msgid "2023-03-12"
  2677. msgstr ""
  2678. #: ../../../CHANGELOG.md:1948
  2679. msgid "synapse-auto-compressor support"
  2680. msgstr ""
  2681. #: ../../../CHANGELOG.md:1950
  2682. msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state)'s `synapse_auto_compressor` tool to run periodically."
  2683. msgstr ""
  2684. #: ../../../CHANGELOG.md:1952
  2685. msgid "If enabled, `synapse_auto_compressor` runs on a schedule and compresses your Synapse database's `state_groups` table. It was possible to run `rust-synapse-compress-state` manually via the playbook even before — see [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state). However, using `synapse_auto_compressor` is better, because:"
  2686. msgstr ""
  2687. #: ../../../CHANGELOG.md:1954
  2688. msgid "it runs on a more up-to-date version of `rust-synapse-compress-state`"
  2689. msgstr ""
  2690. #: ../../../CHANGELOG.md:1955
  2691. msgid "it's a set-it-and-forget-it tool that you can enable and never have to deal with manual compression anymore"
  2692. msgstr ""
  2693. #: ../../../CHANGELOG.md:1957
  2694. msgid "This tool needs to be enabled manually, for now. In the future, we're considering enabling it by default for all Synapse installations."
  2695. msgstr ""
  2696. #: ../../../CHANGELOG.md:1959
  2697. msgid "See our [Setting up synapse-auto-compressor](docs/configuring-playbook-synapse-auto-compressor.md) documentation to get started."
  2698. msgstr ""
  2699. #: ../../../CHANGELOG.md:1962
  2700. msgid "2023-03-07"
  2701. msgstr ""
  2702. #: ../../../CHANGELOG.md:1964
  2703. msgid "Sliding Sync proxy (Element X) support"
  2704. msgstr ""
  2705. #: ../../../CHANGELOG.md:1966
  2706. msgid "Thanks to [Benjamin Kampmann](https://github.com/gnunicorn) for [getting it started](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2515), [FSG-Cat](https://github.com/FSG-Cat) for fixing it up and me ([Slavi](https://github.com/spantaleev)) for polishing it up, the playbook can now install and configure the [sliding-sync proxy](https://github.com/matrix-org/sliding-sync)."
  2707. msgstr ""
  2708. #: ../../../CHANGELOG.md:1968
  2709. msgid "The upcoming Element X clients ([Element X iOS](https://github.com/vector-im/element-x-ios) and [Element X Android](https://github.com/vector-im/element-x-android)) require the `sliding-sync` proxy to do their job. **These clients are still in beta** (especially Element X Android, which requires manual compilation to get it working with a non-`matrix.org` homeseserver). Playbook users can now easily give these clients a try and help test them thanks to us having `sliding-sync` support."
  2710. msgstr ""
  2711. #: ../../../CHANGELOG.md:1970
  2712. msgid "To get started, see our [Setting up the Sliding Sync proxy](docs/configuring-playbook-sliding-sync-proxy.md) documentation page."
  2713. msgstr ""
  2714. #: ../../../CHANGELOG.md:1973
  2715. msgid "2023-03-02"
  2716. msgstr ""
  2717. #: ../../../CHANGELOG.md:1975
  2718. msgid "The matrix-etherpad role lives independently now"
  2719. msgstr ""
  2720. #: ../../../CHANGELOG.md:1977
  2721. msgid "**TLDR**: the `matrix-etherpad` role is now included from [another repository](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). Some variables have been renamed. All functionality remains intact."
  2722. msgstr ""
  2723. #: ../../../CHANGELOG.md:1979
  2724. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Etherpad or not."
  2725. msgstr ""
  2726. #: ../../../CHANGELOG.md:1981
  2727. msgid "If you're making use of Etherpad via this playbook, you will need to update variable references in your `vars.yml` file:"
  2728. msgstr ""
  2729. #: ../../../CHANGELOG.md:1983
  2730. msgid "Rename `matrix_etherpad_public_endpoint` to `etherpad_path_prefix`"
  2731. msgstr ""
  2732. #: ../../../CHANGELOG.md:1985
  2733. msgid "Replace `matrix_etherpad_mode: dimension` with:"
  2734. msgstr ""
  2735. #: ../../../CHANGELOG.md:1986
  2736. msgid "for `matrix-nginx-proxy` users:"
  2737. msgstr ""
  2738. #: ../../../CHANGELOG.md:1987
  2739. msgid "`etherpad_nginx_proxy_dimension_integration_enabled: true`"
  2740. msgstr ""
  2741. #: ../../../CHANGELOG.md:1988
  2742. msgid "`etherpad_hostname: \"{{ matrix_server_fqn_dimension }}\"`"
  2743. msgstr ""
  2744. #: ../../../CHANGELOG.md:1989
  2745. msgid "for Traefik users:"
  2746. msgstr ""
  2747. #: ../../../CHANGELOG.md:1990
  2748. msgid "define your own `etherpad_hostname` and `etherpad_path_prefix` as you see fit"
  2749. msgstr ""
  2750. #: ../../../CHANGELOG.md:1992
  2751. msgid "Rename all other variables:"
  2752. msgstr ""
  2753. #: ../../../CHANGELOG.md:1993
  2754. msgid "`matrix_etherpad_docker_image_` -> `matrix_etherpad_container_image_`"
  2755. msgstr ""
  2756. #: ../../../CHANGELOG.md:1994
  2757. msgid "`matrix_etherpad_` -> `etherpad_`"
  2758. msgstr ""
  2759. #: ../../../CHANGELOG.md:1996
  2760. msgid "Along with this relocation, the new role also:"
  2761. msgstr ""
  2762. #: ../../../CHANGELOG.md:1998
  2763. msgid "supports [self-building](docs/self-building.md), so it should work on `arm32` and `arm64` architectures"
  2764. msgstr ""
  2765. #: ../../../CHANGELOG.md:1999
  2766. msgid "has native Traefik reverse-proxy support (Etherpad requests no longer go through `matrix-nginx-proxy` when using Traefik)"
  2767. msgstr ""
  2768. #: ../../../CHANGELOG.md:2002
  2769. msgid "2023-02-26"
  2770. msgstr ""
  2771. #: ../../../CHANGELOG.md:2004
  2772. msgid "Traefik is the default reverse-proxy now"
  2773. msgstr ""
  2774. #: ../../../CHANGELOG.md:2006
  2775. msgid "**TLDR**: new installations will now default to Traefik as their reverse-proxy. Existing users need to explicitly choose their reverse-proxy type. [Switching to Traefik](#how-do-i-switch-my-existing-setup-to-traefik) is strongly encouraged. `matrix-nginx-proxy` may break over time and will ultimately be removed."
  2776. msgstr ""
  2777. #: ../../../CHANGELOG.md:2008
  2778. msgid "As mentioned 2 weeks ago in [(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support](#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support), the playbook is moving to Traefik as its default SSL-terminating reverse-proxy."
  2779. msgstr ""
  2780. #: ../../../CHANGELOG.md:2010
  2781. msgid "Until now, we've been doing the migration gradually and keeping full backward compatibility. New installations were defaulting to `matrix-nginx-proxy` (just like before), while existing installations were allowed to remain on `matrix-nginx-proxy` as well. This makes things very difficult for us, because we need to maintain and think about lots of different setups:"
  2782. msgstr ""
  2783. #: ../../../CHANGELOG.md:2012
  2784. msgid "Traefik managed by the playbook"
  2785. msgstr ""
  2786. #: ../../../CHANGELOG.md:2013
  2787. msgid "Traefik managed by the user in another way"
  2788. msgstr ""
  2789. #: ../../../CHANGELOG.md:2014
  2790. msgid "another reverse-proxy on the same host (`127.0.0.1` port exposure)"
  2791. msgstr ""
  2792. #: ../../../CHANGELOG.md:2015
  2793. msgid "another reverse-proxy on another host (`0.0.0.0` port exposure)"
  2794. msgstr ""
  2795. #: ../../../CHANGELOG.md:2016
  2796. msgid "`matrix-nginx-proxy` — an `nginx` container managed by the playbook"
  2797. msgstr ""
  2798. #: ../../../CHANGELOG.md:2017
  2799. msgid "`nginx` webserver operated by the user, running without a container on the same server"
  2800. msgstr ""
  2801. #: ../../../CHANGELOG.md:2019
  2802. msgid "Each change we do and each new feature that comes in needs to support all these different ways of reverse-proxying. Because `matrix-nginx-proxy` was the default and pretty much everyone was (and still is) using it, means that new PRs also come with `matrix-nginx-proxy` as their main focus and Traefik as an afterthought, which means we need to spend hours fixing up Traefik support."
  2803. msgstr ""
  2804. #: ../../../CHANGELOG.md:2021
  2805. msgid "We can't spend all this time maintaining so many different configurations anymore. Traefik support has been an option for 2 weeks and lots of people have already migrated their server and have tested things out. Traefik is what we use and preferentially test for."
  2806. msgstr ""
  2807. #: ../../../CHANGELOG.md:2023
  2808. msgid "It's time for the **next step in our migration process** to Traefik and elimination of `matrix-nginx-proxy`:"
  2809. msgstr ""
  2810. #: ../../../CHANGELOG.md:2025
  2811. msgid "Traefik is now the default reverse-proxy for new installations"
  2812. msgstr ""
  2813. #: ../../../CHANGELOG.md:2026
  2814. msgid "All existing users need to explicitly choose their reverse-proxy type by defining the `matrix_playbook_reverse_proxy_type` variable in their `vars.yml` configuration file. We strongly encourage existing users to [switch the Traefik](#how-to-switch-an-existing-setup-to-traefik), as the nginx setup is bound to become more and more broken over time until it's ultimately removed"
  2815. msgstr ""
  2816. #: ../../../CHANGELOG.md:2028
  2817. msgid "How do I switch my existing setup to Traefik?"
  2818. msgstr ""
  2819. #: ../../../CHANGELOG.md:2030
  2820. msgid "**For users who are on `matrix-nginx-proxy`** (the default reverse-proxy provided by the playbook), switching to Traefik can happen with a simple configuration change. Follow this section from 2 weeks ago: [How do I explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-traefik-right-now)."
  2821. msgstr ""
  2822. #: ../../../CHANGELOG.md:2032
  2823. msgid "If you experience trouble:"
  2824. msgstr ""
  2825. #: ../../../CHANGELOG.md:2034
  2826. msgid "Follow [How do I remain on matrix-nginx-proxy?](#how-do-i-remain-on-matrix-nginx-proxy) to bring your server back online using the old reverse-proxy"
  2827. msgstr ""
  2828. #: ../../../CHANGELOG.md:2035
  2829. msgid "Ask for help in our [support channels](README.md#support)"
  2830. msgstr ""
  2831. #: ../../../CHANGELOG.md:2036
  2832. msgid "Try switching to Traefik again later"
  2833. msgstr ""
  2834. #: ../../../CHANGELOG.md:2038
  2835. msgid "**For users with a more special reverse-proxying setup** (another nginx server, Apache, Caddy, etc.), the migration may not be so smooth. Follow the [Using your own webserver](docs/configuring-playbook-own-webserver.md) guide. Ideally, your custom reverse-proxy will be configured in such a way that it **fronts the Traefik reverse-proxy** provided by the playbook. Other means of reverse-proxying are more fragile and may be deprecated in the future."
  2836. msgstr ""
  2837. #: ../../../CHANGELOG.md:2040
  2838. msgid "I already use my own Traefik server. How do I plug that in?"
  2839. msgstr ""
  2840. #: ../../../CHANGELOG.md:2042
  2841. msgid "See the [Traefik managed by the playbook](docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) section."
  2842. msgstr ""
  2843. #: ../../../CHANGELOG.md:2044
  2844. msgid "Why is matrix-nginx-proxy used even after switching to Traefik?"
  2845. msgstr ""
  2846. #: ../../../CHANGELOG.md:2046
  2847. msgid "This playbook manages many different services. All these services were initially integrated with `matrix-nginx-proxy`."
  2848. msgstr ""
  2849. #: ../../../CHANGELOG.md:2048
  2850. msgid "While we migrate all these components to have native Traefik support, some still go through nginx internally (Traefik -> local `matrix-nginx-proxy` -> component). As time goes on, internal reliance on `matrix-nginx-proxy` will gradually decrease until it's completely removed."
  2851. msgstr ""
  2852. #: ../../../CHANGELOG.md:2050
  2853. msgid "How do I remain on matrix-nginx-proxy?"
  2854. msgstr ""
  2855. #: ../../../CHANGELOG.md:2052
  2856. msgid "Most new work and testing targets Traefik, so remaining on nginx is **not** \"the good old stable\" option, but rather the \"still available, but largely untested and likely to be broken very soon\" option."
  2857. msgstr ""
  2858. #: ../../../CHANGELOG.md:2054
  2859. msgid "To proceed regardless of this warning, add `matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your configuration."
  2860. msgstr ""
  2861. #: ../../../CHANGELOG.md:2056
  2862. msgid "At some point in the **near** future (days, or even weeks at most), we hope to completely get rid of `matrix-nginx-proxy` (or break it enough to make it unusable), so you **will soon be forced to migrate** anyway. Plan your migration accordingly."
  2863. msgstr ""
  2864. #: ../../../CHANGELOG.md:2058
  2865. msgid "How do I keep using my own other reverse-proxy?"
  2866. msgstr ""
  2867. #: ../../../CHANGELOG.md:2060
  2868. msgid "We recommend that you follow the guide for [Fronting the integrated reverse-proxy webserver with another reverse-proxy](docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)."
  2869. msgstr ""
  2870. #: ../../../CHANGELOG.md:2063
  2871. msgid "2023-02-25"
  2872. msgstr ""
  2873. #: ../../../CHANGELOG.md:2065
  2874. msgid "rageshake support"
  2875. msgstr ""
  2876. #: ../../../CHANGELOG.md:2067
  2877. msgid "Thanks to [Benjamin Kampmann](https://github.com/gnunicorn), the playbook can now install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server."
  2878. msgstr ""
  2879. #: ../../../CHANGELOG.md:2069
  2880. msgid "Additional details are available in [Setting up rageshake](docs/configuring-playbook-rageshake.md)."
  2881. msgstr ""
  2882. #: ../../../CHANGELOG.md:2072
  2883. msgid "2023-02-17"
  2884. msgstr ""
  2885. #: ../../../CHANGELOG.md:2074
  2886. msgid "Synapse templates customization support"
  2887. msgstr ""
  2888. #: ../../../CHANGELOG.md:2076
  2889. msgid "The playbook can now help you customize Synapse's templates."
  2890. msgstr ""
  2891. #: ../../../CHANGELOG.md:2078
  2892. msgid "Additional details are available in the [Customizing templates](docs/configuring-playbook-synapse.md#customizing-templates) section of our Synapse documentation."
  2893. msgstr ""
  2894. #: ../../../CHANGELOG.md:2080
  2895. msgid "The matrix-redis role lives independently now"
  2896. msgstr ""
  2897. #: ../../../CHANGELOG.md:2082
  2898. msgid "**TLDR**: the `matrix-redis` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
  2899. msgstr ""
  2900. #: ../../../CHANGELOG.md:2084
  2901. msgid "The `matrix-redis` role (which configures [Redis](https://redis.io/)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-redis). This makes it possible to easily use it in other Ansible playbooks."
  2902. msgstr ""
  2903. #: ../../../CHANGELOG.md:2086
  2904. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Ntfy or not. If you're making use of Ntfy via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_redis_` -> `redis_`)."
  2905. msgstr ""
  2906. #: ../../../CHANGELOG.md:2088
  2907. msgid "The matrix-ntfy role lives independently now"
  2908. msgstr ""
  2909. #: ../../../CHANGELOG.md:2090
  2910. msgid "**TLDR**: the `matrix-ntfy` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
  2911. msgstr ""
  2912. #: ../../../CHANGELOG.md:2092
  2913. msgid "The `matrix-ntfy` role (which configures [Ntfy](https://ntfy.sh/)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy). This makes it possible to easily use it in other Ansible playbooks."
  2914. msgstr ""
  2915. #: ../../../CHANGELOG.md:2094
  2916. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Ntfy or not. If you're making use of Ntfy via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_ntfy_` -> `ntfy_`)."
  2917. msgstr ""
  2918. #: ../../../CHANGELOG.md:2097
  2919. msgid "2023-02-15"
  2920. msgstr ""
  2921. #: ../../../CHANGELOG.md:2099
  2922. msgid "The matrix-grafana role lives independently now"
  2923. msgstr ""
  2924. #: ../../../CHANGELOG.md:2101
  2925. msgid "**TLDR**: the `matrix-grafana` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
  2926. msgstr ""
  2927. #: ../../../CHANGELOG.md:2103
  2928. msgid "The `matrix-grafana` role (which configures [Grafana](docs/configuring-playbook-prometheus-grafana.md)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-grafana). This makes it possible to easily use it in other Ansible playbooks."
  2929. msgstr ""
  2930. #: ../../../CHANGELOG.md:2105
  2931. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Grafana or not. If you're making use of Grafana via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_grafana_` -> `grafana_`)."
  2932. msgstr ""
  2933. #: ../../../CHANGELOG.md:2108
  2934. msgid "2023-02-13"
  2935. msgstr ""
  2936. #: ../../../CHANGELOG.md:2110
  2937. msgid "The matrix-backup-borg role lives independently now"
  2938. msgstr ""
  2939. #: ../../../CHANGELOG.md:2112
  2940. msgid "**TLDR**: the `matrix-backup-borg` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
  2941. msgstr ""
  2942. #: ../../../CHANGELOG.md:2114
  2943. msgid "Thanks to [moan0s](https://github.com/moan0s), the `matrix-backup-borg` role (which configures [BorgBackup](docs/configuring-playbook-backup-borg.md)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). This makes it possible to easily use it in other Ansible playbooks and will become part of [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) soon."
  2944. msgstr ""
  2945. #: ../../../CHANGELOG.md:2116
  2946. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Borg's backup functionality or not. If you're making use of BorgBackup via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_backup_borg_` -> `backup_borg_`)."
  2947. msgstr ""
  2948. #: ../../../CHANGELOG.md:2119
  2949. msgid "2023-02-12"
  2950. msgstr ""
  2951. #: ../../../CHANGELOG.md:2121
  2952. msgid "(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support"
  2953. msgstr ""
  2954. #: ../../../CHANGELOG.md:2123
  2955. msgid "**TLDR**:"
  2956. msgstr ""
  2957. #: ../../../CHANGELOG.md:2125
  2958. msgid "there's a new `matrix_playbook_reverse_proxy_type` variable (see [roles/custom/matrix-base/defaults/main.yml](roles/custom/matrix-base/defaults/main.yml)), which lets you tell the playbook what reverse-proxy setup you'd like to have. This makes it easier for people who want to do reverse-proxying in other ways."
  2959. msgstr ""
  2960. #: ../../../CHANGELOG.md:2126
  2961. msgid "the default reverse-proxy (`matrix_playbook_reverse_proxy_type`) is still `playbook-managed-nginx` (via `matrix-nginx-proxy`), for now. **Existing `matrix-nginx-proxy` users should not observe any changes** and can stay on this for now."
  2962. msgstr ""
  2963. #: ../../../CHANGELOG.md:2127
  2964. msgid "**Users who use their [own other webserver](docs/configuring-playbook-own-webserver.md) (e.g. Apache, etc.) need to change** `matrix_playbook_reverse_proxy_type` to something like `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`"
  2965. msgstr ""
  2966. #: ../../../CHANGELOG.md:2128
  2967. msgid "we now have **optional [Traefik](https://traefik.io/) support**, so you could easily host Matrix and other Traefik-native services in containers on the same server. Traefik support is still experimental (albeit, good enough) and will improve over time. It does work, but certain esoteric features may not be there yet."
  2968. msgstr ""
  2969. #: ../../../CHANGELOG.md:2129
  2970. msgid "**Traefik will become the default reverse-proxy in the near future**. `matrix-nginx-proxy` will either remain as an option, or be completely removed to simplify the playbook"
  2971. msgstr ""
  2972. #: ../../../CHANGELOG.md:2131
  2973. msgid "Motivation for redoing our reverse-proxy setup"
  2974. msgstr ""
  2975. #: ../../../CHANGELOG.md:2133
  2976. msgid "The playbook has supported various reverse-proxy setups for a long time. We have various configuration variables (`matrix_nginx_proxy_enabled`, various `_host_bind_port` variables, etc.) which allow the playbook to adapt to these different setups. The whole situation was messy though — hard to figure out and with lots of variables to toggle to make things work as you'd expect — huge **operational complexity**."
  2977. msgstr ""
  2978. #: ../../../CHANGELOG.md:2135
  2979. msgid "We love containers, proven by the fact that **everything** that this playbook manages runs in a container. Yet, we weren't allowing people to easily host other web-exposed containers alongside Matrix services on the same server. We were using `matrix-nginx-proxy` (our integrated [nginx](https://nginx.org/) server), which was handling web-exposure and SSL termination for our own services, but we **weren't helping you with all your other containers**."
  2980. msgstr ""
  2981. #: ../../../CHANGELOG.md:2137
  2982. msgid "People who were **using `matrix-nginx-proxy`** were on the happy path on which everything worked well by default (Matrix-wise), **but** could not easily run other web-exposed services on their Matrix server because `matrix-nginx-proxy` was occupying ports `80` and `443`. Other services which wanted to get web exposure either had to be plugged into `matrix-nginx-proxy` (somewhat difficult) or people had to forgo using `matrix-nginx-proxy` in favor of something else."
  2983. msgstr ""
  2984. #: ../../../CHANGELOG.md:2139
  2985. msgid "Of those that decided to forgo `matrix-nginx-proxy`, many were **using nginx** on the same server without a container. This was likely some ancient nginx version, depending on your choice of distro. The Matrix playbook was trying to be helpful and even with `matrix_nginx_proxy_enabled: false` was still generating nginx configuration in `/matrix/nginx-proxy/conf.d`. Those configuration files were adapted for inclusion into an nginx server running locally. Disabling the `matrix-nginx-proxy` role like this, yet still having it produce files is a bit disgusting, but it's what we've had since the early beginnings of this playbook."
  2986. msgstr ""
  2987. #: ../../../CHANGELOG.md:2141
  2988. msgid "Others still, wanted to run Matrix locally (no SSL certificates), regardless of which web server technology this relied on, and then **reverse-proxy from another machine on the network** which was doing SSL termination. These people were:"
  2989. msgstr ""
  2990. #: ../../../CHANGELOG.md:2143
  2991. msgid "*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined with exposing services manually (setting `_bind_port` variables)"
  2992. msgstr ""
  2993. #: ../../../CHANGELOG.md:2144
  2994. msgid "*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in `http`-only mode (no SSL certificate retrieval)."
  2995. msgstr ""
  2996. #: ../../../CHANGELOG.md:2146
  2997. msgid "Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations."
  2998. msgstr ""
  2999. #: ../../../CHANGELOG.md:2148
  3000. msgid "When using `matrix-nginx-proxy` as is, we still had another problem — one of **internal playbook complexity**. Too many services need to be web-exposed (port 80/443, SSL certificates). Because of this, they all had to integrate with the `matrix-nginx-proxy` role. Tens of different roles explicitly integrating with `matrix-nginx-proxy` is not what we call clean. The `matrix-nginx-proxy` role contains variables for many of these roles (yikes). Other roles were more decoupled from it and were injecting configuration into `matrix-nginx-proxy` at runtime — see all the `inject_into_nginx_proxy.yml` task files in this playbook (more decoupled, but still… yikes)."
  3001. msgstr ""
  3002. #: ../../../CHANGELOG.md:2150
  3003. msgid "The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks:"
  3004. msgstr ""
  3005. #: ../../../CHANGELOG.md:2152
  3006. msgid "[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy) for hosting the [Vaultwarden](https://github.com/dani-garcia/vaultwarden) server — an alternative implementation of the [Bitwarden](https://bitwarden.com/) password manager"
  3007. msgstr ""
  3008. #: ../../../CHANGELOG.md:2153
  3009. msgid "[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) — for hosting the [Gitea](https://gitea.io/) git source code hosting service"
  3010. msgstr ""
  3011. #: ../../../CHANGELOG.md:2154
  3012. msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) — for hosting the [Nextcloud](https://nextcloud.com/) groupware platform"
  3013. msgstr ""
  3014. #: ../../../CHANGELOG.md:2156
  3015. msgid "We'd love for users to be able to **seamlessly use all these playbooks (and others, even) against a single server**. We don't want `matrix-nginx-proxy` to have a monopoly on port `80`/`443` and make it hard for other services to join in on the party. Such a thing forces people into running multiple servers (one for each service), which does provide nice security benefits, but is costly and ineffiecient. We'd like to make self-hosting these services cheap and easy."
  3016. msgstr ""
  3017. #: ../../../CHANGELOG.md:2158
  3018. msgid "These other playbooks have been using [Traefik](https://traefik.io/) as their default reverse-proxy for a long time. They can all coexist nicely together (as an example, see the [Interoperability](https://github.com/spantaleev/nextcloud-docker-ansible-deploy/blob/master/docs/configuring-playbook-interoperability.md) documentation for the [Nextcloud playbook](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)). Now that this playbook is gaining Traefik support, it will be able to interoperate with them. If you're going this way, make sure to have the Matrix playbook install Traefik and have the others use `*_reverse_proxy_type: other-traefik-container`."
  3019. msgstr ""
  3020. #: ../../../CHANGELOG.md:2160
  3021. msgid "Finally, at [etke.cc — a managed Matrix server hosting service](https://etke.cc) (built on top of this playbook, and coincidentally [turning 2 years old today](https://etke.cc/news/upsyw4ykbtgmwhz8k7ukldx0zbbfq-fh0iqi3llixi0/) 🎉), we're allowing people to host some additional services besides Matrix components. Exposing these services to the web requires ugly hacks and configuration files being dropped into `/matrix/nginx-proxy/conf.d`. We believe that everything should run in independent containers and be exposed to the web via a Traefik server, without a huge Ansible role like `matrix-nginx-proxy` that everything else needs to integrate with."
  3022. msgstr ""
  3023. #: ../../../CHANGELOG.md:2162
  3024. msgid "How do these changes fix all these problems?"
  3025. msgstr ""
  3026. #: ../../../CHANGELOG.md:2164
  3027. msgid "The new `matrix_playbook_reverse_proxy_type` lets you easily specify your preferred reverse-proxy type, including `other-on-same-host`, `other-on-another-host` and `none`, so people who'd like to reverse-proxy with their own web server have more options now."
  3028. msgstr ""
  3029. #: ../../../CHANGELOG.md:2166
  3030. msgid "Using Traefik greatly simplifies things, so going forward we'll have a simpler and easier to maintain playbook, which is also interoperable with other services."
  3031. msgstr ""
  3032. #: ../../../CHANGELOG.md:2168
  3033. msgid "Traefik is a web server, which has been specifically **designed for reverse-proxying to services running in containers**. It's ideal for usage in an Ansible playbook which runs everything in containers."
  3034. msgstr ""
  3035. #: ../../../CHANGELOG.md:2170
  3036. msgid "**Traefik obtains SSL certificates automatically**, so there's no need for plugging additional tools like [Certbot](https://certbot.eff.org/) into your web server (like we were doing in the `matrix-nginx-proxy` role). No more certificate renewal timers, web server reloading timers, etc. It's just simpler."
  3037. msgstr ""
  3038. #: ../../../CHANGELOG.md:2172
  3039. msgid "Traefik is a **modern web server**. [HTTP/3](https://doc.traefik.io/traefik/routing/entrypoints/#http3) is supported already (experimentally) and will move to stable soon, in the upcoming Traefik v3 release."
  3040. msgstr ""
  3041. #: ../../../CHANGELOG.md:2174
  3042. msgid "Traefik does not lock important functionality we'd like to use into [plus packages like nginx does](https://www.nginx.com/products/nginx/), leading us to resolve to configuration workarounds. The default Traefik package is good enough as it is."
  3043. msgstr ""
  3044. #: ../../../CHANGELOG.md:2176
  3045. msgid "Where we're at right now?"
  3046. msgstr ""
  3047. #: ../../../CHANGELOG.md:2178
  3048. msgid "`matrix_playbook_reverse_proxy_type` still defaults to a value of `playbook-managed-nginx`."
  3049. msgstr ""
  3050. #: ../../../CHANGELOG.md:2180
  3051. msgid "Unless we have some regression, **existing `matrix-nginx-proxy` users should be able to update their Matrix server and not observe any changes**. Their setup should still remain on nginx and everything should still work as expected."
  3052. msgstr ""
  3053. #: ../../../CHANGELOG.md:2182
  3054. msgid "**Users using [their own webservers](docs/configuring-playbook-own-webserver.md) will need to change `matrix_playbook_reverse_proxy_type`** to something like `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`. Previously, they could toggle `matrix_nginx_proxy_enabled` to `false`, and that made the playbook automatically expose services locally. Currently, we only do this if you change the reverse-proxy type to `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`."
  3055. msgstr ""
  3056. #: ../../../CHANGELOG.md:2184
  3057. msgid "How do I explicitly switch to Traefik right now?"
  3058. msgstr ""
  3059. #: ../../../CHANGELOG.md:2186
  3060. msgid "**Users who wish to migrate to Traefik** today, can do so by **adding** this to their configuration:"
  3061. msgstr ""
  3062. #: ../../../CHANGELOG.md:2192
  3063. msgid "You may still need to keep certain old `matrix_nginx_proxy_*` variables (like `matrix_nginx_proxy_base_domain_serving_enabled`), even when using Traefik. For now, we recommend keeping all `matrix_nginx_proxy_*` variables just in case. In the future, reliance on `matrix-nginx-proxy` will be removed."
  3064. msgstr ""
  3065. #: ../../../CHANGELOG.md:2194
  3066. msgid "Switching to Traefik will obtain new SSL certificates from Let's Encrypt (stored in `/matrix/traefik/ssl/acme.json`). **The switch is reversible**. You can always go back to `playbook-managed-nginx` if Traefik is causing you trouble."
  3067. msgstr ""
  3068. #: ../../../CHANGELOG.md:2196
  3069. msgid "**Note**: toggling `matrix_playbook_reverse_proxy_type` between Traefik and nginx will uninstall the Traefik role and all of its data (under `/matrix/traefik`), so you may run into a Let's Encrypt rate limit if you do it often."
  3070. msgstr ""
  3071. #: ../../../CHANGELOG.md:2198
  3072. msgid "Treafik directly reverse-proxies to **some** services right now, but for most other services it goes through `matrix-nginx-proxy` (e.g. Traefik -> `matrix-nginx-proxy` -> [Ntfy](docs/configuring-playbook-ntfy.md)). So, even if you opt into Traefik, you'll still see `matrix-nginx-proxy` being installed in local-only mode. This will improve with time."
  3073. msgstr ""
  3074. #: ../../../CHANGELOG.md:2200
  3075. msgid "Some services (like [coturn](docs/configuring-playbook-turn.md) and [Postmoogle](docs/configuring-playbook-bridge-postmoogle.md)) cannot be reverse-proxied to directly from Traefik, so they require direct access to SSL certificate files extracted out of Traefik. The playbook does this automatically thanks to a new [com.devture.ansible.role.traefik_certs_dumper](https://github.com/devture/com.devture.ansible.role.traefik_certs_dumper) role utilizing the [traefik-certs-dumper](https://github.com/ldez/traefik-certs-dumper) tool."
  3076. msgstr ""
  3077. #: ../../../CHANGELOG.md:2202
  3078. msgid "Our Traefik setup mostly works, but certain esoteric features may not work. If you have a default setup, we expect you to have a good experience."
  3079. msgstr ""
  3080. #: ../../../CHANGELOG.md:2204
  3081. msgid "Where we're going in the near future?"
  3082. msgstr ""
  3083. #: ../../../CHANGELOG.md:2206
  3084. msgid "The `matrix-nginx-proxy` role is quite messy. It manages both nginx and Certbot and its certificate renewal scripts and timers. It generates configuration even when the role is disabled (weird). Although it doesn't directly reach into variables from other roles, it has explicit awareness of various other services that it reverse-proxies to (`roles/custom/matrix-nginx-proxy/templates/nginx/conf.d/matrix-ntfy.conf.j2`, etc.). We'd like to clean this up. The only way is probably to just get rid of the whole thing at some point."
  3085. msgstr ""
  3086. #: ../../../CHANGELOG.md:2208
  3087. msgid "For now, `matrix-nginx-proxy` will stay around."
  3088. msgstr ""
  3089. #: ../../../CHANGELOG.md:2210
  3090. msgid "As mentioned above, Traefik still reverse-proxies to some (most) services by going through a local-only `matrix-nginx-proxy` server. This has allowed us to add Traefik support to the playbook early on (without having to rework all services), but is not the final goal. We'll **work on making each service support Traefik natively**, so that traffic will not need to go through `matrix-nginx-proxy` anymore. In the end, choosing Traefik should only give you a pure Traefik installation with no `matrix-nginx-proxy` in sight."
  3091. msgstr ""
  3092. #: ../../../CHANGELOG.md:2212
  3093. msgid "As Traefik support becomes complete and proves to be stable for a while, especially as a playbook default, we will **most likely remove `matrix-nginx-proxy` completely**. It will likely be some months before this happens though. Keeping support for both Traefik and nginx in the playbook will be a burden, especially with most of us running Traefik in the future. The Traefik role should do everything nginx does in a better and cleaner way. Users who use their own `nginx` server on the Matrix server will be inconvenienced, as nothing will generate ready-to-include nginx configuration for them. Still, we hope it won't be too hard to migrate their setup to another way of doing things, like:"
  3094. msgstr ""
  3095. #: ../../../CHANGELOG.md:2214
  3096. msgid "not using nginx anymore. A common reason for using nginx until now was that you were running other containers and you need your own nginx to reverse-proxy to all of them. Just switch them to Traefik as well."
  3097. msgstr ""
  3098. #: ../../../CHANGELOG.md:2215
  3099. msgid "running Traefik in local-only mode (`traefik_config_entrypoint_web_secure_enabled: false`) and using some nginx configuration which reverse-proxies to Traefik (we should introduce examples for this in `examples/nginx`)."
  3100. msgstr ""
  3101. #: ../../../CHANGELOG.md:2217
  3102. msgid "How do I help?"
  3103. msgstr ""
  3104. #: ../../../CHANGELOG.md:2219
  3105. msgid "You can help by:"
  3106. msgstr ""
  3107. #: ../../../CHANGELOG.md:2221
  3108. msgid "**explicitly switching your server to Traefik** right now (see example configuration in [How do I explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-traefik-right-now) above), testing, reporting troubles"
  3109. msgstr ""
  3110. #: ../../../CHANGELOG.md:2223
  3111. msgid "**adding native Traefik support to a role** (requires adding Traefik labels, etc.) — for inspiration, see these roles ([prometheus_node_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter), [prometheus_postgres_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter)) and how they're hooked into the playbook via [group_vars/matrix_servers](group_vars/matrix_servers)."
  3112. msgstr ""
  3113. #: ../../../CHANGELOG.md:2225
  3114. msgid "**adding reverse-proxying examples for nginx users** in `examples/nginx`. People who insist on using their own `nginx` server on the same Matrix host, can run Traefik in local-only mode (`traefik_config_entrypoint_web_secure_enabled: false`) and reverse-proxy to the Traefik server"
  3115. msgstr ""
  3116. #: ../../../CHANGELOG.md:2228
  3117. msgid "2023-02-10"
  3118. msgstr ""
  3119. #: ../../../CHANGELOG.md:2230
  3120. msgid "Matrix Authentication Support for Jitsi"
  3121. msgstr ""
  3122. #: ../../../CHANGELOG.md:2232
  3123. msgid "Thanks to [Jakob S.](https://github.com/jakicoll) ([zakk gGmbH](https://github.com/zakk-it)), Jitsi can now use Matrix for authentication (via [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service))."
  3124. msgstr ""
  3125. #: ../../../CHANGELOG.md:2234
  3126. msgid "Additional details are available in the [Authenticate using Matrix OpenID (Auth-Type 'matrix')](docs/configuring-playbook-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix)."
  3127. msgstr ""
  3128. #: ../../../CHANGELOG.md:2236
  3129. msgid "Draupnir moderation tool (bot) support"
  3130. msgstr ""
  3131. #: ../../../CHANGELOG.md:2238
  3132. msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (bot). Draupnir is a fork of [Mjolnir](docs/configuring-playbook-bot-mjolnir.md) (which the playbook has supported for a long time) maintained by Mjolnir's former lead developer."
  3133. msgstr ""
  3134. #: ../../../CHANGELOG.md:2240
  3135. msgid "Additional details are available in [Setting up Draupnir](docs/configuring-playbook-bot-draupnir.md)."
  3136. msgstr ""
  3137. #: ../../../CHANGELOG.md:2243
  3138. msgid "2023-02-05"
  3139. msgstr ""
  3140. #: ../../../CHANGELOG.md:2245
  3141. msgid "The matrix-prometheus-postgres-exporter role lives independently now"
  3142. msgstr ""
  3143. #: ../../../CHANGELOG.md:2247
  3144. msgid "**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
  3145. msgstr ""
  3146. #: ../../../CHANGELOG.md:2249
  3147. msgid "The `matrix-prometheus-postgres-exporter` role (which configures [Prometheus Postgres Exporter](https://github.com/prometheus-community/postgres_exporter)) has been extracted from the playbook and now lives in its own repository at https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter"
  3148. msgstr ""
  3149. #: ../../../CHANGELOG.md:2251
  3150. msgid "It's still part of the playbook, but is now installed via `ansible-galaxy` (by running `just roles` / `make roles`). Some variables have been renamed (`matrix_prometheus_postgres_exporter_` -> `prometheus_postgres_exporter_`, etc.). The playbook will report all variables that you need to rename to get upgraded. All functionality remains intact."
  3151. msgstr ""
  3152. #: ../../../CHANGELOG.md:2253
  3153. msgid "The `matrix-prometheus-services-proxy-connect` role has bee adjusted to help integrate the new `prometheus_postgres_exporter` role with our own services (`matrix-nginx-proxy`)"
  3154. msgstr ""
  3155. #: ../../../CHANGELOG.md:2255
  3156. #: ../../../CHANGELOG.md:2297
  3157. msgid "Other roles which aren't strictly related to Matrix are likely to follow this fate of moving to their own repositories. Extracting them out allows other Ansible playbooks to make use of these roles easily."
  3158. msgstr ""
  3159. #: ../../../CHANGELOG.md:2258
  3160. msgid "2023-01-26"
  3161. msgstr ""
  3162. #: ../../../CHANGELOG.md:2260
  3163. msgid "coturn can now use host-networking"
  3164. msgstr ""
  3165. #: ../../../CHANGELOG.md:2262
  3166. msgid "Large coturn deployments (with a huge range of ports specified via `coturn_turn_udp_min_port` and `coturn_turn_udp_max_port`) experience a huge slowdown with how Docker publishes all these ports (setting up firewall forwarding rules), which leads to a very slow coturn service startup and shutdown."
  3167. msgstr ""
  3168. #: ../../../CHANGELOG.md:2264
  3169. msgid "Such deployments don't need to run coturn within a private container network anymore. coturn can now run with host-networking by using configuration like this:"
  3170. msgstr ""
  3171. #: ../../../CHANGELOG.md:2270
  3172. msgid "With such a configuration, **Docker no longer needs to configure thousands of firewall forwarding rules** each time coturn starts and stops. This, however, means that **you will need to ensure these ports are open** in your firewall yourself."
  3173. msgstr ""
  3174. #: ../../../CHANGELOG.md:2272
  3175. msgid "Thanks to us [tightening coturn security](#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues), running coturn with host-networking should be safe and not expose neither other services running on the host, nor other services running on the local network."
  3176. msgstr ""
  3177. #: ../../../CHANGELOG.md:2274
  3178. msgid "(Backward Compatibility) Tightening coturn security can lead to connectivity issues"
  3179. msgstr ""
  3180. #: ../../../CHANGELOG.md:2276
  3181. msgid "**TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default coturn blocklists. They may need to override `coturn_denied_peer_ips` and remove some IP ranges from it."
  3182. msgstr ""
  3183. #: ../../../CHANGELOG.md:2278
  3184. msgid "Inspired by [this security article](https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-access-control-protection/), we've decided to make use of coturn's `denied-peer-ip` functionality to prevent relaying network traffic to certain private IP subnets. This ensures that your coturn server won't accidentally try to forward traffic to certain services running on your local networks. We run coturn in a container and in a private container network by default, which should prevent such access anyway, but having additional block layers in place is better."
  3185. msgstr ""
  3186. #: ../../../CHANGELOG.md:2280
  3187. msgid "If you access your Matrix server from a local network and need coturn to relay to private IP addresses, you may observe that relaying is now blocked due to our new default `denied-peer-ip` lists (specified in `coturn_denied_peer_ips`). If you experience such connectivity problems, consider overriding this setting in your `vars.yml` file and removing certain networks from it."
  3188. msgstr ""
  3189. #: ../../../CHANGELOG.md:2282
  3190. msgid "We've also added `no-multicast-peers` to the default coturn configuration, but we don't expect this to cause trouble for most people."
  3191. msgstr ""
  3192. #: ../../../CHANGELOG.md:2285
  3193. msgid "2023-01-21"
  3194. msgstr ""
  3195. #: ../../../CHANGELOG.md:2287
  3196. msgid "The matrix-prometheus-node-exporter role lives independently now"
  3197. msgstr ""
  3198. #: ../../../CHANGELOG.md:2289
  3199. msgid "**TLDR**: the `matrix-prometheus-node-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
  3200. msgstr ""
  3201. #: ../../../CHANGELOG.md:2291
  3202. msgid "The `matrix-prometheus-node-exporter` role (which configures [Prometheus node exporter](https://github.com/prometheus/node_exporter)) has been extracted from the playbook and now lives in its own repository at https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter"
  3203. msgstr ""
  3204. #: ../../../CHANGELOG.md:2293
  3205. msgid "It's still part of the playbook, but is now installed via `ansible-galaxy` (by running `just roles` / `make roles`). Some variables have been renamed (`matrix_prometheus_node_exporter_` -> `prometheus_node_exporter_`, etc.). The playbook will report all variables that you need to rename to get upgraded. All functionality remains intact."
  3206. msgstr ""
  3207. #: ../../../CHANGELOG.md:2295
  3208. msgid "A new `matrix-prometheus-services-proxy-connect` role was added to the playbook to help integrate the new `prometheus_node_exporter` role with our own services (`matrix-nginx-proxy`)"
  3209. msgstr ""
  3210. #: ../../../CHANGELOG.md:2300
  3211. msgid "2023-01-13"
  3212. msgstr ""
  3213. #: ../../../CHANGELOG.md:2302
  3214. msgid "Support for running commands via just"
  3215. msgstr ""
  3216. #: ../../../CHANGELOG.md:2304
  3217. msgid "We've previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers `ansible-galaxy`, see [Makefile](Makefile)). Our `Makefile` is still around and you can still run these commands."
  3218. msgstr ""
  3219. #: ../../../CHANGELOG.md:2306
  3220. msgid "In addition, we've added support for running commands via [just](https://github.com/casey/just) — a more modern command-runner alternative to `make`. Instead of `make roles`, you can now run `just roles` to accomplish the same."
  3221. msgstr ""
  3222. #: ../../../CHANGELOG.md:2308
  3223. msgid "Our [justfile](justfile) already defines some additional helpful **shortcut** commands that weren't part of our `Makefile`. Here are some examples:"
  3224. msgstr ""
  3225. #: ../../../CHANGELOG.md:2310
  3226. msgid "`just install-all` to trigger the much longer `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start` command"
  3227. msgstr ""
  3228. #: ../../../CHANGELOG.md:2311
  3229. msgid "`just install-all --ask-vault-pass` — commands also support additional arguments (`--ask-vault-pass` will be appended to the above installation command)"
  3230. msgstr ""
  3231. #: ../../../CHANGELOG.md:2312
  3232. msgid "`just run-tags install-mautrix-slack,start` — to run specific playbook tags"
  3233. msgstr ""
  3234. #: ../../../CHANGELOG.md:2313
  3235. msgid "`just start-all` — (re-)starts all services"
  3236. msgstr ""
  3237. #: ../../../CHANGELOG.md:2314
  3238. msgid "`just stop-group postgres` — to stop only the Postgres service"
  3239. msgstr ""
  3240. #: ../../../CHANGELOG.md:2315
  3241. msgid "`just register-user alice secret-password yes` — registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)"
  3242. msgstr ""
  3243. #: ../../../CHANGELOG.md:2317
  3244. msgid "Additional helpful commands and shortcuts may be defined in the future."
  3245. msgstr ""
  3246. #: ../../../CHANGELOG.md:2319
  3247. msgid "This is all completely optional. If you find it difficult to [install `just`](https://github.com/casey/just#installation) or don't find any of this convenient, feel free to run all commands manually."
  3248. msgstr ""
  3249. #: ../../../CHANGELOG.md:2322
  3250. msgid "2023-01-11"
  3251. msgstr ""
  3252. #: ../../../CHANGELOG.md:2324
  3253. msgid "mautrix-slack support"
  3254. msgstr ""
  3255. #: ../../../CHANGELOG.md:2326
  3256. msgid "Thanks to [Cody Neiman](https://github.com/xangelix)'s efforts, the playbook now supports bridging to [Slack](https://slack.com/) via the [mautrix-slack](https://mau.dev/mautrix/slack) bridge. See our [Setting up Mautrix Slack bridging](docs/configuring-playbook-bridge-mautrix-slack.md) documentation page for getting started."
  3257. msgstr ""
  3258. #: ../../../CHANGELOG.md:2328
  3259. msgid "**Note**: this is a new Slack bridge. The playbook still retains Slack bridging via [matrix-appservice-slack](docs/configuring-playbook-bridge-appservice-slack.md) and [mx-puppet-slack](docs/configuring-playbook-bridge-mx-puppet-slack.md). You're free to use the bridge that serves you better, or even all three of them (for different users and use-cases)."
  3260. msgstr ""
  3261. #: ../../../CHANGELOG.md:2331
  3262. msgid "2023-01-10"
  3263. msgstr ""
  3264. #: ../../../CHANGELOG.md:2333
  3265. msgid "ChatGPT support"
  3266. msgstr ""
  3267. #: ../../../CHANGELOG.md:2335
  3268. msgid "Thanks to [@bertybuttface](https://github.com/bertybuttface), the playbook can now help you set up [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) — a bot through which you can talk to the [ChatGPT](https://openai.com/blog/chatgpt/) model."
  3269. msgstr ""
  3270. #: ../../../CHANGELOG.md:2337
  3271. msgid "See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-chatgpt.md) documentation to get started."
  3272. msgstr ""
  3273. #: ../../../CHANGELOG.md:2340
  3274. msgid "2022-11-30"
  3275. msgstr ""
  3276. #: ../../../CHANGELOG.md:2342
  3277. msgid "matrix-postgres-backup has been replaced by the ansible-role-postgres-backup external role"
  3278. msgstr ""
  3279. #: ../../../CHANGELOG.md:2344
  3280. msgid "Just like we've [replaced Postgres with an external role](#matrix-postgres-has-been-replaced-by-the-comdevtureansiblerolepostgres-external-role) on 2022-11-28, we're now replacing `matrix-postgres-backup` with an external role — [com.devture.ansible.role.postgres_backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres_backup)."
  3281. msgstr ""
  3282. #: ../../../CHANGELOG.md:2346
  3283. msgid "You'll need to rename your `matrix_postgres_backup`-prefixed variables such that they use a `postgres_backup` prefix."
  3284. msgstr ""
  3285. #: ../../../CHANGELOG.md:2349
  3286. msgid "2022-11-28"
  3287. msgstr ""
  3288. #: ../../../CHANGELOG.md:2351
  3289. msgid "matrix-postgres has been replaced by the ansible-role-postgres external role"
  3290. msgstr ""
  3291. #: ../../../CHANGELOG.md:2353
  3292. msgid "**TLDR**: the tasks that install the integrated Postgres server now live in an external role — [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres). You'll need to run `make roles` to install it, and to also rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix (e.g. `matrix_postgres_connection_password` -> `postgres_connection_password`). All your data will still be there! Some scripts have moved (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`)."
  3293. msgstr ""
  3294. #: ../../../CHANGELOG.md:2355
  3295. msgid "The `matrix-postgres` role that has been part of the playbook for a long time has been replaced with the [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) role. This was done as part of our work to [use external roles for some things](#the-playbook-now-uses-external-roles-for-some-things) for better code re-use and maintainability."
  3296. msgstr ""
  3297. #: ../../../CHANGELOG.md:2357
  3298. msgid "The new role is an upgraded version of the old `matrix-postgres` role with these notable differences:"
  3299. msgstr ""
  3300. #: ../../../CHANGELOG.md:2359
  3301. msgid "it uses different names for its variables (`matrix_postgres` -> `devture_postgres`)"
  3302. msgstr ""
  3303. #: ../../../CHANGELOG.md:2360
  3304. msgid "when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-postgresql), it will vacuum all your databases, not just the Synapse one"
  3305. msgstr ""
  3306. #: ../../../CHANGELOG.md:2362
  3307. msgid "You'll need to run `make roles` to install the new role. You would also need to rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix."
  3308. msgstr ""
  3309. #: ../../../CHANGELOG.md:2364
  3310. msgid "Note: the systemd service still remains the same — `matrix-postgres.service`. Your data will still be in `/matrix/postgres`, etc. Postgres-related scripts will be moved to `/matrix/postgres/bin` (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`, etc). Also see [The playbook no longer installs scripts in /usr/local/bin](#the-playbook-no-longer-installs-scripts-in-usrlocalbin)."
  3311. msgstr ""
  3312. #: ../../../CHANGELOG.md:2366
  3313. msgid "The playbook no longer installs scripts to /usr/local/bin"
  3314. msgstr ""
  3315. #: ../../../CHANGELOG.md:2368
  3316. msgid "The locations of various scripts installed by the playbook have changed."
  3317. msgstr ""
  3318. #: ../../../CHANGELOG.md:2370
  3319. msgid "The playbook no longer contaminates your `/usr/local/bin` directory. All scripts installed by the playbook now live in `bin/` directories under `/matrix`. Some examples are below:"
  3320. msgstr ""
  3321. #: ../../../CHANGELOG.md:2372
  3322. msgid "`/usr/local/bin/matrix-remove-all` -> `/matrix/bin/remove-all`"
  3323. msgstr ""
  3324. #: ../../../CHANGELOG.md:2373
  3325. msgid "`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`"
  3326. msgstr ""
  3327. #: ../../../CHANGELOG.md:2374
  3328. msgid "`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> `/matrix/ssl/bin/lets-encrypt-certificates-renew`"
  3329. msgstr ""
  3330. #: ../../../CHANGELOG.md:2375
  3331. msgid "`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin/register-user`"
  3332. msgstr ""
  3333. #: ../../../CHANGELOG.md:2378
  3334. msgid "2022-11-25"
  3335. msgstr ""
  3336. #: ../../../CHANGELOG.md:2380
  3337. msgid "2x-5x performance improvements in playbook runtime"
  3338. msgstr ""
  3339. #: ../../../CHANGELOG.md:2382
  3340. msgid "**TLDR**: the playbook is 2x faster for running `--tags=setup-all` (and various other tags). It also has new `--tags=install-*` tags (like `--tags=install-all`), which skip uninstallation tasks and bring an additional 2.5x speedup. In total, the playbook can maintain your server 5 times faster."
  3341. msgstr ""
  3342. #: ../../../CHANGELOG.md:2384
  3343. msgid "Our [etke.cc managed Matrix hosting service](https://etke.cc) runs maintenance against hundreds of servers, so the playbook being fast means a lot. The [etke.cc Ansible playbook](https://github.com/etkecc/ansible) (which is an extension of this one) is growing to support more and more services (besides just Matrix), so the Matrix playbook being leaner prevents runtimes from becoming too slow and improves the customer experience."
  3344. msgstr ""
  3345. #: ../../../CHANGELOG.md:2386
  3346. msgid "Even when running `ansible-playbook` manually (as most of us here do), it's beneficial not to waste time and CPU resources."
  3347. msgstr ""
  3348. #: ../../../CHANGELOG.md:2388
  3349. msgid "Recently, a few large optimizations have been done to this playbook and its external roles (see [The playbook now uses external roles for some things](#the-playbook-now-uses-external-roles-for-some-things) and don't forget to run `make roles`):"
  3350. msgstr ""
  3351. #: ../../../CHANGELOG.md:2390
  3352. msgid "Replacing Ansible `import_tasks` calls with `include_tasks`, which decreased runtime in half. Using `import_tasks` is slower and causes Ansible to go through and skip way too many tasks (tasks which could have been skipped altogether by not having Ansible include them in the first place). On an experimental VM, **deployment time was decreased from ~530 seconds to ~250 seconds**."
  3353. msgstr ""
  3354. #: ../../../CHANGELOG.md:2392
  3355. msgid "Introducing new `install-*` tags (`install-all` and `install-COMPONENT`, e.g. `install-synapse`, `install-bot-mjolnir`), which only run Ansible tasks pertaining to installation, while skipping uninstallation tasks. In most cases, people are maintaining the same setup or they're *adding* new components. Removing components is rare. Running thousands of uninstallation tasks each time is wasteful. On an experimental VM, **deployment time was decreased from ~250 seconds (`--tags=setup-all`) to ~100 seconds (`--tags=install-all`)**."
  3356. msgstr ""
  3357. #: ../../../CHANGELOG.md:2394
  3358. msgid "You can still use `--tags=setup-all`. In fact, that's the best way to ensure your server is reconciled with the `vars.yml` configuration."
  3359. msgstr ""
  3360. #: ../../../CHANGELOG.md:2396
  3361. msgid "If you know you haven't uninstalled any services since the last time you ran the playbook, you could run `--tags=install-all` instead and benefit from quicker runtimes. It should be noted that a service may become \"eligible for uninstallation\" even if your `vars.yml` file remains the same. In rare cases, we toggle services from being auto-installed to being optional, like we did on the 17th of March 2022 when we made [ma1sd not get installed by default](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/CHANGELOG.md#compatibility-break-ma1sd-identity-server-no-longer-installed-by-default). In such rare cases, you'd also need to run `--tags=setup-all`."
  3362. msgstr ""
  3363. #: ../../../CHANGELOG.md:2399
  3364. msgid "2022-11-22"
  3365. msgstr ""
  3366. #: ../../../CHANGELOG.md:2401
  3367. msgid "Automatic `matrix_architecture` determination"
  3368. msgstr ""
  3369. #: ../../../CHANGELOG.md:2403
  3370. msgid "From now on, the playbook automatically determines your server's architecture and sets the `matrix_architecture` variable accordingly. You no longer need to set this variable manually in your `vars.yml` file."
  3371. msgstr ""
  3372. #: ../../../CHANGELOG.md:2405
  3373. msgid "Docker and the Docker SDK for Python are now installed via external roles"
  3374. msgstr ""
  3375. #: ../../../CHANGELOG.md:2409
  3376. msgid "Docker will now be installed on the server via the [geerlingguy.docker](https://github.com/geerlingguy/ansible-role-docker) Ansible role. If you'd like to manage the Docker installation yourself, you can disable the playbook's installation of Docker by setting `matrix_playbook_docker_installation_enabled: false`."
  3377. msgstr ""
  3378. #: ../../../CHANGELOG.md:2411
  3379. msgid "The Docker SDK for Python (named `docker-python`, `python-docker`, etc. on the different platforms) is now also installed by another role ([com.devture.ansible.role.docker_sdk_for_python](https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python)). To disable this role and install the necessary tools yourself, use `devture_docker_sdk_for_python_installation_enabled: false`."
  3380. msgstr ""
  3381. #: ../../../CHANGELOG.md:2413
  3382. msgid "If you're hitting issues with Docker installation or Docker SDK for Python installation, consider reporting bugs or contributing to these other projects."
  3383. msgstr ""
  3384. #: ../../../CHANGELOG.md:2415
  3385. msgid "These additional roles are downloaded into the playbook directory (to `roles/galaxy`) via an `ansible-galaxy …` command. `make roles` is an easy shortcut for invoking the `ansible-galaxy` command to download these roles."
  3386. msgstr ""
  3387. #: ../../../CHANGELOG.md:2418
  3388. msgid "2022-11-20"
  3389. msgstr ""
  3390. #: ../../../CHANGELOG.md:2420
  3391. msgid "(Backward Compatibility Break) Changing how reverse-proxying to Synapse works — now via a `matrix-synapse-reverse-proxy-companion` service"
  3392. msgstr ""
  3393. #: ../../../CHANGELOG.md:2422
  3394. msgid "**TLDR**: There's now a `matrix-synapse-reverse-proxy-companion` nginx service, which helps with reverse-proxying to Synapse and its various worker processes (if workers are enabled), so that `matrix-nginx-proxy` can be relieved of this role. `matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. `matrix-synapse-reverse-proxy-companion` is just one more reverse-proxy thrown into the mix for convenience. People with a more custom reverse-proxying configuration may be affected — see [Webserver configuration](#webserver-configuration) below."
  3395. msgstr ""
  3396. #: ../../../CHANGELOG.md:2424
  3397. msgid "Background"
  3398. msgstr ""
  3399. #: ../../../CHANGELOG.md:2426
  3400. msgid "Previously, `matrix-nginx-proxy` forwarded requests to Synapse directly. When Synapse is running in worker mode, the reverse-proxying configuration is more complicated (different requests need to go to different Synapse worker processes). `matrix-nginx-proxy` had configuration for sending each URL endpoint to the correct Synapse worker responsible for handling it. However, sometimes people like to disable `matrix-nginx-proxy` (for whatever reason) as detailed in [Using your own webserver, instead of this playbook's nginx proxy](docs/configuring-playbook-own-webserver.md)."
  3401. msgstr ""
  3402. #: ../../../CHANGELOG.md:2428
  3403. msgid "Because `matrix-nginx-proxy` was so central to request forwarding, when it was disabled and Synapse was running with workers enabled, there was nothing which could forward requests to the correct place anymore… which caused [problems such as this one affecting Dimension](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2090)."
  3404. msgstr ""
  3405. #: ../../../CHANGELOG.md:2430
  3406. msgid "Solution"
  3407. msgstr ""
  3408. #: ../../../CHANGELOG.md:2432
  3409. msgid "From now on, `matrix-nginx-proxy` is relieved of its function of reverse-proxying to Synapse and its various worker processes. This role is now handled by the new `matrix-synapse-reverse-proxy-companion` nginx service and works even if `matrix-nginx-proxy` is disabled. The purpose of the new `matrix-synapse-reverse-proxy-companion` service is to:"
  3410. msgstr ""
  3411. #: ../../../CHANGELOG.md:2434
  3412. msgid "serve as a companion to Synapse and know how to reverse-proxy to Synapse correctly (no matter if workers are enabled or not)"
  3413. msgstr ""
  3414. #: ../../../CHANGELOG.md:2436
  3415. msgid "provide a unified container address for reaching Synapse (no matter if workers are enabled or not)"
  3416. msgstr ""
  3417. #: ../../../CHANGELOG.md:2437
  3418. msgid "`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server API traffic"
  3419. msgstr ""
  3420. #: ../../../CHANGELOG.md:2438
  3421. msgid "`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server (Federation) API traffic"
  3422. msgstr ""
  3423. #: ../../../CHANGELOG.md:2440
  3424. msgid "simplify `matrix-nginx-proxy` configuration — it now only needs to send requests to `matrix-synapse-reverse-proxy-companion` or `matrix-dendrite`, etc., without having to worry about workers"
  3425. msgstr ""
  3426. #: ../../../CHANGELOG.md:2442
  3427. msgid "allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is disabled"
  3428. msgstr ""
  3429. #: ../../../CHANGELOG.md:2444
  3430. msgid "`matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. All traffic goes through it before reaching any of the services. It's just that now the Synapse traffic is routed through `matrix-synapse-reverse-proxy-companion` like this:"
  3431. msgstr ""
  3432. #: ../../../CHANGELOG.md:2446
  3433. msgid "(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> (`matrix-synapse` or some Synapse worker))."
  3434. msgstr ""
  3435. #: ../../../CHANGELOG.md:2448
  3436. msgid "Various services (like Dimension, etc.) still talk to Synapse via `matrix-nginx-proxy` (e.g. `http://matrix-nginx-proxy:12080`) preferentially. They only talk to Synapse via the reverse-proxy companion (e.g. `http://matrix-synapse-reverse-proxy-companion:8008`) if `matrix-nginx-proxy` is disabled. Services should not be talking to Synapse (e.g. `https://matrix-synapse:8008` directly anymore), because when workers are enabled, that's the Synapse `master` process and may not be serving all URL endpoints needed by the service."
  3437. msgstr ""
  3438. #: ../../../CHANGELOG.md:2450
  3439. msgid "Webserver configuration"
  3440. msgstr ""
  3441. #: ../../../CHANGELOG.md:2452
  3442. msgid "if you're using `matrix-nginx-proxy` (`matrix_nginx_proxy_enabled: true`, which is the default for the playbook), you don't need to do anything"
  3443. msgstr ""
  3444. #: ../../../CHANGELOG.md:2454
  3445. msgid "if you're using your own `nginx` webserver running on the server, you shouldn't be affected. The `/matrix/nginx/conf.d` configuration and exposed ports that you're relying on will automatically be updated in a way that should work"
  3446. msgstr ""
  3447. #: ../../../CHANGELOG.md:2456
  3448. msgid "if you're using another local webserver (e.g. Apache, etc.) and haven't changed any ports (`matrix_*_host_bind_port` definitions), you shouldn't be affected. You're likely sending Matrix traffic to `127.0.0.1:8008` and `127.0.0.1:8048`. These ports (`8008` and `8048`) will still be exposed on `127.0.0.1` by default — just not by the `matrix-synapse` container from now on, but by the `matrix-synapse-reverse-proxy-companion` container instead"
  3449. msgstr ""
  3450. #: ../../../CHANGELOG.md:2458
  3451. msgid "if you've been exposing `matrix-synapse` ports (`matrix_synapse_container_client_api_host_bind_port`, etc.) manually, you should consider exposing `matrix-synapse-reverse-proxy-companion` ports instead"
  3452. msgstr ""
  3453. #: ../../../CHANGELOG.md:2460
  3454. msgid "if you're running Traefik and reverse-proxying directly to the `matrix-synapse` container, you should start reverse-proxying to the `matrix-synapse-reverse-proxy-companion` container instead. See [our updated Traefik example configuration](docs/configuring-playbook-own-webserver.md#sample-configuration-for-running-behind-traefik-20). Note: we now recommend calling the federation entry point `federation` (instead of `synapse`) and reverse-proxying the federation traffic via `matrix-nginx-proxy`, instead of sending it directly to Synapse (or `matrix-synapse-reverse-proxy-companion`). This makes the configuration simpler."
  3455. msgstr ""
  3456. #: ../../../CHANGELOG.md:2463
  3457. msgid "2022-11-05"
  3458. msgstr ""
  3459. #: ../../../CHANGELOG.md:2465
  3460. msgid "(Backward Compatibility Break) A new default standalone mode for Etherpad"
  3461. msgstr ""
  3462. #: ../../../CHANGELOG.md:2467
  3463. msgid "Until now, [Etherpad](https://etherpad.org/) (which [the playbook could install for you](docs/configuring-playbook-etherpad.md)) required the [Dimension integration manager](docs/configuring-playbook-dimension.md) to also be installed, because Etherpad was hosted on the Dimension domain (at `dimension.example.com/etherpad`)."
  3464. msgstr ""
  3465. #: ../../../CHANGELOG.md:2469
  3466. msgid "From now on, Etherpad can be installed in `standalone` mode on `etherpad.example.com` and used even without Dimension. This is much more versatile, so the playbook now defaults to this new mode (`etherpad_mode: standalone`)."
  3467. msgstr ""
  3468. #: ../../../CHANGELOG.md:2471
  3469. msgid "If you've already got both Etherpad and Dimension in use you could:"
  3470. msgstr ""
  3471. #: ../../../CHANGELOG.md:2473
  3472. msgid "**either** keep hosting Etherpad under the Dimension domain by adding `etherpad_mode: dimension` to your `vars.yml` file. All your existing room widgets will continue working at the same URLs and no other changes will be necessary."
  3473. msgstr ""
  3474. #: ../../../CHANGELOG.md:2475
  3475. msgid "**or**, you could change to hosting Etherpad separately on `etherpad.example.com`. You will need to [configure a DNS record](docs/configuring-dns.md) for this new domain. You will also need to reconfigure Dimension to use the new pad URLs (`https://etherpad.example.com/…`) going forward (refer to our [configuring Etherpad documentation](docs/configuring-playbook-etherpad.md)). All your existing room widgets (which still use `https://dimension.example.com/etherpad/…`) will break as Etherpad is not hosted there anymore. You will need to re-add them or to consider not using `standalone` mode"
  3476. msgstr ""
  3477. #: ../../../CHANGELOG.md:2478
  3478. msgid "2022-11-04"
  3479. msgstr ""
  3480. #: ../../../CHANGELOG.md:2480
  3481. msgid "The playbook now uses external roles for some things"
  3482. msgstr ""
  3483. #: ../../../CHANGELOG.md:2482
  3484. msgid "**TLDR**: when updating the playbook and before running it, you'll need to run `make roles` to make [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) download dependency roles (see the [`requirements.yml` file](requirements.yml)) to the `roles/galaxy` directory. Without this, the playbook won't work."
  3485. msgstr ""
  3486. #: ../../../CHANGELOG.md:2484
  3487. msgid "We're in the process of trimming the playbook and making it reuse Ansible roles."
  3488. msgstr ""
  3489. #: ../../../CHANGELOG.md:2486
  3490. msgid "Starting now, the playbook is composed of 2 types of Ansible roles:"
  3491. msgstr ""
  3492. #: ../../../CHANGELOG.md:2488
  3493. msgid "those that live within the playbook itself (`roles/custom/*`)"
  3494. msgstr ""
  3495. #: ../../../CHANGELOG.md:2490
  3496. msgid "those downloaded from other sources (using [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) to `roles/galaxy`, based on the [`requirements.yml` file](requirements.yml)). These roles are maintained by us or by other people from the Ansible community."
  3497. msgstr ""
  3498. #: ../../../CHANGELOG.md:2492
  3499. msgid "We're doing this for greater code-reuse (across Ansible playbooks, including our own related playbooks [gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) and [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)) and decreased maintenance burden. Until now, certain features were copy-pasted across playbooks or were maintained separately in each one, with improvements often falling behind. We've also tended to do too much by ourselves — installing Docker on the server from our `matrix-base` role, etc. — something that we'd rather not do anymore by switching to the [geerlingguy.docker](https://galaxy.ansible.com/geerlingguy/docker) role."
  3500. msgstr ""
  3501. #: ../../../CHANGELOG.md:2494
  3502. msgid "Some variable names will change during the transition to having more and more external (galaxy) roles. There's a new `custom/matrix_playbook_migration` role added to the playbook which will tell you about these changes each time you run the playbook."
  3503. msgstr ""
  3504. #: ../../../CHANGELOG.md:2496
  3505. msgid "**From now on**, every time you update the playbook (well, every time the `requirements.yml` file changes), it's best to run `make roles` to update the roles downloaded from other sources. `make roles` is a shortcut (a `roles` target defined in [`Makefile`](Makefile) and executed by the [`make`](https://www.gnu.org/software/make/) utility) which ultimately runs [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) to download Ansible roles. If you don't have `make`, you can also manually run the commands seen in the `Makefile`."
  3506. msgstr ""
  3507. #: ../../../CHANGELOG.md:2499
  3508. msgid "2022-10-14"
  3509. msgstr ""
  3510. #: ../../../CHANGELOG.md:2501
  3511. msgid "synapse-s3-storage-provider support"
  3512. msgstr ""
  3513. #: ../../../CHANGELOG.md:2503
  3514. msgid "**`synapse-s3-storage-provider` support is very new and still relatively untested. Using it may cause data loss.**"
  3515. msgstr ""
  3516. #: ../../../CHANGELOG.md:2505
  3517. msgid "You can now store your Synapse media repository files on Amazon S3 (or another S3-compatible object store) using [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) — a media provider for Synapse (Python module), which should work faster and more reliably than our previous [Goofys](docs/configuring-playbook-s3-goofys.md) implementation (Goofys will continue to work)."
  3518. msgstr ""
  3519. #: ../../../CHANGELOG.md:2507
  3520. msgid "This is not just for initial installations. Users with existing files (stored in the local filesystem) can also migrate their files to `synapse-s3-storage-provider`."
  3521. msgstr ""
  3522. #: ../../../CHANGELOG.md:2509
  3523. msgid "To get started, see our [Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3-storage-provider.md) documentation."
  3524. msgstr ""
  3525. #: ../../../CHANGELOG.md:2511
  3526. msgid "Synapse container image customization support"
  3527. msgstr ""
  3528. #: ../../../CHANGELOG.md:2513
  3529. msgid "We now support customizing the Synapse container image by adding additional build steps to its [`Dockerfile`](https://docs.docker.com/engine/reference/builder/)."
  3530. msgstr ""
  3531. #: ../../../CHANGELOG.md:2515
  3532. msgid "Our [synapse-s3-storage-provider support](#synapse-s3-storage-provider-support) is actually built on this. When `s3-storage-provider` is enabled, we automatically add additional build steps to install its Python module into the Synapse image."
  3533. msgstr ""
  3534. #: ../../../CHANGELOG.md:2517
  3535. msgid "Besides this kind of auto-added build steps (for components supported by the playbook), we also let you inject your own custom build steps using configuration like this:"
  3536. msgstr ""
  3537. #: ../../../CHANGELOG.md:2528
  3538. msgid "People who have needed to customize Synapse previously had to fork the git repository, make their changes to the `Dockerfile` there, point the playbook to the new repository (`matrix_synapse_container_image_self_build_repo`) and enable self-building from scratch (`matrix_synapse_container_image_self_build: true`). This is harder and slower."
  3539. msgstr ""
  3540. #: ../../../CHANGELOG.md:2530
  3541. msgid "With the new Synapse-customization feature in the playbook, we use the original upstream (pre-built, if available) Synapse image and only build on top of it, right on the Matrix server. This is much faster than building all of Synapse from scratch."
  3542. msgstr ""
  3543. #: ../../../CHANGELOG.md:2533
  3544. msgid "2022-10-02"
  3545. msgstr ""
  3546. #: ../../../CHANGELOG.md:2535
  3547. msgid "matrix-ldap-registration-proxy support"
  3548. msgstr ""
  3549. #: ../../../CHANGELOG.md:2537
  3550. msgid "Thanks to [@TheOneWithTheBraid](https://github.com/TheOneWithTheBraid), we now support installing [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) — a proxy which handles Matrix registration requests and forwards them to LDAP."
  3551. msgstr ""
  3552. #: ../../../CHANGELOG.md:2539
  3553. msgid "See our [Setting up matrix-ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started."
  3554. msgstr ""
  3555. #: ../../../CHANGELOG.md:2542
  3556. msgid "2022-09-15"
  3557. msgstr ""
  3558. #: ../../../CHANGELOG.md:2544
  3559. msgid "(Potential Backward Compatibility Break) Major improvements to Synapse workers"
  3560. msgstr ""
  3561. #: ../../../CHANGELOG.md:2546
  3562. msgid "People who are interested in running a Synapse worker setup should know that **our Synapse worker implementation is much more powerful now**:"
  3563. msgstr ""
  3564. #: ../../../CHANGELOG.md:2548
  3565. msgid "we've added support for [Stream writers](#stream-writers-support)"
  3566. msgstr ""
  3567. #: ../../../CHANGELOG.md:2549
  3568. msgid "we've added support for [multiple federation sender workers](#multiple-federation-sender-workers-support)"
  3569. msgstr ""
  3570. #: ../../../CHANGELOG.md:2550
  3571. msgid "we've added support for [multiple pusher workers](#multiple-pusher-workers-support)"
  3572. msgstr ""
  3573. #: ../../../CHANGELOG.md:2551
  3574. msgid "we've added support for [running background tasks on a worker](#background-tasks-can-run-on-a-worker)"
  3575. msgstr ""
  3576. #: ../../../CHANGELOG.md:2552
  3577. msgid "we've restored support for [`appservice` workers](#appservice-worker-support-is-back)"
  3578. msgstr ""
  3579. #: ../../../CHANGELOG.md:2553
  3580. msgid "we've restored support for [`user_dir` workers](#user-directory-worker-support-is-back)"
  3581. msgstr ""
  3582. #: ../../../CHANGELOG.md:2554
  3583. msgid "we've made it possible to [reliably use more than 1 `media_repository` worker](#using-more-than-1-media-repository-worker-is-now-more-reliable)"
  3584. msgstr ""
  3585. #: ../../../CHANGELOG.md:2555
  3586. msgid "see the [Potential Backward Incompatibilities after these Synapse worker changes](#potential-backward-incompatibilities-after-these-synapse-worker-changes)"
  3587. msgstr ""
  3588. #: ../../../CHANGELOG.md:2557
  3589. msgid "Stream writers support"
  3590. msgstr ""
  3591. #: ../../../CHANGELOG.md:2559
  3592. msgid "From now on, the playbook lets you easily set up various [stream writer workers](https://matrix-org.github.io/synapse/latest/workers.html#stream-writers) which can handle different streams (`events` stream; `typing` URL endpoints, `to_device` URL endpoints, `account_data` URL endpoints, `receipts` URL endpoints, `presence` URL endpoints). All of this work was previously handled by the main Synapse process, but can now be offloaded to stream writer worker processes."
  3593. msgstr ""
  3594. #: ../../../CHANGELOG.md:2561
  3595. msgid "If you're using `matrix_synapse_workers_preset: one-of-each`, you'll automatically get 6 additional workers (one for each of the above stream types). Our `little-federation-helper` preset (meant to be quite minimal and focusing in improved federation performance) does not include stream writer workers."
  3596. msgstr ""
  3597. #: ../../../CHANGELOG.md:2563
  3598. msgid "If you'd like to customize the number of workers we also make that possible using these variables:"
  3599. msgstr ""
  3600. #: ../../../CHANGELOG.md:2576
  3601. msgid "Multiple federation sender workers support"
  3602. msgstr ""
  3603. #: ../../../CHANGELOG.md:2578
  3604. msgid "Until now, we only supported a single `federation_sender` worker (`matrix_synapse_workers_federation_sender_workers_count` could either be `0` or `1`). From now on, you can have as many as you want to help with your federation traffic."
  3605. msgstr ""
  3606. #: ../../../CHANGELOG.md:2580
  3607. msgid "Multiple pusher workers support"
  3608. msgstr ""
  3609. #: ../../../CHANGELOG.md:2582
  3610. msgid "Until now, we only supported a single `pusher` worker (`matrix_synapse_workers_pusher_workers_count` could either be `0` or `1`). From now on, you can have as many as you want to help with pushing notifications out."
  3611. msgstr ""
  3612. #: ../../../CHANGELOG.md:2584
  3613. msgid "Background tasks can run on a worker"
  3614. msgstr ""
  3615. #: ../../../CHANGELOG.md:2586
  3616. msgid "From now on, you can put [background task processing on a worker](https://matrix-org.github.io/synapse/latest/workers.html#background-tasks)."
  3617. msgstr ""
  3618. #: ../../../CHANGELOG.md:2588
  3619. msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `background` worker automatically. You can also control the `background` workers count with `matrix_synapse_workers_background_workers_count`. Only `0` or `1` workers of this type are supported by Synapse."
  3620. msgstr ""
  3621. #: ../../../CHANGELOG.md:2590
  3622. msgid "Appservice worker support is back"
  3623. msgstr ""
  3624. #: ../../../CHANGELOG.md:2592
  3625. msgid "We previously had an `appservice` worker type, which [Synapse deprecated in v1.59.0](https://github.com/element-hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-synapseappappservice-and-synapseappuser_dir-worker-application-types). So did we, at the time."
  3626. msgstr ""
  3627. #: ../../../CHANGELOG.md:2594
  3628. msgid "The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of talking to Application Services. From now on, we have support for this."
  3629. msgstr ""
  3630. #: ../../../CHANGELOG.md:2596
  3631. msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `appservice` worker automatically. You can also control the `appservice` workers count with `matrix_synapse_workers_appservice_workers_count`. Only `0` or `1` workers of this type are supported by Synapse."
  3632. msgstr ""
  3633. #: ../../../CHANGELOG.md:2598
  3634. msgid "User Directory worker support is back"
  3635. msgstr ""
  3636. #: ../../../CHANGELOG.md:2600
  3637. msgid "We previously had a `user_dir` worker type, which [Synapse deprecated in v1.59.0](https://github.com/element-hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-synapseappappservice-and-synapseappuser_dir-worker-application-types). So did we, at the time."
  3638. msgstr ""
  3639. #: ../../../CHANGELOG.md:2602
  3640. msgid "The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of serving the user directory. From now on, we have support for this."
  3641. msgstr ""
  3642. #: ../../../CHANGELOG.md:2604
  3643. msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `user_dir` worker automatically. You can also control the `user_dir` workers count with `matrix_synapse_workers_user_dir_workers_count`. Only `0` or `1` workers of this type are supported by Synapse."
  3644. msgstr ""
  3645. #: ../../../CHANGELOG.md:2606
  3646. msgid "Using more than 1 media repository worker is now more reliable"
  3647. msgstr ""
  3648. #: ../../../CHANGELOG.md:2608
  3649. msgid "With `matrix_synapse_workers_preset: one-of-each`, we only launch one `media_repository` worker."
  3650. msgstr ""
  3651. #: ../../../CHANGELOG.md:2610
  3652. msgid "If you've been configuring `matrix_synapse_workers_media_repository_workers_count` manually, you may have increased that to more workers. When multiple media repository workers are in use, background tasks related to the media repository must always be configured to run on a single `media_repository` worker via `media_instance_running_background_jobs`. Until now, we weren't doing this correctly, but we now are."
  3653. msgstr ""
  3654. #: ../../../CHANGELOG.md:2612
  3655. msgid "Potential Backward Incompatibilities after these Synapse worker changes"
  3656. msgstr ""
  3657. #: ../../../CHANGELOG.md:2614
  3658. msgid "Below we'll discuss **potential backward incompatibilities**."
  3659. msgstr ""
  3660. #: ../../../CHANGELOG.md:2616
  3661. msgid "**Worker names** (container names, systemd services, worker configuration files) **have changed**. Workers are now labeled sequentially (e.g. `matrix-synapse-worker_generic_worker-18111` -> `matrix-synapse-worker-generic-0`). The playbook will handle these changes automatically."
  3662. msgstr ""
  3663. #: ../../../CHANGELOG.md:2618
  3664. msgid "Due to increased worker types support above, people who use `matrix_synapse_workers_preset: one-of-each` should be aware that with these changes, **the playbook will deploy 9 additional workers** (6 stream writers, 1 `appservice` worker, 1 `user_dir` worker, 1 background task worker). This **may increase RAM/CPU usage**, etc. If you find your server struggling, consider disabling some workers with the appropriate `matrix_synapse_workers_*_workers_count` variables."
  3665. msgstr ""
  3666. #: ../../../CHANGELOG.md:2620
  3667. msgid "**Metric endpoints have also changed** (`/metrics/synapse/worker/generic_worker-18111` -> `/metrics/synapse/worker/generic-worker-0`). If you're [collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server), consider revisiting our [Collecting Synapse worker metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-server) docs and updating your Prometheus configuration. **If you're collecting metrics to the integrated Prometheus server** (not enabled by default), **your Prometheus configuration will be updated automatically**. Old data (from before this change) may stick around though."
  3668. msgstr ""
  3669. #: ../../../CHANGELOG.md:2622
  3670. msgid "**the format of `matrix_synapse_workers_enabled_list` has changed**. You were never advised to use this variable for directly creating workers (we advise people to control workers using `matrix_synapse_workers_preset` or by tweaking `matrix_synapse_workers_*_workers_count` variables only), but some people may have started using the `matrix_synapse_workers_enabled_list` variable to gain more control over workers. If you're one of them, you'll need to adjust its value. See `roles/custom/matrix-synapse/defaults/main.yml` for more information on the new format. The playbook will also do basic validation and complain if you got something wrong."
  3671. msgstr ""
  3672. #: ../../../CHANGELOG.md:2625
  3673. msgid "2022-09-09"
  3674. msgstr ""
  3675. #: ../../../CHANGELOG.md:2627
  3676. msgid "Cactus Comments support"
  3677. msgstr ""
  3678. #: ../../../CHANGELOG.md:2629
  3679. msgid "Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now set up [Cactus Comments](https://cactus.chat) — federated comment system for the web based on Matrix."
  3680. msgstr ""
  3681. #: ../../../CHANGELOG.md:2631
  3682. msgid "See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-comments.md) documentation to get started."
  3683. msgstr ""
  3684. #: ../../../CHANGELOG.md:2634
  3685. msgid "2022-08-23"
  3686. msgstr ""
  3687. #: ../../../CHANGELOG.md:2636
  3688. msgid "Postmoogle email bridge support"
  3689. msgstr ""
  3690. #: ../../../CHANGELOG.md:2638
  3691. msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the new [Postmoogle](https://github.com/etkecc/postmoogle) email bridge. Postmoogle is like the [Email2Matrix bridge](https://github.com/devture/email2matrix) (also [already supported by the playbook](docs/configuring-playbook-email2matrix.md)), but more capable and with the intention to soon support *sending* emails, not just receiving."
  3692. msgstr ""
  3693. #: ../../../CHANGELOG.md:2640
  3694. msgid "See our [Setting up Postmoogle email bridging](docs/configuring-playbook-bridge-postmoogle.md) documentation to get started."
  3695. msgstr ""
  3696. #: ../../../CHANGELOG.md:2643
  3697. msgid "2022-08-10"
  3698. msgstr ""
  3699. #: ../../../CHANGELOG.md:2645
  3700. msgid "mautrix-whatsapp default configuration changes"
  3701. msgstr ""
  3702. #: ../../../CHANGELOG.md:2647
  3703. msgid "In [Pull Request #2012](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2012), we've made some changes to the default configuration used by the `mautrix-whatsapp` bridge."
  3704. msgstr ""
  3705. #: ../../../CHANGELOG.md:2649
  3706. msgid "If you're using this bridge, you should look into this PR and see if the new configuration suits you. If not, you can always change individual preferences in your `vars.yml` file."
  3707. msgstr ""
  3708. #: ../../../CHANGELOG.md:2651
  3709. msgid "Most notably, spaces support has been enabled by default. The bridge will now group rooms into a Matrix space. **If you've already bridged to Whatsapp** prior to this update, you will need to send `!wa sync space` to the bridge bot to make it create the space and put your existing rooms into it."
  3710. msgstr ""
  3711. #: ../../../CHANGELOG.md:2654
  3712. msgid "2022-08-09"
  3713. msgstr ""
  3714. #: ../../../CHANGELOG.md:2656
  3715. msgid "Conduit support"
  3716. msgstr ""
  3717. #: ../../../CHANGELOG.md:2658
  3718. msgid "Thanks to [Charles Wright](https://github.com/cvwright), we now have optional experimental [Conduit](https://conduit.rs) homeserver support for new installations. This comes as a follow-up to the playbook getting [Dendrite support](#dendrite-support) earlier this year."
  3719. msgstr ""
  3720. #: ../../../CHANGELOG.md:2660
  3721. msgid "Existing Synapse or Dendrite installations do **not** need to be updated. **Synapse is still the default homeserver implementation** installed by the playbook."
  3722. msgstr ""
  3723. #: ../../../CHANGELOG.md:2662
  3724. msgid "To try out Conduit, we recommend that you **use a new server** and the following `vars.yml` configuration:"
  3725. msgstr ""
  3726. #: ../../../CHANGELOG.md:2668
  3727. msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse or Dendrite to Conduit) without data loss."
  3728. msgstr ""
  3729. #: ../../../CHANGELOG.md:2671
  3730. msgid "2022-07-29"
  3731. msgstr ""
  3732. #: ../../../CHANGELOG.md:2673
  3733. msgid "mautrix-discord support"
  3734. msgstr ""
  3735. #: ../../../CHANGELOG.md:2675
  3736. msgid "Thanks to [MdotAmaan](https://github.com/MdotAmaan)'s efforts, the playbook now supports bridging to [Discord](https://discordapp.com/) via the [mautrix-discord](https://mau.dev/mautrix/discord) bridge. See our [Setting up Mautrix Discord bridging](docs/configuring-playbook-bridge-mautrix-discord.md) documentation page for getting started."
  3737. msgstr ""
  3738. #: ../../../CHANGELOG.md:2677
  3739. msgid "**Note**: this is a new Discord bridge. The playbook still retains Discord bridging via [matrix-appservice-discord](docs/configuring-playbook-bridge-appservice-discord.md) and [mx-puppet-discord](docs/configuring-playbook-bridge-mx-puppet-discord.md). You're free to use the bridge that serves you better, or even all three of them (for different users and use-cases)."
  3740. msgstr ""
  3741. #: ../../../CHANGELOG.md:2680
  3742. msgid "2022-07-27"
  3743. msgstr ""
  3744. #: ../../../CHANGELOG.md:2682
  3745. msgid "matrix-appservice-kakaotalk support"
  3746. msgstr ""
  3747. #: ../../../CHANGELOG.md:2684
  3748. msgid "The playbook now supports bridging to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) via [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) — a bridge based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code. Thanks to [hnarjis](https://github.com/hnarjis) for helping us add support for this!"
  3749. msgstr ""
  3750. #: ../../../CHANGELOG.md:2686
  3751. msgid "See our [Setting up Appservice Kakaotalk bridging](docs/configuring-playbook-bridge-appservice-kakaotalk.md) documentation to get started."
  3752. msgstr ""
  3753. #: ../../../CHANGELOG.md:2689
  3754. msgid "2022-07-20"
  3755. msgstr ""
  3756. #: ../../../CHANGELOG.md:2691
  3757. msgid "maubot support"
  3758. msgstr ""
  3759. #: ../../../CHANGELOG.md:2693
  3760. msgid "Thanks to [Stuart Mumford (@Cadair)](https://github.com/cadair) for starting ([PR #373](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/373) and [PR #622](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/622)) and to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s) for finishing up (in [PR #1894](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1894)), the playbook can now help you set up [maubot](https://github.com/maubot/maubot) — a plugin-based Matrix bot system."
  3761. msgstr ""
  3762. #: ../../../CHANGELOG.md:2695
  3763. msgid "See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) documentation to get started."
  3764. msgstr ""
  3765. #: ../../../CHANGELOG.md:2698
  3766. msgid "2022-07-14"
  3767. msgstr ""
  3768. #: ../../../CHANGELOG.md:2700
  3769. msgid "mx-puppet-skype removal"
  3770. msgstr ""
  3771. #: ../../../CHANGELOG.md:2702
  3772. msgid "The playbook no longer includes the [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge, because it has been broken and unmaintained for a long time. Users that have `matrix_mx_puppet_skype_enabled` in their configuration files will encounter an error when running the playbook until they remove references to this bridge from their configuration."
  3773. msgstr ""
  3774. #: ../../../CHANGELOG.md:2704
  3775. msgid "To completely clean up your server from `mx-puppet-skype`'s presence on it:"
  3776. msgstr ""
  3777. #: ../../../CHANGELOG.md:2706
  3778. msgid "ensure your Ansible configuration (`vars.yml` file) no longer contains `matrix_mx_puppet_skype_*` references"
  3779. msgstr ""
  3780. #: ../../../CHANGELOG.md:2707
  3781. msgid "stop and disable the systemd service (run `systemctl disable --now matrix-mx-puppet-skype` on the server)"
  3782. msgstr ""
  3783. #: ../../../CHANGELOG.md:2708
  3784. msgid "delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-skype.service` on the server)"
  3785. msgstr ""
  3786. #: ../../../CHANGELOG.md:2709
  3787. msgid "delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on the server)"
  3788. msgstr ""
  3789. #: ../../../CHANGELOG.md:2710
  3790. msgid "drop the `matrix_mx_puppet_skype` database (run `/usr/local/bin/matrix-postgres-cli` on the server, and execute the `DROP DATABASE matrix_mx_puppet_skype;` query there)"
  3791. msgstr ""
  3792. #: ../../../CHANGELOG.md:2712
  3793. msgid "If you still need bridging to [Skype](https://www.skype.com/), consider switching to [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) instead. See [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md)."
  3794. msgstr ""
  3795. #: ../../../CHANGELOG.md:2714
  3796. msgid "If you think this is a mistake and `mx-puppet-skype` works for you (or you get it to work somehow), let us know and we may reconsider this removal."
  3797. msgstr ""
  3798. #: ../../../CHANGELOG.md:2716
  3799. msgid "signald (0.19.0+) upgrade requires data migration"
  3800. msgstr ""
  3801. #: ../../../CHANGELOG.md:2718
  3802. msgid "In [Pull Request #1921](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1921) we upgraded [signald](https://signald.org/) (used by the mautrix-signal bridge) from `v0.18.5` to `v0.20.0`."
  3803. msgstr ""
  3804. #: ../../../CHANGELOG.md:2720
  3805. msgid "Back in the [`v0.19.0` released of signald](https://gitlab.com/signald/signald/-/blob/main/releases/0.19.0.md) (which we skipped and migrated straight to `v0.20.0`), a new `--migrate-data` command had been added that migrates avatars, group images, attachments, etc., into the database (those were previously stored in the filesystem)."
  3806. msgstr ""
  3807. #: ../../../CHANGELOG.md:2722
  3808. msgid "If you've been using the mautrix-signal bridge for a while, you may have files stored in the local filesystem, which will need to be upgraded."
  3809. msgstr ""
  3810. #: ../../../CHANGELOG.md:2724
  3811. msgid "We attempt to do this data migration automatically every time Signald starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` systemd unit definition."
  3812. msgstr ""
  3813. #: ../../../CHANGELOG.md:2726
  3814. msgid "Keep an eye on your Signal bridge and let us know (in our [support room](README.md#support) or in [Pull Request #1921](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1921)) if you experience any trouble!"
  3815. msgstr ""
  3816. #: ../../../CHANGELOG.md:2729
  3817. msgid "2022-07-05"
  3818. msgstr ""
  3819. #: ../../../CHANGELOG.md:2731
  3820. msgid "Ntfy push notifications support"
  3821. msgstr ""
  3822. #: ../../../CHANGELOG.md:2733
  3823. msgid "Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the playbook can now install a [ntfy](https://ntfy.sh/) push notifications server for you."
  3824. msgstr ""
  3825. #: ../../../CHANGELOG.md:2735
  3826. msgid "See our [Setting up the ntfy push notifications server](docs/configuring-playbook-ntfy.md) documentation to get started."
  3827. msgstr ""
  3828. #: ../../../CHANGELOG.md:2738
  3829. msgid "2022-06-23"
  3830. msgstr ""
  3831. #: ../../../CHANGELOG.md:2740
  3832. msgid "(Potential Backward Compatibility Break) Changes around metrics collection"
  3833. msgstr ""
  3834. #: ../../../CHANGELOG.md:2742
  3835. msgid "**TLDR**: we've made extensive **changes to metrics exposure/collection, which concern people using an external Prometheus server**. If you don't know what that is, you don't need to read below."
  3836. msgstr ""
  3837. #: ../../../CHANGELOG.md:2744
  3838. msgid "**Why do major changes to metrics**? Because various services were exposing metrics in different, hacky, ways. Synapse was exposing metrics at `/_synapse/metrics` and `/_synapse-worker-…/metrics` on the `matrix.example.com`. The Hookshot role was **repurposing** the Granana web UI domain (`stats.example.com`) for exposing its metrics on `stats.example.com/hookshot/metrics`, while protecting these routes using Basic Authentication **normally used for Synapse** (`/_synapse/metrics`). Node-exporter and Postgres-exporter roles were advising for more `stats.example.com` usage in manual ways. Each role was doing things differently and mixing variables from other roles. Each metrics endpoint was ending up in a different place, protected by who knows what Basic Authentication credentials (if protected at all)."
  3839. msgstr ""
  3840. #: ../../../CHANGELOG.md:2746
  3841. msgid "**The solution**: a completely revamped way to expose metrics to an external Prometheus server. We are **introducing new `https://matrix.example.com/metrics/*` endpoints**, where various services *can* expose their metrics, for collection by external Prometheus servers. To enable the `/metrics/*` endpoints, use `matrix_nginx_proxy_proxy_matrix_metrics_enabled: true`. There's also a way to protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication). See the `matrix-nginx-proxy` role or our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation for additional variables around `matrix_nginx_proxy_proxy_matrix_metrics_enabled`."
  3842. msgstr ""
  3843. #: ../../../CHANGELOG.md:2748
  3844. msgid "**If you are using the [Hookshot bridge](docs/configuring-playbook-bridge-hookshot.md)**, you may find that:"
  3845. msgstr ""
  3846. #: ../../../CHANGELOG.md:2749
  3847. msgid "**Metrics may not be enabled by default anymore**:"
  3848. msgstr ""
  3849. #: ../../../CHANGELOG.md:2750
  3850. msgid "If Prometheus is enabled (`prometheus_enabled: true`), then Hookshot metrics will be enabled automatically (`matrix_hookshot_metrics_enabled: true`). These metrics will be collected from the local (in-container) Prometheus over the container network."
  3851. msgstr ""
  3852. #: ../../../CHANGELOG.md:2751
  3853. msgid "**If Prometheus is not enabled** (you are either not using Prometheus or are using an external one), **Hookshot metrics will not be enabled by default anymore**. Feel free to enable them by setting `matrix_hookshot_metrics_enabled: true`. Also, see below."
  3854. msgstr ""
  3855. #: ../../../CHANGELOG.md:2752
  3856. msgid "When metrics are meant to be **consumed by an external Prometheus server**, `matrix_hookshot_metrics_proxying_enabled` needs to be set to `true`, so that metrics would be exposed (proxied) \"publicly\" on `https://matrix.example.com/metrics/hookshot`. To make use of this, you'll also need to enable the new `https://matrix.example.com/metrics/*` endpoints mentioned above, using `matrix_nginx_proxy_proxy_matrix_metrics_enabled`. Learn more in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation."
  3857. msgstr ""
  3858. #: ../../../CHANGELOG.md:2753
  3859. msgid "**We've changed the URL we're exposing Hookshot metrics at** for external Prometheus servers. Until now, you were advised to consume Hookshot metrics from `https://stats.example.com/hookshot/metrics` (working in conjunction with `matrix_nginx_proxy_proxy_synapse_metrics`). From now on, **this no longer works**. As described above, you need to start consuming metrics from `https://matrix.example.com/metrics/hookshot`."
  3860. msgstr ""
  3861. #: ../../../CHANGELOG.md:2755
  3862. msgid "**If you're using node-exporter** (`matrix_prometheus_node_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_node_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/node-exporter`."
  3863. msgstr ""
  3864. #: ../../../CHANGELOG.md:2757
  3865. msgid "**If you're using [postgres-exporter](docs/configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-postgres-optional)** (`prometheus_postgres_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/postgres-exporter`."
  3866. msgstr ""
  3867. #: ../../../CHANGELOG.md:2759
  3868. msgid "**If you're using Synapse** and would like to collect its metrics from an external Prometheus server, you may find that:"
  3869. msgstr ""
  3870. #: ../../../CHANGELOG.md:2761
  3871. msgid "Exposing metrics is now done using `matrix_synapse_metrics_proxying_enabled`, not `matrix_nginx_proxy_proxy_synapse_metrics: true`. You may still need to enable metrics using `matrix_synapse_metrics_enabled: true` before exposing them."
  3872. msgstr ""
  3873. #: ../../../CHANGELOG.md:2762
  3874. msgid "Protecting metrics endpoints using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) is now done in another way. See our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation"
  3875. msgstr ""
  3876. #: ../../../CHANGELOG.md:2763
  3877. msgid "If Synapse metrics are exposed, they will be made available at `https://matrix.example.com/metrics/synapse/main-process` or `https://matrix.example.com/metrics/synapse/worker/TYPE-ID` (when workers are enabled), not at `https://matrix.example.com/_synapse/metrics` and `https://matrix.example.com/_synapse-worker-…/metrics`"
  3878. msgstr ""
  3879. #: ../../../CHANGELOG.md:2764
  3880. msgid "The playbook still generates an `external_prometheus.yml.example` sample file for scraping Synapse from Prometheus as described in [Collecting Synapse worker metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-server), but it's now saved under `/matrix/synapse` (not `/matrix`)."
  3881. msgstr ""
  3882. #: ../../../CHANGELOG.md:2766
  3883. msgid "**If you where already using a external Prometheus server** before this change, and you gave a hashed version of the password as a variable, the playbook will now take care of hashing the password for you. Thus, you need to provide the non-hashed version now."
  3884. msgstr ""
  3885. #: ../../../CHANGELOG.md:2768
  3886. msgid "2022-06-13"
  3887. msgstr ""
  3888. #: ../../../CHANGELOG.md:2770
  3889. msgid "go-skype-bridge bridging support"
  3890. msgstr ""
  3891. #: ../../../CHANGELOG.md:2772
  3892. msgid "Thanks to [CyberShadow](https://github.com/CyberShadow), the playbook can now install the [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) bridge for bridging Matrix to [Skype](https://www.skype.com/)."
  3893. msgstr ""
  3894. #: ../../../CHANGELOG.md:2774
  3895. msgid "See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md) documentation to get started."
  3896. msgstr ""
  3897. #: ../../../CHANGELOG.md:2776
  3898. msgid "The playbook has supported [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridging (see [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md)) since [2020-04-09](#2020-04-09), but `mx-puppet-skype` is reportedly broken."
  3899. msgstr ""
  3900. #: ../../../CHANGELOG.md:2779
  3901. msgid "2022-06-09"
  3902. msgstr ""
  3903. #: ../../../CHANGELOG.md:2781
  3904. msgid "Running Ansible in a container can now happen on the Matrix server itself"
  3905. msgstr ""
  3906. #: ../../../CHANGELOG.md:2783
  3907. msgid "If you're tired of being on an old and problematic Ansible version, you can now run [run Ansible in a container on the Matrix server itself](docs/ansible.md#running-ansible-in-a-container-on-the-matrix-server-itself)."
  3908. msgstr ""
  3909. #: ../../../CHANGELOG.md:2786
  3910. msgid "2022-05-31"
  3911. msgstr ""
  3912. #: ../../../CHANGELOG.md:2788
  3913. msgid "Synapse v1.60 upgrade may cause trouble and require manual intervention"
  3914. msgstr ""
  3915. #: ../../../CHANGELOG.md:2790
  3916. msgid "Synapse v1.60 will try to add a new unique index to `state_group_edges` upon startup and could fail if your database is corrupted."
  3917. msgstr ""
  3918. #: ../../../CHANGELOG.md:2792
  3919. msgid "We haven't observed this problem yet, but [the Synapse v1.60.0 upgrade notes](https://github.com/element-hq/synapse/blob/v1.60.0/docs/upgrade.md#adding-a-new-unique-index-to-state_group_edges-could-fail-if-your-database-is-corrupted) mention it, so we're giving you a heads up here in case you're unlucky."
  3920. msgstr ""
  3921. #: ../../../CHANGELOG.md:2794
  3922. msgid "**If Synapse fails to start** after your next playbook run, you'll need to:"
  3923. msgstr ""
  3924. #: ../../../CHANGELOG.md:2796
  3925. msgid "SSH into the Matrix server"
  3926. msgstr ""
  3927. #: ../../../CHANGELOG.md:2797
  3928. msgid "launch `/usr/local/bin/matrix-postgres-cli`"
  3929. msgstr ""
  3930. #: ../../../CHANGELOG.md:2798
  3931. msgid "switch to the `synapse` database: `\\c synapse`"
  3932. msgstr ""
  3933. #: ../../../CHANGELOG.md:2799
  3934. msgid "run the following SQL query:"
  3935. msgstr ""
  3936. #: ../../../CHANGELOG.md:2818
  3937. msgid "You could then restart services: `ansible-playbook -i inventory/hosts setup.yml --tags=start`"
  3938. msgstr ""
  3939. #: ../../../CHANGELOG.md:2821
  3940. msgid "2022-04-25"
  3941. msgstr ""
  3942. #: ../../../CHANGELOG.md:2823
  3943. msgid "Buscarron bot support"
  3944. msgstr ""
  3945. #: ../../../CHANGELOG.md:2825
  3946. msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [the Buscarron bot](https://github.com/etkecc/buscarron). It's a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room"
  3947. msgstr ""
  3948. #: ../../../CHANGELOG.md:2827
  3949. msgid "See our [Setting up Buscarron](docs/configuring-playbook-bot-buscarron.md) documentation to get started."
  3950. msgstr ""
  3951. #: ../../../CHANGELOG.md:2830
  3952. msgid "2022-04-21"
  3953. msgstr ""
  3954. #: ../../../CHANGELOG.md:2832
  3955. msgid "matrix-registration-bot support"
  3956. msgstr ""
  3957. #: ../../../CHANGELOG.md:2834
  3958. msgid "Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now help you set up [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) — a bot that is used to create and manage registration tokens for a Matrix server."
  3959. msgstr ""
  3960. #: ../../../CHANGELOG.md:2836
  3961. msgid "See our [Setting up matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) documentation to get started."
  3962. msgstr ""
  3963. #: ../../../CHANGELOG.md:2839
  3964. msgid "2022-04-19"
  3965. msgstr ""
  3966. #: ../../../CHANGELOG.md:2841
  3967. msgid "BorgBackup support"
  3968. msgstr ""
  3969. #: ../../../CHANGELOG.md:2843
  3970. msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [Borg](https://www.borgbackup.org/) backups with [borgmatic](https://torsion.org/borgmatic/) of your Matrix server."
  3971. msgstr ""
  3972. #: ../../../CHANGELOG.md:2845
  3973. msgid "See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md) documentation to get started."
  3974. msgstr ""
  3975. #: ../../../CHANGELOG.md:2847
  3976. msgid "(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action"
  3977. msgstr ""
  3978. #: ../../../CHANGELOG.md:2849
  3979. msgid "If you're running a worker setup for Synapse (`matrix_synapse_workers_enabled: true`), the [Synapse v1.57 upgrade notes](https://github.com/element-hq/synapse/blob/v1.57.0rc1/docs/upgrade.md#changes-to-database-schema-for-application-services) say that you may need to take special care when upgrading:"
  3980. msgstr ""
  3981. #: ../../../CHANGELOG.md:2851
  3982. msgid "Synapse v1.57.0 includes a change to the way transaction IDs are managed for application services. If your deployment uses a dedicated worker for application service traffic, **it must be stopped** when the database is upgraded (which normally happens when the main process is upgraded), to ensure the change is made safely without any risk of reusing transaction IDs."
  3983. msgstr ""
  3984. #: ../../../CHANGELOG.md:2853
  3985. msgid "If you're not running an `appservice` worker (`matrix_synapse_workers_preset: little-federation-helper` or `matrix_synapse_workers_appservice_workers_count: 0`), you are probably safe to upgrade as per normal, without taking any special care."
  3986. msgstr ""
  3987. #: ../../../CHANGELOG.md:2855
  3988. msgid "If you are running a setup with an `appservice` worker, or otherwise want to be on the safe side, we recommend the following upgrade path:"
  3989. msgstr ""
  3990. #: ../../../CHANGELOG.md:2857
  3991. msgid "Pull the latest playbook changes"
  3992. msgstr ""
  3993. #: ../../../CHANGELOG.md:2858
  3994. msgid "Stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"
  3995. msgstr ""
  3996. #: ../../../CHANGELOG.md:2859
  3997. msgid "Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all`)"
  3998. msgstr ""
  3999. #: ../../../CHANGELOG.md:2860
  4000. msgid "Start Postgres (`systemctl start matrix-postgres` on the server)"
  4001. msgstr ""
  4002. #: ../../../CHANGELOG.md:2861
  4003. msgid "Start the main Synapse process (`systemctl start matrix-synapse` on the server)"
  4004. msgstr ""
  4005. #: ../../../CHANGELOG.md:2862
  4006. msgid "Wait a while so that Synapse can start and complete the database migrations. You can use `journalctl -fu matrix-synapse` on the server to get a clue. Waiting a few minutes should also be enough."
  4007. msgstr ""
  4008. #: ../../../CHANGELOG.md:2863
  4009. msgid "It should now be safe to start all other services. `ansible-playbook -i inventory/hosts setup.yml --tags=start` will do it for you"
  4010. msgstr ""
  4011. #: ../../../CHANGELOG.md:2866
  4012. msgid "2022-04-14"
  4013. msgstr ""
  4014. #: ../../../CHANGELOG.md:2868
  4015. msgid "(Compatibility Break) Changes to `docker-src` permissions necessitating manual action"
  4016. msgstr ""
  4017. #: ../../../CHANGELOG.md:2870
  4018. msgid "Users who build container images from source will need to manually correct file permissions of some directories on the server."
  4019. msgstr ""
  4020. #: ../../../CHANGELOG.md:2872
  4021. msgid "When self-building, the playbook used to `git clone` repositories (into `/matrix/SERVICE/docker-src`) using the `root` user, but now uses `matrix` instead to work around [the following issue with git 2.35.2](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1749)."
  4022. msgstr ""
  4023. #: ../../../CHANGELOG.md:2874
  4024. msgid "If you're on a non-`amd64` architecture (that is, you're overriding `matrix_architecture` in your `vars.yml` file) or you have enabled self-building for some service (e.g. `matrix_*_self_build: true`), you're certainly building some container images from source and have `docker-src` directories with mixed permissions lying around in various `/matrix/SERVICE` directories."
  4025. msgstr ""
  4026. #: ../../../CHANGELOG.md:2876
  4027. msgid "The playbook *could* correct these permissions automatically, but that requires additional Ansible tasks in some ~45 different places — something that takes considerable effort. So we ask users observing errors related to `docker-src` directories to correct the problem manually by **running this command on the Matrix server** (which deletes all `/matrix/*/docker-src` directories): `find /matrix -maxdepth 2 -name 'docker-src' | xargs rm -rf`"
  4028. msgstr ""
  4029. #: ../../../CHANGELOG.md:2879
  4030. msgid "2022-03-17"
  4031. msgstr ""
  4032. #: ../../../CHANGELOG.md:2881
  4033. msgid "(Compatibility Break) ma1sd identity server no longer installed by default"
  4034. msgstr ""
  4035. #: ../../../CHANGELOG.md:2883
  4036. msgid "The playbook no longer installs the [ma1sd](https://github.com/ma1uta/ma1sd) identity server by default. The next time you run the playbook, ma1sd will be uninstalled from your server, unless you explicitly enable the ma1sd service (see how below)."
  4037. msgstr ""
  4038. #: ../../../CHANGELOG.md:2885
  4039. msgid "The main reason we used to install ma1sd by default in the past was to prevent Element clients from talking to the `matrix.org` / `vector.im` identity servers, by forcing it to talk to our own self-hosted (but otherwise useless) identity server instead, thus preventing contact list leaks."
  4040. msgstr ""
  4041. #: ../../../CHANGELOG.md:2887
  4042. msgid "Since Element clients no longer default to using a public identity server if another one is not provided, we can stop installing ma1sd."
  4043. msgstr ""
  4044. #: ../../../CHANGELOG.md:2889
  4045. msgid "If you need to install the ma1sd identity server for some reason, you can explicitly enable it by adding this to your `vars.yml` file:"
  4046. msgstr ""
  4047. #: ../../../CHANGELOG.md:2896
  4048. msgid "2022-02-12"
  4049. msgstr ""
  4050. #: ../../../CHANGELOG.md:2898
  4051. msgid "matrix_encryption_disabler support"
  4052. msgstr ""
  4053. #: ../../../CHANGELOG.md:2900
  4054. msgid "We now support installing the [matrix_encryption_disabler](https://github.com/digitalentity/matrix_encryption_disabler) Synapse module, which lets you prevent End-to-End-Encryption from being enabled by users on your homeserver. The popular opinion is that this is dangerous and shouldn't be done, but there are valid use cases for disabling encryption discussed [here](https://github.com/matrix-org/synapse/issues/4401)."
  4055. msgstr ""
  4056. #: ../../../CHANGELOG.md:2902
  4057. msgid "To enable this module (and prevent encryption from being used on your homserver), add `matrix_synapse_ext_encryption_disabler_enabled: true` to your configuration. This module provides further customization. Check its other configuration settings (and defaults) in `roles/custom/matrix-synapse/defaults/main.yml`."
  4058. msgstr ""
  4059. #: ../../../CHANGELOG.md:2905
  4060. msgid "2022-02-01"
  4061. msgstr ""
  4062. #: ../../../CHANGELOG.md:2907
  4063. msgid "matrix-hookshot bridging support"
  4064. msgstr ""
  4065. #: ../../../CHANGELOG.md:2909
  4066. msgid "Thanks to [HarHarLinks](https://github.com/HarHarLinks), the playbook can now install the [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) bridge for bridging Matrix to multiple project management services, such as GitHub, GitLab and JIRA. See our [Setting up matrix-hookshot](docs/configuring-playbook-bridge-hookshot.md) documentation to get started."
  4067. msgstr ""
  4068. #: ../../../CHANGELOG.md:2912
  4069. msgid "2022-01-31"
  4070. msgstr ""
  4071. #: ../../../CHANGELOG.md:2914
  4072. msgid "ARM support for matrix-corporal"
  4073. msgstr ""
  4074. #: ../../../CHANGELOG.md:2916
  4075. msgid "[matrix-corporal](https://github.com/devture/matrix-corporal) (as of version `2.2.3`) is now published to Docker Hub (see [devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-corporal)) as a multi-arch container image with support for all these platforms: `linux/amd64`, `linux/arm64/v8` and `linux/arm/v7`. The playbook no longer resorts to self-building matrix-corporal on these ARM architectures."
  4076. msgstr ""
  4077. #: ../../../CHANGELOG.md:2919
  4078. msgid "2022-01-07"
  4079. msgstr ""
  4080. #: ../../../CHANGELOG.md:2921
  4081. msgid "Dendrite support"
  4082. msgstr ""
  4083. #: ../../../CHANGELOG.md:2923
  4084. msgid "**TLDR**: We now have optional experimental [Dendrite](https://github.com/matrix-org/dendrite) homeserver support for new installations. **Existing (Synapse) installations need to be updated**, because some internals changed. See [Adapting the configuration for existing Synapse installations](#adapting-the-configuration-for-existing-synapse-installations)."
  4085. msgstr ""
  4086. #: ../../../CHANGELOG.md:2925
  4087. msgid "[Jip J. Dekker](https://github.com/Dekker1) did the [initial work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/818) of adding [Dendrite](https://github.com/matrix-org/dendrite) support to the playbook back in January 2021. Lots of work (and time) later, Dendrite support is finally ready for testing."
  4088. msgstr ""
  4089. #: ../../../CHANGELOG.md:2927
  4090. msgid "We believe that 2022 will be the year of the non-Synapse Matrix server!"
  4091. msgstr ""
  4092. #: ../../../CHANGELOG.md:2929
  4093. msgid "The playbook was previously quite [Synapse](https://github.com/element-hq/synapse)-centric, but can now accommodate multiple homeserver implementations. Only one homeserver implementation can be active (installed) at a given time."
  4094. msgstr ""
  4095. #: ../../../CHANGELOG.md:2931
  4096. msgid "**Synapse is still the default homeserver implementation** installed by the playbook. A new variable (`matrix_homeserver_implementation`) controls which server implementation is enabled (`synapse` or `dendrite` at the given moment)."
  4097. msgstr ""
  4098. #: ../../../CHANGELOG.md:2933
  4099. msgid "Adapting the configuration for existing Synapse installations"
  4100. msgstr ""
  4101. #: ../../../CHANGELOG.md:2935
  4102. msgid "Because the playbook is not so Synapse-centric anymore, a small configuration change is necessary for existing installations to bring them up to date."
  4103. msgstr ""
  4104. #: ../../../CHANGELOG.md:2937
  4105. msgid "The `vars.yml` file for **existing installations will need to be updated** by adding this **additional configuration**:"
  4106. msgstr ""
  4107. #: ../../../CHANGELOG.md:2949
  4108. msgid "Trying out Dendrite"
  4109. msgstr ""
  4110. #: ../../../CHANGELOG.md:2951
  4111. msgid "Finally, **to try out Dendrite**, we recommend that you **use a new server** and the following addition to your `vars.yml` configuration:"
  4112. msgstr ""
  4113. #: ../../../CHANGELOG.md:2957
  4114. msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse to Dendrite) without data loss."
  4115. msgstr ""
  4116. #: ../../../CHANGELOG.md:2959
  4117. msgid "We're excited to gain support for other homeserver implementations, like [Conduit](https://conduit.rs/), etc!"
  4118. msgstr ""
  4119. #: ../../../CHANGELOG.md:2961
  4120. msgid "Honoroit bot support"
  4121. msgstr ""
  4122. #: ../../../CHANGELOG.md:2963
  4123. msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now help you set up [Honoroit](https://github.com/etkecc/honoroit) — a helpdesk bot."
  4124. msgstr ""
  4125. #: ../../../CHANGELOG.md:2965
  4126. msgid "See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documentation to get started."
  4127. msgstr ""
  4128. #: ../../../CHANGELOG.md:2968
  4129. msgid "2022-01-06"
  4130. msgstr ""
  4131. #: ../../../CHANGELOG.md:2970
  4132. msgid "Cinny support"
  4133. msgstr ""
  4134. #: ../../../CHANGELOG.md:2972
  4135. msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports [Cinny](https://cinny.in/) — a new simple, elegant and secure Matrix client."
  4136. msgstr ""
  4137. #: ../../../CHANGELOG.md:2974
  4138. msgid "By default, we still install Element Web. Still, people who'd like to try Cinny out can now install it via the playbook."
  4139. msgstr ""
  4140. #: ../../../CHANGELOG.md:2976
  4141. msgid "Additional details are available in [Setting up Cinny](docs/configuring-playbook-client-cinny.md)."
  4142. msgstr ""
  4143. #: ../../../CHANGELOG.md:2979
  4144. msgid "2021-12-22"
  4145. msgstr ""
  4146. #: ../../../CHANGELOG.md:2981
  4147. msgid "Twitter bridging support via mautrix-twitter"
  4148. msgstr ""
  4149. #: ../../../CHANGELOG.md:2983
  4150. msgid "Thanks to [Matthew Cengia](https://github.com/mattcen) and [Shreyas Ajjarapu](https://github.com/shreyasajj), besides [mx-puppet-twitter](docs/configuring-playbook-bridge-mx-puppet-twitter.md), bridging to [Twitter](https://twitter.com/) can now also happen with [mautrix-twitter](docs/configuring-playbook-bridge-mautrix-twitter.md)."
  4151. msgstr ""
  4152. #: ../../../CHANGELOG.md:2986
  4153. msgid "2021-12-14"
  4154. msgstr ""
  4155. #: ../../../CHANGELOG.md:2988
  4156. msgid "(Security) Users of the Signal bridge may wish to upgrade it to work around log4j vulnerability"
  4157. msgstr ""
  4158. #: ../../../CHANGELOG.md:2990
  4159. msgid "Recently, a security vulnerability affecting the Java logging package `log4j` [has been discovered](https://www.huntress.com/blog/rapid-response-critical-rce-vulnerability-is-affecting-java). Software that uses this Java package is potentially vulnerable."
  4160. msgstr ""
  4161. #: ../../../CHANGELOG.md:2992
  4162. msgid "One such piece of software that is part of the playbook is the [mautrix-signal bridge](./docs/configuring-playbook-bridge-mautrix-signal.md), which [has been patched already](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1452). If you're running this bridge, you may wish to [upgrade](./docs/maintenance-upgrading-services.md)."
  4163. msgstr ""
  4164. #: ../../../CHANGELOG.md:2995
  4165. msgid "2021-11-11"
  4166. msgstr ""
  4167. #: ../../../CHANGELOG.md:2997
  4168. msgid "Dropped support for Postgres v9.6"
  4169. msgstr ""
  4170. #: ../../../CHANGELOG.md:2999
  4171. msgid "Postgres v9.6 reached its end of life today, so the playbook will refuse to run for you if you're still on that version."
  4172. msgstr ""
  4173. #: ../../../CHANGELOG.md:3001
  4174. msgid "Synapse still supports v9.6 (for now), but we're retiring support for it early, to avoid having to maintain support for so many Postgres versions. Users that are still on Postgres v9.6 can easily [upgrade Postgres](docs/maintenance-postgres.md#upgrading-postgresql) via the playbook."
  4175. msgstr ""
  4176. #: ../../../CHANGELOG.md:3004
  4177. msgid "2021-10-23"
  4178. msgstr ""
  4179. #: ../../../CHANGELOG.md:3006
  4180. msgid "Hangouts bridge no longer updated, superseded by a Googlechat bridge"
  4181. msgstr ""
  4182. #: ../../../CHANGELOG.md:3008
  4183. msgid "The mautrix-hangouts bridge is no longer receiving updates upstream and is likely to stop working in the future. We still retain support for this bridge in the playbook, but you're encouraged to switch away from it."
  4184. msgstr ""
  4185. #: ../../../CHANGELOG.md:3010
  4186. msgid "There's a new [mautrix-googlechat](https://github.com/mautrix/googlechat) bridge that you can [install using the playbook](docs/configuring-playbook-bridge-mautrix-googlechat.md). Your **Hangouts bridge data will not be migrated**, however. You need to start fresh with the new bridge."
  4187. msgstr ""
  4188. #: ../../../CHANGELOG.md:3013
  4189. msgid "2021-08-23"
  4190. msgstr ""
  4191. #: ../../../CHANGELOG.md:3015
  4192. msgid "LinkedIn bridging support via beeper-linkedin"
  4193. msgstr ""
  4194. #: ../../../CHANGELOG.md:3017
  4195. msgid "Thanks to [Alexandar Mechev](https://github.com/apmechev), the playbook can now install the [beeper-linkedin](https://gitlab.com/beeper/linkedin) bridge for bridging to [LinkedIn](https://www.linkedin.com/) Messaging."
  4196. msgstr ""
  4197. #: ../../../CHANGELOG.md:3019
  4198. msgid "This brings the total number of bridges supported by the playbook up to 20. See all supported bridges [here](docs/configuring-playbook.md#bridging-other-networks)."
  4199. msgstr ""
  4200. #: ../../../CHANGELOG.md:3021
  4201. msgid "To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)."
  4202. msgstr ""
  4203. #: ../../../CHANGELOG.md:3024
  4204. msgid "2021-08-20"
  4205. msgstr ""
  4206. #: ../../../CHANGELOG.md:3026
  4207. msgid "Sygnal upgraded — ARM support and no longer requires a database"
  4208. msgstr ""
  4209. #: ../../../CHANGELOG.md:3028
  4210. msgid "The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been upgraded from `v0.9.0` to `v0.10.1`."
  4211. msgstr ""
  4212. #: ../../../CHANGELOG.md:3030
  4213. msgid "This is an optional component for the playbook, so most of our users wouldn't care about this announcement."
  4214. msgstr ""
  4215. #: ../../../CHANGELOG.md:3032
  4216. msgid "Since this feels like a relatively big (and untested, as of yet) Sygnal change, we're putting up this changelog entry."
  4217. msgstr ""
  4218. #: ../../../CHANGELOG.md:3034
  4219. msgid "The new version is also available for the ARM architecture. It also no longer requires a database anymore. If you need to downgrade to the previous version, changing `matrix_sygnal_version` or `matrix_sygnal_docker_image` will not be enough, as we've removed the `database` configuration completely. You'd need to switch to an earlier playbook commit."
  4220. msgstr ""
  4221. #: ../../../CHANGELOG.md:3037
  4222. msgid "2021-05-21"
  4223. msgstr ""
  4224. #: ../../../CHANGELOG.md:3039
  4225. msgid "Hydrogen support"
  4226. msgstr ""
  4227. #: ../../../CHANGELOG.md:3041
  4228. msgid "Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook now supports [Hydrogen](https://github.com/vector-im/hydrogen-web) — a new lightweight Matrix client with legacy and mobile browser support."
  4229. msgstr ""
  4230. #: ../../../CHANGELOG.md:3043
  4231. msgid "By default, we still install Element Web, as Hydrogen is still not fully-featured. Still, people who'd like to try Hydrogen out can now install it via the playbook."
  4232. msgstr ""
  4233. #: ../../../CHANGELOG.md:3045
  4234. msgid "Additional details are available in [Setting up Hydrogen](docs/configuring-playbook-client-hydrogen.md)."
  4235. msgstr ""
  4236. #: ../../../CHANGELOG.md:3048
  4237. msgid "2021-05-19"
  4238. msgstr ""
  4239. #: ../../../CHANGELOG.md:3050
  4240. msgid "Heisenbridge support"
  4241. msgstr ""
  4242. #: ../../../CHANGELOG.md:3052
  4243. msgid "Thanks to [Toni Spets (hifi)](https://github.com/hifi), the playbook now supports bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) using yet another bridge (besides matrix-appservice-irc), called [Heisenbridge](https://github.com/hifi/heisenbridge)."
  4244. msgstr ""
  4245. #: ../../../CHANGELOG.md:3054
  4246. msgid "Additional details are available in [Setting up Heisenbridge bouncer-style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)."
  4247. msgstr ""
  4248. #: ../../../CHANGELOG.md:3057
  4249. msgid "2021-04-16"
  4250. msgstr ""
  4251. #: ../../../CHANGELOG.md:3059
  4252. msgid "Disabling TLSv1 and TLSv1.1 for coturn"
  4253. msgstr ""
  4254. #: ../../../CHANGELOG.md:3061
  4255. msgid "To improve security, we've [removed TLSv1 and TLSv1.1 support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/999) from our default [coturn](https://github.com/coturn/coturn) configuration."
  4256. msgstr ""
  4257. #: ../../../CHANGELOG.md:3063
  4258. msgid "If you need to support old clients, you can re-enable both (or whichever one you need) with the following configuration:"
  4259. msgstr ""
  4260. #: ../../../CHANGELOG.md:3071
  4261. msgid "2021-04-05"
  4262. msgstr ""
  4263. #: ../../../CHANGELOG.md:3073
  4264. msgid "Automated local Postgres backup support"
  4265. msgstr ""
  4266. #: ../../../CHANGELOG.md:3075
  4267. msgid "Thanks to [foxcris](https://github.com/foxcris), the playbook can now make automated local Postgres backups on a fixed schedule using [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local)."
  4268. msgstr ""
  4269. #: ../../../CHANGELOG.md:3077
  4270. msgid "Additional details are available in [Setting up Postgres backup](docs/configuring-playbook-postgres-backup.md)."
  4271. msgstr ""
  4272. #: ../../../CHANGELOG.md:3080
  4273. msgid "2021-04-03"
  4274. msgstr ""
  4275. #: ../../../CHANGELOG.md:3082
  4276. msgid "Mjolnir moderation tool (bot) support"
  4277. msgstr ""
  4278. #: ../../../CHANGELOG.md:3084
  4279. msgid "Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook can now install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation tool (bot)."
  4280. msgstr ""
  4281. #: ../../../CHANGELOG.md:3086
  4282. msgid "Additional details are available in [Setting up Mjolnir](docs/configuring-playbook-bot-mjolnir.md)."
  4283. msgstr ""
  4284. #: ../../../CHANGELOG.md:3089
  4285. msgid "2021-03-20"
  4286. msgstr ""
  4287. #: ../../../CHANGELOG.md:3091
  4288. msgid "Sygnal push gateway support"
  4289. msgstr ""
  4290. #: ../../../CHANGELOG.md:3093
  4291. msgid "The playbook can now install the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you."
  4292. msgstr ""
  4293. #: ../../../CHANGELOG.md:3095
  4294. msgid "This is only useful to people who develop/build their own Matrix client applications."
  4295. msgstr ""
  4296. #: ../../../CHANGELOG.md:3097
  4297. msgid "Additional details are available in our [Setting up the Sygnal push gateway](docs/configuring-playbook-sygnal.md) docs."
  4298. msgstr ""
  4299. #: ../../../CHANGELOG.md:3100
  4300. msgid "2021-03-16"
  4301. msgstr ""
  4302. #: ../../../CHANGELOG.md:3102
  4303. msgid "Go-NEB support"
  4304. msgstr ""
  4305. #: ../../../CHANGELOG.md:3104
  4306. msgid "Thanks to [Zir0h](https://github.com/Zir0h), the playbook can now install and configure the [Go-NEB](https://github.com/matrix-org/go-neb) bot."
  4307. msgstr ""
  4308. #: ../../../CHANGELOG.md:3106
  4309. msgid "Additional details are available in [Setting up Go-NEB](docs/configuring-playbook-bot-go-neb.md)."
  4310. msgstr ""
  4311. #: ../../../CHANGELOG.md:3109
  4312. msgid "2021-02-19"
  4313. msgstr ""
  4314. #: ../../../CHANGELOG.md:3111
  4315. msgid "GroupMe bridging support via mx-puppet-groupme"
  4316. msgstr ""
  4317. #: ../../../CHANGELOG.md:3113
  4318. msgid "Thanks to [Cody Neiman](https://github.com/xangelix), the playbook can now install the [mx-puppet-groupme](https://gitlab.com/robintown/mx-puppet-groupme) bridge for bridging to [GroupMe](https://groupme.com)."
  4319. msgstr ""
  4320. #: ../../../CHANGELOG.md:3115
  4321. msgid "This brings the total number of bridges supported by the playbook up to 18. See all supported bridges [here](docs/configuring-playbook.md#bridging-other-networks)."
  4322. msgstr ""
  4323. #: ../../../CHANGELOG.md:3117
  4324. msgid "To get started, follow our [Setting up MX Puppet GroupMe](docs/configuring-playbook-bridge-mx-puppet-groupme.md) docs."
  4325. msgstr ""
  4326. #: ../../../CHANGELOG.md:3119
  4327. msgid "Mautrix Instagram bridging support"
  4328. msgstr ""
  4329. #: ../../../CHANGELOG.md:3121
  4330. msgid "The playbook now supports bridging with [Instagram](https://www.instagram.com/) by installing the [mautrix-instagram](https://github.com/tulir/mautrix-instagram) bridge. This playbook functionality is available thanks to [@MarcProe](https://github.com/MarcProe)."
  4331. msgstr ""
  4332. #: ../../../CHANGELOG.md:3123
  4333. msgid "Additional details are available in [Setting up Mautrix Instagram bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)."
  4334. msgstr ""
  4335. #: ../../../CHANGELOG.md:3125
  4336. msgid "Synapse workers support"
  4337. msgstr ""
  4338. #: ../../../CHANGELOG.md:3127
  4339. msgid "After [lots and lots of work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/456) (done over many months by [Marcel Partap](https://github.com/eMPee584), [Max Klenk](https://github.com/maxklenk), a few others from the [Technical University of Dresden, Germany](https://tu-dresden.de/) and various other contributors), support for Synapse workers has finally landed."
  4340. msgstr ""
  4341. #: ../../../CHANGELOG.md:3129
  4342. msgid "Having support for workers makes the playbook suitable for larger homeserver deployments."
  4343. msgstr ""
  4344. #: ../../../CHANGELOG.md:3131
  4345. msgid "Our setup is not yet perfect (we don't support all types of workers; scaling some of them (like `pusher`, `federation_sender`) beyond a single instance is not yet supported). Still, it's a great start and can already power homeservers with thousands of users, like the [Matrix deployment at TU Dresden](https://doc.matrix.tu-dresden.de/en/) discussed in [Matrix Live S06E09 — TU Dresden on their Matrix deployment](https://www.youtube.com/watch?v=UHJX2pmT2gk)."
  4346. msgstr ""
  4347. #: ../../../CHANGELOG.md:3133
  4348. msgid "By default, workers are disabled and Synapse runs as a single process (homeservers don't necessarily need the complexity and increased memory requirements of running a worker-based setup)."
  4349. msgstr ""
  4350. #: ../../../CHANGELOG.md:3135
  4351. msgid "To enable Synapse workers, follow our [Load balancing with workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) documentation."
  4352. msgstr ""
  4353. #: ../../../CHANGELOG.md:3138
  4354. msgid "2021-02-12"
  4355. msgstr ""
  4356. #: ../../../CHANGELOG.md:3140
  4357. msgid "(Potential Breaking Change) Monitoring/metrics support using Prometheus and Grafana"
  4358. msgstr ""
  4359. #: ../../../CHANGELOG.md:3142
  4360. msgid "Thanks to [@Peetz0r](https://github.com/Peetz0r), the playbook can now install a bunch of tools for monitoring your Matrix server: the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI."
  4361. msgstr ""
  4362. #: ../../../CHANGELOG.md:3144
  4363. msgid "To get get these installed, follow our [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](docs/configuring-playbook-prometheus-grafana.md) docs page."
  4364. msgstr ""
  4365. #: ../../../CHANGELOG.md:3146
  4366. msgid "This update comes with a **potential breaking change** for people who were already exposing Synapse metrics (for consumption via another Prometheus installation). From now on, `matrix_synapse_metrics_enabled: true` no longer exposes metrics publicly via matrix-nginx-proxy (at `https://matrix.example.com/_synapse/metrics`). To do so, you'd need to explicitly set `matrix_nginx_proxy_proxy_synapse_metrics: true`."
  4367. msgstr ""
  4368. #: ../../../CHANGELOG.md:3149
  4369. msgid "2021-01-31"
  4370. msgstr ""
  4371. #: ../../../CHANGELOG.md:3151
  4372. msgid "Etherpad support"
  4373. msgstr ""
  4374. #: ../../../CHANGELOG.md:3153
  4375. msgid "Thanks to [@pushytoxin](https://github.com/pushytoxin), the playbook can now install the [Etherpad](https://etherpad.org) realtime collaborative text editor. It can be used in a [Jitsi](https://jitsi.org/) audio/video call or integrated as a widget into Matrix chat rooms via the [Dimension](https://dimension.t2bot.io) integration manager."
  4376. msgstr ""
  4377. #: ../../../CHANGELOG.md:3155
  4378. msgid "To get it installed, follow [our Etherpad docs page](docs/configuring-playbook-etherpad.md)."
  4379. msgstr ""
  4380. #: ../../../CHANGELOG.md:3158
  4381. msgid "2021-01-22"
  4382. msgstr ""
  4383. #: ../../../CHANGELOG.md:3160
  4384. msgid "(Breaking Change) Postgres changes that require manual intervention"
  4385. msgstr ""
  4386. #: ../../../CHANGELOG.md:3162
  4387. msgid "We've made a lot of changes to our Postgres setup and some manual action is required (described below). Sorry about the hassle."
  4388. msgstr ""
  4389. #: ../../../CHANGELOG.md:3164
  4390. msgid "**TLDR**: people running an [external Postgres server](docs/configuring-playbook-external-postgres.md) don't need to change anything for now. Everyone else (the common/default case) is affected and manual intervention is required."
  4391. msgstr ""
  4392. #: ../../../CHANGELOG.md:3166
  4393. msgid "Why?"
  4394. msgstr ""
  4395. #: ../../../CHANGELOG.md:3168
  4396. msgid "we had a default Postgres password (`matrix_postgres_connection_password: synapse-password`), which we think is **not ideal for security anymore**. We now ask you to generate/provide a strong password yourself. Postgres is normally not exposed outside the container network, making it relatively secure, but still:"
  4397. msgstr ""
  4398. #: ../../../CHANGELOG.md:3169
  4399. msgid "by tweaking the configuration, you may end up intentionally or unintentionally exposing your Postgres server to the local network (or even publicly), while still using the default default credentials (`synapse` + `synapse-password`)"
  4400. msgstr ""
  4401. #: ../../../CHANGELOG.md:3170
  4402. msgid "we can't be sure we trust all these services (bridges, etc). Some of them may try to talk to or attack `matrix-postgres` using the default credentials (`synapse` + `synapse-password`)"
  4403. msgstr ""
  4404. #: ../../../CHANGELOG.md:3171
  4405. msgid "you may have other containers running on the same Docker network, which may try to talk to or attack `matrix-postgres` using the default credentials (`synapse` + `synapse-password`)"
  4406. msgstr ""
  4407. #: ../../../CHANGELOG.md:3172
  4408. msgid "our Postgres usage **was overly-focused on Synapse** (default username of `synapse` and default/main database of `homeserver`). Additional homeserver options are likely coming in the future ([Dendrite](https://matrix.org/docs/projects/server/dendrite), [Conduit](https://matrix.org/docs/projects/server/conduit), [The Construct](https://matrix.org/docs/projects/server/construct)), so being too focused on `matrix-synapse` is not great. From now on, Synapse is just another component of this playbook, which happens to have an *additional database* (called `synapse`) on the Postgres server."
  4409. msgstr ""
  4410. #: ../../../CHANGELOG.md:3173
  4411. msgid "we try to reorganize things a bit, to make the playbook even friendlier to people running an [external Postgres server](docs/configuring-playbook-external-postgres.md). Work on this will proceed in the future."
  4412. msgstr ""
  4413. #: ../../../CHANGELOG.md:3175
  4414. msgid "So, this is some **effort to improve security** and to **prepare for a brighter future of having more homeserver options** than just Synapse."
  4415. msgstr ""
  4416. #: ../../../CHANGELOG.md:3177
  4417. msgid "What has really changed?"
  4418. msgstr ""
  4419. #: ../../../CHANGELOG.md:3179
  4420. msgid "the default superuser Postgres username is now `matrix` (used to be `synapse`)"
  4421. msgstr ""
  4422. #: ../../../CHANGELOG.md:3180
  4423. msgid "the default Postgres database is now `matrix` (used to be `homeserver`)"
  4424. msgstr ""
  4425. #: ../../../CHANGELOG.md:3181
  4426. msgid "Synapse's database is now `synapse` (used to be `homeserver`). This is now just another \"additional database\" that the playbook manages for you"
  4427. msgstr ""
  4428. #: ../../../CHANGELOG.md:3182
  4429. msgid "Synapse's user called `synapse` is just a regular user that can only use the `synapse` database (not a superuser anymore)"
  4430. msgstr ""
  4431. #: ../../../CHANGELOG.md:3184
  4432. msgid "What do I do if I'm using the integrated Postgres server (default)?"
  4433. msgstr ""
  4434. #: ../../../CHANGELOG.md:3186
  4435. msgid "By default, the playbook runs an integrated Postgres server for you in a container (`matrix-postgres`). Unless you've explicitly configured an [external Postgres server](docs/configuring-playbook-external-postgres.md), these steps are meant for you."
  4436. msgstr ""
  4437. #: ../../../CHANGELOG.md:3188
  4438. msgid "To migrate to the new setup, expect a few minutes of downtime, while you follow these steps:"
  4439. msgstr ""
  4440. #: ../../../CHANGELOG.md:3190
  4441. msgid "We believe the steps below are safe and you won't encounter any data loss, but consider [making a Postgres backup](docs/maintenance-postgres.md#backing-up-postgresql) anyway. If you've never backed up Postgres, now would be a good time to try it."
  4442. msgstr ""
  4443. #: ../../../CHANGELOG.md:3192
  4444. msgid "Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can create one with a command like `pwgen -s 64 1`. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy!"
  4445. msgstr ""
  4446. #: ../../../CHANGELOG.md:3194
  4447. msgid "Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` file, adding a line like this:"
  4448. msgstr ""
  4449. #: ../../../CHANGELOG.md:3199
  4450. #: ../../../CHANGELOG.md:3211
  4451. msgid "… where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2."
  4452. msgstr ""
  4453. #: ../../../CHANGELOG.md:3201
  4454. msgid "Stop all services: `ansible-playbook -i inventory/hosts setup.yml --tags=stop`"
  4455. msgstr ""
  4456. #: ../../../CHANGELOG.md:3202
  4457. msgid "Log in to the server via SSH. The next commands will be performed there."
  4458. msgstr ""
  4459. #: ../../../CHANGELOG.md:3203
  4460. msgid "Start the Postgres database server: `systemctl start matrix-postgres`"
  4461. msgstr ""
  4462. #: ../../../CHANGELOG.md:3204
  4463. msgid "Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`"
  4464. msgstr ""
  4465. #: ../../../CHANGELOG.md:3205
  4466. msgid "Execute the following query, while making sure to **change the password inside** (**don't forget the ending `;`**):"
  4467. msgstr ""
  4468. #: ../../../CHANGELOG.md:3213
  4469. msgid "Execute the following queries as you see them (no modifications necessary, so you can just **paste them all at once**):"
  4470. msgstr ""
  4471. #: ../../../CHANGELOG.md:3231
  4472. msgid "You may need to press *Enter* after pasting the lines above."
  4473. msgstr ""
  4474. #: ../../../CHANGELOG.md:3233
  4475. msgid "Re-run the playbook normally: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`"
  4476. msgstr ""
  4477. #: ../../../CHANGELOG.md:3235
  4478. msgid "What do I do if I'm using an external Postgres server?"
  4479. msgstr ""
  4480. #: ../../../CHANGELOG.md:3237
  4481. msgid "If you've explicitly configured an [external Postgres server](docs/configuring-playbook-external-postgres.md), there are **no changes** that you need to do at this time."
  4482. msgstr ""
  4483. #: ../../../CHANGELOG.md:3239
  4484. msgid "The fact that we've renamed Synapse's database from `homeserver` to `synapse` (in our defaults) should not affect you, as you're already explicitly defining `matrix_synapse_database_database` (if you've followed our guide, that is). If you're not explicitly defining this variable, you may wish to do so (`matrix_synapse_database_database: homeserver`), to avoid the new `synapse` default and keep things as they were."
  4485. msgstr ""
  4486. #: ../../../CHANGELOG.md:3242
  4487. msgid "2021-01-20"
  4488. msgstr ""
  4489. #: ../../../CHANGELOG.md:3244
  4490. msgid "(Breaking Change) The mautrix-facebook bridge now requires a Postgres database"
  4491. msgstr ""
  4492. #: ../../../CHANGELOG.md:3246
  4493. msgid "**Update from 2021-11-15**: SQLite support has been re-added to the mautrix-facebook bridge in [v0.3.2](https://github.com/mautrix/facebook/releases/tag/v0.3.2). You can ignore this changelog entry."
  4494. msgstr ""
  4495. #: ../../../CHANGELOG.md:3248
  4496. msgid "A new version of the [mautrix-facebook](https://github.com/tulir/mautrix-facebook) bridge has been released. It's a full rewrite of its backend and the bridge now requires Postgres. New versions of the bridge can no longer run on SQLite."
  4497. msgstr ""
  4498. #: ../../../CHANGELOG.md:3250
  4499. msgid "**TLDR**: if you're NOT using an [external Postgres server](docs/configuring-playbook-external-postgres.md) and have NOT forcefully kept the bridge on SQLite during [The big move to all-on-Postgres (potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous), you will be automatically upgraded without manual intervention. All you need to do is send a `login` message to the Facebook bridge bot again."
  4500. msgstr ""
  4501. #: ../../../CHANGELOG.md:3252
  4502. msgid "Whether this change requires your intervention depends mostly on:"
  4503. msgstr ""
  4504. #: ../../../CHANGELOG.md:3253
  4505. msgid "whether you're using an [external Postgres server](docs/configuring-playbook-external-postgres.md). If yes, then [you need to do something](#upgrade-path-for-people-running-an-external-postgres-server)."
  4506. msgstr ""
  4507. #: ../../../CHANGELOG.md:3254
  4508. msgid "or whether you've force-changed the bridge's database engine to SQLite (`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) some time in the past (likely during [The big move to all-on-Postgres (potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous))."
  4509. msgstr ""
  4510. #: ../../../CHANGELOG.md:3256
  4511. msgid "As already mentioned above, you most likely don't need to do anything. If you rerun the playbook and don't get an error, you've been automatically upgraded. Just send a `login` message to the Facebook bridge bot again. Otherwise, read below for a solution."
  4512. msgstr ""
  4513. #: ../../../CHANGELOG.md:3258
  4514. msgid "Upgrade path for people NOT running an external Postgres server (default for the playbook)"
  4515. msgstr ""
  4516. #: ../../../CHANGELOG.md:3260
  4517. msgid "If you're **not running an external Postgres server**, then this bridge either already works on Postgres for you, or you've intentionally kept it back on SQLite with custom configuration (`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) ."
  4518. msgstr ""
  4519. #: ../../../CHANGELOG.md:3262
  4520. msgid "Simply remove that custom configuration from your `vars.yml` file (if it's there) and re-run the playbook. It should upgrade you automatically. You'll need to send a `login` message to the Facebook bridge bot again."
  4521. msgstr ""
  4522. #: ../../../CHANGELOG.md:3264
  4523. msgid "Alternatively, [you can stay on SQLite for a little longer](#staying-on-sqlite-for-a-little-longer-temporary-solution)."
  4524. msgstr ""
  4525. #: ../../../CHANGELOG.md:3266
  4526. msgid "Upgrade path for people running an external Postgres server"
  4527. msgstr ""
  4528. #: ../../../CHANGELOG.md:3268
  4529. msgid "For people using the internal Postgres server (the default for the playbook):"
  4530. msgstr ""
  4531. #: ../../../CHANGELOG.md:3269
  4532. msgid "we automatically create an additional `matrix_mautrix_facebook` Postgres database and credentials to access it"
  4533. msgstr ""
  4534. #: ../../../CHANGELOG.md:3270
  4535. msgid "we automatically adjust the bridge's `matrix_mautrix_facebook_database_*` variables to point the bridge to that Postgres database"
  4536. msgstr ""
  4537. #: ../../../CHANGELOG.md:3271
  4538. msgid "we use [pgloader](https://pgloader.io/) to automatically import the existing SQLite data for the bridge into the `matrix_mautrix_facebook` Postgres database"
  4539. msgstr ""
  4540. #: ../../../CHANGELOG.md:3273
  4541. msgid "If you are using an [external Postgres server](docs/configuring-playbook-external-postgres.md), unfortunately we currently can't do any of that for you."
  4542. msgstr ""
  4543. #: ../../../CHANGELOG.md:3275
  4544. msgid "You have 3 ways to proceed:"
  4545. msgstr ""
  4546. #: ../../../CHANGELOG.md:3277
  4547. msgid "contribute to the playbook to make this possible (difficult)"
  4548. msgstr ""
  4549. #: ../../../CHANGELOG.md:3278
  4550. msgid "or, do the migration \"steps\" manually:"
  4551. msgstr ""
  4552. #: ../../../CHANGELOG.md:3279
  4553. msgid "stop the bridge (`systemctl stop matrix-mautrix-facebook`)"
  4554. msgstr ""
  4555. #: ../../../CHANGELOG.md:3280
  4556. msgid "create a new `matrix_mautrix_facebook` Postgres database for it"
  4557. msgstr ""
  4558. #: ../../../CHANGELOG.md:3281
  4559. msgid "run [pgloader](https://pgloader.io/) manually (we import this bridge's data using default settings and it works well)"
  4560. msgstr ""
  4561. #: ../../../CHANGELOG.md:3282
  4562. msgid "define `matrix_mautrix_facebook_database_*` variables in your `vars.yml` file (credentials, etc.) — you can find their defaults in `roles/custom/matrix-mautrix-facebook/defaults/main.yml`"
  4563. msgstr ""
  4564. #: ../../../CHANGELOG.md:3283
  4565. msgid "switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: 'postgres'` in your `vars.yml` file)"
  4566. msgstr ""
  4567. #: ../../../CHANGELOG.md:3284
  4568. msgid "re-run the playbook (`--tags=setup-all,start`) and ensure the bridge works (`systemctl status matrix-mautrix-facebook` and `journalctl -fu matrix-mautrix-facebook`)"
  4569. msgstr ""
  4570. #: ../../../CHANGELOG.md:3285
  4571. msgid "send a `login` message to the Facebook bridge bot again"
  4572. msgstr ""
  4573. #: ../../../CHANGELOG.md:3286
  4574. msgid "or, [stay on SQLite for a little longer (temporary solution)](#staying-on-sqlite-for-a-little-longer-temporary-solution)"
  4575. msgstr ""
  4576. #: ../../../CHANGELOG.md:3288
  4577. msgid "Staying on SQLite for a little longer (temporary solution)"
  4578. msgstr ""
  4579. #: ../../../CHANGELOG.md:3290
  4580. msgid "To keep using this bridge with SQLite for a little longer (**not recommended**), use the following configuration in your `vars.yml` file:"
  4581. msgstr ""
  4582. #: ../../../CHANGELOG.md:3300
  4583. msgid "If you do this, keep in mind that **you can't run this forever**. This SQLite-supporting bridge version is not getting any updates and will break sooner or later. The playbook will also drop support for SQLite at some point in the future."
  4584. msgstr ""
  4585. #: ../../../CHANGELOG.md:3303
  4586. msgid "2021-01-17"
  4587. msgstr ""
  4588. #: ../../../CHANGELOG.md:3305
  4589. msgid "matrix-corporal goes 2.0"
  4590. msgstr ""
  4591. #: ../../../CHANGELOG.md:3307
  4592. msgid "[matrix-corporal v2 has been released](https://github.com/devture/matrix-corporal/releases/tag/2.0.0) and the playbook also supports it now."
  4593. msgstr ""
  4594. #: ../../../CHANGELOG.md:3309
  4595. msgid "No manual intervention is required in the common case."
  4596. msgstr ""
  4597. #: ../../../CHANGELOG.md:3311
  4598. msgid "The new [matrix-corporal](https://github.com/devture/matrix-corporal) version is also the first one to support Interactive Authentication. If you wish to enable that (hint: you should), you'll need to set up the [REST auth password provider](docs/configuring-playbook-rest-auth.md). There's more information in [our matrix-corporal docs](docs/configuring-playbook-matrix-corporal.md)."
  4599. msgstr ""
  4600. #: ../../../CHANGELOG.md:3314
  4601. msgid "2021-01-14"
  4602. msgstr ""
  4603. #: ../../../CHANGELOG.md:3316
  4604. msgid "Moving from cronjobs to systemd timers"
  4605. msgstr ""
  4606. #: ../../../CHANGELOG.md:3318
  4607. msgid "We no longer use cronjobs for Let's Encrypt SSL renewal and `matrix-nginx-proxy`/`matrix-coturn` reloading. Instead, we've switched to systemd timers."
  4608. msgstr ""
  4609. #: ../../../CHANGELOG.md:3320
  4610. msgid "The largest benefit of this is that we no longer require you to install a cron daemon, thus simplifying our install procedure."
  4611. msgstr ""
  4612. #: ../../../CHANGELOG.md:3322
  4613. msgid "The playbook will migrate you from cronjobs to systemd timers automatically. This is just a heads up."
  4614. msgstr ""
  4615. #: ../../../CHANGELOG.md:3325
  4616. msgid "2021-01-08"
  4617. msgstr ""
  4618. #: ../../../CHANGELOG.md:3327
  4619. msgid "(Breaking Change) New SSL configuration"
  4620. msgstr ""
  4621. #: ../../../CHANGELOG.md:3329
  4622. msgid "SSL configuration (protocols, ciphers) can now be more easily controlled thanks to us making use of configuration presets."
  4623. msgstr ""
  4624. #: ../../../CHANGELOG.md:3331
  4625. msgid "We define a few presets (old, intermediate, modern), following the [Mozilla SSL Configuration Generator](https://ssl-config.mozilla.org/#server=nginx)."
  4626. msgstr ""
  4627. #: ../../../CHANGELOG.md:3333
  4628. msgid "A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is used (defaults to `\"intermediate\"`)."
  4629. msgstr ""
  4630. #: ../../../CHANGELOG.md:3335
  4631. msgid "Compared to before, this changes nginx's `ssl_prefer_server_ciphers` to `off` (used to default to `on`). It also add some more ciphers to the list, giving better performance on mobile devices, and removes some weak ciphers. More information in the [documentation](docs/configuring-playbook-nginx.md)."
  4632. msgstr ""
  4633. #: ../../../CHANGELOG.md:3337
  4634. msgid "To revert to the old behaviour, set the following variables:"
  4635. msgstr ""
  4636. #: ../../../CHANGELOG.md:3344
  4637. msgid "Just like before, you can still use your own custom protocols by specifying them in `matrix_nginx_proxy_ssl_protocols`. Doing so overrides the values coming from the preset."
  4638. msgstr ""
  4639. #: ../../../CHANGELOG.md:3347
  4640. msgid "2021-01-03"
  4641. msgstr ""
  4642. #: ../../../CHANGELOG.md:3349
  4643. msgid "Signal bridging support via mautrix-signal"
  4644. msgstr ""
  4645. #: ../../../CHANGELOG.md:3351
  4646. msgid "Thanks to [laszabine](https://github.com/laszabine)'s efforts, the playbook now supports bridging to [Signal](https://www.signal.org/) via the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge. See our [Setting up Mautrix Signal bridging](docs/configuring-playbook-bridge-mautrix-signal.md) documentation page for getting started."
  4647. msgstr ""
  4648. #: ../../../CHANGELOG.md:3353
  4649. msgid "If you had installed the mautrix-signal bridge while its Pull Request was still work-in-progress, you can migrate your data to the new and final setup by referring to [this comment](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/686#issuecomment-753510789)."
  4650. msgstr ""
  4651. #: ../../../CHANGELOG.md:3356
  4652. msgid "2020-12-23"
  4653. msgstr ""
  4654. #: ../../../CHANGELOG.md:3358
  4655. msgid "The big move to all-on-Postgres (potentially dangerous)"
  4656. msgstr ""
  4657. #: ../../../CHANGELOG.md:3360
  4658. msgid "**TLDR**: all your bridges (and other services) will likely be auto-migrated from SQLite/nedb to Postgres, hopefully without trouble. You can opt-out (see how below), if too worried about breakage."
  4659. msgstr ""
  4660. #: ../../../CHANGELOG.md:3362
  4661. msgid "Until now, we've only used Postgres as a database for Synapse. All other services (bridges, bots, etc.) were kept simple and used a file-based database (SQLite or nedb)."
  4662. msgstr ""
  4663. #: ../../../CHANGELOG.md:3364
  4664. msgid "Since [this huge pull request](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/740), **all of our services now use Postgres by default**. Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann) for starting the work on it and for providing great input!"
  4665. msgstr ""
  4666. #: ../../../CHANGELOG.md:3366
  4667. msgid "Moving all services to Postgres brings a few **benefits** to us:"
  4668. msgstr ""
  4669. #: ../../../CHANGELOG.md:3368
  4670. msgid "**improved performance**"
  4671. msgstr ""
  4672. #: ../../../CHANGELOG.md:3369
  4673. msgid "**improved compatibility**. Most bridges are deprecating SQLite/nedb support or offer less features when not on Postgres."
  4674. msgstr ""
  4675. #: ../../../CHANGELOG.md:3370
  4676. msgid "**easier backups**. It's still some effort to take a proper backup (Postgres dump + various files, keys), but a Postgres dump now takes you much further."
  4677. msgstr ""
  4678. #: ../../../CHANGELOG.md:3371
  4679. msgid "we're now **more prepared to introduce other services** that need a Postgres database — [Dendrite](https://github.com/matrix-org/dendrite), the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge (existing [pull request](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/686)), etc."
  4680. msgstr ""
  4681. #: ../../../CHANGELOG.md:3373
  4682. msgid "Key takeway"
  4683. msgstr ""
  4684. #: ../../../CHANGELOG.md:3375
  4685. msgid "existing installations that use an [external Postgres](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-external-postgres.md) server should be unaffected (they remain on SQLite/nedb for all services, except Synapse)"
  4686. msgstr ""
  4687. #: ../../../CHANGELOG.md:3377
  4688. msgid "for existing installations which use our integrated Postgres database server (`matrix-postgres`, which is the default), **we automatically migrate data** from SQLite/nedb to Postgres and **archive the database files** (`something.db` -> `something.db.backup`), so you can restore them if you need to go back (see how below)."
  4689. msgstr ""
  4690. #: ../../../CHANGELOG.md:3379
  4691. msgid "Opting-out of the Postgres migration"
  4692. msgstr ""
  4693. #: ../../../CHANGELOG.md:3381
  4694. msgid "This is a **very large and somewhat untested change** (potentially dangerous), so **if you're not feeling confident/experimental, opt-out** of it for now. Still, it's the new default and what we (and various bridges) will focus on going forward, so don't stick to old ways for too long."
  4695. msgstr ""
  4696. #: ../../../CHANGELOG.md:3383
  4697. msgid "You can remain on SQLite/nedb (at least for now) by adding a variable like this to your `vars.yml` file for each service you use: `matrix_COMPONENT_database_engine: sqlite` (e.g. `matrix_mautrix_facebook_database_engine: sqlite`)."
  4698. msgstr ""
  4699. #: ../../../CHANGELOG.md:3385
  4700. msgid "Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them."
  4701. msgstr ""
  4702. #: ../../../CHANGELOG.md:3387
  4703. msgid "Going back to SQLite/nedb if things went wrong"
  4704. msgstr ""
  4705. #: ../../../CHANGELOG.md:3389
  4706. msgid "If you went with the Postgres migration and it went badly for you (some bridge not working as expected or not working at all), do this:"
  4707. msgstr ""
  4708. #: ../../../CHANGELOG.md:3391
  4709. msgid "stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"
  4710. msgstr ""
  4711. #: ../../../CHANGELOG.md:3392
  4712. msgid "SSH into the server and rename the old database files (`something.db.backup` -> `something.db`). Example: `mv /matrix/mautrix-facebook/data/mautrix-facebook.db.backup /matrix/mautrix-facebook/data/mautrix-facebook.db`"
  4713. msgstr ""
  4714. #: ../../../CHANGELOG.md:3393
  4715. msgid "switch the affected service back to SQLite (e.g. `matrix_mautrix_facebook_database_engine: sqlite`). Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them."
  4716. msgstr ""
  4717. #: ../../../CHANGELOG.md:3394
  4718. msgid "re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`)"
  4719. msgstr ""
  4720. #: ../../../CHANGELOG.md:3395
  4721. msgid "[get in touch](README.md#support) with us"
  4722. msgstr ""
  4723. #: ../../../CHANGELOG.md:3397
  4724. msgid "2020-12-11"
  4725. msgstr ""
  4726. #: ../../../CHANGELOG.md:3399
  4727. msgid "synapse-janitor support removed"
  4728. msgstr ""
  4729. #: ../../../CHANGELOG.md:3401
  4730. msgid "We've removed support for the unmaintained [synapse-janitor](https://github.com/xwiki-labs/synapse_scripts) script. There's been past reports of it corrupting the Synapse database. Since there hasn't been any new development on it and it doesn't seem too useful nowadays, there's no point in including it in the playbook."
  4731. msgstr ""
  4732. #: ../../../CHANGELOG.md:3403
  4733. msgid "If you need to clean up or compact your database, consider using the Synapse Admin APIs directly. See our [Synapse maintenance](docs/maintenance-synapse.md) and [Postgres maintenance](docs/maintenance-postgres.md) documentation pages for more details."
  4734. msgstr ""
  4735. #: ../../../CHANGELOG.md:3405
  4736. msgid "Docker 20.10 is here"
  4737. msgstr ""
  4738. #: ../../../CHANGELOG.md:3407
  4739. msgid "(No need to do anything special in relation to this. Just something to keep in mind)"
  4740. msgstr ""
  4741. #: ../../../CHANGELOG.md:3409
  4742. msgid "Docker 20.10 got released recently and your server will likely get it the next time you update."
  4743. msgstr ""
  4744. #: ../../../CHANGELOG.md:3411
  4745. msgid "This is the first major Docker update in a long time and it packs a lot of changes. Some of them introduced some breakage for us initially (see [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/d08b27784f222effcbce2abf924bf07bbe0893be) and [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/7593d969e316cc0144bce378a5be58c76c2c37ee)), but it should be all good now."
  4746. msgstr ""
  4747. #: ../../../CHANGELOG.md:3414
  4748. msgid "2020-12-08"
  4749. msgstr ""
  4750. #: ../../../CHANGELOG.md:3416
  4751. msgid "openid APIs exposed by default on the federation port when federation disabled"
  4752. msgstr ""
  4753. #: ../../../CHANGELOG.md:3418
  4754. msgid "We've changed some defaults. People running with our default configuration (federation enabled), are not affected at all."
  4755. msgstr ""
  4756. #: ../../../CHANGELOG.md:3420
  4757. msgid "If you are running an unfederated server (`matrix_synapse_federation_enabled: false`), this may be of interest to you."
  4758. msgstr ""
  4759. #: ../../../CHANGELOG.md:3422
  4760. msgid "When federation is disabled, but ma1sd or Dimension are enabled, we'll now expose the `openid` APIs on the federation port. These APIs are necessary for some ma1sd features to work. If you'd like to prevent this, you can: `matrix_synapse_federation_port_openid_resource_required: false`."
  4761. msgstr ""
  4762. #: ../../../CHANGELOG.md:3425
  4763. msgid "2020-11-27"
  4764. msgstr ""
  4765. #: ../../../CHANGELOG.md:3427
  4766. msgid "Recent Jitsi updates may require configuration changes"
  4767. msgstr ""
  4768. #: ../../../CHANGELOG.md:3429
  4769. msgid "We've recently [updated from Jitsi build 4857 to build 5142](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/719), which brings a lot of configuration changes."
  4770. msgstr ""
  4771. #: ../../../CHANGELOG.md:3431
  4772. msgid "**If you use our default Jitsi settings, you won't have to do anything.**"
  4773. msgstr ""
  4774. #: ../../../CHANGELOG.md:3433
  4775. msgid "People who have [fine-tuned Jitsi](docs/configuring-playbook-jitsi.md#optional-fine-tune-jitsi) may find that some options got renamed now, others are gone and yet others still need to be defined in another way."
  4776. msgstr ""
  4777. #: ../../../CHANGELOG.md:3435
  4778. msgid "The next time you run the playbook [installation](docs/installing.md) command, our validation logic will tell you if you're using some variables like that and will recommend a migration path for each one."
  4779. msgstr ""
  4780. #: ../../../CHANGELOG.md:3437
  4781. msgid "Additionally, we've recently disabled transcriptions (`jitsi_enable_transcriptions: false`) and recording (`jitsi_enable_recording: false`) by default. These features did not work anyway, because we don't install the required dependencies for them (Jigasi and Jibri, respectively). If you've been somehow pointing your Jitsi installation to some manually installed Jigasi/Jibri service, you may need to toggle these flags back to enabled to have transcriptions and recordings working."
  4782. msgstr ""
  4783. #: ../../../CHANGELOG.md:3440
  4784. msgid "2020-11-23"
  4785. msgstr ""
  4786. #: ../../../CHANGELOG.md:3442
  4787. #: ../../../CHANGELOG.md:3450
  4788. msgid "Breaking change matrix-sms-bridge"
  4789. msgstr ""
  4790. #: ../../../CHANGELOG.md:3444
  4791. msgid "Because of many problems using gammu as SMS provider, matrix-sms-bridge now uses (https://github.com/RebekkaMa/android-sms-gateway-server) by default. See (the docs)[./docs/configuring-playbook-bridge-matrix-bridge-sms.md] which new vars you need to add."
  4792. msgstr ""
  4793. #: ../../../CHANGELOG.md:3446
  4794. msgid "If you are using this playbook to deploy matrix-sms-bridge and still really want to use gammu as SMS provider, we could possibly add support for both android-sms-gateway-server and gammu."
  4795. msgstr ""
  4796. #: ../../../CHANGELOG.md:3448
  4797. msgid "2020-11-13"
  4798. msgstr ""
  4799. #: ../../../CHANGELOG.md:3452
  4800. msgid "The new version of [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) changed its database from neo4j to h2. You need to sync the bridge at the first start. Note that this only will sync rooms where the @smsbot:yourServer is member. For rooms without @smsbot:yourServer you need to kick and invite the telephone number **or** invite @smsbot:yourServer."
  4801. msgstr ""
  4802. #: ../../../CHANGELOG.md:3454
  4803. msgid "Add the following to your `vars.yml` file: `matrix_sms_bridge_container_extra_arguments=['--env SPRING_PROFILES_ACTIVE=initialsync']`"
  4804. msgstr ""
  4805. #: ../../../CHANGELOG.md:3455
  4806. msgid "Login to your host shell and remove old systemd file from your host: `rm /etc/systemd/system/matrix-sms-bridge-database.service`"
  4807. msgstr ""
  4808. #: ../../../CHANGELOG.md:3456
  4809. msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-sms-bridge,start`"
  4810. msgstr ""
  4811. #: ../../../CHANGELOG.md:3457
  4812. msgid "Login to your host shell and check the logs with `journalctl -u matrix-sms-bridge` until the sync finished."
  4813. msgstr ""
  4814. #: ../../../CHANGELOG.md:3458
  4815. msgid "Remove the var from the first step."
  4816. msgstr ""
  4817. #: ../../../CHANGELOG.md:3459
  4818. msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`."
  4819. msgstr ""
  4820. #: ../../../CHANGELOG.md:3461
  4821. msgid "2020-11-10"
  4822. msgstr ""
  4823. #: ../../../CHANGELOG.md:3463
  4824. msgid "Dynamic DNS support"
  4825. msgstr ""
  4826. #: ../../../CHANGELOG.md:3465
  4827. msgid "Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook can now manage Dynamic DNS for you using [ddclient](https://ddclient.net/)."
  4828. msgstr ""
  4829. #: ../../../CHANGELOG.md:3467
  4830. msgid "To learn more, follow our [Dynamic DNS docs page](docs/configuring-playbook-dynamic-dns.md)."
  4831. msgstr ""
  4832. #: ../../../CHANGELOG.md:3470
  4833. msgid "2020-10-28"
  4834. msgstr ""
  4835. #: ../../../CHANGELOG.md:3472
  4836. msgid "(Compatibility Break) https://matrix.example.com/ now redirects to https://element.example.com/"
  4837. msgstr ""
  4838. #: ../../../CHANGELOG.md:3474
  4839. msgid "Until now, we used to serve a static page coming from Synapse at `https://matrix.example.com/`. This page was not very useful to anyone."
  4840. msgstr ""
  4841. #: ../../../CHANGELOG.md:3476
  4842. msgid "Since `matrix.example.com` may be accessed by regular users in certain conditions, it's probably better to redirect them to a better place (e.g. to [Element Web](docs/configuring-playbook-client-element-web.md))."
  4843. msgstr ""
  4844. #: ../../../CHANGELOG.md:3478
  4845. msgid "If Element Web is installed (`matrix_client_element_enabled: true`, which it is by default), we now redirect people to it, instead of showing them a Synapse static page."
  4846. msgstr ""
  4847. #: ../../../CHANGELOG.md:3480
  4848. msgid "If you'd like to control where the redirect goes, use the `matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain` variable. To restore the old behavior of not redirecting anywhere and serving the Synapse static page, set it to an empty value (`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain: \"\"`)."
  4849. msgstr ""
  4850. #: ../../../CHANGELOG.md:3483
  4851. msgid "2020-10-26"
  4852. msgstr ""
  4853. #: ../../../CHANGELOG.md:3485
  4854. msgid "(Compatibility Break) /_synapse/admin is no longer publicly exposed by default"
  4855. msgstr ""
  4856. #: ../../../CHANGELOG.md:3487
  4857. msgid "We used to expose the Synapse Admin APIs publicly (at `https://matrix.example.com/_synapse/admin`). These APIs require authentication with a valid access token, so it's not that big a deal to expose them."
  4858. msgstr ""
  4859. #: ../../../CHANGELOG.md:3489
  4860. msgid "However, following [official Synapse's reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints), we're no longer exposing `/_synapse/admin` by default."
  4861. msgstr ""
  4862. #: ../../../CHANGELOG.md:3491
  4863. msgid "If you'd like to restore restore the old behavior and expose `/_synapse/admin` publicly, you can use the following configuration (in your `vars.yml`):"
  4864. msgstr ""
  4865. #: ../../../CHANGELOG.md:3498
  4866. msgid "2020-10-02"
  4867. msgstr ""
  4868. #: ../../../CHANGELOG.md:3500
  4869. msgid "Minimum Ansible version raised to v2.7.0"
  4870. msgstr ""
  4871. #: ../../../CHANGELOG.md:3502
  4872. msgid "We were claiming to support [Ansible](https://www.ansible.com/) v2.5.2 and higher, but issues like [#662](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/662) demonstrate that we need at least v2.7.0."
  4873. msgstr ""
  4874. #: ../../../CHANGELOG.md:3504
  4875. msgid "If you've been using the playbook without getting any errors until now, you're probably on a version higher than that already (or you're not using the `matrix-ma1sd` and `matrix-client-element` roles)."
  4876. msgstr ""
  4877. #: ../../../CHANGELOG.md:3506
  4878. msgid "Our [Ansible docs page](docs/ansible.md) contains information on how to run a more up-to-date version of Ansible."
  4879. msgstr ""
  4880. #: ../../../CHANGELOG.md:3509
  4881. msgid "2020-10-01"
  4882. msgstr ""
  4883. #: ../../../CHANGELOG.md:3511
  4884. msgid "Postgres 13 support"
  4885. msgstr ""
  4886. #: ../../../CHANGELOG.md:3513
  4887. msgid "The playbook now installs [Postgres 13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) by default."
  4888. msgstr ""
  4889. #: ../../../CHANGELOG.md:3515
  4890. msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x, 10.x, 11.x or 12.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)."
  4891. msgstr ""
  4892. #: ../../../CHANGELOG.md:3517
  4893. msgid "2020-09-01"
  4894. msgstr ""
  4895. #: ../../../CHANGELOG.md:3519
  4896. msgid "matrix-registration support"
  4897. msgstr ""
  4898. #: ../../../CHANGELOG.md:3521
  4899. msgid "The playbook can now help you set up [matrix-registration](https://github.com/ZerataX/matrix-registration) — an application that lets you keep your Matrix server's registration private, but still allow certain users (those having a unique registration link) to register by themselves."
  4900. msgstr ""
  4901. #: ../../../CHANGELOG.md:3523
  4902. msgid "See our [Setting up matrix-registration](docs/configuring-playbook-matrix-registration.md) documentation page to get started."
  4903. msgstr ""
  4904. #: ../../../CHANGELOG.md:3526
  4905. msgid "2020-08-21"
  4906. msgstr ""
  4907. #: ../../../CHANGELOG.md:3528
  4908. msgid "rust-synapse-compress-state support"
  4909. msgstr ""
  4910. #: ../../../CHANGELOG.md:3530
  4911. msgid "The playbook can now help you use [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) to compress the state groups in your Synapse database."
  4912. msgstr ""
  4913. #: ../../../CHANGELOG.md:3532
  4914. msgid "See our [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state) documentation page to get started."
  4915. msgstr ""
  4916. #: ../../../CHANGELOG.md:3535
  4917. msgid "2020-07-22"
  4918. msgstr ""
  4919. #: ../../../CHANGELOG.md:3537
  4920. msgid "Synapse Admin support"
  4921. msgstr ""
  4922. #: ../../../CHANGELOG.md:3539
  4923. msgid "The playbook can now help you set up [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin)."
  4924. msgstr ""
  4925. #: ../../../CHANGELOG.md:3541
  4926. msgid "See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-admin.md) documentation to get started."
  4927. msgstr ""
  4928. #: ../../../CHANGELOG.md:3544
  4929. msgid "2020-07-20"
  4930. msgstr ""
  4931. #: ../../../CHANGELOG.md:3546
  4932. msgid "matrix-reminder-bot support"
  4933. msgstr ""
  4934. #: ../../../CHANGELOG.md:3548
  4935. msgid "The playbook can now help you set up [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)."
  4936. msgstr ""
  4937. #: ../../../CHANGELOG.md:3550
  4938. msgid "See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-matrix-reminder-bot.md) documentation to get started."
  4939. msgstr ""
  4940. #: ../../../CHANGELOG.md:3553
  4941. msgid "2020-07-17"
  4942. msgstr ""
  4943. #: ../../../CHANGELOG.md:3555
  4944. msgid "(Compatibility Break) Riot is now Element"
  4945. msgstr ""
  4946. #: ../../../CHANGELOG.md:3557
  4947. msgid "As per the official announcement, [Riot has been rebraned to Element](https://element.io/blog/welcome-to-element/)."
  4948. msgstr ""
  4949. #: ../../../CHANGELOG.md:3559
  4950. msgid "The playbook follows suit. Existing installations have a few options for how to handle this."
  4951. msgstr ""
  4952. #: ../../../CHANGELOG.md:3561
  4953. msgid "See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md#migrating-to-element) documentation page for more details."
  4954. msgstr ""
  4955. #: ../../../CHANGELOG.md:3564
  4956. msgid "2020-07-03"
  4957. msgstr ""
  4958. #: ../../../CHANGELOG.md:3566
  4959. msgid "Steam bridging support via mx-puppet-steam"
  4960. msgstr ""
  4961. #: ../../../CHANGELOG.md:3568
  4962. msgid "Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the playbook now supports bridging to [Steam](https://steamapp.com/) via the [mx-puppet-steam](https://codeberg.org/icewind/mx-puppet-steam) bridge. See our [Setting up MX Puppet Steam bridging](docs/configuring-playbook-bridge-mx-puppet-steam.md) documentation page for getting started."
  4963. msgstr ""
  4964. #: ../../../CHANGELOG.md:3571
  4965. msgid "2020-07-01"
  4966. msgstr ""
  4967. #: ../../../CHANGELOG.md:3573
  4968. msgid "Discord bridging support via mx-puppet-discord"
  4969. msgstr ""
  4970. #: ../../../CHANGELOG.md:3575
  4971. msgid "Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the playbook now supports bridging to [Discord](https://discordapp.com/) via the [mx-puppet-discord](https://github.com/Sorunome/mx-puppet-discord) bridge. See our [Setting up MX Puppet Discord bridging](docs/configuring-playbook-bridge-mx-puppet-discord.md) documentation page for getting started."
  4972. msgstr ""
  4973. #: ../../../CHANGELOG.md:3577
  4974. msgid "**Note**: this is a new Discord bridge. The playbook still retains Discord bridging via [matrix-appservice-discord](docs/configuring-playbook-bridge-appservice-discord.md). You're free too use the bridge that serves you better, or even both (for different users and use-cases)."
  4975. msgstr ""
  4976. #: ../../../CHANGELOG.md:3580
  4977. msgid "2020-06-30"
  4978. msgstr ""
  4979. #: ../../../CHANGELOG.md:3582
  4980. msgid "Instagram and Twitter bridging support"
  4981. msgstr ""
  4982. #: ../../../CHANGELOG.md:3584
  4983. msgid "Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann)'s efforts, the playbook now supports bridging to [Instagram](https://www.instagram.com/) via the [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) bridge. See our [Setting up MX Puppet Instagram bridging](docs/configuring-playbook-bridge-mx-puppet-instagram.md) documentation page for getting started."
  4984. msgstr ""
  4985. #: ../../../CHANGELOG.md:3586
  4986. msgid "Thanks to [Tulir Asokan](https://github.com/tulir)'s efforts, the playbook now supports bridging to [Twitter](https://twitter.com/) via the [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) bridge. See our [Setting up MX Puppet Twitter bridging](docs/configuring-playbook-bridge-mx-puppet-twitter.md) documentation page for getting started."
  4987. msgstr ""
  4988. #: ../../../CHANGELOG.md:3589
  4989. msgid "2020-06-28"
  4990. msgstr ""
  4991. #: ../../../CHANGELOG.md:3591
  4992. msgid "(Post Mortem / fixed Security Issue) Re-enabling User Directory search powered by the ma1sd Identity Server"
  4993. msgstr ""
  4994. #: ../../../CHANGELOG.md:3593
  4995. #: ../../../CHANGELOG.md:3622
  4996. msgid "User Directory search requests used to go to the ma1sd identity server by default, which queried its own stores and the Synapse database."
  4997. msgstr ""
  4998. #: ../../../CHANGELOG.md:3595
  4999. msgid "ma1sd's [security issue](https://github.com/ma1uta/ma1sd/issues/44) has been fixed in version `2.4.0`, with [this commit](ma1uta/ma1sd@2bb5a734d11662b06471113cf3d6b4cee5e33a85). `ma1sd 2.4.0` is now the default version for this playbook. For more information on what happened, please check the mentioned issue."
  5000. msgstr ""
  5001. #: ../../../CHANGELOG.md:3597
  5002. msgid "We are re-enabling user directory search with this update. Those who would like to keep it disabled can use this configuration: `matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: false`"
  5003. msgstr ""
  5004. #: ../../../CHANGELOG.md:3599
  5005. msgid "As always, re-running the playbook is enough to get the updated bits."
  5006. msgstr ""
  5007. #: ../../../CHANGELOG.md:3601
  5008. msgid "2020-06-11"
  5009. msgstr ""
  5010. #: ../../../CHANGELOG.md:3603
  5011. msgid "SMS bridging requires db reset"
  5012. msgstr ""
  5013. #: ../../../CHANGELOG.md:3605
  5014. msgid "The current version of [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) needs you to delete the database to work as expected. Just remove `/matrix/matrix-sms-bridge/database/*`. It also adds a new required var `matrix_sms_bridge_default_region`."
  5015. msgstr ""
  5016. #: ../../../CHANGELOG.md:3607
  5017. msgid "To reuse your existing rooms, invite `@smsbot:yourServer` to the room or write a message. You are also able to use automated room creation with telephonenumers by writing `sms send -t 01749292923 \"Hello World\"` in a room with `@smsbot:yourServer`. See [the docs](https://github.com/benkuly/matrix-sms-bridge) for more information."
  5018. msgstr ""
  5019. #: ../../../CHANGELOG.md:3609
  5020. msgid "2020-06-05"
  5021. msgstr ""
  5022. #: ../../../CHANGELOG.md:3611
  5023. msgid "SMS bridging support"
  5024. msgstr ""
  5025. #: ../../../CHANGELOG.md:3613
  5026. msgid "Thanks to [benkuly](https://github.com/benkuly)'s efforts, the playbook now supports bridging to SMS (with one telephone number only) via [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)."
  5027. msgstr ""
  5028. #: ../../../CHANGELOG.md:3615
  5029. msgid "See our [Setting up Matrix SMS bridging](docs/configuring-playbook-bridge-matrix-bridge-sms.md) documentation page for getting started."
  5030. msgstr ""
  5031. #: ../../../CHANGELOG.md:3618
  5032. msgid "2020-05-19"
  5033. msgstr ""
  5034. #: ../../../CHANGELOG.md:3620
  5035. msgid "(Compatibility Break / Security Issue) Disabling User Directory search powered by the ma1sd Identity Server"
  5036. msgstr ""
  5037. #: ../../../CHANGELOG.md:3624
  5038. msgid "ma1sd current has [a security issue](https://github.com/ma1uta/ma1sd/issues/44), which made it leak information about all users — including users created by bridges, etc."
  5039. msgstr ""
  5040. #: ../../../CHANGELOG.md:3626
  5041. msgid "Until the issue gets fixed, we're making User Directory search not go to ma1sd by default. You **need to re-run the playbook and restart services to apply this workaround**."
  5042. msgstr ""
  5043. #: ../../../CHANGELOG.md:3628
  5044. msgid "*If you insist on restoring the old behavior* (**which has a security issue!**), you *might* use this configuration: `matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: \"{{ matrix_ma1sd_enabled }}\"`"
  5045. msgstr ""
  5046. #: ../../../CHANGELOG.md:3631
  5047. msgid "2020-04-28"
  5048. msgstr ""
  5049. #: ../../../CHANGELOG.md:3633
  5050. msgid "Newer IRC bridge (with potential breaking change)"
  5051. msgstr ""
  5052. #: ../../../CHANGELOG.md:3635
  5053. msgid "This upgrades matrix-appservice-irc from 0.14.1 to 0.16.0. Upstream made a change to how you define manual mappings. If you added a `mapping` to your configuration, you will need to update it according to the [upstream instructions](https://github.com/matrix-org/matrix-appservice-irc/blob/master/CHANGELOG.md#0150-2020-02-05). If you did not include `mappings` in your configuration for IRC, no change is necessary. `mappings` is not part of the default configuration."
  5054. msgstr ""
  5055. #: ../../../CHANGELOG.md:3644
  5056. msgid "2020-04-23"
  5057. msgstr ""
  5058. #: ../../../CHANGELOG.md:3646
  5059. #: ../../../CHANGELOG.md:3877
  5060. msgid "Slack bridging support"
  5061. msgstr ""
  5062. #: ../../../CHANGELOG.md:3648
  5063. msgid "Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the playbook now supports bridging to [Slack](https://slack.com) via the [mx-puppet-slack](https://github.com/Sorunome/mx-puppet-slack) bridge."
  5064. msgstr ""
  5065. #: ../../../CHANGELOG.md:3650
  5066. msgid "See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-bridge-mx-puppet-slack.md) documentation page for getting started."
  5067. msgstr ""
  5068. #: ../../../CHANGELOG.md:3653
  5069. msgid "2020-04-09"
  5070. msgstr ""
  5071. #: ../../../CHANGELOG.md:3655
  5072. msgid "Skype bridging support"
  5073. msgstr ""
  5074. #: ../../../CHANGELOG.md:3657
  5075. msgid "Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the playbook now supports bridging to [Skype](https://www.skype.com) via the [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge."
  5076. msgstr ""
  5077. #: ../../../CHANGELOG.md:3659
  5078. msgid "See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md) documentation page for getting started."
  5079. msgstr ""
  5080. #: ../../../CHANGELOG.md:3662
  5081. msgid "2020-04-05"
  5082. msgstr ""
  5083. #: ../../../CHANGELOG.md:3664
  5084. msgid "Private Jitsi support"
  5085. msgstr ""
  5086. #: ../../../CHANGELOG.md:3666
  5087. msgid "The [Jitsi support](#jitsi-support) we had landed a few weeks ago was working well, but it was always open to the whole world."
  5088. msgstr ""
  5089. #: ../../../CHANGELOG.md:3668
  5090. msgid "Running such an open instance is not desirable to most people, so [teutat3s](https://github.com/teutat3s) has contributed support for making Jitsi use authentication."
  5091. msgstr ""
  5092. #: ../../../CHANGELOG.md:3670
  5093. msgid "To make your Jitsi server more private, see the [configure internal Jitsi authentication and guests mode](docs/configuring-playbook-jitsi.md#optional-configure-internal-jitsi-authentication-and-guests-mode) section in our Jitsi documentation."
  5094. msgstr ""
  5095. #: ../../../CHANGELOG.md:3673
  5096. msgid "2020-04-03"
  5097. msgstr ""
  5098. #: ../../../CHANGELOG.md:3675
  5099. msgid "(Potential Backward Compatibility Break) ma1sd replaces mxisd"
  5100. msgstr ""
  5101. #: ../../../CHANGELOG.md:3677
  5102. msgid "Thanks to [Marcel Partap](https://github.com/eMPee584)'s efforts, the [mxisd](https://github.com/kamax-io/mxisd) identity server, which has been deprecated for a long time, has finally been replaced by [ma1sd](https://github.com/ma1uta/ma1sd), a compatible fork."
  5103. msgstr ""
  5104. #: ../../../CHANGELOG.md:3679
  5105. msgid "**If you're using the default playbook configuration**, you don't need to do anything — your mxisd installation will be replaced with ma1sd and all existing data will be migrated automatically the next time you run the playbook."
  5106. msgstr ""
  5107. #: ../../../CHANGELOG.md:3681
  5108. msgid "**If you're doing something more special** (defining custom `matrix_mxisd_*` variables), the playbook will ask you to rename them to `matrix_ma1sd_*`. You're also encouraged to test that ma1sd works well for such a more custom setup."
  5109. msgstr ""
  5110. #: ../../../CHANGELOG.md:3684
  5111. msgid "2020-03-29"
  5112. msgstr ""
  5113. #: ../../../CHANGELOG.md:3686
  5114. msgid "Archlinux support"
  5115. msgstr ""
  5116. #: ../../../CHANGELOG.md:3688
  5117. msgid "Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts, the playbook now supports installing to an [Archlinux](https://www.archlinux.org/) server."
  5118. msgstr ""
  5119. #: ../../../CHANGELOG.md:3691
  5120. msgid "2020-03-24"
  5121. msgstr ""
  5122. #: ../../../CHANGELOG.md:3693
  5123. msgid "Jitsi support"
  5124. msgstr ""
  5125. #: ../../../CHANGELOG.md:3695
  5126. msgid "The playbook can now (optionally) install the [Jitsi](https://jitsi.org/) video-conferencing platform and integrate it with [Riot](docs/configuring-playbook-riot-web.md)."
  5127. msgstr ""
  5128. #: ../../../CHANGELOG.md:3697
  5129. msgid "See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to get started."
  5130. msgstr ""
  5131. #: ../../../CHANGELOG.md:3700
  5132. msgid "2020-03-15"
  5133. msgstr ""
  5134. #: ../../../CHANGELOG.md:3702
  5135. msgid "Raspberry Pi support"
  5136. msgstr ""
  5137. #: ../../../CHANGELOG.md:3704
  5138. msgid "Thanks to [Gergely Horváth](https://github.com/hooger)'s effort, the playbook supports installing to a Raspberry Pi server, for at least some of the services."
  5139. msgstr ""
  5140. #: ../../../CHANGELOG.md:3706
  5141. msgid "Since most ready-made container images do not support that architecture, we achieve this by building images locally on the device itself. See our [Self-building documentation page](docs/self-building.md) for how to get started."
  5142. msgstr ""
  5143. #: ../../../CHANGELOG.md:3709
  5144. msgid "2020-02-26"
  5145. msgstr ""
  5146. #: ../../../CHANGELOG.md:3711
  5147. msgid "Riot-web themes are here"
  5148. msgstr ""
  5149. #: ../../../CHANGELOG.md:3713
  5150. msgid "The playbook now makes it easy to install custom riot-web themes."
  5151. msgstr ""
  5152. #: ../../../CHANGELOG.md:3715
  5153. msgid "To learn more, take a look at our [riot-web documentation on Themes](docs/configuring-playbook-riot-web.md#themes)."
  5154. msgstr ""
  5155. #: ../../../CHANGELOG.md:3718
  5156. msgid "2020-02-24"
  5157. msgstr ""
  5158. #: ../../../CHANGELOG.md:3720
  5159. msgid "Customize the server name in Riot's login page"
  5160. msgstr ""
  5161. #: ../../../CHANGELOG.md:3722
  5162. msgid "You can now customize the server name string that Riot-web displays in its login page."
  5163. msgstr ""
  5164. #: ../../../CHANGELOG.md:3724
  5165. msgid "These playbook variables, with these default values, have been added:"
  5166. msgstr ""
  5167. #: ../../../CHANGELOG.md:3730
  5168. msgid "The login page previously said \"Sign in to your Matrix account on matrix.example.org\" (the homeserver's domain name). It will now say \"Sign in … on example.org\" (the server name) by default, or \"Sign in … on Our Server\" if you set the variable to \"Our Server\"."
  5169. msgstr ""
  5170. #: ../../../CHANGELOG.md:3732
  5171. msgid "To support this, the config.json template is changed to use the configuration key `default_server_config` for setting the default HS/IS, and the new configuration key `server_name` is added in there."
  5172. msgstr ""
  5173. #: ../../../CHANGELOG.md:3735
  5174. msgid "2020-01-30"
  5175. msgstr ""
  5176. #: ../../../CHANGELOG.md:3737
  5177. msgid "Disabling TLSv1.1"
  5178. msgstr ""
  5179. #: ../../../CHANGELOG.md:3739
  5180. msgid "To improve security, we've removed TLSv1.1 support from our default matrix-nginx-proxy configuration."
  5181. msgstr ""
  5182. #: ../../../CHANGELOG.md:3741
  5183. msgid "If you need to support old clients, you can re-enable it with the following configuration: `matrix_nginx_proxy_ssl_protocols: \"TLSv1.1 TLSv1.2 TLSv1.3\"`"
  5184. msgstr ""
  5185. #: ../../../CHANGELOG.md:3744
  5186. msgid "2020-01-21"
  5187. msgstr ""
  5188. #: ../../../CHANGELOG.md:3746
  5189. msgid "Postgres collation changes (action required!)"
  5190. msgstr ""
  5191. #: ../../../CHANGELOG.md:3748
  5192. msgid "By default, we've been using a UTF-8 collation for Postgres. This is known to cause Synapse some troubles (see the [relevant issue](https://github.com/matrix-org/synapse/issues/6722)) on systems that use [glibc](https://www.gnu.org/software/libc/). We run Postgres in an [Alpine Linux](https://alpinelinux.org/) container (which uses [musl](https://www.musl-libc.org/), and not glibc), so our users are likely not affected by the index corruption problem observed by others."
  5193. msgstr ""
  5194. #: ../../../CHANGELOG.md:3750
  5195. msgid "Still, we might become affected in the future. In any case, it's imminent that Synapse will complain about databases which do not use a C collation."
  5196. msgstr ""
  5197. #: ../../../CHANGELOG.md:3752
  5198. msgid "To avoid future problems, we recommend that you run the following command:"
  5199. msgstr ""
  5200. #: ../../../CHANGELOG.md:3758
  5201. msgid "It forces a [Postgres database upgrade](docs/maintenance-postgres.md#upgrading-postgresql), which would recreate your Postgres database using the proper (`C`) collation. If you are low on disk space, or run into trouble, refer to the Postgres database upgrade documentation page."
  5202. msgstr ""
  5203. #: ../../../CHANGELOG.md:3761
  5204. msgid "2020-01-14"
  5205. msgstr ""
  5206. #: ../../../CHANGELOG.md:3763
  5207. msgid "Added support for Appservice Webhooks"
  5208. msgstr ""
  5209. #: ../../../CHANGELOG.md:3765
  5210. msgid "Thanks to a contribution from [Björn Marten](https://github.com/tripleawwy) from [netresearch](https://www.netresearch.de/), the playbook can now install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks."
  5211. msgstr ""
  5212. #: ../../../CHANGELOG.md:3767
  5213. msgid "Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-playbook-bridge-appservice-webhooks.md)."
  5214. msgstr ""
  5215. #: ../../../CHANGELOG.md:3770
  5216. msgid "2020-01-12"
  5217. msgstr ""
  5218. #: ../../../CHANGELOG.md:3772
  5219. msgid "Added support for automatic Double Puppeting for all Mautrix bridges"
  5220. msgstr ""
  5221. #: ../../../CHANGELOG.md:3774
  5222. msgid "Double Puppeting can now be easily enabled for all Mautrix bridges supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)."
  5223. msgstr ""
  5224. #: ../../../CHANGELOG.md:3776
  5225. msgid "This is possible due to those bridges' integration with [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) — yet another component that this playbook can install for you."
  5226. msgstr ""
  5227. #: ../../../CHANGELOG.md:3778
  5228. msgid "To get started, following the playbook's documentation for the bridge you'd like to configure."
  5229. msgstr ""
  5230. #: ../../../CHANGELOG.md:3781
  5231. msgid "2019-12-06"
  5232. msgstr ""
  5233. #: ../../../CHANGELOG.md:3783
  5234. msgid "Added support for an alternative method for using another webserver"
  5235. msgstr ""
  5236. #: ../../../CHANGELOG.md:3785
  5237. msgid "We have added support for making `matrix-nginx-proxy` not being so invasive, so that it would be easier to [use your own webserver](docs/configuring-playbook-own-webserver.md)."
  5238. msgstr ""
  5239. #: ../../../CHANGELOG.md:3787
  5240. msgid "The documentation has been updated with a **Method 2**, which might make \"own webserver\" setup easier in some cases (such as [reverse-proxying using Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/296))."
  5241. msgstr ""
  5242. #: ../../../CHANGELOG.md:3789
  5243. msgid "**Existing users** are not affected by this and **don't need to change anything**. The defaults are still the same (`matrix-nginx-proxy` obtaining SSL certificates and doing everything for you automatically)."
  5244. msgstr ""
  5245. #: ../../../CHANGELOG.md:3792
  5246. msgid "2019-11-10"
  5247. msgstr ""
  5248. #: ../../../CHANGELOG.md:3794
  5249. msgid "Tightened security around room directory publishing"
  5250. msgstr ""
  5251. #: ../../../CHANGELOG.md:3796
  5252. msgid "As per this [advisory blog post](https://matrix.org/blog/2019/11/09/avoiding-unwelcome-visitors-on-private-matrix-servers), we've decided to change the default publishing rules for the Matrix room directory."
  5253. msgstr ""
  5254. #: ../../../CHANGELOG.md:3798
  5255. msgid "Our general goal is to favor privacy and security when running personal (family & friends) and corporate homeservers. Both of these likely benefit from having a more secure default of **not showing the room directory without authentication** and **not publishing the room directory over federation**."
  5256. msgstr ""
  5257. #: ../../../CHANGELOG.md:3800
  5258. msgid "As with anything else, these new defaults can be overridden by changing the `matrix_synapse_allow_public_rooms_without_auth` and `matrix_synapse_allow_public_rooms_over_federation` variables, respectively."
  5259. msgstr ""
  5260. #: ../../../CHANGELOG.md:3803
  5261. msgid "2019-10-05"
  5262. msgstr ""
  5263. #: ../../../CHANGELOG.md:3805
  5264. msgid "Improved Postgres upgrading/importing"
  5265. msgstr ""
  5266. #: ../../../CHANGELOG.md:3807
  5267. msgid "Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) and [importing](docs/importing-postgres.md) have been improved to add support for multiple databases and roles."
  5268. msgstr ""
  5269. #: ../../../CHANGELOG.md:3809
  5270. msgid "Previously, the playbook would only take care of the `homeserver` database and `synapse` user. We now back up and restore all databases and users on the Postgres server."
  5271. msgstr ""
  5272. #: ../../../CHANGELOG.md:3811
  5273. msgid "For now, the playbook only uses that one database (`homeserver`) and that one single user (`synapse`), so it's all the same. However, in the future, additional components besides Synapse may also make use the Postgres database server. One such example is the [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge, which strongly encourages use of Postgres in its v1.0 release. We are yet to upgrade to it."
  5274. msgstr ""
  5275. #: ../../../CHANGELOG.md:3813
  5276. msgid "Additionally, Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) now uses gzipped dump files by default, to minimize disk space usage."
  5277. msgstr ""
  5278. #: ../../../CHANGELOG.md:3816
  5279. msgid "2019-10-04"
  5280. msgstr ""
  5281. #: ../../../CHANGELOG.md:3818
  5282. msgid "Postgres 12 support"
  5283. msgstr ""
  5284. #: ../../../CHANGELOG.md:3820
  5285. msgid "The playbook now installs [Postgres 12](https://www.postgresql.org/about/news/1976/) by default."
  5286. msgstr ""
  5287. #: ../../../CHANGELOG.md:3822
  5288. msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x, 10.x or 11.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)."
  5289. msgstr ""
  5290. #: ../../../CHANGELOG.md:3825
  5291. msgid "2019-10-03"
  5292. msgstr ""
  5293. #: ../../../CHANGELOG.md:3827
  5294. msgid "Synapse 1.4.0"
  5295. msgstr ""
  5296. #: ../../../CHANGELOG.md:3829
  5297. msgid "Synapse 1.4.0 [is out](https://matrix.org/blog/2019/10/03/synapse-1-4-0-released) with lots of changes related to privacy."
  5298. msgstr ""
  5299. #: ../../../CHANGELOG.md:3831
  5300. msgid "Its new defaults (which we adopt as well) mean that certain old data will automatically get purged after a certain number of days. 1.4.0 automatically garbage collects redacted messages (defaults to 7 days) and removes unused IP and user agent information stored in the user_ips table (defaults to 30 days). If you'd like to preserve this data, we encourage you to look at the `redaction_retention_period` and `user_ips_max_age` options (controllable by the `matrix_synapse_redaction_retention_period` and `matrix_synapse_user_ips_max_age` playbook variables, respectively) before doing the upgrade. If you'd like to keep data indefinitely, set these variables to `null` (e.g. `matrix_synapse_redaction_retention_period: ~`)."
  5301. msgstr ""
  5302. #: ../../../CHANGELOG.md:3833
  5303. msgid "From now on the `trusted_key_servers` setting for Synapse is configurable. It still defaults to `matrix.org` just like it always has, but in a more explicit way now. If you'd like to use another trusted key server, adjust the `matrix_synapse_trusted_key_servers` playbook variable."
  5304. msgstr ""
  5305. #: ../../../CHANGELOG.md:3835
  5306. msgid "Synapse 1.4.0 also changes lots of things related to identity server integration. Because Synapse will now by default be responsible for validating email addresses for user accounts, running without an identity server looks more feasible. We still [have concerns](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/275/files#r331104117) over disabling the identity server by default, so for now it remains enabled."
  5307. msgstr ""
  5308. #: ../../../CHANGELOG.md:3838
  5309. msgid "2019-09-09"
  5310. msgstr ""
  5311. #: ../../../CHANGELOG.md:3840
  5312. msgid "Synapse Simple Antispam support"
  5313. msgstr ""
  5314. #: ../../../CHANGELOG.md:3842
  5315. msgid "There have been lots of invite-spam attacks lately and [Travis](https://github.com/t2bot) has created a Synapse module ([synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam)) to let people protect themselves."
  5316. msgstr ""
  5317. #: ../../../CHANGELOG.md:3844
  5318. msgid "From now on, you can easily install and configure this spam checker module through the playbook."
  5319. msgstr ""
  5320. #: ../../../CHANGELOG.md:3846
  5321. msgid "Learn more in [Setting up Synapse Simple Antispam](docs/configuring-playbook-synapse-simple-antispam.md)."
  5322. msgstr ""
  5323. #: ../../../CHANGELOG.md:3849
  5324. msgid "2019-08-25"
  5325. msgstr ""
  5326. #: ../../../CHANGELOG.md:3851
  5327. msgid "Extensible Riot-web configuration"
  5328. msgstr ""
  5329. #: ../../../CHANGELOG.md:3853
  5330. msgid "Similarly to [Extensible Synapse configuration](#extensible-synapse-configuration) (below), Riot-web configuration is also extensible now."
  5331. msgstr ""
  5332. #: ../../../CHANGELOG.md:3855
  5333. msgid "From now on, you can extend/override Riot-web's configuration by making use of the `matrix_riot_web_configuration_extension_json` variable. This should be enough for most customization needs."
  5334. msgstr ""
  5335. #: ../../../CHANGELOG.md:3857
  5336. msgid "If you need even more power, you can now also take full control and override `matrix_riot_web_configuration_default` (or `matrix_riot_web_configuration`) directly."
  5337. msgstr ""
  5338. #: ../../../CHANGELOG.md:3859
  5339. msgid "Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-web.md)."
  5340. msgstr ""
  5341. #: ../../../CHANGELOG.md:3862
  5342. msgid "2019-08-22"
  5343. msgstr ""
  5344. #: ../../../CHANGELOG.md:3864
  5345. msgid "Extensible Synapse configuration"
  5346. msgstr ""
  5347. #: ../../../CHANGELOG.md:3866
  5348. msgid "Previously, we had to create custom Ansible variables for each and every Synapse setting. This lead to too much effort (and configuration ugliness) to all of Synapse's settings, so naturally, not all features of Synapse could be controlled through the playbook."
  5349. msgstr ""
  5350. #: ../../../CHANGELOG.md:3868
  5351. msgid "From now on, you can extend/override the Synapse server's configuration by making use of the `matrix_synapse_configuration_extension_yaml` variable. This should be enough for most customization needs."
  5352. msgstr ""
  5353. #: ../../../CHANGELOG.md:3870
  5354. msgid "If you need even more power, you can now also take full control and override `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`) directly."
  5355. msgstr ""
  5356. #: ../../../CHANGELOG.md:3872
  5357. msgid "Learn more here in [Configuring Synapse](docs/configuring-playbook-synapse.md)."
  5358. msgstr ""
  5359. #: ../../../CHANGELOG.md:3875
  5360. msgid "2019-08-21"
  5361. msgstr ""
  5362. #: ../../../CHANGELOG.md:3879
  5363. msgid "Thanks to the [great work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/205) of [kingoftheconnors](https://github.com/kingoftheconnors) and [Stuart Mumford (Cadair)](https://github.com/Cadair), the playbook now supports bridging to [Slack](https://slack.com) via the [appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge."
  5364. msgstr ""
  5365. #: ../../../CHANGELOG.md:3881
  5366. msgid "Additional details are available in [Setting up Appservice Slack bridging](docs/configuring-playbook-bridge-appservice-slack.md)."
  5367. msgstr ""
  5368. #: ../../../CHANGELOG.md:3883
  5369. msgid "Google Hangouts bridging support"
  5370. msgstr ""
  5371. #: ../../../CHANGELOG.md:3885
  5372. msgid "Thanks to the [great work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/251) of [Eduardo Beltrame (Munfred)](https://github.com/Munfred) and [Robbie D (microchipster)](https://github.com/microchipster), the playbook now supports bridging to [Google Hangouts](https://hangouts.google.com/) via the [mautrix-hangouts](https://mau.dev/tulir/mautrix-hangouts) bridge."
  5373. msgstr ""
  5374. #: ../../../CHANGELOG.md:3887
  5375. msgid "Additional details are available in [Setting up Mautrix Hangouts bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)."
  5376. msgstr ""
  5377. #: ../../../CHANGELOG.md:3890
  5378. msgid "2019-08-05"
  5379. msgstr ""
  5380. #: ../../../CHANGELOG.md:3892
  5381. msgid "Email2Matrix support"
  5382. msgstr ""
  5383. #: ../../../CHANGELOG.md:3894
  5384. msgid "Support for [Email2Matrix](https://github.com/devture/email2matrix) has been added."
  5385. msgstr ""
  5386. #: ../../../CHANGELOG.md:3896
  5387. msgid "It's an optional feature that you can enable via the playbook."
  5388. msgstr ""
  5389. #: ../../../CHANGELOG.md:3898
  5390. msgid "To learn more, see the [playbook's documentation on Email2Matrix](./docs/configuring-playbook-email2matrix.md)."
  5391. msgstr ""
  5392. #: ../../../CHANGELOG.md:3901
  5393. msgid "2019-08-03"
  5394. msgstr ""
  5395. #: ../../../CHANGELOG.md:3903
  5396. msgid "Synapse logging level has been reduced to WARNING"
  5397. msgstr ""
  5398. #: ../../../CHANGELOG.md:3905
  5399. msgid "After [some discussion in our support room](https://matrix.to/#/!PukFFdIcHgtaaHZflT:devture.com/$156476852524179TBeKy:matrix.org?via=devture.com&via=matrix.org&via=librem.one), we've decided to change the default logging level for Synapse from `INFO` to `WARNING`."
  5400. msgstr ""
  5401. #: ../../../CHANGELOG.md:3907
  5402. msgid "This greatly reduces the number of log messages that are being logged, leading to:"
  5403. msgstr ""
  5404. #: ../../../CHANGELOG.md:3909
  5405. msgid "much less disk space dedicated to Synapse and thus, logs kept for longer"
  5406. msgstr ""
  5407. #: ../../../CHANGELOG.md:3910
  5408. msgid "easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages, as they're not longer buried in thousands of non-important `INFO` messages"
  5409. msgstr ""
  5410. #: ../../../CHANGELOG.md:3912
  5411. msgid "If you'd like to track down an issue, you [can always increase the logging level as described here](./docs/maintenance-and-troubleshooting.md#increasing-synapse-logging)."
  5412. msgstr ""
  5413. #: ../../../CHANGELOG.md:3915
  5414. msgid "2019-07-08"
  5415. msgstr ""
  5416. #: ../../../CHANGELOG.md:3917
  5417. msgid "Synapse Maintenance docs and synapse-janitor support are available"
  5418. msgstr ""
  5419. #: ../../../CHANGELOG.md:3919
  5420. msgid "The playbook can now help you with Synapse's maintenance."
  5421. msgstr ""
  5422. #: ../../../CHANGELOG.md:3921
  5423. msgid "There's a new documentation page about [Synapse maintenance](./docs/maintenance-synapse.md) and another section on [Postgres vacuuming](./docs/maintenance-postgres.md#vacuuming-postgresql)."
  5424. msgstr ""
  5425. #: ../../../CHANGELOG.md:3923
  5426. msgid "Among other things, if your Postgres database has grown significantly over time, you may wish to [ask the playbook to purge unused data with synapse-janitor](./docs/maintenance-synapse.md#purging-unused-data-with-synapse-janitor) for you."
  5427. msgstr ""
  5428. #: ../../../CHANGELOG.md:3925
  5429. msgid "(BC Break) Rename run control variables"
  5430. msgstr ""
  5431. #: ../../../CHANGELOG.md:3927
  5432. msgid "Some internal playbook control variables have been renamed."
  5433. msgstr ""
  5434. #: ../../../CHANGELOG.md:3929
  5435. msgid "This change **only affects people who run this playbook's roles from another playbook**. If you're using this playbook as-is, you're not affected and don't need to do anything."
  5436. msgstr ""
  5437. #: ../../../CHANGELOG.md:3931
  5438. msgid "The following variables have been renamed:"
  5439. msgstr ""
  5440. #: ../../../CHANGELOG.md:3933
  5441. msgid "from `run_import_postgres` to `run_postgres_import`"
  5442. msgstr ""
  5443. #: ../../../CHANGELOG.md:3934
  5444. msgid "from `run_import_sqlite_db` to `run_postgres_import_sqlite_db`"
  5445. msgstr ""
  5446. #: ../../../CHANGELOG.md:3935
  5447. msgid "from `run_upgrade_postgres` to `run_postgres_upgrade`"
  5448. msgstr ""
  5449. #: ../../../CHANGELOG.md:3936
  5450. msgid "from `run_import_media_store` to `run_synapse_import_media_store`"
  5451. msgstr ""
  5452. #: ../../../CHANGELOG.md:3937
  5453. msgid "from `run_register_user` to `run_synapse_register_user`"
  5454. msgstr ""
  5455. #: ../../../CHANGELOG.md:3938
  5456. msgid "from `run_update_user_password` to `run_synapse_update_user_password`"
  5457. msgstr ""
  5458. #: ../../../CHANGELOG.md:3941
  5459. msgid "2019-07-04"
  5460. msgstr ""
  5461. #: ../../../CHANGELOG.md:3943
  5462. msgid "Synapse no longer logs to text files"
  5463. msgstr ""
  5464. #: ../../../CHANGELOG.md:3945
  5465. msgid "Following what the official Synapse Docker image is doing ([#5565](https://github.com/matrix-org/synapse/pull/5565)) and what we've been doing for mostly everything installed by this playbook, **Synapse no longer logs to text files** (`/matrix/synapse/run/homeserver.log*`)."
  5466. msgstr ""
  5467. #: ../../../CHANGELOG.md:3947
  5468. msgid "From now on, Synapse would only log to console, which goes to systemd's journald. To see Synapse's logs, execute: `journalctl -fu matrix-synapse`"
  5469. msgstr ""
  5470. #: ../../../CHANGELOG.md:3949
  5471. msgid "Because of this, the following variables have become obsolete and were removed:"
  5472. msgstr ""
  5473. #: ../../../CHANGELOG.md:3951
  5474. msgid "`matrix_synapse_max_log_file_size_mb`"
  5475. msgstr ""
  5476. #: ../../../CHANGELOG.md:3952
  5477. msgid "`matrix_synapse_max_log_files_count`"
  5478. msgstr ""
  5479. #: ../../../CHANGELOG.md:3954
  5480. msgid "To prevent confusion, it'd be better if you delete all old files manually after you've upgraded (`rm -f /matrix/synapse/run/homeserver.log*`)."
  5481. msgstr ""
  5482. #: ../../../CHANGELOG.md:3956
  5483. msgid "Because Synapse is incredibly chatty when it comes to logging (here's [one such issue](https://github.com/matrix-org/synapse/issues/4751) describing the problem), if you're running an ancient distribution (like CentOS 7.0), be advised that systemd's journald default logging restrictions may not be high enough to capture all log messages generated by Synapse. This is especially true if you've got a busy (Synapse) server. We advise that you manually add `RateLimitInterval=0` and `RateLimitBurst=0` under `[Storage]` in the `/etc/systemd/journald.conf` file, followed by restarting the logging service (`systemctl restart systemd-journald`)."
  5484. msgstr ""
  5485. #: ../../../CHANGELOG.md:3959
  5486. msgid "2019-06-27"
  5487. msgstr ""
  5488. #: ../../../CHANGELOG.md:3961
  5489. msgid "(BC Break) Discord bridge configuration is now entirely managed by the playbook"
  5490. msgstr ""
  5491. #: ../../../CHANGELOG.md:3963
  5492. msgid "Until now, the `config.yaml` file for the [Discord bridge](docs/configuring-playbook-bridge-appservice-discord.md) was managed by the playbook, but the `registration.yaml` file was not."
  5493. msgstr ""
  5494. #: ../../../CHANGELOG.md:3965
  5495. msgid "From now on, the playbook will keep both configuration files sync for you."
  5496. msgstr ""
  5497. #: ../../../CHANGELOG.md:3967
  5498. msgid "This means that if you were making manual changes to the `/matrix/appservice-discord/discord-registration.yaml` configuration file, those would be lost the next time you run the playbook."
  5499. msgstr ""
  5500. #: ../../../CHANGELOG.md:3969
  5501. msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-discord/config`)."
  5502. msgstr ""
  5503. #: ../../../CHANGELOG.md:3971
  5504. msgid "Likewise, data is now also stored in a subdirectory (`/matrix/appservice-discord/data`). When you run the playbook with an existing database file (`/matrix/appservice-discord/discord.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
  5505. msgstr ""
  5506. #: ../../../CHANGELOG.md:3973
  5507. msgid "The main directory (`/matrix/appservice-discord`) may contain some leftover files (`user-store.db`, `room-store.db`, `config.yaml`, `discord-registration.yaml`, `invite_link`). These are no longer necessary and can be deleted manually."
  5508. msgstr ""
  5509. #: ../../../CHANGELOG.md:3975
  5510. msgid "We're now following the default sample configuration for the Discord bridge. If you need to override some values, define them in `matrix_appservice_discord_configuration_extension_yaml`."
  5511. msgstr ""
  5512. #: ../../../CHANGELOG.md:3978
  5513. msgid "2019-06-24"
  5514. msgstr ""
  5515. #: ../../../CHANGELOG.md:3980
  5516. msgid "(BC Break) WhatsApp bridge configuration is now entirely managed by the playbook"
  5517. msgstr ""
  5518. #: ../../../CHANGELOG.md:3982
  5519. msgid "Until now, configuration files for the [WhatsApp bridge](docs/configuring-playbook-bridge-mautrix-whatsapp.md) were created by the playbook initially, but never modified later on."
  5520. msgstr ""
  5521. #: ../../../CHANGELOG.md:3984
  5522. #: ../../../CHANGELOG.md:4001
  5523. #: ../../../CHANGELOG.md:4020
  5524. #: ../../../CHANGELOG.md:4059
  5525. msgid "From now on, the playbook will keep the configuration in sync for you."
  5526. msgstr ""
  5527. #: ../../../CHANGELOG.md:3986
  5528. msgid "This means that if you were making manual changes to the `/matrix/mautrix-whatsapp/config.yaml` or `/matrix/mautrix-whatsapp/registration.yaml` configuration files, those would be lost the next time you run the playbook."
  5529. msgstr ""
  5530. #: ../../../CHANGELOG.md:3988
  5531. msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-whatsapp/config`), so your old configuration remains in the base directory (`/matrix/mautrix-whatsapp`). You need to migrate any manual changes over to the new `matrix_mautrix_whatsapp_configuration_extension_yaml` variable, so that the playbook would apply them for you."
  5532. msgstr ""
  5533. #: ../../../CHANGELOG.md:3990
  5534. msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-whatsapp/data`). When you run the playbook with an existing database file (`/matrix/mautrix-whatsapp/mautrix-whatsapp.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
  5535. msgstr ""
  5536. #: ../../../CHANGELOG.md:3992
  5537. msgid "We're now following the default configuration for the WhatsApp bridge."
  5538. msgstr ""
  5539. #: ../../../CHANGELOG.md:3995
  5540. msgid "2019-06-20"
  5541. msgstr ""
  5542. #: ../../../CHANGELOG.md:3997
  5543. msgid "(BC Break) IRC bridge configuration is now entirely managed by the playbook"
  5544. msgstr ""
  5545. #: ../../../CHANGELOG.md:3999
  5546. msgid "Until now, configuration files for the [IRC bridge](docs/configuring-playbook-bridge-appservice-irc.md) were created by the playbook initially, but never modified later on."
  5547. msgstr ""
  5548. #: ../../../CHANGELOG.md:4003
  5549. msgid "This means that if you were making manual changes to the `/matrix/appservice-irc/config.yaml` or `/matrix/appservice-irc/registration.yaml` configuration files, those would be lost the next time you run the playbook."
  5550. msgstr ""
  5551. #: ../../../CHANGELOG.md:4005
  5552. msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-irc/config`), so your old configuration remains in the base directory (`/matrix/appservice-irc`)."
  5553. msgstr ""
  5554. #: ../../../CHANGELOG.md:4007
  5555. msgid "Previously, we asked people to configure bridged IRC servers by extending the bridge configuration (`matrix_appservice_irc_configuration_extension_yaml`). While this is still possible and will continue working forever, **we now recommend defining IRC servers in the easier to use `matrix_appservice_irc_ircService_servers` variable**. See [our IRC bridge documentation page](docs/configuring-playbook-bridge-appservice-irc.md) for an example."
  5556. msgstr ""
  5557. #: ../../../CHANGELOG.md:4009
  5558. msgid "If you decide to continue using `matrix_appservice_irc_configuration_extension_yaml`, you might be interested to know that `ircService.databaseUri` and a few other keys now have default values in the base configuration (`matrix_appservice_irc_configuration_yaml`). You may wish to stop redefining those keys, unless you really intend to override them. You most likely only need to override `ircService.servers`."
  5559. msgstr ""
  5560. #: ../../../CHANGELOG.md:4011
  5561. msgid "Bridge data (`passkey.pem` and database files) is now also stored in a subdirectory (`/matrix/appservice-irc/data`). When you run the playbook with an existing `/matrix/appservice-irc/passkey.pem` file, the playbook will stop the bridge and relocate the passkey and database files (`rooms.db` and `users.db`) to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
  5562. msgstr ""
  5563. #: ../../../CHANGELOG.md:4014
  5564. msgid "2019-06-15"
  5565. msgstr ""
  5566. #: ../../../CHANGELOG.md:4016
  5567. msgid "(BC Break) Telegram bridge configuration is now entirely managed by the playbook"
  5568. msgstr ""
  5569. #: ../../../CHANGELOG.md:4018
  5570. msgid "Until now, configuration files for the [Telegram bridge](docs/configuring-playbook-bridge-mautrix-telegram.md) were created by the playbook initially, but never modified later on."
  5571. msgstr ""
  5572. #: ../../../CHANGELOG.md:4022
  5573. msgid "This means that if you were making manual changes to the `/matrix/mautrix-telegram/config.yaml` or `/matrix/mautrix-telegram/registration.yaml` configuration files, those would be lost the next time you run the playbook."
  5574. msgstr ""
  5575. #: ../../../CHANGELOG.md:4024
  5576. msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-telegram/config`), so your old configuration remains in the base directory (`/matrix/mautrix-telegram`). You need to migrate any manual changes over to the new `matrix_mautrix_telegram_configuration_extension_yaml` variable, so that the playbook would apply them for you."
  5577. msgstr ""
  5578. #: ../../../CHANGELOG.md:4026
  5579. msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-telegram/data`). When you run the playbook with an existing database file (`/matrix/mautrix-telegram/mautrix-telegram.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
  5580. msgstr ""
  5581. #: ../../../CHANGELOG.md:4028
  5582. msgid "Also, we're now following the default configuration for the Telegram bridge, so some default configuration values are different:"
  5583. msgstr ""
  5584. #: ../../../CHANGELOG.md:4030
  5585. msgid "`edits_as_replies` (used to be `false`, now `true`) — previously replies were not sent over to Matrix at all; ow they are sent over as a reply to the original message"
  5586. msgstr ""
  5587. #: ../../../CHANGELOG.md:4031
  5588. msgid "`inline_images` (used to be `true`, now `false`) — this has to do with captioned images. Inline-image (included caption) are said to exhibit troubles on Riot iOS. When `false`, the caption arrives on the Matrix side as a separate message."
  5589. msgstr ""
  5590. #: ../../../CHANGELOG.md:4032
  5591. msgid "`authless_portals` (used to be `false`, now `true`) — creating portals from the Telegram side is now possible"
  5592. msgstr ""
  5593. #: ../../../CHANGELOG.md:4033
  5594. msgid "`whitelist_group_admins` (used to be `false`, now `true`) — allows Telegram group admins to use the bot commands"
  5595. msgstr ""
  5596. #: ../../../CHANGELOG.md:4035
  5597. msgid "If the new values are not to your liking, use `matrix_mautrix_telegram_configuration_extension_yaml` to specify an override (refer to `matrix_mautrix_telegram_configuration_yaml` to figure out which variable goes where)."
  5598. msgstr ""
  5599. #: ../../../CHANGELOG.md:4038
  5600. msgid "2019-06-12"
  5601. msgstr ""
  5602. #: ../../../CHANGELOG.md:4040
  5603. msgid "Synapse v1.0"
  5604. msgstr ""
  5605. #: ../../../CHANGELOG.md:4042
  5606. msgid "With [Synapse v1.0 now available](https://matrix.org/blog/2019/06/11/introducing-matrix-1-0-and-the-matrix-org-foundation) and most people being on at least Synapse v0.99, it's time to remove the `_matrix._tcp` DNS SRV record that we've been keeping for compatibility with old Synapse versions (<= 0.34)."
  5607. msgstr ""
  5608. #: ../../../CHANGELOG.md:4044
  5609. msgid "According to the [Server Discovery specification](https://matrix.org/docs/spec/server_server/r0.1.2.html#server-discovery), it's no harm to keep the DNS SRV record. But since it's not necessary for federating with the larger Matrix network anymore, you should be safe to get rid of it."
  5610. msgstr ""
  5611. #: ../../../CHANGELOG.md:4046
  5612. msgid "**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` DNS SRV records. The latter, **must not** be removed."
  5613. msgstr ""
  5614. #: ../../../CHANGELOG.md:4048
  5615. msgid "For completeness, we must say that using a `_matrix._tcp` [SRV record for Server Delegation](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced) is still valid and useful for certain deployments. It's just that our guide recommends the [`/.well-known/matrix/server` Server Delegation method](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), due to its easier implementation when using this playbook."
  5616. msgstr ""
  5617. #: ../../../CHANGELOG.md:4050
  5618. msgid "Besides this optional/non-urgent DNS change, assuming you're already on Synapse v0.99, upgrading to Synapse v1.0 should be as simple as [re-running the playbook](docs/maintenance-upgrading-services.md)."
  5619. msgstr ""
  5620. #: ../../../CHANGELOG.md:4053
  5621. msgid "2019-06-07"
  5622. msgstr ""
  5623. #: ../../../CHANGELOG.md:4055
  5624. msgid "(BC Break) Facebook bridge configuration is now entirely managed by the playbook"
  5625. msgstr ""
  5626. #: ../../../CHANGELOG.md:4057
  5627. msgid "Until now, configuration files for the [Facebook bridge](docs/configuring-playbook-bridge-mautrix-facebook.md) were created by the playbook initially, but never modified later on."
  5628. msgstr ""
  5629. #: ../../../CHANGELOG.md:4061
  5630. msgid "This means that if you were making manual changes to the `/matrix/mautrix-facebook/config.yaml` or `/matrix/mautrix-facebook/registration.yaml` configuration files, those would be lost the next time you run the playbook."
  5631. msgstr ""
  5632. #: ../../../CHANGELOG.md:4063
  5633. msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-facebook/config`), so your old configuration remains in the base directory (`/matrix/mautrix-facebook`). You need to migrate any manual changes over to the new `matrix_mautrix_facebook_configuration_extension_yaml` variable, so that the playbook would apply them for you."
  5634. msgstr ""
  5635. #: ../../../CHANGELOG.md:4065
  5636. msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-facebook/data`). When you run the playbook with an existing database file (`/matrix/mautrix-facebook/mautrix-facebook.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
  5637. msgstr ""
  5638. #: ../../../CHANGELOG.md:4068
  5639. msgid "2019-05-25"
  5640. msgstr ""
  5641. #: ../../../CHANGELOG.md:4070
  5642. msgid "Support for exposing container ports publicly (not just to the host)"
  5643. msgstr ""
  5644. #: ../../../CHANGELOG.md:4072
  5645. msgid "Until now, various roles supported a `matrix_*_expose_port` variable, which would expose their container's port to the host. This was mostly useful for reverse-proxying manually (in case `matrix-nginx-proxy` was disabled). It could also be used for installing some playbook services (e.g. bridges, etc.) and wiring them to a separate (manual) Matrix setup."
  5646. msgstr ""
  5647. #: ../../../CHANGELOG.md:4074
  5648. msgid "`matrix_*_expose_port` variables were not granular enough — sometimes they would expose one port, other times multiple. They also didn't provide control over **where** to expose (to which port number and to which network interface), because they would usually hardcode something like `127.0.0.1:8080`."
  5649. msgstr ""
  5650. #: ../../../CHANGELOG.md:4076
  5651. msgid "All such variables have been superseded by a better (more flexible) way to do it."
  5652. msgstr ""
  5653. #: ../../../CHANGELOG.md:4078
  5654. msgid "**Most** people (including those not using `matrix-nginx-proxy`), **don't need** to bother with this."
  5655. msgstr ""
  5656. #: ../../../CHANGELOG.md:4080
  5657. msgid "Porting examples follow for people having more customized setups:"
  5658. msgstr ""
  5659. #: ../../../CHANGELOG.md:4082
  5660. msgid "**from** `matrix_synapse_container_expose_client_api_port: true` **to** `matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`"
  5661. msgstr ""
  5662. #: ../../../CHANGELOG.md:4084
  5663. msgid "**from** `matrix_synapse_container_expose_federation_api_port: true` **to** `matrix_synapse_container_federation_api_plain_host_bind_port: '127.0.0.1:8048'` and possibly `matrix_synapse_container_federation_api_tls_host_bind_port: '8448'`"
  5664. msgstr ""
  5665. #: ../../../CHANGELOG.md:4086
  5666. msgid "**from** `matrix_synapse_container_expose_metrics_port: true` **to** `matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`"
  5667. msgstr ""
  5668. #: ../../../CHANGELOG.md:4088
  5669. msgid "**from** `matrix_riot_web_container_expose_port: true` **to** `matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`"
  5670. msgstr ""
  5671. #: ../../../CHANGELOG.md:4090
  5672. msgid "**from** `matrix_mxisd_container_expose_port: true` **to** `matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`"
  5673. msgstr ""
  5674. #: ../../../CHANGELOG.md:4092
  5675. msgid "**from** `matrix_dimension_container_expose_port: true` **to** `matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`"
  5676. msgstr ""
  5677. #: ../../../CHANGELOG.md:4094
  5678. msgid "**from** `matrix_corporal_container_expose_ports: true` **to** `matrix_corporal_container_http_gateway_host_bind_port: '127.0.0.1:41080'` and possibly `matrix_corporal_container_http_api_host_bind_port: '127.0.0.1:41081'`"
  5679. msgstr ""
  5680. #: ../../../CHANGELOG.md:4096
  5681. msgid "**from** `matrix_appservice_irc_container_expose_client_server_api_port: true` **to** `matrix_appservice_irc_container_http_host_bind_port: '127.0.0.1:9999'`"
  5682. msgstr ""
  5683. #: ../../../CHANGELOG.md:4098
  5684. msgid "**from** `matrix_appservice_discord_container_expose_client_server_api_port: true` **to** `matrix_appservice_discord_container_http_host_bind_port: '127.0.0.1:9005'`"
  5685. msgstr ""
  5686. #: ../../../CHANGELOG.md:4100
  5687. msgid "As always, if you forget to remove usage of some outdated variable, the playbook will warn you."
  5688. msgstr ""
  5689. #: ../../../CHANGELOG.md:4103
  5690. msgid "2019-05-23"
  5691. msgstr ""
  5692. #: ../../../CHANGELOG.md:4105
  5693. msgid "(BC Break) Ansible 2.8 compatibility"
  5694. msgstr ""
  5695. #: ../../../CHANGELOG.md:4107
  5696. msgid "Thanks to [@danbob](https://github.com/danbob), the playbook now [supports the new Ansible 2.8](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/187)."
  5697. msgstr ""
  5698. #: ../../../CHANGELOG.md:4109
  5699. msgid "A manual change is required to the `inventory/hosts` file, changing the group name from `matrix-servers` to `matrix_servers` (dash to underscore)."
  5700. msgstr ""
  5701. #: ../../../CHANGELOG.md:4111
  5702. msgid "To avoid doing it manually, run this:"
  5703. msgstr ""
  5704. #: ../../../CHANGELOG.md:4112
  5705. msgid "Linux: `sed -i 's/matrix-servers/matrix_servers/g' inventory/hosts`"
  5706. msgstr ""
  5707. #: ../../../CHANGELOG.md:4113
  5708. msgid "Mac: `sed -i '' 's/matrix-servers/matrix_servers/g' inventory/hosts`"
  5709. msgstr ""
  5710. #: ../../../CHANGELOG.md:4116
  5711. msgid "2019-05-21"
  5712. msgstr ""
  5713. #: ../../../CHANGELOG.md:4118
  5714. msgid "Synapse no longer required"
  5715. msgstr ""
  5716. #: ../../../CHANGELOG.md:4120
  5717. msgid "The playbook no longer insists on installing [Synapse](https://github.com/element-hq/synapse) via the `matrix-synapse` role."
  5718. msgstr ""
  5719. #: ../../../CHANGELOG.md:4122
  5720. msgid "If you would prefer to install Synapse another way and just use the playbook to install other services, it should be possible (`matrix_synapse_enabled: false`)."
  5721. msgstr ""
  5722. #: ../../../CHANGELOG.md:4124
  5723. msgid "Note that it won't necessarily be the best experience, since the playbook wires things to Synapse by default. If you're using your own Synapse instance (especially one not running in a container), you may have to override many variables to point them to the correct place."
  5724. msgstr ""
  5725. #: ../../../CHANGELOG.md:4126
  5726. msgid "Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers."
  5727. msgstr ""
  5728. #: ../../../CHANGELOG.md:4128
  5729. msgid "Bridges are now separate from the Synapse role"
  5730. msgstr ""
  5731. #: ../../../CHANGELOG.md:4130
  5732. msgid "Bridges are no longer part of the `matrix-synapse` role. Each bridge now lives in its own separate role (`roles/custom/matrix-bridge-*`)."
  5733. msgstr ""
  5734. #: ../../../CHANGELOG.md:4132
  5735. msgid "These bridge roles are independent of the `matrix-synapse` role, so it should be possible to use them with a Synapse instance installed another way (not through the playbook)."
  5736. msgstr ""
  5737. #: ../../../CHANGELOG.md:4134
  5738. msgid "Renaming inconsistently-named Synapse variables"
  5739. msgstr ""
  5740. #: ../../../CHANGELOG.md:4136
  5741. msgid "For better consistency, the following variables have been renamed:"
  5742. msgstr ""
  5743. #: ../../../CHANGELOG.md:4138
  5744. msgid "`matrix_enable_room_list_search` was renamed to `matrix_synapse_enable_room_list_search`"
  5745. msgstr ""
  5746. #: ../../../CHANGELOG.md:4139
  5747. msgid "`matrix_alias_creation_rules` was renamed to `matrix_synapse_alias_creation_rules`"
  5748. msgstr ""
  5749. #: ../../../CHANGELOG.md:4140
  5750. msgid "`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was renamed to `matrix_synapse_room_list_publication_rules`"
  5751. msgstr ""
  5752. #: ../../../CHANGELOG.md:4143
  5753. msgid "2019-05-09"
  5754. msgstr ""
  5755. #: ../../../CHANGELOG.md:4145
  5756. msgid "Besides a myriad of bug fixes and minor improvements, here are the more notable (bigger) features we can announce today."
  5757. msgstr ""
  5758. #: ../../../CHANGELOG.md:4147
  5759. msgid "Mautrix Facebook/Messenger bridging support"
  5760. msgstr ""
  5761. #: ../../../CHANGELOG.md:4149
  5762. msgid "The playbook now supports bridging with [Facebook](https://www.facebook.com/) by installing the [mautrix-facebook](https://github.com/tulir/mautrix-facebook) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)."
  5763. msgstr ""
  5764. #: ../../../CHANGELOG.md:4151
  5765. msgid "Additional details are available in [Setting up Mautrix Facebook bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)."
  5766. msgstr ""
  5767. #: ../../../CHANGELOG.md:4153
  5768. msgid "mxisd Registration feature integration"
  5769. msgstr ""
  5770. #: ../../../CHANGELOG.md:4155
  5771. msgid "The playbook can now help you integrate with mxisd's [Registration](https://github.com/kamax-matrix/mxisd/blob/master/docs/features/registration.md) feature."
  5772. msgstr ""
  5773. #: ../../../CHANGELOG.md:4157
  5774. msgid "Learn more in [mxisd-controlled Registration](docs/configuring-playbook-mxisd.md#mxisd-controlled-registration)."
  5775. msgstr ""
  5776. #: ../../../CHANGELOG.md:4160
  5777. msgid "2019-04-16"
  5778. msgstr ""
  5779. #: ../../../CHANGELOG.md:4162
  5780. msgid "Caddy webserver examples"
  5781. msgstr ""
  5782. #: ../../../CHANGELOG.md:4164
  5783. msgid "If you prefer using the [Caddy](https://caddyserver.com/) webserver instead of our own integrated nginx, we now have examples for it in the [`examples/caddy`](examples/caddy) directory"
  5784. msgstr ""
  5785. #: ../../../CHANGELOG.md:4166
  5786. msgid "2019-04-10"
  5787. msgstr ""
  5788. #: ../../../CHANGELOG.md:4168
  5789. msgid "Goofys support for other S3-compatible object stores"
  5790. msgstr ""
  5791. #: ../../../CHANGELOG.md:4170
  5792. msgid "Until now, you could optionally host Synapse's media repository on Amazon S3, but we now also support [using other S3-compatible object stores](docs/configuring-playbook-s3.md),"
  5793. msgstr ""
  5794. #: ../../../CHANGELOG.md:4173
  5795. msgid "2019-04-03"
  5796. msgstr ""
  5797. #: ../../../CHANGELOG.md:4175
  5798. msgid "Ansible >= 2.5 is required"
  5799. msgstr ""
  5800. #: ../../../CHANGELOG.md:4177
  5801. msgid "Due to recent playbook improvements and the fact that the world keeps turning, we're bumping the [version requirement for Ansible](docs/ansible.md#supported-ansible-versions) (2.4 -> 2.5)."
  5802. msgstr ""
  5803. #: ../../../CHANGELOG.md:4179
  5804. msgid "We've also started building our own Docker image of Ansible ([devture/ansible](https://hub.docker.com/r/devture/ansible/)), which is useful for people who can't upgrade their local Ansible installation (see [Using Ansible via Docker](docs/ansible.md#using-ansible-via-docker))."
  5805. msgstr ""
  5806. #: ../../../CHANGELOG.md:4182
  5807. msgid "2019-03-19"
  5808. msgstr ""
  5809. #: ../../../CHANGELOG.md:4184
  5810. msgid "TLS support for coturn"
  5811. msgstr ""
  5812. #: ../../../CHANGELOG.md:4186
  5813. msgid "We've added TLS support to the coturn TURN server installed by the playbook by default. The certificates from the Matrix domain will be used for the coturn server."
  5814. msgstr ""
  5815. #: ../../../CHANGELOG.md:4188
  5816. msgid "This feature is enabled by default for new installations. To make use of TLS support for your existing Matrix server's coturn, make sure to rebuild both coturn and Synapse:"
  5817. msgstr ""
  5818. #: ../../../CHANGELOG.md:4194
  5819. msgid "People who have an extra firewall (besides the iptables firewall, which Docker manages automatically), will need to open these additional firewall ports: `5349/tcp` (TURN over TCP) and `5349/udp` (TURN over UDP)."
  5820. msgstr ""
  5821. #: ../../../CHANGELOG.md:4196
  5822. msgid "People who build their own custom playbook from our roles should be aware that:"
  5823. msgstr ""
  5824. #: ../../../CHANGELOG.md:4198
  5825. msgid "the `matrix-coturn` role and actually starting coturn (e.g. `--tags=start`), requires that certificates are already put in place. For this reason, it's usually a good idea to have the `matrix-coturn` role execute after `matrix-nginx-proxy` (which retrieves the certificates)."
  5826. msgstr ""
  5827. #: ../../../CHANGELOG.md:4200
  5828. msgid "there are a few variables that can help you enable TLS support for coturn. See the `matrix-coturn` section in [group_vars/matrix-servers](./group_vars/matrix-servers)."
  5829. msgstr ""
  5830. #: ../../../CHANGELOG.md:4203
  5831. msgid "2019-03-12"
  5832. msgstr ""
  5833. #: ../../../CHANGELOG.md:4205
  5834. msgid "matrix-nginx-proxy support for serving the base domain"
  5835. msgstr ""
  5836. #: ../../../CHANGELOG.md:4207
  5837. msgid "If you don't have a dedicated server for your base domain and want to set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), the playbook has got you covered now."
  5838. msgstr ""
  5839. #: ../../../CHANGELOG.md:4209
  5840. msgid "It's now possible for the playbook to obtain an SSL certificate and serve the necessary files for Matrix Server Delegation on your base domain. Take a look at the new [Serving the base domain](docs/configuring-playbook-base-domain-serving.md) documentation page."
  5841. msgstr ""
  5842. #: ../../../CHANGELOG.md:4211
  5843. msgid "(BC break) matrix-nginx-proxy data variable renamed"
  5844. msgstr ""
  5845. #: ../../../CHANGELOG.md:4213
  5846. msgid "`matrix_nginx_proxy_data_path` was renamed to `matrix_nginx_proxy_base_path`."
  5847. msgstr ""
  5848. #: ../../../CHANGELOG.md:4215
  5849. msgid "There's a new `matrix_nginx_proxy_data_path` variable, which has a different use-purpose now (it's a subdirectory of `matrix_nginx_proxy_base_path` and is meant for storing various data files)."
  5850. msgstr ""
  5851. #: ../../../CHANGELOG.md:4218
  5852. msgid "2019-03-10"
  5853. msgstr ""
  5854. #: ../../../CHANGELOG.md:4220
  5855. msgid "Dimension integration manager support"
  5856. msgstr ""
  5857. #: ../../../CHANGELOG.md:4222
  5858. msgid "Thanks to [NullIsNot0](https://github.com/NullIsNot0), the playbook can now (optionally) install the [Dimension](https://dimension.t2bot.io/) integration manager. To learn more, see the [Setting up Dimension](docs/configuring-playbook-dimension.md) documentation page."
  5859. msgstr ""
  5860. #: ../../../CHANGELOG.md:4225
  5861. msgid "2019-03-07"
  5862. msgstr ""
  5863. #: ../../../CHANGELOG.md:4227
  5864. msgid "Ability to customize mxisd's email templates"
  5865. msgstr ""
  5866. #: ../../../CHANGELOG.md:4229
  5867. msgid "Thanks to [Sylvia van Os](https://github.com/TheLastProject), mxisd's email templates can now be customized easily. To learn more, see the [Customizing email templates](docs/configuring-playbook-mxisd.md#customizing-email-templates) documentation page."
  5868. msgstr ""
  5869. #: ../../../CHANGELOG.md:4232
  5870. msgid "2019-03-05"
  5871. msgstr ""
  5872. #: ../../../CHANGELOG.md:4234
  5873. msgid "Discord bridging support"
  5874. msgstr ""
  5875. #: ../../../CHANGELOG.md:4236
  5876. msgid "[@Lionstiger](https://github.com/Lionstiger) has done some great work adding Discord bridging support via [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord). To learn more, see the [Setting up Appservice Discord bridging](docs/configuring-playbook-bridge-appservice-discord.md) documentation page."
  5877. msgstr ""
  5878. #: ../../../CHANGELOG.md:4239
  5879. msgid "2019-02-19"
  5880. msgstr ""
  5881. #: ../../../CHANGELOG.md:4241
  5882. msgid "Renaming variables"
  5883. msgstr ""
  5884. #: ../../../CHANGELOG.md:4243
  5885. #: ../../../CHANGELOG.md:4560
  5886. #: ../../../CHANGELOG.md:4645
  5887. #: ../../../CHANGELOG.md:4765
  5888. msgid "The following playbook variables were renamed:"
  5889. msgstr ""
  5890. #: ../../../CHANGELOG.md:4245
  5891. msgid "from `host_specific_hostname_identity` to `matrix_domain`"
  5892. msgstr ""
  5893. #: ../../../CHANGELOG.md:4246
  5894. msgid "from `hostname_identity` to `matrix_domain`"
  5895. msgstr ""
  5896. #: ../../../CHANGELOG.md:4247
  5897. msgid "from `hostname_matrix` to `matrix_server_fqn_matrix`"
  5898. msgstr ""
  5899. #: ../../../CHANGELOG.md:4248
  5900. msgid "from `hostname_riot` to `matrix_server_fqn_riot`"
  5901. msgstr ""
  5902. #: ../../../CHANGELOG.md:4249
  5903. msgid "from `host_specific_matrix_ssl_lets_encrypt_support_email` to `matrix_ssl_lets_encrypt_support_email`"
  5904. msgstr ""
  5905. #: ../../../CHANGELOG.md:4251
  5906. msgid "Doing that, we've simplified things, made names less confusing (hopefully) and moved all variable names under the `matrix_` prefix."
  5907. msgstr ""
  5908. #: ../../../CHANGELOG.md:4254
  5909. msgid "2019-02-16"
  5910. msgstr ""
  5911. #: ../../../CHANGELOG.md:4256
  5912. msgid "Riot v1.0.1 support"
  5913. msgstr ""
  5914. #: ../../../CHANGELOG.md:4258
  5915. msgid "You can now use the brand new and redesigned Riot."
  5916. msgstr ""
  5917. #: ../../../CHANGELOG.md:4260
  5918. msgid "The new version no longer has a homepage by default, so we've also removed the custom homepage that we've been installing."
  5919. msgstr ""
  5920. #: ../../../CHANGELOG.md:4262
  5921. msgid "However, we still provide you with hooks to install your own `home.html` file by specifying the `matrix_riot_web_embedded_pages_home_path` variable (used to be called `matrix_riot_web_homepage_template` before)."
  5922. msgstr ""
  5923. #: ../../../CHANGELOG.md:4265
  5924. msgid "2019-02-14"
  5925. msgstr ""
  5926. #: ../../../CHANGELOG.md:4267
  5927. msgid "Synapse v0.99.1"
  5928. msgstr ""
  5929. #: ../../../CHANGELOG.md:4269
  5930. msgid "As we're moving toward Synapse v1.0, things are beginning to stabilize. Upgrading from v0.99.0 to v0.99.1 should be painless."
  5931. msgstr ""
  5932. #: ../../../CHANGELOG.md:4271
  5933. msgid "If you've been overriding the default configuration so that you can terminate TLS at the Synapse side (`matrix_synapse_no_tls: false`), you'll now have to replace this custom configuration with `matrix_synapse_tls_federation_listener_enabled: true`. The `matrix_synapse_no_tls` variable is no more."
  5934. msgstr ""
  5935. #: ../../../CHANGELOG.md:4274
  5936. msgid "2019-02-06"
  5937. msgstr ""
  5938. #: ../../../CHANGELOG.md:4276
  5939. msgid "Synapse v0.99 support and preparation for Synapse v1.0"
  5940. msgstr ""
  5941. #: ../../../CHANGELOG.md:4278
  5942. msgid "Matrix is undergoing a lot of changes as it matures towards Synapse v1.0. The first step is the Synapse v0.99 transitional release, which this playbook now supports."
  5943. msgstr ""
  5944. #: ../../../CHANGELOG.md:4280
  5945. msgid "If you've been using this playbook successfully until now, you'd be aware that we've been doing [Server Delegation](docs/howto-server-delegation.md) using a `_matrix._tcp` DNS SRV record (as per [Configuring DNS](docs/configuring-dns.md))."
  5946. msgstr ""
  5947. #: ../../../CHANGELOG.md:4282
  5948. msgid "Due to changes related to certificate file requirements that will affect us at Synapse v1.0, we'll have to stop using a **`_matrix._tcp` DNS SRV record in the future** (when Synapse goes to v1.0 — around 5th of March 2019). We **still need to keep the SRV record for now**, for backward compatibility with older Synapse versions (lower than v0.99)."
  5949. msgstr ""
  5950. #: ../../../CHANGELOG.md:4284
  5951. msgid "**What you need to do now** is make use of this transitional Synapse v0.99 release to **prepare your federation settings for the future**. You have 2 choices to prepare yourself for compatibility with the future Synapse v1.0:"
  5952. msgstr ""
  5953. #: ../../../CHANGELOG.md:4286
  5954. msgid "(recommended) set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), unless you are affected by the [Downsides of well-known-based Server Delegation](docs/howto-server-delegation.md#downsides-of-well-known-based-server-delegation). If you had previously set up the well-known `client` file, depending on how you've done it, it may be that there is nothing new required of you (besides [upgrading](docs/maintenance-upgrading-services.md)). After upgrading, you can [run a self-check](docs/maintenance-and-troubleshooting.md#how-to-check-if-services-work), which will tell you if you need to do anything extra with regard to setting up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file). After some time, when most people have upgraded to Synapse v0.99 and older releases have disappeared, be prepared to drop your `_matrix._tcp` SRV record."
  5955. msgstr ""
  5956. #: ../../../CHANGELOG.md:4288
  5957. msgid "(more advanced) if the [Downsides of well-known-based Server Delegation](docs/howto-server-delegation.md#downsides-of-well-known-based-server-delegation) are not to your liking, **as an alternative**, you can set up [Server Delegation via a DNS SRV record](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced). In such a case, you get to keep using your existing `_matrix._tcp` DNS SRV record forever and need to NOT set up a `/.well-known/matrix/server` file. Don't forget that you need to do certificate changes though. Follow the guide at [Server Delegation via a DNS SRV record](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)."
  5958. msgstr ""
  5959. #: ../../../CHANGELOG.md:4291
  5960. msgid "2019-02-01"
  5961. msgstr ""
  5962. #: ../../../CHANGELOG.md:4293
  5963. msgid "TLS v1.3 support"
  5964. msgstr ""
  5965. #: ../../../CHANGELOG.md:4295
  5966. msgid "Now that the [nginx Docker image](https://hub.docker.com/_/nginx) has [added support for TLS v1.3](https://github.com/nginxinc/docker-nginx/issues/190), we have enabled that protocol by default."
  5967. msgstr ""
  5968. #: ../../../CHANGELOG.md:4297
  5969. msgid "When using:"
  5970. msgstr ""
  5971. #: ../../../CHANGELOG.md:4299
  5972. msgid "the **integrated nginx server**: TLS v1.3 support might not kick in immediately, because the nginx version hasn't been bumped and you may have an older build of the nginx Docker image (currently `nginx:1.15.8-alpine`). Typically, we do not re-pull images that you already have. When the nginx version gets bumped in the future, everyone will get the update. Until then, you could manually force-pull the rebuilt Docker image by running this on the server: `docker pull nginx:1.15.8-alpine`."
  5973. msgstr ""
  5974. #: ../../../CHANGELOG.md:4301
  5975. msgid "**your own external nginx server**: if your external nginx server is too old, the new configuration we generate for you in `/matrix/nginx-proxy/conf.d/` might not work anymore, because it mentions `TLSv1.3` and your nginx version might not support that. You can adjust the SSL protocol list by overriding the `matrix_nginx_proxy_ssl_protocols` variable. Learn more in the documentation page for [Using your own webserver, instead of this playbook's nginx proxy](docs/configuring-playbook-own-webserver.md)"
  5976. msgstr ""
  5977. #: ../../../CHANGELOG.md:4303
  5978. msgid "**another web server**: you don't need to do anything to accommodate this change"
  5979. msgstr ""
  5980. #: ../../../CHANGELOG.md:4306
  5981. msgid "2019-01-31"
  5982. msgstr ""
  5983. #: ../../../CHANGELOG.md:4308
  5984. msgid "IRC bridging support"
  5985. msgstr ""
  5986. #: ../../../CHANGELOG.md:4310
  5987. msgid "[Devon Maloney (@Plailect)](https://github.com/Plailect) has done some great work bringing IRC bridging support via [matrix-appservice-irc](https://github.com/TeDomum/matrix-appservice-irc). To learn more, see the [Setting up Appservice IRC bridging](docs/configuring-playbook-bridge-appservice-irc.md) documentation page."
  5988. msgstr ""
  5989. #: ../../../CHANGELOG.md:4313
  5990. msgid "2019-01-29"
  5991. msgstr ""
  5992. #: ../../../CHANGELOG.md:4315
  5993. msgid "Running container processes as non-root, without capabilities and read-only"
  5994. msgstr ""
  5995. #: ../../../CHANGELOG.md:4317
  5996. msgid "To improve security, this playbook no longer starts container processes as the `root` user. Most containers were dropping privileges anyway, but we were trusting them with `root` privileges until they would do that. Not anymore — container processes now start as a non-root user (usually `matrix`) from the get-go."
  5997. msgstr ""
  5998. #: ../../../CHANGELOG.md:4319
  5999. msgid "For additional security, various capabilities are also dropped (see [why it's important](https://github.com/projectatomic/atomic-site/issues/203)) for all containers."
  6000. msgstr ""
  6001. #: ../../../CHANGELOG.md:4321
  6002. msgid "Additionally, most containers now use a read-only filesystem (see [why it's important](https://www.projectatomic.io/blog/2015/12/making-docker-images-write-only-in-production/)). Containers are given write access only to the directories they need to write to."
  6003. msgstr ""
  6004. #: ../../../CHANGELOG.md:4323
  6005. msgid "A minor breaking change is the `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size` variable having being renamed to `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size_mb` (note the `_mb` suffix). The new variable expects a number value (e.g. `25M` -> `25`). If you weren't customizing this variable, this wouldn't affect you."
  6006. msgstr ""
  6007. #: ../../../CHANGELOG.md:4325
  6008. msgid "matrix-mailer is now based on Exim, not Postfix"
  6009. msgstr ""
  6010. #: ../../../CHANGELOG.md:4327
  6011. msgid "While we would have preferred to stay with [Postfix](http://www.postfix.org/), we found out that it cannot run as a non-root user. We've had to replace it with [Exim](https://www.exim.org/) (via the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image)."
  6012. msgstr ""
  6013. #: ../../../CHANGELOG.md:4329
  6014. msgid "The internal `matrix-mailer` service (running in a container) now listens on port `8025` (used to be `587` before). The playbook will update your Synapse and mxisd email settings to match (`matrix-mailer:587` -> `matrix-mailer:8025`)."
  6015. msgstr ""
  6016. #: ../../../CHANGELOG.md:4331
  6017. msgid "Using the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image instead of [panubo/postfix](https://hub.docker.com/r/panubo/postfix/) also gives us a nice disk usage reduction (~200MB -> 8MB)."
  6018. msgstr ""
  6019. #: ../../../CHANGELOG.md:4334
  6020. msgid "2019-01-17"
  6021. msgstr ""
  6022. #: ../../../CHANGELOG.md:4336
  6023. msgid "(BC Break) Making the playbook's roles more independent of one another"
  6024. msgstr ""
  6025. #: ../../../CHANGELOG.md:4338
  6026. msgid "The following change **affects people running a more non-standard setup** — external Postgres or using our roles in their own other playbook. **Most users don't need to do anything**, besides becoming aware of the new glue variables file [`group_vars/matrix-servers`](group_vars/matrix-servers)."
  6027. msgstr ""
  6028. #: ../../../CHANGELOG.md:4341
  6029. msgid "Because people like using the playbook's components independently (outside of this playbook) and because it's much better for maintainability, we've continued working on separating them. Still, we'd like to offer a turnkey solution for running a fully-featured Matrix server, so this playbook remains important for wiring up the various components."
  6030. msgstr ""
  6031. #: ../../../CHANGELOG.md:4343
  6032. msgid "With the new changes, **all roles are now only dependent on the minimal `matrix-base` role**. They are no longer dependent among themselves."
  6033. msgstr ""
  6034. #: ../../../CHANGELOG.md:4345
  6035. msgid "In addition, the following components can now be completely disabled (for those who want/need to):"
  6036. msgstr ""
  6037. #: ../../../CHANGELOG.md:4346
  6038. msgid "`matrix-coturn` by using `coturn_enabled: false`"
  6039. msgstr ""
  6040. #: ../../../CHANGELOG.md:4347
  6041. msgid "`matrix-mailer` by using `matrix_mailer_enabled: false`"
  6042. msgstr ""
  6043. #: ../../../CHANGELOG.md:4348
  6044. msgid "`matrix-postgres` by using `matrix_postgres_enabled: false`"
  6045. msgstr ""
  6046. #: ../../../CHANGELOG.md:4350
  6047. msgid "The following changes had to be done:"
  6048. msgstr ""
  6049. #: ../../../CHANGELOG.md:4352
  6050. msgid "glue variables had to be introduced to the playbook, so it can wire together the various components. Those glue vars are stored in the [`group_vars/matrix-servers`](group_vars/matrix-servers) file. When overriding variables for a given component (role), you need to be aware of both the role defaults (`role/ROLE/defaults/main.yml`) and the role's corresponding section in the [`group_vars/matrix-servers`](group_vars/matrix-servers) file."
  6051. msgstr ""
  6052. #: ../../../CHANGELOG.md:4354
  6053. msgid "`matrix_postgres_use_external` has been superseded by the more consistently named `matrix_postgres_enabled` variable and a few other `matrix_synapse_database_` variables. See the [Using an external PostgreSQL server (optional)](docs/configuring-playbook-external-postgres.md) documentation page for an up-to-date replacement."
  6054. msgstr ""
  6055. #: ../../../CHANGELOG.md:4356
  6056. msgid "Postgres tools (`matrix-postgres-cli` and `matrix-make-user-admin`) are no longer installed if you're not enabling the `matrix-postgres` role (`matrix_postgres_enabled: false`)"
  6057. msgstr ""
  6058. #: ../../../CHANGELOG.md:4358
  6059. msgid "roles, being more independent now, are more minimal and do not do so much magic for you. People that are building their own playbook using our roles will definitely need to take a look at the [`group_vars/matrix-servers`](group_vars/matrix-servers) file and adapt their playbooks with the same (or similar) wiring logic."
  6060. msgstr ""
  6061. #: ../../../CHANGELOG.md:4361
  6062. msgid "2019-01-16"
  6063. msgstr ""
  6064. #: ../../../CHANGELOG.md:4363
  6065. msgid "Splitting the playbook into multiple roles"
  6066. msgstr ""
  6067. #: ../../../CHANGELOG.md:4365
  6068. msgid "For better maintainability, the playbook logic (which all used to reside in a single `matrix-server` role) has been split out into a number of different roles: `matrix-synapse`, `matrix-postgres`, `matrix-riot-web`, `matrix-mxisd`, etc. (see the `roles/` directory)."
  6069. msgstr ""
  6070. #: ../../../CHANGELOG.md:4368
  6071. msgid "To keep the filesystem more consistent with this separation, the **Postgres data had to be relocated**."
  6072. msgstr ""
  6073. #: ../../../CHANGELOG.md:4370
  6074. msgid "The default value of `matrix_postgres_data_path` was changed from `/matrix/postgres` to `/matrix/postgres/data`. The `/matrix/postgres` directory is what we consider a base path now (new variable `matrix_postgres_base_path`). **Your Postgres data files will automatically be relocated by the playbook** (`/matrix/postgres/*` -> `/matrix/postgres/data/`) when you run with `--tags=setup-all` (or `--tags=setup-postgres`). While this shouldn't cause data-loss, **it's better if you do a Postgres backup just in case**. You'd need to restart all services after this migration (`--tags=start`)."
  6075. msgstr ""
  6076. #: ../../../CHANGELOG.md:4373
  6077. msgid "2019-01-11"
  6078. msgstr ""
  6079. #: ../../../CHANGELOG.md:4375
  6080. msgid "(BC Break) mxisd configuration changes"
  6081. msgstr ""
  6082. #: ../../../CHANGELOG.md:4377
  6083. msgid "To be more flexible and to support the upcoming [mxisd](https://github.com/kamax-io/mxisd) 1.3.0 (when it gets released), we've had to redo how mxisd gets configured."
  6084. msgstr ""
  6085. #: ../../../CHANGELOG.md:4380
  6086. msgid "The following variables are no longer supported by this playbook:"
  6087. msgstr ""
  6088. #: ../../../CHANGELOG.md:4382
  6089. msgid "`matrix_mxisd_ldap_enabled`"
  6090. msgstr ""
  6091. #: ../../../CHANGELOG.md:4383
  6092. msgid "`matrix_mxisd_ldap_connection_host`"
  6093. msgstr ""
  6094. #: ../../../CHANGELOG.md:4384
  6095. msgid "`matrix_mxisd_ldap_connection_tls`"
  6096. msgstr ""
  6097. #: ../../../CHANGELOG.md:4385
  6098. msgid "`matrix_mxisd_ldap_connection_port`"
  6099. msgstr ""
  6100. #: ../../../CHANGELOG.md:4386
  6101. msgid "`matrix_mxisd_ldap_connection_baseDn`"
  6102. msgstr ""
  6103. #: ../../../CHANGELOG.md:4387
  6104. msgid "`matrix_mxisd_ldap_connection_baseDns`"
  6105. msgstr ""
  6106. #: ../../../CHANGELOG.md:4388
  6107. #: ../../../CHANGELOG.md:4389
  6108. msgid "`matrix_mxisd_ldap_connection_bindDn`"
  6109. msgstr ""
  6110. #: ../../../CHANGELOG.md:4390
  6111. #: ../../../CHANGELOG.md:4394
  6112. msgid "`matrix_mxisd_ldap_connection_bindPassword`"
  6113. msgstr ""
  6114. #: ../../../CHANGELOG.md:4391
  6115. msgid "`matrix_mxisd_ldap_filter`"
  6116. msgstr ""
  6117. #: ../../../CHANGELOG.md:4392
  6118. msgid "`matrix_mxisd_ldap_attribute_uid_type`"
  6119. msgstr ""
  6120. #: ../../../CHANGELOG.md:4393
  6121. msgid "`matrix_mxisd_ldap_attribute_uid_value`"
  6122. msgstr ""
  6123. #: ../../../CHANGELOG.md:4395
  6124. msgid "`matrix_mxisd_ldap_attribute_name`"
  6125. msgstr ""
  6126. #: ../../../CHANGELOG.md:4396
  6127. msgid "`matrix_mxisd_ldap_attribute_threepid_email`"
  6128. msgstr ""
  6129. #: ../../../CHANGELOG.md:4397
  6130. msgid "`matrix_mxisd_ldap_attribute_threepid_msisdn`"
  6131. msgstr ""
  6132. #: ../../../CHANGELOG.md:4398
  6133. msgid "`matrix_mxisd_ldap_identity_filter`"
  6134. msgstr ""
  6135. #: ../../../CHANGELOG.md:4399
  6136. msgid "`matrix_mxisd_ldap_identity_medium`"
  6137. msgstr ""
  6138. #: ../../../CHANGELOG.md:4400
  6139. msgid "`matrix_mxisd_ldap_auth_filter`"
  6140. msgstr ""
  6141. #: ../../../CHANGELOG.md:4401
  6142. msgid "`matrix_mxisd_ldap_directory_filter`"
  6143. msgstr ""
  6144. #: ../../../CHANGELOG.md:4402
  6145. msgid "`matrix_mxisd_template_config`"
  6146. msgstr ""
  6147. #: ../../../CHANGELOG.md:4404
  6148. msgid "You are encouraged to use the `matrix_mxisd_configuration_extension_yaml` variable to define your own mxisd configuration additions and overrides. Refer to the [default variables file](roles/custom/matrix-mxisd/defaults/main.yml) for more information."
  6149. msgstr ""
  6150. #: ../../../CHANGELOG.md:4406
  6151. msgid "This new way of configuring mxisd is beneficial because:"
  6152. msgstr ""
  6153. #: ../../../CHANGELOG.md:4408
  6154. msgid "it lets us support all mxisd configuration options, as the playbook simply forwards them to mxisd without needing to care or understand them"
  6155. msgstr ""
  6156. #: ../../../CHANGELOG.md:4409
  6157. msgid "it lets you upgrade to newer mxisd versions and make use of their features, without us having to add support for them explicitly"
  6158. msgstr ""
  6159. #: ../../../CHANGELOG.md:4412
  6160. msgid "2019-01-08"
  6161. msgstr ""
  6162. #: ../../../CHANGELOG.md:4414
  6163. msgid "(BC Break) Cronjob schedule no longer configurable"
  6164. msgstr ""
  6165. #: ../../../CHANGELOG.md:4416
  6166. msgid "Due to the way we manage cronjobs now, you can no longer configure the schedule they're invoked at."
  6167. msgstr ""
  6168. #: ../../../CHANGELOG.md:4418
  6169. msgid "If you were previously using `matrix_ssl_lets_encrypt_renew_cron_time_definition` or `matrix_nginx_proxy_reload_cron_time_definition` to set a custom schedule, you should note that these variables don't affect anything anymore."
  6170. msgstr ""
  6171. #: ../../../CHANGELOG.md:4421
  6172. msgid "If you miss this functionality, please [open an Issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/new) and let us know about your use case!"
  6173. msgstr ""
  6174. #: ../../../CHANGELOG.md:4424
  6175. msgid "2018-12-23"
  6176. msgstr ""
  6177. #: ../../../CHANGELOG.md:4426
  6178. msgid "(BC Break) More SSL certificate retrieval methods"
  6179. msgstr ""
  6180. #: ../../../CHANGELOG.md:4428
  6181. msgid "The playbook now lets you decide between 3 different SSL certificate retrieval methods:"
  6182. msgstr ""
  6183. #: ../../../CHANGELOG.md:4429
  6184. msgid "(default) obtaining free SSL certificates from Let's Encrypt"
  6185. msgstr ""
  6186. #: ../../../CHANGELOG.md:4430
  6187. msgid "generating self-signed SSL certificates"
  6188. msgstr ""
  6189. #: ../../../CHANGELOG.md:4431
  6190. msgid "managing SSL certificates manually"
  6191. msgstr ""
  6192. #: ../../../CHANGELOG.md:4433
  6193. msgid "Learn more in [Adjusting SSL certificate retrieval](docs/configuring-playbook-ssl-certificates.md)."
  6194. msgstr ""
  6195. #: ../../../CHANGELOG.md:4435
  6196. msgid "For people who use Let's Encrypt (mostly everyone, since it's the default), you'll also have to rename a variable in your configuration:"
  6197. msgstr ""
  6198. #: ../../../CHANGELOG.md:4437
  6199. msgid "before: `host_specific_matrix_ssl_support_email`"
  6200. msgstr ""
  6201. #: ../../../CHANGELOG.md:4438
  6202. msgid "after: `host_specific_matrix_ssl_lets_encrypt_support_email`"
  6203. msgstr ""
  6204. #: ../../../CHANGELOG.md:4440
  6205. msgid "(BC Break) mxisd upgrade with multiple base DN support"
  6206. msgstr ""
  6207. #: ../../../CHANGELOG.md:4442
  6208. msgid "mxisd has bee upgraded to [version 1.2.2](https://github.com/kamax-matrix/mxisd/releases/tag/v1.2.2), which supports [multiple base DNs](https://github.com/kamax-matrix/mxisd/blob/v1.2.2/docs/stores/ldap.md#base)."
  6209. msgstr ""
  6210. #: ../../../CHANGELOG.md:4444
  6211. msgid "If you were configuring this playbook's `matrix_mxisd_ldap_connection_baseDn` variable until now (a string containing a single base DN), you'll need to change to configuring the `matrix_mxisd_ldap_connection_baseDns` variable (an array containing multiple base DNs)."
  6212. msgstr ""
  6213. #: ../../../CHANGELOG.md:4446
  6214. msgid "Example change:"
  6215. msgstr ""
  6216. #: ../../../CHANGELOG.md:4448
  6217. msgid "before: `matrix_mxisd_ldap_connection_baseDn: OU=Users,DC=example,DC=org`"
  6218. msgstr ""
  6219. #: ../../../CHANGELOG.md:4449
  6220. msgid "after: `matrix_mxisd_ldap_connection_baseDns: ['OU=Users,DC=example,DC=org']`"
  6221. msgstr ""
  6222. #: ../../../CHANGELOG.md:4452
  6223. msgid "2018-12-21"
  6224. msgstr ""
  6225. #: ../../../CHANGELOG.md:4454
  6226. msgid "Synapse 0.34.0 and Python 3"
  6227. msgstr ""
  6228. #: ../../../CHANGELOG.md:4456
  6229. msgid "Synapse has been upgraded to 0.34.0 and now uses Python 3. Based on feedback from others, running Synapse on Python 3 is supposed to decrease memory usage significantly (~2x)."
  6230. msgstr ""
  6231. #: ../../../CHANGELOG.md:4459
  6232. msgid "2018-12-12"
  6233. msgstr ""
  6234. #: ../../../CHANGELOG.md:4461
  6235. msgid "Riot homepage customization"
  6236. msgstr ""
  6237. #: ../../../CHANGELOG.md:4463
  6238. msgid "You can now customize some parts of the Riot homepage (or even completely replace it with your own custom page). See the `matrix_riot_web_homepage_` variables in `roles/custom/matrix-riot-web/defaults/main.yml`."
  6239. msgstr ""
  6240. #: ../../../CHANGELOG.md:4466
  6241. msgid "2018-12-04"
  6242. msgstr ""
  6243. #: ../../../CHANGELOG.md:4468
  6244. msgid "mxisd extensibility"
  6245. msgstr ""
  6246. #: ../../../CHANGELOG.md:4470
  6247. msgid "The [LDAP identity store for mxisd](https://github.com/kamax-matrix/mxisd/blob/master/docs/stores/ldap.md) can now be configured easily using playbook variables (see the `matrix_mxisd_ldap_` variables in `roles/custom/matrix-server/defaults/main.yml`)."
  6248. msgstr ""
  6249. #: ../../../CHANGELOG.md:4473
  6250. msgid "2018-11-28"
  6251. msgstr ""
  6252. #: ../../../CHANGELOG.md:4475
  6253. msgid "More scripts"
  6254. msgstr ""
  6255. #: ../../../CHANGELOG.md:4477
  6256. msgid "matrix-remove-all allows to uninstall everything with a single command"
  6257. msgstr ""
  6258. #: ../../../CHANGELOG.md:4478
  6259. msgid "matrix-make-user-admin allows to upgrade a user's privileges"
  6260. msgstr ""
  6261. #: ../../../CHANGELOG.md:4480
  6262. msgid "LDAP auth support via matrix-synapse-ldap3"
  6263. msgstr ""
  6264. #: ../../../CHANGELOG.md:4482
  6265. msgid "The playbook can now install and configure [LDAP auth support](https://github.com/matrix-org/matrix-synapse-ldap3) for you."
  6266. msgstr ""
  6267. #: ../../../CHANGELOG.md:4484
  6268. msgid "Additional details are available in [Setting up the LDAP authentication password provider module](docs/configuring-playbook-ldap-auth.md)."
  6269. msgstr ""
  6270. #: ../../../CHANGELOG.md:4487
  6271. msgid "2018-11-23"
  6272. msgstr ""
  6273. #: ../../../CHANGELOG.md:4489
  6274. msgid "Support for controlling public registration and room auto-join"
  6275. msgstr ""
  6276. #: ../../../CHANGELOG.md:4491
  6277. msgid "The playbook now lets you enable public registration for users (controlled via `matrix_synapse_enable_registration`). By default, public registration is forbidden."
  6278. msgstr ""
  6279. #: ../../../CHANGELOG.md:4493
  6280. msgid "You can also make people automatically get auto-joined to rooms (controlled via `matrix_synapse_auto_join_rooms`)."
  6281. msgstr ""
  6282. #: ../../../CHANGELOG.md:4495
  6283. msgid "Support for changing the welcome user ID (welcome bot)"
  6284. msgstr ""
  6285. #: ../../../CHANGELOG.md:4497
  6286. msgid "By default, `@riot-bot:matrix.org` is used to welcome newly registered users. This can be changed to something else (or disabled) via the new `matrix_riot_web_welcome_user_id` variable."
  6287. msgstr ""
  6288. #: ../../../CHANGELOG.md:4500
  6289. msgid "2018-11-14"
  6290. msgstr ""
  6291. #: ../../../CHANGELOG.md:4502
  6292. msgid "Ability to set Synapse log levels"
  6293. msgstr ""
  6294. #: ../../../CHANGELOG.md:4504
  6295. msgid "The playbook now allows you to set the log levels used by Synapse. The default logging levels remain the same."
  6296. msgstr ""
  6297. #: ../../../CHANGELOG.md:4506
  6298. msgid "You can now override following variables with any of the supported log levels listed here: https://docs.python.org/3/library/logging.html#logging-levels"
  6299. msgstr ""
  6300. #: ../../../CHANGELOG.md:4515
  6301. msgid "2018-11-03"
  6302. msgstr ""
  6303. #: ../../../CHANGELOG.md:4517
  6304. msgid "Customize parts of Riot's config"
  6305. msgstr ""
  6306. #: ../../../CHANGELOG.md:4519
  6307. msgid "You can now customize some parts of Riot's `config.json`. These playbook variables, with these default values, have been added:"
  6308. msgstr ""
  6309. #: ../../../CHANGELOG.md:4530
  6310. msgid "This now allows you use a custom integration manager like [Dimension](https://dimension.t2bot.io). For example, if you wish to use the Dimension instance hosted at dimension.t2bot.io, you can set the following in your vars.yml file:"
  6311. msgstr ""
  6312. #: ../../../CHANGELOG.md:4539
  6313. msgid "SSL protocols used to serve Riot and Synapse"
  6314. msgstr ""
  6315. #: ../../../CHANGELOG.md:4541
  6316. msgid "There's now a new `matrix_nginx_proxy_ssl_protocols` playbook variable, which controls the SSL protocols used to serve Riot and Synapse. Its default value is `TLSv1.1 TLSv1.2`. This playbook previously used `TLSv1 TLSv1.1 TLSv1.2` to serve Riot and Synapse."
  6317. msgstr ""
  6318. #: ../../../CHANGELOG.md:4543
  6319. msgid "You may wish to re-enable TLSv1 if you need to access Riot in older browsers."
  6320. msgstr ""
  6321. #: ../../../CHANGELOG.md:4545
  6322. msgid "Note: Currently the dockerized nginx doesn't support TLSv1.3. See https://github.com/nginxinc/docker-nginx/issues/190 for more details."
  6323. msgstr ""
  6324. #: ../../../CHANGELOG.md:4548
  6325. msgid "2018-11-01"
  6326. msgstr ""
  6327. #: ../../../CHANGELOG.md:4550
  6328. msgid "Postgres 11 support"
  6329. msgstr ""
  6330. #: ../../../CHANGELOG.md:4552
  6331. msgid "The playbook now installs [Postgres 11](https://www.postgresql.org/about/news/1894/) by default."
  6332. msgstr ""
  6333. #: ../../../CHANGELOG.md:4554
  6334. msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x or 10.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)."
  6335. msgstr ""
  6336. #: ../../../CHANGELOG.md:4556
  6337. #: ../../../CHANGELOG.md:4643
  6338. #: ../../../CHANGELOG.md:4763
  6339. msgid "(BC Break) Renaming playbook variables"
  6340. msgstr ""
  6341. #: ../../../CHANGELOG.md:4558
  6342. msgid "Due to the large amount of features added to this playbook lately, to keep things manageable we've had to reorganize its configuration variables a bit."
  6343. msgstr ""
  6344. #: ../../../CHANGELOG.md:4562
  6345. msgid "from `matrix_docker_image_mxisd` to `matrix_mxisd_docker_image`"
  6346. msgstr ""
  6347. #: ../../../CHANGELOG.md:4563
  6348. msgid "from `matrix_docker_image_mautrix_telegram` to `matrix_mautrix_telegram_docker_image`"
  6349. msgstr ""
  6350. #: ../../../CHANGELOG.md:4564
  6351. msgid "from `matrix_docker_image_mautrix_whatsapp` to `matrix_mautrix_whatsapp_docker_image`"
  6352. msgstr ""
  6353. #: ../../../CHANGELOG.md:4565
  6354. msgid "from `matrix_docker_image_mailer` to `matrix_mailer_docker_image`"
  6355. msgstr ""
  6356. #: ../../../CHANGELOG.md:4566
  6357. msgid "from `matrix_docker_image_coturn` to `coturn_container_image`"
  6358. msgstr ""
  6359. #: ../../../CHANGELOG.md:4567
  6360. msgid "from `matrix_docker_image_goofys` to `matrix_s3_goofys_docker_image`"
  6361. msgstr ""
  6362. #: ../../../CHANGELOG.md:4568
  6363. msgid "from `matrix_docker_image_riot` to `matrix_riot_web_docker_image`"
  6364. msgstr ""
  6365. #: ../../../CHANGELOG.md:4569
  6366. msgid "from `matrix_docker_image_nginx` to `matrix_nginx_proxy_docker_image`"
  6367. msgstr ""
  6368. #: ../../../CHANGELOG.md:4570
  6369. msgid "from `matrix_docker_image_synapse` to `matrix_synapse_docker_image`"
  6370. msgstr ""
  6371. #: ../../../CHANGELOG.md:4571
  6372. msgid "from `matrix_docker_image_postgres_v9` to `matrix_postgres_docker_image_v9`"
  6373. msgstr ""
  6374. #: ../../../CHANGELOG.md:4572
  6375. msgid "from `matrix_docker_image_postgres_v10` to `matrix_postgres_docker_image_v10`"
  6376. msgstr ""
  6377. #: ../../../CHANGELOG.md:4573
  6378. msgid "from `matrix_docker_image_postgres_latest` to `matrix_postgres_docker_image_latest`"
  6379. msgstr ""
  6380. #: ../../../CHANGELOG.md:4576
  6381. msgid "2018-10-26"
  6382. msgstr ""
  6383. #: ../../../CHANGELOG.md:4578
  6384. msgid "Mautrix Whatsapp bridging support"
  6385. msgstr ""
  6386. #: ../../../CHANGELOG.md:4580
  6387. msgid "The playbook now supports bridging with [Whatsapp](https://www.whatsapp.com/) by installing the [mautrix-whatsapp](https://github.com/tulir/mautrix-whatsapp) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)."
  6388. msgstr ""
  6389. #: ../../../CHANGELOG.md:4582
  6390. msgid "Additional details are available in [Setting up Mautrix Whatsapp bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)."
  6391. msgstr ""
  6392. #: ../../../CHANGELOG.md:4585
  6393. msgid "2018-10-25"
  6394. msgstr ""
  6395. #: ../../../CHANGELOG.md:4587
  6396. msgid "Support for controlling Matrix federation"
  6397. msgstr ""
  6398. #: ../../../CHANGELOG.md:4589
  6399. msgid "The playbook can now help you with [Controlling Matrix federation](docs/configuring-playbook-federation), should you wish to run a more private (isolated) server."
  6400. msgstr ""
  6401. #: ../../../CHANGELOG.md:4592
  6402. msgid "2018-10-24"
  6403. msgstr ""
  6404. #: ../../../CHANGELOG.md:4594
  6405. msgid "Disabling riot-web guests"
  6406. msgstr ""
  6407. #: ../../../CHANGELOG.md:4596
  6408. msgid "From now on, Riot's configuration setting `disable_guests` would be set to `true`. The homeserver was rejecting guests anyway, so this is just a cosmetic change affecting Riot's UI."
  6409. msgstr ""
  6410. #: ../../../CHANGELOG.md:4599
  6411. msgid "2018-10-21"
  6412. msgstr ""
  6413. #: ../../../CHANGELOG.md:4601
  6414. msgid "Self-check maintenance command"
  6415. msgstr ""
  6416. #: ../../../CHANGELOG.md:4603
  6417. msgid "The playbook can now [check if services are configured correctly](docs/maintenance-and-troubleshooting.md#how-to-check-if-services-work)."
  6418. msgstr ""
  6419. #: ../../../CHANGELOG.md:4606
  6420. msgid "2018-10-05"
  6421. msgstr ""
  6422. #: ../../../CHANGELOG.md:4608
  6423. msgid "Presence tracking made configurable"
  6424. msgstr ""
  6425. #: ../../../CHANGELOG.md:4610
  6426. msgid "The playbook can now enable/disable user presence-status tracking in Synapse, through the playbook's `matrix_synapse_use_presence` variable (having a default value of `true` — enabled)."
  6427. msgstr ""
  6428. #: ../../../CHANGELOG.md:4612
  6429. msgid "If users participate in large rooms with many other servers, disabling presence will decrease server load significantly."
  6430. msgstr ""
  6431. #: ../../../CHANGELOG.md:4615
  6432. msgid "2018-09-27"
  6433. msgstr ""
  6434. #: ../../../CHANGELOG.md:4617
  6435. msgid "Synapse Cache Factor made configurable"
  6436. msgstr ""
  6437. #: ../../../CHANGELOG.md:4619
  6438. msgid "The playbook now makes the Synapse cache factor configurable, through the playbook's `matrix_synapse_cache_factor` variable (having a default value of `0.5`)."
  6439. msgstr ""
  6440. #: ../../../CHANGELOG.md:4621
  6441. msgid "Changing that value allows you to potentially decrease RAM usage or to increase performance by caching more stuff. Some information on it is available here: https://github.com/element-hq/synapse#help-synapse-eats-all-my-ram"
  6442. msgstr ""
  6443. #: ../../../CHANGELOG.md:4624
  6444. msgid "2018-09-26"
  6445. msgstr ""
  6446. #: ../../../CHANGELOG.md:4626
  6447. msgid "Disabling Docker container logging"
  6448. msgstr ""
  6449. #: ../../../CHANGELOG.md:4628
  6450. msgid "`--log-driver=none` is used for all Docker containers now."
  6451. msgstr ""
  6452. #: ../../../CHANGELOG.md:4630
  6453. msgid "All these containers are started through systemd anyway and get logged in journald, so there's no need for Docker to be logging the same thing using the default `json-file` driver. Doing that was growing `/var/lib/docker/containers/…` infinitely until service/container restart."
  6454. msgstr ""
  6455. #: ../../../CHANGELOG.md:4632
  6456. msgid "As a result of this, things like `docker logs matrix-synapse` won't work anymore. `journalctl -u matrix-synapse` is how one can see the logs."
  6457. msgstr ""
  6458. #: ../../../CHANGELOG.md:4635
  6459. msgid "2018-09-17"
  6460. msgstr ""
  6461. #: ../../../CHANGELOG.md:4637
  6462. msgid "Service discovery support"
  6463. msgstr ""
  6464. #: ../../../CHANGELOG.md:4639
  6465. msgid "The playbook now helps you set up [service discovery](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery) using a `/.well-known/matrix/client` file."
  6466. msgstr ""
  6467. #: ../../../CHANGELOG.md:4641
  6468. msgid "Additional details are available in [Configuring service discovery via .well-known](docs/configuring-well-known.md)."
  6469. msgstr ""
  6470. #: ../../../CHANGELOG.md:4647
  6471. msgid "from `matrix_nginx_riot_web_data_path` to `matrix_riot_web_data_path`"
  6472. msgstr ""
  6473. #: ../../../CHANGELOG.md:4648
  6474. msgid "from `matrix_riot_web_default_identity_server_url` to `matrix_identity_server_url`"
  6475. msgstr ""
  6476. #: ../../../CHANGELOG.md:4651
  6477. msgid "2018-09-07"
  6478. msgstr ""
  6479. #: ../../../CHANGELOG.md:4653
  6480. msgid "Mautrix Telegram bridging support"
  6481. msgstr ""
  6482. #: ../../../CHANGELOG.md:4655
  6483. msgid "The playbook now supports bridging with [Telegram](https://telegram.org/) by installing the [mautrix-telegram](https://github.com/tulir/mautrix-telegram) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)."
  6484. msgstr ""
  6485. #: ../../../CHANGELOG.md:4657
  6486. msgid "Additional details are available in [Setting up Mautrix Telegram bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)."
  6487. msgstr ""
  6488. #: ../../../CHANGELOG.md:4659
  6489. msgid "Events cache size increase and configurability for Matrix Synapse"
  6490. msgstr ""
  6491. #: ../../../CHANGELOG.md:4661
  6492. msgid "The playbook now lets you configure Matrix Synapse's `event_cache_size` configuration via the `matrix_synapse_event_cache_size` playbook variable."
  6493. msgstr ""
  6494. #: ../../../CHANGELOG.md:4663
  6495. msgid "Previously, this value was hardcoded to `\"10K\"`. From now on, a more reasonable default of `\"100K\"` is used."
  6496. msgstr ""
  6497. #: ../../../CHANGELOG.md:4665
  6498. msgid "Password-peppering support for Matrix Synapse"
  6499. msgstr ""
  6500. #: ../../../CHANGELOG.md:4667
  6501. msgid "The playbook now supports enabling password-peppering for increased security in Matrix Synapse via the `matrix_synapse_password_config_pepper` playbook variable. Using a password pepper is disabled by default (just like it used to be before this playbook variable got introduced) and is not to be enabled/disabled after initial setup, as that would invalidate all existing passwords."
  6502. msgstr ""
  6503. #: ../../../CHANGELOG.md:4669
  6504. msgid "Statistics-reporting support for Matrix Synapse"
  6505. msgstr ""
  6506. #: ../../../CHANGELOG.md:4671
  6507. msgid "There's now a new `matrix_synapse_report_stats` playbook variable, which controls the `report_stats` configuration option for Matrix Synapse. It defaults to `false`, so no change is required to retain your privacy."
  6508. msgstr ""
  6509. #: ../../../CHANGELOG.md:4673
  6510. msgid "If you'd like to start reporting statistics about your homeserver (things like number of users, number of messages sent, uptime, load, etc.) to matrix.org, you can turn on stats reporting."
  6511. msgstr ""
  6512. #: ../../../CHANGELOG.md:4676
  6513. msgid "2018-08-29"
  6514. msgstr ""
  6515. #: ../../../CHANGELOG.md:4678
  6516. msgid "Changing the way SSL certificates are retrieved"
  6517. msgstr ""
  6518. #: ../../../CHANGELOG.md:4680
  6519. msgid "We've been using [acmetool](https://github.com/hlandau/acme) (with the [willwill/acme-docker](https://hub.docker.com/r/willwill/acme-docker/) Docker image) until now."
  6520. msgstr ""
  6521. #: ../../../CHANGELOG.md:4682
  6522. msgid "Due to the Docker image being deprecated, and things looking bleak for acmetool's support of the newer ACME v2 API endpoint, we've switched to using [certbot](https://certbot.eff.org/) (with the [certbot/certbot](https://hub.docker.com/r/certbot/certbot/) Docker image)."
  6523. msgstr ""
  6524. #: ../../../CHANGELOG.md:4684
  6525. msgid "Simply re-running the playbook will retrieve new certificates (via certbot) for you. To ensure you don't leave any old files behind, though, you'd better do this:"
  6526. msgstr ""
  6527. #: ../../../CHANGELOG.md:4686
  6528. msgid "`systemctl stop 'matrix*'`"
  6529. msgstr ""
  6530. #: ../../../CHANGELOG.md:4687
  6531. msgid "stop your custom webserver, if you're running one (only affects you if you've installed with `matrix_nginx_proxy_enabled: false`)"
  6532. msgstr ""
  6533. #: ../../../CHANGELOG.md:4688
  6534. msgid "`mv /matrix/ssl /matrix/ssl-acmetool-delete-later`"
  6535. msgstr ""
  6536. #: ../../../CHANGELOG.md:4689
  6537. msgid "re-run the playbook's [installation](docs/installing.md)"
  6538. msgstr ""
  6539. #: ../../../CHANGELOG.md:4690
  6540. msgid "possibly delete `/matrix/ssl-acmetool-delete-later`"
  6541. msgstr ""
  6542. #: ../../../CHANGELOG.md:4693
  6543. msgid "2018-08-21"
  6544. msgstr ""
  6545. #: ../../../CHANGELOG.md:4695
  6546. msgid "Matrix Corporal support"
  6547. msgstr ""
  6548. #: ../../../CHANGELOG.md:4697
  6549. msgid "The playbook can now install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you."
  6550. msgstr ""
  6551. #: ../../../CHANGELOG.md:4699
  6552. msgid "Additional details are available in [Setting up Matrix Corporal](docs/configuring-playbook-matrix-corporal.md)."
  6553. msgstr ""
  6554. #: ../../../CHANGELOG.md:4702
  6555. msgid "2018-08-20"
  6556. msgstr ""
  6557. #: ../../../CHANGELOG.md:4704
  6558. msgid "Matrix Synapse rate limit control variables"
  6559. msgstr ""
  6560. #: ../../../CHANGELOG.md:4706
  6561. msgid "The following new variables can now be configured to control Matrix Synapse's rate-limiting (default values are shown below)."
  6562. msgstr ""
  6563. #: ../../../CHANGELOG.md:4713
  6564. msgid "Shared Secret Auth support via matrix-synapse-shared-secret-auth"
  6565. msgstr ""
  6566. #: ../../../CHANGELOG.md:4715
  6567. msgid "The playbook can now install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you."
  6568. msgstr ""
  6569. #: ../../../CHANGELOG.md:4717
  6570. msgid "Additional details are available in [Setting up the Shared Secret Auth password provider module](docs/configuring-playbook-shared-secret-auth.md)."
  6571. msgstr ""
  6572. #: ../../../CHANGELOG.md:4720
  6573. msgid "2018-08-17"
  6574. msgstr ""
  6575. #: ../../../CHANGELOG.md:4722
  6576. msgid "REST auth support via matrix-synapse-rest-auth"
  6577. msgstr ""
  6578. #: ../../../CHANGELOG.md:4724
  6579. msgid "The playbook can now install and configure [matrix-synapse-rest-auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you."
  6580. msgstr ""
  6581. #: ../../../CHANGELOG.md:4726
  6582. msgid "Additional details are available in [Setting up the REST authentication password provider module](docs/configuring-playbook-rest-auth.md)."
  6583. msgstr ""
  6584. #: ../../../CHANGELOG.md:4728
  6585. msgid "Compression improvements"
  6586. msgstr ""
  6587. #: ../../../CHANGELOG.md:4730
  6588. msgid "Shifted Matrix Synapse compression from happening in the Matrix Synapse, to happening in the nginx proxy that's in front of it."
  6589. msgstr ""
  6590. #: ../../../CHANGELOG.md:4733
  6591. msgid "Additionally, `riot-web` also gets compressed now (in the nginx proxy), which drops the initial page load's size from 5.31MB to 1.86MB."
  6592. msgstr ""
  6593. #: ../../../CHANGELOG.md:4736
  6594. msgid "Disabling some unnecessary Synapse services"
  6595. msgstr ""
  6596. #: ../../../CHANGELOG.md:4738
  6597. msgid "The following services are not necessary, so they have been disabled:"
  6598. msgstr ""
  6599. #: ../../../CHANGELOG.md:4739
  6600. msgid "on the federation port (8448): the `client` service"
  6601. msgstr ""
  6602. #: ../../../CHANGELOG.md:4740
  6603. msgid "on the http port (8008, exposed over 443): the old Angular `webclient` and the `federation` service"
  6604. msgstr ""
  6605. #: ../../../CHANGELOG.md:4742
  6606. msgid "Federation runs only on the federation port (8448) now. The Client APIs run only on the http port (8008) now."
  6607. msgstr ""
  6608. #: ../../../CHANGELOG.md:4745
  6609. msgid "2018-08-15"
  6610. msgstr ""
  6611. #: ../../../CHANGELOG.md:4747
  6612. msgid "mxisd Identity Server support"
  6613. msgstr ""
  6614. #: ../../../CHANGELOG.md:4749
  6615. msgid "The playbook now sets up an [mxisd](https://github.com/kamax-io/mxisd) Identity Server for you by default. Additional details are available in [Setting up ma1sd Identity Server](docs/configuring-playbook-mxisd.md)."
  6616. msgstr ""
  6617. #: ../../../CHANGELOG.md:4752
  6618. msgid "2018-08-14"
  6619. msgstr ""
  6620. #: ../../../CHANGELOG.md:4754
  6621. msgid "Email-sending support"
  6622. msgstr ""
  6623. #: ../../../CHANGELOG.md:4756
  6624. msgid "The playbook now configures an email-sending service (postfix) by default. Additional details are available in [Adjusting email-sending settings](docs/configuring-playbook-email.md)."
  6625. msgstr ""
  6626. #: ../../../CHANGELOG.md:4758
  6627. msgid "With this, Matrix Synapse is able to send email notifications for missed messages, etc."
  6628. msgstr ""
  6629. #: ../../../CHANGELOG.md:4761
  6630. msgid "2018-08-08"
  6631. msgstr ""
  6632. #: ../../../CHANGELOG.md:4767
  6633. msgid "from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`"
  6634. msgstr ""
  6635. #: ../../../CHANGELOG.md:4768
  6636. msgid "from `matrix_max_log_file_size_mb` to `matrix_synapse_max_log_file_size_mb`"
  6637. msgstr ""
  6638. #: ../../../CHANGELOG.md:4769
  6639. msgid "from `matrix_max_log_files_count` to `matrix_synapse_max_log_files_count`"
  6640. msgstr ""
  6641. #: ../../../CHANGELOG.md:4770
  6642. msgid "from `docker_matrix_image` to `matrix_docker_image_synapse`"
  6643. msgstr ""
  6644. #: ../../../CHANGELOG.md:4771
  6645. msgid "from `docker_nginx_image` to `matrix_docker_image_nginx`"
  6646. msgstr ""
  6647. #: ../../../CHANGELOG.md:4772
  6648. msgid "from `docker_riot_image` to `matrix_docker_image_riot`"
  6649. msgstr ""
  6650. #: ../../../CHANGELOG.md:4773
  6651. msgid "from `docker_goofys_image` to `matrix_docker_image_goofys`"
  6652. msgstr ""
  6653. #: ../../../CHANGELOG.md:4774
  6654. msgid "from `docker_coturn_image` to `matrix_docker_image_coturn`"
  6655. msgstr ""
  6656. #: ../../../CHANGELOG.md:4776
  6657. msgid "If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names."
  6658. msgstr ""
  6659. #: ../../../CHANGELOG.md:4778
  6660. msgid "Renaming Ansible playbook tag"
  6661. msgstr ""
  6662. #: ../../../CHANGELOG.md:4780
  6663. msgid "The command for executing the whole playbook has changed. The `setup-main` tag got renamed to `setup-all`."
  6664. msgstr ""
  6665. #: ../../../CHANGELOG.md:4782
  6666. msgid "Docker container linking"
  6667. msgstr ""
  6668. #: ../../../CHANGELOG.md:4784
  6669. msgid "Changed the way the Docker containers are linked together. The ones that need to communicate with others operate in a `matrix` network now and not in the default bridge network."
  6670. msgstr ""