overmind
/
matrix-docker-ansible-deploy
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy
1
0
Fork 0
Code Issues 0 Releases 0 Wiki Activity
Matrix Docker Ansible eploy
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
10672 Commits
12 Branches
958 MiB
 
 
Tree: bab0f8639c
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'bab0f8639c'
${ noResults }
matrix-docker-ansible-deploy/i18n/translation-templates/CHANGELOG.pot

7501 lines
374 KiB
Raw Blame History 

  1. # SOME DESCRIPTIVE TITLE.

  2. # Copyright (C) 2018-2025, 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: 2025-11-06 23:09+0900\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 "2025-11-05"

  21. msgstr ""

  22. 

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

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

  25. msgstr ""

  26. 

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

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

  29. msgstr ""

  30. 

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

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

  33. msgstr ""

  34. 

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

  36. msgid "`matrix_mx_puppet_discord_*`"

  37. msgstr ""

  38. 

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

  40. msgid "`matrix_mx_puppet_instagram_*`"

  41. msgstr ""

  42. 

  43. #: ../../../CHANGELOG.md:11

  44. msgid "`matrix_mx_puppet_slack_*`"

  45. msgstr ""

  46. 

  47. #: ../../../CHANGELOG.md:12

  48. msgid "`matrix_mx_puppet_twitter_*`"

  49. msgstr ""

  50. 

  51. #: ../../../CHANGELOG.md:14

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

  53. msgstr ""

  54. 

  55. #: ../../../CHANGELOG.md:16

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

  57. msgstr ""

  58. 

  59. #: ../../../CHANGELOG.md:17

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

  61. msgstr ""

  62. 

  63. #: ../../../CHANGELOG.md:18

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

  65. msgstr ""

  66. 

  67. #: ../../../CHANGELOG.md:19

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

  69. msgstr ""

  70. 

  71. #: ../../../CHANGELOG.md:21

  72. msgid "2025-11-04"

  73. msgstr ""

  74. 

  75. #: ../../../CHANGELOG.md:23

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

  77. msgstr ""

  78. 

  79. #: ../../../CHANGELOG.md:25

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

  81. msgstr ""

  82. 

  83. #: ../../../CHANGELOG.md:27

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

  85. msgstr ""

  86. 

  87. #: ../../../CHANGELOG.md:29

  88. msgid "2025-10-02"

  89. msgstr ""

  90. 

  91. #: ../../../CHANGELOG.md:31

  92. msgid "Element Admin support"

  93. msgstr ""

  94. 

  95. #: ../../../CHANGELOG.md:33

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

  97. msgstr ""

  98. 

  99. #: ../../../CHANGELOG.md:35

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

  101. msgstr ""

  102. 

  103. #: ../../../CHANGELOG.md:37

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

  105. msgstr ""

  106. 

  107. #: ../../../CHANGELOG.md:40

  108. msgid "2025-04-26"

  109. msgstr ""

  110. 

  111. #: ../../../CHANGELOG.md:42

  112. msgid "Continuwuity support"

  113. msgstr ""

  114. 

  115. #: ../../../CHANGELOG.md:44

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

  117. msgstr ""

  118. 

  119. #: ../../../CHANGELOG.md:46

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

  121. msgstr ""

  122. 

  123. #: ../../../CHANGELOG.md:48

  124. #: ../../../CHANGELOG.md:261

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

  126. msgstr ""

  127. 

  128. #: ../../../CHANGELOG.md:50

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

  130. msgstr ""

  131. 

  132. #: ../../../CHANGELOG.md:52

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

  134. msgstr ""

  135. 

  136. #: ../../../CHANGELOG.md:53

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

  138. msgstr ""

  139. 

  140. #: ../../../CHANGELOG.md:55

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

  142. msgstr ""

  143. 

  144. #: ../../../CHANGELOG.md:58

  145. msgid "2025-04-09"

  146. msgstr ""

  147. 

  148. #: ../../../CHANGELOG.md:60

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

  150. msgstr ""

  151. 

  152. #: ../../../CHANGELOG.md:62

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

  154. msgstr ""

  155. 

  156. #: ../../../CHANGELOG.md:64

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

  158. msgstr ""

  159. 

  160. #: ../../../CHANGELOG.md:66

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

  162. msgstr ""

  163. 

  164. #: ../../../CHANGELOG.md:68

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

  166. msgstr ""

  167. 

  168. #: ../../../CHANGELOG.md:70

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

  170. msgstr ""

  171. 

  172. #: ../../../CHANGELOG.md:77

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

  174. msgstr ""

  175. 

  176. #: ../../../CHANGELOG.md:79

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

  178. msgstr ""

  179. 

  180. #: ../../../CHANGELOG.md:82

  181. msgid "2025-03-15"

  182. msgstr ""

  183. 

  184. #: ../../../CHANGELOG.md:84

  185. msgid "Element Call support"

  186. msgstr ""

  187. 

  188. #: ../../../CHANGELOG.md:86

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

  190. msgstr ""

  191. 

  192. #: ../../../CHANGELOG.md:88

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

  194. msgstr ""

  195. 

  196. #: ../../../CHANGELOG.md:90

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

  198. msgstr ""

  199. 

  200. #: ../../../CHANGELOG.md:92

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

  202. msgstr ""

  203. 

  204. #: ../../../CHANGELOG.md:95

  205. msgid "2025-03-08"

  206. msgstr ""

  207. 

  208. #: ../../../CHANGELOG.md:97

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

  210. msgstr ""

  211. 

  212. #: ../../../CHANGELOG.md:99

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

  214. msgstr ""

  215. 

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

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

  218. msgstr ""

  219. 

  220. #: ../../../CHANGELOG.md:103

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

  222. msgstr ""

  223. 

  224. #: ../../../CHANGELOG.md:105

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

  226. msgstr ""

  227. 

  228. #: ../../../CHANGELOG.md:106

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

  230. msgstr ""

  231. 

  232. #: ../../../CHANGELOG.md:107

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

  234. msgstr ""

  235. 

  236. #: ../../../CHANGELOG.md:108

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

  238. msgstr ""

  239. 

  240. #: ../../../CHANGELOG.md:109

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

  242. msgstr ""

  243. 

  244. #: ../../../CHANGELOG.md:111

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

  246. msgstr ""

  247. 

  248. #: ../../../CHANGELOG.md:113

  249. msgid "2025-02-26"

  250. msgstr ""

  251. 

  252. #: ../../../CHANGELOG.md:115

  253. msgid "🪦 Bye-bye, Email2Matrix"

  254. msgstr ""

  255. 

  256. #: ../../../CHANGELOG.md:117

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

  258. msgstr ""

  259. 

  260. #: ../../../CHANGELOG.md:119

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

  262. msgstr ""

  263. 

  264. #: ../../../CHANGELOG.md:122

  265. msgid "2025-02-23"

  266. msgstr ""

  267. 

  268. #: ../../../CHANGELOG.md:124

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

  270. msgstr ""

  271. 

  272. #: ../../../CHANGELOG.md:126

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

  274. msgstr ""

  275. 

  276. #: ../../../CHANGELOG.md:128

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

  278. msgstr ""

  279. 

  280. #: ../../../CHANGELOG.md:131

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

  282. msgstr ""

  283. 

  284. #: ../../../CHANGELOG.md:133

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

  286. msgstr ""

  287. 

  288. #: ../../../CHANGELOG.md:135

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

  290. msgstr ""

  291. 

  292. #: ../../../CHANGELOG.md:137

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

  294. msgstr ""

  295. 

  296. #: ../../../CHANGELOG.md:139

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

  298. msgstr ""

  299. 

  300. #: ../../../CHANGELOG.md:145

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

  302. msgstr ""

  303. 

  304. #: ../../../CHANGELOG.md:147

  305. msgid "2025-02-21"

  306. msgstr ""

  307. 

  308. #: ../../../CHANGELOG.md:149

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

  310. msgstr ""

  311. 

  312. #: ../../../CHANGELOG.md:151

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

  314. msgstr ""

  315. 

  316. #: ../../../CHANGELOG.md:153

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

  318. msgstr ""

  319. 

  320. #: ../../../CHANGELOG.md:155

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

  322. msgstr ""

  323. 

  324. #: ../../../CHANGELOG.md:156

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

  326. msgstr ""

  327. 

  328. #: ../../../CHANGELOG.md:158

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

  330. msgstr ""

  331. 

  332. #: ../../../CHANGELOG.md:159

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

  334. msgstr ""

  335. 

  336. #: ../../../CHANGELOG.md:160

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

  338. msgstr ""

  339. 

  340. #: ../../../CHANGELOG.md:162

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

  342. msgstr ""

  343. 

  344. #: ../../../CHANGELOG.md:165

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

  346. msgstr ""

  347. 

  348. #: ../../../CHANGELOG.md:167

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

  350. msgstr ""

  351. 

  352. #: ../../../CHANGELOG.md:168

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

  354. msgstr ""

  355. 

  356. #: ../../../CHANGELOG.md:169

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

  358. msgstr ""

  359. 

  360. #: ../../../CHANGELOG.md:170

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

  362. msgstr ""

  363. 

  364. #: ../../../CHANGELOG.md:181

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

  366. msgstr ""

  367. 

  368. #: ../../../CHANGELOG.md:183

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

  370. msgstr ""

  371. 

  372. #: ../../../CHANGELOG.md:185

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

  374. msgstr ""

  375. 

  376. #: ../../../CHANGELOG.md:188

  377. msgid "2025-02-19"

  378. msgstr ""

  379. 

  380. #: ../../../CHANGELOG.md:190

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

  382. msgstr ""

  383. 

  384. #: ../../../CHANGELOG.md:192

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

  386. msgstr ""

  387. 

  388. #: ../../../CHANGELOG.md:194

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

  390. msgstr ""

  391. 

  392. #: ../../../CHANGELOG.md:196

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

  394. msgstr ""

  395. 

  396. #: ../../../CHANGELOG.md:198

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

  398. msgstr ""

  399. 

  400. #: ../../../CHANGELOG.md:200

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

  402. msgstr ""

  403. 

  404. #: ../../../CHANGELOG.md:206

  405. msgid "[!WARNING] People running Coturn directly on the `host` network (using `matrix_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)."

  406. msgstr ""

  407. 

  408. #: ../../../CHANGELOG.md:210

  409. msgid "2025-02-17"

  410. msgstr ""

  411. 

  412. #: ../../../CHANGELOG.md:212

  413. msgid "FluffyChat Web support"

  414. msgstr ""

  415. 

  416. #: ../../../CHANGELOG.md:214

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

  418. msgstr ""

  419. 

  420. #: ../../../CHANGELOG.md:216

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

  422. msgstr ""

  423. 

  424. #: ../../../CHANGELOG.md:219

  425. msgid "2025-02-03"

  426. msgstr ""

  427. 

  428. #: ../../../CHANGELOG.md:221

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

  430. msgstr ""

  431. 

  432. #: ../../../CHANGELOG.md:223

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

  434. msgstr ""

  435. 

  436. #: ../../../CHANGELOG.md:225

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

  438. msgstr ""

  439. 

  440. #: ../../../CHANGELOG.md:227

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

  442. msgstr ""

  443. 

  444. #: ../../../CHANGELOG.md:230

  445. msgid "2025-01-27"

  446. msgstr ""

  447. 

  448. #: ../../../CHANGELOG.md:232

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

  450. msgstr ""

  451. 

  452. #: ../../../CHANGELOG.md:234

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

  454. msgstr ""

  455. 

  456. #: ../../../CHANGELOG.md:236

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

  458. msgstr ""

  459. 

  460. #: ../../../CHANGELOG.md:238

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

  462. msgstr ""

  463. 

  464. #: ../../../CHANGELOG.md:239

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

  466. msgstr ""

  467. 

  468. #: ../../../CHANGELOG.md:240

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

  470. msgstr ""

  471. 

  472. #: ../../../CHANGELOG.md:242

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

  474. msgstr ""

  475. 

  476. #: ../../../CHANGELOG.md:244

  477. msgid "removing Redis and KeyDB support entirely"

  478. msgstr ""

  479. 

  480. #: ../../../CHANGELOG.md:245

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

  482. msgstr ""

  483. 

  484. #: ../../../CHANGELOG.md:247

  485. msgid "To update your configuration:"

  486. msgstr ""

  487. 

  488. #: ../../../CHANGELOG.md:249

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

  490. msgstr ""

  491. 

  492. #: ../../../CHANGELOG.md:250

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

  494. msgstr ""

  495. 

  496. #: ../../../CHANGELOG.md:253

  497. msgid "2025-01-19"

  498. msgstr ""

  499. 

  500. #: ../../../CHANGELOG.md:255

  501. msgid "conduwuit support"

  502. msgstr ""

  503. 

  504. #: ../../../CHANGELOG.md:257

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

  506. msgstr ""

  507. 

  508. #: ../../../CHANGELOG.md:259

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

  510. msgstr ""

  511. 

  512. #: ../../../CHANGELOG.md:263

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

  514. msgstr ""

  515. 

  516. #: ../../../CHANGELOG.md:265

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

  518. msgstr ""

  519. 

  520. #: ../../../CHANGELOG.md:268

  521. msgid "2025-01-14"

  522. msgstr ""

  523. 

  524. #: ../../../CHANGELOG.md:270

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

  526. msgstr ""

  527. 

  528. #: ../../../CHANGELOG.md:272

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

  530. msgstr ""

  531. 

  532. #: ../../../CHANGELOG.md:274

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

  534. msgstr ""

  535. 

  536. #: ../../../CHANGELOG.md:276

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

  538. msgstr ""

  539. 

  540. #: ../../../CHANGELOG.md:278

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

  542. msgstr ""

  543. 

  544. #: ../../../CHANGELOG.md:280

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

  546. msgstr ""

  547. 

  548. #: ../../../CHANGELOG.md:288

  549. msgid "2024-11-26"

  550. msgstr ""

  551. 

  552. #: ../../../CHANGELOG.md:290

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

  554. msgstr ""

  555. 

  556. #: ../../../CHANGELOG.md:292

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

  558. msgstr ""

  559. 

  560. #: ../../../CHANGELOG.md:294

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

  562. msgstr ""

  563. 

  564. #: ../../../CHANGELOG.md:296

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

  566. msgstr ""

  567. 

  568. #: ../../../CHANGELOG.md:298

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

  570. msgstr ""

  571. 

  572. #: ../../../CHANGELOG.md:300

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

  574. msgstr ""

  575. 

  576. #: ../../../CHANGELOG.md:302

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

  578. msgstr ""

  579. 

  580. #: ../../../CHANGELOG.md:304

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

  582. msgstr ""

  583. 

  584. #: ../../../CHANGELOG.md:307

  585. msgid "2024-11-23"

  586. msgstr ""

  587. 

  588. #: ../../../CHANGELOG.md:309

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

  590. msgstr ""

  591. 

  592. #: ../../../CHANGELOG.md:311

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

  594. msgstr ""

  595. 

  596. #: ../../../CHANGELOG.md:313

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

  598. msgstr ""

  599. 

  600. #: ../../../CHANGELOG.md:315

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

  602. msgstr ""

  603. 

  604. #: ../../../CHANGELOG.md:317

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

  606. msgstr ""

  607. 

  608. #: ../../../CHANGELOG.md:319

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

  610. msgstr ""

  611. 

  612. #: ../../../CHANGELOG.md:321

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

  614. msgstr ""

  615. 

  616. #: ../../../CHANGELOG.md:323

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

  618. msgstr ""

  619. 

  620. #: ../../../CHANGELOG.md:325

  621. #: ../../../CHANGELOG.md:665

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

  623. msgstr ""

  624. 

  625. #: ../../../CHANGELOG.md:336

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

  627. msgstr ""

  628. 

  629. #: ../../../CHANGELOG.md:346

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

  631. msgstr ""

  632. 

  633. #: ../../../CHANGELOG.md:349

  634. msgid "2024-11-14"

  635. msgstr ""

  636. 

  637. #: ../../../CHANGELOG.md:351

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

  639. msgstr ""

  640. 

  641. #: ../../../CHANGELOG.md:353

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

  643. msgstr ""

  644. 

  645. #: ../../../CHANGELOG.md:355

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

  647. msgstr ""

  648. 

  649. #: ../../../CHANGELOG.md:357

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

  651. msgstr ""

  652. 

  653. #: ../../../CHANGELOG.md:359

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

  655. msgstr ""

  656. 

  657. #: ../../../CHANGELOG.md:361

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

  659. msgstr ""

  660. 

  661. #: ../../../CHANGELOG.md:363

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

  663. msgstr ""

  664. 

  665. #: ../../../CHANGELOG.md:364

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

  667. msgstr ""

  668. 

  669. #: ../../../CHANGELOG.md:365

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

  671. msgstr ""

  672. 

  673. #: ../../../CHANGELOG.md:367

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

  675. msgstr ""

  676. 

  677. #: ../../../CHANGELOG.md:369

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

  679. msgstr ""

  680. 

  681. #: ../../../CHANGELOG.md:371

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

  683. msgstr ""

  684. 

  685. #: ../../../CHANGELOG.md:373

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

  687. msgstr ""

  688. 

  689. #: ../../../CHANGELOG.md:375

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

  691. msgstr ""

  692. 

  693. #: ../../../CHANGELOG.md:377

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

  695. msgstr ""

  696. 

  697. #: ../../../CHANGELOG.md:388

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

  699. msgstr ""

  700. 

  701. #: ../../../CHANGELOG.md:391

  702. msgid "2024-11-08"

  703. msgstr ""

  704. 

  705. #: ../../../CHANGELOG.md:393

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

  707. msgstr ""

  708. 

  709. #: ../../../CHANGELOG.md:395

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

  711. msgstr ""

  712. 

  713. #: ../../../CHANGELOG.md:397

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

  715. msgstr ""

  716. 

  717. #: ../../../CHANGELOG.md:399

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

  719. msgstr ""

  720. 

  721. #: ../../../CHANGELOG.md:402

  722. msgid "2024-10-28"

  723. msgstr ""

  724. 

  725. #: ../../../CHANGELOG.md:404

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

  727. msgstr ""

  728. 

  729. #: ../../../CHANGELOG.md:406

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

  731. msgstr ""

  732. 

  733. #: ../../../CHANGELOG.md:408

  734. msgid "2024-10-19"

  735. msgstr ""

  736. 

  737. #: ../../../CHANGELOG.md:410

  738. msgid "Support for Matrix Authentication Service"

  739. msgstr ""

  740. 

  741. #: ../../../CHANGELOG.md:412

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

  743. msgstr ""

  744. 

  745. #: ../../../CHANGELOG.md:414

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

  747. msgstr ""

  748. 

  749. #: ../../../CHANGELOG.md:416

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

  751. msgstr ""

  752. 

  753. #: ../../../CHANGELOG.md:418

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

  755. msgstr ""

  756. 

  757. #: ../../../CHANGELOG.md:421

  758. msgid "2024-09-27"

  759. msgstr ""

  760. 

  761. #: ../../../CHANGELOG.md:423

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

  763. msgstr ""

  764. 

  765. #: ../../../CHANGELOG.md:425

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

  767. msgstr ""

  768. 

  769. #: ../../../CHANGELOG.md:427

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

  771. msgstr ""

  772. 

  773. #: ../../../CHANGELOG.md:429

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

  775. msgstr ""

  776. 

  777. #: ../../../CHANGELOG.md:431

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

  779. msgstr ""

  780. 

  781. #: ../../../CHANGELOG.md:432

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

  783. msgstr ""

  784. 

  785. #: ../../../CHANGELOG.md:434

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

  787. msgstr ""

  788. 

  789. #: ../../../CHANGELOG.md:437

  790. msgid "2024-09-12"

  791. msgstr ""

  792. 

  793. #: ../../../CHANGELOG.md:439

  794. msgid "Support for baibot"

  795. msgstr ""

  796. 

  797. #: ../../../CHANGELOG.md:441

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

  799. msgstr ""

  800. 

  801. #: ../../../CHANGELOG.md:443

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

  803. msgstr ""

  804. 

  805. #: ../../../CHANGELOG.md:445

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

  807. msgstr ""

  808. 

  809. #: ../../../CHANGELOG.md:447

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

  811. msgstr ""

  812. 

  813. #: ../../../CHANGELOG.md:449

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

  815. msgstr ""

  816. 

  817. #: ../../../CHANGELOG.md:451

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

  819. msgstr ""

  820. 

  821. #: ../../../CHANGELOG.md:453

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

  823. msgstr ""

  824. 

  825. #: ../../../CHANGELOG.md:455

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

  827. msgstr ""

  828. 

  829. #: ../../../CHANGELOG.md:457

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

  831. msgstr ""

  832. 

  833. #: ../../../CHANGELOG.md:470

  834. msgid "2024-08-17"

  835. msgstr ""

  836. 

  837. #: ../../../CHANGELOG.md:472

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

  839. msgstr ""

  840. 

  841. #: ../../../CHANGELOG.md:474

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

  843. msgstr ""

  844. 

  845. #: ../../../CHANGELOG.md:476

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

  847. msgstr ""

  848. 

  849. #: ../../../CHANGELOG.md:478

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

  851. msgstr ""

  852. 

  853. #: ../../../CHANGELOG.md:480

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

  855. msgstr ""

  856. 

  857. #: ../../../CHANGELOG.md:482

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

  859. msgstr ""

  860. 

  861. #: ../../../CHANGELOG.md:488

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

  863. msgstr ""

  864. 

  865. #: ../../../CHANGELOG.md:490

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

  867. msgstr ""

  868. 

  869. #: ../../../CHANGELOG.md:493

  870. msgid "2024-08-15"

  871. msgstr ""

  872. 

  873. #: ../../../CHANGELOG.md:495

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

  875. msgstr ""

  876. 

  877. #: ../../../CHANGELOG.md:497

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

  879. msgstr ""

  880. 

  881. #: ../../../CHANGELOG.md:499

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

  883. msgstr ""

  884. 

  885. #: ../../../CHANGELOG.md:501

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

  887. msgstr ""

  888. 

  889. #: ../../../CHANGELOG.md:503

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

  891. msgstr ""

  892. 

  893. #: ../../../CHANGELOG.md:506

  894. msgid "2024-08-08"

  895. msgstr ""

  896. 

  897. #: ../../../CHANGELOG.md:508

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

  899. msgstr ""

  900. 

  901. #: ../../../CHANGELOG.md:510

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

  903. msgstr ""

  904. 

  905. #: ../../../CHANGELOG.md:512

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

  907. msgstr ""

  908. 

  909. #: ../../../CHANGELOG.md:514

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

  911. msgstr ""

  912. 

  913. #: ../../../CHANGELOG.md:520

  914. msgid "2024-07-25"

  915. msgstr ""

  916. 

  917. #: ../../../CHANGELOG.md:522

  918. msgid "synapse-usage-exporter support"

  919. msgstr ""

  920. 

  921. #: ../../../CHANGELOG.md:524

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

  923. msgstr ""

  924. 

  925. #: ../../../CHANGELOG.md:526

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

  927. msgstr ""

  928. 

  929. #: ../../../CHANGELOG.md:529

  930. msgid "2024-07-06"

  931. msgstr ""

  932. 

  933. #: ../../../CHANGELOG.md:531

  934. msgid "matrix-alertmanager-receiver support"

  935. msgstr ""

  936. 

  937. #: ../../../CHANGELOG.md:533

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

  939. msgstr ""

  940. 

  941. #: ../../../CHANGELOG.md:535

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

  943. msgstr ""

  944. 

  945. #: ../../../CHANGELOG.md:537

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

  947. msgstr ""

  948. 

  949. #: ../../../CHANGELOG.md:539

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

  951. msgstr ""

  952. 

  953. #: ../../../CHANGELOG.md:541

  954. msgid "Traefik v3"

  955. msgstr ""

  956. 

  957. #: ../../../CHANGELOG.md:543

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

  959. msgstr ""

  960. 

  961. #: ../../../CHANGELOG.md:545

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

  963. msgstr ""

  964. 

  965. #: ../../../CHANGELOG.md:547

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

  967. msgstr ""

  968. 

  969. #: ../../../CHANGELOG.md:549

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

  971. msgstr ""

  972. 

  973. #: ../../../CHANGELOG.md:551

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

  975. msgstr ""

  976. 

  977. #: ../../../CHANGELOG.md:553

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

  979. msgstr ""

  980. 

  981. #: ../../../CHANGELOG.md:555

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

  983. msgstr ""

  984. 

  985. #: ../../../CHANGELOG.md:557

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

  987. msgstr ""

  988. 

  989. #: ../../../CHANGELOG.md:559

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

  991. msgstr ""

  992. 

  993. #: ../../../CHANGELOG.md:561

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

  995. msgstr ""

  996. 

  997. #: ../../../CHANGELOG.md:563

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

  999. msgstr ""

  1000. 

  1001. #: ../../../CHANGELOG.md:565

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

  1003. msgstr ""

  1004. 

  1005. #: ../../../CHANGELOG.md:567

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

  1007. msgstr ""

  1008. 

  1009. #: ../../../CHANGELOG.md:581

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

  1011. msgstr ""

  1012. 

  1013. #: ../../../CHANGELOG.md:594

  1014. msgid "2024-07-01"

  1015. msgstr ""

  1016. 

  1017. #: ../../../CHANGELOG.md:596

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

  1019. msgstr ""

  1020. 

  1021. #: ../../../CHANGELOG.md:598

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

  1023. msgstr ""

  1024. 

  1025. #: ../../../CHANGELOG.md:600

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

  1027. msgstr ""

  1028. 

  1029. #: ../../../CHANGELOG.md:602

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

  1031. msgstr ""

  1032. 

  1033. #: ../../../CHANGELOG.md:610

  1034. msgid "2024-06-25"

  1035. msgstr ""

  1036. 

  1037. #: ../../../CHANGELOG.md:612

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

  1039. msgstr ""

  1040. 

  1041. #: ../../../CHANGELOG.md:614

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

  1043. msgstr ""

  1044. 

  1045. #: ../../../CHANGELOG.md:616

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

  1047. msgstr ""

  1048. 

  1049. #: ../../../CHANGELOG.md:618

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

  1051. msgstr ""

  1052. 

  1053. #: ../../../CHANGELOG.md:620

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

  1055. msgstr ""

  1056. 

  1057. #: ../../../CHANGELOG.md:622

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

  1059. msgstr ""

  1060. 

  1061. #: ../../../CHANGELOG.md:624

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

  1063. msgstr ""

  1064. 

  1065. #: ../../../CHANGELOG.md:626

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

  1067. msgstr ""

  1068. 

  1069. #: ../../../CHANGELOG.md:629

  1070. msgid "2024-06-22"

  1071. msgstr ""

  1072. 

  1073. #: ../../../CHANGELOG.md:631

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

  1075. msgstr ""

  1076. 

  1077. #: ../../../CHANGELOG.md:633

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

  1079. msgstr ""

  1080. 

  1081. #: ../../../CHANGELOG.md:635

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

  1083. msgstr ""

  1084. 

  1085. #: ../../../CHANGELOG.md:637

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

  1087. msgstr ""

  1088. 

  1089. #: ../../../CHANGELOG.md:640

  1090. msgid "2024-06-03"

  1091. msgstr ""

  1092. 

  1093. #: ../../../CHANGELOG.md:642

  1094. msgid "WeChat bridging support"

  1095. msgstr ""

  1096. 

  1097. #: ../../../CHANGELOG.md:644

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

  1099. msgstr ""

  1100. 

  1101. #: ../../../CHANGELOG.md:646

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

  1103. msgstr ""

  1104. 

  1105. #: ../../../CHANGELOG.md:649

  1106. msgid "2024-03-26"

  1107. msgstr ""

  1108. 

  1109. #: ../../../CHANGELOG.md:651

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

  1111. msgstr ""

  1112. 

  1113. #: ../../../CHANGELOG.md:653

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

  1115. msgstr ""

  1116. 

  1117. #: ../../../CHANGELOG.md:655

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

  1119. msgstr ""

  1120. 

  1121. #: ../../../CHANGELOG.md:657

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

  1123. msgstr ""

  1124. 

  1125. #: ../../../CHANGELOG.md:659

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

  1127. msgstr ""

  1128. 

  1129. #: ../../../CHANGELOG.md:661

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

  1131. msgstr ""

  1132. 

  1133. #: ../../../CHANGELOG.md:663

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

  1135. msgstr ""

  1136. 

  1137. #: ../../../CHANGELOG.md:674

  1138. msgid "2024-03-24"

  1139. msgstr ""

  1140. 

  1141. #: ../../../CHANGELOG.md:676

  1142. msgid "Initial work on IPv6 support"

  1143. msgstr ""

  1144. 

  1145. #: ../../../CHANGELOG.md:678

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

  1147. msgstr ""

  1148. 

  1149. #: ../../../CHANGELOG.md:680

  1150. msgid "It should be noted that:"

  1151. msgstr ""

  1152. 

  1153. #: ../../../CHANGELOG.md:682

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

  1155. msgstr ""

  1156. 

  1157. #: ../../../CHANGELOG.md:683

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

  1159. msgstr ""

  1160. 

  1161. #: ../../../CHANGELOG.md:684

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

  1163. msgstr ""

  1164. 

  1165. #: ../../../CHANGELOG.md:686

  1166. msgid "Pantalaimon support"

  1167. msgstr ""

  1168. 

  1169. #: ../../../CHANGELOG.md:688

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

  1171. msgstr ""

  1172. 

  1173. #: ../../../CHANGELOG.md:690

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

  1175. msgstr ""

  1176. 

  1177. #: ../../../CHANGELOG.md:693

  1178. msgid "2024-03-05"

  1179. msgstr ""

  1180. 

  1181. #: ../../../CHANGELOG.md:695

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

  1183. msgstr ""

  1184. 

  1185. #: ../../../CHANGELOG.md:697

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

  1187. msgstr ""

  1188. 

  1189. #: ../../../CHANGELOG.md:699

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

  1191. msgstr ""

  1192. 

  1193. #: ../../../CHANGELOG.md:701

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

  1195. msgstr ""

  1196. 

  1197. #: ../../../CHANGELOG.md:704

  1198. msgid "2024-02-19"

  1199. msgstr ""

  1200. 

  1201. #: ../../../CHANGELOG.md:706

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

  1203. msgstr ""

  1204. 

  1205. #: ../../../CHANGELOG.md:708

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

  1207. msgstr ""

  1208. 

  1209. #: ../../../CHANGELOG.md:710

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

  1211. msgstr ""

  1212. 

  1213. #: ../../../CHANGELOG.md:712

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

  1215. msgstr ""

  1216. 

  1217. #: ../../../CHANGELOG.md:714

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

  1219. msgstr ""

  1220. 

  1221. #: ../../../CHANGELOG.md:716

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

  1223. msgstr ""

  1224. 

  1225. #: ../../../CHANGELOG.md:718

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

  1227. msgstr ""

  1228. 

  1229. #: ../../../CHANGELOG.md:721

  1230. msgid "2024-02-14"

  1231. msgstr ""

  1232. 

  1233. #: ../../../CHANGELOG.md:723

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

  1235. msgstr ""

  1236. 

  1237. #: ../../../CHANGELOG.md:725

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

  1239. msgstr ""

  1240. 

  1241. #: ../../../CHANGELOG.md:727

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

  1243. msgstr ""

  1244. 

  1245. #: ../../../CHANGELOG.md:729

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

  1247. msgstr ""

  1248. 

  1249. #: ../../../CHANGELOG.md:731

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

  1251. msgstr ""

  1252. 

  1253. #: ../../../CHANGELOG.md:732

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

  1255. msgstr ""

  1256. 

  1257. #: ../../../CHANGELOG.md:733

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

  1259. msgstr ""

  1260. 

  1261. #: ../../../CHANGELOG.md:735

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

  1263. msgstr ""

  1264. 

  1265. #: ../../../CHANGELOG.md:737

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

  1267. msgstr ""

  1268. 

  1269. #: ../../../CHANGELOG.md:740

  1270. msgid "2024-01-31"

  1271. msgstr ""

  1272. 

  1273. #: ../../../CHANGELOG.md:742

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

  1275. msgstr ""

  1276. 

  1277. #: ../../../CHANGELOG.md:744

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

  1279. msgstr ""

  1280. 

  1281. #: ../../../CHANGELOG.md:746

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

  1283. msgstr ""

  1284. 

  1285. #: ../../../CHANGELOG.md:748

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

  1287. msgstr ""

  1288. 

  1289. #: ../../../CHANGELOG.md:751

  1290. msgid "2024-01-20"

  1291. msgstr ""

  1292. 

  1293. #: ../../../CHANGELOG.md:753

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

  1295. msgstr ""

  1296. 

  1297. #: ../../../CHANGELOG.md:755

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

  1299. msgstr ""

  1300. 

  1301. #: ../../../CHANGELOG.md:757

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

  1303. msgstr ""

  1304. 

  1305. #: ../../../CHANGELOG.md:759

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

  1307. msgstr ""

  1308. 

  1309. #: ../../../CHANGELOG.md:761

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

  1311. msgstr ""

  1312. 

  1313. #: ../../../CHANGELOG.md:764

  1314. msgid "2024-01-17"

  1315. msgstr ""

  1316. 

  1317. #: ../../../CHANGELOG.md:766

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

  1319. msgstr ""

  1320. 

  1321. #: ../../../CHANGELOG.md:768

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

  1323. msgstr ""

  1324. 

  1325. #: ../../../CHANGELOG.md:770

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

  1327. msgstr ""

  1328. 

  1329. #: ../../../CHANGELOG.md:771

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

  1331. msgstr ""

  1332. 

  1333. #: ../../../CHANGELOG.md:773

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

  1335. msgstr ""

  1336. 

  1337. #: ../../../CHANGELOG.md:775

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

  1339. msgstr ""

  1340. 

  1341. #: ../../../CHANGELOG.md:777

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

  1343. msgstr ""

  1344. 

  1345. #: ../../../CHANGELOG.md:779

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

  1347. msgstr ""

  1348. 

  1349. #: ../../../CHANGELOG.md:781

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

  1351. msgstr ""

  1352. 

  1353. #: ../../../CHANGELOG.md:783

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

  1355. msgstr ""

  1356. 

  1357. #: ../../../CHANGELOG.md:785

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

  1359. msgstr ""

  1360. 

  1361. #: ../../../CHANGELOG.md:787

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

  1363. msgstr ""

  1364. 

  1365. #: ../../../CHANGELOG.md:799

  1366. msgid "Notes:"

  1367. msgstr ""

  1368. 

  1369. #: ../../../CHANGELOG.md:801

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

  1371. msgstr ""

  1372. 

  1373. #: ../../../CHANGELOG.md:803

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

  1375. msgstr ""

  1376. 

  1377. #: ../../../CHANGELOG.md:805

  1378. msgid "2024-01-16"

  1379. msgstr ""

  1380. 

  1381. #: ../../../CHANGELOG.md:807

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

  1383. msgstr ""

  1384. 

  1385. #: ../../../CHANGELOG.md:809

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

  1387. msgstr ""

  1388. 

  1389. #: ../../../CHANGELOG.md:811

  1390. msgid "2024-01-15"

  1391. msgstr ""

  1392. 

  1393. #: ../../../CHANGELOG.md:813

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

  1395. msgstr ""

  1396. 

  1397. #: ../../../CHANGELOG.md:815

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

  1399. msgstr ""

  1400. 

  1401. #: ../../../CHANGELOG.md:817

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

  1403. msgstr ""

  1404. 

  1405. #: ../../../CHANGELOG.md:819

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

  1407. msgstr ""

  1408. 

  1409. #: ../../../CHANGELOG.md:821

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

  1411. msgstr ""

  1412. 

  1413. #: ../../../CHANGELOG.md:823

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

  1415. msgstr ""

  1416. 

  1417. #: ../../../CHANGELOG.md:825

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

  1419. msgstr ""

  1420. 

  1421. #: ../../../CHANGELOG.md:826

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

  1423. msgstr ""

  1424. 

  1425. #: ../../../CHANGELOG.md:827

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

  1427. msgstr ""

  1428. 

  1429. #: ../../../CHANGELOG.md:828

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

  1431. msgstr ""

  1432. 

  1433. #: ../../../CHANGELOG.md:829

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

  1435. msgstr ""

  1436. 

  1437. #: ../../../CHANGELOG.md:830

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

  1439. msgstr ""

  1440. 

  1441. #: ../../../CHANGELOG.md:831

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

  1443. msgstr ""

  1444. 

  1445. #: ../../../CHANGELOG.md:833

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

  1447. msgstr ""

  1448. 

  1449. #: ../../../CHANGELOG.md:835

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

  1451. msgstr ""

  1452. 

  1453. #: ../../../CHANGELOG.md:837

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

  1455. msgstr ""

  1456. 

  1457. #: ../../../CHANGELOG.md:839

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

  1459. msgstr ""

  1460. 

  1461. #: ../../../CHANGELOG.md:841

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

  1463. msgstr ""

  1464. 

  1465. #: ../../../CHANGELOG.md:843

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

  1467. msgstr ""

  1468. 

  1469. #: ../../../CHANGELOG.md:845

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

  1471. msgstr ""

  1472. 

  1473. #: ../../../CHANGELOG.md:847

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

  1475. msgstr ""

  1476. 

  1477. #: ../../../CHANGELOG.md:849

  1478. msgid "Traefik now has an extra job"

  1479. msgstr ""

  1480. 

  1481. #: ../../../CHANGELOG.md:851

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

  1483. msgstr ""

  1484. 

  1485. #: ../../../CHANGELOG.md:853

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

  1487. msgstr ""

  1488. 

  1489. #: ../../../CHANGELOG.md:855

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

  1491. msgstr ""

  1492. 

  1493. #: ../../../CHANGELOG.md:857

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

  1495. msgstr ""

  1496. 

  1497. #: ../../../CHANGELOG.md:859

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

  1499. msgstr ""

  1500. 

  1501. #: ../../../CHANGELOG.md:861

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

  1503. msgstr ""

  1504. 

  1505. #: ../../../CHANGELOG.md:863

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

  1507. msgstr ""

  1508. 

  1509. #: ../../../CHANGELOG.md:864

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

  1511. msgstr ""

  1512. 

  1513. #: ../../../CHANGELOG.md:866

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

  1515. msgstr ""

  1516. 

  1517. #: ../../../CHANGELOG.md:868

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

  1519. msgstr ""

  1520. 

  1521. #: ../../../CHANGELOG.md:870

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

  1523. msgstr ""

  1524. 

  1525. #: ../../../CHANGELOG.md:872

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

  1527. msgstr ""

  1528. 

  1529. #: ../../../CHANGELOG.md:874

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

  1531. msgstr ""

  1532. 

  1533. #: ../../../CHANGELOG.md:876

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

  1535. msgstr ""

  1536. 

  1537. #: ../../../CHANGELOG.md:878

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

  1539. msgstr ""

  1540. 

  1541. #: ../../../CHANGELOG.md:880

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

  1543. msgstr ""

  1544. 

  1545. #: ../../../CHANGELOG.md:882

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

  1547. msgstr ""

  1548. 

  1549. #: ../../../CHANGELOG.md:884

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

  1551. msgstr ""

  1552. 

  1553. #: ../../../CHANGELOG.md:886

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

  1555. msgstr ""

  1556. 

  1557. #: ../../../CHANGELOG.md:888

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

  1559. msgstr ""

  1560. 

  1561. #: ../../../CHANGELOG.md:890

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

  1563. msgstr ""

  1564. 

  1565. #: ../../../CHANGELOG.md:892

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

  1567. msgstr ""

  1568. 

  1569. #: ../../../CHANGELOG.md:894

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

  1571. msgstr ""

  1572. 

  1573. #: ../../../CHANGELOG.md:895

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

  1575. msgstr ""

  1576. 

  1577. #: ../../../CHANGELOG.md:896

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

  1579. msgstr ""

  1580. 

  1581. #: ../../../CHANGELOG.md:898

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

  1583. msgstr ""

  1584. 

  1585. #: ../../../CHANGELOG.md:900

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

  1587. msgstr ""

  1588. 

  1589. #: ../../../CHANGELOG.md:902

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

  1591. msgstr ""

  1592. 

  1593. #: ../../../CHANGELOG.md:904

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

  1595. msgstr ""

  1596. 

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

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

  1599. msgstr ""

  1600. 

  1601. #: ../../../CHANGELOG.md:907

  1602. msgid "Container networking changes"

  1603. msgstr ""

  1604. 

  1605. #: ../../../CHANGELOG.md:909

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

  1607. msgstr ""

  1608. 

  1609. #: ../../../CHANGELOG.md:911

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

  1611. msgstr ""

  1612. 

  1613. #: ../../../CHANGELOG.md:913

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

  1615. msgstr ""

  1616. 

  1617. #: ../../../CHANGELOG.md:915

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

  1619. msgstr ""

  1620. 

  1621. #: ../../../CHANGELOG.md:917

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

  1623. msgstr ""

  1624. 

  1625. #: ../../../CHANGELOG.md:919

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

  1627. msgstr ""

  1628. 

  1629. #: ../../../CHANGELOG.md:921

  1630. msgid "Metrics exposure changes"

  1631. msgstr ""

  1632. 

  1633. #: ../../../CHANGELOG.md:923

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

  1635. msgstr ""

  1636. 

  1637. #: ../../../CHANGELOG.md:925

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

  1639. msgstr ""

  1640. 

  1641. #: ../../../CHANGELOG.md:927

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

  1643. msgstr ""

  1644. 

  1645. #: ../../../CHANGELOG.md:929

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

  1647. msgstr ""

  1648. 

  1649. #: ../../../CHANGELOG.md:931

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

  1651. msgstr ""

  1652. 

  1653. #: ../../../CHANGELOG.md:933

  1654. msgid "Matrix static files"

  1655. msgstr ""

  1656. 

  1657. #: ../../../CHANGELOG.md:935

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

  1659. msgstr ""

  1660. 

  1661. #: ../../../CHANGELOG.md:937

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

  1663. msgstr ""

  1664. 

  1665. #: ../../../CHANGELOG.md:939

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

  1667. msgstr ""

  1668. 

  1669. #: ../../../CHANGELOG.md:941

  1670. msgid "A note on performance"

  1671. msgstr ""

  1672. 

  1673. #: ../../../CHANGELOG.md:943

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

  1675. msgstr ""

  1676. 

  1677. #: ../../../CHANGELOG.md:945

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

  1679. msgstr ""

  1680. 

  1681. #: ../../../CHANGELOG.md:947

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

  1683. msgstr ""

  1684. 

  1685. #: ../../../CHANGELOG.md:949

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

  1687. msgstr ""

  1688. 

  1689. #: ../../../CHANGELOG.md:951

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

  1691. msgstr ""

  1692. 

  1693. #: ../../../CHANGELOG.md:953

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

  1695. msgstr ""

  1696. 

  1697. #: ../../../CHANGELOG.md:955

  1698. msgid "Migration procedure"

  1699. msgstr ""

  1700. 

  1701. #: ../../../CHANGELOG.md:957

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

  1703. msgstr ""

  1704. 

  1705. #: ../../../CHANGELOG.md:959

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

  1707. msgstr ""

  1708. 

  1709. #: ../../../CHANGELOG.md:961

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

  1711. msgstr ""

  1712. 

  1713. #: ../../../CHANGELOG.md:963

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

  1715. msgstr ""

  1716. 

  1717. #: ../../../CHANGELOG.md:965

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

  1719. msgstr ""

  1720. 

  1721. #: ../../../CHANGELOG.md:967

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

  1723. msgstr ""

  1724. 

  1725. #: ../../../CHANGELOG.md:969

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

  1727. msgstr ""

  1728. 

  1729. #: ../../../CHANGELOG.md:971

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

  1731. msgstr ""

  1732. 

  1733. #: ../../../CHANGELOG.md:973

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

  1735. msgstr ""

  1736. 

  1737. #: ../../../CHANGELOG.md:975

  1738. msgid "Conclusion"

  1739. msgstr ""

  1740. 

  1741. #: ../../../CHANGELOG.md:977

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

  1743. msgstr ""

  1744. 

  1745. #: ../../../CHANGELOG.md:979

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

  1747. msgstr ""

  1748. 

  1749. #: ../../../CHANGELOG.md:982

  1750. msgid "2024-01-14"

  1751. msgstr ""

  1752. 

  1753. #: ../../../CHANGELOG.md:984

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

  1755. msgstr ""

  1756. 

  1757. #: ../../../CHANGELOG.md:986

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

  1759. msgstr ""

  1760. 

  1761. #: ../../../CHANGELOG.md:988

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

  1763. msgstr ""

  1764. 

  1765. #: ../../../CHANGELOG.md:990

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

  1767. msgstr ""

  1768. 

  1769. #: ../../../CHANGELOG.md:992

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

  1771. msgstr ""

  1772. 

  1773. #: ../../../CHANGELOG.md:994

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

  1775. msgstr ""

  1776. 

  1777. #: ../../../CHANGELOG.md:1027

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

  1779. msgstr ""

  1780. 

  1781. #: ../../../CHANGELOG.md:1030

  1782. msgid "2024-01-13"

  1783. msgstr ""

  1784. 

  1785. #: ../../../CHANGELOG.md:1032

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

  1787. msgstr ""

  1788. 

  1789. #: ../../../CHANGELOG.md:1034

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

  1791. msgstr ""

  1792. 

  1793. #: ../../../CHANGELOG.md:1036

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

  1795. msgstr ""

  1796. 

  1797. #: ../../../CHANGELOG.md:1038

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

  1799. msgstr ""

  1800. 

  1801. #: ../../../CHANGELOG.md:1040

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

  1803. msgstr ""

  1804. 

  1805. #: ../../../CHANGELOG.md:1042

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

  1807. msgstr ""

  1808. 

  1809. #: ../../../CHANGELOG.md:1044

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

  1811. msgstr ""

  1812. 

  1813. #: ../../../CHANGELOG.md:1046

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

  1815. msgstr ""

  1816. 

  1817. #: ../../../CHANGELOG.md:1048

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

  1819. msgstr ""

  1820. 

  1821. #: ../../../CHANGELOG.md:1050

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

  1823. msgstr ""

  1824. 

  1825. #: ../../../CHANGELOG.md:1053

  1826. msgid "2024-01-05"

  1827. msgstr ""

  1828. 

  1829. #: ../../../CHANGELOG.md:1055

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

  1831. msgstr ""

  1832. 

  1833. #: ../../../CHANGELOG.md:1057

  1834. #: ../../../CHANGELOG.md:1695

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

  1836. msgstr ""

  1837. 

  1838. #: ../../../CHANGELOG.md:1059

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

  1840. msgstr ""

  1841. 

  1842. #: ../../../CHANGELOG.md:1061

  1843. msgid "To migrate:"

  1844. msgstr ""

  1845. 

  1846. #: ../../../CHANGELOG.md:1063

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

  1848. msgstr ""

  1849. 

  1850. #: ../../../CHANGELOG.md:1064

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

  1852. msgstr ""

  1853. 

  1854. #: ../../../CHANGELOG.md:1065

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

  1856. msgstr ""

  1857. 

  1858. #: ../../../CHANGELOG.md:1066

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

  1860. msgstr ""

  1861. 

  1862. #: ../../../CHANGELOG.md:1068

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

  1864. msgstr ""

  1865. 

  1866. #: ../../../CHANGELOG.md:1071

  1867. msgid "2024-01-02"

  1868. msgstr ""

  1869. 

  1870. #: ../../../CHANGELOG.md:1073

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

  1872. msgstr ""

  1873. 

  1874. #: ../../../CHANGELOG.md:1075

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

  1876. msgstr ""

  1877. 

  1878. #: ../../../CHANGELOG.md:1077

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

  1880. msgstr ""

  1881. 

  1882. #: ../../../CHANGELOG.md:1079

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

  1884. msgstr ""

  1885. 

  1886. #: ../../../CHANGELOG.md:1082

  1887. msgid "2023-10-23"

  1888. msgstr ""

  1889. 

  1890. #: ../../../CHANGELOG.md:1084

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

  1892. msgstr ""

  1893. 

  1894. #: ../../../CHANGELOG.md:1086

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

  1896. msgstr ""

  1897. 

  1898. #: ../../../CHANGELOG.md:1088

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

  1900. msgstr ""

  1901. 

  1902. #: ../../../CHANGELOG.md:1090

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

  1904. msgstr ""

  1905. 

  1906. #: ../../../CHANGELOG.md:1092

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

  1908. msgstr ""

  1909. 

  1910. #: ../../../CHANGELOG.md:1094

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

  1912. msgstr ""

  1913. 

  1914. #: ../../../CHANGELOG.md:1096

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

  1916. msgstr ""

  1917. 

  1918. #: ../../../CHANGELOG.md:1098

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

  1920. msgstr ""

  1921. 

  1922. #: ../../../CHANGELOG.md:1100

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

  1924. msgstr ""

  1925. 

  1926. #: ../../../CHANGELOG.md:1102

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

  1928. msgstr ""

  1929. 

  1930. #: ../../../CHANGELOG.md:1104

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

  1932. msgstr ""

  1933. 

  1934. #: ../../../CHANGELOG.md:1106

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

  1936. msgstr ""

  1937. 

  1938. #: ../../../CHANGELOG.md:1108

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

  1940. msgstr ""

  1941. 

  1942. #: ../../../CHANGELOG.md:1110

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

  1944. msgstr ""

  1945. 

  1946. #: ../../../CHANGELOG.md:1113

  1947. msgid "2023-10-18"

  1948. msgstr ""

  1949. 

  1950. #: ../../../CHANGELOG.md:1115

  1951. msgid "Postgres parameters are automatically tuned now"

  1952. msgstr ""

  1953. 

  1954. #: ../../../CHANGELOG.md:1117

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

  1956. msgstr ""

  1957. 

  1958. #: ../../../CHANGELOG.md:1119

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

  1960. msgstr ""

  1961. 

  1962. #: ../../../CHANGELOG.md:1121

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

  1964. msgstr ""

  1965. 

  1966. #: ../../../CHANGELOG.md:1123

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

  1968. msgstr ""

  1969. 

  1970. #: ../../../CHANGELOG.md:1126

  1971. msgid "2023-08-31"

  1972. msgstr ""

  1973. 

  1974. #: ../../../CHANGELOG.md:1128

  1975. msgid "SchildiChat Web support"

  1976. msgstr ""

  1977. 

  1978. #: ../../../CHANGELOG.md:1130

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

  1980. msgstr ""

  1981. 

  1982. #: ../../../CHANGELOG.md:1132

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

  1984. msgstr ""

  1985. 

  1986. #: ../../../CHANGELOG.md:1135

  1987. msgid "2023-08-23"

  1988. msgstr ""

  1989. 

  1990. #: ../../../CHANGELOG.md:1137

  1991. msgid "mautrix-wsproxy support"

  1992. msgstr ""

  1993. 

  1994. #: ../../../CHANGELOG.md:1139

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

  1996. msgstr ""

  1997. 

  1998. #: ../../../CHANGELOG.md:1141

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

  2000. msgstr ""

  2001. 

  2002. #: ../../../CHANGELOG.md:1144

  2003. msgid "2023-07-24"

  2004. msgstr ""

  2005. 

  2006. #: ../../../CHANGELOG.md:1146

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

  2008. msgstr ""

  2009. 

  2010. #: ../../../CHANGELOG.md:1148

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

  2012. msgstr ""

  2013. 

  2014. #: ../../../CHANGELOG.md:1150

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

  2016. msgstr ""

  2017. 

  2018. #: ../../../CHANGELOG.md:1152

  2019. msgid "`matrix_bot_matrix_registration_bot_bot_access_token`"

  2020. msgstr ""

  2021. 

  2022. #: ../../../CHANGELOG.md:1153

  2023. msgid "`matrix_bot_matrix_registration_bot_api_token`"

  2024. msgstr ""

  2025. 

  2026. #: ../../../CHANGELOG.md:1156

  2027. msgid "2023-07-21"

  2028. msgstr ""

  2029. 

  2030. #: ../../../CHANGELOG.md:1158

  2031. msgid "mautrix-gmessages support"

  2032. msgstr ""

  2033. 

  2034. #: ../../../CHANGELOG.md:1160

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

  2036. msgstr ""

  2037. 

  2038. #: ../../../CHANGELOG.md:1163

  2039. msgid "2023-07-17"

  2040. msgstr ""

  2041. 

  2042. #: ../../../CHANGELOG.md:1165

  2043. msgid "matrix-media-repo support"

  2044. msgstr ""

  2045. 

  2046. #: ../../../CHANGELOG.md:1167

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

  2048. msgstr ""

  2049. 

  2050. #: ../../../CHANGELOG.md:1169

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

  2052. msgstr ""

  2053. 

  2054. #: ../../../CHANGELOG.md:1172

  2055. msgid "2023-05-25"

  2056. msgstr ""

  2057. 

  2058. #: ../../../CHANGELOG.md:1174

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

  2060. msgstr ""

  2061. 

  2062. #: ../../../CHANGELOG.md:1176

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

  2064. msgstr ""

  2065. 

  2066. #: ../../../CHANGELOG.md:1178

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

  2068. msgstr ""

  2069. 

  2070. #: ../../../CHANGELOG.md:1180

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

  2072. msgstr ""

  2073. 

  2074. #: ../../../CHANGELOG.md:1182

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

  2076. msgstr ""

  2077. 

  2078. #: ../../../CHANGELOG.md:1185

  2079. msgid "2023-04-03"

  2080. msgstr ""

  2081. 

  2082. #: ../../../CHANGELOG.md:1187

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

  2084. msgstr ""

  2085. 

  2086. #: ../../../CHANGELOG.md:1189

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

  2088. msgstr ""

  2089. 

  2090. #: ../../../CHANGELOG.md:1191

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

  2092. msgstr ""

  2093. 

  2094. #: ../../../CHANGELOG.md:1193

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

  2096. msgstr ""

  2097. 

  2098. #: ../../../CHANGELOG.md:1195

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

  2100. msgstr ""

  2101. 

  2102. #: ../../../CHANGELOG.md:1196

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

  2104. msgstr ""

  2105. 

  2106. #: ../../../CHANGELOG.md:1198

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

  2108. msgstr ""

  2109. 

  2110. #: ../../../CHANGELOG.md:1200

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

  2112. msgstr ""

  2113. 

  2114. #: ../../../CHANGELOG.md:1202

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

  2116. msgstr ""

  2117. 

  2118. #: ../../../CHANGELOG.md:1203

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

  2120. msgstr ""

  2121. 

  2122. #: ../../../CHANGELOG.md:1204

  2123. #: ../../../CHANGELOG.md:1231

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

  2125. msgstr ""

  2126. 

  2127. #: ../../../CHANGELOG.md:1206

  2128. msgid "2023-03-22"

  2129. msgstr ""

  2130. 

  2131. #: ../../../CHANGELOG.md:1208

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

  2133. msgstr ""

  2134. 

  2135. #: ../../../CHANGELOG.md:1210

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

  2137. msgstr ""

  2138. 

  2139. #: ../../../CHANGELOG.md:1212

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

  2141. msgstr ""

  2142. 

  2143. #: ../../../CHANGELOG.md:1215

  2144. msgid "2023-03-21"

  2145. msgstr ""

  2146. 

  2147. #: ../../../CHANGELOG.md:1217

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

  2149. msgstr ""

  2150. 

  2151. #: ../../../CHANGELOG.md:1219

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

  2153. msgstr ""

  2154. 

  2155. #: ../../../CHANGELOG.md:1221

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

  2157. msgstr ""

  2158. 

  2159. #: ../../../CHANGELOG.md:1223

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

  2161. msgstr ""

  2162. 

  2163. #: ../../../CHANGELOG.md:1225

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

  2165. msgstr ""

  2166. 

  2167. #: ../../../CHANGELOG.md:1227

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

  2169. msgstr ""

  2170. 

  2171. #: ../../../CHANGELOG.md:1229

  2172. msgid "`matrix_prometheus_docker_image_` -> `matrix_prometheus_container_image_`"

  2173. msgstr ""

  2174. 

  2175. #: ../../../CHANGELOG.md:1230

  2176. msgid "`matrix_prometheus_` -> `prometheus_`"

  2177. msgstr ""

  2178. 

  2179. #: ../../../CHANGELOG.md:1234

  2180. msgid "2023-03-12"

  2181. msgstr ""

  2182. 

  2183. #: ../../../CHANGELOG.md:1236

  2184. msgid "synapse-auto-compressor support"

  2185. msgstr ""

  2186. 

  2187. #: ../../../CHANGELOG.md:1238

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

  2189. msgstr ""

  2190. 

  2191. #: ../../../CHANGELOG.md:1240

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

  2193. msgstr ""

  2194. 

  2195. #: ../../../CHANGELOG.md:1242

  2196. msgid "it runs on a more up-to-date version of `rust-synapse-compress-state`"

  2197. msgstr ""

  2198. 

  2199. #: ../../../CHANGELOG.md:1243

  2200. msgid "it's a set-it-and-forget-it tool that you can enable and never have to deal with manual compression anymore"

  2201. msgstr ""

  2202. 

  2203. #: ../../../CHANGELOG.md:1245

  2204. msgid "This tool needs to be enabled manually, for now. In the future, we're considering enabling it by default for all Synapse installations."

  2205. msgstr ""

  2206. 

  2207. #: ../../../CHANGELOG.md:1247

  2208. msgid "See our [Setting up synapse-auto-compressor](docs/configuring-playbook-synapse-auto-compressor.md) documentation to get started."

  2209. msgstr ""

  2210. 

  2211. #: ../../../CHANGELOG.md:1250

  2212. msgid "2023-03-07"

  2213. msgstr ""

  2214. 

  2215. #: ../../../CHANGELOG.md:1252

  2216. msgid "Sliding Sync proxy (Element X) support"

  2217. msgstr ""

  2218. 

  2219. #: ../../../CHANGELOG.md:1254

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

  2221. msgstr ""

  2222. 

  2223. #: ../../../CHANGELOG.md:1256

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

  2225. msgstr ""

  2226. 

  2227. #: ../../../CHANGELOG.md:1258

  2228. msgid "To get started, see our [Setting up the Sliding Sync proxy](docs/configuring-playbook-sliding-sync-proxy.md) documentation page."

  2229. msgstr ""

  2230. 

  2231. #: ../../../CHANGELOG.md:1261

  2232. msgid "2023-03-02"

  2233. msgstr ""

  2234. 

  2235. #: ../../../CHANGELOG.md:1263

  2236. msgid "The matrix-etherpad role lives independently now"

  2237. msgstr ""

  2238. 

  2239. #: ../../../CHANGELOG.md:1265

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

  2241. msgstr ""

  2242. 

  2243. #: ../../../CHANGELOG.md:1267

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

  2245. msgstr ""

  2246. 

  2247. #: ../../../CHANGELOG.md:1269

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

  2249. msgstr ""

  2250. 

  2251. #: ../../../CHANGELOG.md:1271

  2252. msgid "Rename `matrix_etherpad_public_endpoint` to `etherpad_path_prefix`"

  2253. msgstr ""

  2254. 

  2255. #: ../../../CHANGELOG.md:1273

  2256. msgid "Replace `matrix_etherpad_mode: dimension` with:"

  2257. msgstr ""

  2258. 

  2259. #: ../../../CHANGELOG.md:1274

  2260. msgid "for `matrix-nginx-proxy` users:"

  2261. msgstr ""

  2262. 

  2263. #: ../../../CHANGELOG.md:1275

  2264. msgid "`etherpad_nginx_proxy_dimension_integration_enabled: true`"

  2265. msgstr ""

  2266. 

  2267. #: ../../../CHANGELOG.md:1276

  2268. msgid "`etherpad_hostname: \"{{ matrix_server_fqn_dimension }}\"`"

  2269. msgstr ""

  2270. 

  2271. #: ../../../CHANGELOG.md:1277

  2272. msgid "for Traefik users:"

  2273. msgstr ""

  2274. 

  2275. #: ../../../CHANGELOG.md:1278

  2276. msgid "define your own `etherpad_hostname` and `etherpad_path_prefix` as you see fit"

  2277. msgstr ""

  2278. 

  2279. #: ../../../CHANGELOG.md:1280

  2280. msgid "Rename all other variables:"

  2281. msgstr ""

  2282. 

  2283. #: ../../../CHANGELOG.md:1281

  2284. msgid "`matrix_etherpad_docker_image_` -> `matrix_etherpad_container_image_`"

  2285. msgstr ""

  2286. 

  2287. #: ../../../CHANGELOG.md:1282

  2288. msgid "`matrix_etherpad_` -> `etherpad_`"

  2289. msgstr ""

  2290. 

  2291. #: ../../../CHANGELOG.md:1284

  2292. msgid "Along with this relocation, the new role also:"

  2293. msgstr ""

  2294. 

  2295. #: ../../../CHANGELOG.md:1286

  2296. msgid "supports [self-building](docs/self-building.md), so it should work on `arm32` and `arm64` architectures"

  2297. msgstr ""

  2298. 

  2299. #: ../../../CHANGELOG.md:1287

  2300. msgid "has native Traefik reverse-proxy support (Etherpad requests no longer go through `matrix-nginx-proxy` when using Traefik)"

  2301. msgstr ""

  2302. 

  2303. #: ../../../CHANGELOG.md:1290

  2304. msgid "2023-02-26"

  2305. msgstr ""

  2306. 

  2307. #: ../../../CHANGELOG.md:1292

  2308. msgid "Traefik is the default reverse-proxy now"

  2309. msgstr ""

  2310. 

  2311. #: ../../../CHANGELOG.md:1294

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

  2313. msgstr ""

  2314. 

  2315. #: ../../../CHANGELOG.md:1296

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

  2317. msgstr ""

  2318. 

  2319. #: ../../../CHANGELOG.md:1298

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

  2321. msgstr ""

  2322. 

  2323. #: ../../../CHANGELOG.md:1300

  2324. msgid "Traefik managed by the playbook"

  2325. msgstr ""

  2326. 

  2327. #: ../../../CHANGELOG.md:1301

  2328. msgid "Traefik managed by the user in another way"

  2329. msgstr ""

  2330. 

  2331. #: ../../../CHANGELOG.md:1302

  2332. msgid "another reverse-proxy on the same host (`127.0.0.1` port exposure)"

  2333. msgstr ""

  2334. 

  2335. #: ../../../CHANGELOG.md:1303

  2336. msgid "another reverse-proxy on another host (`0.0.0.0` port exposure)"

  2337. msgstr ""

  2338. 

  2339. #: ../../../CHANGELOG.md:1304

  2340. msgid "`matrix-nginx-proxy` — an `nginx` container managed by the playbook"

  2341. msgstr ""

  2342. 

  2343. #: ../../../CHANGELOG.md:1305

  2344. msgid "`nginx` webserver operated by the user, running without a container on the same server"

  2345. msgstr ""

  2346. 

  2347. #: ../../../CHANGELOG.md:1307

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

  2349. msgstr ""

  2350. 

  2351. #: ../../../CHANGELOG.md:1309

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

  2353. msgstr ""

  2354. 

  2355. #: ../../../CHANGELOG.md:1311

  2356. msgid "It's time for the **next step in our migration process** to Traefik and elimination of `matrix-nginx-proxy`:"

  2357. msgstr ""

  2358. 

  2359. #: ../../../CHANGELOG.md:1313

  2360. msgid "Traefik is now the default reverse-proxy for new installations"

  2361. msgstr ""

  2362. 

  2363. #: ../../../CHANGELOG.md:1314

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

  2365. msgstr ""

  2366. 

  2367. #: ../../../CHANGELOG.md:1316

  2368. msgid "How do I switch my existing setup to Traefik?"

  2369. msgstr ""

  2370. 

  2371. #: ../../../CHANGELOG.md:1318

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

  2373. msgstr ""

  2374. 

  2375. #: ../../../CHANGELOG.md:1320

  2376. msgid "If you experience trouble:"

  2377. msgstr ""

  2378. 

  2379. #: ../../../CHANGELOG.md:1322

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

  2381. msgstr ""

  2382. 

  2383. #: ../../../CHANGELOG.md:1323

  2384. msgid "Ask for help in our [support channels](README.md#support)"

  2385. msgstr ""

  2386. 

  2387. #: ../../../CHANGELOG.md:1324

  2388. msgid "Try switching to Traefik again later"

  2389. msgstr ""

  2390. 

  2391. #: ../../../CHANGELOG.md:1326

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

  2393. msgstr ""

  2394. 

  2395. #: ../../../CHANGELOG.md:1328

  2396. msgid "I already use my own Traefik server. How do I plug that in?"

  2397. msgstr ""

  2398. 

  2399. #: ../../../CHANGELOG.md:1330

  2400. msgid "See the [Traefik managed by the playbook](docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) section."

  2401. msgstr ""

  2402. 

  2403. #: ../../../CHANGELOG.md:1332

  2404. msgid "Why is matrix-nginx-proxy used even after switching to Traefik?"

  2405. msgstr ""

  2406. 

  2407. #: ../../../CHANGELOG.md:1334

  2408. msgid "This playbook manages many different services. All these services were initially integrated with `matrix-nginx-proxy`."

  2409. msgstr ""

  2410. 

  2411. #: ../../../CHANGELOG.md:1336

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

  2413. msgstr ""

  2414. 

  2415. #: ../../../CHANGELOG.md:1338

  2416. msgid "How do I remain on matrix-nginx-proxy?"

  2417. msgstr ""

  2418. 

  2419. #: ../../../CHANGELOG.md:1340

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

  2421. msgstr ""

  2422. 

  2423. #: ../../../CHANGELOG.md:1342

  2424. msgid "To proceed regardless of this warning, add `matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your configuration."

  2425. msgstr ""

  2426. 

  2427. #: ../../../CHANGELOG.md:1344

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

  2429. msgstr ""

  2430. 

  2431. #: ../../../CHANGELOG.md:1346

  2432. msgid "How do I keep using my own other reverse-proxy?"

  2433. msgstr ""

  2434. 

  2435. #: ../../../CHANGELOG.md:1348

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

  2437. msgstr ""

  2438. 

  2439. #: ../../../CHANGELOG.md:1351

  2440. msgid "2023-02-25"

  2441. msgstr ""

  2442. 

  2443. #: ../../../CHANGELOG.md:1353

  2444. msgid "rageshake support"

  2445. msgstr ""

  2446. 

  2447. #: ../../../CHANGELOG.md:1355

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

  2449. msgstr ""

  2450. 

  2451. #: ../../../CHANGELOG.md:1357

  2452. msgid "Additional details are available in [Setting up rageshake](docs/configuring-playbook-rageshake.md)."

  2453. msgstr ""

  2454. 

  2455. #: ../../../CHANGELOG.md:1360

  2456. msgid "2023-02-17"

  2457. msgstr ""

  2458. 

  2459. #: ../../../CHANGELOG.md:1362

  2460. msgid "Synapse templates customization support"

  2461. msgstr ""

  2462. 

  2463. #: ../../../CHANGELOG.md:1364

  2464. msgid "The playbook can now help you customize Synapse's templates."

  2465. msgstr ""

  2466. 

  2467. #: ../../../CHANGELOG.md:1366

  2468. msgid "Additional details are available in the [Customizing templates](docs/configuring-playbook-synapse.md#customizing-templates) section of our Synapse documentation."

  2469. msgstr ""

  2470. 

  2471. #: ../../../CHANGELOG.md:1368

  2472. msgid "The matrix-redis role lives independently now"

  2473. msgstr ""

  2474. 

  2475. #: ../../../CHANGELOG.md:1370

  2476. msgid "**TLDR**: the `matrix-redis` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  2477. msgstr ""

  2478. 

  2479. #: ../../../CHANGELOG.md:1372

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

  2481. msgstr ""

  2482. 

  2483. #: ../../../CHANGELOG.md:1374

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

  2485. msgstr ""

  2486. 

  2487. #: ../../../CHANGELOG.md:1376

  2488. msgid "The matrix-ntfy role lives independently now"

  2489. msgstr ""

  2490. 

  2491. #: ../../../CHANGELOG.md:1378

  2492. msgid "**TLDR**: the `matrix-ntfy` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  2493. msgstr ""

  2494. 

  2495. #: ../../../CHANGELOG.md:1380

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

  2497. msgstr ""

  2498. 

  2499. #: ../../../CHANGELOG.md:1382

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

  2501. msgstr ""

  2502. 

  2503. #: ../../../CHANGELOG.md:1385

  2504. msgid "2023-02-15"

  2505. msgstr ""

  2506. 

  2507. #: ../../../CHANGELOG.md:1387

  2508. msgid "The matrix-grafana role lives independently now"

  2509. msgstr ""

  2510. 

  2511. #: ../../../CHANGELOG.md:1389

  2512. msgid "**TLDR**: the `matrix-grafana` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  2513. msgstr ""

  2514. 

  2515. #: ../../../CHANGELOG.md:1391

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

  2517. msgstr ""

  2518. 

  2519. #: ../../../CHANGELOG.md:1393

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

  2521. msgstr ""

  2522. 

  2523. #: ../../../CHANGELOG.md:1396

  2524. msgid "2023-02-13"

  2525. msgstr ""

  2526. 

  2527. #: ../../../CHANGELOG.md:1398

  2528. msgid "The matrix-backup-borg role lives independently now"

  2529. msgstr ""

  2530. 

  2531. #: ../../../CHANGELOG.md:1400

  2532. msgid "**TLDR**: the `matrix-backup-borg` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  2533. msgstr ""

  2534. 

  2535. #: ../../../CHANGELOG.md:1402

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

  2537. msgstr ""

  2538. 

  2539. #: ../../../CHANGELOG.md:1404

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

  2541. msgstr ""

  2542. 

  2543. #: ../../../CHANGELOG.md:1407

  2544. msgid "2023-02-12"

  2545. msgstr ""

  2546. 

  2547. #: ../../../CHANGELOG.md:1409

  2548. msgid "(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support"

  2549. msgstr ""

  2550. 

  2551. #: ../../../CHANGELOG.md:1411

  2552. msgid "**TLDR**:"

  2553. msgstr ""

  2554. 

  2555. #: ../../../CHANGELOG.md:1413

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

  2557. msgstr ""

  2558. 

  2559. #: ../../../CHANGELOG.md:1414

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

  2561. msgstr ""

  2562. 

  2563. #: ../../../CHANGELOG.md:1415

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

  2565. msgstr ""

  2566. 

  2567. #: ../../../CHANGELOG.md:1416

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

  2569. msgstr ""

  2570. 

  2571. #: ../../../CHANGELOG.md:1417

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

  2573. msgstr ""

  2574. 

  2575. #: ../../../CHANGELOG.md:1419

  2576. msgid "Motivation for redoing our reverse-proxy setup"

  2577. msgstr ""

  2578. 

  2579. #: ../../../CHANGELOG.md:1421

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

  2581. msgstr ""

  2582. 

  2583. #: ../../../CHANGELOG.md:1423

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

  2585. msgstr ""

  2586. 

  2587. #: ../../../CHANGELOG.md:1425

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

  2589. msgstr ""

  2590. 

  2591. #: ../../../CHANGELOG.md:1427

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

  2593. msgstr ""

  2594. 

  2595. #: ../../../CHANGELOG.md:1429

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

  2597. msgstr ""

  2598. 

  2599. #: ../../../CHANGELOG.md:1431

  2600. msgid "*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined with exposing services manually (setting `_bind_port` variables)"

  2601. msgstr ""

  2602. 

  2603. #: ../../../CHANGELOG.md:1432

  2604. msgid "*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in `http`-only mode (no SSL certificate retrieval)."

  2605. msgstr ""

  2606. 

  2607. #: ../../../CHANGELOG.md:1434

  2608. msgid "Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations."

  2609. msgstr ""

  2610. 

  2611. #: ../../../CHANGELOG.md:1436

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

  2613. msgstr ""

  2614. 

  2615. #: ../../../CHANGELOG.md:1438

  2616. msgid "The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks:"

  2617. msgstr ""

  2618. 

  2619. #: ../../../CHANGELOG.md:1440

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

  2621. msgstr ""

  2622. 

  2623. #: ../../../CHANGELOG.md:1441

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

  2625. msgstr ""

  2626. 

  2627. #: ../../../CHANGELOG.md:1442

  2628. msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) — for hosting the [Nextcloud](https://nextcloud.com/) groupware platform"

  2629. msgstr ""

  2630. 

  2631. #: ../../../CHANGELOG.md:1444

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

  2633. msgstr ""

  2634. 

  2635. #: ../../../CHANGELOG.md:1446

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

  2637. msgstr ""

  2638. 

  2639. #: ../../../CHANGELOG.md:1448

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

  2641. msgstr ""

  2642. 

  2643. #: ../../../CHANGELOG.md:1450

  2644. msgid "How do these changes fix all these problems?"

  2645. msgstr ""

  2646. 

  2647. #: ../../../CHANGELOG.md:1452

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

  2649. msgstr ""

  2650. 

  2651. #: ../../../CHANGELOG.md:1454

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

  2653. msgstr ""

  2654. 

  2655. #: ../../../CHANGELOG.md:1456

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

  2657. msgstr ""

  2658. 

  2659. #: ../../../CHANGELOG.md:1458

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

  2661. msgstr ""

  2662. 

  2663. #: ../../../CHANGELOG.md:1460

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

  2665. msgstr ""

  2666. 

  2667. #: ../../../CHANGELOG.md:1462

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

  2669. msgstr ""

  2670. 

  2671. #: ../../../CHANGELOG.md:1464

  2672. msgid "Where we're at right now?"

  2673. msgstr ""

  2674. 

  2675. #: ../../../CHANGELOG.md:1466

  2676. msgid "`matrix_playbook_reverse_proxy_type` still defaults to a value of `playbook-managed-nginx`."

  2677. msgstr ""

  2678. 

  2679. #: ../../../CHANGELOG.md:1468

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

  2681. msgstr ""

  2682. 

  2683. #: ../../../CHANGELOG.md:1470

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

  2685. msgstr ""

  2686. 

  2687. #: ../../../CHANGELOG.md:1472

  2688. msgid "How do I explicitly switch to Traefik right now?"

  2689. msgstr ""

  2690. 

  2691. #: ../../../CHANGELOG.md:1474

  2692. msgid "**Users who wish to migrate to Traefik** today, can do so by **adding** this to their configuration:"

  2693. msgstr ""

  2694. 

  2695. #: ../../../CHANGELOG.md:1480

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

  2697. msgstr ""

  2698. 

  2699. #: ../../../CHANGELOG.md:1482

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

  2701. msgstr ""

  2702. 

  2703. #: ../../../CHANGELOG.md:1484

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

  2705. msgstr ""

  2706. 

  2707. #: ../../../CHANGELOG.md:1486

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

  2709. msgstr ""

  2710. 

  2711. #: ../../../CHANGELOG.md:1488

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

  2713. msgstr ""

  2714. 

  2715. #: ../../../CHANGELOG.md:1490

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

  2717. msgstr ""

  2718. 

  2719. #: ../../../CHANGELOG.md:1492

  2720. msgid "Where we're going in the near future?"

  2721. msgstr ""

  2722. 

  2723. #: ../../../CHANGELOG.md:1494

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

  2725. msgstr ""

  2726. 

  2727. #: ../../../CHANGELOG.md:1496

  2728. msgid "For now, `matrix-nginx-proxy` will stay around."

  2729. msgstr ""

  2730. 

  2731. #: ../../../CHANGELOG.md:1498

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

  2733. msgstr ""

  2734. 

  2735. #: ../../../CHANGELOG.md:1500

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

  2737. msgstr ""

  2738. 

  2739. #: ../../../CHANGELOG.md:1502

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

  2741. msgstr ""

  2742. 

  2743. #: ../../../CHANGELOG.md:1503

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

  2745. msgstr ""

  2746. 

  2747. #: ../../../CHANGELOG.md:1505

  2748. msgid "How do I help?"

  2749. msgstr ""

  2750. 

  2751. #: ../../../CHANGELOG.md:1507

  2752. msgid "You can help by:"

  2753. msgstr ""

  2754. 

  2755. #: ../../../CHANGELOG.md:1509

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

  2757. msgstr ""

  2758. 

  2759. #: ../../../CHANGELOG.md:1511

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

  2761. msgstr ""

  2762. 

  2763. #: ../../../CHANGELOG.md:1513

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

  2765. msgstr ""

  2766. 

  2767. #: ../../../CHANGELOG.md:1516

  2768. msgid "2023-02-10"

  2769. msgstr ""

  2770. 

  2771. #: ../../../CHANGELOG.md:1518

  2772. msgid "Matrix Authentication Support for Jitsi"

  2773. msgstr ""

  2774. 

  2775. #: ../../../CHANGELOG.md:1520

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

  2777. msgstr ""

  2778. 

  2779. #: ../../../CHANGELOG.md:1522

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

  2781. msgstr ""

  2782. 

  2783. #: ../../../CHANGELOG.md:1524

  2784. msgid "Draupnir moderation tool (bot) support"

  2785. msgstr ""

  2786. 

  2787. #: ../../../CHANGELOG.md:1526

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

  2789. msgstr ""

  2790. 

  2791. #: ../../../CHANGELOG.md:1528

  2792. msgid "Additional details are available in [Setting up Draupnir](docs/configuring-playbook-bot-draupnir.md)."

  2793. msgstr ""

  2794. 

  2795. #: ../../../CHANGELOG.md:1531

  2796. msgid "2023-02-05"

  2797. msgstr ""

  2798. 

  2799. #: ../../../CHANGELOG.md:1533

  2800. msgid "The matrix-prometheus-postgres-exporter role lives independently now"

  2801. msgstr ""

  2802. 

  2803. #: ../../../CHANGELOG.md:1535

  2804. msgid "**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  2805. msgstr ""

  2806. 

  2807. #: ../../../CHANGELOG.md:1537

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

  2809. msgstr ""

  2810. 

  2811. #: ../../../CHANGELOG.md:1539

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

  2813. msgstr ""

  2814. 

  2815. #: ../../../CHANGELOG.md:1541

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

  2817. msgstr ""

  2818. 

  2819. #: ../../../CHANGELOG.md:1543

  2820. #: ../../../CHANGELOG.md:1585

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

  2822. msgstr ""

  2823. 

  2824. #: ../../../CHANGELOG.md:1546

  2825. msgid "2023-01-26"

  2826. msgstr ""

  2827. 

  2828. #: ../../../CHANGELOG.md:1548

  2829. msgid "coturn can now use host-networking"

  2830. msgstr ""

  2831. 

  2832. #: ../../../CHANGELOG.md:1550

  2833. msgid "Large coturn deployments (with a huge range of ports specified via `matrix_coturn_turn_udp_min_port` and `matrix_coturn_turn_udp_max_port`) experience a huge slowdown with how Docker publishes all these ports (setting up firewall forwarding rules), which leads to a very slow coturn service startup and shutdown."

  2834. msgstr ""

  2835. 

  2836. #: ../../../CHANGELOG.md:1552

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

  2838. msgstr ""

  2839. 

  2840. #: ../../../CHANGELOG.md:1558

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

  2842. msgstr ""

  2843. 

  2844. #: ../../../CHANGELOG.md:1560

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

  2846. msgstr ""

  2847. 

  2848. #: ../../../CHANGELOG.md:1562

  2849. msgid "(Backward Compatibility) Tightening coturn security can lead to connectivity issues"

  2850. msgstr ""

  2851. 

  2852. #: ../../../CHANGELOG.md:1564

  2853. msgid "**TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default coturn blocklists. They may need to override `matrix_coturn_denied_peer_ips` and remove some IP ranges from it."

  2854. msgstr ""

  2855. 

  2856. #: ../../../CHANGELOG.md:1566

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

  2858. msgstr ""

  2859. 

  2860. #: ../../../CHANGELOG.md:1568

  2861. msgid "If you access your Matrix server from a local network and need coturn to relay to private IP addresses, you may observe that relaying is now blocked due to our new default `denied-peer-ip` lists (specified in `matrix_coturn_denied_peer_ips`). If you experience such connectivity problems, consider overriding this setting in your `vars.yml` file and removing certain networks from it."

  2862. msgstr ""

  2863. 

  2864. #: ../../../CHANGELOG.md:1570

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

  2866. msgstr ""

  2867. 

  2868. #: ../../../CHANGELOG.md:1573

  2869. msgid "2023-01-21"

  2870. msgstr ""

  2871. 

  2872. #: ../../../CHANGELOG.md:1575

  2873. msgid "The matrix-prometheus-node-exporter role lives independently now"

  2874. msgstr ""

  2875. 

  2876. #: ../../../CHANGELOG.md:1577

  2877. msgid "**TLDR**: the `matrix-prometheus-node-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."

  2878. msgstr ""

  2879. 

  2880. #: ../../../CHANGELOG.md:1579

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

  2882. msgstr ""

  2883. 

  2884. #: ../../../CHANGELOG.md:1581

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

  2886. msgstr ""

  2887. 

  2888. #: ../../../CHANGELOG.md:1583

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

  2890. msgstr ""

  2891. 

  2892. #: ../../../CHANGELOG.md:1588

  2893. msgid "2023-01-13"

  2894. msgstr ""

  2895. 

  2896. #: ../../../CHANGELOG.md:1590

  2897. msgid "Support for running commands via just"

  2898. msgstr ""

  2899. 

  2900. #: ../../../CHANGELOG.md:1592

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

  2902. msgstr ""

  2903. 

  2904. #: ../../../CHANGELOG.md:1594

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

  2906. msgstr ""

  2907. 

  2908. #: ../../../CHANGELOG.md:1596

  2909. msgid "Our [justfile](justfile) already defines some additional helpful **shortcut** commands that weren't part of our `Makefile`. Here are some examples:"

  2910. msgstr ""

  2911. 

  2912. #: ../../../CHANGELOG.md:1598

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

  2914. msgstr ""

  2915. 

  2916. #: ../../../CHANGELOG.md:1599

  2917. msgid "`just install-all --ask-vault-pass` — commands also support additional arguments (`--ask-vault-pass` will be appended to the above installation command)"

  2918. msgstr ""

  2919. 

  2920. #: ../../../CHANGELOG.md:1600

  2921. msgid "`just run-tags install-mautrix-slack,start` — to run specific playbook tags"

  2922. msgstr ""

  2923. 

  2924. #: ../../../CHANGELOG.md:1601

  2925. msgid "`just start-all` — (re-)starts all services"

  2926. msgstr ""

  2927. 

  2928. #: ../../../CHANGELOG.md:1602

  2929. msgid "`just stop-group postgres` — to stop only the Postgres service"

  2930. msgstr ""

  2931. 

  2932. #: ../../../CHANGELOG.md:1603

  2933. msgid "`just register-user alice secret-password yes` — registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)"

  2934. msgstr ""

  2935. 

  2936. #: ../../../CHANGELOG.md:1605

  2937. msgid "Additional helpful commands and shortcuts may be defined in the future."

  2938. msgstr ""

  2939. 

  2940. #: ../../../CHANGELOG.md:1607

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

  2942. msgstr ""

  2943. 

  2944. #: ../../../CHANGELOG.md:1610

  2945. msgid "2023-01-11"

  2946. msgstr ""

  2947. 

  2948. #: ../../../CHANGELOG.md:1612

  2949. msgid "mautrix-slack support"

  2950. msgstr ""

  2951. 

  2952. #: ../../../CHANGELOG.md:1614

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

  2954. msgstr ""

  2955. 

  2956. #: ../../../CHANGELOG.md:1616

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

  2958. msgstr ""

  2959. 

  2960. #: ../../../CHANGELOG.md:1619

  2961. msgid "2023-01-10"

  2962. msgstr ""

  2963. 

  2964. #: ../../../CHANGELOG.md:1621

  2965. msgid "ChatGPT support"

  2966. msgstr ""

  2967. 

  2968. #: ../../../CHANGELOG.md:1623

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

  2970. msgstr ""

  2971. 

  2972. #: ../../../CHANGELOG.md:1625

  2973. msgid "See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-chatgpt.md) documentation to get started."

  2974. msgstr ""

  2975. 

  2976. #: ../../../CHANGELOG.md:1628

  2977. msgid "2022-11-30"

  2978. msgstr ""

  2979. 

  2980. #: ../../../CHANGELOG.md:1630

  2981. msgid "matrix-postgres-backup has been replaced by the ansible-role-postgres-backup external role"

  2982. msgstr ""

  2983. 

  2984. #: ../../../CHANGELOG.md:1632

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

  2986. msgstr ""

  2987. 

  2988. #: ../../../CHANGELOG.md:1634

  2989. msgid "You'll need to rename your `matrix_postgres_backup`-prefixed variables such that they use a `postgres_backup` prefix."

  2990. msgstr ""

  2991. 

  2992. #: ../../../CHANGELOG.md:1637

  2993. msgid "2022-11-28"

  2994. msgstr ""

  2995. 

  2996. #: ../../../CHANGELOG.md:1639

  2997. msgid "matrix-postgres has been replaced by the ansible-role-postgres external role"

  2998. msgstr ""

  2999. 

  3000. #: ../../../CHANGELOG.md:1641

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

  3002. msgstr ""

  3003. 

  3004. #: ../../../CHANGELOG.md:1643

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

  3006. msgstr ""

  3007. 

  3008. #: ../../../CHANGELOG.md:1645

  3009. msgid "The new role is an upgraded version of the old `matrix-postgres` role with these notable differences:"

  3010. msgstr ""

  3011. 

  3012. #: ../../../CHANGELOG.md:1647

  3013. msgid "it uses different names for its variables (`matrix_postgres` -> `devture_postgres`)"

  3014. msgstr ""

  3015. 

  3016. #: ../../../CHANGELOG.md:1648

  3017. msgid "when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-postgresql), it will vacuum all your databases, not just the Synapse one"

  3018. msgstr ""

  3019. 

  3020. #: ../../../CHANGELOG.md:1650

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

  3022. msgstr ""

  3023. 

  3024. #: ../../../CHANGELOG.md:1652

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

  3026. msgstr ""

  3027. 

  3028. #: ../../../CHANGELOG.md:1654

  3029. msgid "The playbook no longer installs scripts to /usr/local/bin"

  3030. msgstr ""

  3031. 

  3032. #: ../../../CHANGELOG.md:1656

  3033. msgid "The locations of various scripts installed by the playbook have changed."

  3034. msgstr ""

  3035. 

  3036. #: ../../../CHANGELOG.md:1658

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

  3038. msgstr ""

  3039. 

  3040. #: ../../../CHANGELOG.md:1660

  3041. msgid "`/usr/local/bin/matrix-remove-all` -> `/matrix/bin/remove-all`"

  3042. msgstr ""

  3043. 

  3044. #: ../../../CHANGELOG.md:1661

  3045. msgid "`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`"

  3046. msgstr ""

  3047. 

  3048. #: ../../../CHANGELOG.md:1662

  3049. msgid "`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> `/matrix/ssl/bin/lets-encrypt-certificates-renew`"

  3050. msgstr ""

  3051. 

  3052. #: ../../../CHANGELOG.md:1663

  3053. msgid "`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin/register-user`"

  3054. msgstr ""

  3055. 

  3056. #: ../../../CHANGELOG.md:1666

  3057. msgid "2022-11-25"

  3058. msgstr ""

  3059. 

  3060. #: ../../../CHANGELOG.md:1668

  3061. msgid "2x-5x performance improvements in playbook runtime"

  3062. msgstr ""

  3063. 

  3064. #: ../../../CHANGELOG.md:1670

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

  3066. msgstr ""

  3067. 

  3068. #: ../../../CHANGELOG.md:1672

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

  3070. msgstr ""

  3071. 

  3072. #: ../../../CHANGELOG.md:1674

  3073. msgid "Even when running `ansible-playbook` manually (as most of us here do), it's beneficial not to waste time and CPU resources."

  3074. msgstr ""

  3075. 

  3076. #: ../../../CHANGELOG.md:1676

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

  3078. msgstr ""

  3079. 

  3080. #: ../../../CHANGELOG.md:1678

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

  3082. msgstr ""

  3083. 

  3084. #: ../../../CHANGELOG.md:1680

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

  3086. msgstr ""

  3087. 

  3088. #: ../../../CHANGELOG.md:1682

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

  3090. msgstr ""

  3091. 

  3092. #: ../../../CHANGELOG.md:1684

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

  3094. msgstr ""

  3095. 

  3096. #: ../../../CHANGELOG.md:1687

  3097. msgid "2022-11-22"

  3098. msgstr ""

  3099. 

  3100. #: ../../../CHANGELOG.md:1689

  3101. msgid "Automatic `matrix_architecture` determination"

  3102. msgstr ""

  3103. 

  3104. #: ../../../CHANGELOG.md:1691

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

  3106. msgstr ""

  3107. 

  3108. #: ../../../CHANGELOG.md:1693

  3109. msgid "Docker and the Docker SDK for Python are now installed via external roles"

  3110. msgstr ""

  3111. 

  3112. #: ../../../CHANGELOG.md:1697

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

  3114. msgstr ""

  3115. 

  3116. #: ../../../CHANGELOG.md:1699

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

  3118. msgstr ""

  3119. 

  3120. #: ../../../CHANGELOG.md:1701

  3121. msgid "If you're hitting issues with Docker installation or Docker SDK for Python installation, consider reporting bugs or contributing to these other projects."

  3122. msgstr ""

  3123. 

  3124. #: ../../../CHANGELOG.md:1703

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

  3126. msgstr ""

  3127. 

  3128. #: ../../../CHANGELOG.md:1706

  3129. msgid "2022-11-20"

  3130. msgstr ""

  3131. 

  3132. #: ../../../CHANGELOG.md:1708

  3133. msgid "(Backward Compatibility Break) Changing how reverse-proxying to Synapse works — now via a `matrix-synapse-reverse-proxy-companion` service"

  3134. msgstr ""

  3135. 

  3136. #: ../../../CHANGELOG.md:1710

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

  3138. msgstr ""

  3139. 

  3140. #: ../../../CHANGELOG.md:1712

  3141. msgid "Background"

  3142. msgstr ""

  3143. 

  3144. #: ../../../CHANGELOG.md:1714

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

  3146. msgstr ""

  3147. 

  3148. #: ../../../CHANGELOG.md:1716

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

  3150. msgstr ""

  3151. 

  3152. #: ../../../CHANGELOG.md:1718

  3153. msgid "Solution"

  3154. msgstr ""

  3155. 

  3156. #: ../../../CHANGELOG.md:1720

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

  3158. msgstr ""

  3159. 

  3160. #: ../../../CHANGELOG.md:1722

  3161. msgid "serve as a companion to Synapse and know how to reverse-proxy to Synapse correctly (no matter if workers are enabled or not)"

  3162. msgstr ""

  3163. 

  3164. #: ../../../CHANGELOG.md:1724

  3165. msgid "provide a unified container address for reaching Synapse (no matter if workers are enabled or not)"

  3166. msgstr ""

  3167. 

  3168. #: ../../../CHANGELOG.md:1725

  3169. msgid "`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server API traffic"

  3170. msgstr ""

  3171. 

  3172. #: ../../../CHANGELOG.md:1726

  3173. msgid "`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server (Federation) API traffic"

  3174. msgstr ""

  3175. 

  3176. #: ../../../CHANGELOG.md:1728

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

  3178. msgstr ""

  3179. 

  3180. #: ../../../CHANGELOG.md:1730

  3181. msgid "allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is disabled"

  3182. msgstr ""

  3183. 

  3184. #: ../../../CHANGELOG.md:1732

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

  3186. msgstr ""

  3187. 

  3188. #: ../../../CHANGELOG.md:1734

  3189. msgid "(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> (`matrix-synapse` or some Synapse worker))."

  3190. msgstr ""

  3191. 

  3192. #: ../../../CHANGELOG.md:1736

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

  3194. msgstr ""

  3195. 

  3196. #: ../../../CHANGELOG.md:1738

  3197. msgid "Webserver configuration"

  3198. msgstr ""

  3199. 

  3200. #: ../../../CHANGELOG.md:1740

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

  3202. msgstr ""

  3203. 

  3204. #: ../../../CHANGELOG.md:1742

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

  3206. msgstr ""

  3207. 

  3208. #: ../../../CHANGELOG.md:1744

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

  3210. msgstr ""

  3211. 

  3212. #: ../../../CHANGELOG.md:1746

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

  3214. msgstr ""

  3215. 

  3216. #: ../../../CHANGELOG.md:1748

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

  3218. msgstr ""

  3219. 

  3220. #: ../../../CHANGELOG.md:1751

  3221. msgid "2022-11-05"

  3222. msgstr ""

  3223. 

  3224. #: ../../../CHANGELOG.md:1753

  3225. msgid "(Backward Compatibility Break) A new default standalone mode for Etherpad"

  3226. msgstr ""

  3227. 

  3228. #: ../../../CHANGELOG.md:1755

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

  3230. msgstr ""

  3231. 

  3232. #: ../../../CHANGELOG.md:1757

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

  3234. msgstr ""

  3235. 

  3236. #: ../../../CHANGELOG.md:1759

  3237. msgid "If you've already got both Etherpad and Dimension in use you could:"

  3238. msgstr ""

  3239. 

  3240. #: ../../../CHANGELOG.md:1761

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

  3242. msgstr ""

  3243. 

  3244. #: ../../../CHANGELOG.md:1763

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

  3246. msgstr ""

  3247. 

  3248. #: ../../../CHANGELOG.md:1766

  3249. msgid "2022-11-04"

  3250. msgstr ""

  3251. 

  3252. #: ../../../CHANGELOG.md:1768

  3253. msgid "The playbook now uses external roles for some things"

  3254. msgstr ""

  3255. 

  3256. #: ../../../CHANGELOG.md:1770

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

  3258. msgstr ""

  3259. 

  3260. #: ../../../CHANGELOG.md:1772

  3261. msgid "We're in the process of trimming the playbook and making it reuse Ansible roles."

  3262. msgstr ""

  3263. 

  3264. #: ../../../CHANGELOG.md:1774

  3265. msgid "Starting now, the playbook is composed of 2 types of Ansible roles:"

  3266. msgstr ""

  3267. 

  3268. #: ../../../CHANGELOG.md:1776

  3269. msgid "those that live within the playbook itself (`roles/custom/*`)"

  3270. msgstr ""

  3271. 

  3272. #: ../../../CHANGELOG.md:1778

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

  3274. msgstr ""

  3275. 

  3276. #: ../../../CHANGELOG.md:1780

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

  3278. msgstr ""

  3279. 

  3280. #: ../../../CHANGELOG.md:1782

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

  3282. msgstr ""

  3283. 

  3284. #: ../../../CHANGELOG.md:1784

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

  3286. msgstr ""

  3287. 

  3288. #: ../../../CHANGELOG.md:1787

  3289. msgid "2022-10-14"

  3290. msgstr ""

  3291. 

  3292. #: ../../../CHANGELOG.md:1789

  3293. msgid "synapse-s3-storage-provider support"

  3294. msgstr ""

  3295. 

  3296. #: ../../../CHANGELOG.md:1791

  3297. msgid "**`synapse-s3-storage-provider` support is very new and still relatively untested. Using it may cause data loss.**"

  3298. msgstr ""

  3299. 

  3300. #: ../../../CHANGELOG.md:1793

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

  3302. msgstr ""

  3303. 

  3304. #: ../../../CHANGELOG.md:1795

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

  3306. msgstr ""

  3307. 

  3308. #: ../../../CHANGELOG.md:1797

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

  3310. msgstr ""

  3311. 

  3312. #: ../../../CHANGELOG.md:1799

  3313. msgid "Synapse container image customization support"

  3314. msgstr ""

  3315. 

  3316. #: ../../../CHANGELOG.md:1801

  3317. msgid "We now support customizing the Synapse container image by adding additional build steps to its [`Dockerfile`](https://docs.docker.com/engine/reference/builder/)."

  3318. msgstr ""

  3319. 

  3320. #: ../../../CHANGELOG.md:1803

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

  3322. msgstr ""

  3323. 

  3324. #: ../../../CHANGELOG.md:1805

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

  3326. msgstr ""

  3327. 

  3328. #: ../../../CHANGELOG.md:1816

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

  3330. msgstr ""

  3331. 

  3332. #: ../../../CHANGELOG.md:1818

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

  3334. msgstr ""

  3335. 

  3336. #: ../../../CHANGELOG.md:1821

  3337. msgid "2022-10-02"

  3338. msgstr ""

  3339. 

  3340. #: ../../../CHANGELOG.md:1823

  3341. msgid "matrix-ldap-registration-proxy support"

  3342. msgstr ""

  3343. 

  3344. #: ../../../CHANGELOG.md:1825

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

  3346. msgstr ""

  3347. 

  3348. #: ../../../CHANGELOG.md:1827

  3349. msgid "See our [Setting up matrix-ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started."

  3350. msgstr ""

  3351. 

  3352. #: ../../../CHANGELOG.md:1830

  3353. msgid "2022-09-15"

  3354. msgstr ""

  3355. 

  3356. #: ../../../CHANGELOG.md:1832

  3357. msgid "(Potential Backward Compatibility Break) Major improvements to Synapse workers"

  3358. msgstr ""

  3359. 

  3360. #: ../../../CHANGELOG.md:1834

  3361. msgid "People who are interested in running a Synapse worker setup should know that **our Synapse worker implementation is much more powerful now**:"

  3362. msgstr ""

  3363. 

  3364. #: ../../../CHANGELOG.md:1836

  3365. msgid "we've added support for [Stream writers](#stream-writers-support)"

  3366. msgstr ""

  3367. 

  3368. #: ../../../CHANGELOG.md:1837

  3369. msgid "we've added support for [multiple federation sender workers](#multiple-federation-sender-workers-support)"

  3370. msgstr ""

  3371. 

  3372. #: ../../../CHANGELOG.md:1838

  3373. msgid "we've added support for [multiple pusher workers](#multiple-pusher-workers-support)"

  3374. msgstr ""

  3375. 

  3376. #: ../../../CHANGELOG.md:1839

  3377. msgid "we've added support for [running background tasks on a worker](#background-tasks-can-run-on-a-worker)"

  3378. msgstr ""

  3379. 

  3380. #: ../../../CHANGELOG.md:1840

  3381. msgid "we've restored support for [`appservice` workers](#appservice-worker-support-is-back)"

  3382. msgstr ""

  3383. 

  3384. #: ../../../CHANGELOG.md:1841

  3385. msgid "we've restored support for [`user_dir` workers](#user-directory-worker-support-is-back)"

  3386. msgstr ""

  3387. 

  3388. #: ../../../CHANGELOG.md:1842

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

  3390. msgstr ""

  3391. 

  3392. #: ../../../CHANGELOG.md:1843

  3393. msgid "see the [Potential Backward Incompatibilities after these Synapse worker changes](#potential-backward-incompatibilities-after-these-synapse-worker-changes)"

  3394. msgstr ""

  3395. 

  3396. #: ../../../CHANGELOG.md:1845

  3397. msgid "Stream writers support"

  3398. msgstr ""

  3399. 

  3400. #: ../../../CHANGELOG.md:1847

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

  3402. msgstr ""

  3403. 

  3404. #: ../../../CHANGELOG.md:1849

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

  3406. msgstr ""

  3407. 

  3408. #: ../../../CHANGELOG.md:1851

  3409. msgid "If you'd like to customize the number of workers we also make that possible using these variables:"

  3410. msgstr ""

  3411. 

  3412. #: ../../../CHANGELOG.md:1864

  3413. msgid "Multiple federation sender workers support"

  3414. msgstr ""

  3415. 

  3416. #: ../../../CHANGELOG.md:1866

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

  3418. msgstr ""

  3419. 

  3420. #: ../../../CHANGELOG.md:1868

  3421. msgid "Multiple pusher workers support"

  3422. msgstr ""

  3423. 

  3424. #: ../../../CHANGELOG.md:1870

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

  3426. msgstr ""

  3427. 

  3428. #: ../../../CHANGELOG.md:1872

  3429. msgid "Background tasks can run on a worker"

  3430. msgstr ""

  3431. 

  3432. #: ../../../CHANGELOG.md:1874

  3433. msgid "From now on, you can put [background task processing on a worker](https://matrix-org.github.io/synapse/latest/workers.html#background-tasks)."

  3434. msgstr ""

  3435. 

  3436. #: ../../../CHANGELOG.md:1876

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

  3438. msgstr ""

  3439. 

  3440. #: ../../../CHANGELOG.md:1878

  3441. msgid "Appservice worker support is back"

  3442. msgstr ""

  3443. 

  3444. #: ../../../CHANGELOG.md:1880

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

  3446. msgstr ""

  3447. 

  3448. #: ../../../CHANGELOG.md:1882

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

  3450. msgstr ""

  3451. 

  3452. #: ../../../CHANGELOG.md:1884

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

  3454. msgstr ""

  3455. 

  3456. #: ../../../CHANGELOG.md:1886

  3457. msgid "User Directory worker support is back"

  3458. msgstr ""

  3459. 

  3460. #: ../../../CHANGELOG.md:1888

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

  3462. msgstr ""

  3463. 

  3464. #: ../../../CHANGELOG.md:1890

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

  3466. msgstr ""

  3467. 

  3468. #: ../../../CHANGELOG.md:1892

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

  3470. msgstr ""

  3471. 

  3472. #: ../../../CHANGELOG.md:1894

  3473. msgid "Using more than 1 media repository worker is now more reliable"

  3474. msgstr ""

  3475. 

  3476. #: ../../../CHANGELOG.md:1896

  3477. msgid "With `matrix_synapse_workers_preset: one-of-each`, we only launch one `media_repository` worker."

  3478. msgstr ""

  3479. 

  3480. #: ../../../CHANGELOG.md:1898

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

  3482. msgstr ""

  3483. 

  3484. #: ../../../CHANGELOG.md:1900

  3485. msgid "Potential Backward Incompatibilities after these Synapse worker changes"

  3486. msgstr ""

  3487. 

  3488. #: ../../../CHANGELOG.md:1902

  3489. msgid "Below we'll discuss **potential backward incompatibilities**."

  3490. msgstr ""

  3491. 

  3492. #: ../../../CHANGELOG.md:1904

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

  3494. msgstr ""

  3495. 

  3496. #: ../../../CHANGELOG.md:1906

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

  3498. msgstr ""

  3499. 

  3500. #: ../../../CHANGELOG.md:1908

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

  3502. msgstr ""

  3503. 

  3504. #: ../../../CHANGELOG.md:1910

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

  3506. msgstr ""

  3507. 

  3508. #: ../../../CHANGELOG.md:1913

  3509. msgid "2022-09-09"

  3510. msgstr ""

  3511. 

  3512. #: ../../../CHANGELOG.md:1915

  3513. msgid "Cactus Comments support"

  3514. msgstr ""

  3515. 

  3516. #: ../../../CHANGELOG.md:1917

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

  3518. msgstr ""

  3519. 

  3520. #: ../../../CHANGELOG.md:1919

  3521. msgid "See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-comments.md) documentation to get started."

  3522. msgstr ""

  3523. 

  3524. #: ../../../CHANGELOG.md:1922

  3525. msgid "2022-08-23"

  3526. msgstr ""

  3527. 

  3528. #: ../../../CHANGELOG.md:1924

  3529. msgid "Postmoogle email bridge support"

  3530. msgstr ""

  3531. 

  3532. #: ../../../CHANGELOG.md:1926

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

  3534. msgstr ""

  3535. 

  3536. #: ../../../CHANGELOG.md:1928

  3537. msgid "See our [Setting up Postmoogle email bridging](docs/configuring-playbook-bridge-postmoogle.md) documentation to get started."

  3538. msgstr ""

  3539. 

  3540. #: ../../../CHANGELOG.md:1931

  3541. msgid "2022-08-10"

  3542. msgstr ""

  3543. 

  3544. #: ../../../CHANGELOG.md:1933

  3545. msgid "mautrix-whatsapp default configuration changes"

  3546. msgstr ""

  3547. 

  3548. #: ../../../CHANGELOG.md:1935

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

  3550. msgstr ""

  3551. 

  3552. #: ../../../CHANGELOG.md:1937

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

  3554. msgstr ""

  3555. 

  3556. #: ../../../CHANGELOG.md:1939

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

  3558. msgstr ""

  3559. 

  3560. #: ../../../CHANGELOG.md:1942

  3561. msgid "2022-08-09"

  3562. msgstr ""

  3563. 

  3564. #: ../../../CHANGELOG.md:1944

  3565. msgid "Conduit support"

  3566. msgstr ""

  3567. 

  3568. #: ../../../CHANGELOG.md:1946

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

  3570. msgstr ""

  3571. 

  3572. #: ../../../CHANGELOG.md:1948

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

  3574. msgstr ""

  3575. 

  3576. #: ../../../CHANGELOG.md:1950

  3577. msgid "To try out Conduit, we recommend that you **use a new server** and the following `vars.yml` configuration:"

  3578. msgstr ""

  3579. 

  3580. #: ../../../CHANGELOG.md:1956

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

  3582. msgstr ""

  3583. 

  3584. #: ../../../CHANGELOG.md:1959

  3585. msgid "2022-07-29"

  3586. msgstr ""

  3587. 

  3588. #: ../../../CHANGELOG.md:1961

  3589. msgid "mautrix-discord support"

  3590. msgstr ""

  3591. 

  3592. #: ../../../CHANGELOG.md:1963

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

  3594. msgstr ""

  3595. 

  3596. #: ../../../CHANGELOG.md:1965

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

  3598. msgstr ""

  3599. 

  3600. #: ../../../CHANGELOG.md:1968

  3601. msgid "2022-07-27"

  3602. msgstr ""

  3603. 

  3604. #: ../../../CHANGELOG.md:1970

  3605. msgid "matrix-appservice-kakaotalk support"

  3606. msgstr ""

  3607. 

  3608. #: ../../../CHANGELOG.md:1972

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

  3610. msgstr ""

  3611. 

  3612. #: ../../../CHANGELOG.md:1974

  3613. msgid "See our [Setting up Appservice Kakaotalk bridging](docs/configuring-playbook-bridge-appservice-kakaotalk.md) documentation to get started."

  3614. msgstr ""

  3615. 

  3616. #: ../../../CHANGELOG.md:1977

  3617. msgid "2022-07-20"

  3618. msgstr ""

  3619. 

  3620. #: ../../../CHANGELOG.md:1979

  3621. msgid "maubot support"

  3622. msgstr ""

  3623. 

  3624. #: ../../../CHANGELOG.md:1981

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

  3626. msgstr ""

  3627. 

  3628. #: ../../../CHANGELOG.md:1983

  3629. msgid "See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) documentation to get started."

  3630. msgstr ""

  3631. 

  3632. #: ../../../CHANGELOG.md:1986

  3633. msgid "2022-07-14"

  3634. msgstr ""

  3635. 

  3636. #: ../../../CHANGELOG.md:1988

  3637. msgid "mx-puppet-skype removal"

  3638. msgstr ""

  3639. 

  3640. #: ../../../CHANGELOG.md:1990

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

  3642. msgstr ""

  3643. 

  3644. #: ../../../CHANGELOG.md:1992

  3645. msgid "To completely clean up your server from `mx-puppet-skype`'s presence on it:"

  3646. msgstr ""

  3647. 

  3648. #: ../../../CHANGELOG.md:1994

  3649. msgid "ensure your Ansible configuration (`vars.yml` file) no longer contains `matrix_mx_puppet_skype_*` references"

  3650. msgstr ""

  3651. 

  3652. #: ../../../CHANGELOG.md:1995

  3653. msgid "stop and disable the systemd service (run `systemctl disable --now matrix-mx-puppet-skype` on the server)"

  3654. msgstr ""

  3655. 

  3656. #: ../../../CHANGELOG.md:1996

  3657. msgid "delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-skype.service` on the server)"

  3658. msgstr ""

  3659. 

  3660. #: ../../../CHANGELOG.md:1997

  3661. msgid "delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on the server)"

  3662. msgstr ""

  3663. 

  3664. #: ../../../CHANGELOG.md:1998

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

  3666. msgstr ""

  3667. 

  3668. #: ../../../CHANGELOG.md:2000

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

  3670. msgstr ""

  3671. 

  3672. #: ../../../CHANGELOG.md:2002

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

  3674. msgstr ""

  3675. 

  3676. #: ../../../CHANGELOG.md:2004

  3677. msgid "signald (0.19.0+) upgrade requires data migration"

  3678. msgstr ""

  3679. 

  3680. #: ../../../CHANGELOG.md:2006

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

  3682. msgstr ""

  3683. 

  3684. #: ../../../CHANGELOG.md:2008

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

  3686. msgstr ""

  3687. 

  3688. #: ../../../CHANGELOG.md:2010

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

  3690. msgstr ""

  3691. 

  3692. #: ../../../CHANGELOG.md:2012

  3693. msgid "We attempt to do this data migration automatically every time Signald starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` systemd unit definition."

  3694. msgstr ""

  3695. 

  3696. #: ../../../CHANGELOG.md:2014

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

  3698. msgstr ""

  3699. 

  3700. #: ../../../CHANGELOG.md:2017

  3701. msgid "2022-07-05"

  3702. msgstr ""

  3703. 

  3704. #: ../../../CHANGELOG.md:2019

  3705. msgid "Ntfy push notifications support"

  3706. msgstr ""

  3707. 

  3708. #: ../../../CHANGELOG.md:2021

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

  3710. msgstr ""

  3711. 

  3712. #: ../../../CHANGELOG.md:2023

  3713. msgid "See our [Setting up the ntfy push notifications server](docs/configuring-playbook-ntfy.md) documentation to get started."

  3714. msgstr ""

  3715. 

  3716. #: ../../../CHANGELOG.md:2026

  3717. msgid "2022-06-23"

  3718. msgstr ""

  3719. 

  3720. #: ../../../CHANGELOG.md:2028

  3721. msgid "(Potential Backward Compatibility Break) Changes around metrics collection"

  3722. msgstr ""

  3723. 

  3724. #: ../../../CHANGELOG.md:2030

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

  3726. msgstr ""

  3727. 

  3728. #: ../../../CHANGELOG.md:2032

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

  3730. msgstr ""

  3731. 

  3732. #: ../../../CHANGELOG.md:2034

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

  3734. msgstr ""

  3735. 

  3736. #: ../../../CHANGELOG.md:2036

  3737. msgid "**If you are using the [Hookshot bridge](docs/configuring-playbook-bridge-hookshot.md)**, you may find that:"

  3738. msgstr ""

  3739. 

  3740. #: ../../../CHANGELOG.md:2037

  3741. msgid "**Metrics may not be enabled by default anymore**:"

  3742. msgstr ""

  3743. 

  3744. #: ../../../CHANGELOG.md:2038

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

  3746. msgstr ""

  3747. 

  3748. #: ../../../CHANGELOG.md:2039

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

  3750. msgstr ""

  3751. 

  3752. #: ../../../CHANGELOG.md:2040

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

  3754. msgstr ""

  3755. 

  3756. #: ../../../CHANGELOG.md:2041

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

  3758. msgstr ""

  3759. 

  3760. #: ../../../CHANGELOG.md:2043

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

  3762. msgstr ""

  3763. 

  3764. #: ../../../CHANGELOG.md:2045

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

  3766. msgstr ""

  3767. 

  3768. #: ../../../CHANGELOG.md:2047

  3769. msgid "**If you're using Synapse** and would like to collect its metrics from an external Prometheus server, you may find that:"

  3770. msgstr ""

  3771. 

  3772. #: ../../../CHANGELOG.md:2049

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

  3774. msgstr ""

  3775. 

  3776. #: ../../../CHANGELOG.md:2050

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

  3778. msgstr ""

  3779. 

  3780. #: ../../../CHANGELOG.md:2051

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

  3782. msgstr ""

  3783. 

  3784. #: ../../../CHANGELOG.md:2052

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

  3786. msgstr ""

  3787. 

  3788. #: ../../../CHANGELOG.md:2054

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

  3790. msgstr ""

  3791. 

  3792. #: ../../../CHANGELOG.md:2056

  3793. msgid "2022-06-13"

  3794. msgstr ""

  3795. 

  3796. #: ../../../CHANGELOG.md:2058

  3797. msgid "go-skype-bridge bridging support"

  3798. msgstr ""

  3799. 

  3800. #: ../../../CHANGELOG.md:2060

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

  3802. msgstr ""

  3803. 

  3804. #: ../../../CHANGELOG.md:2062

  3805. msgid "See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md) documentation to get started."

  3806. msgstr ""

  3807. 

  3808. #: ../../../CHANGELOG.md:2064

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

  3810. msgstr ""

  3811. 

  3812. #: ../../../CHANGELOG.md:2067

  3813. msgid "2022-06-09"

  3814. msgstr ""

  3815. 

  3816. #: ../../../CHANGELOG.md:2069

  3817. msgid "Running Ansible in a container can now happen on the Matrix server itself"

  3818. msgstr ""

  3819. 

  3820. #: ../../../CHANGELOG.md:2071

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

  3822. msgstr ""

  3823. 

  3824. #: ../../../CHANGELOG.md:2074

  3825. msgid "2022-05-31"

  3826. msgstr ""

  3827. 

  3828. #: ../../../CHANGELOG.md:2076

  3829. msgid "Synapse v1.60 upgrade may cause trouble and require manual intervention"

  3830. msgstr ""

  3831. 

  3832. #: ../../../CHANGELOG.md:2078

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

  3834. msgstr ""

  3835. 

  3836. #: ../../../CHANGELOG.md:2080

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

  3838. msgstr ""

  3839. 

  3840. #: ../../../CHANGELOG.md:2082

  3841. msgid "**If Synapse fails to start** after your next playbook run, you'll need to:"

  3842. msgstr ""

  3843. 

  3844. #: ../../../CHANGELOG.md:2084

  3845. msgid "SSH into the Matrix server"

  3846. msgstr ""

  3847. 

  3848. #: ../../../CHANGELOG.md:2085

  3849. msgid "launch `/usr/local/bin/matrix-postgres-cli`"

  3850. msgstr ""

  3851. 

  3852. #: ../../../CHANGELOG.md:2086

  3853. msgid "switch to the `synapse` database: `\\c synapse`"

  3854. msgstr ""

  3855. 

  3856. #: ../../../CHANGELOG.md:2087

  3857. msgid "run the following SQL query:"

  3858. msgstr ""

  3859. 

  3860. #: ../../../CHANGELOG.md:2106

  3861. msgid "You could then restart services: `ansible-playbook -i inventory/hosts setup.yml --tags=start`"

  3862. msgstr ""

  3863. 

  3864. #: ../../../CHANGELOG.md:2109

  3865. msgid "2022-04-25"

  3866. msgstr ""

  3867. 

  3868. #: ../../../CHANGELOG.md:2111

  3869. msgid "Buscarron bot support"

  3870. msgstr ""

  3871. 

  3872. #: ../../../CHANGELOG.md:2113

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

  3874. msgstr ""

  3875. 

  3876. #: ../../../CHANGELOG.md:2115

  3877. msgid "See our [Setting up Buscarron](docs/configuring-playbook-bot-buscarron.md) documentation to get started."

  3878. msgstr ""

  3879. 

  3880. #: ../../../CHANGELOG.md:2118

  3881. msgid "2022-04-21"

  3882. msgstr ""

  3883. 

  3884. #: ../../../CHANGELOG.md:2120

  3885. msgid "matrix-registration-bot support"

  3886. msgstr ""

  3887. 

  3888. #: ../../../CHANGELOG.md:2122

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

  3890. msgstr ""

  3891. 

  3892. #: ../../../CHANGELOG.md:2124

  3893. msgid "See our [Setting up matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) documentation to get started."

  3894. msgstr ""

  3895. 

  3896. #: ../../../CHANGELOG.md:2127

  3897. msgid "2022-04-19"

  3898. msgstr ""

  3899. 

  3900. #: ../../../CHANGELOG.md:2129

  3901. msgid "BorgBackup support"

  3902. msgstr ""

  3903. 

  3904. #: ../../../CHANGELOG.md:2131

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

  3906. msgstr ""

  3907. 

  3908. #: ../../../CHANGELOG.md:2133

  3909. msgid "See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md) documentation to get started."

  3910. msgstr ""

  3911. 

  3912. #: ../../../CHANGELOG.md:2135

  3913. msgid "(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action"

  3914. msgstr ""

  3915. 

  3916. #: ../../../CHANGELOG.md:2137

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

  3918. msgstr ""

  3919. 

  3920. #: ../../../CHANGELOG.md:2139

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

  3922. msgstr ""

  3923. 

  3924. #: ../../../CHANGELOG.md:2141

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

  3926. msgstr ""

  3927. 

  3928. #: ../../../CHANGELOG.md:2143

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

  3930. msgstr ""

  3931. 

  3932. #: ../../../CHANGELOG.md:2145

  3933. msgid "Pull the latest playbook changes"

  3934. msgstr ""

  3935. 

  3936. #: ../../../CHANGELOG.md:2146

  3937. msgid "Stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"

  3938. msgstr ""

  3939. 

  3940. #: ../../../CHANGELOG.md:2147

  3941. msgid "Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all`)"

  3942. msgstr ""

  3943. 

  3944. #: ../../../CHANGELOG.md:2148

  3945. msgid "Start Postgres (`systemctl start matrix-postgres` on the server)"

  3946. msgstr ""

  3947. 

  3948. #: ../../../CHANGELOG.md:2149

  3949. msgid "Start the main Synapse process (`systemctl start matrix-synapse` on the server)"

  3950. msgstr ""

  3951. 

  3952. #: ../../../CHANGELOG.md:2150

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

  3954. msgstr ""

  3955. 

  3956. #: ../../../CHANGELOG.md:2151

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

  3958. msgstr ""

  3959. 

  3960. #: ../../../CHANGELOG.md:2154

  3961. msgid "2022-04-14"

  3962. msgstr ""

  3963. 

  3964. #: ../../../CHANGELOG.md:2156

  3965. msgid "(Compatibility Break) Changes to `docker-src` permissions necessitating manual action"

  3966. msgstr ""

  3967. 

  3968. #: ../../../CHANGELOG.md:2158

  3969. msgid "Users who build container images from source will need to manually correct file permissions of some directories on the server."

  3970. msgstr ""

  3971. 

  3972. #: ../../../CHANGELOG.md:2160

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

  3974. msgstr ""

  3975. 

  3976. #: ../../../CHANGELOG.md:2162

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

  3978. msgstr ""

  3979. 

  3980. #: ../../../CHANGELOG.md:2164

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

  3982. msgstr ""

  3983. 

  3984. #: ../../../CHANGELOG.md:2167

  3985. msgid "2022-03-17"

  3986. msgstr ""

  3987. 

  3988. #: ../../../CHANGELOG.md:2169

  3989. msgid "(Compatibility Break) ma1sd identity server no longer installed by default"

  3990. msgstr ""

  3991. 

  3992. #: ../../../CHANGELOG.md:2171

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

  3994. msgstr ""

  3995. 

  3996. #: ../../../CHANGELOG.md:2173

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

  3998. msgstr ""

  3999. 

  4000. #: ../../../CHANGELOG.md:2175

  4001. msgid "Since Element clients no longer default to using a public identity server if another one is not provided, we can stop installing ma1sd."

  4002. msgstr ""

  4003. 

  4004. #: ../../../CHANGELOG.md:2177

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

  4006. msgstr ""

  4007. 

  4008. #: ../../../CHANGELOG.md:2184

  4009. msgid "2022-02-12"

  4010. msgstr ""

  4011. 

  4012. #: ../../../CHANGELOG.md:2186

  4013. msgid "matrix_encryption_disabler support"

  4014. msgstr ""

  4015. 

  4016. #: ../../../CHANGELOG.md:2188

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

  4018. msgstr ""

  4019. 

  4020. #: ../../../CHANGELOG.md:2190

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

  4022. msgstr ""

  4023. 

  4024. #: ../../../CHANGELOG.md:2193

  4025. msgid "2022-02-01"

  4026. msgstr ""

  4027. 

  4028. #: ../../../CHANGELOG.md:2195

  4029. msgid "matrix-hookshot bridging support"

  4030. msgstr ""

  4031. 

  4032. #: ../../../CHANGELOG.md:2197

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

  4034. msgstr ""

  4035. 

  4036. #: ../../../CHANGELOG.md:2200

  4037. msgid "2022-01-31"

  4038. msgstr ""

  4039. 

  4040. #: ../../../CHANGELOG.md:2202

  4041. msgid "ARM support for matrix-corporal"

  4042. msgstr ""

  4043. 

  4044. #: ../../../CHANGELOG.md:2204

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

  4046. msgstr ""

  4047. 

  4048. #: ../../../CHANGELOG.md:2207

  4049. msgid "2022-01-07"

  4050. msgstr ""

  4051. 

  4052. #: ../../../CHANGELOG.md:2209

  4053. msgid "Dendrite support"

  4054. msgstr ""

  4055. 

  4056. #: ../../../CHANGELOG.md:2211

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

  4058. msgstr ""

  4059. 

  4060. #: ../../../CHANGELOG.md:2213

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

  4062. msgstr ""

  4063. 

  4064. #: ../../../CHANGELOG.md:2215

  4065. msgid "We believe that 2022 will be the year of the non-Synapse Matrix server!"

  4066. msgstr ""

  4067. 

  4068. #: ../../../CHANGELOG.md:2217

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

  4070. msgstr ""

  4071. 

  4072. #: ../../../CHANGELOG.md:2219

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

  4074. msgstr ""

  4075. 

  4076. #: ../../../CHANGELOG.md:2221

  4077. msgid "Adapting the configuration for existing Synapse installations"

  4078. msgstr ""

  4079. 

  4080. #: ../../../CHANGELOG.md:2223

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

  4082. msgstr ""

  4083. 

  4084. #: ../../../CHANGELOG.md:2225

  4085. msgid "The `vars.yml` file for **existing installations will need to be updated** by adding this **additional configuration**:"

  4086. msgstr ""

  4087. 

  4088. #: ../../../CHANGELOG.md:2237

  4089. msgid "Trying out Dendrite"

  4090. msgstr ""

  4091. 

  4092. #: ../../../CHANGELOG.md:2239

  4093. msgid "Finally, **to try out Dendrite**, we recommend that you **use a new server** and the following addition to your `vars.yml` configuration:"

  4094. msgstr ""

  4095. 

  4096. #: ../../../CHANGELOG.md:2245

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

  4098. msgstr ""

  4099. 

  4100. #: ../../../CHANGELOG.md:2247

  4101. msgid "We're excited to gain support for other homeserver implementations, like [Conduit](https://conduit.rs/), etc!"

  4102. msgstr ""

  4103. 

  4104. #: ../../../CHANGELOG.md:2249

  4105. msgid "Honoroit bot support"

  4106. msgstr ""

  4107. 

  4108. #: ../../../CHANGELOG.md:2251

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

  4110. msgstr ""

  4111. 

  4112. #: ../../../CHANGELOG.md:2253

  4113. msgid "See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documentation to get started."

  4114. msgstr ""

  4115. 

  4116. #: ../../../CHANGELOG.md:2256

  4117. msgid "2022-01-06"

  4118. msgstr ""

  4119. 

  4120. #: ../../../CHANGELOG.md:2258

  4121. msgid "Cinny support"

  4122. msgstr ""

  4123. 

  4124. #: ../../../CHANGELOG.md:2260

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

  4126. msgstr ""

  4127. 

  4128. #: ../../../CHANGELOG.md:2262

  4129. msgid "By default, we still install Element Web. Still, people who'd like to try Cinny out can now install it via the playbook."

  4130. msgstr ""

  4131. 

  4132. #: ../../../CHANGELOG.md:2264

  4133. msgid "Additional details are available in [Setting up Cinny](docs/configuring-playbook-client-cinny.md)."

  4134. msgstr ""

  4135. 

  4136. #: ../../../CHANGELOG.md:2267

  4137. msgid "2021-12-22"

  4138. msgstr ""

  4139. 

  4140. #: ../../../CHANGELOG.md:2269

  4141. msgid "Twitter bridging support via mautrix-twitter"

  4142. msgstr ""

  4143. 

  4144. #: ../../../CHANGELOG.md:2271

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

  4146. msgstr ""

  4147. 

  4148. #: ../../../CHANGELOG.md:2274

  4149. msgid "2021-12-14"

  4150. msgstr ""

  4151. 

  4152. #: ../../../CHANGELOG.md:2276

  4153. msgid "(Security) Users of the Signal bridge may wish to upgrade it to work around log4j vulnerability"

  4154. msgstr ""

  4155. 

  4156. #: ../../../CHANGELOG.md:2278

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

  4158. msgstr ""

  4159. 

  4160. #: ../../../CHANGELOG.md:2280

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

  4162. msgstr ""

  4163. 

  4164. #: ../../../CHANGELOG.md:2283

  4165. msgid "2021-11-11"

  4166. msgstr ""

  4167. 

  4168. #: ../../../CHANGELOG.md:2285

  4169. msgid "Dropped support for Postgres v9.6"

  4170. msgstr ""

  4171. 

  4172. #: ../../../CHANGELOG.md:2287

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

  4174. msgstr ""

  4175. 

  4176. #: ../../../CHANGELOG.md:2289

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

  4178. msgstr ""

  4179. 

  4180. #: ../../../CHANGELOG.md:2292

  4181. msgid "2021-10-23"

  4182. msgstr ""

  4183. 

  4184. #: ../../../CHANGELOG.md:2294

  4185. msgid "Hangouts bridge no longer updated, superseded by a Googlechat bridge"

  4186. msgstr ""

  4187. 

  4188. #: ../../../CHANGELOG.md:2296

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

  4190. msgstr ""

  4191. 

  4192. #: ../../../CHANGELOG.md:2298

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

  4194. msgstr ""

  4195. 

  4196. #: ../../../CHANGELOG.md:2301

  4197. msgid "2021-08-23"

  4198. msgstr ""

  4199. 

  4200. #: ../../../CHANGELOG.md:2303

  4201. msgid "LinkedIn bridging support via beeper-linkedin"

  4202. msgstr ""

  4203. 

  4204. #: ../../../CHANGELOG.md:2305

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

  4206. msgstr ""

  4207. 

  4208. #: ../../../CHANGELOG.md:2307

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

  4210. msgstr ""

  4211. 

  4212. #: ../../../CHANGELOG.md:2309

  4213. msgid "To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)."

  4214. msgstr ""

  4215. 

  4216. #: ../../../CHANGELOG.md:2312

  4217. msgid "2021-08-20"

  4218. msgstr ""

  4219. 

  4220. #: ../../../CHANGELOG.md:2314

  4221. msgid "Sygnal upgraded — ARM support and no longer requires a database"

  4222. msgstr ""

  4223. 

  4224. #: ../../../CHANGELOG.md:2316

  4225. msgid "The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been upgraded from `v0.9.0` to `v0.10.1`."

  4226. msgstr ""

  4227. 

  4228. #: ../../../CHANGELOG.md:2318

  4229. msgid "This is an optional component for the playbook, so most of our users wouldn't care about this announcement."

  4230. msgstr ""

  4231. 

  4232. #: ../../../CHANGELOG.md:2320

  4233. msgid "Since this feels like a relatively big (and untested, as of yet) Sygnal change, we're putting up this changelog entry."

  4234. msgstr ""

  4235. 

  4236. #: ../../../CHANGELOG.md:2322

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

  4238. msgstr ""

  4239. 

  4240. #: ../../../CHANGELOG.md:2325

  4241. msgid "2021-05-21"

  4242. msgstr ""

  4243. 

  4244. #: ../../../CHANGELOG.md:2327

  4245. msgid "Hydrogen support"

  4246. msgstr ""

  4247. 

  4248. #: ../../../CHANGELOG.md:2329

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

  4250. msgstr ""

  4251. 

  4252. #: ../../../CHANGELOG.md:2331

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

  4254. msgstr ""

  4255. 

  4256. #: ../../../CHANGELOG.md:2333

  4257. msgid "Additional details are available in [Setting up Hydrogen](docs/configuring-playbook-client-hydrogen.md)."

  4258. msgstr ""

  4259. 

  4260. #: ../../../CHANGELOG.md:2336

  4261. msgid "2021-05-19"

  4262. msgstr ""

  4263. 

  4264. #: ../../../CHANGELOG.md:2338

  4265. msgid "Heisenbridge support"

  4266. msgstr ""

  4267. 

  4268. #: ../../../CHANGELOG.md:2340

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

  4270. msgstr ""

  4271. 

  4272. #: ../../../CHANGELOG.md:2342

  4273. msgid "Additional details are available in [Setting up Heisenbridge bouncer-style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)."

  4274. msgstr ""

  4275. 

  4276. #: ../../../CHANGELOG.md:2345

  4277. msgid "2021-04-16"

  4278. msgstr ""

  4279. 

  4280. #: ../../../CHANGELOG.md:2347

  4281. msgid "Disabling TLSv1 and TLSv1.1 for coturn"

  4282. msgstr ""

  4283. 

  4284. #: ../../../CHANGELOG.md:2349

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

  4286. msgstr ""

  4287. 

  4288. #: ../../../CHANGELOG.md:2351

  4289. msgid "If you need to support old clients, you can re-enable both (or whichever one you need) with the following configuration:"

  4290. msgstr ""

  4291. 

  4292. #: ../../../CHANGELOG.md:2359

  4293. msgid "2021-04-05"

  4294. msgstr ""

  4295. 

  4296. #: ../../../CHANGELOG.md:2361

  4297. msgid "Automated local Postgres backup support"

  4298. msgstr ""

  4299. 

  4300. #: ../../../CHANGELOG.md:2363

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

  4302. msgstr ""

  4303. 

  4304. #: ../../../CHANGELOG.md:2365

  4305. msgid "Additional details are available in [Setting up Postgres backup](docs/configuring-playbook-postgres-backup.md)."

  4306. msgstr ""

  4307. 

  4308. #: ../../../CHANGELOG.md:2368

  4309. msgid "2021-04-03"

  4310. msgstr ""

  4311. 

  4312. #: ../../../CHANGELOG.md:2370

  4313. msgid "Mjolnir moderation tool (bot) support"

  4314. msgstr ""

  4315. 

  4316. #: ../../../CHANGELOG.md:2372

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

  4318. msgstr ""

  4319. 

  4320. #: ../../../CHANGELOG.md:2374

  4321. msgid "Additional details are available in [Setting up Mjolnir](docs/configuring-playbook-bot-mjolnir.md)."

  4322. msgstr ""

  4323. 

  4324. #: ../../../CHANGELOG.md:2377

  4325. msgid "2021-03-20"

  4326. msgstr ""

  4327. 

  4328. #: ../../../CHANGELOG.md:2379

  4329. msgid "Sygnal push gateway support"

  4330. msgstr ""

  4331. 

  4332. #: ../../../CHANGELOG.md:2381

  4333. msgid "The playbook can now install the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you."

  4334. msgstr ""

  4335. 

  4336. #: ../../../CHANGELOG.md:2383

  4337. msgid "This is only useful to people who develop/build their own Matrix client applications."

  4338. msgstr ""

  4339. 

  4340. #: ../../../CHANGELOG.md:2385

  4341. msgid "Additional details are available in our [Setting up the Sygnal push gateway](docs/configuring-playbook-sygnal.md) docs."

  4342. msgstr ""

  4343. 

  4344. #: ../../../CHANGELOG.md:2388

  4345. msgid "2021-03-16"

  4346. msgstr ""

  4347. 

  4348. #: ../../../CHANGELOG.md:2390

  4349. msgid "Go-NEB support"

  4350. msgstr ""

  4351. 

  4352. #: ../../../CHANGELOG.md:2392

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

  4354. msgstr ""

  4355. 

  4356. #: ../../../CHANGELOG.md:2394

  4357. msgid "Additional details are available in [Setting up Go-NEB](docs/configuring-playbook-bot-go-neb.md)."

  4358. msgstr ""

  4359. 

  4360. #: ../../../CHANGELOG.md:2397

  4361. msgid "2021-02-19"

  4362. msgstr ""

  4363. 

  4364. #: ../../../CHANGELOG.md:2399

  4365. msgid "GroupMe bridging support via mx-puppet-groupme"

  4366. msgstr ""

  4367. 

  4368. #: ../../../CHANGELOG.md:2401

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

  4370. msgstr ""

  4371. 

  4372. #: ../../../CHANGELOG.md:2403

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

  4374. msgstr ""

  4375. 

  4376. #: ../../../CHANGELOG.md:2405

  4377. msgid "To get started, follow our [Setting up MX Puppet GroupMe](docs/configuring-playbook-bridge-mx-puppet-groupme.md) docs."

  4378. msgstr ""

  4379. 

  4380. #: ../../../CHANGELOG.md:2407

  4381. msgid "Mautrix Instagram bridging support"

  4382. msgstr ""

  4383. 

  4384. #: ../../../CHANGELOG.md:2409

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

  4386. msgstr ""

  4387. 

  4388. #: ../../../CHANGELOG.md:2411

  4389. msgid "Additional details are available in [Setting up Mautrix Instagram bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)."

  4390. msgstr ""

  4391. 

  4392. #: ../../../CHANGELOG.md:2413

  4393. msgid "Synapse workers support"

  4394. msgstr ""

  4395. 

  4396. #: ../../../CHANGELOG.md:2415

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

  4398. msgstr ""

  4399. 

  4400. #: ../../../CHANGELOG.md:2417

  4401. msgid "Having support for workers makes the playbook suitable for larger homeserver deployments."

  4402. msgstr ""

  4403. 

  4404. #: ../../../CHANGELOG.md:2419

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

  4406. msgstr ""

  4407. 

  4408. #: ../../../CHANGELOG.md:2421

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

  4410. msgstr ""

  4411. 

  4412. #: ../../../CHANGELOG.md:2423

  4413. msgid "To enable Synapse workers, follow our [Load balancing with workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) documentation."

  4414. msgstr ""

  4415. 

  4416. #: ../../../CHANGELOG.md:2426

  4417. msgid "2021-02-12"

  4418. msgstr ""

  4419. 

  4420. #: ../../../CHANGELOG.md:2428

  4421. msgid "(Potential Breaking Change) Monitoring/metrics support using Prometheus and Grafana"

  4422. msgstr ""

  4423. 

  4424. #: ../../../CHANGELOG.md:2430

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

  4426. msgstr ""

  4427. 

  4428. #: ../../../CHANGELOG.md:2432

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

  4430. msgstr ""

  4431. 

  4432. #: ../../../CHANGELOG.md:2434

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

  4434. msgstr ""

  4435. 

  4436. #: ../../../CHANGELOG.md:2437

  4437. msgid "2021-01-31"

  4438. msgstr ""

  4439. 

  4440. #: ../../../CHANGELOG.md:2439

  4441. msgid "Etherpad support"

  4442. msgstr ""

  4443. 

  4444. #: ../../../CHANGELOG.md:2441

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

  4446. msgstr ""

  4447. 

  4448. #: ../../../CHANGELOG.md:2443

  4449. msgid "To get it installed, follow [our Etherpad docs page](docs/configuring-playbook-etherpad.md)."

  4450. msgstr ""

  4451. 

  4452. #: ../../../CHANGELOG.md:2446

  4453. msgid "2021-01-22"

  4454. msgstr ""

  4455. 

  4456. #: ../../../CHANGELOG.md:2448

  4457. msgid "(Breaking Change) Postgres changes that require manual intervention"

  4458. msgstr ""

  4459. 

  4460. #: ../../../CHANGELOG.md:2450

  4461. msgid "We've made a lot of changes to our Postgres setup and some manual action is required (described below). Sorry about the hassle."

  4462. msgstr ""

  4463. 

  4464. #: ../../../CHANGELOG.md:2452

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

  4466. msgstr ""

  4467. 

  4468. #: ../../../CHANGELOG.md:2454

  4469. msgid "Why?"

  4470. msgstr ""

  4471. 

  4472. #: ../../../CHANGELOG.md:2456

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

  4474. msgstr ""

  4475. 

  4476. #: ../../../CHANGELOG.md:2457

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

  4478. msgstr ""

  4479. 

  4480. #: ../../../CHANGELOG.md:2458

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

  4482. msgstr ""

  4483. 

  4484. #: ../../../CHANGELOG.md:2459

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

  4486. msgstr ""

  4487. 

  4488. #: ../../../CHANGELOG.md:2460

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

  4490. msgstr ""

  4491. 

  4492. #: ../../../CHANGELOG.md:2461

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

  4494. msgstr ""

  4495. 

  4496. #: ../../../CHANGELOG.md:2463

  4497. msgid "So, this is some **effort to improve security** and to **prepare for a brighter future of having more homeserver options** than just Synapse."

  4498. msgstr ""

  4499. 

  4500. #: ../../../CHANGELOG.md:2465

  4501. msgid "What has really changed?"

  4502. msgstr ""

  4503. 

  4504. #: ../../../CHANGELOG.md:2467

  4505. msgid "the default superuser Postgres username is now `matrix` (used to be `synapse`)"

  4506. msgstr ""

  4507. 

  4508. #: ../../../CHANGELOG.md:2468

  4509. msgid "the default Postgres database is now `matrix` (used to be `homeserver`)"

  4510. msgstr ""

  4511. 

  4512. #: ../../../CHANGELOG.md:2469

  4513. msgid "Synapse's database is now `synapse` (used to be `homeserver`). This is now just another \"additional database\" that the playbook manages for you"

  4514. msgstr ""

  4515. 

  4516. #: ../../../CHANGELOG.md:2470

  4517. msgid "Synapse's user called `synapse` is just a regular user that can only use the `synapse` database (not a superuser anymore)"

  4518. msgstr ""

  4519. 

  4520. #: ../../../CHANGELOG.md:2472

  4521. msgid "What do I do if I'm using the integrated Postgres server (default)?"

  4522. msgstr ""

  4523. 

  4524. #: ../../../CHANGELOG.md:2474

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

  4526. msgstr ""

  4527. 

  4528. #: ../../../CHANGELOG.md:2476

  4529. msgid "To migrate to the new setup, expect a few minutes of downtime, while you follow these steps:"

  4530. msgstr ""

  4531. 

  4532. #: ../../../CHANGELOG.md:2478

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

  4534. msgstr ""

  4535. 

  4536. #: ../../../CHANGELOG.md:2480

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

  4538. msgstr ""

  4539. 

  4540. #: ../../../CHANGELOG.md:2482

  4541. msgid "Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` file, adding a line like this:"

  4542. msgstr ""

  4543. 

  4544. #: ../../../CHANGELOG.md:2487

  4545. #: ../../../CHANGELOG.md:2499

  4546. msgid "… where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2."

  4547. msgstr ""

  4548. 

  4549. #: ../../../CHANGELOG.md:2489

  4550. msgid "Stop all services: `ansible-playbook -i inventory/hosts setup.yml --tags=stop`"

  4551. msgstr ""

  4552. 

  4553. #: ../../../CHANGELOG.md:2490

  4554. msgid "Log in to the server via SSH. The next commands will be performed there."

  4555. msgstr ""

  4556. 

  4557. #: ../../../CHANGELOG.md:2491

  4558. msgid "Start the Postgres database server: `systemctl start matrix-postgres`"

  4559. msgstr ""

  4560. 

  4561. #: ../../../CHANGELOG.md:2492

  4562. msgid "Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`"

  4563. msgstr ""

  4564. 

  4565. #: ../../../CHANGELOG.md:2493

  4566. msgid "Execute the following query, while making sure to **change the password inside** (**don't forget the ending `;`**):"

  4567. msgstr ""

  4568. 

  4569. #: ../../../CHANGELOG.md:2501

  4570. msgid "Execute the following queries as you see them (no modifications necessary, so you can just **paste them all at once**):"

  4571. msgstr ""

  4572. 

  4573. #: ../../../CHANGELOG.md:2519

  4574. msgid "You may need to press *Enter* after pasting the lines above."

  4575. msgstr ""

  4576. 

  4577. #: ../../../CHANGELOG.md:2521

  4578. msgid "Re-run the playbook normally: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`"

  4579. msgstr ""

  4580. 

  4581. #: ../../../CHANGELOG.md:2523

  4582. msgid "What do I do if I'm using an external Postgres server?"

  4583. msgstr ""

  4584. 

  4585. #: ../../../CHANGELOG.md:2525

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

  4587. msgstr ""

  4588. 

  4589. #: ../../../CHANGELOG.md:2527

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

  4591. msgstr ""

  4592. 

  4593. #: ../../../CHANGELOG.md:2530

  4594. msgid "2021-01-20"

  4595. msgstr ""

  4596. 

  4597. #: ../../../CHANGELOG.md:2532

  4598. msgid "(Breaking Change) The mautrix-facebook bridge now requires a Postgres database"

  4599. msgstr ""

  4600. 

  4601. #: ../../../CHANGELOG.md:2534

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

  4603. msgstr ""

  4604. 

  4605. #: ../../../CHANGELOG.md:2536

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

  4607. msgstr ""

  4608. 

  4609. #: ../../../CHANGELOG.md:2538

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

  4611. msgstr ""

  4612. 

  4613. #: ../../../CHANGELOG.md:2540

  4614. msgid "Whether this change requires your intervention depends mostly on:"

  4615. msgstr ""

  4616. 

  4617. #: ../../../CHANGELOG.md:2541

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

  4619. msgstr ""

  4620. 

  4621. #: ../../../CHANGELOG.md:2542

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

  4623. msgstr ""

  4624. 

  4625. #: ../../../CHANGELOG.md:2544

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

  4627. msgstr ""

  4628. 

  4629. #: ../../../CHANGELOG.md:2546

  4630. msgid "Upgrade path for people NOT running an external Postgres server (default for the playbook)"

  4631. msgstr ""

  4632. 

  4633. #: ../../../CHANGELOG.md:2548

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

  4635. msgstr ""

  4636. 

  4637. #: ../../../CHANGELOG.md:2550

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

  4639. msgstr ""

  4640. 

  4641. #: ../../../CHANGELOG.md:2552

  4642. msgid "Alternatively, [you can stay on SQLite for a little longer](#staying-on-sqlite-for-a-little-longer-temporary-solution)."

  4643. msgstr ""

  4644. 

  4645. #: ../../../CHANGELOG.md:2554

  4646. msgid "Upgrade path for people running an external Postgres server"

  4647. msgstr ""

  4648. 

  4649. #: ../../../CHANGELOG.md:2556

  4650. msgid "For people using the internal Postgres server (the default for the playbook):"

  4651. msgstr ""

  4652. 

  4653. #: ../../../CHANGELOG.md:2557

  4654. msgid "we automatically create an additional `matrix_mautrix_facebook` Postgres database and credentials to access it"

  4655. msgstr ""

  4656. 

  4657. #: ../../../CHANGELOG.md:2558

  4658. msgid "we automatically adjust the bridge's `matrix_mautrix_facebook_database_*` variables to point the bridge to that Postgres database"

  4659. msgstr ""

  4660. 

  4661. #: ../../../CHANGELOG.md:2559

  4662. msgid "we use [pgloader](https://pgloader.io/) to automatically import the existing SQLite data for the bridge into the `matrix_mautrix_facebook` Postgres database"

  4663. msgstr ""

  4664. 

  4665. #: ../../../CHANGELOG.md:2561

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

  4667. msgstr ""

  4668. 

  4669. #: ../../../CHANGELOG.md:2563

  4670. msgid "You have 3 ways to proceed:"

  4671. msgstr ""

  4672. 

  4673. #: ../../../CHANGELOG.md:2565

  4674. msgid "contribute to the playbook to make this possible (difficult)"

  4675. msgstr ""

  4676. 

  4677. #: ../../../CHANGELOG.md:2566

  4678. msgid "or, do the migration \"steps\" manually:"

  4679. msgstr ""

  4680. 

  4681. #: ../../../CHANGELOG.md:2567

  4682. msgid "stop the bridge (`systemctl stop matrix-mautrix-facebook`)"

  4683. msgstr ""

  4684. 

  4685. #: ../../../CHANGELOG.md:2568

  4686. msgid "create a new `matrix_mautrix_facebook` Postgres database for it"

  4687. msgstr ""

  4688. 

  4689. #: ../../../CHANGELOG.md:2569

  4690. msgid "run [pgloader](https://pgloader.io/) manually (we import this bridge's data using default settings and it works well)"

  4691. msgstr ""

  4692. 

  4693. #: ../../../CHANGELOG.md:2570

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

  4695. msgstr ""

  4696. 

  4697. #: ../../../CHANGELOG.md:2571

  4698. msgid "switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: 'postgres'` in your `vars.yml` file)"

  4699. msgstr ""

  4700. 

  4701. #: ../../../CHANGELOG.md:2572

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

  4703. msgstr ""

  4704. 

  4705. #: ../../../CHANGELOG.md:2573

  4706. msgid "send a `login` message to the Facebook bridge bot again"

  4707. msgstr ""

  4708. 

  4709. #: ../../../CHANGELOG.md:2574

  4710. msgid "or, [stay on SQLite for a little longer (temporary solution)](#staying-on-sqlite-for-a-little-longer-temporary-solution)"

  4711. msgstr ""

  4712. 

  4713. #: ../../../CHANGELOG.md:2576

  4714. msgid "Staying on SQLite for a little longer (temporary solution)"

  4715. msgstr ""

  4716. 

  4717. #: ../../../CHANGELOG.md:2578

  4718. msgid "To keep using this bridge with SQLite for a little longer (**not recommended**), use the following configuration in your `vars.yml` file:"

  4719. msgstr ""

  4720. 

  4721. #: ../../../CHANGELOG.md:2588

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

  4723. msgstr ""

  4724. 

  4725. #: ../../../CHANGELOG.md:2591

  4726. msgid "2021-01-17"

  4727. msgstr ""

  4728. 

  4729. #: ../../../CHANGELOG.md:2593

  4730. msgid "matrix-corporal goes 2.0"

  4731. msgstr ""

  4732. 

  4733. #: ../../../CHANGELOG.md:2595

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

  4735. msgstr ""

  4736. 

  4737. #: ../../../CHANGELOG.md:2597

  4738. msgid "No manual intervention is required in the common case."

  4739. msgstr ""

  4740. 

  4741. #: ../../../CHANGELOG.md:2599

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

  4743. msgstr ""

  4744. 

  4745. #: ../../../CHANGELOG.md:2602

  4746. msgid "2021-01-14"

  4747. msgstr ""

  4748. 

  4749. #: ../../../CHANGELOG.md:2604

  4750. msgid "Moving from cronjobs to systemd timers"

  4751. msgstr ""

  4752. 

  4753. #: ../../../CHANGELOG.md:2606

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

  4755. msgstr ""

  4756. 

  4757. #: ../../../CHANGELOG.md:2608

  4758. msgid "The largest benefit of this is that we no longer require you to install a cron daemon, thus simplifying our install procedure."

  4759. msgstr ""

  4760. 

  4761. #: ../../../CHANGELOG.md:2610

  4762. msgid "The playbook will migrate you from cronjobs to systemd timers automatically. This is just a heads up."

  4763. msgstr ""

  4764. 

  4765. #: ../../../CHANGELOG.md:2613

  4766. msgid "2021-01-08"

  4767. msgstr ""

  4768. 

  4769. #: ../../../CHANGELOG.md:2615

  4770. msgid "(Breaking Change) New SSL configuration"

  4771. msgstr ""

  4772. 

  4773. #: ../../../CHANGELOG.md:2617

  4774. msgid "SSL configuration (protocols, ciphers) can now be more easily controlled thanks to us making use of configuration presets."

  4775. msgstr ""

  4776. 

  4777. #: ../../../CHANGELOG.md:2619

  4778. msgid "We define a few presets (old, intermediate, modern), following the [Mozilla SSL Configuration Generator](https://ssl-config.mozilla.org/#server=nginx)."

  4779. msgstr ""

  4780. 

  4781. #: ../../../CHANGELOG.md:2621

  4782. msgid "A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is used (defaults to `\"intermediate\"`)."

  4783. msgstr ""

  4784. 

  4785. #: ../../../CHANGELOG.md:2623

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

  4787. msgstr ""

  4788. 

  4789. #: ../../../CHANGELOG.md:2625

  4790. msgid "To revert to the old behaviour, set the following variables:"

  4791. msgstr ""

  4792. 

  4793. #: ../../../CHANGELOG.md:2632

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

  4795. msgstr ""

  4796. 

  4797. #: ../../../CHANGELOG.md:2635

  4798. msgid "2021-01-03"

  4799. msgstr ""

  4800. 

  4801. #: ../../../CHANGELOG.md:2637

  4802. msgid "Signal bridging support via mautrix-signal"

  4803. msgstr ""

  4804. 

  4805. #: ../../../CHANGELOG.md:2639

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

  4807. msgstr ""

  4808. 

  4809. #: ../../../CHANGELOG.md:2641

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

  4811. msgstr ""

  4812. 

  4813. #: ../../../CHANGELOG.md:2644

  4814. msgid "2020-12-23"

  4815. msgstr ""

  4816. 

  4817. #: ../../../CHANGELOG.md:2646

  4818. msgid "The big move to all-on-Postgres (potentially dangerous)"

  4819. msgstr ""

  4820. 

  4821. #: ../../../CHANGELOG.md:2648

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

  4823. msgstr ""

  4824. 

  4825. #: ../../../CHANGELOG.md:2650

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

  4827. msgstr ""

  4828. 

  4829. #: ../../../CHANGELOG.md:2652

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

  4831. msgstr ""

  4832. 

  4833. #: ../../../CHANGELOG.md:2654

  4834. msgid "Moving all services to Postgres brings a few **benefits** to us:"

  4835. msgstr ""

  4836. 

  4837. #: ../../../CHANGELOG.md:2656

  4838. msgid "**improved performance**"

  4839. msgstr ""

  4840. 

  4841. #: ../../../CHANGELOG.md:2657

  4842. msgid "**improved compatibility**. Most bridges are deprecating SQLite/nedb support or offer less features when not on Postgres."

  4843. msgstr ""

  4844. 

  4845. #: ../../../CHANGELOG.md:2658

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

  4847. msgstr ""

  4848. 

  4849. #: ../../../CHANGELOG.md:2659

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

  4851. msgstr ""

  4852. 

  4853. #: ../../../CHANGELOG.md:2661

  4854. msgid "Key takeway"

  4855. msgstr ""

  4856. 

  4857. #: ../../../CHANGELOG.md:2663

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

  4859. msgstr ""

  4860. 

  4861. #: ../../../CHANGELOG.md:2665

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

  4863. msgstr ""

  4864. 

  4865. #: ../../../CHANGELOG.md:2667

  4866. msgid "Opting-out of the Postgres migration"

  4867. msgstr ""

  4868. 

  4869. #: ../../../CHANGELOG.md:2669

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

  4871. msgstr ""

  4872. 

  4873. #: ../../../CHANGELOG.md:2671

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

  4875. msgstr ""

  4876. 

  4877. #: ../../../CHANGELOG.md:2673

  4878. msgid "Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them."

  4879. msgstr ""

  4880. 

  4881. #: ../../../CHANGELOG.md:2675

  4882. msgid "Going back to SQLite/nedb if things went wrong"

  4883. msgstr ""

  4884. 

  4885. #: ../../../CHANGELOG.md:2677

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

  4887. msgstr ""

  4888. 

  4889. #: ../../../CHANGELOG.md:2679

  4890. msgid "stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"

  4891. msgstr ""

  4892. 

  4893. #: ../../../CHANGELOG.md:2680

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

  4895. msgstr ""

  4896. 

  4897. #: ../../../CHANGELOG.md:2681

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

  4899. msgstr ""

  4900. 

  4901. #: ../../../CHANGELOG.md:2682

  4902. msgid "re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`)"

  4903. msgstr ""

  4904. 

  4905. #: ../../../CHANGELOG.md:2683

  4906. msgid "[get in touch](README.md#support) with us"

  4907. msgstr ""

  4908. 

  4909. #: ../../../CHANGELOG.md:2685

  4910. msgid "2020-12-11"

  4911. msgstr ""

  4912. 

  4913. #: ../../../CHANGELOG.md:2687

  4914. msgid "synapse-janitor support removed"

  4915. msgstr ""

  4916. 

  4917. #: ../../../CHANGELOG.md:2689

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

  4919. msgstr ""

  4920. 

  4921. #: ../../../CHANGELOG.md:2691

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

  4923. msgstr ""

  4924. 

  4925. #: ../../../CHANGELOG.md:2693

  4926. msgid "Docker 20.10 is here"

  4927. msgstr ""

  4928. 

  4929. #: ../../../CHANGELOG.md:2695

  4930. msgid "(No need to do anything special in relation to this. Just something to keep in mind)"

  4931. msgstr ""

  4932. 

  4933. #: ../../../CHANGELOG.md:2697

  4934. msgid "Docker 20.10 got released recently and your server will likely get it the next time you update."

  4935. msgstr ""

  4936. 

  4937. #: ../../../CHANGELOG.md:2699

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

  4939. msgstr ""

  4940. 

  4941. #: ../../../CHANGELOG.md:2702

  4942. msgid "2020-12-08"

  4943. msgstr ""

  4944. 

  4945. #: ../../../CHANGELOG.md:2704

  4946. msgid "openid APIs exposed by default on the federation port when federation disabled"

  4947. msgstr ""

  4948. 

  4949. #: ../../../CHANGELOG.md:2706

  4950. msgid "We've changed some defaults. People running with our default configuration (federation enabled), are not affected at all."

  4951. msgstr ""

  4952. 

  4953. #: ../../../CHANGELOG.md:2708

  4954. msgid "If you are running an unfederated server (`matrix_synapse_federation_enabled: false`), this may be of interest to you."

  4955. msgstr ""

  4956. 

  4957. #: ../../../CHANGELOG.md:2710

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

  4959. msgstr ""

  4960. 

  4961. #: ../../../CHANGELOG.md:2713

  4962. msgid "2020-11-27"

  4963. msgstr ""

  4964. 

  4965. #: ../../../CHANGELOG.md:2715

  4966. msgid "Recent Jitsi updates may require configuration changes"

  4967. msgstr ""

  4968. 

  4969. #: ../../../CHANGELOG.md:2717

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

  4971. msgstr ""

  4972. 

  4973. #: ../../../CHANGELOG.md:2719

  4974. msgid "**If you use our default Jitsi settings, you won't have to do anything.**"

  4975. msgstr ""

  4976. 

  4977. #: ../../../CHANGELOG.md:2721

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

  4979. msgstr ""

  4980. 

  4981. #: ../../../CHANGELOG.md:2723

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

  4983. msgstr ""

  4984. 

  4985. #: ../../../CHANGELOG.md:2725

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

  4987. msgstr ""

  4988. 

  4989. #: ../../../CHANGELOG.md:2728

  4990. msgid "2020-11-23"

  4991. msgstr ""

  4992. 

  4993. #: ../../../CHANGELOG.md:2730

  4994. #: ../../../CHANGELOG.md:2738

  4995. msgid "Breaking change matrix-sms-bridge"

  4996. msgstr ""

  4997. 

  4998. #: ../../../CHANGELOG.md:2732

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

  5000. msgstr ""

  5001. 

  5002. #: ../../../CHANGELOG.md:2734

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

  5004. msgstr ""

  5005. 

  5006. #: ../../../CHANGELOG.md:2736

  5007. msgid "2020-11-13"

  5008. msgstr ""

  5009. 

  5010. #: ../../../CHANGELOG.md:2740

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

  5012. msgstr ""

  5013. 

  5014. #: ../../../CHANGELOG.md:2742

  5015. msgid "Add the following to your `vars.yml` file: `matrix_sms_bridge_container_extra_arguments=['--env SPRING_PROFILES_ACTIVE=initialsync']`"

  5016. msgstr ""

  5017. 

  5018. #: ../../../CHANGELOG.md:2743

  5019. msgid "Login to your host shell and remove old systemd file from your host: `rm /etc/systemd/system/matrix-sms-bridge-database.service`"

  5020. msgstr ""

  5021. 

  5022. #: ../../../CHANGELOG.md:2744

  5023. msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-sms-bridge,start`"

  5024. msgstr ""

  5025. 

  5026. #: ../../../CHANGELOG.md:2745

  5027. msgid "Login to your host shell and check the logs with `journalctl -u matrix-sms-bridge` until the sync finished."

  5028. msgstr ""

  5029. 

  5030. #: ../../../CHANGELOG.md:2746

  5031. msgid "Remove the var from the first step."

  5032. msgstr ""

  5033. 

  5034. #: ../../../CHANGELOG.md:2747

  5035. msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`."

  5036. msgstr ""

  5037. 

  5038. #: ../../../CHANGELOG.md:2749

  5039. msgid "2020-11-10"

  5040. msgstr ""

  5041. 

  5042. #: ../../../CHANGELOG.md:2751

  5043. msgid "Dynamic DNS support"

  5044. msgstr ""

  5045. 

  5046. #: ../../../CHANGELOG.md:2753

  5047. msgid "Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook can now manage Dynamic DNS for you using [ddclient](https://ddclient.net/)."

  5048. msgstr ""

  5049. 

  5050. #: ../../../CHANGELOG.md:2755

  5051. msgid "To learn more, follow our [Dynamic DNS docs page](docs/configuring-playbook-dynamic-dns.md)."

  5052. msgstr ""

  5053. 

  5054. #: ../../../CHANGELOG.md:2758

  5055. msgid "2020-10-28"

  5056. msgstr ""

  5057. 

  5058. #: ../../../CHANGELOG.md:2760

  5059. msgid "(Compatibility Break) https://matrix.example.com/ now redirects to https://element.example.com/"

  5060. msgstr ""

  5061. 

  5062. #: ../../../CHANGELOG.md:2762

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

  5064. msgstr ""

  5065. 

  5066. #: ../../../CHANGELOG.md:2764

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

  5068. msgstr ""

  5069. 

  5070. #: ../../../CHANGELOG.md:2766

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

  5072. msgstr ""

  5073. 

  5074. #: ../../../CHANGELOG.md:2768

  5075. 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: \"\"`)."

  5076. msgstr ""

  5077. 

  5078. #: ../../../CHANGELOG.md:2771

  5079. msgid "2020-10-26"

  5080. msgstr ""

  5081. 

  5082. #: ../../../CHANGELOG.md:2773

  5083. msgid "(Compatibility Break) /_synapse/admin is no longer publicly exposed by default"

  5084. msgstr ""

  5085. 

  5086. #: ../../../CHANGELOG.md:2775

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

  5088. msgstr ""

  5089. 

  5090. #: ../../../CHANGELOG.md:2777

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

  5092. msgstr ""

  5093. 

  5094. #: ../../../CHANGELOG.md:2779

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

  5096. msgstr ""

  5097. 

  5098. #: ../../../CHANGELOG.md:2786

  5099. msgid "2020-10-02"

  5100. msgstr ""

  5101. 

  5102. #: ../../../CHANGELOG.md:2788

  5103. msgid "Minimum Ansible version raised to v2.7.0"

  5104. msgstr ""

  5105. 

  5106. #: ../../../CHANGELOG.md:2790

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

  5108. msgstr ""

  5109. 

  5110. #: ../../../CHANGELOG.md:2792

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

  5112. msgstr ""

  5113. 

  5114. #: ../../../CHANGELOG.md:2794

  5115. msgid "Our [Ansible docs page](docs/ansible.md) contains information on how to run a more up-to-date version of Ansible."

  5116. msgstr ""

  5117. 

  5118. #: ../../../CHANGELOG.md:2797

  5119. msgid "2020-10-01"

  5120. msgstr ""

  5121. 

  5122. #: ../../../CHANGELOG.md:2799

  5123. msgid "Postgres 13 support"

  5124. msgstr ""

  5125. 

  5126. #: ../../../CHANGELOG.md:2801

  5127. msgid "The playbook now installs [Postgres 13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) by default."

  5128. msgstr ""

  5129. 

  5130. #: ../../../CHANGELOG.md:2803

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

  5132. msgstr ""

  5133. 

  5134. #: ../../../CHANGELOG.md:2805

  5135. msgid "2020-09-01"

  5136. msgstr ""

  5137. 

  5138. #: ../../../CHANGELOG.md:2807

  5139. msgid "matrix-registration support"

  5140. msgstr ""

  5141. 

  5142. #: ../../../CHANGELOG.md:2809

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

  5144. msgstr ""

  5145. 

  5146. #: ../../../CHANGELOG.md:2811

  5147. msgid "See our [Setting up matrix-registration](docs/configuring-playbook-matrix-registration.md) documentation page to get started."

  5148. msgstr ""

  5149. 

  5150. #: ../../../CHANGELOG.md:2814

  5151. msgid "2020-08-21"

  5152. msgstr ""

  5153. 

  5154. #: ../../../CHANGELOG.md:2816

  5155. msgid "rust-synapse-compress-state support"

  5156. msgstr ""

  5157. 

  5158. #: ../../../CHANGELOG.md:2818

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

  5160. msgstr ""

  5161. 

  5162. #: ../../../CHANGELOG.md:2820

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

  5164. msgstr ""

  5165. 

  5166. #: ../../../CHANGELOG.md:2823

  5167. msgid "2020-07-22"

  5168. msgstr ""

  5169. 

  5170. #: ../../../CHANGELOG.md:2825

  5171. msgid "Synapse Admin support"

  5172. msgstr ""

  5173. 

  5174. #: ../../../CHANGELOG.md:2827

  5175. msgid "The playbook can now help you set up [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin)."

  5176. msgstr ""

  5177. 

  5178. #: ../../../CHANGELOG.md:2829

  5179. msgid "See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-admin.md) documentation to get started."

  5180. msgstr ""

  5181. 

  5182. #: ../../../CHANGELOG.md:2832

  5183. msgid "2020-07-20"

  5184. msgstr ""

  5185. 

  5186. #: ../../../CHANGELOG.md:2834

  5187. msgid "matrix-reminder-bot support"

  5188. msgstr ""

  5189. 

  5190. #: ../../../CHANGELOG.md:2836

  5191. msgid "The playbook can now help you set up [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)."

  5192. msgstr ""

  5193. 

  5194. #: ../../../CHANGELOG.md:2838

  5195. msgid "See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-matrix-reminder-bot.md) documentation to get started."

  5196. msgstr ""

  5197. 

  5198. #: ../../../CHANGELOG.md:2841

  5199. msgid "2020-07-17"

  5200. msgstr ""

  5201. 

  5202. #: ../../../CHANGELOG.md:2843

  5203. msgid "(Compatibility Break) Riot is now Element"

  5204. msgstr ""

  5205. 

  5206. #: ../../../CHANGELOG.md:2845

  5207. msgid "As per the official announcement, [Riot has been rebraned to Element](https://element.io/blog/welcome-to-element/)."

  5208. msgstr ""

  5209. 

  5210. #: ../../../CHANGELOG.md:2847

  5211. msgid "The playbook follows suit. Existing installations have a few options for how to handle this."

  5212. msgstr ""

  5213. 

  5214. #: ../../../CHANGELOG.md:2849

  5215. msgid "See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md#migrating-to-element) documentation page for more details."

  5216. msgstr ""

  5217. 

  5218. #: ../../../CHANGELOG.md:2852

  5219. msgid "2020-07-03"

  5220. msgstr ""

  5221. 

  5222. #: ../../../CHANGELOG.md:2854

  5223. msgid "Steam bridging support via mx-puppet-steam"

  5224. msgstr ""

  5225. 

  5226. #: ../../../CHANGELOG.md:2856

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

  5228. msgstr ""

  5229. 

  5230. #: ../../../CHANGELOG.md:2859

  5231. msgid "2020-07-01"

  5232. msgstr ""

  5233. 

  5234. #: ../../../CHANGELOG.md:2861

  5235. msgid "Discord bridging support via mx-puppet-discord"

  5236. msgstr ""

  5237. 

  5238. #: ../../../CHANGELOG.md:2863

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

  5240. msgstr ""

  5241. 

  5242. #: ../../../CHANGELOG.md:2865

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

  5244. msgstr ""

  5245. 

  5246. #: ../../../CHANGELOG.md:2868

  5247. msgid "2020-06-30"

  5248. msgstr ""

  5249. 

  5250. #: ../../../CHANGELOG.md:2870

  5251. msgid "Instagram and Twitter bridging support"

  5252. msgstr ""

  5253. 

  5254. #: ../../../CHANGELOG.md:2872

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

  5256. msgstr ""

  5257. 

  5258. #: ../../../CHANGELOG.md:2874

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

  5260. msgstr ""

  5261. 

  5262. #: ../../../CHANGELOG.md:2877

  5263. msgid "2020-06-28"

  5264. msgstr ""

  5265. 

  5266. #: ../../../CHANGELOG.md:2879

  5267. msgid "(Post Mortem / fixed Security Issue) Re-enabling User Directory search powered by the ma1sd Identity Server"

  5268. msgstr ""

  5269. 

  5270. #: ../../../CHANGELOG.md:2881

  5271. #: ../../../CHANGELOG.md:2910

  5272. msgid "User Directory search requests used to go to the ma1sd identity server by default, which queried its own stores and the Synapse database."

  5273. msgstr ""

  5274. 

  5275. #: ../../../CHANGELOG.md:2883

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

  5277. msgstr ""

  5278. 

  5279. #: ../../../CHANGELOG.md:2885

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

  5281. msgstr ""

  5282. 

  5283. #: ../../../CHANGELOG.md:2887

  5284. msgid "As always, re-running the playbook is enough to get the updated bits."

  5285. msgstr ""

  5286. 

  5287. #: ../../../CHANGELOG.md:2889

  5288. msgid "2020-06-11"

  5289. msgstr ""

  5290. 

  5291. #: ../../../CHANGELOG.md:2891

  5292. msgid "SMS bridging requires db reset"

  5293. msgstr ""

  5294. 

  5295. #: ../../../CHANGELOG.md:2893

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

  5297. msgstr ""

  5298. 

  5299. #: ../../../CHANGELOG.md:2895

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

  5301. msgstr ""

  5302. 

  5303. #: ../../../CHANGELOG.md:2897

  5304. msgid "2020-06-05"

  5305. msgstr ""

  5306. 

  5307. #: ../../../CHANGELOG.md:2899

  5308. msgid "SMS bridging support"

  5309. msgstr ""

  5310. 

  5311. #: ../../../CHANGELOG.md:2901

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

  5313. msgstr ""

  5314. 

  5315. #: ../../../CHANGELOG.md:2903

  5316. msgid "See our [Setting up Matrix SMS bridging](docs/configuring-playbook-bridge-matrix-bridge-sms.md) documentation page for getting started."

  5317. msgstr ""

  5318. 

  5319. #: ../../../CHANGELOG.md:2906

  5320. msgid "2020-05-19"

  5321. msgstr ""

  5322. 

  5323. #: ../../../CHANGELOG.md:2908

  5324. msgid "(Compatibility Break / Security Issue) Disabling User Directory search powered by the ma1sd Identity Server"

  5325. msgstr ""

  5326. 

  5327. #: ../../../CHANGELOG.md:2912

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

  5329. msgstr ""

  5330. 

  5331. #: ../../../CHANGELOG.md:2914

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

  5333. msgstr ""

  5334. 

  5335. #: ../../../CHANGELOG.md:2916

  5336. 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 }}\"`"

  5337. msgstr ""

  5338. 

  5339. #: ../../../CHANGELOG.md:2919

  5340. msgid "2020-04-28"

  5341. msgstr ""

  5342. 

  5343. #: ../../../CHANGELOG.md:2921

  5344. msgid "Newer IRC bridge (with potential breaking change)"

  5345. msgstr ""

  5346. 

  5347. #: ../../../CHANGELOG.md:2923

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

  5349. msgstr ""

  5350. 

  5351. #: ../../../CHANGELOG.md:2932

  5352. msgid "2020-04-23"

  5353. msgstr ""

  5354. 

  5355. #: ../../../CHANGELOG.md:2934

  5356. #: ../../../CHANGELOG.md:3165

  5357. msgid "Slack bridging support"

  5358. msgstr ""

  5359. 

  5360. #: ../../../CHANGELOG.md:2936

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

  5362. msgstr ""

  5363. 

  5364. #: ../../../CHANGELOG.md:2938

  5365. msgid "See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-bridge-mx-puppet-slack.md) documentation page for getting started."

  5366. msgstr ""

  5367. 

  5368. #: ../../../CHANGELOG.md:2941

  5369. msgid "2020-04-09"

  5370. msgstr ""

  5371. 

  5372. #: ../../../CHANGELOG.md:2943

  5373. msgid "Skype bridging support"

  5374. msgstr ""

  5375. 

  5376. #: ../../../CHANGELOG.md:2945

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

  5378. msgstr ""

  5379. 

  5380. #: ../../../CHANGELOG.md:2947

  5381. msgid "See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md) documentation page for getting started."

  5382. msgstr ""

  5383. 

  5384. #: ../../../CHANGELOG.md:2950

  5385. msgid "2020-04-05"

  5386. msgstr ""

  5387. 

  5388. #: ../../../CHANGELOG.md:2952

  5389. msgid "Private Jitsi support"

  5390. msgstr ""

  5391. 

  5392. #: ../../../CHANGELOG.md:2954

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

  5394. msgstr ""

  5395. 

  5396. #: ../../../CHANGELOG.md:2956

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

  5398. msgstr ""

  5399. 

  5400. #: ../../../CHANGELOG.md:2958

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

  5402. msgstr ""

  5403. 

  5404. #: ../../../CHANGELOG.md:2961

  5405. msgid "2020-04-03"

  5406. msgstr ""

  5407. 

  5408. #: ../../../CHANGELOG.md:2963

  5409. msgid "(Potential Backward Compatibility Break) ma1sd replaces mxisd"

  5410. msgstr ""

  5411. 

  5412. #: ../../../CHANGELOG.md:2965

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

  5414. msgstr ""

  5415. 

  5416. #: ../../../CHANGELOG.md:2967

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

  5418. msgstr ""

  5419. 

  5420. #: ../../../CHANGELOG.md:2969

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

  5422. msgstr ""

  5423. 

  5424. #: ../../../CHANGELOG.md:2972

  5425. msgid "2020-03-29"

  5426. msgstr ""

  5427. 

  5428. #: ../../../CHANGELOG.md:2974

  5429. msgid "Archlinux support"

  5430. msgstr ""

  5431. 

  5432. #: ../../../CHANGELOG.md:2976

  5433. msgid "Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts, the playbook now supports installing to an [Archlinux](https://www.archlinux.org/) server."

  5434. msgstr ""

  5435. 

  5436. #: ../../../CHANGELOG.md:2979

  5437. msgid "2020-03-24"

  5438. msgstr ""

  5439. 

  5440. #: ../../../CHANGELOG.md:2981

  5441. msgid "Jitsi support"

  5442. msgstr ""

  5443. 

  5444. #: ../../../CHANGELOG.md:2983

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

  5446. msgstr ""

  5447. 

  5448. #: ../../../CHANGELOG.md:2985

  5449. msgid "See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to get started."

  5450. msgstr ""

  5451. 

  5452. #: ../../../CHANGELOG.md:2988

  5453. msgid "2020-03-15"

  5454. msgstr ""

  5455. 

  5456. #: ../../../CHANGELOG.md:2990

  5457. msgid "Raspberry Pi support"

  5458. msgstr ""

  5459. 

  5460. #: ../../../CHANGELOG.md:2992

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

  5462. msgstr ""

  5463. 

  5464. #: ../../../CHANGELOG.md:2994

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

  5466. msgstr ""

  5467. 

  5468. #: ../../../CHANGELOG.md:2997

  5469. msgid "2020-02-26"

  5470. msgstr ""

  5471. 

  5472. #: ../../../CHANGELOG.md:2999

  5473. msgid "Riot-web themes are here"

  5474. msgstr ""

  5475. 

  5476. #: ../../../CHANGELOG.md:3001

  5477. msgid "The playbook now makes it easy to install custom riot-web themes."

  5478. msgstr ""

  5479. 

  5480. #: ../../../CHANGELOG.md:3003

  5481. msgid "To learn more, take a look at our [riot-web documentation on Themes](docs/configuring-playbook-riot-web.md#themes)."

  5482. msgstr ""

  5483. 

  5484. #: ../../../CHANGELOG.md:3006

  5485. msgid "2020-02-24"

  5486. msgstr ""

  5487. 

  5488. #: ../../../CHANGELOG.md:3008

  5489. msgid "Customize the server name in Riot's login page"

  5490. msgstr ""

  5491. 

  5492. #: ../../../CHANGELOG.md:3010

  5493. msgid "You can now customize the server name string that Riot-web displays in its login page."

  5494. msgstr ""

  5495. 

  5496. #: ../../../CHANGELOG.md:3012

  5497. msgid "These playbook variables, with these default values, have been added:"

  5498. msgstr ""

  5499. 

  5500. #: ../../../CHANGELOG.md:3018

  5501. 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\"."

  5502. msgstr ""

  5503. 

  5504. #: ../../../CHANGELOG.md:3020

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

  5506. msgstr ""

  5507. 

  5508. #: ../../../CHANGELOG.md:3023

  5509. msgid "2020-01-30"

  5510. msgstr ""

  5511. 

  5512. #: ../../../CHANGELOG.md:3025

  5513. msgid "Disabling TLSv1.1"

  5514. msgstr ""

  5515. 

  5516. #: ../../../CHANGELOG.md:3027

  5517. msgid "To improve security, we've removed TLSv1.1 support from our default matrix-nginx-proxy configuration."

  5518. msgstr ""

  5519. 

  5520. #: ../../../CHANGELOG.md:3029

  5521. 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\"`"

  5522. msgstr ""

  5523. 

  5524. #: ../../../CHANGELOG.md:3032

  5525. msgid "2020-01-21"

  5526. msgstr ""

  5527. 

  5528. #: ../../../CHANGELOG.md:3034

  5529. msgid "Postgres collation changes (action required!)"

  5530. msgstr ""

  5531. 

  5532. #: ../../../CHANGELOG.md:3036

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

  5534. msgstr ""

  5535. 

  5536. #: ../../../CHANGELOG.md:3038

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

  5538. msgstr ""

  5539. 

  5540. #: ../../../CHANGELOG.md:3040

  5541. msgid "To avoid future problems, we recommend that you run the following command:"

  5542. msgstr ""

  5543. 

  5544. #: ../../../CHANGELOG.md:3046

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

  5546. msgstr ""

  5547. 

  5548. #: ../../../CHANGELOG.md:3049

  5549. msgid "2020-01-14"

  5550. msgstr ""

  5551. 

  5552. #: ../../../CHANGELOG.md:3051

  5553. msgid "Added support for Appservice Webhooks"

  5554. msgstr ""

  5555. 

  5556. #: ../../../CHANGELOG.md:3053

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

  5558. msgstr ""

  5559. 

  5560. #: ../../../CHANGELOG.md:3055

  5561. msgid "Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-playbook-bridge-appservice-webhooks.md)."

  5562. msgstr ""

  5563. 

  5564. #: ../../../CHANGELOG.md:3058

  5565. msgid "2020-01-12"

  5566. msgstr ""

  5567. 

  5568. #: ../../../CHANGELOG.md:3060

  5569. msgid "Added support for automatic Double Puppeting for all Mautrix bridges"

  5570. msgstr ""

  5571. 

  5572. #: ../../../CHANGELOG.md:3062

  5573. msgid "Double Puppeting can now be easily enabled for all Mautrix bridges supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)."

  5574. msgstr ""

  5575. 

  5576. #: ../../../CHANGELOG.md:3064

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

  5578. msgstr ""

  5579. 

  5580. #: ../../../CHANGELOG.md:3066

  5581. msgid "To get started, following the playbook's documentation for the bridge you'd like to configure."

  5582. msgstr ""

  5583. 

  5584. #: ../../../CHANGELOG.md:3069

  5585. msgid "2019-12-06"

  5586. msgstr ""

  5587. 

  5588. #: ../../../CHANGELOG.md:3071

  5589. msgid "Added support for an alternative method for using another webserver"

  5590. msgstr ""

  5591. 

  5592. #: ../../../CHANGELOG.md:3073

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

  5594. msgstr ""

  5595. 

  5596. #: ../../../CHANGELOG.md:3075

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

  5598. msgstr ""

  5599. 

  5600. #: ../../../CHANGELOG.md:3077

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

  5602. msgstr ""

  5603. 

  5604. #: ../../../CHANGELOG.md:3080

  5605. msgid "2019-11-10"

  5606. msgstr ""

  5607. 

  5608. #: ../../../CHANGELOG.md:3082

  5609. msgid "Tightened security around room directory publishing"

  5610. msgstr ""

  5611. 

  5612. #: ../../../CHANGELOG.md:3084

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

  5614. msgstr ""

  5615. 

  5616. #: ../../../CHANGELOG.md:3086

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

  5618. msgstr ""

  5619. 

  5620. #: ../../../CHANGELOG.md:3088

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

  5622. msgstr ""

  5623. 

  5624. #: ../../../CHANGELOG.md:3091

  5625. msgid "2019-10-05"

  5626. msgstr ""

  5627. 

  5628. #: ../../../CHANGELOG.md:3093

  5629. msgid "Improved Postgres upgrading/importing"

  5630. msgstr ""

  5631. 

  5632. #: ../../../CHANGELOG.md:3095

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

  5634. msgstr ""

  5635. 

  5636. #: ../../../CHANGELOG.md:3097

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

  5638. msgstr ""

  5639. 

  5640. #: ../../../CHANGELOG.md:3099

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

  5642. msgstr ""

  5643. 

  5644. #: ../../../CHANGELOG.md:3101

  5645. msgid "Additionally, Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) now uses gzipped dump files by default, to minimize disk space usage."

  5646. msgstr ""

  5647. 

  5648. #: ../../../CHANGELOG.md:3104

  5649. msgid "2019-10-04"

  5650. msgstr ""

  5651. 

  5652. #: ../../../CHANGELOG.md:3106

  5653. msgid "Postgres 12 support"

  5654. msgstr ""

  5655. 

  5656. #: ../../../CHANGELOG.md:3108

  5657. msgid "The playbook now installs [Postgres 12](https://www.postgresql.org/about/news/1976/) by default."

  5658. msgstr ""

  5659. 

  5660. #: ../../../CHANGELOG.md:3110

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

  5662. msgstr ""

  5663. 

  5664. #: ../../../CHANGELOG.md:3113

  5665. msgid "2019-10-03"

  5666. msgstr ""

  5667. 

  5668. #: ../../../CHANGELOG.md:3115

  5669. msgid "Synapse 1.4.0"

  5670. msgstr ""

  5671. 

  5672. #: ../../../CHANGELOG.md:3117

  5673. 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."

  5674. msgstr ""

  5675. 

  5676. #: ../../../CHANGELOG.md:3119

  5677. 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: ~`)."

  5678. msgstr ""

  5679. 

  5680. #: ../../../CHANGELOG.md:3121

  5681. 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."

  5682. msgstr ""

  5683. 

  5684. #: ../../../CHANGELOG.md:3123

  5685. 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."

  5686. msgstr ""

  5687. 

  5688. #: ../../../CHANGELOG.md:3126

  5689. msgid "2019-09-09"

  5690. msgstr ""

  5691. 

  5692. #: ../../../CHANGELOG.md:3128

  5693. msgid "Synapse Simple Antispam support"

  5694. msgstr ""

  5695. 

  5696. #: ../../../CHANGELOG.md:3130

  5697. 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."

  5698. msgstr ""

  5699. 

  5700. #: ../../../CHANGELOG.md:3132

  5701. msgid "From now on, you can easily install and configure this spam checker module through the playbook."

  5702. msgstr ""

  5703. 

  5704. #: ../../../CHANGELOG.md:3134

  5705. msgid "Learn more in [Setting up Synapse Simple Antispam](docs/configuring-playbook-synapse-simple-antispam.md)."

  5706. msgstr ""

  5707. 

  5708. #: ../../../CHANGELOG.md:3137

  5709. msgid "2019-08-25"

  5710. msgstr ""

  5711. 

  5712. #: ../../../CHANGELOG.md:3139

  5713. msgid "Extensible Riot-web configuration"

  5714. msgstr ""

  5715. 

  5716. #: ../../../CHANGELOG.md:3141

  5717. msgid "Similarly to [Extensible Synapse configuration](#extensible-synapse-configuration) (below), Riot-web configuration is also extensible now."

  5718. msgstr ""

  5719. 

  5720. #: ../../../CHANGELOG.md:3143

  5721. 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."

  5722. msgstr ""

  5723. 

  5724. #: ../../../CHANGELOG.md:3145

  5725. 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."

  5726. msgstr ""

  5727. 

  5728. #: ../../../CHANGELOG.md:3147

  5729. msgid "Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-web.md)."

  5730. msgstr ""

  5731. 

  5732. #: ../../../CHANGELOG.md:3150

  5733. msgid "2019-08-22"

  5734. msgstr ""

  5735. 

  5736. #: ../../../CHANGELOG.md:3152

  5737. msgid "Extensible Synapse configuration"

  5738. msgstr ""

  5739. 

  5740. #: ../../../CHANGELOG.md:3154

  5741. 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."

  5742. msgstr ""

  5743. 

  5744. #: ../../../CHANGELOG.md:3156

  5745. 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."

  5746. msgstr ""

  5747. 

  5748. #: ../../../CHANGELOG.md:3158

  5749. 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."

  5750. msgstr ""

  5751. 

  5752. #: ../../../CHANGELOG.md:3160

  5753. msgid "Learn more here in [Configuring Synapse](docs/configuring-playbook-synapse.md)."

  5754. msgstr ""

  5755. 

  5756. #: ../../../CHANGELOG.md:3163

  5757. msgid "2019-08-21"

  5758. msgstr ""

  5759. 

  5760. #: ../../../CHANGELOG.md:3167

  5761. 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."

  5762. msgstr ""

  5763. 

  5764. #: ../../../CHANGELOG.md:3169

  5765. msgid "Additional details are available in [Setting up Appservice Slack bridging](docs/configuring-playbook-bridge-appservice-slack.md)."

  5766. msgstr ""

  5767. 

  5768. #: ../../../CHANGELOG.md:3171

  5769. msgid "Google Hangouts bridging support"

  5770. msgstr ""

  5771. 

  5772. #: ../../../CHANGELOG.md:3173

  5773. 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."

  5774. msgstr ""

  5775. 

  5776. #: ../../../CHANGELOG.md:3175

  5777. msgid "Additional details are available in [Setting up Mautrix Hangouts bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)."

  5778. msgstr ""

  5779. 

  5780. #: ../../../CHANGELOG.md:3178

  5781. msgid "2019-08-05"

  5782. msgstr ""

  5783. 

  5784. #: ../../../CHANGELOG.md:3180

  5785. msgid "Email2Matrix support"

  5786. msgstr ""

  5787. 

  5788. #: ../../../CHANGELOG.md:3182

  5789. msgid "Support for [Email2Matrix](https://github.com/devture/email2matrix) has been added."

  5790. msgstr ""

  5791. 

  5792. #: ../../../CHANGELOG.md:3184

  5793. msgid "It's an optional feature that you can enable via the playbook."

  5794. msgstr ""

  5795. 

  5796. #: ../../../CHANGELOG.md:3186

  5797. msgid "To learn more, see the [playbook's documentation on Email2Matrix](./docs/configuring-playbook-email2matrix.md)."

  5798. msgstr ""

  5799. 

  5800. #: ../../../CHANGELOG.md:3189

  5801. msgid "2019-08-03"

  5802. msgstr ""

  5803. 

  5804. #: ../../../CHANGELOG.md:3191

  5805. msgid "Synapse logging level has been reduced to WARNING"

  5806. msgstr ""

  5807. 

  5808. #: ../../../CHANGELOG.md:3193

  5809. 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`."

  5810. msgstr ""

  5811. 

  5812. #: ../../../CHANGELOG.md:3195

  5813. msgid "This greatly reduces the number of log messages that are being logged, leading to:"

  5814. msgstr ""

  5815. 

  5816. #: ../../../CHANGELOG.md:3197

  5817. msgid "much less disk space dedicated to Synapse and thus, logs kept for longer"

  5818. msgstr ""

  5819. 

  5820. #: ../../../CHANGELOG.md:3198

  5821. msgid "easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages, as they're not longer buried in thousands of non-important `INFO` messages"

  5822. msgstr ""

  5823. 

  5824. #: ../../../CHANGELOG.md:3200

  5825. 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)."

  5826. msgstr ""

  5827. 

  5828. #: ../../../CHANGELOG.md:3203

  5829. msgid "2019-07-08"

  5830. msgstr ""

  5831. 

  5832. #: ../../../CHANGELOG.md:3205

  5833. msgid "Synapse Maintenance docs and synapse-janitor support are available"

  5834. msgstr ""

  5835. 

  5836. #: ../../../CHANGELOG.md:3207

  5837. msgid "The playbook can now help you with Synapse's maintenance."

  5838. msgstr ""

  5839. 

  5840. #: ../../../CHANGELOG.md:3209

  5841. 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)."

  5842. msgstr ""

  5843. 

  5844. #: ../../../CHANGELOG.md:3211

  5845. 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."

  5846. msgstr ""

  5847. 

  5848. #: ../../../CHANGELOG.md:3213

  5849. msgid "(BC Break) Rename run control variables"

  5850. msgstr ""

  5851. 

  5852. #: ../../../CHANGELOG.md:3215

  5853. msgid "Some internal playbook control variables have been renamed."

  5854. msgstr ""

  5855. 

  5856. #: ../../../CHANGELOG.md:3217

  5857. 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."

  5858. msgstr ""

  5859. 

  5860. #: ../../../CHANGELOG.md:3219

  5861. msgid "The following variables have been renamed:"

  5862. msgstr ""

  5863. 

  5864. #: ../../../CHANGELOG.md:3221

  5865. msgid "from `run_import_postgres` to `run_postgres_import`"

  5866. msgstr ""

  5867. 

  5868. #: ../../../CHANGELOG.md:3222

  5869. msgid "from `run_import_sqlite_db` to `run_postgres_import_sqlite_db`"

  5870. msgstr ""

  5871. 

  5872. #: ../../../CHANGELOG.md:3223

  5873. msgid "from `run_upgrade_postgres` to `run_postgres_upgrade`"

  5874. msgstr ""

  5875. 

  5876. #: ../../../CHANGELOG.md:3224

  5877. msgid "from `run_import_media_store` to `run_synapse_import_media_store`"

  5878. msgstr ""

  5879. 

  5880. #: ../../../CHANGELOG.md:3225

  5881. msgid "from `run_register_user` to `run_synapse_register_user`"

  5882. msgstr ""

  5883. 

  5884. #: ../../../CHANGELOG.md:3226

  5885. msgid "from `run_update_user_password` to `run_synapse_update_user_password`"

  5886. msgstr ""

  5887. 

  5888. #: ../../../CHANGELOG.md:3229

  5889. msgid "2019-07-04"

  5890. msgstr ""

  5891. 

  5892. #: ../../../CHANGELOG.md:3231

  5893. msgid "Synapse no longer logs to text files"

  5894. msgstr ""

  5895. 

  5896. #: ../../../CHANGELOG.md:3233

  5897. 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*`)."

  5898. msgstr ""

  5899. 

  5900. #: ../../../CHANGELOG.md:3235

  5901. 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`"

  5902. msgstr ""

  5903. 

  5904. #: ../../../CHANGELOG.md:3237

  5905. msgid "Because of this, the following variables have become obsolete and were removed:"

  5906. msgstr ""

  5907. 

  5908. #: ../../../CHANGELOG.md:3239

  5909. msgid "`matrix_synapse_max_log_file_size_mb`"

  5910. msgstr ""

  5911. 

  5912. #: ../../../CHANGELOG.md:3240

  5913. msgid "`matrix_synapse_max_log_files_count`"

  5914. msgstr ""

  5915. 

  5916. #: ../../../CHANGELOG.md:3242

  5917. 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*`)."

  5918. msgstr ""

  5919. 

  5920. #: ../../../CHANGELOG.md:3244

  5921. 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`)."

  5922. msgstr ""

  5923. 

  5924. #: ../../../CHANGELOG.md:3247

  5925. msgid "2019-06-27"

  5926. msgstr ""

  5927. 

  5928. #: ../../../CHANGELOG.md:3249

  5929. msgid "(BC Break) Discord bridge configuration is now entirely managed by the playbook"

  5930. msgstr ""

  5931. 

  5932. #: ../../../CHANGELOG.md:3251

  5933. 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."

  5934. msgstr ""

  5935. 

  5936. #: ../../../CHANGELOG.md:3253

  5937. msgid "From now on, the playbook will keep both configuration files sync for you."

  5938. msgstr ""

  5939. 

  5940. #: ../../../CHANGELOG.md:3255

  5941. 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."

  5942. msgstr ""

  5943. 

  5944. #: ../../../CHANGELOG.md:3257

  5945. msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-discord/config`)."

  5946. msgstr ""

  5947. 

  5948. #: ../../../CHANGELOG.md:3259

  5949. 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`)."

  5950. msgstr ""

  5951. 

  5952. #: ../../../CHANGELOG.md:3261

  5953. 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."

  5954. msgstr ""

  5955. 

  5956. #: ../../../CHANGELOG.md:3263

  5957. 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`."

  5958. msgstr ""

  5959. 

  5960. #: ../../../CHANGELOG.md:3266

  5961. msgid "2019-06-24"

  5962. msgstr ""

  5963. 

  5964. #: ../../../CHANGELOG.md:3268

  5965. msgid "(BC Break) WhatsApp bridge configuration is now entirely managed by the playbook"

  5966. msgstr ""

  5967. 

  5968. #: ../../../CHANGELOG.md:3270

  5969. 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."

  5970. msgstr ""

  5971. 

  5972. #: ../../../CHANGELOG.md:3272

  5973. #: ../../../CHANGELOG.md:3289

  5974. #: ../../../CHANGELOG.md:3308

  5975. #: ../../../CHANGELOG.md:3347

  5976. msgid "From now on, the playbook will keep the configuration in sync for you."

  5977. msgstr ""

  5978. 

  5979. #: ../../../CHANGELOG.md:3274

  5980. 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."

  5981. msgstr ""

  5982. 

  5983. #: ../../../CHANGELOG.md:3276

  5984. 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."

  5985. msgstr ""

  5986. 

  5987. #: ../../../CHANGELOG.md:3278

  5988. 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`)."

  5989. msgstr ""

  5990. 

  5991. #: ../../../CHANGELOG.md:3280

  5992. msgid "We're now following the default configuration for the WhatsApp bridge."

  5993. msgstr ""

  5994. 

  5995. #: ../../../CHANGELOG.md:3283

  5996. msgid "2019-06-20"

  5997. msgstr ""

  5998. 

  5999. #: ../../../CHANGELOG.md:3285

  6000. msgid "(BC Break) IRC bridge configuration is now entirely managed by the playbook"

  6001. msgstr ""

  6002. 

  6003. #: ../../../CHANGELOG.md:3287

  6004. 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."

  6005. msgstr ""

  6006. 

  6007. #: ../../../CHANGELOG.md:3291

  6008. 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."

  6009. msgstr ""

  6010. 

  6011. #: ../../../CHANGELOG.md:3293

  6012. 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`)."

  6013. msgstr ""

  6014. 

  6015. #: ../../../CHANGELOG.md:3295

  6016. 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."

  6017. msgstr ""

  6018. 

  6019. #: ../../../CHANGELOG.md:3297

  6020. 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`."

  6021. msgstr ""

  6022. 

  6023. #: ../../../CHANGELOG.md:3299

  6024. 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`)."

  6025. msgstr ""

  6026. 

  6027. #: ../../../CHANGELOG.md:3302

  6028. msgid "2019-06-15"

  6029. msgstr ""

  6030. 

  6031. #: ../../../CHANGELOG.md:3304

  6032. msgid "(BC Break) Telegram bridge configuration is now entirely managed by the playbook"

  6033. msgstr ""

  6034. 

  6035. #: ../../../CHANGELOG.md:3306

  6036. 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."

  6037. msgstr ""

  6038. 

  6039. #: ../../../CHANGELOG.md:3310

  6040. 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."

  6041. msgstr ""

  6042. 

  6043. #: ../../../CHANGELOG.md:3312

  6044. 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."

  6045. msgstr ""

  6046. 

  6047. #: ../../../CHANGELOG.md:3314

  6048. 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`)."

  6049. msgstr ""

  6050. 

  6051. #: ../../../CHANGELOG.md:3316

  6052. msgid "Also, we're now following the default configuration for the Telegram bridge, so some default configuration values are different:"

  6053. msgstr ""

  6054. 

  6055. #: ../../../CHANGELOG.md:3318

  6056. 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"

  6057. msgstr ""

  6058. 

  6059. #: ../../../CHANGELOG.md:3319

  6060. 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."

  6061. msgstr ""

  6062. 

  6063. #: ../../../CHANGELOG.md:3320

  6064. msgid "`authless_portals` (used to be `false`, now `true`) — creating portals from the Telegram side is now possible"

  6065. msgstr ""

  6066. 

  6067. #: ../../../CHANGELOG.md:3321

  6068. msgid "`whitelist_group_admins` (used to be `false`, now `true`) — allows Telegram group admins to use the bot commands"

  6069. msgstr ""

  6070. 

  6071. #: ../../../CHANGELOG.md:3323

  6072. 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)."

  6073. msgstr ""

  6074. 

  6075. #: ../../../CHANGELOG.md:3326

  6076. msgid "2019-06-12"

  6077. msgstr ""

  6078. 

  6079. #: ../../../CHANGELOG.md:3328

  6080. msgid "Synapse v1.0"

  6081. msgstr ""

  6082. 

  6083. #: ../../../CHANGELOG.md:3330

  6084. 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)."

  6085. msgstr ""

  6086. 

  6087. #: ../../../CHANGELOG.md:3332

  6088. 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."

  6089. msgstr ""

  6090. 

  6091. #: ../../../CHANGELOG.md:3334

  6092. msgid "**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` DNS SRV records. The latter, **must not** be removed."

  6093. msgstr ""

  6094. 

  6095. #: ../../../CHANGELOG.md:3336

  6096. 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."

  6097. msgstr ""

  6098. 

  6099. #: ../../../CHANGELOG.md:3338

  6100. 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)."

  6101. msgstr ""

  6102. 

  6103. #: ../../../CHANGELOG.md:3341

  6104. msgid "2019-06-07"

  6105. msgstr ""

  6106. 

  6107. #: ../../../CHANGELOG.md:3343

  6108. msgid "(BC Break) Facebook bridge configuration is now entirely managed by the playbook"

  6109. msgstr ""

  6110. 

  6111. #: ../../../CHANGELOG.md:3345

  6112. 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."

  6113. msgstr ""

  6114. 

  6115. #: ../../../CHANGELOG.md:3349

  6116. 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."

  6117. msgstr ""

  6118. 

  6119. #: ../../../CHANGELOG.md:3351

  6120. 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."

  6121. msgstr ""

  6122. 

  6123. #: ../../../CHANGELOG.md:3353

  6124. 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`)."

  6125. msgstr ""

  6126. 

  6127. #: ../../../CHANGELOG.md:3356

  6128. msgid "2019-05-25"

  6129. msgstr ""

  6130. 

  6131. #: ../../../CHANGELOG.md:3358

  6132. msgid "Support for exposing container ports publicly (not just to the host)"

  6133. msgstr ""

  6134. 

  6135. #: ../../../CHANGELOG.md:3360

  6136. 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."

  6137. msgstr ""

  6138. 

  6139. #: ../../../CHANGELOG.md:3362

  6140. 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`."

  6141. msgstr ""

  6142. 

  6143. #: ../../../CHANGELOG.md:3364

  6144. msgid "All such variables have been superseded by a better (more flexible) way to do it."

  6145. msgstr ""

  6146. 

  6147. #: ../../../CHANGELOG.md:3366

  6148. msgid "**Most** people (including those not using `matrix-nginx-proxy`), **don't need** to bother with this."

  6149. msgstr ""

  6150. 

  6151. #: ../../../CHANGELOG.md:3368

  6152. msgid "Porting examples follow for people having more customized setups:"

  6153. msgstr ""

  6154. 

  6155. #: ../../../CHANGELOG.md:3370

  6156. msgid "**from** `matrix_synapse_container_expose_client_api_port: true` **to** `matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`"

  6157. msgstr ""

  6158. 

  6159. #: ../../../CHANGELOG.md:3372

  6160. 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'`"

  6161. msgstr ""

  6162. 

  6163. #: ../../../CHANGELOG.md:3374

  6164. msgid "**from** `matrix_synapse_container_expose_metrics_port: true` **to** `matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`"

  6165. msgstr ""

  6166. 

  6167. #: ../../../CHANGELOG.md:3376

  6168. msgid "**from** `matrix_riot_web_container_expose_port: true` **to** `matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`"

  6169. msgstr ""

  6170. 

  6171. #: ../../../CHANGELOG.md:3378

  6172. msgid "**from** `matrix_mxisd_container_expose_port: true` **to** `matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`"

  6173. msgstr ""

  6174. 

  6175. #: ../../../CHANGELOG.md:3380

  6176. msgid "**from** `matrix_dimension_container_expose_port: true` **to** `matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`"

  6177. msgstr ""

  6178. 

  6179. #: ../../../CHANGELOG.md:3382

  6180. 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'`"

  6181. msgstr ""

  6182. 

  6183. #: ../../../CHANGELOG.md:3384

  6184. 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'`"

  6185. msgstr ""

  6186. 

  6187. #: ../../../CHANGELOG.md:3386

  6188. 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'`"

  6189. msgstr ""

  6190. 

  6191. #: ../../../CHANGELOG.md:3388

  6192. msgid "As always, if you forget to remove usage of some outdated variable, the playbook will warn you."

  6193. msgstr ""

  6194. 

  6195. #: ../../../CHANGELOG.md:3391

  6196. msgid "2019-05-23"

  6197. msgstr ""

  6198. 

  6199. #: ../../../CHANGELOG.md:3393

  6200. msgid "(BC Break) Ansible 2.8 compatibility"

  6201. msgstr ""

  6202. 

  6203. #: ../../../CHANGELOG.md:3395

  6204. 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)."

  6205. msgstr ""

  6206. 

  6207. #: ../../../CHANGELOG.md:3397

  6208. msgid "A manual change is required to the `inventory/hosts` file, changing the group name from `matrix-servers` to `matrix_servers` (dash to underscore)."

  6209. msgstr ""

  6210. 

  6211. #: ../../../CHANGELOG.md:3399

  6212. msgid "To avoid doing it manually, run this:"

  6213. msgstr ""

  6214. 

  6215. #: ../../../CHANGELOG.md:3400

  6216. msgid "Linux: `sed -i 's/matrix-servers/matrix_servers/g' inventory/hosts`"

  6217. msgstr ""

  6218. 

  6219. #: ../../../CHANGELOG.md:3401

  6220. msgid "Mac: `sed -i '' 's/matrix-servers/matrix_servers/g' inventory/hosts`"

  6221. msgstr ""

  6222. 

  6223. #: ../../../CHANGELOG.md:3404

  6224. msgid "2019-05-21"

  6225. msgstr ""

  6226. 

  6227. #: ../../../CHANGELOG.md:3406

  6228. msgid "Synapse no longer required"

  6229. msgstr ""

  6230. 

  6231. #: ../../../CHANGELOG.md:3408

  6232. msgid "The playbook no longer insists on installing [Synapse](https://github.com/element-hq/synapse) via the `matrix-synapse` role."

  6233. msgstr ""

  6234. 

  6235. #: ../../../CHANGELOG.md:3410

  6236. 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`)."

  6237. msgstr ""

  6238. 

  6239. #: ../../../CHANGELOG.md:3412

  6240. 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."

  6241. msgstr ""

  6242. 

  6243. #: ../../../CHANGELOG.md:3414

  6244. msgid "Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers."

  6245. msgstr ""

  6246. 

  6247. #: ../../../CHANGELOG.md:3416

  6248. msgid "Bridges are now separate from the Synapse role"

  6249. msgstr ""

  6250. 

  6251. #: ../../../CHANGELOG.md:3418

  6252. msgid "Bridges are no longer part of the `matrix-synapse` role. Each bridge now lives in its own separate role (`roles/custom/matrix-bridge-*`)."

  6253. msgstr ""

  6254. 

  6255. #: ../../../CHANGELOG.md:3420

  6256. 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)."

  6257. msgstr ""

  6258. 

  6259. #: ../../../CHANGELOG.md:3422

  6260. msgid "Renaming inconsistently-named Synapse variables"

  6261. msgstr ""

  6262. 

  6263. #: ../../../CHANGELOG.md:3424

  6264. msgid "For better consistency, the following variables have been renamed:"

  6265. msgstr ""

  6266. 

  6267. #: ../../../CHANGELOG.md:3426

  6268. msgid "`matrix_enable_room_list_search` was renamed to `matrix_synapse_enable_room_list_search`"

  6269. msgstr ""

  6270. 

  6271. #: ../../../CHANGELOG.md:3427

  6272. msgid "`matrix_alias_creation_rules` was renamed to `matrix_synapse_alias_creation_rules`"

  6273. msgstr ""

  6274. 

  6275. #: ../../../CHANGELOG.md:3428

  6276. msgid "`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was renamed to `matrix_synapse_room_list_publication_rules`"

  6277. msgstr ""

  6278. 

  6279. #: ../../../CHANGELOG.md:3431

  6280. msgid "2019-05-09"

  6281. msgstr ""

  6282. 

  6283. #: ../../../CHANGELOG.md:3433

  6284. msgid "Besides a myriad of bug fixes and minor improvements, here are the more notable (bigger) features we can announce today."

  6285. msgstr ""

  6286. 

  6287. #: ../../../CHANGELOG.md:3435

  6288. msgid "Mautrix Facebook/Messenger bridging support"

  6289. msgstr ""

  6290. 

  6291. #: ../../../CHANGELOG.md:3437

  6292. 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)."

  6293. msgstr ""

  6294. 

  6295. #: ../../../CHANGELOG.md:3439

  6296. msgid "Additional details are available in [Setting up Mautrix Facebook bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)."

  6297. msgstr ""

  6298. 

  6299. #: ../../../CHANGELOG.md:3441

  6300. msgid "mxisd Registration feature integration"

  6301. msgstr ""

  6302. 

  6303. #: ../../../CHANGELOG.md:3443

  6304. 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."

  6305. msgstr ""

  6306. 

  6307. #: ../../../CHANGELOG.md:3445

  6308. msgid "Learn more in [mxisd-controlled Registration](docs/configuring-playbook-mxisd.md#mxisd-controlled-registration)."

  6309. msgstr ""

  6310. 

  6311. #: ../../../CHANGELOG.md:3448

  6312. msgid "2019-04-16"

  6313. msgstr ""

  6314. 

  6315. #: ../../../CHANGELOG.md:3450

  6316. msgid "Caddy webserver examples"

  6317. msgstr ""

  6318. 

  6319. #: ../../../CHANGELOG.md:3452

  6320. 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"

  6321. msgstr ""

  6322. 

  6323. #: ../../../CHANGELOG.md:3454

  6324. msgid "2019-04-10"

  6325. msgstr ""

  6326. 

  6327. #: ../../../CHANGELOG.md:3456

  6328. msgid "Goofys support for other S3-compatible object stores"

  6329. msgstr ""

  6330. 

  6331. #: ../../../CHANGELOG.md:3458

  6332. 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),"

  6333. msgstr ""

  6334. 

  6335. #: ../../../CHANGELOG.md:3461

  6336. msgid "2019-04-03"

  6337. msgstr ""

  6338. 

  6339. #: ../../../CHANGELOG.md:3463

  6340. msgid "Ansible >= 2.5 is required"

  6341. msgstr ""

  6342. 

  6343. #: ../../../CHANGELOG.md:3465

  6344. 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)."

  6345. msgstr ""

  6346. 

  6347. #: ../../../CHANGELOG.md:3467

  6348. 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))."

  6349. msgstr ""

  6350. 

  6351. #: ../../../CHANGELOG.md:3470

  6352. msgid "2019-03-19"

  6353. msgstr ""

  6354. 

  6355. #: ../../../CHANGELOG.md:3472

  6356. msgid "TLS support for coturn"

  6357. msgstr ""

  6358. 

  6359. #: ../../../CHANGELOG.md:3474

  6360. 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."

  6361. msgstr ""

  6362. 

  6363. #: ../../../CHANGELOG.md:3476

  6364. 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:"

  6365. msgstr ""

  6366. 

  6367. #: ../../../CHANGELOG.md:3482

  6368. 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)."

  6369. msgstr ""

  6370. 

  6371. #: ../../../CHANGELOG.md:3484

  6372. msgid "People who build their own custom playbook from our roles should be aware that:"

  6373. msgstr ""

  6374. 

  6375. #: ../../../CHANGELOG.md:3486

  6376. 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)."

  6377. msgstr ""

  6378. 

  6379. #: ../../../CHANGELOG.md:3488

  6380. 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)."

  6381. msgstr ""

  6382. 

  6383. #: ../../../CHANGELOG.md:3491

  6384. msgid "2019-03-12"

  6385. msgstr ""

  6386. 

  6387. #: ../../../CHANGELOG.md:3493

  6388. msgid "matrix-nginx-proxy support for serving the base domain"

  6389. msgstr ""

  6390. 

  6391. #: ../../../CHANGELOG.md:3495

  6392. 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."

  6393. msgstr ""

  6394. 

  6395. #: ../../../CHANGELOG.md:3497

  6396. 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."

  6397. msgstr ""

  6398. 

  6399. #: ../../../CHANGELOG.md:3499

  6400. msgid "(BC break) matrix-nginx-proxy data variable renamed"

  6401. msgstr ""

  6402. 

  6403. #: ../../../CHANGELOG.md:3501

  6404. msgid "`matrix_nginx_proxy_data_path` was renamed to `matrix_nginx_proxy_base_path`."

  6405. msgstr ""

  6406. 

  6407. #: ../../../CHANGELOG.md:3503

  6408. 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)."

  6409. msgstr ""

  6410. 

  6411. #: ../../../CHANGELOG.md:3506

  6412. msgid "2019-03-10"

  6413. msgstr ""

  6414. 

  6415. #: ../../../CHANGELOG.md:3508

  6416. msgid "Dimension integration manager support"

  6417. msgstr ""

  6418. 

  6419. #: ../../../CHANGELOG.md:3510

  6420. 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."

  6421. msgstr ""

  6422. 

  6423. #: ../../../CHANGELOG.md:3513

  6424. msgid "2019-03-07"

  6425. msgstr ""

  6426. 

  6427. #: ../../../CHANGELOG.md:3515

  6428. msgid "Ability to customize mxisd's email templates"

  6429. msgstr ""

  6430. 

  6431. #: ../../../CHANGELOG.md:3517

  6432. 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."

  6433. msgstr ""

  6434. 

  6435. #: ../../../CHANGELOG.md:3520

  6436. msgid "2019-03-05"

  6437. msgstr ""

  6438. 

  6439. #: ../../../CHANGELOG.md:3522

  6440. msgid "Discord bridging support"

  6441. msgstr ""

  6442. 

  6443. #: ../../../CHANGELOG.md:3524

  6444. 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."

  6445. msgstr ""

  6446. 

  6447. #: ../../../CHANGELOG.md:3527

  6448. msgid "2019-02-19"

  6449. msgstr ""

  6450. 

  6451. #: ../../../CHANGELOG.md:3529

  6452. msgid "Renaming variables"

  6453. msgstr ""

  6454. 

  6455. #: ../../../CHANGELOG.md:3531

  6456. #: ../../../CHANGELOG.md:3848

  6457. #: ../../../CHANGELOG.md:3933

  6458. #: ../../../CHANGELOG.md:4053

  6459. msgid "The following playbook variables were renamed:"

  6460. msgstr ""

  6461. 

  6462. #: ../../../CHANGELOG.md:3533

  6463. msgid "from `host_specific_hostname_identity` to `matrix_domain`"

  6464. msgstr ""

  6465. 

  6466. #: ../../../CHANGELOG.md:3534

  6467. msgid "from `hostname_identity` to `matrix_domain`"

  6468. msgstr ""

  6469. 

  6470. #: ../../../CHANGELOG.md:3535

  6471. msgid "from `hostname_matrix` to `matrix_server_fqn_matrix`"

  6472. msgstr ""

  6473. 

  6474. #: ../../../CHANGELOG.md:3536

  6475. msgid "from `hostname_riot` to `matrix_server_fqn_riot`"

  6476. msgstr ""

  6477. 

  6478. #: ../../../CHANGELOG.md:3537

  6479. msgid "from `host_specific_matrix_ssl_lets_encrypt_support_email` to `matrix_ssl_lets_encrypt_support_email`"

  6480. msgstr ""

  6481. 

  6482. #: ../../../CHANGELOG.md:3539

  6483. msgid "Doing that, we've simplified things, made names less confusing (hopefully) and moved all variable names under the `matrix_` prefix."

  6484. msgstr ""

  6485. 

  6486. #: ../../../CHANGELOG.md:3542

  6487. msgid "2019-02-16"

  6488. msgstr ""

  6489. 

  6490. #: ../../../CHANGELOG.md:3544

  6491. msgid "Riot v1.0.1 support"

  6492. msgstr ""

  6493. 

  6494. #: ../../../CHANGELOG.md:3546

  6495. msgid "You can now use the brand new and redesigned Riot."

  6496. msgstr ""

  6497. 

  6498. #: ../../../CHANGELOG.md:3548

  6499. msgid "The new version no longer has a homepage by default, so we've also removed the custom homepage that we've been installing."

  6500. msgstr ""

  6501. 

  6502. #: ../../../CHANGELOG.md:3550

  6503. 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)."

  6504. msgstr ""

  6505. 

  6506. #: ../../../CHANGELOG.md:3553

  6507. msgid "2019-02-14"

  6508. msgstr ""

  6509. 

  6510. #: ../../../CHANGELOG.md:3555

  6511. msgid "Synapse v0.99.1"

  6512. msgstr ""

  6513. 

  6514. #: ../../../CHANGELOG.md:3557

  6515. 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."

  6516. msgstr ""

  6517. 

  6518. #: ../../../CHANGELOG.md:3559

  6519. 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."

  6520. msgstr ""

  6521. 

  6522. #: ../../../CHANGELOG.md:3562

  6523. msgid "2019-02-06"

  6524. msgstr ""

  6525. 

  6526. #: ../../../CHANGELOG.md:3564

  6527. msgid "Synapse v0.99 support and preparation for Synapse v1.0"

  6528. msgstr ""

  6529. 

  6530. #: ../../../CHANGELOG.md:3566

  6531. 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."

  6532. msgstr ""

  6533. 

  6534. #: ../../../CHANGELOG.md:3568

  6535. 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))."

  6536. msgstr ""

  6537. 

  6538. #: ../../../CHANGELOG.md:3570

  6539. 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)."

  6540. msgstr ""

  6541. 

  6542. #: ../../../CHANGELOG.md:3572

  6543. 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:"

  6544. msgstr ""

  6545. 

  6546. #: ../../../CHANGELOG.md:3574

  6547. 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."

  6548. msgstr ""

  6549. 

  6550. #: ../../../CHANGELOG.md:3576

  6551. 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)."

  6552. msgstr ""

  6553. 

  6554. #: ../../../CHANGELOG.md:3579

  6555. msgid "2019-02-01"

  6556. msgstr ""

  6557. 

  6558. #: ../../../CHANGELOG.md:3581

  6559. msgid "TLS v1.3 support"

  6560. msgstr ""

  6561. 

  6562. #: ../../../CHANGELOG.md:3583

  6563. 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."

  6564. msgstr ""

  6565. 

  6566. #: ../../../CHANGELOG.md:3585

  6567. msgid "When using:"

  6568. msgstr ""

  6569. 

  6570. #: ../../../CHANGELOG.md:3587

  6571. 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`."

  6572. msgstr ""

  6573. 

  6574. #: ../../../CHANGELOG.md:3589

  6575. 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)"

  6576. msgstr ""

  6577. 

  6578. #: ../../../CHANGELOG.md:3591

  6579. msgid "**another web server**: you don't need to do anything to accommodate this change"

  6580. msgstr ""

  6581. 

  6582. #: ../../../CHANGELOG.md:3594

  6583. msgid "2019-01-31"

  6584. msgstr ""

  6585. 

  6586. #: ../../../CHANGELOG.md:3596

  6587. msgid "IRC bridging support"

  6588. msgstr ""

  6589. 

  6590. #: ../../../CHANGELOG.md:3598

  6591. 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."

  6592. msgstr ""

  6593. 

  6594. #: ../../../CHANGELOG.md:3601

  6595. msgid "2019-01-29"

  6596. msgstr ""

  6597. 

  6598. #: ../../../CHANGELOG.md:3603

  6599. msgid "Running container processes as non-root, without capabilities and read-only"

  6600. msgstr ""

  6601. 

  6602. #: ../../../CHANGELOG.md:3605

  6603. 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."

  6604. msgstr ""

  6605. 

  6606. #: ../../../CHANGELOG.md:3607

  6607. 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."

  6608. msgstr ""

  6609. 

  6610. #: ../../../CHANGELOG.md:3609

  6611. 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."

  6612. msgstr ""

  6613. 

  6614. #: ../../../CHANGELOG.md:3611

  6615. 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."

  6616. msgstr ""

  6617. 

  6618. #: ../../../CHANGELOG.md:3613

  6619. msgid "matrix-mailer is now based on Exim, not Postfix"

  6620. msgstr ""

  6621. 

  6622. #: ../../../CHANGELOG.md:3615

  6623. 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)."

  6624. msgstr ""

  6625. 

  6626. #: ../../../CHANGELOG.md:3617

  6627. 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`)."

  6628. msgstr ""

  6629. 

  6630. #: ../../../CHANGELOG.md:3619

  6631. 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)."

  6632. msgstr ""

  6633. 

  6634. #: ../../../CHANGELOG.md:3622

  6635. msgid "2019-01-17"

  6636. msgstr ""

  6637. 

  6638. #: ../../../CHANGELOG.md:3624

  6639. msgid "(BC Break) Making the playbook's roles more independent of one another"

  6640. msgstr ""

  6641. 

  6642. #: ../../../CHANGELOG.md:3626

  6643. 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)."

  6644. msgstr ""

  6645. 

  6646. #: ../../../CHANGELOG.md:3629

  6647. 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."

  6648. msgstr ""

  6649. 

  6650. #: ../../../CHANGELOG.md:3631

  6651. msgid "With the new changes, **all roles are now only dependent on the minimal `matrix-base` role**. They are no longer dependent among themselves."

  6652. msgstr ""

  6653. 

  6654. #: ../../../CHANGELOG.md:3633

  6655. msgid "In addition, the following components can now be completely disabled (for those who want/need to):"

  6656. msgstr ""

  6657. 

  6658. #: ../../../CHANGELOG.md:3634

  6659. msgid "`matrix-coturn` by using `matrix_coturn_enabled: false`"

  6660. msgstr ""

  6661. 

  6662. #: ../../../CHANGELOG.md:3635

  6663. msgid "`matrix-mailer` by using `matrix_mailer_enabled: false`"

  6664. msgstr ""

  6665. 

  6666. #: ../../../CHANGELOG.md:3636

  6667. msgid "`matrix-postgres` by using `matrix_postgres_enabled: false`"

  6668. msgstr ""

  6669. 

  6670. #: ../../../CHANGELOG.md:3638

  6671. msgid "The following changes had to be done:"

  6672. msgstr ""

  6673. 

  6674. #: ../../../CHANGELOG.md:3640

  6675. 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."

  6676. msgstr ""

  6677. 

  6678. #: ../../../CHANGELOG.md:3642

  6679. 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."

  6680. msgstr ""

  6681. 

  6682. #: ../../../CHANGELOG.md:3644

  6683. 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`)"

  6684. msgstr ""

  6685. 

  6686. #: ../../../CHANGELOG.md:3646

  6687. 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."

  6688. msgstr ""

  6689. 

  6690. #: ../../../CHANGELOG.md:3649

  6691. msgid "2019-01-16"

  6692. msgstr ""

  6693. 

  6694. #: ../../../CHANGELOG.md:3651

  6695. msgid "Splitting the playbook into multiple roles"

  6696. msgstr ""

  6697. 

  6698. #: ../../../CHANGELOG.md:3653

  6699. 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)."

  6700. msgstr ""

  6701. 

  6702. #: ../../../CHANGELOG.md:3656

  6703. msgid "To keep the filesystem more consistent with this separation, the **Postgres data had to be relocated**."

  6704. msgstr ""

  6705. 

  6706. #: ../../../CHANGELOG.md:3658

  6707. 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`)."

  6708. msgstr ""

  6709. 

  6710. #: ../../../CHANGELOG.md:3661

  6711. msgid "2019-01-11"

  6712. msgstr ""

  6713. 

  6714. #: ../../../CHANGELOG.md:3663

  6715. msgid "(BC Break) mxisd configuration changes"

  6716. msgstr ""

  6717. 

  6718. #: ../../../CHANGELOG.md:3665

  6719. 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."

  6720. msgstr ""

  6721. 

  6722. #: ../../../CHANGELOG.md:3668

  6723. msgid "The following variables are no longer supported by this playbook:"

  6724. msgstr ""

  6725. 

  6726. #: ../../../CHANGELOG.md:3670

  6727. msgid "`matrix_mxisd_ldap_enabled`"

  6728. msgstr ""

  6729. 

  6730. #: ../../../CHANGELOG.md:3671

  6731. msgid "`matrix_mxisd_ldap_connection_host`"

  6732. msgstr ""

  6733. 

  6734. #: ../../../CHANGELOG.md:3672

  6735. msgid "`matrix_mxisd_ldap_connection_tls`"

  6736. msgstr ""

  6737. 

  6738. #: ../../../CHANGELOG.md:3673

  6739. msgid "`matrix_mxisd_ldap_connection_port`"

  6740. msgstr ""

  6741. 

  6742. #: ../../../CHANGELOG.md:3674

  6743. msgid "`matrix_mxisd_ldap_connection_baseDn`"

  6744. msgstr ""

  6745. 

  6746. #: ../../../CHANGELOG.md:3675

  6747. msgid "`matrix_mxisd_ldap_connection_baseDns`"

  6748. msgstr ""

  6749. 

  6750. #: ../../../CHANGELOG.md:3676

  6751. #: ../../../CHANGELOG.md:3677

  6752. msgid "`matrix_mxisd_ldap_connection_bindDn`"

  6753. msgstr ""

  6754. 

  6755. #: ../../../CHANGELOG.md:3678

  6756. #: ../../../CHANGELOG.md:3682

  6757. msgid "`matrix_mxisd_ldap_connection_bindPassword`"

  6758. msgstr ""

  6759. 

  6760. #: ../../../CHANGELOG.md:3679

  6761. msgid "`matrix_mxisd_ldap_filter`"

  6762. msgstr ""

  6763. 

  6764. #: ../../../CHANGELOG.md:3680

  6765. msgid "`matrix_mxisd_ldap_attribute_uid_type`"

  6766. msgstr ""

  6767. 

  6768. #: ../../../CHANGELOG.md:3681

  6769. msgid "`matrix_mxisd_ldap_attribute_uid_value`"

  6770. msgstr ""

  6771. 

  6772. #: ../../../CHANGELOG.md:3683

  6773. msgid "`matrix_mxisd_ldap_attribute_name`"

  6774. msgstr ""

  6775. 

  6776. #: ../../../CHANGELOG.md:3684

  6777. msgid "`matrix_mxisd_ldap_attribute_threepid_email`"

  6778. msgstr ""

  6779. 

  6780. #: ../../../CHANGELOG.md:3685

  6781. msgid "`matrix_mxisd_ldap_attribute_threepid_msisdn`"

  6782. msgstr ""

  6783. 

  6784. #: ../../../CHANGELOG.md:3686

  6785. msgid "`matrix_mxisd_ldap_identity_filter`"

  6786. msgstr ""

  6787. 

  6788. #: ../../../CHANGELOG.md:3687

  6789. msgid "`matrix_mxisd_ldap_identity_medium`"

  6790. msgstr ""

  6791. 

  6792. #: ../../../CHANGELOG.md:3688

  6793. msgid "`matrix_mxisd_ldap_auth_filter`"

  6794. msgstr ""

  6795. 

  6796. #: ../../../CHANGELOG.md:3689

  6797. msgid "`matrix_mxisd_ldap_directory_filter`"

  6798. msgstr ""

  6799. 

  6800. #: ../../../CHANGELOG.md:3690

  6801. msgid "`matrix_mxisd_template_config`"

  6802. msgstr ""

  6803. 

  6804. #: ../../../CHANGELOG.md:3692

  6805. 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."

  6806. msgstr ""

  6807. 

  6808. #: ../../../CHANGELOG.md:3694

  6809. msgid "This new way of configuring mxisd is beneficial because:"

  6810. msgstr ""

  6811. 

  6812. #: ../../../CHANGELOG.md:3696

  6813. msgid "it lets us support all mxisd configuration options, as the playbook simply forwards them to mxisd without needing to care or understand them"

  6814. msgstr ""

  6815. 

  6816. #: ../../../CHANGELOG.md:3697

  6817. msgid "it lets you upgrade to newer mxisd versions and make use of their features, without us having to add support for them explicitly"

  6818. msgstr ""

  6819. 

  6820. #: ../../../CHANGELOG.md:3700

  6821. msgid "2019-01-08"

  6822. msgstr ""

  6823. 

  6824. #: ../../../CHANGELOG.md:3702

  6825. msgid "(BC Break) Cronjob schedule no longer configurable"

  6826. msgstr ""

  6827. 

  6828. #: ../../../CHANGELOG.md:3704

  6829. msgid "Due to the way we manage cronjobs now, you can no longer configure the schedule they're invoked at."

  6830. msgstr ""

  6831. 

  6832. #: ../../../CHANGELOG.md:3706

  6833. 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."

  6834. msgstr ""

  6835. 

  6836. #: ../../../CHANGELOG.md:3709

  6837. 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!"

  6838. msgstr ""

  6839. 

  6840. #: ../../../CHANGELOG.md:3712

  6841. msgid "2018-12-23"

  6842. msgstr ""

  6843. 

  6844. #: ../../../CHANGELOG.md:3714

  6845. msgid "(BC Break) More SSL certificate retrieval methods"

  6846. msgstr ""

  6847. 

  6848. #: ../../../CHANGELOG.md:3716

  6849. msgid "The playbook now lets you decide between 3 different SSL certificate retrieval methods:"

  6850. msgstr ""

  6851. 

  6852. #: ../../../CHANGELOG.md:3717

  6853. msgid "(default) obtaining free SSL certificates from Let's Encrypt"

  6854. msgstr ""

  6855. 

  6856. #: ../../../CHANGELOG.md:3718

  6857. msgid "generating self-signed SSL certificates"

  6858. msgstr ""

  6859. 

  6860. #: ../../../CHANGELOG.md:3719

  6861. msgid "managing SSL certificates manually"

  6862. msgstr ""

  6863. 

  6864. #: ../../../CHANGELOG.md:3721

  6865. msgid "Learn more in [Adjusting SSL certificate retrieval](docs/configuring-playbook-ssl-certificates.md)."

  6866. msgstr ""

  6867. 

  6868. #: ../../../CHANGELOG.md:3723

  6869. 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:"

  6870. msgstr ""

  6871. 

  6872. #: ../../../CHANGELOG.md:3725

  6873. msgid "before: `host_specific_matrix_ssl_support_email`"

  6874. msgstr ""

  6875. 

  6876. #: ../../../CHANGELOG.md:3726

  6877. msgid "after: `host_specific_matrix_ssl_lets_encrypt_support_email`"

  6878. msgstr ""

  6879. 

  6880. #: ../../../CHANGELOG.md:3728

  6881. msgid "(BC Break) mxisd upgrade with multiple base DN support"

  6882. msgstr ""

  6883. 

  6884. #: ../../../CHANGELOG.md:3730

  6885. 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)."

  6886. msgstr ""

  6887. 

  6888. #: ../../../CHANGELOG.md:3732

  6889. 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)."

  6890. msgstr ""

  6891. 

  6892. #: ../../../CHANGELOG.md:3734

  6893. msgid "Example change:"

  6894. msgstr ""

  6895. 

  6896. #: ../../../CHANGELOG.md:3736

  6897. msgid "before: `matrix_mxisd_ldap_connection_baseDn: OU=Users,DC=example,DC=org`"

  6898. msgstr ""

  6899. 

  6900. #: ../../../CHANGELOG.md:3737

  6901. msgid "after: `matrix_mxisd_ldap_connection_baseDns: ['OU=Users,DC=example,DC=org']`"

  6902. msgstr ""

  6903. 

  6904. #: ../../../CHANGELOG.md:3740

  6905. msgid "2018-12-21"

  6906. msgstr ""

  6907. 

  6908. #: ../../../CHANGELOG.md:3742

  6909. msgid "Synapse 0.34.0 and Python 3"

  6910. msgstr ""

  6911. 

  6912. #: ../../../CHANGELOG.md:3744

  6913. 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)."

  6914. msgstr ""

  6915. 

  6916. #: ../../../CHANGELOG.md:3747

  6917. msgid "2018-12-12"

  6918. msgstr ""

  6919. 

  6920. #: ../../../CHANGELOG.md:3749

  6921. msgid "Riot homepage customization"

  6922. msgstr ""

  6923. 

  6924. #: ../../../CHANGELOG.md:3751

  6925. 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`."

  6926. msgstr ""

  6927. 

  6928. #: ../../../CHANGELOG.md:3754

  6929. msgid "2018-12-04"

  6930. msgstr ""

  6931. 

  6932. #: ../../../CHANGELOG.md:3756

  6933. msgid "mxisd extensibility"

  6934. msgstr ""

  6935. 

  6936. #: ../../../CHANGELOG.md:3758

  6937. 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`)."

  6938. msgstr ""

  6939. 

  6940. #: ../../../CHANGELOG.md:3761

  6941. msgid "2018-11-28"

  6942. msgstr ""

  6943. 

  6944. #: ../../../CHANGELOG.md:3763

  6945. msgid "More scripts"

  6946. msgstr ""

  6947. 

  6948. #: ../../../CHANGELOG.md:3765

  6949. msgid "matrix-remove-all allows to uninstall everything with a single command"

  6950. msgstr ""

  6951. 

  6952. #: ../../../CHANGELOG.md:3766

  6953. msgid "matrix-make-user-admin allows to upgrade a user's privileges"

  6954. msgstr ""

  6955. 

  6956. #: ../../../CHANGELOG.md:3768

  6957. msgid "LDAP auth support via matrix-synapse-ldap3"

  6958. msgstr ""

  6959. 

  6960. #: ../../../CHANGELOG.md:3770

  6961. msgid "The playbook can now install and configure [LDAP auth support](https://github.com/matrix-org/matrix-synapse-ldap3) for you."

  6962. msgstr ""

  6963. 

  6964. #: ../../../CHANGELOG.md:3772

  6965. msgid "Additional details are available in [Setting up the LDAP authentication password provider module](docs/configuring-playbook-ldap-auth.md)."

  6966. msgstr ""

  6967. 

  6968. #: ../../../CHANGELOG.md:3775

  6969. msgid "2018-11-23"

  6970. msgstr ""

  6971. 

  6972. #: ../../../CHANGELOG.md:3777

  6973. msgid "Support for controlling public registration and room auto-join"

  6974. msgstr ""

  6975. 

  6976. #: ../../../CHANGELOG.md:3779

  6977. msgid "The playbook now lets you enable public registration for users (controlled via `matrix_synapse_enable_registration`). By default, public registration is forbidden."

  6978. msgstr ""

  6979. 

  6980. #: ../../../CHANGELOG.md:3781

  6981. msgid "You can also make people automatically get auto-joined to rooms (controlled via `matrix_synapse_auto_join_rooms`)."

  6982. msgstr ""

  6983. 

  6984. #: ../../../CHANGELOG.md:3783

  6985. msgid "Support for changing the welcome user ID (welcome bot)"

  6986. msgstr ""

  6987. 

  6988. #: ../../../CHANGELOG.md:3785

  6989. 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."

  6990. msgstr ""

  6991. 

  6992. #: ../../../CHANGELOG.md:3788

  6993. msgid "2018-11-14"

  6994. msgstr ""

  6995. 

  6996. #: ../../../CHANGELOG.md:3790

  6997. msgid "Ability to set Synapse log levels"

  6998. msgstr ""

  6999. 

  7000. #: ../../../CHANGELOG.md:3792

  7001. msgid "The playbook now allows you to set the log levels used by Synapse. The default logging levels remain the same."

  7002. msgstr ""

  7003. 

  7004. #: ../../../CHANGELOG.md:3794

  7005. 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"

  7006. msgstr ""

  7007. 

  7008. #: ../../../CHANGELOG.md:3803

  7009. msgid "2018-11-03"

  7010. msgstr ""

  7011. 

  7012. #: ../../../CHANGELOG.md:3805

  7013. msgid "Customize parts of Riot's config"

  7014. msgstr ""

  7015. 

  7016. #: ../../../CHANGELOG.md:3807

  7017. msgid "You can now customize some parts of Riot's `config.json`. These playbook variables, with these default values, have been added:"

  7018. msgstr ""

  7019. 

  7020. #: ../../../CHANGELOG.md:3818

  7021. 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:"

  7022. msgstr ""

  7023. 

  7024. #: ../../../CHANGELOG.md:3827

  7025. msgid "SSL protocols used to serve Riot and Synapse"

  7026. msgstr ""

  7027. 

  7028. #: ../../../CHANGELOG.md:3829

  7029. 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."

  7030. msgstr ""

  7031. 

  7032. #: ../../../CHANGELOG.md:3831

  7033. msgid "You may wish to re-enable TLSv1 if you need to access Riot in older browsers."

  7034. msgstr ""

  7035. 

  7036. #: ../../../CHANGELOG.md:3833

  7037. msgid "Note: Currently the dockerized nginx doesn't support TLSv1.3. See https://github.com/nginxinc/docker-nginx/issues/190 for more details."

  7038. msgstr ""

  7039. 

  7040. #: ../../../CHANGELOG.md:3836

  7041. msgid "2018-11-01"

  7042. msgstr ""

  7043. 

  7044. #: ../../../CHANGELOG.md:3838

  7045. msgid "Postgres 11 support"

  7046. msgstr ""

  7047. 

  7048. #: ../../../CHANGELOG.md:3840

  7049. msgid "The playbook now installs [Postgres 11](https://www.postgresql.org/about/news/1894/) by default."

  7050. msgstr ""

  7051. 

  7052. #: ../../../CHANGELOG.md:3842

  7053. 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)."

  7054. msgstr ""

  7055. 

  7056. #: ../../../CHANGELOG.md:3844

  7057. #: ../../../CHANGELOG.md:3931

  7058. #: ../../../CHANGELOG.md:4051

  7059. msgid "(BC Break) Renaming playbook variables"

  7060. msgstr ""

  7061. 

  7062. #: ../../../CHANGELOG.md:3846

  7063. 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."

  7064. msgstr ""

  7065. 

  7066. #: ../../../CHANGELOG.md:3850

  7067. msgid "from `matrix_docker_image_mxisd` to `matrix_mxisd_docker_image`"

  7068. msgstr ""

  7069. 

  7070. #: ../../../CHANGELOG.md:3851

  7071. msgid "from `matrix_docker_image_mautrix_telegram` to `matrix_mautrix_telegram_docker_image`"

  7072. msgstr ""

  7073. 

  7074. #: ../../../CHANGELOG.md:3852

  7075. msgid "from `matrix_docker_image_mautrix_whatsapp` to `matrix_mautrix_whatsapp_docker_image`"

  7076. msgstr ""

  7077. 

  7078. #: ../../../CHANGELOG.md:3853

  7079. msgid "from `matrix_docker_image_mailer` to `matrix_mailer_docker_image`"

  7080. msgstr ""

  7081. 

  7082. #: ../../../CHANGELOG.md:3854

  7083. msgid "from `matrix_docker_image_coturn` to `matrix_coturn_docker_image`"

  7084. msgstr ""

  7085. 

  7086. #: ../../../CHANGELOG.md:3855

  7087. msgid "from `matrix_docker_image_goofys` to `matrix_s3_goofys_docker_image`"

  7088. msgstr ""

  7089. 

  7090. #: ../../../CHANGELOG.md:3856

  7091. msgid "from `matrix_docker_image_riot` to `matrix_riot_web_docker_image`"

  7092. msgstr ""

  7093. 

  7094. #: ../../../CHANGELOG.md:3857

  7095. msgid "from `matrix_docker_image_nginx` to `matrix_nginx_proxy_docker_image`"

  7096. msgstr ""

  7097. 

  7098. #: ../../../CHANGELOG.md:3858

  7099. msgid "from `matrix_docker_image_synapse` to `matrix_synapse_docker_image`"

  7100. msgstr ""

  7101. 

  7102. #: ../../../CHANGELOG.md:3859

  7103. msgid "from `matrix_docker_image_postgres_v9` to `matrix_postgres_docker_image_v9`"

  7104. msgstr ""

  7105. 

  7106. #: ../../../CHANGELOG.md:3860

  7107. msgid "from `matrix_docker_image_postgres_v10` to `matrix_postgres_docker_image_v10`"

  7108. msgstr ""

  7109. 

  7110. #: ../../../CHANGELOG.md:3861

  7111. msgid "from `matrix_docker_image_postgres_latest` to `matrix_postgres_docker_image_latest`"

  7112. msgstr ""

  7113. 

  7114. #: ../../../CHANGELOG.md:3864

  7115. msgid "2018-10-26"

  7116. msgstr ""

  7117. 

  7118. #: ../../../CHANGELOG.md:3866

  7119. msgid "Mautrix Whatsapp bridging support"

  7120. msgstr ""

  7121. 

  7122. #: ../../../CHANGELOG.md:3868

  7123. 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)."

  7124. msgstr ""

  7125. 

  7126. #: ../../../CHANGELOG.md:3870

  7127. msgid "Additional details are available in [Setting up Mautrix Whatsapp bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)."

  7128. msgstr ""

  7129. 

  7130. #: ../../../CHANGELOG.md:3873

  7131. msgid "2018-10-25"

  7132. msgstr ""

  7133. 

  7134. #: ../../../CHANGELOG.md:3875

  7135. msgid "Support for controlling Matrix federation"

  7136. msgstr ""

  7137. 

  7138. #: ../../../CHANGELOG.md:3877

  7139. 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."

  7140. msgstr ""

  7141. 

  7142. #: ../../../CHANGELOG.md:3880

  7143. msgid "2018-10-24"

  7144. msgstr ""

  7145. 

  7146. #: ../../../CHANGELOG.md:3882

  7147. msgid "Disabling riot-web guests"

  7148. msgstr ""

  7149. 

  7150. #: ../../../CHANGELOG.md:3884

  7151. 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."

  7152. msgstr ""

  7153. 

  7154. #: ../../../CHANGELOG.md:3887

  7155. msgid "2018-10-21"

  7156. msgstr ""

  7157. 

  7158. #: ../../../CHANGELOG.md:3889

  7159. msgid "Self-check maintenance command"

  7160. msgstr ""

  7161. 

  7162. #: ../../../CHANGELOG.md:3891

  7163. msgid "The playbook can now [check if services are configured correctly](docs/maintenance-and-troubleshooting.md#how-to-check-if-services-work)."

  7164. msgstr ""

  7165. 

  7166. #: ../../../CHANGELOG.md:3894

  7167. msgid "2018-10-05"

  7168. msgstr ""

  7169. 

  7170. #: ../../../CHANGELOG.md:3896

  7171. msgid "Presence tracking made configurable"

  7172. msgstr ""

  7173. 

  7174. #: ../../../CHANGELOG.md:3898

  7175. 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)."

  7176. msgstr ""

  7177. 

  7178. #: ../../../CHANGELOG.md:3900

  7179. msgid "If users participate in large rooms with many other servers, disabling presence will decrease server load significantly."

  7180. msgstr ""

  7181. 

  7182. #: ../../../CHANGELOG.md:3903

  7183. msgid "2018-09-27"

  7184. msgstr ""

  7185. 

  7186. #: ../../../CHANGELOG.md:3905

  7187. msgid "Synapse Cache Factor made configurable"

  7188. msgstr ""

  7189. 

  7190. #: ../../../CHANGELOG.md:3907

  7191. 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`)."

  7192. msgstr ""

  7193. 

  7194. #: ../../../CHANGELOG.md:3909

  7195. 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"

  7196. msgstr ""

  7197. 

  7198. #: ../../../CHANGELOG.md:3912

  7199. msgid "2018-09-26"

  7200. msgstr ""

  7201. 

  7202. #: ../../../CHANGELOG.md:3914

  7203. msgid "Disabling Docker container logging"

  7204. msgstr ""

  7205. 

  7206. #: ../../../CHANGELOG.md:3916

  7207. msgid "`--log-driver=none` is used for all Docker containers now."

  7208. msgstr ""

  7209. 

  7210. #: ../../../CHANGELOG.md:3918

  7211. 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."

  7212. msgstr ""

  7213. 

  7214. #: ../../../CHANGELOG.md:3920

  7215. 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."

  7216. msgstr ""

  7217. 

  7218. #: ../../../CHANGELOG.md:3923

  7219. msgid "2018-09-17"

  7220. msgstr ""

  7221. 

  7222. #: ../../../CHANGELOG.md:3925

  7223. msgid "Service discovery support"

  7224. msgstr ""

  7225. 

  7226. #: ../../../CHANGELOG.md:3927

  7227. 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."

  7228. msgstr ""

  7229. 

  7230. #: ../../../CHANGELOG.md:3929

  7231. msgid "Additional details are available in [Configuring service discovery via .well-known](docs/configuring-well-known.md)."

  7232. msgstr ""

  7233. 

  7234. #: ../../../CHANGELOG.md:3935

  7235. msgid "from `matrix_nginx_riot_web_data_path` to `matrix_riot_web_data_path`"

  7236. msgstr ""

  7237. 

  7238. #: ../../../CHANGELOG.md:3936

  7239. msgid "from `matrix_riot_web_default_identity_server_url` to `matrix_identity_server_url`"

  7240. msgstr ""

  7241. 

  7242. #: ../../../CHANGELOG.md:3939

  7243. msgid "2018-09-07"

  7244. msgstr ""

  7245. 

  7246. #: ../../../CHANGELOG.md:3941

  7247. msgid "Mautrix Telegram bridging support"

  7248. msgstr ""

  7249. 

  7250. #: ../../../CHANGELOG.md:3943

  7251. 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)."

  7252. msgstr ""

  7253. 

  7254. #: ../../../CHANGELOG.md:3945

  7255. msgid "Additional details are available in [Setting up Mautrix Telegram bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)."

  7256. msgstr ""

  7257. 

  7258. #: ../../../CHANGELOG.md:3947

  7259. msgid "Events cache size increase and configurability for Matrix Synapse"

  7260. msgstr ""

  7261. 

  7262. #: ../../../CHANGELOG.md:3949

  7263. msgid "The playbook now lets you configure Matrix Synapse's `event_cache_size` configuration via the `matrix_synapse_event_cache_size` playbook variable."

  7264. msgstr ""

  7265. 

  7266. #: ../../../CHANGELOG.md:3951

  7267. msgid "Previously, this value was hardcoded to `\"10K\"`. From now on, a more reasonable default of `\"100K\"` is used."

  7268. msgstr ""

  7269. 

  7270. #: ../../../CHANGELOG.md:3953

  7271. msgid "Password-peppering support for Matrix Synapse"

  7272. msgstr ""

  7273. 

  7274. #: ../../../CHANGELOG.md:3955

  7275. 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."

  7276. msgstr ""

  7277. 

  7278. #: ../../../CHANGELOG.md:3957

  7279. msgid "Statistics-reporting support for Matrix Synapse"

  7280. msgstr ""

  7281. 

  7282. #: ../../../CHANGELOG.md:3959

  7283. 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."

  7284. msgstr ""

  7285. 

  7286. #: ../../../CHANGELOG.md:3961

  7287. 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."

  7288. msgstr ""

  7289. 

  7290. #: ../../../CHANGELOG.md:3964

  7291. msgid "2018-08-29"

  7292. msgstr ""

  7293. 

  7294. #: ../../../CHANGELOG.md:3966

  7295. msgid "Changing the way SSL certificates are retrieved"

  7296. msgstr ""

  7297. 

  7298. #: ../../../CHANGELOG.md:3968

  7299. 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."

  7300. msgstr ""

  7301. 

  7302. #: ../../../CHANGELOG.md:3970

  7303. 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)."

  7304. msgstr ""

  7305. 

  7306. #: ../../../CHANGELOG.md:3972

  7307. 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:"

  7308. msgstr ""

  7309. 

  7310. #: ../../../CHANGELOG.md:3974

  7311. msgid "`systemctl stop 'matrix*'`"

  7312. msgstr ""

  7313. 

  7314. #: ../../../CHANGELOG.md:3975

  7315. msgid "stop your custom webserver, if you're running one (only affects you if you've installed with `matrix_nginx_proxy_enabled: false`)"

  7316. msgstr ""

  7317. 

  7318. #: ../../../CHANGELOG.md:3976

  7319. msgid "`mv /matrix/ssl /matrix/ssl-acmetool-delete-later`"

  7320. msgstr ""

  7321. 

  7322. #: ../../../CHANGELOG.md:3977

  7323. msgid "re-run the playbook's [installation](docs/installing.md)"

  7324. msgstr ""

  7325. 

  7326. #: ../../../CHANGELOG.md:3978

  7327. msgid "possibly delete `/matrix/ssl-acmetool-delete-later`"

  7328. msgstr ""

  7329. 

  7330. #: ../../../CHANGELOG.md:3981

  7331. msgid "2018-08-21"

  7332. msgstr ""

  7333. 

  7334. #: ../../../CHANGELOG.md:3983

  7335. msgid "Matrix Corporal support"

  7336. msgstr ""

  7337. 

  7338. #: ../../../CHANGELOG.md:3985

  7339. msgid "The playbook can now install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you."

  7340. msgstr ""

  7341. 

  7342. #: ../../../CHANGELOG.md:3987

  7343. msgid "Additional details are available in [Setting up Matrix Corporal](docs/configuring-playbook-matrix-corporal.md)."

  7344. msgstr ""

  7345. 

  7346. #: ../../../CHANGELOG.md:3990

  7347. msgid "2018-08-20"

  7348. msgstr ""

  7349. 

  7350. #: ../../../CHANGELOG.md:3992

  7351. msgid "Matrix Synapse rate limit control variables"

  7352. msgstr ""

  7353. 

  7354. #: ../../../CHANGELOG.md:3994

  7355. msgid "The following new variables can now be configured to control Matrix Synapse's rate-limiting (default values are shown below)."

  7356. msgstr ""

  7357. 

  7358. #: ../../../CHANGELOG.md:4001

  7359. msgid "Shared Secret Auth support via matrix-synapse-shared-secret-auth"

  7360. msgstr ""

  7361. 

  7362. #: ../../../CHANGELOG.md:4003

  7363. msgid "The playbook can now install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you."

  7364. msgstr ""

  7365. 

  7366. #: ../../../CHANGELOG.md:4005

  7367. msgid "Additional details are available in [Setting up the Shared Secret Auth password provider module](docs/configuring-playbook-shared-secret-auth.md)."

  7368. msgstr ""

  7369. 

  7370. #: ../../../CHANGELOG.md:4008

  7371. msgid "2018-08-17"

  7372. msgstr ""

  7373. 

  7374. #: ../../../CHANGELOG.md:4010

  7375. msgid "REST auth support via matrix-synapse-rest-auth"

  7376. msgstr ""

  7377. 

  7378. #: ../../../CHANGELOG.md:4012

  7379. msgid "The playbook can now install and configure [matrix-synapse-rest-auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you."

  7380. msgstr ""

  7381. 

  7382. #: ../../../CHANGELOG.md:4014

  7383. msgid "Additional details are available in [Setting up the REST authentication password provider module](docs/configuring-playbook-rest-auth.md)."

  7384. msgstr ""

  7385. 

  7386. #: ../../../CHANGELOG.md:4016

  7387. msgid "Compression improvements"

  7388. msgstr ""

  7389. 

  7390. #: ../../../CHANGELOG.md:4018

  7391. msgid "Shifted Matrix Synapse compression from happening in the Matrix Synapse, to happening in the nginx proxy that's in front of it."

  7392. msgstr ""

  7393. 

  7394. #: ../../../CHANGELOG.md:4021

  7395. 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."

  7396. msgstr ""

  7397. 

  7398. #: ../../../CHANGELOG.md:4024

  7399. msgid "Disabling some unnecessary Synapse services"

  7400. msgstr ""

  7401. 

  7402. #: ../../../CHANGELOG.md:4026

  7403. msgid "The following services are not necessary, so they have been disabled:"

  7404. msgstr ""

  7405. 

  7406. #: ../../../CHANGELOG.md:4027

  7407. msgid "on the federation port (8448): the `client` service"

  7408. msgstr ""

  7409. 

  7410. #: ../../../CHANGELOG.md:4028

  7411. msgid "on the http port (8008, exposed over 443): the old Angular `webclient` and the `federation` service"

  7412. msgstr ""

  7413. 

  7414. #: ../../../CHANGELOG.md:4030

  7415. msgid "Federation runs only on the federation port (8448) now. The Client APIs run only on the http port (8008) now."

  7416. msgstr ""

  7417. 

  7418. #: ../../../CHANGELOG.md:4033

  7419. msgid "2018-08-15"

  7420. msgstr ""

  7421. 

  7422. #: ../../../CHANGELOG.md:4035

  7423. msgid "mxisd Identity Server support"

  7424. msgstr ""

  7425. 

  7426. #: ../../../CHANGELOG.md:4037

  7427. 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)."

  7428. msgstr ""

  7429. 

  7430. #: ../../../CHANGELOG.md:4040

  7431. msgid "2018-08-14"

  7432. msgstr ""

  7433. 

  7434. #: ../../../CHANGELOG.md:4042

  7435. msgid "Email-sending support"

  7436. msgstr ""

  7437. 

  7438. #: ../../../CHANGELOG.md:4044

  7439. 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)."

  7440. msgstr ""

  7441. 

  7442. #: ../../../CHANGELOG.md:4046

  7443. msgid "With this, Matrix Synapse is able to send email notifications for missed messages, etc."

  7444. msgstr ""

  7445. 

  7446. #: ../../../CHANGELOG.md:4049

  7447. msgid "2018-08-08"

  7448. msgstr ""

  7449. 

  7450. #: ../../../CHANGELOG.md:4055

  7451. msgid "from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`"

  7452. msgstr ""

  7453. 

  7454. #: ../../../CHANGELOG.md:4056

  7455. msgid "from `matrix_max_log_file_size_mb` to `matrix_synapse_max_log_file_size_mb`"

  7456. msgstr ""

  7457. 

  7458. #: ../../../CHANGELOG.md:4057

  7459. msgid "from `matrix_max_log_files_count` to `matrix_synapse_max_log_files_count`"

  7460. msgstr ""

  7461. 

  7462. #: ../../../CHANGELOG.md:4058

  7463. msgid "from `docker_matrix_image` to `matrix_docker_image_synapse`"

  7464. msgstr ""

  7465. 

  7466. #: ../../../CHANGELOG.md:4059

  7467. msgid "from `docker_nginx_image` to `matrix_docker_image_nginx`"

  7468. msgstr ""

  7469. 

  7470. #: ../../../CHANGELOG.md:4060

  7471. msgid "from `docker_riot_image` to `matrix_docker_image_riot`"

  7472. msgstr ""

  7473. 

  7474. #: ../../../CHANGELOG.md:4061

  7475. msgid "from `docker_goofys_image` to `matrix_docker_image_goofys`"

  7476. msgstr ""

  7477. 

  7478. #: ../../../CHANGELOG.md:4062

  7479. msgid "from `docker_coturn_image` to `matrix_docker_image_coturn`"

  7480. msgstr ""

  7481. 

  7482. #: ../../../CHANGELOG.md:4064

  7483. msgid "If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names."

  7484. msgstr ""

  7485. 

  7486. #: ../../../CHANGELOG.md:4066

  7487. msgid "Renaming Ansible playbook tag"

  7488. msgstr ""

  7489. 

  7490. #: ../../../CHANGELOG.md:4068

  7491. msgid "The command for executing the whole playbook has changed. The `setup-main` tag got renamed to `setup-all`."

  7492. msgstr ""

  7493. 

  7494. #: ../../../CHANGELOG.md:4070

  7495. msgid "Docker container linking"

  7496. msgstr ""

  7497. 

  7498. #: ../../../CHANGELOG.md:4072

  7499. 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."

  7500. msgstr ""