Merge 46b97d0a7a into a787993aaf

i18n/translation-templates/README.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -244,6 +244,14 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-client-cinny.md)"
 msgstr ""
 
+#: ../../../README.md:0
+msgid "[Sable](https://github.com/7w1/sable)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-client-sable.md)"
+msgstr ""
+
 #: ../../../README.md:0
 msgid "[SchildiChat Web](https://schildi.chat/)"
 msgstr ""
@@ -268,11 +276,11 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-client-fluffychat-web.md)"
 msgstr ""
 
-#: ../../../README.md:70
+#: ../../../README.md:71
 msgid "Server Components"
 msgstr ""
 
-#: ../../../README.md:72
+#: ../../../README.md:73
 msgid "Services that run on the server to make the various parts of your installation work."
 msgstr ""
 
@@ -288,18 +296,6 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-external-postgres.md)"
 msgstr ""
 
-#: ../../../README.md:0
-msgid "[coturn](https://github.com/coturn/coturn)"
-msgstr ""
-
-#: ../../../README.md:0
-msgid "STUN/TURN server for WebRTC audio/video calls"
-msgstr ""
-
-#: ../../../README.md:0
-msgid "[Link](docs/configuring-playbook-turn.md)"
-msgstr ""
-
 #: ../../../README.md:0
 msgid "[Traefik](https://doc.traefik.io/traefik/)"
 msgstr ""
@@ -337,39 +333,39 @@ msgid "[Link](docs/configuring-playbook-email.md)"
 msgstr ""
 
 #: ../../../README.md:0
-msgid "[ddclient](https://github.com/linuxserver/docker-ddclient)"
+msgid "[coturn](https://github.com/coturn/coturn)"
 msgstr ""
 
 #: ../../../README.md:0
-msgid "Dynamic DNS"
+msgid "STUN/TURN server for WebRTC audio/video calls"
 msgstr ""
 
 #: ../../../README.md:0
-msgid "[Link](docs/configuring-playbook-dynamic-dns.md)"
+msgid "[Link](docs/configuring-playbook-turn.md)"
 msgstr ""
 
 #: ../../../README.md:0
-msgid "[LiveKit Server](https://github.com/livekit/livekit)"
+msgid "[ddclient](https://github.com/linuxserver/docker-ddclient)"
 msgstr ""
 
 #: ../../../README.md:0
-msgid "WebRTC server for audio/video calls"
+msgid "Dynamic DNS"
 msgstr ""
 
 #: ../../../README.md:0
-msgid "[Link](docs/configuring-playbook-livekit-server.md)"
+msgid "[Link](docs/configuring-playbook-dynamic-dns.md)"
 msgstr ""
 
 #: ../../../README.md:0
-msgid "[Livekit JWT Service](https://github.com/livekit/livekit-jwt-service)"
+msgid "Matrix RTC stack"
 msgstr ""
 
 #: ../../../README.md:0
-msgid "JWT service for integrating [Element Call](./configuring-playbook-element-call.md) with [LiveKit Server](./configuring-playbook-livekit-server.md)"
+msgid "Supporting components ([LiveKit Server](docs/configuring-playbook-livekit-server.md) and [LiveKit JWT Service](docs/configuring-playbook-livekit-jwt-service.md)) for in-app audio/video calls for Matrix clients"
 msgstr ""
 
 #: ../../../README.md:0
-msgid "[Link](docs/configuring-playbook-livekit-jwt-service.md)"
+msgid "[Link](docs/configuring-playbook-matrix-rtc.md)"
 msgstr ""
 
 #: ../../../README.md:85
@@ -692,14 +688,6 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-bridge-appservice-discord.md)"
 msgstr ""
 
-#: ../../../README.md:0
-msgid "[matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack)"
-msgstr ""
-
-#: ../../../README.md:0
-msgid "[Link](docs/configuring-playbook-bridge-appservice-slack.md)"
-msgstr ""
-
 #: ../../../README.md:0
 msgid "[matrix-hookshot](https://github.com/matrix-org/matrix-hookshot)"
 msgstr ""
@@ -796,11 +784,11 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-bridge-postmoogle.md)"
 msgstr ""
 
-#: ../../../README.md:140
+#: ../../../README.md:139
 msgid "Bots"
 msgstr ""
 
-#: ../../../README.md:142
+#: ../../../README.md:141
 msgid "Bots provide various additional functionality to your installation."
 msgstr ""
 
@@ -900,11 +888,11 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-bot-buscarron.md)"
 msgstr ""
 
-#: ../../../README.md:155
+#: ../../../README.md:154
 msgid "Administration"
 msgstr ""
 
-#: ../../../README.md:157
+#: ../../../README.md:156
 msgid "Services that help you in administrating and monitoring your Matrix installation."
 msgstr ""
 
@@ -992,26 +980,14 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-synapse-usage-exporter.md)"
 msgstr ""
 
-#: ../../../README.md:169
+#: ../../../README.md:168
 msgid "Misc"
 msgstr ""
 
-#: ../../../README.md:171
+#: ../../../README.md:170
 msgid "Various services that don't fit any other categories."
 msgstr ""
 
-#: ../../../README.md:0
-msgid "[synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-accept-invite)"
-msgstr ""
-
-#: ../../../README.md:0
-msgid "Synapse module to automatically accept invites"
-msgstr ""
-
-#: ../../../README.md:0
-msgid "[Link](docs/configuring-playbook-synapse-auto-accept-invite.md)"
-msgstr ""
-
 #: ../../../README.md:0
 msgid "[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor)"
 msgstr ""
@@ -1132,54 +1108,54 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-element-call.md)"
 msgstr ""
 
-#: ../../../README.md:187
+#: ../../../README.md:185
 msgid "🆕 Changes"
 msgstr ""
 
-#: ../../../README.md:189
+#: ../../../README.md:187
 msgid "This playbook evolves over time, sometimes with backward-incompatible changes."
 msgstr ""
 
-#: ../../../README.md:191
+#: ../../../README.md:189
 msgid "When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up with what's new."
 msgstr ""
 
-#: ../../../README.md:193
+#: ../../../README.md:191
 msgid "🆘 Support"
 msgstr ""
 
-#: ../../../README.md:195
+#: ../../../README.md:193
 msgid "Matrix room: [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)"
 msgstr ""
 
-#: ../../../README.md:197
+#: ../../../README.md:195
 msgid "IRC channel: `#matrix-docker-ansible-deploy` on the [Libera Chat](https://libera.chat/) IRC network (irc.libera.chat:6697)"
 msgstr ""
 
-#: ../../../README.md:199
+#: ../../../README.md:197
 msgid "GitHub issues: [spantaleev/matrix-docker-ansible-deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues)"
 msgstr ""
 
-#: ../../../README.md:201
+#: ../../../README.md:199
 msgid "🌐 Translation"
 msgstr ""
 
-#: ../../../README.md:203
+#: ../../../README.md:201
 msgid "See the [i18n/README.md](i18n/README.md) file for more information about translation."
 msgstr ""
 
-#: ../../../README.md:205
+#: ../../../README.md:203
 msgid "Translations are still work in progress."
 msgstr ""
 
-#: ../../../README.md:207
+#: ../../../README.md:205
 msgid "🤝 Related"
 msgstr ""
 
-#: ../../../README.md:209
+#: ../../../README.md:207
 msgid "You may also be interested in [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) - another Ansible playbook for self-hosting non-Matrix services (see its [List of supported services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md))."
 msgstr ""
 
-#: ../../../README.md:211
+#: ../../../README.md:209
 msgid "mash-playbook also makes use of [Traefik](./docs/configuring-playbook-traefik.md) as its reverse-proxy, so with minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md), you can make matrix-docker-ansible-deploy and mash-playbook co-exist and host Matrix and non-Matrix services on the same server."
 msgstr ""

i18n/translation-templates/docs/configuring-playbook-bridge-appservice-slack.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -16,242 +16,22 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:12
-msgid "Setting up Appservice Slack bridging (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:14
-msgid "**Notes**:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:15
-msgid "Bridging to [Slack](https://slack.com) can also happen via the [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridge supported by the playbook."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:16
-msgid "Currently (as of November, 2024) **this component is not available for new installation unless you have already created a classic Slack application** (which the bridge makes use of in order to enable bridging between Slack and Matrix), because the creation of classic Slack applications has been discontinued since June 4 2024. The author of the bridge claims [here](https://github.com/matrix-org/matrix-appservice-slack/issues/789#issuecomment-2172947787) that he plans to support the modern Slack application and until then \"the best (and only) option for new installations is to use the webhook bridging\"."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:18
-msgid "The playbook can install and configure [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) for you."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:20
-msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-slack/blob/master/README.md) to learn what it does and why it might be useful to you."
-msgstr ""
-
 #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:22
-msgid "Prerequisites"
+msgid "Setting up Appservice Slack bridging (optional, removed)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:24
-msgid "Create a Classic Slack App"
+msgid "🪦 The playbook used to be able to install and configure [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack), but no longer includes this component, as it had been unavailable for new installation since 2024, and was finally abandoned because the public Matrix.org Slack bridge has been decommissioned on January 14th, 2026."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:26
-msgid "First, you need to create a Classic Slack App [here](https://api.slack.com/apps?new_classic_app=1)."
+msgid "**Note**: Bridging to [Slack](https://slack.com) can also happen via the [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridge supported by the playbook."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:28
-msgid "Name the app \"matrixbot\" (or anything else you'll remember). Select the team/workspace this app will belong to. Click on bot users and add a new bot user. We will use this account to bridge the the rooms."
+msgid "Uninstalling the component manually"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-appservice-slack.md:30
-msgid "Then, click on Event Subscriptions and enable them and use the request url: `https://matrix.example.com/appservice-slack`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:32
-msgid "Add the following events as `Bot User Events` and save:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:34
-msgid "team_domain_change"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:35
-msgid "message.channels"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:36
-msgid "message.groups (if you want to bridge private channels)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:37
-msgid "reaction_added"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:38
-msgid "reaction_removed"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:40
-msgid "Next, click on \"OAuth & Permissions\" and add the following scopes:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:42
-msgid "chat:write:bot"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:43
-msgid "users:read"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:44
-msgid "reactions:write"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:45
-msgid "files:write:user (if you want to bridge files)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:47
-msgid "**Note**: In order to make Slack files visible to Matrix users, this bridge will make Slack files visible to anyone with the url (including files in private channels). This is different than the current behavior in Slack, which only allows authenticated access to media posted in private channels. See MSC701 for details."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:49
-msgid "Click on \"Install App\" and \"Install App to Workspace\". Note the access tokens shown. You will need the Bot User OAuth Access Token and if you want to bridge files, the OAuth Access Token whenever you link a room."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:51
-msgid "Create an administration control room on Matrix"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:53
-msgid "Create a new Matrix room to act as the administration control room."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:55
-msgid "Note its internal room ID. This can be done in Element Web by sending a message, opening the options for that message and choosing \"view source\". The room ID will be displayed near the top."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:57
-msgid "Adjusting the playbook configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:59
-msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:75
-msgid "Extending the configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:77
-msgid "There are some additional things you may wish to configure about the bridge."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:79
-msgid "Take a look at:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:81
-msgid "`roles/custom/matrix-bridge-appservice-slack/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:82
-msgid "`roles/custom/matrix-bridge-appservice-slack/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_appservice_slack_configuration_extension_yaml` variable"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:84
-msgid "For example, to change the bot's username from `slackbot`, add the following configuration to your `vars.yml` file. Replace `examplebot` with your own."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:91
-msgid "Installing"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:93
-msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:100
-msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:102
-msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:104
-msgid "Usage"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:106
-msgid "To use the bridge, you need to send `/invite @slackbot:example.com` to invite the bridge bot user into the admin room."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:108
-msgid "If Team Sync is not enabled, for each channel you would like to bridge, perform the following steps:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:110
-msgid "Create a Matrix room in the usual manner for your client. Take a note of its Matrix room ID — it will look something like `!qporfwt:example.com`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:111
-msgid "Invite the bot user to both the Slack and Matrix channels you would like to bridge using `/invite @matrixbot` for Slack and `/invite @slackbot:example.com` for Matrix."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:112
-msgid "Determine the \"channel ID\" that Slack uses to identify the channel. You can see it when you open a given Slack channel in a browser. The URL reads like this: `https://app.slack.com/client/XXX/<the channel ID>/details/`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:113
-msgid "Issue a link command in the administration control room with these collected values as arguments:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:115
-msgid "with file bridging:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:121
-msgid "without file bridging:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:127
-msgid "These arguments can be shortened to single-letter forms:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:133
-msgid "Unlinking"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:135
-msgid "Channels can be unlinked again by sending this:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:141
-msgid "Unlinking doesn't only disconnect the bridge, but also makes the slackbot leave the bridged Matrix room. So in case you want to re-link later, don't forget to re-invite the slackbot into this room again."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:143
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:145
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-appservice-slack`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:147
-msgid "Linking: \"Room is now pending-name\""
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:149
-msgid "This typically means that you haven't used the correct Slack channel ID. Unlink the room and recheck 'Determine the \"channel ID\"' from above."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:151
-msgid "Messages work from Matrix to Slack, but not the other way around"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:153
-msgid "Check the logs, and if you find the message like below, unlink your room, reinvite the bot and re-link it again."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:155
-msgid "`WARN SlackEventHandler Ignoring message from unrecognised Slack channel ID : %s (%s) <the channel ID> <some other ID>`"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:157
-msgid "This may particularly hit you, if you tried to unsuccessfully link your room multiple times without unlinking it after each failed attempt."
+msgid "If you still have matrix-appservice-slack installed on your Matrix server, the playbook can no longer help you uninstall it and you will need to do it manually. To uninstall manually, run these commands on the server:"
 msgstr ""

i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-discord.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -28,130 +28,146 @@ msgstr ""
 msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md) bridge supported by the playbook."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:18
-msgid "For using as a Bot we recommend the [Appservice Discord](configuring-playbook-bridge-appservice-discord.md), because it supports plumbing."
-msgstr ""
-
 #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:19
-msgid "For personal use with a discord account we recommend the `mautrix-discord` bridge (the one being discussed here), because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook."
+msgid "The playbook can install and configure [mautrix-discord](https://github.com/mautrix/discord) for you."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:21
-msgid "The playbook can install and configure [mautrix-discord](https://github.com/mautrix/discord) for you."
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/discord/index.html) to learn what it does and why it might be useful to you."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:23
-msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/discord/index.html) to learn what it does and why it might be useful to you."
+msgid "Prerequisites"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:25
-msgid "Prerequisites"
+msgid "There are 3 ways to login to discord using this bridge, either by [scanning a QR code](https://docs.mau.fi/bridges/go/discord/authentication.html#qr-login) using the Discord mobile app, by using a [Discord token](https://docs.mau.fi/bridges/go/discord/authentication.html#token-login), **or** by using a [Discord bot token](https://docs.mau.fi/bridges/go/discord/authentication.html#bot-token-login)."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:27
-msgid "There are 2 ways to login to discord using this bridge, either by [scanning a QR code](#method-1-login-using-qr-code-recommended) using the Discord mobile app **or** by using a [Discord token](#method-2-login-using-discord-token-not-recommended)."
+msgid "⚠️ QR code login is considered a self-bot and is forbidden by Discord. It can result in an account termination. See the [Discord policy](https://support.discord.com/hc/en-us/articles/115002192352-Automated-User-Accounts-Self-Bots)."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:29
-msgid "If this is a dealbreaker for you, consider using [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md). This comes with its own complexity and limitations, however, so we recommend that you proceed with this one if possible."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:31
 msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:33
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:31
 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:35
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:33
 msgid "See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:37
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:35
 msgid "**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:39
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:37
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:41
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:39
 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:47
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:45
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:49
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:47
 msgid "There are some additional things you may wish to configure about the bridge."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:52
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:50
 msgid "See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:54
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:52
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:56
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:54
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:63
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:61
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:65
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:63
 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:67
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:65
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:69
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:67
 msgid "To use the bridge, you need to start a chat with `@discordbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:71
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:69
 msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/discord/authentication.html)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:73
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:71
 msgid "After logging in, the bridge will create portal rooms for some recent direct messages."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:75
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:73
 msgid "Bridge guilds"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:77
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:75
 msgid "If you'd like to bridge guilds, send `guilds status` to see the list of guilds, then send `guilds bridge GUILD_ID_HERE` for each guild that you'd like bridged. Make sure to replace `GUILD_ID_HERE` with the guild's ID."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:79
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:77
 msgid "After bridging, spaces will be created automatically, and rooms will be created if necessary when messages are received. You can also pass `--entire` to the bridge command to immediately create all rooms."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:81
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:79
 msgid "If you want to manually bridge channels, invite the bot to the room you want to bridge, and run `!discord bridge CHANNEL_ID_HERE` to bridge the room. Make sure to replace `CHANNEL_ID_HERE` with the channel's ID."
 msgstr ""
 
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:81
+msgid "Enable relay"
+msgstr ""
+
 #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:83
-msgid "Troubleshooting"
+msgid "The bridge supports using Discord's webhook feature to relay messages from Matrix users who haven't logged into the bridge."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:85
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-discord`."
+msgid "In a room that has already been bridged, run `!discord set-relay --create`. The bridge will then create a webhook in the bridged discord channel and begin relaying messages. If the discord user does not have access to manage webhooks, run `!discord set-relay --url <url>` with the url of an already created webhook. (See Discords [Intro to webhooks](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks))"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:87
-msgid "Increase logging verbosity"
+msgid "More information on relaying is available on the [official documentation](https://docs.mau.fi/bridges/go/discord/relay.html)."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:89
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:91
+msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-discord`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:93
+msgid "Increase logging verbosity"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:95
 msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
 msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:102
+msgid "Command requires room admin rights when user is creator"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:104
+msgid "[MSC4289](https://github.com/matrix-org/matrix-spec-proposals/blob/main/proposals/4289-privilege-creators.md), introduced in [room version 12](https://spec.matrix.org/unstable/rooms/v12/), gives creators an infinitley high powerlevel. At the time of implementation, mautrix-discord and similar applications may not identify creators as or above admins. Either a separate admin user will need to manage the bridge or the room version should be less than version 12."
+msgstr ""

i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-slack.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -25,117 +25,105 @@ msgid "<sup>Refer the common guide for configuring mautrix bridges: [Setting up
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:14
-msgid "**Note**: bridging to [Slack](https://slack.com/) can also happen via the [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) bridge supported by the playbook."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:15
-msgid "For using as a Bot we recommend the [Appservice Slack](configuring-playbook-bridge-appservice-slack.md), because it supports plumbing. Note that it is not available for new installation unless you have already created a classic Slack application, because the creation of classic Slack applications, which this bridge makes use of, has been discontinued."
+msgid "The playbook can install and configure [mautrix-slack](https://github.com/mautrix/slack) for you."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:16
-msgid "For personal use with a slack account we recommend the `mautrix-slack` bridge (the one being discussed here), because it is the most fully-featured and stable of the 3 Slack bridges supported by the playbook."
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/slack/index.html) to learn what it does and why it might be useful to you."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:18
-msgid "The playbook can install and configure [mautrix-slack](https://github.com/mautrix/slack) for you."
+msgid "See the [features and roadmap](https://github.com/mautrix/slack/blob/main/ROADMAP.md) for more information."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:20
-msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/slack/index.html) to learn what it does and why it might be useful to you."
+msgid "Prerequisites"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:22
-msgid "See the [features and roadmap](https://github.com/mautrix/slack/blob/main/ROADMAP.md) for more information."
+msgid "For using this bridge, you would need to authenticate by **providing your username and password** (legacy) or by using a **token login**. See more information in the [docs](https://docs.mau.fi/bridges/go/slack/authentication.html)."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:24
-msgid "Prerequisites"
+msgid "Note that neither of these methods are officially supported by Slack."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:26
-msgid "For using this bridge, you would need to authenticate by **providing your username and password** (legacy) or by using a **token login**. See more information in the [docs](https://docs.mau.fi/bridges/go/slack/authentication.html)."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:28
-msgid "Note that neither of these methods are officially supported by Slack. [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) uses a Slack bot account which is the only officially supported method for bridging a Slack channel."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:30
 msgid "Enable Appservice Double Puppet (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:32
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:28
 msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:34
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:30
 msgid "See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:36
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:32
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:38
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:34
 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:44
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:40
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:46
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:42
 msgid "There are some additional things you may wish to configure about the bridge."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:48
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:44
 msgid "See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:50
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:46
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:52
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:48
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:59
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:55
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:61
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:57
 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:63
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:59
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:65
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:61
 msgid "To use the bridge, you need to start a chat with `@slackbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:67
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:63
 msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/slack/authentication.html)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:69
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:65
 msgid "If you authenticated using a token, the recent chats will be bridged automatically (depending on the `conversation_count` setting). Otherwise (i.e. logging with the Discord application), the chats the bot is in will be bridged automatically."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:71
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:67
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:73
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:69
 msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-slack`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:75
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:71
 msgid "Increase logging verbosity"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:77
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:73
 msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
 msgstr ""

i18n/translation-templates/docs/configuring-playbook-client-sable.pot

@@ -0,0 +1,113 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2026, Slavi Pantaleev, Aine Etke, MDAD community members
+# This file is distributed under the same license as the matrix-docker-ansible-deploy package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../../docs/configuring-playbook-client-sable.md:9
+msgid "Setting up Sable (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:11
+msgid "The playbook can install and configure the [Sable](https://github.com/7w1/sable) Matrix web client for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:13
+msgid "Sable is a web client focusing primarily on simple, elegant and secure interface. It can be installed alongside or instead of [Element Web](./configuring-playbook-client-element-web.md), [Cinny](./configuring-playbook-client-cinny.md) and others."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:15
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:17
+msgid "By default, this playbook installs Sable on the `sable.` subdomain (`sable.example.com`) and requires you to create a CNAME record for `sable`, which targets `matrix.example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:19
+msgid "When setting, replace `example.com` with your own."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:21
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:23
+msgid "To enable Sable, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:29
+msgid "Adjusting the Sable URL (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:31
+msgid "By tweaking the `sable_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:33
+msgid "Example additional configuration for your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:43
+msgid "After changing the domain, **you may need to adjust your DNS** records to point the Sable domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:45
+msgid "**Note**: while there is a `sable_path_prefix` variable for changing the path where Sable is served, overriding it is [not possible](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Sable requires an application rebuild (with a tweaked build config) to be functional under a custom path. You'd need to serve Sable at a dedicated subdomain."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:47
+msgid "Extending the configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:49
+msgid "There are some additional things you may wish to configure about the component."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:51
+msgid "Take a look at:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:53
+msgid "`roles/galaxy/sable/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:54
+msgid "`roles/galaxy/sable/templates/config.json.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `sable_configuration_extension_json` variable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:56
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:58
+msgid "After configuring the playbook and [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:65
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:67
+msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:69
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-sable.md:71
+msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-client-sable`."
+msgstr ""

i18n/translation-templates/docs/configuring-playbook-continuwuity.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -93,69 +93,69 @@ msgid "Unlike other homeserver implementations (like Synapse and Dendrite), cont
 msgstr ""
 
 #: ../../../docs/configuring-playbook-continuwuity.md:61
-msgid "If you followed the instructions above (see [Adjusting the playbook configuration](#adjusting-the-playbook-configuration)), you should have registration enabled and protected by a registration token."
+msgid "On first startup, Continuwuity creates a special one-time-use registration token and logs it to the server's console. To access this, you will need to SSH into the server and run the following command:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-continuwuity.md:63
-msgid "This should allow you to create the first user account via any client (like [Element Web](./configuring-playbook-client-element-web.md)) which supports creating users."
+#: ../../../docs/configuring-playbook-continuwuity.md:68
+msgid "Find the token, highlight it, and copy it (ctrl+shift+C). This token should allow you to create the first user account via any client (like [Element Web](./configuring-playbook-client-element-web.md)) which supports creating users."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-continuwuity.md:65
+#: ../../../docs/configuring-playbook-continuwuity.md:70
 msgid "The **first user account that you create will be marked as an admin** and **will be automatically invited to an admin room**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-continuwuity.md:68
+#: ../../../docs/configuring-playbook-continuwuity.md:73
 msgid "Configuring bridges / appservices"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-continuwuity.md:70
+#: ../../../docs/configuring-playbook-continuwuity.md:75
 msgid "For other homeserver implementations (like Synapse and Dendrite), the playbook automatically registers appservices (for bridges, bots, etc.) with the homeserver."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-continuwuity.md:72
+#: ../../../docs/configuring-playbook-continuwuity.md:77
 msgid "For continuwuity, you will have to manually register appservices using the [`!admin appservices register` command](https://continuwuity.org/appservices.html#set-up-the-appservice---general-instructions) sent to the server bot account."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-continuwuity.md:74
+#: ../../../docs/configuring-playbook-continuwuity.md:79
 msgid "The server's bot account has a Matrix ID of `@conduit:example.com` (not `@continuwuity:example.com`!) due to continuwuity's historical legacy. Your first user account would already have been invited to an admin room with this bot."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-continuwuity.md:77
+#: ../../../docs/configuring-playbook-continuwuity.md:82
 msgid "Find the appservice file you'd like to register. This can be any `registration.yaml` file found in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-continuwuity.md:79
+#: ../../../docs/configuring-playbook-continuwuity.md:84
 msgid "Then, send its content to the existing admin room:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-continuwuity.md:103
+#: ../../../docs/configuring-playbook-continuwuity.md:108
 msgid "Migrating from conduwuit"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-continuwuity.md:105
+#: ../../../docs/configuring-playbook-continuwuity.md:110
 msgid "Since Continuwuity is a drop-in replacement for [conduwuit](configuring-playbook-conduwuit.md), migration is possible."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-continuwuity.md:107
+#: ../../../docs/configuring-playbook-continuwuity.md:112
 msgid "Make sure that Continuwuity is properly set up on your `vars.yml` as described above"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-continuwuity.md:109
+#: ../../../docs/configuring-playbook-continuwuity.md:114
 msgid "Make sure that Conduwuit references are removed from your `vars.yml` file"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-continuwuity.md:111
+#: ../../../docs/configuring-playbook-continuwuity.md:116
 msgid "Run the installation in a way that installs new services and uninstalls old ones (e.g. `just setup-all`)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-continuwuity.md:113
+#: ../../../docs/configuring-playbook-continuwuity.md:118
 msgid "Run the playbook with the `continuwuity-migrate-from-conduwuit` tag (e.g. `just run-tags continuwuity-migrate-from-conduwuit`). This migrates data from `/matrix/conduwuit` to `/matrix/continuwuity`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-continuwuity.md:115
+#: ../../../docs/configuring-playbook-continuwuity.md:120
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-continuwuity.md:117
+#: ../../../docs/configuring-playbook-continuwuity.md:122
 msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-continuwuity`."
 msgstr ""

i18n/translation-templates/docs/configuring-playbook-email.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -41,89 +41,109 @@ msgid "📁 `roles/galaxy/exim_relay/docs/configuring-exim-relay.md` locally, if
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:20
-msgid "Firewall settings"
+msgid "Why use exim-relay?"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:22
-msgid "No matter whether you send email directly (the default) or you relay email through another host, you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration)."
+msgid "**Benefits of using exim-relay** instead of configuring SMTP directly in each service:"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:24
-msgid "Docker automatically opens these ports in the server's firewall, so you likely don't need to do anything. If you use another firewall in front of the server, you may need to adjust it."
+msgid "**Final delivery capability**: Can deliver emails directly if you don't have an SMTP server"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:26
-msgid "Adjusting the playbook configuration"
+msgid "**Centralized configuration**: Configure your upstream SMTP server once in exim-relay, then point all services ([Synapse](configuring-playbook-synapse.md), [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), etc.) there—no need to configure SMTP in each component"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:28
-msgid "Enable DKIM authentication to improve deliverability (optional)"
+msgid "**Local spooling**: Stores messages locally and retries delivery if your upstream SMTP server is temporarily unavailable"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:30
-msgid "By default, exim-relay attempts to deliver emails directly. This may or may not work, depending on your domain configuration."
+msgid "Firewall settings"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:32
-msgid "To improve email deliverability, you can configure authentication methods such as DKIM (DomainKeys Identified Mail), SPF, and DMARC for your domain. Without setting any of these authentication methods, your outgoing email is most likely to be quarantined as spam at recipient's mail servers."
+msgid "No matter whether you send email directly (the default) or you relay email through another host, you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration)."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:34
-msgid "For details about configuring DKIM, refer [this section](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md#enable-dkim-support-optional) on the role's documentation."
+msgid "Docker automatically opens these ports in the server's firewall, so you likely don't need to do anything. If you use another firewall in front of the server, you may need to adjust it."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:36
-msgid "💡 If you cannot enable DKIM, SPF, or DMARC on your domain for some reason, we recommend relaying email through another SMTP server."
+msgid "Adjusting the playbook configuration"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:38
-msgid "Relaying email through another SMTP server (optional)"
+msgid "Enable DKIM authentication to improve deliverability (optional)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:40
-msgid "**On some cloud providers such as Google Cloud, [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible.** In this case, you will need to relay email through another SMTP server."
+msgid "By default, exim-relay attempts to deliver emails directly. This may or may not work, depending on your domain configuration."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:42
-msgid "For details about configuration, refer [this section](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md#relaying-email-through-another-smtp-server) on the role's document."
+msgid "To improve email deliverability, you can configure authentication methods such as DKIM (DomainKeys Identified Mail), SPF, and DMARC for your domain. Without setting any of these authentication methods, your outgoing email is most likely to be quarantined as spam at recipient's mail servers."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:44
-msgid "Disable mail service (optional)"
+msgid "For details about configuring DKIM, refer [this section](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md#enable-dkim-support-optional) on the role's documentation."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:46
-msgid "For a low-power server you might probably want to disable exim-relay. To do so, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgid "💡 If you cannot enable DKIM, SPF, or DMARC on your domain for some reason, we recommend relaying email through another SMTP server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:48
+msgid "Relaying email through another SMTP server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:50
+msgid "**On some cloud providers such as Google Cloud, [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible.** In this case, you will need to relay email through another SMTP server."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:52
-msgid "Note that disabling exim-relay will stop email-notifications and other similar functions from working."
+msgid "For details about configuration, refer [this section](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md#relaying-email-through-another-smtp-server) on the role's document."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:54
-msgid "See [this entry on the FAQ](faq.md#how-do-i-optimize-this-setup-for-a-low-power-server) for other possible optimizations for a low-power server."
+msgid "Disable mail service (optional)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-email.md:56
+msgid "For a low-power server you might probably want to disable exim-relay. To do so, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:62
+msgid "Note that disabling exim-relay will stop email-notifications and other similar functions from working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:64
+msgid "See [this entry on the FAQ](faq.md#how-do-i-optimize-this-setup-for-a-low-power-server) for other possible optimizations for a low-power server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:66
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-email.md:58
+#: ../../../docs/configuring-playbook-email.md:68
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-email.md:65
+#: ../../../docs/configuring-playbook-email.md:75
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-email.md:67
+#: ../../../docs/configuring-playbook-email.md:77
 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-email.md:69
+#: ../../../docs/configuring-playbook-email.md:79
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-email.md:71
+#: ../../../docs/configuring-playbook-email.md:81
 msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md#troubleshooting) on the role's documentation for details."
 msgstr ""

i18n/translation-templates/docs/configuring-playbook-jitsi.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -25,149 +25,153 @@ msgid "The playbook can install and configure the [Jitsi](https://jitsi.org/) vi
 msgstr ""
 
 #: ../../../docs/configuring-playbook-jitsi.md:21
+msgid "Because Jitsi still requires a TURN server, enabling Jitsi automatically enables coturn (`coturn_enabled: true`) unless you explicitly disable it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:24
 msgid "Jitsi is an open source video-conferencing platform. It can not only be integrated with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS) as a widget, but also be used as standalone web app."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:23
+#: ../../../docs/configuring-playbook-jitsi.md:26
 msgid "💡 If you're into experimental technology, you may also be interested in trying out [Element Call](configuring-playbook-element-call.md) - a native Matrix video conferencing application."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:25
+#: ../../../docs/configuring-playbook-jitsi.md:28
 msgid "The [Ansible role for Jitsi](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring Jitsi, you can check them via:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:26
+#: ../../../docs/configuring-playbook-jitsi.md:29
 msgid "🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md) online"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:27
+#: ../../../docs/configuring-playbook-jitsi.md:30
 msgid "📁 `roles/galaxy/jitsi/docs/configuring-jitsi.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:29
+#: ../../../docs/configuring-playbook-jitsi.md:32
 msgid "Prerequisites"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:31
+#: ../../../docs/configuring-playbook-jitsi.md:34
 msgid "Before proceeding, make sure to check server's requirements recommended by [the official deployment guide](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-requirements)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:33
+#: ../../../docs/configuring-playbook-jitsi.md:36
 msgid "You may need to open some ports to your server, if you use another firewall in front of the server. Refer [the role's documentation](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#prerequisites) to check which ones to be configured."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:35
+#: ../../../docs/configuring-playbook-jitsi.md:38
 msgid "Adjusting DNS records"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:37
+#: ../../../docs/configuring-playbook-jitsi.md:40
 msgid "By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to create a CNAME record for `jitsi`, which targets `matrix.example.com`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:39
+#: ../../../docs/configuring-playbook-jitsi.md:42
 msgid "When setting, replace `example.com` with your own."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:41
+#: ../../../docs/configuring-playbook-jitsi.md:44
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:43
+#: ../../../docs/configuring-playbook-jitsi.md:46
 msgid "To enable Jitsi, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:61
+#: ../../../docs/configuring-playbook-jitsi.md:64
 msgid "As the most of the necessary settings for the role have been taken care of by the playbook, you can enable Jitsi on your Matrix server with this minimum configuration."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:63
+#: ../../../docs/configuring-playbook-jitsi.md:66
 msgid "However, **since Jitsi's performance heavily depends on server resource (bandwidth, RAM, and CPU), it is recommended to review settings and optimize them as necessary before deployment.** You can check [here](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#example-configurations) for an example set of configurations to set up a Jitsi instance, focusing on performance. If you will host a large conference, you probably might also want to consider to provision additional JVBs ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)). See [here](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#set-up-additional-jvbs-for-more-video-conferences-optional) for details about setting them up with the playbook."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:65
+#: ../../../docs/configuring-playbook-jitsi.md:68
 msgid "See the role's documentation for details about configuring Jitsi per your preference (such as setting [a custom hostname](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#set-the-hostname) and [the environment variable for running Jitsi in a LAN](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#configure-jvb_advertise_ips-for-running-behind-nat-or-on-a-lan-environment-optional))."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:67
+#: ../../../docs/configuring-playbook-jitsi.md:70
 msgid "Enable authentication and guests mode (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:69
+#: ../../../docs/configuring-playbook-jitsi.md:72
 msgid "By default the Jitsi Meet instance **does not require for anyone to log in, and is open to use without an account**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:71
+#: ../../../docs/configuring-playbook-jitsi.md:74
 msgid "If you would like to control who is allowed to start meetings on your instance, you'd need to enable Jitsi's authentication and optionally guests mode."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:73
+#: ../../../docs/configuring-playbook-jitsi.md:76
 msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#configure-jitsi-authentication-and-guests-mode-optional) on the role's documentation for details about how to configure the authentication and guests mode. The recommended authentication method is `internal` as it also works in federated rooms. If you want to enable authentication with Matrix OpenID making use of [Matrix User Verification Service (UVS)](configuring-playbook-user-verification-service.md), see [here](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix) for details about how to set it up."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:75
+#: ../../../docs/configuring-playbook-jitsi.md:78
 msgid "Enable Gravatar (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:77
+#: ../../../docs/configuring-playbook-jitsi.md:80
 msgid "In the default Jisti Meet configuration, `gravatar.com` is enabled as an avatar service."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:79
+#: ../../../docs/configuring-playbook-jitsi.md:82
 msgid "Since the Element clients send the URL of configured Matrix avatars to the Jitsi instance, our configuration has disabled the Gravatar service."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:81
+#: ../../../docs/configuring-playbook-jitsi.md:84
 msgid "To enable the Gravatar service nevertheless, add the following configuration to your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:87
+#: ../../../docs/configuring-playbook-jitsi.md:90
 msgid "[!WARNING] This will result in third party request leaking data to the Gravatar Service (`gravatar.com`, unless configured otherwise). Besides metadata, the Matrix user_id and possibly the room ID (via `referrer` header) will be also sent to the third party."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:90
+#: ../../../docs/configuring-playbook-jitsi.md:93
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:92
+#: ../../../docs/configuring-playbook-jitsi.md:95
 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:99
+#: ../../../docs/configuring-playbook-jitsi.md:102
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:101
+#: ../../../docs/configuring-playbook-jitsi.md:104
 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:103
+#: ../../../docs/configuring-playbook-jitsi.md:106
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:105
+#: ../../../docs/configuring-playbook-jitsi.md:108
 msgid "You can use the self-hosted Jitsi server in multiple ways:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:107
+#: ../../../docs/configuring-playbook-jitsi.md:110
 msgid "**by adding a widget to a room via Element Web** (the one configured by the playbook at `https://element.example.com`). Just start a voice or a video call in a room containing more than 2 members and that would create a Jitsi widget which utilizes your self-hosted Jitsi server."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:109
+#: ../../../docs/configuring-playbook-jitsi.md:112
 msgid "**directly (without any Matrix integration)**. Just go to `https://jitsi.example.com`, and you can start a videoconference."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:111
+#: ../../../docs/configuring-playbook-jitsi.md:114
 msgid "Note that you'll need to log in to your Jitsi's account to start a conference if you have configured authentication with `internal` auth."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:113
+#: ../../../docs/configuring-playbook-jitsi.md:116
 msgid "Check [the official user guide](https://jitsi.github.io/handbook/docs/category/user-guide) for details about how to use Jitsi."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:115
+#: ../../../docs/configuring-playbook-jitsi.md:118
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-jitsi.md:117
+#: ../../../docs/configuring-playbook-jitsi.md:120
 msgid "See [this section](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#troubleshooting) on the role's documentation for details."
 msgstr ""

i18n/translation-templates/docs/configuring-playbook-livekit-server.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -41,7 +41,7 @@ msgid "🌐 [the role's documentation at the MASH project](https://github.com/mo
 msgstr ""
 
 #: ../../../docs/configuring-playbook-livekit-server.md:18
-msgid "📁 `roles/galaxy/livekit-server/docs/configuring-livekit-server.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)"
+msgid "📁 `roles/galaxy/livekit_server/docs/configuring-livekit-server.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-livekit-server.md:20
@@ -69,17 +69,69 @@ msgid "`5350/tcp`: TURN/TCP. Also see the [Limitations](#limitations) section be
 msgstr ""
 
 #: ../../../docs/configuring-playbook-livekit-server.md:32
-msgid "💡 The suggestions above are inspired by the upstream [Ports and Firewall](https://docs.livekit.io/home/self-hosting/ports-firewall/) documentation based on how LiveKit is configured in the playbook. If you've using custom configuration for the LiveKit Server role, you may need to adjust the firewall rules accordingly."
+msgid "`30000-30020/udp`: TURN relay range used by LiveKit's embedded TURN server."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-livekit-server.md:34
-msgid "Limitations"
+msgid "💡 The suggestions above are inspired by the upstream [Ports and Firewall](https://docs.livekit.io/home/self-hosting/ports-firewall/) documentation based on how LiveKit is configured in the playbook. If you're using custom configuration for the LiveKit Server role, you may need to adjust firewall rules accordingly."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-livekit-server.md:36
-msgid "For some reason, LiveKit Server's TURN ports (`3479/udp` and `5350/tcp`) are not reachable over IPv6 regardless of whether you've [enabled IPv6](./configuring-ipv6.md) for your server."
+msgid "TURN TLS handling"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-livekit-server.md:38
-msgid "It seems like LiveKit Server intentionally only listens on `udp4` and `tcp4` as seen [here](https://github.com/livekit/livekit/blob/154b4d26b769c68a03c096124094b97bf61a996f/pkg/service/turn.go#L128) and [here](https://github.com/livekit/livekit/blob/154b4d26b769c68a03c096124094b97bf61a996f/pkg/service/turn.go#L92)."
+msgid "When `matrix_playbook_reverse_proxy_type` is `playbook-managed-traefik` (which is the default for this playbook), TURN over TCP is terminated by Traefik and forwarded to LiveKit with `turn.external_tls = true`. In this playbook default, this mode is enabled automatically when SSL is enabled and TURN is enabled."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-livekit-server.md:40
+msgid "The playbook installs a dedicated Traefik TCP entrypoint for TURN (`matrix-livekit-turn`) by default and binds it to `tcp/5350`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-livekit-server.md:41
+msgid "`livekit_server_config_turn_external_tls` is automatically enabled for this setup."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-livekit-server.md:42
+msgid "Because Traefik handles TLS, LiveKit no longer needs certificate-file paths for TURN in this mode."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-livekit-server.md:44
+msgid "To opt out and keep TURN TLS termination in LiveKit itself, set:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-livekit-server.md:50
+msgid "In this playbook, certificate paths are managed automatically via `group_vars/matrix_servers` when certificate dumping is enabled."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-livekit-server.md:52
+msgid "If your setup uses `other-traefik-container` or [another reverse-proxy](./configuring-playbook-own-webserver.md), behavior is unchanged by default and still relies on certificates being available inside the container as before."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-livekit-server.md:54
+msgid "Deployments using `other-traefik-container` can opt into the same Traefik-terminated mode there, by setting:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-livekit-server.md:62
+msgid "and configuring their own Traefik TCP entrypoint dedicated to LiveKit TURN traffic."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-livekit-server.md:64
+msgid "Limitations"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-livekit-server.md:66
+msgid "LiveKit Server's TURN listener behavior depends on where TLS is terminated:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-livekit-server.md:68
+msgid "Direct LiveKit TURN listeners (`livekit_server_config_turn_external_tls: false`) still use IPv4-only sockets for `3479/udp` and `5350/tcp`, so IPv6 connectivity to these endpoints is not possible."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-livekit-server.md:69
+msgid "With [TURN TLS handling](#turn-tls-handling) (`livekit_server_config_turn_external_tls: true`), the playbook's dedicated `matrix-livekit-turn` TCP entrypoint can still listen on both IPv4 and IPv6. Traefik then forwards TURN/TCP to LiveKit."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-livekit-server.md:71
+msgid "It appears that LiveKit Server intentionally only listens on `udp4` and `tcp4` in direct mode, as seen [here](https://github.com/livekit/livekit/blob/154b4d26b769c68a03c096124094b97bf61a996f/pkg/service/turn.go#L128) and [here](https://github.com/livekit/livekit/blob/154b4d26b769c68a03c096124094b97bf61a996f/pkg/service/turn.go#L92)."
 msgstr ""

i18n/translation-templates/docs/configuring-playbook-matrix-rtc.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -45,11 +45,11 @@ msgid "Various experimental features for the Synapse homeserver which Element Ca
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-rtc.md:20
-msgid "A [LiveKit Server](configuring-playbook-livekit-server.md) (automatically installed when [Element Call or the Matrix RTC stack is enabled](#decide-between-element-call-vs-just-the-matrix-rtc-stack))"
+msgid "A [LiveKit Server](configuring-playbook-livekit-server.md) (automatically installed when [Element Call or the Matrix RTC stack is enabled](configuring-playbook-element-call.md#decide-between-element-call-vs-just-the-matrix-rtc-stack))"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-rtc.md:21
-msgid "The [LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md) (automatically installed when [Element Call or the Matrix RTC stack is enabled](#decide-between-element-call-vs-just-the-matrix-rtc-stack))"
+msgid "The [LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md) (automatically installed when [Element Call or the Matrix RTC stack is enabled](configuring-playbook-element-call.md#decide-between-element-call-vs-just-the-matrix-rtc-stack))"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-rtc.md:22

i18n/translation-templates/docs/configuring-playbook-prometheus-grafana.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -143,7 +143,7 @@ msgid "[Prometheus role](https://github.com/mother-of-all-self-hosting/ansible-r
 msgstr ""
 
 #: ../../../docs/configuring-playbook-prometheus-grafana.md:109
-msgid "`roles/custom/matrix-prometheus-nginxlog-exporter/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
+msgid "`roles/galaxy/prometheus_nginxlog_exporter/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-prometheus-grafana.md:111
@@ -315,19 +315,19 @@ msgid "Set this to `true` to expose the [Postgres exporter](#enable-metrics-and-
 msgstr ""
 
 #: ../../../docs/configuring-playbook-prometheus-grafana.md:0
-msgid "`matrix_prometheus_nginxlog_exporter_enabled`"
+msgid "`prometheus_nginxlog_exporter_enabled`"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-prometheus-grafana.md:0
-msgid "Set this to `true` to enable the [nginx Log exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) (locally, on the container network)."
+msgid "Set this to `true` to enable the [prometheus-nginxlog-exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) (locally, on the container network)."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-prometheus-grafana.md:0
-msgid "`matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled`"
+msgid "`prometheus_nginxlog_exporter_container_labels_traefik_enabled`"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-prometheus-grafana.md:0
-msgid "Set this to `true` to expose the [nginx Log exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) metrics on `https://matrix.example.com/metrics/nginxlog`."
+msgid "Set this to `true` to expose the [prometheus-nginxlog-exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) metrics on `https://matrix.example.com/metrics/nginxlog`."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-prometheus-grafana.md:187

i18n/translation-templates/docs/configuring-playbook-synapse-admin.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -21,125 +21,137 @@ msgid "Setting up Synapse Admin (optional)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse-admin.md:15
-msgid "The playbook can install and configure [etkecc/synapse-admin](https://github.com/etkecc/synapse-admin) (a [feature-rich](https://github.com/etkecc/synapse-admin#fork-differences) fork of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin), community room: [#synapse-admin:etke.cc](https://matrix.to/#/#synapse-admin:etke.cc)) for you."
+msgid "The playbook can install and configure Synapse Admin for you."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse-admin.md:17
-msgid "synapse-admin is a web UI tool you can use to **administrate users, rooms, media, etc. on your Matrix server**. It's designed to work with the Synapse homeserver implementation and WON'T work with Dendrite because [Dendrite Admin API](https://element-hq.github.io/dendrite/administration/adminapi) differs from [Synapse Admin API](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/)."
+msgid "Synapse Admin is a web UI tool you can use to **administrate users, rooms, media, etc. on your Matrix homeserver**. This playbook is configured to install [etkecc/synapse-admin](https://github.com/etkecc/synapse-admin), which is a [feature-rich](https://github.com/etkecc/synapse-admin#fork-differences) fork of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin)."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse-admin.md:19
-msgid "💡 **Note**: the latest version of synapse-admin is hosted by [etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). If you only need this service occasionally and trust giving your admin credentials to a 3rd party Single Page Application, you can consider using it from there and avoiding the (small) overhead of self-hosting."
+msgid "[!NOTE]"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse-admin.md:21
-msgid "💡 **Note**: The playbook also supports an alternative management UI in the shape of [Element Admin](./configuring-playbook-element-admin.md). However, it's currently less feature-rich than Synapse Admin and has a dependency on [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md)."
+msgid "Synapse Admin does not work with other homeserver implementations than Synapse due to API's incompatibility."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:22
+msgid "The latest version of Synapse Admin is hosted by [etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). If you only need this service occasionally and trust giving your admin credentials to a 3rd party Single Page Application, you can consider using it from there and avoiding the (small) overhead of self-hosting."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse-admin.md:23
-msgid "Adjusting DNS records (optional)"
+msgid "This playbook also supports an alternative management UI in the shape of [Element Admin](./configuring-playbook-element-admin.md). Please note that it's currently less feature-rich than Synapse Admin and requires [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md)."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse-admin.md:25
-msgid "By default, this playbook installs Synapse Admin on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section."
+msgid "Adjusting DNS records (optional)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse-admin.md:27
-msgid "If you wish to adjust it, see the section [below](#adjusting-the-synapse-admin-url-optional) for details about DNS configuration."
+msgid "By default, this playbook installs Synapse Admin on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse-admin.md:29
-msgid "Adjusting the playbook configuration"
+msgid "If you wish to adjust it, see the section [below](#adjusting-the-synapse-admin-url-optional) for details about DNS configuration."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse-admin.md:31
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:33
 msgid "To enable Synapse Admin, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:37
+#: ../../../docs/configuring-playbook-synapse-admin.md:39
 msgid "**Note**: Synapse Admin requires Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to function. Access to them is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, for additional security, we normally leave them unexposed, following [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). Because Synapse Admin needs these APIs to function, when installing Synapse Admin, the playbook **automatically** exposes the Synapse Admin API publicly for you. Depending on the homeserver implementation you're using (Synapse, Dendrite), this is equivalent to:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:39
+#: ../../../docs/configuring-playbook-synapse-admin.md:41
 msgid "for [Synapse](./configuring-playbook-synapse.md) (our default homeserver implementation): `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:40
+#: ../../../docs/configuring-playbook-synapse-admin.md:42
 msgid "for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:42
+#: ../../../docs/configuring-playbook-synapse-admin.md:44
 msgid "By default, synapse-admin installation will be [restricted to only work with one homeserver](https://github.com/etkecc/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) — the one managed by the playbook. To adjust these restrictions, tweak the `matrix_synapse_admin_config_restrictBaseUrl` variable."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:44
+#: ../../../docs/configuring-playbook-synapse-admin.md:46
 msgid "Adjusting the Synapse Admin URL (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:46
+#: ../../../docs/configuring-playbook-synapse-admin.md:48
 msgid "By tweaking the `matrix_synapse_admin_hostname` and `matrix_synapse_admin_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:48
+#: ../../../docs/configuring-playbook-synapse-admin.md:50
 msgid "Example additional configuration for your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:56
+#: ../../../docs/configuring-playbook-synapse-admin.md:58
 msgid "If you've changed the default hostname, you may need to create a CNAME record for the Synapse Admin domain (`admin.example.com`), which targets `matrix.example.com`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:58
+#: ../../../docs/configuring-playbook-synapse-admin.md:60
 msgid "When setting, replace `example.com` with your own."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:60
+#: ../../../docs/configuring-playbook-synapse-admin.md:62
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:62
+#: ../../../docs/configuring-playbook-synapse-admin.md:64
 msgid "There are some additional things you may wish to configure about the component."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:64
+#: ../../../docs/configuring-playbook-synapse-admin.md:66
 msgid "Take a look at:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:66
+#: ../../../docs/configuring-playbook-synapse-admin.md:68
 msgid "`roles/custom/matrix-synapse-admin/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_synapse_admin_configuration_extension_json` variable"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:68
+#: ../../../docs/configuring-playbook-synapse-admin.md:70
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:70
+#: ../../../docs/configuring-playbook-synapse-admin.md:72
 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:77
+#: ../../../docs/configuring-playbook-synapse-admin.md:79
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:79
+#: ../../../docs/configuring-playbook-synapse-admin.md:81
 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:81
+#: ../../../docs/configuring-playbook-synapse-admin.md:83
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:83
+#: ../../../docs/configuring-playbook-synapse-admin.md:85
 msgid "After installation, Synapse Admin will be accessible at: `https://matrix.example.com/synapse-admin/`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:85
+#: ../../../docs/configuring-playbook-synapse-admin.md:87
 msgid "To use Synapse Admin, you need to have [registered at least one administrator account](registering-users.md) on your server."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:87
+#: ../../../docs/configuring-playbook-synapse-admin.md:89
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-admin.md:89
+#: ../../../docs/configuring-playbook-synapse-admin.md:91
 msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-synapse-admin`."
 msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:93
+msgid "If you have questions, you can join this community room and feel free to ask: [#synapse-admin:etke.cc](https://matrix.to/#/#synapse-admin:etke.cc)"
+msgstr ""

i18n/translation-templates/docs/configuring-playbook-synapse-auto-accept-invite.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -16,54 +16,18 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
-#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:9
-msgid "Setting up Synapse Auto Invite Accept (optional)"
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:18
+msgid "Setting up Synapse Auto Invite Accept (optional, removed)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:11
-msgid "The playbook can install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) for you."
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:20
+msgid "🪦 The playbook used to be able to install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite), but no longer includes this component, as the same functionality [has been integrated](https://github.com/element-hq/synapse/pull/17147) to Synapse since [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:13
-msgid "In short, it automatically accepts room invites. You can specify that only 1:1 room invites are auto-accepted. Defaults to false if not specified."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:15
-msgid "See the project's [documentation](https://github.com/matrix-org/synapse-auto-accept-invite/blob/main/README.md) to learn what it does and why it might be useful to you."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:17
-msgid "**Note**: Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0), the same feature [has been merged](https://github.com/element-hq/synapse/pull/17147) into Synapse (see the [Native alternative](#native-alternative) section below). You'd better use the native feature, instead of the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) 3rd party module."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:19
-msgid "Adjusting the playbook configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:21
-msgid "If you decide that you'd like to let this playbook install the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite module for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:29
-msgid "Synapse worker deployments"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:31
-msgid "In a [workerized Synapse deployment](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/c9a842147e09647c355799ca024d65a5de66b099/docs/configuring-playbook-synapse.md#load-balancing-with-workers) it is possible to run this module on a worker to reduce the load on the main process (Default is `null`). For example, add this to your configuration:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:37
-msgid "There might be an [issue with federation](https://github.com/matrix-org/synapse-auto-accept-invite/issues/18)."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:39
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:22
 msgid "Native alternative"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:41
-msgid "Since Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0), the functionality provided by the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) 3rd party module [has been made](https://github.com/element-hq/synapse/pull/17147) part of Synapse."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:43
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:24
 msgid "Here's example configuration for using the **native** Synapse feature:"
 msgstr ""

i18n/translation-templates/docs/configuring-playbook-synapse-s3-storage-provider.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -293,9 +293,13 @@ msgid "… triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` t
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:180
-msgid "So… you don't need to perform any maintenance yourself."
+msgid "The same `migrate` script also prunes empty directories in the local media repository (`remote_content` and `remote_thumbnail`) after upload/delete operations."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:182
+msgid "So… you don't need to perform any maintenance yourself."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:184
 msgid "The schedule is defined in the format of systemd timer calendar. To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs):"
 msgstr ""

i18n/translation-templates/docs/configuring-playbook-synapse.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -149,7 +149,7 @@ msgid "When Synapse workers are enabled, the integrated [Postgres database is tu
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse.md:79
-msgid "A separate Ansible role (`matrix-synapse-reverse-proxy-companion`) and component handles load-balancing for workers. This role/component is automatically enabled when you enable workers. Make sure to use the `setup-all` tag (not `install-all`!) during the playbook's [installation](./installing.md) process, especially if you're disabling workers, so that components may be installed/uninstalled correctly."
+msgid "The `matrix-synapse` role also manages the `matrix-synapse-reverse-proxy-companion` component for load-balancing with workers. This component is automatically enabled when you enable workers. Make sure to use the `setup-all` tag (not `install-all`!) during the playbook's [installation](./installing.md) process, especially if you're disabling workers, so that components may be installed/uninstalled correctly."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse.md:81
@@ -157,141 +157,161 @@ msgid "In case any problems occur, make sure to have a look at the [list of syna
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse.md:83
-msgid "Synapse + OpenID Connect for Single-Sign-On"
+msgid "Limit joining heavy rooms on constrained hosts"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse.md:85
-msgid "💡 An alternative to setting up OIDC in Synapse is to use [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS). Newer clients (like Element X) only support SSO-based authentication via MAS and not via the legacy Synapse OIDC setup described below. That said, MAS is still a new experimental service which comes with its own downsides. Consult its documentation to learn if it will be a good fit for your deployment."
+msgid "If your server is underpowered, joining heavy rooms can cause Synapse to consume a lot of resources and be unavailable for long (while it catches up)."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse.md:87
-msgid "If you'd like to use OpenID Connect authentication with Synapse, you'll need some additional configuration."
+msgid "To avoid this, Synapse can be configured to reject joins for remote rooms that are too complex before users enter them."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse.md:89
-msgid "This example configuration is for [keycloak](https://www.keycloak.org/), an opensource Identity Provider maintained by Red Hat."
+msgid "Complexity is computed as `current_state_events / 500` (Synapse state event count for current room state). When the resulting value is higher than `matrix_synapse_limit_remote_rooms_complexity` and `matrix_synapse_limit_remote_rooms_enabled` is `true`, Synapse blocks joining the room."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-synapse.md:91
+msgid "We recommend using this as a guardrail on low-resource servers:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:106
+msgid "Synapse + OpenID Connect for Single-Sign-On"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:108
+msgid "💡 An alternative to setting up OIDC in Synapse is to use [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS). Newer clients (like Element X) only support SSO-based authentication via MAS and not via the legacy Synapse OIDC setup described below. That said, MAS is still a new experimental service which comes with its own downsides. Consult its documentation to learn if it will be a good fit for your deployment."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:110
+msgid "If you'd like to use OpenID Connect authentication with Synapse, you'll need some additional configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:112
+msgid "This example configuration is for [keycloak](https://www.keycloak.org/), an opensource Identity Provider maintained by Red Hat."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:114
 msgid "For more detailed documentation on available options and how to setup keycloak, see the [Synapse documentation on OpenID Connect with keycloak](https://github.com/element-hq/synapse/blob/develop/docs/openid.md#keycloak)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:93
+#: ../../../docs/configuring-playbook-synapse.md:116
 msgid "In case you encounter errors regarding the parsing of the variables, you can try to add `{% raw %}` and `{% endraw %}` blocks around them. For example ;"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:114
+#: ../../../docs/configuring-playbook-synapse.md:137
 msgid "Customizing templates"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:116
+#: ../../../docs/configuring-playbook-synapse.md:139
 msgid "[Templates](https://github.com/element-hq/synapse/blob/develop/docs/templates.md) are used by Synapse for showing **certain web pages** handled by the server, as well as for **email notifications**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:118
+#: ../../../docs/configuring-playbook-synapse.md:141
 msgid "This playbook allows you to customize the default templates (see the [`synapse/res/templates` directory](https://github.com/element-hq/synapse/tree/develop/synapse/res/templates))."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:120
+#: ../../../docs/configuring-playbook-synapse.md:143
 msgid "If template customization is enabled, the playbook will build a custom container image based on the official one."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:122
+#: ../../../docs/configuring-playbook-synapse.md:145
 msgid "Your custom templates need to live in a public or private git repository. This repository will be cloned during Synapse image customization (during the playbook run)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:124
+#: ../../../docs/configuring-playbook-synapse.md:147
 msgid "To enable template customizations, add the following configuration to your `vars.yml` file (adapt to your needs):"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:150
+#: ../../../docs/configuring-playbook-synapse.md:173
 msgid "As mentioned in Synapse's Templates documentation, Synapse will fall back to its own templates if a template is not found in that directory. Due to this, it's recommended to only store and maintain template files in your repository if you need to make custom changes. Other files (which you don't need to change), should not be duplicated, so that you don't need to worry about getting out-of-sync with the original Synapse templates."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:152
+#: ../../../docs/configuring-playbook-synapse.md:175
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:154
+#: ../../../docs/configuring-playbook-synapse.md:177
 msgid "There are some additional things you may wish to configure about the server."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:156
+#: ../../../docs/configuring-playbook-synapse.md:179
 msgid "Take a look at:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:158
+#: ../../../docs/configuring-playbook-synapse.md:181
 msgid "`roles/custom/matrix-synapse/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:159
+#: ../../../docs/configuring-playbook-synapse.md:182
 msgid "`roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2` for the server's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_synapse_configuration_extension_yaml` variable"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:161
+#: ../../../docs/configuring-playbook-synapse.md:184
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:163
+#: ../../../docs/configuring-playbook-synapse.md:186
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:170
+#: ../../../docs/configuring-playbook-synapse.md:193
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:172
+#: ../../../docs/configuring-playbook-synapse.md:195
 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:174
+#: ../../../docs/configuring-playbook-synapse.md:197
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:176
+#: ../../../docs/configuring-playbook-synapse.md:199
 msgid "Synapse Admin"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:178
+#: ../../../docs/configuring-playbook-synapse.md:201
 msgid "With [Synapse Admin](configuring-playbook-synapse-admin.md), certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:180
+#: ../../../docs/configuring-playbook-synapse.md:203
 msgid "The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:182
+#: ../../../docs/configuring-playbook-synapse.md:205
 msgid "Monitoring Synapse Metrics with Prometheus and Grafana"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:184
+#: ../../../docs/configuring-playbook-synapse.md:207
 msgid "This playbook allows you to enable Synapse metrics, which can provide insight into the performance and activity of Synapse."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:186
+#: ../../../docs/configuring-playbook-synapse.md:209
 msgid "To enable Synapse runtime metrics, see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md) and [its subsection](configuring-playbook-prometheus-grafana.md#expose-metrics-of-other-services-roles)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:188
+#: ../../../docs/configuring-playbook-synapse.md:211
 msgid "To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:190
+#: ../../../docs/configuring-playbook-synapse.md:213
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:192
+#: ../../../docs/configuring-playbook-synapse.md:215
 msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-synapse`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:194
+#: ../../../docs/configuring-playbook-synapse.md:217
 msgid "Increase logging verbosity"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:196
+#: ../../../docs/configuring-playbook-synapse.md:219
 msgid "Because Synapse is originally very chatty when it comes to logging, we intentionally reduce its [logging level](https://docs.python.org/3/library/logging.html#logging-levels) from `INFO` to `WARNING`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:198
+#: ../../../docs/configuring-playbook-synapse.md:221
 msgid "If you'd like to debug an issue or [report a Synapse bug](https://github.com/element-hq/synapse/issues/new/choose) to the developers, it'd be better if you temporarily increase the logging verbosity to `INFO`. To do so, add the following configuration to your `vars.yml` file and re-run the playbook:"
 msgstr ""

i18n/translation-templates/docs/configuring-playbook-turn.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -21,173 +21,213 @@ msgid "Configuring a TURN server (optional, advanced)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-turn.md:16
-msgid "By default, this playbook installs and configures the [coturn](https://github.com/coturn/coturn) as a TURN server, through which clients can make audio/video calls even from [NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed networks. It also configures the Synapse chat server by default, so that it points to the coturn TURN server installed by the playbook. If that's okay, you can skip this document."
+msgid "By default, the [coturn](https://github.com/coturn/coturn) TURN server component is enabled automatically only when [Jitsi](configuring-playbook-jitsi.md) is enabled. If you're not using Jitsi, coturn is not enabled by default."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-turn.md:18
-msgid "If you'd like to stop the playbook installing the server, see the section [below](#disabling-coturn) to check the configuration for disabling it."
+msgid "If you explicitly need coturn while not using Jitsi, enable it with:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:20
-msgid "Adjusting the playbook configuration"
+#: ../../../docs/configuring-playbook-turn.md:24
+msgid "and configure its IP-related settings in the section below."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:22
-msgid "Define public IP manually (optional)"
+#: ../../../docs/configuring-playbook-turn.md:26
+msgid "If you'd like coturn to stay disabled even when Jitsi is enabled, or if you prefer to use an external TURN provider, see [disabling coturn](#disabling-coturn) section below."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:24
-msgid "In the `hosts` file we explicitly ask for your server's external IP address when defining `ansible_host`, because the same value is used for configuring coturn."
+#: ../../../docs/configuring-playbook-turn.md:28
+msgid "When Coturn is not enabled, homeservers (like Synapse) would not point to TURN servers and *legacy* audio/video call functionality may fail. If you're using [Matrix RTC](configuring-playbook-matrix-rtc.md) (for [Element Call](configuring-playbook-element-call.md)), you likely don't have a need to enable coturn."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:26
-msgid "If you'd rather use a local IP for `ansible_host`, add the following configuration to your `vars.yml` file. Make sure to replace `YOUR_PUBLIC_IP` with the pubic IP used by the server."
+#: ../../../docs/configuring-playbook-turn.md:30
+msgid "Adjusting firewall rules"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-turn.md:32
-msgid "If you'd like to rely on external IP address auto-detection (not recommended unless you need it), set an empty value to the variable. The playbook will automatically contact an [echoip](https://github.com/mpolden/echoip)-compatible service (`https://ifconfig.co/json` by default) to determine your server's IP address. This API endpoint is configurable via the `coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable."
+msgid "To ensure Coturn functions correctly, the following firewall rules and port forwarding settings are required when coturn is enabled:"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-turn.md:34
-msgid "[!NOTE] You can self-host the echoip service by using the [Mother-of-All-Self-Hosting (MASH)](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook. See [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/echoip.md) for the instruction to install it with the playbook. If you are wondering how to use it for your Matrix server, refer to [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/setting-up-services-on-mdad-server.md) for the overview."
+msgid "`3478/tcp`: STUN/TURN over TCP"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:35
+msgid "`3478/udp`: STUN/TURN over UDP"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:36
+msgid "`5349/tcp`: TURN over TCP"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-turn.md:37
-msgid "If your server has multiple external IP addresses, the coturn role offers a different variable for specifying them:"
+msgid "`5349/udp`: TURN over UDP"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:38
+msgid "`49152-49172/udp`: TURN/UDP relay range"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:40
+msgid "If LiveKit's embedded TURN is enabled at the same time (for MatrixRTC/Element Call), keep the Coturn relay range distinct from LiveKit's relay range (`livekit_server_config_turn_relay_range_start`/`livekit_server_config_turn_relay_range_end`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:42
+msgid "💡 Docker configures the server's internal firewall for you. In most cases, you don't need to do anything special on the host itself."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-turn.md:44
-msgid "Change the authentication mechanism (optional)"
+msgid "Adjusting the playbook configuration"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-turn.md:46
-msgid "The playbook uses the [`auth-secret` authentication method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L186-L199) by default, but you may switch to the [`lt-cred-mech` method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L178) which [some report](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3191) to be working better."
+msgid "Define public IP manually (optional)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-turn.md:48
+msgid "If you enable coturn (either via Jitsi or manually), we recommend that you configure the public IP addresses of your server in the `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:55
+msgid "If you'd like to rely on external IP address auto-detection (not recommended unless you need it), avoid configuring this variable. The playbook will automatically contact an [echoip](https://github.com/mpolden/echoip)-compatible service (`https://ifconfig.co/json` by default) to determine your server's IP address. This API endpoint is configurable via the `coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:57
+msgid "[!NOTE] You can self-host the echoip service by using the [Mother-of-All-Self-Hosting (MASH)](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook. See [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/echoip.md) for the instruction to install it with the playbook. If you are wondering how to use it for your Matrix server, refer to [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/setting-up-services-on-mdad-server.md) for the overview."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:60
+msgid "Change the authentication mechanism (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:62
+msgid "The playbook uses the [`auth-secret` authentication method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L186-L199) by default, but you may switch to the [`lt-cred-mech` method](https://github.com/coturn/coturn/blob/873cabd6a2e5edd7e9cc5662cac3ffe47fe87a8e/README.turnserver#L178) which [some report](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3191) to be working better."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:64
 msgid "To do so, add the following configuration to your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:54
+#: ../../../docs/configuring-playbook-turn.md:70
 msgid "Regardless of the selected authentication method, the playbook generates secrets automatically and passes them to the homeserver and coturn."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:56
+#: ../../../docs/configuring-playbook-turn.md:72
 msgid "If [Jitsi](configuring-playbook-jitsi.md) is installed, note that switching to `lt-cred-mech` will disable the integration between Jitsi and your coturn server, as Jitsi seems to support the `auth-secret` authentication method only."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:58
+#: ../../../docs/configuring-playbook-turn.md:74
 msgid "Customize the Coturn hostname (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:60
+#: ../../../docs/configuring-playbook-turn.md:76
 msgid "By default, Coturn uses the same hostname as your Matrix homeserver (the value of `matrix_server_fqn_matrix`, which is typically `matrix.example.com`)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:62
+#: ../../../docs/configuring-playbook-turn.md:78
 msgid "If you'd like to use a custom subdomain for Coturn (e.g., `turn.example.com` or `t.matrix.example.com`), add the following configuration to your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:68
+#: ../../../docs/configuring-playbook-turn.md:84
 msgid "The playbook will automatically:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:69
+#: ../../../docs/configuring-playbook-turn.md:85
 msgid "Configure Coturn to use this hostname"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:70
+#: ../../../docs/configuring-playbook-turn.md:86
 msgid "Obtain an SSL certificate for the custom domain via Traefik"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:71
+#: ../../../docs/configuring-playbook-turn.md:87
 msgid "Update all TURN URIs to point to the custom domain"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:73
+#: ../../../docs/configuring-playbook-turn.md:89
 msgid "**Note**: Make sure the custom hostname resolves to your server's IP address via DNS before running the playbook."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:75
+#: ../../../docs/configuring-playbook-turn.md:91
 msgid "Use your own external coturn server (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:77
+#: ../../../docs/configuring-playbook-turn.md:93
 msgid "If you'd like to use another TURN server (be it coturn or some other one), add the following configuration to your `vars.yml` file. Make sure to replace `HOSTNAME_OR_IP` with your own."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:91
+#: ../../../docs/configuring-playbook-turn.md:107
 msgid "If you have or want to enable Jitsi, you might want to enable the TURN server there too. If you do not do it, Jitsi will fall back to an upstream service."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:98
+#: ../../../docs/configuring-playbook-turn.md:114
 msgid "You can put multiple host/port combinations if you'd like to."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:100
+#: ../../../docs/configuring-playbook-turn.md:116
 msgid "Edit the reloading schedule (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:102
+#: ../../../docs/configuring-playbook-turn.md:118
 msgid "By default the service is reloaded on 6:30 a.m. every day based on the `coturn_reload_schedule` variable so that new SSL certificates can kick in. It is defined in the format of systemd timer calendar."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:104
+#: ../../../docs/configuring-playbook-turn.md:120
 msgid "To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs):"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:110
+#: ../../../docs/configuring-playbook-turn.md:126
 msgid "**Note**: the actual job may run with a delay. See `coturn_reload_schedule_randomized_delay_sec` for its default value."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:112
+#: ../../../docs/configuring-playbook-turn.md:128
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:114
+#: ../../../docs/configuring-playbook-turn.md:130
 msgid "There are some additional things you may wish to configure about the TURN server."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:116
+#: ../../../docs/configuring-playbook-turn.md:132
 msgid "Take a look at:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:118
+#: ../../../docs/configuring-playbook-turn.md:134
 msgid "`roles/galaxy/coturn/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:120
+#: ../../../docs/configuring-playbook-turn.md:136
 msgid "Disabling coturn"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:122
-msgid "If, for some reason, you'd like for the playbook to not install coturn (or to uninstall it if it was previously installed), add the following configuration to your `vars.yml` file:"
+#: ../../../docs/configuring-playbook-turn.md:138
+msgid "Coturn is only enabled by default when [Jitsi](configuring-playbook-jitsi.md) is enabled. In most instances, you don't need to explicitly disable it."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:128
-msgid "In that case, Synapse would not point to any coturn servers and audio/video call functionality may fail."
+#: ../../../docs/configuring-playbook-turn.md:140
+msgid "To force the playbook to not install Coturn (even when Jitsi is enabled), add the following configuration to your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:130
+#: ../../../docs/configuring-playbook-turn.md:146
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:132
+#: ../../../docs/configuring-playbook-turn.md:148
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:139
+#: ../../../docs/configuring-playbook-turn.md:155
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:141
+#: ../../../docs/configuring-playbook-turn.md:157
 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:143
+#: ../../../docs/configuring-playbook-turn.md:159
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-turn.md:145
+#: ../../../docs/configuring-playbook-turn.md:161
 msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-coturn`."
 msgstr ""

i18n/translation-templates/docs/configuring-playbook.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -169,155 +169,155 @@ msgid "[Setting up Cinny](configuring-playbook-client-cinny.md), if you've enabl
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:90
-msgid "[Setting up SchildiChat Web](configuring-playbook-client-schildichat-web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a web client based on [Element Web](https://element.io/) with some extras and tweaks"
+msgid "[Setting up Sable](configuring-playbook-client-sable.md), if you've enabled [Sable](https://github.com/7w1/sable), a web client focusing primarily on simple, elegant and secure interface"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:92
-msgid "[Setting up FluffyChat Web](configuring-playbook-client-fluffychat-web.md), if you've enabled [FluffyChat Web](https://github.com/krille-chan/fluffychat), a cute cross-platform messenger (web, iOS, Android) for Matrix written in [Flutter](https://flutter.dev/)"
+msgid "[Setting up SchildiChat Web](configuring-playbook-client-schildichat-web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a web client based on [Element Web](https://element.io/) with some extras and tweaks"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:95
-msgid "Authentication and user-related"
+#: ../../../docs/configuring-playbook.md:94
+msgid "[Setting up FluffyChat Web](configuring-playbook-client-fluffychat-web.md), if you've enabled [FluffyChat Web](https://github.com/krille-chan/fluffychat), a cute cross-platform messenger (web, iOS, Android) for Matrix written in [Flutter](https://flutter.dev/)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:97
-msgid "Extend and modify how users are authenticated on your homeserver."
+msgid "Authentication and user-related"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:99
-msgid "[Setting up Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (Next-generation auth for Matrix, based on OAuth 2.0/OIDC)"
+msgid "Extend and modify how users are authenticated on your homeserver."
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:101
-msgid "[Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)"
+msgid "[Setting up Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (Next-generation auth for Matrix, based on OAuth 2.0/OIDC)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:103
-msgid "[Setting up Synapse Admin](configuring-playbook-synapse-admin.md)"
+msgid "[Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:105
-msgid "[Setting up matrix-registration](configuring-playbook-matrix-registration.md)"
+msgid "[Setting up Synapse Admin](configuring-playbook-synapse-admin.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:107
-msgid "[Setting up the REST authentication password provider module](configuring-playbook-rest-auth.md) (advanced)"
+msgid "[Setting up matrix-registration](configuring-playbook-matrix-registration.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:109
-msgid "[Setting up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) (advanced)"
+msgid "[Setting up the REST authentication password provider module](configuring-playbook-rest-auth.md) (advanced)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:111
-msgid "[Setting up the LDAP authentication password provider module](configuring-playbook-ldap-auth.md) (advanced)"
+msgid "[Setting up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) (advanced)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:113
-msgid "[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) (advanced)"
+msgid "[Setting up the LDAP authentication password provider module](configuring-playbook-ldap-auth.md) (advanced)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:115
-msgid "[Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)"
+msgid "[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) (advanced)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:117
-msgid "[Setting up Matrix User Verification Service](configuring-playbook-user-verification-service.md) (advanced)"
+msgid "[Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:119
-msgid "File Storage"
+msgid "[Setting up Matrix User Verification Service](configuring-playbook-user-verification-service.md) (advanced)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:121
-msgid "Use alternative file storage to the default `media_store` folder."
+msgid "File Storage"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:123
-msgid "[Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
+msgid "Use alternative file storage to the default `media_store` folder."
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:125
-msgid "[Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md)"
+msgid "[Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:127
-msgid "[Storing Synapse media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)"
+msgid "[Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:129
-msgid "[Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md)"
+msgid "[Storing Synapse media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:131
-msgid "Bridging other networks"
+msgid "[Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:133
-msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
+msgid "Bridging other networks"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:135
-msgid "[Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) — a common guide for configuring mautrix bridges"
+msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:137
-msgid "[Setting up Mautrix Bluesky bridging](configuring-playbook-bridge-mautrix-bluesky.md)"
+msgid "[Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) — a common guide for configuring mautrix bridges"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:139
-msgid "[Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md)"
+msgid "[Setting up Mautrix Bluesky bridging](configuring-playbook-bridge-mautrix-bluesky.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:141
-msgid "[Setting up Mautrix Telegram bridging](configuring-playbook-bridge-mautrix-telegram.md)"
+msgid "[Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:143
-msgid "[Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md)"
+msgid "[Setting up Mautrix Telegram bridging](configuring-playbook-bridge-mautrix-telegram.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:145
-msgid "[Setting up Mautrix Google Messages bridging](configuring-playbook-bridge-mautrix-gmessages.md)"
+msgid "[Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:147
-msgid "[Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-mautrix-whatsapp.md)"
+msgid "[Setting up Mautrix Google Messages bridging](configuring-playbook-bridge-mautrix-gmessages.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:149
-msgid "[Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)"
+msgid "[Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-mautrix-whatsapp.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:151
-msgid "[Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)"
+msgid "[Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:153
-msgid "[Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-mautrix-googlechat.md)"
+msgid "[Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:155
-msgid "[Setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md)"
+msgid "[Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-mautrix-googlechat.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:157
-msgid "[Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-signal.md)"
+msgid "[Setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:159
-msgid "[Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](configuring-playbook-bridge-mautrix-wsproxy.md)"
+msgid "[Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-signal.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:161
-msgid "[Setting up Appservice IRC bridging](configuring-playbook-bridge-appservice-irc.md)"
+msgid "[Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](configuring-playbook-bridge-mautrix-wsproxy.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:163
-msgid "[Setting up Appservice Discord bridging](configuring-playbook-bridge-appservice-discord.md)"
+msgid "[Setting up Appservice IRC bridging](configuring-playbook-bridge-appservice-irc.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:165
-msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md)"
+msgid "[Setting up Appservice Discord bridging](configuring-playbook-bridge-appservice-discord.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:167
@@ -465,59 +465,59 @@ msgid "[Setting up Matrix RTC](configuring-playbook-matrix-rtc.md) (optional)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:238
-msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md)"
+msgid "[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:240
-msgid "[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers"
+msgid "[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:242
-msgid "[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)"
+msgid "[Setting up Matrix.to](configuring-playbook-matrixto.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:244
-msgid "[Setting up Matrix.to](configuring-playbook-matrixto.md)"
+msgid "[Setting up Etherpad](configuring-playbook-etherpad.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:246
-msgid "[Setting up Etherpad](configuring-playbook-etherpad.md)"
+msgid "[Setting up the Jitsi video-conferencing platform](configuring-playbook-jitsi.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:248
-msgid "[Setting up the Jitsi video-conferencing platform](configuring-playbook-jitsi.md)"
+msgid "[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) — a federated comment system built on Matrix"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:250
-msgid "[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) — a federated comment system built on Matrix"
+msgid "[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-pantalaimon.md) (advanced)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:252
-msgid "[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-pantalaimon.md) (advanced)"
+msgid "[Setting up the Sygnal push gateway](configuring-playbook-sygnal.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:254
-msgid "[Setting up the Sygnal push gateway](configuring-playbook-sygnal.md)"
+msgid "[Setting up the ntfy push notifications server](configuring-playbook-ntfy.md)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:256
-msgid "[Setting up the ntfy push notifications server](configuring-playbook-ntfy.md)"
+msgid "Deprecated / unmaintained / removed services"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:258
-msgid "Deprecated / unmaintained / removed services"
+msgid "**Note**: since a deprecated or unmaintained service will not be updated, its bug or vulnerability will be unlikely to get patched. It is recommended to migrate from the service to an alternative if any, and make sure to do your own research before you decide to keep it running nonetheless."
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:260
-msgid "**Note**: since a deprecated or unmaintained service will not be updated, its bug or vulnerability will be unlikely to get patched. It is recommended to migrate from the service to an alternative if any, and make sure to do your own research before you decide to keep it running nonetheless."
+msgid "[Configuring conduwuit](configuring-playbook-conduwuit.md) (removed; this component has been abandoned and unmaintained)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:262
-msgid "[Configuring conduwuit](configuring-playbook-conduwuit.md) (removed; this component has been abandoned and unmaintained)"
+msgid "[Setting up the Sliding Sync proxy](configuring-playbook-sliding-sync-proxy.md) for clients which require Sliding Sync support (like old Element X versions, before it got switched to Simplified Sliding Sync)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:264
-msgid "[Setting up the Sliding Sync proxy](configuring-playbook-sliding-sync-proxy.md) for clients which require Sliding Sync support (like old Element X versions, before it got switched to Simplified Sliding Sync)"
+msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md) (removed; this component has been discontinued)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook.md:266
@@ -575,3 +575,7 @@ msgstr ""
 #: ../../../docs/configuring-playbook.md:292
 msgid "[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md))"
 msgstr ""
+
+#: ../../../docs/configuring-playbook.md:294
+msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md) (removed; since Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0) the same feature is available natively.)"
+msgstr ""

i18n/translation-templates/docs/container-images.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -148,6 +148,14 @@ msgstr ""
 msgid "Simple, elegant and secure web client"
 msgstr ""
 
+#: ../../../docs/container-images.md:0
+msgid "[Sable](configuring-playbook-client-sable.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[7w1/sable](https://ghcr.io/7w1/sable)"
+msgstr ""
+
 #: ../../../docs/container-images.md:0
 msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md)"
 msgstr ""
@@ -160,11 +168,11 @@ msgstr ""
 msgid "Based on Element Web, with a more traditional instant messaging experience"
 msgstr ""
 
-#: ../../../docs/container-images.md:44
+#: ../../../docs/container-images.md:45
 msgid "Server Components"
 msgstr ""
 
-#: ../../../docs/container-images.md:46
+#: ../../../docs/container-images.md:47
 msgid "Services that run on the server to make the various parts of your installation work."
 msgstr ""
 
@@ -264,11 +272,11 @@ msgstr ""
 msgid "JWT service for integrating [Element Call](./configuring-playbook-element-call.md) with [LiveKit Server](./configuring-playbook-livekit-server.md)"
 msgstr ""
 
-#: ../../../docs/container-images.md:59
+#: ../../../docs/container-images.md:60
 msgid "Authentication"
 msgstr ""
 
-#: ../../../docs/container-images.md:61
+#: ../../../docs/container-images.md:62
 msgid "Extend and modify how users are authenticated on your homeserver."
 msgstr ""
 
@@ -344,11 +352,11 @@ msgstr ""
 msgid "Spam checker module"
 msgstr ""
 
-#: ../../../docs/container-images.md:73
+#: ../../../docs/container-images.md:74
 msgid "File Storage"
 msgstr ""
 
-#: ../../../docs/container-images.md:75
+#: ../../../docs/container-images.md:76
 msgid "Use alternative file storage to the default `media_store` folder."
 msgstr ""
 
@@ -380,11 +388,11 @@ msgstr ""
 msgid "Highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
 msgstr ""
 
-#: ../../../docs/container-images.md:83
+#: ../../../docs/container-images.md:84
 msgid "Bridges"
 msgstr ""
 
-#: ../../../docs/container-images.md:85
+#: ../../../docs/container-images.md:86
 msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
 msgstr ""
 
@@ -568,14 +576,6 @@ msgstr ""
 msgid "Bridge to [Discord](https://discordapp.com/)"
 msgstr ""
 
-#: ../../../docs/container-images.md:0
-msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md:0
-msgid "[matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)"
-msgstr ""
-
 #: ../../../docs/container-images.md:0
 msgid "[matrix-hookshot](configuring-playbook-bridge-hookshot.md)"
 msgstr ""
@@ -908,14 +908,6 @@ msgstr ""
 msgid "Various services that don't fit any other categories."
 msgstr ""
 
-#: ../../../docs/container-images.md:0
-msgid "[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md:0
-msgid "Synapse module to automatically accept invites"
-msgstr ""
-
 #: ../../../docs/container-images.md:0
 msgid "[synapse_auto_compressor](configuring-playbook-synapse-auto-compressor.md)"
 msgstr ""
@@ -1052,11 +1044,11 @@ msgstr ""
 msgid "A native Matrix video conferencing application"
 msgstr ""
 
-#: ../../../docs/container-images.md:168
+#: ../../../docs/container-images.md:167
 msgid "Container images of deprecated / unmaintained services"
 msgstr ""
 
-#: ../../../docs/container-images.md:170
+#: ../../../docs/container-images.md:169
 msgid "The list of the deprecated or unmaintained services is available [here](configuring-playbook.md#deprecated--unmaintained--removed-services)."
 msgstr ""
 
@@ -1120,6 +1112,14 @@ msgstr ""
 msgid "Matrix Identity Server"
 msgstr ""
 
+#: ../../../docs/container-images.md:0
+msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)"
+msgstr ""
+
 #: ../../../docs/container-images.md:0
 msgid "[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md)"
 msgstr ""
@@ -1223,3 +1223,11 @@ msgstr ""
 #: ../../../docs/container-images.md:0
 msgid "Sliding Sync support for clients which require it (like old Element X versions, before it got switched to Simplified Sliding Sync)"
 msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Synapse module to automatically accept invites"
+msgstr ""

i18n/translation-templates/docs/faq.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -573,254 +573,266 @@ msgid "How do I optimize this setup for a low-power server?"
 msgstr ""
 
 #: ../../../docs/faq.md:308
-msgid "You can disable some not-so-important services to save on memory."
+msgid "For a low-power server, it's best to use an alternative homeserver implementation (other than [Synapse](configuring-playbook-synapse.md))."
 msgstr ""
 
-#: ../../../docs/faq.md:327
-msgid "You can also consider implementing a restriction on room complexity, in order to prevent users from joining very heavy rooms:"
+#: ../../../docs/faq.md:310
+msgid "You can disable some not-so-important services to save on memory."
 msgstr ""
 
-#: ../../../docs/faq.md:337
+#: ../../../docs/faq.md:317
 msgid "If you've installed [Jitsi](configuring-playbook-jitsi.md) (not installed by default), there are additional optimizations listed on its documentation page that you can perform."
 msgstr ""
 
-#: ../../../docs/faq.md:339
+#: ../../../docs/faq.md:320
+msgid "Synapse-specific optimizations"
+msgstr ""
+
+#: ../../../docs/faq.md:322
+msgid "If you're using [Synapse](configuring-playbook-synapse.md), you can also consider the following optimizations:"
+msgstr ""
+
+#: ../../../docs/faq.md:332
+msgid "You can also consider [implementing a restriction on room complexity](configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts), in order to prevent users from joining very heavy rooms:"
+msgstr ""
+
+#: ../../../docs/faq.md:340
 msgid "I already have Docker on my server. Can you stop installing Docker via the playbook?"
 msgstr ""
 
-#: ../../../docs/faq.md:341
+#: ../../../docs/faq.md:342
 msgid "Yes, we can stop installing Docker ourselves. Just use this in your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/faq.md:347
+#: ../../../docs/faq.md:348
 msgid "I run another webserver on the same server where I wish to install Matrix. What now?"
 msgstr ""
 
-#: ../../../docs/faq.md:349
+#: ../../../docs/faq.md:350
 msgid "By default, we install a webserver for you ([Traefik](https://doc.traefik.io/traefik/)), but you can also use [your own webserver](configuring-playbook-own-webserver.md)."
 msgstr ""
 
-#: ../../../docs/faq.md:351
+#: ../../../docs/faq.md:352
 msgid "How is the effective configuration determined?"
 msgstr ""
 
-#: ../../../docs/faq.md:353
+#: ../../../docs/faq.md:354
 msgid "Configuration variables are defined in multiple places in this playbook and are considered in this order:"
 msgstr ""
 
-#: ../../../docs/faq.md:355
+#: ../../../docs/faq.md:356
 msgid "there are defaults coming from each role's defaults file (`role/matrix*/defaults/main.yml`). These variable values aim to be good defaults for when the role is used standalone (outside of this collection of roles, also called playbook)."
 msgstr ""
 
-#: ../../../docs/faq.md:357
+#: ../../../docs/faq.md:358
 msgid "then, there are overrides in `group_vars/matrix_servers`, which aim to adjust these \"standalone role defaults\" to something which better fits the playbook in its entirety."
 msgstr ""
 
-#: ../../../docs/faq.md:359
+#: ../../../docs/faq.md:360
 msgid "finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` file, which is the ultimate override"
 msgstr ""
 
-#: ../../../docs/faq.md:361
+#: ../../../docs/faq.md:362
 msgid "What configuration variables are available?"
 msgstr ""
 
-#: ../../../docs/faq.md:363
+#: ../../../docs/faq.md:364
 msgid "You can discover the variables you can override in each role (`roles/*/*/defaults/main.yml`)."
 msgstr ""
 
-#: ../../../docs/faq.md:365
+#: ../../../docs/faq.md:366
 msgid "As described in [How is the effective configuration determined?](#how-is-the-effective-configuration-determined), these role-defaults may be overridden by values defined in `group_vars/matrix_servers`."
 msgstr ""
 
-#: ../../../docs/faq.md:367
+#: ../../../docs/faq.md:368
 msgid "Refer to both of these for inspiration. Still, as mentioned in [Configuring the playbook](configuring-playbook.md), you're only ever supposed to edit your own `inventory/host_vars/matrix.example.com/vars.yml` file and nothing else inside the playbook (unless you're meaning to contribute new features)."
 msgstr ""
 
-#: ../../../docs/faq.md:369
-#: ../../../docs/faq.md:381
+#: ../../../docs/faq.md:370
+#: ../../../docs/faq.md:382
 msgid "**Note**: some of the roles (`roles/galaxy/*`) live in separate repositories and are only installed after your run `just roles` (or `make roles`) or `just update` (which automatically does `git pull` and `just roles`)."
 msgstr ""
 
-#: ../../../docs/faq.md:371
+#: ../../../docs/faq.md:372
 msgid "I'd like to adjust some configuration which doesn't have a corresponding variable. How do I do it?"
 msgstr ""
 
-#: ../../../docs/faq.md:373
+#: ../../../docs/faq.md:374
 msgid "The playbook doesn't aim to expose all configuration settings for all services using variables. Doing so would amount to hundreds of variables that we have to create and maintain."
 msgstr ""
 
-#: ../../../docs/faq.md:375
+#: ../../../docs/faq.md:376
 msgid "Instead, we only try to make some important basics configurable using dedicated variables you can see in each role. See [What configuration variables are available?](#what-configuration-variables-are-available)."
 msgstr ""
 
-#: ../../../docs/faq.md:377
+#: ../../../docs/faq.md:378
 msgid "Besides that, each role (component) aims to provide a `matrix_SOME_COMPONENT_configuration_extension_yaml` (or `matrix_SOME_COMPONENT_configuration_extension_json`) variable, which can be used to override the configuration."
 msgstr ""
 
-#: ../../../docs/faq.md:379
+#: ../../../docs/faq.md:380
 msgid "Check each role's `roles/*/*/defaults/main.yml` for the corresponding variable and an example for how use it."
 msgstr ""
 
-#: ../../../docs/faq.md:383
+#: ../../../docs/faq.md:384
 msgid "Installation"
 msgstr ""
 
-#: ../../../docs/faq.md:385
+#: ../../../docs/faq.md:386
 msgid "How do I run the installation?"
 msgstr ""
 
-#: ../../../docs/faq.md:387
+#: ../../../docs/faq.md:388
 msgid "See [Installing](installing.md) to learn how to use Ansible to install Matrix services."
 msgstr ""
 
-#: ../../../docs/faq.md:389
+#: ../../../docs/faq.md:390
 msgid "However, we recommend you to follow our installation guide, instead of jumping straight to installing."
 msgstr ""
 
-#: ../../../docs/faq.md:391
+#: ../../../docs/faq.md:392
 msgid "There are two guides available:"
 msgstr ""
 
-#: ../../../docs/faq.md:393
+#: ../../../docs/faq.md:394
 msgid "⚡ **[Quick start](quick-start.md)** (for beginners): this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"."
 msgstr ""
 
-#: ../../../docs/faq.md:395
+#: ../../../docs/faq.md:396
 msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide by starting with the **[Prerequisites](prerequisites.md)** documentation page."
 msgstr ""
 
-#: ../../../docs/faq.md:397
+#: ../../../docs/faq.md:398
 msgid "I installed Synapse some other way. Can I migrate such a setup to the playbook?"
 msgstr ""
 
-#: ../../../docs/faq.md:399
+#: ../../../docs/faq.md:400
 msgid "Yes, you can."
 msgstr ""
 
-#: ../../../docs/faq.md:401
+#: ../../../docs/faq.md:402
 msgid "You generally need to do a playbook installation. It's recommended to follow the full installation guide (starting at the [Prerequisites](prerequisites.md) page), not the [Quick start](quick-start.md) guide. The full installation guide will tell you when it's time to import your existing data into the newly-prepared server."
 msgstr ""
 
-#: ../../../docs/faq.md:403
+#: ../../../docs/faq.md:404
 msgid "This Ansible playbook guides you into installing a server for `example.com` (user IDs are like this: `@alice:example.com`), while the server is at `matrix.example.com`. If your existing setup has a server name (`server_name` configuration setting in Synapse's `homeserver.yaml` file) other than the base `example.com`, you may need to tweak some additional variables. This FAQ entry may be of use if you're dealing with a more complicated setup — [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)"
 msgstr ""
 
-#: ../../../docs/faq.md:405
+#: ../../../docs/faq.md:406
 msgid "After configuring the playbook and installing and **before starting** services (done with `ansible-playbook … --tags=start`) you'd import [your SQLite](importing-synapse-sqlite.md) (or [Postgres](importing-postgres.md)) database and also [import your media store](importing-synapse-media-store.md)."
 msgstr ""
 
-#: ../../../docs/faq.md:407
+#: ../../../docs/faq.md:408
 msgid "I've downloaded Ansible and the playbook on the server. It can't connect using SSH."
 msgstr ""
 
-#: ../../../docs/faq.md:409
+#: ../../../docs/faq.md:410
 msgid "If you're using the playbook directly on the server, then Ansible doesn't need to connect using SSH."
 msgstr ""
 
-#: ../../../docs/faq.md:411
+#: ../../../docs/faq.md:412
 msgid "It can perform a local connection instead. Just set `ansible_connection=local` at the end of the server line in `inventory/hosts` and re-run the playbook."
 msgstr ""
 
-#: ../../../docs/faq.md:413
+#: ../../../docs/faq.md:414
 msgid "If you're running Ansible from within a container (one of the possibilities we list on our [dedicated Ansible documentation page](ansible.md)), then using `ansible_connection=local` is not possible."
 msgstr ""
 
-#: ../../../docs/faq.md:415
+#: ../../../docs/faq.md:416
 msgid "Maintenance and Troubleshooting"
 msgstr ""
 
-#: ../../../docs/faq.md:417
+#: ../../../docs/faq.md:418
 msgid "💡 Also see this page for generic information about maintaining the services and troubleshooting: [Maintenance and Troubleshooting](maintenance-and-troubleshooting.md)"
 msgstr ""
 
-#: ../../../docs/faq.md:419
+#: ../../../docs/faq.md:420
 msgid "Do I need to do anything to keep my Matrix server updated?"
 msgstr ""
 
-#: ../../../docs/faq.md:421
+#: ../../../docs/faq.md:422
 msgid "Yes. We don't update anything for you automatically."
 msgstr ""
 
-#: ../../../docs/faq.md:423
+#: ../../../docs/faq.md:424
 msgid "See our [documentation page about upgrading services](maintenance-upgrading-services.md)."
 msgstr ""
 
-#: ../../../docs/faq.md:425
+#: ../../../docs/faq.md:426
 msgid "How do I move my existing installation to another (VM) server?"
 msgstr ""
 
-#: ../../../docs/faq.md:427
+#: ../../../docs/faq.md:428
 msgid "If you have an existing installation done using this Ansible playbook, you can easily migrate that to another server following [our dedicated server migration guide](maintenance-migrating.md)."
 msgstr ""
 
-#: ../../../docs/faq.md:429
+#: ../../../docs/faq.md:430
 msgid "If your previous installation is done in some other way (not using this Ansible playbook), see [I installed Synapse some other way. Can I migrate such a setup to the playbook?](#i-installed-synapse-some-other-way-can-i-migrate-such-a-setup-to-the-playbook)."
 msgstr ""
 
-#: ../../../docs/faq.md:431
+#: ../../../docs/faq.md:432
 msgid "What is this `/matrix/postgres/data-auto-upgrade-backup` directory that is taking up so much space?"
 msgstr ""
 
-#: ../../../docs/faq.md:433
+#: ../../../docs/faq.md:434
 msgid "When you [perform a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql), we save the the old data files in `/matrix/postgres/data-auto-upgrade-backup`, just so you could easily restore them should something have gone wrong."
 msgstr ""
 
-#: ../../../docs/faq.md:435
+#: ../../../docs/faq.md:436
 msgid "After verifying that everything still works after the Postgres upgrade, you can safely delete `/matrix/postgres/data-auto-upgrade-backup`"
 msgstr ""
 
-#: ../../../docs/faq.md:437
+#: ../../../docs/faq.md:438
 msgid "I get \"Error response from daemon: configured logging driver does not support reading\" when I run `docker logs matrix-synapse`. Why?"
 msgstr ""
 
-#: ../../../docs/faq.md:439
+#: ../../../docs/faq.md:440
 msgid "To prevent double-logging, Docker logging is disabled by explicitly passing `--log-driver=none` to all containers. Due to this, you cannot view logs using `docker logs matrix-*`."
 msgstr ""
 
-#: ../../../docs/faq.md:441
+#: ../../../docs/faq.md:442
 msgid "See [this section](maintenance-and-troubleshooting.md#how-to-see-the-logs) on the page for maintenance and troubleshooting for more details to see the logs."
 msgstr ""
 
-#: ../../../docs/faq.md:443
+#: ../../../docs/faq.md:444
 msgid "The server fails to start due to the `Unable to start service matrix-coturn.service` error. Why and how to solve it?"
 msgstr ""
 
-#: ../../../docs/faq.md:445
+#: ../../../docs/faq.md:446
 msgid "The error is most likely because Traefik cannot obtain SSL certificates due to certain reasons such as wrong domain name configuration or port 80 being unavailable due to other services."
 msgstr ""
 
-#: ../../../docs/faq.md:447
+#: ../../../docs/faq.md:448
 msgid "If Traefik fails to obtain an SSL certificate for domain names such as `matrix.`, Traefik Certs Dumper cannot extract the SSL certificate out of there, and coturn cannot be started and the error occurs. Refer to these comments for details:"
 msgstr ""
 
-#: ../../../docs/faq.md:449
+#: ../../../docs/faq.md:450
 msgid "<https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3957#issuecomment-2599590441>"
 msgstr ""
 
-#: ../../../docs/faq.md:450
+#: ../../../docs/faq.md:451
 msgid "<https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/4570#issuecomment-3364111466>"
 msgstr ""
 
-#: ../../../docs/faq.md:452
+#: ../../../docs/faq.md:453
 msgid "If you are not sure what the problem is, at first make sure that you have set the \"base domain\" (`example.com`, **not `matrix.example.com`**) to `matrix_domain`. You should be able to find it at the top of your `vars.yml`."
 msgstr ""
 
-#: ../../../docs/faq.md:454
+#: ../../../docs/faq.md:455
 msgid "If it is correctly specified, look Traefik's logs (`journalctl -fu matrix-traefik.service`) for errors by Let's Encrypt for troubleshooting."
 msgstr ""
 
-#: ../../../docs/faq.md:456
+#: ../../../docs/faq.md:457
 msgid "Miscellaneous"
 msgstr ""
 
-#: ../../../docs/faq.md:458
+#: ../../../docs/faq.md:459
 msgid "I would like to see this favorite service of mine integrated and become available on my Matrix server. How can I request it?"
 msgstr ""
 
-#: ../../../docs/faq.md:460
+#: ../../../docs/faq.md:461
 msgid "You can freely create an issue for feature request on the repository at GitHub [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/new/choose). Note this is a community project with no financial backing, and there is not assurance that your request would be eventually picked up by others and the requested feature would become available. The easiest way to get a feature into this project is to just develop it yourself."
 msgstr ""
 
-#: ../../../docs/faq.md:462
+#: ../../../docs/faq.md:463
 msgid "Also, please note that this playbook intends to focus solely on Matrix and Matrix-related services. If your request is not specific to Matrix, you may as well to consider to submit it to the [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook), maintained by the members behind this matrix-docker-ansible-deploy project. [This document on the interoperability](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md) describes how to deploy services along with the Matrix services easily."
 msgstr ""

i18n/translation-templates/docs/installing.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -249,61 +249,61 @@ msgid "or join some Matrix rooms:"
 msgstr ""
 
 #: ../../../docs/installing.md:148
-msgid "via the *Explore rooms* feature in Element Web or some other clients, or by discovering them using this [matrix-static list](https://view.matrix.org). **Note**: joining large rooms may overload small servers."
+msgid "via the *Explore rooms* feature in Element Web or some other clients, or by discovering them using this [matrix-static list](https://view.matrix.org). **Note**: joining large rooms may overload small servers. For tuning guidance on constrained hosts, see [Limit joining heavy rooms on constrained hosts](configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts)."
 msgstr ""
 
-#: ../../../docs/installing.md:149
+#: ../../../docs/installing.md:150
 msgid "or come say Hi in our support room — [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting."
 msgstr ""
 
-#: ../../../docs/installing.md:150
+#: ../../../docs/installing.md:151
 msgid "or help make this playbook better by contributing (code, documentation, or [coffee/beer](https://liberapay.com/s.pantaleev/donate))"
 msgstr ""
 
-#: ../../../docs/installing.md:152
+#: ../../../docs/installing.md:153
 msgid "⚠️ Keep the playbook and services up-to-date"
 msgstr ""
 
-#: ../../../docs/installing.md:154
+#: ../../../docs/installing.md:155
 msgid "While this playbook helps you to set up Matrix services and maintain them, it will **not** automatically run the maintenance task for you. You will need to update the playbook and re-run it **manually**."
 msgstr ""
 
-#: ../../../docs/installing.md:156
+#: ../../../docs/installing.md:157
 msgid "The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities."
 msgstr ""
 
-#: ../../../docs/installing.md:158
+#: ../../../docs/installing.md:159
 msgid "Since it is unsafe to keep outdated services running on the server connected to the internet, please consider to update the playbook and re-run it periodically, in order to keep the services up-to-date."
 msgstr ""
 
-#: ../../../docs/installing.md:160
+#: ../../../docs/installing.md:161
 msgid "Also, do not forget to update your system regularly. While this playbook may install basic services, such as Docker, it will not interfere further with system maintenance. Keeping the system itself up-to-date is out of scope for this playbook."
 msgstr ""
 
-#: ../../../docs/installing.md:162
+#: ../../../docs/installing.md:163
 msgid "For more information about upgrading or maintaining services with the playbook, take a look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)"
 msgstr ""
 
-#: ../../../docs/installing.md:164
+#: ../../../docs/installing.md:165
 msgid "Feel free to **re-run the setup command any time** you think something is wrong with the server configuration. Ansible will take your configuration and update your server to match."
 msgstr ""
 
-#: ../../../docs/installing.md:170
+#: ../../../docs/installing.md:171
 msgid "**Note**: see [this page on the playbook tags](playbook-tags.md) for more information about those tags."
 msgstr ""
 
-#: ../../../docs/installing.md:172
+#: ../../../docs/installing.md:173
 msgid "Make full use of `just` shortcut commands"
 msgstr ""
 
-#: ../../../docs/installing.md:174
+#: ../../../docs/installing.md:175
 msgid "After you get familiar with reconfiguring and re-running the playbook to maintain the server, upgrade its services, etc., you probably would like to make use of `just` shortcut commands for faster input."
 msgstr ""
 
-#: ../../../docs/installing.md:176
+#: ../../../docs/installing.md:177
 msgid "For example, `just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
 msgstr ""
 
-#: ../../../docs/installing.md:178
+#: ../../../docs/installing.md:179
 msgid "You can learn about the shortcut commands on this page: [Running `just` commands](just.md)"
 msgstr ""

i18n/translation-templates/docs/just.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -162,17 +162,17 @@ msgid "Conditional service restart"
 msgstr ""
 
 #: ../../../docs/just.md:49
-msgid "When using `just install-all` or `just install-service`, only services whose configuration or container image actually changed during the playbook run will be restarted. Unchanged services are left running (or get started if they were stopped). This reduces unnecessary downtime."
+msgid "When running `install-all` or `install-service` (whether via `just` or raw `ansible-playbook`), only services whose configuration or container image actually changed during the playbook run will be restarted. Unchanged services are left running (or get started if they were stopped). This reduces unnecessary downtime."
 msgstr ""
 
 #: ../../../docs/just.md:51
-msgid "When using `just setup-all`, all services are unconditionally restarted regardless of whether changes were detected. This is appropriate for `setup-all`'s thorough \"full setup\" semantics."
+msgid "When running with `setup-*` tags (e.g. `setup-all`, `setup-synapse`), all services are unconditionally restarted regardless of whether changes were detected. This is appropriate for setup's thorough \"full setup\" semantics."
 msgstr ""
 
 #: ../../../docs/just.md:53
-msgid "`just start-all` and `just start-group` always restart all targeted services, since no installation tasks run during these commands."
+msgid "`start-all` and `start-group` always restart all targeted services, since no installation tasks run during these commands."
 msgstr ""
 
 #: ../../../docs/just.md:55
-msgid "This behavior is controlled by the `devture_systemd_service_manager_conditional_restart_enabled` variable (default: `true`). To force unconditional restarts during installation, pass: `just install-all --extra-vars='devture_systemd_service_manager_conditional_restart_enabled=false'`"
+msgid "This behavior is automatically determined based on the playbook tags in use. It can be overridden with the `devture_systemd_service_manager_conditional_restart_enabled` variable. For example, to force unconditional restarts during installation: `just install-all --extra-vars='devture_systemd_service_manager_conditional_restart_enabled=false'`"
 msgstr ""

i18n/translation-templates/docs/maintenance-synapse.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -145,57 +145,61 @@ msgid "Synapse's presence feature which tracks which users are online and which
 msgstr ""
 
 #: ../../../docs/maintenance-synapse.md:86
-msgid "If you have enough compute resources (CPU & RAM), you can make Synapse better use of them by [enabling load-balancing with workers](configuring-playbook-synapse.md#load-balancing-with-workers)."
+msgid "On smaller servers, consider limiting joins to very complex rooms with [the room complexity guard](configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts)."
 msgstr ""
 
 #: ../../../docs/maintenance-synapse.md:88
-msgid "[Tuning your PostgreSQL database](maintenance-postgres.md#tuning-postgresql) could also improve Synapse performance. The playbook tunes the integrated Postgres database automatically, but based on your needs you may wish to adjust tuning variables manually. If you're using an [external Postgres database](configuring-playbook-external-postgres.md), you will also need to tune Postgres manually."
+msgid "If you have enough compute resources (CPU & RAM), you can make Synapse better use of them by [enabling load-balancing with workers](configuring-playbook-synapse.md#load-balancing-with-workers)."
 msgstr ""
 
 #: ../../../docs/maintenance-synapse.md:90
-msgid "Tuning caches and cache autotuning"
+msgid "[Tuning your PostgreSQL database](maintenance-postgres.md#tuning-postgresql) could also improve Synapse performance. The playbook tunes the integrated Postgres database automatically, but based on your needs you may wish to adjust tuning variables manually. If you're using an [external Postgres database](configuring-playbook-external-postgres.md), you will also need to tune Postgres manually."
 msgstr ""
 
 #: ../../../docs/maintenance-synapse.md:92
-msgid "Tuning Synapse's cache factor is useful for performance increases but also as part of controlling Synapse's memory use. Use the variable `matrix_synapse_caches_global_factor` to set the cache factor as part of this process."
+msgid "Tuning caches and cache autotuning"
 msgstr ""
 
 #: ../../../docs/maintenance-synapse.md:94
-msgid "**The playbook defaults the global cache factor to a large value** (e.g. `10`). A smaller value (e.g. `0.5`) will decrease the amount used for caches, but will [not necessarily decrease RAM usage as a whole](https://github.com/matrix-org/synapse/issues/3939)."
+msgid "Tuning Synapse's cache factor is useful for performance increases but also as part of controlling Synapse's memory use. Use the variable `matrix_synapse_caches_global_factor` to set the cache factor as part of this process."
 msgstr ""
 
 #: ../../../docs/maintenance-synapse.md:96
-msgid "Tuning the cache factor is useful only to a limited degree (as its crude to do in isolation) and therefore users who are tuning their cache factor should likely look into tuning autotune variables as well (see below)."
+msgid "**The playbook defaults the global cache factor to a large value** (e.g. `10`). A smaller value (e.g. `0.5`) will decrease the amount used for caches, but will [not necessarily decrease RAM usage as a whole](https://github.com/matrix-org/synapse/issues/3939)."
 msgstr ""
 
 #: ../../../docs/maintenance-synapse.md:98
-msgid "Cache autotuning is **enabled by default** and controlled via the following variables:"
+msgid "Tuning the cache factor is useful only to a limited degree (as its crude to do in isolation) and therefore users who are tuning their cache factor should likely look into tuning autotune variables as well (see below)."
 msgstr ""
 
 #: ../../../docs/maintenance-synapse.md:100
+msgid "Cache autotuning is **enabled by default** and controlled via the following variables:"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:102
 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"
 msgstr ""
 
-#: ../../../docs/maintenance-synapse.md:101
+#: ../../../docs/maintenance-synapse.md:103
 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"
 msgstr ""
 
-#: ../../../docs/maintenance-synapse.md:102
+#: ../../../docs/maintenance-synapse.md:104
 msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` — defaults to `30s`"
 msgstr ""
 
-#: ../../../docs/maintenance-synapse.md:104
+#: ../../../docs/maintenance-synapse.md:106
 msgid "You can **learn more about cache-autotuning and the global cache factor settings** in the [Synapse's documentation on caches and associated values](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values)."
 msgstr ""
 
-#: ../../../docs/maintenance-synapse.md:106
+#: ../../../docs/maintenance-synapse.md:108
 msgid "To **disable cache auto-tuning**, unset all values:"
 msgstr ""
 
-#: ../../../docs/maintenance-synapse.md:114
+#: ../../../docs/maintenance-synapse.md:116
 msgid "Users who wish to lower Synapse's RAM footprint should look into lowering the global cache factor and tweaking the autotune variables (or disabling auto-tuning). If your cache factor is too low for a given auto tune setting your caches will not reach autotune thresholds and autotune won't be able to do its job. Therefore, when auto-tuning is enabled (which it is by default), it's recommended to have your cache factor be large."
 msgstr ""
 
-#: ../../../docs/maintenance-synapse.md:116
+#: ../../../docs/maintenance-synapse.md:118
 msgid "See also [How do I optimize this setup for a low-power server?](faq.md#how-do-i-optimize-this-setup-for-a-low-power-server)."
 msgstr ""

i18n/translation-templates/docs/prerequisites.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -125,33 +125,13 @@ msgid "`443/tcp` and `443/udp`: HTTPS webserver"
 msgstr ""
 
 #: ../../../docs/prerequisites.md:60
-msgid "`3478/tcp`: STUN/TURN over TCP (used by [coturn](./configuring-playbook-turn.md))"
-msgstr ""
-
-#: ../../../docs/prerequisites.md:61
-msgid "`3478/udp`: STUN/TURN over UDP (used by [coturn](./configuring-playbook-turn.md))"
-msgstr ""
-
-#: ../../../docs/prerequisites.md:62
-msgid "`5349/tcp`: TURN over TCP (used by [coturn](./configuring-playbook-turn.md))"
-msgstr ""
-
-#: ../../../docs/prerequisites.md:63
-msgid "`5349/udp`: TURN over UDP (used by [coturn](./configuring-playbook-turn.md))"
-msgstr ""
-
-#: ../../../docs/prerequisites.md:64
 msgid "`8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. Some components like [Matrix User Verification Service](configuring-playbook-user-verification-service.md#open-matrix-federation-port) require this port to be opened **even with federation disabled**."
 msgstr ""
 
-#: ../../../docs/prerequisites.md:65
-msgid "the range `49152-49172/udp`: TURN over UDP"
-msgstr ""
-
-#: ../../../docs/prerequisites.md:66
+#: ../../../docs/prerequisites.md:61
 msgid "potentially some other ports, depending on the additional (non-default) services that you enable in the **configuring the playbook** step (later on). Consult each service's documentation page in `docs/` for that."
 msgstr ""
 
-#: ../../../docs/prerequisites.md:70
+#: ../../../docs/prerequisites.md:65
 msgid "[▶️](configuring-dns.md) When ready to proceed, continue with [Configuring DNS](configuring-dns.md)."
 msgstr ""

i18n/translation-templates/docs/self-building.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-03-03 10:49+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -65,31 +65,31 @@ msgid "`cinny`"
 msgstr ""
 
 #: ../../../docs/self-building.md:33
-msgid "`matrix-registration`"
+msgid "`sable`"
 msgstr ""
 
 #: ../../../docs/self-building.md:34
-msgid "`coturn`"
+msgid "`matrix-registration`"
 msgstr ""
 
 #: ../../../docs/self-building.md:35
-msgid "`matrix-corporal`"
+msgid "`coturn`"
 msgstr ""
 
 #: ../../../docs/self-building.md:36
-msgid "`exim-relay`"
+msgid "`matrix-corporal`"
 msgstr ""
 
 #: ../../../docs/self-building.md:37
-msgid "`matrix-bridge-hookshot`"
+msgid "`exim-relay`"
 msgstr ""
 
 #: ../../../docs/self-building.md:38
-msgid "`matrix-bridge-appservice-irc`"
+msgid "`matrix-bridge-hookshot`"
 msgstr ""
 
 #: ../../../docs/self-building.md:39
-msgid "`matrix-bridge-appservice-slack`"
+msgid "`matrix-bridge-appservice-irc`"
 msgstr ""
 
 #: ../../../docs/self-building.md:40