overmind
/
matrix-docker-ansible-deploy
zrcadlo https://github.com/spantaleev/matrix-docker-ansible-deploy
1
0
Rozštěpit 0
Zdrojový kód Úkoly 0 Vydání 0 Wiki Aktivita
Matrix Docker Ansible eploy
Nelze vybrat více než 25 témat Téma musí začínat písmenem nebo číslem, může obsahovat pomlčky („-“) a může být dlouhé až 35 znaků.
11135 Revize
12 Větve
702 MiB
 
 
Strom: f8a820212b
Větve Značky
${ item.name }
Vytvořit větev ${ searchTerm }
z „f8a820212b“
${ noResults }
matrix-docker-ansible-deploy/i18n/translation-templates/CHANGELOG.pot

8242 řádky
407 KiB
Surový Blame Historie 

  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-04-03 11:56+0100\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-04-03"

  21. msgstr ""

  22. 

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

  24. msgid "(BC Break) Synapse Admin is now Ketesa"

  25. msgstr ""

  26. 

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

  28. msgid "Synapse Admin has been rebranded to **[Ketesa](https://github.com/etkecc/ketesa)** — a landmark release that introduces a new identity, a full UI redesign, mobile-first layout, and deep Matrix Authentication Service (MAS) integration."

  29. msgstr ""

  30. 

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

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

  33. msgstr ""

  34. 

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

  36. msgid "The `matrix-synapse-admin` role has been **renamed** to `matrix-ketesa`. All `matrix_synapse_admin_*` variables must be **renamed** to `matrix_ketesa_*` in your `vars.yml`."

  37. msgstr ""

  38. 

  39. #: ../../../CHANGELOG.md:11

  40. msgid "Additionally, the **Docker image** changed from `ghcr.io/etkecc/synapse-admin` to `ghcr.io/etkecc/ketesa`. The default path prefix remains `/synapse-admin` for backward compatibility — updating to `/ketesa` is recommended but not required."

  41. msgstr ""

  42. 

  43. #: ../../../CHANGELOG.md:13

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

  45. msgstr ""

  46. 

  47. #: ../../../CHANGELOG.md:15

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

  49. msgstr ""

  50. 

  51. #: ../../../CHANGELOG.md:17

  52. msgid "2026-04-02"

  53. msgstr ""

  54. 

  55. #: ../../../CHANGELOG.md:19

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

  57. msgstr ""

  58. 

  59. #: ../../../CHANGELOG.md:21

  60. msgid "💡 If you don't use [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md), then this breaking change does not concern you.."

  61. msgstr ""

  62. 

  63. #: ../../../CHANGELOG.md:23

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

  65. msgstr ""

  66. 

  67. #: ../../../CHANGELOG.md:25

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

  69. msgstr ""

  70. 

  71. #: ../../../CHANGELOG.md:27

  72. msgid "Manual provisioning by administrators is now the recommended approach. You do not want to enable Self Service Provisioning unless you have additional custom safeguards like those used by asgard.chat in place."

  73. msgstr ""

  74. 

  75. #: ../../../CHANGELOG.md:29

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

  77. msgstr ""

  78. 

  79. #: ../../../CHANGELOG.md:36

  80. msgid "2026-03-23"

  81. msgstr ""

  82. 

  83. #: ../../../CHANGELOG.md:38

  84. msgid "Migration validation system introduced"

  85. msgstr ""

  86. 

  87. #: ../../../CHANGELOG.md:40

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

  89. msgstr ""

  90. 

  91. #: ../../../CHANGELOG.md:42

  92. msgid "Now, the playbook includes a migration validation system that ensures you're aware of breaking changes before they affect your deployment. You're now forced to acknowledge each breaking change, unless you wish to live dangerously (see below)."

  93. msgstr ""

  94. 

  95. #: ../../../CHANGELOG.md:45

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

  97. msgstr ""

  98. 

  99. #: ../../../CHANGELOG.md:47

  100. msgid "**New users** who started from the [example `vars.yml`](examples/vars.yml) file already have this variable set and do not need to do anything."

  101. msgstr ""

  102. 

  103. #: ../../../CHANGELOG.md:49

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

  105. msgstr ""

  106. 

  107. #: ../../../CHANGELOG.md:55

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

  109. msgstr ""

  110. 

  111. #: ../../../CHANGELOG.md:57

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

  113. msgstr ""

  114. 

  115. #: ../../../CHANGELOG.md:59

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

  117. msgstr ""

  118. 

  119. #: ../../../CHANGELOG.md:61

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

  121. msgstr ""

  122. 

  123. #: ../../../CHANGELOG.md:63

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

  125. msgstr ""

  126. 

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

  128. msgid "2026-03-19"

  129. msgstr ""

  130. 

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

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

  133. msgstr ""

  134. 

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

  136. msgid "When [Matrix Authentication Service](docs/configuring-playbook-matrix-authentication-service.md) (MAS) uses the playbook-managed Postgres service, it now connects to it via a [UNIX socket](https://en.wikipedia.org/wiki/Unix_domain_socket) by default instead of TCP."

  137. msgstr ""

  138. 

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

  140. msgid "This follows the same approach [applied to Synapse](#synapse-now-prefers-unix-sockets-for-playbook-managed-postgres-and-valkey) and reduces unnecessary container-network wiring, keeping local IPC off the network stack."

  141. msgstr ""

  142. 

  143. #: ../../../CHANGELOG.md:77

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

  145. msgstr ""

  146. 

  147. #: ../../../CHANGELOG.md:79

  148. #: ../../../CHANGELOG.md:95

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

  150. msgstr ""

  151. 

  152. #: ../../../CHANGELOG.md:85

  153. msgid "2026-03-17"

  154. msgstr ""

  155. 

  156. #: ../../../CHANGELOG.md:87

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

  158. msgstr ""

  159. 

  160. #: ../../../CHANGELOG.md:89

  161. msgid "When Synapse uses the playbook-managed Postgres and Valkey services, it now connects to them via [UNIX sockets](https://en.wikipedia.org/wiki/Unix_domain_socket) by default instead of TCP."

  162. msgstr ""

  163. 

  164. #: ../../../CHANGELOG.md:91

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

  166. msgstr ""

  167. 

  168. #: ../../../CHANGELOG.md:93

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

  170. msgstr ""

  171. 

  172. #: ../../../CHANGELOG.md:102

  173. msgid "2026-03-01"

  174. msgstr ""

  175. 

  176. #: ../../../CHANGELOG.md:104

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

  178. msgstr ""

  179. 

  180. #: ../../../CHANGELOG.md:106

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

  182. msgstr ""

  183. 

  184. #: ../../../CHANGELOG.md:108

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

  186. msgstr ""

  187. 

  188. #: ../../../CHANGELOG.md:109

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

  190. msgstr ""

  191. 

  192. #: ../../../CHANGELOG.md:111

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

  194. msgstr ""

  195. 

  196. #: ../../../CHANGELOG.md:113

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

  198. msgstr ""

  199. 

  200. #: ../../../CHANGELOG.md:115

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

  202. msgstr ""

  203. 

  204. #: ../../../CHANGELOG.md:117

  205. msgid "2026-02-26"

  206. msgstr ""

  207. 

  208. #: ../../../CHANGELOG.md:119

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

  210. msgstr ""

  211. 

  212. #: ../../../CHANGELOG.md:121

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

  214. msgstr ""

  215. 

  216. #: ../../../CHANGELOG.md:123

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

  218. msgstr ""

  219. 

  220. #: ../../../CHANGELOG.md:125

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

  222. msgstr ""

  223. 

  224. #: ../../../CHANGELOG.md:127

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

  226. msgstr ""

  227. 

  228. #: ../../../CHANGELOG.md:129

  229. msgid "2026-02-21"

  230. msgstr ""

  231. 

  232. #: ../../../CHANGELOG.md:131

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

  234. msgstr ""

  235. 

  236. #: ../../../CHANGELOG.md:133

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

  238. msgstr ""

  239. 

  240. #: ../../../CHANGELOG.md:135

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

  242. msgstr ""

  243. 

  244. #: ../../../CHANGELOG.md:137

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

  246. msgstr ""

  247. 

  248. #: ../../../CHANGELOG.md:138

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

  250. msgstr ""

  251. 

  252. #: ../../../CHANGELOG.md:140

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

  254. msgstr ""

  255. 

  256. #: ../../../CHANGELOG.md:142

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

  258. msgstr ""

  259. 

  260. #: ../../../CHANGELOG.md:144

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

  262. msgstr ""

  263. 

  264. #: ../../../CHANGELOG.md:153

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

  266. msgstr ""

  267. 

  268. #: ../../../CHANGELOG.md:155

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

  270. msgstr ""

  271. 

  272. #: ../../../CHANGELOG.md:157

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

  274. msgstr ""

  275. 

  276. #: ../../../CHANGELOG.md:159

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

  278. msgstr ""

  279. 

  280. #: ../../../CHANGELOG.md:161

  281. msgid "2026-02-17"

  282. msgstr ""

  283. 

  284. #: ../../../CHANGELOG.md:163

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

  286. msgstr ""

  287. 

  288. #: ../../../CHANGELOG.md:165

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

  290. msgstr ""

  291. 

  292. #: ../../../CHANGELOG.md:167

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

  294. msgstr ""

  295. 

  296. #: ../../../CHANGELOG.md:169

  297. #: ../../../CHANGELOG.md:231

  298. #: ../../../CHANGELOG.md:241

  299. #: ../../../CHANGELOG.md:302

  300. #: ../../../CHANGELOG.md:324

  301. #: ../../../CHANGELOG.md:859

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

  303. msgstr ""

  304. 

  305. #: ../../../CHANGELOG.md:171

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

  307. msgstr ""

  308. 

  309. #: ../../../CHANGELOG.md:173

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

  311. msgstr ""

  312. 

  313. #: ../../../CHANGELOG.md:175

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

  315. msgstr ""

  316. 

  317. #: ../../../CHANGELOG.md:177

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

  319. msgstr ""

  320. 

  321. #: ../../../CHANGELOG.md:179

  322. msgid "2026-02-16"

  323. msgstr ""

  324. 

  325. #: ../../../CHANGELOG.md:181

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

  327. msgstr ""

  328. 

  329. #: ../../../CHANGELOG.md:183

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

  331. msgstr ""

  332. 

  333. #: ../../../CHANGELOG.md:185

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

  335. msgstr ""

  336. 

  337. #: ../../../CHANGELOG.md:187

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

  339. msgstr ""

  340. 

  341. #: ../../../CHANGELOG.md:189

  342. msgid "2026-02-13"

  343. msgstr ""

  344. 

  345. #: ../../../CHANGELOG.md:191

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

  347. msgstr ""

  348. 

  349. #: ../../../CHANGELOG.md:193

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

  351. msgstr ""

  352. 

  353. #: ../../../CHANGELOG.md:195

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

  355. msgstr ""

  356. 

  357. #: ../../../CHANGELOG.md:197

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

  359. msgstr ""

  360. 

  361. #: ../../../CHANGELOG.md:199

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

  363. msgstr ""

  364. 

  365. #: ../../../CHANGELOG.md:201

  366. msgid "**Before**:"

  367. msgstr ""

  368. 

  369. #: ../../../CHANGELOG.md:202

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

  371. msgstr ""

  372. 

  373. #: ../../../CHANGELOG.md:203

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

  375. msgstr ""

  376. 

  377. #: ../../../CHANGELOG.md:204

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

  379. msgstr ""

  380. 

  381. #: ../../../CHANGELOG.md:205

  382. msgid "**After**:"

  383. msgstr ""

  384. 

  385. #: ../../../CHANGELOG.md:206

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

  387. msgstr ""

  388. 

  389. #: ../../../CHANGELOG.md:207

  390. msgid "Traefik restarted: no ✅"

  391. msgstr ""

  392. 

  393. #: ../../../CHANGELOG.md:208

  394. msgid "dependent services restarted: no ✅"

  395. msgstr ""

  396. 

  397. #: ../../../CHANGELOG.md:210

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

  399. msgstr ""

  400. 

  401. #: ../../../CHANGELOG.md:213

  402. msgid "2026-02-12"

  403. msgstr ""

  404. 

  405. #: ../../../CHANGELOG.md:215

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

  407. msgstr ""

  408. 

  409. #: ../../../CHANGELOG.md:217

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

  411. msgstr ""

  412. 

  413. #: ../../../CHANGELOG.md:219

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

  415. msgstr ""

  416. 

  417. #: ../../../CHANGELOG.md:221

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

  419. msgstr ""

  420. 

  421. #: ../../../CHANGELOG.md:223

  422. msgid "The role for Hydrogen 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:225

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

  427. msgstr ""

  428. 

  429. #: ../../../CHANGELOG.md:227

  430. #: ../../../CHANGELOG.md:320

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

  432. msgstr ""

  433. 

  434. #: ../../../CHANGELOG.md:229

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

  436. msgstr ""

  437. 

  438. #: ../../../CHANGELOG.md:233

  439. msgid "2026-02-11"

  440. msgstr ""

  441. 

  442. #: ../../../CHANGELOG.md:235

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

  444. msgstr ""

  445. 

  446. #: ../../../CHANGELOG.md:237

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

  448. msgstr ""

  449. 

  450. #: ../../../CHANGELOG.md:239

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

  452. msgstr ""

  453. 

  454. #: ../../../CHANGELOG.md:243

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

  456. msgstr ""

  457. 

  458. #: ../../../CHANGELOG.md:245

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

  460. msgstr ""

  461. 

  462. #: ../../../CHANGELOG.md:247

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

  464. msgstr ""

  465. 

  466. #: ../../../CHANGELOG.md:249

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

  468. msgstr ""

  469. 

  470. #: ../../../CHANGELOG.md:251

  471. msgid "2026-02-09"

  472. msgstr ""

  473. 

  474. #: ../../../CHANGELOG.md:253

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

  476. msgstr ""

  477. 

  478. #: ../../../CHANGELOG.md:255

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

  480. msgstr ""

  481. 

  482. #: ../../../CHANGELOG.md:257

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

  484. msgstr ""

  485. 

  486. #: ../../../CHANGELOG.md:259

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

  488. msgstr ""

  489. 

  490. #: ../../../CHANGELOG.md:261

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

  492. msgstr ""

  493. 

  494. #: ../../../CHANGELOG.md:267

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

  496. msgstr ""

  497. 

  498. #: ../../../CHANGELOG.md:276

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

  500. msgstr ""

  501. 

  502. #: ../../../CHANGELOG.md:278

  503. msgid "2026-02-08"

  504. msgstr ""

  505. 

  506. #: ../../../CHANGELOG.md:280

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

  508. msgstr ""

  509. 

  510. #: ../../../CHANGELOG.md:282

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

  512. msgstr ""

  513. 

  514. #: ../../../CHANGELOG.md:284

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

  516. msgstr ""

  517. 

  518. #: ../../../CHANGELOG.md:286

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

  520. msgstr ""

  521. 

  522. #: ../../../CHANGELOG.md:288

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

  524. msgstr ""

  525. 

  526. #: ../../../CHANGELOG.md:290

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

  528. msgstr ""

  529. 

  530. #: ../../../CHANGELOG.md:292

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

  532. msgstr ""

  533. 

  534. #: ../../../CHANGELOG.md:294

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

  536. msgstr ""

  537. 

  538. #: ../../../CHANGELOG.md:296

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

  540. msgstr ""

  541. 

  542. #: ../../../CHANGELOG.md:298

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

  544. msgstr ""

  545. 

  546. #: ../../../CHANGELOG.md:300

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

  548. msgstr ""

  549. 

  550. #: ../../../CHANGELOG.md:304

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

  552. msgstr ""

  553. 

  554. #: ../../../CHANGELOG.md:306

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

  556. msgstr ""

  557. 

  558. #: ../../../CHANGELOG.md:308

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

  560. msgstr ""

  561. 

  562. #: ../../../CHANGELOG.md:310

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

  564. msgstr ""

  565. 

  566. #: ../../../CHANGELOG.md:312

  567. msgid "2026-02-07"

  568. msgstr ""

  569. 

  570. #: ../../../CHANGELOG.md:314

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

  572. msgstr ""

  573. 

  574. #: ../../../CHANGELOG.md:316

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

  576. msgstr ""

  577. 

  578. #: ../../../CHANGELOG.md:318

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

  580. msgstr ""

  581. 

  582. #: ../../../CHANGELOG.md:322

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

  584. msgstr ""

  585. 

  586. #: ../../../CHANGELOG.md:326

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

  588. msgstr ""

  589. 

  590. #: ../../../CHANGELOG.md:328

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

  592. msgstr ""

  593. 

  594. #: ../../../CHANGELOG.md:330

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

  596. msgstr ""

  597. 

  598. #: ../../../CHANGELOG.md:332

  599. msgid "2026-02-04"

  600. msgstr ""

  601. 

  602. #: ../../../CHANGELOG.md:334

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

  604. msgstr ""

  605. 

  606. #: ../../../CHANGELOG.md:336

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

  608. msgstr ""

  609. 

  610. #: ../../../CHANGELOG.md:338

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

  612. msgstr ""

  613. 

  614. #: ../../../CHANGELOG.md:345

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

  616. msgstr ""

  617. 

  618. #: ../../../CHANGELOG.md:347

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

  620. msgstr ""

  621. 

  622. #: ../../../CHANGELOG.md:349

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

  624. msgstr ""

  625. 

  626. #: ../../../CHANGELOG.md:351

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

  628. msgstr ""

  629. 

  630. #: ../../../CHANGELOG.md:353

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

  632. msgstr ""

  633. 

  634. #: ../../../CHANGELOG.md:355

  635. msgid "This change:"

  636. msgstr ""

  637. 

  638. #: ../../../CHANGELOG.md:356

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

  640. msgstr ""

  641. 

  642. #: ../../../CHANGELOG.md:357

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

  644. msgstr ""

  645. 

  646. #: ../../../CHANGELOG.md:358

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

  648. msgstr ""

  649. 

  650. #: ../../../CHANGELOG.md:359

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

  652. msgstr ""

  653. 

  654. #: ../../../CHANGELOG.md:361

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

  656. msgstr ""

  657. 

  658. #: ../../../CHANGELOG.md:372

  659. msgid "2025-12-09"

  660. msgstr ""

  661. 

  662. #: ../../../CHANGELOG.md:374

  663. msgid "Traefik Cert Dumper upgrade"

  664. msgstr ""

  665. 

  666. #: ../../../CHANGELOG.md:376

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

  668. msgstr ""

  669. 

  670. #: ../../../CHANGELOG.md:378

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

  672. msgstr ""

  673. 

  674. #: ../../../CHANGELOG.md:380

  675. msgid "2025-11-23"

  676. msgstr ""

  677. 

  678. #: ../../../CHANGELOG.md:382

  679. msgid "Matrix.to support"

  680. msgstr ""

  681. 

  682. #: ../../../CHANGELOG.md:384

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

  684. msgstr ""

  685. 

  686. #: ../../../CHANGELOG.md:386

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

  688. msgstr ""

  689. 

  690. #: ../../../CHANGELOG.md:388

  691. msgid "2025-11-09"

  692. msgstr ""

  693. 

  694. #: ../../../CHANGELOG.md:390

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

  696. msgstr ""

  697. 

  698. #: ../../../CHANGELOG.md:392

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

  700. msgstr ""

  701. 

  702. #: ../../../CHANGELOG.md:394

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

  704. msgstr ""

  705. 

  706. #: ../../../CHANGELOG.md:396

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

  708. msgstr ""

  709. 

  710. #: ../../../CHANGELOG.md:398

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

  712. msgstr ""

  713. 

  714. #: ../../../CHANGELOG.md:400

  715. #: ../../../CHANGELOG.md:432

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

  717. msgstr ""

  718. 

  719. #: ../../../CHANGELOG.md:402

  720. msgid "`matrix_mautrix_facebook_*`"

  721. msgstr ""

  722. 

  723. #: ../../../CHANGELOG.md:403

  724. msgid "`matrix_mautrix_instagram_*`"

  725. msgstr ""

  726. 

  727. #: ../../../CHANGELOG.md:405

  728. #: ../../../CHANGELOG.md:439

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

  730. msgstr ""

  731. 

  732. #: ../../../CHANGELOG.md:407

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

  734. msgstr ""

  735. 

  736. #: ../../../CHANGELOG.md:408

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

  738. msgstr ""

  739. 

  740. #: ../../../CHANGELOG.md:410

  741. msgid "2025-11-08"

  742. msgstr ""

  743. 

  744. #: ../../../CHANGELOG.md:412

  745. msgid "MatrixZulipBridge support"

  746. msgstr ""

  747. 

  748. #: ../../../CHANGELOG.md:414

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

  750. msgstr ""

  751. 

  752. #: ../../../CHANGELOG.md:416

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

  754. msgstr ""

  755. 

  756. #: ../../../CHANGELOG.md:418

  757. msgid "2025-11-07"

  758. msgstr ""

  759. 

  760. #: ../../../CHANGELOG.md:420

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

  762. msgstr ""

  763. 

  764. #: ../../../CHANGELOG.md:422

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

  766. msgstr ""

  767. 

  768. #: ../../../CHANGELOG.md:424

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

  770. msgstr ""

  771. 

  772. #: ../../../CHANGELOG.md:426

  773. msgid "2025-11-05"

  774. msgstr ""

  775. 

  776. #: ../../../CHANGELOG.md:428

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

  778. msgstr ""

  779. 

  780. #: ../../../CHANGELOG.md:430

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

  782. msgstr ""

  783. 

  784. #: ../../../CHANGELOG.md:434

  785. msgid "`matrix_mx_puppet_discord_*`"

  786. msgstr ""

  787. 

  788. #: ../../../CHANGELOG.md:435

  789. msgid "`matrix_mx_puppet_instagram_*`"

  790. msgstr ""

  791. 

  792. #: ../../../CHANGELOG.md:436

  793. msgid "`matrix_mx_puppet_slack_*`"

  794. msgstr ""

  795. 

  796. #: ../../../CHANGELOG.md:437

  797. msgid "`matrix_mx_puppet_twitter_*`"

  798. msgstr ""

  799. 

  800. #: ../../../CHANGELOG.md:441

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

  802. msgstr ""

  803. 

  804. #: ../../../CHANGELOG.md:442

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

  806. msgstr ""

  807. 

  808. #: ../../../CHANGELOG.md:443

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

  810. msgstr ""

  811. 

  812. #: ../../../CHANGELOG.md:444

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

  814. msgstr ""

  815. 

  816. #: ../../../CHANGELOG.md:446

  817. msgid "2025-11-04"

  818. msgstr ""

  819. 

  820. #: ../../../CHANGELOG.md:448

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

  822. msgstr ""

  823. 

  824. #: ../../../CHANGELOG.md:450

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

  826. msgstr ""

  827. 

  828. #: ../../../CHANGELOG.md:452

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

  830. msgstr ""

  831. 

  832. #: ../../../CHANGELOG.md:454

  833. msgid "2025-10-02"

  834. msgstr ""

  835. 

  836. #: ../../../CHANGELOG.md:456

  837. msgid "Element Admin support"

  838. msgstr ""

  839. 

  840. #: ../../../CHANGELOG.md:458

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

  842. msgstr ""

  843. 

  844. #: ../../../CHANGELOG.md:460

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

  846. msgstr ""

  847. 

  848. #: ../../../CHANGELOG.md:462

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

  850. msgstr ""

  851. 

  852. #: ../../../CHANGELOG.md:465

  853. msgid "2025-04-26"

  854. msgstr ""

  855. 

  856. #: ../../../CHANGELOG.md:467

  857. msgid "Continuwuity support"

  858. msgstr ""

  859. 

  860. #: ../../../CHANGELOG.md:469

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

  862. msgstr ""

  863. 

  864. #: ../../../CHANGELOG.md:471

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

  866. msgstr ""

  867. 

  868. #: ../../../CHANGELOG.md:473

  869. #: ../../../CHANGELOG.md:686

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

  871. msgstr ""

  872. 

  873. #: ../../../CHANGELOG.md:475

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

  875. msgstr ""

  876. 

  877. #: ../../../CHANGELOG.md:477

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

  879. msgstr ""

  880. 

  881. #: ../../../CHANGELOG.md:478

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

  883. msgstr ""

  884. 

  885. #: ../../../CHANGELOG.md:480

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

  887. msgstr ""

  888. 

  889. #: ../../../CHANGELOG.md:483

  890. msgid "2025-04-09"

  891. msgstr ""

  892. 

  893. #: ../../../CHANGELOG.md:485

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

  895. msgstr ""

  896. 

  897. #: ../../../CHANGELOG.md:487

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

  899. msgstr ""

  900. 

  901. #: ../../../CHANGELOG.md:489

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

  903. msgstr ""

  904. 

  905. #: ../../../CHANGELOG.md:491

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

  907. msgstr ""

  908. 

  909. #: ../../../CHANGELOG.md:493

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

  911. msgstr ""

  912. 

  913. #: ../../../CHANGELOG.md:495

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

  915. msgstr ""

  916. 

  917. #: ../../../CHANGELOG.md:502

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

  919. msgstr ""

  920. 

  921. #: ../../../CHANGELOG.md:504

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

  923. msgstr ""

  924. 

  925. #: ../../../CHANGELOG.md:507

  926. msgid "2025-03-15"

  927. msgstr ""

  928. 

  929. #: ../../../CHANGELOG.md:509

  930. msgid "Element Call support"

  931. msgstr ""

  932. 

  933. #: ../../../CHANGELOG.md:511

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

  935. msgstr ""

  936. 

  937. #: ../../../CHANGELOG.md:513

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

  939. msgstr ""

  940. 

  941. #: ../../../CHANGELOG.md:515

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

  943. msgstr ""

  944. 

  945. #: ../../../CHANGELOG.md:517

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

  947. msgstr ""

  948. 

  949. #: ../../../CHANGELOG.md:520

  950. msgid "2025-03-08"

  951. msgstr ""

  952. 

  953. #: ../../../CHANGELOG.md:522

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

  955. msgstr ""

  956. 

  957. #: ../../../CHANGELOG.md:524

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

  959. msgstr ""

  960. 

  961. #: ../../../CHANGELOG.md:526

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

  963. msgstr ""

  964. 

  965. #: ../../../CHANGELOG.md:528

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

  967. msgstr ""

  968. 

  969. #: ../../../CHANGELOG.md:530

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

  971. msgstr ""

  972. 

  973. #: ../../../CHANGELOG.md:531

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

  975. msgstr ""

  976. 

  977. #: ../../../CHANGELOG.md:532

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

  979. msgstr ""

  980. 

  981. #: ../../../CHANGELOG.md:533

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

  983. msgstr ""

  984. 

  985. #: ../../../CHANGELOG.md:534

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

  987. msgstr ""

  988. 

  989. #: ../../../CHANGELOG.md:536

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

  991. msgstr ""

  992. 

  993. #: ../../../CHANGELOG.md:538

  994. msgid "2025-02-26"

  995. msgstr ""

  996. 

  997. #: ../../../CHANGELOG.md:540

  998. msgid "🪦 Bye-bye, Email2Matrix"

  999. msgstr ""

  1000. 

  1001. #: ../../../CHANGELOG.md:542

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

  1003. msgstr ""

  1004. 

  1005. #: ../../../CHANGELOG.md:544

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

  1007. msgstr ""

  1008. 

  1009. #: ../../../CHANGELOG.md:547

  1010. msgid "2025-02-23"

  1011. msgstr ""

  1012. 

  1013. #: ../../../CHANGELOG.md:549

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

  1015. msgstr ""

  1016. 

  1017. #: ../../../CHANGELOG.md:551

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

  1019. msgstr ""

  1020. 

  1021. #: ../../../CHANGELOG.md:553

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

  1023. msgstr ""

  1024. 

  1025. #: ../../../CHANGELOG.md:556

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

  1027. msgstr ""

  1028. 

  1029. #: ../../../CHANGELOG.md:558

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

  1031. msgstr ""

  1032. 

  1033. #: ../../../CHANGELOG.md:560

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

  1035. msgstr ""

  1036. 

  1037. #: ../../../CHANGELOG.md:562

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

  1039. msgstr ""

  1040. 

  1041. #: ../../../CHANGELOG.md:564

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

  1043. msgstr ""

  1044. 

  1045. #: ../../../CHANGELOG.md:570

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

  1047. msgstr ""

  1048. 

  1049. #: ../../../CHANGELOG.md:572

  1050. msgid "2025-02-21"

  1051. msgstr ""

  1052. 

  1053. #: ../../../CHANGELOG.md:574

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

  1055. msgstr ""

  1056. 

  1057. #: ../../../CHANGELOG.md:576

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

  1059. msgstr ""

  1060. 

  1061. #: ../../../CHANGELOG.md:578

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

  1063. msgstr ""

  1064. 

  1065. #: ../../../CHANGELOG.md:580

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

  1067. msgstr ""

  1068. 

  1069. #: ../../../CHANGELOG.md:581

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

  1071. msgstr ""

  1072. 

  1073. #: ../../../CHANGELOG.md:583

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

  1075. msgstr ""

  1076. 

  1077. #: ../../../CHANGELOG.md:584

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

  1079. msgstr ""

  1080. 

  1081. #: ../../../CHANGELOG.md:585

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

  1083. msgstr ""

  1084. 

  1085. #: ../../../CHANGELOG.md:587

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

  1087. msgstr ""

  1088. 

  1089. #: ../../../CHANGELOG.md:590

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

  1091. msgstr ""

  1092. 

  1093. #: ../../../CHANGELOG.md:592

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

  1095. msgstr ""

  1096. 

  1097. #: ../../../CHANGELOG.md:593

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

  1099. msgstr ""

  1100. 

  1101. #: ../../../CHANGELOG.md:594

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

  1103. msgstr ""

  1104. 

  1105. #: ../../../CHANGELOG.md:595

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

  1107. msgstr ""

  1108. 

  1109. #: ../../../CHANGELOG.md:606

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

  1111. msgstr ""

  1112. 

  1113. #: ../../../CHANGELOG.md:608

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

  1115. msgstr ""

  1116. 

  1117. #: ../../../CHANGELOG.md:610

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

  1119. msgstr ""

  1120. 

  1121. #: ../../../CHANGELOG.md:613

  1122. msgid "2025-02-19"

  1123. msgstr ""

  1124. 

  1125. #: ../../../CHANGELOG.md:615

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

  1127. msgstr ""

  1128. 

  1129. #: ../../../CHANGELOG.md:617

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

  1131. msgstr ""

  1132. 

  1133. #: ../../../CHANGELOG.md:619

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

  1135. msgstr ""

  1136. 

  1137. #: ../../../CHANGELOG.md:621

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

  1139. msgstr ""

  1140. 

  1141. #: ../../../CHANGELOG.md:623

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

  1143. msgstr ""

  1144. 

  1145. #: ../../../CHANGELOG.md:625

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

  1147. msgstr ""

  1148. 

  1149. #: ../../../CHANGELOG.md:631

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

  1151. msgstr ""

  1152. 

  1153. #: ../../../CHANGELOG.md:635

  1154. msgid "2025-02-17"

  1155. msgstr ""

  1156. 

  1157. #: ../../../CHANGELOG.md:637

  1158. msgid "FluffyChat Web support"

  1159. msgstr ""

  1160. 

  1161. #: ../../../CHANGELOG.md:639

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

  1163. msgstr ""

  1164. 

  1165. #: ../../../CHANGELOG.md:641

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

  1167. msgstr ""

  1168. 

  1169. #: ../../../CHANGELOG.md:644

  1170. msgid "2025-02-03"

  1171. msgstr ""

  1172. 

  1173. #: ../../../CHANGELOG.md:646

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

  1175. msgstr ""

  1176. 

  1177. #: ../../../CHANGELOG.md:648

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

  1179. msgstr ""

  1180. 

  1181. #: ../../../CHANGELOG.md:650

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

  1183. msgstr ""

  1184. 

  1185. #: ../../../CHANGELOG.md:652

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

  1187. msgstr ""

  1188. 

  1189. #: ../../../CHANGELOG.md:655

  1190. msgid "2025-01-27"

  1191. msgstr ""

  1192. 

  1193. #: ../../../CHANGELOG.md:657

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

  1195. msgstr ""

  1196. 

  1197. #: ../../../CHANGELOG.md:659

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

  1199. msgstr ""

  1200. 

  1201. #: ../../../CHANGELOG.md:661

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

  1203. msgstr ""

  1204. 

  1205. #: ../../../CHANGELOG.md:663

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

  1207. msgstr ""

  1208. 

  1209. #: ../../../CHANGELOG.md:664

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

  1211. msgstr ""

  1212. 

  1213. #: ../../../CHANGELOG.md:665

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

  1215. msgstr ""

  1216. 

  1217. #: ../../../CHANGELOG.md:667

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

  1219. msgstr ""

  1220. 

  1221. #: ../../../CHANGELOG.md:669

  1222. msgid "removing Redis and KeyDB support entirely"

  1223. msgstr ""

  1224. 

  1225. #: ../../../CHANGELOG.md:670

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

  1227. msgstr ""

  1228. 

  1229. #: ../../../CHANGELOG.md:672

  1230. msgid "To update your configuration:"

  1231. msgstr ""

  1232. 

  1233. #: ../../../CHANGELOG.md:674

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

  1235. msgstr ""

  1236. 

  1237. #: ../../../CHANGELOG.md:675

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

  1239. msgstr ""

  1240. 

  1241. #: ../../../CHANGELOG.md:678

  1242. msgid "2025-01-19"

  1243. msgstr ""

  1244. 

  1245. #: ../../../CHANGELOG.md:680

  1246. msgid "conduwuit support"

  1247. msgstr ""

  1248. 

  1249. #: ../../../CHANGELOG.md:682

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

  1251. msgstr ""

  1252. 

  1253. #: ../../../CHANGELOG.md:684

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

  1255. msgstr ""

  1256. 

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

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

  1259. msgstr ""

  1260. 

  1261. #: ../../../CHANGELOG.md:690

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

  1263. msgstr ""

  1264. 

  1265. #: ../../../CHANGELOG.md:693

  1266. msgid "2025-01-14"

  1267. msgstr ""

  1268. 

  1269. #: ../../../CHANGELOG.md:695

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

  1271. msgstr ""

  1272. 

  1273. #: ../../../CHANGELOG.md:697

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

  1275. msgstr ""

  1276. 

  1277. #: ../../../CHANGELOG.md:699

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

  1279. msgstr ""

  1280. 

  1281. #: ../../../CHANGELOG.md:701

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

  1283. msgstr ""

  1284. 

  1285. #: ../../../CHANGELOG.md:703

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

  1287. msgstr ""

  1288. 

  1289. #: ../../../CHANGELOG.md:705

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

  1291. msgstr ""

  1292. 

  1293. #: ../../../CHANGELOG.md:713

  1294. msgid "2024-11-26"

  1295. msgstr ""

  1296. 

  1297. #: ../../../CHANGELOG.md:715

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

  1299. msgstr ""

  1300. 

  1301. #: ../../../CHANGELOG.md:717

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

  1303. msgstr ""

  1304. 

  1305. #: ../../../CHANGELOG.md:719

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

  1307. msgstr ""

  1308. 

  1309. #: ../../../CHANGELOG.md:721

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

  1311. msgstr ""

  1312. 

  1313. #: ../../../CHANGELOG.md:723

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

  1315. msgstr ""

  1316. 

  1317. #: ../../../CHANGELOG.md:725

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

  1319. msgstr ""

  1320. 

  1321. #: ../../../CHANGELOG.md:727

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

  1323. msgstr ""

  1324. 

  1325. #: ../../../CHANGELOG.md:729

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

  1327. msgstr ""

  1328. 

  1329. #: ../../../CHANGELOG.md:732

  1330. msgid "2024-11-23"

  1331. msgstr ""

  1332. 

  1333. #: ../../../CHANGELOG.md:734

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

  1335. msgstr ""

  1336. 

  1337. #: ../../../CHANGELOG.md:736

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

  1339. msgstr ""

  1340. 

  1341. #: ../../../CHANGELOG.md:738

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

  1343. msgstr ""

  1344. 

  1345. #: ../../../CHANGELOG.md:740

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

  1347. msgstr ""

  1348. 

  1349. #: ../../../CHANGELOG.md:742

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

  1351. msgstr ""

  1352. 

  1353. #: ../../../CHANGELOG.md:744

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

  1355. msgstr ""

  1356. 

  1357. #: ../../../CHANGELOG.md:746

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

  1359. msgstr ""

  1360. 

  1361. #: ../../../CHANGELOG.md:748

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

  1363. msgstr ""

  1364. 

  1365. #: ../../../CHANGELOG.md:750

  1366. #: ../../../CHANGELOG.md:1090

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

  1368. msgstr ""

  1369. 

  1370. #: ../../../CHANGELOG.md:761

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

  1372. msgstr ""

  1373. 

  1374. #: ../../../CHANGELOG.md:771

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

  1376. msgstr ""

  1377. 

  1378. #: ../../../CHANGELOG.md:774

  1379. msgid "2024-11-14"

  1380. msgstr ""

  1381. 

  1382. #: ../../../CHANGELOG.md:776

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

  1384. msgstr ""

  1385. 

  1386. #: ../../../CHANGELOG.md:778

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

  1388. msgstr ""

  1389. 

  1390. #: ../../../CHANGELOG.md:780

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

  1392. msgstr ""

  1393. 

  1394. #: ../../../CHANGELOG.md:782

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

  1396. msgstr ""

  1397. 

  1398. #: ../../../CHANGELOG.md:784

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

  1400. msgstr ""

  1401. 

  1402. #: ../../../CHANGELOG.md:786

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

  1404. msgstr ""

  1405. 

  1406. #: ../../../CHANGELOG.md:788

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

  1408. msgstr ""

  1409. 

  1410. #: ../../../CHANGELOG.md:789

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

  1412. msgstr ""

  1413. 

  1414. #: ../../../CHANGELOG.md:790

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

  1416. msgstr ""

  1417. 

  1418. #: ../../../CHANGELOG.md:792

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

  1420. msgstr ""

  1421. 

  1422. #: ../../../CHANGELOG.md:794

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

  1424. msgstr ""

  1425. 

  1426. #: ../../../CHANGELOG.md:796

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

  1428. msgstr ""

  1429. 

  1430. #: ../../../CHANGELOG.md:798

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

  1432. msgstr ""

  1433. 

  1434. #: ../../../CHANGELOG.md:800

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

  1436. msgstr ""

  1437. 

  1438. #: ../../../CHANGELOG.md:802

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

  1440. msgstr ""

  1441. 

  1442. #: ../../../CHANGELOG.md:813

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

  1444. msgstr ""

  1445. 

  1446. #: ../../../CHANGELOG.md:816

  1447. msgid "2024-11-08"

  1448. msgstr ""

  1449. 

  1450. #: ../../../CHANGELOG.md:818

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

  1452. msgstr ""

  1453. 

  1454. #: ../../../CHANGELOG.md:820

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

  1456. msgstr ""

  1457. 

  1458. #: ../../../CHANGELOG.md:822

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

  1460. msgstr ""

  1461. 

  1462. #: ../../../CHANGELOG.md:824

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

  1464. msgstr ""

  1465. 

  1466. #: ../../../CHANGELOG.md:827

  1467. msgid "2024-10-28"

  1468. msgstr ""

  1469. 

  1470. #: ../../../CHANGELOG.md:829

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

  1472. msgstr ""

  1473. 

  1474. #: ../../../CHANGELOG.md:831

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

  1476. msgstr ""

  1477. 

  1478. #: ../../../CHANGELOG.md:833

  1479. msgid "2024-10-19"

  1480. msgstr ""

  1481. 

  1482. #: ../../../CHANGELOG.md:835

  1483. msgid "Support for Matrix Authentication Service"

  1484. msgstr ""

  1485. 

  1486. #: ../../../CHANGELOG.md:837

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

  1488. msgstr ""

  1489. 

  1490. #: ../../../CHANGELOG.md:839

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

  1492. msgstr ""

  1493. 

  1494. #: ../../../CHANGELOG.md:841

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

  1496. msgstr ""

  1497. 

  1498. #: ../../../CHANGELOG.md:843

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

  1500. msgstr ""

  1501. 

  1502. #: ../../../CHANGELOG.md:846

  1503. msgid "2024-09-27"

  1504. msgstr ""

  1505. 

  1506. #: ../../../CHANGELOG.md:848

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

  1508. msgstr ""

  1509. 

  1510. #: ../../../CHANGELOG.md:850

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

  1512. msgstr ""

  1513. 

  1514. #: ../../../CHANGELOG.md:852

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

  1516. msgstr ""

  1517. 

  1518. #: ../../../CHANGELOG.md:854

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

  1520. msgstr ""

  1521. 

  1522. #: ../../../CHANGELOG.md:856

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

  1524. msgstr ""

  1525. 

  1526. #: ../../../CHANGELOG.md:857

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

  1528. msgstr ""

  1529. 

  1530. #: ../../../CHANGELOG.md:862

  1531. msgid "2024-09-12"

  1532. msgstr ""

  1533. 

  1534. #: ../../../CHANGELOG.md:864

  1535. msgid "Support for baibot"

  1536. msgstr ""

  1537. 

  1538. #: ../../../CHANGELOG.md:866

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

  1540. msgstr ""

  1541. 

  1542. #: ../../../CHANGELOG.md:868

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

  1544. msgstr ""

  1545. 

  1546. #: ../../../CHANGELOG.md:870

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

  1548. msgstr ""

  1549. 

  1550. #: ../../../CHANGELOG.md:872

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

  1552. msgstr ""

  1553. 

  1554. #: ../../../CHANGELOG.md:874

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

  1556. msgstr ""

  1557. 

  1558. #: ../../../CHANGELOG.md:876

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

  1560. msgstr ""

  1561. 

  1562. #: ../../../CHANGELOG.md:878

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

  1564. msgstr ""

  1565. 

  1566. #: ../../../CHANGELOG.md:880

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

  1568. msgstr ""

  1569. 

  1570. #: ../../../CHANGELOG.md:882

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

  1572. msgstr ""

  1573. 

  1574. #: ../../../CHANGELOG.md:895

  1575. msgid "2024-08-17"

  1576. msgstr ""

  1577. 

  1578. #: ../../../CHANGELOG.md:897

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

  1580. msgstr ""

  1581. 

  1582. #: ../../../CHANGELOG.md:899

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

  1584. msgstr ""

  1585. 

  1586. #: ../../../CHANGELOG.md:901

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

  1588. msgstr ""

  1589. 

  1590. #: ../../../CHANGELOG.md:903

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

  1592. msgstr ""

  1593. 

  1594. #: ../../../CHANGELOG.md:905

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

  1596. msgstr ""

  1597. 

  1598. #: ../../../CHANGELOG.md:907

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

  1600. msgstr ""

  1601. 

  1602. #: ../../../CHANGELOG.md:913

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

  1604. msgstr ""

  1605. 

  1606. #: ../../../CHANGELOG.md:915

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

  1608. msgstr ""

  1609. 

  1610. #: ../../../CHANGELOG.md:918

  1611. msgid "2024-08-15"

  1612. msgstr ""

  1613. 

  1614. #: ../../../CHANGELOG.md:920

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

  1616. msgstr ""

  1617. 

  1618. #: ../../../CHANGELOG.md:922

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

  1620. msgstr ""

  1621. 

  1622. #: ../../../CHANGELOG.md:924

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

  1624. msgstr ""

  1625. 

  1626. #: ../../../CHANGELOG.md:926

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

  1628. msgstr ""

  1629. 

  1630. #: ../../../CHANGELOG.md:928

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

  1632. msgstr ""

  1633. 

  1634. #: ../../../CHANGELOG.md:931

  1635. msgid "2024-08-08"

  1636. msgstr ""

  1637. 

  1638. #: ../../../CHANGELOG.md:933

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

  1640. msgstr ""

  1641. 

  1642. #: ../../../CHANGELOG.md:935

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

  1644. msgstr ""

  1645. 

  1646. #: ../../../CHANGELOG.md:937

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

  1648. msgstr ""

  1649. 

  1650. #: ../../../CHANGELOG.md:939

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

  1652. msgstr ""

  1653. 

  1654. #: ../../../CHANGELOG.md:945

  1655. msgid "2024-07-25"

  1656. msgstr ""

  1657. 

  1658. #: ../../../CHANGELOG.md:947

  1659. msgid "synapse-usage-exporter support"

  1660. msgstr ""

  1661. 

  1662. #: ../../../CHANGELOG.md:949

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

  1664. msgstr ""

  1665. 

  1666. #: ../../../CHANGELOG.md:951

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

  1668. msgstr ""

  1669. 

  1670. #: ../../../CHANGELOG.md:954

  1671. msgid "2024-07-06"

  1672. msgstr ""

  1673. 

  1674. #: ../../../CHANGELOG.md:956

  1675. msgid "matrix-alertmanager-receiver support"

  1676. msgstr ""

  1677. 

  1678. #: ../../../CHANGELOG.md:958

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

  1680. msgstr ""

  1681. 

  1682. #: ../../../CHANGELOG.md:960

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

  1684. msgstr ""

  1685. 

  1686. #: ../../../CHANGELOG.md:962

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

  1688. msgstr ""

  1689. 

  1690. #: ../../../CHANGELOG.md:964

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

  1692. msgstr ""

  1693. 

  1694. #: ../../../CHANGELOG.md:966

  1695. msgid "Traefik v3"

  1696. msgstr ""

  1697. 

  1698. #: ../../../CHANGELOG.md:968

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

  1700. msgstr ""

  1701. 

  1702. #: ../../../CHANGELOG.md:970

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

  1704. msgstr ""

  1705. 

  1706. #: ../../../CHANGELOG.md:972

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

  1708. msgstr ""

  1709. 

  1710. #: ../../../CHANGELOG.md:974

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

  1712. msgstr ""

  1713. 

  1714. #: ../../../CHANGELOG.md:976

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

  1716. msgstr ""

  1717. 

  1718. #: ../../../CHANGELOG.md:978

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

  1720. msgstr ""

  1721. 

  1722. #: ../../../CHANGELOG.md:980

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

  1724. msgstr ""

  1725. 

  1726. #: ../../../CHANGELOG.md:982

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

  1728. msgstr ""

  1729. 

  1730. #: ../../../CHANGELOG.md:984

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

  1732. msgstr ""

  1733. 

  1734. #: ../../../CHANGELOG.md:986

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

  1736. msgstr ""

  1737. 

  1738. #: ../../../CHANGELOG.md:988

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

  1740. msgstr ""

  1741. 

  1742. #: ../../../CHANGELOG.md:990

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

  1744. msgstr ""

  1745. 

  1746. #: ../../../CHANGELOG.md:992

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

  1748. msgstr ""

  1749. 

  1750. #: ../../../CHANGELOG.md:1006

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

  1752. msgstr ""

  1753. 

  1754. #: ../../../CHANGELOG.md:1019

  1755. msgid "2024-07-01"

  1756. msgstr ""

  1757. 

  1758. #: ../../../CHANGELOG.md:1021

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

  1760. msgstr ""

  1761. 

  1762. #: ../../../CHANGELOG.md:1023

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

  1764. msgstr ""

  1765. 

  1766. #: ../../../CHANGELOG.md:1025

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

  1768. msgstr ""

  1769. 

  1770. #: ../../../CHANGELOG.md:1027

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

  1772. msgstr ""

  1773. 

  1774. #: ../../../CHANGELOG.md:1035

  1775. msgid "2024-06-25"

  1776. msgstr ""

  1777. 

  1778. #: ../../../CHANGELOG.md:1037

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

  1780. msgstr ""

  1781. 

  1782. #: ../../../CHANGELOG.md:1039

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

  1784. msgstr ""

  1785. 

  1786. #: ../../../CHANGELOG.md:1041

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

  1788. msgstr ""

  1789. 

  1790. #: ../../../CHANGELOG.md:1043

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

  1792. msgstr ""

  1793. 

  1794. #: ../../../CHANGELOG.md:1045

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

  1796. msgstr ""

  1797. 

  1798. #: ../../../CHANGELOG.md:1047

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

  1800. msgstr ""

  1801. 

  1802. #: ../../../CHANGELOG.md:1049

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

  1804. msgstr ""

  1805. 

  1806. #: ../../../CHANGELOG.md:1051

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

  1808. msgstr ""

  1809. 

  1810. #: ../../../CHANGELOG.md:1054

  1811. msgid "2024-06-22"

  1812. msgstr ""

  1813. 

  1814. #: ../../../CHANGELOG.md:1056

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

  1816. msgstr ""

  1817. 

  1818. #: ../../../CHANGELOG.md:1058

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

  1820. msgstr ""

  1821. 

  1822. #: ../../../CHANGELOG.md:1060

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

  1824. msgstr ""

  1825. 

  1826. #: ../../../CHANGELOG.md:1062

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

  1828. msgstr ""

  1829. 

  1830. #: ../../../CHANGELOG.md:1065

  1831. msgid "2024-06-03"

  1832. msgstr ""

  1833. 

  1834. #: ../../../CHANGELOG.md:1067

  1835. msgid "WeChat bridging support"

  1836. msgstr ""

  1837. 

  1838. #: ../../../CHANGELOG.md:1069

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

  1840. msgstr ""

  1841. 

  1842. #: ../../../CHANGELOG.md:1071

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

  1844. msgstr ""

  1845. 

  1846. #: ../../../CHANGELOG.md:1074

  1847. msgid "2024-03-26"

  1848. msgstr ""

  1849. 

  1850. #: ../../../CHANGELOG.md:1076

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

  1852. msgstr ""

  1853. 

  1854. #: ../../../CHANGELOG.md:1078

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

  1856. msgstr ""

  1857. 

  1858. #: ../../../CHANGELOG.md:1080

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

  1860. msgstr ""

  1861. 

  1862. #: ../../../CHANGELOG.md:1082

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

  1864. msgstr ""

  1865. 

  1866. #: ../../../CHANGELOG.md:1084

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

  1868. msgstr ""

  1869. 

  1870. #: ../../../CHANGELOG.md:1086

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

  1872. msgstr ""

  1873. 

  1874. #: ../../../CHANGELOG.md:1088

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

  1876. msgstr ""

  1877. 

  1878. #: ../../../CHANGELOG.md:1099

  1879. msgid "2024-03-24"

  1880. msgstr ""

  1881. 

  1882. #: ../../../CHANGELOG.md:1101

  1883. msgid "Initial work on IPv6 support"

  1884. msgstr ""

  1885. 

  1886. #: ../../../CHANGELOG.md:1103

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

  1888. msgstr ""

  1889. 

  1890. #: ../../../CHANGELOG.md:1105

  1891. msgid "It should be noted that:"

  1892. msgstr ""

  1893. 

  1894. #: ../../../CHANGELOG.md:1107

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

  1896. msgstr ""

  1897. 

  1898. #: ../../../CHANGELOG.md:1108

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

  1900. msgstr ""

  1901. 

  1902. #: ../../../CHANGELOG.md:1109

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

  1904. msgstr ""

  1905. 

  1906. #: ../../../CHANGELOG.md:1111

  1907. msgid "Pantalaimon support"

  1908. msgstr ""

  1909. 

  1910. #: ../../../CHANGELOG.md:1113

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

  1912. msgstr ""

  1913. 

  1914. #: ../../../CHANGELOG.md:1115

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

  1916. msgstr ""

  1917. 

  1918. #: ../../../CHANGELOG.md:1118

  1919. msgid "2024-03-05"

  1920. msgstr ""

  1921. 

  1922. #: ../../../CHANGELOG.md:1120

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

  1924. msgstr ""

  1925. 

  1926. #: ../../../CHANGELOG.md:1122

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

  1928. msgstr ""

  1929. 

  1930. #: ../../../CHANGELOG.md:1124

  1931. msgid "This is an alternative to [running Draupnir in bot mode](./docs/configuring-playbook-bot-draupnir.md), which is still supported by the playbook."

  1932. msgstr ""

  1933. 

  1934. #: ../../../CHANGELOG.md:1126

  1935. msgid "The documentation page for [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) contains more information on how to install it."

  1936. msgstr ""

  1937. 

  1938. #: ../../../CHANGELOG.md:1129

  1939. msgid "2024-02-19"

  1940. msgstr ""

  1941. 

  1942. #: ../../../CHANGELOG.md:1131

  1943. msgid "Support for bridging to Facebook/Messenger via the new mautrix-meta bridge"

  1944. msgstr ""

  1945. 

  1946. #: ../../../CHANGELOG.md:1133

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

  1948. msgstr ""

  1949. 

  1950. #: ../../../CHANGELOG.md:1135

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

  1952. msgstr ""

  1953. 

  1954. #: ../../../CHANGELOG.md:1137

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

  1956. msgstr ""

  1957. 

  1958. #: ../../../CHANGELOG.md:1139

  1959. msgid "[Setting up Instagram bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)"

  1960. msgstr ""

  1961. 

  1962. #: ../../../CHANGELOG.md:1141

  1963. msgid "[Setting up Messenger bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-messenger.md)"

  1964. msgstr ""

  1965. 

  1966. #: ../../../CHANGELOG.md:1143

  1967. msgid "The documentation pages contain more information on how to migrate."

  1968. msgstr ""

  1969. 

  1970. #: ../../../CHANGELOG.md:1146

  1971. msgid "2024-02-14"

  1972. msgstr ""

  1973. 

  1974. #: ../../../CHANGELOG.md:1148

  1975. msgid "Much larger Synapse caches and cache auto-tuning enabled by default"

  1976. msgstr ""

  1977. 

  1978. #: ../../../CHANGELOG.md:1150

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

  1980. msgstr ""

  1981. 

  1982. #: ../../../CHANGELOG.md:1152

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

  1984. msgstr ""

  1985. 

  1986. #: ../../../CHANGELOG.md:1154

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

  1988. msgstr ""

  1989. 

  1990. #: ../../../CHANGELOG.md:1156

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

  1992. msgstr ""

  1993. 

  1994. #: ../../../CHANGELOG.md:1157

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

  1996. msgstr ""

  1997. 

  1998. #: ../../../CHANGELOG.md:1158

  1999. msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` — defaults to `30s`"

  2000. msgstr ""

  2001. 

  2002. #: ../../../CHANGELOG.md:1160

  2003. msgid "These values should be good defaults for most servers, but may change over time as we experiment further."

  2004. msgstr ""

  2005. 

  2006. #: ../../../CHANGELOG.md:1162

  2007. msgid "Refer to our new [Tuning caches and cache autotuning](docs/maintenance-synapse.md#tuning-caches-and-cache-autotuning) documentation section for more details."

  2008. msgstr ""

  2009. 

  2010. #: ../../../CHANGELOG.md:1165

  2011. msgid "2024-01-31"

  2012. msgstr ""

  2013. 

  2014. #: ../../../CHANGELOG.md:1167

  2015. msgid "(Backward-compatibility break) Minor changes necessary for some people serving a static website at the base domain"

  2016. msgstr ""

  2017. 

  2018. #: ../../../CHANGELOG.md:1169

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

  2020. msgstr ""

  2021. 

  2022. #: ../../../CHANGELOG.md:1171

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

  2024. msgstr ""

  2025. 

  2026. #: ../../../CHANGELOG.md:1173

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

  2028. msgstr ""

  2029. 

  2030. #: ../../../CHANGELOG.md:1176

  2031. msgid "2024-01-20"

  2032. msgstr ""

  2033. 

  2034. #: ../../../CHANGELOG.md:1178

  2035. msgid "Support for more efficient (specialized) Synapse workers"

  2036. msgstr ""

  2037. 

  2038. #: ../../../CHANGELOG.md:1180

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

  2040. msgstr ""

  2041. 

  2042. #: ../../../CHANGELOG.md:1182

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

  2044. msgstr ""

  2045. 

  2046. #: ../../../CHANGELOG.md:1184

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

  2048. msgstr ""

  2049. 

  2050. #: ../../../CHANGELOG.md:1186

  2051. msgid "To get started, refer to our [Specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) documentation section."

  2052. msgstr ""

  2053. 

  2054. #: ../../../CHANGELOG.md:1189

  2055. msgid "2024-01-17"

  2056. msgstr ""

  2057. 

  2058. #: ../../../CHANGELOG.md:1191

  2059. msgid "Switching to Element's AGPLv3-licensed Synapse release"

  2060. msgstr ""

  2061. 

  2062. #: ../../../CHANGELOG.md:1193

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

  2064. msgstr ""

  2065. 

  2066. #: ../../../CHANGELOG.md:1195

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

  2068. msgstr ""

  2069. 

  2070. #: ../../../CHANGELOG.md:1196

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

  2072. msgstr ""

  2073. 

  2074. #: ../../../CHANGELOG.md:1198

  2075. msgid "You can also learn more in [this post](https://matrix.org/blog/2023/11/06/future-of-synapse-dendrite/) by the Matrix Foundation."

  2076. msgstr ""

  2077. 

  2078. #: ../../../CHANGELOG.md:1200

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

  2080. msgstr ""

  2081. 

  2082. #: ../../../CHANGELOG.md:1202

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

  2084. msgstr ""

  2085. 

  2086. #: ../../../CHANGELOG.md:1204

  2087. msgid "**What does this mean to you?**"

  2088. msgstr ""

  2089. 

  2090. #: ../../../CHANGELOG.md:1206

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

  2092. msgstr ""

  2093. 

  2094. #: ../../../CHANGELOG.md:1208

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

  2096. msgstr ""

  2097. 

  2098. #: ../../../CHANGELOG.md:1210

  2099. 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!"

  2100. msgstr ""

  2101. 

  2102. #: ../../../CHANGELOG.md:1212

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

  2104. msgstr ""

  2105. 

  2106. #: ../../../CHANGELOG.md:1224

  2107. msgid "Notes:"

  2108. msgstr ""

  2109. 

  2110. #: ../../../CHANGELOG.md:1226

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

  2112. msgstr ""

  2113. 

  2114. #: ../../../CHANGELOG.md:1228

  2115. msgid "running an outdated homeserver exposes you to security issues and incompatibilities. Only consider doing this as a short-term solution."

  2116. msgstr ""

  2117. 

  2118. #: ../../../CHANGELOG.md:1230

  2119. msgid "2024-01-16"

  2120. msgstr ""

  2121. 

  2122. #: ../../../CHANGELOG.md:1232

  2123. msgid "`Draupnir` has been relicensed to AFL-3.0"

  2124. msgstr ""

  2125. 

  2126. #: ../../../CHANGELOG.md:1234

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

  2128. msgstr ""

  2129. 

  2130. #: ../../../CHANGELOG.md:1236

  2131. msgid "2024-01-15"

  2132. msgstr ""

  2133. 

  2134. #: ../../../CHANGELOG.md:1238

  2135. msgid "Goodbye, `matrix-nginx-proxy` 🪦"

  2136. msgstr ""

  2137. 

  2138. #: ../../../CHANGELOG.md:1240

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

  2140. msgstr ""

  2141. 

  2142. #: ../../../CHANGELOG.md:1242

  2143. msgid "Backstory on `matrix-nginx-proxy`"

  2144. msgstr ""

  2145. 

  2146. #: ../../../CHANGELOG.md:1244

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

  2148. msgstr ""

  2149. 

  2150. #: ../../../CHANGELOG.md:1246

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

  2152. msgstr ""

  2153. 

  2154. #: ../../../CHANGELOG.md:1248

  2155. msgid "To us, `matrix-nginx-proxy` was:"

  2156. msgstr ""

  2157. 

  2158. #: ../../../CHANGELOG.md:1250

  2159. msgid "an [nginx](https://nginx.org/)-based reverse-proxy"

  2160. msgstr ""

  2161. 

  2162. #: ../../../CHANGELOG.md:1251

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

  2164. msgstr ""

  2165. 

  2166. #: ../../../CHANGELOG.md:1252

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

  2168. msgstr ""

  2169. 

  2170. #: ../../../CHANGELOG.md:1253

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

  2172. msgstr ""

  2173. 

  2174. #: ../../../CHANGELOG.md:1254

  2175. msgid "a webserver for serving the `/.well-known/matrix` static files (generated by the `matrix-base` role until now)"

  2176. msgstr ""

  2177. 

  2178. #: ../../../CHANGELOG.md:1255

  2179. msgid "a webserver [serving your base domain](./docs/configuring-playbook-base-domain-serving.md) (and also generating the `index.html` page for it)"

  2180. msgstr ""

  2181. 

  2182. #: ../../../CHANGELOG.md:1256

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

  2184. msgstr ""

  2185. 

  2186. #: ../../../CHANGELOG.md:1258

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

  2188. msgstr ""

  2189. 

  2190. #: ../../../CHANGELOG.md:1260

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

  2192. msgstr ""

  2193. 

  2194. #: ../../../CHANGELOG.md:1262

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

  2196. msgstr ""

  2197. 

  2198. #: ../../../CHANGELOG.md:1264

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

  2200. msgstr ""

  2201. 

  2202. #: ../../../CHANGELOG.md:1266

  2203. msgid "Going Traefik-native and cutting out all middlemen"

  2204. msgstr ""

  2205. 

  2206. #: ../../../CHANGELOG.md:1268

  2207. msgid "In our new setup, you'll see the bare minimum number of reverse-proxies."

  2208. msgstr ""

  2209. 

  2210. #: ../../../CHANGELOG.md:1270

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

  2212. msgstr ""

  2213. 

  2214. #: ../../../CHANGELOG.md:1272

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

  2216. msgstr ""

  2217. 

  2218. #: ../../../CHANGELOG.md:1274

  2219. msgid "Traefik now has an extra job"

  2220. msgstr ""

  2221. 

  2222. #: ../../../CHANGELOG.md:1276

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

  2224. msgstr ""

  2225. 

  2226. #: ../../../CHANGELOG.md:1278

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

  2228. msgstr ""

  2229. 

  2230. #: ../../../CHANGELOG.md:1280

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

  2232. msgstr ""

  2233. 

  2234. #: ../../../CHANGELOG.md:1282

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

  2236. msgstr ""

  2237. 

  2238. #: ../../../CHANGELOG.md:1284

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

  2240. msgstr ""

  2241. 

  2242. #: ../../../CHANGELOG.md:1286

  2243. msgid "Traefik serving this second purpose has a few downsides:"

  2244. msgstr ""

  2245. 

  2246. #: ../../../CHANGELOG.md:1288

  2247. msgid "Traefik becomes a runtime dependency for all homeserver-dependant container services"

  2248. msgstr ""

  2249. 

  2250. #: ../../../CHANGELOG.md:1289

  2251. msgid "all homeserver-dependant services now need to be connected to the `traefik` container network, even if they don't need public internet exposure"

  2252. msgstr ""

  2253. 

  2254. #: ../../../CHANGELOG.md:1291

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

  2256. msgstr ""

  2257. 

  2258. #: ../../../CHANGELOG.md:1293

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

  2260. msgstr ""

  2261. 

  2262. #: ../../../CHANGELOG.md:1295

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

  2264. msgstr ""

  2265. 

  2266. #: ../../../CHANGELOG.md:1297

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

  2268. msgstr ""

  2269. 

  2270. #: ../../../CHANGELOG.md:1299

  2271. msgid "People managing their own Traefik instance need to do minor changes"

  2272. msgstr ""

  2273. 

  2274. #: ../../../CHANGELOG.md:1301

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

  2276. msgstr ""

  2277. 

  2278. #: ../../../CHANGELOG.md:1303

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

  2280. msgstr ""

  2281. 

  2282. #: ../../../CHANGELOG.md:1305

  2283. msgid "People fronting Traefik with another reverse proxy need to do minor changes"

  2284. msgstr ""

  2285. 

  2286. #: ../../../CHANGELOG.md:1307

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

  2288. msgstr ""

  2289. 

  2290. #: ../../../CHANGELOG.md:1309

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

  2292. msgstr ""

  2293. 

  2294. #: ../../../CHANGELOG.md:1311

  2295. msgid "Supported reverse proxy types are now fewer"

  2296. msgstr ""

  2297. 

  2298. #: ../../../CHANGELOG.md:1313

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

  2300. msgstr ""

  2301. 

  2302. #: ../../../CHANGELOG.md:1315

  2303. msgid "Previously, we allowed you to set `matrix_playbook_reverse_proxy_type` to 7 different values to accommodate various reverse-proxy setups."

  2304. msgstr ""

  2305. 

  2306. #: ../../../CHANGELOG.md:1317

  2307. msgid "The complexity of this is too high, so we only support 3 values right now:"

  2308. msgstr ""

  2309. 

  2310. #: ../../../CHANGELOG.md:1319

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

  2312. msgstr ""

  2313. 

  2314. #: ../../../CHANGELOG.md:1320

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

  2316. msgstr ""

  2317. 

  2318. #: ../../../CHANGELOG.md:1321

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

  2320. msgstr ""

  2321. 

  2322. #: ../../../CHANGELOG.md:1323

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

  2324. msgstr ""

  2325. 

  2326. #: ../../../CHANGELOG.md:1325

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

  2328. msgstr ""

  2329. 

  2330. #: ../../../CHANGELOG.md:1327

  2331. msgid "If you were using these values as a way to stay away from Traefik, you now have 2 options:"

  2332. msgstr ""

  2333. 

  2334. #: ../../../CHANGELOG.md:1329

  2335. msgid "(recommended) [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)"

  2336. msgstr ""

  2337. 

  2338. #: ../../../CHANGELOG.md:1330

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

  2340. msgstr ""

  2341. 

  2342. #: ../../../CHANGELOG.md:1332

  2343. msgid "Container networking changes"

  2344. msgstr ""

  2345. 

  2346. #: ../../../CHANGELOG.md:1334

  2347. msgid "Now that `matrix-nginx-proxy` is not in the mix, it became easier to clear out some other long-overdue technical debt."

  2348. msgstr ""

  2349. 

  2350. #: ../../../CHANGELOG.md:1336

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

  2352. msgstr ""

  2353. 

  2354. #: ../../../CHANGELOG.md:1338

  2355. msgid "Moving components (especially the database) into other container networks was difficult — it required changes to many other components to ensure correct connectivity."

  2356. msgstr ""

  2357. 

  2358. #: ../../../CHANGELOG.md:1340

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

  2360. msgstr ""

  2361. 

  2362. #: ../../../CHANGELOG.md:1342

  2363. msgid "Carrying out these container networking changes necessitated modifying many components, so **we're hoping not too many bugs were introduced in the process**."

  2364. msgstr ""

  2365. 

  2366. #: ../../../CHANGELOG.md:1344

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

  2368. msgstr ""

  2369. 

  2370. #: ../../../CHANGELOG.md:1346

  2371. msgid "Metrics exposure changes"

  2372. msgstr ""

  2373. 

  2374. #: ../../../CHANGELOG.md:1348

  2375. msgid "This section is for people who are exposing monitoring metrics publicly, to be consumed by an external Prometheus server."

  2376. msgstr ""

  2377. 

  2378. #: ../../../CHANGELOG.md:1350

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

  2380. msgstr ""

  2381. 

  2382. #: ../../../CHANGELOG.md:1352

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

  2384. msgstr ""

  2385. 

  2386. #: ../../../CHANGELOG.md:1354

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

  2388. msgstr ""

  2389. 

  2390. #: ../../../CHANGELOG.md:1356

  2391. 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!"

  2392. msgstr ""

  2393. 

  2394. #: ../../../CHANGELOG.md:1358

  2395. msgid "Matrix static files"

  2396. msgstr ""

  2397. 

  2398. #: ../../../CHANGELOG.md:1360

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

  2400. msgstr ""

  2401. 

  2402. #: ../../../CHANGELOG.md:1362

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

  2404. msgstr ""

  2405. 

  2406. #: ../../../CHANGELOG.md:1364

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

  2408. msgstr ""

  2409. 

  2410. #: ../../../CHANGELOG.md:1366

  2411. msgid "A note on performance"

  2412. msgstr ""

  2413. 

  2414. #: ../../../CHANGELOG.md:1368

  2415. msgid "Some of you have been voicing their concerns (for a long time) about Traefik being too slow and nginx being better."

  2416. msgstr ""

  2417. 

  2418. #: ../../../CHANGELOG.md:1370

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

  2420. msgstr ""

  2421. 

  2422. #: ../../../CHANGELOG.md:1372

  2423. msgid "We believe that using Traefik provides way too many benefits to worry about this minor performance impairment."

  2424. msgstr ""

  2425. 

  2426. #: ../../../CHANGELOG.md:1374

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

  2428. msgstr ""

  2429. 

  2430. #: ../../../CHANGELOG.md:1376

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

  2432. msgstr ""

  2433. 

  2434. #: ../../../CHANGELOG.md:1378

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

  2436. msgstr ""

  2437. 

  2438. #: ../../../CHANGELOG.md:1380

  2439. msgid "Migration procedure"

  2440. msgstr ""

  2441. 

  2442. #: ../../../CHANGELOG.md:1382

  2443. msgid "The updated playbook will automatically perform some migration tasks for you:"

  2444. msgstr ""

  2445. 

  2446. #: ../../../CHANGELOG.md:1384

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

  2448. msgstr ""

  2449. 

  2450. #: ../../../CHANGELOG.md:1386

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

  2452. msgstr ""

  2453. 

  2454. #: ../../../CHANGELOG.md:1388

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

  2456. msgstr ""

  2457. 

  2458. #: ../../../CHANGELOG.md:1390

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

  2460. msgstr ""

  2461. 

  2462. #: ../../../CHANGELOG.md:1392

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

  2464. msgstr ""

  2465. 

  2466. #: ../../../CHANGELOG.md:1394

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

  2468. msgstr ""

  2469. 

  2470. #: ../../../CHANGELOG.md:1396

  2471. msgid "We don't recommend changing these variables and suppressing warnings, unless you know what you're doing."

  2472. msgstr ""

  2473. 

  2474. #: ../../../CHANGELOG.md:1398

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

  2476. msgstr ""

  2477. 

  2478. #: ../../../CHANGELOG.md:1400

  2479. msgid "Conclusion"

  2480. msgstr ""

  2481. 

  2482. #: ../../../CHANGELOG.md:1402

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

  2484. msgstr ""

  2485. 

  2486. #: ../../../CHANGELOG.md:1404

  2487. 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!"

  2488. msgstr ""

  2489. 

  2490. #: ../../../CHANGELOG.md:1407

  2491. msgid "2024-01-14"

  2492. msgstr ""

  2493. 

  2494. #: ../../../CHANGELOG.md:1409

  2495. msgid "(Backward Compatibility) Configuration changes required for people fronting the integrated reverse-proxy webserver with another reverse-proxy"

  2496. msgstr ""

  2497. 

  2498. #: ../../../CHANGELOG.md:1411

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

  2500. msgstr ""

  2501. 

  2502. #: ../../../CHANGELOG.md:1413

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

  2504. msgstr ""

  2505. 

  2506. #: ../../../CHANGELOG.md:1415

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

  2508. msgstr ""

  2509. 

  2510. #: ../../../CHANGELOG.md:1417

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

  2512. msgstr ""

  2513. 

  2514. #: ../../../CHANGELOG.md:1419

  2515. msgid "Adapt your configuration as seen below:"

  2516. msgstr ""

  2517. 

  2518. #: ../../../CHANGELOG.md:1452

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

  2520. msgstr ""

  2521. 

  2522. #: ../../../CHANGELOG.md:1455

  2523. msgid "2024-01-13"

  2524. msgstr ""

  2525. 

  2526. #: ../../../CHANGELOG.md:1457

  2527. msgid "matrix-reminder-bot update with more secure (backward-incompatible) default settings"

  2528. msgstr ""

  2529. 

  2530. #: ../../../CHANGELOG.md:1459

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

  2532. msgstr ""

  2533. 

  2534. #: ../../../CHANGELOG.md:1461

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

  2536. msgstr ""

  2537. 

  2538. #: ../../../CHANGELOG.md:1463

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

  2540. msgstr ""

  2541. 

  2542. #: ../../../CHANGELOG.md:1465

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

  2544. msgstr ""

  2545. 

  2546. #: ../../../CHANGELOG.md:1467

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

  2548. msgstr ""

  2549. 

  2550. #: ../../../CHANGELOG.md:1469

  2551. msgid "If you need **to undo or tweak these security improvements**, you can change your `vars.yml` file to:"

  2552. msgstr ""

  2553. 

  2554. #: ../../../CHANGELOG.md:1471

  2555. msgid "disable the allowlist (`matrix_bot_matrix_reminder_bot_allowlist_enabled: false`), making the bot allow usage by anyone, anywhere"

  2556. msgstr ""

  2557. 

  2558. #: ../../../CHANGELOG.md:1473

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

  2560. msgstr ""

  2561. 

  2562. #: ../../../CHANGELOG.md:1475

  2563. msgid "override the default allowlist (in the `group_vars/matrix_servers` file) by redefining `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`"

  2564. msgstr ""

  2565. 

  2566. #: ../../../CHANGELOG.md:1478

  2567. msgid "2024-01-05"

  2568. msgstr ""

  2569. 

  2570. #: ../../../CHANGELOG.md:1480

  2571. msgid "matrix-mailer has been replaced by the exim-relay external role"

  2572. msgstr ""

  2573. 

  2574. #: ../../../CHANGELOG.md:1482

  2575. #: ../../../CHANGELOG.md:2120

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

  2577. msgstr ""

  2578. 

  2579. #: ../../../CHANGELOG.md:1484

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

  2581. msgstr ""

  2582. 

  2583. #: ../../../CHANGELOG.md:1486

  2584. msgid "To migrate:"

  2585. msgstr ""

  2586. 

  2587. #: ../../../CHANGELOG.md:1488

  2588. msgid "pull the playbook changes, as usual"

  2589. msgstr ""

  2590. 

  2591. #: ../../../CHANGELOG.md:1489

  2592. msgid "update your roles (run `just roles` or `make roles`)"

  2593. msgstr ""

  2594. 

  2595. #: ../../../CHANGELOG.md:1490

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

  2597. msgstr ""

  2598. 

  2599. #: ../../../CHANGELOG.md:1491

  2600. msgid "re-run the playbook (`install-all` or `setup-all`)"

  2601. msgstr ""

  2602. 

  2603. #: ../../../CHANGELOG.md:1493

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

  2605. msgstr ""

  2606. 

  2607. #: ../../../CHANGELOG.md:1496

  2608. msgid "2024-01-02"

  2609. msgstr ""

  2610. 

  2611. #: ../../../CHANGELOG.md:1498

  2612. msgid "mautrix-signal now powered by the new Go-based bridge"

  2613. msgstr ""

  2614. 

  2615. #: ../../../CHANGELOG.md:1500

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

  2617. msgstr ""

  2618. 

  2619. #: ../../../CHANGELOG.md:1502

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

  2621. msgstr ""

  2622. 

  2623. #: ../../../CHANGELOG.md:1504

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

  2625. msgstr ""

  2626. 

  2627. #: ../../../CHANGELOG.md:1507

  2628. msgid "2023-10-23"

  2629. msgstr ""

  2630. 

  2631. #: ../../../CHANGELOG.md:1509

  2632. msgid "Enabling `allow_public_rooms_over_federation` by default for Synapse"

  2633. msgstr ""

  2634. 

  2635. #: ../../../CHANGELOG.md:1511

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

  2637. msgstr ""

  2638. 

  2639. #: ../../../CHANGELOG.md:1513

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

  2641. msgstr ""

  2642. 

  2643. #: ../../../CHANGELOG.md:1515

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

  2645. msgstr ""

  2646. 

  2647. #: ../../../CHANGELOG.md:1517

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

  2649. msgstr ""

  2650. 

  2651. #: ../../../CHANGELOG.md:1519

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

  2653. msgstr ""

  2654. 

  2655. #: ../../../CHANGELOG.md:1521

  2656. msgid "The **historical reasoning** behind this change is as follows:"

  2657. msgstr ""

  2658. 

  2659. #: ../../../CHANGELOG.md:1523

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

  2661. msgstr ""

  2662. 

  2663. #: ../../../CHANGELOG.md:1525

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

  2665. msgstr ""

  2666. 

  2667. #: ../../../CHANGELOG.md:1527

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

  2669. msgstr ""

  2670. 

  2671. #: ../../../CHANGELOG.md:1529

  2672. msgid "Here are **actions you may wish to take** as a result of this change:"

  2673. msgstr ""

  2674. 

  2675. #: ../../../CHANGELOG.md:1531

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

  2677. msgstr ""

  2678. 

  2679. #: ../../../CHANGELOG.md:1533

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

  2681. msgstr ""

  2682. 

  2683. #: ../../../CHANGELOG.md:1535

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

  2685. msgstr ""

  2686. 

  2687. #: ../../../CHANGELOG.md:1538

  2688. msgid "2023-10-18"

  2689. msgstr ""

  2690. 

  2691. #: ../../../CHANGELOG.md:1540

  2692. msgid "Postgres parameters are automatically tuned now"

  2693. msgstr ""

  2694. 

  2695. #: ../../../CHANGELOG.md:1542

  2696. msgid "The playbook has provided some hints about [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) for quite a while now."

  2697. msgstr ""

  2698. 

  2699. #: ../../../CHANGELOG.md:1544

  2700. 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/."

  2701. msgstr ""

  2702. 

  2703. #: ../../../CHANGELOG.md:1546

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

  2705. msgstr ""

  2706. 

  2707. #: ../../../CHANGELOG.md:1548

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

  2709. msgstr ""

  2710. 

  2711. #: ../../../CHANGELOG.md:1551

  2712. msgid "2023-08-31"

  2713. msgstr ""

  2714. 

  2715. #: ../../../CHANGELOG.md:1553

  2716. msgid "SchildiChat Web support"

  2717. msgstr ""

  2718. 

  2719. #: ../../../CHANGELOG.md:1555

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

  2721. msgstr ""

  2722. 

  2723. #: ../../../CHANGELOG.md:1557

  2724. msgid "See our [Configuring SchildiChat Web](docs/configuring-playbook-client-schildichat-web.md) documentation to get started."

  2725. msgstr ""

  2726. 

  2727. #: ../../../CHANGELOG.md:1560

  2728. msgid "2023-08-23"

  2729. msgstr ""

  2730. 

  2731. #: ../../../CHANGELOG.md:1562

  2732. msgid "mautrix-wsproxy support"

  2733. msgstr ""

  2734. 

  2735. #: ../../../CHANGELOG.md:1564

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

  2737. msgstr ""

  2738. 

  2739. #: ../../../CHANGELOG.md:1566

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

  2741. msgstr ""

  2742. 

  2743. #: ../../../CHANGELOG.md:1569

  2744. msgid "2023-07-24"

  2745. msgstr ""

  2746. 

  2747. #: ../../../CHANGELOG.md:1571

  2748. msgid "matrix-registration-bot usage changed"

  2749. msgstr ""

  2750. 

  2751. #: ../../../CHANGELOG.md:1573

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

  2753. msgstr ""

  2754. 

  2755. #: ../../../CHANGELOG.md:1575

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

  2757. msgstr ""

  2758. 

  2759. #: ../../../CHANGELOG.md:1577

  2760. msgid "`matrix_bot_matrix_registration_bot_bot_access_token`"

  2761. msgstr ""

  2762. 

  2763. #: ../../../CHANGELOG.md:1578

  2764. msgid "`matrix_bot_matrix_registration_bot_api_token`"

  2765. msgstr ""

  2766. 

  2767. #: ../../../CHANGELOG.md:1581

  2768. msgid "2023-07-21"

  2769. msgstr ""

  2770. 

  2771. #: ../../../CHANGELOG.md:1583

  2772. msgid "mautrix-gmessages support"

  2773. msgstr ""

  2774. 

  2775. #: ../../../CHANGELOG.md:1585

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

  2777. msgstr ""

  2778. 

  2779. #: ../../../CHANGELOG.md:1588

  2780. msgid "2023-07-17"

  2781. msgstr ""

  2782. 

  2783. #: ../../../CHANGELOG.md:1590

  2784. msgid "matrix-media-repo support"

  2785. msgstr ""

  2786. 

  2787. #: ../../../CHANGELOG.md:1592

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

  2789. msgstr ""

  2790. 

  2791. #: ../../../CHANGELOG.md:1594

  2792. msgid "To learn more see our [Storing Matrix media files using matrix-media-repo](docs/configuring-playbook-matrix-media-repo.md) documentation page."

  2793. msgstr ""

  2794. 

  2795. #: ../../../CHANGELOG.md:1597

  2796. msgid "2023-05-25"

  2797. msgstr ""

  2798. 

  2799. #: ../../../CHANGELOG.md:1599

  2800. msgid "Enabling `forget_rooms_on_leave` by default for Synapse"

  2801. msgstr ""

  2802. 

  2803. #: ../../../CHANGELOG.md:1601

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

  2805. msgstr ""

  2806. 

  2807. #: ../../../CHANGELOG.md:1603

  2808. msgid "The upstream Synapse default is `false` (disabled), so that you must forget rooms manually after leaving."

  2809. msgstr ""

  2810. 

  2811. #: ../../../CHANGELOG.md:1605

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

  2813. msgstr ""

  2814. 

  2815. #: ../../../CHANGELOG.md:1607

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

  2817. msgstr ""

  2818. 

  2819. #: ../../../CHANGELOG.md:1610

  2820. msgid "2023-04-03"

  2821. msgstr ""

  2822. 

  2823. #: ../../../CHANGELOG.md:1612

  2824. msgid "The matrix-jitsi role lives independently now"

  2825. msgstr ""

  2826. 

  2827. #: ../../../CHANGELOG.md:1614

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

  2829. msgstr ""

  2830. 

  2831. #: ../../../CHANGELOG.md:1616

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

  2833. msgstr ""

  2834. 

  2835. #: ../../../CHANGELOG.md:1618

  2836. msgid "As part of the extraction process of this role out of the Matrix playbook, a few other things improved:"

  2837. msgstr ""

  2838. 

  2839. #: ../../../CHANGELOG.md:1620

  2840. msgid "**native Traefik support** has been added"

  2841. msgstr ""

  2842. 

  2843. #: ../../../CHANGELOG.md:1621

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

  2845. msgstr ""

  2846. 

  2847. #: ../../../CHANGELOG.md:1623

  2848. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Jitsi or not."

  2849. msgstr ""

  2850. 

  2851. #: ../../../CHANGELOG.md:1625

  2852. msgid "If you're making use of Jitsi via this playbook, you will need to update variable references in your `vars.yml` file:"

  2853. msgstr ""

  2854. 

  2855. #: ../../../CHANGELOG.md:1627

  2856. msgid "`matrix_jitsi_*_docker_image_` -> `matrix_jitsi_*_container_image_`"

  2857. msgstr ""

  2858. 

  2859. #: ../../../CHANGELOG.md:1628

  2860. msgid "`matrix_jitsi_` -> `jitsi_`"

  2861. msgstr ""

  2862. 

  2863. #: ../../../CHANGELOG.md:1629

  2864. #: ../../../CHANGELOG.md:1656

  2865. msgid "some other internal variables have changed, but the playbook will tell you about them"

  2866. msgstr ""

  2867. 

  2868. #: ../../../CHANGELOG.md:1631

  2869. msgid "2023-03-22"

  2870. msgstr ""

  2871. 

  2872. #: ../../../CHANGELOG.md:1633

  2873. msgid "ntfy Web App is disabled by default"

  2874. msgstr ""

  2875. 

  2876. #: ../../../CHANGELOG.md:1635

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

  2878. msgstr ""

  2879. 

  2880. #: ../../../CHANGELOG.md:1637

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

  2882. msgstr ""

  2883. 

  2884. #: ../../../CHANGELOG.md:1640

  2885. msgid "2023-03-21"

  2886. msgstr ""

  2887. 

  2888. #: ../../../CHANGELOG.md:1642

  2889. msgid "The matrix-prometheus role lives independently now"

  2890. msgstr ""

  2891. 

  2892. #: ../../../CHANGELOG.md:1644

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

  2894. msgstr ""

  2895. 

  2896. #: ../../../CHANGELOG.md:1646

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

  2898. msgstr ""

  2899. 

  2900. #: ../../../CHANGELOG.md:1648

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

  2902. msgstr ""

  2903. 

  2904. #: ../../../CHANGELOG.md:1650

  2905. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Prometheus or not."

  2906. msgstr ""

  2907. 

  2908. #: ../../../CHANGELOG.md:1652

  2909. msgid "If you're making use of Prometheus via this playbook, you will need to update variable references in your `vars.yml` file:"

  2910. msgstr ""

  2911. 

  2912. #: ../../../CHANGELOG.md:1654

  2913. msgid "`matrix_prometheus_docker_image_` -> `matrix_prometheus_container_image_`"

  2914. msgstr ""

  2915. 

  2916. #: ../../../CHANGELOG.md:1655

  2917. msgid "`matrix_prometheus_` -> `prometheus_`"

  2918. msgstr ""

  2919. 

  2920. #: ../../../CHANGELOG.md:1659

  2921. msgid "2023-03-12"

  2922. msgstr ""

  2923. 

  2924. #: ../../../CHANGELOG.md:1661

  2925. msgid "synapse-auto-compressor support"

  2926. msgstr ""

  2927. 

  2928. #: ../../../CHANGELOG.md:1663

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

  2930. msgstr ""

  2931. 

  2932. #: ../../../CHANGELOG.md:1665

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

  2934. msgstr ""

  2935. 

  2936. #: ../../../CHANGELOG.md:1667

  2937. msgid "it runs on a more up-to-date version of `rust-synapse-compress-state`"

  2938. msgstr ""

  2939. 

  2940. #: ../../../CHANGELOG.md:1668

  2941. msgid "it's a set-it-and-forget-it tool that you can enable and never have to deal with manual compression anymore"

  2942. msgstr ""

  2943. 

  2944. #: ../../../CHANGELOG.md:1670

  2945. msgid "This tool needs to be enabled manually, for now. In the future, we're considering enabling it by default for all Synapse installations."

  2946. msgstr ""

  2947. 

  2948. #: ../../../CHANGELOG.md:1672

  2949. msgid "See our [Setting up synapse-auto-compressor](docs/configuring-playbook-synapse-auto-compressor.md) documentation to get started."

  2950. msgstr ""

  2951. 

  2952. #: ../../../CHANGELOG.md:1675

  2953. msgid "2023-03-07"

  2954. msgstr ""

  2955. 

  2956. #: ../../../CHANGELOG.md:1677

  2957. msgid "Sliding Sync proxy (Element X) support"

  2958. msgstr ""

  2959. 

  2960. #: ../../../CHANGELOG.md:1679

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

  2962. msgstr ""

  2963. 

  2964. #: ../../../CHANGELOG.md:1681

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

  2966. msgstr ""

  2967. 

  2968. #: ../../../CHANGELOG.md:1683

  2969. msgid "To get started, see our [Setting up the Sliding Sync proxy](docs/configuring-playbook-sliding-sync-proxy.md) documentation page."

  2970. msgstr ""

  2971. 

  2972. #: ../../../CHANGELOG.md:1686

  2973. msgid "2023-03-02"

  2974. msgstr ""

  2975. 

  2976. #: ../../../CHANGELOG.md:1688

  2977. msgid "The matrix-etherpad role lives independently now"

  2978. msgstr ""

  2979. 

  2980. #: ../../../CHANGELOG.md:1690

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

  2982. msgstr ""

  2983. 

  2984. #: ../../../CHANGELOG.md:1692

  2985. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Etherpad or not."

  2986. msgstr ""

  2987. 

  2988. #: ../../../CHANGELOG.md:1694

  2989. msgid "If you're making use of Etherpad via this playbook, you will need to update variable references in your `vars.yml` file:"

  2990. msgstr ""

  2991. 

  2992. #: ../../../CHANGELOG.md:1696

  2993. msgid "Rename `matrix_etherpad_public_endpoint` to `etherpad_path_prefix`"

  2994. msgstr ""

  2995. 

  2996. #: ../../../CHANGELOG.md:1698

  2997. msgid "Replace `matrix_etherpad_mode: dimension` with:"

  2998. msgstr ""

  2999. 

  3000. #: ../../../CHANGELOG.md:1699

  3001. msgid "for `matrix-nginx-proxy` users:"

  3002. msgstr ""

  3003. 

  3004. #: ../../../CHANGELOG.md:1700

  3005. msgid "`etherpad_nginx_proxy_dimension_integration_enabled: true`"

  3006. msgstr ""

  3007. 

  3008. #: ../../../CHANGELOG.md:1701

  3009. msgid "`etherpad_hostname: \"{{ matrix_server_fqn_dimension }}\"`"

  3010. msgstr ""

  3011. 

  3012. #: ../../../CHANGELOG.md:1702

  3013. msgid "for Traefik users:"

  3014. msgstr ""

  3015. 

  3016. #: ../../../CHANGELOG.md:1703

  3017. msgid "define your own `etherpad_hostname` and `etherpad_path_prefix` as you see fit"

  3018. msgstr ""

  3019. 

  3020. #: ../../../CHANGELOG.md:1705

  3021. msgid "Rename all other variables:"

  3022. msgstr ""

  3023. 

  3024. #: ../../../CHANGELOG.md:1706

  3025. msgid "`matrix_etherpad_docker_image_` -> `matrix_etherpad_container_image_`"

  3026. msgstr ""

  3027. 

  3028. #: ../../../CHANGELOG.md:1707

  3029. msgid "`matrix_etherpad_` -> `etherpad_`"

  3030. msgstr ""

  3031. 

  3032. #: ../../../CHANGELOG.md:1709

  3033. msgid "Along with this relocation, the new role also:"

  3034. msgstr ""

  3035. 

  3036. #: ../../../CHANGELOG.md:1711

  3037. msgid "supports [self-building](docs/self-building.md), so it should work on `arm32` and `arm64` architectures"

  3038. msgstr ""

  3039. 

  3040. #: ../../../CHANGELOG.md:1712

  3041. msgid "has native Traefik reverse-proxy support (Etherpad requests no longer go through `matrix-nginx-proxy` when using Traefik)"

  3042. msgstr ""

  3043. 

  3044. #: ../../../CHANGELOG.md:1715

  3045. msgid "2023-02-26"

  3046. msgstr ""

  3047. 

  3048. #: ../../../CHANGELOG.md:1717

  3049. msgid "Traefik is the default reverse-proxy now"

  3050. msgstr ""

  3051. 

  3052. #: ../../../CHANGELOG.md:1719

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

  3054. msgstr ""

  3055. 

  3056. #: ../../../CHANGELOG.md:1721

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

  3058. msgstr ""

  3059. 

  3060. #: ../../../CHANGELOG.md:1723

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

  3062. msgstr ""

  3063. 

  3064. #: ../../../CHANGELOG.md:1725

  3065. msgid "Traefik managed by the playbook"

  3066. msgstr ""

  3067. 

  3068. #: ../../../CHANGELOG.md:1726

  3069. msgid "Traefik managed by the user in another way"

  3070. msgstr ""

  3071. 

  3072. #: ../../../CHANGELOG.md:1727

  3073. msgid "another reverse-proxy on the same host (`127.0.0.1` port exposure)"

  3074. msgstr ""

  3075. 

  3076. #: ../../../CHANGELOG.md:1728

  3077. msgid "another reverse-proxy on another host (`0.0.0.0` port exposure)"

  3078. msgstr ""

  3079. 

  3080. #: ../../../CHANGELOG.md:1729

  3081. msgid "`matrix-nginx-proxy` — an `nginx` container managed by the playbook"

  3082. msgstr ""

  3083. 

  3084. #: ../../../CHANGELOG.md:1730

  3085. msgid "`nginx` webserver operated by the user, running without a container on the same server"

  3086. msgstr ""

  3087. 

  3088. #: ../../../CHANGELOG.md:1732

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

  3090. msgstr ""

  3091. 

  3092. #: ../../../CHANGELOG.md:1734

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

  3094. msgstr ""

  3095. 

  3096. #: ../../../CHANGELOG.md:1736

  3097. msgid "It's time for the **next step in our migration process** to Traefik and elimination of `matrix-nginx-proxy`:"

  3098. msgstr ""

  3099. 

  3100. #: ../../../CHANGELOG.md:1738

  3101. msgid "Traefik is now the default reverse-proxy for new installations"

  3102. msgstr ""

  3103. 

  3104. #: ../../../CHANGELOG.md:1739

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

  3106. msgstr ""

  3107. 

  3108. #: ../../../CHANGELOG.md:1741

  3109. msgid "How do I switch my existing setup to Traefik?"

  3110. msgstr ""

  3111. 

  3112. #: ../../../CHANGELOG.md:1743

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

  3114. msgstr ""

  3115. 

  3116. #: ../../../CHANGELOG.md:1745

  3117. msgid "If you experience trouble:"

  3118. msgstr ""

  3119. 

  3120. #: ../../../CHANGELOG.md:1747

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

  3122. msgstr ""

  3123. 

  3124. #: ../../../CHANGELOG.md:1748

  3125. msgid "Ask for help in our [support channels](README.md#support)"

  3126. msgstr ""

  3127. 

  3128. #: ../../../CHANGELOG.md:1749

  3129. msgid "Try switching to Traefik again later"

  3130. msgstr ""

  3131. 

  3132. #: ../../../CHANGELOG.md:1751

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

  3134. msgstr ""

  3135. 

  3136. #: ../../../CHANGELOG.md:1753

  3137. msgid "I already use my own Traefik server. How do I plug that in?"

  3138. msgstr ""

  3139. 

  3140. #: ../../../CHANGELOG.md:1755

  3141. msgid "See the [Traefik managed by the playbook](docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) section."

  3142. msgstr ""

  3143. 

  3144. #: ../../../CHANGELOG.md:1757

  3145. msgid "Why is matrix-nginx-proxy used even after switching to Traefik?"

  3146. msgstr ""

  3147. 

  3148. #: ../../../CHANGELOG.md:1759

  3149. msgid "This playbook manages many different services. All these services were initially integrated with `matrix-nginx-proxy`."

  3150. msgstr ""

  3151. 

  3152. #: ../../../CHANGELOG.md:1761

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

  3154. msgstr ""

  3155. 

  3156. #: ../../../CHANGELOG.md:1763

  3157. msgid "How do I remain on matrix-nginx-proxy?"

  3158. msgstr ""

  3159. 

  3160. #: ../../../CHANGELOG.md:1765

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

  3162. msgstr ""

  3163. 

  3164. #: ../../../CHANGELOG.md:1767

  3165. msgid "To proceed regardless of this warning, add `matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your configuration."

  3166. msgstr ""

  3167. 

  3168. #: ../../../CHANGELOG.md:1769

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

  3170. msgstr ""

  3171. 

  3172. #: ../../../CHANGELOG.md:1771

  3173. msgid "How do I keep using my own other reverse-proxy?"

  3174. msgstr ""

  3175. 

  3176. #: ../../../CHANGELOG.md:1773

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

  3178. msgstr ""

  3179. 

  3180. #: ../../../CHANGELOG.md:1776

  3181. msgid "2023-02-25"

  3182. msgstr ""

  3183. 

  3184. #: ../../../CHANGELOG.md:1778

  3185. msgid "rageshake support"

  3186. msgstr ""

  3187. 

  3188. #: ../../../CHANGELOG.md:1780

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

  3190. msgstr ""

  3191. 

  3192. #: ../../../CHANGELOG.md:1782

  3193. msgid "Additional details are available in [Setting up rageshake](docs/configuring-playbook-rageshake.md)."

  3194. msgstr ""

  3195. 

  3196. #: ../../../CHANGELOG.md:1785

  3197. msgid "2023-02-17"

  3198. msgstr ""

  3199. 

  3200. #: ../../../CHANGELOG.md:1787

  3201. msgid "Synapse templates customization support"

  3202. msgstr ""

  3203. 

  3204. #: ../../../CHANGELOG.md:1789

  3205. msgid "The playbook can now help you customize Synapse's templates."

  3206. msgstr ""

  3207. 

  3208. #: ../../../CHANGELOG.md:1791

  3209. msgid "Additional details are available in the [Customizing templates](docs/configuring-playbook-synapse.md#customizing-templates) section of our Synapse documentation."

  3210. msgstr ""

  3211. 

  3212. #: ../../../CHANGELOG.md:1793

  3213. msgid "The matrix-redis role lives independently now"

  3214. msgstr ""

  3215. 

  3216. #: ../../../CHANGELOG.md:1795

  3217. msgid "**TLDR**: the `matrix-redis` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3218. msgstr ""

  3219. 

  3220. #: ../../../CHANGELOG.md:1797

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

  3222. msgstr ""

  3223. 

  3224. #: ../../../CHANGELOG.md:1799

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

  3226. msgstr ""

  3227. 

  3228. #: ../../../CHANGELOG.md:1801

  3229. msgid "The matrix-ntfy role lives independently now"

  3230. msgstr ""

  3231. 

  3232. #: ../../../CHANGELOG.md:1803

  3233. msgid "**TLDR**: the `matrix-ntfy` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3234. msgstr ""

  3235. 

  3236. #: ../../../CHANGELOG.md:1805

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

  3238. msgstr ""

  3239. 

  3240. #: ../../../CHANGELOG.md:1807

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

  3242. msgstr ""

  3243. 

  3244. #: ../../../CHANGELOG.md:1810

  3245. msgid "2023-02-15"

  3246. msgstr ""

  3247. 

  3248. #: ../../../CHANGELOG.md:1812

  3249. msgid "The matrix-grafana role lives independently now"

  3250. msgstr ""

  3251. 

  3252. #: ../../../CHANGELOG.md:1814

  3253. msgid "**TLDR**: the `matrix-grafana` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3254. msgstr ""

  3255. 

  3256. #: ../../../CHANGELOG.md:1816

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

  3258. msgstr ""

  3259. 

  3260. #: ../../../CHANGELOG.md:1818

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

  3262. msgstr ""

  3263. 

  3264. #: ../../../CHANGELOG.md:1821

  3265. msgid "2023-02-13"

  3266. msgstr ""

  3267. 

  3268. #: ../../../CHANGELOG.md:1823

  3269. msgid "The matrix-backup-borg role lives independently now"

  3270. msgstr ""

  3271. 

  3272. #: ../../../CHANGELOG.md:1825

  3273. msgid "**TLDR**: the `matrix-backup-borg` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3274. msgstr ""

  3275. 

  3276. #: ../../../CHANGELOG.md:1827

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

  3278. msgstr ""

  3279. 

  3280. #: ../../../CHANGELOG.md:1829

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

  3282. msgstr ""

  3283. 

  3284. #: ../../../CHANGELOG.md:1832

  3285. msgid "2023-02-12"

  3286. msgstr ""

  3287. 

  3288. #: ../../../CHANGELOG.md:1834

  3289. msgid "(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support"

  3290. msgstr ""

  3291. 

  3292. #: ../../../CHANGELOG.md:1836

  3293. msgid "**TLDR**:"

  3294. msgstr ""

  3295. 

  3296. #: ../../../CHANGELOG.md:1838

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

  3298. msgstr ""

  3299. 

  3300. #: ../../../CHANGELOG.md:1839

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

  3302. msgstr ""

  3303. 

  3304. #: ../../../CHANGELOG.md:1840

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

  3306. msgstr ""

  3307. 

  3308. #: ../../../CHANGELOG.md:1841

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

  3310. msgstr ""

  3311. 

  3312. #: ../../../CHANGELOG.md:1842

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

  3314. msgstr ""

  3315. 

  3316. #: ../../../CHANGELOG.md:1844

  3317. msgid "Motivation for redoing our reverse-proxy setup"

  3318. msgstr ""

  3319. 

  3320. #: ../../../CHANGELOG.md:1846

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

  3322. msgstr ""

  3323. 

  3324. #: ../../../CHANGELOG.md:1848

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

  3326. msgstr ""

  3327. 

  3328. #: ../../../CHANGELOG.md:1850

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

  3330. msgstr ""

  3331. 

  3332. #: ../../../CHANGELOG.md:1852

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

  3334. msgstr ""

  3335. 

  3336. #: ../../../CHANGELOG.md:1854

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

  3338. msgstr ""

  3339. 

  3340. #: ../../../CHANGELOG.md:1856

  3341. msgid "*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined with exposing services manually (setting `_bind_port` variables)"

  3342. msgstr ""

  3343. 

  3344. #: ../../../CHANGELOG.md:1857

  3345. msgid "*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in `http`-only mode (no SSL certificate retrieval)."

  3346. msgstr ""

  3347. 

  3348. #: ../../../CHANGELOG.md:1859

  3349. msgid "Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations."

  3350. msgstr ""

  3351. 

  3352. #: ../../../CHANGELOG.md:1861

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

  3354. msgstr ""

  3355. 

  3356. #: ../../../CHANGELOG.md:1863

  3357. msgid "The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks:"

  3358. msgstr ""

  3359. 

  3360. #: ../../../CHANGELOG.md:1865

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

  3362. msgstr ""

  3363. 

  3364. #: ../../../CHANGELOG.md:1866

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

  3366. msgstr ""

  3367. 

  3368. #: ../../../CHANGELOG.md:1867

  3369. msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) — for hosting the [Nextcloud](https://nextcloud.com/) groupware platform"

  3370. msgstr ""

  3371. 

  3372. #: ../../../CHANGELOG.md:1869

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

  3374. msgstr ""

  3375. 

  3376. #: ../../../CHANGELOG.md:1871

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

  3378. msgstr ""

  3379. 

  3380. #: ../../../CHANGELOG.md:1873

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

  3382. msgstr ""

  3383. 

  3384. #: ../../../CHANGELOG.md:1875

  3385. msgid "How do these changes fix all these problems?"

  3386. msgstr ""

  3387. 

  3388. #: ../../../CHANGELOG.md:1877

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

  3390. msgstr ""

  3391. 

  3392. #: ../../../CHANGELOG.md:1879

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

  3394. msgstr ""

  3395. 

  3396. #: ../../../CHANGELOG.md:1881

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

  3398. msgstr ""

  3399. 

  3400. #: ../../../CHANGELOG.md:1883

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

  3402. msgstr ""

  3403. 

  3404. #: ../../../CHANGELOG.md:1885

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

  3406. msgstr ""

  3407. 

  3408. #: ../../../CHANGELOG.md:1887

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

  3410. msgstr ""

  3411. 

  3412. #: ../../../CHANGELOG.md:1889

  3413. msgid "Where we're at right now?"

  3414. msgstr ""

  3415. 

  3416. #: ../../../CHANGELOG.md:1891

  3417. msgid "`matrix_playbook_reverse_proxy_type` still defaults to a value of `playbook-managed-nginx`."

  3418. msgstr ""

  3419. 

  3420. #: ../../../CHANGELOG.md:1893

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

  3422. msgstr ""

  3423. 

  3424. #: ../../../CHANGELOG.md:1895

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

  3426. msgstr ""

  3427. 

  3428. #: ../../../CHANGELOG.md:1897

  3429. msgid "How do I explicitly switch to Traefik right now?"

  3430. msgstr ""

  3431. 

  3432. #: ../../../CHANGELOG.md:1899

  3433. msgid "**Users who wish to migrate to Traefik** today, can do so by **adding** this to their configuration:"

  3434. msgstr ""

  3435. 

  3436. #: ../../../CHANGELOG.md:1905

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

  3438. msgstr ""

  3439. 

  3440. #: ../../../CHANGELOG.md:1907

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

  3442. msgstr ""

  3443. 

  3444. #: ../../../CHANGELOG.md:1909

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

  3446. msgstr ""

  3447. 

  3448. #: ../../../CHANGELOG.md:1911

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

  3450. msgstr ""

  3451. 

  3452. #: ../../../CHANGELOG.md:1913

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

  3454. msgstr ""

  3455. 

  3456. #: ../../../CHANGELOG.md:1915

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

  3458. msgstr ""

  3459. 

  3460. #: ../../../CHANGELOG.md:1917

  3461. msgid "Where we're going in the near future?"

  3462. msgstr ""

  3463. 

  3464. #: ../../../CHANGELOG.md:1919

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

  3466. msgstr ""

  3467. 

  3468. #: ../../../CHANGELOG.md:1921

  3469. msgid "For now, `matrix-nginx-proxy` will stay around."

  3470. msgstr ""

  3471. 

  3472. #: ../../../CHANGELOG.md:1923

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

  3474. msgstr ""

  3475. 

  3476. #: ../../../CHANGELOG.md:1925

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

  3478. msgstr ""

  3479. 

  3480. #: ../../../CHANGELOG.md:1927

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

  3482. msgstr ""

  3483. 

  3484. #: ../../../CHANGELOG.md:1928

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

  3486. msgstr ""

  3487. 

  3488. #: ../../../CHANGELOG.md:1930

  3489. msgid "How do I help?"

  3490. msgstr ""

  3491. 

  3492. #: ../../../CHANGELOG.md:1932

  3493. msgid "You can help by:"

  3494. msgstr ""

  3495. 

  3496. #: ../../../CHANGELOG.md:1934

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

  3498. msgstr ""

  3499. 

  3500. #: ../../../CHANGELOG.md:1936

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

  3502. msgstr ""

  3503. 

  3504. #: ../../../CHANGELOG.md:1938

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

  3506. msgstr ""

  3507. 

  3508. #: ../../../CHANGELOG.md:1941

  3509. msgid "2023-02-10"

  3510. msgstr ""

  3511. 

  3512. #: ../../../CHANGELOG.md:1943

  3513. msgid "Matrix Authentication Support for Jitsi"

  3514. msgstr ""

  3515. 

  3516. #: ../../../CHANGELOG.md:1945

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

  3518. msgstr ""

  3519. 

  3520. #: ../../../CHANGELOG.md:1947

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

  3522. msgstr ""

  3523. 

  3524. #: ../../../CHANGELOG.md:1949

  3525. msgid "Draupnir moderation tool (bot) support"

  3526. msgstr ""

  3527. 

  3528. #: ../../../CHANGELOG.md:1951

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

  3530. msgstr ""

  3531. 

  3532. #: ../../../CHANGELOG.md:1953

  3533. msgid "Additional details are available in [Setting up Draupnir](docs/configuring-playbook-bot-draupnir.md)."

  3534. msgstr ""

  3535. 

  3536. #: ../../../CHANGELOG.md:1956

  3537. msgid "2023-02-05"

  3538. msgstr ""

  3539. 

  3540. #: ../../../CHANGELOG.md:1958

  3541. msgid "The matrix-prometheus-postgres-exporter role lives independently now"

  3542. msgstr ""

  3543. 

  3544. #: ../../../CHANGELOG.md:1960

  3545. msgid "**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3546. msgstr ""

  3547. 

  3548. #: ../../../CHANGELOG.md:1962

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

  3550. msgstr ""

  3551. 

  3552. #: ../../../CHANGELOG.md:1964

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

  3554. msgstr ""

  3555. 

  3556. #: ../../../CHANGELOG.md:1966

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

  3558. msgstr ""

  3559. 

  3560. #: ../../../CHANGELOG.md:1968

  3561. #: ../../../CHANGELOG.md:2010

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

  3563. msgstr ""

  3564. 

  3565. #: ../../../CHANGELOG.md:1971

  3566. msgid "2023-01-26"

  3567. msgstr ""

  3568. 

  3569. #: ../../../CHANGELOG.md:1973

  3570. msgid "coturn can now use host-networking"

  3571. msgstr ""

  3572. 

  3573. #: ../../../CHANGELOG.md:1975

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

  3575. msgstr ""

  3576. 

  3577. #: ../../../CHANGELOG.md:1977

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

  3579. msgstr ""

  3580. 

  3581. #: ../../../CHANGELOG.md:1983

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

  3583. msgstr ""

  3584. 

  3585. #: ../../../CHANGELOG.md:1985

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

  3587. msgstr ""

  3588. 

  3589. #: ../../../CHANGELOG.md:1987

  3590. msgid "(Backward Compatibility) Tightening coturn security can lead to connectivity issues"

  3591. msgstr ""

  3592. 

  3593. #: ../../../CHANGELOG.md:1989

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

  3595. msgstr ""

  3596. 

  3597. #: ../../../CHANGELOG.md:1991

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

  3599. msgstr ""

  3600. 

  3601. #: ../../../CHANGELOG.md:1993

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

  3603. msgstr ""

  3604. 

  3605. #: ../../../CHANGELOG.md:1995

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

  3607. msgstr ""

  3608. 

  3609. #: ../../../CHANGELOG.md:1998

  3610. msgid "2023-01-21"

  3611. msgstr ""

  3612. 

  3613. #: ../../../CHANGELOG.md:2000

  3614. msgid "The matrix-prometheus-node-exporter role lives independently now"

  3615. msgstr ""

  3616. 

  3617. #: ../../../CHANGELOG.md:2002

  3618. msgid "**TLDR**: the `matrix-prometheus-node-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3619. msgstr ""

  3620. 

  3621. #: ../../../CHANGELOG.md:2004

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

  3623. msgstr ""

  3624. 

  3625. #: ../../../CHANGELOG.md:2006

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

  3627. msgstr ""

  3628. 

  3629. #: ../../../CHANGELOG.md:2008

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

  3631. msgstr ""

  3632. 

  3633. #: ../../../CHANGELOG.md:2013

  3634. msgid "2023-01-13"

  3635. msgstr ""

  3636. 

  3637. #: ../../../CHANGELOG.md:2015

  3638. msgid "Support for running commands via just"

  3639. msgstr ""

  3640. 

  3641. #: ../../../CHANGELOG.md:2017

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

  3643. msgstr ""

  3644. 

  3645. #: ../../../CHANGELOG.md:2019

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

  3647. msgstr ""

  3648. 

  3649. #: ../../../CHANGELOG.md:2021

  3650. msgid "Our [justfile](justfile) already defines some additional helpful **shortcut** commands that weren't part of our `Makefile`. Here are some examples:"

  3651. msgstr ""

  3652. 

  3653. #: ../../../CHANGELOG.md:2023

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

  3655. msgstr ""

  3656. 

  3657. #: ../../../CHANGELOG.md:2024

  3658. msgid "`just install-all --ask-vault-pass` — commands also support additional arguments (`--ask-vault-pass` will be appended to the above installation command)"

  3659. msgstr ""

  3660. 

  3661. #: ../../../CHANGELOG.md:2025

  3662. msgid "`just run-tags install-mautrix-slack,start` — to run specific playbook tags"

  3663. msgstr ""

  3664. 

  3665. #: ../../../CHANGELOG.md:2026

  3666. msgid "`just start-all` — (re-)starts all services"

  3667. msgstr ""

  3668. 

  3669. #: ../../../CHANGELOG.md:2027

  3670. msgid "`just stop-group postgres` — to stop only the Postgres service"

  3671. msgstr ""

  3672. 

  3673. #: ../../../CHANGELOG.md:2028

  3674. msgid "`just register-user alice secret-password yes` — registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)"

  3675. msgstr ""

  3676. 

  3677. #: ../../../CHANGELOG.md:2030

  3678. msgid "Additional helpful commands and shortcuts may be defined in the future."

  3679. msgstr ""

  3680. 

  3681. #: ../../../CHANGELOG.md:2032

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

  3683. msgstr ""

  3684. 

  3685. #: ../../../CHANGELOG.md:2035

  3686. msgid "2023-01-11"

  3687. msgstr ""

  3688. 

  3689. #: ../../../CHANGELOG.md:2037

  3690. msgid "mautrix-slack support"

  3691. msgstr ""

  3692. 

  3693. #: ../../../CHANGELOG.md:2039

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

  3695. msgstr ""

  3696. 

  3697. #: ../../../CHANGELOG.md:2041

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

  3699. msgstr ""

  3700. 

  3701. #: ../../../CHANGELOG.md:2044

  3702. msgid "2023-01-10"

  3703. msgstr ""

  3704. 

  3705. #: ../../../CHANGELOG.md:2046

  3706. msgid "ChatGPT support"

  3707. msgstr ""

  3708. 

  3709. #: ../../../CHANGELOG.md:2048

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

  3711. msgstr ""

  3712. 

  3713. #: ../../../CHANGELOG.md:2050

  3714. msgid "See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-chatgpt.md) documentation to get started."

  3715. msgstr ""

  3716. 

  3717. #: ../../../CHANGELOG.md:2053

  3718. msgid "2022-11-30"

  3719. msgstr ""

  3720. 

  3721. #: ../../../CHANGELOG.md:2055

  3722. msgid "matrix-postgres-backup has been replaced by the ansible-role-postgres-backup external role"

  3723. msgstr ""

  3724. 

  3725. #: ../../../CHANGELOG.md:2057

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

  3727. msgstr ""

  3728. 

  3729. #: ../../../CHANGELOG.md:2059

  3730. msgid "You'll need to rename your `matrix_postgres_backup`-prefixed variables such that they use a `postgres_backup` prefix."

  3731. msgstr ""

  3732. 

  3733. #: ../../../CHANGELOG.md:2062

  3734. msgid "2022-11-28"

  3735. msgstr ""

  3736. 

  3737. #: ../../../CHANGELOG.md:2064

  3738. msgid "matrix-postgres has been replaced by the ansible-role-postgres external role"

  3739. msgstr ""

  3740. 

  3741. #: ../../../CHANGELOG.md:2066

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

  3743. msgstr ""

  3744. 

  3745. #: ../../../CHANGELOG.md:2068

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

  3747. msgstr ""

  3748. 

  3749. #: ../../../CHANGELOG.md:2070

  3750. msgid "The new role is an upgraded version of the old `matrix-postgres` role with these notable differences:"

  3751. msgstr ""

  3752. 

  3753. #: ../../../CHANGELOG.md:2072

  3754. msgid "it uses different names for its variables (`matrix_postgres` -> `devture_postgres`)"

  3755. msgstr ""

  3756. 

  3757. #: ../../../CHANGELOG.md:2073

  3758. msgid "when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-postgresql), it will vacuum all your databases, not just the Synapse one"

  3759. msgstr ""

  3760. 

  3761. #: ../../../CHANGELOG.md:2075

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

  3763. msgstr ""

  3764. 

  3765. #: ../../../CHANGELOG.md:2077

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

  3767. msgstr ""

  3768. 

  3769. #: ../../../CHANGELOG.md:2079

  3770. msgid "The playbook no longer installs scripts to /usr/local/bin"

  3771. msgstr ""

  3772. 

  3773. #: ../../../CHANGELOG.md:2081

  3774. msgid "The locations of various scripts installed by the playbook have changed."

  3775. msgstr ""

  3776. 

  3777. #: ../../../CHANGELOG.md:2083

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

  3779. msgstr ""

  3780. 

  3781. #: ../../../CHANGELOG.md:2085

  3782. msgid "`/usr/local/bin/matrix-remove-all` -> `/matrix/bin/remove-all`"

  3783. msgstr ""

  3784. 

  3785. #: ../../../CHANGELOG.md:2086

  3786. msgid "`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`"

  3787. msgstr ""

  3788. 

  3789. #: ../../../CHANGELOG.md:2087

  3790. msgid "`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> `/matrix/ssl/bin/lets-encrypt-certificates-renew`"

  3791. msgstr ""

  3792. 

  3793. #: ../../../CHANGELOG.md:2088

  3794. msgid "`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin/register-user`"

  3795. msgstr ""

  3796. 

  3797. #: ../../../CHANGELOG.md:2091

  3798. msgid "2022-11-25"

  3799. msgstr ""

  3800. 

  3801. #: ../../../CHANGELOG.md:2093

  3802. msgid "2x-5x performance improvements in playbook runtime"

  3803. msgstr ""

  3804. 

  3805. #: ../../../CHANGELOG.md:2095

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

  3807. msgstr ""

  3808. 

  3809. #: ../../../CHANGELOG.md:2097

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

  3811. msgstr ""

  3812. 

  3813. #: ../../../CHANGELOG.md:2099

  3814. msgid "Even when running `ansible-playbook` manually (as most of us here do), it's beneficial not to waste time and CPU resources."

  3815. msgstr ""

  3816. 

  3817. #: ../../../CHANGELOG.md:2101

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

  3819. msgstr ""

  3820. 

  3821. #: ../../../CHANGELOG.md:2103

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

  3823. msgstr ""

  3824. 

  3825. #: ../../../CHANGELOG.md:2105

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

  3827. msgstr ""

  3828. 

  3829. #: ../../../CHANGELOG.md:2107

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

  3831. msgstr ""

  3832. 

  3833. #: ../../../CHANGELOG.md:2109

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

  3835. msgstr ""

  3836. 

  3837. #: ../../../CHANGELOG.md:2112

  3838. msgid "2022-11-22"

  3839. msgstr ""

  3840. 

  3841. #: ../../../CHANGELOG.md:2114

  3842. msgid "Automatic `matrix_architecture` determination"

  3843. msgstr ""

  3844. 

  3845. #: ../../../CHANGELOG.md:2116

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

  3847. msgstr ""

  3848. 

  3849. #: ../../../CHANGELOG.md:2118

  3850. msgid "Docker and the Docker SDK for Python are now installed via external roles"

  3851. msgstr ""

  3852. 

  3853. #: ../../../CHANGELOG.md:2122

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

  3855. msgstr ""

  3856. 

  3857. #: ../../../CHANGELOG.md:2124

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

  3859. msgstr ""

  3860. 

  3861. #: ../../../CHANGELOG.md:2126

  3862. msgid "If you're hitting issues with Docker installation or Docker SDK for Python installation, consider reporting bugs or contributing to these other projects."

  3863. msgstr ""

  3864. 

  3865. #: ../../../CHANGELOG.md:2128

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

  3867. msgstr ""

  3868. 

  3869. #: ../../../CHANGELOG.md:2131

  3870. msgid "2022-11-20"

  3871. msgstr ""

  3872. 

  3873. #: ../../../CHANGELOG.md:2133

  3874. msgid "(Backward Compatibility Break) Changing how reverse-proxying to Synapse works — now via a `matrix-synapse-reverse-proxy-companion` service"

  3875. msgstr ""

  3876. 

  3877. #: ../../../CHANGELOG.md:2135

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

  3879. msgstr ""

  3880. 

  3881. #: ../../../CHANGELOG.md:2137

  3882. msgid "Background"

  3883. msgstr ""

  3884. 

  3885. #: ../../../CHANGELOG.md:2139

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

  3887. msgstr ""

  3888. 

  3889. #: ../../../CHANGELOG.md:2141

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

  3891. msgstr ""

  3892. 

  3893. #: ../../../CHANGELOG.md:2143

  3894. msgid "Solution"

  3895. msgstr ""

  3896. 

  3897. #: ../../../CHANGELOG.md:2145

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

  3899. msgstr ""

  3900. 

  3901. #: ../../../CHANGELOG.md:2147

  3902. msgid "serve as a companion to Synapse and know how to reverse-proxy to Synapse correctly (no matter if workers are enabled or not)"

  3903. msgstr ""

  3904. 

  3905. #: ../../../CHANGELOG.md:2149

  3906. msgid "provide a unified container address for reaching Synapse (no matter if workers are enabled or not)"

  3907. msgstr ""

  3908. 

  3909. #: ../../../CHANGELOG.md:2150

  3910. msgid "`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server API traffic"

  3911. msgstr ""

  3912. 

  3913. #: ../../../CHANGELOG.md:2151

  3914. msgid "`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server (Federation) API traffic"

  3915. msgstr ""

  3916. 

  3917. #: ../../../CHANGELOG.md:2153

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

  3919. msgstr ""

  3920. 

  3921. #: ../../../CHANGELOG.md:2155

  3922. msgid "allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is disabled"

  3923. msgstr ""

  3924. 

  3925. #: ../../../CHANGELOG.md:2157

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

  3927. msgstr ""

  3928. 

  3929. #: ../../../CHANGELOG.md:2159

  3930. msgid "(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> (`matrix-synapse` or some Synapse worker))."

  3931. msgstr ""

  3932. 

  3933. #: ../../../CHANGELOG.md:2161

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

  3935. msgstr ""

  3936. 

  3937. #: ../../../CHANGELOG.md:2163

  3938. msgid "Webserver configuration"

  3939. msgstr ""

  3940. 

  3941. #: ../../../CHANGELOG.md:2165

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

  3943. msgstr ""

  3944. 

  3945. #: ../../../CHANGELOG.md:2167

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

  3947. msgstr ""

  3948. 

  3949. #: ../../../CHANGELOG.md:2169

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

  3951. msgstr ""

  3952. 

  3953. #: ../../../CHANGELOG.md:2171

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

  3955. msgstr ""

  3956. 

  3957. #: ../../../CHANGELOG.md:2173

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

  3959. msgstr ""

  3960. 

  3961. #: ../../../CHANGELOG.md:2176

  3962. msgid "2022-11-05"

  3963. msgstr ""

  3964. 

  3965. #: ../../../CHANGELOG.md:2178

  3966. msgid "(Backward Compatibility Break) A new default standalone mode for Etherpad"

  3967. msgstr ""

  3968. 

  3969. #: ../../../CHANGELOG.md:2180

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

  3971. msgstr ""

  3972. 

  3973. #: ../../../CHANGELOG.md:2182

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

  3975. msgstr ""

  3976. 

  3977. #: ../../../CHANGELOG.md:2184

  3978. msgid "If you've already got both Etherpad and Dimension in use you could:"

  3979. msgstr ""

  3980. 

  3981. #: ../../../CHANGELOG.md:2186

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

  3983. msgstr ""

  3984. 

  3985. #: ../../../CHANGELOG.md:2188

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

  3987. msgstr ""

  3988. 

  3989. #: ../../../CHANGELOG.md:2191

  3990. msgid "2022-11-04"

  3991. msgstr ""

  3992. 

  3993. #: ../../../CHANGELOG.md:2193

  3994. msgid "The playbook now uses external roles for some things"

  3995. msgstr ""

  3996. 

  3997. #: ../../../CHANGELOG.md:2195

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

  3999. msgstr ""

  4000. 

  4001. #: ../../../CHANGELOG.md:2197

  4002. msgid "We're in the process of trimming the playbook and making it reuse Ansible roles."

  4003. msgstr ""

  4004. 

  4005. #: ../../../CHANGELOG.md:2199

  4006. msgid "Starting now, the playbook is composed of 2 types of Ansible roles:"

  4007. msgstr ""

  4008. 

  4009. #: ../../../CHANGELOG.md:2201

  4010. msgid "those that live within the playbook itself (`roles/custom/*`)"

  4011. msgstr ""

  4012. 

  4013. #: ../../../CHANGELOG.md:2203

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

  4015. msgstr ""

  4016. 

  4017. #: ../../../CHANGELOG.md:2205

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

  4019. msgstr ""

  4020. 

  4021. #: ../../../CHANGELOG.md:2207

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

  4023. msgstr ""

  4024. 

  4025. #: ../../../CHANGELOG.md:2209

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

  4027. msgstr ""

  4028. 

  4029. #: ../../../CHANGELOG.md:2212

  4030. msgid "2022-10-14"

  4031. msgstr ""

  4032. 

  4033. #: ../../../CHANGELOG.md:2214

  4034. msgid "synapse-s3-storage-provider support"

  4035. msgstr ""

  4036. 

  4037. #: ../../../CHANGELOG.md:2216

  4038. msgid "**`synapse-s3-storage-provider` support is very new and still relatively untested. Using it may cause data loss.**"

  4039. msgstr ""

  4040. 

  4041. #: ../../../CHANGELOG.md:2218

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

  4043. msgstr ""

  4044. 

  4045. #: ../../../CHANGELOG.md:2220

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

  4047. msgstr ""

  4048. 

  4049. #: ../../../CHANGELOG.md:2222

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

  4051. msgstr ""

  4052. 

  4053. #: ../../../CHANGELOG.md:2224

  4054. msgid "Synapse container image customization support"

  4055. msgstr ""

  4056. 

  4057. #: ../../../CHANGELOG.md:2226

  4058. msgid "We now support customizing the Synapse container image by adding additional build steps to its [`Dockerfile`](https://docs.docker.com/engine/reference/builder/)."

  4059. msgstr ""

  4060. 

  4061. #: ../../../CHANGELOG.md:2228

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

  4063. msgstr ""

  4064. 

  4065. #: ../../../CHANGELOG.md:2230

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

  4067. msgstr ""

  4068. 

  4069. #: ../../../CHANGELOG.md:2241

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

  4071. msgstr ""

  4072. 

  4073. #: ../../../CHANGELOG.md:2243

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

  4075. msgstr ""

  4076. 

  4077. #: ../../../CHANGELOG.md:2246

  4078. msgid "2022-10-02"

  4079. msgstr ""

  4080. 

  4081. #: ../../../CHANGELOG.md:2248

  4082. msgid "matrix-ldap-registration-proxy support"

  4083. msgstr ""

  4084. 

  4085. #: ../../../CHANGELOG.md:2250

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

  4087. msgstr ""

  4088. 

  4089. #: ../../../CHANGELOG.md:2252

  4090. msgid "See our [Setting up matrix-ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started."

  4091. msgstr ""

  4092. 

  4093. #: ../../../CHANGELOG.md:2255

  4094. msgid "2022-09-15"

  4095. msgstr ""

  4096. 

  4097. #: ../../../CHANGELOG.md:2257

  4098. msgid "(Potential Backward Compatibility Break) Major improvements to Synapse workers"

  4099. msgstr ""

  4100. 

  4101. #: ../../../CHANGELOG.md:2259

  4102. msgid "People who are interested in running a Synapse worker setup should know that **our Synapse worker implementation is much more powerful now**:"

  4103. msgstr ""

  4104. 

  4105. #: ../../../CHANGELOG.md:2261

  4106. msgid "we've added support for [Stream writers](#stream-writers-support)"

  4107. msgstr ""

  4108. 

  4109. #: ../../../CHANGELOG.md:2262

  4110. msgid "we've added support for [multiple federation sender workers](#multiple-federation-sender-workers-support)"

  4111. msgstr ""

  4112. 

  4113. #: ../../../CHANGELOG.md:2263

  4114. msgid "we've added support for [multiple pusher workers](#multiple-pusher-workers-support)"

  4115. msgstr ""

  4116. 

  4117. #: ../../../CHANGELOG.md:2264

  4118. msgid "we've added support for [running background tasks on a worker](#background-tasks-can-run-on-a-worker)"

  4119. msgstr ""

  4120. 

  4121. #: ../../../CHANGELOG.md:2265

  4122. msgid "we've restored support for [`appservice` workers](#appservice-worker-support-is-back)"

  4123. msgstr ""

  4124. 

  4125. #: ../../../CHANGELOG.md:2266

  4126. msgid "we've restored support for [`user_dir` workers](#user-directory-worker-support-is-back)"

  4127. msgstr ""

  4128. 

  4129. #: ../../../CHANGELOG.md:2267

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

  4131. msgstr ""

  4132. 

  4133. #: ../../../CHANGELOG.md:2268

  4134. msgid "see the [Potential Backward Incompatibilities after these Synapse worker changes](#potential-backward-incompatibilities-after-these-synapse-worker-changes)"

  4135. msgstr ""

  4136. 

  4137. #: ../../../CHANGELOG.md:2270

  4138. msgid "Stream writers support"

  4139. msgstr ""

  4140. 

  4141. #: ../../../CHANGELOG.md:2272

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

  4143. msgstr ""

  4144. 

  4145. #: ../../../CHANGELOG.md:2274

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

  4147. msgstr ""

  4148. 

  4149. #: ../../../CHANGELOG.md:2276

  4150. msgid "If you'd like to customize the number of workers we also make that possible using these variables:"

  4151. msgstr ""

  4152. 

  4153. #: ../../../CHANGELOG.md:2289

  4154. msgid "Multiple federation sender workers support"

  4155. msgstr ""

  4156. 

  4157. #: ../../../CHANGELOG.md:2291

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

  4159. msgstr ""

  4160. 

  4161. #: ../../../CHANGELOG.md:2293

  4162. msgid "Multiple pusher workers support"

  4163. msgstr ""

  4164. 

  4165. #: ../../../CHANGELOG.md:2295

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

  4167. msgstr ""

  4168. 

  4169. #: ../../../CHANGELOG.md:2297

  4170. msgid "Background tasks can run on a worker"

  4171. msgstr ""

  4172. 

  4173. #: ../../../CHANGELOG.md:2299

  4174. msgid "From now on, you can put [background task processing on a worker](https://matrix-org.github.io/synapse/latest/workers.html#background-tasks)."

  4175. msgstr ""

  4176. 

  4177. #: ../../../CHANGELOG.md:2301

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

  4179. msgstr ""

  4180. 

  4181. #: ../../../CHANGELOG.md:2303

  4182. msgid "Appservice worker support is back"

  4183. msgstr ""

  4184. 

  4185. #: ../../../CHANGELOG.md:2305

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

  4187. msgstr ""

  4188. 

  4189. #: ../../../CHANGELOG.md:2307

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

  4191. msgstr ""

  4192. 

  4193. #: ../../../CHANGELOG.md:2309

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

  4195. msgstr ""

  4196. 

  4197. #: ../../../CHANGELOG.md:2311

  4198. msgid "User Directory worker support is back"

  4199. msgstr ""

  4200. 

  4201. #: ../../../CHANGELOG.md:2313

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

  4203. msgstr ""

  4204. 

  4205. #: ../../../CHANGELOG.md:2315

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

  4207. msgstr ""

  4208. 

  4209. #: ../../../CHANGELOG.md:2317

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

  4211. msgstr ""

  4212. 

  4213. #: ../../../CHANGELOG.md:2319

  4214. msgid "Using more than 1 media repository worker is now more reliable"

  4215. msgstr ""

  4216. 

  4217. #: ../../../CHANGELOG.md:2321

  4218. msgid "With `matrix_synapse_workers_preset: one-of-each`, we only launch one `media_repository` worker."

  4219. msgstr ""

  4220. 

  4221. #: ../../../CHANGELOG.md:2323

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

  4223. msgstr ""

  4224. 

  4225. #: ../../../CHANGELOG.md:2325

  4226. msgid "Potential Backward Incompatibilities after these Synapse worker changes"

  4227. msgstr ""

  4228. 

  4229. #: ../../../CHANGELOG.md:2327

  4230. msgid "Below we'll discuss **potential backward incompatibilities**."

  4231. msgstr ""

  4232. 

  4233. #: ../../../CHANGELOG.md:2329

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

  4235. msgstr ""

  4236. 

  4237. #: ../../../CHANGELOG.md:2331

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

  4239. msgstr ""

  4240. 

  4241. #: ../../../CHANGELOG.md:2333

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

  4243. msgstr ""

  4244. 

  4245. #: ../../../CHANGELOG.md:2335

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

  4247. msgstr ""

  4248. 

  4249. #: ../../../CHANGELOG.md:2338

  4250. msgid "2022-09-09"

  4251. msgstr ""

  4252. 

  4253. #: ../../../CHANGELOG.md:2340

  4254. msgid "Cactus Comments support"

  4255. msgstr ""

  4256. 

  4257. #: ../../../CHANGELOG.md:2342

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

  4259. msgstr ""

  4260. 

  4261. #: ../../../CHANGELOG.md:2344

  4262. msgid "See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-comments.md) documentation to get started."

  4263. msgstr ""

  4264. 

  4265. #: ../../../CHANGELOG.md:2347

  4266. msgid "2022-08-23"

  4267. msgstr ""

  4268. 

  4269. #: ../../../CHANGELOG.md:2349

  4270. msgid "Postmoogle email bridge support"

  4271. msgstr ""

  4272. 

  4273. #: ../../../CHANGELOG.md:2351

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

  4275. msgstr ""

  4276. 

  4277. #: ../../../CHANGELOG.md:2353

  4278. msgid "See our [Setting up Postmoogle email bridging](docs/configuring-playbook-bridge-postmoogle.md) documentation to get started."

  4279. msgstr ""

  4280. 

  4281. #: ../../../CHANGELOG.md:2356

  4282. msgid "2022-08-10"

  4283. msgstr ""

  4284. 

  4285. #: ../../../CHANGELOG.md:2358

  4286. msgid "mautrix-whatsapp default configuration changes"

  4287. msgstr ""

  4288. 

  4289. #: ../../../CHANGELOG.md:2360

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

  4291. msgstr ""

  4292. 

  4293. #: ../../../CHANGELOG.md:2362

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

  4295. msgstr ""

  4296. 

  4297. #: ../../../CHANGELOG.md:2364

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

  4299. msgstr ""

  4300. 

  4301. #: ../../../CHANGELOG.md:2367

  4302. msgid "2022-08-09"

  4303. msgstr ""

  4304. 

  4305. #: ../../../CHANGELOG.md:2369

  4306. msgid "Conduit support"

  4307. msgstr ""

  4308. 

  4309. #: ../../../CHANGELOG.md:2371

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

  4311. msgstr ""

  4312. 

  4313. #: ../../../CHANGELOG.md:2373

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

  4315. msgstr ""

  4316. 

  4317. #: ../../../CHANGELOG.md:2375

  4318. msgid "To try out Conduit, we recommend that you **use a new server** and the following `vars.yml` configuration:"

  4319. msgstr ""

  4320. 

  4321. #: ../../../CHANGELOG.md:2381

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

  4323. msgstr ""

  4324. 

  4325. #: ../../../CHANGELOG.md:2384

  4326. msgid "2022-07-29"

  4327. msgstr ""

  4328. 

  4329. #: ../../../CHANGELOG.md:2386

  4330. msgid "mautrix-discord support"

  4331. msgstr ""

  4332. 

  4333. #: ../../../CHANGELOG.md:2388

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

  4335. msgstr ""

  4336. 

  4337. #: ../../../CHANGELOG.md:2390

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

  4339. msgstr ""

  4340. 

  4341. #: ../../../CHANGELOG.md:2393

  4342. msgid "2022-07-27"

  4343. msgstr ""

  4344. 

  4345. #: ../../../CHANGELOG.md:2395

  4346. msgid "matrix-appservice-kakaotalk support"

  4347. msgstr ""

  4348. 

  4349. #: ../../../CHANGELOG.md:2397

  4350. 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!"

  4351. msgstr ""

  4352. 

  4353. #: ../../../CHANGELOG.md:2399

  4354. msgid "See our [Setting up Appservice Kakaotalk bridging](docs/configuring-playbook-bridge-appservice-kakaotalk.md) documentation to get started."

  4355. msgstr ""

  4356. 

  4357. #: ../../../CHANGELOG.md:2402

  4358. msgid "2022-07-20"

  4359. msgstr ""

  4360. 

  4361. #: ../../../CHANGELOG.md:2404

  4362. msgid "maubot support"

  4363. msgstr ""

  4364. 

  4365. #: ../../../CHANGELOG.md:2406

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

  4367. msgstr ""

  4368. 

  4369. #: ../../../CHANGELOG.md:2408

  4370. msgid "See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) documentation to get started."

  4371. msgstr ""

  4372. 

  4373. #: ../../../CHANGELOG.md:2411

  4374. msgid "2022-07-14"

  4375. msgstr ""

  4376. 

  4377. #: ../../../CHANGELOG.md:2413

  4378. msgid "mx-puppet-skype removal"

  4379. msgstr ""

  4380. 

  4381. #: ../../../CHANGELOG.md:2415

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

  4383. msgstr ""

  4384. 

  4385. #: ../../../CHANGELOG.md:2417

  4386. msgid "To completely clean up your server from `mx-puppet-skype`'s presence on it:"

  4387. msgstr ""

  4388. 

  4389. #: ../../../CHANGELOG.md:2419

  4390. msgid "ensure your Ansible configuration (`vars.yml` file) no longer contains `matrix_mx_puppet_skype_*` references"

  4391. msgstr ""

  4392. 

  4393. #: ../../../CHANGELOG.md:2420

  4394. msgid "stop and disable the systemd service (run `systemctl disable --now matrix-mx-puppet-skype` on the server)"

  4395. msgstr ""

  4396. 

  4397. #: ../../../CHANGELOG.md:2421

  4398. msgid "delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-skype.service` on the server)"

  4399. msgstr ""

  4400. 

  4401. #: ../../../CHANGELOG.md:2422

  4402. msgid "delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on the server)"

  4403. msgstr ""

  4404. 

  4405. #: ../../../CHANGELOG.md:2423

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

  4407. msgstr ""

  4408. 

  4409. #: ../../../CHANGELOG.md:2425

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

  4411. msgstr ""

  4412. 

  4413. #: ../../../CHANGELOG.md:2427

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

  4415. msgstr ""

  4416. 

  4417. #: ../../../CHANGELOG.md:2429

  4418. msgid "signald (0.19.0+) upgrade requires data migration"

  4419. msgstr ""

  4420. 

  4421. #: ../../../CHANGELOG.md:2431

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

  4423. msgstr ""

  4424. 

  4425. #: ../../../CHANGELOG.md:2433

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

  4427. msgstr ""

  4428. 

  4429. #: ../../../CHANGELOG.md:2435

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

  4431. msgstr ""

  4432. 

  4433. #: ../../../CHANGELOG.md:2437

  4434. msgid "We attempt to do this data migration automatically every time Signald starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` systemd unit definition."

  4435. msgstr ""

  4436. 

  4437. #: ../../../CHANGELOG.md:2439

  4438. 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!"

  4439. msgstr ""

  4440. 

  4441. #: ../../../CHANGELOG.md:2442

  4442. msgid "2022-07-05"

  4443. msgstr ""

  4444. 

  4445. #: ../../../CHANGELOG.md:2444

  4446. msgid "Ntfy push notifications support"

  4447. msgstr ""

  4448. 

  4449. #: ../../../CHANGELOG.md:2446

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

  4451. msgstr ""

  4452. 

  4453. #: ../../../CHANGELOG.md:2448

  4454. msgid "See our [Setting up the ntfy push notifications server](docs/configuring-playbook-ntfy.md) documentation to get started."

  4455. msgstr ""

  4456. 

  4457. #: ../../../CHANGELOG.md:2451

  4458. msgid "2022-06-23"

  4459. msgstr ""

  4460. 

  4461. #: ../../../CHANGELOG.md:2453

  4462. msgid "(Potential Backward Compatibility Break) Changes around metrics collection"

  4463. msgstr ""

  4464. 

  4465. #: ../../../CHANGELOG.md:2455

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

  4467. msgstr ""

  4468. 

  4469. #: ../../../CHANGELOG.md:2457

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

  4471. msgstr ""

  4472. 

  4473. #: ../../../CHANGELOG.md:2459

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

  4475. msgstr ""

  4476. 

  4477. #: ../../../CHANGELOG.md:2461

  4478. msgid "**If you are using the [Hookshot bridge](docs/configuring-playbook-bridge-hookshot.md)**, you may find that:"

  4479. msgstr ""

  4480. 

  4481. #: ../../../CHANGELOG.md:2462

  4482. msgid "**Metrics may not be enabled by default anymore**:"

  4483. msgstr ""

  4484. 

  4485. #: ../../../CHANGELOG.md:2463

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

  4487. msgstr ""

  4488. 

  4489. #: ../../../CHANGELOG.md:2464

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

  4491. msgstr ""

  4492. 

  4493. #: ../../../CHANGELOG.md:2465

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

  4495. msgstr ""

  4496. 

  4497. #: ../../../CHANGELOG.md:2466

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

  4499. msgstr ""

  4500. 

  4501. #: ../../../CHANGELOG.md:2468

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

  4503. msgstr ""

  4504. 

  4505. #: ../../../CHANGELOG.md:2470

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

  4507. msgstr ""

  4508. 

  4509. #: ../../../CHANGELOG.md:2472

  4510. msgid "**If you're using Synapse** and would like to collect its metrics from an external Prometheus server, you may find that:"

  4511. msgstr ""

  4512. 

  4513. #: ../../../CHANGELOG.md:2474

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

  4515. msgstr ""

  4516. 

  4517. #: ../../../CHANGELOG.md:2475

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

  4519. msgstr ""

  4520. 

  4521. #: ../../../CHANGELOG.md:2476

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

  4523. msgstr ""

  4524. 

  4525. #: ../../../CHANGELOG.md:2477

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

  4527. msgstr ""

  4528. 

  4529. #: ../../../CHANGELOG.md:2479

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

  4531. msgstr ""

  4532. 

  4533. #: ../../../CHANGELOG.md:2481

  4534. msgid "2022-06-13"

  4535. msgstr ""

  4536. 

  4537. #: ../../../CHANGELOG.md:2483

  4538. msgid "go-skype-bridge bridging support"

  4539. msgstr ""

  4540. 

  4541. #: ../../../CHANGELOG.md:2485

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

  4543. msgstr ""

  4544. 

  4545. #: ../../../CHANGELOG.md:2487

  4546. msgid "See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md) documentation to get started."

  4547. msgstr ""

  4548. 

  4549. #: ../../../CHANGELOG.md:2489

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

  4551. msgstr ""

  4552. 

  4553. #: ../../../CHANGELOG.md:2492

  4554. msgid "2022-06-09"

  4555. msgstr ""

  4556. 

  4557. #: ../../../CHANGELOG.md:2494

  4558. msgid "Running Ansible in a container can now happen on the Matrix server itself"

  4559. msgstr ""

  4560. 

  4561. #: ../../../CHANGELOG.md:2496

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

  4563. msgstr ""

  4564. 

  4565. #: ../../../CHANGELOG.md:2499

  4566. msgid "2022-05-31"

  4567. msgstr ""

  4568. 

  4569. #: ../../../CHANGELOG.md:2501

  4570. msgid "Synapse v1.60 upgrade may cause trouble and require manual intervention"

  4571. msgstr ""

  4572. 

  4573. #: ../../../CHANGELOG.md:2503

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

  4575. msgstr ""

  4576. 

  4577. #: ../../../CHANGELOG.md:2505

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

  4579. msgstr ""

  4580. 

  4581. #: ../../../CHANGELOG.md:2507

  4582. msgid "**If Synapse fails to start** after your next playbook run, you'll need to:"

  4583. msgstr ""

  4584. 

  4585. #: ../../../CHANGELOG.md:2509

  4586. msgid "SSH into the Matrix server"

  4587. msgstr ""

  4588. 

  4589. #: ../../../CHANGELOG.md:2510

  4590. msgid "launch `/usr/local/bin/matrix-postgres-cli`"

  4591. msgstr ""

  4592. 

  4593. #: ../../../CHANGELOG.md:2511

  4594. msgid "switch to the `synapse` database: `\\c synapse`"

  4595. msgstr ""

  4596. 

  4597. #: ../../../CHANGELOG.md:2512

  4598. msgid "run the following SQL query:"

  4599. msgstr ""

  4600. 

  4601. #: ../../../CHANGELOG.md:2531

  4602. msgid "You could then restart services: `ansible-playbook -i inventory/hosts setup.yml --tags=start`"

  4603. msgstr ""

  4604. 

  4605. #: ../../../CHANGELOG.md:2534

  4606. msgid "2022-04-25"

  4607. msgstr ""

  4608. 

  4609. #: ../../../CHANGELOG.md:2536

  4610. msgid "Buscarron bot support"

  4611. msgstr ""

  4612. 

  4613. #: ../../../CHANGELOG.md:2538

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

  4615. msgstr ""

  4616. 

  4617. #: ../../../CHANGELOG.md:2540

  4618. msgid "See our [Setting up Buscarron](docs/configuring-playbook-bot-buscarron.md) documentation to get started."

  4619. msgstr ""

  4620. 

  4621. #: ../../../CHANGELOG.md:2543

  4622. msgid "2022-04-21"

  4623. msgstr ""

  4624. 

  4625. #: ../../../CHANGELOG.md:2545

  4626. msgid "matrix-registration-bot support"

  4627. msgstr ""

  4628. 

  4629. #: ../../../CHANGELOG.md:2547

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

  4631. msgstr ""

  4632. 

  4633. #: ../../../CHANGELOG.md:2549

  4634. msgid "See our [Setting up matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) documentation to get started."

  4635. msgstr ""

  4636. 

  4637. #: ../../../CHANGELOG.md:2552

  4638. msgid "2022-04-19"

  4639. msgstr ""

  4640. 

  4641. #: ../../../CHANGELOG.md:2554

  4642. msgid "BorgBackup support"

  4643. msgstr ""

  4644. 

  4645. #: ../../../CHANGELOG.md:2556

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

  4647. msgstr ""

  4648. 

  4649. #: ../../../CHANGELOG.md:2558

  4650. msgid "See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md) documentation to get started."

  4651. msgstr ""

  4652. 

  4653. #: ../../../CHANGELOG.md:2560

  4654. msgid "(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action"

  4655. msgstr ""

  4656. 

  4657. #: ../../../CHANGELOG.md:2562

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

  4659. msgstr ""

  4660. 

  4661. #: ../../../CHANGELOG.md:2564

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

  4663. msgstr ""

  4664. 

  4665. #: ../../../CHANGELOG.md:2566

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

  4667. msgstr ""

  4668. 

  4669. #: ../../../CHANGELOG.md:2568

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

  4671. msgstr ""

  4672. 

  4673. #: ../../../CHANGELOG.md:2570

  4674. msgid "Pull the latest playbook changes"

  4675. msgstr ""

  4676. 

  4677. #: ../../../CHANGELOG.md:2571

  4678. msgid "Stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"

  4679. msgstr ""

  4680. 

  4681. #: ../../../CHANGELOG.md:2572

  4682. msgid "Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all`)"

  4683. msgstr ""

  4684. 

  4685. #: ../../../CHANGELOG.md:2573

  4686. msgid "Start Postgres (`systemctl start matrix-postgres` on the server)"

  4687. msgstr ""

  4688. 

  4689. #: ../../../CHANGELOG.md:2574

  4690. msgid "Start the main Synapse process (`systemctl start matrix-synapse` on the server)"

  4691. msgstr ""

  4692. 

  4693. #: ../../../CHANGELOG.md:2575

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

  4695. msgstr ""

  4696. 

  4697. #: ../../../CHANGELOG.md:2576

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

  4699. msgstr ""

  4700. 

  4701. #: ../../../CHANGELOG.md:2579

  4702. msgid "2022-04-14"

  4703. msgstr ""

  4704. 

  4705. #: ../../../CHANGELOG.md:2581

  4706. msgid "(Compatibility Break) Changes to `docker-src` permissions necessitating manual action"

  4707. msgstr ""

  4708. 

  4709. #: ../../../CHANGELOG.md:2583

  4710. msgid "Users who build container images from source will need to manually correct file permissions of some directories on the server."

  4711. msgstr ""

  4712. 

  4713. #: ../../../CHANGELOG.md:2585

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

  4715. msgstr ""

  4716. 

  4717. #: ../../../CHANGELOG.md:2587

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

  4719. msgstr ""

  4720. 

  4721. #: ../../../CHANGELOG.md:2589

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

  4723. msgstr ""

  4724. 

  4725. #: ../../../CHANGELOG.md:2592

  4726. msgid "2022-03-17"

  4727. msgstr ""

  4728. 

  4729. #: ../../../CHANGELOG.md:2594

  4730. msgid "(Compatibility Break) ma1sd identity server no longer installed by default"

  4731. msgstr ""

  4732. 

  4733. #: ../../../CHANGELOG.md:2596

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

  4735. msgstr ""

  4736. 

  4737. #: ../../../CHANGELOG.md:2598

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

  4739. msgstr ""

  4740. 

  4741. #: ../../../CHANGELOG.md:2600

  4742. msgid "Since Element clients no longer default to using a public identity server if another one is not provided, we can stop installing ma1sd."

  4743. msgstr ""

  4744. 

  4745. #: ../../../CHANGELOG.md:2602

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

  4747. msgstr ""

  4748. 

  4749. #: ../../../CHANGELOG.md:2609

  4750. msgid "2022-02-12"

  4751. msgstr ""

  4752. 

  4753. #: ../../../CHANGELOG.md:2611

  4754. msgid "matrix_encryption_disabler support"

  4755. msgstr ""

  4756. 

  4757. #: ../../../CHANGELOG.md:2613

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

  4759. msgstr ""

  4760. 

  4761. #: ../../../CHANGELOG.md:2615

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

  4763. msgstr ""

  4764. 

  4765. #: ../../../CHANGELOG.md:2618

  4766. msgid "2022-02-01"

  4767. msgstr ""

  4768. 

  4769. #: ../../../CHANGELOG.md:2620

  4770. msgid "matrix-hookshot bridging support"

  4771. msgstr ""

  4772. 

  4773. #: ../../../CHANGELOG.md:2622

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

  4775. msgstr ""

  4776. 

  4777. #: ../../../CHANGELOG.md:2625

  4778. msgid "2022-01-31"

  4779. msgstr ""

  4780. 

  4781. #: ../../../CHANGELOG.md:2627

  4782. msgid "ARM support for matrix-corporal"

  4783. msgstr ""

  4784. 

  4785. #: ../../../CHANGELOG.md:2629

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

  4787. msgstr ""

  4788. 

  4789. #: ../../../CHANGELOG.md:2632

  4790. msgid "2022-01-07"

  4791. msgstr ""

  4792. 

  4793. #: ../../../CHANGELOG.md:2634

  4794. msgid "Dendrite support"

  4795. msgstr ""

  4796. 

  4797. #: ../../../CHANGELOG.md:2636

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

  4799. msgstr ""

  4800. 

  4801. #: ../../../CHANGELOG.md:2638

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

  4803. msgstr ""

  4804. 

  4805. #: ../../../CHANGELOG.md:2640

  4806. msgid "We believe that 2022 will be the year of the non-Synapse Matrix server!"

  4807. msgstr ""

  4808. 

  4809. #: ../../../CHANGELOG.md:2642

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

  4811. msgstr ""

  4812. 

  4813. #: ../../../CHANGELOG.md:2644

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

  4815. msgstr ""

  4816. 

  4817. #: ../../../CHANGELOG.md:2646

  4818. msgid "Adapting the configuration for existing Synapse installations"

  4819. msgstr ""

  4820. 

  4821. #: ../../../CHANGELOG.md:2648

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

  4823. msgstr ""

  4824. 

  4825. #: ../../../CHANGELOG.md:2650

  4826. msgid "The `vars.yml` file for **existing installations will need to be updated** by adding this **additional configuration**:"

  4827. msgstr ""

  4828. 

  4829. #: ../../../CHANGELOG.md:2662

  4830. msgid "Trying out Dendrite"

  4831. msgstr ""

  4832. 

  4833. #: ../../../CHANGELOG.md:2664

  4834. msgid "Finally, **to try out Dendrite**, we recommend that you **use a new server** and the following addition to your `vars.yml` configuration:"

  4835. msgstr ""

  4836. 

  4837. #: ../../../CHANGELOG.md:2670

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

  4839. msgstr ""

  4840. 

  4841. #: ../../../CHANGELOG.md:2672

  4842. msgid "We're excited to gain support for other homeserver implementations, like [Conduit](https://conduit.rs/), etc!"

  4843. msgstr ""

  4844. 

  4845. #: ../../../CHANGELOG.md:2674

  4846. msgid "Honoroit bot support"

  4847. msgstr ""

  4848. 

  4849. #: ../../../CHANGELOG.md:2676

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

  4851. msgstr ""

  4852. 

  4853. #: ../../../CHANGELOG.md:2678

  4854. msgid "See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documentation to get started."

  4855. msgstr ""

  4856. 

  4857. #: ../../../CHANGELOG.md:2681

  4858. msgid "2022-01-06"

  4859. msgstr ""

  4860. 

  4861. #: ../../../CHANGELOG.md:2683

  4862. msgid "Cinny support"

  4863. msgstr ""

  4864. 

  4865. #: ../../../CHANGELOG.md:2685

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

  4867. msgstr ""

  4868. 

  4869. #: ../../../CHANGELOG.md:2687

  4870. msgid "By default, we still install Element Web. Still, people who'd like to try Cinny out can now install it via the playbook."

  4871. msgstr ""

  4872. 

  4873. #: ../../../CHANGELOG.md:2689

  4874. msgid "Additional details are available in [Setting up Cinny](docs/configuring-playbook-client-cinny.md)."

  4875. msgstr ""

  4876. 

  4877. #: ../../../CHANGELOG.md:2692

  4878. msgid "2021-12-22"

  4879. msgstr ""

  4880. 

  4881. #: ../../../CHANGELOG.md:2694

  4882. msgid "Twitter bridging support via mautrix-twitter"

  4883. msgstr ""

  4884. 

  4885. #: ../../../CHANGELOG.md:2696

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

  4887. msgstr ""

  4888. 

  4889. #: ../../../CHANGELOG.md:2699

  4890. msgid "2021-12-14"

  4891. msgstr ""

  4892. 

  4893. #: ../../../CHANGELOG.md:2701

  4894. msgid "(Security) Users of the Signal bridge may wish to upgrade it to work around log4j vulnerability"

  4895. msgstr ""

  4896. 

  4897. #: ../../../CHANGELOG.md:2703

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

  4899. msgstr ""

  4900. 

  4901. #: ../../../CHANGELOG.md:2705

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

  4903. msgstr ""

  4904. 

  4905. #: ../../../CHANGELOG.md:2708

  4906. msgid "2021-11-11"

  4907. msgstr ""

  4908. 

  4909. #: ../../../CHANGELOG.md:2710

  4910. msgid "Dropped support for Postgres v9.6"

  4911. msgstr ""

  4912. 

  4913. #: ../../../CHANGELOG.md:2712

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

  4915. msgstr ""

  4916. 

  4917. #: ../../../CHANGELOG.md:2714

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

  4919. msgstr ""

  4920. 

  4921. #: ../../../CHANGELOG.md:2717

  4922. msgid "2021-10-23"

  4923. msgstr ""

  4924. 

  4925. #: ../../../CHANGELOG.md:2719

  4926. msgid "Hangouts bridge no longer updated, superseded by a Googlechat bridge"

  4927. msgstr ""

  4928. 

  4929. #: ../../../CHANGELOG.md:2721

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

  4931. msgstr ""

  4932. 

  4933. #: ../../../CHANGELOG.md:2723

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

  4935. msgstr ""

  4936. 

  4937. #: ../../../CHANGELOG.md:2726

  4938. msgid "2021-08-23"

  4939. msgstr ""

  4940. 

  4941. #: ../../../CHANGELOG.md:2728

  4942. msgid "LinkedIn bridging support via beeper-linkedin"

  4943. msgstr ""

  4944. 

  4945. #: ../../../CHANGELOG.md:2730

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

  4947. msgstr ""

  4948. 

  4949. #: ../../../CHANGELOG.md:2732

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

  4951. msgstr ""

  4952. 

  4953. #: ../../../CHANGELOG.md:2734

  4954. msgid "To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)."

  4955. msgstr ""

  4956. 

  4957. #: ../../../CHANGELOG.md:2737

  4958. msgid "2021-08-20"

  4959. msgstr ""

  4960. 

  4961. #: ../../../CHANGELOG.md:2739

  4962. msgid "Sygnal upgraded — ARM support and no longer requires a database"

  4963. msgstr ""

  4964. 

  4965. #: ../../../CHANGELOG.md:2741

  4966. msgid "The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been upgraded from `v0.9.0` to `v0.10.1`."

  4967. msgstr ""

  4968. 

  4969. #: ../../../CHANGELOG.md:2743

  4970. msgid "This is an optional component for the playbook, so most of our users wouldn't care about this announcement."

  4971. msgstr ""

  4972. 

  4973. #: ../../../CHANGELOG.md:2745

  4974. msgid "Since this feels like a relatively big (and untested, as of yet) Sygnal change, we're putting up this changelog entry."

  4975. msgstr ""

  4976. 

  4977. #: ../../../CHANGELOG.md:2747

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

  4979. msgstr ""

  4980. 

  4981. #: ../../../CHANGELOG.md:2750

  4982. msgid "2021-05-21"

  4983. msgstr ""

  4984. 

  4985. #: ../../../CHANGELOG.md:2752

  4986. msgid "Hydrogen support"

  4987. msgstr ""

  4988. 

  4989. #: ../../../CHANGELOG.md:2754

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

  4991. msgstr ""

  4992. 

  4993. #: ../../../CHANGELOG.md:2756

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

  4995. msgstr ""

  4996. 

  4997. #: ../../../CHANGELOG.md:2758

  4998. msgid "Additional details are available in [Setting up Hydrogen](docs/configuring-playbook-client-hydrogen.md)."

  4999. msgstr ""

  5000. 

  5001. #: ../../../CHANGELOG.md:2761

  5002. msgid "2021-05-19"

  5003. msgstr ""

  5004. 

  5005. #: ../../../CHANGELOG.md:2763

  5006. msgid "Heisenbridge support"

  5007. msgstr ""

  5008. 

  5009. #: ../../../CHANGELOG.md:2765

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

  5011. msgstr ""

  5012. 

  5013. #: ../../../CHANGELOG.md:2767

  5014. msgid "Additional details are available in [Setting up Heisenbridge bouncer-style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)."

  5015. msgstr ""

  5016. 

  5017. #: ../../../CHANGELOG.md:2770

  5018. msgid "2021-04-16"

  5019. msgstr ""

  5020. 

  5021. #: ../../../CHANGELOG.md:2772

  5022. msgid "Disabling TLSv1 and TLSv1.1 for coturn"

  5023. msgstr ""

  5024. 

  5025. #: ../../../CHANGELOG.md:2774

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

  5027. msgstr ""

  5028. 

  5029. #: ../../../CHANGELOG.md:2776

  5030. msgid "If you need to support old clients, you can re-enable both (or whichever one you need) with the following configuration:"

  5031. msgstr ""

  5032. 

  5033. #: ../../../CHANGELOG.md:2784

  5034. msgid "2021-04-05"

  5035. msgstr ""

  5036. 

  5037. #: ../../../CHANGELOG.md:2786

  5038. msgid "Automated local Postgres backup support"

  5039. msgstr ""

  5040. 

  5041. #: ../../../CHANGELOG.md:2788

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

  5043. msgstr ""

  5044. 

  5045. #: ../../../CHANGELOG.md:2790

  5046. msgid "Additional details are available in [Setting up Postgres backup](docs/configuring-playbook-postgres-backup.md)."

  5047. msgstr ""

  5048. 

  5049. #: ../../../CHANGELOG.md:2793

  5050. msgid "2021-04-03"

  5051. msgstr ""

  5052. 

  5053. #: ../../../CHANGELOG.md:2795

  5054. msgid "Mjolnir moderation tool (bot) support"

  5055. msgstr ""

  5056. 

  5057. #: ../../../CHANGELOG.md:2797

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

  5059. msgstr ""

  5060. 

  5061. #: ../../../CHANGELOG.md:2799

  5062. msgid "Additional details are available in [Setting up Mjolnir](docs/configuring-playbook-bot-mjolnir.md)."

  5063. msgstr ""

  5064. 

  5065. #: ../../../CHANGELOG.md:2802

  5066. msgid "2021-03-20"

  5067. msgstr ""

  5068. 

  5069. #: ../../../CHANGELOG.md:2804

  5070. msgid "Sygnal push gateway support"

  5071. msgstr ""

  5072. 

  5073. #: ../../../CHANGELOG.md:2806

  5074. msgid "The playbook can now install the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you."

  5075. msgstr ""

  5076. 

  5077. #: ../../../CHANGELOG.md:2808

  5078. msgid "This is only useful to people who develop/build their own Matrix client applications."

  5079. msgstr ""

  5080. 

  5081. #: ../../../CHANGELOG.md:2810

  5082. msgid "Additional details are available in our [Setting up the Sygnal push gateway](docs/configuring-playbook-sygnal.md) docs."

  5083. msgstr ""

  5084. 

  5085. #: ../../../CHANGELOG.md:2813

  5086. msgid "2021-03-16"

  5087. msgstr ""

  5088. 

  5089. #: ../../../CHANGELOG.md:2815

  5090. msgid "Go-NEB support"

  5091. msgstr ""

  5092. 

  5093. #: ../../../CHANGELOG.md:2817

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

  5095. msgstr ""

  5096. 

  5097. #: ../../../CHANGELOG.md:2819

  5098. msgid "Additional details are available in [Setting up Go-NEB](docs/configuring-playbook-bot-go-neb.md)."

  5099. msgstr ""

  5100. 

  5101. #: ../../../CHANGELOG.md:2822

  5102. msgid "2021-02-19"

  5103. msgstr ""

  5104. 

  5105. #: ../../../CHANGELOG.md:2824

  5106. msgid "GroupMe bridging support via mx-puppet-groupme"

  5107. msgstr ""

  5108. 

  5109. #: ../../../CHANGELOG.md:2826

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

  5111. msgstr ""

  5112. 

  5113. #: ../../../CHANGELOG.md:2828

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

  5115. msgstr ""

  5116. 

  5117. #: ../../../CHANGELOG.md:2830

  5118. msgid "To get started, follow our [Setting up MX Puppet GroupMe](docs/configuring-playbook-bridge-mx-puppet-groupme.md) docs."

  5119. msgstr ""

  5120. 

  5121. #: ../../../CHANGELOG.md:2832

  5122. msgid "Mautrix Instagram bridging support"

  5123. msgstr ""

  5124. 

  5125. #: ../../../CHANGELOG.md:2834

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

  5127. msgstr ""

  5128. 

  5129. #: ../../../CHANGELOG.md:2836

  5130. msgid "Additional details are available in [Setting up Mautrix Instagram bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)."

  5131. msgstr ""

  5132. 

  5133. #: ../../../CHANGELOG.md:2838

  5134. msgid "Synapse workers support"

  5135. msgstr ""

  5136. 

  5137. #: ../../../CHANGELOG.md:2840

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

  5139. msgstr ""

  5140. 

  5141. #: ../../../CHANGELOG.md:2842

  5142. msgid "Having support for workers makes the playbook suitable for larger homeserver deployments."

  5143. msgstr ""

  5144. 

  5145. #: ../../../CHANGELOG.md:2844

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

  5147. msgstr ""

  5148. 

  5149. #: ../../../CHANGELOG.md:2846

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

  5151. msgstr ""

  5152. 

  5153. #: ../../../CHANGELOG.md:2848

  5154. msgid "To enable Synapse workers, follow our [Load balancing with workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) documentation."

  5155. msgstr ""

  5156. 

  5157. #: ../../../CHANGELOG.md:2851

  5158. msgid "2021-02-12"

  5159. msgstr ""

  5160. 

  5161. #: ../../../CHANGELOG.md:2853

  5162. msgid "(Potential Breaking Change) Monitoring/metrics support using Prometheus and Grafana"

  5163. msgstr ""

  5164. 

  5165. #: ../../../CHANGELOG.md:2855

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

  5167. msgstr ""

  5168. 

  5169. #: ../../../CHANGELOG.md:2857

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

  5171. msgstr ""

  5172. 

  5173. #: ../../../CHANGELOG.md:2859

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

  5175. msgstr ""

  5176. 

  5177. #: ../../../CHANGELOG.md:2862

  5178. msgid "2021-01-31"

  5179. msgstr ""

  5180. 

  5181. #: ../../../CHANGELOG.md:2864

  5182. msgid "Etherpad support"

  5183. msgstr ""

  5184. 

  5185. #: ../../../CHANGELOG.md:2866

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

  5187. msgstr ""

  5188. 

  5189. #: ../../../CHANGELOG.md:2868

  5190. msgid "To get it installed, follow [our Etherpad docs page](docs/configuring-playbook-etherpad.md)."

  5191. msgstr ""

  5192. 

  5193. #: ../../../CHANGELOG.md:2871

  5194. msgid "2021-01-22"

  5195. msgstr ""

  5196. 

  5197. #: ../../../CHANGELOG.md:2873

  5198. msgid "(Breaking Change) Postgres changes that require manual intervention"

  5199. msgstr ""

  5200. 

  5201. #: ../../../CHANGELOG.md:2875

  5202. msgid "We've made a lot of changes to our Postgres setup and some manual action is required (described below). Sorry about the hassle."

  5203. msgstr ""

  5204. 

  5205. #: ../../../CHANGELOG.md:2877

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

  5207. msgstr ""

  5208. 

  5209. #: ../../../CHANGELOG.md:2879

  5210. msgid "Why?"

  5211. msgstr ""

  5212. 

  5213. #: ../../../CHANGELOG.md:2881

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

  5215. msgstr ""

  5216. 

  5217. #: ../../../CHANGELOG.md:2882

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

  5219. msgstr ""

  5220. 

  5221. #: ../../../CHANGELOG.md:2883

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

  5223. msgstr ""

  5224. 

  5225. #: ../../../CHANGELOG.md:2884

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

  5227. msgstr ""

  5228. 

  5229. #: ../../../CHANGELOG.md:2885

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

  5231. msgstr ""

  5232. 

  5233. #: ../../../CHANGELOG.md:2886

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

  5235. msgstr ""

  5236. 

  5237. #: ../../../CHANGELOG.md:2888

  5238. msgid "So, this is some **effort to improve security** and to **prepare for a brighter future of having more homeserver options** than just Synapse."

  5239. msgstr ""

  5240. 

  5241. #: ../../../CHANGELOG.md:2890

  5242. msgid "What has really changed?"

  5243. msgstr ""

  5244. 

  5245. #: ../../../CHANGELOG.md:2892

  5246. msgid "the default superuser Postgres username is now `matrix` (used to be `synapse`)"

  5247. msgstr ""

  5248. 

  5249. #: ../../../CHANGELOG.md:2893

  5250. msgid "the default Postgres database is now `matrix` (used to be `homeserver`)"

  5251. msgstr ""

  5252. 

  5253. #: ../../../CHANGELOG.md:2894

  5254. msgid "Synapse's database is now `synapse` (used to be `homeserver`). This is now just another \"additional database\" that the playbook manages for you"

  5255. msgstr ""

  5256. 

  5257. #: ../../../CHANGELOG.md:2895

  5258. msgid "Synapse's user called `synapse` is just a regular user that can only use the `synapse` database (not a superuser anymore)"

  5259. msgstr ""

  5260. 

  5261. #: ../../../CHANGELOG.md:2897

  5262. msgid "What do I do if I'm using the integrated Postgres server (default)?"

  5263. msgstr ""

  5264. 

  5265. #: ../../../CHANGELOG.md:2899

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

  5267. msgstr ""

  5268. 

  5269. #: ../../../CHANGELOG.md:2901

  5270. msgid "To migrate to the new setup, expect a few minutes of downtime, while you follow these steps:"

  5271. msgstr ""

  5272. 

  5273. #: ../../../CHANGELOG.md:2903

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

  5275. msgstr ""

  5276. 

  5277. #: ../../../CHANGELOG.md:2905

  5278. 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!"

  5279. msgstr ""

  5280. 

  5281. #: ../../../CHANGELOG.md:2907

  5282. msgid "Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` file, adding a line like this:"

  5283. msgstr ""

  5284. 

  5285. #: ../../../CHANGELOG.md:2912

  5286. #: ../../../CHANGELOG.md:2924

  5287. msgid "… where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2."

  5288. msgstr ""

  5289. 

  5290. #: ../../../CHANGELOG.md:2914

  5291. msgid "Stop all services: `ansible-playbook -i inventory/hosts setup.yml --tags=stop`"

  5292. msgstr ""

  5293. 

  5294. #: ../../../CHANGELOG.md:2915

  5295. msgid "Log in to the server via SSH. The next commands will be performed there."

  5296. msgstr ""

  5297. 

  5298. #: ../../../CHANGELOG.md:2916

  5299. msgid "Start the Postgres database server: `systemctl start matrix-postgres`"

  5300. msgstr ""

  5301. 

  5302. #: ../../../CHANGELOG.md:2917

  5303. msgid "Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`"

  5304. msgstr ""

  5305. 

  5306. #: ../../../CHANGELOG.md:2918

  5307. msgid "Execute the following query, while making sure to **change the password inside** (**don't forget the ending `;`**):"

  5308. msgstr ""

  5309. 

  5310. #: ../../../CHANGELOG.md:2926

  5311. msgid "Execute the following queries as you see them (no modifications necessary, so you can just **paste them all at once**):"

  5312. msgstr ""

  5313. 

  5314. #: ../../../CHANGELOG.md:2944

  5315. msgid "You may need to press *Enter* after pasting the lines above."

  5316. msgstr ""

  5317. 

  5318. #: ../../../CHANGELOG.md:2946

  5319. msgid "Re-run the playbook normally: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`"

  5320. msgstr ""

  5321. 

  5322. #: ../../../CHANGELOG.md:2948

  5323. msgid "What do I do if I'm using an external Postgres server?"

  5324. msgstr ""

  5325. 

  5326. #: ../../../CHANGELOG.md:2950

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

  5328. msgstr ""

  5329. 

  5330. #: ../../../CHANGELOG.md:2952

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

  5332. msgstr ""

  5333. 

  5334. #: ../../../CHANGELOG.md:2955

  5335. msgid "2021-01-20"

  5336. msgstr ""

  5337. 

  5338. #: ../../../CHANGELOG.md:2957

  5339. msgid "(Breaking Change) The mautrix-facebook bridge now requires a Postgres database"

  5340. msgstr ""

  5341. 

  5342. #: ../../../CHANGELOG.md:2959

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

  5344. msgstr ""

  5345. 

  5346. #: ../../../CHANGELOG.md:2961

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

  5348. msgstr ""

  5349. 

  5350. #: ../../../CHANGELOG.md:2963

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

  5352. msgstr ""

  5353. 

  5354. #: ../../../CHANGELOG.md:2965

  5355. msgid "Whether this change requires your intervention depends mostly on:"

  5356. msgstr ""

  5357. 

  5358. #: ../../../CHANGELOG.md:2966

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

  5360. msgstr ""

  5361. 

  5362. #: ../../../CHANGELOG.md:2967

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

  5364. msgstr ""

  5365. 

  5366. #: ../../../CHANGELOG.md:2969

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

  5368. msgstr ""

  5369. 

  5370. #: ../../../CHANGELOG.md:2971

  5371. msgid "Upgrade path for people NOT running an external Postgres server (default for the playbook)"

  5372. msgstr ""

  5373. 

  5374. #: ../../../CHANGELOG.md:2973

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

  5376. msgstr ""

  5377. 

  5378. #: ../../../CHANGELOG.md:2975

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

  5380. msgstr ""

  5381. 

  5382. #: ../../../CHANGELOG.md:2977

  5383. msgid "Alternatively, [you can stay on SQLite for a little longer](#staying-on-sqlite-for-a-little-longer-temporary-solution)."

  5384. msgstr ""

  5385. 

  5386. #: ../../../CHANGELOG.md:2979

  5387. msgid "Upgrade path for people running an external Postgres server"

  5388. msgstr ""

  5389. 

  5390. #: ../../../CHANGELOG.md:2981

  5391. msgid "For people using the internal Postgres server (the default for the playbook):"

  5392. msgstr ""

  5393. 

  5394. #: ../../../CHANGELOG.md:2982

  5395. msgid "we automatically create an additional `matrix_mautrix_facebook` Postgres database and credentials to access it"

  5396. msgstr ""

  5397. 

  5398. #: ../../../CHANGELOG.md:2983

  5399. msgid "we automatically adjust the bridge's `matrix_mautrix_facebook_database_*` variables to point the bridge to that Postgres database"

  5400. msgstr ""

  5401. 

  5402. #: ../../../CHANGELOG.md:2984

  5403. msgid "we use [pgloader](https://pgloader.io/) to automatically import the existing SQLite data for the bridge into the `matrix_mautrix_facebook` Postgres database"

  5404. msgstr ""

  5405. 

  5406. #: ../../../CHANGELOG.md:2986

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

  5408. msgstr ""

  5409. 

  5410. #: ../../../CHANGELOG.md:2988

  5411. msgid "You have 3 ways to proceed:"

  5412. msgstr ""

  5413. 

  5414. #: ../../../CHANGELOG.md:2990

  5415. msgid "contribute to the playbook to make this possible (difficult)"

  5416. msgstr ""

  5417. 

  5418. #: ../../../CHANGELOG.md:2991

  5419. msgid "or, do the migration \"steps\" manually:"

  5420. msgstr ""

  5421. 

  5422. #: ../../../CHANGELOG.md:2992

  5423. msgid "stop the bridge (`systemctl stop matrix-mautrix-facebook`)"

  5424. msgstr ""

  5425. 

  5426. #: ../../../CHANGELOG.md:2993

  5427. msgid "create a new `matrix_mautrix_facebook` Postgres database for it"

  5428. msgstr ""

  5429. 

  5430. #: ../../../CHANGELOG.md:2994

  5431. msgid "run [pgloader](https://pgloader.io/) manually (we import this bridge's data using default settings and it works well)"

  5432. msgstr ""

  5433. 

  5434. #: ../../../CHANGELOG.md:2995

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

  5436. msgstr ""

  5437. 

  5438. #: ../../../CHANGELOG.md:2996

  5439. msgid "switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: 'postgres'` in your `vars.yml` file)"

  5440. msgstr ""

  5441. 

  5442. #: ../../../CHANGELOG.md:2997

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

  5444. msgstr ""

  5445. 

  5446. #: ../../../CHANGELOG.md:2998

  5447. msgid "send a `login` message to the Facebook bridge bot again"

  5448. msgstr ""

  5449. 

  5450. #: ../../../CHANGELOG.md:2999

  5451. msgid "or, [stay on SQLite for a little longer (temporary solution)](#staying-on-sqlite-for-a-little-longer-temporary-solution)"

  5452. msgstr ""

  5453. 

  5454. #: ../../../CHANGELOG.md:3001

  5455. msgid "Staying on SQLite for a little longer (temporary solution)"

  5456. msgstr ""

  5457. 

  5458. #: ../../../CHANGELOG.md:3003

  5459. msgid "To keep using this bridge with SQLite for a little longer (**not recommended**), use the following configuration in your `vars.yml` file:"

  5460. msgstr ""

  5461. 

  5462. #: ../../../CHANGELOG.md:3013

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

  5464. msgstr ""

  5465. 

  5466. #: ../../../CHANGELOG.md:3016

  5467. msgid "2021-01-17"

  5468. msgstr ""

  5469. 

  5470. #: ../../../CHANGELOG.md:3018

  5471. msgid "matrix-corporal goes 2.0"

  5472. msgstr ""

  5473. 

  5474. #: ../../../CHANGELOG.md:3020

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

  5476. msgstr ""

  5477. 

  5478. #: ../../../CHANGELOG.md:3022

  5479. msgid "No manual intervention is required in the common case."

  5480. msgstr ""

  5481. 

  5482. #: ../../../CHANGELOG.md:3024

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

  5484. msgstr ""

  5485. 

  5486. #: ../../../CHANGELOG.md:3027

  5487. msgid "2021-01-14"

  5488. msgstr ""

  5489. 

  5490. #: ../../../CHANGELOG.md:3029

  5491. msgid "Moving from cronjobs to systemd timers"

  5492. msgstr ""

  5493. 

  5494. #: ../../../CHANGELOG.md:3031

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

  5496. msgstr ""

  5497. 

  5498. #: ../../../CHANGELOG.md:3033

  5499. msgid "The largest benefit of this is that we no longer require you to install a cron daemon, thus simplifying our install procedure."

  5500. msgstr ""

  5501. 

  5502. #: ../../../CHANGELOG.md:3035

  5503. msgid "The playbook will migrate you from cronjobs to systemd timers automatically. This is just a heads up."

  5504. msgstr ""

  5505. 

  5506. #: ../../../CHANGELOG.md:3038

  5507. msgid "2021-01-08"

  5508. msgstr ""

  5509. 

  5510. #: ../../../CHANGELOG.md:3040

  5511. msgid "(Breaking Change) New SSL configuration"

  5512. msgstr ""

  5513. 

  5514. #: ../../../CHANGELOG.md:3042

  5515. msgid "SSL configuration (protocols, ciphers) can now be more easily controlled thanks to us making use of configuration presets."

  5516. msgstr ""

  5517. 

  5518. #: ../../../CHANGELOG.md:3044

  5519. msgid "We define a few presets (old, intermediate, modern), following the [Mozilla SSL Configuration Generator](https://ssl-config.mozilla.org/#server=nginx)."

  5520. msgstr ""

  5521. 

  5522. #: ../../../CHANGELOG.md:3046

  5523. msgid "A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is used (defaults to `\"intermediate\"`)."

  5524. msgstr ""

  5525. 

  5526. #: ../../../CHANGELOG.md:3048

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

  5528. msgstr ""

  5529. 

  5530. #: ../../../CHANGELOG.md:3050

  5531. msgid "To revert to the old behaviour, set the following variables:"

  5532. msgstr ""

  5533. 

  5534. #: ../../../CHANGELOG.md:3057

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

  5536. msgstr ""

  5537. 

  5538. #: ../../../CHANGELOG.md:3060

  5539. msgid "2021-01-03"

  5540. msgstr ""

  5541. 

  5542. #: ../../../CHANGELOG.md:3062

  5543. msgid "Signal bridging support via mautrix-signal"

  5544. msgstr ""

  5545. 

  5546. #: ../../../CHANGELOG.md:3064

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

  5548. msgstr ""

  5549. 

  5550. #: ../../../CHANGELOG.md:3066

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

  5552. msgstr ""

  5553. 

  5554. #: ../../../CHANGELOG.md:3069

  5555. msgid "2020-12-23"

  5556. msgstr ""

  5557. 

  5558. #: ../../../CHANGELOG.md:3071

  5559. msgid "The big move to all-on-Postgres (potentially dangerous)"

  5560. msgstr ""

  5561. 

  5562. #: ../../../CHANGELOG.md:3073

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

  5564. msgstr ""

  5565. 

  5566. #: ../../../CHANGELOG.md:3075

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

  5568. msgstr ""

  5569. 

  5570. #: ../../../CHANGELOG.md:3077

  5571. 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!"

  5572. msgstr ""

  5573. 

  5574. #: ../../../CHANGELOG.md:3079

  5575. msgid "Moving all services to Postgres brings a few **benefits** to us:"

  5576. msgstr ""

  5577. 

  5578. #: ../../../CHANGELOG.md:3081

  5579. msgid "**improved performance**"

  5580. msgstr ""

  5581. 

  5582. #: ../../../CHANGELOG.md:3082

  5583. msgid "**improved compatibility**. Most bridges are deprecating SQLite/nedb support or offer less features when not on Postgres."

  5584. msgstr ""

  5585. 

  5586. #: ../../../CHANGELOG.md:3083

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

  5588. msgstr ""

  5589. 

  5590. #: ../../../CHANGELOG.md:3084

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

  5592. msgstr ""

  5593. 

  5594. #: ../../../CHANGELOG.md:3086

  5595. msgid "Key takeway"

  5596. msgstr ""

  5597. 

  5598. #: ../../../CHANGELOG.md:3088

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

  5600. msgstr ""

  5601. 

  5602. #: ../../../CHANGELOG.md:3090

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

  5604. msgstr ""

  5605. 

  5606. #: ../../../CHANGELOG.md:3092

  5607. msgid "Opting-out of the Postgres migration"

  5608. msgstr ""

  5609. 

  5610. #: ../../../CHANGELOG.md:3094

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

  5612. msgstr ""

  5613. 

  5614. #: ../../../CHANGELOG.md:3096

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

  5616. msgstr ""

  5617. 

  5618. #: ../../../CHANGELOG.md:3098

  5619. msgid "Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them."

  5620. msgstr ""

  5621. 

  5622. #: ../../../CHANGELOG.md:3100

  5623. msgid "Going back to SQLite/nedb if things went wrong"

  5624. msgstr ""

  5625. 

  5626. #: ../../../CHANGELOG.md:3102

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

  5628. msgstr ""

  5629. 

  5630. #: ../../../CHANGELOG.md:3104

  5631. msgid "stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"

  5632. msgstr ""

  5633. 

  5634. #: ../../../CHANGELOG.md:3105

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

  5636. msgstr ""

  5637. 

  5638. #: ../../../CHANGELOG.md:3106

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

  5640. msgstr ""

  5641. 

  5642. #: ../../../CHANGELOG.md:3107

  5643. msgid "re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`)"

  5644. msgstr ""

  5645. 

  5646. #: ../../../CHANGELOG.md:3108

  5647. msgid "[get in touch](README.md#support) with us"

  5648. msgstr ""

  5649. 

  5650. #: ../../../CHANGELOG.md:3110

  5651. msgid "2020-12-11"

  5652. msgstr ""

  5653. 

  5654. #: ../../../CHANGELOG.md:3112

  5655. msgid "synapse-janitor support removed"

  5656. msgstr ""

  5657. 

  5658. #: ../../../CHANGELOG.md:3114

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

  5660. msgstr ""

  5661. 

  5662. #: ../../../CHANGELOG.md:3116

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

  5664. msgstr ""

  5665. 

  5666. #: ../../../CHANGELOG.md:3118

  5667. msgid "Docker 20.10 is here"

  5668. msgstr ""

  5669. 

  5670. #: ../../../CHANGELOG.md:3120

  5671. msgid "(No need to do anything special in relation to this. Just something to keep in mind)"

  5672. msgstr ""

  5673. 

  5674. #: ../../../CHANGELOG.md:3122

  5675. msgid "Docker 20.10 got released recently and your server will likely get it the next time you update."

  5676. msgstr ""

  5677. 

  5678. #: ../../../CHANGELOG.md:3124

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

  5680. msgstr ""

  5681. 

  5682. #: ../../../CHANGELOG.md:3127

  5683. msgid "2020-12-08"

  5684. msgstr ""

  5685. 

  5686. #: ../../../CHANGELOG.md:3129

  5687. msgid "openid APIs exposed by default on the federation port when federation disabled"

  5688. msgstr ""

  5689. 

  5690. #: ../../../CHANGELOG.md:3131

  5691. msgid "We've changed some defaults. People running with our default configuration (federation enabled), are not affected at all."

  5692. msgstr ""

  5693. 

  5694. #: ../../../CHANGELOG.md:3133

  5695. msgid "If you are running an unfederated server (`matrix_synapse_federation_enabled: false`), this may be of interest to you."

  5696. msgstr ""

  5697. 

  5698. #: ../../../CHANGELOG.md:3135

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

  5700. msgstr ""

  5701. 

  5702. #: ../../../CHANGELOG.md:3138

  5703. msgid "2020-11-27"

  5704. msgstr ""

  5705. 

  5706. #: ../../../CHANGELOG.md:3140

  5707. msgid "Recent Jitsi updates may require configuration changes"

  5708. msgstr ""

  5709. 

  5710. #: ../../../CHANGELOG.md:3142

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

  5712. msgstr ""

  5713. 

  5714. #: ../../../CHANGELOG.md:3144

  5715. msgid "**If you use our default Jitsi settings, you won't have to do anything.**"

  5716. msgstr ""

  5717. 

  5718. #: ../../../CHANGELOG.md:3146

  5719. 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."

  5720. msgstr ""

  5721. 

  5722. #: ../../../CHANGELOG.md:3148

  5723. 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."

  5724. msgstr ""

  5725. 

  5726. #: ../../../CHANGELOG.md:3150

  5727. 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."

  5728. msgstr ""

  5729. 

  5730. #: ../../../CHANGELOG.md:3153

  5731. msgid "2020-11-23"

  5732. msgstr ""

  5733. 

  5734. #: ../../../CHANGELOG.md:3155

  5735. #: ../../../CHANGELOG.md:3163

  5736. msgid "Breaking change matrix-sms-bridge"

  5737. msgstr ""

  5738. 

  5739. #: ../../../CHANGELOG.md:3157

  5740. 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."

  5741. msgstr ""

  5742. 

  5743. #: ../../../CHANGELOG.md:3159

  5744. 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."

  5745. msgstr ""

  5746. 

  5747. #: ../../../CHANGELOG.md:3161

  5748. msgid "2020-11-13"

  5749. msgstr ""

  5750. 

  5751. #: ../../../CHANGELOG.md:3165

  5752. 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."

  5753. msgstr ""

  5754. 

  5755. #: ../../../CHANGELOG.md:3167

  5756. msgid "Add the following to your `vars.yml` file: `matrix_sms_bridge_container_extra_arguments=['--env SPRING_PROFILES_ACTIVE=initialsync']`"

  5757. msgstr ""

  5758. 

  5759. #: ../../../CHANGELOG.md:3168

  5760. msgid "Login to your host shell and remove old systemd file from your host: `rm /etc/systemd/system/matrix-sms-bridge-database.service`"

  5761. msgstr ""

  5762. 

  5763. #: ../../../CHANGELOG.md:3169

  5764. msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-sms-bridge,start`"

  5765. msgstr ""

  5766. 

  5767. #: ../../../CHANGELOG.md:3170

  5768. msgid "Login to your host shell and check the logs with `journalctl -u matrix-sms-bridge` until the sync finished."

  5769. msgstr ""

  5770. 

  5771. #: ../../../CHANGELOG.md:3171

  5772. msgid "Remove the var from the first step."

  5773. msgstr ""

  5774. 

  5775. #: ../../../CHANGELOG.md:3172

  5776. msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`."

  5777. msgstr ""

  5778. 

  5779. #: ../../../CHANGELOG.md:3174

  5780. msgid "2020-11-10"

  5781. msgstr ""

  5782. 

  5783. #: ../../../CHANGELOG.md:3176

  5784. msgid "Dynamic DNS support"

  5785. msgstr ""

  5786. 

  5787. #: ../../../CHANGELOG.md:3178

  5788. msgid "Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook can now manage Dynamic DNS for you using [ddclient](https://ddclient.net/)."

  5789. msgstr ""

  5790. 

  5791. #: ../../../CHANGELOG.md:3180

  5792. msgid "To learn more, follow our [Dynamic DNS docs page](docs/configuring-playbook-dynamic-dns.md)."

  5793. msgstr ""

  5794. 

  5795. #: ../../../CHANGELOG.md:3183

  5796. msgid "2020-10-28"

  5797. msgstr ""

  5798. 

  5799. #: ../../../CHANGELOG.md:3185

  5800. msgid "(Compatibility Break) https://matrix.example.com/ now redirects to https://element.example.com/"

  5801. msgstr ""

  5802. 

  5803. #: ../../../CHANGELOG.md:3187

  5804. 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."

  5805. msgstr ""

  5806. 

  5807. #: ../../../CHANGELOG.md:3189

  5808. 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))."

  5809. msgstr ""

  5810. 

  5811. #: ../../../CHANGELOG.md:3191

  5812. 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."

  5813. msgstr ""

  5814. 

  5815. #: ../../../CHANGELOG.md:3193

  5816. 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: \"\"`)."

  5817. msgstr ""

  5818. 

  5819. #: ../../../CHANGELOG.md:3196

  5820. msgid "2020-10-26"

  5821. msgstr ""

  5822. 

  5823. #: ../../../CHANGELOG.md:3198

  5824. msgid "(Compatibility Break) /_synapse/admin is no longer publicly exposed by default"

  5825. msgstr ""

  5826. 

  5827. #: ../../../CHANGELOG.md:3200

  5828. 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."

  5829. msgstr ""

  5830. 

  5831. #: ../../../CHANGELOG.md:3202

  5832. 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."

  5833. msgstr ""

  5834. 

  5835. #: ../../../CHANGELOG.md:3204

  5836. 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`):"

  5837. msgstr ""

  5838. 

  5839. #: ../../../CHANGELOG.md:3211

  5840. msgid "2020-10-02"

  5841. msgstr ""

  5842. 

  5843. #: ../../../CHANGELOG.md:3213

  5844. msgid "Minimum Ansible version raised to v2.7.0"

  5845. msgstr ""

  5846. 

  5847. #: ../../../CHANGELOG.md:3215

  5848. 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."

  5849. msgstr ""

  5850. 

  5851. #: ../../../CHANGELOG.md:3217

  5852. 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)."

  5853. msgstr ""

  5854. 

  5855. #: ../../../CHANGELOG.md:3219

  5856. msgid "Our [Ansible docs page](docs/ansible.md) contains information on how to run a more up-to-date version of Ansible."

  5857. msgstr ""

  5858. 

  5859. #: ../../../CHANGELOG.md:3222

  5860. msgid "2020-10-01"

  5861. msgstr ""

  5862. 

  5863. #: ../../../CHANGELOG.md:3224

  5864. msgid "Postgres 13 support"

  5865. msgstr ""

  5866. 

  5867. #: ../../../CHANGELOG.md:3226

  5868. msgid "The playbook now installs [Postgres 13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) by default."

  5869. msgstr ""

  5870. 

  5871. #: ../../../CHANGELOG.md:3228

  5872. 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)."

  5873. msgstr ""

  5874. 

  5875. #: ../../../CHANGELOG.md:3230

  5876. msgid "2020-09-01"

  5877. msgstr ""

  5878. 

  5879. #: ../../../CHANGELOG.md:3232

  5880. msgid "matrix-registration support"

  5881. msgstr ""

  5882. 

  5883. #: ../../../CHANGELOG.md:3234

  5884. 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."

  5885. msgstr ""

  5886. 

  5887. #: ../../../CHANGELOG.md:3236

  5888. msgid "See our [Setting up matrix-registration](docs/configuring-playbook-matrix-registration.md) documentation page to get started."

  5889. msgstr ""

  5890. 

  5891. #: ../../../CHANGELOG.md:3239

  5892. msgid "2020-08-21"

  5893. msgstr ""

  5894. 

  5895. #: ../../../CHANGELOG.md:3241

  5896. msgid "rust-synapse-compress-state support"

  5897. msgstr ""

  5898. 

  5899. #: ../../../CHANGELOG.md:3243

  5900. 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."

  5901. msgstr ""

  5902. 

  5903. #: ../../../CHANGELOG.md:3245

  5904. 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."

  5905. msgstr ""

  5906. 

  5907. #: ../../../CHANGELOG.md:3248

  5908. msgid "2020-07-22"

  5909. msgstr ""

  5910. 

  5911. #: ../../../CHANGELOG.md:3250

  5912. msgid "Synapse Admin support"

  5913. msgstr ""

  5914. 

  5915. #: ../../../CHANGELOG.md:3252

  5916. msgid "The playbook can now help you set up [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin)."

  5917. msgstr ""

  5918. 

  5919. #: ../../../CHANGELOG.md:3254

  5920. msgid "See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-admin.md) documentation to get started."

  5921. msgstr ""

  5922. 

  5923. #: ../../../CHANGELOG.md:3257

  5924. msgid "2020-07-20"

  5925. msgstr ""

  5926. 

  5927. #: ../../../CHANGELOG.md:3259

  5928. msgid "matrix-reminder-bot support"

  5929. msgstr ""

  5930. 

  5931. #: ../../../CHANGELOG.md:3261

  5932. msgid "The playbook can now help you set up [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)."

  5933. msgstr ""

  5934. 

  5935. #: ../../../CHANGELOG.md:3263

  5936. msgid "See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-matrix-reminder-bot.md) documentation to get started."

  5937. msgstr ""

  5938. 

  5939. #: ../../../CHANGELOG.md:3266

  5940. msgid "2020-07-17"

  5941. msgstr ""

  5942. 

  5943. #: ../../../CHANGELOG.md:3268

  5944. msgid "(Compatibility Break) Riot is now Element"

  5945. msgstr ""

  5946. 

  5947. #: ../../../CHANGELOG.md:3270

  5948. msgid "As per the official announcement, [Riot has been rebraned to Element](https://element.io/blog/welcome-to-element/)."

  5949. msgstr ""

  5950. 

  5951. #: ../../../CHANGELOG.md:3272

  5952. msgid "The playbook follows suit. Existing installations have a few options for how to handle this."

  5953. msgstr ""

  5954. 

  5955. #: ../../../CHANGELOG.md:3274

  5956. msgid "See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md#migrating-to-element) documentation page for more details."

  5957. msgstr ""

  5958. 

  5959. #: ../../../CHANGELOG.md:3277

  5960. msgid "2020-07-03"

  5961. msgstr ""

  5962. 

  5963. #: ../../../CHANGELOG.md:3279

  5964. msgid "Steam bridging support via mx-puppet-steam"

  5965. msgstr ""

  5966. 

  5967. #: ../../../CHANGELOG.md:3281

  5968. 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."

  5969. msgstr ""

  5970. 

  5971. #: ../../../CHANGELOG.md:3284

  5972. msgid "2020-07-01"

  5973. msgstr ""

  5974. 

  5975. #: ../../../CHANGELOG.md:3286

  5976. msgid "Discord bridging support via mx-puppet-discord"

  5977. msgstr ""

  5978. 

  5979. #: ../../../CHANGELOG.md:3288

  5980. 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."

  5981. msgstr ""

  5982. 

  5983. #: ../../../CHANGELOG.md:3290

  5984. 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)."

  5985. msgstr ""

  5986. 

  5987. #: ../../../CHANGELOG.md:3293

  5988. msgid "2020-06-30"

  5989. msgstr ""

  5990. 

  5991. #: ../../../CHANGELOG.md:3295

  5992. msgid "Instagram and Twitter bridging support"

  5993. msgstr ""

  5994. 

  5995. #: ../../../CHANGELOG.md:3297

  5996. 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."

  5997. msgstr ""

  5998. 

  5999. #: ../../../CHANGELOG.md:3299

  6000. 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."

  6001. msgstr ""

  6002. 

  6003. #: ../../../CHANGELOG.md:3302

  6004. msgid "2020-06-28"

  6005. msgstr ""

  6006. 

  6007. #: ../../../CHANGELOG.md:3304

  6008. msgid "(Post Mortem / fixed Security Issue) Re-enabling User Directory search powered by the ma1sd Identity Server"

  6009. msgstr ""

  6010. 

  6011. #: ../../../CHANGELOG.md:3306

  6012. #: ../../../CHANGELOG.md:3335

  6013. msgid "User Directory search requests used to go to the ma1sd identity server by default, which queried its own stores and the Synapse database."

  6014. msgstr ""

  6015. 

  6016. #: ../../../CHANGELOG.md:3308

  6017. 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."

  6018. msgstr ""

  6019. 

  6020. #: ../../../CHANGELOG.md:3310

  6021. 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`"

  6022. msgstr ""

  6023. 

  6024. #: ../../../CHANGELOG.md:3312

  6025. msgid "As always, re-running the playbook is enough to get the updated bits."

  6026. msgstr ""

  6027. 

  6028. #: ../../../CHANGELOG.md:3314

  6029. msgid "2020-06-11"

  6030. msgstr ""

  6031. 

  6032. #: ../../../CHANGELOG.md:3316

  6033. msgid "SMS bridging requires db reset"

  6034. msgstr ""

  6035. 

  6036. #: ../../../CHANGELOG.md:3318

  6037. 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`."

  6038. msgstr ""

  6039. 

  6040. #: ../../../CHANGELOG.md:3320

  6041. 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."

  6042. msgstr ""

  6043. 

  6044. #: ../../../CHANGELOG.md:3322

  6045. msgid "2020-06-05"

  6046. msgstr ""

  6047. 

  6048. #: ../../../CHANGELOG.md:3324

  6049. msgid "SMS bridging support"

  6050. msgstr ""

  6051. 

  6052. #: ../../../CHANGELOG.md:3326

  6053. 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)."

  6054. msgstr ""

  6055. 

  6056. #: ../../../CHANGELOG.md:3328

  6057. msgid "See our [Setting up Matrix SMS bridging](docs/configuring-playbook-bridge-matrix-bridge-sms.md) documentation page for getting started."

  6058. msgstr ""

  6059. 

  6060. #: ../../../CHANGELOG.md:3331

  6061. msgid "2020-05-19"

  6062. msgstr ""

  6063. 

  6064. #: ../../../CHANGELOG.md:3333

  6065. msgid "(Compatibility Break / Security Issue) Disabling User Directory search powered by the ma1sd Identity Server"

  6066. msgstr ""

  6067. 

  6068. #: ../../../CHANGELOG.md:3337

  6069. 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."

  6070. msgstr ""

  6071. 

  6072. #: ../../../CHANGELOG.md:3339

  6073. 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**."

  6074. msgstr ""

  6075. 

  6076. #: ../../../CHANGELOG.md:3341

  6077. 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 }}\"`"

  6078. msgstr ""

  6079. 

  6080. #: ../../../CHANGELOG.md:3344

  6081. msgid "2020-04-28"

  6082. msgstr ""

  6083. 

  6084. #: ../../../CHANGELOG.md:3346

  6085. msgid "Newer IRC bridge (with potential breaking change)"

  6086. msgstr ""

  6087. 

  6088. #: ../../../CHANGELOG.md:3348

  6089. 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."

  6090. msgstr ""

  6091. 

  6092. #: ../../../CHANGELOG.md:3357

  6093. msgid "2020-04-23"

  6094. msgstr ""

  6095. 

  6096. #: ../../../CHANGELOG.md:3359

  6097. #: ../../../CHANGELOG.md:3590

  6098. msgid "Slack bridging support"

  6099. msgstr ""

  6100. 

  6101. #: ../../../CHANGELOG.md:3361

  6102. 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."

  6103. msgstr ""

  6104. 

  6105. #: ../../../CHANGELOG.md:3363

  6106. msgid "See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-bridge-mx-puppet-slack.md) documentation page for getting started."

  6107. msgstr ""

  6108. 

  6109. #: ../../../CHANGELOG.md:3366

  6110. msgid "2020-04-09"

  6111. msgstr ""

  6112. 

  6113. #: ../../../CHANGELOG.md:3368

  6114. msgid "Skype bridging support"

  6115. msgstr ""

  6116. 

  6117. #: ../../../CHANGELOG.md:3370

  6118. 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."

  6119. msgstr ""

  6120. 

  6121. #: ../../../CHANGELOG.md:3372

  6122. msgid "See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md) documentation page for getting started."

  6123. msgstr ""

  6124. 

  6125. #: ../../../CHANGELOG.md:3375

  6126. msgid "2020-04-05"

  6127. msgstr ""

  6128. 

  6129. #: ../../../CHANGELOG.md:3377

  6130. msgid "Private Jitsi support"

  6131. msgstr ""

  6132. 

  6133. #: ../../../CHANGELOG.md:3379

  6134. 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."

  6135. msgstr ""

  6136. 

  6137. #: ../../../CHANGELOG.md:3381

  6138. 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."

  6139. msgstr ""

  6140. 

  6141. #: ../../../CHANGELOG.md:3383

  6142. 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."

  6143. msgstr ""

  6144. 

  6145. #: ../../../CHANGELOG.md:3386

  6146. msgid "2020-04-03"

  6147. msgstr ""

  6148. 

  6149. #: ../../../CHANGELOG.md:3388

  6150. msgid "(Potential Backward Compatibility Break) ma1sd replaces mxisd"

  6151. msgstr ""

  6152. 

  6153. #: ../../../CHANGELOG.md:3390

  6154. 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."

  6155. msgstr ""

  6156. 

  6157. #: ../../../CHANGELOG.md:3392

  6158. 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."

  6159. msgstr ""

  6160. 

  6161. #: ../../../CHANGELOG.md:3394

  6162. 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."

  6163. msgstr ""

  6164. 

  6165. #: ../../../CHANGELOG.md:3397

  6166. msgid "2020-03-29"

  6167. msgstr ""

  6168. 

  6169. #: ../../../CHANGELOG.md:3399

  6170. msgid "Archlinux support"

  6171. msgstr ""

  6172. 

  6173. #: ../../../CHANGELOG.md:3401

  6174. msgid "Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts, the playbook now supports installing to an [Archlinux](https://www.archlinux.org/) server."

  6175. msgstr ""

  6176. 

  6177. #: ../../../CHANGELOG.md:3404

  6178. msgid "2020-03-24"

  6179. msgstr ""

  6180. 

  6181. #: ../../../CHANGELOG.md:3406

  6182. msgid "Jitsi support"

  6183. msgstr ""

  6184. 

  6185. #: ../../../CHANGELOG.md:3408

  6186. 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)."

  6187. msgstr ""

  6188. 

  6189. #: ../../../CHANGELOG.md:3410

  6190. msgid "See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to get started."

  6191. msgstr ""

  6192. 

  6193. #: ../../../CHANGELOG.md:3413

  6194. msgid "2020-03-15"

  6195. msgstr ""

  6196. 

  6197. #: ../../../CHANGELOG.md:3415

  6198. msgid "Raspberry Pi support"

  6199. msgstr ""

  6200. 

  6201. #: ../../../CHANGELOG.md:3417

  6202. 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."

  6203. msgstr ""

  6204. 

  6205. #: ../../../CHANGELOG.md:3419

  6206. 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."

  6207. msgstr ""

  6208. 

  6209. #: ../../../CHANGELOG.md:3422

  6210. msgid "2020-02-26"

  6211. msgstr ""

  6212. 

  6213. #: ../../../CHANGELOG.md:3424

  6214. msgid "Riot-web themes are here"

  6215. msgstr ""

  6216. 

  6217. #: ../../../CHANGELOG.md:3426

  6218. msgid "The playbook now makes it easy to install custom riot-web themes."

  6219. msgstr ""

  6220. 

  6221. #: ../../../CHANGELOG.md:3428

  6222. msgid "To learn more, take a look at our [riot-web documentation on Themes](docs/configuring-playbook-riot-web.md#themes)."

  6223. msgstr ""

  6224. 

  6225. #: ../../../CHANGELOG.md:3431

  6226. msgid "2020-02-24"

  6227. msgstr ""

  6228. 

  6229. #: ../../../CHANGELOG.md:3433

  6230. msgid "Customize the server name in Riot's login page"

  6231. msgstr ""

  6232. 

  6233. #: ../../../CHANGELOG.md:3435

  6234. msgid "You can now customize the server name string that Riot-web displays in its login page."

  6235. msgstr ""

  6236. 

  6237. #: ../../../CHANGELOG.md:3437

  6238. msgid "These playbook variables, with these default values, have been added:"

  6239. msgstr ""

  6240. 

  6241. #: ../../../CHANGELOG.md:3443

  6242. 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\"."

  6243. msgstr ""

  6244. 

  6245. #: ../../../CHANGELOG.md:3445

  6246. 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."

  6247. msgstr ""

  6248. 

  6249. #: ../../../CHANGELOG.md:3448

  6250. msgid "2020-01-30"

  6251. msgstr ""

  6252. 

  6253. #: ../../../CHANGELOG.md:3450

  6254. msgid "Disabling TLSv1.1"

  6255. msgstr ""

  6256. 

  6257. #: ../../../CHANGELOG.md:3452

  6258. msgid "To improve security, we've removed TLSv1.1 support from our default matrix-nginx-proxy configuration."

  6259. msgstr ""

  6260. 

  6261. #: ../../../CHANGELOG.md:3454

  6262. 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\"`"

  6263. msgstr ""

  6264. 

  6265. #: ../../../CHANGELOG.md:3457

  6266. msgid "2020-01-21"

  6267. msgstr ""

  6268. 

  6269. #: ../../../CHANGELOG.md:3459

  6270. msgid "Postgres collation changes (action required!)"

  6271. msgstr ""

  6272. 

  6273. #: ../../../CHANGELOG.md:3461

  6274. 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."

  6275. msgstr ""

  6276. 

  6277. #: ../../../CHANGELOG.md:3463

  6278. 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."

  6279. msgstr ""

  6280. 

  6281. #: ../../../CHANGELOG.md:3465

  6282. msgid "To avoid future problems, we recommend that you run the following command:"

  6283. msgstr ""

  6284. 

  6285. #: ../../../CHANGELOG.md:3471

  6286. 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."

  6287. msgstr ""

  6288. 

  6289. #: ../../../CHANGELOG.md:3474

  6290. msgid "2020-01-14"

  6291. msgstr ""

  6292. 

  6293. #: ../../../CHANGELOG.md:3476

  6294. msgid "Added support for Appservice Webhooks"

  6295. msgstr ""

  6296. 

  6297. #: ../../../CHANGELOG.md:3478

  6298. 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."

  6299. msgstr ""

  6300. 

  6301. #: ../../../CHANGELOG.md:3480

  6302. msgid "Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-playbook-bridge-appservice-webhooks.md)."

  6303. msgstr ""

  6304. 

  6305. #: ../../../CHANGELOG.md:3483

  6306. msgid "2020-01-12"

  6307. msgstr ""

  6308. 

  6309. #: ../../../CHANGELOG.md:3485

  6310. msgid "Added support for automatic Double Puppeting for all Mautrix bridges"

  6311. msgstr ""

  6312. 

  6313. #: ../../../CHANGELOG.md:3487

  6314. msgid "Double Puppeting can now be easily enabled for all Mautrix bridges supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)."

  6315. msgstr ""

  6316. 

  6317. #: ../../../CHANGELOG.md:3489

  6318. 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."

  6319. msgstr ""

  6320. 

  6321. #: ../../../CHANGELOG.md:3491

  6322. msgid "To get started, following the playbook's documentation for the bridge you'd like to configure."

  6323. msgstr ""

  6324. 

  6325. #: ../../../CHANGELOG.md:3494

  6326. msgid "2019-12-06"

  6327. msgstr ""

  6328. 

  6329. #: ../../../CHANGELOG.md:3496

  6330. msgid "Added support for an alternative method for using another webserver"

  6331. msgstr ""

  6332. 

  6333. #: ../../../CHANGELOG.md:3498

  6334. 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)."

  6335. msgstr ""

  6336. 

  6337. #: ../../../CHANGELOG.md:3500

  6338. 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))."

  6339. msgstr ""

  6340. 

  6341. #: ../../../CHANGELOG.md:3502

  6342. 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)."

  6343. msgstr ""

  6344. 

  6345. #: ../../../CHANGELOG.md:3505

  6346. msgid "2019-11-10"

  6347. msgstr ""

  6348. 

  6349. #: ../../../CHANGELOG.md:3507

  6350. msgid "Tightened security around room directory publishing"

  6351. msgstr ""

  6352. 

  6353. #: ../../../CHANGELOG.md:3509

  6354. 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."

  6355. msgstr ""

  6356. 

  6357. #: ../../../CHANGELOG.md:3511

  6358. 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**."

  6359. msgstr ""

  6360. 

  6361. #: ../../../CHANGELOG.md:3513

  6362. 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."

  6363. msgstr ""

  6364. 

  6365. #: ../../../CHANGELOG.md:3516

  6366. msgid "2019-10-05"

  6367. msgstr ""

  6368. 

  6369. #: ../../../CHANGELOG.md:3518

  6370. msgid "Improved Postgres upgrading/importing"

  6371. msgstr ""

  6372. 

  6373. #: ../../../CHANGELOG.md:3520

  6374. 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."

  6375. msgstr ""

  6376. 

  6377. #: ../../../CHANGELOG.md:3522

  6378. 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."

  6379. msgstr ""

  6380. 

  6381. #: ../../../CHANGELOG.md:3524

  6382. 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."

  6383. msgstr ""

  6384. 

  6385. #: ../../../CHANGELOG.md:3526

  6386. msgid "Additionally, Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) now uses gzipped dump files by default, to minimize disk space usage."

  6387. msgstr ""

  6388. 

  6389. #: ../../../CHANGELOG.md:3529

  6390. msgid "2019-10-04"

  6391. msgstr ""

  6392. 

  6393. #: ../../../CHANGELOG.md:3531

  6394. msgid "Postgres 12 support"

  6395. msgstr ""

  6396. 

  6397. #: ../../../CHANGELOG.md:3533

  6398. msgid "The playbook now installs [Postgres 12](https://www.postgresql.org/about/news/1976/) by default."

  6399. msgstr ""

  6400. 

  6401. #: ../../../CHANGELOG.md:3535

  6402. 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)."

  6403. msgstr ""

  6404. 

  6405. #: ../../../CHANGELOG.md:3538

  6406. msgid "2019-10-03"

  6407. msgstr ""

  6408. 

  6409. #: ../../../CHANGELOG.md:3540

  6410. msgid "Synapse 1.4.0"

  6411. msgstr ""

  6412. 

  6413. #: ../../../CHANGELOG.md:3542

  6414. 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."

  6415. msgstr ""

  6416. 

  6417. #: ../../../CHANGELOG.md:3544

  6418. 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: ~`)."

  6419. msgstr ""

  6420. 

  6421. #: ../../../CHANGELOG.md:3546

  6422. 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."

  6423. msgstr ""

  6424. 

  6425. #: ../../../CHANGELOG.md:3548

  6426. 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."

  6427. msgstr ""

  6428. 

  6429. #: ../../../CHANGELOG.md:3551

  6430. msgid "2019-09-09"

  6431. msgstr ""

  6432. 

  6433. #: ../../../CHANGELOG.md:3553

  6434. msgid "Synapse Simple Antispam support"

  6435. msgstr ""

  6436. 

  6437. #: ../../../CHANGELOG.md:3555

  6438. 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."

  6439. msgstr ""

  6440. 

  6441. #: ../../../CHANGELOG.md:3557

  6442. msgid "From now on, you can easily install and configure this spam checker module through the playbook."

  6443. msgstr ""

  6444. 

  6445. #: ../../../CHANGELOG.md:3559

  6446. msgid "Learn more in [Setting up Synapse Simple Antispam](docs/configuring-playbook-synapse-simple-antispam.md)."

  6447. msgstr ""

  6448. 

  6449. #: ../../../CHANGELOG.md:3562

  6450. msgid "2019-08-25"

  6451. msgstr ""

  6452. 

  6453. #: ../../../CHANGELOG.md:3564

  6454. msgid "Extensible Riot-web configuration"

  6455. msgstr ""

  6456. 

  6457. #: ../../../CHANGELOG.md:3566

  6458. msgid "Similarly to [Extensible Synapse configuration](#extensible-synapse-configuration) (below), Riot-web configuration is also extensible now."

  6459. msgstr ""

  6460. 

  6461. #: ../../../CHANGELOG.md:3568

  6462. 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."

  6463. msgstr ""

  6464. 

  6465. #: ../../../CHANGELOG.md:3570

  6466. 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."

  6467. msgstr ""

  6468. 

  6469. #: ../../../CHANGELOG.md:3572

  6470. msgid "Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-web.md)."

  6471. msgstr ""

  6472. 

  6473. #: ../../../CHANGELOG.md:3575

  6474. msgid "2019-08-22"

  6475. msgstr ""

  6476. 

  6477. #: ../../../CHANGELOG.md:3577

  6478. msgid "Extensible Synapse configuration"

  6479. msgstr ""

  6480. 

  6481. #: ../../../CHANGELOG.md:3579

  6482. 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."

  6483. msgstr ""

  6484. 

  6485. #: ../../../CHANGELOG.md:3581

  6486. 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."

  6487. msgstr ""

  6488. 

  6489. #: ../../../CHANGELOG.md:3583

  6490. 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."

  6491. msgstr ""

  6492. 

  6493. #: ../../../CHANGELOG.md:3585

  6494. msgid "Learn more here in [Configuring Synapse](docs/configuring-playbook-synapse.md)."

  6495. msgstr ""

  6496. 

  6497. #: ../../../CHANGELOG.md:3588

  6498. msgid "2019-08-21"

  6499. msgstr ""

  6500. 

  6501. #: ../../../CHANGELOG.md:3592

  6502. 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."

  6503. msgstr ""

  6504. 

  6505. #: ../../../CHANGELOG.md:3594

  6506. msgid "Additional details are available in [Setting up Appservice Slack bridging](docs/configuring-playbook-bridge-appservice-slack.md)."

  6507. msgstr ""

  6508. 

  6509. #: ../../../CHANGELOG.md:3596

  6510. msgid "Google Hangouts bridging support"

  6511. msgstr ""

  6512. 

  6513. #: ../../../CHANGELOG.md:3598

  6514. 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."

  6515. msgstr ""

  6516. 

  6517. #: ../../../CHANGELOG.md:3600

  6518. msgid "Additional details are available in [Setting up Mautrix Hangouts bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)."

  6519. msgstr ""

  6520. 

  6521. #: ../../../CHANGELOG.md:3603

  6522. msgid "2019-08-05"

  6523. msgstr ""

  6524. 

  6525. #: ../../../CHANGELOG.md:3605

  6526. msgid "Email2Matrix support"

  6527. msgstr ""

  6528. 

  6529. #: ../../../CHANGELOG.md:3607

  6530. msgid "Support for [Email2Matrix](https://github.com/devture/email2matrix) has been added."

  6531. msgstr ""

  6532. 

  6533. #: ../../../CHANGELOG.md:3609

  6534. msgid "It's an optional feature that you can enable via the playbook."

  6535. msgstr ""

  6536. 

  6537. #: ../../../CHANGELOG.md:3611

  6538. msgid "To learn more, see the [playbook's documentation on Email2Matrix](./docs/configuring-playbook-email2matrix.md)."

  6539. msgstr ""

  6540. 

  6541. #: ../../../CHANGELOG.md:3614

  6542. msgid "2019-08-03"

  6543. msgstr ""

  6544. 

  6545. #: ../../../CHANGELOG.md:3616

  6546. msgid "Synapse logging level has been reduced to WARNING"

  6547. msgstr ""

  6548. 

  6549. #: ../../../CHANGELOG.md:3618

  6550. 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`."

  6551. msgstr ""

  6552. 

  6553. #: ../../../CHANGELOG.md:3620

  6554. msgid "This greatly reduces the number of log messages that are being logged, leading to:"

  6555. msgstr ""

  6556. 

  6557. #: ../../../CHANGELOG.md:3622

  6558. msgid "much less disk space dedicated to Synapse and thus, logs kept for longer"

  6559. msgstr ""

  6560. 

  6561. #: ../../../CHANGELOG.md:3623

  6562. msgid "easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages, as they're not longer buried in thousands of non-important `INFO` messages"

  6563. msgstr ""

  6564. 

  6565. #: ../../../CHANGELOG.md:3625

  6566. 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)."

  6567. msgstr ""

  6568. 

  6569. #: ../../../CHANGELOG.md:3628

  6570. msgid "2019-07-08"

  6571. msgstr ""

  6572. 

  6573. #: ../../../CHANGELOG.md:3630

  6574. msgid "Synapse Maintenance docs and synapse-janitor support are available"

  6575. msgstr ""

  6576. 

  6577. #: ../../../CHANGELOG.md:3632

  6578. msgid "The playbook can now help you with Synapse's maintenance."

  6579. msgstr ""

  6580. 

  6581. #: ../../../CHANGELOG.md:3634

  6582. 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)."

  6583. msgstr ""

  6584. 

  6585. #: ../../../CHANGELOG.md:3636

  6586. 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."

  6587. msgstr ""

  6588. 

  6589. #: ../../../CHANGELOG.md:3638

  6590. msgid "(BC Break) Rename run control variables"

  6591. msgstr ""

  6592. 

  6593. #: ../../../CHANGELOG.md:3640

  6594. msgid "Some internal playbook control variables have been renamed."

  6595. msgstr ""

  6596. 

  6597. #: ../../../CHANGELOG.md:3642

  6598. 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."

  6599. msgstr ""

  6600. 

  6601. #: ../../../CHANGELOG.md:3644

  6602. msgid "The following variables have been renamed:"

  6603. msgstr ""

  6604. 

  6605. #: ../../../CHANGELOG.md:3646

  6606. msgid "from `run_import_postgres` to `run_postgres_import`"

  6607. msgstr ""

  6608. 

  6609. #: ../../../CHANGELOG.md:3647

  6610. msgid "from `run_import_sqlite_db` to `run_postgres_import_sqlite_db`"

  6611. msgstr ""

  6612. 

  6613. #: ../../../CHANGELOG.md:3648

  6614. msgid "from `run_upgrade_postgres` to `run_postgres_upgrade`"

  6615. msgstr ""

  6616. 

  6617. #: ../../../CHANGELOG.md:3649

  6618. msgid "from `run_import_media_store` to `run_synapse_import_media_store`"

  6619. msgstr ""

  6620. 

  6621. #: ../../../CHANGELOG.md:3650

  6622. msgid "from `run_register_user` to `run_synapse_register_user`"

  6623. msgstr ""

  6624. 

  6625. #: ../../../CHANGELOG.md:3651

  6626. msgid "from `run_update_user_password` to `run_synapse_update_user_password`"

  6627. msgstr ""

  6628. 

  6629. #: ../../../CHANGELOG.md:3654

  6630. msgid "2019-07-04"

  6631. msgstr ""

  6632. 

  6633. #: ../../../CHANGELOG.md:3656

  6634. msgid "Synapse no longer logs to text files"

  6635. msgstr ""

  6636. 

  6637. #: ../../../CHANGELOG.md:3658

  6638. 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*`)."

  6639. msgstr ""

  6640. 

  6641. #: ../../../CHANGELOG.md:3660

  6642. 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`"

  6643. msgstr ""

  6644. 

  6645. #: ../../../CHANGELOG.md:3662

  6646. msgid "Because of this, the following variables have become obsolete and were removed:"

  6647. msgstr ""

  6648. 

  6649. #: ../../../CHANGELOG.md:3664

  6650. msgid "`matrix_synapse_max_log_file_size_mb`"

  6651. msgstr ""

  6652. 

  6653. #: ../../../CHANGELOG.md:3665

  6654. msgid "`matrix_synapse_max_log_files_count`"

  6655. msgstr ""

  6656. 

  6657. #: ../../../CHANGELOG.md:3667

  6658. 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*`)."

  6659. msgstr ""

  6660. 

  6661. #: ../../../CHANGELOG.md:3669

  6662. 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`)."

  6663. msgstr ""

  6664. 

  6665. #: ../../../CHANGELOG.md:3672

  6666. msgid "2019-06-27"

  6667. msgstr ""

  6668. 

  6669. #: ../../../CHANGELOG.md:3674

  6670. msgid "(BC Break) Discord bridge configuration is now entirely managed by the playbook"

  6671. msgstr ""

  6672. 

  6673. #: ../../../CHANGELOG.md:3676

  6674. 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."

  6675. msgstr ""

  6676. 

  6677. #: ../../../CHANGELOG.md:3678

  6678. msgid "From now on, the playbook will keep both configuration files sync for you."

  6679. msgstr ""

  6680. 

  6681. #: ../../../CHANGELOG.md:3680

  6682. 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."

  6683. msgstr ""

  6684. 

  6685. #: ../../../CHANGELOG.md:3682

  6686. msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-discord/config`)."

  6687. msgstr ""

  6688. 

  6689. #: ../../../CHANGELOG.md:3684

  6690. 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`)."

  6691. msgstr ""

  6692. 

  6693. #: ../../../CHANGELOG.md:3686

  6694. 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."

  6695. msgstr ""

  6696. 

  6697. #: ../../../CHANGELOG.md:3688

  6698. 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`."

  6699. msgstr ""

  6700. 

  6701. #: ../../../CHANGELOG.md:3691

  6702. msgid "2019-06-24"

  6703. msgstr ""

  6704. 

  6705. #: ../../../CHANGELOG.md:3693

  6706. msgid "(BC Break) WhatsApp bridge configuration is now entirely managed by the playbook"

  6707. msgstr ""

  6708. 

  6709. #: ../../../CHANGELOG.md:3695

  6710. 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."

  6711. msgstr ""

  6712. 

  6713. #: ../../../CHANGELOG.md:3697

  6714. #: ../../../CHANGELOG.md:3714

  6715. #: ../../../CHANGELOG.md:3733

  6716. #: ../../../CHANGELOG.md:3772

  6717. msgid "From now on, the playbook will keep the configuration in sync for you."

  6718. msgstr ""

  6719. 

  6720. #: ../../../CHANGELOG.md:3699

  6721. 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."

  6722. msgstr ""

  6723. 

  6724. #: ../../../CHANGELOG.md:3701

  6725. 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."

  6726. msgstr ""

  6727. 

  6728. #: ../../../CHANGELOG.md:3703

  6729. 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`)."

  6730. msgstr ""

  6731. 

  6732. #: ../../../CHANGELOG.md:3705

  6733. msgid "We're now following the default configuration for the WhatsApp bridge."

  6734. msgstr ""

  6735. 

  6736. #: ../../../CHANGELOG.md:3708

  6737. msgid "2019-06-20"

  6738. msgstr ""

  6739. 

  6740. #: ../../../CHANGELOG.md:3710

  6741. msgid "(BC Break) IRC bridge configuration is now entirely managed by the playbook"

  6742. msgstr ""

  6743. 

  6744. #: ../../../CHANGELOG.md:3712

  6745. 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."

  6746. msgstr ""

  6747. 

  6748. #: ../../../CHANGELOG.md:3716

  6749. 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."

  6750. msgstr ""

  6751. 

  6752. #: ../../../CHANGELOG.md:3718

  6753. 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`)."

  6754. msgstr ""

  6755. 

  6756. #: ../../../CHANGELOG.md:3720

  6757. 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."

  6758. msgstr ""

  6759. 

  6760. #: ../../../CHANGELOG.md:3722

  6761. 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`."

  6762. msgstr ""

  6763. 

  6764. #: ../../../CHANGELOG.md:3724

  6765. 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`)."

  6766. msgstr ""

  6767. 

  6768. #: ../../../CHANGELOG.md:3727

  6769. msgid "2019-06-15"

  6770. msgstr ""

  6771. 

  6772. #: ../../../CHANGELOG.md:3729

  6773. msgid "(BC Break) Telegram bridge configuration is now entirely managed by the playbook"

  6774. msgstr ""

  6775. 

  6776. #: ../../../CHANGELOG.md:3731

  6777. 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."

  6778. msgstr ""

  6779. 

  6780. #: ../../../CHANGELOG.md:3735

  6781. 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."

  6782. msgstr ""

  6783. 

  6784. #: ../../../CHANGELOG.md:3737

  6785. 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."

  6786. msgstr ""

  6787. 

  6788. #: ../../../CHANGELOG.md:3739

  6789. 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`)."

  6790. msgstr ""

  6791. 

  6792. #: ../../../CHANGELOG.md:3741

  6793. msgid "Also, we're now following the default configuration for the Telegram bridge, so some default configuration values are different:"

  6794. msgstr ""

  6795. 

  6796. #: ../../../CHANGELOG.md:3743

  6797. 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"

  6798. msgstr ""

  6799. 

  6800. #: ../../../CHANGELOG.md:3744

  6801. 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."

  6802. msgstr ""

  6803. 

  6804. #: ../../../CHANGELOG.md:3745

  6805. msgid "`authless_portals` (used to be `false`, now `true`) — creating portals from the Telegram side is now possible"

  6806. msgstr ""

  6807. 

  6808. #: ../../../CHANGELOG.md:3746

  6809. msgid "`whitelist_group_admins` (used to be `false`, now `true`) — allows Telegram group admins to use the bot commands"

  6810. msgstr ""

  6811. 

  6812. #: ../../../CHANGELOG.md:3748

  6813. 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)."

  6814. msgstr ""

  6815. 

  6816. #: ../../../CHANGELOG.md:3751

  6817. msgid "2019-06-12"

  6818. msgstr ""

  6819. 

  6820. #: ../../../CHANGELOG.md:3753

  6821. msgid "Synapse v1.0"

  6822. msgstr ""

  6823. 

  6824. #: ../../../CHANGELOG.md:3755

  6825. 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)."

  6826. msgstr ""

  6827. 

  6828. #: ../../../CHANGELOG.md:3757

  6829. 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."

  6830. msgstr ""

  6831. 

  6832. #: ../../../CHANGELOG.md:3759

  6833. msgid "**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` DNS SRV records. The latter, **must not** be removed."

  6834. msgstr ""

  6835. 

  6836. #: ../../../CHANGELOG.md:3761

  6837. 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."

  6838. msgstr ""

  6839. 

  6840. #: ../../../CHANGELOG.md:3763

  6841. 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)."

  6842. msgstr ""

  6843. 

  6844. #: ../../../CHANGELOG.md:3766

  6845. msgid "2019-06-07"

  6846. msgstr ""

  6847. 

  6848. #: ../../../CHANGELOG.md:3768

  6849. msgid "(BC Break) Facebook bridge configuration is now entirely managed by the playbook"

  6850. msgstr ""

  6851. 

  6852. #: ../../../CHANGELOG.md:3770

  6853. 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."

  6854. msgstr ""

  6855. 

  6856. #: ../../../CHANGELOG.md:3774

  6857. 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."

  6858. msgstr ""

  6859. 

  6860. #: ../../../CHANGELOG.md:3776

  6861. 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."

  6862. msgstr ""

  6863. 

  6864. #: ../../../CHANGELOG.md:3778

  6865. 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`)."

  6866. msgstr ""

  6867. 

  6868. #: ../../../CHANGELOG.md:3781

  6869. msgid "2019-05-25"

  6870. msgstr ""

  6871. 

  6872. #: ../../../CHANGELOG.md:3783

  6873. msgid "Support for exposing container ports publicly (not just to the host)"

  6874. msgstr ""

  6875. 

  6876. #: ../../../CHANGELOG.md:3785

  6877. 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."

  6878. msgstr ""

  6879. 

  6880. #: ../../../CHANGELOG.md:3787

  6881. 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`."

  6882. msgstr ""

  6883. 

  6884. #: ../../../CHANGELOG.md:3789

  6885. msgid "All such variables have been superseded by a better (more flexible) way to do it."

  6886. msgstr ""

  6887. 

  6888. #: ../../../CHANGELOG.md:3791

  6889. msgid "**Most** people (including those not using `matrix-nginx-proxy`), **don't need** to bother with this."

  6890. msgstr ""

  6891. 

  6892. #: ../../../CHANGELOG.md:3793

  6893. msgid "Porting examples follow for people having more customized setups:"

  6894. msgstr ""

  6895. 

  6896. #: ../../../CHANGELOG.md:3795

  6897. msgid "**from** `matrix_synapse_container_expose_client_api_port: true` **to** `matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`"

  6898. msgstr ""

  6899. 

  6900. #: ../../../CHANGELOG.md:3797

  6901. 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'`"

  6902. msgstr ""

  6903. 

  6904. #: ../../../CHANGELOG.md:3799

  6905. msgid "**from** `matrix_synapse_container_expose_metrics_port: true` **to** `matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`"

  6906. msgstr ""

  6907. 

  6908. #: ../../../CHANGELOG.md:3801

  6909. msgid "**from** `matrix_riot_web_container_expose_port: true` **to** `matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`"

  6910. msgstr ""

  6911. 

  6912. #: ../../../CHANGELOG.md:3803

  6913. msgid "**from** `matrix_mxisd_container_expose_port: true` **to** `matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`"

  6914. msgstr ""

  6915. 

  6916. #: ../../../CHANGELOG.md:3805

  6917. msgid "**from** `matrix_dimension_container_expose_port: true` **to** `matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`"

  6918. msgstr ""

  6919. 

  6920. #: ../../../CHANGELOG.md:3807

  6921. 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'`"

  6922. msgstr ""

  6923. 

  6924. #: ../../../CHANGELOG.md:3809

  6925. 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'`"

  6926. msgstr ""

  6927. 

  6928. #: ../../../CHANGELOG.md:3811

  6929. 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'`"

  6930. msgstr ""

  6931. 

  6932. #: ../../../CHANGELOG.md:3813

  6933. msgid "As always, if you forget to remove usage of some outdated variable, the playbook will warn you."

  6934. msgstr ""

  6935. 

  6936. #: ../../../CHANGELOG.md:3816

  6937. msgid "2019-05-23"

  6938. msgstr ""

  6939. 

  6940. #: ../../../CHANGELOG.md:3818

  6941. msgid "(BC Break) Ansible 2.8 compatibility"

  6942. msgstr ""

  6943. 

  6944. #: ../../../CHANGELOG.md:3820

  6945. 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)."

  6946. msgstr ""

  6947. 

  6948. #: ../../../CHANGELOG.md:3822

  6949. msgid "A manual change is required to the `inventory/hosts` file, changing the group name from `matrix-servers` to `matrix_servers` (dash to underscore)."

  6950. msgstr ""

  6951. 

  6952. #: ../../../CHANGELOG.md:3824

  6953. msgid "To avoid doing it manually, run this:"

  6954. msgstr ""

  6955. 

  6956. #: ../../../CHANGELOG.md:3825

  6957. msgid "Linux: `sed -i 's/matrix-servers/matrix_servers/g' inventory/hosts`"

  6958. msgstr ""

  6959. 

  6960. #: ../../../CHANGELOG.md:3826

  6961. msgid "Mac: `sed -i '' 's/matrix-servers/matrix_servers/g' inventory/hosts`"

  6962. msgstr ""

  6963. 

  6964. #: ../../../CHANGELOG.md:3829

  6965. msgid "2019-05-21"

  6966. msgstr ""

  6967. 

  6968. #: ../../../CHANGELOG.md:3831

  6969. msgid "Synapse no longer required"

  6970. msgstr ""

  6971. 

  6972. #: ../../../CHANGELOG.md:3833

  6973. msgid "The playbook no longer insists on installing [Synapse](https://github.com/element-hq/synapse) via the `matrix-synapse` role."

  6974. msgstr ""

  6975. 

  6976. #: ../../../CHANGELOG.md:3835

  6977. 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`)."

  6978. msgstr ""

  6979. 

  6980. #: ../../../CHANGELOG.md:3837

  6981. 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."

  6982. msgstr ""

  6983. 

  6984. #: ../../../CHANGELOG.md:3839

  6985. msgid "Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers."

  6986. msgstr ""

  6987. 

  6988. #: ../../../CHANGELOG.md:3841

  6989. msgid "Bridges are now separate from the Synapse role"

  6990. msgstr ""

  6991. 

  6992. #: ../../../CHANGELOG.md:3843

  6993. msgid "Bridges are no longer part of the `matrix-synapse` role. Each bridge now lives in its own separate role (`roles/custom/matrix-bridge-*`)."

  6994. msgstr ""

  6995. 

  6996. #: ../../../CHANGELOG.md:3845

  6997. 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)."

  6998. msgstr ""

  6999. 

  7000. #: ../../../CHANGELOG.md:3847

  7001. msgid "Renaming inconsistently-named Synapse variables"

  7002. msgstr ""

  7003. 

  7004. #: ../../../CHANGELOG.md:3849

  7005. msgid "For better consistency, the following variables have been renamed:"

  7006. msgstr ""

  7007. 

  7008. #: ../../../CHANGELOG.md:3851

  7009. msgid "`matrix_enable_room_list_search` was renamed to `matrix_synapse_enable_room_list_search`"

  7010. msgstr ""

  7011. 

  7012. #: ../../../CHANGELOG.md:3852

  7013. msgid "`matrix_alias_creation_rules` was renamed to `matrix_synapse_alias_creation_rules`"

  7014. msgstr ""

  7015. 

  7016. #: ../../../CHANGELOG.md:3853

  7017. msgid "`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was renamed to `matrix_synapse_room_list_publication_rules`"

  7018. msgstr ""

  7019. 

  7020. #: ../../../CHANGELOG.md:3856

  7021. msgid "2019-05-09"

  7022. msgstr ""

  7023. 

  7024. #: ../../../CHANGELOG.md:3858

  7025. msgid "Besides a myriad of bug fixes and minor improvements, here are the more notable (bigger) features we can announce today."

  7026. msgstr ""

  7027. 

  7028. #: ../../../CHANGELOG.md:3860

  7029. msgid "Mautrix Facebook/Messenger bridging support"

  7030. msgstr ""

  7031. 

  7032. #: ../../../CHANGELOG.md:3862

  7033. 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)."

  7034. msgstr ""

  7035. 

  7036. #: ../../../CHANGELOG.md:3864

  7037. msgid "Additional details are available in [Setting up Mautrix Facebook bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)."

  7038. msgstr ""

  7039. 

  7040. #: ../../../CHANGELOG.md:3866

  7041. msgid "mxisd Registration feature integration"

  7042. msgstr ""

  7043. 

  7044. #: ../../../CHANGELOG.md:3868

  7045. 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."

  7046. msgstr ""

  7047. 

  7048. #: ../../../CHANGELOG.md:3870

  7049. msgid "Learn more in [mxisd-controlled Registration](docs/configuring-playbook-mxisd.md#mxisd-controlled-registration)."

  7050. msgstr ""

  7051. 

  7052. #: ../../../CHANGELOG.md:3873

  7053. msgid "2019-04-16"

  7054. msgstr ""

  7055. 

  7056. #: ../../../CHANGELOG.md:3875

  7057. msgid "Caddy webserver examples"

  7058. msgstr ""

  7059. 

  7060. #: ../../../CHANGELOG.md:3877

  7061. 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"

  7062. msgstr ""

  7063. 

  7064. #: ../../../CHANGELOG.md:3879

  7065. msgid "2019-04-10"

  7066. msgstr ""

  7067. 

  7068. #: ../../../CHANGELOG.md:3881

  7069. msgid "Goofys support for other S3-compatible object stores"

  7070. msgstr ""

  7071. 

  7072. #: ../../../CHANGELOG.md:3883

  7073. 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),"

  7074. msgstr ""

  7075. 

  7076. #: ../../../CHANGELOG.md:3886

  7077. msgid "2019-04-03"

  7078. msgstr ""

  7079. 

  7080. #: ../../../CHANGELOG.md:3888

  7081. msgid "Ansible >= 2.5 is required"

  7082. msgstr ""

  7083. 

  7084. #: ../../../CHANGELOG.md:3890

  7085. 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)."

  7086. msgstr ""

  7087. 

  7088. #: ../../../CHANGELOG.md:3892

  7089. 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))."

  7090. msgstr ""

  7091. 

  7092. #: ../../../CHANGELOG.md:3895

  7093. msgid "2019-03-19"

  7094. msgstr ""

  7095. 

  7096. #: ../../../CHANGELOG.md:3897

  7097. msgid "TLS support for coturn"

  7098. msgstr ""

  7099. 

  7100. #: ../../../CHANGELOG.md:3899

  7101. 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."

  7102. msgstr ""

  7103. 

  7104. #: ../../../CHANGELOG.md:3901

  7105. 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:"

  7106. msgstr ""

  7107. 

  7108. #: ../../../CHANGELOG.md:3907

  7109. 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)."

  7110. msgstr ""

  7111. 

  7112. #: ../../../CHANGELOG.md:3909

  7113. msgid "People who build their own custom playbook from our roles should be aware that:"

  7114. msgstr ""

  7115. 

  7116. #: ../../../CHANGELOG.md:3911

  7117. 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)."

  7118. msgstr ""

  7119. 

  7120. #: ../../../CHANGELOG.md:3913

  7121. 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)."

  7122. msgstr ""

  7123. 

  7124. #: ../../../CHANGELOG.md:3916

  7125. msgid "2019-03-12"

  7126. msgstr ""

  7127. 

  7128. #: ../../../CHANGELOG.md:3918

  7129. msgid "matrix-nginx-proxy support for serving the base domain"

  7130. msgstr ""

  7131. 

  7132. #: ../../../CHANGELOG.md:3920

  7133. 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."

  7134. msgstr ""

  7135. 

  7136. #: ../../../CHANGELOG.md:3922

  7137. 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."

  7138. msgstr ""

  7139. 

  7140. #: ../../../CHANGELOG.md:3924

  7141. msgid "(BC break) matrix-nginx-proxy data variable renamed"

  7142. msgstr ""

  7143. 

  7144. #: ../../../CHANGELOG.md:3926

  7145. msgid "`matrix_nginx_proxy_data_path` was renamed to `matrix_nginx_proxy_base_path`."

  7146. msgstr ""

  7147. 

  7148. #: ../../../CHANGELOG.md:3928

  7149. 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)."

  7150. msgstr ""

  7151. 

  7152. #: ../../../CHANGELOG.md:3931

  7153. msgid "2019-03-10"

  7154. msgstr ""

  7155. 

  7156. #: ../../../CHANGELOG.md:3933

  7157. msgid "Dimension integration manager support"

  7158. msgstr ""

  7159. 

  7160. #: ../../../CHANGELOG.md:3935

  7161. 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."

  7162. msgstr ""

  7163. 

  7164. #: ../../../CHANGELOG.md:3938

  7165. msgid "2019-03-07"

  7166. msgstr ""

  7167. 

  7168. #: ../../../CHANGELOG.md:3940

  7169. msgid "Ability to customize mxisd's email templates"

  7170. msgstr ""

  7171. 

  7172. #: ../../../CHANGELOG.md:3942

  7173. 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."

  7174. msgstr ""

  7175. 

  7176. #: ../../../CHANGELOG.md:3945

  7177. msgid "2019-03-05"

  7178. msgstr ""

  7179. 

  7180. #: ../../../CHANGELOG.md:3947

  7181. msgid "Discord bridging support"

  7182. msgstr ""

  7183. 

  7184. #: ../../../CHANGELOG.md:3949

  7185. 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."

  7186. msgstr ""

  7187. 

  7188. #: ../../../CHANGELOG.md:3952

  7189. msgid "2019-02-19"

  7190. msgstr ""

  7191. 

  7192. #: ../../../CHANGELOG.md:3954

  7193. msgid "Renaming variables"

  7194. msgstr ""

  7195. 

  7196. #: ../../../CHANGELOG.md:3956

  7197. #: ../../../CHANGELOG.md:4273

  7198. #: ../../../CHANGELOG.md:4358

  7199. #: ../../../CHANGELOG.md:4478

  7200. msgid "The following playbook variables were renamed:"

  7201. msgstr ""

  7202. 

  7203. #: ../../../CHANGELOG.md:3958

  7204. msgid "from `host_specific_hostname_identity` to `matrix_domain`"

  7205. msgstr ""

  7206. 

  7207. #: ../../../CHANGELOG.md:3959

  7208. msgid "from `hostname_identity` to `matrix_domain`"

  7209. msgstr ""

  7210. 

  7211. #: ../../../CHANGELOG.md:3960

  7212. msgid "from `hostname_matrix` to `matrix_server_fqn_matrix`"

  7213. msgstr ""

  7214. 

  7215. #: ../../../CHANGELOG.md:3961

  7216. msgid "from `hostname_riot` to `matrix_server_fqn_riot`"

  7217. msgstr ""

  7218. 

  7219. #: ../../../CHANGELOG.md:3962

  7220. msgid "from `host_specific_matrix_ssl_lets_encrypt_support_email` to `matrix_ssl_lets_encrypt_support_email`"

  7221. msgstr ""

  7222. 

  7223. #: ../../../CHANGELOG.md:3964

  7224. msgid "Doing that, we've simplified things, made names less confusing (hopefully) and moved all variable names under the `matrix_` prefix."

  7225. msgstr ""

  7226. 

  7227. #: ../../../CHANGELOG.md:3967

  7228. msgid "2019-02-16"

  7229. msgstr ""

  7230. 

  7231. #: ../../../CHANGELOG.md:3969

  7232. msgid "Riot v1.0.1 support"

  7233. msgstr ""

  7234. 

  7235. #: ../../../CHANGELOG.md:3971

  7236. msgid "You can now use the brand new and redesigned Riot."

  7237. msgstr ""

  7238. 

  7239. #: ../../../CHANGELOG.md:3973

  7240. msgid "The new version no longer has a homepage by default, so we've also removed the custom homepage that we've been installing."

  7241. msgstr ""

  7242. 

  7243. #: ../../../CHANGELOG.md:3975

  7244. 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)."

  7245. msgstr ""

  7246. 

  7247. #: ../../../CHANGELOG.md:3978

  7248. msgid "2019-02-14"

  7249. msgstr ""

  7250. 

  7251. #: ../../../CHANGELOG.md:3980

  7252. msgid "Synapse v0.99.1"

  7253. msgstr ""

  7254. 

  7255. #: ../../../CHANGELOG.md:3982

  7256. 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."

  7257. msgstr ""

  7258. 

  7259. #: ../../../CHANGELOG.md:3984

  7260. 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."

  7261. msgstr ""

  7262. 

  7263. #: ../../../CHANGELOG.md:3987

  7264. msgid "2019-02-06"

  7265. msgstr ""

  7266. 

  7267. #: ../../../CHANGELOG.md:3989

  7268. msgid "Synapse v0.99 support and preparation for Synapse v1.0"

  7269. msgstr ""

  7270. 

  7271. #: ../../../CHANGELOG.md:3991

  7272. 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."

  7273. msgstr ""

  7274. 

  7275. #: ../../../CHANGELOG.md:3993

  7276. 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))."

  7277. msgstr ""

  7278. 

  7279. #: ../../../CHANGELOG.md:3995

  7280. 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)."

  7281. msgstr ""

  7282. 

  7283. #: ../../../CHANGELOG.md:3997

  7284. 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:"

  7285. msgstr ""

  7286. 

  7287. #: ../../../CHANGELOG.md:3999

  7288. 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."

  7289. msgstr ""

  7290. 

  7291. #: ../../../CHANGELOG.md:4001

  7292. 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)."

  7293. msgstr ""

  7294. 

  7295. #: ../../../CHANGELOG.md:4004

  7296. msgid "2019-02-01"

  7297. msgstr ""

  7298. 

  7299. #: ../../../CHANGELOG.md:4006

  7300. msgid "TLS v1.3 support"

  7301. msgstr ""

  7302. 

  7303. #: ../../../CHANGELOG.md:4008

  7304. 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."

  7305. msgstr ""

  7306. 

  7307. #: ../../../CHANGELOG.md:4010

  7308. msgid "When using:"

  7309. msgstr ""

  7310. 

  7311. #: ../../../CHANGELOG.md:4012

  7312. 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`."

  7313. msgstr ""

  7314. 

  7315. #: ../../../CHANGELOG.md:4014

  7316. 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)"

  7317. msgstr ""

  7318. 

  7319. #: ../../../CHANGELOG.md:4016

  7320. msgid "**another web server**: you don't need to do anything to accommodate this change"

  7321. msgstr ""

  7322. 

  7323. #: ../../../CHANGELOG.md:4019

  7324. msgid "2019-01-31"

  7325. msgstr ""

  7326. 

  7327. #: ../../../CHANGELOG.md:4021

  7328. msgid "IRC bridging support"

  7329. msgstr ""

  7330. 

  7331. #: ../../../CHANGELOG.md:4023

  7332. 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."

  7333. msgstr ""

  7334. 

  7335. #: ../../../CHANGELOG.md:4026

  7336. msgid "2019-01-29"

  7337. msgstr ""

  7338. 

  7339. #: ../../../CHANGELOG.md:4028

  7340. msgid "Running container processes as non-root, without capabilities and read-only"

  7341. msgstr ""

  7342. 

  7343. #: ../../../CHANGELOG.md:4030

  7344. 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."

  7345. msgstr ""

  7346. 

  7347. #: ../../../CHANGELOG.md:4032

  7348. 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."

  7349. msgstr ""

  7350. 

  7351. #: ../../../CHANGELOG.md:4034

  7352. 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."

  7353. msgstr ""

  7354. 

  7355. #: ../../../CHANGELOG.md:4036

  7356. 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."

  7357. msgstr ""

  7358. 

  7359. #: ../../../CHANGELOG.md:4038

  7360. msgid "matrix-mailer is now based on Exim, not Postfix"

  7361. msgstr ""

  7362. 

  7363. #: ../../../CHANGELOG.md:4040

  7364. 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)."

  7365. msgstr ""

  7366. 

  7367. #: ../../../CHANGELOG.md:4042

  7368. 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`)."

  7369. msgstr ""

  7370. 

  7371. #: ../../../CHANGELOG.md:4044

  7372. 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)."

  7373. msgstr ""

  7374. 

  7375. #: ../../../CHANGELOG.md:4047

  7376. msgid "2019-01-17"

  7377. msgstr ""

  7378. 

  7379. #: ../../../CHANGELOG.md:4049

  7380. msgid "(BC Break) Making the playbook's roles more independent of one another"

  7381. msgstr ""

  7382. 

  7383. #: ../../../CHANGELOG.md:4051

  7384. 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)."

  7385. msgstr ""

  7386. 

  7387. #: ../../../CHANGELOG.md:4054

  7388. 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."

  7389. msgstr ""

  7390. 

  7391. #: ../../../CHANGELOG.md:4056

  7392. msgid "With the new changes, **all roles are now only dependent on the minimal `matrix-base` role**. They are no longer dependent among themselves."

  7393. msgstr ""

  7394. 

  7395. #: ../../../CHANGELOG.md:4058

  7396. msgid "In addition, the following components can now be completely disabled (for those who want/need to):"

  7397. msgstr ""

  7398. 

  7399. #: ../../../CHANGELOG.md:4059

  7400. msgid "`matrix-coturn` by using `coturn_enabled: false`"

  7401. msgstr ""

  7402. 

  7403. #: ../../../CHANGELOG.md:4060

  7404. msgid "`matrix-mailer` by using `matrix_mailer_enabled: false`"

  7405. msgstr ""

  7406. 

  7407. #: ../../../CHANGELOG.md:4061

  7408. msgid "`matrix-postgres` by using `matrix_postgres_enabled: false`"

  7409. msgstr ""

  7410. 

  7411. #: ../../../CHANGELOG.md:4063

  7412. msgid "The following changes had to be done:"

  7413. msgstr ""

  7414. 

  7415. #: ../../../CHANGELOG.md:4065

  7416. 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."

  7417. msgstr ""

  7418. 

  7419. #: ../../../CHANGELOG.md:4067

  7420. 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."

  7421. msgstr ""

  7422. 

  7423. #: ../../../CHANGELOG.md:4069

  7424. 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`)"

  7425. msgstr ""

  7426. 

  7427. #: ../../../CHANGELOG.md:4071

  7428. 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."

  7429. msgstr ""

  7430. 

  7431. #: ../../../CHANGELOG.md:4074

  7432. msgid "2019-01-16"

  7433. msgstr ""

  7434. 

  7435. #: ../../../CHANGELOG.md:4076

  7436. msgid "Splitting the playbook into multiple roles"

  7437. msgstr ""

  7438. 

  7439. #: ../../../CHANGELOG.md:4078

  7440. 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)."

  7441. msgstr ""

  7442. 

  7443. #: ../../../CHANGELOG.md:4081

  7444. msgid "To keep the filesystem more consistent with this separation, the **Postgres data had to be relocated**."

  7445. msgstr ""

  7446. 

  7447. #: ../../../CHANGELOG.md:4083

  7448. 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`)."

  7449. msgstr ""

  7450. 

  7451. #: ../../../CHANGELOG.md:4086

  7452. msgid "2019-01-11"

  7453. msgstr ""

  7454. 

  7455. #: ../../../CHANGELOG.md:4088

  7456. msgid "(BC Break) mxisd configuration changes"

  7457. msgstr ""

  7458. 

  7459. #: ../../../CHANGELOG.md:4090

  7460. 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."

  7461. msgstr ""

  7462. 

  7463. #: ../../../CHANGELOG.md:4093

  7464. msgid "The following variables are no longer supported by this playbook:"

  7465. msgstr ""

  7466. 

  7467. #: ../../../CHANGELOG.md:4095

  7468. msgid "`matrix_mxisd_ldap_enabled`"

  7469. msgstr ""

  7470. 

  7471. #: ../../../CHANGELOG.md:4096

  7472. msgid "`matrix_mxisd_ldap_connection_host`"

  7473. msgstr ""

  7474. 

  7475. #: ../../../CHANGELOG.md:4097

  7476. msgid "`matrix_mxisd_ldap_connection_tls`"

  7477. msgstr ""

  7478. 

  7479. #: ../../../CHANGELOG.md:4098

  7480. msgid "`matrix_mxisd_ldap_connection_port`"

  7481. msgstr ""

  7482. 

  7483. #: ../../../CHANGELOG.md:4099

  7484. msgid "`matrix_mxisd_ldap_connection_baseDn`"

  7485. msgstr ""

  7486. 

  7487. #: ../../../CHANGELOG.md:4100

  7488. msgid "`matrix_mxisd_ldap_connection_baseDns`"

  7489. msgstr ""

  7490. 

  7491. #: ../../../CHANGELOG.md:4101

  7492. #: ../../../CHANGELOG.md:4102

  7493. msgid "`matrix_mxisd_ldap_connection_bindDn`"

  7494. msgstr ""

  7495. 

  7496. #: ../../../CHANGELOG.md:4103

  7497. #: ../../../CHANGELOG.md:4107

  7498. msgid "`matrix_mxisd_ldap_connection_bindPassword`"

  7499. msgstr ""

  7500. 

  7501. #: ../../../CHANGELOG.md:4104

  7502. msgid "`matrix_mxisd_ldap_filter`"

  7503. msgstr ""

  7504. 

  7505. #: ../../../CHANGELOG.md:4105

  7506. msgid "`matrix_mxisd_ldap_attribute_uid_type`"

  7507. msgstr ""

  7508. 

  7509. #: ../../../CHANGELOG.md:4106

  7510. msgid "`matrix_mxisd_ldap_attribute_uid_value`"

  7511. msgstr ""

  7512. 

  7513. #: ../../../CHANGELOG.md:4108

  7514. msgid "`matrix_mxisd_ldap_attribute_name`"

  7515. msgstr ""

  7516. 

  7517. #: ../../../CHANGELOG.md:4109

  7518. msgid "`matrix_mxisd_ldap_attribute_threepid_email`"

  7519. msgstr ""

  7520. 

  7521. #: ../../../CHANGELOG.md:4110

  7522. msgid "`matrix_mxisd_ldap_attribute_threepid_msisdn`"

  7523. msgstr ""

  7524. 

  7525. #: ../../../CHANGELOG.md:4111

  7526. msgid "`matrix_mxisd_ldap_identity_filter`"

  7527. msgstr ""

  7528. 

  7529. #: ../../../CHANGELOG.md:4112

  7530. msgid "`matrix_mxisd_ldap_identity_medium`"

  7531. msgstr ""

  7532. 

  7533. #: ../../../CHANGELOG.md:4113

  7534. msgid "`matrix_mxisd_ldap_auth_filter`"

  7535. msgstr ""

  7536. 

  7537. #: ../../../CHANGELOG.md:4114

  7538. msgid "`matrix_mxisd_ldap_directory_filter`"

  7539. msgstr ""

  7540. 

  7541. #: ../../../CHANGELOG.md:4115

  7542. msgid "`matrix_mxisd_template_config`"

  7543. msgstr ""

  7544. 

  7545. #: ../../../CHANGELOG.md:4117

  7546. 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."

  7547. msgstr ""

  7548. 

  7549. #: ../../../CHANGELOG.md:4119

  7550. msgid "This new way of configuring mxisd is beneficial because:"

  7551. msgstr ""

  7552. 

  7553. #: ../../../CHANGELOG.md:4121

  7554. msgid "it lets us support all mxisd configuration options, as the playbook simply forwards them to mxisd without needing to care or understand them"

  7555. msgstr ""

  7556. 

  7557. #: ../../../CHANGELOG.md:4122

  7558. msgid "it lets you upgrade to newer mxisd versions and make use of their features, without us having to add support for them explicitly"

  7559. msgstr ""

  7560. 

  7561. #: ../../../CHANGELOG.md:4125

  7562. msgid "2019-01-08"

  7563. msgstr ""

  7564. 

  7565. #: ../../../CHANGELOG.md:4127

  7566. msgid "(BC Break) Cronjob schedule no longer configurable"

  7567. msgstr ""

  7568. 

  7569. #: ../../../CHANGELOG.md:4129

  7570. msgid "Due to the way we manage cronjobs now, you can no longer configure the schedule they're invoked at."

  7571. msgstr ""

  7572. 

  7573. #: ../../../CHANGELOG.md:4131

  7574. 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."

  7575. msgstr ""

  7576. 

  7577. #: ../../../CHANGELOG.md:4134

  7578. 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!"

  7579. msgstr ""

  7580. 

  7581. #: ../../../CHANGELOG.md:4137

  7582. msgid "2018-12-23"

  7583. msgstr ""

  7584. 

  7585. #: ../../../CHANGELOG.md:4139

  7586. msgid "(BC Break) More SSL certificate retrieval methods"

  7587. msgstr ""

  7588. 

  7589. #: ../../../CHANGELOG.md:4141

  7590. msgid "The playbook now lets you decide between 3 different SSL certificate retrieval methods:"

  7591. msgstr ""

  7592. 

  7593. #: ../../../CHANGELOG.md:4142

  7594. msgid "(default) obtaining free SSL certificates from Let's Encrypt"

  7595. msgstr ""

  7596. 

  7597. #: ../../../CHANGELOG.md:4143

  7598. msgid "generating self-signed SSL certificates"

  7599. msgstr ""

  7600. 

  7601. #: ../../../CHANGELOG.md:4144

  7602. msgid "managing SSL certificates manually"

  7603. msgstr ""

  7604. 

  7605. #: ../../../CHANGELOG.md:4146

  7606. msgid "Learn more in [Adjusting SSL certificate retrieval](docs/configuring-playbook-ssl-certificates.md)."

  7607. msgstr ""

  7608. 

  7609. #: ../../../CHANGELOG.md:4148

  7610. 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:"

  7611. msgstr ""

  7612. 

  7613. #: ../../../CHANGELOG.md:4150

  7614. msgid "before: `host_specific_matrix_ssl_support_email`"

  7615. msgstr ""

  7616. 

  7617. #: ../../../CHANGELOG.md:4151

  7618. msgid "after: `host_specific_matrix_ssl_lets_encrypt_support_email`"

  7619. msgstr ""

  7620. 

  7621. #: ../../../CHANGELOG.md:4153

  7622. msgid "(BC Break) mxisd upgrade with multiple base DN support"

  7623. msgstr ""

  7624. 

  7625. #: ../../../CHANGELOG.md:4155

  7626. 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)."

  7627. msgstr ""

  7628. 

  7629. #: ../../../CHANGELOG.md:4157

  7630. 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)."

  7631. msgstr ""

  7632. 

  7633. #: ../../../CHANGELOG.md:4159

  7634. msgid "Example change:"

  7635. msgstr ""

  7636. 

  7637. #: ../../../CHANGELOG.md:4161

  7638. msgid "before: `matrix_mxisd_ldap_connection_baseDn: OU=Users,DC=example,DC=org`"

  7639. msgstr ""

  7640. 

  7641. #: ../../../CHANGELOG.md:4162

  7642. msgid "after: `matrix_mxisd_ldap_connection_baseDns: ['OU=Users,DC=example,DC=org']`"

  7643. msgstr ""

  7644. 

  7645. #: ../../../CHANGELOG.md:4165

  7646. msgid "2018-12-21"

  7647. msgstr ""

  7648. 

  7649. #: ../../../CHANGELOG.md:4167

  7650. msgid "Synapse 0.34.0 and Python 3"

  7651. msgstr ""

  7652. 

  7653. #: ../../../CHANGELOG.md:4169

  7654. 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)."

  7655. msgstr ""

  7656. 

  7657. #: ../../../CHANGELOG.md:4172

  7658. msgid "2018-12-12"

  7659. msgstr ""

  7660. 

  7661. #: ../../../CHANGELOG.md:4174

  7662. msgid "Riot homepage customization"

  7663. msgstr ""

  7664. 

  7665. #: ../../../CHANGELOG.md:4176

  7666. 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`."

  7667. msgstr ""

  7668. 

  7669. #: ../../../CHANGELOG.md:4179

  7670. msgid "2018-12-04"

  7671. msgstr ""

  7672. 

  7673. #: ../../../CHANGELOG.md:4181

  7674. msgid "mxisd extensibility"

  7675. msgstr ""

  7676. 

  7677. #: ../../../CHANGELOG.md:4183

  7678. 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`)."

  7679. msgstr ""

  7680. 

  7681. #: ../../../CHANGELOG.md:4186

  7682. msgid "2018-11-28"

  7683. msgstr ""

  7684. 

  7685. #: ../../../CHANGELOG.md:4188

  7686. msgid "More scripts"

  7687. msgstr ""

  7688. 

  7689. #: ../../../CHANGELOG.md:4190

  7690. msgid "matrix-remove-all allows to uninstall everything with a single command"

  7691. msgstr ""

  7692. 

  7693. #: ../../../CHANGELOG.md:4191

  7694. msgid "matrix-make-user-admin allows to upgrade a user's privileges"

  7695. msgstr ""

  7696. 

  7697. #: ../../../CHANGELOG.md:4193

  7698. msgid "LDAP auth support via matrix-synapse-ldap3"

  7699. msgstr ""

  7700. 

  7701. #: ../../../CHANGELOG.md:4195

  7702. msgid "The playbook can now install and configure [LDAP auth support](https://github.com/matrix-org/matrix-synapse-ldap3) for you."

  7703. msgstr ""

  7704. 

  7705. #: ../../../CHANGELOG.md:4197

  7706. msgid "Additional details are available in [Setting up the LDAP authentication password provider module](docs/configuring-playbook-ldap-auth.md)."

  7707. msgstr ""

  7708. 

  7709. #: ../../../CHANGELOG.md:4200

  7710. msgid "2018-11-23"

  7711. msgstr ""

  7712. 

  7713. #: ../../../CHANGELOG.md:4202

  7714. msgid "Support for controlling public registration and room auto-join"

  7715. msgstr ""

  7716. 

  7717. #: ../../../CHANGELOG.md:4204

  7718. msgid "The playbook now lets you enable public registration for users (controlled via `matrix_synapse_enable_registration`). By default, public registration is forbidden."

  7719. msgstr ""

  7720. 

  7721. #: ../../../CHANGELOG.md:4206

  7722. msgid "You can also make people automatically get auto-joined to rooms (controlled via `matrix_synapse_auto_join_rooms`)."

  7723. msgstr ""

  7724. 

  7725. #: ../../../CHANGELOG.md:4208

  7726. msgid "Support for changing the welcome user ID (welcome bot)"

  7727. msgstr ""

  7728. 

  7729. #: ../../../CHANGELOG.md:4210

  7730. 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."

  7731. msgstr ""

  7732. 

  7733. #: ../../../CHANGELOG.md:4213

  7734. msgid "2018-11-14"

  7735. msgstr ""

  7736. 

  7737. #: ../../../CHANGELOG.md:4215

  7738. msgid "Ability to set Synapse log levels"

  7739. msgstr ""

  7740. 

  7741. #: ../../../CHANGELOG.md:4217

  7742. msgid "The playbook now allows you to set the log levels used by Synapse. The default logging levels remain the same."

  7743. msgstr ""

  7744. 

  7745. #: ../../../CHANGELOG.md:4219

  7746. 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"

  7747. msgstr ""

  7748. 

  7749. #: ../../../CHANGELOG.md:4228

  7750. msgid "2018-11-03"

  7751. msgstr ""

  7752. 

  7753. #: ../../../CHANGELOG.md:4230

  7754. msgid "Customize parts of Riot's config"

  7755. msgstr ""

  7756. 

  7757. #: ../../../CHANGELOG.md:4232

  7758. msgid "You can now customize some parts of Riot's `config.json`. These playbook variables, with these default values, have been added:"

  7759. msgstr ""

  7760. 

  7761. #: ../../../CHANGELOG.md:4243

  7762. 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:"

  7763. msgstr ""

  7764. 

  7765. #: ../../../CHANGELOG.md:4252

  7766. msgid "SSL protocols used to serve Riot and Synapse"

  7767. msgstr ""

  7768. 

  7769. #: ../../../CHANGELOG.md:4254

  7770. 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."

  7771. msgstr ""

  7772. 

  7773. #: ../../../CHANGELOG.md:4256

  7774. msgid "You may wish to re-enable TLSv1 if you need to access Riot in older browsers."

  7775. msgstr ""

  7776. 

  7777. #: ../../../CHANGELOG.md:4258

  7778. msgid "Note: Currently the dockerized nginx doesn't support TLSv1.3. See https://github.com/nginxinc/docker-nginx/issues/190 for more details."

  7779. msgstr ""

  7780. 

  7781. #: ../../../CHANGELOG.md:4261

  7782. msgid "2018-11-01"

  7783. msgstr ""

  7784. 

  7785. #: ../../../CHANGELOG.md:4263

  7786. msgid "Postgres 11 support"

  7787. msgstr ""

  7788. 

  7789. #: ../../../CHANGELOG.md:4265

  7790. msgid "The playbook now installs [Postgres 11](https://www.postgresql.org/about/news/1894/) by default."

  7791. msgstr ""

  7792. 

  7793. #: ../../../CHANGELOG.md:4267

  7794. 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)."

  7795. msgstr ""

  7796. 

  7797. #: ../../../CHANGELOG.md:4269

  7798. #: ../../../CHANGELOG.md:4356

  7799. #: ../../../CHANGELOG.md:4476

  7800. msgid "(BC Break) Renaming playbook variables"

  7801. msgstr ""

  7802. 

  7803. #: ../../../CHANGELOG.md:4271

  7804. 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."

  7805. msgstr ""

  7806. 

  7807. #: ../../../CHANGELOG.md:4275

  7808. msgid "from `matrix_docker_image_mxisd` to `matrix_mxisd_docker_image`"

  7809. msgstr ""

  7810. 

  7811. #: ../../../CHANGELOG.md:4276

  7812. msgid "from `matrix_docker_image_mautrix_telegram` to `matrix_mautrix_telegram_docker_image`"

  7813. msgstr ""

  7814. 

  7815. #: ../../../CHANGELOG.md:4277

  7816. msgid "from `matrix_docker_image_mautrix_whatsapp` to `matrix_mautrix_whatsapp_docker_image`"

  7817. msgstr ""

  7818. 

  7819. #: ../../../CHANGELOG.md:4278

  7820. msgid "from `matrix_docker_image_mailer` to `matrix_mailer_docker_image`"

  7821. msgstr ""

  7822. 

  7823. #: ../../../CHANGELOG.md:4279

  7824. msgid "from `matrix_docker_image_coturn` to `coturn_container_image`"

  7825. msgstr ""

  7826. 

  7827. #: ../../../CHANGELOG.md:4280

  7828. msgid "from `matrix_docker_image_goofys` to `matrix_s3_goofys_docker_image`"

  7829. msgstr ""

  7830. 

  7831. #: ../../../CHANGELOG.md:4281

  7832. msgid "from `matrix_docker_image_riot` to `matrix_riot_web_docker_image`"

  7833. msgstr ""

  7834. 

  7835. #: ../../../CHANGELOG.md:4282

  7836. msgid "from `matrix_docker_image_nginx` to `matrix_nginx_proxy_docker_image`"

  7837. msgstr ""

  7838. 

  7839. #: ../../../CHANGELOG.md:4283

  7840. msgid "from `matrix_docker_image_synapse` to `matrix_synapse_docker_image`"

  7841. msgstr ""

  7842. 

  7843. #: ../../../CHANGELOG.md:4284

  7844. msgid "from `matrix_docker_image_postgres_v9` to `matrix_postgres_docker_image_v9`"

  7845. msgstr ""

  7846. 

  7847. #: ../../../CHANGELOG.md:4285

  7848. msgid "from `matrix_docker_image_postgres_v10` to `matrix_postgres_docker_image_v10`"

  7849. msgstr ""

  7850. 

  7851. #: ../../../CHANGELOG.md:4286

  7852. msgid "from `matrix_docker_image_postgres_latest` to `matrix_postgres_docker_image_latest`"

  7853. msgstr ""

  7854. 

  7855. #: ../../../CHANGELOG.md:4289

  7856. msgid "2018-10-26"

  7857. msgstr ""

  7858. 

  7859. #: ../../../CHANGELOG.md:4291

  7860. msgid "Mautrix Whatsapp bridging support"

  7861. msgstr ""

  7862. 

  7863. #: ../../../CHANGELOG.md:4293

  7864. 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)."

  7865. msgstr ""

  7866. 

  7867. #: ../../../CHANGELOG.md:4295

  7868. msgid "Additional details are available in [Setting up Mautrix Whatsapp bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)."

  7869. msgstr ""

  7870. 

  7871. #: ../../../CHANGELOG.md:4298

  7872. msgid "2018-10-25"

  7873. msgstr ""

  7874. 

  7875. #: ../../../CHANGELOG.md:4300

  7876. msgid "Support for controlling Matrix federation"

  7877. msgstr ""

  7878. 

  7879. #: ../../../CHANGELOG.md:4302

  7880. 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."

  7881. msgstr ""

  7882. 

  7883. #: ../../../CHANGELOG.md:4305

  7884. msgid "2018-10-24"

  7885. msgstr ""

  7886. 

  7887. #: ../../../CHANGELOG.md:4307

  7888. msgid "Disabling riot-web guests"

  7889. msgstr ""

  7890. 

  7891. #: ../../../CHANGELOG.md:4309

  7892. 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."

  7893. msgstr ""

  7894. 

  7895. #: ../../../CHANGELOG.md:4312

  7896. msgid "2018-10-21"

  7897. msgstr ""

  7898. 

  7899. #: ../../../CHANGELOG.md:4314

  7900. msgid "Self-check maintenance command"

  7901. msgstr ""

  7902. 

  7903. #: ../../../CHANGELOG.md:4316

  7904. msgid "The playbook can now [check if services are configured correctly](docs/maintenance-and-troubleshooting.md#how-to-check-if-services-work)."

  7905. msgstr ""

  7906. 

  7907. #: ../../../CHANGELOG.md:4319

  7908. msgid "2018-10-05"

  7909. msgstr ""

  7910. 

  7911. #: ../../../CHANGELOG.md:4321

  7912. msgid "Presence tracking made configurable"

  7913. msgstr ""

  7914. 

  7915. #: ../../../CHANGELOG.md:4323

  7916. 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)."

  7917. msgstr ""

  7918. 

  7919. #: ../../../CHANGELOG.md:4325

  7920. msgid "If users participate in large rooms with many other servers, disabling presence will decrease server load significantly."

  7921. msgstr ""

  7922. 

  7923. #: ../../../CHANGELOG.md:4328

  7924. msgid "2018-09-27"

  7925. msgstr ""

  7926. 

  7927. #: ../../../CHANGELOG.md:4330

  7928. msgid "Synapse Cache Factor made configurable"

  7929. msgstr ""

  7930. 

  7931. #: ../../../CHANGELOG.md:4332

  7932. 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`)."

  7933. msgstr ""

  7934. 

  7935. #: ../../../CHANGELOG.md:4334

  7936. 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"

  7937. msgstr ""

  7938. 

  7939. #: ../../../CHANGELOG.md:4337

  7940. msgid "2018-09-26"

  7941. msgstr ""

  7942. 

  7943. #: ../../../CHANGELOG.md:4339

  7944. msgid "Disabling Docker container logging"

  7945. msgstr ""

  7946. 

  7947. #: ../../../CHANGELOG.md:4341

  7948. msgid "`--log-driver=none` is used for all Docker containers now."

  7949. msgstr ""

  7950. 

  7951. #: ../../../CHANGELOG.md:4343

  7952. 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."

  7953. msgstr ""

  7954. 

  7955. #: ../../../CHANGELOG.md:4345

  7956. 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."

  7957. msgstr ""

  7958. 

  7959. #: ../../../CHANGELOG.md:4348

  7960. msgid "2018-09-17"

  7961. msgstr ""

  7962. 

  7963. #: ../../../CHANGELOG.md:4350

  7964. msgid "Service discovery support"

  7965. msgstr ""

  7966. 

  7967. #: ../../../CHANGELOG.md:4352

  7968. 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."

  7969. msgstr ""

  7970. 

  7971. #: ../../../CHANGELOG.md:4354

  7972. msgid "Additional details are available in [Configuring service discovery via .well-known](docs/configuring-well-known.md)."

  7973. msgstr ""

  7974. 

  7975. #: ../../../CHANGELOG.md:4360

  7976. msgid "from `matrix_nginx_riot_web_data_path` to `matrix_riot_web_data_path`"

  7977. msgstr ""

  7978. 

  7979. #: ../../../CHANGELOG.md:4361

  7980. msgid "from `matrix_riot_web_default_identity_server_url` to `matrix_identity_server_url`"

  7981. msgstr ""

  7982. 

  7983. #: ../../../CHANGELOG.md:4364

  7984. msgid "2018-09-07"

  7985. msgstr ""

  7986. 

  7987. #: ../../../CHANGELOG.md:4366

  7988. msgid "Mautrix Telegram bridging support"

  7989. msgstr ""

  7990. 

  7991. #: ../../../CHANGELOG.md:4368

  7992. 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)."

  7993. msgstr ""

  7994. 

  7995. #: ../../../CHANGELOG.md:4370

  7996. msgid "Additional details are available in [Setting up Mautrix Telegram bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)."

  7997. msgstr ""

  7998. 

  7999. #: ../../../CHANGELOG.md:4372

  8000. msgid "Events cache size increase and configurability for Matrix Synapse"

  8001. msgstr ""

  8002. 

  8003. #: ../../../CHANGELOG.md:4374

  8004. msgid "The playbook now lets you configure Matrix Synapse's `event_cache_size` configuration via the `matrix_synapse_event_cache_size` playbook variable."

  8005. msgstr ""

  8006. 

  8007. #: ../../../CHANGELOG.md:4376

  8008. msgid "Previously, this value was hardcoded to `\"10K\"`. From now on, a more reasonable default of `\"100K\"` is used."

  8009. msgstr ""

  8010. 

  8011. #: ../../../CHANGELOG.md:4378

  8012. msgid "Password-peppering support for Matrix Synapse"

  8013. msgstr ""

  8014. 

  8015. #: ../../../CHANGELOG.md:4380

  8016. 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."

  8017. msgstr ""

  8018. 

  8019. #: ../../../CHANGELOG.md:4382

  8020. msgid "Statistics-reporting support for Matrix Synapse"

  8021. msgstr ""

  8022. 

  8023. #: ../../../CHANGELOG.md:4384

  8024. 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."

  8025. msgstr ""

  8026. 

  8027. #: ../../../CHANGELOG.md:4386

  8028. 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."

  8029. msgstr ""

  8030. 

  8031. #: ../../../CHANGELOG.md:4389

  8032. msgid "2018-08-29"

  8033. msgstr ""

  8034. 

  8035. #: ../../../CHANGELOG.md:4391

  8036. msgid "Changing the way SSL certificates are retrieved"

  8037. msgstr ""

  8038. 

  8039. #: ../../../CHANGELOG.md:4393

  8040. 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."

  8041. msgstr ""

  8042. 

  8043. #: ../../../CHANGELOG.md:4395

  8044. 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)."

  8045. msgstr ""

  8046. 

  8047. #: ../../../CHANGELOG.md:4397

  8048. 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:"

  8049. msgstr ""

  8050. 

  8051. #: ../../../CHANGELOG.md:4399

  8052. msgid "`systemctl stop 'matrix*'`"

  8053. msgstr ""

  8054. 

  8055. #: ../../../CHANGELOG.md:4400

  8056. msgid "stop your custom webserver, if you're running one (only affects you if you've installed with `matrix_nginx_proxy_enabled: false`)"

  8057. msgstr ""

  8058. 

  8059. #: ../../../CHANGELOG.md:4401

  8060. msgid "`mv /matrix/ssl /matrix/ssl-acmetool-delete-later`"

  8061. msgstr ""

  8062. 

  8063. #: ../../../CHANGELOG.md:4402

  8064. msgid "re-run the playbook's [installation](docs/installing.md)"

  8065. msgstr ""

  8066. 

  8067. #: ../../../CHANGELOG.md:4403

  8068. msgid "possibly delete `/matrix/ssl-acmetool-delete-later`"

  8069. msgstr ""

  8070. 

  8071. #: ../../../CHANGELOG.md:4406

  8072. msgid "2018-08-21"

  8073. msgstr ""

  8074. 

  8075. #: ../../../CHANGELOG.md:4408

  8076. msgid "Matrix Corporal support"

  8077. msgstr ""

  8078. 

  8079. #: ../../../CHANGELOG.md:4410

  8080. msgid "The playbook can now install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you."

  8081. msgstr ""

  8082. 

  8083. #: ../../../CHANGELOG.md:4412

  8084. msgid "Additional details are available in [Setting up Matrix Corporal](docs/configuring-playbook-matrix-corporal.md)."

  8085. msgstr ""

  8086. 

  8087. #: ../../../CHANGELOG.md:4415

  8088. msgid "2018-08-20"

  8089. msgstr ""

  8090. 

  8091. #: ../../../CHANGELOG.md:4417

  8092. msgid "Matrix Synapse rate limit control variables"

  8093. msgstr ""

  8094. 

  8095. #: ../../../CHANGELOG.md:4419

  8096. msgid "The following new variables can now be configured to control Matrix Synapse's rate-limiting (default values are shown below)."

  8097. msgstr ""

  8098. 

  8099. #: ../../../CHANGELOG.md:4426

  8100. msgid "Shared Secret Auth support via matrix-synapse-shared-secret-auth"

  8101. msgstr ""

  8102. 

  8103. #: ../../../CHANGELOG.md:4428

  8104. msgid "The playbook can now install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you."

  8105. msgstr ""

  8106. 

  8107. #: ../../../CHANGELOG.md:4430

  8108. msgid "Additional details are available in [Setting up the Shared Secret Auth password provider module](docs/configuring-playbook-shared-secret-auth.md)."

  8109. msgstr ""

  8110. 

  8111. #: ../../../CHANGELOG.md:4433

  8112. msgid "2018-08-17"

  8113. msgstr ""

  8114. 

  8115. #: ../../../CHANGELOG.md:4435

  8116. msgid "REST auth support via matrix-synapse-rest-auth"

  8117. msgstr ""

  8118. 

  8119. #: ../../../CHANGELOG.md:4437

  8120. msgid "The playbook can now install and configure [matrix-synapse-rest-auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you."

  8121. msgstr ""

  8122. 

  8123. #: ../../../CHANGELOG.md:4439

  8124. msgid "Additional details are available in [Setting up the REST authentication password provider module](docs/configuring-playbook-rest-auth.md)."

  8125. msgstr ""

  8126. 

  8127. #: ../../../CHANGELOG.md:4441

  8128. msgid "Compression improvements"

  8129. msgstr ""

  8130. 

  8131. #: ../../../CHANGELOG.md:4443

  8132. msgid "Shifted Matrix Synapse compression from happening in the Matrix Synapse, to happening in the nginx proxy that's in front of it."

  8133. msgstr ""

  8134. 

  8135. #: ../../../CHANGELOG.md:4446

  8136. 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."

  8137. msgstr ""

  8138. 

  8139. #: ../../../CHANGELOG.md:4449

  8140. msgid "Disabling some unnecessary Synapse services"

  8141. msgstr ""

  8142. 

  8143. #: ../../../CHANGELOG.md:4451

  8144. msgid "The following services are not necessary, so they have been disabled:"

  8145. msgstr ""

  8146. 

  8147. #: ../../../CHANGELOG.md:4452

  8148. msgid "on the federation port (8448): the `client` service"

  8149. msgstr ""

  8150. 

  8151. #: ../../../CHANGELOG.md:4453

  8152. msgid "on the http port (8008, exposed over 443): the old Angular `webclient` and the `federation` service"

  8153. msgstr ""

  8154. 

  8155. #: ../../../CHANGELOG.md:4455

  8156. msgid "Federation runs only on the federation port (8448) now. The Client APIs run only on the http port (8008) now."

  8157. msgstr ""

  8158. 

  8159. #: ../../../CHANGELOG.md:4458

  8160. msgid "2018-08-15"

  8161. msgstr ""

  8162. 

  8163. #: ../../../CHANGELOG.md:4460

  8164. msgid "mxisd Identity Server support"

  8165. msgstr ""

  8166. 

  8167. #: ../../../CHANGELOG.md:4462

  8168. 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)."

  8169. msgstr ""

  8170. 

  8171. #: ../../../CHANGELOG.md:4465

  8172. msgid "2018-08-14"

  8173. msgstr ""

  8174. 

  8175. #: ../../../CHANGELOG.md:4467

  8176. msgid "Email-sending support"

  8177. msgstr ""

  8178. 

  8179. #: ../../../CHANGELOG.md:4469

  8180. 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)."

  8181. msgstr ""

  8182. 

  8183. #: ../../../CHANGELOG.md:4471

  8184. msgid "With this, Matrix Synapse is able to send email notifications for missed messages, etc."

  8185. msgstr ""

  8186. 

  8187. #: ../../../CHANGELOG.md:4474

  8188. msgid "2018-08-08"

  8189. msgstr ""

  8190. 

  8191. #: ../../../CHANGELOG.md:4480

  8192. msgid "from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`"

  8193. msgstr ""

  8194. 

  8195. #: ../../../CHANGELOG.md:4481

  8196. msgid "from `matrix_max_log_file_size_mb` to `matrix_synapse_max_log_file_size_mb`"

  8197. msgstr ""

  8198. 

  8199. #: ../../../CHANGELOG.md:4482

  8200. msgid "from `matrix_max_log_files_count` to `matrix_synapse_max_log_files_count`"

  8201. msgstr ""

  8202. 

  8203. #: ../../../CHANGELOG.md:4483

  8204. msgid "from `docker_matrix_image` to `matrix_docker_image_synapse`"

  8205. msgstr ""

  8206. 

  8207. #: ../../../CHANGELOG.md:4484

  8208. msgid "from `docker_nginx_image` to `matrix_docker_image_nginx`"

  8209. msgstr ""

  8210. 

  8211. #: ../../../CHANGELOG.md:4485

  8212. msgid "from `docker_riot_image` to `matrix_docker_image_riot`"

  8213. msgstr ""

  8214. 

  8215. #: ../../../CHANGELOG.md:4486

  8216. msgid "from `docker_goofys_image` to `matrix_docker_image_goofys`"

  8217. msgstr ""

  8218. 

  8219. #: ../../../CHANGELOG.md:4487

  8220. msgid "from `docker_coturn_image` to `matrix_docker_image_coturn`"

  8221. msgstr ""

  8222. 

  8223. #: ../../../CHANGELOG.md:4489

  8224. msgid "If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names."

  8225. msgstr ""

  8226. 

  8227. #: ../../../CHANGELOG.md:4491

  8228. msgid "Renaming Ansible playbook tag"

  8229. msgstr ""

  8230. 

  8231. #: ../../../CHANGELOG.md:4493

  8232. msgid "The command for executing the whole playbook has changed. The `setup-main` tag got renamed to `setup-all`."

  8233. msgstr ""

  8234. 

  8235. #: ../../../CHANGELOG.md:4495

  8236. msgid "Docker container linking"

  8237. msgstr ""

  8238. 

  8239. #: ../../../CHANGELOG.md:4497

  8240. 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."

  8241. msgstr ""