overmind
/
matrix-docker-ansible-deploy
镜像来自 https://github.com/spantaleev/matrix-docker-ansible-deploy
1
0
複製 0
程式碼 問題管理 0 版本發佈 0 Wiki Activity
Matrix Docker Ansible eploy
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
10962 Commit
12 分支
511 MiB
 
 
目錄樹: 08e2449dc7
分支列表 標籤列表
${ item.name }
Create branch ${ searchTerm }
from '08e2449dc7'
${ noResults }
matrix-docker-ansible-deploy/i18n/translation-templates/CHANGELOG.pot

8089 line
401 KiB
原始文件 Blame 文件歷史 

  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-03-03 10:49+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-03-01"

  21. msgstr ""

  22. 

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

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

  25. msgstr ""

  26. 

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

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

  29. msgstr ""

  30. 

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

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

  33. msgstr ""

  34. 

  35. #: ../../../CHANGELOG.md:8

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

  37. msgstr ""

  38. 

  39. #: ../../../CHANGELOG.md:10

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

  41. msgstr ""

  42. 

  43. #: ../../../CHANGELOG.md:12

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

  45. msgstr ""

  46. 

  47. #: ../../../CHANGELOG.md:14

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

  49. msgstr ""

  50. 

  51. #: ../../../CHANGELOG.md:16

  52. msgid "2026-02-26"

  53. msgstr ""

  54. 

  55. #: ../../../CHANGELOG.md:18

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

  57. msgstr ""

  58. 

  59. #: ../../../CHANGELOG.md:20

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

  61. msgstr ""

  62. 

  63. #: ../../../CHANGELOG.md:22

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

  65. msgstr ""

  66. 

  67. #: ../../../CHANGELOG.md:24

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

  69. msgstr ""

  70. 

  71. #: ../../../CHANGELOG.md:26

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

  73. msgstr ""

  74. 

  75. #: ../../../CHANGELOG.md:28

  76. msgid "2026-02-21"

  77. msgstr ""

  78. 

  79. #: ../../../CHANGELOG.md:30

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

  81. msgstr ""

  82. 

  83. #: ../../../CHANGELOG.md:32

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

  85. msgstr ""

  86. 

  87. #: ../../../CHANGELOG.md:34

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

  89. msgstr ""

  90. 

  91. #: ../../../CHANGELOG.md:36

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

  93. msgstr ""

  94. 

  95. #: ../../../CHANGELOG.md:37

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

  97. msgstr ""

  98. 

  99. #: ../../../CHANGELOG.md:39

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

  101. msgstr ""

  102. 

  103. #: ../../../CHANGELOG.md:41

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

  105. msgstr ""

  106. 

  107. #: ../../../CHANGELOG.md:43

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

  109. msgstr ""

  110. 

  111. #: ../../../CHANGELOG.md:52

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

  113. msgstr ""

  114. 

  115. #: ../../../CHANGELOG.md:54

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

  117. msgstr ""

  118. 

  119. #: ../../../CHANGELOG.md:56

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

  121. msgstr ""

  122. 

  123. #: ../../../CHANGELOG.md:58

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

  125. msgstr ""

  126. 

  127. #: ../../../CHANGELOG.md:60

  128. msgid "2026-02-17"

  129. msgstr ""

  130. 

  131. #: ../../../CHANGELOG.md:62

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

  133. msgstr ""

  134. 

  135. #: ../../../CHANGELOG.md:64

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

  137. msgstr ""

  138. 

  139. #: ../../../CHANGELOG.md:66

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

  141. msgstr ""

  142. 

  143. #: ../../../CHANGELOG.md:68

  144. #: ../../../CHANGELOG.md:130

  145. #: ../../../CHANGELOG.md:140

  146. #: ../../../CHANGELOG.md:201

  147. #: ../../../CHANGELOG.md:223

  148. #: ../../../CHANGELOG.md:758

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

  150. msgstr ""

  151. 

  152. #: ../../../CHANGELOG.md:70

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

  154. msgstr ""

  155. 

  156. #: ../../../CHANGELOG.md:72

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

  158. msgstr ""

  159. 

  160. #: ../../../CHANGELOG.md:74

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

  162. msgstr ""

  163. 

  164. #: ../../../CHANGELOG.md:76

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

  166. msgstr ""

  167. 

  168. #: ../../../CHANGELOG.md:78

  169. msgid "2026-02-16"

  170. msgstr ""

  171. 

  172. #: ../../../CHANGELOG.md:80

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

  174. msgstr ""

  175. 

  176. #: ../../../CHANGELOG.md:82

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

  178. msgstr ""

  179. 

  180. #: ../../../CHANGELOG.md:84

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

  182. msgstr ""

  183. 

  184. #: ../../../CHANGELOG.md:86

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

  186. msgstr ""

  187. 

  188. #: ../../../CHANGELOG.md:88

  189. msgid "2026-02-13"

  190. msgstr ""

  191. 

  192. #: ../../../CHANGELOG.md:90

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

  194. msgstr ""

  195. 

  196. #: ../../../CHANGELOG.md:92

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

  198. msgstr ""

  199. 

  200. #: ../../../CHANGELOG.md:94

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

  202. msgstr ""

  203. 

  204. #: ../../../CHANGELOG.md:96

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

  206. msgstr ""

  207. 

  208. #: ../../../CHANGELOG.md:98

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

  210. msgstr ""

  211. 

  212. #: ../../../CHANGELOG.md:100

  213. msgid "**Before**:"

  214. msgstr ""

  215. 

  216. #: ../../../CHANGELOG.md:101

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

  218. msgstr ""

  219. 

  220. #: ../../../CHANGELOG.md:102

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

  222. msgstr ""

  223. 

  224. #: ../../../CHANGELOG.md:103

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

  226. msgstr ""

  227. 

  228. #: ../../../CHANGELOG.md:104

  229. msgid "**After**:"

  230. msgstr ""

  231. 

  232. #: ../../../CHANGELOG.md:105

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

  234. msgstr ""

  235. 

  236. #: ../../../CHANGELOG.md:106

  237. msgid "Traefik restarted: no ✅"

  238. msgstr ""

  239. 

  240. #: ../../../CHANGELOG.md:107

  241. msgid "dependent services restarted: no ✅"

  242. msgstr ""

  243. 

  244. #: ../../../CHANGELOG.md:109

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

  246. msgstr ""

  247. 

  248. #: ../../../CHANGELOG.md:112

  249. msgid "2026-02-12"

  250. msgstr ""

  251. 

  252. #: ../../../CHANGELOG.md:114

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

  254. msgstr ""

  255. 

  256. #: ../../../CHANGELOG.md:116

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

  258. msgstr ""

  259. 

  260. #: ../../../CHANGELOG.md:118

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

  262. msgstr ""

  263. 

  264. #: ../../../CHANGELOG.md:120

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

  266. msgstr ""

  267. 

  268. #: ../../../CHANGELOG.md:122

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

  270. msgstr ""

  271. 

  272. #: ../../../CHANGELOG.md:124

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

  274. msgstr ""

  275. 

  276. #: ../../../CHANGELOG.md:126

  277. #: ../../../CHANGELOG.md:219

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

  279. msgstr ""

  280. 

  281. #: ../../../CHANGELOG.md:128

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

  283. msgstr ""

  284. 

  285. #: ../../../CHANGELOG.md:132

  286. msgid "2026-02-11"

  287. msgstr ""

  288. 

  289. #: ../../../CHANGELOG.md:134

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

  291. msgstr ""

  292. 

  293. #: ../../../CHANGELOG.md:136

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

  295. msgstr ""

  296. 

  297. #: ../../../CHANGELOG.md:138

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

  299. msgstr ""

  300. 

  301. #: ../../../CHANGELOG.md:142

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

  303. msgstr ""

  304. 

  305. #: ../../../CHANGELOG.md:144

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

  307. msgstr ""

  308. 

  309. #: ../../../CHANGELOG.md:146

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

  311. msgstr ""

  312. 

  313. #: ../../../CHANGELOG.md:148

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

  315. msgstr ""

  316. 

  317. #: ../../../CHANGELOG.md:150

  318. msgid "2026-02-09"

  319. msgstr ""

  320. 

  321. #: ../../../CHANGELOG.md:152

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

  323. msgstr ""

  324. 

  325. #: ../../../CHANGELOG.md:154

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

  327. msgstr ""

  328. 

  329. #: ../../../CHANGELOG.md:156

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

  331. msgstr ""

  332. 

  333. #: ../../../CHANGELOG.md:158

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

  335. msgstr ""

  336. 

  337. #: ../../../CHANGELOG.md:160

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

  339. msgstr ""

  340. 

  341. #: ../../../CHANGELOG.md:166

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

  343. msgstr ""

  344. 

  345. #: ../../../CHANGELOG.md:175

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

  347. msgstr ""

  348. 

  349. #: ../../../CHANGELOG.md:177

  350. msgid "2026-02-08"

  351. msgstr ""

  352. 

  353. #: ../../../CHANGELOG.md:179

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

  355. msgstr ""

  356. 

  357. #: ../../../CHANGELOG.md:181

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

  359. msgstr ""

  360. 

  361. #: ../../../CHANGELOG.md:183

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

  363. msgstr ""

  364. 

  365. #: ../../../CHANGELOG.md:185

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

  367. msgstr ""

  368. 

  369. #: ../../../CHANGELOG.md:187

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

  371. msgstr ""

  372. 

  373. #: ../../../CHANGELOG.md:189

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

  375. msgstr ""

  376. 

  377. #: ../../../CHANGELOG.md:191

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

  379. msgstr ""

  380. 

  381. #: ../../../CHANGELOG.md:193

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

  383. msgstr ""

  384. 

  385. #: ../../../CHANGELOG.md:195

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

  387. msgstr ""

  388. 

  389. #: ../../../CHANGELOG.md:197

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

  391. msgstr ""

  392. 

  393. #: ../../../CHANGELOG.md:199

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

  395. msgstr ""

  396. 

  397. #: ../../../CHANGELOG.md:203

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

  399. msgstr ""

  400. 

  401. #: ../../../CHANGELOG.md:205

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

  403. msgstr ""

  404. 

  405. #: ../../../CHANGELOG.md:207

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

  407. msgstr ""

  408. 

  409. #: ../../../CHANGELOG.md:209

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

  411. msgstr ""

  412. 

  413. #: ../../../CHANGELOG.md:211

  414. msgid "2026-02-07"

  415. msgstr ""

  416. 

  417. #: ../../../CHANGELOG.md:213

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

  419. msgstr ""

  420. 

  421. #: ../../../CHANGELOG.md:215

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

  423. msgstr ""

  424. 

  425. #: ../../../CHANGELOG.md:217

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

  427. msgstr ""

  428. 

  429. #: ../../../CHANGELOG.md:221

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

  431. msgstr ""

  432. 

  433. #: ../../../CHANGELOG.md:225

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

  435. msgstr ""

  436. 

  437. #: ../../../CHANGELOG.md:227

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

  439. msgstr ""

  440. 

  441. #: ../../../CHANGELOG.md:229

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

  443. msgstr ""

  444. 

  445. #: ../../../CHANGELOG.md:231

  446. msgid "2026-02-04"

  447. msgstr ""

  448. 

  449. #: ../../../CHANGELOG.md:233

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

  451. msgstr ""

  452. 

  453. #: ../../../CHANGELOG.md:235

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

  455. msgstr ""

  456. 

  457. #: ../../../CHANGELOG.md:237

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

  459. msgstr ""

  460. 

  461. #: ../../../CHANGELOG.md:244

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

  463. msgstr ""

  464. 

  465. #: ../../../CHANGELOG.md:246

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

  467. msgstr ""

  468. 

  469. #: ../../../CHANGELOG.md:248

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

  471. msgstr ""

  472. 

  473. #: ../../../CHANGELOG.md:250

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

  475. msgstr ""

  476. 

  477. #: ../../../CHANGELOG.md:252

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

  479. msgstr ""

  480. 

  481. #: ../../../CHANGELOG.md:254

  482. msgid "This change:"

  483. msgstr ""

  484. 

  485. #: ../../../CHANGELOG.md:255

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

  487. msgstr ""

  488. 

  489. #: ../../../CHANGELOG.md:256

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

  491. msgstr ""

  492. 

  493. #: ../../../CHANGELOG.md:257

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

  495. msgstr ""

  496. 

  497. #: ../../../CHANGELOG.md:258

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

  499. msgstr ""

  500. 

  501. #: ../../../CHANGELOG.md:260

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

  503. msgstr ""

  504. 

  505. #: ../../../CHANGELOG.md:271

  506. msgid "2025-12-09"

  507. msgstr ""

  508. 

  509. #: ../../../CHANGELOG.md:273

  510. msgid "Traefik Cert Dumper upgrade"

  511. msgstr ""

  512. 

  513. #: ../../../CHANGELOG.md:275

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

  515. msgstr ""

  516. 

  517. #: ../../../CHANGELOG.md:277

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

  519. msgstr ""

  520. 

  521. #: ../../../CHANGELOG.md:279

  522. msgid "2025-11-23"

  523. msgstr ""

  524. 

  525. #: ../../../CHANGELOG.md:281

  526. msgid "Matrix.to support"

  527. msgstr ""

  528. 

  529. #: ../../../CHANGELOG.md:283

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

  531. msgstr ""

  532. 

  533. #: ../../../CHANGELOG.md:285

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

  535. msgstr ""

  536. 

  537. #: ../../../CHANGELOG.md:287

  538. msgid "2025-11-09"

  539. msgstr ""

  540. 

  541. #: ../../../CHANGELOG.md:289

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

  543. msgstr ""

  544. 

  545. #: ../../../CHANGELOG.md:291

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

  547. msgstr ""

  548. 

  549. #: ../../../CHANGELOG.md:293

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

  551. msgstr ""

  552. 

  553. #: ../../../CHANGELOG.md:295

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

  555. msgstr ""

  556. 

  557. #: ../../../CHANGELOG.md:297

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

  559. msgstr ""

  560. 

  561. #: ../../../CHANGELOG.md:299

  562. #: ../../../CHANGELOG.md:331

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

  564. msgstr ""

  565. 

  566. #: ../../../CHANGELOG.md:301

  567. msgid "`matrix_mautrix_facebook_*`"

  568. msgstr ""

  569. 

  570. #: ../../../CHANGELOG.md:302

  571. msgid "`matrix_mautrix_instagram_*`"

  572. msgstr ""

  573. 

  574. #: ../../../CHANGELOG.md:304

  575. #: ../../../CHANGELOG.md:338

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

  577. msgstr ""

  578. 

  579. #: ../../../CHANGELOG.md:306

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

  581. msgstr ""

  582. 

  583. #: ../../../CHANGELOG.md:307

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

  585. msgstr ""

  586. 

  587. #: ../../../CHANGELOG.md:309

  588. msgid "2025-11-08"

  589. msgstr ""

  590. 

  591. #: ../../../CHANGELOG.md:311

  592. msgid "MatrixZulipBridge support"

  593. msgstr ""

  594. 

  595. #: ../../../CHANGELOG.md:313

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

  597. msgstr ""

  598. 

  599. #: ../../../CHANGELOG.md:315

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

  601. msgstr ""

  602. 

  603. #: ../../../CHANGELOG.md:317

  604. msgid "2025-11-07"

  605. msgstr ""

  606. 

  607. #: ../../../CHANGELOG.md:319

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

  609. msgstr ""

  610. 

  611. #: ../../../CHANGELOG.md:321

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

  613. msgstr ""

  614. 

  615. #: ../../../CHANGELOG.md:323

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

  617. msgstr ""

  618. 

  619. #: ../../../CHANGELOG.md:325

  620. msgid "2025-11-05"

  621. msgstr ""

  622. 

  623. #: ../../../CHANGELOG.md:327

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

  625. msgstr ""

  626. 

  627. #: ../../../CHANGELOG.md:329

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

  629. msgstr ""

  630. 

  631. #: ../../../CHANGELOG.md:333

  632. msgid "`matrix_mx_puppet_discord_*`"

  633. msgstr ""

  634. 

  635. #: ../../../CHANGELOG.md:334

  636. msgid "`matrix_mx_puppet_instagram_*`"

  637. msgstr ""

  638. 

  639. #: ../../../CHANGELOG.md:335

  640. msgid "`matrix_mx_puppet_slack_*`"

  641. msgstr ""

  642. 

  643. #: ../../../CHANGELOG.md:336

  644. msgid "`matrix_mx_puppet_twitter_*`"

  645. msgstr ""

  646. 

  647. #: ../../../CHANGELOG.md:340

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

  649. msgstr ""

  650. 

  651. #: ../../../CHANGELOG.md:341

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

  653. msgstr ""

  654. 

  655. #: ../../../CHANGELOG.md:342

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

  657. msgstr ""

  658. 

  659. #: ../../../CHANGELOG.md:343

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

  661. msgstr ""

  662. 

  663. #: ../../../CHANGELOG.md:345

  664. msgid "2025-11-04"

  665. msgstr ""

  666. 

  667. #: ../../../CHANGELOG.md:347

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

  669. msgstr ""

  670. 

  671. #: ../../../CHANGELOG.md:349

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

  673. msgstr ""

  674. 

  675. #: ../../../CHANGELOG.md:351

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

  677. msgstr ""

  678. 

  679. #: ../../../CHANGELOG.md:353

  680. msgid "2025-10-02"

  681. msgstr ""

  682. 

  683. #: ../../../CHANGELOG.md:355

  684. msgid "Element Admin support"

  685. msgstr ""

  686. 

  687. #: ../../../CHANGELOG.md:357

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

  689. msgstr ""

  690. 

  691. #: ../../../CHANGELOG.md:359

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

  693. msgstr ""

  694. 

  695. #: ../../../CHANGELOG.md:361

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

  697. msgstr ""

  698. 

  699. #: ../../../CHANGELOG.md:364

  700. msgid "2025-04-26"

  701. msgstr ""

  702. 

  703. #: ../../../CHANGELOG.md:366

  704. msgid "Continuwuity support"

  705. msgstr ""

  706. 

  707. #: ../../../CHANGELOG.md:368

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

  709. msgstr ""

  710. 

  711. #: ../../../CHANGELOG.md:370

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

  713. msgstr ""

  714. 

  715. #: ../../../CHANGELOG.md:372

  716. #: ../../../CHANGELOG.md:585

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

  718. msgstr ""

  719. 

  720. #: ../../../CHANGELOG.md:374

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

  722. msgstr ""

  723. 

  724. #: ../../../CHANGELOG.md:376

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

  726. msgstr ""

  727. 

  728. #: ../../../CHANGELOG.md:377

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

  730. msgstr ""

  731. 

  732. #: ../../../CHANGELOG.md:379

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

  734. msgstr ""

  735. 

  736. #: ../../../CHANGELOG.md:382

  737. msgid "2025-04-09"

  738. msgstr ""

  739. 

  740. #: ../../../CHANGELOG.md:384

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

  742. msgstr ""

  743. 

  744. #: ../../../CHANGELOG.md:386

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

  746. msgstr ""

  747. 

  748. #: ../../../CHANGELOG.md:388

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

  750. msgstr ""

  751. 

  752. #: ../../../CHANGELOG.md:390

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

  754. msgstr ""

  755. 

  756. #: ../../../CHANGELOG.md:392

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

  758. msgstr ""

  759. 

  760. #: ../../../CHANGELOG.md:394

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

  762. msgstr ""

  763. 

  764. #: ../../../CHANGELOG.md:401

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

  766. msgstr ""

  767. 

  768. #: ../../../CHANGELOG.md:403

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

  770. msgstr ""

  771. 

  772. #: ../../../CHANGELOG.md:406

  773. msgid "2025-03-15"

  774. msgstr ""

  775. 

  776. #: ../../../CHANGELOG.md:408

  777. msgid "Element Call support"

  778. msgstr ""

  779. 

  780. #: ../../../CHANGELOG.md:410

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

  782. msgstr ""

  783. 

  784. #: ../../../CHANGELOG.md:412

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

  786. msgstr ""

  787. 

  788. #: ../../../CHANGELOG.md:414

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

  790. msgstr ""

  791. 

  792. #: ../../../CHANGELOG.md:416

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

  794. msgstr ""

  795. 

  796. #: ../../../CHANGELOG.md:419

  797. msgid "2025-03-08"

  798. msgstr ""

  799. 

  800. #: ../../../CHANGELOG.md:421

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

  802. msgstr ""

  803. 

  804. #: ../../../CHANGELOG.md:423

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

  806. msgstr ""

  807. 

  808. #: ../../../CHANGELOG.md:425

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

  810. msgstr ""

  811. 

  812. #: ../../../CHANGELOG.md:427

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

  814. msgstr ""

  815. 

  816. #: ../../../CHANGELOG.md:429

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

  818. msgstr ""

  819. 

  820. #: ../../../CHANGELOG.md:430

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

  822. msgstr ""

  823. 

  824. #: ../../../CHANGELOG.md:431

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

  826. msgstr ""

  827. 

  828. #: ../../../CHANGELOG.md:432

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

  830. msgstr ""

  831. 

  832. #: ../../../CHANGELOG.md:433

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

  834. msgstr ""

  835. 

  836. #: ../../../CHANGELOG.md:435

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

  838. msgstr ""

  839. 

  840. #: ../../../CHANGELOG.md:437

  841. msgid "2025-02-26"

  842. msgstr ""

  843. 

  844. #: ../../../CHANGELOG.md:439

  845. msgid "🪦 Bye-bye, Email2Matrix"

  846. msgstr ""

  847. 

  848. #: ../../../CHANGELOG.md:441

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

  850. msgstr ""

  851. 

  852. #: ../../../CHANGELOG.md:443

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

  854. msgstr ""

  855. 

  856. #: ../../../CHANGELOG.md:446

  857. msgid "2025-02-23"

  858. msgstr ""

  859. 

  860. #: ../../../CHANGELOG.md:448

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

  862. msgstr ""

  863. 

  864. #: ../../../CHANGELOG.md:450

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

  866. msgstr ""

  867. 

  868. #: ../../../CHANGELOG.md:452

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

  870. msgstr ""

  871. 

  872. #: ../../../CHANGELOG.md:455

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

  874. msgstr ""

  875. 

  876. #: ../../../CHANGELOG.md:457

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

  878. msgstr ""

  879. 

  880. #: ../../../CHANGELOG.md:459

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

  882. msgstr ""

  883. 

  884. #: ../../../CHANGELOG.md:461

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

  886. msgstr ""

  887. 

  888. #: ../../../CHANGELOG.md:463

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

  890. msgstr ""

  891. 

  892. #: ../../../CHANGELOG.md:469

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

  894. msgstr ""

  895. 

  896. #: ../../../CHANGELOG.md:471

  897. msgid "2025-02-21"

  898. msgstr ""

  899. 

  900. #: ../../../CHANGELOG.md:473

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

  902. msgstr ""

  903. 

  904. #: ../../../CHANGELOG.md:475

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

  906. msgstr ""

  907. 

  908. #: ../../../CHANGELOG.md:477

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

  910. msgstr ""

  911. 

  912. #: ../../../CHANGELOG.md:479

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

  914. msgstr ""

  915. 

  916. #: ../../../CHANGELOG.md:480

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

  918. msgstr ""

  919. 

  920. #: ../../../CHANGELOG.md:482

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

  922. msgstr ""

  923. 

  924. #: ../../../CHANGELOG.md:483

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

  926. msgstr ""

  927. 

  928. #: ../../../CHANGELOG.md:484

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

  930. msgstr ""

  931. 

  932. #: ../../../CHANGELOG.md:486

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

  934. msgstr ""

  935. 

  936. #: ../../../CHANGELOG.md:489

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

  938. msgstr ""

  939. 

  940. #: ../../../CHANGELOG.md:491

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

  942. msgstr ""

  943. 

  944. #: ../../../CHANGELOG.md:492

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

  946. msgstr ""

  947. 

  948. #: ../../../CHANGELOG.md:493

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

  950. msgstr ""

  951. 

  952. #: ../../../CHANGELOG.md:494

  953. msgid "🔧 .. and you're on an old Docker version, you **are affected** and need to use the following configuration to restore the old behavior:"

  954. msgstr ""

  955. 

  956. #: ../../../CHANGELOG.md:505

  957. msgid "Support for bridging to Bluesky via mautrix-bluesky"

  958. msgstr ""

  959. 

  960. #: ../../../CHANGELOG.md:507

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

  962. msgstr ""

  963. 

  964. #: ../../../CHANGELOG.md:509

  965. msgid "To learn more, see our [Setting up mautrix-bluesky](./docs/configuring-playbook-bridge-mautrix-bluesky.md) documentation page."

  966. msgstr ""

  967. 

  968. #: ../../../CHANGELOG.md:512

  969. msgid "2025-02-19"

  970. msgstr ""

  971. 

  972. #: ../../../CHANGELOG.md:514

  973. msgid "The playbook now defaults to exposing the Coturn STUN port (3478) only over TCP"

  974. msgstr ""

  975. 

  976. #: ../../../CHANGELOG.md:516

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

  978. msgstr ""

  979. 

  980. #: ../../../CHANGELOG.md:518

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

  982. msgstr ""

  983. 

  984. #: ../../../CHANGELOG.md:520

  985. msgid "The playbook now **only exposes the Coturn STUN port (`3478`) over TCP by default**."

  986. msgstr ""

  987. 

  988. #: ../../../CHANGELOG.md:522

  989. msgid "💡 Users may wish to further remove the (now unnecessary) firewall rule allowing access to `3478/udp`."

  990. msgstr ""

  991. 

  992. #: ../../../CHANGELOG.md:524

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

  994. msgstr ""

  995. 

  996. #: ../../../CHANGELOG.md:530

  997. msgid "[!WARNING] 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)."

  998. msgstr ""

  999. 

  1000. #: ../../../CHANGELOG.md:534

  1001. msgid "2025-02-17"

  1002. msgstr ""

  1003. 

  1004. #: ../../../CHANGELOG.md:536

  1005. msgid "FluffyChat Web support"

  1006. msgstr ""

  1007. 

  1008. #: ../../../CHANGELOG.md:538

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

  1010. msgstr ""

  1011. 

  1012. #: ../../../CHANGELOG.md:540

  1013. msgid "To learn more, see our [Setting up FluffyChat Web](docs/configuring-playbook-client-fluffychat-web.md) documentation page."

  1014. msgstr ""

  1015. 

  1016. #: ../../../CHANGELOG.md:543

  1017. msgid "2025-02-03"

  1018. msgstr ""

  1019. 

  1020. #: ../../../CHANGELOG.md:545

  1021. msgid "The mautrix-hangouts bridge has been removed from the playbook"

  1022. msgstr ""

  1023. 

  1024. #: ../../../CHANGELOG.md:547

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

  1026. msgstr ""

  1027. 

  1028. #: ../../../CHANGELOG.md:549

  1029. msgid "This is because Google Hangouts has been discontinued since the 1st of November 2022."

  1030. msgstr ""

  1031. 

  1032. #: ../../../CHANGELOG.md:551

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

  1034. msgstr ""

  1035. 

  1036. #: ../../../CHANGELOG.md:554

  1037. msgid "2025-01-27"

  1038. msgstr ""

  1039. 

  1040. #: ../../../CHANGELOG.md:556

  1041. msgid "Redis and KeyDB are no longer part of the playbook"

  1042. msgstr ""

  1043. 

  1044. #: ../../../CHANGELOG.md:558

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

  1046. msgstr ""

  1047. 

  1048. #: ../../../CHANGELOG.md:560

  1049. msgid "The playbook has gone through several iterations of memorystore implementations:"

  1050. msgstr ""

  1051. 

  1052. #: ../../../CHANGELOG.md:562

  1053. msgid "It initially used Redis, auto-installing it when needed by features/services"

  1054. msgstr ""

  1055. 

  1056. #: ../../../CHANGELOG.md:563

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

  1058. msgstr ""

  1059. 

  1060. #: ../../../CHANGELOG.md:564

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

  1062. msgstr ""

  1063. 

  1064. #: ../../../CHANGELOG.md:566

  1065. msgid "To reduce configuration complexity and maintenance overhead, we are now:"

  1066. msgstr ""

  1067. 

  1068. #: ../../../CHANGELOG.md:568

  1069. msgid "removing Redis and KeyDB support entirely"

  1070. msgstr ""

  1071. 

  1072. #: ../../../CHANGELOG.md:569

  1073. msgid "using Valkey as the sole Redis-compatible memorystore implementation"

  1074. msgstr ""

  1075. 

  1076. #: ../../../CHANGELOG.md:571

  1077. msgid "To update your configuration:"

  1078. msgstr ""

  1079. 

  1080. #: ../../../CHANGELOG.md:573

  1081. msgid "**Most users** don't need to do anything"

  1082. msgstr ""

  1083. 

  1084. #: ../../../CHANGELOG.md:574

  1085. msgid "**Users that were explicitly sticking to Redis/KeyDB** need to update their `vars.yml` to use `valkey_*` variables instead"

  1086. msgstr ""

  1087. 

  1088. #: ../../../CHANGELOG.md:577

  1089. msgid "2025-01-19"

  1090. msgstr ""

  1091. 

  1092. #: ../../../CHANGELOG.md:579

  1093. msgid "conduwuit support"

  1094. msgstr ""

  1095. 

  1096. #: ../../../CHANGELOG.md:581

  1097. msgid "Thanks to [Virkkunen](https://github.com/Virkkunen), we now have optional experimental [conduwuit](https://conduwuit.puppyirl.gay/) homeserver support for new installations."

  1098. msgstr ""

  1099. 

  1100. #: ../../../CHANGELOG.md:583

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

  1102. msgstr ""

  1103. 

  1104. #: ../../../CHANGELOG.md:587

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

  1106. msgstr ""

  1107. 

  1108. #: ../../../CHANGELOG.md:589

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

  1110. msgstr ""

  1111. 

  1112. #: ../../../CHANGELOG.md:592

  1113. msgid "2025-01-14"

  1114. msgstr ""

  1115. 

  1116. #: ../../../CHANGELOG.md:594

  1117. msgid "(Backward Compatibility Break) Synapse v1.122.0 requires Postgres v13"

  1118. msgstr ""

  1119. 

  1120. #: ../../../CHANGELOG.md:596

  1121. msgid "The Synapse homeserver [requires Postgres v13 or newer](https://github.com/element-hq/synapse/issues/18034)."

  1122. msgstr ""

  1123. 

  1124. #: ../../../CHANGELOG.md:598

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

  1126. msgstr ""

  1127. 

  1128. #: ../../../CHANGELOG.md:600

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

  1130. msgstr ""

  1131. 

  1132. #: ../../../CHANGELOG.md:602

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

  1134. msgstr ""

  1135. 

  1136. #: ../../../CHANGELOG.md:604

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

  1138. msgstr ""

  1139. 

  1140. #: ../../../CHANGELOG.md:612

  1141. msgid "2024-11-26"

  1142. msgstr ""

  1143. 

  1144. #: ../../../CHANGELOG.md:614

  1145. msgid "(Backward Compatibility Break) Synapse now defaults to enabling authenticated media"

  1146. msgstr ""

  1147. 

  1148. #: ../../../CHANGELOG.md:616

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

  1150. msgstr ""

  1151. 

  1152. #: ../../../CHANGELOG.md:618

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

  1154. msgstr ""

  1155. 

  1156. #: ../../../CHANGELOG.md:620

  1157. msgid "Servers like `matrix.org` have already [sunset unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) months ago."

  1158. msgstr ""

  1159. 

  1160. #: ../../../CHANGELOG.md:622

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

  1162. msgstr ""

  1163. 

  1164. #: ../../../CHANGELOG.md:624

  1165. msgid "We're changing the playbook configuration for authenticated media to keep up with upstream defaults changing."

  1166. msgstr ""

  1167. 

  1168. #: ../../../CHANGELOG.md:626

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

  1170. msgstr ""

  1171. 

  1172. #: ../../../CHANGELOG.md:628

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

  1174. msgstr ""

  1175. 

  1176. #: ../../../CHANGELOG.md:631

  1177. msgid "2024-11-23"

  1178. msgstr ""

  1179. 

  1180. #: ../../../CHANGELOG.md:633

  1181. msgid "(Backward Compatibility Break) The playbook now defaults to Valkey, instead of KeyDB"

  1182. msgstr ""

  1183. 

  1184. #: ../../../CHANGELOG.md:635

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

  1186. msgstr ""

  1187. 

  1188. #: ../../../CHANGELOG.md:637

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

  1190. msgstr ""

  1191. 

  1192. #: ../../../CHANGELOG.md:639

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

  1194. msgstr ""

  1195. 

  1196. #: ../../../CHANGELOG.md:641

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

  1198. msgstr ""

  1199. 

  1200. #: ../../../CHANGELOG.md:643

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

  1202. msgstr ""

  1203. 

  1204. #: ../../../CHANGELOG.md:645

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

  1206. msgstr ""

  1207. 

  1208. #: ../../../CHANGELOG.md:647

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

  1210. msgstr ""

  1211. 

  1212. #: ../../../CHANGELOG.md:649

  1213. #: ../../../CHANGELOG.md:989

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

  1215. msgstr ""

  1216. 

  1217. #: ../../../CHANGELOG.md:660

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

  1219. msgstr ""

  1220. 

  1221. #: ../../../CHANGELOG.md:670

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

  1223. msgstr ""

  1224. 

  1225. #: ../../../CHANGELOG.md:673

  1226. msgid "2024-11-14"

  1227. msgstr ""

  1228. 

  1229. #: ../../../CHANGELOG.md:675

  1230. msgid "HTTP-compression support for Traefik-based setups"

  1231. msgstr ""

  1232. 

  1233. #: ../../../CHANGELOG.md:677

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

  1235. msgstr ""

  1236. 

  1237. #: ../../../CHANGELOG.md:679

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

  1239. msgstr ""

  1240. 

  1241. #: ../../../CHANGELOG.md:681

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

  1243. msgstr ""

  1244. 

  1245. #: ../../../CHANGELOG.md:683

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

  1247. msgstr ""

  1248. 

  1249. #: ../../../CHANGELOG.md:685

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

  1251. msgstr ""

  1252. 

  1253. #: ../../../CHANGELOG.md:687

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

  1255. msgstr ""

  1256. 

  1257. #: ../../../CHANGELOG.md:688

  1258. msgid "setting `matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled` to `true`"

  1259. msgstr ""

  1260. 

  1261. #: ../../../CHANGELOG.md:689

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

  1263. msgstr ""

  1264. 

  1265. #: ../../../CHANGELOG.md:691

  1266. msgid "Timeout adjustments for Traefik-based setups"

  1267. msgstr ""

  1268. 

  1269. #: ../../../CHANGELOG.md:693

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

  1271. msgstr ""

  1272. 

  1273. #: ../../../CHANGELOG.md:695

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

  1275. msgstr ""

  1276. 

  1277. #: ../../../CHANGELOG.md:697

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

  1279. msgstr ""

  1280. 

  1281. #: ../../../CHANGELOG.md:699

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

  1283. msgstr ""

  1284. 

  1285. #: ../../../CHANGELOG.md:701

  1286. msgid "Example of the default timeout values used by the playbook:"

  1287. msgstr ""

  1288. 

  1289. #: ../../../CHANGELOG.md:712

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

  1291. msgstr ""

  1292. 

  1293. #: ../../../CHANGELOG.md:715

  1294. msgid "2024-11-08"

  1295. msgstr ""

  1296. 

  1297. #: ../../../CHANGELOG.md:717

  1298. msgid "Support for synapse-admin auto-configuration via /.well-known/matrix/client"

  1299. msgstr ""

  1300. 

  1301. #: ../../../CHANGELOG.md:719

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

  1303. msgstr ""

  1304. 

  1305. #: ../../../CHANGELOG.md:721

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

  1307. msgstr ""

  1308. 

  1309. #: ../../../CHANGELOG.md:723

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

  1311. msgstr ""

  1312. 

  1313. #: ../../../CHANGELOG.md:726

  1314. msgid "2024-10-28"

  1315. msgstr ""

  1316. 

  1317. #: ../../../CHANGELOG.md:728

  1318. msgid "(BC Break) Postmoogle's variable names need adjustments"

  1319. msgstr ""

  1320. 

  1321. #: ../../../CHANGELOG.md:730

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

  1323. msgstr ""

  1324. 

  1325. #: ../../../CHANGELOG.md:732

  1326. msgid "2024-10-19"

  1327. msgstr ""

  1328. 

  1329. #: ../../../CHANGELOG.md:734

  1330. msgid "Support for Matrix Authentication Service"

  1331. msgstr ""

  1332. 

  1333. #: ../../../CHANGELOG.md:736

  1334. msgid "The playbook now supports installing and configuring [Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) (MAS)."

  1335. msgstr ""

  1336. 

  1337. #: ../../../CHANGELOG.md:738

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

  1339. msgstr ""

  1340. 

  1341. #: ../../../CHANGELOG.md:740

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

  1343. msgstr ""

  1344. 

  1345. #: ../../../CHANGELOG.md:742

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

  1347. msgstr ""

  1348. 

  1349. #: ../../../CHANGELOG.md:745

  1350. msgid "2024-09-27"

  1351. msgstr ""

  1352. 

  1353. #: ../../../CHANGELOG.md:747

  1354. msgid "(BC Break) Postgres & Traefik roles have been relocated and variable names need adjustments"

  1355. msgstr ""

  1356. 

  1357. #: ../../../CHANGELOG.md:749

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

  1359. msgstr ""

  1360. 

  1361. #: ../../../CHANGELOG.md:751

  1362. msgid "Along with the relocation, the `devture_` prefix was dropped from their variable names, so you need to adjust your `vars.yml` configuration."

  1363. msgstr ""

  1364. 

  1365. #: ../../../CHANGELOG.md:753

  1366. msgid "You need to do the following replacements:"

  1367. msgstr ""

  1368. 

  1369. #: ../../../CHANGELOG.md:755

  1370. msgid "`devture_postgres_` -> `postgres_`"

  1371. msgstr ""

  1372. 

  1373. #: ../../../CHANGELOG.md:756

  1374. msgid "`devture_traefik_` -> `traefik_`"

  1375. msgstr ""

  1376. 

  1377. #: ../../../CHANGELOG.md:761

  1378. msgid "2024-09-12"

  1379. msgstr ""

  1380. 

  1381. #: ../../../CHANGELOG.md:763

  1382. msgid "Support for baibot"

  1383. msgstr ""

  1384. 

  1385. #: ../../../CHANGELOG.md:765

  1386. 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. 🤖"

  1387. msgstr ""

  1388. 

  1389. #: ../../../CHANGELOG.md:767

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

  1391. msgstr ""

  1392. 

  1393. #: ../../../CHANGELOG.md:769

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

  1395. msgstr ""

  1396. 

  1397. #: ../../../CHANGELOG.md:771

  1398. msgid "To get started, see the [Setting up baibot](./docs/configuring-playbook-bot-baibot.md) documentation page."

  1399. msgstr ""

  1400. 

  1401. #: ../../../CHANGELOG.md:773

  1402. msgid "Switching synapse-admin to etke.cc's fork"

  1403. msgstr ""

  1404. 

  1405. #: ../../../CHANGELOG.md:775

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

  1407. msgstr ""

  1408. 

  1409. #: ../../../CHANGELOG.md:777

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

  1411. msgstr ""

  1412. 

  1413. #: ../../../CHANGELOG.md:779

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

  1415. msgstr ""

  1416. 

  1417. #: ../../../CHANGELOG.md:781

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

  1419. msgstr ""

  1420. 

  1421. #: ../../../CHANGELOG.md:794

  1422. msgid "2024-08-17"

  1423. msgstr ""

  1424. 

  1425. #: ../../../CHANGELOG.md:796

  1426. msgid "New appservice-double-puppet service for better double-puppeting"

  1427. msgstr ""

  1428. 

  1429. #: ../../../CHANGELOG.md:798

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

  1431. msgstr ""

  1432. 

  1433. #: ../../../CHANGELOG.md:800

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

  1435. msgstr ""

  1436. 

  1437. #: ../../../CHANGELOG.md:802

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

  1439. msgstr ""

  1440. 

  1441. #: ../../../CHANGELOG.md:804

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

  1443. msgstr ""

  1444. 

  1445. #: ../../../CHANGELOG.md:806

  1446. msgid "We recommend **enabling double-puppeting via the new Appservice method** by adding the following configuration to your `vars.yml` file:"

  1447. msgstr ""

  1448. 

  1449. #: ../../../CHANGELOG.md:812

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

  1451. msgstr ""

  1452. 

  1453. #: ../../../CHANGELOG.md:814

  1454. msgid "When both double-puppeting methods are enabled, the playbook will automatically choose the new and better Appservice method for bridges that support it."

  1455. msgstr ""

  1456. 

  1457. #: ../../../CHANGELOG.md:817

  1458. msgid "2024-08-15"

  1459. msgstr ""

  1460. 

  1461. #: ../../../CHANGELOG.md:819

  1462. msgid "matrix-media-repo now configured for Authenticated Media"

  1463. msgstr ""

  1464. 

  1465. #: ../../../CHANGELOG.md:821

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

  1467. msgstr ""

  1468. 

  1469. #: ../../../CHANGELOG.md:823

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

  1471. msgstr ""

  1472. 

  1473. #: ../../../CHANGELOG.md:825

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

  1475. msgstr ""

  1476. 

  1477. #: ../../../CHANGELOG.md:827

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

  1479. msgstr ""

  1480. 

  1481. #: ../../../CHANGELOG.md:830

  1482. msgid "2024-08-08"

  1483. msgstr ""

  1484. 

  1485. #: ../../../CHANGELOG.md:832

  1486. msgid "(Backward Compatibility Break) matrix-corporal has been upgraded to v3"

  1487. msgstr ""

  1488. 

  1489. #: ../../../CHANGELOG.md:834

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

  1491. msgstr ""

  1492. 

  1493. #: ../../../CHANGELOG.md:836

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

  1495. msgstr ""

  1496. 

  1497. #: ../../../CHANGELOG.md:838

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

  1499. msgstr ""

  1500. 

  1501. #: ../../../CHANGELOG.md:844

  1502. msgid "2024-07-25"

  1503. msgstr ""

  1504. 

  1505. #: ../../../CHANGELOG.md:846

  1506. msgid "synapse-usage-exporter support"

  1507. msgstr ""

  1508. 

  1509. #: ../../../CHANGELOG.md:848

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

  1511. msgstr ""

  1512. 

  1513. #: ../../../CHANGELOG.md:850

  1514. msgid "To learn more see our [Enabling synapse-usage-exporter for Synapse usage statistics](docs/configuring-playbook-synapse-usage-exporter.md) documentation page."

  1515. msgstr ""

  1516. 

  1517. #: ../../../CHANGELOG.md:853

  1518. msgid "2024-07-06"

  1519. msgstr ""

  1520. 

  1521. #: ../../../CHANGELOG.md:855

  1522. msgid "matrix-alertmanager-receiver support"

  1523. msgstr ""

  1524. 

  1525. #: ../../../CHANGELOG.md:857

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

  1527. msgstr ""

  1528. 

  1529. #: ../../../CHANGELOG.md:859

  1530. msgid "See [Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](./docs/configuring-playbook-alertmanager-receiver.md) for more details."

  1531. msgstr ""

  1532. 

  1533. #: ../../../CHANGELOG.md:861

  1534. msgid "Traefik v3 and HTTP/3 are here now"

  1535. msgstr ""

  1536. 

  1537. #: ../../../CHANGELOG.md:863

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

  1539. msgstr ""

  1540. 

  1541. #: ../../../CHANGELOG.md:865

  1542. msgid "Traefik v3"

  1543. msgstr ""

  1544. 

  1545. #: ../../../CHANGELOG.md:867

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

  1547. msgstr ""

  1548. 

  1549. #: ../../../CHANGELOG.md:869

  1550. msgid "We have **updated the playbook to Traefik v3** (make sure to run `just roles` / `make roles` to get it)."

  1551. msgstr ""

  1552. 

  1553. #: ../../../CHANGELOG.md:871

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

  1555. msgstr ""

  1556. 

  1557. #: ../../../CHANGELOG.md:873

  1558. msgid "**Most people using the playbook should not have to do any changes**."

  1559. msgstr ""

  1560. 

  1561. #: ../../../CHANGELOG.md:875

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

  1563. msgstr ""

  1564. 

  1565. #: ../../../CHANGELOG.md:877

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

  1567. msgstr ""

  1568. 

  1569. #: ../../../CHANGELOG.md:879

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

  1571. msgstr ""

  1572. 

  1573. #: ../../../CHANGELOG.md:881

  1574. msgid "HTTP/3 is enabled by default"

  1575. msgstr ""

  1576. 

  1577. #: ../../../CHANGELOG.md:883

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

  1579. msgstr ""

  1580. 

  1581. #: ../../../CHANGELOG.md:885

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

  1583. msgstr ""

  1584. 

  1585. #: ../../../CHANGELOG.md:887

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

  1587. msgstr ""

  1588. 

  1589. #: ../../../CHANGELOG.md:889

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

  1591. msgstr ""

  1592. 

  1593. #: ../../../CHANGELOG.md:891

  1594. msgid "To **disable HTTP/3**, you can use the following configuration:"

  1595. msgstr ""

  1596. 

  1597. #: ../../../CHANGELOG.md:905

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

  1599. msgstr ""

  1600. 

  1601. #: ../../../CHANGELOG.md:918

  1602. msgid "2024-07-01"

  1603. msgstr ""

  1604. 

  1605. #: ../../../CHANGELOG.md:920

  1606. msgid "synapse-admin is now restricted to your homeserver's URL by default"

  1607. msgstr ""

  1608. 

  1609. #: ../../../CHANGELOG.md:922

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

  1611. msgstr ""

  1612. 

  1613. #: ../../../CHANGELOG.md:924

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

  1615. msgstr ""

  1616. 

  1617. #: ../../../CHANGELOG.md:926

  1618. msgid "If you'd like **to go back to the old unrestricted behavior**, use the following configuration:"

  1619. msgstr ""

  1620. 

  1621. #: ../../../CHANGELOG.md:934

  1622. msgid "2024-06-25"

  1623. msgstr ""

  1624. 

  1625. #: ../../../CHANGELOG.md:936

  1626. msgid "The URL-prefix for Hookshot generic webhooks has changed"

  1627. msgstr ""

  1628. 

  1629. #: ../../../CHANGELOG.md:938

  1630. msgid "Until now, generic Hookshot webhook URLs looked like this: `https://matrix.example.com/hookshot/webhooks/:hookId`."

  1631. msgstr ""

  1632. 

  1633. #: ../../../CHANGELOG.md:940

  1634. msgid "The `/hookshot/webhooks` common prefix gets stripped by Traefik automatically, so Hookshot only sees the part that comes after (`/:hookId`)."

  1635. msgstr ""

  1636. 

  1637. #: ../../../CHANGELOG.md:942

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

  1639. msgstr ""

  1640. 

  1641. #: ../../../CHANGELOG.md:944

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

  1643. msgstr ""

  1644. 

  1645. #: ../../../CHANGELOG.md:946

  1646. msgid "When generating new webhooks, you should start seeing the new URLs being used."

  1647. msgstr ""

  1648. 

  1649. #: ../../../CHANGELOG.md:948

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

  1651. msgstr ""

  1652. 

  1653. #: ../../../CHANGELOG.md:950

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

  1655. msgstr ""

  1656. 

  1657. #: ../../../CHANGELOG.md:953

  1658. msgid "2024-06-22"

  1659. msgstr ""

  1660. 

  1661. #: ../../../CHANGELOG.md:955

  1662. msgid "The maubot user is now managed by the playbook"

  1663. msgstr ""

  1664. 

  1665. #: ../../../CHANGELOG.md:957

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

  1667. msgstr ""

  1668. 

  1669. #: ../../../CHANGELOG.md:959

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

  1671. msgstr ""

  1672. 

  1673. #: ../../../CHANGELOG.md:961

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

  1675. msgstr ""

  1676. 

  1677. #: ../../../CHANGELOG.md:964

  1678. msgid "2024-06-03"

  1679. msgstr ""

  1680. 

  1681. #: ../../../CHANGELOG.md:966

  1682. msgid "WeChat bridging support"

  1683. msgstr ""

  1684. 

  1685. #: ../../../CHANGELOG.md:968

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

  1687. msgstr ""

  1688. 

  1689. #: ../../../CHANGELOG.md:970

  1690. msgid "See our [Setting up WeChat bridging](docs/configuring-playbook-bridge-wechat.md) documentation page for getting started."

  1691. msgstr ""

  1692. 

  1693. #: ../../../CHANGELOG.md:973

  1694. msgid "2024-03-26"

  1695. msgstr ""

  1696. 

  1697. #: ../../../CHANGELOG.md:975

  1698. msgid "(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis"

  1699. msgstr ""

  1700. 

  1701. #: ../../../CHANGELOG.md:977

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

  1703. msgstr ""

  1704. 

  1705. #: ../../../CHANGELOG.md:979

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

  1707. msgstr ""

  1708. 

  1709. #: ../../../CHANGELOG.md:981

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

  1711. msgstr ""

  1712. 

  1713. #: ../../../CHANGELOG.md:983

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

  1715. msgstr ""

  1716. 

  1717. #: ../../../CHANGELOG.md:985

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

  1719. msgstr ""

  1720. 

  1721. #: ../../../CHANGELOG.md:987

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

  1723. msgstr ""

  1724. 

  1725. #: ../../../CHANGELOG.md:998

  1726. msgid "2024-03-24"

  1727. msgstr ""

  1728. 

  1729. #: ../../../CHANGELOG.md:1000

  1730. msgid "Initial work on IPv6 support"

  1731. msgstr ""

  1732. 

  1733. #: ../../../CHANGELOG.md:1002

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

  1735. msgstr ""

  1736. 

  1737. #: ../../../CHANGELOG.md:1004

  1738. msgid "It should be noted that:"

  1739. msgstr ""

  1740. 

  1741. #: ../../../CHANGELOG.md:1006

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

  1743. msgstr ""

  1744. 

  1745. #: ../../../CHANGELOG.md:1007

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

  1747. msgstr ""

  1748. 

  1749. #: ../../../CHANGELOG.md:1008

  1750. msgid "this is all very new and untested"

  1751. msgstr ""

  1752. 

  1753. #: ../../../CHANGELOG.md:1010

  1754. msgid "Pantalaimon support"

  1755. msgstr ""

  1756. 

  1757. #: ../../../CHANGELOG.md:1012

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

  1759. msgstr ""

  1760. 

  1761. #: ../../../CHANGELOG.md:1014

  1762. msgid "See our [Setting up Pantalaimon](docs/configuring-playbook-pantalaimon.md) documentation to get started."

  1763. msgstr ""

  1764. 

  1765. #: ../../../CHANGELOG.md:1017

  1766. msgid "2024-03-05"

  1767. msgstr ""

  1768. 

  1769. #: ../../../CHANGELOG.md:1019

  1770. msgid "Support for Draupnir-for-all"

  1771. msgstr ""

  1772. 

  1773. #: ../../../CHANGELOG.md:1021

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

  1775. msgstr ""

  1776. 

  1777. #: ../../../CHANGELOG.md:1023

  1778. msgid "This is an alternative to [running Draupnir in bot mode](./docs/configuring-playbook-bot-draupnir.md), which is still supported by the playbook."

  1779. msgstr ""

  1780. 

  1781. #: ../../../CHANGELOG.md:1025

  1782. msgid "The documentation page for [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) contains more information on how to install it."

  1783. msgstr ""

  1784. 

  1785. #: ../../../CHANGELOG.md:1028

  1786. msgid "2024-02-19"

  1787. msgstr ""

  1788. 

  1789. #: ../../../CHANGELOG.md:1030

  1790. msgid "Support for bridging to Facebook/Messenger via the new mautrix-meta bridge"

  1791. msgstr ""

  1792. 

  1793. #: ../../../CHANGELOG.md:1032

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

  1795. msgstr ""

  1796. 

  1797. #: ../../../CHANGELOG.md:1034

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

  1799. msgstr ""

  1800. 

  1801. #: ../../../CHANGELOG.md:1036

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

  1803. msgstr ""

  1804. 

  1805. #: ../../../CHANGELOG.md:1038

  1806. msgid "[Setting up Instagram bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)"

  1807. msgstr ""

  1808. 

  1809. #: ../../../CHANGELOG.md:1040

  1810. msgid "[Setting up Messenger bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-messenger.md)"

  1811. msgstr ""

  1812. 

  1813. #: ../../../CHANGELOG.md:1042

  1814. msgid "The documentation pages contain more information on how to migrate."

  1815. msgstr ""

  1816. 

  1817. #: ../../../CHANGELOG.md:1045

  1818. msgid "2024-02-14"

  1819. msgstr ""

  1820. 

  1821. #: ../../../CHANGELOG.md:1047

  1822. msgid "Much larger Synapse caches and cache auto-tuning enabled by default"

  1823. msgstr ""

  1824. 

  1825. #: ../../../CHANGELOG.md:1049

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

  1827. msgstr ""

  1828. 

  1829. #: ../../../CHANGELOG.md:1051

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

  1831. msgstr ""

  1832. 

  1833. #: ../../../CHANGELOG.md:1053

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

  1835. msgstr ""

  1836. 

  1837. #: ../../../CHANGELOG.md:1055

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

  1839. msgstr ""

  1840. 

  1841. #: ../../../CHANGELOG.md:1056

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

  1843. msgstr ""

  1844. 

  1845. #: ../../../CHANGELOG.md:1057

  1846. msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` — defaults to `30s`"

  1847. msgstr ""

  1848. 

  1849. #: ../../../CHANGELOG.md:1059

  1850. msgid "These values should be good defaults for most servers, but may change over time as we experiment further."

  1851. msgstr ""

  1852. 

  1853. #: ../../../CHANGELOG.md:1061

  1854. msgid "Refer to our new [Tuning caches and cache autotuning](docs/maintenance-synapse.md#tuning-caches-and-cache-autotuning) documentation section for more details."

  1855. msgstr ""

  1856. 

  1857. #: ../../../CHANGELOG.md:1064

  1858. msgid "2024-01-31"

  1859. msgstr ""

  1860. 

  1861. #: ../../../CHANGELOG.md:1066

  1862. msgid "(Backward-compatibility break) Minor changes necessary for some people serving a static website at the base domain"

  1863. msgstr ""

  1864. 

  1865. #: ../../../CHANGELOG.md:1068

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

  1867. msgstr ""

  1868. 

  1869. #: ../../../CHANGELOG.md:1070

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

  1871. msgstr ""

  1872. 

  1873. #: ../../../CHANGELOG.md:1072

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

  1875. msgstr ""

  1876. 

  1877. #: ../../../CHANGELOG.md:1075

  1878. msgid "2024-01-20"

  1879. msgstr ""

  1880. 

  1881. #: ../../../CHANGELOG.md:1077

  1882. msgid "Support for more efficient (specialized) Synapse workers"

  1883. msgstr ""

  1884. 

  1885. #: ../../../CHANGELOG.md:1079

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

  1887. msgstr ""

  1888. 

  1889. #: ../../../CHANGELOG.md:1081

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

  1891. msgstr ""

  1892. 

  1893. #: ../../../CHANGELOG.md:1083

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

  1895. msgstr ""

  1896. 

  1897. #: ../../../CHANGELOG.md:1085

  1898. msgid "To get started, refer to our [Specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) documentation section."

  1899. msgstr ""

  1900. 

  1901. #: ../../../CHANGELOG.md:1088

  1902. msgid "2024-01-17"

  1903. msgstr ""

  1904. 

  1905. #: ../../../CHANGELOG.md:1090

  1906. msgid "Switching to Element's AGPLv3-licensed Synapse release"

  1907. msgstr ""

  1908. 

  1909. #: ../../../CHANGELOG.md:1092

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

  1911. msgstr ""

  1912. 

  1913. #: ../../../CHANGELOG.md:1094

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

  1915. msgstr ""

  1916. 

  1917. #: ../../../CHANGELOG.md:1095

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

  1919. msgstr ""

  1920. 

  1921. #: ../../../CHANGELOG.md:1097

  1922. msgid "You can also learn more in [this post](https://matrix.org/blog/2023/11/06/future-of-synapse-dendrite/) by the Matrix Foundation."

  1923. msgstr ""

  1924. 

  1925. #: ../../../CHANGELOG.md:1099

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

  1927. msgstr ""

  1928. 

  1929. #: ../../../CHANGELOG.md:1101

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

  1931. msgstr ""

  1932. 

  1933. #: ../../../CHANGELOG.md:1103

  1934. msgid "**What does this mean to you?**"

  1935. msgstr ""

  1936. 

  1937. #: ../../../CHANGELOG.md:1105

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

  1939. msgstr ""

  1940. 

  1941. #: ../../../CHANGELOG.md:1107

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

  1943. msgstr ""

  1944. 

  1945. #: ../../../CHANGELOG.md:1109

  1946. 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!"

  1947. msgstr ""

  1948. 

  1949. #: ../../../CHANGELOG.md:1111

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

  1951. msgstr ""

  1952. 

  1953. #: ../../../CHANGELOG.md:1123

  1954. msgid "Notes:"

  1955. msgstr ""

  1956. 

  1957. #: ../../../CHANGELOG.md:1125

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

  1959. msgstr ""

  1960. 

  1961. #: ../../../CHANGELOG.md:1127

  1962. msgid "running an outdated homeserver exposes you to security issues and incompatibilities. Only consider doing this as a short-term solution."

  1963. msgstr ""

  1964. 

  1965. #: ../../../CHANGELOG.md:1129

  1966. msgid "2024-01-16"

  1967. msgstr ""

  1968. 

  1969. #: ../../../CHANGELOG.md:1131

  1970. msgid "`Draupnir` has been relicensed to AFL-3.0"

  1971. msgstr ""

  1972. 

  1973. #: ../../../CHANGELOG.md:1133

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

  1975. msgstr ""

  1976. 

  1977. #: ../../../CHANGELOG.md:1135

  1978. msgid "2024-01-15"

  1979. msgstr ""

  1980. 

  1981. #: ../../../CHANGELOG.md:1137

  1982. msgid "Goodbye, `matrix-nginx-proxy` 🪦"

  1983. msgstr ""

  1984. 

  1985. #: ../../../CHANGELOG.md:1139

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

  1987. msgstr ""

  1988. 

  1989. #: ../../../CHANGELOG.md:1141

  1990. msgid "Backstory on `matrix-nginx-proxy`"

  1991. msgstr ""

  1992. 

  1993. #: ../../../CHANGELOG.md:1143

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

  1995. msgstr ""

  1996. 

  1997. #: ../../../CHANGELOG.md:1145

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

  1999. msgstr ""

  2000. 

  2001. #: ../../../CHANGELOG.md:1147

  2002. msgid "To us, `matrix-nginx-proxy` was:"

  2003. msgstr ""

  2004. 

  2005. #: ../../../CHANGELOG.md:1149

  2006. msgid "an [nginx](https://nginx.org/)-based reverse-proxy"

  2007. msgstr ""

  2008. 

  2009. #: ../../../CHANGELOG.md:1150

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

  2011. msgstr ""

  2012. 

  2013. #: ../../../CHANGELOG.md:1151

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

  2015. msgstr ""

  2016. 

  2017. #: ../../../CHANGELOG.md:1152

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

  2019. msgstr ""

  2020. 

  2021. #: ../../../CHANGELOG.md:1153

  2022. msgid "a webserver for serving the `/.well-known/matrix` static files (generated by the `matrix-base` role until now)"

  2023. msgstr ""

  2024. 

  2025. #: ../../../CHANGELOG.md:1154

  2026. msgid "a webserver [serving your base domain](./docs/configuring-playbook-base-domain-serving.md) (and also generating the `index.html` page for it)"

  2027. msgstr ""

  2028. 

  2029. #: ../../../CHANGELOG.md:1155

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

  2031. msgstr ""

  2032. 

  2033. #: ../../../CHANGELOG.md:1157

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

  2035. msgstr ""

  2036. 

  2037. #: ../../../CHANGELOG.md:1159

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

  2039. msgstr ""

  2040. 

  2041. #: ../../../CHANGELOG.md:1161

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

  2043. msgstr ""

  2044. 

  2045. #: ../../../CHANGELOG.md:1163

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

  2047. msgstr ""

  2048. 

  2049. #: ../../../CHANGELOG.md:1165

  2050. msgid "Going Traefik-native and cutting out all middlemen"

  2051. msgstr ""

  2052. 

  2053. #: ../../../CHANGELOG.md:1167

  2054. msgid "In our new setup, you'll see the bare minimum number of reverse-proxies."

  2055. msgstr ""

  2056. 

  2057. #: ../../../CHANGELOG.md:1169

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

  2059. msgstr ""

  2060. 

  2061. #: ../../../CHANGELOG.md:1171

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

  2063. msgstr ""

  2064. 

  2065. #: ../../../CHANGELOG.md:1173

  2066. msgid "Traefik now has an extra job"

  2067. msgstr ""

  2068. 

  2069. #: ../../../CHANGELOG.md:1175

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

  2071. msgstr ""

  2072. 

  2073. #: ../../../CHANGELOG.md:1177

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

  2075. msgstr ""

  2076. 

  2077. #: ../../../CHANGELOG.md:1179

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

  2079. msgstr ""

  2080. 

  2081. #: ../../../CHANGELOG.md:1181

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

  2083. msgstr ""

  2084. 

  2085. #: ../../../CHANGELOG.md:1183

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

  2087. msgstr ""

  2088. 

  2089. #: ../../../CHANGELOG.md:1185

  2090. msgid "Traefik serving this second purpose has a few downsides:"

  2091. msgstr ""

  2092. 

  2093. #: ../../../CHANGELOG.md:1187

  2094. msgid "Traefik becomes a runtime dependency for all homeserver-dependant container services"

  2095. msgstr ""

  2096. 

  2097. #: ../../../CHANGELOG.md:1188

  2098. msgid "all homeserver-dependant services now need to be connected to the `traefik` container network, even if they don't need public internet exposure"

  2099. msgstr ""

  2100. 

  2101. #: ../../../CHANGELOG.md:1190

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

  2103. msgstr ""

  2104. 

  2105. #: ../../../CHANGELOG.md:1192

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

  2107. msgstr ""

  2108. 

  2109. #: ../../../CHANGELOG.md:1194

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

  2111. msgstr ""

  2112. 

  2113. #: ../../../CHANGELOG.md:1196

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

  2115. msgstr ""

  2116. 

  2117. #: ../../../CHANGELOG.md:1198

  2118. msgid "People managing their own Traefik instance need to do minor changes"

  2119. msgstr ""

  2120. 

  2121. #: ../../../CHANGELOG.md:1200

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

  2123. msgstr ""

  2124. 

  2125. #: ../../../CHANGELOG.md:1202

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

  2127. msgstr ""

  2128. 

  2129. #: ../../../CHANGELOG.md:1204

  2130. msgid "People fronting Traefik with another reverse proxy need to do minor changes"

  2131. msgstr ""

  2132. 

  2133. #: ../../../CHANGELOG.md:1206

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

  2135. msgstr ""

  2136. 

  2137. #: ../../../CHANGELOG.md:1208

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

  2139. msgstr ""

  2140. 

  2141. #: ../../../CHANGELOG.md:1210

  2142. msgid "Supported reverse proxy types are now fewer"

  2143. msgstr ""

  2144. 

  2145. #: ../../../CHANGELOG.md:1212

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

  2147. msgstr ""

  2148. 

  2149. #: ../../../CHANGELOG.md:1214

  2150. msgid "Previously, we allowed you to set `matrix_playbook_reverse_proxy_type` to 7 different values to accommodate various reverse-proxy setups."

  2151. msgstr ""

  2152. 

  2153. #: ../../../CHANGELOG.md:1216

  2154. msgid "The complexity of this is too high, so we only support 3 values right now:"

  2155. msgstr ""

  2156. 

  2157. #: ../../../CHANGELOG.md:1218

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

  2159. msgstr ""

  2160. 

  2161. #: ../../../CHANGELOG.md:1219

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

  2163. msgstr ""

  2164. 

  2165. #: ../../../CHANGELOG.md:1220

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

  2167. msgstr ""

  2168. 

  2169. #: ../../../CHANGELOG.md:1222

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

  2171. msgstr ""

  2172. 

  2173. #: ../../../CHANGELOG.md:1224

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

  2175. msgstr ""

  2176. 

  2177. #: ../../../CHANGELOG.md:1226

  2178. msgid "If you were using these values as a way to stay away from Traefik, you now have 2 options:"

  2179. msgstr ""

  2180. 

  2181. #: ../../../CHANGELOG.md:1228

  2182. msgid "(recommended) [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)"

  2183. msgstr ""

  2184. 

  2185. #: ../../../CHANGELOG.md:1229

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

  2187. msgstr ""

  2188. 

  2189. #: ../../../CHANGELOG.md:1231

  2190. msgid "Container networking changes"

  2191. msgstr ""

  2192. 

  2193. #: ../../../CHANGELOG.md:1233

  2194. msgid "Now that `matrix-nginx-proxy` is not in the mix, it became easier to clear out some other long-overdue technical debt."

  2195. msgstr ""

  2196. 

  2197. #: ../../../CHANGELOG.md:1235

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

  2199. msgstr ""

  2200. 

  2201. #: ../../../CHANGELOG.md:1237

  2202. msgid "Moving components (especially the database) into other container networks was difficult — it required changes to many other components to ensure correct connectivity."

  2203. msgstr ""

  2204. 

  2205. #: ../../../CHANGELOG.md:1239

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

  2207. msgstr ""

  2208. 

  2209. #: ../../../CHANGELOG.md:1241

  2210. msgid "Carrying out these container networking changes necessitated modifying many components, so **we're hoping not too many bugs were introduced in the process**."

  2211. msgstr ""

  2212. 

  2213. #: ../../../CHANGELOG.md:1243

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

  2215. msgstr ""

  2216. 

  2217. #: ../../../CHANGELOG.md:1245

  2218. msgid "Metrics exposure changes"

  2219. msgstr ""

  2220. 

  2221. #: ../../../CHANGELOG.md:1247

  2222. msgid "This section is for people who are exposing monitoring metrics publicly, to be consumed by an external Prometheus server."

  2223. msgstr ""

  2224. 

  2225. #: ../../../CHANGELOG.md:1249

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

  2227. msgstr ""

  2228. 

  2229. #: ../../../CHANGELOG.md:1251

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

  2231. msgstr ""

  2232. 

  2233. #: ../../../CHANGELOG.md:1253

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

  2235. msgstr ""

  2236. 

  2237. #: ../../../CHANGELOG.md:1255

  2238. 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!"

  2239. msgstr ""

  2240. 

  2241. #: ../../../CHANGELOG.md:1257

  2242. msgid "Matrix static files"

  2243. msgstr ""

  2244. 

  2245. #: ../../../CHANGELOG.md:1259

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

  2247. msgstr ""

  2248. 

  2249. #: ../../../CHANGELOG.md:1261

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

  2251. msgstr ""

  2252. 

  2253. #: ../../../CHANGELOG.md:1263

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

  2255. msgstr ""

  2256. 

  2257. #: ../../../CHANGELOG.md:1265

  2258. msgid "A note on performance"

  2259. msgstr ""

  2260. 

  2261. #: ../../../CHANGELOG.md:1267

  2262. msgid "Some of you have been voicing their concerns (for a long time) about Traefik being too slow and nginx being better."

  2263. msgstr ""

  2264. 

  2265. #: ../../../CHANGELOG.md:1269

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

  2267. msgstr ""

  2268. 

  2269. #: ../../../CHANGELOG.md:1271

  2270. msgid "We believe that using Traefik provides way too many benefits to worry about this minor performance impairment."

  2271. msgstr ""

  2272. 

  2273. #: ../../../CHANGELOG.md:1273

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

  2275. msgstr ""

  2276. 

  2277. #: ../../../CHANGELOG.md:1275

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

  2279. msgstr ""

  2280. 

  2281. #: ../../../CHANGELOG.md:1277

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

  2283. msgstr ""

  2284. 

  2285. #: ../../../CHANGELOG.md:1279

  2286. msgid "Migration procedure"

  2287. msgstr ""

  2288. 

  2289. #: ../../../CHANGELOG.md:1281

  2290. msgid "The updated playbook will automatically perform some migration tasks for you:"

  2291. msgstr ""

  2292. 

  2293. #: ../../../CHANGELOG.md:1283

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

  2295. msgstr ""

  2296. 

  2297. #: ../../../CHANGELOG.md:1285

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

  2299. msgstr ""

  2300. 

  2301. #: ../../../CHANGELOG.md:1287

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

  2303. msgstr ""

  2304. 

  2305. #: ../../../CHANGELOG.md:1289

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

  2307. msgstr ""

  2308. 

  2309. #: ../../../CHANGELOG.md:1291

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

  2311. msgstr ""

  2312. 

  2313. #: ../../../CHANGELOG.md:1293

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

  2315. msgstr ""

  2316. 

  2317. #: ../../../CHANGELOG.md:1295

  2318. msgid "We don't recommend changing these variables and suppressing warnings, unless you know what you're doing."

  2319. msgstr ""

  2320. 

  2321. #: ../../../CHANGELOG.md:1297

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

  2323. msgstr ""

  2324. 

  2325. #: ../../../CHANGELOG.md:1299

  2326. msgid "Conclusion"

  2327. msgstr ""

  2328. 

  2329. #: ../../../CHANGELOG.md:1301

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

  2331. msgstr ""

  2332. 

  2333. #: ../../../CHANGELOG.md:1303

  2334. 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!"

  2335. msgstr ""

  2336. 

  2337. #: ../../../CHANGELOG.md:1306

  2338. msgid "2024-01-14"

  2339. msgstr ""

  2340. 

  2341. #: ../../../CHANGELOG.md:1308

  2342. msgid "(Backward Compatibility) Configuration changes required for people fronting the integrated reverse-proxy webserver with another reverse-proxy"

  2343. msgstr ""

  2344. 

  2345. #: ../../../CHANGELOG.md:1310

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

  2347. msgstr ""

  2348. 

  2349. #: ../../../CHANGELOG.md:1312

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

  2351. msgstr ""

  2352. 

  2353. #: ../../../CHANGELOG.md:1314

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

  2355. msgstr ""

  2356. 

  2357. #: ../../../CHANGELOG.md:1316

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

  2359. msgstr ""

  2360. 

  2361. #: ../../../CHANGELOG.md:1318

  2362. msgid "Adapt your configuration as seen below:"

  2363. msgstr ""

  2364. 

  2365. #: ../../../CHANGELOG.md:1351

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

  2367. msgstr ""

  2368. 

  2369. #: ../../../CHANGELOG.md:1354

  2370. msgid "2024-01-13"

  2371. msgstr ""

  2372. 

  2373. #: ../../../CHANGELOG.md:1356

  2374. msgid "matrix-reminder-bot update with more secure (backward-incompatible) default settings"

  2375. msgstr ""

  2376. 

  2377. #: ../../../CHANGELOG.md:1358

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

  2379. msgstr ""

  2380. 

  2381. #: ../../../CHANGELOG.md:1360

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

  2383. msgstr ""

  2384. 

  2385. #: ../../../CHANGELOG.md:1362

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

  2387. msgstr ""

  2388. 

  2389. #: ../../../CHANGELOG.md:1364

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

  2391. msgstr ""

  2392. 

  2393. #: ../../../CHANGELOG.md:1366

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

  2395. msgstr ""

  2396. 

  2397. #: ../../../CHANGELOG.md:1368

  2398. msgid "If you need **to undo or tweak these security improvements**, you can change your `vars.yml` file to:"

  2399. msgstr ""

  2400. 

  2401. #: ../../../CHANGELOG.md:1370

  2402. msgid "disable the allowlist (`matrix_bot_matrix_reminder_bot_allowlist_enabled: false`), making the bot allow usage by anyone, anywhere"

  2403. msgstr ""

  2404. 

  2405. #: ../../../CHANGELOG.md:1372

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

  2407. msgstr ""

  2408. 

  2409. #: ../../../CHANGELOG.md:1374

  2410. msgid "override the default allowlist (in the `group_vars/matrix_servers` file) by redefining `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`"

  2411. msgstr ""

  2412. 

  2413. #: ../../../CHANGELOG.md:1377

  2414. msgid "2024-01-05"

  2415. msgstr ""

  2416. 

  2417. #: ../../../CHANGELOG.md:1379

  2418. msgid "matrix-mailer has been replaced by the exim-relay external role"

  2419. msgstr ""

  2420. 

  2421. #: ../../../CHANGELOG.md:1381

  2422. #: ../../../CHANGELOG.md:2019

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

  2424. msgstr ""

  2425. 

  2426. #: ../../../CHANGELOG.md:1383

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

  2428. msgstr ""

  2429. 

  2430. #: ../../../CHANGELOG.md:1385

  2431. msgid "To migrate:"

  2432. msgstr ""

  2433. 

  2434. #: ../../../CHANGELOG.md:1387

  2435. msgid "pull the playbook changes, as usual"

  2436. msgstr ""

  2437. 

  2438. #: ../../../CHANGELOG.md:1388

  2439. msgid "update your roles (run `just roles` or `make roles`)"

  2440. msgstr ""

  2441. 

  2442. #: ../../../CHANGELOG.md:1389

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

  2444. msgstr ""

  2445. 

  2446. #: ../../../CHANGELOG.md:1390

  2447. msgid "re-run the playbook (`install-all` or `setup-all`)"

  2448. msgstr ""

  2449. 

  2450. #: ../../../CHANGELOG.md:1392

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

  2452. msgstr ""

  2453. 

  2454. #: ../../../CHANGELOG.md:1395

  2455. msgid "2024-01-02"

  2456. msgstr ""

  2457. 

  2458. #: ../../../CHANGELOG.md:1397

  2459. msgid "mautrix-signal now powered by the new Go-based bridge"

  2460. msgstr ""

  2461. 

  2462. #: ../../../CHANGELOG.md:1399

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

  2464. msgstr ""

  2465. 

  2466. #: ../../../CHANGELOG.md:1401

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

  2468. msgstr ""

  2469. 

  2470. #: ../../../CHANGELOG.md:1403

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

  2472. msgstr ""

  2473. 

  2474. #: ../../../CHANGELOG.md:1406

  2475. msgid "2023-10-23"

  2476. msgstr ""

  2477. 

  2478. #: ../../../CHANGELOG.md:1408

  2479. msgid "Enabling `allow_public_rooms_over_federation` by default for Synapse"

  2480. msgstr ""

  2481. 

  2482. #: ../../../CHANGELOG.md:1410

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

  2484. msgstr ""

  2485. 

  2486. #: ../../../CHANGELOG.md:1412

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

  2488. msgstr ""

  2489. 

  2490. #: ../../../CHANGELOG.md:1414

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

  2492. msgstr ""

  2493. 

  2494. #: ../../../CHANGELOG.md:1416

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

  2496. msgstr ""

  2497. 

  2498. #: ../../../CHANGELOG.md:1418

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

  2500. msgstr ""

  2501. 

  2502. #: ../../../CHANGELOG.md:1420

  2503. msgid "The **historical reasoning** behind this change is as follows:"

  2504. msgstr ""

  2505. 

  2506. #: ../../../CHANGELOG.md:1422

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

  2508. msgstr ""

  2509. 

  2510. #: ../../../CHANGELOG.md:1424

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

  2512. msgstr ""

  2513. 

  2514. #: ../../../CHANGELOG.md:1426

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

  2516. msgstr ""

  2517. 

  2518. #: ../../../CHANGELOG.md:1428

  2519. msgid "Here are **actions you may wish to take** as a result of this change:"

  2520. msgstr ""

  2521. 

  2522. #: ../../../CHANGELOG.md:1430

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

  2524. msgstr ""

  2525. 

  2526. #: ../../../CHANGELOG.md:1432

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

  2528. msgstr ""

  2529. 

  2530. #: ../../../CHANGELOG.md:1434

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

  2532. msgstr ""

  2533. 

  2534. #: ../../../CHANGELOG.md:1437

  2535. msgid "2023-10-18"

  2536. msgstr ""

  2537. 

  2538. #: ../../../CHANGELOG.md:1439

  2539. msgid "Postgres parameters are automatically tuned now"

  2540. msgstr ""

  2541. 

  2542. #: ../../../CHANGELOG.md:1441

  2543. msgid "The playbook has provided some hints about [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) for quite a while now."

  2544. msgstr ""

  2545. 

  2546. #: ../../../CHANGELOG.md:1443

  2547. 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/."

  2548. msgstr ""

  2549. 

  2550. #: ../../../CHANGELOG.md:1445

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

  2552. msgstr ""

  2553. 

  2554. #: ../../../CHANGELOG.md:1447

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

  2556. msgstr ""

  2557. 

  2558. #: ../../../CHANGELOG.md:1450

  2559. msgid "2023-08-31"

  2560. msgstr ""

  2561. 

  2562. #: ../../../CHANGELOG.md:1452

  2563. msgid "SchildiChat Web support"

  2564. msgstr ""

  2565. 

  2566. #: ../../../CHANGELOG.md:1454

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

  2568. msgstr ""

  2569. 

  2570. #: ../../../CHANGELOG.md:1456

  2571. msgid "See our [Configuring SchildiChat Web](docs/configuring-playbook-client-schildichat-web.md) documentation to get started."

  2572. msgstr ""

  2573. 

  2574. #: ../../../CHANGELOG.md:1459

  2575. msgid "2023-08-23"

  2576. msgstr ""

  2577. 

  2578. #: ../../../CHANGELOG.md:1461

  2579. msgid "mautrix-wsproxy support"

  2580. msgstr ""

  2581. 

  2582. #: ../../../CHANGELOG.md:1463

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

  2584. msgstr ""

  2585. 

  2586. #: ../../../CHANGELOG.md:1465

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

  2588. msgstr ""

  2589. 

  2590. #: ../../../CHANGELOG.md:1468

  2591. msgid "2023-07-24"

  2592. msgstr ""

  2593. 

  2594. #: ../../../CHANGELOG.md:1470

  2595. msgid "matrix-registration-bot usage changed"

  2596. msgstr ""

  2597. 

  2598. #: ../../../CHANGELOG.md:1472

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

  2600. msgstr ""

  2601. 

  2602. #: ../../../CHANGELOG.md:1474

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

  2604. msgstr ""

  2605. 

  2606. #: ../../../CHANGELOG.md:1476

  2607. msgid "`matrix_bot_matrix_registration_bot_bot_access_token`"

  2608. msgstr ""

  2609. 

  2610. #: ../../../CHANGELOG.md:1477

  2611. msgid "`matrix_bot_matrix_registration_bot_api_token`"

  2612. msgstr ""

  2613. 

  2614. #: ../../../CHANGELOG.md:1480

  2615. msgid "2023-07-21"

  2616. msgstr ""

  2617. 

  2618. #: ../../../CHANGELOG.md:1482

  2619. msgid "mautrix-gmessages support"

  2620. msgstr ""

  2621. 

  2622. #: ../../../CHANGELOG.md:1484

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

  2624. msgstr ""

  2625. 

  2626. #: ../../../CHANGELOG.md:1487

  2627. msgid "2023-07-17"

  2628. msgstr ""

  2629. 

  2630. #: ../../../CHANGELOG.md:1489

  2631. msgid "matrix-media-repo support"

  2632. msgstr ""

  2633. 

  2634. #: ../../../CHANGELOG.md:1491

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

  2636. msgstr ""

  2637. 

  2638. #: ../../../CHANGELOG.md:1493

  2639. msgid "To learn more see our [Storing Matrix media files using matrix-media-repo](docs/configuring-playbook-matrix-media-repo.md) documentation page."

  2640. msgstr ""

  2641. 

  2642. #: ../../../CHANGELOG.md:1496

  2643. msgid "2023-05-25"

  2644. msgstr ""

  2645. 

  2646. #: ../../../CHANGELOG.md:1498

  2647. msgid "Enabling `forget_rooms_on_leave` by default for Synapse"

  2648. msgstr ""

  2649. 

  2650. #: ../../../CHANGELOG.md:1500

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

  2652. msgstr ""

  2653. 

  2654. #: ../../../CHANGELOG.md:1502

  2655. msgid "The upstream Synapse default is `false` (disabled), so that you must forget rooms manually after leaving."

  2656. msgstr ""

  2657. 

  2658. #: ../../../CHANGELOG.md:1504

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

  2660. msgstr ""

  2661. 

  2662. #: ../../../CHANGELOG.md:1506

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

  2664. msgstr ""

  2665. 

  2666. #: ../../../CHANGELOG.md:1509

  2667. msgid "2023-04-03"

  2668. msgstr ""

  2669. 

  2670. #: ../../../CHANGELOG.md:1511

  2671. msgid "The matrix-jitsi role lives independently now"

  2672. msgstr ""

  2673. 

  2674. #: ../../../CHANGELOG.md:1513

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

  2676. msgstr ""

  2677. 

  2678. #: ../../../CHANGELOG.md:1515

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

  2680. msgstr ""

  2681. 

  2682. #: ../../../CHANGELOG.md:1517

  2683. msgid "As part of the extraction process of this role out of the Matrix playbook, a few other things improved:"

  2684. msgstr ""

  2685. 

  2686. #: ../../../CHANGELOG.md:1519

  2687. msgid "**native Traefik support** has been added"

  2688. msgstr ""

  2689. 

  2690. #: ../../../CHANGELOG.md:1520

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

  2692. msgstr ""

  2693. 

  2694. #: ../../../CHANGELOG.md:1522

  2695. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Jitsi or not."

  2696. msgstr ""

  2697. 

  2698. #: ../../../CHANGELOG.md:1524

  2699. msgid "If you're making use of Jitsi via this playbook, you will need to update variable references in your `vars.yml` file:"

  2700. msgstr ""

  2701. 

  2702. #: ../../../CHANGELOG.md:1526

  2703. msgid "`matrix_jitsi_*_docker_image_` -> `matrix_jitsi_*_container_image_`"

  2704. msgstr ""

  2705. 

  2706. #: ../../../CHANGELOG.md:1527

  2707. msgid "`matrix_jitsi_` -> `jitsi_`"

  2708. msgstr ""

  2709. 

  2710. #: ../../../CHANGELOG.md:1528

  2711. #: ../../../CHANGELOG.md:1555

  2712. msgid "some other internal variables have changed, but the playbook will tell you about them"

  2713. msgstr ""

  2714. 

  2715. #: ../../../CHANGELOG.md:1530

  2716. msgid "2023-03-22"

  2717. msgstr ""

  2718. 

  2719. #: ../../../CHANGELOG.md:1532

  2720. msgid "ntfy Web App is disabled by default"

  2721. msgstr ""

  2722. 

  2723. #: ../../../CHANGELOG.md:1534

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

  2725. msgstr ""

  2726. 

  2727. #: ../../../CHANGELOG.md:1536

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

  2729. msgstr ""

  2730. 

  2731. #: ../../../CHANGELOG.md:1539

  2732. msgid "2023-03-21"

  2733. msgstr ""

  2734. 

  2735. #: ../../../CHANGELOG.md:1541

  2736. msgid "The matrix-prometheus role lives independently now"

  2737. msgstr ""

  2738. 

  2739. #: ../../../CHANGELOG.md:1543

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

  2741. msgstr ""

  2742. 

  2743. #: ../../../CHANGELOG.md:1545

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

  2745. msgstr ""

  2746. 

  2747. #: ../../../CHANGELOG.md:1547

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

  2749. msgstr ""

  2750. 

  2751. #: ../../../CHANGELOG.md:1549

  2752. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Prometheus or not."

  2753. msgstr ""

  2754. 

  2755. #: ../../../CHANGELOG.md:1551

  2756. msgid "If you're making use of Prometheus via this playbook, you will need to update variable references in your `vars.yml` file:"

  2757. msgstr ""

  2758. 

  2759. #: ../../../CHANGELOG.md:1553

  2760. msgid "`matrix_prometheus_docker_image_` -> `matrix_prometheus_container_image_`"

  2761. msgstr ""

  2762. 

  2763. #: ../../../CHANGELOG.md:1554

  2764. msgid "`matrix_prometheus_` -> `prometheus_`"

  2765. msgstr ""

  2766. 

  2767. #: ../../../CHANGELOG.md:1558

  2768. msgid "2023-03-12"

  2769. msgstr ""

  2770. 

  2771. #: ../../../CHANGELOG.md:1560

  2772. msgid "synapse-auto-compressor support"

  2773. msgstr ""

  2774. 

  2775. #: ../../../CHANGELOG.md:1562

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

  2777. msgstr ""

  2778. 

  2779. #: ../../../CHANGELOG.md:1564

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

  2781. msgstr ""

  2782. 

  2783. #: ../../../CHANGELOG.md:1566

  2784. msgid "it runs on a more up-to-date version of `rust-synapse-compress-state`"

  2785. msgstr ""

  2786. 

  2787. #: ../../../CHANGELOG.md:1567

  2788. msgid "it's a set-it-and-forget-it tool that you can enable and never have to deal with manual compression anymore"

  2789. msgstr ""

  2790. 

  2791. #: ../../../CHANGELOG.md:1569

  2792. msgid "This tool needs to be enabled manually, for now. In the future, we're considering enabling it by default for all Synapse installations."

  2793. msgstr ""

  2794. 

  2795. #: ../../../CHANGELOG.md:1571

  2796. msgid "See our [Setting up synapse-auto-compressor](docs/configuring-playbook-synapse-auto-compressor.md) documentation to get started."

  2797. msgstr ""

  2798. 

  2799. #: ../../../CHANGELOG.md:1574

  2800. msgid "2023-03-07"

  2801. msgstr ""

  2802. 

  2803. #: ../../../CHANGELOG.md:1576

  2804. msgid "Sliding Sync proxy (Element X) support"

  2805. msgstr ""

  2806. 

  2807. #: ../../../CHANGELOG.md:1578

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

  2809. msgstr ""

  2810. 

  2811. #: ../../../CHANGELOG.md:1580

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

  2813. msgstr ""

  2814. 

  2815. #: ../../../CHANGELOG.md:1582

  2816. msgid "To get started, see our [Setting up the Sliding Sync proxy](docs/configuring-playbook-sliding-sync-proxy.md) documentation page."

  2817. msgstr ""

  2818. 

  2819. #: ../../../CHANGELOG.md:1585

  2820. msgid "2023-03-02"

  2821. msgstr ""

  2822. 

  2823. #: ../../../CHANGELOG.md:1587

  2824. msgid "The matrix-etherpad role lives independently now"

  2825. msgstr ""

  2826. 

  2827. #: ../../../CHANGELOG.md:1589

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

  2829. msgstr ""

  2830. 

  2831. #: ../../../CHANGELOG.md:1591

  2832. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Etherpad or not."

  2833. msgstr ""

  2834. 

  2835. #: ../../../CHANGELOG.md:1593

  2836. msgid "If you're making use of Etherpad via this playbook, you will need to update variable references in your `vars.yml` file:"

  2837. msgstr ""

  2838. 

  2839. #: ../../../CHANGELOG.md:1595

  2840. msgid "Rename `matrix_etherpad_public_endpoint` to `etherpad_path_prefix`"

  2841. msgstr ""

  2842. 

  2843. #: ../../../CHANGELOG.md:1597

  2844. msgid "Replace `matrix_etherpad_mode: dimension` with:"

  2845. msgstr ""

  2846. 

  2847. #: ../../../CHANGELOG.md:1598

  2848. msgid "for `matrix-nginx-proxy` users:"

  2849. msgstr ""

  2850. 

  2851. #: ../../../CHANGELOG.md:1599

  2852. msgid "`etherpad_nginx_proxy_dimension_integration_enabled: true`"

  2853. msgstr ""

  2854. 

  2855. #: ../../../CHANGELOG.md:1600

  2856. msgid "`etherpad_hostname: \"{{ matrix_server_fqn_dimension }}\"`"

  2857. msgstr ""

  2858. 

  2859. #: ../../../CHANGELOG.md:1601

  2860. msgid "for Traefik users:"

  2861. msgstr ""

  2862. 

  2863. #: ../../../CHANGELOG.md:1602

  2864. msgid "define your own `etherpad_hostname` and `etherpad_path_prefix` as you see fit"

  2865. msgstr ""

  2866. 

  2867. #: ../../../CHANGELOG.md:1604

  2868. msgid "Rename all other variables:"

  2869. msgstr ""

  2870. 

  2871. #: ../../../CHANGELOG.md:1605

  2872. msgid "`matrix_etherpad_docker_image_` -> `matrix_etherpad_container_image_`"

  2873. msgstr ""

  2874. 

  2875. #: ../../../CHANGELOG.md:1606

  2876. msgid "`matrix_etherpad_` -> `etherpad_`"

  2877. msgstr ""

  2878. 

  2879. #: ../../../CHANGELOG.md:1608

  2880. msgid "Along with this relocation, the new role also:"

  2881. msgstr ""

  2882. 

  2883. #: ../../../CHANGELOG.md:1610

  2884. msgid "supports [self-building](docs/self-building.md), so it should work on `arm32` and `arm64` architectures"

  2885. msgstr ""

  2886. 

  2887. #: ../../../CHANGELOG.md:1611

  2888. msgid "has native Traefik reverse-proxy support (Etherpad requests no longer go through `matrix-nginx-proxy` when using Traefik)"

  2889. msgstr ""

  2890. 

  2891. #: ../../../CHANGELOG.md:1614

  2892. msgid "2023-02-26"

  2893. msgstr ""

  2894. 

  2895. #: ../../../CHANGELOG.md:1616

  2896. msgid "Traefik is the default reverse-proxy now"

  2897. msgstr ""

  2898. 

  2899. #: ../../../CHANGELOG.md:1618

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

  2901. msgstr ""

  2902. 

  2903. #: ../../../CHANGELOG.md:1620

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

  2905. msgstr ""

  2906. 

  2907. #: ../../../CHANGELOG.md:1622

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

  2909. msgstr ""

  2910. 

  2911. #: ../../../CHANGELOG.md:1624

  2912. msgid "Traefik managed by the playbook"

  2913. msgstr ""

  2914. 

  2915. #: ../../../CHANGELOG.md:1625

  2916. msgid "Traefik managed by the user in another way"

  2917. msgstr ""

  2918. 

  2919. #: ../../../CHANGELOG.md:1626

  2920. msgid "another reverse-proxy on the same host (`127.0.0.1` port exposure)"

  2921. msgstr ""

  2922. 

  2923. #: ../../../CHANGELOG.md:1627

  2924. msgid "another reverse-proxy on another host (`0.0.0.0` port exposure)"

  2925. msgstr ""

  2926. 

  2927. #: ../../../CHANGELOG.md:1628

  2928. msgid "`matrix-nginx-proxy` — an `nginx` container managed by the playbook"

  2929. msgstr ""

  2930. 

  2931. #: ../../../CHANGELOG.md:1629

  2932. msgid "`nginx` webserver operated by the user, running without a container on the same server"

  2933. msgstr ""

  2934. 

  2935. #: ../../../CHANGELOG.md:1631

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

  2937. msgstr ""

  2938. 

  2939. #: ../../../CHANGELOG.md:1633

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

  2941. msgstr ""

  2942. 

  2943. #: ../../../CHANGELOG.md:1635

  2944. msgid "It's time for the **next step in our migration process** to Traefik and elimination of `matrix-nginx-proxy`:"

  2945. msgstr ""

  2946. 

  2947. #: ../../../CHANGELOG.md:1637

  2948. msgid "Traefik is now the default reverse-proxy for new installations"

  2949. msgstr ""

  2950. 

  2951. #: ../../../CHANGELOG.md:1638

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

  2953. msgstr ""

  2954. 

  2955. #: ../../../CHANGELOG.md:1640

  2956. msgid "How do I switch my existing setup to Traefik?"

  2957. msgstr ""

  2958. 

  2959. #: ../../../CHANGELOG.md:1642

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

  2961. msgstr ""

  2962. 

  2963. #: ../../../CHANGELOG.md:1644

  2964. msgid "If you experience trouble:"

  2965. msgstr ""

  2966. 

  2967. #: ../../../CHANGELOG.md:1646

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

  2969. msgstr ""

  2970. 

  2971. #: ../../../CHANGELOG.md:1647

  2972. msgid "Ask for help in our [support channels](README.md#support)"

  2973. msgstr ""

  2974. 

  2975. #: ../../../CHANGELOG.md:1648

  2976. msgid "Try switching to Traefik again later"

  2977. msgstr ""

  2978. 

  2979. #: ../../../CHANGELOG.md:1650

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

  2981. msgstr ""

  2982. 

  2983. #: ../../../CHANGELOG.md:1652

  2984. msgid "I already use my own Traefik server. How do I plug that in?"

  2985. msgstr ""

  2986. 

  2987. #: ../../../CHANGELOG.md:1654

  2988. msgid "See the [Traefik managed by the playbook](docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) section."

  2989. msgstr ""

  2990. 

  2991. #: ../../../CHANGELOG.md:1656

  2992. msgid "Why is matrix-nginx-proxy used even after switching to Traefik?"

  2993. msgstr ""

  2994. 

  2995. #: ../../../CHANGELOG.md:1658

  2996. msgid "This playbook manages many different services. All these services were initially integrated with `matrix-nginx-proxy`."

  2997. msgstr ""

  2998. 

  2999. #: ../../../CHANGELOG.md:1660

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

  3001. msgstr ""

  3002. 

  3003. #: ../../../CHANGELOG.md:1662

  3004. msgid "How do I remain on matrix-nginx-proxy?"

  3005. msgstr ""

  3006. 

  3007. #: ../../../CHANGELOG.md:1664

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

  3009. msgstr ""

  3010. 

  3011. #: ../../../CHANGELOG.md:1666

  3012. msgid "To proceed regardless of this warning, add `matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your configuration."

  3013. msgstr ""

  3014. 

  3015. #: ../../../CHANGELOG.md:1668

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

  3017. msgstr ""

  3018. 

  3019. #: ../../../CHANGELOG.md:1670

  3020. msgid "How do I keep using my own other reverse-proxy?"

  3021. msgstr ""

  3022. 

  3023. #: ../../../CHANGELOG.md:1672

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

  3025. msgstr ""

  3026. 

  3027. #: ../../../CHANGELOG.md:1675

  3028. msgid "2023-02-25"

  3029. msgstr ""

  3030. 

  3031. #: ../../../CHANGELOG.md:1677

  3032. msgid "rageshake support"

  3033. msgstr ""

  3034. 

  3035. #: ../../../CHANGELOG.md:1679

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

  3037. msgstr ""

  3038. 

  3039. #: ../../../CHANGELOG.md:1681

  3040. msgid "Additional details are available in [Setting up rageshake](docs/configuring-playbook-rageshake.md)."

  3041. msgstr ""

  3042. 

  3043. #: ../../../CHANGELOG.md:1684

  3044. msgid "2023-02-17"

  3045. msgstr ""

  3046. 

  3047. #: ../../../CHANGELOG.md:1686

  3048. msgid "Synapse templates customization support"

  3049. msgstr ""

  3050. 

  3051. #: ../../../CHANGELOG.md:1688

  3052. msgid "The playbook can now help you customize Synapse's templates."

  3053. msgstr ""

  3054. 

  3055. #: ../../../CHANGELOG.md:1690

  3056. msgid "Additional details are available in the [Customizing templates](docs/configuring-playbook-synapse.md#customizing-templates) section of our Synapse documentation."

  3057. msgstr ""

  3058. 

  3059. #: ../../../CHANGELOG.md:1692

  3060. msgid "The matrix-redis role lives independently now"

  3061. msgstr ""

  3062. 

  3063. #: ../../../CHANGELOG.md:1694

  3064. msgid "**TLDR**: the `matrix-redis` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3065. msgstr ""

  3066. 

  3067. #: ../../../CHANGELOG.md:1696

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

  3069. msgstr ""

  3070. 

  3071. #: ../../../CHANGELOG.md:1698

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

  3073. msgstr ""

  3074. 

  3075. #: ../../../CHANGELOG.md:1700

  3076. msgid "The matrix-ntfy role lives independently now"

  3077. msgstr ""

  3078. 

  3079. #: ../../../CHANGELOG.md:1702

  3080. msgid "**TLDR**: the `matrix-ntfy` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3081. msgstr ""

  3082. 

  3083. #: ../../../CHANGELOG.md:1704

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

  3085. msgstr ""

  3086. 

  3087. #: ../../../CHANGELOG.md:1706

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

  3089. msgstr ""

  3090. 

  3091. #: ../../../CHANGELOG.md:1709

  3092. msgid "2023-02-15"

  3093. msgstr ""

  3094. 

  3095. #: ../../../CHANGELOG.md:1711

  3096. msgid "The matrix-grafana role lives independently now"

  3097. msgstr ""

  3098. 

  3099. #: ../../../CHANGELOG.md:1713

  3100. msgid "**TLDR**: the `matrix-grafana` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3101. msgstr ""

  3102. 

  3103. #: ../../../CHANGELOG.md:1715

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

  3105. msgstr ""

  3106. 

  3107. #: ../../../CHANGELOG.md:1717

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

  3109. msgstr ""

  3110. 

  3111. #: ../../../CHANGELOG.md:1720

  3112. msgid "2023-02-13"

  3113. msgstr ""

  3114. 

  3115. #: ../../../CHANGELOG.md:1722

  3116. msgid "The matrix-backup-borg role lives independently now"

  3117. msgstr ""

  3118. 

  3119. #: ../../../CHANGELOG.md:1724

  3120. msgid "**TLDR**: the `matrix-backup-borg` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3121. msgstr ""

  3122. 

  3123. #: ../../../CHANGELOG.md:1726

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

  3125. msgstr ""

  3126. 

  3127. #: ../../../CHANGELOG.md:1728

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

  3129. msgstr ""

  3130. 

  3131. #: ../../../CHANGELOG.md:1731

  3132. msgid "2023-02-12"

  3133. msgstr ""

  3134. 

  3135. #: ../../../CHANGELOG.md:1733

  3136. msgid "(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support"

  3137. msgstr ""

  3138. 

  3139. #: ../../../CHANGELOG.md:1735

  3140. msgid "**TLDR**:"

  3141. msgstr ""

  3142. 

  3143. #: ../../../CHANGELOG.md:1737

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

  3145. msgstr ""

  3146. 

  3147. #: ../../../CHANGELOG.md:1738

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

  3149. msgstr ""

  3150. 

  3151. #: ../../../CHANGELOG.md:1739

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

  3153. msgstr ""

  3154. 

  3155. #: ../../../CHANGELOG.md:1740

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

  3157. msgstr ""

  3158. 

  3159. #: ../../../CHANGELOG.md:1741

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

  3161. msgstr ""

  3162. 

  3163. #: ../../../CHANGELOG.md:1743

  3164. msgid "Motivation for redoing our reverse-proxy setup"

  3165. msgstr ""

  3166. 

  3167. #: ../../../CHANGELOG.md:1745

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

  3169. msgstr ""

  3170. 

  3171. #: ../../../CHANGELOG.md:1747

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

  3173. msgstr ""

  3174. 

  3175. #: ../../../CHANGELOG.md:1749

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

  3177. msgstr ""

  3178. 

  3179. #: ../../../CHANGELOG.md:1751

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

  3181. msgstr ""

  3182. 

  3183. #: ../../../CHANGELOG.md:1753

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

  3185. msgstr ""

  3186. 

  3187. #: ../../../CHANGELOG.md:1755

  3188. msgid "*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined with exposing services manually (setting `_bind_port` variables)"

  3189. msgstr ""

  3190. 

  3191. #: ../../../CHANGELOG.md:1756

  3192. msgid "*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in `http`-only mode (no SSL certificate retrieval)."

  3193. msgstr ""

  3194. 

  3195. #: ../../../CHANGELOG.md:1758

  3196. msgid "Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations."

  3197. msgstr ""

  3198. 

  3199. #: ../../../CHANGELOG.md:1760

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

  3201. msgstr ""

  3202. 

  3203. #: ../../../CHANGELOG.md:1762

  3204. msgid "The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks:"

  3205. msgstr ""

  3206. 

  3207. #: ../../../CHANGELOG.md:1764

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

  3209. msgstr ""

  3210. 

  3211. #: ../../../CHANGELOG.md:1765

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

  3213. msgstr ""

  3214. 

  3215. #: ../../../CHANGELOG.md:1766

  3216. msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) — for hosting the [Nextcloud](https://nextcloud.com/) groupware platform"

  3217. msgstr ""

  3218. 

  3219. #: ../../../CHANGELOG.md:1768

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

  3221. msgstr ""

  3222. 

  3223. #: ../../../CHANGELOG.md:1770

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

  3225. msgstr ""

  3226. 

  3227. #: ../../../CHANGELOG.md:1772

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

  3229. msgstr ""

  3230. 

  3231. #: ../../../CHANGELOG.md:1774

  3232. msgid "How do these changes fix all these problems?"

  3233. msgstr ""

  3234. 

  3235. #: ../../../CHANGELOG.md:1776

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

  3237. msgstr ""

  3238. 

  3239. #: ../../../CHANGELOG.md:1778

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

  3241. msgstr ""

  3242. 

  3243. #: ../../../CHANGELOG.md:1780

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

  3245. msgstr ""

  3246. 

  3247. #: ../../../CHANGELOG.md:1782

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

  3249. msgstr ""

  3250. 

  3251. #: ../../../CHANGELOG.md:1784

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

  3253. msgstr ""

  3254. 

  3255. #: ../../../CHANGELOG.md:1786

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

  3257. msgstr ""

  3258. 

  3259. #: ../../../CHANGELOG.md:1788

  3260. msgid "Where we're at right now?"

  3261. msgstr ""

  3262. 

  3263. #: ../../../CHANGELOG.md:1790

  3264. msgid "`matrix_playbook_reverse_proxy_type` still defaults to a value of `playbook-managed-nginx`."

  3265. msgstr ""

  3266. 

  3267. #: ../../../CHANGELOG.md:1792

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

  3269. msgstr ""

  3270. 

  3271. #: ../../../CHANGELOG.md:1794

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

  3273. msgstr ""

  3274. 

  3275. #: ../../../CHANGELOG.md:1796

  3276. msgid "How do I explicitly switch to Traefik right now?"

  3277. msgstr ""

  3278. 

  3279. #: ../../../CHANGELOG.md:1798

  3280. msgid "**Users who wish to migrate to Traefik** today, can do so by **adding** this to their configuration:"

  3281. msgstr ""

  3282. 

  3283. #: ../../../CHANGELOG.md:1804

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

  3285. msgstr ""

  3286. 

  3287. #: ../../../CHANGELOG.md:1806

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

  3289. msgstr ""

  3290. 

  3291. #: ../../../CHANGELOG.md:1808

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

  3293. msgstr ""

  3294. 

  3295. #: ../../../CHANGELOG.md:1810

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

  3297. msgstr ""

  3298. 

  3299. #: ../../../CHANGELOG.md:1812

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

  3301. msgstr ""

  3302. 

  3303. #: ../../../CHANGELOG.md:1814

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

  3305. msgstr ""

  3306. 

  3307. #: ../../../CHANGELOG.md:1816

  3308. msgid "Where we're going in the near future?"

  3309. msgstr ""

  3310. 

  3311. #: ../../../CHANGELOG.md:1818

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

  3313. msgstr ""

  3314. 

  3315. #: ../../../CHANGELOG.md:1820

  3316. msgid "For now, `matrix-nginx-proxy` will stay around."

  3317. msgstr ""

  3318. 

  3319. #: ../../../CHANGELOG.md:1822

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

  3321. msgstr ""

  3322. 

  3323. #: ../../../CHANGELOG.md:1824

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

  3325. msgstr ""

  3326. 

  3327. #: ../../../CHANGELOG.md:1826

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

  3329. msgstr ""

  3330. 

  3331. #: ../../../CHANGELOG.md:1827

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

  3333. msgstr ""

  3334. 

  3335. #: ../../../CHANGELOG.md:1829

  3336. msgid "How do I help?"

  3337. msgstr ""

  3338. 

  3339. #: ../../../CHANGELOG.md:1831

  3340. msgid "You can help by:"

  3341. msgstr ""

  3342. 

  3343. #: ../../../CHANGELOG.md:1833

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

  3345. msgstr ""

  3346. 

  3347. #: ../../../CHANGELOG.md:1835

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

  3349. msgstr ""

  3350. 

  3351. #: ../../../CHANGELOG.md:1837

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

  3353. msgstr ""

  3354. 

  3355. #: ../../../CHANGELOG.md:1840

  3356. msgid "2023-02-10"

  3357. msgstr ""

  3358. 

  3359. #: ../../../CHANGELOG.md:1842

  3360. msgid "Matrix Authentication Support for Jitsi"

  3361. msgstr ""

  3362. 

  3363. #: ../../../CHANGELOG.md:1844

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

  3365. msgstr ""

  3366. 

  3367. #: ../../../CHANGELOG.md:1846

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

  3369. msgstr ""

  3370. 

  3371. #: ../../../CHANGELOG.md:1848

  3372. msgid "Draupnir moderation tool (bot) support"

  3373. msgstr ""

  3374. 

  3375. #: ../../../CHANGELOG.md:1850

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

  3377. msgstr ""

  3378. 

  3379. #: ../../../CHANGELOG.md:1852

  3380. msgid "Additional details are available in [Setting up Draupnir](docs/configuring-playbook-bot-draupnir.md)."

  3381. msgstr ""

  3382. 

  3383. #: ../../../CHANGELOG.md:1855

  3384. msgid "2023-02-05"

  3385. msgstr ""

  3386. 

  3387. #: ../../../CHANGELOG.md:1857

  3388. msgid "The matrix-prometheus-postgres-exporter role lives independently now"

  3389. msgstr ""

  3390. 

  3391. #: ../../../CHANGELOG.md:1859

  3392. msgid "**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3393. msgstr ""

  3394. 

  3395. #: ../../../CHANGELOG.md:1861

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

  3397. msgstr ""

  3398. 

  3399. #: ../../../CHANGELOG.md:1863

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

  3401. msgstr ""

  3402. 

  3403. #: ../../../CHANGELOG.md:1865

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

  3405. msgstr ""

  3406. 

  3407. #: ../../../CHANGELOG.md:1867

  3408. #: ../../../CHANGELOG.md:1909

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

  3410. msgstr ""

  3411. 

  3412. #: ../../../CHANGELOG.md:1870

  3413. msgid "2023-01-26"

  3414. msgstr ""

  3415. 

  3416. #: ../../../CHANGELOG.md:1872

  3417. msgid "coturn can now use host-networking"

  3418. msgstr ""

  3419. 

  3420. #: ../../../CHANGELOG.md:1874

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

  3422. msgstr ""

  3423. 

  3424. #: ../../../CHANGELOG.md:1876

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

  3426. msgstr ""

  3427. 

  3428. #: ../../../CHANGELOG.md:1882

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

  3430. msgstr ""

  3431. 

  3432. #: ../../../CHANGELOG.md:1884

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

  3434. msgstr ""

  3435. 

  3436. #: ../../../CHANGELOG.md:1886

  3437. msgid "(Backward Compatibility) Tightening coturn security can lead to connectivity issues"

  3438. msgstr ""

  3439. 

  3440. #: ../../../CHANGELOG.md:1888

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

  3442. msgstr ""

  3443. 

  3444. #: ../../../CHANGELOG.md:1890

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

  3446. msgstr ""

  3447. 

  3448. #: ../../../CHANGELOG.md:1892

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

  3450. msgstr ""

  3451. 

  3452. #: ../../../CHANGELOG.md:1894

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

  3454. msgstr ""

  3455. 

  3456. #: ../../../CHANGELOG.md:1897

  3457. msgid "2023-01-21"

  3458. msgstr ""

  3459. 

  3460. #: ../../../CHANGELOG.md:1899

  3461. msgid "The matrix-prometheus-node-exporter role lives independently now"

  3462. msgstr ""

  3463. 

  3464. #: ../../../CHANGELOG.md:1901

  3465. msgid "**TLDR**: the `matrix-prometheus-node-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3466. msgstr ""

  3467. 

  3468. #: ../../../CHANGELOG.md:1903

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

  3470. msgstr ""

  3471. 

  3472. #: ../../../CHANGELOG.md:1905

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

  3474. msgstr ""

  3475. 

  3476. #: ../../../CHANGELOG.md:1907

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

  3478. msgstr ""

  3479. 

  3480. #: ../../../CHANGELOG.md:1912

  3481. msgid "2023-01-13"

  3482. msgstr ""

  3483. 

  3484. #: ../../../CHANGELOG.md:1914

  3485. msgid "Support for running commands via just"

  3486. msgstr ""

  3487. 

  3488. #: ../../../CHANGELOG.md:1916

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

  3490. msgstr ""

  3491. 

  3492. #: ../../../CHANGELOG.md:1918

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

  3494. msgstr ""

  3495. 

  3496. #: ../../../CHANGELOG.md:1920

  3497. msgid "Our [justfile](justfile) already defines some additional helpful **shortcut** commands that weren't part of our `Makefile`. Here are some examples:"

  3498. msgstr ""

  3499. 

  3500. #: ../../../CHANGELOG.md:1922

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

  3502. msgstr ""

  3503. 

  3504. #: ../../../CHANGELOG.md:1923

  3505. msgid "`just install-all --ask-vault-pass` — commands also support additional arguments (`--ask-vault-pass` will be appended to the above installation command)"

  3506. msgstr ""

  3507. 

  3508. #: ../../../CHANGELOG.md:1924

  3509. msgid "`just run-tags install-mautrix-slack,start` — to run specific playbook tags"

  3510. msgstr ""

  3511. 

  3512. #: ../../../CHANGELOG.md:1925

  3513. msgid "`just start-all` — (re-)starts all services"

  3514. msgstr ""

  3515. 

  3516. #: ../../../CHANGELOG.md:1926

  3517. msgid "`just stop-group postgres` — to stop only the Postgres service"

  3518. msgstr ""

  3519. 

  3520. #: ../../../CHANGELOG.md:1927

  3521. msgid "`just register-user alice secret-password yes` — registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)"

  3522. msgstr ""

  3523. 

  3524. #: ../../../CHANGELOG.md:1929

  3525. msgid "Additional helpful commands and shortcuts may be defined in the future."

  3526. msgstr ""

  3527. 

  3528. #: ../../../CHANGELOG.md:1931

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

  3530. msgstr ""

  3531. 

  3532. #: ../../../CHANGELOG.md:1934

  3533. msgid "2023-01-11"

  3534. msgstr ""

  3535. 

  3536. #: ../../../CHANGELOG.md:1936

  3537. msgid "mautrix-slack support"

  3538. msgstr ""

  3539. 

  3540. #: ../../../CHANGELOG.md:1938

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

  3542. msgstr ""

  3543. 

  3544. #: ../../../CHANGELOG.md:1940

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

  3546. msgstr ""

  3547. 

  3548. #: ../../../CHANGELOG.md:1943

  3549. msgid "2023-01-10"

  3550. msgstr ""

  3551. 

  3552. #: ../../../CHANGELOG.md:1945

  3553. msgid "ChatGPT support"

  3554. msgstr ""

  3555. 

  3556. #: ../../../CHANGELOG.md:1947

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

  3558. msgstr ""

  3559. 

  3560. #: ../../../CHANGELOG.md:1949

  3561. msgid "See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-chatgpt.md) documentation to get started."

  3562. msgstr ""

  3563. 

  3564. #: ../../../CHANGELOG.md:1952

  3565. msgid "2022-11-30"

  3566. msgstr ""

  3567. 

  3568. #: ../../../CHANGELOG.md:1954

  3569. msgid "matrix-postgres-backup has been replaced by the ansible-role-postgres-backup external role"

  3570. msgstr ""

  3571. 

  3572. #: ../../../CHANGELOG.md:1956

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

  3574. msgstr ""

  3575. 

  3576. #: ../../../CHANGELOG.md:1958

  3577. msgid "You'll need to rename your `matrix_postgres_backup`-prefixed variables such that they use a `postgres_backup` prefix."

  3578. msgstr ""

  3579. 

  3580. #: ../../../CHANGELOG.md:1961

  3581. msgid "2022-11-28"

  3582. msgstr ""

  3583. 

  3584. #: ../../../CHANGELOG.md:1963

  3585. msgid "matrix-postgres has been replaced by the ansible-role-postgres external role"

  3586. msgstr ""

  3587. 

  3588. #: ../../../CHANGELOG.md:1965

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

  3590. msgstr ""

  3591. 

  3592. #: ../../../CHANGELOG.md:1967

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

  3594. msgstr ""

  3595. 

  3596. #: ../../../CHANGELOG.md:1969

  3597. msgid "The new role is an upgraded version of the old `matrix-postgres` role with these notable differences:"

  3598. msgstr ""

  3599. 

  3600. #: ../../../CHANGELOG.md:1971

  3601. msgid "it uses different names for its variables (`matrix_postgres` -> `devture_postgres`)"

  3602. msgstr ""

  3603. 

  3604. #: ../../../CHANGELOG.md:1972

  3605. msgid "when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-postgresql), it will vacuum all your databases, not just the Synapse one"

  3606. msgstr ""

  3607. 

  3608. #: ../../../CHANGELOG.md:1974

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

  3610. msgstr ""

  3611. 

  3612. #: ../../../CHANGELOG.md:1976

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

  3614. msgstr ""

  3615. 

  3616. #: ../../../CHANGELOG.md:1978

  3617. msgid "The playbook no longer installs scripts to /usr/local/bin"

  3618. msgstr ""

  3619. 

  3620. #: ../../../CHANGELOG.md:1980

  3621. msgid "The locations of various scripts installed by the playbook have changed."

  3622. msgstr ""

  3623. 

  3624. #: ../../../CHANGELOG.md:1982

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

  3626. msgstr ""

  3627. 

  3628. #: ../../../CHANGELOG.md:1984

  3629. msgid "`/usr/local/bin/matrix-remove-all` -> `/matrix/bin/remove-all`"

  3630. msgstr ""

  3631. 

  3632. #: ../../../CHANGELOG.md:1985

  3633. msgid "`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`"

  3634. msgstr ""

  3635. 

  3636. #: ../../../CHANGELOG.md:1986

  3637. msgid "`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> `/matrix/ssl/bin/lets-encrypt-certificates-renew`"

  3638. msgstr ""

  3639. 

  3640. #: ../../../CHANGELOG.md:1987

  3641. msgid "`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin/register-user`"

  3642. msgstr ""

  3643. 

  3644. #: ../../../CHANGELOG.md:1990

  3645. msgid "2022-11-25"

  3646. msgstr ""

  3647. 

  3648. #: ../../../CHANGELOG.md:1992

  3649. msgid "2x-5x performance improvements in playbook runtime"

  3650. msgstr ""

  3651. 

  3652. #: ../../../CHANGELOG.md:1994

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

  3654. msgstr ""

  3655. 

  3656. #: ../../../CHANGELOG.md:1996

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

  3658. msgstr ""

  3659. 

  3660. #: ../../../CHANGELOG.md:1998

  3661. msgid "Even when running `ansible-playbook` manually (as most of us here do), it's beneficial not to waste time and CPU resources."

  3662. msgstr ""

  3663. 

  3664. #: ../../../CHANGELOG.md:2000

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

  3666. msgstr ""

  3667. 

  3668. #: ../../../CHANGELOG.md:2002

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

  3670. msgstr ""

  3671. 

  3672. #: ../../../CHANGELOG.md:2004

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

  3674. msgstr ""

  3675. 

  3676. #: ../../../CHANGELOG.md:2006

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

  3678. msgstr ""

  3679. 

  3680. #: ../../../CHANGELOG.md:2008

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

  3682. msgstr ""

  3683. 

  3684. #: ../../../CHANGELOG.md:2011

  3685. msgid "2022-11-22"

  3686. msgstr ""

  3687. 

  3688. #: ../../../CHANGELOG.md:2013

  3689. msgid "Automatic `matrix_architecture` determination"

  3690. msgstr ""

  3691. 

  3692. #: ../../../CHANGELOG.md:2015

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

  3694. msgstr ""

  3695. 

  3696. #: ../../../CHANGELOG.md:2017

  3697. msgid "Docker and the Docker SDK for Python are now installed via external roles"

  3698. msgstr ""

  3699. 

  3700. #: ../../../CHANGELOG.md:2021

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

  3702. msgstr ""

  3703. 

  3704. #: ../../../CHANGELOG.md:2023

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

  3706. msgstr ""

  3707. 

  3708. #: ../../../CHANGELOG.md:2025

  3709. msgid "If you're hitting issues with Docker installation or Docker SDK for Python installation, consider reporting bugs or contributing to these other projects."

  3710. msgstr ""

  3711. 

  3712. #: ../../../CHANGELOG.md:2027

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

  3714. msgstr ""

  3715. 

  3716. #: ../../../CHANGELOG.md:2030

  3717. msgid "2022-11-20"

  3718. msgstr ""

  3719. 

  3720. #: ../../../CHANGELOG.md:2032

  3721. msgid "(Backward Compatibility Break) Changing how reverse-proxying to Synapse works — now via a `matrix-synapse-reverse-proxy-companion` service"

  3722. msgstr ""

  3723. 

  3724. #: ../../../CHANGELOG.md:2034

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

  3726. msgstr ""

  3727. 

  3728. #: ../../../CHANGELOG.md:2036

  3729. msgid "Background"

  3730. msgstr ""

  3731. 

  3732. #: ../../../CHANGELOG.md:2038

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

  3734. msgstr ""

  3735. 

  3736. #: ../../../CHANGELOG.md:2040

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

  3738. msgstr ""

  3739. 

  3740. #: ../../../CHANGELOG.md:2042

  3741. msgid "Solution"

  3742. msgstr ""

  3743. 

  3744. #: ../../../CHANGELOG.md:2044

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

  3746. msgstr ""

  3747. 

  3748. #: ../../../CHANGELOG.md:2046

  3749. msgid "serve as a companion to Synapse and know how to reverse-proxy to Synapse correctly (no matter if workers are enabled or not)"

  3750. msgstr ""

  3751. 

  3752. #: ../../../CHANGELOG.md:2048

  3753. msgid "provide a unified container address for reaching Synapse (no matter if workers are enabled or not)"

  3754. msgstr ""

  3755. 

  3756. #: ../../../CHANGELOG.md:2049

  3757. msgid "`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server API traffic"

  3758. msgstr ""

  3759. 

  3760. #: ../../../CHANGELOG.md:2050

  3761. msgid "`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server (Federation) API traffic"

  3762. msgstr ""

  3763. 

  3764. #: ../../../CHANGELOG.md:2052

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

  3766. msgstr ""

  3767. 

  3768. #: ../../../CHANGELOG.md:2054

  3769. msgid "allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is disabled"

  3770. msgstr ""

  3771. 

  3772. #: ../../../CHANGELOG.md:2056

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

  3774. msgstr ""

  3775. 

  3776. #: ../../../CHANGELOG.md:2058

  3777. msgid "(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> (`matrix-synapse` or some Synapse worker))."

  3778. msgstr ""

  3779. 

  3780. #: ../../../CHANGELOG.md:2060

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

  3782. msgstr ""

  3783. 

  3784. #: ../../../CHANGELOG.md:2062

  3785. msgid "Webserver configuration"

  3786. msgstr ""

  3787. 

  3788. #: ../../../CHANGELOG.md:2064

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

  3790. msgstr ""

  3791. 

  3792. #: ../../../CHANGELOG.md:2066

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

  3794. msgstr ""

  3795. 

  3796. #: ../../../CHANGELOG.md:2068

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

  3798. msgstr ""

  3799. 

  3800. #: ../../../CHANGELOG.md:2070

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

  3802. msgstr ""

  3803. 

  3804. #: ../../../CHANGELOG.md:2072

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

  3806. msgstr ""

  3807. 

  3808. #: ../../../CHANGELOG.md:2075

  3809. msgid "2022-11-05"

  3810. msgstr ""

  3811. 

  3812. #: ../../../CHANGELOG.md:2077

  3813. msgid "(Backward Compatibility Break) A new default standalone mode for Etherpad"

  3814. msgstr ""

  3815. 

  3816. #: ../../../CHANGELOG.md:2079

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

  3818. msgstr ""

  3819. 

  3820. #: ../../../CHANGELOG.md:2081

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

  3822. msgstr ""

  3823. 

  3824. #: ../../../CHANGELOG.md:2083

  3825. msgid "If you've already got both Etherpad and Dimension in use you could:"

  3826. msgstr ""

  3827. 

  3828. #: ../../../CHANGELOG.md:2085

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

  3830. msgstr ""

  3831. 

  3832. #: ../../../CHANGELOG.md:2087

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

  3834. msgstr ""

  3835. 

  3836. #: ../../../CHANGELOG.md:2090

  3837. msgid "2022-11-04"

  3838. msgstr ""

  3839. 

  3840. #: ../../../CHANGELOG.md:2092

  3841. msgid "The playbook now uses external roles for some things"

  3842. msgstr ""

  3843. 

  3844. #: ../../../CHANGELOG.md:2094

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

  3846. msgstr ""

  3847. 

  3848. #: ../../../CHANGELOG.md:2096

  3849. msgid "We're in the process of trimming the playbook and making it reuse Ansible roles."

  3850. msgstr ""

  3851. 

  3852. #: ../../../CHANGELOG.md:2098

  3853. msgid "Starting now, the playbook is composed of 2 types of Ansible roles:"

  3854. msgstr ""

  3855. 

  3856. #: ../../../CHANGELOG.md:2100

  3857. msgid "those that live within the playbook itself (`roles/custom/*`)"

  3858. msgstr ""

  3859. 

  3860. #: ../../../CHANGELOG.md:2102

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

  3862. msgstr ""

  3863. 

  3864. #: ../../../CHANGELOG.md:2104

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

  3866. msgstr ""

  3867. 

  3868. #: ../../../CHANGELOG.md:2106

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

  3870. msgstr ""

  3871. 

  3872. #: ../../../CHANGELOG.md:2108

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

  3874. msgstr ""

  3875. 

  3876. #: ../../../CHANGELOG.md:2111

  3877. msgid "2022-10-14"

  3878. msgstr ""

  3879. 

  3880. #: ../../../CHANGELOG.md:2113

  3881. msgid "synapse-s3-storage-provider support"

  3882. msgstr ""

  3883. 

  3884. #: ../../../CHANGELOG.md:2115

  3885. msgid "**`synapse-s3-storage-provider` support is very new and still relatively untested. Using it may cause data loss.**"

  3886. msgstr ""

  3887. 

  3888. #: ../../../CHANGELOG.md:2117

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

  3890. msgstr ""

  3891. 

  3892. #: ../../../CHANGELOG.md:2119

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

  3894. msgstr ""

  3895. 

  3896. #: ../../../CHANGELOG.md:2121

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

  3898. msgstr ""

  3899. 

  3900. #: ../../../CHANGELOG.md:2123

  3901. msgid "Synapse container image customization support"

  3902. msgstr ""

  3903. 

  3904. #: ../../../CHANGELOG.md:2125

  3905. msgid "We now support customizing the Synapse container image by adding additional build steps to its [`Dockerfile`](https://docs.docker.com/engine/reference/builder/)."

  3906. msgstr ""

  3907. 

  3908. #: ../../../CHANGELOG.md:2127

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

  3910. msgstr ""

  3911. 

  3912. #: ../../../CHANGELOG.md:2129

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

  3914. msgstr ""

  3915. 

  3916. #: ../../../CHANGELOG.md:2140

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

  3918. msgstr ""

  3919. 

  3920. #: ../../../CHANGELOG.md:2142

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

  3922. msgstr ""

  3923. 

  3924. #: ../../../CHANGELOG.md:2145

  3925. msgid "2022-10-02"

  3926. msgstr ""

  3927. 

  3928. #: ../../../CHANGELOG.md:2147

  3929. msgid "matrix-ldap-registration-proxy support"

  3930. msgstr ""

  3931. 

  3932. #: ../../../CHANGELOG.md:2149

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

  3934. msgstr ""

  3935. 

  3936. #: ../../../CHANGELOG.md:2151

  3937. msgid "See our [Setting up matrix-ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started."

  3938. msgstr ""

  3939. 

  3940. #: ../../../CHANGELOG.md:2154

  3941. msgid "2022-09-15"

  3942. msgstr ""

  3943. 

  3944. #: ../../../CHANGELOG.md:2156

  3945. msgid "(Potential Backward Compatibility Break) Major improvements to Synapse workers"

  3946. msgstr ""

  3947. 

  3948. #: ../../../CHANGELOG.md:2158

  3949. msgid "People who are interested in running a Synapse worker setup should know that **our Synapse worker implementation is much more powerful now**:"

  3950. msgstr ""

  3951. 

  3952. #: ../../../CHANGELOG.md:2160

  3953. msgid "we've added support for [Stream writers](#stream-writers-support)"

  3954. msgstr ""

  3955. 

  3956. #: ../../../CHANGELOG.md:2161

  3957. msgid "we've added support for [multiple federation sender workers](#multiple-federation-sender-workers-support)"

  3958. msgstr ""

  3959. 

  3960. #: ../../../CHANGELOG.md:2162

  3961. msgid "we've added support for [multiple pusher workers](#multiple-pusher-workers-support)"

  3962. msgstr ""

  3963. 

  3964. #: ../../../CHANGELOG.md:2163

  3965. msgid "we've added support for [running background tasks on a worker](#background-tasks-can-run-on-a-worker)"

  3966. msgstr ""

  3967. 

  3968. #: ../../../CHANGELOG.md:2164

  3969. msgid "we've restored support for [`appservice` workers](#appservice-worker-support-is-back)"

  3970. msgstr ""

  3971. 

  3972. #: ../../../CHANGELOG.md:2165

  3973. msgid "we've restored support for [`user_dir` workers](#user-directory-worker-support-is-back)"

  3974. msgstr ""

  3975. 

  3976. #: ../../../CHANGELOG.md:2166

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

  3978. msgstr ""

  3979. 

  3980. #: ../../../CHANGELOG.md:2167

  3981. msgid "see the [Potential Backward Incompatibilities after these Synapse worker changes](#potential-backward-incompatibilities-after-these-synapse-worker-changes)"

  3982. msgstr ""

  3983. 

  3984. #: ../../../CHANGELOG.md:2169

  3985. msgid "Stream writers support"

  3986. msgstr ""

  3987. 

  3988. #: ../../../CHANGELOG.md:2171

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

  3990. msgstr ""

  3991. 

  3992. #: ../../../CHANGELOG.md:2173

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

  3994. msgstr ""

  3995. 

  3996. #: ../../../CHANGELOG.md:2175

  3997. msgid "If you'd like to customize the number of workers we also make that possible using these variables:"

  3998. msgstr ""

  3999. 

  4000. #: ../../../CHANGELOG.md:2188

  4001. msgid "Multiple federation sender workers support"

  4002. msgstr ""

  4003. 

  4004. #: ../../../CHANGELOG.md:2190

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

  4006. msgstr ""

  4007. 

  4008. #: ../../../CHANGELOG.md:2192

  4009. msgid "Multiple pusher workers support"

  4010. msgstr ""

  4011. 

  4012. #: ../../../CHANGELOG.md:2194

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

  4014. msgstr ""

  4015. 

  4016. #: ../../../CHANGELOG.md:2196

  4017. msgid "Background tasks can run on a worker"

  4018. msgstr ""

  4019. 

  4020. #: ../../../CHANGELOG.md:2198

  4021. msgid "From now on, you can put [background task processing on a worker](https://matrix-org.github.io/synapse/latest/workers.html#background-tasks)."

  4022. msgstr ""

  4023. 

  4024. #: ../../../CHANGELOG.md:2200

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

  4026. msgstr ""

  4027. 

  4028. #: ../../../CHANGELOG.md:2202

  4029. msgid "Appservice worker support is back"

  4030. msgstr ""

  4031. 

  4032. #: ../../../CHANGELOG.md:2204

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

  4034. msgstr ""

  4035. 

  4036. #: ../../../CHANGELOG.md:2206

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

  4038. msgstr ""

  4039. 

  4040. #: ../../../CHANGELOG.md:2208

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

  4042. msgstr ""

  4043. 

  4044. #: ../../../CHANGELOG.md:2210

  4045. msgid "User Directory worker support is back"

  4046. msgstr ""

  4047. 

  4048. #: ../../../CHANGELOG.md:2212

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

  4050. msgstr ""

  4051. 

  4052. #: ../../../CHANGELOG.md:2214

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

  4054. msgstr ""

  4055. 

  4056. #: ../../../CHANGELOG.md:2216

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

  4058. msgstr ""

  4059. 

  4060. #: ../../../CHANGELOG.md:2218

  4061. msgid "Using more than 1 media repository worker is now more reliable"

  4062. msgstr ""

  4063. 

  4064. #: ../../../CHANGELOG.md:2220

  4065. msgid "With `matrix_synapse_workers_preset: one-of-each`, we only launch one `media_repository` worker."

  4066. msgstr ""

  4067. 

  4068. #: ../../../CHANGELOG.md:2222

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

  4070. msgstr ""

  4071. 

  4072. #: ../../../CHANGELOG.md:2224

  4073. msgid "Potential Backward Incompatibilities after these Synapse worker changes"

  4074. msgstr ""

  4075. 

  4076. #: ../../../CHANGELOG.md:2226

  4077. msgid "Below we'll discuss **potential backward incompatibilities**."

  4078. msgstr ""

  4079. 

  4080. #: ../../../CHANGELOG.md:2228

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

  4082. msgstr ""

  4083. 

  4084. #: ../../../CHANGELOG.md:2230

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

  4086. msgstr ""

  4087. 

  4088. #: ../../../CHANGELOG.md:2232

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

  4090. msgstr ""

  4091. 

  4092. #: ../../../CHANGELOG.md:2234

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

  4094. msgstr ""

  4095. 

  4096. #: ../../../CHANGELOG.md:2237

  4097. msgid "2022-09-09"

  4098. msgstr ""

  4099. 

  4100. #: ../../../CHANGELOG.md:2239

  4101. msgid "Cactus Comments support"

  4102. msgstr ""

  4103. 

  4104. #: ../../../CHANGELOG.md:2241

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

  4106. msgstr ""

  4107. 

  4108. #: ../../../CHANGELOG.md:2243

  4109. msgid "See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-comments.md) documentation to get started."

  4110. msgstr ""

  4111. 

  4112. #: ../../../CHANGELOG.md:2246

  4113. msgid "2022-08-23"

  4114. msgstr ""

  4115. 

  4116. #: ../../../CHANGELOG.md:2248

  4117. msgid "Postmoogle email bridge support"

  4118. msgstr ""

  4119. 

  4120. #: ../../../CHANGELOG.md:2250

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

  4122. msgstr ""

  4123. 

  4124. #: ../../../CHANGELOG.md:2252

  4125. msgid "See our [Setting up Postmoogle email bridging](docs/configuring-playbook-bridge-postmoogle.md) documentation to get started."

  4126. msgstr ""

  4127. 

  4128. #: ../../../CHANGELOG.md:2255

  4129. msgid "2022-08-10"

  4130. msgstr ""

  4131. 

  4132. #: ../../../CHANGELOG.md:2257

  4133. msgid "mautrix-whatsapp default configuration changes"

  4134. msgstr ""

  4135. 

  4136. #: ../../../CHANGELOG.md:2259

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

  4138. msgstr ""

  4139. 

  4140. #: ../../../CHANGELOG.md:2261

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

  4142. msgstr ""

  4143. 

  4144. #: ../../../CHANGELOG.md:2263

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

  4146. msgstr ""

  4147. 

  4148. #: ../../../CHANGELOG.md:2266

  4149. msgid "2022-08-09"

  4150. msgstr ""

  4151. 

  4152. #: ../../../CHANGELOG.md:2268

  4153. msgid "Conduit support"

  4154. msgstr ""

  4155. 

  4156. #: ../../../CHANGELOG.md:2270

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

  4158. msgstr ""

  4159. 

  4160. #: ../../../CHANGELOG.md:2272

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

  4162. msgstr ""

  4163. 

  4164. #: ../../../CHANGELOG.md:2274

  4165. msgid "To try out Conduit, we recommend that you **use a new server** and the following `vars.yml` configuration:"

  4166. msgstr ""

  4167. 

  4168. #: ../../../CHANGELOG.md:2280

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

  4170. msgstr ""

  4171. 

  4172. #: ../../../CHANGELOG.md:2283

  4173. msgid "2022-07-29"

  4174. msgstr ""

  4175. 

  4176. #: ../../../CHANGELOG.md:2285

  4177. msgid "mautrix-discord support"

  4178. msgstr ""

  4179. 

  4180. #: ../../../CHANGELOG.md:2287

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

  4182. msgstr ""

  4183. 

  4184. #: ../../../CHANGELOG.md:2289

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

  4186. msgstr ""

  4187. 

  4188. #: ../../../CHANGELOG.md:2292

  4189. msgid "2022-07-27"

  4190. msgstr ""

  4191. 

  4192. #: ../../../CHANGELOG.md:2294

  4193. msgid "matrix-appservice-kakaotalk support"

  4194. msgstr ""

  4195. 

  4196. #: ../../../CHANGELOG.md:2296

  4197. 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!"

  4198. msgstr ""

  4199. 

  4200. #: ../../../CHANGELOG.md:2298

  4201. msgid "See our [Setting up Appservice Kakaotalk bridging](docs/configuring-playbook-bridge-appservice-kakaotalk.md) documentation to get started."

  4202. msgstr ""

  4203. 

  4204. #: ../../../CHANGELOG.md:2301

  4205. msgid "2022-07-20"

  4206. msgstr ""

  4207. 

  4208. #: ../../../CHANGELOG.md:2303

  4209. msgid "maubot support"

  4210. msgstr ""

  4211. 

  4212. #: ../../../CHANGELOG.md:2305

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

  4214. msgstr ""

  4215. 

  4216. #: ../../../CHANGELOG.md:2307

  4217. msgid "See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) documentation to get started."

  4218. msgstr ""

  4219. 

  4220. #: ../../../CHANGELOG.md:2310

  4221. msgid "2022-07-14"

  4222. msgstr ""

  4223. 

  4224. #: ../../../CHANGELOG.md:2312

  4225. msgid "mx-puppet-skype removal"

  4226. msgstr ""

  4227. 

  4228. #: ../../../CHANGELOG.md:2314

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

  4230. msgstr ""

  4231. 

  4232. #: ../../../CHANGELOG.md:2316

  4233. msgid "To completely clean up your server from `mx-puppet-skype`'s presence on it:"

  4234. msgstr ""

  4235. 

  4236. #: ../../../CHANGELOG.md:2318

  4237. msgid "ensure your Ansible configuration (`vars.yml` file) no longer contains `matrix_mx_puppet_skype_*` references"

  4238. msgstr ""

  4239. 

  4240. #: ../../../CHANGELOG.md:2319

  4241. msgid "stop and disable the systemd service (run `systemctl disable --now matrix-mx-puppet-skype` on the server)"

  4242. msgstr ""

  4243. 

  4244. #: ../../../CHANGELOG.md:2320

  4245. msgid "delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-skype.service` on the server)"

  4246. msgstr ""

  4247. 

  4248. #: ../../../CHANGELOG.md:2321

  4249. msgid "delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on the server)"

  4250. msgstr ""

  4251. 

  4252. #: ../../../CHANGELOG.md:2322

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

  4254. msgstr ""

  4255. 

  4256. #: ../../../CHANGELOG.md:2324

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

  4258. msgstr ""

  4259. 

  4260. #: ../../../CHANGELOG.md:2326

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

  4262. msgstr ""

  4263. 

  4264. #: ../../../CHANGELOG.md:2328

  4265. msgid "signald (0.19.0+) upgrade requires data migration"

  4266. msgstr ""

  4267. 

  4268. #: ../../../CHANGELOG.md:2330

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

  4270. msgstr ""

  4271. 

  4272. #: ../../../CHANGELOG.md:2332

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

  4274. msgstr ""

  4275. 

  4276. #: ../../../CHANGELOG.md:2334

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

  4278. msgstr ""

  4279. 

  4280. #: ../../../CHANGELOG.md:2336

  4281. msgid "We attempt to do this data migration automatically every time Signald starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` systemd unit definition."

  4282. msgstr ""

  4283. 

  4284. #: ../../../CHANGELOG.md:2338

  4285. 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!"

  4286. msgstr ""

  4287. 

  4288. #: ../../../CHANGELOG.md:2341

  4289. msgid "2022-07-05"

  4290. msgstr ""

  4291. 

  4292. #: ../../../CHANGELOG.md:2343

  4293. msgid "Ntfy push notifications support"

  4294. msgstr ""

  4295. 

  4296. #: ../../../CHANGELOG.md:2345

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

  4298. msgstr ""

  4299. 

  4300. #: ../../../CHANGELOG.md:2347

  4301. msgid "See our [Setting up the ntfy push notifications server](docs/configuring-playbook-ntfy.md) documentation to get started."

  4302. msgstr ""

  4303. 

  4304. #: ../../../CHANGELOG.md:2350

  4305. msgid "2022-06-23"

  4306. msgstr ""

  4307. 

  4308. #: ../../../CHANGELOG.md:2352

  4309. msgid "(Potential Backward Compatibility Break) Changes around metrics collection"

  4310. msgstr ""

  4311. 

  4312. #: ../../../CHANGELOG.md:2354

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

  4314. msgstr ""

  4315. 

  4316. #: ../../../CHANGELOG.md:2356

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

  4318. msgstr ""

  4319. 

  4320. #: ../../../CHANGELOG.md:2358

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

  4322. msgstr ""

  4323. 

  4324. #: ../../../CHANGELOG.md:2360

  4325. msgid "**If you are using the [Hookshot bridge](docs/configuring-playbook-bridge-hookshot.md)**, you may find that:"

  4326. msgstr ""

  4327. 

  4328. #: ../../../CHANGELOG.md:2361

  4329. msgid "**Metrics may not be enabled by default anymore**:"

  4330. msgstr ""

  4331. 

  4332. #: ../../../CHANGELOG.md:2362

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

  4334. msgstr ""

  4335. 

  4336. #: ../../../CHANGELOG.md:2363

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

  4338. msgstr ""

  4339. 

  4340. #: ../../../CHANGELOG.md:2364

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

  4342. msgstr ""

  4343. 

  4344. #: ../../../CHANGELOG.md:2365

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

  4346. msgstr ""

  4347. 

  4348. #: ../../../CHANGELOG.md:2367

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

  4350. msgstr ""

  4351. 

  4352. #: ../../../CHANGELOG.md:2369

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

  4354. msgstr ""

  4355. 

  4356. #: ../../../CHANGELOG.md:2371

  4357. msgid "**If you're using Synapse** and would like to collect its metrics from an external Prometheus server, you may find that:"

  4358. msgstr ""

  4359. 

  4360. #: ../../../CHANGELOG.md:2373

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

  4362. msgstr ""

  4363. 

  4364. #: ../../../CHANGELOG.md:2374

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

  4366. msgstr ""

  4367. 

  4368. #: ../../../CHANGELOG.md:2375

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

  4370. msgstr ""

  4371. 

  4372. #: ../../../CHANGELOG.md:2376

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

  4374. msgstr ""

  4375. 

  4376. #: ../../../CHANGELOG.md:2378

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

  4378. msgstr ""

  4379. 

  4380. #: ../../../CHANGELOG.md:2380

  4381. msgid "2022-06-13"

  4382. msgstr ""

  4383. 

  4384. #: ../../../CHANGELOG.md:2382

  4385. msgid "go-skype-bridge bridging support"

  4386. msgstr ""

  4387. 

  4388. #: ../../../CHANGELOG.md:2384

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

  4390. msgstr ""

  4391. 

  4392. #: ../../../CHANGELOG.md:2386

  4393. msgid "See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md) documentation to get started."

  4394. msgstr ""

  4395. 

  4396. #: ../../../CHANGELOG.md:2388

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

  4398. msgstr ""

  4399. 

  4400. #: ../../../CHANGELOG.md:2391

  4401. msgid "2022-06-09"

  4402. msgstr ""

  4403. 

  4404. #: ../../../CHANGELOG.md:2393

  4405. msgid "Running Ansible in a container can now happen on the Matrix server itself"

  4406. msgstr ""

  4407. 

  4408. #: ../../../CHANGELOG.md:2395

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

  4410. msgstr ""

  4411. 

  4412. #: ../../../CHANGELOG.md:2398

  4413. msgid "2022-05-31"

  4414. msgstr ""

  4415. 

  4416. #: ../../../CHANGELOG.md:2400

  4417. msgid "Synapse v1.60 upgrade may cause trouble and require manual intervention"

  4418. msgstr ""

  4419. 

  4420. #: ../../../CHANGELOG.md:2402

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

  4422. msgstr ""

  4423. 

  4424. #: ../../../CHANGELOG.md:2404

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

  4426. msgstr ""

  4427. 

  4428. #: ../../../CHANGELOG.md:2406

  4429. msgid "**If Synapse fails to start** after your next playbook run, you'll need to:"

  4430. msgstr ""

  4431. 

  4432. #: ../../../CHANGELOG.md:2408

  4433. msgid "SSH into the Matrix server"

  4434. msgstr ""

  4435. 

  4436. #: ../../../CHANGELOG.md:2409

  4437. msgid "launch `/usr/local/bin/matrix-postgres-cli`"

  4438. msgstr ""

  4439. 

  4440. #: ../../../CHANGELOG.md:2410

  4441. msgid "switch to the `synapse` database: `\\c synapse`"

  4442. msgstr ""

  4443. 

  4444. #: ../../../CHANGELOG.md:2411

  4445. msgid "run the following SQL query:"

  4446. msgstr ""

  4447. 

  4448. #: ../../../CHANGELOG.md:2430

  4449. msgid "You could then restart services: `ansible-playbook -i inventory/hosts setup.yml --tags=start`"

  4450. msgstr ""

  4451. 

  4452. #: ../../../CHANGELOG.md:2433

  4453. msgid "2022-04-25"

  4454. msgstr ""

  4455. 

  4456. #: ../../../CHANGELOG.md:2435

  4457. msgid "Buscarron bot support"

  4458. msgstr ""

  4459. 

  4460. #: ../../../CHANGELOG.md:2437

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

  4462. msgstr ""

  4463. 

  4464. #: ../../../CHANGELOG.md:2439

  4465. msgid "See our [Setting up Buscarron](docs/configuring-playbook-bot-buscarron.md) documentation to get started."

  4466. msgstr ""

  4467. 

  4468. #: ../../../CHANGELOG.md:2442

  4469. msgid "2022-04-21"

  4470. msgstr ""

  4471. 

  4472. #: ../../../CHANGELOG.md:2444

  4473. msgid "matrix-registration-bot support"

  4474. msgstr ""

  4475. 

  4476. #: ../../../CHANGELOG.md:2446

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

  4478. msgstr ""

  4479. 

  4480. #: ../../../CHANGELOG.md:2448

  4481. msgid "See our [Setting up matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) documentation to get started."

  4482. msgstr ""

  4483. 

  4484. #: ../../../CHANGELOG.md:2451

  4485. msgid "2022-04-19"

  4486. msgstr ""

  4487. 

  4488. #: ../../../CHANGELOG.md:2453

  4489. msgid "BorgBackup support"

  4490. msgstr ""

  4491. 

  4492. #: ../../../CHANGELOG.md:2455

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

  4494. msgstr ""

  4495. 

  4496. #: ../../../CHANGELOG.md:2457

  4497. msgid "See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md) documentation to get started."

  4498. msgstr ""

  4499. 

  4500. #: ../../../CHANGELOG.md:2459

  4501. msgid "(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action"

  4502. msgstr ""

  4503. 

  4504. #: ../../../CHANGELOG.md:2461

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

  4506. msgstr ""

  4507. 

  4508. #: ../../../CHANGELOG.md:2463

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

  4510. msgstr ""

  4511. 

  4512. #: ../../../CHANGELOG.md:2465

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

  4514. msgstr ""

  4515. 

  4516. #: ../../../CHANGELOG.md:2467

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

  4518. msgstr ""

  4519. 

  4520. #: ../../../CHANGELOG.md:2469

  4521. msgid "Pull the latest playbook changes"

  4522. msgstr ""

  4523. 

  4524. #: ../../../CHANGELOG.md:2470

  4525. msgid "Stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"

  4526. msgstr ""

  4527. 

  4528. #: ../../../CHANGELOG.md:2471

  4529. msgid "Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all`)"

  4530. msgstr ""

  4531. 

  4532. #: ../../../CHANGELOG.md:2472

  4533. msgid "Start Postgres (`systemctl start matrix-postgres` on the server)"

  4534. msgstr ""

  4535. 

  4536. #: ../../../CHANGELOG.md:2473

  4537. msgid "Start the main Synapse process (`systemctl start matrix-synapse` on the server)"

  4538. msgstr ""

  4539. 

  4540. #: ../../../CHANGELOG.md:2474

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

  4542. msgstr ""

  4543. 

  4544. #: ../../../CHANGELOG.md:2475

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

  4546. msgstr ""

  4547. 

  4548. #: ../../../CHANGELOG.md:2478

  4549. msgid "2022-04-14"

  4550. msgstr ""

  4551. 

  4552. #: ../../../CHANGELOG.md:2480

  4553. msgid "(Compatibility Break) Changes to `docker-src` permissions necessitating manual action"

  4554. msgstr ""

  4555. 

  4556. #: ../../../CHANGELOG.md:2482

  4557. msgid "Users who build container images from source will need to manually correct file permissions of some directories on the server."

  4558. msgstr ""

  4559. 

  4560. #: ../../../CHANGELOG.md:2484

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

  4562. msgstr ""

  4563. 

  4564. #: ../../../CHANGELOG.md:2486

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

  4566. msgstr ""

  4567. 

  4568. #: ../../../CHANGELOG.md:2488

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

  4570. msgstr ""

  4571. 

  4572. #: ../../../CHANGELOG.md:2491

  4573. msgid "2022-03-17"

  4574. msgstr ""

  4575. 

  4576. #: ../../../CHANGELOG.md:2493

  4577. msgid "(Compatibility Break) ma1sd identity server no longer installed by default"

  4578. msgstr ""

  4579. 

  4580. #: ../../../CHANGELOG.md:2495

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

  4582. msgstr ""

  4583. 

  4584. #: ../../../CHANGELOG.md:2497

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

  4586. msgstr ""

  4587. 

  4588. #: ../../../CHANGELOG.md:2499

  4589. msgid "Since Element clients no longer default to using a public identity server if another one is not provided, we can stop installing ma1sd."

  4590. msgstr ""

  4591. 

  4592. #: ../../../CHANGELOG.md:2501

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

  4594. msgstr ""

  4595. 

  4596. #: ../../../CHANGELOG.md:2508

  4597. msgid "2022-02-12"

  4598. msgstr ""

  4599. 

  4600. #: ../../../CHANGELOG.md:2510

  4601. msgid "matrix_encryption_disabler support"

  4602. msgstr ""

  4603. 

  4604. #: ../../../CHANGELOG.md:2512

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

  4606. msgstr ""

  4607. 

  4608. #: ../../../CHANGELOG.md:2514

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

  4610. msgstr ""

  4611. 

  4612. #: ../../../CHANGELOG.md:2517

  4613. msgid "2022-02-01"

  4614. msgstr ""

  4615. 

  4616. #: ../../../CHANGELOG.md:2519

  4617. msgid "matrix-hookshot bridging support"

  4618. msgstr ""

  4619. 

  4620. #: ../../../CHANGELOG.md:2521

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

  4622. msgstr ""

  4623. 

  4624. #: ../../../CHANGELOG.md:2524

  4625. msgid "2022-01-31"

  4626. msgstr ""

  4627. 

  4628. #: ../../../CHANGELOG.md:2526

  4629. msgid "ARM support for matrix-corporal"

  4630. msgstr ""

  4631. 

  4632. #: ../../../CHANGELOG.md:2528

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

  4634. msgstr ""

  4635. 

  4636. #: ../../../CHANGELOG.md:2531

  4637. msgid "2022-01-07"

  4638. msgstr ""

  4639. 

  4640. #: ../../../CHANGELOG.md:2533

  4641. msgid "Dendrite support"

  4642. msgstr ""

  4643. 

  4644. #: ../../../CHANGELOG.md:2535

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

  4646. msgstr ""

  4647. 

  4648. #: ../../../CHANGELOG.md:2537

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

  4650. msgstr ""

  4651. 

  4652. #: ../../../CHANGELOG.md:2539

  4653. msgid "We believe that 2022 will be the year of the non-Synapse Matrix server!"

  4654. msgstr ""

  4655. 

  4656. #: ../../../CHANGELOG.md:2541

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

  4658. msgstr ""

  4659. 

  4660. #: ../../../CHANGELOG.md:2543

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

  4662. msgstr ""

  4663. 

  4664. #: ../../../CHANGELOG.md:2545

  4665. msgid "Adapting the configuration for existing Synapse installations"

  4666. msgstr ""

  4667. 

  4668. #: ../../../CHANGELOG.md:2547

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

  4670. msgstr ""

  4671. 

  4672. #: ../../../CHANGELOG.md:2549

  4673. msgid "The `vars.yml` file for **existing installations will need to be updated** by adding this **additional configuration**:"

  4674. msgstr ""

  4675. 

  4676. #: ../../../CHANGELOG.md:2561

  4677. msgid "Trying out Dendrite"

  4678. msgstr ""

  4679. 

  4680. #: ../../../CHANGELOG.md:2563

  4681. msgid "Finally, **to try out Dendrite**, we recommend that you **use a new server** and the following addition to your `vars.yml` configuration:"

  4682. msgstr ""

  4683. 

  4684. #: ../../../CHANGELOG.md:2569

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

  4686. msgstr ""

  4687. 

  4688. #: ../../../CHANGELOG.md:2571

  4689. msgid "We're excited to gain support for other homeserver implementations, like [Conduit](https://conduit.rs/), etc!"

  4690. msgstr ""

  4691. 

  4692. #: ../../../CHANGELOG.md:2573

  4693. msgid "Honoroit bot support"

  4694. msgstr ""

  4695. 

  4696. #: ../../../CHANGELOG.md:2575

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

  4698. msgstr ""

  4699. 

  4700. #: ../../../CHANGELOG.md:2577

  4701. msgid "See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documentation to get started."

  4702. msgstr ""

  4703. 

  4704. #: ../../../CHANGELOG.md:2580

  4705. msgid "2022-01-06"

  4706. msgstr ""

  4707. 

  4708. #: ../../../CHANGELOG.md:2582

  4709. msgid "Cinny support"

  4710. msgstr ""

  4711. 

  4712. #: ../../../CHANGELOG.md:2584

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

  4714. msgstr ""

  4715. 

  4716. #: ../../../CHANGELOG.md:2586

  4717. msgid "By default, we still install Element Web. Still, people who'd like to try Cinny out can now install it via the playbook."

  4718. msgstr ""

  4719. 

  4720. #: ../../../CHANGELOG.md:2588

  4721. msgid "Additional details are available in [Setting up Cinny](docs/configuring-playbook-client-cinny.md)."

  4722. msgstr ""

  4723. 

  4724. #: ../../../CHANGELOG.md:2591

  4725. msgid "2021-12-22"

  4726. msgstr ""

  4727. 

  4728. #: ../../../CHANGELOG.md:2593

  4729. msgid "Twitter bridging support via mautrix-twitter"

  4730. msgstr ""

  4731. 

  4732. #: ../../../CHANGELOG.md:2595

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

  4734. msgstr ""

  4735. 

  4736. #: ../../../CHANGELOG.md:2598

  4737. msgid "2021-12-14"

  4738. msgstr ""

  4739. 

  4740. #: ../../../CHANGELOG.md:2600

  4741. msgid "(Security) Users of the Signal bridge may wish to upgrade it to work around log4j vulnerability"

  4742. msgstr ""

  4743. 

  4744. #: ../../../CHANGELOG.md:2602

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

  4746. msgstr ""

  4747. 

  4748. #: ../../../CHANGELOG.md:2604

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

  4750. msgstr ""

  4751. 

  4752. #: ../../../CHANGELOG.md:2607

  4753. msgid "2021-11-11"

  4754. msgstr ""

  4755. 

  4756. #: ../../../CHANGELOG.md:2609

  4757. msgid "Dropped support for Postgres v9.6"

  4758. msgstr ""

  4759. 

  4760. #: ../../../CHANGELOG.md:2611

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

  4762. msgstr ""

  4763. 

  4764. #: ../../../CHANGELOG.md:2613

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

  4766. msgstr ""

  4767. 

  4768. #: ../../../CHANGELOG.md:2616

  4769. msgid "2021-10-23"

  4770. msgstr ""

  4771. 

  4772. #: ../../../CHANGELOG.md:2618

  4773. msgid "Hangouts bridge no longer updated, superseded by a Googlechat bridge"

  4774. msgstr ""

  4775. 

  4776. #: ../../../CHANGELOG.md:2620

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

  4778. msgstr ""

  4779. 

  4780. #: ../../../CHANGELOG.md:2622

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

  4782. msgstr ""

  4783. 

  4784. #: ../../../CHANGELOG.md:2625

  4785. msgid "2021-08-23"

  4786. msgstr ""

  4787. 

  4788. #: ../../../CHANGELOG.md:2627

  4789. msgid "LinkedIn bridging support via beeper-linkedin"

  4790. msgstr ""

  4791. 

  4792. #: ../../../CHANGELOG.md:2629

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

  4794. msgstr ""

  4795. 

  4796. #: ../../../CHANGELOG.md:2631

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

  4798. msgstr ""

  4799. 

  4800. #: ../../../CHANGELOG.md:2633

  4801. msgid "To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)."

  4802. msgstr ""

  4803. 

  4804. #: ../../../CHANGELOG.md:2636

  4805. msgid "2021-08-20"

  4806. msgstr ""

  4807. 

  4808. #: ../../../CHANGELOG.md:2638

  4809. msgid "Sygnal upgraded — ARM support and no longer requires a database"

  4810. msgstr ""

  4811. 

  4812. #: ../../../CHANGELOG.md:2640

  4813. msgid "The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been upgraded from `v0.9.0` to `v0.10.1`."

  4814. msgstr ""

  4815. 

  4816. #: ../../../CHANGELOG.md:2642

  4817. msgid "This is an optional component for the playbook, so most of our users wouldn't care about this announcement."

  4818. msgstr ""

  4819. 

  4820. #: ../../../CHANGELOG.md:2644

  4821. msgid "Since this feels like a relatively big (and untested, as of yet) Sygnal change, we're putting up this changelog entry."

  4822. msgstr ""

  4823. 

  4824. #: ../../../CHANGELOG.md:2646

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

  4826. msgstr ""

  4827. 

  4828. #: ../../../CHANGELOG.md:2649

  4829. msgid "2021-05-21"

  4830. msgstr ""

  4831. 

  4832. #: ../../../CHANGELOG.md:2651

  4833. msgid "Hydrogen support"

  4834. msgstr ""

  4835. 

  4836. #: ../../../CHANGELOG.md:2653

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

  4838. msgstr ""

  4839. 

  4840. #: ../../../CHANGELOG.md:2655

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

  4842. msgstr ""

  4843. 

  4844. #: ../../../CHANGELOG.md:2657

  4845. msgid "Additional details are available in [Setting up Hydrogen](docs/configuring-playbook-client-hydrogen.md)."

  4846. msgstr ""

  4847. 

  4848. #: ../../../CHANGELOG.md:2660

  4849. msgid "2021-05-19"

  4850. msgstr ""

  4851. 

  4852. #: ../../../CHANGELOG.md:2662

  4853. msgid "Heisenbridge support"

  4854. msgstr ""

  4855. 

  4856. #: ../../../CHANGELOG.md:2664

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

  4858. msgstr ""

  4859. 

  4860. #: ../../../CHANGELOG.md:2666

  4861. msgid "Additional details are available in [Setting up Heisenbridge bouncer-style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)."

  4862. msgstr ""

  4863. 

  4864. #: ../../../CHANGELOG.md:2669

  4865. msgid "2021-04-16"

  4866. msgstr ""

  4867. 

  4868. #: ../../../CHANGELOG.md:2671

  4869. msgid "Disabling TLSv1 and TLSv1.1 for coturn"

  4870. msgstr ""

  4871. 

  4872. #: ../../../CHANGELOG.md:2673

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

  4874. msgstr ""

  4875. 

  4876. #: ../../../CHANGELOG.md:2675

  4877. msgid "If you need to support old clients, you can re-enable both (or whichever one you need) with the following configuration:"

  4878. msgstr ""

  4879. 

  4880. #: ../../../CHANGELOG.md:2683

  4881. msgid "2021-04-05"

  4882. msgstr ""

  4883. 

  4884. #: ../../../CHANGELOG.md:2685

  4885. msgid "Automated local Postgres backup support"

  4886. msgstr ""

  4887. 

  4888. #: ../../../CHANGELOG.md:2687

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

  4890. msgstr ""

  4891. 

  4892. #: ../../../CHANGELOG.md:2689

  4893. msgid "Additional details are available in [Setting up Postgres backup](docs/configuring-playbook-postgres-backup.md)."

  4894. msgstr ""

  4895. 

  4896. #: ../../../CHANGELOG.md:2692

  4897. msgid "2021-04-03"

  4898. msgstr ""

  4899. 

  4900. #: ../../../CHANGELOG.md:2694

  4901. msgid "Mjolnir moderation tool (bot) support"

  4902. msgstr ""

  4903. 

  4904. #: ../../../CHANGELOG.md:2696

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

  4906. msgstr ""

  4907. 

  4908. #: ../../../CHANGELOG.md:2698

  4909. msgid "Additional details are available in [Setting up Mjolnir](docs/configuring-playbook-bot-mjolnir.md)."

  4910. msgstr ""

  4911. 

  4912. #: ../../../CHANGELOG.md:2701

  4913. msgid "2021-03-20"

  4914. msgstr ""

  4915. 

  4916. #: ../../../CHANGELOG.md:2703

  4917. msgid "Sygnal push gateway support"

  4918. msgstr ""

  4919. 

  4920. #: ../../../CHANGELOG.md:2705

  4921. msgid "The playbook can now install the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you."

  4922. msgstr ""

  4923. 

  4924. #: ../../../CHANGELOG.md:2707

  4925. msgid "This is only useful to people who develop/build their own Matrix client applications."

  4926. msgstr ""

  4927. 

  4928. #: ../../../CHANGELOG.md:2709

  4929. msgid "Additional details are available in our [Setting up the Sygnal push gateway](docs/configuring-playbook-sygnal.md) docs."

  4930. msgstr ""

  4931. 

  4932. #: ../../../CHANGELOG.md:2712

  4933. msgid "2021-03-16"

  4934. msgstr ""

  4935. 

  4936. #: ../../../CHANGELOG.md:2714

  4937. msgid "Go-NEB support"

  4938. msgstr ""

  4939. 

  4940. #: ../../../CHANGELOG.md:2716

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

  4942. msgstr ""

  4943. 

  4944. #: ../../../CHANGELOG.md:2718

  4945. msgid "Additional details are available in [Setting up Go-NEB](docs/configuring-playbook-bot-go-neb.md)."

  4946. msgstr ""

  4947. 

  4948. #: ../../../CHANGELOG.md:2721

  4949. msgid "2021-02-19"

  4950. msgstr ""

  4951. 

  4952. #: ../../../CHANGELOG.md:2723

  4953. msgid "GroupMe bridging support via mx-puppet-groupme"

  4954. msgstr ""

  4955. 

  4956. #: ../../../CHANGELOG.md:2725

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

  4958. msgstr ""

  4959. 

  4960. #: ../../../CHANGELOG.md:2727

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

  4962. msgstr ""

  4963. 

  4964. #: ../../../CHANGELOG.md:2729

  4965. msgid "To get started, follow our [Setting up MX Puppet GroupMe](docs/configuring-playbook-bridge-mx-puppet-groupme.md) docs."

  4966. msgstr ""

  4967. 

  4968. #: ../../../CHANGELOG.md:2731

  4969. msgid "Mautrix Instagram bridging support"

  4970. msgstr ""

  4971. 

  4972. #: ../../../CHANGELOG.md:2733

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

  4974. msgstr ""

  4975. 

  4976. #: ../../../CHANGELOG.md:2735

  4977. msgid "Additional details are available in [Setting up Mautrix Instagram bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)."

  4978. msgstr ""

  4979. 

  4980. #: ../../../CHANGELOG.md:2737

  4981. msgid "Synapse workers support"

  4982. msgstr ""

  4983. 

  4984. #: ../../../CHANGELOG.md:2739

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

  4986. msgstr ""

  4987. 

  4988. #: ../../../CHANGELOG.md:2741

  4989. msgid "Having support for workers makes the playbook suitable for larger homeserver deployments."

  4990. msgstr ""

  4991. 

  4992. #: ../../../CHANGELOG.md:2743

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

  4994. msgstr ""

  4995. 

  4996. #: ../../../CHANGELOG.md:2745

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

  4998. msgstr ""

  4999. 

  5000. #: ../../../CHANGELOG.md:2747

  5001. msgid "To enable Synapse workers, follow our [Load balancing with workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) documentation."

  5002. msgstr ""

  5003. 

  5004. #: ../../../CHANGELOG.md:2750

  5005. msgid "2021-02-12"

  5006. msgstr ""

  5007. 

  5008. #: ../../../CHANGELOG.md:2752

  5009. msgid "(Potential Breaking Change) Monitoring/metrics support using Prometheus and Grafana"

  5010. msgstr ""

  5011. 

  5012. #: ../../../CHANGELOG.md:2754

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

  5014. msgstr ""

  5015. 

  5016. #: ../../../CHANGELOG.md:2756

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

  5018. msgstr ""

  5019. 

  5020. #: ../../../CHANGELOG.md:2758

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

  5022. msgstr ""

  5023. 

  5024. #: ../../../CHANGELOG.md:2761

  5025. msgid "2021-01-31"

  5026. msgstr ""

  5027. 

  5028. #: ../../../CHANGELOG.md:2763

  5029. msgid "Etherpad support"

  5030. msgstr ""

  5031. 

  5032. #: ../../../CHANGELOG.md:2765

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

  5034. msgstr ""

  5035. 

  5036. #: ../../../CHANGELOG.md:2767

  5037. msgid "To get it installed, follow [our Etherpad docs page](docs/configuring-playbook-etherpad.md)."

  5038. msgstr ""

  5039. 

  5040. #: ../../../CHANGELOG.md:2770

  5041. msgid "2021-01-22"

  5042. msgstr ""

  5043. 

  5044. #: ../../../CHANGELOG.md:2772

  5045. msgid "(Breaking Change) Postgres changes that require manual intervention"

  5046. msgstr ""

  5047. 

  5048. #: ../../../CHANGELOG.md:2774

  5049. msgid "We've made a lot of changes to our Postgres setup and some manual action is required (described below). Sorry about the hassle."

  5050. msgstr ""

  5051. 

  5052. #: ../../../CHANGELOG.md:2776

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

  5054. msgstr ""

  5055. 

  5056. #: ../../../CHANGELOG.md:2778

  5057. msgid "Why?"

  5058. msgstr ""

  5059. 

  5060. #: ../../../CHANGELOG.md:2780

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

  5062. msgstr ""

  5063. 

  5064. #: ../../../CHANGELOG.md:2781

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

  5066. msgstr ""

  5067. 

  5068. #: ../../../CHANGELOG.md:2782

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

  5070. msgstr ""

  5071. 

  5072. #: ../../../CHANGELOG.md:2783

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

  5074. msgstr ""

  5075. 

  5076. #: ../../../CHANGELOG.md:2784

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

  5078. msgstr ""

  5079. 

  5080. #: ../../../CHANGELOG.md:2785

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

  5082. msgstr ""

  5083. 

  5084. #: ../../../CHANGELOG.md:2787

  5085. msgid "So, this is some **effort to improve security** and to **prepare for a brighter future of having more homeserver options** than just Synapse."

  5086. msgstr ""

  5087. 

  5088. #: ../../../CHANGELOG.md:2789

  5089. msgid "What has really changed?"

  5090. msgstr ""

  5091. 

  5092. #: ../../../CHANGELOG.md:2791

  5093. msgid "the default superuser Postgres username is now `matrix` (used to be `synapse`)"

  5094. msgstr ""

  5095. 

  5096. #: ../../../CHANGELOG.md:2792

  5097. msgid "the default Postgres database is now `matrix` (used to be `homeserver`)"

  5098. msgstr ""

  5099. 

  5100. #: ../../../CHANGELOG.md:2793

  5101. msgid "Synapse's database is now `synapse` (used to be `homeserver`). This is now just another \"additional database\" that the playbook manages for you"

  5102. msgstr ""

  5103. 

  5104. #: ../../../CHANGELOG.md:2794

  5105. msgid "Synapse's user called `synapse` is just a regular user that can only use the `synapse` database (not a superuser anymore)"

  5106. msgstr ""

  5107. 

  5108. #: ../../../CHANGELOG.md:2796

  5109. msgid "What do I do if I'm using the integrated Postgres server (default)?"

  5110. msgstr ""

  5111. 

  5112. #: ../../../CHANGELOG.md:2798

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

  5114. msgstr ""

  5115. 

  5116. #: ../../../CHANGELOG.md:2800

  5117. msgid "To migrate to the new setup, expect a few minutes of downtime, while you follow these steps:"

  5118. msgstr ""

  5119. 

  5120. #: ../../../CHANGELOG.md:2802

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

  5122. msgstr ""

  5123. 

  5124. #: ../../../CHANGELOG.md:2804

  5125. 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!"

  5126. msgstr ""

  5127. 

  5128. #: ../../../CHANGELOG.md:2806

  5129. msgid "Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` file, adding a line like this:"

  5130. msgstr ""

  5131. 

  5132. #: ../../../CHANGELOG.md:2811

  5133. #: ../../../CHANGELOG.md:2823

  5134. msgid "… where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2."

  5135. msgstr ""

  5136. 

  5137. #: ../../../CHANGELOG.md:2813

  5138. msgid "Stop all services: `ansible-playbook -i inventory/hosts setup.yml --tags=stop`"

  5139. msgstr ""

  5140. 

  5141. #: ../../../CHANGELOG.md:2814

  5142. msgid "Log in to the server via SSH. The next commands will be performed there."

  5143. msgstr ""

  5144. 

  5145. #: ../../../CHANGELOG.md:2815

  5146. msgid "Start the Postgres database server: `systemctl start matrix-postgres`"

  5147. msgstr ""

  5148. 

  5149. #: ../../../CHANGELOG.md:2816

  5150. msgid "Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`"

  5151. msgstr ""

  5152. 

  5153. #: ../../../CHANGELOG.md:2817

  5154. msgid "Execute the following query, while making sure to **change the password inside** (**don't forget the ending `;`**):"

  5155. msgstr ""

  5156. 

  5157. #: ../../../CHANGELOG.md:2825

  5158. msgid "Execute the following queries as you see them (no modifications necessary, so you can just **paste them all at once**):"

  5159. msgstr ""

  5160. 

  5161. #: ../../../CHANGELOG.md:2843

  5162. msgid "You may need to press *Enter* after pasting the lines above."

  5163. msgstr ""

  5164. 

  5165. #: ../../../CHANGELOG.md:2845

  5166. msgid "Re-run the playbook normally: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`"

  5167. msgstr ""

  5168. 

  5169. #: ../../../CHANGELOG.md:2847

  5170. msgid "What do I do if I'm using an external Postgres server?"

  5171. msgstr ""

  5172. 

  5173. #: ../../../CHANGELOG.md:2849

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

  5175. msgstr ""

  5176. 

  5177. #: ../../../CHANGELOG.md:2851

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

  5179. msgstr ""

  5180. 

  5181. #: ../../../CHANGELOG.md:2854

  5182. msgid "2021-01-20"

  5183. msgstr ""

  5184. 

  5185. #: ../../../CHANGELOG.md:2856

  5186. msgid "(Breaking Change) The mautrix-facebook bridge now requires a Postgres database"

  5187. msgstr ""

  5188. 

  5189. #: ../../../CHANGELOG.md:2858

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

  5191. msgstr ""

  5192. 

  5193. #: ../../../CHANGELOG.md:2860

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

  5195. msgstr ""

  5196. 

  5197. #: ../../../CHANGELOG.md:2862

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

  5199. msgstr ""

  5200. 

  5201. #: ../../../CHANGELOG.md:2864

  5202. msgid "Whether this change requires your intervention depends mostly on:"

  5203. msgstr ""

  5204. 

  5205. #: ../../../CHANGELOG.md:2865

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

  5207. msgstr ""

  5208. 

  5209. #: ../../../CHANGELOG.md:2866

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

  5211. msgstr ""

  5212. 

  5213. #: ../../../CHANGELOG.md:2868

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

  5215. msgstr ""

  5216. 

  5217. #: ../../../CHANGELOG.md:2870

  5218. msgid "Upgrade path for people NOT running an external Postgres server (default for the playbook)"

  5219. msgstr ""

  5220. 

  5221. #: ../../../CHANGELOG.md:2872

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

  5223. msgstr ""

  5224. 

  5225. #: ../../../CHANGELOG.md:2874

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

  5227. msgstr ""

  5228. 

  5229. #: ../../../CHANGELOG.md:2876

  5230. msgid "Alternatively, [you can stay on SQLite for a little longer](#staying-on-sqlite-for-a-little-longer-temporary-solution)."

  5231. msgstr ""

  5232. 

  5233. #: ../../../CHANGELOG.md:2878

  5234. msgid "Upgrade path for people running an external Postgres server"

  5235. msgstr ""

  5236. 

  5237. #: ../../../CHANGELOG.md:2880

  5238. msgid "For people using the internal Postgres server (the default for the playbook):"

  5239. msgstr ""

  5240. 

  5241. #: ../../../CHANGELOG.md:2881

  5242. msgid "we automatically create an additional `matrix_mautrix_facebook` Postgres database and credentials to access it"

  5243. msgstr ""

  5244. 

  5245. #: ../../../CHANGELOG.md:2882

  5246. msgid "we automatically adjust the bridge's `matrix_mautrix_facebook_database_*` variables to point the bridge to that Postgres database"

  5247. msgstr ""

  5248. 

  5249. #: ../../../CHANGELOG.md:2883

  5250. msgid "we use [pgloader](https://pgloader.io/) to automatically import the existing SQLite data for the bridge into the `matrix_mautrix_facebook` Postgres database"

  5251. msgstr ""

  5252. 

  5253. #: ../../../CHANGELOG.md:2885

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

  5255. msgstr ""

  5256. 

  5257. #: ../../../CHANGELOG.md:2887

  5258. msgid "You have 3 ways to proceed:"

  5259. msgstr ""

  5260. 

  5261. #: ../../../CHANGELOG.md:2889

  5262. msgid "contribute to the playbook to make this possible (difficult)"

  5263. msgstr ""

  5264. 

  5265. #: ../../../CHANGELOG.md:2890

  5266. msgid "or, do the migration \"steps\" manually:"

  5267. msgstr ""

  5268. 

  5269. #: ../../../CHANGELOG.md:2891

  5270. msgid "stop the bridge (`systemctl stop matrix-mautrix-facebook`)"

  5271. msgstr ""

  5272. 

  5273. #: ../../../CHANGELOG.md:2892

  5274. msgid "create a new `matrix_mautrix_facebook` Postgres database for it"

  5275. msgstr ""

  5276. 

  5277. #: ../../../CHANGELOG.md:2893

  5278. msgid "run [pgloader](https://pgloader.io/) manually (we import this bridge's data using default settings and it works well)"

  5279. msgstr ""

  5280. 

  5281. #: ../../../CHANGELOG.md:2894

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

  5283. msgstr ""

  5284. 

  5285. #: ../../../CHANGELOG.md:2895

  5286. msgid "switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: 'postgres'` in your `vars.yml` file)"

  5287. msgstr ""

  5288. 

  5289. #: ../../../CHANGELOG.md:2896

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

  5291. msgstr ""

  5292. 

  5293. #: ../../../CHANGELOG.md:2897

  5294. msgid "send a `login` message to the Facebook bridge bot again"

  5295. msgstr ""

  5296. 

  5297. #: ../../../CHANGELOG.md:2898

  5298. msgid "or, [stay on SQLite for a little longer (temporary solution)](#staying-on-sqlite-for-a-little-longer-temporary-solution)"

  5299. msgstr ""

  5300. 

  5301. #: ../../../CHANGELOG.md:2900

  5302. msgid "Staying on SQLite for a little longer (temporary solution)"

  5303. msgstr ""

  5304. 

  5305. #: ../../../CHANGELOG.md:2902

  5306. msgid "To keep using this bridge with SQLite for a little longer (**not recommended**), use the following configuration in your `vars.yml` file:"

  5307. msgstr ""

  5308. 

  5309. #: ../../../CHANGELOG.md:2912

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

  5311. msgstr ""

  5312. 

  5313. #: ../../../CHANGELOG.md:2915

  5314. msgid "2021-01-17"

  5315. msgstr ""

  5316. 

  5317. #: ../../../CHANGELOG.md:2917

  5318. msgid "matrix-corporal goes 2.0"

  5319. msgstr ""

  5320. 

  5321. #: ../../../CHANGELOG.md:2919

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

  5323. msgstr ""

  5324. 

  5325. #: ../../../CHANGELOG.md:2921

  5326. msgid "No manual intervention is required in the common case."

  5327. msgstr ""

  5328. 

  5329. #: ../../../CHANGELOG.md:2923

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

  5331. msgstr ""

  5332. 

  5333. #: ../../../CHANGELOG.md:2926

  5334. msgid "2021-01-14"

  5335. msgstr ""

  5336. 

  5337. #: ../../../CHANGELOG.md:2928

  5338. msgid "Moving from cronjobs to systemd timers"

  5339. msgstr ""

  5340. 

  5341. #: ../../../CHANGELOG.md:2930

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

  5343. msgstr ""

  5344. 

  5345. #: ../../../CHANGELOG.md:2932

  5346. msgid "The largest benefit of this is that we no longer require you to install a cron daemon, thus simplifying our install procedure."

  5347. msgstr ""

  5348. 

  5349. #: ../../../CHANGELOG.md:2934

  5350. msgid "The playbook will migrate you from cronjobs to systemd timers automatically. This is just a heads up."

  5351. msgstr ""

  5352. 

  5353. #: ../../../CHANGELOG.md:2937

  5354. msgid "2021-01-08"

  5355. msgstr ""

  5356. 

  5357. #: ../../../CHANGELOG.md:2939

  5358. msgid "(Breaking Change) New SSL configuration"

  5359. msgstr ""

  5360. 

  5361. #: ../../../CHANGELOG.md:2941

  5362. msgid "SSL configuration (protocols, ciphers) can now be more easily controlled thanks to us making use of configuration presets."

  5363. msgstr ""

  5364. 

  5365. #: ../../../CHANGELOG.md:2943

  5366. msgid "We define a few presets (old, intermediate, modern), following the [Mozilla SSL Configuration Generator](https://ssl-config.mozilla.org/#server=nginx)."

  5367. msgstr ""

  5368. 

  5369. #: ../../../CHANGELOG.md:2945

  5370. msgid "A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is used (defaults to `\"intermediate\"`)."

  5371. msgstr ""

  5372. 

  5373. #: ../../../CHANGELOG.md:2947

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

  5375. msgstr ""

  5376. 

  5377. #: ../../../CHANGELOG.md:2949

  5378. msgid "To revert to the old behaviour, set the following variables:"

  5379. msgstr ""

  5380. 

  5381. #: ../../../CHANGELOG.md:2956

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

  5383. msgstr ""

  5384. 

  5385. #: ../../../CHANGELOG.md:2959

  5386. msgid "2021-01-03"

  5387. msgstr ""

  5388. 

  5389. #: ../../../CHANGELOG.md:2961

  5390. msgid "Signal bridging support via mautrix-signal"

  5391. msgstr ""

  5392. 

  5393. #: ../../../CHANGELOG.md:2963

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

  5395. msgstr ""

  5396. 

  5397. #: ../../../CHANGELOG.md:2965

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

  5399. msgstr ""

  5400. 

  5401. #: ../../../CHANGELOG.md:2968

  5402. msgid "2020-12-23"

  5403. msgstr ""

  5404. 

  5405. #: ../../../CHANGELOG.md:2970

  5406. msgid "The big move to all-on-Postgres (potentially dangerous)"

  5407. msgstr ""

  5408. 

  5409. #: ../../../CHANGELOG.md:2972

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

  5411. msgstr ""

  5412. 

  5413. #: ../../../CHANGELOG.md:2974

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

  5415. msgstr ""

  5416. 

  5417. #: ../../../CHANGELOG.md:2976

  5418. 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!"

  5419. msgstr ""

  5420. 

  5421. #: ../../../CHANGELOG.md:2978

  5422. msgid "Moving all services to Postgres brings a few **benefits** to us:"

  5423. msgstr ""

  5424. 

  5425. #: ../../../CHANGELOG.md:2980

  5426. msgid "**improved performance**"

  5427. msgstr ""

  5428. 

  5429. #: ../../../CHANGELOG.md:2981

  5430. msgid "**improved compatibility**. Most bridges are deprecating SQLite/nedb support or offer less features when not on Postgres."

  5431. msgstr ""

  5432. 

  5433. #: ../../../CHANGELOG.md:2982

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

  5435. msgstr ""

  5436. 

  5437. #: ../../../CHANGELOG.md:2983

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

  5439. msgstr ""

  5440. 

  5441. #: ../../../CHANGELOG.md:2985

  5442. msgid "Key takeway"

  5443. msgstr ""

  5444. 

  5445. #: ../../../CHANGELOG.md:2987

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

  5447. msgstr ""

  5448. 

  5449. #: ../../../CHANGELOG.md:2989

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

  5451. msgstr ""

  5452. 

  5453. #: ../../../CHANGELOG.md:2991

  5454. msgid "Opting-out of the Postgres migration"

  5455. msgstr ""

  5456. 

  5457. #: ../../../CHANGELOG.md:2993

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

  5459. msgstr ""

  5460. 

  5461. #: ../../../CHANGELOG.md:2995

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

  5463. msgstr ""

  5464. 

  5465. #: ../../../CHANGELOG.md:2997

  5466. msgid "Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them."

  5467. msgstr ""

  5468. 

  5469. #: ../../../CHANGELOG.md:2999

  5470. msgid "Going back to SQLite/nedb if things went wrong"

  5471. msgstr ""

  5472. 

  5473. #: ../../../CHANGELOG.md:3001

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

  5475. msgstr ""

  5476. 

  5477. #: ../../../CHANGELOG.md:3003

  5478. msgid "stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"

  5479. msgstr ""

  5480. 

  5481. #: ../../../CHANGELOG.md:3004

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

  5483. msgstr ""

  5484. 

  5485. #: ../../../CHANGELOG.md:3005

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

  5487. msgstr ""

  5488. 

  5489. #: ../../../CHANGELOG.md:3006

  5490. msgid "re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`)"

  5491. msgstr ""

  5492. 

  5493. #: ../../../CHANGELOG.md:3007

  5494. msgid "[get in touch](README.md#support) with us"

  5495. msgstr ""

  5496. 

  5497. #: ../../../CHANGELOG.md:3009

  5498. msgid "2020-12-11"

  5499. msgstr ""

  5500. 

  5501. #: ../../../CHANGELOG.md:3011

  5502. msgid "synapse-janitor support removed"

  5503. msgstr ""

  5504. 

  5505. #: ../../../CHANGELOG.md:3013

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

  5507. msgstr ""

  5508. 

  5509. #: ../../../CHANGELOG.md:3015

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

  5511. msgstr ""

  5512. 

  5513. #: ../../../CHANGELOG.md:3017

  5514. msgid "Docker 20.10 is here"

  5515. msgstr ""

  5516. 

  5517. #: ../../../CHANGELOG.md:3019

  5518. msgid "(No need to do anything special in relation to this. Just something to keep in mind)"

  5519. msgstr ""

  5520. 

  5521. #: ../../../CHANGELOG.md:3021

  5522. msgid "Docker 20.10 got released recently and your server will likely get it the next time you update."

  5523. msgstr ""

  5524. 

  5525. #: ../../../CHANGELOG.md:3023

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

  5527. msgstr ""

  5528. 

  5529. #: ../../../CHANGELOG.md:3026

  5530. msgid "2020-12-08"

  5531. msgstr ""

  5532. 

  5533. #: ../../../CHANGELOG.md:3028

  5534. msgid "openid APIs exposed by default on the federation port when federation disabled"

  5535. msgstr ""

  5536. 

  5537. #: ../../../CHANGELOG.md:3030

  5538. msgid "We've changed some defaults. People running with our default configuration (federation enabled), are not affected at all."

  5539. msgstr ""

  5540. 

  5541. #: ../../../CHANGELOG.md:3032

  5542. msgid "If you are running an unfederated server (`matrix_synapse_federation_enabled: false`), this may be of interest to you."

  5543. msgstr ""

  5544. 

  5545. #: ../../../CHANGELOG.md:3034

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

  5547. msgstr ""

  5548. 

  5549. #: ../../../CHANGELOG.md:3037

  5550. msgid "2020-11-27"

  5551. msgstr ""

  5552. 

  5553. #: ../../../CHANGELOG.md:3039

  5554. msgid "Recent Jitsi updates may require configuration changes"

  5555. msgstr ""

  5556. 

  5557. #: ../../../CHANGELOG.md:3041

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

  5559. msgstr ""

  5560. 

  5561. #: ../../../CHANGELOG.md:3043

  5562. msgid "**If you use our default Jitsi settings, you won't have to do anything.**"

  5563. msgstr ""

  5564. 

  5565. #: ../../../CHANGELOG.md:3045

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

  5567. msgstr ""

  5568. 

  5569. #: ../../../CHANGELOG.md:3047

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

  5571. msgstr ""

  5572. 

  5573. #: ../../../CHANGELOG.md:3049

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

  5575. msgstr ""

  5576. 

  5577. #: ../../../CHANGELOG.md:3052

  5578. msgid "2020-11-23"

  5579. msgstr ""

  5580. 

  5581. #: ../../../CHANGELOG.md:3054

  5582. #: ../../../CHANGELOG.md:3062

  5583. msgid "Breaking change matrix-sms-bridge"

  5584. msgstr ""

  5585. 

  5586. #: ../../../CHANGELOG.md:3056

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

  5588. msgstr ""

  5589. 

  5590. #: ../../../CHANGELOG.md:3058

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

  5592. msgstr ""

  5593. 

  5594. #: ../../../CHANGELOG.md:3060

  5595. msgid "2020-11-13"

  5596. msgstr ""

  5597. 

  5598. #: ../../../CHANGELOG.md:3064

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

  5600. msgstr ""

  5601. 

  5602. #: ../../../CHANGELOG.md:3066

  5603. msgid "Add the following to your `vars.yml` file: `matrix_sms_bridge_container_extra_arguments=['--env SPRING_PROFILES_ACTIVE=initialsync']`"

  5604. msgstr ""

  5605. 

  5606. #: ../../../CHANGELOG.md:3067

  5607. msgid "Login to your host shell and remove old systemd file from your host: `rm /etc/systemd/system/matrix-sms-bridge-database.service`"

  5608. msgstr ""

  5609. 

  5610. #: ../../../CHANGELOG.md:3068

  5611. msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-sms-bridge,start`"

  5612. msgstr ""

  5613. 

  5614. #: ../../../CHANGELOG.md:3069

  5615. msgid "Login to your host shell and check the logs with `journalctl -u matrix-sms-bridge` until the sync finished."

  5616. msgstr ""

  5617. 

  5618. #: ../../../CHANGELOG.md:3070

  5619. msgid "Remove the var from the first step."

  5620. msgstr ""

  5621. 

  5622. #: ../../../CHANGELOG.md:3071

  5623. msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`."

  5624. msgstr ""

  5625. 

  5626. #: ../../../CHANGELOG.md:3073

  5627. msgid "2020-11-10"

  5628. msgstr ""

  5629. 

  5630. #: ../../../CHANGELOG.md:3075

  5631. msgid "Dynamic DNS support"

  5632. msgstr ""

  5633. 

  5634. #: ../../../CHANGELOG.md:3077

  5635. msgid "Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook can now manage Dynamic DNS for you using [ddclient](https://ddclient.net/)."

  5636. msgstr ""

  5637. 

  5638. #: ../../../CHANGELOG.md:3079

  5639. msgid "To learn more, follow our [Dynamic DNS docs page](docs/configuring-playbook-dynamic-dns.md)."

  5640. msgstr ""

  5641. 

  5642. #: ../../../CHANGELOG.md:3082

  5643. msgid "2020-10-28"

  5644. msgstr ""

  5645. 

  5646. #: ../../../CHANGELOG.md:3084

  5647. msgid "(Compatibility Break) https://matrix.example.com/ now redirects to https://element.example.com/"

  5648. msgstr ""

  5649. 

  5650. #: ../../../CHANGELOG.md:3086

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

  5652. msgstr ""

  5653. 

  5654. #: ../../../CHANGELOG.md:3088

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

  5656. msgstr ""

  5657. 

  5658. #: ../../../CHANGELOG.md:3090

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

  5660. msgstr ""

  5661. 

  5662. #: ../../../CHANGELOG.md:3092

  5663. 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: \"\"`)."

  5664. msgstr ""

  5665. 

  5666. #: ../../../CHANGELOG.md:3095

  5667. msgid "2020-10-26"

  5668. msgstr ""

  5669. 

  5670. #: ../../../CHANGELOG.md:3097

  5671. msgid "(Compatibility Break) /_synapse/admin is no longer publicly exposed by default"

  5672. msgstr ""

  5673. 

  5674. #: ../../../CHANGELOG.md:3099

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

  5676. msgstr ""

  5677. 

  5678. #: ../../../CHANGELOG.md:3101

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

  5680. msgstr ""

  5681. 

  5682. #: ../../../CHANGELOG.md:3103

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

  5684. msgstr ""

  5685. 

  5686. #: ../../../CHANGELOG.md:3110

  5687. msgid "2020-10-02"

  5688. msgstr ""

  5689. 

  5690. #: ../../../CHANGELOG.md:3112

  5691. msgid "Minimum Ansible version raised to v2.7.0"

  5692. msgstr ""

  5693. 

  5694. #: ../../../CHANGELOG.md:3114

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

  5696. msgstr ""

  5697. 

  5698. #: ../../../CHANGELOG.md:3116

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

  5700. msgstr ""

  5701. 

  5702. #: ../../../CHANGELOG.md:3118

  5703. msgid "Our [Ansible docs page](docs/ansible.md) contains information on how to run a more up-to-date version of Ansible."

  5704. msgstr ""

  5705. 

  5706. #: ../../../CHANGELOG.md:3121

  5707. msgid "2020-10-01"

  5708. msgstr ""

  5709. 

  5710. #: ../../../CHANGELOG.md:3123

  5711. msgid "Postgres 13 support"

  5712. msgstr ""

  5713. 

  5714. #: ../../../CHANGELOG.md:3125

  5715. msgid "The playbook now installs [Postgres 13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) by default."

  5716. msgstr ""

  5717. 

  5718. #: ../../../CHANGELOG.md:3127

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

  5720. msgstr ""

  5721. 

  5722. #: ../../../CHANGELOG.md:3129

  5723. msgid "2020-09-01"

  5724. msgstr ""

  5725. 

  5726. #: ../../../CHANGELOG.md:3131

  5727. msgid "matrix-registration support"

  5728. msgstr ""

  5729. 

  5730. #: ../../../CHANGELOG.md:3133

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

  5732. msgstr ""

  5733. 

  5734. #: ../../../CHANGELOG.md:3135

  5735. msgid "See our [Setting up matrix-registration](docs/configuring-playbook-matrix-registration.md) documentation page to get started."

  5736. msgstr ""

  5737. 

  5738. #: ../../../CHANGELOG.md:3138

  5739. msgid "2020-08-21"

  5740. msgstr ""

  5741. 

  5742. #: ../../../CHANGELOG.md:3140

  5743. msgid "rust-synapse-compress-state support"

  5744. msgstr ""

  5745. 

  5746. #: ../../../CHANGELOG.md:3142

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

  5748. msgstr ""

  5749. 

  5750. #: ../../../CHANGELOG.md:3144

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

  5752. msgstr ""

  5753. 

  5754. #: ../../../CHANGELOG.md:3147

  5755. msgid "2020-07-22"

  5756. msgstr ""

  5757. 

  5758. #: ../../../CHANGELOG.md:3149

  5759. msgid "Synapse Admin support"

  5760. msgstr ""

  5761. 

  5762. #: ../../../CHANGELOG.md:3151

  5763. msgid "The playbook can now help you set up [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin)."

  5764. msgstr ""

  5765. 

  5766. #: ../../../CHANGELOG.md:3153

  5767. msgid "See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-admin.md) documentation to get started."

  5768. msgstr ""

  5769. 

  5770. #: ../../../CHANGELOG.md:3156

  5771. msgid "2020-07-20"

  5772. msgstr ""

  5773. 

  5774. #: ../../../CHANGELOG.md:3158

  5775. msgid "matrix-reminder-bot support"

  5776. msgstr ""

  5777. 

  5778. #: ../../../CHANGELOG.md:3160

  5779. msgid "The playbook can now help you set up [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)."

  5780. msgstr ""

  5781. 

  5782. #: ../../../CHANGELOG.md:3162

  5783. msgid "See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-matrix-reminder-bot.md) documentation to get started."

  5784. msgstr ""

  5785. 

  5786. #: ../../../CHANGELOG.md:3165

  5787. msgid "2020-07-17"

  5788. msgstr ""

  5789. 

  5790. #: ../../../CHANGELOG.md:3167

  5791. msgid "(Compatibility Break) Riot is now Element"

  5792. msgstr ""

  5793. 

  5794. #: ../../../CHANGELOG.md:3169

  5795. msgid "As per the official announcement, [Riot has been rebraned to Element](https://element.io/blog/welcome-to-element/)."

  5796. msgstr ""

  5797. 

  5798. #: ../../../CHANGELOG.md:3171

  5799. msgid "The playbook follows suit. Existing installations have a few options for how to handle this."

  5800. msgstr ""

  5801. 

  5802. #: ../../../CHANGELOG.md:3173

  5803. msgid "See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md#migrating-to-element) documentation page for more details."

  5804. msgstr ""

  5805. 

  5806. #: ../../../CHANGELOG.md:3176

  5807. msgid "2020-07-03"

  5808. msgstr ""

  5809. 

  5810. #: ../../../CHANGELOG.md:3178

  5811. msgid "Steam bridging support via mx-puppet-steam"

  5812. msgstr ""

  5813. 

  5814. #: ../../../CHANGELOG.md:3180

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

  5816. msgstr ""

  5817. 

  5818. #: ../../../CHANGELOG.md:3183

  5819. msgid "2020-07-01"

  5820. msgstr ""

  5821. 

  5822. #: ../../../CHANGELOG.md:3185

  5823. msgid "Discord bridging support via mx-puppet-discord"

  5824. msgstr ""

  5825. 

  5826. #: ../../../CHANGELOG.md:3187

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

  5828. msgstr ""

  5829. 

  5830. #: ../../../CHANGELOG.md:3189

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

  5832. msgstr ""

  5833. 

  5834. #: ../../../CHANGELOG.md:3192

  5835. msgid "2020-06-30"

  5836. msgstr ""

  5837. 

  5838. #: ../../../CHANGELOG.md:3194

  5839. msgid "Instagram and Twitter bridging support"

  5840. msgstr ""

  5841. 

  5842. #: ../../../CHANGELOG.md:3196

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

  5844. msgstr ""

  5845. 

  5846. #: ../../../CHANGELOG.md:3198

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

  5848. msgstr ""

  5849. 

  5850. #: ../../../CHANGELOG.md:3201

  5851. msgid "2020-06-28"

  5852. msgstr ""

  5853. 

  5854. #: ../../../CHANGELOG.md:3203

  5855. msgid "(Post Mortem / fixed Security Issue) Re-enabling User Directory search powered by the ma1sd Identity Server"

  5856. msgstr ""

  5857. 

  5858. #: ../../../CHANGELOG.md:3205

  5859. #: ../../../CHANGELOG.md:3234

  5860. msgid "User Directory search requests used to go to the ma1sd identity server by default, which queried its own stores and the Synapse database."

  5861. msgstr ""

  5862. 

  5863. #: ../../../CHANGELOG.md:3207

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

  5865. msgstr ""

  5866. 

  5867. #: ../../../CHANGELOG.md:3209

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

  5869. msgstr ""

  5870. 

  5871. #: ../../../CHANGELOG.md:3211

  5872. msgid "As always, re-running the playbook is enough to get the updated bits."

  5873. msgstr ""

  5874. 

  5875. #: ../../../CHANGELOG.md:3213

  5876. msgid "2020-06-11"

  5877. msgstr ""

  5878. 

  5879. #: ../../../CHANGELOG.md:3215

  5880. msgid "SMS bridging requires db reset"

  5881. msgstr ""

  5882. 

  5883. #: ../../../CHANGELOG.md:3217

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

  5885. msgstr ""

  5886. 

  5887. #: ../../../CHANGELOG.md:3219

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

  5889. msgstr ""

  5890. 

  5891. #: ../../../CHANGELOG.md:3221

  5892. msgid "2020-06-05"

  5893. msgstr ""

  5894. 

  5895. #: ../../../CHANGELOG.md:3223

  5896. msgid "SMS bridging support"

  5897. msgstr ""

  5898. 

  5899. #: ../../../CHANGELOG.md:3225

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

  5901. msgstr ""

  5902. 

  5903. #: ../../../CHANGELOG.md:3227

  5904. msgid "See our [Setting up Matrix SMS bridging](docs/configuring-playbook-bridge-matrix-bridge-sms.md) documentation page for getting started."

  5905. msgstr ""

  5906. 

  5907. #: ../../../CHANGELOG.md:3230

  5908. msgid "2020-05-19"

  5909. msgstr ""

  5910. 

  5911. #: ../../../CHANGELOG.md:3232

  5912. msgid "(Compatibility Break / Security Issue) Disabling User Directory search powered by the ma1sd Identity Server"

  5913. msgstr ""

  5914. 

  5915. #: ../../../CHANGELOG.md:3236

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

  5917. msgstr ""

  5918. 

  5919. #: ../../../CHANGELOG.md:3238

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

  5921. msgstr ""

  5922. 

  5923. #: ../../../CHANGELOG.md:3240

  5924. 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 }}\"`"

  5925. msgstr ""

  5926. 

  5927. #: ../../../CHANGELOG.md:3243

  5928. msgid "2020-04-28"

  5929. msgstr ""

  5930. 

  5931. #: ../../../CHANGELOG.md:3245

  5932. msgid "Newer IRC bridge (with potential breaking change)"

  5933. msgstr ""

  5934. 

  5935. #: ../../../CHANGELOG.md:3247

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

  5937. msgstr ""

  5938. 

  5939. #: ../../../CHANGELOG.md:3256

  5940. msgid "2020-04-23"

  5941. msgstr ""

  5942. 

  5943. #: ../../../CHANGELOG.md:3258

  5944. #: ../../../CHANGELOG.md:3489

  5945. msgid "Slack bridging support"

  5946. msgstr ""

  5947. 

  5948. #: ../../../CHANGELOG.md:3260

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

  5950. msgstr ""

  5951. 

  5952. #: ../../../CHANGELOG.md:3262

  5953. msgid "See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-bridge-mx-puppet-slack.md) documentation page for getting started."

  5954. msgstr ""

  5955. 

  5956. #: ../../../CHANGELOG.md:3265

  5957. msgid "2020-04-09"

  5958. msgstr ""

  5959. 

  5960. #: ../../../CHANGELOG.md:3267

  5961. msgid "Skype bridging support"

  5962. msgstr ""

  5963. 

  5964. #: ../../../CHANGELOG.md:3269

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

  5966. msgstr ""

  5967. 

  5968. #: ../../../CHANGELOG.md:3271

  5969. msgid "See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md) documentation page for getting started."

  5970. msgstr ""

  5971. 

  5972. #: ../../../CHANGELOG.md:3274

  5973. msgid "2020-04-05"

  5974. msgstr ""

  5975. 

  5976. #: ../../../CHANGELOG.md:3276

  5977. msgid "Private Jitsi support"

  5978. msgstr ""

  5979. 

  5980. #: ../../../CHANGELOG.md:3278

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

  5982. msgstr ""

  5983. 

  5984. #: ../../../CHANGELOG.md:3280

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

  5986. msgstr ""

  5987. 

  5988. #: ../../../CHANGELOG.md:3282

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

  5990. msgstr ""

  5991. 

  5992. #: ../../../CHANGELOG.md:3285

  5993. msgid "2020-04-03"

  5994. msgstr ""

  5995. 

  5996. #: ../../../CHANGELOG.md:3287

  5997. msgid "(Potential Backward Compatibility Break) ma1sd replaces mxisd"

  5998. msgstr ""

  5999. 

  6000. #: ../../../CHANGELOG.md:3289

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

  6002. msgstr ""

  6003. 

  6004. #: ../../../CHANGELOG.md:3291

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

  6006. msgstr ""

  6007. 

  6008. #: ../../../CHANGELOG.md:3293

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

  6010. msgstr ""

  6011. 

  6012. #: ../../../CHANGELOG.md:3296

  6013. msgid "2020-03-29"

  6014. msgstr ""

  6015. 

  6016. #: ../../../CHANGELOG.md:3298

  6017. msgid "Archlinux support"

  6018. msgstr ""

  6019. 

  6020. #: ../../../CHANGELOG.md:3300

  6021. msgid "Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts, the playbook now supports installing to an [Archlinux](https://www.archlinux.org/) server."

  6022. msgstr ""

  6023. 

  6024. #: ../../../CHANGELOG.md:3303

  6025. msgid "2020-03-24"

  6026. msgstr ""

  6027. 

  6028. #: ../../../CHANGELOG.md:3305

  6029. msgid "Jitsi support"

  6030. msgstr ""

  6031. 

  6032. #: ../../../CHANGELOG.md:3307

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

  6034. msgstr ""

  6035. 

  6036. #: ../../../CHANGELOG.md:3309

  6037. msgid "See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to get started."

  6038. msgstr ""

  6039. 

  6040. #: ../../../CHANGELOG.md:3312

  6041. msgid "2020-03-15"

  6042. msgstr ""

  6043. 

  6044. #: ../../../CHANGELOG.md:3314

  6045. msgid "Raspberry Pi support"

  6046. msgstr ""

  6047. 

  6048. #: ../../../CHANGELOG.md:3316

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

  6050. msgstr ""

  6051. 

  6052. #: ../../../CHANGELOG.md:3318

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

  6054. msgstr ""

  6055. 

  6056. #: ../../../CHANGELOG.md:3321

  6057. msgid "2020-02-26"

  6058. msgstr ""

  6059. 

  6060. #: ../../../CHANGELOG.md:3323

  6061. msgid "Riot-web themes are here"

  6062. msgstr ""

  6063. 

  6064. #: ../../../CHANGELOG.md:3325

  6065. msgid "The playbook now makes it easy to install custom riot-web themes."

  6066. msgstr ""

  6067. 

  6068. #: ../../../CHANGELOG.md:3327

  6069. msgid "To learn more, take a look at our [riot-web documentation on Themes](docs/configuring-playbook-riot-web.md#themes)."

  6070. msgstr ""

  6071. 

  6072. #: ../../../CHANGELOG.md:3330

  6073. msgid "2020-02-24"

  6074. msgstr ""

  6075. 

  6076. #: ../../../CHANGELOG.md:3332

  6077. msgid "Customize the server name in Riot's login page"

  6078. msgstr ""

  6079. 

  6080. #: ../../../CHANGELOG.md:3334

  6081. msgid "You can now customize the server name string that Riot-web displays in its login page."

  6082. msgstr ""

  6083. 

  6084. #: ../../../CHANGELOG.md:3336

  6085. msgid "These playbook variables, with these default values, have been added:"

  6086. msgstr ""

  6087. 

  6088. #: ../../../CHANGELOG.md:3342

  6089. 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\"."

  6090. msgstr ""

  6091. 

  6092. #: ../../../CHANGELOG.md:3344

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

  6094. msgstr ""

  6095. 

  6096. #: ../../../CHANGELOG.md:3347

  6097. msgid "2020-01-30"

  6098. msgstr ""

  6099. 

  6100. #: ../../../CHANGELOG.md:3349

  6101. msgid "Disabling TLSv1.1"

  6102. msgstr ""

  6103. 

  6104. #: ../../../CHANGELOG.md:3351

  6105. msgid "To improve security, we've removed TLSv1.1 support from our default matrix-nginx-proxy configuration."

  6106. msgstr ""

  6107. 

  6108. #: ../../../CHANGELOG.md:3353

  6109. 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\"`"

  6110. msgstr ""

  6111. 

  6112. #: ../../../CHANGELOG.md:3356

  6113. msgid "2020-01-21"

  6114. msgstr ""

  6115. 

  6116. #: ../../../CHANGELOG.md:3358

  6117. msgid "Postgres collation changes (action required!)"

  6118. msgstr ""

  6119. 

  6120. #: ../../../CHANGELOG.md:3360

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

  6122. msgstr ""

  6123. 

  6124. #: ../../../CHANGELOG.md:3362

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

  6126. msgstr ""

  6127. 

  6128. #: ../../../CHANGELOG.md:3364

  6129. msgid "To avoid future problems, we recommend that you run the following command:"

  6130. msgstr ""

  6131. 

  6132. #: ../../../CHANGELOG.md:3370

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

  6134. msgstr ""

  6135. 

  6136. #: ../../../CHANGELOG.md:3373

  6137. msgid "2020-01-14"

  6138. msgstr ""

  6139. 

  6140. #: ../../../CHANGELOG.md:3375

  6141. msgid "Added support for Appservice Webhooks"

  6142. msgstr ""

  6143. 

  6144. #: ../../../CHANGELOG.md:3377

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

  6146. msgstr ""

  6147. 

  6148. #: ../../../CHANGELOG.md:3379

  6149. msgid "Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-playbook-bridge-appservice-webhooks.md)."

  6150. msgstr ""

  6151. 

  6152. #: ../../../CHANGELOG.md:3382

  6153. msgid "2020-01-12"

  6154. msgstr ""

  6155. 

  6156. #: ../../../CHANGELOG.md:3384

  6157. msgid "Added support for automatic Double Puppeting for all Mautrix bridges"

  6158. msgstr ""

  6159. 

  6160. #: ../../../CHANGELOG.md:3386

  6161. msgid "Double Puppeting can now be easily enabled for all Mautrix bridges supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)."

  6162. msgstr ""

  6163. 

  6164. #: ../../../CHANGELOG.md:3388

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

  6166. msgstr ""

  6167. 

  6168. #: ../../../CHANGELOG.md:3390

  6169. msgid "To get started, following the playbook's documentation for the bridge you'd like to configure."

  6170. msgstr ""

  6171. 

  6172. #: ../../../CHANGELOG.md:3393

  6173. msgid "2019-12-06"

  6174. msgstr ""

  6175. 

  6176. #: ../../../CHANGELOG.md:3395

  6177. msgid "Added support for an alternative method for using another webserver"

  6178. msgstr ""

  6179. 

  6180. #: ../../../CHANGELOG.md:3397

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

  6182. msgstr ""

  6183. 

  6184. #: ../../../CHANGELOG.md:3399

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

  6186. msgstr ""

  6187. 

  6188. #: ../../../CHANGELOG.md:3401

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

  6190. msgstr ""

  6191. 

  6192. #: ../../../CHANGELOG.md:3404

  6193. msgid "2019-11-10"

  6194. msgstr ""

  6195. 

  6196. #: ../../../CHANGELOG.md:3406

  6197. msgid "Tightened security around room directory publishing"

  6198. msgstr ""

  6199. 

  6200. #: ../../../CHANGELOG.md:3408

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

  6202. msgstr ""

  6203. 

  6204. #: ../../../CHANGELOG.md:3410

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

  6206. msgstr ""

  6207. 

  6208. #: ../../../CHANGELOG.md:3412

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

  6210. msgstr ""

  6211. 

  6212. #: ../../../CHANGELOG.md:3415

  6213. msgid "2019-10-05"

  6214. msgstr ""

  6215. 

  6216. #: ../../../CHANGELOG.md:3417

  6217. msgid "Improved Postgres upgrading/importing"

  6218. msgstr ""

  6219. 

  6220. #: ../../../CHANGELOG.md:3419

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

  6222. msgstr ""

  6223. 

  6224. #: ../../../CHANGELOG.md:3421

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

  6226. msgstr ""

  6227. 

  6228. #: ../../../CHANGELOG.md:3423

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

  6230. msgstr ""

  6231. 

  6232. #: ../../../CHANGELOG.md:3425

  6233. msgid "Additionally, Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) now uses gzipped dump files by default, to minimize disk space usage."

  6234. msgstr ""

  6235. 

  6236. #: ../../../CHANGELOG.md:3428

  6237. msgid "2019-10-04"

  6238. msgstr ""

  6239. 

  6240. #: ../../../CHANGELOG.md:3430

  6241. msgid "Postgres 12 support"

  6242. msgstr ""

  6243. 

  6244. #: ../../../CHANGELOG.md:3432

  6245. msgid "The playbook now installs [Postgres 12](https://www.postgresql.org/about/news/1976/) by default."

  6246. msgstr ""

  6247. 

  6248. #: ../../../CHANGELOG.md:3434

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

  6250. msgstr ""

  6251. 

  6252. #: ../../../CHANGELOG.md:3437

  6253. msgid "2019-10-03"

  6254. msgstr ""

  6255. 

  6256. #: ../../../CHANGELOG.md:3439

  6257. msgid "Synapse 1.4.0"

  6258. msgstr ""

  6259. 

  6260. #: ../../../CHANGELOG.md:3441

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

  6262. msgstr ""

  6263. 

  6264. #: ../../../CHANGELOG.md:3443

  6265. 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: ~`)."

  6266. msgstr ""

  6267. 

  6268. #: ../../../CHANGELOG.md:3445

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

  6270. msgstr ""

  6271. 

  6272. #: ../../../CHANGELOG.md:3447

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

  6274. msgstr ""

  6275. 

  6276. #: ../../../CHANGELOG.md:3450

  6277. msgid "2019-09-09"

  6278. msgstr ""

  6279. 

  6280. #: ../../../CHANGELOG.md:3452

  6281. msgid "Synapse Simple Antispam support"

  6282. msgstr ""

  6283. 

  6284. #: ../../../CHANGELOG.md:3454

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

  6286. msgstr ""

  6287. 

  6288. #: ../../../CHANGELOG.md:3456

  6289. msgid "From now on, you can easily install and configure this spam checker module through the playbook."

  6290. msgstr ""

  6291. 

  6292. #: ../../../CHANGELOG.md:3458

  6293. msgid "Learn more in [Setting up Synapse Simple Antispam](docs/configuring-playbook-synapse-simple-antispam.md)."

  6294. msgstr ""

  6295. 

  6296. #: ../../../CHANGELOG.md:3461

  6297. msgid "2019-08-25"

  6298. msgstr ""

  6299. 

  6300. #: ../../../CHANGELOG.md:3463

  6301. msgid "Extensible Riot-web configuration"

  6302. msgstr ""

  6303. 

  6304. #: ../../../CHANGELOG.md:3465

  6305. msgid "Similarly to [Extensible Synapse configuration](#extensible-synapse-configuration) (below), Riot-web configuration is also extensible now."

  6306. msgstr ""

  6307. 

  6308. #: ../../../CHANGELOG.md:3467

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

  6310. msgstr ""

  6311. 

  6312. #: ../../../CHANGELOG.md:3469

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

  6314. msgstr ""

  6315. 

  6316. #: ../../../CHANGELOG.md:3471

  6317. msgid "Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-web.md)."

  6318. msgstr ""

  6319. 

  6320. #: ../../../CHANGELOG.md:3474

  6321. msgid "2019-08-22"

  6322. msgstr ""

  6323. 

  6324. #: ../../../CHANGELOG.md:3476

  6325. msgid "Extensible Synapse configuration"

  6326. msgstr ""

  6327. 

  6328. #: ../../../CHANGELOG.md:3478

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

  6330. msgstr ""

  6331. 

  6332. #: ../../../CHANGELOG.md:3480

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

  6334. msgstr ""

  6335. 

  6336. #: ../../../CHANGELOG.md:3482

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

  6338. msgstr ""

  6339. 

  6340. #: ../../../CHANGELOG.md:3484

  6341. msgid "Learn more here in [Configuring Synapse](docs/configuring-playbook-synapse.md)."

  6342. msgstr ""

  6343. 

  6344. #: ../../../CHANGELOG.md:3487

  6345. msgid "2019-08-21"

  6346. msgstr ""

  6347. 

  6348. #: ../../../CHANGELOG.md:3491

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

  6350. msgstr ""

  6351. 

  6352. #: ../../../CHANGELOG.md:3493

  6353. msgid "Additional details are available in [Setting up Appservice Slack bridging](docs/configuring-playbook-bridge-appservice-slack.md)."

  6354. msgstr ""

  6355. 

  6356. #: ../../../CHANGELOG.md:3495

  6357. msgid "Google Hangouts bridging support"

  6358. msgstr ""

  6359. 

  6360. #: ../../../CHANGELOG.md:3497

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

  6362. msgstr ""

  6363. 

  6364. #: ../../../CHANGELOG.md:3499

  6365. msgid "Additional details are available in [Setting up Mautrix Hangouts bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)."

  6366. msgstr ""

  6367. 

  6368. #: ../../../CHANGELOG.md:3502

  6369. msgid "2019-08-05"

  6370. msgstr ""

  6371. 

  6372. #: ../../../CHANGELOG.md:3504

  6373. msgid "Email2Matrix support"

  6374. msgstr ""

  6375. 

  6376. #: ../../../CHANGELOG.md:3506

  6377. msgid "Support for [Email2Matrix](https://github.com/devture/email2matrix) has been added."

  6378. msgstr ""

  6379. 

  6380. #: ../../../CHANGELOG.md:3508

  6381. msgid "It's an optional feature that you can enable via the playbook."

  6382. msgstr ""

  6383. 

  6384. #: ../../../CHANGELOG.md:3510

  6385. msgid "To learn more, see the [playbook's documentation on Email2Matrix](./docs/configuring-playbook-email2matrix.md)."

  6386. msgstr ""

  6387. 

  6388. #: ../../../CHANGELOG.md:3513

  6389. msgid "2019-08-03"

  6390. msgstr ""

  6391. 

  6392. #: ../../../CHANGELOG.md:3515

  6393. msgid "Synapse logging level has been reduced to WARNING"

  6394. msgstr ""

  6395. 

  6396. #: ../../../CHANGELOG.md:3517

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

  6398. msgstr ""

  6399. 

  6400. #: ../../../CHANGELOG.md:3519

  6401. msgid "This greatly reduces the number of log messages that are being logged, leading to:"

  6402. msgstr ""

  6403. 

  6404. #: ../../../CHANGELOG.md:3521

  6405. msgid "much less disk space dedicated to Synapse and thus, logs kept for longer"

  6406. msgstr ""

  6407. 

  6408. #: ../../../CHANGELOG.md:3522

  6409. msgid "easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages, as they're not longer buried in thousands of non-important `INFO` messages"

  6410. msgstr ""

  6411. 

  6412. #: ../../../CHANGELOG.md:3524

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

  6414. msgstr ""

  6415. 

  6416. #: ../../../CHANGELOG.md:3527

  6417. msgid "2019-07-08"

  6418. msgstr ""

  6419. 

  6420. #: ../../../CHANGELOG.md:3529

  6421. msgid "Synapse Maintenance docs and synapse-janitor support are available"

  6422. msgstr ""

  6423. 

  6424. #: ../../../CHANGELOG.md:3531

  6425. msgid "The playbook can now help you with Synapse's maintenance."

  6426. msgstr ""

  6427. 

  6428. #: ../../../CHANGELOG.md:3533

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

  6430. msgstr ""

  6431. 

  6432. #: ../../../CHANGELOG.md:3535

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

  6434. msgstr ""

  6435. 

  6436. #: ../../../CHANGELOG.md:3537

  6437. msgid "(BC Break) Rename run control variables"

  6438. msgstr ""

  6439. 

  6440. #: ../../../CHANGELOG.md:3539

  6441. msgid "Some internal playbook control variables have been renamed."

  6442. msgstr ""

  6443. 

  6444. #: ../../../CHANGELOG.md:3541

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

  6446. msgstr ""

  6447. 

  6448. #: ../../../CHANGELOG.md:3543

  6449. msgid "The following variables have been renamed:"

  6450. msgstr ""

  6451. 

  6452. #: ../../../CHANGELOG.md:3545

  6453. msgid "from `run_import_postgres` to `run_postgres_import`"

  6454. msgstr ""

  6455. 

  6456. #: ../../../CHANGELOG.md:3546

  6457. msgid "from `run_import_sqlite_db` to `run_postgres_import_sqlite_db`"

  6458. msgstr ""

  6459. 

  6460. #: ../../../CHANGELOG.md:3547

  6461. msgid "from `run_upgrade_postgres` to `run_postgres_upgrade`"

  6462. msgstr ""

  6463. 

  6464. #: ../../../CHANGELOG.md:3548

  6465. msgid "from `run_import_media_store` to `run_synapse_import_media_store`"

  6466. msgstr ""

  6467. 

  6468. #: ../../../CHANGELOG.md:3549

  6469. msgid "from `run_register_user` to `run_synapse_register_user`"

  6470. msgstr ""

  6471. 

  6472. #: ../../../CHANGELOG.md:3550

  6473. msgid "from `run_update_user_password` to `run_synapse_update_user_password`"

  6474. msgstr ""

  6475. 

  6476. #: ../../../CHANGELOG.md:3553

  6477. msgid "2019-07-04"

  6478. msgstr ""

  6479. 

  6480. #: ../../../CHANGELOG.md:3555

  6481. msgid "Synapse no longer logs to text files"

  6482. msgstr ""

  6483. 

  6484. #: ../../../CHANGELOG.md:3557

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

  6486. msgstr ""

  6487. 

  6488. #: ../../../CHANGELOG.md:3559

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

  6490. msgstr ""

  6491. 

  6492. #: ../../../CHANGELOG.md:3561

  6493. msgid "Because of this, the following variables have become obsolete and were removed:"

  6494. msgstr ""

  6495. 

  6496. #: ../../../CHANGELOG.md:3563

  6497. msgid "`matrix_synapse_max_log_file_size_mb`"

  6498. msgstr ""

  6499. 

  6500. #: ../../../CHANGELOG.md:3564

  6501. msgid "`matrix_synapse_max_log_files_count`"

  6502. msgstr ""

  6503. 

  6504. #: ../../../CHANGELOG.md:3566

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

  6506. msgstr ""

  6507. 

  6508. #: ../../../CHANGELOG.md:3568

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

  6510. msgstr ""

  6511. 

  6512. #: ../../../CHANGELOG.md:3571

  6513. msgid "2019-06-27"

  6514. msgstr ""

  6515. 

  6516. #: ../../../CHANGELOG.md:3573

  6517. msgid "(BC Break) Discord bridge configuration is now entirely managed by the playbook"

  6518. msgstr ""

  6519. 

  6520. #: ../../../CHANGELOG.md:3575

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

  6522. msgstr ""

  6523. 

  6524. #: ../../../CHANGELOG.md:3577

  6525. msgid "From now on, the playbook will keep both configuration files sync for you."

  6526. msgstr ""

  6527. 

  6528. #: ../../../CHANGELOG.md:3579

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

  6530. msgstr ""

  6531. 

  6532. #: ../../../CHANGELOG.md:3581

  6533. msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-discord/config`)."

  6534. msgstr ""

  6535. 

  6536. #: ../../../CHANGELOG.md:3583

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

  6538. msgstr ""

  6539. 

  6540. #: ../../../CHANGELOG.md:3585

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

  6542. msgstr ""

  6543. 

  6544. #: ../../../CHANGELOG.md:3587

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

  6546. msgstr ""

  6547. 

  6548. #: ../../../CHANGELOG.md:3590

  6549. msgid "2019-06-24"

  6550. msgstr ""

  6551. 

  6552. #: ../../../CHANGELOG.md:3592

  6553. msgid "(BC Break) WhatsApp bridge configuration is now entirely managed by the playbook"

  6554. msgstr ""

  6555. 

  6556. #: ../../../CHANGELOG.md:3594

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

  6558. msgstr ""

  6559. 

  6560. #: ../../../CHANGELOG.md:3596

  6561. #: ../../../CHANGELOG.md:3613

  6562. #: ../../../CHANGELOG.md:3632

  6563. #: ../../../CHANGELOG.md:3671

  6564. msgid "From now on, the playbook will keep the configuration in sync for you."

  6565. msgstr ""

  6566. 

  6567. #: ../../../CHANGELOG.md:3598

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

  6569. msgstr ""

  6570. 

  6571. #: ../../../CHANGELOG.md:3600

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

  6573. msgstr ""

  6574. 

  6575. #: ../../../CHANGELOG.md:3602

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

  6577. msgstr ""

  6578. 

  6579. #: ../../../CHANGELOG.md:3604

  6580. msgid "We're now following the default configuration for the WhatsApp bridge."

  6581. msgstr ""

  6582. 

  6583. #: ../../../CHANGELOG.md:3607

  6584. msgid "2019-06-20"

  6585. msgstr ""

  6586. 

  6587. #: ../../../CHANGELOG.md:3609

  6588. msgid "(BC Break) IRC bridge configuration is now entirely managed by the playbook"

  6589. msgstr ""

  6590. 

  6591. #: ../../../CHANGELOG.md:3611

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

  6593. msgstr ""

  6594. 

  6595. #: ../../../CHANGELOG.md:3615

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

  6597. msgstr ""

  6598. 

  6599. #: ../../../CHANGELOG.md:3617

  6600. 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`)."

  6601. msgstr ""

  6602. 

  6603. #: ../../../CHANGELOG.md:3619

  6604. 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."

  6605. msgstr ""

  6606. 

  6607. #: ../../../CHANGELOG.md:3621

  6608. 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`."

  6609. msgstr ""

  6610. 

  6611. #: ../../../CHANGELOG.md:3623

  6612. 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`)."

  6613. msgstr ""

  6614. 

  6615. #: ../../../CHANGELOG.md:3626

  6616. msgid "2019-06-15"

  6617. msgstr ""

  6618. 

  6619. #: ../../../CHANGELOG.md:3628

  6620. msgid "(BC Break) Telegram bridge configuration is now entirely managed by the playbook"

  6621. msgstr ""

  6622. 

  6623. #: ../../../CHANGELOG.md:3630

  6624. 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."

  6625. msgstr ""

  6626. 

  6627. #: ../../../CHANGELOG.md:3634

  6628. 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."

  6629. msgstr ""

  6630. 

  6631. #: ../../../CHANGELOG.md:3636

  6632. 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."

  6633. msgstr ""

  6634. 

  6635. #: ../../../CHANGELOG.md:3638

  6636. 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`)."

  6637. msgstr ""

  6638. 

  6639. #: ../../../CHANGELOG.md:3640

  6640. msgid "Also, we're now following the default configuration for the Telegram bridge, so some default configuration values are different:"

  6641. msgstr ""

  6642. 

  6643. #: ../../../CHANGELOG.md:3642

  6644. 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"

  6645. msgstr ""

  6646. 

  6647. #: ../../../CHANGELOG.md:3643

  6648. 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."

  6649. msgstr ""

  6650. 

  6651. #: ../../../CHANGELOG.md:3644

  6652. msgid "`authless_portals` (used to be `false`, now `true`) — creating portals from the Telegram side is now possible"

  6653. msgstr ""

  6654. 

  6655. #: ../../../CHANGELOG.md:3645

  6656. msgid "`whitelist_group_admins` (used to be `false`, now `true`) — allows Telegram group admins to use the bot commands"

  6657. msgstr ""

  6658. 

  6659. #: ../../../CHANGELOG.md:3647

  6660. 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)."

  6661. msgstr ""

  6662. 

  6663. #: ../../../CHANGELOG.md:3650

  6664. msgid "2019-06-12"

  6665. msgstr ""

  6666. 

  6667. #: ../../../CHANGELOG.md:3652

  6668. msgid "Synapse v1.0"

  6669. msgstr ""

  6670. 

  6671. #: ../../../CHANGELOG.md:3654

  6672. 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)."

  6673. msgstr ""

  6674. 

  6675. #: ../../../CHANGELOG.md:3656

  6676. 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."

  6677. msgstr ""

  6678. 

  6679. #: ../../../CHANGELOG.md:3658

  6680. msgid "**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` DNS SRV records. The latter, **must not** be removed."

  6681. msgstr ""

  6682. 

  6683. #: ../../../CHANGELOG.md:3660

  6684. 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."

  6685. msgstr ""

  6686. 

  6687. #: ../../../CHANGELOG.md:3662

  6688. 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)."

  6689. msgstr ""

  6690. 

  6691. #: ../../../CHANGELOG.md:3665

  6692. msgid "2019-06-07"

  6693. msgstr ""

  6694. 

  6695. #: ../../../CHANGELOG.md:3667

  6696. msgid "(BC Break) Facebook bridge configuration is now entirely managed by the playbook"

  6697. msgstr ""

  6698. 

  6699. #: ../../../CHANGELOG.md:3669

  6700. 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."

  6701. msgstr ""

  6702. 

  6703. #: ../../../CHANGELOG.md:3673

  6704. 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."

  6705. msgstr ""

  6706. 

  6707. #: ../../../CHANGELOG.md:3675

  6708. 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."

  6709. msgstr ""

  6710. 

  6711. #: ../../../CHANGELOG.md:3677

  6712. 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`)."

  6713. msgstr ""

  6714. 

  6715. #: ../../../CHANGELOG.md:3680

  6716. msgid "2019-05-25"

  6717. msgstr ""

  6718. 

  6719. #: ../../../CHANGELOG.md:3682

  6720. msgid "Support for exposing container ports publicly (not just to the host)"

  6721. msgstr ""

  6722. 

  6723. #: ../../../CHANGELOG.md:3684

  6724. 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."

  6725. msgstr ""

  6726. 

  6727. #: ../../../CHANGELOG.md:3686

  6728. 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`."

  6729. msgstr ""

  6730. 

  6731. #: ../../../CHANGELOG.md:3688

  6732. msgid "All such variables have been superseded by a better (more flexible) way to do it."

  6733. msgstr ""

  6734. 

  6735. #: ../../../CHANGELOG.md:3690

  6736. msgid "**Most** people (including those not using `matrix-nginx-proxy`), **don't need** to bother with this."

  6737. msgstr ""

  6738. 

  6739. #: ../../../CHANGELOG.md:3692

  6740. msgid "Porting examples follow for people having more customized setups:"

  6741. msgstr ""

  6742. 

  6743. #: ../../../CHANGELOG.md:3694

  6744. msgid "**from** `matrix_synapse_container_expose_client_api_port: true` **to** `matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`"

  6745. msgstr ""

  6746. 

  6747. #: ../../../CHANGELOG.md:3696

  6748. 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'`"

  6749. msgstr ""

  6750. 

  6751. #: ../../../CHANGELOG.md:3698

  6752. msgid "**from** `matrix_synapse_container_expose_metrics_port: true` **to** `matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`"

  6753. msgstr ""

  6754. 

  6755. #: ../../../CHANGELOG.md:3700

  6756. msgid "**from** `matrix_riot_web_container_expose_port: true` **to** `matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`"

  6757. msgstr ""

  6758. 

  6759. #: ../../../CHANGELOG.md:3702

  6760. msgid "**from** `matrix_mxisd_container_expose_port: true` **to** `matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`"

  6761. msgstr ""

  6762. 

  6763. #: ../../../CHANGELOG.md:3704

  6764. msgid "**from** `matrix_dimension_container_expose_port: true` **to** `matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`"

  6765. msgstr ""

  6766. 

  6767. #: ../../../CHANGELOG.md:3706

  6768. 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'`"

  6769. msgstr ""

  6770. 

  6771. #: ../../../CHANGELOG.md:3708

  6772. 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'`"

  6773. msgstr ""

  6774. 

  6775. #: ../../../CHANGELOG.md:3710

  6776. 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'`"

  6777. msgstr ""

  6778. 

  6779. #: ../../../CHANGELOG.md:3712

  6780. msgid "As always, if you forget to remove usage of some outdated variable, the playbook will warn you."

  6781. msgstr ""

  6782. 

  6783. #: ../../../CHANGELOG.md:3715

  6784. msgid "2019-05-23"

  6785. msgstr ""

  6786. 

  6787. #: ../../../CHANGELOG.md:3717

  6788. msgid "(BC Break) Ansible 2.8 compatibility"

  6789. msgstr ""

  6790. 

  6791. #: ../../../CHANGELOG.md:3719

  6792. 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)."

  6793. msgstr ""

  6794. 

  6795. #: ../../../CHANGELOG.md:3721

  6796. msgid "A manual change is required to the `inventory/hosts` file, changing the group name from `matrix-servers` to `matrix_servers` (dash to underscore)."

  6797. msgstr ""

  6798. 

  6799. #: ../../../CHANGELOG.md:3723

  6800. msgid "To avoid doing it manually, run this:"

  6801. msgstr ""

  6802. 

  6803. #: ../../../CHANGELOG.md:3724

  6804. msgid "Linux: `sed -i 's/matrix-servers/matrix_servers/g' inventory/hosts`"

  6805. msgstr ""

  6806. 

  6807. #: ../../../CHANGELOG.md:3725

  6808. msgid "Mac: `sed -i '' 's/matrix-servers/matrix_servers/g' inventory/hosts`"

  6809. msgstr ""

  6810. 

  6811. #: ../../../CHANGELOG.md:3728

  6812. msgid "2019-05-21"

  6813. msgstr ""

  6814. 

  6815. #: ../../../CHANGELOG.md:3730

  6816. msgid "Synapse no longer required"

  6817. msgstr ""

  6818. 

  6819. #: ../../../CHANGELOG.md:3732

  6820. msgid "The playbook no longer insists on installing [Synapse](https://github.com/element-hq/synapse) via the `matrix-synapse` role."

  6821. msgstr ""

  6822. 

  6823. #: ../../../CHANGELOG.md:3734

  6824. 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`)."

  6825. msgstr ""

  6826. 

  6827. #: ../../../CHANGELOG.md:3736

  6828. 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."

  6829. msgstr ""

  6830. 

  6831. #: ../../../CHANGELOG.md:3738

  6832. msgid "Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers."

  6833. msgstr ""

  6834. 

  6835. #: ../../../CHANGELOG.md:3740

  6836. msgid "Bridges are now separate from the Synapse role"

  6837. msgstr ""

  6838. 

  6839. #: ../../../CHANGELOG.md:3742

  6840. msgid "Bridges are no longer part of the `matrix-synapse` role. Each bridge now lives in its own separate role (`roles/custom/matrix-bridge-*`)."

  6841. msgstr ""

  6842. 

  6843. #: ../../../CHANGELOG.md:3744

  6844. 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)."

  6845. msgstr ""

  6846. 

  6847. #: ../../../CHANGELOG.md:3746

  6848. msgid "Renaming inconsistently-named Synapse variables"

  6849. msgstr ""

  6850. 

  6851. #: ../../../CHANGELOG.md:3748

  6852. msgid "For better consistency, the following variables have been renamed:"

  6853. msgstr ""

  6854. 

  6855. #: ../../../CHANGELOG.md:3750

  6856. msgid "`matrix_enable_room_list_search` was renamed to `matrix_synapse_enable_room_list_search`"

  6857. msgstr ""

  6858. 

  6859. #: ../../../CHANGELOG.md:3751

  6860. msgid "`matrix_alias_creation_rules` was renamed to `matrix_synapse_alias_creation_rules`"

  6861. msgstr ""

  6862. 

  6863. #: ../../../CHANGELOG.md:3752

  6864. msgid "`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was renamed to `matrix_synapse_room_list_publication_rules`"

  6865. msgstr ""

  6866. 

  6867. #: ../../../CHANGELOG.md:3755

  6868. msgid "2019-05-09"

  6869. msgstr ""

  6870. 

  6871. #: ../../../CHANGELOG.md:3757

  6872. msgid "Besides a myriad of bug fixes and minor improvements, here are the more notable (bigger) features we can announce today."

  6873. msgstr ""

  6874. 

  6875. #: ../../../CHANGELOG.md:3759

  6876. msgid "Mautrix Facebook/Messenger bridging support"

  6877. msgstr ""

  6878. 

  6879. #: ../../../CHANGELOG.md:3761

  6880. 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)."

  6881. msgstr ""

  6882. 

  6883. #: ../../../CHANGELOG.md:3763

  6884. msgid "Additional details are available in [Setting up Mautrix Facebook bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)."

  6885. msgstr ""

  6886. 

  6887. #: ../../../CHANGELOG.md:3765

  6888. msgid "mxisd Registration feature integration"

  6889. msgstr ""

  6890. 

  6891. #: ../../../CHANGELOG.md:3767

  6892. 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."

  6893. msgstr ""

  6894. 

  6895. #: ../../../CHANGELOG.md:3769

  6896. msgid "Learn more in [mxisd-controlled Registration](docs/configuring-playbook-mxisd.md#mxisd-controlled-registration)."

  6897. msgstr ""

  6898. 

  6899. #: ../../../CHANGELOG.md:3772

  6900. msgid "2019-04-16"

  6901. msgstr ""

  6902. 

  6903. #: ../../../CHANGELOG.md:3774

  6904. msgid "Caddy webserver examples"

  6905. msgstr ""

  6906. 

  6907. #: ../../../CHANGELOG.md:3776

  6908. 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"

  6909. msgstr ""

  6910. 

  6911. #: ../../../CHANGELOG.md:3778

  6912. msgid "2019-04-10"

  6913. msgstr ""

  6914. 

  6915. #: ../../../CHANGELOG.md:3780

  6916. msgid "Goofys support for other S3-compatible object stores"

  6917. msgstr ""

  6918. 

  6919. #: ../../../CHANGELOG.md:3782

  6920. 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),"

  6921. msgstr ""

  6922. 

  6923. #: ../../../CHANGELOG.md:3785

  6924. msgid "2019-04-03"

  6925. msgstr ""

  6926. 

  6927. #: ../../../CHANGELOG.md:3787

  6928. msgid "Ansible >= 2.5 is required"

  6929. msgstr ""

  6930. 

  6931. #: ../../../CHANGELOG.md:3789

  6932. 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)."

  6933. msgstr ""

  6934. 

  6935. #: ../../../CHANGELOG.md:3791

  6936. 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))."

  6937. msgstr ""

  6938. 

  6939. #: ../../../CHANGELOG.md:3794

  6940. msgid "2019-03-19"

  6941. msgstr ""

  6942. 

  6943. #: ../../../CHANGELOG.md:3796

  6944. msgid "TLS support for coturn"

  6945. msgstr ""

  6946. 

  6947. #: ../../../CHANGELOG.md:3798

  6948. 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."

  6949. msgstr ""

  6950. 

  6951. #: ../../../CHANGELOG.md:3800

  6952. 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:"

  6953. msgstr ""

  6954. 

  6955. #: ../../../CHANGELOG.md:3806

  6956. 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)."

  6957. msgstr ""

  6958. 

  6959. #: ../../../CHANGELOG.md:3808

  6960. msgid "People who build their own custom playbook from our roles should be aware that:"

  6961. msgstr ""

  6962. 

  6963. #: ../../../CHANGELOG.md:3810

  6964. 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)."

  6965. msgstr ""

  6966. 

  6967. #: ../../../CHANGELOG.md:3812

  6968. 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)."

  6969. msgstr ""

  6970. 

  6971. #: ../../../CHANGELOG.md:3815

  6972. msgid "2019-03-12"

  6973. msgstr ""

  6974. 

  6975. #: ../../../CHANGELOG.md:3817

  6976. msgid "matrix-nginx-proxy support for serving the base domain"

  6977. msgstr ""

  6978. 

  6979. #: ../../../CHANGELOG.md:3819

  6980. 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."

  6981. msgstr ""

  6982. 

  6983. #: ../../../CHANGELOG.md:3821

  6984. 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."

  6985. msgstr ""

  6986. 

  6987. #: ../../../CHANGELOG.md:3823

  6988. msgid "(BC break) matrix-nginx-proxy data variable renamed"

  6989. msgstr ""

  6990. 

  6991. #: ../../../CHANGELOG.md:3825

  6992. msgid "`matrix_nginx_proxy_data_path` was renamed to `matrix_nginx_proxy_base_path`."

  6993. msgstr ""

  6994. 

  6995. #: ../../../CHANGELOG.md:3827

  6996. 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)."

  6997. msgstr ""

  6998. 

  6999. #: ../../../CHANGELOG.md:3830

  7000. msgid "2019-03-10"

  7001. msgstr ""

  7002. 

  7003. #: ../../../CHANGELOG.md:3832

  7004. msgid "Dimension integration manager support"

  7005. msgstr ""

  7006. 

  7007. #: ../../../CHANGELOG.md:3834

  7008. 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."

  7009. msgstr ""

  7010. 

  7011. #: ../../../CHANGELOG.md:3837

  7012. msgid "2019-03-07"

  7013. msgstr ""

  7014. 

  7015. #: ../../../CHANGELOG.md:3839

  7016. msgid "Ability to customize mxisd's email templates"

  7017. msgstr ""

  7018. 

  7019. #: ../../../CHANGELOG.md:3841

  7020. 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."

  7021. msgstr ""

  7022. 

  7023. #: ../../../CHANGELOG.md:3844

  7024. msgid "2019-03-05"

  7025. msgstr ""

  7026. 

  7027. #: ../../../CHANGELOG.md:3846

  7028. msgid "Discord bridging support"

  7029. msgstr ""

  7030. 

  7031. #: ../../../CHANGELOG.md:3848

  7032. 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."

  7033. msgstr ""

  7034. 

  7035. #: ../../../CHANGELOG.md:3851

  7036. msgid "2019-02-19"

  7037. msgstr ""

  7038. 

  7039. #: ../../../CHANGELOG.md:3853

  7040. msgid "Renaming variables"

  7041. msgstr ""

  7042. 

  7043. #: ../../../CHANGELOG.md:3855

  7044. #: ../../../CHANGELOG.md:4172

  7045. #: ../../../CHANGELOG.md:4257

  7046. #: ../../../CHANGELOG.md:4377

  7047. msgid "The following playbook variables were renamed:"

  7048. msgstr ""

  7049. 

  7050. #: ../../../CHANGELOG.md:3857

  7051. msgid "from `host_specific_hostname_identity` to `matrix_domain`"

  7052. msgstr ""

  7053. 

  7054. #: ../../../CHANGELOG.md:3858

  7055. msgid "from `hostname_identity` to `matrix_domain`"

  7056. msgstr ""

  7057. 

  7058. #: ../../../CHANGELOG.md:3859

  7059. msgid "from `hostname_matrix` to `matrix_server_fqn_matrix`"

  7060. msgstr ""

  7061. 

  7062. #: ../../../CHANGELOG.md:3860

  7063. msgid "from `hostname_riot` to `matrix_server_fqn_riot`"

  7064. msgstr ""

  7065. 

  7066. #: ../../../CHANGELOG.md:3861

  7067. msgid "from `host_specific_matrix_ssl_lets_encrypt_support_email` to `matrix_ssl_lets_encrypt_support_email`"

  7068. msgstr ""

  7069. 

  7070. #: ../../../CHANGELOG.md:3863

  7071. msgid "Doing that, we've simplified things, made names less confusing (hopefully) and moved all variable names under the `matrix_` prefix."

  7072. msgstr ""

  7073. 

  7074. #: ../../../CHANGELOG.md:3866

  7075. msgid "2019-02-16"

  7076. msgstr ""

  7077. 

  7078. #: ../../../CHANGELOG.md:3868

  7079. msgid "Riot v1.0.1 support"

  7080. msgstr ""

  7081. 

  7082. #: ../../../CHANGELOG.md:3870

  7083. msgid "You can now use the brand new and redesigned Riot."

  7084. msgstr ""

  7085. 

  7086. #: ../../../CHANGELOG.md:3872

  7087. msgid "The new version no longer has a homepage by default, so we've also removed the custom homepage that we've been installing."

  7088. msgstr ""

  7089. 

  7090. #: ../../../CHANGELOG.md:3874

  7091. 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)."

  7092. msgstr ""

  7093. 

  7094. #: ../../../CHANGELOG.md:3877

  7095. msgid "2019-02-14"

  7096. msgstr ""

  7097. 

  7098. #: ../../../CHANGELOG.md:3879

  7099. msgid "Synapse v0.99.1"

  7100. msgstr ""

  7101. 

  7102. #: ../../../CHANGELOG.md:3881

  7103. 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."

  7104. msgstr ""

  7105. 

  7106. #: ../../../CHANGELOG.md:3883

  7107. 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."

  7108. msgstr ""

  7109. 

  7110. #: ../../../CHANGELOG.md:3886

  7111. msgid "2019-02-06"

  7112. msgstr ""

  7113. 

  7114. #: ../../../CHANGELOG.md:3888

  7115. msgid "Synapse v0.99 support and preparation for Synapse v1.0"

  7116. msgstr ""

  7117. 

  7118. #: ../../../CHANGELOG.md:3890

  7119. 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."

  7120. msgstr ""

  7121. 

  7122. #: ../../../CHANGELOG.md:3892

  7123. 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))."

  7124. msgstr ""

  7125. 

  7126. #: ../../../CHANGELOG.md:3894

  7127. 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)."

  7128. msgstr ""

  7129. 

  7130. #: ../../../CHANGELOG.md:3896

  7131. 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:"

  7132. msgstr ""

  7133. 

  7134. #: ../../../CHANGELOG.md:3898

  7135. 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."

  7136. msgstr ""

  7137. 

  7138. #: ../../../CHANGELOG.md:3900

  7139. 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)."

  7140. msgstr ""

  7141. 

  7142. #: ../../../CHANGELOG.md:3903

  7143. msgid "2019-02-01"

  7144. msgstr ""

  7145. 

  7146. #: ../../../CHANGELOG.md:3905

  7147. msgid "TLS v1.3 support"

  7148. msgstr ""

  7149. 

  7150. #: ../../../CHANGELOG.md:3907

  7151. 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."

  7152. msgstr ""

  7153. 

  7154. #: ../../../CHANGELOG.md:3909

  7155. msgid "When using:"

  7156. msgstr ""

  7157. 

  7158. #: ../../../CHANGELOG.md:3911

  7159. 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`."

  7160. msgstr ""

  7161. 

  7162. #: ../../../CHANGELOG.md:3913

  7163. 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)"

  7164. msgstr ""

  7165. 

  7166. #: ../../../CHANGELOG.md:3915

  7167. msgid "**another web server**: you don't need to do anything to accommodate this change"

  7168. msgstr ""

  7169. 

  7170. #: ../../../CHANGELOG.md:3918

  7171. msgid "2019-01-31"

  7172. msgstr ""

  7173. 

  7174. #: ../../../CHANGELOG.md:3920

  7175. msgid "IRC bridging support"

  7176. msgstr ""

  7177. 

  7178. #: ../../../CHANGELOG.md:3922

  7179. 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."

  7180. msgstr ""

  7181. 

  7182. #: ../../../CHANGELOG.md:3925

  7183. msgid "2019-01-29"

  7184. msgstr ""

  7185. 

  7186. #: ../../../CHANGELOG.md:3927

  7187. msgid "Running container processes as non-root, without capabilities and read-only"

  7188. msgstr ""

  7189. 

  7190. #: ../../../CHANGELOG.md:3929

  7191. 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."

  7192. msgstr ""

  7193. 

  7194. #: ../../../CHANGELOG.md:3931

  7195. 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."

  7196. msgstr ""

  7197. 

  7198. #: ../../../CHANGELOG.md:3933

  7199. 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."

  7200. msgstr ""

  7201. 

  7202. #: ../../../CHANGELOG.md:3935

  7203. 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."

  7204. msgstr ""

  7205. 

  7206. #: ../../../CHANGELOG.md:3937

  7207. msgid "matrix-mailer is now based on Exim, not Postfix"

  7208. msgstr ""

  7209. 

  7210. #: ../../../CHANGELOG.md:3939

  7211. 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)."

  7212. msgstr ""

  7213. 

  7214. #: ../../../CHANGELOG.md:3941

  7215. 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`)."

  7216. msgstr ""

  7217. 

  7218. #: ../../../CHANGELOG.md:3943

  7219. 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)."

  7220. msgstr ""

  7221. 

  7222. #: ../../../CHANGELOG.md:3946

  7223. msgid "2019-01-17"

  7224. msgstr ""

  7225. 

  7226. #: ../../../CHANGELOG.md:3948

  7227. msgid "(BC Break) Making the playbook's roles more independent of one another"

  7228. msgstr ""

  7229. 

  7230. #: ../../../CHANGELOG.md:3950

  7231. 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)."

  7232. msgstr ""

  7233. 

  7234. #: ../../../CHANGELOG.md:3953

  7235. 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."

  7236. msgstr ""

  7237. 

  7238. #: ../../../CHANGELOG.md:3955

  7239. msgid "With the new changes, **all roles are now only dependent on the minimal `matrix-base` role**. They are no longer dependent among themselves."

  7240. msgstr ""

  7241. 

  7242. #: ../../../CHANGELOG.md:3957

  7243. msgid "In addition, the following components can now be completely disabled (for those who want/need to):"

  7244. msgstr ""

  7245. 

  7246. #: ../../../CHANGELOG.md:3958

  7247. msgid "`matrix-coturn` by using `coturn_enabled: false`"

  7248. msgstr ""

  7249. 

  7250. #: ../../../CHANGELOG.md:3959

  7251. msgid "`matrix-mailer` by using `matrix_mailer_enabled: false`"

  7252. msgstr ""

  7253. 

  7254. #: ../../../CHANGELOG.md:3960

  7255. msgid "`matrix-postgres` by using `matrix_postgres_enabled: false`"

  7256. msgstr ""

  7257. 

  7258. #: ../../../CHANGELOG.md:3962

  7259. msgid "The following changes had to be done:"

  7260. msgstr ""

  7261. 

  7262. #: ../../../CHANGELOG.md:3964

  7263. 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."

  7264. msgstr ""

  7265. 

  7266. #: ../../../CHANGELOG.md:3966

  7267. 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."

  7268. msgstr ""

  7269. 

  7270. #: ../../../CHANGELOG.md:3968

  7271. 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`)"

  7272. msgstr ""

  7273. 

  7274. #: ../../../CHANGELOG.md:3970

  7275. 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."

  7276. msgstr ""

  7277. 

  7278. #: ../../../CHANGELOG.md:3973

  7279. msgid "2019-01-16"

  7280. msgstr ""

  7281. 

  7282. #: ../../../CHANGELOG.md:3975

  7283. msgid "Splitting the playbook into multiple roles"

  7284. msgstr ""

  7285. 

  7286. #: ../../../CHANGELOG.md:3977

  7287. 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)."

  7288. msgstr ""

  7289. 

  7290. #: ../../../CHANGELOG.md:3980

  7291. msgid "To keep the filesystem more consistent with this separation, the **Postgres data had to be relocated**."

  7292. msgstr ""

  7293. 

  7294. #: ../../../CHANGELOG.md:3982

  7295. 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`)."

  7296. msgstr ""

  7297. 

  7298. #: ../../../CHANGELOG.md:3985

  7299. msgid "2019-01-11"

  7300. msgstr ""

  7301. 

  7302. #: ../../../CHANGELOG.md:3987

  7303. msgid "(BC Break) mxisd configuration changes"

  7304. msgstr ""

  7305. 

  7306. #: ../../../CHANGELOG.md:3989

  7307. 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."

  7308. msgstr ""

  7309. 

  7310. #: ../../../CHANGELOG.md:3992

  7311. msgid "The following variables are no longer supported by this playbook:"

  7312. msgstr ""

  7313. 

  7314. #: ../../../CHANGELOG.md:3994

  7315. msgid "`matrix_mxisd_ldap_enabled`"

  7316. msgstr ""

  7317. 

  7318. #: ../../../CHANGELOG.md:3995

  7319. msgid "`matrix_mxisd_ldap_connection_host`"

  7320. msgstr ""

  7321. 

  7322. #: ../../../CHANGELOG.md:3996

  7323. msgid "`matrix_mxisd_ldap_connection_tls`"

  7324. msgstr ""

  7325. 

  7326. #: ../../../CHANGELOG.md:3997

  7327. msgid "`matrix_mxisd_ldap_connection_port`"

  7328. msgstr ""

  7329. 

  7330. #: ../../../CHANGELOG.md:3998

  7331. msgid "`matrix_mxisd_ldap_connection_baseDn`"

  7332. msgstr ""

  7333. 

  7334. #: ../../../CHANGELOG.md:3999

  7335. msgid "`matrix_mxisd_ldap_connection_baseDns`"

  7336. msgstr ""

  7337. 

  7338. #: ../../../CHANGELOG.md:4000

  7339. #: ../../../CHANGELOG.md:4001

  7340. msgid "`matrix_mxisd_ldap_connection_bindDn`"

  7341. msgstr ""

  7342. 

  7343. #: ../../../CHANGELOG.md:4002

  7344. #: ../../../CHANGELOG.md:4006

  7345. msgid "`matrix_mxisd_ldap_connection_bindPassword`"

  7346. msgstr ""

  7347. 

  7348. #: ../../../CHANGELOG.md:4003

  7349. msgid "`matrix_mxisd_ldap_filter`"

  7350. msgstr ""

  7351. 

  7352. #: ../../../CHANGELOG.md:4004

  7353. msgid "`matrix_mxisd_ldap_attribute_uid_type`"

  7354. msgstr ""

  7355. 

  7356. #: ../../../CHANGELOG.md:4005

  7357. msgid "`matrix_mxisd_ldap_attribute_uid_value`"

  7358. msgstr ""

  7359. 

  7360. #: ../../../CHANGELOG.md:4007

  7361. msgid "`matrix_mxisd_ldap_attribute_name`"

  7362. msgstr ""

  7363. 

  7364. #: ../../../CHANGELOG.md:4008

  7365. msgid "`matrix_mxisd_ldap_attribute_threepid_email`"

  7366. msgstr ""

  7367. 

  7368. #: ../../../CHANGELOG.md:4009

  7369. msgid "`matrix_mxisd_ldap_attribute_threepid_msisdn`"

  7370. msgstr ""

  7371. 

  7372. #: ../../../CHANGELOG.md:4010

  7373. msgid "`matrix_mxisd_ldap_identity_filter`"

  7374. msgstr ""

  7375. 

  7376. #: ../../../CHANGELOG.md:4011

  7377. msgid "`matrix_mxisd_ldap_identity_medium`"

  7378. msgstr ""

  7379. 

  7380. #: ../../../CHANGELOG.md:4012

  7381. msgid "`matrix_mxisd_ldap_auth_filter`"

  7382. msgstr ""

  7383. 

  7384. #: ../../../CHANGELOG.md:4013

  7385. msgid "`matrix_mxisd_ldap_directory_filter`"

  7386. msgstr ""

  7387. 

  7388. #: ../../../CHANGELOG.md:4014

  7389. msgid "`matrix_mxisd_template_config`"

  7390. msgstr ""

  7391. 

  7392. #: ../../../CHANGELOG.md:4016

  7393. 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."

  7394. msgstr ""

  7395. 

  7396. #: ../../../CHANGELOG.md:4018

  7397. msgid "This new way of configuring mxisd is beneficial because:"

  7398. msgstr ""

  7399. 

  7400. #: ../../../CHANGELOG.md:4020

  7401. msgid "it lets us support all mxisd configuration options, as the playbook simply forwards them to mxisd without needing to care or understand them"

  7402. msgstr ""

  7403. 

  7404. #: ../../../CHANGELOG.md:4021

  7405. msgid "it lets you upgrade to newer mxisd versions and make use of their features, without us having to add support for them explicitly"

  7406. msgstr ""

  7407. 

  7408. #: ../../../CHANGELOG.md:4024

  7409. msgid "2019-01-08"

  7410. msgstr ""

  7411. 

  7412. #: ../../../CHANGELOG.md:4026

  7413. msgid "(BC Break) Cronjob schedule no longer configurable"

  7414. msgstr ""

  7415. 

  7416. #: ../../../CHANGELOG.md:4028

  7417. msgid "Due to the way we manage cronjobs now, you can no longer configure the schedule they're invoked at."

  7418. msgstr ""

  7419. 

  7420. #: ../../../CHANGELOG.md:4030

  7421. 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."

  7422. msgstr ""

  7423. 

  7424. #: ../../../CHANGELOG.md:4033

  7425. 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!"

  7426. msgstr ""

  7427. 

  7428. #: ../../../CHANGELOG.md:4036

  7429. msgid "2018-12-23"

  7430. msgstr ""

  7431. 

  7432. #: ../../../CHANGELOG.md:4038

  7433. msgid "(BC Break) More SSL certificate retrieval methods"

  7434. msgstr ""

  7435. 

  7436. #: ../../../CHANGELOG.md:4040

  7437. msgid "The playbook now lets you decide between 3 different SSL certificate retrieval methods:"

  7438. msgstr ""

  7439. 

  7440. #: ../../../CHANGELOG.md:4041

  7441. msgid "(default) obtaining free SSL certificates from Let's Encrypt"

  7442. msgstr ""

  7443. 

  7444. #: ../../../CHANGELOG.md:4042

  7445. msgid "generating self-signed SSL certificates"

  7446. msgstr ""

  7447. 

  7448. #: ../../../CHANGELOG.md:4043

  7449. msgid "managing SSL certificates manually"

  7450. msgstr ""

  7451. 

  7452. #: ../../../CHANGELOG.md:4045

  7453. msgid "Learn more in [Adjusting SSL certificate retrieval](docs/configuring-playbook-ssl-certificates.md)."

  7454. msgstr ""

  7455. 

  7456. #: ../../../CHANGELOG.md:4047

  7457. 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:"

  7458. msgstr ""

  7459. 

  7460. #: ../../../CHANGELOG.md:4049

  7461. msgid "before: `host_specific_matrix_ssl_support_email`"

  7462. msgstr ""

  7463. 

  7464. #: ../../../CHANGELOG.md:4050

  7465. msgid "after: `host_specific_matrix_ssl_lets_encrypt_support_email`"

  7466. msgstr ""

  7467. 

  7468. #: ../../../CHANGELOG.md:4052

  7469. msgid "(BC Break) mxisd upgrade with multiple base DN support"

  7470. msgstr ""

  7471. 

  7472. #: ../../../CHANGELOG.md:4054

  7473. 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)."

  7474. msgstr ""

  7475. 

  7476. #: ../../../CHANGELOG.md:4056

  7477. 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)."

  7478. msgstr ""

  7479. 

  7480. #: ../../../CHANGELOG.md:4058

  7481. msgid "Example change:"

  7482. msgstr ""

  7483. 

  7484. #: ../../../CHANGELOG.md:4060

  7485. msgid "before: `matrix_mxisd_ldap_connection_baseDn: OU=Users,DC=example,DC=org`"

  7486. msgstr ""

  7487. 

  7488. #: ../../../CHANGELOG.md:4061

  7489. msgid "after: `matrix_mxisd_ldap_connection_baseDns: ['OU=Users,DC=example,DC=org']`"

  7490. msgstr ""

  7491. 

  7492. #: ../../../CHANGELOG.md:4064

  7493. msgid "2018-12-21"

  7494. msgstr ""

  7495. 

  7496. #: ../../../CHANGELOG.md:4066

  7497. msgid "Synapse 0.34.0 and Python 3"

  7498. msgstr ""

  7499. 

  7500. #: ../../../CHANGELOG.md:4068

  7501. 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)."

  7502. msgstr ""

  7503. 

  7504. #: ../../../CHANGELOG.md:4071

  7505. msgid "2018-12-12"

  7506. msgstr ""

  7507. 

  7508. #: ../../../CHANGELOG.md:4073

  7509. msgid "Riot homepage customization"

  7510. msgstr ""

  7511. 

  7512. #: ../../../CHANGELOG.md:4075

  7513. 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`."

  7514. msgstr ""

  7515. 

  7516. #: ../../../CHANGELOG.md:4078

  7517. msgid "2018-12-04"

  7518. msgstr ""

  7519. 

  7520. #: ../../../CHANGELOG.md:4080

  7521. msgid "mxisd extensibility"

  7522. msgstr ""

  7523. 

  7524. #: ../../../CHANGELOG.md:4082

  7525. 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`)."

  7526. msgstr ""

  7527. 

  7528. #: ../../../CHANGELOG.md:4085

  7529. msgid "2018-11-28"

  7530. msgstr ""

  7531. 

  7532. #: ../../../CHANGELOG.md:4087

  7533. msgid "More scripts"

  7534. msgstr ""

  7535. 

  7536. #: ../../../CHANGELOG.md:4089

  7537. msgid "matrix-remove-all allows to uninstall everything with a single command"

  7538. msgstr ""

  7539. 

  7540. #: ../../../CHANGELOG.md:4090

  7541. msgid "matrix-make-user-admin allows to upgrade a user's privileges"

  7542. msgstr ""

  7543. 

  7544. #: ../../../CHANGELOG.md:4092

  7545. msgid "LDAP auth support via matrix-synapse-ldap3"

  7546. msgstr ""

  7547. 

  7548. #: ../../../CHANGELOG.md:4094

  7549. msgid "The playbook can now install and configure [LDAP auth support](https://github.com/matrix-org/matrix-synapse-ldap3) for you."

  7550. msgstr ""

  7551. 

  7552. #: ../../../CHANGELOG.md:4096

  7553. msgid "Additional details are available in [Setting up the LDAP authentication password provider module](docs/configuring-playbook-ldap-auth.md)."

  7554. msgstr ""

  7555. 

  7556. #: ../../../CHANGELOG.md:4099

  7557. msgid "2018-11-23"

  7558. msgstr ""

  7559. 

  7560. #: ../../../CHANGELOG.md:4101

  7561. msgid "Support for controlling public registration and room auto-join"

  7562. msgstr ""

  7563. 

  7564. #: ../../../CHANGELOG.md:4103

  7565. msgid "The playbook now lets you enable public registration for users (controlled via `matrix_synapse_enable_registration`). By default, public registration is forbidden."

  7566. msgstr ""

  7567. 

  7568. #: ../../../CHANGELOG.md:4105

  7569. msgid "You can also make people automatically get auto-joined to rooms (controlled via `matrix_synapse_auto_join_rooms`)."

  7570. msgstr ""

  7571. 

  7572. #: ../../../CHANGELOG.md:4107

  7573. msgid "Support for changing the welcome user ID (welcome bot)"

  7574. msgstr ""

  7575. 

  7576. #: ../../../CHANGELOG.md:4109

  7577. 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."

  7578. msgstr ""

  7579. 

  7580. #: ../../../CHANGELOG.md:4112

  7581. msgid "2018-11-14"

  7582. msgstr ""

  7583. 

  7584. #: ../../../CHANGELOG.md:4114

  7585. msgid "Ability to set Synapse log levels"

  7586. msgstr ""

  7587. 

  7588. #: ../../../CHANGELOG.md:4116

  7589. msgid "The playbook now allows you to set the log levels used by Synapse. The default logging levels remain the same."

  7590. msgstr ""

  7591. 

  7592. #: ../../../CHANGELOG.md:4118

  7593. 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"

  7594. msgstr ""

  7595. 

  7596. #: ../../../CHANGELOG.md:4127

  7597. msgid "2018-11-03"

  7598. msgstr ""

  7599. 

  7600. #: ../../../CHANGELOG.md:4129

  7601. msgid "Customize parts of Riot's config"

  7602. msgstr ""

  7603. 

  7604. #: ../../../CHANGELOG.md:4131

  7605. msgid "You can now customize some parts of Riot's `config.json`. These playbook variables, with these default values, have been added:"

  7606. msgstr ""

  7607. 

  7608. #: ../../../CHANGELOG.md:4142

  7609. 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:"

  7610. msgstr ""

  7611. 

  7612. #: ../../../CHANGELOG.md:4151

  7613. msgid "SSL protocols used to serve Riot and Synapse"

  7614. msgstr ""

  7615. 

  7616. #: ../../../CHANGELOG.md:4153

  7617. 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."

  7618. msgstr ""

  7619. 

  7620. #: ../../../CHANGELOG.md:4155

  7621. msgid "You may wish to re-enable TLSv1 if you need to access Riot in older browsers."

  7622. msgstr ""

  7623. 

  7624. #: ../../../CHANGELOG.md:4157

  7625. msgid "Note: Currently the dockerized nginx doesn't support TLSv1.3. See https://github.com/nginxinc/docker-nginx/issues/190 for more details."

  7626. msgstr ""

  7627. 

  7628. #: ../../../CHANGELOG.md:4160

  7629. msgid "2018-11-01"

  7630. msgstr ""

  7631. 

  7632. #: ../../../CHANGELOG.md:4162

  7633. msgid "Postgres 11 support"

  7634. msgstr ""

  7635. 

  7636. #: ../../../CHANGELOG.md:4164

  7637. msgid "The playbook now installs [Postgres 11](https://www.postgresql.org/about/news/1894/) by default."

  7638. msgstr ""

  7639. 

  7640. #: ../../../CHANGELOG.md:4166

  7641. 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)."

  7642. msgstr ""

  7643. 

  7644. #: ../../../CHANGELOG.md:4168

  7645. #: ../../../CHANGELOG.md:4255

  7646. #: ../../../CHANGELOG.md:4375

  7647. msgid "(BC Break) Renaming playbook variables"

  7648. msgstr ""

  7649. 

  7650. #: ../../../CHANGELOG.md:4170

  7651. 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."

  7652. msgstr ""

  7653. 

  7654. #: ../../../CHANGELOG.md:4174

  7655. msgid "from `matrix_docker_image_mxisd` to `matrix_mxisd_docker_image`"

  7656. msgstr ""

  7657. 

  7658. #: ../../../CHANGELOG.md:4175

  7659. msgid "from `matrix_docker_image_mautrix_telegram` to `matrix_mautrix_telegram_docker_image`"

  7660. msgstr ""

  7661. 

  7662. #: ../../../CHANGELOG.md:4176

  7663. msgid "from `matrix_docker_image_mautrix_whatsapp` to `matrix_mautrix_whatsapp_docker_image`"

  7664. msgstr ""

  7665. 

  7666. #: ../../../CHANGELOG.md:4177

  7667. msgid "from `matrix_docker_image_mailer` to `matrix_mailer_docker_image`"

  7668. msgstr ""

  7669. 

  7670. #: ../../../CHANGELOG.md:4178

  7671. msgid "from `matrix_docker_image_coturn` to `coturn_container_image`"

  7672. msgstr ""

  7673. 

  7674. #: ../../../CHANGELOG.md:4179

  7675. msgid "from `matrix_docker_image_goofys` to `matrix_s3_goofys_docker_image`"

  7676. msgstr ""

  7677. 

  7678. #: ../../../CHANGELOG.md:4180

  7679. msgid "from `matrix_docker_image_riot` to `matrix_riot_web_docker_image`"

  7680. msgstr ""

  7681. 

  7682. #: ../../../CHANGELOG.md:4181

  7683. msgid "from `matrix_docker_image_nginx` to `matrix_nginx_proxy_docker_image`"

  7684. msgstr ""

  7685. 

  7686. #: ../../../CHANGELOG.md:4182

  7687. msgid "from `matrix_docker_image_synapse` to `matrix_synapse_docker_image`"

  7688. msgstr ""

  7689. 

  7690. #: ../../../CHANGELOG.md:4183

  7691. msgid "from `matrix_docker_image_postgres_v9` to `matrix_postgres_docker_image_v9`"

  7692. msgstr ""

  7693. 

  7694. #: ../../../CHANGELOG.md:4184

  7695. msgid "from `matrix_docker_image_postgres_v10` to `matrix_postgres_docker_image_v10`"

  7696. msgstr ""

  7697. 

  7698. #: ../../../CHANGELOG.md:4185

  7699. msgid "from `matrix_docker_image_postgres_latest` to `matrix_postgres_docker_image_latest`"

  7700. msgstr ""

  7701. 

  7702. #: ../../../CHANGELOG.md:4188

  7703. msgid "2018-10-26"

  7704. msgstr ""

  7705. 

  7706. #: ../../../CHANGELOG.md:4190

  7707. msgid "Mautrix Whatsapp bridging support"

  7708. msgstr ""

  7709. 

  7710. #: ../../../CHANGELOG.md:4192

  7711. 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)."

  7712. msgstr ""

  7713. 

  7714. #: ../../../CHANGELOG.md:4194

  7715. msgid "Additional details are available in [Setting up Mautrix Whatsapp bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)."

  7716. msgstr ""

  7717. 

  7718. #: ../../../CHANGELOG.md:4197

  7719. msgid "2018-10-25"

  7720. msgstr ""

  7721. 

  7722. #: ../../../CHANGELOG.md:4199

  7723. msgid "Support for controlling Matrix federation"

  7724. msgstr ""

  7725. 

  7726. #: ../../../CHANGELOG.md:4201

  7727. 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."

  7728. msgstr ""

  7729. 

  7730. #: ../../../CHANGELOG.md:4204

  7731. msgid "2018-10-24"

  7732. msgstr ""

  7733. 

  7734. #: ../../../CHANGELOG.md:4206

  7735. msgid "Disabling riot-web guests"

  7736. msgstr ""

  7737. 

  7738. #: ../../../CHANGELOG.md:4208

  7739. 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."

  7740. msgstr ""

  7741. 

  7742. #: ../../../CHANGELOG.md:4211

  7743. msgid "2018-10-21"

  7744. msgstr ""

  7745. 

  7746. #: ../../../CHANGELOG.md:4213

  7747. msgid "Self-check maintenance command"

  7748. msgstr ""

  7749. 

  7750. #: ../../../CHANGELOG.md:4215

  7751. msgid "The playbook can now [check if services are configured correctly](docs/maintenance-and-troubleshooting.md#how-to-check-if-services-work)."

  7752. msgstr ""

  7753. 

  7754. #: ../../../CHANGELOG.md:4218

  7755. msgid "2018-10-05"

  7756. msgstr ""

  7757. 

  7758. #: ../../../CHANGELOG.md:4220

  7759. msgid "Presence tracking made configurable"

  7760. msgstr ""

  7761. 

  7762. #: ../../../CHANGELOG.md:4222

  7763. 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)."

  7764. msgstr ""

  7765. 

  7766. #: ../../../CHANGELOG.md:4224

  7767. msgid "If users participate in large rooms with many other servers, disabling presence will decrease server load significantly."

  7768. msgstr ""

  7769. 

  7770. #: ../../../CHANGELOG.md:4227

  7771. msgid "2018-09-27"

  7772. msgstr ""

  7773. 

  7774. #: ../../../CHANGELOG.md:4229

  7775. msgid "Synapse Cache Factor made configurable"

  7776. msgstr ""

  7777. 

  7778. #: ../../../CHANGELOG.md:4231

  7779. 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`)."

  7780. msgstr ""

  7781. 

  7782. #: ../../../CHANGELOG.md:4233

  7783. 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"

  7784. msgstr ""

  7785. 

  7786. #: ../../../CHANGELOG.md:4236

  7787. msgid "2018-09-26"

  7788. msgstr ""

  7789. 

  7790. #: ../../../CHANGELOG.md:4238

  7791. msgid "Disabling Docker container logging"

  7792. msgstr ""

  7793. 

  7794. #: ../../../CHANGELOG.md:4240

  7795. msgid "`--log-driver=none` is used for all Docker containers now."

  7796. msgstr ""

  7797. 

  7798. #: ../../../CHANGELOG.md:4242

  7799. 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."

  7800. msgstr ""

  7801. 

  7802. #: ../../../CHANGELOG.md:4244

  7803. 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."

  7804. msgstr ""

  7805. 

  7806. #: ../../../CHANGELOG.md:4247

  7807. msgid "2018-09-17"

  7808. msgstr ""

  7809. 

  7810. #: ../../../CHANGELOG.md:4249

  7811. msgid "Service discovery support"

  7812. msgstr ""

  7813. 

  7814. #: ../../../CHANGELOG.md:4251

  7815. 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."

  7816. msgstr ""

  7817. 

  7818. #: ../../../CHANGELOG.md:4253

  7819. msgid "Additional details are available in [Configuring service discovery via .well-known](docs/configuring-well-known.md)."

  7820. msgstr ""

  7821. 

  7822. #: ../../../CHANGELOG.md:4259

  7823. msgid "from `matrix_nginx_riot_web_data_path` to `matrix_riot_web_data_path`"

  7824. msgstr ""

  7825. 

  7826. #: ../../../CHANGELOG.md:4260

  7827. msgid "from `matrix_riot_web_default_identity_server_url` to `matrix_identity_server_url`"

  7828. msgstr ""

  7829. 

  7830. #: ../../../CHANGELOG.md:4263

  7831. msgid "2018-09-07"

  7832. msgstr ""

  7833. 

  7834. #: ../../../CHANGELOG.md:4265

  7835. msgid "Mautrix Telegram bridging support"

  7836. msgstr ""

  7837. 

  7838. #: ../../../CHANGELOG.md:4267

  7839. 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)."

  7840. msgstr ""

  7841. 

  7842. #: ../../../CHANGELOG.md:4269

  7843. msgid "Additional details are available in [Setting up Mautrix Telegram bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)."

  7844. msgstr ""

  7845. 

  7846. #: ../../../CHANGELOG.md:4271

  7847. msgid "Events cache size increase and configurability for Matrix Synapse"

  7848. msgstr ""

  7849. 

  7850. #: ../../../CHANGELOG.md:4273

  7851. msgid "The playbook now lets you configure Matrix Synapse's `event_cache_size` configuration via the `matrix_synapse_event_cache_size` playbook variable."

  7852. msgstr ""

  7853. 

  7854. #: ../../../CHANGELOG.md:4275

  7855. msgid "Previously, this value was hardcoded to `\"10K\"`. From now on, a more reasonable default of `\"100K\"` is used."

  7856. msgstr ""

  7857. 

  7858. #: ../../../CHANGELOG.md:4277

  7859. msgid "Password-peppering support for Matrix Synapse"

  7860. msgstr ""

  7861. 

  7862. #: ../../../CHANGELOG.md:4279

  7863. 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."

  7864. msgstr ""

  7865. 

  7866. #: ../../../CHANGELOG.md:4281

  7867. msgid "Statistics-reporting support for Matrix Synapse"

  7868. msgstr ""

  7869. 

  7870. #: ../../../CHANGELOG.md:4283

  7871. 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."

  7872. msgstr ""

  7873. 

  7874. #: ../../../CHANGELOG.md:4285

  7875. 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."

  7876. msgstr ""

  7877. 

  7878. #: ../../../CHANGELOG.md:4288

  7879. msgid "2018-08-29"

  7880. msgstr ""

  7881. 

  7882. #: ../../../CHANGELOG.md:4290

  7883. msgid "Changing the way SSL certificates are retrieved"

  7884. msgstr ""

  7885. 

  7886. #: ../../../CHANGELOG.md:4292

  7887. 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."

  7888. msgstr ""

  7889. 

  7890. #: ../../../CHANGELOG.md:4294

  7891. 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)."

  7892. msgstr ""

  7893. 

  7894. #: ../../../CHANGELOG.md:4296

  7895. 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:"

  7896. msgstr ""

  7897. 

  7898. #: ../../../CHANGELOG.md:4298

  7899. msgid "`systemctl stop 'matrix*'`"

  7900. msgstr ""

  7901. 

  7902. #: ../../../CHANGELOG.md:4299

  7903. msgid "stop your custom webserver, if you're running one (only affects you if you've installed with `matrix_nginx_proxy_enabled: false`)"

  7904. msgstr ""

  7905. 

  7906. #: ../../../CHANGELOG.md:4300

  7907. msgid "`mv /matrix/ssl /matrix/ssl-acmetool-delete-later`"

  7908. msgstr ""

  7909. 

  7910. #: ../../../CHANGELOG.md:4301

  7911. msgid "re-run the playbook's [installation](docs/installing.md)"

  7912. msgstr ""

  7913. 

  7914. #: ../../../CHANGELOG.md:4302

  7915. msgid "possibly delete `/matrix/ssl-acmetool-delete-later`"

  7916. msgstr ""

  7917. 

  7918. #: ../../../CHANGELOG.md:4305

  7919. msgid "2018-08-21"

  7920. msgstr ""

  7921. 

  7922. #: ../../../CHANGELOG.md:4307

  7923. msgid "Matrix Corporal support"

  7924. msgstr ""

  7925. 

  7926. #: ../../../CHANGELOG.md:4309

  7927. msgid "The playbook can now install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you."

  7928. msgstr ""

  7929. 

  7930. #: ../../../CHANGELOG.md:4311

  7931. msgid "Additional details are available in [Setting up Matrix Corporal](docs/configuring-playbook-matrix-corporal.md)."

  7932. msgstr ""

  7933. 

  7934. #: ../../../CHANGELOG.md:4314

  7935. msgid "2018-08-20"

  7936. msgstr ""

  7937. 

  7938. #: ../../../CHANGELOG.md:4316

  7939. msgid "Matrix Synapse rate limit control variables"

  7940. msgstr ""

  7941. 

  7942. #: ../../../CHANGELOG.md:4318

  7943. msgid "The following new variables can now be configured to control Matrix Synapse's rate-limiting (default values are shown below)."

  7944. msgstr ""

  7945. 

  7946. #: ../../../CHANGELOG.md:4325

  7947. msgid "Shared Secret Auth support via matrix-synapse-shared-secret-auth"

  7948. msgstr ""

  7949. 

  7950. #: ../../../CHANGELOG.md:4327

  7951. msgid "The playbook can now install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you."

  7952. msgstr ""

  7953. 

  7954. #: ../../../CHANGELOG.md:4329

  7955. msgid "Additional details are available in [Setting up the Shared Secret Auth password provider module](docs/configuring-playbook-shared-secret-auth.md)."

  7956. msgstr ""

  7957. 

  7958. #: ../../../CHANGELOG.md:4332

  7959. msgid "2018-08-17"

  7960. msgstr ""

  7961. 

  7962. #: ../../../CHANGELOG.md:4334

  7963. msgid "REST auth support via matrix-synapse-rest-auth"

  7964. msgstr ""

  7965. 

  7966. #: ../../../CHANGELOG.md:4336

  7967. msgid "The playbook can now install and configure [matrix-synapse-rest-auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you."

  7968. msgstr ""

  7969. 

  7970. #: ../../../CHANGELOG.md:4338

  7971. msgid "Additional details are available in [Setting up the REST authentication password provider module](docs/configuring-playbook-rest-auth.md)."

  7972. msgstr ""

  7973. 

  7974. #: ../../../CHANGELOG.md:4340

  7975. msgid "Compression improvements"

  7976. msgstr ""

  7977. 

  7978. #: ../../../CHANGELOG.md:4342

  7979. msgid "Shifted Matrix Synapse compression from happening in the Matrix Synapse, to happening in the nginx proxy that's in front of it."

  7980. msgstr ""

  7981. 

  7982. #: ../../../CHANGELOG.md:4345

  7983. 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."

  7984. msgstr ""

  7985. 

  7986. #: ../../../CHANGELOG.md:4348

  7987. msgid "Disabling some unnecessary Synapse services"

  7988. msgstr ""

  7989. 

  7990. #: ../../../CHANGELOG.md:4350

  7991. msgid "The following services are not necessary, so they have been disabled:"

  7992. msgstr ""

  7993. 

  7994. #: ../../../CHANGELOG.md:4351

  7995. msgid "on the federation port (8448): the `client` service"

  7996. msgstr ""

  7997. 

  7998. #: ../../../CHANGELOG.md:4352

  7999. msgid "on the http port (8008, exposed over 443): the old Angular `webclient` and the `federation` service"

  8000. msgstr ""

  8001. 

  8002. #: ../../../CHANGELOG.md:4354

  8003. msgid "Federation runs only on the federation port (8448) now. The Client APIs run only on the http port (8008) now."

  8004. msgstr ""

  8005. 

  8006. #: ../../../CHANGELOG.md:4357

  8007. msgid "2018-08-15"

  8008. msgstr ""

  8009. 

  8010. #: ../../../CHANGELOG.md:4359

  8011. msgid "mxisd Identity Server support"

  8012. msgstr ""

  8013. 

  8014. #: ../../../CHANGELOG.md:4361

  8015. 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)."

  8016. msgstr ""

  8017. 

  8018. #: ../../../CHANGELOG.md:4364

  8019. msgid "2018-08-14"

  8020. msgstr ""

  8021. 

  8022. #: ../../../CHANGELOG.md:4366

  8023. msgid "Email-sending support"

  8024. msgstr ""

  8025. 

  8026. #: ../../../CHANGELOG.md:4368

  8027. 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)."

  8028. msgstr ""

  8029. 

  8030. #: ../../../CHANGELOG.md:4370

  8031. msgid "With this, Matrix Synapse is able to send email notifications for missed messages, etc."

  8032. msgstr ""

  8033. 

  8034. #: ../../../CHANGELOG.md:4373

  8035. msgid "2018-08-08"

  8036. msgstr ""

  8037. 

  8038. #: ../../../CHANGELOG.md:4379

  8039. msgid "from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`"

  8040. msgstr ""

  8041. 

  8042. #: ../../../CHANGELOG.md:4380

  8043. msgid "from `matrix_max_log_file_size_mb` to `matrix_synapse_max_log_file_size_mb`"

  8044. msgstr ""

  8045. 

  8046. #: ../../../CHANGELOG.md:4381

  8047. msgid "from `matrix_max_log_files_count` to `matrix_synapse_max_log_files_count`"

  8048. msgstr ""

  8049. 

  8050. #: ../../../CHANGELOG.md:4382

  8051. msgid "from `docker_matrix_image` to `matrix_docker_image_synapse`"

  8052. msgstr ""

  8053. 

  8054. #: ../../../CHANGELOG.md:4383

  8055. msgid "from `docker_nginx_image` to `matrix_docker_image_nginx`"

  8056. msgstr ""

  8057. 

  8058. #: ../../../CHANGELOG.md:4384

  8059. msgid "from `docker_riot_image` to `matrix_docker_image_riot`"

  8060. msgstr ""

  8061. 

  8062. #: ../../../CHANGELOG.md:4385

  8063. msgid "from `docker_goofys_image` to `matrix_docker_image_goofys`"

  8064. msgstr ""

  8065. 

  8066. #: ../../../CHANGELOG.md:4386

  8067. msgid "from `docker_coturn_image` to `matrix_docker_image_coturn`"

  8068. msgstr ""

  8069. 

  8070. #: ../../../CHANGELOG.md:4388

  8071. msgid "If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names."

  8072. msgstr ""

  8073. 

  8074. #: ../../../CHANGELOG.md:4390

  8075. msgid "Renaming Ansible playbook tag"

  8076. msgstr ""

  8077. 

  8078. #: ../../../CHANGELOG.md:4392

  8079. msgid "The command for executing the whole playbook has changed. The `setup-main` tag got renamed to `setup-all`."

  8080. msgstr ""

  8081. 

  8082. #: ../../../CHANGELOG.md:4394

  8083. msgid "Docker container linking"

  8084. msgstr ""

  8085. 

  8086. #: ../../../CHANGELOG.md:4396

  8087. 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."

  8088. msgstr ""