overmind
/
matrix-docker-ansible-deploy
réplica de https://github.com/spantaleev/matrix-docker-ansible-deploy
1
0
Fork 0
Código Incidencias 0 Lanzamientos 0 Wiki Actividad
Matrix Docker Ansible eploy
No puede seleccionar más de 25 temas Los temas deben comenzar con una letra o número, pueden incluir guiones ('-') y pueden tener hasta 35 caracteres de largo.
10090 Commits
13 Ramas
950 MiB
 
 
Árbol: ec00a76b14
Ramas Etiquetas
${ item.name }
Crear rama ${ searchTerm }
desde 'ec00a76b14'
${ noResults }
matrix-docker-ansible-deploy/i18n/locales/bg/LC_MESSAGES/CHANGELOG.po

7071 líneas
356 KiB
Original Blame Histórico 

  1. # SOME DESCRIPTIVE TITLE.

  2. # Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community

  3. # members

  4. # This file is distributed under the same license as the

  5. # matrix-docker-ansible-deploy package.

  6. # FIRST AUTHOR <EMAIL@ADDRESS>, 2024.

  7. #

  8. #, fuzzy

  9. msgid ""

  10. msgstr ""

  11. "Project-Id-Version: matrix-docker-ansible-deploy \n"

  12. "Report-Msgid-Bugs-To: \n"

  13. "POT-Creation-Date: 2025-01-27 09:54+0200\n"

  14. "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"

  15. "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"

  16. "Language: bg\n"

  17. "Language-Team: bg <LL@li.org>\n"

  18. "Plural-Forms: nplurals=2; plural=(n != 1);\n"

  19. "MIME-Version: 1.0\n"

  20. "Content-Type: text/plain; charset=utf-8\n"

  21. "Content-Transfer-Encoding: 8bit\n"

  22. "Generated-By: Babel 2.16.0\n"

  23. 

  24. #: ../../../CHANGELOG.md:1

  25. msgid "2025-01-27"

  26. msgstr ""

  27. 

  28. #: ../../../CHANGELOG.md:3

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

  30. msgstr ""

  31. 

  32. #: ../../../CHANGELOG.md:5

  33. 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 definining `redis_*` or `keydb_*` variables will need to update their configuration to use `valkey_*` variables instead."

  34. msgstr ""

  35. 

  36. #: ../../../CHANGELOG.md:7

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

  38. msgstr ""

  39. 

  40. #: ../../../CHANGELOG.md:9

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

  42. msgstr ""

  43. 

  44. #: ../../../CHANGELOG.md:10

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

  46. msgstr ""

  47. 

  48. #: ../../../CHANGELOG.md:11

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

  50. msgstr ""

  51. 

  52. #: ../../../CHANGELOG.md:13

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

  54. msgstr ""

  55. 

  56. #: ../../../CHANGELOG.md:15

  57. msgid "removing Redis and KeyDB support entirely"

  58. msgstr ""

  59. 

  60. #: ../../../CHANGELOG.md:16

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

  62. msgstr ""

  63. 

  64. #: ../../../CHANGELOG.md:18

  65. msgid "To update your configuration:"

  66. msgstr ""

  67. 

  68. #: ../../../CHANGELOG.md:20

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

  70. msgstr ""

  71. 

  72. #: ../../../CHANGELOG.md:21

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

  74. msgstr ""

  75. 

  76. #: ../../../CHANGELOG.md:24

  77. msgid "2025-01-19"

  78. msgstr ""

  79. 

  80. #: ../../../CHANGELOG.md:26

  81. msgid "conduwuit support"

  82. msgstr ""

  83. 

  84. #: ../../../CHANGELOG.md:28

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

  86. msgstr ""

  87. 

  88. #: ../../../CHANGELOG.md:30

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

  90. msgstr ""

  91. 

  92. #: ../../../CHANGELOG.md:32

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

  94. msgstr ""

  95. 

  96. #: ../../../CHANGELOG.md:34

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

  98. msgstr ""

  99. 

  100. #: ../../../CHANGELOG.md:36

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

  102. msgstr ""

  103. 

  104. #: ../../../CHANGELOG.md:39

  105. msgid "2025-01-14"

  106. msgstr ""

  107. 

  108. #: ../../../CHANGELOG.md:41

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

  110. msgstr ""

  111. 

  112. #: ../../../CHANGELOG.md:43

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

  114. msgstr ""

  115. 

  116. #: ../../../CHANGELOG.md:45

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

  118. msgstr ""

  119. 

  120. #: ../../../CHANGELOG.md:47

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

  122. msgstr ""

  123. 

  124. #: ../../../CHANGELOG.md:49

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

  126. msgstr ""

  127. 

  128. #: ../../../CHANGELOG.md:51

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

  130. msgstr ""

  131. 

  132. #: ../../../CHANGELOG.md:59

  133. msgid "2024-11-26"

  134. msgstr ""

  135. 

  136. #: ../../../CHANGELOG.md:61

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

  138. msgstr ""

  139. 

  140. #: ../../../CHANGELOG.md:63

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

  142. msgstr ""

  143. 

  144. #: ../../../CHANGELOG.md:65

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

  146. msgstr ""

  147. 

  148. #: ../../../CHANGELOG.md:67

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

  150. msgstr ""

  151. 

  152. #: ../../../CHANGELOG.md:69

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

  154. msgstr ""

  155. 

  156. #: ../../../CHANGELOG.md:71

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

  158. msgstr ""

  159. 

  160. #: ../../../CHANGELOG.md:73

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

  162. msgstr ""

  163. 

  164. #: ../../../CHANGELOG.md:75

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

  166. msgstr ""

  167. 

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

  169. msgid "2024-11-23"

  170. msgstr ""

  171. 

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

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

  174. msgstr ""

  175. 

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

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

  178. msgstr ""

  179. 

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

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

  182. msgstr ""

  183. 

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

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

  186. msgstr ""

  187. 

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

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

  190. msgstr ""

  191. 

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

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

  194. msgstr ""

  195. 

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

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

  198. msgstr ""

  199. 

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

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

  202. msgstr ""

  203. 

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

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

  206. msgstr ""

  207. 

  208. #: ../../../CHANGELOG.md:107

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

  210. msgstr ""

  211. 

  212. #: ../../../CHANGELOG.md:117

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

  214. msgstr ""

  215. 

  216. #: ../../../CHANGELOG.md:120

  217. msgid "2024-11-14"

  218. msgstr ""

  219. 

  220. #: ../../../CHANGELOG.md:122

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

  222. msgstr ""

  223. 

  224. #: ../../../CHANGELOG.md:124

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

  226. msgstr ""

  227. 

  228. #: ../../../CHANGELOG.md:126

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

  230. msgstr ""

  231. 

  232. #: ../../../CHANGELOG.md:128

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

  234. msgstr ""

  235. 

  236. #: ../../../CHANGELOG.md:130

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

  238. msgstr ""

  239. 

  240. #: ../../../CHANGELOG.md:132

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

  242. msgstr ""

  243. 

  244. #: ../../../CHANGELOG.md:134

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

  246. msgstr ""

  247. 

  248. #: ../../../CHANGELOG.md:135

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

  250. msgstr ""

  251. 

  252. #: ../../../CHANGELOG.md:136

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

  254. msgstr ""

  255. 

  256. #: ../../../CHANGELOG.md:138

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

  258. msgstr ""

  259. 

  260. #: ../../../CHANGELOG.md:140

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

  262. msgstr ""

  263. 

  264. #: ../../../CHANGELOG.md:142

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

  266. msgstr ""

  267. 

  268. #: ../../../CHANGELOG.md:144

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

  270. msgstr ""

  271. 

  272. #: ../../../CHANGELOG.md:146

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

  274. msgstr ""

  275. 

  276. #: ../../../CHANGELOG.md:148

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

  278. msgstr ""

  279. 

  280. #: ../../../CHANGELOG.md:159

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

  282. msgstr ""

  283. 

  284. #: ../../../CHANGELOG.md:162

  285. msgid "2024-11-08"

  286. msgstr ""

  287. 

  288. #: ../../../CHANGELOG.md:164

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

  290. msgstr ""

  291. 

  292. #: ../../../CHANGELOG.md:166

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

  294. msgstr ""

  295. 

  296. #: ../../../CHANGELOG.md:168

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

  298. msgstr ""

  299. 

  300. #: ../../../CHANGELOG.md:170

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

  302. msgstr ""

  303. 

  304. #: ../../../CHANGELOG.md:173

  305. msgid "2024-10-28"

  306. msgstr ""

  307. 

  308. #: ../../../CHANGELOG.md:175

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

  310. msgstr ""

  311. 

  312. #: ../../../CHANGELOG.md:177

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

  314. msgstr ""

  315. 

  316. #: ../../../CHANGELOG.md:179

  317. msgid "2024-10-19"

  318. msgstr ""

  319. 

  320. #: ../../../CHANGELOG.md:181

  321. msgid "Support for Matrix Authentication Service"

  322. msgstr ""

  323. 

  324. #: ../../../CHANGELOG.md:183

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

  326. msgstr ""

  327. 

  328. #: ../../../CHANGELOG.md:185

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

  330. msgstr ""

  331. 

  332. #: ../../../CHANGELOG.md:187

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

  334. msgstr ""

  335. 

  336. #: ../../../CHANGELOG.md:189

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

  338. msgstr ""

  339. 

  340. #: ../../../CHANGELOG.md:192

  341. msgid "2024-09-27"

  342. msgstr ""

  343. 

  344. #: ../../../CHANGELOG.md:194

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

  346. msgstr ""

  347. 

  348. #: ../../../CHANGELOG.md:196

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

  350. msgstr ""

  351. 

  352. #: ../../../CHANGELOG.md:198

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

  354. msgstr ""

  355. 

  356. #: ../../../CHANGELOG.md:200

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

  358. msgstr ""

  359. 

  360. #: ../../../CHANGELOG.md:202

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

  362. msgstr ""

  363. 

  364. #: ../../../CHANGELOG.md:203

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

  366. msgstr ""

  367. 

  368. #: ../../../CHANGELOG.md:205

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

  370. msgstr ""

  371. 

  372. #: ../../../CHANGELOG.md:208

  373. msgid "2024-09-12"

  374. msgstr ""

  375. 

  376. #: ../../../CHANGELOG.md:210

  377. msgid "Support for baibot"

  378. msgstr ""

  379. 

  380. #: ../../../CHANGELOG.md:212

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

  382. msgstr ""

  383. 

  384. #: ../../../CHANGELOG.md:214

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

  386. msgstr ""

  387. 

  388. #: ../../../CHANGELOG.md:216

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

  390. msgstr ""

  391. 

  392. #: ../../../CHANGELOG.md:218

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

  394. msgstr ""

  395. 

  396. #: ../../../CHANGELOG.md:220

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

  398. msgstr ""

  399. 

  400. #: ../../../CHANGELOG.md:222

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

  402. msgstr ""

  403. 

  404. #: ../../../CHANGELOG.md:224

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

  406. msgstr ""

  407. 

  408. #: ../../../CHANGELOG.md:226

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

  410. msgstr ""

  411. 

  412. #: ../../../CHANGELOG.md:228

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

  414. msgstr ""

  415. 

  416. #: ../../../CHANGELOG.md:241

  417. msgid "2024-08-17"

  418. msgstr ""

  419. 

  420. #: ../../../CHANGELOG.md:243

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

  422. msgstr ""

  423. 

  424. #: ../../../CHANGELOG.md:245

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

  426. msgstr ""

  427. 

  428. #: ../../../CHANGELOG.md:247

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

  430. msgstr ""

  431. 

  432. #: ../../../CHANGELOG.md:249

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

  434. msgstr ""

  435. 

  436. #: ../../../CHANGELOG.md:251

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

  438. msgstr ""

  439. 

  440. #: ../../../CHANGELOG.md:253

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

  442. msgstr ""

  443. 

  444. #: ../../../CHANGELOG.md:259

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

  446. msgstr ""

  447. 

  448. #: ../../../CHANGELOG.md:261

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

  450. msgstr ""

  451. 

  452. #: ../../../CHANGELOG.md:264

  453. msgid "2024-08-15"

  454. msgstr ""

  455. 

  456. #: ../../../CHANGELOG.md:266

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

  458. msgstr ""

  459. 

  460. #: ../../../CHANGELOG.md:268

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

  462. msgstr ""

  463. 

  464. #: ../../../CHANGELOG.md:270

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

  466. msgstr ""

  467. 

  468. #: ../../../CHANGELOG.md:272

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

  470. msgstr ""

  471. 

  472. #: ../../../CHANGELOG.md:274

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

  474. msgstr ""

  475. 

  476. #: ../../../CHANGELOG.md:277

  477. msgid "2024-08-08"

  478. msgstr ""

  479. 

  480. #: ../../../CHANGELOG.md:279

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

  482. msgstr ""

  483. 

  484. #: ../../../CHANGELOG.md:281

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

  486. msgstr ""

  487. 

  488. #: ../../../CHANGELOG.md:283

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

  490. msgstr ""

  491. 

  492. #: ../../../CHANGELOG.md:285

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

  494. msgstr ""

  495. 

  496. #: ../../../CHANGELOG.md:291

  497. msgid "2024-07-25"

  498. msgstr ""

  499. 

  500. #: ../../../CHANGELOG.md:293

  501. msgid "synapse-usage-exporter support"

  502. msgstr ""

  503. 

  504. #: ../../../CHANGELOG.md:295

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

  506. msgstr ""

  507. 

  508. #: ../../../CHANGELOG.md:297

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

  510. msgstr ""

  511. 

  512. #: ../../../CHANGELOG.md:300

  513. msgid "2024-07-06"

  514. msgstr ""

  515. 

  516. #: ../../../CHANGELOG.md:302

  517. msgid "matrix-alertmanager-receiver support"

  518. msgstr ""

  519. 

  520. #: ../../../CHANGELOG.md:304

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

  522. msgstr ""

  523. 

  524. #: ../../../CHANGELOG.md:306

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

  526. msgstr ""

  527. 

  528. #: ../../../CHANGELOG.md:308

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

  530. msgstr ""

  531. 

  532. #: ../../../CHANGELOG.md:310

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

  534. msgstr ""

  535. 

  536. #: ../../../CHANGELOG.md:312

  537. msgid "Traefik v3"

  538. msgstr ""

  539. 

  540. #: ../../../CHANGELOG.md:314

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

  542. msgstr ""

  543. 

  544. #: ../../../CHANGELOG.md:316

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

  546. msgstr ""

  547. 

  548. #: ../../../CHANGELOG.md:318

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

  550. msgstr ""

  551. 

  552. #: ../../../CHANGELOG.md:320

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

  554. msgstr ""

  555. 

  556. #: ../../../CHANGELOG.md:322

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

  558. msgstr ""

  559. 

  560. #: ../../../CHANGELOG.md:324

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

  562. msgstr ""

  563. 

  564. #: ../../../CHANGELOG.md:326

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

  566. msgstr ""

  567. 

  568. #: ../../../CHANGELOG.md:328

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

  570. msgstr ""

  571. 

  572. #: ../../../CHANGELOG.md:330

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

  574. msgstr ""

  575. 

  576. #: ../../../CHANGELOG.md:332

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

  578. msgstr ""

  579. 

  580. #: ../../../CHANGELOG.md:334

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

  582. msgstr ""

  583. 

  584. #: ../../../CHANGELOG.md:336

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

  586. msgstr ""

  587. 

  588. #: ../../../CHANGELOG.md:338

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

  590. msgstr ""

  591. 

  592. #: ../../../CHANGELOG.md:352

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

  594. msgstr ""

  595. 

  596. #: ../../../CHANGELOG.md:365

  597. msgid "2024-07-01"

  598. msgstr ""

  599. 

  600. #: ../../../CHANGELOG.md:367

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

  602. msgstr ""

  603. 

  604. #: ../../../CHANGELOG.md:369

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

  606. msgstr ""

  607. 

  608. #: ../../../CHANGELOG.md:371

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

  610. msgstr ""

  611. 

  612. #: ../../../CHANGELOG.md:373

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

  614. msgstr ""

  615. 

  616. #: ../../../CHANGELOG.md:381

  617. msgid "2024-06-25"

  618. msgstr ""

  619. 

  620. #: ../../../CHANGELOG.md:383

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

  622. msgstr ""

  623. 

  624. #: ../../../CHANGELOG.md:385

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

  626. msgstr ""

  627. 

  628. #: ../../../CHANGELOG.md:387

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

  630. msgstr ""

  631. 

  632. #: ../../../CHANGELOG.md:389

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

  634. msgstr ""

  635. 

  636. #: ../../../CHANGELOG.md:391

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

  638. msgstr ""

  639. 

  640. #: ../../../CHANGELOG.md:393

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

  642. msgstr ""

  643. 

  644. #: ../../../CHANGELOG.md:395

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

  646. msgstr ""

  647. 

  648. #: ../../../CHANGELOG.md:397

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

  650. msgstr ""

  651. 

  652. #: ../../../CHANGELOG.md:400

  653. msgid "2024-06-22"

  654. msgstr ""

  655. 

  656. #: ../../../CHANGELOG.md:402

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

  658. msgstr ""

  659. 

  660. #: ../../../CHANGELOG.md:404

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

  662. msgstr ""

  663. 

  664. #: ../../../CHANGELOG.md:406

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

  666. msgstr ""

  667. 

  668. #: ../../../CHANGELOG.md:408

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

  670. msgstr ""

  671. 

  672. #: ../../../CHANGELOG.md:411

  673. msgid "2024-06-03"

  674. msgstr ""

  675. 

  676. #: ../../../CHANGELOG.md:413

  677. msgid "WeChat bridging support"

  678. msgstr ""

  679. 

  680. #: ../../../CHANGELOG.md:415

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

  682. msgstr ""

  683. 

  684. #: ../../../CHANGELOG.md:417

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

  686. msgstr ""

  687. 

  688. #: ../../../CHANGELOG.md:420

  689. msgid "2024-03-26"

  690. msgstr ""

  691. 

  692. #: ../../../CHANGELOG.md:422

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

  694. msgstr ""

  695. 

  696. #: ../../../CHANGELOG.md:424

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

  698. msgstr ""

  699. 

  700. #: ../../../CHANGELOG.md:426

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

  702. msgstr ""

  703. 

  704. #: ../../../CHANGELOG.md:428

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

  706. msgstr ""

  707. 

  708. #: ../../../CHANGELOG.md:430

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

  710. msgstr ""

  711. 

  712. #: ../../../CHANGELOG.md:432

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

  714. msgstr ""

  715. 

  716. #: ../../../CHANGELOG.md:434

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

  718. msgstr ""

  719. 

  720. #: ../../../CHANGELOG.md:445

  721. msgid "2024-03-24"

  722. msgstr ""

  723. 

  724. #: ../../../CHANGELOG.md:447

  725. msgid "Initial work on IPv6 support"

  726. msgstr ""

  727. 

  728. #: ../../../CHANGELOG.md:449

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

  730. msgstr ""

  731. 

  732. #: ../../../CHANGELOG.md:451

  733. msgid "It should be noted that:"

  734. msgstr ""

  735. 

  736. #: ../../../CHANGELOG.md:453

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

  738. msgstr ""

  739. 

  740. #: ../../../CHANGELOG.md:454

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

  742. msgstr ""

  743. 

  744. #: ../../../CHANGELOG.md:455

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

  746. msgstr ""

  747. 

  748. #: ../../../CHANGELOG.md:457

  749. msgid "Pantalaimon support"

  750. msgstr ""

  751. 

  752. #: ../../../CHANGELOG.md:459

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

  754. msgstr ""

  755. 

  756. #: ../../../CHANGELOG.md:461

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

  758. msgstr ""

  759. 

  760. #: ../../../CHANGELOG.md:464

  761. msgid "2024-03-05"

  762. msgstr ""

  763. 

  764. #: ../../../CHANGELOG.md:466

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

  766. msgstr ""

  767. 

  768. #: ../../../CHANGELOG.md:468

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

  770. msgstr ""

  771. 

  772. #: ../../../CHANGELOG.md:470

  773. msgid "This is an alternative to [running Draupnir in bot mode](./docs/configuring-playbook-bot-draupnir.md), which is still supported by the playbook."

  774. msgstr ""

  775. 

  776. #: ../../../CHANGELOG.md:472

  777. msgid "The documentation page for [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) contains more information on how to install it."

  778. msgstr ""

  779. 

  780. #: ../../../CHANGELOG.md:475

  781. msgid "2024-02-19"

  782. msgstr ""

  783. 

  784. #: ../../../CHANGELOG.md:477

  785. msgid "Support for bridging to Facebook/Messenger via the new mautrix-meta bridge"

  786. msgstr ""

  787. 

  788. #: ../../../CHANGELOG.md:479

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

  790. msgstr ""

  791. 

  792. #: ../../../CHANGELOG.md:481

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

  794. msgstr ""

  795. 

  796. #: ../../../CHANGELOG.md:483

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

  798. msgstr ""

  799. 

  800. #: ../../../CHANGELOG.md:485

  801. msgid "[Setting up Instagram bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)"

  802. msgstr ""

  803. 

  804. #: ../../../CHANGELOG.md:487

  805. msgid "[Setting up Messenger bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-messenger.md)"

  806. msgstr ""

  807. 

  808. #: ../../../CHANGELOG.md:489

  809. msgid "The documentation pages contain more information on how to migrate."

  810. msgstr ""

  811. 

  812. #: ../../../CHANGELOG.md:492

  813. msgid "2024-02-14"

  814. msgstr ""

  815. 

  816. #: ../../../CHANGELOG.md:494

  817. msgid "Much larger Synapse caches and cache auto-tuning enabled by default"

  818. msgstr ""

  819. 

  820. #: ../../../CHANGELOG.md:496

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

  822. msgstr ""

  823. 

  824. #: ../../../CHANGELOG.md:498

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

  826. msgstr ""

  827. 

  828. #: ../../../CHANGELOG.md:500

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

  830. msgstr ""

  831. 

  832. #: ../../../CHANGELOG.md:502

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

  834. msgstr ""

  835. 

  836. #: ../../../CHANGELOG.md:503

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

  838. msgstr ""

  839. 

  840. #: ../../../CHANGELOG.md:504

  841. msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` — defaults to `30s`"

  842. msgstr ""

  843. 

  844. #: ../../../CHANGELOG.md:506

  845. msgid "These values should be good defaults for most servers, but may change over time as we experiment further."

  846. msgstr ""

  847. 

  848. #: ../../../CHANGELOG.md:508

  849. msgid "Refer to our new [Tuning caches and cache autotuning](docs/maintenance-synapse.md#tuning-caches-and-cache-autotuning) documentation section for more details."

  850. msgstr ""

  851. 

  852. #: ../../../CHANGELOG.md:511

  853. msgid "2024-01-31"

  854. msgstr ""

  855. 

  856. #: ../../../CHANGELOG.md:513

  857. msgid "(Backward-compatibility break) Minor changes necessary for some people serving a static website at the base domain"

  858. msgstr ""

  859. 

  860. #: ../../../CHANGELOG.md:515

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

  862. msgstr ""

  863. 

  864. #: ../../../CHANGELOG.md:517

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

  866. msgstr ""

  867. 

  868. #: ../../../CHANGELOG.md:519

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

  870. msgstr ""

  871. 

  872. #: ../../../CHANGELOG.md:522

  873. msgid "2024-01-20"

  874. msgstr ""

  875. 

  876. #: ../../../CHANGELOG.md:524

  877. msgid "Support for more efficient (specialized) Synapse workers"

  878. msgstr ""

  879. 

  880. #: ../../../CHANGELOG.md:526

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

  882. msgstr ""

  883. 

  884. #: ../../../CHANGELOG.md:528

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

  886. msgstr ""

  887. 

  888. #: ../../../CHANGELOG.md:530

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

  890. msgstr ""

  891. 

  892. #: ../../../CHANGELOG.md:532

  893. msgid "To get started, refer to our [Specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) documentation section."

  894. msgstr ""

  895. 

  896. #: ../../../CHANGELOG.md:535

  897. msgid "2024-01-17"

  898. msgstr ""

  899. 

  900. #: ../../../CHANGELOG.md:537

  901. msgid "Switching to Element's AGPLv3-licensed Synapse release"

  902. msgstr ""

  903. 

  904. #: ../../../CHANGELOG.md:539

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

  906. msgstr ""

  907. 

  908. #: ../../../CHANGELOG.md:541

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

  910. msgstr ""

  911. 

  912. #: ../../../CHANGELOG.md:542

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

  914. msgstr ""

  915. 

  916. #: ../../../CHANGELOG.md:544

  917. msgid "You can also learn more in [this post](https://matrix.org/blog/2023/11/06/future-of-synapse-dendrite/) by the Matrix Foundation."

  918. msgstr ""

  919. 

  920. #: ../../../CHANGELOG.md:546

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

  922. msgstr ""

  923. 

  924. #: ../../../CHANGELOG.md:548

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

  926. msgstr ""

  927. 

  928. #: ../../../CHANGELOG.md:550

  929. msgid "**What does this mean to you?**"

  930. msgstr ""

  931. 

  932. #: ../../../CHANGELOG.md:552

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

  934. msgstr ""

  935. 

  936. #: ../../../CHANGELOG.md:554

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

  938. msgstr ""

  939. 

  940. #: ../../../CHANGELOG.md:556

  941. 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!"

  942. msgstr ""

  943. 

  944. #: ../../../CHANGELOG.md:558

  945. 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 intruducing a new Ansible variable. You can do it like this:"

  946. msgstr ""

  947. 

  948. #: ../../../CHANGELOG.md:570

  949. msgid "Notes:"

  950. msgstr ""

  951. 

  952. #: ../../../CHANGELOG.md:572

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

  954. msgstr ""

  955. 

  956. #: ../../../CHANGELOG.md:574

  957. msgid "running an outdated homeserver exposes you to security issues and incompatibilities. Only consider doing this as a short-term solution."

  958. msgstr ""

  959. 

  960. #: ../../../CHANGELOG.md:576

  961. msgid "2024-01-16"

  962. msgstr ""

  963. 

  964. #: ../../../CHANGELOG.md:578

  965. msgid "`Draupnir` has been relicensed to AFL-3.0"

  966. msgstr ""

  967. 

  968. #: ../../../CHANGELOG.md:580

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

  970. msgstr ""

  971. 

  972. #: ../../../CHANGELOG.md:582

  973. msgid "2024-01-15"

  974. msgstr ""

  975. 

  976. #: ../../../CHANGELOG.md:584

  977. msgid "Goodbye, `matrix-nginx-proxy` 🪦"

  978. msgstr ""

  979. 

  980. #: ../../../CHANGELOG.md:586

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

  982. msgstr ""

  983. 

  984. #: ../../../CHANGELOG.md:588

  985. msgid "Backstory on `matrix-nginx-proxy`"

  986. msgstr ""

  987. 

  988. #: ../../../CHANGELOG.md:590

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

  990. msgstr ""

  991. 

  992. #: ../../../CHANGELOG.md:592

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

  994. msgstr ""

  995. 

  996. #: ../../../CHANGELOG.md:594

  997. msgid "To us, `matrix-nginx-proxy` was:"

  998. msgstr ""

  999. 

  1000. #: ../../../CHANGELOG.md:596

  1001. msgid "an [nginx](https://nginx.org/)-based reverse-proxy"

  1002. msgstr ""

  1003. 

  1004. #: ../../../CHANGELOG.md:597

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

  1006. msgstr ""

  1007. 

  1008. #: ../../../CHANGELOG.md:598

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

  1010. msgstr ""

  1011. 

  1012. #: ../../../CHANGELOG.md:599

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

  1014. msgstr ""

  1015. 

  1016. #: ../../../CHANGELOG.md:600

  1017. msgid "a webserver for serving the `/.well-known/matrix` static files (generated by the `matrix-base` role until now)"

  1018. msgstr ""

  1019. 

  1020. #: ../../../CHANGELOG.md:601

  1021. msgid "a webserver [serving your base domain](./docs/configuring-playbook-base-domain-serving.md) (and also generating the `index.html` page for it)"

  1022. msgstr ""

  1023. 

  1024. #: ../../../CHANGELOG.md:602

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

  1026. msgstr ""

  1027. 

  1028. #: ../../../CHANGELOG.md:604

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

  1030. msgstr ""

  1031. 

  1032. #: ../../../CHANGELOG.md:606

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

  1034. msgstr ""

  1035. 

  1036. #: ../../../CHANGELOG.md:608

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

  1038. msgstr ""

  1039. 

  1040. #: ../../../CHANGELOG.md:610

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

  1042. msgstr ""

  1043. 

  1044. #: ../../../CHANGELOG.md:612

  1045. msgid "Going Traefik-native and cutting out all middlemen"

  1046. msgstr ""

  1047. 

  1048. #: ../../../CHANGELOG.md:614

  1049. msgid "In our new setup, you'll see the bare minimum number of reverse-proxies."

  1050. msgstr ""

  1051. 

  1052. #: ../../../CHANGELOG.md:616

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

  1054. msgstr ""

  1055. 

  1056. #: ../../../CHANGELOG.md:618

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

  1058. msgstr ""

  1059. 

  1060. #: ../../../CHANGELOG.md:620

  1061. msgid "Traefik now has an extra job"

  1062. msgstr ""

  1063. 

  1064. #: ../../../CHANGELOG.md:622

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

  1066. msgstr ""

  1067. 

  1068. #: ../../../CHANGELOG.md:624

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

  1070. msgstr ""

  1071. 

  1072. #: ../../../CHANGELOG.md:626

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

  1074. msgstr ""

  1075. 

  1076. #: ../../../CHANGELOG.md:628

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

  1078. msgstr ""

  1079. 

  1080. #: ../../../CHANGELOG.md:630

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

  1082. msgstr ""

  1083. 

  1084. #: ../../../CHANGELOG.md:632

  1085. msgid "Traefik serving this second purpose has a few downsides:"

  1086. msgstr ""

  1087. 

  1088. #: ../../../CHANGELOG.md:634

  1089. msgid "Traefik becomes a runtime dependency for all homeserver-dependant container services"

  1090. msgstr ""

  1091. 

  1092. #: ../../../CHANGELOG.md:635

  1093. msgid "all homeserver-dependant services now need to be connected to the `traefik` container network, even if they don't need public internet exposure"

  1094. msgstr ""

  1095. 

  1096. #: ../../../CHANGELOG.md:637

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

  1098. msgstr ""

  1099. 

  1100. #: ../../../CHANGELOG.md:639

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

  1102. msgstr ""

  1103. 

  1104. #: ../../../CHANGELOG.md:641

  1105. msgid "**People runnning 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."

  1106. msgstr ""

  1107. 

  1108. #: ../../../CHANGELOG.md:643

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

  1110. msgstr ""

  1111. 

  1112. #: ../../../CHANGELOG.md:645

  1113. msgid "People managing their own Traefik instance need to do minor changes"

  1114. msgstr ""

  1115. 

  1116. #: ../../../CHANGELOG.md:647

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

  1118. msgstr ""

  1119. 

  1120. #: ../../../CHANGELOG.md:649

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

  1122. msgstr ""

  1123. 

  1124. #: ../../../CHANGELOG.md:651

  1125. msgid "People fronting Traefik with another reverse proxy need to do minor changes"

  1126. msgstr ""

  1127. 

  1128. #: ../../../CHANGELOG.md:653

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

  1130. msgstr ""

  1131. 

  1132. #: ../../../CHANGELOG.md:655

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

  1134. msgstr ""

  1135. 

  1136. #: ../../../CHANGELOG.md:657

  1137. msgid "Supported reverse proxy types are now fewer"

  1138. msgstr ""

  1139. 

  1140. #: ../../../CHANGELOG.md:659

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

  1142. msgstr ""

  1143. 

  1144. #: ../../../CHANGELOG.md:661

  1145. msgid "Previously, we allowed you to set `matrix_playbook_reverse_proxy_type` to 7 different values to accommodate various reverse-proxy setups."

  1146. msgstr ""

  1147. 

  1148. #: ../../../CHANGELOG.md:663

  1149. msgid "The complexity of this is too high, so we only support 3 values right now:"

  1150. msgstr ""

  1151. 

  1152. #: ../../../CHANGELOG.md:665

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

  1154. msgstr ""

  1155. 

  1156. #: ../../../CHANGELOG.md:666

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

  1158. msgstr ""

  1159. 

  1160. #: ../../../CHANGELOG.md:667

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

  1162. msgstr ""

  1163. 

  1164. #: ../../../CHANGELOG.md:669

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

  1166. msgstr ""

  1167. 

  1168. #: ../../../CHANGELOG.md:671

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

  1170. msgstr ""

  1171. 

  1172. #: ../../../CHANGELOG.md:673

  1173. msgid "If you were using these values as a way to stay away from Traefik, you now have 2 options:"

  1174. msgstr ""

  1175. 

  1176. #: ../../../CHANGELOG.md:675

  1177. msgid "(recommended) [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)"

  1178. msgstr ""

  1179. 

  1180. #: ../../../CHANGELOG.md:676

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

  1182. msgstr ""

  1183. 

  1184. #: ../../../CHANGELOG.md:678

  1185. msgid "Container networking changes"

  1186. msgstr ""

  1187. 

  1188. #: ../../../CHANGELOG.md:680

  1189. msgid "Now that `matrix-nginx-proxy` is not in the mix, it became easier to clear out some other long-overdue technical debt."

  1190. msgstr ""

  1191. 

  1192. #: ../../../CHANGELOG.md:682

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

  1194. msgstr ""

  1195. 

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

  1197. msgid "Moving components (especially the database) into other container networks was difficult — it required changes to many other components to ensure correct connectivity."

  1198. msgstr ""

  1199. 

  1200. #: ../../../CHANGELOG.md:686

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

  1202. msgstr ""

  1203. 

  1204. #: ../../../CHANGELOG.md:688

  1205. msgid "Carrying out these container networking changes necessitated modifying many components, so **we're hoping not too many bugs were introduced in the process**."

  1206. msgstr ""

  1207. 

  1208. #: ../../../CHANGELOG.md:690

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

  1210. msgstr ""

  1211. 

  1212. #: ../../../CHANGELOG.md:692

  1213. msgid "Metrics exposure changes"

  1214. msgstr ""

  1215. 

  1216. #: ../../../CHANGELOG.md:694

  1217. msgid "This section is for people who are exposing monitoring metrics publicly, to be consumed by an external Prometheus server."

  1218. msgstr ""

  1219. 

  1220. #: ../../../CHANGELOG.md:696

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

  1222. msgstr ""

  1223. 

  1224. #: ../../../CHANGELOG.md:698

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

  1226. msgstr ""

  1227. 

  1228. #: ../../../CHANGELOG.md:700

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

  1230. msgstr ""

  1231. 

  1232. #: ../../../CHANGELOG.md:702

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

  1234. msgstr ""

  1235. 

  1236. #: ../../../CHANGELOG.md:704

  1237. msgid "Matrix static files"

  1238. msgstr ""

  1239. 

  1240. #: ../../../CHANGELOG.md:706

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

  1242. msgstr ""

  1243. 

  1244. #: ../../../CHANGELOG.md:708

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

  1246. msgstr ""

  1247. 

  1248. #: ../../../CHANGELOG.md:710

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

  1250. msgstr ""

  1251. 

  1252. #: ../../../CHANGELOG.md:712

  1253. msgid "A note on performance"

  1254. msgstr ""

  1255. 

  1256. #: ../../../CHANGELOG.md:714

  1257. msgid "Some of you have been voicing their concerns (for a long time) about Traefik being too slow and nginx being better."

  1258. msgstr ""

  1259. 

  1260. #: ../../../CHANGELOG.md:716

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

  1262. msgstr ""

  1263. 

  1264. #: ../../../CHANGELOG.md:718

  1265. msgid "We believe that using Traefik provides way too many benefits to worry about this minor performance impairment."

  1266. msgstr ""

  1267. 

  1268. #: ../../../CHANGELOG.md:720

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

  1270. msgstr ""

  1271. 

  1272. #: ../../../CHANGELOG.md:722

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

  1274. msgstr ""

  1275. 

  1276. #: ../../../CHANGELOG.md:724

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

  1278. msgstr ""

  1279. 

  1280. #: ../../../CHANGELOG.md:726

  1281. msgid "Migration procedure"

  1282. msgstr ""

  1283. 

  1284. #: ../../../CHANGELOG.md:728

  1285. msgid "The updated playbook will automatically perform some migration tasks for you:"

  1286. msgstr ""

  1287. 

  1288. #: ../../../CHANGELOG.md:730

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

  1290. msgstr ""

  1291. 

  1292. #: ../../../CHANGELOG.md:732

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

  1294. msgstr ""

  1295. 

  1296. #: ../../../CHANGELOG.md:734

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

  1298. msgstr ""

  1299. 

  1300. #: ../../../CHANGELOG.md:736

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

  1302. msgstr ""

  1303. 

  1304. #: ../../../CHANGELOG.md:738

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

  1306. msgstr ""

  1307. 

  1308. #: ../../../CHANGELOG.md:740

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

  1310. msgstr ""

  1311. 

  1312. #: ../../../CHANGELOG.md:742

  1313. msgid "We don't recommend changing these variables and suppressing warnings, unless you know what you're doing."

  1314. msgstr ""

  1315. 

  1316. #: ../../../CHANGELOG.md:744

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

  1318. msgstr ""

  1319. 

  1320. #: ../../../CHANGELOG.md:746

  1321. msgid "Conclusion"

  1322. msgstr ""

  1323. 

  1324. #: ../../../CHANGELOG.md:748

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

  1326. msgstr ""

  1327. 

  1328. #: ../../../CHANGELOG.md:750

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

  1330. msgstr ""

  1331. 

  1332. #: ../../../CHANGELOG.md:753

  1333. msgid "2024-01-14"

  1334. msgstr ""

  1335. 

  1336. #: ../../../CHANGELOG.md:755

  1337. msgid "(Backward Compatibility) Configuration changes required for people fronting the integrated reverse-proxy webserver with another reverse-proxy"

  1338. msgstr ""

  1339. 

  1340. #: ../../../CHANGELOG.md:757

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

  1342. msgstr ""

  1343. 

  1344. #: ../../../CHANGELOG.md:759

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

  1346. msgstr ""

  1347. 

  1348. #: ../../../CHANGELOG.md:761

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

  1350. msgstr ""

  1351. 

  1352. #: ../../../CHANGELOG.md:763

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

  1354. msgstr ""

  1355. 

  1356. #: ../../../CHANGELOG.md:765

  1357. msgid "Adapt your configuration as seen below:"

  1358. msgstr ""

  1359. 

  1360. #: ../../../CHANGELOG.md:798

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

  1362. msgstr ""

  1363. 

  1364. #: ../../../CHANGELOG.md:801

  1365. msgid "2024-01-13"

  1366. msgstr ""

  1367. 

  1368. #: ../../../CHANGELOG.md:803

  1369. msgid "matrix-reminder-bot update with more secure (backward-incompatible) default settings"

  1370. msgstr ""

  1371. 

  1372. #: ../../../CHANGELOG.md:805

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

  1374. msgstr ""

  1375. 

  1376. #: ../../../CHANGELOG.md:807

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

  1378. msgstr ""

  1379. 

  1380. #: ../../../CHANGELOG.md:809

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

  1382. msgstr ""

  1383. 

  1384. #: ../../../CHANGELOG.md:811

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

  1386. msgstr ""

  1387. 

  1388. #: ../../../CHANGELOG.md:813

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

  1390. msgstr ""

  1391. 

  1392. #: ../../../CHANGELOG.md:815

  1393. msgid "If you need **to undo or tweak these security improvements**, you can change your `vars.yml` file to:"

  1394. msgstr ""

  1395. 

  1396. #: ../../../CHANGELOG.md:817

  1397. msgid "disable the allowlist (`matrix_bot_matrix_reminder_bot_allowlist_enabled: false`), making the bot allow usage by anyone, anywhere"

  1398. msgstr ""

  1399. 

  1400. #: ../../../CHANGELOG.md:819

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

  1402. msgstr ""

  1403. 

  1404. #: ../../../CHANGELOG.md:821

  1405. msgid "override the default allowlist (in the `group_vars/matrix_servers` file) by redefining `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`"

  1406. msgstr ""

  1407. 

  1408. #: ../../../CHANGELOG.md:824

  1409. msgid "2024-01-05"

  1410. msgstr ""

  1411. 

  1412. #: ../../../CHANGELOG.md:826

  1413. msgid "matrix-mailer has been replaced by the exim-relay external role"

  1414. msgstr ""

  1415. 

  1416. #: ../../../CHANGELOG.md:828 ../../../CHANGELOG.md:1468

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

  1418. msgstr ""

  1419. 

  1420. #: ../../../CHANGELOG.md:830

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

  1422. msgstr ""

  1423. 

  1424. #: ../../../CHANGELOG.md:832

  1425. msgid "To migrate:"

  1426. msgstr ""

  1427. 

  1428. #: ../../../CHANGELOG.md:834

  1429. msgid "pull the playbook changes, as usual"

  1430. msgstr ""

  1431. 

  1432. #: ../../../CHANGELOG.md:835

  1433. msgid "update your roles (run `just roles` or `make roles`)"

  1434. msgstr ""

  1435. 

  1436. #: ../../../CHANGELOG.md:836

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

  1438. msgstr ""

  1439. 

  1440. #: ../../../CHANGELOG.md:837

  1441. msgid "re-run the playbook (`install-all` or `setup-all`)"

  1442. msgstr ""

  1443. 

  1444. #: ../../../CHANGELOG.md:839

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

  1446. msgstr ""

  1447. 

  1448. #: ../../../CHANGELOG.md:842

  1449. msgid "2024-01-02"

  1450. msgstr ""

  1451. 

  1452. #: ../../../CHANGELOG.md:844

  1453. msgid "mautrix-signal now powered by the new Go-based bridge"

  1454. msgstr ""

  1455. 

  1456. #: ../../../CHANGELOG.md:846

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

  1458. msgstr ""

  1459. 

  1460. #: ../../../CHANGELOG.md:848

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

  1462. msgstr ""

  1463. 

  1464. #: ../../../CHANGELOG.md:850

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

  1466. msgstr ""

  1467. 

  1468. #: ../../../CHANGELOG.md:853

  1469. msgid "2023-10-23"

  1470. msgstr ""

  1471. 

  1472. #: ../../../CHANGELOG.md:855

  1473. msgid "Enabling `allow_public_rooms_over_federation` by default for Synapse"

  1474. msgstr ""

  1475. 

  1476. #: ../../../CHANGELOG.md:857

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

  1478. msgstr ""

  1479. 

  1480. #: ../../../CHANGELOG.md:859

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

  1482. msgstr ""

  1483. 

  1484. #: ../../../CHANGELOG.md:861

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

  1486. msgstr ""

  1487. 

  1488. #: ../../../CHANGELOG.md:863

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

  1490. msgstr ""

  1491. 

  1492. #: ../../../CHANGELOG.md:865

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

  1494. msgstr ""

  1495. 

  1496. #: ../../../CHANGELOG.md:867

  1497. msgid "The **historical reasoning** behind this change is as follows:"

  1498. msgstr ""

  1499. 

  1500. #: ../../../CHANGELOG.md:869

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

  1502. msgstr ""

  1503. 

  1504. #: ../../../CHANGELOG.md:871

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

  1506. msgstr ""

  1507. 

  1508. #: ../../../CHANGELOG.md:873

  1509. #, python-format

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

  1511. msgstr ""

  1512. 

  1513. #: ../../../CHANGELOG.md:875

  1514. msgid "Here are **actions you may wish to take** as a result of this change:"

  1515. msgstr ""

  1516. 

  1517. #: ../../../CHANGELOG.md:877

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

  1519. msgstr ""

  1520. 

  1521. #: ../../../CHANGELOG.md:879

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

  1523. msgstr ""

  1524. 

  1525. #: ../../../CHANGELOG.md:881

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

  1527. msgstr ""

  1528. 

  1529. #: ../../../CHANGELOG.md:884

  1530. msgid "2023-10-18"

  1531. msgstr ""

  1532. 

  1533. #: ../../../CHANGELOG.md:886

  1534. msgid "Postgres parameters are automatically tuned now"

  1535. msgstr ""

  1536. 

  1537. #: ../../../CHANGELOG.md:888

  1538. msgid "The playbook has provided some hints about [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) for quite a while now."

  1539. msgstr ""

  1540. 

  1541. #: ../../../CHANGELOG.md:890

  1542. 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/."

  1543. msgstr ""

  1544. 

  1545. #: ../../../CHANGELOG.md:892

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

  1547. msgstr ""

  1548. 

  1549. #: ../../../CHANGELOG.md:894

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

  1551. msgstr ""

  1552. 

  1553. #: ../../../CHANGELOG.md:897

  1554. msgid "2023-08-31"

  1555. msgstr ""

  1556. 

  1557. #: ../../../CHANGELOG.md:899

  1558. msgid "SchildiChat Web support"

  1559. msgstr ""

  1560. 

  1561. #: ../../../CHANGELOG.md:901

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

  1563. msgstr ""

  1564. 

  1565. #: ../../../CHANGELOG.md:903

  1566. msgid "See our [Configuring SchildiChat Web](docs/configuring-playbook-client-schildichat-web.md) documentation to get started."

  1567. msgstr ""

  1568. 

  1569. #: ../../../CHANGELOG.md:906

  1570. msgid "2023-08-23"

  1571. msgstr ""

  1572. 

  1573. #: ../../../CHANGELOG.md:908

  1574. msgid "mautrix-wsproxy support"

  1575. msgstr ""

  1576. 

  1577. #: ../../../CHANGELOG.md:910

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

  1579. msgstr ""

  1580. 

  1581. #: ../../../CHANGELOG.md:912

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

  1583. msgstr ""

  1584. 

  1585. #: ../../../CHANGELOG.md:915

  1586. msgid "2023-07-24"

  1587. msgstr ""

  1588. 

  1589. #: ../../../CHANGELOG.md:917

  1590. msgid "matrix-registration-bot usage changed"

  1591. msgstr ""

  1592. 

  1593. #: ../../../CHANGELOG.md:919

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

  1595. msgstr ""

  1596. 

  1597. #: ../../../CHANGELOG.md:921

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

  1599. msgstr ""

  1600. 

  1601. #: ../../../CHANGELOG.md:923

  1602. msgid "`matrix_bot_matrix_registration_bot_bot_access_token`"

  1603. msgstr ""

  1604. 

  1605. #: ../../../CHANGELOG.md:924

  1606. msgid "`matrix_bot_matrix_registration_bot_api_token`"

  1607. msgstr ""

  1608. 

  1609. #: ../../../CHANGELOG.md:927

  1610. msgid "2023-07-21"

  1611. msgstr ""

  1612. 

  1613. #: ../../../CHANGELOG.md:929

  1614. msgid "mautrix-gmessages support"

  1615. msgstr ""

  1616. 

  1617. #: ../../../CHANGELOG.md:931

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

  1619. msgstr ""

  1620. 

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

  1622. msgid "2023-07-17"

  1623. msgstr ""

  1624. 

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

  1626. msgid "matrix-media-repo support"

  1627. msgstr ""

  1628. 

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

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

  1631. msgstr ""

  1632. 

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

  1634. msgid "To learn more see our [Storing Matrix media files using matrix-media-repo](docs/configuring-playbook-matrix-media-repo.md) documentation page."

  1635. msgstr ""

  1636. 

  1637. #: ../../../CHANGELOG.md:943

  1638. msgid "2023-05-25"

  1639. msgstr ""

  1640. 

  1641. #: ../../../CHANGELOG.md:945

  1642. msgid "Enabling `forget_rooms_on_leave` by default for Synapse"

  1643. msgstr ""

  1644. 

  1645. #: ../../../CHANGELOG.md:947

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

  1647. msgstr ""

  1648. 

  1649. #: ../../../CHANGELOG.md:949

  1650. msgid "The upstream Synapse default is `false` (disabled), so that you must forget rooms manually after leaving."

  1651. msgstr ""

  1652. 

  1653. #: ../../../CHANGELOG.md:951

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

  1655. msgstr ""

  1656. 

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

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

  1659. msgstr ""

  1660. 

  1661. #: ../../../CHANGELOG.md:956

  1662. msgid "2023-04-03"

  1663. msgstr ""

  1664. 

  1665. #: ../../../CHANGELOG.md:958

  1666. msgid "The matrix-jitsi role lives independently now"

  1667. msgstr ""

  1668. 

  1669. #: ../../../CHANGELOG.md:960

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

  1671. msgstr ""

  1672. 

  1673. #: ../../../CHANGELOG.md:962

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

  1675. msgstr ""

  1676. 

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

  1678. msgid "As part of the extraction process of this role out of the Matrix playbook, a few other things improved:"

  1679. msgstr ""

  1680. 

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

  1682. msgid "**native Traefik support** has been added"

  1683. msgstr ""

  1684. 

  1685. #: ../../../CHANGELOG.md:967

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

  1687. msgstr ""

  1688. 

  1689. #: ../../../CHANGELOG.md:969

  1690. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Jitsi or not."

  1691. msgstr ""

  1692. 

  1693. #: ../../../CHANGELOG.md:971

  1694. msgid "If you're making use of Jitsi via this playbook, you will need to update variable references in your `vars.yml` file:"

  1695. msgstr ""

  1696. 

  1697. #: ../../../CHANGELOG.md:973

  1698. msgid "`matrix_jitsi_*_docker_image_` -> `matrix_jitsi_*_container_image_`"

  1699. msgstr ""

  1700. 

  1701. #: ../../../CHANGELOG.md:974

  1702. msgid "`matrix_jitsi_` -> `jitsi_`"

  1703. msgstr ""

  1704. 

  1705. #: ../../../CHANGELOG.md:975 ../../../CHANGELOG.md:1002

  1706. msgid "some other internal variables have changed, but the playbook will tell you about them"

  1707. msgstr ""

  1708. 

  1709. #: ../../../CHANGELOG.md:977

  1710. msgid "2023-03-22"

  1711. msgstr ""

  1712. 

  1713. #: ../../../CHANGELOG.md:979

  1714. msgid "ntfy Web App is disabled by default"

  1715. msgstr ""

  1716. 

  1717. #: ../../../CHANGELOG.md:981

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

  1719. msgstr ""

  1720. 

  1721. #: ../../../CHANGELOG.md:983

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

  1723. msgstr ""

  1724. 

  1725. #: ../../../CHANGELOG.md:986

  1726. msgid "2023-03-21"

  1727. msgstr ""

  1728. 

  1729. #: ../../../CHANGELOG.md:988

  1730. msgid "The matrix-prometheus role lives independently now"

  1731. msgstr ""

  1732. 

  1733. #: ../../../CHANGELOG.md:990

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

  1735. msgstr ""

  1736. 

  1737. #: ../../../CHANGELOG.md:992

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

  1739. msgstr ""

  1740. 

  1741. #: ../../../CHANGELOG.md:994

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

  1743. msgstr ""

  1744. 

  1745. #: ../../../CHANGELOG.md:996

  1746. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Prometheus or not."

  1747. msgstr ""

  1748. 

  1749. #: ../../../CHANGELOG.md:998

  1750. msgid "If you're making use of Prometheus via this playbook, you will need to update variable references in your `vars.yml` file:"

  1751. msgstr ""

  1752. 

  1753. #: ../../../CHANGELOG.md:1000

  1754. msgid "`matrix_prometheus_docker_image_` -> `matrix_prometheus_container_image_`"

  1755. msgstr ""

  1756. 

  1757. #: ../../../CHANGELOG.md:1001

  1758. msgid "`matrix_prometheus_` -> `prometheus_`"

  1759. msgstr ""

  1760. 

  1761. #: ../../../CHANGELOG.md:1005

  1762. msgid "2023-03-12"

  1763. msgstr ""

  1764. 

  1765. #: ../../../CHANGELOG.md:1007

  1766. msgid "synapse-auto-compressor support"

  1767. msgstr ""

  1768. 

  1769. #: ../../../CHANGELOG.md:1009

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

  1771. msgstr ""

  1772. 

  1773. #: ../../../CHANGELOG.md:1011

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

  1775. msgstr ""

  1776. 

  1777. #: ../../../CHANGELOG.md:1013

  1778. msgid "it runs on a more up-to-date version of `rust-synapse-compress-state`"

  1779. msgstr ""

  1780. 

  1781. #: ../../../CHANGELOG.md:1014

  1782. msgid "it's a set-it-and-forget-it tool that you can enable and never have to deal with manual compression anymore"

  1783. msgstr ""

  1784. 

  1785. #: ../../../CHANGELOG.md:1016

  1786. msgid "This tool needs to be enabled manually, for now. In the future, we're considering enabling it by default for all Synapse installations."

  1787. msgstr ""

  1788. 

  1789. #: ../../../CHANGELOG.md:1018

  1790. msgid "See our [Setting up synapse-auto-compressor](docs/configuring-playbook-synapse-auto-compressor.md) documentation to get started."

  1791. msgstr ""

  1792. 

  1793. #: ../../../CHANGELOG.md:1021

  1794. msgid "2023-03-07"

  1795. msgstr ""

  1796. 

  1797. #: ../../../CHANGELOG.md:1023

  1798. msgid "Sliding Sync proxy (Element X) support"

  1799. msgstr ""

  1800. 

  1801. #: ../../../CHANGELOG.md:1025

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

  1803. msgstr ""

  1804. 

  1805. #: ../../../CHANGELOG.md:1027

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

  1807. msgstr ""

  1808. 

  1809. #: ../../../CHANGELOG.md:1029

  1810. msgid "To get started, see our [Setting up the Sliding Sync proxy](docs/configuring-playbook-sliding-sync-proxy.md) documentation page."

  1811. msgstr ""

  1812. 

  1813. #: ../../../CHANGELOG.md:1032

  1814. msgid "2023-03-02"

  1815. msgstr ""

  1816. 

  1817. #: ../../../CHANGELOG.md:1034

  1818. msgid "The matrix-etherpad role lives independently now"

  1819. msgstr ""

  1820. 

  1821. #: ../../../CHANGELOG.md:1036

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

  1823. msgstr ""

  1824. 

  1825. #: ../../../CHANGELOG.md:1038

  1826. msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Etherpad or not."

  1827. msgstr ""

  1828. 

  1829. #: ../../../CHANGELOG.md:1040

  1830. msgid "If you're making use of Etherpad via this playbook, you will need to update variable references in your `vars.yml` file:"

  1831. msgstr ""

  1832. 

  1833. #: ../../../CHANGELOG.md:1042

  1834. msgid "Rename `matrix_etherpad_public_endpoint` to `etherpad_path_prefix`"

  1835. msgstr ""

  1836. 

  1837. #: ../../../CHANGELOG.md:1044

  1838. msgid "Replace `matrix_etherpad_mode: dimension` with:"

  1839. msgstr ""

  1840. 

  1841. #: ../../../CHANGELOG.md:1045

  1842. msgid "for `matrix-nginx-proxy` users:"

  1843. msgstr ""

  1844. 

  1845. #: ../../../CHANGELOG.md:1046

  1846. msgid "`etherpad_nginx_proxy_dimension_integration_enabled: true`"

  1847. msgstr ""

  1848. 

  1849. #: ../../../CHANGELOG.md:1047

  1850. msgid "`etherpad_hostname: \"{{ matrix_server_fqn_dimension }}\"`"

  1851. msgstr ""

  1852. 

  1853. #: ../../../CHANGELOG.md:1048

  1854. msgid "for Traefik users:"

  1855. msgstr ""

  1856. 

  1857. #: ../../../CHANGELOG.md:1049

  1858. msgid "define your own `etherpad_hostname` and `etherpad_path_prefix` as you see fit"

  1859. msgstr ""

  1860. 

  1861. #: ../../../CHANGELOG.md:1051

  1862. msgid "Rename all other variables:"

  1863. msgstr ""

  1864. 

  1865. #: ../../../CHANGELOG.md:1052

  1866. msgid "`matrix_etherpad_docker_image_` -> `matrix_etherpad_container_image_`"

  1867. msgstr ""

  1868. 

  1869. #: ../../../CHANGELOG.md:1053

  1870. msgid "`matrix_etherpad_` -> `etherpad_`"

  1871. msgstr ""

  1872. 

  1873. #: ../../../CHANGELOG.md:1055

  1874. msgid "Along with this relocation, the new role also:"

  1875. msgstr ""

  1876. 

  1877. #: ../../../CHANGELOG.md:1057

  1878. msgid "supports [self-building](docs/self-building.md), so it should work on `arm32` and `arm64` architectures"

  1879. msgstr ""

  1880. 

  1881. #: ../../../CHANGELOG.md:1058

  1882. msgid "has native Traefik reverse-proxy support (Etherpad requests no longer go through `matrix-nginx-proxy` when using Traefik)"

  1883. msgstr ""

  1884. 

  1885. #: ../../../CHANGELOG.md:1061

  1886. msgid "2023-02-26"

  1887. msgstr ""

  1888. 

  1889. #: ../../../CHANGELOG.md:1063

  1890. msgid "Traefik is the default reverse-proxy now"

  1891. msgstr ""

  1892. 

  1893. #: ../../../CHANGELOG.md:1065

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

  1895. msgstr ""

  1896. 

  1897. #: ../../../CHANGELOG.md:1067

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

  1899. msgstr ""

  1900. 

  1901. #: ../../../CHANGELOG.md:1069

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

  1903. msgstr ""

  1904. 

  1905. #: ../../../CHANGELOG.md:1071

  1906. msgid "Traefik managed by the playbook"

  1907. msgstr ""

  1908. 

  1909. #: ../../../CHANGELOG.md:1072

  1910. msgid "Traefik managed by the user in another way"

  1911. msgstr ""

  1912. 

  1913. #: ../../../CHANGELOG.md:1073

  1914. msgid "another reverse-proxy on the same host (`127.0.0.1` port exposure)"

  1915. msgstr ""

  1916. 

  1917. #: ../../../CHANGELOG.md:1074

  1918. msgid "another reverse-proxy on another host (`0.0.0.0` port exposure)"

  1919. msgstr ""

  1920. 

  1921. #: ../../../CHANGELOG.md:1075

  1922. msgid "`matrix-nginx-proxy` — an `nginx` container managed by the playbook"

  1923. msgstr ""

  1924. 

  1925. #: ../../../CHANGELOG.md:1076

  1926. msgid "`nginx` webserver operated by the user, running without a container on the same server"

  1927. msgstr ""

  1928. 

  1929. #: ../../../CHANGELOG.md:1078

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

  1931. msgstr ""

  1932. 

  1933. #: ../../../CHANGELOG.md:1080

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

  1935. msgstr ""

  1936. 

  1937. #: ../../../CHANGELOG.md:1082

  1938. msgid "It's time for the **next step in our migration process** to Traefik and elimination of `matrix-nginx-proxy`:"

  1939. msgstr ""

  1940. 

  1941. #: ../../../CHANGELOG.md:1084

  1942. msgid "Traefik is now the default reverse-proxy for new installations"

  1943. msgstr ""

  1944. 

  1945. #: ../../../CHANGELOG.md:1085

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

  1947. msgstr ""

  1948. 

  1949. #: ../../../CHANGELOG.md:1087

  1950. msgid "How do I switch my existing setup to Traefik?"

  1951. msgstr ""

  1952. 

  1953. #: ../../../CHANGELOG.md:1089

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

  1955. msgstr ""

  1956. 

  1957. #: ../../../CHANGELOG.md:1091

  1958. msgid "If you experience trouble:"

  1959. msgstr ""

  1960. 

  1961. #: ../../../CHANGELOG.md:1093

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

  1963. msgstr ""

  1964. 

  1965. #: ../../../CHANGELOG.md:1094

  1966. msgid "Ask for help in our [support channels](README.md#support)"

  1967. msgstr ""

  1968. 

  1969. #: ../../../CHANGELOG.md:1095

  1970. msgid "Try switching to Traefik again later"

  1971. msgstr ""

  1972. 

  1973. #: ../../../CHANGELOG.md:1097

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

  1975. msgstr ""

  1976. 

  1977. #: ../../../CHANGELOG.md:1099

  1978. msgid "I already use my own Traefik server. How do I plug that in?"

  1979. msgstr ""

  1980. 

  1981. #: ../../../CHANGELOG.md:1101

  1982. msgid "See the [Traefik managed by the playbook](docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) section."

  1983. msgstr ""

  1984. 

  1985. #: ../../../CHANGELOG.md:1103

  1986. msgid "Why is matrix-nginx-proxy used even after switching to Traefik?"

  1987. msgstr ""

  1988. 

  1989. #: ../../../CHANGELOG.md:1105

  1990. msgid "This playbook manages many different services. All these services were initially integrated with `matrix-nginx-proxy`."

  1991. msgstr ""

  1992. 

  1993. #: ../../../CHANGELOG.md:1107

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

  1995. msgstr ""

  1996. 

  1997. #: ../../../CHANGELOG.md:1109

  1998. msgid "How do I remain on matrix-nginx-proxy?"

  1999. msgstr ""

  2000. 

  2001. #: ../../../CHANGELOG.md:1111

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

  2003. msgstr ""

  2004. 

  2005. #: ../../../CHANGELOG.md:1113

  2006. msgid "To proceed regardless of this warning, add `matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your configuration."

  2007. msgstr ""

  2008. 

  2009. #: ../../../CHANGELOG.md:1115

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

  2011. msgstr ""

  2012. 

  2013. #: ../../../CHANGELOG.md:1117

  2014. msgid "How do I keep using my own other reverse-proxy?"

  2015. msgstr ""

  2016. 

  2017. #: ../../../CHANGELOG.md:1119

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

  2019. msgstr ""

  2020. 

  2021. #: ../../../CHANGELOG.md:1122

  2022. msgid "2023-02-25"

  2023. msgstr ""

  2024. 

  2025. #: ../../../CHANGELOG.md:1124

  2026. msgid "rageshake support"

  2027. msgstr ""

  2028. 

  2029. #: ../../../CHANGELOG.md:1126

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

  2031. msgstr ""

  2032. 

  2033. #: ../../../CHANGELOG.md:1128

  2034. msgid "Additional details are available in [Setting up rageshake](docs/configuring-playbook-rageshake.md)."

  2035. msgstr ""

  2036. 

  2037. #: ../../../CHANGELOG.md:1131

  2038. msgid "2023-02-17"

  2039. msgstr ""

  2040. 

  2041. #: ../../../CHANGELOG.md:1133

  2042. msgid "Synapse templates customization support"

  2043. msgstr ""

  2044. 

  2045. #: ../../../CHANGELOG.md:1135

  2046. msgid "The playbook can now help you customize Synapse's templates."

  2047. msgstr ""

  2048. 

  2049. #: ../../../CHANGELOG.md:1137

  2050. msgid "Additional details are available in the [Customizing templates](docs/configuring-playbook-synapse.md#customizing-templates) section of our Synapse documentation."

  2051. msgstr ""

  2052. 

  2053. #: ../../../CHANGELOG.md:1139

  2054. msgid "The matrix-redis role lives independently now"

  2055. msgstr ""

  2056. 

  2057. #: ../../../CHANGELOG.md:1141

  2058. msgid "**TLDR**: the `matrix-redis` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  2059. msgstr ""

  2060. 

  2061. #: ../../../CHANGELOG.md:1143

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

  2063. msgstr ""

  2064. 

  2065. #: ../../../CHANGELOG.md:1145

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

  2067. msgstr ""

  2068. 

  2069. #: ../../../CHANGELOG.md:1147

  2070. msgid "The matrix-ntfy role lives independently now"

  2071. msgstr ""

  2072. 

  2073. #: ../../../CHANGELOG.md:1149

  2074. msgid "**TLDR**: the `matrix-ntfy` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  2075. msgstr ""

  2076. 

  2077. #: ../../../CHANGELOG.md:1151

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

  2079. msgstr ""

  2080. 

  2081. #: ../../../CHANGELOG.md:1153

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

  2083. msgstr ""

  2084. 

  2085. #: ../../../CHANGELOG.md:1156

  2086. msgid "2023-02-15"

  2087. msgstr ""

  2088. 

  2089. #: ../../../CHANGELOG.md:1158

  2090. msgid "The matrix-grafana role lives independently now"

  2091. msgstr ""

  2092. 

  2093. #: ../../../CHANGELOG.md:1160

  2094. msgid "**TLDR**: the `matrix-grafana` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  2095. msgstr ""

  2096. 

  2097. #: ../../../CHANGELOG.md:1162

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

  2099. msgstr ""

  2100. 

  2101. #: ../../../CHANGELOG.md:1164

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

  2103. msgstr ""

  2104. 

  2105. #: ../../../CHANGELOG.md:1167

  2106. msgid "2023-02-13"

  2107. msgstr ""

  2108. 

  2109. #: ../../../CHANGELOG.md:1169

  2110. msgid "The matrix-backup-borg role lives independently now"

  2111. msgstr ""

  2112. 

  2113. #: ../../../CHANGELOG.md:1171

  2114. msgid "**TLDR**: the `matrix-backup-borg` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  2115. msgstr ""

  2116. 

  2117. #: ../../../CHANGELOG.md:1173

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

  2119. msgstr ""

  2120. 

  2121. #: ../../../CHANGELOG.md:1175

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

  2123. msgstr ""

  2124. 

  2125. #: ../../../CHANGELOG.md:1178

  2126. msgid "2023-02-12"

  2127. msgstr ""

  2128. 

  2129. #: ../../../CHANGELOG.md:1180

  2130. msgid "(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support"

  2131. msgstr ""

  2132. 

  2133. #: ../../../CHANGELOG.md:1182

  2134. msgid "**TLDR**:"

  2135. msgstr ""

  2136. 

  2137. #: ../../../CHANGELOG.md:1184

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

  2139. msgstr ""

  2140. 

  2141. #: ../../../CHANGELOG.md:1185

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

  2143. msgstr ""

  2144. 

  2145. #: ../../../CHANGELOG.md:1186

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

  2147. msgstr ""

  2148. 

  2149. #: ../../../CHANGELOG.md:1187

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

  2151. msgstr ""

  2152. 

  2153. #: ../../../CHANGELOG.md:1188

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

  2155. msgstr ""

  2156. 

  2157. #: ../../../CHANGELOG.md:1190

  2158. msgid "Motivation for redoing our reverse-proxy setup"

  2159. msgstr ""

  2160. 

  2161. #: ../../../CHANGELOG.md:1192

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

  2163. msgstr ""

  2164. 

  2165. #: ../../../CHANGELOG.md:1194

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

  2167. msgstr ""

  2168. 

  2169. #: ../../../CHANGELOG.md:1196

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

  2171. msgstr ""

  2172. 

  2173. #: ../../../CHANGELOG.md:1198

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

  2175. msgstr ""

  2176. 

  2177. #: ../../../CHANGELOG.md:1200

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

  2179. msgstr ""

  2180. 

  2181. #: ../../../CHANGELOG.md:1202

  2182. msgid "*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined with exposing services manually (setting `_bind_port` variables)"

  2183. msgstr ""

  2184. 

  2185. #: ../../../CHANGELOG.md:1203

  2186. msgid "*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in `http`-only mode (no SSL certificate retrieval)."

  2187. msgstr ""

  2188. 

  2189. #: ../../../CHANGELOG.md:1205

  2190. msgid "Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations."

  2191. msgstr ""

  2192. 

  2193. #: ../../../CHANGELOG.md:1207

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

  2195. msgstr ""

  2196. 

  2197. #: ../../../CHANGELOG.md:1209

  2198. msgid "The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks:"

  2199. msgstr ""

  2200. 

  2201. #: ../../../CHANGELOG.md:1211

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

  2203. msgstr ""

  2204. 

  2205. #: ../../../CHANGELOG.md:1212

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

  2207. msgstr ""

  2208. 

  2209. #: ../../../CHANGELOG.md:1213

  2210. msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) — for hosting the [Nextcloud](https://nextcloud.com/) groupware platform"

  2211. msgstr ""

  2212. 

  2213. #: ../../../CHANGELOG.md:1215

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

  2215. msgstr ""

  2216. 

  2217. #: ../../../CHANGELOG.md:1217

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

  2219. msgstr ""

  2220. 

  2221. #: ../../../CHANGELOG.md:1219

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

  2223. msgstr ""

  2224. 

  2225. #: ../../../CHANGELOG.md:1221

  2226. msgid "How do these changes fix all these problems?"

  2227. msgstr ""

  2228. 

  2229. #: ../../../CHANGELOG.md:1223

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

  2231. msgstr ""

  2232. 

  2233. #: ../../../CHANGELOG.md:1225

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

  2235. msgstr ""

  2236. 

  2237. #: ../../../CHANGELOG.md:1227

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

  2239. msgstr ""

  2240. 

  2241. #: ../../../CHANGELOG.md:1229

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

  2243. msgstr ""

  2244. 

  2245. #: ../../../CHANGELOG.md:1231

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

  2247. msgstr ""

  2248. 

  2249. #: ../../../CHANGELOG.md:1233

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

  2251. msgstr ""

  2252. 

  2253. #: ../../../CHANGELOG.md:1235

  2254. msgid "Where we're at right now?"

  2255. msgstr ""

  2256. 

  2257. #: ../../../CHANGELOG.md:1237

  2258. msgid "`matrix_playbook_reverse_proxy_type` still defaults to a value of `playbook-managed-nginx`."

  2259. msgstr ""

  2260. 

  2261. #: ../../../CHANGELOG.md:1239

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

  2263. msgstr ""

  2264. 

  2265. #: ../../../CHANGELOG.md:1241

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

  2267. msgstr ""

  2268. 

  2269. #: ../../../CHANGELOG.md:1243

  2270. msgid "How do I explicitly switch to Traefik right now?"

  2271. msgstr ""

  2272. 

  2273. #: ../../../CHANGELOG.md:1245

  2274. msgid "**Users who wish to migrate to Traefik** today, can do so by **adding** this to their configuration:"

  2275. msgstr ""

  2276. 

  2277. #: ../../../CHANGELOG.md:1253

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

  2279. msgstr ""

  2280. 

  2281. #: ../../../CHANGELOG.md:1255

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

  2283. msgstr ""

  2284. 

  2285. #: ../../../CHANGELOG.md:1257

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

  2287. msgstr ""

  2288. 

  2289. #: ../../../CHANGELOG.md:1259

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

  2291. msgstr ""

  2292. 

  2293. #: ../../../CHANGELOG.md:1261

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

  2295. msgstr ""

  2296. 

  2297. #: ../../../CHANGELOG.md:1263

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

  2299. msgstr ""

  2300. 

  2301. #: ../../../CHANGELOG.md:1265

  2302. msgid "Where we're going in the near future?"

  2303. msgstr ""

  2304. 

  2305. #: ../../../CHANGELOG.md:1267

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

  2307. msgstr ""

  2308. 

  2309. #: ../../../CHANGELOG.md:1269

  2310. msgid "For now, `matrix-nginx-proxy` will stay around."

  2311. msgstr ""

  2312. 

  2313. #: ../../../CHANGELOG.md:1271

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

  2315. msgstr ""

  2316. 

  2317. #: ../../../CHANGELOG.md:1273

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

  2319. msgstr ""

  2320. 

  2321. #: ../../../CHANGELOG.md:1275

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

  2323. msgstr ""

  2324. 

  2325. #: ../../../CHANGELOG.md:1276

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

  2327. msgstr ""

  2328. 

  2329. #: ../../../CHANGELOG.md:1278

  2330. msgid "How do I help?"

  2331. msgstr ""

  2332. 

  2333. #: ../../../CHANGELOG.md:1280

  2334. msgid "You can help by:"

  2335. msgstr ""

  2336. 

  2337. #: ../../../CHANGELOG.md:1282

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

  2339. msgstr ""

  2340. 

  2341. #: ../../../CHANGELOG.md:1284

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

  2343. msgstr ""

  2344. 

  2345. #: ../../../CHANGELOG.md:1286

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

  2347. msgstr ""

  2348. 

  2349. #: ../../../CHANGELOG.md:1289

  2350. msgid "2023-02-10"

  2351. msgstr ""

  2352. 

  2353. #: ../../../CHANGELOG.md:1291

  2354. msgid "Matrix Authentication Support for Jitsi"

  2355. msgstr ""

  2356. 

  2357. #: ../../../CHANGELOG.md:1293

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

  2359. msgstr ""

  2360. 

  2361. #: ../../../CHANGELOG.md:1295

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

  2363. msgstr ""

  2364. 

  2365. #: ../../../CHANGELOG.md:1297

  2366. msgid "Draupnir moderation tool (bot) support"

  2367. msgstr ""

  2368. 

  2369. #: ../../../CHANGELOG.md:1299

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

  2371. msgstr ""

  2372. 

  2373. #: ../../../CHANGELOG.md:1301

  2374. msgid "Additional details are available in [Setting up Draupnir](docs/configuring-playbook-bot-draupnir.md)."

  2375. msgstr ""

  2376. 

  2377. #: ../../../CHANGELOG.md:1304

  2378. msgid "2023-02-05"

  2379. msgstr ""

  2380. 

  2381. #: ../../../CHANGELOG.md:1306

  2382. msgid "The matrix-prometheus-postgres-exporter role lives independently now"

  2383. msgstr ""

  2384. 

  2385. #: ../../../CHANGELOG.md:1308

  2386. msgid "**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  2387. msgstr ""

  2388. 

  2389. #: ../../../CHANGELOG.md:1310

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

  2391. msgstr ""

  2392. 

  2393. #: ../../../CHANGELOG.md:1312

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

  2395. msgstr ""

  2396. 

  2397. #: ../../../CHANGELOG.md:1314

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

  2399. msgstr ""

  2400. 

  2401. #: ../../../CHANGELOG.md:1316 ../../../CHANGELOG.md:1358

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

  2403. msgstr ""

  2404. 

  2405. #: ../../../CHANGELOG.md:1319

  2406. msgid "2023-01-26"

  2407. msgstr ""

  2408. 

  2409. #: ../../../CHANGELOG.md:1321

  2410. msgid "coturn can now use host-networking"

  2411. msgstr ""

  2412. 

  2413. #: ../../../CHANGELOG.md:1323

  2414. msgid "Large coturn deployments (with a huge range of ports specified via `matrix_coturn_turn_udp_min_port` and `matrix_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."

  2415. msgstr ""

  2416. 

  2417. #: ../../../CHANGELOG.md:1325

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

  2419. msgstr ""

  2420. 

  2421. #: ../../../CHANGELOG.md:1331

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

  2423. msgstr ""

  2424. 

  2425. #: ../../../CHANGELOG.md:1333

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

  2427. msgstr ""

  2428. 

  2429. #: ../../../CHANGELOG.md:1335

  2430. msgid "(Backward Compatibility) Tightening coturn security can lead to connectivity issues"

  2431. msgstr ""

  2432. 

  2433. #: ../../../CHANGELOG.md:1337

  2434. 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 `matrix_coturn_denied_peer_ips` and remove some IP ranges from it."

  2435. msgstr ""

  2436. 

  2437. #: ../../../CHANGELOG.md:1339

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

  2439. msgstr ""

  2440. 

  2441. #: ../../../CHANGELOG.md:1341

  2442. 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 `matrix_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."

  2443. msgstr ""

  2444. 

  2445. #: ../../../CHANGELOG.md:1343

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

  2447. msgstr ""

  2448. 

  2449. #: ../../../CHANGELOG.md:1346

  2450. msgid "2023-01-21"

  2451. msgstr ""

  2452. 

  2453. #: ../../../CHANGELOG.md:1348

  2454. msgid "The matrix-prometheus-node-exporter role lives independently now"

  2455. msgstr ""

  2456. 

  2457. #: ../../../CHANGELOG.md:1350

  2458. msgid "**TLDR**: the `matrix-prometheus-node-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  2459. msgstr ""

  2460. 

  2461. #: ../../../CHANGELOG.md:1352

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

  2463. msgstr ""

  2464. 

  2465. #: ../../../CHANGELOG.md:1354

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

  2467. msgstr ""

  2468. 

  2469. #: ../../../CHANGELOG.md:1356

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

  2471. msgstr ""

  2472. 

  2473. #: ../../../CHANGELOG.md:1361

  2474. msgid "2023-01-13"

  2475. msgstr ""

  2476. 

  2477. #: ../../../CHANGELOG.md:1363

  2478. msgid "Support for running commands via just"

  2479. msgstr ""

  2480. 

  2481. #: ../../../CHANGELOG.md:1365

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

  2483. msgstr ""

  2484. 

  2485. #: ../../../CHANGELOG.md:1367

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

  2487. msgstr ""

  2488. 

  2489. #: ../../../CHANGELOG.md:1369

  2490. msgid "Our [justfile](justfile) already defines some additional helpful **shortcut** commands that weren't part of our `Makefile`. Here are some examples:"

  2491. msgstr ""

  2492. 

  2493. #: ../../../CHANGELOG.md:1371

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

  2495. msgstr ""

  2496. 

  2497. #: ../../../CHANGELOG.md:1372

  2498. msgid "`just install-all --ask-vault-pass` — commands also support additional arguments (`--ask-vault-pass` will be appended to the above installation command)"

  2499. msgstr ""

  2500. 

  2501. #: ../../../CHANGELOG.md:1373

  2502. msgid "`just run-tags install-mautrix-slack,start` — to run specific playbook tags"

  2503. msgstr ""

  2504. 

  2505. #: ../../../CHANGELOG.md:1374

  2506. msgid "`just start-all` — (re-)starts all services"

  2507. msgstr ""

  2508. 

  2509. #: ../../../CHANGELOG.md:1375

  2510. msgid "`just stop-group postgres` — to stop only the Postgres service"

  2511. msgstr ""

  2512. 

  2513. #: ../../../CHANGELOG.md:1376

  2514. msgid "`just register-user alice secret-password yes` — registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)"

  2515. msgstr ""

  2516. 

  2517. #: ../../../CHANGELOG.md:1378

  2518. msgid "Additional helpful commands and shortcuts may be defined in the future."

  2519. msgstr ""

  2520. 

  2521. #: ../../../CHANGELOG.md:1380

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

  2523. msgstr ""

  2524. 

  2525. #: ../../../CHANGELOG.md:1383

  2526. msgid "2023-01-11"

  2527. msgstr ""

  2528. 

  2529. #: ../../../CHANGELOG.md:1385

  2530. msgid "mautrix-slack support"

  2531. msgstr ""

  2532. 

  2533. #: ../../../CHANGELOG.md:1387

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

  2535. msgstr ""

  2536. 

  2537. #: ../../../CHANGELOG.md:1389

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

  2539. msgstr ""

  2540. 

  2541. #: ../../../CHANGELOG.md:1392

  2542. msgid "2023-01-10"

  2543. msgstr ""

  2544. 

  2545. #: ../../../CHANGELOG.md:1394

  2546. msgid "ChatGPT support"

  2547. msgstr ""

  2548. 

  2549. #: ../../../CHANGELOG.md:1396

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

  2551. msgstr ""

  2552. 

  2553. #: ../../../CHANGELOG.md:1398

  2554. msgid "See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-chatgpt.md) documentation to get started."

  2555. msgstr ""

  2556. 

  2557. #: ../../../CHANGELOG.md:1401

  2558. msgid "2022-11-30"

  2559. msgstr ""

  2560. 

  2561. #: ../../../CHANGELOG.md:1403

  2562. msgid "matrix-postgres-backup has been replaced by the ansible-role-postgres-backup external role"

  2563. msgstr ""

  2564. 

  2565. #: ../../../CHANGELOG.md:1405

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

  2567. msgstr ""

  2568. 

  2569. #: ../../../CHANGELOG.md:1407

  2570. msgid "You'll need to rename your `matrix_postgres_backup`-prefixed variables such that they use a `postgres_backup` prefix."

  2571. msgstr ""

  2572. 

  2573. #: ../../../CHANGELOG.md:1410

  2574. msgid "2022-11-28"

  2575. msgstr ""

  2576. 

  2577. #: ../../../CHANGELOG.md:1412

  2578. msgid "matrix-postgres has been replaced by the ansible-role-postgres external role"

  2579. msgstr ""

  2580. 

  2581. #: ../../../CHANGELOG.md:1414

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

  2583. msgstr ""

  2584. 

  2585. #: ../../../CHANGELOG.md:1416

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

  2587. msgstr ""

  2588. 

  2589. #: ../../../CHANGELOG.md:1418

  2590. msgid "The new role is an upgraded version of the old `matrix-postgres` role with these notable differences:"

  2591. msgstr ""

  2592. 

  2593. #: ../../../CHANGELOG.md:1420

  2594. msgid "it uses different names for its variables (`matrix_postgres` -> `devture_postgres`)"

  2595. msgstr ""

  2596. 

  2597. #: ../../../CHANGELOG.md:1421

  2598. msgid "when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-postgresql), it will vacuum all your databases, not just the Synapse one"

  2599. msgstr ""

  2600. 

  2601. #: ../../../CHANGELOG.md:1423

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

  2603. msgstr ""

  2604. 

  2605. #: ../../../CHANGELOG.md:1425

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

  2607. msgstr ""

  2608. 

  2609. #: ../../../CHANGELOG.md:1427

  2610. msgid "The playbook no longer installs scripts to /usr/local/bin"

  2611. msgstr ""

  2612. 

  2613. #: ../../../CHANGELOG.md:1429

  2614. msgid "The locations of various scripts installed by the playbook have changed."

  2615. msgstr ""

  2616. 

  2617. #: ../../../CHANGELOG.md:1431

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

  2619. msgstr ""

  2620. 

  2621. #: ../../../CHANGELOG.md:1433

  2622. msgid "`/usr/local/bin/matrix-remove-all` -> `/matrix/bin/remove-all`"

  2623. msgstr ""

  2624. 

  2625. #: ../../../CHANGELOG.md:1434

  2626. msgid "`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`"

  2627. msgstr ""

  2628. 

  2629. #: ../../../CHANGELOG.md:1435

  2630. msgid "`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> `/matrix/ssl/bin/lets-encrypt-certificates-renew`"

  2631. msgstr ""

  2632. 

  2633. #: ../../../CHANGELOG.md:1436

  2634. msgid "`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin/register-user`"

  2635. msgstr ""

  2636. 

  2637. #: ../../../CHANGELOG.md:1439

  2638. msgid "2022-11-25"

  2639. msgstr ""

  2640. 

  2641. #: ../../../CHANGELOG.md:1441

  2642. msgid "2x-5x performance improvements in playbook runtime"

  2643. msgstr ""

  2644. 

  2645. #: ../../../CHANGELOG.md:1443

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

  2647. msgstr ""

  2648. 

  2649. #: ../../../CHANGELOG.md:1445

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

  2651. msgstr ""

  2652. 

  2653. #: ../../../CHANGELOG.md:1447

  2654. msgid "Even when running `ansible-playbook` manually (as most of us here do), it's beneficial not to waste time and CPU resources."

  2655. msgstr ""

  2656. 

  2657. #: ../../../CHANGELOG.md:1449

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

  2659. msgstr ""

  2660. 

  2661. #: ../../../CHANGELOG.md:1451

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

  2663. msgstr ""

  2664. 

  2665. #: ../../../CHANGELOG.md:1453

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

  2667. msgstr ""

  2668. 

  2669. #: ../../../CHANGELOG.md:1455

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

  2671. msgstr ""

  2672. 

  2673. #: ../../../CHANGELOG.md:1457

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

  2675. msgstr ""

  2676. 

  2677. #: ../../../CHANGELOG.md:1460

  2678. msgid "2022-11-22"

  2679. msgstr ""

  2680. 

  2681. #: ../../../CHANGELOG.md:1462

  2682. msgid "Automatic `matrix_architecture` determination"

  2683. msgstr ""

  2684. 

  2685. #: ../../../CHANGELOG.md:1464

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

  2687. msgstr ""

  2688. 

  2689. #: ../../../CHANGELOG.md:1466

  2690. msgid "Docker and the Docker SDK for Python are now installed via external roles"

  2691. msgstr ""

  2692. 

  2693. #: ../../../CHANGELOG.md:1470

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

  2695. msgstr ""

  2696. 

  2697. #: ../../../CHANGELOG.md:1472

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

  2699. msgstr ""

  2700. 

  2701. #: ../../../CHANGELOG.md:1474

  2702. msgid "If you're hitting issues with Docker installation or Docker SDK for Python installation, consider reporting bugs or contributing to these other projects."

  2703. msgstr ""

  2704. 

  2705. #: ../../../CHANGELOG.md:1476

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

  2707. msgstr ""

  2708. 

  2709. #: ../../../CHANGELOG.md:1479

  2710. msgid "2022-11-20"

  2711. msgstr ""

  2712. 

  2713. #: ../../../CHANGELOG.md:1481

  2714. msgid "(Backward Compatibility Break) Changing how reverse-proxying to Synapse works — now via a `matrix-synapse-reverse-proxy-companion` service"

  2715. msgstr ""

  2716. 

  2717. #: ../../../CHANGELOG.md:1483

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

  2719. msgstr ""

  2720. 

  2721. #: ../../../CHANGELOG.md:1485

  2722. msgid "Background"

  2723. msgstr ""

  2724. 

  2725. #: ../../../CHANGELOG.md:1487

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

  2727. msgstr ""

  2728. 

  2729. #: ../../../CHANGELOG.md:1489

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

  2731. msgstr ""

  2732. 

  2733. #: ../../../CHANGELOG.md:1491

  2734. msgid "Solution"

  2735. msgstr ""

  2736. 

  2737. #: ../../../CHANGELOG.md:1493

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

  2739. msgstr ""

  2740. 

  2741. #: ../../../CHANGELOG.md:1495

  2742. msgid "serve as a companion to Synapse and know how to reverse-proxy to Synapse correctly (no matter if workers are enabled or not)"

  2743. msgstr ""

  2744. 

  2745. #: ../../../CHANGELOG.md:1497

  2746. msgid "provide a unified container address for reaching Synapse (no matter if workers are enabled or not)"

  2747. msgstr ""

  2748. 

  2749. #: ../../../CHANGELOG.md:1498

  2750. msgid "`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server API traffic"

  2751. msgstr ""

  2752. 

  2753. #: ../../../CHANGELOG.md:1499

  2754. msgid "`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server (Federation) API traffic"

  2755. msgstr ""

  2756. 

  2757. #: ../../../CHANGELOG.md:1501

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

  2759. msgstr ""

  2760. 

  2761. #: ../../../CHANGELOG.md:1503

  2762. msgid "allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is disabled"

  2763. msgstr ""

  2764. 

  2765. #: ../../../CHANGELOG.md:1505

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

  2767. msgstr ""

  2768. 

  2769. #: ../../../CHANGELOG.md:1507

  2770. msgid "(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> (`matrix-synapse` or some Synapse worker))."

  2771. msgstr ""

  2772. 

  2773. #: ../../../CHANGELOG.md:1509

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

  2775. msgstr ""

  2776. 

  2777. #: ../../../CHANGELOG.md:1511

  2778. msgid "Webserver configuration"

  2779. msgstr ""

  2780. 

  2781. #: ../../../CHANGELOG.md:1513

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

  2783. msgstr ""

  2784. 

  2785. #: ../../../CHANGELOG.md:1515

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

  2787. msgstr ""

  2788. 

  2789. #: ../../../CHANGELOG.md:1517

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

  2791. msgstr ""

  2792. 

  2793. #: ../../../CHANGELOG.md:1519

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

  2795. msgstr ""

  2796. 

  2797. #: ../../../CHANGELOG.md:1521

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

  2799. msgstr ""

  2800. 

  2801. #: ../../../CHANGELOG.md:1524

  2802. msgid "2022-11-05"

  2803. msgstr ""

  2804. 

  2805. #: ../../../CHANGELOG.md:1526

  2806. msgid "(Backward Compatibility Break) A new default standalone mode for Etherpad"

  2807. msgstr ""

  2808. 

  2809. #: ../../../CHANGELOG.md:1528

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

  2811. msgstr ""

  2812. 

  2813. #: ../../../CHANGELOG.md:1530

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

  2815. msgstr ""

  2816. 

  2817. #: ../../../CHANGELOG.md:1532

  2818. msgid "If you've already got both Etherpad and Dimension in use you could:"

  2819. msgstr ""

  2820. 

  2821. #: ../../../CHANGELOG.md:1534

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

  2823. msgstr ""

  2824. 

  2825. #: ../../../CHANGELOG.md:1536

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

  2827. msgstr ""

  2828. 

  2829. #: ../../../CHANGELOG.md:1539

  2830. msgid "2022-11-04"

  2831. msgstr ""

  2832. 

  2833. #: ../../../CHANGELOG.md:1541

  2834. msgid "The playbook now uses external roles for some things"

  2835. msgstr ""

  2836. 

  2837. #: ../../../CHANGELOG.md:1543

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

  2839. msgstr ""

  2840. 

  2841. #: ../../../CHANGELOG.md:1545

  2842. msgid "We're in the process of trimming the playbook and making it reuse Ansible roles."

  2843. msgstr ""

  2844. 

  2845. #: ../../../CHANGELOG.md:1547

  2846. msgid "Starting now, the playbook is composed of 2 types of Ansible roles:"

  2847. msgstr ""

  2848. 

  2849. #: ../../../CHANGELOG.md:1549

  2850. msgid "those that live within the playbook itself (`roles/custom/*`)"

  2851. msgstr ""

  2852. 

  2853. #: ../../../CHANGELOG.md:1551

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

  2855. msgstr ""

  2856. 

  2857. #: ../../../CHANGELOG.md:1553

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

  2859. msgstr ""

  2860. 

  2861. #: ../../../CHANGELOG.md:1555

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

  2863. msgstr ""

  2864. 

  2865. #: ../../../CHANGELOG.md:1557

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

  2867. msgstr ""

  2868. 

  2869. #: ../../../CHANGELOG.md:1560

  2870. msgid "2022-10-14"

  2871. msgstr ""

  2872. 

  2873. #: ../../../CHANGELOG.md:1562

  2874. msgid "synapse-s3-storage-provider support"

  2875. msgstr ""

  2876. 

  2877. #: ../../../CHANGELOG.md:1564

  2878. msgid "**`synapse-s3-storage-provider` support is very new and still relatively untested. Using it may cause data loss.**"

  2879. msgstr ""

  2880. 

  2881. #: ../../../CHANGELOG.md:1566

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

  2883. msgstr ""

  2884. 

  2885. #: ../../../CHANGELOG.md:1568

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

  2887. msgstr ""

  2888. 

  2889. #: ../../../CHANGELOG.md:1570

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

  2891. msgstr ""

  2892. 

  2893. #: ../../../CHANGELOG.md:1572

  2894. msgid "Synapse container image customization support"

  2895. msgstr ""

  2896. 

  2897. #: ../../../CHANGELOG.md:1574

  2898. msgid "We now support customizing the Synapse container image by adding additional build steps to its [`Dockerfile`](https://docs.docker.com/engine/reference/builder/)."

  2899. msgstr ""

  2900. 

  2901. #: ../../../CHANGELOG.md:1576

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

  2903. msgstr ""

  2904. 

  2905. #: ../../../CHANGELOG.md:1578

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

  2907. msgstr ""

  2908. 

  2909. #: ../../../CHANGELOG.md:1589

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

  2911. msgstr ""

  2912. 

  2913. #: ../../../CHANGELOG.md:1591

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

  2915. msgstr ""

  2916. 

  2917. #: ../../../CHANGELOG.md:1594

  2918. msgid "2022-10-02"

  2919. msgstr ""

  2920. 

  2921. #: ../../../CHANGELOG.md:1596

  2922. msgid "matrix-ldap-registration-proxy support"

  2923. msgstr ""

  2924. 

  2925. #: ../../../CHANGELOG.md:1598

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

  2927. msgstr ""

  2928. 

  2929. #: ../../../CHANGELOG.md:1600

  2930. msgid "See our [Setting up matrix-ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started."

  2931. msgstr ""

  2932. 

  2933. #: ../../../CHANGELOG.md:1603

  2934. msgid "2022-09-15"

  2935. msgstr ""

  2936. 

  2937. #: ../../../CHANGELOG.md:1605

  2938. msgid "(Potential Backward Compatibility Break) Major improvements to Synapse workers"

  2939. msgstr ""

  2940. 

  2941. #: ../../../CHANGELOG.md:1607

  2942. msgid "People who are interested in running a Synapse worker setup should know that **our Synapse worker implementation is much more powerful now**:"

  2943. msgstr ""

  2944. 

  2945. #: ../../../CHANGELOG.md:1609

  2946. msgid "we've added support for [Stream writers](#stream-writers-support)"

  2947. msgstr ""

  2948. 

  2949. #: ../../../CHANGELOG.md:1610

  2950. msgid "we've added support for [multiple federation sender workers](#multiple-federation-sender-workers-support)"

  2951. msgstr ""

  2952. 

  2953. #: ../../../CHANGELOG.md:1611

  2954. msgid "we've added support for [multiple pusher workers](#multiple-pusher-workers-support)"

  2955. msgstr ""

  2956. 

  2957. #: ../../../CHANGELOG.md:1612

  2958. msgid "we've added support for [running background tasks on a worker](#background-tasks-can-run-on-a-worker)"

  2959. msgstr ""

  2960. 

  2961. #: ../../../CHANGELOG.md:1613

  2962. msgid "we've restored support for [`appservice` workers](#appservice-worker-support-is-back)"

  2963. msgstr ""

  2964. 

  2965. #: ../../../CHANGELOG.md:1614

  2966. msgid "we've restored support for [`user_dir` workers](#user-directory-worker-support-is-back)"

  2967. msgstr ""

  2968. 

  2969. #: ../../../CHANGELOG.md:1615

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

  2971. msgstr ""

  2972. 

  2973. #: ../../../CHANGELOG.md:1616

  2974. msgid "see the [Potential Backward Incompatibilities after these Synapse worker changes](#potential-backward-incompatibilities-after-these-synapse-worker-changes)"

  2975. msgstr ""

  2976. 

  2977. #: ../../../CHANGELOG.md:1618

  2978. msgid "Stream writers support"

  2979. msgstr ""

  2980. 

  2981. #: ../../../CHANGELOG.md:1620

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

  2983. msgstr ""

  2984. 

  2985. #: ../../../CHANGELOG.md:1622

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

  2987. msgstr ""

  2988. 

  2989. #: ../../../CHANGELOG.md:1624

  2990. msgid "If you'd like to customize the number of workers we also make that possible using these variables:"

  2991. msgstr ""

  2992. 

  2993. #: ../../../CHANGELOG.md:1637

  2994. msgid "Multiple federation sender workers support"

  2995. msgstr ""

  2996. 

  2997. #: ../../../CHANGELOG.md:1639

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

  2999. msgstr ""

  3000. 

  3001. #: ../../../CHANGELOG.md:1641

  3002. msgid "Multiple pusher workers support"

  3003. msgstr ""

  3004. 

  3005. #: ../../../CHANGELOG.md:1643

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

  3007. msgstr ""

  3008. 

  3009. #: ../../../CHANGELOG.md:1645

  3010. msgid "Background tasks can run on a worker"

  3011. msgstr ""

  3012. 

  3013. #: ../../../CHANGELOG.md:1647

  3014. msgid "From now on, you can put [background task processing on a worker](https://matrix-org.github.io/synapse/latest/workers.html#background-tasks)."

  3015. msgstr ""

  3016. 

  3017. #: ../../../CHANGELOG.md:1649

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

  3019. msgstr ""

  3020. 

  3021. #: ../../../CHANGELOG.md:1651

  3022. msgid "Appservice worker support is back"

  3023. msgstr ""

  3024. 

  3025. #: ../../../CHANGELOG.md:1653

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

  3027. msgstr ""

  3028. 

  3029. #: ../../../CHANGELOG.md:1655

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

  3031. msgstr ""

  3032. 

  3033. #: ../../../CHANGELOG.md:1657

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

  3035. msgstr ""

  3036. 

  3037. #: ../../../CHANGELOG.md:1659

  3038. msgid "User Directory worker support is back"

  3039. msgstr ""

  3040. 

  3041. #: ../../../CHANGELOG.md:1661

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

  3043. msgstr ""

  3044. 

  3045. #: ../../../CHANGELOG.md:1663

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

  3047. msgstr ""

  3048. 

  3049. #: ../../../CHANGELOG.md:1665

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

  3051. msgstr ""

  3052. 

  3053. #: ../../../CHANGELOG.md:1667

  3054. msgid "Using more than 1 media repository worker is now more reliable"

  3055. msgstr ""

  3056. 

  3057. #: ../../../CHANGELOG.md:1669

  3058. msgid "With `matrix_synapse_workers_preset: one-of-each`, we only launch one `media_repository` worker."

  3059. msgstr ""

  3060. 

  3061. #: ../../../CHANGELOG.md:1671

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

  3063. msgstr ""

  3064. 

  3065. #: ../../../CHANGELOG.md:1673

  3066. msgid "Potential Backward Incompatibilities after these Synapse worker changes"

  3067. msgstr ""

  3068. 

  3069. #: ../../../CHANGELOG.md:1675

  3070. msgid "Below we'll discuss **potential backward incompatibilities**."

  3071. msgstr ""

  3072. 

  3073. #: ../../../CHANGELOG.md:1677

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

  3075. msgstr ""

  3076. 

  3077. #: ../../../CHANGELOG.md:1679

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

  3079. msgstr ""

  3080. 

  3081. #: ../../../CHANGELOG.md:1681

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

  3083. msgstr ""

  3084. 

  3085. #: ../../../CHANGELOG.md:1683

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

  3087. msgstr ""

  3088. 

  3089. #: ../../../CHANGELOG.md:1686

  3090. msgid "2022-09-09"

  3091. msgstr ""

  3092. 

  3093. #: ../../../CHANGELOG.md:1688

  3094. msgid "Cactus Comments support"

  3095. msgstr ""

  3096. 

  3097. #: ../../../CHANGELOG.md:1690

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

  3099. msgstr ""

  3100. 

  3101. #: ../../../CHANGELOG.md:1692

  3102. msgid "See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-comments.md) documentation to get started."

  3103. msgstr ""

  3104. 

  3105. #: ../../../CHANGELOG.md:1695

  3106. msgid "2022-08-23"

  3107. msgstr ""

  3108. 

  3109. #: ../../../CHANGELOG.md:1697

  3110. msgid "Postmoogle email bridge support"

  3111. msgstr ""

  3112. 

  3113. #: ../../../CHANGELOG.md:1699

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

  3115. msgstr ""

  3116. 

  3117. #: ../../../CHANGELOG.md:1701

  3118. msgid "See our [Setting up Postmoogle email bridging](docs/configuring-playbook-bridge-postmoogle.md) documentation to get started."

  3119. msgstr ""

  3120. 

  3121. #: ../../../CHANGELOG.md:1704

  3122. msgid "2022-08-10"

  3123. msgstr ""

  3124. 

  3125. #: ../../../CHANGELOG.md:1706

  3126. msgid "mautrix-whatsapp default configuration changes"

  3127. msgstr ""

  3128. 

  3129. #: ../../../CHANGELOG.md:1708

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

  3131. msgstr ""

  3132. 

  3133. #: ../../../CHANGELOG.md:1710

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

  3135. msgstr ""

  3136. 

  3137. #: ../../../CHANGELOG.md:1712

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

  3139. msgstr ""

  3140. 

  3141. #: ../../../CHANGELOG.md:1715

  3142. msgid "2022-08-09"

  3143. msgstr ""

  3144. 

  3145. #: ../../../CHANGELOG.md:1717

  3146. msgid "Conduit support"

  3147. msgstr ""

  3148. 

  3149. #: ../../../CHANGELOG.md:1719

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

  3151. msgstr ""

  3152. 

  3153. #: ../../../CHANGELOG.md:1721

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

  3155. msgstr ""

  3156. 

  3157. #: ../../../CHANGELOG.md:1723

  3158. msgid "To try out Conduit, we recommend that you **use a new server** and the following `vars.yml` configuration:"

  3159. msgstr ""

  3160. 

  3161. #: ../../../CHANGELOG.md:1729

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

  3163. msgstr ""

  3164. 

  3165. #: ../../../CHANGELOG.md:1732

  3166. msgid "2022-07-29"

  3167. msgstr ""

  3168. 

  3169. #: ../../../CHANGELOG.md:1734

  3170. msgid "mautrix-discord support"

  3171. msgstr ""

  3172. 

  3173. #: ../../../CHANGELOG.md:1736

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

  3175. msgstr ""

  3176. 

  3177. #: ../../../CHANGELOG.md:1738

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

  3179. msgstr ""

  3180. 

  3181. #: ../../../CHANGELOG.md:1741

  3182. msgid "2022-07-27"

  3183. msgstr ""

  3184. 

  3185. #: ../../../CHANGELOG.md:1743

  3186. msgid "matrix-appservice-kakaotalk support"

  3187. msgstr ""

  3188. 

  3189. #: ../../../CHANGELOG.md:1745

  3190. 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!"

  3191. msgstr ""

  3192. 

  3193. #: ../../../CHANGELOG.md:1747

  3194. msgid "See our [Setting up Appservice Kakaotalk bridging](docs/configuring-playbook-bridge-appservice-kakaotalk.md) documentation to get started."

  3195. msgstr ""

  3196. 

  3197. #: ../../../CHANGELOG.md:1750

  3198. msgid "2022-07-20"

  3199. msgstr ""

  3200. 

  3201. #: ../../../CHANGELOG.md:1752

  3202. msgid "maubot support"

  3203. msgstr ""

  3204. 

  3205. #: ../../../CHANGELOG.md:1754

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

  3207. msgstr ""

  3208. 

  3209. #: ../../../CHANGELOG.md:1756

  3210. msgid "See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) documentation to get started."

  3211. msgstr ""

  3212. 

  3213. #: ../../../CHANGELOG.md:1759

  3214. msgid "2022-07-14"

  3215. msgstr ""

  3216. 

  3217. #: ../../../CHANGELOG.md:1761

  3218. msgid "mx-puppet-skype removal"

  3219. msgstr ""

  3220. 

  3221. #: ../../../CHANGELOG.md:1763

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

  3223. msgstr ""

  3224. 

  3225. #: ../../../CHANGELOG.md:1765

  3226. msgid "To completely clean up your server from `mx-puppet-skype`'s presence on it:"

  3227. msgstr ""

  3228. 

  3229. #: ../../../CHANGELOG.md:1767

  3230. msgid "ensure your Ansible configuration (`vars.yml` file) no longer contains `matrix_mx_puppet_skype_*` references"

  3231. msgstr ""

  3232. 

  3233. #: ../../../CHANGELOG.md:1768

  3234. msgid "stop and disable the systemd service (run `systemctl disable --now matrix-mx-puppet-skype` on the server)"

  3235. msgstr ""

  3236. 

  3237. #: ../../../CHANGELOG.md:1769

  3238. msgid "delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-skype.service` on the server)"

  3239. msgstr ""

  3240. 

  3241. #: ../../../CHANGELOG.md:1770

  3242. msgid "delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on the server)"

  3243. msgstr ""

  3244. 

  3245. #: ../../../CHANGELOG.md:1771

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

  3247. msgstr ""

  3248. 

  3249. #: ../../../CHANGELOG.md:1773

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

  3251. msgstr ""

  3252. 

  3253. #: ../../../CHANGELOG.md:1775

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

  3255. msgstr ""

  3256. 

  3257. #: ../../../CHANGELOG.md:1777

  3258. msgid "signald (0.19.0+) upgrade requires data migration"

  3259. msgstr ""

  3260. 

  3261. #: ../../../CHANGELOG.md:1779

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

  3263. msgstr ""

  3264. 

  3265. #: ../../../CHANGELOG.md:1781

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

  3267. msgstr ""

  3268. 

  3269. #: ../../../CHANGELOG.md:1783

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

  3271. msgstr ""

  3272. 

  3273. #: ../../../CHANGELOG.md:1785

  3274. msgid "We attempt to do this data migration automatically every time Signald starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` systemd unit definition."

  3275. msgstr ""

  3276. 

  3277. #: ../../../CHANGELOG.md:1787

  3278. 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!"

  3279. msgstr ""

  3280. 

  3281. #: ../../../CHANGELOG.md:1790

  3282. msgid "2022-07-05"

  3283. msgstr ""

  3284. 

  3285. #: ../../../CHANGELOG.md:1792

  3286. msgid "Ntfy push notifications support"

  3287. msgstr ""

  3288. 

  3289. #: ../../../CHANGELOG.md:1794

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

  3291. msgstr ""

  3292. 

  3293. #: ../../../CHANGELOG.md:1796

  3294. msgid "See our [Setting up the ntfy push notifications server](docs/configuring-playbook-ntfy.md) documentation to get started."

  3295. msgstr ""

  3296. 

  3297. #: ../../../CHANGELOG.md:1799

  3298. msgid "2022-06-23"

  3299. msgstr ""

  3300. 

  3301. #: ../../../CHANGELOG.md:1801

  3302. msgid "(Potential Backward Compatibility Break) Changes around metrics collection"

  3303. msgstr ""

  3304. 

  3305. #: ../../../CHANGELOG.md:1803

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

  3307. msgstr ""

  3308. 

  3309. #: ../../../CHANGELOG.md:1805

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

  3311. msgstr ""

  3312. 

  3313. #: ../../../CHANGELOG.md:1807

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

  3315. msgstr ""

  3316. 

  3317. #: ../../../CHANGELOG.md:1809

  3318. msgid "**If you are using the [Hookshot bridge](docs/configuring-playbook-bridge-hookshot.md)**, you may find that:"

  3319. msgstr ""

  3320. 

  3321. #: ../../../CHANGELOG.md:1810

  3322. msgid "**Metrics may not be enabled by default anymore**:"

  3323. msgstr ""

  3324. 

  3325. #: ../../../CHANGELOG.md:1811

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

  3327. msgstr ""

  3328. 

  3329. #: ../../../CHANGELOG.md:1812

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

  3331. msgstr ""

  3332. 

  3333. #: ../../../CHANGELOG.md:1813

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

  3335. msgstr ""

  3336. 

  3337. #: ../../../CHANGELOG.md:1814

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

  3339. msgstr ""

  3340. 

  3341. #: ../../../CHANGELOG.md:1816

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

  3343. msgstr ""

  3344. 

  3345. #: ../../../CHANGELOG.md:1818

  3346. msgid "**If you're using [postgres-exporter](docs/configuring-playbook-prometheus-postgres.md)** (`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`."

  3347. msgstr ""

  3348. 

  3349. #: ../../../CHANGELOG.md:1820

  3350. msgid "**If you're using Synapse** and would like to collect its metrics from an external Prometheus server, you may find that:"

  3351. msgstr ""

  3352. 

  3353. #: ../../../CHANGELOG.md:1822

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

  3355. msgstr ""

  3356. 

  3357. #: ../../../CHANGELOG.md:1823

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

  3359. msgstr ""

  3360. 

  3361. #: ../../../CHANGELOG.md:1824

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

  3363. msgstr ""

  3364. 

  3365. #: ../../../CHANGELOG.md:1825

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

  3367. msgstr ""

  3368. 

  3369. #: ../../../CHANGELOG.md:1827

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

  3371. msgstr ""

  3372. 

  3373. #: ../../../CHANGELOG.md:1829

  3374. msgid "2022-06-13"

  3375. msgstr ""

  3376. 

  3377. #: ../../../CHANGELOG.md:1831

  3378. msgid "go-skype-bridge bridging support"

  3379. msgstr ""

  3380. 

  3381. #: ../../../CHANGELOG.md:1833

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

  3383. msgstr ""

  3384. 

  3385. #: ../../../CHANGELOG.md:1835

  3386. msgid "See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md) documentation to get started."

  3387. msgstr ""

  3388. 

  3389. #: ../../../CHANGELOG.md:1837

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

  3391. msgstr ""

  3392. 

  3393. #: ../../../CHANGELOG.md:1840

  3394. msgid "2022-06-09"

  3395. msgstr ""

  3396. 

  3397. #: ../../../CHANGELOG.md:1842

  3398. msgid "Running Ansible in a container can now happen on the Matrix server itself"

  3399. msgstr ""

  3400. 

  3401. #: ../../../CHANGELOG.md:1844

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

  3403. msgstr ""

  3404. 

  3405. #: ../../../CHANGELOG.md:1847

  3406. msgid "2022-05-31"

  3407. msgstr ""

  3408. 

  3409. #: ../../../CHANGELOG.md:1849

  3410. msgid "Synapse v1.60 upgrade may cause trouble and require manual intervention"

  3411. msgstr ""

  3412. 

  3413. #: ../../../CHANGELOG.md:1851

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

  3415. msgstr ""

  3416. 

  3417. #: ../../../CHANGELOG.md:1853

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

  3419. msgstr ""

  3420. 

  3421. #: ../../../CHANGELOG.md:1855

  3422. msgid "**If Synapse fails to start** after your next playbook run, you'll need to:"

  3423. msgstr ""

  3424. 

  3425. #: ../../../CHANGELOG.md:1857

  3426. msgid "SSH into the Matrix server"

  3427. msgstr ""

  3428. 

  3429. #: ../../../CHANGELOG.md:1858

  3430. msgid "launch `/usr/local/bin/matrix-postgres-cli`"

  3431. msgstr ""

  3432. 

  3433. #: ../../../CHANGELOG.md:1859

  3434. msgid "switch to the `synapse` database: `\\c synapse`"

  3435. msgstr ""

  3436. 

  3437. #: ../../../CHANGELOG.md:1860

  3438. msgid "run the following SQL query:"

  3439. msgstr ""

  3440. 

  3441. #: ../../../CHANGELOG.md:1879

  3442. msgid "You could then restart services: `ansible-playbook -i inventory/hosts setup.yml --tags=start`"

  3443. msgstr ""

  3444. 

  3445. #: ../../../CHANGELOG.md:1882

  3446. msgid "2022-04-25"

  3447. msgstr ""

  3448. 

  3449. #: ../../../CHANGELOG.md:1884

  3450. msgid "Buscarron bot support"

  3451. msgstr ""

  3452. 

  3453. #: ../../../CHANGELOG.md:1886

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

  3455. msgstr ""

  3456. 

  3457. #: ../../../CHANGELOG.md:1888

  3458. msgid "See our [Setting up Buscarron](docs/configuring-playbook-bot-buscarron.md) documentation to get started."

  3459. msgstr ""

  3460. 

  3461. #: ../../../CHANGELOG.md:1891

  3462. msgid "2022-04-21"

  3463. msgstr ""

  3464. 

  3465. #: ../../../CHANGELOG.md:1893

  3466. msgid "matrix-registration-bot support"

  3467. msgstr ""

  3468. 

  3469. #: ../../../CHANGELOG.md:1895

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

  3471. msgstr ""

  3472. 

  3473. #: ../../../CHANGELOG.md:1897

  3474. msgid "See our [Setting up matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) documentation to get started."

  3475. msgstr ""

  3476. 

  3477. #: ../../../CHANGELOG.md:1900

  3478. msgid "2022-04-19"

  3479. msgstr ""

  3480. 

  3481. #: ../../../CHANGELOG.md:1902

  3482. msgid "BorgBackup support"

  3483. msgstr ""

  3484. 

  3485. #: ../../../CHANGELOG.md:1904

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

  3487. msgstr ""

  3488. 

  3489. #: ../../../CHANGELOG.md:1906

  3490. msgid "See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md) documentation to get started."

  3491. msgstr ""

  3492. 

  3493. #: ../../../CHANGELOG.md:1908

  3494. msgid "(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action"

  3495. msgstr ""

  3496. 

  3497. #: ../../../CHANGELOG.md:1910

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

  3499. msgstr ""

  3500. 

  3501. #: ../../../CHANGELOG.md:1912

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

  3503. msgstr ""

  3504. 

  3505. #: ../../../CHANGELOG.md:1914

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

  3507. msgstr ""

  3508. 

  3509. #: ../../../CHANGELOG.md:1916

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

  3511. msgstr ""

  3512. 

  3513. #: ../../../CHANGELOG.md:1918

  3514. msgid "Pull the latest playbook changes"

  3515. msgstr ""

  3516. 

  3517. #: ../../../CHANGELOG.md:1919

  3518. msgid "Stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"

  3519. msgstr ""

  3520. 

  3521. #: ../../../CHANGELOG.md:1920

  3522. msgid "Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all`)"

  3523. msgstr ""

  3524. 

  3525. #: ../../../CHANGELOG.md:1921

  3526. msgid "Start Postgres (`systemctl start matrix-postgres` on the server)"

  3527. msgstr ""

  3528. 

  3529. #: ../../../CHANGELOG.md:1922

  3530. msgid "Start the main Synapse process (`systemctl start matrix-synapse` on the server)"

  3531. msgstr ""

  3532. 

  3533. #: ../../../CHANGELOG.md:1923

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

  3535. msgstr ""

  3536. 

  3537. #: ../../../CHANGELOG.md:1924

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

  3539. msgstr ""

  3540. 

  3541. #: ../../../CHANGELOG.md:1927

  3542. msgid "2022-04-14"

  3543. msgstr ""

  3544. 

  3545. #: ../../../CHANGELOG.md:1929

  3546. msgid "(Compatibility Break) Changes to `docker-src` permissions necessitating manual action"

  3547. msgstr ""

  3548. 

  3549. #: ../../../CHANGELOG.md:1931

  3550. msgid "Users who build container images from source will need to manually correct file permissions of some directories on the server."

  3551. msgstr ""

  3552. 

  3553. #: ../../../CHANGELOG.md:1933

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

  3555. msgstr ""

  3556. 

  3557. #: ../../../CHANGELOG.md:1935

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

  3559. msgstr ""

  3560. 

  3561. #: ../../../CHANGELOG.md:1937

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

  3563. msgstr ""

  3564. 

  3565. #: ../../../CHANGELOG.md:1940

  3566. msgid "2022-03-17"

  3567. msgstr ""

  3568. 

  3569. #: ../../../CHANGELOG.md:1942

  3570. msgid "(Compatibility Break) ma1sd identity server no longer installed by default"

  3571. msgstr ""

  3572. 

  3573. #: ../../../CHANGELOG.md:1944

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

  3575. msgstr ""

  3576. 

  3577. #: ../../../CHANGELOG.md:1946

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

  3579. msgstr ""

  3580. 

  3581. #: ../../../CHANGELOG.md:1948

  3582. msgid "Since Element clients no longer default to using a public identity server if another one is not provided, we can stop installing ma1sd."

  3583. msgstr ""

  3584. 

  3585. #: ../../../CHANGELOG.md:1950

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

  3587. msgstr ""

  3588. 

  3589. #: ../../../CHANGELOG.md:1957

  3590. msgid "2022-02-12"

  3591. msgstr ""

  3592. 

  3593. #: ../../../CHANGELOG.md:1959

  3594. msgid "matrix_encryption_disabler support"

  3595. msgstr ""

  3596. 

  3597. #: ../../../CHANGELOG.md:1961

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

  3599. msgstr ""

  3600. 

  3601. #: ../../../CHANGELOG.md:1963

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

  3603. msgstr ""

  3604. 

  3605. #: ../../../CHANGELOG.md:1966

  3606. msgid "2022-02-01"

  3607. msgstr ""

  3608. 

  3609. #: ../../../CHANGELOG.md:1968

  3610. msgid "matrix-hookshot bridging support"

  3611. msgstr ""

  3612. 

  3613. #: ../../../CHANGELOG.md:1970

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

  3615. msgstr ""

  3616. 

  3617. #: ../../../CHANGELOG.md:1973

  3618. msgid "2022-01-31"

  3619. msgstr ""

  3620. 

  3621. #: ../../../CHANGELOG.md:1975

  3622. msgid "ARM support for matrix-corporal"

  3623. msgstr ""

  3624. 

  3625. #: ../../../CHANGELOG.md:1977

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

  3627. msgstr ""

  3628. 

  3629. #: ../../../CHANGELOG.md:1980

  3630. msgid "2022-01-07"

  3631. msgstr ""

  3632. 

  3633. #: ../../../CHANGELOG.md:1982

  3634. msgid "Dendrite support"

  3635. msgstr ""

  3636. 

  3637. #: ../../../CHANGELOG.md:1984

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

  3639. msgstr ""

  3640. 

  3641. #: ../../../CHANGELOG.md:1986

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

  3643. msgstr ""

  3644. 

  3645. #: ../../../CHANGELOG.md:1988

  3646. msgid "We believe that 2022 will be the year of the non-Synapse Matrix server!"

  3647. msgstr ""

  3648. 

  3649. #: ../../../CHANGELOG.md:1990

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

  3651. msgstr ""

  3652. 

  3653. #: ../../../CHANGELOG.md:1992

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

  3655. msgstr ""

  3656. 

  3657. #: ../../../CHANGELOG.md:1994

  3658. msgid "Adapting the configuration for existing Synapse installations"

  3659. msgstr ""

  3660. 

  3661. #: ../../../CHANGELOG.md:1996

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

  3663. msgstr ""

  3664. 

  3665. #: ../../../CHANGELOG.md:1998

  3666. msgid "The `vars.yml` file for **existing installations will need to be updated** by adding this **additional configuration**:"

  3667. msgstr ""

  3668. 

  3669. #: ../../../CHANGELOG.md:2010

  3670. msgid "Trying out Dendrite"

  3671. msgstr ""

  3672. 

  3673. #: ../../../CHANGELOG.md:2012

  3674. msgid "Finally, **to try out Dendrite**, we recommend that you **use a new server** and the following addition to your `vars.yml` configuration:"

  3675. msgstr ""

  3676. 

  3677. #: ../../../CHANGELOG.md:2018

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

  3679. msgstr ""

  3680. 

  3681. #: ../../../CHANGELOG.md:2020

  3682. msgid "We're excited to gain support for other homeserver implementations, like [Conduit](https://conduit.rs/), etc!"

  3683. msgstr ""

  3684. 

  3685. #: ../../../CHANGELOG.md:2022

  3686. msgid "Honoroit bot support"

  3687. msgstr ""

  3688. 

  3689. #: ../../../CHANGELOG.md:2024

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

  3691. msgstr ""

  3692. 

  3693. #: ../../../CHANGELOG.md:2026

  3694. msgid "See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documentation to get started."

  3695. msgstr ""

  3696. 

  3697. #: ../../../CHANGELOG.md:2029

  3698. msgid "2022-01-06"

  3699. msgstr ""

  3700. 

  3701. #: ../../../CHANGELOG.md:2031

  3702. msgid "Cinny support"

  3703. msgstr ""

  3704. 

  3705. #: ../../../CHANGELOG.md:2033

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

  3707. msgstr ""

  3708. 

  3709. #: ../../../CHANGELOG.md:2035

  3710. msgid "By default, we still install Element Web. Still, people who'd like to try Cinny out can now install it via the playbook."

  3711. msgstr ""

  3712. 

  3713. #: ../../../CHANGELOG.md:2037

  3714. msgid "Additional details are available in [Setting up Cinny](docs/configuring-playbook-client-cinny.md)."

  3715. msgstr ""

  3716. 

  3717. #: ../../../CHANGELOG.md:2040

  3718. msgid "2021-12-22"

  3719. msgstr ""

  3720. 

  3721. #: ../../../CHANGELOG.md:2042

  3722. msgid "Twitter bridging support via mautrix-twitter"

  3723. msgstr ""

  3724. 

  3725. #: ../../../CHANGELOG.md:2044

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

  3727. msgstr ""

  3728. 

  3729. #: ../../../CHANGELOG.md:2047

  3730. msgid "2021-12-14"

  3731. msgstr ""

  3732. 

  3733. #: ../../../CHANGELOG.md:2049

  3734. msgid "(Security) Users of the Signal bridge may wish to upgrade it to work around log4j vulnerability"

  3735. msgstr ""

  3736. 

  3737. #: ../../../CHANGELOG.md:2051

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

  3739. msgstr ""

  3740. 

  3741. #: ../../../CHANGELOG.md:2053

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

  3743. msgstr ""

  3744. 

  3745. #: ../../../CHANGELOG.md:2056

  3746. msgid "2021-11-11"

  3747. msgstr ""

  3748. 

  3749. #: ../../../CHANGELOG.md:2058

  3750. msgid "Dropped support for Postgres v9.6"

  3751. msgstr ""

  3752. 

  3753. #: ../../../CHANGELOG.md:2060

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

  3755. msgstr ""

  3756. 

  3757. #: ../../../CHANGELOG.md:2062

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

  3759. msgstr ""

  3760. 

  3761. #: ../../../CHANGELOG.md:2065

  3762. msgid "2021-10-23"

  3763. msgstr ""

  3764. 

  3765. #: ../../../CHANGELOG.md:2067

  3766. msgid "Hangouts bridge no longer updated, superseded by a Googlechat bridge"

  3767. msgstr ""

  3768. 

  3769. #: ../../../CHANGELOG.md:2069

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

  3771. msgstr ""

  3772. 

  3773. #: ../../../CHANGELOG.md:2071

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

  3775. msgstr ""

  3776. 

  3777. #: ../../../CHANGELOG.md:2074

  3778. msgid "2021-08-23"

  3779. msgstr ""

  3780. 

  3781. #: ../../../CHANGELOG.md:2076

  3782. msgid "LinkedIn bridging support via beeper-linkedin"

  3783. msgstr ""

  3784. 

  3785. #: ../../../CHANGELOG.md:2078

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

  3787. msgstr ""

  3788. 

  3789. #: ../../../CHANGELOG.md:2080

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

  3791. msgstr ""

  3792. 

  3793. #: ../../../CHANGELOG.md:2082

  3794. msgid "To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)."

  3795. msgstr ""

  3796. 

  3797. #: ../../../CHANGELOG.md:2085

  3798. msgid "2021-08-20"

  3799. msgstr ""

  3800. 

  3801. #: ../../../CHANGELOG.md:2087

  3802. msgid "Sygnal upgraded — ARM support and no longer requires a database"

  3803. msgstr ""

  3804. 

  3805. #: ../../../CHANGELOG.md:2089

  3806. msgid "The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been upgraded from `v0.9.0` to `v0.10.1`."

  3807. msgstr ""

  3808. 

  3809. #: ../../../CHANGELOG.md:2091

  3810. msgid "This is an optional component for the playbook, so most of our users wouldn't care about this announcement."

  3811. msgstr ""

  3812. 

  3813. #: ../../../CHANGELOG.md:2093

  3814. msgid "Since this feels like a relatively big (and untested, as of yet) Sygnal change, we're putting up this changelog entry."

  3815. msgstr ""

  3816. 

  3817. #: ../../../CHANGELOG.md:2095

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

  3819. msgstr ""

  3820. 

  3821. #: ../../../CHANGELOG.md:2098

  3822. msgid "2021-05-21"

  3823. msgstr ""

  3824. 

  3825. #: ../../../CHANGELOG.md:2100

  3826. msgid "Hydrogen support"

  3827. msgstr ""

  3828. 

  3829. #: ../../../CHANGELOG.md:2102

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

  3831. msgstr ""

  3832. 

  3833. #: ../../../CHANGELOG.md:2104

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

  3835. msgstr ""

  3836. 

  3837. #: ../../../CHANGELOG.md:2106

  3838. msgid "Additional details are available in [Setting up Hydrogen](docs/configuring-playbook-client-hydrogen.md)."

  3839. msgstr ""

  3840. 

  3841. #: ../../../CHANGELOG.md:2109

  3842. msgid "2021-05-19"

  3843. msgstr ""

  3844. 

  3845. #: ../../../CHANGELOG.md:2111

  3846. msgid "Heisenbridge support"

  3847. msgstr ""

  3848. 

  3849. #: ../../../CHANGELOG.md:2113

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

  3851. msgstr ""

  3852. 

  3853. #: ../../../CHANGELOG.md:2115

  3854. msgid "Additional details are available in [Setting up Heisenbridge bouncer-style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)."

  3855. msgstr ""

  3856. 

  3857. #: ../../../CHANGELOG.md:2118

  3858. msgid "2021-04-16"

  3859. msgstr ""

  3860. 

  3861. #: ../../../CHANGELOG.md:2120

  3862. msgid "Disabling TLSv1 and TLSv1.1 for coturn"

  3863. msgstr ""

  3864. 

  3865. #: ../../../CHANGELOG.md:2122

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

  3867. msgstr ""

  3868. 

  3869. #: ../../../CHANGELOG.md:2124

  3870. msgid "If you need to support old clients, you can re-enable both (or whichever one you need) with the following configuration:"

  3871. msgstr ""

  3872. 

  3873. #: ../../../CHANGELOG.md:2132

  3874. msgid "2021-04-05"

  3875. msgstr ""

  3876. 

  3877. #: ../../../CHANGELOG.md:2134

  3878. msgid "Automated local Postgres backup support"

  3879. msgstr ""

  3880. 

  3881. #: ../../../CHANGELOG.md:2136

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

  3883. msgstr ""

  3884. 

  3885. #: ../../../CHANGELOG.md:2138

  3886. msgid "Additional details are available in [Setting up postgres backup](docs/configuring-playbook-postgres-backup.md)."

  3887. msgstr ""

  3888. 

  3889. #: ../../../CHANGELOG.md:2141

  3890. msgid "2021-04-03"

  3891. msgstr ""

  3892. 

  3893. #: ../../../CHANGELOG.md:2143

  3894. msgid "Mjolnir moderation tool (bot) support"

  3895. msgstr ""

  3896. 

  3897. #: ../../../CHANGELOG.md:2145

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

  3899. msgstr ""

  3900. 

  3901. #: ../../../CHANGELOG.md:2147

  3902. msgid "Additional details are available in [Setting up Mjolnir](docs/configuring-playbook-bot-mjolnir.md)."

  3903. msgstr ""

  3904. 

  3905. #: ../../../CHANGELOG.md:2150

  3906. msgid "2021-03-20"

  3907. msgstr ""

  3908. 

  3909. #: ../../../CHANGELOG.md:2152

  3910. msgid "Sygnal push gateway support"

  3911. msgstr ""

  3912. 

  3913. #: ../../../CHANGELOG.md:2154

  3914. msgid "The playbook can now install the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you."

  3915. msgstr ""

  3916. 

  3917. #: ../../../CHANGELOG.md:2156

  3918. msgid "This is only useful to people who develop/build their own Matrix client applications."

  3919. msgstr ""

  3920. 

  3921. #: ../../../CHANGELOG.md:2158

  3922. msgid "Additional details are available in our [Setting up the Sygnal push gateway](docs/configuring-playbook-sygnal.md) docs."

  3923. msgstr ""

  3924. 

  3925. #: ../../../CHANGELOG.md:2161

  3926. msgid "2021-03-16"

  3927. msgstr ""

  3928. 

  3929. #: ../../../CHANGELOG.md:2163

  3930. msgid "Go-NEB support"

  3931. msgstr ""

  3932. 

  3933. #: ../../../CHANGELOG.md:2165

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

  3935. msgstr ""

  3936. 

  3937. #: ../../../CHANGELOG.md:2167

  3938. msgid "Additional details are available in [Setting up Go-NEB](docs/configuring-playbook-bot-go-neb.md)."

  3939. msgstr ""

  3940. 

  3941. #: ../../../CHANGELOG.md:2170

  3942. msgid "2021-02-19"

  3943. msgstr ""

  3944. 

  3945. #: ../../../CHANGELOG.md:2172

  3946. msgid "GroupMe bridging support via mx-puppet-groupme"

  3947. msgstr ""

  3948. 

  3949. #: ../../../CHANGELOG.md:2174

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

  3951. msgstr ""

  3952. 

  3953. #: ../../../CHANGELOG.md:2176

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

  3955. msgstr ""

  3956. 

  3957. #: ../../../CHANGELOG.md:2178

  3958. msgid "To get started, follow our [Setting up MX Puppet GroupMe](docs/configuring-playbook-bridge-mx-puppet-groupme.md) docs."

  3959. msgstr ""

  3960. 

  3961. #: ../../../CHANGELOG.md:2180

  3962. msgid "Mautrix Instagram bridging support"

  3963. msgstr ""

  3964. 

  3965. #: ../../../CHANGELOG.md:2182

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

  3967. msgstr ""

  3968. 

  3969. #: ../../../CHANGELOG.md:2184

  3970. msgid "Additional details are available in [Setting up Mautrix Instagram bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)."

  3971. msgstr ""

  3972. 

  3973. #: ../../../CHANGELOG.md:2186

  3974. msgid "Synapse workers support"

  3975. msgstr ""

  3976. 

  3977. #: ../../../CHANGELOG.md:2188

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

  3979. msgstr ""

  3980. 

  3981. #: ../../../CHANGELOG.md:2190

  3982. msgid "Having support for workers makes the playbook suitable for larger homeserver deployments."

  3983. msgstr ""

  3984. 

  3985. #: ../../../CHANGELOG.md:2192

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

  3987. msgstr ""

  3988. 

  3989. #: ../../../CHANGELOG.md:2194

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

  3991. msgstr ""

  3992. 

  3993. #: ../../../CHANGELOG.md:2196

  3994. msgid "To enable Synapse workers, follow our [Load balancing with workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) documentation."

  3995. msgstr ""

  3996. 

  3997. #: ../../../CHANGELOG.md:2199

  3998. msgid "2021-02-12"

  3999. msgstr ""

  4000. 

  4001. #: ../../../CHANGELOG.md:2201

  4002. msgid "(Potential Breaking Change) Monitoring/metrics support using Prometheus and Grafana"

  4003. msgstr ""

  4004. 

  4005. #: ../../../CHANGELOG.md:2203

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

  4007. msgstr ""

  4008. 

  4009. #: ../../../CHANGELOG.md:2205

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

  4011. msgstr ""

  4012. 

  4013. #: ../../../CHANGELOG.md:2207

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

  4015. msgstr ""

  4016. 

  4017. #: ../../../CHANGELOG.md:2210

  4018. msgid "2021-01-31"

  4019. msgstr ""

  4020. 

  4021. #: ../../../CHANGELOG.md:2212

  4022. msgid "Etherpad support"

  4023. msgstr ""

  4024. 

  4025. #: ../../../CHANGELOG.md:2214

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

  4027. msgstr ""

  4028. 

  4029. #: ../../../CHANGELOG.md:2216

  4030. msgid "To get it installed, follow [our Etherpad docs page](docs/configuring-playbook-etherpad.md)."

  4031. msgstr ""

  4032. 

  4033. #: ../../../CHANGELOG.md:2219

  4034. msgid "2021-01-22"

  4035. msgstr ""

  4036. 

  4037. #: ../../../CHANGELOG.md:2221

  4038. msgid "(Breaking Change) Postgres changes that require manual intervention"

  4039. msgstr ""

  4040. 

  4041. #: ../../../CHANGELOG.md:2223

  4042. msgid "We've made a lot of changes to our Postgres setup and some manual action is required (described below). Sorry about the hassle."

  4043. msgstr ""

  4044. 

  4045. #: ../../../CHANGELOG.md:2225

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

  4047. msgstr ""

  4048. 

  4049. #: ../../../CHANGELOG.md:2227

  4050. msgid "Why?"

  4051. msgstr ""

  4052. 

  4053. #: ../../../CHANGELOG.md:2229

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

  4055. msgstr ""

  4056. 

  4057. #: ../../../CHANGELOG.md:2230

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

  4059. msgstr ""

  4060. 

  4061. #: ../../../CHANGELOG.md:2231

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

  4063. msgstr ""

  4064. 

  4065. #: ../../../CHANGELOG.md:2232

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

  4067. msgstr ""

  4068. 

  4069. #: ../../../CHANGELOG.md:2233

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

  4071. msgstr ""

  4072. 

  4073. #: ../../../CHANGELOG.md:2234

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

  4075. msgstr ""

  4076. 

  4077. #: ../../../CHANGELOG.md:2236

  4078. msgid "So, this is some **effort to improve security** and to **prepare for a brighter future of having more homeserver options** than just Synapse."

  4079. msgstr ""

  4080. 

  4081. #: ../../../CHANGELOG.md:2238

  4082. msgid "What has really changed?"

  4083. msgstr ""

  4084. 

  4085. #: ../../../CHANGELOG.md:2240

  4086. msgid "the default superuser Postgres username is now `matrix` (used to be `synapse`)"

  4087. msgstr ""

  4088. 

  4089. #: ../../../CHANGELOG.md:2241

  4090. msgid "the default Postgres database is now `matrix` (used to be `homeserver`)"

  4091. msgstr ""

  4092. 

  4093. #: ../../../CHANGELOG.md:2242

  4094. msgid "Synapse's database is now `synapse` (used to be `homeserver`). This is now just another \"additional database\" that the playbook manages for you"

  4095. msgstr ""

  4096. 

  4097. #: ../../../CHANGELOG.md:2243

  4098. msgid "Synapse's user called `synapse` is just a regular user that can only use the `synapse` database (not a superuser anymore)"

  4099. msgstr ""

  4100. 

  4101. #: ../../../CHANGELOG.md:2245

  4102. msgid "What do I do if I'm using the integrated Postgres server (default)?"

  4103. msgstr ""

  4104. 

  4105. #: ../../../CHANGELOG.md:2247

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

  4107. msgstr ""

  4108. 

  4109. #: ../../../CHANGELOG.md:2249

  4110. msgid "To migrate to the new setup, expect a few minutes of downtime, while you follow these steps:"

  4111. msgstr ""

  4112. 

  4113. #: ../../../CHANGELOG.md:2251

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

  4115. msgstr ""

  4116. 

  4117. #: ../../../CHANGELOG.md:2253

  4118. 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!"

  4119. msgstr ""

  4120. 

  4121. #: ../../../CHANGELOG.md:2255

  4122. msgid "Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` file, adding a line like this:"

  4123. msgstr ""

  4124. 

  4125. #: ../../../CHANGELOG.md:2260 ../../../CHANGELOG.md:2272

  4126. msgid "… where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2."

  4127. msgstr ""

  4128. 

  4129. #: ../../../CHANGELOG.md:2262

  4130. msgid "Stop all services: `ansible-playbook -i inventory/hosts setup.yml --tags=stop`"

  4131. msgstr ""

  4132. 

  4133. #: ../../../CHANGELOG.md:2263

  4134. msgid "Log in to the server via SSH. The next commands will be performed there."

  4135. msgstr ""

  4136. 

  4137. #: ../../../CHANGELOG.md:2264

  4138. msgid "Start the Postgres database server: `systemctl start matrix-postgres`"

  4139. msgstr ""

  4140. 

  4141. #: ../../../CHANGELOG.md:2265

  4142. msgid "Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`"

  4143. msgstr ""

  4144. 

  4145. #: ../../../CHANGELOG.md:2266

  4146. msgid "Execute the following query, while making sure to **change the password inside** (**don't forget the ending `;`**):"

  4147. msgstr ""

  4148. 

  4149. #: ../../../CHANGELOG.md:2274

  4150. msgid "Execute the following queries as you see them (no modifications necessary, so you can just **paste them all at once**):"

  4151. msgstr ""

  4152. 

  4153. #: ../../../CHANGELOG.md:2292

  4154. msgid "You may need to press *Enter* after pasting the lines above."

  4155. msgstr ""

  4156. 

  4157. #: ../../../CHANGELOG.md:2294

  4158. msgid "Re-run the playbook normally: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`"

  4159. msgstr ""

  4160. 

  4161. #: ../../../CHANGELOG.md:2296

  4162. msgid "What do I do if I'm using an external Postgres server?"

  4163. msgstr ""

  4164. 

  4165. #: ../../../CHANGELOG.md:2298

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

  4167. msgstr ""

  4168. 

  4169. #: ../../../CHANGELOG.md:2300

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

  4171. msgstr ""

  4172. 

  4173. #: ../../../CHANGELOG.md:2303

  4174. msgid "2021-01-20"

  4175. msgstr ""

  4176. 

  4177. #: ../../../CHANGELOG.md:2305

  4178. msgid "(Breaking Change) The mautrix-facebook bridge now requires a Postgres database"

  4179. msgstr ""

  4180. 

  4181. #: ../../../CHANGELOG.md:2307

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

  4183. msgstr ""

  4184. 

  4185. #: ../../../CHANGELOG.md:2309

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

  4187. msgstr ""

  4188. 

  4189. #: ../../../CHANGELOG.md:2311

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

  4191. msgstr ""

  4192. 

  4193. #: ../../../CHANGELOG.md:2313

  4194. msgid "Whether this change requires your intervention depends mostly on:"

  4195. msgstr ""

  4196. 

  4197. #: ../../../CHANGELOG.md:2314

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

  4199. msgstr ""

  4200. 

  4201. #: ../../../CHANGELOG.md:2315

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

  4203. msgstr ""

  4204. 

  4205. #: ../../../CHANGELOG.md:2317

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

  4207. msgstr ""

  4208. 

  4209. #: ../../../CHANGELOG.md:2319

  4210. msgid "Upgrade path for people NOT running an external Postgres server (default for the playbook)"

  4211. msgstr ""

  4212. 

  4213. #: ../../../CHANGELOG.md:2321

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

  4215. msgstr ""

  4216. 

  4217. #: ../../../CHANGELOG.md:2323

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

  4219. msgstr ""

  4220. 

  4221. #: ../../../CHANGELOG.md:2325

  4222. msgid "Alternatively, [you can stay on SQLite for a little longer](#staying-on-sqlite-for-a-little-longer-temporary-solution)."

  4223. msgstr ""

  4224. 

  4225. #: ../../../CHANGELOG.md:2327

  4226. msgid "Upgrade path for people running an external Postgres server"

  4227. msgstr ""

  4228. 

  4229. #: ../../../CHANGELOG.md:2329

  4230. msgid "For people using the internal Postgres server (the default for the playbook):"

  4231. msgstr ""

  4232. 

  4233. #: ../../../CHANGELOG.md:2330

  4234. msgid "we automatically create an additional `matrix_mautrix_facebook` Postgres database and credentials to access it"

  4235. msgstr ""

  4236. 

  4237. #: ../../../CHANGELOG.md:2331

  4238. msgid "we automatically adjust the bridge's `matrix_mautrix_facebook_database_*` variables to point the bridge to that Postgres database"

  4239. msgstr ""

  4240. 

  4241. #: ../../../CHANGELOG.md:2332

  4242. msgid "we use [pgloader](https://pgloader.io/) to automatically import the existing SQLite data for the bridge into the `matrix_mautrix_facebook` Postgres database"

  4243. msgstr ""

  4244. 

  4245. #: ../../../CHANGELOG.md:2334

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

  4247. msgstr ""

  4248. 

  4249. #: ../../../CHANGELOG.md:2336

  4250. msgid "You have 3 ways to proceed:"

  4251. msgstr ""

  4252. 

  4253. #: ../../../CHANGELOG.md:2338

  4254. msgid "contribute to the playbook to make this possible (difficult)"

  4255. msgstr ""

  4256. 

  4257. #: ../../../CHANGELOG.md:2339

  4258. msgid "or, do the migration \"steps\" manually:"

  4259. msgstr ""

  4260. 

  4261. #: ../../../CHANGELOG.md:2340

  4262. msgid "stop the bridge (`systemctl stop matrix-mautrix-facebook`)"

  4263. msgstr ""

  4264. 

  4265. #: ../../../CHANGELOG.md:2341

  4266. msgid "create a new `matrix_mautrix_facebook` Postgres database for it"

  4267. msgstr ""

  4268. 

  4269. #: ../../../CHANGELOG.md:2342

  4270. msgid "run [pgloader](https://pgloader.io/) manually (we import this bridge's data using default settings and it works well)"

  4271. msgstr ""

  4272. 

  4273. #: ../../../CHANGELOG.md:2343

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

  4275. msgstr ""

  4276. 

  4277. #: ../../../CHANGELOG.md:2344

  4278. msgid "switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: 'postgres'` in your `vars.yml` file)"

  4279. msgstr ""

  4280. 

  4281. #: ../../../CHANGELOG.md:2345

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

  4283. msgstr ""

  4284. 

  4285. #: ../../../CHANGELOG.md:2346

  4286. msgid "send a `login` message to the Facebook bridge bot again"

  4287. msgstr ""

  4288. 

  4289. #: ../../../CHANGELOG.md:2347

  4290. msgid "or, [stay on SQLite for a little longer (temporary solution)](#staying-on-sqlite-for-a-little-longer-temporary-solution)"

  4291. msgstr ""

  4292. 

  4293. #: ../../../CHANGELOG.md:2349

  4294. msgid "Staying on SQLite for a little longer (temporary solution)"

  4295. msgstr ""

  4296. 

  4297. #: ../../../CHANGELOG.md:2351

  4298. msgid "To keep using this bridge with SQLite for a little longer (**not recommended**), use the following configuration in your `vars.yml` file:"

  4299. msgstr ""

  4300. 

  4301. #: ../../../CHANGELOG.md:2361

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

  4303. msgstr ""

  4304. 

  4305. #: ../../../CHANGELOG.md:2364

  4306. msgid "2021-01-17"

  4307. msgstr ""

  4308. 

  4309. #: ../../../CHANGELOG.md:2366

  4310. msgid "matrix-corporal goes 2.0"

  4311. msgstr ""

  4312. 

  4313. #: ../../../CHANGELOG.md:2368

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

  4315. msgstr ""

  4316. 

  4317. #: ../../../CHANGELOG.md:2370

  4318. msgid "No manual intervention is required in the common case."

  4319. msgstr ""

  4320. 

  4321. #: ../../../CHANGELOG.md:2372

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

  4323. msgstr ""

  4324. 

  4325. #: ../../../CHANGELOG.md:2375

  4326. msgid "2021-01-14"

  4327. msgstr ""

  4328. 

  4329. #: ../../../CHANGELOG.md:2377

  4330. msgid "Moving from cronjobs to systemd timers"

  4331. msgstr ""

  4332. 

  4333. #: ../../../CHANGELOG.md:2379

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

  4335. msgstr ""

  4336. 

  4337. #: ../../../CHANGELOG.md:2381

  4338. msgid "The largest benefit of this is that we no longer require you to install a cron daemon, thus simplifying our install procedure."

  4339. msgstr ""

  4340. 

  4341. #: ../../../CHANGELOG.md:2383

  4342. msgid "The playbook will migrate you from cronjobs to systemd timers automatically. This is just a heads up."

  4343. msgstr ""

  4344. 

  4345. #: ../../../CHANGELOG.md:2386

  4346. msgid "2021-01-08"

  4347. msgstr ""

  4348. 

  4349. #: ../../../CHANGELOG.md:2388

  4350. msgid "(Breaking Change) New SSL configuration"

  4351. msgstr ""

  4352. 

  4353. #: ../../../CHANGELOG.md:2390

  4354. msgid "SSL configuration (protocols, ciphers) can now be more easily controlled thanks to us making use of configuration presets."

  4355. msgstr ""

  4356. 

  4357. #: ../../../CHANGELOG.md:2392

  4358. msgid "We define a few presets (old, intermediate, modern), following the [Mozilla SSL Configuration Generator](https://ssl-config.mozilla.org/#server=nginx)."

  4359. msgstr ""

  4360. 

  4361. #: ../../../CHANGELOG.md:2394

  4362. msgid "A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is used (defaults to `\"intermediate\"`)."

  4363. msgstr ""

  4364. 

  4365. #: ../../../CHANGELOG.md:2396

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

  4367. msgstr ""

  4368. 

  4369. #: ../../../CHANGELOG.md:2398

  4370. msgid "To revert to the old behaviour, set the following variables:"

  4371. msgstr ""

  4372. 

  4373. #: ../../../CHANGELOG.md:2405

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

  4375. msgstr ""

  4376. 

  4377. #: ../../../CHANGELOG.md:2408

  4378. msgid "2021-01-03"

  4379. msgstr ""

  4380. 

  4381. #: ../../../CHANGELOG.md:2410

  4382. msgid "Signal bridging support via mautrix-signal"

  4383. msgstr ""

  4384. 

  4385. #: ../../../CHANGELOG.md:2412

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

  4387. msgstr ""

  4388. 

  4389. #: ../../../CHANGELOG.md:2414

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

  4391. msgstr ""

  4392. 

  4393. #: ../../../CHANGELOG.md:2417

  4394. msgid "2020-12-23"

  4395. msgstr ""

  4396. 

  4397. #: ../../../CHANGELOG.md:2419

  4398. msgid "The big move to all-on-Postgres (potentially dangerous)"

  4399. msgstr ""

  4400. 

  4401. #: ../../../CHANGELOG.md:2421

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

  4403. msgstr ""

  4404. 

  4405. #: ../../../CHANGELOG.md:2423

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

  4407. msgstr ""

  4408. 

  4409. #: ../../../CHANGELOG.md:2425

  4410. 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!"

  4411. msgstr ""

  4412. 

  4413. #: ../../../CHANGELOG.md:2427

  4414. msgid "Moving all services to Postgres brings a few **benefits** to us:"

  4415. msgstr ""

  4416. 

  4417. #: ../../../CHANGELOG.md:2429

  4418. msgid "**improved performance**"

  4419. msgstr ""

  4420. 

  4421. #: ../../../CHANGELOG.md:2430

  4422. msgid "**improved compatibility**. Most bridges are deprecating SQLite/nedb support or offer less features when not on Postgres."

  4423. msgstr ""

  4424. 

  4425. #: ../../../CHANGELOG.md:2431

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

  4427. msgstr ""

  4428. 

  4429. #: ../../../CHANGELOG.md:2432

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

  4431. msgstr ""

  4432. 

  4433. #: ../../../CHANGELOG.md:2434

  4434. msgid "Key takeway"

  4435. msgstr ""

  4436. 

  4437. #: ../../../CHANGELOG.md:2436

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

  4439. msgstr ""

  4440. 

  4441. #: ../../../CHANGELOG.md:2438

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

  4443. msgstr ""

  4444. 

  4445. #: ../../../CHANGELOG.md:2440

  4446. msgid "Opting-out of the Postgres migration"

  4447. msgstr ""

  4448. 

  4449. #: ../../../CHANGELOG.md:2442

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

  4451. msgstr ""

  4452. 

  4453. #: ../../../CHANGELOG.md:2444

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

  4455. msgstr ""

  4456. 

  4457. #: ../../../CHANGELOG.md:2446

  4458. msgid "Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them."

  4459. msgstr ""

  4460. 

  4461. #: ../../../CHANGELOG.md:2448

  4462. msgid "Going back to SQLite/nedb if things went wrong"

  4463. msgstr ""

  4464. 

  4465. #: ../../../CHANGELOG.md:2450

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

  4467. msgstr ""

  4468. 

  4469. #: ../../../CHANGELOG.md:2452

  4470. msgid "stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"

  4471. msgstr ""

  4472. 

  4473. #: ../../../CHANGELOG.md:2453

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

  4475. msgstr ""

  4476. 

  4477. #: ../../../CHANGELOG.md:2454

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

  4479. msgstr ""

  4480. 

  4481. #: ../../../CHANGELOG.md:2455

  4482. msgid "re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`)"

  4483. msgstr ""

  4484. 

  4485. #: ../../../CHANGELOG.md:2456

  4486. msgid "[get in touch](README.md#support) with us"

  4487. msgstr ""

  4488. 

  4489. #: ../../../CHANGELOG.md:2458

  4490. msgid "2020-12-11"

  4491. msgstr ""

  4492. 

  4493. #: ../../../CHANGELOG.md:2460

  4494. msgid "synapse-janitor support removed"

  4495. msgstr ""

  4496. 

  4497. #: ../../../CHANGELOG.md:2462

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

  4499. msgstr ""

  4500. 

  4501. #: ../../../CHANGELOG.md:2464

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

  4503. msgstr ""

  4504. 

  4505. #: ../../../CHANGELOG.md:2466

  4506. msgid "Docker 20.10 is here"

  4507. msgstr ""

  4508. 

  4509. #: ../../../CHANGELOG.md:2468

  4510. msgid "(No need to do anything special in relation to this. Just something to keep in mind)"

  4511. msgstr ""

  4512. 

  4513. #: ../../../CHANGELOG.md:2470

  4514. msgid "Docker 20.10 got released recently and your server will likely get it the next time you update."

  4515. msgstr ""

  4516. 

  4517. #: ../../../CHANGELOG.md:2472

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

  4519. msgstr ""

  4520. 

  4521. #: ../../../CHANGELOG.md:2475

  4522. msgid "2020-12-08"

  4523. msgstr ""

  4524. 

  4525. #: ../../../CHANGELOG.md:2477

  4526. msgid "openid APIs exposed by default on the federation port when federation disabled"

  4527. msgstr ""

  4528. 

  4529. #: ../../../CHANGELOG.md:2479

  4530. msgid "We've changed some defaults. People running with our default configuration (federation enabled), are not affected at all."

  4531. msgstr ""

  4532. 

  4533. #: ../../../CHANGELOG.md:2481

  4534. msgid "If you are running an unfederated server (`matrix_synapse_federation_enabled: false`), this may be of interest to you."

  4535. msgstr ""

  4536. 

  4537. #: ../../../CHANGELOG.md:2483

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

  4539. msgstr ""

  4540. 

  4541. #: ../../../CHANGELOG.md:2486

  4542. msgid "2020-11-27"

  4543. msgstr ""

  4544. 

  4545. #: ../../../CHANGELOG.md:2488

  4546. msgid "Recent Jitsi updates may require configuration changes"

  4547. msgstr ""

  4548. 

  4549. #: ../../../CHANGELOG.md:2490

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

  4551. msgstr ""

  4552. 

  4553. #: ../../../CHANGELOG.md:2492

  4554. msgid "**If you use our default Jitsi settings, you won't have to do anything.**"

  4555. msgstr ""

  4556. 

  4557. #: ../../../CHANGELOG.md:2494

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

  4559. msgstr ""

  4560. 

  4561. #: ../../../CHANGELOG.md:2496

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

  4563. msgstr ""

  4564. 

  4565. #: ../../../CHANGELOG.md:2498

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

  4567. msgstr ""

  4568. 

  4569. #: ../../../CHANGELOG.md:2501

  4570. msgid "2020-11-23"

  4571. msgstr ""

  4572. 

  4573. #: ../../../CHANGELOG.md:2503 ../../../CHANGELOG.md:2511

  4574. msgid "Breaking change matrix-sms-bridge"

  4575. msgstr ""

  4576. 

  4577. #: ../../../CHANGELOG.md:2505

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

  4579. msgstr ""

  4580. 

  4581. #: ../../../CHANGELOG.md:2507

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

  4583. msgstr ""

  4584. 

  4585. #: ../../../CHANGELOG.md:2509

  4586. msgid "2020-11-13"

  4587. msgstr ""

  4588. 

  4589. #: ../../../CHANGELOG.md:2513

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

  4591. msgstr ""

  4592. 

  4593. #: ../../../CHANGELOG.md:2515

  4594. msgid "Add the following to your `vars.yml` file: `matrix_sms_bridge_container_extra_arguments=['--env SPRING_PROFILES_ACTIVE=initialsync']`"

  4595. msgstr ""

  4596. 

  4597. #: ../../../CHANGELOG.md:2516

  4598. msgid "Login to your host shell and remove old systemd file from your host: `rm /etc/systemd/system/matrix-sms-bridge-database.service`"

  4599. msgstr ""

  4600. 

  4601. #: ../../../CHANGELOG.md:2517

  4602. msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-sms-bridge,start`"

  4603. msgstr ""

  4604. 

  4605. #: ../../../CHANGELOG.md:2518

  4606. msgid "Login to your host shell and check the logs with `journalctl -u matrix-sms-bridge` until the sync finished."

  4607. msgstr ""

  4608. 

  4609. #: ../../../CHANGELOG.md:2519

  4610. msgid "Remove the var from the first step."

  4611. msgstr ""

  4612. 

  4613. #: ../../../CHANGELOG.md:2520

  4614. msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`."

  4615. msgstr ""

  4616. 

  4617. #: ../../../CHANGELOG.md:2522

  4618. msgid "2020-11-10"

  4619. msgstr ""

  4620. 

  4621. #: ../../../CHANGELOG.md:2524

  4622. msgid "Dynamic DNS support"

  4623. msgstr ""

  4624. 

  4625. #: ../../../CHANGELOG.md:2526

  4626. msgid "Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook can now manage Dynamic DNS for you using [ddclient](https://ddclient.net/)."

  4627. msgstr ""

  4628. 

  4629. #: ../../../CHANGELOG.md:2528

  4630. msgid "To learn more, follow our [Dynamic DNS docs page](docs/configuring-playbook-dynamic-dns.md)."

  4631. msgstr ""

  4632. 

  4633. #: ../../../CHANGELOG.md:2531

  4634. msgid "2020-10-28"

  4635. msgstr ""

  4636. 

  4637. #: ../../../CHANGELOG.md:2533

  4638. msgid "(Compatibility Break) https://matrix.example.com/ now redirects to https://element.example.com/"

  4639. msgstr ""

  4640. 

  4641. #: ../../../CHANGELOG.md:2535

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

  4643. msgstr ""

  4644. 

  4645. #: ../../../CHANGELOG.md:2537

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

  4647. msgstr ""

  4648. 

  4649. #: ../../../CHANGELOG.md:2539

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

  4651. msgstr ""

  4652. 

  4653. #: ../../../CHANGELOG.md:2541

  4654. 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: \"\"`)."

  4655. msgstr ""

  4656. 

  4657. #: ../../../CHANGELOG.md:2544

  4658. msgid "2020-10-26"

  4659. msgstr ""

  4660. 

  4661. #: ../../../CHANGELOG.md:2546

  4662. msgid "(Compatibility Break) /_synapse/admin is no longer publicly exposed by default"

  4663. msgstr ""

  4664. 

  4665. #: ../../../CHANGELOG.md:2548

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

  4667. msgstr ""

  4668. 

  4669. #: ../../../CHANGELOG.md:2550

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

  4671. msgstr ""

  4672. 

  4673. #: ../../../CHANGELOG.md:2552

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

  4675. msgstr ""

  4676. 

  4677. #: ../../../CHANGELOG.md:2559

  4678. msgid "2020-10-02"

  4679. msgstr ""

  4680. 

  4681. #: ../../../CHANGELOG.md:2561

  4682. msgid "Minimum Ansible version raised to v2.7.0"

  4683. msgstr ""

  4684. 

  4685. #: ../../../CHANGELOG.md:2563

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

  4687. msgstr ""

  4688. 

  4689. #: ../../../CHANGELOG.md:2565

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

  4691. msgstr ""

  4692. 

  4693. #: ../../../CHANGELOG.md:2567

  4694. msgid "Our [Ansible docs page](docs/ansible.md) contains information on how to run a more up-to-date version of Ansible."

  4695. msgstr ""

  4696. 

  4697. #: ../../../CHANGELOG.md:2570

  4698. msgid "2020-10-01"

  4699. msgstr ""

  4700. 

  4701. #: ../../../CHANGELOG.md:2572

  4702. msgid "Postgres 13 support"

  4703. msgstr ""

  4704. 

  4705. #: ../../../CHANGELOG.md:2574

  4706. msgid "The playbook now installs [Postgres 13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) by default."

  4707. msgstr ""

  4708. 

  4709. #: ../../../CHANGELOG.md:2576

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

  4711. msgstr ""

  4712. 

  4713. #: ../../../CHANGELOG.md:2578

  4714. msgid "2020-09-01"

  4715. msgstr ""

  4716. 

  4717. #: ../../../CHANGELOG.md:2580

  4718. msgid "matrix-registration support"

  4719. msgstr ""

  4720. 

  4721. #: ../../../CHANGELOG.md:2582

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

  4723. msgstr ""

  4724. 

  4725. #: ../../../CHANGELOG.md:2584

  4726. msgid "See our [Setting up matrix-registration](docs/configuring-playbook-matrix-registration.md) documentation page to get started."

  4727. msgstr ""

  4728. 

  4729. #: ../../../CHANGELOG.md:2587

  4730. msgid "2020-08-21"

  4731. msgstr ""

  4732. 

  4733. #: ../../../CHANGELOG.md:2589

  4734. msgid "rust-synapse-compress-state support"

  4735. msgstr ""

  4736. 

  4737. #: ../../../CHANGELOG.md:2591

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

  4739. msgstr ""

  4740. 

  4741. #: ../../../CHANGELOG.md:2593

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

  4743. msgstr ""

  4744. 

  4745. #: ../../../CHANGELOG.md:2596

  4746. msgid "2020-07-22"

  4747. msgstr ""

  4748. 

  4749. #: ../../../CHANGELOG.md:2598

  4750. msgid "Synapse Admin support"

  4751. msgstr ""

  4752. 

  4753. #: ../../../CHANGELOG.md:2600

  4754. msgid "The playbook can now help you set up [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin)."

  4755. msgstr ""

  4756. 

  4757. #: ../../../CHANGELOG.md:2602

  4758. msgid "See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-admin.md) documentation to get started."

  4759. msgstr ""

  4760. 

  4761. #: ../../../CHANGELOG.md:2605

  4762. msgid "2020-07-20"

  4763. msgstr ""

  4764. 

  4765. #: ../../../CHANGELOG.md:2607

  4766. msgid "matrix-reminder-bot support"

  4767. msgstr ""

  4768. 

  4769. #: ../../../CHANGELOG.md:2609

  4770. msgid "The playbook can now help you set up [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)."

  4771. msgstr ""

  4772. 

  4773. #: ../../../CHANGELOG.md:2611

  4774. msgid "See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-matrix-reminder-bot.md) documentation to get started."

  4775. msgstr ""

  4776. 

  4777. #: ../../../CHANGELOG.md:2614

  4778. msgid "2020-07-17"

  4779. msgstr ""

  4780. 

  4781. #: ../../../CHANGELOG.md:2616

  4782. msgid "(Compatibility Break) Riot is now Element"

  4783. msgstr ""

  4784. 

  4785. #: ../../../CHANGELOG.md:2618

  4786. msgid "As per the official announcement, [Riot has been rebraned to Element](https://element.io/blog/welcome-to-element/)."

  4787. msgstr ""

  4788. 

  4789. #: ../../../CHANGELOG.md:2620

  4790. msgid "The playbook follows suit. Existing installations have a few options for how to handle this."

  4791. msgstr ""

  4792. 

  4793. #: ../../../CHANGELOG.md:2622

  4794. msgid "See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md#migrating-to-element) documentation page for more details."

  4795. msgstr ""

  4796. 

  4797. #: ../../../CHANGELOG.md:2625

  4798. msgid "2020-07-03"

  4799. msgstr ""

  4800. 

  4801. #: ../../../CHANGELOG.md:2627

  4802. msgid "Steam bridging support via mx-puppet-steam"

  4803. msgstr ""

  4804. 

  4805. #: ../../../CHANGELOG.md:2629

  4806. 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://github.com/icewind1991/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."

  4807. msgstr ""

  4808. 

  4809. #: ../../../CHANGELOG.md:2632

  4810. msgid "2020-07-01"

  4811. msgstr ""

  4812. 

  4813. #: ../../../CHANGELOG.md:2634

  4814. msgid "Discord bridging support via mx-puppet-discord"

  4815. msgstr ""

  4816. 

  4817. #: ../../../CHANGELOG.md:2636

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

  4819. msgstr ""

  4820. 

  4821. #: ../../../CHANGELOG.md:2638

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

  4823. msgstr ""

  4824. 

  4825. #: ../../../CHANGELOG.md:2641

  4826. msgid "2020-06-30"

  4827. msgstr ""

  4828. 

  4829. #: ../../../CHANGELOG.md:2643

  4830. msgid "Instagram and Twitter bridging support"

  4831. msgstr ""

  4832. 

  4833. #: ../../../CHANGELOG.md:2645

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

  4835. msgstr ""

  4836. 

  4837. #: ../../../CHANGELOG.md:2647

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

  4839. msgstr ""

  4840. 

  4841. #: ../../../CHANGELOG.md:2650

  4842. msgid "2020-06-28"

  4843. msgstr ""

  4844. 

  4845. #: ../../../CHANGELOG.md:2652

  4846. msgid "(Post Mortem / fixed Security Issue) Re-enabling User Directory search powered by the ma1sd Identity Server"

  4847. msgstr ""

  4848. 

  4849. #: ../../../CHANGELOG.md:2654 ../../../CHANGELOG.md:2683

  4850. msgid "User Directory search requests used to go to the ma1sd identity server by default, which queried its own stores and the Synapse database."

  4851. msgstr ""

  4852. 

  4853. #: ../../../CHANGELOG.md:2656

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

  4855. msgstr ""

  4856. 

  4857. #: ../../../CHANGELOG.md:2658

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

  4859. msgstr ""

  4860. 

  4861. #: ../../../CHANGELOG.md:2660

  4862. msgid "As always, re-running the playbook is enough to get the updated bits."

  4863. msgstr ""

  4864. 

  4865. #: ../../../CHANGELOG.md:2662

  4866. msgid "2020-06-11"

  4867. msgstr ""

  4868. 

  4869. #: ../../../CHANGELOG.md:2664

  4870. msgid "SMS bridging requires db reset"

  4871. msgstr ""

  4872. 

  4873. #: ../../../CHANGELOG.md:2666

  4874. 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 requried var `matrix_sms_bridge_default_region`."

  4875. msgstr ""

  4876. 

  4877. #: ../../../CHANGELOG.md:2668

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

  4879. msgstr ""

  4880. 

  4881. #: ../../../CHANGELOG.md:2670

  4882. msgid "2020-06-05"

  4883. msgstr ""

  4884. 

  4885. #: ../../../CHANGELOG.md:2672

  4886. msgid "SMS bridging support"

  4887. msgstr ""

  4888. 

  4889. #: ../../../CHANGELOG.md:2674

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

  4891. msgstr ""

  4892. 

  4893. #: ../../../CHANGELOG.md:2676

  4894. msgid "See our [Setting up Matrix SMS bridging](docs/configuring-playbook-bridge-matrix-bridge-sms.md) documentation page for getting started."

  4895. msgstr ""

  4896. 

  4897. #: ../../../CHANGELOG.md:2679

  4898. msgid "2020-05-19"

  4899. msgstr ""

  4900. 

  4901. #: ../../../CHANGELOG.md:2681

  4902. msgid "(Compatibility Break / Security Issue) Disabling User Directory search powered by the ma1sd Identity Server"

  4903. msgstr ""

  4904. 

  4905. #: ../../../CHANGELOG.md:2685

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

  4907. msgstr ""

  4908. 

  4909. #: ../../../CHANGELOG.md:2687

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

  4911. msgstr ""

  4912. 

  4913. #: ../../../CHANGELOG.md:2689

  4914. 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 }}\"`"

  4915. msgstr ""

  4916. 

  4917. #: ../../../CHANGELOG.md:2692

  4918. msgid "2020-04-28"

  4919. msgstr ""

  4920. 

  4921. #: ../../../CHANGELOG.md:2694

  4922. msgid "Newer IRC bridge (with potential breaking change)"

  4923. msgstr ""

  4924. 

  4925. #: ../../../CHANGELOG.md:2696

  4926. 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 accoring 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."

  4927. msgstr ""

  4928. 

  4929. #: ../../../CHANGELOG.md:2705

  4930. msgid "2020-04-23"

  4931. msgstr ""

  4932. 

  4933. #: ../../../CHANGELOG.md:2707 ../../../CHANGELOG.md:2938

  4934. msgid "Slack bridging support"

  4935. msgstr ""

  4936. 

  4937. #: ../../../CHANGELOG.md:2709

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

  4939. msgstr ""

  4940. 

  4941. #: ../../../CHANGELOG.md:2711

  4942. msgid "See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-bridge-mx-puppet-slack.md) documentation page for getting started."

  4943. msgstr ""

  4944. 

  4945. #: ../../../CHANGELOG.md:2714

  4946. msgid "2020-04-09"

  4947. msgstr ""

  4948. 

  4949. #: ../../../CHANGELOG.md:2716

  4950. msgid "Skype bridging support"

  4951. msgstr ""

  4952. 

  4953. #: ../../../CHANGELOG.md:2718

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

  4955. msgstr ""

  4956. 

  4957. #: ../../../CHANGELOG.md:2720

  4958. msgid "See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md) documentation page for getting started."

  4959. msgstr ""

  4960. 

  4961. #: ../../../CHANGELOG.md:2723

  4962. msgid "2020-04-05"

  4963. msgstr ""

  4964. 

  4965. #: ../../../CHANGELOG.md:2725

  4966. msgid "Private Jitsi support"

  4967. msgstr ""

  4968. 

  4969. #: ../../../CHANGELOG.md:2727

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

  4971. msgstr ""

  4972. 

  4973. #: ../../../CHANGELOG.md:2729

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

  4975. msgstr ""

  4976. 

  4977. #: ../../../CHANGELOG.md:2731

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

  4979. msgstr ""

  4980. 

  4981. #: ../../../CHANGELOG.md:2734

  4982. msgid "2020-04-03"

  4983. msgstr ""

  4984. 

  4985. #: ../../../CHANGELOG.md:2736

  4986. msgid "(Potential Backward Compatibility Break) ma1sd replaces mxisd"

  4987. msgstr ""

  4988. 

  4989. #: ../../../CHANGELOG.md:2738

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

  4991. msgstr ""

  4992. 

  4993. #: ../../../CHANGELOG.md:2740

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

  4995. msgstr ""

  4996. 

  4997. #: ../../../CHANGELOG.md:2742

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

  4999. msgstr ""

  5000. 

  5001. #: ../../../CHANGELOG.md:2745

  5002. msgid "2020-03-29"

  5003. msgstr ""

  5004. 

  5005. #: ../../../CHANGELOG.md:2747

  5006. msgid "Archlinux support"

  5007. msgstr ""

  5008. 

  5009. #: ../../../CHANGELOG.md:2749

  5010. msgid "Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts, the playbook now supports installing to an [Archlinux](https://www.archlinux.org/) server."

  5011. msgstr ""

  5012. 

  5013. #: ../../../CHANGELOG.md:2752

  5014. msgid "2020-03-24"

  5015. msgstr ""

  5016. 

  5017. #: ../../../CHANGELOG.md:2754

  5018. msgid "Jitsi support"

  5019. msgstr ""

  5020. 

  5021. #: ../../../CHANGELOG.md:2756

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

  5023. msgstr ""

  5024. 

  5025. #: ../../../CHANGELOG.md:2758

  5026. msgid "See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to get started."

  5027. msgstr ""

  5028. 

  5029. #: ../../../CHANGELOG.md:2761

  5030. msgid "2020-03-15"

  5031. msgstr ""

  5032. 

  5033. #: ../../../CHANGELOG.md:2763

  5034. msgid "Raspberry Pi support"

  5035. msgstr ""

  5036. 

  5037. #: ../../../CHANGELOG.md:2765

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

  5039. msgstr ""

  5040. 

  5041. #: ../../../CHANGELOG.md:2767

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

  5043. msgstr ""

  5044. 

  5045. #: ../../../CHANGELOG.md:2770

  5046. msgid "2020-02-26"

  5047. msgstr ""

  5048. 

  5049. #: ../../../CHANGELOG.md:2772

  5050. msgid "Riot-web themes are here"

  5051. msgstr ""

  5052. 

  5053. #: ../../../CHANGELOG.md:2774

  5054. msgid "The playbook now makes it easy to install custom riot-web themes."

  5055. msgstr ""

  5056. 

  5057. #: ../../../CHANGELOG.md:2776

  5058. msgid "To learn more, take a look at our [riot-web documentation on Themes](docs/configuring-playbook-riot-web.md#themes)."

  5059. msgstr ""

  5060. 

  5061. #: ../../../CHANGELOG.md:2779

  5062. msgid "2020-02-24"

  5063. msgstr ""

  5064. 

  5065. #: ../../../CHANGELOG.md:2781

  5066. msgid "Customize the server name in Riot's login page"

  5067. msgstr ""

  5068. 

  5069. #: ../../../CHANGELOG.md:2783

  5070. msgid "You can now customize the server name string that Riot-web displays in its login page."

  5071. msgstr ""

  5072. 

  5073. #: ../../../CHANGELOG.md:2785

  5074. msgid "These playbook variables, with these default values, have been added:"

  5075. msgstr ""

  5076. 

  5077. #: ../../../CHANGELOG.md:2791

  5078. 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\"."

  5079. msgstr ""

  5080. 

  5081. #: ../../../CHANGELOG.md:2793

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

  5083. msgstr ""

  5084. 

  5085. #: ../../../CHANGELOG.md:2796

  5086. msgid "2020-01-30"

  5087. msgstr ""

  5088. 

  5089. #: ../../../CHANGELOG.md:2798

  5090. msgid "Disabling TLSv1.1"

  5091. msgstr ""

  5092. 

  5093. #: ../../../CHANGELOG.md:2800

  5094. msgid "To improve security, we've removed TLSv1.1 support from our default matrix-nginx-proxy configuration."

  5095. msgstr ""

  5096. 

  5097. #: ../../../CHANGELOG.md:2802

  5098. 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\"`"

  5099. msgstr ""

  5100. 

  5101. #: ../../../CHANGELOG.md:2805

  5102. msgid "2020-01-21"

  5103. msgstr ""

  5104. 

  5105. #: ../../../CHANGELOG.md:2807

  5106. msgid "Postgres collation changes (action required!)"

  5107. msgstr ""

  5108. 

  5109. #: ../../../CHANGELOG.md:2809

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

  5111. msgstr ""

  5112. 

  5113. #: ../../../CHANGELOG.md:2811

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

  5115. msgstr ""

  5116. 

  5117. #: ../../../CHANGELOG.md:2813

  5118. msgid "To avoid future problems, we recommend that you run the following command:"

  5119. msgstr ""

  5120. 

  5121. #: ../../../CHANGELOG.md:2819

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

  5123. msgstr ""

  5124. 

  5125. #: ../../../CHANGELOG.md:2822

  5126. msgid "2020-01-14"

  5127. msgstr ""

  5128. 

  5129. #: ../../../CHANGELOG.md:2824

  5130. msgid "Added support for Appservice Webhooks"

  5131. msgstr ""

  5132. 

  5133. #: ../../../CHANGELOG.md:2826

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

  5135. msgstr ""

  5136. 

  5137. #: ../../../CHANGELOG.md:2828

  5138. msgid "Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-playbook-bridge-appservice-webhooks.md)."

  5139. msgstr ""

  5140. 

  5141. #: ../../../CHANGELOG.md:2831

  5142. msgid "2020-01-12"

  5143. msgstr ""

  5144. 

  5145. #: ../../../CHANGELOG.md:2833

  5146. msgid "Added support for automatic Double Puppeting for all Mautrix bridges"

  5147. msgstr ""

  5148. 

  5149. #: ../../../CHANGELOG.md:2835

  5150. msgid "Double Puppeting can now be easily enabled for all Mautrix bridges supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)."

  5151. msgstr ""

  5152. 

  5153. #: ../../../CHANGELOG.md:2837

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

  5155. msgstr ""

  5156. 

  5157. #: ../../../CHANGELOG.md:2839

  5158. msgid "To get started, following the playbook's documentation for the bridge you'd like to configure."

  5159. msgstr ""

  5160. 

  5161. #: ../../../CHANGELOG.md:2842

  5162. msgid "2019-12-06"

  5163. msgstr ""

  5164. 

  5165. #: ../../../CHANGELOG.md:2844

  5166. msgid "Added support for an alternative method for using another webserver"

  5167. msgstr ""

  5168. 

  5169. #: ../../../CHANGELOG.md:2846

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

  5171. msgstr ""

  5172. 

  5173. #: ../../../CHANGELOG.md:2848

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

  5175. msgstr ""

  5176. 

  5177. #: ../../../CHANGELOG.md:2850

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

  5179. msgstr ""

  5180. 

  5181. #: ../../../CHANGELOG.md:2853

  5182. msgid "2019-11-10"

  5183. msgstr ""

  5184. 

  5185. #: ../../../CHANGELOG.md:2855

  5186. msgid "Tightened security around room directory publishing"

  5187. msgstr ""

  5188. 

  5189. #: ../../../CHANGELOG.md:2857

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

  5191. msgstr ""

  5192. 

  5193. #: ../../../CHANGELOG.md:2859

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

  5195. msgstr ""

  5196. 

  5197. #: ../../../CHANGELOG.md:2861

  5198. msgid "As with anything else, these new defaults can be overriden by changing the `matrix_synapse_allow_public_rooms_without_auth` and `matrix_synapse_allow_public_rooms_over_federation` variables, respectively."

  5199. msgstr ""

  5200. 

  5201. #: ../../../CHANGELOG.md:2864

  5202. msgid "2019-10-05"

  5203. msgstr ""

  5204. 

  5205. #: ../../../CHANGELOG.md:2866

  5206. msgid "Improved Postgres upgrading/importing"

  5207. msgstr ""

  5208. 

  5209. #: ../../../CHANGELOG.md:2868

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

  5211. msgstr ""

  5212. 

  5213. #: ../../../CHANGELOG.md:2870

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

  5215. msgstr ""

  5216. 

  5217. #: ../../../CHANGELOG.md:2872

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

  5219. msgstr ""

  5220. 

  5221. #: ../../../CHANGELOG.md:2874

  5222. msgid "Additionally, Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) now uses gzipped dump files by default, to minimize disk space usage."

  5223. msgstr ""

  5224. 

  5225. #: ../../../CHANGELOG.md:2877

  5226. msgid "2019-10-04"

  5227. msgstr ""

  5228. 

  5229. #: ../../../CHANGELOG.md:2879

  5230. msgid "Postgres 12 support"

  5231. msgstr ""

  5232. 

  5233. #: ../../../CHANGELOG.md:2881

  5234. msgid "The playbook now installs [Postgres 12](https://www.postgresql.org/about/news/1976/) by default."

  5235. msgstr ""

  5236. 

  5237. #: ../../../CHANGELOG.md:2883

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

  5239. msgstr ""

  5240. 

  5241. #: ../../../CHANGELOG.md:2886

  5242. msgid "2019-10-03"

  5243. msgstr ""

  5244. 

  5245. #: ../../../CHANGELOG.md:2888

  5246. msgid "Synapse 1.4.0"

  5247. msgstr ""

  5248. 

  5249. #: ../../../CHANGELOG.md:2890

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

  5251. msgstr ""

  5252. 

  5253. #: ../../../CHANGELOG.md:2892

  5254. 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: ~`)."

  5255. msgstr ""

  5256. 

  5257. #: ../../../CHANGELOG.md:2894

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

  5259. msgstr ""

  5260. 

  5261. #: ../../../CHANGELOG.md:2896

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

  5263. msgstr ""

  5264. 

  5265. #: ../../../CHANGELOG.md:2899

  5266. msgid "2019-09-09"

  5267. msgstr ""

  5268. 

  5269. #: ../../../CHANGELOG.md:2901

  5270. msgid "Synapse Simple Antispam support"

  5271. msgstr ""

  5272. 

  5273. #: ../../../CHANGELOG.md:2903

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

  5275. msgstr ""

  5276. 

  5277. #: ../../../CHANGELOG.md:2905

  5278. msgid "From now on, you can easily install and configure this spam checker module through the playbook."

  5279. msgstr ""

  5280. 

  5281. #: ../../../CHANGELOG.md:2907

  5282. msgid "Learn more in [Setting up Synapse Simple Antispam](docs/configuring-playbook-synapse-simple-antispam.md)."

  5283. msgstr ""

  5284. 

  5285. #: ../../../CHANGELOG.md:2910

  5286. msgid "2019-08-25"

  5287. msgstr ""

  5288. 

  5289. #: ../../../CHANGELOG.md:2912

  5290. msgid "Extensible Riot-web configuration"

  5291. msgstr ""

  5292. 

  5293. #: ../../../CHANGELOG.md:2914

  5294. msgid "Similarly to [Extensible Synapse configuration](#extensible-synapse-configuration) (below), Riot-web configuration is also extensible now."

  5295. msgstr ""

  5296. 

  5297. #: ../../../CHANGELOG.md:2916

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

  5299. msgstr ""

  5300. 

  5301. #: ../../../CHANGELOG.md:2918

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

  5303. msgstr ""

  5304. 

  5305. #: ../../../CHANGELOG.md:2920

  5306. msgid "Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-web.md)."

  5307. msgstr ""

  5308. 

  5309. #: ../../../CHANGELOG.md:2923

  5310. msgid "2019-08-22"

  5311. msgstr ""

  5312. 

  5313. #: ../../../CHANGELOG.md:2925

  5314. msgid "Extensible Synapse configuration"

  5315. msgstr ""

  5316. 

  5317. #: ../../../CHANGELOG.md:2927

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

  5319. msgstr ""

  5320. 

  5321. #: ../../../CHANGELOG.md:2929

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

  5323. msgstr ""

  5324. 

  5325. #: ../../../CHANGELOG.md:2931

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

  5327. msgstr ""

  5328. 

  5329. #: ../../../CHANGELOG.md:2933

  5330. msgid "Learn more here in [Configuring Synapse](docs/configuring-playbook-synapse.md)."

  5331. msgstr ""

  5332. 

  5333. #: ../../../CHANGELOG.md:2936

  5334. msgid "2019-08-21"

  5335. msgstr ""

  5336. 

  5337. #: ../../../CHANGELOG.md:2940

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

  5339. msgstr ""

  5340. 

  5341. #: ../../../CHANGELOG.md:2942

  5342. msgid "Additional details are available in [Setting up Appservice Slack bridging](docs/configuring-playbook-bridge-appservice-slack.md)."

  5343. msgstr ""

  5344. 

  5345. #: ../../../CHANGELOG.md:2944

  5346. msgid "Google Hangouts bridging support"

  5347. msgstr ""

  5348. 

  5349. #: ../../../CHANGELOG.md:2946

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

  5351. msgstr ""

  5352. 

  5353. #: ../../../CHANGELOG.md:2948

  5354. msgid "Additional details are available in [Setting up Mautrix Hangouts bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)."

  5355. msgstr ""

  5356. 

  5357. #: ../../../CHANGELOG.md:2951

  5358. msgid "2019-08-05"

  5359. msgstr ""

  5360. 

  5361. #: ../../../CHANGELOG.md:2953

  5362. msgid "Email2Matrix support"

  5363. msgstr ""

  5364. 

  5365. #: ../../../CHANGELOG.md:2955

  5366. msgid "Support for [Email2Matrix](https://github.com/devture/email2matrix) has been added."

  5367. msgstr ""

  5368. 

  5369. #: ../../../CHANGELOG.md:2957

  5370. msgid "It's an optional feature that you can enable via the playbook."

  5371. msgstr ""

  5372. 

  5373. #: ../../../CHANGELOG.md:2959

  5374. msgid "To learn more, see the [playbook's documentation on Email2Matrix](./docs/configuring-playbook-email2matrix.md)."

  5375. msgstr ""

  5376. 

  5377. #: ../../../CHANGELOG.md:2962

  5378. msgid "2019-08-03"

  5379. msgstr ""

  5380. 

  5381. #: ../../../CHANGELOG.md:2964

  5382. msgid "Synapse logging level has been reduced to WARNING"

  5383. msgstr ""

  5384. 

  5385. #: ../../../CHANGELOG.md:2966

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

  5387. msgstr ""

  5388. 

  5389. #: ../../../CHANGELOG.md:2968

  5390. msgid "This greatly reduces the number of log messages that are being logged, leading to:"

  5391. msgstr ""

  5392. 

  5393. #: ../../../CHANGELOG.md:2970

  5394. msgid "much less disk space dedicated to Synapse and thus, logs kept for longer"

  5395. msgstr ""

  5396. 

  5397. #: ../../../CHANGELOG.md:2971

  5398. msgid "easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages, as they're not longer buried in thousands of non-important `INFO` messages"

  5399. msgstr ""

  5400. 

  5401. #: ../../../CHANGELOG.md:2973

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

  5403. msgstr ""

  5404. 

  5405. #: ../../../CHANGELOG.md:2976

  5406. msgid "2019-07-08"

  5407. msgstr ""

  5408. 

  5409. #: ../../../CHANGELOG.md:2978

  5410. msgid "Synapse Maintenance docs and synapse-janitor support are available"

  5411. msgstr ""

  5412. 

  5413. #: ../../../CHANGELOG.md:2980

  5414. msgid "The playbook can now help you with Synapse's maintenance."

  5415. msgstr ""

  5416. 

  5417. #: ../../../CHANGELOG.md:2982

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

  5419. msgstr ""

  5420. 

  5421. #: ../../../CHANGELOG.md:2984

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

  5423. msgstr ""

  5424. 

  5425. #: ../../../CHANGELOG.md:2986

  5426. msgid "(BC Break) Rename run control variables"

  5427. msgstr ""

  5428. 

  5429. #: ../../../CHANGELOG.md:2988

  5430. msgid "Some internal playbook control variables have been renamed."

  5431. msgstr ""

  5432. 

  5433. #: ../../../CHANGELOG.md:2990

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

  5435. msgstr ""

  5436. 

  5437. #: ../../../CHANGELOG.md:2992

  5438. msgid "The following variables have been renamed:"

  5439. msgstr ""

  5440. 

  5441. #: ../../../CHANGELOG.md:2994

  5442. msgid "from `run_import_postgres` to `run_postgres_import`"

  5443. msgstr ""

  5444. 

  5445. #: ../../../CHANGELOG.md:2995

  5446. msgid "from `run_import_sqlite_db` to `run_postgres_import_sqlite_db`"

  5447. msgstr ""

  5448. 

  5449. #: ../../../CHANGELOG.md:2996

  5450. msgid "from `run_upgrade_postgres` to `run_postgres_upgrade`"

  5451. msgstr ""

  5452. 

  5453. #: ../../../CHANGELOG.md:2997

  5454. msgid "from `run_import_media_store` to `run_synapse_import_media_store`"

  5455. msgstr ""

  5456. 

  5457. #: ../../../CHANGELOG.md:2998

  5458. msgid "from `run_register_user` to `run_synapse_register_user`"

  5459. msgstr ""

  5460. 

  5461. #: ../../../CHANGELOG.md:2999

  5462. msgid "from `run_update_user_password` to `run_synapse_update_user_password`"

  5463. msgstr ""

  5464. 

  5465. #: ../../../CHANGELOG.md:3002

  5466. msgid "2019-07-04"

  5467. msgstr ""

  5468. 

  5469. #: ../../../CHANGELOG.md:3004

  5470. msgid "Synapse no longer logs to text files"

  5471. msgstr ""

  5472. 

  5473. #: ../../../CHANGELOG.md:3006

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

  5475. msgstr ""

  5476. 

  5477. #: ../../../CHANGELOG.md:3008

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

  5479. msgstr ""

  5480. 

  5481. #: ../../../CHANGELOG.md:3010

  5482. msgid "Because of this, the following variables have become obsolete and were removed:"

  5483. msgstr ""

  5484. 

  5485. #: ../../../CHANGELOG.md:3012

  5486. msgid "`matrix_synapse_max_log_file_size_mb`"

  5487. msgstr ""

  5488. 

  5489. #: ../../../CHANGELOG.md:3013

  5490. msgid "`matrix_synapse_max_log_files_count`"

  5491. msgstr ""

  5492. 

  5493. #: ../../../CHANGELOG.md:3015

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

  5495. msgstr ""

  5496. 

  5497. #: ../../../CHANGELOG.md:3017

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

  5499. msgstr ""

  5500. 

  5501. #: ../../../CHANGELOG.md:3020

  5502. msgid "2019-06-27"

  5503. msgstr ""

  5504. 

  5505. #: ../../../CHANGELOG.md:3022

  5506. msgid "(BC Break) Discord bridge configuration is now entirely managed by the playbook"

  5507. msgstr ""

  5508. 

  5509. #: ../../../CHANGELOG.md:3024

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

  5511. msgstr ""

  5512. 

  5513. #: ../../../CHANGELOG.md:3026

  5514. msgid "From now on, the playbook will keep both configuration files sync for you."

  5515. msgstr ""

  5516. 

  5517. #: ../../../CHANGELOG.md:3028

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

  5519. msgstr ""

  5520. 

  5521. #: ../../../CHANGELOG.md:3030

  5522. msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-discord/config`)."

  5523. msgstr ""

  5524. 

  5525. #: ../../../CHANGELOG.md:3032

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

  5527. msgstr ""

  5528. 

  5529. #: ../../../CHANGELOG.md:3034

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

  5531. msgstr ""

  5532. 

  5533. #: ../../../CHANGELOG.md:3036

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

  5535. msgstr ""

  5536. 

  5537. #: ../../../CHANGELOG.md:3039

  5538. msgid "2019-06-24"

  5539. msgstr ""

  5540. 

  5541. #: ../../../CHANGELOG.md:3041

  5542. msgid "(BC Break) WhatsApp bridge configuration is now entirely managed by the playbook"

  5543. msgstr ""

  5544. 

  5545. #: ../../../CHANGELOG.md:3043

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

  5547. msgstr ""

  5548. 

  5549. #: ../../../CHANGELOG.md:3045 ../../../CHANGELOG.md:3062

  5550. #: ../../../CHANGELOG.md:3081 ../../../CHANGELOG.md:3120

  5551. msgid "From now on, the playbook will keep the configuration in sync for you."

  5552. msgstr ""

  5553. 

  5554. #: ../../../CHANGELOG.md:3047

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

  5556. msgstr ""

  5557. 

  5558. #: ../../../CHANGELOG.md:3049

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

  5560. msgstr ""

  5561. 

  5562. #: ../../../CHANGELOG.md:3051

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

  5564. msgstr ""

  5565. 

  5566. #: ../../../CHANGELOG.md:3053

  5567. msgid "We're now following the default configuration for the WhatsApp bridge."

  5568. msgstr ""

  5569. 

  5570. #: ../../../CHANGELOG.md:3056

  5571. msgid "2019-06-20"

  5572. msgstr ""

  5573. 

  5574. #: ../../../CHANGELOG.md:3058

  5575. msgid "(BC Break) IRC bridge configuration is now entirely managed by the playbook"

  5576. msgstr ""

  5577. 

  5578. #: ../../../CHANGELOG.md:3060

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

  5580. msgstr ""

  5581. 

  5582. #: ../../../CHANGELOG.md:3064

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

  5584. msgstr ""

  5585. 

  5586. #: ../../../CHANGELOG.md:3066

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

  5588. msgstr ""

  5589. 

  5590. #: ../../../CHANGELOG.md:3068

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

  5592. msgstr ""

  5593. 

  5594. #: ../../../CHANGELOG.md:3070

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

  5596. msgstr ""

  5597. 

  5598. #: ../../../CHANGELOG.md:3072

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

  5600. msgstr ""

  5601. 

  5602. #: ../../../CHANGELOG.md:3075

  5603. msgid "2019-06-15"

  5604. msgstr ""

  5605. 

  5606. #: ../../../CHANGELOG.md:3077

  5607. msgid "(BC Break) Telegram bridge configuration is now entirely managed by the playbook"

  5608. msgstr ""

  5609. 

  5610. #: ../../../CHANGELOG.md:3079

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

  5612. msgstr ""

  5613. 

  5614. #: ../../../CHANGELOG.md:3083

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

  5616. msgstr ""

  5617. 

  5618. #: ../../../CHANGELOG.md:3085

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

  5620. msgstr ""

  5621. 

  5622. #: ../../../CHANGELOG.md:3087

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

  5624. msgstr ""

  5625. 

  5626. #: ../../../CHANGELOG.md:3089

  5627. msgid "Also, we're now following the default configuration for the Telegram bridge, so some default configuration values are different:"

  5628. msgstr ""

  5629. 

  5630. #: ../../../CHANGELOG.md:3091

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

  5632. msgstr ""

  5633. 

  5634. #: ../../../CHANGELOG.md:3092

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

  5636. msgstr ""

  5637. 

  5638. #: ../../../CHANGELOG.md:3093

  5639. msgid "`authless_portals` (used to be `false`, now `true`) — creating portals from the Telegram side is now possible"

  5640. msgstr ""

  5641. 

  5642. #: ../../../CHANGELOG.md:3094

  5643. msgid "`whitelist_group_admins` (used to be `false`, now `true`) — allows Telegram group admins to use the bot commands"

  5644. msgstr ""

  5645. 

  5646. #: ../../../CHANGELOG.md:3096

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

  5648. msgstr ""

  5649. 

  5650. #: ../../../CHANGELOG.md:3099

  5651. msgid "2019-06-12"

  5652. msgstr ""

  5653. 

  5654. #: ../../../CHANGELOG.md:3101

  5655. msgid "Synapse v1.0"

  5656. msgstr ""

  5657. 

  5658. #: ../../../CHANGELOG.md:3103

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

  5660. msgstr ""

  5661. 

  5662. #: ../../../CHANGELOG.md:3105

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

  5664. msgstr ""

  5665. 

  5666. #: ../../../CHANGELOG.md:3107

  5667. msgid "**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` DNS SRV records. The latter, **must not** be removed."

  5668. msgstr ""

  5669. 

  5670. #: ../../../CHANGELOG.md:3109

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

  5672. msgstr ""

  5673. 

  5674. #: ../../../CHANGELOG.md:3111

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

  5676. msgstr ""

  5677. 

  5678. #: ../../../CHANGELOG.md:3114

  5679. msgid "2019-06-07"

  5680. msgstr ""

  5681. 

  5682. #: ../../../CHANGELOG.md:3116

  5683. msgid "(BC Break) Facebook bridge configuration is now entirely managed by the playbook"

  5684. msgstr ""

  5685. 

  5686. #: ../../../CHANGELOG.md:3118

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

  5688. msgstr ""

  5689. 

  5690. #: ../../../CHANGELOG.md:3122

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

  5692. msgstr ""

  5693. 

  5694. #: ../../../CHANGELOG.md:3124

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

  5696. msgstr ""

  5697. 

  5698. #: ../../../CHANGELOG.md:3126

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

  5700. msgstr ""

  5701. 

  5702. #: ../../../CHANGELOG.md:3129

  5703. msgid "2019-05-25"

  5704. msgstr ""

  5705. 

  5706. #: ../../../CHANGELOG.md:3131

  5707. msgid "Support for exposing container ports publicly (not just to the host)"

  5708. msgstr ""

  5709. 

  5710. #: ../../../CHANGELOG.md:3133

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

  5712. msgstr ""

  5713. 

  5714. #: ../../../CHANGELOG.md:3135

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

  5716. msgstr ""

  5717. 

  5718. #: ../../../CHANGELOG.md:3137

  5719. msgid "All such variables have been superseded by a better (more flexible) way to do it."

  5720. msgstr ""

  5721. 

  5722. #: ../../../CHANGELOG.md:3139

  5723. msgid "**Most** people (including those not using `matrix-nginx-proxy`), **don't need** to bother with this."

  5724. msgstr ""

  5725. 

  5726. #: ../../../CHANGELOG.md:3141

  5727. msgid "Porting examples follow for people having more customized setups:"

  5728. msgstr ""

  5729. 

  5730. #: ../../../CHANGELOG.md:3143

  5731. msgid "**from** `matrix_synapse_container_expose_client_api_port: true` **to** `matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`"

  5732. msgstr ""

  5733. 

  5734. #: ../../../CHANGELOG.md:3145

  5735. 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'`"

  5736. msgstr ""

  5737. 

  5738. #: ../../../CHANGELOG.md:3147

  5739. msgid "**from** `matrix_synapse_container_expose_metrics_port: true` **to** `matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`"

  5740. msgstr ""

  5741. 

  5742. #: ../../../CHANGELOG.md:3149

  5743. msgid "**from** `matrix_riot_web_container_expose_port: true` **to** `matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`"

  5744. msgstr ""

  5745. 

  5746. #: ../../../CHANGELOG.md:3151

  5747. msgid "**from** `matrix_mxisd_container_expose_port: true` **to** `matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`"

  5748. msgstr ""

  5749. 

  5750. #: ../../../CHANGELOG.md:3153

  5751. msgid "**from** `matrix_dimension_container_expose_port: true` **to** `matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`"

  5752. msgstr ""

  5753. 

  5754. #: ../../../CHANGELOG.md:3155

  5755. 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'`"

  5756. msgstr ""

  5757. 

  5758. #: ../../../CHANGELOG.md:3157

  5759. 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'`"

  5760. msgstr ""

  5761. 

  5762. #: ../../../CHANGELOG.md:3159

  5763. 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'`"

  5764. msgstr ""

  5765. 

  5766. #: ../../../CHANGELOG.md:3161

  5767. msgid "As always, if you forget to remove usage of some outdated variable, the playbook will warn you."

  5768. msgstr ""

  5769. 

  5770. #: ../../../CHANGELOG.md:3164

  5771. msgid "2019-05-23"

  5772. msgstr ""

  5773. 

  5774. #: ../../../CHANGELOG.md:3166

  5775. msgid "(BC Break) Ansible 2.8 compatibility"

  5776. msgstr ""

  5777. 

  5778. #: ../../../CHANGELOG.md:3168

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

  5780. msgstr ""

  5781. 

  5782. #: ../../../CHANGELOG.md:3170

  5783. msgid "A manual change is required to the `inventory/hosts` file, changing the group name from `matrix-servers` to `matrix_servers` (dash to underscore)."

  5784. msgstr ""

  5785. 

  5786. #: ../../../CHANGELOG.md:3172

  5787. msgid "To avoid doing it manually, run this:"

  5788. msgstr ""

  5789. 

  5790. #: ../../../CHANGELOG.md:3173

  5791. msgid "Linux: `sed -i 's/matrix-servers/matrix_servers/g' inventory/hosts`"

  5792. msgstr ""

  5793. 

  5794. #: ../../../CHANGELOG.md:3174

  5795. msgid "Mac: `sed -i '' 's/matrix-servers/matrix_servers/g' inventory/hosts`"

  5796. msgstr ""

  5797. 

  5798. #: ../../../CHANGELOG.md:3177

  5799. msgid "2019-05-21"

  5800. msgstr ""

  5801. 

  5802. #: ../../../CHANGELOG.md:3179

  5803. msgid "Synapse no longer required"

  5804. msgstr ""

  5805. 

  5806. #: ../../../CHANGELOG.md:3181

  5807. msgid "The playbook no longer insists on installing [Synapse](https://github.com/element-hq/synapse) via the `matrix-synapse` role."

  5808. msgstr ""

  5809. 

  5810. #: ../../../CHANGELOG.md:3183

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

  5812. msgstr ""

  5813. 

  5814. #: ../../../CHANGELOG.md:3185

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

  5816. msgstr ""

  5817. 

  5818. #: ../../../CHANGELOG.md:3187

  5819. msgid "Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers."

  5820. msgstr ""

  5821. 

  5822. #: ../../../CHANGELOG.md:3189

  5823. msgid "Bridges are now separate from the Synapse role"

  5824. msgstr ""

  5825. 

  5826. #: ../../../CHANGELOG.md:3191

  5827. msgid "Bridges are no longer part of the `matrix-synapse` role. Each bridge now lives in its own separate role (`roles/custom/matrix-bridge-*`)."

  5828. msgstr ""

  5829. 

  5830. #: ../../../CHANGELOG.md:3193

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

  5832. msgstr ""

  5833. 

  5834. #: ../../../CHANGELOG.md:3195

  5835. msgid "Renaming inconsistently-named Synapse variables"

  5836. msgstr ""

  5837. 

  5838. #: ../../../CHANGELOG.md:3197

  5839. msgid "For better consistency, the following variables have been renamed:"

  5840. msgstr ""

  5841. 

  5842. #: ../../../CHANGELOG.md:3199

  5843. msgid "`matrix_enable_room_list_search` was renamed to `matrix_synapse_enable_room_list_search`"

  5844. msgstr ""

  5845. 

  5846. #: ../../../CHANGELOG.md:3200

  5847. msgid "`matrix_alias_creation_rules` was renamed to `matrix_synapse_alias_creation_rules`"

  5848. msgstr ""

  5849. 

  5850. #: ../../../CHANGELOG.md:3201

  5851. msgid "`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was renamed to `matrix_synapse_room_list_publication_rules`"

  5852. msgstr ""

  5853. 

  5854. #: ../../../CHANGELOG.md:3204

  5855. msgid "2019-05-09"

  5856. msgstr ""

  5857. 

  5858. #: ../../../CHANGELOG.md:3206

  5859. msgid "Besides a myriad of bug fixes and minor improvements, here are the more notable (bigger) features we can announce today."

  5860. msgstr ""

  5861. 

  5862. #: ../../../CHANGELOG.md:3208

  5863. msgid "Mautrix Facebook/Messenger bridging support"

  5864. msgstr ""

  5865. 

  5866. #: ../../../CHANGELOG.md:3210

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

  5868. msgstr ""

  5869. 

  5870. #: ../../../CHANGELOG.md:3212

  5871. msgid "Additional details are available in [Setting up Mautrix Facebook bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)."

  5872. msgstr ""

  5873. 

  5874. #: ../../../CHANGELOG.md:3214

  5875. msgid "mxisd Registration feature integration"

  5876. msgstr ""

  5877. 

  5878. #: ../../../CHANGELOG.md:3216

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

  5880. msgstr ""

  5881. 

  5882. #: ../../../CHANGELOG.md:3218

  5883. msgid "Learn more in [mxisd-controlled Registration](docs/configuring-playbook-mxisd.md#mxisd-controlled-registration)."

  5884. msgstr ""

  5885. 

  5886. #: ../../../CHANGELOG.md:3221

  5887. msgid "2019-04-16"

  5888. msgstr ""

  5889. 

  5890. #: ../../../CHANGELOG.md:3223

  5891. msgid "Caddy webserver examples"

  5892. msgstr ""

  5893. 

  5894. #: ../../../CHANGELOG.md:3225

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

  5896. msgstr ""

  5897. 

  5898. #: ../../../CHANGELOG.md:3227

  5899. msgid "2019-04-10"

  5900. msgstr ""

  5901. 

  5902. #: ../../../CHANGELOG.md:3229

  5903. msgid "Goofys support for other S3-compatible object stores"

  5904. msgstr ""

  5905. 

  5906. #: ../../../CHANGELOG.md:3231

  5907. 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),"

  5908. msgstr ""

  5909. 

  5910. #: ../../../CHANGELOG.md:3234

  5911. msgid "2019-04-03"

  5912. msgstr ""

  5913. 

  5914. #: ../../../CHANGELOG.md:3236

  5915. msgid "Ansible >= 2.5 is required"

  5916. msgstr ""

  5917. 

  5918. #: ../../../CHANGELOG.md:3238

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

  5920. msgstr ""

  5921. 

  5922. #: ../../../CHANGELOG.md:3240

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

  5924. msgstr ""

  5925. 

  5926. #: ../../../CHANGELOG.md:3243

  5927. msgid "2019-03-19"

  5928. msgstr ""

  5929. 

  5930. #: ../../../CHANGELOG.md:3245

  5931. msgid "TLS support for coturn"

  5932. msgstr ""

  5933. 

  5934. #: ../../../CHANGELOG.md:3247

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

  5936. msgstr ""

  5937. 

  5938. #: ../../../CHANGELOG.md:3249

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

  5940. msgstr ""

  5941. 

  5942. #: ../../../CHANGELOG.md:3255

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

  5944. msgstr ""

  5945. 

  5946. #: ../../../CHANGELOG.md:3257

  5947. msgid "People who build their own custom playbook from our roles should be aware that:"

  5948. msgstr ""

  5949. 

  5950. #: ../../../CHANGELOG.md:3259

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

  5952. msgstr ""

  5953. 

  5954. #: ../../../CHANGELOG.md:3261

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

  5956. msgstr ""

  5957. 

  5958. #: ../../../CHANGELOG.md:3264

  5959. msgid "2019-03-12"

  5960. msgstr ""

  5961. 

  5962. #: ../../../CHANGELOG.md:3266

  5963. msgid "matrix-nginx-proxy support for serving the base domain"

  5964. msgstr ""

  5965. 

  5966. #: ../../../CHANGELOG.md:3268

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

  5968. msgstr ""

  5969. 

  5970. #: ../../../CHANGELOG.md:3270

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

  5972. msgstr ""

  5973. 

  5974. #: ../../../CHANGELOG.md:3272

  5975. msgid "(BC break) matrix-nginx-proxy data variable renamed"

  5976. msgstr ""

  5977. 

  5978. #: ../../../CHANGELOG.md:3274

  5979. msgid "`matrix_nginx_proxy_data_path` was renamed to `matrix_nginx_proxy_base_path`."

  5980. msgstr ""

  5981. 

  5982. #: ../../../CHANGELOG.md:3276

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

  5984. msgstr ""

  5985. 

  5986. #: ../../../CHANGELOG.md:3279

  5987. msgid "2019-03-10"

  5988. msgstr ""

  5989. 

  5990. #: ../../../CHANGELOG.md:3281

  5991. msgid "Dimension integration manager support"

  5992. msgstr ""

  5993. 

  5994. #: ../../../CHANGELOG.md:3283

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

  5996. msgstr ""

  5997. 

  5998. #: ../../../CHANGELOG.md:3286

  5999. msgid "2019-03-07"

  6000. msgstr ""

  6001. 

  6002. #: ../../../CHANGELOG.md:3288

  6003. msgid "Ability to customize mxisd's email templates"

  6004. msgstr ""

  6005. 

  6006. #: ../../../CHANGELOG.md:3290

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

  6008. msgstr ""

  6009. 

  6010. #: ../../../CHANGELOG.md:3293

  6011. msgid "2019-03-05"

  6012. msgstr ""

  6013. 

  6014. #: ../../../CHANGELOG.md:3295

  6015. msgid "Discord bridging support"

  6016. msgstr ""

  6017. 

  6018. #: ../../../CHANGELOG.md:3297

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

  6020. msgstr ""

  6021. 

  6022. #: ../../../CHANGELOG.md:3300

  6023. msgid "2019-02-19"

  6024. msgstr ""

  6025. 

  6026. #: ../../../CHANGELOG.md:3302

  6027. msgid "Renaming variables"

  6028. msgstr ""

  6029. 

  6030. #: ../../../CHANGELOG.md:3304 ../../../CHANGELOG.md:3621

  6031. #: ../../../CHANGELOG.md:3706 ../../../CHANGELOG.md:3826

  6032. msgid "The following playbook variables were renamed:"

  6033. msgstr ""

  6034. 

  6035. #: ../../../CHANGELOG.md:3306

  6036. msgid "from `host_specific_hostname_identity` to `matrix_domain`"

  6037. msgstr ""

  6038. 

  6039. #: ../../../CHANGELOG.md:3307

  6040. msgid "from `hostname_identity` to `matrix_domain`"

  6041. msgstr ""

  6042. 

  6043. #: ../../../CHANGELOG.md:3308

  6044. msgid "from `hostname_matrix` to `matrix_server_fqn_matrix`"

  6045. msgstr ""

  6046. 

  6047. #: ../../../CHANGELOG.md:3309

  6048. msgid "from `hostname_riot` to `matrix_server_fqn_riot`"

  6049. msgstr ""

  6050. 

  6051. #: ../../../CHANGELOG.md:3310

  6052. msgid "from `host_specific_matrix_ssl_lets_encrypt_support_email` to `matrix_ssl_lets_encrypt_support_email`"

  6053. msgstr ""

  6054. 

  6055. #: ../../../CHANGELOG.md:3312

  6056. msgid "Doing that, we've simplified things, made names less confusing (hopefully) and moved all variable names under the `matrix_` prefix."

  6057. msgstr ""

  6058. 

  6059. #: ../../../CHANGELOG.md:3315

  6060. msgid "2019-02-16"

  6061. msgstr ""

  6062. 

  6063. #: ../../../CHANGELOG.md:3317

  6064. msgid "Riot v1.0.1 support"

  6065. msgstr ""

  6066. 

  6067. #: ../../../CHANGELOG.md:3319

  6068. msgid "You can now use the brand new and redesigned Riot."

  6069. msgstr ""

  6070. 

  6071. #: ../../../CHANGELOG.md:3321

  6072. msgid "The new version no longer has a homepage by default, so we've also removed the custom homepage that we've been installing."

  6073. msgstr ""

  6074. 

  6075. #: ../../../CHANGELOG.md:3323

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

  6077. msgstr ""

  6078. 

  6079. #: ../../../CHANGELOG.md:3326

  6080. msgid "2019-02-14"

  6081. msgstr ""

  6082. 

  6083. #: ../../../CHANGELOG.md:3328

  6084. msgid "Synapse v0.99.1"

  6085. msgstr ""

  6086. 

  6087. #: ../../../CHANGELOG.md:3330

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

  6089. msgstr ""

  6090. 

  6091. #: ../../../CHANGELOG.md:3332

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

  6093. msgstr ""

  6094. 

  6095. #: ../../../CHANGELOG.md:3335

  6096. msgid "2019-02-06"

  6097. msgstr ""

  6098. 

  6099. #: ../../../CHANGELOG.md:3337

  6100. msgid "Synapse v0.99 support and preparation for Synapse v1.0"

  6101. msgstr ""

  6102. 

  6103. #: ../../../CHANGELOG.md:3339

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

  6105. msgstr ""

  6106. 

  6107. #: ../../../CHANGELOG.md:3341

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

  6109. msgstr ""

  6110. 

  6111. #: ../../../CHANGELOG.md:3343

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

  6113. msgstr ""

  6114. 

  6115. #: ../../../CHANGELOG.md:3345

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

  6117. msgstr ""

  6118. 

  6119. #: ../../../CHANGELOG.md:3347

  6120. 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-checking-services.md), 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."

  6121. msgstr ""

  6122. 

  6123. #: ../../../CHANGELOG.md:3349

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

  6125. msgstr ""

  6126. 

  6127. #: ../../../CHANGELOG.md:3352

  6128. msgid "2019-02-01"

  6129. msgstr ""

  6130. 

  6131. #: ../../../CHANGELOG.md:3354

  6132. msgid "TLS v1.3 support"

  6133. msgstr ""

  6134. 

  6135. #: ../../../CHANGELOG.md:3356

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

  6137. msgstr ""

  6138. 

  6139. #: ../../../CHANGELOG.md:3358

  6140. msgid "When using:"

  6141. msgstr ""

  6142. 

  6143. #: ../../../CHANGELOG.md:3360

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

  6145. msgstr ""

  6146. 

  6147. #: ../../../CHANGELOG.md:3362

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

  6149. msgstr ""

  6150. 

  6151. #: ../../../CHANGELOG.md:3364

  6152. msgid "**another web server**: you don't need to do anything to accommodate this change"

  6153. msgstr ""

  6154. 

  6155. #: ../../../CHANGELOG.md:3367

  6156. msgid "2019-01-31"

  6157. msgstr ""

  6158. 

  6159. #: ../../../CHANGELOG.md:3369

  6160. msgid "IRC bridging support"

  6161. msgstr ""

  6162. 

  6163. #: ../../../CHANGELOG.md:3371

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

  6165. msgstr ""

  6166. 

  6167. #: ../../../CHANGELOG.md:3374

  6168. msgid "2019-01-29"

  6169. msgstr ""

  6170. 

  6171. #: ../../../CHANGELOG.md:3376

  6172. msgid "Running container processes as non-root, without capabilities and read-only"

  6173. msgstr ""

  6174. 

  6175. #: ../../../CHANGELOG.md:3378

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

  6177. msgstr ""

  6178. 

  6179. #: ../../../CHANGELOG.md:3380

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

  6181. msgstr ""

  6182. 

  6183. #: ../../../CHANGELOG.md:3382

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

  6185. msgstr ""

  6186. 

  6187. #: ../../../CHANGELOG.md:3384

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

  6189. msgstr ""

  6190. 

  6191. #: ../../../CHANGELOG.md:3386

  6192. msgid "matrix-mailer is now based on Exim, not Postfix"

  6193. msgstr ""

  6194. 

  6195. #: ../../../CHANGELOG.md:3388

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

  6197. msgstr ""

  6198. 

  6199. #: ../../../CHANGELOG.md:3390

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

  6201. msgstr ""

  6202. 

  6203. #: ../../../CHANGELOG.md:3392

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

  6205. msgstr ""

  6206. 

  6207. #: ../../../CHANGELOG.md:3395

  6208. msgid "2019-01-17"

  6209. msgstr ""

  6210. 

  6211. #: ../../../CHANGELOG.md:3397

  6212. msgid "(BC Break) Making the playbook's roles more independent of one another"

  6213. msgstr ""

  6214. 

  6215. #: ../../../CHANGELOG.md:3399

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

  6217. msgstr ""

  6218. 

  6219. #: ../../../CHANGELOG.md:3402

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

  6221. msgstr ""

  6222. 

  6223. #: ../../../CHANGELOG.md:3404

  6224. msgid "With the new changes, **all roles are now only dependent on the minimal `matrix-base` role**. They are no longer dependent among themselves."

  6225. msgstr ""

  6226. 

  6227. #: ../../../CHANGELOG.md:3406

  6228. msgid "In addition, the following components can now be completely disabled (for those who want/need to):"

  6229. msgstr ""

  6230. 

  6231. #: ../../../CHANGELOG.md:3407

  6232. msgid "`matrix-coturn` by using `matrix_coturn_enabled: false`"

  6233. msgstr ""

  6234. 

  6235. #: ../../../CHANGELOG.md:3408

  6236. msgid "`matrix-mailer` by using `matrix_mailer_enabled: false`"

  6237. msgstr ""

  6238. 

  6239. #: ../../../CHANGELOG.md:3409

  6240. msgid "`matrix-postgres` by using `matrix_postgres_enabled: false`"

  6241. msgstr ""

  6242. 

  6243. #: ../../../CHANGELOG.md:3411

  6244. msgid "The following changes had to be done:"

  6245. msgstr ""

  6246. 

  6247. #: ../../../CHANGELOG.md:3413

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

  6249. msgstr ""

  6250. 

  6251. #: ../../../CHANGELOG.md:3415

  6252. msgid "`matrix_postgres_use_external` has been superceeded 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."

  6253. msgstr ""

  6254. 

  6255. #: ../../../CHANGELOG.md:3417

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

  6257. msgstr ""

  6258. 

  6259. #: ../../../CHANGELOG.md:3419

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

  6261. msgstr ""

  6262. 

  6263. #: ../../../CHANGELOG.md:3422

  6264. msgid "2019-01-16"

  6265. msgstr ""

  6266. 

  6267. #: ../../../CHANGELOG.md:3424

  6268. msgid "Splitting the playbook into multiple roles"

  6269. msgstr ""

  6270. 

  6271. #: ../../../CHANGELOG.md:3426

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

  6273. msgstr ""

  6274. 

  6275. #: ../../../CHANGELOG.md:3429

  6276. msgid "To keep the filesystem more consistent with this separation, the **Postgres data had to be relocated**."

  6277. msgstr ""

  6278. 

  6279. #: ../../../CHANGELOG.md:3431

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

  6281. msgstr ""

  6282. 

  6283. #: ../../../CHANGELOG.md:3434

  6284. msgid "2019-01-11"

  6285. msgstr ""

  6286. 

  6287. #: ../../../CHANGELOG.md:3436

  6288. msgid "(BC Break) mxisd configuration changes"

  6289. msgstr ""

  6290. 

  6291. #: ../../../CHANGELOG.md:3438

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

  6293. msgstr ""

  6294. 

  6295. #: ../../../CHANGELOG.md:3441

  6296. msgid "The following variables are no longer supported by this playbook:"

  6297. msgstr ""

  6298. 

  6299. #: ../../../CHANGELOG.md:3443

  6300. msgid "`matrix_mxisd_ldap_enabled`"

  6301. msgstr ""

  6302. 

  6303. #: ../../../CHANGELOG.md:3444

  6304. msgid "`matrix_mxisd_ldap_connection_host`"

  6305. msgstr ""

  6306. 

  6307. #: ../../../CHANGELOG.md:3445

  6308. msgid "`matrix_mxisd_ldap_connection_tls`"

  6309. msgstr ""

  6310. 

  6311. #: ../../../CHANGELOG.md:3446

  6312. msgid "`matrix_mxisd_ldap_connection_port`"

  6313. msgstr ""

  6314. 

  6315. #: ../../../CHANGELOG.md:3447

  6316. msgid "`matrix_mxisd_ldap_connection_baseDn`"

  6317. msgstr ""

  6318. 

  6319. #: ../../../CHANGELOG.md:3448

  6320. msgid "`matrix_mxisd_ldap_connection_baseDns`"

  6321. msgstr ""

  6322. 

  6323. #: ../../../CHANGELOG.md:3449 ../../../CHANGELOG.md:3450

  6324. msgid "`matrix_mxisd_ldap_connection_bindDn`"

  6325. msgstr ""

  6326. 

  6327. #: ../../../CHANGELOG.md:3451 ../../../CHANGELOG.md:3455

  6328. msgid "`matrix_mxisd_ldap_connection_bindPassword`"

  6329. msgstr ""

  6330. 

  6331. #: ../../../CHANGELOG.md:3452

  6332. msgid "`matrix_mxisd_ldap_filter`"

  6333. msgstr ""

  6334. 

  6335. #: ../../../CHANGELOG.md:3453

  6336. msgid "`matrix_mxisd_ldap_attribute_uid_type`"

  6337. msgstr ""

  6338. 

  6339. #: ../../../CHANGELOG.md:3454

  6340. msgid "`matrix_mxisd_ldap_attribute_uid_value`"

  6341. msgstr ""

  6342. 

  6343. #: ../../../CHANGELOG.md:3456

  6344. msgid "`matrix_mxisd_ldap_attribute_name`"

  6345. msgstr ""

  6346. 

  6347. #: ../../../CHANGELOG.md:3457

  6348. msgid "`matrix_mxisd_ldap_attribute_threepid_email`"

  6349. msgstr ""

  6350. 

  6351. #: ../../../CHANGELOG.md:3458

  6352. msgid "`matrix_mxisd_ldap_attribute_threepid_msisdn`"

  6353. msgstr ""

  6354. 

  6355. #: ../../../CHANGELOG.md:3459

  6356. msgid "`matrix_mxisd_ldap_identity_filter`"

  6357. msgstr ""

  6358. 

  6359. #: ../../../CHANGELOG.md:3460

  6360. msgid "`matrix_mxisd_ldap_identity_medium`"

  6361. msgstr ""

  6362. 

  6363. #: ../../../CHANGELOG.md:3461

  6364. msgid "`matrix_mxisd_ldap_auth_filter`"

  6365. msgstr ""

  6366. 

  6367. #: ../../../CHANGELOG.md:3462

  6368. msgid "`matrix_mxisd_ldap_directory_filter`"

  6369. msgstr ""

  6370. 

  6371. #: ../../../CHANGELOG.md:3463

  6372. msgid "`matrix_mxisd_template_config`"

  6373. msgstr ""

  6374. 

  6375. #: ../../../CHANGELOG.md:3465

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

  6377. msgstr ""

  6378. 

  6379. #: ../../../CHANGELOG.md:3467

  6380. msgid "This new way of configuring mxisd is beneficial because:"

  6381. msgstr ""

  6382. 

  6383. #: ../../../CHANGELOG.md:3469

  6384. msgid "it lets us support all mxisd configuration options, as the playbook simply forwards them to mxisd without needing to care or understand them"

  6385. msgstr ""

  6386. 

  6387. #: ../../../CHANGELOG.md:3470

  6388. msgid "it lets you upgrade to newer mxisd versions and make use of their features, without us having to add support for them explicitly"

  6389. msgstr ""

  6390. 

  6391. #: ../../../CHANGELOG.md:3473

  6392. msgid "2019-01-08"

  6393. msgstr ""

  6394. 

  6395. #: ../../../CHANGELOG.md:3475

  6396. msgid "(BC Break) Cronjob schedule no longer configurable"

  6397. msgstr ""

  6398. 

  6399. #: ../../../CHANGELOG.md:3477

  6400. msgid "Due to the way we manage cronjobs now, you can no longer configure the schedule they're invoked at."

  6401. msgstr ""

  6402. 

  6403. #: ../../../CHANGELOG.md:3479

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

  6405. msgstr ""

  6406. 

  6407. #: ../../../CHANGELOG.md:3482

  6408. 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!"

  6409. msgstr ""

  6410. 

  6411. #: ../../../CHANGELOG.md:3485

  6412. msgid "2018-12-23"

  6413. msgstr ""

  6414. 

  6415. #: ../../../CHANGELOG.md:3487

  6416. msgid "(BC Break) More SSL certificate retrieval methods"

  6417. msgstr ""

  6418. 

  6419. #: ../../../CHANGELOG.md:3489

  6420. msgid "The playbook now lets you decide between 3 different SSL certificate retrieval methods:"

  6421. msgstr ""

  6422. 

  6423. #: ../../../CHANGELOG.md:3490

  6424. msgid "(default) obtaining free SSL certificates from Let's Encrypt"

  6425. msgstr ""

  6426. 

  6427. #: ../../../CHANGELOG.md:3491

  6428. msgid "generating self-signed SSL certificates"

  6429. msgstr ""

  6430. 

  6431. #: ../../../CHANGELOG.md:3492

  6432. msgid "managing SSL certificates manually"

  6433. msgstr ""

  6434. 

  6435. #: ../../../CHANGELOG.md:3494

  6436. msgid "Learn more in [Adjusting SSL certificate retrieval](docs/configuring-playbook-ssl-certificates.md)."

  6437. msgstr ""

  6438. 

  6439. #: ../../../CHANGELOG.md:3496

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

  6441. msgstr ""

  6442. 

  6443. #: ../../../CHANGELOG.md:3498

  6444. msgid "before: `host_specific_matrix_ssl_support_email`"

  6445. msgstr ""

  6446. 

  6447. #: ../../../CHANGELOG.md:3499

  6448. msgid "after: `host_specific_matrix_ssl_lets_encrypt_support_email`"

  6449. msgstr ""

  6450. 

  6451. #: ../../../CHANGELOG.md:3501

  6452. msgid "(BC Break) mxisd upgrade with multiple base DN support"

  6453. msgstr ""

  6454. 

  6455. #: ../../../CHANGELOG.md:3503

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

  6457. msgstr ""

  6458. 

  6459. #: ../../../CHANGELOG.md:3505

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

  6461. msgstr ""

  6462. 

  6463. #: ../../../CHANGELOG.md:3507

  6464. msgid "Example change:"

  6465. msgstr ""

  6466. 

  6467. #: ../../../CHANGELOG.md:3509

  6468. msgid "before: `matrix_mxisd_ldap_connection_baseDn: OU=Users,DC=example,DC=org`"

  6469. msgstr ""

  6470. 

  6471. #: ../../../CHANGELOG.md:3510

  6472. msgid "after: `matrix_mxisd_ldap_connection_baseDns: ['OU=Users,DC=example,DC=org']`"

  6473. msgstr ""

  6474. 

  6475. #: ../../../CHANGELOG.md:3513

  6476. msgid "2018-12-21"

  6477. msgstr ""

  6478. 

  6479. #: ../../../CHANGELOG.md:3515

  6480. msgid "Synapse 0.34.0 and Python 3"

  6481. msgstr ""

  6482. 

  6483. #: ../../../CHANGELOG.md:3517

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

  6485. msgstr ""

  6486. 

  6487. #: ../../../CHANGELOG.md:3520

  6488. msgid "2018-12-12"

  6489. msgstr ""

  6490. 

  6491. #: ../../../CHANGELOG.md:3522

  6492. msgid "Riot homepage customization"

  6493. msgstr ""

  6494. 

  6495. #: ../../../CHANGELOG.md:3524

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

  6497. msgstr ""

  6498. 

  6499. #: ../../../CHANGELOG.md:3527

  6500. msgid "2018-12-04"

  6501. msgstr ""

  6502. 

  6503. #: ../../../CHANGELOG.md:3529

  6504. msgid "mxisd extensibility"

  6505. msgstr ""

  6506. 

  6507. #: ../../../CHANGELOG.md:3531

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

  6509. msgstr ""

  6510. 

  6511. #: ../../../CHANGELOG.md:3534

  6512. msgid "2018-11-28"

  6513. msgstr ""

  6514. 

  6515. #: ../../../CHANGELOG.md:3536

  6516. msgid "More scripts"

  6517. msgstr ""

  6518. 

  6519. #: ../../../CHANGELOG.md:3538

  6520. msgid "matrix-remove-all allows to uninstall everything with a single command"

  6521. msgstr ""

  6522. 

  6523. #: ../../../CHANGELOG.md:3539

  6524. msgid "matrix-make-user-admin allows to upgrade a user's privileges"

  6525. msgstr ""

  6526. 

  6527. #: ../../../CHANGELOG.md:3541

  6528. msgid "LDAP auth support via matrix-synapse-ldap3"

  6529. msgstr ""

  6530. 

  6531. #: ../../../CHANGELOG.md:3543

  6532. msgid "The playbook can now install and configure [LDAP auth support](https://github.com/matrix-org/matrix-synapse-ldap3) for you."

  6533. msgstr ""

  6534. 

  6535. #: ../../../CHANGELOG.md:3545

  6536. msgid "Additional details are available in [Setting up the LDAP authentication password provider module](docs/configuring-playbook-ldap-auth.md)."

  6537. msgstr ""

  6538. 

  6539. #: ../../../CHANGELOG.md:3548

  6540. msgid "2018-11-23"

  6541. msgstr ""

  6542. 

  6543. #: ../../../CHANGELOG.md:3550

  6544. msgid "Support for controlling public registration and room auto-join"

  6545. msgstr ""

  6546. 

  6547. #: ../../../CHANGELOG.md:3552

  6548. msgid "The playbook now lets you enable public registration for users (controlled via `matrix_synapse_enable_registration`). By default, public registration is forbidden."

  6549. msgstr ""

  6550. 

  6551. #: ../../../CHANGELOG.md:3554

  6552. msgid "You can also make people automatically get auto-joined to rooms (controlled via `matrix_synapse_auto_join_rooms`)."

  6553. msgstr ""

  6554. 

  6555. #: ../../../CHANGELOG.md:3556

  6556. msgid "Support for changing the welcome user ID (welcome bot)"

  6557. msgstr ""

  6558. 

  6559. #: ../../../CHANGELOG.md:3558

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

  6561. msgstr ""

  6562. 

  6563. #: ../../../CHANGELOG.md:3561

  6564. msgid "2018-11-14"

  6565. msgstr ""

  6566. 

  6567. #: ../../../CHANGELOG.md:3563

  6568. msgid "Ability to set Synapse log levels"

  6569. msgstr ""

  6570. 

  6571. #: ../../../CHANGELOG.md:3565

  6572. msgid "The playbook now allows you to set the log levels used by Synapse. The default logging levels remain the same."

  6573. msgstr ""

  6574. 

  6575. #: ../../../CHANGELOG.md:3567

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

  6577. msgstr ""

  6578. 

  6579. #: ../../../CHANGELOG.md:3576

  6580. msgid "2018-11-03"

  6581. msgstr ""

  6582. 

  6583. #: ../../../CHANGELOG.md:3578

  6584. msgid "Customize parts of Riot's config"

  6585. msgstr ""

  6586. 

  6587. #: ../../../CHANGELOG.md:3580

  6588. msgid "You can now customize some parts of Riot's `config.json`. These playbook variables, with these default values, have been added:"

  6589. msgstr ""

  6590. 

  6591. #: ../../../CHANGELOG.md:3591

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

  6593. msgstr ""

  6594. 

  6595. #: ../../../CHANGELOG.md:3600

  6596. msgid "SSL protocols used to serve Riot and Synapse"

  6597. msgstr ""

  6598. 

  6599. #: ../../../CHANGELOG.md:3602

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

  6601. msgstr ""

  6602. 

  6603. #: ../../../CHANGELOG.md:3604

  6604. msgid "You may wish to reenable TLSv1 if you need to access Riot in older browsers."

  6605. msgstr ""

  6606. 

  6607. #: ../../../CHANGELOG.md:3606

  6608. msgid "Note: Currently the dockerized nginx doesn't support TLSv1.3. See https://github.com/nginxinc/docker-nginx/issues/190 for more details."

  6609. msgstr ""

  6610. 

  6611. #: ../../../CHANGELOG.md:3609

  6612. msgid "2018-11-01"

  6613. msgstr ""

  6614. 

  6615. #: ../../../CHANGELOG.md:3611

  6616. msgid "Postgres 11 support"

  6617. msgstr ""

  6618. 

  6619. #: ../../../CHANGELOG.md:3613

  6620. msgid "The playbook now installs [Postgres 11](https://www.postgresql.org/about/news/1894/) by default."

  6621. msgstr ""

  6622. 

  6623. #: ../../../CHANGELOG.md:3615

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

  6625. msgstr ""

  6626. 

  6627. #: ../../../CHANGELOG.md:3617 ../../../CHANGELOG.md:3704

  6628. #: ../../../CHANGELOG.md:3824

  6629. msgid "(BC Break) Renaming playbook variables"

  6630. msgstr ""

  6631. 

  6632. #: ../../../CHANGELOG.md:3619

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

  6634. msgstr ""

  6635. 

  6636. #: ../../../CHANGELOG.md:3623

  6637. msgid "from `matrix_docker_image_mxisd` to `matrix_mxisd_docker_image`"

  6638. msgstr ""

  6639. 

  6640. #: ../../../CHANGELOG.md:3624

  6641. msgid "from `matrix_docker_image_mautrix_telegram` to `matrix_mautrix_telegram_docker_image`"

  6642. msgstr ""

  6643. 

  6644. #: ../../../CHANGELOG.md:3625

  6645. msgid "from `matrix_docker_image_mautrix_whatsapp` to `matrix_mautrix_whatsapp_docker_image`"

  6646. msgstr ""

  6647. 

  6648. #: ../../../CHANGELOG.md:3626

  6649. msgid "from `matrix_docker_image_mailer` to `matrix_mailer_docker_image`"

  6650. msgstr ""

  6651. 

  6652. #: ../../../CHANGELOG.md:3627

  6653. msgid "from `matrix_docker_image_coturn` to `matrix_coturn_docker_image`"

  6654. msgstr ""

  6655. 

  6656. #: ../../../CHANGELOG.md:3628

  6657. msgid "from `matrix_docker_image_goofys` to `matrix_s3_goofys_docker_image`"

  6658. msgstr ""

  6659. 

  6660. #: ../../../CHANGELOG.md:3629

  6661. msgid "from `matrix_docker_image_riot` to `matrix_riot_web_docker_image`"

  6662. msgstr ""

  6663. 

  6664. #: ../../../CHANGELOG.md:3630

  6665. msgid "from `matrix_docker_image_nginx` to `matrix_nginx_proxy_docker_image`"

  6666. msgstr ""

  6667. 

  6668. #: ../../../CHANGELOG.md:3631

  6669. msgid "from `matrix_docker_image_synapse` to `matrix_synapse_docker_image`"

  6670. msgstr ""

  6671. 

  6672. #: ../../../CHANGELOG.md:3632

  6673. msgid "from `matrix_docker_image_postgres_v9` to `matrix_postgres_docker_image_v9`"

  6674. msgstr ""

  6675. 

  6676. #: ../../../CHANGELOG.md:3633

  6677. msgid "from `matrix_docker_image_postgres_v10` to `matrix_postgres_docker_image_v10`"

  6678. msgstr ""

  6679. 

  6680. #: ../../../CHANGELOG.md:3634

  6681. msgid "from `matrix_docker_image_postgres_latest` to `matrix_postgres_docker_image_latest`"

  6682. msgstr ""

  6683. 

  6684. #: ../../../CHANGELOG.md:3637

  6685. msgid "2018-10-26"

  6686. msgstr ""

  6687. 

  6688. #: ../../../CHANGELOG.md:3639

  6689. msgid "Mautrix Whatsapp bridging support"

  6690. msgstr ""

  6691. 

  6692. #: ../../../CHANGELOG.md:3641

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

  6694. msgstr ""

  6695. 

  6696. #: ../../../CHANGELOG.md:3643

  6697. msgid "Additional details are available in [Setting up Mautrix Whatsapp bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)."

  6698. msgstr ""

  6699. 

  6700. #: ../../../CHANGELOG.md:3646

  6701. msgid "2018-10-25"

  6702. msgstr ""

  6703. 

  6704. #: ../../../CHANGELOG.md:3648

  6705. msgid "Support for controlling Matrix federation"

  6706. msgstr ""

  6707. 

  6708. #: ../../../CHANGELOG.md:3650

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

  6710. msgstr ""

  6711. 

  6712. #: ../../../CHANGELOG.md:3653

  6713. msgid "2018-10-24"

  6714. msgstr ""

  6715. 

  6716. #: ../../../CHANGELOG.md:3655

  6717. msgid "Disabling riot-web guests"

  6718. msgstr ""

  6719. 

  6720. #: ../../../CHANGELOG.md:3657

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

  6722. msgstr ""

  6723. 

  6724. #: ../../../CHANGELOG.md:3660

  6725. msgid "2018-10-21"

  6726. msgstr ""

  6727. 

  6728. #: ../../../CHANGELOG.md:3662

  6729. msgid "Self-check maintenance command"

  6730. msgstr ""

  6731. 

  6732. #: ../../../CHANGELOG.md:3664

  6733. msgid "The playbook can now [check if services are configured correctly](docs/maintenance-checking-services.md)."

  6734. msgstr ""

  6735. 

  6736. #: ../../../CHANGELOG.md:3667

  6737. msgid "2018-10-05"

  6738. msgstr ""

  6739. 

  6740. #: ../../../CHANGELOG.md:3669

  6741. msgid "Presence tracking made configurable"

  6742. msgstr ""

  6743. 

  6744. #: ../../../CHANGELOG.md:3671

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

  6746. msgstr ""

  6747. 

  6748. #: ../../../CHANGELOG.md:3673

  6749. msgid "If users participate in large rooms with many other servers, disabling presence will decrease server load significantly."

  6750. msgstr ""

  6751. 

  6752. #: ../../../CHANGELOG.md:3676

  6753. msgid "2018-09-27"

  6754. msgstr ""

  6755. 

  6756. #: ../../../CHANGELOG.md:3678

  6757. msgid "Synapse Cache Factor made configurable"

  6758. msgstr ""

  6759. 

  6760. #: ../../../CHANGELOG.md:3680

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

  6762. msgstr ""

  6763. 

  6764. #: ../../../CHANGELOG.md:3682

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

  6766. msgstr ""

  6767. 

  6768. #: ../../../CHANGELOG.md:3685

  6769. msgid "2018-09-26"

  6770. msgstr ""

  6771. 

  6772. #: ../../../CHANGELOG.md:3687

  6773. msgid "Disabling Docker container logging"

  6774. msgstr ""

  6775. 

  6776. #: ../../../CHANGELOG.md:3689

  6777. msgid "`--log-driver=none` is used for all Docker containers now."

  6778. msgstr ""

  6779. 

  6780. #: ../../../CHANGELOG.md:3691

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

  6782. msgstr ""

  6783. 

  6784. #: ../../../CHANGELOG.md:3693

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

  6786. msgstr ""

  6787. 

  6788. #: ../../../CHANGELOG.md:3696

  6789. msgid "2018-09-17"

  6790. msgstr ""

  6791. 

  6792. #: ../../../CHANGELOG.md:3698

  6793. msgid "Service discovery support"

  6794. msgstr ""

  6795. 

  6796. #: ../../../CHANGELOG.md:3700

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

  6798. msgstr ""

  6799. 

  6800. #: ../../../CHANGELOG.md:3702

  6801. msgid "Additional details are available in [Configuring service discovery via .well-known](docs/configuring-well-known.md)."

  6802. msgstr ""

  6803. 

  6804. #: ../../../CHANGELOG.md:3708

  6805. msgid "from `matrix_nginx_riot_web_data_path` to `matrix_riot_web_data_path`"

  6806. msgstr ""

  6807. 

  6808. #: ../../../CHANGELOG.md:3709

  6809. msgid "from `matrix_riot_web_default_identity_server_url` to `matrix_identity_server_url`"

  6810. msgstr ""

  6811. 

  6812. #: ../../../CHANGELOG.md:3712

  6813. msgid "2018-09-07"

  6814. msgstr ""

  6815. 

  6816. #: ../../../CHANGELOG.md:3714

  6817. msgid "Mautrix Telegram bridging support"

  6818. msgstr ""

  6819. 

  6820. #: ../../../CHANGELOG.md:3716

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

  6822. msgstr ""

  6823. 

  6824. #: ../../../CHANGELOG.md:3718

  6825. msgid "Additional details are available in [Setting up Mautrix Telegram bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)."

  6826. msgstr ""

  6827. 

  6828. #: ../../../CHANGELOG.md:3720

  6829. msgid "Events cache size increase and configurability for Matrix Synapse"

  6830. msgstr ""

  6831. 

  6832. #: ../../../CHANGELOG.md:3722

  6833. msgid "The playbook now lets you configure Matrix Synapse's `event_cache_size` configuration via the `matrix_synapse_event_cache_size` playbook variable."

  6834. msgstr ""

  6835. 

  6836. #: ../../../CHANGELOG.md:3724

  6837. msgid "Previously, this value was hardcoded to `\"10K\"`. From now on, a more reasonable default of `\"100K\"` is used."

  6838. msgstr ""

  6839. 

  6840. #: ../../../CHANGELOG.md:3726

  6841. msgid "Password-peppering support for Matrix Synapse"

  6842. msgstr ""

  6843. 

  6844. #: ../../../CHANGELOG.md:3728

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

  6846. msgstr ""

  6847. 

  6848. #: ../../../CHANGELOG.md:3730

  6849. msgid "Statistics-reporting support for Matrix Synapse"

  6850. msgstr ""

  6851. 

  6852. #: ../../../CHANGELOG.md:3732

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

  6854. msgstr ""

  6855. 

  6856. #: ../../../CHANGELOG.md:3734

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

  6858. msgstr ""

  6859. 

  6860. #: ../../../CHANGELOG.md:3737

  6861. msgid "2018-08-29"

  6862. msgstr ""

  6863. 

  6864. #: ../../../CHANGELOG.md:3739

  6865. msgid "Changing the way SSL certificates are retrieved"

  6866. msgstr ""

  6867. 

  6868. #: ../../../CHANGELOG.md:3741

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

  6870. msgstr ""

  6871. 

  6872. #: ../../../CHANGELOG.md:3743

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

  6874. msgstr ""

  6875. 

  6876. #: ../../../CHANGELOG.md:3745

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

  6878. msgstr ""

  6879. 

  6880. #: ../../../CHANGELOG.md:3747

  6881. msgid "`systemctl stop 'matrix*'`"

  6882. msgstr ""

  6883. 

  6884. #: ../../../CHANGELOG.md:3748

  6885. msgid "stop your custom webserver, if you're running one (only affects you if you've installed with `matrix_nginx_proxy_enabled: false`)"

  6886. msgstr ""

  6887. 

  6888. #: ../../../CHANGELOG.md:3749

  6889. msgid "`mv /matrix/ssl /matrix/ssl-acmetool-delete-later`"

  6890. msgstr ""

  6891. 

  6892. #: ../../../CHANGELOG.md:3750

  6893. msgid "re-run the playbook's [installation](docs/installing.md)"

  6894. msgstr ""

  6895. 

  6896. #: ../../../CHANGELOG.md:3751

  6897. msgid "possibly delete `/matrix/ssl-acmetool-delete-later`"

  6898. msgstr ""

  6899. 

  6900. #: ../../../CHANGELOG.md:3754

  6901. msgid "2018-08-21"

  6902. msgstr ""

  6903. 

  6904. #: ../../../CHANGELOG.md:3756

  6905. msgid "Matrix Corporal support"

  6906. msgstr ""

  6907. 

  6908. #: ../../../CHANGELOG.md:3758

  6909. msgid "The playbook can now install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you."

  6910. msgstr ""

  6911. 

  6912. #: ../../../CHANGELOG.md:3760

  6913. msgid "Additional details are available in [Setting up Matrix Corporal](docs/configuring-playbook-matrix-corporal.md)."

  6914. msgstr ""

  6915. 

  6916. #: ../../../CHANGELOG.md:3763

  6917. msgid "2018-08-20"

  6918. msgstr ""

  6919. 

  6920. #: ../../../CHANGELOG.md:3765

  6921. msgid "Matrix Synapse rate limit control variables"

  6922. msgstr ""

  6923. 

  6924. #: ../../../CHANGELOG.md:3767

  6925. msgid "The following new variables can now be configured to control Matrix Synapse's rate-limiting (default values are shown below)."

  6926. msgstr ""

  6927. 

  6928. #: ../../../CHANGELOG.md:3774

  6929. msgid "Shared Secret Auth support via matrix-synapse-shared-secret-auth"

  6930. msgstr ""

  6931. 

  6932. #: ../../../CHANGELOG.md:3776

  6933. msgid "The playbook can now install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you."

  6934. msgstr ""

  6935. 

  6936. #: ../../../CHANGELOG.md:3778

  6937. msgid "Additional details are available in [Setting up the Shared Secret Auth password provider module](docs/configuring-playbook-shared-secret-auth.md)."

  6938. msgstr ""

  6939. 

  6940. #: ../../../CHANGELOG.md:3781

  6941. msgid "2018-08-17"

  6942. msgstr ""

  6943. 

  6944. #: ../../../CHANGELOG.md:3783

  6945. msgid "REST auth support via matrix-synapse-rest-auth"

  6946. msgstr ""

  6947. 

  6948. #: ../../../CHANGELOG.md:3785

  6949. msgid "The playbook can now install and configure [matrix-synapse-rest-auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you."

  6950. msgstr ""

  6951. 

  6952. #: ../../../CHANGELOG.md:3787

  6953. msgid "Additional details are available in [Setting up the REST authentication password provider module](docs/configuring-playbook-rest-auth.md)."

  6954. msgstr ""

  6955. 

  6956. #: ../../../CHANGELOG.md:3789

  6957. msgid "Compression improvements"

  6958. msgstr ""

  6959. 

  6960. #: ../../../CHANGELOG.md:3791

  6961. msgid "Shifted Matrix Synapse compression from happening in the Matrix Synapse, to happening in the nginx proxy that's in front of it."

  6962. msgstr ""

  6963. 

  6964. #: ../../../CHANGELOG.md:3794

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

  6966. msgstr ""

  6967. 

  6968. #: ../../../CHANGELOG.md:3797

  6969. msgid "Disabling some unnecessary Synapse services"

  6970. msgstr ""

  6971. 

  6972. #: ../../../CHANGELOG.md:3799

  6973. msgid "The following services are not necessary, so they have been disabled:"

  6974. msgstr ""

  6975. 

  6976. #: ../../../CHANGELOG.md:3800

  6977. msgid "on the federation port (8448): the `client` service"

  6978. msgstr ""

  6979. 

  6980. #: ../../../CHANGELOG.md:3801

  6981. msgid "on the http port (8008, exposed over 443): the old Angular `webclient` and the `federation` service"

  6982. msgstr ""

  6983. 

  6984. #: ../../../CHANGELOG.md:3803

  6985. msgid "Federation runs only on the federation port (8448) now. The Client APIs run only on the http port (8008) now."

  6986. msgstr ""

  6987. 

  6988. #: ../../../CHANGELOG.md:3806

  6989. msgid "2018-08-15"

  6990. msgstr ""

  6991. 

  6992. #: ../../../CHANGELOG.md:3808

  6993. msgid "mxisd Identity Server support"

  6994. msgstr ""

  6995. 

  6996. #: ../../../CHANGELOG.md:3810

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

  6998. msgstr ""

  6999. 

  7000. #: ../../../CHANGELOG.md:3813

  7001. msgid "2018-08-14"

  7002. msgstr ""

  7003. 

  7004. #: ../../../CHANGELOG.md:3815

  7005. msgid "Email-sending support"

  7006. msgstr ""

  7007. 

  7008. #: ../../../CHANGELOG.md:3817

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

  7010. msgstr ""

  7011. 

  7012. #: ../../../CHANGELOG.md:3819

  7013. msgid "With this, Matrix Synapse is able to send email notifications for missed messages, etc."

  7014. msgstr ""

  7015. 

  7016. #: ../../../CHANGELOG.md:3822

  7017. msgid "2018-08-08"

  7018. msgstr ""

  7019. 

  7020. #: ../../../CHANGELOG.md:3828

  7021. msgid "from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`"

  7022. msgstr ""

  7023. 

  7024. #: ../../../CHANGELOG.md:3829

  7025. msgid "from `matrix_max_log_file_size_mb` to `matrix_synapse_max_log_file_size_mb`"

  7026. msgstr ""

  7027. 

  7028. #: ../../../CHANGELOG.md:3830

  7029. msgid "from `matrix_max_log_files_count` to `matrix_synapse_max_log_files_count`"

  7030. msgstr ""

  7031. 

  7032. #: ../../../CHANGELOG.md:3831

  7033. msgid "from `docker_matrix_image` to `matrix_docker_image_synapse`"

  7034. msgstr ""

  7035. 

  7036. #: ../../../CHANGELOG.md:3832

  7037. msgid "from `docker_nginx_image` to `matrix_docker_image_nginx`"

  7038. msgstr ""

  7039. 

  7040. #: ../../../CHANGELOG.md:3833

  7041. msgid "from `docker_riot_image` to `matrix_docker_image_riot`"

  7042. msgstr ""

  7043. 

  7044. #: ../../../CHANGELOG.md:3834

  7045. msgid "from `docker_goofys_image` to `matrix_docker_image_goofys`"

  7046. msgstr ""

  7047. 

  7048. #: ../../../CHANGELOG.md:3835

  7049. msgid "from `docker_coturn_image` to `matrix_docker_image_coturn`"

  7050. msgstr ""

  7051. 

  7052. #: ../../../CHANGELOG.md:3837

  7053. msgid "If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names."

  7054. msgstr ""

  7055. 

  7056. #: ../../../CHANGELOG.md:3839

  7057. msgid "Renaming Ansible playbook tag"

  7058. msgstr ""

  7059. 

  7060. #: ../../../CHANGELOG.md:3841

  7061. msgid "The command for executing the whole playbook has changed. The `setup-main` tag got renamed to `setup-all`."

  7062. msgstr ""

  7063. 

  7064. #: ../../../CHANGELOG.md:3843

  7065. msgid "Docker container linking"

  7066. msgstr ""

  7067. 

  7068. #: ../../../CHANGELOG.md:3845

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

  7070. msgstr ""