overmind
/
matrix-docker-ansible-deploy
kopia lustrzana https://github.com/spantaleev/matrix-docker-ansible-deploy
1
0
Forkuj 0
Kod Zgłoszenia 0 Wydania 0 Wiki Aktywność
Matrix Docker Ansible eploy
Nie możesz wybrać więcej, niż 25 tematów Tematy muszą się zaczynać od litery lub cyfry, mogą zawierać myślniki ('-') i mogą mieć do 35 znaków.
11723 Commity
5 Gałęzie
549 MiB
 
 
 
Drzewo: 5c42769db6
Gałęzie Tagi
${ item.name }
Utwórz gałąź ${ searchTerm }
z '5c42769db6'
${ noResults }
matrix-docker-ansible-deploy/i18n/translation-templates/CHANGELOG.pot

9003 wiersze
442 KiB
Czysty Wina Historia 

  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-08-01 17:14+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. 

  19. #: ../../../CHANGELOG.md:1

  20. msgid "2026-07-28"

  21. msgstr ""

  22. 

  23. #: ../../../CHANGELOG.md:3

  24. msgid "(Backward Compatibility Break) ntfy users are now declared with hashed passwords"

  25. msgstr ""

  26. 

  27. #: ../../../CHANGELOG.md:5

  28. msgid "This only affects you if you have enabled authentication for [ntfy](docs/configuring-playbook-ntfy.md) via `ntfy_credentials`."

  29. msgstr ""

  30. 

  31. #: ../../../CHANGELOG.md:7

  32. msgid "The ntfy role used to create users by invoking `ntfy user` commands against the running container. Since v2.14.0, ntfy can provision users and access-control entries from its own configuration file, so the role now does that instead. Besides being a lot simpler, this fixes passwords containing spaces never arriving intact."

  33. msgstr ""

  34. 

  35. #: ../../../CHANGELOG.md:9

  36. msgid "Replace `ntfy_credentials` with `ntfy_auth_users_custom`, which takes bcrypt password hashes rather than plaintext passwords:"

  37. msgstr ""

  38. 

  39. #: ../../../CHANGELOG.md:18

  40. msgid "Generate a hash for each of your passwords by running the following command on any machine which has Docker installed. It asks for the password and prints its hash:"

  41. msgstr ""

  42. 

  43. #: ../../../CHANGELOG.md:24

  44. msgid "The playbook will let you know if your configuration still uses `ntfy_credentials`."

  45. msgstr ""

  46. 

  47. #: ../../../CHANGELOG.md:26

  48. msgid "Your existing ntfy users are left alone and keep working until you declare them again this way. Note that ntfy manages declared users and access-control entries declaratively, so removing one from your configuration later deletes it from ntfy's user database."

  49. msgstr ""

  50. 

  51. #: ../../../CHANGELOG.md:28

  52. msgid "Users with the `admin` role get access to all topics. Others start with no access at all, and can be granted access to specific topics via `ntfy_auth_access_custom`. It is also now possible to control what unauthenticated visitors may do (`ntfy_auth_default_access`) and whether users may log in at all (`ntfy_enable_login`, which follows your authentication setup by default). See the role's [documentation on access control](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/docs/configuring-ntfy.md#enable-access-control-with-authentication-optional) for details."

  53. msgstr ""

  54. 

  55. #: ../../../CHANGELOG.md:30

  56. msgid "Support for bridging to LinkedIn via mautrix-linkedin"

  57. msgstr ""

  58. 

  59. #: ../../../CHANGELOG.md:32

  60. msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports bridging to [LinkedIn](https://www.linkedin.com/) via [mautrix-linkedin](https://github.com/mautrix/linkedin)."

  61. msgstr ""

  62. 

  63. #: ../../../CHANGELOG.md:34

  64. msgid "Logging in requires copying a request out of your browser's developer tools, and only works with Chrome or another Chrome-based browser. To learn more, see our [Setting up Mautrix LinkedIn bridging](./docs/configuring-playbook-bridge-mautrix-linkedin.md) documentation page."

  65. msgstr ""

  66. 

  67. #: ../../../CHANGELOG.md:36

  68. msgid "This bridge supersedes [beeper-linkedin](./docs/configuring-playbook-bridge-beeper-linkedin.md), which is now considered unmaintained (its [upstream repository](https://github.com/beeper/linkedin) has been archived). The old bridge remains installable, but you may wish to switch. Both bridges claim the same appservice namespaces, so the playbook refuses to install mautrix-linkedin while beeper-linkedin is still enabled."

  69. msgstr ""

  70. 

  71. #: ../../../CHANGELOG.md:38

  72. msgid "Support for bridging to LINE via beeper-line"

  73. msgstr ""

  74. 

  75. #: ../../../CHANGELOG.md:40

  76. msgid "Thanks to [Co van Leeuwen](https://github.com/c00), the playbook can now bridge [LINE](https://line.me/) via [beeper-line](https://github.com/beeper/line), a bridge based on the modern mautrix bridge framework. It supports LINE accounts with Letter Sealing enabled or disabled and bridges messages, media, reactions, replies, receipts, and other common chat features."

  77. msgstr ""

  78. 

  79. #: ../../../CHANGELOG.md:42

  80. msgid "The bridge identifies itself as a LINE Chrome Extension client, so it cannot be used at the same time as the real LINE Chrome Extension. See [Setting up Beeper LINE bridging](docs/configuring-playbook-bridge-beeper-line.md) to get started."

  81. msgstr ""

  82. 

  83. #: ../../../CHANGELOG.md:45

  84. msgid "2026-07-19"

  85. msgstr ""

  86. 

  87. #: ../../../CHANGELOG.md:47

  88. msgid "Tuwunel now exposes its administration and /_tuwunel API paths"

  89. msgstr ""

  90. 

  91. #: ../../../CHANGELOG.md:49

  92. msgid "The [Tuwunel](docs/configuring-playbook-tuwunel.md) role previously routed only the `/_matrix` path through the reverse proxy. It now also exposes the two other API paths that Tuwunel serves."

  93. msgstr ""

  94. 

  95. #: ../../../CHANGELOG.md:51

  96. msgid "The Synapse-compatible administration API (`/_synapse/admin`) powers administration dashboards and moderation bots. As with Synapse and Dendrite, the playbook now exposes it automatically when such a tool is installed: publicly for [Ketesa](docs/configuring-playbook-ketesa.md) or [Element Admin](docs/configuring-playbook-element-admin.md), and on the internal entrypoint for [Draupnir](docs/configuring-playbook-bot-draupnir.md). To expose it yourself, set `matrix_tuwunel_container_labels_public_client_synapse_admin_api_enabled: true` (or the `internal_` variant)."

  97. msgstr ""

  98. 

  99. #: ../../../CHANGELOG.md:53

  100. msgid "Tuwunel also serves first-party routes under `/_tuwunel`, including its native OpenID Connect provider endpoints, which the reverse proxy must route for OIDC login to work. This path is now routed on the public entrypoint by default. To keep it off the public entrypoint, set `matrix_tuwunel_container_labels_public_tuwunel_api_enabled: false`."

  101. msgstr ""

  102. 

  103. #: ../../../CHANGELOG.md:56

  104. msgid "2026-07-18"

  105. msgstr ""

  106. 

  107. #: ../../../CHANGELOG.md:58

  108. msgid "LiveKit Server port configuration must be unambiguous now"

  109. msgstr ""

  110. 

  111. #: ../../../CHANGELOG.md:60

  112. msgid "This only affects you if you have configured a LiveKit Server RTC port range (`livekit_server_config_rtc_port_range_start` and `livekit_server_config_rtc_port_range_end`)."

  113. msgstr ""

  114. 

  115. #: ../../../CHANGELOG.md:62

  116. msgid "LiveKit only uses one of the two port configuration mechanisms: when a port range is defined, the multiplexed UDP port (`livekit_server_config_rtc_udp_port`) is ignored entirely. Previously, the role would silently render its default UDP port (7882) into the configuration alongside your port range, misleadingly suggesting that both are in effect."

  117. msgstr ""

  118. 

  119. #: ../../../CHANGELOG.md:64

  120. msgid "The role now asks you to make the choice explicit: if you define a port range, unset the UDP port by adding `livekit_server_config_rtc_udp_port: ''` to your `vars.yml` file. A validation error will guide you, if your configuration is affected."

  121. msgstr ""

  122. 

  123. #: ../../../CHANGELOG.md:67

  124. msgid "2026-07-17"

  125. msgstr ""

  126. 

  127. #: ../../../CHANGELOG.md:69

  128. msgid "prometheus-nginxlog-exporter metric names have changed"

  129. msgstr ""

  130. 

  131. #: ../../../CHANGELOG.md:71

  132. msgid "If you have enabled [metrics for nginx logs](docs/configuring-playbook-prometheus-grafana.md) (`prometheus_nginxlog_exporter_enabled: true`), note that the exporter's metric names have changed."

  133. msgstr ""

  134. 

  135. #: ../../../CHANGELOG.md:73

  136. msgid "The exporter's configuration used to ship a leftover `myprefix` placeholder as the metric name prefix, producing metrics like `myprefix_http_response_count_total`. The bundled Grafana dashboard queries unprefixed metric names (`http_response_count_total`), so it could never show any data (reported in [#3380](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3380))."

  137. msgstr ""

  138. 

  139. #: ../../../CHANGELOG.md:75

  140. msgid "Metric names are now unprefixed, matching the bundled dashboard, which should start working. Each metric carries a `namespace` label, whose value is now `nginx` (previously `matrix`); it is configurable via `prometheus_nginxlog_exporter_config_namespace_name`. If you have built custom dashboards or alerts on top of the old `myprefix_*` metric names, adjust them accordingly, or restore the old behavior by setting `prometheus_nginxlog_exporter_config_namespace_metrics_prefix: myprefix` in your `vars.yml` file."

  141. msgstr ""

  142. 

  143. #: ../../../CHANGELOG.md:78

  144. msgid "2026-07-16"

  145. msgstr ""

  146. 

  147. #: ../../../CHANGELOG.md:80

  148. msgid "(Backward Compatibility Break) Bridge variables have been renamed"

  149. msgstr ""

  150. 

  151. #: ../../../CHANGELOG.md:82

  152. 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)."

  153. msgstr ""

  154. 

  155. #: ../../../CHANGELOG.md:84

  156. 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."

  157. msgstr ""

  158. 

  159. #: ../../../CHANGELOG.md:86

  160. 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."

  161. msgstr ""

  162. 

  163. #: ../../../CHANGELOG.md:88

  164. msgid "The playbook will let you know if your configuration still uses old-style variable names."

  165. msgstr ""

  166. 

  167. #: ../../../CHANGELOG.md:90

  168. msgid "Here is the full rename map:"

  169. msgstr ""

  170. 

  171. #: ../../../CHANGELOG.md:0

  172. msgid "Old variable prefix"

  173. msgstr ""

  174. 

  175. #: ../../../CHANGELOG.md:0

  176. msgid "New variable prefix"

  177. msgstr ""

  178. 

  179. #: ../../../CHANGELOG.md:0

  180. msgid "`matrix_appservice_discord_`"

  181. msgstr ""

  182. 

  183. #: ../../../CHANGELOG.md:0

  184. msgid "`matrix_bridge_appservice_discord_`"

  185. msgstr ""

  186. 

  187. #: ../../../CHANGELOG.md:0

  188. msgid "`matrix_appservice_irc_`"

  189. msgstr ""

  190. 

  191. #: ../../../CHANGELOG.md:0

  192. msgid "`matrix_bridge_appservice_irc_`"

  193. msgstr ""

  194. 

  195. #: ../../../CHANGELOG.md:0

  196. msgid "`matrix_beeper_linkedin_`"

  197. msgstr ""

  198. 

  199. #: ../../../CHANGELOG.md:0

  200. msgid "`matrix_bridge_beeper_linkedin_`"

  201. msgstr ""

  202. 

  203. #: ../../../CHANGELOG.md:0

  204. msgid "`matrix_heisenbridge_`"

  205. msgstr ""

  206. 

  207. #: ../../../CHANGELOG.md:0

  208. msgid "`matrix_bridge_heisenbridge_`"

  209. msgstr ""

  210. 

  211. #: ../../../CHANGELOG.md:0

  212. msgid "`matrix_hookshot_`"

  213. msgstr ""

  214. 

  215. #: ../../../CHANGELOG.md:0

  216. msgid "`matrix_bridge_hookshot_`"

  217. msgstr ""

  218. 

  219. #: ../../../CHANGELOG.md:0

  220. msgid "`matrix_mautrix_androidsms_`"

  221. msgstr ""

  222. 

  223. #: ../../../CHANGELOG.md:0

  224. msgid "`matrix_bridge_mautrix_wsproxy_androidsms_`"

  225. msgstr ""

  226. 

  227. #: ../../../CHANGELOG.md:0

  228. msgid "`matrix_mautrix_bluesky_`"

  229. msgstr ""

  230. 

  231. #: ../../../CHANGELOG.md:0

  232. msgid "`matrix_bridge_mautrix_bluesky_`"

  233. msgstr ""

  234. 

  235. #: ../../../CHANGELOG.md:0

  236. msgid "`matrix_mautrix_discord_`"

  237. msgstr ""

  238. 

  239. #: ../../../CHANGELOG.md:0

  240. msgid "`matrix_bridge_mautrix_discord_`"

  241. msgstr ""

  242. 

  243. #: ../../../CHANGELOG.md:0

  244. msgid "`matrix_mautrix_gmessages_`"

  245. msgstr ""

  246. 

  247. #: ../../../CHANGELOG.md:0

  248. msgid "`matrix_bridge_mautrix_gmessages_`"

  249. msgstr ""

  250. 

  251. #: ../../../CHANGELOG.md:0

  252. msgid "`matrix_mautrix_googlechat_`"

  253. msgstr ""

  254. 

  255. #: ../../../CHANGELOG.md:0

  256. msgid "`matrix_bridge_mautrix_googlechat_`"

  257. msgstr ""

  258. 

  259. #: ../../../CHANGELOG.md:0

  260. msgid "`matrix_mautrix_gvoice_`"

  261. msgstr ""

  262. 

  263. #: ../../../CHANGELOG.md:0

  264. msgid "`matrix_bridge_mautrix_gvoice_`"

  265. msgstr ""

  266. 

  267. #: ../../../CHANGELOG.md:0

  268. msgid "`matrix_mautrix_imessage_`"

  269. msgstr ""

  270. 

  271. #: ../../../CHANGELOG.md:0

  272. msgid "`matrix_bridge_mautrix_wsproxy_imessage_`"

  273. msgstr ""

  274. 

  275. #: ../../../CHANGELOG.md:0

  276. msgid "`matrix_mautrix_meta_instagram_`"

  277. msgstr ""

  278. 

  279. #: ../../../CHANGELOG.md:0

  280. msgid "`matrix_bridge_mautrix_meta_instagram_`"

  281. msgstr ""

  282. 

  283. #: ../../../CHANGELOG.md:0

  284. msgid "`matrix_mautrix_meta_messenger_`"

  285. msgstr ""

  286. 

  287. #: ../../../CHANGELOG.md:0

  288. msgid "`matrix_bridge_mautrix_meta_messenger_`"

  289. msgstr ""

  290. 

  291. #: ../../../CHANGELOG.md:0

  292. msgid "`matrix_mautrix_signal_`"

  293. msgstr ""

  294. 

  295. #: ../../../CHANGELOG.md:0

  296. msgid "`matrix_bridge_mautrix_signal_`"

  297. msgstr ""

  298. 

  299. #: ../../../CHANGELOG.md:0

  300. msgid "`matrix_mautrix_slack_`"

  301. msgstr ""

  302. 

  303. #: ../../../CHANGELOG.md:0

  304. msgid "`matrix_bridge_mautrix_slack_`"

  305. msgstr ""

  306. 

  307. #: ../../../CHANGELOG.md:0

  308. msgid "`matrix_mautrix_telegram_`"

  309. msgstr ""

  310. 

  311. #: ../../../CHANGELOG.md:0

  312. msgid "`matrix_bridge_mautrix_telegram_`"

  313. msgstr ""

  314. 

  315. #: ../../../CHANGELOG.md:0

  316. msgid "`matrix_mautrix_twitter_`"

  317. msgstr ""

  318. 

  319. #: ../../../CHANGELOG.md:0

  320. msgid "`matrix_bridge_mautrix_twitter_`"

  321. msgstr ""

  322. 

  323. #: ../../../CHANGELOG.md:0

  324. msgid "`matrix_mautrix_whatsapp_`"

  325. msgstr ""

  326. 

  327. #: ../../../CHANGELOG.md:0

  328. msgid "`matrix_bridge_mautrix_whatsapp_`"

  329. msgstr ""

  330. 

  331. #: ../../../CHANGELOG.md:0

  332. msgid "`matrix_mautrix_wsproxy_`"

  333. msgstr ""

  334. 

  335. #: ../../../CHANGELOG.md:0

  336. msgid "`matrix_bridge_mautrix_wsproxy_`"

  337. msgstr ""

  338. 

  339. #: ../../../CHANGELOG.md:0

  340. msgid "`matrix_meshtastic_relay_`"

  341. msgstr ""

  342. 

  343. #: ../../../CHANGELOG.md:0

  344. msgid "`matrix_bridge_meshtastic_relay_`"

  345. msgstr ""

  346. 

  347. #: ../../../CHANGELOG.md:0

  348. msgid "`matrix_mx_puppet_groupme_`"

  349. msgstr ""

  350. 

  351. #: ../../../CHANGELOG.md:0

  352. msgid "`matrix_bridge_mx_puppet_groupme_`"

  353. msgstr ""

  354. 

  355. #: ../../../CHANGELOG.md:0

  356. msgid "`matrix_mx_puppet_steam_`"

  357. msgstr ""

  358. 

  359. #: ../../../CHANGELOG.md:0

  360. msgid "`matrix_bridge_mx_puppet_steam_`"

  361. msgstr ""

  362. 

  363. #: ../../../CHANGELOG.md:0

  364. msgid "`matrix_postmoogle_`"

  365. msgstr ""

  366. 

  367. #: ../../../CHANGELOG.md:0

  368. msgid "`matrix_bridge_postmoogle_`"

  369. msgstr ""

  370. 

  371. #: ../../../CHANGELOG.md:0

  372. msgid "`matrix_rustpush_bridge_`"

  373. msgstr ""

  374. 

  375. #: ../../../CHANGELOG.md:0

  376. msgid "`matrix_bridge_rustpush_`"

  377. msgstr ""

  378. 

  379. #: ../../../CHANGELOG.md:0

  380. msgid "`matrix_sms_bridge_`"

  381. msgstr ""

  382. 

  383. #: ../../../CHANGELOG.md:0

  384. msgid "`matrix_bridge_sms_`"

  385. msgstr ""

  386. 

  387. #: ../../../CHANGELOG.md:0

  388. msgid "`matrix_steam_bridge_`"

  389. msgstr ""

  390. 

  391. #: ../../../CHANGELOG.md:0

  392. msgid "`matrix_bridge_steam_`"

  393. msgstr ""

  394. 

  395. #: ../../../CHANGELOG.md:0

  396. msgid "`matrix_wechat_`"

  397. msgstr ""

  398. 

  399. #: ../../../CHANGELOG.md:0

  400. msgid "`matrix_bridge_wechat_`"

  401. msgstr ""

  402. 

  403. #: ../../../CHANGELOG.md:123

  404. msgid "A few special cases beyond the prefix map:"

  405. msgstr ""

  406. 

  407. #: ../../../CHANGELOG.md:125

  408. 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`"

  409. msgstr ""

  410. 

  411. #: ../../../CHANGELOG.md:126

  412. msgid "`matrix_playbook_migration_matrix_postmoogle_migration_validation_enabled` is now `matrix_playbook_migration_matrix_bridge_postmoogle_migration_validation_enabled`"

  413. msgstr ""

  414. 

  415. #: ../../../CHANGELOG.md:128

  416. msgid "You can update your `vars.yml` file automatically with this `sed` command (on macOS, use `sed -i ''` instead of `sed -i`):"

  417. msgstr ""

  418. 

  419. #: ../../../CHANGELOG.md:165

  420. 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."

  421. msgstr ""

  422. 

  423. #: ../../../CHANGELOG.md:167

  424. 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."

  425. msgstr ""

  426. 

  427. #: ../../../CHANGELOG.md:169

  428. msgid "2026-07-15"

  429. msgstr ""

  430. 

  431. #: ../../../CHANGELOG.md:171

  432. msgid "Google Voice bridging"

  433. msgstr ""

  434. 

  435. #: ../../../CHANGELOG.md:173

  436. 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."

  437. msgstr ""

  438. 

  439. #: ../../../CHANGELOG.md:175

  440. 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."

  441. msgstr ""

  442. 

  443. #: ../../../CHANGELOG.md:177

  444. msgid "matrix-appservice-kakaotalk has been removed from the playbook"

  445. msgstr ""

  446. 

  447. #: ../../../CHANGELOG.md:179

  448. 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."

  449. msgstr ""

  450. 

  451. #: ../../../CHANGELOG.md:181

  452. 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)."

  453. msgstr ""

  454. 

  455. #: ../../../CHANGELOG.md:183

  456. msgid "Dedicated CAPTCHA variables for Matrix Authentication Service"

  457. msgstr ""

  458. 

  459. #: ../../../CHANGELOG.md:185

  460. 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."

  461. msgstr ""

  462. 

  463. #: ../../../CHANGELOG.md:187

  464. msgid "2026-07-14"

  465. msgstr ""

  466. 

  467. #: ../../../CHANGELOG.md:189

  468. msgid "The playbook no longer ships a custom welcome page for Element Web"

  469. msgstr ""

  470. 

  471. #: ../../../CHANGELOG.md:191

  472. 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."

  473. msgstr ""

  474. 

  475. #: ../../../CHANGELOG.md:193

  476. 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`."

  477. msgstr ""

  478. 

  479. #: ../../../CHANGELOG.md:195

  480. msgid "Most welcome page customizations keep working, because they go through Element Web's branding configuration, which the new welcome page still honors:"

  481. msgstr ""

  482. 

  483. #: ../../../CHANGELOG.md:197

  484. msgid "a custom logo, via `matrix_client_element_welcome_logo` (or `matrix_client_element_branding_auth_header_logo_url`)"

  485. msgstr ""

  486. 

  487. #: ../../../CHANGELOG.md:198

  488. msgid "a custom background, via `matrix_client_element_branding_welcome_background_url`"

  489. msgstr ""

  490. 

  491. #: ../../../CHANGELOG.md:200

  492. msgid "If you need a fully custom welcome page, you can self-host an HTML page and point Element Web at it, like this:"

  493. msgstr ""

  494. 

  495. #: ../../../CHANGELOG.md:211

  496. msgid "BorgBackup now includes Synapse's local thumbnails"

  497. msgstr ""

  498. 

  499. #: ../../../CHANGELOG.md:213

  500. 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."

  501. msgstr ""

  502. 

  503. #: ../../../CHANGELOG.md:215

  504. 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."

  505. msgstr ""

  506. 

  507. #: ../../../CHANGELOG.md:217

  508. 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`."

  509. msgstr ""

  510. 

  511. #: ../../../CHANGELOG.md:219

  512. msgid "2026-07-12"

  513. msgstr ""

  514. 

  515. #: ../../../CHANGELOG.md:221

  516. msgid "matrix-registration-bot has been removed from the playbook"

  517. msgstr ""

  518. 

  519. #: ../../../CHANGELOG.md:223

  520. 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."

  521. msgstr ""

  522. 

  523. #: ../../../CHANGELOG.md:225

  524. 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)."

  525. msgstr ""

  526. 

  527. #: ../../../CHANGELOG.md:227

  528. msgid "Continuwuity v26 no longer supports LDAP"

  529. msgstr ""

  530. 

  531. #: ../../../CHANGELOG.md:229

  532. 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))."

  533. msgstr ""

  534. 

  535. #: ../../../CHANGELOG.md:231

  536. 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)."

  537. msgstr ""

  538. 

  539. #: ../../../CHANGELOG.md:233

  540. msgid "2026-06-29"

  541. msgstr ""

  542. 

  543. #: ../../../CHANGELOG.md:235

  544. msgid "Support for running on Synology DSM"

  545. msgstr ""

  546. 

  547. #: ../../../CHANGELOG.md:237

  548. msgid "Thanks to [cksit](https://github.com/cksit), the playbook can now run on [Synology DSM](https://www.synology.com/dsm) 7 and later."

  549. msgstr ""

  550. 

  551. #: ../../../CHANGELOG.md:239

  552. 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."

  553. msgstr ""

  554. 

  555. #: ../../../CHANGELOG.md:241

  556. msgid "To get started, see the new [Configuring Synology DSM](./docs/configuring-playbook-synology.md) documentation page."

  557. msgstr ""

  558. 

  559. #: ../../../CHANGELOG.md:243

  560. msgid "Mautrix bridges now expose their API (for Mautrix Manager and similar tools)"

  561. msgstr ""

  562. 

  563. #: ../../../CHANGELOG.md:245

  564. 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."

  565. msgstr ""

  566. 

  567. #: ../../../CHANGELOG.md:247

  568. 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."

  569. msgstr ""

  570. 

  571. #: ../../../CHANGELOG.md:249

  572. 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."

  573. msgstr ""

  574. 

  575. #: ../../../CHANGELOG.md:251

  576. 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."

  577. msgstr ""

  578. 

  579. #: ../../../CHANGELOG.md:253

  580. msgid "2026-06-28"

  581. msgstr ""

  582. 

  583. #: ../../../CHANGELOG.md:255

  584. msgid "baibot now supports Venice, our recommended provider"

  585. msgstr ""

  586. 

  587. #: ../../../CHANGELOG.md:257

  588. 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."

  589. msgstr ""

  590. 

  591. #: ../../../CHANGELOG.md:259

  592. msgid "Enabling it takes a preset toggle and an API key:"

  593. msgstr ""

  594. 

  595. #: ../../../CHANGELOG.md:267

  596. 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."

  597. msgstr ""

  598. 

  599. #: ../../../CHANGELOG.md:269

  600. msgid "2026-06-24"

  601. msgstr ""

  602. 

  603. #: ../../../CHANGELOG.md:271

  604. msgid "Support for bridging to iMessage via RustPush"

  605. msgstr ""

  606. 

  607. #: ../../../CHANGELOG.md:273

  608. 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))."

  609. msgstr ""

  610. 

  611. #: ../../../CHANGELOG.md:275

  612. 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."

  613. msgstr ""

  614. 

  615. #: ../../../CHANGELOG.md:277

  616. msgid "To learn more, see our [Setting up RustPush (iMessage) bridging](./docs/configuring-playbook-bridge-rustpush.md) documentation page."

  617. msgstr ""

  618. 

  619. #: ../../../CHANGELOG.md:279

  620. msgid "2026-05-24"

  621. msgstr ""

  622. 

  623. #: ../../../CHANGELOG.md:281

  624. msgid "matrix-ldap-registration-proxy has been removed from the playbook"

  625. msgstr ""

  626. 

  627. #: ../../../CHANGELOG.md:283

  628. 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."

  629. msgstr ""

  630. 

  631. #: ../../../CHANGELOG.md:285

  632. 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)."

  633. msgstr ""

  634. 

  635. #: ../../../CHANGELOG.md:287

  636. msgid "2026-05-23"

  637. msgstr ""

  638. 

  639. #: ../../../CHANGELOG.md:289

  640. msgid "Go-NEB has been removed from the playbook"

  641. msgstr ""

  642. 

  643. #: ../../../CHANGELOG.md:291

  644. msgid "[Go-NEB](./docs/configuring-playbook-bot-go-neb.md) has been removed from the playbook, as it has been discontinued since June 2023."

  645. msgstr ""

  646. 

  647. #: ../../../CHANGELOG.md:293

  648. 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)."

  649. msgstr ""

  650. 

  651. #: ../../../CHANGELOG.md:295

  652. msgid "2026-05-19"

  653. msgstr ""

  654. 

  655. #: ../../../CHANGELOG.md:297

  656. msgid "matrix-registration has been removed from the playbook"

  657. msgstr ""

  658. 

  659. #: ../../../CHANGELOG.md:299

  660. 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."

  661. msgstr ""

  662. 

  663. #: ../../../CHANGELOG.md:301

  664. 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)."

  665. msgstr ""

  666. 

  667. #: ../../../CHANGELOG.md:303

  668. msgid "2026-05-18"

  669. msgstr ""

  670. 

  671. #: ../../../CHANGELOG.md:305

  672. msgid "LiveKit Server has been upgraded to v1.12.0"

  673. msgstr ""

  674. 

  675. #: ../../../CHANGELOG.md:307

  676. 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."

  677. msgstr ""

  678. 

  679. #: ../../../CHANGELOG.md:309

  680. msgid "This release tightens TURN security:"

  681. msgstr ""

  682. 

  683. #: ../../../CHANGELOG.md:311

  684. msgid "**TURN credentials now carry a TTL** (default: 300 seconds), exposed via `livekit_server_config_turn_ttl_seconds`."

  685. msgstr ""

  686. 

  687. #: ../../../CHANGELOG.md:312

  688. 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`."

  689. msgstr ""

  690. 

  691. #: ../../../CHANGELOG.md:314

  692. 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`:"

  693. msgstr ""

  694. 

  695. #: ../../../CHANGELOG.md:322

  696. 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."

  697. msgstr ""

  698. 

  699. #: ../../../CHANGELOG.md:325

  700. msgid "2026-05-07"

  701. msgstr ""

  702. 

  703. #: ../../../CHANGELOG.md:327

  704. msgid "Tuwunel support"

  705. msgstr ""

  706. 

  707. #: ../../../CHANGELOG.md:329

  708. 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."

  709. msgstr ""

  710. 

  711. #: ../../../CHANGELOG.md:331

  712. 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."

  713. msgstr ""

  714. 

  715. #: ../../../CHANGELOG.md:333

  716. #: ../../../CHANGELOG.md:837

  717. #: ../../../CHANGELOG.md:1050

  718. msgid "Existing installations do **not** need to be updated. **Synapse is still the default homeserver implementation** installed by the playbook."

  719. msgstr ""

  720. 

  721. #: ../../../CHANGELOG.md:335

  722. 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."

  723. msgstr ""

  724. 

  725. #: ../../../CHANGELOG.md:337

  726. 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."

  727. msgstr ""

  728. 

  729. #: ../../../CHANGELOG.md:340

  730. msgid "2026-04-24"

  731. msgstr ""

  732. 

  733. #: ../../../CHANGELOG.md:342

  734. msgid "Support for bridging to Meshtastic via meshtastic-matrix-relay"

  735. msgstr ""

  736. 

  737. #: ../../../CHANGELOG.md:344

  738. 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)."

  739. msgstr ""

  740. 

  741. #: ../../../CHANGELOG.md:346

  742. msgid "To learn more, see our [Setting up a Matrix <-> Meshtastic bridge](./docs/configuring-playbook-bridge-meshtastic-relay.md) documentation page."

  743. msgstr ""

  744. 

  745. #: ../../../CHANGELOG.md:348

  746. msgid "(BC Break) mautrix-telegram has been rewritten in Go (bridgev2)"

  747. msgstr ""

  748. 

  749. #: ../../../CHANGELOG.md:350

  750. 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.)."

  751. msgstr ""

  752. 

  753. #: ../../../CHANGELOG.md:352

  754. 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."

  755. msgstr ""

  756. 

  757. #: ../../../CHANGELOG.md:354

  758. 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."

  759. msgstr ""

  760. 

  761. #: ../../../CHANGELOG.md:356

  762. msgid "Playbook-specific things to know. The playbook will fail loudly if you're affected:"

  763. msgstr ""

  764. 

  765. #: ../../../CHANGELOG.md:358

  766. 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."

  767. msgstr ""

  768. 

  769. #: ../../../CHANGELOG.md:359

  770. 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`."

  771. msgstr ""

  772. 

  773. #: ../../../CHANGELOG.md:360

  774. 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."

  775. msgstr ""

  776. 

  777. #: ../../../CHANGELOG.md:361

  778. msgid "**Custom `matrix_mautrix_telegram_bridge_permissions`**: map `relaybot` to `relay`, `puppeting` to `user`, `full` to `user`. Validated at playbook time."

  779. msgstr ""

  780. 

  781. #: ../../../CHANGELOG.md:363

  782. msgid "2026-04-03"

  783. msgstr ""

  784. 

  785. #: ../../../CHANGELOG.md:365

  786. msgid "(BC Break) Synapse Admin (fork by etke.cc) is now Ketesa"

  787. msgstr ""

  788. 

  789. #: ../../../CHANGELOG.md:367

  790. 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/)."

  791. msgstr ""

  792. 

  793. #: ../../../CHANGELOG.md:369

  794. msgid "Ketesa is a zero-configuration drop-in replacement for Synapse Admin: no server-side changes required, just update the role variables."

  795. msgstr ""

  796. 

  797. #: ../../../CHANGELOG.md:371

  798. 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`."

  799. msgstr ""

  800. 

  801. #: ../../../CHANGELOG.md:373

  802. 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."

  803. msgstr ""

  804. 

  805. #: ../../../CHANGELOG.md:375

  806. msgid "The playbook will automatically detect leftover `matrix_synapse_admin_*` variables and fail with a helpful message listing what needs to be renamed."

  807. msgstr ""

  808. 

  809. #: ../../../CHANGELOG.md:377

  810. 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)."

  811. msgstr ""

  812. 

  813. #: ../../../CHANGELOG.md:379

  814. msgid "See the [Ketesa documentation](docs/configuring-playbook-ketesa.md) for details."

  815. msgstr ""

  816. 

  817. #: ../../../CHANGELOG.md:381

  818. msgid "2026-04-02"

  819. msgstr ""

  820. 

  821. #: ../../../CHANGELOG.md:383

  822. msgid "(BC Break) Draupnir for all Self Service Provisioning is now disabled by default"

  823. msgstr ""

  824. 

  825. #: ../../../CHANGELOG.md:385

  826. 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.."

  827. msgstr ""

  828. 

  829. #: ../../../CHANGELOG.md:387

  830. msgid "[Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) now ships with `allowSelfServiceProvisioning: false` as default upstream and in this playbook."

  831. msgstr ""

  832. 

  833. #: ../../../CHANGELOG.md:389

  834. msgid "This means users can no longer provision Draupnir instances by inviting the appservice bot unless you explicitly opt in."

  835. msgstr ""

  836. 

  837. #: ../../../CHANGELOG.md:391

  838. 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."

  839. msgstr ""

  840. 

  841. #: ../../../CHANGELOG.md:393

  842. msgid "If you want to enable Self Service Provisioning, add the following to your `vars.yml`:"

  843. msgstr ""

  844. 

  845. #: ../../../CHANGELOG.md:400

  846. msgid "2026-03-23"

  847. msgstr ""

  848. 

  849. #: ../../../CHANGELOG.md:402

  850. msgid "Migration validation system introduced"

  851. msgstr ""

  852. 

  853. #: ../../../CHANGELOG.md:404

  854. msgid "Previously, when updating your setup, you had to remember to read the [CHANGELOG](CHANGELOG.md) file or risk breakage."

  855. msgstr ""

  856. 

  857. #: ../../../CHANGELOG.md:406

  858. 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)."

  859. msgstr ""

  860. 

  861. #: ../../../CHANGELOG.md:409

  862. msgid "A new `matrix_playbook_migration_validated_version` variable has been introduced."

  863. msgstr ""

  864. 

  865. #: ../../../CHANGELOG.md:411

  866. 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."

  867. msgstr ""

  868. 

  869. #: ../../../CHANGELOG.md:413

  870. msgid "**Existing users** will need to add the following to their `vars.yml` file after reviewing all changelog entries up to now:"

  871. msgstr ""

  872. 

  873. #: ../../../CHANGELOG.md:419

  874. msgid "Going forward, whenever a breaking change is introduced the playbook will:"

  875. msgstr ""

  876. 

  877. #: ../../../CHANGELOG.md:421

  878. msgid "bump its expected version value (`matrix_playbook_migration_expected_version`), causing a discrepancy with what you validated (`matrix_playbook_migration_validated_version`)"

  879. msgstr ""

  880. 

  881. #: ../../../CHANGELOG.md:423

  882. msgid "fail when you run it with a helpful message listing what changed and linking to the relevant changelog entries"

  883. msgstr ""

  884. 

  885. #: ../../../CHANGELOG.md:425

  886. msgid "After reviewing and adapting your setup, you simply update the variable to the new version."

  887. msgstr ""

  888. 

  889. #: ../../../CHANGELOG.md:427

  890. msgid "If you'd like to live dangerously and skip these checks (not recommended), you can set this once and be done with it:"

  891. msgstr ""

  892. 

  893. #: ../../../CHANGELOG.md:433

  894. msgid "2026-03-19"

  895. msgstr ""

  896. 

  897. #: ../../../CHANGELOG.md:435

  898. msgid "Matrix Authentication Service now prefers UNIX sockets for playbook-managed Postgres"

  899. msgstr ""

  900. 

  901. #: ../../../CHANGELOG.md:437

  902. 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."

  903. msgstr ""

  904. 

  905. #: ../../../CHANGELOG.md:439

  906. 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."

  907. msgstr ""

  908. 

  909. #: ../../../CHANGELOG.md:441

  910. msgid "If you use an external Postgres server for MAS, this does not change your setup."

  911. msgstr ""

  912. 

  913. #: ../../../CHANGELOG.md:443

  914. #: ../../../CHANGELOG.md:459

  915. msgid "If you'd like to keep the previous TCP-based behavior, add the following configuration to your `vars.yml`:"

  916. msgstr ""

  917. 

  918. #: ../../../CHANGELOG.md:449

  919. msgid "2026-03-17"

  920. msgstr ""

  921. 

  922. #: ../../../CHANGELOG.md:451

  923. msgid "Synapse now prefers UNIX sockets for playbook-managed Postgres and Valkey"

  924. msgstr ""

  925. 

  926. #: ../../../CHANGELOG.md:453

  927. 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."

  928. msgstr ""

  929. 

  930. #: ../../../CHANGELOG.md:455

  931. msgid "This reduces unnecessary container-network wiring and keeps local IPC off the network stack, which is a bit simpler and slightly more secure."

  932. msgstr ""

  933. 

  934. #: ../../../CHANGELOG.md:457

  935. msgid "If you use an external Postgres server or external Redis/Valkey for Synapse, this does not change your setup."

  936. msgstr ""

  937. 

  938. #: ../../../CHANGELOG.md:466

  939. msgid "2026-03-01"

  940. msgstr ""

  941. 

  942. #: ../../../CHANGELOG.md:468

  943. msgid "(Potential BC Break) Synapse S3 media prefix is now applied consistently"

  944. msgstr ""

  945. 

  946. #: ../../../CHANGELOG.md:470

  947. msgid "The `matrix_synapse_ext_synapse_s3_storage_provider_config_prefix` variable is now wired consistently for both:"

  948. msgstr ""

  949. 

  950. #: ../../../CHANGELOG.md:472

  951. msgid "the Synapse `s3_storage_provider` module configuration"

  952. msgstr ""

  953. 

  954. #: ../../../CHANGELOG.md:473

  955. msgid "the `matrix-synapse-s3-storage-provider-migrate` migration script (`s3_media_upload --prefix`)"

  956. msgstr ""

  957. 

  958. #: ../../../CHANGELOG.md:475

  959. msgid "Previously, this variable could be set, but was not effectively applied by either of these paths."

  960. msgstr ""

  961. 

  962. #: ../../../CHANGELOG.md:477

  963. 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."

  964. msgstr ""

  965. 

  966. #: ../../../CHANGELOG.md:479

  967. 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."

  968. msgstr ""

  969. 

  970. #: ../../../CHANGELOG.md:481

  971. msgid "2026-02-26"

  972. msgstr ""

  973. 

  974. #: ../../../CHANGELOG.md:483

  975. msgid "Internal refactor: merged the Synapse reverse-proxy companion role into `matrix-synapse`"

  976. msgstr ""

  977. 

  978. #: ../../../CHANGELOG.md:485

  979. msgid "The standalone `matrix-synapse-reverse-proxy-companion` role has been merged into the [matrix-synapse](roles/custom/matrix-synapse/) role."

  980. msgstr ""

  981. 

  982. #: ../../../CHANGELOG.md:487

  983. 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."

  984. msgstr ""

  985. 

  986. #: ../../../CHANGELOG.md:489

  987. msgid "Compatibility note: existing companion-specific tags (`setup-synapse-reverse-proxy-companion` and `install-synapse-reverse-proxy-companion`) are still available."

  988. msgstr ""

  989. 

  990. #: ../../../CHANGELOG.md:491

  991. 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."

  992. msgstr ""

  993. 

  994. #: ../../../CHANGELOG.md:493

  995. msgid "2026-02-21"

  996. msgstr ""

  997. 

  998. #: ../../../CHANGELOG.md:495

  999. msgid "(BC Break) coturn is no longer auto-enabled by default"

  1000. msgstr ""

  1001. 

  1002. #: ../../../CHANGELOG.md:497

  1003. msgid "By default, the [coturn](./docs/configuring-playbook-turn.md) TURN server component is no longer enabled for every deployment."

  1004. msgstr ""

  1005. 

  1006. #: ../../../CHANGELOG.md:499

  1007. msgid "This reduces resources and attach surface for deployments which:"

  1008. msgstr ""

  1009. 

  1010. #: ../../../CHANGELOG.md:501

  1011. msgid "either don't need calls at all"

  1012. msgstr ""

  1013. 

  1014. #: ../../../CHANGELOG.md:502

  1015. msgid "or use the modern [Matrix RTC](docs/configuring-playbook-matrix-rtc.md)/[Element Call](docs/configuring-playbook-element-call.md) stack."

  1016. msgstr ""

  1017. 

  1018. #: ../../../CHANGELOG.md:504

  1019. 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."

  1020. msgstr ""

  1021. 

  1022. #: ../../../CHANGELOG.md:506

  1023. 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`."

  1024. msgstr ""

  1025. 

  1026. #: ../../../CHANGELOG.md:508

  1027. msgid "To restore the old behavior (needed for legacy call setups), add the following configuration to your `vars.yml`:"

  1028. msgstr ""

  1029. 

  1030. #: ../../../CHANGELOG.md:517

  1031. msgid "LiveKit TURN TLS is now automatically fronted by playbook-managed Traefik"

  1032. msgstr ""

  1033. 

  1034. #: ../../../CHANGELOG.md:519

  1035. 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."

  1036. msgstr ""

  1037. 

  1038. #: ../../../CHANGELOG.md:521

  1039. 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."

  1040. msgstr ""

  1041. 

  1042. #: ../../../CHANGELOG.md:523

  1043. 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."

  1044. msgstr ""

  1045. 

  1046. #: ../../../CHANGELOG.md:525

  1047. msgid "2026-02-17"

  1048. msgstr ""

  1049. 

  1050. #: ../../../CHANGELOG.md:527

  1051. msgid "(BC Break) prometheus-nginxlog-exporter role has been relocated and variable names need adjustments"

  1052. msgstr ""

  1053. 

  1054. #: ../../../CHANGELOG.md:529

  1055. 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."

  1056. msgstr ""

  1057. 

  1058. #: ../../../CHANGELOG.md:531

  1059. 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."

  1060. msgstr ""

  1061. 

  1062. #: ../../../CHANGELOG.md:533

  1063. #: ../../../CHANGELOG.md:595

  1064. #: ../../../CHANGELOG.md:605

  1065. #: ../../../CHANGELOG.md:666

  1066. #: ../../../CHANGELOG.md:688

  1067. #: ../../../CHANGELOG.md:1223

  1068. msgid "As always, the playbook would let you know about this and point out any variables you may have missed."

  1069. msgstr ""

  1070. 

  1071. #: ../../../CHANGELOG.md:535

  1072. msgid "synapse-auto-invite-accept has been removed from the playbook"

  1073. msgstr ""

  1074. 

  1075. #: ../../../CHANGELOG.md:537

  1076. 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)."

  1077. msgstr ""

  1078. 

  1079. #: ../../../CHANGELOG.md:539

  1080. msgid "See [this section](./docs/configuring-playbook-synapse-auto-accept-invite.md#native-alternative) for details about how to enable the function on Synapse."

  1081. msgstr ""

  1082. 

  1083. #: ../../../CHANGELOG.md:541

  1084. 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`."

  1085. msgstr ""

  1086. 

  1087. #: ../../../CHANGELOG.md:543

  1088. msgid "2026-02-16"

  1089. msgstr ""

  1090. 

  1091. #: ../../../CHANGELOG.md:545

  1092. msgid "matrix-appservice-slack has been removed from the playbook"

  1093. msgstr ""

  1094. 

  1095. #: ../../../CHANGELOG.md:547

  1096. 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."

  1097. msgstr ""

  1098. 

  1099. #: ../../../CHANGELOG.md:549

  1100. 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)."

  1101. msgstr ""

  1102. 

  1103. #: ../../../CHANGELOG.md:551

  1104. 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."

  1105. msgstr ""

  1106. 

  1107. #: ../../../CHANGELOG.md:553

  1108. msgid "2026-02-13"

  1109. msgstr ""

  1110. 

  1111. #: ../../../CHANGELOG.md:555

  1112. msgid "Conditional service restart for `install-*` commands"

  1113. msgstr ""

  1114. 

  1115. #: ../../../CHANGELOG.md:557

  1116. 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."

  1117. msgstr ""

  1118. 

  1119. #: ../../../CHANGELOG.md:559

  1120. msgid "When running with `setup-*` tags (e.g. `setup-all`, `setup-synapse`), all services continue to be unconditionally restarted as before."

  1121. msgstr ""

  1122. 

  1123. #: ../../../CHANGELOG.md:561

  1124. 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."

  1125. msgstr ""

  1126. 

  1127. #: ../../../CHANGELOG.md:563

  1128. msgid "Some benchmarks for `just install-service traefik` when Traefik settings did not change:"

  1129. msgstr ""

  1130. 

  1131. #: ../../../CHANGELOG.md:565

  1132. msgid "**Before**:"

  1133. msgstr ""

  1134. 

  1135. #: ../../../CHANGELOG.md:566

  1136. msgid "total time: ~56 seconds 🐌"

  1137. msgstr ""

  1138. 

  1139. #: ../../../CHANGELOG.md:567

  1140. msgid "Traefik restarted: yes (unnecessarily) ❌"

  1141. msgstr ""

  1142. 

  1143. #: ../../../CHANGELOG.md:568

  1144. msgid "dependent services restarted: yes, all of them ❌"

  1145. msgstr ""

  1146. 

  1147. #: ../../../CHANGELOG.md:569

  1148. msgid "**After**:"

  1149. msgstr ""

  1150. 

  1151. #: ../../../CHANGELOG.md:570

  1152. msgid "total time: ~27 seconds ⚡"

  1153. msgstr ""

  1154. 

  1155. #: ../../../CHANGELOG.md:571

  1156. msgid "Traefik restarted: no ✅"

  1157. msgstr ""

  1158. 

  1159. #: ../../../CHANGELOG.md:572

  1160. msgid "dependent services restarted: no ✅"

  1161. msgstr ""

  1162. 

  1163. #: ../../../CHANGELOG.md:574

  1164. 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."

  1165. msgstr ""

  1166. 

  1167. #: ../../../CHANGELOG.md:577

  1168. msgid "2026-02-12"

  1169. msgstr ""

  1170. 

  1171. #: ../../../CHANGELOG.md:579

  1172. msgid "Dimension integration manager has been removed from the playbook"

  1173. msgstr ""

  1174. 

  1175. #: ../../../CHANGELOG.md:581

  1176. msgid "The [Dimension integration manager](./docs/configuring-playbook-dimension.md) has been removed from the playbook, as it has been unmaintained."

  1177. msgstr ""

  1178. 

  1179. #: ../../../CHANGELOG.md:583

  1180. 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)."

  1181. msgstr ""

  1182. 

  1183. #: ../../../CHANGELOG.md:585

  1184. msgid "(BC Break) Hydrogen role has been relocated and variable names need adjustments"

  1185. msgstr ""

  1186. 

  1187. #: ../../../CHANGELOG.md:587

  1188. msgid "The role for Hydrogen has been relocated to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization."

  1189. msgstr ""

  1190. 

  1191. #: ../../../CHANGELOG.md:589

  1192. 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."

  1193. msgstr ""

  1194. 

  1195. #: ../../../CHANGELOG.md:591

  1196. #: ../../../CHANGELOG.md:684

  1197. msgid "You need to do the following replacement:"

  1198. msgstr ""

  1199. 

  1200. #: ../../../CHANGELOG.md:593

  1201. msgid "`matrix_client_hydrogen_` -> `hydrogen_`"

  1202. msgstr ""

  1203. 

  1204. #: ../../../CHANGELOG.md:597

  1205. msgid "2026-02-11"

  1206. msgstr ""

  1207. 

  1208. #: ../../../CHANGELOG.md:599

  1209. msgid "(BC Break) coturn role has been relocated and variable names need adjustments"

  1210. msgstr ""

  1211. 

  1212. #: ../../../CHANGELOG.md:601

  1213. msgid "The role for coturn has been relocated to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization."

  1214. msgstr ""

  1215. 

  1216. #: ../../../CHANGELOG.md:603

  1217. 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."

  1218. msgstr ""

  1219. 

  1220. #: ../../../CHANGELOG.md:607

  1221. msgid "conduwuit has been removed from the playbook"

  1222. msgstr ""

  1223. 

  1224. #: ../../../CHANGELOG.md:609

  1225. msgid "[conduwuit](./docs/configuring-playbook-conduwuit.md) has been removed from the playbook, as it has been abandoned."

  1226. msgstr ""

  1227. 

  1228. #: ../../../CHANGELOG.md:611

  1229. 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)."

  1230. msgstr ""

  1231. 

  1232. #: ../../../CHANGELOG.md:613

  1233. 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."

  1234. msgstr ""

  1235. 

  1236. #: ../../../CHANGELOG.md:615

  1237. msgid "2026-02-09"

  1238. msgstr ""

  1239. 

  1240. #: ../../../CHANGELOG.md:617

  1241. msgid "(BC Break) matrix-media-repo datastore IDs are now required in `vars.yml`"

  1242. msgstr ""

  1243. 

  1244. #: ../../../CHANGELOG.md:619

  1245. msgid "**Affects**: users with [matrix-media-repo](docs/configuring-playbook-matrix-media-repo.md) enabled (`matrix_media_repo_enabled: true`)"

  1246. msgstr ""

  1247. 

  1248. #: ../../../CHANGELOG.md:621

  1249. 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)."

  1250. msgstr ""

  1251. 

  1252. #: ../../../CHANGELOG.md:623

  1253. 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."

  1254. msgstr ""

  1255. 

  1256. #: ../../../CHANGELOG.md:625

  1257. msgid "**For existing installations**, retrieve your current values from the server:"

  1258. msgstr ""

  1259. 

  1260. #: ../../../CHANGELOG.md:631

  1261. msgid "Then add to your `vars.yml`:"

  1262. msgstr ""

  1263. 

  1264. #: ../../../CHANGELOG.md:640

  1265. 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."

  1266. msgstr ""

  1267. 

  1268. #: ../../../CHANGELOG.md:642

  1269. msgid "2026-02-08"

  1270. msgstr ""

  1271. 

  1272. #: ../../../CHANGELOG.md:644

  1273. msgid "Zulip bridge has been removed from the playbook"

  1274. msgstr ""

  1275. 

  1276. #: ../../../CHANGELOG.md:646

  1277. 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."

  1278. msgstr ""

  1279. 

  1280. #: ../../../CHANGELOG.md:648

  1281. msgid "Switched to faster secret derivation for service passwords"

  1282. msgstr ""

  1283. 

  1284. #: ../../../CHANGELOG.md:650

  1285. msgid "We've switched the method used for deriving service passwords (database passwords, appservice tokens, etc.) from the `matrix_homeserver_generic_secret_key` variable."

  1286. msgstr ""

  1287. 

  1288. #: ../../../CHANGELOG.md:652

  1289. 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."

  1290. msgstr ""

  1291. 

  1292. #: ../../../CHANGELOG.md:654

  1293. 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."

  1294. msgstr ""

  1295. 

  1296. #: ../../../CHANGELOG.md:656

  1297. 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."

  1298. msgstr ""

  1299. 

  1300. #: ../../../CHANGELOG.md:658

  1301. 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."

  1302. msgstr ""

  1303. 

  1304. #: ../../../CHANGELOG.md:660

  1305. msgid "(BC Break) Dynamic DNS role has been relocated and variable names need adjustments"

  1306. msgstr ""

  1307. 

  1308. #: ../../../CHANGELOG.md:662

  1309. 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."

  1310. msgstr ""

  1311. 

  1312. #: ../../../CHANGELOG.md:664

  1313. 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."

  1314. msgstr ""

  1315. 

  1316. #: ../../../CHANGELOG.md:668

  1317. msgid "ma1sd has been removed from the playbook"

  1318. msgstr ""

  1319. 

  1320. #: ../../../CHANGELOG.md:670

  1321. msgid "[ma1sd](./docs/configuring-playbook-ma1sd.md) has been removed from the playbook, as it has been unmaintained for a long time."

  1322. msgstr ""

  1323. 

  1324. #: ../../../CHANGELOG.md:672

  1325. 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)."

  1326. msgstr ""

  1327. 

  1328. #: ../../../CHANGELOG.md:674

  1329. 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."

  1330. msgstr ""

  1331. 

  1332. #: ../../../CHANGELOG.md:676

  1333. msgid "2026-02-07"

  1334. msgstr ""

  1335. 

  1336. #: ../../../CHANGELOG.md:678

  1337. msgid "(BC Break) Cinny role has been relocated and variable names need adjustments"

  1338. msgstr ""

  1339. 

  1340. #: ../../../CHANGELOG.md:680

  1341. msgid "The role for Cinny has been relocated to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization."

  1342. msgstr ""

  1343. 

  1344. #: ../../../CHANGELOG.md:682

  1345. 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."

  1346. msgstr ""

  1347. 

  1348. #: ../../../CHANGELOG.md:686

  1349. msgid "`matrix_client_cinny_` -> `cinny_`"

  1350. msgstr ""

  1351. 

  1352. #: ../../../CHANGELOG.md:690

  1353. msgid "The Sliding Sync proxy has been removed from the playbook"

  1354. msgstr ""

  1355. 

  1356. #: ../../../CHANGELOG.md:692

  1357. 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`)."

  1358. msgstr ""

  1359. 

  1360. #: ../../../CHANGELOG.md:694

  1361. 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)."

  1362. msgstr ""

  1363. 

  1364. #: ../../../CHANGELOG.md:696

  1365. msgid "2026-02-04"

  1366. msgstr ""

  1367. 

  1368. #: ../../../CHANGELOG.md:698

  1369. msgid "baibot now supports OpenAI's built-in tools (Web Search and Code Interpreter)"

  1370. msgstr ""

  1371. 

  1372. #: ../../../CHANGELOG.md:700

  1373. 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."

  1374. msgstr ""

  1375. 

  1376. #: ../../../CHANGELOG.md:702

  1377. msgid "These tools are **disabled by default** and can be enabled via Ansible variables for static agent configurations:"

  1378. msgstr ""

  1379. 

  1380. #: ../../../CHANGELOG.md:709

  1381. 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."

  1382. msgstr ""

  1383. 

  1384. #: ../../../CHANGELOG.md:711

  1385. msgid "Whoami-based sync worker routing for improved sticky sessions for Synapse"

  1386. msgstr ""

  1387. 

  1388. #: ../../../CHANGELOG.md:713

  1389. 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))."

  1390. msgstr ""

  1391. 

  1392. #: ../../../CHANGELOG.md:715

  1393. 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."

  1394. msgstr ""

  1395. 

  1396. #: ../../../CHANGELOG.md:717

  1397. 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."

  1398. msgstr ""

  1399. 

  1400. #: ../../../CHANGELOG.md:719

  1401. msgid "This change:"

  1402. msgstr ""

  1403. 

  1404. #: ../../../CHANGELOG.md:720

  1405. msgid "**Automatically enables** when sync workers are configured (no action required)"

  1406. msgstr ""

  1407. 

  1408. #: ../../../CHANGELOG.md:721

  1409. msgid "**Works universally** with any authentication system"

  1410. msgstr ""

  1411. 

  1412. #: ../../../CHANGELOG.md:722

  1413. msgid "**Replaces the old implementation** entirely to keep the codebase simple"

  1414. msgstr ""

  1415. 

  1416. #: ../../../CHANGELOG.md:723

  1417. msgid "**Adds minimal overhead** (one cached internal subrequest per sync request) for non-MAS deployments"

  1418. msgstr ""

  1419. 

  1420. #: ../../../CHANGELOG.md:725

  1421. msgid "For debugging, you can enable verbose logging and/or response headers showing routing decisions:"

  1422. msgstr ""

  1423. 

  1424. #: ../../../CHANGELOG.md:736

  1425. msgid "2025-12-09"

  1426. msgstr ""

  1427. 

  1428. #: ../../../CHANGELOG.md:738

  1429. msgid "Traefik Cert Dumper upgrade"

  1430. msgstr ""

  1431. 

  1432. #: ../../../CHANGELOG.md:740

  1433. 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."

  1434. msgstr ""

  1435. 

  1436. #: ../../../CHANGELOG.md:742

  1437. 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."

  1438. msgstr ""

  1439. 

  1440. #: ../../../CHANGELOG.md:744

  1441. msgid "2025-11-23"

  1442. msgstr ""

  1443. 

  1444. #: ../../../CHANGELOG.md:746

  1445. msgid "Matrix.to support"

  1446. msgstr ""

  1447. 

  1448. #: ../../../CHANGELOG.md:748

  1449. 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)."

  1450. msgstr ""

  1451. 

  1452. #: ../../../CHANGELOG.md:750

  1453. msgid "To learn more, see our [Setting up Matrix.to](docs/configuring-playbook-matrixto.md) documentation page."

  1454. msgstr ""

  1455. 

  1456. #: ../../../CHANGELOG.md:752

  1457. msgid "2025-11-09"

  1458. msgstr ""

  1459. 

  1460. #: ../../../CHANGELOG.md:754

  1461. msgid "matrix-appservice-webhooks has been removed from the playbook"

  1462. msgstr ""

  1463. 

  1464. #: ../../../CHANGELOG.md:756

  1465. 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."

  1466. msgstr ""

  1467. 

  1468. #: ../../../CHANGELOG.md:758

  1469. 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)."

  1470. msgstr ""

  1471. 

  1472. #: ../../../CHANGELOG.md:760

  1473. msgid "mautrix-facebook and mautrix-instagram have been removed from the playbook"

  1474. msgstr ""

  1475. 

  1476. #: ../../../CHANGELOG.md:762

  1477. 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)."

  1478. msgstr ""

  1479. 

  1480. #: ../../../CHANGELOG.md:764

  1481. #: ../../../CHANGELOG.md:796

  1482. msgid "The playbook will let you know if you're using any variables for those bridges:"

  1483. msgstr ""

  1484. 

  1485. #: ../../../CHANGELOG.md:766

  1486. msgid "`matrix_mautrix_facebook_*`"

  1487. msgstr ""

  1488. 

  1489. #: ../../../CHANGELOG.md:767

  1490. msgid "`matrix_mautrix_instagram_*`"

  1491. msgstr ""

  1492. 

  1493. #: ../../../CHANGELOG.md:769

  1494. #: ../../../CHANGELOG.md:803

  1495. msgid "You'll need to remove them from `vars.yml` and potentially uninstall them manually. Consult pages below for details:"

  1496. msgstr ""

  1497. 

  1498. #: ../../../CHANGELOG.md:771

  1499. msgid "[Instruction for mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-facebook.md#uninstalling-the-bridge-manually)"

  1500. msgstr ""

  1501. 

  1502. #: ../../../CHANGELOG.md:772

  1503. msgid "[Instruction for mautrix-instagram](./docs/configuring-playbook-bridge-mautrix-instagram.md#uninstalling-the-bridge-manually)"

  1504. msgstr ""

  1505. 

  1506. #: ../../../CHANGELOG.md:774

  1507. msgid "2025-11-08"

  1508. msgstr ""

  1509. 

  1510. #: ../../../CHANGELOG.md:776

  1511. msgid "MatrixZulipBridge support"

  1512. msgstr ""

  1513. 

  1514. #: ../../../CHANGELOG.md:778

  1515. 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/)."

  1516. msgstr ""

  1517. 

  1518. #: ../../../CHANGELOG.md:780

  1519. msgid "To learn more, see our [Setting up Zulip bridging](docs/configuring-playbook-bridge-zulip.md) documentation page."

  1520. msgstr ""

  1521. 

  1522. #: ../../../CHANGELOG.md:782

  1523. msgid "2025-11-07"

  1524. msgstr ""

  1525. 

  1526. #: ../../../CHANGELOG.md:784

  1527. msgid "The matrix-chatgpt-bot has been removed from the playbook"

  1528. msgstr ""

  1529. 

  1530. #: ../../../CHANGELOG.md:786

  1531. 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."

  1532. msgstr ""

  1533. 

  1534. #: ../../../CHANGELOG.md:788

  1535. 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)."

  1536. msgstr ""

  1537. 

  1538. #: ../../../CHANGELOG.md:790

  1539. msgid "2025-11-05"

  1540. msgstr ""

  1541. 

  1542. #: ../../../CHANGELOG.md:792

  1543. msgid "The MX Puppet bridges for Discord, Instagram, Slack, and Twitter have been removed from the playbook"

  1544. msgstr ""

  1545. 

  1546. #: ../../../CHANGELOG.md:794

  1547. 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."

  1548. msgstr ""

  1549. 

  1550. #: ../../../CHANGELOG.md:798

  1551. msgid "`matrix_mx_puppet_discord_*`"

  1552. msgstr ""

  1553. 

  1554. #: ../../../CHANGELOG.md:799

  1555. msgid "`matrix_mx_puppet_instagram_*`"

  1556. msgstr ""

  1557. 

  1558. #: ../../../CHANGELOG.md:800

  1559. msgid "`matrix_mx_puppet_slack_*`"

  1560. msgstr ""

  1561. 

  1562. #: ../../../CHANGELOG.md:801

  1563. msgid "`matrix_mx_puppet_twitter_*`"

  1564. msgstr ""

  1565. 

  1566. #: ../../../CHANGELOG.md:805

  1567. msgid "[Instruction for MX Puppet Discord bridge](./docs/configuring-playbook-bridge-mx-puppet-discord.md#uninstalling-the-bridge-manually)"

  1568. msgstr ""

  1569. 

  1570. #: ../../../CHANGELOG.md:806

  1571. msgid "[Instruction for MX Puppet Instagram bridge](./docs/configuring-playbook-bridge-mx-puppet-instagram.md#uninstalling-the-bridge-manually)"

  1572. msgstr ""

  1573. 

  1574. #: ../../../CHANGELOG.md:807

  1575. msgid "[Instruction for MX Puppet Slack bridge](./docs/configuring-playbook-bridge-mx-puppet-slack.md#uninstalling-the-bridge-manually)"

  1576. msgstr ""

  1577. 

  1578. #: ../../../CHANGELOG.md:808

  1579. msgid "[Instruction for MX Puppet Twitter bridge](./docs/configuring-playbook-bridge-mx-puppet-twitter.md#uninstalling-the-bridge-manually)"

  1580. msgstr ""

  1581. 

  1582. #: ../../../CHANGELOG.md:810

  1583. msgid "2025-11-04"

  1584. msgstr ""

  1585. 

  1586. #: ../../../CHANGELOG.md:812

  1587. msgid "The Go Skype bridge has been removed from the playbook"

  1588. msgstr ""

  1589. 

  1590. #: ../../../CHANGELOG.md:814

  1591. 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."

  1592. msgstr ""

  1593. 

  1594. #: ../../../CHANGELOG.md:816

  1595. 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)."

  1596. msgstr ""

  1597. 

  1598. #: ../../../CHANGELOG.md:818

  1599. msgid "2025-10-02"

  1600. msgstr ""

  1601. 

  1602. #: ../../../CHANGELOG.md:820

  1603. msgid "Element Admin support"

  1604. msgstr ""

  1605. 

  1606. #: ../../../CHANGELOG.md:822

  1607. 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)."

  1608. msgstr ""

  1609. 

  1610. #: ../../../CHANGELOG.md:824

  1611. msgid "Deployments based on Matrix Authentication Service may find it useful to run both Synapse Admin and Element Admin at the same time."

  1612. msgstr ""

  1613. 

  1614. #: ../../../CHANGELOG.md:826

  1615. 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)."

  1616. msgstr ""

  1617. 

  1618. #: ../../../CHANGELOG.md:829

  1619. msgid "2025-04-26"

  1620. msgstr ""

  1621. 

  1622. #: ../../../CHANGELOG.md:831

  1623. msgid "Continuwuity support"

  1624. msgstr ""

  1625. 

  1626. #: ../../../CHANGELOG.md:833

  1627. msgid "Thanks to [Virkkunen](https://github.com/Virkkunen), we now have optional experimental [Continuwuity](./docs/configuring-playbook-continuwuity.md) homeserver support."

  1628. msgstr ""

  1629. 

  1630. #: ../../../CHANGELOG.md:835

  1631. 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."

  1632. msgstr ""

  1633. 

  1634. #: ../../../CHANGELOG.md:839

  1635. msgid "People that used to run conduwuit, may wish to:"

  1636. msgstr ""

  1637. 

  1638. #: ../../../CHANGELOG.md:841

  1639. msgid "either [migrate from conduwuit to Continuwuity](./docs/configuring-playbook-continuwuity.md#migrating-from-conduwuit)"

  1640. msgstr ""

  1641. 

  1642. #: ../../../CHANGELOG.md:842

  1643. msgid "or wait for some of the other forks to progress and for support for them to get added to the playbook"

  1644. msgstr ""

  1645. 

  1646. #: ../../../CHANGELOG.md:844

  1647. msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse/Conduit/Dendrite to Continuwuity) without data loss."

  1648. msgstr ""

  1649. 

  1650. #: ../../../CHANGELOG.md:847

  1651. msgid "2025-04-09"

  1652. msgstr ""

  1653. 

  1654. #: ../../../CHANGELOG.md:849

  1655. msgid "Element Call frontend installation is now optional"

  1656. msgstr ""

  1657. 

  1658. #: ../../../CHANGELOG.md:851

  1659. 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**."

  1660. msgstr ""

  1661. 

  1662. #: ../../../CHANGELOG.md:853

  1663. 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)."

  1664. msgstr ""

  1665. 

  1666. #: ../../../CHANGELOG.md:855

  1667. 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)."

  1668. msgstr ""

  1669. 

  1670. #: ../../../CHANGELOG.md:857

  1671. 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:"

  1672. msgstr ""

  1673. 

  1674. #: ../../../CHANGELOG.md:859

  1675. msgid "Adjusting your `vars.yml` configuration like this:"

  1676. msgstr ""

  1677. 

  1678. #: ../../../CHANGELOG.md:866

  1679. msgid "[Re-running the playbook](./docs/installing.md) with the `setup-all` Ansible tag (e.g. `just setup-all`)"

  1680. msgstr ""

  1681. 

  1682. #: ../../../CHANGELOG.md:868

  1683. msgid "Getting rid of the `call.element.example.com` DNS record"

  1684. msgstr ""

  1685. 

  1686. #: ../../../CHANGELOG.md:871

  1687. msgid "2025-03-15"

  1688. msgstr ""

  1689. 

  1690. #: ../../../CHANGELOG.md:873

  1691. msgid "Element Call support"

  1692. msgstr ""

  1693. 

  1694. #: ../../../CHANGELOG.md:875

  1695. 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)."

  1696. msgstr ""

  1697. 

  1698. #: ../../../CHANGELOG.md:877

  1699. 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."

  1700. msgstr ""

  1701. 

  1702. #: ../../../CHANGELOG.md:879

  1703. 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."

  1704. msgstr ""

  1705. 

  1706. #: ../../../CHANGELOG.md:881

  1707. msgid "To get started, see the [Configuring Element Call](docs/configuring-playbook-element-call.md) documentation page."

  1708. msgstr ""

  1709. 

  1710. #: ../../../CHANGELOG.md:884

  1711. msgid "2025-03-08"

  1712. msgstr ""

  1713. 

  1714. #: ../../../CHANGELOG.md:886

  1715. msgid "6️⃣ IPv6 support enablement recommended by default"

  1716. msgstr ""

  1717. 

  1718. #: ../../../CHANGELOG.md:888

  1719. 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."

  1720. msgstr ""

  1721. 

  1722. #: ../../../CHANGELOG.md:890

  1723. msgid "Our new [Configuring IPv6](./docs/configuring-ipv6.md) documentation page has more details about the playbook's IPv6 support."

  1724. msgstr ""

  1725. 

  1726. #: ../../../CHANGELOG.md:892

  1727. msgid "**Existing playbook users** will **need to do some manual work** to enable IPv6 support. This consists of:"

  1728. msgstr ""

  1729. 

  1730. #: ../../../CHANGELOG.md:894

  1731. msgid "enabling IPv6 support for the Docker container networks:"

  1732. msgstr ""

  1733. 

  1734. #: ../../../CHANGELOG.md:895

  1735. msgid "add `devture_systemd_docker_base_ipv6_enabled: true` to their `vars.yml` configuration file"

  1736. msgstr ""

  1737. 

  1738. #: ../../../CHANGELOG.md:896

  1739. msgid "stop all services (`just stop-all`)"

  1740. msgstr ""

  1741. 

  1742. #: ../../../CHANGELOG.md:897

  1743. msgid "delete all container networks on the server: `docker network rm $(docker network ls -q)`"

  1744. msgstr ""

  1745. 

  1746. #: ../../../CHANGELOG.md:898

  1747. msgid "re-run the playbook fully: `just install-all`"

  1748. msgstr ""

  1749. 

  1750. #: ../../../CHANGELOG.md:900

  1751. msgid "[configuring IPv6 (`AAAA`) DNS records](./docs/configuring-ipv6.md#configuring-dns-records-for-ipv6)"

  1752. msgstr ""

  1753. 

  1754. #: ../../../CHANGELOG.md:902

  1755. msgid "2025-02-26"

  1756. msgstr ""

  1757. 

  1758. #: ../../../CHANGELOG.md:904

  1759. msgid "🪦 Bye-bye, Email2Matrix"

  1760. msgstr ""

  1761. 

  1762. #: ../../../CHANGELOG.md:906

  1763. 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."

  1764. msgstr ""

  1765. 

  1766. #: ../../../CHANGELOG.md:908

  1767. 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."

  1768. msgstr ""

  1769. 

  1770. #: ../../../CHANGELOG.md:911

  1771. msgid "2025-02-23"

  1772. msgstr ""

  1773. 

  1774. #: ../../../CHANGELOG.md:913

  1775. msgid "The playbook defaults to exposing the Coturn STUN port (3478) over UDP once again"

  1776. msgstr ""

  1777. 

  1778. #: ../../../CHANGELOG.md:915

  1779. 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."

  1780. msgstr ""

  1781. 

  1782. #: ../../../CHANGELOG.md:917

  1783. 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**."

  1784. msgstr ""

  1785. 

  1786. #: ../../../CHANGELOG.md:920

  1787. msgid "In light of this new information, you have 2 options:"

  1788. msgstr ""

  1789. 

  1790. #: ../../../CHANGELOG.md:922

  1791. msgid "**If you already adapted to the previous change and would like to adapt to this change one again**:"

  1792. msgstr ""

  1793. 

  1794. #: ../../../CHANGELOG.md:924

  1795. msgid "make sure the `3478/udp` port is whitelisted in your external firewall (if you have one) once again."

  1796. msgstr ""

  1797. 

  1798. #: ../../../CHANGELOG.md:926

  1799. msgid "**If you don't care about old Element clients and wish to reduce the severity of DDoS amplification/reflection attacks**:"

  1800. msgstr ""

  1801. 

  1802. #: ../../../CHANGELOG.md:928

  1803. msgid "Consider closing the STUN/UDP port with the following configuration:"

  1804. msgstr ""

  1805. 

  1806. #: ../../../CHANGELOG.md:934

  1807. msgid "Consider keeping `3478/udp` blocked in your external firewall (if you have one)"

  1808. msgstr ""

  1809. 

  1810. #: ../../../CHANGELOG.md:936

  1811. msgid "2025-02-21"

  1812. msgstr ""

  1813. 

  1814. #: ../../../CHANGELOG.md:938

  1815. msgid "Docker daemon options are no longer adjusted when IPv6 is enabled"

  1816. msgstr ""

  1817. 

  1818. #: ../../../CHANGELOG.md:940

  1819. 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`."

  1820. msgstr ""

  1821. 

  1822. #: ../../../CHANGELOG.md:942

  1823. msgid "This variable did **2 different things at once**:"

  1824. msgstr ""

  1825. 

  1826. #: ../../../CHANGELOG.md:944

  1827. msgid "ensured that container networks were created with IPv6 being enabled"

  1828. msgstr ""

  1829. 

  1830. #: ../../../CHANGELOG.md:945

  1831. msgid "adjusted the Docker daemon's configuration to set `experimental: true` and `ip6tables: true` (a necessary prerequisite for creating IPv6-enabled networks)"

  1832. msgstr ""

  1833. 

  1834. #: ../../../CHANGELOG.md:947

  1835. 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:"

  1836. msgstr ""

  1837. 

  1838. #: ../../../CHANGELOG.md:948

  1839. msgid "`ip6tables` defaults to `true` for everyone"

  1840. msgstr ""

  1841. 

  1842. #: ../../../CHANGELOG.md:949

  1843. msgid "`ip6tables` is out of the experimental phase, so `experimental` is no longer necessary"

  1844. msgstr ""

  1845. 

  1846. #: ../../../CHANGELOG.md:951

  1847. 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`."

  1848. msgstr ""

  1849. 

  1850. #: ../../../CHANGELOG.md:954

  1851. msgid "This change affects you like this:"

  1852. msgstr ""

  1853. 

  1854. #: ../../../CHANGELOG.md:956

  1855. msgid "✅ if you're **not explicitly enabling IPv6** (via `devture_systemd_docker_base_ipv6_enabled` in your configuration): you're unaffected"

  1856. msgstr ""

  1857. 

  1858. #: ../../../CHANGELOG.md:957

  1859. msgid "❓ if you're **explicitly enabling IPv6** (via `devture_systemd_docker_base_ipv6_enabled` in your configuration):"

  1860. msgstr ""

  1861. 

  1862. #: ../../../CHANGELOG.md:958

  1863. 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."

  1864. msgstr ""

  1865. 

  1866. #: ../../../CHANGELOG.md:959

  1867. msgid "🔧 .. and you're on an old Docker version, you **are affected** and need to use the following configuration to restore the old behavior:"

  1868. msgstr ""

  1869. 

  1870. #: ../../../CHANGELOG.md:970

  1871. msgid "Support for bridging to Bluesky via mautrix-bluesky"

  1872. msgstr ""

  1873. 

  1874. #: ../../../CHANGELOG.md:972

  1875. 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)."

  1876. msgstr ""

  1877. 

  1878. #: ../../../CHANGELOG.md:974

  1879. msgid "To learn more, see our [Setting up mautrix-bluesky](./docs/configuring-playbook-bridge-mautrix-bluesky.md) documentation page."

  1880. msgstr ""

  1881. 

  1882. #: ../../../CHANGELOG.md:977

  1883. msgid "2025-02-19"

  1884. msgstr ""

  1885. 

  1886. #: ../../../CHANGELOG.md:979

  1887. msgid "The playbook now defaults to exposing the Coturn STUN port (3478) only over TCP"

  1888. msgstr ""

  1889. 

  1890. #: ../../../CHANGELOG.md:981

  1891. 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)."

  1892. msgstr ""

  1893. 

  1894. #: ../../../CHANGELOG.md:983

  1895. 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."

  1896. msgstr ""

  1897. 

  1898. #: ../../../CHANGELOG.md:985

  1899. msgid "The playbook now **only exposes the Coturn STUN port (`3478`) over TCP by default**."

  1900. msgstr ""

  1901. 

  1902. #: ../../../CHANGELOG.md:987

  1903. msgid "💡 Users may wish to further remove the (now unnecessary) firewall rule allowing access to `3478/udp`."

  1904. msgstr ""

  1905. 

  1906. #: ../../../CHANGELOG.md:989

  1907. 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:"

  1908. msgstr ""

  1909. 

  1910. #: ../../../CHANGELOG.md:996

  1911. 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)."

  1912. msgstr ""

  1913. 

  1914. #: ../../../CHANGELOG.md:999

  1915. msgid "2025-02-17"

  1916. msgstr ""

  1917. 

  1918. #: ../../../CHANGELOG.md:1001

  1919. msgid "FluffyChat Web support"

  1920. msgstr ""

  1921. 

  1922. #: ../../../CHANGELOG.md:1003

  1923. 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."

  1924. msgstr ""

  1925. 

  1926. #: ../../../CHANGELOG.md:1005

  1927. msgid "To learn more, see our [Setting up FluffyChat Web](docs/configuring-playbook-client-fluffychat-web.md) documentation page."

  1928. msgstr ""

  1929. 

  1930. #: ../../../CHANGELOG.md:1008

  1931. msgid "2025-02-03"

  1932. msgstr ""

  1933. 

  1934. #: ../../../CHANGELOG.md:1010

  1935. msgid "The mautrix-hangouts bridge has been removed from the playbook"

  1936. msgstr ""

  1937. 

  1938. #: ../../../CHANGELOG.md:1012

  1939. 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."

  1940. msgstr ""

  1941. 

  1942. #: ../../../CHANGELOG.md:1014

  1943. msgid "This is because Google Hangouts has been discontinued since the 1st of November 2022."

  1944. msgstr ""

  1945. 

  1946. #: ../../../CHANGELOG.md:1016

  1947. 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)."

  1948. msgstr ""

  1949. 

  1950. #: ../../../CHANGELOG.md:1019

  1951. msgid "2025-01-27"

  1952. msgstr ""

  1953. 

  1954. #: ../../../CHANGELOG.md:1021

  1955. msgid "Redis and KeyDB are no longer part of the playbook"

  1956. msgstr ""

  1957. 

  1958. #: ../../../CHANGELOG.md:1023

  1959. 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."

  1960. msgstr ""

  1961. 

  1962. #: ../../../CHANGELOG.md:1025

  1963. msgid "The playbook has gone through several iterations of memorystore implementations:"

  1964. msgstr ""

  1965. 

  1966. #: ../../../CHANGELOG.md:1027

  1967. msgid "It initially used Redis, auto-installing it when needed by features/services"

  1968. msgstr ""

  1969. 

  1970. #: ../../../CHANGELOG.md:1028

  1971. 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"

  1972. msgstr ""

  1973. 

  1974. #: ../../../CHANGELOG.md:1029

  1975. 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"

  1976. msgstr ""

  1977. 

  1978. #: ../../../CHANGELOG.md:1031

  1979. msgid "To reduce configuration complexity and maintenance overhead, we are now:"

  1980. msgstr ""

  1981. 

  1982. #: ../../../CHANGELOG.md:1033

  1983. msgid "removing Redis and KeyDB support entirely"

  1984. msgstr ""

  1985. 

  1986. #: ../../../CHANGELOG.md:1034

  1987. msgid "using Valkey as the sole Redis-compatible memorystore implementation"

  1988. msgstr ""

  1989. 

  1990. #: ../../../CHANGELOG.md:1036

  1991. msgid "To update your configuration:"

  1992. msgstr ""

  1993. 

  1994. #: ../../../CHANGELOG.md:1038

  1995. msgid "**Most users** don't need to do anything"

  1996. msgstr ""

  1997. 

  1998. #: ../../../CHANGELOG.md:1039

  1999. msgid "**Users that were explicitly sticking to Redis/KeyDB** need to update their `vars.yml` to use `valkey_*` variables instead"

  2000. msgstr ""

  2001. 

  2002. #: ../../../CHANGELOG.md:1042

  2003. msgid "2025-01-19"

  2004. msgstr ""

  2005. 

  2006. #: ../../../CHANGELOG.md:1044

  2007. msgid "conduwuit support"

  2008. msgstr ""

  2009. 

  2010. #: ../../../CHANGELOG.md:1046

  2011. msgid "Thanks to [Virkkunen](https://github.com/Virkkunen), we now have optional experimental [conduwuit](https://conduwuit.puppyirl.gay/) homeserver support for new installations."

  2012. msgstr ""

  2013. 

  2014. #: ../../../CHANGELOG.md:1048

  2015. 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)."

  2016. msgstr ""

  2017. 

  2018. #: ../../../CHANGELOG.md:1052

  2019. 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."

  2020. msgstr ""

  2021. 

  2022. #: ../../../CHANGELOG.md:1054

  2023. msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse/Conduit/Dendrite to conduwuit) without data loss."

  2024. msgstr ""

  2025. 

  2026. #: ../../../CHANGELOG.md:1057

  2027. msgid "2025-01-14"

  2028. msgstr ""

  2029. 

  2030. #: ../../../CHANGELOG.md:1059

  2031. msgid "(Backward Compatibility Break) Synapse v1.122.0 requires Postgres v13"

  2032. msgstr ""

  2033. 

  2034. #: ../../../CHANGELOG.md:1061

  2035. msgid "The Synapse homeserver [requires Postgres v13 or newer](https://github.com/element-hq/synapse/issues/18034)."

  2036. msgstr ""

  2037. 

  2038. #: ../../../CHANGELOG.md:1063

  2039. 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."

  2040. msgstr ""

  2041. 

  2042. #: ../../../CHANGELOG.md:1065

  2043. 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."

  2044. msgstr ""

  2045. 

  2046. #: ../../../CHANGELOG.md:1067

  2047. 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."

  2048. msgstr ""

  2049. 

  2050. #: ../../../CHANGELOG.md:1069

  2051. 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:"

  2052. msgstr ""

  2053. 

  2054. #: ../../../CHANGELOG.md:1077

  2055. msgid "2024-11-26"

  2056. msgstr ""

  2057. 

  2058. #: ../../../CHANGELOG.md:1079

  2059. msgid "(Backward Compatibility Break) Synapse now defaults to enabling authenticated media"

  2060. msgstr ""

  2061. 

  2062. #: ../../../CHANGELOG.md:1081

  2063. 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)."

  2064. msgstr ""

  2065. 

  2066. #: ../../../CHANGELOG.md:1083

  2067. 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)."

  2068. msgstr ""

  2069. 

  2070. #: ../../../CHANGELOG.md:1085

  2071. msgid "Servers like `matrix.org` have already [sunset unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) months ago."

  2072. msgstr ""

  2073. 

  2074. #: ../../../CHANGELOG.md:1087

  2075. 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."

  2076. msgstr ""

  2077. 

  2078. #: ../../../CHANGELOG.md:1089

  2079. msgid "We're changing the playbook configuration for authenticated media to keep up with upstream defaults changing."

  2080. msgstr ""

  2081. 

  2082. #: ../../../CHANGELOG.md:1091

  2083. 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."

  2084. msgstr ""

  2085. 

  2086. #: ../../../CHANGELOG.md:1093

  2087. 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."

  2088. msgstr ""

  2089. 

  2090. #: ../../../CHANGELOG.md:1096

  2091. msgid "2024-11-23"

  2092. msgstr ""

  2093. 

  2094. #: ../../../CHANGELOG.md:1098

  2095. msgid "(Backward Compatibility Break) The playbook now defaults to Valkey, instead of KeyDB"

  2096. msgstr ""

  2097. 

  2098. #: ../../../CHANGELOG.md:1100

  2099. 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."

  2100. msgstr ""

  2101. 

  2102. #: ../../../CHANGELOG.md:1102

  2103. 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.)."

  2104. msgstr ""

  2105. 

  2106. #: ../../../CHANGELOG.md:1104

  2107. 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)."

  2108. msgstr ""

  2109. 

  2110. #: ../../../CHANGELOG.md:1106

  2111. 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."

  2112. msgstr ""

  2113. 

  2114. #: ../../../CHANGELOG.md:1108

  2115. 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."

  2116. msgstr ""

  2117. 

  2118. #: ../../../CHANGELOG.md:1110

  2119. 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."

  2120. msgstr ""

  2121. 

  2122. #: ../../../CHANGELOG.md:1112

  2123. 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)."

  2124. msgstr ""

  2125. 

  2126. #: ../../../CHANGELOG.md:1114

  2127. #: ../../../CHANGELOG.md:1454

  2128. 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:"

  2129. msgstr ""

  2130. 

  2131. #: ../../../CHANGELOG.md:1125

  2132. 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:"

  2133. msgstr ""

  2134. 

  2135. #: ../../../CHANGELOG.md:1135

  2136. 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."

  2137. msgstr ""

  2138. 

  2139. #: ../../../CHANGELOG.md:1138

  2140. msgid "2024-11-14"

  2141. msgstr ""

  2142. 

  2143. #: ../../../CHANGELOG.md:1140

  2144. msgid "HTTP-compression support for Traefik-based setups"

  2145. msgstr ""

  2146. 

  2147. #: ../../../CHANGELOG.md:1142

  2148. 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`)."

  2149. msgstr ""

  2150. 

  2151. #: ../../../CHANGELOG.md:1144

  2152. 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."

  2153. msgstr ""

  2154. 

  2155. #: ../../../CHANGELOG.md:1146

  2156. 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."

  2157. msgstr ""

  2158. 

  2159. #: ../../../CHANGELOG.md:1148

  2160. 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`)."

  2161. msgstr ""

  2162. 

  2163. #: ../../../CHANGELOG.md:1150

  2164. 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:"

  2165. msgstr ""

  2166. 

  2167. #: ../../../CHANGELOG.md:1152

  2168. 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)"

  2169. msgstr ""

  2170. 

  2171. #: ../../../CHANGELOG.md:1153

  2172. msgid "setting `matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled` to `true`"

  2173. msgstr ""

  2174. 

  2175. #: ../../../CHANGELOG.md:1154

  2176. 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`)"

  2177. msgstr ""

  2178. 

  2179. #: ../../../CHANGELOG.md:1156

  2180. msgid "Timeout adjustments for Traefik-based setups"

  2181. msgstr ""

  2182. 

  2183. #: ../../../CHANGELOG.md:1158

  2184. 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."

  2185. msgstr ""

  2186. 

  2187. #: ../../../CHANGELOG.md:1160

  2188. 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."

  2189. msgstr ""

  2190. 

  2191. #: ../../../CHANGELOG.md:1162

  2192. 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."

  2193. msgstr ""

  2194. 

  2195. #: ../../../CHANGELOG.md:1164

  2196. 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."

  2197. msgstr ""

  2198. 

  2199. #: ../../../CHANGELOG.md:1166

  2200. msgid "Example of the default timeout values used by the playbook:"

  2201. msgstr ""

  2202. 

  2203. #: ../../../CHANGELOG.md:1177

  2204. 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`)."

  2205. msgstr ""

  2206. 

  2207. #: ../../../CHANGELOG.md:1180

  2208. msgid "2024-11-08"

  2209. msgstr ""

  2210. 

  2211. #: ../../../CHANGELOG.md:1182

  2212. msgid "Support for synapse-admin auto-configuration via /.well-known/matrix/client"

  2213. msgstr ""

  2214. 

  2215. #: ../../../CHANGELOG.md:1184

  2216. 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)."

  2217. msgstr ""

  2218. 

  2219. #: ../../../CHANGELOG.md:1186

  2220. 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."

  2221. msgstr ""

  2222. 

  2223. #: ../../../CHANGELOG.md:1188

  2224. 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`"

  2225. msgstr ""

  2226. 

  2227. #: ../../../CHANGELOG.md:1191

  2228. msgid "2024-10-28"

  2229. msgstr ""

  2230. 

  2231. #: ../../../CHANGELOG.md:1193

  2232. msgid "(BC Break) Postmoogle's variable names need adjustments"

  2233. msgstr ""

  2234. 

  2235. #: ../../../CHANGELOG.md:1195

  2236. 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."

  2237. msgstr ""

  2238. 

  2239. #: ../../../CHANGELOG.md:1197

  2240. msgid "2024-10-19"

  2241. msgstr ""

  2242. 

  2243. #: ../../../CHANGELOG.md:1199

  2244. msgid "Support for Matrix Authentication Service"

  2245. msgstr ""

  2246. 

  2247. #: ../../../CHANGELOG.md:1201

  2248. msgid "The playbook now supports installing and configuring [Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) (MAS)."

  2249. msgstr ""

  2250. 

  2251. #: ../../../CHANGELOG.md:1203

  2252. 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."

  2253. msgstr ""

  2254. 

  2255. #: ../../../CHANGELOG.md:1205

  2256. 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."

  2257. msgstr ""

  2258. 

  2259. #: ../../../CHANGELOG.md:1207

  2260. 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."

  2261. msgstr ""

  2262. 

  2263. #: ../../../CHANGELOG.md:1210

  2264. msgid "2024-09-27"

  2265. msgstr ""

  2266. 

  2267. #: ../../../CHANGELOG.md:1212

  2268. msgid "(BC Break) Postgres & Traefik roles have been relocated and variable names need adjustments"

  2269. msgstr ""

  2270. 

  2271. #: ../../../CHANGELOG.md:1214

  2272. 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."

  2273. msgstr ""

  2274. 

  2275. #: ../../../CHANGELOG.md:1216

  2276. msgid "Along with the relocation, the `devture_` prefix was dropped from their variable names, so you need to adjust your `vars.yml` configuration."

  2277. msgstr ""

  2278. 

  2279. #: ../../../CHANGELOG.md:1218

  2280. msgid "You need to do the following replacements:"

  2281. msgstr ""

  2282. 

  2283. #: ../../../CHANGELOG.md:1220

  2284. msgid "`devture_postgres_` -> `postgres_`"

  2285. msgstr ""

  2286. 

  2287. #: ../../../CHANGELOG.md:1221

  2288. msgid "`devture_traefik_` -> `traefik_`"

  2289. msgstr ""

  2290. 

  2291. #: ../../../CHANGELOG.md:1226

  2292. msgid "2024-09-12"

  2293. msgstr ""

  2294. 

  2295. #: ../../../CHANGELOG.md:1228

  2296. msgid "Support for baibot"

  2297. msgstr ""

  2298. 

  2299. #: ../../../CHANGELOG.md:1230

  2300. 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. 🤖"

  2301. msgstr ""

  2302. 

  2303. #: ../../../CHANGELOG.md:1232

  2304. 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)."

  2305. msgstr ""

  2306. 

  2307. #: ../../../CHANGELOG.md:1234

  2308. 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)."

  2309. msgstr ""

  2310. 

  2311. #: ../../../CHANGELOG.md:1236

  2312. msgid "To get started, see the [Setting up baibot](./docs/configuring-playbook-bot-baibot.md) documentation page."

  2313. msgstr ""

  2314. 

  2315. #: ../../../CHANGELOG.md:1238

  2316. msgid "Switching synapse-admin to etke.cc's fork"

  2317. msgstr ""

  2318. 

  2319. #: ../../../CHANGELOG.md:1240

  2320. 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."

  2321. msgstr ""

  2322. 

  2323. #: ../../../CHANGELOG.md:1242

  2324. 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."

  2325. msgstr ""

  2326. 

  2327. #: ../../../CHANGELOG.md:1244

  2328. 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."

  2329. msgstr ""

  2330. 

  2331. #: ../../../CHANGELOG.md:1246

  2332. 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:"

  2333. msgstr ""

  2334. 

  2335. #: ../../../CHANGELOG.md:1259

  2336. msgid "2024-08-17"

  2337. msgstr ""

  2338. 

  2339. #: ../../../CHANGELOG.md:1261

  2340. msgid "New appservice-double-puppet service for better double-puppeting"

  2341. msgstr ""

  2342. 

  2343. #: ../../../CHANGELOG.md:1263

  2344. 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."

  2345. msgstr ""

  2346. 

  2347. #: ../../../CHANGELOG.md:1265

  2348. 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."

  2349. msgstr ""

  2350. 

  2351. #: ../../../CHANGELOG.md:1267

  2352. 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."

  2353. msgstr ""

  2354. 

  2355. #: ../../../CHANGELOG.md:1269

  2356. 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**."

  2357. msgstr ""

  2358. 

  2359. #: ../../../CHANGELOG.md:1271

  2360. msgid "We recommend **enabling double-puppeting via the new Appservice method** by adding the following configuration to your `vars.yml` file:"

  2361. msgstr ""

  2362. 

  2363. #: ../../../CHANGELOG.md:1277

  2364. 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."

  2365. msgstr ""

  2366. 

  2367. #: ../../../CHANGELOG.md:1279

  2368. msgid "When both double-puppeting methods are enabled, the playbook will automatically choose the new and better Appservice method for bridges that support it."

  2369. msgstr ""

  2370. 

  2371. #: ../../../CHANGELOG.md:1282

  2372. msgid "2024-08-15"

  2373. msgstr ""

  2374. 

  2375. #: ../../../CHANGELOG.md:1284

  2376. msgid "matrix-media-repo now configured for Authenticated Media"

  2377. msgstr ""

  2378. 

  2379. #: ../../../CHANGELOG.md:1286

  2380. 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))."

  2381. msgstr ""

  2382. 

  2383. #: ../../../CHANGELOG.md:1288

  2384. 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."

  2385. msgstr ""

  2386. 

  2387. #: ../../../CHANGELOG.md:1290

  2388. 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."

  2389. msgstr ""

  2390. 

  2391. #: ../../../CHANGELOG.md:1292

  2392. 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."

  2393. msgstr ""

  2394. 

  2395. #: ../../../CHANGELOG.md:1295

  2396. msgid "2024-08-08"

  2397. msgstr ""

  2398. 

  2399. #: ../../../CHANGELOG.md:1297

  2400. msgid "(Backward Compatibility Break) matrix-corporal has been upgraded to v3"

  2401. msgstr ""

  2402. 

  2403. #: ../../../CHANGELOG.md:1299

  2404. 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))."

  2405. msgstr ""

  2406. 

  2407. #: ../../../CHANGELOG.md:1301

  2408. 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)."

  2409. msgstr ""

  2410. 

  2411. #: ../../../CHANGELOG.md:1303

  2412. 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:"

  2413. msgstr ""

  2414. 

  2415. #: ../../../CHANGELOG.md:1309

  2416. msgid "2024-07-25"

  2417. msgstr ""

  2418. 

  2419. #: ../../../CHANGELOG.md:1311

  2420. msgid "synapse-usage-exporter support"

  2421. msgstr ""

  2422. 

  2423. #: ../../../CHANGELOG.md:1313

  2424. 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."

  2425. msgstr ""

  2426. 

  2427. #: ../../../CHANGELOG.md:1315

  2428. msgid "To learn more see our [Enabling synapse-usage-exporter for Synapse usage statistics](docs/configuring-playbook-synapse-usage-exporter.md) documentation page."

  2429. msgstr ""

  2430. 

  2431. #: ../../../CHANGELOG.md:1318

  2432. msgid "2024-07-06"

  2433. msgstr ""

  2434. 

  2435. #: ../../../CHANGELOG.md:1320

  2436. msgid "matrix-alertmanager-receiver support"

  2437. msgstr ""

  2438. 

  2439. #: ../../../CHANGELOG.md:1322

  2440. 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)."

  2441. msgstr ""

  2442. 

  2443. #: ../../../CHANGELOG.md:1324

  2444. msgid "See [Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](./docs/configuring-playbook-alertmanager-receiver.md) for more details."

  2445. msgstr ""

  2446. 

  2447. #: ../../../CHANGELOG.md:1326

  2448. msgid "Traefik v3 and HTTP/3 are here now"

  2449. msgstr ""

  2450. 

  2451. #: ../../../CHANGELOG.md:1328

  2452. 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."

  2453. msgstr ""

  2454. 

  2455. #: ../../../CHANGELOG.md:1330

  2456. msgid "Traefik v3"

  2457. msgstr ""

  2458. 

  2459. #: ../../../CHANGELOG.md:1332

  2460. 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/)."

  2461. msgstr ""

  2462. 

  2463. #: ../../../CHANGELOG.md:1334

  2464. msgid "We have **updated the playbook to Traefik v3** (make sure to run `just roles` / `make roles` to get it)."

  2465. msgstr ""

  2466. 

  2467. #: ../../../CHANGELOG.md:1336

  2468. 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."

  2469. msgstr ""

  2470. 

  2471. #: ../../../CHANGELOG.md:1338

  2472. msgid "**Most people using the playbook should not have to do any changes**."

  2473. msgstr ""

  2474. 

  2475. #: ../../../CHANGELOG.md:1340

  2476. 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/)."

  2477. msgstr ""

  2478. 

  2479. #: ../../../CHANGELOG.md:1342

  2480. 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)."

  2481. msgstr ""

  2482. 

  2483. #: ../../../CHANGELOG.md:1344

  2484. 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."

  2485. msgstr ""

  2486. 

  2487. #: ../../../CHANGELOG.md:1346

  2488. msgid "HTTP/3 is enabled by default"

  2489. msgstr ""

  2490. 

  2491. #: ../../../CHANGELOG.md:1348

  2492. 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."

  2493. msgstr ""

  2494. 

  2495. #: ../../../CHANGELOG.md:1350

  2496. 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**."

  2497. msgstr ""

  2498. 

  2499. #: ../../../CHANGELOG.md:1352

  2500. 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)."

  2501. msgstr ""

  2502. 

  2503. #: ../../../CHANGELOG.md:1354

  2504. 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)."

  2505. msgstr ""

  2506. 

  2507. #: ../../../CHANGELOG.md:1356

  2508. msgid "To **disable HTTP/3**, you can use the following configuration:"

  2509. msgstr ""

  2510. 

  2511. #: ../../../CHANGELOG.md:1370

  2512. 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:"

  2513. msgstr ""

  2514. 

  2515. #: ../../../CHANGELOG.md:1383

  2516. msgid "2024-07-01"

  2517. msgstr ""

  2518. 

  2519. #: ../../../CHANGELOG.md:1385

  2520. msgid "synapse-admin is now restricted to your homeserver's URL by default"

  2521. msgstr ""

  2522. 

  2523. #: ../../../CHANGELOG.md:1387

  2524. 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)."

  2525. msgstr ""

  2526. 

  2527. #: ../../../CHANGELOG.md:1389

  2528. 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."

  2529. msgstr ""

  2530. 

  2531. #: ../../../CHANGELOG.md:1391

  2532. msgid "If you'd like **to go back to the old unrestricted behavior**, use the following configuration:"

  2533. msgstr ""

  2534. 

  2535. #: ../../../CHANGELOG.md:1399

  2536. msgid "2024-06-25"

  2537. msgstr ""

  2538. 

  2539. #: ../../../CHANGELOG.md:1401

  2540. msgid "The URL-prefix for Hookshot generic webhooks has changed"

  2541. msgstr ""

  2542. 

  2543. #: ../../../CHANGELOG.md:1403

  2544. msgid "Until now, generic Hookshot webhook URLs looked like this: `https://matrix.example.com/hookshot/webhooks/:hookId`."

  2545. msgstr ""

  2546. 

  2547. #: ../../../CHANGELOG.md:1405

  2548. msgid "The `/hookshot/webhooks` common prefix gets stripped by Traefik automatically, so Hookshot only sees the part that comes after (`/:hookId`)."

  2549. msgstr ""

  2550. 

  2551. #: ../../../CHANGELOG.md:1407

  2552. 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`)."

  2553. msgstr ""

  2554. 

  2555. #: ../../../CHANGELOG.md:1409

  2556. 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."

  2557. msgstr ""

  2558. 

  2559. #: ../../../CHANGELOG.md:1411

  2560. msgid "When generating new webhooks, you should start seeing the new URLs being used."

  2561. msgstr ""

  2562. 

  2563. #: ../../../CHANGELOG.md:1413

  2564. 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."

  2565. msgstr ""

  2566. 

  2567. #: ../../../CHANGELOG.md:1415

  2568. 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."

  2569. msgstr ""

  2570. 

  2571. #: ../../../CHANGELOG.md:1418

  2572. msgid "2024-06-22"

  2573. msgstr ""

  2574. 

  2575. #: ../../../CHANGELOG.md:1420

  2576. msgid "The maubot user is now managed by the playbook"

  2577. msgstr ""

  2578. 

  2579. #: ../../../CHANGELOG.md:1422

  2580. 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."

  2581. msgstr ""

  2582. 

  2583. #: ../../../CHANGELOG.md:1424

  2584. 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."

  2585. msgstr ""

  2586. 

  2587. #: ../../../CHANGELOG.md:1426

  2588. 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`)."

  2589. msgstr ""

  2590. 

  2591. #: ../../../CHANGELOG.md:1429

  2592. msgid "2024-06-03"

  2593. msgstr ""

  2594. 

  2595. #: ../../../CHANGELOG.md:1431

  2596. msgid "WeChat bridging support"

  2597. msgstr ""

  2598. 

  2599. #: ../../../CHANGELOG.md:1433

  2600. 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."

  2601. msgstr ""

  2602. 

  2603. #: ../../../CHANGELOG.md:1435

  2604. msgid "See our [Setting up WeChat bridging](docs/configuring-playbook-bridge-wechat.md) documentation page for getting started."

  2605. msgstr ""

  2606. 

  2607. #: ../../../CHANGELOG.md:1438

  2608. msgid "2024-03-26"

  2609. msgstr ""

  2610. 

  2611. #: ../../../CHANGELOG.md:1440

  2612. msgid "(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis"

  2613. msgstr ""

  2614. 

  2615. #: ../../../CHANGELOG.md:1442

  2616. 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/)."

  2617. msgstr ""

  2618. 

  2619. #: ../../../CHANGELOG.md:1444

  2620. 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/)."

  2621. msgstr ""

  2622. 

  2623. #: ../../../CHANGELOG.md:1446

  2624. 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`)."

  2625. msgstr ""

  2626. 

  2627. #: ../../../CHANGELOG.md:1448

  2628. 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."

  2629. msgstr ""

  2630. 

  2631. #: ../../../CHANGELOG.md:1450

  2632. 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."

  2633. msgstr ""

  2634. 

  2635. #: ../../../CHANGELOG.md:1452

  2636. 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)."

  2637. msgstr ""

  2638. 

  2639. #: ../../../CHANGELOG.md:1463

  2640. msgid "2024-03-24"

  2641. msgstr ""

  2642. 

  2643. #: ../../../CHANGELOG.md:1465

  2644. msgid "Initial work on IPv6 support"

  2645. msgstr ""

  2646. 

  2647. #: ../../../CHANGELOG.md:1467

  2648. 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)."

  2649. msgstr ""

  2650. 

  2651. #: ../../../CHANGELOG.md:1469

  2652. msgid "It should be noted that:"

  2653. msgstr ""

  2654. 

  2655. #: ../../../CHANGELOG.md:1471

  2656. 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"

  2657. msgstr ""

  2658. 

  2659. #: ../../../CHANGELOG.md:1472

  2660. 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)"

  2661. msgstr ""

  2662. 

  2663. #: ../../../CHANGELOG.md:1473

  2664. msgid "this is all very new and untested"

  2665. msgstr ""

  2666. 

  2667. #: ../../../CHANGELOG.md:1475

  2668. msgid "Pantalaimon support"

  2669. msgstr ""

  2670. 

  2671. #: ../../../CHANGELOG.md:1477

  2672. 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."

  2673. msgstr ""

  2674. 

  2675. #: ../../../CHANGELOG.md:1479

  2676. msgid "See our [Setting up Pantalaimon](docs/configuring-playbook-pantalaimon.md) documentation to get started."

  2677. msgstr ""

  2678. 

  2679. #: ../../../CHANGELOG.md:1482

  2680. msgid "2024-03-05"

  2681. msgstr ""

  2682. 

  2683. #: ../../../CHANGELOG.md:1484

  2684. msgid "Support for Draupnir-for-all"

  2685. msgstr ""

  2686. 

  2687. #: ../../../CHANGELOG.md:1486

  2688. 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)."

  2689. msgstr ""

  2690. 

  2691. #: ../../../CHANGELOG.md:1488

  2692. msgid "This is an alternative to [running Draupnir in bot mode](./docs/configuring-playbook-bot-draupnir.md), which is still supported by the playbook."

  2693. msgstr ""

  2694. 

  2695. #: ../../../CHANGELOG.md:1490

  2696. msgid "The documentation page for [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) contains more information on how to install it."

  2697. msgstr ""

  2698. 

  2699. #: ../../../CHANGELOG.md:1493

  2700. msgid "2024-02-19"

  2701. msgstr ""

  2702. 

  2703. #: ../../../CHANGELOG.md:1495

  2704. msgid "Support for bridging to Facebook/Messenger via the new mautrix-meta bridge"

  2705. msgstr ""

  2706. 

  2707. #: ../../../CHANGELOG.md:1497

  2708. 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."

  2709. msgstr ""

  2710. 

  2711. #: ../../../CHANGELOG.md:1499

  2712. 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."

  2713. msgstr ""

  2714. 

  2715. #: ../../../CHANGELOG.md:1501

  2716. 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:"

  2717. msgstr ""

  2718. 

  2719. #: ../../../CHANGELOG.md:1503

  2720. msgid "[Setting up Instagram bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)"

  2721. msgstr ""

  2722. 

  2723. #: ../../../CHANGELOG.md:1505

  2724. msgid "[Setting up Messenger bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-messenger.md)"

  2725. msgstr ""

  2726. 

  2727. #: ../../../CHANGELOG.md:1507

  2728. msgid "The documentation pages contain more information on how to migrate."

  2729. msgstr ""

  2730. 

  2731. #: ../../../CHANGELOG.md:1510

  2732. msgid "2024-02-14"

  2733. msgstr ""

  2734. 

  2735. #: ../../../CHANGELOG.md:1512

  2736. msgid "Much larger Synapse caches and cache auto-tuning enabled by default"

  2737. msgstr ""

  2738. 

  2739. #: ../../../CHANGELOG.md:1514

  2740. 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)."

  2741. msgstr ""

  2742. 

  2743. #: ../../../CHANGELOG.md:1516

  2744. 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)."

  2745. msgstr ""

  2746. 

  2747. #: ../../../CHANGELOG.md:1518

  2748. 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:"

  2749. msgstr ""

  2750. 

  2751. #: ../../../CHANGELOG.md:1520

  2752. 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"

  2753. msgstr ""

  2754. 

  2755. #: ../../../CHANGELOG.md:1521

  2756. 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"

  2757. msgstr ""

  2758. 

  2759. #: ../../../CHANGELOG.md:1522

  2760. msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` — defaults to `30s`"

  2761. msgstr ""

  2762. 

  2763. #: ../../../CHANGELOG.md:1524

  2764. msgid "These values should be good defaults for most servers, but may change over time as we experiment further."

  2765. msgstr ""

  2766. 

  2767. #: ../../../CHANGELOG.md:1526

  2768. msgid "Refer to our new [Tuning caches and cache autotuning](docs/maintenance-synapse.md#tuning-caches-and-cache-autotuning) documentation section for more details."

  2769. msgstr ""

  2770. 

  2771. #: ../../../CHANGELOG.md:1529

  2772. msgid "2024-01-31"

  2773. msgstr ""

  2774. 

  2775. #: ../../../CHANGELOG.md:1531

  2776. msgid "(Backward-compatibility break) Minor changes necessary for some people serving a static website at the base domain"

  2777. msgstr ""

  2778. 

  2779. #: ../../../CHANGELOG.md:1533

  2780. 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."

  2781. msgstr ""

  2782. 

  2783. #: ../../../CHANGELOG.md:1535

  2784. 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."

  2785. msgstr ""

  2786. 

  2787. #: ../../../CHANGELOG.md:1537

  2788. 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."

  2789. msgstr ""

  2790. 

  2791. #: ../../../CHANGELOG.md:1540

  2792. msgid "2024-01-20"

  2793. msgstr ""

  2794. 

  2795. #: ../../../CHANGELOG.md:1542

  2796. msgid "Support for more efficient (specialized) Synapse workers"

  2797. msgstr ""

  2798. 

  2799. #: ../../../CHANGELOG.md:1544

  2800. 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."

  2801. msgstr ""

  2802. 

  2803. #: ../../../CHANGELOG.md:1546

  2804. 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."

  2805. msgstr ""

  2806. 

  2807. #: ../../../CHANGELOG.md:1548

  2808. 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)."

  2809. msgstr ""

  2810. 

  2811. #: ../../../CHANGELOG.md:1550

  2812. msgid "To get started, refer to our [Specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) documentation section."

  2813. msgstr ""

  2814. 

  2815. #: ../../../CHANGELOG.md:1553

  2816. msgid "2024-01-17"

  2817. msgstr ""

  2818. 

  2819. #: ../../../CHANGELOG.md:1555

  2820. msgid "Switching to Element's AGPLv3-licensed Synapse release"

  2821. msgstr ""

  2822. 

  2823. #: ../../../CHANGELOG.md:1557

  2824. 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:"

  2825. msgstr ""

  2826. 

  2827. #: ../../../CHANGELOG.md:1559

  2828. 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"

  2829. msgstr ""

  2830. 

  2831. #: ../../../CHANGELOG.md:1560

  2832. 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"

  2833. msgstr ""

  2834. 

  2835. #: ../../../CHANGELOG.md:1562

  2836. msgid "You can also learn more in [this post](https://matrix.org/blog/2023/11/06/future-of-synapse-dendrite/) by the Matrix Foundation."

  2837. msgstr ""

  2838. 

  2839. #: ../../../CHANGELOG.md:1564

  2840. 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)."

  2841. msgstr ""

  2842. 

  2843. #: ../../../CHANGELOG.md:1566

  2844. 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."

  2845. msgstr ""

  2846. 

  2847. #: ../../../CHANGELOG.md:1568

  2848. msgid "**What does this mean to you?**"

  2849. msgstr ""

  2850. 

  2851. #: ../../../CHANGELOG.md:1570

  2852. 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."

  2853. msgstr ""

  2854. 

  2855. #: ../../../CHANGELOG.md:1572

  2856. 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)."

  2857. msgstr ""

  2858. 

  2859. #: ../../../CHANGELOG.md:1574

  2860. 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!"

  2861. msgstr ""

  2862. 

  2863. #: ../../../CHANGELOG.md:1576

  2864. 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:"

  2865. msgstr ""

  2866. 

  2867. #: ../../../CHANGELOG.md:1588

  2868. msgid "Notes:"

  2869. msgstr ""

  2870. 

  2871. #: ../../../CHANGELOG.md:1590

  2872. 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"

  2873. msgstr ""

  2874. 

  2875. #: ../../../CHANGELOG.md:1592

  2876. msgid "running an outdated homeserver exposes you to security issues and incompatibilities. Only consider doing this as a short-term solution."

  2877. msgstr ""

  2878. 

  2879. #: ../../../CHANGELOG.md:1594

  2880. msgid "2024-01-16"

  2881. msgstr ""

  2882. 

  2883. #: ../../../CHANGELOG.md:1596

  2884. msgid "`Draupnir` has been relicensed to AFL-3.0"

  2885. msgstr ""

  2886. 

  2887. #: ../../../CHANGELOG.md:1598

  2888. 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."

  2889. msgstr ""

  2890. 

  2891. #: ../../../CHANGELOG.md:1600

  2892. msgid "2024-01-15"

  2893. msgstr ""

  2894. 

  2895. #: ../../../CHANGELOG.md:1602

  2896. msgid "Goodbye, `matrix-nginx-proxy` 🪦"

  2897. msgstr ""

  2898. 

  2899. #: ../../../CHANGELOG.md:1604

  2900. 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."

  2901. msgstr ""

  2902. 

  2903. #: ../../../CHANGELOG.md:1606

  2904. msgid "Backstory on `matrix-nginx-proxy`"

  2905. msgstr ""

  2906. 

  2907. #: ../../../CHANGELOG.md:1608

  2908. 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."

  2909. msgstr ""

  2910. 

  2911. #: ../../../CHANGELOG.md:1610

  2912. 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."

  2913. msgstr ""

  2914. 

  2915. #: ../../../CHANGELOG.md:1612

  2916. msgid "To us, `matrix-nginx-proxy` was:"

  2917. msgstr ""

  2918. 

  2919. #: ../../../CHANGELOG.md:1614

  2920. msgid "an [nginx](https://nginx.org/)-based reverse-proxy"

  2921. msgstr ""

  2922. 

  2923. #: ../../../CHANGELOG.md:1615

  2924. 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)"

  2925. msgstr ""

  2926. 

  2927. #: ../../../CHANGELOG.md:1616

  2928. 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"

  2929. msgstr ""

  2930. 

  2931. #: ../../../CHANGELOG.md:1617

  2932. 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"

  2933. msgstr ""

  2934. 

  2935. #: ../../../CHANGELOG.md:1618

  2936. msgid "a webserver for serving the `/.well-known/matrix` static files (generated by the `matrix-base` role until now)"

  2937. msgstr ""

  2938. 

  2939. #: ../../../CHANGELOG.md:1619

  2940. msgid "a webserver [serving your base domain](./docs/configuring-playbook-base-domain-serving.md) (and also generating the `index.html` page for it)"

  2941. msgstr ""

  2942. 

  2943. #: ../../../CHANGELOG.md:1620

  2944. 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"

  2945. msgstr ""

  2946. 

  2947. #: ../../../CHANGELOG.md:1622

  2948. 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."

  2949. msgstr ""

  2950. 

  2951. #: ../../../CHANGELOG.md:1624

  2952. 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`)."

  2953. msgstr ""

  2954. 

  2955. #: ../../../CHANGELOG.md:1626

  2956. 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."

  2957. msgstr ""

  2958. 

  2959. #: ../../../CHANGELOG.md:1628

  2960. 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`."

  2961. msgstr ""

  2962. 

  2963. #: ../../../CHANGELOG.md:1630

  2964. msgid "Going Traefik-native and cutting out all middlemen"

  2965. msgstr ""

  2966. 

  2967. #: ../../../CHANGELOG.md:1632

  2968. msgid "In our new setup, you'll see the bare minimum number of reverse-proxies."

  2969. msgstr ""

  2970. 

  2971. #: ../../../CHANGELOG.md:1634

  2972. 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."

  2973. msgstr ""

  2974. 

  2975. #: ../../../CHANGELOG.md:1636

  2976. 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."

  2977. msgstr ""

  2978. 

  2979. #: ../../../CHANGELOG.md:1638

  2980. msgid "Traefik now has an extra job"

  2981. msgstr ""

  2982. 

  2983. #: ../../../CHANGELOG.md:1640

  2984. 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."

  2985. msgstr ""

  2986. 

  2987. #: ../../../CHANGELOG.md:1642

  2988. 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."

  2989. msgstr ""

  2990. 

  2991. #: ../../../CHANGELOG.md:1644

  2992. 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."

  2993. msgstr ""

  2994. 

  2995. #: ../../../CHANGELOG.md:1646

  2996. 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."

  2997. msgstr ""

  2998. 

  2999. #: ../../../CHANGELOG.md:1648

  3000. 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)."

  3001. msgstr ""

  3002. 

  3003. #: ../../../CHANGELOG.md:1650

  3004. msgid "Traefik serving this second purpose has a few downsides:"

  3005. msgstr ""

  3006. 

  3007. #: ../../../CHANGELOG.md:1652

  3008. msgid "Traefik becomes a runtime dependency for all homeserver-dependant container services"

  3009. msgstr ""

  3010. 

  3011. #: ../../../CHANGELOG.md:1653

  3012. msgid "all homeserver-dependant services now need to be connected to the `traefik` container network, even if they don't need public internet exposure"

  3013. msgstr ""

  3014. 

  3015. #: ../../../CHANGELOG.md:1655

  3016. 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)."

  3017. msgstr ""

  3018. 

  3019. #: ../../../CHANGELOG.md:1657

  3020. 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."

  3021. msgstr ""

  3022. 

  3023. #: ../../../CHANGELOG.md:1659

  3024. 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."

  3025. msgstr ""

  3026. 

  3027. #: ../../../CHANGELOG.md:1661

  3028. 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."

  3029. msgstr ""

  3030. 

  3031. #: ../../../CHANGELOG.md:1663

  3032. msgid "People managing their own Traefik instance need to do minor changes"

  3033. msgstr ""

  3034. 

  3035. #: ../../../CHANGELOG.md:1665

  3036. 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."

  3037. msgstr ""

  3038. 

  3039. #: ../../../CHANGELOG.md:1667

  3040. 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."

  3041. msgstr ""

  3042. 

  3043. #: ../../../CHANGELOG.md:1669

  3044. msgid "People fronting Traefik with another reverse proxy need to do minor changes"

  3045. msgstr ""

  3046. 

  3047. #: ../../../CHANGELOG.md:1671

  3048. 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)."

  3049. msgstr ""

  3050. 

  3051. #: ../../../CHANGELOG.md:1673

  3052. 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)."

  3053. msgstr ""

  3054. 

  3055. #: ../../../CHANGELOG.md:1675

  3056. msgid "Supported reverse proxy types are now fewer"

  3057. msgstr ""

  3058. 

  3059. #: ../../../CHANGELOG.md:1677

  3060. 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`)."

  3061. msgstr ""

  3062. 

  3063. #: ../../../CHANGELOG.md:1679

  3064. msgid "Previously, we allowed you to set `matrix_playbook_reverse_proxy_type` to 7 different values to accommodate various reverse-proxy setups."

  3065. msgstr ""

  3066. 

  3067. #: ../../../CHANGELOG.md:1681

  3068. msgid "The complexity of this is too high, so we only support 3 values right now:"

  3069. msgstr ""

  3070. 

  3071. #: ../../../CHANGELOG.md:1683

  3072. 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)"

  3073. msgstr ""

  3074. 

  3075. #: ../../../CHANGELOG.md:1684

  3076. 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)"

  3077. msgstr ""

  3078. 

  3079. #: ../../../CHANGELOG.md:1685

  3080. 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)"

  3081. msgstr ""

  3082. 

  3083. #: ../../../CHANGELOG.md:1687

  3084. 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."

  3085. msgstr ""

  3086. 

  3087. #: ../../../CHANGELOG.md:1689

  3088. 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`."

  3089. msgstr ""

  3090. 

  3091. #: ../../../CHANGELOG.md:1691

  3092. msgid "If you were using these values as a way to stay away from Traefik, you now have 2 options:"

  3093. msgstr ""

  3094. 

  3095. #: ../../../CHANGELOG.md:1693

  3096. msgid "(recommended) [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)"

  3097. msgstr ""

  3098. 

  3099. #: ../../../CHANGELOG.md:1694

  3100. 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"

  3101. msgstr ""

  3102. 

  3103. #: ../../../CHANGELOG.md:1696

  3104. msgid "Container networking changes"

  3105. msgstr ""

  3106. 

  3107. #: ../../../CHANGELOG.md:1698

  3108. msgid "Now that `matrix-nginx-proxy` is not in the mix, it became easier to clear out some other long-overdue technical debt."

  3109. msgstr ""

  3110. 

  3111. #: ../../../CHANGELOG.md:1700

  3112. 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."

  3113. msgstr ""

  3114. 

  3115. #: ../../../CHANGELOG.md:1702

  3116. msgid "Moving components (especially the database) into other container networks was difficult — it required changes to many other components to ensure correct connectivity."

  3117. msgstr ""

  3118. 

  3119. #: ../../../CHANGELOG.md:1704

  3120. 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."

  3121. msgstr ""

  3122. 

  3123. #: ../../../CHANGELOG.md:1706

  3124. msgid "Carrying out these container networking changes necessitated modifying many components, so **we're hoping not too many bugs were introduced in the process**."

  3125. msgstr ""

  3126. 

  3127. #: ../../../CHANGELOG.md:1708

  3128. 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."

  3129. msgstr ""

  3130. 

  3131. #: ../../../CHANGELOG.md:1710

  3132. msgid "Metrics exposure changes"

  3133. msgstr ""

  3134. 

  3135. #: ../../../CHANGELOG.md:1712

  3136. msgid "This section is for people who are exposing monitoring metrics publicly, to be consumed by an external Prometheus server."

  3137. msgstr ""

  3138. 

  3139. #: ../../../CHANGELOG.md:1714

  3140. 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)."

  3141. msgstr ""

  3142. 

  3143. #: ../../../CHANGELOG.md:1716

  3144. 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."

  3145. msgstr ""

  3146. 

  3147. #: ../../../CHANGELOG.md:1718

  3148. 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."

  3149. msgstr ""

  3150. 

  3151. #: ../../../CHANGELOG.md:1720

  3152. 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!"

  3153. msgstr ""

  3154. 

  3155. #: ../../../CHANGELOG.md:1722

  3156. msgid "Matrix static files"

  3157. msgstr ""

  3158. 

  3159. #: ../../../CHANGELOG.md:1724

  3160. 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."

  3161. msgstr ""

  3162. 

  3163. #: ../../../CHANGELOG.md:1726

  3164. 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`)."

  3165. msgstr ""

  3166. 

  3167. #: ../../../CHANGELOG.md:1728

  3168. 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."

  3169. msgstr ""

  3170. 

  3171. #: ../../../CHANGELOG.md:1730

  3172. msgid "A note on performance"

  3173. msgstr ""

  3174. 

  3175. #: ../../../CHANGELOG.md:1732

  3176. msgid "Some of you have been voicing their concerns (for a long time) about Traefik being too slow and nginx being better."

  3177. msgstr ""

  3178. 

  3179. #: ../../../CHANGELOG.md:1734

  3180. 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."

  3181. msgstr ""

  3182. 

  3183. #: ../../../CHANGELOG.md:1736

  3184. msgid "We believe that using Traefik provides way too many benefits to worry about this minor performance impairment."

  3185. msgstr ""

  3186. 

  3187. #: ../../../CHANGELOG.md:1738

  3188. 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."

  3189. msgstr ""

  3190. 

  3191. #: ../../../CHANGELOG.md:1740

  3192. 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."

  3193. msgstr ""

  3194. 

  3195. #: ../../../CHANGELOG.md:1742

  3196. 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."

  3197. msgstr ""

  3198. 

  3199. #: ../../../CHANGELOG.md:1744

  3200. msgid "Migration procedure"

  3201. msgstr ""

  3202. 

  3203. #: ../../../CHANGELOG.md:1746

  3204. msgid "The updated playbook will automatically perform some migration tasks for you:"

  3205. msgstr ""

  3206. 

  3207. #: ../../../CHANGELOG.md:1748

  3208. 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."

  3209. msgstr ""

  3210. 

  3211. #: ../../../CHANGELOG.md:1750

  3212. 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."

  3213. msgstr ""

  3214. 

  3215. #: ../../../CHANGELOG.md:1752

  3216. 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."

  3217. msgstr ""

  3218. 

  3219. #: ../../../CHANGELOG.md:1754

  3220. 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."

  3221. msgstr ""

  3222. 

  3223. #: ../../../CHANGELOG.md:1756

  3224. 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."

  3225. msgstr ""

  3226. 

  3227. #: ../../../CHANGELOG.md:1758

  3228. 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."

  3229. msgstr ""

  3230. 

  3231. #: ../../../CHANGELOG.md:1760

  3232. msgid "We don't recommend changing these variables and suppressing warnings, unless you know what you're doing."

  3233. msgstr ""

  3234. 

  3235. #: ../../../CHANGELOG.md:1762

  3236. 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."

  3237. msgstr ""

  3238. 

  3239. #: ../../../CHANGELOG.md:1764

  3240. msgid "Conclusion"

  3241. msgstr ""

  3242. 

  3243. #: ../../../CHANGELOG.md:1766

  3244. 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."

  3245. msgstr ""

  3246. 

  3247. #: ../../../CHANGELOG.md:1768

  3248. 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!"

  3249. msgstr ""

  3250. 

  3251. #: ../../../CHANGELOG.md:1771

  3252. msgid "2024-01-14"

  3253. msgstr ""

  3254. 

  3255. #: ../../../CHANGELOG.md:1773

  3256. msgid "(Backward Compatibility) Configuration changes required for people fronting the integrated reverse-proxy webserver with another reverse-proxy"

  3257. msgstr ""

  3258. 

  3259. #: ../../../CHANGELOG.md:1775

  3260. 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."

  3261. msgstr ""

  3262. 

  3263. #: ../../../CHANGELOG.md:1777

  3264. 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."

  3265. msgstr ""

  3266. 

  3267. #: ../../../CHANGELOG.md:1779

  3268. 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."

  3269. msgstr ""

  3270. 

  3271. #: ../../../CHANGELOG.md:1781

  3272. 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`."

  3273. msgstr ""

  3274. 

  3275. #: ../../../CHANGELOG.md:1783

  3276. msgid "Adapt your configuration as seen below:"

  3277. msgstr ""

  3278. 

  3279. #: ../../../CHANGELOG.md:1816

  3280. 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."

  3281. msgstr ""

  3282. 

  3283. #: ../../../CHANGELOG.md:1819

  3284. msgid "2024-01-13"

  3285. msgstr ""

  3286. 

  3287. #: ../../../CHANGELOG.md:1821

  3288. msgid "matrix-reminder-bot update with more secure (backward-incompatible) default settings"

  3289. msgstr ""

  3290. 

  3291. #: ../../../CHANGELOG.md:1823

  3292. 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."

  3293. msgstr ""

  3294. 

  3295. #: ../../../CHANGELOG.md:1825

  3296. 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)."

  3297. msgstr ""

  3298. 

  3299. #: ../../../CHANGELOG.md:1827

  3300. 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."

  3301. msgstr ""

  3302. 

  3303. #: ../../../CHANGELOG.md:1829

  3304. 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."

  3305. msgstr ""

  3306. 

  3307. #: ../../../CHANGELOG.md:1831

  3308. 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."

  3309. msgstr ""

  3310. 

  3311. #: ../../../CHANGELOG.md:1833

  3312. msgid "If you need **to undo or tweak these security improvements**, you can change your `vars.yml` file to:"

  3313. msgstr ""

  3314. 

  3315. #: ../../../CHANGELOG.md:1835

  3316. msgid "disable the allowlist (`matrix_bot_matrix_reminder_bot_allowlist_enabled: false`), making the bot allow usage by anyone, anywhere"

  3317. msgstr ""

  3318. 

  3319. #: ../../../CHANGELOG.md:1837

  3320. 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))"

  3321. msgstr ""

  3322. 

  3323. #: ../../../CHANGELOG.md:1839

  3324. msgid "override the default allowlist (in the `group_vars/matrix_servers` file) by redefining `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`"

  3325. msgstr ""

  3326. 

  3327. #: ../../../CHANGELOG.md:1842

  3328. msgid "2024-01-05"

  3329. msgstr ""

  3330. 

  3331. #: ../../../CHANGELOG.md:1844

  3332. msgid "matrix-mailer has been replaced by the exim-relay external role"

  3333. msgstr ""

  3334. 

  3335. #: ../../../CHANGELOG.md:1846

  3336. #: ../../../CHANGELOG.md:2484

  3337. 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."

  3338. msgstr ""

  3339. 

  3340. #: ../../../CHANGELOG.md:1848

  3341. 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."

  3342. msgstr ""

  3343. 

  3344. #: ../../../CHANGELOG.md:1850

  3345. msgid "To migrate:"

  3346. msgstr ""

  3347. 

  3348. #: ../../../CHANGELOG.md:1852

  3349. msgid "pull the playbook changes, as usual"

  3350. msgstr ""

  3351. 

  3352. #: ../../../CHANGELOG.md:1853

  3353. msgid "update your roles (run `just roles` or `make roles`)"

  3354. msgstr ""

  3355. 

  3356. #: ../../../CHANGELOG.md:1854

  3357. 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."

  3358. msgstr ""

  3359. 

  3360. #: ../../../CHANGELOG.md:1855

  3361. msgid "re-run the playbook (`install-all` or `setup-all`)"

  3362. msgstr ""

  3363. 

  3364. #: ../../../CHANGELOG.md:1857

  3365. 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`)."

  3366. msgstr ""

  3367. 

  3368. #: ../../../CHANGELOG.md:1860

  3369. msgid "2024-01-02"

  3370. msgstr ""

  3371. 

  3372. #: ../../../CHANGELOG.md:1862

  3373. msgid "mautrix-signal now powered by the new Go-based bridge"

  3374. msgstr ""

  3375. 

  3376. #: ../../../CHANGELOG.md:1864

  3377. 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."

  3378. msgstr ""

  3379. 

  3380. #: ../../../CHANGELOG.md:1866

  3381. 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)."

  3382. msgstr ""

  3383. 

  3384. #: ../../../CHANGELOG.md:1868

  3385. 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."

  3386. msgstr ""

  3387. 

  3388. #: ../../../CHANGELOG.md:1871

  3389. msgid "2023-10-23"

  3390. msgstr ""

  3391. 

  3392. #: ../../../CHANGELOG.md:1873

  3393. msgid "Enabling `allow_public_rooms_over_federation` by default for Synapse"

  3394. msgstr ""

  3395. 

  3396. #: ../../../CHANGELOG.md:1875

  3397. 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."

  3398. msgstr ""

  3399. 

  3400. #: ../../../CHANGELOG.md:1877

  3401. 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."

  3402. msgstr ""

  3403. 

  3404. #: ../../../CHANGELOG.md:1879

  3405. 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)."

  3406. msgstr ""

  3407. 

  3408. #: ../../../CHANGELOG.md:1881

  3409. 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."

  3410. msgstr ""

  3411. 

  3412. #: ../../../CHANGELOG.md:1883

  3413. 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."

  3414. msgstr ""

  3415. 

  3416. #: ../../../CHANGELOG.md:1885

  3417. msgid "The **historical reasoning** behind this change is as follows:"

  3418. msgstr ""

  3419. 

  3420. #: ../../../CHANGELOG.md:1887

  3421. 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."

  3422. msgstr ""

  3423. 

  3424. #: ../../../CHANGELOG.md:1889

  3425. 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."

  3426. msgstr ""

  3427. 

  3428. #: ../../../CHANGELOG.md:1891

  3429. 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."

  3430. msgstr ""

  3431. 

  3432. #: ../../../CHANGELOG.md:1893

  3433. msgid "Here are **actions you may wish to take** as a result of this change:"

  3434. msgstr ""

  3435. 

  3436. #: ../../../CHANGELOG.md:1895

  3437. 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."

  3438. msgstr ""

  3439. 

  3440. #: ../../../CHANGELOG.md:1897

  3441. 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."

  3442. msgstr ""

  3443. 

  3444. #: ../../../CHANGELOG.md:1899

  3445. 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."

  3446. msgstr ""

  3447. 

  3448. #: ../../../CHANGELOG.md:1902

  3449. msgid "2023-10-18"

  3450. msgstr ""

  3451. 

  3452. #: ../../../CHANGELOG.md:1904

  3453. msgid "Postgres parameters are automatically tuned now"

  3454. msgstr ""

  3455. 

  3456. #: ../../../CHANGELOG.md:1906

  3457. msgid "The playbook has provided some hints about [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) for quite a while now."

  3458. msgstr ""

  3459. 

  3460. #: ../../../CHANGELOG.md:1908

  3461. 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/."

  3462. msgstr ""

  3463. 

  3464. #: ../../../CHANGELOG.md:1910

  3465. 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."

  3466. msgstr ""

  3467. 

  3468. #: ../../../CHANGELOG.md:1912

  3469. 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."

  3470. msgstr ""

  3471. 

  3472. #: ../../../CHANGELOG.md:1915

  3473. msgid "2023-08-31"

  3474. msgstr ""

  3475. 

  3476. #: ../../../CHANGELOG.md:1917

  3477. msgid "SchildiChat Web support"

  3478. msgstr ""

  3479. 

  3480. #: ../../../CHANGELOG.md:1919

  3481. 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."

  3482. msgstr ""

  3483. 

  3484. #: ../../../CHANGELOG.md:1921

  3485. msgid "See our [Configuring SchildiChat Web](docs/configuring-playbook-client-schildichat-web.md) documentation to get started."

  3486. msgstr ""

  3487. 

  3488. #: ../../../CHANGELOG.md:1924

  3489. msgid "2023-08-23"

  3490. msgstr ""

  3491. 

  3492. #: ../../../CHANGELOG.md:1926

  3493. msgid "mautrix-wsproxy support"

  3494. msgstr ""

  3495. 

  3496. #: ../../../CHANGELOG.md:1928

  3497. 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)."

  3498. msgstr ""

  3499. 

  3500. #: ../../../CHANGELOG.md:1930

  3501. 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."

  3502. msgstr ""

  3503. 

  3504. #: ../../../CHANGELOG.md:1933

  3505. msgid "2023-07-24"

  3506. msgstr ""

  3507. 

  3508. #: ../../../CHANGELOG.md:1935

  3509. msgid "matrix-registration-bot usage changed"

  3510. msgstr ""

  3511. 

  3512. #: ../../../CHANGELOG.md:1937

  3513. 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."

  3514. msgstr ""

  3515. 

  3516. #: ../../../CHANGELOG.md:1939

  3517. 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"

  3518. msgstr ""

  3519. 

  3520. #: ../../../CHANGELOG.md:1941

  3521. msgid "`matrix_bot_matrix_registration_bot_bot_access_token`"

  3522. msgstr ""

  3523. 

  3524. #: ../../../CHANGELOG.md:1942

  3525. msgid "`matrix_bot_matrix_registration_bot_api_token`"

  3526. msgstr ""

  3527. 

  3528. #: ../../../CHANGELOG.md:1945

  3529. msgid "2023-07-21"

  3530. msgstr ""

  3531. 

  3532. #: ../../../CHANGELOG.md:1947

  3533. msgid "mautrix-gmessages support"

  3534. msgstr ""

  3535. 

  3536. #: ../../../CHANGELOG.md:1949

  3537. 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."

  3538. msgstr ""

  3539. 

  3540. #: ../../../CHANGELOG.md:1952

  3541. msgid "2023-07-17"

  3542. msgstr ""

  3543. 

  3544. #: ../../../CHANGELOG.md:1954

  3545. msgid "matrix-media-repo support"

  3546. msgstr ""

  3547. 

  3548. #: ../../../CHANGELOG.md:1956

  3549. 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."

  3550. msgstr ""

  3551. 

  3552. #: ../../../CHANGELOG.md:1958

  3553. msgid "To learn more see our [Storing Matrix media files using matrix-media-repo](docs/configuring-playbook-matrix-media-repo.md) documentation page."

  3554. msgstr ""

  3555. 

  3556. #: ../../../CHANGELOG.md:1961

  3557. msgid "2023-05-25"

  3558. msgstr ""

  3559. 

  3560. #: ../../../CHANGELOG.md:1963

  3561. msgid "Enabling `forget_rooms_on_leave` by default for Synapse"

  3562. msgstr ""

  3563. 

  3564. #: ../../../CHANGELOG.md:1965

  3565. 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**."

  3566. msgstr ""

  3567. 

  3568. #: ../../../CHANGELOG.md:1967

  3569. msgid "The upstream Synapse default is `false` (disabled), so that you must forget rooms manually after leaving."

  3570. msgstr ""

  3571. 

  3572. #: ../../../CHANGELOG.md:1969

  3573. 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."

  3574. msgstr ""

  3575. 

  3576. #: ../../../CHANGELOG.md:1971

  3577. 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`"

  3578. msgstr ""

  3579. 

  3580. #: ../../../CHANGELOG.md:1974

  3581. msgid "2023-04-03"

  3582. msgstr ""

  3583. 

  3584. #: ../../../CHANGELOG.md:1976

  3585. msgid "The matrix-jitsi role lives independently now"

  3586. msgstr ""

  3587. 

  3588. #: ../../../CHANGELOG.md:1978

  3589. 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."

  3590. msgstr ""

  3591. 

  3592. #: ../../../CHANGELOG.md:1980

  3593. 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."

  3594. msgstr ""

  3595. 

  3596. #: ../../../CHANGELOG.md:1982

  3597. msgid "As part of the extraction process of this role out of the Matrix playbook, a few other things improved:"

  3598. msgstr ""

  3599. 

  3600. #: ../../../CHANGELOG.md:1984

  3601. msgid "**native Traefik support** has been added"

  3602. msgstr ""

  3603. 

  3604. #: ../../../CHANGELOG.md:1985

  3605. 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)"

  3606. msgstr ""

  3607. 

  3608. #: ../../../CHANGELOG.md:1987

  3609. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Jitsi or not."

  3610. msgstr ""

  3611. 

  3612. #: ../../../CHANGELOG.md:1989

  3613. msgid "If you're making use of Jitsi via this playbook, you will need to update variable references in your `vars.yml` file:"

  3614. msgstr ""

  3615. 

  3616. #: ../../../CHANGELOG.md:1991

  3617. msgid "`matrix_jitsi_*_docker_image_` -> `matrix_jitsi_*_container_image_`"

  3618. msgstr ""

  3619. 

  3620. #: ../../../CHANGELOG.md:1992

  3621. msgid "`matrix_jitsi_` -> `jitsi_`"

  3622. msgstr ""

  3623. 

  3624. #: ../../../CHANGELOG.md:1993

  3625. #: ../../../CHANGELOG.md:2020

  3626. msgid "some other internal variables have changed, but the playbook will tell you about them"

  3627. msgstr ""

  3628. 

  3629. #: ../../../CHANGELOG.md:1995

  3630. msgid "2023-03-22"

  3631. msgstr ""

  3632. 

  3633. #: ../../../CHANGELOG.md:1997

  3634. msgid "ntfy Web App is disabled by default"

  3635. msgstr ""

  3636. 

  3637. #: ../../../CHANGELOG.md:1999

  3638. 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))."

  3639. msgstr ""

  3640. 

  3641. #: ../../../CHANGELOG.md:2001

  3642. 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))."

  3643. msgstr ""

  3644. 

  3645. #: ../../../CHANGELOG.md:2004

  3646. msgid "2023-03-21"

  3647. msgstr ""

  3648. 

  3649. #: ../../../CHANGELOG.md:2006

  3650. msgid "The matrix-prometheus role lives independently now"

  3651. msgstr ""

  3652. 

  3653. #: ../../../CHANGELOG.md:2008

  3654. 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."

  3655. msgstr ""

  3656. 

  3657. #: ../../../CHANGELOG.md:2010

  3658. 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."

  3659. msgstr ""

  3660. 

  3661. #: ../../../CHANGELOG.md:2012

  3662. 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."

  3663. msgstr ""

  3664. 

  3665. #: ../../../CHANGELOG.md:2014

  3666. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Prometheus or not."

  3667. msgstr ""

  3668. 

  3669. #: ../../../CHANGELOG.md:2016

  3670. msgid "If you're making use of Prometheus via this playbook, you will need to update variable references in your `vars.yml` file:"

  3671. msgstr ""

  3672. 

  3673. #: ../../../CHANGELOG.md:2018

  3674. msgid "`matrix_prometheus_docker_image_` -> `matrix_prometheus_container_image_`"

  3675. msgstr ""

  3676. 

  3677. #: ../../../CHANGELOG.md:2019

  3678. msgid "`matrix_prometheus_` -> `prometheus_`"

  3679. msgstr ""

  3680. 

  3681. #: ../../../CHANGELOG.md:2023

  3682. msgid "2023-03-12"

  3683. msgstr ""

  3684. 

  3685. #: ../../../CHANGELOG.md:2025

  3686. msgid "synapse-auto-compressor support"

  3687. msgstr ""

  3688. 

  3689. #: ../../../CHANGELOG.md:2027

  3690. 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."

  3691. msgstr ""

  3692. 

  3693. #: ../../../CHANGELOG.md:2029

  3694. 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:"

  3695. msgstr ""

  3696. 

  3697. #: ../../../CHANGELOG.md:2031

  3698. msgid "it runs on a more up-to-date version of `rust-synapse-compress-state`"

  3699. msgstr ""

  3700. 

  3701. #: ../../../CHANGELOG.md:2032

  3702. msgid "it's a set-it-and-forget-it tool that you can enable and never have to deal with manual compression anymore"

  3703. msgstr ""

  3704. 

  3705. #: ../../../CHANGELOG.md:2034

  3706. msgid "This tool needs to be enabled manually, for now. In the future, we're considering enabling it by default for all Synapse installations."

  3707. msgstr ""

  3708. 

  3709. #: ../../../CHANGELOG.md:2036

  3710. msgid "See our [Setting up synapse-auto-compressor](docs/configuring-playbook-synapse-auto-compressor.md) documentation to get started."

  3711. msgstr ""

  3712. 

  3713. #: ../../../CHANGELOG.md:2039

  3714. msgid "2023-03-07"

  3715. msgstr ""

  3716. 

  3717. #: ../../../CHANGELOG.md:2041

  3718. msgid "Sliding Sync proxy (Element X) support"

  3719. msgstr ""

  3720. 

  3721. #: ../../../CHANGELOG.md:2043

  3722. 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)."

  3723. msgstr ""

  3724. 

  3725. #: ../../../CHANGELOG.md:2045

  3726. 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."

  3727. msgstr ""

  3728. 

  3729. #: ../../../CHANGELOG.md:2047

  3730. msgid "To get started, see our [Setting up the Sliding Sync proxy](docs/configuring-playbook-sliding-sync-proxy.md) documentation page."

  3731. msgstr ""

  3732. 

  3733. #: ../../../CHANGELOG.md:2050

  3734. msgid "2023-03-02"

  3735. msgstr ""

  3736. 

  3737. #: ../../../CHANGELOG.md:2052

  3738. msgid "The matrix-etherpad role lives independently now"

  3739. msgstr ""

  3740. 

  3741. #: ../../../CHANGELOG.md:2054

  3742. 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."

  3743. msgstr ""

  3744. 

  3745. #: ../../../CHANGELOG.md:2056

  3746. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Etherpad or not."

  3747. msgstr ""

  3748. 

  3749. #: ../../../CHANGELOG.md:2058

  3750. msgid "If you're making use of Etherpad via this playbook, you will need to update variable references in your `vars.yml` file:"

  3751. msgstr ""

  3752. 

  3753. #: ../../../CHANGELOG.md:2060

  3754. msgid "Rename `matrix_etherpad_public_endpoint` to `etherpad_path_prefix`"

  3755. msgstr ""

  3756. 

  3757. #: ../../../CHANGELOG.md:2062

  3758. msgid "Replace `matrix_etherpad_mode: dimension` with:"

  3759. msgstr ""

  3760. 

  3761. #: ../../../CHANGELOG.md:2063

  3762. msgid "for `matrix-nginx-proxy` users:"

  3763. msgstr ""

  3764. 

  3765. #: ../../../CHANGELOG.md:2064

  3766. msgid "`etherpad_nginx_proxy_dimension_integration_enabled: true`"

  3767. msgstr ""

  3768. 

  3769. #: ../../../CHANGELOG.md:2065

  3770. msgid "`etherpad_hostname: \"{{ matrix_server_fqn_dimension }}\"`"

  3771. msgstr ""

  3772. 

  3773. #: ../../../CHANGELOG.md:2066

  3774. msgid "for Traefik users:"

  3775. msgstr ""

  3776. 

  3777. #: ../../../CHANGELOG.md:2067

  3778. msgid "define your own `etherpad_hostname` and `etherpad_path_prefix` as you see fit"

  3779. msgstr ""

  3780. 

  3781. #: ../../../CHANGELOG.md:2069

  3782. msgid "Rename all other variables:"

  3783. msgstr ""

  3784. 

  3785. #: ../../../CHANGELOG.md:2070

  3786. msgid "`matrix_etherpad_docker_image_` -> `matrix_etherpad_container_image_`"

  3787. msgstr ""

  3788. 

  3789. #: ../../../CHANGELOG.md:2071

  3790. msgid "`matrix_etherpad_` -> `etherpad_`"

  3791. msgstr ""

  3792. 

  3793. #: ../../../CHANGELOG.md:2073

  3794. msgid "Along with this relocation, the new role also:"

  3795. msgstr ""

  3796. 

  3797. #: ../../../CHANGELOG.md:2075

  3798. msgid "supports [self-building](docs/self-building.md), so it should work on `arm32` and `arm64` architectures"

  3799. msgstr ""

  3800. 

  3801. #: ../../../CHANGELOG.md:2076

  3802. msgid "has native Traefik reverse-proxy support (Etherpad requests no longer go through `matrix-nginx-proxy` when using Traefik)"

  3803. msgstr ""

  3804. 

  3805. #: ../../../CHANGELOG.md:2079

  3806. msgid "2023-02-26"

  3807. msgstr ""

  3808. 

  3809. #: ../../../CHANGELOG.md:2081

  3810. msgid "Traefik is the default reverse-proxy now"

  3811. msgstr ""

  3812. 

  3813. #: ../../../CHANGELOG.md:2083

  3814. 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."

  3815. msgstr ""

  3816. 

  3817. #: ../../../CHANGELOG.md:2085

  3818. 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."

  3819. msgstr ""

  3820. 

  3821. #: ../../../CHANGELOG.md:2087

  3822. 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:"

  3823. msgstr ""

  3824. 

  3825. #: ../../../CHANGELOG.md:2089

  3826. msgid "Traefik managed by the playbook"

  3827. msgstr ""

  3828. 

  3829. #: ../../../CHANGELOG.md:2090

  3830. msgid "Traefik managed by the user in another way"

  3831. msgstr ""

  3832. 

  3833. #: ../../../CHANGELOG.md:2091

  3834. msgid "another reverse-proxy on the same host (`127.0.0.1` port exposure)"

  3835. msgstr ""

  3836. 

  3837. #: ../../../CHANGELOG.md:2092

  3838. msgid "another reverse-proxy on another host (`0.0.0.0` port exposure)"

  3839. msgstr ""

  3840. 

  3841. #: ../../../CHANGELOG.md:2093

  3842. msgid "`matrix-nginx-proxy` — an `nginx` container managed by the playbook"

  3843. msgstr ""

  3844. 

  3845. #: ../../../CHANGELOG.md:2094

  3846. msgid "`nginx` webserver operated by the user, running without a container on the same server"

  3847. msgstr ""

  3848. 

  3849. #: ../../../CHANGELOG.md:2096

  3850. 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."

  3851. msgstr ""

  3852. 

  3853. #: ../../../CHANGELOG.md:2098

  3854. 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."

  3855. msgstr ""

  3856. 

  3857. #: ../../../CHANGELOG.md:2100

  3858. msgid "It's time for the **next step in our migration process** to Traefik and elimination of `matrix-nginx-proxy`:"

  3859. msgstr ""

  3860. 

  3861. #: ../../../CHANGELOG.md:2102

  3862. msgid "Traefik is now the default reverse-proxy for new installations"

  3863. msgstr ""

  3864. 

  3865. #: ../../../CHANGELOG.md:2103

  3866. 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"

  3867. msgstr ""

  3868. 

  3869. #: ../../../CHANGELOG.md:2105

  3870. msgid "How do I switch my existing setup to Traefik?"

  3871. msgstr ""

  3872. 

  3873. #: ../../../CHANGELOG.md:2107

  3874. 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)."

  3875. msgstr ""

  3876. 

  3877. #: ../../../CHANGELOG.md:2109

  3878. msgid "If you experience trouble:"

  3879. msgstr ""

  3880. 

  3881. #: ../../../CHANGELOG.md:2111

  3882. 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"

  3883. msgstr ""

  3884. 

  3885. #: ../../../CHANGELOG.md:2112

  3886. msgid "Ask for help in our [support channels](README.md#support)"

  3887. msgstr ""

  3888. 

  3889. #: ../../../CHANGELOG.md:2113

  3890. msgid "Try switching to Traefik again later"

  3891. msgstr ""

  3892. 

  3893. #: ../../../CHANGELOG.md:2115

  3894. 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."

  3895. msgstr ""

  3896. 

  3897. #: ../../../CHANGELOG.md:2117

  3898. msgid "I already use my own Traefik server. How do I plug that in?"

  3899. msgstr ""

  3900. 

  3901. #: ../../../CHANGELOG.md:2119

  3902. msgid "See the [Traefik managed by the playbook](docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) section."

  3903. msgstr ""

  3904. 

  3905. #: ../../../CHANGELOG.md:2121

  3906. msgid "Why is matrix-nginx-proxy used even after switching to Traefik?"

  3907. msgstr ""

  3908. 

  3909. #: ../../../CHANGELOG.md:2123

  3910. msgid "This playbook manages many different services. All these services were initially integrated with `matrix-nginx-proxy`."

  3911. msgstr ""

  3912. 

  3913. #: ../../../CHANGELOG.md:2125

  3914. 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."

  3915. msgstr ""

  3916. 

  3917. #: ../../../CHANGELOG.md:2127

  3918. msgid "How do I remain on matrix-nginx-proxy?"

  3919. msgstr ""

  3920. 

  3921. #: ../../../CHANGELOG.md:2129

  3922. 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."

  3923. msgstr ""

  3924. 

  3925. #: ../../../CHANGELOG.md:2131

  3926. msgid "To proceed regardless of this warning, add `matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your configuration."

  3927. msgstr ""

  3928. 

  3929. #: ../../../CHANGELOG.md:2133

  3930. 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."

  3931. msgstr ""

  3932. 

  3933. #: ../../../CHANGELOG.md:2135

  3934. msgid "How do I keep using my own other reverse-proxy?"

  3935. msgstr ""

  3936. 

  3937. #: ../../../CHANGELOG.md:2137

  3938. 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)."

  3939. msgstr ""

  3940. 

  3941. #: ../../../CHANGELOG.md:2140

  3942. msgid "2023-02-25"

  3943. msgstr ""

  3944. 

  3945. #: ../../../CHANGELOG.md:2142

  3946. msgid "rageshake support"

  3947. msgstr ""

  3948. 

  3949. #: ../../../CHANGELOG.md:2144

  3950. 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."

  3951. msgstr ""

  3952. 

  3953. #: ../../../CHANGELOG.md:2146

  3954. msgid "Additional details are available in [Setting up rageshake](docs/configuring-playbook-rageshake.md)."

  3955. msgstr ""

  3956. 

  3957. #: ../../../CHANGELOG.md:2149

  3958. msgid "2023-02-17"

  3959. msgstr ""

  3960. 

  3961. #: ../../../CHANGELOG.md:2151

  3962. msgid "Synapse templates customization support"

  3963. msgstr ""

  3964. 

  3965. #: ../../../CHANGELOG.md:2153

  3966. msgid "The playbook can now help you customize Synapse's templates."

  3967. msgstr ""

  3968. 

  3969. #: ../../../CHANGELOG.md:2155

  3970. msgid "Additional details are available in the [Customizing templates](docs/configuring-playbook-synapse.md#customizing-templates) section of our Synapse documentation."

  3971. msgstr ""

  3972. 

  3973. #: ../../../CHANGELOG.md:2157

  3974. msgid "The matrix-redis role lives independently now"

  3975. msgstr ""

  3976. 

  3977. #: ../../../CHANGELOG.md:2159

  3978. msgid "**TLDR**: the `matrix-redis` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3979. msgstr ""

  3980. 

  3981. #: ../../../CHANGELOG.md:2161

  3982. 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."

  3983. msgstr ""

  3984. 

  3985. #: ../../../CHANGELOG.md:2163

  3986. 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_`)."

  3987. msgstr ""

  3988. 

  3989. #: ../../../CHANGELOG.md:2165

  3990. msgid "The matrix-ntfy role lives independently now"

  3991. msgstr ""

  3992. 

  3993. #: ../../../CHANGELOG.md:2167

  3994. msgid "**TLDR**: the `matrix-ntfy` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3995. msgstr ""

  3996. 

  3997. #: ../../../CHANGELOG.md:2169

  3998. 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."

  3999. msgstr ""

  4000. 

  4001. #: ../../../CHANGELOG.md:2171

  4002. 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_`)."

  4003. msgstr ""

  4004. 

  4005. #: ../../../CHANGELOG.md:2174

  4006. msgid "2023-02-15"

  4007. msgstr ""

  4008. 

  4009. #: ../../../CHANGELOG.md:2176

  4010. msgid "The matrix-grafana role lives independently now"

  4011. msgstr ""

  4012. 

  4013. #: ../../../CHANGELOG.md:2178

  4014. msgid "**TLDR**: the `matrix-grafana` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  4015. msgstr ""

  4016. 

  4017. #: ../../../CHANGELOG.md:2180

  4018. 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."

  4019. msgstr ""

  4020. 

  4021. #: ../../../CHANGELOG.md:2182

  4022. 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_`)."

  4023. msgstr ""

  4024. 

  4025. #: ../../../CHANGELOG.md:2185

  4026. msgid "2023-02-13"

  4027. msgstr ""

  4028. 

  4029. #: ../../../CHANGELOG.md:2187

  4030. msgid "The matrix-backup-borg role lives independently now"

  4031. msgstr ""

  4032. 

  4033. #: ../../../CHANGELOG.md:2189

  4034. msgid "**TLDR**: the `matrix-backup-borg` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  4035. msgstr ""

  4036. 

  4037. #: ../../../CHANGELOG.md:2191

  4038. 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."

  4039. msgstr ""

  4040. 

  4041. #: ../../../CHANGELOG.md:2193

  4042. 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_`)."

  4043. msgstr ""

  4044. 

  4045. #: ../../../CHANGELOG.md:2196

  4046. msgid "2023-02-12"

  4047. msgstr ""

  4048. 

  4049. #: ../../../CHANGELOG.md:2198

  4050. msgid "(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support"

  4051. msgstr ""

  4052. 

  4053. #: ../../../CHANGELOG.md:2200

  4054. msgid "**TLDR**:"

  4055. msgstr ""

  4056. 

  4057. #: ../../../CHANGELOG.md:2202

  4058. 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."

  4059. msgstr ""

  4060. 

  4061. #: ../../../CHANGELOG.md:2203

  4062. 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."

  4063. msgstr ""

  4064. 

  4065. #: ../../../CHANGELOG.md:2204

  4066. 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`"

  4067. msgstr ""

  4068. 

  4069. #: ../../../CHANGELOG.md:2205

  4070. 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."

  4071. msgstr ""

  4072. 

  4073. #: ../../../CHANGELOG.md:2206

  4074. 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"

  4075. msgstr ""

  4076. 

  4077. #: ../../../CHANGELOG.md:2208

  4078. msgid "Motivation for redoing our reverse-proxy setup"

  4079. msgstr ""

  4080. 

  4081. #: ../../../CHANGELOG.md:2210

  4082. 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**."

  4083. msgstr ""

  4084. 

  4085. #: ../../../CHANGELOG.md:2212

  4086. 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**."

  4087. msgstr ""

  4088. 

  4089. #: ../../../CHANGELOG.md:2214

  4090. 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."

  4091. msgstr ""

  4092. 

  4093. #: ../../../CHANGELOG.md:2216

  4094. 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."

  4095. msgstr ""

  4096. 

  4097. #: ../../../CHANGELOG.md:2218

  4098. 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:"

  4099. msgstr ""

  4100. 

  4101. #: ../../../CHANGELOG.md:2220

  4102. msgid "*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined with exposing services manually (setting `_bind_port` variables)"

  4103. msgstr ""

  4104. 

  4105. #: ../../../CHANGELOG.md:2221

  4106. msgid "*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in `http`-only mode (no SSL certificate retrieval)."

  4107. msgstr ""

  4108. 

  4109. #: ../../../CHANGELOG.md:2223

  4110. msgid "Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations."

  4111. msgstr ""

  4112. 

  4113. #: ../../../CHANGELOG.md:2225

  4114. 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)."

  4115. msgstr ""

  4116. 

  4117. #: ../../../CHANGELOG.md:2227

  4118. msgid "The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks:"

  4119. msgstr ""

  4120. 

  4121. #: ../../../CHANGELOG.md:2229

  4122. 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"

  4123. msgstr ""

  4124. 

  4125. #: ../../../CHANGELOG.md:2230

  4126. 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"

  4127. msgstr ""

  4128. 

  4129. #: ../../../CHANGELOG.md:2231

  4130. msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) — for hosting the [Nextcloud](https://nextcloud.com/) groupware platform"

  4131. msgstr ""

  4132. 

  4133. #: ../../../CHANGELOG.md:2233

  4134. 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."

  4135. msgstr ""

  4136. 

  4137. #: ../../../CHANGELOG.md:2235

  4138. 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`."

  4139. msgstr ""

  4140. 

  4141. #: ../../../CHANGELOG.md:2237

  4142. 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."

  4143. msgstr ""

  4144. 

  4145. #: ../../../CHANGELOG.md:2239

  4146. msgid "How do these changes fix all these problems?"

  4147. msgstr ""

  4148. 

  4149. #: ../../../CHANGELOG.md:2241

  4150. 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."

  4151. msgstr ""

  4152. 

  4153. #: ../../../CHANGELOG.md:2243

  4154. 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."

  4155. msgstr ""

  4156. 

  4157. #: ../../../CHANGELOG.md:2245

  4158. 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."

  4159. msgstr ""

  4160. 

  4161. #: ../../../CHANGELOG.md:2247

  4162. 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."

  4163. msgstr ""

  4164. 

  4165. #: ../../../CHANGELOG.md:2249

  4166. 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."

  4167. msgstr ""

  4168. 

  4169. #: ../../../CHANGELOG.md:2251

  4170. 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."

  4171. msgstr ""

  4172. 

  4173. #: ../../../CHANGELOG.md:2253

  4174. msgid "Where we're at right now?"

  4175. msgstr ""

  4176. 

  4177. #: ../../../CHANGELOG.md:2255

  4178. msgid "`matrix_playbook_reverse_proxy_type` still defaults to a value of `playbook-managed-nginx`."

  4179. msgstr ""

  4180. 

  4181. #: ../../../CHANGELOG.md:2257

  4182. 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."

  4183. msgstr ""

  4184. 

  4185. #: ../../../CHANGELOG.md:2259

  4186. 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`."

  4187. msgstr ""

  4188. 

  4189. #: ../../../CHANGELOG.md:2261

  4190. msgid "How do I explicitly switch to Traefik right now?"

  4191. msgstr ""

  4192. 

  4193. #: ../../../CHANGELOG.md:2263

  4194. msgid "**Users who wish to migrate to Traefik** today, can do so by **adding** this to their configuration:"

  4195. msgstr ""

  4196. 

  4197. #: ../../../CHANGELOG.md:2269

  4198. 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."

  4199. msgstr ""

  4200. 

  4201. #: ../../../CHANGELOG.md:2271

  4202. 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."

  4203. msgstr ""

  4204. 

  4205. #: ../../../CHANGELOG.md:2273

  4206. 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."

  4207. msgstr ""

  4208. 

  4209. #: ../../../CHANGELOG.md:2275

  4210. 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."

  4211. msgstr ""

  4212. 

  4213. #: ../../../CHANGELOG.md:2277

  4214. 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."

  4215. msgstr ""

  4216. 

  4217. #: ../../../CHANGELOG.md:2279

  4218. 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."

  4219. msgstr ""

  4220. 

  4221. #: ../../../CHANGELOG.md:2281

  4222. msgid "Where we're going in the near future?"

  4223. msgstr ""

  4224. 

  4225. #: ../../../CHANGELOG.md:2283

  4226. 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."

  4227. msgstr ""

  4228. 

  4229. #: ../../../CHANGELOG.md:2285

  4230. msgid "For now, `matrix-nginx-proxy` will stay around."

  4231. msgstr ""

  4232. 

  4233. #: ../../../CHANGELOG.md:2287

  4234. 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."

  4235. msgstr ""

  4236. 

  4237. #: ../../../CHANGELOG.md:2289

  4238. 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:"

  4239. msgstr ""

  4240. 

  4241. #: ../../../CHANGELOG.md:2291

  4242. 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."

  4243. msgstr ""

  4244. 

  4245. #: ../../../CHANGELOG.md:2292

  4246. 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`)."

  4247. msgstr ""

  4248. 

  4249. #: ../../../CHANGELOG.md:2294

  4250. msgid "How do I help?"

  4251. msgstr ""

  4252. 

  4253. #: ../../../CHANGELOG.md:2296

  4254. msgid "You can help by:"

  4255. msgstr ""

  4256. 

  4257. #: ../../../CHANGELOG.md:2298

  4258. 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"

  4259. msgstr ""

  4260. 

  4261. #: ../../../CHANGELOG.md:2300

  4262. 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)."

  4263. msgstr ""

  4264. 

  4265. #: ../../../CHANGELOG.md:2302

  4266. 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"

  4267. msgstr ""

  4268. 

  4269. #: ../../../CHANGELOG.md:2305

  4270. msgid "2023-02-10"

  4271. msgstr ""

  4272. 

  4273. #: ../../../CHANGELOG.md:2307

  4274. msgid "Matrix Authentication Support for Jitsi"

  4275. msgstr ""

  4276. 

  4277. #: ../../../CHANGELOG.md:2309

  4278. 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))."

  4279. msgstr ""

  4280. 

  4281. #: ../../../CHANGELOG.md:2311

  4282. 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)."

  4283. msgstr ""

  4284. 

  4285. #: ../../../CHANGELOG.md:2313

  4286. msgid "Draupnir moderation tool (bot) support"

  4287. msgstr ""

  4288. 

  4289. #: ../../../CHANGELOG.md:2315

  4290. 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."

  4291. msgstr ""

  4292. 

  4293. #: ../../../CHANGELOG.md:2317

  4294. msgid "Additional details are available in [Setting up Draupnir](docs/configuring-playbook-bot-draupnir.md)."

  4295. msgstr ""

  4296. 

  4297. #: ../../../CHANGELOG.md:2320

  4298. msgid "2023-02-05"

  4299. msgstr ""

  4300. 

  4301. #: ../../../CHANGELOG.md:2322

  4302. msgid "The matrix-prometheus-postgres-exporter role lives independently now"

  4303. msgstr ""

  4304. 

  4305. #: ../../../CHANGELOG.md:2324

  4306. msgid "**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  4307. msgstr ""

  4308. 

  4309. #: ../../../CHANGELOG.md:2326

  4310. 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"

  4311. msgstr ""

  4312. 

  4313. #: ../../../CHANGELOG.md:2328

  4314. 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."

  4315. msgstr ""

  4316. 

  4317. #: ../../../CHANGELOG.md:2330

  4318. 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`)"

  4319. msgstr ""

  4320. 

  4321. #: ../../../CHANGELOG.md:2332

  4322. #: ../../../CHANGELOG.md:2374

  4323. 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."

  4324. msgstr ""

  4325. 

  4326. #: ../../../CHANGELOG.md:2335

  4327. msgid "2023-01-26"

  4328. msgstr ""

  4329. 

  4330. #: ../../../CHANGELOG.md:2337

  4331. msgid "coturn can now use host-networking"

  4332. msgstr ""

  4333. 

  4334. #: ../../../CHANGELOG.md:2339

  4335. 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."

  4336. msgstr ""

  4337. 

  4338. #: ../../../CHANGELOG.md:2341

  4339. 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:"

  4340. msgstr ""

  4341. 

  4342. #: ../../../CHANGELOG.md:2347

  4343. 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."

  4344. msgstr ""

  4345. 

  4346. #: ../../../CHANGELOG.md:2349

  4347. 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."

  4348. msgstr ""

  4349. 

  4350. #: ../../../CHANGELOG.md:2351

  4351. msgid "(Backward Compatibility) Tightening coturn security can lead to connectivity issues"

  4352. msgstr ""

  4353. 

  4354. #: ../../../CHANGELOG.md:2353

  4355. 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."

  4356. msgstr ""

  4357. 

  4358. #: ../../../CHANGELOG.md:2355

  4359. 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."

  4360. msgstr ""

  4361. 

  4362. #: ../../../CHANGELOG.md:2357

  4363. 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."

  4364. msgstr ""

  4365. 

  4366. #: ../../../CHANGELOG.md:2359

  4367. 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."

  4368. msgstr ""

  4369. 

  4370. #: ../../../CHANGELOG.md:2362

  4371. msgid "2023-01-21"

  4372. msgstr ""

  4373. 

  4374. #: ../../../CHANGELOG.md:2364

  4375. msgid "The matrix-prometheus-node-exporter role lives independently now"

  4376. msgstr ""

  4377. 

  4378. #: ../../../CHANGELOG.md:2366

  4379. msgid "**TLDR**: the `matrix-prometheus-node-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  4380. msgstr ""

  4381. 

  4382. #: ../../../CHANGELOG.md:2368

  4383. 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"

  4384. msgstr ""

  4385. 

  4386. #: ../../../CHANGELOG.md:2370

  4387. 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."

  4388. msgstr ""

  4389. 

  4390. #: ../../../CHANGELOG.md:2372

  4391. 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`)"

  4392. msgstr ""

  4393. 

  4394. #: ../../../CHANGELOG.md:2377

  4395. msgid "2023-01-13"

  4396. msgstr ""

  4397. 

  4398. #: ../../../CHANGELOG.md:2379

  4399. msgid "Support for running commands via just"

  4400. msgstr ""

  4401. 

  4402. #: ../../../CHANGELOG.md:2381

  4403. 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."

  4404. msgstr ""

  4405. 

  4406. #: ../../../CHANGELOG.md:2383

  4407. 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."

  4408. msgstr ""

  4409. 

  4410. #: ../../../CHANGELOG.md:2385

  4411. msgid "Our [justfile](justfile) already defines some additional helpful **shortcut** commands that weren't part of our `Makefile`. Here are some examples:"

  4412. msgstr ""

  4413. 

  4414. #: ../../../CHANGELOG.md:2387

  4415. 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"

  4416. msgstr ""

  4417. 

  4418. #: ../../../CHANGELOG.md:2388

  4419. msgid "`just install-all --ask-vault-pass` — commands also support additional arguments (`--ask-vault-pass` will be appended to the above installation command)"

  4420. msgstr ""

  4421. 

  4422. #: ../../../CHANGELOG.md:2389

  4423. msgid "`just run-tags install-mautrix-slack,start` — to run specific playbook tags"

  4424. msgstr ""

  4425. 

  4426. #: ../../../CHANGELOG.md:2390

  4427. msgid "`just start-all` — (re-)starts all services"

  4428. msgstr ""

  4429. 

  4430. #: ../../../CHANGELOG.md:2391

  4431. msgid "`just stop-group postgres` — to stop only the Postgres service"

  4432. msgstr ""

  4433. 

  4434. #: ../../../CHANGELOG.md:2392

  4435. msgid "`just register-user alice secret-password yes` — registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)"

  4436. msgstr ""

  4437. 

  4438. #: ../../../CHANGELOG.md:2394

  4439. msgid "Additional helpful commands and shortcuts may be defined in the future."

  4440. msgstr ""

  4441. 

  4442. #: ../../../CHANGELOG.md:2396

  4443. 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."

  4444. msgstr ""

  4445. 

  4446. #: ../../../CHANGELOG.md:2399

  4447. msgid "2023-01-11"

  4448. msgstr ""

  4449. 

  4450. #: ../../../CHANGELOG.md:2401

  4451. msgid "mautrix-slack support"

  4452. msgstr ""

  4453. 

  4454. #: ../../../CHANGELOG.md:2403

  4455. 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."

  4456. msgstr ""

  4457. 

  4458. #: ../../../CHANGELOG.md:2405

  4459. 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)."

  4460. msgstr ""

  4461. 

  4462. #: ../../../CHANGELOG.md:2408

  4463. msgid "2023-01-10"

  4464. msgstr ""

  4465. 

  4466. #: ../../../CHANGELOG.md:2410

  4467. msgid "ChatGPT support"

  4468. msgstr ""

  4469. 

  4470. #: ../../../CHANGELOG.md:2412

  4471. 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."

  4472. msgstr ""

  4473. 

  4474. #: ../../../CHANGELOG.md:2414

  4475. msgid "See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-chatgpt.md) documentation to get started."

  4476. msgstr ""

  4477. 

  4478. #: ../../../CHANGELOG.md:2417

  4479. msgid "2022-11-30"

  4480. msgstr ""

  4481. 

  4482. #: ../../../CHANGELOG.md:2419

  4483. msgid "matrix-postgres-backup has been replaced by the ansible-role-postgres-backup external role"

  4484. msgstr ""

  4485. 

  4486. #: ../../../CHANGELOG.md:2421

  4487. 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)."

  4488. msgstr ""

  4489. 

  4490. #: ../../../CHANGELOG.md:2423

  4491. msgid "You'll need to rename your `matrix_postgres_backup`-prefixed variables such that they use a `postgres_backup` prefix."

  4492. msgstr ""

  4493. 

  4494. #: ../../../CHANGELOG.md:2426

  4495. msgid "2022-11-28"

  4496. msgstr ""

  4497. 

  4498. #: ../../../CHANGELOG.md:2428

  4499. msgid "matrix-postgres has been replaced by the ansible-role-postgres external role"

  4500. msgstr ""

  4501. 

  4502. #: ../../../CHANGELOG.md:2430

  4503. 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`)."

  4504. msgstr ""

  4505. 

  4506. #: ../../../CHANGELOG.md:2432

  4507. 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."

  4508. msgstr ""

  4509. 

  4510. #: ../../../CHANGELOG.md:2434

  4511. msgid "The new role is an upgraded version of the old `matrix-postgres` role with these notable differences:"

  4512. msgstr ""

  4513. 

  4514. #: ../../../CHANGELOG.md:2436

  4515. msgid "it uses different names for its variables (`matrix_postgres` -> `devture_postgres`)"

  4516. msgstr ""

  4517. 

  4518. #: ../../../CHANGELOG.md:2437

  4519. msgid "when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-postgresql), it will vacuum all your databases, not just the Synapse one"

  4520. msgstr ""

  4521. 

  4522. #: ../../../CHANGELOG.md:2439

  4523. 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."

  4524. msgstr ""

  4525. 

  4526. #: ../../../CHANGELOG.md:2441

  4527. 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)."

  4528. msgstr ""

  4529. 

  4530. #: ../../../CHANGELOG.md:2443

  4531. msgid "The playbook no longer installs scripts to /usr/local/bin"

  4532. msgstr ""

  4533. 

  4534. #: ../../../CHANGELOG.md:2445

  4535. msgid "The locations of various scripts installed by the playbook have changed."

  4536. msgstr ""

  4537. 

  4538. #: ../../../CHANGELOG.md:2447

  4539. 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:"

  4540. msgstr ""

  4541. 

  4542. #: ../../../CHANGELOG.md:2449

  4543. msgid "`/usr/local/bin/matrix-remove-all` -> `/matrix/bin/remove-all`"

  4544. msgstr ""

  4545. 

  4546. #: ../../../CHANGELOG.md:2450

  4547. msgid "`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`"

  4548. msgstr ""

  4549. 

  4550. #: ../../../CHANGELOG.md:2451

  4551. msgid "`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> `/matrix/ssl/bin/lets-encrypt-certificates-renew`"

  4552. msgstr ""

  4553. 

  4554. #: ../../../CHANGELOG.md:2452

  4555. msgid "`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin/register-user`"

  4556. msgstr ""

  4557. 

  4558. #: ../../../CHANGELOG.md:2455

  4559. msgid "2022-11-25"

  4560. msgstr ""

  4561. 

  4562. #: ../../../CHANGELOG.md:2457

  4563. msgid "2x-5x performance improvements in playbook runtime"

  4564. msgstr ""

  4565. 

  4566. #: ../../../CHANGELOG.md:2459

  4567. 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."

  4568. msgstr ""

  4569. 

  4570. #: ../../../CHANGELOG.md:2461

  4571. 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."

  4572. msgstr ""

  4573. 

  4574. #: ../../../CHANGELOG.md:2463

  4575. msgid "Even when running `ansible-playbook` manually (as most of us here do), it's beneficial not to waste time and CPU resources."

  4576. msgstr ""

  4577. 

  4578. #: ../../../CHANGELOG.md:2465

  4579. 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`):"

  4580. msgstr ""

  4581. 

  4582. #: ../../../CHANGELOG.md:2467

  4583. 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**."

  4584. msgstr ""

  4585. 

  4586. #: ../../../CHANGELOG.md:2469

  4587. 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`)**."

  4588. msgstr ""

  4589. 

  4590. #: ../../../CHANGELOG.md:2471

  4591. 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."

  4592. msgstr ""

  4593. 

  4594. #: ../../../CHANGELOG.md:2473

  4595. 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`."

  4596. msgstr ""

  4597. 

  4598. #: ../../../CHANGELOG.md:2476

  4599. msgid "2022-11-22"

  4600. msgstr ""

  4601. 

  4602. #: ../../../CHANGELOG.md:2478

  4603. msgid "Automatic `matrix_architecture` determination"

  4604. msgstr ""

  4605. 

  4606. #: ../../../CHANGELOG.md:2480

  4607. 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."

  4608. msgstr ""

  4609. 

  4610. #: ../../../CHANGELOG.md:2482

  4611. msgid "Docker and the Docker SDK for Python are now installed via external roles"

  4612. msgstr ""

  4613. 

  4614. #: ../../../CHANGELOG.md:2486

  4615. 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`."

  4616. msgstr ""

  4617. 

  4618. #: ../../../CHANGELOG.md:2488

  4619. 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`."

  4620. msgstr ""

  4621. 

  4622. #: ../../../CHANGELOG.md:2490

  4623. msgid "If you're hitting issues with Docker installation or Docker SDK for Python installation, consider reporting bugs or contributing to these other projects."

  4624. msgstr ""

  4625. 

  4626. #: ../../../CHANGELOG.md:2492

  4627. 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."

  4628. msgstr ""

  4629. 

  4630. #: ../../../CHANGELOG.md:2495

  4631. msgid "2022-11-20"

  4632. msgstr ""

  4633. 

  4634. #: ../../../CHANGELOG.md:2497

  4635. msgid "(Backward Compatibility Break) Changing how reverse-proxying to Synapse works — now via a `matrix-synapse-reverse-proxy-companion` service"

  4636. msgstr ""

  4637. 

  4638. #: ../../../CHANGELOG.md:2499

  4639. 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."

  4640. msgstr ""

  4641. 

  4642. #: ../../../CHANGELOG.md:2501

  4643. msgid "Background"

  4644. msgstr ""

  4645. 

  4646. #: ../../../CHANGELOG.md:2503

  4647. 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)."

  4648. msgstr ""

  4649. 

  4650. #: ../../../CHANGELOG.md:2505

  4651. 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)."

  4652. msgstr ""

  4653. 

  4654. #: ../../../CHANGELOG.md:2507

  4655. msgid "Solution"

  4656. msgstr ""

  4657. 

  4658. #: ../../../CHANGELOG.md:2509

  4659. 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:"

  4660. msgstr ""

  4661. 

  4662. #: ../../../CHANGELOG.md:2511

  4663. msgid "serve as a companion to Synapse and know how to reverse-proxy to Synapse correctly (no matter if workers are enabled or not)"

  4664. msgstr ""

  4665. 

  4666. #: ../../../CHANGELOG.md:2513

  4667. msgid "provide a unified container address for reaching Synapse (no matter if workers are enabled or not)"

  4668. msgstr ""

  4669. 

  4670. #: ../../../CHANGELOG.md:2514

  4671. msgid "`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server API traffic"

  4672. msgstr ""

  4673. 

  4674. #: ../../../CHANGELOG.md:2515

  4675. msgid "`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server (Federation) API traffic"

  4676. msgstr ""

  4677. 

  4678. #: ../../../CHANGELOG.md:2517

  4679. 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"

  4680. msgstr ""

  4681. 

  4682. #: ../../../CHANGELOG.md:2519

  4683. msgid "allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is disabled"

  4684. msgstr ""

  4685. 

  4686. #: ../../../CHANGELOG.md:2521

  4687. 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:"

  4688. msgstr ""

  4689. 

  4690. #: ../../../CHANGELOG.md:2523

  4691. msgid "(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> (`matrix-synapse` or some Synapse worker))."

  4692. msgstr ""

  4693. 

  4694. #: ../../../CHANGELOG.md:2525

  4695. 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."

  4696. msgstr ""

  4697. 

  4698. #: ../../../CHANGELOG.md:2527

  4699. msgid "Webserver configuration"

  4700. msgstr ""

  4701. 

  4702. #: ../../../CHANGELOG.md:2529

  4703. 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"

  4704. msgstr ""

  4705. 

  4706. #: ../../../CHANGELOG.md:2531

  4707. 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"

  4708. msgstr ""

  4709. 

  4710. #: ../../../CHANGELOG.md:2533

  4711. 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"

  4712. msgstr ""

  4713. 

  4714. #: ../../../CHANGELOG.md:2535

  4715. 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"

  4716. msgstr ""

  4717. 

  4718. #: ../../../CHANGELOG.md:2537

  4719. 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."

  4720. msgstr ""

  4721. 

  4722. #: ../../../CHANGELOG.md:2540

  4723. msgid "2022-11-05"

  4724. msgstr ""

  4725. 

  4726. #: ../../../CHANGELOG.md:2542

  4727. msgid "(Backward Compatibility Break) A new default standalone mode for Etherpad"

  4728. msgstr ""

  4729. 

  4730. #: ../../../CHANGELOG.md:2544

  4731. 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`)."

  4732. msgstr ""

  4733. 

  4734. #: ../../../CHANGELOG.md:2546

  4735. 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`)."

  4736. msgstr ""

  4737. 

  4738. #: ../../../CHANGELOG.md:2548

  4739. msgid "If you've already got both Etherpad and Dimension in use you could:"

  4740. msgstr ""

  4741. 

  4742. #: ../../../CHANGELOG.md:2550

  4743. 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."

  4744. msgstr ""

  4745. 

  4746. #: ../../../CHANGELOG.md:2552

  4747. 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"

  4748. msgstr ""

  4749. 

  4750. #: ../../../CHANGELOG.md:2555

  4751. msgid "2022-11-04"

  4752. msgstr ""

  4753. 

  4754. #: ../../../CHANGELOG.md:2557

  4755. msgid "The playbook now uses external roles for some things"

  4756. msgstr ""

  4757. 

  4758. #: ../../../CHANGELOG.md:2559

  4759. 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."

  4760. msgstr ""

  4761. 

  4762. #: ../../../CHANGELOG.md:2561

  4763. msgid "We're in the process of trimming the playbook and making it reuse Ansible roles."

  4764. msgstr ""

  4765. 

  4766. #: ../../../CHANGELOG.md:2563

  4767. msgid "Starting now, the playbook is composed of 2 types of Ansible roles:"

  4768. msgstr ""

  4769. 

  4770. #: ../../../CHANGELOG.md:2565

  4771. msgid "those that live within the playbook itself (`roles/custom/*`)"

  4772. msgstr ""

  4773. 

  4774. #: ../../../CHANGELOG.md:2567

  4775. 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."

  4776. msgstr ""

  4777. 

  4778. #: ../../../CHANGELOG.md:2569

  4779. 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."

  4780. msgstr ""

  4781. 

  4782. #: ../../../CHANGELOG.md:2571

  4783. 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."

  4784. msgstr ""

  4785. 

  4786. #: ../../../CHANGELOG.md:2573

  4787. 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`."

  4788. msgstr ""

  4789. 

  4790. #: ../../../CHANGELOG.md:2576

  4791. msgid "2022-10-14"

  4792. msgstr ""

  4793. 

  4794. #: ../../../CHANGELOG.md:2578

  4795. msgid "synapse-s3-storage-provider support"

  4796. msgstr ""

  4797. 

  4798. #: ../../../CHANGELOG.md:2580

  4799. msgid "**`synapse-s3-storage-provider` support is very new and still relatively untested. Using it may cause data loss.**"

  4800. msgstr ""

  4801. 

  4802. #: ../../../CHANGELOG.md:2582

  4803. 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)."

  4804. msgstr ""

  4805. 

  4806. #: ../../../CHANGELOG.md:2584

  4807. 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`."

  4808. msgstr ""

  4809. 

  4810. #: ../../../CHANGELOG.md:2586

  4811. 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."

  4812. msgstr ""

  4813. 

  4814. #: ../../../CHANGELOG.md:2588

  4815. msgid "Synapse container image customization support"

  4816. msgstr ""

  4817. 

  4818. #: ../../../CHANGELOG.md:2590

  4819. msgid "We now support customizing the Synapse container image by adding additional build steps to its [`Dockerfile`](https://docs.docker.com/engine/reference/builder/)."

  4820. msgstr ""

  4821. 

  4822. #: ../../../CHANGELOG.md:2592

  4823. 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."

  4824. msgstr ""

  4825. 

  4826. #: ../../../CHANGELOG.md:2594

  4827. 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:"

  4828. msgstr ""

  4829. 

  4830. #: ../../../CHANGELOG.md:2605

  4831. 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."

  4832. msgstr ""

  4833. 

  4834. #: ../../../CHANGELOG.md:2607

  4835. 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."

  4836. msgstr ""

  4837. 

  4838. #: ../../../CHANGELOG.md:2610

  4839. msgid "2022-10-02"

  4840. msgstr ""

  4841. 

  4842. #: ../../../CHANGELOG.md:2612

  4843. msgid "matrix-ldap-registration-proxy support"

  4844. msgstr ""

  4845. 

  4846. #: ../../../CHANGELOG.md:2614

  4847. 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."

  4848. msgstr ""

  4849. 

  4850. #: ../../../CHANGELOG.md:2616

  4851. msgid "See our [Setting up matrix-ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started."

  4852. msgstr ""

  4853. 

  4854. #: ../../../CHANGELOG.md:2619

  4855. msgid "2022-09-15"

  4856. msgstr ""

  4857. 

  4858. #: ../../../CHANGELOG.md:2621

  4859. msgid "(Potential Backward Compatibility Break) Major improvements to Synapse workers"

  4860. msgstr ""

  4861. 

  4862. #: ../../../CHANGELOG.md:2623

  4863. msgid "People who are interested in running a Synapse worker setup should know that **our Synapse worker implementation is much more powerful now**:"

  4864. msgstr ""

  4865. 

  4866. #: ../../../CHANGELOG.md:2625

  4867. msgid "we've added support for [Stream writers](#stream-writers-support)"

  4868. msgstr ""

  4869. 

  4870. #: ../../../CHANGELOG.md:2626

  4871. msgid "we've added support for [multiple federation sender workers](#multiple-federation-sender-workers-support)"

  4872. msgstr ""

  4873. 

  4874. #: ../../../CHANGELOG.md:2627

  4875. msgid "we've added support for [multiple pusher workers](#multiple-pusher-workers-support)"

  4876. msgstr ""

  4877. 

  4878. #: ../../../CHANGELOG.md:2628

  4879. msgid "we've added support for [running background tasks on a worker](#background-tasks-can-run-on-a-worker)"

  4880. msgstr ""

  4881. 

  4882. #: ../../../CHANGELOG.md:2629

  4883. msgid "we've restored support for [`appservice` workers](#appservice-worker-support-is-back)"

  4884. msgstr ""

  4885. 

  4886. #: ../../../CHANGELOG.md:2630

  4887. msgid "we've restored support for [`user_dir` workers](#user-directory-worker-support-is-back)"

  4888. msgstr ""

  4889. 

  4890. #: ../../../CHANGELOG.md:2631

  4891. 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)"

  4892. msgstr ""

  4893. 

  4894. #: ../../../CHANGELOG.md:2632

  4895. msgid "see the [Potential Backward Incompatibilities after these Synapse worker changes](#potential-backward-incompatibilities-after-these-synapse-worker-changes)"

  4896. msgstr ""

  4897. 

  4898. #: ../../../CHANGELOG.md:2634

  4899. msgid "Stream writers support"

  4900. msgstr ""

  4901. 

  4902. #: ../../../CHANGELOG.md:2636

  4903. 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."

  4904. msgstr ""

  4905. 

  4906. #: ../../../CHANGELOG.md:2638

  4907. 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."

  4908. msgstr ""

  4909. 

  4910. #: ../../../CHANGELOG.md:2640

  4911. msgid "If you'd like to customize the number of workers we also make that possible using these variables:"

  4912. msgstr ""

  4913. 

  4914. #: ../../../CHANGELOG.md:2653

  4915. msgid "Multiple federation sender workers support"

  4916. msgstr ""

  4917. 

  4918. #: ../../../CHANGELOG.md:2655

  4919. 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."

  4920. msgstr ""

  4921. 

  4922. #: ../../../CHANGELOG.md:2657

  4923. msgid "Multiple pusher workers support"

  4924. msgstr ""

  4925. 

  4926. #: ../../../CHANGELOG.md:2659

  4927. 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."

  4928. msgstr ""

  4929. 

  4930. #: ../../../CHANGELOG.md:2661

  4931. msgid "Background tasks can run on a worker"

  4932. msgstr ""

  4933. 

  4934. #: ../../../CHANGELOG.md:2663

  4935. msgid "From now on, you can put [background task processing on a worker](https://matrix-org.github.io/synapse/latest/workers.html#background-tasks)."

  4936. msgstr ""

  4937. 

  4938. #: ../../../CHANGELOG.md:2665

  4939. 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."

  4940. msgstr ""

  4941. 

  4942. #: ../../../CHANGELOG.md:2667

  4943. msgid "Appservice worker support is back"

  4944. msgstr ""

  4945. 

  4946. #: ../../../CHANGELOG.md:2669

  4947. 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."

  4948. msgstr ""

  4949. 

  4950. #: ../../../CHANGELOG.md:2671

  4951. 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."

  4952. msgstr ""

  4953. 

  4954. #: ../../../CHANGELOG.md:2673

  4955. 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."

  4956. msgstr ""

  4957. 

  4958. #: ../../../CHANGELOG.md:2675

  4959. msgid "User Directory worker support is back"

  4960. msgstr ""

  4961. 

  4962. #: ../../../CHANGELOG.md:2677

  4963. 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."

  4964. msgstr ""

  4965. 

  4966. #: ../../../CHANGELOG.md:2679

  4967. 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."

  4968. msgstr ""

  4969. 

  4970. #: ../../../CHANGELOG.md:2681

  4971. 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."

  4972. msgstr ""

  4973. 

  4974. #: ../../../CHANGELOG.md:2683

  4975. msgid "Using more than 1 media repository worker is now more reliable"

  4976. msgstr ""

  4977. 

  4978. #: ../../../CHANGELOG.md:2685

  4979. msgid "With `matrix_synapse_workers_preset: one-of-each`, we only launch one `media_repository` worker."

  4980. msgstr ""

  4981. 

  4982. #: ../../../CHANGELOG.md:2687

  4983. 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."

  4984. msgstr ""

  4985. 

  4986. #: ../../../CHANGELOG.md:2689

  4987. msgid "Potential Backward Incompatibilities after these Synapse worker changes"

  4988. msgstr ""

  4989. 

  4990. #: ../../../CHANGELOG.md:2691

  4991. msgid "Below we'll discuss **potential backward incompatibilities**."

  4992. msgstr ""

  4993. 

  4994. #: ../../../CHANGELOG.md:2693

  4995. 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."

  4996. msgstr ""

  4997. 

  4998. #: ../../../CHANGELOG.md:2695

  4999. 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."

  5000. msgstr ""

  5001. 

  5002. #: ../../../CHANGELOG.md:2697

  5003. 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."

  5004. msgstr ""

  5005. 

  5006. #: ../../../CHANGELOG.md:2699

  5007. 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."

  5008. msgstr ""

  5009. 

  5010. #: ../../../CHANGELOG.md:2702

  5011. msgid "2022-09-09"

  5012. msgstr ""

  5013. 

  5014. #: ../../../CHANGELOG.md:2704

  5015. msgid "Cactus Comments support"

  5016. msgstr ""

  5017. 

  5018. #: ../../../CHANGELOG.md:2706

  5019. 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."

  5020. msgstr ""

  5021. 

  5022. #: ../../../CHANGELOG.md:2708

  5023. msgid "See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-comments.md) documentation to get started."

  5024. msgstr ""

  5025. 

  5026. #: ../../../CHANGELOG.md:2711

  5027. msgid "2022-08-23"

  5028. msgstr ""

  5029. 

  5030. #: ../../../CHANGELOG.md:2713

  5031. msgid "Postmoogle email bridge support"

  5032. msgstr ""

  5033. 

  5034. #: ../../../CHANGELOG.md:2715

  5035. 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."

  5036. msgstr ""

  5037. 

  5038. #: ../../../CHANGELOG.md:2717

  5039. msgid "See our [Setting up Postmoogle email bridging](docs/configuring-playbook-bridge-postmoogle.md) documentation to get started."

  5040. msgstr ""

  5041. 

  5042. #: ../../../CHANGELOG.md:2720

  5043. msgid "2022-08-10"

  5044. msgstr ""

  5045. 

  5046. #: ../../../CHANGELOG.md:2722

  5047. msgid "mautrix-whatsapp default configuration changes"

  5048. msgstr ""

  5049. 

  5050. #: ../../../CHANGELOG.md:2724

  5051. 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."

  5052. msgstr ""

  5053. 

  5054. #: ../../../CHANGELOG.md:2726

  5055. 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."

  5056. msgstr ""

  5057. 

  5058. #: ../../../CHANGELOG.md:2728

  5059. 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."

  5060. msgstr ""

  5061. 

  5062. #: ../../../CHANGELOG.md:2731

  5063. msgid "2022-08-09"

  5064. msgstr ""

  5065. 

  5066. #: ../../../CHANGELOG.md:2733

  5067. msgid "Conduit support"

  5068. msgstr ""

  5069. 

  5070. #: ../../../CHANGELOG.md:2735

  5071. 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."

  5072. msgstr ""

  5073. 

  5074. #: ../../../CHANGELOG.md:2737

  5075. msgid "Existing Synapse or Dendrite installations do **not** need to be updated. **Synapse is still the default homeserver implementation** installed by the playbook."

  5076. msgstr ""

  5077. 

  5078. #: ../../../CHANGELOG.md:2739

  5079. msgid "To try out Conduit, we recommend that you **use a new server** and the following `vars.yml` configuration:"

  5080. msgstr ""

  5081. 

  5082. #: ../../../CHANGELOG.md:2745

  5083. msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse or Dendrite to Conduit) without data loss."

  5084. msgstr ""

  5085. 

  5086. #: ../../../CHANGELOG.md:2748

  5087. msgid "2022-07-29"

  5088. msgstr ""

  5089. 

  5090. #: ../../../CHANGELOG.md:2750

  5091. msgid "mautrix-discord support"

  5092. msgstr ""

  5093. 

  5094. #: ../../../CHANGELOG.md:2752

  5095. 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."

  5096. msgstr ""

  5097. 

  5098. #: ../../../CHANGELOG.md:2754

  5099. 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)."

  5100. msgstr ""

  5101. 

  5102. #: ../../../CHANGELOG.md:2757

  5103. msgid "2022-07-27"

  5104. msgstr ""

  5105. 

  5106. #: ../../../CHANGELOG.md:2759

  5107. msgid "matrix-appservice-kakaotalk support"

  5108. msgstr ""

  5109. 

  5110. #: ../../../CHANGELOG.md:2761

  5111. 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!"

  5112. msgstr ""

  5113. 

  5114. #: ../../../CHANGELOG.md:2763

  5115. msgid "See our [Setting up Appservice Kakaotalk bridging](docs/configuring-playbook-bridge-appservice-kakaotalk.md) documentation to get started."

  5116. msgstr ""

  5117. 

  5118. #: ../../../CHANGELOG.md:2766

  5119. msgid "2022-07-20"

  5120. msgstr ""

  5121. 

  5122. #: ../../../CHANGELOG.md:2768

  5123. msgid "maubot support"

  5124. msgstr ""

  5125. 

  5126. #: ../../../CHANGELOG.md:2770

  5127. 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."

  5128. msgstr ""

  5129. 

  5130. #: ../../../CHANGELOG.md:2772

  5131. msgid "See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) documentation to get started."

  5132. msgstr ""

  5133. 

  5134. #: ../../../CHANGELOG.md:2775

  5135. msgid "2022-07-14"

  5136. msgstr ""

  5137. 

  5138. #: ../../../CHANGELOG.md:2777

  5139. msgid "mx-puppet-skype removal"

  5140. msgstr ""

  5141. 

  5142. #: ../../../CHANGELOG.md:2779

  5143. 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."

  5144. msgstr ""

  5145. 

  5146. #: ../../../CHANGELOG.md:2781

  5147. msgid "To completely clean up your server from `mx-puppet-skype`'s presence on it:"

  5148. msgstr ""

  5149. 

  5150. #: ../../../CHANGELOG.md:2783

  5151. msgid "ensure your Ansible configuration (`vars.yml` file) no longer contains `matrix_mx_puppet_skype_*` references"

  5152. msgstr ""

  5153. 

  5154. #: ../../../CHANGELOG.md:2784

  5155. msgid "stop and disable the systemd service (run `systemctl disable --now matrix-mx-puppet-skype` on the server)"

  5156. msgstr ""

  5157. 

  5158. #: ../../../CHANGELOG.md:2785

  5159. msgid "delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-skype.service` on the server)"

  5160. msgstr ""

  5161. 

  5162. #: ../../../CHANGELOG.md:2786

  5163. msgid "delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on the server)"

  5164. msgstr ""

  5165. 

  5166. #: ../../../CHANGELOG.md:2787

  5167. 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)"

  5168. msgstr ""

  5169. 

  5170. #: ../../../CHANGELOG.md:2789

  5171. 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)."

  5172. msgstr ""

  5173. 

  5174. #: ../../../CHANGELOG.md:2791

  5175. 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."

  5176. msgstr ""

  5177. 

  5178. #: ../../../CHANGELOG.md:2793

  5179. msgid "signald (0.19.0+) upgrade requires data migration"

  5180. msgstr ""

  5181. 

  5182. #: ../../../CHANGELOG.md:2795

  5183. 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`."

  5184. msgstr ""

  5185. 

  5186. #: ../../../CHANGELOG.md:2797

  5187. 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)."

  5188. msgstr ""

  5189. 

  5190. #: ../../../CHANGELOG.md:2799

  5191. 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."

  5192. msgstr ""

  5193. 

  5194. #: ../../../CHANGELOG.md:2801

  5195. msgid "We attempt to do this data migration automatically every time Signald starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` systemd unit definition."

  5196. msgstr ""

  5197. 

  5198. #: ../../../CHANGELOG.md:2803

  5199. 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!"

  5200. msgstr ""

  5201. 

  5202. #: ../../../CHANGELOG.md:2806

  5203. msgid "2022-07-05"

  5204. msgstr ""

  5205. 

  5206. #: ../../../CHANGELOG.md:2808

  5207. msgid "Ntfy push notifications support"

  5208. msgstr ""

  5209. 

  5210. #: ../../../CHANGELOG.md:2810

  5211. 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."

  5212. msgstr ""

  5213. 

  5214. #: ../../../CHANGELOG.md:2812

  5215. msgid "See our [Setting up the ntfy push notifications server](docs/configuring-playbook-ntfy.md) documentation to get started."

  5216. msgstr ""

  5217. 

  5218. #: ../../../CHANGELOG.md:2815

  5219. msgid "2022-06-23"

  5220. msgstr ""

  5221. 

  5222. #: ../../../CHANGELOG.md:2817

  5223. msgid "(Potential Backward Compatibility Break) Changes around metrics collection"

  5224. msgstr ""

  5225. 

  5226. #: ../../../CHANGELOG.md:2819

  5227. 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."

  5228. msgstr ""

  5229. 

  5230. #: ../../../CHANGELOG.md:2821

  5231. 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)."

  5232. msgstr ""

  5233. 

  5234. #: ../../../CHANGELOG.md:2823

  5235. 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`."

  5236. msgstr ""

  5237. 

  5238. #: ../../../CHANGELOG.md:2825

  5239. msgid "**If you are using the [Hookshot bridge](docs/configuring-playbook-bridge-hookshot.md)**, you may find that:"

  5240. msgstr ""

  5241. 

  5242. #: ../../../CHANGELOG.md:2826

  5243. msgid "**Metrics may not be enabled by default anymore**:"

  5244. msgstr ""

  5245. 

  5246. #: ../../../CHANGELOG.md:2827

  5247. 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."

  5248. msgstr ""

  5249. 

  5250. #: ../../../CHANGELOG.md:2828

  5251. 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."

  5252. msgstr ""

  5253. 

  5254. #: ../../../CHANGELOG.md:2829

  5255. 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."

  5256. msgstr ""

  5257. 

  5258. #: ../../../CHANGELOG.md:2830

  5259. 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`."

  5260. msgstr ""

  5261. 

  5262. #: ../../../CHANGELOG.md:2832

  5263. 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`."

  5264. msgstr ""

  5265. 

  5266. #: ../../../CHANGELOG.md:2834

  5267. 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`."

  5268. msgstr ""

  5269. 

  5270. #: ../../../CHANGELOG.md:2836

  5271. msgid "**If you're using Synapse** and would like to collect its metrics from an external Prometheus server, you may find that:"

  5272. msgstr ""

  5273. 

  5274. #: ../../../CHANGELOG.md:2838

  5275. 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."

  5276. msgstr ""

  5277. 

  5278. #: ../../../CHANGELOG.md:2839

  5279. 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"

  5280. msgstr ""

  5281. 

  5282. #: ../../../CHANGELOG.md:2840

  5283. 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`"

  5284. msgstr ""

  5285. 

  5286. #: ../../../CHANGELOG.md:2841

  5287. 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`)."

  5288. msgstr ""

  5289. 

  5290. #: ../../../CHANGELOG.md:2843

  5291. 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."

  5292. msgstr ""

  5293. 

  5294. #: ../../../CHANGELOG.md:2845

  5295. msgid "2022-06-13"

  5296. msgstr ""

  5297. 

  5298. #: ../../../CHANGELOG.md:2847

  5299. msgid "go-skype-bridge bridging support"

  5300. msgstr ""

  5301. 

  5302. #: ../../../CHANGELOG.md:2849

  5303. 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/)."

  5304. msgstr ""

  5305. 

  5306. #: ../../../CHANGELOG.md:2851

  5307. msgid "See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md) documentation to get started."

  5308. msgstr ""

  5309. 

  5310. #: ../../../CHANGELOG.md:2853

  5311. 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."

  5312. msgstr ""

  5313. 

  5314. #: ../../../CHANGELOG.md:2856

  5315. msgid "2022-06-09"

  5316. msgstr ""

  5317. 

  5318. #: ../../../CHANGELOG.md:2858

  5319. msgid "Running Ansible in a container can now happen on the Matrix server itself"

  5320. msgstr ""

  5321. 

  5322. #: ../../../CHANGELOG.md:2860

  5323. 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)."

  5324. msgstr ""

  5325. 

  5326. #: ../../../CHANGELOG.md:2863

  5327. msgid "2022-05-31"

  5328. msgstr ""

  5329. 

  5330. #: ../../../CHANGELOG.md:2865

  5331. msgid "Synapse v1.60 upgrade may cause trouble and require manual intervention"

  5332. msgstr ""

  5333. 

  5334. #: ../../../CHANGELOG.md:2867

  5335. 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."

  5336. msgstr ""

  5337. 

  5338. #: ../../../CHANGELOG.md:2869

  5339. 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."

  5340. msgstr ""

  5341. 

  5342. #: ../../../CHANGELOG.md:2871

  5343. msgid "**If Synapse fails to start** after your next playbook run, you'll need to:"

  5344. msgstr ""

  5345. 

  5346. #: ../../../CHANGELOG.md:2873

  5347. msgid "SSH into the Matrix server"

  5348. msgstr ""

  5349. 

  5350. #: ../../../CHANGELOG.md:2874

  5351. msgid "launch `/usr/local/bin/matrix-postgres-cli`"

  5352. msgstr ""

  5353. 

  5354. #: ../../../CHANGELOG.md:2875

  5355. msgid "switch to the `synapse` database: `\\c synapse`"

  5356. msgstr ""

  5357. 

  5358. #: ../../../CHANGELOG.md:2876

  5359. msgid "run the following SQL query:"

  5360. msgstr ""

  5361. 

  5362. #: ../../../CHANGELOG.md:2895

  5363. msgid "You could then restart services: `ansible-playbook -i inventory/hosts setup.yml --tags=start`"

  5364. msgstr ""

  5365. 

  5366. #: ../../../CHANGELOG.md:2898

  5367. msgid "2022-04-25"

  5368. msgstr ""

  5369. 

  5370. #: ../../../CHANGELOG.md:2900

  5371. msgid "Buscarron bot support"

  5372. msgstr ""

  5373. 

  5374. #: ../../../CHANGELOG.md:2902

  5375. 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"

  5376. msgstr ""

  5377. 

  5378. #: ../../../CHANGELOG.md:2904

  5379. msgid "See our [Setting up Buscarron](docs/configuring-playbook-bot-buscarron.md) documentation to get started."

  5380. msgstr ""

  5381. 

  5382. #: ../../../CHANGELOG.md:2907

  5383. msgid "2022-04-21"

  5384. msgstr ""

  5385. 

  5386. #: ../../../CHANGELOG.md:2909

  5387. msgid "matrix-registration-bot support"

  5388. msgstr ""

  5389. 

  5390. #: ../../../CHANGELOG.md:2911

  5391. 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."

  5392. msgstr ""

  5393. 

  5394. #: ../../../CHANGELOG.md:2913

  5395. msgid "See our [Setting up matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) documentation to get started."

  5396. msgstr ""

  5397. 

  5398. #: ../../../CHANGELOG.md:2916

  5399. msgid "2022-04-19"

  5400. msgstr ""

  5401. 

  5402. #: ../../../CHANGELOG.md:2918

  5403. msgid "BorgBackup support"

  5404. msgstr ""

  5405. 

  5406. #: ../../../CHANGELOG.md:2920

  5407. 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."

  5408. msgstr ""

  5409. 

  5410. #: ../../../CHANGELOG.md:2922

  5411. msgid "See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md) documentation to get started."

  5412. msgstr ""

  5413. 

  5414. #: ../../../CHANGELOG.md:2924

  5415. msgid "(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action"

  5416. msgstr ""

  5417. 

  5418. #: ../../../CHANGELOG.md:2926

  5419. 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:"

  5420. msgstr ""

  5421. 

  5422. #: ../../../CHANGELOG.md:2928

  5423. 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."

  5424. msgstr ""

  5425. 

  5426. #: ../../../CHANGELOG.md:2930

  5427. 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."

  5428. msgstr ""

  5429. 

  5430. #: ../../../CHANGELOG.md:2932

  5431. 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:"

  5432. msgstr ""

  5433. 

  5434. #: ../../../CHANGELOG.md:2934

  5435. msgid "Pull the latest playbook changes"

  5436. msgstr ""

  5437. 

  5438. #: ../../../CHANGELOG.md:2935

  5439. msgid "Stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"

  5440. msgstr ""

  5441. 

  5442. #: ../../../CHANGELOG.md:2936

  5443. msgid "Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all`)"

  5444. msgstr ""

  5445. 

  5446. #: ../../../CHANGELOG.md:2937

  5447. msgid "Start Postgres (`systemctl start matrix-postgres` on the server)"

  5448. msgstr ""

  5449. 

  5450. #: ../../../CHANGELOG.md:2938

  5451. msgid "Start the main Synapse process (`systemctl start matrix-synapse` on the server)"

  5452. msgstr ""

  5453. 

  5454. #: ../../../CHANGELOG.md:2939

  5455. 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."

  5456. msgstr ""

  5457. 

  5458. #: ../../../CHANGELOG.md:2940

  5459. 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"

  5460. msgstr ""

  5461. 

  5462. #: ../../../CHANGELOG.md:2943

  5463. msgid "2022-04-14"

  5464. msgstr ""

  5465. 

  5466. #: ../../../CHANGELOG.md:2945

  5467. msgid "(Compatibility Break) Changes to `docker-src` permissions necessitating manual action"

  5468. msgstr ""

  5469. 

  5470. #: ../../../CHANGELOG.md:2947

  5471. msgid "Users who build container images from source will need to manually correct file permissions of some directories on the server."

  5472. msgstr ""

  5473. 

  5474. #: ../../../CHANGELOG.md:2949

  5475. 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)."

  5476. msgstr ""

  5477. 

  5478. #: ../../../CHANGELOG.md:2951

  5479. 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."

  5480. msgstr ""

  5481. 

  5482. #: ../../../CHANGELOG.md:2953

  5483. 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`"

  5484. msgstr ""

  5485. 

  5486. #: ../../../CHANGELOG.md:2956

  5487. msgid "2022-03-17"

  5488. msgstr ""

  5489. 

  5490. #: ../../../CHANGELOG.md:2958

  5491. msgid "(Compatibility Break) ma1sd identity server no longer installed by default"

  5492. msgstr ""

  5493. 

  5494. #: ../../../CHANGELOG.md:2960

  5495. 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)."

  5496. msgstr ""

  5497. 

  5498. #: ../../../CHANGELOG.md:2962

  5499. 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."

  5500. msgstr ""

  5501. 

  5502. #: ../../../CHANGELOG.md:2964

  5503. msgid "Since Element clients no longer default to using a public identity server if another one is not provided, we can stop installing ma1sd."

  5504. msgstr ""

  5505. 

  5506. #: ../../../CHANGELOG.md:2966

  5507. 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:"

  5508. msgstr ""

  5509. 

  5510. #: ../../../CHANGELOG.md:2973

  5511. msgid "2022-02-12"

  5512. msgstr ""

  5513. 

  5514. #: ../../../CHANGELOG.md:2975

  5515. msgid "matrix_encryption_disabler support"

  5516. msgstr ""

  5517. 

  5518. #: ../../../CHANGELOG.md:2977

  5519. 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)."

  5520. msgstr ""

  5521. 

  5522. #: ../../../CHANGELOG.md:2979

  5523. 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`."

  5524. msgstr ""

  5525. 

  5526. #: ../../../CHANGELOG.md:2982

  5527. msgid "2022-02-01"

  5528. msgstr ""

  5529. 

  5530. #: ../../../CHANGELOG.md:2984

  5531. msgid "matrix-hookshot bridging support"

  5532. msgstr ""

  5533. 

  5534. #: ../../../CHANGELOG.md:2986

  5535. 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."

  5536. msgstr ""

  5537. 

  5538. #: ../../../CHANGELOG.md:2989

  5539. msgid "2022-01-31"

  5540. msgstr ""

  5541. 

  5542. #: ../../../CHANGELOG.md:2991

  5543. msgid "ARM support for matrix-corporal"

  5544. msgstr ""

  5545. 

  5546. #: ../../../CHANGELOG.md:2993

  5547. 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."

  5548. msgstr ""

  5549. 

  5550. #: ../../../CHANGELOG.md:2996

  5551. msgid "2022-01-07"

  5552. msgstr ""

  5553. 

  5554. #: ../../../CHANGELOG.md:2998

  5555. msgid "Dendrite support"

  5556. msgstr ""

  5557. 

  5558. #: ../../../CHANGELOG.md:3000

  5559. 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)."

  5560. msgstr ""

  5561. 

  5562. #: ../../../CHANGELOG.md:3002

  5563. 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."

  5564. msgstr ""

  5565. 

  5566. #: ../../../CHANGELOG.md:3004

  5567. msgid "We believe that 2022 will be the year of the non-Synapse Matrix server!"

  5568. msgstr ""

  5569. 

  5570. #: ../../../CHANGELOG.md:3006

  5571. 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."

  5572. msgstr ""

  5573. 

  5574. #: ../../../CHANGELOG.md:3008

  5575. 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)."

  5576. msgstr ""

  5577. 

  5578. #: ../../../CHANGELOG.md:3010

  5579. msgid "Adapting the configuration for existing Synapse installations"

  5580. msgstr ""

  5581. 

  5582. #: ../../../CHANGELOG.md:3012

  5583. 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."

  5584. msgstr ""

  5585. 

  5586. #: ../../../CHANGELOG.md:3014

  5587. msgid "The `vars.yml` file for **existing installations will need to be updated** by adding this **additional configuration**:"

  5588. msgstr ""

  5589. 

  5590. #: ../../../CHANGELOG.md:3026

  5591. msgid "Trying out Dendrite"

  5592. msgstr ""

  5593. 

  5594. #: ../../../CHANGELOG.md:3028

  5595. msgid "Finally, **to try out Dendrite**, we recommend that you **use a new server** and the following addition to your `vars.yml` configuration:"

  5596. msgstr ""

  5597. 

  5598. #: ../../../CHANGELOG.md:3034

  5599. msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse to Dendrite) without data loss."

  5600. msgstr ""

  5601. 

  5602. #: ../../../CHANGELOG.md:3036

  5603. msgid "We're excited to gain support for other homeserver implementations, like [Conduit](https://conduit.rs/), etc!"

  5604. msgstr ""

  5605. 

  5606. #: ../../../CHANGELOG.md:3038

  5607. msgid "Honoroit bot support"

  5608. msgstr ""

  5609. 

  5610. #: ../../../CHANGELOG.md:3040

  5611. 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."

  5612. msgstr ""

  5613. 

  5614. #: ../../../CHANGELOG.md:3042

  5615. msgid "See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documentation to get started."

  5616. msgstr ""

  5617. 

  5618. #: ../../../CHANGELOG.md:3045

  5619. msgid "2022-01-06"

  5620. msgstr ""

  5621. 

  5622. #: ../../../CHANGELOG.md:3047

  5623. msgid "Cinny support"

  5624. msgstr ""

  5625. 

  5626. #: ../../../CHANGELOG.md:3049

  5627. 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."

  5628. msgstr ""

  5629. 

  5630. #: ../../../CHANGELOG.md:3051

  5631. msgid "By default, we still install Element Web. Still, people who'd like to try Cinny out can now install it via the playbook."

  5632. msgstr ""

  5633. 

  5634. #: ../../../CHANGELOG.md:3053

  5635. msgid "Additional details are available in [Setting up Cinny](docs/configuring-playbook-client-cinny.md)."

  5636. msgstr ""

  5637. 

  5638. #: ../../../CHANGELOG.md:3056

  5639. msgid "2021-12-22"

  5640. msgstr ""

  5641. 

  5642. #: ../../../CHANGELOG.md:3058

  5643. msgid "Twitter bridging support via mautrix-twitter"

  5644. msgstr ""

  5645. 

  5646. #: ../../../CHANGELOG.md:3060

  5647. 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)."

  5648. msgstr ""

  5649. 

  5650. #: ../../../CHANGELOG.md:3063

  5651. msgid "2021-12-14"

  5652. msgstr ""

  5653. 

  5654. #: ../../../CHANGELOG.md:3065

  5655. msgid "(Security) Users of the Signal bridge may wish to upgrade it to work around log4j vulnerability"

  5656. msgstr ""

  5657. 

  5658. #: ../../../CHANGELOG.md:3067

  5659. 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."

  5660. msgstr ""

  5661. 

  5662. #: ../../../CHANGELOG.md:3069

  5663. 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)."

  5664. msgstr ""

  5665. 

  5666. #: ../../../CHANGELOG.md:3072

  5667. msgid "2021-11-11"

  5668. msgstr ""

  5669. 

  5670. #: ../../../CHANGELOG.md:3074

  5671. msgid "Dropped support for Postgres v9.6"

  5672. msgstr ""

  5673. 

  5674. #: ../../../CHANGELOG.md:3076

  5675. 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."

  5676. msgstr ""

  5677. 

  5678. #: ../../../CHANGELOG.md:3078

  5679. 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."

  5680. msgstr ""

  5681. 

  5682. #: ../../../CHANGELOG.md:3081

  5683. msgid "2021-10-23"

  5684. msgstr ""

  5685. 

  5686. #: ../../../CHANGELOG.md:3083

  5687. msgid "Hangouts bridge no longer updated, superseded by a Googlechat bridge"

  5688. msgstr ""

  5689. 

  5690. #: ../../../CHANGELOG.md:3085

  5691. 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."

  5692. msgstr ""

  5693. 

  5694. #: ../../../CHANGELOG.md:3087

  5695. 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."

  5696. msgstr ""

  5697. 

  5698. #: ../../../CHANGELOG.md:3090

  5699. msgid "2021-08-23"

  5700. msgstr ""

  5701. 

  5702. #: ../../../CHANGELOG.md:3092

  5703. msgid "LinkedIn bridging support via beeper-linkedin"

  5704. msgstr ""

  5705. 

  5706. #: ../../../CHANGELOG.md:3094

  5707. 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."

  5708. msgstr ""

  5709. 

  5710. #: ../../../CHANGELOG.md:3096

  5711. 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)."

  5712. msgstr ""

  5713. 

  5714. #: ../../../CHANGELOG.md:3098

  5715. msgid "To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)."

  5716. msgstr ""

  5717. 

  5718. #: ../../../CHANGELOG.md:3101

  5719. msgid "2021-08-20"

  5720. msgstr ""

  5721. 

  5722. #: ../../../CHANGELOG.md:3103

  5723. msgid "Sygnal upgraded — ARM support and no longer requires a database"

  5724. msgstr ""

  5725. 

  5726. #: ../../../CHANGELOG.md:3105

  5727. msgid "The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been upgraded from `v0.9.0` to `v0.10.1`."

  5728. msgstr ""

  5729. 

  5730. #: ../../../CHANGELOG.md:3107

  5731. msgid "This is an optional component for the playbook, so most of our users wouldn't care about this announcement."

  5732. msgstr ""

  5733. 

  5734. #: ../../../CHANGELOG.md:3109

  5735. msgid "Since this feels like a relatively big (and untested, as of yet) Sygnal change, we're putting up this changelog entry."

  5736. msgstr ""

  5737. 

  5738. #: ../../../CHANGELOG.md:3111

  5739. 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."

  5740. msgstr ""

  5741. 

  5742. #: ../../../CHANGELOG.md:3114

  5743. msgid "2021-05-21"

  5744. msgstr ""

  5745. 

  5746. #: ../../../CHANGELOG.md:3116

  5747. msgid "Hydrogen support"

  5748. msgstr ""

  5749. 

  5750. #: ../../../CHANGELOG.md:3118

  5751. 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."

  5752. msgstr ""

  5753. 

  5754. #: ../../../CHANGELOG.md:3120

  5755. 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."

  5756. msgstr ""

  5757. 

  5758. #: ../../../CHANGELOG.md:3122

  5759. msgid "Additional details are available in [Setting up Hydrogen](docs/configuring-playbook-client-hydrogen.md)."

  5760. msgstr ""

  5761. 

  5762. #: ../../../CHANGELOG.md:3125

  5763. msgid "2021-05-19"

  5764. msgstr ""

  5765. 

  5766. #: ../../../CHANGELOG.md:3127

  5767. msgid "Heisenbridge support"

  5768. msgstr ""

  5769. 

  5770. #: ../../../CHANGELOG.md:3129

  5771. 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)."

  5772. msgstr ""

  5773. 

  5774. #: ../../../CHANGELOG.md:3131

  5775. msgid "Additional details are available in [Setting up Heisenbridge bouncer-style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)."

  5776. msgstr ""

  5777. 

  5778. #: ../../../CHANGELOG.md:3134

  5779. msgid "2021-04-16"

  5780. msgstr ""

  5781. 

  5782. #: ../../../CHANGELOG.md:3136

  5783. msgid "Disabling TLSv1 and TLSv1.1 for coturn"

  5784. msgstr ""

  5785. 

  5786. #: ../../../CHANGELOG.md:3138

  5787. 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."

  5788. msgstr ""

  5789. 

  5790. #: ../../../CHANGELOG.md:3140

  5791. msgid "If you need to support old clients, you can re-enable both (or whichever one you need) with the following configuration:"

  5792. msgstr ""

  5793. 

  5794. #: ../../../CHANGELOG.md:3148

  5795. msgid "2021-04-05"

  5796. msgstr ""

  5797. 

  5798. #: ../../../CHANGELOG.md:3150

  5799. msgid "Automated local Postgres backup support"

  5800. msgstr ""

  5801. 

  5802. #: ../../../CHANGELOG.md:3152

  5803. 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)."

  5804. msgstr ""

  5805. 

  5806. #: ../../../CHANGELOG.md:3154

  5807. msgid "Additional details are available in [Setting up Postgres backup](docs/configuring-playbook-postgres-backup.md)."

  5808. msgstr ""

  5809. 

  5810. #: ../../../CHANGELOG.md:3157

  5811. msgid "2021-04-03"

  5812. msgstr ""

  5813. 

  5814. #: ../../../CHANGELOG.md:3159

  5815. msgid "Mjolnir moderation tool (bot) support"

  5816. msgstr ""

  5817. 

  5818. #: ../../../CHANGELOG.md:3161

  5819. 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)."

  5820. msgstr ""

  5821. 

  5822. #: ../../../CHANGELOG.md:3163

  5823. msgid "Additional details are available in [Setting up Mjolnir](docs/configuring-playbook-bot-mjolnir.md)."

  5824. msgstr ""

  5825. 

  5826. #: ../../../CHANGELOG.md:3166

  5827. msgid "2021-03-20"

  5828. msgstr ""

  5829. 

  5830. #: ../../../CHANGELOG.md:3168

  5831. msgid "Sygnal push gateway support"

  5832. msgstr ""

  5833. 

  5834. #: ../../../CHANGELOG.md:3170

  5835. msgid "The playbook can now install the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you."

  5836. msgstr ""

  5837. 

  5838. #: ../../../CHANGELOG.md:3172

  5839. msgid "This is only useful to people who develop/build their own Matrix client applications."

  5840. msgstr ""

  5841. 

  5842. #: ../../../CHANGELOG.md:3174

  5843. msgid "Additional details are available in our [Setting up the Sygnal push gateway](docs/configuring-playbook-sygnal.md) docs."

  5844. msgstr ""

  5845. 

  5846. #: ../../../CHANGELOG.md:3177

  5847. msgid "2021-03-16"

  5848. msgstr ""

  5849. 

  5850. #: ../../../CHANGELOG.md:3179

  5851. msgid "Go-NEB support"

  5852. msgstr ""

  5853. 

  5854. #: ../../../CHANGELOG.md:3181

  5855. 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."

  5856. msgstr ""

  5857. 

  5858. #: ../../../CHANGELOG.md:3183

  5859. msgid "Additional details are available in [Setting up Go-NEB](docs/configuring-playbook-bot-go-neb.md)."

  5860. msgstr ""

  5861. 

  5862. #: ../../../CHANGELOG.md:3186

  5863. msgid "2021-02-19"

  5864. msgstr ""

  5865. 

  5866. #: ../../../CHANGELOG.md:3188

  5867. msgid "GroupMe bridging support via mx-puppet-groupme"

  5868. msgstr ""

  5869. 

  5870. #: ../../../CHANGELOG.md:3190

  5871. 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)."

  5872. msgstr ""

  5873. 

  5874. #: ../../../CHANGELOG.md:3192

  5875. 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)."

  5876. msgstr ""

  5877. 

  5878. #: ../../../CHANGELOG.md:3194

  5879. msgid "To get started, follow our [Setting up MX Puppet GroupMe](docs/configuring-playbook-bridge-mx-puppet-groupme.md) docs."

  5880. msgstr ""

  5881. 

  5882. #: ../../../CHANGELOG.md:3196

  5883. msgid "Mautrix Instagram bridging support"

  5884. msgstr ""

  5885. 

  5886. #: ../../../CHANGELOG.md:3198

  5887. 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)."

  5888. msgstr ""

  5889. 

  5890. #: ../../../CHANGELOG.md:3200

  5891. msgid "Additional details are available in [Setting up Mautrix Instagram bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)."

  5892. msgstr ""

  5893. 

  5894. #: ../../../CHANGELOG.md:3202

  5895. msgid "Synapse workers support"

  5896. msgstr ""

  5897. 

  5898. #: ../../../CHANGELOG.md:3204

  5899. 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."

  5900. msgstr ""

  5901. 

  5902. #: ../../../CHANGELOG.md:3206

  5903. msgid "Having support for workers makes the playbook suitable for larger homeserver deployments."

  5904. msgstr ""

  5905. 

  5906. #: ../../../CHANGELOG.md:3208

  5907. 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)."

  5908. msgstr ""

  5909. 

  5910. #: ../../../CHANGELOG.md:3210

  5911. 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)."

  5912. msgstr ""

  5913. 

  5914. #: ../../../CHANGELOG.md:3212

  5915. msgid "To enable Synapse workers, follow our [Load balancing with workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) documentation."

  5916. msgstr ""

  5917. 

  5918. #: ../../../CHANGELOG.md:3215

  5919. msgid "2021-02-12"

  5920. msgstr ""

  5921. 

  5922. #: ../../../CHANGELOG.md:3217

  5923. msgid "(Potential Breaking Change) Monitoring/metrics support using Prometheus and Grafana"

  5924. msgstr ""

  5925. 

  5926. #: ../../../CHANGELOG.md:3219

  5927. 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."

  5928. msgstr ""

  5929. 

  5930. #: ../../../CHANGELOG.md:3221

  5931. 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."

  5932. msgstr ""

  5933. 

  5934. #: ../../../CHANGELOG.md:3223

  5935. 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`."

  5936. msgstr ""

  5937. 

  5938. #: ../../../CHANGELOG.md:3226

  5939. msgid "2021-01-31"

  5940. msgstr ""

  5941. 

  5942. #: ../../../CHANGELOG.md:3228

  5943. msgid "Etherpad support"

  5944. msgstr ""

  5945. 

  5946. #: ../../../CHANGELOG.md:3230

  5947. 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."

  5948. msgstr ""

  5949. 

  5950. #: ../../../CHANGELOG.md:3232

  5951. msgid "To get it installed, follow [our Etherpad docs page](docs/configuring-playbook-etherpad.md)."

  5952. msgstr ""

  5953. 

  5954. #: ../../../CHANGELOG.md:3235

  5955. msgid "2021-01-22"

  5956. msgstr ""

  5957. 

  5958. #: ../../../CHANGELOG.md:3237

  5959. msgid "(Breaking Change) Postgres changes that require manual intervention"

  5960. msgstr ""

  5961. 

  5962. #: ../../../CHANGELOG.md:3239

  5963. msgid "We've made a lot of changes to our Postgres setup and some manual action is required (described below). Sorry about the hassle."

  5964. msgstr ""

  5965. 

  5966. #: ../../../CHANGELOG.md:3241

  5967. 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."

  5968. msgstr ""

  5969. 

  5970. #: ../../../CHANGELOG.md:3243

  5971. msgid "Why?"

  5972. msgstr ""

  5973. 

  5974. #: ../../../CHANGELOG.md:3245

  5975. 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:"

  5976. msgstr ""

  5977. 

  5978. #: ../../../CHANGELOG.md:3246

  5979. 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`)"

  5980. msgstr ""

  5981. 

  5982. #: ../../../CHANGELOG.md:3247

  5983. 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`)"

  5984. msgstr ""

  5985. 

  5986. #: ../../../CHANGELOG.md:3248

  5987. 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`)"

  5988. msgstr ""

  5989. 

  5990. #: ../../../CHANGELOG.md:3249

  5991. 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."

  5992. msgstr ""

  5993. 

  5994. #: ../../../CHANGELOG.md:3250

  5995. 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."

  5996. msgstr ""

  5997. 

  5998. #: ../../../CHANGELOG.md:3252

  5999. msgid "So, this is some **effort to improve security** and to **prepare for a brighter future of having more homeserver options** than just Synapse."

  6000. msgstr ""

  6001. 

  6002. #: ../../../CHANGELOG.md:3254

  6003. msgid "What has really changed?"

  6004. msgstr ""

  6005. 

  6006. #: ../../../CHANGELOG.md:3256

  6007. msgid "the default superuser Postgres username is now `matrix` (used to be `synapse`)"

  6008. msgstr ""

  6009. 

  6010. #: ../../../CHANGELOG.md:3257

  6011. msgid "the default Postgres database is now `matrix` (used to be `homeserver`)"

  6012. msgstr ""

  6013. 

  6014. #: ../../../CHANGELOG.md:3258

  6015. msgid "Synapse's database is now `synapse` (used to be `homeserver`). This is now just another \"additional database\" that the playbook manages for you"

  6016. msgstr ""

  6017. 

  6018. #: ../../../CHANGELOG.md:3259

  6019. msgid "Synapse's user called `synapse` is just a regular user that can only use the `synapse` database (not a superuser anymore)"

  6020. msgstr ""

  6021. 

  6022. #: ../../../CHANGELOG.md:3261

  6023. msgid "What do I do if I'm using the integrated Postgres server (default)?"

  6024. msgstr ""

  6025. 

  6026. #: ../../../CHANGELOG.md:3263

  6027. 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."

  6028. msgstr ""

  6029. 

  6030. #: ../../../CHANGELOG.md:3265

  6031. msgid "To migrate to the new setup, expect a few minutes of downtime, while you follow these steps:"

  6032. msgstr ""

  6033. 

  6034. #: ../../../CHANGELOG.md:3267

  6035. 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."

  6036. msgstr ""

  6037. 

  6038. #: ../../../CHANGELOG.md:3269

  6039. 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!"

  6040. msgstr ""

  6041. 

  6042. #: ../../../CHANGELOG.md:3271

  6043. msgid "Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` file, adding a line like this:"

  6044. msgstr ""

  6045. 

  6046. #: ../../../CHANGELOG.md:3276

  6047. #: ../../../CHANGELOG.md:3288

  6048. msgid "… where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2."

  6049. msgstr ""

  6050. 

  6051. #: ../../../CHANGELOG.md:3278

  6052. msgid "Stop all services: `ansible-playbook -i inventory/hosts setup.yml --tags=stop`"

  6053. msgstr ""

  6054. 

  6055. #: ../../../CHANGELOG.md:3279

  6056. msgid "Log in to the server via SSH. The next commands will be performed there."

  6057. msgstr ""

  6058. 

  6059. #: ../../../CHANGELOG.md:3280

  6060. msgid "Start the Postgres database server: `systemctl start matrix-postgres`"

  6061. msgstr ""

  6062. 

  6063. #: ../../../CHANGELOG.md:3281

  6064. msgid "Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`"

  6065. msgstr ""

  6066. 

  6067. #: ../../../CHANGELOG.md:3282

  6068. msgid "Execute the following query, while making sure to **change the password inside** (**don't forget the ending `;`**):"

  6069. msgstr ""

  6070. 

  6071. #: ../../../CHANGELOG.md:3290

  6072. msgid "Execute the following queries as you see them (no modifications necessary, so you can just **paste them all at once**):"

  6073. msgstr ""

  6074. 

  6075. #: ../../../CHANGELOG.md:3308

  6076. msgid "You may need to press *Enter* after pasting the lines above."

  6077. msgstr ""

  6078. 

  6079. #: ../../../CHANGELOG.md:3310

  6080. msgid "Re-run the playbook normally: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`"

  6081. msgstr ""

  6082. 

  6083. #: ../../../CHANGELOG.md:3312

  6084. msgid "What do I do if I'm using an external Postgres server?"

  6085. msgstr ""

  6086. 

  6087. #: ../../../CHANGELOG.md:3314

  6088. 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."

  6089. msgstr ""

  6090. 

  6091. #: ../../../CHANGELOG.md:3316

  6092. 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."

  6093. msgstr ""

  6094. 

  6095. #: ../../../CHANGELOG.md:3319

  6096. msgid "2021-01-20"

  6097. msgstr ""

  6098. 

  6099. #: ../../../CHANGELOG.md:3321

  6100. msgid "(Breaking Change) The mautrix-facebook bridge now requires a Postgres database"

  6101. msgstr ""

  6102. 

  6103. #: ../../../CHANGELOG.md:3323

  6104. 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."

  6105. msgstr ""

  6106. 

  6107. #: ../../../CHANGELOG.md:3325

  6108. 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."

  6109. msgstr ""

  6110. 

  6111. #: ../../../CHANGELOG.md:3327

  6112. 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."

  6113. msgstr ""

  6114. 

  6115. #: ../../../CHANGELOG.md:3329

  6116. msgid "Whether this change requires your intervention depends mostly on:"

  6117. msgstr ""

  6118. 

  6119. #: ../../../CHANGELOG.md:3330

  6120. 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)."

  6121. msgstr ""

  6122. 

  6123. #: ../../../CHANGELOG.md:3331

  6124. 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))."

  6125. msgstr ""

  6126. 

  6127. #: ../../../CHANGELOG.md:3333

  6128. 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."

  6129. msgstr ""

  6130. 

  6131. #: ../../../CHANGELOG.md:3335

  6132. msgid "Upgrade path for people NOT running an external Postgres server (default for the playbook)"

  6133. msgstr ""

  6134. 

  6135. #: ../../../CHANGELOG.md:3337

  6136. 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`) ."

  6137. msgstr ""

  6138. 

  6139. #: ../../../CHANGELOG.md:3339

  6140. 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."

  6141. msgstr ""

  6142. 

  6143. #: ../../../CHANGELOG.md:3341

  6144. msgid "Alternatively, [you can stay on SQLite for a little longer](#staying-on-sqlite-for-a-little-longer-temporary-solution)."

  6145. msgstr ""

  6146. 

  6147. #: ../../../CHANGELOG.md:3343

  6148. msgid "Upgrade path for people running an external Postgres server"

  6149. msgstr ""

  6150. 

  6151. #: ../../../CHANGELOG.md:3345

  6152. msgid "For people using the internal Postgres server (the default for the playbook):"

  6153. msgstr ""

  6154. 

  6155. #: ../../../CHANGELOG.md:3346

  6156. msgid "we automatically create an additional `matrix_mautrix_facebook` Postgres database and credentials to access it"

  6157. msgstr ""

  6158. 

  6159. #: ../../../CHANGELOG.md:3347

  6160. msgid "we automatically adjust the bridge's `matrix_mautrix_facebook_database_*` variables to point the bridge to that Postgres database"

  6161. msgstr ""

  6162. 

  6163. #: ../../../CHANGELOG.md:3348

  6164. msgid "we use [pgloader](https://pgloader.io/) to automatically import the existing SQLite data for the bridge into the `matrix_mautrix_facebook` Postgres database"

  6165. msgstr ""

  6166. 

  6167. #: ../../../CHANGELOG.md:3350

  6168. 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."

  6169. msgstr ""

  6170. 

  6171. #: ../../../CHANGELOG.md:3352

  6172. msgid "You have 3 ways to proceed:"

  6173. msgstr ""

  6174. 

  6175. #: ../../../CHANGELOG.md:3354

  6176. msgid "contribute to the playbook to make this possible (difficult)"

  6177. msgstr ""

  6178. 

  6179. #: ../../../CHANGELOG.md:3355

  6180. msgid "or, do the migration \"steps\" manually:"

  6181. msgstr ""

  6182. 

  6183. #: ../../../CHANGELOG.md:3356

  6184. msgid "stop the bridge (`systemctl stop matrix-mautrix-facebook`)"

  6185. msgstr ""

  6186. 

  6187. #: ../../../CHANGELOG.md:3357

  6188. msgid "create a new `matrix_mautrix_facebook` Postgres database for it"

  6189. msgstr ""

  6190. 

  6191. #: ../../../CHANGELOG.md:3358

  6192. msgid "run [pgloader](https://pgloader.io/) manually (we import this bridge's data using default settings and it works well)"

  6193. msgstr ""

  6194. 

  6195. #: ../../../CHANGELOG.md:3359

  6196. 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`"

  6197. msgstr ""

  6198. 

  6199. #: ../../../CHANGELOG.md:3360

  6200. msgid "switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: 'postgres'` in your `vars.yml` file)"

  6201. msgstr ""

  6202. 

  6203. #: ../../../CHANGELOG.md:3361

  6204. 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`)"

  6205. msgstr ""

  6206. 

  6207. #: ../../../CHANGELOG.md:3362

  6208. msgid "send a `login` message to the Facebook bridge bot again"

  6209. msgstr ""

  6210. 

  6211. #: ../../../CHANGELOG.md:3363

  6212. msgid "or, [stay on SQLite for a little longer (temporary solution)](#staying-on-sqlite-for-a-little-longer-temporary-solution)"

  6213. msgstr ""

  6214. 

  6215. #: ../../../CHANGELOG.md:3365

  6216. msgid "Staying on SQLite for a little longer (temporary solution)"

  6217. msgstr ""

  6218. 

  6219. #: ../../../CHANGELOG.md:3367

  6220. msgid "To keep using this bridge with SQLite for a little longer (**not recommended**), use the following configuration in your `vars.yml` file:"

  6221. msgstr ""

  6222. 

  6223. #: ../../../CHANGELOG.md:3377

  6224. 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."

  6225. msgstr ""

  6226. 

  6227. #: ../../../CHANGELOG.md:3380

  6228. msgid "2021-01-17"

  6229. msgstr ""

  6230. 

  6231. #: ../../../CHANGELOG.md:3382

  6232. msgid "matrix-corporal goes 2.0"

  6233. msgstr ""

  6234. 

  6235. #: ../../../CHANGELOG.md:3384

  6236. 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."

  6237. msgstr ""

  6238. 

  6239. #: ../../../CHANGELOG.md:3386

  6240. msgid "No manual intervention is required in the common case."

  6241. msgstr ""

  6242. 

  6243. #: ../../../CHANGELOG.md:3388

  6244. 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)."

  6245. msgstr ""

  6246. 

  6247. #: ../../../CHANGELOG.md:3391

  6248. msgid "2021-01-14"

  6249. msgstr ""

  6250. 

  6251. #: ../../../CHANGELOG.md:3393

  6252. msgid "Moving from cronjobs to systemd timers"

  6253. msgstr ""

  6254. 

  6255. #: ../../../CHANGELOG.md:3395

  6256. 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."

  6257. msgstr ""

  6258. 

  6259. #: ../../../CHANGELOG.md:3397

  6260. msgid "The largest benefit of this is that we no longer require you to install a cron daemon, thus simplifying our install procedure."

  6261. msgstr ""

  6262. 

  6263. #: ../../../CHANGELOG.md:3399

  6264. msgid "The playbook will migrate you from cronjobs to systemd timers automatically. This is just a heads up."

  6265. msgstr ""

  6266. 

  6267. #: ../../../CHANGELOG.md:3402

  6268. msgid "2021-01-08"

  6269. msgstr ""

  6270. 

  6271. #: ../../../CHANGELOG.md:3404

  6272. msgid "(Breaking Change) New SSL configuration"

  6273. msgstr ""

  6274. 

  6275. #: ../../../CHANGELOG.md:3406

  6276. msgid "SSL configuration (protocols, ciphers) can now be more easily controlled thanks to us making use of configuration presets."

  6277. msgstr ""

  6278. 

  6279. #: ../../../CHANGELOG.md:3408

  6280. msgid "We define a few presets (old, intermediate, modern), following the [Mozilla SSL Configuration Generator](https://ssl-config.mozilla.org/#server=nginx)."

  6281. msgstr ""

  6282. 

  6283. #: ../../../CHANGELOG.md:3410

  6284. msgid "A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is used (defaults to `\"intermediate\"`)."

  6285. msgstr ""

  6286. 

  6287. #: ../../../CHANGELOG.md:3412

  6288. 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)."

  6289. msgstr ""

  6290. 

  6291. #: ../../../CHANGELOG.md:3414

  6292. msgid "To revert to the old behaviour, set the following variables:"

  6293. msgstr ""

  6294. 

  6295. #: ../../../CHANGELOG.md:3421

  6296. 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."

  6297. msgstr ""

  6298. 

  6299. #: ../../../CHANGELOG.md:3424

  6300. msgid "2021-01-03"

  6301. msgstr ""

  6302. 

  6303. #: ../../../CHANGELOG.md:3426

  6304. msgid "Signal bridging support via mautrix-signal"

  6305. msgstr ""

  6306. 

  6307. #: ../../../CHANGELOG.md:3428

  6308. 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."

  6309. msgstr ""

  6310. 

  6311. #: ../../../CHANGELOG.md:3430

  6312. 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)."

  6313. msgstr ""

  6314. 

  6315. #: ../../../CHANGELOG.md:3433

  6316. msgid "2020-12-23"

  6317. msgstr ""

  6318. 

  6319. #: ../../../CHANGELOG.md:3435

  6320. msgid "The big move to all-on-Postgres (potentially dangerous)"

  6321. msgstr ""

  6322. 

  6323. #: ../../../CHANGELOG.md:3437

  6324. 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."

  6325. msgstr ""

  6326. 

  6327. #: ../../../CHANGELOG.md:3439

  6328. 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)."

  6329. msgstr ""

  6330. 

  6331. #: ../../../CHANGELOG.md:3441

  6332. 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!"

  6333. msgstr ""

  6334. 

  6335. #: ../../../CHANGELOG.md:3443

  6336. msgid "Moving all services to Postgres brings a few **benefits** to us:"

  6337. msgstr ""

  6338. 

  6339. #: ../../../CHANGELOG.md:3445

  6340. msgid "**improved performance**"

  6341. msgstr ""

  6342. 

  6343. #: ../../../CHANGELOG.md:3446

  6344. msgid "**improved compatibility**. Most bridges are deprecating SQLite/nedb support or offer less features when not on Postgres."

  6345. msgstr ""

  6346. 

  6347. #: ../../../CHANGELOG.md:3447

  6348. 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."

  6349. msgstr ""

  6350. 

  6351. #: ../../../CHANGELOG.md:3448

  6352. 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."

  6353. msgstr ""

  6354. 

  6355. #: ../../../CHANGELOG.md:3450

  6356. msgid "Key takeway"

  6357. msgstr ""

  6358. 

  6359. #: ../../../CHANGELOG.md:3452

  6360. 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)"

  6361. msgstr ""

  6362. 

  6363. #: ../../../CHANGELOG.md:3454

  6364. 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)."

  6365. msgstr ""

  6366. 

  6367. #: ../../../CHANGELOG.md:3456

  6368. msgid "Opting-out of the Postgres migration"

  6369. msgstr ""

  6370. 

  6371. #: ../../../CHANGELOG.md:3458

  6372. 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."

  6373. msgstr ""

  6374. 

  6375. #: ../../../CHANGELOG.md:3460

  6376. 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`)."

  6377. msgstr ""

  6378. 

  6379. #: ../../../CHANGELOG.md:3462

  6380. msgid "Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them."

  6381. msgstr ""

  6382. 

  6383. #: ../../../CHANGELOG.md:3464

  6384. msgid "Going back to SQLite/nedb if things went wrong"

  6385. msgstr ""

  6386. 

  6387. #: ../../../CHANGELOG.md:3466

  6388. 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:"

  6389. msgstr ""

  6390. 

  6391. #: ../../../CHANGELOG.md:3468

  6392. msgid "stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"

  6393. msgstr ""

  6394. 

  6395. #: ../../../CHANGELOG.md:3469

  6396. 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`"

  6397. msgstr ""

  6398. 

  6399. #: ../../../CHANGELOG.md:3470

  6400. 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."

  6401. msgstr ""

  6402. 

  6403. #: ../../../CHANGELOG.md:3471

  6404. msgid "re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`)"

  6405. msgstr ""

  6406. 

  6407. #: ../../../CHANGELOG.md:3472

  6408. msgid "[get in touch](README.md#support) with us"

  6409. msgstr ""

  6410. 

  6411. #: ../../../CHANGELOG.md:3474

  6412. msgid "2020-12-11"

  6413. msgstr ""

  6414. 

  6415. #: ../../../CHANGELOG.md:3476

  6416. msgid "synapse-janitor support removed"

  6417. msgstr ""

  6418. 

  6419. #: ../../../CHANGELOG.md:3478

  6420. 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."

  6421. msgstr ""

  6422. 

  6423. #: ../../../CHANGELOG.md:3480

  6424. 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."

  6425. msgstr ""

  6426. 

  6427. #: ../../../CHANGELOG.md:3482

  6428. msgid "Docker 20.10 is here"

  6429. msgstr ""

  6430. 

  6431. #: ../../../CHANGELOG.md:3484

  6432. msgid "(No need to do anything special in relation to this. Just something to keep in mind)"

  6433. msgstr ""

  6434. 

  6435. #: ../../../CHANGELOG.md:3486

  6436. msgid "Docker 20.10 got released recently and your server will likely get it the next time you update."

  6437. msgstr ""

  6438. 

  6439. #: ../../../CHANGELOG.md:3488

  6440. 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."

  6441. msgstr ""

  6442. 

  6443. #: ../../../CHANGELOG.md:3491

  6444. msgid "2020-12-08"

  6445. msgstr ""

  6446. 

  6447. #: ../../../CHANGELOG.md:3493

  6448. msgid "openid APIs exposed by default on the federation port when federation disabled"

  6449. msgstr ""

  6450. 

  6451. #: ../../../CHANGELOG.md:3495

  6452. msgid "We've changed some defaults. People running with our default configuration (federation enabled), are not affected at all."

  6453. msgstr ""

  6454. 

  6455. #: ../../../CHANGELOG.md:3497

  6456. msgid "If you are running an unfederated server (`matrix_synapse_federation_enabled: false`), this may be of interest to you."

  6457. msgstr ""

  6458. 

  6459. #: ../../../CHANGELOG.md:3499

  6460. 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`."

  6461. msgstr ""

  6462. 

  6463. #: ../../../CHANGELOG.md:3502

  6464. msgid "2020-11-27"

  6465. msgstr ""

  6466. 

  6467. #: ../../../CHANGELOG.md:3504

  6468. msgid "Recent Jitsi updates may require configuration changes"

  6469. msgstr ""

  6470. 

  6471. #: ../../../CHANGELOG.md:3506

  6472. 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."

  6473. msgstr ""

  6474. 

  6475. #: ../../../CHANGELOG.md:3508

  6476. msgid "**If you use our default Jitsi settings, you won't have to do anything.**"

  6477. msgstr ""

  6478. 

  6479. #: ../../../CHANGELOG.md:3510

  6480. 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."

  6481. msgstr ""

  6482. 

  6483. #: ../../../CHANGELOG.md:3512

  6484. 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."

  6485. msgstr ""

  6486. 

  6487. #: ../../../CHANGELOG.md:3514

  6488. 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."

  6489. msgstr ""

  6490. 

  6491. #: ../../../CHANGELOG.md:3517

  6492. msgid "2020-11-23"

  6493. msgstr ""

  6494. 

  6495. #: ../../../CHANGELOG.md:3519

  6496. #: ../../../CHANGELOG.md:3527

  6497. msgid "Breaking change matrix-sms-bridge"

  6498. msgstr ""

  6499. 

  6500. #: ../../../CHANGELOG.md:3521

  6501. 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."

  6502. msgstr ""

  6503. 

  6504. #: ../../../CHANGELOG.md:3523

  6505. 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."

  6506. msgstr ""

  6507. 

  6508. #: ../../../CHANGELOG.md:3525

  6509. msgid "2020-11-13"

  6510. msgstr ""

  6511. 

  6512. #: ../../../CHANGELOG.md:3529

  6513. 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."

  6514. msgstr ""

  6515. 

  6516. #: ../../../CHANGELOG.md:3531

  6517. msgid "Add the following to your `vars.yml` file: `matrix_sms_bridge_container_extra_arguments=['--env SPRING_PROFILES_ACTIVE=initialsync']`"

  6518. msgstr ""

  6519. 

  6520. #: ../../../CHANGELOG.md:3532

  6521. msgid "Login to your host shell and remove old systemd file from your host: `rm /etc/systemd/system/matrix-sms-bridge-database.service`"

  6522. msgstr ""

  6523. 

  6524. #: ../../../CHANGELOG.md:3533

  6525. msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-sms-bridge,start`"

  6526. msgstr ""

  6527. 

  6528. #: ../../../CHANGELOG.md:3534

  6529. msgid "Login to your host shell and check the logs with `journalctl -u matrix-sms-bridge` until the sync finished."

  6530. msgstr ""

  6531. 

  6532. #: ../../../CHANGELOG.md:3535

  6533. msgid "Remove the var from the first step."

  6534. msgstr ""

  6535. 

  6536. #: ../../../CHANGELOG.md:3536

  6537. msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`."

  6538. msgstr ""

  6539. 

  6540. #: ../../../CHANGELOG.md:3538

  6541. msgid "2020-11-10"

  6542. msgstr ""

  6543. 

  6544. #: ../../../CHANGELOG.md:3540

  6545. msgid "Dynamic DNS support"

  6546. msgstr ""

  6547. 

  6548. #: ../../../CHANGELOG.md:3542

  6549. msgid "Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook can now manage Dynamic DNS for you using [ddclient](https://ddclient.net/)."

  6550. msgstr ""

  6551. 

  6552. #: ../../../CHANGELOG.md:3544

  6553. msgid "To learn more, follow our [Dynamic DNS docs page](docs/configuring-playbook-dynamic-dns.md)."

  6554. msgstr ""

  6555. 

  6556. #: ../../../CHANGELOG.md:3547

  6557. msgid "2020-10-28"

  6558. msgstr ""

  6559. 

  6560. #: ../../../CHANGELOG.md:3549

  6561. msgid "(Compatibility Break) https://matrix.example.com/ now redirects to https://element.example.com/"

  6562. msgstr ""

  6563. 

  6564. #: ../../../CHANGELOG.md:3551

  6565. 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."

  6566. msgstr ""

  6567. 

  6568. #: ../../../CHANGELOG.md:3553

  6569. 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))."

  6570. msgstr ""

  6571. 

  6572. #: ../../../CHANGELOG.md:3555

  6573. 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."

  6574. msgstr ""

  6575. 

  6576. #: ../../../CHANGELOG.md:3557

  6577. 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: \"\"`)."

  6578. msgstr ""

  6579. 

  6580. #: ../../../CHANGELOG.md:3560

  6581. msgid "2020-10-26"

  6582. msgstr ""

  6583. 

  6584. #: ../../../CHANGELOG.md:3562

  6585. msgid "(Compatibility Break) /_synapse/admin is no longer publicly exposed by default"

  6586. msgstr ""

  6587. 

  6588. #: ../../../CHANGELOG.md:3564

  6589. 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."

  6590. msgstr ""

  6591. 

  6592. #: ../../../CHANGELOG.md:3566

  6593. 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."

  6594. msgstr ""

  6595. 

  6596. #: ../../../CHANGELOG.md:3568

  6597. 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`):"

  6598. msgstr ""

  6599. 

  6600. #: ../../../CHANGELOG.md:3575

  6601. msgid "2020-10-02"

  6602. msgstr ""

  6603. 

  6604. #: ../../../CHANGELOG.md:3577

  6605. msgid "Minimum Ansible version raised to v2.7.0"

  6606. msgstr ""

  6607. 

  6608. #: ../../../CHANGELOG.md:3579

  6609. 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."

  6610. msgstr ""

  6611. 

  6612. #: ../../../CHANGELOG.md:3581

  6613. 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)."

  6614. msgstr ""

  6615. 

  6616. #: ../../../CHANGELOG.md:3583

  6617. msgid "Our [Ansible docs page](docs/ansible.md) contains information on how to run a more up-to-date version of Ansible."

  6618. msgstr ""

  6619. 

  6620. #: ../../../CHANGELOG.md:3586

  6621. msgid "2020-10-01"

  6622. msgstr ""

  6623. 

  6624. #: ../../../CHANGELOG.md:3588

  6625. msgid "Postgres 13 support"

  6626. msgstr ""

  6627. 

  6628. #: ../../../CHANGELOG.md:3590

  6629. msgid "The playbook now installs [Postgres 13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) by default."

  6630. msgstr ""

  6631. 

  6632. #: ../../../CHANGELOG.md:3592

  6633. 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)."

  6634. msgstr ""

  6635. 

  6636. #: ../../../CHANGELOG.md:3594

  6637. msgid "2020-09-01"

  6638. msgstr ""

  6639. 

  6640. #: ../../../CHANGELOG.md:3596

  6641. msgid "matrix-registration support"

  6642. msgstr ""

  6643. 

  6644. #: ../../../CHANGELOG.md:3598

  6645. 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."

  6646. msgstr ""

  6647. 

  6648. #: ../../../CHANGELOG.md:3600

  6649. msgid "See our [Setting up matrix-registration](docs/configuring-playbook-matrix-registration.md) documentation page to get started."

  6650. msgstr ""

  6651. 

  6652. #: ../../../CHANGELOG.md:3603

  6653. msgid "2020-08-21"

  6654. msgstr ""

  6655. 

  6656. #: ../../../CHANGELOG.md:3605

  6657. msgid "rust-synapse-compress-state support"

  6658. msgstr ""

  6659. 

  6660. #: ../../../CHANGELOG.md:3607

  6661. 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."

  6662. msgstr ""

  6663. 

  6664. #: ../../../CHANGELOG.md:3609

  6665. 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."

  6666. msgstr ""

  6667. 

  6668. #: ../../../CHANGELOG.md:3612

  6669. msgid "2020-07-22"

  6670. msgstr ""

  6671. 

  6672. #: ../../../CHANGELOG.md:3614

  6673. msgid "Synapse Admin support"

  6674. msgstr ""

  6675. 

  6676. #: ../../../CHANGELOG.md:3616

  6677. msgid "The playbook can now help you set up [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin)."

  6678. msgstr ""

  6679. 

  6680. #: ../../../CHANGELOG.md:3618

  6681. msgid "See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-admin.md) documentation to get started."

  6682. msgstr ""

  6683. 

  6684. #: ../../../CHANGELOG.md:3621

  6685. msgid "2020-07-20"

  6686. msgstr ""

  6687. 

  6688. #: ../../../CHANGELOG.md:3623

  6689. msgid "matrix-reminder-bot support"

  6690. msgstr ""

  6691. 

  6692. #: ../../../CHANGELOG.md:3625

  6693. msgid "The playbook can now help you set up [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)."

  6694. msgstr ""

  6695. 

  6696. #: ../../../CHANGELOG.md:3627

  6697. msgid "See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-matrix-reminder-bot.md) documentation to get started."

  6698. msgstr ""

  6699. 

  6700. #: ../../../CHANGELOG.md:3630

  6701. msgid "2020-07-17"

  6702. msgstr ""

  6703. 

  6704. #: ../../../CHANGELOG.md:3632

  6705. msgid "(Compatibility Break) Riot is now Element"

  6706. msgstr ""

  6707. 

  6708. #: ../../../CHANGELOG.md:3634

  6709. msgid "As per the official announcement, [Riot has been rebraned to Element](https://element.io/blog/welcome-to-element/)."

  6710. msgstr ""

  6711. 

  6712. #: ../../../CHANGELOG.md:3636

  6713. msgid "The playbook follows suit. Existing installations have a few options for how to handle this."

  6714. msgstr ""

  6715. 

  6716. #: ../../../CHANGELOG.md:3638

  6717. msgid "See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md#migrating-to-element) documentation page for more details."

  6718. msgstr ""

  6719. 

  6720. #: ../../../CHANGELOG.md:3641

  6721. msgid "2020-07-03"

  6722. msgstr ""

  6723. 

  6724. #: ../../../CHANGELOG.md:3643

  6725. msgid "Steam bridging support via mx-puppet-steam"

  6726. msgstr ""

  6727. 

  6728. #: ../../../CHANGELOG.md:3645

  6729. 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."

  6730. msgstr ""

  6731. 

  6732. #: ../../../CHANGELOG.md:3648

  6733. msgid "2020-07-01"

  6734. msgstr ""

  6735. 

  6736. #: ../../../CHANGELOG.md:3650

  6737. msgid "Discord bridging support via mx-puppet-discord"

  6738. msgstr ""

  6739. 

  6740. #: ../../../CHANGELOG.md:3652

  6741. 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."

  6742. msgstr ""

  6743. 

  6744. #: ../../../CHANGELOG.md:3654

  6745. 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)."

  6746. msgstr ""

  6747. 

  6748. #: ../../../CHANGELOG.md:3657

  6749. msgid "2020-06-30"

  6750. msgstr ""

  6751. 

  6752. #: ../../../CHANGELOG.md:3659

  6753. msgid "Instagram and Twitter bridging support"

  6754. msgstr ""

  6755. 

  6756. #: ../../../CHANGELOG.md:3661

  6757. 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."

  6758. msgstr ""

  6759. 

  6760. #: ../../../CHANGELOG.md:3663

  6761. 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."

  6762. msgstr ""

  6763. 

  6764. #: ../../../CHANGELOG.md:3666

  6765. msgid "2020-06-28"

  6766. msgstr ""

  6767. 

  6768. #: ../../../CHANGELOG.md:3668

  6769. msgid "(Post Mortem / fixed Security Issue) Re-enabling User Directory search powered by the ma1sd Identity Server"

  6770. msgstr ""

  6771. 

  6772. #: ../../../CHANGELOG.md:3670

  6773. #: ../../../CHANGELOG.md:3699

  6774. msgid "User Directory search requests used to go to the ma1sd identity server by default, which queried its own stores and the Synapse database."

  6775. msgstr ""

  6776. 

  6777. #: ../../../CHANGELOG.md:3672

  6778. 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."

  6779. msgstr ""

  6780. 

  6781. #: ../../../CHANGELOG.md:3674

  6782. 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`"

  6783. msgstr ""

  6784. 

  6785. #: ../../../CHANGELOG.md:3676

  6786. msgid "As always, re-running the playbook is enough to get the updated bits."

  6787. msgstr ""

  6788. 

  6789. #: ../../../CHANGELOG.md:3678

  6790. msgid "2020-06-11"

  6791. msgstr ""

  6792. 

  6793. #: ../../../CHANGELOG.md:3680

  6794. msgid "SMS bridging requires db reset"

  6795. msgstr ""

  6796. 

  6797. #: ../../../CHANGELOG.md:3682

  6798. 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`."

  6799. msgstr ""

  6800. 

  6801. #: ../../../CHANGELOG.md:3684

  6802. 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."

  6803. msgstr ""

  6804. 

  6805. #: ../../../CHANGELOG.md:3686

  6806. msgid "2020-06-05"

  6807. msgstr ""

  6808. 

  6809. #: ../../../CHANGELOG.md:3688

  6810. msgid "SMS bridging support"

  6811. msgstr ""

  6812. 

  6813. #: ../../../CHANGELOG.md:3690

  6814. 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)."

  6815. msgstr ""

  6816. 

  6817. #: ../../../CHANGELOG.md:3692

  6818. msgid "See our [Setting up Matrix SMS bridging](docs/configuring-playbook-bridge-matrix-bridge-sms.md) documentation page for getting started."

  6819. msgstr ""

  6820. 

  6821. #: ../../../CHANGELOG.md:3695

  6822. msgid "2020-05-19"

  6823. msgstr ""

  6824. 

  6825. #: ../../../CHANGELOG.md:3697

  6826. msgid "(Compatibility Break / Security Issue) Disabling User Directory search powered by the ma1sd Identity Server"

  6827. msgstr ""

  6828. 

  6829. #: ../../../CHANGELOG.md:3701

  6830. 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."

  6831. msgstr ""

  6832. 

  6833. #: ../../../CHANGELOG.md:3703

  6834. 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**."

  6835. msgstr ""

  6836. 

  6837. #: ../../../CHANGELOG.md:3705

  6838. 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 }}\"`"

  6839. msgstr ""

  6840. 

  6841. #: ../../../CHANGELOG.md:3708

  6842. msgid "2020-04-28"

  6843. msgstr ""

  6844. 

  6845. #: ../../../CHANGELOG.md:3710

  6846. msgid "Newer IRC bridge (with potential breaking change)"

  6847. msgstr ""

  6848. 

  6849. #: ../../../CHANGELOG.md:3712

  6850. 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."

  6851. msgstr ""

  6852. 

  6853. #: ../../../CHANGELOG.md:3721

  6854. msgid "2020-04-23"

  6855. msgstr ""

  6856. 

  6857. #: ../../../CHANGELOG.md:3723

  6858. #: ../../../CHANGELOG.md:3954

  6859. msgid "Slack bridging support"

  6860. msgstr ""

  6861. 

  6862. #: ../../../CHANGELOG.md:3725

  6863. 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."

  6864. msgstr ""

  6865. 

  6866. #: ../../../CHANGELOG.md:3727

  6867. msgid "See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-bridge-mx-puppet-slack.md) documentation page for getting started."

  6868. msgstr ""

  6869. 

  6870. #: ../../../CHANGELOG.md:3730

  6871. msgid "2020-04-09"

  6872. msgstr ""

  6873. 

  6874. #: ../../../CHANGELOG.md:3732

  6875. msgid "Skype bridging support"

  6876. msgstr ""

  6877. 

  6878. #: ../../../CHANGELOG.md:3734

  6879. 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."

  6880. msgstr ""

  6881. 

  6882. #: ../../../CHANGELOG.md:3736

  6883. msgid "See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md) documentation page for getting started."

  6884. msgstr ""

  6885. 

  6886. #: ../../../CHANGELOG.md:3739

  6887. msgid "2020-04-05"

  6888. msgstr ""

  6889. 

  6890. #: ../../../CHANGELOG.md:3741

  6891. msgid "Private Jitsi support"

  6892. msgstr ""

  6893. 

  6894. #: ../../../CHANGELOG.md:3743

  6895. 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."

  6896. msgstr ""

  6897. 

  6898. #: ../../../CHANGELOG.md:3745

  6899. 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."

  6900. msgstr ""

  6901. 

  6902. #: ../../../CHANGELOG.md:3747

  6903. 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."

  6904. msgstr ""

  6905. 

  6906. #: ../../../CHANGELOG.md:3750

  6907. msgid "2020-04-03"

  6908. msgstr ""

  6909. 

  6910. #: ../../../CHANGELOG.md:3752

  6911. msgid "(Potential Backward Compatibility Break) ma1sd replaces mxisd"

  6912. msgstr ""

  6913. 

  6914. #: ../../../CHANGELOG.md:3754

  6915. 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."

  6916. msgstr ""

  6917. 

  6918. #: ../../../CHANGELOG.md:3756

  6919. 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."

  6920. msgstr ""

  6921. 

  6922. #: ../../../CHANGELOG.md:3758

  6923. 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."

  6924. msgstr ""

  6925. 

  6926. #: ../../../CHANGELOG.md:3761

  6927. msgid "2020-03-29"

  6928. msgstr ""

  6929. 

  6930. #: ../../../CHANGELOG.md:3763

  6931. msgid "Archlinux support"

  6932. msgstr ""

  6933. 

  6934. #: ../../../CHANGELOG.md:3765

  6935. msgid "Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts, the playbook now supports installing to an [Archlinux](https://www.archlinux.org/) server."

  6936. msgstr ""

  6937. 

  6938. #: ../../../CHANGELOG.md:3768

  6939. msgid "2020-03-24"

  6940. msgstr ""

  6941. 

  6942. #: ../../../CHANGELOG.md:3770

  6943. msgid "Jitsi support"

  6944. msgstr ""

  6945. 

  6946. #: ../../../CHANGELOG.md:3772

  6947. 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)."

  6948. msgstr ""

  6949. 

  6950. #: ../../../CHANGELOG.md:3774

  6951. msgid "See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to get started."

  6952. msgstr ""

  6953. 

  6954. #: ../../../CHANGELOG.md:3777

  6955. msgid "2020-03-15"

  6956. msgstr ""

  6957. 

  6958. #: ../../../CHANGELOG.md:3779

  6959. msgid "Raspberry Pi support"

  6960. msgstr ""

  6961. 

  6962. #: ../../../CHANGELOG.md:3781

  6963. 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."

  6964. msgstr ""

  6965. 

  6966. #: ../../../CHANGELOG.md:3783

  6967. 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."

  6968. msgstr ""

  6969. 

  6970. #: ../../../CHANGELOG.md:3786

  6971. msgid "2020-02-26"

  6972. msgstr ""

  6973. 

  6974. #: ../../../CHANGELOG.md:3788

  6975. msgid "Riot-web themes are here"

  6976. msgstr ""

  6977. 

  6978. #: ../../../CHANGELOG.md:3790

  6979. msgid "The playbook now makes it easy to install custom riot-web themes."

  6980. msgstr ""

  6981. 

  6982. #: ../../../CHANGELOG.md:3792

  6983. msgid "To learn more, take a look at our [riot-web documentation on Themes](docs/configuring-playbook-riot-web.md#themes)."

  6984. msgstr ""

  6985. 

  6986. #: ../../../CHANGELOG.md:3795

  6987. msgid "2020-02-24"

  6988. msgstr ""

  6989. 

  6990. #: ../../../CHANGELOG.md:3797

  6991. msgid "Customize the server name in Riot's login page"

  6992. msgstr ""

  6993. 

  6994. #: ../../../CHANGELOG.md:3799

  6995. msgid "You can now customize the server name string that Riot-web displays in its login page."

  6996. msgstr ""

  6997. 

  6998. #: ../../../CHANGELOG.md:3801

  6999. msgid "These playbook variables, with these default values, have been added:"

  7000. msgstr ""

  7001. 

  7002. #: ../../../CHANGELOG.md:3807

  7003. 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\"."

  7004. msgstr ""

  7005. 

  7006. #: ../../../CHANGELOG.md:3809

  7007. 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."

  7008. msgstr ""

  7009. 

  7010. #: ../../../CHANGELOG.md:3812

  7011. msgid "2020-01-30"

  7012. msgstr ""

  7013. 

  7014. #: ../../../CHANGELOG.md:3814

  7015. msgid "Disabling TLSv1.1"

  7016. msgstr ""

  7017. 

  7018. #: ../../../CHANGELOG.md:3816

  7019. msgid "To improve security, we've removed TLSv1.1 support from our default matrix-nginx-proxy configuration."

  7020. msgstr ""

  7021. 

  7022. #: ../../../CHANGELOG.md:3818

  7023. 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\"`"

  7024. msgstr ""

  7025. 

  7026. #: ../../../CHANGELOG.md:3821

  7027. msgid "2020-01-21"

  7028. msgstr ""

  7029. 

  7030. #: ../../../CHANGELOG.md:3823

  7031. msgid "Postgres collation changes (action required!)"

  7032. msgstr ""

  7033. 

  7034. #: ../../../CHANGELOG.md:3825

  7035. 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."

  7036. msgstr ""

  7037. 

  7038. #: ../../../CHANGELOG.md:3827

  7039. 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."

  7040. msgstr ""

  7041. 

  7042. #: ../../../CHANGELOG.md:3829

  7043. msgid "To avoid future problems, we recommend that you run the following command:"

  7044. msgstr ""

  7045. 

  7046. #: ../../../CHANGELOG.md:3835

  7047. 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."

  7048. msgstr ""

  7049. 

  7050. #: ../../../CHANGELOG.md:3838

  7051. msgid "2020-01-14"

  7052. msgstr ""

  7053. 

  7054. #: ../../../CHANGELOG.md:3840

  7055. msgid "Added support for Appservice Webhooks"

  7056. msgstr ""

  7057. 

  7058. #: ../../../CHANGELOG.md:3842

  7059. 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."

  7060. msgstr ""

  7061. 

  7062. #: ../../../CHANGELOG.md:3844

  7063. msgid "Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-playbook-bridge-appservice-webhooks.md)."

  7064. msgstr ""

  7065. 

  7066. #: ../../../CHANGELOG.md:3847

  7067. msgid "2020-01-12"

  7068. msgstr ""

  7069. 

  7070. #: ../../../CHANGELOG.md:3849

  7071. msgid "Added support for automatic Double Puppeting for all Mautrix bridges"

  7072. msgstr ""

  7073. 

  7074. #: ../../../CHANGELOG.md:3851

  7075. msgid "Double Puppeting can now be easily enabled for all Mautrix bridges supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)."

  7076. msgstr ""

  7077. 

  7078. #: ../../../CHANGELOG.md:3853

  7079. 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."

  7080. msgstr ""

  7081. 

  7082. #: ../../../CHANGELOG.md:3855

  7083. msgid "To get started, following the playbook's documentation for the bridge you'd like to configure."

  7084. msgstr ""

  7085. 

  7086. #: ../../../CHANGELOG.md:3858

  7087. msgid "2019-12-06"

  7088. msgstr ""

  7089. 

  7090. #: ../../../CHANGELOG.md:3860

  7091. msgid "Added support for an alternative method for using another webserver"

  7092. msgstr ""

  7093. 

  7094. #: ../../../CHANGELOG.md:3862

  7095. 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)."

  7096. msgstr ""

  7097. 

  7098. #: ../../../CHANGELOG.md:3864

  7099. 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))."

  7100. msgstr ""

  7101. 

  7102. #: ../../../CHANGELOG.md:3866

  7103. 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)."

  7104. msgstr ""

  7105. 

  7106. #: ../../../CHANGELOG.md:3869

  7107. msgid "2019-11-10"

  7108. msgstr ""

  7109. 

  7110. #: ../../../CHANGELOG.md:3871

  7111. msgid "Tightened security around room directory publishing"

  7112. msgstr ""

  7113. 

  7114. #: ../../../CHANGELOG.md:3873

  7115. 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."

  7116. msgstr ""

  7117. 

  7118. #: ../../../CHANGELOG.md:3875

  7119. 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**."

  7120. msgstr ""

  7121. 

  7122. #: ../../../CHANGELOG.md:3877

  7123. 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."

  7124. msgstr ""

  7125. 

  7126. #: ../../../CHANGELOG.md:3880

  7127. msgid "2019-10-05"

  7128. msgstr ""

  7129. 

  7130. #: ../../../CHANGELOG.md:3882

  7131. msgid "Improved Postgres upgrading/importing"

  7132. msgstr ""

  7133. 

  7134. #: ../../../CHANGELOG.md:3884

  7135. 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."

  7136. msgstr ""

  7137. 

  7138. #: ../../../CHANGELOG.md:3886

  7139. 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."

  7140. msgstr ""

  7141. 

  7142. #: ../../../CHANGELOG.md:3888

  7143. 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."

  7144. msgstr ""

  7145. 

  7146. #: ../../../CHANGELOG.md:3890

  7147. msgid "Additionally, Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) now uses gzipped dump files by default, to minimize disk space usage."

  7148. msgstr ""

  7149. 

  7150. #: ../../../CHANGELOG.md:3893

  7151. msgid "2019-10-04"

  7152. msgstr ""

  7153. 

  7154. #: ../../../CHANGELOG.md:3895

  7155. msgid "Postgres 12 support"

  7156. msgstr ""

  7157. 

  7158. #: ../../../CHANGELOG.md:3897

  7159. msgid "The playbook now installs [Postgres 12](https://www.postgresql.org/about/news/1976/) by default."

  7160. msgstr ""

  7161. 

  7162. #: ../../../CHANGELOG.md:3899

  7163. 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)."

  7164. msgstr ""

  7165. 

  7166. #: ../../../CHANGELOG.md:3902

  7167. msgid "2019-10-03"

  7168. msgstr ""

  7169. 

  7170. #: ../../../CHANGELOG.md:3904

  7171. msgid "Synapse 1.4.0"

  7172. msgstr ""

  7173. 

  7174. #: ../../../CHANGELOG.md:3906

  7175. 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."

  7176. msgstr ""

  7177. 

  7178. #: ../../../CHANGELOG.md:3908

  7179. 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: ~`)."

  7180. msgstr ""

  7181. 

  7182. #: ../../../CHANGELOG.md:3910

  7183. 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."

  7184. msgstr ""

  7185. 

  7186. #: ../../../CHANGELOG.md:3912

  7187. 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."

  7188. msgstr ""

  7189. 

  7190. #: ../../../CHANGELOG.md:3915

  7191. msgid "2019-09-09"

  7192. msgstr ""

  7193. 

  7194. #: ../../../CHANGELOG.md:3917

  7195. msgid "Synapse Simple Antispam support"

  7196. msgstr ""

  7197. 

  7198. #: ../../../CHANGELOG.md:3919

  7199. 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."

  7200. msgstr ""

  7201. 

  7202. #: ../../../CHANGELOG.md:3921

  7203. msgid "From now on, you can easily install and configure this spam checker module through the playbook."

  7204. msgstr ""

  7205. 

  7206. #: ../../../CHANGELOG.md:3923

  7207. msgid "Learn more in [Setting up Synapse Simple Antispam](docs/configuring-playbook-synapse-simple-antispam.md)."

  7208. msgstr ""

  7209. 

  7210. #: ../../../CHANGELOG.md:3926

  7211. msgid "2019-08-25"

  7212. msgstr ""

  7213. 

  7214. #: ../../../CHANGELOG.md:3928

  7215. msgid "Extensible Riot-web configuration"

  7216. msgstr ""

  7217. 

  7218. #: ../../../CHANGELOG.md:3930

  7219. msgid "Similarly to [Extensible Synapse configuration](#extensible-synapse-configuration) (below), Riot-web configuration is also extensible now."

  7220. msgstr ""

  7221. 

  7222. #: ../../../CHANGELOG.md:3932

  7223. 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."

  7224. msgstr ""

  7225. 

  7226. #: ../../../CHANGELOG.md:3934

  7227. 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."

  7228. msgstr ""

  7229. 

  7230. #: ../../../CHANGELOG.md:3936

  7231. msgid "Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-web.md)."

  7232. msgstr ""

  7233. 

  7234. #: ../../../CHANGELOG.md:3939

  7235. msgid "2019-08-22"

  7236. msgstr ""

  7237. 

  7238. #: ../../../CHANGELOG.md:3941

  7239. msgid "Extensible Synapse configuration"

  7240. msgstr ""

  7241. 

  7242. #: ../../../CHANGELOG.md:3943

  7243. 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."

  7244. msgstr ""

  7245. 

  7246. #: ../../../CHANGELOG.md:3945

  7247. 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."

  7248. msgstr ""

  7249. 

  7250. #: ../../../CHANGELOG.md:3947

  7251. 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."

  7252. msgstr ""

  7253. 

  7254. #: ../../../CHANGELOG.md:3949

  7255. msgid "Learn more here in [Configuring Synapse](docs/configuring-playbook-synapse.md)."

  7256. msgstr ""

  7257. 

  7258. #: ../../../CHANGELOG.md:3952

  7259. msgid "2019-08-21"

  7260. msgstr ""

  7261. 

  7262. #: ../../../CHANGELOG.md:3956

  7263. 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."

  7264. msgstr ""

  7265. 

  7266. #: ../../../CHANGELOG.md:3958

  7267. msgid "Additional details are available in [Setting up Appservice Slack bridging](docs/configuring-playbook-bridge-appservice-slack.md)."

  7268. msgstr ""

  7269. 

  7270. #: ../../../CHANGELOG.md:3960

  7271. msgid "Google Hangouts bridging support"

  7272. msgstr ""

  7273. 

  7274. #: ../../../CHANGELOG.md:3962

  7275. 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."

  7276. msgstr ""

  7277. 

  7278. #: ../../../CHANGELOG.md:3964

  7279. msgid "Additional details are available in [Setting up Mautrix Hangouts bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)."

  7280. msgstr ""

  7281. 

  7282. #: ../../../CHANGELOG.md:3967

  7283. msgid "2019-08-05"

  7284. msgstr ""

  7285. 

  7286. #: ../../../CHANGELOG.md:3969

  7287. msgid "Email2Matrix support"

  7288. msgstr ""

  7289. 

  7290. #: ../../../CHANGELOG.md:3971

  7291. msgid "Support for [Email2Matrix](https://github.com/devture/email2matrix) has been added."

  7292. msgstr ""

  7293. 

  7294. #: ../../../CHANGELOG.md:3973

  7295. msgid "It's an optional feature that you can enable via the playbook."

  7296. msgstr ""

  7297. 

  7298. #: ../../../CHANGELOG.md:3975

  7299. msgid "To learn more, see the [playbook's documentation on Email2Matrix](./docs/configuring-playbook-email2matrix.md)."

  7300. msgstr ""

  7301. 

  7302. #: ../../../CHANGELOG.md:3978

  7303. msgid "2019-08-03"

  7304. msgstr ""

  7305. 

  7306. #: ../../../CHANGELOG.md:3980

  7307. msgid "Synapse logging level has been reduced to WARNING"

  7308. msgstr ""

  7309. 

  7310. #: ../../../CHANGELOG.md:3982

  7311. 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`."

  7312. msgstr ""

  7313. 

  7314. #: ../../../CHANGELOG.md:3984

  7315. msgid "This greatly reduces the number of log messages that are being logged, leading to:"

  7316. msgstr ""

  7317. 

  7318. #: ../../../CHANGELOG.md:3986

  7319. msgid "much less disk space dedicated to Synapse and thus, logs kept for longer"

  7320. msgstr ""

  7321. 

  7322. #: ../../../CHANGELOG.md:3987

  7323. msgid "easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages, as they're not longer buried in thousands of non-important `INFO` messages"

  7324. msgstr ""

  7325. 

  7326. #: ../../../CHANGELOG.md:3989

  7327. 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)."

  7328. msgstr ""

  7329. 

  7330. #: ../../../CHANGELOG.md:3992

  7331. msgid "2019-07-08"

  7332. msgstr ""

  7333. 

  7334. #: ../../../CHANGELOG.md:3994

  7335. msgid "Synapse Maintenance docs and synapse-janitor support are available"

  7336. msgstr ""

  7337. 

  7338. #: ../../../CHANGELOG.md:3996

  7339. msgid "The playbook can now help you with Synapse's maintenance."

  7340. msgstr ""

  7341. 

  7342. #: ../../../CHANGELOG.md:3998

  7343. 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)."

  7344. msgstr ""

  7345. 

  7346. #: ../../../CHANGELOG.md:4000

  7347. 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."

  7348. msgstr ""

  7349. 

  7350. #: ../../../CHANGELOG.md:4002

  7351. msgid "(BC Break) Rename run control variables"

  7352. msgstr ""

  7353. 

  7354. #: ../../../CHANGELOG.md:4004

  7355. msgid "Some internal playbook control variables have been renamed."

  7356. msgstr ""

  7357. 

  7358. #: ../../../CHANGELOG.md:4006

  7359. 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."

  7360. msgstr ""

  7361. 

  7362. #: ../../../CHANGELOG.md:4008

  7363. msgid "The following variables have been renamed:"

  7364. msgstr ""

  7365. 

  7366. #: ../../../CHANGELOG.md:4010

  7367. msgid "from `run_import_postgres` to `run_postgres_import`"

  7368. msgstr ""

  7369. 

  7370. #: ../../../CHANGELOG.md:4011

  7371. msgid "from `run_import_sqlite_db` to `run_postgres_import_sqlite_db`"

  7372. msgstr ""

  7373. 

  7374. #: ../../../CHANGELOG.md:4012

  7375. msgid "from `run_upgrade_postgres` to `run_postgres_upgrade`"

  7376. msgstr ""

  7377. 

  7378. #: ../../../CHANGELOG.md:4013

  7379. msgid "from `run_import_media_store` to `run_synapse_import_media_store`"

  7380. msgstr ""

  7381. 

  7382. #: ../../../CHANGELOG.md:4014

  7383. msgid "from `run_register_user` to `run_synapse_register_user`"

  7384. msgstr ""

  7385. 

  7386. #: ../../../CHANGELOG.md:4015

  7387. msgid "from `run_update_user_password` to `run_synapse_update_user_password`"

  7388. msgstr ""

  7389. 

  7390. #: ../../../CHANGELOG.md:4018

  7391. msgid "2019-07-04"

  7392. msgstr ""

  7393. 

  7394. #: ../../../CHANGELOG.md:4020

  7395. msgid "Synapse no longer logs to text files"

  7396. msgstr ""

  7397. 

  7398. #: ../../../CHANGELOG.md:4022

  7399. 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*`)."

  7400. msgstr ""

  7401. 

  7402. #: ../../../CHANGELOG.md:4024

  7403. 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`"

  7404. msgstr ""

  7405. 

  7406. #: ../../../CHANGELOG.md:4026

  7407. msgid "Because of this, the following variables have become obsolete and were removed:"

  7408. msgstr ""

  7409. 

  7410. #: ../../../CHANGELOG.md:4028

  7411. msgid "`matrix_synapse_max_log_file_size_mb`"

  7412. msgstr ""

  7413. 

  7414. #: ../../../CHANGELOG.md:4029

  7415. msgid "`matrix_synapse_max_log_files_count`"

  7416. msgstr ""

  7417. 

  7418. #: ../../../CHANGELOG.md:4031

  7419. 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*`)."

  7420. msgstr ""

  7421. 

  7422. #: ../../../CHANGELOG.md:4033

  7423. 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`)."

  7424. msgstr ""

  7425. 

  7426. #: ../../../CHANGELOG.md:4036

  7427. msgid "2019-06-27"

  7428. msgstr ""

  7429. 

  7430. #: ../../../CHANGELOG.md:4038

  7431. msgid "(BC Break) Discord bridge configuration is now entirely managed by the playbook"

  7432. msgstr ""

  7433. 

  7434. #: ../../../CHANGELOG.md:4040

  7435. 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."

  7436. msgstr ""

  7437. 

  7438. #: ../../../CHANGELOG.md:4042

  7439. msgid "From now on, the playbook will keep both configuration files sync for you."

  7440. msgstr ""

  7441. 

  7442. #: ../../../CHANGELOG.md:4044

  7443. 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."

  7444. msgstr ""

  7445. 

  7446. #: ../../../CHANGELOG.md:4046

  7447. msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-discord/config`)."

  7448. msgstr ""

  7449. 

  7450. #: ../../../CHANGELOG.md:4048

  7451. 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`)."

  7452. msgstr ""

  7453. 

  7454. #: ../../../CHANGELOG.md:4050

  7455. 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."

  7456. msgstr ""

  7457. 

  7458. #: ../../../CHANGELOG.md:4052

  7459. 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`."

  7460. msgstr ""

  7461. 

  7462. #: ../../../CHANGELOG.md:4055

  7463. msgid "2019-06-24"

  7464. msgstr ""

  7465. 

  7466. #: ../../../CHANGELOG.md:4057

  7467. msgid "(BC Break) WhatsApp bridge configuration is now entirely managed by the playbook"

  7468. msgstr ""

  7469. 

  7470. #: ../../../CHANGELOG.md:4059

  7471. 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."

  7472. msgstr ""

  7473. 

  7474. #: ../../../CHANGELOG.md:4061

  7475. #: ../../../CHANGELOG.md:4078

  7476. #: ../../../CHANGELOG.md:4097

  7477. #: ../../../CHANGELOG.md:4136

  7478. msgid "From now on, the playbook will keep the configuration in sync for you."

  7479. msgstr ""

  7480. 

  7481. #: ../../../CHANGELOG.md:4063

  7482. 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."

  7483. msgstr ""

  7484. 

  7485. #: ../../../CHANGELOG.md:4065

  7486. 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."

  7487. msgstr ""

  7488. 

  7489. #: ../../../CHANGELOG.md:4067

  7490. 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`)."

  7491. msgstr ""

  7492. 

  7493. #: ../../../CHANGELOG.md:4069

  7494. msgid "We're now following the default configuration for the WhatsApp bridge."

  7495. msgstr ""

  7496. 

  7497. #: ../../../CHANGELOG.md:4072

  7498. msgid "2019-06-20"

  7499. msgstr ""

  7500. 

  7501. #: ../../../CHANGELOG.md:4074

  7502. msgid "(BC Break) IRC bridge configuration is now entirely managed by the playbook"

  7503. msgstr ""

  7504. 

  7505. #: ../../../CHANGELOG.md:4076

  7506. 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."

  7507. msgstr ""

  7508. 

  7509. #: ../../../CHANGELOG.md:4080

  7510. 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."

  7511. msgstr ""

  7512. 

  7513. #: ../../../CHANGELOG.md:4082

  7514. 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`)."

  7515. msgstr ""

  7516. 

  7517. #: ../../../CHANGELOG.md:4084

  7518. 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."

  7519. msgstr ""

  7520. 

  7521. #: ../../../CHANGELOG.md:4086

  7522. 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`."

  7523. msgstr ""

  7524. 

  7525. #: ../../../CHANGELOG.md:4088

  7526. 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`)."

  7527. msgstr ""

  7528. 

  7529. #: ../../../CHANGELOG.md:4091

  7530. msgid "2019-06-15"

  7531. msgstr ""

  7532. 

  7533. #: ../../../CHANGELOG.md:4093

  7534. msgid "(BC Break) Telegram bridge configuration is now entirely managed by the playbook"

  7535. msgstr ""

  7536. 

  7537. #: ../../../CHANGELOG.md:4095

  7538. 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."

  7539. msgstr ""

  7540. 

  7541. #: ../../../CHANGELOG.md:4099

  7542. 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."

  7543. msgstr ""

  7544. 

  7545. #: ../../../CHANGELOG.md:4101

  7546. 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."

  7547. msgstr ""

  7548. 

  7549. #: ../../../CHANGELOG.md:4103

  7550. 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`)."

  7551. msgstr ""

  7552. 

  7553. #: ../../../CHANGELOG.md:4105

  7554. msgid "Also, we're now following the default configuration for the Telegram bridge, so some default configuration values are different:"

  7555. msgstr ""

  7556. 

  7557. #: ../../../CHANGELOG.md:4107

  7558. 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"

  7559. msgstr ""

  7560. 

  7561. #: ../../../CHANGELOG.md:4108

  7562. 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."

  7563. msgstr ""

  7564. 

  7565. #: ../../../CHANGELOG.md:4109

  7566. msgid "`authless_portals` (used to be `false`, now `true`) — creating portals from the Telegram side is now possible"

  7567. msgstr ""

  7568. 

  7569. #: ../../../CHANGELOG.md:4110

  7570. msgid "`whitelist_group_admins` (used to be `false`, now `true`) — allows Telegram group admins to use the bot commands"

  7571. msgstr ""

  7572. 

  7573. #: ../../../CHANGELOG.md:4112

  7574. 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)."

  7575. msgstr ""

  7576. 

  7577. #: ../../../CHANGELOG.md:4115

  7578. msgid "2019-06-12"

  7579. msgstr ""

  7580. 

  7581. #: ../../../CHANGELOG.md:4117

  7582. msgid "Synapse v1.0"

  7583. msgstr ""

  7584. 

  7585. #: ../../../CHANGELOG.md:4119

  7586. 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)."

  7587. msgstr ""

  7588. 

  7589. #: ../../../CHANGELOG.md:4121

  7590. 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."

  7591. msgstr ""

  7592. 

  7593. #: ../../../CHANGELOG.md:4123

  7594. msgid "**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` DNS SRV records. The latter, **must not** be removed."

  7595. msgstr ""

  7596. 

  7597. #: ../../../CHANGELOG.md:4125

  7598. 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."

  7599. msgstr ""

  7600. 

  7601. #: ../../../CHANGELOG.md:4127

  7602. 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)."

  7603. msgstr ""

  7604. 

  7605. #: ../../../CHANGELOG.md:4130

  7606. msgid "2019-06-07"

  7607. msgstr ""

  7608. 

  7609. #: ../../../CHANGELOG.md:4132

  7610. msgid "(BC Break) Facebook bridge configuration is now entirely managed by the playbook"

  7611. msgstr ""

  7612. 

  7613. #: ../../../CHANGELOG.md:4134

  7614. 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."

  7615. msgstr ""

  7616. 

  7617. #: ../../../CHANGELOG.md:4138

  7618. 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."

  7619. msgstr ""

  7620. 

  7621. #: ../../../CHANGELOG.md:4140

  7622. 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."

  7623. msgstr ""

  7624. 

  7625. #: ../../../CHANGELOG.md:4142

  7626. 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`)."

  7627. msgstr ""

  7628. 

  7629. #: ../../../CHANGELOG.md:4145

  7630. msgid "2019-05-25"

  7631. msgstr ""

  7632. 

  7633. #: ../../../CHANGELOG.md:4147

  7634. msgid "Support for exposing container ports publicly (not just to the host)"

  7635. msgstr ""

  7636. 

  7637. #: ../../../CHANGELOG.md:4149

  7638. 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."

  7639. msgstr ""

  7640. 

  7641. #: ../../../CHANGELOG.md:4151

  7642. 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`."

  7643. msgstr ""

  7644. 

  7645. #: ../../../CHANGELOG.md:4153

  7646. msgid "All such variables have been superseded by a better (more flexible) way to do it."

  7647. msgstr ""

  7648. 

  7649. #: ../../../CHANGELOG.md:4155

  7650. msgid "**Most** people (including those not using `matrix-nginx-proxy`), **don't need** to bother with this."

  7651. msgstr ""

  7652. 

  7653. #: ../../../CHANGELOG.md:4157

  7654. msgid "Porting examples follow for people having more customized setups:"

  7655. msgstr ""

  7656. 

  7657. #: ../../../CHANGELOG.md:4159

  7658. msgid "**from** `matrix_synapse_container_expose_client_api_port: true` **to** `matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`"

  7659. msgstr ""

  7660. 

  7661. #: ../../../CHANGELOG.md:4161

  7662. 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'`"

  7663. msgstr ""

  7664. 

  7665. #: ../../../CHANGELOG.md:4163

  7666. msgid "**from** `matrix_synapse_container_expose_metrics_port: true` **to** `matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`"

  7667. msgstr ""

  7668. 

  7669. #: ../../../CHANGELOG.md:4165

  7670. msgid "**from** `matrix_riot_web_container_expose_port: true` **to** `matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`"

  7671. msgstr ""

  7672. 

  7673. #: ../../../CHANGELOG.md:4167

  7674. msgid "**from** `matrix_mxisd_container_expose_port: true` **to** `matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`"

  7675. msgstr ""

  7676. 

  7677. #: ../../../CHANGELOG.md:4169

  7678. msgid "**from** `matrix_dimension_container_expose_port: true` **to** `matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`"

  7679. msgstr ""

  7680. 

  7681. #: ../../../CHANGELOG.md:4171

  7682. 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'`"

  7683. msgstr ""

  7684. 

  7685. #: ../../../CHANGELOG.md:4173

  7686. 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'`"

  7687. msgstr ""

  7688. 

  7689. #: ../../../CHANGELOG.md:4175

  7690. 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'`"

  7691. msgstr ""

  7692. 

  7693. #: ../../../CHANGELOG.md:4177

  7694. msgid "As always, if you forget to remove usage of some outdated variable, the playbook will warn you."

  7695. msgstr ""

  7696. 

  7697. #: ../../../CHANGELOG.md:4180

  7698. msgid "2019-05-23"

  7699. msgstr ""

  7700. 

  7701. #: ../../../CHANGELOG.md:4182

  7702. msgid "(BC Break) Ansible 2.8 compatibility"

  7703. msgstr ""

  7704. 

  7705. #: ../../../CHANGELOG.md:4184

  7706. 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)."

  7707. msgstr ""

  7708. 

  7709. #: ../../../CHANGELOG.md:4186

  7710. msgid "A manual change is required to the `inventory/hosts` file, changing the group name from `matrix-servers` to `matrix_servers` (dash to underscore)."

  7711. msgstr ""

  7712. 

  7713. #: ../../../CHANGELOG.md:4188

  7714. msgid "To avoid doing it manually, run this:"

  7715. msgstr ""

  7716. 

  7717. #: ../../../CHANGELOG.md:4189

  7718. msgid "Linux: `sed -i 's/matrix-servers/matrix_servers/g' inventory/hosts`"

  7719. msgstr ""

  7720. 

  7721. #: ../../../CHANGELOG.md:4190

  7722. msgid "Mac: `sed -i '' 's/matrix-servers/matrix_servers/g' inventory/hosts`"

  7723. msgstr ""

  7724. 

  7725. #: ../../../CHANGELOG.md:4193

  7726. msgid "2019-05-21"

  7727. msgstr ""

  7728. 

  7729. #: ../../../CHANGELOG.md:4195

  7730. msgid "Synapse no longer required"

  7731. msgstr ""

  7732. 

  7733. #: ../../../CHANGELOG.md:4197

  7734. msgid "The playbook no longer insists on installing [Synapse](https://github.com/element-hq/synapse) via the `matrix-synapse` role."

  7735. msgstr ""

  7736. 

  7737. #: ../../../CHANGELOG.md:4199

  7738. 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`)."

  7739. msgstr ""

  7740. 

  7741. #: ../../../CHANGELOG.md:4201

  7742. 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."

  7743. msgstr ""

  7744. 

  7745. #: ../../../CHANGELOG.md:4203

  7746. msgid "Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers."

  7747. msgstr ""

  7748. 

  7749. #: ../../../CHANGELOG.md:4205

  7750. msgid "Bridges are now separate from the Synapse role"

  7751. msgstr ""

  7752. 

  7753. #: ../../../CHANGELOG.md:4207

  7754. msgid "Bridges are no longer part of the `matrix-synapse` role. Each bridge now lives in its own separate role (`roles/custom/matrix-bridge-*`)."

  7755. msgstr ""

  7756. 

  7757. #: ../../../CHANGELOG.md:4209

  7758. 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)."

  7759. msgstr ""

  7760. 

  7761. #: ../../../CHANGELOG.md:4211

  7762. msgid "Renaming inconsistently-named Synapse variables"

  7763. msgstr ""

  7764. 

  7765. #: ../../../CHANGELOG.md:4213

  7766. msgid "For better consistency, the following variables have been renamed:"

  7767. msgstr ""

  7768. 

  7769. #: ../../../CHANGELOG.md:4215

  7770. msgid "`matrix_enable_room_list_search` was renamed to `matrix_synapse_enable_room_list_search`"

  7771. msgstr ""

  7772. 

  7773. #: ../../../CHANGELOG.md:4216

  7774. msgid "`matrix_alias_creation_rules` was renamed to `matrix_synapse_alias_creation_rules`"

  7775. msgstr ""

  7776. 

  7777. #: ../../../CHANGELOG.md:4217

  7778. msgid "`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was renamed to `matrix_synapse_room_list_publication_rules`"

  7779. msgstr ""

  7780. 

  7781. #: ../../../CHANGELOG.md:4220

  7782. msgid "2019-05-09"

  7783. msgstr ""

  7784. 

  7785. #: ../../../CHANGELOG.md:4222

  7786. msgid "Besides a myriad of bug fixes and minor improvements, here are the more notable (bigger) features we can announce today."

  7787. msgstr ""

  7788. 

  7789. #: ../../../CHANGELOG.md:4224

  7790. msgid "Mautrix Facebook/Messenger bridging support"

  7791. msgstr ""

  7792. 

  7793. #: ../../../CHANGELOG.md:4226

  7794. 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)."

  7795. msgstr ""

  7796. 

  7797. #: ../../../CHANGELOG.md:4228

  7798. msgid "Additional details are available in [Setting up Mautrix Facebook bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)."

  7799. msgstr ""

  7800. 

  7801. #: ../../../CHANGELOG.md:4230

  7802. msgid "mxisd Registration feature integration"

  7803. msgstr ""

  7804. 

  7805. #: ../../../CHANGELOG.md:4232

  7806. 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."

  7807. msgstr ""

  7808. 

  7809. #: ../../../CHANGELOG.md:4234

  7810. msgid "Learn more in [mxisd-controlled Registration](docs/configuring-playbook-mxisd.md#mxisd-controlled-registration)."

  7811. msgstr ""

  7812. 

  7813. #: ../../../CHANGELOG.md:4237

  7814. msgid "2019-04-16"

  7815. msgstr ""

  7816. 

  7817. #: ../../../CHANGELOG.md:4239

  7818. msgid "Caddy webserver examples"

  7819. msgstr ""

  7820. 

  7821. #: ../../../CHANGELOG.md:4241

  7822. 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"

  7823. msgstr ""

  7824. 

  7825. #: ../../../CHANGELOG.md:4243

  7826. msgid "2019-04-10"

  7827. msgstr ""

  7828. 

  7829. #: ../../../CHANGELOG.md:4245

  7830. msgid "Goofys support for other S3-compatible object stores"

  7831. msgstr ""

  7832. 

  7833. #: ../../../CHANGELOG.md:4247

  7834. 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),"

  7835. msgstr ""

  7836. 

  7837. #: ../../../CHANGELOG.md:4250

  7838. msgid "2019-04-03"

  7839. msgstr ""

  7840. 

  7841. #: ../../../CHANGELOG.md:4252

  7842. msgid "Ansible >= 2.5 is required"

  7843. msgstr ""

  7844. 

  7845. #: ../../../CHANGELOG.md:4254

  7846. 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)."

  7847. msgstr ""

  7848. 

  7849. #: ../../../CHANGELOG.md:4256

  7850. 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))."

  7851. msgstr ""

  7852. 

  7853. #: ../../../CHANGELOG.md:4259

  7854. msgid "2019-03-19"

  7855. msgstr ""

  7856. 

  7857. #: ../../../CHANGELOG.md:4261

  7858. msgid "TLS support for coturn"

  7859. msgstr ""

  7860. 

  7861. #: ../../../CHANGELOG.md:4263

  7862. 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."

  7863. msgstr ""

  7864. 

  7865. #: ../../../CHANGELOG.md:4265

  7866. 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:"

  7867. msgstr ""

  7868. 

  7869. #: ../../../CHANGELOG.md:4271

  7870. 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)."

  7871. msgstr ""

  7872. 

  7873. #: ../../../CHANGELOG.md:4273

  7874. msgid "People who build their own custom playbook from our roles should be aware that:"

  7875. msgstr ""

  7876. 

  7877. #: ../../../CHANGELOG.md:4275

  7878. 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)."

  7879. msgstr ""

  7880. 

  7881. #: ../../../CHANGELOG.md:4277

  7882. 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)."

  7883. msgstr ""

  7884. 

  7885. #: ../../../CHANGELOG.md:4280

  7886. msgid "2019-03-12"

  7887. msgstr ""

  7888. 

  7889. #: ../../../CHANGELOG.md:4282

  7890. msgid "matrix-nginx-proxy support for serving the base domain"

  7891. msgstr ""

  7892. 

  7893. #: ../../../CHANGELOG.md:4284

  7894. 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."

  7895. msgstr ""

  7896. 

  7897. #: ../../../CHANGELOG.md:4286

  7898. 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."

  7899. msgstr ""

  7900. 

  7901. #: ../../../CHANGELOG.md:4288

  7902. msgid "(BC break) matrix-nginx-proxy data variable renamed"

  7903. msgstr ""

  7904. 

  7905. #: ../../../CHANGELOG.md:4290

  7906. msgid "`matrix_nginx_proxy_data_path` was renamed to `matrix_nginx_proxy_base_path`."

  7907. msgstr ""

  7908. 

  7909. #: ../../../CHANGELOG.md:4292

  7910. 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)."

  7911. msgstr ""

  7912. 

  7913. #: ../../../CHANGELOG.md:4295

  7914. msgid "2019-03-10"

  7915. msgstr ""

  7916. 

  7917. #: ../../../CHANGELOG.md:4297

  7918. msgid "Dimension integration manager support"

  7919. msgstr ""

  7920. 

  7921. #: ../../../CHANGELOG.md:4299

  7922. 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."

  7923. msgstr ""

  7924. 

  7925. #: ../../../CHANGELOG.md:4302

  7926. msgid "2019-03-07"

  7927. msgstr ""

  7928. 

  7929. #: ../../../CHANGELOG.md:4304

  7930. msgid "Ability to customize mxisd's email templates"

  7931. msgstr ""

  7932. 

  7933. #: ../../../CHANGELOG.md:4306

  7934. 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."

  7935. msgstr ""

  7936. 

  7937. #: ../../../CHANGELOG.md:4309

  7938. msgid "2019-03-05"

  7939. msgstr ""

  7940. 

  7941. #: ../../../CHANGELOG.md:4311

  7942. msgid "Discord bridging support"

  7943. msgstr ""

  7944. 

  7945. #: ../../../CHANGELOG.md:4313

  7946. 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."

  7947. msgstr ""

  7948. 

  7949. #: ../../../CHANGELOG.md:4316

  7950. msgid "2019-02-19"

  7951. msgstr ""

  7952. 

  7953. #: ../../../CHANGELOG.md:4318

  7954. msgid "Renaming variables"

  7955. msgstr ""

  7956. 

  7957. #: ../../../CHANGELOG.md:4320

  7958. #: ../../../CHANGELOG.md:4637

  7959. #: ../../../CHANGELOG.md:4722

  7960. #: ../../../CHANGELOG.md:4842

  7961. msgid "The following playbook variables were renamed:"

  7962. msgstr ""

  7963. 

  7964. #: ../../../CHANGELOG.md:4322

  7965. msgid "from `host_specific_hostname_identity` to `matrix_domain`"

  7966. msgstr ""

  7967. 

  7968. #: ../../../CHANGELOG.md:4323

  7969. msgid "from `hostname_identity` to `matrix_domain`"

  7970. msgstr ""

  7971. 

  7972. #: ../../../CHANGELOG.md:4324

  7973. msgid "from `hostname_matrix` to `matrix_server_fqn_matrix`"

  7974. msgstr ""

  7975. 

  7976. #: ../../../CHANGELOG.md:4325

  7977. msgid "from `hostname_riot` to `matrix_server_fqn_riot`"

  7978. msgstr ""

  7979. 

  7980. #: ../../../CHANGELOG.md:4326

  7981. msgid "from `host_specific_matrix_ssl_lets_encrypt_support_email` to `matrix_ssl_lets_encrypt_support_email`"

  7982. msgstr ""

  7983. 

  7984. #: ../../../CHANGELOG.md:4328

  7985. msgid "Doing that, we've simplified things, made names less confusing (hopefully) and moved all variable names under the `matrix_` prefix."

  7986. msgstr ""

  7987. 

  7988. #: ../../../CHANGELOG.md:4331

  7989. msgid "2019-02-16"

  7990. msgstr ""

  7991. 

  7992. #: ../../../CHANGELOG.md:4333

  7993. msgid "Riot v1.0.1 support"

  7994. msgstr ""

  7995. 

  7996. #: ../../../CHANGELOG.md:4335

  7997. msgid "You can now use the brand new and redesigned Riot."

  7998. msgstr ""

  7999. 

  8000. #: ../../../CHANGELOG.md:4337

  8001. msgid "The new version no longer has a homepage by default, so we've also removed the custom homepage that we've been installing."

  8002. msgstr ""

  8003. 

  8004. #: ../../../CHANGELOG.md:4339

  8005. 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)."

  8006. msgstr ""

  8007. 

  8008. #: ../../../CHANGELOG.md:4342

  8009. msgid "2019-02-14"

  8010. msgstr ""

  8011. 

  8012. #: ../../../CHANGELOG.md:4344

  8013. msgid "Synapse v0.99.1"

  8014. msgstr ""

  8015. 

  8016. #: ../../../CHANGELOG.md:4346

  8017. 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."

  8018. msgstr ""

  8019. 

  8020. #: ../../../CHANGELOG.md:4348

  8021. 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."

  8022. msgstr ""

  8023. 

  8024. #: ../../../CHANGELOG.md:4351

  8025. msgid "2019-02-06"

  8026. msgstr ""

  8027. 

  8028. #: ../../../CHANGELOG.md:4353

  8029. msgid "Synapse v0.99 support and preparation for Synapse v1.0"

  8030. msgstr ""

  8031. 

  8032. #: ../../../CHANGELOG.md:4355

  8033. 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."

  8034. msgstr ""

  8035. 

  8036. #: ../../../CHANGELOG.md:4357

  8037. 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))."

  8038. msgstr ""

  8039. 

  8040. #: ../../../CHANGELOG.md:4359

  8041. 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)."

  8042. msgstr ""

  8043. 

  8044. #: ../../../CHANGELOG.md:4361

  8045. 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:"

  8046. msgstr ""

  8047. 

  8048. #: ../../../CHANGELOG.md:4363

  8049. 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."

  8050. msgstr ""

  8051. 

  8052. #: ../../../CHANGELOG.md:4365

  8053. 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)."

  8054. msgstr ""

  8055. 

  8056. #: ../../../CHANGELOG.md:4368

  8057. msgid "2019-02-01"

  8058. msgstr ""

  8059. 

  8060. #: ../../../CHANGELOG.md:4370

  8061. msgid "TLS v1.3 support"

  8062. msgstr ""

  8063. 

  8064. #: ../../../CHANGELOG.md:4372

  8065. 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."

  8066. msgstr ""

  8067. 

  8068. #: ../../../CHANGELOG.md:4374

  8069. msgid "When using:"

  8070. msgstr ""

  8071. 

  8072. #: ../../../CHANGELOG.md:4376

  8073. 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`."

  8074. msgstr ""

  8075. 

  8076. #: ../../../CHANGELOG.md:4378

  8077. 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)"

  8078. msgstr ""

  8079. 

  8080. #: ../../../CHANGELOG.md:4380

  8081. msgid "**another web server**: you don't need to do anything to accommodate this change"

  8082. msgstr ""

  8083. 

  8084. #: ../../../CHANGELOG.md:4383

  8085. msgid "2019-01-31"

  8086. msgstr ""

  8087. 

  8088. #: ../../../CHANGELOG.md:4385

  8089. msgid "IRC bridging support"

  8090. msgstr ""

  8091. 

  8092. #: ../../../CHANGELOG.md:4387

  8093. 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."

  8094. msgstr ""

  8095. 

  8096. #: ../../../CHANGELOG.md:4390

  8097. msgid "2019-01-29"

  8098. msgstr ""

  8099. 

  8100. #: ../../../CHANGELOG.md:4392

  8101. msgid "Running container processes as non-root, without capabilities and read-only"

  8102. msgstr ""

  8103. 

  8104. #: ../../../CHANGELOG.md:4394

  8105. 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."

  8106. msgstr ""

  8107. 

  8108. #: ../../../CHANGELOG.md:4396

  8109. 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."

  8110. msgstr ""

  8111. 

  8112. #: ../../../CHANGELOG.md:4398

  8113. 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."

  8114. msgstr ""

  8115. 

  8116. #: ../../../CHANGELOG.md:4400

  8117. 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."

  8118. msgstr ""

  8119. 

  8120. #: ../../../CHANGELOG.md:4402

  8121. msgid "matrix-mailer is now based on Exim, not Postfix"

  8122. msgstr ""

  8123. 

  8124. #: ../../../CHANGELOG.md:4404

  8125. 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)."

  8126. msgstr ""

  8127. 

  8128. #: ../../../CHANGELOG.md:4406

  8129. 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`)."

  8130. msgstr ""

  8131. 

  8132. #: ../../../CHANGELOG.md:4408

  8133. 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)."

  8134. msgstr ""

  8135. 

  8136. #: ../../../CHANGELOG.md:4411

  8137. msgid "2019-01-17"

  8138. msgstr ""

  8139. 

  8140. #: ../../../CHANGELOG.md:4413

  8141. msgid "(BC Break) Making the playbook's roles more independent of one another"

  8142. msgstr ""

  8143. 

  8144. #: ../../../CHANGELOG.md:4415

  8145. 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)."

  8146. msgstr ""

  8147. 

  8148. #: ../../../CHANGELOG.md:4418

  8149. 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."

  8150. msgstr ""

  8151. 

  8152. #: ../../../CHANGELOG.md:4420

  8153. msgid "With the new changes, **all roles are now only dependent on the minimal `matrix-base` role**. They are no longer dependent among themselves."

  8154. msgstr ""

  8155. 

  8156. #: ../../../CHANGELOG.md:4422

  8157. msgid "In addition, the following components can now be completely disabled (for those who want/need to):"

  8158. msgstr ""

  8159. 

  8160. #: ../../../CHANGELOG.md:4423

  8161. msgid "`matrix-coturn` by using `coturn_enabled: false`"

  8162. msgstr ""

  8163. 

  8164. #: ../../../CHANGELOG.md:4424

  8165. msgid "`matrix-mailer` by using `matrix_mailer_enabled: false`"

  8166. msgstr ""

  8167. 

  8168. #: ../../../CHANGELOG.md:4425

  8169. msgid "`matrix-postgres` by using `matrix_postgres_enabled: false`"

  8170. msgstr ""

  8171. 

  8172. #: ../../../CHANGELOG.md:4427

  8173. msgid "The following changes had to be done:"

  8174. msgstr ""

  8175. 

  8176. #: ../../../CHANGELOG.md:4429

  8177. 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."

  8178. msgstr ""

  8179. 

  8180. #: ../../../CHANGELOG.md:4431

  8181. 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."

  8182. msgstr ""

  8183. 

  8184. #: ../../../CHANGELOG.md:4433

  8185. 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`)"

  8186. msgstr ""

  8187. 

  8188. #: ../../../CHANGELOG.md:4435

  8189. 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."

  8190. msgstr ""

  8191. 

  8192. #: ../../../CHANGELOG.md:4438

  8193. msgid "2019-01-16"

  8194. msgstr ""

  8195. 

  8196. #: ../../../CHANGELOG.md:4440

  8197. msgid "Splitting the playbook into multiple roles"

  8198. msgstr ""

  8199. 

  8200. #: ../../../CHANGELOG.md:4442

  8201. 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)."

  8202. msgstr ""

  8203. 

  8204. #: ../../../CHANGELOG.md:4445

  8205. msgid "To keep the filesystem more consistent with this separation, the **Postgres data had to be relocated**."

  8206. msgstr ""

  8207. 

  8208. #: ../../../CHANGELOG.md:4447

  8209. 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`)."

  8210. msgstr ""

  8211. 

  8212. #: ../../../CHANGELOG.md:4450

  8213. msgid "2019-01-11"

  8214. msgstr ""

  8215. 

  8216. #: ../../../CHANGELOG.md:4452

  8217. msgid "(BC Break) mxisd configuration changes"

  8218. msgstr ""

  8219. 

  8220. #: ../../../CHANGELOG.md:4454

  8221. 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."

  8222. msgstr ""

  8223. 

  8224. #: ../../../CHANGELOG.md:4457

  8225. msgid "The following variables are no longer supported by this playbook:"

  8226. msgstr ""

  8227. 

  8228. #: ../../../CHANGELOG.md:4459

  8229. msgid "`matrix_mxisd_ldap_enabled`"

  8230. msgstr ""

  8231. 

  8232. #: ../../../CHANGELOG.md:4460

  8233. msgid "`matrix_mxisd_ldap_connection_host`"

  8234. msgstr ""

  8235. 

  8236. #: ../../../CHANGELOG.md:4461

  8237. msgid "`matrix_mxisd_ldap_connection_tls`"

  8238. msgstr ""

  8239. 

  8240. #: ../../../CHANGELOG.md:4462

  8241. msgid "`matrix_mxisd_ldap_connection_port`"

  8242. msgstr ""

  8243. 

  8244. #: ../../../CHANGELOG.md:4463

  8245. msgid "`matrix_mxisd_ldap_connection_baseDn`"

  8246. msgstr ""

  8247. 

  8248. #: ../../../CHANGELOG.md:4464

  8249. msgid "`matrix_mxisd_ldap_connection_baseDns`"

  8250. msgstr ""

  8251. 

  8252. #: ../../../CHANGELOG.md:4465

  8253. #: ../../../CHANGELOG.md:4466

  8254. msgid "`matrix_mxisd_ldap_connection_bindDn`"

  8255. msgstr ""

  8256. 

  8257. #: ../../../CHANGELOG.md:4467

  8258. #: ../../../CHANGELOG.md:4471

  8259. msgid "`matrix_mxisd_ldap_connection_bindPassword`"

  8260. msgstr ""

  8261. 

  8262. #: ../../../CHANGELOG.md:4468

  8263. msgid "`matrix_mxisd_ldap_filter`"

  8264. msgstr ""

  8265. 

  8266. #: ../../../CHANGELOG.md:4469

  8267. msgid "`matrix_mxisd_ldap_attribute_uid_type`"

  8268. msgstr ""

  8269. 

  8270. #: ../../../CHANGELOG.md:4470

  8271. msgid "`matrix_mxisd_ldap_attribute_uid_value`"

  8272. msgstr ""

  8273. 

  8274. #: ../../../CHANGELOG.md:4472

  8275. msgid "`matrix_mxisd_ldap_attribute_name`"

  8276. msgstr ""

  8277. 

  8278. #: ../../../CHANGELOG.md:4473

  8279. msgid "`matrix_mxisd_ldap_attribute_threepid_email`"

  8280. msgstr ""

  8281. 

  8282. #: ../../../CHANGELOG.md:4474

  8283. msgid "`matrix_mxisd_ldap_attribute_threepid_msisdn`"

  8284. msgstr ""

  8285. 

  8286. #: ../../../CHANGELOG.md:4475

  8287. msgid "`matrix_mxisd_ldap_identity_filter`"

  8288. msgstr ""

  8289. 

  8290. #: ../../../CHANGELOG.md:4476

  8291. msgid "`matrix_mxisd_ldap_identity_medium`"

  8292. msgstr ""

  8293. 

  8294. #: ../../../CHANGELOG.md:4477

  8295. msgid "`matrix_mxisd_ldap_auth_filter`"

  8296. msgstr ""

  8297. 

  8298. #: ../../../CHANGELOG.md:4478

  8299. msgid "`matrix_mxisd_ldap_directory_filter`"

  8300. msgstr ""

  8301. 

  8302. #: ../../../CHANGELOG.md:4479

  8303. msgid "`matrix_mxisd_template_config`"

  8304. msgstr ""

  8305. 

  8306. #: ../../../CHANGELOG.md:4481

  8307. 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."

  8308. msgstr ""

  8309. 

  8310. #: ../../../CHANGELOG.md:4483

  8311. msgid "This new way of configuring mxisd is beneficial because:"

  8312. msgstr ""

  8313. 

  8314. #: ../../../CHANGELOG.md:4485

  8315. msgid "it lets us support all mxisd configuration options, as the playbook simply forwards them to mxisd without needing to care or understand them"

  8316. msgstr ""

  8317. 

  8318. #: ../../../CHANGELOG.md:4486

  8319. msgid "it lets you upgrade to newer mxisd versions and make use of their features, without us having to add support for them explicitly"

  8320. msgstr ""

  8321. 

  8322. #: ../../../CHANGELOG.md:4489

  8323. msgid "2019-01-08"

  8324. msgstr ""

  8325. 

  8326. #: ../../../CHANGELOG.md:4491

  8327. msgid "(BC Break) Cronjob schedule no longer configurable"

  8328. msgstr ""

  8329. 

  8330. #: ../../../CHANGELOG.md:4493

  8331. msgid "Due to the way we manage cronjobs now, you can no longer configure the schedule they're invoked at."

  8332. msgstr ""

  8333. 

  8334. #: ../../../CHANGELOG.md:4495

  8335. 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."

  8336. msgstr ""

  8337. 

  8338. #: ../../../CHANGELOG.md:4498

  8339. 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!"

  8340. msgstr ""

  8341. 

  8342. #: ../../../CHANGELOG.md:4501

  8343. msgid "2018-12-23"

  8344. msgstr ""

  8345. 

  8346. #: ../../../CHANGELOG.md:4503

  8347. msgid "(BC Break) More SSL certificate retrieval methods"

  8348. msgstr ""

  8349. 

  8350. #: ../../../CHANGELOG.md:4505

  8351. msgid "The playbook now lets you decide between 3 different SSL certificate retrieval methods:"

  8352. msgstr ""

  8353. 

  8354. #: ../../../CHANGELOG.md:4506

  8355. msgid "(default) obtaining free SSL certificates from Let's Encrypt"

  8356. msgstr ""

  8357. 

  8358. #: ../../../CHANGELOG.md:4507

  8359. msgid "generating self-signed SSL certificates"

  8360. msgstr ""

  8361. 

  8362. #: ../../../CHANGELOG.md:4508

  8363. msgid "managing SSL certificates manually"

  8364. msgstr ""

  8365. 

  8366. #: ../../../CHANGELOG.md:4510

  8367. msgid "Learn more in [Adjusting SSL certificate retrieval](docs/configuring-playbook-ssl-certificates.md)."

  8368. msgstr ""

  8369. 

  8370. #: ../../../CHANGELOG.md:4512

  8371. 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:"

  8372. msgstr ""

  8373. 

  8374. #: ../../../CHANGELOG.md:4514

  8375. msgid "before: `host_specific_matrix_ssl_support_email`"

  8376. msgstr ""

  8377. 

  8378. #: ../../../CHANGELOG.md:4515

  8379. msgid "after: `host_specific_matrix_ssl_lets_encrypt_support_email`"

  8380. msgstr ""

  8381. 

  8382. #: ../../../CHANGELOG.md:4517

  8383. msgid "(BC Break) mxisd upgrade with multiple base DN support"

  8384. msgstr ""

  8385. 

  8386. #: ../../../CHANGELOG.md:4519

  8387. 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)."

  8388. msgstr ""

  8389. 

  8390. #: ../../../CHANGELOG.md:4521

  8391. 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)."

  8392. msgstr ""

  8393. 

  8394. #: ../../../CHANGELOG.md:4523

  8395. msgid "Example change:"

  8396. msgstr ""

  8397. 

  8398. #: ../../../CHANGELOG.md:4525

  8399. msgid "before: `matrix_mxisd_ldap_connection_baseDn: OU=Users,DC=example,DC=org`"

  8400. msgstr ""

  8401. 

  8402. #: ../../../CHANGELOG.md:4526

  8403. msgid "after: `matrix_mxisd_ldap_connection_baseDns: ['OU=Users,DC=example,DC=org']`"

  8404. msgstr ""

  8405. 

  8406. #: ../../../CHANGELOG.md:4529

  8407. msgid "2018-12-21"

  8408. msgstr ""

  8409. 

  8410. #: ../../../CHANGELOG.md:4531

  8411. msgid "Synapse 0.34.0 and Python 3"

  8412. msgstr ""

  8413. 

  8414. #: ../../../CHANGELOG.md:4533

  8415. 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)."

  8416. msgstr ""

  8417. 

  8418. #: ../../../CHANGELOG.md:4536

  8419. msgid "2018-12-12"

  8420. msgstr ""

  8421. 

  8422. #: ../../../CHANGELOG.md:4538

  8423. msgid "Riot homepage customization"

  8424. msgstr ""

  8425. 

  8426. #: ../../../CHANGELOG.md:4540

  8427. 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`."

  8428. msgstr ""

  8429. 

  8430. #: ../../../CHANGELOG.md:4543

  8431. msgid "2018-12-04"

  8432. msgstr ""

  8433. 

  8434. #: ../../../CHANGELOG.md:4545

  8435. msgid "mxisd extensibility"

  8436. msgstr ""

  8437. 

  8438. #: ../../../CHANGELOG.md:4547

  8439. 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`)."

  8440. msgstr ""

  8441. 

  8442. #: ../../../CHANGELOG.md:4550

  8443. msgid "2018-11-28"

  8444. msgstr ""

  8445. 

  8446. #: ../../../CHANGELOG.md:4552

  8447. msgid "More scripts"

  8448. msgstr ""

  8449. 

  8450. #: ../../../CHANGELOG.md:4554

  8451. msgid "matrix-remove-all allows to uninstall everything with a single command"

  8452. msgstr ""

  8453. 

  8454. #: ../../../CHANGELOG.md:4555

  8455. msgid "matrix-make-user-admin allows to upgrade a user's privileges"

  8456. msgstr ""

  8457. 

  8458. #: ../../../CHANGELOG.md:4557

  8459. msgid "LDAP auth support via matrix-synapse-ldap3"

  8460. msgstr ""

  8461. 

  8462. #: ../../../CHANGELOG.md:4559

  8463. msgid "The playbook can now install and configure [LDAP auth support](https://github.com/matrix-org/matrix-synapse-ldap3) for you."

  8464. msgstr ""

  8465. 

  8466. #: ../../../CHANGELOG.md:4561

  8467. msgid "Additional details are available in [Setting up the LDAP authentication password provider module](docs/configuring-playbook-ldap-auth.md)."

  8468. msgstr ""

  8469. 

  8470. #: ../../../CHANGELOG.md:4564

  8471. msgid "2018-11-23"

  8472. msgstr ""

  8473. 

  8474. #: ../../../CHANGELOG.md:4566

  8475. msgid "Support for controlling public registration and room auto-join"

  8476. msgstr ""

  8477. 

  8478. #: ../../../CHANGELOG.md:4568

  8479. msgid "The playbook now lets you enable public registration for users (controlled via `matrix_synapse_enable_registration`). By default, public registration is forbidden."

  8480. msgstr ""

  8481. 

  8482. #: ../../../CHANGELOG.md:4570

  8483. msgid "You can also make people automatically get auto-joined to rooms (controlled via `matrix_synapse_auto_join_rooms`)."

  8484. msgstr ""

  8485. 

  8486. #: ../../../CHANGELOG.md:4572

  8487. msgid "Support for changing the welcome user ID (welcome bot)"

  8488. msgstr ""

  8489. 

  8490. #: ../../../CHANGELOG.md:4574

  8491. 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."

  8492. msgstr ""

  8493. 

  8494. #: ../../../CHANGELOG.md:4577

  8495. msgid "2018-11-14"

  8496. msgstr ""

  8497. 

  8498. #: ../../../CHANGELOG.md:4579

  8499. msgid "Ability to set Synapse log levels"

  8500. msgstr ""

  8501. 

  8502. #: ../../../CHANGELOG.md:4581

  8503. msgid "The playbook now allows you to set the log levels used by Synapse. The default logging levels remain the same."

  8504. msgstr ""

  8505. 

  8506. #: ../../../CHANGELOG.md:4583

  8507. 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"

  8508. msgstr ""

  8509. 

  8510. #: ../../../CHANGELOG.md:4592

  8511. msgid "2018-11-03"

  8512. msgstr ""

  8513. 

  8514. #: ../../../CHANGELOG.md:4594

  8515. msgid "Customize parts of Riot's config"

  8516. msgstr ""

  8517. 

  8518. #: ../../../CHANGELOG.md:4596

  8519. msgid "You can now customize some parts of Riot's `config.json`. These playbook variables, with these default values, have been added:"

  8520. msgstr ""

  8521. 

  8522. #: ../../../CHANGELOG.md:4607

  8523. 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:"

  8524. msgstr ""

  8525. 

  8526. #: ../../../CHANGELOG.md:4616

  8527. msgid "SSL protocols used to serve Riot and Synapse"

  8528. msgstr ""

  8529. 

  8530. #: ../../../CHANGELOG.md:4618

  8531. 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."

  8532. msgstr ""

  8533. 

  8534. #: ../../../CHANGELOG.md:4620

  8535. msgid "You may wish to re-enable TLSv1 if you need to access Riot in older browsers."

  8536. msgstr ""

  8537. 

  8538. #: ../../../CHANGELOG.md:4622

  8539. msgid "Note: Currently the dockerized nginx doesn't support TLSv1.3. See https://github.com/nginxinc/docker-nginx/issues/190 for more details."

  8540. msgstr ""

  8541. 

  8542. #: ../../../CHANGELOG.md:4625

  8543. msgid "2018-11-01"

  8544. msgstr ""

  8545. 

  8546. #: ../../../CHANGELOG.md:4627

  8547. msgid "Postgres 11 support"

  8548. msgstr ""

  8549. 

  8550. #: ../../../CHANGELOG.md:4629

  8551. msgid "The playbook now installs [Postgres 11](https://www.postgresql.org/about/news/1894/) by default."

  8552. msgstr ""

  8553. 

  8554. #: ../../../CHANGELOG.md:4631

  8555. 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)."

  8556. msgstr ""

  8557. 

  8558. #: ../../../CHANGELOG.md:4633

  8559. #: ../../../CHANGELOG.md:4720

  8560. #: ../../../CHANGELOG.md:4840

  8561. msgid "(BC Break) Renaming playbook variables"

  8562. msgstr ""

  8563. 

  8564. #: ../../../CHANGELOG.md:4635

  8565. 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."

  8566. msgstr ""

  8567. 

  8568. #: ../../../CHANGELOG.md:4639

  8569. msgid "from `matrix_docker_image_mxisd` to `matrix_mxisd_docker_image`"

  8570. msgstr ""

  8571. 

  8572. #: ../../../CHANGELOG.md:4640

  8573. msgid "from `matrix_docker_image_mautrix_telegram` to `matrix_mautrix_telegram_docker_image`"

  8574. msgstr ""

  8575. 

  8576. #: ../../../CHANGELOG.md:4641

  8577. msgid "from `matrix_docker_image_mautrix_whatsapp` to `matrix_mautrix_whatsapp_docker_image`"

  8578. msgstr ""

  8579. 

  8580. #: ../../../CHANGELOG.md:4642

  8581. msgid "from `matrix_docker_image_mailer` to `matrix_mailer_docker_image`"

  8582. msgstr ""

  8583. 

  8584. #: ../../../CHANGELOG.md:4643

  8585. msgid "from `matrix_docker_image_coturn` to `coturn_container_image`"

  8586. msgstr ""

  8587. 

  8588. #: ../../../CHANGELOG.md:4644

  8589. msgid "from `matrix_docker_image_goofys` to `matrix_s3_goofys_docker_image`"

  8590. msgstr ""

  8591. 

  8592. #: ../../../CHANGELOG.md:4645

  8593. msgid "from `matrix_docker_image_riot` to `matrix_riot_web_docker_image`"

  8594. msgstr ""

  8595. 

  8596. #: ../../../CHANGELOG.md:4646

  8597. msgid "from `matrix_docker_image_nginx` to `matrix_nginx_proxy_docker_image`"

  8598. msgstr ""

  8599. 

  8600. #: ../../../CHANGELOG.md:4647

  8601. msgid "from `matrix_docker_image_synapse` to `matrix_synapse_docker_image`"

  8602. msgstr ""

  8603. 

  8604. #: ../../../CHANGELOG.md:4648

  8605. msgid "from `matrix_docker_image_postgres_v9` to `matrix_postgres_docker_image_v9`"

  8606. msgstr ""

  8607. 

  8608. #: ../../../CHANGELOG.md:4649

  8609. msgid "from `matrix_docker_image_postgres_v10` to `matrix_postgres_docker_image_v10`"

  8610. msgstr ""

  8611. 

  8612. #: ../../../CHANGELOG.md:4650

  8613. msgid "from `matrix_docker_image_postgres_latest` to `matrix_postgres_docker_image_latest`"

  8614. msgstr ""

  8615. 

  8616. #: ../../../CHANGELOG.md:4653

  8617. msgid "2018-10-26"

  8618. msgstr ""

  8619. 

  8620. #: ../../../CHANGELOG.md:4655

  8621. msgid "Mautrix Whatsapp bridging support"

  8622. msgstr ""

  8623. 

  8624. #: ../../../CHANGELOG.md:4657

  8625. 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)."

  8626. msgstr ""

  8627. 

  8628. #: ../../../CHANGELOG.md:4659

  8629. msgid "Additional details are available in [Setting up Mautrix Whatsapp bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)."

  8630. msgstr ""

  8631. 

  8632. #: ../../../CHANGELOG.md:4662

  8633. msgid "2018-10-25"

  8634. msgstr ""

  8635. 

  8636. #: ../../../CHANGELOG.md:4664

  8637. msgid "Support for controlling Matrix federation"

  8638. msgstr ""

  8639. 

  8640. #: ../../../CHANGELOG.md:4666

  8641. 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."

  8642. msgstr ""

  8643. 

  8644. #: ../../../CHANGELOG.md:4669

  8645. msgid "2018-10-24"

  8646. msgstr ""

  8647. 

  8648. #: ../../../CHANGELOG.md:4671

  8649. msgid "Disabling riot-web guests"

  8650. msgstr ""

  8651. 

  8652. #: ../../../CHANGELOG.md:4673

  8653. 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."

  8654. msgstr ""

  8655. 

  8656. #: ../../../CHANGELOG.md:4676

  8657. msgid "2018-10-21"

  8658. msgstr ""

  8659. 

  8660. #: ../../../CHANGELOG.md:4678

  8661. msgid "Self-check maintenance command"

  8662. msgstr ""

  8663. 

  8664. #: ../../../CHANGELOG.md:4680

  8665. msgid "The playbook can now [check if services are configured correctly](docs/maintenance-and-troubleshooting.md#how-to-check-if-services-work)."

  8666. msgstr ""

  8667. 

  8668. #: ../../../CHANGELOG.md:4683

  8669. msgid "2018-10-05"

  8670. msgstr ""

  8671. 

  8672. #: ../../../CHANGELOG.md:4685

  8673. msgid "Presence tracking made configurable"

  8674. msgstr ""

  8675. 

  8676. #: ../../../CHANGELOG.md:4687

  8677. 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)."

  8678. msgstr ""

  8679. 

  8680. #: ../../../CHANGELOG.md:4689

  8681. msgid "If users participate in large rooms with many other servers, disabling presence will decrease server load significantly."

  8682. msgstr ""

  8683. 

  8684. #: ../../../CHANGELOG.md:4692

  8685. msgid "2018-09-27"

  8686. msgstr ""

  8687. 

  8688. #: ../../../CHANGELOG.md:4694

  8689. msgid "Synapse Cache Factor made configurable"

  8690. msgstr ""

  8691. 

  8692. #: ../../../CHANGELOG.md:4696

  8693. 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`)."

  8694. msgstr ""

  8695. 

  8696. #: ../../../CHANGELOG.md:4698

  8697. 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"

  8698. msgstr ""

  8699. 

  8700. #: ../../../CHANGELOG.md:4701

  8701. msgid "2018-09-26"

  8702. msgstr ""

  8703. 

  8704. #: ../../../CHANGELOG.md:4703

  8705. msgid "Disabling Docker container logging"

  8706. msgstr ""

  8707. 

  8708. #: ../../../CHANGELOG.md:4705

  8709. msgid "`--log-driver=none` is used for all Docker containers now."

  8710. msgstr ""

  8711. 

  8712. #: ../../../CHANGELOG.md:4707

  8713. 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."

  8714. msgstr ""

  8715. 

  8716. #: ../../../CHANGELOG.md:4709

  8717. 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."

  8718. msgstr ""

  8719. 

  8720. #: ../../../CHANGELOG.md:4712

  8721. msgid "2018-09-17"

  8722. msgstr ""

  8723. 

  8724. #: ../../../CHANGELOG.md:4714

  8725. msgid "Service discovery support"

  8726. msgstr ""

  8727. 

  8728. #: ../../../CHANGELOG.md:4716

  8729. 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."

  8730. msgstr ""

  8731. 

  8732. #: ../../../CHANGELOG.md:4718

  8733. msgid "Additional details are available in [Configuring service discovery via .well-known](docs/configuring-well-known.md)."

  8734. msgstr ""

  8735. 

  8736. #: ../../../CHANGELOG.md:4724

  8737. msgid "from `matrix_nginx_riot_web_data_path` to `matrix_riot_web_data_path`"

  8738. msgstr ""

  8739. 

  8740. #: ../../../CHANGELOG.md:4725

  8741. msgid "from `matrix_riot_web_default_identity_server_url` to `matrix_identity_server_url`"

  8742. msgstr ""

  8743. 

  8744. #: ../../../CHANGELOG.md:4728

  8745. msgid "2018-09-07"

  8746. msgstr ""

  8747. 

  8748. #: ../../../CHANGELOG.md:4730

  8749. msgid "Mautrix Telegram bridging support"

  8750. msgstr ""

  8751. 

  8752. #: ../../../CHANGELOG.md:4732

  8753. 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)."

  8754. msgstr ""

  8755. 

  8756. #: ../../../CHANGELOG.md:4734

  8757. msgid "Additional details are available in [Setting up Mautrix Telegram bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)."

  8758. msgstr ""

  8759. 

  8760. #: ../../../CHANGELOG.md:4736

  8761. msgid "Events cache size increase and configurability for Matrix Synapse"

  8762. msgstr ""

  8763. 

  8764. #: ../../../CHANGELOG.md:4738

  8765. msgid "The playbook now lets you configure Matrix Synapse's `event_cache_size` configuration via the `matrix_synapse_event_cache_size` playbook variable."

  8766. msgstr ""

  8767. 

  8768. #: ../../../CHANGELOG.md:4740

  8769. msgid "Previously, this value was hardcoded to `\"10K\"`. From now on, a more reasonable default of `\"100K\"` is used."

  8770. msgstr ""

  8771. 

  8772. #: ../../../CHANGELOG.md:4742

  8773. msgid "Password-peppering support for Matrix Synapse"

  8774. msgstr ""

  8775. 

  8776. #: ../../../CHANGELOG.md:4744

  8777. 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."

  8778. msgstr ""

  8779. 

  8780. #: ../../../CHANGELOG.md:4746

  8781. msgid "Statistics-reporting support for Matrix Synapse"

  8782. msgstr ""

  8783. 

  8784. #: ../../../CHANGELOG.md:4748

  8785. 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."

  8786. msgstr ""

  8787. 

  8788. #: ../../../CHANGELOG.md:4750

  8789. 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."

  8790. msgstr ""

  8791. 

  8792. #: ../../../CHANGELOG.md:4753

  8793. msgid "2018-08-29"

  8794. msgstr ""

  8795. 

  8796. #: ../../../CHANGELOG.md:4755

  8797. msgid "Changing the way SSL certificates are retrieved"

  8798. msgstr ""

  8799. 

  8800. #: ../../../CHANGELOG.md:4757

  8801. 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."

  8802. msgstr ""

  8803. 

  8804. #: ../../../CHANGELOG.md:4759

  8805. 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)."

  8806. msgstr ""

  8807. 

  8808. #: ../../../CHANGELOG.md:4761

  8809. 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:"

  8810. msgstr ""

  8811. 

  8812. #: ../../../CHANGELOG.md:4763

  8813. msgid "`systemctl stop 'matrix*'`"

  8814. msgstr ""

  8815. 

  8816. #: ../../../CHANGELOG.md:4764

  8817. msgid "stop your custom webserver, if you're running one (only affects you if you've installed with `matrix_nginx_proxy_enabled: false`)"

  8818. msgstr ""

  8819. 

  8820. #: ../../../CHANGELOG.md:4765

  8821. msgid "`mv /matrix/ssl /matrix/ssl-acmetool-delete-later`"

  8822. msgstr ""

  8823. 

  8824. #: ../../../CHANGELOG.md:4766

  8825. msgid "re-run the playbook's [installation](docs/installing.md)"

  8826. msgstr ""

  8827. 

  8828. #: ../../../CHANGELOG.md:4767

  8829. msgid "possibly delete `/matrix/ssl-acmetool-delete-later`"

  8830. msgstr ""

  8831. 

  8832. #: ../../../CHANGELOG.md:4770

  8833. msgid "2018-08-21"

  8834. msgstr ""

  8835. 

  8836. #: ../../../CHANGELOG.md:4772

  8837. msgid "Matrix Corporal support"

  8838. msgstr ""

  8839. 

  8840. #: ../../../CHANGELOG.md:4774

  8841. msgid "The playbook can now install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you."

  8842. msgstr ""

  8843. 

  8844. #: ../../../CHANGELOG.md:4776

  8845. msgid "Additional details are available in [Setting up Matrix Corporal](docs/configuring-playbook-matrix-corporal.md)."

  8846. msgstr ""

  8847. 

  8848. #: ../../../CHANGELOG.md:4779

  8849. msgid "2018-08-20"

  8850. msgstr ""

  8851. 

  8852. #: ../../../CHANGELOG.md:4781

  8853. msgid "Matrix Synapse rate limit control variables"

  8854. msgstr ""

  8855. 

  8856. #: ../../../CHANGELOG.md:4783

  8857. msgid "The following new variables can now be configured to control Matrix Synapse's rate-limiting (default values are shown below)."

  8858. msgstr ""

  8859. 

  8860. #: ../../../CHANGELOG.md:4790

  8861. msgid "Shared Secret Auth support via matrix-synapse-shared-secret-auth"

  8862. msgstr ""

  8863. 

  8864. #: ../../../CHANGELOG.md:4792

  8865. msgid "The playbook can now install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you."

  8866. msgstr ""

  8867. 

  8868. #: ../../../CHANGELOG.md:4794

  8869. msgid "Additional details are available in [Setting up the Shared Secret Auth password provider module](docs/configuring-playbook-shared-secret-auth.md)."

  8870. msgstr ""

  8871. 

  8872. #: ../../../CHANGELOG.md:4797

  8873. msgid "2018-08-17"

  8874. msgstr ""

  8875. 

  8876. #: ../../../CHANGELOG.md:4799

  8877. msgid "REST auth support via matrix-synapse-rest-auth"

  8878. msgstr ""

  8879. 

  8880. #: ../../../CHANGELOG.md:4801

  8881. msgid "The playbook can now install and configure [matrix-synapse-rest-auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you."

  8882. msgstr ""

  8883. 

  8884. #: ../../../CHANGELOG.md:4803

  8885. msgid "Additional details are available in [Setting up the REST authentication password provider module](docs/configuring-playbook-rest-auth.md)."

  8886. msgstr ""

  8887. 

  8888. #: ../../../CHANGELOG.md:4805

  8889. msgid "Compression improvements"

  8890. msgstr ""

  8891. 

  8892. #: ../../../CHANGELOG.md:4807

  8893. msgid "Shifted Matrix Synapse compression from happening in the Matrix Synapse, to happening in the nginx proxy that's in front of it."

  8894. msgstr ""

  8895. 

  8896. #: ../../../CHANGELOG.md:4810

  8897. 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."

  8898. msgstr ""

  8899. 

  8900. #: ../../../CHANGELOG.md:4813

  8901. msgid "Disabling some unnecessary Synapse services"

  8902. msgstr ""

  8903. 

  8904. #: ../../../CHANGELOG.md:4815

  8905. msgid "The following services are not necessary, so they have been disabled:"

  8906. msgstr ""

  8907. 

  8908. #: ../../../CHANGELOG.md:4816

  8909. msgid "on the federation port (8448): the `client` service"

  8910. msgstr ""

  8911. 

  8912. #: ../../../CHANGELOG.md:4817

  8913. msgid "on the http port (8008, exposed over 443): the old Angular `webclient` and the `federation` service"

  8914. msgstr ""

  8915. 

  8916. #: ../../../CHANGELOG.md:4819

  8917. msgid "Federation runs only on the federation port (8448) now. The Client APIs run only on the http port (8008) now."

  8918. msgstr ""

  8919. 

  8920. #: ../../../CHANGELOG.md:4822

  8921. msgid "2018-08-15"

  8922. msgstr ""

  8923. 

  8924. #: ../../../CHANGELOG.md:4824

  8925. msgid "mxisd Identity Server support"

  8926. msgstr ""

  8927. 

  8928. #: ../../../CHANGELOG.md:4826

  8929. 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)."

  8930. msgstr ""

  8931. 

  8932. #: ../../../CHANGELOG.md:4829

  8933. msgid "2018-08-14"

  8934. msgstr ""

  8935. 

  8936. #: ../../../CHANGELOG.md:4831

  8937. msgid "Email-sending support"

  8938. msgstr ""

  8939. 

  8940. #: ../../../CHANGELOG.md:4833

  8941. 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)."

  8942. msgstr ""

  8943. 

  8944. #: ../../../CHANGELOG.md:4835

  8945. msgid "With this, Matrix Synapse is able to send email notifications for missed messages, etc."

  8946. msgstr ""

  8947. 

  8948. #: ../../../CHANGELOG.md:4838

  8949. msgid "2018-08-08"

  8950. msgstr ""

  8951. 

  8952. #: ../../../CHANGELOG.md:4844

  8953. msgid "from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`"

  8954. msgstr ""

  8955. 

  8956. #: ../../../CHANGELOG.md:4845

  8957. msgid "from `matrix_max_log_file_size_mb` to `matrix_synapse_max_log_file_size_mb`"

  8958. msgstr ""

  8959. 

  8960. #: ../../../CHANGELOG.md:4846

  8961. msgid "from `matrix_max_log_files_count` to `matrix_synapse_max_log_files_count`"

  8962. msgstr ""

  8963. 

  8964. #: ../../../CHANGELOG.md:4847

  8965. msgid "from `docker_matrix_image` to `matrix_docker_image_synapse`"

  8966. msgstr ""

  8967. 

  8968. #: ../../../CHANGELOG.md:4848

  8969. msgid "from `docker_nginx_image` to `matrix_docker_image_nginx`"

  8970. msgstr ""

  8971. 

  8972. #: ../../../CHANGELOG.md:4849

  8973. msgid "from `docker_riot_image` to `matrix_docker_image_riot`"

  8974. msgstr ""

  8975. 

  8976. #: ../../../CHANGELOG.md:4850

  8977. msgid "from `docker_goofys_image` to `matrix_docker_image_goofys`"

  8978. msgstr ""

  8979. 

  8980. #: ../../../CHANGELOG.md:4851

  8981. msgid "from `docker_coturn_image` to `matrix_docker_image_coturn`"

  8982. msgstr ""

  8983. 

  8984. #: ../../../CHANGELOG.md:4853

  8985. msgid "If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names."

  8986. msgstr ""

  8987. 

  8988. #: ../../../CHANGELOG.md:4855

  8989. msgid "Renaming Ansible playbook tag"

  8990. msgstr ""

  8991. 

  8992. #: ../../../CHANGELOG.md:4857

  8993. msgid "The command for executing the whole playbook has changed. The `setup-main` tag got renamed to `setup-all`."

  8994. msgstr ""

  8995. 

  8996. #: ../../../CHANGELOG.md:4859

  8997. msgid "Docker container linking"

  8998. msgstr ""

  8999. 

  9000. #: ../../../CHANGELOG.md:4861

  9001. 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."

  9002. msgstr ""