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.
11507 Commits
1 Rama
107 MiB
 
 
 
Árbol: e6e0df3d32
Ramas Etiquetas
${ item.name }
Crear rama ${ searchTerm }
desde 'e6e0df3d32'
${ noResults }
matrix-docker-ansible-deploy/i18n/translation-templates/CHANGELOG.pot

8483 líneas
420 KiB
Original Blame Histórico 

  1. # SOME DESCRIPTIVE TITLE.

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

  3. # This file is distributed under the same license as the matrix-docker-ansible-deploy package.

  4. # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.

  5. #

  6. #, fuzzy

  7. msgid ""

  8. msgstr ""

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

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

  11. "POT-Creation-Date: 2026-06-29 17:11+0000\n"

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

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

  14. "Language-Team: LANGUAGE <LL@li.org>\n"

  15. "MIME-Version: 1.0\n"

  16. "Content-Type: text/plain; charset=UTF-8\n"

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

  18. 

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

  20. msgid "2026-06-29"

  21. msgstr ""

  22. 

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

  24. msgid "Support for running on Synology DSM"

  25. msgstr ""

  26. 

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

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

  29. msgstr ""

  30. 

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

  32. msgid "Synology hosts are detected automatically (via `/etc/synoinfo.conf`), so other systems are unaffected. On DSM, the playbook uses the platform's native user management (`synouser`/`synogroup`), works around a Docker SDK incompatibility, and installs a small boot-fix service that handles a few DSM-specific boot quirks."

  33. msgstr ""

  34. 

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

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

  37. msgstr ""

  38. 

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

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

  41. msgstr ""

  42. 

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

  44. msgid "The playbook now exposes the HTTP API of each [mautrix](https://github.com/mautrix) bridge, so tools like [Mautrix Manager](https://github.com/mautrix/manager) can help you log into them. This is especially useful for [mautrix-gmessages](./docs/configuring-playbook-bridge-mautrix-gmessages.md): Google has removed its QR-code login, leaving a [manual cookie-extraction flow](https://docs.mau.fi/bridges/go/gmessages/authentication.html) that tools like Mautrix Manager can streamline."

  45. msgstr ""

  46. 

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

  48. msgid "The API is exposed at `https://matrix.example.com/bridges/SERVICENAME` (for example, `https://matrix.example.com/bridges/gmessages`) and is advertised via a new `/.well-known/matrix/mautrix` file, so compatible tools can discover your bridges automatically. Such tools authenticate with your own Matrix access token, so no bridge secret needs to be shared with them."

  49. msgstr ""

  50. 

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

  52. msgid "This affects all mautrix bridges based on the new bridge framework (bluesky, gmessages, meta-instagram, meta-messenger, signal, slack, telegram, twitter and whatsapp) and is enabled by default."

  53. msgstr ""

  54. 

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

  56. msgid "To learn more (including how to turn it off), see the [Expose the bridge's API](./docs/configuring-playbook-bridge-mautrix-bridges.md#expose-the-bridges-api-for-mautrix-manager-and-similar-tools) section on our common mautrix bridges documentation page."

  57. msgstr ""

  58. 

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

  60. msgid "2026-06-28"

  61. msgstr ""

  62. 

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

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

  65. msgstr ""

  66. 

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

  68. msgid "[baibot](./docs/configuring-playbook-bot-baibot.md) now ships a preset for the [Venice](./docs/configuring-playbook-bot-baibot.md#venice) provider, and it's the one we recommend. It's the most capable provider baibot supports (text generation with vision, file inputs and web search, speech-to-text, text-to-speech, and image generation and editing), and the only one that runs inference with no logging and no training on your data."

  69. msgstr ""

  70. 

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

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

  73. msgstr ""

  74. 

  75. #: ../../../CHANGELOG.md:35

  76. msgid "[OpenAI](https://openai.com/) and baibot's other providers remain fully supported. To get started, see the [Setting up baibot](./docs/configuring-playbook-bot-baibot.md#venice) documentation page."

  77. msgstr ""

  78. 

  79. #: ../../../CHANGELOG.md:37

  80. msgid "2026-06-24"

  81. msgstr ""

  82. 

  83. #: ../../../CHANGELOG.md:39

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

  85. msgstr ""

  86. 

  87. #: ../../../CHANGELOG.md:41

  88. msgid "Thanks to [jasonlaguidice](https://github.com/jasonlaguidice), the playbook now supports bridging to [iMessage](https://support.apple.com/messages) via a new [RustPush](https://github.com/OpenBubbles/rustpush)-based bridge ([jasonlaguidice/imessage](https://github.com/jasonlaguidice/imessage))."

  89. msgstr ""

  90. 

  91. #: ../../../CHANGELOG.md:43

  92. msgid "Unlike the existing [mautrix-wsproxy](./docs/configuring-playbook-bridge-mautrix-wsproxy.md) iMessage bridge, this one talks directly to Apple's push notification service, so it needs neither a running Mac nor a wsproxy on the homeserver. Each user supplies a hardware key extracted from a Mac through the bridge bot's login flow."

  93. msgstr ""

  94. 

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

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

  97. msgstr ""

  98. 

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

  100. msgid "2026-05-24"

  101. msgstr ""

  102. 

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

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

  105. msgstr ""

  106. 

  107. #: ../../../CHANGELOG.md:51

  108. msgid "The [matrix-ldap-registration-proxy](./docs/configuring-playbook-matrix-ldap-registration-proxy.md) service has been removed from the playbook, as the source code and the container image have become unavailable."

  109. msgstr ""

  110. 

  111. #: ../../../CHANGELOG.md:53

  112. msgid "The playbook will let you know if you're using any `matrix_ldap_registration_proxy_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-matrix-ldap-registration-proxy.md#uninstalling-the-component-manually)."

  113. msgstr ""

  114. 

  115. #: ../../../CHANGELOG.md:55

  116. msgid "2026-05-23"

  117. msgstr ""

  118. 

  119. #: ../../../CHANGELOG.md:57

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

  121. msgstr ""

  122. 

  123. #: ../../../CHANGELOG.md:59

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

  125. msgstr ""

  126. 

  127. #: ../../../CHANGELOG.md:61

  128. msgid "The playbook will let you know if you're using any `matrix_bot_go_neb_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the bot manually](./docs/configuring-playbook-bot-go-neb.md#uninstalling-go-neb-manually)."

  129. msgstr ""

  130. 

  131. #: ../../../CHANGELOG.md:63

  132. msgid "2026-05-19"

  133. msgstr ""

  134. 

  135. #: ../../../CHANGELOG.md:65

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

  137. msgstr ""

  138. 

  139. #: ../../../CHANGELOG.md:67

  140. msgid "The [matrix-registration](./docs/configuring-playbook-matrix-registration.md) service has been removed from the playbook, as it has been unmaintained (archived) since November, 2025."

  141. msgstr ""

  142. 

  143. #: ../../../CHANGELOG.md:69

  144. msgid "The playbook will let you know if you're using any `matrix_registration_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-matrix-registration.md#uninstalling-the-component-manually)."

  145. msgstr ""

  146. 

  147. #: ../../../CHANGELOG.md:71

  148. msgid "2026-05-18"

  149. msgstr ""

  150. 

  151. #: ../../../CHANGELOG.md:73

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

  153. msgstr ""

  154. 

  155. #: ../../../CHANGELOG.md:75

  156. msgid "The playbook now ships [LiveKit Server](./docs/configuring-playbook-livekit-server.md) v1.12.0. See the [upstream release notes](https://github.com/livekit/livekit/releases/tag/v1.12.0) for details."

  157. msgstr ""

  158. 

  159. #: ../../../CHANGELOG.md:77

  160. msgid "This release tightens TURN security:"

  161. msgstr ""

  162. 

  163. #: ../../../CHANGELOG.md:79

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

  165. msgstr ""

  166. 

  167. #: ../../../CHANGELOG.md:80

  168. msgid "**TURN no longer relays traffic to restricted peer CIDRs** (loopback, link-local, multicast, private, unspecified) by default. If your setup legitimately requires it, list the ranges in `livekit_server_config_turn_allow_restricted_peer_cidrs`."

  169. msgstr ""

  170. 

  171. #: ../../../CHANGELOG.md:82

  172. msgid "For example, to allow TURN to reach the common [RFC1918](https://www.rfc-editor.org/rfc/rfc1918) private ranges, add to your `vars.yml`:"

  173. msgstr ""

  174. 

  175. #: ../../../CHANGELOG.md:90

  176. msgid "Adjust the ranges to match your network. To deny specific CIDRs (taking precedence over the allow list above), use `livekit_server_config_turn_deny_peer_cidrs` in the same shape."

  177. msgstr ""

  178. 

  179. #: ../../../CHANGELOG.md:93

  180. msgid "2026-05-07"

  181. msgstr ""

  182. 

  183. #: ../../../CHANGELOG.md:95

  184. msgid "Tuwunel support"

  185. msgstr ""

  186. 

  187. #: ../../../CHANGELOG.md:97

  188. msgid "Thanks to [Jason Volk](https://github.com/jevolk), the playbook now supports the [Tuwunel](./docs/configuring-playbook-tuwunel.md) homeserver as an optional alternative to Synapse."

  189. msgstr ""

  190. 

  191. #: ../../../CHANGELOG.md:99

  192. msgid "Tuwunel is a fork of [conduwuit](./docs/configuring-playbook-conduwuit.md) written in Rust. The former conduwuit maintainer [endorses Tuwunel as conduwuit's successor](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/5200#issuecomment-4396211185). Like [Continuwuity](./docs/configuring-playbook-continuwuity.md), Tuwunel continues development on top of conduwuit's database format."

  193. msgstr ""

  194. 

  195. #: ../../../CHANGELOG.md:101

  196. #: ../../../CHANGELOG.md:605

  197. #: ../../../CHANGELOG.md:818

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

  199. msgstr ""

  200. 

  201. #: ../../../CHANGELOG.md:103

  202. msgid "People that used to run conduwuit may wish to [migrate from conduwuit to Tuwunel](./docs/configuring-playbook-tuwunel.md#migrating-from-conduwuit) via the new `tuwunel-migrate-from-conduwuit` tag, which performs an in-place binary-swap migration that reads the conduwuit database directly."

  203. msgstr ""

  204. 

  205. #: ../../../CHANGELOG.md:105

  206. msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse/Conduit/Dendrite/Continuwuity to Tuwunel) without data loss. The exception is conduwuit, due to the shared database format."

  207. msgstr ""

  208. 

  209. #: ../../../CHANGELOG.md:108

  210. msgid "2026-04-24"

  211. msgstr ""

  212. 

  213. #: ../../../CHANGELOG.md:110

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

  215. msgstr ""

  216. 

  217. #: ../../../CHANGELOG.md:112

  218. msgid "Thanks to [luschmar](https://github.com/luschmar), the playbook now supports bridging to [Meshtastic](https://meshtastic.org/) mesh networks via [meshtastic-matrix-relay](https://github.com/jeremiah-k/meshtastic-matrix-relay) (mmrelay)."

  219. msgstr ""

  220. 

  221. #: ../../../CHANGELOG.md:114

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

  223. msgstr ""

  224. 

  225. #: ../../../CHANGELOG.md:116

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

  227. msgstr ""

  228. 

  229. #: ../../../CHANGELOG.md:118

  230. msgid "The [mautrix-telegram](./docs/configuring-playbook-bridge-mautrix-telegram.md) bridge has been [rewritten in Go](https://mau.fi/blog/2026-04-mautrix-release/) on top of the [bridgev2](https://docs.mau.fi/bridges/go/) architecture. See the [upstream v26.04 release notes](https://github.com/mautrix/telegram/releases/tag/v0.2604.0) for what changed in the bridge itself (shared-portal behavior, management-room state, new features, etc.)."

  231. msgstr ""

  232. 

  233. #: ../../../CHANGELOG.md:120

  234. msgid "**Most users won't have to do anything.** If you use the playbook's integrated Postgres (the default) and haven't customized telegram-bridge variables beyond `matrix_mautrix_telegram_api_id` and `matrix_mautrix_telegram_api_hash`, just re-run the playbook; the bridge will migrate itself on first start. Taking a backup beforehand is still a good idea."

  235. msgstr ""

  236. 

  237. #: ../../../CHANGELOG.md:122

  238. msgid "⚠️ **SQLite users: do not upgrade yet.** Upstream v0.2604.0 has a [known bug in the legacy SQLite migration](https://github.com/mautrix/telegram/releases/tag/v0.2604.0) that can corrupt your data. The playbook detects this case and will refuse to proceed. Either switch to Postgres first (set `matrix_mautrix_telegram_database_engine: postgres`; the playbook handles the pgloader migration), or wait for the next upstream release."

  239. msgstr ""

  240. 

  241. #: ../../../CHANGELOG.md:124

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

  243. msgstr ""

  244. 

  245. #: ../../../CHANGELOG.md:126

  246. msgid "Many `matrix_mautrix_telegram_*` variables have been **removed** (web-login endpoint, lottieconverter, username/alias/displayname templates, filter-mode, bot-token relaybot, Shared-Secret-Auth map). The deprecation check will tell you exactly what to rename or drop when you run the playbook."

  247. msgstr ""

  248. 

  249. #: ../../../CHANGELOG.md:127

  250. msgid "**Old-style relaybot users** (`matrix_mautrix_telegram_bot_token`): switch to the common [mautrix bridge relay mode](./docs/configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional) via `matrix_mautrix_telegram_bridge_relay_enabled: true`."

  251. msgstr ""

  252. 

  253. #: ../../../CHANGELOG.md:128

  254. msgid "**Shared-Secret-Auth double-puppeting users**: switch to [Appservice Double Puppet](./docs/configuring-playbook-appservice-double-puppet.md); the playbook wires it up automatically."

  255. msgstr ""

  256. 

  257. #: ../../../CHANGELOG.md:129

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

  259. msgstr ""

  260. 

  261. #: ../../../CHANGELOG.md:131

  262. msgid "2026-04-03"

  263. msgstr ""

  264. 

  265. #: ../../../CHANGELOG.md:133

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

  267. msgstr ""

  268. 

  269. #: ../../../CHANGELOG.md:135

  270. msgid "Synapse Admin has been rebranded to **[Ketesa](https://github.com/etkecc/ketesa)** — a landmark release that introduces a new identity, a full UI redesign, mobile-first layout, and deep Matrix Authentication Service (MAS) integration. For the full story behind the rename and a tour of what's new, see the [Ketesa v1.0.0 announcement](https://etke.cc/blog/introducing-ketesa/)."

  271. msgstr ""

  272. 

  273. #: ../../../CHANGELOG.md:137

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

  275. msgstr ""

  276. 

  277. #: ../../../CHANGELOG.md:139

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

  279. msgstr ""

  280. 

  281. #: ../../../CHANGELOG.md:141

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

  283. msgstr ""

  284. 

  285. #: ../../../CHANGELOG.md:143

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

  287. msgstr ""

  288. 

  289. #: ../../../CHANGELOG.md:145

  290. msgid "The playbook handles reverse-proxy routing for subpath deployments (e.g. `/ketesa`), including MAS-enabled setups — though OIDC auth flows on real servers still have some rough edges. Feedback is appreciated in [#ketesa:etke.cc](https://matrix.to/#/#ketesa:etke.cc)."

  291. msgstr ""

  292. 

  293. #: ../../../CHANGELOG.md:147

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

  295. msgstr ""

  296. 

  297. #: ../../../CHANGELOG.md:149

  298. msgid "2026-04-02"

  299. msgstr ""

  300. 

  301. #: ../../../CHANGELOG.md:151

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

  303. msgstr ""

  304. 

  305. #: ../../../CHANGELOG.md:153

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

  307. msgstr ""

  308. 

  309. #: ../../../CHANGELOG.md:155

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

  311. msgstr ""

  312. 

  313. #: ../../../CHANGELOG.md:157

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

  315. msgstr ""

  316. 

  317. #: ../../../CHANGELOG.md:159

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

  319. msgstr ""

  320. 

  321. #: ../../../CHANGELOG.md:161

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

  323. msgstr ""

  324. 

  325. #: ../../../CHANGELOG.md:168

  326. msgid "2026-03-23"

  327. msgstr ""

  328. 

  329. #: ../../../CHANGELOG.md:170

  330. msgid "Migration validation system introduced"

  331. msgstr ""

  332. 

  333. #: ../../../CHANGELOG.md:172

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

  335. msgstr ""

  336. 

  337. #: ../../../CHANGELOG.md:174

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

  339. msgstr ""

  340. 

  341. #: ../../../CHANGELOG.md:177

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

  343. msgstr ""

  344. 

  345. #: ../../../CHANGELOG.md:179

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

  347. msgstr ""

  348. 

  349. #: ../../../CHANGELOG.md:181

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

  351. msgstr ""

  352. 

  353. #: ../../../CHANGELOG.md:187

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

  355. msgstr ""

  356. 

  357. #: ../../../CHANGELOG.md:189

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

  359. msgstr ""

  360. 

  361. #: ../../../CHANGELOG.md:191

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

  363. msgstr ""

  364. 

  365. #: ../../../CHANGELOG.md:193

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

  367. msgstr ""

  368. 

  369. #: ../../../CHANGELOG.md:195

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

  371. msgstr ""

  372. 

  373. #: ../../../CHANGELOG.md:201

  374. msgid "2026-03-19"

  375. msgstr ""

  376. 

  377. #: ../../../CHANGELOG.md:203

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

  379. msgstr ""

  380. 

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

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

  383. msgstr ""

  384. 

  385. #: ../../../CHANGELOG.md:207

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

  387. msgstr ""

  388. 

  389. #: ../../../CHANGELOG.md:209

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

  391. msgstr ""

  392. 

  393. #: ../../../CHANGELOG.md:211

  394. #: ../../../CHANGELOG.md:227

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

  396. msgstr ""

  397. 

  398. #: ../../../CHANGELOG.md:217

  399. msgid "2026-03-17"

  400. msgstr ""

  401. 

  402. #: ../../../CHANGELOG.md:219

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

  404. msgstr ""

  405. 

  406. #: ../../../CHANGELOG.md:221

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

  408. msgstr ""

  409. 

  410. #: ../../../CHANGELOG.md:223

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

  412. msgstr ""

  413. 

  414. #: ../../../CHANGELOG.md:225

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

  416. msgstr ""

  417. 

  418. #: ../../../CHANGELOG.md:234

  419. msgid "2026-03-01"

  420. msgstr ""

  421. 

  422. #: ../../../CHANGELOG.md:236

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

  424. msgstr ""

  425. 

  426. #: ../../../CHANGELOG.md:238

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

  428. msgstr ""

  429. 

  430. #: ../../../CHANGELOG.md:240

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

  432. msgstr ""

  433. 

  434. #: ../../../CHANGELOG.md:241

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

  436. msgstr ""

  437. 

  438. #: ../../../CHANGELOG.md:243

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

  440. msgstr ""

  441. 

  442. #: ../../../CHANGELOG.md:245

  443. msgid "**Affects**: users of [synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3-storage-provider.md) who have configured a non-empty `matrix_synapse_ext_synapse_s3_storage_provider_config_prefix` value."

  444. msgstr ""

  445. 

  446. #: ../../../CHANGELOG.md:247

  447. msgid "If your bucket data was uploaded without the prefix before this fix, enabling proper prefix usage can make existing objects appear missing until data is migrated/copied to the prefixed key namespace."

  448. msgstr ""

  449. 

  450. #: ../../../CHANGELOG.md:249

  451. msgid "2026-02-26"

  452. msgstr ""

  453. 

  454. #: ../../../CHANGELOG.md:251

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

  456. msgstr ""

  457. 

  458. #: ../../../CHANGELOG.md:253

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

  460. msgstr ""

  461. 

  462. #: ../../../CHANGELOG.md:255

  463. msgid "This is not a user-facing change and does not change variable names (`matrix_synapse_reverse_proxy_companion_*` remain the same). The split looked clean on paper, but in practice both parts are tightly coupled through worker routing, tags (`setup-synapse`/`install-synapse`), and lifecycle ordering, so keeping them separate added coordination overhead with little practical benefit."

  464. msgstr ""

  465. 

  466. #: ../../../CHANGELOG.md:257

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

  468. msgstr ""

  469. 

  470. #: ../../../CHANGELOG.md:259

  471. msgid "With this change, Synapse and its reverse-proxy companion are managed in one role (`matrix-synapse`) while still keeping companion logic in dedicated task/template subdirectories for maintainability."

  472. msgstr ""

  473. 

  474. #: ../../../CHANGELOG.md:261

  475. msgid "2026-02-21"

  476. msgstr ""

  477. 

  478. #: ../../../CHANGELOG.md:263

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

  480. msgstr ""

  481. 

  482. #: ../../../CHANGELOG.md:265

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

  484. msgstr ""

  485. 

  486. #: ../../../CHANGELOG.md:267

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

  488. msgstr ""

  489. 

  490. #: ../../../CHANGELOG.md:269

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

  492. msgstr ""

  493. 

  494. #: ../../../CHANGELOG.md:270

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

  496. msgstr ""

  497. 

  498. #: ../../../CHANGELOG.md:272

  499. msgid "Coturn is still auto-enabled when [Jitsi](./docs/configuring-playbook-jitsi.md) is enabled (`jitsi_enabled: true`), because Jitsi still depends on TURN for legacy Matrix integration."

  500. msgstr ""

  501. 

  502. #: ../../../CHANGELOG.md:274

  503. msgid "Additionally, Coturn (when enabled) now defaults to using automatic IP detection of your server's external IP address, instead of assuming your Ansible inventory (`ansible_host`) points to a public address and using it for configuring `coturn_turn_external_ip_address`."

  504. msgstr ""

  505. 

  506. #: ../../../CHANGELOG.md:276

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

  508. msgstr ""

  509. 

  510. #: ../../../CHANGELOG.md:285

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

  512. msgstr ""

  513. 

  514. #: ../../../CHANGELOG.md:287

  515. msgid "For deployments that use the playbook-managed Traefik reverse-proxy, LiveKit TURN over TCP is now SSL-terminated at Traefik and passed as plain TCP to LiveKit (`turn.external_tls = true`) by default."

  516. msgstr ""

  517. 

  518. #: ../../../CHANGELOG.md:289

  519. msgid "To disable this behavior, set `livekit_server_config_turn_external_tls: false` and the playbook will revert to the old behavior - using traefik-certs-dumper to extract SSL certificates out of Traefik and pass them to LiveKit for explicit SSL termination there."

  520. msgstr ""

  521. 

  522. #: ../../../CHANGELOG.md:291

  523. msgid "If you are using `other-traefik-container` or [another reverse-proxy](./configuring-playbook-own-webserver.md), this change does **not** switch behavior automatically. That mode remains using certificate files in the container (Traefik certificates dumper flow) unless you explicitly set the TURN-Traefik mode variables to opt in."

  524. msgstr ""

  525. 

  526. #: ../../../CHANGELOG.md:293

  527. msgid "2026-02-17"

  528. msgstr ""

  529. 

  530. #: ../../../CHANGELOG.md:295

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

  532. msgstr ""

  533. 

  534. #: ../../../CHANGELOG.md:297

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

  536. msgstr ""

  537. 

  538. #: ../../../CHANGELOG.md:299

  539. msgid "Along with the relocation, the `matrix_prometheus_nginxlog_exporter_` prefix on its variable names has been renamed to `prometheus_nginxlog_exporter_`, so you need to adjust your `vars.yml` configuration."

  540. msgstr ""

  541. 

  542. #: ../../../CHANGELOG.md:301

  543. #: ../../../CHANGELOG.md:363

  544. #: ../../../CHANGELOG.md:373

  545. #: ../../../CHANGELOG.md:434

  546. #: ../../../CHANGELOG.md:456

  547. #: ../../../CHANGELOG.md:991

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

  549. msgstr ""

  550. 

  551. #: ../../../CHANGELOG.md:303

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

  553. msgstr ""

  554. 

  555. #: ../../../CHANGELOG.md:305

  556. msgid "[synapse-auto-invite-accept](./docs/configuring-playbook-synapse-auto-accept-invite.md) has been removed from the playbook, as the same functionality [has been integrated](https://github.com/element-hq/synapse/pull/17147) to Synapse since [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0)."

  557. msgstr ""

  558. 

  559. #: ../../../CHANGELOG.md:307

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

  561. msgstr ""

  562. 

  563. #: ../../../CHANGELOG.md:309

  564. msgid "If you're using any `matrix_synapse_ext_synapse_auto_accept_invite_*` variables, the playbook will let you know which one you'll need to remove from `vars.yml`."

  565. msgstr ""

  566. 

  567. #: ../../../CHANGELOG.md:311

  568. msgid "2026-02-16"

  569. msgstr ""

  570. 

  571. #: ../../../CHANGELOG.md:313

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

  573. msgstr ""

  574. 

  575. #: ../../../CHANGELOG.md:315

  576. msgid "[matrix-appservice-slack](./docs/configuring-playbook-bridge-appservice-slack.md) has been removed from the playbook, as it has been discontinued because the public Matrix.org Slack bridge has been decommissioned on January 14th, 2026."

  577. msgstr ""

  578. 

  579. #: ../../../CHANGELOG.md:317

  580. msgid "The playbook will let you know if you're using any `matrix_appservice_slack_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-bridge-appservice-slack.md#uninstalling-the-component-manually)."

  581. msgstr ""

  582. 

  583. #: ../../../CHANGELOG.md:319

  584. msgid "**Note**: Bridging to [Slack](https://slack.com) can also happen via the [mautrix-slack](./docs/configuring-playbook-bridge-mautrix-slack.md) bridge supported by the playbook."

  585. msgstr ""

  586. 

  587. #: ../../../CHANGELOG.md:321

  588. msgid "2026-02-13"

  589. msgstr ""

  590. 

  591. #: ../../../CHANGELOG.md:323

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

  593. msgstr ""

  594. 

  595. #: ../../../CHANGELOG.md:325

  596. msgid "When running `install-all` or `install-service` (whether via `just` or raw `ansible-playbook`), only services whose configuration or container image actually changed during the playbook run will now be restarted. Unchanged services are left running (or get started if they were stopped). This reduces unnecessary downtime — particularly for services like Traefik (the reverse proxy), which previously caused brief connectivity interruptions on every playbook run even when nothing changed."

  597. msgstr ""

  598. 

  599. #: ../../../CHANGELOG.md:327

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

  601. msgstr ""

  602. 

  603. #: ../../../CHANGELOG.md:329

  604. msgid "Currently, only Traefik tracks its own changes and benefits from conditional restart. All other services default to being restarted (the previous behavior). This is just the beginning — as more roles gain change-tracking support, playbook performance will improve and downtime will decrease dramatically, especially for `install-all` runs where most services haven't changed."

  605. msgstr ""

  606. 

  607. #: ../../../CHANGELOG.md:331

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

  609. msgstr ""

  610. 

  611. #: ../../../CHANGELOG.md:333

  612. msgid "**Before**:"

  613. msgstr ""

  614. 

  615. #: ../../../CHANGELOG.md:334

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

  617. msgstr ""

  618. 

  619. #: ../../../CHANGELOG.md:335

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

  621. msgstr ""

  622. 

  623. #: ../../../CHANGELOG.md:336

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

  625. msgstr ""

  626. 

  627. #: ../../../CHANGELOG.md:337

  628. msgid "**After**:"

  629. msgstr ""

  630. 

  631. #: ../../../CHANGELOG.md:338

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

  633. msgstr ""

  634. 

  635. #: ../../../CHANGELOG.md:339

  636. msgid "Traefik restarted: no ✅"

  637. msgstr ""

  638. 

  639. #: ../../../CHANGELOG.md:340

  640. msgid "dependent services restarted: no ✅"

  641. msgstr ""

  642. 

  643. #: ../../../CHANGELOG.md:342

  644. msgid "This behavior can be overridden via `--extra-vars='devture_systemd_service_manager_conditional_restart_enabled=false'` to force unconditional restarts. See [Conditional service restart](docs/just.md#conditional-service-restart) for details."

  645. msgstr ""

  646. 

  647. #: ../../../CHANGELOG.md:345

  648. msgid "2026-02-12"

  649. msgstr ""

  650. 

  651. #: ../../../CHANGELOG.md:347

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

  653. msgstr ""

  654. 

  655. #: ../../../CHANGELOG.md:349

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

  657. msgstr ""

  658. 

  659. #: ../../../CHANGELOG.md:351

  660. msgid "The playbook will let you know if you're using any `matrix_dimension_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-dimension.md#uninstalling-the-component-manually)."

  661. msgstr ""

  662. 

  663. #: ../../../CHANGELOG.md:353

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

  665. msgstr ""

  666. 

  667. #: ../../../CHANGELOG.md:355

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

  669. msgstr ""

  670. 

  671. #: ../../../CHANGELOG.md:357

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

  673. msgstr ""

  674. 

  675. #: ../../../CHANGELOG.md:359

  676. #: ../../../CHANGELOG.md:452

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

  678. msgstr ""

  679. 

  680. #: ../../../CHANGELOG.md:361

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

  682. msgstr ""

  683. 

  684. #: ../../../CHANGELOG.md:365

  685. msgid "2026-02-11"

  686. msgstr ""

  687. 

  688. #: ../../../CHANGELOG.md:367

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

  690. msgstr ""

  691. 

  692. #: ../../../CHANGELOG.md:369

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

  694. msgstr ""

  695. 

  696. #: ../../../CHANGELOG.md:371

  697. msgid "Along with the relocation, the `matrix_coturn_` prefix on its variable names has been renamed to `coturn_`, so you need to adjust your `vars.yml` configuration."

  698. msgstr ""

  699. 

  700. #: ../../../CHANGELOG.md:375

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

  702. msgstr ""

  703. 

  704. #: ../../../CHANGELOG.md:377

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

  706. msgstr ""

  707. 

  708. #: ../../../CHANGELOG.md:379

  709. msgid "The playbook will let you know if you're using any `matrix_conduwuit_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the service manually](./docs/configuring-playbook-conduwuit.md#uninstalling-the-service-manually)."

  710. msgstr ""

  711. 

  712. #: ../../../CHANGELOG.md:381

  713. msgid "Since [Continuwuity](configuring-playbook-continuwuity.md) is a drop-in replacement for conduwuit, migration is possible. Please refer to [this section](./configuring-playbook-continuwuity.md#migrating-from-conduwuit) for details."

  714. msgstr ""

  715. 

  716. #: ../../../CHANGELOG.md:383

  717. msgid "2026-02-09"

  718. msgstr ""

  719. 

  720. #: ../../../CHANGELOG.md:385

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

  722. msgstr ""

  723. 

  724. #: ../../../CHANGELOG.md:387

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

  726. msgstr ""

  727. 

  728. #: ../../../CHANGELOG.md:389

  729. msgid "The `matrix_media_repo_datastore_file_id` and `matrix_media_repo_datastore_s3_id` variables are no longer auto-configured with values. They must now be explicitly defined in your `vars.yml` file. The playbook will fail with a helpful error if they are not set (when needed)."

  730. msgstr ""

  731. 

  732. #: ../../../CHANGELOG.md:391

  733. msgid "These were never meant to be auto-configured. They were derived from `matrix_homeserver_generic_secret_key`, which is intended for secrets that are OK to change subsequently (and Ansible would assist in propagating these changes). matrix-media-repo datastore IDs are not secrets — they are static identifiers linking media to storage backends, and **must not change** after first use."

  734. msgstr ""

  735. 

  736. #: ../../../CHANGELOG.md:393

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

  738. msgstr ""

  739. 

  740. #: ../../../CHANGELOG.md:399

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

  742. msgstr ""

  743. 

  744. #: ../../../CHANGELOG.md:408

  745. msgid "**Why do this?**: This change allows us to **remove the [passlib](https://passlib.readthedocs.io/en/stable/index.html) Python library** from the [prerequisites](docs/prerequisites.md), as it was the last component that depended on it."

  746. msgstr ""

  747. 

  748. #: ../../../CHANGELOG.md:410

  749. msgid "2026-02-08"

  750. msgstr ""

  751. 

  752. #: ../../../CHANGELOG.md:412

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

  754. msgstr ""

  755. 

  756. #: ../../../CHANGELOG.md:414

  757. msgid "Zulip bridge has been removed from the playbook, as it doesn't work, and the maintainer seems to have abandoned it. See [this issue](https://github.com/GearKite/MatrixZulipBridge/issues/23) for more context."

  758. msgstr ""

  759. 

  760. #: ../../../CHANGELOG.md:416

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

  762. msgstr ""

  763. 

  764. #: ../../../CHANGELOG.md:418

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

  766. msgstr ""

  767. 

  768. #: ../../../CHANGELOG.md:420

  769. msgid "The old method used `password_hash('sha512', rounds=655555)` (655,555 rounds of SHA-512 hashing), which was designed for protecting low-entropy human passwords against brute-force attacks. For deriving secrets from an already high-entropy secret key, this many rounds provide no additional security - the secret key's entropy is what protects the derived passwords, not the computational cost of hashing."

  770. msgstr ""

  771. 

  772. #: ../../../CHANGELOG.md:422

  773. msgid "The new method uses a single-round `hash('sha512')` with a unique salt per service. This is equally secure for this use case (SHA-512 remains preimage-resistant; brute-forcing a high-entropy key is infeasible regardless of rounds), while being dramatically faster."

  774. msgstr ""

  775. 

  776. #: ../../../CHANGELOG.md:424

  777. msgid "On a fast mini PC, evaluating `postgres_managed_databases` (which references multiple database passwords) dropped from **~10.7 seconds to ~0.6 seconds**. The Postgres role evaluates this variable multiple times during a run, so the cumulative savings are significant. All other roles that reference derived passwords also benefit."

  778. msgstr ""

  779. 

  780. #: ../../../CHANGELOG.md:426

  781. msgid "**What this means for users**: all derived service passwords (database passwords, appservice tokens, etc.) will change on the next playbook run. The main/superuser database password (`postgres_connection_password`) is not affected, as it is hardcoded in inventory variables rather than derived via hashing. All services will receive their new passwords as part of the same run, so this should be a seamless, non-user-impacting change."

  782. msgstr ""

  783. 

  784. #: ../../../CHANGELOG.md:428

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

  786. msgstr ""

  787. 

  788. #: ../../../CHANGELOG.md:430

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

  790. msgstr ""

  791. 

  792. #: ../../../CHANGELOG.md:432

  793. msgid "Along with the relocation, the `matrix_dynamic_dns_` prefix on its variable names has been renamed to `ddclient_`, so you need to adjust your `vars.yml` configuration."

  794. msgstr ""

  795. 

  796. #: ../../../CHANGELOG.md:436

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

  798. msgstr ""

  799. 

  800. #: ../../../CHANGELOG.md:438

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

  802. msgstr ""

  803. 

  804. #: ../../../CHANGELOG.md:440

  805. msgid "The playbook will let you know if you're using any `matrix_ma1sd_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-ma1sd.md#uninstalling-the-component-manually)."

  806. msgstr ""

  807. 

  808. #: ../../../CHANGELOG.md:442

  809. msgid "Please note that some of the functions can be achieved with other components. For example, if you wish to implement LDAP integration, you might as well check out [the LDAP provider module for Synapse](./docs/configuring-playbook-ldap-auth.md) instead."

  810. msgstr ""

  811. 

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

  813. msgid "2026-02-07"

  814. msgstr ""

  815. 

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

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

  818. msgstr ""

  819. 

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

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

  822. msgstr ""

  823. 

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

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

  826. msgstr ""

  827. 

  828. #: ../../../CHANGELOG.md:454

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

  830. msgstr ""

  831. 

  832. #: ../../../CHANGELOG.md:458

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

  834. msgstr ""

  835. 

  836. #: ../../../CHANGELOG.md:460

  837. msgid "The [Sliding Sync proxy](./docs/configuring-playbook-sliding-sync-proxy.md) has been removed from the playbook, as it's been replaced with a different method (called Simplified Sliding Sync) integrated to newer homeservers by default (**Conduit** homeserver from version `0.6.0` or **Synapse** from version `1.114`)."

  838. msgstr ""

  839. 

  840. #: ../../../CHANGELOG.md:462

  841. msgid "The playbook will let you know if you're using any `matrix_sliding_sync_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the proxy manually](./docs/configuring-playbook-sliding-sync-proxy.md#uninstalling-the-proxy-manually)."

  842. msgstr ""

  843. 

  844. #: ../../../CHANGELOG.md:464

  845. msgid "2026-02-04"

  846. msgstr ""

  847. 

  848. #: ../../../CHANGELOG.md:466

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

  850. msgstr ""

  851. 

  852. #: ../../../CHANGELOG.md:468

  853. msgid "**TLDR**: if you're using the [OpenAI provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai) with [baibot](docs/configuring-playbook-bot-baibot.md), you can now enable [built-in tools](https://github.com/etkecc/baibot/blob/61d18b2/docs/features.md#%EF%B8%8F-built-in-tools-openai-only) (`web_search` and `code_interpreter`) to extend the model's capabilities."

  854. msgstr ""

  855. 

  856. #: ../../../CHANGELOG.md:470

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

  858. msgstr ""

  859. 

  860. #: ../../../CHANGELOG.md:477

  861. msgid "Users who define agents dynamically at runtime will need to [update their agents](https://github.com/etkecc/baibot/blob/61d18b2/docs/agents.md#updating-agents) to enable these tools. See the [baibot v1.14.0 changelog](https://github.com/etkecc/baibot/blob/61d18b2/CHANGELOG.md) for details."

  862. msgstr ""

  863. 

  864. #: ../../../CHANGELOG.md:479

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

  866. msgstr ""

  867. 

  868. #: ../../../CHANGELOG.md:481

  869. msgid "Deployments using [Synapse workers](./docs/configuring-playbook-synapse.md#load-balancing-with-workers) now benefit from improved sync worker routing via a new whoami-based mechanism (making use of the [whoami Matrix Client-Server API](https://spec.matrix.org/v1.17/client-server-api/#get_matrixclientv3accountwhoami))."

  870. msgstr ""

  871. 

  872. #: ../../../CHANGELOG.md:483

  873. msgid "Previously, sticky routing for sync workers relied on parsing usernames from access tokens, which only worked with native Synapse tokens (`syt_<base64 username>_...`). This approach failed for [Matrix Authentication Service](docs/configuring-playbook-matrix-authentication-service.md) (MAS) deployments, where tokens are opaque and don't contain username information. This resulted in device-level stickiness (same token → same worker) rather than user-level stickiness (same user → same worker regardless of device), leading to suboptimal cache utilization on sync workers."

  874. msgstr ""

  875. 

  876. #: ../../../CHANGELOG.md:485

  877. msgid "The new implementation calls Synapse's `/whoami` endpoint to resolve access tokens to usernames, enabling proper user-level sticky routing regardless of the authentication system in use (native Synapse auth, MAS, etc.). Results are cached to minimize overhead."

  878. msgstr ""

  879. 

  880. #: ../../../CHANGELOG.md:487

  881. msgid "This change:"

  882. msgstr ""

  883. 

  884. #: ../../../CHANGELOG.md:488

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

  886. msgstr ""

  887. 

  888. #: ../../../CHANGELOG.md:489

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

  890. msgstr ""

  891. 

  892. #: ../../../CHANGELOG.md:490

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

  894. msgstr ""

  895. 

  896. #: ../../../CHANGELOG.md:491

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

  898. msgstr ""

  899. 

  900. #: ../../../CHANGELOG.md:493

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

  902. msgstr ""

  903. 

  904. #: ../../../CHANGELOG.md:504

  905. msgid "2025-12-09"

  906. msgstr ""

  907. 

  908. #: ../../../CHANGELOG.md:506

  909. msgid "Traefik Cert Dumper upgrade"

  910. msgstr ""

  911. 

  912. #: ../../../CHANGELOG.md:508

  913. msgid "The variable `traefik_certs_dumper_ssl_dir_path` was renamed to `traefik_certs_dumper_ssl_path`. Users who use [their own webserver with Traefik](docs/configuring-playbook-own-webserver.md) may need to adjust their configuration."

  914. msgstr ""

  915. 

  916. #: ../../../CHANGELOG.md:510

  917. msgid "The variable `traefik_certs_dumper_dumped_certificates_dir_path` was renamed to `traefik_certs_dumper_dumped_certificates_path`. Users who use [SRV Server Delegation](docs/howto-srv-server-delegation.md) may need to adjust their configuration."

  918. msgstr ""

  919. 

  920. #: ../../../CHANGELOG.md:512

  921. msgid "2025-11-23"

  922. msgstr ""

  923. 

  924. #: ../../../CHANGELOG.md:514

  925. msgid "Matrix.to support"

  926. msgstr ""

  927. 

  928. #: ../../../CHANGELOG.md:516

  929. msgid "The playbook now supports [Matrix.to](https://github.com/matrix-org/matrix.to) — a simple URL redirection service which powers [matrix.to](https://matrix.to)."

  930. msgstr ""

  931. 

  932. #: ../../../CHANGELOG.md:518

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

  934. msgstr ""

  935. 

  936. #: ../../../CHANGELOG.md:520

  937. msgid "2025-11-09"

  938. msgstr ""

  939. 

  940. #: ../../../CHANGELOG.md:522

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

  942. msgstr ""

  943. 

  944. #: ../../../CHANGELOG.md:524

  945. msgid "[matrix-appservice-webhooks](./docs/configuring-playbook-bridge-appservice-webhooks.md) has been removed from the playbook, as it has been deprecated since more than several years."

  946. msgstr ""

  947. 

  948. #: ../../../CHANGELOG.md:526

  949. msgid "The playbook will let you know if you're using any `matrix_appservice_webhooks_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the bridge manually](./docs/configuring-playbook-bridge-appservice-webhooks.md#uninstalling-the-bridge-manually)."

  950. msgstr ""

  951. 

  952. #: ../../../CHANGELOG.md:528

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

  954. msgstr ""

  955. 

  956. #: ../../../CHANGELOG.md:530

  957. msgid "[mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-facebook.md) and [mautrix-instagram](./docs/configuring-playbook-bridge-mautrix-instagram.md) have been removed from the playbook, as they have been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, integrated to the playbook at [2024-02-19](#2024-02-19)."

  958. msgstr ""

  959. 

  960. #: ../../../CHANGELOG.md:532

  961. #: ../../../CHANGELOG.md:564

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

  963. msgstr ""

  964. 

  965. #: ../../../CHANGELOG.md:534

  966. msgid "`matrix_mautrix_facebook_*`"

  967. msgstr ""

  968. 

  969. #: ../../../CHANGELOG.md:535

  970. msgid "`matrix_mautrix_instagram_*`"

  971. msgstr ""

  972. 

  973. #: ../../../CHANGELOG.md:537

  974. #: ../../../CHANGELOG.md:571

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

  976. msgstr ""

  977. 

  978. #: ../../../CHANGELOG.md:539

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

  980. msgstr ""

  981. 

  982. #: ../../../CHANGELOG.md:540

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

  984. msgstr ""

  985. 

  986. #: ../../../CHANGELOG.md:542

  987. msgid "2025-11-08"

  988. msgstr ""

  989. 

  990. #: ../../../CHANGELOG.md:544

  991. msgid "MatrixZulipBridge support"

  992. msgstr ""

  993. 

  994. #: ../../../CHANGELOG.md:546

  995. msgid "Thanks to [Suguru Hirahara](https://github.com/luixxiul), the playbook now supports the [GearKite/MatrixZulipBridge](https://github.com/GearKite/MatrixZulipBridg) bridge for bridging Matrix to [Zulip](https://zulip.com/)."

  996. msgstr ""

  997. 

  998. #: ../../../CHANGELOG.md:548

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

  1000. msgstr ""

  1001. 

  1002. #: ../../../CHANGELOG.md:550

  1003. msgid "2025-11-07"

  1004. msgstr ""

  1005. 

  1006. #: ../../../CHANGELOG.md:552

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

  1008. msgstr ""

  1009. 

  1010. #: ../../../CHANGELOG.md:554

  1011. msgid "The [matrix-bot-chatgpt](./docs/configuring-playbook-bot-chatgpt.md) has been removed from the playbook, as it has been deprecated since September 2024."

  1012. msgstr ""

  1013. 

  1014. #: ../../../CHANGELOG.md:556

  1015. msgid "The playbook will let you know if you're using any `matrix_bot_chatgpt_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the bot manually](./docs/configuring-playbook-bot-chatgpt.md#uninstalling-matrix-chatgpt-bot-manually)."

  1016. msgstr ""

  1017. 

  1018. #: ../../../CHANGELOG.md:558

  1019. msgid "2025-11-05"

  1020. msgstr ""

  1021. 

  1022. #: ../../../CHANGELOG.md:560

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

  1024. msgstr ""

  1025. 

  1026. #: ../../../CHANGELOG.md:562

  1027. msgid "The MX Puppet bridges for Discord, Instagram, Slack, and Twitter have been removed from the playbook, as they have been unmaintained for more than several years and do not support important features like authenticated media. See [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3867) for the context."

  1028. msgstr ""

  1029. 

  1030. #: ../../../CHANGELOG.md:566

  1031. msgid "`matrix_mx_puppet_discord_*`"

  1032. msgstr ""

  1033. 

  1034. #: ../../../CHANGELOG.md:567

  1035. msgid "`matrix_mx_puppet_instagram_*`"

  1036. msgstr ""

  1037. 

  1038. #: ../../../CHANGELOG.md:568

  1039. msgid "`matrix_mx_puppet_slack_*`"

  1040. msgstr ""

  1041. 

  1042. #: ../../../CHANGELOG.md:569

  1043. msgid "`matrix_mx_puppet_twitter_*`"

  1044. msgstr ""

  1045. 

  1046. #: ../../../CHANGELOG.md:573

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

  1048. msgstr ""

  1049. 

  1050. #: ../../../CHANGELOG.md:574

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

  1052. msgstr ""

  1053. 

  1054. #: ../../../CHANGELOG.md:575

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

  1056. msgstr ""

  1057. 

  1058. #: ../../../CHANGELOG.md:576

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

  1060. msgstr ""

  1061. 

  1062. #: ../../../CHANGELOG.md:578

  1063. msgid "2025-11-04"

  1064. msgstr ""

  1065. 

  1066. #: ../../../CHANGELOG.md:580

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

  1068. msgstr ""

  1069. 

  1070. #: ../../../CHANGELOG.md:582

  1071. msgid "The [go-skype-bridge](./docs/configuring-playbook-bridge-go-skype-bridge.md) has been removed from the playbook, as Skype has been discontinued since the May 2025."

  1072. msgstr ""

  1073. 

  1074. #: ../../../CHANGELOG.md:584

  1075. msgid "The playbook will let you know if you're using any `matrix_go_skype_bridge_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the bridge manually](./docs/configuring-playbook-bridge-go-skype-bridge.md#uninstalling-the-bridge-manually)."

  1076. msgstr ""

  1077. 

  1078. #: ../../../CHANGELOG.md:586

  1079. msgid "2025-10-02"

  1080. msgstr ""

  1081. 

  1082. #: ../../../CHANGELOG.md:588

  1083. msgid "Element Admin support"

  1084. msgstr ""

  1085. 

  1086. #: ../../../CHANGELOG.md:590

  1087. msgid "The playbook now supports [Element Admin](./docs/configuring-playbook-element-admin.md) - a new web-based administration panel for Synapse and [Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md)."

  1088. msgstr ""

  1089. 

  1090. #: ../../../CHANGELOG.md:592

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

  1092. msgstr ""

  1093. 

  1094. #: ../../../CHANGELOG.md:594

  1095. msgid "Deployments that don't rely on Matrix Authentication Service are unlikely to find anything useful in Element Admin right now (it's too basic in its current form)."

  1096. msgstr ""

  1097. 

  1098. #: ../../../CHANGELOG.md:597

  1099. msgid "2025-04-26"

  1100. msgstr ""

  1101. 

  1102. #: ../../../CHANGELOG.md:599

  1103. msgid "Continuwuity support"

  1104. msgstr ""

  1105. 

  1106. #: ../../../CHANGELOG.md:601

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

  1108. msgstr ""

  1109. 

  1110. #: ../../../CHANGELOG.md:603

  1111. msgid "Continuwuity is a fork of [conduwuit](./docs/configuring-playbook-conduwuit.md), which the playbook also supports. It appears that conduwuit has been abandoned and various forks (like Continuwuity, [Tuwunel](https://github.com/matrix-construct/tuwunel) and possibly others) are continuing in its path."

  1112. msgstr ""

  1113. 

  1114. #: ../../../CHANGELOG.md:607

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

  1116. msgstr ""

  1117. 

  1118. #: ../../../CHANGELOG.md:609

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

  1120. msgstr ""

  1121. 

  1122. #: ../../../CHANGELOG.md:610

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

  1124. msgstr ""

  1125. 

  1126. #: ../../../CHANGELOG.md:612

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

  1128. msgstr ""

  1129. 

  1130. #: ../../../CHANGELOG.md:615

  1131. msgid "2025-04-09"

  1132. msgstr ""

  1133. 

  1134. #: ../../../CHANGELOG.md:617

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

  1136. msgstr ""

  1137. 

  1138. #: ../../../CHANGELOG.md:619

  1139. msgid "Because all Element clients (Element Web and Element X mobile) now embed and use their own Element Call frontend application (and not the one hosted via the playbook), it makes little sense for the playbook to self-host the Element Call frontend for you. Setting up the frontend requires an additional hostname (DNS setup) and it won't be used by Element clients anyway, so **we now recommend not installing the Element Call frontend**."

  1140. msgstr ""

  1141. 

  1142. #: ../../../CHANGELOG.md:621

  1143. msgid "💡 A reason you may wish to continue installing the Element Call frontend (despite Matrix clients not making use of it), is if you need to use it standalone - directly via a browser (without a Matrix client)."

  1144. msgstr ""

  1145. 

  1146. #: ../../../CHANGELOG.md:623

  1147. msgid "The playbook now lets you [Decide between Element Call vs just the Matrix RTC stack](./docs/configuring-playbook-element-call.md#decide-between-element-call-vs-just-the-matrix-rtc-stack)."

  1148. msgstr ""

  1149. 

  1150. #: ../../../CHANGELOG.md:625

  1151. msgid "If you've already installed Element Call (via `matrix_element_call_enabled: true`), you can switch to installing just the [Matrix RTC (Real-Time Communication) stack](./docs/configuring-playbook-matrix-rtc.md) (all supporting services **without the Element Call frontend**) by:"

  1152. msgstr ""

  1153. 

  1154. #: ../../../CHANGELOG.md:627

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

  1156. msgstr ""

  1157. 

  1158. #: ../../../CHANGELOG.md:634

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

  1160. msgstr ""

  1161. 

  1162. #: ../../../CHANGELOG.md:636

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

  1164. msgstr ""

  1165. 

  1166. #: ../../../CHANGELOG.md:639

  1167. msgid "2025-03-15"

  1168. msgstr ""

  1169. 

  1170. #: ../../../CHANGELOG.md:641

  1171. msgid "Element Call support"

  1172. msgstr ""

  1173. 

  1174. #: ../../../CHANGELOG.md:643

  1175. msgid "The playbook now supports [Element Call](https://github.com/element-hq/element-call) as an optional feature. Thanks to [wjbeckett](https://github.com/wjbeckett) for getting us started via [PR#3562](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3562)."

  1176. msgstr ""

  1177. 

  1178. #: ../../../CHANGELOG.md:645

  1179. msgid "Element Call is a native Matrix video conferencing application developed by [Element](https://element.io/) that has the goal of replacing [Jitsi](./docs/configuring-playbook-jitsi.md) and the old WebRTC stack used in previous Element versions."

  1180. msgstr ""

  1181. 

  1182. #: ../../../CHANGELOG.md:647

  1183. msgid "💡 For now, Element Call is only supported with the [Synapse](docs/configuring-playbook-synapse.md) homeserver (with [federation](docs/configuring-playbook-federation.md) enabled) and [Element Web](docs/configuring-playbook-client-element-web.md) and Element X mobile clients. See the [Prerequisites](docs/configuring-playbook-element-call.md#prerequisites) section of the [Element Call documentation](docs/configuring-playbook-element-call.md) for more details."

  1184. msgstr ""

  1185. 

  1186. #: ../../../CHANGELOG.md:649

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

  1188. msgstr ""

  1189. 

  1190. #: ../../../CHANGELOG.md:652

  1191. msgid "2025-03-08"

  1192. msgstr ""

  1193. 

  1194. #: ../../../CHANGELOG.md:654

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

  1196. msgstr ""

  1197. 

  1198. #: ../../../CHANGELOG.md:656

  1199. msgid "Our [default example configuration](./examples/vars.yml) and [Configuring DNS](./docs/configuring-dns.md) guides now recommend enabling [IPv6](https://en.wikipedia.org/wiki/IPv6) support. We recommend that everyone enables IPv6 support for their Matrix server, even if they don't have IPv6 connectivity yet."

  1200. msgstr ""

  1201. 

  1202. #: ../../../CHANGELOG.md:658

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

  1204. msgstr ""

  1205. 

  1206. #: ../../../CHANGELOG.md:660

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

  1208. msgstr ""

  1209. 

  1210. #: ../../../CHANGELOG.md:662

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

  1212. msgstr ""

  1213. 

  1214. #: ../../../CHANGELOG.md:663

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

  1216. msgstr ""

  1217. 

  1218. #: ../../../CHANGELOG.md:664

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

  1220. msgstr ""

  1221. 

  1222. #: ../../../CHANGELOG.md:665

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

  1224. msgstr ""

  1225. 

  1226. #: ../../../CHANGELOG.md:666

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

  1228. msgstr ""

  1229. 

  1230. #: ../../../CHANGELOG.md:668

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

  1232. msgstr ""

  1233. 

  1234. #: ../../../CHANGELOG.md:670

  1235. msgid "2025-02-26"

  1236. msgstr ""

  1237. 

  1238. #: ../../../CHANGELOG.md:672

  1239. msgid "🪦 Bye-bye, Email2Matrix"

  1240. msgstr ""

  1241. 

  1242. #: ../../../CHANGELOG.md:674

  1243. msgid "The [Email2Matrix](./docs/configuring-playbook-email2matrix.md) service has been superseded by the [Postmoogle](./docs/configuring-playbook-bridge-postmoogle.md) bridge for a long time now and was completely removed from the playbook today."

  1244. msgstr ""

  1245. 

  1246. #: ../../../CHANGELOG.md:676

  1247. msgid "If you still have the Email2Matrix component installed on your Matrix server, the playbook can no longer help you uninstall it and you will need to do it manually as described in the [Uninstalling Email2Matrix manually](./docs/configuring-playbook-email2matrix.md#uninstalling-email2matrix-manually) section of the documentation. The playbook will warn you if there are any `matrix_email2matrix_*` variables still remaining in your configuration."

  1248. msgstr ""

  1249. 

  1250. #: ../../../CHANGELOG.md:679

  1251. msgid "2025-02-23"

  1252. msgstr ""

  1253. 

  1254. #: ../../../CHANGELOG.md:681

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

  1256. msgstr ""

  1257. 

  1258. #: ../../../CHANGELOG.md:683

  1259. msgid "Recently, we made the playbook [default to exposing the Coturn STUN port (3478) only over TCP](#the-playbook-now-defaults-to-exposing-the-coturn-stun-port-3478-only-over-tcp) to reduce the severity of DDoS amplification/reflection attacks."

  1260. msgstr ""

  1261. 

  1262. #: ../../../CHANGELOG.md:685

  1263. msgid "It seems like old Element clients on mobile devices only support talking to the STUN port over UDP, not TCP. To accommodate such ancient clients, we're now **reversing this change** and **defaulting to exposing the Coturn STUN port (3478) over UDP once again**."

  1264. msgstr ""

  1265. 

  1266. #: ../../../CHANGELOG.md:688

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

  1268. msgstr ""

  1269. 

  1270. #: ../../../CHANGELOG.md:690

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

  1272. msgstr ""

  1273. 

  1274. #: ../../../CHANGELOG.md:692

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

  1276. msgstr ""

  1277. 

  1278. #: ../../../CHANGELOG.md:694

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

  1280. msgstr ""

  1281. 

  1282. #: ../../../CHANGELOG.md:696

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

  1284. msgstr ""

  1285. 

  1286. #: ../../../CHANGELOG.md:702

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

  1288. msgstr ""

  1289. 

  1290. #: ../../../CHANGELOG.md:704

  1291. msgid "2025-02-21"

  1292. msgstr ""

  1293. 

  1294. #: ../../../CHANGELOG.md:706

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

  1296. msgstr ""

  1297. 

  1298. #: ../../../CHANGELOG.md:708

  1299. msgid "We landed [initial IPv6 support](#initial-work-on-ipv6-support) in the past via a `devture_systemd_docker_base_ipv6_enabled` variable that one had to toggle to `true`."

  1300. msgstr ""

  1301. 

  1302. #: ../../../CHANGELOG.md:710

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

  1304. msgstr ""

  1305. 

  1306. #: ../../../CHANGELOG.md:712

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

  1308. msgstr ""

  1309. 

  1310. #: ../../../CHANGELOG.md:713

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

  1312. msgstr ""

  1313. 

  1314. #: ../../../CHANGELOG.md:715

  1315. msgid "Since Docker 27.0.1's [changes to how it handles IPv6](https://docs.docker.com/engine/release-notes/27/#ipv6), **adjusting the Docker daemon's configuration is no longer necessary**, because:"

  1316. msgstr ""

  1317. 

  1318. #: ../../../CHANGELOG.md:716

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

  1320. msgstr ""

  1321. 

  1322. #: ../../../CHANGELOG.md:717

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

  1324. msgstr ""

  1325. 

  1326. #: ../../../CHANGELOG.md:719

  1327. msgid "In light of this, we're introducing a new variable (`devture_systemd_docker_base_ipv6_daemon_options_changing_enabled`) for controlling if IPv6 should be force-enabled in the Docker daemon's configuration options. Since most people should be on a modern enough Docker daemon version which doesn't require such changes, this variable defaults to `false`."

  1328. msgstr ""

  1329. 

  1330. #: ../../../CHANGELOG.md:722

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

  1332. msgstr ""

  1333. 

  1334. #: ../../../CHANGELOG.md:724

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

  1336. msgstr ""

  1337. 

  1338. #: ../../../CHANGELOG.md:725

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

  1340. msgstr ""

  1341. 

  1342. #: ../../../CHANGELOG.md:726

  1343. msgid "✅ .. and you're on a modern enough Docker version (which you most likely are): the playbook will no longer mess with your Docker daemon options. You're unaffected."

  1344. msgstr ""

  1345. 

  1346. #: ../../../CHANGELOG.md:727

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

  1348. msgstr ""

  1349. 

  1350. #: ../../../CHANGELOG.md:738

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

  1352. msgstr ""

  1353. 

  1354. #: ../../../CHANGELOG.md:740

  1355. msgid "Thanks to [Zepmann](https://github.com/Zepmann), the playbook now supports bridging to [Bluesky](https://bsky.app/) via [mautrix-bluesky](https://github.com/mautrix/bluesky)."

  1356. msgstr ""

  1357. 

  1358. #: ../../../CHANGELOG.md:742

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

  1360. msgstr ""

  1361. 

  1362. #: ../../../CHANGELOG.md:745

  1363. msgid "2025-02-19"

  1364. msgstr ""

  1365. 

  1366. #: ../../../CHANGELOG.md:747

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

  1368. msgstr ""

  1369. 

  1370. #: ../../../CHANGELOG.md:749

  1371. msgid "We've previously done some work to **decrease the severity** of DDoS amplification attacks done through the [Coturn](./docs/configuring-playbook-turn.md)'s STUN port (2.8x -> 1.6x) as reported in [coturn: Lower DDoS amplification/reflection factor from 2.8 to 1.6 #2592](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2592)."

  1372. msgstr ""

  1373. 

  1374. #: ../../../CHANGELOG.md:751

  1375. msgid "To **completely eliminate the problem** of DDoS amplification attacks done through the [Coturn](./docs/configuring-playbook-turn.md) STUN port even further (read more about this in [this article](https://stormwall.network/resources/blog/protect-against-ddos-based-on-stun-exploit)), the playbook now **disables exposure of the Coturn STUN port (`3478`) over UDP**. This is a bit heavy-handed, but is probably the only way to completely eliminate the problem."

  1376. msgstr ""

  1377. 

  1378. #: ../../../CHANGELOG.md:753

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

  1380. msgstr ""

  1381. 

  1382. #: ../../../CHANGELOG.md:755

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

  1384. msgstr ""

  1385. 

  1386. #: ../../../CHANGELOG.md:757

  1387. msgid "If you'd like the Coturn STUN port to be exposed over UDP like before, you can revert to the previous behavior by using the following configuration in your `vars.yml` file:"

  1388. msgstr ""

  1389. 

  1390. #: ../../../CHANGELOG.md:764

  1391. msgid "People running Coturn directly on the `host` network (using `coturn_container_network: host`) will still have the STUN port exposed over UDP, as port exposure is done directly via Coturn and not via Docker. In such cases, the playbook cannot prevent `3478/udp` port exposure and you'd need to do it in another way (separate firewall rule, etc)."

  1392. msgstr ""

  1393. 

  1394. #: ../../../CHANGELOG.md:767

  1395. msgid "2025-02-17"

  1396. msgstr ""

  1397. 

  1398. #: ../../../CHANGELOG.md:769

  1399. msgid "FluffyChat Web support"

  1400. msgstr ""

  1401. 

  1402. #: ../../../CHANGELOG.md:771

  1403. msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports [FluffyChat Web](https://github.com/krille-chan/fluffychat) as an additional Matrix client you can self-host."

  1404. msgstr ""

  1405. 

  1406. #: ../../../CHANGELOG.md:773

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

  1408. msgstr ""

  1409. 

  1410. #: ../../../CHANGELOG.md:776

  1411. msgid "2025-02-03"

  1412. msgstr ""

  1413. 

  1414. #: ../../../CHANGELOG.md:778

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

  1416. msgstr ""

  1417. 

  1418. #: ../../../CHANGELOG.md:780

  1419. msgid "The [mautrix-hangouts](./docs/configuring-playbook-bridge-mautrix-hangouts.md) bridge has been deprecated in the playbook since December 2024 and finally got completely removed from the playbook in February 2025."

  1420. msgstr ""

  1421. 

  1422. #: ../../../CHANGELOG.md:782

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

  1424. msgstr ""

  1425. 

  1426. #: ../../../CHANGELOG.md:784

  1427. msgid "The playbook will let you know if you're using any `matrix_mautrix_hangouts_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the bridge manually](./docs/configuring-playbook-bridge-mautrix-hangouts.md#uninstalling-the-bridge-manually)."

  1428. msgstr ""

  1429. 

  1430. #: ../../../CHANGELOG.md:787

  1431. msgid "2025-01-27"

  1432. msgstr ""

  1433. 

  1434. #: ../../../CHANGELOG.md:789

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

  1436. msgstr ""

  1437. 

  1438. #: ../../../CHANGELOG.md:791

  1439. msgid "**TLDR**: The playbook now exclusively uses Valkey as its Redis-compatible memorystore implementation, removing support for Redis and KeyDB. Most users are unaffected by this change unless they explicitly configured Redis or KeyDB variables. Only users that were explicitly defining `redis_*` or `keydb_*` variables will need to update their configuration to use `valkey_*` variables instead."

  1440. msgstr ""

  1441. 

  1442. #: ../../../CHANGELOG.md:793

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

  1444. msgstr ""

  1445. 

  1446. #: ../../../CHANGELOG.md:795

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

  1448. msgstr ""

  1449. 

  1450. #: ../../../CHANGELOG.md:796

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

  1452. msgstr ""

  1453. 

  1454. #: ../../../CHANGELOG.md:797

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

  1456. msgstr ""

  1457. 

  1458. #: ../../../CHANGELOG.md:799

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

  1460. msgstr ""

  1461. 

  1462. #: ../../../CHANGELOG.md:801

  1463. msgid "removing Redis and KeyDB support entirely"

  1464. msgstr ""

  1465. 

  1466. #: ../../../CHANGELOG.md:802

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

  1468. msgstr ""

  1469. 

  1470. #: ../../../CHANGELOG.md:804

  1471. msgid "To update your configuration:"

  1472. msgstr ""

  1473. 

  1474. #: ../../../CHANGELOG.md:806

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

  1476. msgstr ""

  1477. 

  1478. #: ../../../CHANGELOG.md:807

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

  1480. msgstr ""

  1481. 

  1482. #: ../../../CHANGELOG.md:810

  1483. msgid "2025-01-19"

  1484. msgstr ""

  1485. 

  1486. #: ../../../CHANGELOG.md:812

  1487. msgid "conduwuit support"

  1488. msgstr ""

  1489. 

  1490. #: ../../../CHANGELOG.md:814

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

  1492. msgstr ""

  1493. 

  1494. #: ../../../CHANGELOG.md:816

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

  1496. msgstr ""

  1497. 

  1498. #: ../../../CHANGELOG.md:820

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

  1500. msgstr ""

  1501. 

  1502. #: ../../../CHANGELOG.md:822

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

  1504. msgstr ""

  1505. 

  1506. #: ../../../CHANGELOG.md:825

  1507. msgid "2025-01-14"

  1508. msgstr ""

  1509. 

  1510. #: ../../../CHANGELOG.md:827

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

  1512. msgstr ""

  1513. 

  1514. #: ../../../CHANGELOG.md:829

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

  1516. msgstr ""

  1517. 

  1518. #: ../../../CHANGELOG.md:831

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

  1520. msgstr ""

  1521. 

  1522. #: ../../../CHANGELOG.md:833

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

  1524. msgstr ""

  1525. 

  1526. #: ../../../CHANGELOG.md:835

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

  1528. msgstr ""

  1529. 

  1530. #: ../../../CHANGELOG.md:837

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

  1532. msgstr ""

  1533. 

  1534. #: ../../../CHANGELOG.md:845

  1535. msgid "2024-11-26"

  1536. msgstr ""

  1537. 

  1538. #: ../../../CHANGELOG.md:847

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

  1540. msgstr ""

  1541. 

  1542. #: ../../../CHANGELOG.md:849

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

  1544. msgstr ""

  1545. 

  1546. #: ../../../CHANGELOG.md:851

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

  1548. msgstr ""

  1549. 

  1550. #: ../../../CHANGELOG.md:853

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

  1552. msgstr ""

  1553. 

  1554. #: ../../../CHANGELOG.md:855

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

  1556. msgstr ""

  1557. 

  1558. #: ../../../CHANGELOG.md:857

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

  1560. msgstr ""

  1561. 

  1562. #: ../../../CHANGELOG.md:859

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

  1564. msgstr ""

  1565. 

  1566. #: ../../../CHANGELOG.md:861

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

  1568. msgstr ""

  1569. 

  1570. #: ../../../CHANGELOG.md:864

  1571. msgid "2024-11-23"

  1572. msgstr ""

  1573. 

  1574. #: ../../../CHANGELOG.md:866

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

  1576. msgstr ""

  1577. 

  1578. #: ../../../CHANGELOG.md:868

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

  1580. msgstr ""

  1581. 

  1582. #: ../../../CHANGELOG.md:870

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

  1584. msgstr ""

  1585. 

  1586. #: ../../../CHANGELOG.md:872

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

  1588. msgstr ""

  1589. 

  1590. #: ../../../CHANGELOG.md:874

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

  1592. msgstr ""

  1593. 

  1594. #: ../../../CHANGELOG.md:876

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

  1596. msgstr ""

  1597. 

  1598. #: ../../../CHANGELOG.md:878

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

  1600. msgstr ""

  1601. 

  1602. #: ../../../CHANGELOG.md:880

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

  1604. msgstr ""

  1605. 

  1606. #: ../../../CHANGELOG.md:882

  1607. #: ../../../CHANGELOG.md:1222

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

  1609. msgstr ""

  1610. 

  1611. #: ../../../CHANGELOG.md:893

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

  1613. msgstr ""

  1614. 

  1615. #: ../../../CHANGELOG.md:903

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

  1617. msgstr ""

  1618. 

  1619. #: ../../../CHANGELOG.md:906

  1620. msgid "2024-11-14"

  1621. msgstr ""

  1622. 

  1623. #: ../../../CHANGELOG.md:908

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

  1625. msgstr ""

  1626. 

  1627. #: ../../../CHANGELOG.md:910

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

  1629. msgstr ""

  1630. 

  1631. #: ../../../CHANGELOG.md:912

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

  1633. msgstr ""

  1634. 

  1635. #: ../../../CHANGELOG.md:914

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

  1637. msgstr ""

  1638. 

  1639. #: ../../../CHANGELOG.md:916

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

  1641. msgstr ""

  1642. 

  1643. #: ../../../CHANGELOG.md:918

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

  1645. msgstr ""

  1646. 

  1647. #: ../../../CHANGELOG.md:920

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

  1649. msgstr ""

  1650. 

  1651. #: ../../../CHANGELOG.md:921

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

  1653. msgstr ""

  1654. 

  1655. #: ../../../CHANGELOG.md:922

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

  1657. msgstr ""

  1658. 

  1659. #: ../../../CHANGELOG.md:924

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

  1661. msgstr ""

  1662. 

  1663. #: ../../../CHANGELOG.md:926

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

  1665. msgstr ""

  1666. 

  1667. #: ../../../CHANGELOG.md:928

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

  1669. msgstr ""

  1670. 

  1671. #: ../../../CHANGELOG.md:930

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

  1673. msgstr ""

  1674. 

  1675. #: ../../../CHANGELOG.md:932

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

  1677. msgstr ""

  1678. 

  1679. #: ../../../CHANGELOG.md:934

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

  1681. msgstr ""

  1682. 

  1683. #: ../../../CHANGELOG.md:945

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

  1685. msgstr ""

  1686. 

  1687. #: ../../../CHANGELOG.md:948

  1688. msgid "2024-11-08"

  1689. msgstr ""

  1690. 

  1691. #: ../../../CHANGELOG.md:950

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

  1693. msgstr ""

  1694. 

  1695. #: ../../../CHANGELOG.md:952

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

  1697. msgstr ""

  1698. 

  1699. #: ../../../CHANGELOG.md:954

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

  1701. msgstr ""

  1702. 

  1703. #: ../../../CHANGELOG.md:956

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

  1705. msgstr ""

  1706. 

  1707. #: ../../../CHANGELOG.md:959

  1708. msgid "2024-10-28"

  1709. msgstr ""

  1710. 

  1711. #: ../../../CHANGELOG.md:961

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

  1713. msgstr ""

  1714. 

  1715. #: ../../../CHANGELOG.md:963

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

  1717. msgstr ""

  1718. 

  1719. #: ../../../CHANGELOG.md:965

  1720. msgid "2024-10-19"

  1721. msgstr ""

  1722. 

  1723. #: ../../../CHANGELOG.md:967

  1724. msgid "Support for Matrix Authentication Service"

  1725. msgstr ""

  1726. 

  1727. #: ../../../CHANGELOG.md:969

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

  1729. msgstr ""

  1730. 

  1731. #: ../../../CHANGELOG.md:971

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

  1733. msgstr ""

  1734. 

  1735. #: ../../../CHANGELOG.md:973

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

  1737. msgstr ""

  1738. 

  1739. #: ../../../CHANGELOG.md:975

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

  1741. msgstr ""

  1742. 

  1743. #: ../../../CHANGELOG.md:978

  1744. msgid "2024-09-27"

  1745. msgstr ""

  1746. 

  1747. #: ../../../CHANGELOG.md:980

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

  1749. msgstr ""

  1750. 

  1751. #: ../../../CHANGELOG.md:982

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

  1753. msgstr ""

  1754. 

  1755. #: ../../../CHANGELOG.md:984

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

  1757. msgstr ""

  1758. 

  1759. #: ../../../CHANGELOG.md:986

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

  1761. msgstr ""

  1762. 

  1763. #: ../../../CHANGELOG.md:988

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

  1765. msgstr ""

  1766. 

  1767. #: ../../../CHANGELOG.md:989

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

  1769. msgstr ""

  1770. 

  1771. #: ../../../CHANGELOG.md:994

  1772. msgid "2024-09-12"

  1773. msgstr ""

  1774. 

  1775. #: ../../../CHANGELOG.md:996

  1776. msgid "Support for baibot"

  1777. msgstr ""

  1778. 

  1779. #: ../../../CHANGELOG.md:998

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

  1781. msgstr ""

  1782. 

  1783. #: ../../../CHANGELOG.md:1000

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

  1785. msgstr ""

  1786. 

  1787. #: ../../../CHANGELOG.md:1002

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

  1789. msgstr ""

  1790. 

  1791. #: ../../../CHANGELOG.md:1004

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

  1793. msgstr ""

  1794. 

  1795. #: ../../../CHANGELOG.md:1006

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

  1797. msgstr ""

  1798. 

  1799. #: ../../../CHANGELOG.md:1008

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

  1801. msgstr ""

  1802. 

  1803. #: ../../../CHANGELOG.md:1010

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

  1805. msgstr ""

  1806. 

  1807. #: ../../../CHANGELOG.md:1012

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

  1809. msgstr ""

  1810. 

  1811. #: ../../../CHANGELOG.md:1014

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

  1813. msgstr ""

  1814. 

  1815. #: ../../../CHANGELOG.md:1027

  1816. msgid "2024-08-17"

  1817. msgstr ""

  1818. 

  1819. #: ../../../CHANGELOG.md:1029

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

  1821. msgstr ""

  1822. 

  1823. #: ../../../CHANGELOG.md:1031

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

  1825. msgstr ""

  1826. 

  1827. #: ../../../CHANGELOG.md:1033

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

  1829. msgstr ""

  1830. 

  1831. #: ../../../CHANGELOG.md:1035

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

  1833. msgstr ""

  1834. 

  1835. #: ../../../CHANGELOG.md:1037

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

  1837. msgstr ""

  1838. 

  1839. #: ../../../CHANGELOG.md:1039

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

  1841. msgstr ""

  1842. 

  1843. #: ../../../CHANGELOG.md:1045

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

  1845. msgstr ""

  1846. 

  1847. #: ../../../CHANGELOG.md:1047

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

  1849. msgstr ""

  1850. 

  1851. #: ../../../CHANGELOG.md:1050

  1852. msgid "2024-08-15"

  1853. msgstr ""

  1854. 

  1855. #: ../../../CHANGELOG.md:1052

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

  1857. msgstr ""

  1858. 

  1859. #: ../../../CHANGELOG.md:1054

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

  1861. msgstr ""

  1862. 

  1863. #: ../../../CHANGELOG.md:1056

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

  1865. msgstr ""

  1866. 

  1867. #: ../../../CHANGELOG.md:1058

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

  1869. msgstr ""

  1870. 

  1871. #: ../../../CHANGELOG.md:1060

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

  1873. msgstr ""

  1874. 

  1875. #: ../../../CHANGELOG.md:1063

  1876. msgid "2024-08-08"

  1877. msgstr ""

  1878. 

  1879. #: ../../../CHANGELOG.md:1065

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

  1881. msgstr ""

  1882. 

  1883. #: ../../../CHANGELOG.md:1067

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

  1885. msgstr ""

  1886. 

  1887. #: ../../../CHANGELOG.md:1069

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

  1889. msgstr ""

  1890. 

  1891. #: ../../../CHANGELOG.md:1071

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

  1893. msgstr ""

  1894. 

  1895. #: ../../../CHANGELOG.md:1077

  1896. msgid "2024-07-25"

  1897. msgstr ""

  1898. 

  1899. #: ../../../CHANGELOG.md:1079

  1900. msgid "synapse-usage-exporter support"

  1901. msgstr ""

  1902. 

  1903. #: ../../../CHANGELOG.md:1081

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

  1905. msgstr ""

  1906. 

  1907. #: ../../../CHANGELOG.md:1083

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

  1909. msgstr ""

  1910. 

  1911. #: ../../../CHANGELOG.md:1086

  1912. msgid "2024-07-06"

  1913. msgstr ""

  1914. 

  1915. #: ../../../CHANGELOG.md:1088

  1916. msgid "matrix-alertmanager-receiver support"

  1917. msgstr ""

  1918. 

  1919. #: ../../../CHANGELOG.md:1090

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

  1921. msgstr ""

  1922. 

  1923. #: ../../../CHANGELOG.md:1092

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

  1925. msgstr ""

  1926. 

  1927. #: ../../../CHANGELOG.md:1094

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

  1929. msgstr ""

  1930. 

  1931. #: ../../../CHANGELOG.md:1096

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

  1933. msgstr ""

  1934. 

  1935. #: ../../../CHANGELOG.md:1098

  1936. msgid "Traefik v3"

  1937. msgstr ""

  1938. 

  1939. #: ../../../CHANGELOG.md:1100

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

  1941. msgstr ""

  1942. 

  1943. #: ../../../CHANGELOG.md:1102

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

  1945. msgstr ""

  1946. 

  1947. #: ../../../CHANGELOG.md:1104

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

  1949. msgstr ""

  1950. 

  1951. #: ../../../CHANGELOG.md:1106

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

  1953. msgstr ""

  1954. 

  1955. #: ../../../CHANGELOG.md:1108

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

  1957. msgstr ""

  1958. 

  1959. #: ../../../CHANGELOG.md:1110

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

  1961. msgstr ""

  1962. 

  1963. #: ../../../CHANGELOG.md:1112

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

  1965. msgstr ""

  1966. 

  1967. #: ../../../CHANGELOG.md:1114

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

  1969. msgstr ""

  1970. 

  1971. #: ../../../CHANGELOG.md:1116

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

  1973. msgstr ""

  1974. 

  1975. #: ../../../CHANGELOG.md:1118

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

  1977. msgstr ""

  1978. 

  1979. #: ../../../CHANGELOG.md:1120

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

  1981. msgstr ""

  1982. 

  1983. #: ../../../CHANGELOG.md:1122

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

  1985. msgstr ""

  1986. 

  1987. #: ../../../CHANGELOG.md:1124

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

  1989. msgstr ""

  1990. 

  1991. #: ../../../CHANGELOG.md:1138

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

  1993. msgstr ""

  1994. 

  1995. #: ../../../CHANGELOG.md:1151

  1996. msgid "2024-07-01"

  1997. msgstr ""

  1998. 

  1999. #: ../../../CHANGELOG.md:1153

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

  2001. msgstr ""

  2002. 

  2003. #: ../../../CHANGELOG.md:1155

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

  2005. msgstr ""

  2006. 

  2007. #: ../../../CHANGELOG.md:1157

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

  2009. msgstr ""

  2010. 

  2011. #: ../../../CHANGELOG.md:1159

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

  2013. msgstr ""

  2014. 

  2015. #: ../../../CHANGELOG.md:1167

  2016. msgid "2024-06-25"

  2017. msgstr ""

  2018. 

  2019. #: ../../../CHANGELOG.md:1169

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

  2021. msgstr ""

  2022. 

  2023. #: ../../../CHANGELOG.md:1171

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

  2025. msgstr ""

  2026. 

  2027. #: ../../../CHANGELOG.md:1173

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

  2029. msgstr ""

  2030. 

  2031. #: ../../../CHANGELOG.md:1175

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

  2033. msgstr ""

  2034. 

  2035. #: ../../../CHANGELOG.md:1177

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

  2037. msgstr ""

  2038. 

  2039. #: ../../../CHANGELOG.md:1179

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

  2041. msgstr ""

  2042. 

  2043. #: ../../../CHANGELOG.md:1181

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

  2045. msgstr ""

  2046. 

  2047. #: ../../../CHANGELOG.md:1183

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

  2049. msgstr ""

  2050. 

  2051. #: ../../../CHANGELOG.md:1186

  2052. msgid "2024-06-22"

  2053. msgstr ""

  2054. 

  2055. #: ../../../CHANGELOG.md:1188

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

  2057. msgstr ""

  2058. 

  2059. #: ../../../CHANGELOG.md:1190

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

  2061. msgstr ""

  2062. 

  2063. #: ../../../CHANGELOG.md:1192

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

  2065. msgstr ""

  2066. 

  2067. #: ../../../CHANGELOG.md:1194

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

  2069. msgstr ""

  2070. 

  2071. #: ../../../CHANGELOG.md:1197

  2072. msgid "2024-06-03"

  2073. msgstr ""

  2074. 

  2075. #: ../../../CHANGELOG.md:1199

  2076. msgid "WeChat bridging support"

  2077. msgstr ""

  2078. 

  2079. #: ../../../CHANGELOG.md:1201

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

  2081. msgstr ""

  2082. 

  2083. #: ../../../CHANGELOG.md:1203

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

  2085. msgstr ""

  2086. 

  2087. #: ../../../CHANGELOG.md:1206

  2088. msgid "2024-03-26"

  2089. msgstr ""

  2090. 

  2091. #: ../../../CHANGELOG.md:1208

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

  2093. msgstr ""

  2094. 

  2095. #: ../../../CHANGELOG.md:1210

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

  2097. msgstr ""

  2098. 

  2099. #: ../../../CHANGELOG.md:1212

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

  2101. msgstr ""

  2102. 

  2103. #: ../../../CHANGELOG.md:1214

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

  2105. msgstr ""

  2106. 

  2107. #: ../../../CHANGELOG.md:1216

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

  2109. msgstr ""

  2110. 

  2111. #: ../../../CHANGELOG.md:1218

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

  2113. msgstr ""

  2114. 

  2115. #: ../../../CHANGELOG.md:1220

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

  2117. msgstr ""

  2118. 

  2119. #: ../../../CHANGELOG.md:1231

  2120. msgid "2024-03-24"

  2121. msgstr ""

  2122. 

  2123. #: ../../../CHANGELOG.md:1233

  2124. msgid "Initial work on IPv6 support"

  2125. msgstr ""

  2126. 

  2127. #: ../../../CHANGELOG.md:1235

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

  2129. msgstr ""

  2130. 

  2131. #: ../../../CHANGELOG.md:1237

  2132. msgid "It should be noted that:"

  2133. msgstr ""

  2134. 

  2135. #: ../../../CHANGELOG.md:1239

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

  2137. msgstr ""

  2138. 

  2139. #: ../../../CHANGELOG.md:1240

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

  2141. msgstr ""

  2142. 

  2143. #: ../../../CHANGELOG.md:1241

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

  2145. msgstr ""

  2146. 

  2147. #: ../../../CHANGELOG.md:1243

  2148. msgid "Pantalaimon support"

  2149. msgstr ""

  2150. 

  2151. #: ../../../CHANGELOG.md:1245

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

  2153. msgstr ""

  2154. 

  2155. #: ../../../CHANGELOG.md:1247

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

  2157. msgstr ""

  2158. 

  2159. #: ../../../CHANGELOG.md:1250

  2160. msgid "2024-03-05"

  2161. msgstr ""

  2162. 

  2163. #: ../../../CHANGELOG.md:1252

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

  2165. msgstr ""

  2166. 

  2167. #: ../../../CHANGELOG.md:1254

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

  2169. msgstr ""

  2170. 

  2171. #: ../../../CHANGELOG.md:1256

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

  2173. msgstr ""

  2174. 

  2175. #: ../../../CHANGELOG.md:1258

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

  2177. msgstr ""

  2178. 

  2179. #: ../../../CHANGELOG.md:1261

  2180. msgid "2024-02-19"

  2181. msgstr ""

  2182. 

  2183. #: ../../../CHANGELOG.md:1263

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

  2185. msgstr ""

  2186. 

  2187. #: ../../../CHANGELOG.md:1265

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

  2189. msgstr ""

  2190. 

  2191. #: ../../../CHANGELOG.md:1267

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

  2193. msgstr ""

  2194. 

  2195. #: ../../../CHANGELOG.md:1269

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

  2197. msgstr ""

  2198. 

  2199. #: ../../../CHANGELOG.md:1271

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

  2201. msgstr ""

  2202. 

  2203. #: ../../../CHANGELOG.md:1273

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

  2205. msgstr ""

  2206. 

  2207. #: ../../../CHANGELOG.md:1275

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

  2209. msgstr ""

  2210. 

  2211. #: ../../../CHANGELOG.md:1278

  2212. msgid "2024-02-14"

  2213. msgstr ""

  2214. 

  2215. #: ../../../CHANGELOG.md:1280

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

  2217. msgstr ""

  2218. 

  2219. #: ../../../CHANGELOG.md:1282

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

  2221. msgstr ""

  2222. 

  2223. #: ../../../CHANGELOG.md:1284

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

  2225. msgstr ""

  2226. 

  2227. #: ../../../CHANGELOG.md:1286

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

  2229. msgstr ""

  2230. 

  2231. #: ../../../CHANGELOG.md:1288

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

  2233. msgstr ""

  2234. 

  2235. #: ../../../CHANGELOG.md:1289

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

  2237. msgstr ""

  2238. 

  2239. #: ../../../CHANGELOG.md:1290

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

  2241. msgstr ""

  2242. 

  2243. #: ../../../CHANGELOG.md:1292

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

  2245. msgstr ""

  2246. 

  2247. #: ../../../CHANGELOG.md:1294

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

  2249. msgstr ""

  2250. 

  2251. #: ../../../CHANGELOG.md:1297

  2252. msgid "2024-01-31"

  2253. msgstr ""

  2254. 

  2255. #: ../../../CHANGELOG.md:1299

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

  2257. msgstr ""

  2258. 

  2259. #: ../../../CHANGELOG.md:1301

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

  2261. msgstr ""

  2262. 

  2263. #: ../../../CHANGELOG.md:1303

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

  2265. msgstr ""

  2266. 

  2267. #: ../../../CHANGELOG.md:1305

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

  2269. msgstr ""

  2270. 

  2271. #: ../../../CHANGELOG.md:1308

  2272. msgid "2024-01-20"

  2273. msgstr ""

  2274. 

  2275. #: ../../../CHANGELOG.md:1310

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

  2277. msgstr ""

  2278. 

  2279. #: ../../../CHANGELOG.md:1312

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

  2281. msgstr ""

  2282. 

  2283. #: ../../../CHANGELOG.md:1314

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

  2285. msgstr ""

  2286. 

  2287. #: ../../../CHANGELOG.md:1316

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

  2289. msgstr ""

  2290. 

  2291. #: ../../../CHANGELOG.md:1318

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

  2293. msgstr ""

  2294. 

  2295. #: ../../../CHANGELOG.md:1321

  2296. msgid "2024-01-17"

  2297. msgstr ""

  2298. 

  2299. #: ../../../CHANGELOG.md:1323

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

  2301. msgstr ""

  2302. 

  2303. #: ../../../CHANGELOG.md:1325

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

  2305. msgstr ""

  2306. 

  2307. #: ../../../CHANGELOG.md:1327

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

  2309. msgstr ""

  2310. 

  2311. #: ../../../CHANGELOG.md:1328

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

  2313. msgstr ""

  2314. 

  2315. #: ../../../CHANGELOG.md:1330

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

  2317. msgstr ""

  2318. 

  2319. #: ../../../CHANGELOG.md:1332

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

  2321. msgstr ""

  2322. 

  2323. #: ../../../CHANGELOG.md:1334

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

  2325. msgstr ""

  2326. 

  2327. #: ../../../CHANGELOG.md:1336

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

  2329. msgstr ""

  2330. 

  2331. #: ../../../CHANGELOG.md:1338

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

  2333. msgstr ""

  2334. 

  2335. #: ../../../CHANGELOG.md:1340

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

  2337. msgstr ""

  2338. 

  2339. #: ../../../CHANGELOG.md:1342

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

  2341. msgstr ""

  2342. 

  2343. #: ../../../CHANGELOG.md:1344

  2344. msgid "If you'd like to continue using the old Apache-2.0-licensed Synapse (for a while longer anyway), the playbook makes it possible by introducing a new Ansible variable. You can do it like this:"

  2345. msgstr ""

  2346. 

  2347. #: ../../../CHANGELOG.md:1356

  2348. msgid "Notes:"

  2349. msgstr ""

  2350. 

  2351. #: ../../../CHANGELOG.md:1358

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

  2353. msgstr ""

  2354. 

  2355. #: ../../../CHANGELOG.md:1360

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

  2357. msgstr ""

  2358. 

  2359. #: ../../../CHANGELOG.md:1362

  2360. msgid "2024-01-16"

  2361. msgstr ""

  2362. 

  2363. #: ../../../CHANGELOG.md:1364

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

  2365. msgstr ""

  2366. 

  2367. #: ../../../CHANGELOG.md:1366

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

  2369. msgstr ""

  2370. 

  2371. #: ../../../CHANGELOG.md:1368

  2372. msgid "2024-01-15"

  2373. msgstr ""

  2374. 

  2375. #: ../../../CHANGELOG.md:1370

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

  2377. msgstr ""

  2378. 

  2379. #: ../../../CHANGELOG.md:1372

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

  2381. msgstr ""

  2382. 

  2383. #: ../../../CHANGELOG.md:1374

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

  2385. msgstr ""

  2386. 

  2387. #: ../../../CHANGELOG.md:1376

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

  2389. msgstr ""

  2390. 

  2391. #: ../../../CHANGELOG.md:1378

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

  2393. msgstr ""

  2394. 

  2395. #: ../../../CHANGELOG.md:1380

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

  2397. msgstr ""

  2398. 

  2399. #: ../../../CHANGELOG.md:1382

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

  2401. msgstr ""

  2402. 

  2403. #: ../../../CHANGELOG.md:1383

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

  2405. msgstr ""

  2406. 

  2407. #: ../../../CHANGELOG.md:1384

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

  2409. msgstr ""

  2410. 

  2411. #: ../../../CHANGELOG.md:1385

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

  2413. msgstr ""

  2414. 

  2415. #: ../../../CHANGELOG.md:1386

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

  2417. msgstr ""

  2418. 

  2419. #: ../../../CHANGELOG.md:1387

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

  2421. msgstr ""

  2422. 

  2423. #: ../../../CHANGELOG.md:1388

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

  2425. msgstr ""

  2426. 

  2427. #: ../../../CHANGELOG.md:1390

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

  2429. msgstr ""

  2430. 

  2431. #: ../../../CHANGELOG.md:1392

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

  2433. msgstr ""

  2434. 

  2435. #: ../../../CHANGELOG.md:1394

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

  2437. msgstr ""

  2438. 

  2439. #: ../../../CHANGELOG.md:1396

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

  2441. msgstr ""

  2442. 

  2443. #: ../../../CHANGELOG.md:1398

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

  2445. msgstr ""

  2446. 

  2447. #: ../../../CHANGELOG.md:1400

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

  2449. msgstr ""

  2450. 

  2451. #: ../../../CHANGELOG.md:1402

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

  2453. msgstr ""

  2454. 

  2455. #: ../../../CHANGELOG.md:1404

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

  2457. msgstr ""

  2458. 

  2459. #: ../../../CHANGELOG.md:1406

  2460. msgid "Traefik now has an extra job"

  2461. msgstr ""

  2462. 

  2463. #: ../../../CHANGELOG.md:1408

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

  2465. msgstr ""

  2466. 

  2467. #: ../../../CHANGELOG.md:1410

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

  2469. msgstr ""

  2470. 

  2471. #: ../../../CHANGELOG.md:1412

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

  2473. msgstr ""

  2474. 

  2475. #: ../../../CHANGELOG.md:1414

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

  2477. msgstr ""

  2478. 

  2479. #: ../../../CHANGELOG.md:1416

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

  2481. msgstr ""

  2482. 

  2483. #: ../../../CHANGELOG.md:1418

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

  2485. msgstr ""

  2486. 

  2487. #: ../../../CHANGELOG.md:1420

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

  2489. msgstr ""

  2490. 

  2491. #: ../../../CHANGELOG.md:1421

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

  2493. msgstr ""

  2494. 

  2495. #: ../../../CHANGELOG.md:1423

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

  2497. msgstr ""

  2498. 

  2499. #: ../../../CHANGELOG.md:1425

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

  2501. msgstr ""

  2502. 

  2503. #: ../../../CHANGELOG.md:1427

  2504. msgid "**People running their own Traefik reverse-proxy need to do [minor adjustments](#people-managing-their-own-traefik-instance-need-to-do-minor-changes)**, as described in the section below."

  2505. msgstr ""

  2506. 

  2507. #: ../../../CHANGELOG.md:1429

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

  2509. msgstr ""

  2510. 

  2511. #: ../../../CHANGELOG.md:1431

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

  2513. msgstr ""

  2514. 

  2515. #: ../../../CHANGELOG.md:1433

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

  2517. msgstr ""

  2518. 

  2519. #: ../../../CHANGELOG.md:1435

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

  2521. msgstr ""

  2522. 

  2523. #: ../../../CHANGELOG.md:1437

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

  2525. msgstr ""

  2526. 

  2527. #: ../../../CHANGELOG.md:1439

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

  2529. msgstr ""

  2530. 

  2531. #: ../../../CHANGELOG.md:1441

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

  2533. msgstr ""

  2534. 

  2535. #: ../../../CHANGELOG.md:1443

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

  2537. msgstr ""

  2538. 

  2539. #: ../../../CHANGELOG.md:1445

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

  2541. msgstr ""

  2542. 

  2543. #: ../../../CHANGELOG.md:1447

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

  2545. msgstr ""

  2546. 

  2547. #: ../../../CHANGELOG.md:1449

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

  2549. msgstr ""

  2550. 

  2551. #: ../../../CHANGELOG.md:1451

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

  2553. msgstr ""

  2554. 

  2555. #: ../../../CHANGELOG.md:1452

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

  2557. msgstr ""

  2558. 

  2559. #: ../../../CHANGELOG.md:1453

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

  2561. msgstr ""

  2562. 

  2563. #: ../../../CHANGELOG.md:1455

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

  2565. msgstr ""

  2566. 

  2567. #: ../../../CHANGELOG.md:1457

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

  2569. msgstr ""

  2570. 

  2571. #: ../../../CHANGELOG.md:1459

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

  2573. msgstr ""

  2574. 

  2575. #: ../../../CHANGELOG.md:1461

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

  2577. msgstr ""

  2578. 

  2579. #: ../../../CHANGELOG.md:1462

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

  2581. msgstr ""

  2582. 

  2583. #: ../../../CHANGELOG.md:1464

  2584. msgid "Container networking changes"

  2585. msgstr ""

  2586. 

  2587. #: ../../../CHANGELOG.md:1466

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

  2589. msgstr ""

  2590. 

  2591. #: ../../../CHANGELOG.md:1468

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

  2593. msgstr ""

  2594. 

  2595. #: ../../../CHANGELOG.md:1470

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

  2597. msgstr ""

  2598. 

  2599. #: ../../../CHANGELOG.md:1472

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

  2601. msgstr ""

  2602. 

  2603. #: ../../../CHANGELOG.md:1474

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

  2605. msgstr ""

  2606. 

  2607. #: ../../../CHANGELOG.md:1476

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

  2609. msgstr ""

  2610. 

  2611. #: ../../../CHANGELOG.md:1478

  2612. msgid "Metrics exposure changes"

  2613. msgstr ""

  2614. 

  2615. #: ../../../CHANGELOG.md:1480

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

  2617. msgstr ""

  2618. 

  2619. #: ../../../CHANGELOG.md:1482

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

  2621. msgstr ""

  2622. 

  2623. #: ../../../CHANGELOG.md:1484

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

  2625. msgstr ""

  2626. 

  2627. #: ../../../CHANGELOG.md:1486

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

  2629. msgstr ""

  2630. 

  2631. #: ../../../CHANGELOG.md:1488

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

  2633. msgstr ""

  2634. 

  2635. #: ../../../CHANGELOG.md:1490

  2636. msgid "Matrix static files"

  2637. msgstr ""

  2638. 

  2639. #: ../../../CHANGELOG.md:1492

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

  2641. msgstr ""

  2642. 

  2643. #: ../../../CHANGELOG.md:1494

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

  2645. msgstr ""

  2646. 

  2647. #: ../../../CHANGELOG.md:1496

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

  2649. msgstr ""

  2650. 

  2651. #: ../../../CHANGELOG.md:1498

  2652. msgid "A note on performance"

  2653. msgstr ""

  2654. 

  2655. #: ../../../CHANGELOG.md:1500

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

  2657. msgstr ""

  2658. 

  2659. #: ../../../CHANGELOG.md:1502

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

  2661. msgstr ""

  2662. 

  2663. #: ../../../CHANGELOG.md:1504

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

  2665. msgstr ""

  2666. 

  2667. #: ../../../CHANGELOG.md:1506

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

  2669. msgstr ""

  2670. 

  2671. #: ../../../CHANGELOG.md:1508

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

  2673. msgstr ""

  2674. 

  2675. #: ../../../CHANGELOG.md:1510

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

  2677. msgstr ""

  2678. 

  2679. #: ../../../CHANGELOG.md:1512

  2680. msgid "Migration procedure"

  2681. msgstr ""

  2682. 

  2683. #: ../../../CHANGELOG.md:1514

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

  2685. msgstr ""

  2686. 

  2687. #: ../../../CHANGELOG.md:1516

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

  2689. msgstr ""

  2690. 

  2691. #: ../../../CHANGELOG.md:1518

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

  2693. msgstr ""

  2694. 

  2695. #: ../../../CHANGELOG.md:1520

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

  2697. msgstr ""

  2698. 

  2699. #: ../../../CHANGELOG.md:1522

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

  2701. msgstr ""

  2702. 

  2703. #: ../../../CHANGELOG.md:1524

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

  2705. msgstr ""

  2706. 

  2707. #: ../../../CHANGELOG.md:1526

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

  2709. msgstr ""

  2710. 

  2711. #: ../../../CHANGELOG.md:1528

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

  2713. msgstr ""

  2714. 

  2715. #: ../../../CHANGELOG.md:1530

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

  2717. msgstr ""

  2718. 

  2719. #: ../../../CHANGELOG.md:1532

  2720. msgid "Conclusion"

  2721. msgstr ""

  2722. 

  2723. #: ../../../CHANGELOG.md:1534

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

  2725. msgstr ""

  2726. 

  2727. #: ../../../CHANGELOG.md:1536

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

  2729. msgstr ""

  2730. 

  2731. #: ../../../CHANGELOG.md:1539

  2732. msgid "2024-01-14"

  2733. msgstr ""

  2734. 

  2735. #: ../../../CHANGELOG.md:1541

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

  2737. msgstr ""

  2738. 

  2739. #: ../../../CHANGELOG.md:1543

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

  2741. msgstr ""

  2742. 

  2743. #: ../../../CHANGELOG.md:1545

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

  2745. msgstr ""

  2746. 

  2747. #: ../../../CHANGELOG.md:1547

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

  2749. msgstr ""

  2750. 

  2751. #: ../../../CHANGELOG.md:1549

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

  2753. msgstr ""

  2754. 

  2755. #: ../../../CHANGELOG.md:1551

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

  2757. msgstr ""

  2758. 

  2759. #: ../../../CHANGELOG.md:1584

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

  2761. msgstr ""

  2762. 

  2763. #: ../../../CHANGELOG.md:1587

  2764. msgid "2024-01-13"

  2765. msgstr ""

  2766. 

  2767. #: ../../../CHANGELOG.md:1589

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

  2769. msgstr ""

  2770. 

  2771. #: ../../../CHANGELOG.md:1591

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

  2773. msgstr ""

  2774. 

  2775. #: ../../../CHANGELOG.md:1593

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

  2777. msgstr ""

  2778. 

  2779. #: ../../../CHANGELOG.md:1595

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

  2781. msgstr ""

  2782. 

  2783. #: ../../../CHANGELOG.md:1597

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

  2785. msgstr ""

  2786. 

  2787. #: ../../../CHANGELOG.md:1599

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

  2789. msgstr ""

  2790. 

  2791. #: ../../../CHANGELOG.md:1601

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

  2793. msgstr ""

  2794. 

  2795. #: ../../../CHANGELOG.md:1603

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

  2797. msgstr ""

  2798. 

  2799. #: ../../../CHANGELOG.md:1605

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

  2801. msgstr ""

  2802. 

  2803. #: ../../../CHANGELOG.md:1607

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

  2805. msgstr ""

  2806. 

  2807. #: ../../../CHANGELOG.md:1610

  2808. msgid "2024-01-05"

  2809. msgstr ""

  2810. 

  2811. #: ../../../CHANGELOG.md:1612

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

  2813. msgstr ""

  2814. 

  2815. #: ../../../CHANGELOG.md:1614

  2816. #: ../../../CHANGELOG.md:2252

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

  2818. msgstr ""

  2819. 

  2820. #: ../../../CHANGELOG.md:1616

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

  2822. msgstr ""

  2823. 

  2824. #: ../../../CHANGELOG.md:1618

  2825. msgid "To migrate:"

  2826. msgstr ""

  2827. 

  2828. #: ../../../CHANGELOG.md:1620

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

  2830. msgstr ""

  2831. 

  2832. #: ../../../CHANGELOG.md:1621

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

  2834. msgstr ""

  2835. 

  2836. #: ../../../CHANGELOG.md:1622

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

  2838. msgstr ""

  2839. 

  2840. #: ../../../CHANGELOG.md:1623

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

  2842. msgstr ""

  2843. 

  2844. #: ../../../CHANGELOG.md:1625

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

  2846. msgstr ""

  2847. 

  2848. #: ../../../CHANGELOG.md:1628

  2849. msgid "2024-01-02"

  2850. msgstr ""

  2851. 

  2852. #: ../../../CHANGELOG.md:1630

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

  2854. msgstr ""

  2855. 

  2856. #: ../../../CHANGELOG.md:1632

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

  2858. msgstr ""

  2859. 

  2860. #: ../../../CHANGELOG.md:1634

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

  2862. msgstr ""

  2863. 

  2864. #: ../../../CHANGELOG.md:1636

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

  2866. msgstr ""

  2867. 

  2868. #: ../../../CHANGELOG.md:1639

  2869. msgid "2023-10-23"

  2870. msgstr ""

  2871. 

  2872. #: ../../../CHANGELOG.md:1641

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

  2874. msgstr ""

  2875. 

  2876. #: ../../../CHANGELOG.md:1643

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

  2878. msgstr ""

  2879. 

  2880. #: ../../../CHANGELOG.md:1645

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

  2882. msgstr ""

  2883. 

  2884. #: ../../../CHANGELOG.md:1647

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

  2886. msgstr ""

  2887. 

  2888. #: ../../../CHANGELOG.md:1649

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

  2890. msgstr ""

  2891. 

  2892. #: ../../../CHANGELOG.md:1651

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

  2894. msgstr ""

  2895. 

  2896. #: ../../../CHANGELOG.md:1653

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

  2898. msgstr ""

  2899. 

  2900. #: ../../../CHANGELOG.md:1655

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

  2902. msgstr ""

  2903. 

  2904. #: ../../../CHANGELOG.md:1657

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

  2906. msgstr ""

  2907. 

  2908. #: ../../../CHANGELOG.md:1659

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

  2910. msgstr ""

  2911. 

  2912. #: ../../../CHANGELOG.md:1661

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

  2914. msgstr ""

  2915. 

  2916. #: ../../../CHANGELOG.md:1663

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

  2918. msgstr ""

  2919. 

  2920. #: ../../../CHANGELOG.md:1665

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

  2922. msgstr ""

  2923. 

  2924. #: ../../../CHANGELOG.md:1667

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

  2926. msgstr ""

  2927. 

  2928. #: ../../../CHANGELOG.md:1670

  2929. msgid "2023-10-18"

  2930. msgstr ""

  2931. 

  2932. #: ../../../CHANGELOG.md:1672

  2933. msgid "Postgres parameters are automatically tuned now"

  2934. msgstr ""

  2935. 

  2936. #: ../../../CHANGELOG.md:1674

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

  2938. msgstr ""

  2939. 

  2940. #: ../../../CHANGELOG.md:1676

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

  2942. msgstr ""

  2943. 

  2944. #: ../../../CHANGELOG.md:1678

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

  2946. msgstr ""

  2947. 

  2948. #: ../../../CHANGELOG.md:1680

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

  2950. msgstr ""

  2951. 

  2952. #: ../../../CHANGELOG.md:1683

  2953. msgid "2023-08-31"

  2954. msgstr ""

  2955. 

  2956. #: ../../../CHANGELOG.md:1685

  2957. msgid "SchildiChat Web support"

  2958. msgstr ""

  2959. 

  2960. #: ../../../CHANGELOG.md:1687

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

  2962. msgstr ""

  2963. 

  2964. #: ../../../CHANGELOG.md:1689

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

  2966. msgstr ""

  2967. 

  2968. #: ../../../CHANGELOG.md:1692

  2969. msgid "2023-08-23"

  2970. msgstr ""

  2971. 

  2972. #: ../../../CHANGELOG.md:1694

  2973. msgid "mautrix-wsproxy support"

  2974. msgstr ""

  2975. 

  2976. #: ../../../CHANGELOG.md:1696

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

  2978. msgstr ""

  2979. 

  2980. #: ../../../CHANGELOG.md:1698

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

  2982. msgstr ""

  2983. 

  2984. #: ../../../CHANGELOG.md:1701

  2985. msgid "2023-07-24"

  2986. msgstr ""

  2987. 

  2988. #: ../../../CHANGELOG.md:1703

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

  2990. msgstr ""

  2991. 

  2992. #: ../../../CHANGELOG.md:1705

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

  2994. msgstr ""

  2995. 

  2996. #: ../../../CHANGELOG.md:1707

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

  2998. msgstr ""

  2999. 

  3000. #: ../../../CHANGELOG.md:1709

  3001. msgid "`matrix_bot_matrix_registration_bot_bot_access_token`"

  3002. msgstr ""

  3003. 

  3004. #: ../../../CHANGELOG.md:1710

  3005. msgid "`matrix_bot_matrix_registration_bot_api_token`"

  3006. msgstr ""

  3007. 

  3008. #: ../../../CHANGELOG.md:1713

  3009. msgid "2023-07-21"

  3010. msgstr ""

  3011. 

  3012. #: ../../../CHANGELOG.md:1715

  3013. msgid "mautrix-gmessages support"

  3014. msgstr ""

  3015. 

  3016. #: ../../../CHANGELOG.md:1717

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

  3018. msgstr ""

  3019. 

  3020. #: ../../../CHANGELOG.md:1720

  3021. msgid "2023-07-17"

  3022. msgstr ""

  3023. 

  3024. #: ../../../CHANGELOG.md:1722

  3025. msgid "matrix-media-repo support"

  3026. msgstr ""

  3027. 

  3028. #: ../../../CHANGELOG.md:1724

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

  3030. msgstr ""

  3031. 

  3032. #: ../../../CHANGELOG.md:1726

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

  3034. msgstr ""

  3035. 

  3036. #: ../../../CHANGELOG.md:1729

  3037. msgid "2023-05-25"

  3038. msgstr ""

  3039. 

  3040. #: ../../../CHANGELOG.md:1731

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

  3042. msgstr ""

  3043. 

  3044. #: ../../../CHANGELOG.md:1733

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

  3046. msgstr ""

  3047. 

  3048. #: ../../../CHANGELOG.md:1735

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

  3050. msgstr ""

  3051. 

  3052. #: ../../../CHANGELOG.md:1737

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

  3054. msgstr ""

  3055. 

  3056. #: ../../../CHANGELOG.md:1739

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

  3058. msgstr ""

  3059. 

  3060. #: ../../../CHANGELOG.md:1742

  3061. msgid "2023-04-03"

  3062. msgstr ""

  3063. 

  3064. #: ../../../CHANGELOG.md:1744

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

  3066. msgstr ""

  3067. 

  3068. #: ../../../CHANGELOG.md:1746

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

  3070. msgstr ""

  3071. 

  3072. #: ../../../CHANGELOG.md:1748

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

  3074. msgstr ""

  3075. 

  3076. #: ../../../CHANGELOG.md:1750

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

  3078. msgstr ""

  3079. 

  3080. #: ../../../CHANGELOG.md:1752

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

  3082. msgstr ""

  3083. 

  3084. #: ../../../CHANGELOG.md:1753

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

  3086. msgstr ""

  3087. 

  3088. #: ../../../CHANGELOG.md:1755

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

  3090. msgstr ""

  3091. 

  3092. #: ../../../CHANGELOG.md:1757

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

  3094. msgstr ""

  3095. 

  3096. #: ../../../CHANGELOG.md:1759

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

  3098. msgstr ""

  3099. 

  3100. #: ../../../CHANGELOG.md:1760

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

  3102. msgstr ""

  3103. 

  3104. #: ../../../CHANGELOG.md:1761

  3105. #: ../../../CHANGELOG.md:1788

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

  3107. msgstr ""

  3108. 

  3109. #: ../../../CHANGELOG.md:1763

  3110. msgid "2023-03-22"

  3111. msgstr ""

  3112. 

  3113. #: ../../../CHANGELOG.md:1765

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

  3115. msgstr ""

  3116. 

  3117. #: ../../../CHANGELOG.md:1767

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

  3119. msgstr ""

  3120. 

  3121. #: ../../../CHANGELOG.md:1769

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

  3123. msgstr ""

  3124. 

  3125. #: ../../../CHANGELOG.md:1772

  3126. msgid "2023-03-21"

  3127. msgstr ""

  3128. 

  3129. #: ../../../CHANGELOG.md:1774

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

  3131. msgstr ""

  3132. 

  3133. #: ../../../CHANGELOG.md:1776

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

  3135. msgstr ""

  3136. 

  3137. #: ../../../CHANGELOG.md:1778

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

  3139. msgstr ""

  3140. 

  3141. #: ../../../CHANGELOG.md:1780

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

  3143. msgstr ""

  3144. 

  3145. #: ../../../CHANGELOG.md:1782

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

  3147. msgstr ""

  3148. 

  3149. #: ../../../CHANGELOG.md:1784

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

  3151. msgstr ""

  3152. 

  3153. #: ../../../CHANGELOG.md:1786

  3154. msgid "`matrix_prometheus_docker_image_` -> `matrix_prometheus_container_image_`"

  3155. msgstr ""

  3156. 

  3157. #: ../../../CHANGELOG.md:1787

  3158. msgid "`matrix_prometheus_` -> `prometheus_`"

  3159. msgstr ""

  3160. 

  3161. #: ../../../CHANGELOG.md:1791

  3162. msgid "2023-03-12"

  3163. msgstr ""

  3164. 

  3165. #: ../../../CHANGELOG.md:1793

  3166. msgid "synapse-auto-compressor support"

  3167. msgstr ""

  3168. 

  3169. #: ../../../CHANGELOG.md:1795

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

  3171. msgstr ""

  3172. 

  3173. #: ../../../CHANGELOG.md:1797

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

  3175. msgstr ""

  3176. 

  3177. #: ../../../CHANGELOG.md:1799

  3178. msgid "it runs on a more up-to-date version of `rust-synapse-compress-state`"

  3179. msgstr ""

  3180. 

  3181. #: ../../../CHANGELOG.md:1800

  3182. msgid "it's a set-it-and-forget-it tool that you can enable and never have to deal with manual compression anymore"

  3183. msgstr ""

  3184. 

  3185. #: ../../../CHANGELOG.md:1802

  3186. msgid "This tool needs to be enabled manually, for now. In the future, we're considering enabling it by default for all Synapse installations."

  3187. msgstr ""

  3188. 

  3189. #: ../../../CHANGELOG.md:1804

  3190. msgid "See our [Setting up synapse-auto-compressor](docs/configuring-playbook-synapse-auto-compressor.md) documentation to get started."

  3191. msgstr ""

  3192. 

  3193. #: ../../../CHANGELOG.md:1807

  3194. msgid "2023-03-07"

  3195. msgstr ""

  3196. 

  3197. #: ../../../CHANGELOG.md:1809

  3198. msgid "Sliding Sync proxy (Element X) support"

  3199. msgstr ""

  3200. 

  3201. #: ../../../CHANGELOG.md:1811

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

  3203. msgstr ""

  3204. 

  3205. #: ../../../CHANGELOG.md:1813

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

  3207. msgstr ""

  3208. 

  3209. #: ../../../CHANGELOG.md:1815

  3210. msgid "To get started, see our [Setting up the Sliding Sync proxy](docs/configuring-playbook-sliding-sync-proxy.md) documentation page."

  3211. msgstr ""

  3212. 

  3213. #: ../../../CHANGELOG.md:1818

  3214. msgid "2023-03-02"

  3215. msgstr ""

  3216. 

  3217. #: ../../../CHANGELOG.md:1820

  3218. msgid "The matrix-etherpad role lives independently now"

  3219. msgstr ""

  3220. 

  3221. #: ../../../CHANGELOG.md:1822

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

  3223. msgstr ""

  3224. 

  3225. #: ../../../CHANGELOG.md:1824

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

  3227. msgstr ""

  3228. 

  3229. #: ../../../CHANGELOG.md:1826

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

  3231. msgstr ""

  3232. 

  3233. #: ../../../CHANGELOG.md:1828

  3234. msgid "Rename `matrix_etherpad_public_endpoint` to `etherpad_path_prefix`"

  3235. msgstr ""

  3236. 

  3237. #: ../../../CHANGELOG.md:1830

  3238. msgid "Replace `matrix_etherpad_mode: dimension` with:"

  3239. msgstr ""

  3240. 

  3241. #: ../../../CHANGELOG.md:1831

  3242. msgid "for `matrix-nginx-proxy` users:"

  3243. msgstr ""

  3244. 

  3245. #: ../../../CHANGELOG.md:1832

  3246. msgid "`etherpad_nginx_proxy_dimension_integration_enabled: true`"

  3247. msgstr ""

  3248. 

  3249. #: ../../../CHANGELOG.md:1833

  3250. msgid "`etherpad_hostname: \"{{ matrix_server_fqn_dimension }}\"`"

  3251. msgstr ""

  3252. 

  3253. #: ../../../CHANGELOG.md:1834

  3254. msgid "for Traefik users:"

  3255. msgstr ""

  3256. 

  3257. #: ../../../CHANGELOG.md:1835

  3258. msgid "define your own `etherpad_hostname` and `etherpad_path_prefix` as you see fit"

  3259. msgstr ""

  3260. 

  3261. #: ../../../CHANGELOG.md:1837

  3262. msgid "Rename all other variables:"

  3263. msgstr ""

  3264. 

  3265. #: ../../../CHANGELOG.md:1838

  3266. msgid "`matrix_etherpad_docker_image_` -> `matrix_etherpad_container_image_`"

  3267. msgstr ""

  3268. 

  3269. #: ../../../CHANGELOG.md:1839

  3270. msgid "`matrix_etherpad_` -> `etherpad_`"

  3271. msgstr ""

  3272. 

  3273. #: ../../../CHANGELOG.md:1841

  3274. msgid "Along with this relocation, the new role also:"

  3275. msgstr ""

  3276. 

  3277. #: ../../../CHANGELOG.md:1843

  3278. msgid "supports [self-building](docs/self-building.md), so it should work on `arm32` and `arm64` architectures"

  3279. msgstr ""

  3280. 

  3281. #: ../../../CHANGELOG.md:1844

  3282. msgid "has native Traefik reverse-proxy support (Etherpad requests no longer go through `matrix-nginx-proxy` when using Traefik)"

  3283. msgstr ""

  3284. 

  3285. #: ../../../CHANGELOG.md:1847

  3286. msgid "2023-02-26"

  3287. msgstr ""

  3288. 

  3289. #: ../../../CHANGELOG.md:1849

  3290. msgid "Traefik is the default reverse-proxy now"

  3291. msgstr ""

  3292. 

  3293. #: ../../../CHANGELOG.md:1851

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

  3295. msgstr ""

  3296. 

  3297. #: ../../../CHANGELOG.md:1853

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

  3299. msgstr ""

  3300. 

  3301. #: ../../../CHANGELOG.md:1855

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

  3303. msgstr ""

  3304. 

  3305. #: ../../../CHANGELOG.md:1857

  3306. msgid "Traefik managed by the playbook"

  3307. msgstr ""

  3308. 

  3309. #: ../../../CHANGELOG.md:1858

  3310. msgid "Traefik managed by the user in another way"

  3311. msgstr ""

  3312. 

  3313. #: ../../../CHANGELOG.md:1859

  3314. msgid "another reverse-proxy on the same host (`127.0.0.1` port exposure)"

  3315. msgstr ""

  3316. 

  3317. #: ../../../CHANGELOG.md:1860

  3318. msgid "another reverse-proxy on another host (`0.0.0.0` port exposure)"

  3319. msgstr ""

  3320. 

  3321. #: ../../../CHANGELOG.md:1861

  3322. msgid "`matrix-nginx-proxy` — an `nginx` container managed by the playbook"

  3323. msgstr ""

  3324. 

  3325. #: ../../../CHANGELOG.md:1862

  3326. msgid "`nginx` webserver operated by the user, running without a container on the same server"

  3327. msgstr ""

  3328. 

  3329. #: ../../../CHANGELOG.md:1864

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

  3331. msgstr ""

  3332. 

  3333. #: ../../../CHANGELOG.md:1866

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

  3335. msgstr ""

  3336. 

  3337. #: ../../../CHANGELOG.md:1868

  3338. msgid "It's time for the **next step in our migration process** to Traefik and elimination of `matrix-nginx-proxy`:"

  3339. msgstr ""

  3340. 

  3341. #: ../../../CHANGELOG.md:1870

  3342. msgid "Traefik is now the default reverse-proxy for new installations"

  3343. msgstr ""

  3344. 

  3345. #: ../../../CHANGELOG.md:1871

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

  3347. msgstr ""

  3348. 

  3349. #: ../../../CHANGELOG.md:1873

  3350. msgid "How do I switch my existing setup to Traefik?"

  3351. msgstr ""

  3352. 

  3353. #: ../../../CHANGELOG.md:1875

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

  3355. msgstr ""

  3356. 

  3357. #: ../../../CHANGELOG.md:1877

  3358. msgid "If you experience trouble:"

  3359. msgstr ""

  3360. 

  3361. #: ../../../CHANGELOG.md:1879

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

  3363. msgstr ""

  3364. 

  3365. #: ../../../CHANGELOG.md:1880

  3366. msgid "Ask for help in our [support channels](README.md#support)"

  3367. msgstr ""

  3368. 

  3369. #: ../../../CHANGELOG.md:1881

  3370. msgid "Try switching to Traefik again later"

  3371. msgstr ""

  3372. 

  3373. #: ../../../CHANGELOG.md:1883

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

  3375. msgstr ""

  3376. 

  3377. #: ../../../CHANGELOG.md:1885

  3378. msgid "I already use my own Traefik server. How do I plug that in?"

  3379. msgstr ""

  3380. 

  3381. #: ../../../CHANGELOG.md:1887

  3382. msgid "See the [Traefik managed by the playbook](docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) section."

  3383. msgstr ""

  3384. 

  3385. #: ../../../CHANGELOG.md:1889

  3386. msgid "Why is matrix-nginx-proxy used even after switching to Traefik?"

  3387. msgstr ""

  3388. 

  3389. #: ../../../CHANGELOG.md:1891

  3390. msgid "This playbook manages many different services. All these services were initially integrated with `matrix-nginx-proxy`."

  3391. msgstr ""

  3392. 

  3393. #: ../../../CHANGELOG.md:1893

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

  3395. msgstr ""

  3396. 

  3397. #: ../../../CHANGELOG.md:1895

  3398. msgid "How do I remain on matrix-nginx-proxy?"

  3399. msgstr ""

  3400. 

  3401. #: ../../../CHANGELOG.md:1897

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

  3403. msgstr ""

  3404. 

  3405. #: ../../../CHANGELOG.md:1899

  3406. msgid "To proceed regardless of this warning, add `matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your configuration."

  3407. msgstr ""

  3408. 

  3409. #: ../../../CHANGELOG.md:1901

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

  3411. msgstr ""

  3412. 

  3413. #: ../../../CHANGELOG.md:1903

  3414. msgid "How do I keep using my own other reverse-proxy?"

  3415. msgstr ""

  3416. 

  3417. #: ../../../CHANGELOG.md:1905

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

  3419. msgstr ""

  3420. 

  3421. #: ../../../CHANGELOG.md:1908

  3422. msgid "2023-02-25"

  3423. msgstr ""

  3424. 

  3425. #: ../../../CHANGELOG.md:1910

  3426. msgid "rageshake support"

  3427. msgstr ""

  3428. 

  3429. #: ../../../CHANGELOG.md:1912

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

  3431. msgstr ""

  3432. 

  3433. #: ../../../CHANGELOG.md:1914

  3434. msgid "Additional details are available in [Setting up rageshake](docs/configuring-playbook-rageshake.md)."

  3435. msgstr ""

  3436. 

  3437. #: ../../../CHANGELOG.md:1917

  3438. msgid "2023-02-17"

  3439. msgstr ""

  3440. 

  3441. #: ../../../CHANGELOG.md:1919

  3442. msgid "Synapse templates customization support"

  3443. msgstr ""

  3444. 

  3445. #: ../../../CHANGELOG.md:1921

  3446. msgid "The playbook can now help you customize Synapse's templates."

  3447. msgstr ""

  3448. 

  3449. #: ../../../CHANGELOG.md:1923

  3450. msgid "Additional details are available in the [Customizing templates](docs/configuring-playbook-synapse.md#customizing-templates) section of our Synapse documentation."

  3451. msgstr ""

  3452. 

  3453. #: ../../../CHANGELOG.md:1925

  3454. msgid "The matrix-redis role lives independently now"

  3455. msgstr ""

  3456. 

  3457. #: ../../../CHANGELOG.md:1927

  3458. msgid "**TLDR**: the `matrix-redis` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3459. msgstr ""

  3460. 

  3461. #: ../../../CHANGELOG.md:1929

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

  3463. msgstr ""

  3464. 

  3465. #: ../../../CHANGELOG.md:1931

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

  3467. msgstr ""

  3468. 

  3469. #: ../../../CHANGELOG.md:1933

  3470. msgid "The matrix-ntfy role lives independently now"

  3471. msgstr ""

  3472. 

  3473. #: ../../../CHANGELOG.md:1935

  3474. msgid "**TLDR**: the `matrix-ntfy` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3475. msgstr ""

  3476. 

  3477. #: ../../../CHANGELOG.md:1937

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

  3479. msgstr ""

  3480. 

  3481. #: ../../../CHANGELOG.md:1939

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

  3483. msgstr ""

  3484. 

  3485. #: ../../../CHANGELOG.md:1942

  3486. msgid "2023-02-15"

  3487. msgstr ""

  3488. 

  3489. #: ../../../CHANGELOG.md:1944

  3490. msgid "The matrix-grafana role lives independently now"

  3491. msgstr ""

  3492. 

  3493. #: ../../../CHANGELOG.md:1946

  3494. msgid "**TLDR**: the `matrix-grafana` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3495. msgstr ""

  3496. 

  3497. #: ../../../CHANGELOG.md:1948

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

  3499. msgstr ""

  3500. 

  3501. #: ../../../CHANGELOG.md:1950

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

  3503. msgstr ""

  3504. 

  3505. #: ../../../CHANGELOG.md:1953

  3506. msgid "2023-02-13"

  3507. msgstr ""

  3508. 

  3509. #: ../../../CHANGELOG.md:1955

  3510. msgid "The matrix-backup-borg role lives independently now"

  3511. msgstr ""

  3512. 

  3513. #: ../../../CHANGELOG.md:1957

  3514. msgid "**TLDR**: the `matrix-backup-borg` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3515. msgstr ""

  3516. 

  3517. #: ../../../CHANGELOG.md:1959

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

  3519. msgstr ""

  3520. 

  3521. #: ../../../CHANGELOG.md:1961

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

  3523. msgstr ""

  3524. 

  3525. #: ../../../CHANGELOG.md:1964

  3526. msgid "2023-02-12"

  3527. msgstr ""

  3528. 

  3529. #: ../../../CHANGELOG.md:1966

  3530. msgid "(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support"

  3531. msgstr ""

  3532. 

  3533. #: ../../../CHANGELOG.md:1968

  3534. msgid "**TLDR**:"

  3535. msgstr ""

  3536. 

  3537. #: ../../../CHANGELOG.md:1970

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

  3539. msgstr ""

  3540. 

  3541. #: ../../../CHANGELOG.md:1971

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

  3543. msgstr ""

  3544. 

  3545. #: ../../../CHANGELOG.md:1972

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

  3547. msgstr ""

  3548. 

  3549. #: ../../../CHANGELOG.md:1973

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

  3551. msgstr ""

  3552. 

  3553. #: ../../../CHANGELOG.md:1974

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

  3555. msgstr ""

  3556. 

  3557. #: ../../../CHANGELOG.md:1976

  3558. msgid "Motivation for redoing our reverse-proxy setup"

  3559. msgstr ""

  3560. 

  3561. #: ../../../CHANGELOG.md:1978

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

  3563. msgstr ""

  3564. 

  3565. #: ../../../CHANGELOG.md:1980

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

  3567. msgstr ""

  3568. 

  3569. #: ../../../CHANGELOG.md:1982

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

  3571. msgstr ""

  3572. 

  3573. #: ../../../CHANGELOG.md:1984

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

  3575. msgstr ""

  3576. 

  3577. #: ../../../CHANGELOG.md:1986

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

  3579. msgstr ""

  3580. 

  3581. #: ../../../CHANGELOG.md:1988

  3582. msgid "*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined with exposing services manually (setting `_bind_port` variables)"

  3583. msgstr ""

  3584. 

  3585. #: ../../../CHANGELOG.md:1989

  3586. msgid "*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in `http`-only mode (no SSL certificate retrieval)."

  3587. msgstr ""

  3588. 

  3589. #: ../../../CHANGELOG.md:1991

  3590. msgid "Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations."

  3591. msgstr ""

  3592. 

  3593. #: ../../../CHANGELOG.md:1993

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

  3595. msgstr ""

  3596. 

  3597. #: ../../../CHANGELOG.md:1995

  3598. msgid "The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks:"

  3599. msgstr ""

  3600. 

  3601. #: ../../../CHANGELOG.md:1997

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

  3603. msgstr ""

  3604. 

  3605. #: ../../../CHANGELOG.md:1998

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

  3607. msgstr ""

  3608. 

  3609. #: ../../../CHANGELOG.md:1999

  3610. msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) — for hosting the [Nextcloud](https://nextcloud.com/) groupware platform"

  3611. msgstr ""

  3612. 

  3613. #: ../../../CHANGELOG.md:2001

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

  3615. msgstr ""

  3616. 

  3617. #: ../../../CHANGELOG.md:2003

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

  3619. msgstr ""

  3620. 

  3621. #: ../../../CHANGELOG.md:2005

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

  3623. msgstr ""

  3624. 

  3625. #: ../../../CHANGELOG.md:2007

  3626. msgid "How do these changes fix all these problems?"

  3627. msgstr ""

  3628. 

  3629. #: ../../../CHANGELOG.md:2009

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

  3631. msgstr ""

  3632. 

  3633. #: ../../../CHANGELOG.md:2011

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

  3635. msgstr ""

  3636. 

  3637. #: ../../../CHANGELOG.md:2013

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

  3639. msgstr ""

  3640. 

  3641. #: ../../../CHANGELOG.md:2015

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

  3643. msgstr ""

  3644. 

  3645. #: ../../../CHANGELOG.md:2017

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

  3647. msgstr ""

  3648. 

  3649. #: ../../../CHANGELOG.md:2019

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

  3651. msgstr ""

  3652. 

  3653. #: ../../../CHANGELOG.md:2021

  3654. msgid "Where we're at right now?"

  3655. msgstr ""

  3656. 

  3657. #: ../../../CHANGELOG.md:2023

  3658. msgid "`matrix_playbook_reverse_proxy_type` still defaults to a value of `playbook-managed-nginx`."

  3659. msgstr ""

  3660. 

  3661. #: ../../../CHANGELOG.md:2025

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

  3663. msgstr ""

  3664. 

  3665. #: ../../../CHANGELOG.md:2027

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

  3667. msgstr ""

  3668. 

  3669. #: ../../../CHANGELOG.md:2029

  3670. msgid "How do I explicitly switch to Traefik right now?"

  3671. msgstr ""

  3672. 

  3673. #: ../../../CHANGELOG.md:2031

  3674. msgid "**Users who wish to migrate to Traefik** today, can do so by **adding** this to their configuration:"

  3675. msgstr ""

  3676. 

  3677. #: ../../../CHANGELOG.md:2037

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

  3679. msgstr ""

  3680. 

  3681. #: ../../../CHANGELOG.md:2039

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

  3683. msgstr ""

  3684. 

  3685. #: ../../../CHANGELOG.md:2041

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

  3687. msgstr ""

  3688. 

  3689. #: ../../../CHANGELOG.md:2043

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

  3691. msgstr ""

  3692. 

  3693. #: ../../../CHANGELOG.md:2045

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

  3695. msgstr ""

  3696. 

  3697. #: ../../../CHANGELOG.md:2047

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

  3699. msgstr ""

  3700. 

  3701. #: ../../../CHANGELOG.md:2049

  3702. msgid "Where we're going in the near future?"

  3703. msgstr ""

  3704. 

  3705. #: ../../../CHANGELOG.md:2051

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

  3707. msgstr ""

  3708. 

  3709. #: ../../../CHANGELOG.md:2053

  3710. msgid "For now, `matrix-nginx-proxy` will stay around."

  3711. msgstr ""

  3712. 

  3713. #: ../../../CHANGELOG.md:2055

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

  3715. msgstr ""

  3716. 

  3717. #: ../../../CHANGELOG.md:2057

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

  3719. msgstr ""

  3720. 

  3721. #: ../../../CHANGELOG.md:2059

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

  3723. msgstr ""

  3724. 

  3725. #: ../../../CHANGELOG.md:2060

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

  3727. msgstr ""

  3728. 

  3729. #: ../../../CHANGELOG.md:2062

  3730. msgid "How do I help?"

  3731. msgstr ""

  3732. 

  3733. #: ../../../CHANGELOG.md:2064

  3734. msgid "You can help by:"

  3735. msgstr ""

  3736. 

  3737. #: ../../../CHANGELOG.md:2066

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

  3739. msgstr ""

  3740. 

  3741. #: ../../../CHANGELOG.md:2068

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

  3743. msgstr ""

  3744. 

  3745. #: ../../../CHANGELOG.md:2070

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

  3747. msgstr ""

  3748. 

  3749. #: ../../../CHANGELOG.md:2073

  3750. msgid "2023-02-10"

  3751. msgstr ""

  3752. 

  3753. #: ../../../CHANGELOG.md:2075

  3754. msgid "Matrix Authentication Support for Jitsi"

  3755. msgstr ""

  3756. 

  3757. #: ../../../CHANGELOG.md:2077

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

  3759. msgstr ""

  3760. 

  3761. #: ../../../CHANGELOG.md:2079

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

  3763. msgstr ""

  3764. 

  3765. #: ../../../CHANGELOG.md:2081

  3766. msgid "Draupnir moderation tool (bot) support"

  3767. msgstr ""

  3768. 

  3769. #: ../../../CHANGELOG.md:2083

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

  3771. msgstr ""

  3772. 

  3773. #: ../../../CHANGELOG.md:2085

  3774. msgid "Additional details are available in [Setting up Draupnir](docs/configuring-playbook-bot-draupnir.md)."

  3775. msgstr ""

  3776. 

  3777. #: ../../../CHANGELOG.md:2088

  3778. msgid "2023-02-05"

  3779. msgstr ""

  3780. 

  3781. #: ../../../CHANGELOG.md:2090

  3782. msgid "The matrix-prometheus-postgres-exporter role lives independently now"

  3783. msgstr ""

  3784. 

  3785. #: ../../../CHANGELOG.md:2092

  3786. msgid "**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3787. msgstr ""

  3788. 

  3789. #: ../../../CHANGELOG.md:2094

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

  3791. msgstr ""

  3792. 

  3793. #: ../../../CHANGELOG.md:2096

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

  3795. msgstr ""

  3796. 

  3797. #: ../../../CHANGELOG.md:2098

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

  3799. msgstr ""

  3800. 

  3801. #: ../../../CHANGELOG.md:2100

  3802. #: ../../../CHANGELOG.md:2142

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

  3804. msgstr ""

  3805. 

  3806. #: ../../../CHANGELOG.md:2103

  3807. msgid "2023-01-26"

  3808. msgstr ""

  3809. 

  3810. #: ../../../CHANGELOG.md:2105

  3811. msgid "coturn can now use host-networking"

  3812. msgstr ""

  3813. 

  3814. #: ../../../CHANGELOG.md:2107

  3815. msgid "Large coturn deployments (with a huge range of ports specified via `coturn_turn_udp_min_port` and `coturn_turn_udp_max_port`) experience a huge slowdown with how Docker publishes all these ports (setting up firewall forwarding rules), which leads to a very slow coturn service startup and shutdown."

  3816. msgstr ""

  3817. 

  3818. #: ../../../CHANGELOG.md:2109

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

  3820. msgstr ""

  3821. 

  3822. #: ../../../CHANGELOG.md:2115

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

  3824. msgstr ""

  3825. 

  3826. #: ../../../CHANGELOG.md:2117

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

  3828. msgstr ""

  3829. 

  3830. #: ../../../CHANGELOG.md:2119

  3831. msgid "(Backward Compatibility) Tightening coturn security can lead to connectivity issues"

  3832. msgstr ""

  3833. 

  3834. #: ../../../CHANGELOG.md:2121

  3835. msgid "**TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default coturn blocklists. They may need to override `coturn_denied_peer_ips` and remove some IP ranges from it."

  3836. msgstr ""

  3837. 

  3838. #: ../../../CHANGELOG.md:2123

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

  3840. msgstr ""

  3841. 

  3842. #: ../../../CHANGELOG.md:2125

  3843. msgid "If you access your Matrix server from a local network and need coturn to relay to private IP addresses, you may observe that relaying is now blocked due to our new default `denied-peer-ip` lists (specified in `coturn_denied_peer_ips`). If you experience such connectivity problems, consider overriding this setting in your `vars.yml` file and removing certain networks from it."

  3844. msgstr ""

  3845. 

  3846. #: ../../../CHANGELOG.md:2127

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

  3848. msgstr ""

  3849. 

  3850. #: ../../../CHANGELOG.md:2130

  3851. msgid "2023-01-21"

  3852. msgstr ""

  3853. 

  3854. #: ../../../CHANGELOG.md:2132

  3855. msgid "The matrix-prometheus-node-exporter role lives independently now"

  3856. msgstr ""

  3857. 

  3858. #: ../../../CHANGELOG.md:2134

  3859. msgid "**TLDR**: the `matrix-prometheus-node-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  3860. msgstr ""

  3861. 

  3862. #: ../../../CHANGELOG.md:2136

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

  3864. msgstr ""

  3865. 

  3866. #: ../../../CHANGELOG.md:2138

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

  3868. msgstr ""

  3869. 

  3870. #: ../../../CHANGELOG.md:2140

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

  3872. msgstr ""

  3873. 

  3874. #: ../../../CHANGELOG.md:2145

  3875. msgid "2023-01-13"

  3876. msgstr ""

  3877. 

  3878. #: ../../../CHANGELOG.md:2147

  3879. msgid "Support for running commands via just"

  3880. msgstr ""

  3881. 

  3882. #: ../../../CHANGELOG.md:2149

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

  3884. msgstr ""

  3885. 

  3886. #: ../../../CHANGELOG.md:2151

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

  3888. msgstr ""

  3889. 

  3890. #: ../../../CHANGELOG.md:2153

  3891. msgid "Our [justfile](justfile) already defines some additional helpful **shortcut** commands that weren't part of our `Makefile`. Here are some examples:"

  3892. msgstr ""

  3893. 

  3894. #: ../../../CHANGELOG.md:2155

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

  3896. msgstr ""

  3897. 

  3898. #: ../../../CHANGELOG.md:2156

  3899. msgid "`just install-all --ask-vault-pass` — commands also support additional arguments (`--ask-vault-pass` will be appended to the above installation command)"

  3900. msgstr ""

  3901. 

  3902. #: ../../../CHANGELOG.md:2157

  3903. msgid "`just run-tags install-mautrix-slack,start` — to run specific playbook tags"

  3904. msgstr ""

  3905. 

  3906. #: ../../../CHANGELOG.md:2158

  3907. msgid "`just start-all` — (re-)starts all services"

  3908. msgstr ""

  3909. 

  3910. #: ../../../CHANGELOG.md:2159

  3911. msgid "`just stop-group postgres` — to stop only the Postgres service"

  3912. msgstr ""

  3913. 

  3914. #: ../../../CHANGELOG.md:2160

  3915. msgid "`just register-user alice secret-password yes` — registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)"

  3916. msgstr ""

  3917. 

  3918. #: ../../../CHANGELOG.md:2162

  3919. msgid "Additional helpful commands and shortcuts may be defined in the future."

  3920. msgstr ""

  3921. 

  3922. #: ../../../CHANGELOG.md:2164

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

  3924. msgstr ""

  3925. 

  3926. #: ../../../CHANGELOG.md:2167

  3927. msgid "2023-01-11"

  3928. msgstr ""

  3929. 

  3930. #: ../../../CHANGELOG.md:2169

  3931. msgid "mautrix-slack support"

  3932. msgstr ""

  3933. 

  3934. #: ../../../CHANGELOG.md:2171

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

  3936. msgstr ""

  3937. 

  3938. #: ../../../CHANGELOG.md:2173

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

  3940. msgstr ""

  3941. 

  3942. #: ../../../CHANGELOG.md:2176

  3943. msgid "2023-01-10"

  3944. msgstr ""

  3945. 

  3946. #: ../../../CHANGELOG.md:2178

  3947. msgid "ChatGPT support"

  3948. msgstr ""

  3949. 

  3950. #: ../../../CHANGELOG.md:2180

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

  3952. msgstr ""

  3953. 

  3954. #: ../../../CHANGELOG.md:2182

  3955. msgid "See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-chatgpt.md) documentation to get started."

  3956. msgstr ""

  3957. 

  3958. #: ../../../CHANGELOG.md:2185

  3959. msgid "2022-11-30"

  3960. msgstr ""

  3961. 

  3962. #: ../../../CHANGELOG.md:2187

  3963. msgid "matrix-postgres-backup has been replaced by the ansible-role-postgres-backup external role"

  3964. msgstr ""

  3965. 

  3966. #: ../../../CHANGELOG.md:2189

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

  3968. msgstr ""

  3969. 

  3970. #: ../../../CHANGELOG.md:2191

  3971. msgid "You'll need to rename your `matrix_postgres_backup`-prefixed variables such that they use a `postgres_backup` prefix."

  3972. msgstr ""

  3973. 

  3974. #: ../../../CHANGELOG.md:2194

  3975. msgid "2022-11-28"

  3976. msgstr ""

  3977. 

  3978. #: ../../../CHANGELOG.md:2196

  3979. msgid "matrix-postgres has been replaced by the ansible-role-postgres external role"

  3980. msgstr ""

  3981. 

  3982. #: ../../../CHANGELOG.md:2198

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

  3984. msgstr ""

  3985. 

  3986. #: ../../../CHANGELOG.md:2200

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

  3988. msgstr ""

  3989. 

  3990. #: ../../../CHANGELOG.md:2202

  3991. msgid "The new role is an upgraded version of the old `matrix-postgres` role with these notable differences:"

  3992. msgstr ""

  3993. 

  3994. #: ../../../CHANGELOG.md:2204

  3995. msgid "it uses different names for its variables (`matrix_postgres` -> `devture_postgres`)"

  3996. msgstr ""

  3997. 

  3998. #: ../../../CHANGELOG.md:2205

  3999. msgid "when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-postgresql), it will vacuum all your databases, not just the Synapse one"

  4000. msgstr ""

  4001. 

  4002. #: ../../../CHANGELOG.md:2207

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

  4004. msgstr ""

  4005. 

  4006. #: ../../../CHANGELOG.md:2209

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

  4008. msgstr ""

  4009. 

  4010. #: ../../../CHANGELOG.md:2211

  4011. msgid "The playbook no longer installs scripts to /usr/local/bin"

  4012. msgstr ""

  4013. 

  4014. #: ../../../CHANGELOG.md:2213

  4015. msgid "The locations of various scripts installed by the playbook have changed."

  4016. msgstr ""

  4017. 

  4018. #: ../../../CHANGELOG.md:2215

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

  4020. msgstr ""

  4021. 

  4022. #: ../../../CHANGELOG.md:2217

  4023. msgid "`/usr/local/bin/matrix-remove-all` -> `/matrix/bin/remove-all`"

  4024. msgstr ""

  4025. 

  4026. #: ../../../CHANGELOG.md:2218

  4027. msgid "`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`"

  4028. msgstr ""

  4029. 

  4030. #: ../../../CHANGELOG.md:2219

  4031. msgid "`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> `/matrix/ssl/bin/lets-encrypt-certificates-renew`"

  4032. msgstr ""

  4033. 

  4034. #: ../../../CHANGELOG.md:2220

  4035. msgid "`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin/register-user`"

  4036. msgstr ""

  4037. 

  4038. #: ../../../CHANGELOG.md:2223

  4039. msgid "2022-11-25"

  4040. msgstr ""

  4041. 

  4042. #: ../../../CHANGELOG.md:2225

  4043. msgid "2x-5x performance improvements in playbook runtime"

  4044. msgstr ""

  4045. 

  4046. #: ../../../CHANGELOG.md:2227

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

  4048. msgstr ""

  4049. 

  4050. #: ../../../CHANGELOG.md:2229

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

  4052. msgstr ""

  4053. 

  4054. #: ../../../CHANGELOG.md:2231

  4055. msgid "Even when running `ansible-playbook` manually (as most of us here do), it's beneficial not to waste time and CPU resources."

  4056. msgstr ""

  4057. 

  4058. #: ../../../CHANGELOG.md:2233

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

  4060. msgstr ""

  4061. 

  4062. #: ../../../CHANGELOG.md:2235

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

  4064. msgstr ""

  4065. 

  4066. #: ../../../CHANGELOG.md:2237

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

  4068. msgstr ""

  4069. 

  4070. #: ../../../CHANGELOG.md:2239

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

  4072. msgstr ""

  4073. 

  4074. #: ../../../CHANGELOG.md:2241

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

  4076. msgstr ""

  4077. 

  4078. #: ../../../CHANGELOG.md:2244

  4079. msgid "2022-11-22"

  4080. msgstr ""

  4081. 

  4082. #: ../../../CHANGELOG.md:2246

  4083. msgid "Automatic `matrix_architecture` determination"

  4084. msgstr ""

  4085. 

  4086. #: ../../../CHANGELOG.md:2248

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

  4088. msgstr ""

  4089. 

  4090. #: ../../../CHANGELOG.md:2250

  4091. msgid "Docker and the Docker SDK for Python are now installed via external roles"

  4092. msgstr ""

  4093. 

  4094. #: ../../../CHANGELOG.md:2254

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

  4096. msgstr ""

  4097. 

  4098. #: ../../../CHANGELOG.md:2256

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

  4100. msgstr ""

  4101. 

  4102. #: ../../../CHANGELOG.md:2258

  4103. msgid "If you're hitting issues with Docker installation or Docker SDK for Python installation, consider reporting bugs or contributing to these other projects."

  4104. msgstr ""

  4105. 

  4106. #: ../../../CHANGELOG.md:2260

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

  4108. msgstr ""

  4109. 

  4110. #: ../../../CHANGELOG.md:2263

  4111. msgid "2022-11-20"

  4112. msgstr ""

  4113. 

  4114. #: ../../../CHANGELOG.md:2265

  4115. msgid "(Backward Compatibility Break) Changing how reverse-proxying to Synapse works — now via a `matrix-synapse-reverse-proxy-companion` service"

  4116. msgstr ""

  4117. 

  4118. #: ../../../CHANGELOG.md:2267

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

  4120. msgstr ""

  4121. 

  4122. #: ../../../CHANGELOG.md:2269

  4123. msgid "Background"

  4124. msgstr ""

  4125. 

  4126. #: ../../../CHANGELOG.md:2271

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

  4128. msgstr ""

  4129. 

  4130. #: ../../../CHANGELOG.md:2273

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

  4132. msgstr ""

  4133. 

  4134. #: ../../../CHANGELOG.md:2275

  4135. msgid "Solution"

  4136. msgstr ""

  4137. 

  4138. #: ../../../CHANGELOG.md:2277

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

  4140. msgstr ""

  4141. 

  4142. #: ../../../CHANGELOG.md:2279

  4143. msgid "serve as a companion to Synapse and know how to reverse-proxy to Synapse correctly (no matter if workers are enabled or not)"

  4144. msgstr ""

  4145. 

  4146. #: ../../../CHANGELOG.md:2281

  4147. msgid "provide a unified container address for reaching Synapse (no matter if workers are enabled or not)"

  4148. msgstr ""

  4149. 

  4150. #: ../../../CHANGELOG.md:2282

  4151. msgid "`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server API traffic"

  4152. msgstr ""

  4153. 

  4154. #: ../../../CHANGELOG.md:2283

  4155. msgid "`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server (Federation) API traffic"

  4156. msgstr ""

  4157. 

  4158. #: ../../../CHANGELOG.md:2285

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

  4160. msgstr ""

  4161. 

  4162. #: ../../../CHANGELOG.md:2287

  4163. msgid "allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is disabled"

  4164. msgstr ""

  4165. 

  4166. #: ../../../CHANGELOG.md:2289

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

  4168. msgstr ""

  4169. 

  4170. #: ../../../CHANGELOG.md:2291

  4171. msgid "(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> (`matrix-synapse` or some Synapse worker))."

  4172. msgstr ""

  4173. 

  4174. #: ../../../CHANGELOG.md:2293

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

  4176. msgstr ""

  4177. 

  4178. #: ../../../CHANGELOG.md:2295

  4179. msgid "Webserver configuration"

  4180. msgstr ""

  4181. 

  4182. #: ../../../CHANGELOG.md:2297

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

  4184. msgstr ""

  4185. 

  4186. #: ../../../CHANGELOG.md:2299

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

  4188. msgstr ""

  4189. 

  4190. #: ../../../CHANGELOG.md:2301

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

  4192. msgstr ""

  4193. 

  4194. #: ../../../CHANGELOG.md:2303

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

  4196. msgstr ""

  4197. 

  4198. #: ../../../CHANGELOG.md:2305

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

  4200. msgstr ""

  4201. 

  4202. #: ../../../CHANGELOG.md:2308

  4203. msgid "2022-11-05"

  4204. msgstr ""

  4205. 

  4206. #: ../../../CHANGELOG.md:2310

  4207. msgid "(Backward Compatibility Break) A new default standalone mode for Etherpad"

  4208. msgstr ""

  4209. 

  4210. #: ../../../CHANGELOG.md:2312

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

  4212. msgstr ""

  4213. 

  4214. #: ../../../CHANGELOG.md:2314

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

  4216. msgstr ""

  4217. 

  4218. #: ../../../CHANGELOG.md:2316

  4219. msgid "If you've already got both Etherpad and Dimension in use you could:"

  4220. msgstr ""

  4221. 

  4222. #: ../../../CHANGELOG.md:2318

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

  4224. msgstr ""

  4225. 

  4226. #: ../../../CHANGELOG.md:2320

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

  4228. msgstr ""

  4229. 

  4230. #: ../../../CHANGELOG.md:2323

  4231. msgid "2022-11-04"

  4232. msgstr ""

  4233. 

  4234. #: ../../../CHANGELOG.md:2325

  4235. msgid "The playbook now uses external roles for some things"

  4236. msgstr ""

  4237. 

  4238. #: ../../../CHANGELOG.md:2327

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

  4240. msgstr ""

  4241. 

  4242. #: ../../../CHANGELOG.md:2329

  4243. msgid "We're in the process of trimming the playbook and making it reuse Ansible roles."

  4244. msgstr ""

  4245. 

  4246. #: ../../../CHANGELOG.md:2331

  4247. msgid "Starting now, the playbook is composed of 2 types of Ansible roles:"

  4248. msgstr ""

  4249. 

  4250. #: ../../../CHANGELOG.md:2333

  4251. msgid "those that live within the playbook itself (`roles/custom/*`)"

  4252. msgstr ""

  4253. 

  4254. #: ../../../CHANGELOG.md:2335

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

  4256. msgstr ""

  4257. 

  4258. #: ../../../CHANGELOG.md:2337

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

  4260. msgstr ""

  4261. 

  4262. #: ../../../CHANGELOG.md:2339

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

  4264. msgstr ""

  4265. 

  4266. #: ../../../CHANGELOG.md:2341

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

  4268. msgstr ""

  4269. 

  4270. #: ../../../CHANGELOG.md:2344

  4271. msgid "2022-10-14"

  4272. msgstr ""

  4273. 

  4274. #: ../../../CHANGELOG.md:2346

  4275. msgid "synapse-s3-storage-provider support"

  4276. msgstr ""

  4277. 

  4278. #: ../../../CHANGELOG.md:2348

  4279. msgid "**`synapse-s3-storage-provider` support is very new and still relatively untested. Using it may cause data loss.**"

  4280. msgstr ""

  4281. 

  4282. #: ../../../CHANGELOG.md:2350

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

  4284. msgstr ""

  4285. 

  4286. #: ../../../CHANGELOG.md:2352

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

  4288. msgstr ""

  4289. 

  4290. #: ../../../CHANGELOG.md:2354

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

  4292. msgstr ""

  4293. 

  4294. #: ../../../CHANGELOG.md:2356

  4295. msgid "Synapse container image customization support"

  4296. msgstr ""

  4297. 

  4298. #: ../../../CHANGELOG.md:2358

  4299. msgid "We now support customizing the Synapse container image by adding additional build steps to its [`Dockerfile`](https://docs.docker.com/engine/reference/builder/)."

  4300. msgstr ""

  4301. 

  4302. #: ../../../CHANGELOG.md:2360

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

  4304. msgstr ""

  4305. 

  4306. #: ../../../CHANGELOG.md:2362

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

  4308. msgstr ""

  4309. 

  4310. #: ../../../CHANGELOG.md:2373

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

  4312. msgstr ""

  4313. 

  4314. #: ../../../CHANGELOG.md:2375

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

  4316. msgstr ""

  4317. 

  4318. #: ../../../CHANGELOG.md:2378

  4319. msgid "2022-10-02"

  4320. msgstr ""

  4321. 

  4322. #: ../../../CHANGELOG.md:2380

  4323. msgid "matrix-ldap-registration-proxy support"

  4324. msgstr ""

  4325. 

  4326. #: ../../../CHANGELOG.md:2382

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

  4328. msgstr ""

  4329. 

  4330. #: ../../../CHANGELOG.md:2384

  4331. msgid "See our [Setting up matrix-ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started."

  4332. msgstr ""

  4333. 

  4334. #: ../../../CHANGELOG.md:2387

  4335. msgid "2022-09-15"

  4336. msgstr ""

  4337. 

  4338. #: ../../../CHANGELOG.md:2389

  4339. msgid "(Potential Backward Compatibility Break) Major improvements to Synapse workers"

  4340. msgstr ""

  4341. 

  4342. #: ../../../CHANGELOG.md:2391

  4343. msgid "People who are interested in running a Synapse worker setup should know that **our Synapse worker implementation is much more powerful now**:"

  4344. msgstr ""

  4345. 

  4346. #: ../../../CHANGELOG.md:2393

  4347. msgid "we've added support for [Stream writers](#stream-writers-support)"

  4348. msgstr ""

  4349. 

  4350. #: ../../../CHANGELOG.md:2394

  4351. msgid "we've added support for [multiple federation sender workers](#multiple-federation-sender-workers-support)"

  4352. msgstr ""

  4353. 

  4354. #: ../../../CHANGELOG.md:2395

  4355. msgid "we've added support for [multiple pusher workers](#multiple-pusher-workers-support)"

  4356. msgstr ""

  4357. 

  4358. #: ../../../CHANGELOG.md:2396

  4359. msgid "we've added support for [running background tasks on a worker](#background-tasks-can-run-on-a-worker)"

  4360. msgstr ""

  4361. 

  4362. #: ../../../CHANGELOG.md:2397

  4363. msgid "we've restored support for [`appservice` workers](#appservice-worker-support-is-back)"

  4364. msgstr ""

  4365. 

  4366. #: ../../../CHANGELOG.md:2398

  4367. msgid "we've restored support for [`user_dir` workers](#user-directory-worker-support-is-back)"

  4368. msgstr ""

  4369. 

  4370. #: ../../../CHANGELOG.md:2399

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

  4372. msgstr ""

  4373. 

  4374. #: ../../../CHANGELOG.md:2400

  4375. msgid "see the [Potential Backward Incompatibilities after these Synapse worker changes](#potential-backward-incompatibilities-after-these-synapse-worker-changes)"

  4376. msgstr ""

  4377. 

  4378. #: ../../../CHANGELOG.md:2402

  4379. msgid "Stream writers support"

  4380. msgstr ""

  4381. 

  4382. #: ../../../CHANGELOG.md:2404

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

  4384. msgstr ""

  4385. 

  4386. #: ../../../CHANGELOG.md:2406

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

  4388. msgstr ""

  4389. 

  4390. #: ../../../CHANGELOG.md:2408

  4391. msgid "If you'd like to customize the number of workers we also make that possible using these variables:"

  4392. msgstr ""

  4393. 

  4394. #: ../../../CHANGELOG.md:2421

  4395. msgid "Multiple federation sender workers support"

  4396. msgstr ""

  4397. 

  4398. #: ../../../CHANGELOG.md:2423

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

  4400. msgstr ""

  4401. 

  4402. #: ../../../CHANGELOG.md:2425

  4403. msgid "Multiple pusher workers support"

  4404. msgstr ""

  4405. 

  4406. #: ../../../CHANGELOG.md:2427

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

  4408. msgstr ""

  4409. 

  4410. #: ../../../CHANGELOG.md:2429

  4411. msgid "Background tasks can run on a worker"

  4412. msgstr ""

  4413. 

  4414. #: ../../../CHANGELOG.md:2431

  4415. msgid "From now on, you can put [background task processing on a worker](https://matrix-org.github.io/synapse/latest/workers.html#background-tasks)."

  4416. msgstr ""

  4417. 

  4418. #: ../../../CHANGELOG.md:2433

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

  4420. msgstr ""

  4421. 

  4422. #: ../../../CHANGELOG.md:2435

  4423. msgid "Appservice worker support is back"

  4424. msgstr ""

  4425. 

  4426. #: ../../../CHANGELOG.md:2437

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

  4428. msgstr ""

  4429. 

  4430. #: ../../../CHANGELOG.md:2439

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

  4432. msgstr ""

  4433. 

  4434. #: ../../../CHANGELOG.md:2441

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

  4436. msgstr ""

  4437. 

  4438. #: ../../../CHANGELOG.md:2443

  4439. msgid "User Directory worker support is back"

  4440. msgstr ""

  4441. 

  4442. #: ../../../CHANGELOG.md:2445

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

  4444. msgstr ""

  4445. 

  4446. #: ../../../CHANGELOG.md:2447

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

  4448. msgstr ""

  4449. 

  4450. #: ../../../CHANGELOG.md:2449

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

  4452. msgstr ""

  4453. 

  4454. #: ../../../CHANGELOG.md:2451

  4455. msgid "Using more than 1 media repository worker is now more reliable"

  4456. msgstr ""

  4457. 

  4458. #: ../../../CHANGELOG.md:2453

  4459. msgid "With `matrix_synapse_workers_preset: one-of-each`, we only launch one `media_repository` worker."

  4460. msgstr ""

  4461. 

  4462. #: ../../../CHANGELOG.md:2455

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

  4464. msgstr ""

  4465. 

  4466. #: ../../../CHANGELOG.md:2457

  4467. msgid "Potential Backward Incompatibilities after these Synapse worker changes"

  4468. msgstr ""

  4469. 

  4470. #: ../../../CHANGELOG.md:2459

  4471. msgid "Below we'll discuss **potential backward incompatibilities**."

  4472. msgstr ""

  4473. 

  4474. #: ../../../CHANGELOG.md:2461

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

  4476. msgstr ""

  4477. 

  4478. #: ../../../CHANGELOG.md:2463

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

  4480. msgstr ""

  4481. 

  4482. #: ../../../CHANGELOG.md:2465

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

  4484. msgstr ""

  4485. 

  4486. #: ../../../CHANGELOG.md:2467

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

  4488. msgstr ""

  4489. 

  4490. #: ../../../CHANGELOG.md:2470

  4491. msgid "2022-09-09"

  4492. msgstr ""

  4493. 

  4494. #: ../../../CHANGELOG.md:2472

  4495. msgid "Cactus Comments support"

  4496. msgstr ""

  4497. 

  4498. #: ../../../CHANGELOG.md:2474

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

  4500. msgstr ""

  4501. 

  4502. #: ../../../CHANGELOG.md:2476

  4503. msgid "See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-comments.md) documentation to get started."

  4504. msgstr ""

  4505. 

  4506. #: ../../../CHANGELOG.md:2479

  4507. msgid "2022-08-23"

  4508. msgstr ""

  4509. 

  4510. #: ../../../CHANGELOG.md:2481

  4511. msgid "Postmoogle email bridge support"

  4512. msgstr ""

  4513. 

  4514. #: ../../../CHANGELOG.md:2483

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

  4516. msgstr ""

  4517. 

  4518. #: ../../../CHANGELOG.md:2485

  4519. msgid "See our [Setting up Postmoogle email bridging](docs/configuring-playbook-bridge-postmoogle.md) documentation to get started."

  4520. msgstr ""

  4521. 

  4522. #: ../../../CHANGELOG.md:2488

  4523. msgid "2022-08-10"

  4524. msgstr ""

  4525. 

  4526. #: ../../../CHANGELOG.md:2490

  4527. msgid "mautrix-whatsapp default configuration changes"

  4528. msgstr ""

  4529. 

  4530. #: ../../../CHANGELOG.md:2492

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

  4532. msgstr ""

  4533. 

  4534. #: ../../../CHANGELOG.md:2494

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

  4536. msgstr ""

  4537. 

  4538. #: ../../../CHANGELOG.md:2496

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

  4540. msgstr ""

  4541. 

  4542. #: ../../../CHANGELOG.md:2499

  4543. msgid "2022-08-09"

  4544. msgstr ""

  4545. 

  4546. #: ../../../CHANGELOG.md:2501

  4547. msgid "Conduit support"

  4548. msgstr ""

  4549. 

  4550. #: ../../../CHANGELOG.md:2503

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

  4552. msgstr ""

  4553. 

  4554. #: ../../../CHANGELOG.md:2505

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

  4556. msgstr ""

  4557. 

  4558. #: ../../../CHANGELOG.md:2507

  4559. msgid "To try out Conduit, we recommend that you **use a new server** and the following `vars.yml` configuration:"

  4560. msgstr ""

  4561. 

  4562. #: ../../../CHANGELOG.md:2513

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

  4564. msgstr ""

  4565. 

  4566. #: ../../../CHANGELOG.md:2516

  4567. msgid "2022-07-29"

  4568. msgstr ""

  4569. 

  4570. #: ../../../CHANGELOG.md:2518

  4571. msgid "mautrix-discord support"

  4572. msgstr ""

  4573. 

  4574. #: ../../../CHANGELOG.md:2520

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

  4576. msgstr ""

  4577. 

  4578. #: ../../../CHANGELOG.md:2522

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

  4580. msgstr ""

  4581. 

  4582. #: ../../../CHANGELOG.md:2525

  4583. msgid "2022-07-27"

  4584. msgstr ""

  4585. 

  4586. #: ../../../CHANGELOG.md:2527

  4587. msgid "matrix-appservice-kakaotalk support"

  4588. msgstr ""

  4589. 

  4590. #: ../../../CHANGELOG.md:2529

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

  4592. msgstr ""

  4593. 

  4594. #: ../../../CHANGELOG.md:2531

  4595. msgid "See our [Setting up Appservice Kakaotalk bridging](docs/configuring-playbook-bridge-appservice-kakaotalk.md) documentation to get started."

  4596. msgstr ""

  4597. 

  4598. #: ../../../CHANGELOG.md:2534

  4599. msgid "2022-07-20"

  4600. msgstr ""

  4601. 

  4602. #: ../../../CHANGELOG.md:2536

  4603. msgid "maubot support"

  4604. msgstr ""

  4605. 

  4606. #: ../../../CHANGELOG.md:2538

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

  4608. msgstr ""

  4609. 

  4610. #: ../../../CHANGELOG.md:2540

  4611. msgid "See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) documentation to get started."

  4612. msgstr ""

  4613. 

  4614. #: ../../../CHANGELOG.md:2543

  4615. msgid "2022-07-14"

  4616. msgstr ""

  4617. 

  4618. #: ../../../CHANGELOG.md:2545

  4619. msgid "mx-puppet-skype removal"

  4620. msgstr ""

  4621. 

  4622. #: ../../../CHANGELOG.md:2547

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

  4624. msgstr ""

  4625. 

  4626. #: ../../../CHANGELOG.md:2549

  4627. msgid "To completely clean up your server from `mx-puppet-skype`'s presence on it:"

  4628. msgstr ""

  4629. 

  4630. #: ../../../CHANGELOG.md:2551

  4631. msgid "ensure your Ansible configuration (`vars.yml` file) no longer contains `matrix_mx_puppet_skype_*` references"

  4632. msgstr ""

  4633. 

  4634. #: ../../../CHANGELOG.md:2552

  4635. msgid "stop and disable the systemd service (run `systemctl disable --now matrix-mx-puppet-skype` on the server)"

  4636. msgstr ""

  4637. 

  4638. #: ../../../CHANGELOG.md:2553

  4639. msgid "delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-skype.service` on the server)"

  4640. msgstr ""

  4641. 

  4642. #: ../../../CHANGELOG.md:2554

  4643. msgid "delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on the server)"

  4644. msgstr ""

  4645. 

  4646. #: ../../../CHANGELOG.md:2555

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

  4648. msgstr ""

  4649. 

  4650. #: ../../../CHANGELOG.md:2557

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

  4652. msgstr ""

  4653. 

  4654. #: ../../../CHANGELOG.md:2559

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

  4656. msgstr ""

  4657. 

  4658. #: ../../../CHANGELOG.md:2561

  4659. msgid "signald (0.19.0+) upgrade requires data migration"

  4660. msgstr ""

  4661. 

  4662. #: ../../../CHANGELOG.md:2563

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

  4664. msgstr ""

  4665. 

  4666. #: ../../../CHANGELOG.md:2565

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

  4668. msgstr ""

  4669. 

  4670. #: ../../../CHANGELOG.md:2567

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

  4672. msgstr ""

  4673. 

  4674. #: ../../../CHANGELOG.md:2569

  4675. msgid "We attempt to do this data migration automatically every time Signald starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` systemd unit definition."

  4676. msgstr ""

  4677. 

  4678. #: ../../../CHANGELOG.md:2571

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

  4680. msgstr ""

  4681. 

  4682. #: ../../../CHANGELOG.md:2574

  4683. msgid "2022-07-05"

  4684. msgstr ""

  4685. 

  4686. #: ../../../CHANGELOG.md:2576

  4687. msgid "Ntfy push notifications support"

  4688. msgstr ""

  4689. 

  4690. #: ../../../CHANGELOG.md:2578

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

  4692. msgstr ""

  4693. 

  4694. #: ../../../CHANGELOG.md:2580

  4695. msgid "See our [Setting up the ntfy push notifications server](docs/configuring-playbook-ntfy.md) documentation to get started."

  4696. msgstr ""

  4697. 

  4698. #: ../../../CHANGELOG.md:2583

  4699. msgid "2022-06-23"

  4700. msgstr ""

  4701. 

  4702. #: ../../../CHANGELOG.md:2585

  4703. msgid "(Potential Backward Compatibility Break) Changes around metrics collection"

  4704. msgstr ""

  4705. 

  4706. #: ../../../CHANGELOG.md:2587

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

  4708. msgstr ""

  4709. 

  4710. #: ../../../CHANGELOG.md:2589

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

  4712. msgstr ""

  4713. 

  4714. #: ../../../CHANGELOG.md:2591

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

  4716. msgstr ""

  4717. 

  4718. #: ../../../CHANGELOG.md:2593

  4719. msgid "**If you are using the [Hookshot bridge](docs/configuring-playbook-bridge-hookshot.md)**, you may find that:"

  4720. msgstr ""

  4721. 

  4722. #: ../../../CHANGELOG.md:2594

  4723. msgid "**Metrics may not be enabled by default anymore**:"

  4724. msgstr ""

  4725. 

  4726. #: ../../../CHANGELOG.md:2595

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

  4728. msgstr ""

  4729. 

  4730. #: ../../../CHANGELOG.md:2596

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

  4732. msgstr ""

  4733. 

  4734. #: ../../../CHANGELOG.md:2597

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

  4736. msgstr ""

  4737. 

  4738. #: ../../../CHANGELOG.md:2598

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

  4740. msgstr ""

  4741. 

  4742. #: ../../../CHANGELOG.md:2600

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

  4744. msgstr ""

  4745. 

  4746. #: ../../../CHANGELOG.md:2602

  4747. msgid "**If you're using [postgres-exporter](docs/configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-postgres-optional)** (`prometheus_postgres_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/postgres-exporter`."

  4748. msgstr ""

  4749. 

  4750. #: ../../../CHANGELOG.md:2604

  4751. msgid "**If you're using Synapse** and would like to collect its metrics from an external Prometheus server, you may find that:"

  4752. msgstr ""

  4753. 

  4754. #: ../../../CHANGELOG.md:2606

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

  4756. msgstr ""

  4757. 

  4758. #: ../../../CHANGELOG.md:2607

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

  4760. msgstr ""

  4761. 

  4762. #: ../../../CHANGELOG.md:2608

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

  4764. msgstr ""

  4765. 

  4766. #: ../../../CHANGELOG.md:2609

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

  4768. msgstr ""

  4769. 

  4770. #: ../../../CHANGELOG.md:2611

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

  4772. msgstr ""

  4773. 

  4774. #: ../../../CHANGELOG.md:2613

  4775. msgid "2022-06-13"

  4776. msgstr ""

  4777. 

  4778. #: ../../../CHANGELOG.md:2615

  4779. msgid "go-skype-bridge bridging support"

  4780. msgstr ""

  4781. 

  4782. #: ../../../CHANGELOG.md:2617

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

  4784. msgstr ""

  4785. 

  4786. #: ../../../CHANGELOG.md:2619

  4787. msgid "See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md) documentation to get started."

  4788. msgstr ""

  4789. 

  4790. #: ../../../CHANGELOG.md:2621

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

  4792. msgstr ""

  4793. 

  4794. #: ../../../CHANGELOG.md:2624

  4795. msgid "2022-06-09"

  4796. msgstr ""

  4797. 

  4798. #: ../../../CHANGELOG.md:2626

  4799. msgid "Running Ansible in a container can now happen on the Matrix server itself"

  4800. msgstr ""

  4801. 

  4802. #: ../../../CHANGELOG.md:2628

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

  4804. msgstr ""

  4805. 

  4806. #: ../../../CHANGELOG.md:2631

  4807. msgid "2022-05-31"

  4808. msgstr ""

  4809. 

  4810. #: ../../../CHANGELOG.md:2633

  4811. msgid "Synapse v1.60 upgrade may cause trouble and require manual intervention"

  4812. msgstr ""

  4813. 

  4814. #: ../../../CHANGELOG.md:2635

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

  4816. msgstr ""

  4817. 

  4818. #: ../../../CHANGELOG.md:2637

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

  4820. msgstr ""

  4821. 

  4822. #: ../../../CHANGELOG.md:2639

  4823. msgid "**If Synapse fails to start** after your next playbook run, you'll need to:"

  4824. msgstr ""

  4825. 

  4826. #: ../../../CHANGELOG.md:2641

  4827. msgid "SSH into the Matrix server"

  4828. msgstr ""

  4829. 

  4830. #: ../../../CHANGELOG.md:2642

  4831. msgid "launch `/usr/local/bin/matrix-postgres-cli`"

  4832. msgstr ""

  4833. 

  4834. #: ../../../CHANGELOG.md:2643

  4835. msgid "switch to the `synapse` database: `\\c synapse`"

  4836. msgstr ""

  4837. 

  4838. #: ../../../CHANGELOG.md:2644

  4839. msgid "run the following SQL query:"

  4840. msgstr ""

  4841. 

  4842. #: ../../../CHANGELOG.md:2663

  4843. msgid "You could then restart services: `ansible-playbook -i inventory/hosts setup.yml --tags=start`"

  4844. msgstr ""

  4845. 

  4846. #: ../../../CHANGELOG.md:2666

  4847. msgid "2022-04-25"

  4848. msgstr ""

  4849. 

  4850. #: ../../../CHANGELOG.md:2668

  4851. msgid "Buscarron bot support"

  4852. msgstr ""

  4853. 

  4854. #: ../../../CHANGELOG.md:2670

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

  4856. msgstr ""

  4857. 

  4858. #: ../../../CHANGELOG.md:2672

  4859. msgid "See our [Setting up Buscarron](docs/configuring-playbook-bot-buscarron.md) documentation to get started."

  4860. msgstr ""

  4861. 

  4862. #: ../../../CHANGELOG.md:2675

  4863. msgid "2022-04-21"

  4864. msgstr ""

  4865. 

  4866. #: ../../../CHANGELOG.md:2677

  4867. msgid "matrix-registration-bot support"

  4868. msgstr ""

  4869. 

  4870. #: ../../../CHANGELOG.md:2679

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

  4872. msgstr ""

  4873. 

  4874. #: ../../../CHANGELOG.md:2681

  4875. msgid "See our [Setting up matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) documentation to get started."

  4876. msgstr ""

  4877. 

  4878. #: ../../../CHANGELOG.md:2684

  4879. msgid "2022-04-19"

  4880. msgstr ""

  4881. 

  4882. #: ../../../CHANGELOG.md:2686

  4883. msgid "BorgBackup support"

  4884. msgstr ""

  4885. 

  4886. #: ../../../CHANGELOG.md:2688

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

  4888. msgstr ""

  4889. 

  4890. #: ../../../CHANGELOG.md:2690

  4891. msgid "See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md) documentation to get started."

  4892. msgstr ""

  4893. 

  4894. #: ../../../CHANGELOG.md:2692

  4895. msgid "(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action"

  4896. msgstr ""

  4897. 

  4898. #: ../../../CHANGELOG.md:2694

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

  4900. msgstr ""

  4901. 

  4902. #: ../../../CHANGELOG.md:2696

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

  4904. msgstr ""

  4905. 

  4906. #: ../../../CHANGELOG.md:2698

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

  4908. msgstr ""

  4909. 

  4910. #: ../../../CHANGELOG.md:2700

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

  4912. msgstr ""

  4913. 

  4914. #: ../../../CHANGELOG.md:2702

  4915. msgid "Pull the latest playbook changes"

  4916. msgstr ""

  4917. 

  4918. #: ../../../CHANGELOG.md:2703

  4919. msgid "Stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"

  4920. msgstr ""

  4921. 

  4922. #: ../../../CHANGELOG.md:2704

  4923. msgid "Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all`)"

  4924. msgstr ""

  4925. 

  4926. #: ../../../CHANGELOG.md:2705

  4927. msgid "Start Postgres (`systemctl start matrix-postgres` on the server)"

  4928. msgstr ""

  4929. 

  4930. #: ../../../CHANGELOG.md:2706

  4931. msgid "Start the main Synapse process (`systemctl start matrix-synapse` on the server)"

  4932. msgstr ""

  4933. 

  4934. #: ../../../CHANGELOG.md:2707

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

  4936. msgstr ""

  4937. 

  4938. #: ../../../CHANGELOG.md:2708

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

  4940. msgstr ""

  4941. 

  4942. #: ../../../CHANGELOG.md:2711

  4943. msgid "2022-04-14"

  4944. msgstr ""

  4945. 

  4946. #: ../../../CHANGELOG.md:2713

  4947. msgid "(Compatibility Break) Changes to `docker-src` permissions necessitating manual action"

  4948. msgstr ""

  4949. 

  4950. #: ../../../CHANGELOG.md:2715

  4951. msgid "Users who build container images from source will need to manually correct file permissions of some directories on the server."

  4952. msgstr ""

  4953. 

  4954. #: ../../../CHANGELOG.md:2717

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

  4956. msgstr ""

  4957. 

  4958. #: ../../../CHANGELOG.md:2719

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

  4960. msgstr ""

  4961. 

  4962. #: ../../../CHANGELOG.md:2721

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

  4964. msgstr ""

  4965. 

  4966. #: ../../../CHANGELOG.md:2724

  4967. msgid "2022-03-17"

  4968. msgstr ""

  4969. 

  4970. #: ../../../CHANGELOG.md:2726

  4971. msgid "(Compatibility Break) ma1sd identity server no longer installed by default"

  4972. msgstr ""

  4973. 

  4974. #: ../../../CHANGELOG.md:2728

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

  4976. msgstr ""

  4977. 

  4978. #: ../../../CHANGELOG.md:2730

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

  4980. msgstr ""

  4981. 

  4982. #: ../../../CHANGELOG.md:2732

  4983. msgid "Since Element clients no longer default to using a public identity server if another one is not provided, we can stop installing ma1sd."

  4984. msgstr ""

  4985. 

  4986. #: ../../../CHANGELOG.md:2734

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

  4988. msgstr ""

  4989. 

  4990. #: ../../../CHANGELOG.md:2741

  4991. msgid "2022-02-12"

  4992. msgstr ""

  4993. 

  4994. #: ../../../CHANGELOG.md:2743

  4995. msgid "matrix_encryption_disabler support"

  4996. msgstr ""

  4997. 

  4998. #: ../../../CHANGELOG.md:2745

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

  5000. msgstr ""

  5001. 

  5002. #: ../../../CHANGELOG.md:2747

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

  5004. msgstr ""

  5005. 

  5006. #: ../../../CHANGELOG.md:2750

  5007. msgid "2022-02-01"

  5008. msgstr ""

  5009. 

  5010. #: ../../../CHANGELOG.md:2752

  5011. msgid "matrix-hookshot bridging support"

  5012. msgstr ""

  5013. 

  5014. #: ../../../CHANGELOG.md:2754

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

  5016. msgstr ""

  5017. 

  5018. #: ../../../CHANGELOG.md:2757

  5019. msgid "2022-01-31"

  5020. msgstr ""

  5021. 

  5022. #: ../../../CHANGELOG.md:2759

  5023. msgid "ARM support for matrix-corporal"

  5024. msgstr ""

  5025. 

  5026. #: ../../../CHANGELOG.md:2761

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

  5028. msgstr ""

  5029. 

  5030. #: ../../../CHANGELOG.md:2764

  5031. msgid "2022-01-07"

  5032. msgstr ""

  5033. 

  5034. #: ../../../CHANGELOG.md:2766

  5035. msgid "Dendrite support"

  5036. msgstr ""

  5037. 

  5038. #: ../../../CHANGELOG.md:2768

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

  5040. msgstr ""

  5041. 

  5042. #: ../../../CHANGELOG.md:2770

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

  5044. msgstr ""

  5045. 

  5046. #: ../../../CHANGELOG.md:2772

  5047. msgid "We believe that 2022 will be the year of the non-Synapse Matrix server!"

  5048. msgstr ""

  5049. 

  5050. #: ../../../CHANGELOG.md:2774

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

  5052. msgstr ""

  5053. 

  5054. #: ../../../CHANGELOG.md:2776

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

  5056. msgstr ""

  5057. 

  5058. #: ../../../CHANGELOG.md:2778

  5059. msgid "Adapting the configuration for existing Synapse installations"

  5060. msgstr ""

  5061. 

  5062. #: ../../../CHANGELOG.md:2780

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

  5064. msgstr ""

  5065. 

  5066. #: ../../../CHANGELOG.md:2782

  5067. msgid "The `vars.yml` file for **existing installations will need to be updated** by adding this **additional configuration**:"

  5068. msgstr ""

  5069. 

  5070. #: ../../../CHANGELOG.md:2794

  5071. msgid "Trying out Dendrite"

  5072. msgstr ""

  5073. 

  5074. #: ../../../CHANGELOG.md:2796

  5075. msgid "Finally, **to try out Dendrite**, we recommend that you **use a new server** and the following addition to your `vars.yml` configuration:"

  5076. msgstr ""

  5077. 

  5078. #: ../../../CHANGELOG.md:2802

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

  5080. msgstr ""

  5081. 

  5082. #: ../../../CHANGELOG.md:2804

  5083. msgid "We're excited to gain support for other homeserver implementations, like [Conduit](https://conduit.rs/), etc!"

  5084. msgstr ""

  5085. 

  5086. #: ../../../CHANGELOG.md:2806

  5087. msgid "Honoroit bot support"

  5088. msgstr ""

  5089. 

  5090. #: ../../../CHANGELOG.md:2808

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

  5092. msgstr ""

  5093. 

  5094. #: ../../../CHANGELOG.md:2810

  5095. msgid "See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documentation to get started."

  5096. msgstr ""

  5097. 

  5098. #: ../../../CHANGELOG.md:2813

  5099. msgid "2022-01-06"

  5100. msgstr ""

  5101. 

  5102. #: ../../../CHANGELOG.md:2815

  5103. msgid "Cinny support"

  5104. msgstr ""

  5105. 

  5106. #: ../../../CHANGELOG.md:2817

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

  5108. msgstr ""

  5109. 

  5110. #: ../../../CHANGELOG.md:2819

  5111. msgid "By default, we still install Element Web. Still, people who'd like to try Cinny out can now install it via the playbook."

  5112. msgstr ""

  5113. 

  5114. #: ../../../CHANGELOG.md:2821

  5115. msgid "Additional details are available in [Setting up Cinny](docs/configuring-playbook-client-cinny.md)."

  5116. msgstr ""

  5117. 

  5118. #: ../../../CHANGELOG.md:2824

  5119. msgid "2021-12-22"

  5120. msgstr ""

  5121. 

  5122. #: ../../../CHANGELOG.md:2826

  5123. msgid "Twitter bridging support via mautrix-twitter"

  5124. msgstr ""

  5125. 

  5126. #: ../../../CHANGELOG.md:2828

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

  5128. msgstr ""

  5129. 

  5130. #: ../../../CHANGELOG.md:2831

  5131. msgid "2021-12-14"

  5132. msgstr ""

  5133. 

  5134. #: ../../../CHANGELOG.md:2833

  5135. msgid "(Security) Users of the Signal bridge may wish to upgrade it to work around log4j vulnerability"

  5136. msgstr ""

  5137. 

  5138. #: ../../../CHANGELOG.md:2835

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

  5140. msgstr ""

  5141. 

  5142. #: ../../../CHANGELOG.md:2837

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

  5144. msgstr ""

  5145. 

  5146. #: ../../../CHANGELOG.md:2840

  5147. msgid "2021-11-11"

  5148. msgstr ""

  5149. 

  5150. #: ../../../CHANGELOG.md:2842

  5151. msgid "Dropped support for Postgres v9.6"

  5152. msgstr ""

  5153. 

  5154. #: ../../../CHANGELOG.md:2844

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

  5156. msgstr ""

  5157. 

  5158. #: ../../../CHANGELOG.md:2846

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

  5160. msgstr ""

  5161. 

  5162. #: ../../../CHANGELOG.md:2849

  5163. msgid "2021-10-23"

  5164. msgstr ""

  5165. 

  5166. #: ../../../CHANGELOG.md:2851

  5167. msgid "Hangouts bridge no longer updated, superseded by a Googlechat bridge"

  5168. msgstr ""

  5169. 

  5170. #: ../../../CHANGELOG.md:2853

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

  5172. msgstr ""

  5173. 

  5174. #: ../../../CHANGELOG.md:2855

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

  5176. msgstr ""

  5177. 

  5178. #: ../../../CHANGELOG.md:2858

  5179. msgid "2021-08-23"

  5180. msgstr ""

  5181. 

  5182. #: ../../../CHANGELOG.md:2860

  5183. msgid "LinkedIn bridging support via beeper-linkedin"

  5184. msgstr ""

  5185. 

  5186. #: ../../../CHANGELOG.md:2862

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

  5188. msgstr ""

  5189. 

  5190. #: ../../../CHANGELOG.md:2864

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

  5192. msgstr ""

  5193. 

  5194. #: ../../../CHANGELOG.md:2866

  5195. msgid "To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)."

  5196. msgstr ""

  5197. 

  5198. #: ../../../CHANGELOG.md:2869

  5199. msgid "2021-08-20"

  5200. msgstr ""

  5201. 

  5202. #: ../../../CHANGELOG.md:2871

  5203. msgid "Sygnal upgraded — ARM support and no longer requires a database"

  5204. msgstr ""

  5205. 

  5206. #: ../../../CHANGELOG.md:2873

  5207. msgid "The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been upgraded from `v0.9.0` to `v0.10.1`."

  5208. msgstr ""

  5209. 

  5210. #: ../../../CHANGELOG.md:2875

  5211. msgid "This is an optional component for the playbook, so most of our users wouldn't care about this announcement."

  5212. msgstr ""

  5213. 

  5214. #: ../../../CHANGELOG.md:2877

  5215. msgid "Since this feels like a relatively big (and untested, as of yet) Sygnal change, we're putting up this changelog entry."

  5216. msgstr ""

  5217. 

  5218. #: ../../../CHANGELOG.md:2879

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

  5220. msgstr ""

  5221. 

  5222. #: ../../../CHANGELOG.md:2882

  5223. msgid "2021-05-21"

  5224. msgstr ""

  5225. 

  5226. #: ../../../CHANGELOG.md:2884

  5227. msgid "Hydrogen support"

  5228. msgstr ""

  5229. 

  5230. #: ../../../CHANGELOG.md:2886

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

  5232. msgstr ""

  5233. 

  5234. #: ../../../CHANGELOG.md:2888

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

  5236. msgstr ""

  5237. 

  5238. #: ../../../CHANGELOG.md:2890

  5239. msgid "Additional details are available in [Setting up Hydrogen](docs/configuring-playbook-client-hydrogen.md)."

  5240. msgstr ""

  5241. 

  5242. #: ../../../CHANGELOG.md:2893

  5243. msgid "2021-05-19"

  5244. msgstr ""

  5245. 

  5246. #: ../../../CHANGELOG.md:2895

  5247. msgid "Heisenbridge support"

  5248. msgstr ""

  5249. 

  5250. #: ../../../CHANGELOG.md:2897

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

  5252. msgstr ""

  5253. 

  5254. #: ../../../CHANGELOG.md:2899

  5255. msgid "Additional details are available in [Setting up Heisenbridge bouncer-style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)."

  5256. msgstr ""

  5257. 

  5258. #: ../../../CHANGELOG.md:2902

  5259. msgid "2021-04-16"

  5260. msgstr ""

  5261. 

  5262. #: ../../../CHANGELOG.md:2904

  5263. msgid "Disabling TLSv1 and TLSv1.1 for coturn"

  5264. msgstr ""

  5265. 

  5266. #: ../../../CHANGELOG.md:2906

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

  5268. msgstr ""

  5269. 

  5270. #: ../../../CHANGELOG.md:2908

  5271. msgid "If you need to support old clients, you can re-enable both (or whichever one you need) with the following configuration:"

  5272. msgstr ""

  5273. 

  5274. #: ../../../CHANGELOG.md:2916

  5275. msgid "2021-04-05"

  5276. msgstr ""

  5277. 

  5278. #: ../../../CHANGELOG.md:2918

  5279. msgid "Automated local Postgres backup support"

  5280. msgstr ""

  5281. 

  5282. #: ../../../CHANGELOG.md:2920

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

  5284. msgstr ""

  5285. 

  5286. #: ../../../CHANGELOG.md:2922

  5287. msgid "Additional details are available in [Setting up Postgres backup](docs/configuring-playbook-postgres-backup.md)."

  5288. msgstr ""

  5289. 

  5290. #: ../../../CHANGELOG.md:2925

  5291. msgid "2021-04-03"

  5292. msgstr ""

  5293. 

  5294. #: ../../../CHANGELOG.md:2927

  5295. msgid "Mjolnir moderation tool (bot) support"

  5296. msgstr ""

  5297. 

  5298. #: ../../../CHANGELOG.md:2929

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

  5300. msgstr ""

  5301. 

  5302. #: ../../../CHANGELOG.md:2931

  5303. msgid "Additional details are available in [Setting up Mjolnir](docs/configuring-playbook-bot-mjolnir.md)."

  5304. msgstr ""

  5305. 

  5306. #: ../../../CHANGELOG.md:2934

  5307. msgid "2021-03-20"

  5308. msgstr ""

  5309. 

  5310. #: ../../../CHANGELOG.md:2936

  5311. msgid "Sygnal push gateway support"

  5312. msgstr ""

  5313. 

  5314. #: ../../../CHANGELOG.md:2938

  5315. msgid "The playbook can now install the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you."

  5316. msgstr ""

  5317. 

  5318. #: ../../../CHANGELOG.md:2940

  5319. msgid "This is only useful to people who develop/build their own Matrix client applications."

  5320. msgstr ""

  5321. 

  5322. #: ../../../CHANGELOG.md:2942

  5323. msgid "Additional details are available in our [Setting up the Sygnal push gateway](docs/configuring-playbook-sygnal.md) docs."

  5324. msgstr ""

  5325. 

  5326. #: ../../../CHANGELOG.md:2945

  5327. msgid "2021-03-16"

  5328. msgstr ""

  5329. 

  5330. #: ../../../CHANGELOG.md:2947

  5331. msgid "Go-NEB support"

  5332. msgstr ""

  5333. 

  5334. #: ../../../CHANGELOG.md:2949

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

  5336. msgstr ""

  5337. 

  5338. #: ../../../CHANGELOG.md:2951

  5339. msgid "Additional details are available in [Setting up Go-NEB](docs/configuring-playbook-bot-go-neb.md)."

  5340. msgstr ""

  5341. 

  5342. #: ../../../CHANGELOG.md:2954

  5343. msgid "2021-02-19"

  5344. msgstr ""

  5345. 

  5346. #: ../../../CHANGELOG.md:2956

  5347. msgid "GroupMe bridging support via mx-puppet-groupme"

  5348. msgstr ""

  5349. 

  5350. #: ../../../CHANGELOG.md:2958

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

  5352. msgstr ""

  5353. 

  5354. #: ../../../CHANGELOG.md:2960

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

  5356. msgstr ""

  5357. 

  5358. #: ../../../CHANGELOG.md:2962

  5359. msgid "To get started, follow our [Setting up MX Puppet GroupMe](docs/configuring-playbook-bridge-mx-puppet-groupme.md) docs."

  5360. msgstr ""

  5361. 

  5362. #: ../../../CHANGELOG.md:2964

  5363. msgid "Mautrix Instagram bridging support"

  5364. msgstr ""

  5365. 

  5366. #: ../../../CHANGELOG.md:2966

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

  5368. msgstr ""

  5369. 

  5370. #: ../../../CHANGELOG.md:2968

  5371. msgid "Additional details are available in [Setting up Mautrix Instagram bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)."

  5372. msgstr ""

  5373. 

  5374. #: ../../../CHANGELOG.md:2970

  5375. msgid "Synapse workers support"

  5376. msgstr ""

  5377. 

  5378. #: ../../../CHANGELOG.md:2972

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

  5380. msgstr ""

  5381. 

  5382. #: ../../../CHANGELOG.md:2974

  5383. msgid "Having support for workers makes the playbook suitable for larger homeserver deployments."

  5384. msgstr ""

  5385. 

  5386. #: ../../../CHANGELOG.md:2976

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

  5388. msgstr ""

  5389. 

  5390. #: ../../../CHANGELOG.md:2978

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

  5392. msgstr ""

  5393. 

  5394. #: ../../../CHANGELOG.md:2980

  5395. msgid "To enable Synapse workers, follow our [Load balancing with workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) documentation."

  5396. msgstr ""

  5397. 

  5398. #: ../../../CHANGELOG.md:2983

  5399. msgid "2021-02-12"

  5400. msgstr ""

  5401. 

  5402. #: ../../../CHANGELOG.md:2985

  5403. msgid "(Potential Breaking Change) Monitoring/metrics support using Prometheus and Grafana"

  5404. msgstr ""

  5405. 

  5406. #: ../../../CHANGELOG.md:2987

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

  5408. msgstr ""

  5409. 

  5410. #: ../../../CHANGELOG.md:2989

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

  5412. msgstr ""

  5413. 

  5414. #: ../../../CHANGELOG.md:2991

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

  5416. msgstr ""

  5417. 

  5418. #: ../../../CHANGELOG.md:2994

  5419. msgid "2021-01-31"

  5420. msgstr ""

  5421. 

  5422. #: ../../../CHANGELOG.md:2996

  5423. msgid "Etherpad support"

  5424. msgstr ""

  5425. 

  5426. #: ../../../CHANGELOG.md:2998

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

  5428. msgstr ""

  5429. 

  5430. #: ../../../CHANGELOG.md:3000

  5431. msgid "To get it installed, follow [our Etherpad docs page](docs/configuring-playbook-etherpad.md)."

  5432. msgstr ""

  5433. 

  5434. #: ../../../CHANGELOG.md:3003

  5435. msgid "2021-01-22"

  5436. msgstr ""

  5437. 

  5438. #: ../../../CHANGELOG.md:3005

  5439. msgid "(Breaking Change) Postgres changes that require manual intervention"

  5440. msgstr ""

  5441. 

  5442. #: ../../../CHANGELOG.md:3007

  5443. msgid "We've made a lot of changes to our Postgres setup and some manual action is required (described below). Sorry about the hassle."

  5444. msgstr ""

  5445. 

  5446. #: ../../../CHANGELOG.md:3009

  5447. 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."

  5448. msgstr ""

  5449. 

  5450. #: ../../../CHANGELOG.md:3011

  5451. msgid "Why?"

  5452. msgstr ""

  5453. 

  5454. #: ../../../CHANGELOG.md:3013

  5455. 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:"

  5456. msgstr ""

  5457. 

  5458. #: ../../../CHANGELOG.md:3014

  5459. 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`)"

  5460. msgstr ""

  5461. 

  5462. #: ../../../CHANGELOG.md:3015

  5463. 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`)"

  5464. msgstr ""

  5465. 

  5466. #: ../../../CHANGELOG.md:3016

  5467. 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`)"

  5468. msgstr ""

  5469. 

  5470. #: ../../../CHANGELOG.md:3017

  5471. 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."

  5472. msgstr ""

  5473. 

  5474. #: ../../../CHANGELOG.md:3018

  5475. 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."

  5476. msgstr ""

  5477. 

  5478. #: ../../../CHANGELOG.md:3020

  5479. msgid "So, this is some **effort to improve security** and to **prepare for a brighter future of having more homeserver options** than just Synapse."

  5480. msgstr ""

  5481. 

  5482. #: ../../../CHANGELOG.md:3022

  5483. msgid "What has really changed?"

  5484. msgstr ""

  5485. 

  5486. #: ../../../CHANGELOG.md:3024

  5487. msgid "the default superuser Postgres username is now `matrix` (used to be `synapse`)"

  5488. msgstr ""

  5489. 

  5490. #: ../../../CHANGELOG.md:3025

  5491. msgid "the default Postgres database is now `matrix` (used to be `homeserver`)"

  5492. msgstr ""

  5493. 

  5494. #: ../../../CHANGELOG.md:3026

  5495. msgid "Synapse's database is now `synapse` (used to be `homeserver`). This is now just another \"additional database\" that the playbook manages for you"

  5496. msgstr ""

  5497. 

  5498. #: ../../../CHANGELOG.md:3027

  5499. msgid "Synapse's user called `synapse` is just a regular user that can only use the `synapse` database (not a superuser anymore)"

  5500. msgstr ""

  5501. 

  5502. #: ../../../CHANGELOG.md:3029

  5503. msgid "What do I do if I'm using the integrated Postgres server (default)?"

  5504. msgstr ""

  5505. 

  5506. #: ../../../CHANGELOG.md:3031

  5507. 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."

  5508. msgstr ""

  5509. 

  5510. #: ../../../CHANGELOG.md:3033

  5511. msgid "To migrate to the new setup, expect a few minutes of downtime, while you follow these steps:"

  5512. msgstr ""

  5513. 

  5514. #: ../../../CHANGELOG.md:3035

  5515. 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."

  5516. msgstr ""

  5517. 

  5518. #: ../../../CHANGELOG.md:3037

  5519. 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!"

  5520. msgstr ""

  5521. 

  5522. #: ../../../CHANGELOG.md:3039

  5523. msgid "Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` file, adding a line like this:"

  5524. msgstr ""

  5525. 

  5526. #: ../../../CHANGELOG.md:3044

  5527. #: ../../../CHANGELOG.md:3056

  5528. msgid "… where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2."

  5529. msgstr ""

  5530. 

  5531. #: ../../../CHANGELOG.md:3046

  5532. msgid "Stop all services: `ansible-playbook -i inventory/hosts setup.yml --tags=stop`"

  5533. msgstr ""

  5534. 

  5535. #: ../../../CHANGELOG.md:3047

  5536. msgid "Log in to the server via SSH. The next commands will be performed there."

  5537. msgstr ""

  5538. 

  5539. #: ../../../CHANGELOG.md:3048

  5540. msgid "Start the Postgres database server: `systemctl start matrix-postgres`"

  5541. msgstr ""

  5542. 

  5543. #: ../../../CHANGELOG.md:3049

  5544. msgid "Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`"

  5545. msgstr ""

  5546. 

  5547. #: ../../../CHANGELOG.md:3050

  5548. msgid "Execute the following query, while making sure to **change the password inside** (**don't forget the ending `;`**):"

  5549. msgstr ""

  5550. 

  5551. #: ../../../CHANGELOG.md:3058

  5552. msgid "Execute the following queries as you see them (no modifications necessary, so you can just **paste them all at once**):"

  5553. msgstr ""

  5554. 

  5555. #: ../../../CHANGELOG.md:3076

  5556. msgid "You may need to press *Enter* after pasting the lines above."

  5557. msgstr ""

  5558. 

  5559. #: ../../../CHANGELOG.md:3078

  5560. msgid "Re-run the playbook normally: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`"

  5561. msgstr ""

  5562. 

  5563. #: ../../../CHANGELOG.md:3080

  5564. msgid "What do I do if I'm using an external Postgres server?"

  5565. msgstr ""

  5566. 

  5567. #: ../../../CHANGELOG.md:3082

  5568. 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."

  5569. msgstr ""

  5570. 

  5571. #: ../../../CHANGELOG.md:3084

  5572. 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."

  5573. msgstr ""

  5574. 

  5575. #: ../../../CHANGELOG.md:3087

  5576. msgid "2021-01-20"

  5577. msgstr ""

  5578. 

  5579. #: ../../../CHANGELOG.md:3089

  5580. msgid "(Breaking Change) The mautrix-facebook bridge now requires a Postgres database"

  5581. msgstr ""

  5582. 

  5583. #: ../../../CHANGELOG.md:3091

  5584. 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."

  5585. msgstr ""

  5586. 

  5587. #: ../../../CHANGELOG.md:3093

  5588. 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."

  5589. msgstr ""

  5590. 

  5591. #: ../../../CHANGELOG.md:3095

  5592. 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."

  5593. msgstr ""

  5594. 

  5595. #: ../../../CHANGELOG.md:3097

  5596. msgid "Whether this change requires your intervention depends mostly on:"

  5597. msgstr ""

  5598. 

  5599. #: ../../../CHANGELOG.md:3098

  5600. 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)."

  5601. msgstr ""

  5602. 

  5603. #: ../../../CHANGELOG.md:3099

  5604. 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))."

  5605. msgstr ""

  5606. 

  5607. #: ../../../CHANGELOG.md:3101

  5608. 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."

  5609. msgstr ""

  5610. 

  5611. #: ../../../CHANGELOG.md:3103

  5612. msgid "Upgrade path for people NOT running an external Postgres server (default for the playbook)"

  5613. msgstr ""

  5614. 

  5615. #: ../../../CHANGELOG.md:3105

  5616. 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`) ."

  5617. msgstr ""

  5618. 

  5619. #: ../../../CHANGELOG.md:3107

  5620. 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."

  5621. msgstr ""

  5622. 

  5623. #: ../../../CHANGELOG.md:3109

  5624. msgid "Alternatively, [you can stay on SQLite for a little longer](#staying-on-sqlite-for-a-little-longer-temporary-solution)."

  5625. msgstr ""

  5626. 

  5627. #: ../../../CHANGELOG.md:3111

  5628. msgid "Upgrade path for people running an external Postgres server"

  5629. msgstr ""

  5630. 

  5631. #: ../../../CHANGELOG.md:3113

  5632. msgid "For people using the internal Postgres server (the default for the playbook):"

  5633. msgstr ""

  5634. 

  5635. #: ../../../CHANGELOG.md:3114

  5636. msgid "we automatically create an additional `matrix_mautrix_facebook` Postgres database and credentials to access it"

  5637. msgstr ""

  5638. 

  5639. #: ../../../CHANGELOG.md:3115

  5640. msgid "we automatically adjust the bridge's `matrix_mautrix_facebook_database_*` variables to point the bridge to that Postgres database"

  5641. msgstr ""

  5642. 

  5643. #: ../../../CHANGELOG.md:3116

  5644. msgid "we use [pgloader](https://pgloader.io/) to automatically import the existing SQLite data for the bridge into the `matrix_mautrix_facebook` Postgres database"

  5645. msgstr ""

  5646. 

  5647. #: ../../../CHANGELOG.md:3118

  5648. 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."

  5649. msgstr ""

  5650. 

  5651. #: ../../../CHANGELOG.md:3120

  5652. msgid "You have 3 ways to proceed:"

  5653. msgstr ""

  5654. 

  5655. #: ../../../CHANGELOG.md:3122

  5656. msgid "contribute to the playbook to make this possible (difficult)"

  5657. msgstr ""

  5658. 

  5659. #: ../../../CHANGELOG.md:3123

  5660. msgid "or, do the migration \"steps\" manually:"

  5661. msgstr ""

  5662. 

  5663. #: ../../../CHANGELOG.md:3124

  5664. msgid "stop the bridge (`systemctl stop matrix-mautrix-facebook`)"

  5665. msgstr ""

  5666. 

  5667. #: ../../../CHANGELOG.md:3125

  5668. msgid "create a new `matrix_mautrix_facebook` Postgres database for it"

  5669. msgstr ""

  5670. 

  5671. #: ../../../CHANGELOG.md:3126

  5672. msgid "run [pgloader](https://pgloader.io/) manually (we import this bridge's data using default settings and it works well)"

  5673. msgstr ""

  5674. 

  5675. #: ../../../CHANGELOG.md:3127

  5676. 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`"

  5677. msgstr ""

  5678. 

  5679. #: ../../../CHANGELOG.md:3128

  5680. msgid "switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: 'postgres'` in your `vars.yml` file)"

  5681. msgstr ""

  5682. 

  5683. #: ../../../CHANGELOG.md:3129

  5684. 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`)"

  5685. msgstr ""

  5686. 

  5687. #: ../../../CHANGELOG.md:3130

  5688. msgid "send a `login` message to the Facebook bridge bot again"

  5689. msgstr ""

  5690. 

  5691. #: ../../../CHANGELOG.md:3131

  5692. msgid "or, [stay on SQLite for a little longer (temporary solution)](#staying-on-sqlite-for-a-little-longer-temporary-solution)"

  5693. msgstr ""

  5694. 

  5695. #: ../../../CHANGELOG.md:3133

  5696. msgid "Staying on SQLite for a little longer (temporary solution)"

  5697. msgstr ""

  5698. 

  5699. #: ../../../CHANGELOG.md:3135

  5700. msgid "To keep using this bridge with SQLite for a little longer (**not recommended**), use the following configuration in your `vars.yml` file:"

  5701. msgstr ""

  5702. 

  5703. #: ../../../CHANGELOG.md:3145

  5704. 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."

  5705. msgstr ""

  5706. 

  5707. #: ../../../CHANGELOG.md:3148

  5708. msgid "2021-01-17"

  5709. msgstr ""

  5710. 

  5711. #: ../../../CHANGELOG.md:3150

  5712. msgid "matrix-corporal goes 2.0"

  5713. msgstr ""

  5714. 

  5715. #: ../../../CHANGELOG.md:3152

  5716. 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."

  5717. msgstr ""

  5718. 

  5719. #: ../../../CHANGELOG.md:3154

  5720. msgid "No manual intervention is required in the common case."

  5721. msgstr ""

  5722. 

  5723. #: ../../../CHANGELOG.md:3156

  5724. 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)."

  5725. msgstr ""

  5726. 

  5727. #: ../../../CHANGELOG.md:3159

  5728. msgid "2021-01-14"

  5729. msgstr ""

  5730. 

  5731. #: ../../../CHANGELOG.md:3161

  5732. msgid "Moving from cronjobs to systemd timers"

  5733. msgstr ""

  5734. 

  5735. #: ../../../CHANGELOG.md:3163

  5736. 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."

  5737. msgstr ""

  5738. 

  5739. #: ../../../CHANGELOG.md:3165

  5740. msgid "The largest benefit of this is that we no longer require you to install a cron daemon, thus simplifying our install procedure."

  5741. msgstr ""

  5742. 

  5743. #: ../../../CHANGELOG.md:3167

  5744. msgid "The playbook will migrate you from cronjobs to systemd timers automatically. This is just a heads up."

  5745. msgstr ""

  5746. 

  5747. #: ../../../CHANGELOG.md:3170

  5748. msgid "2021-01-08"

  5749. msgstr ""

  5750. 

  5751. #: ../../../CHANGELOG.md:3172

  5752. msgid "(Breaking Change) New SSL configuration"

  5753. msgstr ""

  5754. 

  5755. #: ../../../CHANGELOG.md:3174

  5756. msgid "SSL configuration (protocols, ciphers) can now be more easily controlled thanks to us making use of configuration presets."

  5757. msgstr ""

  5758. 

  5759. #: ../../../CHANGELOG.md:3176

  5760. msgid "We define a few presets (old, intermediate, modern), following the [Mozilla SSL Configuration Generator](https://ssl-config.mozilla.org/#server=nginx)."

  5761. msgstr ""

  5762. 

  5763. #: ../../../CHANGELOG.md:3178

  5764. msgid "A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is used (defaults to `\"intermediate\"`)."

  5765. msgstr ""

  5766. 

  5767. #: ../../../CHANGELOG.md:3180

  5768. 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)."

  5769. msgstr ""

  5770. 

  5771. #: ../../../CHANGELOG.md:3182

  5772. msgid "To revert to the old behaviour, set the following variables:"

  5773. msgstr ""

  5774. 

  5775. #: ../../../CHANGELOG.md:3189

  5776. 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."

  5777. msgstr ""

  5778. 

  5779. #: ../../../CHANGELOG.md:3192

  5780. msgid "2021-01-03"

  5781. msgstr ""

  5782. 

  5783. #: ../../../CHANGELOG.md:3194

  5784. msgid "Signal bridging support via mautrix-signal"

  5785. msgstr ""

  5786. 

  5787. #: ../../../CHANGELOG.md:3196

  5788. 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."

  5789. msgstr ""

  5790. 

  5791. #: ../../../CHANGELOG.md:3198

  5792. 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)."

  5793. msgstr ""

  5794. 

  5795. #: ../../../CHANGELOG.md:3201

  5796. msgid "2020-12-23"

  5797. msgstr ""

  5798. 

  5799. #: ../../../CHANGELOG.md:3203

  5800. msgid "The big move to all-on-Postgres (potentially dangerous)"

  5801. msgstr ""

  5802. 

  5803. #: ../../../CHANGELOG.md:3205

  5804. 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."

  5805. msgstr ""

  5806. 

  5807. #: ../../../CHANGELOG.md:3207

  5808. 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)."

  5809. msgstr ""

  5810. 

  5811. #: ../../../CHANGELOG.md:3209

  5812. 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!"

  5813. msgstr ""

  5814. 

  5815. #: ../../../CHANGELOG.md:3211

  5816. msgid "Moving all services to Postgres brings a few **benefits** to us:"

  5817. msgstr ""

  5818. 

  5819. #: ../../../CHANGELOG.md:3213

  5820. msgid "**improved performance**"

  5821. msgstr ""

  5822. 

  5823. #: ../../../CHANGELOG.md:3214

  5824. msgid "**improved compatibility**. Most bridges are deprecating SQLite/nedb support or offer less features when not on Postgres."

  5825. msgstr ""

  5826. 

  5827. #: ../../../CHANGELOG.md:3215

  5828. 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."

  5829. msgstr ""

  5830. 

  5831. #: ../../../CHANGELOG.md:3216

  5832. 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."

  5833. msgstr ""

  5834. 

  5835. #: ../../../CHANGELOG.md:3218

  5836. msgid "Key takeway"

  5837. msgstr ""

  5838. 

  5839. #: ../../../CHANGELOG.md:3220

  5840. 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)"

  5841. msgstr ""

  5842. 

  5843. #: ../../../CHANGELOG.md:3222

  5844. 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)."

  5845. msgstr ""

  5846. 

  5847. #: ../../../CHANGELOG.md:3224

  5848. msgid "Opting-out of the Postgres migration"

  5849. msgstr ""

  5850. 

  5851. #: ../../../CHANGELOG.md:3226

  5852. 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."

  5853. msgstr ""

  5854. 

  5855. #: ../../../CHANGELOG.md:3228

  5856. 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`)."

  5857. msgstr ""

  5858. 

  5859. #: ../../../CHANGELOG.md:3230

  5860. msgid "Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them."

  5861. msgstr ""

  5862. 

  5863. #: ../../../CHANGELOG.md:3232

  5864. msgid "Going back to SQLite/nedb if things went wrong"

  5865. msgstr ""

  5866. 

  5867. #: ../../../CHANGELOG.md:3234

  5868. 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:"

  5869. msgstr ""

  5870. 

  5871. #: ../../../CHANGELOG.md:3236

  5872. msgid "stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"

  5873. msgstr ""

  5874. 

  5875. #: ../../../CHANGELOG.md:3237

  5876. 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`"

  5877. msgstr ""

  5878. 

  5879. #: ../../../CHANGELOG.md:3238

  5880. 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."

  5881. msgstr ""

  5882. 

  5883. #: ../../../CHANGELOG.md:3239

  5884. msgid "re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`)"

  5885. msgstr ""

  5886. 

  5887. #: ../../../CHANGELOG.md:3240

  5888. msgid "[get in touch](README.md#support) with us"

  5889. msgstr ""

  5890. 

  5891. #: ../../../CHANGELOG.md:3242

  5892. msgid "2020-12-11"

  5893. msgstr ""

  5894. 

  5895. #: ../../../CHANGELOG.md:3244

  5896. msgid "synapse-janitor support removed"

  5897. msgstr ""

  5898. 

  5899. #: ../../../CHANGELOG.md:3246

  5900. 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."

  5901. msgstr ""

  5902. 

  5903. #: ../../../CHANGELOG.md:3248

  5904. 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."

  5905. msgstr ""

  5906. 

  5907. #: ../../../CHANGELOG.md:3250

  5908. msgid "Docker 20.10 is here"

  5909. msgstr ""

  5910. 

  5911. #: ../../../CHANGELOG.md:3252

  5912. msgid "(No need to do anything special in relation to this. Just something to keep in mind)"

  5913. msgstr ""

  5914. 

  5915. #: ../../../CHANGELOG.md:3254

  5916. msgid "Docker 20.10 got released recently and your server will likely get it the next time you update."

  5917. msgstr ""

  5918. 

  5919. #: ../../../CHANGELOG.md:3256

  5920. 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."

  5921. msgstr ""

  5922. 

  5923. #: ../../../CHANGELOG.md:3259

  5924. msgid "2020-12-08"

  5925. msgstr ""

  5926. 

  5927. #: ../../../CHANGELOG.md:3261

  5928. msgid "openid APIs exposed by default on the federation port when federation disabled"

  5929. msgstr ""

  5930. 

  5931. #: ../../../CHANGELOG.md:3263

  5932. msgid "We've changed some defaults. People running with our default configuration (federation enabled), are not affected at all."

  5933. msgstr ""

  5934. 

  5935. #: ../../../CHANGELOG.md:3265

  5936. msgid "If you are running an unfederated server (`matrix_synapse_federation_enabled: false`), this may be of interest to you."

  5937. msgstr ""

  5938. 

  5939. #: ../../../CHANGELOG.md:3267

  5940. 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`."

  5941. msgstr ""

  5942. 

  5943. #: ../../../CHANGELOG.md:3270

  5944. msgid "2020-11-27"

  5945. msgstr ""

  5946. 

  5947. #: ../../../CHANGELOG.md:3272

  5948. msgid "Recent Jitsi updates may require configuration changes"

  5949. msgstr ""

  5950. 

  5951. #: ../../../CHANGELOG.md:3274

  5952. 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."

  5953. msgstr ""

  5954. 

  5955. #: ../../../CHANGELOG.md:3276

  5956. msgid "**If you use our default Jitsi settings, you won't have to do anything.**"

  5957. msgstr ""

  5958. 

  5959. #: ../../../CHANGELOG.md:3278

  5960. 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."

  5961. msgstr ""

  5962. 

  5963. #: ../../../CHANGELOG.md:3280

  5964. 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."

  5965. msgstr ""

  5966. 

  5967. #: ../../../CHANGELOG.md:3282

  5968. 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."

  5969. msgstr ""

  5970. 

  5971. #: ../../../CHANGELOG.md:3285

  5972. msgid "2020-11-23"

  5973. msgstr ""

  5974. 

  5975. #: ../../../CHANGELOG.md:3287

  5976. #: ../../../CHANGELOG.md:3295

  5977. msgid "Breaking change matrix-sms-bridge"

  5978. msgstr ""

  5979. 

  5980. #: ../../../CHANGELOG.md:3289

  5981. 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."

  5982. msgstr ""

  5983. 

  5984. #: ../../../CHANGELOG.md:3291

  5985. 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."

  5986. msgstr ""

  5987. 

  5988. #: ../../../CHANGELOG.md:3293

  5989. msgid "2020-11-13"

  5990. msgstr ""

  5991. 

  5992. #: ../../../CHANGELOG.md:3297

  5993. 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."

  5994. msgstr ""

  5995. 

  5996. #: ../../../CHANGELOG.md:3299

  5997. msgid "Add the following to your `vars.yml` file: `matrix_sms_bridge_container_extra_arguments=['--env SPRING_PROFILES_ACTIVE=initialsync']`"

  5998. msgstr ""

  5999. 

  6000. #: ../../../CHANGELOG.md:3300

  6001. msgid "Login to your host shell and remove old systemd file from your host: `rm /etc/systemd/system/matrix-sms-bridge-database.service`"

  6002. msgstr ""

  6003. 

  6004. #: ../../../CHANGELOG.md:3301

  6005. msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-sms-bridge,start`"

  6006. msgstr ""

  6007. 

  6008. #: ../../../CHANGELOG.md:3302

  6009. msgid "Login to your host shell and check the logs with `journalctl -u matrix-sms-bridge` until the sync finished."

  6010. msgstr ""

  6011. 

  6012. #: ../../../CHANGELOG.md:3303

  6013. msgid "Remove the var from the first step."

  6014. msgstr ""

  6015. 

  6016. #: ../../../CHANGELOG.md:3304

  6017. msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`."

  6018. msgstr ""

  6019. 

  6020. #: ../../../CHANGELOG.md:3306

  6021. msgid "2020-11-10"

  6022. msgstr ""

  6023. 

  6024. #: ../../../CHANGELOG.md:3308

  6025. msgid "Dynamic DNS support"

  6026. msgstr ""

  6027. 

  6028. #: ../../../CHANGELOG.md:3310

  6029. msgid "Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook can now manage Dynamic DNS for you using [ddclient](https://ddclient.net/)."

  6030. msgstr ""

  6031. 

  6032. #: ../../../CHANGELOG.md:3312

  6033. msgid "To learn more, follow our [Dynamic DNS docs page](docs/configuring-playbook-dynamic-dns.md)."

  6034. msgstr ""

  6035. 

  6036. #: ../../../CHANGELOG.md:3315

  6037. msgid "2020-10-28"

  6038. msgstr ""

  6039. 

  6040. #: ../../../CHANGELOG.md:3317

  6041. msgid "(Compatibility Break) https://matrix.example.com/ now redirects to https://element.example.com/"

  6042. msgstr ""

  6043. 

  6044. #: ../../../CHANGELOG.md:3319

  6045. 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."

  6046. msgstr ""

  6047. 

  6048. #: ../../../CHANGELOG.md:3321

  6049. 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))."

  6050. msgstr ""

  6051. 

  6052. #: ../../../CHANGELOG.md:3323

  6053. 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."

  6054. msgstr ""

  6055. 

  6056. #: ../../../CHANGELOG.md:3325

  6057. 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: \"\"`)."

  6058. msgstr ""

  6059. 

  6060. #: ../../../CHANGELOG.md:3328

  6061. msgid "2020-10-26"

  6062. msgstr ""

  6063. 

  6064. #: ../../../CHANGELOG.md:3330

  6065. msgid "(Compatibility Break) /_synapse/admin is no longer publicly exposed by default"

  6066. msgstr ""

  6067. 

  6068. #: ../../../CHANGELOG.md:3332

  6069. 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."

  6070. msgstr ""

  6071. 

  6072. #: ../../../CHANGELOG.md:3334

  6073. 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."

  6074. msgstr ""

  6075. 

  6076. #: ../../../CHANGELOG.md:3336

  6077. 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`):"

  6078. msgstr ""

  6079. 

  6080. #: ../../../CHANGELOG.md:3343

  6081. msgid "2020-10-02"

  6082. msgstr ""

  6083. 

  6084. #: ../../../CHANGELOG.md:3345

  6085. msgid "Minimum Ansible version raised to v2.7.0"

  6086. msgstr ""

  6087. 

  6088. #: ../../../CHANGELOG.md:3347

  6089. 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."

  6090. msgstr ""

  6091. 

  6092. #: ../../../CHANGELOG.md:3349

  6093. 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)."

  6094. msgstr ""

  6095. 

  6096. #: ../../../CHANGELOG.md:3351

  6097. msgid "Our [Ansible docs page](docs/ansible.md) contains information on how to run a more up-to-date version of Ansible."

  6098. msgstr ""

  6099. 

  6100. #: ../../../CHANGELOG.md:3354

  6101. msgid "2020-10-01"

  6102. msgstr ""

  6103. 

  6104. #: ../../../CHANGELOG.md:3356

  6105. msgid "Postgres 13 support"

  6106. msgstr ""

  6107. 

  6108. #: ../../../CHANGELOG.md:3358

  6109. msgid "The playbook now installs [Postgres 13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) by default."

  6110. msgstr ""

  6111. 

  6112. #: ../../../CHANGELOG.md:3360

  6113. 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)."

  6114. msgstr ""

  6115. 

  6116. #: ../../../CHANGELOG.md:3362

  6117. msgid "2020-09-01"

  6118. msgstr ""

  6119. 

  6120. #: ../../../CHANGELOG.md:3364

  6121. msgid "matrix-registration support"

  6122. msgstr ""

  6123. 

  6124. #: ../../../CHANGELOG.md:3366

  6125. 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."

  6126. msgstr ""

  6127. 

  6128. #: ../../../CHANGELOG.md:3368

  6129. msgid "See our [Setting up matrix-registration](docs/configuring-playbook-matrix-registration.md) documentation page to get started."

  6130. msgstr ""

  6131. 

  6132. #: ../../../CHANGELOG.md:3371

  6133. msgid "2020-08-21"

  6134. msgstr ""

  6135. 

  6136. #: ../../../CHANGELOG.md:3373

  6137. msgid "rust-synapse-compress-state support"

  6138. msgstr ""

  6139. 

  6140. #: ../../../CHANGELOG.md:3375

  6141. 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."

  6142. msgstr ""

  6143. 

  6144. #: ../../../CHANGELOG.md:3377

  6145. 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."

  6146. msgstr ""

  6147. 

  6148. #: ../../../CHANGELOG.md:3380

  6149. msgid "2020-07-22"

  6150. msgstr ""

  6151. 

  6152. #: ../../../CHANGELOG.md:3382

  6153. msgid "Synapse Admin support"

  6154. msgstr ""

  6155. 

  6156. #: ../../../CHANGELOG.md:3384

  6157. msgid "The playbook can now help you set up [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin)."

  6158. msgstr ""

  6159. 

  6160. #: ../../../CHANGELOG.md:3386

  6161. msgid "See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-admin.md) documentation to get started."

  6162. msgstr ""

  6163. 

  6164. #: ../../../CHANGELOG.md:3389

  6165. msgid "2020-07-20"

  6166. msgstr ""

  6167. 

  6168. #: ../../../CHANGELOG.md:3391

  6169. msgid "matrix-reminder-bot support"

  6170. msgstr ""

  6171. 

  6172. #: ../../../CHANGELOG.md:3393

  6173. msgid "The playbook can now help you set up [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)."

  6174. msgstr ""

  6175. 

  6176. #: ../../../CHANGELOG.md:3395

  6177. msgid "See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-matrix-reminder-bot.md) documentation to get started."

  6178. msgstr ""

  6179. 

  6180. #: ../../../CHANGELOG.md:3398

  6181. msgid "2020-07-17"

  6182. msgstr ""

  6183. 

  6184. #: ../../../CHANGELOG.md:3400

  6185. msgid "(Compatibility Break) Riot is now Element"

  6186. msgstr ""

  6187. 

  6188. #: ../../../CHANGELOG.md:3402

  6189. msgid "As per the official announcement, [Riot has been rebraned to Element](https://element.io/blog/welcome-to-element/)."

  6190. msgstr ""

  6191. 

  6192. #: ../../../CHANGELOG.md:3404

  6193. msgid "The playbook follows suit. Existing installations have a few options for how to handle this."

  6194. msgstr ""

  6195. 

  6196. #: ../../../CHANGELOG.md:3406

  6197. msgid "See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md#migrating-to-element) documentation page for more details."

  6198. msgstr ""

  6199. 

  6200. #: ../../../CHANGELOG.md:3409

  6201. msgid "2020-07-03"

  6202. msgstr ""

  6203. 

  6204. #: ../../../CHANGELOG.md:3411

  6205. msgid "Steam bridging support via mx-puppet-steam"

  6206. msgstr ""

  6207. 

  6208. #: ../../../CHANGELOG.md:3413

  6209. msgid "Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the playbook now supports bridging to [Steam](https://steamapp.com/) via the [mx-puppet-steam](https://codeberg.org/icewind/mx-puppet-steam) bridge. See our [Setting up MX Puppet Steam bridging](docs/configuring-playbook-bridge-mx-puppet-steam.md) documentation page for getting started."

  6210. msgstr ""

  6211. 

  6212. #: ../../../CHANGELOG.md:3416

  6213. msgid "2020-07-01"

  6214. msgstr ""

  6215. 

  6216. #: ../../../CHANGELOG.md:3418

  6217. msgid "Discord bridging support via mx-puppet-discord"

  6218. msgstr ""

  6219. 

  6220. #: ../../../CHANGELOG.md:3420

  6221. 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."

  6222. msgstr ""

  6223. 

  6224. #: ../../../CHANGELOG.md:3422

  6225. 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)."

  6226. msgstr ""

  6227. 

  6228. #: ../../../CHANGELOG.md:3425

  6229. msgid "2020-06-30"

  6230. msgstr ""

  6231. 

  6232. #: ../../../CHANGELOG.md:3427

  6233. msgid "Instagram and Twitter bridging support"

  6234. msgstr ""

  6235. 

  6236. #: ../../../CHANGELOG.md:3429

  6237. 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."

  6238. msgstr ""

  6239. 

  6240. #: ../../../CHANGELOG.md:3431

  6241. 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."

  6242. msgstr ""

  6243. 

  6244. #: ../../../CHANGELOG.md:3434

  6245. msgid "2020-06-28"

  6246. msgstr ""

  6247. 

  6248. #: ../../../CHANGELOG.md:3436

  6249. msgid "(Post Mortem / fixed Security Issue) Re-enabling User Directory search powered by the ma1sd Identity Server"

  6250. msgstr ""

  6251. 

  6252. #: ../../../CHANGELOG.md:3438

  6253. #: ../../../CHANGELOG.md:3467

  6254. msgid "User Directory search requests used to go to the ma1sd identity server by default, which queried its own stores and the Synapse database."

  6255. msgstr ""

  6256. 

  6257. #: ../../../CHANGELOG.md:3440

  6258. 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."

  6259. msgstr ""

  6260. 

  6261. #: ../../../CHANGELOG.md:3442

  6262. 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`"

  6263. msgstr ""

  6264. 

  6265. #: ../../../CHANGELOG.md:3444

  6266. msgid "As always, re-running the playbook is enough to get the updated bits."

  6267. msgstr ""

  6268. 

  6269. #: ../../../CHANGELOG.md:3446

  6270. msgid "2020-06-11"

  6271. msgstr ""

  6272. 

  6273. #: ../../../CHANGELOG.md:3448

  6274. msgid "SMS bridging requires db reset"

  6275. msgstr ""

  6276. 

  6277. #: ../../../CHANGELOG.md:3450

  6278. msgid "The current version of [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) needs you to delete the database to work as expected. Just remove `/matrix/matrix-sms-bridge/database/*`. It also adds a new required var `matrix_sms_bridge_default_region`."

  6279. msgstr ""

  6280. 

  6281. #: ../../../CHANGELOG.md:3452

  6282. 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."

  6283. msgstr ""

  6284. 

  6285. #: ../../../CHANGELOG.md:3454

  6286. msgid "2020-06-05"

  6287. msgstr ""

  6288. 

  6289. #: ../../../CHANGELOG.md:3456

  6290. msgid "SMS bridging support"

  6291. msgstr ""

  6292. 

  6293. #: ../../../CHANGELOG.md:3458

  6294. 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)."

  6295. msgstr ""

  6296. 

  6297. #: ../../../CHANGELOG.md:3460

  6298. msgid "See our [Setting up Matrix SMS bridging](docs/configuring-playbook-bridge-matrix-bridge-sms.md) documentation page for getting started."

  6299. msgstr ""

  6300. 

  6301. #: ../../../CHANGELOG.md:3463

  6302. msgid "2020-05-19"

  6303. msgstr ""

  6304. 

  6305. #: ../../../CHANGELOG.md:3465

  6306. msgid "(Compatibility Break / Security Issue) Disabling User Directory search powered by the ma1sd Identity Server"

  6307. msgstr ""

  6308. 

  6309. #: ../../../CHANGELOG.md:3469

  6310. 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."

  6311. msgstr ""

  6312. 

  6313. #: ../../../CHANGELOG.md:3471

  6314. 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**."

  6315. msgstr ""

  6316. 

  6317. #: ../../../CHANGELOG.md:3473

  6318. 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 }}\"`"

  6319. msgstr ""

  6320. 

  6321. #: ../../../CHANGELOG.md:3476

  6322. msgid "2020-04-28"

  6323. msgstr ""

  6324. 

  6325. #: ../../../CHANGELOG.md:3478

  6326. msgid "Newer IRC bridge (with potential breaking change)"

  6327. msgstr ""

  6328. 

  6329. #: ../../../CHANGELOG.md:3480

  6330. msgid "This upgrades matrix-appservice-irc from 0.14.1 to 0.16.0. Upstream made a change to how you define manual mappings. If you added a `mapping` to your configuration, you will need to update it according to the [upstream instructions](https://github.com/matrix-org/matrix-appservice-irc/blob/master/CHANGELOG.md#0150-2020-02-05). If you did not include `mappings` in your configuration for IRC, no change is necessary. `mappings` is not part of the default configuration."

  6331. msgstr ""

  6332. 

  6333. #: ../../../CHANGELOG.md:3489

  6334. msgid "2020-04-23"

  6335. msgstr ""

  6336. 

  6337. #: ../../../CHANGELOG.md:3491

  6338. #: ../../../CHANGELOG.md:3722

  6339. msgid "Slack bridging support"

  6340. msgstr ""

  6341. 

  6342. #: ../../../CHANGELOG.md:3493

  6343. 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."

  6344. msgstr ""

  6345. 

  6346. #: ../../../CHANGELOG.md:3495

  6347. msgid "See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-bridge-mx-puppet-slack.md) documentation page for getting started."

  6348. msgstr ""

  6349. 

  6350. #: ../../../CHANGELOG.md:3498

  6351. msgid "2020-04-09"

  6352. msgstr ""

  6353. 

  6354. #: ../../../CHANGELOG.md:3500

  6355. msgid "Skype bridging support"

  6356. msgstr ""

  6357. 

  6358. #: ../../../CHANGELOG.md:3502

  6359. 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."

  6360. msgstr ""

  6361. 

  6362. #: ../../../CHANGELOG.md:3504

  6363. msgid "See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md) documentation page for getting started."

  6364. msgstr ""

  6365. 

  6366. #: ../../../CHANGELOG.md:3507

  6367. msgid "2020-04-05"

  6368. msgstr ""

  6369. 

  6370. #: ../../../CHANGELOG.md:3509

  6371. msgid "Private Jitsi support"

  6372. msgstr ""

  6373. 

  6374. #: ../../../CHANGELOG.md:3511

  6375. 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."

  6376. msgstr ""

  6377. 

  6378. #: ../../../CHANGELOG.md:3513

  6379. 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."

  6380. msgstr ""

  6381. 

  6382. #: ../../../CHANGELOG.md:3515

  6383. 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."

  6384. msgstr ""

  6385. 

  6386. #: ../../../CHANGELOG.md:3518

  6387. msgid "2020-04-03"

  6388. msgstr ""

  6389. 

  6390. #: ../../../CHANGELOG.md:3520

  6391. msgid "(Potential Backward Compatibility Break) ma1sd replaces mxisd"

  6392. msgstr ""

  6393. 

  6394. #: ../../../CHANGELOG.md:3522

  6395. 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."

  6396. msgstr ""

  6397. 

  6398. #: ../../../CHANGELOG.md:3524

  6399. 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."

  6400. msgstr ""

  6401. 

  6402. #: ../../../CHANGELOG.md:3526

  6403. 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."

  6404. msgstr ""

  6405. 

  6406. #: ../../../CHANGELOG.md:3529

  6407. msgid "2020-03-29"

  6408. msgstr ""

  6409. 

  6410. #: ../../../CHANGELOG.md:3531

  6411. msgid "Archlinux support"

  6412. msgstr ""

  6413. 

  6414. #: ../../../CHANGELOG.md:3533

  6415. msgid "Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts, the playbook now supports installing to an [Archlinux](https://www.archlinux.org/) server."

  6416. msgstr ""

  6417. 

  6418. #: ../../../CHANGELOG.md:3536

  6419. msgid "2020-03-24"

  6420. msgstr ""

  6421. 

  6422. #: ../../../CHANGELOG.md:3538

  6423. msgid "Jitsi support"

  6424. msgstr ""

  6425. 

  6426. #: ../../../CHANGELOG.md:3540

  6427. 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)."

  6428. msgstr ""

  6429. 

  6430. #: ../../../CHANGELOG.md:3542

  6431. msgid "See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to get started."

  6432. msgstr ""

  6433. 

  6434. #: ../../../CHANGELOG.md:3545

  6435. msgid "2020-03-15"

  6436. msgstr ""

  6437. 

  6438. #: ../../../CHANGELOG.md:3547

  6439. msgid "Raspberry Pi support"

  6440. msgstr ""

  6441. 

  6442. #: ../../../CHANGELOG.md:3549

  6443. 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."

  6444. msgstr ""

  6445. 

  6446. #: ../../../CHANGELOG.md:3551

  6447. 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."

  6448. msgstr ""

  6449. 

  6450. #: ../../../CHANGELOG.md:3554

  6451. msgid "2020-02-26"

  6452. msgstr ""

  6453. 

  6454. #: ../../../CHANGELOG.md:3556

  6455. msgid "Riot-web themes are here"

  6456. msgstr ""

  6457. 

  6458. #: ../../../CHANGELOG.md:3558

  6459. msgid "The playbook now makes it easy to install custom riot-web themes."

  6460. msgstr ""

  6461. 

  6462. #: ../../../CHANGELOG.md:3560

  6463. msgid "To learn more, take a look at our [riot-web documentation on Themes](docs/configuring-playbook-riot-web.md#themes)."

  6464. msgstr ""

  6465. 

  6466. #: ../../../CHANGELOG.md:3563

  6467. msgid "2020-02-24"

  6468. msgstr ""

  6469. 

  6470. #: ../../../CHANGELOG.md:3565

  6471. msgid "Customize the server name in Riot's login page"

  6472. msgstr ""

  6473. 

  6474. #: ../../../CHANGELOG.md:3567

  6475. msgid "You can now customize the server name string that Riot-web displays in its login page."

  6476. msgstr ""

  6477. 

  6478. #: ../../../CHANGELOG.md:3569

  6479. msgid "These playbook variables, with these default values, have been added:"

  6480. msgstr ""

  6481. 

  6482. #: ../../../CHANGELOG.md:3575

  6483. 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\"."

  6484. msgstr ""

  6485. 

  6486. #: ../../../CHANGELOG.md:3577

  6487. 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."

  6488. msgstr ""

  6489. 

  6490. #: ../../../CHANGELOG.md:3580

  6491. msgid "2020-01-30"

  6492. msgstr ""

  6493. 

  6494. #: ../../../CHANGELOG.md:3582

  6495. msgid "Disabling TLSv1.1"

  6496. msgstr ""

  6497. 

  6498. #: ../../../CHANGELOG.md:3584

  6499. msgid "To improve security, we've removed TLSv1.1 support from our default matrix-nginx-proxy configuration."

  6500. msgstr ""

  6501. 

  6502. #: ../../../CHANGELOG.md:3586

  6503. 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\"`"

  6504. msgstr ""

  6505. 

  6506. #: ../../../CHANGELOG.md:3589

  6507. msgid "2020-01-21"

  6508. msgstr ""

  6509. 

  6510. #: ../../../CHANGELOG.md:3591

  6511. msgid "Postgres collation changes (action required!)"

  6512. msgstr ""

  6513. 

  6514. #: ../../../CHANGELOG.md:3593

  6515. 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."

  6516. msgstr ""

  6517. 

  6518. #: ../../../CHANGELOG.md:3595

  6519. 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."

  6520. msgstr ""

  6521. 

  6522. #: ../../../CHANGELOG.md:3597

  6523. msgid "To avoid future problems, we recommend that you run the following command:"

  6524. msgstr ""

  6525. 

  6526. #: ../../../CHANGELOG.md:3603

  6527. 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."

  6528. msgstr ""

  6529. 

  6530. #: ../../../CHANGELOG.md:3606

  6531. msgid "2020-01-14"

  6532. msgstr ""

  6533. 

  6534. #: ../../../CHANGELOG.md:3608

  6535. msgid "Added support for Appservice Webhooks"

  6536. msgstr ""

  6537. 

  6538. #: ../../../CHANGELOG.md:3610

  6539. 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."

  6540. msgstr ""

  6541. 

  6542. #: ../../../CHANGELOG.md:3612

  6543. msgid "Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-playbook-bridge-appservice-webhooks.md)."

  6544. msgstr ""

  6545. 

  6546. #: ../../../CHANGELOG.md:3615

  6547. msgid "2020-01-12"

  6548. msgstr ""

  6549. 

  6550. #: ../../../CHANGELOG.md:3617

  6551. msgid "Added support for automatic Double Puppeting for all Mautrix bridges"

  6552. msgstr ""

  6553. 

  6554. #: ../../../CHANGELOG.md:3619

  6555. msgid "Double Puppeting can now be easily enabled for all Mautrix bridges supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)."

  6556. msgstr ""

  6557. 

  6558. #: ../../../CHANGELOG.md:3621

  6559. 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."

  6560. msgstr ""

  6561. 

  6562. #: ../../../CHANGELOG.md:3623

  6563. msgid "To get started, following the playbook's documentation for the bridge you'd like to configure."

  6564. msgstr ""

  6565. 

  6566. #: ../../../CHANGELOG.md:3626

  6567. msgid "2019-12-06"

  6568. msgstr ""

  6569. 

  6570. #: ../../../CHANGELOG.md:3628

  6571. msgid "Added support for an alternative method for using another webserver"

  6572. msgstr ""

  6573. 

  6574. #: ../../../CHANGELOG.md:3630

  6575. 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)."

  6576. msgstr ""

  6577. 

  6578. #: ../../../CHANGELOG.md:3632

  6579. 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))."

  6580. msgstr ""

  6581. 

  6582. #: ../../../CHANGELOG.md:3634

  6583. 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)."

  6584. msgstr ""

  6585. 

  6586. #: ../../../CHANGELOG.md:3637

  6587. msgid "2019-11-10"

  6588. msgstr ""

  6589. 

  6590. #: ../../../CHANGELOG.md:3639

  6591. msgid "Tightened security around room directory publishing"

  6592. msgstr ""

  6593. 

  6594. #: ../../../CHANGELOG.md:3641

  6595. 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."

  6596. msgstr ""

  6597. 

  6598. #: ../../../CHANGELOG.md:3643

  6599. 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**."

  6600. msgstr ""

  6601. 

  6602. #: ../../../CHANGELOG.md:3645

  6603. msgid "As with anything else, these new defaults can be overridden by changing the `matrix_synapse_allow_public_rooms_without_auth` and `matrix_synapse_allow_public_rooms_over_federation` variables, respectively."

  6604. msgstr ""

  6605. 

  6606. #: ../../../CHANGELOG.md:3648

  6607. msgid "2019-10-05"

  6608. msgstr ""

  6609. 

  6610. #: ../../../CHANGELOG.md:3650

  6611. msgid "Improved Postgres upgrading/importing"

  6612. msgstr ""

  6613. 

  6614. #: ../../../CHANGELOG.md:3652

  6615. 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."

  6616. msgstr ""

  6617. 

  6618. #: ../../../CHANGELOG.md:3654

  6619. 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."

  6620. msgstr ""

  6621. 

  6622. #: ../../../CHANGELOG.md:3656

  6623. 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."

  6624. msgstr ""

  6625. 

  6626. #: ../../../CHANGELOG.md:3658

  6627. msgid "Additionally, Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) now uses gzipped dump files by default, to minimize disk space usage."

  6628. msgstr ""

  6629. 

  6630. #: ../../../CHANGELOG.md:3661

  6631. msgid "2019-10-04"

  6632. msgstr ""

  6633. 

  6634. #: ../../../CHANGELOG.md:3663

  6635. msgid "Postgres 12 support"

  6636. msgstr ""

  6637. 

  6638. #: ../../../CHANGELOG.md:3665

  6639. msgid "The playbook now installs [Postgres 12](https://www.postgresql.org/about/news/1976/) by default."

  6640. msgstr ""

  6641. 

  6642. #: ../../../CHANGELOG.md:3667

  6643. 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)."

  6644. msgstr ""

  6645. 

  6646. #: ../../../CHANGELOG.md:3670

  6647. msgid "2019-10-03"

  6648. msgstr ""

  6649. 

  6650. #: ../../../CHANGELOG.md:3672

  6651. msgid "Synapse 1.4.0"

  6652. msgstr ""

  6653. 

  6654. #: ../../../CHANGELOG.md:3674

  6655. 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."

  6656. msgstr ""

  6657. 

  6658. #: ../../../CHANGELOG.md:3676

  6659. 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: ~`)."

  6660. msgstr ""

  6661. 

  6662. #: ../../../CHANGELOG.md:3678

  6663. 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."

  6664. msgstr ""

  6665. 

  6666. #: ../../../CHANGELOG.md:3680

  6667. 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."

  6668. msgstr ""

  6669. 

  6670. #: ../../../CHANGELOG.md:3683

  6671. msgid "2019-09-09"

  6672. msgstr ""

  6673. 

  6674. #: ../../../CHANGELOG.md:3685

  6675. msgid "Synapse Simple Antispam support"

  6676. msgstr ""

  6677. 

  6678. #: ../../../CHANGELOG.md:3687

  6679. 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."

  6680. msgstr ""

  6681. 

  6682. #: ../../../CHANGELOG.md:3689

  6683. msgid "From now on, you can easily install and configure this spam checker module through the playbook."

  6684. msgstr ""

  6685. 

  6686. #: ../../../CHANGELOG.md:3691

  6687. msgid "Learn more in [Setting up Synapse Simple Antispam](docs/configuring-playbook-synapse-simple-antispam.md)."

  6688. msgstr ""

  6689. 

  6690. #: ../../../CHANGELOG.md:3694

  6691. msgid "2019-08-25"

  6692. msgstr ""

  6693. 

  6694. #: ../../../CHANGELOG.md:3696

  6695. msgid "Extensible Riot-web configuration"

  6696. msgstr ""

  6697. 

  6698. #: ../../../CHANGELOG.md:3698

  6699. msgid "Similarly to [Extensible Synapse configuration](#extensible-synapse-configuration) (below), Riot-web configuration is also extensible now."

  6700. msgstr ""

  6701. 

  6702. #: ../../../CHANGELOG.md:3700

  6703. 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."

  6704. msgstr ""

  6705. 

  6706. #: ../../../CHANGELOG.md:3702

  6707. 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."

  6708. msgstr ""

  6709. 

  6710. #: ../../../CHANGELOG.md:3704

  6711. msgid "Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-web.md)."

  6712. msgstr ""

  6713. 

  6714. #: ../../../CHANGELOG.md:3707

  6715. msgid "2019-08-22"

  6716. msgstr ""

  6717. 

  6718. #: ../../../CHANGELOG.md:3709

  6719. msgid "Extensible Synapse configuration"

  6720. msgstr ""

  6721. 

  6722. #: ../../../CHANGELOG.md:3711

  6723. 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."

  6724. msgstr ""

  6725. 

  6726. #: ../../../CHANGELOG.md:3713

  6727. 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."

  6728. msgstr ""

  6729. 

  6730. #: ../../../CHANGELOG.md:3715

  6731. 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."

  6732. msgstr ""

  6733. 

  6734. #: ../../../CHANGELOG.md:3717

  6735. msgid "Learn more here in [Configuring Synapse](docs/configuring-playbook-synapse.md)."

  6736. msgstr ""

  6737. 

  6738. #: ../../../CHANGELOG.md:3720

  6739. msgid "2019-08-21"

  6740. msgstr ""

  6741. 

  6742. #: ../../../CHANGELOG.md:3724

  6743. 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."

  6744. msgstr ""

  6745. 

  6746. #: ../../../CHANGELOG.md:3726

  6747. msgid "Additional details are available in [Setting up Appservice Slack bridging](docs/configuring-playbook-bridge-appservice-slack.md)."

  6748. msgstr ""

  6749. 

  6750. #: ../../../CHANGELOG.md:3728

  6751. msgid "Google Hangouts bridging support"

  6752. msgstr ""

  6753. 

  6754. #: ../../../CHANGELOG.md:3730

  6755. 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."

  6756. msgstr ""

  6757. 

  6758. #: ../../../CHANGELOG.md:3732

  6759. msgid "Additional details are available in [Setting up Mautrix Hangouts bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)."

  6760. msgstr ""

  6761. 

  6762. #: ../../../CHANGELOG.md:3735

  6763. msgid "2019-08-05"

  6764. msgstr ""

  6765. 

  6766. #: ../../../CHANGELOG.md:3737

  6767. msgid "Email2Matrix support"

  6768. msgstr ""

  6769. 

  6770. #: ../../../CHANGELOG.md:3739

  6771. msgid "Support for [Email2Matrix](https://github.com/devture/email2matrix) has been added."

  6772. msgstr ""

  6773. 

  6774. #: ../../../CHANGELOG.md:3741

  6775. msgid "It's an optional feature that you can enable via the playbook."

  6776. msgstr ""

  6777. 

  6778. #: ../../../CHANGELOG.md:3743

  6779. msgid "To learn more, see the [playbook's documentation on Email2Matrix](./docs/configuring-playbook-email2matrix.md)."

  6780. msgstr ""

  6781. 

  6782. #: ../../../CHANGELOG.md:3746

  6783. msgid "2019-08-03"

  6784. msgstr ""

  6785. 

  6786. #: ../../../CHANGELOG.md:3748

  6787. msgid "Synapse logging level has been reduced to WARNING"

  6788. msgstr ""

  6789. 

  6790. #: ../../../CHANGELOG.md:3750

  6791. 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`."

  6792. msgstr ""

  6793. 

  6794. #: ../../../CHANGELOG.md:3752

  6795. msgid "This greatly reduces the number of log messages that are being logged, leading to:"

  6796. msgstr ""

  6797. 

  6798. #: ../../../CHANGELOG.md:3754

  6799. msgid "much less disk space dedicated to Synapse and thus, logs kept for longer"

  6800. msgstr ""

  6801. 

  6802. #: ../../../CHANGELOG.md:3755

  6803. msgid "easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages, as they're not longer buried in thousands of non-important `INFO` messages"

  6804. msgstr ""

  6805. 

  6806. #: ../../../CHANGELOG.md:3757

  6807. 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)."

  6808. msgstr ""

  6809. 

  6810. #: ../../../CHANGELOG.md:3760

  6811. msgid "2019-07-08"

  6812. msgstr ""

  6813. 

  6814. #: ../../../CHANGELOG.md:3762

  6815. msgid "Synapse Maintenance docs and synapse-janitor support are available"

  6816. msgstr ""

  6817. 

  6818. #: ../../../CHANGELOG.md:3764

  6819. msgid "The playbook can now help you with Synapse's maintenance."

  6820. msgstr ""

  6821. 

  6822. #: ../../../CHANGELOG.md:3766

  6823. 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)."

  6824. msgstr ""

  6825. 

  6826. #: ../../../CHANGELOG.md:3768

  6827. 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."

  6828. msgstr ""

  6829. 

  6830. #: ../../../CHANGELOG.md:3770

  6831. msgid "(BC Break) Rename run control variables"

  6832. msgstr ""

  6833. 

  6834. #: ../../../CHANGELOG.md:3772

  6835. msgid "Some internal playbook control variables have been renamed."

  6836. msgstr ""

  6837. 

  6838. #: ../../../CHANGELOG.md:3774

  6839. 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."

  6840. msgstr ""

  6841. 

  6842. #: ../../../CHANGELOG.md:3776

  6843. msgid "The following variables have been renamed:"

  6844. msgstr ""

  6845. 

  6846. #: ../../../CHANGELOG.md:3778

  6847. msgid "from `run_import_postgres` to `run_postgres_import`"

  6848. msgstr ""

  6849. 

  6850. #: ../../../CHANGELOG.md:3779

  6851. msgid "from `run_import_sqlite_db` to `run_postgres_import_sqlite_db`"

  6852. msgstr ""

  6853. 

  6854. #: ../../../CHANGELOG.md:3780

  6855. msgid "from `run_upgrade_postgres` to `run_postgres_upgrade`"

  6856. msgstr ""

  6857. 

  6858. #: ../../../CHANGELOG.md:3781

  6859. msgid "from `run_import_media_store` to `run_synapse_import_media_store`"

  6860. msgstr ""

  6861. 

  6862. #: ../../../CHANGELOG.md:3782

  6863. msgid "from `run_register_user` to `run_synapse_register_user`"

  6864. msgstr ""

  6865. 

  6866. #: ../../../CHANGELOG.md:3783

  6867. msgid "from `run_update_user_password` to `run_synapse_update_user_password`"

  6868. msgstr ""

  6869. 

  6870. #: ../../../CHANGELOG.md:3786

  6871. msgid "2019-07-04"

  6872. msgstr ""

  6873. 

  6874. #: ../../../CHANGELOG.md:3788

  6875. msgid "Synapse no longer logs to text files"

  6876. msgstr ""

  6877. 

  6878. #: ../../../CHANGELOG.md:3790

  6879. 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*`)."

  6880. msgstr ""

  6881. 

  6882. #: ../../../CHANGELOG.md:3792

  6883. 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`"

  6884. msgstr ""

  6885. 

  6886. #: ../../../CHANGELOG.md:3794

  6887. msgid "Because of this, the following variables have become obsolete and were removed:"

  6888. msgstr ""

  6889. 

  6890. #: ../../../CHANGELOG.md:3796

  6891. msgid "`matrix_synapse_max_log_file_size_mb`"

  6892. msgstr ""

  6893. 

  6894. #: ../../../CHANGELOG.md:3797

  6895. msgid "`matrix_synapse_max_log_files_count`"

  6896. msgstr ""

  6897. 

  6898. #: ../../../CHANGELOG.md:3799

  6899. 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*`)."

  6900. msgstr ""

  6901. 

  6902. #: ../../../CHANGELOG.md:3801

  6903. 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`)."

  6904. msgstr ""

  6905. 

  6906. #: ../../../CHANGELOG.md:3804

  6907. msgid "2019-06-27"

  6908. msgstr ""

  6909. 

  6910. #: ../../../CHANGELOG.md:3806

  6911. msgid "(BC Break) Discord bridge configuration is now entirely managed by the playbook"

  6912. msgstr ""

  6913. 

  6914. #: ../../../CHANGELOG.md:3808

  6915. 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."

  6916. msgstr ""

  6917. 

  6918. #: ../../../CHANGELOG.md:3810

  6919. msgid "From now on, the playbook will keep both configuration files sync for you."

  6920. msgstr ""

  6921. 

  6922. #: ../../../CHANGELOG.md:3812

  6923. 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."

  6924. msgstr ""

  6925. 

  6926. #: ../../../CHANGELOG.md:3814

  6927. msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-discord/config`)."

  6928. msgstr ""

  6929. 

  6930. #: ../../../CHANGELOG.md:3816

  6931. 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`)."

  6932. msgstr ""

  6933. 

  6934. #: ../../../CHANGELOG.md:3818

  6935. 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."

  6936. msgstr ""

  6937. 

  6938. #: ../../../CHANGELOG.md:3820

  6939. 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`."

  6940. msgstr ""

  6941. 

  6942. #: ../../../CHANGELOG.md:3823

  6943. msgid "2019-06-24"

  6944. msgstr ""

  6945. 

  6946. #: ../../../CHANGELOG.md:3825

  6947. msgid "(BC Break) WhatsApp bridge configuration is now entirely managed by the playbook"

  6948. msgstr ""

  6949. 

  6950. #: ../../../CHANGELOG.md:3827

  6951. 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."

  6952. msgstr ""

  6953. 

  6954. #: ../../../CHANGELOG.md:3829

  6955. #: ../../../CHANGELOG.md:3846

  6956. #: ../../../CHANGELOG.md:3865

  6957. #: ../../../CHANGELOG.md:3904

  6958. msgid "From now on, the playbook will keep the configuration in sync for you."

  6959. msgstr ""

  6960. 

  6961. #: ../../../CHANGELOG.md:3831

  6962. 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."

  6963. msgstr ""

  6964. 

  6965. #: ../../../CHANGELOG.md:3833

  6966. 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."

  6967. msgstr ""

  6968. 

  6969. #: ../../../CHANGELOG.md:3835

  6970. 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`)."

  6971. msgstr ""

  6972. 

  6973. #: ../../../CHANGELOG.md:3837

  6974. msgid "We're now following the default configuration for the WhatsApp bridge."

  6975. msgstr ""

  6976. 

  6977. #: ../../../CHANGELOG.md:3840

  6978. msgid "2019-06-20"

  6979. msgstr ""

  6980. 

  6981. #: ../../../CHANGELOG.md:3842

  6982. msgid "(BC Break) IRC bridge configuration is now entirely managed by the playbook"

  6983. msgstr ""

  6984. 

  6985. #: ../../../CHANGELOG.md:3844

  6986. 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."

  6987. msgstr ""

  6988. 

  6989. #: ../../../CHANGELOG.md:3848

  6990. 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."

  6991. msgstr ""

  6992. 

  6993. #: ../../../CHANGELOG.md:3850

  6994. 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`)."

  6995. msgstr ""

  6996. 

  6997. #: ../../../CHANGELOG.md:3852

  6998. 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."

  6999. msgstr ""

  7000. 

  7001. #: ../../../CHANGELOG.md:3854

  7002. 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`."

  7003. msgstr ""

  7004. 

  7005. #: ../../../CHANGELOG.md:3856

  7006. 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`)."

  7007. msgstr ""

  7008. 

  7009. #: ../../../CHANGELOG.md:3859

  7010. msgid "2019-06-15"

  7011. msgstr ""

  7012. 

  7013. #: ../../../CHANGELOG.md:3861

  7014. msgid "(BC Break) Telegram bridge configuration is now entirely managed by the playbook"

  7015. msgstr ""

  7016. 

  7017. #: ../../../CHANGELOG.md:3863

  7018. 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."

  7019. msgstr ""

  7020. 

  7021. #: ../../../CHANGELOG.md:3867

  7022. 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."

  7023. msgstr ""

  7024. 

  7025. #: ../../../CHANGELOG.md:3869

  7026. 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."

  7027. msgstr ""

  7028. 

  7029. #: ../../../CHANGELOG.md:3871

  7030. 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`)."

  7031. msgstr ""

  7032. 

  7033. #: ../../../CHANGELOG.md:3873

  7034. msgid "Also, we're now following the default configuration for the Telegram bridge, so some default configuration values are different:"

  7035. msgstr ""

  7036. 

  7037. #: ../../../CHANGELOG.md:3875

  7038. 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"

  7039. msgstr ""

  7040. 

  7041. #: ../../../CHANGELOG.md:3876

  7042. 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."

  7043. msgstr ""

  7044. 

  7045. #: ../../../CHANGELOG.md:3877

  7046. msgid "`authless_portals` (used to be `false`, now `true`) — creating portals from the Telegram side is now possible"

  7047. msgstr ""

  7048. 

  7049. #: ../../../CHANGELOG.md:3878

  7050. msgid "`whitelist_group_admins` (used to be `false`, now `true`) — allows Telegram group admins to use the bot commands"

  7051. msgstr ""

  7052. 

  7053. #: ../../../CHANGELOG.md:3880

  7054. 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)."

  7055. msgstr ""

  7056. 

  7057. #: ../../../CHANGELOG.md:3883

  7058. msgid "2019-06-12"

  7059. msgstr ""

  7060. 

  7061. #: ../../../CHANGELOG.md:3885

  7062. msgid "Synapse v1.0"

  7063. msgstr ""

  7064. 

  7065. #: ../../../CHANGELOG.md:3887

  7066. 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)."

  7067. msgstr ""

  7068. 

  7069. #: ../../../CHANGELOG.md:3889

  7070. 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."

  7071. msgstr ""

  7072. 

  7073. #: ../../../CHANGELOG.md:3891

  7074. msgid "**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` DNS SRV records. The latter, **must not** be removed."

  7075. msgstr ""

  7076. 

  7077. #: ../../../CHANGELOG.md:3893

  7078. 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."

  7079. msgstr ""

  7080. 

  7081. #: ../../../CHANGELOG.md:3895

  7082. 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)."

  7083. msgstr ""

  7084. 

  7085. #: ../../../CHANGELOG.md:3898

  7086. msgid "2019-06-07"

  7087. msgstr ""

  7088. 

  7089. #: ../../../CHANGELOG.md:3900

  7090. msgid "(BC Break) Facebook bridge configuration is now entirely managed by the playbook"

  7091. msgstr ""

  7092. 

  7093. #: ../../../CHANGELOG.md:3902

  7094. 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."

  7095. msgstr ""

  7096. 

  7097. #: ../../../CHANGELOG.md:3906

  7098. 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."

  7099. msgstr ""

  7100. 

  7101. #: ../../../CHANGELOG.md:3908

  7102. 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."

  7103. msgstr ""

  7104. 

  7105. #: ../../../CHANGELOG.md:3910

  7106. 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`)."

  7107. msgstr ""

  7108. 

  7109. #: ../../../CHANGELOG.md:3913

  7110. msgid "2019-05-25"

  7111. msgstr ""

  7112. 

  7113. #: ../../../CHANGELOG.md:3915

  7114. msgid "Support for exposing container ports publicly (not just to the host)"

  7115. msgstr ""

  7116. 

  7117. #: ../../../CHANGELOG.md:3917

  7118. 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."

  7119. msgstr ""

  7120. 

  7121. #: ../../../CHANGELOG.md:3919

  7122. 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`."

  7123. msgstr ""

  7124. 

  7125. #: ../../../CHANGELOG.md:3921

  7126. msgid "All such variables have been superseded by a better (more flexible) way to do it."

  7127. msgstr ""

  7128. 

  7129. #: ../../../CHANGELOG.md:3923

  7130. msgid "**Most** people (including those not using `matrix-nginx-proxy`), **don't need** to bother with this."

  7131. msgstr ""

  7132. 

  7133. #: ../../../CHANGELOG.md:3925

  7134. msgid "Porting examples follow for people having more customized setups:"

  7135. msgstr ""

  7136. 

  7137. #: ../../../CHANGELOG.md:3927

  7138. msgid "**from** `matrix_synapse_container_expose_client_api_port: true` **to** `matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`"

  7139. msgstr ""

  7140. 

  7141. #: ../../../CHANGELOG.md:3929

  7142. 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'`"

  7143. msgstr ""

  7144. 

  7145. #: ../../../CHANGELOG.md:3931

  7146. msgid "**from** `matrix_synapse_container_expose_metrics_port: true` **to** `matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`"

  7147. msgstr ""

  7148. 

  7149. #: ../../../CHANGELOG.md:3933

  7150. msgid "**from** `matrix_riot_web_container_expose_port: true` **to** `matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`"

  7151. msgstr ""

  7152. 

  7153. #: ../../../CHANGELOG.md:3935

  7154. msgid "**from** `matrix_mxisd_container_expose_port: true` **to** `matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`"

  7155. msgstr ""

  7156. 

  7157. #: ../../../CHANGELOG.md:3937

  7158. msgid "**from** `matrix_dimension_container_expose_port: true` **to** `matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`"

  7159. msgstr ""

  7160. 

  7161. #: ../../../CHANGELOG.md:3939

  7162. 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'`"

  7163. msgstr ""

  7164. 

  7165. #: ../../../CHANGELOG.md:3941

  7166. 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'`"

  7167. msgstr ""

  7168. 

  7169. #: ../../../CHANGELOG.md:3943

  7170. 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'`"

  7171. msgstr ""

  7172. 

  7173. #: ../../../CHANGELOG.md:3945

  7174. msgid "As always, if you forget to remove usage of some outdated variable, the playbook will warn you."

  7175. msgstr ""

  7176. 

  7177. #: ../../../CHANGELOG.md:3948

  7178. msgid "2019-05-23"

  7179. msgstr ""

  7180. 

  7181. #: ../../../CHANGELOG.md:3950

  7182. msgid "(BC Break) Ansible 2.8 compatibility"

  7183. msgstr ""

  7184. 

  7185. #: ../../../CHANGELOG.md:3952

  7186. 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)."

  7187. msgstr ""

  7188. 

  7189. #: ../../../CHANGELOG.md:3954

  7190. msgid "A manual change is required to the `inventory/hosts` file, changing the group name from `matrix-servers` to `matrix_servers` (dash to underscore)."

  7191. msgstr ""

  7192. 

  7193. #: ../../../CHANGELOG.md:3956

  7194. msgid "To avoid doing it manually, run this:"

  7195. msgstr ""

  7196. 

  7197. #: ../../../CHANGELOG.md:3957

  7198. msgid "Linux: `sed -i 's/matrix-servers/matrix_servers/g' inventory/hosts`"

  7199. msgstr ""

  7200. 

  7201. #: ../../../CHANGELOG.md:3958

  7202. msgid "Mac: `sed -i '' 's/matrix-servers/matrix_servers/g' inventory/hosts`"

  7203. msgstr ""

  7204. 

  7205. #: ../../../CHANGELOG.md:3961

  7206. msgid "2019-05-21"

  7207. msgstr ""

  7208. 

  7209. #: ../../../CHANGELOG.md:3963

  7210. msgid "Synapse no longer required"

  7211. msgstr ""

  7212. 

  7213. #: ../../../CHANGELOG.md:3965

  7214. msgid "The playbook no longer insists on installing [Synapse](https://github.com/element-hq/synapse) via the `matrix-synapse` role."

  7215. msgstr ""

  7216. 

  7217. #: ../../../CHANGELOG.md:3967

  7218. 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`)."

  7219. msgstr ""

  7220. 

  7221. #: ../../../CHANGELOG.md:3969

  7222. 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."

  7223. msgstr ""

  7224. 

  7225. #: ../../../CHANGELOG.md:3971

  7226. msgid "Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers."

  7227. msgstr ""

  7228. 

  7229. #: ../../../CHANGELOG.md:3973

  7230. msgid "Bridges are now separate from the Synapse role"

  7231. msgstr ""

  7232. 

  7233. #: ../../../CHANGELOG.md:3975

  7234. msgid "Bridges are no longer part of the `matrix-synapse` role. Each bridge now lives in its own separate role (`roles/custom/matrix-bridge-*`)."

  7235. msgstr ""

  7236. 

  7237. #: ../../../CHANGELOG.md:3977

  7238. 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)."

  7239. msgstr ""

  7240. 

  7241. #: ../../../CHANGELOG.md:3979

  7242. msgid "Renaming inconsistently-named Synapse variables"

  7243. msgstr ""

  7244. 

  7245. #: ../../../CHANGELOG.md:3981

  7246. msgid "For better consistency, the following variables have been renamed:"

  7247. msgstr ""

  7248. 

  7249. #: ../../../CHANGELOG.md:3983

  7250. msgid "`matrix_enable_room_list_search` was renamed to `matrix_synapse_enable_room_list_search`"

  7251. msgstr ""

  7252. 

  7253. #: ../../../CHANGELOG.md:3984

  7254. msgid "`matrix_alias_creation_rules` was renamed to `matrix_synapse_alias_creation_rules`"

  7255. msgstr ""

  7256. 

  7257. #: ../../../CHANGELOG.md:3985

  7258. msgid "`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was renamed to `matrix_synapse_room_list_publication_rules`"

  7259. msgstr ""

  7260. 

  7261. #: ../../../CHANGELOG.md:3988

  7262. msgid "2019-05-09"

  7263. msgstr ""

  7264. 

  7265. #: ../../../CHANGELOG.md:3990

  7266. msgid "Besides a myriad of bug fixes and minor improvements, here are the more notable (bigger) features we can announce today."

  7267. msgstr ""

  7268. 

  7269. #: ../../../CHANGELOG.md:3992

  7270. msgid "Mautrix Facebook/Messenger bridging support"

  7271. msgstr ""

  7272. 

  7273. #: ../../../CHANGELOG.md:3994

  7274. 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)."

  7275. msgstr ""

  7276. 

  7277. #: ../../../CHANGELOG.md:3996

  7278. msgid "Additional details are available in [Setting up Mautrix Facebook bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)."

  7279. msgstr ""

  7280. 

  7281. #: ../../../CHANGELOG.md:3998

  7282. msgid "mxisd Registration feature integration"

  7283. msgstr ""

  7284. 

  7285. #: ../../../CHANGELOG.md:4000

  7286. 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."

  7287. msgstr ""

  7288. 

  7289. #: ../../../CHANGELOG.md:4002

  7290. msgid "Learn more in [mxisd-controlled Registration](docs/configuring-playbook-mxisd.md#mxisd-controlled-registration)."

  7291. msgstr ""

  7292. 

  7293. #: ../../../CHANGELOG.md:4005

  7294. msgid "2019-04-16"

  7295. msgstr ""

  7296. 

  7297. #: ../../../CHANGELOG.md:4007

  7298. msgid "Caddy webserver examples"

  7299. msgstr ""

  7300. 

  7301. #: ../../../CHANGELOG.md:4009

  7302. 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"

  7303. msgstr ""

  7304. 

  7305. #: ../../../CHANGELOG.md:4011

  7306. msgid "2019-04-10"

  7307. msgstr ""

  7308. 

  7309. #: ../../../CHANGELOG.md:4013

  7310. msgid "Goofys support for other S3-compatible object stores"

  7311. msgstr ""

  7312. 

  7313. #: ../../../CHANGELOG.md:4015

  7314. 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),"

  7315. msgstr ""

  7316. 

  7317. #: ../../../CHANGELOG.md:4018

  7318. msgid "2019-04-03"

  7319. msgstr ""

  7320. 

  7321. #: ../../../CHANGELOG.md:4020

  7322. msgid "Ansible >= 2.5 is required"

  7323. msgstr ""

  7324. 

  7325. #: ../../../CHANGELOG.md:4022

  7326. 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)."

  7327. msgstr ""

  7328. 

  7329. #: ../../../CHANGELOG.md:4024

  7330. 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))."

  7331. msgstr ""

  7332. 

  7333. #: ../../../CHANGELOG.md:4027

  7334. msgid "2019-03-19"

  7335. msgstr ""

  7336. 

  7337. #: ../../../CHANGELOG.md:4029

  7338. msgid "TLS support for coturn"

  7339. msgstr ""

  7340. 

  7341. #: ../../../CHANGELOG.md:4031

  7342. 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."

  7343. msgstr ""

  7344. 

  7345. #: ../../../CHANGELOG.md:4033

  7346. 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:"

  7347. msgstr ""

  7348. 

  7349. #: ../../../CHANGELOG.md:4039

  7350. 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)."

  7351. msgstr ""

  7352. 

  7353. #: ../../../CHANGELOG.md:4041

  7354. msgid "People who build their own custom playbook from our roles should be aware that:"

  7355. msgstr ""

  7356. 

  7357. #: ../../../CHANGELOG.md:4043

  7358. 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)."

  7359. msgstr ""

  7360. 

  7361. #: ../../../CHANGELOG.md:4045

  7362. 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)."

  7363. msgstr ""

  7364. 

  7365. #: ../../../CHANGELOG.md:4048

  7366. msgid "2019-03-12"

  7367. msgstr ""

  7368. 

  7369. #: ../../../CHANGELOG.md:4050

  7370. msgid "matrix-nginx-proxy support for serving the base domain"

  7371. msgstr ""

  7372. 

  7373. #: ../../../CHANGELOG.md:4052

  7374. 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."

  7375. msgstr ""

  7376. 

  7377. #: ../../../CHANGELOG.md:4054

  7378. 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."

  7379. msgstr ""

  7380. 

  7381. #: ../../../CHANGELOG.md:4056

  7382. msgid "(BC break) matrix-nginx-proxy data variable renamed"

  7383. msgstr ""

  7384. 

  7385. #: ../../../CHANGELOG.md:4058

  7386. msgid "`matrix_nginx_proxy_data_path` was renamed to `matrix_nginx_proxy_base_path`."

  7387. msgstr ""

  7388. 

  7389. #: ../../../CHANGELOG.md:4060

  7390. 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)."

  7391. msgstr ""

  7392. 

  7393. #: ../../../CHANGELOG.md:4063

  7394. msgid "2019-03-10"

  7395. msgstr ""

  7396. 

  7397. #: ../../../CHANGELOG.md:4065

  7398. msgid "Dimension integration manager support"

  7399. msgstr ""

  7400. 

  7401. #: ../../../CHANGELOG.md:4067

  7402. 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."

  7403. msgstr ""

  7404. 

  7405. #: ../../../CHANGELOG.md:4070

  7406. msgid "2019-03-07"

  7407. msgstr ""

  7408. 

  7409. #: ../../../CHANGELOG.md:4072

  7410. msgid "Ability to customize mxisd's email templates"

  7411. msgstr ""

  7412. 

  7413. #: ../../../CHANGELOG.md:4074

  7414. 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."

  7415. msgstr ""

  7416. 

  7417. #: ../../../CHANGELOG.md:4077

  7418. msgid "2019-03-05"

  7419. msgstr ""

  7420. 

  7421. #: ../../../CHANGELOG.md:4079

  7422. msgid "Discord bridging support"

  7423. msgstr ""

  7424. 

  7425. #: ../../../CHANGELOG.md:4081

  7426. 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."

  7427. msgstr ""

  7428. 

  7429. #: ../../../CHANGELOG.md:4084

  7430. msgid "2019-02-19"

  7431. msgstr ""

  7432. 

  7433. #: ../../../CHANGELOG.md:4086

  7434. msgid "Renaming variables"

  7435. msgstr ""

  7436. 

  7437. #: ../../../CHANGELOG.md:4088

  7438. #: ../../../CHANGELOG.md:4405

  7439. #: ../../../CHANGELOG.md:4490

  7440. #: ../../../CHANGELOG.md:4610

  7441. msgid "The following playbook variables were renamed:"

  7442. msgstr ""

  7443. 

  7444. #: ../../../CHANGELOG.md:4090

  7445. msgid "from `host_specific_hostname_identity` to `matrix_domain`"

  7446. msgstr ""

  7447. 

  7448. #: ../../../CHANGELOG.md:4091

  7449. msgid "from `hostname_identity` to `matrix_domain`"

  7450. msgstr ""

  7451. 

  7452. #: ../../../CHANGELOG.md:4092

  7453. msgid "from `hostname_matrix` to `matrix_server_fqn_matrix`"

  7454. msgstr ""

  7455. 

  7456. #: ../../../CHANGELOG.md:4093

  7457. msgid "from `hostname_riot` to `matrix_server_fqn_riot`"

  7458. msgstr ""

  7459. 

  7460. #: ../../../CHANGELOG.md:4094

  7461. msgid "from `host_specific_matrix_ssl_lets_encrypt_support_email` to `matrix_ssl_lets_encrypt_support_email`"

  7462. msgstr ""

  7463. 

  7464. #: ../../../CHANGELOG.md:4096

  7465. msgid "Doing that, we've simplified things, made names less confusing (hopefully) and moved all variable names under the `matrix_` prefix."

  7466. msgstr ""

  7467. 

  7468. #: ../../../CHANGELOG.md:4099

  7469. msgid "2019-02-16"

  7470. msgstr ""

  7471. 

  7472. #: ../../../CHANGELOG.md:4101

  7473. msgid "Riot v1.0.1 support"

  7474. msgstr ""

  7475. 

  7476. #: ../../../CHANGELOG.md:4103

  7477. msgid "You can now use the brand new and redesigned Riot."

  7478. msgstr ""

  7479. 

  7480. #: ../../../CHANGELOG.md:4105

  7481. msgid "The new version no longer has a homepage by default, so we've also removed the custom homepage that we've been installing."

  7482. msgstr ""

  7483. 

  7484. #: ../../../CHANGELOG.md:4107

  7485. 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)."

  7486. msgstr ""

  7487. 

  7488. #: ../../../CHANGELOG.md:4110

  7489. msgid "2019-02-14"

  7490. msgstr ""

  7491. 

  7492. #: ../../../CHANGELOG.md:4112

  7493. msgid "Synapse v0.99.1"

  7494. msgstr ""

  7495. 

  7496. #: ../../../CHANGELOG.md:4114

  7497. 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."

  7498. msgstr ""

  7499. 

  7500. #: ../../../CHANGELOG.md:4116

  7501. 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."

  7502. msgstr ""

  7503. 

  7504. #: ../../../CHANGELOG.md:4119

  7505. msgid "2019-02-06"

  7506. msgstr ""

  7507. 

  7508. #: ../../../CHANGELOG.md:4121

  7509. msgid "Synapse v0.99 support and preparation for Synapse v1.0"

  7510. msgstr ""

  7511. 

  7512. #: ../../../CHANGELOG.md:4123

  7513. 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."

  7514. msgstr ""

  7515. 

  7516. #: ../../../CHANGELOG.md:4125

  7517. 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))."

  7518. msgstr ""

  7519. 

  7520. #: ../../../CHANGELOG.md:4127

  7521. 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)."

  7522. msgstr ""

  7523. 

  7524. #: ../../../CHANGELOG.md:4129

  7525. 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:"

  7526. msgstr ""

  7527. 

  7528. #: ../../../CHANGELOG.md:4131

  7529. msgid "(recommended) set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), unless you are affected by the [Downsides of well-known-based Server Delegation](docs/howto-server-delegation.md#downsides-of-well-known-based-server-delegation). If you had previously set up the well-known `client` file, depending on how you've done it, it may be that there is nothing new required of you (besides [upgrading](docs/maintenance-upgrading-services.md)). After upgrading, you can [run a self-check](docs/maintenance-and-troubleshooting.md#how-to-check-if-services-work), which will tell you if you need to do anything extra with regard to setting up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file). After some time, when most people have upgraded to Synapse v0.99 and older releases have disappeared, be prepared to drop your `_matrix._tcp` SRV record."

  7530. msgstr ""

  7531. 

  7532. #: ../../../CHANGELOG.md:4133

  7533. 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)."

  7534. msgstr ""

  7535. 

  7536. #: ../../../CHANGELOG.md:4136

  7537. msgid "2019-02-01"

  7538. msgstr ""

  7539. 

  7540. #: ../../../CHANGELOG.md:4138

  7541. msgid "TLS v1.3 support"

  7542. msgstr ""

  7543. 

  7544. #: ../../../CHANGELOG.md:4140

  7545. 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."

  7546. msgstr ""

  7547. 

  7548. #: ../../../CHANGELOG.md:4142

  7549. msgid "When using:"

  7550. msgstr ""

  7551. 

  7552. #: ../../../CHANGELOG.md:4144

  7553. 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`."

  7554. msgstr ""

  7555. 

  7556. #: ../../../CHANGELOG.md:4146

  7557. 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)"

  7558. msgstr ""

  7559. 

  7560. #: ../../../CHANGELOG.md:4148

  7561. msgid "**another web server**: you don't need to do anything to accommodate this change"

  7562. msgstr ""

  7563. 

  7564. #: ../../../CHANGELOG.md:4151

  7565. msgid "2019-01-31"

  7566. msgstr ""

  7567. 

  7568. #: ../../../CHANGELOG.md:4153

  7569. msgid "IRC bridging support"

  7570. msgstr ""

  7571. 

  7572. #: ../../../CHANGELOG.md:4155

  7573. 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."

  7574. msgstr ""

  7575. 

  7576. #: ../../../CHANGELOG.md:4158

  7577. msgid "2019-01-29"

  7578. msgstr ""

  7579. 

  7580. #: ../../../CHANGELOG.md:4160

  7581. msgid "Running container processes as non-root, without capabilities and read-only"

  7582. msgstr ""

  7583. 

  7584. #: ../../../CHANGELOG.md:4162

  7585. 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."

  7586. msgstr ""

  7587. 

  7588. #: ../../../CHANGELOG.md:4164

  7589. 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."

  7590. msgstr ""

  7591. 

  7592. #: ../../../CHANGELOG.md:4166

  7593. 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."

  7594. msgstr ""

  7595. 

  7596. #: ../../../CHANGELOG.md:4168

  7597. 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."

  7598. msgstr ""

  7599. 

  7600. #: ../../../CHANGELOG.md:4170

  7601. msgid "matrix-mailer is now based on Exim, not Postfix"

  7602. msgstr ""

  7603. 

  7604. #: ../../../CHANGELOG.md:4172

  7605. 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)."

  7606. msgstr ""

  7607. 

  7608. #: ../../../CHANGELOG.md:4174

  7609. 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`)."

  7610. msgstr ""

  7611. 

  7612. #: ../../../CHANGELOG.md:4176

  7613. 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)."

  7614. msgstr ""

  7615. 

  7616. #: ../../../CHANGELOG.md:4179

  7617. msgid "2019-01-17"

  7618. msgstr ""

  7619. 

  7620. #: ../../../CHANGELOG.md:4181

  7621. msgid "(BC Break) Making the playbook's roles more independent of one another"

  7622. msgstr ""

  7623. 

  7624. #: ../../../CHANGELOG.md:4183

  7625. 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)."

  7626. msgstr ""

  7627. 

  7628. #: ../../../CHANGELOG.md:4186

  7629. 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."

  7630. msgstr ""

  7631. 

  7632. #: ../../../CHANGELOG.md:4188

  7633. msgid "With the new changes, **all roles are now only dependent on the minimal `matrix-base` role**. They are no longer dependent among themselves."

  7634. msgstr ""

  7635. 

  7636. #: ../../../CHANGELOG.md:4190

  7637. msgid "In addition, the following components can now be completely disabled (for those who want/need to):"

  7638. msgstr ""

  7639. 

  7640. #: ../../../CHANGELOG.md:4191

  7641. msgid "`matrix-coturn` by using `coturn_enabled: false`"

  7642. msgstr ""

  7643. 

  7644. #: ../../../CHANGELOG.md:4192

  7645. msgid "`matrix-mailer` by using `matrix_mailer_enabled: false`"

  7646. msgstr ""

  7647. 

  7648. #: ../../../CHANGELOG.md:4193

  7649. msgid "`matrix-postgres` by using `matrix_postgres_enabled: false`"

  7650. msgstr ""

  7651. 

  7652. #: ../../../CHANGELOG.md:4195

  7653. msgid "The following changes had to be done:"

  7654. msgstr ""

  7655. 

  7656. #: ../../../CHANGELOG.md:4197

  7657. 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."

  7658. msgstr ""

  7659. 

  7660. #: ../../../CHANGELOG.md:4199

  7661. msgid "`matrix_postgres_use_external` has been superseded by the more consistently named `matrix_postgres_enabled` variable and a few other `matrix_synapse_database_` variables. See the [Using an external PostgreSQL server (optional)](docs/configuring-playbook-external-postgres.md) documentation page for an up-to-date replacement."

  7662. msgstr ""

  7663. 

  7664. #: ../../../CHANGELOG.md:4201

  7665. 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`)"

  7666. msgstr ""

  7667. 

  7668. #: ../../../CHANGELOG.md:4203

  7669. 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."

  7670. msgstr ""

  7671. 

  7672. #: ../../../CHANGELOG.md:4206

  7673. msgid "2019-01-16"

  7674. msgstr ""

  7675. 

  7676. #: ../../../CHANGELOG.md:4208

  7677. msgid "Splitting the playbook into multiple roles"

  7678. msgstr ""

  7679. 

  7680. #: ../../../CHANGELOG.md:4210

  7681. 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)."

  7682. msgstr ""

  7683. 

  7684. #: ../../../CHANGELOG.md:4213

  7685. msgid "To keep the filesystem more consistent with this separation, the **Postgres data had to be relocated**."

  7686. msgstr ""

  7687. 

  7688. #: ../../../CHANGELOG.md:4215

  7689. 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`)."

  7690. msgstr ""

  7691. 

  7692. #: ../../../CHANGELOG.md:4218

  7693. msgid "2019-01-11"

  7694. msgstr ""

  7695. 

  7696. #: ../../../CHANGELOG.md:4220

  7697. msgid "(BC Break) mxisd configuration changes"

  7698. msgstr ""

  7699. 

  7700. #: ../../../CHANGELOG.md:4222

  7701. 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."

  7702. msgstr ""

  7703. 

  7704. #: ../../../CHANGELOG.md:4225

  7705. msgid "The following variables are no longer supported by this playbook:"

  7706. msgstr ""

  7707. 

  7708. #: ../../../CHANGELOG.md:4227

  7709. msgid "`matrix_mxisd_ldap_enabled`"

  7710. msgstr ""

  7711. 

  7712. #: ../../../CHANGELOG.md:4228

  7713. msgid "`matrix_mxisd_ldap_connection_host`"

  7714. msgstr ""

  7715. 

  7716. #: ../../../CHANGELOG.md:4229

  7717. msgid "`matrix_mxisd_ldap_connection_tls`"

  7718. msgstr ""

  7719. 

  7720. #: ../../../CHANGELOG.md:4230

  7721. msgid "`matrix_mxisd_ldap_connection_port`"

  7722. msgstr ""

  7723. 

  7724. #: ../../../CHANGELOG.md:4231

  7725. msgid "`matrix_mxisd_ldap_connection_baseDn`"

  7726. msgstr ""

  7727. 

  7728. #: ../../../CHANGELOG.md:4232

  7729. msgid "`matrix_mxisd_ldap_connection_baseDns`"

  7730. msgstr ""

  7731. 

  7732. #: ../../../CHANGELOG.md:4233

  7733. #: ../../../CHANGELOG.md:4234

  7734. msgid "`matrix_mxisd_ldap_connection_bindDn`"

  7735. msgstr ""

  7736. 

  7737. #: ../../../CHANGELOG.md:4235

  7738. #: ../../../CHANGELOG.md:4239

  7739. msgid "`matrix_mxisd_ldap_connection_bindPassword`"

  7740. msgstr ""

  7741. 

  7742. #: ../../../CHANGELOG.md:4236

  7743. msgid "`matrix_mxisd_ldap_filter`"

  7744. msgstr ""

  7745. 

  7746. #: ../../../CHANGELOG.md:4237

  7747. msgid "`matrix_mxisd_ldap_attribute_uid_type`"

  7748. msgstr ""

  7749. 

  7750. #: ../../../CHANGELOG.md:4238

  7751. msgid "`matrix_mxisd_ldap_attribute_uid_value`"

  7752. msgstr ""

  7753. 

  7754. #: ../../../CHANGELOG.md:4240

  7755. msgid "`matrix_mxisd_ldap_attribute_name`"

  7756. msgstr ""

  7757. 

  7758. #: ../../../CHANGELOG.md:4241

  7759. msgid "`matrix_mxisd_ldap_attribute_threepid_email`"

  7760. msgstr ""

  7761. 

  7762. #: ../../../CHANGELOG.md:4242

  7763. msgid "`matrix_mxisd_ldap_attribute_threepid_msisdn`"

  7764. msgstr ""

  7765. 

  7766. #: ../../../CHANGELOG.md:4243

  7767. msgid "`matrix_mxisd_ldap_identity_filter`"

  7768. msgstr ""

  7769. 

  7770. #: ../../../CHANGELOG.md:4244

  7771. msgid "`matrix_mxisd_ldap_identity_medium`"

  7772. msgstr ""

  7773. 

  7774. #: ../../../CHANGELOG.md:4245

  7775. msgid "`matrix_mxisd_ldap_auth_filter`"

  7776. msgstr ""

  7777. 

  7778. #: ../../../CHANGELOG.md:4246

  7779. msgid "`matrix_mxisd_ldap_directory_filter`"

  7780. msgstr ""

  7781. 

  7782. #: ../../../CHANGELOG.md:4247

  7783. msgid "`matrix_mxisd_template_config`"

  7784. msgstr ""

  7785. 

  7786. #: ../../../CHANGELOG.md:4249

  7787. 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."

  7788. msgstr ""

  7789. 

  7790. #: ../../../CHANGELOG.md:4251

  7791. msgid "This new way of configuring mxisd is beneficial because:"

  7792. msgstr ""

  7793. 

  7794. #: ../../../CHANGELOG.md:4253

  7795. msgid "it lets us support all mxisd configuration options, as the playbook simply forwards them to mxisd without needing to care or understand them"

  7796. msgstr ""

  7797. 

  7798. #: ../../../CHANGELOG.md:4254

  7799. msgid "it lets you upgrade to newer mxisd versions and make use of their features, without us having to add support for them explicitly"

  7800. msgstr ""

  7801. 

  7802. #: ../../../CHANGELOG.md:4257

  7803. msgid "2019-01-08"

  7804. msgstr ""

  7805. 

  7806. #: ../../../CHANGELOG.md:4259

  7807. msgid "(BC Break) Cronjob schedule no longer configurable"

  7808. msgstr ""

  7809. 

  7810. #: ../../../CHANGELOG.md:4261

  7811. msgid "Due to the way we manage cronjobs now, you can no longer configure the schedule they're invoked at."

  7812. msgstr ""

  7813. 

  7814. #: ../../../CHANGELOG.md:4263

  7815. 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."

  7816. msgstr ""

  7817. 

  7818. #: ../../../CHANGELOG.md:4266

  7819. 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!"

  7820. msgstr ""

  7821. 

  7822. #: ../../../CHANGELOG.md:4269

  7823. msgid "2018-12-23"

  7824. msgstr ""

  7825. 

  7826. #: ../../../CHANGELOG.md:4271

  7827. msgid "(BC Break) More SSL certificate retrieval methods"

  7828. msgstr ""

  7829. 

  7830. #: ../../../CHANGELOG.md:4273

  7831. msgid "The playbook now lets you decide between 3 different SSL certificate retrieval methods:"

  7832. msgstr ""

  7833. 

  7834. #: ../../../CHANGELOG.md:4274

  7835. msgid "(default) obtaining free SSL certificates from Let's Encrypt"

  7836. msgstr ""

  7837. 

  7838. #: ../../../CHANGELOG.md:4275

  7839. msgid "generating self-signed SSL certificates"

  7840. msgstr ""

  7841. 

  7842. #: ../../../CHANGELOG.md:4276

  7843. msgid "managing SSL certificates manually"

  7844. msgstr ""

  7845. 

  7846. #: ../../../CHANGELOG.md:4278

  7847. msgid "Learn more in [Adjusting SSL certificate retrieval](docs/configuring-playbook-ssl-certificates.md)."

  7848. msgstr ""

  7849. 

  7850. #: ../../../CHANGELOG.md:4280

  7851. 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:"

  7852. msgstr ""

  7853. 

  7854. #: ../../../CHANGELOG.md:4282

  7855. msgid "before: `host_specific_matrix_ssl_support_email`"

  7856. msgstr ""

  7857. 

  7858. #: ../../../CHANGELOG.md:4283

  7859. msgid "after: `host_specific_matrix_ssl_lets_encrypt_support_email`"

  7860. msgstr ""

  7861. 

  7862. #: ../../../CHANGELOG.md:4285

  7863. msgid "(BC Break) mxisd upgrade with multiple base DN support"

  7864. msgstr ""

  7865. 

  7866. #: ../../../CHANGELOG.md:4287

  7867. 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)."

  7868. msgstr ""

  7869. 

  7870. #: ../../../CHANGELOG.md:4289

  7871. 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)."

  7872. msgstr ""

  7873. 

  7874. #: ../../../CHANGELOG.md:4291

  7875. msgid "Example change:"

  7876. msgstr ""

  7877. 

  7878. #: ../../../CHANGELOG.md:4293

  7879. msgid "before: `matrix_mxisd_ldap_connection_baseDn: OU=Users,DC=example,DC=org`"

  7880. msgstr ""

  7881. 

  7882. #: ../../../CHANGELOG.md:4294

  7883. msgid "after: `matrix_mxisd_ldap_connection_baseDns: ['OU=Users,DC=example,DC=org']`"

  7884. msgstr ""

  7885. 

  7886. #: ../../../CHANGELOG.md:4297

  7887. msgid "2018-12-21"

  7888. msgstr ""

  7889. 

  7890. #: ../../../CHANGELOG.md:4299

  7891. msgid "Synapse 0.34.0 and Python 3"

  7892. msgstr ""

  7893. 

  7894. #: ../../../CHANGELOG.md:4301

  7895. 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)."

  7896. msgstr ""

  7897. 

  7898. #: ../../../CHANGELOG.md:4304

  7899. msgid "2018-12-12"

  7900. msgstr ""

  7901. 

  7902. #: ../../../CHANGELOG.md:4306

  7903. msgid "Riot homepage customization"

  7904. msgstr ""

  7905. 

  7906. #: ../../../CHANGELOG.md:4308

  7907. 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`."

  7908. msgstr ""

  7909. 

  7910. #: ../../../CHANGELOG.md:4311

  7911. msgid "2018-12-04"

  7912. msgstr ""

  7913. 

  7914. #: ../../../CHANGELOG.md:4313

  7915. msgid "mxisd extensibility"

  7916. msgstr ""

  7917. 

  7918. #: ../../../CHANGELOG.md:4315

  7919. 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`)."

  7920. msgstr ""

  7921. 

  7922. #: ../../../CHANGELOG.md:4318

  7923. msgid "2018-11-28"

  7924. msgstr ""

  7925. 

  7926. #: ../../../CHANGELOG.md:4320

  7927. msgid "More scripts"

  7928. msgstr ""

  7929. 

  7930. #: ../../../CHANGELOG.md:4322

  7931. msgid "matrix-remove-all allows to uninstall everything with a single command"

  7932. msgstr ""

  7933. 

  7934. #: ../../../CHANGELOG.md:4323

  7935. msgid "matrix-make-user-admin allows to upgrade a user's privileges"

  7936. msgstr ""

  7937. 

  7938. #: ../../../CHANGELOG.md:4325

  7939. msgid "LDAP auth support via matrix-synapse-ldap3"

  7940. msgstr ""

  7941. 

  7942. #: ../../../CHANGELOG.md:4327

  7943. msgid "The playbook can now install and configure [LDAP auth support](https://github.com/matrix-org/matrix-synapse-ldap3) for you."

  7944. msgstr ""

  7945. 

  7946. #: ../../../CHANGELOG.md:4329

  7947. msgid "Additional details are available in [Setting up the LDAP authentication password provider module](docs/configuring-playbook-ldap-auth.md)."

  7948. msgstr ""

  7949. 

  7950. #: ../../../CHANGELOG.md:4332

  7951. msgid "2018-11-23"

  7952. msgstr ""

  7953. 

  7954. #: ../../../CHANGELOG.md:4334

  7955. msgid "Support for controlling public registration and room auto-join"

  7956. msgstr ""

  7957. 

  7958. #: ../../../CHANGELOG.md:4336

  7959. msgid "The playbook now lets you enable public registration for users (controlled via `matrix_synapse_enable_registration`). By default, public registration is forbidden."

  7960. msgstr ""

  7961. 

  7962. #: ../../../CHANGELOG.md:4338

  7963. msgid "You can also make people automatically get auto-joined to rooms (controlled via `matrix_synapse_auto_join_rooms`)."

  7964. msgstr ""

  7965. 

  7966. #: ../../../CHANGELOG.md:4340

  7967. msgid "Support for changing the welcome user ID (welcome bot)"

  7968. msgstr ""

  7969. 

  7970. #: ../../../CHANGELOG.md:4342

  7971. 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."

  7972. msgstr ""

  7973. 

  7974. #: ../../../CHANGELOG.md:4345

  7975. msgid "2018-11-14"

  7976. msgstr ""

  7977. 

  7978. #: ../../../CHANGELOG.md:4347

  7979. msgid "Ability to set Synapse log levels"

  7980. msgstr ""

  7981. 

  7982. #: ../../../CHANGELOG.md:4349

  7983. msgid "The playbook now allows you to set the log levels used by Synapse. The default logging levels remain the same."

  7984. msgstr ""

  7985. 

  7986. #: ../../../CHANGELOG.md:4351

  7987. 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"

  7988. msgstr ""

  7989. 

  7990. #: ../../../CHANGELOG.md:4360

  7991. msgid "2018-11-03"

  7992. msgstr ""

  7993. 

  7994. #: ../../../CHANGELOG.md:4362

  7995. msgid "Customize parts of Riot's config"

  7996. msgstr ""

  7997. 

  7998. #: ../../../CHANGELOG.md:4364

  7999. msgid "You can now customize some parts of Riot's `config.json`. These playbook variables, with these default values, have been added:"

  8000. msgstr ""

  8001. 

  8002. #: ../../../CHANGELOG.md:4375

  8003. 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:"

  8004. msgstr ""

  8005. 

  8006. #: ../../../CHANGELOG.md:4384

  8007. msgid "SSL protocols used to serve Riot and Synapse"

  8008. msgstr ""

  8009. 

  8010. #: ../../../CHANGELOG.md:4386

  8011. 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."

  8012. msgstr ""

  8013. 

  8014. #: ../../../CHANGELOG.md:4388

  8015. msgid "You may wish to re-enable TLSv1 if you need to access Riot in older browsers."

  8016. msgstr ""

  8017. 

  8018. #: ../../../CHANGELOG.md:4390

  8019. msgid "Note: Currently the dockerized nginx doesn't support TLSv1.3. See https://github.com/nginxinc/docker-nginx/issues/190 for more details."

  8020. msgstr ""

  8021. 

  8022. #: ../../../CHANGELOG.md:4393

  8023. msgid "2018-11-01"

  8024. msgstr ""

  8025. 

  8026. #: ../../../CHANGELOG.md:4395

  8027. msgid "Postgres 11 support"

  8028. msgstr ""

  8029. 

  8030. #: ../../../CHANGELOG.md:4397

  8031. msgid "The playbook now installs [Postgres 11](https://www.postgresql.org/about/news/1894/) by default."

  8032. msgstr ""

  8033. 

  8034. #: ../../../CHANGELOG.md:4399

  8035. 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)."

  8036. msgstr ""

  8037. 

  8038. #: ../../../CHANGELOG.md:4401

  8039. #: ../../../CHANGELOG.md:4488

  8040. #: ../../../CHANGELOG.md:4608

  8041. msgid "(BC Break) Renaming playbook variables"

  8042. msgstr ""

  8043. 

  8044. #: ../../../CHANGELOG.md:4403

  8045. 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."

  8046. msgstr ""

  8047. 

  8048. #: ../../../CHANGELOG.md:4407

  8049. msgid "from `matrix_docker_image_mxisd` to `matrix_mxisd_docker_image`"

  8050. msgstr ""

  8051. 

  8052. #: ../../../CHANGELOG.md:4408

  8053. msgid "from `matrix_docker_image_mautrix_telegram` to `matrix_mautrix_telegram_docker_image`"

  8054. msgstr ""

  8055. 

  8056. #: ../../../CHANGELOG.md:4409

  8057. msgid "from `matrix_docker_image_mautrix_whatsapp` to `matrix_mautrix_whatsapp_docker_image`"

  8058. msgstr ""

  8059. 

  8060. #: ../../../CHANGELOG.md:4410

  8061. msgid "from `matrix_docker_image_mailer` to `matrix_mailer_docker_image`"

  8062. msgstr ""

  8063. 

  8064. #: ../../../CHANGELOG.md:4411

  8065. msgid "from `matrix_docker_image_coturn` to `coturn_container_image`"

  8066. msgstr ""

  8067. 

  8068. #: ../../../CHANGELOG.md:4412

  8069. msgid "from `matrix_docker_image_goofys` to `matrix_s3_goofys_docker_image`"

  8070. msgstr ""

  8071. 

  8072. #: ../../../CHANGELOG.md:4413

  8073. msgid "from `matrix_docker_image_riot` to `matrix_riot_web_docker_image`"

  8074. msgstr ""

  8075. 

  8076. #: ../../../CHANGELOG.md:4414

  8077. msgid "from `matrix_docker_image_nginx` to `matrix_nginx_proxy_docker_image`"

  8078. msgstr ""

  8079. 

  8080. #: ../../../CHANGELOG.md:4415

  8081. msgid "from `matrix_docker_image_synapse` to `matrix_synapse_docker_image`"

  8082. msgstr ""

  8083. 

  8084. #: ../../../CHANGELOG.md:4416

  8085. msgid "from `matrix_docker_image_postgres_v9` to `matrix_postgres_docker_image_v9`"

  8086. msgstr ""

  8087. 

  8088. #: ../../../CHANGELOG.md:4417

  8089. msgid "from `matrix_docker_image_postgres_v10` to `matrix_postgres_docker_image_v10`"

  8090. msgstr ""

  8091. 

  8092. #: ../../../CHANGELOG.md:4418

  8093. msgid "from `matrix_docker_image_postgres_latest` to `matrix_postgres_docker_image_latest`"

  8094. msgstr ""

  8095. 

  8096. #: ../../../CHANGELOG.md:4421

  8097. msgid "2018-10-26"

  8098. msgstr ""

  8099. 

  8100. #: ../../../CHANGELOG.md:4423

  8101. msgid "Mautrix Whatsapp bridging support"

  8102. msgstr ""

  8103. 

  8104. #: ../../../CHANGELOG.md:4425

  8105. 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)."

  8106. msgstr ""

  8107. 

  8108. #: ../../../CHANGELOG.md:4427

  8109. msgid "Additional details are available in [Setting up Mautrix Whatsapp bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)."

  8110. msgstr ""

  8111. 

  8112. #: ../../../CHANGELOG.md:4430

  8113. msgid "2018-10-25"

  8114. msgstr ""

  8115. 

  8116. #: ../../../CHANGELOG.md:4432

  8117. msgid "Support for controlling Matrix federation"

  8118. msgstr ""

  8119. 

  8120. #: ../../../CHANGELOG.md:4434

  8121. 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."

  8122. msgstr ""

  8123. 

  8124. #: ../../../CHANGELOG.md:4437

  8125. msgid "2018-10-24"

  8126. msgstr ""

  8127. 

  8128. #: ../../../CHANGELOG.md:4439

  8129. msgid "Disabling riot-web guests"

  8130. msgstr ""

  8131. 

  8132. #: ../../../CHANGELOG.md:4441

  8133. 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."

  8134. msgstr ""

  8135. 

  8136. #: ../../../CHANGELOG.md:4444

  8137. msgid "2018-10-21"

  8138. msgstr ""

  8139. 

  8140. #: ../../../CHANGELOG.md:4446

  8141. msgid "Self-check maintenance command"

  8142. msgstr ""

  8143. 

  8144. #: ../../../CHANGELOG.md:4448

  8145. msgid "The playbook can now [check if services are configured correctly](docs/maintenance-and-troubleshooting.md#how-to-check-if-services-work)."

  8146. msgstr ""

  8147. 

  8148. #: ../../../CHANGELOG.md:4451

  8149. msgid "2018-10-05"

  8150. msgstr ""

  8151. 

  8152. #: ../../../CHANGELOG.md:4453

  8153. msgid "Presence tracking made configurable"

  8154. msgstr ""

  8155. 

  8156. #: ../../../CHANGELOG.md:4455

  8157. 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)."

  8158. msgstr ""

  8159. 

  8160. #: ../../../CHANGELOG.md:4457

  8161. msgid "If users participate in large rooms with many other servers, disabling presence will decrease server load significantly."

  8162. msgstr ""

  8163. 

  8164. #: ../../../CHANGELOG.md:4460

  8165. msgid "2018-09-27"

  8166. msgstr ""

  8167. 

  8168. #: ../../../CHANGELOG.md:4462

  8169. msgid "Synapse Cache Factor made configurable"

  8170. msgstr ""

  8171. 

  8172. #: ../../../CHANGELOG.md:4464

  8173. 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`)."

  8174. msgstr ""

  8175. 

  8176. #: ../../../CHANGELOG.md:4466

  8177. 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"

  8178. msgstr ""

  8179. 

  8180. #: ../../../CHANGELOG.md:4469

  8181. msgid "2018-09-26"

  8182. msgstr ""

  8183. 

  8184. #: ../../../CHANGELOG.md:4471

  8185. msgid "Disabling Docker container logging"

  8186. msgstr ""

  8187. 

  8188. #: ../../../CHANGELOG.md:4473

  8189. msgid "`--log-driver=none` is used for all Docker containers now."

  8190. msgstr ""

  8191. 

  8192. #: ../../../CHANGELOG.md:4475

  8193. 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."

  8194. msgstr ""

  8195. 

  8196. #: ../../../CHANGELOG.md:4477

  8197. 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."

  8198. msgstr ""

  8199. 

  8200. #: ../../../CHANGELOG.md:4480

  8201. msgid "2018-09-17"

  8202. msgstr ""

  8203. 

  8204. #: ../../../CHANGELOG.md:4482

  8205. msgid "Service discovery support"

  8206. msgstr ""

  8207. 

  8208. #: ../../../CHANGELOG.md:4484

  8209. 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."

  8210. msgstr ""

  8211. 

  8212. #: ../../../CHANGELOG.md:4486

  8213. msgid "Additional details are available in [Configuring service discovery via .well-known](docs/configuring-well-known.md)."

  8214. msgstr ""

  8215. 

  8216. #: ../../../CHANGELOG.md:4492

  8217. msgid "from `matrix_nginx_riot_web_data_path` to `matrix_riot_web_data_path`"

  8218. msgstr ""

  8219. 

  8220. #: ../../../CHANGELOG.md:4493

  8221. msgid "from `matrix_riot_web_default_identity_server_url` to `matrix_identity_server_url`"

  8222. msgstr ""

  8223. 

  8224. #: ../../../CHANGELOG.md:4496

  8225. msgid "2018-09-07"

  8226. msgstr ""

  8227. 

  8228. #: ../../../CHANGELOG.md:4498

  8229. msgid "Mautrix Telegram bridging support"

  8230. msgstr ""

  8231. 

  8232. #: ../../../CHANGELOG.md:4500

  8233. 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)."

  8234. msgstr ""

  8235. 

  8236. #: ../../../CHANGELOG.md:4502

  8237. msgid "Additional details are available in [Setting up Mautrix Telegram bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)."

  8238. msgstr ""

  8239. 

  8240. #: ../../../CHANGELOG.md:4504

  8241. msgid "Events cache size increase and configurability for Matrix Synapse"

  8242. msgstr ""

  8243. 

  8244. #: ../../../CHANGELOG.md:4506

  8245. msgid "The playbook now lets you configure Matrix Synapse's `event_cache_size` configuration via the `matrix_synapse_event_cache_size` playbook variable."

  8246. msgstr ""

  8247. 

  8248. #: ../../../CHANGELOG.md:4508

  8249. msgid "Previously, this value was hardcoded to `\"10K\"`. From now on, a more reasonable default of `\"100K\"` is used."

  8250. msgstr ""

  8251. 

  8252. #: ../../../CHANGELOG.md:4510

  8253. msgid "Password-peppering support for Matrix Synapse"

  8254. msgstr ""

  8255. 

  8256. #: ../../../CHANGELOG.md:4512

  8257. 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."

  8258. msgstr ""

  8259. 

  8260. #: ../../../CHANGELOG.md:4514

  8261. msgid "Statistics-reporting support for Matrix Synapse"

  8262. msgstr ""

  8263. 

  8264. #: ../../../CHANGELOG.md:4516

  8265. 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."

  8266. msgstr ""

  8267. 

  8268. #: ../../../CHANGELOG.md:4518

  8269. 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."

  8270. msgstr ""

  8271. 

  8272. #: ../../../CHANGELOG.md:4521

  8273. msgid "2018-08-29"

  8274. msgstr ""

  8275. 

  8276. #: ../../../CHANGELOG.md:4523

  8277. msgid "Changing the way SSL certificates are retrieved"

  8278. msgstr ""

  8279. 

  8280. #: ../../../CHANGELOG.md:4525

  8281. 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."

  8282. msgstr ""

  8283. 

  8284. #: ../../../CHANGELOG.md:4527

  8285. 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)."

  8286. msgstr ""

  8287. 

  8288. #: ../../../CHANGELOG.md:4529

  8289. 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:"

  8290. msgstr ""

  8291. 

  8292. #: ../../../CHANGELOG.md:4531

  8293. msgid "`systemctl stop 'matrix*'`"

  8294. msgstr ""

  8295. 

  8296. #: ../../../CHANGELOG.md:4532

  8297. msgid "stop your custom webserver, if you're running one (only affects you if you've installed with `matrix_nginx_proxy_enabled: false`)"

  8298. msgstr ""

  8299. 

  8300. #: ../../../CHANGELOG.md:4533

  8301. msgid "`mv /matrix/ssl /matrix/ssl-acmetool-delete-later`"

  8302. msgstr ""

  8303. 

  8304. #: ../../../CHANGELOG.md:4534

  8305. msgid "re-run the playbook's [installation](docs/installing.md)"

  8306. msgstr ""

  8307. 

  8308. #: ../../../CHANGELOG.md:4535

  8309. msgid "possibly delete `/matrix/ssl-acmetool-delete-later`"

  8310. msgstr ""

  8311. 

  8312. #: ../../../CHANGELOG.md:4538

  8313. msgid "2018-08-21"

  8314. msgstr ""

  8315. 

  8316. #: ../../../CHANGELOG.md:4540

  8317. msgid "Matrix Corporal support"

  8318. msgstr ""

  8319. 

  8320. #: ../../../CHANGELOG.md:4542

  8321. msgid "The playbook can now install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you."

  8322. msgstr ""

  8323. 

  8324. #: ../../../CHANGELOG.md:4544

  8325. msgid "Additional details are available in [Setting up Matrix Corporal](docs/configuring-playbook-matrix-corporal.md)."

  8326. msgstr ""

  8327. 

  8328. #: ../../../CHANGELOG.md:4547

  8329. msgid "2018-08-20"

  8330. msgstr ""

  8331. 

  8332. #: ../../../CHANGELOG.md:4549

  8333. msgid "Matrix Synapse rate limit control variables"

  8334. msgstr ""

  8335. 

  8336. #: ../../../CHANGELOG.md:4551

  8337. msgid "The following new variables can now be configured to control Matrix Synapse's rate-limiting (default values are shown below)."

  8338. msgstr ""

  8339. 

  8340. #: ../../../CHANGELOG.md:4558

  8341. msgid "Shared Secret Auth support via matrix-synapse-shared-secret-auth"

  8342. msgstr ""

  8343. 

  8344. #: ../../../CHANGELOG.md:4560

  8345. msgid "The playbook can now install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you."

  8346. msgstr ""

  8347. 

  8348. #: ../../../CHANGELOG.md:4562

  8349. msgid "Additional details are available in [Setting up the Shared Secret Auth password provider module](docs/configuring-playbook-shared-secret-auth.md)."

  8350. msgstr ""

  8351. 

  8352. #: ../../../CHANGELOG.md:4565

  8353. msgid "2018-08-17"

  8354. msgstr ""

  8355. 

  8356. #: ../../../CHANGELOG.md:4567

  8357. msgid "REST auth support via matrix-synapse-rest-auth"

  8358. msgstr ""

  8359. 

  8360. #: ../../../CHANGELOG.md:4569

  8361. msgid "The playbook can now install and configure [matrix-synapse-rest-auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you."

  8362. msgstr ""

  8363. 

  8364. #: ../../../CHANGELOG.md:4571

  8365. msgid "Additional details are available in [Setting up the REST authentication password provider module](docs/configuring-playbook-rest-auth.md)."

  8366. msgstr ""

  8367. 

  8368. #: ../../../CHANGELOG.md:4573

  8369. msgid "Compression improvements"

  8370. msgstr ""

  8371. 

  8372. #: ../../../CHANGELOG.md:4575

  8373. msgid "Shifted Matrix Synapse compression from happening in the Matrix Synapse, to happening in the nginx proxy that's in front of it."

  8374. msgstr ""

  8375. 

  8376. #: ../../../CHANGELOG.md:4578

  8377. 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."

  8378. msgstr ""

  8379. 

  8380. #: ../../../CHANGELOG.md:4581

  8381. msgid "Disabling some unnecessary Synapse services"

  8382. msgstr ""

  8383. 

  8384. #: ../../../CHANGELOG.md:4583

  8385. msgid "The following services are not necessary, so they have been disabled:"

  8386. msgstr ""

  8387. 

  8388. #: ../../../CHANGELOG.md:4584

  8389. msgid "on the federation port (8448): the `client` service"

  8390. msgstr ""

  8391. 

  8392. #: ../../../CHANGELOG.md:4585

  8393. msgid "on the http port (8008, exposed over 443): the old Angular `webclient` and the `federation` service"

  8394. msgstr ""

  8395. 

  8396. #: ../../../CHANGELOG.md:4587

  8397. msgid "Federation runs only on the federation port (8448) now. The Client APIs run only on the http port (8008) now."

  8398. msgstr ""

  8399. 

  8400. #: ../../../CHANGELOG.md:4590

  8401. msgid "2018-08-15"

  8402. msgstr ""

  8403. 

  8404. #: ../../../CHANGELOG.md:4592

  8405. msgid "mxisd Identity Server support"

  8406. msgstr ""

  8407. 

  8408. #: ../../../CHANGELOG.md:4594

  8409. 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)."

  8410. msgstr ""

  8411. 

  8412. #: ../../../CHANGELOG.md:4597

  8413. msgid "2018-08-14"

  8414. msgstr ""

  8415. 

  8416. #: ../../../CHANGELOG.md:4599

  8417. msgid "Email-sending support"

  8418. msgstr ""

  8419. 

  8420. #: ../../../CHANGELOG.md:4601

  8421. 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)."

  8422. msgstr ""

  8423. 

  8424. #: ../../../CHANGELOG.md:4603

  8425. msgid "With this, Matrix Synapse is able to send email notifications for missed messages, etc."

  8426. msgstr ""

  8427. 

  8428. #: ../../../CHANGELOG.md:4606

  8429. msgid "2018-08-08"

  8430. msgstr ""

  8431. 

  8432. #: ../../../CHANGELOG.md:4612

  8433. msgid "from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`"

  8434. msgstr ""

  8435. 

  8436. #: ../../../CHANGELOG.md:4613

  8437. msgid "from `matrix_max_log_file_size_mb` to `matrix_synapse_max_log_file_size_mb`"

  8438. msgstr ""

  8439. 

  8440. #: ../../../CHANGELOG.md:4614

  8441. msgid "from `matrix_max_log_files_count` to `matrix_synapse_max_log_files_count`"

  8442. msgstr ""

  8443. 

  8444. #: ../../../CHANGELOG.md:4615

  8445. msgid "from `docker_matrix_image` to `matrix_docker_image_synapse`"

  8446. msgstr ""

  8447. 

  8448. #: ../../../CHANGELOG.md:4616

  8449. msgid "from `docker_nginx_image` to `matrix_docker_image_nginx`"

  8450. msgstr ""

  8451. 

  8452. #: ../../../CHANGELOG.md:4617

  8453. msgid "from `docker_riot_image` to `matrix_docker_image_riot`"

  8454. msgstr ""

  8455. 

  8456. #: ../../../CHANGELOG.md:4618

  8457. msgid "from `docker_goofys_image` to `matrix_docker_image_goofys`"

  8458. msgstr ""

  8459. 

  8460. #: ../../../CHANGELOG.md:4619

  8461. msgid "from `docker_coturn_image` to `matrix_docker_image_coturn`"

  8462. msgstr ""

  8463. 

  8464. #: ../../../CHANGELOG.md:4621

  8465. msgid "If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names."

  8466. msgstr ""

  8467. 

  8468. #: ../../../CHANGELOG.md:4623

  8469. msgid "Renaming Ansible playbook tag"

  8470. msgstr ""

  8471. 

  8472. #: ../../../CHANGELOG.md:4625

  8473. msgid "The command for executing the whole playbook has changed. The `setup-main` tag got renamed to `setup-all`."

  8474. msgstr ""

  8475. 

  8476. #: ../../../CHANGELOG.md:4627

  8477. msgid "Docker container linking"

  8478. msgstr ""

  8479. 

  8480. #: ../../../CHANGELOG.md:4629

  8481. 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."

  8482. msgstr ""