diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 9dffaee8f..fff721410 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -2,7 +2,7 @@
 name: Bug report
 about: Create a report to help us improve
 title: ''
-labels: ''
+labels: bug
 assignees: ''
 
 ---
@@ -11,7 +11,7 @@ assignees: ''
 A clear and concise description of what the bug is.
 
 <!--
-NOTE: This Ansible playbook installs tens of separate services. If you're having a problem with a specific service, it is likely that the problem is not with our deployment method, but with the service itself. You may wish to report that problem at the source, upstream, and not to us
+NOTE: This Ansible playbook installs tens of separate services. If you're having a problem with a specific one, it is likely that the problem is with the service itself. You may wish to report that problem at the source, upstream.
 -->
 
 **To Reproduce**
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000..57488385d
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,6 @@
+---
+blank_issues_enabled: false
+contact_links:
+    - name: Support room on Matrix
+      url: https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com
+      about: Get timely support from more people by joining our Matrix room.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
index 3fb2ffe26..5746ab313 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -2,18 +2,20 @@
 name: Feature request
 about: Suggest an idea for this project
 title: ''
-labels: ''
+labels: suggestion
 assignees: ''
 
 ---
 
 **Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+A clear and concise description of what the problem is. Ex. I'm always frustrated when […]
 
 <!--
 NOTE: When submitting feature requests, be aware that:
 
-- This Ansible playbook installs tens of separate services. If you're having a problem with a specific service or you'd like some functionality added to it, it is likely that the problem is not with our deployment method, but with the service itself. You may wish to report that problem at the source, upstream, and not to us.
+- This Ansible playbook installs tens of separate services. If you're having a problem with a specific one, it is likely that the problem is with the service itself. You may wish to report that problem at the source, upstream.
+
+- This playbook intends to focus solely on Matrix and Matrix-related services. If your request is not specific to them, you may as well to consider to submit it to the mash-playbook project: https://github.com/mother-of-all-self-hosting/mash-playbook
 
 - This is a community project with no financial backing. The easiest way to get a feature into this project is to just develop it yourself.
 -->
diff --git a/.github/ISSUE_TEMPLATE/i-need-help.md b/.github/ISSUE_TEMPLATE/i-need-help.md
index 6e862463b..8bf1a4da4 100644
--- a/.github/ISSUE_TEMPLATE/i-need-help.md
+++ b/.github/ISSUE_TEMPLATE/i-need-help.md
@@ -2,13 +2,15 @@
 name: I need help
 about: Get support from our community
 title: ''
-labels: ''
+labels: question
 assignees: ''
 
 ---
 
 <!--
-NOTE: you can usually get more timely support and from more people by joining our Matrix room (also bridged to IRC). See the [Support section of our README](https://github.com/spantaleev/matrix-docker-ansible-deploy#support)
+NOTE: our FAQ page is available at https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/faq.md. It contains a list of questions and answers about configuration, installation, troubleshooting, etc. Before creating a new issue, you are encouraged to have a look at it.
+
+Also you can usually get more timely support and from more people by joining our Matrix room (also bridged to IRC). See the support section of our README.
 -->
 
 **Playbook Configuration**:
diff --git a/.github/renovate.json b/.github/renovate.json
index 06bf4ade9..e9c3ceb67 100644
--- a/.github/renovate.json
+++ b/.github/renovate.json
@@ -3,6 +3,7 @@
 	"extends": [
 		"config:base"
 	],
+	"labels": ["dependencies"],
 	"regexManagers": [
 		{
 			"fileMatch": ["defaults/main.yml$"],
@@ -19,5 +20,8 @@
 			],
 			"ignoreUnstable": false
 		}
+	],
+	"ignoreDeps": [
+		"ghcr.io/matrixgpt/matrix-chatgpt-bot"
 	]
 }
diff --git a/.github/workflows/close-stale-issues.yml b/.github/workflows/close-stale-issues.yml
new file mode 100644
index 000000000..4473c589e
--- /dev/null
+++ b/.github/workflows/close-stale-issues.yml
@@ -0,0 +1,50 @@
+---
+name: 'Close stale issues and PRs'
+on:  # yamllint disable-line rule:truthy
+  # Use this to do a dry run from a pull request
+  # pull_request:
+  schedule:
+    - cron: '30 1 * * *'
+
+permissions:
+  issues: write
+  pull-requests: write
+
+jobs:
+  stale:
+    if: github.repository == 'spantaleev/matrix-docker-ansible-deploy'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v9
+        with:
+          ######################################################################
+          # Issues/PRs
+          ######################################################################
+          exempt-assignees: 'spantaleev,aine-etke'
+          operations-per-run: 500
+          # Use this to do a dry run from a pull request
+          # debug-only: true
+          ######################################################################
+          # Issues
+          ######################################################################
+          stale-issue-message: 'This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. To exempt the issue from being marked as stale again due to inactivity, add "confirmed" label.'
+          close-issue-message: 'This issue was closed because it has been stalled for 7 days with no activity. If this issue is still reproduced, feel free to provide the issue with up-to-date information.'
+          stale-issue-label: 'stale'
+          # Add this label to exempt the issue from being marked as stale due to inactivity
+          exempt-issue-labels: 'confirmed'
+          # An allow-list of label(s) to only process the issues which contain one of these label(s).
+          any-of-issue-labels: 'needs-info,question'
+          ######################################################################
+          # PRs
+          ######################################################################
+          days-before-pr-stale: '365'
+          days-before-pr-close: '30'
+          stale-pr-message: 'This PR is stale because it has not been provided with required information or its conflicts have not been fixed over a year. Remove stale label or this will be closed in 30 days. To exempt the PR from being marked as stale again due to inactivity, add "confirmed" label.'
+          close-pr-message: 'This PR was closed because it has been stalled for 30 days with no activity.'
+          stale-pr-label: 'stale'
+          # Add this label to exempt the PR from being marked as stale due to inactivity
+          exempt-pr-labels: 'confirmed'
+          # An allow-list of label(s) to only process the PRs which contain one of these label(s).
+          any-of-pr-labels: 'needs-info,needs-rebase'
+          # Use this to ignore updates such as comments (only to keep the PR alive by bumping)
+          ignore-pr-updates: true
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 84c5b1722..a31ce22ff 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,158 @@
+# 2025-01-19
+
+## Conduwuit support
+
+Thanks to [Virkkunen](https://github.com/Virkkunen), we now have optional experimental [Conduwuit](https://conduwuit.puppyirl.gay/) homeserver support for new installations.
+
+Conduwuit is a fork of [Conduit](./docs/configuring-playbook-conduit.md), which the playbook also supports. See [Differences from upstream Conduit](https://conduwuit.puppyirl.gay/differences.html).
+
+Existing installations do **not** need to be updated. **Synapse is still the default homeserver implementation** installed by the playbook.
+
+To try out Conduwuit, we recommend that you **use a new server**. Refer to our [Configuring Conduwuit](./docs/configuring-playbook-conduwuit.md) guide for details.
+
+**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse/Conduit/Dendrite to Conduwuit) without data loss.
+
+
+# 2025-01-14
+
+## (Backward Compatibility Break) Synapse v1.122.0 requires Postgres v13
+
+The Synapse homeserver [requires Postgres v13 or newer](https://github.com/element-hq/synapse/issues/18034).
+
+If you've been maintaining your setup for a while and you haven't been doing [Postgres upgrades](maintenance-postgres.md#upgrading-postgresql), you may be on an old version of Postgres. The easiest way to check is to see the contents of the `/matrix/postgres/data/PG_VERSION` file.
+
+If you're on a Postgres version older than v13, you need to [upgrade your Postgres setup](maintenance-postgres.md#upgrading-postgresql) or Synapse will produce an error on startup.
+
+If you're using an external Postgres server (not installed by this playbook), you'll need to figure out how to upgrade it yourself.
+
+If you're not ready to upgrade your Postgres setup yet, you can temporarily remain on an old Synapse version by adding the following configuration to your `vars.yml` file:
+
+```yaml
+# Pinning to the last Synapse version which supports Postgres v11 and v12.
+matrix_synapse_version: v1.121.1
+```
+
+
+# 2024-11-26
+
+## (Backward Compatibility Break) Synapse now defaults to enabling authenticated media
+
+**TLDR**: with this update, your Synapse homeserver will start requiring authentication for newly-uploaded media files. While the majority of the ecosystem (clients, bots, etc.) should support this, certain software may lack support for it (and you may wish to turn it off, if it's causing issues).
+
+The default configuration for the Synapse homeserver now [enforces Authenticated media by default](https://element-hq.github.io/synapse/v1.120/upgrade.html#authenticated-media-is-now-enforced-by-default).
+
+Servers like `matrix.org` have already [sunset unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) months ago.
+
+Now that **various clients, bots, bridges and extra services have caught up with authenticated media support**, Synapse developers seem confident that it's time to enable authenticated media by default.
+
+We're changing the playbook configuration for authenticated media to keep up with upstream defaults changing.
+
+Old and unmaintained bridges (like all mx-puppet bridges, etc.) do not support authenticated media. Other software may be similarly affected. If you experience issues with some Matrix-related software, you may wish to disable authenticated media and contact the software maintainers to let them know.
+
+You can disable authenticated media at any time by setting `matrix_synapse_enable_authenticated_media: false` in your `vars.yml` configuration file and re-running the playbook.
+
+
+# 2024-11-23
+
+## (Backward Compatibility Break) The playbook now defaults to Valkey, instead of KeyDB
+
+**TLDR**: if the playbook installed KeyDB (or Redis) as a dependency for you before, it will now replace it with [Valkey](https://valkey.io/) (a drop-in alternative). We [previously switched from Redis to KeyDB](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis), but Valkey is a better alternative, so we're switching again.
+
+The playbook used to install Redis or KeyDB if services have a need for a Redis-compatible implementation ([enabling worker support for Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-workers), [enabling Hookshot encryption](docs/configuring-playbook-bridge-hookshot.md#end-to-bridge-encryption), etc.).
+
+Earlier this year, we switched from Redis to KeyDB - see [(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis).
+
+Because Valkey seems to be a better successor to Redis (than KeyDB) and likely doesn't suffer from [issues like this one](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3544), we now replace KeyDB with Valkey.
+
+Valkey (like KeyDB and Redis in the past) is an implicitly enabled dependency - you don't need custom configuration in `vars.yml` to enable it.
+
+Next time your run the playbook (via the `setup-all` tag), **KeyDB will be automatically uninstalled and replaced with Valkey**. Some Synapse downtime may occur while the switch happens.
+
+Users on `arm32` should be aware that there's **neither a prebuilt `arm32` container image for Valkey**, nor the Valkey role supports self-building yet. Users on this architecture likely don't run Synapse with workers, etc., so they're likely in no need of Valkey (or Redis/KeyDB). If Redis is necessary in an `arm32` deployment, disabling Valkey and making the playbook fall back to Redis is possible (see below).
+
+**The playbook still supports Redis** and you can keep using Redis (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:
+
+```yml
+# Explicitly disable both Valkey and KeyDB.
+#
+# Redis will be auto-enabled if necessary,
+# because there's no other Redis-compatible implementation being enabled.
+valkey_enabled: false
+keydb_enabled: false
+```
+
+**The playbook still supports KeyDB** and you can keep using KeyDB (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:
+
+```yml
+# Explicitly disable Valkey  enable KeyDB.
+#
+# Redis will not be auto-enabled beandcause a Redis-compatible implementation (KeyDB) is enabled.
+valkey_enabled: false
+keydb_enabled: true
+```
+
+At some point in time in the future, we'll remove both KeyDB and Redis from the playbook, so we recommend that you migrate to Valkey earlier anyway.
+
+
+# 2024-11-14
+
+## HTTP-compression support for Traefik-based setups
+
+The playbook now **automatically enables HTTP-compression support** for major services powered by the playbook, like [Cinny](./docs/configuring-playbook-client-cinny.md), [Element Web](./docs/configuring-playbook-client-element-web.md), [Hydrogen](./docs/configuring-playbook-client-hydrogen.md), as well as for Matrix Client-Server and Federation APIs (`matrix.example.com`).
+
+Other services installed by the playbook are currently not compression-enabled, but may become so over time. This change is rolled out on a per-service basis (as opposed to doing it globally, at the Traefik entrypoint level) to allow certain services or route endpoints which do not behave well when compressed (e.g. [issue 3749](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3749)) to be excluded from compression.
+
+A long time ago, various services were operating with `gzip`-compression enabled at the nginx level. Since the switch to Traefik (see [Goodbye, `matrix-nginx-proxy` 🪦](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/57c5271d9d6265a34a9d9cceb93365f685074f96/CHANGELOG.md#goodbye-matrix-nginx-proxy-)), all services (with the exception of Matrix APIs for Synapse worker-enabled setups which are powered by `nginx` via `synapse-reverse-proxy-companion`) have been operating without HTTP-compression support.
+
+HTTP-compression is now done via Traefik's [compress](https://doc.traefik.io/traefik/middlewares/http/compress/) middleware. We use the default configuration for this middleware, which enables `zstd`, `br` and `gzip` support (in this order). This middleware's configuration can be configured via variables in the Traefik role (see `traefik_config_http_middlewares_compression_middleware_options`).
+
+If you're using your own Traefik reverse-proxy server ([Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)) instead of the playbook's integrated Traefik service, you can benefit from the same by:
+
+- defining a [compress](https://doc.traefik.io/traefik/middlewares/http/compress/) middleware (via the [file](https://doc.traefik.io/traefik/providers/file/) or [Docker](https://doc.traefik.io/traefik/providers/docker/) providers)
+- setting `matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled` to `true`
+- specifying the middleware's name in `matrix_playbook_reverse_proxy_traefik_middleware_compression_name` (e.g. `matrix_playbook_reverse_proxy_traefik_middleware_compression_name: my-compression-middleware@file`)
+
+## Timeout adjustments for Traefik-based setups
+
+The playbook now supports configuring various [transport.respondingTimeouts](https://doc.traefik.io/traefik/routing/entrypoints/#respondingtimeouts) timeout values (`readTimeout`, `writeTimeout`, `idleTimeout`) for the `web`, `web-secure` and `matrix-federation` entrypoints.
+
+If you're using your own Traefik reverse-proxy server ([Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)) instead of the playbook's integrated Traefik service, you may wish to do similar configuration changes to your setup manually.
+
+The most interesting of these is the `readTimeout` configuration value (the maximum duration for reading the entire request, including the body), which used to default to `60s`. For large and slowly progressing file uploads, `60s` would often not be enough for the transfer to finish and uploads would end up being interrupted. The playbook now raises the `readTimeout` value to 5 minutes (`300s`) to improve this use-case.
+
+The `traefik_config_entrypoint_web_transport_respondingTimeouts_*` variables (for the `web` entrypoint) cascade to affecting the timeout values for the `web-secure` and `matrix-federation` entrypoints, so you can easily adjust all timeout values using them.
+
+Example of the default timeout values used by the playbook:
+
+```yml
+traefik_config_entrypoint_web_transport_respondingTimeouts_readTimeout: 300s
+
+# 0s means "no timeout"
+traefik_config_entrypoint_web_transport_respondingTimeouts_writeTimeout: 0s
+
+traefik_config_entrypoint_web_transport_respondingTimeouts_idleTimeout: 180s
+```
+
+Alternatively, you may adjust the timeout values for specific entrypoints (like `web-secure` and `matrix-federation`) using dedicated variables (like `traefik_config_entrypoint_web_secure_transport_respondingTimeouts_readTimeout` and `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_readTimeout`).
+
+
+# 2024-11-08
+
+## Support for synapse-admin auto-configuration via /.well-known/matrix/client
+
+You can administrate your Synapse-powered homeserver using synapse-admin hosted externally (e.g. [admin.etke.cc](https://admin.etke.cc/)) and the synapse-admin instance would still auto-configure itself correctly for your server by [reading its `/.well-known/matrix/client` file](https://github.com/etkecc/synapse-admin/pull/126).
+
+The playbook now configures the `/.well-known/matrix/client` file for this by default, injecting into it a `cc.etke.synapse-admin` section that contains the full synapse-admin configuration. This is done even if you don't enable the synapse-admin service in your configuration. The reason for always doing it is to allow users to skip the (small) overhead of self-hosting the non-core synapse-admin service, yet still be able to use it from elsewhere when needed.
+
+If you don't ever plan on using synapse-admin from other servers (besides your own due to [self-hosting synapse-admin](./docs/configuring-playbook-synapse-admin.md)), you **can disable this** `/.well-known/matrix/client` configuration via `matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_enabled: false`
+
+
+# 2024-10-28
+
+## (BC Break) Postmoogle's variable names need adjustments
+
+Due to the recategorization of [Postmoogle](./docs/configuring-playbook-bridge-postmoogle.md) from the bot to the bridge, its variables were renamed (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`). You need to adjust your `vars.yml` configuration accordingly.
+
 # 2024-10-19
 
 ## Support for Matrix Authentication Service
@@ -39,7 +194,6 @@ It's designed as a more private and [✨ featureful](https://github.com/etkecc/b
 
 To get started, see the [Setting up baibot](./docs/configuring-playbook-bot-baibot.md) documentation page.
 
-
 ## Switching synapse-admin to etke.cc's fork
 
 The playbook now installs [etke.cc](https://etke.cc/)'s [fork](https://github.com/etkecc/synapse-admin) of [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin) (originally developed by [Awesome-Technologies](https://github.com/Awesome-Technologies)). This fork is a drop-in replacement for the original software.
@@ -50,7 +204,7 @@ If upstream synapse-admin picks up the pace and improves, the etke.cc fork may d
 
 If you'd like to switch back to the original synapse-admin software, you can do so by adding the following configuration to your `vars.yml` file:
 
-```yml
+```yaml
 matrix_synapse_admin_docker_image: "{{ matrix_synapse_admin_docker_image_name_prefix }}awesometechnologies/synapse-admin:{{ matrix_synapse_admin_version }}"
 matrix_synapse_admin_docker_image_name_prefix: "{{ 'localhost/' if matrix_synapse_admin_container_image_self_build else matrix_container_global_registry_prefix }}"
 
@@ -75,7 +229,7 @@ All non-deprecated mautrix bridges in the playbook have been reworked to support
 
 We recommend **enabling double-puppeting via the new Appservice method** by adding the following configuration to your `vars.yml` file:
 
-```yml
+```yaml
 matrix_appservice_double_puppet_enabled: true
 ```
 
@@ -107,7 +261,7 @@ This upgrade necessitates configuration policy changes as described in [matrix-c
 
 If you'd like to remain on the old (v2) version of matrix-corporal, you can do so by adding the following configuration to your `vars.yml` file:
 
-```yml
+```yaml
 matrix_corporal_version: 2.8.0
 ```
 
@@ -128,7 +282,6 @@ For those wishing to more easily integrate [Prometheus](https://prometheus.io/)'
 
 See [Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](./docs/configuring-playbook-alertmanager-receiver.md) for more details.
 
-
 ## Traefik v3 and HTTP/3 are here now
 
 **TLDR**: Traefik was migrated from v2 to v3. Minor changes were done to the playbook. Mostly everything else worked out of the box. Most people will not have to do any tweaks to their configuration. In addition, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is now auto-enabled for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints. If you have a firewall in front of your server and you wish to benefit from `HTTP3`, you will need to open the `443` and `8448` UDP ports in it.
@@ -149,11 +302,9 @@ If you've tweaked any of this playbook's `_path_prefix` variables and made them
 
 If you're not using [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) (the only role we had to tweak to adapt it to Traefik v3), you **may potentially downgrade to Traefik v2** (if necessary) by adding `traefik_verison: v2.11.4` to your configuration. People using `matrix-media-repo` cannot downgrade this way, because `matrix-media-repo` has been adjusted to use `PathRegexp` - a [routing matcher](https://doc.traefik.io/traefik/v2.11/routing/routers/#rule) that Traefik v2 does not understand.
 
-
 ### HTTP/3 is enabled by default
 
-In Traefik v3, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is no longer considered experimental now.
-Due to this, **the playbook auto-enables HTTP3** for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints.
+In Traefik v3, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is no longer considered experimental now. Due to this, **the playbook auto-enables HTTP3** for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints.
 
 HTTP3 uses the UDP protocol and **the playbook (together with Docker) will make sure that the appropriate ports** (`443` over UDP & `8448` over UDP) **are exposed and whitelisted in your server's firewall**. However, **if you have another firewall in front of your server** (as is the case for many cloud providers), **you will need to manually open these UDP ports**.
 
@@ -163,7 +314,7 @@ Still, if HTTP/3 cannot function correctly in your setup, it's best to disable a
 
 To **disable HTTP/3**, you can use the following configuration:
 
-```yml
+```yaml
 traefik_config_entrypoint_web_secure_http3_enabled: false
 
 # Disabling HTTP/3 for the web-secure entrypoint (above),
@@ -177,7 +328,7 @@ matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_http3_ena
 
 If you are using [your own webserver](./docs/configuring-playbook-own-webserver.md) (in front of Traefik), port binding on UDP port `8448` by default due to HTTP/3 is either unnecessary or [may get in the way](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3402). If it does, you can disable it:
 
-```yml
+```yaml
 # Disable HTTP/3 for the federation entrypoint.
 # If you'd like HTTP/3, consider configuring it for your other reverse-proxy.
 #
@@ -198,7 +349,7 @@ The playbook has just started making use of this feature. **From now on, your sy
 
 If you'd like **to go back to the old unrestricted behavior**, use the following configuration:
 
-```yml
+```yaml
 # Use this configuration to allow synapse-admin to manage any homeserver instance.
 matrix_synapse_admin_config_restrictBaseUrl: []
 ```
@@ -218,20 +369,18 @@ To avoid future problems, we've [reconfigured](https://github.com/spantaleev/mat
 
 When generating new webhooks, you should start seeing the new URLs being used.
 
-**For now**, **both** old URLs (`/hookshot/webhooks/:hookId`) and new URLs (`/hookshot/webhooks/webhook/:hookId`) **continue to work***, so your webhooks will not break just yet.
+**For now**, **both** old URLs (`/hookshot/webhooks/:hookId`) and new URLs (`/hookshot/webhooks/webhook/:hookId`) **continue to work**, so your webhooks will not break just yet.
 
 However, **we recommend that you update all your old webhook URLs** (configured in other systems) to include the new `/webhook` path component, so that future Hookshot changes (whenever they come) will not break your webhooks. You don't need to do anything on the Hookshot side - you merely need to reconfigure the remote systems that use your webhook URLs.
 
 
-
 # 2024-06-22
 
 ## The maubot user is now managed by the playbook
 
 To make things easier and to be consistent with other roles, the [maubot](./docs/configuring-playbook-bot-maubot.md) user (`bot.maubot` by default) is [now](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3376) automatically created be the playbook.
 
-If you have an existing maubot installation, you will need to specify `matrix_bot_maubot_initial_password` in your `vars.yml` file to make the playbook not complain about it being undefined.
-Since the bot is already registered in your installation, there's nothing for the playbook to do anyway. In case you don't remember the password you've registered your maubot user account with, you can specify any value for this variable.
+If you have an existing maubot installation, you will need to specify `matrix_bot_maubot_initial_password` in your `vars.yml` file to make the playbook not complain about it being undefined. Since the bot is already registered in your installation, there's nothing for the playbook to do anyway. In case you don't remember the password you've registered your maubot user account with, you can specify any value for this variable.
 
 If you've registered another username for the bot (other than the recommended default of `bot.maubot`), consider adjusting the `matrix_bot_maubot_login` variable (e.g. `matrix_bot_maubot_login: my.maubot.username`).
 
@@ -263,14 +412,13 @@ Users on `arm32` should be aware that there's **neither a prebuilt `arm32` conta
 
 **The playbook still supports Redis** and you can keep using Redis (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:
 
-```yml
+```yaml
 # Explicitly disable KeyDB, which will auto-enable Redis
 # if the playbook requires it as a dependency for its operation.
 keydb_enabled: false
 ```
 
 
-
 # 2024-03-24
 
 ## Initial work on IPv6 support
@@ -322,8 +470,7 @@ The documentation pages contain more information on how to migrate.
 
 ## Much larger Synapse caches and cache auto-tuning enabled by default
 
-Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook now uses much larger caches and enables Synapse's [cache auto-tuning functionality](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values).
-This work and the default values used by the playbook are inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/deployment/synapse.html).
+Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook now uses much larger caches and enables Synapse's [cache auto-tuning functionality](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values). This work and the default values used by the playbook are inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/deployment/synapse.html).
 
 The playbook has always used a very conservative cache factor (`matrix_synapse_caches_global_factor`) value of `0.5`, which may be OK for small and underactive deployments, but is not ideal for larger servers. Paradoxically, a small global cache factor value [does not necessarily decrease RAM usage as a whole](https://github.com/matrix-org/synapse/issues/3939).
 
@@ -424,7 +571,7 @@ For 6 years, `matrix-nginx-proxy` has been the front-most reverse-proxy in our s
 To us, `matrix-nginx-proxy` was:
 
 - an [nginx](https://nginx.org/)-based reverse-proxy
-- an Ansible role organizing the work of [certbot](https://certbot.eff.org/) - retrieving free [Let's Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-proxy` and for the [Coturn TURN server](./docs/configuring-playbook-turn.md)
+- an Ansible role organizing the work of [certbot](https://certbot.eff.org/) - retrieving free [Let's Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-proxy` and for the [coturn TURN server](./docs/configuring-playbook-turn.md)
 - a central component for reverse-proxying to the [long list of services](./docs/configuring-playbook.md) supported by the playbook. As such, it became a dependency that all these services had to inject themselves into during runtime
 - an intermediary through which addons (bridges, bots) communicated with the homeserver. Going through an intermediary (instead of directly talking to the homeserver) is useful when certain components (like [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) are enabled, because it lets these services "steal routes" from the homeserver
 - a webserver for serving the `/.well-known/matrix` static files (generated by the `matrix-base` role until now)
@@ -433,23 +580,19 @@ To us, `matrix-nginx-proxy` was:
 
 Talk about a jack of all trades! The [UNIX philosophy](https://en.wikipedia.org/wiki/Unix_philosophy) (and Docker container philosophy) of "do one thing and do it well" had been severely violated for too long.
 
-On a related note, we also had a large chain of reverse-proxies in the mix.
-In the worst case, it was something like this: (Traefik -> `matrix-nginx-proxy:8080` -> `matrix-nginx-proxy:12080` -> `matrix-synapse-reverse-proxy-companion:8008` -> `matrix-synapse:8008`).
+On a related note, we also had a large chain of reverse-proxies in the mix. In the worst case, it was something like this: (Traefik -> `matrix-nginx-proxy:8080` -> `matrix-nginx-proxy:12080` -> `matrix-synapse-reverse-proxy-companion:8008` -> `matrix-synapse:8008`).
 
-Due to complexity and the playbook's flexibility (trying to accommodate a mix of tens of components), many layers of indirection were necessary. We do like reverse-proxies, but.. not quite enough to enjoy going through a chain of ~4 of them before reaching the target service.
+Due to complexity and the playbook's flexibility (trying to accommodate a mix of tens of components), many layers of indirection were necessary. We do like reverse-proxies, but… not quite enough to enjoy going through a chain of ~4 of them before reaching the target service.
 
 After **a ton of work** in the last weeks (200+ commits, which changed 467 files - 8684 insertions and 8913 deletions), **we're finally saying goodbye** to `matrix-nginx-proxy`.
 
-
 ### Going Traefik-native and cutting out all middlemen
 
 In our new setup, you'll see the bare minimum number of reverse-proxies.
 
 In most cases, there's only Traefik and all services being registered directly with it. When [Synapse workers](./docs/configuring-playbook-synapse.md#load-balancing-with-workers) are enabled, `matrix-synapse-reverse-proxy-companion` remains as an extra reverse-proxy that requests go through (for load-balancing to the correct Synapse worker), but in all other cases services are exposed directly.
 
-This reduces "network" hops (improving performance) and also decreases the number of components (containers).
-Each Ansible role in our setup is now independent and doesn't need to interact with other roles during runtime.
-
+This reduces "network" hops (improving performance) and also decreases the number of components (containers). Each Ansible role in our setup is now independent and doesn't need to interact with other roles during runtime.
 
 ### Traefik now has an extra job
 
@@ -476,21 +619,18 @@ People running the default Traefik setup do not need to do anything to make Trae
 
 You may disable Traefik acting as an intermediary by explicitly setting `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_enabled` to `false`. Services would then be configured to talk to the homeserver directly, giving you a slight performance boost and a "simpler" Traefik setup. However, such a configuration is less tested and will cause troubles, especially if you enable more services (like `matrix-media-repo`, etc.) in the future. As such, it's not recommended.
 
-
 ### People managing their own Traefik instance need to do minor changes
 
 This section is for people [managing their own Traefik instance on the Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you). Those [using Traefik managed by the playbook](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) don't need to do any changes.
 
 Because [Traefik has an extra job now](#traefik-now-has-an-extra-job), you need to adapt your configuration to add the additional `matrix-internal-matrix-client-api` entrypoint and potentially configure the `matrix_playbook_reverse_proxy_container_network` variable. See the [Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you) documentation section for more details.
 
-
 ### People fronting Traefik with another reverse proxy need to do minor changes
 
 We've already previously mentioned that you need to do some minor [configuration changes related to `traefik_additional_entrypoints_auto`](#backward-compatibility-configuration-changes-required-for-people-fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy).
 
 If you don't do these changes (switching from `traefik_additional_entrypoints_auto` to multiple other variables), your Traefik setup will not automatically receive the new `matrix-internal-matrix-client-api` Traefik entrypoint and Traefik would not be able to perform [its new duty of connecting addons with the homeserver](#traefik-now-has-an-extra-job).
 
-
 ### Supported reverse proxy types are now fewer
 
 This section is for people using a more custom reverse-proxy setup - those having `matrix_playbook_reverse_proxy_type` set to a value different than the default (`playbook-managed-traefik`).
@@ -512,7 +652,6 @@ If you were using these values as a way to stay away from Traefik, you now have
 - (recommended) [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)
 - (not recommended) [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all) and reverse-proxying to each and every service manually
 
-
 ### Container networking changes
 
 Now that `matrix-nginx-proxy` is not in the mix, it became easier to clear out some other long-overdue technical debt.
@@ -527,7 +666,6 @@ Carrying out these container networking changes necessitated modifying many comp
 
 We've refrained from creating too many container networks (e.g. one for each component), to avoid exhausting Docker's default network pool and contaminating the container networks list too much.
 
-
 ### Metrics exposure changes
 
 This section is for people who are exposing monitoring metrics publicly, to be consumed by an external Prometheus server.
@@ -540,7 +678,6 @@ From now on, there are new variables for doing roughly the same - `matrix_metric
 
 The playbook will tell you about all variables that you need to migrate during runtime, so rest assured - you shouldn't be able to miss anything!
 
-
 ### Matrix static files
 
 As mentioned above, static files like `/.well-known/matrix/*` or your base domain's `index.html` file (when [serving the base domain via the Matrix server](./docs/configuring-playbook-base-domain-serving.md) was enabled) were generated by the `matrix-base` or `matrix-nginx-proxy` roles and put into a `/matrix/static-files` directory on the server. Then `matrix-nginx-proxy` was serving all these static files.
@@ -549,7 +686,6 @@ All of this has been extracted into a new `matrix-static-files` Ansible role tha
 
 The playbook will migrate and update the `/.well-known/matrix/*` files automatically but not your own files in `nginx-proxy/data/matrix-domain/` you will need to back these up yourself otherwise they will be lost. It will also warn you about usage of old variable names, so you can adapt to the new names.
 
-
 ### A note on performance
 
 Some of you have been voicing their concerns (for a long time) about Traefik being too slow and nginx being better.
@@ -564,7 +700,6 @@ Even our previously mentioned benchmarks (yielding ~1300 rps) are synthetic - hi
 
 If this is still not convincing enough for you and you want the best possible performance, consider [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) (thus having the slowest part - SSL termination - happen elsewhere) or [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all). The playbook will not get in your way of doing that, but these options may make your life much harder. Performance comes at a cost, after all.
 
-
 ### Migration procedure
 
 The updated playbook will automatically perform some migration tasks for you:
@@ -583,14 +718,11 @@ The updated playbook will automatically perform some migration tasks for you:
 
 We don't recommend changing these variables and suppressing warnings, unless you know what you're doing.
 
-**Most people should just upgrade as per-normal**, bearing in mind that a lot has changed and some issues may arise.
-The playbook would guide you through renamed variables automatically.
-
+**Most people should just upgrade as per-normal**, bearing in mind that a lot has changed and some issues may arise. The playbook would guide you through renamed variables automatically.
 
 ### Conclusion
 
-Thousands of lines of code were changed across hundreds of files.
-All addons (bridges, bots) were rewired in terms of container networking and in terms of how they reach the homeserver.
+Thousands of lines of code were changed across hundreds of files. All addons (bridges, bots) were rewired in terms of container networking and in terms of how they reach the homeserver.
 
 I don't actively use all the ~100 components offered by the playbook (no one does), nor do I operate servers exercising all edge-cases. As such, issues may arise. Please have patience and report (or try to fix) these issues!
 
@@ -605,8 +737,7 @@ People who are [Fronting the integrated Traefik reverse-proxy webserver with ano
 
 Such a full variable redefinion is intrustive, because it prevents the playbook from injecting additional entrypoints into the Traefik webserver. In the future, the playbook may have a need to do so.
 
-For this reason, we no longer recommend completely redefining `traefik_additional_entrypoints_auto`.
-The playbook now defines [various `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_*` variables in the `defaults/main.yml` file](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-base/defaults/main.yml) of the `matrix-base` role which can be used as a safer alternative to `traefik_additional_entrypoints_auto`.
+For this reason, we no longer recommend completely redefining `traefik_additional_entrypoints_auto`. The playbook now defines [various `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_*` variables in the `defaults/main.yml` file](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-base/defaults/main.yml) of the `matrix-base` role which can be used as a safer alternative to `traefik_additional_entrypoints_auto`.
 
 Adapt your configuration as seen below:
 
@@ -656,8 +787,7 @@ Thanks to them, a new [v0.3.0](https://github.com/anoadragon453/matrix-reminder-
 
 The new version also comes with new `allowlist` and `blocklist` settings, which make it possible to restrict who can use the bot. Previously anyone, even across the Matrix Federation could talk to it and schedule reminders.
 
-The playbook defaults all bridges and bots (where possible) to only be exposed to users of the current homeserver, not users across federation.
-Thanks to the new version of this bot making such a restriction possible, we're now making use of it. The playbook (via its `group_vars/matrix_servers` file) automatically enables the `allowlist` (`matrix_bot_matrix_reminder_bot_allowlist_enabled: true`) and configures it in such a way (`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) so as to restrict the bot to your homeserver's users.
+The playbook defaults all bridges and bots (where possible) to only be exposed to users of the current homeserver, not users across federation. Thanks to the new version of this bot making such a restriction possible, we're now making use of it. The playbook (via its `group_vars/matrix_servers` file) automatically enables the `allowlist` (`matrix_bot_matrix_reminder_bot_allowlist_enabled: true`) and configures it in such a way (`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) so as to restrict the bot to your homeserver's users.
 
 If you need **to undo or tweak these security improvements**, you can change your `vars.yml` file to:
 
@@ -694,8 +824,7 @@ The old Python-based [mautrix-signal](https://github.com/mautrix/signal) bridge
 
 It seems like the path forward is to switch to the new mautrix-signal bridge written in Golang, which we did thanks to [PR #3031](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3041) by [Pierre 'McFly' Marty](https://github.com/pm-McFly).
 
-The playbook should **automatically migrate your mautrix-signal installation to the new bridge code**.
-You will **need to relink all your devices** to continue your bridged conversations.
+The playbook should **automatically migrate your mautrix-signal installation to the new bridge code**. You will **need to relink all your devices** to continue your bridged conversations.
 
 
 # 2023-10-23
@@ -706,8 +835,7 @@ You will **need to relink all your devices** to continue your bridged conversati
 
 We generally try to stick to the default configuration for Synapse (and all other components), unless these defaults seem wrong or harmful. One such previous case from a few months ago was us [Enabling `forget_rooms_on_leave` by default for Synapse](#enabling-forget_rooms_on_leave-by-default-for-synapse) - the default value was making Synapse more wasteful of resources by default.
 
-Today, we're going against upstream defaults again and flipping the `allow_public_rooms_over_federation` configuration option to `true`.
-This way, public rooms on your server will be made discoverable by others via federation, using the [`GET /_matrix/federation/v1/publicRooms` of the Server-Server API](https://spec.matrix.org/v1.8/server-server-api/#get_matrixfederationv1publicrooms).
+Today, we're going against upstream defaults again and flipping the `allow_public_rooms_over_federation` configuration option to `true`. This way, public rooms on your server will be made discoverable by others via federation, using the [`GET /_matrix/federation/v1/publicRooms` of the Server-Server API](https://spec.matrix.org/v1.8/server-server-api/#get_matrixfederationv1publicrooms).
 
 The upstream Synapse default is `false` (disabled), so that public rooms are not exposed for other servers to discover (learn about their existence). Nevertheless, even if these rooms are not exposed (listed) for discovery, they are **still joinable** by anyone who knows their address or is invited to the room by an existing member.
 
@@ -725,7 +853,7 @@ Here are **actions you may wish to take** as a result of this change:
 
 - (recommended) embrace the new default. If your Matrix server is federating, your public rooms have always been joinable across federation anyway. Exposing the list of public rooms does no harm and more-so does good by contributing to the usefulness of the Matrix network by facilitating room discovery.
 
-- (switch to a better way of doings things on your semi-private server) The problem that the Synapse team appears to have solved by flipping the `allow_public_rooms_over_federation` default in Synapse v1.7.0 seems to for "mostly private" servers, which federate and have a bunch of rooms made public (and published in their room directory) in an effort to allow people on the same homeserver to easily find and join them (self-onboarding). With the introduction of Matrix Spaces, you can reorganize your flow around spaces - you can auto-join your users to a Matrix Space (via Synapse's `auto_join_rooms` setting - controlled by our `matrix_synapse_auto_join_rooms` variable), then add a bunch of rooms to the space and make them joinable by people belonging to the space. That is to say, do not make rooms public and do not publish them to the room directory unless they are really public. Instead, use other mechanisms for semi-public rooms or private rooms. One alternative is to stick to what you're doing (public rooms published to your rooms directory) but having a `m.federate: true` flag set during creation (clients like Element have a nice UI checkbox for this) to explicitly disable federation for them.
+- (switch to a better way of doings things on your semi-private server) The problem that the Synapse team appears to have solved by flipping the `allow_public_rooms_over_federation` default in Synapse v1.7.0 seems to for "mostly private" servers, which federate and have a bunch of rooms made public (and published in their room directory) in an effort to allow people on the same homeserver to easily find and join them (self-onboarding). With the introduction of Matrix Spaces, you can reorganize your flow around spaces - you can auto-join your users to a Matrix Space (via Synapse's `auto_join_rooms` setting - controlled by our `matrix_synapse_auto_join_rooms` variable), then add a bunch of rooms to the space and make them joinable by people belonging to the space. That is to say, do not make rooms public and do not publish them to the room directory unless they are really public. Instead, use other mechanisms for semi-public rooms or private rooms. One alternative is to stick to what you're doing (public rooms published to your rooms directory) but having a `m.federate: true` flag set during creation (clients like Element Web have a nice UI checkbox for this) to explicitly disable federation for them.
 
 - (keeping the old behavior) if you wish to keep doing what you're doing (keeping your Matrix server federating, but hiding its public rooms list), add `matrix_synapse_allow_public_rooms_over_federation: false` to your `vars.yml` configuration. This restores the old behavior. You may also consider [disabling federation](docs/configuring-playbook-federation.md#disabling-federation) completely instead of relying on security-by-obscurity measures.
 
@@ -745,11 +873,11 @@ People who [enable load-balancing with Synapse workers](docs/configuring-playboo
 
 # 2023-08-31
 
-## SchildiChat support
+## SchildiChat Web support
 
-Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the [SchildiChat](https://github.com/SchildiChat/schildichat-desktop) client.
+Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client.
 
-See our [Configuring SchildiChat](docs/configuring-playbook-client-schildichat.md) documentation to get started.
+See our [Configuring SchildiChat Web](docs/configuring-playbook-client-schildichat-web.md) documentation to get started.
 
 
 # 2023-08-23
@@ -793,8 +921,7 @@ To learn more see our [Storing Matrix media files using matrix-media-repo](docs/
 
 ## Enabling `forget_rooms_on_leave` by default for Synapse
 
-With the [Synapse v1.84.0 update](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2698), we've also **changed the default value** of the `forget_rooms_on_leave` setting of Synapse to a value of `true`.
-This way, **when you leave a room, Synapse will now forget it automatically**.
+With the [Synapse v1.84.0 update](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2698), we've also **changed the default value** of the `forget_rooms_on_leave` setting of Synapse to a value of `true`. This way, **when you leave a room, Synapse will now forget it automatically**.
 
 The upstream Synapse default is `false` (disabled), so that you must forget rooms manually after leaving.
 
@@ -876,7 +1003,7 @@ Thanks to [Benjamin Kampmann](https://github.com/gnunicorn) for [getting it star
 
 The upcoming Element X clients ([Element X iOS](https://github.com/vector-im/element-x-ios) and [Element X Android](https://github.com/vector-im/element-x-android)) require the `sliding-sync` proxy to do their job. **These clients are still in beta** (especially Element X Android, which requires manual compilation to get it working with a non-`matrix.org` homeseserver). Playbook users can now easily give these clients a try and help test them thanks to us having `sliding-sync` support.
 
-To get started, see our [Setting up Sliding Sync proxy](docs/configuring-playbook-sliding-sync-proxy.md) documentation page.
+To get started, see our [Setting up the Sliding Sync proxy](docs/configuring-playbook-sliding-sync-proxy.md) documentation page.
 
 
 # 2023-03-02
@@ -954,8 +1081,7 @@ See the [Traefik managed by the playbook](docs/configuring-playbook-own-webserve
 
 This playbook manages many different services. All these services were initially integrated with `matrix-nginx-proxy`.
 
-While we migrate all these components to have native Traefik support, some still go through nginx internally (Traefik -> local `matrix-nginx-proxy` -> component).
-As time goes on, internal reliance on `matrix-nginx-proxy` will gradually decrease until it's completely removed.
+While we migrate all these components to have native Traefik support, some still go through nginx internally (Traefik -> local `matrix-nginx-proxy` -> component). As time goes on, internal reliance on `matrix-nginx-proxy` will gradually decrease until it's completely removed.
 
 ### How do I remain on matrix-nginx-proxy?
 
@@ -1040,8 +1166,7 @@ You need to **update your roles** (`just roles` or `make roles`) regardless of w
 
 ### Motivation for redoing our reverse-proxy setup
 
-The playbook has supported various reverse-proxy setups for a long time.
-We have various configuration variables (`matrix_nginx_proxy_enabled`, various `_host_bind_port` variables, etc.) which allow the playbook to adapt to these different setups. The whole situation was messy though - hard to figure out and with lots of variables to toggle to make things work as you'd expect - huge **operational complexity**.
+The playbook has supported various reverse-proxy setups for a long time. We have various configuration variables (`matrix_nginx_proxy_enabled`, various `_host_bind_port` variables, etc.) which allow the playbook to adapt to these different setups. The whole situation was messy though - hard to figure out and with lots of variables to toggle to make things work as you'd expect - huge **operational complexity**.
 
 We love containers, proven by the fact that **everything** that this playbook manages runs in a container. Yet, we weren't allowing people to easily host other web-exposed containers alongside Matrix services on the same server. We were using `matrix-nginx-proxy` (our integrated [nginx](https://nginx.org/) server), which was handling web-exposure and SSL termination for our own services, but we **weren't helping you with all your other containers**.
 
@@ -1056,7 +1181,7 @@ Others still, wanted to run Matrix locally (no SSL certificates), regardless of
 
 Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations.
 
-When using `matrix-nginx-proxy` as is, we still had another problem - one of **internal playbook complexity**. Too many services need to be web-exposed (port 80/443, SSL certificates). Because of this, they all had to integrate with the `matrix-nginx-proxy` role. Tens of different roles explicitly integrating with `matrix-nginx-proxy` is not what we call clean. The `matrix-nginx-proxy` role contains variables for many of these roles (yikes). Other roles were more decoupled from it and were injecting configuration into `matrix-nginx-proxy` at runtime - see all the `inject_into_nginx_proxy.yml` task files in this playbook (more decoupled, but still.. yikes).
+When using `matrix-nginx-proxy` as is, we still had another problem - one of **internal playbook complexity**. Too many services need to be web-exposed (port 80/443, SSL certificates). Because of this, they all had to integrate with the `matrix-nginx-proxy` role. Tens of different roles explicitly integrating with `matrix-nginx-proxy` is not what we call clean. The `matrix-nginx-proxy` role contains variables for many of these roles (yikes). Other roles were more decoupled from it and were injecting configuration into `matrix-nginx-proxy` at runtime - see all the `inject_into_nginx_proxy.yml` task files in this playbook (more decoupled, but still… yikes).
 
 The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks:
 
@@ -1110,11 +1235,10 @@ Switching to Traefik will obtain new SSL certificates from Let's Encrypt (stored
 
 Treafik directly reverse-proxies to **some** services right now, but for most other services it goes through `matrix-nginx-proxy` (e.g. Traefik -> `matrix-nginx-proxy` -> [Ntfy](docs/configuring-playbook-ntfy.md)). So, even if you opt into Traefik, you'll still see `matrix-nginx-proxy` being installed in local-only mode. This will improve with time.
 
-Some services (like [Coturn](docs/configuring-playbook-turn.md) and [Postmoogle](docs/configuring-playbook-bot-postmoogle.md)) cannot be reverse-proxied to directly from Traefik, so they require direct access to SSL certificate files extracted out of Traefik. The playbook does this automatically thanks to a new [com.devture.ansible.role.traefik_certs_dumper](https://github.com/devture/com.devture.ansible.role.traefik_certs_dumper) role utilizing the [traefik-certs-dumper](https://github.com/ldez/traefik-certs-dumper) tool.
+Some services (like [coturn](docs/configuring-playbook-turn.md) and [Postmoogle](docs/configuring-playbook-bridge-postmoogle.md)) cannot be reverse-proxied to directly from Traefik, so they require direct access to SSL certificate files extracted out of Traefik. The playbook does this automatically thanks to a new [com.devture.ansible.role.traefik_certs_dumper](https://github.com/devture/com.devture.ansible.role.traefik_certs_dumper) role utilizing the [traefik-certs-dumper](https://github.com/ldez/traefik-certs-dumper) tool.
 
 Our Traefik setup mostly works, but certain esoteric features may not work. If you have a default setup, we expect you to have a good experience.
 
-
 ### Where we're going in the near future?
 
 The `matrix-nginx-proxy` role is quite messy. It manages both nginx and Certbot and its certificate renewal scripts and timers. It generates configuration even when the role is disabled (weird). Although it doesn't directly reach into variables from other roles, it has explicit awareness of various other services that it reverse-proxies to (`roles/custom/matrix-nginx-proxy/templates/nginx/conf.d/matrix-ntfy.conf.j2`, etc.). We'd like to clean this up. The only way is probably to just get rid of the whole thing at some point.
@@ -1147,7 +1271,6 @@ Thanks to [Jakob S.](https://github.com/jakicoll) ([zakk gGmbH](https://github.c
 
 Additional details are available in the [Authenticate using Matrix OpenID (Auth-Type 'matrix')](docs/configuring-playbook-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix).
 
-
 ## Draupnir moderation tool (bot) support
 
 Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (bot). Draupnir is a fork of [Mjolnir](docs/configuring-playbook-bot-mjolnir.md) (which the playbook has supported for a long time) maintained by Mjolnir's former lead developer.
@@ -1172,31 +1295,29 @@ Other roles which aren't strictly related to Matrix are likely to follow this fa
 
 # 2023-01-26
 
-## Coturn can now use host-networking
+## coturn can now use host-networking
 
-Large Coturn deployments (with a huge range of ports specified via `matrix_coturn_turn_udp_min_port` and `matrix_coturn_turn_udp_max_port`) experience a huge slowdown with how Docker publishes all these ports (setting up firewall forwarding rules), which leads to a very slow Coturn service startup and shutdown.
+Large coturn deployments (with a huge range of ports specified via `matrix_coturn_turn_udp_min_port` and `matrix_coturn_turn_udp_max_port`) experience a huge slowdown with how Docker publishes all these ports (setting up firewall forwarding rules), which leads to a very slow coturn service startup and shutdown.
 
-Such deployments don't need to run Coturn within a private container network anymore. Coturn can now run with host-networking by using configuration like this:
+Such deployments don't need to run coturn within a private container network anymore. coturn can now run with host-networking by using configuration like this:
 
 ```yaml
 matrix_coturn_container_network: host
 ```
 
-With such a configuration, **Docker no longer needs to configure thousands of firewall forwarding rules** each time Coturn starts and stops.
-This, however, means that **you will need to ensure these ports are open** in your firewall yourself.
+With such a configuration, **Docker no longer needs to configure thousands of firewall forwarding rules** each time coturn starts and stops. This, however, means that **you will need to ensure these ports are open** in your firewall yourself.
 
-Thanks to us [tightening Coturn security](#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues), running Coturn with host-networking should be safe and not expose neither other services running on the host, nor other services running on the local network.
+Thanks to us [tightening coturn security](#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues), running coturn with host-networking should be safe and not expose neither other services running on the host, nor other services running on the local network.
 
+## (Backward Compatibility) Tightening coturn security can lead to connectivity issues
 
-## (Backward Compatibility) Tightening Coturn security can lead to connectivity issues
+**TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default coturn blocklists. They may need to override `matrix_coturn_denied_peer_ips` and remove some IP ranges from it.
 
-**TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default Coturn blocklists. They may need to override `matrix_coturn_denied_peer_ips` and remove some IP ranges from it.
+Inspired by [this security article](https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-access-control-protection/), we've decided to make use of coturn's `denied-peer-ip` functionality to prevent relaying network traffic to certain private IP subnets. This ensures that your coturn server won't accidentally try to forward traffic to certain services running on your local networks. We run coturn in a container and in a private container network by default, which should prevent such access anyway, but having additional block layers in place is better.
 
-Inspired by [this security article](https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-access-control-protection/), we've decided to make use of Coturn's `denied-peer-ip` functionality to prevent relaying network traffic to certain private IP subnets. This ensures that your Coturn server won't accidentally try to forward traffic to certain services running on your local networks. We run Coturn in a container and in a private container network by default, which should prevent such access anyway, but having additional block layers in place is better.
+If you access your Matrix server from a local network and need coturn to relay to private IP addresses, you may observe that relaying is now blocked due to our new default `denied-peer-ip` lists (specified in `matrix_coturn_denied_peer_ips`). If you experience such connectivity problems, consider overriding this setting in your `vars.yml` file and removing certain networks from it.
 
-If you access your Matrix server from a local network and need Coturn to relay to private IP addresses, you may observe that relaying is now blocked due to our new default `denied-peer-ip` lists (specified in `matrix_coturn_denied_peer_ips`). If you experience such connectivity problems, consider overriding this setting in your `vars.yml` file and removing certain networks from it.
-
-We've also added `no-multicast-peers` to the default Coturn configuration, but we don't expect this to cause trouble for most people.
+We've also added `no-multicast-peers` to the default coturn configuration, but we don't expect this to cause trouble for most people.
 
 
 # 2023-01-21
@@ -1218,8 +1339,7 @@ Other roles which aren't strictly related to Matrix are likely to follow this fa
 
 ## Support for running commands via just
 
-We've previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers `ansible-galaxy`, see [Makefile](Makefile)).
-Our `Makefile` is still around and you can still run these commands.
+We've previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers `ansible-galaxy`, see [Makefile](Makefile)). Our `Makefile` is still around and you can still run these commands.
 
 In addition, we've added support for running commands via [just](https://github.com/casey/just) - a more modern command-runner alternative to `make`. Instead of `make roles`, you can now run `just roles` to accomplish the same.
 
@@ -1230,7 +1350,7 @@ Our [justfile](justfile) already defines some additional helpful **shortcut** co
 - `just run-tags install-mautrix-slack,start` - to run specific playbook tags
 - `just start-all` - (re-)starts all services
 - `just stop-group postgres` - to stop only the Postgres service
-- `just register-user john secret-password yes` - registers a `john` user with the `secret-password` password and admin access (admin = `yes`)
+- `just register-user alice secret-password yes` - registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)
 
 Additional helpful commands and shortcuts may be defined in the future.
 
@@ -1279,15 +1399,13 @@ The new role is an upgraded version of the old `matrix-postgres` role with these
 
 You'll need to run `make roles` to install the new role. You would also need to rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix.
 
-Note: the systemd service still remains the same - `matrix-postgres.service`. Your data will still be in `/matrix/postgres`, etc.
-Postgres-related scripts will be moved to `/matrix/postgres/bin` (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`, etc). Also see [The playbook no longer installs scripts in /usr/local/bin](#the-playbook-no-longer-installs-scripts-in-usrlocalbin).
+Note: the systemd service still remains the same - `matrix-postgres.service`. Your data will still be in `/matrix/postgres`, etc. Postgres-related scripts will be moved to `/matrix/postgres/bin` (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`, etc). Also see [The playbook no longer installs scripts in /usr/local/bin](#the-playbook-no-longer-installs-scripts-in-usrlocalbin).
 
 ## The playbook no longer installs scripts to /usr/local/bin
 
 The locations of various scripts installed by the playbook have changed.
 
-The playbook no longer contaminates your `/usr/local/bin` directory.
-All scripts installed by the playbook now live in `bin/` directories under `/matrix`. Some examples are below:
+The playbook no longer contaminates your `/usr/local/bin` directory. All scripts installed by the playbook now live in `bin/` directories under `/matrix`. Some examples are below:
 
 - `/usr/local/bin/matrix-remove-all` -> `/matrix/bin/remove-all`
 - `/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`
@@ -1301,8 +1419,7 @@ All scripts installed by the playbook now live in `bin/` directories under `/mat
 
 **TLDR**: the playbook is 2x faster for running `--tags=setup-all` (and various other tags). It also has new `--tags=install-*` tags (like `--tags=install-all`), which skip uninstallation tasks and bring an additional 2.5x speedup. In total, the playbook can maintain your server 5 times faster.
 
-Our [etke.cc managed Matrix hosting service](https://etke.cc) runs maintenance against hundreds of servers, so the playbook being fast means a lot.
-The [etke.cc Ansible playbook](https://github.com/etkecc/ansible) (which is an extension of this one) is growing to support more and more services (besides just Matrix), so the Matrix playbook being leaner prevents runtimes from becoming too slow and improves the customer experience.
+Our [etke.cc managed Matrix hosting service](https://etke.cc) runs maintenance against hundreds of servers, so the playbook being fast means a lot. The [etke.cc Ansible playbook](https://github.com/etkecc/ansible) (which is an extension of this one) is growing to support more and more services (besides just Matrix), so the Matrix playbook being leaner prevents runtimes from becoming too slow and improves the customer experience.
 
 Even when running `ansible-playbook` manually (as most of us here do), it's beneficial not to waste time and CPU resources.
 
@@ -1310,33 +1427,30 @@ Recently, a few large optimizations have been done to this playbook and its exte
 
 1. Replacing Ansible `import_tasks` calls with `include_tasks`, which decreased runtime in half. Using `import_tasks` is slower and causes Ansible to go through and skip way too many tasks (tasks which could have been skipped altogether by not having Ansible include them in the first place). On an experimental VM, **deployment time was decreased from ~530 seconds to ~250 seconds**.
 
-2. Introducing new `install-*` tags (`install-all` and `install-COMPONENT`, e.g. `install-synapse`, `install-bot-postmoogle`), which only run Ansible tasks pertaining to installation, while skipping uninstallation tasks. In most cases, people are maintaining the same setup or they're *adding* new components. Removing components is rare. Running thousands of uninstallation tasks each time is wasteful. On an experimental VM, **deployment time was decreased from ~250 seconds (`--tags=setup-all`) to ~100 seconds (`--tags=install-all`)**.
+2. Introducing new `install-*` tags (`install-all` and `install-COMPONENT`, e.g. `install-synapse`, `install-bot-mjolnir`), which only run Ansible tasks pertaining to installation, while skipping uninstallation tasks. In most cases, people are maintaining the same setup or they're *adding* new components. Removing components is rare. Running thousands of uninstallation tasks each time is wasteful. On an experimental VM, **deployment time was decreased from ~250 seconds (`--tags=setup-all`) to ~100 seconds (`--tags=install-all`)**.
 
 You can still use `--tags=setup-all`. In fact, that's the best way to ensure your server is reconciled with the `vars.yml` configuration.
 
-If you know you haven't uninstalled any services since the last time you ran the playbook, you could run `--tags=install-all` instead and benefit from quicker runtimes.
-It should be noted that a service may become "eligible for uninstallation" even if your `vars.yml` file remains the same. In rare cases, we toggle services from being auto-installed to being optional, like we did on the 17th of March 2022 when we made [ma1sd not get installed by default](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/CHANGELOG.md#compatibility-break-ma1sd-identity-server-no-longer-installed-by-default). In such rare cases, you'd also need to run `--tags=setup-all`.
+If you know you haven't uninstalled any services since the last time you ran the playbook, you could run `--tags=install-all` instead and benefit from quicker runtimes. It should be noted that a service may become "eligible for uninstallation" even if your `vars.yml` file remains the same. In rare cases, we toggle services from being auto-installed to being optional, like we did on the 17th of March 2022 when we made [ma1sd not get installed by default](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/CHANGELOG.md#compatibility-break-ma1sd-identity-server-no-longer-installed-by-default). In such rare cases, you'd also need to run `--tags=setup-all`.
 
 
 # 2022-11-22
 
 # Automatic `matrix_architecture` determination
 
-From now on, the playbook automatically determines your server's architecture and sets the `matrix_architecture` variable accordingly.
-You no longer need to set this variable manually in your `vars.yml` file.
+From now on, the playbook automatically determines your server's architecture and sets the `matrix_architecture` variable accordingly. You no longer need to set this variable manually in your `vars.yml` file.
 
 # Docker and the Docker SDK for Python are now installed via external roles
 
 We're continuing our effort to make [the playbook use external roles for some things](#the-playbook-now-uses-external-roles-for-some-things), so as to avoid doing everything ourselves and to facilitate code re-use.
 
-Docker will now be installed on the server via the [geerlingguy.docker](https://github.com/geerlingguy/ansible-role-docker) Ansible role.
-If you'd like to manage the Docker installation yourself, you can disable the playbook's installation of Docker by setting `matrix_playbook_docker_installation_enabled: false`.
+Docker will now be installed on the server via the [geerlingguy.docker](https://github.com/geerlingguy/ansible-role-docker) Ansible role. If you'd like to manage the Docker installation yourself, you can disable the playbook's installation of Docker by setting `matrix_playbook_docker_installation_enabled: false`.
 
 The Docker SDK for Python (named `docker-python`, `python-docker`, etc. on the different platforms) is now also installed by another role ([com.devture.ansible.role.docker_sdk_for_python](https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python)). To disable this role and install the necessary tools yourself, use `devture_docker_sdk_for_python_installation_enabled: false`.
 
 If you're hitting issues with Docker installation or Docker SDK for Python installation, consider reporting bugs or contributing to these other projects.
 
-These additional roles are downloaded into the playbook directory (to `roles/galaxy`) via an `ansible-galaxy ..` command. `make roles` is an easy shortcut for invoking the `ansible-galaxy` command to download these roles.
+These additional roles are downloaded into the playbook directory (to `roles/galaxy`) via an `ansible-galaxy …` command. `make roles` is an easy shortcut for invoking the `ansible-galaxy` command to download these roles.
 
 
 # 2022-11-20
@@ -1349,13 +1463,11 @@ These additional roles are downloaded into the playbook directory (to `roles/gal
 
 Previously, `matrix-nginx-proxy` forwarded requests to Synapse directly. When Synapse is running in worker mode, the reverse-proxying configuration is more complicated (different requests need to go to different Synapse worker processes). `matrix-nginx-proxy` had configuration for sending each URL endpoint to the correct Synapse worker responsible for handling it. However, sometimes people like to disable `matrix-nginx-proxy` (for whatever reason) as detailed in [Using your own webserver, instead of this playbook's nginx proxy](docs/configuring-playbook-own-webserver.md).
 
-Because `matrix-nginx-proxy` was so central to request forwarding, when it was disabled and Synapse was running with workers enabled, there was nothing which could forward requests to the correct place anymore.. which caused [problems such as this one affecting Dimension](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2090).
+Because `matrix-nginx-proxy` was so central to request forwarding, when it was disabled and Synapse was running with workers enabled, there was nothing which could forward requests to the correct place anymore… which caused [problems such as this one affecting Dimension](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2090).
 
 ### Solution
 
-From now on, `matrix-nginx-proxy` is relieved of its function of reverse-proxying to Synapse and its various worker processes.
-This role is now handled by the new `matrix-synapse-reverse-proxy-companion` nginx service and works even if `matrix-nginx-proxy` is disabled.
-The purpose of the new `matrix-synapse-reverse-proxy-companion` service is to:
+From now on, `matrix-nginx-proxy` is relieved of its function of reverse-proxying to Synapse and its various worker processes. This role is now handled by the new `matrix-synapse-reverse-proxy-companion` nginx service and works even if `matrix-nginx-proxy` is disabled. The purpose of the new `matrix-synapse-reverse-proxy-companion` service is to:
 
 - serve as a companion to Synapse and know how to reverse-proxy to Synapse correctly (no matter if workers are enabled or not)
 
@@ -1367,8 +1479,7 @@ The purpose of the new `matrix-synapse-reverse-proxy-companion` service is to:
 
 - allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is disabled
 
-`matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. All traffic goes through it before reaching any of the services.
-It's just that now the Synapse traffic is routed through `matrix-synapse-reverse-proxy-companion` like this:
+`matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. All traffic goes through it before reaching any of the services. It's just that now the Synapse traffic is routed through `matrix-synapse-reverse-proxy-companion` like this:
 
 (`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> (`matrix-synapse` or some Synapse worker)).
 
@@ -1399,7 +1510,7 @@ If you've already got both Etherpad and Dimension in use you could:
 
 - **either** keep hosting Etherpad under the Dimension domain by adding `etherpad_mode: dimension` to your `vars.yml` file. All your existing room widgets will continue working at the same URLs and no other changes will be necessary.
 
-- **or**, you could change to hosting Etherpad separately on `etherpad.example.com`. You will need to [configure a DNS record](docs/configuring-dns.md) for this new domain. You will also need to reconfigure Dimension to use the new pad URLs (`https://etherpad.example.com/...`) going forward (refer to our [configuring Etherpad documentation](docs/configuring-playbook-etherpad.md)). All your existing room widgets (which still use `https://dimension.example.com/etherpad/...`) will break as Etherpad is not hosted there anymore. You will need to re-add them or to consider not using `standalone` mode
+- **or**, you could change to hosting Etherpad separately on `etherpad.example.com`. You will need to [configure a DNS record](docs/configuring-dns.md) for this new domain. You will also need to reconfigure Dimension to use the new pad URLs (`https://etherpad.example.com/…`) going forward (refer to our [configuring Etherpad documentation](docs/configuring-playbook-etherpad.md)). All your existing room widgets (which still use `https://dimension.example.com/etherpad/…`) will break as Etherpad is not hosted there anymore. You will need to re-add them or to consider not using `standalone` mode
 
 
 # 2022-11-04
@@ -1435,7 +1546,6 @@ This is not just for initial installations. Users with existing files (stored in
 
 To get started, see our [Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3-storage-provider.md) documentation.
 
-
 ## Synapse container image customization support
 
 We now support customizing the Synapse container image by adding additional build steps to its [`Dockerfile`](https://docs.docker.com/engine/reference/builder/).
@@ -1464,7 +1574,7 @@ With the new Synapse-customization feature in the playbook, we use the original
 
 Thanks to [@TheOneWithTheBraid](https://github.com/TheOneWithTheBraid), we now support installing [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) - a proxy which handles Matrix registration requests and forwards them to LDAP.
 
-See our [Setting up the ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started.
+See our [Setting up matrix-ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started.
 
 
 # 2022-09-15
@@ -1503,47 +1613,39 @@ matrix_synapse_workers_stream_writer_presence_stream_workers_count: 1
 
 ### Multiple federation sender workers support
 
-Until now, we only supported a single `federation_sender` worker (`matrix_synapse_workers_federation_sender_workers_count` could either be `0` or `1`).
-From now on, you can have as many as you want to help with your federation traffic.
+Until now, we only supported a single `federation_sender` worker (`matrix_synapse_workers_federation_sender_workers_count` could either be `0` or `1`). From now on, you can have as many as you want to help with your federation traffic.
 
 ### Multiple pusher workers support
 
-Until now, we only supported a single `pusher` worker (`matrix_synapse_workers_pusher_workers_count` could either be `0` or `1`).
-From now on, you can have as many as you want to help with pushing notifications out.
+Until now, we only supported a single `pusher` worker (`matrix_synapse_workers_pusher_workers_count` could either be `0` or `1`). From now on, you can have as many as you want to help with pushing notifications out.
 
 ### Background tasks can run on a worker
 
 From now on, you can put [background task processing on a worker](https://matrix-org.github.io/synapse/latest/workers.html#background-tasks).
 
-With `matrix_synapse_workers_preset: one-of-each`, you'll get one `background` worker automatically.
-You can also control the `background` workers count with `matrix_synapse_workers_background_workers_count`. Only  `0` or `1` workers of this type are supported by Synapse.
+With `matrix_synapse_workers_preset: one-of-each`, you'll get one `background` worker automatically. You can also control the `background` workers count with `matrix_synapse_workers_background_workers_count`. Only  `0` or `1` workers of this type are supported by Synapse.
 
 ### Appservice worker support is back
 
 We previously had an `appservice` worker type, which [Synapse deprecated in v1.59.0](https://github.com/element-hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-synapseappappservice-and-synapseappuser_dir-worker-application-types). So did we, at the time.
 
-The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of talking to Application Services.
-From now on, we have support for this.
+The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of talking to Application Services. From now on, we have support for this.
 
-With `matrix_synapse_workers_preset: one-of-each`, you'll get one `appservice` worker automatically.
-You can also control the `appservice` workers count with `matrix_synapse_workers_appservice_workers_count`. Only  `0` or `1` workers of this type are supported by Synapse.
+With `matrix_synapse_workers_preset: one-of-each`, you'll get one `appservice` worker automatically. You can also control the `appservice` workers count with `matrix_synapse_workers_appservice_workers_count`. Only  `0` or `1` workers of this type are supported by Synapse.
 
 ### User Directory worker support is back
 
 We previously had a `user_dir` worker type, which [Synapse deprecated in v1.59.0](https://github.com/element-hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-synapseappappservice-and-synapseappuser_dir-worker-application-types). So did we, at the time.
 
-The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of serving the user directory.
-From now on, we have support for this.
+The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of serving the user directory. From now on, we have support for this.
 
-With `matrix_synapse_workers_preset: one-of-each`, you'll get one `user_dir` worker automatically.
-You can also control the `user_dir` workers count with `matrix_synapse_workers_user_dir_workers_count`. Only  `0` or `1` workers of this type are supported by Synapse.
+With `matrix_synapse_workers_preset: one-of-each`, you'll get one `user_dir` worker automatically. You can also control the `user_dir` workers count with `matrix_synapse_workers_user_dir_workers_count`. Only  `0` or `1` workers of this type are supported by Synapse.
 
 ### Using more than 1 media repository worker is now more reliable
 
 With `matrix_synapse_workers_preset: one-of-each`, we only launch one `media_repository` worker.
 
-If you've been configuring `matrix_synapse_workers_media_repository_workers_count` manually, you may have increased that to more workers.
-When multiple media repository workers are in use, background tasks related to the media repository must always be configured to run on a single `media_repository` worker via `media_instance_running_background_jobs`. Until now, we weren't doing this correctly, but we now are.
+If you've been configuring `matrix_synapse_workers_media_repository_workers_count` manually, you may have increased that to more workers. When multiple media repository workers are in use, background tasks related to the media repository must always be configured to run on a single `media_repository` worker via `media_instance_running_background_jobs`. Until now, we weren't doing this correctly, but we now are.
 
 ### Potential Backward Incompatibilities after these Synapse worker changes
 
@@ -1564,16 +1666,16 @@ Below we'll discuss **potential backward incompatibilities**.
 
 Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now set up [Cactus Comments](https://cactus.chat) - federated comment system for the web based on Matrix.
 
-See our [Setting up a Cactus Comments server](docs/configuring-playbook-cactus-comments.md) documentation to get started.
+See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-comments.md) documentation to get started.
 
 
 # 2022-08-23
 
 ## Postmoogle email bridge support
 
-Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the new [Postmoogle](https://github.com/etkecc/postmoogle) email bridge/bot. Postmoogle is like the [email2matrix bridge](https://github.com/devture/email2matrix) (also [already supported by the playbook](docs/configuring-playbook-email2matrix.md)), but more capable and with the intention to soon support *sending* emails, not just receiving.
+Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the new [Postmoogle](https://github.com/etkecc/postmoogle) email bridge. Postmoogle is like the [email2matrix bridge](https://github.com/devture/email2matrix) (also [already supported by the playbook](docs/configuring-playbook-email2matrix.md)), but more capable and with the intention to soon support *sending* emails, not just receiving.
 
-See our [Setting up Postmoogle email bridging](docs/configuring-playbook-bot-postmoogle.md) documentation to get started.
+See our [Setting up Postmoogle email bridging](docs/configuring-playbook-bridge-postmoogle.md) documentation to get started.
 
 
 # 2022-08-10
@@ -1635,7 +1737,7 @@ See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) documentati
 
 ## mx-puppet-skype removal
 
-The playbook no longer includes the [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge, because it has been broken and unmaintaned for a long time. Users that have `matrix_mx_puppet_skype_enabled` in their configuration files will encounter an error when running the playbook until they remove references to this bridge from their configuration.
+The playbook no longer includes the [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge, because it has been broken and unmaintained for a long time. Users that have `matrix_mx_puppet_skype_enabled` in their configuration files will encounter an error when running the playbook until they remove references to this bridge from their configuration.
 
 To completely clean up your server from `mx-puppet-skype`'s presence on it:
 
@@ -1649,7 +1751,6 @@ If you still need bridging to [Skype](https://www.skype.com/), consider switchin
 
 If you think this is a mistake and `mx-puppet-skype` works for you (or you get it to work somehow), let us know and we may reconsider this removal.
 
-
 ## signald (0.19.0+) upgrade requires data migration
 
 In [Pull Request #1921](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1921) we upgraded [signald](https://signald.org/) (used by the mautrix-signal bridge) from `v0.18.5` to `v0.20.0`.
@@ -1678,14 +1779,14 @@ See our [Setting up the ntfy push notifications server](docs/configuring-playboo
 
 **TLDR**: we've made extensive **changes to metrics exposure/collection, which concern people using an external Prometheus server**. If you don't know what that is, you don't need to read below.
 
-**Why do major changes to metrics**? Because various services were exposing metrics in different, hacky, ways. Synapse was exposing metrics at `/_synapse/metrics` and `/_synapse-worker-.../metrics` on the `matrix.example.com`. The Hookshot role was **repurposing** the Granana web UI domain (`stats.example.com`) for exposing its metrics on `stats.example.com/hookshot/metrics`, while protecting these routes using Basic Authentication **normally used for Synapse** (`/_synapse/metrics`). Node-exporter and Postgres-exporter roles were advising for more `stats.example.com` usage in manual ways. Each role was doing things differently and mixing variables from other roles. Each metrics endpoint was ending up in a different place, protected by who knows what Basic Authentication credentials (if protected at all).
+**Why do major changes to metrics**? Because various services were exposing metrics in different, hacky, ways. Synapse was exposing metrics at `/_synapse/metrics` and `/_synapse-worker-…/metrics` on the `matrix.example.com`. The Hookshot role was **repurposing** the Granana web UI domain (`stats.example.com`) for exposing its metrics on `stats.example.com/hookshot/metrics`, while protecting these routes using Basic Authentication **normally used for Synapse** (`/_synapse/metrics`). Node-exporter and Postgres-exporter roles were advising for more `stats.example.com` usage in manual ways. Each role was doing things differently and mixing variables from other roles. Each metrics endpoint was ending up in a different place, protected by who knows what Basic Authentication credentials (if protected at all).
 
 **The solution**: a completely revamped way to expose metrics to an external Prometheus server. We are **introducing new `https://matrix.example.com/metrics/*` endpoints**, where various services *can* expose their metrics, for collection by external Prometheus servers. To enable the `/metrics/*` endpoints, use `matrix_nginx_proxy_proxy_matrix_metrics_enabled: true`. There's also a way to protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication). See the `matrix-nginx-proxy` role or our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation for additional variables around `matrix_nginx_proxy_proxy_matrix_metrics_enabled`.
 
 **If you are using the [Hookshot bridge](docs/configuring-playbook-bridge-hookshot.md)**, you may find that:
 1. **Metrics may not be enabled by default anymore**:
-  - If Prometheus is enabled (`prometheus_enabled: true`), then Hookshot metrics will be enabled automatically (`matrix_hookshot_metrics_enabled: true`). These metrics will be collected from the local (in-container) Prometheus over the container network.
-  - **If Prometheus is not enabled** (you are either not using Prometheus or are using an external one), **Hookshot metrics will not be enabled by default anymore**. Feel free to enable them by setting `matrix_hookshot_metrics_enabled: true`. Also, see below.
+    - If Prometheus is enabled (`prometheus_enabled: true`), then Hookshot metrics will be enabled automatically (`matrix_hookshot_metrics_enabled: true`). These metrics will be collected from the local (in-container) Prometheus over the container network.
+    - **If Prometheus is not enabled** (you are either not using Prometheus or are using an external one), **Hookshot metrics will not be enabled by default anymore**. Feel free to enable them by setting `matrix_hookshot_metrics_enabled: true`. Also, see below.
 2. When metrics are meant to be **consumed by an external Prometheus server**, `matrix_hookshot_metrics_proxying_enabled` needs to be set to `true`, so that metrics would be exposed (proxied) "publicly" on `https://matrix.example.com/metrics/hookshot`. To make use of this, you'll also need to enable the new `https://matrix.example.com/metrics/*` endpoints mentioned above, using `matrix_nginx_proxy_proxy_matrix_metrics_enabled`. Learn more in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation.
 3. **We've changed the URL we're exposing Hookshot metrics at** for external Prometheus servers. Until now, you were advised to consume Hookshot metrics from `https://stats.example.com/hookshot/metrics` (working in conjunction with `matrix_nginx_proxy_proxy_synapse_metrics`). From now on, **this no longer works**. As described above, you need to start consuming metrics from `https://matrix.example.com/metrics/hookshot`.
 
@@ -1697,7 +1798,7 @@ See our [Setting up the ntfy push notifications server](docs/configuring-playboo
 
 1. Exposing metrics is now done using `matrix_synapse_metrics_proxying_enabled`, not `matrix_nginx_proxy_proxy_synapse_metrics: true`. You may still need to enable metrics using `matrix_synapse_metrics_enabled: true` before exposing them.
 2. Protecting metrics endpoints using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) is now done in another way. See our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation
-3. If Synapse metrics are exposed, they will be made available at `https://matrix.example.com/metrics/synapse/main-process` or `https://matrix.example.com/metrics/synapse/worker/TYPE-ID` (when workers are enabled), not at `https://matrix.example.com/_synapse/metrics` and `https://matrix.example.com/_synapse-worker-.../metrics`
+3. If Synapse metrics are exposed, they will be made available at `https://matrix.example.com/metrics/synapse/main-process` or `https://matrix.example.com/metrics/synapse/worker/TYPE-ID` (when workers are enabled), not at `https://matrix.example.com/_synapse/metrics` and `https://matrix.example.com/_synapse-worker-…/metrics`
 4. The playbook still generates an `external_prometheus.yml.example` sample file for scraping Synapse from Prometheus as described in [Collecting Synapse worker metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-server), but it's now saved under `/matrix/synapse` (not `/matrix`).
 
 **If you where already using a external Prometheus server** before this change, and you gave a hashed version of the password as a variable, the playbook will now take care of hashing the password for you. Thus, you need to provide the non-hashed version now.
@@ -1708,7 +1809,7 @@ See our [Setting up the ntfy push notifications server](docs/configuring-playboo
 
 Thanks to [CyberShadow](https://github.com/CyberShadow), the playbook can now install the [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) bridge for bridging Matrix to [Skype](https://www.skype.com/).
 
-See our [Setting up Go Skype Bridge](docs/configuring-playbook-bridge-go-skype-bridge.md) documentation to get started.
+See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md) documentation to get started.
 
 The playbook has supported [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridging (see [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md)) since [2020-04-09](#2020-04-09), but `mx-puppet-skype` is reportedly broken.
 
@@ -1757,7 +1858,7 @@ You could then restart services: `ansible-playbook -i inventory/hosts setup.yml
 
 # 2022-04-25
 
-## buscarron bot support
+## Buscarron bot support
 
 Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [the Buscarron bot](https://github.com/etkecc/buscarron). It's a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room
 
@@ -1781,7 +1882,6 @@ Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the
 
 See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md) documentation to get started.
 
-
 ## (Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action
 
 If you're running a worker setup for Synapse (`matrix_synapse_workers_enabled: true`), the [Synapse v1.57 upgrade notes](https://github.com/element-hq/synapse/blob/v1.57.0rc1/docs/upgrade.md#changes-to-database-schema-for-application-services) say that you may need to take special care when upgrading:
@@ -1820,9 +1920,9 @@ The playbook *could* correct these permissions automatically, but that requires
 
 The playbook no longer installs the [ma1sd](https://github.com/ma1uta/ma1sd) identity server by default. The next time you run the playbook, ma1sd will be uninstalled from your server, unless you explicitly enable the ma1sd service (see how below).
 
-The main reason we used to install ma1sd by default in the past was to prevent Element from talking to the `matrix.org` / `vector.im` identity servers, by forcing it to talk to our own self-hosted (but otherwise useless) identity server instead, thus preventing contact list leaks.
+The main reason we used to install ma1sd by default in the past was to prevent Element clients from talking to the `matrix.org` / `vector.im` identity servers, by forcing it to talk to our own self-hosted (but otherwise useless) identity server instead, thus preventing contact list leaks.
 
-Since Element no longer defaults to using a public identity server if another one is not provided, we can stop installing ma1sd.
+Since Element clients no longer default to using a public identity server if another one is not provided, we can stop installing ma1sd.
 
 If you need to install the ma1sd identity server for some reason, you can explicitly enable it by adding this to your `vars.yml` file:
 
@@ -1844,8 +1944,7 @@ To enable this module (and prevent encryption from being used on your homserver)
 
 ## matrix-hookshot bridging support
 
-Thanks to [HarHarLinks](https://github.com/HarHarLinks), the playbook can now install the [matrix-hookshot](https://github.com/Half-Shot/matrix-hookshot) bridge for bridging Matrix to multiple project management services, such as GitHub, GitLab and JIRA.
-See our [Setting up matrix-hookshot](docs/configuring-playbook-bridge-hookshot.md) documentation to get started.
+Thanks to [HarHarLinks](https://github.com/HarHarLinks), the playbook can now install the [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) bridge for bridging Matrix to multiple project management services, such as GitHub, GitLab and JIRA. See our [Setting up matrix-hookshot](docs/configuring-playbook-bridge-hookshot.md) documentation to get started.
 
 
 # 2022-01-31
@@ -1897,7 +1996,6 @@ matrix_homeserver_implementation: dendrite
 
 We're excited to gain support for other homeserver implementations, like [Conduit](https://conduit.rs/), etc!
 
-
 ## Honoroit bot support
 
 Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now help you set up [Honoroit](https://github.com/etkecc/honoroit) - a helpdesk bot.
@@ -1911,7 +2009,7 @@ See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documen
 
 Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports [Cinny](https://cinny.in/) - a new simple, elegant and secure Matrix client.
 
-By default, we still install Element. Still, people who'd like to try Cinny out can now install it via the playbook.
+By default, we still install Element Web. Still, people who'd like to try Cinny out can now install it via the playbook.
 
 Additional details are available in [Setting up Cinny](docs/configuring-playbook-client-cinny.md).
 
@@ -1945,11 +2043,9 @@ Synapse still supports v9.6 (for now), but we're retiring support for it early,
 
 ## Hangouts bridge no longer updated, superseded by a Googlechat bridge
 
-The mautrix-hangouts bridge is no longer receiving updates upstream and is likely to stop working in the future.
-We still retain support for this bridge in the playbook, but you're encouraged to switch away from it.
+The mautrix-hangouts bridge is no longer receiving updates upstream and is likely to stop working in the future. We still retain support for this bridge in the playbook, but you're encouraged to switch away from it.
 
-There's a new [mautrix-googlechat](https://github.com/mautrix/googlechat) bridge that you can [install using the playbook](docs/configuring-playbook-bridge-mautrix-googlechat.md).
-Your **Hangouts bridge data will not be migrated**, however. You need to start fresh with the new bridge.
+There's a new [mautrix-googlechat](https://github.com/mautrix/googlechat) bridge that you can [install using the playbook](docs/configuring-playbook-bridge-mautrix-googlechat.md). Your **Hangouts bridge data will not be migrated**, however. You need to start fresh with the new bridge.
 
 
 # 2021-08-23
@@ -1973,8 +2069,7 @@ This is an optional component for the playbook, so most of our users wouldn't ca
 
 Since this feels like a relatively big (and untested, as of yet) Sygnal change, we're putting up this changelog entry.
 
-The new version is also available for the ARM architecture. It also no longer requires a database anymore.
-If you need to downgrade to the previous version, changing `matrix_sygnal_version` or `matrix_sygnal_docker_image` will not be enough, as we've removed the `database` configuration completely. You'd need to switch to an earlier playbook commit.
+The new version is also available for the ARM architecture. It also no longer requires a database anymore. If you need to downgrade to the previous version, changing `matrix_sygnal_version` or `matrix_sygnal_docker_image` will not be enough, as we've removed the `database` configuration completely. You'd need to switch to an earlier playbook commit.
 
 
 # 2021-05-21
@@ -1983,7 +2078,7 @@ If you need to downgrade to the previous version, changing `matrix_sygnal_versio
 
 Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook now supports [Hydrogen](https://github.com/vector-im/hydrogen-web) - a new lightweight Matrix client with legacy and mobile browser support.
 
-By default, we still install Element, as Hydrogen is still not fully-featured. Still, people who'd like to try Hydrogen out can now install it via the playbook.
+By default, we still install Element Web, as Hydrogen is still not fully-featured. Still, people who'd like to try Hydrogen out can now install it via the playbook.
 
 Additional details are available in [Setting up Hydrogen](docs/configuring-playbook-client-hydrogen.md).
 
@@ -1999,9 +2094,9 @@ Additional details are available in [Setting up Heisenbridge bouncer-style IRC b
 
 # 2021-04-16
 
-## Disabling TLSv1 and TLSv1.1 for Coturn
+## Disabling TLSv1 and TLSv1.1 for coturn
 
-To improve security, we've [removed TLSv1 and TLSv1.1 support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/999) from our default [Coturn](https://github.com/coturn/coturn) configuration.
+To improve security, we've [removed TLSv1 and TLSv1.1 support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/999) from our default [coturn](https://github.com/coturn/coturn) configuration.
 
 If you need to support old clients, you can re-enable both (or whichever one you need) with the following configuration:
 
@@ -2020,7 +2115,6 @@ Thanks to [foxcris](https://github.com/foxcris), the playbook can now make autom
 Additional details are available in [Setting up postgres backup](docs/configuring-playbook-postgres-backup.md).
 
 
-
 # 2021-04-03
 
 ## Mjolnir moderation tool (bot) support
@@ -2038,7 +2132,7 @@ The playbook can now install the [Sygnal](https://github.com/matrix-org/sygnal)
 
 This is only useful to people who develop/build their own Matrix client applications.
 
-Additional details are available in our [Setting up Sygnal](docs/configuring-playbook-sygnal.md) docs.
+Additional details are available in our [Setting up the Sygnal push gateway](docs/configuring-playbook-sygnal.md) docs.
 
 
 # 2021-03-16
@@ -2133,14 +2227,14 @@ To migrate to the new setup, expect a few minutes of downtime, while you follow
 
 1. We believe the steps below are safe and you won't encounter any data loss, but consider [making a Postgres backup](docs/maintenance-postgres.md#backing-up-postgresql) anyway. If you've never backed up Postgres, now would be a good time to try it.
 
-2. Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can use `pwgen -s 64 1` to generate it, or some other tool. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy!
+2. Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can create one with a command like `pwgen -s 64 1`. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy!
 
 3. Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` file, adding a line like this:
-```yaml
-matrix_postgres_connection_password: 'YOUR_POSTGRES_PASSWORD_HERE'
-```
+    ```yaml
+    matrix_postgres_connection_password: 'YOUR_POSTGRES_PASSWORD_HERE'
+    ```
 
-.. where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2.
+… where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2.
 
 4. Stop all services: `ansible-playbook -i inventory/hosts setup.yml --tags=stop`
 5. Log in to the server via SSH. The next commands will be performed there.
@@ -2148,31 +2242,31 @@ matrix_postgres_connection_password: 'YOUR_POSTGRES_PASSWORD_HERE'
 7. Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`
 8. Execute the following query, while making sure to **change the password inside** (**don't forget the ending `;`**):
 
-```sql
-CREATE ROLE matrix LOGIN SUPERUSER PASSWORD 'YOUR_POSTGRES_PASSWORD_HERE';
-```
+    ```sql
+    CREATE ROLE matrix LOGIN SUPERUSER PASSWORD 'YOUR_POSTGRES_PASSWORD_HERE';
+    ```
 
-.. where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2.
+… where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2.
 
 9. Execute the following queries as you see them (no modifications necessary, so you can just **paste them all at once**):
 
-```sql
-CREATE DATABASE matrix OWNER matrix;
+    ```sql
+    CREATE DATABASE matrix OWNER matrix;
 
-ALTER DATABASE postgres OWNER TO matrix;
-ALTER DATABASE template0 OWNER TO matrix;
-ALTER DATABASE template1 OWNER TO matrix;
+    ALTER DATABASE postgres OWNER TO matrix;
+    ALTER DATABASE template0 OWNER TO matrix;
+    ALTER DATABASE template1 OWNER TO matrix;
 
-\c matrix;
+    \c matrix;
 
-ALTER DATABASE homeserver RENAME TO synapse;
+    ALTER DATABASE homeserver RENAME TO synapse;
 
-ALTER ROLE synapse NOSUPERUSER NOCREATEDB NOCREATEROLE;
+    ALTER ROLE synapse NOSUPERUSER NOCREATEDB NOCREATEROLE;
 
-\quit
-```
+    \quit
+    ```
 
-You may need to press *Enter* after pasting the lines above.
+    You may need to press *Enter* after pasting the lines above.
 
 10. Re-run the playbook normally: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`
 
@@ -2203,8 +2297,7 @@ As already mentioned above, you most likely don't need to do anything. If you re
 
 If you're **not running an external Postgres server**, then this bridge either already works on Postgres for you, or you've intentionally kept it back on SQLite with custom configuration (`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) .
 
-Simply remove that custom configuration from your `vars.yml` file (if it's there) and re-run the playbook. It should upgrade you automatically.
-You'll need to send a `login` message to the Facebook bridge bot again.
+Simply remove that custom configuration from your `vars.yml` file (if it's there) and re-run the playbook. It should upgrade you automatically. You'll need to send a `login` message to the Facebook bridge bot again.
 
 Alternatively, [you can stay on SQLite for a little longer](#staying-on-sqlite-for-a-little-longer-temporary-solution).
 
@@ -2347,15 +2440,13 @@ We've removed support for the unmaintained [synapse-janitor](https://github.com/
 
 If you need to clean up or compact your database, consider using the Synapse Admin APIs directly. See our [Synapse maintenance](docs/maintenance-synapse.md) and [Postgres maintenance](docs/maintenance-postgres.md) documentation pages for more details.
 
-
 ## Docker 20.10 is here
 
 (No need to do anything special in relation to this. Just something to keep in mind)
 
 Docker 20.10 got released recently and your server will likely get it the next time you update.
 
-This is the first major Docker update in a long time and it packs a lot of changes.
-Some of them introduced some breakage for us initially (see [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/d08b27784f222effcbce2abf924bf07bbe0893be) and [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/7593d969e316cc0144bce378a5be58c76c2c37ee)), but it should be all good now.
+This is the first major Docker update in a long time and it packs a lot of changes. Some of them introduced some breakage for us initially (see [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/d08b27784f222effcbce2abf924bf07bbe0893be) and [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/7593d969e316cc0144bce378a5be58c76c2c37ee)), but it should be all good now.
 
 
 # 2020-12-08
@@ -2366,8 +2457,7 @@ We've changed some defaults. People running with our default configuration (fede
 
 If you are running an unfederated server (`matrix_synapse_federation_enabled: false`), this may be of interest to you.
 
-When federation is disabled, but ma1sd or Dimension are enabled, we'll now expose the `openid` APIs on the federation port.
-These APIs are necessary for some ma1sd features to work. If you'd like to prevent this, you can: `matrix_synapse_federation_port_openid_resource_required: false`.
+When federation is disabled, but ma1sd or Dimension are enabled, we'll now expose the `openid` APIs on the federation port. These APIs are necessary for some ma1sd features to work. If you'd like to prevent this, you can: `matrix_synapse_federation_port_openid_resource_required: false`.
 
 
 # 2020-11-27
@@ -2421,20 +2511,18 @@ To learn more, follow our [Dynamic DNS docs page](docs/configuring-playbook-dyna
 
 Until now, we used to serve a static page coming from Synapse at `https://matrix.example.com/`. This page was not very useful to anyone.
 
-Since `matrix.example.com` may be accessed by regular users in certain conditions, it's probably better to redirect them to a better place (e.g. to the [Element](docs/configuring-playbook-client-element.md) client).
+Since `matrix.example.com` may be accessed by regular users in certain conditions, it's probably better to redirect them to a better place (e.g. to [Element Web](docs/configuring-playbook-client-element-web.md)).
 
-If Element is installed (`matrix_client_element_enabled: true`, which it is by default), we now redirect people to it, instead of showing them a Synapse static page.
+If Element Web is installed (`matrix_client_element_enabled: true`, which it is by default), we now redirect people to it, instead of showing them a Synapse static page.
 
-If you'd like to control where the redirect goes, use the `matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain` variable.
-To restore the old behavior of not redirecting anywhere and serving the Synapse static page, set it to an empty value (`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain: ""`).
+If you'd like to control where the redirect goes, use the `matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain` variable. To restore the old behavior of not redirecting anywhere and serving the Synapse static page, set it to an empty value (`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain: ""`).
 
 
 # 2020-10-26
 
 ## (Compatibility Break) /_synapse/admin is no longer publicly exposed by default
 
-We used to expose the Synapse Admin APIs publicly (at `https://matrix.example.com/_synapse/admin`).
-These APIs require authentication with a valid access token, so it's not that big a deal to expose them.
+We used to expose the Synapse Admin APIs publicly (at `https://matrix.example.com/_synapse/admin`). These APIs require authentication with a valid access token, so it's not that big a deal to expose them.
 
 However, following [official Synapse's reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints), we're no longer exposing `/_synapse/admin` by default.
 
@@ -2508,7 +2596,7 @@ As per the official announcement, [Riot has been rebraned to Element](https://el
 
 The playbook follows suit. Existing installations have a few options for how to handle this.
 
-See our [Migrating to Element](docs/configuring-playbook-riot-web.md#migrating-to-element) documentation page for more details.
+See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md#migrating-to-element) documentation page for more details.
 
 
 # 2020-07-03
@@ -2586,8 +2674,7 @@ This upgrades matrix-appservice-irc from 0.14.1 to 0.16.0.  Upstream
 made a change to how you define manual mappings.  If you added a
 `mapping` to your configuration, you will need to update it accoring
 to the [upstream
-instructions](https://github.com/matrix-org/matrix-appservice-irc/blob/master/CHANGELOG.md#0150-2020-02-05).
-If you did not include `mappings` in your configuration for IRC, no
+instructions](https://github.com/matrix-org/matrix-appservice-irc/blob/master/CHANGELOG.md#0150-2020-02-05). If you did not include `mappings` in your configuration for IRC, no
 change is necessary.  `mappings` is not part of the default
 configuration.
 
@@ -2629,8 +2716,7 @@ Thanks to [Marcel Partap](https://github.com/eMPee584)'s efforts, the [mxisd](ht
 
 **If you're using the default playbook configuration**, you don't need to do anything -- your mxisd installation will be replaced with ma1sd and all existing data will be migrated automatically the next time you run the playbook.
 
-**If you're doing something more special** (defining custom `matrix_mxisd_*` variables), the playbook will ask you to rename them to `matrix_ma1sd_*`.
-You're also encouraged to test that ma1sd works well for such a more custom setup.
+**If you're doing something more special** (defining custom `matrix_mxisd_*` variables), the playbook will ask you to rename them to `matrix_ma1sd_*`. You're also encouraged to test that ma1sd works well for such a more custom setup.
 
 
 # 2020-03-29
@@ -2655,8 +2741,7 @@ See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to get st
 
 Thanks to [Gergely Horváth](https://github.com/hooger)'s effort, the playbook supports installing to a Raspberry Pi server, for at least some of the services.
 
-Since most ready-made container images do not support that architecture, we achieve this by building images locally on the device itself.
-See our [Self-building documentation page](docs/self-building.md) for how to get started.
+Since most ready-made container images do not support that architecture, we achieve this by building images locally on the device itself. See our [Self-building documentation page](docs/self-building.md) for how to get started.
 
 
 # 2020-02-26
@@ -2676,11 +2761,11 @@ You can now customize the server name string that Riot-web displays in its login
 
 These playbook variables, with these default values, have been added:
 
-```
+```yaml
 matrix_riot_web_default_server_name: "{{ matrix_domain }}"
 ```
 
-The login page previously said "Sign in to your Matrix account on matrix.example.org" (the homeserver's domain name). It will now say "Sign in ... on example.org" (the server name) by default, or "Sign in ... on Our Server" if you set the variable to "Our Server".
+The login page previously said "Sign in to your Matrix account on matrix.example.org" (the homeserver's domain name). It will now say "Sign in … on example.org" (the server name) by default, or "Sign in … on Our Server" if you set the variable to "Our Server".
 
 To support this, the config.json template is changed to use the configuration key `default_server_config` for setting the default HS/IS, and the new configuration key `server_name` is added in there.
 
@@ -2704,7 +2789,7 @@ Still, we might become affected in the future. In any case, it's imminent that S
 
 To avoid future problems, we recommend that you run the following command:
 
-```
+```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=upgrade-postgres --extra-vars='{"postgres_force_upgrade": true}'
 ```
 
@@ -2717,7 +2802,7 @@ It forces a [Postgres database upgrade](docs/maintenance-postgres.md#upgrading-p
 
 Thanks to a contribution from [Björn Marten](https://github.com/tripleawwy) from [netresearch](https://www.netresearch.de/), the playbook can now install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks.
 
-Learn more in [Setting up Appservice Webhooks](docs/configuring-playbook-bridge-appservice-webhooks.md).
+Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-playbook-bridge-appservice-webhooks.md).
 
 
 # 2020-01-12
@@ -2739,8 +2824,7 @@ We have added support for making `matrix-nginx-proxy` not being so invasive, so
 
 The documentation has been updated with a **Method 2**, which might make "own webserver" setup easier in some cases (such as [reverse-proxying using Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/296)).
 
-**Existing users** are not affected by this and **don't need to change anything**.
-The defaults are still the same (`matrix-nginx-proxy` obtaining SSL certificates and doing everything for you automatically).
+**Existing users** are not affected by this and **don't need to change anything**. The defaults are still the same (`matrix-nginx-proxy` obtaining SSL certificates and doing everything for you automatically).
 
 
 # 2019-11-10
@@ -2749,8 +2833,7 @@ The defaults are still the same (`matrix-nginx-proxy` obtaining SSL certificates
 
 As per this [advisory blog post](https://matrix.org/blog/2019/11/09/avoiding-unwelcome-visitors-on-private-matrix-servers), we've decided to change the default publishing rules for the Matrix room directory.
 
-Our general goal is to favor privacy and security when running personal (family & friends) and corporate homeservers.
-Both of these likely benefit from having a more secure default of **not showing the room directory without authentication** and **not publishing the room directory over federation**.
+Our general goal is to favor privacy and security when running personal (family & friends) and corporate homeservers. Both of these likely benefit from having a more secure default of **not showing the room directory without authentication** and **not publishing the room directory over federation**.
 
 As with anything else, these new defaults can be overriden by changing the `matrix_synapse_allow_public_rooms_without_auth` and `matrix_synapse_allow_public_rooms_over_federation` variables, respectively.
 
@@ -2761,12 +2844,9 @@ As with anything else, these new defaults can be overriden by changing the `matr
 
 Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) and [importing](docs/importing-postgres.md) have been improved to add support for multiple databases and roles.
 
-Previously, the playbook would only take care of the `homeserver` database and `synapse` user.
-We now back up and restore all databases and users on the Postgres server.
+Previously, the playbook would only take care of the `homeserver` database and `synapse` user. We now back up and restore all databases and users on the Postgres server.
 
-For now, the playbook only uses that one database (`homeserver`) and that one single user (`synapse`), so it's all the same.
-However, in the future, additional components besides Synapse may also make use the Postgres database server.
-One such example is the [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge, which strongly encourages use of Postgres in its v1.0 release. We are yet to upgrade to it.
+For now, the playbook only uses that one database (`homeserver`) and that one single user (`synapse`), so it's all the same. However, in the future, additional components besides Synapse may also make use the Postgres database server. One such example is the [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge, which strongly encourages use of Postgres in its v1.0 release. We are yet to upgrade to it.
 
 Additionally, Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) now uses gzipped dump files by default, to minimize disk space usage.
 
@@ -2790,9 +2870,7 @@ Its new defaults (which we adopt as well) mean that certain old data will automa
 
 From now on the `trusted_key_servers` setting for Synapse is configurable. It still defaults to `matrix.org` just like it always has, but in a more explicit way now. If you'd like to use another trusted key server, adjust the `matrix_synapse_trusted_key_servers` playbook variable.
 
-Synapse 1.4.0 also changes lots of things related to identity server integration.
-Because Synapse will now by default be responsible for validating email addresses for user accounts, running without an identity server looks more feasible.
-We still [have concerns](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/275/files#r331104117) over disabling the identity server by default, so for now it remains enabled.
+Synapse 1.4.0 also changes lots of things related to identity server integration. Because Synapse will now by default be responsible for validating email addresses for user accounts, running without an identity server looks more feasible. We still [have concerns](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/275/files#r331104117) over disabling the identity server by default, so for now it remains enabled.
 
 
 # 2019-09-09
@@ -2812,8 +2890,7 @@ Learn more in [Setting up Synapse Simple Antispam](docs/configuring-playbook-syn
 
 Similarly to [Extensible Synapse configuration](#extensible-synapse-configuration) (below), Riot-web configuration is also extensible now.
 
-From now on, you can extend/override Riot-web's configuration by making use of the `matrix_riot_web_configuration_extension_json` variable.
-This should be enough for most customization needs.
+From now on, you can extend/override Riot-web's configuration by making use of the `matrix_riot_web_configuration_extension_json` variable. This should be enough for most customization needs.
 
 If you need even more power, you can now also take full control and override `matrix_riot_web_configuration_default` (or `matrix_riot_web_configuration`) directly.
 
@@ -2824,11 +2901,9 @@ Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-web.md).
 
 ## Extensible Synapse configuration
 
-Previously, we had to create custom Ansible variables for each and every Synapse setting.
-This lead to too much effort (and configuration ugliness) to all of Synapse's settings, so naturally, not all features of Synapse could be controlled through the playbook.
+Previously, we had to create custom Ansible variables for each and every Synapse setting. This lead to too much effort (and configuration ugliness) to all of Synapse's settings, so naturally, not all features of Synapse could be controlled through the playbook.
 
-From now on, you can extend/override the Synapse server's configuration by making use of the `matrix_synapse_configuration_extension_yaml` variable.
-This should be enough for most customization needs.
+From now on, you can extend/override the Synapse server's configuration by making use of the `matrix_synapse_configuration_extension_yaml` variable. This should be enough for most customization needs.
 
 If you need even more power, you can now also take full control and override `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`) directly.
 
@@ -2875,7 +2950,6 @@ This greatly reduces the number of log messages that are being logged, leading t
 If you'd like to track down an issue, you [can always increase the logging level as described here](./docs/maintenance-and-troubleshooting.md#increasing-synapse-logging).
 
 
-
 # 2019-07-08
 
 ## Synapse Maintenance docs and synapse-janitor support are available
@@ -2886,13 +2960,11 @@ There's a new documentation page about [Synapse maintenance](./docs/maintenance-
 
 Among other things, if your Postgres database has grown significantly over time, you may wish to [ask the playbook to purge unused data with synapse-janitor](./docs/maintenance-synapse.md#purging-unused-data-with-synapse-janitor) for you.
 
-
 ## (BC Break) Rename run control variables
 
 Some internal playbook control variables have been renamed.
 
-This change **only affects people who run this playbook's roles from another playbook**.
-If you're using this playbook as-is, you're not affected and don't need to do anything.
+This change **only affects people who run this playbook's roles from another playbook**. If you're using this playbook as-is, you're not affected and don't need to do anything.
 
 The following variables have been renamed:
 
@@ -2910,8 +2982,7 @@ The following variables have been renamed:
 
 Following what the official Synapse Docker image is doing ([#5565](https://github.com/matrix-org/synapse/pull/5565)) and what we've been doing for mostly everything installed by this playbook, **Synapse no longer logs to text files** (`/matrix/synapse/run/homeserver.log*`).
 
-From now on, Synapse would only log to console, which goes to systemd's journald.
-To see Synapse's logs, execute: `journalctl -fu matrix-synapse`
+From now on, Synapse would only log to console, which goes to systemd's journald. To see Synapse's logs, execute: `journalctl -fu matrix-synapse`
 
 Because of this, the following variables have become obsolete and were removed:
 
@@ -2939,8 +3010,7 @@ Likewise, data is now also stored in a subdirectory (`/matrix/appservice-discord
 
 The main directory (`/matrix/appservice-discord`) may contain some leftover files (`user-store.db`, `room-store.db`, `config.yaml`, `discord-registration.yaml`, `invite_link`). These are no longer necessary and can be deleted manually.
 
-We're now following the default sample configuration for the Discord bridge.
-If you need to override some values, define them in `matrix_appservice_discord_configuration_extension_yaml`.
+We're now following the default sample configuration for the Discord bridge. If you need to override some values, define them in `matrix_appservice_discord_configuration_extension_yaml`.
 
 
 # 2019-06-24
@@ -2953,8 +3023,7 @@ From now on, the playbook will keep the configuration in sync for you.
 
 This means that if you were making manual changes to the `/matrix/mautrix-whatsapp/config.yaml` or `/matrix/mautrix-whatsapp/registration.yaml` configuration files, those would be lost the next time you run the playbook.
 
-The bridge now stores configuration in a subdirectory (`/matrix/mautrix-whatsapp/config`), so your old configuration remains in the base directory (`/matrix/mautrix-whatsapp`).
-You need to migrate any manual changes over to the new `matrix_mautrix_whatsapp_configuration_extension_yaml` variable, so that the playbook would apply them for you.
+The bridge now stores configuration in a subdirectory (`/matrix/mautrix-whatsapp/config`), so your old configuration remains in the base directory (`/matrix/mautrix-whatsapp`). You need to migrate any manual changes over to the new `matrix_mautrix_whatsapp_configuration_extension_yaml` variable, so that the playbook would apply them for you.
 
 Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-whatsapp/data`). When you run the playbook with an existing database file (`/matrix/mautrix-whatsapp/mautrix-whatsapp.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`).
 
@@ -2977,8 +3046,7 @@ Previously, we asked people to configure bridged IRC servers by extending the br
 
 If you decide to continue using `matrix_appservice_irc_configuration_extension_yaml`, you might be interested to know that `ircService.databaseUri` and a few other keys now have default values in the base configuration (`matrix_appservice_irc_configuration_yaml`). You may wish to stop redefining those keys, unless you really intend to override them. You most likely only need to override `ircService.servers`.
 
-Bridge data (`passkey.pem` and database files) is now also stored in a subdirectory (`/matrix/appservice-irc/data`).
-When you run the playbook with an existing `/matrix/appservice-irc/passkey.pem` file, the playbook will stop the bridge and relocate the passkey and database files (`rooms.db` and `users.db`) to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`).
+Bridge data (`passkey.pem` and database files) is now also stored in a subdirectory (`/matrix/appservice-irc/data`). When you run the playbook with an existing `/matrix/appservice-irc/passkey.pem` file, the playbook will stop the bridge and relocate the passkey and database files (`rooms.db` and `users.db`) to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`).
 
 
 # 2019-06-15
@@ -2991,8 +3059,7 @@ From now on, the playbook will keep the configuration in sync for you.
 
 This means that if you were making manual changes to the `/matrix/mautrix-telegram/config.yaml` or `/matrix/mautrix-telegram/registration.yaml` configuration files, those would be lost the next time you run the playbook.
 
-The bridge now stores configuration in a subdirectory (`/matrix/mautrix-telegram/config`), so your old configuration remains in the base directory (`/matrix/mautrix-telegram`).
-You need to migrate any manual changes over to the new `matrix_mautrix_telegram_configuration_extension_yaml` variable, so that the playbook would apply them for you.
+The bridge now stores configuration in a subdirectory (`/matrix/mautrix-telegram/config`), so your old configuration remains in the base directory (`/matrix/mautrix-telegram`). You need to migrate any manual changes over to the new `matrix_mautrix_telegram_configuration_extension_yaml` variable, so that the playbook would apply them for you.
 
 Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-telegram/data`). When you run the playbook with an existing database file (`/matrix/mautrix-telegram/mautrix-telegram.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`).
 
@@ -3031,8 +3098,7 @@ From now on, the playbook will keep the configuration in sync for you.
 
 This means that if you were making manual changes to the `/matrix/mautrix-facebook/config.yaml` or `/matrix/mautrix-facebook/registration.yaml` configuration files, those would be lost the next time you run the playbook.
 
-The bridge now stores configuration in a subdirectory (`/matrix/mautrix-facebook/config`), so your old configuration remains in the base directory (`/matrix/mautrix-facebook`).
-You need to migrate any manual changes over to the new `matrix_mautrix_facebook_configuration_extension_yaml` variable, so that the playbook would apply them for you.
+The bridge now stores configuration in a subdirectory (`/matrix/mautrix-facebook/config`), so your old configuration remains in the base directory (`/matrix/mautrix-facebook`). You need to migrate any manual changes over to the new `matrix_mautrix_facebook_configuration_extension_yaml` variable, so that the playbook would apply them for you.
 
 Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-facebook/data`). When you run the playbook with an existing database file (`/matrix/mautrix-facebook/mautrix-facebook.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`).
 
@@ -3093,20 +3159,16 @@ The playbook no longer insists on installing [Synapse](https://github.com/elemen
 
 If you would prefer to install Synapse another way and just use the playbook to install other services, it should be possible (`matrix_synapse_enabled: false`).
 
-Note that it won't necessarily be the best experience, since the playbook wires things to Synapse by default.
-If you're using your own Synapse instance (especially one not running in a container), you may have to override many variables to point them to the correct place.
+Note that it won't necessarily be the best experience, since the playbook wires things to Synapse by default. If you're using your own Synapse instance (especially one not running in a container), you may have to override many variables to point them to the correct place.
 
 Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers.
 
-
 ## Bridges are now separate from the Synapse role
 
-Bridges are no longer part of the `matrix-synapse` role.
-Each bridge now lives in its own separate role (`roles/custom/matrix-bridge-*`).
+Bridges are no longer part of the `matrix-synapse` role. Each bridge now lives in its own separate role (`roles/custom/matrix-bridge-*`).
 
 These bridge roles are independent of the `matrix-synapse` role, so it should be possible to use them with a Synapse instance installed another way (not through the playbook).
 
-
 ## Renaming inconsistently-named Synapse variables
 
 For better consistency, the following variables have been renamed:
@@ -3157,15 +3219,13 @@ We've also started building our own Docker image of Ansible ([devture/ansible](h
 
 # 2019-03-19
 
-## TLS support for Coturn
+## TLS support for coturn
 
-We've added TLS support to the Coturn TURN server installed by the playbook by default.
-The certificates from the Matrix domain will be used for the Coturn server.
+We've added TLS support to the coturn TURN server installed by the playbook by default. The certificates from the Matrix domain will be used for the coturn server.
 
-This feature is enabled by default for new installations.
-To make use of TLS support for your existing Matrix server's Coturn, make sure to rebuild both Coturn and Synapse:
+This feature is enabled by default for new installations. To make use of TLS support for your existing Matrix server's coturn, make sure to rebuild both coturn and Synapse:
 
-```bash
+```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=setup-coturn,setup-synapse,start
 ```
 
@@ -3173,9 +3233,9 @@ People who have an extra firewall (besides the iptables firewall, which Docker m
 
 People who build their own custom playbook from our roles should be aware that:
 
-- the `matrix-coturn` role and actually starting Coturn (e.g. `--tags=start`), requires that certificates are already put in place. For this reason, it's usually a good idea to have the `matrix-coturn` role execute after `matrix-nginx-proxy` (which retrieves the certificates).
+- the `matrix-coturn` role and actually starting coturn (e.g. `--tags=start`), requires that certificates are already put in place. For this reason, it's usually a good idea to have the `matrix-coturn` role execute after `matrix-nginx-proxy` (which retrieves the certificates).
 
-- there are a few variables that can help you enable TLS support for Coturn. See the `matrix-coturn` section in [group_vars/matrix-servers](./group_vars/matrix-servers).
+- there are a few variables that can help you enable TLS support for coturn. See the `matrix-coturn` section in [group_vars/matrix-servers](./group_vars/matrix-servers).
 
 
 # 2019-03-12
@@ -3184,9 +3244,7 @@ People who build their own custom playbook from our roles should be aware that:
 
 If you don't have a dedicated server for your base domain and want to set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), the playbook has got you covered now.
 
-It's now possible for the playbook to obtain an SSL certificate and serve the necessary files for Matrix Server Delegation on your base domain.
-Take a look at the new [Serving the base domain](docs/configuring-playbook-base-domain-serving.md) documentation page.
-
+It's now possible for the playbook to obtain an SSL certificate and serve the necessary files for Matrix Server Delegation on your base domain. Take a look at the new [Serving the base domain](docs/configuring-playbook-base-domain-serving.md) documentation page.
 
 ## (BC break) matrix-nginx-proxy data variable renamed
 
@@ -3206,16 +3264,14 @@ Thanks to [NullIsNot0](https://github.com/NullIsNot0), the playbook can now (opt
 
 ## Ability to customize mxisd's email templates
 
-Thanks to [Sylvia van Os](https://github.com/TheLastProject), mxisd's email templates can now be customized easily.
-To learn more, see the [Customizing email templates](docs/configuring-playbook-mxisd.md#customizing-email-templates) documentation page.
+Thanks to [Sylvia van Os](https://github.com/TheLastProject), mxisd's email templates can now be customized easily. To learn more, see the [Customizing email templates](docs/configuring-playbook-mxisd.md#customizing-email-templates) documentation page.
 
 
 # 2019-03-05
 
 ## Discord bridging support
 
-[@Lionstiger](https://github.com/Lionstiger) has done some great work adding Discord bridging support via [matrix-appservice-discord](https://github.com/Half-Shot/matrix-appservice-discord).
-To learn more, see the [Setting up Appservice Discord bridging](docs/configuring-playbook-bridge-appservice-discord.md) documentation page.
+[@Lionstiger](https://github.com/Lionstiger) has done some great work adding Discord bridging support via [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord). To learn more, see the [Setting up Appservice Discord bridging](docs/configuring-playbook-bridge-appservice-discord.md) documentation page.
 
 
 # 2019-02-19
@@ -3248,8 +3304,7 @@ However, we still provide you with hooks to install your own `home.html` file by
 
 ## Synapse v0.99.1
 
-As we're moving toward Synapse v1.0, things are beginning to stabilize.
-Upgrading from v0.99.0 to v0.99.1 should be painless.
+As we're moving toward Synapse v1.0, things are beginning to stabilize. Upgrading from v0.99.0 to v0.99.1 should be painless.
 
 If you've been overriding the default configuration so that you can terminate TLS at the Synapse side (`matrix_synapse_no_tls: false`), you'll now have to replace this custom configuration with `matrix_synapse_tls_federation_listener_enabled: true`. The `matrix_synapse_no_tls` variable is no more.
 
@@ -3258,8 +3313,7 @@ If you've been overriding the default configuration so that you can terminate TL
 
 ## Synapse v0.99 support and preparation for Synapse v1.0
 
-Matrix is undergoing a lot of changes as it matures towards Synapse v1.0.
-The first step is the Synapse v0.99 transitional release, which this playbook now supports.
+Matrix is undergoing a lot of changes as it matures towards Synapse v1.0. The first step is the Synapse v0.99 transitional release, which this playbook now supports.
 
 If you've been using this playbook successfully until now, you'd be aware that we've been doing [Server Delegation](docs/howto-server-delegation.md) using a `_matrix._tcp` DNS SRV record (as per [Configuring DNS](docs/configuring-dns.md)).
 
@@ -3291,34 +3345,26 @@ When using:
 
 ## IRC bridging support
 
-[Devon Maloney (@Plailect)](https://github.com/Plailect) has done some great work bringing IRC bridging support via [matrix-appservice-irc](https://github.com/TeDomum/matrix-appservice-irc).
-To learn more, see the [Setting up Appservice IRC](docs/configuring-playbook-bridge-appservice-irc.md) documentation page.
+[Devon Maloney (@Plailect)](https://github.com/Plailect) has done some great work bringing IRC bridging support via [matrix-appservice-irc](https://github.com/TeDomum/matrix-appservice-irc). To learn more, see the [Setting up Appservice IRC bridging](docs/configuring-playbook-bridge-appservice-irc.md) documentation page.
 
 
 # 2019-01-29
 
 ## Running container processes as non-root, without capabilities and read-only
 
-To improve security, this playbook no longer starts container processes as the `root` user.
-Most containers were dropping privileges anyway, but we were trusting them with `root` privileges until they would do that.
-Not anymore -- container processes now start as a non-root user (usually `matrix`) from the get-go.
+To improve security, this playbook no longer starts container processes as the `root` user. Most containers were dropping privileges anyway, but we were trusting them with `root` privileges until they would do that. Not anymore -- container processes now start as a non-root user (usually `matrix`) from the get-go.
 
 For additional security, various capabilities are also dropped (see [why it's important](https://github.com/projectatomic/atomic-site/issues/203)) for all containers.
 
-Additionally, most containers now use a read-only filesystem (see [why it's important](https://www.projectatomic.io/blog/2015/12/making-docker-images-write-only-in-production/)).
-Containers are given write access only to the directories they need to write to.
-
-A minor breaking change is the `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size` variable having being renamed to `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size_mb` (note the `_mb` suffix). The new variable expects a number value (e.g. `25M` -> `25`).
-If you weren't customizing this variable, this wouldn't affect you.
+Additionally, most containers now use a read-only filesystem (see [why it's important](https://www.projectatomic.io/blog/2015/12/making-docker-images-write-only-in-production/)). Containers are given write access only to the directories they need to write to.
 
+A minor breaking change is the `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size` variable having being renamed to `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size_mb` (note the `_mb` suffix). The new variable expects a number value (e.g. `25M` -> `25`). If you weren't customizing this variable, this wouldn't affect you.
 
 ## matrix-mailer is now based on Exim, not Postfix
 
-While we would have preferred to stay with [Postfix](http://www.postfix.org/), we found out that it cannot run as a non-root user.
-We've had to replace it with [Exim](https://www.exim.org/) (via the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image).
+While we would have preferred to stay with [Postfix](http://www.postfix.org/), we found out that it cannot run as a non-root user. We've had to replace it with [Exim](https://www.exim.org/) (via the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image).
 
-The internal `matrix-mailer` service (running in a container) now listens on port `8025` (used to be `587` before).
-The playbook will update your Synapse and mxisd email settings to match (`matrix-mailer:587` -> `matrix-mailer:8025`).
+The internal `matrix-mailer` service (running in a container) now listens on port `8025` (used to be `587` before). The playbook will update your Synapse and mxisd email settings to match (`matrix-mailer:587` -> `matrix-mailer:8025`).
 
 Using the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image instead of [panubo/postfix](https://hub.docker.com/r/panubo/postfix/) also gives us a nice disk usage reduction (~200MB -> 8MB).
 
@@ -3330,8 +3376,7 @@ Using the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) cont
 The following change **affects people running a more non-standard setup** - external Postgres or using our roles in their own other playbook.
 **Most users don't need to do anything**, besides becoming aware of the new glue variables file [`group_vars/matrix-servers`](group_vars/matrix-servers).
 
-Because people like using the playbook's components independently (outside of this playbook) and because it's much better for maintainability, we've continued working on separating them.
-Still, we'd like to offer a turnkey solution for running a fully-featured Matrix server, so this playbook remains important for wiring up the various components.
+Because people like using the playbook's components independently (outside of this playbook) and because it's much better for maintainability, we've continued working on separating them. Still, we'd like to offer a turnkey solution for running a fully-featured Matrix server, so this playbook remains important for wiring up the various components.
 
 With the new changes, **all roles are now only dependent on the minimal `matrix-base` role**. They are no longer dependent among themselves.
 
@@ -3394,8 +3439,7 @@ The following variables are no longer supported by this playbook:
 - `matrix_mxisd_ldap_directory_filter`
 - `matrix_mxisd_template_config`
 
-You are encouraged to use the `matrix_mxisd_configuration_extension_yaml` variable to define your own mxisd configuration additions and overrides.
-Refer to the [default variables file](roles/custom/matrix-mxisd/defaults/main.yml) for more information.
+You are encouraged to use the `matrix_mxisd_configuration_extension_yaml` variable to define your own mxisd configuration additions and overrides. Refer to the [default variables file](roles/custom/matrix-mxisd/defaults/main.yml) for more information.
 
 This new way of configuring mxisd is beneficial because:
 
@@ -3431,7 +3475,6 @@ For people who use Let's Encrypt (mostly everyone, since it's the default), you'
 - before: `host_specific_matrix_ssl_support_email`
 - after: `host_specific_matrix_ssl_lets_encrypt_support_email`
 
-
 ## (BC Break) mxisd upgrade with multiple base DN support
 
 mxisd has bee upgraded to [version 1.2.2](https://github.com/kamax-matrix/mxisd/releases/tag/v1.2.2), which supports [multiple base DNs](https://github.com/kamax-matrix/mxisd/blob/v1.2.2/docs/stores/ldap.md#base).
@@ -3448,16 +3491,14 @@ Example change:
 
 ## Synapse 0.34.0 and Python 3
 
-Synapse has been upgraded to 0.34.0 and now uses Python 3.
-Based on feedback from others, running Synapse on Python 3 is supposed to decrease memory usage significantly (~2x).
+Synapse has been upgraded to 0.34.0 and now uses Python 3. Based on feedback from others, running Synapse on Python 3 is supposed to decrease memory usage significantly (~2x).
 
 
 # 2018-12-12
 
 ## Riot homepage customization
 
-You can now customize some parts of the Riot homepage (or even completely replace it with your own custom page).
-See the `matrix_riot_web_homepage_` variables in `roles/custom/matrix-riot-web/defaults/main.yml`.
+You can now customize some parts of the Riot homepage (or even completely replace it with your own custom page). See the `matrix_riot_web_homepage_` variables in `roles/custom/matrix-riot-web/defaults/main.yml`.
 
 
 # 2018-12-04
@@ -3485,15 +3526,13 @@ Additional details are available in [Setting up the LDAP authentication password
 
 ## Support for controlling public registration and room auto-join
 
-The playbook now lets you enable public registration for users (controlled via `matrix_synapse_enable_registration`).
-By default, public registration is forbidden.
+The playbook now lets you enable public registration for users (controlled via `matrix_synapse_enable_registration`). By default, public registration is forbidden.
 
 You can also make people automatically get auto-joined to rooms (controlled via `matrix_synapse_auto_join_rooms`).
 
 ## Support for changing the welcome user ID (welcome bot)
 
-By default, `@riot-bot:matrix.org` is used to welcome newly registered users.
-This can be changed to something else (or disabled) via the new `matrix_riot_web_welcome_user_id` variable.
+By default, `@riot-bot:matrix.org` is used to welcome newly registered users. This can be changed to something else (or disabled) via the new `matrix_riot_web_welcome_user_id` variable.
 
 
 # 2018-11-14
@@ -3504,7 +3543,7 @@ The playbook now allows you to set the log levels used by Synapse. The default l
 
 You can now override following variables with any of the supported log levels listed here: https://docs.python.org/3/library/logging.html#logging-levels
 
-```
+```yaml
 matrix_synapse_log_level: "INFO"
 matrix_synapse_storage_sql_log_level: "INFO"
 matrix_synapse_root_log_level: "INFO"
@@ -3517,7 +3556,7 @@ matrix_synapse_root_log_level: "INFO"
 
 You can now customize some parts of Riot's `config.json`. These playbook variables, with these default values, have been added:
 
-```
+```yaml
 matrix_riot_web_disable_custom_urls: true
 matrix_riot_web_disable_guests: true
 matrix_riot_web_integrations_ui_url: "https://scalar.vector.im/"
@@ -3528,7 +3567,7 @@ matrix_riot_web_integrations_jitsi_widget_url: "https://scalar.vector.im/api/wid
 
 This now allows you use a custom integration manager like [Dimension](https://dimension.t2bot.io). For example, if you wish to use the Dimension instance hosted at dimension.t2bot.io, you can set the following in your vars.yml file:
 
-```
+```yaml
 matrix_riot_web_integrations_ui_url: "https://dimension.t2bot.io/riot"
 matrix_riot_web_integrations_rest_url: "https://dimension.t2bot.io/api/v1/scalar"
 matrix_riot_web_integrations_widgets_urls: "https://dimension.t2bot.io/widgets"
@@ -3552,7 +3591,6 @@ The playbook now installs [Postgres 11](https://www.postgresql.org/about/news/18
 
 If you have have an existing setup, it's likely running on an older Postgres version (9.x or 10.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql).
 
-
 ## (BC Break) Renaming playbook variables
 
 Due to the large amount of features added to this playbook lately, to keep things manageable we've had to reorganize its configuration variables a bit.
@@ -3593,8 +3631,7 @@ The playbook can now help you with [Controlling Matrix federation](docs/configur
 
 ## Disabling riot-web guests
 
-From now on, Riot's configuration setting `disable_guests` would be set to `true`.
-The homeserver was rejecting guests anyway, so this is just a cosmetic change affecting Riot's UI.
+From now on, Riot's configuration setting `disable_guests` would be set to `true`. The homeserver was rejecting guests anyway, so this is just a cosmetic change affecting Riot's UI.
 
 
 # 2018-10-21
@@ -3619,8 +3656,7 @@ If users participate in large rooms with many other servers, disabling presence
 
 The playbook now makes the Synapse cache factor configurable, through the playbook's `matrix_synapse_cache_factor` variable (having a default value of `0.5`).
 
-Changing that value allows you to potentially decrease RAM usage or to increase performance by caching more stuff.
-Some information on it is available here: https://github.com/element-hq/synapse#help-synapse-eats-all-my-ram
+Changing that value allows you to potentially decrease RAM usage or to increase performance by caching more stuff. Some information on it is available here: https://github.com/element-hq/synapse#help-synapse-eats-all-my-ram
 
 
 # 2018-09-26
@@ -3629,7 +3665,7 @@ Some information on it is available here: https://github.com/element-hq/synapse#
 
 `--log-driver=none` is used for all Docker containers now.
 
-All these containers are started through systemd anyway and get logged in journald, so there's no need for Docker to be logging the same thing using the default `json-file` driver. Doing that was growing `/var/lib/docker/containers/..` infinitely until service/container restart.
+All these containers are started through systemd anyway and get logged in journald, so there's no need for Docker to be logging the same thing using the default `json-file` driver. Doing that was growing `/var/lib/docker/containers/…` infinitely until service/container restart.
 
 As a result of this, things like `docker logs matrix-synapse` won't work anymore. `journalctl -u matrix-synapse` is how one can see the logs.
 
@@ -3642,7 +3678,6 @@ The playbook now helps you set up [service discovery](https://matrix.org/docs/sp
 
 Additional details are available in [Configuring service discovery via .well-known](docs/configuring-well-known.md).
 
-
 ## (BC Break) Renaming playbook variables
 
 The following playbook variables were renamed:
@@ -3659,19 +3694,16 @@ The playbook now supports bridging with [Telegram](https://telegram.org/) by ins
 
 Additional details are available in [Setting up Mautrix Telegram bridging](docs/configuring-playbook-bridge-mautrix-telegram.md).
 
-
 ## Events cache size increase and configurability for Matrix Synapse
 
 The playbook now lets you configure Matrix Synapse's `event_cache_size` configuration via the `matrix_synapse_event_cache_size` playbook variable.
 
 Previously, this value was hardcoded to `"10K"`. From now on, a more reasonable default of `"100K"` is used.
 
-
 ## Password-peppering support for Matrix Synapse
 
 The playbook now supports enabling password-peppering for increased security in Matrix Synapse via the `matrix_synapse_password_config_pepper` playbook variable. Using a password pepper is disabled by default (just like it used to be before this playbook variable got introduced) and is not to be enabled/disabled after initial setup, as that would invalidate all existing passwords.
 
-
 ## Statistics-reporting support for Matrix Synapse
 
 There's now a new `matrix_synapse_report_stats` playbook variable, which controls the `report_stats` configuration option for Matrix Synapse. It defaults to `false`, so no change is required to retain your privacy.
@@ -3687,8 +3719,7 @@ We've been using [acmetool](https://github.com/hlandau/acme) (with the [willwill
 
 Due to the Docker image being deprecated, and things looking bleak for acmetool's support of the newer ACME v2 API endpoint, we've switched to using [certbot](https://certbot.eff.org/) (with the [certbot/certbot](https://hub.docker.com/r/certbot/certbot/) Docker image).
 
-Simply re-running the playbook will retrieve new certificates (via certbot) for you.
-To ensure you don't leave any old files behind, though, you'd better do this:
+Simply re-running the playbook will retrieve new certificates (via certbot) for you. To ensure you don't leave any old files behind, though, you'd better do this:
 
 - `systemctl stop 'matrix*'`
 - stop your custom webserver, if you're running one (only affects you if you've installed with `matrix_nginx_proxy_enabled: false`)
@@ -3732,7 +3763,6 @@ The playbook can now install and configure [matrix-synapse-rest-auth](https://gi
 
 Additional details are available in [Setting up the REST authentication password provider module](docs/configuring-playbook-rest-auth.md).
 
-
 ## Compression improvements
 
 Shifted Matrix Synapse compression from happening in the Matrix Synapse,
@@ -3741,38 +3771,33 @@ to happening in the nginx proxy that's in front of it.
 Additionally, `riot-web` also gets compressed now (in the nginx proxy),
 which drops the initial page load's size from 5.31MB to 1.86MB.
 
-
 ## Disabling some unnecessary Synapse services
 
 The following services are not necessary, so they have been disabled:
 - on the federation port (8448): the `client` service
 - on the http port (8008, exposed over 443): the old Angular `webclient` and the `federation` service
 
-Federation runs only on the federation port (8448) now.
-The Client APIs run only on the http port (8008) now.
+Federation runs only on the federation port (8448) now. The Client APIs run only on the http port (8008) now.
 
 
 # 2018-08-15
 
 ## mxisd Identity Server support
 
-The playbook now sets up an [mxisd](https://github.com/kamax-io/mxisd) Identity Server for you by default.
-Additional details are available in [Adjusting mxisd Identity Server configuration](docs/configuring-playbook-mxisd.md).
+The playbook now sets up an [mxisd](https://github.com/kamax-io/mxisd) Identity Server for you by default. Additional details are available in [Setting up ma1sd Identity Server](docs/configuring-playbook-mxisd.md).
 
 
 # 2018-08-14
 
 ## Email-sending support
 
-The playbook now configures an email-sending service (postfix) by default.
-Additional details are available in [Adjusting email-sending settings](docs/configuring-playbook-email.md).
+The playbook now configures an email-sending service (postfix) by default. Additional details are available in [Adjusting email-sending settings](docs/configuring-playbook-email.md).
 
 With this, Matrix Synapse is able to send email notifications for missed messages, etc.
 
 
 # 2018-08-08
 
-
 ## (BC Break) Renaming playbook variables
 
 The following playbook variables were renamed:
@@ -3788,12 +3813,9 @@ The following playbook variables were renamed:
 
 If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names.
 
-
 ## Renaming Ansible playbook tag
 
-The command for executing the whole playbook has changed.
-The `setup-main` tag got renamed to `setup-all`.
-
+The command for executing the whole playbook has changed. The `setup-main` tag got renamed to `setup-all`.
 
 ## Docker container linking
 
diff --git a/LICENSES/AGPL-3.0-or-later.txt b/LICENSES/AGPL-3.0-or-later.txt
new file mode 100644
index 000000000..0c97efd25
--- /dev/null
+++ b/LICENSES/AGPL-3.0-or-later.txt
@@ -0,0 +1,235 @@
+GNU AFFERO GENERAL PUBLIC LICENSE
+Version 3, 19 November 2007
+
+Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+
+                            Preamble
+
+The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software.
+
+The licenses for most software and other practical works are designed to take away your freedom to share and change the works.  By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users.
+
+When we speak of free software, we are referring to freedom, not price.  Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
+
+Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software.
+
+A secondary benefit of defending all users' freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate.  Many developers of free software are heartened and encouraged by the resulting cooperation.  However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public.
+
+The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community.  It requires the operator of a network server to provide the source code of the modified version running there to the users of that server.  Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version.
+
+An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals.  This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license.
+
+The precise terms and conditions for copying, distribution and modification follow.
+
+                       TERMS AND CONDITIONS
+
+0. Definitions.
+
+"This License" refers to version 3 of the GNU Affero General Public License.
+
+"Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
+
+"The Program" refers to any copyrightable work licensed under this License.  Each licensee is addressed as "you".  "Licensees" and "recipients" may be individuals or organizations.
+
+To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy.  The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.
+
+A "covered work" means either the unmodified Program or a work based on the Program.
+
+To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy.  Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
+
+To "convey" a work means any kind of propagation that enables other parties to make or receive copies.  Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
+
+An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License.  If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
+
+1. Source Code.
+The "source code" for a work means the preferred form of the work for making modifications to it.  "Object code" means any non-source form of a work.
+
+A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
+
+The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form.  A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
+
+The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities.  However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work.  For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
+
+The Corresponding Source for a work in source code form is that same work.
+
+2. Basic Permissions.
+All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met.  This License explicitly affirms your unlimited permission to run the unmodified Program.  The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work.  This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
+
+You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force.  You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright.  Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
+
+Conveying under any other circumstances is permitted solely under the conditions stated below.  Sublicensing is not allowed; section 10 makes it unnecessary.
+
+3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
+
+When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
+
+4. Conveying Verbatim Copies.
+You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
+
+You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
+
+5. Conveying Modified Source Versions.
+You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7.  This requirement modifies the requirement in section 4 to "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy.  This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged.  This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
+
+A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit.  Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
+
+6. Conveying Non-Source Forms.
+You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source.  This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
+
+    d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge.  You need not require recipients to copy the Corresponding Source along with the object code.  If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source.  Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
+
+A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
+
+A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling.  In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage.  For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product.  A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
+
+"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source.  The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
+
+If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information.  But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
+
+The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed.  Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
+
+Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
+
+7. Additional Terms.
+"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law.  If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it.  (Additional permissions may be written to require their own removal in certain cases when you modify the work.)  You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
+
+Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
+
+All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10.  If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term.  If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
+
+8. Termination.
+
+You may not propagate or modify a covered work except as expressly provided under this License.  Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
+
+However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
+
+Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License.  If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
+
+9. Acceptance Not Required for Having Copies.
+
+You are not required to accept this License in order to receive or run a copy of the Program.  Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance.  However, nothing other than this License grants you permission to propagate or modify any covered work.  These actions infringe copyright if you do not accept this License.  Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
+
+10. Automatic Licensing of Downstream Recipients.
+
+Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License.  You are not responsible for enforcing compliance by third parties with this License.
+
+An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations.  If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License.  For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
+
+11. Patents.
+
+A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based.  The work thus licensed is called the contributor's "contributor version".
+
+A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version.  For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
+
+In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement).  To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
+
+A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License.  You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
+
+12. No Surrender of Others' Freedom.
+
+If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License.  If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
+
+13. Remote Network Interaction; Use with the GNU General Public License.
+
+Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software.  This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph.
+
+Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work.  The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License.
+
+14. Revised Versions of this License.
+
+The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time.  Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program specifies that a certain numbered version of the GNU Affero General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation.  If the Program does not specify a version number of the GNU Affero General Public License, you may choose any version ever published by the Free Software Foundation.
+
+If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
+
+Later license versions may give you additional or different permissions.  However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
+
+15. Disclaimer of Warranty.
+
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+16. Limitation of Liability.
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+17. Interpretation of Sections 15 and 16.
+
+If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
+
+END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
+
+To do so, attach the following notices to the program.  It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
+
+     <one line to give the program's name and a brief idea of what it does.>
+     Copyright (C) <year>  <name of author>
+
+     This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
+
+     This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU Affero General Public License for more details.
+
+     You should have received a copy of the GNU Affero General Public License along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If your software can interact with users remotely through a computer network, you should also make sure that it provides a way for users to get its source.  For example, if your program is a web application, its interface could display a "Source" link that leads users to an archive of the code.  There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements.
+
+You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU AGPL, see <http://www.gnu.org/licenses/>.
diff --git a/README.md b/README.md
index 50a4cbaea..ee1c5a144 100644
--- a/README.md
+++ b/README.md
@@ -2,32 +2,47 @@
 
 # Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker
 
-## Purpose
+## 🎯 Purpose
 
 This [Ansible](https://www.ansible.com/) playbook is meant to help you run your own [Matrix](http://matrix.org/) homeserver, along with the [various services](#supported-services) related to that.
 
-That is, it lets you join the Matrix network using your own `@<username>:example.com` identifier, all hosted on your own server (see [prerequisites](docs/prerequisites.md)).
+That is, it lets you join the Matrix network using your own user ID like `@alice:example.com`, all hosted on your own server (see [prerequisites](docs/prerequisites.md)).
 
-We run all services in [Docker](https://www.docker.com/) containers (see [the container images we use](docs/container-images.md)), which lets us have a predictable and up-to-date setup, across multiple supported distros (see [prerequisites](docs/prerequisites.md)) and [architectures](docs/alternative-architectures.md) (x86/amd64 being recommended).
+We run all [supported services](#-supported-services) in [Docker](https://www.docker.com/) containers (see [the container images we use](docs/container-images.md)), which lets us have a predictable and up-to-date setup, across multiple supported distros (see [prerequisites](docs/prerequisites.md)) and [architectures](docs/alternative-architectures.md) (x86/amd64 being recommended).
 
-[Installation](docs/README.md) (upgrades) and some maintenance tasks are automated using [Ansible](https://www.ansible.com/) (see [our Ansible guide](docs/ansible.md)).
+Installation (upgrades) and some maintenance tasks are automated using [Ansible](https://www.ansible.com/) (see [our Ansible guide](docs/ansible.md)).
 
+## ☁ Self-hosting or Managed / SaaS
 
-## Self-hosting or Managed / SaaS
-
-This Ansible playbook tries to make self-hosting and maintaining a Matrix server fairly easy. Still, running any service smoothly requires knowledge, time and effort.
+This Ansible playbook tries to make self-hosting and maintaining a Matrix server fairly easy (see [Getting started](#-getting-started)). Still, running any service smoothly requires knowledge, time and effort.
 
 If you like the [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) spirit of this Ansible playbook, but prefer to put the responsibility on someone else, you can also [get a managed Matrix server from etke.cc](https://etke.cc?utm_source=github&utm_medium=readme&utm_campaign=mdad) (both hosting and on-premises) - a service built on top of this Ansible playbook but with [additional components](https://etke.cc/help/extras/?utm_source=github&utm_medium=readme&utm_campaign=mdad) and [services](https://etke.cc/services/?utm_source=github&utm_medium=readme&utm_campaign=mdad) which all help you run a Matrix server with ease. Be advised that etke.cc operates on a subscription-based approach and there is no "just set up my server once and be done with it" option.
 
+## 🚀 Getting started
 
-## Supported services
+We have detailed documentation in the [docs/](./docs) directory - see the Table of Contents in the [documentation README](./docs/README.md).
+
+While the [list of supported services](#-supported-services) and documentation is very extensive, you don't need to read through everything. We recommend:
+
+- Starting with the basics. You can always add/remove or tweak services later on.
+
+- Following our installation guide. There are two guides available for beginners and advanced users:
+
+    - ⚡ **[Quick start](./docs/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".
+
+    - **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](./docs/prerequisites.md)** documentation page.
+
+If you experience an issue on configuring the playbook, setting up your server, maintaining services on it, etc., please take a look at our [FAQ](./docs/faq.md). If you cannot find an answer to your question, feel free to ask for [help and support](#-support).
+
+## ✔ Supported services
 
 Using this playbook, you can get the following list of services configured on your server. Basically, this playbook aims to get you up-and-running with all the necessities around Matrix, without you having to do anything else.
 
-**Note**: the list below is exhaustive. It includes optional or even some advanced components that you will most likely not need.
-Sticking with the defaults (which install a subset of the above components) is the best choice, especially for a new installation.
-You can always re-run the playbook later to add or remove components.
+**Notes**:
 
+- The list below is exhaustive. It includes optional or even some advanced components that you will most likely not need. Sticking with the defaults (which install a subset of the above components) is the best choice, especially for a new installation. You can always re-run the playbook later to add or remove components.
+
+- Deprecated or unmaintained services are not listed. You can find documentations for them [here](docs/configuring-playbook.md#deprecated--unmaintained--removed-services).
 
 ### Homeserver
 
@@ -35,9 +50,10 @@ The homeserver is the backbone of your Matrix system. Choose one from the follow
 
 | Name | Default? | Description | Documentation |
 | ---- | -------- | ----------- | ------------- |
-| [Synapse](https://github.com/element-hq/synapse) | ✓ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network | [Link](docs/configuring-playbook-synapse.md) |
-| [Conduit](https://conduit.rs) | x | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements | [Link](docs/configuring-playbook-conduit.md) |
-| [Dendrite](https://github.com/matrix-org/dendrite) | x | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse. | [Link](docs/configuring-playbook-dendrite.md) |
+| [Synapse](https://github.com/element-hq/synapse) | ✅ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network | [Link](docs/configuring-playbook-synapse.md) |
+| [Conduit](https://conduit.rs) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements | [Link](docs/configuring-playbook-conduit.md) |
+| [Conduwuit](https://conduwuit.puppyirl.gay/) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduwuit is a fork of Conduit. | [Link](docs/configuring-playbook-conduwuit.md) |
+| [Dendrite](https://github.com/element-hq/dendrite) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse. | [Link](docs/configuring-playbook-dendrite.md) |
 
 ### Clients
 
@@ -45,12 +61,10 @@ Web clients for Matrix that you can host on your own domains.
 
 | Name | Default? | Description | Documentation |
 | ---- | -------- | ----------- | ------------- |
-| [Element](https://app.element.io/) | ✓ | Web UI, which is configured to connect to your own Synapse server by default | [Link](docs/configuring-playbook-client-element.md) |
-| [Hydrogen](https://github.com/element-hq/hydrogen-web) | x | Lightweight Matrix client with legacy and mobile browser support | [Link](docs/configuring-playbook-client-hydrogen.md) |
-| [Cinny](https://github.com/ajbura/cinny) |  x | Simple, elegant and secure web client | [Link](docs/configuring-playbook-client-cinny.md) |
-| [SchildiChat](https://schildi.chat/) | x | Based on Element, with a more traditional instant messaging experience | [Link](docs/configuring-playbook-client-schildichat.md) |
-
-
+| [Element Web](https://github.com/element-hq/element-web) | ✅ | Default Matrix web client, configured to connect to your own Synapse server | [Link](docs/configuring-playbook-client-element-web.md) |
+| [Hydrogen](https://github.com/element-hq/hydrogen-web) | ❌ | Lightweight Matrix client with legacy and mobile browser support | [Link](docs/configuring-playbook-client-hydrogen.md) |
+| [Cinny](https://github.com/ajbura/cinny) |  ❌ | Simple, elegant and secure web client | [Link](docs/configuring-playbook-client-cinny.md) |
+| [SchildiChat Web](https://schildi.chat/) | ❌ | Based on Element Web, with a more traditional instant messaging experience | [Link](docs/configuring-playbook-client-schildichat-web.md) |
 
 ### Server Components
 
@@ -58,16 +72,13 @@ Services that run on the server to make the various parts of your installation w
 
 | Name | Default? | Description | Documentation |
 | ---- | -------- | ----------- | ------------- |
-| [PostgreSQL](https://www.postgresql.org/)| ✓ | Database for Synapse. [Using an external PostgreSQL server](docs/configuring-playbook-external-postgres.md) is also possible. | [Link](docs/configuring-playbook-external-postgres.md) |
-| [Coturn](https://github.com/coturn/coturn) | ✓ | STUN/TURN server for WebRTC audio/video calls | [Link](docs/configuring-playbook-turn.md) |
-| [Traefik](https://doc.traefik.io/traefik/) | ✓ | Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](docs/configuring-playbook-own-webserver.md) | [Link](docs/configuring-playbook-traefik.md) |
-| [Let's Encrypt](https://letsencrypt.org/) | ✓ | Free SSL certificate, which secures the connection to all components | [Link](docs/configuring-playbook-ssl-certificates.md) |
-| [ma1sd](https://github.com/ma1uta/ma1sd) | x | Matrix Identity Server | [Link](docs/configuring-playbook-ma1sd.md)
-| [Exim](https://www.exim.org/) | ✓ | Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server) | [Link](docs/configuring-playbook-email.md) |
-| [Dimension](https://github.com/turt2live/matrix-dimension) | x | An open source integration manager for Matrix clients | [Link](docs/configuring-playbook-dimension.md) |
-| [Sygnal](https://github.com/matrix-org/sygnal) | x | Push gateway | [Link](docs/configuring-playbook-sygnal.md) |
-| [ntfy](https://ntfy.sh) | x | Push notifications server | [Link](docs/configuring-playbook-ntfy.md) |
-
+| [PostgreSQL](https://www.postgresql.org/)| ✅ | Database for Synapse. [Using an external PostgreSQL server](docs/configuring-playbook-external-postgres.md) is also possible. | [Link](docs/configuring-playbook-external-postgres.md) |
+| [coturn](https://github.com/coturn/coturn) | ✅ | STUN/TURN server for WebRTC audio/video calls | [Link](docs/configuring-playbook-turn.md) |
+| [Traefik](https://doc.traefik.io/traefik/) | ✅ | Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](docs/configuring-playbook-own-webserver.md) | [Link](docs/configuring-playbook-traefik.md) |
+| [Let's Encrypt](https://letsencrypt.org/) | ✅ | Free SSL certificate, which secures the connection to all components | [Link](docs/configuring-playbook-ssl-certificates.md) |
+| [Exim](https://www.exim.org/) | ✅ | Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server) | [Link](docs/configuring-playbook-email.md) |
+| [ma1sd](https://github.com/ma1uta/ma1sd) | ❌ | Matrix Identity Server | [Link](docs/configuring-playbook-ma1sd.md)
+| [ddclient](https://github.com/linuxserver/docker-ddclient) | ❌ | Dynamic DNS | [Link](docs/configuring-playbook-dynamic-dns.md) |
 
 ### Authentication
 
@@ -75,12 +86,13 @@ Extend and modify how users are authenticated on your homeserver.
 
 | Name | Default? | Description | Documentation |
 | ---- | -------- | ----------- | ------------- |
-| [matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) (advanced) | x | REST authentication password provider module | [Link](docs/configuring-playbook-rest-auth.md) |
-|[matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) (advanced) | x | Password provider module | [Link](docs/configuring-playbook-shared-secret-auth.md) |
-| [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) (advanced) | x | LDAP Auth password provider module | [Link](docs/configuring-playbook-ldap-auth.md) |
-| [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) (advanced) | x | A proxy that handles Matrix registration requests and forwards them to LDAP. | [Link](docs/configuring-playbook-matrix-ldap-registration-proxy.md) |
-| [matrix-registration](https://github.com/ZerataX/matrix-registration) | x | A simple python application to have a token based Matrix registration | [Link](docs/configuring-playbook-matrix-registration.md) |
-
+| [matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) (advanced) | ❌ | REST authentication password provider module | [Link](docs/configuring-playbook-rest-auth.md) |
+|[matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) (advanced) | ❌ | Password provider module | [Link](docs/configuring-playbook-shared-secret-auth.md) |
+| [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) (advanced) | ❌ | LDAP Auth password provider module | [Link](docs/configuring-playbook-ldap-auth.md) |
+| [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) (advanced) | ❌ | A proxy that handles Matrix registration requests and forwards them to LDAP. | [Link](docs/configuring-playbook-matrix-ldap-registration-proxy.md) |
+| [matrix-registration](https://github.com/ZerataX/matrix-registration) | ❌ | A simple python application to have a token based Matrix registration | [Link](docs/configuring-playbook-matrix-registration.md) |
+| [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (UVS) | ❌ | Service to verify details of a user based on an Open ID token | [Link](docs/configuring-playbook-user-verification-service.md) |
+| [synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) (advanced) | ❌ | A spam checker module | [Link](docs/configuring-playbook-synapse-simple-antispam.md) |
 
 ### File Storage
 
@@ -88,9 +100,9 @@ Use alternative file storage to the default `media_store` folder.
 
 | Name | Default? | Description | Documentation |
 | ---- | -------- | ----------- | ------------- |
-| [Goofys](https://github.com/kahing/goofys) | x | [Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files | [Link](docs/configuring-playbook-s3-goofys.md) |
-| [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) | x | [Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files | [Link](docs/configuring-playbook-s3.md) |
-| [matrix-media-repo](https://github.com/turt2live/matrix-media-repo) | x | matrix-media-repo is a 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. | [Link](docs/configuring-playbook-matrix-media-repo.md) |
+| [Goofys](https://github.com/kahing/goofys) | ❌ | [Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files | [Link](docs/configuring-playbook-s3-goofys.md) |
+| [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) | ❌ | [Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files | [Link](docs/configuring-playbook-s3.md) |
+| [matrix-media-repo](https://github.com/turt2live/matrix-media-repo) | ❌ | matrix-media-repo is a 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. | [Link](docs/configuring-playbook-matrix-media-repo.md) |
 
 ### Bridges
 
@@ -98,34 +110,34 @@ Bridges can be used to connect your Matrix installation with third-party communi
 
 | Name | Default? | Description | Documentation |
 | ---- | -------- | ----------- | ------------- |
-| [mautrix-discord](https://github.com/mautrix/discord) | x | Bridge to [Discord](https://discord.com/) | [Link](docs/configuring-playbook-bridge-mautrix-discord.md) |
-| [mautrix-slack](https://github.com/mautrix/slack) | x | Bridge to [Slack](https://slack.com/) | [Link](docs/configuring-playbook-bridge-mautrix-slack.md) |
-| [mautrix-telegram](https://github.com/mautrix/telegram) | x | Bridge to [Telegram](https://telegram.org/) | [Link](docs/configuring-playbook-bridge-mautrix-telegram.md) |
-| [mautrix-gmessages](https://github.com/mautrix/gmessages) | x | Bridge to [Google Messages](https://messages.google.com/) | [Link](docs/configuring-playbook-bridge-mautrix-gmessages.md) |
-| [mautrix-whatsapp](https://github.com/mautrix/whatsapp) | x | Bridge to [WhatsApp](https://www.whatsapp.com/) | [Link](docs/configuring-playbook-bridge-mautrix-whatsapp.md) |
-| [mautrix-facebook](https://github.com/mautrix/facebook) | x | Bridge to [Facebook](https://facebook.com/) | [Link](docs/configuring-playbook-bridge-mautrix-facebook.md) |
-| [mautrix-twitter](https://github.com/mautrix/twitter) | x | Bridge to [Twitter](https://twitter.com/) | [Link](docs/configuring-playbook-bridge-mautrix-twitter.md) |
-| [mautrix-hangouts](https://github.com/mautrix/hangouts) | x | Bridge to [Google Hangouts](https://en.wikipedia.org/wiki/Google_Hangouts) | [Link](docs/configuring-playbook-bridge-mautrix-hangouts.md) |
-| [mautrix-googlechat](https://github.com/mautrix/googlechat) | x | Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat) | [Link](docs/configuring-playbook-bridge-mautrix-googlechat.md) |
-| [mautrix-instagram](https://github.com/mautrix/instagram) | x | Bridge to [Instagram](https://instagram.com/) | [Link](docs/configuring-playbook-bridge-mautrix-instagram.md) |
-| [mautrix-signal](https://github.com/mautrix/signal) | x | Bridge to [Signal](https://www.signal.org/) | [Link](docs/configuring-playbook-bridge-mautrix-signal.md) |
-| [beeper-linkedin](https://github.com/beeper/linkedin) | x | Bridge to [LinkedIn](https://www.linkedin.com/) | [Link](docs/configuring-playbook-bridge-beeper-linkedin.md) |
-| [matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc) | x | Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat) | [Link](docs/configuring-playbook-bridge-appservice-irc.md) |
-| [matrix-appservice-discord](https://github.com/Half-Shot/matrix-appservice-discord) | x | Bridge to [Discord](https://discordapp.com/) | [Link](docs/configuring-playbook-bridge-appservice-discord.md) |
-| [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) | x | Bridge to [Slack](https://slack.com/) | [Link](docs/configuring-playbook-bridge-appservice-slack.md) |
-| [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) | x | Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.) | [Link](docs/configuring-playbook-bridge-appservice-webhooks.md) |
-| [matrix-hookshot](https://github.com/Half-Shot/matrix-hookshot) | x | Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular | [Link](docs/configuring-playbook-bridge-hookshot.md) |
-| [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) | x | Bridge to SMS | [Link](docs/configuring-playbook-bridge-matrix-bridge-sms.md) |
-| [Heisenbridge](https://github.com/hifi/heisenbridge) | x | Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat) | [Link](docs/configuring-playbook-bridge-heisenbridge.md) |
-| [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) | x | Bridge to [Skype](https://www.skype.com) | [Link](docs/configuring-playbook-bridge-go-skype-bridge.md) |
-| [mx-puppet-slack](https://hub.docker.com/r/sorunome/mx-puppet-slack) | x | Bridge to [Slack](https://slack.com) | [Link](docs/configuring-playbook-bridge-mx-puppet-slack.md) |
-| [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) | x | Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/)) | [Link](docs/configuring-playbook-bridge-mx-puppet-instagram.md) |
-| [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) | x | Bridge for Twitter-DMs ([Twitter](https://twitter.com/)) | [Link](docs/configuring-playbook-bridge-mx-puppet-twitter.md) |
-| [mx-puppet-discord](https://github.com/matrix-discord/mx-puppet-discord) | x | Bridge to [Discord](https://discordapp.com/) | [Link](docs/configuring-playbook-bridge-mx-puppet-discord.md) |
-| [mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) | x | Bridge to [GroupMe](https://groupme.com/) | [Link](docs/configuring-playbook-bridge-mx-puppet-groupme.md) |
-| [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) | x | Bridge to [Steam](https://steamapp.com/) | [Link](docs/configuring-playbook-bridge-mx-puppet-steam.md) |
-| [Email2Matrix](https://github.com/devture/email2matrix) | x | Bridge for relaying emails to Matrix rooms | [Link](docs/configuring-playbook-email2matrix.md) |
-
+| [mautrix-discord](https://github.com/mautrix/discord) | ❌ | Bridge to [Discord](https://discord.com/) | [Link](docs/configuring-playbook-bridge-mautrix-discord.md) |
+| [mautrix-slack](https://github.com/mautrix/slack) | ❌ | Bridge to [Slack](https://slack.com/) | [Link](docs/configuring-playbook-bridge-mautrix-slack.md) |
+| [mautrix-telegram](https://github.com/mautrix/telegram) | ❌ | Bridge to [Telegram](https://telegram.org/) | [Link](docs/configuring-playbook-bridge-mautrix-telegram.md) |
+| [mautrix-gmessages](https://github.com/mautrix/gmessages) | ❌ | Bridge to [Google Messages](https://messages.google.com/) | [Link](docs/configuring-playbook-bridge-mautrix-gmessages.md) |
+| [mautrix-whatsapp](https://github.com/mautrix/whatsapp) | ❌ | Bridge to [WhatsApp](https://www.whatsapp.com/) | [Link](docs/configuring-playbook-bridge-mautrix-whatsapp.md) |
+| [mautrix-wsproxy](https://github.com/mautrix/wsproxy) | ❌ | Bridge to Android SMS or Apple iMessage | [Link](docs/configuring-playbook-bridge-mautrix-wsproxy.md) |
+| [mautrix-twitter](https://github.com/mautrix/twitter) | ❌ | Bridge to [Twitter](https://twitter.com/) | [Link](docs/configuring-playbook-bridge-mautrix-twitter.md) |
+| [mautrix-googlechat](https://github.com/mautrix/googlechat) | ❌ | Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat) | [Link](docs/configuring-playbook-bridge-mautrix-googlechat.md) |
+| [mautrix-meta](https://github.com/mautrix/instagram) | ❌ | Bridge to [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) | Link for [Messenger](docs/configuring-playbook-bridge-mautrix-meta-messenger.md) / [Instagram](docs/configuring-playbook-bridge-mautrix-meta-instagram.md) |
+| [mautrix-signal](https://github.com/mautrix/signal) | ❌ | Bridge to [Signal](https://www.signal.org/) | [Link](docs/configuring-playbook-bridge-mautrix-signal.md) |
+| [beeper-linkedin](https://github.com/beeper/linkedin) | ❌ | Bridge to [LinkedIn](https://www.linkedin.com/) | [Link](docs/configuring-playbook-bridge-beeper-linkedin.md) |
+| [matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc) | ❌ | Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat) | [Link](docs/configuring-playbook-bridge-appservice-irc.md) |
+| [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) | ❌ | Bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) | [Link](docs/configuring-playbook-bridge-appservice-kakaotalk.md) |
+| [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord) | ❌ | Bridge to [Discord](https://discordapp.com/) | [Link](docs/configuring-playbook-bridge-appservice-discord.md) |
+| [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) | ❌ | Bridge to [Slack](https://slack.com/) | [Link](docs/configuring-playbook-bridge-appservice-slack.md) |
+| [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) | ❌ | Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular | [Link](docs/configuring-playbook-bridge-hookshot.md) |
+| [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) | ❌ | Bridge to SMS | [Link](docs/configuring-playbook-bridge-matrix-bridge-sms.md) |
+| [matrix-wechat](https://github.com/duo/matrix-wechat) | ❌ | Bridge to [WeChat](https://www.wechat.com/) | [Link](docs/configuring-playbook-bridge-wechat.md) |
+| [Heisenbridge](https://github.com/hifi/heisenbridge) | ❌ | Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat) | [Link](docs/configuring-playbook-bridge-heisenbridge.md) |
+| [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) | ❌ | Bridge to [Skype](https://www.skype.com) | [Link](docs/configuring-playbook-bridge-go-skype-bridge.md) |
+| [mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) | ❌ | Bridge to [Slack](https://slack.com) | [Link](docs/configuring-playbook-bridge-mx-puppet-slack.md) |
+| [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) | ❌ | Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/)) | [Link](docs/configuring-playbook-bridge-mx-puppet-instagram.md) |
+| [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) | ❌ | Bridge for Twitter-DMs ([Twitter](https://twitter.com/)) | [Link](docs/configuring-playbook-bridge-mx-puppet-twitter.md) |
+| [mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) | ❌ | Bridge to [Discord](https://discordapp.com/) | [Link](docs/configuring-playbook-bridge-mx-puppet-discord.md) |
+| [mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) | ❌ | Bridge to [GroupMe](https://groupme.com/) | [Link](docs/configuring-playbook-bridge-mx-puppet-groupme.md) |
+| [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) | ❌ | Bridge to [Steam](https://steamapp.com/) | [Link](docs/configuring-playbook-bridge-mx-puppet-steam.md) |
+| [Email2Matrix](https://github.com/devture/email2matrix) | ❌ | Bridge for relaying emails to Matrix rooms | [Link](docs/configuring-playbook-email2matrix.md) |
+| [Postmoogle](https://github.com/etkecc/postmoogle) | ❌ | Email to Matrix bridge | [Link](docs/configuring-playbook-bridge-postmoogle.md) |
 
 ### Bots
 
@@ -133,61 +145,53 @@ Bots provide various additional functionality to your installation.
 
 | Name | Default? | Description | Documentation |
 | ---- | -------- | ----------- | ------------- |
-| [baibot](https://github.com/etkecc/baibot) | x | A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you | [Link](docs/configuring-playbook-bot-baibot.md) |
-| [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot) | x | Bot for scheduling one-off & recurring reminders and alarms | [Link](docs/configuring-playbook-bot-matrix-reminder-bot.md) |
-| [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) | x | Bot for invitations by creating and managing registration tokens | [Link](docs/configuring-playbook-bot-matrix-registration-bot.md) |
-| [maubot](https://github.com/maubot/maubot) | x | A plugin-based Matrix bot system | [Link](docs/configuring-playbook-bot-maubot.md) |
-| [honoroit](https://github.com/etkecc/honoroit) | x | A helpdesk bot | [Link](docs/configuring-playbook-bot-honoroit.md) |
-| [Postmoogle](https://github.com/etkecc/postmoogle) | x | Email to Matrix bot | [Link](docs/configuring-playbook-bot-postmoogle.md) |
-| [Go-NEB](https://github.com/matrix-org/go-neb) | x | A multi functional bot written in Go | [Link](docs/configuring-playbook-bot-go-neb.md) |
-| [Mjolnir](https://github.com/matrix-org/mjolnir) | x | A moderation tool for Matrix | [Link](docs/configuring-playbook-bot-mjolnir.md) |
-| [Draupnir](https://github.com/the-draupnir-project/Draupnir) | x | A moderation tool for Matrix (Fork of Mjolnir) | [Link](docs/configuring-playbook-bot-draupnir.md) |
-| [Buscarron](https://github.com/etkecc/buscarron) | x | Web forms (HTTP POST) to Matrix | [Link](docs/configuring-playbook-bot-buscarron.md) |
-| [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) | x | ChatGPT from Matrix | [Link](docs/configuring-playbook-bot-chatgpt.md) |
+| [baibot](https://github.com/etkecc/baibot) | ❌ | A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you | [Link](docs/configuring-playbook-bot-baibot.md) |
+| [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot) | ❌ | Bot for scheduling one-off & recurring reminders and alarms | [Link](docs/configuring-playbook-bot-matrix-reminder-bot.md) |
+| [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) | ❌ | Bot for invitations by creating and managing registration tokens | [Link](docs/configuring-playbook-bot-matrix-registration-bot.md) |
+| [maubot](https://github.com/maubot/maubot) | ❌ | A plugin-based Matrix bot system | [Link](docs/configuring-playbook-bot-maubot.md) |
+| [Honoroit](https://github.com/etkecc/honoroit) | ❌ | A helpdesk bot | [Link](docs/configuring-playbook-bot-honoroit.md) |
+| [Mjolnir](https://github.com/matrix-org/mjolnir) | ❌ | A moderation tool for Matrix | [Link](docs/configuring-playbook-bot-mjolnir.md) |
+| [Draupnir](https://github.com/the-draupnir-project/Draupnir) | ❌ | A moderation tool for Matrix (Fork of Mjolnir) | [Link](docs/configuring-playbook-bot-draupnir.md) (for [appservice mode](docs/configuring-playbook-appservice-draupnir-for-all.md))|
+| [Buscarron](https://github.com/etkecc/buscarron) | ❌ | Web forms (HTTP POST) to Matrix | [Link](docs/configuring-playbook-bot-buscarron.md) |
 
 ### Administration
 
 Services that help you in administrating and monitoring your Matrix installation.
 
-
 | Name | Default? | Description | Documentation |
 | ---- | -------- | ----------- | ------------- |
-| [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin) | x | A web UI tool for administrating users and rooms on your Matrix server | [Link](docs/configuring-playbook-synapse-admin.md) |
-| Metrics and Graphs | x | Consists of the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI | [Link](docs/configuring-playbook-prometheus-grafana.md) |
-| [Borg](https://borgbackup.org) | x | Backups | [Link](docs/configuring-playbook-backup-borg.md) |
-| [rageshake](https://github.com/matrix-org/rageshake) | x | Bug report server | [Link](docs/configuring-playbook-rageshake.md) |
-| [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) | x | Export the usage statistics of a Synapse homeserver to be scraped by Prometheus. | [Link](docs/configuring-playbook-synapse-usage-exporter.md) |
+| [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver) | ❌ | Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client | [Link](docs/configuring-playbook-alertmanager-receiver.md) |
+| [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) | ❌ | OAuth 2.0 and OpenID Provider server | [Link](docs/configuring-playbook-matrix-authentication-service.md) |
+| [synapse-admin](https://github.com/etkecc/synapse-admin) | ❌ | A web UI tool for administrating users and rooms on your Matrix server | [Link](docs/configuring-playbook-synapse-admin.md) |
+| Metrics and Graphs | ❌ | Consists of the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI, with [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) being available too | [Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-nginxlog.md)) |
+| [Borg](https://borgbackup.org) | ❌ | Backups | [Link](docs/configuring-playbook-backup-borg.md) |
+| [rageshake](https://github.com/matrix-org/rageshake) | ❌ | Bug report server | [Link](docs/configuring-playbook-rageshake.md) |
+| [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) | ❌ | Export the usage statistics of a Synapse homeserver to be scraped by Prometheus. | [Link](docs/configuring-playbook-synapse-usage-exporter.md) |
 
 ### Misc
 
-Various services that don't fit any other category.
+Various services that don't fit any other categories.
 
 | Name | Default? | Description | Documentation |
 | ---- | -------- | ----------- | ------------- |
-| [sliding-sync](https://github.com/matrix-org/sliding-sync)| x | Sliding Sync support for clients which require it (e.g. Element X) | [Link](docs/configuring-playbook-sliding-sync-proxy.md) |
-| [synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-accept-invite) | x | A Synapse module to automatically accept invites. | [Link](docs/configuring-playbook-synapse-auto-accept-invite.md) |
-| [synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) | x | A cli tool that automatically compresses `state_groups` database table in background. | [Link](docs/configuring-playbook-synapse-auto-compressor.md) |
-| [synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) (advanced) | x | A spam checker module | [Link](docs/configuring-playbook-synapse-simple-antispam.md) |
-| [Matrix Corporal](https://github.com/devture/matrix-corporal) (advanced) | x | Reconciliator and gateway for a managed Matrix server | [Link](docs/configuring-playbook-matrix-corporal.md) |
-| [Etherpad](https://etherpad.org) | x | An open source collaborative text editor | [Link](docs/configuring-playbook-etherpad.md) |
-| [Jitsi](https://jitsi.org/) | x | An open source video-conferencing platform | [Link](docs/configuring-playbook-jitsi.md) |
-| [Cactus Comments](https://cactus.chat) | x | A federated comment system built on Matrix | [Link](docs/configuring-playbook-cactus-comments.md) |
-| [Pantalaimon](https://github.com/matrix-org/pantalaimon) | x | An E2EE aware proxy daemon | [Link](docs/configuring-playbook-pantalaimon.md) |
+| [sliding-sync](https://github.com/matrix-org/sliding-sync)| ❌ | (Superseded by Simplified Sliding Sync integrated into Synapse > `1.114` and Conduit > `0.6.0`) Sliding Sync support for clients which require it (e.g. old Element X versions before Simplified Sliding Sync was developed) | [Link](docs/configuring-playbook-sliding-sync-proxy.md) |
+| [synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-accept-invite) | ❌ | A Synapse module to automatically accept invites. | [Link](docs/configuring-playbook-synapse-auto-accept-invite.md) |
+| [synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) | ❌ | A cli tool that automatically compresses `state_groups` database table in background. | [Link](docs/configuring-playbook-synapse-auto-compressor.md) |
+| [Matrix Corporal](https://github.com/devture/matrix-corporal) (advanced) | ❌ | Reconciliator and gateway for a managed Matrix server | [Link](docs/configuring-playbook-matrix-corporal.md) |
+| [Etherpad](https://etherpad.org) | ❌ | An open source collaborative text editor | [Link](docs/configuring-playbook-etherpad.md) |
+| [Jitsi](https://jitsi.org/) | ❌ | An open source video-conferencing platform | [Link](docs/configuring-playbook-jitsi.md) |
+| [Cactus Comments](https://cactus.chat) | ❌ | A federated comment system built on Matrix | [Link](docs/configuring-playbook-cactus-comments.md) |
+| [Pantalaimon](https://github.com/matrix-org/pantalaimon) | ❌ | An E2EE aware proxy daemon | [Link](docs/configuring-playbook-pantalaimon.md) |
+| [Sygnal](https://github.com/matrix-org/sygnal) | ❌ | Push gateway | [Link](docs/configuring-playbook-sygnal.md) |
+| [ntfy](https://ntfy.sh) | ❌ | Push notifications server | [Link](docs/configuring-playbook-ntfy.md) |
 
-
-## Installation
-
-To configure and install Matrix on your own server, follow the [README in the docs/ directory](docs/README.md).
-
-
-## Changes
+## 🆕 Changes
 
 This playbook evolves over time, sometimes with backward-incompatible changes.
 
 When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up with what's new.
 
-
-## Support
+## 🆘 Support
 
 - Matrix room: [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)
 
@@ -195,8 +199,13 @@ When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up w
 
 - GitHub issues: [spantaleev/matrix-docker-ansible-deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues)
 
+## 🌐 Translation
 
-## Related
+See the [i18n/README.md](i18n/README.md) file for more information about translation.
+
+Translations are still work in progress.
+
+## 🤝 Related
 
 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)).
 
diff --git a/YEAR-IN-REVIEW.md b/YEAR-IN-REVIEW.md
index 3c756e81b..d14602f08 100644
--- a/YEAR-IN-REVIEW.md
+++ b/YEAR-IN-REVIEW.md
@@ -37,7 +37,7 @@ A few other **major components and changes** landed in 2023:
 *   (2023-03-07) [Sliding Sync proxy](https://github.com/matrix-org/sliding-sync) (currently a necessary component for [Element X](https://element.io/labs/element-x) to work), thanks to: [Benjamin Kampmann](https://github.com/gnunicorn) and [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#sliding-sync-proxy-element-x-support))
 *   (2023-03-12) synapse-auto-compressor to periodically and automatically run [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#synapse-auto-compressor-support))
 *   (2023-07-17) [matrix-media-repo](https://github.com/turt2live/matrix-media-repo),  thanks to a PR by [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-media-repo-support))
-*   (2023-08-31) [SchildiChat](https://github.com/SchildiChat/schildichat-desktop) client app (fork of [element-web)](https://github.com/element-hq/element-web), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#schildichat-support))
+*   (2023-08-31) [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client app (fork of [Element Web)](https://github.com/element-hq/element-web), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#schildichat-support))
 *   (2023-10-18) Postgres parameters auto-tuning, thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#postgres-parameters-are-automatically-tuned-now))
 *   (2023-10-23) Enabling federation of the room directory for Synapse (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#enabling-allow_public_rooms_over_federation-by-default-for-synapse))
 
@@ -52,7 +52,7 @@ Hopefully, Synapse defaults would also change the same way and we'd see the numb
 
 With this configuration change in place, projects like [MatrixRooms.info](https://matrixrooms.info/) (made by [etke.cc](https://etke.cc/)) and potentially others in the future, can discover, index the metadata (room address, title, topic, number of users, etc.) and make public rooms browsable & searchable across the whole Matrix Federation. It'd be great if users joining Matrix could more easily find interesting communities that match their interests!
 
-On the **media side of things**, besides Jitsi getting better Matrix integration (via the aforementioned Matrix User Verification Service), we've also had some [Coturn security tightening](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues) as well as [performance optimizations](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#coturn-can-now-use-host-networking) for configurations exposing lots of network ports.
+On the **media side of things**, besides Jitsi getting better Matrix integration (via the aforementioned Matrix User Verification Service), we've also had some [coturn security tightening](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues) as well as [performance optimizations](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#coturn-can-now-use-host-networking) for configurations exposing lots of network ports.
 
 [Element Call](https://github.com/element-hq/element-call) seems to have become a nice and polished product lately (as proclaimed in [The Matrix Holiday Update 2023](https://matrix.org/blog/2023/12/25/the-matrix-holiday-update-2023/)), so 2024 is likely the year we'll see support for it in the playbook. Element Call depends on the [LiveKit](https://livekit.io/) streaming server (which is also useful to developers even by itself), so the first step is likely to see LiveKit support in mash-playbook via a reusable Ansible role. Such a LiveKit Ansible role could later easily land in matrix-docker-ansible-deploy and an Element Call static website could be hooked to it.
 
diff --git a/conf.py b/conf.py
new file mode 100644
index 000000000..1dcc1801d
--- /dev/null
+++ b/conf.py
@@ -0,0 +1,48 @@
+# SPDX-FileCopyrightText: 2024 Slavi Pantaleev <slavi@devture.com>
+# SPDX-FileCopyrightText: 2024 Suguru Hirahara <acioustick@noreply.codeberg.org>
+#
+# SPDX-License-Identifier: AGPL-3.0-or-later
+
+# Configuration file for the Sphinx documentation builder.
+# Also see the `i18n/` directory.
+#
+# For the full list of built-in configuration values, see the documentation:
+# https://www.sphinx-doc.org/en/master/usage/configuration.html
+
+# -- Project information -----------------------------------------------------
+# https://www.sphinx-doc.org/en/master/usage/configuration.html#project-information
+
+project = 'matrix-docker-ansible-deploy'
+copyright = '2018-%Y, Slavi Pantaleev, Aine Etke, MDAD community members'
+author = 'Slavi Pantaleev, Aine Etke, MDAD community members'
+
+# -- General configuration ---------------------------------------------------
+# https://www.sphinx-doc.org/en/master/usage/configuration.html#general-configuration
+
+needs_sphinx = '8.1' # For the copyright year placeholder (%Y). Specified with pyproject.toml as well.
+
+extensions = [
+	'myst_parser',
+	'sphinx_markdown_builder'
+]
+myst_gfm_only = True
+myst_heading_anchors = 4 # https://myst-parser.readthedocs.io/en/latest/syntax/optional.html#auto-generated-header-anchors
+
+master_doc = 'README'
+source_suffix = {'.md': 'markdown'}
+
+# Though the default config file advocates exclude_patterns, it is straightforward for us to use include_patterns to select directories explicitly.
+include_patterns = [
+	'docs/*',
+	'i18n/README.md',
+	'*.md',
+]
+
+locale_dirs = ['i18n/locales/']
+gettext_compact = False
+
+# -- Options for HTML output -------------------------------------------------
+# https://www.sphinx-doc.org/en/master/usage/configuration.html#options-for-html-output
+
+# html_theme = 'alabaster'
+# html_static_path = ['_static']
diff --git a/docs/README.md b/docs/README.md
index 77c5099df..6a0cf1059 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -1,39 +1,86 @@
 # Table of Contents
 
-- [FAQ](faq.md) - lots of questions and answers. Jump to [Prerequisites](prerequisites.md) to avoid reading too much and to just start a guided installation.
+## ⬇️ Installaton guides <!-- NOTE: the 🚀 emoji is used by "Getting started" on README.md -->
 
-- [Prerequisites](prerequisites.md) - go here to a guided installation using this Ansible playbook
+There are two installation guides available for beginners and advanced users.
 
-- [Configuring your DNS server](configuring-dns.md)
+- ⚡ **[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".
 
-- [Getting this playbook's source code](getting-the-playbook.md)
+- **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.
 
-- [Configuring the playbook](configuring-playbook.md)
+    - [Prerequisites](prerequisites.md)
 
-- [Installing](installing.md)
+    - [Configuring your DNS settings](configuring-dns.md)
 
-- **Importing data from another server installation**
+    - [Getting the playbook](getting-the-playbook.md)
 
-  - [Importing an existing SQLite database (from another Synapse installation)](importing-synapse-sqlite.md) (optional)
+    - [Configuring the playbook](configuring-playbook.md)
 
-  - [Importing an existing Postgres database (from another installation)](importing-postgres.md) (optional)
+    - [Installing](installing.md)
 
-  - [Importing `media_store` data files from an existing Synapse installation](importing-synapse-media-store.md) (optional)
+## 🛠️ Configuration options
 
-- [Registering users](registering-users.md)
+<!--
+NOTE:
+- Avoid putting the same anchor links as configuring-playbook.md lists under the "configuration options" section. Note that most of them are linked to "configure-playbook-*.md" and their titles start with "Setting up" (e.g. "Setting up Hydrogen").
+-->
 
-- [Updating users passwords](updating-users-passwords.md)
+You can check useful documentation for configuring components here: [Configuring the playbook](configuring-playbook.md)
 
-- [Configuring service discovery via .well-known](configuring-well-known.md)
+- [Administration](configuring-playbook.md#administration) - services that help you in administrating and monitoring your Matrix installation
 
-- [Maintenance / checking if services work](maintenance-checking-services.md)
+- [Authentication and user-related](configuring-playbook.md#authentication-and-user-related) - extend and modify how users are authenticated on your homeserver
 
-- [Maintenance / upgrading services](maintenance-upgrading-services.md)
+- [Bots](configuring-playbook.md#bots) - bots provide various additional functionality to your installation
 
-- [Maintenance / Synapse](maintenance-synapse.md)
+- [Bridges](configuring-playbook.md#bridging-other-networks) - bridges can be used to connect your Matrix installation with third-party communication networks
 
-- [Maintenance / PostgreSQL](maintenance-postgres.md)
+- [Clients](configuring-playbook.md#clients) - web clients for Matrix that you can host on your own domains
+
+- [Core service adjustments](configuring-playbook.md#core-service-adjustments) - backbone of your Matrix system
+
+- [File Storage](configuring-playbook.md#file-storage) - use alternative file storage to the default `media_store` folder
+
+<!-- NOTE: sort list items above alphabetically -->
+
+- [Other specialized services](configuring-playbook.md#other-specialized-services) - various services that don't fit any other categories
+
+## 👨‍🔧 Maintenance
+
+If your server and services experience issues, feel free to come to [our support room](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) and ask for help.
+
+<!-- NOTE: sort list items alphabetically -->
+
+- [Checking if services work](maintenance-checking-services.md)
 
 - [Maintenance and Troubleshooting](maintenance-and-troubleshooting.md)
 
+- [PostgreSQL maintenance](maintenance-postgres.md)
+
+- [Synapse maintenance](maintenance-synapse.md)
+
+- [Upgrading services](maintenance-upgrading-services.md)
+
+## Other documentation pages <!-- NOTE: this header's title and the section below need optimization -->
+
+- ℹ️ **[FAQ](faq.md)** - various Frequently Asked Questions about Matrix, with a focus on this Ansible playbook
+
+<!-- NOTE: sort list items under faq.md alphabetically -->
+
+- [Alternative architectures](alternative-architectures.md)
+
+- [Container images used by the playbook](container-images.md)
+
+- [Obtaining an Access Token](obtaining-access-tokens.md)
+
+- [Playbook tags](playbook-tags.md)
+
+- [Registering users](registering-users.md)
+
+- [Running `just` commands](just.md)
+
+- [Self-building](self-building.md)
+
 - [Uninstalling](uninstalling.md)
+
+- [Updating users passwords](updating-users-passwords.md)
diff --git a/docs/alternative-architectures.md b/docs/alternative-architectures.md
index 0865de1f0..fa05a4b46 100644
--- a/docs/alternative-architectures.md
+++ b/docs/alternative-architectures.md
@@ -10,7 +10,6 @@ The playbook automatically determines the target server's architecture (the `mat
 
 Some tools and container images can be built on the host or other measures can be used to install on that architecture.
 
-
 ## Implementation details
 
 For `amd64`, prebuilt container images (see the [container images we use](container-images.md)) are used for all components (except [Hydrogen](configuring-playbook-client-hydrogen.md), which goes through self-building).
diff --git a/docs/ansible.md b/docs/ansible.md
index 7783c55be..87b4d86e8 100644
--- a/docs/ansible.md
+++ b/docs/ansible.md
@@ -5,7 +5,6 @@ This playbook is meant to be run using [Ansible](https://www.ansible.com/).
 
 Ansible typically runs on your local computer and carries out tasks on a remote server. If your local computer cannot run Ansible, you can also run Ansible on some server somewhere (including the server you wish to install to).
 
-
 ## Supported Ansible versions
 
 To manually check which version of Ansible you're on, run: `ansible --version`.
@@ -16,7 +15,6 @@ We're not sure what's the minimum version of Ansible that can run this playbook
 
 If your distro ships with an Ansible version older than this, you may run into issues. Consider [Upgrading Ansible](#upgrading-ansible) or [using Ansible via Docker](#using-ansible-via-docker).
 
-
 ## Upgrading Ansible
 
 Depending on your distribution, you may be able to upgrade Ansible in a few different ways:
@@ -27,10 +25,8 @@ Depending on your distribution, you may be able to upgrade Ansible in a few diff
 
 If using the `pip` method, do note that the `ansible-playbook` binary may not be on the `$PATH` (https://linuxconfig.org/linux-path-environment-variable), but in some more special location like `/usr/local/bin/ansible-playbook`. You may need to invoke it using the full path.
 
-
 **Note**: Both of the above methods are a bad way to run system software such as Ansible. If you find yourself needing to resort to such hacks, please consider reporting a bug to your distribution and/or switching to a sane distribution, which provides up-to-date software.
 
-
 ## Using Ansible via Docker
 
 Alternatively, you can run Ansible inside a Docker container (powered by the [devture/ansible](https://hub.docker.com/r/devture/ansible/) Docker image).
@@ -39,7 +35,6 @@ This ensures that you're using a very recent Ansible version, which is less like
 
 You can either [run Ansible in a container on the Matrix server itself](#running-ansible-in-a-container-on-the-matrix-server-itself) or [run Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server).
 
-
 ### Running Ansible in a container on the Matrix server itself
 
 To run Ansible in a (Docker) container on the Matrix server itself, you need to have a working Docker installation. Docker is normally installed by the playbook, so this may be a bit of a chicken and egg problem. To solve it:
@@ -47,42 +42,41 @@ To run Ansible in a (Docker) container on the Matrix server itself, you need to
 - you **either** need to install Docker manually first. Follow [the upstream instructions](https://docs.docker.com/engine/install/) for your distribution and consider setting `matrix_playbook_docker_installation_enabled: false` in your `vars.yml` file, to prevent the playbook from installing Docker
 - **or** you need to run the playbook in another way (e.g. [Running Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)) at least the first time around
 
-Once you have a working Docker installation on the server, **clone the playbook** somewhere on the server and configure it as per usual (`inventory/hosts`, `inventory/host_vars/..`, etc.), as described in [configuring the playbook](configuring-playbook.md).
+Once you have a working Docker installation on the server, **clone the playbook** somewhere on the server and configure it as per usual (`inventory/hosts`, `inventory/host_vars/…`, etc.), as described in [configuring the playbook](configuring-playbook.md).
 
 You would then need to add `ansible_connection=community.docker.nsenter` to the host line in `inventory/hosts`. This tells Ansible to connect to the "remote" machine by switching Linux namespaces with [nsenter](https://man7.org/linux/man-pages/man1/nsenter.1.html), instead of using SSH.
 
-Alternatively, you can leave your `inventory/hosts` as is and specify the connection type in **each** `ansible-playbook` call you do later, like this: `ansible-playbook --connection=community.docker.nsenter ...`
+Alternatively, you can leave your `inventory/hosts` as is and specify the connection type in **each** `ansible-playbook` call you do later, like this: `ansible-playbook --connection=community.docker.nsenter …`
 
 Run this from the playbook's directory:
 
-```bash
+```sh
 docker run -it --rm \
 --privileged \
 --pid=host \
 -w /work \
 -v `pwd`:/work \
 --entrypoint=/bin/sh \
-docker.io/devture/ansible:2.17.0-r0-1
+docker.io/devture/ansible:2.18.1-r0-0
 ```
 
 Once you execute the above command, you'll be dropped into a `/work` directory inside a Docker container. The `/work` directory contains the playbook's code.
 
 First, consider running `git config --global --add safe.directory /work` to [resolve directory ownership issues](#resolve-directory-ownership-issues).
 
-Finally, you can execute `ansible-playbook ...` (or `ansible-playbook --connection=community.docker.nsenter ...`) commands as per normal now.
-
+Finally, you can execute `ansible-playbook …` (or `ansible-playbook --connection=community.docker.nsenter …`) commands as per normal now.
 
 ### Running Ansible in a container on another computer (not the Matrix server)
 
 Run this from the playbook's directory:
 
-```bash
+```sh
 docker run -it --rm \
 -w /work \
 -v `pwd`:/work \
 -v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro \
 --entrypoint=/bin/sh \
-docker.io/devture/ansible:2.17.0-r0-1
+docker.io/devture/ansible:2.18.1-r0-0
 ```
 
 The above command tries to mount an SSH key (`$HOME/.ssh/id_rsa`) into the container (at `/root/.ssh/id_rsa`). If your SSH key is at a different path (not in `$HOME/.ssh/id_rsa`), adjust that part.
@@ -91,19 +85,19 @@ Once you execute the above command, you'll be dropped into a `/work` directory i
 
 First, consider running `git config --global --add safe.directory /work` to [resolve directory ownership issues](#resolve-directory-ownership-issues).
 
-Finally, you execute `ansible-playbook ...` commands as per normal now.
-
+Finally, you execute `ansible-playbook …` commands as per normal now.
 
 #### If you don't use SSH keys for authentication
 
 If you don't use SSH keys for authentication, simply remove that whole line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`).
 
-To authenticate at your server using a password, you need to add a package. So, when you are in the shell of the ansible docker container (the previously used `docker run -it ...` command), run:
-```bash
+To authenticate at your server using a password, you need to add a package. So, when you are in the shell of the ansible docker container (the previously used `docker run -it …` command), run:
+
+```sh
 apk add sshpass
 ```
-Then, to be asked for the password whenever running an  `ansible-playbook` command add `--ask-pass` to the arguments of the command.
 
+Then, to be asked for the password whenever running an  `ansible-playbook` command add `--ask-pass` to the arguments of the command.
 
 #### Resolve directory ownership issues
 
diff --git a/docs/assets/obtain_admin_access_token_element.png b/docs/assets/obtain_admin_access_token_element_web.png
similarity index 100%
rename from docs/assets/obtain_admin_access_token_element.png
rename to docs/assets/obtain_admin_access_token_element_web.png
diff --git a/docs/configuring-captcha.md b/docs/configuring-captcha.md
index ad411ddde..a4a16a1dc 100644
--- a/docs/configuring-captcha.md
+++ b/docs/configuring-captcha.md
@@ -1,6 +1,7 @@
 (Adapted from the [upstream project](https://github.com/element-hq/synapse/blob/develop/docs/CAPTCHA_SETUP.md))
 
 # Overview
+
 Captcha can be enabled for this home server. This file explains how to do that.
 
 The captcha mechanism used is Google's [ReCaptcha](https://www.google.com/recaptcha/). This requires API keys from Google. If your homeserver is Dendrite then [hCapcha](https://www.hcaptcha.com) can be used instead.
diff --git a/docs/configuring-dns.md b/docs/configuring-dns.md
index 605da4182..51e30d69e 100644
--- a/docs/configuring-dns.md
+++ b/docs/configuring-dns.md
@@ -1,100 +1,43 @@
-# Configuring your DNS server
+# Configuring your DNS settings
+
+<sup>[Prerequisites](prerequisites.md) > Configuring your DNS settings > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)</sup>
 
 To set up Matrix on your domain, you'd need to do some DNS configuration.
 
-To use an identifier like `@<username>:example.com`, you don't actually need to install anything on the actual `example.com` server.
-
-You do, however, need to instruct the Matrix network that Matrix services for `example.com` are delegated over to `matrix.example.com`.
-
-As we discuss in [Server Delegation](howto-server-delegation.md), there are 2 different ways to set up such delegation:
-
-- either by serving a `https://example.com/.well-known/matrix/server` file (from the base domain!)
-- or by using a `_matrix._tcp` DNS SRV record (don't confuse this with the `_matrix-identity._tcp` SRV record described below)
-
-This playbook mostly discusses the well-known file method, because it's easier to manage with regard to certificates. If you decide to go with the alternative method ([Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)), please be aware that the general flow that this playbook guides you through may not match what you need to do.
-
 ## DNS settings for services enabled by default
 
-| Type  | Host                         | Priority | Weight | Port | Target                 |
-| ----- | ---------------------------- | -------- | ------ | ---- | ---------------------- |
-| A     | `matrix`                     | -        | -      | -    | `matrix-server-IP`     |
+To serve the base domain (`example.com`) and [Element Web](configuring-playbook-client-element-web.md) with the default subdomain, adjust DNS records as below.
+
+| Type  | Host                         | Priority | Weight | Port | Target               |
+| ----- | ---------------------------- | -------- | ------ | ---- | ---------------------|
+| A     | `matrix`                     | -        | -      | -    | `matrix-server-IP`   |
 | CNAME | `element`                    | -        | -      | -    | `matrix.example.com` |
 
+As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine).
+
+The `element.example.com` subdomain is necessary, because this playbook installs the [Element Web](https://github.com/element-hq/element-web) client for you by default. If you'd rather instruct the playbook not to install Element Web (`matrix_client_element_enabled: false` when [Configuring the playbook](configuring-playbook.md) later), feel free to skip the `element.example.com` DNS record.
+
 Be mindful as to how long it will take for the DNS records to propagate.
 
-If you are using Cloudflare DNS, make sure to disable the proxy and set all records to `DNS only`. Otherwise, fetching certificates will fail.
+**Note**: if you are using Cloudflare DNS, make sure to disable the proxy and set all records to "DNS only". Otherwise, fetching certificates will fail.
 
-When you're done configuring DNS, proceed to [Configuring the playbook](configuring-playbook.md).
+## DNS setting for server delegation (optional)
 
-## DNS settings for optional services/features
+In the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com`.
 
-| Used by component                                                                                                       | Type  | Host                           | Priority | Weight | Port | Target                      |
-| ----------------------------------------------------------------------------------------------------------------------- | ----- | ------------------------------ | -------- | ------ | ---- | --------------------------- |
-| [ma1sd](configuring-playbook-ma1sd.md) identity server                                                                  | SRV   | `_matrix-identity._tcp`        | 10       | 0      | 443  | `matrix.example.com`      |
-| [Dimension](configuring-playbook-dimension.md) integration server                                                       | CNAME | `dimension`                    | -        | -      | -    | `matrix.example.com`      |
-| [Jitsi](configuring-playbook-jitsi.md) video-conferencing platform                                                      | CNAME | `jitsi`                        | -        | -      | -    | `matrix.example.com`      |
-| [Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) monitoring system                                      | CNAME | `stats`                        | -        | -      | -    | `matrix.example.com`      |
-| [Go-NEB](configuring-playbook-bot-go-neb.md) bot                                                                        | CNAME | `goneb`                        | -        | -      | -    | `matrix.example.com`      |
-| [Sygnal](configuring-playbook-sygnal.md) push notification gateway                                                      | CNAME | `sygnal`                       | -        | -      | -    | `matrix.example.com`      |
-| [ntfy](configuring-playbook-ntfy.md) push notifications server                                                          | CNAME | `ntfy`                         | -        | -      | -    | `matrix.example.com`      |
-| [Etherpad](configuring-playbook-etherpad.md) collaborative text editor                                                  | CNAME | `etherpad`                     | -        | -      | -    | `matrix.example.com`      |
-| [Hydrogen](configuring-playbook-client-hydrogen.md) web client                                                          | CNAME | `hydrogen`                     | -        | -      | -    | `matrix.example.com`      |
-| [Cinny](configuring-playbook-client-cinny.md) web client                                                                | CNAME | `cinny`                        | -        | -      | -    | `matrix.example.com`      |
-| [SchildiChat](configuring-playbook-client-schildichat.md) web client                                                    | CNAME | `schildichat`                  | -        | -      | -    | `matrix.example.com`      |
-| [wsproxy](configuring-playbook-bridge-mautrix-wsproxy.md) sms bridge                                                    | CNAME | `wsproxy`                      | -        | -      | -    | `matrix.example.com`      |
-| [Buscarron](configuring-playbook-bot-buscarron.md) helpdesk bot                                                         | CNAME | `buscarron`                    | -        | -      | -    | `matrix.example.com`      |
-| [rageshake](docs/configuring-playbook-rageshake.md) bug report server                                                   | CNAME | `rageshake`                    | -        | -      | -    | `matrix.example.com`      |
-| [Postmoogle](configuring-playbook-bot-postmoogle.md)/[Email2Matrix](configuring-playbook-email2matrix.md) email bridges | MX    | `matrix`                       | 10       | 0      | -    | `matrix.example.com`      |
-| [Postmoogle](configuring-playbook-bot-postmoogle.md) email bridge                                                       | TXT   | `matrix`                       | -        | -      | -    | `v=spf1 ip4:<your-ip> -all` |
-| [Postmoogle](configuring-playbook-bot-postmoogle.md) email bridge                                                       | TXT   | `_dmarc.matrix`                | -        | -      | -    | `v=DMARC1; p=quarantine;`   |
-| [Postmoogle](configuring-playbook-bot-postmoogle.md) email bridge                                                       | TXT   | `postmoogle._domainkey.matrix` | -        | -      | -    | get it from `!pm dkim`      |
+To use such an ID, you don't need to install anything on the actual `example.com` server. Instead, you need to instruct the Matrix network that Matrix services for `example.com` are redirected over to `matrix.example.com`. This redirection is also known as "delegation".
 
-When setting up a SRV record, if you are asked for a service and protocol instead of a hostname split the host value from the table where the period is. For example use service as `_matrix-identity` and protocol as `_tcp`.
+As we discuss in [Server Delegation](howto-server-delegation.md), server delegation can be configured in either of these ways:
 
-## Subdomains setup
+- Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)
+- Setting up a `_matrix._tcp` DNS SRV record
 
-As the table above illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your new server's IP address (DNS `A` record or `CNAME` record is fine).
+For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file, instead of using a DNS SRV record.
 
-The `element.example.com` subdomain may be necessary, because this playbook installs the [Element](https://github.com/element-hq/element-web) web client for you. If you'd rather instruct the playbook not to install Element (`matrix_client_element_enabled: false` when [Configuring the playbook](configuring-playbook.md) later), feel free to skip the `element.example.com` DNS record.
+If you choose the recommended method (file-based delegation), you do not need to configure the DNS record to enable server delegation. You will need to add a necessary configuration later, when you [finalize the installation](installing.md#finalize-the-installation) after installing and starting Matrix services.
 
-The `dimension.example.com` subdomain may be necessary, because this playbook could install the [Dimension integration manager](http://dimension.t2bot.io/) for you. The installation of Dimension is disabled by default, because it's only possible to install it after the other Matrix services are working (see [Setting up Dimension integration manager](configuring-playbook-dimension.md) later). If you do not wish to set up Dimension, feel free to skip the `dimension.example.com` DNS record.
+On the other hand, if you choose this method (setting up a DNS SRV record), you need to configure the additional DNS record as well as adjust SSL certificate handling. Take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)
 
-The `jitsi.example.com` subdomain may be necessary, because this playbook could install the [Jitsi video-conferencing platform](https://jitsi.org/) for you. The installation of Jitsi is disabled by default, because it may be heavy and is not a core required component. To learn how to install it, see our [Jitsi](configuring-playbook-jitsi.md) guide. If you do not wish to set up Jitsi, feel free to skip the `jitsi.example.com` DNS record.
+---------------------------------------------
 
-The `stats.example.com` subdomain may be necessary, because this playbook could install [Grafana](https://grafana.com/) and setup performance metrics for you. The installation of Grafana is disabled by default, it is not a core required component. To learn how to install it, see our [metrics and graphs guide](configuring-playbook-prometheus-grafana.md). If you do not wish to set up Grafana, feel free to skip the `stats.example.com` DNS record. It is possible to install Prometheus without installing Grafana, this would also not require the `stats.example.com` subdomain.
-
-The `goneb.example.com` subdomain may be necessary, because this playbook could install the [Go-NEB](https://github.com/matrix-org/go-neb) bot. The installation of Go-NEB is disabled by default, it is not a core required component. To learn how to install it, see our [configuring Go-NEB guide](configuring-playbook-bot-go-neb.md). If you do not wish to set up Go-NEB, feel free to skip the `goneb.example.com` DNS record.
-
-The `sygnal.example.com` subdomain may be necessary, because this playbook could install the [Sygnal](https://github.com/matrix-org/sygnal) push gateway. The installation of Sygnal is disabled by default, it is not a core required component. To learn how to install it, see our [configuring Sygnal guide](configuring-playbook-sygnal.md). If you do not wish to set up Sygnal (you probably don't, unless you're also developing/building your own Matrix apps), feel free to skip the `sygnal.example.com` DNS record.
-
-The `ntfy.example.com` subdomain may be necessary, because this playbook could install the [ntfy](https://ntfy.sh/) UnifiedPush-compatible push notifications server. The installation of ntfy is disabled by default, it is not a core required component. To learn how to install it, see our [configuring ntfy guide](configuring-playbook-ntfy.md). If you do not wish to set up ntfy, feel free to skip the `ntfy.example.com` DNS record.
-
-The `etherpad.example.com` subdomain may be necessary, because this playbook could install the [Etherpad](https://etherpad.org/) a highly customizable open source online editor providing collaborative editing in really real-time. The installation of Etherpad is disabled by default, it is not a core required component. To learn how to install it, see our [configuring Etherpad guide](configuring-playbook-etherpad.md). If you do not wish to set up Etherpad, feel free to skip the `etherpad.example.com` DNS record.
-
-The `hydrogen.example.com` subdomain may be necessary, because this playbook could install the [Hydrogen](https://github.com/element-hq/hydrogen-web) web client. The installation of Hydrogen is disabled by default, it is not a core required component. To learn how to install it, see our [configuring Hydrogen guide](configuring-playbook-client-hydrogen.md). If you do not wish to set up Hydrogen, feel free to skip the `hydrogen.example.com` DNS record.
-
-The `cinny.example.com` subdomain may be necessary, because this playbook could install the [Cinny](https://github.com/ajbura/cinny) web client. The installation of Cinny is disabled by default, it is not a core required component. To learn how to install it, see our [configuring Cinny guide](configuring-playbook-client-cinny.md). If you do not wish to set up Cinny, feel free to skip the `cinny.example.com` DNS record.
-
-The `schildichat.example.com` subdomain may be necessary, because this playbook could install the [SchildiChat](https://github.com/SchildiChat/schildichat-desktop) web client. The installation of SchildiChat is disabled by default, it is not a core required component. To learn how to install it, see our [configuring SchildiChat guide](configuring-playbook-client-schildichat.md). If you do not wish to set up SchildiChat, feel free to skip the `schildichat.example.com` DNS record.
-
-The `wsproxy.example.com` subdomain may be necessary, because this playbook could install the [wsproxy](https://github.com/mautrix/wsproxy) web client. The installation of wsproxy is disabled by default, it is not a core required component. To learn how to install it, see our [configuring wsproxy guide](configuring-playbook-bridge-mautrix-wsproxy.md). If you do not wish to set up wsproxy, feel free to skip the `wsproxy.example.com` DNS record.
-
-The `buscarron.example.com` subdomain may be necessary, because this playbook could install the [buscarron](https://github.com/etkecc/buscarron) bot. The installation of buscarron is disabled by default, it is not a core required component. To learn how to install it, see our [configuring buscarron guide](configuring-playbook-bot-buscarron.md). If you do not wish to set up buscarron, feel free to skip the `buscarron.example.com` DNS record.
-
-The `rageshake.example.com` subdomain may be necessary, because this playbook could install the [rageshake](https://github.com/matrix-org/rageshake) bug report server. The installation of rageshake is disabled by default, it is not a core required component. To learn how to install it, see our [configuring rageshake guide](configuring-playbook-rageshake.md). If you do not wish to set up rageshake, feel free to skip the `rageshake.example.com` DNS record.
-
-## `_matrix-identity._tcp` SRV record setup
-
-To make the [ma1sd](https://github.com/ma1uta/ma1sd) Identity Server (which this playbook may optionally install for you) enable its federation features, set up an SRV record that looks like this:
-- Name: `_matrix-identity._tcp` (use this text as-is)
-- Content: `10 0 443 matrix.example.com` (replace `example.com` with your own)
-
-This is an optional feature for the optionally-installed [ma1sd service](configuring-playbook-ma1sd.md). See [ma1sd's documentation](https://github.com/ma1uta/ma1sd/wiki/mxisd-and-your-privacy#choices-are-never-easy) for information on the privacy implications of setting up this SRV record.
-
-**Note**: This `_matrix-identity._tcp` SRV record for the identity server is different from the `_matrix._tcp` that can be used for Synapse delegation. See [howto-server-delegation.md](howto-server-delegation.md) for more information about delegation.
-
-When you're done with the DNS configuration and ready to proceed, continue with [Getting the playbook](getting-the-playbook.md).
-
-## `_dmarc`, `postmoogle._domainkey` TXT and `matrix` MX records setup
-
-To make the [postmoogle](configuring-playbook-bot-postmoogle.md) email bridge enable its email sending features, you need to configure SPF (TXT), DMARC (TXT), DKIM (TXT) and MX records
+[▶️](getting-the-playbook.md) When you're done with the DNS configuration and ready to proceed, continue with [Getting the playbook](getting-the-playbook.md).
diff --git a/docs/configuring-playbook-alertmanager-receiver.md b/docs/configuring-playbook-alertmanager-receiver.md
index f05fcaa80..8a0b8776b 100644
--- a/docs/configuring-playbook-alertmanager-receiver.md
+++ b/docs/configuring-playbook-alertmanager-receiver.md
@@ -1,26 +1,58 @@
-# Setting up matrix-alertmanager-receiver (optional)
+# Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver (optional)
 
 The playbook can install and configure the [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver) service for you. It's a [client](https://prometheus.io/docs/alerting/latest/clients/) for Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/), allowing you to deliver alerts to Matrix rooms.
 
-See the project's [documentation](https://github.com/metio/matrix-alertmanager-receiver) to learn more about what this component does and why it might be useful to you.
-
-At the moment, **setting up this service's bot requires some manual actions** as described below in [Account and room preparation](#account-and-room-preparation).
+See the project's [documentation](https://github.com/metio/matrix-alertmanager-receiver/blob/main/README.md) to learn what it does and why it might be useful to you.
 
 This service is meant to be used with an external [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) instance. It's **not** meant to be integrated with the [Prometheus & Grafana stack](./configuring-playbook-prometheus-grafana.md) installed by this playbook, because the Alertmanager component is not installed by it.
 
+## Prerequisites
+
+### Register the bot account
+
+This service uses a bot (with a username specified in `matrix_alertmanager_receiver_config_matrix_user_id_localpart`) for delivering messages.
+
+The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot.
+
+Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`.
+
+You can use the playbook to [register a new user](registering-users.md):
+
+```sh
+ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.alertmanager.receiver password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user
+```
+
+### Obtain an access token
+
+The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md).
+
+⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.
+
+### Join to rooms as the bot manually
+
+ℹ️ **This bot does not accept room invitations automatically**. To deliver messages to rooms, the bot must be joined to all rooms manually.
+
+For each new room you would like the bot to deliver alerts to, invite the bot to the room.
+
+Then, log in as the bot using any Matrix client of your choosing, accept the room invitation from the bot's account, and log out.
+
+## Adjusting DNS records (optional)
+
+By default, this playbook installs matrix-alertmanager-receiver on the `matrix.` subdomain, at the `/matrix-alertmanager-receiver` path (https://matrix.example.com/matrix-alertmanager-receiver). 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.
+
+If you wish to adjust it, see the section [below](#adjusting-the-matrix-alertmanager-receiver-url-optional) for details about DNS configuration.
+
 ## Adjusting the playbook configuration
 
-To enable matrix-alertmanager-receiver, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token).
 
-```yml
+```yaml
 matrix_alertmanager_receiver_enabled: true
 
-# If you'd like to change the username for this bot, uncomment and adjust. Otherwise, remove.
+# Uncomment and adjust this part if you'd like to use a username different than the default
 # matrix_alertmanager_receiver_config_matrix_user_id_localpart: "bot.alertmanager.receiver"
 
-# Specify the bot user's access token here.
-# See the "Account and room preparation" section below.
-matrix_alertmanager_receiver_config_matrix_access_token: ''
+matrix_alertmanager_receiver_config_matrix_access_token: "ACCESS_TOKEN_HERE"
 
 # Optionally, configure some mappings (URL-friendly room name -> actual Matrix room ID).
 #
@@ -35,13 +67,11 @@ matrix_alertmanager_receiver_config_matrix_room_mapping:
 
 See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for additional configuration variables.
 
-### Adjusting the matrix-alertmanager-receiver URL
-
-By default, this playbook installs matrix-alertmanager-receiver on the `matrix.` subdomain, at the `/matrix-alertmanager-receiver` path (https://matrix.example.com/matrix-alertmanager-receiver). 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.
+### Adjusting the matrix-alertmanager-receiver URL (optional)
 
 By tweaking the `matrix_alertmanager_receiver_hostname` and `matrix_alertmanager_receiver_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Change the default hostname and path prefix
@@ -49,43 +79,32 @@ matrix_alertmanager_receiver_hostname: alertmanager.example.com
 matrix_alertmanager_receiver_path_prefix: /
 ```
 
-## Adjusting DNS records
-
-If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-alertmanager-receiver domain to the Matrix server.
-
-See [Configuring DNS](configuring-dns.md) for details about DNS changes.
-
-If you've decided to use the default hostname, you won't need to do any extra DNS configuration.
-
-## Account and room preparation
-
-The playbook can automatically create users, but it cannot automatically obtain access tokens, nor perform any of the other manual actions below.
-
-`matrix-alertmanager-receiver` uses a bot (with a username specified in `matrix_alertmanager_receiver_config_matrix_user_id_localpart` - see above) for delivering messages. You need to **manually register this bot acccount and obtain an access token for it**.
-
-1. [Register a new user](registering-users.md): `ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.alertmanager.receiver password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user`
-2. [Obtain an access token](obtaining-access-tokens.md) for the bot's user account
-3. Invite the bot to a room where you'd like to alerts to be delivered
-4. Log in as the bot using any Matrix client of your choosing, accept the room invitation from the bot's account and log out
-5. (Optionally) Adjust `matrix_alertmanager_receiver_config_matrix_room_mapping` to create a mapping between the new room and its ID
-
-Steps 1 and 2 above only need to be done once, while preparing your [configuration](#adjusting-the-playbook-configuration).
-
-Steps 3 and 4 need to be done for each new room you'd like the bot to deliver alerts to. Step 5 is optional and provides cleaner `/alert/` URLs.
+If you've changed the default hostname, you may need to create a CNAME record for the matrix-alertmanager-receiver domain (`alertmanager.example.com`), which targets `matrix.example.com`.
 
+When setting, replace `example.com` with your own.
 
 ## Installing
 
-Now that you've [prepared the bot account and room](#account-and-room-preparation), [configured the playbook](#adjusting-the-playbook-configuration), and potentially [adjusted your DNS records](#adjusting-dns-records), you can run the [installation](installing.md) command: `just install-all`
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
 
-Then, you can proceed to [Usage](#usage).
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
 
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
 Configure your Prometheus Alertmanager with configuration like this:
 
-```yml
+```yaml
 receivers:
   - name: matrix
     webhook_configs:
@@ -102,6 +121,4 @@ route:
     - receiver: matrix
 ```
 
-.. where `URL_HERE` looks like `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/some-room-name` or `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/!qporfwt:example.com`.
-
-This bot does **not** accept room invitations automatically (like many other bots do). To deliver messages to rooms, **the bot must be joined to all rooms manually** - see Step 5 of the [Account and room preparation](#account-and-room-preparation) section.
+where `URL_HERE` looks like `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/some-room-name` or `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/!qporfwt:example.com`.
diff --git a/docs/configuring-playbook-appservice-double-puppet.md b/docs/configuring-playbook-appservice-double-puppet.md
index 814f34b9a..41967f3fa 100644
--- a/docs/configuring-playbook-appservice-double-puppet.md
+++ b/docs/configuring-playbook-appservice-double-puppet.md
@@ -1,23 +1,44 @@
 # Setting up Appservice Double Puppet (optional)
 
-Appservice Double Puppet is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver.
+The playbook can install and configure the Appservice Double Puppet service for you. It is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver.
 
-This is useful for performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via the [appservice method](https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new). The Appservice Double Puppet service is an implementation of this approach.
+This is useful for performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via the appservice method. The service is an implementation of this approach.
 
-Previously, bridges supported performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but this old and hacky solution has been superseded by this Appservice Double Puppet method.
+Previously, bridges supported performing double-puppeting with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but this old and hacky solution has been superseded by this Appservice Double Puppet method.
 
 ## Adjusting the playbook configuration
 
 To enable the Appservice Double Puppet service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
-```yml
+```yaml
 matrix_appservice_double_puppet_enabled: true
 ```
 
+### Extending the configuration
+
+There are some additional things you may wish to configure about the service.
+
+Take a look at:
+
+- `roles/custom/matrix-appservice-double-puppet/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_appservice_double_puppet_registration_configuration_extension_yaml` variable
+
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
-When enabled, double puppeting will automatically be enabled for all bridges that support double puppeting via the appservice method.
+Installing the service will automatically enable double puppeting for all bridges that support double puppeting via the appservice method.
diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md
index a8c703381..be7aacc30 100644
--- a/docs/configuring-playbook-appservice-draupnir-for-all.md
+++ b/docs/configuring-playbook-appservice-draupnir-for-all.md
@@ -4,7 +4,6 @@ The playbook can install and configure the [Draupnir](https://github.com/the-dra
 
 Appservice mode can be used together with the regular [Draupnir bot](configuring-playbook-bot-draupnir.md) or independently. Details about the differences between the 2 modes are described below.
 
-
 ## Draupnir Appservice mode compared to Draupnir bot mode
 
 The administrative functions for managing the appservice are alpha quality and very limited. However, the experience of using an appservice-provisioned Draupnir is on par with the experience of using Draupnir from bot mode except in the case of avatar customisation as described later on in this document.
@@ -13,78 +12,43 @@ Draupnir for all is the way to go if you need more than 1 Draupnir instance, but
 
 Draupnir for all in the playbook is rate-limit-exempt automatically as its appservice configuration file does not specify any rate limits.
 
-Normal Draupnir does come with the benefit of access to Synapse Admin features. You are also able to more easily customise your normal Draupnir than D4A as D4A even on the branch with the Avatar command (To be Upstreamed to Mainline Draupnir) that command is clunky as it requires the use of things like Element devtools. In normal draupnir this is a quick operation where you login to Draupnir with a normal client and set Avatar and Display name normally.
+Normal Draupnir does come with the benefit of access to Synapse Admin features. You are also able to more easily customise your normal Draupnir than D4A as D4A even on the branch with the Avatar command (To be Upstreamed to Mainline Draupnir) that command is clunky as it requires the use of things like Element Web devtools. In normal Draupnir this is a quick operation where you login to Draupnir with a normal client and set Avatar and Display name normally.
 
 Draupnir for all does not support external tooling like [MRU](https://mru.rory.gay) as it can't access Draupnir's user account.
 
+## Prerequisites
 
-## Installation
+### Create a main management room
 
-### 1. Create a main management room.
+The playbook does not create a management room for your Main Draupnir. You **need to create the room manually** before setting up the bot.
 
-The playbook does not create a management room for your Main Draupnir. This task you have to do on your own.
+Note that the room must be unencrypted.
 
-The management room has to be given an alias and be public when you are setting up the bot for the first time as the bot does not differentiate between invites and invites to the management room.
+The management room has to be given an alias, and your bot has to be invited to the room.
 
-This management room is used to control who has access to your D4A deployment. The room stores this data inside of the control room state so your bot must have sufficient powerlevel to send custom state events. This is default 50 or moderator as Element calls this powerlevel.
+This management room is used to control who has access to your D4A deployment. The room stores this data inside of the control room state so your bot must have sufficient powerlevel to send custom state events. This is default 50 or moderator as Element clients call this powerlevel.
 
-As noted in the Draupnir install instructions the control room is sensitive. The following is said about the control room in the Draupnir install instructions.
->Anyone in this room can control the bot so it is important that you only invite trusted users to this room. The room must be unencrypted since the playbook does not support installing Pantalaimon yet.
+As noted in the Draupnir install instructions the control room is sensitive. **Anyone in this room can control the bot so it is important that you only invite trusted users to this room.**
 
-### 2. Give your main management room an alias.
+### Set an alias to the management room
 
-Give the room from step 1 an alias. This alias can be anything you want and its recommended for increased security during the setup phase of the bot that you make this alias be a random string. You can give your room a secondary human readable alias when it has been locked down after setup phase.
+Next, set an alias to the management room.
 
-### 3. Adjusting the playbook configuration.
+## Adjusting the playbook configuration
 
-Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):
-
-You must replace `ALIAS_FROM_STEP_2_GOES_HERE` with the alias you created in step 2.
+Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ALIAS_HERE`.
 
 ```yaml
 matrix_appservice_draupnir_for_all_enabled: true
 
-matrix_appservice_draupnir_for_all_master_control_room_alias: "ALIAS_FROM_STEP_2_GOES_HERE"
+matrix_appservice_draupnir_for_all_master_control_room_alias: "MANAGEMENT_ROOM_ALIAS_HERE"
 ```
 
-### 4. Installing
+### Extending the configuration
 
-After configuring the playbook, run the [installation](installing.md) command:
+You can configure additional options by adding the `matrix_appservice_draupnir_for_all_extension_yaml` variable.
 
-```
-ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
-```
-
-
-## Usage
-
-If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com` you have succesfully installed Draupnir for All and can now start using it.
-
-The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for allis almost identical to Draupnir bot mode.
-
-### 1. Granting Users the ability to use D4A
-
-Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recomendation. Using the chat is recomended.
-
-The bot requires a powerlevel of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297))
-
-To allow users or whole homeservers you type /plain @draupnir-main:example.com allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially.
-
-### 2. How to provision a D4A once you are allowed to.
-
-Open a DM with @draupnir-main:example.com and if using Element send a message into this DM to finalise creating it. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience.
-
-Congratulations if you made it all the way here because you now have a fully working Draupnir for all deployment.
-
-### Configuration of D4A
-
-You can refer to the upstream [documentation](https://github.com/the-draupnir-project/Draupnir) for more configuration documentation. Please note that the playbook ships a full copy of the example config that does transfer to provisioned draupnirs in the production-bots.yaml.j2 file in the template directory of the role.
-
-Please note that Config extension does not affect the appservices config as this config is not extensible in current Draupnir anyways. Config extension instead touches the config passed to the Draupnirs that your Appservice creates. So for example below makes all provisioned Draupnirs protect all joined rooms.
-
-You can configure additional options by adding the `matrix_appservice_draupnir_for_all_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file.
-
-For example to change draupnir's `protectAllJoinedRooms` option to `true` you would add the following to your `vars.yml` file.
+For example, to change Draupnir's `protectAllJoinedRooms` option to `true`, add the following configuration to your `vars.yml` file:
 
 ```yaml
 matrix_appservice_draupnir_for_all_extension_yaml: |
@@ -97,3 +61,46 @@ matrix_appservice_draupnir_for_all_extension_yaml: |
   # completely redefining `matrix_appservice_draupnir_for_all_yaml`.
   protectAllJoinedRooms: true
 ```
+
+You can refer to the upstream [documentation](https://github.com/the-draupnir-project/Draupnir) for more configuration documentation.
+
+**Notes**:
+
+- The playbook ships a full copy of the example config that does transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in the template directory of the role.
+
+- Config extension does not affect the appservices config as this config is not extensible in current Draupnir anyway. It instead touches the config passed to the Draupnirs that your Appservice creates. So the example above (`protectAllJoinedRooms: true`) makes all provisioned Draupnirs protect all joined rooms.
+
+## Installing
+
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+**Notes**:
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
+
+## Usage
+
+If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com` you have succesfully installed Draupnir for All and can now start using it.
+
+The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot mode.
+
+### Granting Users the ability to use D4A
+
+Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recomendation. Using the chat is recomended.
+
+The bot requires a powerlevel of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297))
+
+To allow users or whole homeservers you type /plain !admin allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially.
+
+### How to provision a D4A once you are allowed to
+
+To provision a D4A, you need to start a chat with `@draupnir-main:example.com`. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience.
+
+Congratulations if you made it all the way here because you now have a fully working Draupnir for all deployment.
diff --git a/docs/configuring-playbook-backup-borg.md b/docs/configuring-playbook-backup-borg.md
index 416b79093..ed960f252 100644
--- a/docs/configuring-playbook-backup-borg.md
+++ b/docs/configuring-playbook-backup-borg.md
@@ -4,44 +4,65 @@ The playbook can install and configure [BorgBackup](https://www.borgbackup.org/)
 
 BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service.
 
-You will need a remote server where BorgBackup will store the backups. There are hosted, BorgBackup compatible solutions available, such as [BorgBase](https://www.borgbase.com).
-
-The backup will run based on `backup_borg_schedule` var (systemd timer calendar), default: 4am every day.
-
-By default, if you're using the integrated Postgres database server (as opposed to [an external Postgres server](configuring-playbook-external-postgres.md)), backups with BorgBackup will also include dumps of your Postgres database. An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md). If you decide to go with another solution, you can disable Postgres-backup support for BorgBackup using the `backup_borg_postgresql_enabled` variable.
-
-
 ## Prerequisites
 
-1. Create a new SSH key:
+### Set up a remote server for storing backups
 
-```bash
+You will need a remote server where BorgBackup will store the backups. There are hosted, BorgBackup compatible solutions available, such as [BorgBase](https://www.borgbase.com).
+
+### Check the Postgres version
+
+By default, if you're using the integrated Postgres database server (as opposed to [an external Postgres server](configuring-playbook-external-postgres.md)), backups with BorgBackup will also include dumps of your Postgres database.
+
+Unless you disable the Postgres-backup support, make sure that the Postgres version of your homeserver's database is compatible with borgmatic. You can check the compatible versions [here](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml).
+
+An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md). If you decide to go with another solution, you can disable Postgres-backup support for BorgBackup using the `backup_borg_postgresql_enabled` variable.
+
+### Create a new SSH key
+
+Run the command below on any machine to create a new SSH key:
+
+```sh
 ssh-keygen -t ed25519 -N '' -f matrix-borg-backup -C matrix
 ```
 
-This can be done on any machine and you don't need to place the key in the `.ssh` folder. It will be added to the Ansible config later.
+You don't need to place the key in the `.ssh` folder.
 
-2. Add the **public** part of this SSH key (the `matrix-borg-backup.pub` file) to your BorgBackup provider/server:
+### Add the public key
 
-If you plan to use a hosted solution, follow their instructions. If you have your own server, copy the key over:
+Next, add the **public** part of this SSH key (the `matrix-borg-backup.pub` file) to your BorgBackup provider/server.
 
-```bash
-# example to append the new PUBKEY contents, where:
-# PUBKEY is path to the public key,
-# USER is a ssh user on a provider / server
-# HOST is a ssh host of a provider / server
+If you are using a hosted solution, follow their instructions. If you have your own server, copy the key to it with the command like below:
+
+```sh
+# Example to append the new PUBKEY contents, where:
+# - PUBKEY is path to the public key
+# - USER is a ssh user on a provider / server
+# - HOST is a ssh host of a provider / server
 cat PUBKEY | ssh USER@HOST 'dd of=.ssh/authorized_keys oflag=append conv=notrunc'
 ```
 
+The **private** key needs to be added to `backup_borg_ssh_key_private` on your `inventory/host_vars/matrix.example.com/vars.yml` file as below.
+
 ## Adjusting the playbook configuration
 
-Minimal working configuration (`inventory/host_vars/matrix.example.com/vars.yml`) to enable BorgBackup:
+To enable BorgBackup, add the following configuration to your `vars.yml` file (adapt to your needs):
 
 ```yaml
 backup_borg_enabled: true
+
+# Set the repository location, where:
+# - USER is a ssh user on a provider / server
+# - HOST is a ssh host of a provider / server
+# - REPO is a BorgBackup repository name
 backup_borg_location_repositories:
  - ssh://USER@HOST/./REPO
+
+# Generate a strong password used for encrypting backups. You can create one with a command like `pwgen -s 64 1`.
 backup_borg_storage_encryption_passphrase: "PASSPHRASE"
+
+# Add the content of the **private** part of the SSH key you have created.
+# Note: the whole key (all of its belonging lines) under the variable needs to be indented with 2 spaces.
 backup_borg_ssh_key_private: |
   -----BEGIN OPENSSH PRIVATE KEY-----
   TG9yZW0gaXBzdW0gZG9sb3Igc2l0IGFtZXQsIGNvbnNlY3RldHVyIGFkaXBpc2NpbmcgZW
@@ -52,28 +73,71 @@ backup_borg_ssh_key_private: |
   -----END OPENSSH PRIVATE KEY-----
 ```
 
-where:
+**Note**: `REPO` will be initialized on backup start, for example: `matrix`. See [Remote repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html#repository-urls) for the syntax.
 
-* USER - SSH user of a provider/server
-* HOST - SSH host of a provider/server
-* REPO - BorgBackup repository name, it will be initialized on backup start, eg: `matrix`, regarding Syntax see [Remote repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html#repository-urls)
-* PASSPHRASE - passphrase used for encrypting backups, you may generate it with `pwgen -s 64 1` or use any password manager
-* PRIVATE KEY - the content of the **private** part of the SSH key you created before. The whole key (all of its belonging lines) under `backup_borg_ssh_key_private` needs to be indented with 2 spaces
+### Set backup archive name (optional)
 
-To backup without encryption, add `backup_borg_encryption: 'none'` to your vars. This will also enable the `backup_borg_unknown_unencrypted_repo_access_is_ok` variable.
+You can specify the backup archive name format. To set it, add the following configuration to your `vars.yml` file (adapt to your needs):
 
-`backup_borg_location_source_directories` defines the list of directories to back up: it's set to `{{ matrix_base_data_path }}` by default, which is the base directory for every service's data, such as Synapse, Postgres and the bridges. You might want to exclude certain directories or file patterns from the backup using the `backup_borg_location_exclude_patterns` variable.
+```yaml
+backup_borg_storage_archive_name_format: matrix-{now:%Y-%m-%d-%H%M%S}
+```
 
-Check the [backup_borg role](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)'s [defaults/main.yml](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/-/blob/main/defaults/main.yml) file for the full list of available options.
+### Configure retention policy (optional)
+
+It is also possible to configure a retention strategy. To configure it, add the following configuration to your `vars.yml` file (adapt to your needs):
+
+```yaml
+backup_borg_retention_keep_hourly: 0
+backup_borg_retention_keep_daily: 7
+backup_borg_retention_keep_weekly: 4
+backup_borg_retention_keep_monthly: 12
+backup_borg_retention_keep_yearly: 2
+```
+
+### Edit the backup schedule (optional)
+
+By default the backup will run 4 a.m. every day based on the `backup_borg_schedule` variable. It 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):
+
+```yaml
+backup_borg_schedule: "*-*-* 04:00:00"
+```
+
+**Note**: the actual job may run with a delay. See `backup_borg_schedule_randomized_delay_sec` [here](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/f5d5b473d48c6504be10b3d946255ef5c186c2a6/defaults/main.yml#L50) for its default value.
+
+### Set include and/or exclude directories (optional)
+
+`backup_borg_location_source_directories` defines the list of directories to back up. It's set to `{{ matrix_base_data_path }}` by default, which is the base directory for every service's data, such as Synapse, Postgres and the bridges.
+
+You might also want to exclude certain directories or file patterns from the backup using the `backup_borg_location_exclude_patterns` variable.
+
+### Extending the configuration
+
+There are some additional things you may wish to configure about the component.
+
+Take a look at:
+
+- [backup_borg role](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/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 `backup_borg_configuration_extension_yaml` variable
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command:
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-```
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
 ```
 
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
+
 ## Manually start a backup
 
-For testing your setup it can be helpful to not wait until 4am. If you want to run the backup immediately, log onto the server and run `systemctl start matrix-backup-borg`. This will not return until the backup is done, so possibly a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable.
+Sometimes it can be helpful to run the backup as you'd like, avoiding to wait until 4 a.m., like when you test your configuration.
+
+If you want to run the backup immediately, log in to the server with SSH and run `systemctl start matrix-backup-borg`.
+
+This will not return until the backup is done, so it can possibly take a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable.
diff --git a/docs/configuring-playbook-base-domain-serving.md b/docs/configuring-playbook-base-domain-serving.md
index 175eae883..3a3335e70 100644
--- a/docs/configuring-playbook-base-domain-serving.md
+++ b/docs/configuring-playbook-base-domain-serving.md
@@ -1,8 +1,15 @@
-# Serving the base domain
+# Serving the base domain (optional)
 
-This playbook sets up services on your Matrix server (`matrix.example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up [Server Delegation](howto-server-delegation.md). This is normally done by [configuring well-known](configuring-well-known.md) files on the base domain.
+By default, this playbook sets up services on your Matrix server (`matrix.example.com`), but has it configured so that it presents itself as the base domain (`example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection.
 
-People who don't have a separate server to dedicate to the base domain have trouble arranging this.
+As we discuss in [Server Delegation](howto-server-delegation.md), server delegation / redirection can be configured in either of these ways:
+
+- Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)
+- Setting up a `_matrix._tcp` DNS SRV record
+
+For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file.
+
+However, those who don't have a separate server to dedicate to the base domain have trouble arranging this.
 
 Usually, there are 2 options:
 
@@ -12,7 +19,7 @@ Usually, there are 2 options:
 
 This documentation page tells you how to do the latter. With some easy changes, we make it possible to serve the base domain from the Matrix server via the integrated webserver.
 
-Just **adjust your DNS records**, so that your base domain is pointed to the Matrix server's IP address (using a DNS `A` record) **and then add the following configuration** to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Just [**adjust your DNS records**](configuring-dns.md), so that your base domain is pointed to the Matrix server's IP address (using a DNS `A` record) **and then add the following configuration** to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
 ```yaml
 matrix_static_files_container_labels_base_domain_enabled: true
@@ -22,11 +29,10 @@ Doing this, the playbook will:
 
 - obtain an SSL certificate for the base domain, just like it does for all other domains (see [how we handle SSL certificates](configuring-playbook-ssl-certificates.md))
 
-- serve the `/.well-known/matrix/*` files which are necessary for [Federation Server Discovery](configuring-well-known.md#introduction-to-client-server-discovery) (also see [Server Delegation](howto-server-delegation.md)) and [Client-Server discovery](configuring-well-known.md#introduction-to-client-server-discovery)
+- serve the `/.well-known/matrix/*` files which are necessary for [Federation Server Discovery](configuring-well-known.md#federation-server-discovery) (also see [Server Delegation](howto-server-delegation.md)) and [Client-Server discovery](configuring-well-known.md#client-server-discovery)
 
 - serve a simple homepage at `https://example.com` with content `Hello from example.com` (configurable via the `matrix_static_files_file_index_html_template` variable). You can also [serve a more complicated static website](#serving-a-static-website-at-the-base-domain).
 
-
 ## Serving a static website at the base domain
 
 By default, when "serving the base domain" is enabled, the playbook hosts a simple `index.html` webpage at `/matrix/static-files/public/index.html`. The content of this page is taken from the `matrix_static_files_file_index_html_template` variable.
@@ -49,7 +55,6 @@ With this configuration, Ansible will no longer mess around with the `/matrix/st
 
 You are then free to upload any static website files to `/matrix/static-files/public` and they will get served at the base domain. You can do so manually or by using the [ansible-role-aux](https://github.com/mother-of-all-self-hosting/ansible-role-aux) Ansible role, which is part of this playbook already.
 
-
 ## Serving a more complicated website at the base domain
 
 If you'd like to serve an even more complicated (dynamic) website from the Matrix server, relying on the playbook to serve the base domain is not the best choice.
diff --git a/docs/configuring-playbook-bot-baibot.md b/docs/configuring-playbook-bot-baibot.md
index 1c7aa419e..0874095d5 100644
--- a/docs/configuring-playbook-bot-baibot.md
+++ b/docs/configuring-playbook-bot-baibot.md
@@ -11,12 +11,10 @@ It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/ch
 
 It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to [matrix-chatgpt-bot](./configuring-playbook-bot-chatgpt.md). See the [baibot](https://github.com/etkecc/baibot) project and its documentation for more information.
 
-
 ## Prerequisites
 
 API access to one or more LLM [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md).
 
-
 ## Adjusting the playbook configuration
 
 There are **a lot of configuration options** (some required, some possibly required, some optional), so they're **split into multiple sections below**:
@@ -30,10 +28,9 @@ There are **a lot of configuration options** (some required, some possibly requi
 
 Depending on your current `vars.yml` file and desired configuration, **you may require more than just the [base configuration](#base-configuration)**.
 
-
 ### Base configuration
 
-Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
 ```yaml
 matrix_bot_baibot_enabled: true
@@ -41,12 +38,12 @@ matrix_bot_baibot_enabled: true
 # Uncomment and adjust this part if you'd like to use a username different than the default
 # matrix_bot_baibot_config_user_mxid_localpart: baibot
 
-# Generate a strong password here. Consider generating it with `pwgen -s 64 1`.
+# Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`.
 # If you'd like to change this password subsequently, see the details below.
 matrix_bot_baibot_config_user_password: 'PASSWORD_FOR_THE_BOT'
 
 # An optional passphrase to use for backing up and recovering the bot's encryption keys.
-# You can put any string here, but generating a strong one is preferred (e.g. `pwgen -s 64 1`).
+# You can create one with a command like `pwgen -s 64 1`.
 #
 # If set to null, the recovery module will not be used and losing your session/database
 # will mean you lose access to old messages in encrypted room.
@@ -73,7 +70,6 @@ matrix_bot_baibot_config_persistence_config_encryption_key: 'A_HEX_STRING_OF_64_
 
 As mentioned above, **this may not be enough**. Continue with the configuration sections below.
 
-
 ### 👮‍♂️ Administrator configuration
 
 This is an addition to the [base configuration](#base-configuration).
@@ -82,16 +78,16 @@ To specify who is considered a bot [👮‍♂️ Administrator](https://github.
 
 If `matrix_admin` is already configured in your `vars.yml` configuration, you can skip this section.
 
-**If necessary**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+**If necessary**, add the following configuration to your `vars.yml` file:
 
-```yml
+```yaml
 # Uncomment to add one or more admins to this bridge:
 #
 # matrix_bot_baibot_config_access_admin_patterns:
 #   - "@*:example.com"
 #   - "@admin:example.net"
 #
-# .. unless you've made yourself an admin of all bots/bridges like this:
+# … unless you've made yourself an admin of all bots/bridges like this:
 #
 # matrix_admin: '@yourAdminAccount:{{ matrix_domain }}'
 ```
@@ -111,9 +107,9 @@ Configuring `matrix_bot_baibot_config_initial_global_config_user_patterns` is op
 
 **Note**: Once initially configured, the allowed users list **cannot be managed via Ansible anymore**. It can only be managed subsequently via bot commands.
 
-**If necessary**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+**If necessary**, add the following configuration to your `vars.yml` file:
 
-```yml
+```yaml
 # Uncomment and adjust the bot users if necessary:
 #
 # Subsequent changes to `matrix_bot_baibot_config_initial_global_config_user_patterns` do not affect the bot's behavior.
@@ -139,41 +135,37 @@ Depending on your propensity for [GitOps](https://en.wikipedia.org/wiki/DevOps#G
 
 Before proceeding, we recommend reading the upstream documentation on [How to choose a provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#how-to-choose-a-provider). In short, it's probably best to go with [OpenAI](#openai).
 
-
 #### Anthropic
 
 You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Anthropic provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic) with the help of the playbook's preset variables.
 
 Here's an example **addition** to your `vars.yml` file:
 
-```yml
+```yaml
 matrix_bot_baibot_config_agents_static_definitions_anthropic_enabled: true
 
 matrix_bot_baibot_config_agents_static_definitions_anthropic_config_api_key: "YOUR_API_KEY_HERE"
 
-# If you'd like to use another text-generation agent, uncomment and adjust:
+# Uncomment and adjust this part if you'd like to use another text-generation agent
 # matrix_bot_baibot_config_agents_static_definitions_anthropic_config_text_generation_model_id: claude-3-5-sonnet-20240620
 
 # The playbook defines a default prompt for all statically-defined agents.
 # You can adjust it in the `matrix_bot_baibot_config_agents_static_definitions_prompt` variable,
 # or you can adjust it below only for the Anthropic agent.
 # matrix_bot_baibot_config_agents_static_definitions_anthropic_config_text_generation_prompt: "{{ matrix_bot_baibot_config_agents_static_definitions_prompt }}"
-
-# See `defaults/main.yml` in the baibot role for more configuration options.
 ```
 
 If you'd like to use more than one model, take a look at the [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset) section below.
 
 💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers).
 
-
 #### Groq
 
 You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Groq provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq) with the help of the playbook's preset variables.
 
 Here's an example **addition** to your `vars.yml` file:
 
-```yml
+```yaml
 matrix_bot_baibot_config_agents_static_definitions_groq_enabled: true
 
 matrix_bot_baibot_config_agents_static_definitions_groq_config_api_key: "YOUR_API_KEY_HERE"
@@ -190,8 +182,6 @@ matrix_bot_baibot_config_agents_static_definitions_groq_config_text_generation_m
 #
 # matrix_bot_baibot_config_agents_static_definitions_groq_config_speech_to_text_enabled: true
 # matrix_bot_baibot_config_agents_static_definitions_groq_config_speech_to_text_model_id: whisper-large-v3
-
-# See `defaults/main.yml` in the baibot role for more configuration options.
 ```
 
 Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/groq`.
@@ -200,14 +190,13 @@ If you'd like to use more than one model, take a look at the [Configuring additi
 
 💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers).
 
-
 #### Mistral
 
 You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [🇫🇷 Mistral provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral) with the help of the playbook's preset variables.
 
 Here's an example **addition** to your `vars.yml` file:
 
-```yml
+```yaml
 matrix_bot_baibot_config_agents_static_definitions_mistral_enabled: true
 
 matrix_bot_baibot_config_agents_static_definitions_mistral_config_api_key: "YOUR_API_KEY_HERE"
@@ -219,8 +208,6 @@ matrix_bot_baibot_config_agents_static_definitions_mistral_config_api_key: "YOUR
 
 # Uncomment and adjust this part if you're not happy with these defaults:
 # matrix_bot_baibot_config_agents_static_definitions_mistral_config_text_generation_model_id: mistral-large-latest
-
-# See `defaults/main.yml` in the baibot role for more configuration options.
 ```
 
 Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/mistral`.
@@ -229,7 +216,6 @@ If you'd like to use more than one model, take a look at the [Configuring additi
 
 💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers).
 
-
 #### OpenAI
 
 You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai) with the help of the playbook's preset variables.
@@ -238,7 +224,7 @@ The OpenAI provider is **only meant to be used with OpenAI's official API** and
 
 Here's an example **addition** to your `vars.yml` file:
 
-```yml
+```yaml
 matrix_bot_baibot_config_agents_static_definitions_openai_enabled: true
 
 matrix_bot_baibot_config_agents_static_definitions_openai_config_api_key: "YOUR_API_KEY_HERE"
@@ -250,8 +236,6 @@ matrix_bot_baibot_config_agents_static_definitions_openai_config_api_key: "YOUR_
 
 # If you'd like to use another text-generation agent, uncomment and adjust:
 # matrix_bot_baibot_config_agents_static_definitions_openai_config_text_generation_model_id: gpt-4o
-
-# See `defaults/main.yml` in the baibot role for more configuration options.
 ```
 
 Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/openai`.
@@ -260,7 +244,6 @@ If you'd like to use more than one model, take a look at the [Configuring additi
 
 💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers).
 
-
 #### OpenAI Compatible
 
 You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI Compatible provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai-compatible) with the help of the playbook's preset variables.
@@ -271,7 +254,6 @@ Some of these popular services already have **shortcut** providers (see [support
 
 As of this moment, the playbook does not include presets for any of these services, so you'll need to [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset).
 
-
 #### Configuring additional agents (without a preset)
 
 The Ansible role may be lacking preset variables for some [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), or you may wish to statically-define an agent on the same provider twice (or more) with different configuration.
@@ -282,7 +264,7 @@ You can also define providers at runtime, by chatting with the bot, so using Ans
 
 Below is an an **example** demonstrating **statically-defining agents via Ansible without using presets**:
 
-```yml
+```yaml
 matrix_bot_baibot_config_agents_static_definitions_custom:
   # This agent will use the GPT 3.5 model and will only support text-generation,
   # even though the `openai` provider could support other features (e.g. image-generation).
@@ -327,7 +309,6 @@ As with any [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.
 
 💡 You may also wish to use these new agents for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers).
 
-
 ### 🤝 Configuring initial default handlers
 
 This section is only useful if you're [🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible), as it lets you put these agents to use as soon as the bot starts (by adjusting the bot's **initial global configuration**).
@@ -356,7 +337,7 @@ You can configure the **initial values** for these via Ansible, via the `matrix_
 
 Example **additional** `vars.yml` configuration:
 
-```yml
+```yaml
 # Note: these are initial defaults for the bot's global configuration.
 # As such, changing any of these values subsequently has no effect on the bot's behavior.
 # Once initially configured, the global configuration is managed via bot commands, not via Ansible.
@@ -373,25 +354,37 @@ matrix_bot_baibot_config_initial_global_config_handler_image_generation: null
 
 **Note**: these are initial defaults for the bot's global configuration. As such, changing any of these values subsequently has no effect on the bot's behavior. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands.
 
+### Extending the configuration
+
+There are some additional things you may wish to configure about the bot.
+
+Take a look at:
+
+- `roles/custom/matrix-bot-baibot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+- `roles/custom/matrix-bot-baibot/templates/config.yaml.j2` for the bot's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_bot_baibot_configuration_extension_yaml` variable
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command:
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
 ```sh
-just run-tags install-all,ensure-matrix-users-created,start
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
 ```
 
 **Notes**:
 
-- the `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-- if you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
+  `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.
+
+- If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password.
 
 ## Usage
 
-To use the bot, invite the `@baibot:example.com` bot user into a room.
+To use the bot, invite it to any existing Matrix room (`/invite @baibot:example.com` where `example.com` is your base domain, not the `matrix.` domain).
 
 If you're an allowed bot [👥 user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) (see [👥 Initial users configuration](#-initial-users-configuration)), the bot will accept your invitation and join the room.
 
@@ -399,11 +392,10 @@ After joining, the bot will introduce itself and show information about the [✨
 
 If you've [🤖 configured one or more agents via Ansible](#-configuring-agents-via-ansible) and have [🤝 configured initial default handlers](#configuring-initial-default-handlers), the bot will immediately be able to make use of these agents for this new room. Otherwise, you will need to configure agents and/or handlers via chat commands.
 
-Send `!bai help` to the room at any time to see the bot's help menu for additional commands.
+Send `!bai help` to the bot in the room to see the available commands.
 
 You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) project's documentation.
 
-
 ## Debugging
 
 As with all other services, you can find service logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-bot-baibot`
diff --git a/docs/configuring-playbook-bot-buscarron.md b/docs/configuring-playbook-bot-buscarron.md
index f38d25298..c7ed4f69d 100644
--- a/docs/configuring-playbook-bot-buscarron.md
+++ b/docs/configuring-playbook-bot-buscarron.md
@@ -1,12 +1,18 @@
 # Setting up Buscarron (optional)
 
-The playbook can install and configure [buscarron](https://github.com/etkecc/buscarron) for you.
+The playbook can install and configure [Buscarron](https://github.com/etkecc/buscarron) for you.
 
 Buscarron is bot that receives HTTP POST submissions of web forms and forwards them to a Matrix room.
 
+## Adjusting DNS records
+
+By default, this playbook installs Buscarron on the `buscarron.` subdomain (`buscarron.example.com`) and requires you to create a CNAME record for `buscarron`, which targets `matrix.example.com`.
+
+When setting, replace `example.com` with your own.
+
 ## Adjusting the playbook configuration
 
-To enable Buscarron, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
 ```yaml
 matrix_bot_buscarron_enabled: true
@@ -14,7 +20,7 @@ matrix_bot_buscarron_enabled: true
 # Uncomment and adjust this part if you'd like to use a username different than the default
 # matrix_bot_buscarron_login: bot.buscarron
 
-# Generate a strong password here. Consider generating it with `pwgen -s 64 1`
+# Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`.
 matrix_bot_buscarron_password: PASSWORD_FOR_THE_BOT
 
 # Adjust accepted forms
@@ -29,13 +35,11 @@ matrix_bot_buscarron_forms:
 matrix_bot_buscarron_spamlist: [] # (optional) list of emails/domains/hosts (with wildcards support) that should be rejected automatically
 ```
 
-### Adjusting the Buscarron URL
-
-By default, this playbook installs Buscarron on the `buscarron.` subdomain (`buscarron.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records).
+### Adjusting the Buscarron URL (optional)
 
 By tweaking the `matrix_bot_buscarron_hostname` and `matrix_bot_buscarron_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Switch to the domain used for Matrix services (`matrix.example.com`),
@@ -46,32 +50,36 @@ matrix_bot_buscarron_hostname: "{{ matrix_server_fqn_matrix }}"
 matrix_bot_buscarron_path_prefix: /buscarron
 ```
 
-## Adjusting DNS records
-
-Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Buscarron domain to the Matrix server.
-
-By default, you will need to create a CNAME record for `buscarron`. See [Configuring DNS](configuring-dns.md) for details about DNS changes.
+After changing the domain, **you may need to adjust your DNS** records to point the Buscarron domain to the Matrix server.
 
 If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command:
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
 
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
 ```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
 ```
 
 **Notes**:
 
-- the `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-- if you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
+  `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.
+
+- If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password.
 
 ## Usage
 
-To use the bot, invite the `@bot.buscarron:example.com` to the room you specified in a config, after that any point your form to the form url, example for the `contact` form:
+To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.buscarron:example.com` where `example.com` is your base domain, not the `matrix.` domain).
+
+After the bot joins the room, anyone can call the web form via HTTP POST method.
+
+Here is an example for the `contact` form:
 
 ```html
 <form method="POST" action="https://buscarron.example.com/contact">
@@ -81,9 +89,9 @@ To use the bot, invite the `@bot.buscarron:example.com` to the room you specifie
 
 **Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:
 
-- if you hit the homepage (HTTP `GET` request to `/`)
-- if you submit a form to the wrong URL (`POST` request to `/non-existing-form`)
-- if `hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field
+- you hit the homepage (HTTP `GET` request to `/`)
+- you submit a form to the wrong URL (`POST` request to `/non-existing-form`)
+- `hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field
 
 If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server.
 
diff --git a/docs/configuring-playbook-bot-chatgpt.md b/docs/configuring-playbook-bot-chatgpt.md
index 100b1060c..3ed5ef729 100644
--- a/docs/configuring-playbook-bot-chatgpt.md
+++ b/docs/configuring-playbook-bot-chatgpt.md
@@ -1,71 +1,77 @@
-# Setting up ChatGPT (optional)
+# Setting up matrix-bot-chatgpt (optional, unmaintained)
+
+**Note**: [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) is now an archived (**unmaintained**) project. Talking to ChatGPT (and many other LLM providers) can happen via the much more featureful [baibot](https://github.com/etkecc/baibot), which can be installed using [this playbook](configuring-playbook-bot-baibot.md). Consider using that bot instead of this one.
 
 The playbook can install and configure [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) for you.
 
 Talk to [ChatGPT](https://openai.com/blog/chatgpt/) via your favourite Matrix client!
 
-**Note**: [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) is now an archived (**unmaintained**) project. Talking to ChatGPT (and many other LLM providers) can happen via the much more featureful [baibot](./configuring-playbook-bot-baibot.md) bot supported by the playbook.
+## Prerequisites
 
+### Obtain an OpenAI API key
 
-## 1. Register the bot account
+To use the bot, you'd need to obtain an API key from [https://platform.openai.com/account/api-keys](https://platform.openai.com/account/api-keys).
 
-The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver.
+### Register the bot account
 
-You **need to register the bot user manually** before setting up the bot.
+The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot.
 
-Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`.
+Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`.
 
 You can use the playbook to [register a new user](registering-users.md):
 
-```
+```sh
 ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.chatgpt password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user
 ```
 
+### Obtain an access token and create encryption keys
 
-## 2. Get an access token and create encryption keys
+The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md).
 
-Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md).
+⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.
 
-To make sure the bot can read encrypted messages, it will need an encryption key, just like any other new user. While obtaining the access token, follow the prompts to setup a backup key. More information can be found in the [element documentation](https://element.io/help#encryption6).
+To make sure the bot can read encrypted messages, it will need an encryption key, just like any other new user. While obtaining the access token, follow the prompts to setup a backup key. More information can be found in the [Element documentation](https://element.io/help#encryption6).
 
+## Adjusting the playbook configuration
 
-## 3. Adjusting the playbook configuration
-
-Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):
+To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `API_KEY_HERE` with the API key retrieved [here](#obtain-an-openai-api-key) and `ACCESS_TOKEN_HERE` with the access token created [here](#obtain-an-access-token-and-create-encryption-keys), respectively.
 
 ```yaml
 matrix_bot_chatgpt_enabled: true
 
-# Obtain a new API key from https://platform.openai.com/account/api-keys
-matrix_bot_chatgpt_openai_api_key: ''
+matrix_bot_chatgpt_openai_api_key: 'API_KEY_HERE'
 
-# This is the default username
+# Uncomment and adjust this part if you'd like to use a username different than the default
 # matrix_bot_chatgpt_matrix_bot_username_localpart: 'bot.chatgpt'
 
-# Matrix access token (from bot user above)
-# see: https://webapps.stackexchange.com/questions/131056/how-to-get-an-access-token-for-element-riot-matrix
-matrix_bot_chatgpt_matrix_access_token: ''
+matrix_bot_chatgpt_matrix_access_token: 'ACCESS_TOKEN_HERE'
 
 # Configuring the system promt used, needed if the bot is used for special tasks.
 # More information: https://github.com/mustvlad/ChatGPT-System-Prompts
 matrix_bot_chatgpt_matrix_bot_prompt_prefix: 'Instructions:\nYou are ChatGPT, a large language model trained by OpenAI.'
-
 ```
 
-You will need to get tokens for ChatGPT.
+## Installing
 
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-## 4. Installing
-
-After configuring the playbook, run the [installation](installing.md) command:
-
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
 ```sh
-ansible-playbook -i inventory/hosts setup.yml --tags=install-all,start
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
 ```
 
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
-To use the bot, invite the `@bot.chatgpt:example.com` to the room you specified in a config, after that start speaking to it, use the prefix if you configured one or mention the bot.
+To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.chatgpt:example.com` where `example.com` is your base domain, not the `matrix.` domain).
+
+After the bot joins the room, you can send a message to it. When you do so, use the prefix if you configured it or mention the bot.
 
 You can also refer to the upstream [documentation](https://github.com/matrixgpt/matrix-chatgpt-bot).
diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md
index 5bd9c3df8..58c15b1af 100644
--- a/docs/configuring-playbook-bot-draupnir.md
+++ b/docs/configuring-playbook-bot-draupnir.md
@@ -1,126 +1,162 @@
-# Setting up draupnir (optional)
+# Setting up Draupnir (optional)
 
-The playbook can install and configure the [draupnir](https://github.com/the-draupnir-project/Draupnir) moderation bot for you.
+The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation bot for you.
 
-See the project's [documentation](https://github.com/the-draupnir-project/Draupnir) to learn what it does and why it might be useful to you.
+See the project's [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) to learn what it does and why it might be useful to you.
 
 This documentation page is about installing Draupnir in bot mode. As an alternative, you can run a multi-instance Draupnir deployment by installing [Draupnir in appservice mode](./configuring-playbook-appservice-draupnir-for-all.md) (called Draupnir-for-all) instead.
 
+If your migrating from Mjolnir skip to [this section](#migrating-from-mjolnir-only-required-if-migrating).
 
-If your migrating from Mjolnir skip to step 5b.
+## Prerequisites
 
-## 1. Register the bot account
-
-The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver.
-
-You **need to register the bot user manually** before setting up the bot.
-
-Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`.
-
-You can use the playbook to [register a new user](registering-users.md):
-
-```
-ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.draupnir password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user
-```
-
-If you would like draupnir to be able to deactivate users, move aliases, shutdown rooms, show abuse reports ([see below](#abuse-reports)), etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above.
-
-
-## 2. Get an access token
-
-Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md).
-
-
-## 3. Make sure the account is free from rate limiting
-
-You will need to prevent Synapse from rate limiting the bot's account. This is not an optional step. If you do not do this step draupnir will crash. This can be done using Synapse's [admin API](https://matrix-org.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). Please ask for help if you are uncomfortable with these steps or run into issues.
-
-If your Synapse Admin API is exposed to the internet for some reason like running the Synapse Admin Role [Link](/docs/configuring-playbook-synapse-admin.md) or running `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` in your playbook config. If your API is not externally exposed you should still be able to on the local host for your synapse run these commands.
-
-The following command works on semi up to date Windows 10 installs and All Windows 11 installations and other systems that ship curl. `curl --header "Authorization: Bearer <access_token>" -X POST https://matrix.example.com/_synapse/admin/v1/users/@example:example.com/override_ratelimit` Replace `@example:example.com` with the MXID of your Draupnir and example.com with your homeserver domain. You can easily obtain an access token for a homeserver admin account the same way you can obtain an access token for Draupnir itself. If you made Draupnir Admin you can just use the Draupnir token.
-
-
-
-## 4. Create a management room
+### Create a management room
 
 Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room.
 
-If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see below).
+If you make the management room encrypted (E2EE), then you need to enable the native E2EE support (see [below](#native-e2ee-support)).
 
-Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`.
+Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`.
 
-Finally invite the `@bot.draupnir:example.com` account you created earlier into the room.
+Finally invite the `@bot.draupnir:example.com` account that the playbook will create for you to the management room. Please note that clients can issue a warning that your attempting to invite a user that doesnt have a profile and might not exist. This warning is expected as your inviting the bot before its user account exists.
 
+## End-to-End Encryption support
 
-## 5. Adjusting the playbook configuration
+Decide whether you want to support having an Encrypted management room or not. Draupnir can still protect encrypted rooms without encryption support enabled.
 
-Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms. To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md).
+Refer to Draupnir's [Documentation](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#protecting-encrypted-rooms) for more information on why you might or might not care about encryption support for protected rooms.
 
-### 5a. Configuration with E2EE support
+**Note**: Draupnir does not support running with Pantalaimon as it would break all workflows that involve answering prompts with reactions.
 
-When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password.
+### Native E2EE support
 
-Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):
+To enable the native E2EE support, you need to obtain an access token for Draupnir.
+
+Note that native E2EE requires a clean access token that has not touched E2EE so curl is recommended as a method to obtain it. **The access token obtained via Element Web does not work with it**. Refer to the documentation on [how to obtain an access token via curl](obtaining-access-tokens.md#obtain-an-access-token-via-curl).
+
+To enable the native E2EE support, add the following configuration to your `vars.yml` file:
 
 ```yaml
-# Enable Pantalaimon. See docs/configuring-playbook-pantalaimon.md
-matrix_pantalaimon_enabled: true
+# Enables the native E2EE Support
+matrix_bot_draupnir_enable_experimental_rust_crypto: true
 
+# Access Token the bot uses to login.
+# Comment out `matrix_bot_draupnir_login_native` when using this option.
+matrix_bot_draupnir_access_token: "ACCESS_TOKEN_HERE"
+```
+
+## Adjusting the playbook configuration
+
+To enable the bot, add the following configuration to your `vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`.
+
+```yaml
 # Enable Draupnir
 matrix_bot_draupnir_enabled: true
 
-# Tell Draupnir to use Pantalaimon
-matrix_bot_draupnir_pantalaimon_use: true
+# Uncomment and adjust this part if you'd like to use a username different than the default
+# matrix_bot_draupnir_login: bot.draupnir
 
-# User name and password for the bot. Required when using Pantalaimon.
-matrix_bot_draupnir_pantalaimon_username: "DRAUPNIR_USERNAME_FROM_STEP_1"
-matrix_bot_draupnir_pantalaimon_password: ### you should create a secure password for the bot account
+# Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`.
+# If creating the user on your own and using `matrix_bot_draupnir_access_token` to login you can comment out this line.
+matrix_bot_draupnir_password: PASSWORD_FOR_THE_BOT
 
-matrix_bot_draupnir_management_room: "ROOM_ID_FROM_STEP_4_GOES_HERE"
+# Comment out if using `matrix_bot_draupnir_enable_experimental_rust_crypto: true` or `matrix_bot_draupnir_access_token` to login.
+matrix_bot_draupnir_login_native: true
+
+matrix_bot_draupnir_management_room: "MANAGEMENT_ROOM_ID_HERE"
 ```
 
-The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Draupnir uses to reach the homeserver, one through Pantalaimon and one "raw". This example is taken from the playbook's `group_vars`:
+Before Proceeding run the playbook with the following command to make sure the Draupnir user has been created.
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created
+```
+
+### Make sure the account is free from rate limiting
+
+If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a heavily recomended step. If you do not configure it, Draupnir performance will be degraded.**
+
+This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally.
+
+To expose the APIs publicly, add the following configuration to your `vars.yml` file:
 
 ```yaml
-# Endpoint URL that Draupnir uses to interact with the Matrix homeserver (client-server API).
-# Set this to the pantalaimon URL if you're using that.
-matrix_bot_draupnir_homeserver_url: "{{ 'http://matrix-pantalaimon:8009' if matrix_bot_draupnir_pantalaimon_use else matrix_addons_homeserver_client_api_url }}"
-
-# Endpoint URL that Draupnir could use to fetch events related to reports (client-server API and /_synapse/),
-# only set this to the public-internet homeserver client API URL, do NOT set this to the pantalaimon URL.
-matrix_bot_draupnir_raw_homeserver_url: "{{ matrix_addons_homeserver_client_api_url }}"
+matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true
 ```
 
-### 5b. Configuration without E2EE support
+The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md).
 
-When NOT using Pantalaimon, Draupnir does not log in by itself and you must give it an access token for its bot account.
+**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints).
 
-Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):
+To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir:
 
-You must replace `ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and `ROOM_ID_FROM_STEP_4_GOES_HERE` with the your own values.
+```sh
+curl --header "Authorization: Bearer <access_token>" -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.draupnir:example.com/override_ratelimit
+```
+
+### Obtain an access token
+
+Manual access to Synapse's Admin API requires an access token. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md).
+
+⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.
+
+### Abuse Reports
+
+Draupnir can receive reports in the management room.
+
+The bot can intercept the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using Traefik, this playbook can set this up for you:
 
 ```yaml
-matrix_bot_draupnir_enabled: true
-
-matrix_bot_draupnir_access_token: "ACCESS_TOKEN_FROM_STEP_2_GOES_HERE"
-
-matrix_bot_draupnir_management_room: "ROOM_ID_FROM_STEP_4_GOES_HERE"
+matrix_bot_draupnir_abuse_reporting_enabled: true
 ```
 
-### 5c. Migrating from Mjolnir (Only required if migrating.)
+<!--
+NOTE: this is unsupported by the playbook due to the admin API being inaccessible from containers currently.
+
+The other method polls an Synapse Admin API endpoint, hence it is available only if using Synapse and if the Draupnir user is an admin (see [above](#register-the-bot-account)). To enable it, set `pollReports: true` on `vars.yml` file as below. 
+-->
+
+### Extending the configuration
+
+You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable.
+
+For example, to change Draupnir's `acceptInvitesFromSpace` option to `!qporfwt:example.com`, add the following configuration to your `vars.yml` file:
+
+```yaml
+matrix_bot_draupnir_configuration_extension_yaml: |
+  # Your custom YAML configuration goes here.
+  # This configuration extends the default starting configuration (`matrix_bot_draupnir_configuration_yaml`).
+  #
+  # You can override individual variables from the default configuration, or introduce new ones.
+  #
+  # If you need something more special, you can take full control by
+  # completely redefining `matrix_bot_draupnir_configuration_yaml`.
+  acceptInvitesFromSpace: "!qporfwt:example.com"
+```
+
+### Migrating from Mjolnir (Only required if migrating)
 
 Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration.
 
+Note that Pantalaimon is unsupported by Draupnir so it is recommended to consult the instructions to enable [the native E2EE support](#native-e2ee-support).
+
 That is all you need to do due to that Draupnir can complete migration on its own.
 
-## 6. Installing
+## Installing
 
-After configuring the playbook, run the [installation](installing.md) command:
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-```
-ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
 ```
 
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
@@ -166,7 +202,7 @@ The simplest and most useful entity to target is `user`. Below are a few example
 
 To create rules, you run commands in the Management Room (**not** in the policy list room).
 
-- (ban a single user on a given homeserver): `!draupnir ban @someone:example.com my-bans Rude to others`
+- (ban a single user on a given homeserver): `!draupnir ban @charles:example.com my-bans Rude to others`
 - (ban all users on a given homeserver by using a [wildcard](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - all users are fake`
 
 As a result of running these commands, you may observe:
@@ -182,46 +218,10 @@ You can also **turn on various built-in [protections](https://the-draupnir-proje
 
 To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room.
 
-To **see the configuration options for a given protection**, send a `!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get JoinWaveShortCircuit`).
+To **see the configuration options for a given protection**, send a `!draupnir protections show PROTECTION_NAME` (e.g. `!draupnir protections show JoinWaveShortCircuit`).
 
 To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`).
 
 To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`).
 
 To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`).
-
-
-## Extending the configuration
-
-You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file.
-
-For example to change draupnir's `recordIgnoredInvites` option to `true` you would add the following to your `vars.yml` file.
-
-```yaml
-matrix_bot_draupnir_configuration_extension_yaml: |
-  # Your custom YAML configuration goes here.
-  # This configuration extends the default starting configuration (`matrix_bot_draupnir_configuration_yaml`).
-  #
-  # You can override individual variables from the default configuration, or introduce new ones.
-  #
-  # If you need something more special, you can take full control by
-  # completely redefining `matrix_bot_draupnir_configuration_yaml`.
-  recordIgnoredInvites: true
-```
-
-## Abuse Reports
-
-Draupnir supports two methods to receive reports in the management room.
-
-The first method intercepts the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using traefik, this playbook can set this up for you:
-
-```yaml
-matrix_bot_draupnir_abuse_reporting_enabled: true
-```
-
-The other method polls an synapse admin API endpoint and is hence only available when using synapse and when the Draupnir user is an admin user (see step 1). To enable it, set `pollReports: true` in Draupnir's config:
-
-```yaml
-matrix_bot_draupnir_configuration_extension_yaml: |
-  pollReports: true
-```
diff --git a/docs/configuring-playbook-bot-go-neb.md b/docs/configuring-playbook-bot-go-neb.md
index 767998450..cd6e875cd 100644
--- a/docs/configuring-playbook-bot-go-neb.md
+++ b/docs/configuring-playbook-bot-go-neb.md
@@ -1,32 +1,42 @@
-# Setting up Go-NEB (optional)
+# Setting up Go-NEB (optional, unmaintained)
+
+**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an archived (**unmaintained**) project. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bot instead of this one.
 
 The playbook can install and configure [Go-NEB](https://github.com/matrix-org/go-neb) for you.
 
 Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, the original Matrix bot written in Python.
 
-See the project's [documentation](https://github.com/matrix-org/go-neb) to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/matrix-org/go-neb/blob/master/README.md) to learn what it does and why it might be useful to you.
 
+## Prerequisites
 
-## Registering the bot user
+### Register the bot account
 
-The playbook does not automatically create users for you. The bot requires at least 1 access token to be able to connect to your homeserver.
+The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot.
 
-You **need to register the bot user manually** before setting up the bot.
-
-Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`.
+Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`.
 
 You can use the playbook to [register a new user](registering-users.md):
 
-```
+```sh
 ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.go-neb password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user
 ```
 
-Once the user is created you can [obtain an access token](obtaining-access-tokens.md).
+### Obtain an access token
 
+The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md).
+
+⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.
+
+## Adjusting DNS records
+
+By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to create a CNAME record for `goneb`, which targets `matrix.example.com`.
+
+When setting, replace `example.com` with your own.
 
 ## Adjusting the playbook configuration
 
-To enable Go-NEB, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_GONEB_HERE` and `ACCESS_TOKEN_FOR_ANOTHER_GONEB_HERE` with the ones created [above](#obtain-an-access-token).
 
 ```yaml
 matrix_bot_go_neb_enabled: true
@@ -35,7 +45,7 @@ matrix_bot_go_neb_enabled: true
 # Use the access token you obtained in the step above.
 matrix_bot_go_neb_clients:
   - UserID: "@goneb:{{ matrix_domain }}"
-    AccessToken: "MDASDASJDIASDJASDAFGFRGER"
+    AccessToken: "ACCESS_TOKEN_FOR_GONEB_HERE"
     DeviceID: "DEVICE1"
     HomeserverURL: "{{ matrix_addons_homeserver_client_api_url }}"
     Sync: true
@@ -44,7 +54,7 @@ matrix_bot_go_neb_clients:
     AcceptVerificationFromUsers: [":{{ matrix_domain }}"]
 
   - UserID: "@another_goneb:{{ matrix_domain }}"
-    AccessToken: "MDASDASJDIASDJASDAFGFRGER"
+    AccessToken: "ACCESS_TOKEN_FOR_ANOTHER_GONEB_HERE"
     DeviceID: "DEVICE2"
     HomeserverURL: "{{ matrix_addons_homeserver_client_api_url }}"
     Sync: false
@@ -62,7 +72,7 @@ matrix_bot_go_neb_realms:
 matrix_bot_go_neb_sessions:
   - SessionID: "your_github_session"
     RealmID: "github_realm"
-    UserID: "@YOUR_USER_ID:{{ matrix_domain }}" # This needs to be the username of the person that's allowed to use the !github commands
+    UserID: "@alice:{{ matrix_domain }}" # This needs to be the username of the person that's allowed to use the !github commands
     Config:
       # Populate these fields by generating a "Personal Access Token" on github.com
       AccessToken: "YOUR_GITHUB_ACCESS_TOKEN"
@@ -105,7 +115,7 @@ matrix_bot_go_neb_services:
       api_key: "AIzaSyA4FD39m9"
       cx: "AIASDFWSRRtrtr"
 
-# Get a key via https://api.imgur.com/oauth2/addclient
+# Obtain a key via https://api.imgur.com/oauth2/addclient
 # Select "oauth2 without callback url"
   - ID: "imgur_service"
     Type: "imgur"
@@ -149,7 +159,7 @@ matrix_bot_go_neb_services:
     UserID: "@another_goneb:{{ matrix_domain }}"
     Config:
       RealmID: "github_realm"
-      ClientUserID: "@YOUR_USER_ID:{{ matrix_domain }}" # needs to be an authenticated user so Go-NEB can create webhooks. Check the UserID field in the github_realm in matrix_bot_go_neb_sessions.
+      ClientUserID: "@alice:{{ matrix_domain }}" # needs to be an authenticated user so Go-NEB can create webhooks. Check the UserID field in the github_realm in matrix_bot_go_neb_sessions.
       Rooms:
         "!qporfwt:example.com":
           Repos:
@@ -190,46 +200,48 @@ matrix_bot_go_neb_services:
           msg_type: "m.text"  # Must be either `m.text` or `m.notice`
 ```
 
-### Adjusting the Go-NEB URL
-
-By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records).
+### Adjusting the Go-NEB URL (optional)
 
 By tweaking the `matrix_bot_go_neb_hostname` and `matrix_bot_go_neb_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Switch to the domain used for Matrix services (`matrix.example.com`),
 # so we won't need to add additional DNS records for Go-NEB.
 matrix_bot_go_neb_hostname: "{{ matrix_server_fqn_matrix }}"
 
-# Expose under the /buscarron subpath
+# Expose under the /go-neb subpath
 matrix_bot_go_neb_path_prefix: /go-neb
 ```
 
-## Adjusting DNS records
-
-Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Go-NEB domain to the Matrix server.
-
-By default, you will need to create a CNAME record for `goneb`. See [Configuring DNS](configuring-dns.md) for details about DNS changes.
+After changing the domain, **you may need to adjust your DNS** records to point the Go-NEB domain to the Matrix server.
 
 If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command:
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
 
-```
-ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
 ```
 
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
-To use the bot, invite it to any existing Matrix room (`/invite @whatever_you_chose:example.com` where `example.com` is your base domain, not the `matrix.` domain, make sure you have permission from the room owner if that's not you).
+To use the bot, invite it to any existing Matrix room (`/invite @bot.go-neb:example.com` where `example.com` is your base domain, not the `matrix.` domain). Make sure you are granted with the sufficient permission if you are not the room owner.
 
 Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy matrix`
 
-If you enabled the github_cmd service you can get the supported commands via `!github help`
+If you enabled the github_cmd service, send `!github help` to the bot in the room to see the available commands.
 
 You can also refer to the upstream [Documentation](https://github.com/matrix-org/go-neb).
diff --git a/docs/configuring-playbook-bot-honoroit.md b/docs/configuring-playbook-bot-honoroit.md
index 982c7ca0a..d89aa7152 100644
--- a/docs/configuring-playbook-bot-honoroit.md
+++ b/docs/configuring-playbook-bot-honoroit.md
@@ -4,12 +4,17 @@ The playbook can install and configure [Honoroit](https://github.com/etkecc/hono
 
 It's a bot you can use to setup **your own helpdesk on matrix**
 
-See the project's [documentation](https://github.com/etkecc/honoroit#how-it-looks-like) to learn what it does with screenshots and why it might be useful to you.
+See the project's [documentation](https://github.com/etkecc/honoroit/blob/main/README.md) to learn what it does and why it might be useful to you.
 
+## Adjusting DNS records (optional)
+
+By default, this playbook installs Honoroit on the `matrix.` subdomain, at the `/honoroit` path (https://matrix.example.com/honoroit). 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.
+
+If you wish to adjust it, see the section [below](#adjusting-the-honoroit-url-optional) for details about DNS configuration.
 
 ## Adjusting the playbook configuration
 
-To enable Honoroit, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
 ```yaml
 matrix_bot_honoroit_enabled: true
@@ -17,20 +22,18 @@ matrix_bot_honoroit_enabled: true
 # Uncomment and adjust this part if you'd like to use a username different than the default
 # matrix_bot_honoroit_login: honoroit
 
-# Generate a strong password here. Consider generating it with `pwgen -s 64 1`
+# Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`.
 matrix_bot_honoroit_password: PASSWORD_FOR_THE_BOT
 
 # Adjust this to your room ID
 matrix_bot_honoroit_roomid: "!qporfwt:{{ matrix_domain }}"
 ```
 
-### Adjusting the Honoroit URL
-
-By default, this playbook installs Honoroit on the `matrix.` subdomain, at the `/honoroit` path (https://matrix.example.com/honoroit). 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.
+### Adjusting the Honoroit URL (optional)
 
 By tweaking the `matrix_bot_honoroit_hostname` and `matrix_bot_honoroit_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Change the default hostname and path prefix
@@ -38,33 +41,35 @@ matrix_bot_honoroit_hostname: honoroit.example.com
 matrix_bot_honoroit_path_prefix: /
 ```
 
-## Adjusting DNS records
+If you've changed the default hostname, you may need to create a CNAME record for the Honoroit domain (`honoroit.example.com`), which targets `matrix.example.com`.
 
-If you've changed the default hostname, **you may need to adjust your DNS** records to point the Honoroit domain to the Matrix server.
-
-See [Configuring DNS](configuring-dns.md) for details about DNS changes.
-
-If you've decided to use the default hostname, you won't need to do any extra DNS configuration.
+When setting, replace `example.com` with your own.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command:
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
 
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
 ```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
 ```
 
 **Notes**:
 
-- the `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-- if you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
+  `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.
+
+- If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password.
 
 ## Usage
 
-To use the bot, invite the `@honoroit:example.com` to the room you specified in config, after that any Matrix user can send a message to the `@honoroit:example.com` to start a new thread in that room.
+To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @honoroit:example.com` where `example.com` is your base domain, not the `matrix.` domain).
 
-Send `!ho help` to the room to see the bot's help menu for additional commands.
+After the bot joins the room, any Matrix user can send a message to it to start a new thread in that room.
+
+Send `!ho help` to the bot in the room to see the available commands.
 
 You can also refer to the upstream [documentation](https://github.com/etkecc/honoroit#features).
diff --git a/docs/configuring-playbook-bot-matrix-registration-bot.md b/docs/configuring-playbook-bot-matrix-registration-bot.md
index 6583a92e0..95b86163f 100644
--- a/docs/configuring-playbook-bot-matrix-registration-bot.md
+++ b/docs/configuring-playbook-bot-matrix-registration-bot.md
@@ -4,10 +4,9 @@ The playbook can install and configure [matrix-registration-bot](https://github.
 
 The bot allows you to easily **create and manage registration tokens** aka. invitation codes. It can be used for an invitation-based server, where you invite someone by sending them a registration token (tokens look like this: `rbalQ0zkaDSRQCOp`). They can register as per normal but have to provide a valid registration token in the final step of the registration process.
 
-See the project's [documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands) to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/moan0s/matrix-registration-bot/blob/master/README.md) to learn what it does and why it might be useful to you.
 
-
-## Configuration
+## Adjusting the playbook configuration
 
 To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
@@ -18,7 +17,7 @@ matrix_bot_matrix_registration_bot_enabled: true
 # Uncomment and adjust this part if you'd like to use a username different than the default
 # matrix_bot_matrix_registration_bot_matrix_user_id_localpart: bot.matrix-registration-bot
 
-# Generate a strong password here. Consider generating it with `pwgen -s 64 1`
+# Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`.
 matrix_bot_matrix_registration_bot_bot_password: PASSWORD_FOR_THE_BOT
 
 # Enables registration
@@ -32,20 +31,35 @@ The bot account will be created automatically.
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
+
+- If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password.
 
 ## Usage
 
 To use the bot, start a chat with `@bot.matrix-registration-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
 
-In this room send `help` and the bot will reply with all options.
+Send `help` to the bot to see the available commands.
 
 You can also refer to the upstream [Usage documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands).
 
 If you have any questions, or if you need help setting it up, read the [troublshooting guide](https://github.com/moan0s/matrix-registration-bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de).
 
-To clean the cache (session & encryption data) after you changed the bot's username, changed the login method from access_token to password etc... you can use:
+To clean the cache (session & encryption data) after you changed the bot's username, changed the login method from access_token to password etc… you can use:
 
-```bash
+```sh
 just run-tags bot-matrix-registration-bot-clean-cache
 ```
diff --git a/docs/configuring-playbook-bot-matrix-reminder-bot.md b/docs/configuring-playbook-bot-matrix-reminder-bot.md
index 2bce34765..d82c3eae1 100644
--- a/docs/configuring-playbook-bot-matrix-reminder-bot.md
+++ b/docs/configuring-playbook-bot-matrix-reminder-bot.md
@@ -4,12 +4,11 @@ The playbook can install and configure [matrix-reminder-bot](https://github.com/
 
 It's a bot you can use to **schedule one-off & recurring reminders and alarms**.
 
-See the project's [documentation](https://github.com/anoadragon453/matrix-reminder-bot#usage) to learn what it does and why it might be useful to you.
-
+See the project's [documentation](https://github.com/anoadragon453/matrix-reminder-bot/blob/master/README.md) to learn what it does and why it might be useful to you.
 
 ## Adjusting the playbook configuration
 
-Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
 ```yaml
 matrix_bot_matrix_reminder_bot_enabled: true
@@ -17,28 +16,31 @@ matrix_bot_matrix_reminder_bot_enabled: true
 # Uncomment and adjust this part if you'd like to use a username different than the default
 # matrix_bot_matrix_reminder_bot_matrix_user_id_localpart: bot.matrix-reminder-bot
 
-# Generate a strong password here. Consider generating it with `pwgen -s 64 1`
+# Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`.
 matrix_bot_matrix_reminder_bot_matrix_user_password: PASSWORD_FOR_THE_BOT
 
 # Adjust this to your timezone
 matrix_bot_matrix_reminder_bot_reminders_timezone: Europe/London
 ```
 
-
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command:
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
 ```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
 ```
 
 **Notes**:
 
-- the `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-- if you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
+  `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.
+
+- If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password.
 
 ## Usage
 
diff --git a/docs/configuring-playbook-bot-maubot.md b/docs/configuring-playbook-bot-maubot.md
index 31714e38a..0436de588 100644
--- a/docs/configuring-playbook-bot-maubot.md
+++ b/docs/configuring-playbook-bot-maubot.md
@@ -6,9 +6,15 @@ After setting up maubot, you can use the web management interface to make it do
 
 See the project's [documentation](https://docs.mau.fi/maubot/usage/basic.html) to learn what it does and why it might be useful to you.
 
+## Adjusting DNS records (optional)
+
+By default, this playbook installs maubot on the `matrix.` subdomain, at the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**.
+
+If you wish to adjust it, see the section [below](#adjusting-the-maubot-url-optional) for details about DNS configuration.
+
 ## Adjusting the playbook configuration
 
-To enable maubot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
 ```yaml
 matrix_bot_maubot_enabled: true
@@ -16,7 +22,7 @@ matrix_bot_maubot_enabled: true
 # Uncomment and adjust this part if you'd like to use a username different than the default
 # matrix_bot_maubot_login: bot.maubot
 
-# Generate a strong password here. Consider generating it with `pwgen -s 64 1`
+# Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`.
 matrix_bot_maubot_initial_password: PASSWORD_FOR_THE_BOT
 
 matrix_bot_maubot_admins:
@@ -25,13 +31,11 @@ matrix_bot_maubot_admins:
 
 You can add multiple admins. The admin accounts are only used to access the maubot administration interface.
 
-### Adjusting the maubot URL
-
-By default, this playbook installs maubot on the `matrix.` subdomain, at the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/). 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.
+### Adjusting the maubot URL (optional)
 
 By tweaking the `matrix_bot_maubot_hostname` and `matrix_bot_maubot_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Change the default hostname and path prefix
@@ -39,21 +43,47 @@ matrix_bot_maubot_hostname: maubot.example.com
 matrix_bot_maubot_path_prefix: /
 ```
 
-## Adjusting DNS records
+If you've changed the default hostname, you may need to create a CNAME record for the maubot domain (`maubot.example.com`), which targets `matrix.example.com`.
 
-If you've changed the default hostname, **you may need to adjust your DNS** records to point the maubot domain to the Matrix server.
+When setting, replace `example.com` with your own.
 
-See [Configuring DNS](configuring-dns.md) for details about DNS changes.
+## Customizing the maubot container image
 
-If you've decided to use the default hostname, you won't need to do any extra DNS configuration.
+Certain [maubot plugins](https://plugins.mau.bot/) require additional dependencies to be installed.
+
+You can customize the default maubot container image and install your own dependencies.
+
+Example additional configuration for your `vars.yml` file:
+
+```yaml
+matrix_bot_maubot_container_image_customizations_enabled: true
+
+# Adjust the Dockerfile and install ffmpeg.
+#
+matrix_bot_maubot_container_image_customizations_dockerfile_body_custom: |
+  RUN apk add --no-cache ffmpeg
+```
+
+Consult the [Dockerfile reference](https://docs.docker.com/reference/dockerfile/) for more information about the syntax.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all`
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
 
 **Notes**:
 
-- if you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
+
+- If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password.
 
 ## Usage
 
@@ -64,8 +94,10 @@ You should start in the following order
 2. **Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source.
 3. **Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)
 
-## Obtaining an access token
+## Obtain an access token
 
 This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`.
 
-Alternatively, you can follow our generic [obtain an access token](obtaining-access-tokens.md) documentation. Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element**) as the latter will give your bot issues in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients).
+Alternatively, you can refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will causes issues to your bot in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients).
+
+⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.
diff --git a/docs/configuring-playbook-bot-mjolnir.md b/docs/configuring-playbook-bot-mjolnir.md
index be2e6060e..c7a211491 100644
--- a/docs/configuring-playbook-bot-mjolnir.md
+++ b/docs/configuring-playbook-bot-mjolnir.md
@@ -2,75 +2,97 @@
 
 The playbook can install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation bot for you.
 
-See the project's [documentation](https://github.com/matrix-org/mjolnir) to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/matrix-org/mjolnir/blob/main/README.md) to learn what it does and why it might be useful to you.
 
+## Prerequisites
 
-## 1. Register the bot account
+### Register the bot account
 
-The playbook does not automatically create users for you. The bot requires an access token to be able to connect to your homeserver.
+The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot.
 
-You **need to register the bot user manually** before setting up the bot.
-
-Choose a strong password for the bot. You can generate a good password with a command like this: `pwgen -s 64 1`.
+Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`.
 
 You can use the playbook to [register a new user](registering-users.md):
 
-```
+```sh
 ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=bot.mjolnir password=PASSWORD_FOR_THE_BOT admin=no' --tags=register-user
 ```
 
 If you would like Mjolnir to be able to deactivate users, move aliases, shutdown rooms, etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above.
 
+### Obtain an access token
 
-## 2. Get an access token
+The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md).
 
-Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md).
+⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.
 
+### Make sure the account is free from rate limiting
 
-## 3. Make sure the account is free from rate limiting
+If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.**
 
-You will need to prevent Synapse from rate limiting the bot's account. This is not an optional step. If you do not do this step Mjolnir will crash. This can be done using Synapse's [admin API](https://matrix-org.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). Please ask for help if you are uncomfortable with these steps or run into issues.
+This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally.
 
-If your Synapse Admin API is exposed to the internet for some reason like running the Synapse Admin Role [Link](/docs/configuring-playbook-synapse-admin.md) or running `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` in your playbook config. If your API is not externally exposed you should still be able to on the local host for your synapse run these commands.
+To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
-The following command works on semi up to date Windows 10 installs and All Windows 11 installations and other systems that ship curl. `curl --header "Authorization: Bearer <access_token>" -X POST https://matrix.example.com/_synapse/admin/v1/users/@example:example.com/override_ratelimit` Replace `@example:example.com` with the MXID of your Mjolnir and example.com with your homeserver domain. You can easily obtain an access token for a homeserver admin account the same way you can obtain an access token for Mjolnir itself. If you made Mjolnir Admin you can just use the Mjolnir token.
+```yaml
+matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true
+```
 
-## 4. Create a management room
+The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md).
+
+**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints).
+
+To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir:
+
+```sh
+curl --header "Authorization: Bearer <access_token>" -X POST https://matrix.example.com/_synapse/admin/v1/users/@bot.mjolnir:example.com/override_ratelimit
+```
+
+You can obtain an access token for a homeserver admin account in the same way as you can do so for Mjolnir itself. If you have made Mjolnir an admin, you can just use the Mjolnir token.
+
+### Create a management room
 
 Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room.
 
-If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see below).
+If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support)).
 
-Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`.
+Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`.
 
 Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room.
 
+## Adjusting the playbook configuration
 
-## 5. Adjusting the playbook configuration
+To enable the bot, add the following configuration to your `vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`.
 
-Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms. To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md).
+```yaml
+# Enable Mjolnir
+matrix_bot_mjolnir_enabled: true
 
-### 5a. Configuration with E2EE support
+matrix_bot_mjolnir_management_room: "MANAGEMENT_ROOM_ID_HERE"
+```
+
+### End-to-End Encryption support
+
+Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms.
+
+To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md).
+
+#### Configuration with E2EE support
 
 When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password.
 
-Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):
+Add the following configuration to your `vars.yml` file (adapt to your needs):
 
 ```yaml
 # Enable Pantalaimon. See docs/configuring-playbook-pantalaimon.md
 matrix_pantalaimon_enabled: true
 
-# Enable Mjolnir
-matrix_bot_mjolnir_enabled: true
-
 # Tell Mjolnir to use Pantalaimon
 matrix_bot_mjolnir_pantalaimon_use: true
 
-# User name and password for the bot. Required when using Pantalaimon.
-matrix_bot_mjolnir_pantalaimon_username: "MJOLNIR_USERNAME_FROM_STEP_1"
-matrix_bot_mjolnir_pantalaimon_password: ### you should create a secure password for the bot account
-
-matrix_bot_mjolnir_management_room: "ROOM_ID_FROM_STEP_4_GOES_HERE"
+# User name and password for the bot you have created above. Required when using Pantalaimon.
+matrix_bot_mjolnir_pantalaimon_username: "bot.mjolnir"
+matrix_bot_mjolnir_pantalaimon_password: "PASSWORD_FOR_THE_BOT"
 ```
 
 The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Mjolnir uses to reach the homeserver, one through Pantalaimon and one "raw". This example is taken from the playbook's `group_vars`:
@@ -85,26 +107,19 @@ matrix_bot_mjolnir_homeserver_url: "{{ 'http://matrix-pantalaimon:8009' if matri
 matrix_bot_mjolnir_raw_homeserver_url: "{{ matrix_addons_homeserver_client_api_url }}"
 ```
 
-### 5b. Configuration without E2EE support
+#### Configuration without E2EE support
 
 When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account.
 
-Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):
-
-You must replace `ACCESS_TOKEN_FROM_STEP_2_GOES_HERE` and `ROOM_ID_FROM_STEP_4_GOES_HERE` with the your own values.
+Add the following configuration to your `vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token).
 
 ```yaml
-matrix_bot_mjolnir_enabled: true
-
-matrix_bot_mjolnir_access_token: "ACCESS_TOKEN_FROM_STEP_2_GOES_HERE"
-
-matrix_bot_mjolnir_management_room: "ROOM_ID_FROM_STEP_4_GOES_HERE"
+matrix_bot_mjolnir_access_token: "ACCESS_TOKEN_HERE"
 ```
 
-## 6. Adding Mjolnir synapse antispam module (optional)
-
-Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):
+### Adding Mjolnir synapse antispam module (optional)
 
+To enable Mjolnir synapse antispam module, add the following configuration to your `vars.yml` file (adapt to your needs):
 
 ```yaml
 matrix_synapse_ext_spam_checker_mjolnir_antispam_enabled: true
@@ -114,23 +129,11 @@ matrix_synapse_ext_spam_checker_mjolnir_antispam_config_block_usernames: false
 matrix_synapse_ext_spam_checker_mjolnir_antispam_config_ban_lists: []
 ```
 
-
-## 7. Installing
-
-After configuring the playbook, run the [installation](installing.md) command:
-
-```
-ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
-```
-
-
-## Usage
-
-You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot.
+### Extending the configuration
 
 You can configure additional options by adding the `matrix_bot_mjolnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file.
 
-For example to change Mjolnir's `recordIgnoredInvites` option to `true` you would add the following to your `vars.yml` file.
+For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `vars.yml` file:
 
 ```yaml
 matrix_bot_mjolnir_configuration_extension_yaml: |
@@ -143,3 +146,26 @@ matrix_bot_mjolnir_configuration_extension_yaml: |
   # completely redefining `matrix_bot_mjolnir_configuration_yaml`.
   recordIgnoredInvites: true
 ```
+
+## Installing
+
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
+
+- If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password.
+
+## Usage
+
+You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot.
diff --git a/docs/configuring-playbook-bot-postmoogle.md b/docs/configuring-playbook-bot-postmoogle.md
deleted file mode 100644
index 9de3ac035..000000000
--- a/docs/configuring-playbook-bot-postmoogle.md
+++ /dev/null
@@ -1,83 +0,0 @@
-# Setting up Postmoogle (optional)
-
-**Note**: email bridging can also happen via the [email2matrix](configuring-playbook-email2matrix.md) bridge supported by the playbook.
-
-The playbook can install and configure [Postmoogle](https://github.com/etkecc/postmoogle) for you.
-
-Postmoogle is a bot/bridge you can use to forward emails to Matrix rooms. It runs an SMTP email server and allows you to assign mailbox addresses to Matrix rooms.
-
-See the project's [documentation](https://github.com/etkecc/postmoogle) to learn what it does and why it might be useful to you.
-
-## Prerequisites
-
-Open the following ports on your server to be able to receive incoming emails:
-
-  - `25/tcp`: SMTP
-  - `587/tcp`: Submission (TLS-encrypted SMTP)
-
-If you don't open these ports, you will still be able to send emails, but not receive any.
-
-These port numbers are configurable via the `matrix_bot_postmoogle_smtp_host_bind_port` and `matrix_bot_postmoogle_submission_host_bind_port` variables, but other email servers will try to deliver on these default (standard) ports, so changing them is of little use.
-
-
-## Adjusting the playbook configuration
-
-Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
-
-```yaml
-matrix_bot_postmoogle_enabled: true
-
-# Uncomment and adjust this part if you'd like to use a username different than the default
-# matrix_bot_postmoogle_login: postmoogle
-
-# Generate a strong password here. Consider generating it with `pwgen -s 64 1`
-matrix_bot_postmoogle_password: PASSWORD_FOR_THE_BOT
-
-# Uncomment to add one or more admins to this bridge:
-#
-# matrix_bot_postmoogle_admins:
-#  - '@yourAdminAccount:{{ matrix_domain }}'
-#
-# .. unless you've made yourself an admin of all bots/bridges like this:
-#
-# matrix_admin: '@yourAdminAccount:{{ matrix_domain }}'
-```
-
-## Adjusting DNS records
-
-You will also need to add several DNS records so that Postmoogle can send emails. See [Configuring DNS](configuring-dns.md) for details about DNS changes.
-
-## Installing
-
-After configuring the playbook, run the [installation](installing.md) command:
-
-```sh
-ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
-```
-
-**Notes**:
-
-- the `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account
-
-- if you change the bot password (`matrix_bot_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_postmoogle_password` to let the bot know its new password
-
-
-## Usage
-
-To use the bot, invite the `@postmoogle:example.com` bot user into a room you want to use as a mailbox.
-
-Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with the email address `NAME@matrix.example.com`. Emails sent to that email address will be forwarded to the room.
-
-Send `!pm help` to the room to see the bot's help menu for additional commands.
-
-You can also refer to the upstream [documentation](https://github.com/etkecc/postmoogle).
-
-### Debug/Logs
-
-As with all other services, you can find their logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-bot-postmoogle`
-
-The default logging level for this bridge is `INFO`, but you can increase it to `DEBUG` with the following additional configuration:
-
-```yaml
-matrix_bot_postmoogle_loglevel: 'DEBUG'
-```
diff --git a/docs/configuring-playbook-bridge-appservice-discord.md b/docs/configuring-playbook-bridge-appservice-discord.md
index 0eaad761c..5368db974 100644
--- a/docs/configuring-playbook-bridge-appservice-discord.md
+++ b/docs/configuring-playbook-bridge-appservice-discord.md
@@ -1,42 +1,53 @@
-# Setting up Appservice Discord (optional)
+# Setting up Appservice Discord bridging (optional)
 
 **Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook.
 - For using as a Bot we are recommend the Appservice Discord bridge (the one being discussed here), because it supports plumbing.
 - For personal use we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook.
 
-The playbook can install and configure [matrix-appservice-discord](https://github.com/Half-Shot/matrix-appservice-discord) for you.
+The playbook can install and configure [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord) for you.
 
-See the project's [documentation](https://github.com/Half-Shot/matrix-appservice-discord/blob/master/README.md) to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/matrix-org/matrix-appservice-discord/blob/master/README.md) to learn what it does and why it might be useful to you.
 
+## Prerequisites
 
-## Setup Instructions
+Create a Discord Application [here](https://discordapp.com/developers/applications). Then retrieve Client ID, and create a bot from the Bot tab and retrieve the Bot token.
 
-Instructions loosely based on [this](https://github.com/Half-Shot/matrix-appservice-discord#setting-up).
+## Adjusting the playbook configuration
 
-1. Create a Discord Application [here](https://discordapp.com/developers/applications).
-2. Retrieve Client ID.
-3. Create a bot from the Bot tab and retrieve the Bot token.
-4. Enable the bridge with the following configuration in your `vars.yml` file:
+To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
 ```yaml
 matrix_appservice_discord_enabled: true
 matrix_appservice_discord_client_id: "YOUR DISCORD APP CLIENT ID"
 matrix_appservice_discord_bot_token: "YOUR DISCORD APP BOT TOKEN"
-```
-5. As of Synapse 1.90.0, you will need to add the following to `matrix_synapse_configuration_extension_yaml` to enable the [backwards compatibility](https://matrix-org.github.io/synapse/latest/upgrade#upgrading-to-v1900) that this bridge needs:
-```yaml
-matrix_synapse_configuration_extension_yaml: |
-  use_appservice_legacy_authorization: true
-```
-**Note**: This deprecated method is considered insecure.
 
-6. If you've already installed Matrix services using the playbook before, you'll need to re-run it (`--tags=setup-all,start`). If not, proceed with [configuring other playbook services](configuring-playbook.md) and then with [Installing](installing.md). Get back to this guide once ready.
+# As of Synapse 1.90.0, uncomment to enable the backwards compatibility (https://matrix-org.github.io/synapse/latest/upgrade#upgrading-to-v1900) that this bridge needs.
+# Note: This deprecated method is considered insecure.
+#
+# matrix_synapse_configuration_extension_yaml: |
+#   use_appservice_legacy_authorization: true
+```
 
-Other configuration options are available via the `matrix_appservice_discord_configuration_extension_yaml` variable.
+## Installing
+
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Self-Service Bridging (Manual)
 
-Self-service bridging allows you to bridge specific and existing Matrix rooms to specific Discord rooms. This is disabled by default, so it must be enabled by adding this to your `vars.yml`:
+Self-service bridging allows you to bridge specific and existing Matrix rooms to specific Discord rooms. To enable it, add the following configuration to your `vars.yml` file:
 
 ```yaml
 matrix_appservice_discord_bridge_enableSelfServiceBridging: true
@@ -44,27 +55,32 @@ matrix_appservice_discord_bridge_enableSelfServiceBridging: true
 
 **Note**: If self-service bridging is not enabled, `!discord help` commands will return no results.
 
-Once self-service is enabled:
+### Usage
 
-1. Start a chat with `@_discord_bot:example.com` and say `!discord help bridge`.
-2. Follow the instructions in the help output message. If the bot is not already in the Discord server, follow the provided invite link. This may require you to be a administrator of the Discord server.
+Once self-service is enabled, start a chat with `@_discord_bot:example.com` and say `!discord help bridge`.
+
+Then, follow the instructions in the help output message.
+
+If the bot is not already in the Discord server, follow the provided invite link. This may require you to be a administrator of the Discord server.
+
+On the Discord side, send `!matrix help` to the bot to see the available commands for managing the bridge and Matrix users.
 
 **Note**: Encrypted Matrix rooms are not supported as of writing.
 
-On the Discord side, you can say `!matrix help` to get a list of available commands to manage the bridge and Matrix users.
-
 ## Portal Bridging (Automatic)
 
-Through portal bridging, Matrix rooms will automatically be created by the bot and bridged to the relevant Discord room. This is done by simply joining a room with a specific name pattern (`#_discord_<guildID>_<channlID>`).
+Through portal bridging, Matrix rooms will automatically be created by the bot and bridged to the relevant Discord room. This is done by simply joining a room with a specific name pattern (`#_discord_<guildID>_<channelID>`).
 
 All Matrix rooms created this way are **listed publicly** by default, and you will not have admin permissions to change this. To get more control, [make yourself a room Administrator](#getting-administrator-access-in-a-portal-bridged-room). You can then unlist the room from the directory and change the join rules.
 
-If you want to disable portal bridging, set the following in `vars.yml`:
+To disable portal bridging, add the following configuration to your `vars.yml` file:
 
 ```yaml
 matrix_appservice_discord_bridge_disablePortalBridging: true
 ```
 
+### Usage
+
 To get started with Portal Bridging:
 
 1. To invite the bot to Discord, retrieve the invite link from the `{{ matrix_appservice_discord_config_path }}/invite_link` file on the server (this defaults to `/matrix/appservice-discord/config/invite_link`). You need to peek at the file on the server via SSH, etc., because it's not available via HTTP(S).
@@ -77,9 +93,9 @@ By default, you won't have Administrator access in rooms created by the bridge.
 
 To adjust room access privileges or do various other things (change the room name subsequently, etc.), you'd wish to become an Administrator.
 
-There's the Discord bridge's guide for [setting privileges on bridge managed rooms](https://github.com/Half-Shot/matrix-appservice-discord/blob/master/docs/howto.md#set-privileges-on-bridge-managed-rooms). To do the same with our container setup, run the following command on the server:
+There's the Discord bridge's guide for [setting privileges on bridge managed rooms](https://github.com/matrix-org/matrix-appservice-discord/blob/master/docs/howto.md#set-privileges-on-bridge-managed-rooms). To do the same with our container setup, run the following command on the server:
 
 ```sh
 docker exec -it matrix-appservice-discord \
-/bin/sh -c 'cp /cfg/registration.yaml /tmp/discord-registration.yaml && cd /tmp && node /build/tools/adminme.js -c /cfg/config.yaml -m "!qporfwt:example.com" -u "@USER:example.com" -p 100'
+/bin/sh -c 'cp /cfg/registration.yaml /tmp/discord-registration.yaml && cd /tmp && node /build/tools/adminme.js -c /cfg/config.yaml -m "!qporfwt:example.com" -u "@alice:example.com" -p 100'
 ```
diff --git a/docs/configuring-playbook-bridge-appservice-irc.md b/docs/configuring-playbook-bridge-appservice-irc.md
index 82623b998..af4003f6d 100644
--- a/docs/configuring-playbook-bridge-appservice-irc.md
+++ b/docs/configuring-playbook-bridge-appservice-irc.md
@@ -1,4 +1,4 @@
-# Setting up Appservice IRC (optional)
+# Setting up Appservice IRC bridging (optional)
 
 **Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [Heisenbridge](configuring-playbook-bridge-heisenbridge.md) bridge supported by the playbook.
 
@@ -62,8 +62,21 @@ matrix_appservice_irc_ircService_servers:
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
-You then need to start a chat with `@irc_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `@irc_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
diff --git a/docs/configuring-playbook-bridge-appservice-kakaotalk.md b/docs/configuring-playbook-bridge-appservice-kakaotalk.md
index cbc52a6cc..af0955273 100644
--- a/docs/configuring-playbook-bridge-appservice-kakaotalk.md
+++ b/docs/configuring-playbook-bridge-appservice-kakaotalk.md
@@ -1,13 +1,22 @@
-# Setting up Appservice Kakaotalk (optional)
+# Setting up Appservice Kakaotalk bridging (optional)
 
-The playbook can install and configure [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) for you. `matrix-appservice-kakaotalk` is a bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code.
+The playbook can install and configure [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) for you, for bridging to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG). This bridge is based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code.
 
-**Note**: there have been recent reports (~2022-09-16) that **using this bridge may get your account banned**.
+See the project's [documentation](https://src.miscworks.net/fair/matrix-appservice-kakaotalk/src/branch/master/README.md) to learn what it does and why it might be useful to you.
 
-See the project's [documentation](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) to learn what it does and why it might be useful to you.
+⚠️ **Warning**: there have been recent reports (~2022-09-16) that **using this bridge may get your account banned**.
 
+## Prerequisite (optional)
 
-## Installing
+### Enable Shared Secret Auth
+
+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 [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook.
+
+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.
+
+**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future.
+
+## Adjusting the playbook configuration
 
 To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
@@ -15,20 +24,7 @@ To enable the bridge, add the following configuration to your `inventory/host_va
 matrix_appservice_kakaotalk_enabled: true
 ```
 
-You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation.
-
-## Installing
-
-After configuring the playbook, run the [installation](installing.md) command:
-
-```
-ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
-```
-
-To make use of the Kakaotalk bridge, see [Usage](#usage) below.
-
-
-### Additional configuration
+### Extending the configuration
 
 There are some additional things you may wish to configure about the bridge.
 
@@ -37,34 +33,25 @@ Take a look at:
 - `roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
 - `roles/custom/matrix-bridge-appservice-kakaotalk/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_kakaotalk_configuration_extension_yaml` variable
 
+## Installing
 
-### Set up Double Puppeting
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-If you'd like to use [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do), you have 2 ways of going about it.
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
 
-#### Method 1: automatically, by enabling Shared Secret Auth
+**Notes**:
 
-The bridge will automatically perform Double Puppeting if you enable [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook.
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
-
-#### Method 2: manually, by asking each user to provide a working access token
-
-**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging (see [Usage](#usage)).
-
-When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:
-
-- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md).
-
-- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`
-
-- make sure you don't log out the `Appservice-Kakaotalk` device some time in the future, as that would break the Double Puppeting feature
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
+  `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.
 
 ## Usage
 
-Start a chat with `@kakaotalkbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `@kakaotalkbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
 
-Send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable bridging for your Kakaotalk account. The `--save` flag may be omitted, if you'd rather not save your password.
-
-After successfully enabling bridging, you may wish to [set up Double Puppeting](#set-up-double-puppeting), if you haven't already done so.
+You then need to send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable bridging for your Kakaotalk account. The `--save` flag may be omitted, if you'd rather not save your password.
diff --git a/docs/configuring-playbook-bridge-appservice-slack.md b/docs/configuring-playbook-bridge-appservice-slack.md
index ecc0ab04e..b33f565cf 100644
--- a/docs/configuring-playbook-bridge-appservice-slack.md
+++ b/docs/configuring-playbook-bridge-appservice-slack.md
@@ -1,134 +1,136 @@
-# Setting up Appservice Slack (optional)
+# Setting up Appservice Slack bridging (optional)
 
-**Note**: bridging to [Slack](https://slack.com) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook.
+**Notes**:
+- Bridging to [Slack](https://slack.com) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook.
+- 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".
 
 The playbook can install and configure [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) for you.
 
 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.
 
-## Setup Instructions:
+## Prerequisites
 
-loosely based on [this](https://github.com/matrix-org/matrix-appservice-slack#Setup)
+### Create a Classic Slack App
 
-1. Create a new Matrix room to act as the administration control room. Note its internal room ID. This can be done in Element by sending a message, opening the options for that message and choosing "view source". The room ID will be displayed near the top.
+First, you need to create a Classic Slack App [here](https://api.slack.com/apps?new_classic_app=1).
 
-2. Enable the bridge by adding the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+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.
 
-    ```yaml
-    matrix_appservice_slack_enabled: true
-    matrix_appservice_slack_control_room_id: "Your Matrix admin room ID"
-    ```
+Then, click on Event Subscriptions and enable them and use the request url: `https://matrix.example.com/appservice-slack`.
 
-3. Enable puppeting (optional, but recommended)
+Add the following events as `Bot User Events` and save:
 
-    ```yaml
-    matrix_appservice_slack_puppeting_enabled: true
-    matrix_appservice_slack_puppeting_slackapp_client_id: "Your Classic Slack App Client ID"
-    matrix_appservice_slack_puppeting_slackapp_client_secret: "Your Classic Slack App Client Secret"
-    ```
+- team_domain_change
+- message.channels
+- message.groups (if you want to bridge private channels)
+- reaction_added
+- reaction_removed
 
-4. Enable Team Sync (optional)
+Next, click on "OAuth & Permissions" and add the following scopes:
 
-    ```yaml
-    matrix_appservice_slack_team_sync_enabled: true
-    ```
+- chat:write:bot
+- users:read
+- reactions:write
+- files:write:user (if you want to bridge files)
 
-    See https://matrix-appservice-slack.readthedocs.io/en/latest/team_sync/
+**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.
 
-5. If you've already installed Matrix services using the playbook before, you'll need to re-run it (`--tags=setup-all,start`). If not, proceed with [configuring other playbook services](configuring-playbook.md) and then with [Installing](installing.md). Get back to this guide once ready.
+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.
 
-6. Invite the bridge bot user into the admin room:
+### Create an administration control room on Matrix
+
+Create a new Matrix room to act as the administration control room.
+
+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.
+
+## Adjusting the playbook configuration
+
+To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+
+```yaml
+matrix_appservice_slack_enabled: true
+matrix_appservice_slack_control_room_id: "Your Matrix admin room ID"
+
+# Uncomment to enable puppeting (optional, but recommended)
+# matrix_appservice_slack_puppeting_enabled: true
+# matrix_appservice_slack_puppeting_slackapp_client_id: "Your Classic Slack App Client ID"
+# matrix_appservice_slack_puppeting_slackapp_client_secret: "Your Classic Slack App Client Secret"
+
+# Uncomment to enable Team Sync (optional)
+# See https://matrix-appservice-slack.readthedocs.io/en/latest/team_sync/
+# matrix_appservice_slack_team_sync_enabled: true
+```
+
+Other configuration options are available via the `matrix_appservice_slack_configuration_extension_yaml` variable.
+
+## Installing
+
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
+
+## Usage
+
+To use the bridge, you need to send `/invite @slackbot:example.com` to invite the bridge bot user into the admin room.
+
+If Team Sync is not enabled, for each channel you would like to bridge, perform the following steps:
+
+- 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`.
+- 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.
+- 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/`.
+- Issue a link command in the administration control room with these collected values as arguments:
+
+    with file bridging:
 
     ```
-    /invite @slackbot:example.com
+    link --channel_id CHANNELID --room !qporfwt:example.com --slack_bot_token xoxb-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxxx --slack_user_token xoxp-xxxxxxxx-xxxxxxxxx-xxxxxxxx-xxxxxxxx
     ```
 
-    Note that the bot's domain is your server's domain **without the `matrix.` prefix.**
-
-7. Create a Classic Slack App [here](https://api.slack.com/apps?new_classic_app=1).
-
-    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.
-
-8. Click on Event Subscriptions and enable them and use the request url `https://matrix.example.com/appservice-slack`. Then add the following events and save:
-
-     Bot User Events:
-
-    - team_domain_change
-    - message.channels
-    - message.groups (if you want to bridge private channels)
-    - reaction_added
-    - reaction_removed
-
-9. Click on OAuth & Permissions and add the following scopes:
-
-    - chat:write:bot
-    - users:read
-    - reactions:write
-
-    If you want to bridge files, also add the following:
-
-    - files:write:user
-
-    **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.
-
-10. 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.
-
-11. If Team Sync is not enabled, for each channel you would like to bridge, perform the following steps:
-
-    * 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.
-
-    * 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.
-
-    * 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/`.
-
-    * Issue a link command in the administration control room with these collected values as arguments:
-
-        with file bridging:
-
-        ```
-        link --channel_id CHANNELID --room !qporfwt:example.com --slack_bot_token xoxb-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxxx --slack_user_token xoxp-xxxxxxxx-xxxxxxxxx-xxxxxxxx-xxxxxxxx
-        ```
-
-        without file bridging:
-
-        ```
-        link --channel_id CHANNELID --room !qporfwt:example.com --slack_bot_token xoxb-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxxx
-        ```
-
-        These arguments can be shortened to single-letter forms:
-
-        ```
-        link -I CHANNELID -R !qporfwt:example.com -t xoxb-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxxx
-        ```
-
-        Other configuration options are available via the `matrix_appservice_slack_configuration_extension_yaml` variable.
-
-12. Unlinking
-
-    Channels can be unlinked again like this:
+    without file bridging:
 
     ```
-    unlink --room !qporfwt:example.com
+    link --channel_id CHANNELID --room !qporfwt:example.com --slack_bot_token xoxb-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxxx
     ```
 
-    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.
+    These arguments can be shortened to single-letter forms:
+
+    ```
+    link -I CHANNELID -R !qporfwt:example.com -t xoxb-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxxx
+    ```
+
+### Unlinking
+
+Channels can be unlinked again by sending this:
+
+```
+unlink --room !qporfwt:example.com
+```
+
+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.
 
 ## Troubleshooting
 
-* As always, check the logs: `journalctl -fu matrix-appservice-slack`
+As always, check the logs: `journalctl -fu matrix-appservice-slack`
 
-* Linking: "Room is now pending-name"
+### Linking: "Room is now pending-name"
 
-  This typically means that you haven't used the correct Slack channel ID. Unlink the room and recheck 'Determine the "channel ID"' from above.
+This typically means that you haven't used the correct Slack channel ID. Unlink the room and recheck 'Determine the "channel ID"' from above.
 
-* Messages work from M to S, but not the other way around
+### Messages work from Matrix to Slack, but not the other way around
 
-  Check you logs, if they say something like
+Check you logs, if they say something like
 
-  `WARN SlackEventHandler Ignoring message from unrecognised Slack channel ID : %s (%s) <the channel ID> <some other ID>`
+`WARN SlackEventHandler Ignoring message from unrecognised Slack channel ID : %s (%s) <the channel ID> <some other ID>`
 
-  then unlink your room, reinvite the bot and re-link it again. This may particularly hit you, if you tried to unsuccessfully link your room multiple times without unlinking it after each failed attempt.
+then unlink your room, reinvite the bot and re-link it again. This may particularly hit you, if you tried to unsuccessfully link your room multiple times without unlinking it after each failed attempt.
diff --git a/docs/configuring-playbook-bridge-appservice-webhooks.md b/docs/configuring-playbook-bridge-appservice-webhooks.md
index 07fe99d8c..e4d212f46 100644
--- a/docs/configuring-playbook-bridge-appservice-webhooks.md
+++ b/docs/configuring-playbook-bridge-appservice-webhooks.md
@@ -1,53 +1,61 @@
-# Setting up Appservice Webhooks (optional)
+# Setting up Appservice Webhooks bridging (optional, deprecated)
 
-The playbook can install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you.
+**Note**: This bridge has been deprecated. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bridge instead of this one.
 
-**Note**: This bridge is no longer maintained. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/Half-Shot/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md).
+The playbook can install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks.
 
-This bridge provides support for Slack-compatible webhooks.
+See the project's [documentation](https://github.com/turt2live/matrix-appservice-webhooks/blob/master/README.md) to learn what it does and why it might be useful to you.
 
-Setup Instructions:
+## Adjusting the playbook configuration
 
-loosely based on [this](https://github.com/turt2live/matrix-appservice-webhooks/blob/master/README.md)
-
-1. All you basically need is to adjust your `inventory/host_vars/matrix.example.com/vars.yml`:
+To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
 ```yaml
 matrix_appservice_webhooks_enabled: true
 matrix_appservice_webhooks_api_secret: '<your_secret>'
+
+# Uncomment to increase the verbosity of logging via `journalctl -fu matrix-appservice-webhooks.service`
+# matrix_appservice_webhooks_log_level: 'verbose'
+
+# As of Synapse 1.90.0, uncomment to enable the backwards compatibility (https://matrix-org.github.io/synapse/latest/upgrade#upgrading-to-v1900) that this bridge needs.
+# Note: This deprecated method is considered insecure.
+#
+# matrix_synapse_configuration_extension_yaml: |
+#   use_appservice_legacy_authorization: true
 ```
 
-2. In case you want to change the verbosity of logging via `journalctl -fu matrix-appservice-webhooks.service` you can adjust this in `inventory/host_vars/matrix.example.com/vars.yml` as well.
+## Installing
 
-**Note**: default value is: `info` and availabe log levels are : `info`, `verbose`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-```yaml
-matrix_appservice_webhooks_log_level: '<log_level>'
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
 ```
 
-3. As of Synapse 1.90.0, you will need to add the following to `matrix_synapse_configuration_extension_yaml` to enable the [backwards compatibility](https://matrix-org.github.io/synapse/latest/upgrade#upgrading-to-v1900) that this bridge needs:
-```yaml
-matrix_synapse_configuration_extension_yaml: |
-  use_appservice_legacy_authorization: true
-```
-**Note**: This deprecated method is considered insecure.
+**Notes**:
 
-4. If you've already installed Matrix services using the playbook before, you'll need to re-run it (`--tags=setup-all,start`). If not, proceed with [configuring other playbook services](configuring-playbook.md) and then with [Installing](installing.md). Get back to this guide once ready.
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-5. If you're using the [Dimension integration manager](configuring-playbook-dimension.md), you can configure the Webhooks bridge by opening the Dimension integration manager -> Settings -> Bridges and selecting edit action for "Webhook Bridge". Press "Add self-hosted Bridge" button and populate "Provisioning URL"  & "Shared Secret" values from `/matrix/appservice-webhooks/config/config.yaml` file's homeserver URL value and provisioning secret value, respectively.
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
-6. Invite the bridge bot user to your room:
+  `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.
 
-    - either with `/invite @_webhook:example.com` (**Note**: Make sure you have administration permissions in your room)
+## Usage
 
-    - or simply add the bridge bot to a private channel (personal channels imply you being an administrator)
+To use the bridge, you need to invite the bridge bot user to your room in either way.
+
+- Send `/invite @_webhook:example.com` (**Note**: Make sure you have administration permissions in your room)
+- Add the bridge bot to a private channel (personal channels imply you being an administrator)
+
+You then need to send a message to the bridge bot to receive a private message including the webhook link:
 
-7. Send a message to the bridge bot in order to receive a private message including the webhook link.
 ```
 !webhook
 ```
 
-8. The JSON body for posting messages will have to look like this:
+The JSON body for posting messages will have to look like this:
+
 ```json
 {
     "text": "Hello world!",
@@ -59,7 +67,7 @@ matrix_synapse_configuration_extension_yaml: |
 
 You can test this via curl like so:
 
-```
+```sh
 curl --header "Content-Type: application/json" \
 --data '{
 "text": "Hello world!",
@@ -67,5 +75,13 @@ curl --header "Content-Type: application/json" \
 "displayName": "My Cool Webhook",
 "avatar_url": "http://i.imgur.com/IDOBtEJ.png"
 }' \
-<the link you've gotten in 5.>
+<the webhook link you've gotten from the bridge bot>
 ```
+
+### Setting Webhooks with Dimension integration manager
+
+If you're using the [Dimension integration manager](configuring-playbook-dimension.md), you can configure the Webhooks bridge with it.
+
+To configure it, open the Dimension integration manager, and go to "Settings" and "Bridges", then select edit action for "Webhook Bridge".
+
+On the UI, press "Add self-hosted Bridge" button and populate "Provisioning URL"  and "Shared Secret" values from `/matrix/appservice-webhooks/config/config.yaml` file's homeserver URL value and provisioning secret value, respectively.
diff --git a/docs/configuring-playbook-bridge-beeper-linkedin.md b/docs/configuring-playbook-bridge-beeper-linkedin.md
index 5ba0233ec..73059ce64 100644
--- a/docs/configuring-playbook-bridge-beeper-linkedin.md
+++ b/docs/configuring-playbook-bridge-beeper-linkedin.md
@@ -1,9 +1,19 @@
-# Setting up Beeper Linkedin (optional)
+# Setting up Beeper Linkedin bridging (optional)
 
-The playbook can install and configure [beeper-linkedin](https://github.com/beeper/linkedin) for you, for bridging to [LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on the mautrix-python framework and can be configured in a similar way to the other mautrix bridges
+The playbook can install and configure [beeper-linkedin](https://github.com/beeper/linkedin) for you, for bridging to [LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on the mautrix-python framework and can be configured in a similar way to the mautrix bridges.
 
 See the project's [documentation](https://github.com/beeper/linkedin/blob/master/README.md) to learn what it does and why it might be useful to you.
 
+## Prerequisite
+
+### Enable Appservice Double Puppet or Shared Secret Auth (optional)
+
+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.
+
+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.
+
+**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future.
+
 ## Adjusting the playbook configuration
 
 To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
@@ -12,50 +22,36 @@ To enable the bridge, add the following configuration to your `inventory/host_va
 matrix_beeper_linkedin_enabled: true
 ```
 
-There are some additional things you may wish to configure about the bridge before you continue.
+### Extending the configuration
 
-Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:
-```yaml
-matrix_beeper_linkedin_configuration_extension_yaml: |
-  bridge:
-    encryption:
-      allow: true
-      default: true
-```
+There are some additional things you may wish to configure about the bridge.
 
-If you would like to be able to administrate the bridge from your account it can be configured like this:
-```yaml
-matrix_beeper_linkedin_configuration_extension_yaml: |
-  bridge:
-    permissions:
-      '@YOUR_USERNAME:example.com': admin
-```
+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.
 
-You may wish to look at `roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2` to find other things you would like to configure.
+**Note**: when following the guide to configure the bridge, make sure to replace `_mautrix_SERVICENAME_` in the variable names with `_beeper_linkedin_`.
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-## Set up Double Puppeting by enabling Appservice Double Puppet or Shared Secret Auth
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
 
-The bridge will automatically perform Double Puppeting if you enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service or the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook.
+**Notes**:
 
-Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future.
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
+  `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.
 
 ## Usage
 
-You then need to start a chat with `@linkedinbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
-
-Send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to enable bridging for your LinkedIn account.
-
-If you run into trouble, check the [Troubleshooting](#troubleshooting) section below.
-
-After successfully enabling bridging, you may wish to [set up Double Puppeting](#set-up-double-puppeting), if you haven't already done so.
+To use the bridge, you need to start a chat with `@linkedinbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
 
+You then need to send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to enable bridging for your LinkedIn account.
 
 ## Troubleshooting
 
diff --git a/docs/configuring-playbook-bridge-go-skype-bridge.md b/docs/configuring-playbook-bridge-go-skype-bridge.md
index ed39d9996..62d1eb77b 100644
--- a/docs/configuring-playbook-bridge-go-skype-bridge.md
+++ b/docs/configuring-playbook-bridge-go-skype-bridge.md
@@ -1,23 +1,52 @@
-# Setting up Go Skype Bridge (optional)
+# Setting up Go Skype Bridge bridging (optional)
 
-The playbook can install and configure [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) for you.
+The playbook can install and configure [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) for you, for bridging to [Skype](https://www.skype.com/). This bridge was created based on [mautrix-whatsapp](https://github.com/mautrix/whatsapp) and can be configured in a similar way to it.
 
-See the project page to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/kelaresg/go-skype-bridge/blob/master/README.md) to learn what it does and why it might be useful to you.
+
+## Prerequisite (optional)
+
+### Enable Shared Secret Auth
+
+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 [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook.
+
+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.
+
+**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future.
 
 ## Adjusting the playbook configuration
 
-To enable the [Skype](https://www.skype.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
 ```yaml
 matrix_go_skype_bridge_enabled: true
 ```
 
+### Extending the configuration
+
+There are some additional things you may wish to configure about the bridge.
+
+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.
+
+**Note**: when following the guide to configure the bridge, make sure to replace `_mautrix_SERVICENAME_` in the variable names with `_go_skype_bridge_`.
+
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
-Once the bot is enabled, you need to start a chat with `Skype bridge bot` with the handle `@skypebridgebot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
-
-Send `help` to the bot to see the commands available.
+To use the bridge, you need to start a chat with `@skypebridgebot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
diff --git a/docs/configuring-playbook-bridge-heisenbridge.md b/docs/configuring-playbook-bridge-heisenbridge.md
index c5b7f4a7c..a464a60f3 100644
--- a/docs/configuring-playbook-bridge-heisenbridge.md
+++ b/docs/configuring-playbook-bridge-heisenbridge.md
@@ -1,12 +1,18 @@
-# Setting up Heisenbridge (optional)
+# Setting up Heisenbridge bouncer-style IRC bridging (optional)
 
 **Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md) bridge supported by the playbook.
 
 The playbook can install and configure [Heisenbridge](https://github.com/hifi/heisenbridge) - the bouncer-style [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) bridge for you.
 
-See the project's [README](https://github.com/hifi/heisenbridge/blob/master/README.md) to learn what it does and why it might be useful to you. You can also take a look at [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I).
+See the project's [documentation](https://github.com/hifi/heisenbridge/blob/master/README.md) to learn what it does and why it might be useful to you. You can also take a look at [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I).
 
-## Configuration
+## Adjusting DNS records (optional)
+
+By default, this playbook installs Heisenbridge on the `matrix.` subdomain, at the `/heisenbridge` path (https://matrix.example.com/heisenbridge). It would handle media requests there (see the [release notes for Heisenbridge v1.15.0](https://github.com/hifi/heisenbridge/releases/tag/v1.15.0)). 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.
+
+If you wish to adjust it, see the section [below](#adjusting-the-heisenbridge-url-optional) for details about DNS configuration.
+
+## Adjusting the playbook configuration
 
 To enable Heisenbridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
@@ -15,23 +21,17 @@ matrix_heisenbridge_enabled: true
 
 # Setting the owner is optional as the first local user to DM `@heisenbridge:example.com` will be made the owner.
 # If you are not using a local user you must set it as otherwise you can't DM it at all.
-matrix_heisenbridge_owner: "@you:example.com"
+matrix_heisenbridge_owner: "@alice:{{ matrix_domain }}"
 
 # Uncomment to enable identd on host port 113/TCP (optional)
 # matrix_heisenbridge_identd_enabled: true
 ```
 
-For a more complete list of variables that you could override, see the [`defaults/main.yml` file](../roles/custom/matrix-bridge-heisenbridge/defaults/main.yml) of the Heisenbridge Ansible role.
-
-### Adjusting the Heisenbridge URL
-
-By default, this playbook installs Heisenbridge on the `matrix.` subdomain, at the `/heisenbridge` path (https://matrix.example.com/heisenbridge). It would handle media requests there (see the [release notes for Heisenbridge v1.15.0](https://github.com/hifi/heisenbridge/releases/tag/v1.15.0)).
-
-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.
+### Adjusting the Heisenbridge URL (optional)
 
 By tweaking the `matrix_heisenbridge_hostname` and `matrix_heisenbridge_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Change the default hostname and path prefix
@@ -39,21 +39,30 @@ matrix_heisenbridge_hostname: heisenbridge.example.com
 matrix_heisenbridge_path_prefix: /
 ```
 
-## Adjusting DNS records
+If you've changed the default hostname, you may need to create a CNAME record for the Heisenbridge domain (`heisenbridge.example.com`), which targets `matrix.example.com`.
 
-If you've changed the default hostname, **you may need to adjust your DNS** records to point the Heisenbridge domain to the Matrix server.
-
-See [Configuring DNS](configuring-dns.md) for details about DNS changes.
-
-If you've decided to use the default hostname, you won't need to do any extra DNS configuration.
+When setting, replace `example.com` with your own.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
-After the bridge is successfully running just DM `@heisenbridge:example.com` to start setting it up. If the bridge ignores you and a DM is not accepted then the owner setting may be wrong.
+To use the bridge, you need to start a chat with `@heisenbridge:example.com` (where `example.com` is your base domain, not the `matrix.` domain). If the bridge ignores you and a DM is not accepted then the owner setting may be wrong.
 
 Help is available for all commands with the `-h` switch.
 
diff --git a/docs/configuring-playbook-bridge-hookshot.md b/docs/configuring-playbook-bridge-hookshot.md
index 3bb1ba0ab..e0f852f1c 100644
--- a/docs/configuring-playbook-bridge-hookshot.md
+++ b/docs/configuring-playbook-bridge-hookshot.md
@@ -1,46 +1,79 @@
-# Setting up Hookshot (optional)
+# Setting up matrix-hookshot (optional)
 
 The playbook can install and configure [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) for you.
 
-Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) from software project management services such as GitHub, GitLab, JIRA, and Figma, as well as generic webhooks.
+Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) from software project management services such as GitHub, GitLab, Jira, and Figma, as well as generic webhooks.
 
-See the project's [documentation](https://matrix-org.github.io/matrix-hookshot/latest/hookshot.html) to learn what it does in detail and why it might be useful to you.
+See the project's [documentation](https://matrix-org.github.io/matrix-hookshot/latest/hookshot.html) to learn what it does and why it might be useful to you.
 
-**Note**: the playbook also supports [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), which however is soon to be archived by its author and to be replaced by hookshot.
+**Note**: the playbook also supports [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), which however was deprecated by its author.
 
+## Prerequisites
 
-## Setup Instructions
+### Download GitHub app private key (optional)
 
-Refer to the [official instructions](https://matrix-org.github.io/matrix-hookshot/latest/setup.html) to learn what the individual options do.
+If you're setting up the GitHub bridge, you need to create your GitHub app, and generate a private key file of it.
 
-1. Enable the bridge by adding `matrix_hookshot_enabled: true` to your `vars.yml` file
-2. For each of the services (GitHub, GitLab, Jira, Figma, generic webhooks) fill in the respective variables `matrix_hookshot_service_*` listed in [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) as required.
-3. Take special note of the `matrix_hookshot_*_enabled` variables. Services that need no further configuration are enabled by default (GitLab, Generic), while you must first add the required configuration and enable the others (GitHub, Jira, Figma).
-4. If you're setting up the GitHub bridge, you'll need to generate and download a private key file after you created your GitHub app. Copy the contents of that file to the variable `matrix_hookshot_github_private_key` so the playbook can install it for you, or use one of the [other methods](#manage-github-private-key-with-aux-role) explained below.
-5. If you've already installed Matrix services using the playbook before, you'll need to re-run it (`--tags=setup-all,start`). If not, proceed with [configuring other playbook services](configuring-playbook.md) and then with [Installing](installing.md). Get back to this guide once ready. Hookshot can be set up individually using the tag `setup-hookshot`.
+You need to download the private key file, if you will install the file manually or with the `aux` role. For details, see [the section below](#manage-github-private-key-with-aux-role).
 
-Other configuration options are available via the `matrix_hookshot_configuration_extension_yaml` and `matrix_hookshot_registration_extension_yaml` variables, see the comments in [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) for how to use them.
+## Adjusting the playbook configuration
 
-Finally, run the playbook (see [installing](installing.md)).
+Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `GITHUB_PRIVATE_KEY_HERE` with the one created [above](#download-github-app-private-key).
 
-### End-to-bridge encryption
+```yaml
+matrix_hookshot_enabled: true
 
-You can enable [experimental encryption](https://matrix-org.github.io/matrix-hookshot/latest/advanced/encryption.html) for Hookshot by adding `matrix_hookshot_experimental_encryption_enabled: true` to your configuration (`vars.yml`) and [executing the playbook](installing.md) again.
+# Uncomment to enable end-to-bridge encryption.
+# See: https://matrix-org.github.io/matrix-hookshot/latest/advanced/encryption.html
+# matrix_hookshot_experimental_encryption_enabled: true
 
-Should the crypto store be corrupted, you can reset it by executing this Ansible playbook with the tag `reset-hookshot-encryption` added, for example `ansible-playbook -i inventory/hosts setup.yml -K --tags=reset-hookshot-encryption`.
+# Uncomment and paste the contents of GitHub app private key to enable GitHub bridge.
+# Alternatively, you can use one of the other methods explained below on the "Manage GitHub Private Key with aux role" section.
+# matrix_hookshot_github_private_key: "GITHUB_PRIVATE_KEY_HERE"
+```
+
+For each of the services (GitHub, GitLab, Jira, Figma, and generic webhooks) fill in the respective variables `matrix_hookshot_service_*` listed in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) as required.
+
+Take special note of the `matrix_hookshot_*_enabled` variables. Services that need no further configuration are enabled by default (GitLab and generic webhooks), while you must first add the required configuration and enable the others (GitHub, Jira, and Figma).
+
+### Extending the configuration
+
+You can configure additional options by adding the `matrix_hookshot_configuration_extension_yaml` and `matrix_hookshot_registration_extension_yaml` variables.
+
+Refer the [official instructions](https://matrix-org.github.io/matrix-hookshot/latest/setup.html) and the comments in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) to learn what the individual options do.
+
+## Installing
+
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-service hookshot` or `just setup-all`
+
+`just install-service hookshot` is useful for maintaining your setup quickly 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 `just setup-all` runs the `ensure-matrix-users-created` tag too.
 
 ## Usage
 
-Create a room and invite the Hookshot bot (`@hookshot:example.com`) to it.
+To use the bridge, you need to create a room and invite the Hookshot bot (`@hookshot:example.com`) to it.
 
 Make sure the bot is able to send state events (usually the Moderator power level in clients).
 
-Send a `!hookshot help` message to see a list of help commands.
+Send `!hookshot help` to the bot to see the available commands.
 
 Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-hookshot/latest/usage.html) for more details about using the bridge's various features.
 
-**Important**: Note that the different listeners are bound to certain paths which might differ from those assumed by the hookshot documentation, see [URLs for bridges setup](#urls-for-bridges-setup) below.
+💡 **Note**: the different listeners are bound to certain paths which might differ from those assumed by the hookshot documentation. See [URLs for bridges setup](#urls-for-bridges-setup) below.
 
+### Reset crypto store
+
+Should the crypto store be corrupted, you can reset it by executing this Ansible playbook with the tag `reset-hookshot-encryption` added:
+
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=reset-hookshot-encryption
+```
 
 ## More setup documentation
 
@@ -48,30 +81,32 @@ Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-hookshot
 
 Unless indicated otherwise, the following endpoints are reachable on your `matrix.` subdomain (if the feature is enabled).
 
-| listener | default path | variable | used as |
+| Listener | Default path | Variable | Used as |
 |---|---|---|---|
 | - | `/hookshot/webhooks/` | `matrix_hookshot_webhook_endpoint` | Webhook-prefix, which affects all webhook-related URLs below |
 | generic | `/hookshot/webhooks/webhook` | `matrix_hookshot_generic_endpoint` | Generic webhooks |
 | github oauth | `/hookshot/webhooks/oauth` | `matrix_hookshot_github_oauth_endpoint` | GitHub "Callback URL" |
-| jira oauth | `/hookshot/webhooks/jira/oauth` | `matrix_hookshot_jira_oauth_endpoint` | JIRA OAuth |
+| jira oauth | `/hookshot/webhooks/jira/oauth` | `matrix_hookshot_jira_oauth_endpoint` | Jira OAuth |
 | figma endpoint | `/hookshot/webhooks/figma/webhook` | `matrix_hookshot_figma_endpoint` | Figma |
 | provisioning | `/hookshot/v1/` | `matrix_hookshot_provisioning_endpoint` | Dimension [provisioning](#provisioning-api) |
 | appservice | `/hookshot/_matrix/app/` | `matrix_hookshot_appservice_endpoint` | Matrix server |
 | widgets | `/hookshot/widgetapi/` | `matrix_hookshot_widgets_endpoint` | Widgets |
 | metrics | `/metrics/hookshot` | `matrix_hookshot_metrics_enabled` and exposure enabled via `matrix_hookshot_metrics_proxying_enabled` or `matrix_metrics_exposure_enabled`. Read more in the [Metrics section](#metrics) below. | Prometheus |
 
-Also see the various `matrix_hookshot_container_labels_*` variables in [default/main.yml](/roles/custom/matrix-bridge-hookshot/default/main.yml), which expose URLs publicly.
+Also see the various `matrix_hookshot_container_labels_*` variables in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), which expose URLs publicly
 
-The different listeners are also reachable *internally* in the docker-network via the container's name (configured by `matrix_hookshot_container_url`) and on different ports (e.g. `matrix_hookshot_appservice_port`). Read [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml) in detail for more info.
+The different listeners are also reachable *internally* in the docker-network via the container's name (configured by `matrix_hookshot_container_url`) and on different ports (e.g. `matrix_hookshot_appservice_port`). Read [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) in detail for more info.
 
 ### Manage GitHub Private Key with aux role
 
 The GitHub bridge requires you to install a private key file. This can be done in multiple ways:
-- copy the *contents* of the downloaded file and set the variable `matrix_hookshot_github_private_key` to the contents (see example in [main.yml](/roles/custom/matrix-bridge-hookshot/defaults/main.yml)).
+
+- copy the *contents* of the downloaded file and set the variable `matrix_hookshot_github_private_key` to the contents (see example in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml)).
 - somehow copy the file to the path `{{ matrix_hookshot_base_path }}/{{ matrix_hookshot_github_private_key_file }}` (default: `/matrix/hookshot/private-key.pem`) on the server manually.
 - use the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) to copy the file from an arbitrary path on your ansible client to the correct path on the server.
 
-To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following additional configuration:
+To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following configuration to your `vars.yml` file:
+
 ```yaml
 aux_file_definitions:
   - dest: "{{ matrix_hookshot_base_path }}/{{ matrix_hookshot_github_private_key_file }}"
@@ -80,6 +115,7 @@ aux_file_definitions:
     owner: "{{ matrix_user_username }}"
     group: "{{ matrix_user_groupname }}"
 ```
+
 For more information, see the documentation in the [default configuration of the aux role](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml).
 
 ### Provisioning API
diff --git a/docs/configuring-playbook-bridge-matrix-bridge-sms.md b/docs/configuring-playbook-bridge-matrix-bridge-sms.md
index f698ad986..7f58a74cd 100644
--- a/docs/configuring-playbook-bridge-matrix-bridge-sms.md
+++ b/docs/configuring-playbook-bridge-matrix-bridge-sms.md
@@ -1,10 +1,12 @@
-# Setting up matrix-sms-bridge (optional)
+# Setting up Matrix SMS bridging (optional)
 
 The playbook can install and configure [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) for you.
 
-See the project page to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/benkuly/matrix-sms-bridge/blob/master/README.md) to learn what it does and why it might be useful to you.
 
-**The bridge uses [android-sms-gateway-server](https://github.com/RebekkaMa/android-sms-gateway-server). You need to configure it first.**
+## Prerequisite
+
+The bridge uses [android-sms-gateway-server](https://github.com/RebekkaMa/android-sms-gateway-server). You need to configure it first.
 
 ## Adjusting the playbook configuration
 
@@ -33,7 +35,20 @@ matrix_sms_bridge_provider_android_truststore_password: 123
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
diff --git a/docs/configuring-playbook-bridge-mautrix-bridges.md b/docs/configuring-playbook-bridge-mautrix-bridges.md
new file mode 100644
index 000000000..12f70a66e
--- /dev/null
+++ b/docs/configuring-playbook-bridge-mautrix-bridges.md
@@ -0,0 +1,213 @@
+# Setting up a Generic Mautrix Bridge (optional)
+
+The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, discord, signal, googlechat, etc.), as well as many other (non-mautrix) bridges. This is a common guide for configuring mautrix bridges.
+
+The author of the bridges maintains [the official docs](https://docs.mau.fi/bridges/index.html), whose source code is available at [mautrix/docs](https://github.com/mautrix/docs) repository on GitHub. You may as well to refer it while configuring them.
+
+You can see each bridge's features on the `ROADMAP.md` file in its corresponding mautrix repository.
+
+## Adjusting the playbook configuration
+
+To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+
+```yaml
+# Replace SERVICENAME with one of: twitter, discord, signal, googlechat, etc.
+matrix_mautrix_SERVICENAME_enabled: true
+```
+
+**Note**: for bridging to Meta's Messenger or Instagram, you would need to add `meta` with an underscore symbol (`_`) or hyphen (`-`) based on the context as prefix to each `SERVICENAME`; add `_` to variables (as in `matrix_mautrix_meta_messenger_configuration_extension_yaml` for example) and `-` to paths of the configuration files (as in `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2`), respectively. **`matrix_mautrix_facebook_*` and `matrix_mautrix_instagram_*` variables belong to the deprecated components and do not control the new bridge** ([mautrix-meta](https://github.com/mautrix/meta)), which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md).
+
+There are some additional things you may wish to configure about the bridge before you continue. Each bridge may have additional requirements besides `_enabled: true`. For example, the mautrix-telegram bridge (our documentation page about it is [here](configuring-playbook-bridge-mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and `matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each bridge's individual documentation page for details about enabling bridges.
+
+### Configure bridge permissions (optional)
+
+By default any user on your homeserver will be able to use the mautrix bridges. To limit who can use them you would need to configure their permissions settings.
+
+Different levels of permission can be granted to users. For example, to **configure a user as an administrator for all bridges**, add the following configuration to your `vars.yml` file:
+
+```yaml
+matrix_admin: "@alice:{{ matrix_domain }}"
+```
+
+If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default.
+
+**Alternatively** (more verbose, but allows multiple admins to be configured), you can do the same on a per-bridge basis with:
+
+```yaml
+matrix_mautrix_SERVICENAME_configuration_extension_yaml: |
+  bridge:
+    permissions:
+      '@alice:{{ matrix_domain }}': admin
+```
+
+This will add the admin permission to the specific user, while keeping the default permissions.
+
+You could also redefine the default permissions settings completely, rather than adding extra permissions. You may wish to look at `roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` to find information on the permission settings and other options you would like to configure.
+
+### Enable encryption (optional)
+
+[Encryption (End-to-Bridge Encryption, E2BE) support](https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html) is off by default. If you would like to enable encryption, add the following configuration to your `vars.yml` file:
+
+**for all bridges with encryption support**:
+
+```yaml
+matrix_bridges_encryption_enabled: true
+matrix_bridges_encryption_default: true
+```
+
+**Alternatively**, for a specific bridge:
+
+```yaml
+matrix_mautrix_SERVICENAME_bridge_encryption_enabled: true
+matrix_mautrix_SERVICENAME_bridge_encryption_default: true
+```
+
+### Enable relay mode (optional)
+
+[Relay mode](https://docs.mau.fi/bridges/general/relay-mode.html) is off by default. Check [the table on the official documentation](https://docs.mau.fi/bridges/general/relay-mode.html#support-table) for bridges which support relay mode.
+
+If you would like to enable it, add the following configuration to your `vars.yml` file:
+
+**for all bridges with relay mode support**:
+
+```yaml
+matrix_bridges_relay_enabled: true
+```
+
+**Alternatively**, for a specific bridge:
+
+```yaml
+matrix_mautrix_SERVICENAME_configuration_extension_yaml: |
+  bridge:
+    relay:
+      enabled: true
+```
+
+You can only have one `matrix_mautrix_SERVICENAME_configuration_extension_yaml` definition in `vars.yml` per bridge, so if you need multiple pieces of configuration there, just merge them like this:
+
+```yaml
+matrix_mautrix_SERVICENAME_configuration_extension_yaml: |
+  bridge:
+    relay:
+      enabled: true
+    permissions:
+      '@alice:{{ matrix_domain }}': admin
+    encryption:
+      allow: true
+      default: true
+```
+
+If you want to activate the relaybot in a room, send `!prefix set-relay` in the rooms where you want to use the bot (replace `!prefix` with the appropriate command prefix for the bridge, like `!signal` or `!wa`). To deactivate, send `!prefix unset-relay`.
+
+Use `!prefix set-pl 100` to be able for the bot to modify room settings and invite others.
+
+#### Allow anyone on the homeserver to become a relay user (optional)
+
+By default, only admins are allowed to set themselves as relay users. To allow anyone on your homeserver to set themselves as relay users, add the following configuration to your `vars.yml` file:
+
+```yaml
+matrix_mautrix_SERVICENAME_bridge_relay_admin_only: false
+```
+
+### Set the bot's username (optional)
+
+To set the bot's username, add the following configuration to your `vars.yml` file:
+
+```yaml
+matrix_mautrix_SERVICENAME_appservice_bot_username: "BOTNAME"
+```
+
+### Configure the logging level (optional)
+
+To specify the logging level, add the following configuration to your `vars.yml` file:
+
+```yaml
+matrix_mautrix_SERVICENAME_logging_level: warn
+```
+
+Replace `warn` with one of the following to control the verbosity of the logs generated: `trace`, `debug`, `info`, `warn`, `error` or `fatal`.
+
+If you have issues with a service, and are requesting support, the higher levels of logging (those that appear earlier in the list, like `trace`) will generally be more helpful.
+
+### Extending the configuration
+
+There are some additional things you may wish to configure about the bridge.
+
+Take a look at:
+
+- `roles/custom/matrix-bridge-mautrix-SERVICENAME/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+- `roles/custom/matrix-bridge-mautrix-SERVICENAME/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_mautrix_SERVICENAME_configuration_extension_yaml` variable
+
+## Installing
+
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
+
+## Usage
+
+To use the bridge, you need to start a chat with `@SERVICENAMEbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+
+For details about the next steps, refer to each bridge's individual documentation page.
+
+Send `help` to the bot to see the available commands.
+
+If you run into trouble, check the [Troubleshooting](#troubleshooting) section below.
+
+### Set up Double Puppeting (optional)
+
+After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do).
+
+To set it up, you have 2 ways of going about it.
+
+#### Method 1: automatically, by enabling Appservice Double Puppet (recommended)
+
+To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html), you could enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook.
+
+Appservice Double Puppet is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver.
+
+To enable the Appservice Double Puppet service, add the following configuration to your `vars.yml` file:
+
+```yaml
+matrix_appservice_double_puppet_enabled: true
+```
+
+When enabled, double puppeting will automatically be enabled for all bridges that support double puppeting via the appservice method.
+
+This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
+
+**Notes**:
+
+- Previously there were multiple different automatic double puppeting methods like one with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but they have been superseded by this Appservice Double Puppet method. Double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future as the older methods were completely removed in the megabridge rewrites on [the upstream project](https://docs.mau.fi/bridges/general/double-puppeting.html#automatically).
+
+<!-- TODO: remove this note if the Shared Secret Auth service has stopped working or the bridges have been removed -->
+- Some bridges like [the deprecated Facebook mautrix bridge](configuring-playbook-bridge-mautrix-facebook.md) and [matrix-appservice-kakaotalk](configuring-playbook-bridge-appservice-kakaotalk.md), which is partially based on the Facebook bridge, are compatible with the Shared Secret Auth service only. These bridges automatically perform Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook.
+
+#### Method 2: manually, by asking each user to provide a working access token
+
+When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:
+
+- retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md).
+
+- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`
+
+- make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature
+
+## Troubleshooting
+
+For troubleshooting information with a specific bridge, please see the playbook documentation about it (some other document in in `docs/`) and the upstream ([mautrix](https://github.com/mautrix)) bridge documentation for that specific bridge.
+
+If the bridge's bot doesn't accept the invite to a chat, refer [the official troubleshooting page](https://docs.mau.fi/bridges/general/troubleshooting.html) as well.
+
+If you found bugs in mautrix bridges, they should be reported to the upstream project, in the corresponding mautrix repository, not to us.
diff --git a/docs/configuring-playbook-bridge-mautrix-discord.md b/docs/configuring-playbook-bridge-mautrix-discord.md
index 11a3560b0..d5e6b4834 100644
--- a/docs/configuring-playbook-bridge-mautrix-discord.md
+++ b/docs/configuring-playbook-bridge-mautrix-discord.md
@@ -1,4 +1,6 @@
-# Setting up Mautrix Discord (optional)
+# Setting up Mautrix Discord bridging (optional)
+
+<sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>
 
 **Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md) bridges supported by the playbook.
 - For using as a Bot we recommend the [Appservice Discord](configuring-playbook-bridge-appservice-discord.md), because it supports plumbing.
@@ -8,13 +10,20 @@ The playbook can install and configure [mautrix-discord](https://github.com/maut
 
 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.
 
-
 ## Prerequisites
 
 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).
 
 If this is a dealbreaker for you, consider using one of the other Discord bridges supported by the playbook: [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) or [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md). These come with their own complexity and limitations, however, so we recommend that you proceed with this one if possible.
 
+### Enable Appservice Double Puppet or Shared Secret Auth (optional)
+
+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.
+
+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.
+
+**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future.
+
 ## Adjusting the playbook configuration
 
 To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
@@ -23,77 +32,42 @@ To enable the bridge, add the following configuration to your `inventory/host_va
 matrix_mautrix_discord_enabled: true
 ```
 
-You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation.
-
-## Installing
-
-After configuring the playbook, run the [installation](installing.md) command:
-
-```
-ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
-```
-
-To make use of the bridge, see [Usage](#usage) below.
-
-
-### Additional configuration
+### Extending the configuration
 
 There are some additional things you may wish to configure about the bridge.
 
-Take a look at:
+<!-- NOTE: common relay mode is not supported for this bridge -->
+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.
 
-- `roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
-- `roles/custom/matrix-bridge-mautrix-discord/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_mautrix_discord_configuration_extension_yaml` variable
+## Installing
 
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-### Set up Double Puppeting
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
 
-If you'd like to use [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do), you have 2 ways of going about it.
+**Notes**:
 
-#### Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-The bridge will automatically perform Double Puppeting if you enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service or the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook.
-
-Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
-
-Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future.
-
-#### Method 2: manually, by asking each user to provide a working access token
-
-**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging (see [Usage](#usage)).
-
-When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:
-
-- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md).
-
-- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`
-
-- make sure you don't log out the `Mautrix-Discord` device some time in the future, as that would break the Double Puppeting feature
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
+  `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.
 
 ## Usage
 
-### Logging in
+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).
 
-#### Method 1: Login using QR code (recommended)
+You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/discord/authentication.html).
 
-For using this bridge, you would need to authenticate by **scanning a QR code** with the Discord app on your phone.
+After logging in, the bridge will create portal rooms for some recent direct messages.
 
-You can delete the Discord app after the authentication process.
+### Bridge guilds
 
-#### Method 2: Login using Discord token (not recommended)
+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.
 
-To acquire the token, open Discord in a private browser window. Then open the developer settings (keyboard shortcut might be "ctrl+shift+i" or by pressing "F12"). Navigate to the "Network" tab then reload the page. In the URL filter or search bar type "/api" and find the response with the file name of "library". Under the request headers you should find a variable called "Authorization", this is the token to your Discord account. After copying the token, you can close the browser window.
+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.
 
-### Bridging
-
-1. Start a chat with `@discordbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
-2. If you would like to login to Discord using a token, send `login-token` command, otherwise, send `login-qr` command.
-3. You'll see a QR code which you need to scan with the Discord app on your phone. You can scan it with the camera app too, which will open Discord, which will then instruct you to scan it a 2nd time in the Discord app.
-4. After confirming (in the Discord app) that you'd like to allow this login, the bot should respond with "Succcessfully authenticated as ..."
-5. Now that you're logged in, you can send a `help` command to the bot again, to see additional commands you have access to
-6. Some Direct Messages from Discord should start syncing automatically
-7. If you'd like to bridge guilds:
-    - send `guilds status` to see the list of guilds
-    - for each guild that you'd like bridged, send `guilds bridge GUILD_ID --entire`
-8. You may wish to uninstall the Discord app from your phone now. It's not needed for the bridge to function.
+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.
diff --git a/docs/configuring-playbook-bridge-mautrix-facebook.md b/docs/configuring-playbook-bridge-mautrix-facebook.md
index 3ce6010de..51a162caf 100644
--- a/docs/configuring-playbook-bridge-mautrix-facebook.md
+++ b/docs/configuring-playbook-bridge-mautrix-facebook.md
@@ -1,10 +1,22 @@
-# Setting up Mautrix Facebook (optional)
+# Setting up Mautrix Facebook bridging (optional, deprecated)
 
-**Note**: bridging to Facebook [Messenger](https://messenger.com) via this bridge is being [superseded by a new bridge - mautrix-meta](https://github.com/mautrix/facebook/issues/332). For now, the mautrix-facebook bridge continues to work, but the new [mautrix-meta-messenger bridge](./configuring-playbook-bridge-mautrix-meta-messenger.md) is better and more supported. Consider using that bridge instead of this one.
+<sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>
+
+**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md). Consider using that bridge instead of this one.
 
 The playbook can install and configure [mautrix-facebook](https://github.com/mautrix/facebook) for you.
 
-See the project's [documentation](https://github.com/mautrix/facebook/blob/master/ROADMAP.md) to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/mautrix/facebook/blob/master/README.md) to learn what it does and why it might be useful to you.
+
+## Prerequisite (optional)
+
+### Enable Shared Secret Auth
+
+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 [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook.
+
+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.
+
+**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future.
 
 ## Adjusting the playbook configuration
 
@@ -14,77 +26,37 @@ To enable the bridge, add the following configuration to your `inventory/host_va
 matrix_mautrix_facebook_enabled: true
 ```
 
-There are some additional things you may wish to configure about the bridge before you continue.
+### Extending the configuration
 
-Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:
-```yaml
-matrix_mautrix_facebook_configuration_extension_yaml: |
-  bridge:
-    encryption:
-      allow: true
-      default: true
-```
+There are some additional things you may wish to configure about the bridge.
 
-If you would like to be able to administrate the bridge from your account it can be configured like this:
-```yaml
-matrix_mautrix_facebook_configuration_extension_yaml: |
-  bridge:
-    permissions:
-      '@YOUR_USERNAME:{{ matrix_domain }}': admin
-```
-
-Using both would look like
-
-```yaml
-matrix_mautrix_facebook_configuration_extension_yaml: |
-  bridge:
-    permissions:
-      '@YOUR_USERNAME:{{ matrix_domain }}': admin
-    encryption:
-      allow: true
-      default: true
-```
-
-You may wish to look at `roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml` to find other things you would like to configure.
+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.
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-## Set up Double Puppeting
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
 
-If you'd like to use [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do), you have 2 ways of going about it.
+**Notes**:
 
-### Method 1: automatically, by enabling Shared Secret Auth
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-The bridge will automatically perform Double Puppeting if you enable [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook.
-
-This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
-
-### Method 2: manually, by asking each user to provide a working access token
-
-**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging (see [Usage](#usage)).
-
-When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:
-
-- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md).
-
-- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`
-
-- make sure you don't log out the `Mautrix-Facebook` device some time in the future, as that would break the Double Puppeting feature
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
+  `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.
 
 ## Usage
 
-You then need to start a chat with `@facebookbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `@facebookbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
 
-Send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable bridging for your Facebook Messenger account. You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/facebook/authentication.html).
+You then need to send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable bridging for your Facebook Messenger account.
 
 If you run into trouble, check the [Troubleshooting](#troubleshooting) section below.
 
-After successfully enabling bridging, you may wish to [set up Double Puppeting](#set-up-double-puppeting), if you haven't already done so.
-
-
 ## Troubleshooting
 
 ### Facebook rejecting login attempts and forcing you to change password
@@ -97,7 +69,7 @@ The easiest way to do this may be to use [sshuttle](https://sshuttle.readthedocs
 
 Example command for proxying your traffic through the Matrix server:
 
-```
+```sh
 sshuttle -r root@matrix.example.com:22 0/0
 ```
 
diff --git a/docs/configuring-playbook-bridge-mautrix-gmessages.md b/docs/configuring-playbook-bridge-mautrix-gmessages.md
index 6b44eeeee..eae32a1f7 100644
--- a/docs/configuring-playbook-bridge-mautrix-gmessages.md
+++ b/docs/configuring-playbook-bridge-mautrix-gmessages.md
@@ -1,9 +1,19 @@
-# Setting up Mautrix gmessages (optional)
+# Setting up Mautrix Google Messages bridging (optional)
+
+<sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>
 
 The playbook can install and configure [mautrix-gmessages](https://github.com/mautrix/gmessages) for you, for bridging to [Google Messages](https://messages.google.com/).
 
 See the project's [documentation](https://docs.mau.fi/bridges/go/gmessages/index.html) to learn what it does and why it might be useful to you.
 
+## Prerequisite (optional)
+
+### Enable Appservice Double Puppet
+
+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) for this playbook.
+
+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.
+
 ## Adjusting the playbook configuration
 
 To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
@@ -12,33 +22,34 @@ To enable the bridge, add the following configuration to your `inventory/host_va
 matrix_mautrix_gmessages_enabled: true
 ```
 
+### Extending the configuration
+
+There are some additional things you may wish to configure about the bridge.
+
+<!-- NOTE: relay mode is not supported for this bridge -->
+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.
+
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-## Set up Double Puppeting
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
 
-If you'd like to use [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do), you have 2 ways of going about it.
+**Notes**:
 
-### Method 1: automatically, by enabling Appservice Double Puppet
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-The bridge will automatically perform Double Puppeting if you enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook.
-
-Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
-
-### Method 2: manually, by asking each user to provide a working access token
-
-**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging (see [Usage](#usage)).
-
-When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:
-
-- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md).
-
-- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`
-
-- make sure you don't log out the `Mautrix-gmessages` device some time in the future, as that would break the Double Puppeting feature
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
+  `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.
 
 ## Usage
 
-You then need to start a chat with `@gmessagesbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `@gmessagesbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+
+You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/gmessages/authentication.html).
+
+After logging in, the bridge will create portal rooms for recent chats.
diff --git a/docs/configuring-playbook-bridge-mautrix-googlechat.md b/docs/configuring-playbook-bridge-mautrix-googlechat.md
index a62003cb2..4dbde4dd8 100644
--- a/docs/configuring-playbook-bridge-mautrix-googlechat.md
+++ b/docs/configuring-playbook-bridge-mautrix-googlechat.md
@@ -1,9 +1,21 @@
-# Setting up Mautrix Google Chat (optional)
+# Setting up Mautrix Google Chat bridging (optional)
+
+<sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>
 
 The playbook can install and configure [mautrix-googlechat](https://github.com/mautrix/googlechat) for you.
 
 See the project's [documentation](https://docs.mau.fi/bridges/python/googlechat/index.html) to learn what it does and why it might be useful to you.
 
+## Prerequisite (optional)
+
+### Enable Appservice Double Puppet or Shared Secret Auth
+
+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.
+
+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.
+
+**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future.
+
 ## Adjusting the playbook configuration
 
 To enable the [Google Chat](https://chat.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
@@ -12,46 +24,34 @@ To enable the [Google Chat](https://chat.google.com/) bridge, add the following
 matrix_mautrix_googlechat_enabled: true
 ```
 
+### Extending the configuration
+
+There are some additional things you may wish to configure about the bridge.
+
+<!-- NOTE: relay mode is not supported for this bridge -->
+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.
+
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-## Set up Double Puppeting
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
 
-If you'd like to use [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do), you have 2 ways of going about it.
+**Notes**:
 
-### Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-The bridge will automatically perform Double Puppeting if you enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service or the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook.
-
-Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
-
-Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future.
-
-
-### Method 2: manually, by asking each user to provide a working access token
-
-**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging (see [Usage](#usage)).
-
-When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:
-
-- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md).
-
-- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`
-
-- make sure you don't log out the `Mautrix-googlechat` device some time in the future, as that would break the Double Puppeting feature
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
+  `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.
 
 ## Usage
 
-Once the bot is enabled you need to start a chat with `googlechat bridge bot` with handle `@googlechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `@googlechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
 
-Send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions.
+You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html).
 
-Automatic login may not work. If it does not, reload the page and select the "Manual login" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools.
-
-Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages.
-
-You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html).
-
-After successfully enabling bridging, you may wish to [set up Double Puppeting](#set-up-double-puppeting), if you haven't already done so.
+After logging in, the bridge will create portal rooms for some recent chats. Portal rooms for other chats will be created as you receive messages.
diff --git a/docs/configuring-playbook-bridge-mautrix-hangouts.md b/docs/configuring-playbook-bridge-mautrix-hangouts.md
index 198d4c923..307605be4 100644
--- a/docs/configuring-playbook-bridge-mautrix-hangouts.md
+++ b/docs/configuring-playbook-bridge-mautrix-hangouts.md
@@ -1,10 +1,20 @@
-# The [Mautrix Hangouts Bridge](https://mau.dev/mautrix/hangouts) is no longer maintained.  It has changed to a [Google Chat Bridge](https://github.com/mautrix/googlechat). Setup instructions for the Google Chat Bridge can be [found here](configuring-playbook-bridge-mautrix-googlechat.md).
+# Setting up Mautrix Hangouts bridging (optional, deprecated)
 
-# Setting up Mautrix Hangouts (optional)
+<sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>
+
+💡 **Note**: This bridge has been deprecated in favor of [Google Chat bridge](https://github.com/mautrix/googlechat), which can be installed using [this playbook](configuring-playbook-bridge-mautrix-googlechat.md). Installing the mautrix-hangouts bridge is **no longer possible**. For now, this documentation page remains here for historical purposes.
 
 The playbook can install and configure [mautrix-hangouts](https://github.com/mautrix/hangouts) for you.
 
-See the project's [documentation](https://docs.mau.fi/bridges/python/hangouts/index.html) to learn what it does and why it might be useful to you.
+## Prerequisite (optional)
+
+### Enable Shared Secret Auth
+
+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 [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook.
+
+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.
+
+**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future.
 
 ## Adjusting the playbook configuration
 
@@ -14,44 +24,35 @@ To enable the [Google Hangouts](https://hangouts.google.com/) bridge, add the fo
 matrix_mautrix_hangouts_enabled: true
 ```
 
+### Extending the configuration
+
+There are some additional things you may wish to configure about the bridge.
+
+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.
+
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-## Set up Double Puppeting
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
 
-If you'd like to use [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do), you have 2 ways of going about it.
+**Notes**:
 
-### Method 1: automatically, by enabling Shared Secret Auth
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-The bridge will automatically perform Double Puppeting if you enable [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook.
-
-This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
-
-
-### Method 2: manually, by asking each user to provide a working access token
-
-**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging (see [Usage](#usage)).
-
-When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:
-
-- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md).
-
-- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`
-
-- make sure you don't log out the `Mautrix-Hangouts` device some time in the future, as that would break the Double Puppeting feature
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
+  `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.
 
 ## Usage
 
-Once the bot is enabled you need to start a chat with `Hangouts bridge bot` with handle `@hangoutsbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `@hangoutsbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
 
-Send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions.
+You then need to send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions.
 
 Automatic login may not work. If it does not, reload the page and select the "Manual login" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools.
 
 Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages.
-
-You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/hangouts/authentication.html).
-
-After successfully enabling bridging, you may wish to [set up Double Puppeting](#set-up-double-puppeting), if you haven't already done so.
diff --git a/docs/configuring-playbook-bridge-mautrix-instagram.md b/docs/configuring-playbook-bridge-mautrix-instagram.md
index ffafa25db..99988df41 100644
--- a/docs/configuring-playbook-bridge-mautrix-instagram.md
+++ b/docs/configuring-playbook-bridge-mautrix-instagram.md
@@ -1,10 +1,12 @@
-# Setting up Mautrix Instagram (optional)
+# Setting up Mautrix Instagram bridging (optional, deprecated)
 
-**Note**: bridging to Facebook [Instagram](https://instagram.com) via this bridge is being [superseded by a new bridge - mautrix-meta](https://github.com/mautrix/facebook/issues/332). For now, the mautrix-instagram bridge continues to work, but the new [mautrix-meta-instagram bridge](./configuring-playbook-bridge-mautrix-meta-instagram.md) is better and more supported. Consider using that bridge instead of this one.
+<sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>
+
+**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-instagram.md). Consider using that bridge instead of this one.
 
 The playbook can install and configure [mautrix-instagram](https://github.com/mautrix/instagram) for you.
 
-See the project's [documentation](https://docs.mau.fi/bridges/python/instagram/index.html) to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/mautrix/instagram/blob/master/README.md) to learn what it does and why it might be useful to you.
 
 ## Adjusting the playbook configuration
 
@@ -14,40 +16,31 @@ To enable the bridge, add the following configuration to your `inventory/host_va
 matrix_mautrix_instagram_enabled: true
 ```
 
-There are some additional things you may wish to configure about the bridge before you continue.
+### Extending the configuration
 
-Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:
-```yaml
-matrix_mautrix_instagram_configuration_extension_yaml: |
-  bridge:
-    encryption:
-      allow: true
-      default: true
-```
+There are some additional things you may wish to configure about the bridge.
 
-If you would like to be able to administrate the bridge from your account it can be configured like this:
-```yaml
-# The easy way. The specified Matrix user ID will be made an admin of all bridges
-matrix_admin: "@YOUR_USERNAME:{{ matrix_domain }}"
-
-# OR:
-# The more verbose way. Applies to this bridge only. You may define multiple Matrix users as admins.
-matrix_mautrix_instagram_configuration_extension_yaml: |
-  bridge:
-    permissions:
-      '@YOUR_USERNAME:example.com': admin
-```
-
-You may wish to look at `roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml` to find other things you would like to configure.
+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.
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
-You then need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
 
-Send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the bridge bot to enable bridging for your instagram/Messenger account.
-
-You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/instagram/authentication.html).
+You then need to send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the bridge bot to enable bridging for your instagram/Messenger account.
diff --git a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md
index f7809090d..d89c1d50c 100644
--- a/docs/configuring-playbook-bridge-mautrix-meta-instagram.md
+++ b/docs/configuring-playbook-bridge-mautrix-meta-instagram.md
@@ -1,25 +1,33 @@
 # Setting up Instagram bridging via Mautrix Meta (optional)
 
+<sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>
+
 The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you.
 
+See the project's [documentation](https://docs.mau.fi/bridges/go/meta/index.html) to learn what it does and why it might be useful to you.
+
 Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`).
 
 This documentation page only deals with the bridge's ability to bridge to Instagram. For bridging to Facebook/Messenger, see [Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md).
 
+## Prerequisites
 
-## Migrating from the old mautrix-instagram bridge
+### Migrating from the old mautrix-instagram bridge
 
 If you've been using the [mautrix-instagram](./configuring-playbook-bridge-mautrix-instagram.md) bridge, **you'd better get rid of it first** or the 2 bridges will be in conflict:
 
 - both trying to use `@instagrambot:example.com` as their username. This conflict may be resolved by adjusting `matrix_mautrix_instagram_appservice_bot_username` or `matrix_mautrix_meta_instagram_appservice_username`
 - both trying to bridge the same DMs
 
-To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@instagrambot:example.com`).
-
-This would give you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc.
+To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@instagrambot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc.
 
 Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages.
 
+### Enable Appservice Double Puppet (optional)
+
+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.
+
+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.
 
 ## Adjusting the playbook configuration
 
@@ -31,64 +39,33 @@ matrix_mautrix_meta_instagram_enabled: true
 
 Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below.
 
-### Bridge permissions
+### Extending the configuration
 
-By default, any user on your homeserver will be able to use the bridge.
+There are some additional things you may wish to configure about the bridge.
 
-Different levels of permission can be granted to users:
-
-- `relay` - Allowed to be relayed through the bridge, no access to commands
-- `user` - Use the bridge with puppeting
-- `admin` - Use and administer the bridge
-
-The permissions are following the sequence: nothing < `relay` < `user` < `admin`.
-
-The default permissions are set via `matrix_mautrix_meta_instagram_bridge_permissions_default` and are somewhat like this:
-```yaml
-matrix_mautrix_meta_instagram_bridge_permissions_default:
-  '*': relay
-  example.com: user
-  '{{ matrix_admin }}': admin
-```
-
-If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @user:example.com`), then there's no admin by default.
-
-You may redefine `matrix_mautrix_meta_instagram_bridge_permissions_default` any way you see fit, or add extra permissions using `matrix_mautrix_meta_instagram_bridge_permissions_custom` like this:
-
-```yaml
-matrix_mautrix_meta_instagram_bridge_permissions_custom:
-  '@YOUR_USERNAME:example.com': admin
-```
-
-You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-instagram/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure.
+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.
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-## Set up Double Puppeting
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
 
-If you'd like to use [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do), you have 2 ways of going about it.
+**Notes**:
 
-### Method 1: automatically, by enabling Appservice Double Puppet
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-The bridge will automatically perform Double Puppeting if you enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook.
-
-Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
-
-### Method 2: manually, by asking each user to provide a working access token
-
-**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging (see [Usage](#usage)).
-
-When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:
-
-- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md).
-
-- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`
-
-- make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
+  `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.
 
 ## Usage
 
-You then need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+
+You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/meta/authentication.html).
+
+After logging in, the bridge will sync recent chats.
diff --git a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md
index 927475d90..de3421147 100644
--- a/docs/configuring-playbook-bridge-mautrix-meta-messenger.md
+++ b/docs/configuring-playbook-bridge-mautrix-meta-messenger.md
@@ -1,22 +1,33 @@
 # Setting up Messenger bridging via Mautrix Meta (optional)
 
+<sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>
+
 The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you.
 
+See the project's [documentation](https://docs.mau.fi/bridges/go/meta/index.html) to learn what it does and why it might be useful to you.
+
 Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`).
 
 This documentation page only deals with the bridge's ability to bridge to Facebook Messenger. For bridging to Instagram, see [Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md).
 
+## Prerequisites
 
-## Migrating from the old mautrix-facebook bridge
+### Migrating from the old mautrix-facebook bridge
 
 If you've been using the [mautrix-facebook](./configuring-playbook-bridge-mautrix-facebook.md) bridge, it's possible to migrate the database using [instructions from the bridge documentation](https://docs.mau.fi/bridges/go/meta/facebook-migration.html) (advanced).
 
-Then you may wish to get rid of the Facebook bridge. To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@facebookbot:example.com`).
-
-This would give you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc.
+Then you may wish to get rid of the Facebook bridge. To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@facebookbot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc.
 
 Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages.
 
+**Note**: the user ID of the new bridge bot is `@messengerbot:example.com`, not `@facebookbot:example.com`. After disabling the old bridge, its bot user will stop responding to a command.
+
+### Enable Appservice Double Puppet (optional)
+
+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.
+
+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.
+
 ## Adjusting the playbook configuration
 
 To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
@@ -41,69 +52,35 @@ You may switch the mode via the `matrix_mautrix_meta_messenger_meta_mode` variab
 
 Note that switching the mode (especially between `facebook*` and `messenger`) will intentionally make the bridge use another database (`matrix_mautrix_meta_facebook` or `matrix_mautrix_meta_messenger`) to isolate the 2 instances. Switching between Tor and non-Tor may be possible without dataloss, but your mileage may vary. Before switching to a new mode, you may wish to de-configure the old one (send `help` to the bridge bot and unbridge your portals, etc.).
 
+### Extending the configuration
 
-### Bridge permissions
+There are some additional things you may wish to configure about the bridge.
 
-By default, any user on your homeserver will be able to use the bridge.
-
-Different levels of permission can be granted to users:
-
-- `relay` - Allowed to be relayed through the bridge, no access to commands
-- `user` - Use the bridge with puppeting
-- `admin` - Use and administer the bridge
-
-The permissions are following the sequence: nothing < `relay` < `user` < `admin`.
-
-The default permissions are set via `matrix_mautrix_meta_messenger_bridge_permissions_default` and are somewhat like this:
-```yaml
-matrix_mautrix_meta_messenger_bridge_permissions_default:
-  '*': relay
-  example.com: user
-  '{{ matrix_admin }}': admin
-```
-
-If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @user:example.com`), then there's no admin by default.
-
-You may redefine `matrix_mautrix_meta_messenger_bridge_permissions_default` any way you see fit, or add extra permissions using `matrix_mautrix_meta_messenger_bridge_permissions_custom` like this:
-
-```yaml
-matrix_mautrix_meta_messenger_bridge_permissions_custom:
-  '@YOUR_USERNAME:example.com': admin
-```
-
-You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure.
+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.
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-## Set up Double Puppeting
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
 
-If you'd like to use [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do), you have 2 ways of going about it.
+**Notes**:
 
-### Method 1: automatically, by enabling Appservice Double Puppet
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-The bridge will automatically perform Double Puppeting if you enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook.
-
-Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
-
-### Method 2: manually, by asking each user to provide a working access token
-
-**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging (see [Usage](#usage)).
-
-When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:
-
-- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md).
-
-- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`
-
-- make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
+  `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.
 
 ## Usage
 
-You then need to start a chat with `@messengerbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `@messengerbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). Note that the user ID of the bridge's bot is not `@facebookbot:example.com`.
 
-You then need to send a `login` command and follow the bridge bot's instructions.
+You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/meta/authentication.html).
 
-Given that the bot is configured in `messenger` [bridge mode](#bridge-mode) by default, you will need to log in to [messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain the cookies from there as per [the bridge's authentication instructions](https://docs.mau.fi/bridges/go/meta/authentication.html).
+After logging in, the bridge will sync recent chats.
+
+**Note**: given that the bot is configured in `messenger` [bridge mode](#bridge-mode) by default, you will need to log in to [messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain the cookies from there.
diff --git a/docs/configuring-playbook-bridge-mautrix-signal.md b/docs/configuring-playbook-bridge-mautrix-signal.md
index ec9d18024..f0f1ccf74 100644
--- a/docs/configuring-playbook-bridge-mautrix-signal.md
+++ b/docs/configuring-playbook-bridge-mautrix-signal.md
@@ -1,12 +1,24 @@
-# Setting up Mautrix Signal (optional)
+# Setting up Mautrix Signal bridging (optional)
+
+<sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>
 
 The playbook can install and configure [mautrix-signal](https://github.com/mautrix/signal) for you.
 
-See the project's [documentation](https://docs.mau.fi/bridges/python/signal/index.html) to learn what it does and why it might be useful to you.
+See the project's [documentation](https://docs.mau.fi/bridges/go/signal/index.html) to learn what it does and why it might be useful to you.
 
-**Note/Prerequisite**: If you're running with the Postgres database server integrated by the playbook (which is the default), you don't need to do anything special and can easily proceed with installing. However, if you're [using an external Postgres server](configuring-playbook-external-postgres.md), you'd need to manually prepare a Postgres database for this bridge and adjust the variables related to that (`matrix_mautrix_signal_database_*`).
+## Prerequisites (optional)
 
-**Note**: This revamped version of the [mautrix-signal (legacy)](configuring-playbook-bridge-mautrix-signal.md) may increase the CPU usage of your homeserver.
+### Prepare Postgres database on external Postgres server
+
+If you're running with the Postgres database server integrated by the playbook (which is the default), you don't need to do anything special and can easily proceed with installing.
+
+However, if you're [using an external Postgres server](configuring-playbook-external-postgres.md), you'd need to manually prepare a Postgres database for this bridge and adjust the variables related to that (`matrix_mautrix_signal_database_*`).
+
+### Enable Appservice Double Puppet
+
+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.
+
+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.
 
 ## Adjusting the playbook configuration
 
@@ -16,71 +28,35 @@ To enable the bridge, add the following configuration to your `inventory/host_va
 matrix_mautrix_signal_enabled: true
 ```
 
-There are some additional things you may wish to configure about the bridge before you continue.
+### Extending the configuration
 
-By default, any user on your homeserver will be able to use the bridge.
+There are some additional things you may wish to configure about the bridge.
 
-Different levels of permission can be granted to users:
-
-* relay - Allowed to be relayed through the bridge, no access to commands;
-* user - Use the bridge with puppeting;
-* admin - Use and administer the bridge.
-
-The permissions are following the sequence: nothing < relay < user < admin.
-
-The default permissions are set as follows:
-```yaml
-permissions:
-  '*': relay
-  example.com: user
-```
-
-If you want to augment the preset permissions, you might want to set the additional permissions with the following settings in your `vars.yml` file:
-```yaml
-matrix_mautrix_signal_configuration_extension_yaml: |
-  bridge:
-    permissions:
-      '@YOUR_USERNAME:example.com': admin
-```
-
-This will add the admin permission to the specific user, while keeping the default permissions.
-
-In case you want to replace the default permissions settings **completely**, populate the following item within your `vars.yml` file:
-```yaml
-matrix_mautrix_signal_bridge_permissions:
-  '@ADMIN:example.com': admin
-  '@USER:example.com' : user
-```
-
-You may wish to look at `roles/custom/matrix-bridge-mautrix-signal/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure.
+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.
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-## Set up Double Puppeting
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
 
-If you'd like to use [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do), you have 2 ways of going about it.
+**Notes**:
 
-### Method 1: automatically, by enabling Appservice Double Puppet
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-The bridge will automatically perform Double Puppeting if you enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook.
-
-This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
-
-### Method 2: manually, by asking each user to provide a working access token
-
-**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging (see [Usage](#usage)).
-
-When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:
-
-- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md).
-
-- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`
-
-- make sure you don't log out the `Mautrix-Signal` device some time in the future, as that would break the Double Puppeting feature
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
+  `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.
 
 ## Usage
 
-You then need to start a chat with `@signalbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `@signalbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+
+You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/signal/authentication.html).
+
+After logging in, the bridge will bridge chats as you receive messages.
+
+**Note**: Signal does not support any kind of message history (even on official apps), so the bridge won't backfill any messages.
diff --git a/docs/configuring-playbook-bridge-mautrix-slack.md b/docs/configuring-playbook-bridge-mautrix-slack.md
index 43eaf274b..b113f52f0 100644
--- a/docs/configuring-playbook-bridge-mautrix-slack.md
+++ b/docs/configuring-playbook-bridge-mautrix-slack.md
@@ -1,7 +1,9 @@
-# Setting up Mautrix Slack (optional)
+# Setting up Mautrix Slack bridging (optional)
+
+<sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>
 
 **Note**: bridging to [Slack](https://slack.com/) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) bridges supported by the playbook.
-- For using as a Bot we recommend the [Appservice Slack](configuring-playbook-bridge-appservice-slack.md), because it supports plumbing.
+- 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.
 - 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.
 
 The playbook can install and configure [mautrix-slack](https://github.com/mautrix/slack) for you.
@@ -10,13 +12,17 @@ See the project's [documentation](https://docs.mau.fi/bridges/go/slack/index.htm
 
 See the [features and roadmap](https://github.com/mautrix/slack/blob/main/ROADMAP.md) for more information.
 
-
 ## Prerequisites
 
 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).
 
 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.
 
+### Enable Appservice Double Puppet (optional)
+
+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.
+
+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.
 
 ## Adjusting the playbook configuration
 
@@ -26,56 +32,34 @@ To enable the bridge, add the following configuration to your `inventory/host_va
 matrix_mautrix_slack_enabled: true
 ```
 
-You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation.
+### Extending the configuration
+
+There are some additional things you may wish to configure about the bridge.
+
+<!-- NOTE: relay mode is not supported for this bridge -->
+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.
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command:
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-```
-ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
 ```
 
-To make use of the bridge, see [Usage](#usage) below.
+**Notes**:
 
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-### Additional configuration
-
-There are some additional options you may wish to configure with the bridge.
-
-Take a look at:
-
-- `roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
-- `roles/custom/matrix-bridge-mautrix-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_mautrix_slack_configuration_extension_yaml` variable
-
-
-### Set up Double Puppeting
-
-If you'd like to use [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do), you have 2 ways of going about it.
-
-#### Method 1: automatically, by enabling Appservice Double Puppet
-
-The bridge will automatically perform Double Puppeting if you enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook.
-
-This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
-
-#### Method 2: manually, by asking each user to provide a working access token
-
-**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging (see [Usage](#usage)).
-
-When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:
-
-- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md).
-
-- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`
-
-- make sure you don't log out the `Mautrix-Slack` device some time in the future, as that would break the Double Puppeting feature
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
+  `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.
 
 ## Usage
 
-1. Start a chat with `@slackbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
-2. If you would like to login to Slack using a token, send the `login-token` command, otherwise, send the `login-password` command. Read [here](https://docs.mau.fi/bridges/go/slack/authentication.html) on how to retrieve your token and cookie token.
-3. The bot should respond with "Successfully logged into <email> for team <workspace>"
-4. Now that you're logged in, you can send a `help` command to the bot again, to see additional commands you have access to.
-5. Slack channels should automatically begin bridging if you authenticated using a token. Otherwise, you must wait to receive a message in the channel if you used password authentication.
+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).
+
+You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/slack/authentication.html).
+
+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.
diff --git a/docs/configuring-playbook-bridge-mautrix-telegram.md b/docs/configuring-playbook-bridge-mautrix-telegram.md
index 48ed559a1..f3deabc77 100644
--- a/docs/configuring-playbook-bridge-mautrix-telegram.md
+++ b/docs/configuring-playbook-bridge-mautrix-telegram.md
@@ -1,12 +1,32 @@
-# Setting up Mautrix Telegram (optional)
+# Setting up Mautrix Telegram bridging (optional)
+
+<sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>
 
 The playbook can install and configure [mautrix-telegram](https://github.com/mautrix/telegram) for you.
 
 See the project's [documentation](https://docs.mau.fi/bridges/python/telegram/index.html) to learn what it does and why it might be useful to you.
 
+## Prerequisites
+
+### Obtain a Telegram API key
+
+To use the bridge, you'd need to obtain an API key from [https://my.telegram.org/apps](https://my.telegram.org/apps).
+
+### Enable Appservice Double Puppet or Shared Secret Auth (optional)
+
+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.
+
+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.
+
+**Notes**:
+
+- Double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future.
+
+- If you decided to enable Double Puppeting manually, send `login-matrix` to the bot in order to receive an instruction about how to send an access token to it.
+
 ## Adjusting the playbook configuration
 
-You'll need to obtain API keys from [https://my.telegram.org/apps](https://my.telegram.org/apps) and then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `YOUR_TELEGRAM_APP_ID` and `YOUR_TELEGRAM_API_HASH`.
 
 ```yaml
 matrix_mautrix_telegram_enabled: true
@@ -14,40 +34,11 @@ matrix_mautrix_telegram_api_id: YOUR_TELEGRAM_APP_ID
 matrix_mautrix_telegram_api_hash: YOUR_TELEGRAM_API_HASH
 ```
 
-## Installing
+### Relaying
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+### Enable relay-bot (optional)
 
-## Set up Double Puppeting
-
-If you'd like to use [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do), you have 2 ways of going about it.
-
-### Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth
-
-The bridge will automatically perform Double Puppeting if you enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service or the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook.
-
-Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
-
-Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future.
-
-### Method 2: manually, by asking each user to provide a working access token
-
-**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging.
-
-When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:
-
-- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md).
-
-- send `login-matrix` to the bot and follow instructions about how to send the access token to it
-
-- make sure you don't log out the `Mautrix-Telegram` device some time in the future, as that would break the Double Puppeting feature
-
-
-## Usage
-
-You then need to start a chat with `@telegrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
-
-If you want to use the relay-bot feature ([relay bot documentation](https://docs.mau.fi/bridges/python/telegram/relay-bot.html)), which allows anonymous user to chat with telegram users, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+If you want to use the relay-bot feature ([relay bot documentation](https://docs.mau.fi/bridges/python/telegram/relay-bot.html)), which allows anonymous user to chat with telegram users, add the following configuration to your `vars.yml` file:
 
 ```yaml
 matrix_mautrix_telegram_bot_token: YOUR_TELEGRAM_BOT_TOKEN
@@ -57,17 +48,48 @@ matrix_mautrix_telegram_configuration_extension_yaml: |
       '*': relaybot
 ```
 
-You might also want to give permissions to administrate the bot:
-```yaml
-matrix_mautrix_telegram_configuration_extension_yaml: |
-  bridge:
-    permissions:
-      '@user:example.com': admin
-```
+### Configure a user as an administrator of the bridge (optional)
+
+You might also want to give permissions to a user to administrate the bot. See [this section](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional) on the common guide for details about it.
 
 More details about permissions in this example: https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-config.yaml#L410
 
-If you like to exclude all groups from syncing and use the Telgeram-Bridge only for direct chats, you can add the following additional playbook configuration:
+### Use the bridge for direct chats only (optional)
+
+If you want to exclude all groups from syncing and use the Telegram-Bridge only for direct chats, add the following configuration to your `vars.yml` file:
+
 ```yaml
 matrix_mautrix_telegram_filter_mode: whitelist
 ```
+
+### Extending the configuration
+
+There are some additional things you may wish to configure about the bridge.
+
+<!-- NOTE: common relay mode is not supported for this bridge -->
+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.
+
+## Installing
+
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
+
+## Usage
+
+To use the bridge, you need to start a chat with `@telegrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+
+You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/telegram/authentication.html).
+
+After logging in, the bridge will create portal rooms for all of your Telegram groups and invite you to them. Note that the bridge won't automatically create rooms for private chats.
diff --git a/docs/configuring-playbook-bridge-mautrix-twitter.md b/docs/configuring-playbook-bridge-mautrix-twitter.md
index fe08c77bf..bb25019fe 100644
--- a/docs/configuring-playbook-bridge-mautrix-twitter.md
+++ b/docs/configuring-playbook-bridge-mautrix-twitter.md
@@ -1,10 +1,20 @@
-# Setting up Mautrix Twitter (optional)
+# Setting up Mautrix Twitter bridging (optional)
+
+<sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>
 
 **Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md) bridge supported by the playbook.
 
 The playbook can install and configure [mautrix-twitter](https://github.com/mautrix/twitter) for you.
 
-See the project's [documentation](https://github.com/mautrix/twitter) to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/mautrix/twitter/blob/master/README.md) to learn what it does and why it might be useful to you.
+
+## Prerequisite (optional)
+
+### Enable Appservice Double Puppet
+
+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.
+
+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.
 
 ## Adjusting the playbook configuration
 
@@ -14,31 +24,34 @@ To enable the bridge, add the following configuration to your `inventory/host_va
 matrix_mautrix_twitter_enabled: true
 ```
 
+### Extending the configuration
+
+There are some additional things you may wish to configure about the bridge.
+
+<!-- NOTE: relay mode is not supported for this bridge -->
+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.
+
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-## Set up Double Puppeting
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
 
-If you'd like to use [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do), you have 2 ways of going about it.
+**Notes**:
 
-### Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-The bridge will automatically perform Double Puppeting if you enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service or the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook.
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
-Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
-
-Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future.
-
-### Method 2: manually, by asking each user to provide a working access token
-
-This method is currently not available for the Mautrix-Twitter bridge, but is on the [roadmap](https://github.com/mautrix/twitter/blob/master/ROADMAP.md) under Misc/Manual login with `login-matrix`
+  `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.
 
 ## Usage
 
-1. You then need to start a chat with `@twitterbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
-2. Send login-cookie to start the login. The bot should respond with instructions on how to proceed.
+To use the bridge, you need to start a chat with `@twitterbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
 
-You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/twitter/authentication.html).
+You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/twitter/authentication.html).
 
-After successfully enabling bridging, you may wish to [set up Double Puppeting](#set-up-double-puppeting), if you haven't already done so.
+After logging in, the bridge will create portal rooms for some recent chats. Portal rooms for other chats will be created as you receive messages.
diff --git a/docs/configuring-playbook-bridge-mautrix-whatsapp.md b/docs/configuring-playbook-bridge-mautrix-whatsapp.md
index c04940ebf..8201be513 100644
--- a/docs/configuring-playbook-bridge-mautrix-whatsapp.md
+++ b/docs/configuring-playbook-bridge-mautrix-whatsapp.md
@@ -1,9 +1,21 @@
-# Setting up Mautrix Whatsapp (optional)
+# Setting up Mautrix Whatsapp bridging (optional)
+
+<sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>
 
 The playbook can install and configure [mautrix-whatsapp](https://github.com/mautrix/whatsapp) for you.
 
 See the project's [documentation](https://docs.mau.fi/bridges/go/whatsapp/index.html) to learn what it does and why it might be useful to you.
 
+## Prerequisite (optional)
+
+### Enable Appservice Double Puppet or Shared Secret Auth
+
+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.
+
+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.
+
+**Note**: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future.
+
 ## Adjusting the playbook configuration
 
 To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
@@ -12,51 +24,35 @@ To enable the bridge, add the following configuration to your `inventory/host_va
 matrix_mautrix_whatsapp_enabled: true
 ```
 
-Whatsapp multidevice beta is required, now it is enough if Whatsapp is connected to the Internet every 2 weeks.
+### Extending the configuration
 
-The relay bot functionality is off by default. If you would like to enable the relay bot, add the following to your `vars.yml` file:
+There are some additional things you may wish to configure about the bridge.
 
-```yaml
-matrix_mautrix_whatsapp_bridge_relay_enabled: true
-```
-
-By default, only admins are allowed to set themselves as relay users. To allow anyone on your homeserver to set themselves as relay users add this to your `vars.yml` file:
-
-```yaml
-matrix_mautrix_whatsapp_bridge_relay_admin_only: false
-```
-
-If you want to activate the relay bot in a room, send `!wa set-relay`. To deactivate, send `!wa unset-relay`.
+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.
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-## Set up Double Puppeting
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
 
-If you'd like to use [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do), you have 2 ways of going about it.
+**Notes**:
 
-### Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
 
-The bridge will automatically perform Double Puppeting if you enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service or the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook.
-
-Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
-
-Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future.
-
-### Method 2: manually, by asking each user to provide a working access token
-
-**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging (see [Usage](#usage)).
-
-When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:
-
-- retrieve a Matrix access token for yourself. Refer to the documentation on [how to do that](obtaining-access-tokens.md).
-
-- send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`
-
-- make sure you don't log out the `Mautrix-Whatsapp` device some time in the future, as that would break the Double Puppeting feature
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
+  `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.
 
 ## Usage
 
-You then need to start a chat with `@whatsappbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `@whatsappbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+
+You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/whatsapp/authentication.html).
+
+Approximately in a minute after logging in, the bridge will create portal rooms for recent chats.
+
+**Note**: your linked devices will be logged out if you don’t use your phone for over 14 days (see the official FAQ entry [here](https://faq.whatsapp.com/general/download-and-installation/about-linked-devices)). The bridge will warn you if it doesn't receive any data from the phone over 12 days.
diff --git a/docs/configuring-playbook-bridge-mautrix-wsproxy.md b/docs/configuring-playbook-bridge-mautrix-wsproxy.md
index b32a4749d..bdc1f3bb2 100644
--- a/docs/configuring-playbook-bridge-mautrix-wsproxy.md
+++ b/docs/configuring-playbook-bridge-mautrix-wsproxy.md
@@ -1,8 +1,16 @@
-# Setting up Mautrix wsproxy (optional)
+# Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage (optional)
+
+<sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>
 
 The playbook can install and configure [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for you.
 
-See the project's [documentation](https://github.com/mautrix/wsproxy#readme) to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/mautrix/wsproxy/blob/master/README.md) to learn what it does and why it might be useful to you.
+
+## Adjusting DNS records
+
+By default, this playbook installs wsproxy on the `wsproxy.` subdomain (`wsproxy.example.com`) and requires you to create a CNAME record for `wsproxy`, which targets `matrix.example.com`.
+
+When setting, replace `example.com` with your own.
 
 ## Adjusting the playbook configuration
 
@@ -20,29 +28,42 @@ matrix_mautrix_wsproxy_syncproxy_shared_secret: 'secret token from bridge'
 
 Note that the tokens must match what is compiled into the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android device.
 
-### Adjusting the wsproxy URL
+### Extending the configuration
 
-By default, this playbook installs wsproxy on the `wsproxy.` subdomain (`wsproxy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records).
+There are some additional things you may wish to configure about the bridge.
+
+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.
+
+### Adjusting the wsproxy URL (optional)
 
 By tweaking the `matrix_mautrix_wsproxy_hostname` variable, you can easily make the service available at a **different hostname** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Change the default hostname
 matrix_mautrix_wsproxy_hostname: ws.example.com
 ```
 
-## Adjusting DNS records
-
-Once you've decided on the domain, **you may need to adjust your DNS** records to point the wsproxy domain to the Matrix server.
-
-By default, you will need to create a CNAME record for `wsproxy`. See [Configuring DNS](configuring-dns.md) for details about DNS changes.
+After changing the domain, **you may need to adjust your DNS** records to point the wsproxy domain to the Matrix server.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
-Follow the [matrix-imessage documenation](https://docs.mau.fi/bridges/go/imessage/index.html) for running `android-sms` and/or `matrix-imessage` on your device(s).
+Follow the [mautrix-imessage documenation](https://docs.mau.fi/bridges/go/imessage/index.html) for running `android-sms` and/or `matrix-imessage` on your device(s).
diff --git a/docs/configuring-playbook-bridge-mx-puppet-discord.md b/docs/configuring-playbook-bridge-mx-puppet-discord.md
index 01eaef8d4..cbc61c068 100644
--- a/docs/configuring-playbook-bridge-mx-puppet-discord.md
+++ b/docs/configuring-playbook-bridge-mx-puppet-discord.md
@@ -1,14 +1,12 @@
-# Setting up MX Puppet Discord (optional)
+# Setting up MX Puppet Discord bridging (optional)
 
 **Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md)and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook.   
 - For using as a Bot we recommend the [Appservice Discord](configuring-playbook-bridge-appservice-discord.md), because it supports plumbing.  
 - For personal use with a discord account we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook.
 
-The playbook can install and configure [mx-puppet-discord](https://github.com/matrix-discord/mx-puppet-discord) for you.
+The playbook can install and configure [mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) for you.
 
-See the project page to learn what it does and why it might be useful to you.
-
-**Note**: we actually use the [Beeper](https://www.beeper.com/)-maintained [fork of mx-puppet-discord](https://gitlab.com/beeper/mx-puppet-monorepo), because `matrix-discord/mx-puppet-discord` is a low-quality and poorly maintained project.
+See the project's [documentation](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/blob/master/README.md) to learn what it does and why it might be useful to you.
 
 ## Adjusting the playbook configuration
 
@@ -20,16 +18,29 @@ matrix_mx_puppet_discord_enabled: true
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
-Once the bot is enabled you need to start a chat with `Discord Puppet Bridge` with the handle `@_discordpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `Discord Puppet Bridge` with the handle `@_discordpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
 
-Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-discord [documentation](https://github.com/matrix-discord/mx-puppet-discord) for more information about how to configure the bridge.
+Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-discord [documentation](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) for more information about how to configure the bridge.
 
 Once logged in, send `list` to the bot user to list the available rooms.
 
 Clicking rooms in the list will result in you receiving an invitation to the bridged room.
 
-Also send `help` to the bot to see the commands available.
+Send `help` to the bot to see the available commands.
diff --git a/docs/configuring-playbook-bridge-mx-puppet-groupme.md b/docs/configuring-playbook-bridge-mx-puppet-groupme.md
index 5090b2d59..6a7f8bb97 100644
--- a/docs/configuring-playbook-bridge-mx-puppet-groupme.md
+++ b/docs/configuring-playbook-bridge-mx-puppet-groupme.md
@@ -1,8 +1,8 @@
-# Setting up MX Puppet GroupMe (optional)
+# Setting up MX Puppet GroupMe bridging (optional)
 
 The playbook can install and configure [mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) for you.
 
-See the project page to learn what it does and why it might be useful to you.
+See the project's [documentation](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme/blob/master/README.md) to learn what it does and why it might be useful to you.
 
 ## Adjusting the playbook configuration
 
@@ -14,11 +14,24 @@ matrix_mx_puppet_groupme_enabled: true
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
-Once the bot is enabled you need to start a chat with `GroupMe Puppet Bridge` with the handle `@_groupmepuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `GroupMe Puppet Bridge` with the handle `@_groupmepuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
 
 One authentication method is available.
 
@@ -32,4 +45,4 @@ Once logged in, send `listrooms` to the bot user to list the available rooms.
 
 Clicking rooms in the list will result in you receiving an invitation to the bridged room.
 
-Also send `help` to the bot to see the commands available.
+Send `help` to the bot to see the available commands.
diff --git a/docs/configuring-playbook-bridge-mx-puppet-instagram.md b/docs/configuring-playbook-bridge-mx-puppet-instagram.md
index 145baa49a..53375a029 100644
--- a/docs/configuring-playbook-bridge-mx-puppet-instagram.md
+++ b/docs/configuring-playbook-bridge-mx-puppet-instagram.md
@@ -1,4 +1,4 @@
-# Setting up mx-puppet-instagram (optional)
+# Setting up MX Puppet Instagram bridging (optional)
 
 The playbook can install and configure [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) for you.
 
@@ -14,11 +14,24 @@ matrix_mx_puppet_instagram_enabled: true
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
-Once the bot is enabled, you need to start a chat with `Instagram Puppet Bridge` with the handle `@_instagrampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `Instagram Puppet Bridge` with the handle `@_instagrampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
 
 Send `link <username> <password>` to the bridge bot to link your instagram account.
 
@@ -32,4 +45,4 @@ For double-puppeting, you probably want to issue these commands:
 
 If you are linking only one Instagram account, your `$puppetId` is probably 1, but use the `list` command find out.
 
-The `help` command shows which commands are available, though at the time of writing, not every command is fully implemented.
+Send `help` to the bot to see the available commands. At the time of writing, not every command is fully implemented.
diff --git a/docs/configuring-playbook-bridge-mx-puppet-skype.md b/docs/configuring-playbook-bridge-mx-puppet-skype.md
index c80b1af82..bc9d6d534 100644
--- a/docs/configuring-playbook-bridge-mx-puppet-skype.md
+++ b/docs/configuring-playbook-bridge-mx-puppet-skype.md
@@ -1,5 +1,5 @@
-# Setting up MX Puppet Skype (optional)
+# Setting up MX Puppet Skype bridging (optional, removed)
 
-The playbook used to be able to install and configure [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype), but no longer includes this component, because it has been broken and unmaintaned for a long time.
+The playbook used to be able to install and configure [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype), but no longer includes this component, because it has been broken and unmaintained for a long time.
 
 Bridging to [Skype](https://www.skype.com/) can also happen via the [go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md) bridge supported by the playbook.
diff --git a/docs/configuring-playbook-bridge-mx-puppet-slack.md b/docs/configuring-playbook-bridge-mx-puppet-slack.md
index 44d86056f..b8e8971b6 100644
--- a/docs/configuring-playbook-bridge-mx-puppet-slack.md
+++ b/docs/configuring-playbook-bridge-mx-puppet-slack.md
@@ -1,15 +1,14 @@
-# Setting up MX Puppet Slack (optional)
+# Setting up MX Puppet Slack bridging (optional)
 
-**Note**: bridging to [Slack](https://slack.com) can also happen via the
-[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook.
+**Note**: bridging to [Slack](https://slack.com) can also happen via the [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook. Note that `matrix-appservice-slack` 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.
 
-The playbook can install and configure [Beeper](https://www.beeper.com/)-maintained fork of [mx-puppet-slack](https://gitlab.com/beeper/mx-puppet-monorepo) for you.
+The playbook can install and configure [mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for you.
 
-See the project page to learn what it does and why it might be useful to you.
+See the project's [documentation](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/blob/master/README.md) to learn what it does and why it might be useful to you.
 
 ## Prerequisite
 
-Follow the [OAuth credentials](https://github.com/Sorunome/mx-puppet-slack#option-2-oauth) instructions to create a new Slack app, setting the redirect URL to `https://matrix.example.com/slack/oauth`.
+Follow the [OAuth credentials](https://gitlab.com/mx-puppet/slack/mx-puppet-slack#option-2-oauth) instructions to create a new Slack app, setting the redirect URL to `https://matrix.example.com/slack/oauth`.
 
 ## Adjusting the playbook configuration
 
@@ -24,20 +23,29 @@ matrix_mx_puppet_slack_oauth_client_secret: "<SLACK_APP_CLIENT_SECRET>"
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command:
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
 ```
-ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
-```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
-Once the bot is enabled you need to start a chat with `Slack Puppet Bridge` with the handle `@_slackpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `Slack Puppet Bridge` with the handle `@_slackpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
 
-Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-slack [documentation](https://github.com/Sorunome/mx-puppet-slack) for more information about how to configure the bridge.
+Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-slack [documentation](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for more information about how to configure the bridge.
 
 Once logged in, send `list` to the bot user to list the available rooms.
 
 Clicking rooms in the list will result in you receiving an invitation to the bridged room.
 
-Also send `help` to the bot to see the commands available.
+Send `help` to the bot to see the available commands.
diff --git a/docs/configuring-playbook-bridge-mx-puppet-steam.md b/docs/configuring-playbook-bridge-mx-puppet-steam.md
index 66edf8c79..18ea7ad22 100644
--- a/docs/configuring-playbook-bridge-mx-puppet-steam.md
+++ b/docs/configuring-playbook-bridge-mx-puppet-steam.md
@@ -1,8 +1,8 @@
-# Setting up MX Puppet Steam (optional)
+# Setting up MX Puppet Steam bridging (optional)
 
 The playbook can install and configure [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) for you.
 
-See the project page to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/icewind1991/mx-puppet-steam/blob/master/README.md) to learn what it does and why it might be useful to you.
 
 ## Adjusting the playbook configuration
 
@@ -14,11 +14,24 @@ matrix_mx_puppet_steam_enabled: true
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
-Once the bot is enabled you need to start a chat with `Steam Puppet Bridge` with the handle `@_steampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `Steam Puppet Bridge` with the handle `@_steampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
 
 Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-steam [documentation](https://github.com/icewind1991/mx-puppet-steam) for more information about how to configure the bridge.
 
@@ -26,4 +39,4 @@ Once logged in, send `list` to the bot user to list the available rooms.
 
 Clicking rooms in the list will result in you receiving an invitation to the bridged room.
 
-Also send `help` to the bot to see the commands available.
+Send `help` to the bot to see the available commands.
diff --git a/docs/configuring-playbook-bridge-mx-puppet-twitter.md b/docs/configuring-playbook-bridge-mx-puppet-twitter.md
index 493eb1403..be0df2305 100644
--- a/docs/configuring-playbook-bridge-mx-puppet-twitter.md
+++ b/docs/configuring-playbook-bridge-mx-puppet-twitter.md
@@ -1,10 +1,10 @@
-# Setting up MX Puppet Twitter (optional)
+# Setting up MX Puppet Twitter bridging (optional)
 
 **Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mautrix-twitter](configuring-playbook-bridge-mautrix-twitter.md) bridge supported by the playbook.
 
 The playbook can install and configure [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) for you.
 
-See the project page to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/Sorunome/mx-puppet-twitter/blob/master/README.md) to learn what it does and why it might be useful to you.
 
 ## Prerequisite
 
@@ -25,11 +25,24 @@ matrix_mx_puppet_twitter_environment: ''
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
-Once the bot is enabled you need to start a chat with `Twitter Puppet Bridge` with the handle `@_twitterpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `Twitter Puppet Bridge` with the handle `@_twitterpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
 
 To log in, use `link` and click the link.
 
@@ -37,4 +50,4 @@ Once logged in, send `list` to the bot user to list the available rooms.
 
 Clicking rooms in the list will result in you receiving an invitation to the bridged room.
 
-Also send `help` to the bot to see the commands available.
+Send `help` to the bot to see the available commands.
diff --git a/docs/configuring-playbook-bridge-postmoogle.md b/docs/configuring-playbook-bridge-postmoogle.md
new file mode 100644
index 000000000..af52e6acc
--- /dev/null
+++ b/docs/configuring-playbook-bridge-postmoogle.md
@@ -0,0 +1,95 @@
+# Setting up Postmoogle email bridging (optional)
+
+**Note**: email bridging can also happen via the [email2matrix](configuring-playbook-email2matrix.md) bridge supported by the playbook.
+
+The playbook can install and configure [Postmoogle](https://github.com/etkecc/postmoogle) for you.
+
+Postmoogle is a bridge you can use to have its bot user forward emails to Matrix rooms. It runs an SMTP email server and allows you to assign mailbox addresses to the rooms.
+
+See the project's [documentation](https://github.com/etkecc/postmoogle/blob/master/README.md) to learn what it does and why it might be useful to you.
+
+## Prerequisites
+
+Open the following ports on your server to be able to receive incoming emails:
+
+  - `25/tcp`: SMTP
+  - `587/tcp`: Submission (TLS-encrypted SMTP)
+
+If you don't open these ports, you will still be able to send emails, but not receive any.
+
+These port numbers are configurable via the `matrix_postmoogle_smtp_host_bind_port` and `matrix_postmoogle_submission_host_bind_port` variables, but other email servers will try to deliver on these default (standard) ports, so changing them is of little use.
+
+## Adjusting DNS records
+
+To make Postmoogle enable its email sending features, you need to configure MX and TXT (SPF, DMARC, and DKIM) records. See the table below for values which need to be specified.
+
+| Type | Host                           | Priority | Weight | Port | Target                             |
+|------|--------------------------------|----------|--------|------|------------------------------------|
+| MX   | `matrix`                       | 10       | 0      | -    | `matrix.example.com`               |
+| TXT  | `matrix`                       | -        | -      | -    | `v=spf1 ip4:matrix-server-IP -all` |
+| TXT  | `_dmarc.matrix`                | -        | -      | -    | `v=DMARC1; p=quarantine;`          |
+| TXT  | `postmoogle._domainkey.matrix` | -        | -      | -    | get it from `!pm dkim`             |
+
+**Note**: the DKIM record can be retrieved after configuring and installing the bridge's bot.
+
+## Adjusting the playbook configuration
+
+Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+
+```yaml
+matrix_postmoogle_enabled: true
+
+# Uncomment and adjust this part if you'd like to use a username different than the default
+# matrix_postmoogle_login: postmoogle
+
+# Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`.
+matrix_postmoogle_password: PASSWORD_FOR_THE_BOT
+
+# Uncomment to add one or more admins to this bridge:
+#
+# matrix_postmoogle_admins:
+#  - '@yourAdminAccount:{{ matrix_domain }}'
+#
+# … unless you've made yourself an admin of all bots/bridges like this:
+#
+# matrix_admin: '@yourAdminAccount:{{ matrix_domain }}'
+```
+
+## Installing
+
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create a user account of the bridge's bot.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
+
+- If you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password.
+
+## Usage
+
+To use the bridge, invite the `@postmoogle:example.com` bot user into a room you want to use as a mailbox.
+
+Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with the email address `NAME@matrix.example.com`. Emails sent to that email address will be forwarded to the room.
+
+Send `!pm help` to the bot in the room to see the available commands.
+
+You can also refer to the upstream [documentation](https://github.com/etkecc/postmoogle).
+
+### Debug/Logs
+
+As with all other services, you can find their logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-postmoogle`
+
+The default logging level for this bridge is `INFO`, but you can increase it to `DEBUG` with the following additional configuration:
+
+```yaml
+matrix_postmoogle_loglevel: 'DEBUG'
+```
diff --git a/docs/configuring-playbook-bridge-wechat.md b/docs/configuring-playbook-bridge-wechat.md
index e5a1546c7..0016cbdd9 100644
--- a/docs/configuring-playbook-bridge-wechat.md
+++ b/docs/configuring-playbook-bridge-wechat.md
@@ -1,8 +1,8 @@
-# Setting up the WeChat Bridge (optional)
+# Setting up WeChat bridging (optional)
 
-The playbook can install and configure the [matrix-wechat](https://github.com/duo/matrix-wechat) bridge for you (for bridging to the [WeChat](https://www.wechat.com/) network).
+The playbook can install and configure [matrix-wechat](https://github.com/duo/matrix-wechat) for you, for bridging to [WeChat](https://www.wechat.com/).
 
-See the project page to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/duo/matrix-wechat/blob/master/README.md) to learn what it does and why it might be useful to you.
 
 ## Adjusting the playbook configuration
 
@@ -14,10 +14,23 @@ matrix_wechat_enabled: true
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
-Once the bridge is installed, start a chat with `@wechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
+To use the bridge, you need to start a chat with `@wechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
 
 Send `help` to the bot to see the available commands.
diff --git a/docs/configuring-playbook-cactus-comments.md b/docs/configuring-playbook-cactus-comments.md
index 0607e288e..ee5213be9 100644
--- a/docs/configuring-playbook-cactus-comments.md
+++ b/docs/configuring-playbook-cactus-comments.md
@@ -14,7 +14,13 @@ The playbook contains 2 roles for configuring different pieces of the Cactus Com
 
 You can enable whichever component you need (typically both).
 
-## Configuration
+## Adjusting DNS records (optional)
+
+By default, this playbook installs Cactus Comments' client on the `matrix.` subdomain, at the `/cactus-comments` path (https://matrix.example.com/cactus-comments). 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.
+
+If you wish to adjust it, see the section [below](#adjusting-the-cactus-comments-client-url-optional) for details about DNS configuration.
+
+## Adjusting the playbook configuration
 
 To enable Cactus Comments, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
@@ -38,13 +44,11 @@ matrix_cactus_comments_enabled: true
 matrix_cactus_comments_client_enabled: true
 ```
 
-### Adjusting the Cactus Comments' client URL
-
-By default, this playbook installs Cactus Comments' client on the `matrix.` subdomain, at the `/cactus-comments` path (https://matrix.example.com/cactus-comments). 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.
+### Adjusting the Cactus Comments' client URL (optional)
 
 By tweaking the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Change the default hostname and path prefix to host the client assets at a different location
@@ -53,23 +57,32 @@ matrix_cactus_comments_client_hostname: cactus.example.com
 matrix_cactus_comments_client_path_prefix: /
 ```
 
-## Adjusting DNS records
+If you've changed the default hostname, you may need to create a CNAME record for the Cactus Comments' client domain (`cactus.example.com`), which targets `matrix.example.com`.
 
-If you've changed the default hostname, **you may need to adjust your DNS** records to point the Cactus Comments' client domain to the Matrix server.
-
-See [Configuring DNS](configuring-dns.md) for details about DNS changes.
-
-If you've decided to use the default hostname, you won't need to do any extra DNS configuration.
+When setting, replace `example.com` with your own.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
 
 ## Usage
 
 Upon starting Cactus Comments, a `bot.cactusbot` user account is created automatically.
 
-To get started, send a `help` message to the `@bot.cactusbot:example.com` bot to confirm it's working.
+To get started, send `help` to the `@bot.cactusbot:example.com` bot to confirm it's working.
 
 Then, register a site by sending `register <YourSiteName>` (where `<YourSiteName>` is a unique identifier you choose. It does not have to match your domain). You will then be invited into a moderation room.
 
diff --git a/docs/configuring-playbook-client-cinny.md b/docs/configuring-playbook-client-cinny.md
index 9925c836f..4e9decb4f 100644
--- a/docs/configuring-playbook-client-cinny.md
+++ b/docs/configuring-playbook-client-cinny.md
@@ -1,8 +1,18 @@
-# Configuring Cinny (optional)
+# Setting up Cinny (optional)
 
-This playbook can install the [cinny](https://github.com/ajbura/cinny) Matrix web client for you.
+The playbook can install and configure the [Cinny](https://github.com/ajbura/cinny) Matrix web client for you.
 
-Cinny is a web client focusing primarily on simple, elegant and secure interface. It can be installed alongside or instead of Element.
+Cinny 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).
+
+💡 **Note**: the latest version of Cinny is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting:
+
+- [app.cinny.in](https://app.cinny.in), hosted by the [Cinny](https://cinny.in/) developers
+
+## Adjusting DNS records
+
+By default, this playbook installs Cinny on the `cinny.` subdomain (`cinny.example.com`) and requires you to create a CNAME record for `cinny`, which targets `matrix.example.com`.
+
+When setting, replace `example.com` with your own.
 
 ## Adjusting the playbook configuration
 
@@ -12,31 +22,33 @@ To enable Cinny, add the following configuration to your `inventory/host_vars/ma
 matrix_client_cinny_enabled: true
 ```
 
-### Adjusting the Cinny URL
+### Adjusting the Cinny URL (optional)
 
-By default, this playbook installs Cinny on the `cinny.` subdomain (`cinny.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records).
+By tweaking the `matrix_client_cinny_hostname` variable, you can easily make the service available at a **different hostname** than the default one.
 
-By tweaking the `matrix_client_cinny_hostname` and `matrix_client_cinny_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
-
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
-# Switch to the domain used for Matrix services (`matrix.example.com`),
-# so we won't need to add additional DNS records for Cinny.
-matrix_client_cinny_hostname: "{{ matrix_server_fqn_matrix }}"
+# Switch to a different domain (`app.example.com`) than the default one (`cinny.example.com`)
+matrix_client_cinny_hostname: "app.{{ matrix_domain }}"
 
 # Expose under the /cinny subpath
-matrix_client_cinny_path_prefix: /cinny
+# matrix_client_cinny_path_prefix: /cinny
 ```
 
-## Adjusting DNS records
+After changing the domain, **you may need to adjust your DNS** records to point the Cinny domain to the Matrix server.
 
-Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Cinny domain to the Matrix server.
-
-By default, you will need to create a CNAME record for `cinny`. See [Configuring DNS](configuring-dns.md) for details about DNS changes.
-
-If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration.
+**Note**: while there is a `matrix_client_cinny_path_prefix` variable for changing the path where Cinny is served, overriding it is [not possible](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Cinny requires an application rebuild (with a tweaked build config) to be functional under a custom path. You'd need to serve Cinny at a dedicated subdomain.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook and [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
diff --git a/docs/configuring-playbook-client-element-web.md b/docs/configuring-playbook-client-element-web.md
new file mode 100644
index 000000000..4d832752c
--- /dev/null
+++ b/docs/configuring-playbook-client-element-web.md
@@ -0,0 +1,114 @@
+# Configuring Element Web (optional)
+
+By default, this playbook installs the [Element Web](https://github.com/element-hq/element-web) Matrix client for you. If that's okay, you can skip this document.
+
+If you'd like to stop the playbook installing the client, see the section [below](#disabling-element-web) to check the configuration for disabling it.
+
+💡 **Note**: the latest version of Element Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting (by [disabling Element Web](#disabling-element-web)):
+
+- [app.element.io](https://app.element.io/), hosted by [Element](https://element.io/)
+- [app.etke.cc](https://app.etke.cc/), hosted by [etke.cc](https://etke.cc/)
+
+## Adjusting DNS records
+
+By default, this playbook installs Element Web on the `element.` subdomain (`element.example.com`) and requires you to create a CNAME record for `element`, which targets `matrix.example.com`.
+
+When setting, replace `example.com` with your own.
+
+## Adjusting the playbook configuration
+
+### Themes
+
+You can change the look of Element Web by pulling themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project or defining your own themes manually.
+
+#### Use themes by `element-themes`
+
+To pull the themes from the `element-themes` project and use them for your Element Web instance, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+
+```yaml
+matrix_client_element_themes_enabled: true
+```
+
+If the variable is set to `true`, all themes found in the repository specified with `matrix_client_element_themes_repository_url` will be installed and enabled automatically.
+
+Note that for a custom theme to work well, all Element Web instances that you use must have the same theme installed.
+
+#### Define themes manually
+
+You can also define your own themes manually by adding and adjusting the following configuration to your `vars.yml` file:
+
+```yaml
+# Controls the `setting_defaults.custom_themes` setting of the Element Web configuration.
+matrix_client_element_setting_defaults_custom_themes: []
+```
+
+If you define your own themes with it and set `matrix_client_element_themes_enabled` to `true` for the themes by `element-themes`, your themes will be preserved as well.
+
+If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it.
+
+### Adjusting the Element Web URL (optional)
+
+By tweaking the `matrix_client_element_hostname` and `matrix_client_element_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
+
+Example additional configuration for your `vars.yml` file:
+
+```yaml
+# Switch to the domain used for Matrix services (`matrix.example.com`),
+# so we won't need to add additional DNS records for Element Web.
+matrix_client_element_hostname: "{{ matrix_server_fqn_matrix }}"
+
+# Expose under the /element subpath
+matrix_client_element_path_prefix: /element
+```
+
+After changing the domain, **you may need to adjust your DNS** records to point the Element domain to the Matrix server.
+
+If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration.
+
+### Extending the configuration
+
+There are some additional things you may wish to configure about the component.
+
+Take a look at:
+
+- `roles/custom/matrix-client-element/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+- `roles/custom/matrix-client-element/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 `matrix_client_element_configuration_extension_json` variable
+
+For example, to override some Element Web settings, add the following configuration to your `vars.yml` file:
+
+```yaml
+ # Your custom JSON configuration for Element Web should go to `matrix_client_element_configuration_extension_json`.
+ # This configuration extends the default starting configuration (`matrix_client_element_configuration_default`).
+ #
+ # You can override individual variables from the default configuration, or introduce new ones.
+ #
+ # If you need something more special, you can take full control by
+ # completely redefining `matrix_client_element_configuration_default`.
+ #
+matrix_client_element_configuration_extension_json: |
+ {
+ "disable_3pid_login": true,
+ "disable_login_language_selector": true
+ }
+```
+
+## Disabling Element Web
+
+If you'd like for the playbook to not install Element Web (or to uninstall it if it was previously installed), add the following configuration to your `vars.yml` file:
+
+```yaml
+matrix_client_element_enabled: false
+```
+
+## Installing
+
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
diff --git a/docs/configuring-playbook-client-element.md b/docs/configuring-playbook-client-element.md
deleted file mode 100644
index c0f7c348c..000000000
--- a/docs/configuring-playbook-client-element.md
+++ /dev/null
@@ -1,69 +0,0 @@
-# Configuring Element (optional)
-
-By default, this playbook installs the [Element](https://github.com/element-hq/element-web) Matrix web client for you. If that's okay, you can skip this document.
-
-
-## Disabling Element
-
-If you'd like for the playbook to not install Element (or to uninstall it if it was previously installed), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
-
-```yaml
-matrix_client_element_enabled: false
-```
-
-
-## Adjusting the playbook configuration
-
-The playbook provides some customization variables you could use to change Element's settings.
-
-Their defaults are defined in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml) and they ultimately end up in the generated `/matrix/element/config.json` file (on the server). This file is generated from the [`roles/custom/matrix-client-element/templates/config.json.j2`](../roles/custom/matrix-client-element/templates/config.json.j2) template.
-
-**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes.
-
-Alternatively, **if there is no pre-defined variable** for an Element setting you wish to change:
-
-- you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Element's various settings that rarely get used.
-
-- or, you can **extend and override the default configuration** ([`config.json.j2`](../roles/custom/matrix-client-element/templates/config.json.j2)) by making use of the `matrix_client_element_configuration_extension_json_` variable. You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml).
-
-- or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_element_configuration_default` (or `matrix_client_element_configuration`). You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml).
-
-
-### Themes
-
-To change the look of Element, you can define your own themes manually by using the `matrix_client_element_setting_defaults_custom_themes` setting.
-
-Or better yet, you can automatically pull it all themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project by simply flipping a flag (`matrix_client_element_themes_enabled: true`).
-
-If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it.
-
-Note that for a custom theme to work well, all Element instances that you use must have the same theme installed.
-
-### Adjusting the Element URL
-
-By default, this playbook installs Element on the `element.` subdomain (`element.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records).
-
-By tweaking the `matrix_client_element_hostname` and `matrix_client_element_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
-
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
-
-```yaml
-# Switch to the domain used for Matrix services (`matrix.example.com`),
-# so we won't need to add additional DNS records for Element.
-matrix_client_element_hostname: "{{ matrix_server_fqn_matrix }}"
-
-# Expose under the /element subpath
-matrix_client_element_path_prefix: /element
-```
-
-## Adjusting DNS records
-
-Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Element domain to the Matrix server.
-
-By default, you will need to create a CNAME record for `element`. See [Configuring DNS](configuring-dns.md) for details about DNS changes.
-
-If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration.
-
-## Installing
-
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all`
diff --git a/docs/configuring-playbook-client-hydrogen.md b/docs/configuring-playbook-client-hydrogen.md
index 7e3aab465..db44e6a62 100644
--- a/docs/configuring-playbook-client-hydrogen.md
+++ b/docs/configuring-playbook-client-hydrogen.md
@@ -1,8 +1,14 @@
-# Configuring Hydrogen (optional)
+# Setting up Hydrogen (optional)
 
-This playbook can install the [Hydrogen](https://github.com/element-hq/hydrogen-web) Matrix web client for you.
+The playbook can install and configure the [Hydrogen](https://github.com/element-hq/hydrogen-web) Matrix web client for you.
 
-Hydrogen is a lightweight web client that supports mobile and legacy web browsers. It can be installed alongside or instead of Element.
+Hydrogen is a lightweight web client that supports mobile and legacy web browsers. It can be installed alongside or instead of Element Web.
+
+## Adjusting DNS records
+
+By default, this playbook installs Hydrogen on the `hydrogen.` subdomain (`hydrogen.example.com`) and requires you to create a CNAME record for `hydrogen`, which targets `matrix.example.com`.
+
+When setting, replace `example.com` with your own.
 
 ## Adjusting the playbook configuration
 
@@ -12,13 +18,11 @@ To enable Hydrogen, add the following configuration to your `inventory/host_vars
 matrix_client_hydrogen_enabled: true
 ```
 
-### Adjusting the Hydrogen URL
-
-By default, this playbook installs Hydrogen on the `hydrogen.` subdomain (`hydrogen.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records).
+### Adjusting the Hydrogen URL (optional)
 
 By tweaking the `matrix_client_hydrogen_hostname` and `matrix_client_hydrogen_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Switch to the domain used for Matrix services (`matrix.example.com`),
@@ -29,14 +33,19 @@ matrix_client_hydrogen_hostname: "{{ matrix_server_fqn_matrix }}"
 matrix_client_hydrogen_path_prefix: /hydrogen
 ```
 
-## Adjusting DNS records
-
-Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Hydrogen domain to the Matrix server.
-
-By default, you will need to create a CNAME record for `hydrogen`. See [Configuring DNS](configuring-dns.md) for details about DNS changes.
+After changing the domain, **you may need to adjust your DNS** records to point the Hydrogen domain to the Matrix server.
 
 If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
diff --git a/docs/configuring-playbook-client-schildichat-web.md b/docs/configuring-playbook-client-schildichat-web.md
new file mode 100644
index 000000000..e9781255a
--- /dev/null
+++ b/docs/configuring-playbook-client-schildichat-web.md
@@ -0,0 +1,111 @@
+# Setting up SchildiChat Web (optional)
+
+The playbook can install and configure the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) Matrix client for you.
+
+SchildiChat Web is a feature-rich messenger for Matrix based on Element Web with some extras and tweaks. It can be installed alongside or instead of Element Web.
+
+💡 **Note**: the latest version of SchildiChat Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Application, you can consider using it from there:
+
+- [app.schildi.chat](https://app.schildi.chat/), hosted by the [SchildiChat](https://schildi.chat/) developers
+
+## Adjusting DNS records
+
+By default, this playbook installs SchildiChat Web on the `schildichat.` subdomain (`schildichat.example.com`) and requires you to create a CNAME record for `schildichat`, which targets `matrix.example.com`.
+
+When setting, replace `example.com` with your own.
+
+## Adjusting the playbook configuration
+
+To enable SchildiChat Web, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+
+```yaml
+matrix_client_schildichat_enabled: true
+```
+
+### Themes
+
+You can change the look of SchildiChat Web by pulling themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project or defining your own themes manually.
+
+#### Use themes by `element-themes`
+
+To pull the themes from the `element-themes` project and use them for your SchildiChat Web instance, add the following configuration to your `vars.yml` file:
+
+```yaml
+matrix_client_schildichat_themes_enabled: true
+```
+
+If the variable is set to `true`, all themes found in the repository specified with `matrix_client_schildichat_themes_repository_url` will be installed and enabled automatically.
+
+Note that for a custom theme to work well, all SchildiChat Web instances that you use must have the same theme installed.
+
+#### Define themes manually
+
+You can also define your own themes manually by adding and adjusting the following configuration to your `vars.yml` file:
+
+```yaml
+# Controls the `setting_defaults.custom_themes` setting of the SchildiChat Web configuration.
+matrix_client_schildichat_setting_defaults_custom_themes: []
+```
+
+If you define your own themes with it and set `matrix_client_schildichat_themes_enabled` to `true` for the themes by `element-themes`, your themes will be preserved as well.
+
+If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it.
+
+### Adjusting the SchildiChat Web URL (optional)
+
+By tweaking the `matrix_client_schildichat_hostname` and `matrix_client_schildichat_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
+
+Example additional configuration for your `vars.yml` file:
+
+```yaml
+# Switch to the domain used for Matrix services (`matrix.example.com`),
+# so we won't need to add additional DNS records for SchildiChat Web.
+matrix_client_schildichat_hostname: "{{ matrix_server_fqn_matrix }}"
+
+# Expose under the /schildichat subpath
+matrix_client_schildichat_path_prefix: /schildichat
+```
+
+After changing the domain, **you may need to adjust your DNS** records to point the SchildiChat Web domain to the Matrix server.
+
+If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration.
+
+### Extending the configuration
+
+There are some additional things you may wish to configure about the component.
+
+Take a look at:
+
+- `roles/custom/matrix-client-schildichat/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+- `roles/custom/matrix-client-schildichat/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 `matrix_client_schildichat_configuration_extension_json` variable
+
+For example, to override some SchildiChat Web settings, add the following configuration to your `vars.yml` file:
+
+```yaml
+ # Your custom JSON configuration for SchildiChat Web should go to `matrix_client_schildichat_configuration_extension_json`.
+ # This configuration extends the default starting configuration (`matrix_client_schildichat_configuration_default`).
+ #
+ # You can override individual variables from the default configuration, or introduce new ones.
+ #
+ # If you need something more special, you can take full control by
+ # completely redefining `matrix_client_schildichat_configuration_default`.
+ #
+matrix_client_schildichat_configuration_extension_json: |
+ {
+ "disable_3pid_login": true,
+ "disable_login_language_selector": true
+ }
+```
+
+## Installing
+
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
diff --git a/docs/configuring-playbook-client-schildichat.md b/docs/configuring-playbook-client-schildichat.md
deleted file mode 100644
index 0cf640f6f..000000000
--- a/docs/configuring-playbook-client-schildichat.md
+++ /dev/null
@@ -1,68 +0,0 @@
-# Configuring SchildiChat (optional)
-
-This playbook can install the [SchildiChat](https://github.com/SchildiChat/schildichat-desktop) Matrix web client for you.
-
-SchildiChat is a feature-rich messenger for Matrix based on Element with some extras and tweaks. It can be installed alongside or instead of Element.
-
-**WARNING**: SchildiChat Web is based on Element-web, but its releases are lagging behind. As an example (from 2024-02-26), SchildiChat Web is 22 releases behind (it being based on element-web `v1.11.36`, while element-web is now on `v1.11.58`). Element-web frequently suffers from security issues, so running something based on an ancient Element-web release is **dangerous**. Use SchildiChat Web at your own risk!
-
-## Adjusting the playbook configuration
-
-To enable SchildiChat, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
-
-```yaml
-matrix_client_schildichat_enabled: true
-```
-
-The playbook provides some customization variables you could use to change SchildiChat's settings.
-
-Their defaults are defined in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml) and they ultimately end up in the generated `/matrix/schildichat/config.json` file (on the server). This file is generated from the [`roles/custom/matrix-client-schildichat/templates/config.json.j2`](../roles/custom/matrix-client-schildichat/templates/config.json.j2) template.
-
-**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes.
-
-Alternatively, **if there is no pre-defined variable** for a SchildiChat setting you wish to change:
-
-- you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of SchildiChat's various settings that rarely get used.
-
-- or, you can **extend and override the default configuration** ([`config.json.j2`](../roles/custom/matrix-client-schildichat/templates/config.json.j2)) by making use of the `matrix_client_schildichat_configuration_extension_json_` variable. You can find information about this in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml).
-
-- or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_schildichat_configuration_default` (or `matrix_client_schildichat_configuration`). You can find information about this in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml).
-
-### Themes
-
-To change the look of SchildiChat, you can define your own themes manually by using the `matrix_client_schildichat_setting_defaults_custom_themes` setting.
-
-Or better yet, you can automatically pull it all themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project by simply flipping a flag (`matrix_client_schildichat_themes_enabled: true`).
-
-If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it.
-
-Note that for a custom theme to work well, all SchildiChat instances that you use must have the same theme installed.
-
-### Adjusting the SchildiChat URL
-
-By default, this playbook installs SchildiChat on the `schildichat.` subdomain (`schildichat.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records).
-
-By tweaking the `matrix_client_schildichat_hostname` and `matrix_client_schildichat_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
-
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
-
-```yaml
-# Switch to the domain used for Matrix services (`matrix.example.com`),
-# so we won't need to add additional DNS records for SchildiChat.
-matrix_client_schildichat_hostname: "{{ matrix_server_fqn_matrix }}"
-
-# Expose under the /schildichat subpath
-matrix_client_schildichat_path_prefix: /schildichat
-```
-
-## Adjusting DNS records
-
-Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the SchildiChat domain to the Matrix server.
-
-By default, you will need to create a CNAME record for `schildichat`. See [Configuring DNS](configuring-dns.md) for details about DNS changes.
-
-If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration.
-
-## Installing
-
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all`
diff --git a/docs/configuring-playbook-conduit.md b/docs/configuring-playbook-conduit.md
index 3707e7fe4..81ac48ee5 100644
--- a/docs/configuring-playbook-conduit.md
+++ b/docs/configuring-playbook-conduit.md
@@ -1,42 +1,61 @@
 # Configuring Conduit (optional)
 
-By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Conduit](https://conduit.rs).
+The playbook can install and configure the [Conduit](https://conduit.rs) Matrix server for you.
 
-**Notes**:
+See the project's [documentation](https://docs.conduit.rs/) to learn what it does and why it might be useful to you.
+
+By default, the playbook installs [Synapse](https://github.com/element-hq/synapse) as it's the only full-featured Matrix server at the moment. If that's okay, you can skip this document.
+
+💡 **Note**: The playbook also supports installing a (currently) faster-moving Conduit fork called [Conduwuit](./configuring-playbook-conduwuit.md).
+
+⚠️ **Warnings**:
 
 - **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet.
 
-- **homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding
+- **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding
 
 ## Adjusting the playbook configuration
 
-To use Conduit, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+To use Conduit, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below:
 
 ```yaml
 matrix_homeserver_implementation: conduit
 ```
 
+### Extending the configuration
+
+There are some additional things you may wish to configure about the server.
+
+Take a look at:
+
+- `roles/custom/matrix-conduit/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+- `roles/custom/matrix-conduit/templates/conduit.toml.j2` for the server's default configuration
+
+If you'd like to have your own different configuration, feel free to copy and paste the original files into your inventory (e.g. in `inventory/host_vars/matrix.example.com/`) and then change the specific host's `vars.yml` file like this:
+
+```yaml
+matrix_conduit_template_conduit_config: "{{ playbook_dir }}/inventory/host_vars/matrix.example.com/conduit.toml.j2"
+```
+
 ## Creating the first user account
 
 Since it is difficult to create the first user account on Conduit (see [famedly/conduit#276](https://gitlab.com/famedly/conduit/-/issues/276) and [famedly/conduit#354](https://gitlab.com/famedly/conduit/-/merge_requests/354)) and it does not support [registering users](registering-users.md) (via the command line or via the playbook) like Synapse and Dendrite do, we recommend the following procedure:
 
 1. Add `matrix_conduit_allow_registration: true` to your `vars.yml` the first time around, temporarily
 2. Run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start` - see [Installing](installing.md))
-3. Create your first user via Element or any other client which supports creating users
+3. Create your first user via Element Web or any other client which supports creating users
 4. Get rid of `matrix_conduit_allow_registration: true` from your `vars.yml`
 5. Run the playbook again (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-conduit,start` would be enough this time)
 6. You can now use your server safely. Additional users can be created by messaging the internal Conduit bot
 
-
 ## Configuring bridges / appservices
 
-Automatic appservice setup is currently unsupported when using Conduit. After setting up the service as usual you may notice that it is unable to start.
+For other homeserver implementations (like Synapse and Dendrite), the playbook automatically registers appservices (for bridges, bots, etc.) with the homeserver.
 
-You will have to manually register appservices using the the [register-appservice](https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.md) command.
+For Conduit, you will have to manually register appservices using the the [register-appservice](https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.md) command.
 
 Find the `registration.yaml` in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`, then pass the content to Conduit:
 
-
     @conduit:example.com: register-appservice
     ```
     as_token: <token>
diff --git a/docs/configuring-playbook-conduwuit.md b/docs/configuring-playbook-conduwuit.md
new file mode 100644
index 000000000..512f4530b
--- /dev/null
+++ b/docs/configuring-playbook-conduwuit.md
@@ -0,0 +1,95 @@
+# Configuring Conduwuit (optional)
+
+The playbook can install and configure the [Conduwuit](https://conduwuit.puppyirl.gay/) Matrix server for you.
+
+See the project's [documentation](https://conduwuit.puppyirl.gay/) to learn what it does and why it might be useful to you.
+
+By default, the playbook installs [Synapse](https://github.com/element-hq/synapse) as it's the only full-featured Matrix server at the moment. If that's okay, you can skip this document.
+
+💡 **Note**: Conduwuit is a fork of [Conduit](./configuring-playbook-conduit.md), which the playbook also supports. See [Differences from upstream Conduit](https://conduwuit.puppyirl.gay/differences.html).
+
+⚠️ **Warnings**:
+
+- **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduwuit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet.
+
+- **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding
+
+## Adjusting the playbook configuration
+
+To use Conduwuit, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below:
+
+```yaml
+matrix_homeserver_implementation: conduwuit
+
+# Registering users can only happen via the API,
+# so it makes sense to enable it, at least initially.
+matrix_conduwuit_config_allow_registration: true
+
+# Generate a strong registration token to protect the registration endpoint from abuse.
+# You can create one with a command like `pwgen -s 64 1`.
+matrix_conduwuit_config_registration_token: ''
+```
+
+### Extending the configuration
+
+There are some additional things you may wish to configure about the server.
+
+Take a look at:
+
+- `roles/custom/matrix-conduwuit/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+- `roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2` for the server's default configuration
+
+There are various Ansible variables that control settings in the `conduwuit.toml` file.
+
+If a specific setting you'd like to change does not have a dedicated Ansible variable, you can either submit a PR to us to add it, or you can [override the setting using an environment variable](https://conduwuit.puppyirl.gay/configuration.html#environment-variables) using `matrix_conduwuit_environment_variables_extension`. For example:
+
+```yaml
+matrix_conduwuit_environment_variables_extension: |
+  CONDUWUIT_MAX_REQUEST_SIZE=50000000
+  CONDUWUIT_REQUEST_TIMEOUT=60
+```
+
+## Creating the first user account
+
+Unlike other homeserver implementations (like Synapse and Dendrite), Conduwuit does not support creating users via the command line or via the playbook.
+
+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.
+
+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.
+
+The **first user account that you create will be marked as an admin** and **will be automatically invited to an admin room**.
+
+
+## Configuring bridges / appservices
+
+For other homeserver implementations (like Synapse and Dendrite), the playbook automatically registers appservices (for bridges, bots, etc.) with the homeserver.
+
+For Conduwuit, you will have to manually register appservices using the [`!admin appservices register` command](https://conduwuit.puppyirl.gay/appservices.html#set-up-the-appservice---general-instructions) sent to the server bot account.
+
+The server's bot account has a Matrix ID of `@conduit:example.com` (not `@conduwuit:example.com`!) due to Conduwuit's historical legacy.
+Your first user account would already have been invited to an admin room with this bot.
+
+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`.
+
+Then, send its content to the existing admin room:
+
+    !admin appservices register
+
+    ```
+    as_token: <token>
+    de.sorunome.msc2409.push_ephemeral: true
+    hs_token: <token>
+    id: signal
+    namespaces:
+      aliases:
+      - exclusive: true
+        regex: ^#signal_.+:example\.org$
+      users:
+      - exclusive: true
+        regex: ^@signal_.+:example\.org$
+      - exclusive: true
+        regex: ^@signalbot:example\.org$
+    rate_limited: false
+    sender_localpart: _bot_signalbot
+    url: http://matrix-mautrix-signal:29328
+    ```
diff --git a/docs/configuring-playbook-dendrite.md b/docs/configuring-playbook-dendrite.md
index 0ffa8ed04..83510e7af 100644
--- a/docs/configuring-playbook-dendrite.md
+++ b/docs/configuring-playbook-dendrite.md
@@ -1,37 +1,64 @@
 # Configuring Dendrite (optional)
 
-By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Dendrite](https://github.com/matrix-org/dendrite).
+The playbook can install and configure the [Dendrite](https://github.com/element-hq/dendrite) Matrix server for you.
 
-**Notes**:
+See the project's [documentation](https://element-hq.github.io/dendrite/) to learn what it does and why it might be useful to you.
+
+By default, the playbook installs [Synapse](https://github.com/element-hq/synapse) as it's the only full-featured Matrix server at the moment. If that's okay, you can skip this document.
+
+⚠️ **Warnings**:
 
 - **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Dendrite). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet.
 
-- **homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding
+- **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding
 
 ## Adjusting the playbook configuration
 
-To use Dendrite, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+To use Dendrite, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below:
 
 ```yaml
 matrix_homeserver_implementation: dendrite
 ```
 
-The playbook provides lots of customization variables you could use to change Dendrite's settings.
+### Extending the configuration
 
-Their defaults are defined in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml) and they ultimately end up in the generated `/matrix/dendrite/config/dendrite.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2) template.
+There are some additional things you may wish to configure about the server.
 
-**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes.
+Take a look at:
 
-Alternatively, **if there is no pre-defined variable** for a Dendrite setting you wish to change:
-
-- you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Dendrite's various settings that rarely get used.
-
-- or, you can **extend and override the default configuration** ([`dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2)) by making use of the `matrix_dendrite_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml).
-
-- or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_dendrite_configuration` (or `matrix_dendrite_configuration_yaml`). You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml).
+- `roles/custom/matrix-dendrite/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+- `roles/custom/matrix-dendrite/templates/dendrite.yaml.j2` for the server's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_dendrite_configuration_extension_yaml` variable
 
+For example, to override some Dendrite settings, add the following configuration to your `vars.yml` file:
 
+```yaml
+matrix_dendrite_configuration_extension_yaml: |
+  # Your custom YAML configuration for Dendrite goes here.
+  # This configuration extends the default starting configuration (`matrix_dendrite_configuration_yaml`).
+  #
+  # You can override individual variables from the default configuration, or introduce new ones.
+  #
+  # If you need something more special, you can take full control by
+  # completely redefining `matrix_dendrite_configuration_yaml`.
+  #
+  # Example configuration extension follows:
+  #
+  server_notices:
+    system_mxid_localpart: notices
+    system_mxid_display_name: "Server Notices"
+    system_mxid_avatar_url: "mxc://example.com/oumMVlgDnLYFaPVkExemNVVZ"
+    room_name: "Server Notices"
+```
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
diff --git a/docs/configuring-playbook-dimension.md b/docs/configuring-playbook-dimension.md
index 5d5a2b6a3..7d1c0ce3f 100644
--- a/docs/configuring-playbook-dimension.md
+++ b/docs/configuring-playbook-dimension.md
@@ -1,54 +1,74 @@
-# Setting up Dimension (optional)
+# Setting up Dimension integration manager (optional, unmaintained)
 
-**[Dimension](https://dimension.t2bot.io) can only be installed after Matrix services are installed and running.** If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) flow and come back here later.
+**Notes**:
+- Dimension is **[officially unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299)**. We recommend not bothering with installing it.
+- This playbook now supports running Dimension in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`.
 
-**Note**: Dimension is **[officially unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299)**. We recommend not bothering with installing it.
+The playbook can install and configure the [Dimension](https://dimension.t2bot.io) integration manager for you.
 
-**Note**: This playbook now supports running [Dimension](https://dimension.t2bot.io) in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`. Enabling Dimension, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible).
+See the project's [documentation](https://github.com/turt2live/matrix-dimension/blob/master/README.md) to learn what it does and why it might be useful to you.
+
+## Prerequisites
+
+### Open Matrix Federation port
+
+Enabling the Dimension service will automatically reconfigure your Synapse homeserver to expose the `openid` API endpoints on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. If you enable the component, make sure that the port is accessible.
+
+### Install Matrix services
+
+Dimension can only be installed after Matrix services are installed and running. If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) and come back here later.
+
+### Register a dedicated Matrix user (optional, recommended)
+
+We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username).
+
+Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`.
+
+You can use the playbook to [register a new user](registering-users.md):
+
+```sh
+ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=dimension password=PASSWORD_FOR_THE_USER admin=no' --tags=register-user
+```
+
+### Obtain an access token
+
+Dimension requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md).
+
+⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.
+
+## Adjusting DNS records
+
+By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to create a CNAME record for `dimension`, which targets `matrix.example.com`.
+
+When setting, replace `example.com` with your own.
 
 ## Adjusting the playbook configuration
 
-To enable Dimension, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):
+To enable Dimension, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token).
 
 ```yaml
 matrix_dimension_enabled: true
+
+matrix_dimension_access_token: "ACCESS_TOKEN_HERE"
 ```
 
 ### Define admin users
 
-These users can modify the integrations this Dimension supports. Add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):
+To define admin users who can modify the integrations this Dimension supports, add the following configuration to your `vars.yml` file:
 
 ```yaml
 matrix_dimension_admins:
-  - "@user1:{{ matrix_domain }}"
-  - "@user2:{{ matrix_domain }}"
+  - "@alice:{{ matrix_domain }}"
+  - "@bob:{{ matrix_domain }}"
 ```
 
-The admin interface is accessible within Element by accessing it in any room and clicking the cog wheel/settings icon in the top right. Currently, Dimension can be opened in Element by the "Add widgets, bridges, & bots" link in the room information.
+The admin interface is accessible within Element Web by accessing it in any room and clicking the cog wheel/settings icon in the top right. Currently, Dimension can be opened in Element Web by the "Add widgets, bridges, & bots" link in the room information.
 
-### Access token
-
-We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username). Follow our [Registering users](registering-users.md) guide to learn how to register **a regular (non-admin) user**.
-
-You are required to specify an access token (belonging to this new user) for Dimension to work. To get an access token for the Dimension user, you can follow the documentation on [how to do obtain an access token](obtaining-access-tokens.md).
-
-**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**
-
-Add access token to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):
-
-```yaml
-matrix_dimension_access_token: "YOUR ACCESS TOKEN HERE"
-```
-
-For more information on how to acquire an access token, visit [https://t2bot.io/docs/access_tokens](https://t2bot.io/docs/access_tokens).
-
-### Adjusting the Dimension URL
-
-By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records).
+### Adjusting the Dimension URL (optional)
 
 By tweaking the `matrix_dimension_hostname` and `matrix_dimension_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Switch to the domain used for Matrix services (`matrix.example.com`),
@@ -59,31 +79,34 @@ matrix_dimension_hostname: "{{ matrix_server_fqn_matrix }}"
 # matrix_dimension_path_prefix: /dimension
 ```
 
-**Note**: While there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You must serve Dimension at a dedicated subdomain.
+After changing the domain, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server.
 
-## Adjusting DNS records
+If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration.
 
-Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server.
-
-By default, you will need to create a CNAME record for `dimension`. See [Configuring DNS](configuring-dns.md) for details about DNS changes.
+**Note**: while there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You'd need to serve Dimension at a dedicated subdomain.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command:
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
 
-```
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
 ```
 
-After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots.
+**Notes**:
 
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
+
+- After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots.
 
 ## Jitsi domain
 
 By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](./configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance. Currently there is no way to configure this via the playbook, see [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details.
 
-In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element, go to *Manage Integrations* &rightarrow; *Settings* &rightarrow; *Widgets* &rightarrow; *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately.
-
+In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element Web, go to *Manage Integrations* &rightarrow; *Settings* &rightarrow; *Widgets* &rightarrow; *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately.
 
 ## Additional features
 
diff --git a/docs/configuring-playbook-dynamic-dns.md b/docs/configuring-playbook-dynamic-dns.md
index 4bae5ea83..7108e8b65 100644
--- a/docs/configuring-playbook-dynamic-dns.md
+++ b/docs/configuring-playbook-dynamic-dns.md
@@ -1,24 +1,40 @@
-# Dynamic DNS
+# Setting up Dynamic DNS (optional)
 
-## Setup
+The playbook can configure Dynamic DNS with [ddclient⁠](https://github.com/ddclient/ddclient) for you. It is a Perl client used to update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider.
 
 Most cloud providers / ISPs will charge you extra for a static IP address. If you're not hosting a highly reliable homeserver you can workaround this via dynamic DNS.
 
-To set this up, you'll need to get the username/password from your DNS provider. For google domains, this process is described [here](https://support.google.com/domains/answer/6147083).
+## Prerequisite
 
-After you've gotten the proper credentials you can add the following config to your `inventory/host_vars/matrix.example.com/vars.yml`:
+You'll need to get a username and password from your DNS provider. Please consult with the provider about how to retrieve them.
+
+## Adjusting the playbook configuration
+
+To enable dynamic DNS, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
 ```yaml
 matrix_dynamic_dns_enabled: true
 
 matrix_dynamic_dns_domain_configurations:
-  - provider: domains.google.com
+  - provider: example.net
     protocol: dyndn2
-    username: XXXXXXXXXXXXXXXX
-    password: XXXXXXXXXXXXXXXX
+    username: YOUR_USERNAME_HERE
+    password: YOUR_PASSWORD_HERE
     domain: "{{ matrix_domain }}"
 ```
 
+## Installing
+
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
 
 ## Additional Reading
 
diff --git a/docs/configuring-playbook-email.md b/docs/configuring-playbook-email.md
index e8e80415a..b10dd8224 100644
--- a/docs/configuring-playbook-email.md
+++ b/docs/configuring-playbook-email.md
@@ -6,16 +6,14 @@ The email server would attempt to deliver emails directly to their final destina
 
 By default, emails are sent from `matrix@matrix.example.com`, as specified by the `exim_relay_sender_address` playbook variable.
 
-⚠ **Warning**: On some cloud providers (Google Cloud, etc.), [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible. You will need to [relay email through another SMTP server](#relaying-email-through-another-smtp-server).
+⚠️ **Warning**: On some cloud providers (Google Cloud, etc.), [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible. You will need to [relay email through another SMTP server](#relaying-email-through-another-smtp-server).
 
 💡 To improve deliverability, we recommend [relaying email through another SMTP server](#relaying-email-through-another-smtp-server) anyway.
 
-
 ## Firewall settings
 
 No matter whether you send email directly (the default) or you relay email through another host (see how below), you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration).
 
-
 ## Relaying email through another SMTP server
 
 If you'd like to relay email through another SMTP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):
@@ -32,8 +30,8 @@ exim_relay_relay_auth_password: "some-password"
 
 **Note**: only the secure submission protocol (using `STARTTLS`, usually on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port `465`) **is not supported**.
 
-
 ### Configuations for sending emails using Sendgrid
+
 An easy and free SMTP service to set up is [Sendgrid](https://sendgrid.com/), the free tier allows for up to 100 emails per day to be sent. In the settings below you can provide any email for `exim_relay_sender_address`.
 
 The only other thing you need to change is the `exim_relay_relay_auth_password`, which you can generate at https://app.sendgrid.com/settings/api_keys. The API key password looks something like `SG.955oW1mLSfwds7i9Yd6IA5Q.q8GTaB8q9kGDzasegdG6u95fQ-6zkdwrPP8bOeuI`.
diff --git a/docs/configuring-playbook-email2matrix.md b/docs/configuring-playbook-email2matrix.md
index fa56b8c82..d703d5417 100644
--- a/docs/configuring-playbook-email2matrix.md
+++ b/docs/configuring-playbook-email2matrix.md
@@ -1,18 +1,13 @@
 # Setting up Email2Matrix (optional)
 
-**Note**: email bridging can also happen via the [Postmoogle](configuring-playbook-bot-postmoogle.md) bot supported by the playbook. Postmoogle is much more powerful and easier to use, so we recommend that you use it, instead of Email2Matrix.
+**Note**: email bridging can also happen via the [Postmoogle](configuring-playbook-bridge-postmoogle.md) bridge supported by the playbook. Postmoogle is much more powerful and easier to use, so we recommend that you use it, instead of Email2Matrix.
 
 The playbook can install and configure [email2matrix](https://github.com/devture/email2matrix) for you.
 
 See the project's [documentation](https://github.com/devture/email2matrix/blob/master/docs/README.md) to learn what it does and why it might be useful to you.
 
-
 ## Preparation
 
-### DNS configuration
-
-It's not strictly necessary, but you may increase the chances that incoming emails reach your server by adding an `MX` record for `matrix.example.com`, as described in the [Configuring DNS](configuring-dns.md) documentation page.
-
 ### Port availability
 
 Ensure that port 25 is available on your Matrix server and open in your firewall.
@@ -23,37 +18,60 @@ If you really need to run an email server on the Matrix machine for other purpos
 
 For details about using Email2Matrix alongside [Postfix](http://www.postfix.org/), see [here](https://github.com/devture/email2matrix/blob/master/docs/setup_with_postfix.md).
 
-### Creating a user
+### Register a dedicated Matrix user (optional, recommended)
 
-Before enabling Email2Matrix, you'd most likely wish to create a dedicated user (or more) that would be sending messages on the Matrix side. Refer to [Registering users](registering-users.md) for ways to do that. A regular (non-admin) user works best.
+We recommend that you create a dedicated Matrix user for Email2Matrix.
 
-### Creating a shared room
+Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`.
 
-After creating a sender user, you should create one or more Matrix rooms that you share with that user. It doesn't matter who creates and owns the rooms and who joins later (you or the sender user).
+You can use the playbook to [register a new user](registering-users.md):
 
-What matters is that both you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there.
+```sh
+ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=email2matrix password=PASSWORD_FOR_THE_USER admin=no' --tags=register-user
+```
 
-Inviting additional people to the room is okay too.
+Take note of the user's ID as it needs to be specified as `MatrixUserId` on your `inventory/host_vars/matrix.example.com/vars.yml` file later.
+
+### Obtain an access token
+
+Email2Matrix requires an access token for the sender user to be able to send messages to the room. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md).
+
+⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.
+
+### Join to rooms as the sender user manually
+
+ℹ️ **Email2Matrix does not accept room invitations automatically**. To deliver messages to rooms, the sender user must be joined to all rooms manually.
+
+For each new room you would like the user to deliver messages to, invite the user to the room.
+
+Then, log in as the sender user using any Matrix client of your choosing, accept the room invitation from the user's account.
+
+Make sure that you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there, then log out.
 
 Take note of each room's room ID (different clients show the room ID in a different place). You'll need the room ID when [configuring the playbook](#adjusting-the-playbook-configuration) below.
 
-### Obtaining an access token for the sender user
+## Adjusting DNS records
 
-In order for the sender user created above to be able to send messages to the room, we'll need to obtain an access token for it. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md).
+To increase the chances that incoming emails reach your server, you can set up a `MX` record for `matrix.example.com` that looks like this:
+
+| Type | Host     | Priority | Weight | Port | Target                             |
+|------|----------|----------|--------|------|------------------------------------|
+| MX   | `matrix` | 10       | 0      | -    | `matrix.example.com`               |
 
 ## Adjusting the playbook configuration
 
-After doing the preparation steps above, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):
+To enable Email2Matrix, add the following configuration to your `vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE` and `ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE` with the ones created [above](#obtain-an-access-token).
 
 ```yaml
 matrix_email2matrix_enabled: true
 
+# You need at least 1 mailbox.
 matrix_email2matrix_matrix_mappings:
   - MailboxName: "mailbox1"
     MatrixRoomId: "!qporfwt:{{ matrix_domain }}"
     MatrixHomeserverUrl: "{{ matrix_homeserver_url }}"
-    MatrixUserId: "@email2matrix:{{ matrix_domain }}"
-    MatrixAccessToken: "MATRIX_ACCESS_TOKEN_HERE"
+    MatrixUserId: "@email2matrix1:{{ matrix_domain }}"
+    MatrixAccessToken: "ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE"
     IgnoreSubject: false
     IgnoreBody: false
     SkipMarkdown: false
@@ -61,8 +79,8 @@ matrix_email2matrix_matrix_mappings:
   - MailboxName: "mailbox2"
     MatrixRoomId: "!aaabaa:{{ matrix_domain }}"
     MatrixHomeserverUrl: "{{ matrix_homeserver_url }}"
-    MatrixUserId: "@email2matrix:{{ matrix_domain }}"
-    MatrixAccessToken: "MATRIX_ACCESS_TOKEN_HERE"
+    MatrixUserId: "@email2matrix2:{{ matrix_domain }}"
+    MatrixAccessToken: "ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE"
     IgnoreSubject: true
     IgnoreBody: false
     SkipMarkdown: true
@@ -73,7 +91,7 @@ where:
 * MailboxName - local-part of the email address, through which emails are bridged to the room whose ID is defined with MatrixRoomId
 * MatrixRoomId - internal ID of the room, to which received emails are sent as Matrix message
 * MatrixHomeserverUrl - URL of your Matrix homeserver, through which to send Matrix messages. You can also set `MatrixHomeserverUrl` to the container URL where your homeserver's Client-Server API lives by using the `{{ matrix_addons_homeserver_client_api_url }}` variable
-* MatrixUserId - the full ID of the sender user which sends bridged messages to the room
+* MatrixUserId - the full ID of the sender user which sends bridged messages to the room. On this configuration it is `@email2matrix1:example.com` and `@email2matrix2:example.com` (where `example.com` is your base domain, not the `matrix.` domain)
 * MatrixAccessToken - sender user's access token
 * IgnoreSubject - if set to "true", the subject is not bridged to Matrix
 * IgnoreBody - if set to "true", the message body is not bridged to Matrix
@@ -83,6 +101,17 @@ Refer to the official documentation [here](https://github.com/devture/email2matr
 
 ## Installing
 
-To enable Email2Matrix, run the [installation](installing.md) command (`--tags=setup-email2matrix,start`).
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected.
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+**Notes**:
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-service email2matrix` or `just setup-all`
+
+  `just install-service email2matrix` is useful for maintaining your setup quickly 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 `just setup-all` runs the `ensure-matrix-users-created` tag too.
+
+- After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected.
diff --git a/docs/configuring-playbook-etherpad.md b/docs/configuring-playbook-etherpad.md
index ea758afec..65f11b9b4 100644
--- a/docs/configuring-playbook-etherpad.md
+++ b/docs/configuring-playbook-etherpad.md
@@ -1,9 +1,17 @@
 # Setting up Etherpad (optional)
 
-[Etherpad](https://etherpad.org) is an open source collaborative text editor that can be embedded in a Matrix chat room using the [Dimension integration manager](https://dimension.t2bot.io) or used as standalone web app.
+The playbook can install and configure [Etherpad](https://etherpad.org) for you.
+
+Etherpad is an open source collaborative text editor. 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.
 
 When enabled together with the Jitsi audio/video conferencing system (see [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made available as an option during the conferences.
 
+## Adjusting DNS records
+
+By default, this playbook installs Etherpad on the `etherpad.` subdomain (`etherpad.example.com`) and requires you to create a CNAME record for `etherpad`, which targets `matrix.example.com`.
+
+When setting, replace `example.com` with your own.
+
 ## Adjusting the playbook configuration
 
 To enable Etherpad, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
@@ -16,13 +24,11 @@ etherpad_enabled: true
 # etherpad_admin_password: YOUR_PASSWORD_HERE
 ```
 
-### Adjusting the Etherpad URL
-
-By default, this playbook installs Etherpad on the `etherpad.` subdomain (`etherpad.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records).
+### Adjusting the Etherpad URL (optional)
 
 By tweaking the `etherpad_hostname` and `etherpad_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Switch to the domain used for Matrix services (`matrix.example.com`),
@@ -33,56 +39,69 @@ etherpad_hostname: "{{ matrix_server_fqn_matrix }}"
 etherpad_path_prefix: /etherpad
 ```
 
-
-## Adjusting DNS records
-
-Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Etherpad domain to the Matrix server.
-
-By default, you will need to create a CNAME record for `etherpad`. See [Configuring DNS](configuring-dns.md) for details about DNS changes.
+After changing the domain, **you may need to adjust your DNS** records to point the Etherpad domain to the Matrix server.
 
 If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration.
 
+### Configure the default text (optional)
+
+You can also edit the default text on a new pad with the variable `etherpad_default_pad_text`.
+
+To do so, add the following configuration to your `vars.yml` file (adapt to your needs):
+
+```yaml
+# Note: the whole text (all of its belonging lines) under the variable needs to be indented with 2 spaces.
+etherpad_default_pad_text: |
+  Welcome to Etherpad!
+
+  This pad text is synchronized as you type, so that everyone viewing this page sees the same text. This allows you to collaborate seamlessly on documents!
+
+  Get involved with Etherpad at https://etherpad.org
+```
+
+### Extending the configuration
+
+There are some additional things you may wish to configure about the component.
+
+Take a look at:
+
+- [etherpad role](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad/blob/main/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 `etherpad_configuration_extension_json` variable
+
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the Etherpad admin user (`etherpad_admin_username`).
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
+
+- If you change the Etherpad admin user's password (`etherpad_admin_password` in your `vars.yml` file) subsequently, the admin user's credentials on the homeserver won't be updated automatically. If you'd like to change the admin user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `etherpad_admin_password` to let the admin user know its new password.
 
 ## Usage
 
 The Etherpad UI should be available at `https://etherpad.example.com`, while the admin UI (if enabled) should then be available at `https://etherpad.example.com/admin`.
 
-If you've [decided on another hostname or path-prefix](#decide-on-a-domain-and-path) (e.g. `https://matrix.example.com/etherpad`), adjust these URLs accordingly before usage.
-
+If you've [decided on another hostname or path-prefix](#adjusting-the-etherpad-url-optional) (e.g. `https://matrix.example.com/etherpad`), adjust these URLs accordingly before using it.
 
 ### Managing / Deleting old pads
 
-If you want to manage and remove old unused pads from Etherpad, you will first need to able Admin access as described above.
+If you want to manage and remove old unused pads from Etherpad, you will first need to create the Etherpad admin user as described above.
 
-Then from the plugin manager page (`https://etherpad.example.com/admin/plugins`, install the `adminpads2` plugin. Once installed, you should have a "Manage pads" section in the Admin web-UI.
+After logging in to the admin web UI, go to the plugin manager page, and install the `adminpads2` plugin.
 
+Once the plugin is installed, you should have a "Manage pads" section in the UI.
 
-### How to use Etherpad widgets without an integration manager (like Dimension)
+### Integrating a Etherpad widget in a room
 
-This is how it works in Element, it might work quite similar with other clients:
+**Note**: this is how it works in Element Web. It might work quite similar with other clients:
 
 To integrate a standalone Etherpad in a room, create your pad by visiting `https://etherpad.example.com`. When the pad opens, copy the URL and send a command like this to the room: `/addwidget URL`. You will then find your integrated Etherpad within the right sidebar in the `Widgets` section.
-
-
-### Set Dimension default to the self-hosted Etherpad (optional)
-
-If you decided to install [Dimension integration manager](configuring-playbook-dimension.md) alongside Etherpad, the Dimension administrator users can configure the default URL template.
-
-The Dimension configuration menu can be accessed with the sprocket icon as you begin to add a widget to a room in Element. There you will find the Etherpad Widget Configuration action beneath the _Widgets_ tab.
-
-
-#### Removing the integrated Etherpad chat
-
-If you wish to disable the Etherpad chat button, you can do it by appending `?showChat=false` to the end of the pad URL, or the template.
-
-Example: `https://etherpad.example.com/p/$roomId_$padName?showChat=false`
-
-
-## Known issues
-
-If your Etherpad widget fails to load, this might be due to Dimension generating a Pad name so long, the Etherpad app rejects it.
-
-`$roomId_$padName` can end up being longer than 50 characters. You can avoid having this problem by altering the template so it only contains the three word random identifier `$padName`.
diff --git a/docs/configuring-playbook-federation.md b/docs/configuring-playbook-federation.md
index 926d694f1..87e573830 100644
--- a/docs/configuring-playbook-federation.md
+++ b/docs/configuring-playbook-federation.md
@@ -2,6 +2,7 @@
 
 By default, your server federates with the whole Matrix network. That is, people on your server can communicate with people on any other Matrix server.
 
+**Note**: in the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com` and set up [server delegation](howto-server-delegation.md) / redirection. Without a proper configuration, your server will effectively not be part of the Matrix network. If you find your server is not federated, make sure to [check whether services work](maintenance-checking-services.md) and your server is properly delegated.
 
 ## Federating only with select servers
 
@@ -15,21 +16,19 @@ matrix_synapse_federation_domain_whitelist:
 
 If you wish to disable federation, you can do that with an empty list (`[]`), or better yet by completely disabling federation (see below).
 
-
 ## Exposing the room directory over federation
 
 By default, your server's public rooms directory is not exposed to other servers via federation.
 
-If you wish to expose it, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):
+To expose it, add the following configuration to your `vars.yml` file:
 
 ```yaml
 matrix_synapse_allow_public_rooms_over_federation: true
 ```
 
-
 ## Disabling federation
 
-To completely disable federation, isolating your server from the rest of the Matrix network, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):
+To completely disable federation, isolating your server from the rest of the Matrix network, add the following configuration to your `vars.yml` file:
 
 ```yaml
 matrix_homeserver_federation_enabled: false
@@ -53,10 +52,9 @@ matrix_synapse_reverse_proxy_companion_federation_api_enabled: false
 
 Why? This change could be useful for people running small Synapse instances on small severs/VPSes to avoid being impacted by a simple DOS/DDOS when bandwidth, RAM, an CPU resources are limited and if your hosting provider does not provide a DOS/DDOS protection.
 
+To make it possible to proxy the federation through a CDN such as CloudFlare or any other, add the following configuration to your `vars.yml` file:
 
-The following changes in the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) will allow this and make it possible to proxy the federation through a CDN such as CloudFlare or any other:
-
-```
+```yaml
 matrix_synapse_http_listener_resource_names: ["client","federation"]
 # Any port can be used but in this case we use 443
 matrix_federation_public_port: 443
diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md
index 3f71a0f1c..a6b3cc28f 100644
--- a/docs/configuring-playbook-jitsi.md
+++ b/docs/configuring-playbook-jitsi.md
@@ -1,19 +1,25 @@
-# Jitsi
+# Setting up the Jitsi video-conferencing platform (optional)
 
-The playbook can install the [Jitsi](https://jitsi.org/) video-conferencing platform and integrate it with [Element](configuring-playbook-client-element.md).
+The playbook can install and configure the [Jitsi](https://jitsi.org/) video-conferencing platform for you.
 
-Jitsi installation is **not enabled by default**, because it's not a core component of Matrix services.
+Jitsi 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.
 
-The setup done by the playbook is very similar to [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the documentation there for many of the options here.
+See the project's [documentation](https://jitsi.github.io/handbook/) to learn what it does and why it might be useful to you.
 
+**Note**: the configuration by the playbook is similar to the one by [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the official documentation for Docker deployment [here](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/).
 
 ## Prerequisites
 
 You may need to open the following ports to your server:
 
 - `4443/tcp` - RTP media fallback over TCP
-- `10000/udp` - RTP media over UDP. Depending on your firewall/NAT setup, incoming RTP packets on port `10000` may have the external IP of your firewall as destination address, due to the usage of STUN in JVB (see [`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/defaults/main.yml)).
+- `10000/udp` - RTP media over UDP. Depending on your firewall/NAT configuration, incoming RTP packets on port `10000` may have the external IP of your firewall as destination address, due to the usage of STUN in JVB (see [`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/defaults/main.yml)).
 
+## Adjusting DNS records
+
+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`.
+
+When setting, replace `example.com` with your own.
 
 ## Adjusting the playbook configuration
 
@@ -23,64 +29,54 @@ To enable Jitsi, add the following configuration to your `inventory/host_vars/ma
 jitsi_enabled: true
 ```
 
-### Adjusting the Jitsi URL
-
-By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records).
+### Adjusting the Jitsi URL (optional)
 
 By tweaking the `jitsi_hostname` variable, you can easily make the service available at a **different hostname** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Change the default hostname
 jitsi_hostname: call.example.com
 ```
 
-## Adjusting DNS records
+After changing the domain, **you may need to adjust your DNS** records to point the Jitsi domain to the Matrix server.
 
-Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Jitsi domain to the Matrix server.
+### Configure Jitsi authentication and guests mode (optional)
 
-By default, you will need to create a CNAME record for `jitsi`. See [Configuring DNS](configuring-dns.md) for details about DNS changes.
+By default the Jitsi instance does not require for anyone to log in, and is open to use without an account. To control who is allowed to start meetings on your Jitsi instance, you'd need to enable Jitsi's authentication and optionally guests mode.
 
-## (Optional) Configure Jitsi authentication and guests mode
+Authentication type must be one of them: `internal` (default), `jwt`, `matrix` or `ldap`. Currently, only `internal`, `matrix` and `ldap` mechanisms are supported by the [Jitsi role](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi).
 
-By default the Jitsi Meet instance does not require any kind of login and is open to use for anyone without registration.
+With authentication enabled, all meetings have to be started by a registered user. After the meeting is started by that user, then guests are free to join. If the registered user is not yet present, the guests are put on hold in individual waiting rooms.
 
-If you're fine with such an open Jitsi instance, please skip to [Apply changes](#apply-changes).
+**Note**: authentication is not tested by the playbook's self-checks. We therefore recommend that you would make sure by yourself that authentication is configured properly. To test it, start a meeting at `jitsi.example.com` on your browser.
 
-If you would like to control who is allowed to open meetings on your new Jitsi instance, then please follow the following steps to enable Jitsi's authentication and optionally guests mode.
+#### Authenticate using Jitsi accounts: Auth-Type `internal` (recommended)
 
-Currently, there are three supported authentication modes: 'internal' (default), 'matrix' and 'ldap'.
+The default authentication mechanism is `internal` auth, which requires a Jitsi account to have been configured. This is a recommended method, as it also works in federated rooms.
 
-**Note**: Authentication is not tested via the playbook's self-checks. We therefore recommend that you manually verify if authentication is required by jitsi. For this, try to manually create a conference on jitsi.example.com in your browser.
-
-### Authenticate using Jitsi accounts (Auth-Type 'internal')
-
-The default authentication mechanism is 'internal' auth, which requires jitsi-accounts to be setup and is the recommended setup, as it also works in federated rooms. With authentication enabled, all meeting rooms have to be opened by a registered user, after which guests are free to join. If a registered host is not yet present, guests are put on hold in individual waiting rooms.
-
-Add these lines to your `inventory/host_vars/matrix.example.com/vars.yml` configuration:
+To enable authentication with a Jitsi account, add the following configuration to your `vars.yml` file. Make sure to replace `USERNAME_…` and `PASSWORD_…` with your own values.
 
 ```yaml
 jitsi_enable_auth: true
 jitsi_enable_guests: true
 jitsi_prosody_auth_internal_accounts:
-  - username: "jitsi-moderator"
-    password: "secret-password"
-  - username: "another-user"
-    password: "another-password"
+  - username: "USERNAME_FOR_THE_FIRST_USER_HERE"
+    password: "PASSWORD_FOR_THE_FIRST_USER_HERE"
+  - username: "USERNAME_FOR_THE_SECOND_USER_HERE"
+    password: "PASSWORD_FOR_THE_SECOND_USER_HERE"
 ```
 
-**Caution**: Accounts added here and subsequently removed will not be automatically removed from the Prosody server until user account cleaning is integrated into the playbook.
+**Note**: as Jitsi account removal function is not integrated into the playbook, these accounts will not be able to be removed from the Prosody server automatically, even if they are removed from your `vars.yml` file subsequently.
 
-**If you get an error** like this: "Error: Account creation/modification not supported.", it's likely that you had previously installed Jitsi without auth/guest support. In such a case, you should look into [Rebuilding your Jitsi installation](#rebuilding-your-jitsi-installation).
+#### Authenticate using Matrix OpenID: Auth-Type `matrix`
 
-### Authenticate using Matrix OpenID (Auth-Type 'matrix')
+⚠️ **Warning**: this breaks the Jitsi instance on federated rooms probably and does not allow sharing conference links with guests.
 
-**Attention: Probably breaks Jitsi in federated rooms and does not allow sharing conference links with guests.**
+This authentication method requires [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service), which can be installed using this [playbook](configuring-playbook-user-verification-service.md). It verifies against Matrix openID, and requires a user-verification-service to run.
 
-Using this authentication type require a [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service). By default, this playbook creates and configures a user-verification-service to run locally, see [configuring-user-verification-service](configuring-playbook-user-verification-service.md).
-
-To enable set this configuration at host level:
+To enable authentication with Matrix OpenID, add the following configuration to your `vars.yml` file:
 
 ```yaml
 jitsi_enable_auth: true
@@ -90,9 +86,9 @@ matrix_user_verification_service_enabled: true
 
 For more information see also [https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification](https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification).
 
-### Authenticate using LDAP (Auth-Type 'ldap')
+#### Authenticate using LDAP: Auth-Type `ldap`
 
-An example LDAP configuration could be:
+To enable authentication with LDAP, add the following configuration to your `vars.yml` file (adapt to your needs):
 
 ```yaml
 jitsi_enable_auth: true
@@ -114,112 +110,220 @@ jitsi_ldap_start_tls: false
 
 For more information refer to the [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation.
 
+### Configure `JVB_ADVERTISE_IPS` for running behind NAT or on a LAN environment (optional)
 
-## (Optional) Making your Jitsi server work on a LAN
+When running Jitsi in a LAN environment, or on the public Internet via NAT, the `JVB_ADVERTISE_IPS` enviornment variable should be set.
 
-By default the Jitsi Meet instance does not work with a client in LAN (Local Area Network), even if others are connected from WAN. There are no video and audio. In the case of WAN to WAN everything is ok.
+This variable allows to control which IP addresses the JVB will advertise for WebRTC media traffic. It is necessary to set it regardless of the use of a reverse proxy, since it's the IP address that will receive the media (audio / video) and not HTTP traffic, hence it's oblivious to the reverse proxy.
 
-The reason is the Jitsi VideoBridge git to LAN client the IP address of the docker image instead of the host. The [documentation](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/#running-behind-nat-or-on-a-lan-environment) of Jitsi in docker suggest to add `JVB_ADVERTISE_IPS` in enviornment variable to make it work.
+If your users are coming in over the Internet (and not over LAN), this will likely be your public IP address. If this is not set up correctly, calls will crash when more than two users join a meeting.
 
-Here is how to do it in the playbook.
-
-Add these two lines to your `inventory/host_vars/matrix.example.com/vars.yml` configuration:
+To set the variable, add the following configuration to your `vars.yml` file. Make sure to replace `LOCAL_IP_ADDRESS_OF_THE_HOST_HERE` with a proper value.
 
 ```yaml
 jitsi_jvb_container_extra_arguments:
-  - '--env "JVB_ADVERTISE_IPS=<Local IP address of the host>"'
+  - '--env "JVB_ADVERTISE_IPS=LOCAL_IP_ADDRESS_OF_THE_HOST_HERE"'
 ```
 
-## (Optional) Fine tune Jitsi
+Check [the official documentation](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/#running-behind-nat-or-on-a-lan-environment) for more details about it.
 
-Sample **additional** `inventory/host_vars/matrix.example.com/vars.yml` configuration to save up resources (explained below):
+### Set a maximum number of participants on a Jitsi conference (optional)
 
-```yaml
-jitsi_web_custom_config_extension: |
-  config.enableLayerSuspension = true;
+You can set a maximum number of participants allowed to join a Jitsi conference. By default the number is not specified.
 
-  config.disableAudioLevels = true;
-
-  // Limit the number of video feeds forwarded to each client
-  config.channelLastN = 4;
-
-jitsi_web_config_resolution_width_ideal_and_max: 480
-jitsi_web_config_resolution_height_ideal_and_max: 240
-```
-
-You may want to **suspend unused video layers** until they are requested again, to save up resources on both server and clients. Read more on this feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-feature/)
-
-You may wish to **disable audio levels** to avoid excessive refresh of the client-side page and decrease the CPU consumption involved.
-
-You may want to **limit the number of video feeds forwarded to each client**, to save up resources on both server and clients. As clients’ bandwidth and CPU may not bear the load, use this setting to avoid lag and crashes. This feature is found by default in other webconference applications such as Office 365 Teams (limit is set to 4). Read how it works [here](https://github.com/jitsi/jitsi-videobridge/blob/master/doc/last-n.md) and performance evaluation on this [study](https://jitsi.org/wp-content/uploads/2016/12/nossdav2015lastn.pdf).
-
-You may want to **limit the maximum video resolution**, to save up resources on both server and clients.
-
-## (Optional) Specify a Max number of participants on a Jitsi conference
-
-The playbook allows a user to set a max number of participants allowed to join a Jitsi conference. By default there is no limit.
-
-In order to set the max number of participants use the following **additional** configuration:
+To set it, add the following configuration to your `vars.yml` file (adapt to your needs):
 
 ```yaml
 jitsi_prosody_max_participants: 4 # example value
 ```
 
-## (Optional) Additional JVBs
+### Enable Gravatar (optional)
 
-By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)) is deployed on the same host as the Matrix server. To allow more video-conferences to happen at the same time, you may need to provision additional JVB services on other hosts.
+In the default Jisti Meet configuration, `gravatar.com` is enabled as an avatar service.
 
-There is an ansible playbook that can be run with the following tag: `ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start`
+Since the Element clients send the URL of configured Matrix avatars to the Jitsi instance, our default configuration has disabled the Gravatar service.
 
-For this role to work you will need an additional section in the ansible hosts file with the details of the JVB hosts, for example:
+To enable the Gravatar service, add the following configuration to your `vars.yml` file:
+
+```yaml
+jitsi_disable_gravatar: false
 ```
+
+⚠️ **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.
+
+### Fine tune Jitsi (optional)
+
+If you'd like to have Jitsi save up resources, add the following configuration to your `vars.yml` file (adapt to your needs):
+
+```yaml
+jitsi_web_config_resolution_width_ideal_and_max: 480
+jitsi_web_config_resolution_height_ideal_and_max: 240
+jitsi_web_custom_config_extension: |
+  config.enableLayerSuspension = true;
+
+  config.disableAudioLevels = true;
+
+  config.channelLastN = 4;
+```
+
+These configurations:
+
+- **limit the maximum video resolution**, to save up resources on both server and clients
+- **suspend unused video layers** until they are requested again, to save up resources on both server and clients. Read more on this feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-feature/).
+- **disable audio levels** to avoid excessive refresh of the client-side page and decrease the CPU consumption involved
+- **limit the number of video feeds forwarded to each client**, to save up resources on both server and clients. As clients’ bandwidth and CPU may not bear the load, use this setting to avoid lag and crashes. This feature is available by default on other webconference applications such as Office 365 Teams (the number is limited to 4). Read how it works [here](https://github.com/jitsi/jitsi-videobridge/blob/5ff195985edf46c9399dcf263cb07167f0a2c724/doc/allocation.md).
+
+### Example configurations
+
+Here is an example set of configurations for running a Jitsi instance with:
+
+- authentication using a Jitsi account (username: `US3RNAME`, password: `passw0rd`)
+- guests: allowed
+- maximum participants: 6 people
+- fine tuning with the configurations presented above
+- other miscellaneous options (see the official Jitsi documentation [here](https://jitsi.github.io/handbook/docs/dev-guide/dev-guide-configuration) and [here](https://jitsi.github.io/handbook/docs/user-guide/user-guide-advanced))
+
+```yaml
+jitsi_enabled: true
+jitsi_enable_auth: true
+jitsi_enable_guests: true
+jitsi_prosody_auth_internal_accounts:
+  - username: "US3RNAME"
+    password: "passw0rd"
+jitsi_prosody_max_participants: 6
+jitsi_web_config_resolution_width_ideal_and_max: 480
+jitsi_web_config_resolution_height_ideal_and_max: 240
+jitsi_web_custom_config_extension: |
+  config.enableLayerSuspension = true;
+  config.disableAudioLevels = true;
+  config.channelLastN = 4;
+  config.requireDisplayName = true; // force users to set a display name
+  config.startAudioOnly = true; // start the conference in audio only mode (no video is being received nor sent)
+```
+
+## Installing
+
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
+
+## Usage
+
+You can use the self-hosted Jitsi server in multiple ways:
+
+- **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.
+
+- **directly (without any Matrix integration)**. Just go to `https://jitsi.example.com`
+
+### Set up additional JVBs for more video-conferences (optional)
+
+By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)) is deployed on the same host as the Matrix server. To allow more video-conferences to happen at the same time, you'd need to provision additional JVB services on other hosts.
+
+These settings below will allow you to provision those extra JVB instances. The instances will register themselves with the Prosody service, and be available for Jicofo to route conferences too.
+
+#### Add the `jitsi_jvb_servers` section on `hosts` file
+
+For additional JVBs, you'd need to add the section titled `jitsi_jvb_servers` on the ansible `hosts` file with the details of the JVB hosts as below:
+
+```INI
 [jitsi_jvb_servers]
-<your jvb hosts> ansible_host=<ip address of the jvb host>
+jvb-2.example.com ansible_host=192.168.0.2
 ```
 
-Each JVB will require a server ID to be set so that it can be uniquely identified and this allows Jitsi to keep track of which conferences are on which JVB. The server ID is set with the variable `jitsi_jvb_server_id` which ends up as the JVB_WS_SERVER_ID environment variables in the JVB docker container. This variable can be set via the host file, a parameter to the ansible command or in the `vars.yaml` for the host which will have the additional JVB. For example:
+Make sure to replace `jvb-2.example.com` with your hostname for the JVB and `192.168.0.2` with your JVB's external IP address, respectively.
 
-``` yaml
-jitsi_jvb_server_id: 'jvb-2'
-```
+You could add JVB hosts as many as you would like. When doing so, add lines with the details of them.
 
-``` INI
-[jitsi_jvb_servers]
-jvb-2.example.com ansible_host=192.168.0.2 jitsi_jvb_server_id=jvb-2
-jvb-3.example.com ansible_host=192.168.0.3 jitsi_jvb_server_id=jvb-2
-```
+#### Prepare `vars.yml` files for additional JVBs
 
-Note that the server ID `jvb-1` is reserved for the JVB instance running on the Matrix host and therefore should not be used as the ID of an additional jvb host.
+If the main server is `matrix.example.com` and the additional JVB instance is going to be deployed at `jvb-2.example.com`, the variables for the latter need to be specified on `vars.yml` in its directory (`inventory/host_vars/jvb-2.example.com`).
 
-The additional JVB will also need to expose the colibri web socket port and this can be done with the following variable:
+Note that most (if not all) variables are common for both servers.
+
+If you are setting up multiple JVB instances, you'd need to create `vars.yml` files for each of them too (`inventory/host_vars/jvb-3.example.com/vars.yml`, for example).
+
+#### Set the server ID to each JVB
+
+Each JVB requires a server ID to be set, so that it will be uniquely identified. The server ID allows Jitsi to keep track of which conferences are on which JVB.
+
+The server ID can be set with the variable `jitsi_jvb_server_id`. It will end up as the `JVB_WS_SERVER_ID` environment variables in the JVB docker container.
+
+To set the server ID to `jvb-2`, add the following configuration to either `hosts` or `vars.yml` files (adapt to your needs).
+
+- On `hosts`:
+
+  Add `jitsi_jvb_server_id=jvb-2` after your JVB's external IP addresses as below:
+
+  ```INI
+  [jitsi_jvb_servers]
+  jvb-2.example.com ansible_host=192.168.0.2 jitsi_jvb_server_id=jvb-2
+  jvb-3.example.com ansible_host=192.168.0.3 jitsi_jvb_server_id=jvb-2
+  ```
+
+- On `vars.yml` files:
+
+  ```yaml
+  jitsi_jvb_server_id: 'jvb-2'
+  ```
+
+Alternatively, you can specify the variable as a parameter to [the ansible command](#run-the-playbook).
+
+**Note**: the server ID `jvb-1` is reserved for the JVB instance running on the Matrix host, therefore should not be used as the ID of an additional JVB host.
+
+#### Set colibri WebSocket port
+
+The additional JVBs will need to expose the colibri WebSocket port.
+
+To expose the port, add the following configuration to your `vars.yml` files:
 
 ```yaml
 jitsi_jvb_container_colibri_ws_host_bind_port: 9090
 ```
 
-The JVB will also need to know where the prosody xmpp server is located, similar to the server ID this can be set in the vars for the JVB by using the variable `jitsi_xmpp_server`. The Jitsi prosody container is deployed on the Matrix server by default so the value can be set to the Matrix domain. For example:
+#### Set Prosody XMPP server
+
+The JVB will also need to know the location of the Prosody XMPP server.
+
+Similar to the server ID (`jitsi_jvb_server_id`), this can be set with the variable for the JVB by using the variable `jitsi_xmpp_server`.
+
+##### Set the Matrix domain
+
+The Jitsi Prosody container is deployed on the Matrix server by default, so the value can be set to the Matrix domain. To set the value, add the following configuration to your `vars.yml` files:
 
 ```yaml
 jitsi_xmpp_server: "{{ matrix_domain }}"
 ```
 
-However, it can also be set the ip address of the Matrix server. This can be useful if you wish to use a private ip. For example:
+##### Set an IP address of the Matrix server
+
+Alternatively, the IP address of the Matrix server can be set. This can be useful if you would like to use a private IP address.
+
+To set the IP address of the Matrix server, add the following configuration to your `vars.yml` files:
 
 ```yaml
 jitsi_xmpp_server: "192.168.0.1"
 ```
 
-For the JVB to be able to contact the XMPP server, the latter must expose the XMPP port (5222). By default, the Matrix server does not expose the port; only the XMPP container exposes it internally inside the host, which means that the first JVB (which runs on the Matrix server) can reach it but the additional JVB cannot. The port is exposed by setting `jitsi_prosody_container_jvb_host_bind_port` like this:
+##### Expose XMPP port
+
+By default, the Matrix server does not expose the XMPP port (`5222`); only the XMPP container exposes it internally inside the host. This means that the first JVB (which runs on the Matrix server) can reach it but the additional JVBs cannot. Therefore, the XMPP server needs to expose the port, so that the additional JVBs can connect to it.
+
+To expose the port and have Docker forward the port, add the following configuration to your `vars.yml` files:
 
 ```yaml
 jitsi_prosody_container_jvb_host_bind_port: 5222
 ```
 
-(The default is empty; if it's set then docker forwards the port.)
+#### Reverse-proxy with Traefik
 
-Applied together this will allow you to provision extra JVB instances which will register themselves with the prosody service and be available for jicofo to route conferences too.
-
-To make Traefik reverse-proxy to these additional JVBs (living on other hosts), **you would need to add the following Traefik configuration extension**:
+To make Traefik reverse-proxy to these additional JVBs, add the following configuration to your main `vars.yml` file (`inventory/host_vars/matrix.example.com/vars.yml`):
 
 ```yaml
 # Traefik proxying for additional JVBs. These can't be configured using Docker
@@ -255,51 +359,31 @@ traefik_provider_configuration_extension_yaml: |
      {% endfor %}
 ```
 
-## (Optional) Enable Gravatar
+#### Run the playbook
 
-In the default Jisti Meet configuration, gravatar.com is enabled as an avatar service. This results in third party request leaking data to gravatar. Since element already sends the url of configured Matrix avatars to Jitsi, we disabled gravatar.
+After configuring `hosts` and `vars.yml` files, run the playbook with [playbook tags](playbook-tags.md) as below:
 
-To enable Gravatar set:
-
-```yaml
-jitsi_disable_gravatar: false
+```sh
+ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start
 ```
 
-**Beware**: This leaks information to a third party, namely the Gravatar-Service (unless configured otherwise: gravatar.com). Besides metadata, this includes the Matrix user_id and possibly the room identifier (via `referrer` header).
-
-## Installing
-
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command:
-
-```
-ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
-```
-
-## Usage
-
-You can use the self-hosted Jitsi server in multiple ways:
-
-- **by adding a widget to a room via Element** (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.
-
-- **by adding a widget to a room via the Dimension integration manager**. You'll have to point the widget to your own Jitsi server manually. See our [Dimension integration manager](./configuring-playbook-dimension.md) documentation page for more details. Naturally, Dimension would need to be installed first (the playbook doesn't install it by default).
-
-- **directly (without any Matrix integration)**. Just go to `https://jitsi.example.com`
-
-**Note**: Element apps on mobile devices currently [don't support joining meetings on a self-hosted Jitsi server](https://github.com/element-hq/riot-web/blob/601816862f7d84ac47547891bd53effa73d32957/docs/jitsi.md#mobile-app-support).
-
-
 ## Troubleshooting
 
+### `Error: Account creation/modification not supported`
+
+If you get an error like `Error: Account creation/modification not supported` with authentication enabled, it's likely that you had previously installed Jitsi without auth/guest support.
+
+In this case, you should consider to rebuild your Jitsi installation.
+
 ### Rebuilding your Jitsi installation
 
-**If you ever run into any trouble** or **if you change configuration (`jitsi_*` variables) too much**, we urge you to rebuild your Jitsi setup.
+If you ever run into any trouble or if you have changed configuration (`jitsi_*` variables) too much, you can rebuild your Jitsi installation.
 
-We normally don't require such manual intervention for other services, but Jitsi services generate a lot of configuration files on their own.
+We normally don't recommend manual intervention, but Jitsi services tend to generate a lot of configuration files, and it is often wise to start afresh setting the services up, rather than messing with the existing configuration files. Since not all of those files are managed by Ansible (at least not yet), you may sometimes need to delete them by yourself manually.
 
-These files are not all managed by Ansible (at least not yet), so you may sometimes need to delete them all and start fresh.
+To rebuild your Jitsi configuration, follow the procedure below:
 
-To rebuild your Jitsi configuration:
-
-- ask Ansible to stop all Jitsi services: `just run-tags stop-group --extra-vars=group=jitsi`
-- SSH into the server and do this and remove all Jitsi configuration & data (`rm -rf /matrix/jitsi`)
-- ask Ansible to set up Jitsi anew and restart services (`just install-service jitsi`)
+- run this command locally to stop all Jitsi services: `just run-tags stop-group --extra-vars=group=jitsi`
+- log in the server with SSH
+- run this command remotely to remove all Jitsi configuration & data: `rm -rf /matrix/jitsi`
+- run this command locally to set up Jitsi anew and restart services: `just install-service jitsi`
diff --git a/docs/configuring-playbook-ldap-auth.md b/docs/configuring-playbook-ldap-auth.md
index 451d386ba..d3a95d138 100644
--- a/docs/configuring-playbook-ldap-auth.md
+++ b/docs/configuring-playbook-ldap-auth.md
@@ -2,7 +2,7 @@
 
 The playbook can install and configure the [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) LDAP Auth password provider for you.
 
-See that project's documentation to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/matrix-org/matrix-synapse-ldap3/blob/main/README.rst) to learn what it does and why it might be useful to you.
 
 If you decide that you'd like to let this playbook install it for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):
 
@@ -21,7 +21,6 @@ matrix_synapse_ext_password_provider_ldap_bind_password: ""
 matrix_synapse_ext_password_provider_ldap_filter: ""
 ```
 
-
 ## Authenticating only using a password provider
 
 If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:
@@ -30,11 +29,11 @@ If you wish for users to **authenticate only against configured password provide
 matrix_synapse_password_config_localdb_enabled: false
 ```
 
+## Using ma1sd Identity Server for authentication (not recommended)
 
-## Using ma1sd Identity Server for authentication
-
-If you wish to use the ma1sd Identity Server for LDAP authentication instead of [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) consult [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md#authentication).
+The playbook can instead configure [ma1sd](https://github.com/ma1uta/ma1sd) Identity Server for LDAP authentication. However, **we recommend not bothering with installing it** as ma1sd has been unmaintained for years.
 
+If you wish to install it anyway, consult the [ma1sd Identity Server configuration](configuring-playbook-ma1sd.md#authentication).
 
 ## Handling user registration
 
diff --git a/docs/configuring-playbook-ma1sd.md b/docs/configuring-playbook-ma1sd.md
index 1f8a6f28f..c2f9d3132 100644
--- a/docs/configuring-playbook-ma1sd.md
+++ b/docs/configuring-playbook-ma1sd.md
@@ -1,14 +1,31 @@
-# Adjusting ma1sd Identity Server configuration (optional)
+# Setting up ma1sd Identity Server (optional)
 
-The playbook can configure the [ma1sd](https://github.com/ma1uta/ma1sd) Identity Server for you.
+**⚠️Note**: ma1sd itself has also been unmaintained for years (the latest commit and release being from 2021). The role of identity servers in the Matrix specification also has an uncertain future. **We recommend not bothering with installing it unless it's the only way you can do what you need to do**. For example, certain things like LDAP integration can also be implemented via [the LDAP provider module for Synapse](./configuring-playbook-ldap-auth.md).
 
-ma1sd, being an Identity Server, is not strictly needed. It is only used for 3PIDs (3rd party identifiers like E-mail and phone numbers) and some [enhanced features](https://github.com/ma1uta/ma1sd/#features).
+The playbook can configure the [ma1sd](https://github.com/ma1uta/ma1sd) Identity Server for you. It is a fork of [mxisd](https://github.com/kamax-io/mxisd) which was pronounced end of life 2019-06-21.
 
-This server is private by default, potentially at the expense of user discoverability.
+ma1sd is used for 3PIDs (3rd party identifiers like E-mail and phone numbers) and some [enhanced features](https://github.com/ma1uta/ma1sd/#features). It is private by default, potentially at the expense of user discoverability.
 
-*ma1sd is a fork of [mxisd](https://github.com/kamax-io/mxisd) which was pronounced end of life 2019-06-21.*
+See the project's [documentation](https://github.com/ma1uta/ma1sd/blob/master/README.md) to learn what it does and why it might be useful to you.
 
-**Note**: enabling ma1sd, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible).
+## Prerequisites
+
+### Open Matrix Federation port
+
+Enabling the ma1sd service will automatically reconfigure your Synapse homeserver to expose the `openid` API endpoints on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. If you enable the component, make sure that the port is accessible.
+
+## Adjusting DNS records
+
+To make the ma1sd Identity Server enable its federation features, set up a SRV record that looks like this:
+
+- Name: `_matrix-identity._tcp` (use this text as-is)
+- Content: `10 0 443 matrix.example.com` (replace `example.com` with your own)
+
+See [ma1sd's documentation](https://github.com/ma1uta/ma1sd/wiki/mxisd-and-your-privacy#choices-are-never-easy) for information on the privacy implications of setting up this SRV record.
+
+When setting up a SRV record, if you are asked for a service and protocol instead of a hostname split the host value from the table where the period is. For example use service as `_matrix-identity` and protocol as `_tcp`.
+
+**Note**: This `_matrix-identity._tcp` SRV record for the identity server is different from the `_matrix._tcp` that can be used for Synapse delegation. See [howto-server-delegation.md](howto-server-delegation.md) for more information about delegation.
 
 ## Adjusting the playbook configuration
 
@@ -24,27 +41,33 @@ To ensure maximum discovery, you can make your identity server also forward look
 
 Enabling this is discouraged and you'd better [learn more](https://github.com/ma1uta/ma1sd/blob/master/docs/features/identity.md#lookups) before proceeding.
 
-Enabling matrix.org forwarding can happen with the following configuration:
+To enable matrix.org forwarding, add the following configuration to your `vars.yml` file:
 
 ```yaml
 matrix_ma1sd_matrixorg_forwarding_enabled: true
 ```
 
-### Customizing email templates
+### Additional features
+
+What this playbook configures for your is some bare minimum Identity Server functionality, so that you won't need to rely on external 3rd party services.
+
+A few variables can be toggled in this playbook to alter the ma1sd configuration that gets generated.
+
+Still, ma1sd can do much more. You can refer to the [ma1sd website](https://github.com/ma1uta/ma1sd) for more details and configuration options.
+
+To use a more custom configuration, you can define a `matrix_ma1sd_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_ma1sd_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-ma1sd/defaults/main.yml) of the ma1sd component.
+
+#### Customizing email templates
 
 If you'd like to change the default email templates used by ma1sd, take a look at the `matrix_ma1sd_threepid_medium_email_custom_` variables (in the `roles/custom/matrix-ma1sd/defaults/main.yml` file.
 
-## Installing
-
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
-
-## ma1sd-controlled Registration
+#### ma1sd-controlled Registration
 
 To use the [Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) feature of ma1sd, you can make use of the following variables:
 
 - `matrix_synapse_enable_registration` - to enable user-initiated registration in Synapse
 
-- `matrix_synapse_enable_registration_captcha` - to validate registering users using reCAPTCHA, as described in the [enabling reCAPTCHA](configuring_captcha.md) documentation.
+- `matrix_synapse_enable_registration_captcha` - to validate registering users using reCAPTCHA, as described in the [enabling reCAPTCHA](configuring-captcha.md) documentation.
 
 - `matrix_synapse_registrations_require_3pid` - a list of 3pid types (among `'email'`, `'msisdn'`) required by the Synapse server for registering
 
@@ -54,10 +77,11 @@ To use the [Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/featu
 
 **Note**: For this to work, either the homeserver needs to [federate](configuring-playbook-federation.md) or the `openid` APIs need to exposed on the federation port. When federation is disabled and ma1sd is enabled, we automatically expose the `openid` APIs (only!) on the federation port. Make sure the federation port (usually `https://matrix.example.com:8448`) is whitelisted in your firewall (even if you don't actually use/need federation).
 
+#### Authentication
 
-## Authentication
+[Authentication](https://github.com/ma1uta/ma1sd/blob/master/docs/features/authentication.md) provides the possibility to use your own [Identity Stores](https://github.com/ma1uta/ma1sd/blob/master/docs/stores/README.md) (for example LDAP) to authenticate users on your Homeserver.
 
-[Authentication](https://github.com/ma1uta/ma1sd/blob/master/docs/features/authentication.md) provides the possibility to use your own [Identity Stores](https://github.com/ma1uta/ma1sd/blob/master/docs/stores/README.md) (for example LDAP) to authenticate users on your Homeserver. The following configuration can be used to authenticate against an LDAP server:
+To enable authentication against an LDAP server, add the following configuration to your `vars.yml` file:
 
 ```yaml
 matrix_synapse_ext_password_provider_rest_auth_enabled: true
@@ -77,17 +101,7 @@ matrix_ma1sd_configuration_extension_yaml: |
       bindPassword: TheUserPassword
 ```
 
-## Additional features
-
-What this playbook configures for your is some bare minimum Identity Server functionality, so that you won't need to rely on external 3rd party services.
-
-A few variables can be toggled in this playbook to alter the ma1sd configuration that gets generated.
-
-Still, ma1sd can do much more. You can refer to the [ma1sd website](https://github.com/ma1uta/ma1sd) for more details and configuration options.
-
-To use a more custom configuration, you can define a `matrix_ma1sd_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_ma1sd_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-ma1sd/defaults/main.yml) of the ma1sd component.
-
-## Example: SMS verification
+#### Example: SMS verification
 
 If your use case requires mobile verification, it is quite simple to integrate ma1sd with [Twilio](https://www.twilio.com/), an online telephony services gateway. Their prices are reasonable for low-volume projects and integration can be done with the following configuration:
 
@@ -103,7 +117,7 @@ matrix_ma1sd_configuration_extension_yaml: |
             number: '+<msisdn-number>'
 ```
 
-## Example: Open Registration for every Domain
+#### Example: Open Registration for every Domain
 
 If you want to open registration for any domain, you have to setup the allowed domains with ma1sd's `blacklist` and `whitelist`. The default behavior when neither the `blacklist`, nor the `whitelist` match, is to allow registration. Beware: you can't block toplevel domains (aka `.xy`) because the internal architecture of ma1sd doesn't allow that.
 
@@ -119,13 +133,26 @@ matrix_ma1sd_configuration_extension_yaml: |
             whitelist: ~
 ```
 
+## Installing
+
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
+
 ## Troubleshooting
 
 If email address validation emails sent by ma1sd are not reaching you, you should look into [Adjusting email-sending settings](configuring-playbook-email.md).
 
 If you'd like additional logging information, temporarily enable verbose logging for ma1sd.
 
-Example configuration (`inventory/host_vars/matrix.example.com/vars.yml`):
+To enable it, add the following configuration to your `vars.yml` file:
 
 ```yaml
 matrix_ma1sd_verbose_logging: true
diff --git a/docs/configuring-playbook-matrix-authentication-service.md b/docs/configuring-playbook-matrix-authentication-service.md
index d6ddf5144..616ab54cc 100644
--- a/docs/configuring-playbook-matrix-authentication-service.md
+++ b/docs/configuring-playbook-matrix-authentication-service.md
@@ -1,6 +1,6 @@
-# Matrix Authentication Service (MAS)
+# Setting up Matrix Authentication Service (optional)
 
-This playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) - a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/).
+The playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) - a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/).
 
 Matrix Authentication Service is an implementation of [MSC3861: Next-generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website.
 
@@ -10,8 +10,7 @@ Matrix Authentication Service is an implementation of [MSC3861: Next-generation
 - the [Expectations](#expectations) section below
 - the [FAQ section on areweoidcyet.com](https://areweoidcyet.com/#faqs)
 
-**If you've already been using Synapse** and have user accounts in its database, you can [migrate to Matrix Authentication Service](#migrating-an-existing-homeserver-to-matrix-authentication-service).
-
+**If you've already been using Synapse** and have user accounts in its database, you can [migrate to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service).
 
 ## Reasons to use Matrix Authentication Service
 
@@ -33,16 +32,14 @@ Below, we'll try to **highlight some potential reasons for switching** to Matrix
 
 - To reap some of the security benefits that Matrix Authentication Service offers, as outlined in the [Better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/) article.
 
-
 ## Prerequisites
 
-- ⚠ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet.
+- ⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet.
 
-- ⚠ **email sending** configured (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working.
+- ⚠️ **email sending** configured (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working.
 
 - ❌ **disabling all password providers** for Synapse (things like [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc.) More details about this are available in the [Expectations](#expectations) section below.
 
-
 ## Expectations
 
 This section details what you can expect when switching to the Matrix Authentication Service (MAS).
@@ -51,32 +48,39 @@ This section details what you can expect when switching to the Matrix Authentica
 
 - ❌ Certain **tools like [synapse-admin](./configuring-playbook-synapse-admin.md) do not have full compatibility with MAS yet**. synapse-admin already supports [login with access token](https://github.com/etkecc/synapse-admin/pull/58), browsing users (which Synapse will internally fetch from MAS) and updating user avatars. However, editing users (passwords, etc.) now needs to happen directly against MAS using the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html), which synapse-admin cannot interact with yet.
 
-- ❌ **Some services** (e.g. [Postmoogle](./configuring-playbook-bot-postmoogle.md), but possibly others - the list is yet to be determined) appear to **experience issues when authenticating via MAS**. We're still investigating what breaks and why.
+- ❌ **Some services experience issues when authenticating via MAS**:
+
+  - [Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first time around, but it consistently fails after restarting:
+
+    > cannot initialize matrix bot error="olm account is marked as shared, keys seem to have disappeared from the server"
+
+  - [matrix-reminder-bot](./configuring-playbook-bot-matrix-reminder-bot.md) fails to start (see [element-hq/matrix-authentication-service#3439](https://github.com/element-hq/matrix-authentication-service/issues/3439))
+  - Other services may be similarly affected. This list is not exhaustive.
 
 - ❌ **Encrypted appservices** do not work yet (related to [MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) and [PR 17705 for Synapse](https://github.com/element-hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will fail to start (see [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3658) for Hookshot). You can use these bridges/bots only if you **keep end-to-bridge encryption disabled** (which is the default setting).
 
-- ⚠ **You will need to have email sending configured** (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working.
+- ⚠️ **You will need to have email sending configured** (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working.
 
-- ⚠ **Migrating an existing homeserver to MAS is possible**, but requires **some playbook-assisted manual work** as described in the [Migrating an existing homeserver to Matrix Authentication Service](#migrating-an-existing-homeserver-to-matrix-authentication-service) section below. **Migration is reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break.
+- ⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break.
 
-- ⚠ Delegating user authentication to MAS causes **your Synapse server to be completely dependant on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch.
+- ⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) does not currently seem to preserve the "admin" flag for users (as found in the Synapse database). All users are imported as non-admin - see [element-hq/matrix-authentication-service#3440](https://github.com/element-hq/matrix-authentication-service/issues/3440). You may need update the Matrix Authentication Service's database manually and adjust the `can_request_admin` column in the `users` table to `true` for users that need to be administrators (e.g. `UPDATE users SET can_request_admin = true WHERE username = 'someone';`)
 
-- ⚠ If you've got [OIDC configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to migrate your OIDC configuration to MAS by adding an [Upstream OAuth2 configuration](#upstream-oauth2-configuration).
+- ⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependant on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch.
 
-- ⚠ A [compatibility layer](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) is installed - all `/_matrix/client/*/login` (etc.) requests will be routed to MAS instead of going to the homeserver. This is done both publicly (e.g. `https://matrix.example.com/_matrix/client/*/login`) and on the internal Traefik entrypoint (e.g. `https://matrix-traefik:8008/_matrix/client/*/login`) which helps addon services reach the homeserver's Client-Server API. You typically don't need to do anything to make this work, but it's good to be aware of it, especially if you have a [custom webserver setup](./configuring-playbook-own-webserver.md).
+- ⚠️ If you've got [OIDC configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to migrate your OIDC configuration to MAS by adding an [Upstream OAuth2 configuration](#upstream-oauth2-configuration).
+
+- ⚠️ A [compatibility layer](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) is installed - all `/_matrix/client/*/login` (etc.) requests will be routed to MAS instead of going to the homeserver. This is done both publicly (e.g. `https://matrix.example.com/_matrix/client/*/login`) and on the internal Traefik entrypoint (e.g. `https://matrix-traefik:8008/_matrix/client/*/login`) which helps addon services reach the homeserver's Client-Server API. You typically don't need to do anything to make this work, but it's good to be aware of it, especially if you have a [custom webserver setup](./configuring-playbook-own-webserver.md).
 
 - ✅ Your **existing login sessions will continue to work** (you won't get logged out). Migration will require a bit of manual work and minutes of downtime, but it's not too bad.
 
-- ✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), [Element-web](./configuring-playbook-client-element.md), Element X, FluffyChat) will be able to use the **new SSO-based login flow** provided by Matrix Authentication Service
+- ✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), [Element Web](./configuring-playbook-client-element-web.md), Element X, FluffyChat) will be able to use the **new SSO-based login flow** provided by Matrix Authentication Service
 
-- ✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work. Going through the old login flow does not require users to have a verified email address, as [is the case](https://github.com/element-hq/matrix-authentication-service/issues/1505) for the new SSO-based login flow.
+- ✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work. Going through the old login flow does not require users to have a verified email address, as [is the case](https://github.com/element-hq/matrix-authentication-service/issues/1505) for the new SSO-based login flow.
 
 - ✅ [Registering users](./registering-users.md) via **the playbook's `register-user` tag remains unchanged**. The playbook automatically does the right thing regardless of homeserver implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, the playbook will forward user-registration requests to MAS. Registering users via the command-line is no longer done via the `/matrix/synapse/bin/register` script, but via `/matrix/matrix-authentication-service/bin/register-user`.
 
 - ✅ Users that are prepared by the playbook (for bots, bridges, etc.) will continue to be registered automatically as expected. The playbook automatically does the right thing regardless of homeserver implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, the playbook will forward user-registration requests to MAS.
 
-
-
 ## Installation flows
 
 ### New homeserver
@@ -91,8 +95,13 @@ For existing Synapse homeservers:
 
 - when following the [Adjusting the playbook configuration](#adjusting-the-playbook-configuration) instructions, make sure to **disable the integration between Synapse and MAS** by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line as described in the [Marking an existing homeserver for migration](#marking-an-existing-homeserver-for-migration) section below.
 
-- then follow the [Migrating an existing homeserver to Matrix Authentication Service](#migrating-an-existing-homeserver-to-matrix-authentication-service) instructions to perform the installation and migration
+- then follow the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) instructions to perform the installation and migration
 
+## Adjusting DNS records (optional)
+
+By default, this playbook installs the Matrix Authentication Service on the `matrix.` subdomain, at the `/auth` path (https://matrix.example.com/auth). 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.
+
+If you wish to adjust it, see the section [below](#adjusting-the-matrix-authentication-service-url-optional) for details about DNS configuration.
 
 ## Adjusting the playbook configuration
 
@@ -114,14 +123,11 @@ In the sub-sections that follow, we'll cover some additional configuration optio
 
 There are many other configuration options available. Consult the [`defaults/main.yml` file](../roles/custom/matrix-authentication-service/defaults/main.yml) in the [matrix-authentication-service role](../roles/custom/matrix-authentication-service/) to discover them.
 
-
-### Adjusting the Matrix Authentication Service URL
-
-By default, this playbook installs the Matrix Authentication Service on the `matrix.` subdomain, at the `/auth` path (https://matrix.example.com/auth). 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.
+### Adjusting the Matrix Authentication Service URL (optional)
 
 By tweaking the `matrix_authentication_service_hostname` and `matrix_authentication_service_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Change the default hostname and path prefix
@@ -129,12 +135,15 @@ matrix_authentication_service_hostname: auth.example.com
 matrix_authentication_service_path_prefix: /
 ```
 
+If you've changed the default hostname, you may need to create a CNAME record for the Matrix Authentication Service domain (`auth.example.com`), which targets `matrix.example.com`.
+
+When setting, replace `example.com` with your own.
+
 ### Marking an existing homeserver for migration
 
 The [configuration above](#adjusting-the-playbook-configuration) instructs existing users wishing to migrate to add `matrix_authentication_service_migration_in_progress: true` to their configuration.
 
-This is done temporarily. The migration steps are described in more detail in the [Migrating an existing homeserver to Matrix Authentication Service](#migrating-an-existing-homeserver-to-matrix-authentication-service) section below.
-
+This is done temporarily. The migration steps are described in more detail in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) section below.
 
 ### Upstream OAuth2 configuration
 
@@ -145,7 +154,7 @@ The playbook exposes a `matrix_authentication_service_config_upstream_oauth2_pro
 <details>
 <summary>Click to expand the example configuration:</summary>
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 matrix_authentication_service_config_upstream_oauth2_providers:
@@ -259,28 +268,33 @@ matrix_authentication_service_config_upstream_oauth2_providers:
 
 💡 Refer to the [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers) for the most up-to-date schema and example for providers. The value shown above here may be out of date.
 
-⚠ The syntax for existing [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) is slightly different, so you will need to adjust your configuration when switching from Synapse OIDC to MAS upstream OAuth2.
+⚠️ The syntax for existing [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) is slightly different, so you will need to adjust your configuration when switching from Synapse OIDC to MAS upstream OAuth2.
 
-⚠ When [migrating an existing homeserver](#migrating-an-existing-homeserver-to-matrix-authentication-service) which contains OIDC-sourced users, you will need to [Configure upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas).
+⚠️ When [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) which contains OIDC-sourced users, you will need to:
 
-
-## Adjusting DNS records
-
-If you've changed the default hostname, **you may need to adjust your DNS** records to point the Matrix Authentication Service domain to the Matrix server.
-
-See [Configuring DNS](configuring-dns.md) for details about DNS changes.
-
-If you've decided to use the default hostname, you won't need to do any extra DNS configuration.
+- [Configure upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)
+- go through the [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) process
+- remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration
 
 ## Installing
 
-Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the [installation](installing.md) command: `just install-all`
+Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below:
 
-If you're in the process of migrating an existing Synapse homeserver to MAS, you should now follow the rest of the steps in the [Migrating an existing homeserver to Matrix Authentication Service](#migrating-an-existing-homeserver-to-matrix-authentication-service) guide.
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+**Notes**:
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
+
+- If you're in the process of migrating an existing Synapse homeserver to MAS, you should now follow the rest of the steps in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) guide.
 
 💡 After installation, you should [verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly).
 
-
 ## Migrating an existing Synapse homeserver to Matrix Authentication Service
 
 Our migration guide is loosely based on the upstream [Migrating an existing homeserver](https://element-hq.github.io/matrix-authentication-service/setup/migration.html) guide.
@@ -293,29 +307,32 @@ The installation + migration steps are like this:
 
 2. Perform the initial [installation](#installing). At this point:
 
-  - Matrix Authentication Service will be installed. Its database will be empty, so it cannot validate existing access tokens or authentication users yet.
+    - Matrix Authentication Service will be installed. Its database will be empty, so it cannot validate existing access tokens or authentication users yet.
 
-  - The homeserver will still continue to use its local database for validating existing access tokens.
+    - The homeserver will still continue to use its local database for validating existing access tokens.
 
-  - Various [compatibility layer URLs](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) are not yet installed. New login sessions will still be forwarded to the homeserver, which is capable of completing them.
+    - Various [compatibility layer URLs](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) are not yet installed. New login sessions will still be forwarded to the homeserver, which is capable of completing them.
 
-  - The `matrix-user-creator` role would be suppressed, so that it doesn't automatically attempt to create users (for bots, etc.) in the MAS database. These user accounts likely already exist in Synapse's user database and could be migrated over (via syn2mas, as per the steps below), so creating them in the MAS database would have been unnecessary and potentially problematic (conflicts during the syn2mas migration).
+    - The `matrix-user-creator` role would be suppressed, so that it doesn't automatically attempt to create users (for bots, etc.) in the MAS database. These user accounts likely already exist in Synapse's user database and could be migrated over (via syn2mas, as per the steps below), so creating them in the MAS database would have been unnecessary and potentially problematic (conflicts during the syn2mas migration).
 
 3. Consider taking a full [backup of your Postgres database](./maintenance-postgres.md#backing-up-postgresql). This is done just in case. The **syn2mas migration tool does not delete any data**, so it should be possible to revert to your previous setup by merely disabling MAS and re-running the playbook (no need to restore a Postgres backup). However, do note that as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break.
 
 4. [Migrate your data from Synapse to Matrix Authentication Service using syn2mas](#migrate-your-data-from-synapse-to-matrix-authentication-service-using-syn2mas)
 
-5. [Adjust your configuration](#adjusting-the-playbook-configuration) again, removing the `matrix_authentication_service_migration_in_progress: false` line
+5. [Adjust your configuration](#adjusting-the-playbook-configuration) again, to:
+
+  - remove the `matrix_authentication_service_migration_in_progress: false` line
+
+  - if you had been using [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration
 
 5. Perform the [installation](#installing) again. At this point:
 
-  - The homeserver will start delegating authentication to MAS.
+    - The homeserver will start delegating authentication to MAS.
 
-  - The compatibility layer URLs will be installed. New login sessions will be completed by MAS.
+    - The compatibility layer URLs will be installed. New login sessions will be completed by MAS.
 
 6. [Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)
 
-
 ### Migrate your data from Synapse to Matrix Authentication Service using syn2mas
 
 We **don't** ask you to [run the `syn2mas` migration advisor command](https://element-hq.github.io/matrix-authentication-service/setup/migration.html#run-the-migration-advisor), because it only gives you the green light if your Synapse configuration (`homeserver.yaml`) is configured in a way that's compatible with MAS (delegating authentication to MAS; disabling Synapse's password config; etc.). Until we migrate your data with the `syn2mas` tool, we intentionally avoid doing these changes to allow existing user sessions to work.
@@ -336,7 +353,7 @@ If you have existing OIDC users in your Synapse user database (which will be the
 
 If you don't do this, `syn2mas` would report errors like this one:
 
-> [FATAL] migrate - [Failed to import external id 4264b0f0-4f11-4ddd-aedb-b500e4d07c25 with oidc-keycloak for user @user:example.com: Error: Unknown upstream provider oidc-keycloak]
+> [FATAL] migrate - [Failed to import external id 4264b0f0-4f11-4ddd-aedb-b500e4d07c25 with oidc-keycloak for user @alice:example.com: Error: Unknown upstream provider oidc-keycloak]
 
 Below is an example situation and a guide for how to solve it.
 
@@ -344,10 +361,10 @@ If in `matrix_synapse_oidc_providers` your provider `idp_id` is (was) named `key
 
 The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` on the MAS side, as defined in `matrix_authentication_service_config_upstream_oauth2_providers` (see the [Upstream OAuth2 configuration](#upstream-oauth2-configuration) section above).
 
-To tell `syn2mas` how the Synapse-configured OIDC provider maps to the new MAS-configured OIDC provider, add this additional configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+To tell `syn2mas` how the Synapse-configured OIDC provider maps to the new MAS-configured OIDC provider, add this additional configuration to your `vars.yml` file:
 
-```yml
-# Adjust the mapping below to match your provider ids on the Synapse side and the MAS side.
+```yaml
+# Adjust the mapping below to match your provider IDs on the Synapse side and the MAS side.
 # Don't forget that Synapse automatically adds an `oidc-` prefix to provider ids defined in its configuration.
 matrix_authentication_service_syn2mas_process_extra_arguments:
   - "--upstreamProviderMapping oidc-keycloak:01HFVBY12TMNTYTBV8W921M5FA"
@@ -389,7 +406,6 @@ just run-tags matrix-authentication-service-syn2mas
 
 Having performed a `syn2mas` migration once, trying to do it again will report errors for users that were already migrated (e.g. "Error: Unknown upstream provider oauth-delegated").
 
-
 ## Verify that Matrix Authentication Service is installed correctly
 
 After [installation](#installing), run the `doctor` subcommand of the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) to verify that MAS is installed correctly.
@@ -424,14 +440,12 @@ This documentation page already mentions:
 
 There are other sub-commands available. Run `/matrix/matrix-authentication-service/bin/mas-cli` to get an overview.
 
-
 ## User registration
 
 After Matrix Authentication Service is [installed](#installing), users need to be managed there (unless you're managing them in an [upstream OAuth2 provider](#upstream-oauth2-configuration)).
 
 You can register users new users as described in the [Registering users](./registering-users.md) documentation (via `mas-cli manage register-user` or the Ansible playbook's `register-user` tag).
 
-
 ## Working around email deliverability issues
 
 Because Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user, you may need to work around email deliverability issues if [your email-sending configuration](./configuring-playbook-email.md) is not working.
diff --git a/docs/configuring-playbook-matrix-corporal.md b/docs/configuring-playbook-matrix-corporal.md
index bb72dbb72..6c4df4985 100644
--- a/docs/configuring-playbook-matrix-corporal.md
+++ b/docs/configuring-playbook-matrix-corporal.md
@@ -1,20 +1,21 @@
 # Setting up Matrix Corporal (optional, advanced)
 
--------------------------------------
+<hr/>
 
-**WARNING**: This is an advanced feature! It requires prior experience with Matrix and a specific need for using [Matrix Corporal](https://github.com/devture/matrix-corporal). If you're unsure whether you have such a need, you most likely don't.
+⚠️ **Warning**: This is an advanced feature! It requires prior experience with Matrix and a specific need for using [Matrix Corporal](https://github.com/devture/matrix-corporal). If you're unsure whether you have such a need, you most likely don't.
 
--------------------------------------
+<hr/>
 
 The playbook can install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you.
 
-In short, it's a sort of automation and firewalling service, which is helpful if you're instaling Matrix services in a controlled corporate environment. See that project's documentation to learn what it does and why it might be useful to you.
+In short, it's a sort of automation and firewalling service, which is helpful if you're instaling Matrix services in a controlled corporate environment.
+
+See the project's [documentation](https://github.com/devture/matrix-corporal/blob/main/README.md) to learn what it does and why it might be useful to you.
 
 If you decide that you'd like to let this playbook install it for you, you'd need to also:
 - (required) [set up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md)
 - (optional, but encouraged) [set up the REST authentication password provider module](configuring-playbook-rest-auth.md)
 
-
 ## Adjusting the playbook configuration
 
 Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):
@@ -47,7 +48,7 @@ matrix_corporal_policy_provider_config: |
     "TimeoutMilliseconds": 300
   }
 
-# If you also want to enable Matrix Corporal's HTTP API..
+# If you also want to enable Matrix Corporal's HTTP API…
 matrix_corporal_http_api_enabled: true
 matrix_corporal_http_api_auth_token: "AUTH_TOKEN_HERE"
 
@@ -116,8 +117,16 @@ To learn more about what the policy configuration, see the matrix-corporal docum
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command (`--tags=setup-all,start` or `--tags=setup-aux-files,setup-corporal,start`).
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-aux-files,setup-corporal,start` or `just setup-all`
+
+`just run-tags setup-aux-files,setup-corporal,start` is useful for maintaining your setup quickly 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 `just setup-all` runs the `ensure-matrix-users-created` tag too.
 
 ## Matrix Corporal files
 
diff --git a/docs/configuring-playbook-matrix-ldap-registration-proxy.md b/docs/configuring-playbook-matrix-ldap-registration-proxy.md
index 828dee04a..5f58ead69 100644
--- a/docs/configuring-playbook-matrix-ldap-registration-proxy.md
+++ b/docs/configuring-playbook-matrix-ldap-registration-proxy.md
@@ -34,4 +34,13 @@ matrix_ldap_registration_proxy_systemd_wanted_services_list_custom:
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
diff --git a/docs/configuring-playbook-matrix-media-repo.md b/docs/configuring-playbook-matrix-media-repo.md
index a935bcbea..4a9c31372 100644
--- a/docs/configuring-playbook-matrix-media-repo.md
+++ b/docs/configuring-playbook-matrix-media-repo.md
@@ -1,4 +1,4 @@
-# Setting up matrix-media-repo (optional)
+# Storing Matrix media files using matrix-media-repo (optional)
 
 [matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often abbreviated "MMR") is a highly customizable multi-domain media repository for Matrix. Intended for medium to large environments consisting of several homeservers, this media repo de-duplicates media (including remote media) while being fully compliant with the specification.
 
@@ -30,6 +30,7 @@ By default, the media-repo will use the local filesystem for data storage. You c
 ## Configuring the media-repo
 
 Additional common configuration options:
+
 ```yaml
 
 # The postgres database pooling options
@@ -46,7 +47,7 @@ matrix_media_repo_database_max_idle_connections: 5
 # See docs/admin.md for information on what these people can do. They must belong to one of the
 # configured homeservers above.
 # matrix_media_repo_admins: [
-#   "@your_username:example.org"
+#   "@alice:example.org"
 # ]
 
 matrix_media_repo_admins: []
@@ -87,7 +88,7 @@ matrix_media_repo_datastore_s3_opts_bucket_name: "your-media-bucket"
 
 ```
 
-Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-media-repo/defaults/main.yml)
+Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](../roles/custom/matrix-media-repo/defaults/main.yml)
 
 ## Signing Keys
 
diff --git a/docs/configuring-playbook-matrix-registration.md b/docs/configuring-playbook-matrix-registration.md
index edc529eda..fb5e04b31 100644
--- a/docs/configuring-playbook-matrix-registration.md
+++ b/docs/configuring-playbook-matrix-registration.md
@@ -1,14 +1,12 @@
 # Setting up matrix-registration (optional)
 
-The playbook can install and configure [matrix-registration](https://github.com/ZerataX/matrix-registration) for you.
+⚠️ **Warnings**:
+- This is a poorly maintained and buggy project. It's better to avoid using it.
+- This is not related to [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)
 
-**WARNING**: this is a poorly maintained and buggy project. It's better to avoid using it.
+The playbook can install and configure [matrix-registration](https://github.com/ZerataX/matrix-registration) for you. It is a simple python application to have a token based Matrix registration.
 
-**WARNING**: this is not related to [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)
-
-> matrix-registration is a simple python application to have a token based Matrix registration.
-
-Use matrix-registration to **create unique registration links**, which people can use to register on your Matrix server. It allows you to **keep your server's registration closed (private)**, but still allow certain people (these having a special link) to register a user account.
+Use matrix-registration to **create unique registration links**, which people can use to register on your Matrix server. It allows certain people (these having a special link) to register a user account, **keeping your server's registration closed (private)**.
 
 **matrix-registration** provides 2 things:
 
@@ -16,6 +14,11 @@ Use matrix-registration to **create unique registration links**, which people ca
 
 - **a user registration page**, where people can use these registration tokens. By default, exposed at `https://matrix.example.com/matrix-registration`
 
+## Adjusting DNS records (optional)
+
+By default, this playbook installs the matrix-registration on the `matrix.` subdomain, at the `/matrix-registration` path (https://matrix.example.com/matrix-registration). 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.
+
+If you wish to adjust it, see the section [below](#adjusting-the-matrix-registration-url-optional) for details about DNS configuration.
 
 ## Adjusting the playbook configuration
 
@@ -24,17 +27,15 @@ To enable matrix-registration, add the following configuration to your `inventor
 ```yaml
 matrix_registration_enabled: true
 
-# Generate a strong secret here. Consider generating it with `pwgen -s 64 1`
+# Generate a strong secret here. You can create one with a command like `pwgen -s 64 1`.
 matrix_registration_admin_secret: "ENTER_SOME_SECRET_HERE"
 ```
 
-### Adjusting the matrix-registration URL
-
-By default, this playbook installs the matrix-registration on the `matrix.` subdomain, at the `/matrix-registration` path (https://matrix.example.com/matrix-registration). 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.
+### Adjusting the matrix-registration URL (optional)
 
 By tweaking the `matrix_registration_hostname` and `matrix_registration_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Change the default hostname and path prefix
@@ -42,22 +43,22 @@ matrix_registration_hostname: registration.example.com
 matrix_registration_path_prefix: /
 ```
 
-## Adjusting DNS records
+If you've changed the default hostname, you may need to create a CNAME record for the matrix-registration domain (`registration.example.com`), which targets `matrix.example.com`.
 
-If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-registration domain to the Matrix server.
-
-See [Configuring DNS](configuring-dns.md) for details about DNS changes.
-
-If you've decided to use the default hostname, you won't need to do any extra DNS configuration.
+When setting, replace `example.com` with your own.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command:
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
 
-```
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
 ```
 
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
 
 ## Usage
 
@@ -67,12 +68,11 @@ It provides various [APIs](https://github.com/ZerataX/matrix-registration/wiki/a
 
 We make the most common APIs easy to use via the playbook (see below).
 
-
 ### Creating registration tokens
 
 To **create a new user registration token (link)**, use this command:
 
-```bash
+```sh
 ansible-playbook -i inventory/hosts setup.yml \
 --tags=generate-matrix-registration-token \
 --extra-vars="one_time=yes ex_date=2021-12-31"
@@ -82,12 +82,13 @@ The above command creates and returns a **one-time use** token, which **expires*
 
 Share the unique registration link (generated by the command above) with users to let them register on your Matrix server.
 
-
 ### Listing registration tokens
 
 To **list the existing user registration tokens**, use this command:
 
-```bash
+```sh
 ansible-playbook -i inventory/hosts setup.yml \
 --tags=list-matrix-registration-tokens
 ```
+
+The shortcut command with `just` program is also available: `just run-tags list-matrix-registration-tokens`
diff --git a/docs/configuring-playbook-mautrix-bridges.md b/docs/configuring-playbook-mautrix-bridges.md
deleted file mode 100644
index 1747b079a..000000000
--- a/docs/configuring-playbook-mautrix-bridges.md
+++ /dev/null
@@ -1,135 +0,0 @@
-# Setting up a Generic Mautrix Bridge (optional)
-
-The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, facebook, instagram, signal, hangouts, googlechat, etc.), as well as many other (non-mautrix) bridges. This is a common guide for configuring mautrix bridges.
-
-You can see each bridge's features at in the `ROADMAP.md` file in its corresponding [mautrix](https://github.com/mautrix) repository.
-
-## Adjusting the playbook configuration
-
-To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
-
-```yaml
-# Replace SERVICENAME with one of: twitter, facebook, instagram, ..
-matrix_mautrix_SERVICENAME_enabled: true
-```
-
-There are some additional things you may wish to configure about the bridge before you continue. Each bridge may have additional requirements besides `_enabled: true`. For example, the mautrix-telegram bridge (our documentation page about it is [here](configuring-playbook-bridge-mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and `matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each bridge's individual documentation page for details about enabling bridges.
-
-To **configure a user as an administrator for all bridges**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
-
-```yaml
-matrix_admin: "@YOUR_USERNAME:{{ matrix_domain }}"
-```
-
-**Alternatively** (more verbose, but allows multiple admins to be configured), you can do the same on a per-bridge basis with:
-
-```yaml
-matrix_mautrix_SERVICENAME_configuration_extension_yaml: |
-  bridge:
-    permissions:
-      '@YOUR_USERNAME:{{ matrix_domain }}': admin
-```
-
-## encryption
-
-Encryption support is off by default. If you would like to enable encryption, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
-
-**for all bridges with encryption support**:
-
-```yaml
-matrix_bridges_encryption_enabled: true
-matrix_bridges_encryption_default: true
-```
-
-**Alternatively**, for a specific bridge:
-
-```yaml
-matrix_mautrix_SERVICENAME_bridge_encryption_enabled: true
-matrix_mautrix_SERVICENAME_bridge_encryption_default: true
-```
-
-## relay mode
-
-Relay mode is off by default. If you would like to enable relay mode, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
-
-**for all bridges with relay mode support**:
-
-```yaml
-matrix_bridges_relay_enabled: true
-```
-
-**Alternatively**, for a specific bridge:
-
-```yaml
-matrix_mautrix_SERVICENAME_configuration_extension_yaml: |
-  bridge:
-    relay:
-      enabled: true
-```
-
-You can only have one `matrix_mautrix_SERVICENAME_configuration_extension_yaml` definition in `vars.yml` per bridge, so if you need multiple pieces of configuration there, just merge them like this:
-
-```yaml
-matrix_mautrix_SERVICENAME_configuration_extension_yaml: |
-  bridge:
-    permissions:
-      '@YOUR_USERNAME:{{ matrix_domain }}': admin
-    encryption:
-      allow: true
-      default: true
-```
-
-## Setting the bot's username
-
-```yaml
-matrix_mautrix_SERVICENAME_appservice_bot_username: "BOTNAME"
-```
-
-Can be used to set the username for the bridge.
-
-## Discovering additional configuration options
-
-You may wish to look at `roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-SERVICENAME/defaults/main.yml` to find other things you would like to configure.
-
-## Installing
-
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
-
-## Set up Double Puppeting
-
-To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook.
-
-The bridge will automatically perform Double Puppeting if you enable [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook by adding
-
-```yaml
-matrix_appservice_double_puppet_enabled: true
-```
-
-This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.
-
-## Controlling the logging level
-
-```yaml
-matrix_mautrix_SERVICENAME_logging_level: WARN
-```
-
-to `vars.yml` to control the logging level, where you may replace WARN with one of the following to control the verbosity of the logs generated: TRACE, DEBUG, INFO, WARN, ERROR, or FATAL.
-
-If you have issues with a service, and are requesting support, the higher levels of logging will generally be more helpful.
-
-
-## Usage
-
-You then need to start a chat with `@SERVICENAMEbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain).
-
-Send `login` to the bridge bot to get started. You can learn more here about authentication from the bridge's official documentation on Authentication: https://docs.mau.fi/bridges/python/SERVICENAME/authentication.html
-
-If you run into trouble, check the [Troubleshooting](#troubleshooting) section below.
-
-
-
-## Troubleshooting
-
-For troubleshooting information with a specific bridge, please see the playbook documentation about it (some other document in in `docs/`) and the upstream ([mautrix](https://github.com/mautrix)) bridge documentation for that specific bridge.
-
-Reporting bridge bugs should happen upstream, in the corresponding mautrix repository, not to us.
diff --git a/docs/configuring-playbook-ntfy.md b/docs/configuring-playbook-ntfy.md
index e89f20ea7..12bc7fc61 100644
--- a/docs/configuring-playbook-ntfy.md
+++ b/docs/configuring-playbook-ntfy.md
@@ -1,4 +1,4 @@
-# Setting up ntfy (optional)
+# Setting up the ntfy push notifications server (optional)
 
 The playbook can install and configure the [ntfy](https://ntfy.sh/) push notifications server for you.
 
@@ -8,6 +8,11 @@ This role is intended to support UnifiedPush notifications for use with the Matr
 
 **Note**: In contrast to push notifications using Google's FCM or Apple's APNs, the use of UnifiedPush allows each end-user to choose the push notification server that they prefer.  As a consequence, deploying this ntfy server does not by itself ensure any particular user or device or client app will use it.
 
+## Adjusting DNS records
+
+By default, this playbook installs ntfy on the `ntfy.` subdomain (`ntfy.example.com`) and requires you to create a CNAME record for `ntfy`, which targets `matrix.example.com`.
+
+When setting, replace `example.com` with your own.
 
 ## Adjusting the playbook configuration
 
@@ -25,37 +30,35 @@ ntfy_enabled: true
 #   log_level: DEBUG
 ```
 
-For a more complete list of variables that you could override, see the [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/-/blob/main/defaults/main.yml) of the ntfy Ansible role.
+For a more complete list of variables that you could override, see the [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/defaults/main.yml) of the ntfy Ansible role.
 
 For a complete list of ntfy config options that you could put in `ntfy_configuration_extension_yaml`, see the [ntfy config documentation](https://ntfy.sh/docs/config/#config-options).
 
-### Adjusting the ntfy URL
-
-By default, this playbook installs ntfy on the `ntfy.` subdomain (`ntfy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records).
+### Adjusting the ntfy URL (optional)
 
 By tweaking the `ntfy_hostname` variable, you can easily make the service available at a **different hostname** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Change the default hostname
 ntfy_hostname: push.example.com
 ```
 
-## Adjusting DNS records
-
-Once you've decided on the domain, **you may need to adjust your DNS** records to point the ntfy domain to the Matrix server.
-
-By default, you will need to create a CNAME record for `ntfy`. See [Configuring DNS](configuring-dns.md) for details about DNS changes.
+After changing the domain, **you may need to adjust your DNS** records to point the ntfy domain to the Matrix server.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command:
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
 
-```
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
 ```
 
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
 
 ## Usage
 
@@ -102,17 +105,16 @@ ntfy also has a web app to subscribe to and push to topics from the browser. Thi
 
 The web app is disabled in this playbook by default as the expectation is that most users won't use it. You can either use the [official hosted one](https://ntfy.sh/app) (it supports using other public reachable ntfy instances) or host it yourself by setting `ntfy_web_root: "app"` and re-running Ansible.
 
-
 ## Troubleshooting
 
 First check that the Matrix client app you are using supports UnifiedPush. There may well be different variants of the app.
 
 Set the ntfy server's log level to 'DEBUG', as shown in the example settings above, and watch the server's logs with `sudo journalctl -fu matrix-ntfy`.
 
-To check if UnifiedPush is correctly configured on the client device, look at "Settings -> Notifications -> Notification Targets" in Element-Android or SchildiChat, or "Settings -> Notifications -> Devices" in FluffyChat. There should be one entry for each Matrix client app that has enabled push notifications, and when that client is using UnifiedPush you should see a URL that begins with your ntfy server's URL.
+To check if UnifiedPush is correctly configured on the client device, look at "Settings -> Notifications -> Notification Targets" in Element Android or SchildiChat Android, or "Settings -> Notifications -> Devices" in FluffyChat. There should be one entry for each Matrix client app that has enabled push notifications, and when that client is using UnifiedPush you should see a URL that begins with your ntfy server's URL.
 
-In the "Notification Targets" screen in Element-Android or SchildiChat, two relevant URLs are shown, "push\_key" and "Url", and both should begin with your ntfy server's URL. If "push\_key" shows your server but "Url" shows an external server such as `up.schildi.chat` then push notifications will still work but are being routed through that external server before they reach your ntfy server. To rectify that, in SchildiChat (at least around version 1.4.20.sc55) you must enable the `Force custom push gateway` setting as described in the "Usage" section above.
+In the "Notification Targets" screen in Element Android or SchildiChat Android, two relevant URLs are shown, "push\_key" and "Url", and both should begin with your ntfy server's URL. If "push\_key" shows your server but "Url" shows an external server such as `up.schildi.chat` then push notifications will still work but are being routed through that external server before they reach your ntfy server. To rectify that, in SchildiChat (at least around version 1.4.20.sc55) you must enable the `Force custom push gateway` setting as described in the "Usage" section above.
 
-If it is not working, useful tools are "Settings -> Notifications -> Re-register push distributor" and "Settings -> Notifications -> Troubleshoot Notifications" in SchildiChat (possibly also Element-Android). In particular the "Endpoint/FCM" step of that troubleshooter should display your ntfy server's URL that it has discovered from the ntfy client app.
+If it is not working, useful tools are "Settings -> Notifications -> Re-register push distributor" and "Settings -> Notifications -> Troubleshoot Notifications" in SchildiChat Android (possibly also Element Android). In particular the "Endpoint/FCM" step of that troubleshooter should display your ntfy server's URL that it has discovered from the ntfy client app.
 
 The simple [UnifiedPush troubleshooting](https://unifiedpush.org/users/troubleshooting/) app [UP-Example](https://f-droid.org/en/packages/org.unifiedpush.example/) can be used to manually test UnifiedPush registration and operation on an Android device.
diff --git a/docs/configuring-playbook-own-webserver.md b/docs/configuring-playbook-own-webserver.md
index 5fa55eaed..8f8f8682d 100644
--- a/docs/configuring-playbook-own-webserver.md
+++ b/docs/configuring-playbook-own-webserver.md
@@ -24,7 +24,6 @@ traefik_config_certificatesResolvers_acme_email: YOUR_EMAIL_ADDRESS
 
 Traefik will manage SSL certificates for all services seamlessly.
 
-
 ### Traefik managed by you
 
 ```yaml
@@ -41,6 +40,14 @@ traefik_certs_dumper_ssl_dir_path: "/path/to/your/traefiks/acme.json/directory"
 # Uncomment and adjust the variable below if the name of your federation entrypoint is different
 # than the default value (matrix-federation).
 # matrix_federation_traefik_entrypoint_name: matrix-federation
+
+# Uncomment and adjust the variables below if you'd like to enable HTTP-compression.
+#
+# For this to work, you will need to define a compress middleware (https://doc.traefik.io/traefik/middlewares/http/compress/) for your Traefik instance
+# using a file (https://doc.traefik.io/traefik/providers/file/) or Docker (https://doc.traefik.io/traefik/providers/docker/) configuration provider.
+#
+# matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled: true
+# matrix_playbook_reverse_proxy_traefik_middleware_compression_name: my-compression-middleware@file
 ```
 
 In this mode all roles will still have Traefik labels attached. You will, however, need to configure your Traefik instance and its entrypoints.
@@ -84,7 +91,7 @@ version: "3.3"
 services:
 
   traefik:
-    image: "docker.io/traefik:v2.9.6"
+    image: "docker.io/traefik:v3.2.0"
     restart: always
     container_name: "traefik"
     networks:
@@ -124,7 +131,6 @@ There are 2 ways to go about it:
 
 - (difficult) [Using no reverse-proxy on the Matrix side at all](#using-no-reverse-proxy-on-the-matrix-side-at-all) disabling the playbook-managed reverse-proxy (Traefik), exposing services one by one using `_host_bind_port` variables and forwarding traffic from your own webserver to those ports
 
-
 ### Fronting the integrated reverse-proxy webserver with another reverse-proxy
 
 This method is about leaving the integrated reverse-proxy webserver be, but making it not get in the way (using up important ports, trying to retrieve SSL certificates, etc.).
@@ -185,14 +191,13 @@ matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_custom:
   # trustedIPs: ['IP-ADDRESS-OF-YOUR-REVERSE-PROXY']
 ```
 
-Such a configuration would expose all services on a local port `81` and Matrix Federation on a local port `8449`.
+Such a configuration would expose all services on a local port `81` and Matrix Federation on a local port `8449`. Your reverse-proxy configuration needs to send traffic to these ports. [`examples/reverse-proxies`](../examples/reverse-proxies/) contains examples for various webservers such as Apache2, Caddy, HAproxy, nginx and Nginx Proxy Manager.
 
-Your reverse-proxy configuration needs to send traffic to these ports. The [`examples/reverse-proxies` directory](../examples/reverse-proxies/) contains sample configuration for various webservers (Apache2, Caddy, HAproxy, nginx, Nginx Proxy Manager).
-
-It's important that these webservers proxy-pass requests to the correct place and also set the `Host` HTTP header appropriately. If you don't pass the `Host` header correctly, you would get a 404 not found error from Traefik.
-
-To put it another way, `curl http://127.0.0.1:81` would give you a 404, but `curl -H 'Host: matrix.example.com' http://127.0.0.1:81` should work.
+It's important that these webservers proxy-pass requests to the correct `ip:port` and also set the `Host` HTTP header appropriately. If you don't pass the `Host` header correctly, Traefik will return a `404 - not found` error.
 
+To put it another way:
+- `curl http://127.0.0.1:81` will result in a `404 - not found` error
+- but `curl -H 'Host: matrix.example.com' http://127.0.0.1:81` should work.
 
 ### Using no reverse-proxy on the Matrix side at all
 
diff --git a/docs/configuring-playbook-pantalaimon.md b/docs/configuring-playbook-pantalaimon.md
index 4c2ad39ec..db40fe018 100644
--- a/docs/configuring-playbook-pantalaimon.md
+++ b/docs/configuring-playbook-pantalaimon.md
@@ -1,12 +1,12 @@
-# Setting up pantalaimon (optional)
+# Setting up Pantalaimon (E2EE aware proxy daemon) (optional)
 
 The playbook can install and configure the [pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you.
 
-See the project's [documentation](https://github.com/matrix-org/pantalaimon) to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/matrix-org/pantalaimon/blob/master/README.md) to learn what it does and why it might be useful to you.
 
 This role exposes Pantalaimon's API only within the container network, so bots and clients installed on the same machine can use it. In particular the [Draupnir](configuring-playbook-bot-draupnir.md) and [Mjolnir](configuring-playbook-bot-mjolnir.md) roles (and possibly others) can use it.
 
-## 1. Adjusting the playbook configuration
+## Adjusting the playbook configuration
 
 Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):
 
@@ -16,6 +16,15 @@ matrix_pantalaimon_enabled: true
 
 The default configuration should suffice. For advanced configuration, you can override the variables documented in the role's [defaults](../roles/custom/matrix-pantalaimon/defaults/main.yml).
 
-## 2. Installing
+## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
diff --git a/docs/configuring-playbook-postgres-backup.md b/docs/configuring-playbook-postgres-backup.md
index 109cf8c20..165609d0c 100644
--- a/docs/configuring-playbook-postgres-backup.md
+++ b/docs/configuring-playbook-postgres-backup.md
@@ -4,7 +4,6 @@ The playbook can install and configure [docker-postgres-backup-local](https://gi
 
 For a more complete backup solution (one that includes not only Postgres, but also other configuration/data files), you may wish to look into [BorgBackup](configuring-playbook-backup-borg.md) instead.
 
-
 ## Adjusting the playbook configuration
 
 To enable Postgres backup, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
@@ -15,7 +14,6 @@ postgres_backup_enabled: true
 
 Refer to the table below for additional configuration variables and their default values.
 
-
 | Name                              | Default value                | Description                                                      |
 | :-------------------------------- | :--------------------------- | :--------------------------------------------------------------- |
 |`postgres_backup_enabled`|`false`|Set to true to use [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) to create automatic database backups|
@@ -26,11 +24,15 @@ Refer to the table below for additional configuration variables and their defaul
 |`postgres_backup_base_path` | `"{{ matrix_base_data_path }}/postgres-backup"` | Base path for postgres-backup. Also see `postgres_backup_data_path` |
 |`postgres_backup_data_path` | `"{{ postgres_backup_base_path }}/data"` | Storage path for postgres-backup database backups |
 
-
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command:
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-```
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
 ```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
diff --git a/docs/configuring-playbook-prometheus-grafana.md b/docs/configuring-playbook-prometheus-grafana.md
index 92197cbff..851fa1635 100644
--- a/docs/configuring-playbook-prometheus-grafana.md
+++ b/docs/configuring-playbook-prometheus-grafana.md
@@ -1,7 +1,13 @@
-# Enabling metrics and graphs for your Matrix server (optional)
+# Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server (optional)
 
 The playbook can install [Grafana](https://grafana.com/) with [Prometheus](https://prometheus.io/) and configure performance metrics of your homeserver with graphs for you.
 
+## Adjusting DNS records
+
+By default, this playbook installs Grafana web user-interface on the `stats.` subdomain (`stats.example.com`) and requires you to create a CNAME record for `stats`, which targets `matrix.example.com`.
+
+When setting, replace `example.com` with your own.
+
 ## Adjusting the playbook configuration
 
 To enable Grafana and/or Prometheus, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
@@ -32,30 +38,33 @@ grafana_default_admin_password: "some_strong_password_chosen_by_you"
 
 The retention policy of Prometheus metrics is [15 days by default](https://prometheus.io/docs/prometheus/latest/storage/#operational-aspects). Older data gets deleted automatically.
 
-### Adjusting the Grafana URL
-
-By default, this playbook installs Grafana web user-interface on the `stats.` subdomain (`stats.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records).
+### Adjusting the Grafana URL (optional)
 
 By tweaking the `grafana_hostname` variable, you can easily make the service available at a **different hostname** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Change the default hostname
 grafana_hostname: grafana.example.com
 ```
 
-## Adjusting DNS records
-
-Once you've decided on the domain, **you may need to adjust your DNS** records to point the Grafana domain to the Matrix server.
-
-By default, you will need to create a CNAME record for `stats`. See [Configuring DNS](configuring-dns.md) for details about DNS changes.
+After changing the domain, **you may need to adjust your DNS** records to point the Grafana domain to the Matrix server.
 
 **Note**: It is possible to install Prometheus without installing Grafana. This case it is not required to create the CNAME record.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
 
 ## What does it do?
 
@@ -69,14 +78,12 @@ Name | Description
 `grafana_anonymous_access`|By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option.
 `grafana_default_admin_user`<br>`grafana_default_admin_password`|By default Grafana creates a user with `admin` as the username and password. If you feel this is insecure and you want to change it beforehand, you can do that here
 
-
 ## Security and privacy
 
 Metrics and resulting graphs can contain a lot of information. This includes system specs but also usage patterns. This applies especially to small personal/family scale homeservers. Someone might be able to figure out when you wake up and go to sleep by looking at the graphs over time. Think about this before enabling anonymous access. And you should really not forget to change your Grafana password.
 
 Most of our docker containers run with limited system access, but the `prometheus-node-exporter` has access to the host network stack and (readonly) root filesystem. This is required to report on them. If you don't like that, you can set `prometheus_node_exporter_enabled: false` (which is actually the default). You will still get Synapse metrics with this container disabled. Both of the dashboards will always be enabled, so you can still look at historical data after disabling either source.
 
-
 ## Collecting metrics to an external Prometheus server
 
 **If the integrated Prometheus server is enabled** (`prometheus_enabled: true`), metrics are collected by it from each service via communication that happens over the container network. Each service does not need to expose its metrics "publicly".
@@ -113,6 +120,7 @@ Name | Description
 If you are using workers (`matrix_synapse_workers_enabled: true`) and have enabled `matrix_synapse_metrics_proxying_enabled` as described above, the playbook will also automatically expose all Synapse worker threads' metrics to `https://matrix.example.com/metrics/synapse/worker/ID`, where `ID` corresponds to the worker `id` as exemplified in `matrix_synapse_workers_enabled_list`.
 
 The playbook also generates an exemplary config file (`/matrix/synapse/external_prometheus.yml.template`) with all the correct paths which you can copy to your Prometheus server and adapt to your needs. Make sure to edit the specified `password_file` path and contents and path to your `synapse-v2.rules`. It will look a bit like this:
+
 ```yaml
 scrape_configs:
   - job_name: 'synapse'
@@ -139,7 +147,6 @@ scrape_configs:
           index: 18111
 ```
 
-
 ## More information
 
 - [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)
diff --git a/docs/configuring-playbook-prometheus-nginxlog.md b/docs/configuring-playbook-prometheus-nginxlog.md
index e6ed3043a..1683210c3 100644
--- a/docs/configuring-playbook-prometheus-nginxlog.md
+++ b/docs/configuring-playbook-prometheus-nginxlog.md
@@ -12,7 +12,7 @@ To make use of this, you need to install [Prometheus](./configuring-playbook-pro
 
 If your setup includes [Grafana](./configuring-playbook-prometheus-grafana.md), a dedicated `NGINX PROXY` Grafana dashboard will be created.
 
-## Configuration
+## Adjusting the playbook configuration
 
 Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
@@ -22,7 +22,16 @@ matrix_prometheus_nginxlog_exporter_enabled: true
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
 
 ## Docker Image Compatibility
 
diff --git a/docs/configuring-playbook-prometheus-postgres.md b/docs/configuring-playbook-prometheus-postgres.md
index f24bc0818..74d3eda4f 100644
--- a/docs/configuring-playbook-prometheus-postgres.md
+++ b/docs/configuring-playbook-prometheus-postgres.md
@@ -12,7 +12,16 @@ prometheus_postgres_exporter_enabled: true
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
 
 ## What does it do?
 
@@ -23,7 +32,6 @@ Name | Description
 `prometheus_postgres_exporter_database_password`| The 'password' for the user that the exporter uses to connect to the database. By default, this is auto-generated by the playbook
 `prometheus_postgres_exporter_container_labels_traefik_enabled`|If set to `true`, exposes the Postgres exporter metrics on `https://matrix.example.com/metrics/postgres-exporter` for usage with an [external Prometheus server](configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` on that other documentation page.
 
-
 ## More information
 
 - [The PostgresSQL dashboard](https://grafana.com/grafana/dashboards/9628) (generic postgres dashboard)
diff --git a/docs/configuring-playbook-rageshake.md b/docs/configuring-playbook-rageshake.md
index e43114459..6db32e43a 100644
--- a/docs/configuring-playbook-rageshake.md
+++ b/docs/configuring-playbook-rageshake.md
@@ -1,8 +1,16 @@
-# Setting up rageshake (optional)
+# Setting up the rageshake bug report server (optional)
 
 The playbook can install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server for you.
 
-This is useful if you're developing your own applications and would like to collect bug reports for them.
+See the project's [documentation](https://github.com/matrix-org/rageshake/blob/main/README.md) to learn what it does and why it might be useful to you.
+
+**Note**: most people don't need to install rageshake to collect bug reports. This component is only useful to people who develop/build their own Matrix client applications themselves.
+
+## Adjusting DNS records
+
+By default, this playbook installs rageshake on the `rageshake.` subdomain (`rageshake.example.com`) and requires you to create a CNAME record for `rageshake`, which targets `matrix.example.com`.
+
+When setting, replace `example.com` with your own.
 
 ## Adjusting the playbook configuration
 
@@ -24,13 +32,11 @@ matrix_rageshake_configuration_extension_yaml: |
      my-app: octocat/HelloWorld
 ```
 
-### Adjusting the rageshake URL
-
-By default, this playbook installs rageshake on the `rageshake.` subdomain (`rageshake.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records).
+### Adjusting the rageshake URL (optional)
 
 By tweaking the `matrix_rageshake_hostname` and `matrix_rageshake_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Switch to the domain used for Matrix services (`matrix.example.com`),
@@ -41,23 +47,23 @@ matrix_rageshake_hostname: "{{ matrix_server_fqn_matrix }}"
 matrix_rageshake_path_prefix: /rageshake
 ```
 
-## Adjusting DNS records
-
-Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the rageshake domain to the Matrix server.
-
-By default, you will need to create a CNAME record for `rageshake`. See [Configuring DNS](configuring-dns.md) for details about DNS changes.
+After changing the domain, **you may need to adjust your DNS** records to point the rageshake domain to the Matrix server.
 
 If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command:
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
 
-```
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
 ```
 
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
 
 ## Usage
 
-Refer to the [rageshake documentation](https://github.com/matrix-org/rageshake) for available APIs, etc.
+Refer to the project's [documentation](https://github.com/matrix-org/rageshake/blob/main/README.md) for available APIs, etc.
diff --git a/docs/configuring-playbook-rest-auth.md b/docs/configuring-playbook-rest-auth.md
index c9352c6c6..d15ba586b 100644
--- a/docs/configuring-playbook-rest-auth.md
+++ b/docs/configuring-playbook-rest-auth.md
@@ -2,7 +2,7 @@
 
 The playbook can install and configure [matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) for you.
 
-See that project's documentation to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/ma1uta/matrix-synapse-rest-password-provider/blob/master/README.md) to learn what it does and why it might be useful to you.
 
 ## Adjusting the playbook configuration
 
@@ -26,4 +26,13 @@ matrix_synapse_password_config_localdb_enabled: false
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
diff --git a/docs/configuring-playbook-riot-web.md b/docs/configuring-playbook-riot-web.md
index f2ffb869a..e008a3f89 100644
--- a/docs/configuring-playbook-riot-web.md
+++ b/docs/configuring-playbook-riot-web.md
@@ -4,11 +4,10 @@ By default, this playbook **used to install** the [Riot-web](https://github.com/
 
 Riot has since been [renamed to Element](https://element.io/blog/welcome-to-element/).
 
-- to learn more about Element and its configuration, see our dedicated [Configuring Element](configuring-playbook-client-element.md) documentation page
-- to learn how to migrate from Riot to Element, see [Migrating to Element](#migrating-to-element) below
+- to learn more about Element Web and its configuration, see our dedicated [Configuring Element Web](configuring-playbook-client-element-web.md) documentation page
+- to learn how to migrate from Riot to Element Web, see [Migrating to Element Web](#migrating-to-element-web) below
 
-
-## Migrating to Element
+## Migrating to Element Web
 
 ### Migrating your custom settings
 
@@ -16,18 +15,25 @@ If you have custom `matrix_riot_web_` variables in your `inventory/host_vars/mat
 
 Some other playbook variables (but not all) with `riot` in their name are also renamed. The playbook checks and warns if you are using the old name for some commonly used ones.
 
-
 ### Domain migration
 
-We used to set up Riot at the `riot.example.com` domain. The playbook now sets up Element at `element.example.com` by default.
+We used to set up Riot at the `riot.example.com` domain. The playbook now sets up Element Web at `element.example.com` by default.
 
 There are a few options for handling this:
 
-- (**avoiding changes** - using the old `riot.example.com` domain and avoiding DNS changes) -- to keep using `riot.example.com` instead of `element.example.com`, override the domain at which the playbook serves Element: `matrix_server_fqn_element: "riot.{{ matrix_domain }}"`
+- (**avoiding changes** - using the old `riot.example.com` domain and avoiding DNS changes) -- to keep using `riot.example.com` instead of `element.example.com`, override the domain at which the playbook serves Element Web: `matrix_server_fqn_element: "riot.{{ matrix_domain }}"`
 
 - (**embracing changes** - using only `element.example.com`) - set up the `element.example.com` DNS record (see [Configuring DNS](configuring-dns.md)). You can drop the `riot.example.com` in this case.
 
-
 ### Re-running the playbook
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
diff --git a/docs/configuring-playbook-s3-goofys.md b/docs/configuring-playbook-s3-goofys.md
index ba1001f0e..720c7d8b2 100644
--- a/docs/configuring-playbook-s3-goofys.md
+++ b/docs/configuring-playbook-s3-goofys.md
@@ -29,58 +29,52 @@ matrix_s3_media_store_custom_endpoint: "https://your-custom-endpoint"
 
 If you have local media store files and wish to migrate to Backblaze B2 subsequently, follow our [migration guide to Backblaze B2](#migrating-to-backblaze-b2) below instead of applying this configuration as-is.
 
-
 ## Migrating from local filesystem storage to S3
 
-It's a good idea to [make a complete server backup](faq.md#how-do-i-backup-the-data-on-my-server) before migrating your local media store to an S3-backed one.
+It's a good idea to [make a complete server backup](faq.md#how-do-i-back-up-the-data-on-my-server) before migrating your local media store to an S3-backed one.
 
-Follow one of the guides below for a migration path from a locally-stored media store to one stored on S3-compatible storage:
+After making the backup, follow one of the guides below for a migration path from a locally-stored media store to one stored on S3-compatible storage:
 
-- [Storing Matrix media files on Amazon S3 with Goofys (optional)](#storing-matrix-media-files-on-amazon-s3-with-goofys-optional)
-	- [Usage](#usage)
-	- [Migrating from local filesystem storage to S3](#migrating-from-local-filesystem-storage-to-s3)
-		- [Migrating to any S3-compatible storage (universal, but likely slow)](#migrating-to-any-s3-compatible-storage-universal-but-likely-slow)
-		- [Migrating to Backblaze B2](#migrating-to-backblaze-b2)
+- [Migrating to any S3-compatible storage (universal, but likely slow)](#migrating-to-any-s3-compatible-storage-universal-but-likely-slow)
+- [Migrating to Backblaze B2](#migrating-to-backblaze-b2)
 
 ### Migrating to any S3-compatible storage (universal, but likely slow)
 
-It's a good idea to [make a complete server backup](faq.md#how-do-i-backup-the-data-on-my-server) before doing this.
-
 1. Proceed with the steps below without stopping Matrix services
 
 2. Start by adding the base S3 configuration in your `vars.yml` file (seen above, may be different depending on the S3 provider of your choice)
 
 3. In addition to the base configuration you see above, add this to your `vars.yml` file:
 
-```yaml
-matrix_s3_media_store_path: /matrix/s3-media-store
-```
+    ```yaml
+    matrix_s3_media_store_path: /matrix/s3-media-store
+    ```
 
-This enables S3 support, but mounts the S3 storage bucket to `/matrix/s3-media-store` without hooking it to your homeserver yet. Your homeserver will still continue using your local filesystem for its media store.
+    This enables S3 support, but mounts the S3 storage bucket to `/matrix/s3-media-store` without hooking it to your homeserver yet. Your homeserver will still continue using your local filesystem for its media store.
 
 4. Run the playbook to apply the changes: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`
 
 5. Do an **initial sync of your files** by running this **on the server** (it may take a very long time):
 
-```sh
-sudo -u matrix -- rsync --size-only --ignore-existing -avr /matrix/synapse/storage/media-store/. /matrix/s3-media-store/.
-```
+    ```sh
+    sudo -u matrix -- rsync --size-only --ignore-existing -avr /matrix/synapse/storage/media-store/. /matrix/s3-media-store/.
+    ```
 
-You may need to install `rsync` manually.
+    You may need to install `rsync` manually.
 
 6. Stop all Matrix services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)
 
 7. Start the S3 service by running this **on the server**: `systemctl start matrix-goofys`
 
-8. Sync the files again by re-running the `rsync` command you see in step #6
+8. Sync the files again by re-running the `rsync` command you see in step #5
 
 9. Stop the S3 service by running this **on the server**: `systemctl stop matrix-goofys`
 
 10. Get the old media store out of the way by running this command on the server:
 
-```sh
-mv /matrix/synapse/storage/media-store /matrix/synapse/storage/media-store-local-backup
-```
+    ```sh
+    mv /matrix/synapse/storage/media-store /matrix/synapse/storage/media-store-local-backup
+    ```
 
 11. Remove the `matrix_s3_media_store_path` configuration from your `vars.yml` file (undoing step #3 above)
 
@@ -90,43 +84,40 @@ mv /matrix/synapse/storage/media-store /matrix/synapse/storage/media-store-local
 
 14. When confident that it all works, get rid of the local media store directory: `rm -rf /matrix/synapse/storage/media-store-local-backup`
 
-
 ### Migrating to Backblaze B2
 
-It's a good idea to [make a complete server backup](faq.md#how-do-i-backup-the-data-on-my-server) before doing this.
-
 1. While all Matrix services are running, run the following command on the server:
 
-(you need to adjust the 3 `--env` line below with your own data)
+    (you need to adjust the 3 `--env` line below with your own data)
 
-```sh
-docker run -it --rm -w /work \
---env='B2_KEY_ID=YOUR_KEY_GOES_HERE' \
---env='B2_KEY_SECRET=YOUR_SECRET_GOES_HERE' \
---env='B2_BUCKET_NAME=YOUR_BUCKET_NAME_GOES_HERE' \
---mount type=bind,src=/matrix/synapse/storage/media-store,dst=/work,ro \
---entrypoint=/bin/sh \
-docker.io/tianon/backblaze-b2:3.6.0 \
--c 'b2 authorize-account $B2_KEY_ID $B2_KEY_SECRET && b2 sync /work b2://$B2_BUCKET_NAME --skipNewer'
-```
+    ```sh
+    docker run -it --rm -w /work \
+    --env='B2_KEY_ID=YOUR_KEY_GOES_HERE' \
+    --env='B2_KEY_SECRET=YOUR_SECRET_GOES_HERE' \
+    --env='B2_BUCKET_NAME=YOUR_BUCKET_NAME_GOES_HERE' \
+    --mount type=bind,src=/matrix/synapse/storage/media-store,dst=/work,ro \
+    --entrypoint=/bin/sh \
+    docker.io/tianon/backblaze-b2:3.6.0 \
+    -c 'b2 authorize-account $B2_KEY_ID $B2_KEY_SECRET && b2 sync /work b2://$B2_BUCKET_NAME --skipNewer'
+    ```
 
-This is some initial file sync, which may take a very long time.
+    This is some initial file sync, which may take a very long time.
 
 2. Stop all Matrix services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)
 
 3. Run the command from step #1 again.
 
-Doing this will sync any new files that may have been created locally in the meantime.
+    Doing this will sync any new files that may have been created locally in the meantime.
 
-Now that Matrix services aren't running, we're sure to get Backblaze B2 and your local media store fully in sync.
+    Now that Matrix services aren't running, we're sure to get Backblaze B2 and your local media store fully in sync.
 
 4. Get the old media store out of the way by running this command on the server:
 
-```sh
-mv /matrix/synapse/storage/media-store /matrix/synapse/storage/media-store-local-backup
-```
+    ```sh
+    mv /matrix/synapse/storage/media-store /matrix/synapse/storage/media-store-local-backup
+    ```
 
-5. Put the [Backblaze B2 settings seen above](#backblaze-b2) in your `vars.yml` file
+5. Put the [Backblaze B2 settings](configuring-playbook-s3.md#backblaze-b2) in your `vars.yml` file
 
 6. Run the playbook: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`
 
diff --git a/docs/configuring-playbook-s3.md b/docs/configuring-playbook-s3.md
index fb7b51b10..cb43c62fb 100644
--- a/docs/configuring-playbook-s3.md
+++ b/docs/configuring-playbook-s3.md
@@ -12,26 +12,24 @@ Then, [create the S3 bucket](#bucket-creation-and-security-configuration).
 
 Finally, [set up S3 storage for Synapse](#setting-up) (with [Goofys](configuring-playbook-s3-goofys.md), [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md), or use s3 datastore with the [matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/configuration/s3-datastore.html)).
 
-
 ## Choosing an Object Storage provider
 
-You can create [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object store like [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html), [Wasabi](https://wasabi.com), [Digital Ocean Spaces](https://www.digitalocean.com/products/spaces), etc.
+You can create [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object storage like [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html), [Storj](https://storj.io), [Wasabi](https://wasabi.com), [Digital Ocean Spaces](https://www.digitalocean.com/products/spaces), etc.
 
-Amazon S3 and Backblaze S3 are pay-as-you with no minimum charges for storing too little data.
+Amazon S3, Backblaze B2, and Storj are pay-as-you with no minimum charges for storing too little data.
 
-All these providers have different prices, with Backblaze B2 appearing to be the cheapest.
+All these providers have different prices, with Storj appearing to be the cheapest (as of 2024-10, storage fee is $0.004 per GB/month, and egress fee is $0.007 per GB). Backblaze egress is free, but for only certain users for up to 3x the amount of data stored. Beyond that you will pay $0.01/GB of egress.
 
-Wasabi has a minimum charge of 1TB if you're storing less than 1TB, which becomes expensive if you need to store less data than that.
+Wasabi has a minimum charge of 1TB if you're storing less than 1TB, which becomes expensive if you need to store less data than that. Likewise, Digital Ocean Spaces has also a minimum charge of 250GB ($5/month as of 2022-10).
 
-Digital Ocean Spaces has a minimum charge of 250GB ($5/month as of 2022-10), which is also expensive if you're storing less data than that.
-
-Important aspects of choosing the right provider are:
-
-- a provider by a company you like and trust (or dislike less than the others)
-- a provider which has a data region close to your Matrix server (if it's farther away, high latency may cause slowdowns)
-- a provider which is OK pricewise
-- a provider with free or cheap egress (if you need to get the data out often, for some reason) - likely not too important for the common use-case
+Here are some of the important aspects of choosing the right provider:
 
+- if a provider is a company you like and trust (or dislike less than the others)
+- if a provider implements end-to-end encryption of your data
+- if a provider has a data region close to your Matrix server (if it's farther away, high latency may cause slowdowns)
+- if a provider's infrastructure such as data center is centralized or distributed
+- if a provider's price model is transparent (whether it includes hidden costs like minimum charge, minimum storage term, etc.)
+- if a provider has free or cheap egress fee (in case you need to get the data out often, for some reason) - likely not too important for the common use-case
 
 ## Bucket creation and Security Configuration
 
@@ -66,7 +64,6 @@ You'll need an Amazon S3 bucket and some IAM user credentials (access key + secr
 
 **Note**: This policy needs to be attached to an IAM user created from the **Security Credentials** menu. This is not a **Bucket Policy**.
 
-
 ## Backblaze B2
 
 To use [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html) you first need to sign up.
@@ -92,18 +89,16 @@ For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3-synapse-stora
 
 - **Storage Class** - use `STANDARD`. Backblaze B2 does not have different storage classes, so it doesn't make sense to use any other value.
 
-
 ## Other providers
 
 For other S3-compatible providers, you may not need to configure security policies, etc. (just like for [Backblaze B2](#backblaze-b2)).
 
 You most likely just need to create an S3 bucket and get some credentials (access key and secret key) for accessing the bucket in a read/write manner.
 
-
 ## Setting up
 
 To set up Synapse to store files in S3, follow the instructions for the method of your choice:
 
 - using [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) (recommended)
 - using [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)
-- using [matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/configuration/s3-datastore.html)
+- using [matrix-media-repo](configuring-playbook-matrix-media-repo.md)
diff --git a/docs/configuring-playbook-shared-secret-auth.md b/docs/configuring-playbook-shared-secret-auth.md
index 0c11df290..c7dced046 100644
--- a/docs/configuring-playbook-shared-secret-auth.md
+++ b/docs/configuring-playbook-shared-secret-auth.md
@@ -2,7 +2,7 @@
 
 The playbook can install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you.
 
-See that project's documentation to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/devture/matrix-synapse-shared-secret-auth/blob/master/README.md) to learn what it does and why it might be useful to you.
 
 ## Adjusting the playbook configuration
 
@@ -11,7 +11,7 @@ Add the following configuration to your `inventory/host_vars/matrix.example.com/
 ```yaml
 matrix_synapse_ext_password_provider_shared_secret_auth_enabled: true
 
-# Generate a strong shared secret here. Consider generating it with `pwgen -s 64 1`
+# Generate a strong shared secret here. You can create one with a command like `pwgen -s 64 1`.
 matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret: YOUR_SHARED_SECRET_GOES_HERE
 ```
 
@@ -25,4 +25,13 @@ matrix_synapse_password_config_localdb_enabled: false
 
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
diff --git a/docs/configuring-playbook-sliding-sync-proxy.md b/docs/configuring-playbook-sliding-sync-proxy.md
index 5754a5e9a..406dc6196 100644
--- a/docs/configuring-playbook-sliding-sync-proxy.md
+++ b/docs/configuring-playbook-sliding-sync-proxy.md
@@ -1,16 +1,16 @@
-# Setting up Sliding Sync proxy (optional)
+# Setting up the Sliding Sync proxy (optional)
+
+**Note**: The sliding-sync proxy is **not required** anymore as it's been replaced with a different method (called Simplified Sliding Sync) which is integrated into newer homeservers by default (**Conduit** homeserver from version `0.6.0` or **Synapse** from version `1.114`). This component and documentation remain here for historical purposes, but **installing this old sliding-sync proxy is generally not recommended anymore**.
 
 The playbook can install and configure [sliding-sync](https://github.com/matrix-org/sliding-sync) proxy for you.
 
-Sliding Sync is an implementation of [MSC3575](https://github.com/matrix-org/matrix-spec-proposals/blob/kegan/sync-v3/proposals/3575-sync.md) and a prerequisite for running the new (**still beta**) Element X clients ([Element X iOS](https://github.com/element-hq/element-x-ios) and [Element X Android](https://github.com/element-hq/element-x-android)).
+Sliding Sync is an implementation of [MSC3575](https://github.com/matrix-org/matrix-spec-proposals/blob/kegan/sync-v3/proposals/3575-sync.md) and a prerequisite for running Element X clients ([Element X iOS](https://github.com/element-hq/element-x-ios) and [Element X Android](https://github.com/element-hq/element-x-android)). See the project's [documentation](https://github.com/matrix-org/sliding-sync) to learn more.
 
-See the project's [documentation](https://github.com/matrix-org/sliding-sync) to learn more.
+## Adjusting DNS records (optional)
 
-Element X iOS is [available on TestFlight](https://testflight.apple.com/join/uZbeZCOi).
+By default, this playbook installs the Sliding Sync proxy on the `matrix.` subdomain, at the `/sliding-sync` path (https://matrix.example.com/sliding-sync). 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.
 
-Element X Android is [available on the Github Releases page](https://github.com/element-hq/element-x-android/releases).
-
-**Note**: The sliding-sync proxy is **not required** when using the **Conduit homeserver**. Starting from version `0.6.0` Conduit has native support for some sliding sync features. If there are issues with the native implementation, you might have a better experience when enabling the sliding-sync proxy anyway.
+If you wish to adjust it, see the section [below](#adjusting-the-sliding-sync-proxy-url-optional) for details about DNS configuration.
 
 ## Adjusting the playbook configuration
 
@@ -20,13 +20,11 @@ To enable Sliding Sync proxy, add the following configuration to your `inventory
 matrix_sliding_sync_enabled: true
 ```
 
-### Adjusting the Sliding Sync proxy URL
-
-By default, this playbook installs the Sliding Sync proxy on the `matrix.` subdomain, at the `/sliding-sync` path (https://matrix.example.com/sliding-sync). 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.
+### Adjusting the Sliding Sync proxy URL (optional)
 
 By tweaking the `matrix_sliding_sync_hostname` and `matrix_sliding_sync_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Change the default hostname and path prefix
@@ -34,17 +32,22 @@ matrix_sliding_sync_hostname: ss.example.com
 matrix_sliding_sync_path_prefix: /
 ```
 
-## Adjusting DNS records
+If you've changed the default hostname, you may need to create a CNAME record for the Sliding Sync proxy domain (`ss.example.com`), which targets `matrix.example.com`.
 
-If you've changed the default hostname, **you may need to adjust your DNS** records to point the Honoroit domain to the Matrix server.
-
-See [Configuring DNS](configuring-dns.md) for details about DNS changes.
-
-If you've decided to use the default hostname, you won't need to do any extra DNS configuration.
+When setting, replace `example.com` with your own.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all`.
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
 
 ### External databases
 
diff --git a/docs/configuring-playbook-ssl-certificates.md b/docs/configuring-playbook-ssl-certificates.md
index e086d457f..94c4d58c5 100644
--- a/docs/configuring-playbook-ssl-certificates.md
+++ b/docs/configuring-playbook-ssl-certificates.md
@@ -4,7 +4,6 @@ By default, this playbook retrieves and auto-renews free SSL certificates from [
 
 This guide is about using the integrated Traefik server and doesn't apply if you're using [your own webserver](configuring-playbook-own-webserver.md).
 
-
 ## Using staging Let's Encrypt certificates instead of real ones
 
 For testing purposes, you may wish to use staging certificates provide by Let's Encrypt.
@@ -15,18 +14,16 @@ Add the following configuration to your `inventory/host_vars/matrix.example.com/
 traefik_config_certificatesResolvers_acme_use_staging: true
 ```
 
-
 ## Disabling SSL termination
 
 For testing or other purposes, you may wish to install services without SSL termination and have services exposed to `http://` instead of `https://`.
 
-Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Add the following configuration to your `vars.yml` file:
 
 ```yaml
 traefik_config_entrypoint_web_secure_enabled: false
 ```
 
-
 ## Using self-signed SSL certificates
 
 If you'd like to use your own SSL certificates, instead of the default (SSL certificates obtained automatically via [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) from [Let's Encrypt](https://letsencrypt.org/)):
@@ -34,7 +31,6 @@ If you'd like to use your own SSL certificates, instead of the default (SSL cert
 - generate your self-signed certificate files
 - follow the [Using your own SSL certificates](#using-your-own-ssl-certificates) documentation below
 
-
 ## Using your own SSL certificates
 
 To use your own SSL certificates with Traefik, you need to:
@@ -54,7 +50,7 @@ traefik_ssl_dir_enabled: true
 
 # Tell Traefik to load our custom ssl key pair by extending provider configuration.
 # The key pair files are created below, in `aux_file_definitions`.
-# The `/ssl/..` path is an in-container path, not a path on the host (like `/matrix/traefik/ssl`). Do not change it!
+# The `/ssl/…` path is an in-container path, not a path on the host (like `/matrix/traefik/ssl`). Do not change it!
 traefik_provider_configuration_extension_yaml:
   tls:
     certificates:
diff --git a/docs/configuring-playbook-sygnal.md b/docs/configuring-playbook-sygnal.md
index df6d57292..7ce58714e 100644
--- a/docs/configuring-playbook-sygnal.md
+++ b/docs/configuring-playbook-sygnal.md
@@ -1,8 +1,8 @@
-# Setting up Sygnal (optional)
+# Setting up the Sygnal push gateway (optional)
 
 The playbook can install and configure the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you.
 
-See the project's [documentation](https://github.com/matrix-org/sygnal) to learn what it does and why it might be useful to you.
+See the project's [documentation](https://github.com/matrix-org/sygnal/blob/master/README.md) to learn what it does and why it might be useful to you.
 
 **Note**: most people don't need to install their own gateway. As Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) documentation says:
 
@@ -10,6 +10,12 @@ See the project's [documentation](https://github.com/matrix-org/sygnal) to learn
 
 This optional playbook component is only useful to people who develop/build their own Matrix client applications themselves.
 
+## Adjusting DNS records
+
+By default, this playbook installs Sygnal on the `sygnal.` subdomain (`sygnal.example.com`) and requires you to create a CNAME record for `sygnal`, which targets `matrix.example.com`.
+
+When setting, replace `example.com` with your own.
+
 ## Adjusting the playbook configuration
 
 To enable Sygnal, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
@@ -23,11 +29,11 @@ matrix_sygnal_apps:
   com.example.myapp.ios:
     type: apns
     keyfile: /data/my_key.p8
-    # .. more configuration ..
+    # … more configuration …
   com.example.myapp.android:
     type: gcm
     api_key: your_api_key_for_gcm
-    # .. more configuration ..
+    # … more configuration …
 
 aux_file_definitions:
   - dest: "{{ matrix_sygnal_data_path }}/my_key.p8"
@@ -40,23 +46,19 @@ aux_file_definitions:
     group: "{{ matrix_user_groupname }}"
 ```
 
-For a more complete example of available fields and values they can take, see `roles/custom/matrix-sygnal/templates/sygnal.yaml.j2` (or the [upstream `sygnal.yaml.sample` configuration file](https://github.com/matrix-org/sygnal/blob/master/sygnal.yaml.sample)).
-
 Configuring [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/) is easier, as it only requires that you provide some config values.
 
 To configure [APNS](https://developer.apple.com/notifications/) (Apple Push Notification Service), you'd need to provide one or more certificate files. To do that, the above example configuration:
 
 - makes use of the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) (and its `aux_file_definitions` variable) to make the playbook install files into `/matrix/sygnal/data` (the `matrix_sygnal_data_path` variable). See [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml) of the `aux` role for usage examples. It also makes sure the files are owned by `matrix:matrix`, so that Sygnal can read them. Of course, you can also install these files manually yourself, if you'd rather not use `aux`.
 
-- references these files in the Sygnal configuration (`matrix_sygnal_apps`) using a path like `/data/..` (the `/matrix/sygnal/data` directory on the host system is mounted into the `/data` directory inside the container)
+- references these files in the Sygnal configuration (`matrix_sygnal_apps`) using a path like `/data/…` (the `/matrix/sygnal/data` directory on the host system is mounted into the `/data` directory inside the container)
 
-### Adjusting the Sygnal URL
-
-By default, this playbook installs Sygnal on the `sygnal.` subdomain (`sygnal.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records).
+### Adjusting the Sygnal URL (optional)
 
 By tweaking the `matrix_sygnal_hostname` and `matrix_sygnal_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Switch to the domain used for Matrix services (`matrix.example.com`),
@@ -67,22 +69,31 @@ matrix_sygnal_hostname: "{{ matrix_server_fqn_matrix }}"
 matrix_sygnal_path_prefix: /sygnal
 ```
 
-## Adjusting DNS records
-
-Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Sygnal domain to the Matrix server.
-
-By default, you will need to create a CNAME record for `sygnal`. See [Configuring DNS](configuring-dns.md) for details about DNS changes.
+After changing the domain, **you may need to adjust your DNS** records to point the Sygnal domain to the Matrix server.
 
 If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration.
 
+### Extending the configuration
+
+There are some additional things you may wish to configure about the component.
+
+Take a look at:
+
+- `roles/custom/matrix-sygnal/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+- `roles/custom/matrix-sygnal/templates/config.yaml.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_sygnal_configuration_extension_yaml` variable
+
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command:
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
 
-```
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
 ```
 
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
 
 ## Usage
 
diff --git a/docs/configuring-playbook-synapse-admin.md b/docs/configuring-playbook-synapse-admin.md
index 27003b528..22635d012 100644
--- a/docs/configuring-playbook-synapse-admin.md
+++ b/docs/configuring-playbook-synapse-admin.md
@@ -1,11 +1,16 @@
 # Setting up Synapse Admin (optional)
 
-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)) for you.
+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.
 
-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://matrix-org.github.io/dendrite/administration/adminapi) differs from [Synapse Admin API](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/).
+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/).
 
-See the project's [documentation](https://github.com/etkecc/synapse-admin) to learn what it does and why it might be useful to you.
+💡 **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.
 
+## Adjusting DNS records (optional)
+
+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.
+
+If you wish to adjust it, see the section [below](#adjusting-the-synapse-admin-url-optional) for details about DNS configuration.
 
 ## Adjusting the playbook configuration
 
@@ -22,15 +27,13 @@ matrix_synapse_admin_enabled: true
 
 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.
 
-⚠ **Warning**: If you're using [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS) for authentication, you will be able to [log into synapse-admin with an access token](https://github.com/etkecc/synapse-admin/pull/58), but certain synapse-admin features (especially those around user management) will be limited or not work at all.
+⚠️ **Warning**: If you're using [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS) for authentication, you will be able to [log into synapse-admin with an access token](https://github.com/etkecc/synapse-admin/pull/58), but certain synapse-admin features (especially those around user management) will be limited or not work at all.
 
-### Adjusting the Synapse Admin URL
-
-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.
+### Adjusting the Synapse Admin URL (optional)
 
 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.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Change the default hostname and path prefix
@@ -38,17 +41,22 @@ matrix_synapse_admin_hostname: admin.example.com
 matrix_synapse_admin_path_prefix: /
 ```
 
-## Adjusting DNS records
+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`.
 
-If you've changed the default hostname, **you may need to adjust your DNS** records to point the Synapse Admin domain to the Matrix server.
-
-See [Configuring DNS](configuring-dns.md) for details about DNS changes.
-
-If you've decided to use the default hostname, you won't need to do any extra DNS configuration.
+When setting, replace `example.com` with your own.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command:
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
 
 ## Usage
 
diff --git a/docs/configuring-playbook-synapse-auto-accept-invite.md b/docs/configuring-playbook-synapse-auto-accept-invite.md
index d315f6410..52c1c46ae 100644
--- a/docs/configuring-playbook-synapse-auto-accept-invite.md
+++ b/docs/configuring-playbook-synapse-auto-accept-invite.md
@@ -2,12 +2,13 @@
 
 The playbook can install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) for you.
 
-See that project's [documentation](https://github.com/matrix-org/synapse-auto-accept-invite) to learn what it does and why it might be useful to you. 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.
+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.
+
+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.
 
 **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.
 
-
-## Configuration
+## Adjusting the playbook configuration
 
 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:
 
@@ -27,14 +28,13 @@ matrix_synapse_ext_synapse_auto_accept_invite_worker_to_run_on: 'matrix-synapse-
 
 There might be an [issue with federation](https://github.com/matrix-org/synapse-auto-accept-invite/issues/18).
 
-
 ## Native alternative
 
 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.
 
 Here's example configuration for using the **native** Synapse feature:
 
-```yml
+```yaml
 matrix_synapse_auto_accept_invites_enabled: true
 
 # Default settings below. Uncomment and adjust this part if necessary.
diff --git a/docs/configuring-playbook-synapse-auto-compressor.md b/docs/configuring-playbook-synapse-auto-compressor.md
index bf2c0e1c4..50e981cb4 100644
--- a/docs/configuring-playbook-synapse-auto-compressor.md
+++ b/docs/configuring-playbook-synapse-auto-compressor.md
@@ -1,11 +1,10 @@
-# Setting up synapse_auto_compressor
+# Setting up synapse-auto-compressor (optional)
 
 The playbook can install and configure [synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) for you.
 
 It's a CLI tool that automatically compresses Synapse's `state_groups` database table in the background.
 
-See the project's [documentation](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) to learn what it does and why it might be useful to you.
-
+See the project's [documentation](https://github.com/matrix-org/rust-synapse-compress-state/blob/master/README.md#automated-tool-synapse_auto_compressor) to learn what it does and why it might be useful to you.
 
 ## Adjusting the playbook configuration
 
@@ -15,15 +14,18 @@ Add the following configuration to your `inventory/host_vars/matrix.example.com/
 matrix_synapse_auto_compressor_enabled: true
 ```
 
-
 ## Installing
 
-After configuring the playbook, run the [installation](installing.md) command:
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-```
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
 ```
 
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
 
 ## Usage
 
diff --git a/docs/configuring-playbook-synapse-s3-storage-provider.md b/docs/configuring-playbook-synapse-s3-storage-provider.md
index dc7d56648..02b79c240 100644
--- a/docs/configuring-playbook-synapse-s3-storage-provider.md
+++ b/docs/configuring-playbook-synapse-s3-storage-provider.md
@@ -4,7 +4,6 @@ If you'd like to store Synapse's content repository (`media_store`) files on Ama
 
 An alternative (which has worse performance) is to use [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md).
 
-
 ## How it works?
 
 Summarized writings here are inspired by [this article](https://quentin.dufour.io/blog/2021-09-14/matrix-synapse-s3-storage/).
@@ -22,10 +21,9 @@ You can run some scripts to delete the local files once in a while (which we do
 
 While you will need some local disk space around, it's only to accommodate usage, etc., and won't grow as large as your S3 store.
 
+## Adjusting the playbook configuration
 
-## Installing
-
-After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), you can proceed to configure `s3-storage-provider` in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):
+After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
 ```yaml
 matrix_synapse_ext_synapse_s3_storage_provider_enabled: true
@@ -45,11 +43,19 @@ matrix_synapse_ext_synapse_s3_storage_provider_config_storage_class: STANDARD #
 # This only works on AWS when your server is hosted on an EC2 instance with the correct instance profile set.
 # Uncomment the variable below to use it.
 # matrix_synapse_ext_synapse_s3_storage_provider_config_ec2_instance_profile: true
-
-# For additional advanced settings, take a look at `roles/custom/matrix-synapse/defaults/main.yml`
 ```
 
-If you have existing files in Synapse's media repository (`/matrix/synapse/media-store/..`):
+### Extending the configuration
+
+There are some additional things you may wish to configure about the server.
+
+Take a look at:
+
+- `roles/custom/matrix-synapse/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+
+## Usage
+
+If you have existing files in Synapse's media repository (`/matrix/synapse/storage/media-store/…`):
 
 - new files will start being stored both locally and on the S3 store
 - the existing files will remain on the local filesystem only until [migrating them to the S3 store](#migrating-your-existing-media-files-to-the-s3-store)
@@ -57,17 +63,16 @@ If you have existing files in Synapse's media repository (`/matrix/synapse/media
 
 Regardless of whether you need to [Migrate your existing files to the S3 store](#migrating-your-existing-media-files-to-the-s3-store) or not, make sure you've familiarized yourself with [How it works?](#how-it-works) above and [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem) below.
 
-
-## Migrating your existing media files to the S3 store
+### Migrating your existing media files to the S3 store
 
 Migrating your existing data can happen in multiple ways:
 
 - [using the `s3_media_upload` script from `synapse-s3-storage-provider`](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (very slow when dealing with lots of data)
 - [using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload) (quicker when dealing with lots of data)
 
-### Using the `s3_media_upload` script from `synapse-s3-storage-provider`
+💡 **Note**: instead of using `s3_media_upload` directly, which is very slow and painful for an initial data migration, we recommend [using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload).
 
-Instead of using `s3_media_upload` directly, which is very slow and painful for an initial data migration, we recommend [using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload).
+#### Using the `s3_media_upload` script from `synapse-s3-storage-provider`
 
 To copy your existing files, SSH into the server and run `/matrix/synapse/ext/s3-storage-provider/bin/shell`.
 
@@ -76,8 +81,8 @@ This launches a Synapse container, which has access to the local media store, Po
 Then use the following commands (`$` values come from environment variables - they're **not placeholders** that you need to substitute):
 
 1. `s3_media_upload update-db $UPDATE_DB_DURATION` - create a local SQLite database (`cache.db`) with a list of media repository files (from the `synapse` Postgres database) eligible for operating on
-  - `$UPDATE_DB_DURATION` is influenced by the `matrix_synapse_ext_synapse_s3_storage_provider_update_db_day_count` variable (defaults to `0`)
-  - `$UPDATE_DB_DURATION` defaults to `0d` (0 days), which means **include files which haven't been accessed for more than 0 days** (that is, **all files will be included**).
+    - `$UPDATE_DB_DURATION` is influenced by the `matrix_synapse_ext_synapse_s3_storage_provider_update_db_day_count` variable (defaults to `0`)
+    - `$UPDATE_DB_DURATION` defaults to `0d` (0 days), which means **include files which haven't been accessed for more than 0 days** (that is, **all files will be included**).
 2. `s3_media_upload check-deleted $MEDIA_PATH` - check whether files in the local cache still exist in the local media repository directory
 3. `s3_media_upload upload $MEDIA_PATH $BUCKET --delete --storage-class $STORAGE_CLASS --endpoint-url $ENDPOINT` - uploads locally-stored files to S3 and deletes them from the local media repository directory
 
@@ -88,9 +93,9 @@ Instead of running the above commands manually in the shell, you can also run th
 - it's what the upstream project demonstrates and it teaches you how to use the `s3_media_upload` tool
 - allows you to check and verify the output of each command, to catch mistakes
 - includes progress bars and detailed output for each command
-- allows you to easily interrupt slow-running commands, etc. (the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container without interactive TTY support, so `Ctrl+C` may not work and you and require killing via `docker kill ..`)
+- allows you to easily interrupt slow-running commands, etc. (the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container without interactive TTY support, so `Ctrl+C` may not work and you and require killing via `docker kill …`)
 
-### Using another tool in combination with `s3_media_upload`
+#### Using another tool in combination with `s3_media_upload`
 
 To migrate your existing local data to S3, we recommend to:
 
@@ -98,7 +103,7 @@ To migrate your existing local data to S3, we recommend to:
 
 - **only then** [use the `s3_media_upload` tool to finish the migration](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (this checks to ensure all files are uploaded and then deletes the local files)
 
-#### Copying data to Amazon S3
+##### Copying data to Amazon S3
 
 To copy to AWS S3, start a container on the Matrix server like this:
 
@@ -112,13 +117,13 @@ docker.io/amazon/aws-cli:2.9.16 \
 -c 'aws s3 sync /work/. s3://$BUCKET/'
 ```
 
-#### Copying data to an S3 alternative using the aws-s3 tool
+##### Copying data to an S3 alternative using the aws-s3 tool
 
-To copy to a provider other than AWS S3 (e.g. Wasabi, Digital Ocean Spaces, etc.), you can use the command for [Copying data to Amazon S3](#copying-data-to-amazon-s3) with an added `--endpoint-url=$ENDPOINT` argument.
+To copy to a provider other than AWS S3 (e.g. Storj, Wasabi, Digital Ocean Spaces, etc.), you can use the command for [Copying data to Amazon S3](#copying-data-to-amazon-s3) with an added `--endpoint-url=$ENDPOINT` argument.
 
 Add this argument to the command **as-is** (`$ENDPOINT` is an environment variable corresponding to `matrix_synapse_ext_synapse_s3_storage_provider_config_endpoint_url`, so you don't need to touch it). Make sure to add the argument **before** the final quote (`'`) of the command.
 
-#### Copying data to Backblaze B2
+##### Copying data to Backblaze B2
 
 You can copy files to Backblaze B2 either by following the [Copying data to an S3 alternative using the aws-s3 tool](#copying-data-to-an-s3-alternative-using-the-aws-s3-tool) or by using the B2-specific [b2 command-line tool](https://www.backblaze.com/b2/docs/quick_command_line.html) as described below.
 
@@ -136,14 +141,14 @@ docker.io/tianon/backblaze-b2:3.6.0 \
 -c 'b2 authorize-account $B2_KEY_ID $B2_KEY_SECRET && b2 sync /work b2://$B2_BUCKET_NAME --skipNewer'
 ```
 
-## Periodically cleaning up the local filesystem
+### Periodically cleaning up the local filesystem
 
 As described in [How it works?](#how-it-works) above, when new media is uploaded to the Synapse homeserver, it's first stored locally and then also stored on the remote S3 storage.
 
 By default, we periodically ensure that all local files are uploaded to S3 and are then removed from the local filesystem. This is done automatically using:
 
 - the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script
-- .. invoked via the `matrix-synapse-s3-storage-provider-migrate.service` service
-- .. triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` timer, every day at 05:00
+- … invoked via the `matrix-synapse-s3-storage-provider-migrate.service` service
+- … triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` timer, every day at 05:00
 
-So.. you don't need to perform any maintenance yourself.
+So… you don't need to perform any maintenance yourself.
diff --git a/docs/configuring-playbook-synapse-simple-antispam.md b/docs/configuring-playbook-synapse-simple-antispam.md
index 96072b248..069b26d2f 100644
--- a/docs/configuring-playbook-synapse-simple-antispam.md
+++ b/docs/configuring-playbook-synapse-simple-antispam.md
@@ -2,7 +2,9 @@
 
 The playbook can install and configure [synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) for you.
 
-See that project's documentation to learn what it does and why it might be useful to you. In short, it lets you fight invite-spam by automatically blocking invitiations from a list of servers specified by you (blacklisting).
+It lets you fight invite-spam by automatically blocking invitiations from a list of servers specified by you (blacklisting).
+
+See the project's [documentation](https://github.com/t2bot/synapse-simple-antispam/blob/master/README.md) to learn what it does and why it might be useful to you.
 
 ## Adjusting the playbook configuration
 
diff --git a/docs/configuring-playbook-synapse-usage-exporter.md b/docs/configuring-playbook-synapse-usage-exporter.md
index 8a472f345..e07fc6d0d 100644
--- a/docs/configuring-playbook-synapse-usage-exporter.md
+++ b/docs/configuring-playbook-synapse-usage-exporter.md
@@ -1,4 +1,4 @@
-# Setting up synapse-usage-exporter (optional)
+# Enabling synapse-usage-exporter for Synapse usage statistics (optional)
 
 [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) allows you to export the usage statistics of a Synapse homeserver to this container service and for the collected metrics to later be scraped by Prometheus.
 
@@ -11,6 +11,12 @@ Enabling this service will automatically:
 - re-configure [Prometheus](./configuring-playbook-prometheus-grafana.md) (if Prometheus is enabled), to periodically scrape metrics from synapse-usage-exporter
 - add a new [Grafana](./configuring-playbook-prometheus-grafana.md) dashboard (if Grafana is enabled) containing Synapse usage statistics
 
+## Adjusting DNS records (optional)
+
+By default, this playbook installs synapse-usage-exporter on the `matrix.` subdomain, at the `/report-usage-stats/push` path (https://matrix.example.com/report-usage-stats/push). 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.
+
+If you wish to adjust it, see the section [below](#adjusting-the-synapse-usage-exporter-url-optional) for details about DNS configuration.
+
 ## Adjusting the playbook configuration
 
 To enable synapse-usage-exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
@@ -25,13 +31,11 @@ matrix_synapse_usage_exporter_enabled: true
 # matrix_synapse_usage_exporter_proxying_enabled: true
 ```
 
-### Adjusting the synapse-usage-exporter URL
-
-By default, this playbook installs synapse-usage-exporter on the `matrix.` subdomain, at the `/report-usage-stats/push` path (https://matrix.example.com/report-usage-stats/push). 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.
+### Adjusting the synapse-usage-exporter URL (optional)
 
 By tweaking the `matrix_synapse_usage_exporter_hostname` and `matrix_synapse_usage_exporter_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
-Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:
+Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Change the default hostname and path prefix
@@ -40,14 +44,19 @@ matrix_synapse_usage_exporter_hostname: sue.example.com
 matrix_synapse_usage_exporter_path_prefix: /
 ```
 
-## Adjusting DNS records
+If you've changed the default hostname, you may need to create a CNAME record for the synapse-usage-exporter domain (`sue.example.com`), which targets `matrix.example.com`.
 
-If you've changed the default hostname, **you may need to adjust your DNS** records to point the synapse-usage-exporter domain to the Matrix server.
-
-See [Configuring DNS](configuring-dns.md) for details about DNS changes.
-
-If you've decided to use the default hostname, you won't need to do any extra DNS configuration.
+When setting, replace `example.com` with your own.
 
 ## Installing
 
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the [installation](installing.md) command: `just install-all` or `just setup-all`
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
diff --git a/docs/configuring-playbook-synapse.md b/docs/configuring-playbook-synapse.md
index 1a214eaec..6b1ec9f3e 100644
--- a/docs/configuring-playbook-synapse.md
+++ b/docs/configuring-playbook-synapse.md
@@ -2,22 +2,9 @@
 
 By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, so that it works for the general case. If that's okay, you can skip this document.
 
-The playbook provides lots of customization variables you could use to change Synapse's settings.
+## Adjusting the playbook configuration
 
-Their defaults are defined in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml) and they ultimately end up in the generated `/matrix/synapse/config/homeserver.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2`](../roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2) template.
-
-**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes.
-
-Alternatively, **if there is no pre-defined variable** for a Synapse setting you wish to change:
-
-- you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Synapse's various settings that rarely get used.
-
-- or, you can **extend and override the default configuration** ([`homeserver.yaml.j2`](../roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2)) by making use of the `matrix_synapse_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml).
-
-- or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`). You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml).
-
-
-## Load balancing with workers
+### Load balancing with workers
 
 To have Synapse gracefully handle thousands of users, worker support should be enabled. It factors out some homeserver tasks and spreads the load of incoming client and server-to-server traffic between multiple processes. More information can be found in the [official Synapse workers documentation](https://github.com/element-hq/synapse/blob/master/docs/workers.md) and [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html).
 
@@ -31,7 +18,7 @@ matrix_synapse_workers_preset: one-of-each
 
 By default, this enables the `one-of-each` [worker preset](#worker-presets), but you may wish to use another preset or [control the number of worker instances](#controlling-the-number-of-worker-instances).
 
-### Worker presets
+#### Worker presets
 
 We support a few configuration presets (`matrix_synapse_workers_preset: one-of-each` being the default configuration right now):
 
@@ -41,7 +28,7 @@ We support a few configuration presets (`matrix_synapse_workers_preset: one-of-e
 
 These presets represent a few common configurations. There are many worker types which can be mixed and matched based on your needs.
 
-#### Generic workers
+##### Generic workers
 
 Previously, the playbook only supported the most basic type of load-balancing. We call it **generic load-balancing** below, because incoming HTTP requests are sent to a generic worker. Load-balancing was done based on the requestor's IP address. This is simple, but not necessarily optimal. If you're accessing your account from multiple IP addresses (e.g. your mobile phone being on a different network than your PC), these separate requests may potentially be routed to different workers, each of which would need to cache roughly the same data.
 
@@ -51,7 +38,7 @@ To use generic load-balancing, do not specify `matrix_synapse_workers_preset` to
 
 You may also consider [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each).
 
-#### Specialized workers
+##### Specialized workers
 
 The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requestor's IP adddress, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** - the access token (username) of the requestor and/or on the resource (room, etc.) being requested.
 
@@ -64,7 +51,7 @@ The playbook supports these **4 types** of specialized workers:
 
 To use specialized load-balancing, consider enabling the `specialized-workers` [worker preset](#worker-presets) and potentially [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each).
 
-#### Controlling the number of worker instances
+##### Controlling the number of worker instances
 
 If you'd like more customization power, you can start with one of the [worker presets](#worker-presets) and then tweak various `matrix_synapse_workers_*_count` variables manually.
 
@@ -72,21 +59,15 @@ To find what variables are available for you to override in your own `vars.yml`
 
 The only thing you **cannot** do is mix [generic workers](#generic-workers) and [specialized workers](#specialized-workers).
 
-#### Effect of enabling workers on the rest of your server
+##### Effect of enabling workers on the rest of your server
 
 When Synapse workers are enabled, the integrated [Postgres database is tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum number of Postgres connections are increased from `200` to `500`. If you need to decrease or increase the number of maximum Postgres connections further, use the `postgres_max_connections` variable.
 
 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.
 
-In case any problems occur, make sure to have a look at the [list of synapse issues about workers](https://github.com/matrix-org/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit 'matrix-*'`.
+In case any problems occur, make sure to have a look at the [list of synapse issues about workers](https://github.com/element-hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit 'matrix-*'`.
 
-
-## Synapse Admin
-
-Certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace, if you install [Synapse Admin](configuring-playbook-synapse-admin.md).
-
-
-## Synapse + OpenID Connect for Single-Sign-On
+### Synapse + OpenID Connect for Single-Sign-On
 
 💡 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.
 
@@ -98,13 +79,13 @@ For more detailed documentation on available options and how to setup keycloak,
 
 In case you encounter errors regarding the parsing of the variables, you can try to add `{% raw %}` and `{% endraw %}` blocks around them. For example ;
 
-```yml
+```yaml
 matrix_synapse_oidc_enabled: true
 
 matrix_synapse_oidc_providers:
   - idp_id: keycloak
     idp_name: "My KeyCloak server"
-    issuer: "https://url.ix/auth/realms/{realm_name}"
+    issuer: "https://url.ix/realms/{realm_name}"
     client_id: "matrix"
     client_secret: "{{ vault_synapse_keycloak }}"
     scopes: ["openid", "profile"]
@@ -117,8 +98,7 @@ matrix_synapse_oidc_providers:
     backchannel_logout_enabled: true # Optional
 ```
 
-
-## Customizing templates
+### Customizing templates
 
 [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**.
 
@@ -128,7 +108,7 @@ If template customization is enabled, the playbook will build a custom container
 
 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).
 
-To enable template customizations, use a configuration (`inventory/host_vars/matrix.example.com/vars.yml`) like this:
+To enable template customizations, add the following configuration to your `vars.yml` file (adapt to your needs):
 
 ```yaml
 # If you'd like to ensure that the customized image is built each time the playbook runs, enable this.
@@ -150,14 +130,43 @@ matrix_synapse_container_image_customizations_templates_git_repository_keyscan_h
 # If your git repository is public, do not define the private key (remove the variable).
 matrix_synapse_container_image_customizations_templates_git_repository_ssh_private_key: |
   -----BEGIN OPENSSH PRIVATE KEY-----
-  ....
+  …
   -----END OPENSSH PRIVATE KEY-----
 ```
 
 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.
 
+### Extending the configuration
 
-## Monitoring Synapse Metrics with Prometheus and Grafana
+There are some additional things you may wish to configure about the server.
+
+Take a look at:
+
+- `roles/custom/matrix-synapse/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+- `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
+
+## Installing
+
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
+
+## Usage
+
+### Synapse Admin
+
+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.
+
+The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md).
+
+### Monitoring Synapse Metrics with Prometheus and Grafana
 
 This playbook allows you to enable Synapse metrics, which can provide insight into the performance and activity of Synapse.
 
diff --git a/docs/configuring-playbook-telemetry.md b/docs/configuring-playbook-telemetry.md
index 37ad76b0b..aa26fb734 100644
--- a/docs/configuring-playbook-telemetry.md
+++ b/docs/configuring-playbook-telemetry.md
@@ -4,8 +4,7 @@ By default, this playbook configures your Matrix homeserver to not send any tele
 
 The [matrix.org](https://matrix.org) team would really appreciate it if you could help the project out by reporting usage statistics from your homeserver. Enabling usage statistics helps track the growth of the Matrix community, and helps to make Matrix a success.
 
-
-## Enabling Telemetry
+## Adjusting the playbook configuration
 
 If you'd like to **help by enabling submission of general usage statistics** for your homeserver, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
@@ -15,9 +14,8 @@ matrix_synapse_report_stats: true # for synapse
 matrix_dendrite_report_stats: true # for dendrite
 ```
 
-
 ## Usage statistics being submitted
 
 When enabled, your homeserver will regularly upload a few dozen statistics about your server. This data includes your homeserver's domain, the total number of users, the number of active users, the total number of rooms, and the number of messages sent per day on your homeserver.
 
-See [Synapse's documentation](https://github.com/element-hq/synapse/blob/develop/docs/usage/administration/monitoring/reporting_homeserver_usage_statistics.md#available-statistics) or [Dendrite's documentation](https://github.com/matrix-org/dendrite/blob/main/docs/FAQ.md#what-is-being-reported-when-enabling-phone-home-statistics) for the full list of statistics that are reported.
+See [Synapse's documentation](https://github.com/element-hq/synapse/blob/develop/docs/usage/administration/monitoring/reporting_homeserver_usage_statistics.md#available-statistics) or [Dendrite's documentation](https://github.com/element-hq/dendrite/blob/main/docs/FAQ.md#what-is-being-reported-when-enabling-phone-home-statistics) for the full list of statistics that are reported.
diff --git a/docs/configuring-playbook-traefik.md b/docs/configuring-playbook-traefik.md
index de860cef8..66d6b1aee 100644
--- a/docs/configuring-playbook-traefik.md
+++ b/docs/configuring-playbook-traefik.md
@@ -1,10 +1,9 @@
-# Configure Traefik (optional, advanced)
+# Configuring the Traefik reverse-proxy (optional, advanced)
 
 By default, this playbook installs and manages a [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered by the [ansible-role-traefik](https://github.com/mother-of-all-self-hosting/ansible-role-traefik) Ansible role.
 
 This Ansible role support various configuration options. Feel free to consult its `default/main.yml` variables file.
 
-
 ## Adjusting SSL certificate retrieval
 
 See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page.
@@ -35,7 +34,7 @@ traefik_dashboard_basicauth_user: YOUR_USERNAME_HERE
 traefik_dashboard_basicauth_password: YOUR_PASSWORD_HERE
 ```
 
-**WARNING**: Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts.
+⚠️ **Warning**: Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts.
 
 ## Additional configuration
 
@@ -89,7 +88,6 @@ traefik_configuration_extension_yaml: |
     insecureSkipVerify: true
 ```
 
-
 Next, you have to add a new dynamic configuration file for Traefik that contains the actual information of the server using the `aux_file_definitions` variable. In this example, we will terminate SSL at the Traefik instance and connect to the other server via HTTPS. Traefik will now take care of managing the certificates.
 
 ```yaml
@@ -136,8 +134,7 @@ Changing the `url` to one with an `http://` prefix would allow to connect to the
 
 With these changes, all TCP traffic will be reverse-proxied to the target system.
 
-**WARNING**: This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```.
-
+⚠️ **Warning**: This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```.
 
 ## Traefik behind a `proxy_protocol` reverse-proxy
 
diff --git a/docs/configuring-playbook-turn.md b/docs/configuring-playbook-turn.md
index 0a85fd129..a0915312d 100644
--- a/docs/configuring-playbook-turn.md
+++ b/docs/configuring-playbook-turn.md
@@ -1,63 +1,53 @@
-# TURN server
+# Configuring a TURN server (optional, advanced)
 
-The playbook installs a [Coturn](https://github.com/coturn/coturn) TURN server by default, so that clients can make audio/video calls even from [NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed networks.
+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.
 
-By default, the Synapse chat server is configured, so that it points to the Coturn TURN server installed by the playbook.
+If you'd like to stop the playbook installing the server, see the section [below](#disabling-coturn) to check the configuration for disabling it.
 
+## Adjusting the playbook configuration
 
-## Disabling Coturn
+### Define public IP manually (optional)
 
-If, for some reason, you'd like to prevent the playbook from installing Coturn, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+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.
 
-```yaml
-matrix_coturn_enabled: false
-```
-
-In that case, Synapse would not point to any Coturn servers and audio/video call functionality may fail.
-
-## Manually defining your public IP
-
-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.
-
-If you'd rather use a local IP for `ansible_host`, make sure to set up `matrix_coturn_turn_external_ip_address` replacing `YOUR_PUBLIC_IP` with the pubic IP used by the server.
+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.
 
 ```yaml
 matrix_coturn_turn_external_ip_address: "YOUR_PUBLIC_IP"
 ```
 
-If you'd like to rely on external IP address auto-detection (not recommended unless you need it), set `matrix_coturn_turn_external_ip_address` to an empty value. 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 `matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable.
+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 `matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable.
 
-If your server has multiple external IP addresses, the Coturn role offers a different variable for specifying them:
+If your server has multiple external IP addresses, the coturn role offers a different variable for specifying them:
 
 ```yaml
 # Note: matrix_coturn_turn_external_ip_addresses is different than matrix_coturn_turn_external_ip_address
 matrix_coturn_turn_external_ip_addresses: ['1.2.3.4', '4.5.6.7']
 ```
 
-## Changing the authentication mechanism
+### Change the authentication mechanism (optional)
 
 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.
 
-To do so, add this override to your configuration:
+To do so, add the following configuration to your `vars.yml` file:
 
-```yml
+```yaml
 matrix_coturn_authentication_method: lt-cred-mech
 ```
 
-Regardless of the selected authentication method, the playbook generates secrets automatically and passes them to the homeserver and Coturn.
+Regardless of the selected authentication method, the playbook generates secrets automatically and passes them to the homeserver and coturn.
 
-If you're using [Jitsi](./configuring-playbook-jitsi.md), note that switching to `lt-cred-mech` will remove the integration between Jitsi and your own Coturn server, because Jitsi only seems to support the `auth-secret` authentication method.
+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.
 
+### Use your own external coturn server (optional)
 
-## Using your own external Coturn server
-
-If you'd like to use another TURN server (be it Coturn or some other one), you can configure the playbook like this:
+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.
 
 ```yaml
-# Disable integrated Coturn server
+# Disable integrated coturn server
 matrix_coturn_enabled: false
 
-# Point Synapse to your other Coturn server
+# Point Synapse to your other coturn server
 matrix_synapse_turn_uris:
 - turns:HOSTNAME_OR_IP?transport=udp
 - turns:HOSTNAME_OR_IP?transport=tcp
@@ -65,13 +55,42 @@ matrix_synapse_turn_uris:
 - turn:HOSTNAME_OR_IP?transport=tcp
 ```
 
-If you have or want to enable [Jitsi](configuring-playbook-jitsi.md), you might want to enable the TURN server there too. If you do not do it, Jitsi will fall back to an upstream service.
+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.
 
 ```yaml
 jitsi_web_stun_servers:
 - stun:HOSTNAME_OR_IP:PORT
 ```
-You can put multiple host/port combinations if you like.
 
-## Further variables and configuration options
-To see all the available configuration options, check roles/custom/matrix-coturn/defaults/main.yml
+You can put multiple host/port combinations if you'd like to.
+
+### Extending the configuration
+
+There are some additional things you may wish to configure about the TURN server.
+
+Take a look at:
+
+- `roles/custom/matrix-coturn/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+
+## Disabling coturn
+
+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:
+
+```yaml
+matrix_coturn_enabled: false
+```
+
+In that case, Synapse would not point to any coturn servers and audio/video call functionality may fail.
+
+## Installing
+
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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.
diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md
index e0566c86b..4b62c378b 100644
--- a/docs/configuring-playbook-user-verification-service.md
+++ b/docs/configuring-playbook-user-verification-service.md
@@ -1,109 +1,125 @@
 # Setting up Matrix User Verification Service (optional)
 
-**[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (hereafter: UVS) can only be installed after Matrix services are installed and running.** If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) flow and come back here later.
+The playbook can install and configure [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (hereafter: UVS) for you.
 
-Currently, the main purpose of this role is to allow Jitsi to authenticate Matrix users and check if they are authorized to join a conference. Please refer to the documentation of the [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) to understand how it works.
+See the project's [documentation](https://github.com/matrix-org/matrix-user-verification-service/blob/master/README.md) to learn what it does and why it might be useful to you.
 
-**Note**: enabling Matrix User Verification Service, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled.
+Currently, the main purpose of this role is to allow Jitsi to authenticate Matrix users and check if they are authorized to join a conference. If the Jitsi server is also configured by this playbook, all plugging of variables and secrets is handled in `group_vars/matrix_servers`.
 
-If the Jitsi server is also configured by this playbook, all plugging of variables and secrets is handled in `group_vars/matrix_servers`.
-
-__Some general concepts of UVS may be helpful to understand the rest, so here they are:__
+## What does it do?
 
 UVS can be used to verify two claims:
 
 * (A) Whether a given OpenID token is valid for a given server and
 * (B) whether a user is member of a given room and the corresponding PowerLevel
 
-Verifying an OpenID token ID done by finding the corresponding Homeserver via  '.well-known/matrix/server' for the given domain. The configured `matrix_user_verification_service_uvs_homeserver_url` does **not** factor into this. By default, this playbook only checks against `matrix_server_fqn_matrix`. Therefore, the request will be made against the public openid API for `matrix_server_fqn_matrix`.
+Verifying an OpenID token ID done by finding the corresponding Homeserver via `/.well-known/matrix/server` for the given domain. The configured `matrix_user_verification_service_uvs_homeserver_url` does **not** factor into this. By default, this playbook only checks against `matrix_server_fqn_matrix`. Therefore, the request will be made against the public `openid` API for `matrix_server_fqn_matrix`.
 
 Verifying RoomMembership and PowerLevel is done against `matrix_user_verification_service_uvs_homeserver_url` which is by default done via the docker network. UVS will verify the validity of the token beforehand though.
 
 ## Prerequisites
 
-In order to use UVS, an admin token for the configured homeserver must be supplied. For now this means configuring Synapse and creating the token before installing UVS.
+### Open Matrix Federation port
 
-## Enable
+Enabling the UVS service will automatically reconfigure your Synapse homeserver to expose the `openid` API endpoints on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. If you enable the component, make sure that the port is accessible.
 
-To enable Matrix User Verification Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+### Install Matrix services
+
+UVS can only be installed after Matrix services are installed and running. If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) and come back here later.
+
+### Register a dedicated Matrix user (optional, recommended)
+
+We recommend that you create a dedicated Matrix user for uvs (`uvs` is a good username). **Because UVS requires an access token as an admin user, that user needs to be an admin.**
+
+Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`.
+
+You can use the playbook to [register a new user](registering-users.md):
+
+```sh
+ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=uvs password=PASSWORD_FOR_THE_USER admin=yes' --tags=register-user
+```
+
+### Obtain an access token
+
+UVS requires an access token as an admin user to verify RoomMembership and PowerLevel against `matrix_user_verification_service_uvs_homeserver_url`. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md).
+
+⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.
+
+## Adjusting the playbook configuration
+
+To enable UVS, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token).
 
 ```yaml
 matrix_user_verification_service_enabled: true
+
+matrix_user_verification_service_uvs_access_token: "ACCESS_TOKEN_HERE"
 ```
 
-## Configuration
-
-The only required configuration variable is `matrix_user_verification_service_uvs_access_token` (see below).
-
-For a list of all configuration options see the role defaults [`roles/matrix-user-verification-service/defaults/main.yml`](../roles/custom/matrix-user-verification-service/defaults/main.yml). But be aware of all the plugging happening in `group_vars/matrix_servers`.
+Check the role's [defaults/main.yml](../roles/custom/matrix-user-verification-service/defaults/main.yml) for the full list of variables that you could override. Note that all the plugging happening in `group_vars/matrix_servers`.
 
 In the default configuration, the UVS Server is only reachable via the docker network, which is fine if e.g. Jitsi is also running in a container on the host. However, it is possible to expose UVS via setting `matrix_user_verification_service_container_http_host_bind_port`.
 
-### Access token
-
-The Synapse Access Token is used to verify RoomMembership and PowerLevel against `matrix_user_verification_service_uvs_homeserver_url`.
-
-We recommend that you create a dedicated Matrix user for uvs (`uvs` is a good username). Follow our [Registering users](registering-users.md) guide to register a user with administration privileges.
-
-You are required to specify an access token (belonging to this new user) for UVS to work. To get an access token for the UVS user, you can follow the documentation on [how to do obtain an access token](obtaining-access-tokens.md).
-
-**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**
-
-```yaml
-matrix_user_verification_service_uvs_access_token: "YOUR ACCESS TOKEN HERE"
-```
-
-### (Optional) Custom Auth Token
+### Custom Auth Token (optional)
 
 It is possible to set an API Auth Token to restrict access to the UVS. If this is enabled, anyone making a request to UVS must provide it via the header "Authorization: Bearer TOKEN"
 
 By default, the token will be derived from `matrix_homeserver_generic_secret_key` in `group_vars/matrix_servers`.
 
-To set your own Token, simply put the following in your host_vars.
+To set your own Token, add the following configuration to your `vars.yml` file:
 
 ```yaml
 matrix_user_verification_service_uvs_auth_token: "TOKEN"
 ```
 
-In case Jitsi is also managed by this playbook and 'matrix' authentication in Jitsi is enabled, this collection will automatically configure Jitsi to use the configured auth token.
+If a Jitsi instance is also managed by this playbook and [`matrix` authentication](configuring-playbook-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix) is enabled there, this collection will automatically configure Jitsi to use the configured auth token.
 
-###  (Optional) Disable Auth
-Authorization is enabled by default. To disable set
+### Disable Auth (optional)
+
+Authorization is enabled by default. To disable it, add the following configuration to your `vars.yml` file:
 
 ```yaml
 matrix_user_verification_service_uvs_require_auth: false
 ```
 
-in your host_vars.
+### Federation (optional)
 
-### (Optional) Federation
-
-In theory (however currently untested), UVS can handle federation. Simply set:
+In theory (however currently untested), UVS can handle federation. To enable it, add the following configuration to your `vars.yml` file:
 
 ```yaml
 matrix_user_verification_service_uvs_pin_openid_verify_server_name: false
 ```
 
-in your host_vars.
-
 This will instruct UVS to verify the OpenID token against any domain given in a request. Homeserver discovery is done via '.well-known/matrix/server' of the given domain.
 
+### Controlling the logging level (optional)
+
+To specify the logging level, add the following configuration to your `vars.yml` file:
+
+```yaml
+UVS_LOG_LEVEL: info
+```
+
+Replace `info` with one of the choices (they can be checked [here](https://github.com/winstonjs/winston#logging-levels)) to control the verbosity of the logs generated.
+
+If you have issues with a service, and are requesting support, the higher levels of logging will generally be more helpful.
+
 ## Installing
 
-After these variables have been set, run the [installation](installing.md) command to restart UVS:
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
 
-```
-ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-user-verification-service,start
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
 ```
 
-## Logging
+The shortcut commands with the [`just` program](just.md) are also available: `just install-service matrix-user-verification-service` or `just setup-all`
 
-The configuration variable `UVS_LOG_LEVEL` can be set to:
-- warning
-- info
-- debug
+`just install-service matrix-user-verification-service` is useful for maintaining your setup quickly 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 `just setup-all` runs the `ensure-matrix-users-created` tag too.
+
+## Troubleshooting
+
+### TLS Certificate Checking
 
-## TLS Certificate Checking
 If the Matrix Homeserver does not provide a valid TLS certificate, UVS will fail with the following error message:
 
 > message: 'No response received: [object Object]',
diff --git a/docs/configuring-playbook.md b/docs/configuring-playbook.md
index f85201e26..98d182122 100644
--- a/docs/configuring-playbook.md
+++ b/docs/configuring-playbook.md
@@ -1,12 +1,8 @@
-# Configuring the Ansible playbook
+# Configuring the playbook
 
-To configure the playbook, you need to have done the following things:
+<sup>[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md)</sup>
 
-- have a server where Matrix services will run
-- [configured your DNS records](configuring-dns.md)
-- [retrieved the playbook's source code](getting-the-playbook.md) to your computer
-
-You can then follow these steps inside the playbook directory:
+If you've configured your DNS records and retrieved the playbook's source code to your computer, you can start configuring the playbook. To do so, follow these steps inside the playbook directory:
 
 1. create a directory to hold your configuration (`mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your "base domain")
 
@@ -26,212 +22,236 @@ For a basic Matrix installation, that's all you need.
 
 For a more custom setup, see the [Other configuration options](#other-configuration-options) below.
 
-When you're done with all the configuration you'd like to do, continue with [Installing](installing.md).
-
+[▶️](installing.md) When you're done with all the configuration you'd like to do, continue with [Installing](installing.md).
 
 ## Other configuration options
 
-### Additional useful services
-
-- [Setting up the Dimension integration manager](configuring-playbook-dimension.md) (optional; [unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299); after [installing](installing.md))
-
-- [Setting up the Jitsi video-conferencing platform](configuring-playbook-jitsi.md) (optional)
-
-- [Setting up Etherpad](configuring-playbook-etherpad.md) (optional)
-
-- [Setting up Dynamic DNS](configuring-playbook-dynamic-dns.md) (optional)
-
-- [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md) (optional)
-
-- [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md) (optional)
+**Note**: some of the roles like one for integrating Etherpad or Jitsi are managed by their own repositories, and the configuration files for them cannot be found locally (in `roles/galaxy`) until those roles are fetched from the upstream projects. Check [requirements.yml](../requirements.yml) for the URLs of those roles.
 
 ### Core service adjustments
 
 - Homeserver configuration:
-  - [Configuring Synapse](configuring-playbook-synapse.md), if you're going with the default/recommended homeserver implementation (optional)
+  - [Configuring Synapse](configuring-playbook-synapse.md), if you're going with the default/recommended homeserver implementation
 
-  - [Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation (optional)
+  - [Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation
 
-  - [Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation (optional)
+  - [Configuring Conduwuit](configuring-playbook-conduwuit.md), if you've switched to the [Conduwuit](https://conduwuit.puppyirl.gay/) homeserver implementation
 
-- [Configuring Element](configuring-playbook-client-element.md) (optional)
+  - [Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation
 
-- [Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md) (optional)
+- Server components:
+  - [Using an external PostgreSQL server](configuring-playbook-external-postgres.md)
 
-- [Storing Matrix media files on Amazon S3](configuring-playbook-s3.md) (optional)
+  - [Configuring a TURN server](configuring-playbook-turn.md) (advanced)
 
-- [Using an external PostgreSQL server](configuring-playbook-external-postgres.md) (optional)
+  - [Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) (advanced)
 
-- [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) (optional, advanced)
+  - [Using your own webserver, instead of this playbook's Traefik reverse-proxy](configuring-playbook-own-webserver.md) (advanced)
 
-- [Serving your base domain using this playbook's nginx server](configuring-playbook-base-domain-serving.md) (optional)
+  - [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) (advanced)
 
-- [Configure the Traefik reverse-proxy](configuring-playbook-traefik.md) (optional, advanced)
+  - [Adjusting email-sending settings](configuring-playbook-email.md)
 
-- [Using your own webserver, instead of this playbook's default reverse-proxy](configuring-playbook-own-webserver.md) (optional, advanced)
+  - [Setting up ma1sd Identity Server](configuring-playbook-ma1sd.md)
 
-- [Adjusting TURN server configuration](configuring-playbook-turn.md) (optional, advanced)
+  - [Setting up Dynamic DNS](configuring-playbook-dynamic-dns.md)
 
+- Server connectivity:
+  - [Enabling Telemetry for your Matrix server](configuring-playbook-telemetry.md)
 
-### Server connectivity
+  - [Controlling Matrix federation](configuring-playbook-federation.md)
 
-- [Enabling Telemetry for your Matrix server](configuring-playbook-telemetry.md) (optional)
+### Clients
 
-- [Controlling Matrix federation](configuring-playbook-federation.md) (optional)
+Web clients for Matrix that you can host on your own domains.
 
-- [Adjusting email-sending settings](configuring-playbook-email.md) (optional)
+- [Configuring Element Web](configuring-playbook-client-element-web.md), if you're going with the default/recommended client
 
-- [Setting up Hydrogen](configuring-playbook-client-hydrogen.md) - a new lightweight Matrix client with legacy and mobile browser support (optional)
+- [Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a lightweight Matrix client with legacy and mobile browser support
 
-- [Setting up Cinny](configuring-playbook-client-cinny.md) - a web client focusing primarily on simple, elegant and secure interface (optional)
-
-- [Setting up SchildiChat](configuring-playbook-client-schildichat.md) - a web client based on [Element](https://element.io/) with some extras and tweaks (optional)
+- [Setting up Cinny](configuring-playbook-client-cinny.md), if you've enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing primarily on simple, elegant and secure interface
 
+- [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
 
 ### Authentication and user-related
 
-- [Setting up Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (Next-generation auth for Matrix, based on OAuth 2.0/OIDC) (optional)
+Extend and modify how users are authenticated on your homeserver.
 
-- [Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) (optional)
+- [Setting up Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (Next-generation auth for Matrix, based on OAuth 2.0/OIDC)
 
-- [Setting up an ma1sd Identity Server](configuring-playbook-ma1sd.md) (optional)
+- [Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)
 
-- [Setting up Synapse Admin](configuring-playbook-synapse-admin.md) (optional)
+- [Setting up Synapse Admin](configuring-playbook-synapse-admin.md)
 
-- [Setting up matrix-registration](configuring-playbook-matrix-registration.md) (optional)
+- [Setting up matrix-registration](configuring-playbook-matrix-registration.md)
 
-- [Setting up the REST authentication password provider module](configuring-playbook-rest-auth.md) (optional, advanced)
+- [Setting up the REST authentication password provider module](configuring-playbook-rest-auth.md) (advanced)
 
-- [Setting up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) (optional, advanced)
+- [Setting up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) (advanced)
 
-- [Setting up the LDAP password provider module](configuring-playbook-ldap-auth.md) (optional, advanced)
+- [Setting up the LDAP authentication password provider module](configuring-playbook-ldap-auth.md) (advanced)
 
-- [Setting up the ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) (optional, advanced)
+- [Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) (advanced)
 
-- [Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-antispam.md) (optional, advanced)
+- [Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)
 
-- [Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) (optional, advanced)
+- [Setting up Matrix User Verification Service](configuring-playbook-user-verification-service.md) (advanced)
 
-- [Setting up Matrix User Verification Service](configuring-playbook-user-verification-service.md) (optional, advanced)
+### File Storage
 
-- [Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-pantalaimon.md) (optional, advanced)
+Use alternative file storage to the default `media_store` folder.
 
+- [Storing Matrix media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)
+
+- [Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md)
+
+- [Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md)
 
 ### Bridging other networks
 
-- [Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md) (optional)
+Bridges can be used to connect your Matrix installation with third-party communication networks.
 
-- [Setting up Mautrix Telegram bridging](configuring-playbook-bridge-mautrix-telegram.md) (optional)
+- [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) - a common guide for configuring mautrix bridges
 
-- [Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md) (optional)
+- [Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md)
 
-- [Setting up Mautrix Google Messages bridging](configuring-playbook-bridge-mautrix-gmessages.md) (optional)
+- [Setting up Mautrix Telegram bridging](configuring-playbook-bridge-mautrix-telegram.md)
 
-- [Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-mautrix-whatsapp.md) (optional)
+- [Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md)
 
-- [Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md) (optional)
+- [Setting up Mautrix Google Messages bridging](configuring-playbook-bridge-mautrix-gmessages.md)
 
-- [Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md) (optional)
+- [Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-mautrix-whatsapp.md)
 
-- ~~[Setting up Mautrix Facebook bridging](configuring-playbook-bridge-mautrix-facebook.md)~~ - consider bridging to Facebook/Messenger using the new [mautrix-meta-messenger](./configuring-playbook-bridge-mautrix-meta-messenger.md) bridge (optional)
+- [Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)
 
-- [Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-mautrix-hangouts.md) (optional)
+- [Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)
 
-- [Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-mautrix-googlechat.md) (optional)
+- [Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-mautrix-googlechat.md)
 
-- ~~[Setting up Mautrix Instagram bridging](configuring-playbook-bridge-mautrix-instagram.md)~~ - consider bridging to Instagram using the new [mautrix-meta-instagram](./configuring-playbook-bridge-mautrix-meta-instagram.md) bridge (optional)
+- [Setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md)
 
-- [Setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md) (optional)
+- [Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-signal.md)
 
-- [Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-signal.md) (optional)
+- [Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](configuring-playbook-bridge-mautrix-wsproxy.md)
 
-- [Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](configuring-playbook-bridge-mautrix-wsproxy.md) (optional)
+- [Setting up Appservice IRC bridging](configuring-playbook-bridge-appservice-irc.md)
 
-- [Setting up Appservice IRC bridging](configuring-playbook-bridge-appservice-irc.md) (optional)
+- [Setting up Appservice Discord bridging](configuring-playbook-bridge-appservice-discord.md)
 
-- [Setting up Appservice Discord bridging](configuring-playbook-bridge-appservice-discord.md) (optional)
+- [Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md)
 
-- [Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md) (optional)
+- [Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-appservice-kakaotalk.md)
 
-- [Setting up Appservice Webhooks bridging](configuring-playbook-bridge-appservice-webhooks.md) (optional)
+- [Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-linkedin.md)
 
-- [Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-appservice-kakaotalk.md) (optional)
+- [Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) - a bridge between Matrix and multiple project management services, such as [GitHub](https://github.com), [GitLab](https://about.gitlab.com) and [JIRA](https://www.atlassian.com/software/jira).
 
-- [Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-linkedin.md) (optional)
+- [Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md)
 
-- [Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) - a bridge between Matrix and multiple project management services, such as [GitHub](https://github.com), [GitLab](https://about.gitlab.com) and [JIRA](https://www.atlassian.com/software/jira). (optional)
+- [Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-puppet-instagram.md)
 
-- ~~[Setting up MX Puppet Skype bridging](configuring-playbook-bridge-mx-puppet-skype.md)~~ (optional) - this component has been broken for a long time, so it has been removed from the playbook. Consider [Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md)
+- [Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md)
 
-- [Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md) (optional)
+- [Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-puppet-discord.md)
 
-- [Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-puppet-instagram.md) (optional)
+- [Setting up MX Puppet GroupMe bridging](configuring-playbook-bridge-mx-puppet-groupme.md)
 
-- [Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md) (optional)
+- [Setting up MX Puppet Steam bridging](configuring-playbook-bridge-mx-puppet-steam.md)
 
-- [Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-puppet-discord.md) (optional)
+- [Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md)
 
-- [Setting up MX Puppet GroupMe bridging](configuring-playbook-bridge-mx-puppet-groupme.md) (optional)
+- [Setting up Email2Matrix](configuring-playbook-email2matrix.md)
 
-- [Setting up MX Puppet Steam bridging](configuring-playbook-bridge-mx-puppet-steam.md) (optional)
+- [Setting up Postmoogle email bridging](configuring-playbook-bridge-postmoogle.md)
 
-- [Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md) (optional)
+- [Setting up Matrix SMS bridging](configuring-playbook-bridge-matrix-bridge-sms.md)
 
-- [Setting up Email2Matrix](configuring-playbook-email2matrix.md) (optional)
-
-- [Setting up Postmoogle email bridging](configuring-playbook-bot-postmoogle.md) (optional)
-
-- [Setting up Matrix SMS bridging](configuring-playbook-bridge-matrix-bridge-sms.md) (optional)
-
-- [Setting up Heisenbridge bouncer-style IRC bridging](configuring-playbook-bridge-heisenbridge.md) (optional)
-
-- [Setting up WeChat bridging](configuring-playbook-bridge-wechat.md) (optional)
+- [Setting up Heisenbridge bouncer-style IRC bridging](configuring-playbook-bridge-heisenbridge.md)
 
+- [Setting up WeChat bridging](configuring-playbook-bridge-wechat.md)
 
 ### Bots
 
-- [Setting up baibot](configuring-playbook-bot-baibot.md) - a bot through which you can talk to various [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) services ([OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) and [others](https://github.com/etkecc/baibot/blob/main/docs/providers.md)) (optional)
+Bots provide various additional functionality to your installation.
 
-- [Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) - a bot through which you can talk to the [ChatGPT](https://openai.com/blog/chatgpt/) model (optional)
+- [Setting up baibot](configuring-playbook-bot-baibot.md) - a bot through which you can talk to various [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) services ([OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) and [others](https://github.com/etkecc/baibot/blob/main/docs/providers.md))
 
-- [Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md) - a bot to remind you about stuff (optional)
+- [Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md) - a bot to remind you about stuff
 
-- [Setting up matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) - a bot to create and manage registration tokens to invite users (optional)
+- [Setting up matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) - a bot to create and manage registration tokens to invite users
 
-- [Setting up maubot](configuring-playbook-bot-maubot.md) - a plugin-based Matrix bot system (optional)
+- [Setting up maubot](configuring-playbook-bot-maubot.md) - a plugin-based Matrix bot system
 
-- [Setting up honoroit](configuring-playbook-bot-honoroit.md) - a helpdesk bot (optional)
+- [Setting up Honoroit](configuring-playbook-bot-honoroit.md) - a helpdesk bot
 
-- [Setting up Go-NEB](configuring-playbook-bot-go-neb.md) - an extensible multifunctional bot (optional)
+- [Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) - a moderation tool/bot
 
-- [Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) - a moderation tool/bot (optional)
+- [Setting up Draupnir](configuring-playbook-bot-draupnir.md) - a moderation tool/bot, forked from Mjolnir and maintained by its former leader developer
 
-- [Setting up Draupnir](configuring-playbook-bot-draupnir.md) - a moderation tool/bot, forked from Mjolnir and maintained by its former leader developer (optional)
+- [Setting up Draupnir for all/D4A](configuring-playbook-appservice-draupnir-for-all.md) - like the [Draupnir bot](configuring-playbook-bot-draupnir.md) mentioned above, but running in appservice mode and supporting multiple instances
 
-- [Setting up Draupnir for all](configuring-playbook-appservice-draupnir-for-all.md) - like the [Draupnir bot](configuring-playbook-bot-draupnir.md) mentioned above, but running in appservice mode and supporting multiple instances (optional)
+- [Setting up Buscarron](configuring-playbook-bot-buscarron.md) - a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room
 
-- [Setting up Buscarron](configuring-playbook-bot-buscarron.md) - a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room (optional)
+### Administration
 
+Services that help you in administrating and monitoring your Matrix installation.
 
-### Backups
+- [Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)
 
-- [Setting up BorgBackup](configuring-playbook-backup-borg.md) - a full Matrix server backup solution, including the Postgres database (optional)
+- [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)
 
-- [Setting up postgres backup](configuring-playbook-postgres-backup.md) - a Postgres-database backup solution (note: does not include other files) (optional)
+- [Enabling metrics and graphs for NginX logs](configuring-playbook-prometheus-nginxlog.md)
 
+- [Setting up the rageshake bug report server](configuring-playbook-rageshake.md)
+
+- [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)
+
+- Backups:
+  - [Setting up BorgBackup](configuring-playbook-backup-borg.md) - a full Matrix server backup solution, including the Postgres database
+
+  - [Setting up postgres backup](configuring-playbook-postgres-backup.md) - a Postgres-database backup solution (note: does not include other files)
 
 ### Other specialized services
 
-- [Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers (optional)
+Various services that don't fit any other categories.
 
-- [Setting up the Sliding Sync proxy](configuring-playbook-sliding-sync-proxy.md) for clients which require Sliding Sync support (like Element X) (optional)
+- [Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md)
 
-- [Setting up the Sygnal push gateway](configuring-playbook-sygnal.md) (optional)
+- [Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers
 
-- [Setting up the ntfy push notifications server](configuring-playbook-ntfy.md) (optional)
+- [Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)
 
-- [Setting up a Cactus Comments server](configuring-playbook-cactus-comments.md) - a federated comment system built on Matrix (optional)
+- [Setting up Etherpad](configuring-playbook-etherpad.md)
 
-- [Setting up the rageshake bug report server](configuring-playbook-rageshake.md) (optional)
+- [Setting up the Jitsi video-conferencing platform](configuring-playbook-jitsi.md)
 
-- [Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md) (optional)
+- [Setting up Cactus Comments](configuring-playbook-cactus-comments.md) - a federated comment system built on Matrix
+
+- [Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-pantalaimon.md) (advanced)
+
+- [Setting up the Sygnal push gateway](configuring-playbook-sygnal.md)
+
+- [Setting up the ntfy push notifications server](configuring-playbook-ntfy.md)
+
+### Deprecated / unmaintained / removed services
+
+**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.
+
+- [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)
+
+- [Setting up Appservice Webhooks bridging](configuring-playbook-bridge-appservice-webhooks.md) (deprecated; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))
+
+- [Setting up the Dimension integration manager](configuring-playbook-dimension.md) ([unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299); after [installing](installing.md))
+
+- [Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))
+
+- [Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) (unmaintained; the bridge's author suggests taking a look at [baibot](https://github.com/etkecc/baibot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bot-baibot.md))
+
+- [Setting up Mautrix Facebook bridging](configuring-playbook-bridge-mautrix-facebook.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-messenger](configuring-playbook-bridge-mautrix-meta-messenger.md))
+
+- [Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-mautrix-hangouts.md) (deprecated in favor of the Google Chat bridge with [mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md))
+
+- [Setting up Mautrix Instagram bridging](configuring-playbook-bridge-mautrix-instagram.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-instagram](configuring-playbook-bridge-mautrix-meta-instagram.md))
+
+- [Setting up MX Puppet Skype bridging](configuring-playbook-bridge-mx-puppet-skype.md) (removed; this component has been broken for a long time, so it has been removed from the playbook. Consider [setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md))
diff --git a/docs/configuring-well-known.md b/docs/configuring-well-known.md
index e453814d9..9c8e9bef8 100644
--- a/docs/configuring-well-known.md
+++ b/docs/configuring-well-known.md
@@ -1,49 +1,46 @@
 # Configuring Service Discovery via .well-known
 
-Service discovery is a way for the Matrix network to discover where a Matrix server is.
+This documentation page explains how to configure Service discovery via `/.well-known/` files. Service discovery is a way for the Matrix network to discover where a Matrix server is.
 
-There are 2 types of well-known service discovery that Matrix makes use of:
+## Types of well-known service discovery mechanism
 
-- (important) **Federation Server discovery** (`/.well-known/matrix/server`) -- assists other servers in the Matrix network with finding your server. Without a proper configuration, your server will effectively not be part of the Matrix network. Learn more in [Introduction to Federation Server Discovery](#introduction-to-federation-server-discovery)
+There are 3 types of well-known service discovery mechanism that Matrix makes use of:
 
-- (not that important) **Client Server discovery** (`/.well-known/matrix/client`) -- assists programs that you use to connect to your server (e.g. Element), so that they can make it more convenient for you by automatically configuring the "Homeserver URL" and "Identity Server URL" addresses. Learn more in [Introduction to Client Server Discovery](#introduction-to-client-server-discovery)
+- (important) **Federation Server discovery** (`/.well-known/matrix/server`) -- assists other servers in the Matrix network with finding your server. With the default playbook configuration specified on the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), this is necessary for federation to work. Without a proper configuration, your server will effectively not be part of the Matrix network.
 
+- (less important) **Client Server discovery** (`/.well-known/matrix/client`) -- assists programs that you use to connect to your server (e.g. Element Web), so that they can make it more convenient for you by automatically configuring the "Homeserver URL" and "Identity Server URL" addresses.
 
-## Introduction to Federation Server Discovery
+- (optional) **Support service discovery** (`/.well-known/matrix/support`) -- returns server admin contact and support page of the domain.
 
-All services created by this playbook are meant to be installed on their own server (such as `matrix.example.com`).
+### Federation Server Discovery
 
-As [per the Server-Server specification](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), to use a Matrix user identifier like `@<username>:example.com` while hosting services on a subdomain like `matrix.example.com`, the Matrix network needs to be instructed of such delegation/redirection.
+All services created by this playbook are meant to be installed on their own server (such as `matrix.example.com`), instead of the base domain (`example.com`).
 
-Server delegation can be configured using DNS SRV records or by setting up a `/.well-known/matrix/server` file on the base domain (`example.com`).
+As [per the Server-Server specification](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), in order to use a short Matrix user ID like `@alice:example.com` instead of `@alice:matrix.example.com` while hosting services on a subdomain such as `matrix.example.com`, the Matrix network needs to be instructed of [server delegation](howto-server-delegation.md) / redirection.
 
-Both methods have their place and will continue to do so. You only need to use just one of these delegation methods. For simplicity reasons, our setup advocates for the `/.well-known/matrix/server` method and guides you into using that.
+For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file.
 
-To learn how to set up `/.well-known/matrix/server`, read the Installing section below.
+If you set up the DNS SRV record for server delegation instead, take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)
 
+### Client Server Discovery
 
-## Introduction to Client Server Discovery
-
-Client Server Service discovery lets various client programs which support it, to receive a full user ID (e.g. `@username:example.com`) and determine where the Matrix server is automatically (e.g. `https://matrix.example.com`).
+Client Server Service discovery lets various client programs which support it, to receive a full user ID (e.g. `@alice:example.com`) and determine where the Matrix server is automatically (e.g. `https://matrix.example.com`).
 
 This lets you (and your users) easily connect to your Matrix server without having to customize connection URLs. When using client programs that support it, you won't need to point them to `https://matrix.example.com` in Custom Server options manually anymore. The connection URL would be discovered automatically from your full username.
 
+Without /.well-known/matrix/client, the client will make the wrong "homeserver URL" assumption (it will default to using https://example.com, and users will need to notice and adjust it manually (changing it to https://matrix.example.com).
+
 As [per the Client-Server specification](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery) Matrix does Client Server service discovery using a `/.well-known/matrix/client` file hosted on the base domain (e.g. `example.com`).
 
 However, this playbook installs your Matrix server on another domain (e.g. `matrix.example.com`) and not on the base domain (e.g. `example.com`), so it takes a little extra manual effort to set up the file.
 
-To learn how to set it up, read the Installing section below.
+### Support Service Discovery (optional)
 
+[MSC 1929](https://github.com/matrix-org/matrix-spec-proposals/pull/1929), which was added to [Matrix Specification version v1.10](https://spec.matrix.org/v1.10/client-server-api/#getwell-knownmatrixsupport), specifies a way to add contact details of admins, as well as a link to a support page for users who are having issues with the service. Automated services may also index this information and use it for abuse reports, etc.
 
-## (Optional) Introduction to Homeserver Admin Contact and Support page
+To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
-[MSC 1929](https://github.com/matrix-org/matrix-spec-proposals/pull/1929) specifies a way to add contact details of admins, as well as a link to a support page for users who are having issues with the service. Automated services may also index this information and use it for abuse reports, etc.
-
-The two playbook variables that you could look for, if you're interested in being an early adopter, are: `matrix_static_files_file_matrix_support_property_m_contacts` and `matrix_static_files_file_matrix_support_property_m_support_page`.
-
-Example snippet for `vars.yml`:
-
-```
+```yaml
 # Enable generation of `/.well-known/matrix/support`.
 matrix_static_files_file_matrix_support_enabled: true
 
@@ -62,45 +59,41 @@ matrix_static_files_file_matrix_support_property_m_contacts:
 matrix_static_files_file_matrix_support_property_m_support_page: "https://example.com/support"
 ```
 
-To learn how to set up `/.well-known/matrix/support` for the base domain, read the Installing section below.
-
-
 ## Installing well-known files on the base domain's server
 
-To implement the two service discovery mechanisms, your base domain's server (e.g. `example.com`) needs to run an HTTPS-capable webserver.
+To implement the service discovery mechanisms, your base domain's server (e.g. `example.com`) needs to run an HTTPS-capable webserver.
 
-If you don't have a server for your base domain at all, you can use the Matrix server for this. See [Serving the base domain](configuring-playbook-base-domain-serving.md) to learn how the playbook can help you set it up. If you decide to go this route, you don't need to read ahead in this document. When **Serving the base domain**, the playbook takes care to serve the appropriate well-known files automatically.
+### Serving the base domain from the Matrix server via the playbook
+
+If you don't have a server for your base domain at all, you can use the Matrix server for this. If you don't need the base domain (e.g. `example.com`) for anything else (hosting a website, etc.), you can point it to the Matrix server's IP address and tell the playbook to configure it.
+
+**This is the easiest way to set up well-known serving** -- letting the playbook handle the whole base domain for you (including SSL certificates, etc.) and take care to serve the appropriate well-known files automatically.
+
+If you decide to go this route, you don't need to read ahead in this document. Instead, go to [Serving the base domain](configuring-playbook-base-domain-serving.md) to learn how the playbook can help you set it up.
+
+However, if you need to use the base domain for other things, this method is less suitable than the one explained below.
+
+### Manually installing well-known files on the base domain's server
 
 If you're managing the base domain by yourself somehow, you'll need to set up serving of some `/.well-known/matrix/*` files from it via HTTPS.
 
-To make things easy for you to set up, this playbook generates and hosts 2 well-known files on the Matrix domain's server. The files are generated at `/matrix/static-files/.well-known/matrix/` and hosted at `https://matrix.example.com/.well-known/matrix/server` and `https://matrix.example.com/.well-known/matrix/client`, even though this is the wrong place to host them.
+To make things easy for you to set up, this playbook generates and hosts a few well-known files on the Matrix domain's server. The files are generated at the `/matrix/static-files/public/.well-known/matrix/` path on the server and hosted at URLs like `https://matrix.example.com/.well-known/matrix/server` and `https://matrix.example.com/.well-known/matrix/client`, even though this is the wrong place to host them.
 
-You have 3 options when it comes to installing the files on the base domain's server:
+You have two options when it comes to installing the files on the base domain's server:
 
+#### (Option 1): **Copying the files manually** to your base domain's server
 
-### (Option 1): **Copying the files manually** to your base domain's server
-
-**Hint**: Option 2 and 3 (below) are generally a better way to do this. Make sure to go with them, if possible.
+**Hint**: Option 2 is generally a better way to do this. Make sure to go with it, if possible.
 
 All you need to do is:
 
 - copy `/.well-known/matrix/server` and `/.well-known/matrix/client` from the Matrix server (e.g. `matrix.example.com`) to your base domain's server (`example.com`). You can find these files in the `/matrix/static-files/.well-known/matrix` directory on the Matrix server. They are also accessible on URLs like this: `https://matrix.example.com/.well-known/matrix/server` (same for `client`).
 
-- set up the server at your base domain (e.g. `example.com`) so that it adds an extra HTTP header when serving the `/.well-known/matrix/client` file. [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS), the `Access-Control-Allow-Origin` header should be set with a value of `*`. If you don't do this step, web-based Matrix clients (like Element) may fail to work. Setting up headers for the `/.well-known/matrix/server` file is not necessary, as this file is only consumed by non-browsers, which don't care about CORS.
+- set up the server at your base domain (e.g. `example.com`) so that it adds an extra HTTP header when serving the `/.well-known/matrix/client` file. [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS), the `Access-Control-Allow-Origin` header should be set with a value of `*`. If you don't do this step, web-based Matrix clients (like Element Web) may fail to work. Setting up headers for the `/.well-known/matrix/server` file is not necessary, as this file is only consumed by non-browsers, which don't care about CORS.
 
 This is relatively easy to do and possibly your only choice if you can only host static files from the base domain's server. It is, however, **a little fragile**, as future updates performed by this playbook may regenerate the well-known files and you may need to notice that and copy them over again.
 
-
-### (Option 2): **Serving the base domain** from the Matrix server via the playbook
-
-If you don't need the base domain (e.g. `example.com`) for anything else (hosting a website, etc.), you can point it to the Matrix server's IP address and tell the playbook to configure it.
-
-This is the easiest way to set up well-known serving -- letting the playbook handle the whole base domain for you (including SSL certificates, etc.). However, if you need to use the base domain for other things (such as hosting some website, etc.), going with Option 1 or Option 3 might be more suitable.
-
-See [Serving the base domain](configuring-playbook-base-domain-serving.md) to learn how the playbook can help you set it up.
-
-
-### (Option 3): **Setting up reverse-proxying** of the well-known files from the base domain's server to the Matrix server
+#### (Option 2): **Setting up reverse-proxying** of the well-known files from the base domain's server to the Matrix server
 
 This option is less fragile and generally better.
 
@@ -118,7 +111,7 @@ server {
 	location /.well-known/matrix {
 		proxy_pass https://matrix.example.com/.well-known/matrix;
 		proxy_set_header X-Forwarded-For $remote_addr;
-        proxy_ssl_server_name on;
+		proxy_ssl_server_name on;
 	}
 
 	# other configuration
@@ -184,7 +177,6 @@ Make sure to:
 - **replace `example.com`** in the server configuration with your actual domain name
 - and: to **do this for the HTTPS-enabled server block**, as that's where Matrix expects the file to be
 
-
 ## Confirming it works
 
 No matter which method you've used to set up the well-known files, if you've done it correctly you should be able to see a JSON file at these URLs:
diff --git a/docs/container-images.md b/docs/container-images.md
index 60ddcde1e..2a38b2bd4 100644
--- a/docs/container-images.md
+++ b/docs/container-images.md
@@ -1,125 +1,165 @@
-# Container Images used by the playbook
+# Container images used by the playbook
 
 This page summarizes the container ([Docker](https://www.docker.com/)) images used by the playbook when setting up your server.
 
 We try to stick to official images (provided by their respective projects) as much as possible.
 
+## Homeserver
 
-## Container images used by default
+| Service | Container image | Default? | Description |
+| ------- | --------------- | -------- | ----------- |
+| [Synapse](configuring-playbook-synapse.md) | [element-hq/synapse](https://ghcr.io/element-hq/synapse) | ✅ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network |
+| [Conduit](configuring-playbook-conduit.md) | [matrixconduit/matrix-conduit](https://hub.docker.com/r/matrixconduit/matrix-conduit) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements |
+| [Conduwuit](configuring-playbook-conduwuit.md) | [girlbossceo/conduwuit](https://ghcr.io/girlbossceo/conduwuit) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduwuit is a fork of Conduit. |
+| [Dendrite](configuring-playbook-dendrite.md) | [matrixdotorg/dendrite-monolith](https://hub.docker.com/r/matrixdotorg/dendrite-monolith/) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse. |
 
-These services are enabled and used by default, but you can turn them off, if you wish.
+## Clients
 
-- [matrixdotorg/synapse](https://hub.docker.com/r/matrixdotorg/synapse/) - the official [Synapse](https://github.com/element-hq/synapse) Matrix homeserver (optional)
+Web clients for Matrix that you can host on your own domains.
 
-- [coturn/coturn](https://hub.docker.com/r/coturn/coturn/) - the [Coturn](https://github.com/coturn/coturn) STUN/TURN server (optional)
+| Service | Container image | Default? | Description |
+| ------- | --------------- | -------- | ----------- |
+| [Element Web](configuring-playbook-client-element-web.md) | [vectorim/element-web](https://hub.docker.com/r/vectorim/element-web/) | ✅ | Default Matrix web client, configured to connect to your own Synapse server |
+| [Hydrogen](configuring-playbook-client-hydrogen.md) | [element-hq/hydrogen-web](https://ghcr.io/element-hq/hydrogen-web) | ❌ | Lightweight Matrix client with legacy and mobile browser support |
+| [Cinny](configuring-playbook-client-cinny.md) | [ajbura/cinny](https://hub.docker.com/r/ajbura/cinny) | ❌ | Simple, elegant and secure web client |
+| [SchildiChat Web](configuring-playbook-client-schildichat-web.md) | [etke.cc/schildichat-web](https://ghcr.io/etkecc/schildichat-web) | ❌ | Based on Element Web, with a more traditional instant messaging experience |
 
-- [vectorim/element-web](https://hub.docker.com/r/vectorim/element-web/) - the [Element](https://element.io/) web client (optional)
+## Server Components
 
-- [postgres](https://hub.docker.com/_/postgres/) - the [Postgres](https://www.postgresql.org/) database server (optional)
+Services that run on the server to make the various parts of your installation work.
 
-- [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay/) - the [Exim](https://www.exim.org/) email server (optional)
+| Service | Container image | Default? | Description |
+| ------- | --------------- | -------- | ----------- |
+| [PostgreSQL](configuring-playbook-external-postgres.md) | [postgres](https://hub.docker.com/_/postgres/) | ✅ | Database for Synapse. [Using an external PostgreSQL server](configuring-playbook-external-postgres.md) is also possible. |
+| [coturn](configuring-playbook-turn.md) | [coturn/coturn](https://hub.docker.com/r/coturn/coturn/) | ✅ | STUN/TURN server for WebRTC audio/video calls |
+| [Traefik](configuring-playbook-traefik.md) | [Traefik](https://hub.docker.com/_/traefik/) | ✅ | Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](configuring-playbook-own-webserver.md) |
+| [Let's Encrypt](configuring-playbook-ssl-certificates.md) | [certbot/certbot](https://hub.docker.com/r/certbot/certbot/) | ✅ | The [certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/) |
+| [Exim](configuring-playbook-email.md) | [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay/) | ✅ | Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server) |
+| [ma1sd](configuring-playbook-ma1sd.md) | [ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/) | ❌ | Matrix Identity Server |
+| [ddclient](configuring-playbook-dynamic-dns.md) | [linuxserver/ddclient](https://hub.docker.com/r/linuxserver/ddclient) | ❌ | Update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider |
 
-- [Traefik](https://hub.docker.com/_/traefik/) - the [Traefik](https://traefik.io/) web server (optional)
+## Authentication
 
-- [certbot/certbot](https://hub.docker.com/r/certbot/certbot/) - the [certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/) (optional)
+Extend and modify how users are authenticated on your homeserver.
 
+| Service | Container image | Default? | Description |
+| ------- | --------------- | -------- | ----------- |
+| [matrix-synapse-rest-auth](configuring-playbook-rest-auth.md) | (N/A) | ❌ | REST authentication password provider module |
+| [matrix-synapse-shared-secret-auth](configuring-playbook-shared-secret-auth.md) | (N/A) | ❌ | Password provider module |
+| [matrix-synapse-ldap3](configuring-playbook-ldap-auth.md) (advanced) | (N/A) | ❌ | LDAP Auth password provider module |
+| [matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) | [activism.international/matrix_ldap_registration_proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy/container_registry) | ❌ | A proxy that handles Matrix registration requests and forwards them to LDAP. |
+| [matrix-registration](configuring-playbook-matrix-registration.md) | [zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-matrix-registration/) | ❌ | A simple python application to have a token based Matrix registration |
+| [Matrix User Verification Service](configuring-playbook-user-verification-service.md) (UVS) | [matrixdotorg/matrix-user-verification-service](https://hub.docker.com/r/atrixdotorg/matrix-user-verification-service) | ❌ | Service to verify details of a user based on an Open ID token |
+| [synapse-simple-antispam](configuring-playbook-synapse-simple-antispam.md) (advanced) | (N/A) | ❌ | A spam checker module |
 
-## Optional other container images we may use
+## File Storage
 
-These services are not part of our default installation, but can be enabled by [configuring the playbook](configuring-playbook.md) (either before the initial installation or any time later):
+Use alternative file storage to the default `media_store` folder.
 
-- [ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/) - the [ma1sd](https://github.com/ma1uta/ma1sd) Matrix Identity server (optional)
+| Service | Container image | Default? | Description |
+| ------- | --------------- | -------- | ----------- |
+| [Goofys](configuring-playbook-s3-goofys.md) | [ewoutp/goofys](https://hub.docker.com/r/ewoutp/goofys/) | ❌ | [Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files |
+| [synapse-s3-storage-provider](configuring-playbook-s3.md) | (N/A) | ❌ | [Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files |
+| [matrix-media-repo](configuring-playbook-matrix-media-repo.md) | [t2bot/matrix-media-repo](https://ghcr.io/t2bot/matrix-media-repo) | ❌ | matrix-media-repo is a 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. |
 
-- [matrixconduit/matrix-conduit](https://hub.docker.com/r/matrixconduit/matrix-conduit) - the [Conduit](https://conduit.rs) Matrix homeserver (optional)
+# Bridges
 
-- [matrixdotorg/dendrite-monolith](https://hub.docker.com/r/matrixdotorg/dendrite-monolith/) - the [Dendrite](https://github.com/matrix-org/dendrite) Matrix homeserver (optional)
+Bridges can be used to connect your Matrix installation with third-party communication networks.
 
-- [ewoutp/goofys](https://hub.docker.com/r/ewoutp/goofys/) - the [Goofys](https://github.com/kahing/goofys) Amazon [S3](https://aws.amazon.com/s3/) file-system-mounting program (optional)
+| Service | Container image | Default? | Description |
+| ------- | --------------- | -------- | ----------- |
+| [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) | [mautrix/discord](https://mau.dev/mautrix/discord/container_registry) | ❌ | Bridge to [Discord](https://discord.com/) |
+| [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) | [mautrix/slack](https://mau.dev/mautrix/slack/container_registry) | ❌ | Bridge to [Slack](https://slack.com/) |
+| [mautrix-telegram](configuring-playbook-bridge-mautrix-telegram.md) | [mautrix/telegram](https://mau.dev/mautrix/telegram/container_registry) | ❌ | Bridge to [Telegram](https://telegram.org/) |
+| [mautrix-gmessages](configuring-playbook-bridge-mautrix-gmessages.md) | [mautrix/gmessages](https://mau.dev/mautrix/gmessages/container_registry) | ❌ | Bridge to [Google Messages](https://messages.google.com/) |
+| [mautrix-whatsapp](configuring-playbook-bridge-mautrix-whatsapp.md) | [mautrix/whatsapp](https://mau.dev/mautrix/whatsapp/container_registry) | ❌ | Bridge to [WhatsApp](https://www.whatsapp.com/) |
+| [mautrix-wsproxy](configuring-playbook-bridge-mautrix-wsproxy.md) | [mautrix/wsproxy](https://mau.dev/mautrix/wsproxy/container_registry) | ❌ | Bridge to Android SMS or Apple iMessage |
+| [mautrix-twitter](configuring-playbook-bridge-mautrix-twitter.md) | [mautrix/twitter](https://mau.dev/mautrix/twitter/container_registry) | ❌ | Bridge to [Twitter](https://twitter.com/) |
+| [mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md) | [mautrix/googlechat](https://mau.dev/mautrix/googlechat/container_registry) | ❌ | Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat) |
+| mautrix-meta (for [Messenger](configuring-playbook-bridge-mautrix-meta-messenger.md) and [Instagram](configuring-playbook-bridge-mautrix-meta-instagram.md)) | [mautrix/meta](https://mau.dev/mautrix/meta/container_registry) | ❌ | Bridge to [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) |
+| [mautrix-signal](configuring-playbook-bridge-mautrix-signal.md) | [mautrix/signal](https://mau.dev/mautrix/signal/container_registry) | ❌ | Bridge to [Signal](https://www.signal.org/) |
+| [beeper-linkedin](configuring-playbook-bridge-beeper-linkedin.md) | [beeper/linkedin](https://ghcr.io/beeper/linkedin) | ❌ | Bridge to [LinkedIn](https://www.linkedin.com/) |
+| [matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md) | [matrixdotorg/matrix-appservice-irc](https://hub.docker.com/r/matrixdotorg/matrix-appservice-irc) | ❌ | Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat) |
+| [matrix-appservice-kakaotalk](configuring-playbook-bridge-appservice-kakaotalk.md) | Self-building | ❌ | Bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) |
+| [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md) | [matrix-org/matrix-appservice-discord](https://ghcr.io/matrix-org/matrix-appservice-discord) | ❌ | Bridge to [Discord](https://discordapp.com/) |
+| [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) | [matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack) | ❌ | Bridge to [Slack](https://slack.com/) |
+| [matrix-hookshot](configuring-playbook-bridge-hookshot.md) | [halfshot/matrix-hookshot](https://hub.docker.com/r/halfshot/matrix-hookshot) | ❌ | Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular |
+| [matrix-sms-bridge](configuring-playbook-bridge-matrix-bridge-sms.md) | [folivonet/matrix-sms-bridge](https://hub.docker.com/repository/docker/folivonet/matrix-sms-bridge) | ❌ | Bridge to SMS |
+| [matrix-wechat](configuring-playbook-bridge-wechat.md) | [lxduo/matrix-wechat](https://hub.docker.com/r/lxduo/matrix-wechat) | ❌ | Bridge to [WeChat](https://www.wechat.com/) |
+| [Heisenbridge](configuring-playbook-bridge-heisenbridge.md) | [hif1/heisenbridge](https://hub.docker.com/r/hif1/heisenbridge) | ❌ | Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat) |
+| [go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md) | [nodefyme/go-skype-bridge](https://hub.docker.com/r/nodefyme/go-skype-bridge) | ❌ | Bridge to [Skype](https://www.skype.com) |
+| [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) | [mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/container_registry) | ❌ | Bridge to [Slack](https://slack.com) |
+| [mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md) | [sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-puppet-instagram) | ❌ | Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/)) |
+| [mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md) | [sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter) | ❌ | Bridge for Twitter-DMs ([Twitter](https://twitter.com/)) |
+| [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) | [mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/container_registry) | ❌ | Bridge to [Discord](https://discordapp.com/) |
+| [mx-puppet-groupme](configuring-playbook-bridge-mx-puppet-groupme.md) | [xangelix/mx-puppet-groupme](https://hub.docker.com/r/xangelix/mx-puppet-groupme) | ❌ | Bridge to [GroupMe](https://groupme.com/) |
+| [mx-puppet-steam](configuring-playbook-bridge-mx-puppet-steam.md) | [icewind1991/mx-puppet-steam](https://hub.docker.com/r/icewind1991/mx-puppet-steam) | ❌ | Bridge to [Steam](https://steamapp.com/) |
+| [Email2Matrix](configuring-playbook-email2matrix.md) | [devture/email2matrix](https://hub.docker.com/r/devture/email2matrix/) | ❌ | Bridge for relaying emails to Matrix rooms |
+| [Postmoogle](configuring-playbook-bridge-postmoogle.md) | [etke.cc/postmoogle](https://github.com/etkecc/postmoogle/container_registry) | ❌ | Email to Matrix bridge |
 
-- [etherpad/etherpad](https://hub.docker.com/r/etherpad/etherpad/) - the [Etherpad](https://etherpad.org) realtime collaborative text editor that can be used in a Jitsi audio/video call or integrated as a widget into Matrix chat rooms via the Dimension integration manager (optional)
+## Bots
 
-- [devture/email2matrix](https://hub.docker.com/r/devture/email2matrix/) - the [Email2Matrix](https://github.com/devture/email2matrix) email server, which can relay email messages to Matrix rooms (optional)
+Bots provide various additional functionality to your installation.
 
-- [devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-corporal/) - [Matrix Corporal](https://github.com/devture/matrix-corporal): reconciliator and gateway for a managed Matrix server (optional)
+| Service | Container image | Default? | Description |
+| ------- | --------------- | -------- | ----------- |
+| [baibot](configuring-playbook-bot-baibot.md) | [etke.cc/baibot](https://ghcr.io/etkecc/baibot) | ❌ | A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you |
+| [matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md) | [anoa/matrix-reminder-bot](https://hub.docker.com/r/anoa/matrix-reminder-bot) | ❌ | Bot for scheduling one-off & recurring reminders and alarms |
+| [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) | [moanos/matrix-registration-bot](https://hub.docker.com/r/moanos/matrix-registration-bot/) | ❌ | Bot for invitations by creating and managing registration tokens |
+| [maubot](configuring-playbook-bot-maubot.md) | [dock.mau.dev/maubot/maubot](https://mau.dev/maubot/maubot/container_registry) | ❌ | A plugin-based Matrix bot system |
+| [Honoroit](configuring-playbook-bot-honoroit.md) | [etke.cc/honoroit](https://github.com/etkecc/honoroit/container_registry) | ❌ | A helpdesk bot |
+| [Mjolnir](configuring-playbook-bot-mjolnir.md) | [matrixdotorg/mjolnir](https://hub.docker.com/r/matrixdotorg/mjolnir) | ❌ | A moderation tool for Matrix |
+| [Draupnir](configuring-playbook-bot-draupnir.md) | [gnuxie/draupnir](https://hub.docker.com/r/gnuxie/draupnir) | ❌ | A moderation tool for Matrix (Fork of Mjolnir) |
+| [Buscarron](configuring-playbook-bot-buscarron.md) | [etke.cc/buscarron](https://ghcr.io/etkecc/buscarron) | ❌ | Web forms (HTTP POST) to Matrix |
 
-- [zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-matrix-registration/) - [matrix-registration](https://github.com/ZerataX/matrix-registration): a simple python application to have a token based Matrix registration (optional)
+## Administration
 
-- [mautrix/telegram](https://mau.dev/mautrix/telegram/container_registry) - the [mautrix-telegram](https://github.com/mautrix/telegram) bridge to [Telegram](https://telegram.org/) (optional)
+Services that help you in administrating and monitoring your Matrix installation.
 
-- [mautrix/gmessages](https://mau.dev/mautrix/gmessages/container_registry) - the [mautrix-gmessages](https://github.com/mautrix/gmessages) bridge to [Google Messages](https://messages.google.com/) (optional)
+| Service | Container image | Default? | Description |
+| ------- | --------------- | -------- | ----------- |
+| [matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md) | [metio/matrix-alertmanager-receiver](https://hub.docker.com/r/metio/matrix-alertmanager-receiver)  | ❌ | Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client |
+| [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) | [element-hq/matrix-authentication-service](https://ghcr.io/element-hq/matrix-authentication-service) | ❌ | OAuth 2.0 and OpenID Provider server |
+| [synapse-admin](configuring-playbook-synapse-admin.md) | [etke.cc/synapse-admin](https://ghcr.io/etkecc/synapse-admin) | ❌ | A web UI tool for administrating users and rooms on your Matrix server |
+| [Metrics and Graphs](configuring-playbook-prometheus-grafana.md) | [prom/prometheus](https://hub.docker.com/r/prom/prometheus/) | ❌ | [Prometheus](https://prometheus.io) time-series database server |
+| [Metrics and Graphs](configuring-playbook-prometheus-grafana.md) | [prom/node-exporter](https://hub.docker.com/r/prom/node-exporter/) | ❌ | Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter |
+| [Metrics and Graphs](configuring-playbook-prometheus-grafana.md) | [grafana/grafana](https://hub.docker.com/r/grafana/grafana/) | ❌ | Graphing tool that works well with the above two images. Our playbook also adds two dashboards for [Synapse](https://github.com/element-hq/synapse/tree/master/contrib/grafana) and [Node Exporter](https://github.com/rfrail3/grafana-dashboards) |
+| [Metrics and Graphs](configuring-playbook-prometheus-nginxlog.md) | [martin-helmich/prometheus-nginxlog-exporter/exporter](https://ghcr.io/martin-helmich/prometheus-nginxlog-exporter/exporter) | ❌ | Addon for Prometheus that gathers access logs from various nginx reverse-proxies |
+| [Borg](configuring-playbook-backup-borg.md) | (N/A) | ❌ | Backups |
+| [rageshake](configuring-playbook-rageshake.md) | [matrix-org/rageshake](https://ghcr.io/matrix-org/rageshake) | ❌ | Bug report server |
+| [synapse-usage-exporter](configuring-playbook-synapse-usage-exporter.md) | Self-building | ❌ | Export the usage statistics of a Synapse homeserver to be scraped by Prometheus. |
 
-- [mautrix/whatsapp](https://mau.dev/mautrix/whatsapp/container_registry) - the [mautrix-whatsapp](https://github.com/mautrix/whatsapp) bridge to [Whatsapp](https://www.whatsapp.com/) (optional)
+## Misc
 
-- [mautrix/facebook](https://mau.dev/mautrix/facebook/container_registry) - the [mautrix-facebook](https://github.com/mautrix/facebook) bridge to [Facebook](https://facebook.com/) (optional)
+Various services that don't fit any other categories.
 
-- [mautrix/twitter](https://mau.dev/mautrix/twitter/container_registry) - the [mautrix-twitter](https://github.com/mautrix/twitter) bridge to [Twitter](https://twitter.com/) (optional)
+| Service | Container image | Default? | Description |
+| ------- | --------------- | -------- | ----------- |
+| [sliding-sync](configuring-playbook-sliding-sync-proxy.md) | [matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync) | ❌ | Sliding Sync support for clients which require it (like old Element X versions, before it got switched to Simplified Sliding Sync) |
+| [synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md) | (N/A) | ❌ | A Synapse module to automatically accept invites. |
+| [synapse_auto_compressor](configuring-playbook-synapse-auto-compressor.md) | [etke.cc/rust-synapse-compress-state](https://gitlab.com/etke.cc/rust-synapse-compress-state/container_registry) | ❌ | A cli tool that automatically compresses `state_groups` database table in background. |
+| [Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced) | [devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-corporal/) | ❌ | Reconciliator and gateway for a managed Matrix server |
+| [Etherpad](configuring-playbook-etherpad.md) | [etherpad/etherpad](https://hub.docker.com/r/etherpad/etherpad/) | ❌ | An open source collaborative text editor |
+| [Jitsi](configuring-playbook-jitsi.md) | [jitsi/web](https://hub.docker.com/r/jitsi/web) | ❌ | the [Jitsi](https://jitsi.org/) web UI |
+| [Jitsi](configuring-playbook-jitsi.md) | [jitsi/jicofo](https://hub.docker.com/r/jitsi/jicofo) | ❌ | the [Jitsi](https://jitsi.org/) Focus component |
+| [Jitsi](configuring-playbook-jitsi.md) | [jitsi/prosody](https://hub.docker.com/r/jitsi/prosody) | ❌ | the [Jitsi](https://jitsi.org/) Prosody XMPP server component |
+| [Jitsi](configuring-playbook-jitsi.md) | [jitsi/jvb](https://hub.docker.com/r/jitsi/jvb) | ❌ | the [Jitsi](https://jitsi.org/) Video Bridge component |
+| [Cactus Comments](configuring-playbook-cactus-comments.md) | [cactuscomments/cactus-appservice](https://hub.docker.com/r/cactuscomments/cactus-appservice/) | ❌ | A federated comment system built on Matrix |
+| [Cactus Comments](configuring-playbook-cactus-comments.md) | [joseluisq/static-web-server](https://hub.docker.com/r/joseluisq/static-web-server) | ❌ | A federated comment system built on Matrix |
+| [Pantalaimon](configuring-playbook-pantalaimon.md) | [matrixdotorg/pantalaimon](https://hub.docker.com/r/matrixdotorg/pantalaimon) | ❌ | An E2EE aware proxy daemon |
+| [Sygnal](configuring-playbook-sygnal.md) | [matrixdotorg/sygnal](https://hub.docker.com/r/matrixdotorg/sygnal/) | ❌ | Reference Push Gateway for Matrix |
+| [ntfy](configuring-playbook-ntfy.md) | [binwiederhier/ntfy](https://hub.docker.com/r/binwiederhier/ntfy/) | ❌ | Self-hosted, UnifiedPush-compatible push notifications server |
 
-- [mautrix/hangouts](https://mau.dev/mautrix/hangouts/container_registry) - the [mautrix-hangouts](https://github.com/mautrix/hangouts) bridge to [Google Hangouts](https://en.wikipedia.org/wiki/Google_Hangouts) (optional)
+## Container images of deprecated / unmaintained services
 
-- [mautrix/googlechat](https://mau.dev/mautrix/googlechat/container_registry) - the [mautrix-googlechat](https://github.com/mautrix/googlechat) bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat) (optional)
+The list of the deprecated or unmaintained services is available [here](configuring-playbook.md#deprecated--unmaintained--removed-services).
 
-- [mautrix/instagram](https://mau.dev/mautrix/instagram/container_registry) - the [mautrix-instagram](https://github.com/mautrix/instagram) bridge to [Instagram](https://instagram.com/) (optional)
-
-- [mautrix/signal](https://mau.dev/mautrix/signal/container_registry) - the [mautrix-signal](https://github.com/mautrix/signal) bridge to [Signal](https://www.signal.org/) (optional)
-
-- [matrixdotorg/matrix-appservice-irc](https://hub.docker.com/r/matrixdotorg/matrix-appservice-irc) - the [matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc) bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat) (optional)
-
-- [halfshot/matrix-appservice-discord](https://hub.docker.com/r/halfshot/matrix-appservice-discord) - the [matrix-appservice-discord](https://github.com/Half-Shot/matrix-appservice-discord) bridge to [Discord](https://discordapp.com/) (optional)
-
-- [cadair/matrix-appservice-slack](https://hub.docker.com/r/cadair/matrix-appservice-slack) - the [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge to [Slack](https://slack.com/) (optional)
-
-- [turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks) - the [Appservice Webhooks](https://github.com/turt2live/matrix-appservice-webhooks) bridge (optional)
-
-- [folivonet/matrix-sms-bridge](https://hub.docker.com/repository/docker/folivonet/matrix-sms-bridge) - the [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) (optional)
-
-- [sorunome/mx-puppet-slack](https://hub.docker.com/r/sorunome/mx-puppet-slack) - the [mx-puppet-slack](https://github.com/Sorunome/mx-puppet-slack) bridge to [Slack](https://slack.com) (optional)
-
-- [sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-puppet-instagram) - the [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) bridge to [Instagram](https://www.instagram.com) (optional)
-
-- [sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter) - the [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) bridge to [Twitter](https://twitter.com) (optional)
-
-- [sorunome/mx-puppet-discord](https://hub.docker.com/r/sorunome/mx-puppet-discord) - the [mx-puppet-discord](https://github.com/matrix-discord/mx-puppet-discord) bridge to [Discord](https://discordapp.com) (optional)
-
-- [xangelix/mx-puppet-groupme](https://hub.docker.com/r/xangelix/mx-puppet-groupme) - the [mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) bridge to [GroupMe](https://groupme.com/) (optional)
-
-- [icewind1991/mx-puppet-steam](https://hub.docker.com/r/icewind1991/mx-puppet-steam) - the [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) bridge to [Steam](https://steampowered.com) (optional)
-
-- [turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-dimension) - the [Dimension](https://dimension.t2bot.io/) integration manager (optional)
-
-- [jitsi/web](https://hub.docker.com/r/jitsi/web) - the [Jitsi](https://jitsi.org/) web UI (optional)
-
-- [jitsi/jicofo](https://hub.docker.com/r/jitsi/jicofo) - the [Jitsi](https://jitsi.org/) Focus component (optional)
-
-- [jitsi/prosody](https://hub.docker.com/r/jitsi/prosody) - the [Jitsi](https://jitsi.org/) Prosody XMPP server component (optional)
-
-- [jitsi/jvb](https://hub.docker.com/r/jitsi/jvb) - the [Jitsi](https://jitsi.org/) Video Bridge component (optional)
-
-- [anoa/matrix-reminder-bot](https://hub.docker.com/r/anoa/matrix-reminder-bot) - the [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot) bot for one-off & recurring reminders and alarms (optional)
-
-- [moanos/matrix-registration-bot/](https://hub.docker.com/r/moanos/matrix-registration-bot/) - the [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) bot (manage registration tokens for invitations to the server) (optional)
-
-- [dock.mau.dev/maubot/maubot](https://mau.dev/maubot/maubot/container_registry) - the [maubot](https://github.com/maubot/maubot) bot (a plugin-based Matrix bot system) (optional)
-
-- [etke.cc/honoroit](https://github.com/etkecc/honoroit/container_registry) - the [honoroit](https://github.com/etkecc/honoroit) helpdesk bot (optional)
-
-- [etke.cc/postmoogle](https://github.com/etkecc/postmoogle/container_registry) - the [Postmoogle](https://github.com/etkecc/postmoogle) email bridge bot (optional)
-
-- [matrixdotorg/go-neb](https://hub.docker.com/r/matrixdotorg/go-neb) - the [Go-NEB](https://github.com/matrix-org/go-neb) bot (optional)
-
-- [matrixdotorg/mjolnir](https://hub.docker.com/r/matrixdotorg/mjolnir) - the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation bot (optional)
-
-- [gnuxie/draupnir](https://hub.docker.com/r/gnuxie/draupnir) - the [Draupnir](https://github.com/the-draupnir-project/Draupnir/) moderation bot (optional)
-
-- [awesometechnologies/synapse-admin](https://hub.docker.com/r/awesometechnologies/synapse-admin) - the [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin) web UI tool for administrating users and rooms on your Matrix server (optional)
-
-- [prom/prometheus](https://hub.docker.com/r/prom/prometheus/) - [Prometheus](https://github.com/prometheus/prometheus/) is a systems and service monitoring system
-
-- [prom/node-exporter](https://hub.docker.com/r/prom/node-exporter/) - [Prometheus Node Exporter](https://github.com/prometheus/node_exporter/) is an addon for Prometheus that gathers standard system metrics
-
-- [grafana/grafana](https://hub.docker.com/r/grafana/grafana/) - [Grafana](https://github.com/grafana/grafana/) is a graphing tool that works well with the above two images. Our playbook also adds two dashboards for [Synapse](https://github.com/element-hq/synapse/tree/master/contrib/grafana) and  [Node Exporter](https://github.com/rfrail3/grafana-dashboards)
-
-- [matrixdotorg/sygnal](https://hub.docker.com/r/matrixdotorg/sygnal/) - [Sygnal](https://github.com/matrix-org/sygnal) is a reference Push Gateway for Matrix
-
-- [binwiederhier/ntfy](https://hub.docker.com/r/binwiederhier/ntfy/) - [ntfy](https://ntfy.sh/) is a self-hosted, UnifiedPush-compatible push notifications server
-
-- [cactuscomments/cactus-appservice](https://hub.docker.com/r/cactuscomments/cactus-appservice/) - [Cactus Comments](https://cactus.chat) a federated comment system built on Matrix
+| Service | Container image | Default? | Description |
+| ------- | --------------- | -------- | ----------- |
+| [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md) | [turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks) | ❌ | Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.) |
+| [Dimension](configuring-playbook-dimension.md) | [turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-dimension) | ❌ | An open source integration manager for Matrix clients |
+| [Go-NEB](configuring-playbook-bot-go-neb.md) | [matrixdotorg/go-neb](https://hub.docker.com/r/matrixdotorg/go-neb) | ❌ | A multi functional bot written in Go |
+| [matrix-chatgpt-bot](configuring-playbook-bot-chatgpt.md) | [matrixgpt/matrix-chatgpt-bot](https://ghcr.io/matrixgpt/matrix-chatgpt-bot) | ❌ | Accessing ChatGPT via your favourite Matrix client |
+| [mautrix-facebook](configuring-playbook-bridge-mautrix-facebook.md) | [mautrix/facebook](https://mau.dev/mautrix/facebook/container_registry) | ❌ | Bridge to [Facebook](https://facebook.com/) |
+| [mautrix-hangouts](configuring-playbook-bridge-mautrix-hangouts.md) | [mautrix/hangouts](https://mau.dev/mautrix/hangouts/container_registry) | ❌ | Bridge to [Google Hangouts](https://en.wikipedia.org/wiki/Google_Hangouts) |
+| [mautrix-instagram](configuring-playbook-bridge-mautrix-instagram.md) | [mautrix/instagram](https://mau.dev/mautrix/instagram/container_registry) | ❌ | Bridge to [Instagram](https://instagram.com/) |
diff --git a/docs/faq.md b/docs/faq.md
index cbd210868..51e093fc7 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -6,30 +6,29 @@ This FAQ page does not intend to replace the [matrix.org FAQ](https://matrix.org
 
 We've only started this FAQ recently, so it's still somewhat empty.
 
-Also, we encourage you to not dig yourself into a hole by reading way too much. When you've heard enough, proceed to [Prerequisites](prerequisites.md) to get guided into installing Matrix.
-
+Also, we encourage you to not dig yourself into a hole by reading way too much. When you've heard enough, proceed to installation. To get started, see [below](#how-do-i-run-the-installation) about our installation guides.
 
 ## Introductory
 
-## Where do I find more questions and answers about Matrix?
+### Where do I find more questions and answers about Matrix?
 
 This is a Frequently Asked Questions page focused on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work)) for deploying a [Matrix](https://matrix.org/) server.
 
 For a lot more generic questions and answers, see the [matrix.org FAQ](https://matrix.org/faq/).
 
-## What is Matrix? What is Element? What is Synapse? Why are you confusing me with so many terms?
+### What is Matrix? What is Element? What is Synapse? Why are you confusing me with so many terms?
 
 [Matrix](https://matrix.org/) is a new type of realtime communication (chat) network, the closest analogy to which is probably "email".
 
 You don't just use the "email" protocols (SMTP, POP3, IMAP) directly though. There's a *server* somewhere which stores your data (`@gmail.com`, `@yahoo.com`, `@hotmail.com`, `@your-company.com`) and you access it by using these "email" protocols via some *client* program (Outlook, Thunderbird, some website, etc).
 
-In the world of the Matrix chat protocol, there are various client programs. The first and currently most full-featured one is called [Element](https://element.io/) (used to be called Riot.im and Vector.im in the past). There are [many other clients](https://matrix.org/clients/). You can switch clients as much as you want until you find the one that is right for you on a given platform (you may use Element on your desktop, but Fluffychat on your phone, etc).
+In the world of the Matrix chat protocol, there are various client programs. The first and currently most full-featured one is called [Element](https://element.io/) (used to be called Riot.im and Vector.im in the past). There are [many other clients](https://matrix.org/clients/). You can switch clients as much as you want until you find the one that is right for you on a given platform (you may use Element Desktop on your desktop, but Fluffychat on your phone, etc).
 
 Matrix is also like email due to the fact that there are many servers around the world which can all talk to each other (you can send email from `@gmail.com` addresses to `@yahoo.com` and `@hotmail.com` addresses). It's the same with Matrix (`@bob:example.com` can talk to `@alice:example.org`).
 
-If someone else is hosting your Matrix server (you being `@user:matrix.org` or some other public server like this), all you need is a Matrix client program, like Element.
+If someone else is hosting your Matrix server (you being `@alice:matrix.org` or some other public server like this), all you need is a Matrix client program, like Element Web or Element X Android.
 
-If you'd like to host your own server (you being `@user:example.com`), you'd need to set up a Matrix server program, like Synapse.
+If you'd like to host your own server (you being `@alice:example.com`), you'd need to set up a Matrix server program, like Synapse.
 
 In short:
 
@@ -39,7 +38,7 @@ In short:
 
 This FAQ here mostly focuses on installing various Matrix services using the Ansible automation tool. You can learn much more about Matrix in the [matrix.org FAQ](https://matrix.org/faq/).
 
-## People I wish to talk to are not on Matrix. Can I talk to them?
+### People I wish to talk to are not on Matrix. Can I talk to them?
 
 You most likely can. Besides Matrix-native chats, Matrix also supports the concept of "bridging", which allows you to plug other networks into it.
 
@@ -47,17 +46,17 @@ This Ansible playbook can help you install [tens of bridges for various networks
 
 Besides setting up your own bridges (preferable), you can also use some [public bridges hosted by others](https://publiclist.anchel.nl/#bridges).
 
-## How do I get started with Matrix?
+### How do I get started with Matrix?
 
 One of [Matrix](https://matrix.org/)'s distinguishing strengths (compared to other chat networks) is its decentralized nature. There's not just one entity (company, organization) controlling the servers. Rather there's thousands of servers operated by different people - one server being insecure, slow or disrespective toward its users does not affect the rest of the network. To participate in that decentralization in its fullest, consider hosting your own server or using some public server other than the largest/default one (`matrix.org`).
 
 There are 3 ways to get into Matrix, depending on your technical ability and needs:
 
-- **using the existing default server** - the easiest way is to use an existing server. The largest public Matrix server is `matrix.org` and it's configured as a default server in clients such as [Element](https://element.io) and many others. Just use Element on the browser via that link (or download the Element app on a smartphone), create an account and start chatting.
+- **using the existing default server** - the easiest way is to use an existing server. The largest public Matrix server is `matrix.org` and it's configured as a default server in clients such as [Element Web](https://app.element.io) and many others. Just use Element Web on the browser via that link (or [download client apps for your Desktop or smartphone](https://element.io/app-for-productivity)), create an account and start chatting.
 
-- **using some other server** - instead of using the largest public server (`matrix.org`), you can use another public one. Here's a [list of public Matrix servers](https://joinmatrix.org/servers/) to choose from. Again, you download [Element](https://element.io) or [some other client](https://matrix.org/clients/) of your choosing and adjust the homeserver URL during login.
+- **using some other server** - instead of using the largest public server (`matrix.org`), you can use another public one. Here's a [list of public Matrix servers](https://joinmatrix.org/servers/) to choose from. Go to [Element Web](https://app.element.io) or download [some other client](https://matrix.org/clients/) of your choosing and adjust the homeserver URL during login.
 
-- **using your own server** - running your own server puts you in ultimate control of your data. It also lets you have your own user identifiers (e.g. `@bob:example.com`). See [How do I set up my own Matrix server](#how-do-i-set-up-my-own-matrix-server).
+- **using your own server** - running your own server puts you in ultimate control of your data. It also lets you have your own user IDs (e.g. `@bob:example.com`). See [How do I set up my own Matrix server](#how-do-i-set-up-my-own-matrix-server).
 
 ### How do I set up my own Matrix server?
 
@@ -66,7 +65,8 @@ Normally, you'd first choose the [Matrix](https://matrix.org/) server software y
 There are [many guides about installing Synapse](https://matrix.org/docs/guides/#installing-synapse). Using this Ansible playbook is just one way of doing it.
 
 Naturally, we're biased, so our usual recommendation is to go with this [Ansible](https://www.ansible.com/) playbook, instead of installing Synapse (and many many other things around it) manually.
-To get started with the playbook, start at the [Prerequisites](prerequisites.md) page.
+
+To get started with the playbook, check out the [Quick start](quick-start.md) or full installation guide (starting at the [Prerequisites](prerequisites.md) page).
 
 ### What is Ansible? How does it work?
 
@@ -80,6 +80,16 @@ Alternatively, you can download Ansible and the playbook itself directly on the
 
 To learn more, see our [dedicated Ansible documentation page](ansible.md).
 
+### What is `just`?
+
+[`just`](https://github.com/casey/just) is a modern command-runner alternative to [make](https://www.gnu.org/software/make/). It can be used to invoke commands with less typing.
+
+The `just` utility executes shortcut commands (called "recipes"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile).
+
+For details about `just` commands, take a look at: [Running `just` commands](just.md).
+
+The playbook also contains a `Makefile` for the `make` tool, but most of the just recipes are not available as targets in the `Makefile`.
+
 ### Why use this playbook and not install Synapse and other things manually?
 
 There are various guides telling you how easy it is to install [Synapse](https://github.com/element-hq/synapse).
@@ -88,7 +98,7 @@ Reading the documentation of this Ansible playbook, you may also be thinking:
 
 > I don't know what [Ansible](https://www.ansible.com/) is. I don't know what [Docker](https://www.docker.com/) is. This looks more complicated.
 
-.. so you may be leaning toward [installing Synapse manually](https://github.com/element-hq/synapse/blob/master/INSTALL.md).
+… so you may be leaning toward [installing Synapse manually](https://github.com/element-hq/synapse/blob/master/INSTALL.md).
 
 The problem with a manual installation is:
 
@@ -111,6 +121,10 @@ Besides Synapse, you'd need other things - a Postgres database, likely the [Elem
 
 Using the playbook, you get all these components in a way that works well together out of the box.
 
+### Occasionally I see some people are talking about "MDAD". What is it?
+
+It is the acronym of us: **m**atrix-**d**ocker-**a**nsible-**d**eploy.
+
 ### What's different about this Ansible playbook compared to [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy)?
 
 This is similar to the [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy) Ansible deployment, but:
@@ -183,7 +197,7 @@ The only thing we need on the distro is systemd and Python (we install Docker ou
 
 Instead of using [docker-compose](https://docs.docker.com/compose/), we prefer installing systemd services and scheduling those independently.
 
-There are people who have worked on turning this setup into a docker-compose-based one. See these experiments [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/64#issuecomment-603164625).
+There are people who have worked on turning this setup into a docker-compose-based one. See these experiments [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/64#issuecomment-603164625). There is also a demo project ([element-docker-demo](https://github.com/element-hq/element-docker-demo)) by Element.
 
 ### Can I run this on a distro without systemd?
 
@@ -215,34 +229,25 @@ Besides the regular Matrix stuff, we also support things like video-conferencing
 
 If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container.
 
-
 ## Configuration
 
 ### Why install my server at matrix.example.com and not at the base domain?
 
 It's the same with email servers. Your email address is likely `name@company.com`, not `name@mail.company.com`, even though it's `mail.company.com` that is really handling your data for `@company.com` email to work.
 
-Using a separate domain name is easier to manage (although it's a little hard to get right at first) and keeps your Matrix server isolated from your website (if you have one), from your email server (if you have one), etc.
-
-We allow `matrix.example.com` to be the Matrix server handling Matrix stuff for `example.com` by [Server Delegation](howto-server-delegation.md). During the installation procedure, we recommend that you set up server delegation using the [.well-known](configuring-well-known.md) method.
-
-If you'd really like to install Matrix services directly on the base domain, see [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain)
+Using a separate domain name is easier to manage (although it's a little hard to get right at first) and keeps your Matrix server isolated from your website (if you have one), from your email server (if you have one), etc. Therefore, this playbook sets up services on your Matrix server (`matrix.example.com`) by default.
 
 ### I don't control anything on the base domain and can't set up delegation to matrix.example.com. What do I do?
 
-If you're not in control of your base domain (or the server handling it) at all, you can take a look at [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain)
+If you're not in control of your base domain (or the server handling it) at all, you can take a look at [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)
 
 ### I can't set up HTTPS on the base domain. How will I get Matrix federating?
 
-If you really can't obtain an HTTPS certificate for your base domain, you can take a look at [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain)
+If you really can't obtain an HTTPS certificate for your base domain, you can take a look at [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)
 
 ### How do I install on matrix.example.com without involving the base domain?
 
-This Ansible playbook guides you into installing a server for `example.com` (user identifiers are like this: `@user:example.com`), while the server is at `matrix.example.com`.
-
-We allow `matrix.example.com` to be the Matrix server handling Matrix stuff for `example.com` by [Server Delegation](howto-server-delegation.md). During the installation procedure, we recommend that you set up server delegation using the [.well-known](configuring-well-known.md) method.
-
-If you're fine with uglier identifiers (`@user:matrix.example.com`, which is the equivalent of having an email address like `bob@mail.company.com`, instead of just `bob@company.com`), you can do that as well using the following configuration in your `vars.yml` file:
+Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
 ```yaml
 # This is what your identifiers are like (e.g. `@bob:matrix.example.com`).
@@ -251,23 +256,33 @@ matrix_domain: "matrix.example.com"
 # This is where Matrix services
 matrix_server_fqn_matrix: "matrix.example.com"
 
-# This is where you access the Element web UI from (if enabled via `matrix_client_element_enabled: true`; enabled by default).
+# This is where you access the Element Web from (if enabled via `matrix_client_element_enabled: true`; enabled by default).
 # This and the Matrix FQN (see above) are expected to be on the same server.
 #
 # Feel free to use `element.matrix.example.com`, if you'd prefer that.
 matrix_server_fqn_element: "element.example.com"
 
-# This is where you access Dimension (if enabled via `matrix_dimension_enabled: true`; NOT enabled by default).
+# This is where you access Etherpad (if enabled via `etherpad_enabled: true`; NOT enabled by default).
 #
-# Feel free to use `dimension.matrix.example.com`, if you'd prefer that.
-matrix_server_fqn_dimension: "dimension.example.com"
-
-# This is where you access Jitsi (if enabled via `jitsi_enabled: true`; NOT enabled by default).
-#
-# Feel free to use `jitsi.matrix.example.com`, if you'd prefer that.
-matrix_server_fqn_jitsi: "jitsi.example.com"
+# Feel free to use `etherpad.matrix.example.com`, if you'd prefer that.
+matrix_server_fqn_etherpad: "etherpad.example.com"
 ```
 
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+**Notes**:
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
+
+- Without setting up [server delegation](howto-server-delegation.md) to `matrix.example.com`, your user IDs will be like `@alice:matrix.example.com`. This is equivalent to having an email address like `bob@mail.company.com`, instead of just `bob@company.com`.
+
 ### I don't use the base domain for anything. How am I supposed to set up Server Delegation for Matrix services?
 
 If you don't use your base domain for anything, then it's hard for you to "serve files over HTTPS" on it -- something we ask you to do for the [.well-known](configuring-well-known.md) setup (needed for [Server Delegation](howto-server-delegation.md)).
@@ -356,24 +371,29 @@ Check each role's `roles/*/*/defaults/main.yml` for the corresponding variable a
 
 **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`).
 
-
 ## Installation
 
 ### How do I run the installation?
 
 See [Installing](installing.md) to learn how to use Ansible to install Matrix services.
 
-Of course, don't just jump straight to Installing. Rather, start at [Prerequisites](prerequisites.md) and get guided from there (into [setting up DNS](configuring-dns.md), [configuring the playbook](configuring-playbook.md), etc).
+However, we recommend you to follow our installation guide, instead of jumping straight to installing.
+
+There are two guides available:
+
+- ⚡ **[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".
+
+- **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.
 
 ### I installed Synapse some other way. Can I migrate such a setup to the playbook?
 
 Yes, you can.
 
-You generally need to do a playbook installation (start at the [Prerequisites](prerequisites.md) page), followed by importing your existing data into it.
+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.
 
-This Ansible playbook guides you into installing a server for `example.com` (user identifiers are like this: `@user: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-matrix-example-com-without-involving-the-base-domain)
+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)
 
-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).
+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).
 
 ### I've downloaded Ansible and the playbook on the server. It can't connect using SSH.
 
@@ -383,7 +403,6 @@ It can perform a local connection instead. Just set `ansible_connection=local` a
 
 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.
 
-
 ## Troubleshooting
 
 ### I get "Error response from daemon: configured logging driver does not support reading" when I do `docker logs matrix-synapse`.
@@ -423,7 +442,6 @@ RateLimitBurst=0
 Storage=persistent
 ```
 
-
 ## Maintenance
 
 ### Do I need to do anything to keep my Matrix server updated?
@@ -446,12 +464,10 @@ We haven't documented this properly yet, but the general advice is to:
 
 - back up all `/matrix` files, except for `/matrix/postgres/data` (you already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` (this directory may exist and contain your old data if you've [performed a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql)).
 
-You can later restore these roughly like this:
+You can later restore these by:
 
-- restore the `/matrix` directory and files on the new server manually
-- run the playbook again (see [Installing](installing.md)), but **don't** start services yet (**don't run** `... --tags=start`). This step will fix any file permission mismatches and will also set up additional software (Docker, etc.) and files on the server (systemd service, etc.).
-- perform a Postgres database import (see [Importing Postgres](importing-postgres.md)) to restore your database backup
-- start services (see [Starting the services](installing.md#starting-the-services))
+- Restoring the `/matrix` directory and files on the new server manually
+- Following the instruction described on [Installing a server into which you'll import old data](installing.md#installing-a-server-into-which-youll-import-old-data)
 
 If your server's IP address has changed, you may need to [set up DNS](configuring-dns.md) again.
 
@@ -468,3 +484,11 @@ SSL certificates are managed automatically by the [Traefik](https://doc.traefik.
 If you're having trouble with SSL certificate renewal, check the Traefik logs (`journalctl -fu matrix-traefik`).
 
 If you're [using your own webserver](configuring-playbook-own-webserver.md) instead of the integrated one (Traefik), you should investigate in another way.
+
+## Miscellaneous
+
+### I would like to see this favorite service of mine integrated and become available on my Matrix server. How can I request it?
+
+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). 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.
+
+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.
diff --git a/docs/getting-the-playbook.md b/docs/getting-the-playbook.md
index ea172a499..4db76c5c6 100644
--- a/docs/getting-the-playbook.md
+++ b/docs/getting-the-playbook.md
@@ -1,5 +1,7 @@
 # Getting the playbook
 
+<sup>[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > Getting the playbook > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)</sup>
+
 This Ansible playbook is meant to be executed on your own computer (not the Matrix server).
 
 In special cases (if your computer cannot run Ansible, etc.) you may put the playbook on the server as well.
@@ -10,20 +12,18 @@ You can retrieve the playbook's source code by:
 
 - [Downloading the playbook as a ZIP archive](#downloading-the-playbook-as-a-zip-archive) (not recommended)
 
-
 ## Using git to get the playbook
 
 We recommend using the [git](https://git-scm.com/) tool to get the playbook's source code, because it lets you easily keep up to date in the future when [Maintaining services](maintenance-upgrading-services.md).
 
 Once you've installed git on your computer, you can go to any directory of your choosing and run the following command to retrieve the playbook's source code:
 
-```bash
+```sh
 git clone https://github.com/spantaleev/matrix-docker-ansible-deploy.git
 ```
 
 This will create a new `matrix-docker-ansible-deploy` directory. You're supposed to execute all other installation commands inside that directory.
 
-
 ## Downloading the playbook as a ZIP archive
 
 Alternatively, you can download the playbook as a ZIP archive. This is not recommended, as it's not easy to keep up to date with future updates. We suggest you [use git](#using-git-to-get-the-playbook) instead.
@@ -32,7 +32,6 @@ The latest version is always at the following URL: https://github.com/spantaleev
 
 You can extract this archive anywhere. You'll get a directory called `matrix-docker-ansible-deploy-master`. You're supposed to execute all other installation commands inside that directory.
 
-
 ---------------------------------------------
 
-No matter which method you've used to download the playbook, you can proceed by [Configuring the playbook](configuring-playbook.md).
+[▶️](configuring-playbook.md) No matter which method you've used to download the playbook, you can proceed by [Configuring the playbook](configuring-playbook.md).
diff --git a/docs/howto-server-delegation.md b/docs/howto-server-delegation.md
index 7b61553d1..429e06982 100644
--- a/docs/howto-server-delegation.md
+++ b/docs/howto-server-delegation.md
@@ -1,20 +1,23 @@
 # Server Delegation
 
-To have a server on a subdomain (e.g. `matrix.example.com`) handle Matrix federation traffic for the base domain (`example.com`), we need to instruct the Matrix network of such a delegation.
+By default, this playbook sets up services on your Matrix server (`matrix.example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection.
 
-By default, this playbook guides you into setting up [Server Delegation via a well-known file](#server-delegation-via-a-well-known-file). However, that method may have some downsides that are not to your liking. Hence this guide about alternative ways to set up Server Delegation.
+Server delegation can be configured in either of these ways:
 
-It is a complicated matter, so unless you are affected by the [Downsides of well-known-based Server Delegation](#downsides-of-well-known-based-server-delegation), we suggest you stay on the simple/default path.
+- [Setting up a `/.well-known/matrix/server` file](#server-delegation-via-a-well-known-file) on the base domain (`example.com`)
+- [Setting up a `_matrix._tcp` DNS SRV record](#server-delegation-via-a-dns-srv-record-advanced)
 
+Both methods have their place and will continue to do so. You only need to use just one of these delegation methods.
+
+For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file. However, that method may have some downsides that are not to your liking. Hence this guide about alternative ways to set up Server Delegation.
+
+**Note**: as an alternative, it is possible to install the server such that it uses only the `matrix.example.com` domain (instead of identifying as the shorter base domain - `example.com`). This should be helpful if you are not in control of anything on the base domain (`example.com`). In this case, you would not need to configure server delegation, but you would need to add other configuration. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ.
 
 ## Server Delegation via a well-known file
 
-Serving a `/.well-known/matrix/server` file from the base domain is the most straightforward way to set up server delegation, but it suffers from some problems that we list in [Downsides of well-known-based Server Delegation](#downsides-of-well-known-based-server-delegation).
-
-As we already mention in [Configuring DNS](configuring-dns.md) and [Configuring Service Discovery via .well-known](configuring-well-known.md), this playbook already properly guides you into setting up such delegation by means of a `/.well-known/matrix/server` file served from the base domain (`example.com`).
-
-If this is okay with you, feel free to not read ahead.
+This playbook recommends you to set up server delegation by means of a `/.well-known/matrix/server` file served from the base domain (`example.com`), as this is the most straightforward way to set up the delegation.
 
+To configure server delegation with the well-known file, check this section on [Configuring Service Discovery via .well-known](configuring-well-known.md): [Installing well-known files on the base domain's server](configuring-well-known.md#installing-well-known-files-on-the-base-domain-s-server)
 
 ### Downsides of well-known-based Server Delegation
 
@@ -30,10 +33,9 @@ Server Delegation by means of a `/.well-known/matrix/server` file is the most st
 
 Otherwise, you can decide to go against the default for this playbook, and instead set up [Server Delegation via a DNS SRV record (advanced)](#server-delegation-via-a-dns-srv-record-advanced) (much more complicated).
 
-
 ## Server Delegation via a DNS SRV record (advanced)
 
-**Note**: doing Server Delegation via a DNS SRV record is a more **advanced** way to do it and is not the default for this playbook. This is usually **much more complicated** to set up, so **we don't recommend it**. If you're not an experience sysadmin, you'd better stay away from this.
+**Note**: doing Server Delegation via a DNS SRV record is a more **advanced** way to do it and is not the default for this playbook. This is usually **much more complicated** to set up, so **we don't recommend it**. If you're not an experienced sysadmin, you'd better stay away from this.
 
 As per the [Server-Server spec](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), it's possible to do Server Delegation using only a SRV record (without a `/.well-known/matrix/server` file).
 
@@ -47,9 +49,9 @@ To use DNS SRV record validation, you need to:
 
 - ensure that you are serving the Matrix Federation API (tcp/8448) with a certificate for `example.com` (not `matrix.example.com`!). Getting this certificate to the `matrix.example.com` server may be complicated. The playbook's automatic SSL obtaining/renewal flow will likely not work and you'll need to copy certificates around manually. See below.
 
-For more details on [how to configure the playbook to work with SRV delegation](howto-srv-server-delegation.md)
+For more details on how to configure the playbook to work with SRV delegation, take a look at this documentation: [Server Delegation via a DNS SRV record (advanced)](howto-srv-server-delegation.md)
 
-### Obtaining certificates
+### Obtain certificates
 
 How you can obtain a valid certificate for `example.com` on the `matrix.example.com` server is up to you.
 
@@ -57,34 +59,15 @@ If `example.com` and `matrix.example.com` are hosted on the same machine, you ca
 
 If `example.com` and `matrix.example.com` are not hosted on the same machine, you can copy over the certificate files manually. Don't forget that they may get renewed once in a while, so you may also have to transfer them periodically. How often you do that is up to you, as long as the certificate files don't expire.
 
-
 ### Serving the Federation API with your certificates
 
 Regardless of which method for obtaining certificates you've used, once you've managed to get certificates for your base domain onto the `matrix.example.com` machine you can put them to use.
 
 Based on your setup, you have different ways to go about it:
 
-- [Server Delegation](#server-delegation)
-	- [Server Delegation via a well-known file](#server-delegation-via-a-well-known-file)
-		- [Downsides of well-known-based Server Delegation](#downsides-of-well-known-based-server-delegation)
-	- [Server Delegation via a DNS SRV record (advanced)](#server-delegation-via-a-dns-srv-record-advanced)
-		- [Obtaining certificates](#obtaining-certificates)
-		- [Serving the Federation API with your certificates](#serving-the-federation-api-with-your-certificates)
-		- [Serving the Federation API with your certificates and another webserver](#serving-the-federation-api-with-your-certificates-and-another-webserver)
-		- [Serving the Federation API with your certificates and Synapse handling Federation](#serving-the-federation-api-with-your-certificates-and-synapse-handling-federation)
+#### Serving the Federation API with your certificates and Synapse handling Federation
 
-
-
-
-### Serving the Federation API with your certificates and another webserver
-
-**If you are using some other webserver**, you can set up reverse-proxying for the `tcp/8448` port by yourself. Make sure to use the proper certificates for `example.com` (not for `matrix.example.com`) when serving the `tcp/8448` port.
-
-As recommended in our [Fronting the integrated reverse-proxy webserver with another reverse-proxy](./configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) documentation section, we recommend you to expose the Matrix Federation entrypoint from traffic at a local port (e.g. `127.0.0.1:8449`), so your reverese-proxy should send traffic there.
-
-### Serving the Federation API with your certificates and Synapse handling Federation
-
-**Alternatively**, you can let Synapse handle Federation by itself.
+You can let Synapse handle Federation by itself.
 
 To do that, make sure the certificate files are mounted into the Synapse container:
 
@@ -102,3 +85,9 @@ matrix_synapse_tls_private_key_path: /some/path/inside/the/container/private.key
 ```
 
 Make sure to reload Synapse once in a while (`systemctl reload matrix-synapse`), so that newer certificates can kick in. Reloading doesn't cause any downtime.
+
+#### Serving the Federation API with your certificates and another webserver
+
+**Alternatively**, if you are using another webserver, you can set up reverse-proxying for the `tcp/8448` port by yourself. Make sure to use the proper certificates for `example.com` (not for `matrix.example.com`) when serving the `tcp/8448` port.
+
+As recommended in our [Fronting the integrated reverse-proxy webserver with another reverse-proxy](./configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) documentation section, we recommend you to expose the Matrix Federation entrypoint from traffic at a local port (e.g. `127.0.0.1:8449`), so your reverese-proxy should send traffic there.
diff --git a/docs/howto-srv-server-delegation.md b/docs/howto-srv-server-delegation.md
index 9de7b297e..7cf484712 100644
--- a/docs/howto-srv-server-delegation.md
+++ b/docs/howto-srv-server-delegation.md
@@ -14,11 +14,11 @@ This means that this is **limited to the list of DNS providers supported by Trae
 
 The up-to-date list can be accessed on [traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers)
 
-## The changes
+## Adjusting the playbook configuration
 
 **Note**: the changes below instruct you how to do this for a basic Synapse installation. You will need to adapt the variable name and the content of the labels:
 
-- if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md) or [Dendrite](./configuring-playbook-dendrite.md))
+- if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md), [Conduwuit](./configuring-playbook-conduwuit.md) or [Dendrite](./configuring-playbook-dendrite.md))
 - if you're using [Synapse with workers enabled](./configuring-playbook-synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled: true`). In that case, it's actually the `matrix-synapse-reverse-proxy-companion` service which has Traefik labels attached
 
 Also, all instructions below are from an older version of the playbook and may not work anymore.
@@ -73,7 +73,7 @@ traefik_configuration_extension_yaml: |
         storage: {{ traefik_config_certificatesResolvers_acme_storage | to_json }}
 
 # 2. Configure the environment variables needed by Rraefik to automate the ACME DNS Challenge (example for Cloudflare)
-traefik_environment_variables: |
+traefik_environment_variables_additional_variables: |
   CF_API_EMAIL=redacted
   CF_ZONE_API_TOKEN=redacted
   CF_DNS_API_TOKEN=redacted
@@ -83,17 +83,17 @@ traefik_environment_variables: |
 traefik_certResolver_primary: dns
 ```
 
-## Adjust Coturn's configuration
+## Adjust coturn's configuration
 
-The last step is to alter the generated Coturn configuration.
+The last step is to alter the generated coturn configuration.
 
-By default, Coturn is configured to wait on the certificate for the `matrix.` subdomain using an [instantiated systemd service](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Service%20Templates) using the domain name as the parameter for this service. However, we need to serve the wildcard certificate, which is incompatible with systemd, it will try to expand the `*`, which will break and prevent Coturn from starting.
+By default, coturn is configured to wait on the certificate for the `matrix.` subdomain using an [instantiated systemd service](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Service%20Templates) using the domain name as the parameter for this service. However, we need to serve the wildcard certificate, which is incompatible with systemd, it will try to expand the `*`, which will break and prevent coturn from starting.
 
-We also need to indicate to Coturn where the wildcard certificate is.
+We also need to indicate to coturn where the wildcard certificate is.
 
-**⚠ WARNING ⚠** : On first start of the services, Coturn might still fail to start because Traefik is still in the process of obtaining the certificates. If you still get an error, make sure Traefik obtained the certificates and restart the Coturn service (`just start-group coturn`).
+⚠️ **Warning** : On first start of the services, coturn might still fail to start because Traefik is still in the process of obtaining the certificates. If you still get an error, make sure Traefik obtained the certificates and restart the coturn service (`just start-group coturn`).
 
-This should not happen again afterwards as Traefik will renew certificates well before their expiry date, and the Coturn service is setup to restart periodically.
+This should not happen again afterwards as Traefik will renew certificates well before their expiry date, and the coturn service is setup to restart periodically.
 
 ```yaml
 # Only depend on docker.service, this removes the dependency on the certificate exporter, might imply the need to manually restart coturn on the first installation once the certificates are obtained, afterwards, the reload service should handle things
@@ -153,13 +153,13 @@ traefik_configuration_extension_yaml: |
 traefik_certResolver_primary: "dns"
 
 # Configure the environment variables needed by Traefik to automate the ACME DNS Challenge (example for Cloudflare)
-traefik_environment_variables: |
+traefik_environment_variables_additional_variables: |
   CF_API_EMAIL=redacted
   CF_ZONE_API_TOKEN=redacted
   CF_DNS_API_TOKEN=redacted
   LEGO_DISABLE_CNAME_SUPPORT=true
 
-# Only depend on docker.service, this removes the dependency on the certificate exporter, might imply the need to manually restart Coturn on the first installation once the certificates are obtained, afterwards, the reload service should handle things
+# Only depend on docker.service, this removes the dependency on the certificate exporter, might imply the need to manually restart coturn on the first installation once the certificates are obtained, afterwards, the reload service should handle things
 matrix_coturn_systemd_required_services_list: ['docker.service']
 
 # This changes the path of the loaded certificate, while maintaining the original functionality, we're now loading the wildcard certificate.
diff --git a/docs/importing-postgres.md b/docs/importing-postgres.md
index 762900c64..44c49c7c6 100644
--- a/docs/importing-postgres.md
+++ b/docs/importing-postgres.md
@@ -3,18 +3,16 @@
 Run this if you'd like to import your database from a previous installation.
 (don't forget to import your Synapse `media_store` files as well - see [the importing-synape-media-store guide](importing-synapse-media-store.md)).
 
-
 ## Prerequisites
 
 For this to work, **the database name in Postgres must match** what this playbook uses. This playbook uses a Postgres database name of `synapse` by default (controlled by the `matrix_synapse_database_database` variable). If your database name differs, be sure to change `matrix_synapse_database_database` to your desired name and to re-run the playbook before proceeding.
 
 The playbook supports importing Postgres dump files in **text** (e.g. `pg_dump > dump.sql`) or **gzipped** formats (e.g. `pg_dump | gzip -c > dump.sql.gz`). Importing multiple databases (as dumped by `pg_dumpall`) is also supported.
 
-The migration might be a good moment, to "reset" a not properly working bridge. Be aware, that it might affect all users (new link to bridge, new rooms, ...)
+The migration might be a good moment, to "reset" a not properly working bridge. Be aware, that it might affect all users (new link to bridge, new rooms, …)
 
 Before doing the actual import, **you need to upload your Postgres dump file to the server** (any path is okay).
 
-
 ## Importing
 
 To import, run this command (make sure to replace `SERVER_PATH_TO_POSTGRES_DUMP_FILE` with a file path on your server):
@@ -34,6 +32,7 @@ just run-tags import-postgres \
 ## Troubleshooting
 
 ### Table Ownership
+
 A table ownership issue can occur if you are importing from a Synapse installation which was both:
 
  - migrated from SQLite to Postgres, and
@@ -56,7 +55,7 @@ ALTER TABLE public.account_data OWNER TO synapse_user;
 ALTER TABLE public.account_data_max_stream_id OWNER TO synapse_user;
 ALTER TABLE public.account_validity OWNER TO synapse_user;
 ALTER TABLE public.application_services_state OWNER TO synapse_user;
-...
+…
 ```
 
 It can be worked around by changing the username to `synapse`, for example by using `sed`:
@@ -65,7 +64,7 @@ It can be worked around by changing the username to `synapse`, for example by us
 $ sed -i "s/OWNER TO synapse_user;/OWNER TO synapse;/g" homeserver.sql
 ```
 
-This uses sed to perform an 'in-place' (`-i`) replacement globally (`/g`), searching for `synapse_user` and replacing with `synapse` (`s/synapse_user/synapse`). If your database username was different, change `synapse_user` to that username instead. Expand search/replace statement as shown in example above, in case of old user name like `matrix` - replacing `matrix` only would... well - you can imagine.
+This uses sed to perform an 'in-place' (`-i`) replacement globally (`/g`), searching for `synapse_user` and replacing with `synapse` (`s/synapse_user/synapse`). If your database username was different, change `synapse_user` to that username instead. Expand search/replace statement as shown in example above, in case of old user name like `matrix` - replacing `matrix` only would… well - you can imagine.
 
 Note that if the previous import failed with an error it may have made changes which are incompatible with re-running the import task right away; if you do so it may fail with an error such as:
 
@@ -86,6 +85,7 @@ In this case you can use the command suggested in the import task to clear the d
 Now on your local machine run `just run-tags setup-postgres` to prepare the database roles etc.
 
 If not, you probably get this error. `synapse` is the correct table owner, but the role is missing in database.
+
 ```
 "ERROR:  role synapse does not exist"
 ```
@@ -94,7 +94,7 @@ Once the database is clear and the ownership of the tables has been fixed in the
 
 Check, if `--dbname` is set to `synapse` (not `matrix`) and replace paths (or even better, copy this line from your terminal)
 
-```
+```sh
 /usr/bin/env docker run --rm --name matrix-postgres-import --log-driver=none --user=998:1001 --cap-drop=ALL --network=matrix --env-file=/matrix/postgres/env-postgres-psql --mount type=bind,src=/migration/synapse_dump.sql,dst=/synapse_dump.sql,ro --entrypoint=/bin/sh docker.io/postgres:15.0-alpine -c "cat /synapse_dump.sql | grep -vE '^(CREATE|ALTER) ROLE (matrix)(;| WITH)' | grep -vE '^CREATE DATABASE (matrix)\s' | psql -v ON_ERROR_STOP=1 -h matrix-postgres --dbname=synapse"
 ```
 
diff --git a/docs/importing-synapse-media-store.md b/docs/importing-synapse-media-store.md
index 97d89c4e9..dd1fe9671 100644
--- a/docs/importing-synapse-media-store.md
+++ b/docs/importing-synapse-media-store.md
@@ -2,22 +2,22 @@
 
 Run this if you'd like to import your `media_store` files from a previous installation of Synapse.
 
-
 ## Prerequisites
 
 Before doing the actual data restore, **you need to upload your media store directory to the server** (any path is okay).
 
-If you are [Storing Matrix media files on Amazon S3](configuring-playbook-s3.md) (optional), restoring with this tool is not possible right now.
+If you are [storing Matrix media files on Amazon S3](configuring-playbook-s3.md) (optional), restoring with this tool is not possible right now.
 
 As an alternative, you can perform a manual restore using the [AWS CLI tool](https://aws.amazon.com/cli/) (e.g. `aws s3 sync /path/to/server/media_store/. s3://name-of-bucket/`)
 
 **Note for Mac users**: Due to case-sensitivity issues on certain Mac filesystems (HFS or HFS+), filename corruption may occur if you copy a `media_store` directory to your Mac. If you're transferring a `media_store` directory between 2 servers, make sure you do it directly (from server to server with a tool such as [rsync](https://rsync.samba.org/)), and not by downloading the files to your Mac.
 
-
 ## Importing
 
 Run this command (make sure to replace `<server-path-to-media_store>` with a path on your server):
 
-	ansible-playbook -i inventory/hosts setup.yml --extra-vars='server_path_media_store=<server-path-to-media_store>' --tags=import-synapse-media-store
+```sh
+ansible-playbook -i inventory/hosts setup.yml --extra-vars='server_path_media_store=<server-path-to-media_store>' --tags=import-synapse-media-store
+```
 
 **Note**: `<server-path-to-media_store>` must be a file path to a `media_store` directory on the server (not on your local machine!).
diff --git a/docs/importing-synapse-sqlite.md b/docs/importing-synapse-sqlite.md
index b850cfa64..2453e8cfc 100644
--- a/docs/importing-synapse-sqlite.md
+++ b/docs/importing-synapse-sqlite.md
@@ -6,7 +6,6 @@ While this playbook only supports running Synapse in combination with PostgreSQL
 
 If you have such a Synapse setup and wish to migrate it to one managed by the playbook (and over to PostgreSQL), this documentation page is for you.
 
-
 ## Prerequisites
 
 Before doing the actual import:
diff --git a/docs/installing.md b/docs/installing.md
index 48103c2be..c4eda3b9f 100644
--- a/docs/installing.md
+++ b/docs/installing.md
@@ -1,45 +1,35 @@
 # Installing
 
-If you've [configured your DNS](configuring-dns.md) and have [configured the playbook](configuring-playbook.md), you can start the installation procedure.
+<sup>[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > Installing</sup>
 
-**Before installing** and each time you update the playbook in the future, you will need to update the Ansible roles in this playbook by running `just roles`. `just roles` is a shortcut (a `roles` target defined in [`justfile`](../justfile) and executed by the [`just`](https://github.com/casey/just) utility) which ultimately runs [agru](https://github.com/etkecc/agru) or [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) (depending on what is available in your system) to download Ansible roles. If you don't have `just`, you can also manually run the `roles` commands seen in the `justfile`.
+If you've configured your DNS records and the playbook, you can start the installation procedure.
 
-There's another shortcut (`just update`) which updates the playbook (`git pull`) and updates roles (`just update`) at the same time.
+## Update Ansible roles
 
+Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside.
 
-## Playbook tags introduction
+To update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file), run:
+
+- either: `just update`
+- or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)
+
+If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`
+
+For details about `just` commands, take a look at: [Running `just` commands](just.md).
+
+## Install Matrix server and services
 
 The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks.
 
-The general command syntax is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`
+The general command syntax for installation (and also maintenance) is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`. It is recommended to get yourself familiar with the [playbook tags](playbook-tags.md) before proceeding.
 
-Here are some playbook tags that you should be familiar with:
+If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the all Ansible commands.
 
-- `setup-all` - runs all setup tasks (installation and uninstallation) for all components, but does not start/restart services
-
-- `install-all` - like `setup-all`, but skips uninstallation tasks. Useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove components, you'd need to run `setup-all` though, or these components will still remain installed
-
-- `setup-SERVICE` (e.g. `setup-bot-postmoogle`) - runs the setup tasks only for a given role, but does not start/restart services. You can discover these additional tags in each role (`roles/**/tasks/main.yml`). Running per-component setup tasks is **not recommended**, as components sometimes depend on each other and running just the setup tasks for a given component may not be enough. For example, setting up the [mautrix-telegram bridge](configuring-playbook-bridge-mautrix-telegram.md), in addition to the `setup-mautrix-telegram` tag, requires database changes (the `setup-postgres` tag) as well as reverse-proxy changes (the `setup-nginx-proxy` tag).
-
-- `install-SERVICE` (e.g. `install-bot-postmoogle`) - like `setup-SERVICE`, but skips uninstallation tasks. See `install-all` above for additional information.
-
-- `start` - starts all systemd services and makes them start automatically in the future
-
-- `stop` - stops all systemd services
-
-- `ensure-matrix-users-created` - a special tag which ensures that all special users needed by the playbook (for bots, etc.) are created
-
-`setup-*` tags and `install-*` tags **do not start services** automatically, because you may wish to do things before starting services, such as importing a database dump, restoring data from another server, etc.
-
-
-## 1. Installing Matrix
-
-If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the all Ansible commands
-
-If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to all Ansible commands
+If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to all Ansible commands.
 
 There 2 ways to start the installation process - depending on whether you're [Installing a brand new server (without importing data)](#installing-a-brand-new-server-without-importing-data) or [Installing a server into which you'll import old data](#installing-a-server-into-which-youll-import-old-data).
 
+**Note**: if you are migrating from an old server to a new one, take a look at [this guide](maintenance-migrating.md) instead. This is an easier and more straightforward way than installing a server and importing old data into it.
 
 ### Installing a brand new server (without importing data)
 
@@ -51,19 +41,20 @@ ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-u
 
 This will do a full installation and start all Matrix services.
 
-Proceed to [Maintaining your setup in the future](#2-maintaining-your-setup-in-the-future) and [Finalize the installation](#3-finalize-the-installation)
-
+**Note**: if the command does not work as expected, make sure that you have properly installed and configured software required to run the playbook, as described on [Prerequisites](prerequisites.md).
 
 ### Installing a server into which you'll import old data
 
 If you will be importing data into your newly created Matrix server, install it, but **do not** start its services just yet. Starting its services or messing with its database now will affect your data import later on.
 
-To do the installation **without** starting services, run only the `install-all` tag:
+To do the installation **without** starting services, run `ansible-playbook` with the `install-all` tag only:
 
 ```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=install-all
 ```
 
+⚠️ **Warning**: do not run the just "recipe" `just install-all` instead, because it automatically starts services at the end of execution. See: [Difference between playbook tags and shortcuts](just.md#difference-between-playbook-tags-and-shortcuts)
+
 When this command completes, services won't be running yet.
 
 You can now:
@@ -74,39 +65,95 @@ You can now:
 
 - [Importing `media_store` data files from an existing Synapse installation](importing-synapse-media-store.md) (optional)
 
-.. and then proceed to starting all services:
+… and then proceed to starting all services:
 
 ```sh
-ansible-playbook -i inventory/hosts setup.yml --tags=start
+ansible-playbook -i inventory/hosts setup.yml --tags=ensure-matrix-users-created,start
 ```
 
-Proceed to [Maintaining your setup in the future](#2-maintaining-your-setup-in-the-future) and [Finalize the installation](#3-finalize-the-installation)
+## Create your user account
 
+ℹ️ *You can skip this step if you have installed a server and imported old data to it.*
 
-## 2. Maintaining your setup in the future
+As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server.
 
-Feel free to **re-run the setup command any time** you think something is off with the server configuration. Ansible will take your configuration and update your server to match.
+After creating the user account, you can log in to it with [Element Web](configuring-playbook-client-element-web.md) that this playbook has installed for you at this URL: `https://element.example.com/`.
 
-Note that if you remove components from `vars.yml`, or if we switch some component from being installed by default to not being installed by default anymore, you'd need to run the setup command with `--tags=setup-all` instead of `--tags=install-all`. See [Playbook tags introduction](#playbook-tags-introduction)
+To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer.
 
-A way to invoke these `ansible-playbook` commands with less typing in the future is to use [just](https://github.com/casey/just) to run them: `just install-all` or `just setup-all`. See [our `justfile`](../justfile) for more information.
+**Notes**:
+- Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`
+- For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)
+- Use `admin=yes` to make your user account an administrator of the Matrix server
 
+```sh
+ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=YOUR_USERNAME_HERE password=YOUR_PASSWORD_HERE admin=yes' --tags=register-user
 
-## 3. Finalize the installation
+# Example: ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=alice password=secret-password admin=yes' --tags=register-user
+```
 
-Now that services are running, you need to **finalize the installation process** (required for federation to work!) by [Configuring Service Discovery via .well-known](configuring-well-known.md).
+Feel free to create as many accounts (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your account only (with `admin=yes`), and others should be created with `admin=no`.
 
+For more information, see the documentation for [registering users](registering-users.md).
 
-## 4. Things to do next
+## Finalize the installation
 
-After you have started the services and **finalized the installation process** (required for federation to work!) by [Configuring Service Discovery via .well-known](configuring-well-known.md), you can:
+Now you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network.
+
+This is required for federation to work! Without a proper configuration, your server will effectively not be part of the Matrix network.
+
+To configure the delegation, you have these two options. Choose one of them according to your situation.
+
+- If you can afford to point the base domain at the Matrix server, follow the instructions below which guide you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server. It will enable you to use a Matrix user ID like `@alice:example.com` while hosting services on a subdomain like `matrix.example.com`.
+- Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot "serve the base domain" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server), but feel free to familiarize yourself with all [server delegation (redirection) options](howto-server-delegation.md).
+
+To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+
+```yaml
+matrix_static_files_container_labels_base_domain_enabled: true
+```
+
+After configuring the playbook, run the command below:
+
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=install-matrix-static-files,start
+```
+
+## Things to do next
+
+After finilizing the installation, you can:
 
 - [check if services work](maintenance-checking-services.md)
-- or [create your first Matrix user account](registering-users.md)
 - or [set up additional services](configuring-playbook.md#other-configuration-options) (bridges to other chat networks, bots, etc.)
 - or learn how to [upgrade services when new versions are released](maintenance-upgrading-services.md)
 - or learn how to [maintain your server](faq.md#maintenance)
 - or join some Matrix rooms:
-  * via the *Explore rooms* feature in Element or some other client, or by discovering them using this [matrix-static list](https://view.matrix.org). **Note**: joining large rooms may overload small servers.
+  * 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.
   * 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.
 - or help make this playbook better by contributing (code, documentation, or [coffee/beer](https://liberapay.com/s.pantaleev/donate))
+
+### Maintaining your setup in the future
+
+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**.
+
+The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities.
+
+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.
+
+For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)
+
+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.
+
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Note**: see [this page on the playbook tags](playbook-tags.md) for more information about those tags.
+
+### Make full use of `just` shortcut commands
+
+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.
+
+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.
+
+You can learn about the shortcut commands on this page: [Running `just` commands](just.md)
diff --git a/docs/just.md b/docs/just.md
new file mode 100644
index 000000000..ecc09e495
--- /dev/null
+++ b/docs/just.md
@@ -0,0 +1,38 @@
+# Running `just` commands
+
+We have previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers [`ansible-galaxy`](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html)). Our [`Makefile`](../Makefile) is still around, and you can still run these commands.
+
+In addition, we have added support for running commands via [`just`](https://github.com/casey/just) - a more modern command-runner alternative to `make`. It can be used to invoke `ansible-playbook` commands with less typing.
+
+The `just` utility executes shortcut commands (called as "recipes"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile). Most of the just recipes have no corresponding `Makefile` targets.
+
+For some recipes such as `just update`, our `justfile` recommends installing [`agru`](https://github.com/etkecc/agru) (a faster alternative to `ansible-galaxy`) to speed up the process.
+
+Here are some examples of shortcuts:
+
+| Shortcut                                       | Result                                                                                                         |
+|------------------------------------------------|----------------------------------------------------------------------------------------------------------------|
+| `just roles`                                   | Install the necessary Ansible roles pinned in [`requirements.yml`](../requirements.yml)                        |
+| `just update`                                  | Run `git pull` (to update the playbook) and install the Ansible roles                                          |
+| `just install-all`                             | Run `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start`       |
+| `just setup-all`                               | Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start`         |
+| `just install-all --ask-vault-pass`            | Run commands with additional arguments (`--ask-vault-pass` will be appended to the above installation command) |
+| `just run-tags install-mautrix-slack,start`    | Run specific playbook tags (here `install-mautrix-slack` and `start`)                                          |
+| `just install-service mautrix-slack`           | Run `just run-tags install-mautrix-slack,start` with even less typing                                          |
+| `just start-all`                               | (Re-)starts all services                                                                                       |
+| `just stop-group postgres`                     | Stop only the Postgres service                                                                                 |
+| `just register-user alice secret-password yes` | Registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)                 |
+
+While [our documentation on prerequisites](prerequisites.md) lists `just` as one of the requirements for installation, using `just` is optional. If you find it difficult to install it, do not find it useful, or want to prefer raw `ansible-playbook` commands for some reason, feel free to run all commands manually. For example, you can run `ansible-galaxy` directly to install the Ansible roles: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`.
+
+## Difference between playbook tags and shortcuts
+
+It is worth noting that `just` "recipes" are different from [playbook tags](playbook-tags.md). The recipes are shortcuts of commands defined in `justfile` and can be executed by the `just` program only, while the playbook tags are available for the raw `ansible-playbook` commands as well. Please be careful not to confuse them.
+
+For example, these two commands are different:
+- `just install-all`
+- `ansible-playbook -i inventory/hosts setup.yml --tags=install-all`
+
+The just recipe runs `ensure-matrix-users-created` and `start` tags after `install-all`, while the latter runs only `install-all` tag. The correct shortcut of the latter is `just run-tags install-all`.
+
+Such kind of difference sometimes matters. For example, when you install a Matrix server into which you will import old data (see [here](installing.md#installing-a-server-into-which-youll-import-old-data)), you are not supposed to run `just install-all` or `just setup-all`, because these commands start services immediately after installing components which may prevent your from importing old data.
diff --git a/docs/maintenance-and-troubleshooting.md b/docs/maintenance-and-troubleshooting.md
index b6262a63a..0ab46f900 100644
--- a/docs/maintenance-and-troubleshooting.md
+++ b/docs/maintenance-and-troubleshooting.md
@@ -3,7 +3,8 @@
 ## How to see the current status of your services
 
 You can check the status of your services by using `systemctl status`. Example:
-```
+
+```sh
 sudo systemctl status matrix-synapse
 
 ● matrix-synapse.service - Synapse server
@@ -21,12 +22,11 @@ To view systemd-journald logs using [journalctl](https://man.archlinux.org/man/j
 sudo journalctl -fu matrix-synapse
 ```
 
-
-## Increasing Synapse logging
+## Increase logging verbosity
 
 Because the [Synapse](https://github.com/element-hq/synapse) Matrix server 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`.
 
-If you'd like to debug an issue or [report a Synapse bug](https://github.com/matrix-org/synapse/issues/new/choose) to the developers, it'd be better if you temporarily increasing the logging level to `INFO`.
+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 increasing the logging level to `INFO`.
 
 Example configuration (`inventory/host_vars/matrix.example.com/vars.yml`):
 
@@ -41,14 +41,13 @@ Re-run the playbook after making these configuration changes.
 ## Remove unused Docker data
 
 You can free some disk space from Docker, see [docker system prune](https://docs.docker.com/engine/reference/commandline/system_prune/) for more information.
-```bash
+
+```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=run-docker-prune
 ```
 
+The shortcut command with `just` program is also available: `just run-tags run-docker-prune`
+
 ## Postgres
 
 See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) documentation page.
-
-## Ma1sd
-
-See the dedicated [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md) documentation page.
diff --git a/docs/maintenance-checking-services.md b/docs/maintenance-checking-services.md
index 151a5778b..b2d90554c 100644
--- a/docs/maintenance-checking-services.md
+++ b/docs/maintenance-checking-services.md
@@ -1,13 +1,15 @@
 # Checking if services work
 
-This playbook can perform a check to ensure that you've configured things correctly and that services are running.
+The playbook can perform a check to ensure that you've configured things correctly and that services are running.
 
 To perform the check, run:
 
-```bash
+```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=self-check
 ```
 
+The shortcut command with `just` program is also available: `just run-tags self-check`
+
 If it's all green, everything is probably running correctly.
 
-Besides this self-check, you can also check your server using the [Federation Tester](https://federationtester.matrix.org/).
+Besides this self-check, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain.
diff --git a/docs/maintenance-migrating.md b/docs/maintenance-migrating.md
index d71a13e3d..e2c0a7efa 100644
--- a/docs/maintenance-migrating.md
+++ b/docs/maintenance-migrating.md
@@ -1,14 +1,71 @@
-> **Note**: This migration guide is applicable if you migrate from one server to another server having the same CPU architecture (e.g. both servers being `amd64`).
->
-> If you're trying to migrate between different architectures (e.g. `amd64` --> `arm64`), simply copying the complete `/matrix` directory is not possible as it would move the raw PostgreSQL data (`/matrix/postgres/data`) between different architectures. In this specific case, you can use the guide below as a reference, but you would also need to avoid syncing `/matrix/postgres/data` to the new host, and also dump the database on your current server and import it properly on the new server. See our [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql) docs for help with PostgreSQL backup/restore.
-
 # Migrating to new server
 
-1. Prepare by lowering DNS TTL for your domains (`matrix.example.com`, etc.), so that DNS record changes (step 4 below) would happen faster, leading to less downtime
-2. Stop all services on the old server and make sure they won't be starting again. Execute this on the old server: `systemctl disable --now matrix*` (you might have to cd to /etc/systemd/system/ first)
-3. Copy directory `/matrix` from the old server to the new server. Make sure to preserve ownership and permissions (use `cp -p` or `rsync -ar`)!
-4. Make sure your DNS records are adjusted to point to the new server's IP address
-5. Remove old server from the `inventory/hosts` file and add new server.
-6. Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-system-user`. This will create the `matrix` user and group on the new server
-7. Because the `matrix` user and group are created dynamically on each server, the user/group ID may differ between the old and new server. We suggest that you adjust ownership of `/matrix` files manually by running this on the new server: `chown -R matrix:matrix /matrix`.
-8. Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start` to finish the installation and start all services
+This documentation explains how to migrate your Matrix services (server, client, bridges, etc.) and data **from an old server to a new server**.
+
+**Notes**:
+- This migration guide is applicable if you migrate from one server to another server having the same CPU architecture (e.g. both servers being `amd64`).
+
+  If you're trying to migrate between different architectures (e.g. `amd64` --> `arm64`), simply copying the complete `/matrix` directory is **not** possible as it would move the raw PostgreSQL data (`/matrix/postgres/data`) between different architectures. In this specific case, you can use the guide below as a reference, but you would also need to avoid syncing `/matrix/postgres/data` to the new host, and also dump the database on your current server and import it properly on the new server. See our [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql) docs for help with PostgreSQL backup/restore.
+- If you have any questions about migration or encountered an issue during migration, do not hesitate to ask for help on [our Matrix room](https://matrix.to/#/%23matrix-docker-ansible-deploy:devture.com). You probably might want to prepare a temporary/sub account on another Matrix server in case it becomes impossible to use your server due to migration failure by any chance.
+
+- You can't change the domain (specified in the `matrix_domain` variable) after the initial deployment.
+
+## Lower DNS TTL
+
+Prepare by lowering DNS TTL for your domains (`matrix.example.com`, etc.), so that DNS record changes would happen faster, leading to less downtime.
+
+## Stop services on the old server completely
+
+Before migrating, you need to stop all services on the old server and make sure they won't be starting again.
+
+To do so, it is recommended to run the `systemctl` command on the server. Running the playbook's `stop` tag also stops the services, but just once; they will start again if you reboot the server.
+
+Log in to the old server and run the command as `root` (or a user that can run it with `sudo`):
+
+```sh
+cd /etc/systemd/system/ && systemctl disable --now matrix*
+```
+
+## Copy data directory to the new server
+
+After you've confirmed that all services were stopped, copy the `/matrix` directory from the old server to the new server. When copying, make sure to preserve ownership and permissions (use `cp -p` or `rsync -ar`)!
+
+## Adjust DNS records
+
+Make sure your DNS records are adjusted to point to the new server's IP address.
+
+## Update `inventory/hosts` file
+
+Having adjusted DNS records, replace the old server's external IP address on the `inventory/hosts` file with that of the new server.
+
+## Create `matrix` user and group on the new server
+
+Then, run the command below on your local computer to create the `matrix` user and group on the new server:
+
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-system-user
+```
+
+The shortcut command with `just` program is also available: `just run-tags setup-system-user`
+
+**Note**: because the `matrix` user and group are created dynamically on each server, the user/group ID may differ between the old and new server. We suggest that you adjust ownership of `/matrix` files. To adjust the ownership, log in to the new server and run the command:
+
+```sh
+chown -R matrix:matrix /matrix
+```
+
+## Install and start all services on the new server
+
+Finally, run the command below on your local computer to finish the installation and start all services:
+
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=install-all,start
+```
+
+The shortcut command with `just` program is also available: `just run-tags install-all,start`
+
+### Check if services work
+
+After starting the services, you probably might want to ensure that you've migrated things correctly and that services are running. For instructions, see: [check if services work](maintenance-checking-services.md)
+
+Having make sure that both services and federation work as expected, you can safely shutdown the old server.
diff --git a/docs/maintenance-postgres.md b/docs/maintenance-postgres.md
index deac1faa7..82c4757c6 100644
--- a/docs/maintenance-postgres.md
+++ b/docs/maintenance-postgres.md
@@ -30,7 +30,6 @@ You can then proceed to write queries. Example: `SELECT COUNT(*) FROM users;`
 
 **Be careful**. Modifying the database directly (especially as services are running) is dangerous and may lead to irreversible database corruption. When in doubt, consider [making a backup](#backing-up-postgresql).
 
-
 ## Vacuuming PostgreSQL
 
 Deleting lots data from Postgres does not make it release disk space, until you perform a [`VACUUM` operation](https://www.postgresql.org/docs/current/sql-vacuum.html).
@@ -50,14 +49,13 @@ Example playbook invocations:
 - `just run-tags run-postgres-vacuum`: runs the default `vacuum-complete` preset and restarts all services
 - `just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze`: runs the `analyze` preset with all services remaining operational at all times
 
-
 ## Backing up PostgreSQL
 
 To automatically make Postgres database backups on a fixed schedule, see [Setting up postgres backup](configuring-playbook-postgres-backup.md).
 
 To make a one off back up of the current PostgreSQL database, make sure it's running and then execute a command like this on the server:
 
-```bash
+```sh
 /usr/bin/docker exec \
 --env-file=/matrix/postgres/env-postgres-psql \
 matrix-postgres \
@@ -70,7 +68,6 @@ If you are using an [external Postgres server](configuring-playbook-external-pos
 
 Restoring a backup made this way can be done by [importing it](importing-postgres.md).
 
-
 ## Upgrading PostgreSQL
 
 Unless you are using an [external Postgres server](configuring-playbook-external-postgres.md), this playbook initially installs Postgres for you.
@@ -79,7 +76,7 @@ Once installed, the playbook attempts to preserve the Postgres version it starts
 
 Upgrades must be performed manually.
 
-This playbook can upgrade your existing Postgres setup with the following command:
+The playbook can upgrade your existing Postgres setup with the following command:
 
 ```sh
 just run-tags upgrade-postgres
@@ -91,12 +88,10 @@ The auto-upgrade-backup directory stays around forever, until you **manually dec
 
 As part of the upgrade, the database is dumped to `/tmp`, an upgraded and empty Postgres server is started, and then the dump is restored into the new server. To use a different directory for the dump, pass some extra flags to the command above, like this: `--extra-vars="postgres_dump_dir=/directory/to/dump/here"`
 
-To save disk space in `/tmp`, the dump file is gzipped on the fly at the expense of CPU usage.
-If you have plenty of space in `/tmp` and would rather avoid gzipping, you can explicitly pass a dump filename which doesn't end in `.gz`. Example: `--extra-vars="postgres_dump_name=matrix-postgres-dump.sql"`
+To save disk space in `/tmp`, the dump file is gzipped on the fly at the expense of CPU usage. If you have plenty of space in `/tmp` and would rather avoid gzipping, you can explicitly pass a dump filename which doesn't end in `.gz`. Example: `--extra-vars="postgres_dump_name=matrix-postgres-dump.sql"`
 
 **All databases, roles, etc. on the Postgres server are migrated**.
 
-
 ## Tuning PostgreSQL
 
 PostgreSQL can be [tuned](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) to make it run faster. This is done by passing extra arguments to the Postgres process.
diff --git a/docs/maintenance-synapse.md b/docs/maintenance-synapse.md
index eca39f886..0c2eded9b 100644
--- a/docs/maintenance-synapse.md
+++ b/docs/maintenance-synapse.md
@@ -18,13 +18,14 @@ You can use the **[Purge History API](https://github.com/element-hq/synapse/blob
 
 To make use of this Synapse Admin API, **you'll need an admin access token** first. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md).
 
+⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.
+
 Synapse's Admin API is not exposed to the internet by default, following [official Synapse reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints). To expose it you will need to add `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` to your `vars.yml` file.
 
 Follow the [Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md) documentation page for the actual purging instructions.
 
 After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql).
 
-
 ## Compressing state with rust-synapse-compress-state
 
 [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) can be used to optimize some `_state` tables used by Synapse. If your server participates in large rooms this is the most effective way to reduce the size of your database.
@@ -35,15 +36,16 @@ After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintena
 
 To ask the playbook to run rust-synapse-compress-state, execute:
 
-```
+```sh
 ansible-playbook -i inventory/hosts setup.yml --tags=rust-synapse-compress-state
 ```
 
+The shortcut command with `just` program is also available: `just run-tags rust-synapse-compress-state`
+
 By default, all rooms with more than `100000` state group rows will be compressed. If you need to adjust this, pass: `--extra-vars='matrix_synapse_rust_synapse_compress_state_min_state_groups_required=SOME_NUMBER_HERE'` to the command above.
 
 After state compression, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql).
 
-
 ## Browse and manipulate the database
 
 When the [Synapse Admin API](https://github.com/element-hq/synapse/tree/master/docs/admin_api) and the other tools do not provide a more convenient way, having a look at synapse's postgresql database can satisfy a lot of admins' needs.
@@ -52,20 +54,20 @@ Editing the database manually is not recommended or supported by the Synapse dev
 
 First, set up an SSH tunnel to your Matrix server (skip if it is your local machine):
 
-```
+```sh
 # you may replace 1799 with an arbitrary port unbound on both machines
 ssh -L 1799:localhost:1799 matrix.example.com
 ```
 
 Then start up an ephemeral [adminer](https://www.adminer.org/) container on the Matrix server, connecting it to the `matrix` network and linking the postgresql container:
 
-```
+```sh
 docker run --rm --publish 1799:8080 --link matrix-postgres --net matrix adminer
 ```
 
 You should then be able to browse the adminer database administration GUI at http://localhost:1799/ after entering your DB credentials (found in the `host_vars` or on the server in `{{matrix_synapse_config_dir_path}}/homeserver.yaml` under `database.args`)
 
-⚠️ Be **very careful** with this, there is **no undo** for impromptu DB operations.
+⚠️️ Be **very careful** with this, there is **no undo** for impromptu DB operations.
 
 ## Make Synapse faster
 
@@ -93,7 +95,7 @@ You can **learn more about cache-autotuning and the global cache factor settings
 
 To **disable cache auto-tuning**, unset all values:
 
-```yml
+```yaml
 matrix_synapse_cache_autotuning_max_cache_memory_usage: ''
 matrix_synapse_cache_autotuning_target_cache_memory_usage: ''
 matrix_synapse_cache_autotuning_min_cache_ttl: ''
diff --git a/docs/maintenance-upgrading-services.md b/docs/maintenance-upgrading-services.md
index ea7ffb4d7..ca1ea78f1 100644
--- a/docs/maintenance-upgrading-services.md
+++ b/docs/maintenance-upgrading-services.md
@@ -2,17 +2,59 @@
 
 This playbook not only installs the various Matrix services for you, but can also upgrade them as new versions are made available.
 
+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**.
+
+The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities (for example, see [here](https://github.com/element-hq/element-web/security) for known ones on Element Web).
+
+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.
+
+The developers of this playbook strive to maintain the playbook updated, so that you can re-run the playbook to address such vulnerabilities. It is **your responsibility** to keep your server and the services on it up-to-date.
+
 If you want to be notified when new versions of Synapse are released, you should join the Synapse Homeowners room: [#homeowners:matrix.org](https://matrix.to/#/#homeowners:matrix.org).
 
-To upgrade services:
+## Steps to upgrade the Matrix services
 
-- update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file) using:
+### Check the changelog
 
-  - either: `just update`
-  - or: a combination of `git pull` and `just roles` (or `make roles`)
+Before updating the playbook and the Ansible roles in the playbook, take a look at [the changelog](../CHANGELOG.md) to see if there have been any backward-incompatible changes that you need to take care of.
 
-- take a look at [the changelog](../CHANGELOG.md) to see if there have been any backward-incompatible changes that you need to take care of
+### Update the playbook and the Ansible roles
 
-- re-run the [playbook setup](installing.md) and restart all services: `just install-all` or `just setup-all`
+If it looks good to you, go to the `matrix-docker-ansible-deploy` directory, update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file) by running:
 
-**Note**: major version upgrades to the internal PostgreSQL database are not done automatically. To upgrade it, refer to the [upgrading PostgreSQL guide](maintenance-postgres.md#upgrading-postgresql).
+- either: `just update`
+- or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)
+
+If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`
+
+**Note**: for details about `just` commands, take a look at: [Running `just` commands](just.md).
+
+### Re-run the playbook setup
+
+After updating the Ansible roles, then re-run the [playbook setup](installing.md#maintaining-your-setup-in-the-future) and restart all services:
+
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=install-all,start
+```
+
+If you remove components from `vars.yml`, or if we switch some component from being installed by default to not being installed by default anymore, you'd need to run the setup command with the `setup-all` tag as below:
+
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+**Notes**:
+
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account, if any.
+
+- Our estimation is that running `--tags=install-all,start` is approximately from **2 to 5 times faster** than running `setup-all,ensure-matrix-users-created,start`. See [this entry](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) on `CHANGELOG.md` for more information.
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`. Note these shortcuts run the `ensure-matrix-users-created` tag too.
+
+- See [this page on the playbook tags](playbook-tags.md) for more information about those tags.
+
+## PostgreSQL major version upgrade
+
+Major version upgrades to the internal PostgreSQL database are not done automatically. Upgrades must be performed manually.
+
+For details about upgrading it, refer to the [upgrading PostgreSQL guide](maintenance-postgres.md#upgrading-postgresql).
diff --git a/docs/obtaining-access-tokens.md b/docs/obtaining-access-tokens.md
index 301ea8db2..e1f69b226 100644
--- a/docs/obtaining-access-tokens.md
+++ b/docs/obtaining-access-tokens.md
@@ -2,32 +2,31 @@
 
 When setting up some optional features like bots and bridges you will need to provide an access token for some user. This document provides documentation on how to obtain such an access token.
 
-**Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.**
+⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone.
 
 ## Prerequisites
 
 The user for whom you want to obtain an access token needs to already exist. You can use this playbook to [register a new user](registering-users.md), if you have not already.
 
-Below, we describe 2 ways to generate an access token for a user - using [Element](#obtain-an-access-token-via-element) or [curl](#obtain-an-access-token-via-curl). For both ways you need the user's password.
+Below, we describe 2 ways to generate an access token for a user - using [Element Web](#obtain-an-access-token-via-element-web) or [curl](#obtain-an-access-token-via-curl). For both ways you need the user's password.
 
-## Obtain an access token via Element
+## Obtain an access token via Element Web
 
-1. In a private browsing session (incognito window), open Element.
+1. In a private browsing session (incognito window), open Element Web.
 2. Log in with the user's credentials.
 3. In the settings page, choose "Help & About", scroll down to the bottom and expand the `Access Token` section (see screenshot below).
 4. Copy the access token to your configuration.
 5. Close the private browsing session. **Do not log out**. Logging out will invalidate the token, making it not work.
 
-![Obtaining an access token with Element](assets/obtain_admin_access_token_element.png)
-
+![Obtaining an access token with Element Web](assets/obtain_admin_access_token_element_web.png)
 
 ## Obtain an access token via curl
 
 You can use the following command to get an access token for your user directly from the [Matrix Client-Server API](https://www.matrix.org/docs/guides/client-server-api#login):
 
-```
+```sh
 curl -XPOST -d '{
-    "identifier": { "type": "m.id.user", "user": "USERNAME" },
+    "identifier": { "type": "m.id.user", "user": "alice" },
     "password": "PASSWORD",
     "type": "m.login.password",
     "device_id": "YOURDEVICEID"
@@ -41,7 +40,7 @@ Your response will look like this (prettified):
 
 ```
 {
-    "user_id":"@USERNAME:example.com",
+    "user_id":"@alice:example.com",
     "access_token":">>>YOUR_ACCESS_TOKEN_IS_HERE<<<",
     "home_server":"example.com",
     "device_id":"YOURDEVICEID"
diff --git a/docs/playbook-tags.md b/docs/playbook-tags.md
new file mode 100644
index 000000000..8e2a064ce
--- /dev/null
+++ b/docs/playbook-tags.md
@@ -0,0 +1,25 @@
+# Playbook tags
+
+The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks.
+
+The general command syntax is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`
+
+Here are some playbook tags that you should be familiar with:
+
+- `setup-all` - runs all setup tasks (installation and uninstallation) for all components, but does not start/restart services
+
+- `install-all` - like `setup-all`, but skips uninstallation tasks. Useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove components, you'd need to run `setup-all` though, or these components will still remain installed
+
+- `setup-SERVICE` (e.g. `setup-postmoogle`) - runs the setup tasks only for a given role, but does not start/restart services. You can discover these additional tags in each role (`roles/**/tasks/main.yml`). Running per-component setup tasks is **not recommended**, as components sometimes depend on each other and running just the setup tasks for a given component may not be enough. For example, setting up the [mautrix-telegram bridge](configuring-playbook-bridge-mautrix-telegram.md), in addition to the `setup-mautrix-telegram` tag, requires database changes (the `setup-postgres` tag) as well as reverse-proxy changes (the `setup-nginx-proxy` tag).
+
+- `install-SERVICE` (e.g. `install-postmoogle`) - like `setup-SERVICE`, but skips uninstallation tasks. See `install-all` above for additional information.
+
+- `start` - starts all systemd services and makes them start automatically in the future
+
+- `stop` - stops all systemd services
+
+- `ensure-matrix-users-created` - a special tag which ensures that all special users needed by the playbook (for bots, etc.) are created
+
+**Notes**:
+- `setup-*` tags and `install-*` tags **do not start services** automatically, because you may wish to do things before starting services, such as importing a database dump, restoring data from another server, etc.
+- Please be careful not to confuse the playbook tags with the `just` shortcut commands ("recipes"). For details about `just` commands, see: [Running `just` commands](just.md)
diff --git a/docs/prerequisites.md b/docs/prerequisites.md
index 24baabedb..3bd3da975 100644
--- a/docs/prerequisites.md
+++ b/docs/prerequisites.md
@@ -1,6 +1,26 @@
 # Prerequisites
 
-To install Matrix services using this Ansible playbook, you need:
+<sup>Prerequisites > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)</sup>
+
+To install Matrix services using this Ansible playbook, you need to prepare several requirements both on your local computer (where you will run the playbook to configure the server) and the server (where the playbook will install the Matrix services for you). **These requirements need to be set up manually** before proceeding to the next step.
+
+We will be using `example.com` as the domain in the following instruction. Please remember to replace it with your own domain before running any commands.
+
+**Note**: if you do not have an existing Matrix server and want to start quickly with "opinionated defaults", we suggest you to follow ⚡ **[Quick start](quick-start.md)** installation guide.
+
+## Your local computer
+
+- [Ansible](http://ansible.com/) program. It's used to run this playbook and configures your server for you. Take a look at [our guide about Ansible](ansible.md) for more information, as well as [version requirements](ansible.md#supported-ansible-versions) and alternative ways to run Ansible.
+
+- [passlib](https://passlib.readthedocs.io/en/stable/index.html) Python library. See [this official documentation](https://passlib.readthedocs.io/en/stable/install.html#installation-instructions) for an instruction to install it. On most distros, you need to install some `python-passlib` or `py3-passlib` package, etc.
+
+- [`git`](https://git-scm.com/) as the recommended way to download the playbook. `git` may also be required on the server if you will be [self-building](self-building.md) components.
+
+- [`just`](https://github.com/casey/just) for running `just roles`, `just update`, etc. (see [`justfile`](../justfile)), although you can also run these commands manually. Take at look at this documentation for more information: [Running `just` commands](just.md).
+
+- Strong password (random strings) generator. The playbook often requires you to create a strong password and use it for settings on `vars.yml`, components, etc. As any tools should be fine, this playbook has adopted [`pwgen`](https://linux.die.net/man/1/pwgen) (running `pwgen -s 64 1`). [Password Tech](https://pwgen-win.sourceforge.io/), formerly known as "PWGen for Windows", is available as free and open source password generator for Windows. Generally, using a random generator available on the internet is not recommended.
+
+## Server
 
 - (Recommended) An **x86** server ([What kind of server specs do I need?](faq.md#what-kind-of-server-specs-do-i-need)) running one of these operating systems that make use of [systemd](https://systemd.io/):
   - **Archlinux**
@@ -8,7 +28,7 @@ To install Matrix services using this Ansible playbook, you need:
   - **Debian** (10/Buster or newer)
   - **Ubuntu** (18.04 or newer, although [20.04 may be problematic](ansible.md#supported-ansible-versions) if you run the Ansible playbook on it)
 
-  Generally, newer is better. We only strive to support released stable versions of distributions, not betas or pre-releases. This playbook can take over your whole server or co-exist with other services that you have there.
+  Generally, newer is better. We only strive to support released stable versions of distributions, not betas or pre-releases. The playbook can take over your whole server or co-exist with other services that you have there.
 
   This playbook somewhat supports running on non-`amd64` architectures like ARM. See [Alternative Architectures](alternative-architectures.md).
 
@@ -16,17 +36,9 @@ To install Matrix services using this Ansible playbook, you need:
 
 - `root` access to your server (or a user capable of elevating to `root` via `sudo`).
 
-- [Python](https://www.python.org/) being installed on the server. Most distributions install Python by default, but some don't (e.g. Ubuntu 18.04) and require manual installation (something like `apt-get install python3`). On some distros, Ansible may incorrectly [detect the Python version](https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html) (2 vs 3) and you may need to explicitly specify the interpreter path in `inventory/hosts` during installation (e.g. `ansible_python_interpreter=/usr/bin/python3`)
+- [Python](https://www.python.org/). Most distributions install Python by default, but some don't (e.g. Ubuntu 18.04) and require manual installation (something like `apt-get install python3`). On some distros, Ansible may incorrectly [detect the Python version](https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html) (2 vs 3) and you may need to explicitly specify the interpreter path in `inventory/hosts` during installation (e.g. `ansible_python_interpreter=/usr/bin/python3`)
 
-- [sudo](https://www.sudo.ws/) being installed on the server, even when you've configured Ansible to log in as `root`. Some distributions, like a minimal Debian net install, do not include the `sudo` package by default.
-
-- The [Ansible](http://ansible.com/) program being installed on your own computer. It's used to run this playbook and configures your server for you. Take a look at [our guide about Ansible](ansible.md) for more information, as well as [version requirements](ansible.md#supported-ansible-versions) and alternative ways to run Ansible.
-
-- the [passlib](https://passlib.readthedocs.io/en/stable/index.html) Python library installed on the computer you run Ansible. On most distros, you need to install some `python-passlib` or `py3-passlib` package, etc.
-
-- [`git`](https://git-scm.com/) is the recommended way to download the playbook to your computer. `git` may also be required on the server if you will be [self-building](self-building.md) components.
-
-- [`just`](https://github.com/casey/just) for running `just roles`, `just update`, etc. (see [`justfile`](../justfile)), although you can also run these commands manually
+- [sudo](https://www.sudo.ws/), even when you've configured Ansible to log in as `root`. Some distributions, like a minimal Debian net install, do not include the `sudo` package by default.
 
 - An HTTPS-capable web server at the base domain name (`example.com`) which is capable of serving static files. Unless you decide to [Serve the base domain from the Matrix server](configuring-playbook-base-domain-serving.md) or alternatively, to use DNS SRV records for [Server Delegation](howto-server-delegation.md).
 
@@ -36,12 +48,14 @@ To install Matrix services using this Ansible playbook, you need:
 
   - `80/tcp`: HTTP webserver
   - `443/tcp` and `443/udp`: HTTPS webserver
-  - `3478/tcp`: TURN over TCP (used by Coturn)
-  - `3478/udp`: TURN over UDP (used by Coturn)
-  - `5349/tcp`: TURN over TCP (used by Coturn)
-  - `5349/udp`: TURN over UDP (used by Coturn)
-  - `8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. In some cases, this **may necessary even with federation disabled**. Integration Servers (like Dimension) and Identity Servers (like ma1sd) may need to access `openid` APIs on the federation port.
+  - `3478/tcp`: TURN over TCP (used by coturn)
+  - `3478/udp`: TURN over UDP (used by coturn)
+  - `5349/tcp`: TURN over TCP (used by coturn)
+  - `5349/udp`: TURN over UDP (used by coturn)
+  - `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**.
   - the range `49152-49172/udp`: TURN over UDP
   - 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.
 
-When ready to proceed, continue with [Configuring DNS](configuring-dns.md).
+---------------------------------------------
+
+[▶️](configuring-dns.md) When ready to proceed, continue with [Configuring DNS](configuring-dns.md).
diff --git a/docs/quick-start.md b/docs/quick-start.md
new file mode 100644
index 000000000..9f75b61f7
--- /dev/null
+++ b/docs/quick-start.md
@@ -0,0 +1,210 @@
+# Quick start
+
+<!--
+NOTE:
+- Let's keep it as tidy and simple as possible.
+- Because this documentation is intended to be referred by those who have not configured a Matrix server and services by using the playbook, from the educational point of view it intentionally avoids instructions based on just program's "recipes" in favor of ansible-playbook commands in most cases.
+-->
+
+This page explains how to use this Ansible playbook to install Matrix services on your server with a minimal set of core services.
+
+We will be using `example.com` as the "base domain" in the following instruction.
+
+By following the instruction on this page, you will set up:
+
+- **your own Matrix server** on a `matrix.example.com` server, which is configured to present itself as `example.com`
+- **your user account** like `@alice:example.com` on the server
+- a **self-hosted Matrix client**, [Element Web](configuring-playbook-client-element-web.md) with the default subdomain at `element.example.com`
+- Matrix delegation, so that your `matrix.example.com` server (presenting itself as `example.com`) can join the Matrix Federation and communicate with any other server in the Matrix network
+
+Please remember to replace `example.com` with your own domain before running any commands.
+
+## Prerequisites
+
+<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Prerequisites](prerequisites.md)</sup>
+
+At first, **check prerequisites** and prepare for installation by setting up programs [on your own computer](prerequisites.md#your-local-computer) and [your server](prerequisites.md#server). You also need `root` access on your server (a user that could elevate to `root` via `sudo` also works).
+
+When preparing your server, make sure to check [the server specs you need](faq.md#what-kind-of-server-specs-do-i-need). We recommend starting with a server having at least 2GB of memory.
+
+<!--
+TODO: Add one liners (or instructions, a script, etc.) for easy and consistent installation of required software. See: https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3757
+-->
+
+If you encounter an error during installation, please make sure that you have installed and configured programs correctly.
+
+One of the main reasons of basic errors is using an incompatible version of required software such as Ansible. Take a look at [our guide about Ansible](ansible.md) for more information. In short: installing the latest available version is recommended.
+
+## Configure your DNS settings
+
+<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Configuring your DNS settings](configuring-dns.md)</sup>
+
+After installing and configuring prerequisites, you will need to **configure DNS records**.
+
+To configure Matrix services in the default settings, go to your DNS service provider, and adjust DNS records as below.
+
+| Type  | Host                         | Priority | Weight | Port | Target               |
+| ----- | ---------------------------- | -------- | ------ | ---- | ---------------------|
+| A     | `matrix`                     | -        | -      | -    | `matrix-server-IP`   |
+| CNAME | `element`                    | -        | -      | -    | `matrix.example.com` |
+
+As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine).
+
+It might take some time for the DNS records to propagate after creation.
+
+**💡 Note**: if you are using Cloudflare DNS, make sure to disable the proxy and set all records to "DNS only"
+
+## Get the playbook
+
+<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Getting the playbook](getting-the-playbook.md)</sup>
+
+Next, let's **get the playbook's source code**.
+
+We recommend to do so with [git](https://git-scm.com/) as it enables you to keep it up to date with the latest source code. While it is possible to download the playbook as a ZIP archive, it is not recommended.
+
+To get the playbook with git, install git on your computer, go to a directory, and run the command:
+
+```sh
+git clone https://github.com/spantaleev/matrix-docker-ansible-deploy.git
+```
+
+It will fetch the playbook to a new `matrix-docker-ansible-deploy` directory underneath the directory you are currently in.
+
+## Configure the playbook
+
+<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Configuring the playbook](configuring-playbook.md)</sup>
+
+Now that the playbook was fetched, it is time to **configure** it per your needs.
+
+To install Matrix services with this playbook, you would at least need 2 configuration files.
+
+For your convenience, we have prepared example files of them ([`vars.yml`](../examples/vars.yml) and [`hosts`](../examples/hosts)).
+
+To start quickly based on these example files, go into the `matrix-docker-ansible-deploy` directory and follow the instructions below:
+
+1. Create a directory to hold your configuration: `mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your "base domain"
+2. Copy the sample configuration file: `cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`
+3. Copy the sample inventory hosts file: `cp examples/hosts inventory/hosts`
+4. Edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`)
+5. Edit the inventory hosts file (`inventory/hosts`)
+
+Before editing these 2 files, make sure to read explanations on them to understand what needs to be configured.
+
+**💡 Notes:**
+- If you are not in control of anything on the base domain, you would need to set additional configuration on `vars.yml`. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ.
+- Certain configuration decisions (like the base domain configured in `matrix_domain` and homeserver implementation configured in `matrix_homeserver_implementation`) are final. If you make the wrong choice and wish to change it, you'll have to run the Uninstalling step and start over.
+- Instead of configuring a lot of things all at once, we recommend starting with the basic (default) settings in order to get yourself familiar with how the playbook works. After making sure that everything works as expected, you can add (and remove) advanced settings / features and run the playbook as many times as you wish.
+
+## Install
+
+<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Installing](installing.md)</sup>
+
+After editing `vars.yml` and `hosts` files, let's start the **installation** procedure.
+
+### Update Ansible roles
+
+Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside.
+
+To update your playbook directory and all upstream Ansible roles, run:
+
+- either: `just update`
+- or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)
+
+If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`
+
+### Run installation command
+
+Then, run the command below to start installation:
+
+````sh
+ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start
+````
+
+If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the command.
+
+If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to the command.
+
+Wait until the command completes. If it's all green, everything should be running properly.
+
+## Create your user account
+
+<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Registering users](registering-users.md)</sup>
+
+As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server.
+
+To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer.
+
+**💡 Notes**:
+- Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`
+- For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)
+
+```sh
+ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=YOUR_USERNAME_HERE password=YOUR_PASSWORD_HERE admin=yes' --tags=register-user
+
+# Example: ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=alice password=secret-password admin=yes' --tags=register-user
+```
+
+<!--
+NOTE: detailed instruction to add users can be found on docs/registering-users.md and installing.md, which include a note about usage of admin=yes and admin=no variables. In order to keep this guide as reasonably short as possible, let's not repeat the same instruction here.
+-->
+
+## Finalize server installation
+
+<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Server Delegation](howto-server-delegation.md)</sup>
+
+Now that you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network.
+
+**This is required for federation to work!** Without a proper configuration, your server will effectively not be part of the Matrix network.
+
+To configure the delegation, you have these two options. Choose one of them according to your situation.
+
+- If you can afford to point the base domain at the Matrix server, follow the instruction below which guides you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server.
+- Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot "serve the base domain" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server).
+
+To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+
+```yaml
+matrix_static_files_container_labels_base_domain_enabled: true
+```
+
+After configuring the playbook, run the command below and wait until it finishes:
+
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=install-matrix-static-files,start
+```
+
+💡 Running the `install-matrix-static-files` playbook tag (as done here) is an optimized version of running [the full setup command](#run-installation-command).
+
+After the command finishes, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain.
+
+### Re-run the full setup command any time
+
+If you think something is wrong with the server configuration, feel free to re-run the setup command any time:
+
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
+```
+
+## Log in to your user account
+
+Finally, let's make sure that you can log in to the created account with the specified password.
+
+You should be able to log in to it with your own [Element Web](configuring-playbook-client-element-web.md) client which you have set up at `element.example.com` by running the playbook. Open the URL (`https://element.example.com`) in a web browser and enter your credentials to log in.
+
+**If you successfully logged in to your account, installing and configuring is complete**🎉
+
+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.
+
+## Things to do next
+
+Once you get familiar with the playbook, you might probably want to set up additional services such as a bridge on your server.
+
+As this page intends to be a quick start guide which explains how to start the core Matrix services, it does not cover a topic like how to set them up. Take a look at the list of [things to do next](installing.md#things-to-do-next) to learn more.
+
+### ⚠️Keep the playbook and services up-to-date
+
+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**.
+
+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.
+
+For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)
diff --git a/docs/registering-users.md b/docs/registering-users.md
index acb86a908..ca62398da 100644
--- a/docs/registering-users.md
+++ b/docs/registering-users.md
@@ -1,6 +1,6 @@
 # Registering users
 
-This documentation page tells you how to create user account on your Matrix server.
+This documentation page tells you how to create user accounts on your Matrix server.
 
 Table of contents:
 
@@ -9,65 +9,69 @@ Table of contents:
 	- [Managing users via a Web UI](#managing-users-via-a-web-ui)
 	- [Letting certain users register on your private server](#letting-certain-users-register-on-your-private-server)
 	- [Enabling public user registration](#enabling-public-user-registration)
-	- [Adding/Removing Administrator privileges to an existing Synapse user](#addingremoving-administrator-privileges-to-an-existing-synapse-user)
-
+	- [Adding/Removing Administrator privileges to an existing user](#addingremoving-administrator-privileges-to-an-existing-user)
 
 ## Registering users manually
 
-**Note**: in the commands below, `<your-username>` is just a plain username (like `john`), not your full `@<username>:example.com` identifier.
+**Notes**:
+- Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`
+- For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)
+- Use `admin=yes` or `admin=no` depending on whether you wish to make the user an administrator of the Matrix server
 
-After registering a user (using one of the methods below), **you can log in with that user** via the [Element](configuring-playbook-client-element.md) service that this playbook has installed for you at a URL like this: `https://element.example.com/`.
+After registering a user (using one of the methods below), **you can log in with that user** via the [Element Web](configuring-playbook-client-element-web.md) service that this playbook has installed for you at a URL like this: `https://element.example.com/`.
 
 ### Registering users via the Ansible playbook
 
 It's best to register users via the Ansible playbook, because it works regardless of homeserver implementation (Synapse, Dendrite, etc) or usage of [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (MAS).
 
-To register a user via this Ansible playbook (make sure to edit the `<your-username>` and `<your-password>` part below):
+To register a user via this Ansible playbook:
 
 ```sh
-just register-user <your-username> <your-password> <admin access: yes or no>
+just register-user USERNAME_HERE PASSWORD_HERE <admin access: yes or no>
 
-# Example: `just register-user john secret-password yes`
+# Example: `just register-user alice secret-password yes`
 ```
 
 **or** by invoking `ansible-playbook` manually:
 
 ```sh
-ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=<your-username> password=<your-password> admin=<yes|no>' --tags=register-user
+ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=USERNAME_HERE password=PASSWORD_HERE admin=<yes|no>' --tags=register-user
 
-# Example: `ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=john password=secret-password admin=yes' --tags=register-user`
+# Example: ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=alice password=secret-password admin=yes' --tags=register-user
 ```
 
-⚠ **Warning**: If you're registering users against Matrix Authentication Service, do note that it [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information.
+Feel free to register as many users (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your user account only (with `admin=yes`), and others should be created with `admin=no`.
+
+⚠️ **Warning**: If you're registering users against Matrix Authentication Service, do note that it [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information.
 
 ### Registering users manually for Synapse
 
-If you're using the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default), you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](#starting-the-services)):
+If you're using the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default), you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):
 
 ```sh
-/matrix/synapse/bin/register-user <your-username> <your-password> <admin access: 0 or 1>
+/matrix/synapse/bin/register-user USERNAME_HERE PASSWORD_HERE <admin access: 0 or 1>
 
-# Example: `/matrix/synapse/bin/register-user john secret-password 1`
+# Example: `/matrix/synapse/bin/register-user alice secret-password 1`
 ```
 
 ### Registering users manually for Dendrite
 
-If you're using the [Dendrite](./configuring-playbook-dendrite.md) homeserver implementation, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](#starting-the-services)):
+If you're using the [Dendrite](./configuring-playbook-dendrite.md) homeserver implementation, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):
 
 ```sh
-/matrix/dendrite/bin/create-account <your-username> <your-password> <admin access: 0 or 1>
+/matrix/dendrite/bin/create-account USERNAME_HERE PASSWORD_HERE <admin access: 0 or 1>
 
-# Example: `/matrix/dendrite/bin/create-account john secret-password 1`
+# Example: `/matrix/dendrite/bin/create-account alice secret-password 1`
 ```
 
 ### Registering users manually for Matrix Authentication Service
 
-If you're using the [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) and your existing homeserver (most likely [Synapse](./configuring-playbook-synapse.md)) is delegating authentication to it, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](#starting-the-services)):
+If you're using the [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) and your existing homeserver (most likely [Synapse](./configuring-playbook-synapse.md)) is delegating authentication to it, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):
 
 ```sh
-/matrix/matrix-authentication-service/bin/register-user <your-username> <your-password> <admin access: 0 or 1>
+/matrix/matrix-authentication-service/bin/register-user USERNAME_HERE PASSWORD_HERE <admin access: 0 or 1>
 
-# Example: `/matrix/matrix-authentication-service/bin/register-user john secret-password 1`
+# Example: `/matrix/matrix-authentication-service/bin/register-user alice secret-password 1`
 ```
 
 This `register-user` script actually invokes the `mas-cli manage register-user` command under the hood. If you'd like more control over the registration process, consider invoking the `mas-cli` command directly:
@@ -76,38 +80,48 @@ This `register-user` script actually invokes the `mas-cli manage register-user`
 /matrix/matrix-authentication-service/bin/mas-cli manage register-user --help
 ```
 
-⚠ **Warning**: Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information.
-
-
-## Things to do after registering users
-
-If you've just installed Matrix and created some users, **to finalize the installation process** it's best if you proceed with [Configuring service discovery via .well-known](configuring-well-known.md)
-
+⚠️ **Warning**: Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information.
 
 ## Managing users via a Web UI
 
 To manage users more easily (via a web user-interace), you can install [Synapse Admin](configuring-playbook-synapse-admin.md).
 
-⚠ **Warning**: If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information.
-
+⚠️ **Warning**: If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information.
 
 ## Letting certain users register on your private server
 
 If you'd rather **keep your server private** (public registration closed, as is the default), and **let certain people create accounts by themselves** (instead of creating user accounts manually like this), consider installing and making use of [matrix-registration](configuring-playbook-matrix-registration.md).
 
-
 ## Enabling public user registration
 
 To **open up user registration publicly** (usually **not recommended**), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
+For Synapse:
+
 ```yaml
 matrix_synapse_enable_registration: true
 ```
 
-After configuring the playbook, run the [installation](installing.md) command: `just install-all` or `just setup-all`
+For Dendrite:
 
-If you're opening up registrations publicly like this, you might also wish to [configure CAPTCHA protection](configuring-captcha.md).
+```yaml
+matrix_dendrite_client_api_registration_disabled: false
+```
 
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+**Notes**:
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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.
+
+- If you're opening up registrations publicly like this, you might also wish to [configure CAPTCHA protection](configuring-captcha.md).
 
 ## Adding/Removing Administrator privileges to an existing user
 
@@ -116,7 +130,7 @@ If you're opening up registrations publicly like this, you might also wish to [c
 To change the admin privileges for a user in Synapse's local database, you need to run an SQL query like this against the `synapse` database:
 
 ```sql
-UPDATE users SET admin=ADMIN_VALUE WHERE name = '@USER:example.com';
+UPDATE users SET admin=ADMIN_VALUE WHERE name = '@alice:example.com';
 ```
 
 where:
diff --git a/docs/uninstalling.md b/docs/uninstalling.md
index 73a414ede..14c8c211f 100644
--- a/docs/uninstalling.md
+++ b/docs/uninstalling.md
@@ -1,22 +1,17 @@
 # Uninstalling
 
-**Warnings**:
-
+⚠️ **Warnings**:
 - If your server federates with others, make sure to **leave any federated rooms before nuking your Matrix server's data**. Otherwise, the next time you set up a Matrix server for this domain (regardless of the installation method you use), you'll encounter trouble federating.
-
 - If you have some trouble with your installation, you can just [re-run the playbook](installing.md) and it will try to set things up again. **Uninstalling and then installing anew rarely solves anything**.
 
-
 -----------------
 
-
 ## Uninstalling using a script
 
 Installing places a `/matrix/bin/remove-all` script on the server.
 
 You can run it to to have it uninstall things for you automatically (see below). **Use with caution!**
 
-
 ## Uninstalling manually
 
 If you prefer to uninstall manually, run these commands (most are meant to be executed on the Matrix server itself):
@@ -32,5 +27,3 @@ If you prefer to uninstall manually, run these commands (most are meant to be ex
 - uninstall Docker itself, if necessary
 
 - delete the `/matrix` directory (`rm -rf /matrix`)
-
-
diff --git a/docs/updating-users-passwords.md b/docs/updating-users-passwords.md
index 1785a67ca..aecd038ef 100644
--- a/docs/updating-users-passwords.md
+++ b/docs/updating-users-passwords.md
@@ -2,44 +2,48 @@
 
 ## Option 1 (if you are using the integrated Postgres database):
 
-You can reset a user's password via the Ansible playbook (make sure to edit the `<your-username>` and `<your-password>` part below):
+**Notes**:
+- Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`
+- For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)
 
-```
-ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=<your-username> password=<your-password>' --tags=update-user-password
+You can reset a user's password via the Ansible playbook:
+
+```sh
+ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=USERNAME_HERE password=PASSWORD_HERE' --tags=update-user-password
 ```
 
-**Note**: `<your-username>` is just a plain username (like `john`), not your full `@<username>:example.com` identifier.
-
-**You can then log in with that user** via the Element service that this playbook has created for you at a URL like this: `https://element.example.com/`.
-
+**You can then log in with that user** via Element Web that this playbook has created for you at a URL like this: `https://element.example.com/`.
 
 ## Option 2 (if you are using an external Postgres server):
 
-You can manually generate the password hash by using the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#starting-the-services)):
+You can manually generate the password hash by using the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#finalize-the-installation):
 
-```
+```sh
 docker exec -it matrix-synapse /usr/local/bin/hash_password -c /data/homeserver.yaml
 ```
 
 and then connecting to the postgres server and executing:
 
-```
-UPDATE users SET password_hash = '<password-hash>' WHERE name = '@someone:example.com'
+```sql
+UPDATE users SET password_hash = '<password-hash>' WHERE name = '@alice:example.com';
 ```
 
 where `<password-hash>` is the hash returned by the docker command above.
 
-
 ## Option 3:
 
 Use the Synapse User Admin API as described here: https://github.com/element-hq/synapse/blob/master/docs/admin_api/user_admin_api.rst#reset-password
 
 This requires an [access token](obtaining-access-tokens.md) from a server admin account. *This method will also log the user out of all of their clients while the other options do not.*
 
-If you didn't make your account a server admin when you created it, you can learn how to switch it now by reading about it in [Adding/Removing Administrator privileges to an existing Synapse user](registering-users.md#addingremoving-administrator-privileges-to-an-existing-synapse-user).
+If you didn't make your account a server admin when you created it, you can learn how to switch it now by reading about it in [Adding/Removing Administrator privileges to an existing user in Synapse](registering-users.md#addingremoving-administrator-privileges-to-an-existing-user-in-synapse).
 
 ### Example:
-To set @user:example.com's password to `correct_horse_battery_staple` you could use this curl command:
-```
-curl -XPOST -d '{ "new_password": "correct_horse_battery_staple" }' "https://matrix.example.com/_matrix/client/r0/admin/reset_password/@user:example.com?access_token=MDA...this_is_my_access_token
+
+To set @alice:example.com's password to `correct_horse_battery_staple` you could use this curl command:
+
+```sh
+curl -XPOST -d '{ "new_password": "correct_horse_battery_staple" }' "https://matrix.example.com/_matrix/client/r0/admin/reset_password/@alice:example.com?access_token=ACCESS_TOKEN_HERE
 ```
+
+Make sure to replace `ACCESS_TOKEN_HERE` with the access token of the server admin account.
diff --git a/examples/hosts b/examples/hosts
index d9407b2ab..e4500455d 100644
--- a/examples/hosts
+++ b/examples/hosts
@@ -1,4 +1,4 @@
-# We explicitly ask for your server's external IP address, because the same value is used for configuring Coturn.
+# We explicitly ask for your server's external IP address, because the same value is used for configuring coturn.
 # If you'd rather use a local IP here, make sure to set up `matrix_coturn_turn_external_ip_address`.
 #
 # To connect using a non-root user (and elevate to root with sudo later),
diff --git a/examples/reverse-proxies/apache/README.md b/examples/reverse-proxies/apache/README.md
index da349db74..b4608c87c 100644
--- a/examples/reverse-proxies/apache/README.md
+++ b/examples/reverse-proxies/apache/README.md
@@ -10,5 +10,5 @@ To get started, first follow the [front the integrated reverse-proxy webserver w
 
 `matrix-domain.conf` contains configuration for the Matrix domain, which handles both the Client-Server API (port `443`) and the Matrix Federation API (port `8448`).
 
-`matrix-client-element.conf` is an example for when you're hosting Element at `element.example.com`.
+`matrix-client-element.conf` is an example for when you're hosting Element Web at `element.example.com`.
 This configuration can also be used as an example for handling other domains, depending on the services you enable with the playbook (e.g. `dimension.example.com`, etc).
diff --git a/examples/reverse-proxies/apache/matrix-client-element.conf b/examples/reverse-proxies/apache/matrix-client-element.conf
index 6ae104ea4..d4321c2bd 100644
--- a/examples/reverse-proxies/apache/matrix-client-element.conf
+++ b/examples/reverse-proxies/apache/matrix-client-element.conf
@@ -1,5 +1,5 @@
 # This is a sample file demonstrating how to set up reverse-proxy for element.example.com.
-# If you're not using Element (`matrix_client_element_enabled: false`), you won't need this.
+# If you're not using Element Web (`matrix_client_element_enabled: false`), you won't need this.
 
 <VirtualHost *:80>
 	ServerName element.example.com
diff --git a/examples/reverse-proxies/caddy2-in-container/README.md b/examples/reverse-proxies/caddy2-in-container/README.md
index be654f0d5..3a87bf234 100644
--- a/examples/reverse-proxies/caddy2-in-container/README.md
+++ b/examples/reverse-proxies/caddy2-in-container/README.md
@@ -4,7 +4,6 @@ This directory contains a sample config that shows you how to front the integrat
 
 **Note**: if you're running Caddy on the host itself (not in a container), refer to the [caddy2](../caddy2/README.md) example instead.
 
-
 ## Prerequisite configuration
 
 To get started, first follow the [front the integrated reverse-proxy webserver with another reverse-proxy](../../../docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) instructions and update your playbook's configuration (`inventory/host_vars/matrix.example.com/vars.yml`).
@@ -16,4 +15,4 @@ Then, adjust your Caddy  `docker-compose.yaml` file (if you're using docker-comp
 You can either just use the [Caddyfile](Caddyfile) directly or append its content to your own Caddyfile.
 In both cases make sure to replace all the `example.com` domains with your own domain.
 
-This example does not include additional services like Element, but you should be able copy the first block and replace the `matrix.` subdomain with the subdomain of the some other service (e.g. `element.`).
+This example does not include additional services like Element Web, but you should be able copy the first block and replace the `matrix.` subdomain with the subdomain of the some other service (e.g. `element.`).
diff --git a/examples/reverse-proxies/caddy2-in-container/docker-compose.yaml b/examples/reverse-proxies/caddy2-in-container/docker-compose.yaml
index 5884018dd..49671e7ac 100644
--- a/examples/reverse-proxies/caddy2-in-container/docker-compose.yaml
+++ b/examples/reverse-proxies/caddy2-in-container/docker-compose.yaml
@@ -14,7 +14,7 @@ services:
     volumes:
       - ./Caddyfile:/etc/caddy/Caddyfile
       # - ./site:/var/www
-    #  Other configurations ...
+    #  Other configurations …
 
 networks:
   # add this as well
diff --git a/examples/reverse-proxies/caddy2/README.md b/examples/reverse-proxies/caddy2/README.md
index 2dc3d6b62..dcc1538af 100644
--- a/examples/reverse-proxies/caddy2/README.md
+++ b/examples/reverse-proxies/caddy2/README.md
@@ -2,15 +2,13 @@
 
 This directory contains a sample config that shows you how to front the integrated [Traefik](https://traefik.io/) reverse-proxy webserver with your own [Caddy](https://caddyserver.com/) reverse-proxy.
 
-
 ## Prerequisite configuration
 
 To get started, first follow the [front the integrated reverse-proxy webserver with another reverse-proxy](../../../docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) instructions and update your playbook's configuration (`inventory/host_vars/matrix.example.com/vars.yml`).
 
-
 ## Using the Caddyfile
 
 You can either just use the [Caddyfile](Caddyfile) directly or append its content to your own Caddyfile.
 In both cases make sure to replace all the `example.com` domains with your own domain.
 
-This example does not include additional services like element, but you should be able copy the first block and replace the `matrix` subdomain with the additional services subdomain. I have not tested this though.
+This example does not include additional services like Element, but you should be able copy the first block and replace the `matrix` subdomain with the additional services subdomain. I have not tested this though.
diff --git a/examples/reverse-proxies/nginx-proxy-manager/README.md b/examples/reverse-proxies/nginx-proxy-manager/README.md
index 735901c3f..e90289e9c 100644
--- a/examples/reverse-proxies/nginx-proxy-manager/README.md
+++ b/examples/reverse-proxies/nginx-proxy-manager/README.md
@@ -4,14 +4,12 @@ Similar to standard nginx, [Nginx Proxy Manager](https://nginxproxymanager.com/)
 
 This page summarizes how to use Nginx Proxy Manager (NPM) to front the integrated [Traefik](https://traefik.io/) reverse-proxy webserver.
 
-
 ## Prerequisite configuration
 
 To get started, first follow the [front the integrated reverse-proxy webserver with another reverse-proxy](../../../docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) instructions and update your playbook's configuration (`inventory/host_vars/matrix.example.com/vars.yml`).
 
 If Matrix federation is enabled, then you will need to make changes to [NPM's Docker configuration](https://nginxproxymanager.com/guide/#quick-setup). By default NPM already exposes ports `80` and `443`, but you would also need to **additionally expose the Matrix Federation port** (as it appears on the public side): `8448`.
 
-
 ## Using Nginx Proxy Manager
 
 You'll need to create two proxy hosts in NPM for Matrix web and federation traffic.
diff --git a/examples/reverse-proxies/nginx/README.md b/examples/reverse-proxies/nginx/README.md
index 67381c4f2..1fe76340d 100644
--- a/examples/reverse-proxies/nginx/README.md
+++ b/examples/reverse-proxies/nginx/README.md
@@ -2,16 +2,14 @@
 
 This directory contains a sample config that shows you how to use the [nginx](https://nginx.org/) webserver to front the integrated [Traefik](https://traefik.io/) reverse-proxy webserver with another reverse-proxy.
 
-
 ## Prerequisite configuration
 
 To get started, first follow the [front the integrated reverse-proxy webserver with another reverse-proxy](../../../docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) instructions and update your playbook's configuration (`inventory/host_vars/matrix.example.com/vars.yml`).
 
-
 ## Using the nginx configuration
 
 Copy the [matrix.conf](matrix.conf) file to your nginx server's filesystem, modify it to your needs and include it in your nginx configuration (e.g. `include /path/to/matrix.conf;`).
 
 This configuration **disables SSL certificate retrieval**, so you will **need to obtain SSL certificates manually** (e.g. by using [certbot](https://certbot.eff.org/)) and set the appropriate path in `matrix.conf`. In the example nginx configuration, a single certificate is used for all subdomains (`matrix.example.com`, `element.example.com`, etc.). For your setup, may wish to change this and use separate `server` blocks and separate certificate files for each host.
 
-Also note that your copy of the `matrix.conf` file has to be adapted to whatever services you are using. For example, remove `element.example.com` from the `server_name` list if you don't use [Element](../../../docs/configuring-playbook-client-element.md) web client or add `dimension.example.com` to it if you do use the [Dimension](../../../docs/configuring-playbook-dimension.md) integration manager.
+Also note that your copy of the `matrix.conf` file has to be adapted to whatever services you are using. For example, remove `element.example.com` from the `server_name` list if you don't use [Element Web](../../../docs/configuring-playbook-client-element-web.md) client or add `dimension.example.com` to it if you do use the [Dimension](../../../docs/configuring-playbook-dimension.md) integration manager.
diff --git a/examples/vars.yml b/examples/vars.yml
index b6f20c277..d4d8066f8 100644
--- a/examples/vars.yml
+++ b/examples/vars.yml
@@ -1,6 +1,6 @@
 ---
 # The bare domain name which represents your Matrix identity.
-# Matrix user ids for your server will be of the form (`@user:example.com`).
+# Matrix user IDs for your server will be of the form (`@alice:example.com`).
 #
 # Note: this playbook does not touch the server referenced here.
 # Installation happens on another server ("matrix.example.com", see `matrix_server_fqn_matrix`).
@@ -12,11 +12,15 @@ matrix_domain: example.com
 # The Matrix homeserver software to install.
 # See:
 #  - `roles/custom/matrix-base/defaults/main.yml` for valid options
-# - the `docs/configuring-playbook-IMPLEMENTATION_NAME.md` documentation page, if one is available for your implementation choice
+#  - the `docs/configuring-playbook-IMPLEMENTATION_NAME.md` documentation page, if one is available for your implementation choice
+#
+# By default, we use Synapse, because it's the only full-featured Matrix server at the moment.
+#
+# Note that the homeserver implementation of a server will not be able to be changed without data loss.
 matrix_homeserver_implementation: synapse
 
 # A secret used as a base, for generating various other secrets.
-# You can put any string here, but generating a strong one is preferred (e.g. `pwgen -s 64 1`).
+# You can put any string here, but generating a strong one is preferred. You can create one with a command like `pwgen -s 64 1`.
 matrix_homeserver_generic_secret_key: ''
 
 # By default, the playbook manages its own Traefik (https://doc.traefik.io/traefik/) reverse-proxy server.
@@ -40,7 +44,7 @@ traefik_config_certificatesResolvers_acme_email: ''
 # using this superuser account.
 postgres_connection_password: ''
 
-# By default, we configure Coturn's external IP address using the value specified for `ansible_host` in your `inventory/hosts` file.
+# By default, we configure coturn's external IP address using the value specified for `ansible_host` in your `inventory/hosts` file.
 # If this value is an external IP address, you can skip this section.
 #
 # If `ansible_host` is not the server's external IP address, you have 2 choices:
@@ -48,7 +52,7 @@ postgres_connection_password: ''
 # 2. Uncomment and adjust the line below to specify an IP address manually
 #
 # By default, auto-detection will be attempted using the `https://ifconfig.co/json` API.
-# Default values for this are specified in `matrix_coturn_turn_external_ip_address_auto_detection_*` variables in the Coturn role
+# Default values for this are specified in `matrix_coturn_turn_external_ip_address_auto_detection_*` variables in the coturn role
 # (see `roles/custom/matrix-coturn/defaults/main.yml`).
 #
 # If your server has multiple IP addresses, you may define them in another variable which allows a list of addresses.
diff --git a/group_vars/matrix_servers b/group_vars/matrix_servers
index eecdf9264..4e5f0c9b2 100755
--- a/group_vars/matrix_servers
+++ b/group_vars/matrix_servers
@@ -32,9 +32,12 @@ matrix_playbook_docker_installation_daemon_options_custom: {}
 # yet still use Traefik installed in another way.
 matrix_playbook_traefik_labels_enabled: "{{ matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] }}"
 
-matrix_playbook_reverse_proxy_container_network: "{{ traefik_container_network if traefik_enabled else 'traefik' }}"
+matrix_playbook_reverse_proxy_container_network: "{{ traefik_container_network if traefik_enabled else 'traefik' if matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] else '' }}"
 matrix_playbook_reverse_proxy_hostname: "{{ traefik_identifier if traefik_enabled else 'traefik' }}"
 
+matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled: "{{ traefik_config_http_middlewares_compression_enabled if (traefik_enabled and traefik_config_http_middlewares_compression_enabled) else false }}"
+matrix_playbook_reverse_proxy_traefik_middleware_compression_name: "{{ (traefik_config_http_middlewares_compression_middleware_name + '@file') if traefik_enabled else '' }}"
+
 # A separate Matrix Federation entrypoint is always enabled, unless the federation port matches one of the ports for existing (default) entrypoints
 matrix_playbook_public_matrix_federation_api_traefik_entrypoint_enabled: "{{ matrix_federation_public_port not in [traefik_config_entrypoint_web_port, traefik_config_entrypoint_web_secure_port] }}"
 
@@ -229,7 +232,7 @@ matrix_addons_homeserver_client_api_url: "{{ ('http://' + matrix_playbook_revers
 matrix_addons_homeserver_systemd_services_list: "{{ ([traefik_identifier + '.service'] if matrix_playbook_reverse_proxy_type == 'playbook-managed-traefik' else []) if matrix_playbook_internal_matrix_client_api_traefik_entrypoint_enabled else matrix_homeserver_systemd_services_list }}"
 
 # Starting from version `0.6.0` Conduit natively supports some sync v3 (sliding-sync) features.
-matrix_homeserver_sliding_sync_url: "{{ matrix_sliding_sync_base_url if matrix_sliding_sync_enabled else (matrix_homeserver_url if matrix_homeserver_implementation in ['conduit'] else '') }}"
+matrix_homeserver_sliding_sync_url: "{{ matrix_sliding_sync_base_url if matrix_sliding_sync_enabled else (matrix_homeserver_url if matrix_homeserver_implementation in ['conduit', 'conduwuit'] else '') }}"
 
 ########################################################################
 #                                                                      #
@@ -254,18 +257,18 @@ matrix_homeserver_sliding_sync_url: "{{ matrix_sliding_sync_base_url if matrix_s
 #   - so that addon services (starting later) can communicte with the homeserver via Traefik's internal entrypoint
 #     (see `matrix_playbook_internal_matrix_client_api_traefik_entrypoint_enabled`)
 # - core services (the homeserver) get a level of ~1000
-# - services that the homeserver depends on (database, Redis, ntfy, Coturn, etc.) get a lower level - between 500 and 1000
-# - Coturn gets a higher level if `devture_systemd_service_manager_service_restart_mode == 'one-by-one'` to intentionally delay it, because:
+# - services that the homeserver depends on (database, Redis, ntfy, coturn, etc.) get a lower level - between 500 and 1000
+# - coturn gets a higher level if `devture_systemd_service_manager_service_restart_mode == 'one-by-one'` to intentionally delay it, because:
 #  - starting services one by one means that the service manager role waits for each service to fully start before proceeding to the next one
-#  - if Coturn has a lower priority than the homeserver, it would be started before it
-#  - since Coturn is started before the homeserver, there's no container label telling Traefik to get a `matrix.example.com` certificate
-#  - thus, Coturn would spin and wait for a certificate until it fails. We'd get a playbook failure due to it, but service manager will proceed to start all other services anyway.
+#  - if coturn has a lower priority than the homeserver, it would be started before it
+#  - since coturn is started before the homeserver, there's no container label telling Traefik to get a `matrix.example.com` certificate
+#  - thus, coturn would spin and wait for a certificate until it fails. We'd get a playbook failure due to it, but service manager will proceed to start all other services anyway.
 #  - only later, when the homeserver actually starts, would that certificate be fetched and dumped
 # - reverse-proxying services get level 3000
 # - Matrix utility services (bridges, bots) get a level of 2000/2200, so that:
 #   - they can start before the reverse-proxy
 #   - so that, when the reverse-proxy is up (Matrix is up), all bots and bridges can be interacted with
-# - monitoring services (Prometheus, Grafana, ..) get a level of 4000 - they can start later than all-of-Matrix
+# - monitoring services (Prometheus, Grafana, …) get a level of 4000 - they can start later than all-of-Matrix
 # - services which aren't time-sensitive (various crons and timers) get a level of 5000 - they can start later than all-of-Matrix
 devture_systemd_service_manager_services_list_auto: |
   {{
@@ -293,8 +296,6 @@ devture_systemd_service_manager_services_list_auto: |
     +
     ([{'name': 'matrix-bot-draupnir.service', 'priority': 4000, 'groups': ['matrix', 'bots', 'draupnir', 'bot-draupnir']}] if matrix_bot_draupnir_enabled else [])
     +
-    ([{'name': 'matrix-bot-postmoogle.service', 'priority': 2200, 'groups': ['matrix', 'bots', 'postmoogle', 'bot-postmoogle']}] if matrix_bot_postmoogle_enabled else [])
-    +
     ([{'name': 'matrix-bot-chatgpt.service', 'priority': 2200, 'groups': ['matrix', 'bots', 'chatgpt', 'bot-chatgpt']}] if matrix_bot_chatgpt_enabled else [])
     +
     ([{'name': 'matrix-appservice-discord.service', 'priority': 2000, 'groups': ['matrix', 'bridges', 'appservice-discord']}] if matrix_appservice_discord_enabled else [])
@@ -365,6 +366,8 @@ devture_systemd_service_manager_services_list_auto: |
     +
     ([{'name': 'matrix-mx-puppet-twitter.service', 'priority': 2000, 'groups': ['matrix', 'bridges', 'mx-puppet-twitter']}] if matrix_mx_puppet_twitter_enabled else [])
     +
+    ([{'name': 'matrix-postmoogle.service', 'priority': 2200, 'groups': ['matrix', 'bridges', 'postmoogle']}] if matrix_postmoogle_enabled else [])
+    +
     ([{'name': 'matrix-sms-bridge.service', 'priority': 2000, 'groups': ['matrix', 'bridges', 'sms']}] if matrix_sms_bridge_enabled else [])
     +
     ([{'name': 'matrix-cactus-comments.service', 'priority': 2000, 'groups': ['matrix', 'cactus-comments']}] if matrix_cactus_comments_enabled else [])
@@ -433,6 +436,8 @@ devture_systemd_service_manager_services_list_auto: |
     +
     ([{'name': (keydb_identifier + '.service'), 'priority': 750, 'groups': ['matrix', 'keydb']}] if keydb_enabled else [])
     +
+    ([{'name': (valkey_identifier + '.service'), 'priority': 750, 'groups': ['matrix', 'valkey']}] if valkey_enabled else [])
+    +
     ([{'name': 'matrix-pantalaimon.service', 'priority': 4000, 'groups': ['matrix', 'pantalaimon']}] if matrix_pantalaimon_enabled else [])
     +
     ([{'name': 'matrix-registration.service', 'priority': 4000, 'groups': ['matrix', 'registration', 'matrix-registration']}] if matrix_registration_enabled else [])
@@ -548,6 +553,7 @@ matrix_homeserver_container_client_api_endpoint: |-
       'synapse': ('matrix-synapse-reverse-proxy-companion:8008' if matrix_synapse_reverse_proxy_companion_enabled | default(false) else ('matrix-synapse:'+ matrix_synapse_container_client_api_port | default('8008') | string)),
       'dendrite': ('matrix-dendrite:' + matrix_dendrite_http_bind_port | default('8008') | string),
       'conduit': ('matrix-conduit:' + matrix_conduit_port_number | default('8008') | string),
+      'conduwuit': ('matrix-conduwuit:' + matrix_conduwuit_config_port_number | default('8008') | string),
     }[matrix_homeserver_implementation]
   }}
 
@@ -557,6 +563,7 @@ matrix_homeserver_container_federation_api_endpoint: |-
       'synapse': ('matrix-synapse-reverse-proxy-companion:8048' if matrix_synapse_reverse_proxy_companion_enabled else ('matrix-synapse:'+ matrix_synapse_container_federation_api_plain_port | default('8008') | string)),
       'dendrite': ('matrix-dendrite:' + matrix_dendrite_http_bind_port | default('8008') | string),
       'conduit': ('matrix-conduit:' + matrix_conduit_port_number | default('8008') | string),
+      'conduwuit': ('matrix-conduwuit:' + matrix_conduwuit_config_port_number | default('8008') | string),
     }[matrix_homeserver_implementation]
   }}
 
@@ -748,7 +755,7 @@ matrix_appservice_discord_container_additional_networks_auto: |-
   }}
 
 # If the homeserver disables presence, it's likely better (less wasteful) to also disable presence on the bridge side.
-matrix_appservice_discord_bridge_disablePresence: "{{ not matrix_synapse_presence_enabled }}"
+matrix_appservice_discord_bridge_disablePresence: "{{ (not matrix_synapse_presence_enabled) if matrix_homeserver_implementation == 'synapse' else false }}"
 
 matrix_appservice_discord_appservice_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'discord.as.token', rounds=655555) | to_uuid }}"
 
@@ -909,7 +916,7 @@ matrix_appservice_irc_container_additional_networks_auto: |-
 
 # The IRC bridge docs say that if homeserver presence is disabled, it's better to also disable
 # IRC bridge presence, for performance reasons.
-matrix_appservice_irc_homeserver_enablePresence: "{{ matrix_synapse_presence_enabled }}"
+matrix_appservice_irc_homeserver_enablePresence: "{{ matrix_synapse_presence_enabled if matrix_homeserver_implementation == 'synapse' else true }}"
 
 matrix_appservice_irc_appservice_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'irc.as.token', rounds=655555) | to_uuid }}"
 
@@ -1006,18 +1013,20 @@ matrix_beeper_linkedin_appservice_token: "{{ '%s' | format(matrix_homeserver_gen
 matrix_beeper_linkedin_homeserver_address: "{{ matrix_addons_homeserver_client_api_url }}"
 matrix_beeper_linkedin_homeserver_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'linked.hs.token', rounds=655555) | to_uuid }}"
 
-matrix_beeper_linkedin_login_shared_secret: |-
+matrix_beeper_linkedin_bridge_login_shared_secret_map_auto: |-
   {{
-    ("as_token:" + matrix_appservice_double_puppet_registration_as_token)
+    ({
+      matrix_beeper_linkedin_homeserver_domain: ("as_token:" + matrix_appservice_double_puppet_registration_as_token)
+    })
     if matrix_appservice_double_puppet_enabled
     else (
-      matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret if matrix_synapse_ext_password_provider_shared_secret_auth_enabled
+      {matrix_beeper_linkedin_homeserver_domain: matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret}
       if matrix_synapse_ext_password_provider_shared_secret_auth_enabled
-      else ""
+      else {}
     )
   }}
 
-matrix_beeper_linkedin_bridge_presence: "{{ matrix_synapse_presence_enabled if matrix_synapse_enabled else true }}"
+matrix_beeper_linkedin_bridge_presence: "{{ (matrix_synapse_presence_enabled if matrix_synapse_enabled else true) if matrix_homeserver_implementation == 'synapse' else true }}"
 
 matrix_beeper_linkedin_database_hostname: "{{ postgres_connection_hostname if postgres_enabled else '' }}"
 matrix_beeper_linkedin_database_password: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'maulinkedin.db', rounds=655555) | to_uuid }}"
@@ -1096,9 +1105,16 @@ matrix_mautrix_discord_container_additional_networks_auto: |-
       ([] if matrix_addons_homeserver_container_network == '' else [matrix_addons_homeserver_container_network])
       +
       ([postgres_container_network] if postgres_enabled and matrix_mautrix_facebook_database_hostname == postgres_connection_hostname else [])
+      +
+      ([matrix_playbook_reverse_proxyable_services_additional_network] if (matrix_playbook_reverse_proxyable_services_additional_network and matrix_mautrix_discord_container_labels_traefik_enabled) else [])
     ) | unique
   }}
 
+matrix_mautrix_discord_container_labels_traefik_enabled: "{{ matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] }}"
+matrix_mautrix_discord_container_labels_traefik_docker_network: "{{ matrix_playbook_reverse_proxyable_services_additional_network }}"
+matrix_mautrix_discord_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_primary }}"
+matrix_mautrix_discord_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}"
+
 matrix_mautrix_discord_systemd_required_services_list_auto: |
   {{
     matrix_addons_homeserver_systemd_services_list
@@ -1109,9 +1125,13 @@ matrix_mautrix_discord_systemd_required_services_list_auto: |
 matrix_mautrix_discord_appservice_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'maudisc.as.tok', rounds=655555) | to_uuid }}"
 
 matrix_mautrix_discord_homeserver_address: "{{ matrix_addons_homeserver_client_api_url }}"
-matrix_mautrix_discord_homeserver_public_address: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}://{{ matrix_server_fqn_matrix }}"
 matrix_mautrix_discord_homeserver_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'maudisc.hs.tok', rounds=655555) | to_uuid }}"
 
+matrix_mautrix_discord_bridge_avatar_proxy_key: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'maudisc.avatar', rounds=655555) | to_uuid }}"
+
+matrix_mautrix_discord_hostname: "{{ matrix_server_fqn_matrix }}"
+matrix_mautrix_discord_scheme: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}"
+
 matrix_mautrix_discord_bridge_login_shared_secret_map_auto: |-
   {{
     ({
@@ -1248,7 +1268,7 @@ matrix_mautrix_facebook_appservice_public_prefix: "/{{ '%s' | format(matrix_home
 
 matrix_mautrix_facebook_login_shared_secret: "{{ matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret if matrix_synapse_ext_password_provider_shared_secret_auth_enabled else '' }}"
 
-matrix_mautrix_facebook_bridge_presence: "{{ matrix_synapse_presence_enabled if matrix_synapse_enabled else true }}"
+matrix_mautrix_facebook_bridge_presence: "{{ (matrix_synapse_presence_enabled if matrix_synapse_enabled else true) if matrix_homeserver_implementation == 'synapse' else true }}"
 
 matrix_mautrix_facebook_metrics_enabled: "{{ prometheus_enabled or matrix_metrics_exposure_enabled }}"
 
@@ -1460,7 +1480,7 @@ matrix_mautrix_instagram_homeserver_token: "{{ '%s' | format(matrix_homeserver_g
 
 matrix_mautrix_instagram_login_shared_secret: "{{ matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret if matrix_synapse_ext_password_provider_shared_secret_auth_enabled else '' }}"
 
-matrix_mautrix_instagram_bridge_presence: "{{ matrix_synapse_presence_enabled if matrix_synapse_enabled else true }}"
+matrix_mautrix_instagram_bridge_presence: "{{ (matrix_synapse_presence_enabled if matrix_synapse_enabled else true) if matrix_homeserver_implementation == 'synapse' else true }}"
 
 matrix_mautrix_instagram_metrics_enabled: "{{ prometheus_enabled or matrix_metrics_exposure_enabled }}"
 
@@ -1828,17 +1848,15 @@ matrix_mautrix_twitter_appservice_token: "{{ '%s' | format(matrix_homeserver_gen
 matrix_mautrix_twitter_homeserver_address: "{{ matrix_addons_homeserver_client_api_url }}"
 matrix_mautrix_twitter_homeserver_token: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'twt.hs.token', rounds=655555) | to_uuid }}"
 
-matrix_mautrix_twitter_bridge_login_shared_secret_map_auto: |-
+matrix_mautrix_twitter_provisioning_shared_secret: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'mau.twit.prov', rounds=655555) | to_uuid }}"
+
+matrix_mautrix_twitter_double_puppet_secrets_auto: |-
   {{
     ({
       matrix_mautrix_twitter_homeserver_domain: ("as_token:" + matrix_appservice_double_puppet_registration_as_token)
     })
     if matrix_appservice_double_puppet_enabled
-    else (
-      {matrix_mautrix_twitter_homeserver_domain: matrix_synapse_ext_password_provider_shared_secret_auth_shared_secret}
-      if matrix_synapse_ext_password_provider_shared_secret_auth_enabled
-      else {}
-    )
+    else {}
   }}
 
 matrix_mautrix_twitter_metrics_enabled: "{{ prometheus_enabled or matrix_metrics_exposure_enabled }}"
@@ -2200,12 +2218,14 @@ matrix_hookshot_systemd_wanted_services_list: |
     ([(redis_identifier + '.service')] if redis_enabled and matrix_hookshot_cache_redis_host == redis_identifier else [])
     +
     ([(keydb_identifier + '.service')] if keydb_enabled and matrix_hookshot_cache_redis_host == keydb_identifier else [])
+    +
+    ([(valkey_identifier + '.service')] if valkey_enabled and matrix_hookshot_cache_redis_host == valkey_identifier else [])
   }}
 
 # Hookshot's experimental encryption feature (and possibly others) may benefit from Redis, if available.
 # We only connect to Redis if encryption is enabled (not for everyone who has Redis enabled),
 # because connectivity is still potentially troublesome and is to be investigated.
-matrix_hookshot_cache_redis_host: "{{ redis_identifier if redis_enabled and matrix_hookshot_experimental_encryption_enabled else (keydb_identifier if keydb_enabled and matrix_hookshot_experimental_encryption_enabled else '') }}"
+matrix_hookshot_cache_redis_host: "{{ valkey_identifier if valkey_enabled else (redis_identifier if redis_enabled else (keydb_identifier if keydb_enabled else '')) }}"
 
 matrix_hookshot_container_network: "{{ matrix_addons_container_network }}"
 
@@ -2218,6 +2238,8 @@ matrix_hookshot_container_additional_networks_auto: |
       +
       ([keydb_container_network] if keydb_enabled and matrix_hookshot_cache_redis_host == keydb_identifier else [])
       +
+      ([valkey_container_network] if valkey_enabled and matrix_hookshot_cache_redis_host == valkey_identifier else [])
+      +
       ([matrix_playbook_reverse_proxyable_services_additional_network] if matrix_playbook_reverse_proxyable_services_additional_network and matrix_hookshot_container_labels_traefik_enabled else [])
     ) | unique
   }}
@@ -2571,6 +2593,81 @@ matrix_mx_puppet_groupme_database_password: "{{ '%s' | format(matrix_homeserver_
 #
 ######################################################################
 
+######################################################################
+#
+# matrix-bridge-postmoogle
+#
+######################################################################
+
+# We don't enable bridges by default.
+matrix_postmoogle_enabled: false
+
+matrix_postmoogle_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}"
+
+matrix_postmoogle_ssl_path: |-
+  {{
+    {
+      'playbook-managed-traefik': (traefik_certs_dumper_dumped_certificates_dir_path if traefik_certs_dumper_enabled else ''),
+      'other-traefik-container': (traefik_certs_dumper_dumped_certificates_dir_path if traefik_certs_dumper_enabled else ''),
+      'none': '',
+    }[matrix_playbook_reverse_proxy_type]
+  }}
+
+matrix_playbook_bridge_postmoogle_traefik_tls_cert: "{% for domain in matrix_postmoogle_domains %}/ssl/{{ domain }}/certificate.crt {% endfor %}"
+matrix_playbook_bridge_postmoogle_traefik_key: "{% for domain in matrix_postmoogle_domains %}/ssl/{{ domain }}/privatekey.key {% endfor %}"
+
+matrix_postmoogle_tls_cert: |-
+  {{
+    {
+      'playbook-managed-traefik': (matrix_playbook_bridge_postmoogle_traefik_tls_cert if traefik_certs_dumper_enabled else ''),
+      'other-traefik-container': (matrix_playbook_bridge_postmoogle_traefik_tls_cert if traefik_certs_dumper_enabled else ''),
+      'none': '',
+    }[matrix_playbook_reverse_proxy_type]
+  }}
+
+matrix_postmoogle_tls_key: |-
+  {{
+    {
+      'playbook-managed-traefik': (matrix_playbook_bridge_postmoogle_traefik_key if traefik_certs_dumper_enabled else ''),
+      'other-traefik-container': (matrix_playbook_bridge_postmoogle_traefik_key if traefik_certs_dumper_enabled else ''),
+      'none': '',
+    }[matrix_playbook_reverse_proxy_type]
+  }}
+
+matrix_playbook_bridge_postmoogle_traefik_certs_dumper_waiter_services: "{% for domain in matrix_postmoogle_domains %}{{ traefik_certs_dumper_identifier }}-wait-for-domain@{{ domain }}.service {% endfor %}"
+
+matrix_postmoogle_systemd_required_services_list_auto: |
+  {{
+    matrix_addons_homeserver_systemd_services_list
+    +
+    ([postgres_identifier ~ '.service'] if postgres_enabled and matrix_postmoogle_database_hostname == matrix_postmoogle_database_hostname else [])
+    +
+    (matrix_playbook_bridge_postmoogle_traefik_certs_dumper_waiter_services | trim | split(' ') if matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] and traefik_certs_dumper_enabled else [])
+  }}
+
+# Postgres is the default, except if not using internal Postgres server
+matrix_postmoogle_database_engine: "{{ 'postgres' if postgres_enabled else 'sqlite' }}"
+matrix_postmoogle_database_hostname: "{{ postgres_connection_hostname if postgres_enabled else '' }}"
+matrix_postmoogle_database_password: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'postmoogle.db', rounds=655555) | to_uuid }}"
+
+matrix_postmoogle_homeserver: "{{ matrix_addons_homeserver_client_api_url }}"
+
+matrix_postmoogle_container_network: "{{ matrix_addons_container_network }}"
+
+matrix_postmoogle_container_additional_networks_auto: |-
+  {{
+    (
+      ([] if matrix_addons_homeserver_container_network == '' else [matrix_addons_homeserver_container_network])
+      +
+      ([postgres_container_network] if postgres_enabled and matrix_bot_matrix_reminder_bot_database_hostname == postgres_connection_hostname else [])
+    ) | unique
+  }}
+
+######################################################################
+#
+# /matrix-bridge-postmoogle
+#
+######################################################################
 
 ######################################################################
 #
@@ -2639,10 +2736,12 @@ matrix_bot_matrix_registration_bot_container_network: "{{ matrix_addons_containe
 
 matrix_bot_matrix_registration_bot_container_additional_networks_auto: |-
   {{
-    ([] if matrix_addons_homeserver_container_network == '' else [matrix_addons_homeserver_container_network])
+    ([matrix_homeserver_container_network] if matrix_bot_matrix_registration_bot_container_network != matrix_homeserver_container_network else [])
   }}
 
-matrix_bot_matrix_registration_bot_matrix_homeserver_url: "{{ matrix_addons_homeserver_client_api_url }}"
+# Using `matrix_addons_homeserver_client_api_url` would not work here,
+# because `matrix-traefik:8008` (matrix-internal-client-api) does not expose any `/_synapse` paths.
+matrix_bot_matrix_registration_bot_api_base_url: "{{ matrix_homeserver_container_url }}"
 
 ######################################################################
 #
@@ -2855,84 +2954,6 @@ matrix_bot_baibot_container_additional_networks_auto: |-
 #
 ######################################################################
 
-
-######################################################################
-#
-# matrix-bot-postmoogle
-#
-######################################################################
-
-# We don't enable bots by default.
-matrix_bot_postmoogle_enabled: false
-
-matrix_bot_postmoogle_container_image_self_build: "{{ matrix_architecture not in ['amd64', 'arm64'] }}"
-
-matrix_bot_postmoogle_ssl_path: |-
-  {{
-    {
-      'playbook-managed-traefik': (traefik_certs_dumper_dumped_certificates_dir_path if traefik_certs_dumper_enabled else ''),
-      'other-traefik-container': (traefik_certs_dumper_dumped_certificates_dir_path if traefik_certs_dumper_enabled else ''),
-      'none': '',
-    }[matrix_playbook_reverse_proxy_type]
-  }}
-
-matrix_playbook_bot_postmoogle_traefik_tls_cert: "{% for domain in matrix_bot_postmoogle_domains %}/ssl/{{ domain }}/certificate.crt {% endfor %}"
-matrix_playbook_bot_postmoogle_traefik_key: "{% for domain in matrix_bot_postmoogle_domains %}/ssl/{{ domain }}/privatekey.key {% endfor %}"
-
-matrix_bot_postmoogle_tls_cert: |-
-  {{
-    {
-      'playbook-managed-traefik': (matrix_playbook_bot_postmoogle_traefik_tls_cert if traefik_certs_dumper_enabled else ''),
-      'other-traefik-container': (matrix_playbook_bot_postmoogle_traefik_tls_cert if traefik_certs_dumper_enabled else ''),
-      'none': '',
-    }[matrix_playbook_reverse_proxy_type]
-  }}
-
-matrix_bot_postmoogle_tls_key: |-
-  {{
-    {
-      'playbook-managed-traefik': (matrix_playbook_bot_postmoogle_traefik_key if traefik_certs_dumper_enabled else ''),
-      'other-traefik-container': (matrix_playbook_bot_postmoogle_traefik_key if traefik_certs_dumper_enabled else ''),
-      'none': '',
-    }[matrix_playbook_reverse_proxy_type]
-  }}
-
-matrix_playbook_bot_postmoogle_traefik_certs_dumper_waiter_services: "{% for domain in matrix_bot_postmoogle_domains %}{{ traefik_certs_dumper_identifier }}-wait-for-domain@{{ domain }}.service {% endfor %}"
-
-matrix_bot_postmoogle_systemd_required_services_list_auto: |
-  {{
-    matrix_addons_homeserver_systemd_services_list
-    +
-    ([postgres_identifier ~ '.service'] if postgres_enabled and matrix_bot_postmoogle_database_hostname == matrix_bot_postmoogle_database_hostname else [])
-    +
-    (matrix_playbook_bot_postmoogle_traefik_certs_dumper_waiter_services | trim | split(' ') if matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] and traefik_certs_dumper_enabled else [])
-  }}
-
-# Postgres is the default, except if not using internal Postgres server
-matrix_bot_postmoogle_database_engine: "{{ 'postgres' if postgres_enabled else 'sqlite' }}"
-matrix_bot_postmoogle_database_hostname: "{{ postgres_connection_hostname if postgres_enabled else '' }}"
-matrix_bot_postmoogle_database_password: "{{ '%s' | format(matrix_homeserver_generic_secret_key) | password_hash('sha512', 'postmoogle.db', rounds=655555) | to_uuid }}"
-
-matrix_bot_postmoogle_homeserver: "{{ matrix_addons_homeserver_client_api_url }}"
-
-matrix_bot_postmoogle_container_network: "{{ matrix_addons_container_network }}"
-
-matrix_bot_postmoogle_container_additional_networks_auto: |-
-  {{
-    (
-      ([] if matrix_addons_homeserver_container_network == '' else [matrix_addons_homeserver_container_network])
-      +
-      ([postgres_container_network] if postgres_enabled and matrix_bot_matrix_reminder_bot_database_hostname == postgres_connection_hostname else [])
-    ) | unique
-  }}
-
-######################################################################
-#
-# /matrix-bot-postmoogle
-#
-######################################################################
-
-
 ######################################################################
 #
 # matrix-bot-chatgpt
@@ -3180,7 +3201,6 @@ matrix_pantalaimon_homeserver_url: "{{ matrix_addons_homeserver_client_api_url }
 backup_borg_enabled: false
 
 backup_borg_identifier: matrix-backup-borg
-backup_borg_retention_prefix: matrix-
 backup_borg_storage_archive_name_format: matrix-{now:%Y-%m-%d-%H%M%S}
 
 backup_borg_base_path: "{{ matrix_base_data_path }}/backup-borg"
@@ -3673,7 +3693,7 @@ jitsi_web_stun_servers: |
 # The Jitsi instance installed by this playbook is meant for embedding into Matrix clients, so framing is allowed.
 jitsi_web_framing_enabled: true
 
-# Jitsi (Prosody) only seems to support authenticating with Coturn using `auth-secret`, not `lt-cred-mech`.
+# Jitsi (Prosody) only seems to support authenticating with coturn using `auth-secret`, not `lt-cred-mech`.
 # See: https://prosody.im/doc/coturn
 jitsi_turn_credentials: "{{ matrix_coturn_turn_static_auth_secret if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'auth-secret') else '' }}"
 jitsi_turn_host: "{{ ('turn.' + matrix_server_fqn_matrix) if matrix_coturn_enabled else '' }}"
@@ -4054,10 +4074,10 @@ postgres_managed_databases_auto: |
     }] if (matrix_bot_honoroit_enabled and matrix_bot_honoroit_database_engine == 'postgres' and matrix_bot_honoroit_database_hostname == postgres_connection_hostname) else [])
     +
     ([{
-      'name': matrix_bot_postmoogle_database_name,
-      'username': matrix_bot_postmoogle_database_username,
-      'password': matrix_bot_postmoogle_database_password,
-    }] if (matrix_bot_postmoogle_enabled and matrix_bot_postmoogle_database_engine == 'postgres' and matrix_bot_postmoogle_database_hostname == postgres_connection_hostname) else [])
+      'name': matrix_postmoogle_database_name,
+      'username': matrix_postmoogle_database_username,
+      'password': matrix_postmoogle_database_password,
+    }] if (matrix_postmoogle_enabled and matrix_postmoogle_database_engine == 'postgres' and matrix_postmoogle_database_hostname == postgres_connection_hostname) else [])
     +
     ([{
       'name': matrix_bot_maubot_database_name,
@@ -4393,11 +4413,11 @@ ntfy_visitor_request_limit_exempt_hosts_hostnames_auto: |
 
 ######################################################################
 #
-# etke/redis
+# redis
 #
 ######################################################################
 
-redis_enabled: "{{ not keydb_enabled and (matrix_synapse_workers_enabled or (matrix_hookshot_enabled and matrix_hookshot_experimental_encryption_enabled)) }}"
+redis_enabled: "{{ not (keydb_enabled or valkey_enabled) and (matrix_synapse_workers_enabled or (matrix_hookshot_enabled and matrix_hookshot_encryption_enabled)) }}"
 
 redis_identifier: matrix-redis
 
@@ -4408,7 +4428,7 @@ redis_base_path: "{{ matrix_base_data_path }}/redis"
 
 ######################################################################
 #
-# /etke/redis
+# /redis
 #
 ######################################################################
 
@@ -4418,7 +4438,7 @@ redis_base_path: "{{ matrix_base_data_path }}/redis"
 #
 ######################################################################
 
-keydb_enabled: "{{ matrix_synapse_workers_enabled or (matrix_hookshot_enabled and matrix_hookshot_experimental_encryption_enabled) }}"
+keydb_enabled: false
 
 keydb_identifier: matrix-keydb
 
@@ -4442,13 +4462,38 @@ keydb_arch: |-
 #
 ######################################################################
 
+
+######################################################################
+#
+# valkey
+#
+######################################################################
+
+valkey_enabled: "{{ matrix_synapse_workers_enabled or (matrix_hookshot_enabled and matrix_hookshot_encryption_enabled) }}"
+
+valkey_identifier: matrix-valkey
+
+valkey_uid: "{{ matrix_user_uid }}"
+valkey_gid: "{{ matrix_user_gid }}"
+
+valkey_base_path: "{{ matrix_base_data_path }}/valkey"
+
+valkey_arch: "{{ matrix_architecture }}"
+
+######################################################################
+#
+# valkey
+#
+######################################################################
+
+
 ######################################################################
 #
 # matrix-client-element
 #
 ######################################################################
 
-# By default, this playbook installs the Element web UI on the `matrix_server_fqn_element` domain.
+# By default, this playbook installs the Element Web on the `matrix_server_fqn_element` domain.
 # If you wish to connect to your Matrix server by other means, you may wish to disable this.
 matrix_client_element_enabled: true
 
@@ -4467,6 +4512,9 @@ matrix_client_element_container_labels_traefik_docker_network: "{{ matrix_playbo
 matrix_client_element_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_primary }}"
 matrix_client_element_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}"
 
+matrix_client_element_container_labels_traefik_compression_middleware_enabled: "{{ matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled }}"
+matrix_client_element_container_labels_traefik_compression_middleware_name: "{{ matrix_playbook_reverse_proxy_traefik_middleware_compression_name if matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled else '' }}"
+
 matrix_client_element_default_hs_url: "{{ matrix_homeserver_url }}"
 matrix_client_element_default_is_url: "{{ matrix_identity_server_url }}"
 
@@ -4516,6 +4564,9 @@ matrix_client_hydrogen_container_labels_traefik_docker_network: "{{ matrix_playb
 matrix_client_hydrogen_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_primary }}"
 matrix_client_hydrogen_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}"
 
+matrix_client_hydrogen_container_labels_traefik_compression_middleware_enabled: "{{ matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled }}"
+matrix_client_hydrogen_container_labels_traefik_compression_middleware_name: "{{ matrix_playbook_reverse_proxy_traefik_middleware_compression_name if matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled else '' }}"
+
 matrix_client_hydrogen_scheme: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}"
 
 matrix_client_hydrogen_default_hs_url: "{{ matrix_homeserver_url }}"
@@ -4549,6 +4600,9 @@ matrix_client_cinny_container_labels_traefik_docker_network: "{{ matrix_playbook
 matrix_client_cinny_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_primary }}"
 matrix_client_cinny_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}"
 
+matrix_client_cinny_container_labels_traefik_compression_middleware_enabled: "{{ matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled }}"
+matrix_client_cinny_container_labels_traefik_compression_middleware_name: "{{ matrix_playbook_reverse_proxy_traefik_middleware_compression_name if matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled else '' }}"
+
 matrix_client_cinny_scheme: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}"
 
 matrix_client_cinny_default_hs_url: "{{ matrix_homeserver_url }}"
@@ -4655,6 +4709,8 @@ matrix_synapse_container_additional_networks_auto: |
       +
       ([keydb_container_network] if matrix_synapse_redis_enabled and matrix_synapse_redis_host == keydb_identifier else [])
       +
+      ([valkey_container_network] if matrix_synapse_redis_enabled and matrix_synapse_redis_host == valkey_identifier else [])
+      +
       ([exim_relay_container_network] if (exim_relay_enabled and matrix_synapse_email_enabled and matrix_synapse_email_smtp_host == exim_relay_identifier and matrix_synapse_container_network != exim_relay_container_network) else [])
       +
       ([matrix_ma1sd_container_network] if (matrix_ma1sd_enabled and matrix_synapse_account_threepid_delegates_msisdn == matrix_synapse_account_threepid_delegates_msisdn_mas1sd_url and matrix_synapse_container_network != matrix_ma1sd_container_network) else [])
@@ -4667,6 +4723,9 @@ matrix_synapse_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_prim
 matrix_synapse_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}"
 matrix_synapse_container_labels_traefik_hostname: "{{ matrix_server_fqn_matrix }}"
 
+matrix_synapse_container_labels_traefik_compression_middleware_enabled: "{{ matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled }}"
+matrix_synapse_container_labels_traefik_compression_middleware_name: "{{ matrix_playbook_reverse_proxy_traefik_middleware_compression_name if matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled else '' }}"
+
 matrix_synapse_container_labels_matrix_labels_enabled: "{{ not matrix_synapse_workers_enabled }}"
 
 matrix_synapse_container_labels_public_client_root_redirection_enabled: "{{ matrix_synapse_container_labels_public_client_root_redirection_url != '' }}"
@@ -4739,6 +4798,8 @@ matrix_synapse_systemd_required_services_list_auto: |
     +
     ([keydb_identifier ~ '.service'] if matrix_synapse_redis_enabled and matrix_synapse_redis_host == keydb_identifier else [])
     +
+    ([valkey_identifier ~ '.service'] if matrix_synapse_redis_enabled and matrix_synapse_redis_host == valkey_identifier else [])
+    +
     (['matrix-goofys.service'] if matrix_s3_media_store_enabled else [])
     +
     (['matrix-authentication-service.service'] if (matrix_authentication_service_enabled and matrix_synapse_experimental_features_msc3861_enabled) else [])
@@ -4752,9 +4813,9 @@ matrix_synapse_systemd_wanted_services_list_auto: |
   }}
 
 # Synapse workers (used for parallel load-scaling) need Redis for IPC.
-matrix_synapse_redis_enabled: "{{ redis_enabled or keydb_enabled }}"
-matrix_synapse_redis_host: "{{ redis_identifier if redis_enabled else (keydb_identifier if keydb_enabled else '') }}"
-matrix_synapse_redis_password: "{{ redis_connection_password if redis_enabled else (keydb_connection_password if keydb_enabled else '') }}"
+matrix_synapse_redis_enabled: "{{ redis_enabled or keydb_enabled or valkey_enabled }}"
+matrix_synapse_redis_host: "{{ valkey_identifier if valkey_enabled else (redis_identifier if redis_enabled else (keydb_identifier if keydb_enabled else '')) }}"
+matrix_synapse_redis_password: "{{ valkey_connection_password if valkey_enabled else (redis_connection_password if redis_enabled else (keydb_connection_password if keydb_enabled else '')) }}"
 
 matrix_synapse_container_extra_arguments_auto: "{{ matrix_homeserver_container_extra_arguments_auto }}"
 matrix_synapse_app_service_config_files_auto: "{{ matrix_homeserver_app_service_config_files_auto }}"
@@ -4772,6 +4833,8 @@ matrix_synapse_experimental_features_msc3861_client_secret: "{{ '%s' | format(ma
 matrix_synapse_experimental_features_msc3861_admin_token: "{{ matrix_authentication_service_config_matrix_secret if matrix_authentication_service_enabled else '' }}"
 matrix_synapse_experimental_features_msc3861_account_management_url: "{{ matrix_authentication_service_account_management_url if matrix_authentication_service_enabled else '' }}"
 
+matrix_synapse_experimental_features_msc4108_enabled: "{{ matrix_authentication_service_enabled and not matrix_authentication_service_migration_in_progress }}"
+
 # Disable password authentication when delegating authentication to Matrix Authentication Service.
 # Unless this is done, Synapse fails on startup with:
 # > Error in configuration at 'password_config.enabled':
@@ -4855,6 +4918,9 @@ matrix_synapse_reverse_proxy_companion_container_labels_traefik_entrypoints: "{{
 matrix_synapse_reverse_proxy_companion_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}"
 matrix_synapse_reverse_proxy_companion_container_labels_traefik_hostname: "{{ matrix_server_fqn_matrix }}"
 
+matrix_synapse_reverse_proxy_companion_container_labels_traefik_compression_middleware_enabled: "{{ matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled }}"
+matrix_synapse_reverse_proxy_companion_container_labels_traefik_compression_middleware_name: "{{ matrix_playbook_reverse_proxy_traefik_middleware_compression_name if matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled else '' }}"
+
 matrix_synapse_reverse_proxy_companion_container_labels_public_client_synapse_client_api_enabled: "{{ matrix_synapse_container_labels_public_client_synapse_client_api_enabled }}"
 matrix_synapse_reverse_proxy_companion_container_labels_public_client_synapse_admin_api_enabled: "{{ matrix_synapse_container_labels_public_client_synapse_admin_api_enabled }}"
 
@@ -4929,6 +4995,10 @@ matrix_synapse_admin_config_asManagedUsers_auto: |
       '^@'+(matrix_bot_buscarron_login | default('') | regex_escape) +':'+(matrix_domain | regex_escape)+'$',
     ] if matrix_bot_buscarron_enabled else [])
     +
+    ([
+      '^@'+(matrix_bot_draupnir_login | default('') | regex_escape) +':'+(matrix_domain | regex_escape)+'$',
+    ] if matrix_bot_draupnir_enabled else [])
+    +
     ([
       '^@'+(matrix_bot_chatgpt_matrix_bot_username_localpart | default('') | regex_escape) +':'+(matrix_domain | regex_escape)+'$',
     ] if matrix_bot_chatgpt_enabled else [])
@@ -4950,8 +5020,8 @@ matrix_synapse_admin_config_asManagedUsers_auto: |
     ] if matrix_bot_maubot_enabled else [])
     +
     ([
-      '^@'+(matrix_bot_postmoogle_login | default('') | regex_escape) +':'+(matrix_domain | regex_escape)+'$',
-    ] if matrix_bot_postmoogle_enabled else [])
+      '^@'+(matrix_postmoogle_login | default('') | regex_escape) +':'+(matrix_domain | regex_escape)+'$',
+    ] if matrix_postmoogle_enabled else [])
     +
     ([
       '^@_discord_[a-zA-Z0-9]+:'+(matrix_domain | regex_escape)+'$',
@@ -5435,6 +5505,7 @@ grafana_default_home_dashboard_path: |-
       'synapse': ('/etc/grafana/dashboards/synapse.json' if matrix_synapse_metrics_enabled and matrix_synapse_metrics_enabled else ('/etc/grafana/dashboards/node-exporter-full.json' if prometheus_node_exporter_enabled else '')),
       'dendrite': ('/etc/grafana/dashboards/node-exporter-full.json' if prometheus_node_exporter_enabled else ''),
       'conduit': ('/etc/grafana/dashboards/node-exporter-full.json' if prometheus_node_exporter_enabled else ''),
+      'conduwuit': ('/etc/grafana/dashboards/node-exporter-full.json' if prometheus_node_exporter_enabled else ''),
     }[matrix_homeserver_implementation]
   }}
 
@@ -5492,6 +5563,7 @@ matrix_registration_shared_secret: |-
       'synapse': matrix_synapse_registration_shared_secret | default (''),
       'dendrite': matrix_dendrite_client_api_registration_shared_secret | default (''),
       'conduit': '',
+      'conduwuit': '',
     }[matrix_homeserver_implementation]
   }}
 
@@ -5736,6 +5808,68 @@ matrix_conduit_turn_password: "{{ matrix_coturn_lt_cred_mech_password if (matrix
 ######################################################################
 
 
+######################################################################
+#
+# matrix-conduwuit
+#
+######################################################################
+
+matrix_conduwuit_enabled: "{{ matrix_homeserver_implementation == 'conduwuit' }}"
+
+matrix_conduwuit_hostname: "{{ matrix_server_fqn_matrix }}"
+
+matrix_conduwuit_config_allow_federation: "{{ matrix_homeserver_federation_enabled }}"
+
+matrix_conduwuit_container_network: "{{ matrix_homeserver_container_network }}"
+
+matrix_conduwuit_container_additional_networks_auto: |
+  {{
+    (
+      ([matrix_playbook_reverse_proxyable_services_additional_network] if matrix_conduwuit_container_labels_traefik_enabled and matrix_playbook_reverse_proxyable_services_additional_network else [])
+    ) | unique
+  }}
+
+matrix_conduwuit_container_labels_traefik_enabled: "{{ matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] and not matrix_synapse_workers_enabled }}"
+matrix_conduwuit_container_labels_traefik_docker_network: "{{ matrix_playbook_reverse_proxyable_services_additional_network }}"
+matrix_conduwuit_container_labels_traefik_entrypoints: "{{ traefik_entrypoint_primary }}"
+matrix_conduwuit_container_labels_traefik_tls_certResolver: "{{ traefik_certResolver_primary }}"
+
+matrix_conduwuit_container_labels_public_client_root_redirection_enabled: "{{ matrix_conduwuit_container_labels_public_client_root_redirection_url != '' }}"
+matrix_conduwuit_container_labels_public_client_root_redirection_url: "{{ (('https://' if matrix_playbook_ssl_enabled else 'http://') + matrix_server_fqn_element) if matrix_client_element_enabled else '' }}"
+
+matrix_conduwuit_container_labels_public_federation_api_traefik_hostname: "{{ matrix_server_fqn_matrix_federation }}"
+matrix_conduwuit_container_labels_public_federation_api_traefik_entrypoints: "{{ matrix_federation_traefik_entrypoint_name }}"
+matrix_conduwuit_container_labels_public_federation_api_traefik_tls: "{{ matrix_federation_traefik_entrypoint_tls }}"
+
+matrix_conduwuit_container_labels_internal_client_api_enabled: "{{ matrix_playbook_internal_matrix_client_api_traefik_entrypoint_enabled }}"
+matrix_conduwuit_container_labels_internal_client_api_traefik_entrypoints: "{{ matrix_playbook_internal_matrix_client_api_traefik_entrypoint_name }}"
+
+matrix_conduwuit_config_turn_uris: |
+  {{
+    ([
+      'turns:' + matrix_server_fqn_matrix + '?transport=udp',
+      'turns:' + matrix_server_fqn_matrix + '?transport=tcp',
+    ] if matrix_coturn_enabled and matrix_coturn_tls_enabled else [])
+    +
+    ([
+      'turn:' + matrix_server_fqn_matrix + '?transport=udp',
+      'turn:' + matrix_server_fqn_matrix + '?transport=tcp',
+    ] if matrix_coturn_enabled else [])
+  }}
+
+matrix_conduwuit_config_turn_secret: "{{ matrix_coturn_turn_static_auth_secret if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'auth-secret') else '' }}"
+matrix_conduwuit_config_turn_username: "{{ matrix_coturn_lt_cred_mech_username if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'lt-cred-mech') else '' }}"
+matrix_conduwuit_config_turn_password: "{{ matrix_coturn_lt_cred_mech_password if (matrix_coturn_enabled and matrix_coturn_authentication_method == 'lt-cred-mech') else '' }}"
+
+matrix_conduwuit_self_check_validate_certificates: "{{ matrix_playbook_ssl_enabled }}"
+
+######################################################################
+#
+# /matrix-conduwuit
+#
+######################################################################
+
+
 ######################################################################
 #
 # matrix-user-creator
@@ -5775,10 +5909,10 @@ matrix_user_creator_users_auto: |
     }] if matrix_bot_honoroit_enabled else [])
     +
     ([{
-      'username': matrix_bot_postmoogle_login,
-      'initial_password': matrix_bot_postmoogle_password,
+      'username': matrix_postmoogle_login,
+      'initial_password': matrix_postmoogle_password,
       'initial_type': 'bot',
-    }] if matrix_bot_postmoogle_enabled else [])
+    }] if matrix_postmoogle_enabled else [])
     +
     ([{
       'username': matrix_bot_buscarron_login,
@@ -5791,6 +5925,12 @@ matrix_user_creator_users_auto: |
       'initial_password': matrix_bot_maubot_initial_password,
       'initial_type': 'bot',
     }] if matrix_bot_maubot_enabled else [])
+        +
+    ([{
+      'username': matrix_bot_draupnir_login,
+      'initial_password': matrix_bot_draupnir_password,
+      'initial_type': 'bot',
+    }] if matrix_bot_draupnir_enabled and matrix_bot_draupnir_password else [])
   }}
 
 ######################################################################
@@ -5885,6 +6025,10 @@ matrix_static_files_file_matrix_client_property_org_matrix_msc2965_authenticatio
 matrix_static_files_file_matrix_client_property_m_tile_server_entries_enabled: "{{ matrix_client_element_location_sharing_enabled }}"
 matrix_static_files_file_matrix_client_property_m_tile_server_map_style_url: "{{ ('https://' if matrix_playbook_ssl_enabled else 'http://') + matrix_server_fqn_element }}/map_style.json"
 
+# We set this regardless of whether synapse-admin is enabled, because people may wish to use a hosted (externally) synapse-admin installation and still have it auto-configured.
+# See: https://github.com/etkecc/synapse-admin/pull/126
+matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_auto: "{{ matrix_synapse_admin_configuration if matrix_homeserver_implementation == 'synapse' else {} }}"
+
 matrix_static_files_file_matrix_server_property_m_server: "{{ matrix_server_fqn_matrix_federation }}:{{ matrix_federation_public_port }}"
 
 matrix_static_files_scheme: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}"
@@ -5939,6 +6083,10 @@ traefik_base_path: "{{ matrix_base_data_path }}/traefik"
 traefik_uid: "{{ matrix_user_uid }}"
 traefik_gid: "{{ matrix_user_gid }}"
 
+# It's common for setups to deal with large file uploads which may take longer than the default readTimeout (60s).
+# This override (for the `web` entrypoint) also cascades to overriding the `web-secure` entrypoint and the `matrix-federation` entrypoint.
+traefik_config_entrypoint_web_transport_respondingTimeouts_readTimeout: 300s
+
 traefik_additional_entrypoints_auto: |
   {{
     ([matrix_playbook_public_matrix_federation_api_traefik_entrypoint_definition] if matrix_playbook_public_matrix_federation_api_traefik_entrypoint_enabled else [])
diff --git a/i18n/.gitignore b/i18n/.gitignore
new file mode 100644
index 000000000..dcb737746
--- /dev/null
+++ b/i18n/.gitignore
@@ -0,0 +1,6 @@
+.venv/
+doctrees
+.doctrees/
+/**/*.mo
+
+/translations/*
diff --git a/i18n/PUBLISHED_LANGUAGES b/i18n/PUBLISHED_LANGUAGES
new file mode 100644
index 000000000..e69de29bb
diff --git a/i18n/README.md b/i18n/README.md
new file mode 100644
index 000000000..94cf013e4
--- /dev/null
+++ b/i18n/README.md
@@ -0,0 +1,104 @@
+<!--
+SPDX-FileCopyrightText: 2024 Slavi Pantaleev <slavi@devture.com>
+SPDX-FileCopyrightText: 2024 Suguru Hirahara <acioustick@noreply.codeberg.org>
+
+SPDX-License-Identifier: AGPL-3.0-or-later
+-->
+
+# Internationalization
+
+Translated documentation files are published and maintained in [`translations/`](translations/) directory.
+
+Currently, we support translation of:
+
+- Markdown files found at the top level project directory
+- Markdown files found in the [`docs`](../docs/) directory (this is where the bulk of the documentation is)
+- this current document in the `i18n` directory
+
+💡 For readers' sake, we only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold (requiring that at least the project README and core installation guides are translated).
+
+Organization of this `i18n` directory is as follows:
+
+- [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translations/](translations/) directory)
+- [.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionaly ignore translated results (`translations/<language>` directories) for languages taht are still in progress. We only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold.
+- [justfile](justfile): a list of recipes for [just](https://github.com/casey/just) command runner
+- [requirements.txt](requirements.txt): a list of Python packages required to work with translations
+- [translation-templates/](translation-templates/): a list of English translation templates - strings extracted from Markdown files
+- [locales/](locales/): localization files for languages
+- [translations/](translations/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language))
+
+## Guide for translators
+
+This project uses [Sphinx](https://www.sphinx-doc.org/) to generate translated documents.
+
+For details about using Sphinx for translation, refer [this official document](https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) as well.
+
+For now, translations are handled manually by editing `.po` files in the `locales/<language>` directory. In the future, we plan on integrating with [Weblate](https://weblate.org/) to allow for translating from a web interface.
+
+### (Recommended) Using the uv package manager and just command runner
+
+If you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed, you can use our [justfile](justfile) recipes to easily manage translation files and build translated documents.
+
+The recipes will use [uv](https://github.com/astral-sh/uv) to auto-create [a Python virtual environment](https://docs.astral.sh/uv/pip/environments/) in the `.venv` directory and install the required Python packages (as per [requirements.txt](requirements.txt)) to it.
+
+#### Preparation
+
+Make sure you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed.
+
+#### Translation
+
+Recommended flow when working on a new language (replace `<language>` with the language code, e.g. `bg`):
+
+- Update the locale files for your language: `just sync-for-language <language>` (internally, this automatically runs `just extract-translation-templates` to make sure the translation templates are up-to-date)
+
+- Use an editor to translate the files in the `locales/<language>` directory
+
+- Build translated documents: `just build-for-language <language>`
+
+- Preview the result in the `translations/<language>` directory
+
+- Commit your changes done to the `locales/<language>` directory
+
+- If you have progressed with the translation beyond a certain threshold, consider [Publishing translations in a new language](#publish-translations-in-a-new-language)
+
+### Using any other package manager and manual scripts
+
+If you cannot use [uv](https://docs.astral.sh/uv/) and/or [just](https://github.com/casey/just), you can:
+
+- manage Python packages in another way ([pip](https://pip.pypa.io/en/stable/), [Poetry](https://python-poetry.org/), etc.)
+- manage translation strings and build translated documents manually by invoking scripts from the [bin](bin/) directory
+
+#### Preparation
+
+##### virtualenv and pip
+
+- Create a Python virtual environment in the `.venv` directory: `virtualenv .venv`
+- Activate the virtual environment: `source .venv/bin/activate`
+- Install the required Python packages using [pip](https://pip.pypa.io/en/stable/): `pip install -r requirements.txt`
+
+#### Translation
+
+Recommended flow when working on a new language (replace `<language>` with the language code, e.g. `bg`):
+
+- Ensure the English translation templates ([translation-templates/](translation-templates/)) are extracted: `./bin/extract-translation-templates.sh`
+
+- Update the locale files for your language: `./bin/sync-translation-templates-to-locales.sh <language>`
+
+- Use an editor to translate the files in the `locales/<language>` directory
+
+- Build translated documents: `./bin/build-translated-result.sh <language>`
+
+- Preview the result in the `translations/<language>` directory
+
+- Commit your changes done to the `locales/<language>` directory
+
+- If you have progressed with the translation beyond a certain threshold, consider [Publishing translations in a new language](#publish-translations-in-a-new-language)
+
+### Publish translations in a new language
+
+To publish prebuilt documents translated in a new language to the `translations/<language>` directory:
+
+- add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file
+- whitelist its `translations/<language>` directory by adding a `!translations/<language>` rule to the [.gitignore](.gitignore) file
+
+💡 Leave a trailing new line at the end of the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file.
diff --git a/i18n/bin/build-translated-result.sh b/i18n/bin/build-translated-result.sh
new file mode 100755
index 000000000..0f860fe7f
--- /dev/null
+++ b/i18n/bin/build-translated-result.sh
@@ -0,0 +1,61 @@
+#!/bin/bash
+
+# SPDX-FileCopyrightText: 2024 Slavi Pantaleev <slavi@devture.com>
+# SPDX-FileCopyrightText: 2024 Suguru Hirahara <acioustick@noreply.codeberg.org>
+#
+# SPDX-License-Identifier: AGPL-3.0-or-later
+
+# This script builds the translated result (translated project) for a given language in the `translations/<language>/` directory.
+
+set -euxo pipefail
+
+if [ $# -ne 1 ]; then
+    echo "Usage: $0 <language>"
+    exit 1
+fi
+
+LANGUAGE=$1
+
+base_path="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)"
+
+if [ ! -f ${base_path}/i18n/locales/${LANGUAGE}/LC_MESSAGES/README.po ]; then
+    echo "Locales for ${LANGUAGE} not found. Please run the `sync-translation-templates-to-locales.sh` script first."
+    exit 1
+fi
+
+# Prepare a clean build directory
+if [ -d ${base_path}/i18n/translated-result-build-${LANGUAGE} ]; then
+    rm -rf ${base_path}/i18n/translated-result-build-${LANGUAGE}
+fi
+mkdir -p ${base_path}/i18n/translated-result-build-${LANGUAGE}
+
+# Build the translated documentation
+sphinx-build \
+    -b markdown \
+    -D language="${LANGUAGE}" \
+    ${base_path}/ \
+    ${base_path}/i18n/translated-result-build-${LANGUAGE}
+
+# Clean up .mo files produced during the build.
+# We don't commit them to the repository anyway, so they can be left alone,
+# but we'd rather keep things clean anyway.
+find ${base_path}/i18n/locales/${LANGUAGE} -type f -name '*.mo' -delete
+
+# Clean up the build directory
+rm -rf ${base_path}/i18n/translated-result-build-${LANGUAGE}/.doctrees
+
+# Copy assets
+cp -r ${base_path}/docs/assets ${base_path}/i18n/translated-result-build-${LANGUAGE}/docs/assets/
+
+# Remove the old result directory for this language
+if [ -d ${base_path}/i18n/translations/${LANGUAGE} ]; then
+    rm -rf ${base_path}/i18n/translations/${LANGUAGE}
+fi
+
+# Make sure the `translations/` directory exists
+if [ ! -d ${base_path}/i18n/translations ]; then
+    mkdir -p ${base_path}/i18n/translations
+fi
+
+# Relocate the built result to translations/<language>
+mv ${base_path}/i18n/translated-result-build-${LANGUAGE} ${base_path}/i18n/translations/${LANGUAGE}
diff --git a/i18n/bin/extract-translation-templates.sh b/i18n/bin/extract-translation-templates.sh
new file mode 100755
index 000000000..3cbaeec8f
--- /dev/null
+++ b/i18n/bin/extract-translation-templates.sh
@@ -0,0 +1,36 @@
+#!/bin/bash
+
+# SPDX-FileCopyrightText: 2024 Slavi Pantaleev <slavi@devture.com>
+
+# This script extracts translation templates (original English strings) into the `translation-templates/` directory.
+# These templates are later used to generate locale files for each language in the `locales/` directory.
+#
+# By default `sphinx-build` extracts the templates into a `build/gettext` directory, while we'd like to have them in the `translation-templates/` directory.
+# To avoid the `POT-Creation-Date` information in templates being updated every time we extract them,
+# we restore the `translation-templates/` directory to the `build/gettext` directory before running the script.
+
+set -euxo pipefail
+
+base_path="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)"
+
+# Restore the `translation-templates/` directory to the `build/gettext` directory
+if [ -d ${base_path}/i18n/build ]; then
+    rm -rf ${base_path}/i18n/build
+fi
+mkdir -p ${base_path}/i18n/build
+cp -r ${base_path}/i18n/translation-templates ${base_path}/i18n/build/gettext
+
+# Extract translation templates from the documentation into the `build/gettext` directory
+sphinx-build -M gettext ${base_path} ${base_path}/i18n/build
+
+# Clean up the build directory
+rm -rf ${base_path}/i18n/build/gettext/.doctrees
+
+# Update the `translation-templates/` directory with the new templates
+if [ -d ${base_path}/i18n/translation-templates ]; then
+    rm -rf ${base_path}/i18n/translation-templates
+fi
+mv ${base_path}/i18n/build/gettext ${base_path}/i18n/translation-templates
+
+# Get rid of the `build` directory
+rmdir ${base_path}/i18n/build
diff --git a/i18n/bin/sync-translation-templates-to-locales.sh b/i18n/bin/sync-translation-templates-to-locales.sh
new file mode 100755
index 000000000..c1678a393
--- /dev/null
+++ b/i18n/bin/sync-translation-templates-to-locales.sh
@@ -0,0 +1,42 @@
+#!/bin/bash
+
+# SPDX-FileCopyrightText: 2024 Slavi Pantaleev <slavi@devture.com>
+#
+# SPDX-License-Identifier: AGPL-3.0-or-later
+
+# This script updates the translation files (locales/<language>/**/*.po) for a given language.
+# It uses the translation templates (translation-templates/**/*.pot) to generate the translation files.
+
+set -euxo pipefail
+
+if [ $# -ne 1 ]; then
+    echo "Usage: $0 <language>"
+    exit 1
+fi
+
+LANGUAGE=$1
+
+base_path="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)"
+
+if [ ! -f ${base_path}/i18n/translation-templates/README.pot ]; then
+    echo "Translation templates not found. Please run the `extract-translation-templates.sh` script first."
+    exit 1
+fi
+
+# Create necessary directories to avoid race conditions caused by
+# Sphinx potentially trying to concurrently create them from separate threads below.
+mkdir -p ${base_path}/i18n/locales/${LANGUAGE}/LC_MESSAGES/docs
+
+# Update the translation files
+sphinx-intl update \
+    --pot-dir ${base_path}/i18n/translation-templates \
+    --locale-dir ${base_path}/i18n/locales \
+    --language ${LANGUAGE}
+
+# Post-process all .po files to remove word-wrapping.
+#
+# Tools for editing .po files like Poedit don't use word-wrapping,
+# and us not using word-wrapping here means diffs can be smaller.
+for po_file in $(find ${base_path}/i18n/locales -name '*.po'); do
+    msgcat --no-wrap -o "$po_file" "$po_file"
+done
diff --git a/i18n/justfile b/i18n/justfile
new file mode 100644
index 000000000..57b9d8400
--- /dev/null
+++ b/i18n/justfile
@@ -0,0 +1,65 @@
+# SPDX-FileCopyrightText: 2024 Slavi Pantaleev <slavi@devture.com>
+# SPDX-FileCopyrightText: 2024 Suguru Hirahara <acioustick@noreply.codeberg.org>
+#
+# SPDX-License-Identifier: AGPL-3.0-or-later
+
+# Shows help
+default:
+    @just --list --justfile {{ justfile() }}
+
+# Extracts original English strings (translation templates) into the `translation-templates/` directory
+extract-translation-templates: _venv
+    @echo "Extracting translation templates…"
+    PATH={{ justfile_directory() }}/.venv/bin:$PATH {{ justfile_directory() }}/bin/extract-translation-templates.sh
+
+# Syncs the translation templates (affects `translation-templates/`) and strings (affects `locales/*`) for all published languages (`PUBLISHED_LANGUAGES`)
+sync-for-all-published-languages: _venv
+    #!/bin/sh
+    cat {{ justfile_directory() }}/PUBLISHED_LANGUAGES | while read language ; do
+        {{ just_executable() }} sync-for-language $language
+    done
+
+# Syncs the translation templates (affects `translation-templates/`) and strings for all known languages (`KNOWN_LANGUAGES`)
+sync-for-all-known-languages:
+    #!/bin/sh
+    find {{ justfile_directory() }}/locales -mindepth 1 -maxdepth 1 -type d | while read path ; do
+        language=$(basename "$path")
+        echo "Syncing for language $language…"
+        {{ just_executable() }} sync-for-language $language
+    done
+
+# Updates the translation templates (affects `translation-templates/`) and syncs the translation strings for a given language (affects `locales/{{ language }}`)
+sync-for-language language: extract-translation-templates (_sync-translation-templates-to-locales-for-language language)
+
+# Updates `locales/{{ language }}` files based on the original template strings from `translation-templates/`
+_sync-translation-templates-to-locales-for-language language: _venv
+    PATH={{ justfile_directory() }}/.venv/bin:$PATH {{ justfile_directory() }}/bin/sync-translation-templates-to-locales.sh {{ language }}
+
+# Builds the translated result for a given language into the `translations/{{ language }}` directory
+build-for-language language: _venv
+    PATH={{ justfile_directory() }}/.venv/bin:$PATH {{ justfile_directory() }}/bin/build-translated-result.sh {{ language }}
+
+# Builds the translated result for all published languages into the `translations/` directory
+build-for-all-published-languages:
+    #!/bin/sh
+    cat {{ justfile_directory() }}/PUBLISHED_LANGUAGES | while read language ; do
+        {{ just_executable() }} build-for-language $language
+    done
+
+# Builds the translated result for all known languages into the `translations/` directory
+build-for-all-known-languages:
+    #!/bin/sh
+    find {{ justfile_directory() }}/locales -mindepth 1 -maxdepth 1 -type d | while read path ; do
+        language=$(basename "$path")
+        echo "Building for language $language…"
+        {{ just_executable() }} build-for-language $language
+    done
+
+# Creates the virtual environment and installs the required Python packages
+_venv:
+    #!/bin/sh
+    if [ ! -f {{ justfile_directory() }}/.venv/bin/sphinx-build ]; then
+        echo "No sphinx-build found, creating virtual environment and installing requirements…"
+        uv venv {{ justfile_directory() }}/.venv
+        VIRTUAL_ENV={{ justfile_directory() }}/.venv uv pip install -r {{ justfile_directory() }}/requirements.txt
+    fi
diff --git a/i18n/locales/bg/LC_MESSAGES/CHANGELOG.po b/i18n/locales/bg/LC_MESSAGES/CHANGELOG.po
new file mode 100644
index 000000000..a6080952c
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/CHANGELOG.po
@@ -0,0 +1,6962 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-22 17:53+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../CHANGELOG.md:1
+msgid "2024-11-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3
+msgid "(Backward Compatibility Break) Synapse now defaults to enabling authenticated media"
+msgstr ""
+
+#: ../../../CHANGELOG.md:5
+msgid "**TLDR**: with this update, your Synapse homeserver will start requiring authentication for newly-uploaded media files. While the majority of the ecosystem (clients, bots, etc.) should support this, certain software may lack support for it (and you may wish to turn it off, if it's causing issues)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:7
+msgid "The default configuration for the Synapse homeserver now [enforces Authenticated media by default](https://element-hq.github.io/synapse/v1.120/upgrade.html#authenticated-media-is-now-enforced-by-default)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:9
+msgid "Servers like `matrix.org` have already [sunset unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) months ago."
+msgstr ""
+
+#: ../../../CHANGELOG.md:11
+msgid "Now that **various clients, bots, bridges and extra services have caught up with authenticated media support**, Synapse developers seem confident that it's time to enable authenticated media by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:13
+msgid "We're changing the playbook configuration for authenticated media to keep up with upstream defaults changing."
+msgstr ""
+
+#: ../../../CHANGELOG.md:15
+msgid "Old and unmaintained bridges (like all mx-puppet bridges, etc.) do not support authenticated media. Other software may be similarly affected. If you experience issues with some Matrix-related software, you may wish to disable authenticated media and contact the software maintainers to let them know."
+msgstr ""
+
+#: ../../../CHANGELOG.md:17
+msgid "You can disable authenticated media at any time by setting `matrix_synapse_enable_authenticated_media: false` in your `vars.yml` configuration file and re-running the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:20
+msgid "2024-11-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:22
+msgid "(Backward Compatibility Break) The playbook now defaults to Valkey, instead of KeyDB"
+msgstr ""
+
+#: ../../../CHANGELOG.md:24
+msgid "**TLDR**: if the playbook installed KeyDB (or Redis) as a dependency for you before, it will now replace it with [Valkey](https://valkey.io/) (a drop-in alternative). We [previously switched from Redis to KeyDB](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis), but Valkey is a better alternative, so we're switching again."
+msgstr ""
+
+#: ../../../CHANGELOG.md:26
+msgid "The playbook used to install Redis or KeyDB if services have a need for a Redis-compatible implementation ([enabling worker support for Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-workers), [enabling Hookshot encryption](docs/configuring-playbook-bridge-hookshot.md#end-to-bridge-encryption), etc.)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:28
+msgid "Earlier this year, we switched from Redis to KeyDB - see [(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:30
+msgid "Because Valkey seems to be a better successor to Redis (than KeyDB) and likely doesn't suffer from [issues like this one](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3544), we now replace KeyDB with Valkey."
+msgstr ""
+
+#: ../../../CHANGELOG.md:32
+msgid "Valkey (like KeyDB and Redis in the past) is an implicitly enabled dependency - you don't need custom configuration in `vars.yml` to enable it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:34
+msgid "Next time your run the playbook (via the `setup-all` tag), **KeyDB will be automatically uninstalled and replaced with Valkey**. Some Synapse downtime may occur while the switch happens."
+msgstr ""
+
+#: ../../../CHANGELOG.md:36
+msgid "Users on `arm32` should be aware that there's **neither a prebuilt `arm32` container image for Valkey**, nor the Valkey role supports self-building yet. Users on this architecture likely don't run Synapse with workers, etc., so they're likely in no need of Valkey (or Redis/KeyDB). If Redis is necessary in an `arm32` deployment, disabling Valkey and making the playbook fall back to Redis is possible (see below)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:38 ../../../CHANGELOG.md:378
+msgid "**The playbook still supports Redis** and you can keep using Redis (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:49
+msgid "**The playbook still supports KeyDB** and you can keep using KeyDB (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:59
+msgid "At some point in time in the future, we'll remove both KeyDB and Redis from the playbook, so we recommend that you migrate to Valkey earlier anyway."
+msgstr ""
+
+#: ../../../CHANGELOG.md:62
+msgid "2024-11-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:64
+msgid "HTTP-compression support for Traefik-based setups"
+msgstr ""
+
+#: ../../../CHANGELOG.md:66
+msgid "The playbook now **automatically enables HTTP-compression support** for major services powered by the playbook, like [Cinny](./docs/configuring-playbook-client-cinny.md), [Element Web](./docs/configuring-playbook-client-element-web.md), [Hydrogen](./docs/configuring-playbook-client-hydrogen.md), as well as for Matrix Client-Server and Federation APIs (`matrix.example.com`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:68
+msgid "Other services installed by the playbook are currently not compression-enabled, but may become so over time. This change is rolled out on a per-service basis (as opposed to doing it globally, at the Traefik entrypoint level) to allow certain services or route endpoints which do not behave well when compressed (e.g. [issue 3749](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3749)) to be excluded from compression."
+msgstr ""
+
+#: ../../../CHANGELOG.md:70
+msgid "A long time ago, various services were operating with `gzip`-compression enabled at the nginx level. Since the switch to Traefik (see [Goodbye, `matrix-nginx-proxy` 🪦](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/57c5271d9d6265a34a9d9cceb93365f685074f96/CHANGELOG.md#goodbye-matrix-nginx-proxy-)), all services (with the exception of Matrix APIs for Synapse worker-enabled setups which are powered by `nginx` via `synapse-reverse-proxy-companion`) have been operating without HTTP-compression support."
+msgstr ""
+
+#: ../../../CHANGELOG.md:72
+msgid "HTTP-compression is now done via Traefik's [compress](https://doc.traefik.io/traefik/middlewares/http/compress/) middleware. We use the default configuration for this middleware, which enables `zstd`, `br` and `gzip` support (in this order). This middleware's configuration can be configured via variables in the Traefik role (see `traefik_config_http_middlewares_compression_middleware_options`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:74
+msgid "If you're using your own Traefik reverse-proxy server ([Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)) instead of the playbook's integrated Traefik service, you can benefit from the same by:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:76
+msgid "defining a [compress](https://doc.traefik.io/traefik/middlewares/http/compress/) middleware (via the [file](https://doc.traefik.io/traefik/providers/file/) or [Docker](https://doc.traefik.io/traefik/providers/docker/) providers)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:77
+msgid "setting `matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled` to `true`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:78
+msgid "specifying the middleware's name in `matrix_playbook_reverse_proxy_traefik_middleware_compression_name` (e.g. `matrix_playbook_reverse_proxy_traefik_middleware_compression_name: my-compression-middleware@file`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:80
+msgid "Timeout adjustments for Traefik-based setups"
+msgstr ""
+
+#: ../../../CHANGELOG.md:82
+msgid "The playbook now supports configuring various [transport.respondingTimeouts](https://doc.traefik.io/traefik/routing/entrypoints/#respondingtimeouts) timeout values (`readTimeout`, `writeTimeout`, `idleTimeout`) for the `web`, `web-secure` and `matrix-federation` entrypoints."
+msgstr ""
+
+#: ../../../CHANGELOG.md:84
+msgid "If you're using your own Traefik reverse-proxy server ([Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)) instead of the playbook's integrated Traefik service, you may wish to do similar configuration changes to your setup manually."
+msgstr ""
+
+#: ../../../CHANGELOG.md:86
+msgid "The most interesting of these is the `readTimeout` configuration value (the maximum duration for reading the entire request, including the body), which used to default to `60s`. For large and slowly progressing file uploads, `60s` would often not be enough for the transfer to finish and uploads would end up being interrupted. The playbook now raises the `readTimeout` value to 5 minutes (`300s`) to improve this use-case."
+msgstr ""
+
+#: ../../../CHANGELOG.md:88
+msgid "The `traefik_config_entrypoint_web_transport_respondingTimeouts_*` variables (for the `web` entrypoint) cascade to affecting the timeout values for the `web-secure` and `matrix-federation` entrypoints, so you can easily adjust all timeout values using them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:90
+msgid "Example of the default timeout values used by the playbook:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:101
+msgid "Alternatively, you may adjust the timeout values for specific entrypoints (like `web-secure` and `matrix-federation`) using dedicated variables (like `traefik_config_entrypoint_web_secure_transport_respondingTimeouts_readTimeout` and `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_readTimeout`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:104
+msgid "2024-11-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:106
+msgid "Support for synapse-admin auto-configuration via /.well-known/matrix/client"
+msgstr ""
+
+#: ../../../CHANGELOG.md:108
+msgid "You can administrate your Synapse-powered homeserver using synapse-admin hosted externally (e.g. [admin.etke.cc](https://admin.etke.cc/)) and the synapse-admin instance would still auto-configure itself correctly for your server by [reading its `/.well-known/matrix/client` file](https://github.com/etkecc/synapse-admin/pull/126)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:110
+msgid "The playbook now configures the `/.well-known/matrix/client` file for this by default, injecting into it a `cc.etke.synapse-admin` section that contains the full synapse-admin configuration. This is done even if you don't enable the synapse-admin service in your configuration. The reason for always doing it is to allow users to skip the (small) overhead of self-hosting the non-core synapse-admin service, yet still be able to use it from elsewhere when needed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:112
+msgid "If you don't ever plan on using synapse-admin from other servers (besides your own due to [self-hosting synapse-admin](./docs/configuring-playbook-synapse-admin.md)), you **can disable this** `/.well-known/matrix/client` configuration via `matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_enabled: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:115
+msgid "2024-10-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:117
+msgid "(BC Break) Postmoogle's variable names need adjustments"
+msgstr ""
+
+#: ../../../CHANGELOG.md:119
+msgid "Due to the recategorization of [Postmoogle](./docs/configuring-playbook-bridge-postmoogle.md) from the bot to the bridge, its variables were renamed (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`). You need to adjust your `vars.yml` configuration accordingly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:121
+msgid "2024-10-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:123
+msgid "Support for Matrix Authentication Service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:125
+msgid "The playbook now supports installing and configuring [Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) (MAS)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:127
+msgid "Huge thanks to [Quentin Gliech](https://github.com/sandhose) from the [Element](https://element.io/) / [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service) team for answering our numerous questions about MAS."
+msgstr ""
+
+#: ../../../CHANGELOG.md:129
+msgid "This is an **experimental service** and there are **still certain issues with it** (see [Expectations](./docs/configuring-playbook-matrix-authentication-service.md#expectations)). Matrix server administrators should only consider switching if they identify with one or more [reasons to use Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md#reasons-to-use-matrix-authentication-service). As MAS adoption improves and more services are adjusted to support it, we expect that using MAS will become the norm."
+msgstr ""
+
+#: ../../../CHANGELOG.md:131
+msgid "Our [Setting up Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) documentation page has more details about this new service, what you might expect from the switch and how you can migrate your existing (Synapse) homeserver setup to MAS."
+msgstr ""
+
+#: ../../../CHANGELOG.md:134
+msgid "2024-09-27"
+msgstr ""
+
+#: ../../../CHANGELOG.md:136
+msgid "(BC Break) Postgres & Traefik roles have been relocated and variable names need adjustments"
+msgstr ""
+
+#: ../../../CHANGELOG.md:138
+msgid "Various roles have been relocated from the [devture](https://github.com/devture) organization to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization."
+msgstr ""
+
+#: ../../../CHANGELOG.md:140
+msgid "Along with the relocation, the `devture_` prefix was dropped from their variable names, so you need to adjust your `vars.yml` configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:142
+msgid "You need to do the following replacements:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:144
+msgid "`devture_postgres_` -> `postgres_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:145
+msgid "`devture_traefik_` -> `traefik_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:147
+msgid "As always, the playbook would let you know about this and point out any variables you may have missed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:150
+msgid "2024-09-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:152
+msgid "Support for baibot"
+msgstr ""
+
+#: ../../../CHANGELOG.md:154
+msgid "The playbook now supports installing [baibot](./docs/configuring-playbook-bot-baibot.md) (pronounced bye-bot) - a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖"
+msgstr ""
+
+#: ../../../CHANGELOG.md:156
+msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as well as many other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:158
+msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to the now-unmaintained [matrix-chatgpt-bot](./docs/configuring-playbook-bot-chatgpt.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:160
+msgid "To get started, see the [Setting up baibot](./docs/configuring-playbook-bot-baibot.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:162
+msgid "Switching synapse-admin to etke.cc's fork"
+msgstr ""
+
+#: ../../../CHANGELOG.md:164
+msgid "The playbook now installs [etke.cc](https://etke.cc/)'s [fork](https://github.com/etkecc/synapse-admin) of [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin) (originally developed by [Awesome-Technologies](https://github.com/Awesome-Technologies)). This fork is a drop-in replacement for the original software."
+msgstr ""
+
+#: ../../../CHANGELOG.md:166
+msgid "The creation of the fork has been provoked by users frequently encountering issues with the original synapse-admin software, such as unintentionally deleting their one-and-only admin user account (fixed [here](https://github.com/etkecc/synapse-admin/pull/1) and also contributed upstream [here](https://github.com/Awesome-Technologies/synapse-admin/pull/608) - to no avail for now). Since its inception, [a bunch of other quality-of-life improvements](https://github.com/etkecc/synapse-admin?tab=readme-ov-file#changes) have been made to the fork."
+msgstr ""
+
+#: ../../../CHANGELOG.md:168
+msgid "If upstream synapse-admin picks up the pace and improves, the etke.cc fork may disappear and the playbook may switch to the original software again. Until that time comes, we believe that etke.cc's fork is the better software to use right now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:170
+msgid "If you'd like to switch back to the original synapse-admin software, you can do so by adding the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:183
+msgid "2024-08-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:185
+msgid "New appservice-double-puppet service for better double-puppeting"
+msgstr ""
+
+#: ../../../CHANGELOG.md:187
+msgid "Mautrix bridges are undergoing large changes as announced in the [August 2024 releases & progress](https://mau.fi/blog/2024-08-mautrix-release/) blog post."
+msgstr ""
+
+#: ../../../CHANGELOG.md:189
+msgid "The playbook has already upgraded to the rewritten mautrix-slack ([v0.1.0](https://github.com/mautrix/slack/releases/tag/v0.1.0)) and mautrix-signal ([v0.7.0](https://github.com/mautrix/signal/releases/tag/v0.7.0)) bridges."
+msgstr ""
+
+#: ../../../CHANGELOG.md:191
+msgid "The newly rewritten bridges do not support double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) anymore, which has prompted us to switch to the new & better [appservice method](https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new) for double-puppeting. The playbook automates this double-puppeting setup for you if you enable the new [Appservice Double Puppet](./docs/configuring-playbook-appservice-double-puppet.md) service."
+msgstr ""
+
+#: ../../../CHANGELOG.md:193
+msgid "All non-deprecated mautrix bridges in the playbook have been reworked to support double-puppeting via an Appservice. Most bridges still support double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md), so the playbook supports it too. If only Shared Secret Auth is enabled, double-puppeting will be configured using that method (for the bridges that support it). That said, **Shared Secret Auth double-puppeting is being phased out and we recommend replacing it with the new Appservice method**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:195
+msgid "We recommend **enabling double-puppeting via the new Appservice method** by adding the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:201
+msgid "You can still **keep** [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) enabled. Non-mautrix bridges and other services (e.g. [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) may still require it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:203
+msgid "When both double-puppeting methods are enabled, the playbook will automatically choose the new and better Appservice method for bridges that support it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:206
+msgid "2024-08-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:208
+msgid "matrix-media-repo now configured for Authenticated Media"
+msgstr ""
+
+#: ../../../CHANGELOG.md:210
+msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), our matrix-media-repo implementation now automatically [sets up signing keys](https://docs.t2bot.io/matrix-media-repo/v1.3.5/installation/signing-key/) for Authenticated Media (as per [MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:212
+msgid "If you had never heard of Authenticated Media before, the [Sunsetting unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) article on [matrix.org](https://matrix.org/) is a good introduction."
+msgstr ""
+
+#: ../../../CHANGELOG.md:214
+msgid "This feature is enabled for matrix-media-repo installations by default and will append an additional (matrix-media-repo-generated signing key) to your homeserver's (Synapse or Dendrite) signing key. See the [Signing keys](./docs/configuring-playbook-matrix-media-repo.md#signing-keys) and [Key backup and revoking](./docs/configuring-playbook-matrix-media-repo.md#key-backup-and-revoking) sections of the matrix-media-repo documentation for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:216
+msgid "If you'd like to avoid this new feature, you can disable it by setting `matrix_media_repo_generate_signing_key: false` in your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:219
+msgid "2024-08-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:221
+msgid "(Backward Compatibility Break) matrix-corporal has been upgraded to v3"
+msgstr ""
+
+#: ../../../CHANGELOG.md:223
+msgid "The playbook now installs [matrix-corporal](https://github.com/devture/matrix-corporal) v3.0.0, which brings support for **power-level management** (thanks to [this PR](https://github.com/devture/matrix-corporal/pull/32))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:225
+msgid "This upgrade necessitates configuration policy changes as described in [matrix-corporal's changelog entry](https://github.com/devture/matrix-corporal/blob/5287cb81c82cd3b951c2a099b4697c3e0b384559/CHANGELOG.md#version-300-2024-08-08)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:227
+msgid "If you'd like to remain on the old (v2) version of matrix-corporal, you can do so by adding the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:233
+msgid "2024-07-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:235
+msgid "synapse-usage-exporter support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:237
+msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) - a small [Flask](https://flask.palletsprojects.com)-based webservice which can capture usage statistics from Synapse (via HTTP `PUT`) and then make them available for Prometheus to scrape."
+msgstr ""
+
+#: ../../../CHANGELOG.md:239
+msgid "To learn more see our [Enabling synapse-usage-exporter for Synapse usage statistics](docs/configuring-playbook-synapse-usage-exporter.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:242
+msgid "2024-07-06"
+msgstr ""
+
+#: ../../../CHANGELOG.md:244
+msgid "matrix-alertmanager-receiver support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:246
+msgid "For those wishing to more easily integrate [Prometheus](https://prometheus.io/)' alerting service ([Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/)) with Matrix, the playbook can now set up [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:248
+msgid "See [Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](./docs/configuring-playbook-alertmanager-receiver.md) for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:250
+msgid "Traefik v3 and HTTP/3 are here now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:252
+msgid "**TLDR**: Traefik was migrated from v2 to v3. Minor changes were done to the playbook. Mostly everything else worked out of the box. Most people will not have to do any tweaks to their configuration. In addition, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is now auto-enabled for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints. If you have a firewall in front of your server and you wish to benefit from `HTTP3`, you will need to open the `443` and `8448` UDP ports in it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:254
+msgid "Traefik v3"
+msgstr ""
+
+#: ../../../CHANGELOG.md:256
+msgid "The reverse-proxy that the playbook uses by default (Traefik) has recently been upgraded to v3 (see [this blog post](https://traefik.io/blog/announcing-traefik-proxy-v3-rc/) to learn about its new features). Version 3 includes some small breaking configuration changes requiring a [migration](https://doc.traefik.io/traefik/migration/v2-to-v3/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:258
+msgid "We have **updated the playbook to Traefik v3** (make sure to run `just roles` / `make roles` to get it)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:260
+msgid "There were **only minor playbook changes required** to adapt to Traefik v3, and only to the Ansible role for [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) where we changed a few [`PathPrefix` instances to `PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-pathprefix-and-pathregexp), because these instances were using a regular expression instead of a fixed path. For fixed-path values, `PathPrefix` is still the preferred matcher function to use."
+msgstr ""
+
+#: ../../../CHANGELOG.md:262
+msgid "**Most people using the playbook should not have to do any changes**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:264
+msgid "If you're using the playbook's Traefik instance to reverse-proxy to some other services of your own (not managed by the playbook), you may wish to review their Traefik labels and make sure they're in line with the [Traefik v2 to v3 migration guide](https://doc.traefik.io/traefik/migration/v2-to-v3/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:266
+msgid "If you've tweaked any of this playbook's `_path_prefix` variables and made them use a regular expression, you will now need to make additional adjustments. The playbook makes extensive use of `PathPrefix()` matchers in Traefik rules and `PathPrefix` does not support regular expressions anymore. To work around it, you may now need to override a whole `_traefik_rule` variable and switch it from [`PathPrefix` to `PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-pathprefix-and-pathregexp)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:268
+msgid "If you're not using [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) (the only role we had to tweak to adapt it to Traefik v3), you **may potentially downgrade to Traefik v2** (if necessary) by adding `traefik_verison: v2.11.4` to your configuration. People using `matrix-media-repo` cannot downgrade this way, because `matrix-media-repo` has been adjusted to use `PathRegexp` - a [routing matcher](https://doc.traefik.io/traefik/v2.11/routing/routers/#rule) that Traefik v2 does not understand."
+msgstr ""
+
+#: ../../../CHANGELOG.md:270
+msgid "HTTP/3 is enabled by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:272
+msgid "In Traefik v3, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is no longer considered experimental now. Due to this, **the playbook auto-enables HTTP3** for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints."
+msgstr ""
+
+#: ../../../CHANGELOG.md:274
+msgid "HTTP3 uses the UDP protocol and **the playbook (together with Docker) will make sure that the appropriate ports** (`443` over UDP & `8448` over UDP) **are exposed and whitelisted in your server's firewall**. However, **if you have another firewall in front of your server** (as is the case for many cloud providers), **you will need to manually open these UDP ports**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:276
+msgid "If you do not open the UDP ports correctly or there is some other issue, clients (browsers, mostly) will fall-back to [HTTP/2](https://en.wikipedia.org/wiki/HTTP/2) or even [HTTP/1.1](https://en.wikipedia.org/wiki/HTTP)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:278
+msgid "Still, if HTTP/3 cannot function correctly in your setup, it's best to disable advertising support for it (and misleading clients into trying to use HTTP/3)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:280
+msgid "To **disable HTTP/3**, you can use the following configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:294
+msgid "If you are using [your own webserver](./docs/configuring-playbook-own-webserver.md) (in front of Traefik), port binding on UDP port `8448` by default due to HTTP/3 is either unnecessary or [may get in the way](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3402). If it does, you can disable it:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:307
+msgid "2024-07-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:309
+msgid "synapse-admin is now restricted to your homeserver's URL by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:311
+msgid "A new feature introduced in synapse-admin [v0.10.0](https://github.com/Awesome-Technologies/synapse-admin/releases/tag/0.10.0) (released and supported by the playbook since a a few months ago) provides the ability to [restrict its usage to a specific homeserver](https://github.com/Awesome-Technologies/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) (or multiple homeservers)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:313
+msgid "The playbook has just started making use of this feature. **From now on, your synapse-admin instance will be restricted to the homeserver you're managing via the playbook**. When configured like this, the *Homeserver URL* field in synapse-admin's web UI changes from a text field to a dropdown having a single value (the URL of your homeserver). This makes usage simpler for most people, as they won't need to manually enter a *Homeserver URL* anymore."
+msgstr ""
+
+#: ../../../CHANGELOG.md:315
+msgid "If you'd like **to go back to the old unrestricted behavior**, use the following configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:323
+msgid "2024-06-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:325
+msgid "The URL-prefix for Hookshot generic webhooks has changed"
+msgstr ""
+
+#: ../../../CHANGELOG.md:327
+msgid "Until now, generic Hookshot webhook URLs looked like this: `https://matrix.example.com/hookshot/webhooks/:hookId`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:329
+msgid "The `/hookshot/webhooks` common prefix gets stripped by Traefik automatically, so Hookshot only sees the part that comes after (`/:hookId`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:331
+msgid "[A few years ago](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1681), Hookshot started to prefer to handle webhooks at a `/webhook/:hookId` path (instead of directly at `/:hookId`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:333
+msgid "To avoid future problems, we've [reconfigured](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/4704a60718946fd469aeee7fc3ae8127c633bb6b) our Hookshot configuration to use webhook URLs that include `/webhook` in the URL suffix (e.g. `/hookshot/webhooks/webhook/:hookId`, instead of `/hookshot/webhooks/:hookId`). This means that when we strip the common prefi (`/hookshot/webhooks`), we'll end up sending `/webhook/:hookId` to Hookshot, just like recommended."
+msgstr ""
+
+#: ../../../CHANGELOG.md:335
+msgid "When generating new webhooks, you should start seeing the new URLs being used."
+msgstr ""
+
+#: ../../../CHANGELOG.md:337
+msgid "**For now**, **both** old URLs (`/hookshot/webhooks/:hookId`) and new URLs (`/hookshot/webhooks/webhook/:hookId`) **continue to work**, so your webhooks will not break just yet."
+msgstr ""
+
+#: ../../../CHANGELOG.md:339
+msgid "However, **we recommend that you update all your old webhook URLs** (configured in other systems) to include the new `/webhook` path component, so that future Hookshot changes (whenever they come) will not break your webhooks. You don't need to do anything on the Hookshot side - you merely need to reconfigure the remote systems that use your webhook URLs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:342
+msgid "2024-06-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:344
+msgid "The maubot user is now managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:346
+msgid "To make things easier and to be consistent with other roles, the [maubot](./docs/configuring-playbook-bot-maubot.md) user (`bot.maubot` by default) is [now](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3376) automatically created be the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:348
+msgid "If you have an existing maubot installation, you will need to specify `matrix_bot_maubot_initial_password` in your `vars.yml` file to make the playbook not complain about it being undefined. Since the bot is already registered in your installation, there's nothing for the playbook to do anyway. In case you don't remember the password you've registered your maubot user account with, you can specify any value for this variable."
+msgstr ""
+
+#: ../../../CHANGELOG.md:350
+msgid "If you've registered another username for the bot (other than the recommended default of `bot.maubot`), consider adjusting the `matrix_bot_maubot_login` variable (e.g. `matrix_bot_maubot_login: my.maubot.username`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:353
+msgid "2024-06-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:355
+msgid "WeChat bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:357
+msgid "Thanks to [Tobias Diez](https://github.com/tobiasdiez)'s [efforts](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3241), the playbook now supports bridging to [WeChat](https://www.wechat.com/) via the [matrix-wechat](https://github.com/duo/matrix-wechat) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:359
+msgid "See our [Setting up WeChat bridging](docs/configuring-playbook-bridge-wechat.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:362
+msgid "2024-03-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:364
+msgid "(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis"
+msgstr ""
+
+#: ../../../CHANGELOG.md:366
+msgid "**TLDR**: if the playbook used installed Redis as a dependency for you before, it will now replace it with [KeyDB](https://docs.keydb.dev/) (a drop-in alternative) due to [Redis having changed its license](https://redis.com/blog/redis-adopts-dual-source-available-licensing/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:368
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now uses [KeyDB](https://docs.keydb.dev/) (a drop-in alternative for Redis), instead of [Redis](https://redis.io/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:370
+msgid "The playbook used to install Redis (and now installs KeyDB in its place) if services have a need for it ([enabling worker support for Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-workers), [enabling Hookshot encryption](docs/configuring-playbook-bridge-hookshot.md#end-to-bridge-encryption), etc.) or if you explicitly enabled the service (`redis_enabled: true` or `keydb_enabled: true`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:372
+msgid "This change is provoked by the fact that [Redis is now \"source available\"](https://redis.com/blog/redis-adopts-dual-source-available-licensing/). According to the Limitations of [the new license](https://redis.com/legal/rsalv2-agreement/) (as best as we understand them, given that we're not lawyers), using Redis in the playbook (even in a commercial FOSS service like [etke.cc](https://etke.cc/)) does not violate the new Redis license. That said, we'd rather neither risk it, nor endorse shady licenses and products that pretend to be free-software. Another high-quality alternative to Redis seems to be [Dragonfly](https://www.dragonflydb.io/), but the [Dragonfly license](https://github.com/dragonflydb/dragonfly?tab=License-1-ov-file#readme) is no better than Redis's."
+msgstr ""
+
+#: ../../../CHANGELOG.md:374
+msgid "Next time your run the playbook (via the `setup-all` tag), **Redis will be automatically uninstalled and replaced with KeyDB**. Some Synapse downtime may occur while the switch happens."
+msgstr ""
+
+#: ../../../CHANGELOG.md:376
+msgid "Users on `arm32` should be aware that there's **neither a prebuilt `arm32` container image for KeyDB**, nor the KeyDB role supports self-building yet. Users on this architecture likely don't run Synapse with workers, etc., so they're likely in no need of KeyDB (or Redis). If Redis is necessary in an `arm32` deployment, disabling KeyDB and making the playbook fall back to Redis is possible (see below)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:387
+msgid "2024-03-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:389
+msgid "Initial work on IPv6 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:391
+msgid "Thanks to [Tilo Spannagel](https://github.com/tilosp), the playbook can now enable IPv6 for container networks for various components (roles) via [the `devture_systemd_docker_base_ipv6_enabled` variable](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L14-L31)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:393
+msgid "It should be noted that:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:395
+msgid "Matrix roles (`roles/custom/matrix-*`) respect this variable, but external roles (those defined in `requirements.yml` and installed via `just roles`) do not respect it yet. Additional work is necessary"
+msgstr ""
+
+#: ../../../CHANGELOG.md:396
+msgid "changing the variable subsequently may not change existing container networks. Refer to [these instructions](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L26-L30)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:397
+msgid "this is all very new and untested"
+msgstr ""
+
+#: ../../../CHANGELOG.md:399
+msgid "Pantalaimon support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:401
+msgid "Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the playbook can now install the [Pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you. It's already possible to integrate it with [Draupnir](docs/configuring-playbook-bot-draupnir.md) to allow it to work in E2EE rooms - see our Draupnir docs for details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:403
+msgid "See our [Setting up Pantalaimon](docs/configuring-playbook-pantalaimon.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:406
+msgid "2024-03-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:408
+msgid "Support for Draupnir-for-all"
+msgstr ""
+
+#: ../../../CHANGELOG.md:410
+msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now install [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) (aka multi-instance Draupnir running in appservice mode)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:412
+msgid "This is an alternative to [running Draupnir in bot mode](./docs/configuring-playbook-bot-draupnir.md), which is still supported by the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:414
+msgid "The documentation page for [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) contains more information on how to install it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:417
+msgid "2024-02-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:419
+msgid "Support for bridging to Facebook/Messenger via the new mautrix-meta bridge"
+msgstr ""
+
+#: ../../../CHANGELOG.md:421
+msgid "The [mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-facebook.md) and [mautrix-instagram](./docs/configuring-playbook-bridge-mautrix-instagram.md) bridges are being [superseded by a new bridge](https://github.com/mautrix/facebook/issues/332) - the [mautrix-meta](https://github.com/mautrix/meta) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:423
+msgid "The playbook now supports the new mautrix-meta bridge - a single bridge, which can run in different modes and bridge to Messenger (via [Facebook](https://facebook.com/), Facebook over [Tor](https://www.torproject.org/) or via [Messenger](https://messenger.com/)) and [Instagram](https://instagram.com/). The playbook makes this bridge available via 2 separate Ansible roles, allowing you to easily run 2 instances of mautrix-meta, for bridging to both services at the same time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:425
+msgid "If you're using mautrix-facebook or mautrix-instagram right now, **you can still continue using the old bridges, but may wish to change to the new bridge implementations**. See:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:427
+msgid "[Setting up Instagram bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:429
+msgid "[Setting up Messenger bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-messenger.md)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:431
+msgid "The documentation pages contain more information on how to migrate."
+msgstr ""
+
+#: ../../../CHANGELOG.md:434
+msgid "2024-02-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:436
+msgid "Much larger Synapse caches and cache auto-tuning enabled by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:438
+msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook now uses much larger caches and enables Synapse's [cache auto-tuning functionality](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values). This work and the default values used by the playbook are inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/deployment/synapse.html)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:440
+msgid "The playbook has always used a very conservative cache factor (`matrix_synapse_caches_global_factor`) value of `0.5`, which may be OK for small and underactive deployments, but is not ideal for larger servers. Paradoxically, a small global cache factor value [does not necessarily decrease RAM usage as a whole](https://github.com/matrix-org/synapse/issues/3939)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:442
+msgid "The playbook now uses **a 20x larger cache factor** (currently `10`), adjusts a few other cache-related variables, and **enables cache auto-tuning** via the following variables:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:444
+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 ""
+
+#: ../../../CHANGELOG.md:445
+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 ""
+
+#: ../../../CHANGELOG.md:446
+msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:448
+msgid "These values should be good defaults for most servers, but may change over time as we experiment further."
+msgstr ""
+
+#: ../../../CHANGELOG.md:450
+msgid "Refer to our new [Tuning caches and cache autotuning](docs/maintenance-synapse.md#tuning-caches-and-cache-autotuning) documentation section for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:453
+msgid "2024-01-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:455
+msgid "(Backward-compatibility break) Minor changes necessary for some people serving a static website at the base domain"
+msgstr ""
+
+#: ../../../CHANGELOG.md:457
+msgid "This only affects people who are [Serving a static website at the base domain](./docs/configuring-playbook-base-domain-serving.md#serving-a-static-website-at-the-base-domain), but not managing its `index.html` through the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:459
+msgid "That is, for people who have `matrix_static_files_file_index_html_enabled: false` in their `vars.yml` configuration, the playbook has a new default behavior. Since the playbook is not managing the `index.html` file, it will default to a more sensible way of handling the base domain  - redirecting `https://example.com/` to `https://matrix.example.com/`, instead of serving a 404 page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:461
+msgid "If you are managing your static website by yourself (by dropping files into `/matrix/static-files/public` somehow), then you probably don't wish for such redirection to happen. You can disable it by adding `matrix_static_files_container_labels_base_domain_root_path_redirection_enabled: false` to your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:464
+msgid "2024-01-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:466
+msgid "Support for more efficient (specialized) Synapse workers"
+msgstr ""
+
+#: ../../../CHANGELOG.md:468
+msgid "Thanks to [Charles Wright](https://github.com/cvwright) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook has [received support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3100) for load-balancing the Synapse workload via [specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) which are supposed to work better than our old [generic workers](./docs/configuring-playbook-synapse.md#generic-workers) implementation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:470
+msgid "For now, playbook defaults remain unchanged and the `one-of-each` [workers preset](./docs/configuring-playbook-synapse.md#worker-presets) continues being the default. However, the default may change in the future. If you'd like to remain on this preset even if/when the defaults change, consider explicitly adding `matrix_synapse_workers_preset: one-of-each` to your `vars.yml` configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:472
+msgid "Our specialized workers setup is based on recommendations found in [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). What's special about our new setup is that we try to parse information out of the request (who the user is; which room is being operated on) and try to forward similar requests to the same worker. As an example, this means that once a worker caches some room information, subsequent requests for the same room will be routed to the same worker (which supposedly still has the room's state cached)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:474
+msgid "To get started, refer to our [Specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) documentation section."
+msgstr ""
+
+#: ../../../CHANGELOG.md:477
+msgid "2024-01-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:479
+msgid "Switching to Element's AGPLv3-licensed Synapse release"
+msgstr ""
+
+#: ../../../CHANGELOG.md:481
+msgid "A few months ago, the [Element](https://element.io/) company has [announced](https://element.io/blog/element-to-adopt-agplv3/) that their work on the Synapse homeserver would no longer be available under the permissive [Apache-2.0 license](https://www.apache.org/licenses/LICENSE-2.0), but only under:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:483
+msgid "the [AGPLv3](https://www.gnu.org/licenses/agpl-3.0.en.html) free-software license - the same license that this Ansible playbook has always used"
+msgstr ""
+
+#: ../../../CHANGELOG.md:484
+msgid "a proprietary license, for those wishing for Element to [sell them an exception](https://gnu.org/philosophy/selling-exceptions.html) to the AGPLv3 license"
+msgstr ""
+
+#: ../../../CHANGELOG.md:486
+msgid "You can also learn more in [this post](https://matrix.org/blog/2023/11/06/future-of-synapse-dendrite/) by the Matrix Foundation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:488
+msgid "The change has [already happened](https://element.io/blog/synapse-now-lives-at-github-com-element-hq-synapse/) and the first Synapse release under the new license is here: [v1.99.0](https://github.com/element-hq/synapse/releases/tag/v1.99.0)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:490
+msgid "There is no up-to-date alternative Synapse fork right now and this free-software (AGPLv3-licensed) playbook is definitely not against free-software licenses, so we are now switching to the Element-maintained Synapse release."
+msgstr ""
+
+#: ../../../CHANGELOG.md:492
+msgid "**What does this mean to you?**"
+msgstr ""
+
+#: ../../../CHANGELOG.md:494
+msgid "For most home users, it doesn't mean anything. Your installation will continue working as it should and you don't need to do anything."
+msgstr ""
+
+#: ../../../CHANGELOG.md:496
+msgid "For people building commercial products on top of Synapse, they may have to either buy a license exception from Element (from what we hear, the fee depends on the number of monthly-active users on your instance) or they may need to release all related code as free-software (which is what we've been doing at [etke.cc](https://etke.cc/) ([here](https://gitlab.com/etke.cc)) all along)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:498
+msgid "We're no lawyers and this changelog entry does not aim to give you the best legal advice, so please research on your own!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:500
+msgid "If you'd like to continue using the old Apache-2.0-licensed Synapse (for a while longer anyway), the playbook makes it possible by intruducing a new Ansible variable. You can do it like this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:512
+msgid "Notes:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:514
+msgid "if you had already upgraded Synapse to `v1.99.0` by running this playbook, you will still be able to downgrade to `v1.98.0`, because both releases use the same database schema version (`SCHEMA_COMPAT_VERSION = 83` - see [here for v1.98.0](https://github.com/element-hq/synapse/blob/v1.98.0/synapse/storage/schema/__init__.py#L131-L134) and [here for v1.99.0](https://github.com/element-hq/synapse/blob/v1.99.0/synapse/storage/schema/__init__.py#L137-L140)). More details on Synapse's database schema are available [here](https://element-hq.github.io/synapse/develop/development/database_schema.html). It appears that there are no new database migrations introduced in `v1.99.0`, so going back to the older release is possible. This is not guaranteed to hold true for future Synapse releases, so if you're seeing this early-enough, consider pinning the version and organization before re-running the playbook and getting upgraded to the latest version"
+msgstr ""
+
+#: ../../../CHANGELOG.md:516
+msgid "running an outdated homeserver exposes you to security issues and incompatibilities. Only consider doing this as a short-term solution."
+msgstr ""
+
+#: ../../../CHANGELOG.md:518
+msgid "2024-01-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:520
+msgid "`Draupnir` has been relicensed to AFL-3.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:522
+msgid "As of [#204](https://github.com/the-draupnir-project/Draupnir/pull/204) Draupnir changed its licence to AFL-3.0 from the CSL licence. This change affects playbook users who could not run Draupnir under the old license restrictions. The new license is considerably less restrictive and is OSI approved. Draupnir version v1.86.0 and later are covered by this license change."
+msgstr ""
+
+#: ../../../CHANGELOG.md:524
+msgid "2024-01-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:526
+msgid "Goodbye, `matrix-nginx-proxy` 🪦"
+msgstr ""
+
+#: ../../../CHANGELOG.md:528
+msgid "**TLDR**: All traces of the `matrix-nginx-proxy` reverse-proxy component are now gone. This brought about many other internal changes (and security improvements), so setups may need minor adjustments or suffer some (temporary) breakage. People who have been on the Traefik-native setup may upgrade without much issues. Those running their own Traefik instance may need minor changes. People who have been postponing the migration away from `matrix-nginx-proxy` (for more than a year already!) will now finally need to do something about it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:530
+msgid "Backstory on `matrix-nginx-proxy`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:532
+msgid "We gather here today to celebrate the loss of a once-beloved component in our stack - `matrix-nginx-proxy`. It's been our [nginx](https://nginx.org/)-based reverse-proxy of choice since the [first commit](https://github.com/spantaleev/matrix-docker-ansible-deploy/tree/87f5883f2455fb115457b65f267f17de305c053c) of this playbook, 7 years ago."
+msgstr ""
+
+#: ../../../CHANGELOG.md:534
+msgid "For 6 years, `matrix-nginx-proxy` has been the front-most reverse-proxy in our setup (doing SSL termination, etc.). After [transitioning to Traefik last year](#traefik-is-the-default-reverse-proxy-now), `matrix-nginx-proxy` took a step back. Nevertheless, since it was so ingrained into the playbook, it still remained in use - even if only internally. Despite our warnings of its imminent death, many of you have indubitably continued to use it instead of Traefik. Its suffering continued for too long, because it served many different purposes and massive effort was required to transition them to others."
+msgstr ""
+
+#: ../../../CHANGELOG.md:536
+msgid "To us, `matrix-nginx-proxy` was:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:538
+msgid "an [nginx](https://nginx.org/)-based reverse-proxy"
+msgstr ""
+
+#: ../../../CHANGELOG.md:539
+msgid "an Ansible role organizing the work of [certbot](https://certbot.eff.org/) - retrieving free [Let's Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-proxy` and for the [Coturn TURN server](./docs/configuring-playbook-turn.md)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:540
+msgid "a central component for reverse-proxying to the [long list of services](./docs/configuring-playbook.md) supported by the playbook. As such, it became a dependency that all these services had to inject themselves into during runtime"
+msgstr ""
+
+#: ../../../CHANGELOG.md:541
+msgid "an intermediary through which addons (bridges, bots) communicated with the homeserver. Going through an intermediary (instead of directly talking to the homeserver) is useful when certain components (like [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) are enabled, because it lets these services \"steal routes\" from the homeserver"
+msgstr ""
+
+#: ../../../CHANGELOG.md:542
+msgid "a webserver for serving the `/.well-known/matrix` static files (generated by the `matrix-base` role until now)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:543
+msgid "a webserver [serving your base domain](./docs/configuring-playbook-base-domain-serving.md) (and also generating the `index.html` page for it)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:544
+msgid "a central component providing global [HTTP Basic Auth](https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication) password-protection for all `/metrics` endpoints when metrics were exposed publicly for consumption from a remote Prometheus server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:546
+msgid "Talk about a jack of all trades! The [UNIX philosophy](https://en.wikipedia.org/wiki/Unix_philosophy) (and Docker container philosophy) of \"do one thing and do it well\" had been severely violated for too long."
+msgstr ""
+
+#: ../../../CHANGELOG.md:548
+msgid "On a related note, we also had a large chain of reverse-proxies in the mix. In the worst case, it was something like this: (Traefik -> `matrix-nginx-proxy:8080` -> `matrix-nginx-proxy:12080` -> `matrix-synapse-reverse-proxy-companion:8008` -> `matrix-synapse:8008`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:550
+msgid "Due to complexity and the playbook's flexibility (trying to accommodate a mix of tens of components), many layers of indirection were necessary. We do like reverse-proxies, but.. not quite enough to enjoy going through a chain of ~4 of them before reaching the target service."
+msgstr ""
+
+#: ../../../CHANGELOG.md:552
+msgid "After **a ton of work** in the last weeks (200+ commits, which changed 467 files - 8684 insertions and 8913 deletions), **we're finally saying goodbye** to `matrix-nginx-proxy`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:554
+msgid "Going Traefik-native and cutting out all middlemen"
+msgstr ""
+
+#: ../../../CHANGELOG.md:556
+msgid "In our new setup, you'll see the bare minimum number of reverse-proxies."
+msgstr ""
+
+#: ../../../CHANGELOG.md:558
+msgid "In most cases, there's only Traefik and all services being registered directly with it. When [Synapse workers](./docs/configuring-playbook-synapse.md#load-balancing-with-workers) are enabled, `matrix-synapse-reverse-proxy-companion` remains as an extra reverse-proxy that requests go through (for load-balancing to the correct Synapse worker), but in all other cases services are exposed directly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:560
+msgid "This reduces \"network\" hops (improving performance) and also decreases the number of components (containers). Each Ansible role in our setup is now independent and doesn't need to interact with other roles during runtime."
+msgstr ""
+
+#: ../../../CHANGELOG.md:562
+msgid "Traefik now has an extra job"
+msgstr ""
+
+#: ../../../CHANGELOG.md:564
+msgid "Previously, **Traefik had a single purpose** - being the main reverse-proxy. It was either front-most (terminating SSL, etc.) or you were [fronting Traefik with your own other reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy). In any case - it had this central (yet decentralized) job."
+msgstr ""
+
+#: ../../../CHANGELOG.md:566
+msgid "Now, **Traefik has one more role** - it serves as an intermediary which allows addon services (bridges, bots, etc.) to communicate with the homeserver. As mentioned above, such an intermediary service is not strictly necessary in all kinds of setups, but more complex setups (including [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) benefit from it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:568
+msgid "To perform this new role, Traefik now has a new internal [entrypoint](https://doc.traefik.io/traefik/routing/entrypoints/) called `matrix-internal-matrix-client-api`. All homeservers (Conduit, Dendrite, Synapse and even `matrix-synapse-reverse-proxy-companion`) and homeserver-related core services ([matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md), [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md) and potentially others) register their routes (using [container labels](https://docs.docker.com/config/labels-custom-metadata/)) not only on the public entrypoints (`web-secure`, `matrix-federation`), but also on this new internal entrypoint."
+msgstr ""
+
+#: ../../../CHANGELOG.md:570
+msgid "Doing so, services can contact Traefik on this entrypoint's dedicated port (the URL defaults to `http://matrix-traefik:8008`) and reach the homeserver Client-Server API as they expect. Internally, Traefik takes care of the routing to the correct service."
+msgstr ""
+
+#: ../../../CHANGELOG.md:572
+msgid "We've also considered keeping it simple and having services talk to the homeserver over the public internet (e.g. `https://matrix.example.com`) thus reusing all existing Traefik routing labels. In this scenario, performance was incredibly poor (e.g. 70 rps, instead of 1400 rps) due to TLS and networking overhead. The need for fast internal communication (via the new internal non-TLS-enabled Traefik entrypoint) is definitely there. In our benchmarks, Traefik even proved more efficient than nginx at doing this: ~1200 rps for Traefik compared to ~900 rps for nginx (out of ~1400 rps when talking to the Synapse homeserver directly)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:574
+msgid "Traefik serving this second purpose has a few downsides:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:576
+msgid "Traefik becomes a runtime dependency for all homeserver-dependant container services"
+msgstr ""
+
+#: ../../../CHANGELOG.md:577
+msgid "all homeserver-dependant services now need to be connected to the `traefik` container network, even if they don't need public internet exposure"
+msgstr ""
+
+#: ../../../CHANGELOG.md:579
+msgid "Despite these downsides (which the playbook manages automatically), we believe it's still a good compromise given the amount of complexity it eliminates and the performance benefits it yields. One alternative we've [considered](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3045#issuecomment-1867327001) was adding a new intermediary service (e.g. `matrix-homeserver-proxy` powered by nginx), but this both had much higher complexity (one more component in the mix; duplication of effort to produce nginx-compatible route definitions for it) and slightly worse performance (see above)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:581
+msgid "People running the default Traefik setup do not need to do anything to make Traefik take on this extra job. Your Traefik configuration will be updated automatically."
+msgstr ""
+
+#: ../../../CHANGELOG.md:583
+msgid "**People runnning their own Traefik reverse-proxy need to do [minor adjustments](#people-managing-their-own-traefik-instance-need-to-do-minor-changes)**, as described in the section below."
+msgstr ""
+
+#: ../../../CHANGELOG.md:585
+msgid "You may disable Traefik acting as an intermediary by explicitly setting `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_enabled` to `false`. Services would then be configured to talk to the homeserver directly, giving you a slight performance boost and a \"simpler\" Traefik setup. However, such a configuration is less tested and will cause troubles, especially if you enable more services (like `matrix-media-repo`, etc.) in the future. As such, it's not recommended."
+msgstr ""
+
+#: ../../../CHANGELOG.md:587
+msgid "People managing their own Traefik instance need to do minor changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:589
+msgid "This section is for people [managing their own Traefik instance on the Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you). Those [using Traefik managed by the playbook](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) don't need to do any changes."
+msgstr ""
+
+#: ../../../CHANGELOG.md:591
+msgid "Because [Traefik has an extra job now](#traefik-now-has-an-extra-job), you need to adapt your configuration to add the additional `matrix-internal-matrix-client-api` entrypoint and potentially configure the `matrix_playbook_reverse_proxy_container_network` variable. See the [Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you) documentation section for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:593
+msgid "People fronting Traefik with another reverse proxy need to do minor changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:595
+msgid "We've already previously mentioned that you need to do some minor [configuration changes related to `traefik_additional_entrypoints_auto`](#backward-compatibility-configuration-changes-required-for-people-fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:597
+msgid "If you don't do these changes (switching from `traefik_additional_entrypoints_auto` to multiple other variables), your Traefik setup will not automatically receive the new `matrix-internal-matrix-client-api` Traefik entrypoint and Traefik would not be able to perform [its new duty of connecting addons with the homeserver](#traefik-now-has-an-extra-job)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:599
+msgid "Supported reverse proxy types are now fewer"
+msgstr ""
+
+#: ../../../CHANGELOG.md:601
+msgid "This section is for people using a more custom reverse-proxy setup - those having `matrix_playbook_reverse_proxy_type` set to a value different than the default (`playbook-managed-traefik`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:603
+msgid "Previously, we allowed you to set `matrix_playbook_reverse_proxy_type` to 7 different values to accommodate various reverse-proxy setups."
+msgstr ""
+
+#: ../../../CHANGELOG.md:605
+msgid "The complexity of this is too high, so we only support 3 values right now:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:607
+msgid "(the default) `playbook-managed-traefik`, when you're [using Traefik managed by the playbook](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:608
+msgid "`other-traefik-container`, when you're [managing your own Traefik instance on the Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:609
+msgid "`none`, when you wish for [no reverse-proxy integration to be done at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:611
+msgid "The `none` value is not recommended and may not work adequately, due to lack of testing and [Traefik's new responsibilities](#traefik-now-has-an-extra-job) in our setup."
+msgstr ""
+
+#: ../../../CHANGELOG.md:613
+msgid "**Previous values that are now gone** (and the playbook would report them as such) are: `playbook-managed-nginx`, `other-nginx-non-container`, `other-on-same-host` and `other-on-another-host`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:615
+msgid "If you were using these values as a way to stay away from Traefik, you now have 2 options:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:617
+msgid "(recommended) [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:618
+msgid "(not recommended) [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all) and reverse-proxying to each and every service manually"
+msgstr ""
+
+#: ../../../CHANGELOG.md:620
+msgid "Container networking changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:622
+msgid "Now that `matrix-nginx-proxy` is not in the mix, it became easier to clear out some other long-overdue technical debt."
+msgstr ""
+
+#: ../../../CHANGELOG.md:624
+msgid "Since the very beginning of this playbook, all playbook services were connected to a single (shared) `matrix` container network. Later on, some additional container networks appeared, but most services (database, etc.) still remained in the `matrix` container network.  This meant that any random container in this network could try to talk (or attack) the Postgres database operating in the same `matrix` network."
+msgstr ""
+
+#: ../../../CHANGELOG.md:626
+msgid "Moving components (especially the database) into other container networks was difficult - it required changes to many other components to ensure correct connectivity."
+msgstr ""
+
+#: ../../../CHANGELOG.md:628
+msgid "All the hard work has been done now. We've added much more isolation between services by splitting them up into separate networks (`matrix-homeserver`, `matrix-addons`, `matrix-monitoring`, `matrix-exim-relay`, etc). Components are only joined to the networks they need and should (for the most part) not be able to access unrelated things."
+msgstr ""
+
+#: ../../../CHANGELOG.md:630
+msgid "Carrying out these container networking changes necessitated modifying many components, so **we're hoping not too many bugs were introduced in the process**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:632
+msgid "We've refrained from creating too many container networks (e.g. one for each component), to avoid exhausting Docker's default network pool and contaminating the container networks list too much."
+msgstr ""
+
+#: ../../../CHANGELOG.md:634
+msgid "Metrics exposure changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:636
+msgid "This section is for people who are exposing monitoring metrics publicly, to be consumed by an external Prometheus server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:638
+msgid "Previously, `matrix-nginx-proxy` was potentially password-protecting all `/metrics/*` endpoints with the same username and password (specified as plain-text in your `vars.yml` configuration file)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:640
+msgid "From now on, there are new variables for doing roughly the same - `matrix_metrics_exposure_enabled`, `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`. See the [Prometheus & Grafana](./docs/configuring-playbook-prometheus-grafana.md) docs page for details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:642
+msgid "`matrix-nginx-proxy` is not acting as a \"global guardian\" anymore. Now, each role provides its own metrics exposure and protection by registering with Traefik. Nevertheless, all roles are wired (via playbook configuration in `group_vars/matrix_servers`) to obey these new `matrix_metrics_exposure_*` variables. We've eliminated the centralization, but have kept the ease of use. Now, you can also do per-service password-protection (with different credentials), should you need to do that for some reason."
+msgstr ""
+
+#: ../../../CHANGELOG.md:644
+msgid "The playbook will tell you about all variables that you need to migrate during runtime, so rest assured - you shouldn't be able to miss anything!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:646
+msgid "Matrix static files"
+msgstr ""
+
+#: ../../../CHANGELOG.md:648
+msgid "As mentioned above, static files like `/.well-known/matrix/*` or your base domain's `index.html` file (when [serving the base domain via the Matrix server](./docs/configuring-playbook-base-domain-serving.md) was enabled) were generated by the `matrix-base` or `matrix-nginx-proxy` roles and put into a `/matrix/static-files` directory on the server. Then `matrix-nginx-proxy` was serving all these static files."
+msgstr ""
+
+#: ../../../CHANGELOG.md:650
+msgid "All of this has been extracted into a new `matrix-static-files` Ansible role that's part of the playbook. The static files generated by this new role still live at roughly the same place (`/matrix/static-files/public` directory, instead of `/matrix/static-files`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:652
+msgid "The playbook will migrate and update the `/.well-known/matrix/*` files automatically but not your own files in `nginx-proxy/data/matrix-domain/` you will need to back these up yourself otherwise they will be lost. It will also warn you about usage of old variable names, so you can adapt to the new names."
+msgstr ""
+
+#: ../../../CHANGELOG.md:654
+msgid "A note on performance"
+msgstr ""
+
+#: ../../../CHANGELOG.md:656
+msgid "Some of you have been voicing their concerns (for a long time) about Traefik being too slow and nginx being better."
+msgstr ""
+
+#: ../../../CHANGELOG.md:658
+msgid "Some online benchmarks support this by demonstrating slightly higher SSL-termination performance in favor of nginx. The upcoming Traefik v3 release is [said to](https://medium.com/beyn-technology/is-nginx-dead-is-traefik-v3-20-faster-than-traefik-v2-f28ffb7eed3e) improve Traefik's SSL performance by some 20%, but that still ends up being somewhat slower than nginx."
+msgstr ""
+
+#: ../../../CHANGELOG.md:660
+msgid "We believe that using Traefik provides way too many benefits to worry about this minor performance impairment."
+msgstr ""
+
+#: ../../../CHANGELOG.md:662
+msgid "The heaviest part of running a Matrix homeserver is all the slow and potentially inefficient things the homeserver (e.g. Synapse) is doing. These things affect performance much more than whatever reverse-proxy is in front. Your server will die the same way by joining the famously large **Matrix HQ** room, no matter which reverse-proxy you put in front."
+msgstr ""
+
+#: ../../../CHANGELOG.md:664
+msgid "Even our previously mentioned benchmarks (yielding ~1300 rps) are synthetic - hitting a useless `/_matrix/client/versions` endpoint. Real-use does much more than this."
+msgstr ""
+
+#: ../../../CHANGELOG.md:666
+msgid "If this is still not convincing enough for you and you want the best possible performance, consider [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) (thus having the slowest part - SSL termination - happen elsewhere) or [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all). The playbook will not get in your way of doing that, but these options may make your life much harder. Performance comes at a cost, after all."
+msgstr ""
+
+#: ../../../CHANGELOG.md:668
+msgid "Migration procedure"
+msgstr ""
+
+#: ../../../CHANGELOG.md:670
+msgid "The updated playbook will automatically perform some migration tasks for you:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:672
+msgid "It will stop and remove the `matrix-nginx-proxy` systemd service and container for you. This behavior cannot be disabled. It's essential that this service gets stopped, because it remaining running (and having container labels) may confuse Traefik as to where to route HTTP requests."
+msgstr ""
+
+#: ../../../CHANGELOG.md:674
+msgid "It will delete the `/matrix/nginx-proxy` directory and all files within it. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_uninstallation_enabled: false` to your `vars.yml` configuration file. Doing so will leave its data around."
+msgstr ""
+
+#: ../../../CHANGELOG.md:676
+msgid "It will delete the `/matrix/ssl` directory and all files within it. You can disable this behavior by adding `matrix_playbook_migration_matrix_ssl_uninstallation_enabled: false` to your `vars.yml` configuration file. If you have some important certificates there for some reason, take them out or temporarily disable removal of these files until you do."
+msgstr ""
+
+#: ../../../CHANGELOG.md:678
+msgid "It will tell you about all variables (`matrix_nginx_proxy_*` and many others - even from other roles) that have changed during this large nginx-elimination upgrade. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_elimination_variable_transition_checks_enabled: false` to your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:680
+msgid "It will tell you about any leftover `matrix_nginx_proxy_*` variables in your `vars.yml` file. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_leftover_variable_validation_checks_enabled: false` to your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:682
+msgid "It will tell you about any leftover `matrix_ssl_*` variables in your `vars.yml` file. You can disable this behavior by adding `matrix_playbook_migration_matrix_ssl_leftover_variable_checks_enabled: false` to your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:684
+msgid "We don't recommend changing these variables and suppressing warnings, unless you know what you're doing."
+msgstr ""
+
+#: ../../../CHANGELOG.md:686
+msgid "**Most people should just upgrade as per-normal**, bearing in mind that a lot has changed and some issues may arise. The playbook would guide you through renamed variables automatically."
+msgstr ""
+
+#: ../../../CHANGELOG.md:688
+msgid "Conclusion"
+msgstr ""
+
+#: ../../../CHANGELOG.md:690
+msgid "Thousands of lines of code were changed across hundreds of files. All addons (bridges, bots) were rewired in terms of container networking and in terms of how they reach the homeserver."
+msgstr ""
+
+#: ../../../CHANGELOG.md:692
+msgid "I don't actively use all the ~100 components offered by the playbook (no one does), nor do I operate servers exercising all edge-cases. As such, issues may arise. Please have patience and report (or try to fix) these issues!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:695
+msgid "2024-01-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:697
+msgid "(Backward Compatibility) Configuration changes required for people fronting the integrated reverse-proxy webserver with another reverse-proxy"
+msgstr ""
+
+#: ../../../CHANGELOG.md:699
+msgid "If you're on the default setup (using the Traefik reverse-proxy as installed by the playbook), you don't need to do anything."
+msgstr ""
+
+#: ../../../CHANGELOG.md:701
+msgid "People who are [Fronting the integrated Traefik reverse-proxy webserver with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy), as per our previous instructions are redefining `traefik_additional_entrypoints_auto` in their `vars.yml` configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:703
+msgid "Such a full variable redefinion is intrustive, because it prevents the playbook from injecting additional entrypoints into the Traefik webserver. In the future, the playbook may have a need to do so."
+msgstr ""
+
+#: ../../../CHANGELOG.md:705
+msgid "For this reason, we no longer recommend completely redefining `traefik_additional_entrypoints_auto`. The playbook now defines [various `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_*` variables in the `defaults/main.yml` file](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-base/defaults/main.yml) of the `matrix-base` role which can be used as a safer alternative to `traefik_additional_entrypoints_auto`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:707
+msgid "Adapt your configuration as seen below:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:740
+msgid "Also, feel free to read the [Fronting the integrated Traefik reverse-proxy webserver with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) documentation section again for additional details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:743
+msgid "2024-01-13"
+msgstr ""
+
+#: ../../../CHANGELOG.md:745
+msgid "matrix-reminder-bot update with more secure (backward-incompatible) default settings"
+msgstr ""
+
+#: ../../../CHANGELOG.md:747
+msgid "**TLDR**: your updated (to [v0.3.0](https://github.com/anoadragon453/matrix-reminder-bot/releases/tag/v0.3.0)) [matrix-reminder-bot](./docs/configuring-playbook-bot-matrix-reminder-bot.md) is now more secure. By default, like other bridges/bots managed by the playbook, it will only provide its services to users of your own server (not to anyone, even across the Matrix Federation). If that's fine, there's nothing you need to do."
+msgstr ""
+
+#: ../../../CHANGELOG.md:749
+msgid "Maintenance of [matrix-reminder-bot](./docs/configuring-playbook-bot-matrix-reminder-bot.md) has been picked up by [Kim Brose](https://github.com/HarHarLinks) and [@svierne](https://github.com/svierne)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:751
+msgid "Thanks to them, a new [v0.3.0](https://github.com/anoadragon453/matrix-reminder-bot/releases/tag/v0.3.0) release is out. The new version is now available for the ARM64 architecture, so playbook users on this architecture will no longer need to wait for [self-building](./docs/self-building.md) to happen."
+msgstr ""
+
+#: ../../../CHANGELOG.md:753
+msgid "The new version also comes with new `allowlist` and `blocklist` settings, which make it possible to restrict who can use the bot. Previously anyone, even across the Matrix Federation could talk to it and schedule reminders."
+msgstr ""
+
+#: ../../../CHANGELOG.md:755
+msgid "The playbook defaults all bridges and bots (where possible) to only be exposed to users of the current homeserver, not users across federation. Thanks to the new version of this bot making such a restriction possible, we're now making use of it. The playbook (via its `group_vars/matrix_servers` file) automatically enables the `allowlist` (`matrix_bot_matrix_reminder_bot_allowlist_enabled: true`) and configures it in such a way (`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) so as to restrict the bot to your homeserver's users."
+msgstr ""
+
+#: ../../../CHANGELOG.md:757
+msgid "If you need **to undo or tweak these security improvements**, you can change your `vars.yml` file to:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:759
+msgid "disable the allowlist (`matrix_bot_matrix_reminder_bot_allowlist_enabled: false`), making the bot allow usage by anyone, anywhere"
+msgstr ""
+
+#: ../../../CHANGELOG.md:761
+msgid "inject additional allowed servers or users by adding **additional** (on top of the default allowlist in `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) custom regexes in the `matrix_bot_matrix_reminder_bot_allowlist_regexes_custom` list variable (see the [syntax reference](https://github.com/anoadragon453/matrix-reminder-bot/blob/1e910c0aa3469d280d93ee7e6c6d577227a3460c/sample.config.yaml#L43-L49))"
+msgstr ""
+
+#: ../../../CHANGELOG.md:763
+msgid "override the default allowlist (in the `group_vars/matrix_servers` file) by redefining `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:766
+msgid "2024-01-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:768
+msgid "matrix-mailer has been replaced by the exim-relay external role"
+msgstr ""
+
+#: ../../../CHANGELOG.md:770 ../../../CHANGELOG.md:1410
+msgid "We're continuing our effort to make [the playbook use external roles for some things](#the-playbook-now-uses-external-roles-for-some-things), so as to avoid doing everything ourselves and to facilitate code re-use."
+msgstr ""
+
+#: ../../../CHANGELOG.md:772
+msgid "The `matrix-mailer` role has been moved to its own repository ([ansible-role-exim-relay](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay)) that this playbook now includes."
+msgstr ""
+
+#: ../../../CHANGELOG.md:774
+msgid "To migrate:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:776
+msgid "pull the playbook changes, as usual"
+msgstr ""
+
+#: ../../../CHANGELOG.md:777
+msgid "update your roles (run `just roles` or `make roles`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:778
+msgid "update your `vars.yml`, renaming `matrix_mailer`-prefixed variables to `exim_relay`-prefixed ones (e.g. `matrix_mailer_sender_address` -> `exim_relay_sender_address`). If you find none, it means you're using the default configuration and your migraiton job is even simpler."
+msgstr ""
+
+#: ../../../CHANGELOG.md:779
+msgid "re-run the playbook (`install-all` or `setup-all`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:781
+msgid "The playbook will take care of stopping the old `matrix-mailer` systemd service, relocating its directory and restarting it under the new name (`matrix-exim-relay.service`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:784
+msgid "2024-01-02"
+msgstr ""
+
+#: ../../../CHANGELOG.md:786
+msgid "mautrix-signal now powered by the new Go-based bridge"
+msgstr ""
+
+#: ../../../CHANGELOG.md:788
+msgid "The old Python-based [mautrix-signal](https://github.com/mautrix/signal) bridge is no longer maintained upstream. It's also known to have issues linking new devices."
+msgstr ""
+
+#: ../../../CHANGELOG.md:790
+msgid "It seems like the path forward is to switch to the new mautrix-signal bridge written in Golang, which we did thanks to [PR #3031](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3041) by [Pierre 'McFly' Marty](https://github.com/pm-McFly)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:792
+msgid "The playbook should **automatically migrate your mautrix-signal installation to the new bridge code**. You will **need to relink all your devices** to continue your bridged conversations."
+msgstr ""
+
+#: ../../../CHANGELOG.md:795
+msgid "2023-10-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:797
+msgid "Enabling `allow_public_rooms_over_federation` by default for Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:799
+msgid "**TDLR**: if your Matrix server is federating (which it mostly likely is, unless you've [disabled federation](docs/configuring-playbook-federation.md#disabling-federation)), your public rooms will not only be joinable across federation (as they've always been), but from now on will be discoverable (made available as a list across federation). We're changing this by flipping the value for Synapse's `allow_public_rooms_over_federation` setting to `true`, going against the upstream default. Servers that disable federation are not affected. Servers that have public rooms which are not published to the room directory are also not affected."
+msgstr ""
+
+#: ../../../CHANGELOG.md:801
+msgid "We generally try to stick to the default configuration for Synapse (and all other components), unless these defaults seem wrong or harmful. One such previous case from a few months ago was us [Enabling `forget_rooms_on_leave` by default for Synapse](#enabling-forget_rooms_on_leave-by-default-for-synapse) - the default value was making Synapse more wasteful of resources by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:803
+msgid "Today, we're going against upstream defaults again and flipping the `allow_public_rooms_over_federation` configuration option to `true`. This way, public rooms on your server will be made discoverable by others via federation, using the [`GET /_matrix/federation/v1/publicRooms` of the Server-Server API](https://spec.matrix.org/v1.8/server-server-api/#get_matrixfederationv1publicrooms)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:805
+msgid "The upstream Synapse default is `false` (disabled), so that public rooms are not exposed for other servers to discover (learn about their existence). Nevertheless, even if these rooms are not exposed (listed) for discovery, they are **still joinable** by anyone who knows their address or is invited to the room by an existing member."
+msgstr ""
+
+#: ../../../CHANGELOG.md:807
+msgid "**We go against the upstream default** in an effort to make Matrix federation more useful - a public room should be globally public - not only joinable, but also discoverable across federation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:809
+msgid "The **historical reasoning** behind this change is as follows:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:811
+msgid "`allow_public_rooms_over_federation` seems to have been enabled by default for Synapse until v1.7.0 (~2019), just like we believe it should be for a globally-federating network - rooms should be joinable and discoverable across federation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:813
+msgid "In Synapse v1.7.0 (~2019), `allow_public_rooms_over_federation` [got disabled](https://github.com/element-hq/synapse/blob/e9069c9f919685606506f04527332e83fbfa44d9/docs/upgrade.md?plain=1#L1877-L1891) by default in a [security-by-obscurity](https://en.wikipedia.org/wiki/Security_through_obscurity) workaround for misconfigured servers. See the [Avoiding unwelcome visitors on private Matrix servers](https://matrix.org/blog/2019/11/09/avoiding-unwelcome-visitors-on-private-matrix-servers/) `matrix.org` blog article. We believe that people wishing for a truly private server, should [disable federation](docs/configuring-playbook-federation.md#disabling-federation), instead of having a fully-federating server and trying to hide its public rooms. We also provide other workarounds below. We (and the Synapse team, obviously) believe that Matrix should federate by default, so federating the public room list seems to make sense."
+msgstr ""
+
+#: ../../../CHANGELOG.md:815
+#, python-format
+msgid "[etke.cc](https://etke.cc/) has been developing the free-software [Matrix Rooms Search](https://github.com/etkecc/mrs) project for a while now. One public (demo) instance of it is hosted at [matrixrooms.info](https://matrixrooms.info/). This search engine tries to go through the Matrix federation and discover & index public rooms to allow people to find them. We believe it's vital for Matrix (and any chat or social network for that matter) to be more discoverable, so that people can find communities and others to talk to. Today (on 23rd of October 2023), `matrixrooms.info` is indexing `23066` Matrix servers. Of these, only `1567` servers (7%) are making their public rooms discoverable. Who knows what wonderful communities and rooms are available on these 93% other Matrix servers that are supposedly federating, but are still gate-keeping their public room list. Indubitably, many of these servers are hosted via matrix-docker-ansible-deploy, so we feel partially responsible for making Matrix federation less useful."
+msgstr ""
+
+#: ../../../CHANGELOG.md:817
+msgid "Here are **actions you may wish to take** as a result of this change:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:819
+msgid "(recommended) embrace the new default. If your Matrix server is federating, your public rooms have always been joinable across federation anyway. Exposing the list of public rooms does no harm and more-so does good by contributing to the usefulness of the Matrix network by facilitating room discovery."
+msgstr ""
+
+#: ../../../CHANGELOG.md:821
+msgid "(switch to a better way of doings things on your semi-private server) The problem that the Synapse team appears to have solved by flipping the `allow_public_rooms_over_federation` default in Synapse v1.7.0 seems to for \"mostly private\" servers, which federate and have a bunch of rooms made public (and published in their room directory) in an effort to allow people on the same homeserver to easily find and join them (self-onboarding). With the introduction of Matrix Spaces, you can reorganize your flow around spaces - you can auto-join your users to a Matrix Space (via Synapse's `auto_join_rooms` setting - controlled by our `matrix_synapse_auto_join_rooms` variable), then add a bunch of rooms to the space and make them joinable by people belonging to the space. That is to say, do not make rooms public and do not publish them to the room directory unless they are really public. Instead, use other mechanisms for semi-public rooms or private rooms. One alternative is to stick to what you're doing (public rooms published to your rooms directory) but having a `m.federate: true` flag set during creation (clients like Element Web have a nice UI checkbox for this) to explicitly disable federation for them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:823
+msgid "(keeping the old behavior) if you wish to keep doing what you're doing (keeping your Matrix server federating, but hiding its public rooms list), add `matrix_synapse_allow_public_rooms_over_federation: false` to your `vars.yml` configuration. This restores the old behavior. You may also consider [disabling federation](docs/configuring-playbook-federation.md#disabling-federation) completely instead of relying on security-by-obscurity measures."
+msgstr ""
+
+#: ../../../CHANGELOG.md:826
+msgid "2023-10-18"
+msgstr ""
+
+#: ../../../CHANGELOG.md:828
+msgid "Postgres parameters are automatically tuned now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:830
+msgid "The playbook has provided some hints about [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) for quite a while now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:832
+msgid "From now on, the [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) automatically tunes your Postgres configuration with the same [calculation logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) that powers https://pgtune.leopard.in.ua/."
+msgstr ""
+
+#: ../../../CHANGELOG.md:834
+msgid "Our [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) documentation page has details about how you can turn auto-tuning off or adjust the automatically-determined Postgres configuration parameters manually."
+msgstr ""
+
+#: ../../../CHANGELOG.md:836
+msgid "People who [enable load-balancing with Synapse workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) no longer need to increase the maximum number of Postgres connections manually (previously done via `postgres_process_extra_arguments`). There's a new variable (`postgres_max_connections`) for controlling this number and the playbook automatically raises its value from `200` to `500` for setups which enable workers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:839
+msgid "2023-08-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:841
+msgid "SchildiChat Web support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:843
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client."
+msgstr ""
+
+#: ../../../CHANGELOG.md:845
+msgid "See our [Configuring SchildiChat Web](docs/configuring-playbook-client-schildichat-web.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:848
+msgid "2023-08-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:850
+msgid "mautrix-wsproxy support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:852
+msgid "Thanks to [Johan Swetzén](https://github.com/jswetzen)'s efforts (who finished what was started by [James Reilly](https://github.com/hanthor) and [Shreyas Ajjarapu](https://github.com/shreyasajj)), the playbook now supports bridging to Android SMS and Apple iMessage via the [mautrix-wsproxy](https://github.com/mautrix/wsproxy) service (in combination with a [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android phone)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:854
+msgid "See our [Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](docs/configuring-playbook-bridge-mautrix-wsproxy.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:857
+msgid "2023-07-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:859
+msgid "matrix-registration-bot usage changed"
+msgstr ""
+
+#: ../../../CHANGELOG.md:861
+msgid "[matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) got some updates and now supports password-only-based login. Therefore the bot now doesn't need any manual configuration except setting a password in your `vars.yml`. The bot will be registered as admin and access tokens will be obtained automatically by the bot."
+msgstr ""
+
+#: ../../../CHANGELOG.md:863
+msgid "**For existing users** You need to set `matrix_bot_matrix_registration_bot_bot_password` if you previously only used `matrix_bot_matrix_registration_bot_bot_access_token`. Please also remove the following deprecated settings"
+msgstr ""
+
+#: ../../../CHANGELOG.md:865
+msgid "`matrix_bot_matrix_registration_bot_bot_access_token`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:866
+msgid "`matrix_bot_matrix_registration_bot_api_token`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:869
+msgid "2023-07-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:871
+msgid "mautrix-gmessages support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:873
+msgid "Thanks to [Shreyas Ajjarapu](https://github.com/shreyasajj)'s efforts, the playbook now supports bridging to [Google Messages](https://messages.google.com/) via the [mautrix-gmessages](https://github.com/mautrix/gmessages) bridge. See our [Setting up Mautrix Google Messages bridging](docs/configuring-playbook-bridge-mautrix-gmessages.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:876
+msgid "2023-07-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:878
+msgid "matrix-media-repo support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:880
+msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [matrix-media-repo](https://github.com/turt2live/matrix-media-repo) - an alternative way to store homeserver media files, powered by a homeserver-independent implementation which supports S3 storage, IPFS, deduplication and other advanced features."
+msgstr ""
+
+#: ../../../CHANGELOG.md:882
+msgid "To learn more see our [Storing Matrix media files using matrix-media-repo](docs/configuring-playbook-matrix-media-repo.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:885
+msgid "2023-05-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:887
+msgid "Enabling `forget_rooms_on_leave` by default for Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:889
+msgid "With the [Synapse v1.84.0 update](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2698), we've also **changed the default value** of the `forget_rooms_on_leave` setting of Synapse to a value of `true`. This way, **when you leave a room, Synapse will now forget it automatically**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:891
+msgid "The upstream Synapse default is `false` (disabled), so that you must forget rooms manually after leaving."
+msgstr ""
+
+#: ../../../CHANGELOG.md:893
+msgid "**We go against the upstream default** ([somewhat controversially](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2700)) in an effort to make Synapse leaner and potentially do what we believe most users would expect their homeserver to be doing."
+msgstr ""
+
+#: ../../../CHANGELOG.md:895
+msgid "If you'd like to go back to the old behavior, add the following to your configuration: `matrix_synapse_forget_rooms_on_leave: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:898
+msgid "2023-04-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:900
+msgid "The matrix-jitsi role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:902
+msgid "**TLDR**: the `matrix-jitsi` role is now included from the [ansible-role-jitsi](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi) repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:904
+msgid "The `matrix-jitsi` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project - an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Jitsi stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so."
+msgstr ""
+
+#: ../../../CHANGELOG.md:906
+msgid "As part of the extraction process of this role out of the Matrix playbook, a few other things improved:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:908
+msgid "**native Traefik support** has been added"
+msgstr ""
+
+#: ../../../CHANGELOG.md:909
+msgid "**support for hosting under a subpath** has been added, although it suffers from a few minor issues listed [here](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/jitsi.md#url)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:911
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Jitsi or not."
+msgstr ""
+
+#: ../../../CHANGELOG.md:913
+msgid "If you're making use of Jitsi via this playbook, you will need to update variable references in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:915
+msgid "`matrix_jitsi_*_docker_image_` -> `matrix_jitsi_*_container_image_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:916
+msgid "`matrix_jitsi_` -> `jitsi_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:917 ../../../CHANGELOG.md:944
+msgid "some other internal variables have changed, but the playbook will tell you about them"
+msgstr ""
+
+#: ../../../CHANGELOG.md:919
+msgid "2023-03-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:921
+msgid "ntfy Web App is disabled by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:923
+msgid "ntfy provides a web app, which is now disabled by default, because it may be unknown to and unused by most users of this playbook. You can enable it by setting `ntfy_web_root: \"app\"` (see [ntfy documentation](docs/configuring-playbook-ntfy.md))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:925
+msgid "This change was already applied a while before this entry, but as some users were reporting the missing web app, this entry was added (see [#2529](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2529))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:928
+msgid "2023-03-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:930
+msgid "The matrix-prometheus role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:932
+msgid "**TLDR**: the `matrix-prometheus` role is now included from the [ansible-role-prometheus](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus) repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:934
+msgid "The `matrix-prometheus` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project - an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Prometheus stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so."
+msgstr ""
+
+#: ../../../CHANGELOG.md:936
+msgid "Extracting the Prometheus role out of this Matrix playbook required huge internal refactoring to the way the Prometheus configuration (scraping jobs) is generated. If you notice any breakage after upgrading, let us know."
+msgstr ""
+
+#: ../../../CHANGELOG.md:938
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Prometheus or not."
+msgstr ""
+
+#: ../../../CHANGELOG.md:940
+msgid "If you're making use of Prometheus via this playbook, you will need to update variable references in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:942
+msgid "`matrix_prometheus_docker_image_` -> `matrix_prometheus_container_image_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:943
+msgid "`matrix_prometheus_` -> `prometheus_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:947
+msgid "2023-03-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:949
+msgid "synapse-auto-compressor support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:951
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state)'s `synapse_auto_compressor` tool to run periodically."
+msgstr ""
+
+#: ../../../CHANGELOG.md:953
+msgid "If enabled, `synapse_auto_compressor` runs on a schedule and compresses your Synapse database's `state_groups` table. It was possible to run `rust-synapse-compress-state` manually via the playbook even before - see [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state). However, using `synapse_auto_compressor` is better, because:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:955
+msgid "it runs on a more up-to-date version of `rust-synapse-compress-state`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:956
+msgid "it's a set-it-and-forget-it tool that you can enable and never have to deal with manual compression anymore"
+msgstr ""
+
+#: ../../../CHANGELOG.md:958
+msgid "This tool needs to be enabled manually, for now. In the future, we're considering enabling it by default for all Synapse installations."
+msgstr ""
+
+#: ../../../CHANGELOG.md:960
+msgid "See our [Setting up synapse-auto-compressor](docs/configuring-playbook-synapse-auto-compressor.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:963
+msgid "2023-03-07"
+msgstr ""
+
+#: ../../../CHANGELOG.md:965
+msgid "Sliding Sync proxy (Element X) support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:967
+msgid "Thanks to [Benjamin Kampmann](https://github.com/gnunicorn) for [getting it started](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2515), [FSG-Cat](https://github.com/FSG-Cat) for fixing it up and me ([Slavi](https://github.com/spantaleev)) for polishing it up, the playbook can now install and configure the [sliding-sync proxy](https://github.com/matrix-org/sliding-sync)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:969
+msgid "The upcoming Element X clients ([Element X iOS](https://github.com/vector-im/element-x-ios) and [Element X Android](https://github.com/vector-im/element-x-android)) require the `sliding-sync` proxy to do their job. **These clients are still in beta** (especially Element X Android, which requires manual compilation to get it working with a non-`matrix.org` homeseserver). Playbook users can now easily give these clients a try and help test them thanks to us having `sliding-sync` support."
+msgstr ""
+
+#: ../../../CHANGELOG.md:971
+msgid "To get started, see our [Setting up the Sliding Sync proxy](docs/configuring-playbook-sliding-sync-proxy.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:974
+msgid "2023-03-02"
+msgstr ""
+
+#: ../../../CHANGELOG.md:976
+msgid "The matrix-etherpad role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:978
+msgid "**TLDR**: the `matrix-etherpad` role is now included from [another repository](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:980
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Etherpad or not."
+msgstr ""
+
+#: ../../../CHANGELOG.md:982
+msgid "If you're making use of Etherpad via this playbook, you will need to update variable references in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:984
+msgid "Rename `matrix_etherpad_public_endpoint` to `etherpad_path_prefix`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:986
+msgid "Replace `matrix_etherpad_mode: dimension` with:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:987
+msgid "for `matrix-nginx-proxy` users:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:988
+msgid "`etherpad_nginx_proxy_dimension_integration_enabled: true`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:989
+msgid "`etherpad_hostname: \"{{ matrix_server_fqn_dimension }}\"`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:990
+msgid "for Traefik users:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:991
+msgid "define your own `etherpad_hostname` and `etherpad_path_prefix` as you see fit"
+msgstr ""
+
+#: ../../../CHANGELOG.md:993
+msgid "Rename all other variables:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:994
+msgid "`matrix_etherpad_docker_image_` -> `matrix_etherpad_container_image_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:995
+msgid "`matrix_etherpad_` -> `etherpad_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:997
+msgid "Along with this relocation, the new role also:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:999
+msgid "supports [self-building](docs/self-building.md), so it should work on `arm32` and `arm64` architectures"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1000
+msgid "has native Traefik reverse-proxy support (Etherpad requests no longer go through `matrix-nginx-proxy` when using Traefik)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1003
+msgid "2023-02-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1005
+msgid "Traefik is the default reverse-proxy now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1007
+msgid "**TLDR**: new installations will now default to Traefik as their reverse-proxy. Existing users need to explicitly choose their reverse-proxy type. [Switching to Traefik](#how-do-i-switch-my-existing-setup-to-traefik) is strongly encouraged. `matrix-nginx-proxy` may break over time and will ultimately be removed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1009
+msgid "As mentioned 2 weeks ago in [(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support](#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support), the playbook is moving to Traefik as its default SSL-terminating reverse-proxy."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1011
+msgid "Until now, we've been doing the migration gradually and keeping full backward compatibility. New installations were defaulting to `matrix-nginx-proxy` (just like before), while existing installations were allowed to remain on `matrix-nginx-proxy` as well. This makes things very difficult for us, because we need to maintain and think about lots of different setups:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1013
+msgid "Traefik managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1014
+msgid "Traefik managed by the user in another way"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1015
+msgid "another reverse-proxy on the same host (`127.0.0.1` port exposure)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1016
+msgid "another reverse-proxy on another host (`0.0.0.0` port exposure)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1017
+msgid "`matrix-nginx-proxy` - an `nginx` container managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1018
+msgid "`nginx` webserver operated by the user, running without a container on the same server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1020
+msgid "Each change we do and each new feature that comes in needs to support all these different ways of reverse-proxying. Because `matrix-nginx-proxy` was the default and pretty much everyone was (and still is) using it, means that new PRs also come with `matrix-nginx-proxy` as their main focus and Traefik as an afterthought, which means we need to spend hours fixing up Traefik support."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1022
+msgid "We can't spend all this time maintaining so many different configurations anymore. Traefik support has been an option for 2 weeks and lots of people have already migrated their server and have tested things out. Traefik is what we use and preferentially test for."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1024
+msgid "It's time for the **next step in our migration process** to Traefik and elimination of `matrix-nginx-proxy`:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1026
+msgid "Traefik is now the default reverse-proxy for new installations"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1027
+msgid "All existing users need to explicitly choose their reverse-proxy type by defining the `matrix_playbook_reverse_proxy_type` variable in their `vars.yml` configuration file. We strongly encourage existing users to [switch the Traefik](#how-to-switch-an-existing-setup-to-traefik), as the nginx setup is bound to become more and more broken over time until it's ultimately removed"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1029
+msgid "How do I switch my existing setup to Traefik?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1031
+msgid "**For users who are on `matrix-nginx-proxy`** (the default reverse-proxy provided by the playbook), switching to Traefik can happen with a simple configuration change. Follow this section from 2 weeks ago: [How do I explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-traefik-right-now)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1033
+msgid "If you experience trouble:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1035
+msgid "Follow [How do I remain on matrix-nginx-proxy?](#how-do-i-remain-on-matrix-nginx-proxy) to bring your server back online using the old reverse-proxy"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1036
+msgid "Ask for help in our [support channels](README.md#support)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1037
+msgid "Try switching to Traefik again later"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1039
+msgid "**For users with a more special reverse-proxying setup** (another nginx server, Apache, Caddy, etc.), the migration may not be so smooth. Follow the [Using your own webserver](docs/configuring-playbook-own-webserver.md) guide. Ideally, your custom reverse-proxy will be configured in such a way that it **fronts the Traefik reverse-proxy** provided by the playbook. Other means of reverse-proxying are more fragile and may be deprecated in the future."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1041
+msgid "I already use my own Traefik server. How do I plug that in?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1043
+msgid "See the [Traefik managed by the playbook](docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) section."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1045
+msgid "Why is matrix-nginx-proxy used even after switching to Traefik?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1047
+msgid "This playbook manages many different services. All these services were initially integrated with `matrix-nginx-proxy`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1049
+msgid "While we migrate all these components to have native Traefik support, some still go through nginx internally (Traefik -> local `matrix-nginx-proxy` -> component). As time goes on, internal reliance on `matrix-nginx-proxy` will gradually decrease until it's completely removed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1051
+msgid "How do I remain on matrix-nginx-proxy?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1053
+msgid "Most new work and testing targets Traefik, so remaining on nginx is **not** \"the good old stable\" option, but rather the \"still available, but largely untested and likely to be broken very soon\" option."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1055
+msgid "To proceed regardless of this warning, add `matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1057
+msgid "At some point in the **near** future (days, or even weeks at most), we hope to completely get rid of `matrix-nginx-proxy` (or break it enough to make it unusable), so you **will soon be forced to migrate** anyway. Plan your migration accordingly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1059
+msgid "How do I keep using my own other reverse-proxy?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1061
+msgid "We recommend that you follow the guide for [Fronting the integrated reverse-proxy webserver with another reverse-proxy](docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1064
+msgid "2023-02-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1066
+msgid "rageshake support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1068
+msgid "Thanks to [Benjamin Kampmann](https://github.com/gnunicorn), the playbook can now install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1070
+msgid "Additional details are available in [Setting up rageshake](docs/configuring-playbook-rageshake.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1073
+msgid "2023-02-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1075
+msgid "Synapse templates customization support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1077
+msgid "The playbook can now help you customize Synapse's templates."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1079
+msgid "Additional details are available in the [Customizing templates](docs/configuring-playbook-synapse.md#customizing-templates) section of our Synapse documentation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1081
+msgid "The matrix-redis role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1083
+msgid "**TLDR**: the `matrix-redis` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1085
+msgid "The `matrix-redis` role (which configures [Redis](https://redis.io/)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-redis). This makes it possible to easily use it in other Ansible playbooks."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1087
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Ntfy or not. If you're making use of Ntfy via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_redis_` -> `redis_`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1089
+msgid "The matrix-ntfy role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1091
+msgid "**TLDR**: the `matrix-ntfy` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1093
+msgid "The `matrix-ntfy` role (which configures [Ntfy](https://ntfy.sh/)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy). This makes it possible to easily use it in other Ansible playbooks."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1095
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Ntfy or not. If you're making use of Ntfy via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_ntfy_` -> `ntfy_`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1098
+msgid "2023-02-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1100
+msgid "The matrix-grafana role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1102
+msgid "**TLDR**: the `matrix-grafana` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1104
+msgid "The `matrix-grafana` role (which configures [Grafana](docs/configuring-playbook-prometheus-grafana.md)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-grafana). This makes it possible to easily use it in other Ansible playbooks."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1106
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Grafana or not. If you're making use of Grafana via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_grafana_` -> `grafana_`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1109
+msgid "2023-02-13"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1111
+msgid "The matrix-backup-borg role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1113
+msgid "**TLDR**: the `matrix-backup-borg` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1115
+msgid "Thanks to [moan0s](https://github.com/moan0s), the `matrix-backup-borg` role (which configures [BorgBackup](docs/configuring-playbook-backup-borg.md)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). This makes it possible to easily use it in other Ansible playbooks and will become part of [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) soon."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1117
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Borg's backup functionality or not. If you're making use of BorgBackup via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_backup_borg_` -> `backup_borg_`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1120
+msgid "2023-02-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1122
+msgid "(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1124
+msgid "**TLDR**:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1126
+msgid "there's a new `matrix_playbook_reverse_proxy_type` variable (see [roles/custom/matrix-base/defaults/main.yml](roles/custom/matrix-base/defaults/main.yml)), which lets you tell the playbook what reverse-proxy setup you'd like to have. This makes it easier for people who want to do reverse-proxying in other ways."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1127
+msgid "the default reverse-proxy (`matrix_playbook_reverse_proxy_type`) is still `playbook-managed-nginx` (via `matrix-nginx-proxy`), for now. **Existing `matrix-nginx-proxy` users should not observe any changes** and can stay on this for now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1128
+msgid "**Users who use their [own other webserver](docs/configuring-playbook-own-webserver.md) (e.g. Apache, etc.) need to change** `matrix_playbook_reverse_proxy_type` to something like `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1129
+msgid "we now have **optional [Traefik](https://traefik.io/) support**, so you could easily host Matrix and other Traefik-native services in containers on the same server. Traefik support is still experimental (albeit, good enough) and will improve over time. It does work, but certain esoteric features may not be there yet."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1130
+msgid "**Traefik will become the default reverse-proxy in the near future**. `matrix-nginx-proxy` will either remain as an option, or be completely removed to simplify the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1132
+msgid "Motivation for redoing our reverse-proxy setup"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1134
+msgid "The playbook has supported various reverse-proxy setups for a long time. We have various configuration variables (`matrix_nginx_proxy_enabled`, various `_host_bind_port` variables, etc.) which allow the playbook to adapt to these different setups. The whole situation was messy though - hard to figure out and with lots of variables to toggle to make things work as you'd expect - huge **operational complexity**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1136
+msgid "We love containers, proven by the fact that **everything** that this playbook manages runs in a container. Yet, we weren't allowing people to easily host other web-exposed containers alongside Matrix services on the same server. We were using `matrix-nginx-proxy` (our integrated [nginx](https://nginx.org/) server), which was handling web-exposure and SSL termination for our own services, but we **weren't helping you with all your other containers**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1138
+msgid "People who were **using `matrix-nginx-proxy`** were on the happy path on which everything worked well by default (Matrix-wise), **but** could not easily run other web-exposed services on their Matrix server because `matrix-nginx-proxy` was occupying ports `80` and `443`. Other services which wanted to get web exposure either had to be plugged into `matrix-nginx-proxy` (somewhat difficult) or people had to forgo using `matrix-nginx-proxy` in favor of something else."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1140
+msgid "Of those that decided to forgo `matrix-nginx-proxy`, many were **using nginx** on the same server without a container. This was likely some ancient nginx version, depending on your choice of distro. The Matrix playbook was trying to be helpful and even with `matrix_nginx_proxy_enabled: false` was still generating nginx configuration in `/matrix/nginx-proxy/conf.d`. Those configuration files were adapted for inclusion into an nginx server running locally. Disabling the `matrix-nginx-proxy` role like this, yet still having it produce files is a bit disgusting, but it's what we've had since the early beginnings of this playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1142
+msgid "Others still, wanted to run Matrix locally (no SSL certificates), regardless of which web server technology this relied on, and then **reverse-proxy from another machine on the network** which was doing SSL termination. These people were:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1144
+msgid "*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined with exposing services manually (setting `_bind_port` variables)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1145
+msgid "*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in `http`-only mode (no SSL certificate retrieval)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1147
+msgid "Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1149
+msgid "When using `matrix-nginx-proxy` as is, we still had another problem - one of **internal playbook complexity**. Too many services need to be web-exposed (port 80/443, SSL certificates). Because of this, they all had to integrate with the `matrix-nginx-proxy` role. Tens of different roles explicitly integrating with `matrix-nginx-proxy` is not what we call clean. The `matrix-nginx-proxy` role contains variables for many of these roles (yikes). Other roles were more decoupled from it and were injecting configuration into `matrix-nginx-proxy` at runtime - see all the `inject_into_nginx_proxy.yml` task files in this playbook (more decoupled, but still.. yikes)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1151
+msgid "The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1153
+msgid "[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy) for hosting the [Vaultwarden](https://github.com/dani-garcia/vaultwarden) server - an alternative implementation of the [Bitwarden](https://bitwarden.com/) password manager"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1154
+msgid "[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) - for hosting the [Gitea](https://gitea.io/) git source code hosting service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1155
+msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) - for hosting the [Nextcloud](https://nextcloud.com/) groupware platform"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1157
+msgid "We'd love for users to be able to **seamlessly use all these playbooks (and others, even) against a single server**. We don't want `matrix-nginx-proxy` to have a monopoly on port `80`/`443` and make it hard for other services to join in on the party. Such a thing forces people into running multiple servers (one for each service), which does provide nice security benefits, but is costly and ineffiecient. We'd like to make self-hosting these services cheap and easy."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1159
+msgid "These other playbooks have been using [Traefik](https://traefik.io/) as their default reverse-proxy for a long time. They can all coexist nicely together (as an example, see the [Interoperability](https://github.com/spantaleev/nextcloud-docker-ansible-deploy/blob/master/docs/configuring-playbook-interoperability.md) documentation for the [Nextcloud playbook](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)). Now that this playbook is gaining Traefik support, it will be able to interoperate with them. If you're going this way, make sure to have the Matrix playbook install Traefik and have the others use `*_reverse_proxy_type: other-traefik-container`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1161
+msgid "Finally, at [etke.cc - a managed Matrix server hosting service](https://etke.cc) (built on top of this playbook, and coincidentally [turning 2 years old today](https://etke.cc/news/upsyw4ykbtgmwhz8k7ukldx0zbbfq-fh0iqi3llixi0/) 🎉), we're allowing people to host some additional services besides Matrix components. Exposing these services to the web requires ugly hacks and configuration files being dropped into `/matrix/nginx-proxy/conf.d`. We believe that everything should run in independent containers and be exposed to the web via a Traefik server, without a huge Ansible role like `matrix-nginx-proxy` that everything else needs to integrate with."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1163
+msgid "How do these changes fix all these problems?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1165
+msgid "The new `matrix_playbook_reverse_proxy_type` lets you easily specify your preferred reverse-proxy type, including `other-on-same-host`, `other-on-another-host` and `none`, so people who'd like to reverse-proxy with their own web server have more options now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1167
+msgid "Using Traefik greatly simplifies things, so going forward we'll have a simpler and easier to maintain playbook, which is also interoperable with other services."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1169
+msgid "Traefik is a web server, which has been specifically **designed for reverse-proxying to services running in containers**. It's ideal for usage in an Ansible playbook which runs everything in containers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1171
+msgid "**Traefik obtains SSL certificates automatically**, so there's no need for plugging additional tools like [Certbot](https://certbot.eff.org/) into your web server (like we were doing in the `matrix-nginx-proxy` role). No more certificate renewal timers, web server reloading timers, etc. It's just simpler."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1173
+msgid "Traefik is a **modern web server**. [HTTP/3](https://doc.traefik.io/traefik/routing/entrypoints/#http3) is supported already (experimentally) and will move to stable soon, in the upcoming Traefik v3 release."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1175
+msgid "Traefik does not lock important functionality we'd like to use into [plus packages like nginx does](https://www.nginx.com/products/nginx/), leading us to resolve to configuration workarounds. The default Traefik package is good enough as it is."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1177
+msgid "Where we're at right now?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1179
+msgid "`matrix_playbook_reverse_proxy_type` still defaults to a value of `playbook-managed-nginx`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1181
+msgid "Unless we have some regression, **existing `matrix-nginx-proxy` users should be able to update their Matrix server and not observe any changes**. Their setup should still remain on nginx and everything should still work as expected."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1183
+msgid "**Users using [their own webservers](docs/configuring-playbook-own-webserver.md) will need to change `matrix_playbook_reverse_proxy_type`** to something like `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`. Previously, they could toggle `matrix_nginx_proxy_enabled` to `false`, and that made the playbook automatically expose services locally. Currently, we only do this if you change the reverse-proxy type to `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1185
+msgid "How do I explicitly switch to Traefik right now?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1187
+msgid "**Users who wish to migrate to Traefik** today, can do so by **adding** this to their configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1195
+msgid "You may still need to keep certain old `matrix_nginx_proxy_*` variables (like `matrix_nginx_proxy_base_domain_serving_enabled`), even when using Traefik. For now, we recommend keeping all `matrix_nginx_proxy_*` variables just in case. In the future, reliance on `matrix-nginx-proxy` will be removed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1197
+msgid "Switching to Traefik will obtain new SSL certificates from Let's Encrypt (stored in `/matrix/traefik/ssl/acme.json`). **The switch is reversible**. You can always go back to `playbook-managed-nginx` if Traefik is causing you trouble."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1199
+msgid "**Note**: toggling `matrix_playbook_reverse_proxy_type` between Traefik and nginx will uninstall the Traefik role and all of its data (under `/matrix/traefik`), so you may run into a Let's Encrypt rate limit if you do it often."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1201
+msgid "Treafik directly reverse-proxies to **some** services right now, but for most other services it goes through `matrix-nginx-proxy` (e.g. Traefik -> `matrix-nginx-proxy` -> [Ntfy](docs/configuring-playbook-ntfy.md)). So, even if you opt into Traefik, you'll still see `matrix-nginx-proxy` being installed in local-only mode. This will improve with time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1203
+msgid "Some services (like [Coturn](docs/configuring-playbook-turn.md) and [Postmoogle](docs/configuring-playbook-bridge-postmoogle.md)) cannot be reverse-proxied to directly from Traefik, so they require direct access to SSL certificate files extracted out of Traefik. The playbook does this automatically thanks to a new [com.devture.ansible.role.traefik_certs_dumper](https://github.com/devture/com.devture.ansible.role.traefik_certs_dumper) role utilizing the [traefik-certs-dumper](https://github.com/ldez/traefik-certs-dumper) tool."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1205
+msgid "Our Traefik setup mostly works, but certain esoteric features may not work. If you have a default setup, we expect you to have a good experience."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1207
+msgid "Where we're going in the near future?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1209
+msgid "The `matrix-nginx-proxy` role is quite messy. It manages both nginx and Certbot and its certificate renewal scripts and timers. It generates configuration even when the role is disabled (weird). Although it doesn't directly reach into variables from other roles, it has explicit awareness of various other services that it reverse-proxies to (`roles/custom/matrix-nginx-proxy/templates/nginx/conf.d/matrix-ntfy.conf.j2`, etc.). We'd like to clean this up. The only way is probably to just get rid of the whole thing at some point."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1211
+msgid "For now, `matrix-nginx-proxy` will stay around."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1213
+msgid "As mentioned above, Traefik still reverse-proxies to some (most) services by going through a local-only `matrix-nginx-proxy` server. This has allowed us to add Traefik support to the playbook early on (without having to rework all services), but is not the final goal. We'll **work on making each service support Traefik natively**, so that traffic will not need to go through `matrix-nginx-proxy` anymore. In the end, choosing Traefik should only give you a pure Traefik installation with no `matrix-nginx-proxy` in sight."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1215
+msgid "As Traefik support becomes complete and proves to be stable for a while, especially as a playbook default, we will **most likely remove `matrix-nginx-proxy` completely**. It will likely be some months before this happens though. Keeping support for both Traefik and nginx in the playbook will be a burden, especially with most of us running Traefik in the future. The Traefik role should do everything nginx does in a better and cleaner way. Users who use their own `nginx` server on the Matrix server will be inconvenienced, as nothing will generate ready-to-include nginx configuration for them. Still, we hope it won't be too hard to migrate their setup to another way of doing things, like:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1217
+msgid "not using nginx anymore. A common reason for using nginx until now was that you were running other containers and you need your own nginx to reverse-proxy to all of them. Just switch them to Traefik as well."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1218
+msgid "running Traefik in local-only mode (`traefik_config_entrypoint_web_secure_enabled: false`) and using some nginx configuration which reverse-proxies to Traefik (we should introduce examples for this in `examples/nginx`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1220
+msgid "How do I help?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1222
+msgid "You can help by:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1224
+msgid "**explicitly switching your server to Traefik** right now (see example configuration in [How do I explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-traefik-right-now) above), testing, reporting troubles"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1226
+msgid "**adding native Traefik support to a role** (requires adding Traefik labels, etc.) - for inspiration, see these roles ([prometheus_node_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter), [prometheus_postgres_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter)) and how they're hooked into the playbook via [group_vars/matrix_servers](group_vars/matrix_servers)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1228
+msgid "**adding reverse-proxying examples for nginx users** in `examples/nginx`. People who insist on using their own `nginx` server on the same Matrix host, can run Traefik in local-only mode (`traefik_config_entrypoint_web_secure_enabled: false`) and reverse-proxy to the Traefik server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1231
+msgid "2023-02-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1233
+msgid "Matrix Authentication Support for Jitsi"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1235
+msgid "Thanks to [Jakob S.](https://github.com/jakicoll) ([zakk gGmbH](https://github.com/zakk-it)), Jitsi can now use Matrix for authentication (via [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1237
+msgid "Additional details are available in the [Authenticate using Matrix OpenID (Auth-Type 'matrix')](docs/configuring-playbook-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1239
+msgid "Draupnir moderation tool (bot) support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1241
+msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (bot). Draupnir is a fork of [Mjolnir](docs/configuring-playbook-bot-mjolnir.md) (which the playbook has supported for a long time) maintained by Mjolnir's former lead developer."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1243
+msgid "Additional details are available in [Setting up Draupnir](docs/configuring-playbook-bot-draupnir.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1246
+msgid "2023-02-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1248
+msgid "The matrix-prometheus-postgres-exporter role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1250
+msgid "**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1252
+msgid "The `matrix-prometheus-postgres-exporter` role (which configures [Prometheus Postgres Exporter](https://github.com/prometheus-community/postgres_exporter)) has been extracted from the playbook and now lives in its own repository at https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1254
+msgid "It's still part of the playbook, but is now installed via `ansible-galaxy` (by running `just roles` / `make roles`). Some variables have been renamed (`matrix_prometheus_postgres_exporter_` -> `prometheus_postgres_exporter_`, etc.). The playbook will report all variables that you need to rename to get upgraded. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1256
+msgid "The `matrix-prometheus-services-proxy-connect` role has bee adjusted to help integrate the new `prometheus_postgres_exporter` role with our own services (`matrix-nginx-proxy`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1258 ../../../CHANGELOG.md:1300
+msgid "Other roles which aren't strictly related to Matrix are likely to follow this fate of moving to their own repositories. Extracting them out allows other Ansible playbooks to make use of these roles easily."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1261
+msgid "2023-01-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1263
+msgid "Coturn can now use host-networking"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1265
+msgid "Large Coturn deployments (with a huge range of ports specified via `matrix_coturn_turn_udp_min_port` and `matrix_coturn_turn_udp_max_port`) experience a huge slowdown with how Docker publishes all these ports (setting up firewall forwarding rules), which leads to a very slow Coturn service startup and shutdown."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1267
+msgid "Such deployments don't need to run Coturn within a private container network anymore. Coturn can now run with host-networking by using configuration like this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1273
+msgid "With such a configuration, **Docker no longer needs to configure thousands of firewall forwarding rules** each time Coturn starts and stops. This, however, means that **you will need to ensure these ports are open** in your firewall yourself."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1275
+msgid "Thanks to us [tightening Coturn security](#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues), running Coturn with host-networking should be safe and not expose neither other services running on the host, nor other services running on the local network."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1277
+msgid "(Backward Compatibility) Tightening Coturn security can lead to connectivity issues"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1279
+msgid "**TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default Coturn blocklists. They may need to override `matrix_coturn_denied_peer_ips` and remove some IP ranges from it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1281
+msgid "Inspired by [this security article](https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-access-control-protection/), we've decided to make use of Coturn's `denied-peer-ip` functionality to prevent relaying network traffic to certain private IP subnets. This ensures that your Coturn server won't accidentally try to forward traffic to certain services running on your local networks. We run Coturn in a container and in a private container network by default, which should prevent such access anyway, but having additional block layers in place is better."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1283
+msgid "If you access your Matrix server from a local network and need Coturn to relay to private IP addresses, you may observe that relaying is now blocked due to our new default `denied-peer-ip` lists (specified in `matrix_coturn_denied_peer_ips`). If you experience such connectivity problems, consider overriding this setting in your `vars.yml` file and removing certain networks from it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1285
+msgid "We've also added `no-multicast-peers` to the default Coturn configuration, but we don't expect this to cause trouble for most people."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1288
+msgid "2023-01-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1290
+msgid "The matrix-prometheus-node-exporter role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1292
+msgid "**TLDR**: the `matrix-prometheus-node-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1294
+msgid "The `matrix-prometheus-node-exporter` role (which configures [Prometheus node exporter](https://github.com/prometheus/node_exporter)) has been extracted from the playbook and now lives in its own repository at https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1296
+msgid "It's still part of the playbook, but is now installed via `ansible-galaxy` (by running `just roles` / `make roles`). Some variables have been renamed (`matrix_prometheus_node_exporter_` -> `prometheus_node_exporter_`, etc.). The playbook will report all variables that you need to rename to get upgraded. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1298
+msgid "A new `matrix-prometheus-services-proxy-connect` role was added to the playbook to help integrate the new `prometheus_node_exporter` role with our own services (`matrix-nginx-proxy`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1303
+msgid "2023-01-13"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1305
+msgid "Support for running commands via just"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1307
+msgid "We've previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers `ansible-galaxy`, see [Makefile](Makefile)). Our `Makefile` is still around and you can still run these commands."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1309
+msgid "In addition, we've added support for running commands via [just](https://github.com/casey/just) - a more modern command-runner alternative to `make`. Instead of `make roles`, you can now run `just roles` to accomplish the same."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1311
+msgid "Our [justfile](justfile) already defines some additional helpful **shortcut** commands that weren't part of our `Makefile`. Here are some examples:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1313
+msgid "`just install-all` to trigger the much longer `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start` command"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1314
+msgid "`just install-all --ask-vault-pass` - commands also support additional arguments (`--ask-vault-pass` will be appended to the above installation command)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1315
+msgid "`just run-tags install-mautrix-slack,start` - to run specific playbook tags"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1316
+msgid "`just start-all` - (re-)starts all services"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1317
+msgid "`just stop-group postgres` - to stop only the Postgres service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1318
+msgid "`just register-user alice secret-password yes` - registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1320
+msgid "Additional helpful commands and shortcuts may be defined in the future."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1322
+msgid "This is all completely optional. If you find it difficult to [install `just`](https://github.com/casey/just#installation) or don't find any of this convenient, feel free to run all commands manually."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1325
+msgid "2023-01-11"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1327
+msgid "mautrix-slack support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1329
+msgid "Thanks to [Cody Neiman](https://github.com/xangelix)'s efforts, the playbook now supports bridging to [Slack](https://slack.com/) via the [mautrix-slack](https://mau.dev/mautrix/slack) bridge. See our [Setting up Mautrix Slack bridging](docs/configuring-playbook-bridge-mautrix-slack.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1331
+msgid "**Note**: this is a new Slack bridge. The playbook still retains Slack bridging via [matrix-appservice-slack](docs/configuring-playbook-bridge-appservice-slack.md) and [mx-puppet-slack](docs/configuring-playbook-bridge-mx-puppet-slack.md). You're free to use the bridge that serves you better, or even all three of them (for different users and use-cases)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1334
+msgid "2023-01-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1336
+msgid "ChatGPT support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1338
+msgid "Thanks to [@bertybuttface](https://github.com/bertybuttface), the playbook can now help you set up [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) - a bot through which you can talk to the [ChatGPT](https://openai.com/blog/chatgpt/) model."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1340
+msgid "See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-chatgpt.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1343
+msgid "2022-11-30"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1345
+msgid "matrix-postgres-backup has been replaced by the ansible-role-postgres-backup external role"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1347
+msgid "Just like we've [replaced Postgres with an external role](#matrix-postgres-has-been-replaced-by-the-comdevtureansiblerolepostgres-external-role) on 2022-11-28, we're now replacing `matrix-postgres-backup` with an external role - [com.devture.ansible.role.postgres_backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres_backup)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1349
+msgid "You'll need to rename your `matrix_postgres_backup`-prefixed variables such that they use a `postgres_backup` prefix."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1352
+msgid "2022-11-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1354
+msgid "matrix-postgres has been replaced by the ansible-role-postgres external role"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1356
+msgid "**TLDR**: the tasks that install the integrated Postgres server now live in an external role - [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres). You'll need to run `make roles` to install it, and to also rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix (e.g. `matrix_postgres_connection_password` -> `postgres_connection_password`). All your data will still be there! Some scripts have moved (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1358
+msgid "The `matrix-postgres` role that has been part of the playbook for a long time has been replaced with the [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) role. This was done as part of our work to [use external roles for some things](#the-playbook-now-uses-external-roles-for-some-things) for better code re-use and maintainability."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1360
+msgid "The new role is an upgraded version of the old `matrix-postgres` role with these notable differences:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1362
+msgid "it uses different names for its variables (`matrix_postgres` -> `devture_postgres`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1363
+msgid "when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-postgresql), it will vacuum all your databases, not just the Synapse one"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1365
+msgid "You'll need to run `make roles` to install the new role. You would also need to rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1367
+msgid "Note: the systemd service still remains the same - `matrix-postgres.service`. Your data will still be in `/matrix/postgres`, etc. Postgres-related scripts will be moved to `/matrix/postgres/bin` (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`, etc). Also see [The playbook no longer installs scripts in /usr/local/bin](#the-playbook-no-longer-installs-scripts-in-usrlocalbin)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1369
+msgid "The playbook no longer installs scripts to /usr/local/bin"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1371
+msgid "The locations of various scripts installed by the playbook have changed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1373
+msgid "The playbook no longer contaminates your `/usr/local/bin` directory. All scripts installed by the playbook now live in `bin/` directories under `/matrix`. Some examples are below:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1375
+msgid "`/usr/local/bin/matrix-remove-all` -> `/matrix/bin/remove-all`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1376
+msgid "`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1377
+msgid "`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> `/matrix/ssl/bin/lets-encrypt-certificates-renew`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1378
+msgid "`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin/register-user`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1381
+msgid "2022-11-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1383
+msgid "2x-5x performance improvements in playbook runtime"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1385
+msgid "**TLDR**: the playbook is 2x faster for running `--tags=setup-all` (and various other tags). It also has new `--tags=install-*` tags (like `--tags=install-all`), which skip uninstallation tasks and bring an additional 2.5x speedup. In total, the playbook can maintain your server 5 times faster."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1387
+msgid "Our [etke.cc managed Matrix hosting service](https://etke.cc) runs maintenance against hundreds of servers, so the playbook being fast means a lot. The [etke.cc Ansible playbook](https://github.com/etkecc/ansible) (which is an extension of this one) is growing to support more and more services (besides just Matrix), so the Matrix playbook being leaner prevents runtimes from becoming too slow and improves the customer experience."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1389
+msgid "Even when running `ansible-playbook` manually (as most of us here do), it's beneficial not to waste time and CPU resources."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1391
+msgid "Recently, a few large optimizations have been done to this playbook and its external roles (see [The playbook now uses external roles for some things](#the-playbook-now-uses-external-roles-for-some-things) and don't forget to run `make roles`):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1393
+msgid "Replacing Ansible `import_tasks` calls with `include_tasks`, which decreased runtime in half. Using `import_tasks` is slower and causes Ansible to go through and skip way too many tasks (tasks which could have been skipped altogether by not having Ansible include them in the first place). On an experimental VM, **deployment time was decreased from ~530 seconds to ~250 seconds**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1395
+msgid "Introducing new `install-*` tags (`install-all` and `install-COMPONENT`, e.g. `install-synapse`, `install-bot-mjolnir`), which only run Ansible tasks pertaining to installation, while skipping uninstallation tasks. In most cases, people are maintaining the same setup or they're *adding* new components. Removing components is rare. Running thousands of uninstallation tasks each time is wasteful. On an experimental VM, **deployment time was decreased from ~250 seconds (`--tags=setup-all`) to ~100 seconds (`--tags=install-all`)**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1397
+msgid "You can still use `--tags=setup-all`. In fact, that's the best way to ensure your server is reconciled with the `vars.yml` configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1399
+msgid "If you know you haven't uninstalled any services since the last time you ran the playbook, you could run `--tags=install-all` instead and benefit from quicker runtimes. It should be noted that a service may become \"eligible for uninstallation\" even if your `vars.yml` file remains the same. In rare cases, we toggle services from being auto-installed to being optional, like we did on the 17th of March 2022 when we made [ma1sd not get installed by default](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/CHANGELOG.md#compatibility-break-ma1sd-identity-server-no-longer-installed-by-default). In such rare cases, you'd also need to run `--tags=setup-all`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1402
+msgid "2022-11-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1404
+msgid "Automatic `matrix_architecture` determination"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1406
+msgid "From now on, the playbook automatically determines your server's architecture and sets the `matrix_architecture` variable accordingly. You no longer need to set this variable manually in your `vars.yml` file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1408
+msgid "Docker and the Docker SDK for Python are now installed via external roles"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1412
+msgid "Docker will now be installed on the server via the [geerlingguy.docker](https://github.com/geerlingguy/ansible-role-docker) Ansible role. If you'd like to manage the Docker installation yourself, you can disable the playbook's installation of Docker by setting `matrix_playbook_docker_installation_enabled: false`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1414
+msgid "The Docker SDK for Python (named `docker-python`, `python-docker`, etc. on the different platforms) is now also installed by another role ([com.devture.ansible.role.docker_sdk_for_python](https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python)). To disable this role and install the necessary tools yourself, use `devture_docker_sdk_for_python_installation_enabled: false`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1416
+msgid "If you're hitting issues with Docker installation or Docker SDK for Python installation, consider reporting bugs or contributing to these other projects."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1418
+msgid "These additional roles are downloaded into the playbook directory (to `roles/galaxy`) via an `ansible-galaxy ..` command. `make roles` is an easy shortcut for invoking the `ansible-galaxy` command to download these roles."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1421
+msgid "2022-11-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1423
+msgid "(Backward Compatibility Break) Changing how reverse-proxying to Synapse works - now via a `matrix-synapse-reverse-proxy-companion` service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1425
+msgid "**TLDR**: There's now a `matrix-synapse-reverse-proxy-companion` nginx service, which helps with reverse-proxying to Synapse and its various worker processes (if workers are enabled), so that `matrix-nginx-proxy` can be relieved of this role. `matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. `matrix-synapse-reverse-proxy-companion` is just one more reverse-proxy thrown into the mix for convenience. People with a more custom reverse-proxying configuration may be affected - see [Webserver configuration](#webserver-configuration) below."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1427
+msgid "Background"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1429
+msgid "Previously, `matrix-nginx-proxy` forwarded requests to Synapse directly. When Synapse is running in worker mode, the reverse-proxying configuration is more complicated (different requests need to go to different Synapse worker processes). `matrix-nginx-proxy` had configuration for sending each URL endpoint to the correct Synapse worker responsible for handling it. However, sometimes people like to disable `matrix-nginx-proxy` (for whatever reason) as detailed in [Using your own webserver, instead of this playbook's nginx proxy](docs/configuring-playbook-own-webserver.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1431
+msgid "Because `matrix-nginx-proxy` was so central to request forwarding, when it was disabled and Synapse was running with workers enabled, there was nothing which could forward requests to the correct place anymore.. which caused [problems such as this one affecting Dimension](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2090)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1433
+msgid "Solution"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1435
+msgid "From now on, `matrix-nginx-proxy` is relieved of its function of reverse-proxying to Synapse and its various worker processes. This role is now handled by the new `matrix-synapse-reverse-proxy-companion` nginx service and works even if `matrix-nginx-proxy` is disabled. The purpose of the new `matrix-synapse-reverse-proxy-companion` service is to:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1437
+msgid "serve as a companion to Synapse and know how to reverse-proxy to Synapse correctly (no matter if workers are enabled or not)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1439
+msgid "provide a unified container address for reaching Synapse (no matter if workers are enabled or not)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1440
+msgid "`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server API traffic"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1441
+msgid "`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server (Federation) API traffic"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1443
+msgid "simplify `matrix-nginx-proxy` configuration - it now only needs to send requests to `matrix-synapse-reverse-proxy-companion` or `matrix-dendrite`, etc., without having to worry about workers"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1445
+msgid "allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is disabled"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1447
+msgid "`matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. All traffic goes through it before reaching any of the services. It's just that now the Synapse traffic is routed through `matrix-synapse-reverse-proxy-companion` like this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1449
+msgid "(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> (`matrix-synapse` or some Synapse worker))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1451
+msgid "Various services (like Dimension, etc.) still talk to Synapse via `matrix-nginx-proxy` (e.g. `http://matrix-nginx-proxy:12080`) preferentially. They only talk to Synapse via the reverse-proxy companion (e.g. `http://matrix-synapse-reverse-proxy-companion:8008`) if `matrix-nginx-proxy` is disabled. Services should not be talking to Synapse (e.g. `https://matrix-synapse:8008` directly anymore), because when workers are enabled, that's the Synapse `master` process and may not be serving all URL endpoints needed by the service."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1453
+msgid "Webserver configuration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1455
+msgid "if you're using `matrix-nginx-proxy` (`matrix_nginx_proxy_enabled: true`, which is the default for the playbook), you don't need to do anything"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1457
+msgid "if you're using your own `nginx` webserver running on the server, you shouldn't be affected. The `/matrix/nginx/conf.d` configuration and exposed ports that you're relying on will automatically be updated in a way that should work"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1459
+msgid "if you're using another local webserver (e.g. Apache, etc.) and haven't changed any ports (`matrix_*_host_bind_port` definitions), you shouldn't be affected. You're likely sending Matrix traffic to `127.0.0.1:8008` and `127.0.0.1:8048`. These ports (`8008` and `8048`) will still be exposed on `127.0.0.1` by default - just not by the `matrix-synapse` container from now on, but by the `matrix-synapse-reverse-proxy-companion` container instead"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1461
+msgid "if you've been exposing `matrix-synapse` ports (`matrix_synapse_container_client_api_host_bind_port`, etc.) manually, you should consider exposing `matrix-synapse-reverse-proxy-companion` ports instead"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1463
+msgid "if you're running Traefik and reverse-proxying directly to the `matrix-synapse` container, you should start reverse-proxying to the `matrix-synapse-reverse-proxy-companion` container instead. See [our updated Traefik example configuration](docs/configuring-playbook-own-webserver.md#sample-configuration-for-running-behind-traefik-20). Note: we now recommend calling the federation entry point `federation` (instead of `synapse`) and reverse-proxying the federation traffic via `matrix-nginx-proxy`, instead of sending it directly to Synapse (or `matrix-synapse-reverse-proxy-companion`). This makes the configuration simpler."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1466
+msgid "2022-11-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1468
+msgid "(Backward Compatibility Break) A new default standalone mode for Etherpad"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1470
+msgid "Until now, [Etherpad](https://etherpad.org/) (which [the playbook could install for you](docs/configuring-playbook-etherpad.md)) required the [Dimension integration manager](docs/configuring-playbook-dimension.md) to also be installed, because Etherpad was hosted on the Dimension domain (at `dimension.example.com/etherpad`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1472
+msgid "From now on, Etherpad can be installed in `standalone` mode on `etherpad.example.com` and used even without Dimension. This is much more versatile, so the playbook now defaults to this new mode (`etherpad_mode: standalone`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1474
+msgid "If you've already got both Etherpad and Dimension in use you could:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1476
+msgid "**either** keep hosting Etherpad under the Dimension domain by adding `etherpad_mode: dimension` to your `vars.yml` file. All your existing room widgets will continue working at the same URLs and no other changes will be necessary."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1478
+msgid "**or**, you could change to hosting Etherpad separately on `etherpad.example.com`. You will need to [configure a DNS record](docs/configuring-dns.md) for this new domain. You will also need to reconfigure Dimension to use the new pad URLs (`https://etherpad.example.com/…`) going forward (refer to our [configuring Etherpad documentation](docs/configuring-playbook-etherpad.md)). All your existing room widgets (which still use `https://dimension.example.com/etherpad/…`) will break as Etherpad is not hosted there anymore. You will need to re-add them or to consider not using `standalone` mode"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1481
+msgid "2022-11-04"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1483
+msgid "The playbook now uses external roles for some things"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1485
+msgid "**TLDR**: when updating the playbook and before running it, you'll need to run `make roles` to make [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) download dependency roles (see the [`requirements.yml` file](requirements.yml)) to the `roles/galaxy` directory. Without this, the playbook won't work."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1487
+msgid "We're in the process of trimming the playbook and making it reuse Ansible roles."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1489
+msgid "Starting now, the playbook is composed of 2 types of Ansible roles:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1491
+msgid "those that live within the playbook itself (`roles/custom/*`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1493
+msgid "those downloaded from other sources (using [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) to `roles/galaxy`, based on the [`requirements.yml` file](requirements.yml)). These roles are maintained by us or by other people from the Ansible community."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1495
+msgid "We're doing this for greater code-reuse (across Ansible playbooks, including our own related playbooks [gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) and [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)) and decreased maintenance burden. Until now, certain features were copy-pasted across playbooks or were maintained separately in each one, with improvements often falling behind. We've also tended to do too much by ourselves - installing Docker on the server from our `matrix-base` role, etc. - something that we'd rather not do anymore by switching to the [geerlingguy.docker](https://galaxy.ansible.com/geerlingguy/docker) role."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1497
+msgid "Some variable names will change during the transition to having more and more external (galaxy) roles. There's a new `custom/matrix_playbook_migration` role added to the playbook which will tell you about these changes each time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1499
+msgid "**From now on**, every time you update the playbook (well, every time the `requirements.yml` file changes), it's best to run `make roles` to update the roles downloaded from other sources. `make roles` is a shortcut (a `roles` target defined in [`Makefile`](Makefile) and executed by the [`make`](https://www.gnu.org/software/make/) utility) which ultimately runs [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) to download Ansible roles. If you don't have `make`, you can also manually run the commands seen in the `Makefile`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1502
+msgid "2022-10-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1504
+msgid "synapse-s3-storage-provider support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1506
+msgid "**`synapse-s3-storage-provider` support is very new and still relatively untested. Using it may cause data loss.**"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1508
+msgid "You can now store your Synapse media repository files on Amazon S3 (or another S3-compatible object store) using [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) - a media provider for Synapse (Python module), which should work faster and more reliably than our previous [Goofys](docs/configuring-playbook-s3-goofys.md) implementation (Goofys will continue to work)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1510
+msgid "This is not just for initial installations. Users with existing files (stored in the local filesystem) can also migrate their files to `synapse-s3-storage-provider`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1512
+msgid "To get started, see our [Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3-storage-provider.md) documentation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1514
+msgid "Synapse container image customization support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1516
+msgid "We now support customizing the Synapse container image by adding additional build steps to its [`Dockerfile`](https://docs.docker.com/engine/reference/builder/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1518
+msgid "Our [synapse-s3-storage-provider support](#synapse-s3-storage-provider-support) is actually built on this. When `s3-storage-provider` is enabled, we automatically add additional build steps to install its Python module into the Synapse image."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1520
+msgid "Besides this kind of auto-added build steps (for components supported by the playbook), we also let you inject your own custom build steps using configuration like this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1531
+msgid "People who have needed to customize Synapse previously had to fork the git repository, make their changes to the `Dockerfile` there, point the playbook to the new repository (`matrix_synapse_container_image_self_build_repo`) and enable self-building from scratch (`matrix_synapse_container_image_self_build: true`). This is harder and slower."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1533
+msgid "With the new Synapse-customization feature in the playbook, we use the original upstream (pre-built, if available) Synapse image and only build on top of it, right on the Matrix server. This is much faster than building all of Synapse from scratch."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1536
+msgid "2022-10-02"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1538
+msgid "matrix-ldap-registration-proxy support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1540
+msgid "Thanks to [@TheOneWithTheBraid](https://github.com/TheOneWithTheBraid), we now support installing [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) - a proxy which handles Matrix registration requests and forwards them to LDAP."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1542
+msgid "See our [Setting up matrix-ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1545
+msgid "2022-09-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1547
+msgid "(Potential Backward Compatibility Break) Major improvements to Synapse workers"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1549
+msgid "People who are interested in running a Synapse worker setup should know that **our Synapse worker implementation is much more powerful now**:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1551
+msgid "we've added support for [Stream writers](#stream-writers-support)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1552
+msgid "we've added support for [multiple federation sender workers](#multiple-federation-sender-workers-support)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1553
+msgid "we've added support for [multiple pusher workers](#multiple-pusher-workers-support)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1554
+msgid "we've added support for [running background tasks on a worker](#background-tasks-can-run-on-a-worker)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1555
+msgid "we've restored support for [`appservice` workers](#appservice-worker-support-is-back)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1556
+msgid "we've restored support for [`user_dir` workers](#user-directory-worker-support-is-back)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1557
+msgid "we've made it possible to [reliably use more than 1 `media_repository` worker](#using-more-than-1-media-repository-worker-is-now-more-reliable)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1558
+msgid "see the [Potential Backward Incompatibilities after these Synapse worker changes](#potential-backward-incompatibilities-after-these-synapse-worker-changes)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1560
+msgid "Stream writers support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1562
+msgid "From now on, the playbook lets you easily set up various [stream writer workers](https://matrix-org.github.io/synapse/latest/workers.html#stream-writers) which can handle different streams (`events` stream; `typing` URL endpoints, `to_device` URL endpoints, `account_data` URL endpoints, `receipts` URL endpoints, `presence` URL endpoints). All of this work was previously handled by the main Synapse process, but can now be offloaded to stream writer worker processes."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1564
+msgid "If you're using `matrix_synapse_workers_preset: one-of-each`, you'll automatically get 6 additional workers (one for each of the above stream types). Our `little-federation-helper` preset (meant to be quite minimal and focusing in improved federation performance) does not include stream writer workers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1566
+msgid "If you'd like to customize the number of workers we also make that possible using these variables:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1579
+msgid "Multiple federation sender workers support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1581
+msgid "Until now, we only supported a single `federation_sender` worker (`matrix_synapse_workers_federation_sender_workers_count` could either be `0` or `1`). From now on, you can have as many as you want to help with your federation traffic."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1583
+msgid "Multiple pusher workers support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1585
+msgid "Until now, we only supported a single `pusher` worker (`matrix_synapse_workers_pusher_workers_count` could either be `0` or `1`). From now on, you can have as many as you want to help with pushing notifications out."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1587
+msgid "Background tasks can run on a worker"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1589
+msgid "From now on, you can put [background task processing on a worker](https://matrix-org.github.io/synapse/latest/workers.html#background-tasks)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1591
+msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `background` worker automatically. You can also control the `background` workers count with `matrix_synapse_workers_background_workers_count`. Only  `0` or `1` workers of this type are supported by Synapse."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1593
+msgid "Appservice worker support is back"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1595
+msgid "We previously had an `appservice` worker type, which [Synapse deprecated in v1.59.0](https://github.com/element-hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-synapseappappservice-and-synapseappuser_dir-worker-application-types). So did we, at the time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1597
+msgid "The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of talking to Application Services. From now on, we have support for this."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1599
+msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `appservice` worker automatically. You can also control the `appservice` workers count with `matrix_synapse_workers_appservice_workers_count`. Only  `0` or `1` workers of this type are supported by Synapse."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1601
+msgid "User Directory worker support is back"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1603
+msgid "We previously had a `user_dir` worker type, which [Synapse deprecated in v1.59.0](https://github.com/element-hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-synapseappappservice-and-synapseappuser_dir-worker-application-types). So did we, at the time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1605
+msgid "The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of serving the user directory. From now on, we have support for this."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1607
+msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `user_dir` worker automatically. You can also control the `user_dir` workers count with `matrix_synapse_workers_user_dir_workers_count`. Only  `0` or `1` workers of this type are supported by Synapse."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1609
+msgid "Using more than 1 media repository worker is now more reliable"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1611
+msgid "With `matrix_synapse_workers_preset: one-of-each`, we only launch one `media_repository` worker."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1613
+msgid "If you've been configuring `matrix_synapse_workers_media_repository_workers_count` manually, you may have increased that to more workers. When multiple media repository workers are in use, background tasks related to the media repository must always be configured to run on a single `media_repository` worker via `media_instance_running_background_jobs`. Until now, we weren't doing this correctly, but we now are."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1615
+msgid "Potential Backward Incompatibilities after these Synapse worker changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1617
+msgid "Below we'll discuss **potential backward incompatibilities**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1619
+msgid "**Worker names** (container names, systemd services, worker configuration files) **have changed**. Workers are now labeled sequentially (e.g. `matrix-synapse-worker_generic_worker-18111` -> `matrix-synapse-worker-generic-0`). The playbook will handle these changes automatically."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1621
+msgid "Due to increased worker types support above, people who use `matrix_synapse_workers_preset: one-of-each` should be aware that with these changes, **the playbook will deploy 9 additional workers** (6 stream writers, 1 `appservice` worker, 1 `user_dir` worker, 1 background task worker). This **may increase RAM/CPU usage**, etc. If you find your server struggling, consider disabling some workers with the appropriate `matrix_synapse_workers_*_workers_count` variables."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1623
+msgid "**Metric endpoints have also changed** (`/metrics/synapse/worker/generic_worker-18111` -> `/metrics/synapse/worker/generic-worker-0`). If you're [collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server), consider revisiting our [Collecting Synapse worker metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-server) docs and updating your Prometheus configuration. **If you're collecting metrics to the integrated Prometheus server** (not enabled by default), **your Prometheus configuration will be updated automatically**. Old data (from before this change) may stick around though."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1625
+msgid "**the format of `matrix_synapse_workers_enabled_list` has changed**. You were never advised to use this variable for directly creating workers (we advise people to control workers using `matrix_synapse_workers_preset` or by tweaking `matrix_synapse_workers_*_workers_count` variables only), but some people may have started using the `matrix_synapse_workers_enabled_list` variable to gain more control over workers. If you're one of them, you'll need to adjust its value. See `roles/custom/matrix-synapse/defaults/main.yml` for more information on the new format. The playbook will also do basic validation and complain if you got something wrong."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1628
+msgid "2022-09-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1630
+msgid "Cactus Comments support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1632
+msgid "Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now set up [Cactus Comments](https://cactus.chat) - federated comment system for the web based on Matrix."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1634
+msgid "See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-comments.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1637
+msgid "2022-08-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1639
+msgid "Postmoogle email bridge support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1641
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the new [Postmoogle](https://github.com/etkecc/postmoogle) email bridge. Postmoogle is like the [email2matrix bridge](https://github.com/devture/email2matrix) (also [already supported by the playbook](docs/configuring-playbook-email2matrix.md)), but more capable and with the intention to soon support *sending* emails, not just receiving."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1643
+msgid "See our [Setting up Postmoogle email bridging](docs/configuring-playbook-bridge-postmoogle.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1646
+msgid "2022-08-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1648
+msgid "mautrix-whatsapp default configuration changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1650
+msgid "In [Pull Request #2012](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2012), we've made some changes to the default configuration used by the `mautrix-whatsapp` bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1652
+msgid "If you're using this bridge, you should look into this PR and see if the new configuration suits you. If not, you can always change individual preferences in your `vars.yml` file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1654
+msgid "Most notably, spaces support has been enabled by default. The bridge will now group rooms into a Matrix space. **If you've already bridged to Whatsapp** prior to this update, you will need to send `!wa sync space` to the bridge bot to make it create the space and put your existing rooms into it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1657
+msgid "2022-08-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1659
+msgid "Conduit support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1661
+msgid "Thanks to [Charles Wright](https://github.com/cvwright), we now have optional experimental [Conduit](https://conduit.rs) homeserver support for new installations. This comes as a follow-up to the playbook getting [Dendrite support](#dendrite-support) earlier this year."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1663
+msgid "Existing Synapse or Dendrite installations do **not** need to be updated. **Synapse is still the default homeserver implementation** installed by the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1665
+msgid "To try out Conduit, we recommend that you **use a new server** and the following `vars.yml` configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1671
+msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse or Dendrite to Conduit) without data loss."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1674
+msgid "2022-07-29"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1676
+msgid "mautrix-discord support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1678
+msgid "Thanks to [MdotAmaan](https://github.com/MdotAmaan)'s efforts, the playbook now supports bridging to [Discord](https://discordapp.com/) via the [mautrix-discord](https://mau.dev/mautrix/discord) bridge. See our [Setting up Mautrix Discord bridging](docs/configuring-playbook-bridge-mautrix-discord.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1680
+msgid "**Note**: this is a new Discord bridge. The playbook still retains Discord bridging via [matrix-appservice-discord](docs/configuring-playbook-bridge-appservice-discord.md) and [mx-puppet-discord](docs/configuring-playbook-bridge-mx-puppet-discord.md). You're free to use the bridge that serves you better, or even all three of them (for different users and use-cases)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1683
+msgid "2022-07-27"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1685
+msgid "matrix-appservice-kakaotalk support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1687
+msgid "The playbook now supports bridging to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) via [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) - a bridge based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code. Thanks to [hnarjis](https://github.com/hnarjis) for helping us add support for this!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1689
+msgid "See our [Setting up Appservice Kakaotalk bridging](docs/configuring-playbook-bridge-appservice-kakaotalk.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1692
+msgid "2022-07-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1694
+msgid "maubot support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1696
+msgid "Thanks to [Stuart Mumford (@Cadair)](https://github.com/cadair) for starting ([PR #373](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/373) and [PR #622](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/622)) and to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s) for finishing up (in [PR #1894](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1894)), the playbook can now help you set up [maubot](https://github.com/maubot/maubot) - a plugin-based Matrix bot system."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1698
+msgid "See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1701
+msgid "2022-07-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1703
+msgid "mx-puppet-skype removal"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1705
+msgid "The playbook no longer includes the [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge, because it has been broken and unmaintained for a long time. Users that have `matrix_mx_puppet_skype_enabled` in their configuration files will encounter an error when running the playbook until they remove references to this bridge from their configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1707
+msgid "To completely clean up your server from `mx-puppet-skype`'s presence on it:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1709
+msgid "ensure your Ansible configuration (`vars.yml` file) no longer contains `matrix_mx_puppet_skype_*` references"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1710
+msgid "stop and disable the systemd service (run `systemctl disable --now matrix-mx-puppet-skype` on the server)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1711
+msgid "delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-skype.service` on the server)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1712
+msgid "delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on the server)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1713
+msgid "drop the `matrix_mx_puppet_skype` database (run `/usr/local/bin/matrix-postgres-cli` on the server, and execute the `DROP DATABASE matrix_mx_puppet_skype;` query there)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1715
+msgid "If you still need bridging to [Skype](https://www.skype.com/), consider switching to [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) instead. See [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1717
+msgid "If you think this is a mistake and `mx-puppet-skype` works for you (or you get it to work somehow), let us know and we may reconsider this removal."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1719
+msgid "signald (0.19.0+) upgrade requires data migration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1721
+msgid "In [Pull Request #1921](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1921) we upgraded [signald](https://signald.org/) (used by the mautrix-signal bridge) from `v0.18.5` to `v0.20.0`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1723
+msgid "Back in the [`v0.19.0` released of signald](https://gitlab.com/signald/signald/-/blob/main/releases/0.19.0.md) (which we skipped and migrated straight to `v0.20.0`), a new `--migrate-data` command had been added that migrates avatars, group images, attachments, etc., into the database (those were previously stored in the filesystem)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1725
+msgid "If you've been using the mautrix-signal bridge for a while, you may have files stored in the local filesystem, which will need to be upgraded."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1727
+msgid "We attempt to do this data migration automatically every time Signald starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` systemd unit definition."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1729
+msgid "Keep an eye on your Signal bridge and let us know (in our [support room](README.md#support) or in [Pull Request #1921](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1921)) if you experience any trouble!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1732
+msgid "2022-07-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1734
+msgid "Ntfy push notifications support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1736
+msgid "Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the playbook can now install a [ntfy](https://ntfy.sh/) push notifications server for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1738
+msgid "See our [Setting up the ntfy push notifications server](docs/configuring-playbook-ntfy.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1741
+msgid "2022-06-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1743
+msgid "(Potential Backward Compatibility Break) Changes around metrics collection"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1745
+msgid "**TLDR**: we've made extensive **changes to metrics exposure/collection, which concern people using an external Prometheus server**. If you don't know what that is, you don't need to read below."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1747
+msgid "**Why do major changes to metrics**? Because various services were exposing metrics in different, hacky, ways. Synapse was exposing metrics at `/_synapse/metrics` and `/_synapse-worker-…/metrics` on the `matrix.example.com`. The Hookshot role was **repurposing** the Granana web UI domain (`stats.example.com`) for exposing its metrics on `stats.example.com/hookshot/metrics`, while protecting these routes using Basic Authentication **normally used for Synapse** (`/_synapse/metrics`). Node-exporter and Postgres-exporter roles were advising for more `stats.example.com` usage in manual ways. Each role was doing things differently and mixing variables from other roles. Each metrics endpoint was ending up in a different place, protected by who knows what Basic Authentication credentials (if protected at all)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1749
+msgid "**The solution**: a completely revamped way to expose metrics to an external Prometheus server. We are **introducing new `https://matrix.example.com/metrics/*` endpoints**, where various services *can* expose their metrics, for collection by external Prometheus servers. To enable the `/metrics/*` endpoints, use `matrix_nginx_proxy_proxy_matrix_metrics_enabled: true`. There's also a way to protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication). See the `matrix-nginx-proxy` role or our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation for additional variables around `matrix_nginx_proxy_proxy_matrix_metrics_enabled`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1751
+msgid "**If you are using the [Hookshot bridge](docs/configuring-playbook-bridge-hookshot.md)**, you may find that:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1752
+msgid "**Metrics may not be enabled by default anymore**:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1753
+msgid "If Prometheus is enabled (`prometheus_enabled: true`), then Hookshot metrics will be enabled automatically (`matrix_hookshot_metrics_enabled: true`). These metrics will be collected from the local (in-container) Prometheus over the container network."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1754
+msgid "**If Prometheus is not enabled** (you are either not using Prometheus or are using an external one), **Hookshot metrics will not be enabled by default anymore**. Feel free to enable them by setting `matrix_hookshot_metrics_enabled: true`. Also, see below."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1755
+msgid "When metrics are meant to be **consumed by an external Prometheus server**, `matrix_hookshot_metrics_proxying_enabled` needs to be set to `true`, so that metrics would be exposed (proxied) \"publicly\" on `https://matrix.example.com/metrics/hookshot`. To make use of this, you'll also need to enable the new `https://matrix.example.com/metrics/*` endpoints mentioned above, using `matrix_nginx_proxy_proxy_matrix_metrics_enabled`. Learn more in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1756
+msgid "**We've changed the URL we're exposing Hookshot metrics at** for external Prometheus servers. Until now, you were advised to consume Hookshot metrics from `https://stats.example.com/hookshot/metrics` (working in conjunction with `matrix_nginx_proxy_proxy_synapse_metrics`). From now on, **this no longer works**. As described above, you need to start consuming metrics from `https://matrix.example.com/metrics/hookshot`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1758
+msgid "**If you're using node-exporter** (`matrix_prometheus_node_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_node_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/node-exporter`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1760
+msgid "**If you're using [postgres-exporter](docs/configuring-playbook-prometheus-postgres.md)** (`prometheus_postgres_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/postgres-exporter`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1762
+msgid "**If you're using Synapse** and would like to collect its metrics from an external Prometheus server, you may find that:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1764
+msgid "Exposing metrics is now done using `matrix_synapse_metrics_proxying_enabled`, not `matrix_nginx_proxy_proxy_synapse_metrics: true`. You may still need to enable metrics using `matrix_synapse_metrics_enabled: true` before exposing them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1765
+msgid "Protecting metrics endpoints using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) is now done in another way. See our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1766
+msgid "If Synapse metrics are exposed, they will be made available at `https://matrix.example.com/metrics/synapse/main-process` or `https://matrix.example.com/metrics/synapse/worker/TYPE-ID` (when workers are enabled), not at `https://matrix.example.com/_synapse/metrics` and `https://matrix.example.com/_synapse-worker-…/metrics`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1767
+msgid "The playbook still generates an `external_prometheus.yml.example` sample file for scraping Synapse from Prometheus as described in [Collecting Synapse worker metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-server), but it's now saved under `/matrix/synapse` (not `/matrix`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1769
+msgid "**If you where already using a external Prometheus server** before this change, and you gave a hashed version of the password as a variable, the playbook will now take care of hashing the password for you. Thus, you need to provide the non-hashed version now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1771
+msgid "2022-06-13"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1773
+msgid "go-skype-bridge bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1775
+msgid "Thanks to [CyberShadow](https://github.com/CyberShadow), the playbook can now install the [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) bridge for bridging Matrix to [Skype](https://www.skype.com/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1777
+msgid "See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1779
+msgid "The playbook has supported [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridging (see [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md)) since [2020-04-09](#2020-04-09), but `mx-puppet-skype` is reportedly broken."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1782
+msgid "2022-06-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1784
+msgid "Running Ansible in a container can now happen on the Matrix server itself"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1786
+msgid "If you're tired of being on an old and problematic Ansible version, you can now run [run Ansible in a container on the Matrix server itself](docs/ansible.md#running-ansible-in-a-container-on-the-matrix-server-itself)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1789
+msgid "2022-05-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1791
+msgid "Synapse v1.60 upgrade may cause trouble and require manual intervention"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1793
+msgid "Synapse v1.60 will try to add a new unique index to `state_group_edges` upon startup and could fail if your database is corrupted."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1795
+msgid "We haven't observed this problem yet, but [the Synapse v1.60.0 upgrade notes](https://github.com/element-hq/synapse/blob/v1.60.0/docs/upgrade.md#adding-a-new-unique-index-to-state_group_edges-could-fail-if-your-database-is-corrupted) mention it, so we're giving you a heads up here in case you're unlucky."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1797
+msgid "**If Synapse fails to start** after your next playbook run, you'll need to:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1799
+msgid "SSH into the Matrix server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1800
+msgid "launch `/usr/local/bin/matrix-postgres-cli`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1801
+msgid "switch to the `synapse` database: `\\c synapse`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1802
+msgid "run the following SQL query:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1821
+msgid "You could then restart services: `ansible-playbook -i inventory/hosts setup.yml --tags=start`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1824
+msgid "2022-04-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1826
+msgid "Buscarron bot support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1828
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [the Buscarron bot](https://github.com/etkecc/buscarron). It's a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1830
+msgid "See our [Setting up Buscarron](docs/configuring-playbook-bot-buscarron.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1833
+msgid "2022-04-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1835
+msgid "matrix-registration-bot support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1837
+msgid "Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now help you set up [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) - a bot that is used to create and manage registration tokens for a Matrix server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1839
+msgid "See our [Setting up matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1842
+msgid "2022-04-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1844
+msgid "BorgBackup support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1846
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [Borg](https://www.borgbackup.org/) backups with [borgmatic](https://torsion.org/borgmatic/) of your Matrix server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1848
+msgid "See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1850
+msgid "(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1852
+msgid "If you're running a worker setup for Synapse (`matrix_synapse_workers_enabled: true`), the [Synapse v1.57 upgrade notes](https://github.com/element-hq/synapse/blob/v1.57.0rc1/docs/upgrade.md#changes-to-database-schema-for-application-services) say that you may need to take special care when upgrading:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1854
+msgid "Synapse v1.57.0 includes a change to the way transaction IDs are managed for application services. If your deployment uses a dedicated worker for application service traffic, **it must be stopped** when the database is upgraded (which normally happens when the main process is upgraded), to ensure the change is made safely without any risk of reusing transaction IDs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1856
+msgid "If you're not running an `appservice` worker (`matrix_synapse_workers_preset: little-federation-helper` or `matrix_synapse_workers_appservice_workers_count: 0`), you are probably safe to upgrade as per normal, without taking any special care."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1858
+msgid "If you are running a setup with an `appservice` worker, or otherwise want to be on the safe side, we recommend the following upgrade path:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1860
+msgid "Pull the latest playbook changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1861
+msgid "Stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1862
+msgid "Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1863
+msgid "Start Postgres (`systemctl start matrix-postgres` on the server)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1864
+msgid "Start the main Synapse process (`systemctl start matrix-synapse` on the server)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1865
+msgid "Wait a while so that Synapse can start and complete the database migrations. You can use `journalctl -fu matrix-synapse` on the server to get a clue. Waiting a few minutes should also be enough."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1866
+msgid "It should now be safe to start all other services. `ansible-playbook -i inventory/hosts setup.yml --tags=start` will do it for you"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1869
+msgid "2022-04-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1871
+msgid "(Compatibility Break) Changes to `docker-src` permissions necessitating manual action"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1873
+msgid "Users who build container images from source will need to manually correct file permissions of some directories on the server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1875
+msgid "When self-building, the playbook used to `git clone` repositories (into `/matrix/SERVICE/docker-src`) using the `root` user, but now uses `matrix` instead to work around [the following issue with git 2.35.2](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1749)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1877
+msgid "If you're on a non-`amd64` architecture (that is, you're overriding `matrix_architecture` in your `vars.yml` file) or you have enabled self-building for some service (e.g. `matrix_*_self_build: true`), you're certainly building some container images from source and have `docker-src` directories with mixed permissions lying around in various `/matrix/SERVICE` directories."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1879
+msgid "The playbook *could* correct these permissions automatically, but that requires additional Ansible tasks in some ~45 different places - something that takes considerable effort. So we ask users observing errors related to `docker-src` directories to correct the problem manually by **running this command on the Matrix server** (which deletes all `/matrix/*/docker-src` directories): `find /matrix -maxdepth 2 -name 'docker-src' | xargs rm -rf`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1882
+msgid "2022-03-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1884
+msgid "(Compatibility Break) ma1sd identity server no longer installed by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1886
+msgid "The playbook no longer installs the [ma1sd](https://github.com/ma1uta/ma1sd) identity server by default. The next time you run the playbook, ma1sd will be uninstalled from your server, unless you explicitly enable the ma1sd service (see how below)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1888
+msgid "The main reason we used to install ma1sd by default in the past was to prevent Element clients from talking to the `matrix.org` / `vector.im` identity servers, by forcing it to talk to our own self-hosted (but otherwise useless) identity server instead, thus preventing contact list leaks."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1890
+msgid "Since Element clients no longer default to using a public identity server if another one is not provided, we can stop installing ma1sd."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1892
+msgid "If you need to install the ma1sd identity server for some reason, you can explicitly enable it by adding this to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1899
+msgid "2022-02-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1901
+msgid "matrix_encryption_disabler support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1903
+msgid "We now support installing the [matrix_encryption_disabler](https://github.com/digitalentity/matrix_encryption_disabler) Synapse module, which lets you prevent End-to-End-Encryption from being enabled by users on your homeserver. The popular opinion is that this is dangerous and shouldn't be done, but there are valid use cases for disabling encryption discussed [here](https://github.com/matrix-org/synapse/issues/4401)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1905
+msgid "To enable this module (and prevent encryption from being used on your homserver), add `matrix_synapse_ext_encryption_disabler_enabled: true` to your configuration. This module provides further customization. Check its other configuration settings (and defaults) in `roles/custom/matrix-synapse/defaults/main.yml`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1908
+msgid "2022-02-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1910
+msgid "matrix-hookshot bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1912
+msgid "Thanks to [HarHarLinks](https://github.com/HarHarLinks), the playbook can now install the [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) bridge for bridging Matrix to multiple project management services, such as GitHub, GitLab and JIRA. See our [Setting up matrix-hookshot](docs/configuring-playbook-bridge-hookshot.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1915
+msgid "2022-01-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1917
+msgid "ARM support for matrix-corporal"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1919
+msgid "[matrix-corporal](https://github.com/devture/matrix-corporal) (as of version `2.2.3`) is now published to Docker Hub (see [devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-corporal)) as a multi-arch container image with support for all these platforms: `linux/amd64`, `linux/arm64/v8` and `linux/arm/v7`. The playbook no longer resorts to self-building matrix-corporal on these ARM architectures."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1922
+msgid "2022-01-07"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1924
+msgid "Dendrite support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1926
+msgid "**TLDR**: We now have optional experimental [Dendrite](https://github.com/matrix-org/dendrite) homeserver support for new installations. **Existing (Synapse) installations need to be updated**, because some internals changed. See [Adapting the configuration for existing Synapse installations](#adapting-the-configuration-for-existing-synapse-installations)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1928
+msgid "[Jip J. Dekker](https://github.com/Dekker1) did the [initial work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/818) of adding [Dendrite](https://github.com/matrix-org/dendrite) support to the playbook back in January 2021. Lots of work (and time) later, Dendrite support is finally ready for testing."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1930
+msgid "We believe that 2022 will be the year of the non-Synapse Matrix server!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1932
+msgid "The playbook was previously quite [Synapse](https://github.com/element-hq/synapse)-centric, but can now accommodate multiple homeserver implementations. Only one homeserver implementation can be active (installed) at a given time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1934
+msgid "**Synapse is still the default homeserver implementation** installed by the playbook. A new variable (`matrix_homeserver_implementation`) controls which server implementation is enabled (`synapse` or `dendrite` at the given moment)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1936
+msgid "Adapting the configuration for existing Synapse installations"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1938
+msgid "Because the playbook is not so Synapse-centric anymore, a small configuration change is necessary for existing installations to bring them up to date."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1940
+msgid "The `vars.yml` file for **existing installations will need to be updated** by adding this **additional configuration**:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1952
+msgid "Trying out Dendrite"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1954
+msgid "Finally, **to try out Dendrite**, we recommend that you **use a new server** and the following addition to your `vars.yml` configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1960
+msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse to Dendrite) without data loss."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1962
+msgid "We're excited to gain support for other homeserver implementations, like [Conduit](https://conduit.rs/), etc!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1964
+msgid "Honoroit bot support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1966
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now help you set up [Honoroit](https://github.com/etkecc/honoroit) - a helpdesk bot."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1968
+msgid "See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1971
+msgid "2022-01-06"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1973
+msgid "Cinny support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1975
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports [Cinny](https://cinny.in/) - a new simple, elegant and secure Matrix client."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1977
+msgid "By default, we still install Element Web. Still, people who'd like to try Cinny out can now install it via the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1979
+msgid "Additional details are available in [Setting up Cinny](docs/configuring-playbook-client-cinny.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1982
+msgid "2021-12-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1984
+msgid "Twitter bridging support via mautrix-twitter"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1986
+msgid "Thanks to [Matthew Cengia](https://github.com/mattcen) and [Shreyas Ajjarapu](https://github.com/shreyasajj), besides [mx-puppet-twitter](docs/configuring-playbook-bridge-mx-puppet-twitter.md), bridging to [Twitter](https://twitter.com/) can now also happen with [mautrix-twitter](docs/configuring-playbook-bridge-mautrix-twitter.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1989
+msgid "2021-12-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1991
+msgid "(Security) Users of the Signal bridge may wish to upgrade it to work around log4j vulnerability"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1993
+msgid "Recently, a security vulnerability affecting the Java logging package `log4j` [has been discovered](https://www.huntress.com/blog/rapid-response-critical-rce-vulnerability-is-affecting-java). Software that uses this Java package is potentially vulnerable."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1995
+msgid "One such piece of software that is part of the playbook is the [mautrix-signal bridge](./docs/configuring-playbook-bridge-mautrix-signal.md), which [has been patched already](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1452). If you're running this bridge, you may wish to [upgrade](./docs/maintenance-upgrading-services.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1998
+msgid "2021-11-11"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2000
+msgid "Dropped support for Postgres v9.6"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2002
+msgid "Postgres v9.6 reached its end of life today, so the playbook will refuse to run for you if you're still on that version."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2004
+msgid "Synapse still supports v9.6 (for now), but we're retiring support for it early, to avoid having to maintain support for so many Postgres versions. Users that are still on Postgres v9.6 can easily [upgrade Postgres](docs/maintenance-postgres.md#upgrading-postgresql) via the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2007
+msgid "2021-10-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2009
+msgid "Hangouts bridge no longer updated, superseded by a Googlechat bridge"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2011
+msgid "The mautrix-hangouts bridge is no longer receiving updates upstream and is likely to stop working in the future. We still retain support for this bridge in the playbook, but you're encouraged to switch away from it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2013
+msgid "There's a new [mautrix-googlechat](https://github.com/mautrix/googlechat) bridge that you can [install using the playbook](docs/configuring-playbook-bridge-mautrix-googlechat.md). Your **Hangouts bridge data will not be migrated**, however. You need to start fresh with the new bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2016
+msgid "2021-08-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2018
+msgid "LinkedIn bridging support via beeper-linkedin"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2020
+msgid "Thanks to [Alexandar Mechev](https://github.com/apmechev), the playbook can now install the [beeper-linkedin](https://gitlab.com/beeper/linkedin) bridge for bridging to [LinkedIn](https://www.linkedin.com/) Messaging."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2022
+msgid "This brings the total number of bridges supported by the playbook up to 20. See all supported bridges [here](docs/configuring-playbook.md#bridging-other-networks)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2024
+msgid "To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2027
+msgid "2021-08-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2029
+msgid "Sygnal upgraded - ARM support and no longer requires a database"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2031
+msgid "The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been upgraded from `v0.9.0` to `v0.10.1`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2033
+msgid "This is an optional component for the playbook, so most of our users wouldn't care about this announcement."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2035
+msgid "Since this feels like a relatively big (and untested, as of yet) Sygnal change, we're putting up this changelog entry."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2037
+msgid "The new version is also available for the ARM architecture. It also no longer requires a database anymore. If you need to downgrade to the previous version, changing `matrix_sygnal_version` or `matrix_sygnal_docker_image` will not be enough, as we've removed the `database` configuration completely. You'd need to switch to an earlier playbook commit."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2040
+msgid "2021-05-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2042
+msgid "Hydrogen support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2044
+msgid "Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook now supports [Hydrogen](https://github.com/vector-im/hydrogen-web) - a new lightweight Matrix client with legacy and mobile browser support."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2046
+msgid "By default, we still install Element Web, as Hydrogen is still not fully-featured. Still, people who'd like to try Hydrogen out can now install it via the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2048
+msgid "Additional details are available in [Setting up Hydrogen](docs/configuring-playbook-client-hydrogen.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2051
+msgid "2021-05-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2053
+msgid "Heisenbridge support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2055
+msgid "Thanks to [Toni Spets (hifi)](https://github.com/hifi), the playbook now supports bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) using yet another bridge (besides matrix-appservice-irc), called [Heisenbridge](https://github.com/hifi/heisenbridge)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2057
+msgid "Additional details are available in [Setting up Heisenbridge bouncer-style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2060
+msgid "2021-04-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2062
+msgid "Disabling TLSv1 and TLSv1.1 for Coturn"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2064
+msgid "To improve security, we've [removed TLSv1 and TLSv1.1 support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/999) from our default [Coturn](https://github.com/coturn/coturn) configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2066
+msgid "If you need to support old clients, you can re-enable both (or whichever one you need) with the following configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2074
+msgid "2021-04-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2076
+msgid "Automated local Postgres backup support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2078
+msgid "Thanks to [foxcris](https://github.com/foxcris), the playbook can now make automated local Postgres backups on a fixed schedule using [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2080
+msgid "Additional details are available in [Setting up postgres backup](docs/configuring-playbook-postgres-backup.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2083
+msgid "2021-04-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2085
+msgid "Mjolnir moderation tool (bot) support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2087
+msgid "Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook can now install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation tool (bot)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2089
+msgid "Additional details are available in [Setting up Mjolnir](docs/configuring-playbook-bot-mjolnir.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2092
+msgid "2021-03-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2094
+msgid "Sygnal push gateway support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2096
+msgid "The playbook can now install the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2098
+msgid "This is only useful to people who develop/build their own Matrix client applications."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2100
+msgid "Additional details are available in our [Setting up the Sygnal push gateway](docs/configuring-playbook-sygnal.md) docs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2103
+msgid "2021-03-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2105
+msgid "Go-NEB support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2107
+msgid "Thanks to [Zir0h](https://github.com/Zir0h), the playbook can now install and configure the [Go-NEB](https://github.com/matrix-org/go-neb) bot."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2109
+msgid "Additional details are available in [Setting up Go-NEB](docs/configuring-playbook-bot-go-neb.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2112
+msgid "2021-02-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2114
+msgid "GroupMe bridging support via mx-puppet-groupme"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2116
+msgid "Thanks to [Cody Neiman](https://github.com/xangelix), the playbook can now install the [mx-puppet-groupme](https://gitlab.com/robintown/mx-puppet-groupme) bridge for bridging to [GroupMe](https://groupme.com)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2118
+msgid "This brings the total number of bridges supported by the playbook up to 18. See all supported bridges [here](docs/configuring-playbook.md#bridging-other-networks)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2120
+msgid "To get started, follow our [Setting up MX Puppet GroupMe](docs/configuring-playbook-bridge-mx-puppet-groupme.md) docs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2122
+msgid "Mautrix Instagram bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2124
+msgid "The playbook now supports bridging with [Instagram](https://www.instagram.com/) by installing the [mautrix-instagram](https://github.com/tulir/mautrix-instagram) bridge. This playbook functionality is available thanks to [@MarcProe](https://github.com/MarcProe)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2126
+msgid "Additional details are available in [Setting up Mautrix Instagram bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2128
+msgid "Synapse workers support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2130
+msgid "After [lots and lots of work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/456) (done over many months by [Marcel Partap](https://github.com/eMPee584), [Max Klenk](https://github.com/maxklenk), a few others from the [Technical University of Dresden, Germany](https://tu-dresden.de/) and various other contributors), support for Synapse workers has finally landed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2132
+msgid "Having support for workers makes the playbook suitable for larger homeserver deployments."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2134
+msgid "Our setup is not yet perfect (we don't support all types of workers; scaling some of them (like `pusher`, `federation_sender`) beyond a single instance is not yet supported). Still, it's a great start and can already power homeservers with thousands of users, like the [Matrix deployment at TU Dresden](https://doc.matrix.tu-dresden.de/en/) discussed in [Matrix Live S06E09 - TU Dresden on their Matrix deployment](https://www.youtube.com/watch?v=UHJX2pmT2gk)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2136
+msgid "By default, workers are disabled and Synapse runs as a single process (homeservers don't necessarily need the complexity and increased memory requirements of running a worker-based setup)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2138
+msgid "To enable Synapse workers, follow our [Load balancing with workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) documentation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2141
+msgid "2021-02-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2143
+msgid "(Potential Breaking Change) Monitoring/metrics support using Prometheus and Grafana"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2145
+msgid "Thanks to [@Peetz0r](https://github.com/Peetz0r), the playbook can now install a bunch of tools for monitoring your Matrix server: the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2147
+msgid "To get get these installed, follow our [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](docs/configuring-playbook-prometheus-grafana.md) docs page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2149
+msgid "This update comes with a **potential breaking change** for people who were already exposing Synapse metrics (for consumption via another Prometheus installation). From now on, `matrix_synapse_metrics_enabled: true` no longer exposes metrics publicly via matrix-nginx-proxy (at `https://matrix.example.com/_synapse/metrics`). To do so, you'd need to explicitly set `matrix_nginx_proxy_proxy_synapse_metrics: true`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2152
+msgid "2021-01-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2154
+msgid "Etherpad support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2156
+msgid "Thanks to [@pushytoxin](https://github.com/pushytoxin), the playbook can now install the [Etherpad](https://etherpad.org) realtime collaborative text editor. It can be used in a [Jitsi](https://jitsi.org/) audio/video call or integrated as a widget into Matrix chat rooms via the [Dimension](https://dimension.t2bot.io) integration manager."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2158
+msgid "To get it installed, follow [our Etherpad docs page](docs/configuring-playbook-etherpad.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2161
+msgid "2021-01-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2163
+msgid "(Breaking Change) Postgres changes that require manual intervention"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2165
+msgid "We've made a lot of changes to our Postgres setup and some manual action is required (described below). Sorry about the hassle."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2167
+msgid "**TLDR**: people running an [external Postgres server](docs/configuring-playbook-external-postgres.md) don't need to change anything for now. Everyone else (the common/default case) is affected and manual intervention is required."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2169
+msgid "Why?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2171
+msgid "we had a default Postgres password (`matrix_postgres_connection_password: synapse-password`), which we think is **not ideal for security anymore**. We now ask you to generate/provide a strong password yourself. Postgres is normally not exposed outside the container network, making it relatively secure, but still:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2172
+msgid "by tweaking the configuration, you may end up intentionally or unintentionally exposing your Postgres server to the local network (or even publicly), while still using the default default credentials (`synapse` + `synapse-password`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2173
+msgid "we can't be sure we trust all these services (bridges, etc). Some of them may try to talk to or attack `matrix-postgres` using the default credentials (`synapse` + `synapse-password`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2174
+msgid "you may have other containers running on the same Docker network, which may try to talk to or attack `matrix-postgres` using the default credentials (`synapse` + `synapse-password`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2175
+msgid "our Postgres usage **was overly-focused on Synapse** (default username of `synapse` and default/main database of `homeserver`). Additional homeserver options are likely coming in the future ([Dendrite](https://matrix.org/docs/projects/server/dendrite), [Conduit](https://matrix.org/docs/projects/server/conduit), [The Construct](https://matrix.org/docs/projects/server/construct)), so being too focused on `matrix-synapse` is not great. From now on, Synapse is just another component of this playbook, which happens to have an *additional database* (called `synapse`) on the Postgres server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2176
+msgid "we try to reorganize things a bit, to make the playbook even friendlier to people running an [external Postgres server](docs/configuring-playbook-external-postgres.md). Work on this will proceed in the future."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2178
+msgid "So, this is some **effort to improve security** and to **prepare for a brighter future of having more homeserver options** than just Synapse."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2180
+msgid "What has really changed?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2182
+msgid "the default superuser Postgres username is now `matrix` (used to be `synapse`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2183
+msgid "the default Postgres database is now `matrix` (used to be `homeserver`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2184
+msgid "Synapse's database is now `synapse` (used to be `homeserver`). This is now just another \"additional database\" that the playbook manages for you"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2185
+msgid "Synapse's user called `synapse` is just a regular user that can only use the `synapse` database (not a superuser anymore)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2187
+msgid "What do I do if I'm using the integrated Postgres server (default)?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2189
+msgid "By default, the playbook runs an integrated Postgres server for you in a container (`matrix-postgres`). Unless you've explicitly configured an [external Postgres server](docs/configuring-playbook-external-postgres.md), these steps are meant for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2191
+msgid "To migrate to the new setup, expect a few minutes of downtime, while you follow these steps:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2193
+msgid "We believe the steps below are safe and you won't encounter any data loss, but consider [making a Postgres backup](docs/maintenance-postgres.md#backing-up-postgresql) anyway. If you've never backed up Postgres, now would be a good time to try it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2195
+msgid "Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can create one with a command like `pwgen -s 64 1`. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2197
+msgid "Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` file, adding a line like this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2202 ../../../CHANGELOG.md:2214
+msgid ".. where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2204
+msgid "Stop all services: `ansible-playbook -i inventory/hosts setup.yml --tags=stop`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2205
+msgid "Log in to the server via SSH. The next commands will be performed there."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2206
+msgid "Start the Postgres database server: `systemctl start matrix-postgres`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2207
+msgid "Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2208
+msgid "Execute the following query, while making sure to **change the password inside** (**don't forget the ending `;`**):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2216
+msgid "Execute the following queries as you see them (no modifications necessary, so you can just **paste them all at once**):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2234
+msgid "You may need to press *Enter* after pasting the lines above."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2236
+msgid "Re-run the playbook normally: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2238
+msgid "What do I do if I'm using an external Postgres server?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2240
+msgid "If you've explicitly configured an [external Postgres server](docs/configuring-playbook-external-postgres.md), there are **no changes** that you need to do at this time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2242
+msgid "The fact that we've renamed Synapse's database from `homeserver` to `synapse` (in our defaults) should not affect you, as you're already explicitly defining `matrix_synapse_database_database` (if you've followed our guide, that is). If you're not explicitly defining this variable, you may wish to do so (`matrix_synapse_database_database: homeserver`), to avoid the new `synapse` default and keep things as they were."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2245
+msgid "2021-01-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2247
+msgid "(Breaking Change) The mautrix-facebook bridge now requires a Postgres database"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2249
+msgid "**Update from 2021-11-15**: SQLite support has been re-added to the mautrix-facebook bridge in [v0.3.2](https://github.com/mautrix/facebook/releases/tag/v0.3.2). You can ignore this changelog entry."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2251
+msgid "A new version of the [mautrix-facebook](https://github.com/tulir/mautrix-facebook) bridge has been released. It's a full rewrite of its backend and the bridge now requires Postgres. New versions of the bridge can no longer run on SQLite."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2253
+msgid "**TLDR**: if you're NOT using an [external Postgres server](docs/configuring-playbook-external-postgres.md) and have NOT forcefully kept the bridge on SQLite during [The big move to all-on-Postgres (potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous), you will be automatically upgraded without manual intervention. All you need to do is send a `login` message to the Facebook bridge bot again."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2255
+msgid "Whether this change requires your intervention depends mostly on:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2256
+msgid "whether you're using an [external Postgres server](docs/configuring-playbook-external-postgres.md). If yes, then [you need to do something](#upgrade-path-for-people-running-an-external-postgres-server)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2257
+msgid "or whether you've force-changed the bridge's database engine to SQLite (`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) some time in the past (likely during [The big move to all-on-Postgres (potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2259
+msgid "As already mentioned above, you most likely don't need to do anything. If you rerun the playbook and don't get an error, you've been automatically upgraded. Just send a `login` message to the Facebook bridge bot again. Otherwise, read below for a solution."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2261
+msgid "Upgrade path for people NOT running an external Postgres server (default for the playbook)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2263
+msgid "If you're **not running an external Postgres server**, then this bridge either already works on Postgres for you, or you've intentionally kept it back on SQLite with custom configuration (`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) ."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2265
+msgid "Simply remove that custom configuration from your `vars.yml` file (if it's there) and re-run the playbook. It should upgrade you automatically. You'll need to send a `login` message to the Facebook bridge bot again."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2267
+msgid "Alternatively, [you can stay on SQLite for a little longer](#staying-on-sqlite-for-a-little-longer-temporary-solution)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2269
+msgid "Upgrade path for people running an external Postgres server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2271
+msgid "For people using the internal Postgres server (the default for the playbook):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2272
+msgid "we automatically create an additional `matrix_mautrix_facebook` Postgres database and credentials to access it"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2273
+msgid "we automatically adjust the bridge's `matrix_mautrix_facebook_database_*` variables to point the bridge to that Postgres database"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2274
+msgid "we use [pgloader](https://pgloader.io/) to automatically import the existing SQLite data for the bridge into the `matrix_mautrix_facebook` Postgres database"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2276
+msgid "If you are using an [external Postgres server](docs/configuring-playbook-external-postgres.md), unfortunately we currently can't do any of that for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2278
+msgid "You have 3 ways to proceed:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2280
+msgid "contribute to the playbook to make this possible (difficult)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2281
+msgid "or, do the migration \"steps\" manually:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2282
+msgid "stop the bridge (`systemctl stop matrix-mautrix-facebook`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2283
+msgid "create a new `matrix_mautrix_facebook` Postgres database for it"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2284
+msgid "run [pgloader](https://pgloader.io/) manually (we import this bridge's data using default settings and it works well)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2285
+msgid "define `matrix_mautrix_facebook_database_*` variables in your `vars.yml` file (credentials, etc.) - you can find their defaults in `roles/custom/matrix-mautrix-facebook/defaults/main.yml`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2286
+msgid "switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: 'postgres'` in your `vars.yml` file)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2287
+msgid "re-run the playbook (`--tags=setup-all,start`) and ensure the bridge works (`systemctl status matrix-mautrix-facebook` and `journalctl -fu matrix-mautrix-facebook`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2288
+msgid "send a `login` message to the Facebook bridge bot again"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2289
+msgid "or, [stay on SQLite for a little longer (temporary solution)](#staying-on-sqlite-for-a-little-longer-temporary-solution)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2291
+msgid "Staying on SQLite for a little longer (temporary solution)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2293
+msgid "To keep using this bridge with SQLite for a little longer (**not recommended**), use the following configuration in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2303
+msgid "If you do this, keep in mind that **you can't run this forever**. This SQLite-supporting bridge version is not getting any updates and will break sooner or later. The playbook will also drop support for SQLite at some point in the future."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2306
+msgid "2021-01-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2308
+msgid "matrix-corporal goes 2.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2310
+msgid "[matrix-corporal v2 has been released](https://github.com/devture/matrix-corporal/releases/tag/2.0.0) and the playbook also supports it now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2312
+msgid "No manual intervention is required in the common case."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2314
+msgid "The new [matrix-corporal](https://github.com/devture/matrix-corporal) version is also the first one to support Interactive Authentication. If you wish to enable that (hint: you should), you'll need to set up the [REST auth password provider](docs/configuring-playbook-rest-auth.md). There's more information in [our matrix-corporal docs](docs/configuring-playbook-matrix-corporal.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2317
+msgid "2021-01-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2319
+msgid "Moving from cronjobs to systemd timers"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2321
+msgid "We no longer use cronjobs for Let's Encrypt SSL renewal and `matrix-nginx-proxy`/`matrix-coturn` reloading. Instead, we've switched to systemd timers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2323
+msgid "The largest benefit of this is that we no longer require you to install a cron daemon, thus simplifying our install procedure."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2325
+msgid "The playbook will migrate you from cronjobs to systemd timers automatically. This is just a heads up."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2328
+msgid "2021-01-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2330
+msgid "(Breaking Change) New SSL configuration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2332
+msgid "SSL configuration (protocols, ciphers) can now be more easily controlled thanks to us making use of configuration presets."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2334
+msgid "We define a few presets (old, intermediate, modern), following the [Mozilla SSL Configuration Generator](https://ssl-config.mozilla.org/#server=nginx)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2336
+msgid "A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is used (defaults to `\"intermediate\"`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2338
+msgid "Compared to before, this changes nginx's `ssl_prefer_server_ciphers` to `off`  (used to default to `on`). It also add some more ciphers to the list, giving better performance on mobile devices, and removes some weak ciphers. More information in the [documentation](docs/configuring-playbook-nginx.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2340
+msgid "To revert to the old behaviour, set the following variables:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2347
+msgid "Just like before, you can still use your own custom protocols by specifying them in `matrix_nginx_proxy_ssl_protocols`. Doing so overrides the values coming from the preset."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2350
+msgid "2021-01-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2352
+msgid "Signal bridging support via mautrix-signal"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2354
+msgid "Thanks to [laszabine](https://github.com/laszabine)'s efforts, the playbook now supports bridging to [Signal](https://www.signal.org/) via the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge. See our [Setting up Mautrix Signal bridging](docs/configuring-playbook-bridge-mautrix-signal.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2356
+msgid "If you had installed the mautrix-signal bridge while its Pull Request was still work-in-progress, you can migrate your data to the new and final setup by referring to [this comment](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/686#issuecomment-753510789)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2359
+msgid "2020-12-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2361
+msgid "The big move to all-on-Postgres (potentially dangerous)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2363
+msgid "**TLDR**: all your bridges (and other services) will likely be auto-migrated from SQLite/nedb to Postgres, hopefully without trouble. You can opt-out (see how below), if too worried about breakage."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2365
+msgid "Until now, we've only used Postgres as a database for Synapse. All other services (bridges, bots, etc.) were kept simple and used a file-based database (SQLite or nedb)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2367
+msgid "Since [this huge pull request](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/740), **all of our services now use Postgres by default**. Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann) for starting the work on it and for providing great input!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2369
+msgid "Moving all services to Postgres brings a few **benefits** to us:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2371
+msgid "**improved performance**"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2372
+msgid "**improved compatibility**. Most bridges are deprecating SQLite/nedb support or offer less features when not on Postgres."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2373
+msgid "**easier backups**. It's still some effort to take a proper backup (Postgres dump + various files, keys), but a Postgres dump now takes you much further."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2374
+msgid "we're now **more prepared to introduce other services** that need a Postgres database - [Dendrite](https://github.com/matrix-org/dendrite), the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge (existing [pull request](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/686)), etc."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2376
+msgid "Key takeway"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2378
+msgid "existing installations that use an [external Postgres](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-external-postgres.md) server should be unaffected (they remain on SQLite/nedb for all services, except Synapse)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2380
+msgid "for existing installations which use our integrated Postgres database server (`matrix-postgres`, which is the default), **we automatically migrate data** from SQLite/nedb to Postgres and **archive the database files** (`something.db` -> `something.db.backup`), so you can restore them if you need to go back (see how below)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2382
+msgid "Opting-out of the Postgres migration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2384
+msgid "This is a **very large and somewhat untested change** (potentially dangerous), so **if you're not feeling confident/experimental, opt-out** of it for now. Still, it's the new default and what we (and various bridges) will focus on going forward, so don't stick to old ways for too long."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2386
+msgid "You can remain on SQLite/nedb (at least for now) by adding a variable like this to your `vars.yml` file for each service you use: `matrix_COMPONENT_database_engine: sqlite` (e.g. `matrix_mautrix_facebook_database_engine: sqlite`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2388
+msgid "Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2390
+msgid "Going back to SQLite/nedb if things went wrong"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2392
+msgid "If you went with the Postgres migration and it went badly for you (some bridge not working as expected or not working at all), do this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2394
+msgid "stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2395
+msgid "SSH into the server and rename the old database files (`something.db.backup` -> `something.db`). Example: `mv /matrix/mautrix-facebook/data/mautrix-facebook.db.backup /matrix/mautrix-facebook/data/mautrix-facebook.db`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2396
+msgid "switch the affected service back to SQLite (e.g. `matrix_mautrix_facebook_database_engine: sqlite`). Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2397
+msgid "re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2398
+msgid "[get in touch](README.md#support) with us"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2400
+msgid "2020-12-11"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2402
+msgid "synapse-janitor support removed"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2404
+msgid "We've removed support for the unmaintained [synapse-janitor](https://github.com/xwiki-labs/synapse_scripts) script. There's been past reports of it corrupting the Synapse database. Since there hasn't been any new development on it and it doesn't seem too useful nowadays, there's no point in including it in the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2406
+msgid "If you need to clean up or compact your database, consider using the Synapse Admin APIs directly. See our [Synapse maintenance](docs/maintenance-synapse.md) and [Postgres maintenance](docs/maintenance-postgres.md) documentation pages for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2408
+msgid "Docker 20.10 is here"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2410
+msgid "(No need to do anything special in relation to this. Just something to keep in mind)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2412
+msgid "Docker 20.10 got released recently and your server will likely get it the next time you update."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2414
+msgid "This is the first major Docker update in a long time and it packs a lot of changes. Some of them introduced some breakage for us initially (see [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/d08b27784f222effcbce2abf924bf07bbe0893be) and [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/7593d969e316cc0144bce378a5be58c76c2c37ee)), but it should be all good now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2417
+msgid "2020-12-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2419
+msgid "openid APIs exposed by default on the federation port when federation disabled"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2421
+msgid "We've changed some defaults. People running with our default configuration (federation enabled), are not affected at all."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2423
+msgid "If you are running an unfederated server (`matrix_synapse_federation_enabled: false`), this may be of interest to you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2425
+msgid "When federation is disabled, but ma1sd or Dimension are enabled, we'll now expose the `openid` APIs on the federation port. These APIs are necessary for some ma1sd features to work. If you'd like to prevent this, you can: `matrix_synapse_federation_port_openid_resource_required: false`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2428
+msgid "2020-11-27"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2430
+msgid "Recent Jitsi updates may require configuration changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2432
+msgid "We've recently [updated from Jitsi build 4857 to build 5142](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/719), which brings a lot of configuration changes."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2434
+msgid "**If you use our default Jitsi settings, you won't have to do anything.**"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2436
+msgid "People who have [fine-tuned Jitsi](docs/configuring-playbook-jitsi.md#optional-fine-tune-jitsi) may find that some options got renamed now, others are gone and yet others still need to be defined in another way."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2438
+msgid "The next time you run the playbook [installation](docs/installing.md) command, our validation logic will tell you if you're using some variables like that and will recommend a migration path for each one."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2440
+msgid "Additionally, we've recently disabled transcriptions (`jitsi_enable_transcriptions: false`) and recording (`jitsi_enable_recording: false`) by default. These features did not work anyway, because we don't install the required dependencies for them (Jigasi and Jibri, respectively). If you've been somehow pointing your Jitsi installation to some manually installed Jigasi/Jibri service, you may need to toggle these flags back to enabled to have transcriptions and recordings working."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2443
+msgid "2020-11-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2445 ../../../CHANGELOG.md:2453
+msgid "Breaking change matrix-sms-bridge"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2447
+msgid "Because of many problems using gammu as SMS provider, matrix-sms-bridge now uses (https://github.com/RebekkaMa/android-sms-gateway-server) by default. See (the docs)[./docs/configuring-playbook-bridge-matrix-bridge-sms.md] which new vars you need to add."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2449
+msgid "If you are using this playbook to deploy matrix-sms-bridge and still really want to use gammu as SMS provider, we could possibly add support for both android-sms-gateway-server and gammu."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2451
+msgid "2020-11-13"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2455
+msgid "The new version of [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) changed its database from neo4j to h2. You need to sync the bridge at the first start. Note that this only will sync rooms where the @smsbot:yourServer is member. For rooms without @smsbot:yourServer you need to kick and invite the telephone number **or** invite @smsbot:yourServer."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2457
+msgid "Add the following to your `vars.yml` file: `matrix_sms_bridge_container_extra_arguments=['--env SPRING_PROFILES_ACTIVE=initialsync']`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2458
+msgid "Login to your host shell and remove old systemd file from your host: `rm /etc/systemd/system/matrix-sms-bridge-database.service`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2459
+msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-sms-bridge,start`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2460
+msgid "Login to your host shell and check the logs with `journalctl -u matrix-sms-bridge` until the sync finished."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2461
+msgid "Remove the var from the first step."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2462
+msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2464
+msgid "2020-11-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2466
+msgid "Dynamic DNS support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2468
+msgid "Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook can now manage Dynamic DNS for you using [ddclient](https://ddclient.net/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2470
+msgid "To learn more, follow our [Dynamic DNS docs page](docs/configuring-playbook-dynamic-dns.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2473
+msgid "2020-10-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2475
+msgid "(Compatibility Break) https://matrix.example.com/ now redirects to https://element.example.com/"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2477
+msgid "Until now, we used to serve a static page coming from Synapse at `https://matrix.example.com/`. This page was not very useful to anyone."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2479
+msgid "Since `matrix.example.com` may be accessed by regular users in certain conditions, it's probably better to redirect them to a better place (e.g. to [Element Web](docs/configuring-playbook-client-element-web.md))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2481
+msgid "If Element Web is installed (`matrix_client_element_enabled: true`, which it is by default), we now redirect people to it, instead of showing them a Synapse static page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2483
+msgid "If you'd like to control where the redirect goes, use the `matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain` variable. To restore the old behavior of not redirecting anywhere and serving the Synapse static page, set it to an empty value (`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain: \"\"`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2486
+msgid "2020-10-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2488
+msgid "(Compatibility Break) /_synapse/admin is no longer publicly exposed by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2490
+msgid "We used to expose the Synapse Admin APIs publicly (at `https://matrix.example.com/_synapse/admin`). These APIs require authentication with a valid access token, so it's not that big a deal to expose them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2492
+msgid "However, following [official Synapse's reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints), we're no longer exposing `/_synapse/admin` by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2494
+msgid "If you'd like to restore restore the old behavior and expose `/_synapse/admin` publicly, you can use the following configuration (in your `vars.yml`):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2501
+msgid "2020-10-02"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2503
+msgid "Minimum Ansible version raised to v2.7.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2505
+msgid "We were claiming to support [Ansible](https://www.ansible.com/) v2.5.2 and higher, but issues like [#662](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/662) demonstrate that we need at least v2.7.0."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2507
+msgid "If you've been using the playbook without getting any errors until now, you're probably on a version higher than that already (or you're not using the `matrix-ma1sd` and `matrix-client-element` roles)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2509
+msgid "Our [Ansible docs page](docs/ansible.md) contains information on how to run a more up-to-date version of Ansible."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2512
+msgid "2020-10-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2514
+msgid "Postgres 13 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2516
+msgid "The playbook now installs [Postgres 13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2518
+msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x, 10.x, 11.x or 12.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2520
+msgid "2020-09-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2522
+msgid "matrix-registration support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2524
+msgid "The playbook can now help you set up [matrix-registration](https://github.com/ZerataX/matrix-registration) - an application that lets you keep your Matrix server's registration private, but still allow certain users (those having a unique registration link) to register by themselves."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2526
+msgid "See our [Setting up matrix-registration](docs/configuring-playbook-matrix-registration.md) documentation page to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2529
+msgid "2020-08-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2531
+msgid "rust-synapse-compress-state support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2533
+msgid "The playbook can now help you use [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) to compress the state groups in your Synapse database."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2535
+msgid "See our [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state) documentation page to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2538
+msgid "2020-07-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2540
+msgid "Synapse Admin support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2542
+msgid "The playbook can now help you set up [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2544
+msgid "See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-admin.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2547
+msgid "2020-07-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2549
+msgid "matrix-reminder-bot support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2551
+msgid "The playbook can now help you set up [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2553
+msgid "See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-matrix-reminder-bot.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2556
+msgid "2020-07-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2558
+msgid "(Compatibility Break) Riot is now Element"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2560
+msgid "As per the official announcement, [Riot has been rebraned to Element](https://element.io/blog/welcome-to-element/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2562
+msgid "The playbook follows suit. Existing installations have a few options for how to handle this."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2564
+msgid "See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md#migrating-to-element) documentation page for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2567
+msgid "2020-07-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2569
+msgid "Steam bridging support via mx-puppet-steam"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2571
+msgid "Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the playbook now supports bridging to [Steam](https://steamapp.com/) via the [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) bridge. See our [Setting up MX Puppet Steam bridging](docs/configuring-playbook-bridge-mx-puppet-steam.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2574
+msgid "2020-07-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2576
+msgid "Discord bridging support via mx-puppet-discord"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2578
+msgid "Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the playbook now supports bridging to [Discord](https://discordapp.com/) via the [mx-puppet-discord](https://github.com/Sorunome/mx-puppet-discord) bridge. See our [Setting up MX Puppet Discord bridging](docs/configuring-playbook-bridge-mx-puppet-discord.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2580
+msgid "**Note**: this is a new Discord bridge. The playbook still retains Discord bridging via [matrix-appservice-discord](docs/configuring-playbook-bridge-appservice-discord.md). You're free too use the bridge that serves you better, or even both (for different users and use-cases)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2583
+msgid "2020-06-30"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2585
+msgid "Instagram and Twitter bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2587
+msgid "Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann)'s efforts, the playbook now supports bridging to [Instagram](https://www.instagram.com/) via the [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) bridge. See our [Setting up MX Puppet Instagram bridging](docs/configuring-playbook-bridge-mx-puppet-instagram.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2589
+msgid "Thanks to [Tulir Asokan](https://github.com/tulir)'s efforts, the playbook now supports bridging to [Twitter](https://twitter.com/) via the [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) bridge. See our [Setting up MX Puppet Twitter bridging](docs/configuring-playbook-bridge-mx-puppet-twitter.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2592
+msgid "2020-06-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2594
+msgid "(Post Mortem / fixed Security Issue) Re-enabling User Directory search powered by the ma1sd Identity Server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2596 ../../../CHANGELOG.md:2625
+msgid "User Directory search requests used to go to the ma1sd identity server by default, which queried its own stores and the Synapse database."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2598
+msgid "ma1sd's [security issue](https://github.com/ma1uta/ma1sd/issues/44) has been fixed in version `2.4.0`, with [this commit](ma1uta/ma1sd@2bb5a734d11662b06471113cf3d6b4cee5e33a85). `ma1sd 2.4.0` is now the default version for this playbook. For more information on what happened, please check the mentioned issue."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2600
+msgid "We are re-enabling user directory search with this update. Those who would like to keep it disabled can use this configuration: `matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2602
+msgid "As always, re-running the playbook is enough to get the updated bits."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2604
+msgid "2020-06-11"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2606
+msgid "SMS bridging requires db reset"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2608
+msgid "The current version of [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) needs you to delete the database to work as expected. Just remove `/matrix/matrix-sms-bridge/database/*`. It also adds a new requried var `matrix_sms_bridge_default_region`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2610
+msgid "To reuse your existing rooms, invite `@smsbot:yourServer` to the room or write a message. You are also able to use automated room creation with telephonenumers by writing `sms send -t 01749292923 \"Hello World\"` in a room with `@smsbot:yourServer`. See [the docs](https://github.com/benkuly/matrix-sms-bridge) for more information."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2612
+msgid "2020-06-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2614
+msgid "SMS bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2616
+msgid "Thanks to [benkuly](https://github.com/benkuly)'s efforts, the playbook now supports bridging to SMS (with one telephone number only) via [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2618
+msgid "See our [Setting up Matrix SMS bridging](docs/configuring-playbook-bridge-matrix-bridge-sms.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2621
+msgid "2020-05-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2623
+msgid "(Compatibility Break / Security Issue) Disabling User Directory search powered by the ma1sd Identity Server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2627
+msgid "ma1sd current has [a security issue](https://github.com/ma1uta/ma1sd/issues/44), which made it leak information about all users - including users created by bridges, etc."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2629
+msgid "Until the issue gets fixed, we're making User Directory search not go to ma1sd by default. You **need to re-run the playbook and restart services to apply this workaround**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2631
+msgid "*If you insist on restoring the old behavior* (**which has a security issue!**), you *might* use this configuration: `matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: \"{{ matrix_ma1sd_enabled }}\"`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2634
+msgid "2020-04-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2636
+msgid "Newer IRC bridge (with potential breaking change)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2638
+msgid "This upgrades matrix-appservice-irc from 0.14.1 to 0.16.0.  Upstream made a change to how you define manual mappings.  If you added a `mapping` to your configuration, you will need to update it accoring to the [upstream instructions](https://github.com/matrix-org/matrix-appservice-irc/blob/master/CHANGELOG.md#0150-2020-02-05). If you did not include `mappings` in your configuration for IRC, no change is necessary.  `mappings` is not part of the default configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2647
+msgid "2020-04-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2649 ../../../CHANGELOG.md:2880
+msgid "Slack bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2651
+msgid "Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the playbook now supports bridging to [Slack](https://slack.com) via the [mx-puppet-slack](https://github.com/Sorunome/mx-puppet-slack) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2653
+msgid "See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-bridge-mx-puppet-slack.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2656
+msgid "2020-04-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2658
+msgid "Skype bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2660
+msgid "Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the playbook now supports bridging to [Skype](https://www.skype.com) via the [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2662
+msgid "See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2665
+msgid "2020-04-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2667
+msgid "Private Jitsi support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2669
+msgid "The [Jitsi support](#jitsi-support) we had landed a few weeks ago was working well, but it was always open to the whole world."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2671
+msgid "Running such an open instance is not desirable to most people, so [teutat3s](https://github.com/teutat3s) has contributed support for making Jitsi use authentication."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2673
+msgid "To make your Jitsi server more private, see the [configure internal Jitsi authentication and guests mode](docs/configuring-playbook-jitsi.md#optional-configure-internal-jitsi-authentication-and-guests-mode) section in our Jitsi documentation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2676
+msgid "2020-04-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2678
+msgid "(Potential Backward Compatibility Break) ma1sd replaces mxisd"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2680
+msgid "Thanks to [Marcel Partap](https://github.com/eMPee584)'s efforts, the [mxisd](https://github.com/kamax-io/mxisd) identity server, which has been deprecated for a long time, has finally been replaced by [ma1sd](https://github.com/ma1uta/ma1sd), a compatible fork."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2682
+msgid "**If you're using the default playbook configuration**, you don't need to do anything -- your mxisd installation will be replaced with ma1sd and all existing data will be migrated automatically the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2684
+msgid "**If you're doing something more special** (defining custom `matrix_mxisd_*` variables), the playbook will ask you to rename them to `matrix_ma1sd_*`. You're also encouraged to test that ma1sd works well for such a more custom setup."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2687
+msgid "2020-03-29"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2689
+msgid "Archlinux support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2691
+msgid "Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts, the playbook now supports installing to an [Archlinux](https://www.archlinux.org/) server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2694
+msgid "2020-03-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2696
+msgid "Jitsi support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2698
+msgid "The playbook can now (optionally) install the [Jitsi](https://jitsi.org/) video-conferencing platform and integrate it with [Riot](docs/configuring-playbook-riot-web.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2700
+msgid "See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2703
+msgid "2020-03-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2705
+msgid "Raspberry Pi support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2707
+msgid "Thanks to [Gergely Horváth](https://github.com/hooger)'s effort, the playbook supports installing to a Raspberry Pi server, for at least some of the services."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2709
+msgid "Since most ready-made container images do not support that architecture, we achieve this by building images locally on the device itself. See our [Self-building documentation page](docs/self-building.md) for how to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2712
+msgid "2020-02-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2714
+msgid "Riot-web themes are here"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2716
+msgid "The playbook now makes it easy to install custom riot-web themes."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2718
+msgid "To learn more, take a look at our [riot-web documentation on Themes](docs/configuring-playbook-riot-web.md#themes)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2721
+msgid "2020-02-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2723
+msgid "Customize the server name in Riot's login page"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2725
+msgid "You can now customize the server name string that Riot-web displays in its login page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2727
+msgid "These playbook variables, with these default values, have been added:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2733
+msgid "The login page previously said \"Sign in to your Matrix account on matrix.example.org\" (the homeserver's domain name). It will now say \"Sign in … on example.org\" (the server name) by default, or \"Sign in … on Our Server\" if you set the variable to \"Our Server\"."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2735
+msgid "To support this, the config.json template is changed to use the configuration key `default_server_config` for setting the default HS/IS, and the new configuration key `server_name` is added in there."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2738
+msgid "2020-01-30"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2740
+msgid "Disabling TLSv1.1"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2742
+msgid "To improve security, we've removed TLSv1.1 support from our default matrix-nginx-proxy configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2744
+msgid "If you need to support old clients, you can re-enable it with the following configuration: `matrix_nginx_proxy_ssl_protocols: \"TLSv1.1 TLSv1.2 TLSv1.3\"`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2747
+msgid "2020-01-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2749
+msgid "Postgres collation changes (action required!)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2751
+msgid "By default, we've been using a UTF-8 collation for Postgres. This is known to cause Synapse some troubles (see the [relevant issue](https://github.com/matrix-org/synapse/issues/6722)) on systems that use [glibc](https://www.gnu.org/software/libc/). We run Postgres in an [Alpine Linux](https://alpinelinux.org/) container (which uses [musl](https://www.musl-libc.org/), and not glibc), so our users are likely not affected by the index corruption problem observed by others."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2753
+msgid "Still, we might become affected in the future. In any case, it's imminent that Synapse will complain about databases which do not use a C collation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2755
+msgid "To avoid future problems, we recommend that you run the following command:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2761
+msgid "It forces a [Postgres database upgrade](docs/maintenance-postgres.md#upgrading-postgresql), which would recreate your Postgres database using the proper (`C`) collation. If you are low on disk space, or run into trouble, refer to the Postgres database upgrade documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2764
+msgid "2020-01-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2766
+msgid "Added support for Appservice Webhooks"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2768
+msgid "Thanks to a contribution from [Björn Marten](https://github.com/tripleawwy) from [netresearch](https://www.netresearch.de/), the playbook can now install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2770
+msgid "Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-playbook-bridge-appservice-webhooks.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2773
+msgid "2020-01-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2775
+msgid "Added support for automatic Double Puppeting for all Mautrix bridges"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2777
+msgid "Double Puppeting can now be easily enabled for all Mautrix bridges supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2779
+msgid "This is possible due to those bridges' integration with [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) - yet another component that this playbook can install for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2781
+msgid "To get started, following the playbook's documentation for the bridge you'd like to configure."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2784
+msgid "2019-12-06"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2786
+msgid "Added support for an alternative method for using another webserver"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2788
+msgid "We have added support for making `matrix-nginx-proxy` not being so invasive, so that it would be easier to [use your own webserver](docs/configuring-playbook-own-webserver.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2790
+msgid "The documentation has been updated with a **Method 2**, which might make \"own webserver\" setup easier in some cases (such as [reverse-proxying using Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/296))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2792
+msgid "**Existing users** are not affected by this and **don't need to change anything**. The defaults are still the same (`matrix-nginx-proxy` obtaining SSL certificates and doing everything for you automatically)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2795
+msgid "2019-11-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2797
+msgid "Tightened security around room directory publishing"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2799
+msgid "As per this [advisory blog post](https://matrix.org/blog/2019/11/09/avoiding-unwelcome-visitors-on-private-matrix-servers), we've decided to change the default publishing rules for the Matrix room directory."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2801
+msgid "Our general goal is to favor privacy and security when running personal (family & friends) and corporate homeservers. Both of these likely benefit from having a more secure default of **not showing the room directory without authentication** and **not publishing the room directory over federation**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2803
+msgid "As with anything else, these new defaults can be overriden by changing the `matrix_synapse_allow_public_rooms_without_auth` and `matrix_synapse_allow_public_rooms_over_federation` variables, respectively."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2806
+msgid "2019-10-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2808
+msgid "Improved Postgres upgrading/importing"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2810
+msgid "Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) and [importing](docs/importing-postgres.md) have been improved to add support for multiple databases and roles."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2812
+msgid "Previously, the playbook would only take care of the `homeserver` database and `synapse` user. We now back up and restore all databases and users on the Postgres server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2814
+msgid "For now, the playbook only uses that one database (`homeserver`) and that one single user (`synapse`), so it's all the same. However, in the future, additional components besides Synapse may also make use the Postgres database server. One such example is the [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge, which strongly encourages use of Postgres in its v1.0 release. We are yet to upgrade to it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2816
+msgid "Additionally, Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) now uses gzipped dump files by default, to minimize disk space usage."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2819
+msgid "2019-10-04"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2821
+msgid "Postgres 12 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2823
+msgid "The playbook now installs [Postgres 12](https://www.postgresql.org/about/news/1976/) by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2825
+msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x, 10.x or 11.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2828
+msgid "2019-10-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2830
+msgid "Synapse 1.4.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2832
+msgid "Synapse 1.4.0 [is out](https://matrix.org/blog/2019/10/03/synapse-1-4-0-released) with lots of changes related to privacy."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2834
+msgid "Its new defaults (which we adopt as well) mean that certain old data will automatically get purged after a certain number of days. 1.4.0 automatically garbage collects redacted messages (defaults to 7 days) and removes unused IP and user agent information stored in the user_ips table (defaults to 30 days). If you'd like to preserve this data, we encourage you to look at the `redaction_retention_period` and `user_ips_max_age` options (controllable by the `matrix_synapse_redaction_retention_period` and `matrix_synapse_user_ips_max_age` playbook variables, respectively) before doing the upgrade. If you'd like to keep data indefinitely, set these variables to `null` (e.g. `matrix_synapse_redaction_retention_period: ~`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2836
+msgid "From now on the `trusted_key_servers` setting for Synapse is configurable. It still defaults to `matrix.org` just like it always has, but in a more explicit way now. If you'd like to use another trusted key server, adjust the `matrix_synapse_trusted_key_servers` playbook variable."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2838
+msgid "Synapse 1.4.0 also changes lots of things related to identity server integration. Because Synapse will now by default be responsible for validating email addresses for user accounts, running without an identity server looks more feasible. We still [have concerns](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/275/files#r331104117) over disabling the identity server by default, so for now it remains enabled."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2841
+msgid "2019-09-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2843
+msgid "Synapse Simple Antispam support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2845
+msgid "There have been lots of invite-spam attacks lately and [Travis](https://github.com/t2bot) has created a Synapse module ([synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam)) to let people protect themselves."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2847
+msgid "From now on, you can easily install and configure this spam checker module through the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2849
+msgid "Learn more in [Setting up Synapse Simple Antispam](docs/configuring-playbook-synapse-simple-antispam.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2852
+msgid "2019-08-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2854
+msgid "Extensible Riot-web configuration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2856
+msgid "Similarly to [Extensible Synapse configuration](#extensible-synapse-configuration) (below), Riot-web configuration is also extensible now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2858
+msgid "From now on, you can extend/override Riot-web's configuration by making use of the `matrix_riot_web_configuration_extension_json` variable. This should be enough for most customization needs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2860
+msgid "If you need even more power, you can now also take full control and override `matrix_riot_web_configuration_default` (or `matrix_riot_web_configuration`) directly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2862
+msgid "Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-web.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2865
+msgid "2019-08-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2867
+msgid "Extensible Synapse configuration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2869
+msgid "Previously, we had to create custom Ansible variables for each and every Synapse setting. This lead to too much effort (and configuration ugliness) to all of Synapse's settings, so naturally, not all features of Synapse could be controlled through the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2871
+msgid "From now on, you can extend/override the Synapse server's configuration by making use of the `matrix_synapse_configuration_extension_yaml` variable. This should be enough for most customization needs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2873
+msgid "If you need even more power, you can now also take full control and override `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`) directly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2875
+msgid "Learn more here in [Configuring Synapse](docs/configuring-playbook-synapse.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2878
+msgid "2019-08-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2882
+msgid "Thanks to the [great work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/205) of [kingoftheconnors](https://github.com/kingoftheconnors) and [Stuart Mumford (Cadair)](https://github.com/Cadair), the playbook now supports bridging to [Slack](https://slack.com) via the [appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2884
+msgid "Additional details are available in [Setting up Appservice Slack bridging](docs/configuring-playbook-bridge-appservice-slack.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2886
+msgid "Google Hangouts bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2888
+msgid "Thanks to the [great work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/251) of [Eduardo Beltrame (Munfred)](https://github.com/Munfred) and [Robbie D (microchipster)](https://github.com/microchipster), the playbook now supports bridging to [Google Hangouts](https://hangouts.google.com/) via the [mautrix-hangouts](https://mau.dev/tulir/mautrix-hangouts) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2890
+msgid "Additional details are available in [Setting up Mautrix Hangouts bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2893
+msgid "2019-08-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2895
+msgid "Email2Matrix support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2897
+msgid "Support for [Email2Matrix](https://github.com/devture/email2matrix) has been added."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2899
+msgid "It's an optional feature that you can enable via the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2901
+msgid "To learn more, see the [playbook's documentation on Email2Matrix](./docs/configuring-playbook-email2matrix.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2904
+msgid "2019-08-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2906
+msgid "Synapse logging level has been reduced to WARNING"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2908
+msgid "After [some discussion in our support room](https://matrix.to/#/!PukFFdIcHgtaaHZflT:devture.com/$156476852524179TBeKy:matrix.org?via=devture.com&via=matrix.org&via=librem.one), we've decided to change the default logging level for Synapse from `INFO` to `WARNING`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2910
+msgid "This greatly reduces the number of log messages that are being logged, leading to:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2912
+msgid "much less disk space dedicated to Synapse and thus, logs kept for longer"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2913
+msgid "easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages, as they're not longer buried in thousands of non-important `INFO` messages"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2915
+msgid "If you'd like to track down an issue, you [can always increase the logging level as described here](./docs/maintenance-and-troubleshooting.md#increasing-synapse-logging)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2918
+msgid "2019-07-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2920
+msgid "Synapse Maintenance docs and synapse-janitor support are available"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2922
+msgid "The playbook can now help you with Synapse's maintenance."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2924
+msgid "There's a new documentation page about [Synapse maintenance](./docs/maintenance-synapse.md) and another section on [Postgres vacuuming](./docs/maintenance-postgres.md#vacuuming-postgresql)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2926
+msgid "Among other things, if your Postgres database has grown significantly over time, you may wish to [ask the playbook to purge unused data with synapse-janitor](./docs/maintenance-synapse.md#purging-unused-data-with-synapse-janitor) for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2928
+msgid "(BC Break) Rename run control variables"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2930
+msgid "Some internal playbook control variables have been renamed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2932
+msgid "This change **only affects people who run this playbook's roles from another playbook**. If you're using this playbook as-is, you're not affected and don't need to do anything."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2934
+msgid "The following variables have been renamed:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2936
+msgid "from `run_import_postgres` to `run_postgres_import`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2937
+msgid "from `run_import_sqlite_db` to `run_postgres_import_sqlite_db`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2938
+msgid "from `run_upgrade_postgres` to `run_postgres_upgrade`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2939
+msgid "from `run_import_media_store` to `run_synapse_import_media_store`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2940
+msgid "from `run_register_user` to `run_synapse_register_user`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2941
+msgid "from `run_update_user_password` to `run_synapse_update_user_password`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2944
+msgid "2019-07-04"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2946
+msgid "Synapse no longer logs to text files"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2948
+msgid "Following what the official Synapse Docker image is doing ([#5565](https://github.com/matrix-org/synapse/pull/5565)) and what we've been doing for mostly everything installed by this playbook, **Synapse no longer logs to text files** (`/matrix/synapse/run/homeserver.log*`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2950
+msgid "From now on, Synapse would only log to console, which goes to systemd's journald. To see Synapse's logs, execute: `journalctl -fu matrix-synapse`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2952
+msgid "Because of this, the following variables have become obsolete and were removed:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2954
+msgid "`matrix_synapse_max_log_file_size_mb`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2955
+msgid "`matrix_synapse_max_log_files_count`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2957
+msgid "To prevent confusion, it'd be better if you delete all old files manually after you've upgraded (`rm -f /matrix/synapse/run/homeserver.log*`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2959
+msgid "Because Synapse is incredibly chatty when it comes to logging (here's [one such issue](https://github.com/matrix-org/synapse/issues/4751) describing the problem), if you're running an ancient distribution (like CentOS 7.0), be advised that systemd's journald default logging restrictions may not be high enough to capture all log messages generated by Synapse. This is especially true if you've got a busy (Synapse) server. We advise that you manually add `RateLimitInterval=0` and `RateLimitBurst=0` under `[Storage]` in the `/etc/systemd/journald.conf` file, followed by restarting the logging service (`systemctl restart systemd-journald`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2962
+msgid "2019-06-27"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2964
+msgid "(BC Break) Discord bridge configuration is now entirely managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2966
+msgid "Until now, the `config.yaml` file for the [Discord bridge](docs/configuring-playbook-bridge-appservice-discord.md) was managed by the playbook, but the `registration.yaml` file was not."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2968
+msgid "From now on, the playbook will keep both configuration files sync for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2970
+msgid "This means that if you were making manual changes to the `/matrix/appservice-discord/discord-registration.yaml` configuration file, those would be lost the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2972
+msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-discord/config`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2974
+msgid "Likewise, data is now also stored in a subdirectory (`/matrix/appservice-discord/data`). When you run the playbook with an existing database file (`/matrix/appservice-discord/discord.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2976
+msgid "The main directory (`/matrix/appservice-discord`) may contain some leftover files (`user-store.db`, `room-store.db`, `config.yaml`, `discord-registration.yaml`, `invite_link`). These are no longer necessary and can be deleted manually."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2978
+msgid "We're now following the default sample configuration for the Discord bridge. If you need to override some values, define them in `matrix_appservice_discord_configuration_extension_yaml`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2981
+msgid "2019-06-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2983
+msgid "(BC Break) WhatsApp bridge configuration is now entirely managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2985
+msgid "Until now, configuration files for the [WhatsApp bridge](docs/configuring-playbook-bridge-mautrix-whatsapp.md) were created by the playbook initially, but never modified later on."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2987 ../../../CHANGELOG.md:3004
+#: ../../../CHANGELOG.md:3023 ../../../CHANGELOG.md:3062
+msgid "From now on, the playbook will keep the configuration in sync for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2989
+msgid "This means that if you were making manual changes to the `/matrix/mautrix-whatsapp/config.yaml` or `/matrix/mautrix-whatsapp/registration.yaml` configuration files, those would be lost the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2991
+msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-whatsapp/config`), so your old configuration remains in the base directory (`/matrix/mautrix-whatsapp`). You need to migrate any manual changes over to the new `matrix_mautrix_whatsapp_configuration_extension_yaml` variable, so that the playbook would apply them for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2993
+msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-whatsapp/data`). When you run the playbook with an existing database file (`/matrix/mautrix-whatsapp/mautrix-whatsapp.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2995
+msgid "We're now following the default configuration for the WhatsApp bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2998
+msgid "2019-06-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3000
+msgid "(BC Break) IRC bridge configuration is now entirely managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3002
+msgid "Until now, configuration files for the [IRC bridge](docs/configuring-playbook-bridge-appservice-irc.md) were created by the playbook initially, but never modified later on."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3006
+msgid "This means that if you were making manual changes to the `/matrix/appservice-irc/config.yaml` or `/matrix/appservice-irc/registration.yaml` configuration files, those would be lost the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3008
+msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-irc/config`), so your old configuration remains in the base directory (`/matrix/appservice-irc`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3010
+msgid "Previously, we asked people to configure bridged IRC servers by extending the bridge configuration (`matrix_appservice_irc_configuration_extension_yaml`). While this is still possible and will continue working forever, **we now recommend defining IRC servers in the easier to use `matrix_appservice_irc_ircService_servers` variable**. See [our IRC bridge documentation page](docs/configuring-playbook-bridge-appservice-irc.md) for an example."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3012
+msgid "If you decide to continue using `matrix_appservice_irc_configuration_extension_yaml`, you might be interested to know that `ircService.databaseUri` and a few other keys now have default values in the base configuration (`matrix_appservice_irc_configuration_yaml`). You may wish to stop redefining those keys, unless you really intend to override them. You most likely only need to override `ircService.servers`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3014
+msgid "Bridge data (`passkey.pem` and database files) is now also stored in a subdirectory (`/matrix/appservice-irc/data`). When you run the playbook with an existing `/matrix/appservice-irc/passkey.pem` file, the playbook will stop the bridge and relocate the passkey and database files (`rooms.db` and `users.db`) to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3017
+msgid "2019-06-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3019
+msgid "(BC Break) Telegram bridge configuration is now entirely managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3021
+msgid "Until now, configuration files for the [Telegram bridge](docs/configuring-playbook-bridge-mautrix-telegram.md) were created by the playbook initially, but never modified later on."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3025
+msgid "This means that if you were making manual changes to the `/matrix/mautrix-telegram/config.yaml` or `/matrix/mautrix-telegram/registration.yaml` configuration files, those would be lost the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3027
+msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-telegram/config`), so your old configuration remains in the base directory (`/matrix/mautrix-telegram`). You need to migrate any manual changes over to the new `matrix_mautrix_telegram_configuration_extension_yaml` variable, so that the playbook would apply them for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3029
+msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-telegram/data`). When you run the playbook with an existing database file (`/matrix/mautrix-telegram/mautrix-telegram.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3031
+msgid "Also, we're now following the default configuration for the Telegram bridge, so some default configuration values are different:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3033
+msgid "`edits_as_replies` (used to be `false`, now `true`) - previously replies were not sent over to Matrix at all; ow they are sent over as a reply to the original message"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3034
+msgid "`inline_images` (used to be `true`, now `false`) - this has to do with captioned images. Inline-image (included caption) are said to exhibit troubles on Riot iOS. When `false`, the caption arrives on the Matrix side as a separate message."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3035
+msgid "`authless_portals` (used to be `false`, now `true`) - creating portals from the Telegram side is now possible"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3036
+msgid "`whitelist_group_admins` (used to be `false`, now `true`) - allows Telegram group admins to use the bot commands"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3038
+msgid "If the new values are not to your liking, use `matrix_mautrix_telegram_configuration_extension_yaml` to specify an override (refer to `matrix_mautrix_telegram_configuration_yaml` to figure out which variable goes where)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3041
+msgid "2019-06-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3043
+msgid "Synapse v1.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3045
+msgid "With [Synapse v1.0 now available](https://matrix.org/blog/2019/06/11/introducing-matrix-1-0-and-the-matrix-org-foundation) and most people being on at least Synapse v0.99, it's time to remove the `_matrix._tcp` DNS SRV record that we've been keeping for compatibility with old Synapse versions (<= 0.34)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3047
+msgid "According to the [Server Discovery specification](https://matrix.org/docs/spec/server_server/r0.1.2.html#server-discovery), it's no harm to keep the DNS SRV record. But since it's not necessary for federating with the larger Matrix network anymore, you should be safe to get rid of it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3049
+msgid "**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` DNS SRV records. The latter, **must not** be removed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3051
+msgid "For completeness, we must say that using a `_matrix._tcp` [SRV record for Server Delegation](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced) is still valid and useful for certain deployments. It's just that our guide recommends the [`/.well-known/matrix/server` Server Delegation method](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), due to its easier implementation when using this playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3053
+msgid "Besides this optional/non-urgent DNS change, assuming you're already on Synapse v0.99, upgrading to Synapse v1.0 should be as simple as [re-running the playbook](docs/maintenance-upgrading-services.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3056
+msgid "2019-06-07"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3058
+msgid "(BC Break) Facebook bridge configuration is now entirely managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3060
+msgid "Until now, configuration files for the [Facebook bridge](docs/configuring-playbook-bridge-mautrix-facebook.md) were created by the playbook initially, but never modified later on."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3064
+msgid "This means that if you were making manual changes to the `/matrix/mautrix-facebook/config.yaml` or `/matrix/mautrix-facebook/registration.yaml` configuration files, those would be lost the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3066
+msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-facebook/config`), so your old configuration remains in the base directory (`/matrix/mautrix-facebook`). You need to migrate any manual changes over to the new `matrix_mautrix_facebook_configuration_extension_yaml` variable, so that the playbook would apply them for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3068
+msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-facebook/data`). When you run the playbook with an existing database file (`/matrix/mautrix-facebook/mautrix-facebook.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3071
+msgid "2019-05-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3073
+msgid "Support for exposing container ports publicly (not just to the host)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3075
+msgid "Until now, various roles supported a `matrix_*_expose_port` variable, which would expose their container's port to the host. This was mostly useful for reverse-proxying manually (in case `matrix-nginx-proxy` was disabled). It could also be used for installing some playbook services (e.g. bridges, etc.) and wiring them to a separate (manual) Matrix setup."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3077
+msgid "`matrix_*_expose_port` variables were not granular enough - sometimes they would expose one port, other times multiple. They also didn't provide control over **where** to expose (to which port number and to which network interface), because they would usually hardcode something like `127.0.0.1:8080`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3079
+msgid "All such variables have been superseded by a better (more flexible) way to do it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3081
+msgid "**Most** people (including those not using `matrix-nginx-proxy`), **don't need** to bother with this."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3083
+msgid "Porting examples follow for people having more customized setups:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3085
+msgid "**from** `matrix_synapse_container_expose_client_api_port: true` **to** `matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3087
+msgid "**from** `matrix_synapse_container_expose_federation_api_port: true` **to** `matrix_synapse_container_federation_api_plain_host_bind_port: '127.0.0.1:8048'` and possibly `matrix_synapse_container_federation_api_tls_host_bind_port: '8448'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3089
+msgid "**from** `matrix_synapse_container_expose_metrics_port: true` **to** `matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3091
+msgid "**from** `matrix_riot_web_container_expose_port: true` **to** `matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3093
+msgid "**from** `matrix_mxisd_container_expose_port: true` **to** `matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3095
+msgid "**from** `matrix_dimension_container_expose_port: true` **to** `matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3097
+msgid "**from** `matrix_corporal_container_expose_ports: true` **to** `matrix_corporal_container_http_gateway_host_bind_port: '127.0.0.1:41080'` and possibly `matrix_corporal_container_http_api_host_bind_port: '127.0.0.1:41081'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3099
+msgid "**from** `matrix_appservice_irc_container_expose_client_server_api_port: true` **to** `matrix_appservice_irc_container_http_host_bind_port: '127.0.0.1:9999'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3101
+msgid "**from** `matrix_appservice_discord_container_expose_client_server_api_port: true` **to** `matrix_appservice_discord_container_http_host_bind_port: '127.0.0.1:9005'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3103
+msgid "As always, if you forget to remove usage of some outdated variable, the playbook will warn you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3106
+msgid "2019-05-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3108
+msgid "(BC Break) Ansible 2.8 compatibility"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3110
+msgid "Thanks to [@danbob](https://github.com/danbob), the playbook now [supports the new Ansible 2.8](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/187)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3112
+msgid "A manual change is required to the `inventory/hosts` file, changing the group name from `matrix-servers` to `matrix_servers` (dash to underscore)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3114
+msgid "To avoid doing it manually, run this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3115
+msgid "Linux: `sed -i 's/matrix-servers/matrix_servers/g' inventory/hosts`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3116
+msgid "Mac: `sed -i '' 's/matrix-servers/matrix_servers/g' inventory/hosts`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3119
+msgid "2019-05-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3121
+msgid "Synapse no longer required"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3123
+msgid "The playbook no longer insists on installing [Synapse](https://github.com/element-hq/synapse) via the `matrix-synapse` role."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3125
+msgid "If you would prefer to install Synapse another way and just use the playbook to install other services, it should be possible (`matrix_synapse_enabled: false`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3127
+msgid "Note that it won't necessarily be the best experience, since the playbook wires things to Synapse by default. If you're using your own Synapse instance (especially one not running in a container), you may have to override many variables to point them to the correct place."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3129
+msgid "Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3131
+msgid "Bridges are now separate from the Synapse role"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3133
+msgid "Bridges are no longer part of the `matrix-synapse` role. Each bridge now lives in its own separate role (`roles/custom/matrix-bridge-*`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3135
+msgid "These bridge roles are independent of the `matrix-synapse` role, so it should be possible to use them with a Synapse instance installed another way (not through the playbook)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3137
+msgid "Renaming inconsistently-named Synapse variables"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3139
+msgid "For better consistency, the following variables have been renamed:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3141
+msgid "`matrix_enable_room_list_search` was renamed to `matrix_synapse_enable_room_list_search`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3142
+msgid "`matrix_alias_creation_rules` was renamed to `matrix_synapse_alias_creation_rules`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3143
+msgid "`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was renamed to `matrix_synapse_room_list_publication_rules`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3146
+msgid "2019-05-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3148
+msgid "Besides a myriad of bug fixes and minor improvements, here are the more notable (bigger) features we can announce today."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3150
+msgid "Mautrix Facebook/Messenger bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3152
+msgid "The playbook now supports bridging with [Facebook](https://www.facebook.com/) by installing the [mautrix-facebook](https://github.com/tulir/mautrix-facebook) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3154
+msgid "Additional details are available in [Setting up Mautrix Facebook bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3156
+msgid "mxisd Registration feature integration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3158
+msgid "The playbook can now help you integrate with mxisd's [Registration](https://github.com/kamax-matrix/mxisd/blob/master/docs/features/registration.md) feature."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3160
+msgid "Learn more in [mxisd-controlled Registration](docs/configuring-playbook-mxisd.md#mxisd-controlled-registration)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3163
+msgid "2019-04-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3165
+msgid "Caddy webserver examples"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3167
+msgid "If you prefer using the [Caddy](https://caddyserver.com/) webserver instead of our own integrated nginx, we now have examples for it in the [`examples/caddy`](examples/caddy) directory"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3169
+msgid "2019-04-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3171
+msgid "Goofys support for other S3-compatible object stores"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3173
+msgid "Until now, you could optionally host Synapse's media repository on Amazon S3, but we now also support [using other S3-compatible object stores](docs/configuring-playbook-s3.md),"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3176
+msgid "2019-04-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3178
+msgid "Ansible >= 2.5 is required"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3180
+msgid "Due to recent playbook improvements and the fact that the world keeps turning, we're bumping the [version requirement for Ansible](docs/ansible.md#supported-ansible-versions) (2.4 -> 2.5)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3182
+msgid "We've also started building our own Docker image of Ansible ([devture/ansible](https://hub.docker.com/r/devture/ansible/)), which is useful for people who can't upgrade their local Ansible installation (see [Using Ansible via Docker](docs/ansible.md#using-ansible-via-docker))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3185
+msgid "2019-03-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3187
+msgid "TLS support for Coturn"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3189
+msgid "We've added TLS support to the Coturn TURN server installed by the playbook by default. The certificates from the Matrix domain will be used for the Coturn server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3191
+msgid "This feature is enabled by default for new installations. To make use of TLS support for your existing Matrix server's Coturn, make sure to rebuild both Coturn and Synapse:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3197
+msgid "People who have an extra firewall (besides the iptables firewall, which Docker manages automatically), will need to open these additional firewall ports: `5349/tcp` (TURN over TCP) and `5349/udp` (TURN over UDP)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3199
+msgid "People who build their own custom playbook from our roles should be aware that:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3201
+msgid "the `matrix-coturn` role and actually starting Coturn (e.g. `--tags=start`), requires that certificates are already put in place. For this reason, it's usually a good idea to have the `matrix-coturn` role execute after `matrix-nginx-proxy` (which retrieves the certificates)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3203
+msgid "there are a few variables that can help you enable TLS support for Coturn. See the `matrix-coturn` section in [group_vars/matrix-servers](./group_vars/matrix-servers)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3206
+msgid "2019-03-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3208
+msgid "matrix-nginx-proxy support for serving the base domain"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3210
+msgid "If you don't have a dedicated server for your base domain and want to set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), the playbook has got you covered now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3212
+msgid "It's now possible for the playbook to obtain an SSL certificate and serve the necessary files for Matrix Server Delegation on your base domain. Take a look at the new [Serving the base domain](docs/configuring-playbook-base-domain-serving.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3214
+msgid "(BC break) matrix-nginx-proxy data variable renamed"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3216
+msgid "`matrix_nginx_proxy_data_path` was renamed to `matrix_nginx_proxy_base_path`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3218
+msgid "There's a new `matrix_nginx_proxy_data_path` variable, which has a different use-purpose now (it's a subdirectory of `matrix_nginx_proxy_base_path` and is meant for storing various data files)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3221
+msgid "2019-03-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3223
+msgid "Dimension integration manager support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3225
+msgid "Thanks to [NullIsNot0](https://github.com/NullIsNot0), the playbook can now (optionally) install the [Dimension](https://dimension.t2bot.io/) integration manager. To learn more, see the [Setting up Dimension](docs/configuring-playbook-dimension.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3228
+msgid "2019-03-07"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3230
+msgid "Ability to customize mxisd's email templates"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3232
+msgid "Thanks to [Sylvia van Os](https://github.com/TheLastProject), mxisd's email templates can now be customized easily. To learn more, see the [Customizing email templates](docs/configuring-playbook-mxisd.md#customizing-email-templates) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3235
+msgid "2019-03-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3237
+msgid "Discord bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3239
+msgid "[@Lionstiger](https://github.com/Lionstiger) has done some great work adding Discord bridging support via [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord). To learn more, see the [Setting up Appservice Discord bridging](docs/configuring-playbook-bridge-appservice-discord.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3242
+msgid "2019-02-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3244
+msgid "Renaming variables"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3246 ../../../CHANGELOG.md:3563
+#: ../../../CHANGELOG.md:3648 ../../../CHANGELOG.md:3768
+msgid "The following playbook variables were renamed:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3248
+msgid "from `host_specific_hostname_identity` to `matrix_domain`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3249
+msgid "from `hostname_identity` to `matrix_domain`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3250
+msgid "from `hostname_matrix` to `matrix_server_fqn_matrix`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3251
+msgid "from `hostname_riot` to `matrix_server_fqn_riot`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3252
+msgid "from `host_specific_matrix_ssl_lets_encrypt_support_email` to `matrix_ssl_lets_encrypt_support_email`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3254
+msgid "Doing that, we've simplified things, made names less confusing (hopefully) and moved all variable names under the `matrix_` prefix."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3257
+msgid "2019-02-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3259
+msgid "Riot v1.0.1 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3261
+msgid "You can now use the brand new and redesigned Riot."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3263
+msgid "The new version no longer has a homepage by default, so we've also removed the custom homepage that we've been installing."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3265
+msgid "However, we still provide you with hooks to install your own `home.html` file by specifying the `matrix_riot_web_embedded_pages_home_path` variable (used to be called `matrix_riot_web_homepage_template` before)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3268
+msgid "2019-02-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3270
+msgid "Synapse v0.99.1"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3272
+msgid "As we're moving toward Synapse v1.0, things are beginning to stabilize. Upgrading from v0.99.0 to v0.99.1 should be painless."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3274
+msgid "If you've been overriding the default configuration so that you can terminate TLS at the Synapse side (`matrix_synapse_no_tls: false`), you'll now have to replace this custom configuration with `matrix_synapse_tls_federation_listener_enabled: true`. The `matrix_synapse_no_tls` variable is no more."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3277
+msgid "2019-02-06"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3279
+msgid "Synapse v0.99 support and preparation for Synapse v1.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3281
+msgid "Matrix is undergoing a lot of changes as it matures towards Synapse v1.0. The first step is the Synapse v0.99 transitional release, which this playbook now supports."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3283
+msgid "If you've been using this playbook successfully until now, you'd be aware that we've been doing [Server Delegation](docs/howto-server-delegation.md) using a `_matrix._tcp` DNS SRV record (as per [Configuring DNS](docs/configuring-dns.md))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3285
+msgid "Due to changes related to certificate file requirements that will affect us at Synapse v1.0, we'll have to stop using a **`_matrix._tcp` DNS SRV record in the future** (when Synapse goes to v1.0 - around 5th of March 2019). We **still need to keep the SRV record for now**, for backward compatibility with older Synapse versions (lower than v0.99)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3287
+msgid "**What you need to do now** is make use of this transitional Synapse v0.99 release to **prepare your federation settings for the future**. You have 2 choices to prepare yourself for compatibility with the future Synapse v1.0:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3289
+msgid "(recommended) set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), unless you are affected by the [Downsides of well-known-based Server Delegation](docs/howto-server-delegation.md#downsides-of-well-known-based-server-delegation). If you had previously set up the well-known `client` file, depending on how you've done it, it may be that there is nothing new required of you (besides [upgrading](docs/maintenance-upgrading-services.md)). After upgrading, you can [run a self-check](docs/maintenance-checking-services.md), which will tell you if you need to do anything extra with regard to setting up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file). After some time, when most people have upgraded to Synapse v0.99 and older releases have disappeared, be prepared to drop your `_matrix._tcp` SRV record."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3291
+msgid "(more advanced) if the [Downsides of well-known-based Server Delegation](docs/howto-server-delegation.md#downsides-of-well-known-based-server-delegation) are not to your liking, **as an alternative**, you can set up [Server Delegation via a DNS SRV record](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced). In such a case, you get to keep using your existing `_matrix._tcp` DNS SRV record forever and need to NOT set up a `/.well-known/matrix/server` file. Don't forget that you need to do certificate changes though. Follow the guide at [Server Delegation via a DNS SRV record](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3294
+msgid "2019-02-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3296
+msgid "TLS v1.3 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3298
+msgid "Now that the [nginx Docker image](https://hub.docker.com/_/nginx) has [added support for TLS v1.3](https://github.com/nginxinc/docker-nginx/issues/190), we have enabled that protocol by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3300
+msgid "When using:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3302
+msgid "the **integrated nginx server**: TLS v1.3 support might not kick in immediately, because the nginx version hasn't been bumped and you may have an older build of the nginx Docker image (currently `nginx:1.15.8-alpine`). Typically, we do not re-pull images that you already have. When the nginx version gets bumped in the future, everyone will get the update. Until then, you could manually force-pull the rebuilt Docker image by running this on the server: `docker pull nginx:1.15.8-alpine`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3304
+msgid "**your own external nginx server**: if your external nginx server is too old, the new configuration we generate for you in `/matrix/nginx-proxy/conf.d/` might not work anymore, because it mentions `TLSv1.3` and your nginx version might not support that. You can adjust the SSL protocol list by overriding the `matrix_nginx_proxy_ssl_protocols` variable. Learn more in the documentation page for [Using your own webserver, instead of this playbook's nginx proxy](docs/configuring-playbook-own-webserver.md)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3306
+msgid "**another web server**: you don't need to do anything to accommodate this change"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3309
+msgid "2019-01-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3311
+msgid "IRC bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3313
+msgid "[Devon Maloney (@Plailect)](https://github.com/Plailect) has done some great work bringing IRC bridging support via [matrix-appservice-irc](https://github.com/TeDomum/matrix-appservice-irc). To learn more, see the [Setting up Appservice IRC bridging](docs/configuring-playbook-bridge-appservice-irc.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3316
+msgid "2019-01-29"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3318
+msgid "Running container processes as non-root, without capabilities and read-only"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3320
+msgid "To improve security, this playbook no longer starts container processes as the `root` user. Most containers were dropping privileges anyway, but we were trusting them with `root` privileges until they would do that. Not anymore -- container processes now start as a non-root user (usually `matrix`) from the get-go."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3322
+msgid "For additional security, various capabilities are also dropped (see [why it's important](https://github.com/projectatomic/atomic-site/issues/203)) for all containers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3324
+msgid "Additionally, most containers now use a read-only filesystem (see [why it's important](https://www.projectatomic.io/blog/2015/12/making-docker-images-write-only-in-production/)). Containers are given write access only to the directories they need to write to."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3326
+msgid "A minor breaking change is the `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size` variable having being renamed to `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size_mb` (note the `_mb` suffix). The new variable expects a number value (e.g. `25M` -> `25`). If you weren't customizing this variable, this wouldn't affect you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3328
+msgid "matrix-mailer is now based on Exim, not Postfix"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3330
+msgid "While we would have preferred to stay with [Postfix](http://www.postfix.org/), we found out that it cannot run as a non-root user. We've had to replace it with [Exim](https://www.exim.org/) (via the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3332
+msgid "The internal `matrix-mailer` service (running in a container) now listens on port `8025` (used to be `587` before). The playbook will update your Synapse and mxisd email settings to match (`matrix-mailer:587` -> `matrix-mailer:8025`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3334
+msgid "Using the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image instead of [panubo/postfix](https://hub.docker.com/r/panubo/postfix/) also gives us a nice disk usage reduction (~200MB -> 8MB)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3337
+msgid "2019-01-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3339
+msgid "(BC Break) Making the playbook's roles more independent of one another"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3341
+msgid "The following change **affects people running a more non-standard setup** - external Postgres or using our roles in their own other playbook. **Most users don't need to do anything**, besides becoming aware of the new glue variables file [`group_vars/matrix-servers`](group_vars/matrix-servers)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3344
+msgid "Because people like using the playbook's components independently (outside of this playbook) and because it's much better for maintainability, we've continued working on separating them. Still, we'd like to offer a turnkey solution for running a fully-featured Matrix server, so this playbook remains important for wiring up the various components."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3346
+msgid "With the new changes, **all roles are now only dependent on the minimal `matrix-base` role**. They are no longer dependent among themselves."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3348
+msgid "In addition, the following components can now be completely disabled (for those who want/need to):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3349
+msgid "`matrix-coturn` by using `matrix_coturn_enabled: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3350
+msgid "`matrix-mailer` by using `matrix_mailer_enabled: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3351
+msgid "`matrix-postgres` by using `matrix_postgres_enabled: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3353
+msgid "The following changes had to be done:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3355
+msgid "glue variables had to be introduced to the playbook, so it can wire together the various components. Those glue vars are stored in the [`group_vars/matrix-servers`](group_vars/matrix-servers) file. When overriding variables for a given component (role), you need to be aware of both the role defaults (`role/ROLE/defaults/main.yml`) and the role's corresponding section in the [`group_vars/matrix-servers`](group_vars/matrix-servers) file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3357
+msgid "`matrix_postgres_use_external` has been superceeded by the more consistently named `matrix_postgres_enabled` variable and a few other `matrix_synapse_database_` variables. See the [Using an external PostgreSQL server (optional)](docs/configuring-playbook-external-postgres.md) documentation page for an up-to-date replacement."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3359
+msgid "Postgres tools (`matrix-postgres-cli` and `matrix-make-user-admin`) are no longer installed if you're not enabling the `matrix-postgres` role (`matrix_postgres_enabled: false`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3361
+msgid "roles, being more independent now, are more minimal and do not do so much magic for you. People that are building their own playbook using our roles will definitely need to take a look at the [`group_vars/matrix-servers`](group_vars/matrix-servers) file and adapt their playbooks with the same (or similar) wiring logic."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3364
+msgid "2019-01-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3366
+msgid "Splitting the playbook into multiple roles"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3368
+msgid "For better maintainability, the playbook logic (which all used to reside in a single `matrix-server` role) has been split out into a number of different roles: `matrix-synapse`, `matrix-postgres`, `matrix-riot-web`, `matrix-mxisd`, etc. (see the `roles/` directory)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3371
+msgid "To keep the filesystem more consistent with this separation, the **Postgres data had to be relocated**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3373
+msgid "The default value of `matrix_postgres_data_path` was changed from `/matrix/postgres` to `/matrix/postgres/data`. The `/matrix/postgres` directory is what we consider a base path now (new variable `matrix_postgres_base_path`). **Your Postgres data files will automatically be relocated by the playbook** (`/matrix/postgres/*` -> `/matrix/postgres/data/`) when you run with `--tags=setup-all` (or `--tags=setup-postgres`). While this shouldn't cause data-loss, **it's better if you do a Postgres backup just in case**. You'd need to restart all services after this migration (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3376
+msgid "2019-01-11"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3378
+msgid "(BC Break) mxisd configuration changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3380
+msgid "To be more flexible and to support the upcoming [mxisd](https://github.com/kamax-io/mxisd) 1.3.0 (when it gets released), we've had to redo how mxisd gets configured."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3383
+msgid "The following variables are no longer supported by this playbook:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3385
+msgid "`matrix_mxisd_ldap_enabled`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3386
+msgid "`matrix_mxisd_ldap_connection_host`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3387
+msgid "`matrix_mxisd_ldap_connection_tls`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3388
+msgid "`matrix_mxisd_ldap_connection_port`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3389
+msgid "`matrix_mxisd_ldap_connection_baseDn`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3390
+msgid "`matrix_mxisd_ldap_connection_baseDns`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3391 ../../../CHANGELOG.md:3392
+msgid "`matrix_mxisd_ldap_connection_bindDn`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3393 ../../../CHANGELOG.md:3397
+msgid "`matrix_mxisd_ldap_connection_bindPassword`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3394
+msgid "`matrix_mxisd_ldap_filter`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3395
+msgid "`matrix_mxisd_ldap_attribute_uid_type`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3396
+msgid "`matrix_mxisd_ldap_attribute_uid_value`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3398
+msgid "`matrix_mxisd_ldap_attribute_name`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3399
+msgid "`matrix_mxisd_ldap_attribute_threepid_email`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3400
+msgid "`matrix_mxisd_ldap_attribute_threepid_msisdn`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3401
+msgid "`matrix_mxisd_ldap_identity_filter`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3402
+msgid "`matrix_mxisd_ldap_identity_medium`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3403
+msgid "`matrix_mxisd_ldap_auth_filter`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3404
+msgid "`matrix_mxisd_ldap_directory_filter`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3405
+msgid "`matrix_mxisd_template_config`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3407
+msgid "You are encouraged to use the `matrix_mxisd_configuration_extension_yaml` variable to define your own mxisd configuration additions and overrides. Refer to the [default variables file](roles/custom/matrix-mxisd/defaults/main.yml) for more information."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3409
+msgid "This new way of configuring mxisd is beneficial because:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3411
+msgid "it lets us support all mxisd configuration options, as the playbook simply forwards them to mxisd without needing to care or understand them"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3412
+msgid "it lets you upgrade to newer mxisd versions and make use of their features, without us having to add support for them explicitly"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3415
+msgid "2019-01-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3417
+msgid "(BC Break) Cronjob schedule no longer configurable"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3419
+msgid "Due to the way we manage cronjobs now, you can no longer configure the schedule they're invoked at."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3421
+msgid "If you were previously using `matrix_ssl_lets_encrypt_renew_cron_time_definition` or `matrix_nginx_proxy_reload_cron_time_definition` to set a custom schedule, you should note that these variables don't affect anything anymore."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3424
+msgid "If you miss this functionality, please [open an Issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/new) and let us know about your use case!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3427
+msgid "2018-12-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3429
+msgid "(BC Break) More SSL certificate retrieval methods"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3431
+msgid "The playbook now lets you decide between 3 different SSL certificate retrieval methods:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3432
+msgid "(default) obtaining free SSL certificates from Let's Encrypt"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3433
+msgid "generating self-signed SSL certificates"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3434
+msgid "managing SSL certificates manually"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3436
+msgid "Learn more in [Adjusting SSL certificate retrieval](docs/configuring-playbook-ssl-certificates.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3438
+msgid "For people who use Let's Encrypt (mostly everyone, since it's the default), you'll also have to rename a variable in your configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3440
+msgid "before: `host_specific_matrix_ssl_support_email`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3441
+msgid "after: `host_specific_matrix_ssl_lets_encrypt_support_email`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3443
+msgid "(BC Break) mxisd upgrade with multiple base DN support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3445
+msgid "mxisd has bee upgraded to [version 1.2.2](https://github.com/kamax-matrix/mxisd/releases/tag/v1.2.2), which supports [multiple base DNs](https://github.com/kamax-matrix/mxisd/blob/v1.2.2/docs/stores/ldap.md#base)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3447
+msgid "If you were configuring this playbook's `matrix_mxisd_ldap_connection_baseDn` variable until now (a string containing a single base DN), you'll need to change to configuring the `matrix_mxisd_ldap_connection_baseDns` variable (an array containing multiple base DNs)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3449
+msgid "Example change:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3451
+msgid "before: `matrix_mxisd_ldap_connection_baseDn: OU=Users,DC=example,DC=org`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3452
+msgid "after: `matrix_mxisd_ldap_connection_baseDns: ['OU=Users,DC=example,DC=org']`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3455
+msgid "2018-12-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3457
+msgid "Synapse 0.34.0 and Python 3"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3459
+msgid "Synapse has been upgraded to 0.34.0 and now uses Python 3. Based on feedback from others, running Synapse on Python 3 is supposed to decrease memory usage significantly (~2x)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3462
+msgid "2018-12-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3464
+msgid "Riot homepage customization"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3466
+msgid "You can now customize some parts of the Riot homepage (or even completely replace it with your own custom page). See the `matrix_riot_web_homepage_` variables in `roles/custom/matrix-riot-web/defaults/main.yml`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3469
+msgid "2018-12-04"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3471
+msgid "mxisd extensibility"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3473
+msgid "The [LDAP identity store for mxisd](https://github.com/kamax-matrix/mxisd/blob/master/docs/stores/ldap.md) can now be configured easily using playbook variables (see the `matrix_mxisd_ldap_` variables in `roles/custom/matrix-server/defaults/main.yml`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3476
+msgid "2018-11-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3478
+msgid "More scripts"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3480
+msgid "matrix-remove-all allows to uninstall everything with a single command"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3481
+msgid "matrix-make-user-admin allows to upgrade a user's privileges"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3483
+msgid "LDAP auth support via matrix-synapse-ldap3"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3485
+msgid "The playbook can now install and configure [LDAP auth support](https://github.com/matrix-org/matrix-synapse-ldap3) for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3487
+msgid "Additional details are available in [Setting up the LDAP authentication password provider module](docs/configuring-playbook-ldap-auth.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3490
+msgid "2018-11-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3492
+msgid "Support for controlling public registration and room auto-join"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3494
+msgid "The playbook now lets you enable public registration for users (controlled via `matrix_synapse_enable_registration`). By default, public registration is forbidden."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3496
+msgid "You can also make people automatically get auto-joined to rooms (controlled via `matrix_synapse_auto_join_rooms`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3498
+msgid "Support for changing the welcome user ID (welcome bot)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3500
+msgid "By default, `@riot-bot:matrix.org` is used to welcome newly registered users. This can be changed to something else (or disabled) via the new `matrix_riot_web_welcome_user_id` variable."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3503
+msgid "2018-11-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3505
+msgid "Ability to set Synapse log levels"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3507
+msgid "The playbook now allows you to set the log levels used by Synapse. The default logging levels remain the same."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3509
+msgid "You can now override following variables with any of the supported log levels listed here: https://docs.python.org/3/library/logging.html#logging-levels"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3518
+msgid "2018-11-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3520
+msgid "Customize parts of Riot's config"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3522
+msgid "You can now customize some parts of Riot's `config.json`. These playbook variables, with these default values, have been added:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3533
+msgid "This now allows you use a custom integration manager like [Dimension](https://dimension.t2bot.io). For example, if you wish to use the Dimension instance hosted at dimension.t2bot.io, you can set the following in your vars.yml file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3542
+msgid "SSL protocols used to serve Riot and Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3544
+msgid "There's now a new `matrix_nginx_proxy_ssl_protocols` playbook variable, which controls the SSL protocols used to serve Riot and Synapse. Its default value is `TLSv1.1 TLSv1.2`. This playbook previously used `TLSv1 TLSv1.1 TLSv1.2` to serve Riot and Synapse."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3546
+msgid "You may wish to reenable TLSv1 if you need to access Riot in older browsers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3548
+msgid "Note: Currently the dockerized nginx doesn't support TLSv1.3. See https://github.com/nginxinc/docker-nginx/issues/190 for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3551
+msgid "2018-11-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3553
+msgid "Postgres 11 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3555
+msgid "The playbook now installs [Postgres 11](https://www.postgresql.org/about/news/1894/) by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3557
+msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x or 10.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3559 ../../../CHANGELOG.md:3646
+#: ../../../CHANGELOG.md:3766
+msgid "(BC Break) Renaming playbook variables"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3561
+msgid "Due to the large amount of features added to this playbook lately, to keep things manageable we've had to reorganize its configuration variables a bit."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3565
+msgid "from `matrix_docker_image_mxisd` to `matrix_mxisd_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3566
+msgid "from `matrix_docker_image_mautrix_telegram` to `matrix_mautrix_telegram_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3567
+msgid "from `matrix_docker_image_mautrix_whatsapp` to `matrix_mautrix_whatsapp_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3568
+msgid "from `matrix_docker_image_mailer` to `matrix_mailer_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3569
+msgid "from `matrix_docker_image_coturn` to `matrix_coturn_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3570
+msgid "from `matrix_docker_image_goofys` to `matrix_s3_goofys_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3571
+msgid "from `matrix_docker_image_riot` to `matrix_riot_web_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3572
+msgid "from `matrix_docker_image_nginx` to `matrix_nginx_proxy_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3573
+msgid "from `matrix_docker_image_synapse` to `matrix_synapse_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3574
+msgid "from `matrix_docker_image_postgres_v9` to `matrix_postgres_docker_image_v9`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3575
+msgid "from `matrix_docker_image_postgres_v10` to `matrix_postgres_docker_image_v10`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3576
+msgid "from `matrix_docker_image_postgres_latest` to `matrix_postgres_docker_image_latest`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3579
+msgid "2018-10-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3581
+msgid "Mautrix Whatsapp bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3583
+msgid "The playbook now supports bridging with [Whatsapp](https://www.whatsapp.com/) by installing the [mautrix-whatsapp](https://github.com/tulir/mautrix-whatsapp) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3585
+msgid "Additional details are available in [Setting up Mautrix Whatsapp bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3588
+msgid "2018-10-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3590
+msgid "Support for controlling Matrix federation"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3592
+msgid "The playbook can now help you with [Controlling Matrix federation](docs/configuring-playbook-federation), should you wish to run a more private (isolated) server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3595
+msgid "2018-10-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3597
+msgid "Disabling riot-web guests"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3599
+msgid "From now on, Riot's configuration setting `disable_guests` would be set to `true`. The homeserver was rejecting guests anyway, so this is just a cosmetic change affecting Riot's UI."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3602
+msgid "2018-10-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3604
+msgid "Self-check maintenance command"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3606
+msgid "The playbook can now [check if services are configured correctly](docs/maintenance-checking-services.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3609
+msgid "2018-10-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3611
+msgid "Presence tracking made configurable"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3613
+msgid "The playbook can now enable/disable user presence-status tracking in Synapse, through the playbook's `matrix_synapse_use_presence` variable (having a default value of `true` - enabled)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3615
+msgid "If users participate in large rooms with many other servers, disabling presence will decrease server load significantly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3618
+msgid "2018-09-27"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3620
+msgid "Synapse Cache Factor made configurable"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3622
+msgid "The playbook now makes the Synapse cache factor configurable, through the playbook's `matrix_synapse_cache_factor` variable (having a default value of `0.5`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3624
+msgid "Changing that value allows you to potentially decrease RAM usage or to increase performance by caching more stuff. Some information on it is available here: https://github.com/element-hq/synapse#help-synapse-eats-all-my-ram"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3627
+msgid "2018-09-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3629
+msgid "Disabling Docker container logging"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3631
+msgid "`--log-driver=none` is used for all Docker containers now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3633
+msgid "All these containers are started through systemd anyway and get logged in journald, so there's no need for Docker to be logging the same thing using the default `json-file` driver. Doing that was growing `/var/lib/docker/containers/..` infinitely until service/container restart."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3635
+msgid "As a result of this, things like `docker logs matrix-synapse` won't work anymore. `journalctl -u matrix-synapse` is how one can see the logs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3638
+msgid "2018-09-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3640
+msgid "Service discovery support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3642
+msgid "The playbook now helps you set up [service discovery](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery) using a `/.well-known/matrix/client` file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3644
+msgid "Additional details are available in [Configuring service discovery via .well-known](docs/configuring-well-known.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3650
+msgid "from `matrix_nginx_riot_web_data_path` to `matrix_riot_web_data_path`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3651
+msgid "from `matrix_riot_web_default_identity_server_url` to `matrix_identity_server_url`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3654
+msgid "2018-09-07"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3656
+msgid "Mautrix Telegram bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3658
+msgid "The playbook now supports bridging with [Telegram](https://telegram.org/) by installing the [mautrix-telegram](https://github.com/tulir/mautrix-telegram) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3660
+msgid "Additional details are available in [Setting up Mautrix Telegram bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3662
+msgid "Events cache size increase and configurability for Matrix Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3664
+msgid "The playbook now lets you configure Matrix Synapse's `event_cache_size` configuration via the `matrix_synapse_event_cache_size` playbook variable."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3666
+msgid "Previously, this value was hardcoded to `\"10K\"`. From now on, a more reasonable default of `\"100K\"` is used."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3668
+msgid "Password-peppering support for Matrix Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3670
+msgid "The playbook now supports enabling password-peppering for increased security in Matrix Synapse via the `matrix_synapse_password_config_pepper` playbook variable. Using a password pepper is disabled by default (just like it used to be before this playbook variable got introduced) and is not to be enabled/disabled after initial setup, as that would invalidate all existing passwords."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3672
+msgid "Statistics-reporting support for Matrix Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3674
+msgid "There's now a new `matrix_synapse_report_stats` playbook variable, which controls the `report_stats` configuration option for Matrix Synapse. It defaults to `false`, so no change is required to retain your privacy."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3676
+msgid "If you'd like to start reporting statistics about your homeserver (things like number of users, number of messages sent, uptime, load, etc.) to matrix.org, you can turn on stats reporting."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3679
+msgid "2018-08-29"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3681
+msgid "Changing the way SSL certificates are retrieved"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3683
+msgid "We've been using [acmetool](https://github.com/hlandau/acme) (with the [willwill/acme-docker](https://hub.docker.com/r/willwill/acme-docker/) Docker image) until now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3685
+msgid "Due to the Docker image being deprecated, and things looking bleak for acmetool's support of the newer ACME v2 API endpoint, we've switched to using [certbot](https://certbot.eff.org/) (with the [certbot/certbot](https://hub.docker.com/r/certbot/certbot/) Docker image)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3687
+msgid "Simply re-running the playbook will retrieve new certificates (via certbot) for you. To ensure you don't leave any old files behind, though, you'd better do this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3689
+msgid "`systemctl stop 'matrix*'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3690
+msgid "stop your custom webserver, if you're running one (only affects you if you've installed with `matrix_nginx_proxy_enabled: false`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3691
+msgid "`mv /matrix/ssl /matrix/ssl-acmetool-delete-later`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3692
+msgid "re-run the playbook's [installation](docs/installing.md)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3693
+msgid "possibly delete `/matrix/ssl-acmetool-delete-later`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3696
+msgid "2018-08-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3698
+msgid "Matrix Corporal support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3700
+msgid "The playbook can now install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3702
+msgid "Additional details are available in [Setting up Matrix Corporal](docs/configuring-playbook-matrix-corporal.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3705
+msgid "2018-08-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3707
+msgid "Matrix Synapse rate limit control variables"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3709
+msgid "The following new variables can now be configured to control Matrix Synapse's rate-limiting (default values are shown below)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3716
+msgid "Shared Secret Auth support via matrix-synapse-shared-secret-auth"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3718
+msgid "The playbook can now install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3720
+msgid "Additional details are available in [Setting up the Shared Secret Auth password provider module](docs/configuring-playbook-shared-secret-auth.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3723
+msgid "2018-08-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3725
+msgid "REST auth support via matrix-synapse-rest-auth"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3727
+msgid "The playbook can now install and configure [matrix-synapse-rest-auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3729
+msgid "Additional details are available in [Setting up the REST authentication password provider module](docs/configuring-playbook-rest-auth.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3731
+msgid "Compression improvements"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3733
+msgid "Shifted Matrix Synapse compression from happening in the Matrix Synapse, to happening in the nginx proxy that's in front of it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3736
+msgid "Additionally, `riot-web` also gets compressed now (in the nginx proxy), which drops the initial page load's size from 5.31MB to 1.86MB."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3739
+msgid "Disabling some unnecessary Synapse services"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3741
+msgid "The following services are not necessary, so they have been disabled:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3742
+msgid "on the federation port (8448): the `client` service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3743
+msgid "on the http port (8008, exposed over 443): the old Angular `webclient` and the `federation` service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3745
+msgid "Federation runs only on the federation port (8448) now. The Client APIs run only on the http port (8008) now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3748
+msgid "2018-08-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3750
+msgid "mxisd Identity Server support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3752
+msgid "The playbook now sets up an [mxisd](https://github.com/kamax-io/mxisd) Identity Server for you by default. Additional details are available in [Setting up ma1sd Identity Server](docs/configuring-playbook-mxisd.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3755
+msgid "2018-08-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3757
+msgid "Email-sending support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3759
+msgid "The playbook now configures an email-sending service (postfix) by default. Additional details are available in [Adjusting email-sending settings](docs/configuring-playbook-email.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3761
+msgid "With this, Matrix Synapse is able to send email notifications for missed messages, etc."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3764
+msgid "2018-08-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3770
+msgid "from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3771
+msgid "from `matrix_max_log_file_size_mb` to `matrix_synapse_max_log_file_size_mb`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3772
+msgid "from `matrix_max_log_files_count` to `matrix_synapse_max_log_files_count`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3773
+msgid "from `docker_matrix_image` to `matrix_docker_image_synapse`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3774
+msgid "from `docker_nginx_image` to `matrix_docker_image_nginx`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3775
+msgid "from `docker_riot_image` to `matrix_docker_image_riot`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3776
+msgid "from `docker_goofys_image` to `matrix_docker_image_goofys`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3777
+msgid "from `docker_coturn_image` to `matrix_docker_image_coturn`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3779
+msgid "If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3781
+msgid "Renaming Ansible playbook tag"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3783
+msgid "The command for executing the whole playbook has changed. The `setup-main` tag got renamed to `setup-all`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3785
+msgid "Docker container linking"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3787
+msgid "Changed the way the Docker containers are linked together. The ones that need to communicate with others operate in a `matrix` network now and not in the default bridge network."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/README.po b/i18n/locales/bg/LC_MESSAGES/README.po
new file mode 100644
index 000000000..653a76b8b
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/README.po
@@ -0,0 +1,1183 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: 2024-12-20 14:56+0200\n"
+"Last-Translator: \n"
+"Language-Team: bg <LL@li.org>\n"
+"Language: bg\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../../README.md:1
+msgid "[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)"
+msgstr "[![Matrix стая за поддържка](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)"
+
+#: ../../../README.md:1
+msgid "Support room on Matrix"
+msgstr "Matrix стая за поддръжка"
+
+#: ../../../README.md:1
+msgid "donate"
+msgstr "дарения"
+
+#: ../../../README.md:3
+msgid "Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker"
+msgstr "Настройка на Matrix (отворена мрежа за сигурна децентрализирана комуникация) чрез Ansible и Docker"
+
+#: ../../../README.md:5
+msgid "🎯 Purpose"
+msgstr "🎯 Цел"
+
+#: ../../../README.md:7
+msgid "This [Ansible](https://www.ansible.com/) playbook is meant to help you run your own [Matrix](http://matrix.org/) homeserver, along with the [various services](#supported-services) related to that."
+msgstr "Този [Ansible](https://www.ansible.com/) плейбук има за цел да ви помогне да стартирате свой собствен [Matrix](http://matrix.org/) домашен сървър, заедно с [различните услуги](#-поддържани-услуги) около него."
+
+#: ../../../README.md:9
+msgid "That is, it lets you join the Matrix network using your own user ID like `@alice:example.com`, all hosted on your own server (see [prerequisites](docs/prerequisites.md))."
+msgstr "С други думи, позволява ви да се присъедините към Matrix мрежата със собствен сървър (вижте [предварителни условия](docs/prerequisites.md)) използвайки потребителско име като `@alice:example.com`."
+
+#: ../../../README.md:11
+msgid "We run all [supported services](#-supported-services) in [Docker](https://www.docker.com/) containers (see [the container images we use](docs/container-images.md)), which lets us have a predictable and up-to-date setup, across multiple supported distros (see [prerequisites](docs/prerequisites.md)) and [architectures](docs/alternative-architectures.md) (x86/amd64 being recommended)."
+msgstr "Подкарваме всички [поддържани услуги](#-поддържани-услуги) в [Docker](https://www.docker.com/) контейнери (вижте [използваните контейнер image-и](docs/container-images.md)), което ни позволява да имаме предсказуема и в крак с времето инсталация, без значение от операционната система (вижте [предварителните условия](docs/prerequisites.md)) и [архитектура](docs/alternative-architectures.md) (препоръчва се x86/amd64)."
+
+#: ../../../README.md:13
+msgid "Installation (upgrades) and some maintenance tasks are automated using [Ansible](https://www.ansible.com/) (see [our Ansible guide](docs/ansible.md))."
+msgstr "Инсталацията (обновленията) и някои задачи по поддръжката са автоматизирани чрез [Ansible](https://www.ansible.com/) (вижте [нашия Ansible наръчник](docs/ansible.md))."
+
+#: ../../../README.md:15
+msgid "☁ Self-hosting or Managed / SaaS"
+msgstr "☁ Самостоятелно хостване или Управлявано / SaaS"
+
+#: ../../../README.md:17
+msgid "This Ansible playbook tries to make self-hosting and maintaining a Matrix server fairly easy (see [Getting started](#-getting-started)). Still, running any service smoothly requires knowledge, time and effort."
+msgstr "Този Ansible плейбук се стреми да направи самостоятелното хостване и поддръжка на Matrix сървър лесно (вижте [Стартиране](#-стартиране)). Въпреки това, поддържането на коя да е услуга изисква знания, време и усилия."
+
+#: ../../../README.md:19
+msgid "If you like the [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) spirit of this Ansible playbook, but prefer to put the responsibility on someone else, you can also [get a managed Matrix server from etke.cc](https://etke.cc?utm_source=github&utm_medium=readme&utm_campaign=mdad) (both hosting and on-premises) - a service built on top of this Ansible playbook but with [additional components](https://etke.cc/help/extras/?utm_source=github&utm_medium=readme&utm_campaign=mdad) and [services](https://etke.cc/services/?utm_source=github&utm_medium=readme&utm_campaign=mdad) which all help you run a Matrix server with ease. Be advised that etke.cc operates on a subscription-based approach and there is no \"just set up my server once and be done with it\" option."
+msgstr ""
+
+#: ../../../README.md:21
+msgid "🚀 Getting started"
+msgstr "🚀 Стартиране"
+
+#: ../../../README.md:23
+msgid "We have detailed documentation in the [docs/](./docs) directory - see the Table of Contents in the [documentation README](./docs/README.md)."
+msgstr ""
+
+#: ../../../README.md:25
+msgid "While the [list of supported services](#-supported-services) and documentation is very extensive, you don't need to read through everything. We recommend:"
+msgstr ""
+
+#: ../../../README.md:27
+msgid "Starting with the basics. You can always add/remove or tweak services later on."
+msgstr ""
+
+#: ../../../README.md:29
+msgid "Following our installation guide. There are two guides available for beginners and advanced users:"
+msgstr ""
+
+#: ../../../README.md:31
+msgid "⚡ **[Quick start](./docs/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 ""
+
+#: ../../../README.md:33
+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](./docs/prerequisites.md)** documentation page."
+msgstr ""
+
+#: ../../../README.md:35
+msgid "If you experience an issue on configuring the playbook, setting up your server, maintaining services on it, etc., please take a look at our [FAQ](./docs/faq.md). If you cannot find an answer to your question, feel free to ask for [help and support](#-support)."
+msgstr ""
+
+#: ../../../README.md:37
+msgid "✔ Supported services"
+msgstr "✔ Поддържани услуги"
+
+#: ../../../README.md:39
+msgid "Using this playbook, you can get the following list of services configured on your server. Basically, this playbook aims to get you up-and-running with all the necessities around Matrix, without you having to do anything else."
+msgstr ""
+
+#: ../../../README.md:41
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../README.md:43
+msgid "The list below is exhaustive. It includes optional or even some advanced components that you will most likely not need. Sticking with the defaults (which install a subset of the above components) is the best choice, especially for a new installation. You can always re-run the playbook later to add or remove components."
+msgstr ""
+
+#: ../../../README.md:45
+msgid "Deprecated or unmaintained services are not listed. You can find documentations for them [here](docs/configuring-playbook.md#deprecated--unmaintained--removed-services)."
+msgstr ""
+
+#: ../../../README.md:47
+msgid "Homeserver"
+msgstr ""
+
+#: ../../../README.md:49
+msgid "The homeserver is the backbone of your Matrix system. Choose one from the following list."
+msgstr ""
+
+#: ../../../README.md
+msgid "Name"
+msgstr ""
+
+#: ../../../README.md
+msgid "Default?"
+msgstr ""
+
+#: ../../../README.md
+msgid "Description"
+msgstr ""
+
+#: ../../../README.md
+msgid "Documentation"
+msgstr "Документация"
+
+#: ../../../README.md
+msgid "[Synapse](https://github.com/element-hq/synapse)"
+msgstr ""
+
+#: ../../../README.md
+msgid "✅"
+msgstr ""
+
+#: ../../../README.md
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-synapse.md)"
+msgstr "[Връзка](docs/configuring-playbook-synapse.md)"
+
+#: ../../../README.md
+msgid "[Conduit](https://conduit.rs)"
+msgstr "[Conduit](https://conduit.rs)"
+
+#: ../../../README.md
+msgid "❌"
+msgstr ""
+
+#: ../../../README.md
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-conduit.md)"
+msgstr "[Връзка](docs/configuring-playbook-conduit.md)"
+
+#: ../../../README.md
+msgid "[Dendrite](https://github.com/matrix-org/dendrite)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-dendrite.md)"
+msgstr ""
+
+#: ../../../README.md:57
+msgid "Clients"
+msgstr "Клиенти"
+
+#: ../../../README.md:59
+msgid "Web clients for Matrix that you can host on your own domains."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Element Web](https://github.com/element-hq/element-web)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Default Matrix web client, configured to connect to your own Synapse server"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-client-element-web.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Hydrogen](https://github.com/element-hq/hydrogen-web)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Lightweight Matrix client with legacy and mobile browser support"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-client-hydrogen.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Cinny](https://github.com/ajbura/cinny)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Simple, elegant and secure web client"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-client-cinny.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[SchildiChat Web](https://schildi.chat/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Based on Element Web, with a more traditional instant messaging experience"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-client-schildichat-web.md)"
+msgstr ""
+
+#: ../../../README.md:68
+msgid "Server Components"
+msgstr ""
+
+#: ../../../README.md:70
+msgid "Services that run on the server to make the various parts of your installation work."
+msgstr ""
+
+#: ../../../README.md
+msgid "[PostgreSQL](https://www.postgresql.org/)"
+msgstr "[PostgreSQL](https://www.postgresql.org/)"
+
+#: ../../../README.md
+msgid "Database for Synapse. [Using an external PostgreSQL server](docs/configuring-playbook-external-postgres.md) is also possible."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-external-postgres.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Coturn](https://github.com/coturn/coturn)"
+msgstr ""
+
+#: ../../../README.md
+msgid "STUN/TURN server for WebRTC audio/video calls"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-turn.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Traefik](https://doc.traefik.io/traefik/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](docs/configuring-playbook-own-webserver.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-traefik.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Let's Encrypt](https://letsencrypt.org/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Free SSL certificate, which secures the connection to all components"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-ssl-certificates.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Exim](https://www.exim.org/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-email.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[ma1sd](https://github.com/ma1uta/ma1sd)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Matrix Identity Server"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-ma1sd.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[ddclient](https://github.com/linuxserver/docker-ddclient)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Dynamic DNS"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-dynamic-dns.md)"
+msgstr "[Връзка](docs/configuring-playbook-dynamic-dns.md)"
+
+#: ../../../README.md:82
+msgid "Authentication"
+msgstr ""
+
+#: ../../../README.md:84
+msgid "Extend and modify how users are authenticated on your homeserver."
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) (advanced)"
+msgstr ""
+
+#: ../../../README.md
+msgid "REST authentication password provider module"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-rest-auth.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) (advanced)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Password provider module"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-shared-secret-auth.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) (advanced)"
+msgstr ""
+
+#: ../../../README.md
+msgid "LDAP Auth password provider module"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-ldap-auth.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) (advanced)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A proxy that handles Matrix registration requests and forwards them to LDAP."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-matrix-ldap-registration-proxy.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-registration](https://github.com/ZerataX/matrix-registration)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A simple python application to have a token based Matrix registration"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-matrix-registration.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (UVS)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Service to verify details of a user based on an Open ID token"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-user-verification-service.md)"
+msgstr "[Връзка](docs/configuring-playbook-user-verification-service.md)"
+
+#: ../../../README.md
+msgid "[synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) (advanced)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A spam checker module"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-synapse-simple-antispam.md)"
+msgstr ""
+
+#: ../../../README.md:96
+msgid "File Storage"
+msgstr ""
+
+#: ../../../README.md:98
+msgid "Use alternative file storage to the default `media_store` folder."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Goofys](https://github.com/kahing/goofys)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-s3-goofys.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-s3.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-media-repo](https://github.com/turt2live/matrix-media-repo)"
+msgstr ""
+
+#: ../../../README.md
+msgid "matrix-media-repo is a 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 ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-matrix-media-repo.md)"
+msgstr ""
+
+#: ../../../README.md:106
+msgid "Bridges"
+msgstr ""
+
+#: ../../../README.md:108
+msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-discord](https://github.com/mautrix/discord)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Discord](https://discord.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-discord.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-slack](https://github.com/mautrix/slack)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Slack](https://slack.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-slack.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-telegram](https://github.com/mautrix/telegram)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Telegram](https://telegram.org/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-telegram.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-gmessages](https://github.com/mautrix/gmessages)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Google Messages](https://messages.google.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-gmessages.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-whatsapp](https://github.com/mautrix/whatsapp)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [WhatsApp](https://www.whatsapp.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-whatsapp.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-wsproxy](https://github.com/mautrix/wsproxy)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to Android SMS or Apple iMessage"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-wsproxy.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-twitter](https://github.com/mautrix/twitter)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Twitter](https://twitter.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-twitter.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-googlechat](https://github.com/mautrix/googlechat)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-googlechat.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-meta](https://github.com/mautrix/instagram)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Link for [Messenger](docs/configuring-playbook-bridge-mautrix-meta-messenger.md) / [Instagram](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-signal](https://github.com/mautrix/signal)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Signal](https://www.signal.org/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-signal.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[beeper-linkedin](https://github.com/beeper/linkedin)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [LinkedIn](https://www.linkedin.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-beeper-linkedin.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-appservice-irc.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-appservice-kakaotalk.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Discord](https://discordapp.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-appservice-discord.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-appservice-slack.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-hookshot](https://github.com/matrix-org/matrix-hookshot)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-hookshot.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to SMS"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-matrix-bridge-sms.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-wechat](https://github.com/duo/matrix-wechat)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [WeChat](https://www.wechat.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-wechat.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Heisenbridge](https://github.com/hifi/heisenbridge)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-heisenbridge.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[go-skype-bridge](https://github.com/kelaresg/go-skype-bridge)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Skype](https://www.skype.com)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-go-skype-bridge.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Slack](https://slack.com)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-slack.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-instagram.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-twitter.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-discord.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [GroupMe](https://groupme.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-groupme.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Steam](https://steamapp.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-steam.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Email2Matrix](https://github.com/devture/email2matrix)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge for relaying emails to Matrix rooms"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-email2matrix.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Postmoogle](https://github.com/etkecc/postmoogle)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Email to Matrix bridge"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-postmoogle.md)"
+msgstr ""
+
+#: ../../../README.md:141
+msgid "Bots"
+msgstr ""
+
+#: ../../../README.md:143
+msgid "Bots provide various additional functionality to your installation."
+msgstr ""
+
+#: ../../../README.md
+msgid "[baibot](https://github.com/etkecc/baibot)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bot-baibot.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bot for scheduling one-off & recurring reminders and alarms"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bot-matrix-reminder-bot.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bot for invitations by creating and managing registration tokens"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bot-matrix-registration-bot.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[maubot](https://github.com/maubot/maubot)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A plugin-based Matrix bot system"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bot-maubot.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Honoroit](https://github.com/etkecc/honoroit)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A helpdesk bot"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bot-honoroit.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Mjolnir](https://github.com/matrix-org/mjolnir)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A moderation tool for Matrix"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bot-mjolnir.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Draupnir](https://github.com/the-draupnir-project/Draupnir)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A moderation tool for Matrix (Fork of Mjolnir)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bot-draupnir.md) (for [appservice mode](docs/configuring-playbook-appservice-draupnir-for-all.md))"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Buscarron](https://github.com/etkecc/buscarron)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Web forms (HTTP POST) to Matrix"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bot-buscarron.md)"
+msgstr ""
+
+#: ../../../README.md:156
+msgid "Administration"
+msgstr ""
+
+#: ../../../README.md:158
+msgid "Services that help you in administrating and monitoring your Matrix installation."
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-alertmanager-receiver.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "OAuth 2.0 and OpenID Provider server"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-matrix-authentication-service.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[synapse-admin](https://github.com/etkecc/synapse-admin)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A web UI tool for administrating users and rooms on your Matrix server"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-synapse-admin.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Metrics and Graphs"
+msgstr ""
+
+#: ../../../README.md
+msgid "Consists of the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI, with [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) being available too"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-nginxlog.md))"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Borg](https://borgbackup.org)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Backups"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-backup-borg.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[rageshake](https://github.com/matrix-org/rageshake)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bug report server"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-rageshake.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-synapse-usage-exporter.md)"
+msgstr ""
+
+#: ../../../README.md:170
+msgid "Misc"
+msgstr ""
+
+#: ../../../README.md:172
+msgid "Various services that don't fit any other categories."
+msgstr ""
+
+#: ../../../README.md
+msgid "[sliding-sync](https://github.com/matrix-org/sliding-sync)"
+msgstr ""
+
+#: ../../../README.md
+msgid "(Superseded by Simplified Sliding Sync integrated into Synapse > `1.114` and Conduit > `0.6.0`) Sliding Sync support for clients which require it (e.g. old Element X versions before Simplified Sliding Sync was developed)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-sliding-sync-proxy.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-accept-invite)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A Synapse module to automatically accept invites."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-synapse-auto-accept-invite.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A cli tool that automatically compresses `state_groups` database table in background."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-synapse-auto-compressor.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Matrix Corporal](https://github.com/devture/matrix-corporal) (advanced)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Reconciliator and gateway for a managed Matrix server"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-matrix-corporal.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Etherpad](https://etherpad.org)"
+msgstr ""
+
+#: ../../../README.md
+msgid "An open source collaborative text editor"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-etherpad.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Jitsi](https://jitsi.org/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "An open source video-conferencing platform"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-jitsi.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Cactus Comments](https://cactus.chat)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A federated comment system built on Matrix"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-cactus-comments.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Pantalaimon](https://github.com/matrix-org/pantalaimon)"
+msgstr ""
+
+#: ../../../README.md
+msgid "An E2EE aware proxy daemon"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-pantalaimon.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Sygnal](https://github.com/matrix-org/sygnal)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Push gateway"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-sygnal.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[ntfy](https://ntfy.sh)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Push notifications server"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-ntfy.md)"
+msgstr ""
+
+#: ../../../README.md:187
+msgid "🆕 Changes"
+msgstr ""
+
+#: ../../../README.md:189
+msgid "This playbook evolves over time, sometimes with backward-incompatible changes."
+msgstr "Този плейбук се развива във времето и понякога съдържа обратно-несъвместими промени."
+
+#: ../../../README.md:191
+msgid "When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up with what's new."
+msgstr ""
+
+#: ../../../README.md:193
+msgid "🆘 Support"
+msgstr ""
+
+#: ../../../README.md:195
+msgid "Matrix room: [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)"
+msgstr ""
+
+#: ../../../README.md:197
+msgid "IRC channel: `#matrix-docker-ansible-deploy` on the [Libera Chat](https://libera.chat/) IRC network (irc.libera.chat:6697)"
+msgstr ""
+
+#: ../../../README.md:199
+msgid "GitHub issues: [spantaleev/matrix-docker-ansible-deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues)"
+msgstr ""
+
+#: ../../../README.md:201
+msgid "🌐 Translation"
+msgstr ""
+
+#: ../../../README.md:203
+msgid "See the [i18n/README.md](i18n/README.md) file for more information about translation."
+msgstr "Вижте файла [i18n/README.md](i18n/README.md) за повече информация относно превода."
+
+#: ../../../README.md:205
+msgid "Translations are still work in progress."
+msgstr "Все още се работи по преводите."
+
+#: ../../../README.md:207
+msgid "🤝 Related"
+msgstr ""
+
+#: ../../../README.md:209
+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
+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 ""
diff --git a/i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po b/i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po
new file mode 100644
index 000000000..70d2e7f11
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/YEAR-IN-REVIEW.po
@@ -0,0 +1,290 @@
+# Translations template for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\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"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../YEAR-IN-REVIEW.md:1
+msgid "2023"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:3
+msgid "2023 was a year filled with many changes for matrix-docker-ansible-deploy. In this post, we're looking backward at some of the major changes that happened this year, as well as taking a glimpse of what's ahead in 2024."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:5
+msgid "2023 is probably [the year of AI](https://journal.everypixel.com/2023-the-year-of-ai), with millions of people jumping aboard [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/chatgpt) train. matrix-docker-ansible-deploy is no stranger to this and 2023 began with a PR from [bertybuttface](https://github.com/bertybuttface) who added support for [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#chatgpt-support)). While OpenAI's chat GPT website was frequently overloaded in the past, their API was up which made using this bot both convenient and more reliable."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:7
+msgid "AI aside, with the playbook's focus being containers, we're **doubling down on being \"container native\"** and becoming more interoperable for people hosting other containers on the Matrix server. In [2022](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/YEAR-IN-REVIEW.md#2022), we've announced a few sibling Ansible playbooks, their use of [Traefik](https://doc.traefik.io/traefik/) and the possiblity of matrix-docker-ansible-deploy also switching to this reverse-proxy. This prediction materialized quickly. The **largest change** in the playbook in 2023 happened way back in February - matrix-docker-ansible-deploy [starting the switch from nginx to Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support) and then quickly [making Treafik the default reverse-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#traefik-is-the-default-reverse-proxy-now). As noted in the changelog entries, we envisioned a quick and complete elimination of `matrix-nginx-proxy`, but at the end of 2023, it hasn't happened yet. The playbook is already using Traefik as the front-most reverse-proxy, but nginx (via `matrix-nginx-proxy`) is still around - it has taken a step back and is only used internally for new setups. Work got to a stall due to:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:9
+msgid "complexity: untangling the overly large and messy `matrix-nginx-proxy` component is difficult"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:10
+msgid "the current setup became \"good enough\" because nginx has become an internal implementation detail for those who have migrated to Traefik. Traefik is already the default public reverse-proxy and gives better possibilities to people wishing to run other web-exposed containers on their Matrix server via [Docker Compose](https://docs.docker.com/compose/), other Ansible playbooks like [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) (more about this one, below) or any other way."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:12
+msgid "`matrix-nginx-proxy` is no longer in the way of us being interoperable, but its ugly internal details are still there. It is one more proxy in the long chain of reverse-proxies we have and we'd like to cut it out. This would both make things simpler and also boost performance."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:14
+msgid "The delay in eliminating `matrix-nginx-proxy` has probably been welcome by many existing users who decided to postpone the Traefik migration a bit longer. In 2024, work on eliminating `matrix-nginx-proxy` will continue with rapid pace. People who are still using `matrix-nginx-proxy` as their front-most reverse-proxy will need to rework their setup. About a year of putting it off has been long enough."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:16
+msgid "This large Traefik reverse-proxy change was also accompanied by another internal change which began in 2022, but continued in 2023 - **moving non-Matrix-related roles from being internal to the playbook to living their own life outside of it**. Various roles were made more decoupled and moved outside of the playbook, so that other projects (like the [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook or other Ansible playbooks) could benefit from them. This led to the **death of a few sibling playbooks** ([gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy), [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), [peertube-docker-ansible-deploy](https://github.com/spantaleev/peertube-docker-ansible-deploy), [vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy)), but brought life to something better, which supports all these services and more."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:18
+msgid "[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) is a new Ansible playbook that a few of us (matrix-docker-ansible-deploy contributors) have launched in 2023. It has quickly grown to supports [60+ services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md) and aims to do the same for [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) service hosting, as matrix-docker-ansible-deploy has done for Matrix - providing a clean and secure way to run a bunch of services in containers on a regular server (that is to say, without Kubernetes, etc.). Thanks to Traefik and Ansible role reuse, it's easy to host both mash-playbook services and matrix-docker-ansible-deploy services on the same server - see mash-playbook's [interoperability](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md) documentation page. If you've been looking for a holiday project or your New Year's Resolutions list contains \"self-hosting more services\", then you're welcome to give this new playbook a try and join its Matrix room ([#mash-playbook:devture.com](https://matrix.to/#/#mash-playbook:devture.com))."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:20
+msgid "Because many of the roles are now external to this playbook (defined in the [requirements.yml](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/da27655ef34999fa924bc0a5e641dbd9ba06f133/requirements.yml) file), running `make roles` (or better yet `just roles` via the [just tool](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#support-for-running-commands-via-just)) becomes a necessity each time one pulls playbook updates (`git pull`). Pulling external roles happens via the [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) command-line tool, but if available, the playbook would also use the much faster [agru](https://github.com/etkecc/agru) tool (developed by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) this year)."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:22
+msgid "With the internal (but important) details out of the way, we can now talk more about **new features that landed in matrix-docker-ansible-deploy in 2023**."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:24
+msgid "The following **new** **bridges** were added to the playbook in 2023:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:26
+msgid "(2023-01-11) [mautrix-slack](https://mau.dev/mautrix/slack), thanks to a PR by [Cody Neiman](https://github.com/xangelix) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#mautrix-slack-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:27
+msgid "(2023-07-21) [mautrix-gmessages](https://github.com/mautrix/gmessages), thanks to a PR by [Shreyas Ajjarapu](https://github.com/shreyasajj) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#mautrix-gmessages-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:28
+msgid "(2023-08-23) [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for Apple iMessage bridging (when combined with the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android phone), thanks to a PR by [Johan Swetzén](https://github.com/jswetzen)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:30
+msgid "This brings the total number of **[bridges that the playbook supports](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/docs/configuring-playbook.md#bridging-other-networks) up to 30**. There are alternative bridge implementations for various networks and protocols, so the number of \"unique bridged networks\" is surely much smaller."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:32
+msgid "A few other **major components and changes** landed in 2023:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:34
+msgid "(2023-02-10) The [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (successor to [Mjolnir](https://github.com/matrix-org/mjolnir)), thanks to a PR by [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#draupnir-moderation-tool-bot-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:35
+msgid "(2023-02-10) [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) to add Matrix Authentication Support to our Jitsi setup, thanks to a PR by [Jakob S.](https://github.com/jakicoll) from [zakk gGmbH](https://github.com/zakk-it) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-authentication-support-for-jitsi))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:36
+msgid "(2023-02-25) The [rageshake](https://github.com/matrix-org/rageshake) bug report server, thanks to a PR by [Benjamin Kampmann](https://github.com/gnunicorn) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#rageshake-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:37
+msgid "(2023-03-07) [Sliding Sync proxy](https://github.com/matrix-org/sliding-sync) (currently a necessary component for [Element X](https://element.io/labs/element-x) to work), thanks to: [Benjamin Kampmann](https://github.com/gnunicorn) and [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#sliding-sync-proxy-element-x-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:38
+msgid "(2023-03-12) synapse-auto-compressor to periodically and automatically run [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#synapse-auto-compressor-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:39
+msgid "(2023-07-17) [matrix-media-repo](https://github.com/turt2live/matrix-media-repo),  thanks to a PR by [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-media-repo-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:40
+msgid "(2023-08-31) [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client app (fork of [Element Web)](https://github.com/element-hq/element-web), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#schildichat-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:41
+msgid "(2023-10-18) Postgres parameters auto-tuning, thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#postgres-parameters-are-automatically-tuned-now))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:42
+msgid "(2023-10-23) Enabling federation of the room directory for Synapse (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#enabling-allow_public_rooms_over_federation-by-default-for-synapse))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:44
+msgid "The most recent change in the list above (Enabling federation of the room directory for Synapse) has been somewhat **controversial** as it goes against upstream defaults for Synapse. Nevertheless, we believe it **promotes the well-being of the Matrix Federation by improving room discovery**."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:46
+msgid "**Matrix Federation Stats** (containing the percentage of servers publishing their room directory publicly) are posted to [TWIM](https://matrix.org/category/this-week-in-matrix/) each week by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/). The number of servers which [currently published their room directory publicly](https://matrix.org/blog/2023/12/2/this-week-in-matrix-2023-12-22/#matrix-federation-stats) stands at `26.6%`, which is:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:48
+msgid "**2.4% more** than when it was when [first published to TWIM](https://matrix.org/blog/2023/11/03/this-week-in-matrix-2023-11-03/#matrix-federation-stats) (1 month earlier, in November)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:49
+msgid "likely about **15+% more** than from before we flipped the switch (in October)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:51
+msgid "Hopefully, Synapse defaults would also change the same way and we'd see the number of servers publicly listing their room directory grow faster."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:53
+msgid "With this configuration change in place, projects like [MatrixRooms.info](https://matrixrooms.info/) (made by [etke.cc](https://etke.cc/)) and potentially others in the future, can discover, index the metadata (room address, title, topic, number of users, etc.) and make public rooms browsable & searchable across the whole Matrix Federation. It'd be great if users joining Matrix could more easily find interesting communities that match their interests!"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:55
+msgid "On the **media side of things**, besides Jitsi getting better Matrix integration (via the aforementioned Matrix User Verification Service), we've also had some [Coturn security tightening](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues) as well as [performance optimizations](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#coturn-can-now-use-host-networking) for configurations exposing lots of network ports."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:57
+msgid "[Element Call](https://github.com/element-hq/element-call) seems to have become a nice and polished product lately (as proclaimed in [The Matrix Holiday Update 2023](https://matrix.org/blog/2023/12/25/the-matrix-holiday-update-2023/)), so 2024 is likely the year we'll see support for it in the playbook. Element Call depends on the [LiveKit](https://livekit.io/) streaming server (which is also useful to developers even by itself), so the first step is likely to see LiveKit support in mash-playbook via a reusable Ansible role. Such a LiveKit Ansible role could later easily land in matrix-docker-ansible-deploy and an Element Call static website could be hooked to it."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:59
+msgid "Besides these highlights, there were many other relatively large changes announced in our [CHANGELOG](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md) and hundreds of other more minor (but still important) playbook changes that didn't get a mention."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:61
+msgid "We have **hundreds of contributors to thank for their hard work** on making Matrix self-hosting better for all of us! It should be noted that **support comes in many shapes**, not only in raw code commits and financial help (via [donations](https://liberapay.com/s.pantaleev) or using the [etke.cc managed Matrix hosting service](https://etke.cc/) which is based on matrix-docker-ansible-deploy). It also comes in the shape of code reviews, helping others with [issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues), reporting new issues, participating in our support room on Matrix ([#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)), etc. To everyone who has been there to make matrix-docker-ansible-deploy better in 2023, thank you! 🙇‍♂️"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:64
+msgid "2022"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:66
+msgid "For [matrix-docker-ansible-deploy](https://github.com/spantaleev/matrix-docker-ansible-deploy/), 2022 started with **breaking the** [**Synapse**](https://github.com/element-hq/synapse) **monopoly** by [adding support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#dendrite-support) for the [Dendrite](https://github.com/matrix-org/dendrite) Matrix homeserver in early January. This required various internal changes so that the [Ansible](https://www.ansible.com/) playbook would not be Synapse-centric anymore. This groundwork paved the way for continuing in this direction and we [added support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#conduit-support) for [Conduit](https://conduit.rs/) in August."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:68
+msgid "When it comes to the `matrix-docker-ansible-deploy` Ansible playbook, 2022 was the year of the non-Synapse homeserver implementation. In practice, none of these homeserver implementations seem ready for prime-time yet and there is no migration path when coming from Synapse. Having done our job of adding support for these alternative homeserver implementations, we can say that we're not getting in the way of future progress. It's time for the Dendrite developers to push harder (development-wise) and for the Synapse developers to take a well-deserved long (infinite) break, and we may get to see more people migrating away from Synapse in the next year(s)."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:70
+msgid "Support for the following new **bridges** was added:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:72
+msgid "[Postmoogle](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#postmoogle-email-bridge-support) for bi-directional email bridging, which supersedes my old and simplistic [email2matrix](https://github.com/devture/email2matrix) one-way bridge-bot"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:73
+msgid "[mautrix-discord](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#mautrix-discord-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:74
+msgid "[go-skype-bridge](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#go-skype-bridge-bridging-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:75
+msgid "[matrix-appservice-kakaotalk](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-appservice-kakaotalk-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:77
+msgid "Support for the following new **bots** was added:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:79
+msgid "[buscarron bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#buscarron-bot-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:80
+msgid "[Honoroit bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#honoroit-bot-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:81
+msgid "[matrix-registration-bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-registration-bot-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:82
+msgid "[matrix-hookshot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-hookshot-bridging-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:83
+msgid "[maubot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#maubot-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:85
+msgid "Support for the following new **components and services** was added:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:87
+msgid "[BorgBackup](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#borg-backup-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:88
+msgid "[Cactus Comments](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cactus-comments-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:89
+msgid "[Cinny](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cinny-support) client support"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:90
+msgid "[ntfy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#ntfy-push-notifications-support) notifications"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:91
+msgid "[matrix-ldap-registration-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-ldap-registration-proxy-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:92
+msgid "[matrix\\_encryption\\_disabler support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix_encryption_disabler-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:93
+msgid "[synapse-s3-storage-provider](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-s3-storage-provider-support) to stop the Synapse media store from being a scalability problem. This brought along [another feature](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-container-image-customization-support) - an easier way to customize the Synapse container image without having to fork and self-build all of it from scratch"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:95
+msgid "Besides these major user-visible changes, a lot of work also happened **under the hood**:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:97
+msgid "we made [major improvements to Synapse workers](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#potential-backward-compatibility-break-major-improvements-to-synapse-workers) - adding support for stream writers and for running multiple workers of various kinds (federation senders, pushers, background task processing workers, etc.)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:98
+msgid "we [improved the compatibility of (Synapse + workers) with the rest of the playbook](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#backward-compatibility-break-changing-how-reverse-proxying-to-synapse-works---now-via-a-matrix-synapse-reverse-proxy-companion-service) by introducing a new `matrix-synapse-reverse-proxy-companion-service` service"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:99
+msgid "we started [splitting various Ansible roles out of the Matrix playbook and into independent roles](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#the-playbook-now-uses-external-roles-for-some-things) (e.g. `matrix-postgres` -> [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres)), which could be included in other Ansible playbooks. In fact, these roles already power a few **interesting other sibling playbooks**:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:100
+msgid "[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy), for deploying a [Gitea](https://gitea.io/) (self-hosted [Git](https://git-scm.com/) service) server"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:101
+msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), for deploying a [Nextcloud](https://nextcloud.com/) groupware server"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:102
+msgid "[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy), for deploying a [Vaultwarden](https://github.com/dani-garcia/vaultwarden) password manager server (unofficial [Bitwarden](https://bitwarden.com/) compatible server)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:104
+msgid "These sibling playbooks co-exist nicely with one another due to using [Traefik](https://traefik.io/) for reverse-proxying, instead of trying to overtake the whole server by running their own [nginx](https://nginx.org/) reverse-proxy. Hopefully soon, the Matrix playbook will follow suit and be powered by Traefik by default."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:106
+msgid "Last, but not least, to optimize our [etke.cc managed Matrix hosting service](https://etke.cc/)'s performance (but also individual Ansible playbook runs for people self-hosting by themselves using the playbook), we've [improved playbook runtime 2-5x](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) by employing various Ansible tricks."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/README.po b/i18n/locales/bg/LC_MESSAGES/docs/README.po
new file mode 100644
index 000000000..57112b8f3
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/README.po
@@ -0,0 +1,174 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/README.md:1
+msgid "Table of Contents"
+msgstr ""
+
+#: ../../../docs/README.md:3
+msgid "⬇️ Installaton guides <!-- NOTE: the 🚀 emoji is used by \"Getting started\" on README.md -->"
+msgstr ""
+
+#: ../../../docs/README.md:5
+msgid "There are two installation guides available for beginners and advanced users."
+msgstr ""
+
+#: ../../../docs/README.md:7
+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/README.md:9
+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."
+msgstr ""
+
+#: ../../../docs/README.md:11
+msgid "[Prerequisites](prerequisites.md)"
+msgstr ""
+
+#: ../../../docs/README.md:13
+msgid "[Configuring your DNS settings](configuring-dns.md)"
+msgstr ""
+
+#: ../../../docs/README.md:15
+msgid "[Getting the playbook](getting-the-playbook.md)"
+msgstr ""
+
+#: ../../../docs/README.md:17
+msgid "[Configuring the playbook](configuring-playbook.md)"
+msgstr ""
+
+#: ../../../docs/README.md:19
+msgid "[Installing](installing.md)"
+msgstr ""
+
+#: ../../../docs/README.md:21
+msgid "🛠️ Configuration options"
+msgstr ""
+
+#: ../../../docs/README.md:28
+msgid "You can check useful documentation for configuring components here: [Configuring the playbook](configuring-playbook.md)"
+msgstr ""
+
+#: ../../../docs/README.md:30
+msgid "[Administration](configuring-playbook.md#administration) - services that help you in administrating and monitoring your Matrix installation"
+msgstr ""
+
+#: ../../../docs/README.md:32
+msgid "[Authentication and user-related](configuring-playbook.md#authentication-and-user-related) - extend and modify how users are authenticated on your homeserver"
+msgstr ""
+
+#: ../../../docs/README.md:34
+msgid "[Bots](configuring-playbook.md#bots) - bots provide various additional functionality to your installation"
+msgstr ""
+
+#: ../../../docs/README.md:36
+msgid "[Bridges](configuring-playbook.md#bridging-other-networks) - bridges can be used to connect your Matrix installation with third-party communication networks"
+msgstr ""
+
+#: ../../../docs/README.md:38
+msgid "[Clients](configuring-playbook.md#clients) - web clients for Matrix that you can host on your own domains"
+msgstr ""
+
+#: ../../../docs/README.md:40
+msgid "[Core service adjustments](configuring-playbook.md#core-service-adjustments) - backbone of your Matrix system"
+msgstr ""
+
+#: ../../../docs/README.md:42
+msgid "[File Storage](configuring-playbook.md#file-storage) - use alternative file storage to the default `media_store` folder"
+msgstr ""
+
+#: ../../../docs/README.md:46
+msgid "[Other specialized services](configuring-playbook.md#other-specialized-services) - various services that don't fit any other categories"
+msgstr ""
+
+#: ../../../docs/README.md:48
+msgid "👨‍🔧 Maintenance"
+msgstr ""
+
+#: ../../../docs/README.md:50
+msgid "If your server and services experience issues, feel free to come to [our support room](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) and ask for help."
+msgstr ""
+
+#: ../../../docs/README.md:54
+msgid "[Checking if services work](maintenance-checking-services.md)"
+msgstr ""
+
+#: ../../../docs/README.md:56
+msgid "[Maintenance and Troubleshooting](maintenance-and-troubleshooting.md)"
+msgstr ""
+
+#: ../../../docs/README.md:58
+msgid "[PostgreSQL maintenance](maintenance-postgres.md)"
+msgstr ""
+
+#: ../../../docs/README.md:60
+msgid "[Synapse maintenance](maintenance-synapse.md)"
+msgstr ""
+
+#: ../../../docs/README.md:62
+msgid "[Upgrading services](maintenance-upgrading-services.md)"
+msgstr ""
+
+#: ../../../docs/README.md:64
+msgid "Other documentation pages <!-- NOTE: this header's title and the section below need optimization -->"
+msgstr ""
+
+#: ../../../docs/README.md:66
+msgid "ℹ️ **[FAQ](faq.md)** - various Frequently Asked Questions about Matrix, with a focus on this Ansible playbook"
+msgstr ""
+
+#: ../../../docs/README.md:70
+msgid "[Alternative architectures](alternative-architectures.md)"
+msgstr ""
+
+#: ../../../docs/README.md:72
+msgid "[Container images used by the playbook](container-images.md)"
+msgstr ""
+
+#: ../../../docs/README.md:74
+msgid "[Obtaining an Access Token](obtaining-access-tokens.md)"
+msgstr ""
+
+#: ../../../docs/README.md:76
+msgid "[Playbook tags](playbook-tags.md)"
+msgstr ""
+
+#: ../../../docs/README.md:78
+msgid "[Registering users](registering-users.md)"
+msgstr ""
+
+#: ../../../docs/README.md:80
+msgid "[Running `just` commands](just.md)"
+msgstr ""
+
+#: ../../../docs/README.md:82
+msgid "[Self-building](self-building.md)"
+msgstr ""
+
+#: ../../../docs/README.md:84
+msgid "[Uninstalling](uninstalling.md)"
+msgstr ""
+
+#: ../../../docs/README.md:86
+msgid "[Updating users passwords](updating-users-passwords.md)"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/alternative-architectures.po b/i18n/locales/bg/LC_MESSAGES/docs/alternative-architectures.po
new file mode 100644
index 000000000..24b46ed48
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/alternative-architectures.po
@@ -0,0 +1,62 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/alternative-architectures.md:1
+msgid "Alternative architectures"
+msgstr "Алтернативни архитектури"
+
+#: ../../../docs/alternative-architectures.md:3
+msgid "As stated in the [Prerequisites](prerequisites.md), currently only `amd64` (`x86_64`) is fully supported."
+msgstr "Както е посочено в [Предусловия](prerequisites.md), в момента само `amd64` (`x86_64`) е напълно поддържана архитектура."
+
+#: ../../../docs/alternative-architectures.md:5
+msgid "The playbook automatically determines the target server's architecture (the `matrix_architecture` variable) to be one of the following:"
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:7
+msgid "`amd64` (`x86_64`)"
+msgstr "`amd64` (`x86_64`)"
+
+#: ../../../docs/alternative-architectures.md:8
+msgid "`arm32`"
+msgstr "`arm32`"
+
+#: ../../../docs/alternative-architectures.md:9
+msgid "`arm64`"
+msgstr "`arm64`"
+
+#: ../../../docs/alternative-architectures.md:11
+msgid "Some tools and container images can be built on the host or other measures can be used to install on that architecture."
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:13
+msgid "Implementation details"
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:15
+msgid "For `amd64`, prebuilt container images (see the [container images we use](container-images.md)) are used for all components (except [Hydrogen](configuring-playbook-client-hydrogen.md), which goes through self-building)."
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:17
+msgid "For other architecture (`arm64`, `arm32`), components which have a prebuilt image make use of it. If the component is not available for the specific architecture, [self-building](self-building.md) will be used. Not all components support self-building though, so your mileage may vary."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/ansible.po b/i18n/locales/bg/LC_MESSAGES/docs/ansible.po
new file mode 100644
index 000000000..3b6998f22
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/ansible.po
@@ -0,0 +1,182 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/ansible.md:2
+msgid "Running this playbook"
+msgstr ""
+
+#: ../../../docs/ansible.md:4
+msgid "This playbook is meant to be run using [Ansible](https://www.ansible.com/)."
+msgstr ""
+
+#: ../../../docs/ansible.md:6
+msgid "Ansible typically runs on your local computer and carries out tasks on a remote server. If your local computer cannot run Ansible, you can also run Ansible on some server somewhere (including the server you wish to install to)."
+msgstr ""
+
+#: ../../../docs/ansible.md:8
+msgid "Supported Ansible versions"
+msgstr ""
+
+#: ../../../docs/ansible.md:10
+msgid "To manually check which version of Ansible you're on, run: `ansible --version`."
+msgstr ""
+
+#: ../../../docs/ansible.md:12
+msgid "For the **best experience**, we recommend getting the **latest version of Ansible available**."
+msgstr ""
+
+#: ../../../docs/ansible.md:14
+msgid "We're not sure what's the minimum version of Ansible that can run this playbook successfully. The lowest version that we've confirmed (on 2022-11-26) to be working fine is: `ansible-core` (`2.11.7`) combined with `ansible` (`4.10.0`)."
+msgstr ""
+
+#: ../../../docs/ansible.md:16
+msgid "If your distro ships with an Ansible version older than this, you may run into issues. Consider [Upgrading Ansible](#upgrading-ansible) or [using Ansible via Docker](#using-ansible-via-docker)."
+msgstr ""
+
+#: ../../../docs/ansible.md:18
+msgid "Upgrading Ansible"
+msgstr ""
+
+#: ../../../docs/ansible.md:20
+msgid "Depending on your distribution, you may be able to upgrade Ansible in a few different ways:"
+msgstr ""
+
+#: ../../../docs/ansible.md:22
+msgid "by using an additional repository (PPA, etc.), which provides newer Ansible versions. See instructions for [CentOS](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-rhel-centos-or-fedora), [Debian](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-debian), or [Ubuntu](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-ubuntu) on the Ansible website."
+msgstr ""
+
+#: ../../../docs/ansible.md:24
+msgid "by removing the Ansible package (`yum remove ansible` or `apt-get remove ansible`) and installing via [pip](https://pip.pypa.io/en/stable/installation/) (`pip install ansible`)."
+msgstr ""
+
+#: ../../../docs/ansible.md:26
+msgid "If using the `pip` method, do note that the `ansible-playbook` binary may not be on the `$PATH` (https://linuxconfig.org/linux-path-environment-variable), but in some more special location like `/usr/local/bin/ansible-playbook`. You may need to invoke it using the full path."
+msgstr ""
+
+#: ../../../docs/ansible.md:28
+msgid "**Note**: Both of the above methods are a bad way to run system software such as Ansible. If you find yourself needing to resort to such hacks, please consider reporting a bug to your distribution and/or switching to a sane distribution, which provides up-to-date software."
+msgstr ""
+
+#: ../../../docs/ansible.md:30
+msgid "Using Ansible via Docker"
+msgstr ""
+
+#: ../../../docs/ansible.md:32
+msgid "Alternatively, you can run Ansible inside a Docker container (powered by the [devture/ansible](https://hub.docker.com/r/devture/ansible/) Docker image)."
+msgstr ""
+
+#: ../../../docs/ansible.md:34
+msgid "This ensures that you're using a very recent Ansible version, which is less likely to be incompatible with the playbook."
+msgstr ""
+
+#: ../../../docs/ansible.md:36
+msgid "You can either [run Ansible in a container on the Matrix server itself](#running-ansible-in-a-container-on-the-matrix-server-itself) or [run Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)."
+msgstr ""
+
+#: ../../../docs/ansible.md:38
+msgid "Running Ansible in a container on the Matrix server itself"
+msgstr ""
+
+#: ../../../docs/ansible.md:40
+msgid "To run Ansible in a (Docker) container on the Matrix server itself, you need to have a working Docker installation. Docker is normally installed by the playbook, so this may be a bit of a chicken and egg problem. To solve it:"
+msgstr ""
+
+#: ../../../docs/ansible.md:42
+msgid "you **either** need to install Docker manually first. Follow [the upstream instructions](https://docs.docker.com/engine/install/) for your distribution and consider setting `matrix_playbook_docker_installation_enabled: false` in your `vars.yml` file, to prevent the playbook from installing Docker"
+msgstr ""
+
+#: ../../../docs/ansible.md:43
+msgid "**or** you need to run the playbook in another way (e.g. [Running Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)) at least the first time around"
+msgstr ""
+
+#: ../../../docs/ansible.md:45
+msgid "Once you have a working Docker installation on the server, **clone the playbook** somewhere on the server and configure it as per usual (`inventory/hosts`, `inventory/host_vars/..`, etc.), as described in [configuring the playbook](configuring-playbook.md)."
+msgstr ""
+
+#: ../../../docs/ansible.md:47
+msgid "You would then need to add `ansible_connection=community.docker.nsenter` to the host line in `inventory/hosts`. This tells Ansible to connect to the \"remote\" machine by switching Linux namespaces with [nsenter](https://man7.org/linux/man-pages/man1/nsenter.1.html), instead of using SSH."
+msgstr ""
+
+#: ../../../docs/ansible.md:49
+msgid "Alternatively, you can leave your `inventory/hosts` as is and specify the connection type in **each** `ansible-playbook` call you do later, like this: `ansible-playbook --connection=community.docker.nsenter …`"
+msgstr ""
+
+#: ../../../docs/ansible.md:51 ../../../docs/ansible.md:71
+msgid "Run this from the playbook's directory:"
+msgstr ""
+
+#: ../../../docs/ansible.md:63 ../../../docs/ansible.md:84
+msgid "Once you execute the above command, you'll be dropped into a `/work` directory inside a Docker container. The `/work` directory contains the playbook's code."
+msgstr ""
+
+#: ../../../docs/ansible.md:65 ../../../docs/ansible.md:86
+msgid "First, consider running `git config --global --add safe.directory /work` to [resolve directory ownership issues](#resolve-directory-ownership-issues)."
+msgstr ""
+
+#: ../../../docs/ansible.md:67
+msgid "Finally, you can execute `ansible-playbook …` (or `ansible-playbook --connection=community.docker.nsenter …`) commands as per normal now."
+msgstr ""
+
+#: ../../../docs/ansible.md:69
+msgid "Running Ansible in a container on another computer (not the Matrix server)"
+msgstr ""
+
+#: ../../../docs/ansible.md:82
+msgid "The above command tries to mount an SSH key (`$HOME/.ssh/id_rsa`) into the container (at `/root/.ssh/id_rsa`). If your SSH key is at a different path (not in `$HOME/.ssh/id_rsa`), adjust that part."
+msgstr ""
+
+#: ../../../docs/ansible.md:88
+msgid "Finally, you execute `ansible-playbook …` commands as per normal now."
+msgstr ""
+
+#: ../../../docs/ansible.md:90
+msgid "If you don't use SSH keys for authentication"
+msgstr ""
+
+#: ../../../docs/ansible.md:92
+msgid "If you don't use SSH keys for authentication, simply remove that whole line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`)."
+msgstr ""
+
+#: ../../../docs/ansible.md:94
+msgid "To authenticate at your server using a password, you need to add a package. So, when you are in the shell of the ansible docker container (the previously used `docker run -it …` command), run:"
+msgstr ""
+
+#: ../../../docs/ansible.md:100
+msgid "Then, to be asked for the password whenever running an  `ansible-playbook` command add `--ask-pass` to the arguments of the command."
+msgstr ""
+
+#: ../../../docs/ansible.md:102
+msgid "Resolve directory ownership issues"
+msgstr ""
+
+#: ../../../docs/ansible.md:104
+msgid "Because you're `root` in the container running Ansible and this likely differs fom the owner (your regular user account) of the playbook directory outside of the container, certain playbook features which use `git` locally may report warnings such as:"
+msgstr ""
+
+#: ../../../docs/ansible.md:106
+msgid "fatal: unsafe repository ('/work' is owned by someone else) To add an exception for this directory, call:  git config --global --add safe.directory /work"
+msgstr ""
+
+#: ../../../docs/ansible.md:110
+msgid "These errors can be resolved by making `git` trust the playbook directory by running `git config --global --add safe.directory /work`"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-captcha.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-captcha.po
new file mode 100644
index 000000000..ebdb77ac7
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-captcha.po
@@ -0,0 +1,80 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-captcha.md:1
+msgid "(Adapted from the [upstream project](https://github.com/element-hq/synapse/blob/develop/docs/CAPTCHA_SETUP.md))"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:3
+msgid "Overview"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:5
+msgid "Captcha can be enabled for this home server. This file explains how to do that."
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:7
+msgid "The captcha mechanism used is Google's [ReCaptcha](https://www.google.com/recaptcha/). This requires API keys from Google. If your homeserver is Dendrite then [hCapcha](https://www.hcaptcha.com) can be used instead."
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:9
+msgid "ReCaptcha"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:11
+#: ../../../docs/configuring-captcha.md:37
+msgid "Getting keys"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:13
+#: ../../../docs/configuring-captcha.md:39
+msgid "Requires a site/secret key pair from:"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:15
+msgid "<http://www.google.com/recaptcha/admin>"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:17
+msgid "Must be a reCAPTCHA **v2** key using the \"I'm not a robot\" Checkbox option"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:19
+msgid "Setting ReCaptcha keys"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:21
+msgid "Once registered as above, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:35
+msgid "hCaptcha"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:41
+msgid "<https://dashboard.hcaptcha.com/sites/new>"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:43
+msgid "Setting hCaptcha keys"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-dns.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-dns.po
new file mode 100644
index 000000000..c74078901
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-dns.po
@@ -0,0 +1,346 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-dns.md:1
+msgid "Configuring your DNS settings"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:3
+msgid "<sup>[Prerequisites](prerequisites.md) > Configuring your DNS settings > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)</sup>"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:5
+msgid "To set up Matrix on your domain, you'd need to do some DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:7
+msgid "DNS setting for server delegation (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:9
+msgid "In the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:11
+msgid "To use such an ID, you don't need to install anything on the actual `example.com` server. Instead, you need to instruct the Matrix network that Matrix services for `example.com` are redirected over to `matrix.example.com`. This redirection is also known as \"delegation\"."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:13
+msgid "As we discuss in [Server Delegation](howto-server-delegation.md), server delegation can be configured in either of these ways:"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:15
+msgid "Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:16
+msgid "Setting up a `_matrix._tcp` DNS SRV record"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:18
+msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file, instead of using a DNS SRV record."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:20
+msgid "If you choose the recommended method (file-based delegation), you do not need to configure the DNS record to enable server delegation. You will need to add a necessary configuration later, when you [finalize the installation](installing.md#finalize-the-installation) after installing and starting Matrix services."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:22
+msgid "On the other hand, if you choose this method (setting up a DNS SRV record), you need to configure the additional DNS record as well as adjust SSL certificate handling. Take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:24
+msgid "DNS settings for services enabled by default"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:26
+msgid "To serve the base domain (`example.com`) and [Element Web](configuring-playbook-client-element-web.md) with the default subdomain, adjust DNS records as below."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "Type"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "Host"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "Priority"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "Weight"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "Port"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "Target"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "A"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`matrix`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "-"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`matrix-server-IP`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "CNAME"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`element`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`matrix.example.com`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:33
+msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:35
+msgid "The `element.example.com` subdomain is necessary, because this playbook installs the [Element Web](https://github.com/element-hq/element-web) client for you by default. If you'd rather instruct the playbook not to install Element Web (`matrix_client_element_enabled: false` when [Configuring the playbook](configuring-playbook.md) later), feel free to skip the `element.example.com` DNS record."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:37
+msgid "Be mindful as to how long it will take for the DNS records to propagate."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:39
+msgid "If you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\". Otherwise, fetching certificates will fail."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:41
+msgid "DNS settings for optional services/features"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:43
+msgid "For other services which may need subdomain settings, see the table below and configure the DNS (`CNAME`) records accordingly."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "Used by component"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Dimension](configuring-playbook-dimension.md) integration server"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`dimension`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Jitsi](configuring-playbook-jitsi.md) video-conferencing platform"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`jitsi`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) monitoring system"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`stats`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Go-NEB](configuring-playbook-bot-go-neb.md) bot"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`goneb`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Sygnal](configuring-playbook-sygnal.md) push notification gateway"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`sygnal`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[ntfy](configuring-playbook-ntfy.md) push notifications server"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`ntfy`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Etherpad](configuring-playbook-etherpad.md) collaborative text editor"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`etherpad`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Hydrogen](configuring-playbook-client-hydrogen.md) web client"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`hydrogen`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Cinny](configuring-playbook-client-cinny.md) web client"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`cinny`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md) client"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`schildichat`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[wsproxy](configuring-playbook-bridge-mautrix-wsproxy.md) sms bridge"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`wsproxy`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Buscarron](configuring-playbook-bot-buscarron.md) helpdesk bot"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`buscarron`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[rageshake](configuring-playbook-rageshake.md) bug report server"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`rageshake`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[ma1sd](configuring-playbook-ma1sd.md) identity server"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "SRV"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`_matrix-identity._tcp`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "10"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "0"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "443"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md)/[Email2Matrix](configuring-playbook-email2matrix.md) email bridges"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "MX"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md) email bridge"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "TXT"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`v=spf1 ip4:matrix-server-IP -all`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`_dmarc.matrix`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`v=DMARC1; p=quarantine;`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`postmoogle._domainkey.matrix`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "get it from `!pm dkim`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:66
+msgid "SRV record for ma1sd"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:68
+msgid "To make ma1sd enable its federation features, you need to set up a `_matrix-identity._tcp` SRV record. Don't confuse this with the `_matrix._tcp` SRV record for server delegation. See the table above and [this section](configuring-playbook-ma1sd.md#adjusting-dns-records) for values which need to be specified."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:70
+msgid "When setting up a SRV record, if you are asked for a service and protocol instead of a hostname split the host value from the table where the period is. For example use service as `_matrix-identity` and protocol as `_tcp`."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:72
+msgid "MX and TXT records for Postmoogle"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:74
+msgid "To make Postmoogle enable its email sending features, you need to configure MX and TXT (SPF, DMARC, and DKIM) records. See the table above for values which need to be specified."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:78
+msgid "[▶️](getting-the-playbook.md) When you're done with the DNS configuration and ready to proceed, continue with [Getting the playbook](getting-the-playbook.md)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po
new file mode 100644
index 000000000..2c03e93ea
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po
@@ -0,0 +1,170 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:1
+msgid "Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:3
+msgid "The playbook can install and configure the [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver) service for you. It's a [client](https://prometheus.io/docs/alerting/latest/clients/) for Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/), allowing you to deliver alerts to Matrix rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:5
+msgid "See the project's [documentation](https://github.com/metio/matrix-alertmanager-receiver/blob/main/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:7
+msgid "This service is meant to be used with an external [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) instance. It's **not** meant to be integrated with the [Prometheus & Grafana stack](./configuring-playbook-prometheus-grafana.md) installed by this playbook, because the Alertmanager component is not installed by it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:11
+msgid "Register the bot account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:13
+msgid "This service uses a bot (with a username specified in `matrix_alertmanager_receiver_config_matrix_user_id_localpart`) for delivering messages."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:15
+msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:17
+msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:19
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:25
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:27
+msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:29
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:31
+msgid "Join to rooms as the bot manually"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:33
+msgid "ℹ️ **This bot does not accept room invitations automatically**. To deliver messages to rooms, the bot must be joined to all rooms manually."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:35
+msgid "For each new room you would like the bot to deliver alerts to, invite the bot to the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:37
+msgid "Then, log in as the bot using any Matrix client of your choosing, accept the room invitation from the bot's account, and log out."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:39
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:41
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:62
+msgid "See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for additional configuration variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:64
+msgid "Adjusting the matrix-alertmanager-receiver URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:66
+msgid "By default, this playbook installs matrix-alertmanager-receiver on the `matrix.` subdomain, at the `/matrix-alertmanager-receiver` path (https://matrix.example.com/matrix-alertmanager-receiver). 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-alertmanager-receiver.md:68
+msgid "By tweaking the `matrix_alertmanager_receiver_hostname` and `matrix_alertmanager_receiver_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-alertmanager-receiver.md:70
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:78
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:80
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-alertmanager-receiver domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:82
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:84
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:86
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:88
+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-alertmanager-receiver.md:95
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:97
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:99
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:101
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:103
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:105
+msgid "Configure your Prometheus Alertmanager with configuration like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:124
+msgid "where `URL_HERE` looks like `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/some-room-name` or `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/!qporfwt:example.com`."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po
new file mode 100644
index 000000000..1fc381a95
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po
@@ -0,0 +1,78 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:1
+msgid "Setting up Appservice Double Puppet (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:3
+msgid "Appservice Double Puppet is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:5
+msgid "This is useful for performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via the [appservice method](https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new). The Appservice Double Puppet service is an implementation of this approach."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:7
+msgid "Previously, bridges supported performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but this old and hacky solution has been superseded by this Appservice Double Puppet method."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:11
+msgid "To enable the Appservice Double Puppet service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:17
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:19
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:26
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:28
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:30
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:32
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:34
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:36
+msgid "When enabled, double puppeting will automatically be enabled for all bridges that support double puppeting via the appservice method."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po
new file mode 100644
index 000000000..e4c00fb90
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po
@@ -0,0 +1,195 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:1
+msgid "Setting up Draupnir for All/D4A (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:3
+msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool for you in appservice mode."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:5
+msgid "Appservice mode can be used together with the regular [Draupnir bot](configuring-playbook-bot-draupnir.md) or independently. Details about the differences between the 2 modes are described below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:7
+msgid "Draupnir Appservice mode compared to Draupnir bot mode"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:9
+msgid "The administrative functions for managing the appservice are alpha quality and very limited. However, the experience of using an appservice-provisioned Draupnir is on par with the experience of using Draupnir from bot mode except in the case of avatar customisation as described later on in this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:11
+msgid "Draupnir for all is the way to go if you need more than 1 Draupnir instance, but you don't need access to Synapse Admin features as they are not accessible through Draupnir for All (Even though the commands do show up in help)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:13
+msgid "Draupnir for all in the playbook is rate-limit-exempt automatically as its appservice configuration file does not specify any rate limits."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:15
+msgid "Normal Draupnir does come with the benefit of access to Synapse Admin features. You are also able to more easily customise your normal Draupnir than D4A as D4A even on the branch with the Avatar command (To be Upstreamed to Mainline Draupnir) that command is clunky as it requires the use of things like Element Web devtools. In normal Draupnir this is a quick operation where you login to Draupnir with a normal client and set Avatar and Display name normally."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:17
+msgid "Draupnir for all does not support external tooling like [MRU](https://mru.rory.gay) as it can't access Draupnir's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:19
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:21
+msgid "Create a main management room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:23
+msgid "The playbook does not create a management room for your Main Draupnir. You **need to create the room manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:25
+msgid "Note that the room must be unencrypted."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:29
+msgid "The management room has to be given an alias and be public when you are setting up the bot for the first time as the bot does not differentiate between invites and invites to the management room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:31
+msgid "This management room is used to control who has access to your D4A deployment. The room stores this data inside of the control room state so your bot must have sufficient powerlevel to send custom state events. This is default 50 or moderator as Element clients call this powerlevel."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:33
+msgid "As noted in the Draupnir install instructions the control room is sensitive. **Anyone in this room can control the bot so it is important that you only invite trusted users to this room.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:35
+msgid "Set an alias to the management room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:37
+msgid "Next, set an alias to the management room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:39
+msgid "This alias can be anything you want. However, for increased security during the setup phase, it is recommended to make this alias be a random string. When it has been locked down after setup phase, you can give your room a secondary human readable alias."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:41
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:43
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ALIAS_HERE`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:51
+msgid "Extending the configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:53
+msgid "You can configure additional options by adding the `matrix_appservice_draupnir_for_all_extension_yaml` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:55
+msgid "For example, to change Draupnir's `protectAllJoinedRooms` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:69
+msgid "You can refer to the upstream [documentation](https://github.com/the-draupnir-project/Draupnir) for more configuration documentation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:71
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:86
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:73
+msgid "The playbook ships a full copy of the example config that does transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in the template directory of the role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:75
+msgid "Config extension does not affect the appservices config as this config is not extensible in current Draupnir anyway. It instead touches the config passed to the Draupnirs that your Appservice creates. So the example above (`protectAllJoinedRooms: true`) makes all provisioned Draupnirs protect all joined rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:77
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:79
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:88
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:90
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:92
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:94
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:96
+msgid "If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com` you have succesfully installed Draupnir for All and can now start using it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:98
+msgid "The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot mode."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:100
+msgid "Granting Users the ability to use D4A"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:102
+msgid "Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recomendation. Using the chat is recomended."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:104
+msgid "The bot requires a powerlevel of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:106
+msgid "To allow users or whole homeservers you type /plain @draupnir-main:example.com allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:108
+msgid "How to provision a D4A once you are allowed to"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:110
+msgid "To provision a D4A, you need to start a chat with `@draupnir-main:example.com`. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:112
+msgid "Congratulations if you made it all the way here because you now have a fully working Draupnir for all deployment."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-backup-borg.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-backup-borg.po
new file mode 100644
index 000000000..9940bcadd
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-backup-borg.po
@@ -0,0 +1,142 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-22 17:53+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-backup-borg.md:1
+msgid "Setting up BorgBackup (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:3
+msgid "The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) (short: Borg) with [borgmatic](https://torsion.org/borgmatic/) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:5
+msgid "BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:7
+msgid "You will need a remote server where BorgBackup will store the backups. There are hosted, BorgBackup compatible solutions available, such as [BorgBase](https://www.borgbase.com)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:9
+msgid "The backup will run based on `backup_borg_schedule` var (systemd timer calendar), default: 4am every day."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:11
+msgid "By default, if you're using the integrated Postgres database server (as opposed to [an external Postgres server](configuring-playbook-external-postgres.md)), backups with BorgBackup will also include dumps of your Postgres database. An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md). If you decide to go with another solution, you can disable Postgres-backup support for BorgBackup using the `backup_borg_postgresql_enabled` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:13
+msgid "**Note**: the component is not managed by this repository but its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:15
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:17
+msgid "If you do not disable Postgres-backup support, make sure that the Postgres version of your homeserver's database is compatible with borgmatic."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:19
+msgid "Create a new SSH key:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:25
+msgid "This can be done on any machine and you don't need to place the key in the `.ssh` folder. It will be added to the Ansible config later."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:27
+msgid "Add the **public** part of this SSH key (the `matrix-borg-backup.pub` file) to your BorgBackup provider/server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:29
+msgid "If you plan to use a hosted solution, follow their instructions. If you have your own server, copy the key over:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:39
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:41
+msgid "Minimal working configuration (`inventory/host_vars/matrix.example.com/vars.yml`) to enable BorgBackup:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:58
+msgid "where:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:60
+msgid "USER - SSH user of a provider/server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:61
+msgid "HOST - SSH host of a provider/server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:62
+msgid "REPO - BorgBackup repository name, it will be initialized on backup start, eg: `matrix`, regarding Syntax see [Remote repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html#repository-urls)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:63
+msgid "PASSPHRASE - passphrase used for encrypting backups. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:64
+msgid "PRIVATE KEY - the content of the **private** part of the SSH key you created before. The whole key (all of its belonging lines) under `backup_borg_ssh_key_private` needs to be indented with 2 spaces"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:66
+msgid "To backup without encryption, add `backup_borg_encryption: 'none'` to your vars. This will also enable the `backup_borg_unknown_unencrypted_repo_access_is_ok` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:68
+msgid "`backup_borg_location_source_directories` defines the list of directories to back up: it's set to `{{ matrix_base_data_path }}` by default, which is the base directory for every service's data, such as Synapse, Postgres and the bridges. You might want to exclude certain directories or file patterns from the backup using the `backup_borg_location_exclude_patterns` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:70
+msgid "Check the [backup_borg role](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)'s [defaults/main.yml](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml) file for the full list of available options."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:72
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:74
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:81
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:83
+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-backup-borg.md:85
+msgid "Manually start a backup"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:87
+msgid "For testing your setup it can be helpful to not wait until 4am. If you want to run the backup immediately, log onto the server and run `systemctl start matrix-backup-borg`. This will not return until the backup is done, so possibly a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po
new file mode 100644
index 000000000..df0ffc237
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po
@@ -0,0 +1,162 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:1
+msgid "Serving the base domain (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:3
+msgid "By default, this playbook sets up services on your Matrix server (`matrix.example.com`), but has it configured so that it presents itself as the base domain (`example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:5
+msgid "As we discuss in [Server Delegation](howto-server-delegation.md), server delegation / redirection can be configured in either of these ways:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:7
+msgid "Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:8
+msgid "Setting up a `_matrix._tcp` DNS SRV record"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:10
+msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:12
+msgid "However, those who don't have a separate server to dedicate to the base domain have trouble arranging this."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:14
+msgid "Usually, there are 2 options:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:16
+msgid "either get a separate server for the base domain, just for serving the files necessary for [Server Delegation via a well-known file](howto-server-delegation.md#server-delegation-via-a-well-known-file)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:18
+msgid "or, arrange for the Matrix server to serve the base domain. This either involves you [using your own webserver](configuring-playbook-own-webserver.md) or making the integrated webserver serve the base domain for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:20
+msgid "This documentation page tells you how to do the latter. With some easy changes, we make it possible to serve the base domain from the Matrix server via the integrated webserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:22
+msgid "Just [**adjust your DNS records**](configuring-dns.md), so that your base domain is pointed to the Matrix server's IP address (using a DNS `A` record) **and then add the following configuration** to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:28
+msgid "Doing this, the playbook will:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:30
+msgid "obtain an SSL certificate for the base domain, just like it does for all other domains (see [how we handle SSL certificates](configuring-playbook-ssl-certificates.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:32
+msgid "serve the `/.well-known/matrix/*` files which are necessary for [Federation Server Discovery](configuring-well-known.md#federation-server-discovery) (also see [Server Delegation](howto-server-delegation.md)) and [Client-Server discovery](configuring-well-known.md#client-server-discovery)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:34
+msgid "serve a simple homepage at `https://example.com` with content `Hello from example.com` (configurable via the `matrix_static_files_file_index_html_template` variable). You can also [serve a more complicated static website](#serving-a-static-website-at-the-base-domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:36
+msgid "Serving a static website at the base domain"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:38
+msgid "By default, when \"serving the base domain\" is enabled, the playbook hosts a simple `index.html` webpage at `/matrix/static-files/public/index.html`. The content of this page is taken from the `matrix_static_files_file_index_html_template` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:40
+msgid "If you'd like to host your own static website (more than a single `index.html` page) at the base domain, you can disable the creation of this default `index.html` page like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:54
+msgid "With this configuration, Ansible will no longer mess around with the `/matrix/static-files/public/index.html` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:56
+msgid "You are then free to upload any static website files to `/matrix/static-files/public` and they will get served at the base domain. You can do so manually or by using the [ansible-role-aux](https://github.com/mother-of-all-self-hosting/ansible-role-aux) Ansible role, which is part of this playbook already."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:58
+msgid "Serving a more complicated website at the base domain"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:60
+msgid "If you'd like to serve an even more complicated (dynamic) website from the Matrix server, relying on the playbook to serve the base domain is not the best choice."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:62
+msgid "You have 2 options."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:64
+msgid "**One way is to host your base domain elsewhere**. This involves:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:65
+msgid "you stopping to serve it from the Matrix server: remove `matrix_static_files_container_labels_base_domain_enabled` from your configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:66
+msgid "[configuring Matrix Delegation via well-known](./configuring-well-known.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:68
+msgid "**Another way is to serve the base domain from another (your own) container on the Matrix server**. This involves:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:69
+msgid "telling the playbook to only serve `example.com/.well-known/matrix` files by adjusting your `vars.yml` configuration like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:70
+msgid "keep `matrix_static_files_container_labels_base_domain_enabled: true`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:71
+msgid "add an extra: `matrix_static_files_container_labels_base_domain_traefik_path_prefix: /.well-known/matrix`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:72
+msgid "building and running a new container on the Matrix server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:73
+msgid "it should be connected to the `traefik` network, so that Traefik can reverse-proxy to it"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:74
+msgid "it should have appropriate [container labels](https://docs.docker.com/config/labels-custom-metadata/), which instruct Traefik to reverse-proxy to it"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:76
+msgid "How you'll be managing building and running this container is up-to-you. You may use of the primitives from [ansible-role-aux](https://github.com/mother-of-all-self-hosting/ansible-role-aux) Ansible role to organize it yourself, or you can set it up in another way."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po
new file mode 100644
index 000000000..4c6509717
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po
@@ -0,0 +1,429 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-23 13:09+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:1
+msgid "Setting up baibot (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:8
+msgid "🤖 [baibot](https://github.com/etkecc/baibot) (pronounced bye-bot) is a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:10
+msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as many well as other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:12
+msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to [matrix-chatgpt-bot](./configuring-playbook-bot-chatgpt.md). See the [baibot](https://github.com/etkecc/baibot) project and its documentation for more information."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:14
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:16
+msgid "API access to one or more LLM [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:18
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:20
+msgid "There are **a lot of configuration options** (some required, some possibly required, some optional), so they're **split into multiple sections below**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:23
+msgid "[Base configuration](#base-configuration)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:24
+msgid "[👮‍♂️ Administrator configuration](#️-administrator-configuration)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:25
+msgid "[👥 Initial users configuration](#-initial-users-configuration)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:26
+msgid "[🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:27
+msgid "[🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:29
+msgid "Depending on your current `vars.yml` file and desired configuration, **you may require more than just the [base configuration](#base-configuration)**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:31
+msgid "Base configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:33
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:71
+msgid "As mentioned above, **this may not be enough**. Continue with the configuration sections below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:73
+msgid "👮‍♂️ Administrator configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:75
+#: ../../../docs/configuring-playbook-bot-baibot.md:99
+msgid "This is an addition to the [base configuration](#base-configuration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:77
+msgid "To specify who is considered a bot [👮‍♂️ Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators), you either need to specify `matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The latter is a single variable which affects all bridges and bots."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:79
+msgid "If `matrix_admin` is already configured in your `vars.yml` configuration, you can skip this section."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:81
+#: ../../../docs/configuring-playbook-bot-baibot.md:110
+msgid "**If necessary**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:95
+msgid "👥 Initial users configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:97
+msgid "By default, **all users on your homeserver are considered allowed users**. If that's OK, you can skip this section."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:101
+msgid "To specify who is considered a bot [👥 User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), you may:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:103
+msgid "define an **initial** value for `matrix_bot_baibot_config_initial_global_config_user_patterns` Ansible variable, as shown below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:104
+msgid "configure the list at runtime via the bot's `!bai access set-users SPACE_SEPARATED_PATTERNS` command"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:106
+msgid "Configuring `matrix_bot_baibot_config_initial_global_config_user_patterns` is optional, but it can be useful to pre-configure the bot with a list of users who should have access to the bot's features."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:108
+msgid "**Note**: Once initially configured, the allowed users list **cannot be managed via Ansible anymore**. It can only be managed subsequently via bot commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:122
+msgid "🤖 Configuring agents via Ansible"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:124
+msgid "You are **not required** to define agents [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration) via Ansible. **To get started quickly**, you can **skip this section and define agents at runtime via chat commands** (following the bot's guidance)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:126
+msgid "Privileged users (like the [👮‍♂️ Administrator](#️-administrator-configuration), but potentially others too - see the upstream [🔒 access](https://github.com/etkecc/baibot/blob/main/docs/access.md) documentation) can **define agents dynamically at any time** via chat commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:128
+msgid "The Ansible role includes preset variables for easily enabling some [🤖 agents](https://github.com/etkecc/baibot/blob/main/docs/agents.md) on various [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md) (e.g. OpenAI, etc)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:130
+msgid "Besides the presets, the Ansible role also includes support for configuring additional statically-defined agents via the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:132
+msgid "Agents defined statically and those created dynamically (via chat) are named differently, so **conflict cannot arise**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:134
+msgid "Depending on your propensity for [GitOps](https://en.wikipedia.org/wiki/DevOps#GitOps), you may prefer to define agents statically via Ansible, or you may wish to do it dynamically via chat."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:136
+msgid "Before proceeding, we recommend reading the upstream documentation on [How to choose a provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#how-to-choose-a-provider). In short, it's probably best to go with [OpenAI](#openai)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:138
+msgid "Anthropic"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:140
+msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Anthropic provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic) with the help of the playbook's preset variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:142
+#: ../../../docs/configuring-playbook-bot-baibot.md:168
+#: ../../../docs/configuring-playbook-bot-baibot.md:201
+#: ../../../docs/configuring-playbook-bot-baibot.md:231
+msgid "Here's an example **addition** to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:160
+#: ../../../docs/configuring-playbook-bot-baibot.md:193
+#: ../../../docs/configuring-playbook-bot-baibot.md:221
+#: ../../../docs/configuring-playbook-bot-baibot.md:251
+msgid "If you'd like to use more than one model, take a look at the [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:162
+#: ../../../docs/configuring-playbook-bot-baibot.md:195
+#: ../../../docs/configuring-playbook-bot-baibot.md:223
+#: ../../../docs/configuring-playbook-bot-baibot.md:253
+msgid "💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:164
+msgid "Groq"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:166
+msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Groq provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq) with the help of the playbook's preset variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:191
+msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/groq`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:197
+msgid "Mistral"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:199
+msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [🇫🇷 Mistral provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral) with the help of the playbook's preset variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:219
+msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/mistral`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:225
+msgid "OpenAI"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:227
+msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai) with the help of the playbook's preset variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:229
+msgid "The OpenAI provider is **only meant to be used with OpenAI's official API** and compatibility with other services (which do not fully adhere to the OpenAI API spec completely) is limited. **If you're targeting an OpenAI-compatible service**, use the [OpenAI Compatible](#openai-compatible) provider instead."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:249
+msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/openai`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:255
+msgid "OpenAI Compatible"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:257
+msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI Compatible provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai-compatible) with the help of the playbook's preset variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:259
+msgid "This provider allows you to use OpenAI-compatible API services like [OpenRouter](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openrouter), [Together AI](https://github.com/etkecc/baibot/blob/main/docs/providers.md#together-ai), etc."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:261
+msgid "Some of these popular services already have **shortcut** providers (see [supported providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md#supported-providers) leading to this one behind the scenes - this make it easier to get started."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:263
+msgid "As of this moment, the playbook does not include presets for any of these services, so you'll need to [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:265
+msgid "Configuring additional agents (without a preset)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:267
+msgid "The Ansible role may be lacking preset variables for some [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), or you may wish to statically-define an agent on the same provider twice (or more) with different configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:269
+msgid "It's possible to inject your own agent configuration using the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:271
+msgid "You can also define providers at runtime, by chatting with the bot, so using Ansible is not a requirement."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:273
+msgid "Below is an an **example** demonstrating **statically-defining agents via Ansible without using presets**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:312
+msgid "Because these are [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agents, they will be given a `static/` ID prefix and will be named `static/my-openai-gpt-3.5-turbo-agent` and `static/my-ollama-agent`, respectively."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:314
+msgid "💡 To figure out what to put in the `config` section, refer to the [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md) page, which contains **sample configuration YAML for each provider**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:316
+msgid "As with any [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), defining them means they exist. To actually make use of them, they need to be configured as handlers globally or in a specific room - see [Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:318
+msgid "💡 You may also wish to use these new agents for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:320
+msgid "🤝 Configuring initial default handlers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:322
+msgid "This section is only useful if you're [🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible), as it lets you put these agents to use as soon as the bot starts (by adjusting the bot's **initial global configuration**)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:324
+msgid "If you're not configuring agents via Ansible, you can skip this section."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:326
+msgid "This section is only useful the first time around. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:328
+msgid "baibot supports [various purposes](https://github.com/etkecc/baibot/blob/main/docs/features.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:330
+msgid "[💬 text-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-generation): communicating with you via text"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:332
+msgid "[🦻 speech-to-text](https://github.com/etkecc/baibot/blob/main/docs/features.md#-speech-to-text): turning your voice messages into text"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:334
+msgid "[🗣️ text-to-speech](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-to-speech): turning bot or users text messages into voice messages"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:336
+msgid "[🖌️ image-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-image-generation): generating images based on instructions"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:338
+msgid "❓ catch-all: special purposes, indicating use as a fallback (when no specific handler is configured)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:340
+msgid "[Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models) is made possible by the bot's ability to have different [🤝 handlers](https://github.com/etkecc/baibot/blob/main/docs/configuration/handlers.md) configured for different purposes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:342
+msgid "This configuration can be done as a global fallback, or per-room. Both of these [🛠️ configurations](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md) are managed at runtime (viat chat), but **the global configuration can have some initial defaults configured via Ansible**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:344
+msgid "You can configure the **initial values** for these via Ansible, via the `matrix_bot_baibot_config_initial_global_config_handler_*` variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:346
+msgid "Example **additional** `vars.yml` configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:363
+msgid "**Note**: these are initial defaults for the bot's global configuration. As such, changing any of these values subsequently has no effect on the bot's behavior. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:365
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:367
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:374
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:376
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:378
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:380
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:382
+msgid "If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:384
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:386
+msgid "To use the bot, invite it to any existing Matrix room (`/invite @baibot:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:388
+msgid "If you're an allowed bot [👥 user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) (see [👥 Initial users configuration](#-initial-users-configuration)), the bot will accept your invitation and join the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:390
+msgid "After joining, the bot will introduce itself and show information about the [✨ features](https://github.com/etkecc/baibot/blob/main/docs/features.md) that are enabled for it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:392
+msgid "If you've [🤖 configured one or more agents via Ansible](#-configuring-agents-via-ansible) and have [🤝 configured initial default handlers](#configuring-initial-default-handlers), the bot will immediately be able to make use of these agents for this new room. Otherwise, you will need to configure agents and/or handlers via chat commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:394
+msgid "Send `!bai help` to the bot in the room to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:396
+msgid "You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) project's documentation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:398
+msgid "Debugging"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:400
+msgid "As with all other services, you can find service logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-bot-baibot`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:402
+msgid "The default logging level for this service is `info`, but you can increase it to `debug` (or even `trace`) with the following additional configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:416
+msgid "**Alternatively**, you can use a single variable to set the logging level for all of the above (bot + all libraries):"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po
new file mode 100644
index 000000000..55af029e1
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po
@@ -0,0 +1,142 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-23 13:09+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:1
+msgid "Setting up Buscarron (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:3
+msgid "The playbook can install and configure [Buscarron](https://github.com/etkecc/buscarron) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:5
+msgid "Buscarron is bot that receives HTTP POST submissions of web forms and forwards them to a Matrix room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:9
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:32
+msgid "Adjusting the Buscarron URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:34
+msgid "By default, this playbook installs Buscarron on the `buscarron.` subdomain (`buscarron.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:36
+msgid "By tweaking the `matrix_bot_buscarron_hostname` and `matrix_bot_buscarron_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-bot-buscarron.md:38
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:49
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:51
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Buscarron domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:53
+msgid "By default, you will need to create a CNAME record for `buscarron`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:55
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:57
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:59
+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-bot-buscarron.md:66
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:68
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:70
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:72
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:74
+msgid "If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:76
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:78
+msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.buscarron:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:80
+msgid "After the bot joins the room, anyone can call the web form via HTTP POST method."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:82
+msgid "Here is an example for the `contact` form:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:90
+msgid "**Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:92
+msgid "you hit the homepage (HTTP `GET` request to `/`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:93
+msgid "you submit a form to the wrong URL (`POST` request to `/non-existing-form`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:94
+msgid "`hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:96
+msgid "If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:98
+msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/buscarron)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po
new file mode 100644
index 000000000..c54da193f
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po
@@ -0,0 +1,130 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:1
+msgid "Setting up matrix-bot-chatgpt (optional, unmaintained)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:3
+msgid "**Note**: [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) is now an archived (**unmaintained**) project. Talking to ChatGPT (and many other LLM providers) can happen via the much more featureful [baibot](https://github.com/etkecc/baibot), which can be installed using [this playbook](configuring-playbook-bot-baibot.md). Consider using that bot instead of this one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:5
+msgid "The playbook can install and configure [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:7
+msgid "Talk to [ChatGPT](https://openai.com/blog/chatgpt/) via your favourite Matrix client!"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:11
+msgid "Obtain an OpenAI API key"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:13
+msgid "To use the bot, you'd need to obtain an API key from [https://platform.openai.com/account/api-keys](https://platform.openai.com/account/api-keys)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:15
+msgid "Register the bot account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:17
+msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:19
+msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:21
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:27
+msgid "Obtain an access token and create encryption keys"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:29
+msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:31
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:33
+msgid "To make sure the bot can read encrypted messages, it will need an encryption key, just like any other new user. While obtaining the access token, follow the prompts to setup a backup key. More information can be found in the [Element documentation](https://element.io/help#encryption6)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:35
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:37
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `API_KEY_HERE` with the API key retrieved [here](#obtain-an-openai-api-key) and `ACCESS_TOKEN_HERE` with the access token created [here](#obtain-an-access-token-and-create-encryption-keys), respectively."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:54
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:56
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:63
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:65
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:67
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:69
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:71
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:73
+msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.chatgpt:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:75
+msgid "After the bot joins the room, you can send a message to it. When you do so, use the prefix if you configured it or mention the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:77
+msgid "You can also refer to the upstream [documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po
new file mode 100644
index 000000000..bab221487
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po
@@ -0,0 +1,386 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:1
+msgid "Setting up Draupnir (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:3
+msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation bot for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:5
+msgid "See the project's [documentation](https://github.com/the-draupnir-project/Draupnir/blob/main/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:7
+msgid "This documentation page is about installing Draupnir in bot mode. As an alternative, you can run a multi-instance Draupnir deployment by installing [Draupnir in appservice mode](./configuring-playbook-appservice-draupnir-for-all.md) (called Draupnir-for-all) instead."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:9
+msgid "If your migrating from Mjolnir skip to [this section](#migrating-from-mjolnir-only-required-if-migrating)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:13
+msgid "Register the bot account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:15
+msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:17
+msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:19
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:25
+msgid "If you would like Draupnir to be able to deactivate users, move aliases, shutdown rooms, show abuse reports (see [below](#abuse-reports)), etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:27
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:29
+msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:31
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:33
+msgid "Make sure the account is free from rate limiting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:35
+msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Draupnir will crash.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:37
+msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:39
+msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:45
+msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. 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-bot-draupnir.md:47
+msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:49
+msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:55
+msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Draupnir itself. If you have made Draupnir an admin, you can just use the Draupnir token."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:57
+msgid "Create a management room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:59
+msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:61
+msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:63
+msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:65
+msgid "Finally invite the `@bot.draupnir:example.com` account you created earlier into the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:67
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:69
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:78
+msgid "End-to-End Encryption support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:80
+msgid "Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:82
+msgid "To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:84
+msgid "Configuration with E2EE support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:86
+msgid "When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:88
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:102
+msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Draupnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:114
+msgid "Configuration without E2EE support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:116
+msgid "When NOT using Pantalaimon, Draupnir does not log in by itself and you must give it an access token for its bot account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:118
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:124
+msgid "Abuse Reports"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:126
+msgid "Draupnir supports two methods to receive reports in the management room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:128
+msgid "The first method intercepts the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using traefik, this playbook can set this up for you:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:134
+msgid "The other method polls an Synapse Admin API endpoint, hence it is available only if using Synapse and if the Draupnir user is an admin (see [above](#register-the-bot-account)). To enable it, set `pollReports: true` on `vars.yml` file as below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:136
+msgid "Extending the configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:138
+msgid "You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:140
+msgid "For example, to change Draupnir's `pollReports` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:154
+msgid "Migrating from Mjolnir (Only required if migrating)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:156
+msgid "Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:158
+msgid "That is all you need to do due to that Draupnir can complete migration on its own."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:160
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:162
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:169
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:171
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:173
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:175
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:177
+msgid "If you change the Pantalaimon's password (`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:179
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:181
+msgid "You can refer to the upstream [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) for additional ways to use and configure Draupnir and for a more detailed usage guide."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:183
+msgid "Below is a **non-exhaustive quick-start guide** for the impatient."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:185
+msgid "Making Draupnir join and protect a room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:187
+msgid "Draupnir can be told to self-join public rooms, but it's better to follow this flow which works well for all kinds of rooms:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:189
+msgid "Invite the bot to the room manually ([inviting Draupnir to rooms](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#inviting-draupnir-to-rooms)). Before joining, the bot *may* ask for confirmation in the Management Room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:191
+msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:193
+msgid "Tell it to protect the room (using the [rooms command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#using-the-draupnir-rooms-command)) by sending the following command to the Management Room: `!draupnir rooms add !qporfwt:example.com`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:195
+msgid "To have Draupnir provide useful room protection, you need do to a bit more work (at least the first time around). You may wish to [Subscribe to a public policy list](#subscribing-to-a-public-policy-list), [Create your own own policy and rules](#creating-your-own-policy-lists-and-rules) and [Enabling built-in protections](#enabling-built-in-protections)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:197
+msgid "Giving Draupnir permissions to do its job"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:199
+msgid "For Draupnir to do its job, you need to [give it permissions](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#giving-draupnir-permissions) in rooms it's protecting. This involves **giving it an Administrator power level**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:201
+msgid "**We recommend setting this power level as soon as the bot joins your room** (and before you create new rules), so that it can apply rules as soon as they are available. If the bot is under-privileged, it may fail to apply protections and may not retry for a while (or until your restart it)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:203
+msgid "Subscribing to a public policy list"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:205
+msgid "We recommend **subscribing to a public [policy list](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists)** using the [watch command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-watch-command-to-subscribe-to-policy-rooms)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:207
+msgid "Polcy lists are maintained in Matrix rooms. A popular policy list is maintained in the public `#community-moderation-effort-bl:neko.dev` room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:209
+msgid "You can tell Draupnir to subscribe to it by sending the following command to the Management Room: `!draupnir watch #community-moderation-effort-bl:neko.dev`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:211
+msgid "Creating your own policy lists and rules"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:213
+msgid "We also recommend **creating your own policy lists** with the [list create](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-list-create-command-to-create-a-policy-room) command."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:215
+msgid "You can do so by sending the following command to the Management Room: `!draupnir list create my-bans my-bans-bl`. This will create a policy list having a name (shortcode) of `my-bans` and stored in a public `#my-bans-bl:example.com` room on your server. As soon as you run this command, the bot will invite you to the policy list room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:217
+msgid "A policy list does nothing by itself, so the next step is **adding some rules to your policy list**. Policies target a so-called `entity` (one of: `user`, `room` or `server`). These entities are mentioned on the [policy lists](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists) documentation page and in the Matrix Spec [here](https://spec.matrix.org/v1.11/client-server-api/#mban-recommendation)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:219
+msgid "The simplest and most useful entity to target is `user`. Below are a few examples using the [ban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-ban-command) and targeting users."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:221
+msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:223
+msgid "(ban a single user on a given homeserver): `!draupnir ban @charles:example.com my-bans Rude to others`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:224
+msgid "(ban all users on a given homeserver by using a [wildcard](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - all users are fake`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:226
+msgid "As a result of running these commands, you may observe:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:228
+msgid "Draupnir creating `m.policy.rule.user` state events in the `#my-bans-bl:example.com` room on your server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:229
+msgid "applying these rules against all rooms that Draupnir is an Administrator in"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:231
+msgid "You can undo bans with the [unban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-unban-command)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:233
+msgid "Enabling built-in protections"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:235
+msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the room to invite-only\")."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:237
+msgid "To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:239
+msgid "To **see the configuration options for a given protection**, send a `!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get JoinWaveShortCircuit`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:241
+msgid "To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:243
+msgid "To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:245
+msgid "To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po
new file mode 100644
index 000000000..72c8f2272
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po
@@ -0,0 +1,154 @@
+# Translations template for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\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"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:1
+msgid "Setting up Go-NEB (optional, unmaintained)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:3
+msgid "**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an archived (**unmaintained**) project. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bot instead of this one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:5
+msgid "The playbook can install and configure [Go-NEB](https://github.com/matrix-org/go-neb) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:7
+msgid "Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, the original Matrix bot written in Python."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:9
+msgid "See the project's [documentation](https://github.com/matrix-org/go-neb/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:13
+msgid "Register the bot account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:15
+msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:17
+msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:19
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:25
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:27
+msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:29
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:31
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:33
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_GONEB_HERE` and `ACCESS_TOKEN_FOR_ANOTHER_GONEB_HERE` with the ones created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:197
+msgid "Adjusting the Go-NEB URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:199
+msgid "By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:201
+msgid "By tweaking the `matrix_bot_go_neb_hostname` and `matrix_bot_go_neb_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-bot-go-neb.md:203
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:214
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:216
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Go-NEB domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:218
+msgid "By default, you will need to create a CNAME record for `goneb`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:220
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:222
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:224
+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-bot-go-neb.md:231
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:233
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:235
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:237
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:239
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:241
+msgid "To use the bot, invite it to any existing Matrix room (`/invite @bot.go-neb:example.com` where `example.com` is your base domain, not the `matrix.` domain). Make sure you are granted with the sufficient permission if you are not the room owner."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:243
+msgid "Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy matrix`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:245
+msgid "If you enabled the github_cmd service, send `!github help` to the bot in the room to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:247
+msgid "You can also refer to the upstream [Documentation](https://github.com/matrix-org/go-neb)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po
new file mode 100644
index 000000000..06874ae70
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po
@@ -0,0 +1,126 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-23 13:09+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:1
+msgid "Setting up Honoroit (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:3
+msgid "The playbook can install and configure [Honoroit](https://github.com/etkecc/honoroit) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:5
+msgid "It's a bot you can use to setup **your own helpdesk on matrix**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:7
+msgid "See the project's [documentation](https://github.com/etkecc/honoroit/blob/main/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:11
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:26
+msgid "Adjusting the Honoroit URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:28
+msgid "By default, this playbook installs Honoroit on the `matrix.` subdomain, at the `/honoroit` path (https://matrix.example.com/honoroit). 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-bot-honoroit.md:30
+msgid "By tweaking the `matrix_bot_honoroit_hostname` and `matrix_bot_honoroit_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-bot-honoroit.md:32
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:40
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:42
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Honoroit domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:44
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:46
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:48
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:50
+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-bot-honoroit.md:57
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:59
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.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-bot-honoroit.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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:65
+msgid "If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:67
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:69
+msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @honoroit:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:71
+msgid "After the bot joins the room, any Matrix user can send a message to it to start a new thread in that room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:73
+msgid "Send `!ho help` to the bot in the room to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:75
+msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/honoroit#features)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po
new file mode 100644
index 000000000..3471823b4
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po
@@ -0,0 +1,102 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-23 13:09+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:1
+msgid "Setting up matrix-registration-bot (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:3
+msgid "The playbook can install and configure [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:5
+msgid "The bot allows you to easily **create and manage registration tokens** aka. invitation codes. It can be used for an invitation-based server, where you invite someone by sending them a registration token (tokens look like this: `rbalQ0zkaDSRQCOp`). They can register as per normal but have to provide a valid registration token in the final step of the registration process."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:7
+msgid "See the project's [documentation](https://github.com/moan0s/matrix-registration-bot/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:11
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:30
+msgid "The bot account will be created automatically."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:32
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:34
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:41
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:43
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:45
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:47
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:49
+msgid "If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:51
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:53
+msgid "To use the bot, start a chat with `@bot.matrix-registration-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57
+msgid "You can also refer to the upstream [Usage documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:59
+msgid "If you have any questions, or if you need help setting it up, read the [troublshooting guide](https://github.com/moan0s/matrix-registration-bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:61
+msgid "To clean the cache (session & encryption data) after you changed the bot's username, changed the login method from access_token to password etc… you can use:"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po
new file mode 100644
index 000000000..84f39a049
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po
@@ -0,0 +1,98 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-23 13:09+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:1
+msgid "Setting up matrix-reminder-bot (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:3
+msgid "The playbook can install and configure [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:5
+msgid "It's a bot you can use to **schedule one-off & recurring reminders and alarms**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:7
+msgid "See the project's [documentation](https://github.com/anoadragon453/matrix-reminder-bot/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:26
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:28
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:35
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:37
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:39
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:41
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:43
+msgid "If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:45
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:47
+msgid "To use the bot, start a chat with `@bot.matrix-reminder-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:49
+msgid "You can also add the bot to any existing Matrix room (`/invite @bot.matrix-reminder-bot:example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:51
+msgid "Basic usage is like this: `!remindme in 2 minutes; This is a test`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:53
+msgid "Send `!help reminders` to the room to see the bot's help menu for additional commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:55
+msgid "You can also refer to the upstream [Usage documentation](https://github.com/anoadragon453/matrix-reminder-bot#usage)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po
new file mode 100644
index 000000000..f4130be13
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po
@@ -0,0 +1,167 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:1
+msgid "Setting up maubot (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:3
+msgid "The playbook can install and configure [maubot](https://github.com/maubot/maubot) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:5
+msgid "After setting up maubot, you can use the web management interface to make it do things. The default location of the management interface is `matrix.example.com/_matrix/maubot/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:7
+msgid "See the project's [documentation](https://docs.mau.fi/maubot/usage/basic.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:11
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:26
+msgid "You can add multiple admins. The admin accounts are only used to access the maubot administration interface."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:28
+msgid "Adjusting the maubot URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:30
+msgid "By default, this playbook installs maubot on the `matrix.` subdomain, at the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/). 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-bot-maubot.md:32
+msgid "By tweaking the `matrix_bot_maubot_hostname` and `matrix_bot_maubot_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-bot-maubot.md:34
+#: ../../../docs/configuring-playbook-bot-maubot.md:56
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:42
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:44
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the maubot domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:46
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:48
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:50
+msgid "Customizing the maubot container image"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:52
+msgid "Certain [maubot plugins](https://plugins.mau.bot/) require additional dependencies to be installed."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:54
+msgid "You can customize the default maubot container image and install your own dependencies."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:67
+msgid "Consult the [Dockerfile reference](https://docs.docker.com/reference/dockerfile/) for more information about the syntax."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:69
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:71
+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-bot-maubot.md:78
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:80
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:82
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:84
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:86
+msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:88
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:90
+msgid "By default, you can visit `matrix.example.com/_matrix/maubot/` to manage your available plugins, clients and instances."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:92
+msgid "You should start in the following order"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:93
+msgid "**Create one or more clients**: A client is a Matrix account which the bot will use to message. By default, the playbook creates a `bot.maubot` account (as per the configuration above). You only need to [obtain an access token](#obtaining-an-access-token) for it"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:94
+msgid "**Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:95
+msgid "**Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:97
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:99
+msgid "This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:101
+msgid "Alternatively, you can refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will causes issues to your bot in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:103
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po
new file mode 100644
index 000000000..148e91976
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po
@@ -0,0 +1,226 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:1
+msgid "Setting up Mjolnir (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:3
+msgid "The playbook can install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation bot for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:5
+msgid "See the project's [documentation](https://github.com/matrix-org/mjolnir/blob/main/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:7
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:9
+msgid "Register the bot account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:11
+msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:13
+msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:15
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:21
+msgid "If you would like Mjolnir to be able to deactivate users, move aliases, shutdown rooms, etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:23
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:25
+msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:27
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:29
+msgid "Make sure the account is free from rate limiting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:31
+msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:33
+msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:35
+msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:41
+msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. 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-bot-mjolnir.md:43
+msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:45
+msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:51
+msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Mjolnir itself. If you have made Mjolnir an admin, you can just use the Mjolnir token."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:53
+msgid "Create a management room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:55
+msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:57
+msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:59
+msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:61
+msgid "Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:63
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:65
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:74
+msgid "End-to-End Encryption support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:76
+msgid "Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:78
+msgid "To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:80
+msgid "Configuration with E2EE support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:82
+msgid "When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:84
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:98
+msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Mjolnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:110
+msgid "Configuration without E2EE support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:112
+msgid "When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:114
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:120
+msgid "Adding Mjolnir synapse antispam module (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:122
+msgid "To enable Mjolnir synapse antispam module, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:132
+msgid "Extending the configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:134
+msgid "You can configure additional options by adding the `matrix_bot_mjolnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:136
+msgid "For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:150
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:152
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:159
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:161
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:163
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:165
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:167
+msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:169
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:171
+msgid "You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po
new file mode 100644
index 000000000..c57241d4d
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po
@@ -0,0 +1,171 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:1
+msgid "Setting up Appservice Discord bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:3
+msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:4
+msgid "For using as a Bot we are recommend the Appservice Discord bridge (the one being discussed here), because it supports plumbing."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:5
+msgid "For personal use we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:7
+msgid "The playbook can install and configure [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:9
+msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-discord/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:13
+msgid "Create a Discord Application [here](https://discordapp.com/developers/applications). Then retrieve Client ID, and create a bot from the Bot tab and retrieve the Bot token."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:15
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:17
+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-discord.md:31
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:33
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:40
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:42
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:44
+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-discord.md:46
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:48
+msgid "Self-Service Bridging (Manual)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:50
+msgid "Self-service bridging allows you to bridge specific and existing Matrix rooms to specific Discord rooms. To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:56
+msgid "**Note**: If self-service bridging is not enabled, `!discord help` commands will return no results."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:58
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:82
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:60
+msgid "Once self-service is enabled, start a chat with `@_discord_bot:example.com` and say `!discord help bridge`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:62
+msgid "Then, follow the instructions in the help output message."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:64
+msgid "If the bot is not already in the Discord server, follow the provided invite link. This may require you to be a administrator of the Discord server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:66
+msgid "On the Discord side, send `!matrix help` to the bot to see the available commands for managing the bridge and Matrix users."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:68
+msgid "**Note**: Encrypted Matrix rooms are not supported as of writing."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:70
+msgid "Portal Bridging (Automatic)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:72
+msgid "Through portal bridging, Matrix rooms will automatically be created by the bot and bridged to the relevant Discord room. This is done by simply joining a room with a specific name pattern (`#_discord_<guildID>_<channelID>`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:74
+msgid "All Matrix rooms created this way are **listed publicly** by default, and you will not have admin permissions to change this. To get more control, [make yourself a room Administrator](#getting-administrator-access-in-a-portal-bridged-room). You can then unlist the room from the directory and change the join rules."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:76
+msgid "To disable portal bridging, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:84
+msgid "To get started with Portal Bridging:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:86
+msgid "To invite the bot to Discord, retrieve the invite link from the `{{ matrix_appservice_discord_config_path }}/invite_link` file on the server (this defaults to `/matrix/appservice-discord/config/invite_link`). You need to peek at the file on the server via SSH, etc., because it's not available via HTTP(S)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:87
+msgid "Room addresses follow this syntax: `#_discord_<guildID>_<channelID>`. You can easily find the guild and channel IDs by logging into Discord in a browser and opening the desired channel. The URL will have this format: `discord.com/channels/<guildID>/<channelID>`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:88
+msgid "Once you have figured out the appropriate room address, you can join by doing `/join #_discord_<guildID>_<channelID>` in your Matrix client."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:90
+msgid "Getting Administrator access in a portal bridged room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:92
+msgid "By default, you won't have Administrator access in rooms created by the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:94
+msgid "To adjust room access privileges or do various other things (change the room name subsequently, etc.), you'd wish to become an Administrator."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:96
+msgid "There's the Discord bridge's guide for [setting privileges on bridge managed rooms](https://github.com/matrix-org/matrix-appservice-discord/blob/master/docs/howto.md#set-privileges-on-bridge-managed-rooms). To do the same with our container setup, run the following command on the server:"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po
new file mode 100644
index 000000000..f4723b399
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po
@@ -0,0 +1,78 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:1
+msgid "Setting up Appservice IRC bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:3
+msgid "**Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [Heisenbridge](configuring-playbook-bridge-heisenbridge.md) bridge supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:5
+msgid "The playbook can install and configure the [matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc) bridge for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:7
+msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-irc/blob/master/HOWTO.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:11
+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-irc.md:63
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:65
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:72
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:74
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:76
+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-irc.md:78
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:80
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:82
+msgid "To use the bridge, you need to start a chat with `@irc_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po
new file mode 100644
index 000000000..c9efff085
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po
@@ -0,0 +1,162 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:1
+msgid "Setting up Appservice Kakaotalk bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:3
+msgid "The playbook can install and configure [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) for you. `matrix-appservice-kakaotalk` is a bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:5
+msgid "⚠️ **Warning**: there have been recent reports (~2022-09-16) that **using this bridge may get your account banned**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:7
+msgid "See the project's [documentation](https://src.miscworks.net/fair/matrix-appservice-kakaotalk/src/branch/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:9
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:11
+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 [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:13
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:15
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:17
+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-kakaotalk.md:23
+msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:25
+msgid "Additional configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:27
+msgid "There are some additional things you may wish to configure about the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:29
+msgid "Take a look at:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:31
+msgid "`roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:32
+msgid "`roles/custom/matrix-bridge-appservice-kakaotalk/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_kakaotalk_configuration_extension_yaml` variable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:34
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:36
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:43
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:45
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:47
+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-kakaotalk.md:49
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:51
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:53
+msgid "To use the bridge, you need to start a chat with `@kakaotalkbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:55
+msgid "Send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable bridging for your Kakaotalk account. The `--save` flag may be omitted, if you'd rather not save your password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:57
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:59
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:61
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:63
+msgid "Method 1: automatically, by enabling Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:65
+msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:67
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:69
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:71
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:73
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:75
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:77
+msgid "make sure you don't log out the `Appservice-Kakaotalk` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po
new file mode 100644
index 000000000..d290ee5a5
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po
@@ -0,0 +1,248 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:1
+msgid "Setting up Appservice Slack bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:3
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:75
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:4
+msgid "Bridging to [Slack](https://slack.com) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:5
+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:7
+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:9
+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:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:13
+msgid "Create a Classic Slack App"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:15
+msgid "First, you need to create a Classic Slack App [here](https://api.slack.com/apps?new_classic_app=1)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:17
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:19
+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:21
+msgid "Add the following events as `Bot User Events` and save:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:23
+msgid "team_domain_change"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:24
+msgid "message.channels"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:25
+msgid "message.groups (if you want to bridge private channels)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:26
+msgid "reaction_added"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:27
+msgid "reaction_removed"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:29
+msgid "Next, click on \"OAuth & Permissions\" and add the following scopes:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:31
+msgid "chat:write:bot"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:32
+msgid "users:read"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:33
+msgid "reactions:write"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:34
+msgid "files:write:user (if you want to bridge files)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:36
+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:38
+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:40
+msgid "Create an administration control room on Matrix"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:42
+msgid "Create a new Matrix room to act as the administration control room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:44
+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:46
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:48
+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:64
+msgid "Other configuration options are available via the `matrix_appservice_slack_configuration_extension_yaml` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:66
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:68
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:77
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.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-bridge-appservice-slack.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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:83
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:85
+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:87
+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:89
+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:90
+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:91
+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:92
+msgid "Issue a link command in the administration control room with these collected values as arguments:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:94
+msgid "with file bridging:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:100
+msgid "without file bridging:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:106
+msgid "These arguments can be shortened to single-letter forms:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:112
+msgid "Unlinking"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:114
+msgid "Channels can be unlinked again by sending this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:120
+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:122
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:124
+msgid "As always, check the logs: `journalctl -fu matrix-appservice-slack`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:126
+msgid "Linking: \"Room is now pending-name\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:128
+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:130
+msgid "Messages work from Matrix to Slack, but not the other way around"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:132
+msgid "Check you logs, if they say something like"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:134
+#, python-format
+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:136
+msgid "then unlink your room, reinvite the bot and re-link it again. This may particularly hit you, if you tried to unsuccessfully link your room multiple times without unlinking it after each failed attempt."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po
new file mode 100644
index 000000000..64a274009
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po
@@ -0,0 +1,114 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:1
+msgid "Setting up Appservice Webhooks bridging (optional, deprecated)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:3
+msgid "**Note**: This bridge has been deprecated. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bridge instead of this one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:5
+msgid "The playbook can install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:7
+msgid "See the project's [documentation](https://github.com/turt2live/matrix-appservice-webhooks/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:11
+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-webhooks.md:27
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:29
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:36
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:38
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:40
+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-webhooks.md:42
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:44
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:46
+msgid "To use the bridge, you need to invite the bridge bot user to your room in either way."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:48
+msgid "Send `/invite @_webhook:example.com` (**Note**: Make sure you have administration permissions in your room)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:49
+msgid "Add the bridge bot to a private channel (personal channels imply you being an administrator)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:51
+msgid "You then need to send a message to the bridge bot in order to receive a private message including the webhook link:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:57
+msgid "The JSON body for posting messages will have to look like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:68
+msgid "You can test this via curl like so:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:81
+msgid "Setting Webhooks with Dimension integration manager"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:83
+msgid "If you're using the [Dimension integration manager](configuring-playbook-dimension.md), you can configure the Webhooks bridge with it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:85
+msgid "To configure it, open the Dimension integration manager, and go to \"Settings\" and \"Bridges\", then select edit action for \"Webhook Bridge\"."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:87
+msgid "On the UI, press \"Add self-hosted Bridge\" button and populate \"Provisioning URL\"  and \"Shared Secret\" values from `/matrix/appservice-webhooks/config/config.yaml` file's homeserver URL value and provisioning secret value, respectively."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po
new file mode 100644
index 000000000..d837a775d
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po
@@ -0,0 +1,130 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:1
+msgid "Setting up Beeper Linkedin bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:3
+msgid "The playbook can install and configure [beeper-linkedin](https://github.com/beeper/linkedin) for you, for bridging to [LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on the mautrix-python framework and can be configured in a similar way to the other mautrix bridges"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:5
+msgid "See the project's [documentation](https://github.com/beeper/linkedin/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:9
+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-beeper-linkedin.md:15
+msgid "There are some additional things you may wish to configure about the bridge before you continue."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:17
+msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:24
+msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:33
+msgid "You may wish to look at `roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2` to find other things you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:35
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:37
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:44
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:46
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:48
+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-beeper-linkedin.md:50
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:52
+msgid "Set up Double Puppeting by enabling Appservice Double Puppet or Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:54
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:56
+msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:58
+msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:60
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:62
+msgid "To use the bridge, you need to start a chat with `@linkedinbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:64
+msgid "Send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to enable bridging for your LinkedIn account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:66
+msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:68
+msgid "After successfully enabling bridging, you may wish to [set up Double Puppeting](#set-up-double-puppeting-by-enabling-appservice-double-puppet-or-shared-secret-auth), if you haven't already done so."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:70
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:72
+msgid "Bridge asking for 2FA even if you don't have 2FA enabled"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:74
+msgid "If you don't have 2FA enabled and are logging in from a strange IP for the first time, LinkedIn will send an email with a one-time code. You can use this code to authorize the bridge session. In my experience, once the IP is authorized, you will not be asked again."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po
new file mode 100644
index 000000000..76a31dbd3
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po
@@ -0,0 +1,78 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:1
+msgid "Setting up Go Skype Bridge bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:3
+msgid "The playbook can install and configure [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:5
+msgid "See the project's [documentation](https://github.com/kelaresg/go-skype-bridge/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:9
+msgid "To enable the [Skype](https://www.skype.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:15
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:17
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:24
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:26
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:28
+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-go-skype-bridge.md:30
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:32
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:34
+msgid "To use the bridge, you need to start a chat with `Skype bridge bot` with the handle `@skypebridgebot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:36
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po
new file mode 100644
index 000000000..028356920
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po
@@ -0,0 +1,130 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:1
+msgid "Setting up Heisenbridge bouncer-style IRC bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:3
+msgid "**Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md) bridge supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:5
+msgid "The playbook can install and configure [Heisenbridge](https://github.com/hifi/heisenbridge) - the bouncer-style [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) bridge for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:7
+msgid "See the project's [documentation](https://github.com/hifi/heisenbridge/blob/master/README.md) to learn what it does and why it might be useful to you. You can also take a look at [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:9
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:11
+msgid "To enable Heisenbridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:24
+msgid "For a more complete list of variables that you could override, see the [`defaults/main.yml` file](../roles/custom/matrix-bridge-heisenbridge/defaults/main.yml) of the Heisenbridge Ansible role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:26
+msgid "Adjusting the Heisenbridge URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:28
+msgid "By default, this playbook installs Heisenbridge on the `matrix.` subdomain, at the `/heisenbridge` path (https://matrix.example.com/heisenbridge). It would handle media requests there (see the [release notes for Heisenbridge v1.15.0](https://github.com/hifi/heisenbridge/releases/tag/v1.15.0))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:30
+msgid "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-bridge-heisenbridge.md:32
+msgid "By tweaking the `matrix_heisenbridge_hostname` and `matrix_heisenbridge_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-bridge-heisenbridge.md:34
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:42
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:44
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Heisenbridge domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:46
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:48
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:50
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:52
+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-bridge-heisenbridge.md:59
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:61
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:63
+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-heisenbridge.md:65
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:67
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:69
+msgid "To use the bridge, you need to start a chat with `@heisenbridge:example.com` (where `example.com` is your base domain, not the `matrix.` domain). If the bridge ignores you and a DM is not accepted then the owner setting may be wrong."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:71
+msgid "Help is available for all commands with the `-h` switch."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:73
+msgid "You can also learn the basics by watching [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:75
+msgid "If you encounter issues or feel lost you can join the project room at [#heisenbridge:vi.fi](https://matrix.to/#/#heisenbridge:vi.fi) for help."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po
new file mode 100644
index 000000000..4c3b51aae
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po
@@ -0,0 +1,386 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:1
+msgid "Setting up matrix-hookshot (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:3
+msgid "The playbook can install and configure [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:5
+msgid "Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) from software project management services such as GitHub, GitLab, Jira, and Figma, as well as generic webhooks."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:7
+msgid "See the project's [documentation](https://matrix-org.github.io/matrix-hookshot/latest/hookshot.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:9
+msgid "**Note**: the playbook also supports [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), which however was deprecated by its author."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:13
+msgid "Download GitHub app private key (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:15
+msgid "If you're setting up the GitHub bridge, you need to create your GitHub app, and generate a private key file of it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:17
+msgid "You need to download the private key file, if you will install the file manually or with the `aux` role. For details, see [the section below](#manage-github-private-key-with-aux-role)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:19
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:21
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `GITHUB_PRIVATE_KEY_HERE` with the one created [above](#download-github-app-private-key)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:35
+msgid "For each of the services (GitHub, GitLab, Jira, Figma, and generic webhooks) fill in the respective variables `matrix_hookshot_service_*` listed in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) as required."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:37
+msgid "Take special note of the `matrix_hookshot_*_enabled` variables. Services that need no further configuration are enabled by default (GitLab and generic webhooks), while you must first add the required configuration and enable the others (GitHub, Jira, and Figma)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:39
+msgid "Extending the configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:41
+msgid "You can configure additional options by adding the `matrix_hookshot_configuration_extension_yaml` and `matrix_hookshot_registration_extension_yaml` variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:43
+msgid "Refer the [official instructions](https://matrix-org.github.io/matrix-hookshot/latest/setup.html) and the comments in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) to learn what the individual options do."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:45
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:47
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:54
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service hookshot` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:56
+msgid "`just install-service hookshot` is useful for maintaining your setup quickly 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 `just setup-all` runs the `ensure-matrix-users-created` tag too."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:58
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:60
+msgid "To use the bridge, you need to create a room and invite the Hookshot bot (`@hookshot:example.com`) to it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:62
+msgid "Make sure the bot is able to send state events (usually the Moderator power level in clients)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:64
+msgid "Send `!hookshot help` to the bot to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:66
+msgid "Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-hookshot/latest/usage.html) for more details about using the bridge's various features."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:68
+msgid "💡 **Note**: the different listeners are bound to certain paths which might differ from those assumed by the hookshot documentation. See [URLs for bridges setup](#urls-for-bridges-setup) below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:70
+msgid "Reset crypto store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:72
+msgid "Should the crypto store be corrupted, you can reset it by executing this Ansible playbook with the tag `reset-hookshot-encryption` added:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:78
+msgid "More setup documentation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:80
+msgid "URLs for bridges setup"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:82
+msgid "Unless indicated otherwise, the following endpoints are reachable on your `matrix.` subdomain (if the feature is enabled)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Listener"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Default path"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Variable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Used as"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "-"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/hookshot/webhooks/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_webhook_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Webhook-prefix, which affects all webhook-related URLs below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "generic"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/hookshot/webhooks/webhook`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_generic_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Generic webhooks"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "github oauth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/hookshot/webhooks/oauth`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_github_oauth_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "GitHub \"Callback URL\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "jira oauth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/hookshot/webhooks/jira/oauth`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_jira_oauth_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Jira OAuth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "figma endpoint"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/hookshot/webhooks/figma/webhook`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_figma_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Figma"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "provisioning"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/hookshot/v1/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_provisioning_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Dimension [provisioning](#provisioning-api)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "appservice"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/hookshot/_matrix/app/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_appservice_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Matrix server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "widgets"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/hookshot/widgetapi/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_widgets_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Widgets"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "metrics"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/metrics/hookshot`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_metrics_enabled` and exposure enabled via `matrix_hookshot_metrics_proxying_enabled` or `matrix_metrics_exposure_enabled`. Read more in the [Metrics section](#metrics) below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Prometheus"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:96
+msgid "Also see the various `matrix_hookshot_container_labels_*` variables in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), which expose URLs publicly"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:98
+msgid "The different listeners are also reachable *internally* in the docker-network via the container's name (configured by `matrix_hookshot_container_url`) and on different ports (e.g. `matrix_hookshot_appservice_port`). Read [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) in detail for more info."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:100
+msgid "Manage GitHub Private Key with aux role"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:102
+msgid "The GitHub bridge requires you to install a private key file. This can be done in multiple ways:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:104
+msgid "copy the *contents* of the downloaded file and set the variable `matrix_hookshot_github_private_key` to the contents (see example in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:105
+msgid "somehow copy the file to the path `{{ matrix_hookshot_base_path }}/{{ matrix_hookshot_github_private_key_file }}` (default: `/matrix/hookshot/private-key.pem`) on the server manually."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:106
+msgid "use the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) to copy the file from an arbitrary path on your ansible client to the correct path on the server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:108
+msgid "To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:119
+msgid "For more information, see the documentation in the [default configuration of the aux role](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:121
+msgid "Provisioning API"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:123
+msgid "The provisioning API will be enabled automatically if you set `matrix_dimension_enabled: true` and provided a `matrix_hookshot_provisioning_secret`, unless you override it either way. To use hookshot with dimension, you will need to enter as \"Provisioning URL\": `http://matrix-hookshot:9002`, which is made up of the variables `matrix_hookshot_container_url` and `matrix_hookshot_provisioning_port`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:125
+msgid "Metrics"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:127
+msgid "Metrics are **only enabled by default** if the builtin [Prometheus](configuring-playbook-prometheus-grafana.md) is enabled (by default, Prometheus isn't enabled). If so, metrics will automatically be collected by Prometheus and made available in Grafana. You will, however, need to set up your own Dashboard for displaying them."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:129
+msgid "To explicitly enable metrics, use `matrix_hookshot_metrics_enabled: true`. This only exposes metrics over the container network, however."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:131
+msgid "**To collect metrics from an external Prometheus server**, besides enabling metrics as described above, you will also need to enable metrics exposure on `https://matrix.example.com/metrics/hookshot` by:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:133
+msgid "either enabling metrics exposure for Hookshot via `matrix_hookshot_metrics_proxying_enabled: true`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:134
+msgid "or enabling metrics exposure for all services via `matrix_metrics_exposure_enabled: true`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:136
+msgid "Whichever one you go with, by default metrics are exposed publicly **without** password-protection. See [the Prometheus and Grafana docs](configuring-playbook-prometheus-grafana.md) for details about password-protection for metrics."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:138
+msgid "Collision with matrix-appservice-webhooks"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:140
+msgid "If you are also running [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), it reserves its namespace by the default setting `matrix_appservice_webhooks_user_prefix: '_webhook_'`. You should take care if you modify its or hookshot's prefix that they do not collide with each other's namespace (default `matrix_hookshot_generic_userIdPrefix: '_webhooks_'`)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po
new file mode 100644
index 000000000..c2f8ef9ba
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po
@@ -0,0 +1,78 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:1
+msgid "Setting up Matrix SMS bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:3
+msgid "The playbook can install and configure [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:5
+msgid "See the project's [documentation](https://github.com/benkuly/matrix-sms-bridge/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:7
+msgid "**The bridge uses [android-sms-gateway-server](https://github.com/RebekkaMa/android-sms-gateway-server). You need to configure it first.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:11
+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-matrix-bridge-sms.md:34
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:36
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:43
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:45
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:47
+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-matrix-bridge-sms.md:49
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:51
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:53
+msgid "Read the [user guide](https://github.com/benkuly/matrix-sms-bridge/blob/master/README.md#user-guide) to see how this bridge works."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po
new file mode 100644
index 000000000..bd0311833
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po
@@ -0,0 +1,246 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:1
+msgid "Setting up Mautrix Discord bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:3
+msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md) bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:4
+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:5
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:7
+msgid "The playbook can install and configure [mautrix-discord](https://github.com/mautrix/discord) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:9
+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:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:13
+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)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:15
+msgid "If this is a dealbreaker for you, consider using one of the other Discord bridges supported by the playbook: [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) or [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md). These come with their own complexity and limitations, however, so we recommend that you proceed with this one if possible."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:17
+msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:19
+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:21
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:23
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:25
+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:31
+msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:33
+msgid "Additional configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:35
+msgid "There are some additional things you may wish to configure about the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:37
+msgid "Take a look at:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:39
+msgid "`roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:40
+msgid "`roles/custom/matrix-bridge-mautrix-discord/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_mautrix_discord_configuration_extension_yaml` variable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:42
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:44
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:51
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:53
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.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-discord.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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:59
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:61
+msgid "Logging in"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:63
+msgid "Method 1: Login using QR code (recommended)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:65
+msgid "For using this bridge, you would need to authenticate by **scanning a QR code** with the Discord app on your phone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:67
+msgid "You can delete the Discord app after the authentication process."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:69
+msgid "Method 2: Login using Discord token (not recommended)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:71
+msgid "To acquire the token, open Discord in a private browser window. Then open the developer settings (keyboard shortcut might be \"ctrl+shift+i\" or by pressing \"F12\"). Navigate to the \"Network\" tab then reload the page. In the URL filter or search bar type \"/api\" and find the response with the file name of \"library\". Under the request headers you should find a variable called \"Authorization\", this is the token to your Discord account. After copying the token, you can close the browser window."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:73
+msgid "Bridging"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:75
+msgid "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:76
+msgid "If you would like to login to Discord using a token, send `login-token` command, otherwise, send `login-qr` command."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:77
+msgid "You'll see a QR code which you need to scan with the Discord app on your phone. You can scan it with the camera app too, which will open Discord, which will then instruct you to scan it a 2nd time in the Discord app."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:78
+msgid "After confirming (in the Discord app) that you'd like to allow this login, the bot should respond with \"Succcessfully authenticated as …\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:79
+msgid "Now that you're logged in, you can send `help` to the bot to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:80
+msgid "Some Direct Messages from Discord should start syncing automatically"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:81
+msgid "If you'd like to bridge guilds:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:82
+msgid "send `guilds status` to see the list of guilds"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:83
+msgid "for each guild that you'd like bridged, send `guilds bridge GUILD_ID --entire`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:84
+msgid "You may wish to uninstall the Discord app from your phone now. It's not needed for the bridge to function."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:86
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:88
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:90
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:92
+msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:94
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:96
+msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:98
+msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:100
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:102
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:104
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:106
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:108
+msgid "make sure you don't log out the `Mautrix-Discord` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po
new file mode 100644
index 000000000..a16acf802
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po
@@ -0,0 +1,202 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:1
+msgid "Setting up Mautrix Facebook bridging (optional, deprecated)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:3
+msgid "**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md). Consider using that bridge instead of this one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:5
+msgid "The playbook can install and configure [mautrix-facebook](https://github.com/mautrix/facebook) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:7
+msgid "See the project's [documentation](https://github.com/mautrix/facebook/blob/master/ROADMAP.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:9
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:11
+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 [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:13
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:15
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:17
+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-facebook.md:23
+msgid "There are some additional things you may wish to configure about the bridge before you continue."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:25
+msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:35
+msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:44
+msgid "Using both would look like"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:56
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml` to find other things you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:58
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:60
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:67
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:69
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:71
+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-facebook.md:73
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:75
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:77
+msgid "To use the bridge, you need to start a chat with `@facebookbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:79
+msgid "Send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable bridging for your Facebook Messenger account. You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/facebook/authentication.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:81
+msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:83
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:85
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:87
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:89
+msgid "Method 1: automatically, by enabling Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:91
+msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:93
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:95
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:97
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:99
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:101
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:103
+msgid "make sure you don't log out the `Mautrix-Facebook` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:105
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:107
+msgid "Facebook rejecting login attempts and forcing you to change password"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:109
+msgid "If your Matrix server is in a wildly different location than where you usually use your Facebook account from, the bridge's login attempts may be outright rejected by Facebook. Along with that, Facebook may even force you to change the account's password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:111
+msgid "If you happen to run into this problem while [setting up bridging](#usage), try to first get a successful session up by logging in to Facebook through the Matrix server's IP address."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:113
+msgid "The easiest way to do this may be to use [sshuttle](https://sshuttle.readthedocs.io/) to proxy your traffic through the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:115
+msgid "Example command for proxying your traffic through the Matrix server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:121
+msgid "Once connected, you should be able to verify that you're browsing the web through the Matrix server's IP by checking [icanhazip](https://icanhazip.com/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:123
+msgid "Then proceed to log in to [Facebook/Messenger](https://www.facebook.com/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:125
+msgid "Once logged in, proceed to [set up bridging](#usage)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:127
+msgid "If that doesn't work, enable 2FA (see: [Facebook help page on enabling 2FA](https://www.facebook.com/help/148233965247823)) and try to login again with a new password, and entering the 2FA code when prompted, it may take more then one try, in between attempts, check facebook.com to see if they are requiring another password change"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po
new file mode 100644
index 000000000..40bc5001c
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po
@@ -0,0 +1,130 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:1
+msgid "Setting up Mautrix Google Messages bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:3
+msgid "The playbook can install and configure [mautrix-gmessages](https://github.com/mautrix/gmessages) for you, for bridging to [Google Messages](https://messages.google.com/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:5
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/gmessages/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:7
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:9
+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) for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:11
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:15
+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-gmessages.md:21
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:23
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:30
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:32
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:34
+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-gmessages.md:36
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:38
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:40
+msgid "To use the bridge, you need to start a chat with `@gmessagesbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:42
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:44
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:46
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:48
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:50
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:52
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:54
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:56
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:58
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:60
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:62
+msgid "make sure you don't log out the `Mautrix-gmessages` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po
new file mode 100644
index 000000000..3fd090658
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po
@@ -0,0 +1,150 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:1
+msgid "Setting up Mautrix Google Chat bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:3
+msgid "The playbook can install and configure [mautrix-googlechat](https://github.com/mautrix/googlechat) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:5
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/googlechat/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:7
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:9
+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-googlechat.md:11
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:15
+msgid "To enable the [Google Chat](https://chat.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:21
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:23
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:30
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:32
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:34
+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-googlechat.md:36
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:38
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:40
+msgid "To use the bridge, you need to start a chat with `googlechat bridge bot` with handle `@googlechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:42
+msgid "Send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:44
+msgid "Automatic login may not work. If it does not, reload the page and select the \"Manual login\" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:46
+msgid "Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:48
+msgid "You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:50
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:52
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:54
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:56
+msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:58
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:60
+msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:62
+msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:64
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:66
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:68
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:70
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:72
+msgid "make sure you don't log out the `Mautrix-googlechat` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po
new file mode 100644
index 000000000..0d552d93a
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po
@@ -0,0 +1,150 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:1
+msgid "Setting up Mautrix Hangouts bridging (optional, deprecated)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:3
+msgid "💡 **Note**: This bridge has been deprecated in favor of [Google Chat bridge](https://github.com/mautrix/googlechat), which can be installed using [this playbook](configuring-playbook-bridge-mautrix-googlechat.md). Installing the mautrix-hangouts bridge is **no longer possible**. For now, this documentation page remains here for historical purposes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:5
+msgid "The playbook can install and configure [mautrix-hangouts](https://github.com/mautrix/hangouts) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:7
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/hangouts/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:9
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:11
+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 [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:13
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:15
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:17
+msgid "To enable the [Google Hangouts](https://hangouts.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:23
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:25
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:32
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:34
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:36
+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-hangouts.md:38
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:40
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:42
+msgid "To use the bridge, you need to start a chat with `Hangouts bridge bot` with handle `@hangoutsbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:44
+msgid "Send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:46
+msgid "Automatic login may not work. If it does not, reload the page and select the \"Manual login\" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:48
+msgid "Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:50
+msgid "You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/hangouts/authentication.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:52
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:54
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:56
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:58
+msgid "Method 1: automatically, by enabling Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:60
+msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:62
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:64
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:66
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:68
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:70
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:72
+msgid "make sure you don't log out the `Mautrix-Hangouts` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po
new file mode 100644
index 000000000..71ddb21c6
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po
@@ -0,0 +1,102 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:1
+msgid "Setting up Mautrix Instagram bridging (optional, deprecated)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:3
+msgid "**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-instagram.md). Consider using that bridge instead of this one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:5
+msgid "The playbook can install and configure [mautrix-instagram](https://github.com/mautrix/instagram) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:7
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/instagram/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:11
+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-instagram.md:17
+msgid "There are some additional things you may wish to configure about the bridge before you continue."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:19
+msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:29
+msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:43
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml` to find other things you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:45
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:47
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:54
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:56
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:58
+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-instagram.md:60
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:62
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:64
+msgid "To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:66
+msgid "Send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the bridge bot to enable bridging for your instagram/Messenger account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:68
+msgid "You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/instagram/authentication.html)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po
new file mode 100644
index 000000000..e1c347b88
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po
@@ -0,0 +1,210 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:1
+msgid "Setting up Instagram bridging via Mautrix Meta (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:3
+msgid "The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:5
+msgid "Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:7
+msgid "This documentation page only deals with the bridge's ability to bridge to Instagram. For bridging to Facebook/Messenger, see [Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:11
+msgid "Migrating from the old mautrix-instagram bridge"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:13
+msgid "If you've been using the [mautrix-instagram](./configuring-playbook-bridge-mautrix-instagram.md) bridge, **you'd better get rid of it first** or the 2 bridges will be in conflict:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:15
+msgid "both trying to use `@instagrambot:example.com` as their username. This conflict may be resolved by adjusting `matrix_mautrix_instagram_appservice_bot_username` or `matrix_mautrix_meta_instagram_appservice_username`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:16
+msgid "both trying to bridge the same DMs"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:18
+msgid "To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@instagrambot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:20
+msgid "Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:22
+msgid "Enable Appservice Double Puppet (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:24
+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-meta-instagram.md:26
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:28
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:30
+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-meta-instagram.md:36
+msgid "Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:38
+msgid "Bridge permissions"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:40
+msgid "By default, any user on your homeserver will be able to use the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:42
+msgid "Different levels of permission can be granted to users:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:44
+msgid "`relay` - Allowed to be relayed through the bridge, no access to commands"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:45
+msgid "`user` - Use the bridge with puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:46
+msgid "`admin` - Use and administer the bridge"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:48
+msgid "The permissions are following the sequence: nothing < `relay` < `user` < `admin`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:50
+msgid "The default permissions are set via `matrix_mautrix_meta_instagram_bridge_permissions_default` and are somewhat like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:59
+msgid "If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:61
+msgid "You may redefine `matrix_mautrix_meta_instagram_bridge_permissions_default` any way you see fit, or add extra permissions using `matrix_mautrix_meta_instagram_bridge_permissions_custom` like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:68
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-instagram/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:70
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:72
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:79
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:81
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:83
+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-meta-instagram.md:85
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:87
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:89
+msgid "To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:91
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:93
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:95
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:97
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:99
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:101
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:103
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:105
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:107
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:109
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:111
+msgid "make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po
new file mode 100644
index 000000000..905ac480e
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po
@@ -0,0 +1,246 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:1
+msgid "Setting up Messenger bridging via Mautrix Meta (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:3
+msgid "The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:5
+msgid "Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:7
+msgid "This documentation page only deals with the bridge's ability to bridge to Facebook Messenger. For bridging to Instagram, see [Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:11
+msgid "Migrating from the old mautrix-facebook bridge"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:13
+msgid "If you've been using the [mautrix-facebook](./configuring-playbook-bridge-mautrix-facebook.md) bridge, it's possible to migrate the database using [instructions from the bridge documentation](https://docs.mau.fi/bridges/go/meta/facebook-migration.html) (advanced)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:15
+msgid "Then you may wish to get rid of the Facebook bridge. To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@facebookbot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:17
+msgid "Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:19
+msgid "**Note**: the user ID of the new bridge bot is `@messengerbot:example.com`, not `@facebookbot:example.com`. After disabling the old bridge, its bot user will stop responding to a command."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:21
+msgid "Enable Appservice Double Puppet (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:23
+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-meta-messenger.md:25
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:27
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:29
+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-meta-messenger.md:35
+msgid "Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:37
+msgid "Bridge mode"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:39
+msgid "As mentioned above, the [mautrix-meta](https://github.com/mautrix/meta) bridge supports multiple modes of operation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:41
+msgid "The bridge can pull your Messenger messages via 3 different methods:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:43
+msgid "(`facebook`) Facebook via `facebook.com`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:44
+msgid "(`facebook-tor`) Facebook via `facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion` ([Tor](https://www.torproject.org/)) - does not currently proxy media downloads"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:45
+msgid "(default) (`messenger`) Messenger via `messenger.com` - usable even without a Facebook account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:47
+msgid "You may switch the mode via the `matrix_mautrix_meta_messenger_meta_mode` variable. The playbook defaults to the `messenger` mode, because it's most universal (every Facebook user has a Messenger account, but the opposite is not true)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:49
+msgid "Note that switching the mode (especially between `facebook*` and `messenger`) will intentionally make the bridge use another database (`matrix_mautrix_meta_facebook` or `matrix_mautrix_meta_messenger`) to isolate the 2 instances. Switching between Tor and non-Tor may be possible without dataloss, but your mileage may vary. Before switching to a new mode, you may wish to de-configure the old one (send `help` to the bridge bot and unbridge your portals, etc.)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:51
+msgid "Bridge permissions"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:53
+msgid "By default, any user on your homeserver will be able to use the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:55
+msgid "Different levels of permission can be granted to users:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:57
+msgid "`relay` - Allowed to be relayed through the bridge, no access to commands"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:58
+msgid "`user` - Use the bridge with puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:59
+msgid "`admin` - Use and administer the bridge"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:61
+msgid "The permissions are following the sequence: nothing < `relay` < `user` < `admin`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:63
+msgid "The default permissions are set via `matrix_mautrix_meta_messenger_bridge_permissions_default` and are somewhat like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:72
+msgid "If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:74
+msgid "You may redefine `matrix_mautrix_meta_messenger_bridge_permissions_default` any way you see fit, or add extra permissions using `matrix_mautrix_meta_messenger_bridge_permissions_custom` like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:81
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:83
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:85
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:92
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:94
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:96
+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-meta-messenger.md:98
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:100
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:102
+msgid "To use the bridge, you need to start a chat with `@messengerbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). Note that the user ID of the bridge's bot is not `@facebookbot:example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:104
+msgid "You then need to send a `login` command and follow the bridge bot's instructions."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:106
+msgid "Given that the bot is configured in `messenger` [bridge mode](#bridge-mode) by default, you will need to log in to [messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain the cookies from there as per [the bridge's authentication instructions](https://docs.mau.fi/bridges/go/meta/authentication.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:108
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:110
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:112
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:114
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:116
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:118
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:120
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:122
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:124
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:126
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:128
+msgid "make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po
new file mode 100644
index 000000000..990eefa26
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po
@@ -0,0 +1,198 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:1
+msgid "Setting up Mautrix Signal bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:3
+msgid "The playbook can install and configure [mautrix-signal](https://github.com/mautrix/signal) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:5
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/signal/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:7
+msgid "**Note**: This revamped version of the [mautrix-signal (legacy)](configuring-playbook-bridge-mautrix-signal.md) may increase the CPU usage of your homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:9
+msgid "Prerequisites (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:11
+msgid "Prepare Postgres database on external Postgres server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:13
+msgid "If you're running with the Postgres database server integrated by the playbook (which is the default), you don't need to do anything special and can easily proceed with installing."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:15
+msgid "However, if you're [using an external Postgres server](configuring-playbook-external-postgres.md), you'd need to manually prepare a Postgres database for this bridge and adjust the variables related to that (`matrix_mautrix_signal_database_*`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:17
+msgid "Enable Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:19
+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-signal.md:21
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:23
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:25
+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-signal.md:31
+msgid "There are some additional things you may wish to configure about the bridge before you continue."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:33
+msgid "By default, any user on your homeserver will be able to use the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:35
+msgid "Different levels of permission can be granted to users:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:37
+msgid "relay - Allowed to be relayed through the bridge, no access to commands;"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:38
+msgid "user - Use the bridge with puppeting;"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:39
+msgid "admin - Use and administer the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:41
+msgid "The permissions are following the sequence: nothing < relay < user < admin."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:43
+msgid "The default permissions are set as follows:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:51
+msgid "If you want to augment the preset permissions, you might want to set the additional permissions with the following settings in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:60
+msgid "This will add the admin permission to the specific user, while keeping the default permissions."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:62
+msgid "In case you want to replace the default permissions settings **completely**, populate the following item within your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:70
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-signal/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:72
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:74
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:81
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:83
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:85
+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-signal.md:87
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:89
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:91
+msgid "To use the bridge, you need to start a chat with `@signalbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:93
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:95
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:97
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:99
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:101
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:103
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:105
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:107
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:109
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:111
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:113
+msgid "make sure you don't log out the `Mautrix-Signal` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po
new file mode 100644
index 000000000..3de53dfe5
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po
@@ -0,0 +1,198 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:1
+msgid "Setting up Mautrix Slack bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:3
+msgid "**Note**: bridging to [Slack](https://slack.com/) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:4
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:5
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:7
+msgid "The playbook can install and configure [mautrix-slack](https://github.com/mautrix/slack) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:9
+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:11
+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:13
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:15
+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:17
+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:19
+msgid "Enable Appservice Double Puppet (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:21
+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:23
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:25
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:27
+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:33
+msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:35
+msgid "Additional configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:37
+msgid "There are some additional options you may wish to configure with the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:39
+msgid "Take a look at:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:41
+msgid "`roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:42
+msgid "`roles/custom/matrix-bridge-mautrix-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_mautrix_slack_configuration_extension_yaml` variable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:44
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:46
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:53
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:55
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:57
+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:59
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:61
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:63
+msgid "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:64
+msgid "If you would like to login to Slack using a token, send the `login-token` command, otherwise, send the `login-password` command. Read [here](https://docs.mau.fi/bridges/go/slack/authentication.html) on how to retrieve your token and cookie token."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:65
+msgid "The bot should respond with \"Successfully logged into <email> for team <workspace>\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:66
+msgid "Now that you're logged in, you can send `help` to the bot to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:67
+msgid "Slack channels should automatically begin bridging if you authenticated using a token. Otherwise, you must wait to receive a message in the channel if you used password authentication."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:69
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:71
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:73
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:75
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:77
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:79
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:81
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:83
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:85
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:87
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:89
+msgid "make sure you don't log out the `Mautrix-Slack` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po
new file mode 100644
index 000000000..5dbfc7b62
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po
@@ -0,0 +1,154 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:1
+msgid "Setting up Mautrix Telegram bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:3
+msgid "The playbook can install and configure [mautrix-telegram](https://github.com/mautrix/telegram) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:5
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/telegram/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:7
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:9
+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-telegram.md:11
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:15
+msgid "You'll need to obtain API keys from [https://my.telegram.org/apps](https://my.telegram.org/apps) and then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:23
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:25
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:32
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:34
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:36
+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-telegram.md:38
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:40
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:42
+msgid "To use the bridge, you need to start a chat with `@telegrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:44
+msgid "If you want to use the relay-bot feature ([relay bot documentation](https://docs.mau.fi/bridges/python/telegram/relay-bot.html)), which allows anonymous user to chat with telegram users, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:54
+msgid "You might also want to give permissions to administrate the bot:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:63
+msgid "More details about permissions in this example: https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-config.yaml#L410"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:65
+msgid "If you like to exclude all groups from syncing and use the Telgeram-Bridge only for direct chats, you can add the following additional playbook configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:71
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:73
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:75
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:77
+msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:79
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:81
+msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:83
+msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:85
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:87
+msgid "**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:89
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:91
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:93
+msgid "send `login-matrix` to the bot and follow instructions about how to send the access token to it"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:95
+msgid "make sure you don't log out the `Mautrix-Telegram` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po
new file mode 100644
index 000000000..403b09145
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po
@@ -0,0 +1,146 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:1
+msgid "Setting up Mautrix Twitter bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:3
+msgid "**Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md) bridge supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:5
+msgid "The playbook can install and configure [mautrix-twitter](https://github.com/mautrix/twitter) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:7
+msgid "See the project's [documentation](https://github.com/mautrix/twitter/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:9
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:11
+msgid "Enable Appservice Double Puppet (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:13
+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-twitter.md:15
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:17
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:19
+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-twitter.md:25
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:27
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:38
+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-twitter.md:40
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:42
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:44
+msgid "You then need to start a chat with `@twitterbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:45
+msgid "Send login-cookie to start the login. The bot should respond with instructions on how to proceed."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:47
+msgid "You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/twitter/authentication.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:49
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:51
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:53
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:55
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:57
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:59
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:61
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:63
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:65
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:67
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:69
+msgid "make sure you don't log out the `Mautrix-Slack` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po
new file mode 100644
index 000000000..15cd1e448
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po
@@ -0,0 +1,150 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:1
+msgid "Setting up Mautrix Whatsapp bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:3
+msgid "The playbook can install and configure [mautrix-whatsapp](https://github.com/mautrix/whatsapp) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:5
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/whatsapp/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:7
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:9
+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-whatsapp.md:11
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:15
+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-whatsapp.md:21
+msgid "Whatsapp multidevice beta is required, now it is enough if Whatsapp is connected to the Internet every 2 weeks."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:23
+msgid "The relay bot functionality is off by default. If you would like to enable the relay bot, add the following to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:29
+msgid "By default, only admins are allowed to set themselves as relay users. To allow anyone on your homeserver to set themselves as relay users add this to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:35
+msgid "If you want to activate the relay bot in a room, send `!wa set-relay`. To deactivate, send `!wa unset-relay`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:37
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:39
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:46
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:48
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:50
+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-whatsapp.md:52
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:54
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:56
+msgid "To use the bridge, you need to start a chat with `@whatsappbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:58
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:60
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:62
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:64
+msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:66
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:68
+msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:70
+msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:72
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:74
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:76
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:78
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:80
+msgid "make sure you don't log out the `Mautrix-Whatsapp` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po
new file mode 100644
index 000000000..840972572
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po
@@ -0,0 +1,106 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:1
+msgid "Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:3
+msgid "The playbook can install and configure [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:5
+msgid "See the project's [documentation](https://github.com/mautrix/wsproxy/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:9
+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-wsproxy.md:21
+msgid "Note that the tokens must match what is compiled into the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android device."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:23
+msgid "Adjusting the wsproxy URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:25
+msgid "By default, this playbook installs wsproxy on the `wsproxy.` subdomain (`wsproxy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:27
+msgid "By tweaking the `matrix_mautrix_wsproxy_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:29
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:36
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:38
+msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the wsproxy domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:40
+msgid "By default, you will need to create a CNAME record for `wsproxy`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:42
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:44
+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-bridge-mautrix-wsproxy.md:51
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:53
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.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-wsproxy.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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:59
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:61
+msgid "Follow the [matrix-imessage documenation](https://docs.mau.fi/bridges/go/imessage/index.html) for running `android-sms` and/or `matrix-imessage` on your device(s)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po
new file mode 100644
index 000000000..38262cd43
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po
@@ -0,0 +1,102 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:1
+msgid "Setting up MX Puppet Discord bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:3
+msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md)and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:4
+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-mx-puppet-discord.md:5
+msgid "For personal use with a discord account we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:7
+msgid "The playbook can install and configure [mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:9
+msgid "See the project's [documentation](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:13
+msgid "To enable the [Discord](https://discordapp.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:19
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:21
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:28
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:30
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:32
+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-mx-puppet-discord.md:34
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:36
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:38
+msgid "To use the bridge, you need to start a chat with `Discord Puppet Bridge` with the handle `@_discordpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:40
+msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-discord [documentation](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) for more information about how to configure the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:42
+msgid "Once logged in, send `list` to the bot user to list the available rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:44
+msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:46
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po
new file mode 100644
index 000000000..ad848ffcb
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po
@@ -0,0 +1,94 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:1
+msgid "Setting up MX Puppet GroupMe bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:3
+msgid "The playbook can install and configure [mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:5
+msgid "See the project's [documentation](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:9
+msgid "To enable the [GroupMe](https://groupme.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:15
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:17
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:24
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:26
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:28
+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-mx-puppet-groupme.md:30
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:32
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:34
+msgid "To use the bridge, you need to start a chat with `GroupMe Puppet Bridge` with the handle `@_groupmepuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:36
+msgid "One authentication method is available."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:38
+msgid "To link your GroupMe account, go to [dev.groupme.com](https://dev.groupme.com/), sign in, and select \"Access Token\" from the top menu. Copy the token and message the bridge with:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:44
+msgid "Once logged in, send `listrooms` to the bot user to list the available rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:46
+msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:48
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po
new file mode 100644
index 000000000..918c8fe79
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po
@@ -0,0 +1,106 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:1
+msgid "Setting up MX Puppet Instagram bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:3
+msgid "The playbook can install and configure [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:5
+msgid "This allows you to bridge Instagram DirectMessages into Matrix."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:9
+msgid "To enable the [Instagram](https://www.instagram.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:15
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:17
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:24
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:26
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:28
+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-mx-puppet-instagram.md:30
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:32
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:34
+msgid "To use the bridge, you need to start a chat with `Instagram Puppet Bridge` with the handle `@_instagrampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:36
+msgid "Send `link <username> <password>` to the bridge bot to link your instagram account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:38
+msgid "The `list` commands shows which accounts are linked and which `puppetId` is associated."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:40
+msgid "For double-puppeting, you probably want to issue these commands:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:42
+msgid "`settype $puppetId puppet` to enable puppeting for the link (instead of relaying)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:43
+msgid "`setautoinvite $puppetId 1` to automatically invite you to chats"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:44
+msgid "`setmatrixtoken $accessToken` to set the access token to enable puppeting from the other side (the \"double\" in double puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:46
+msgid "If you are linking only one Instagram account, your `$puppetId` is probably 1, but use the `list` command find out."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:48
+msgid "Send `help` to the bot to see the available commands. At the time of writing, not every command is fully implemented."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po
new file mode 100644
index 000000000..97456fc18
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po
@@ -0,0 +1,34 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:1
+msgid "Setting up MX Puppet Skype bridging (optional, removed)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:3
+msgid "The playbook used to be able to install and configure [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype), but no longer includes this component, because it has been broken and unmaintained for a long time."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:5
+msgid "Bridging to [Skype](https://www.skype.com/) can also happen via the [go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md) bridge supported by the playbook."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po
new file mode 100644
index 000000000..67ae99b1e
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po
@@ -0,0 +1,98 @@
+# Translations template for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\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"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:1
+msgid "Setting up MX Puppet Slack bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:3
+msgid "**Note**: bridging to [Slack](https://slack.com) can also happen via the [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook. Note that `matrix-appservice-slack` 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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:5
+msgid "The playbook can install and configure [mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:7
+msgid "See the project's [documentation](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:9
+msgid "Prerequisite"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:11
+msgid "Follow the [OAuth credentials](https://gitlab.com/mx-puppet/slack/mx-puppet-slack#option-2-oauth) instructions to create a new Slack app, setting the redirect URL to `https://matrix.example.com/slack/oauth`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:15
+msgid "To enable the [Slack](https://slack.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:24
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:26
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:33
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:35
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:37
+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-mx-puppet-slack.md:39
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:41
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:43
+msgid "To use the bridge, you need to start a chat with `Slack Puppet Bridge` with the handle `@_slackpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:45
+msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-slack [documentation](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for more information about how to configure the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:47
+msgid "Once logged in, send `list` to the bot user to list the available rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:49
+msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:51
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po
new file mode 100644
index 000000000..4ece71ba6
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po
@@ -0,0 +1,90 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:1
+msgid "Setting up MX Puppet Steam bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:3
+msgid "The playbook can install and configure [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:5
+msgid "See the project's [documentation](https://github.com/icewind1991/mx-puppet-steam/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:9
+msgid "To enable the [Steam](https://steampowered.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:15
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:17
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:24
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:26
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:28
+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-mx-puppet-steam.md:30
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:32
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:34
+msgid "To use the bridge, you need to start a chat with `Steam Puppet Bridge` with the handle `@_steampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:36
+msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-steam [documentation](https://github.com/icewind1991/mx-puppet-steam) for more information about how to configure the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:38
+msgid "Once logged in, send `list` to the bot user to list the available rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:40
+msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:42
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po
new file mode 100644
index 000000000..904abfeac
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po
@@ -0,0 +1,102 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:1
+msgid "Setting up MX Puppet Twitter bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:3
+msgid "**Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mautrix-twitter](configuring-playbook-bridge-mautrix-twitter.md) bridge supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:5
+msgid "The playbook can install and configure [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:7
+msgid "See the project's [documentation](https://github.com/Sorunome/mx-puppet-twitter/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:9
+msgid "Prerequisite"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:11
+msgid "Make an app on [developer.twitter.com](https://developer.twitter.com/en/apps)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:15
+msgid "To enable the [Twitter](https://twitter.com) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:26
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:28
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:35
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:37
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:39
+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-mx-puppet-twitter.md:41
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:43
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:45
+msgid "To use the bridge, you need to start a chat with `Twitter Puppet Bridge` with the handle `@_twitterpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:47
+msgid "To log in, use `link` and click the link."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:49
+msgid "Once logged in, send `list` to the bot user to list the available rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:51
+msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:53
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po
new file mode 100644
index 000000000..dceac0da9
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po
@@ -0,0 +1,138 @@
+# Translations template for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\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"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:1
+msgid "Setting up Postmoogle email bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:3
+msgid "**Note**: email bridging can also happen via the [email2matrix](configuring-playbook-email2matrix.md) bridge supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:5
+msgid "The playbook can install and configure [Postmoogle](https://github.com/etkecc/postmoogle) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:7
+msgid "Postmoogle is a bridge you can use to have its bot user forward emails to Matrix rooms. It runs an SMTP email server and allows you to assign mailbox addresses to the rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:9
+msgid "See the project's [documentation](https://github.com/etkecc/postmoogle/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:13
+msgid "Open the following ports on your server to be able to receive incoming emails:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:15
+msgid "`25/tcp`: SMTP"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:16
+msgid "`587/tcp`: Submission (TLS-encrypted SMTP)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:18
+msgid "If you don't open these ports, you will still be able to send emails, but not receive any."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:20
+msgid "These port numbers are configurable via the `matrix_postmoogle_smtp_host_bind_port` and `matrix_postmoogle_submission_host_bind_port` variables, but other email servers will try to deliver on these default (standard) ports, so changing them is of little use."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:22
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:24
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:45
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:47
+msgid "You will also need to add several DNS records so that Postmoogle can send emails. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:49
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:51
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:58
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:60
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create a user account of the bridge's bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:62
+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-postmoogle.md:64
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:66
+msgid "If you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:68
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:70
+msgid "To use the bridge, invite the `@postmoogle:example.com` bot user into a room you want to use as a mailbox."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:72
+msgid "Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with the email address `NAME@matrix.example.com`. Emails sent to that email address will be forwarded to the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:74
+msgid "Send `!pm help` to the bot in the room to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:76
+msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/postmoogle)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:78
+msgid "Debug/Logs"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:80
+msgid "As with all other services, you can find their logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-postmoogle`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:82
+msgid "The default logging level for this bridge is `INFO`, but you can increase it to `DEBUG` with the following additional configuration:"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po
new file mode 100644
index 000000000..8654f62a0
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po
@@ -0,0 +1,78 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:1
+msgid "Setting up WeChat bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:3
+msgid "The playbook can install and configure the [matrix-wechat](https://github.com/duo/matrix-wechat) bridge for you (for bridging to the [WeChat](https://www.wechat.com/) network)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:5
+msgid "See the project's [documentation](https://github.com/duo/matrix-wechat/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:9
+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-wechat.md:15
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:17
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:24
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:26
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:28
+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-wechat.md:30
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:32
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:34
+msgid "Once the bridge is installed, start a chat with `@wechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:36
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po
new file mode 100644
index 000000000..b28acaeed
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po
@@ -0,0 +1,170 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:1
+msgid "Setting up Cactus Comments (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:3
+msgid "The playbook can install and configure the [Cactus Comments](https://cactus.chat) system for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:5
+msgid "Cactus Comments is a **federated comment system** built on Matrix. It respects your privacy, and puts you in control."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:7
+msgid "See the project's [documentation](https://cactus.chat/docs/getting-started/introduction/) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:9
+msgid "The playbook contains 2 roles for configuring different pieces of the Cactus Comments system:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:11
+msgid "`matrix-cactus-comments` - the backend appservice integrating with the Matrix homeserver"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:13
+msgid "`matrix-cactus-comments-client` - a static website server serving the [cactus-client](https://cactus.chat/docs/client/introduction/) static assets (`cactus.js` and `styles.css`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:15
+msgid "You can enable whichever component you need (typically both)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:17
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:19
+msgid "To enable Cactus Comments, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:41
+msgid "Adjusting the Cactus Comments' client URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:43
+msgid "By default, this playbook installs Cactus Comments' client on the `matrix.` subdomain, at the `/cactus-comments` path (https://matrix.example.com/cactus-comments). 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-cactus-comments.md:45
+msgid "By tweaking the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_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-cactus-comments.md:47
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:56
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:58
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Cactus Comments' client domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:60
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:62
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:64
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:66
+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-cactus-comments.md:73
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:75
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:77
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:79
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:81
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:83
+msgid "Upon starting Cactus Comments, a `bot.cactusbot` user account is created automatically."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:85
+msgid "To get started, send `help` to the `@bot.cactusbot:example.com` bot to confirm it's working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:87
+msgid "Then, register a site by sending `register <YourSiteName>` (where `<YourSiteName>` is a unique identifier you choose. It does not have to match your domain). You will then be invited into a moderation room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:89
+msgid "Now you are good to go and can embed the comment section on your website!"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:91
+msgid "Embed Cactus Comments"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:93
+msgid "The official [documentation](https://cactus.chat/docs/getting-started/quick-start/) provides a useful guide to embed Cactus Comments on your website."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:95
+msgid "After including the JavaScript and CSS asset files, insert a `<div>` where you'd like to display the comment section:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:101
+msgid "Then, you need to initialize the comment section. Make sure to replace `example.com` with your base domain and `<YourSiteName>` with the one that has been registered above:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:115
+msgid "Adjust the domain name for self-hosting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:117
+msgid "To have the assets served from your homeserver (not from `cactus.chat`), you need to adjust the domain name on the official documentation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:119
+msgid "Make sure to replace `example.com` with your base domain before you include the following lines, instead of the one provided by the official documentation:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:126
+msgid "**Note**: if the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_path_prefix` variables are tweaked, you would need to adjust the URLs of the assets accordingly."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-cinny.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-cinny.po
new file mode 100644
index 000000000..b6f8f2750
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-cinny.po
@@ -0,0 +1,102 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-client-cinny.md:1
+msgid "Setting up Cinny (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:3
+msgid "This playbook can install the [Cinny](https://github.com/ajbura/cinny) Matrix web client for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:5
+msgid "Cinny 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)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:7
+msgid "💡 **Note**: the latest version of Cinny is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:9
+msgid "[app.cinny.in](https://app.cinny.in), hosted by the [Cinny](https://cinny.in/) developers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:13
+msgid "To enable Cinny, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:19
+msgid "Adjusting the Cinny URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:21
+msgid "By default, this playbook installs Cinny on the `cinny.` subdomain (`cinny.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:23
+msgid "By tweaking the `matrix_client_cinny_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:25
+msgid "While a `matrix_client_cinny_path_prefix` variable exists for tweaking the path-prefix, it's [not supported anymore](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Cinny requires an application rebuild (with a tweaked build config) to be functional under a custom path."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:27
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:34
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:36
+msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the Cinny domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:38
+msgid "By default, you will need to create a CNAME record for `cinny`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:40
+msgid "If you've adjusted `matrix_client_cinny_hostname`, you will need to adjust your DNS configuration accordingly."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:42
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:44
+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-cinny.md:51
+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-cinny.md:53
+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 ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-element-web.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-element-web.po
new file mode 100644
index 000000000..ab7f413bf
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-element-web.po
@@ -0,0 +1,150 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-client-element-web.md:1
+msgid "Configuring Element Web (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:3
+msgid "By default, this playbook installs the [Element Web](https://github.com/element-hq/element-web) Matrix client for you. If that's okay, you can skip this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:5
+msgid "💡 **Note**: the latest version of Element Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting (by [disabling Element Web](#disabling-element-web)):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:7
+msgid "[app.element.io](https://app.element.io/), hosted by [Element](https://element.io/)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:8
+msgid "[app.etke.cc](https://app.etke.cc/), hosted by [etke.cc](https://etke.cc/)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:10
+msgid "Disabling Element Web"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:12
+msgid "If you'd like for the playbook to not install Element Web (or to uninstall it if it was previously installed), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:18
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:20
+msgid "The playbook provides some customization variables you could use to change Element Web's settings."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:22
+msgid "Their defaults are defined in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml) and they ultimately end up in the generated `/matrix/element/config.json` file (on the server). This file is generated from the [`roles/custom/matrix-client-element/templates/config.json.j2`](../roles/custom/matrix-client-element/templates/config.json.j2) template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:24
+msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:26
+msgid "Alternatively, **if there is no pre-defined variable** for an Element Web setting you wish to change:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:28
+msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Element Web's various settings that rarely get used."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:30
+msgid "or, you can **extend and override the default configuration** ([`config.json.j2`](../roles/custom/matrix-client-element/templates/config.json.j2)) by making use of the `matrix_client_element_configuration_extension_json_` variable. You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:32
+msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_element_configuration_default` (or `matrix_client_element_configuration`). You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:34
+msgid "Themes"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:36
+msgid "To change the look of Element Web, you can define your own themes manually by using the `matrix_client_element_setting_defaults_custom_themes` setting."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:38
+msgid "Or better yet, you can automatically pull it all themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project by simply flipping a flag (`matrix_client_element_themes_enabled: true`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:40
+msgid "If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:42
+msgid "Note that for a custom theme to work well, all Element Web instances that you use must have the same theme installed."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:44
+msgid "Adjusting the Element Web URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:46
+msgid "By default, this playbook installs Element Web on the `element.` subdomain (`element.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:48
+msgid "By tweaking the `matrix_client_element_hostname` and `matrix_client_element_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-client-element-web.md:50
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:61
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:63
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Element Web domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:65
+msgid "By default, you will need to create a CNAME record for `element`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:67
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:69
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:71
+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-client-element-web.md:78
+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-element-web.md:80
+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 ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po
new file mode 100644
index 000000000..ad0c5b439
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po
@@ -0,0 +1,90 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:1
+msgid "Setting up Hydrogen (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:3
+msgid "This playbook can install the [Hydrogen](https://github.com/element-hq/hydrogen-web) Matrix web client for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:5
+msgid "Hydrogen is a lightweight web client that supports mobile and legacy web browsers. It can be installed alongside or instead of Element Web."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:9
+msgid "To enable Hydrogen, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:15
+msgid "Adjusting the Hydrogen URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:17
+msgid "By default, this playbook installs Hydrogen on the `hydrogen.` subdomain (`hydrogen.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:19
+msgid "By tweaking the `matrix_client_hydrogen_hostname` and `matrix_client_hydrogen_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-client-hydrogen.md:21
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:32
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:34
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Hydrogen domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:36
+msgid "By default, you will need to create a CNAME record for `hydrogen`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:38
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:40
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:42
+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-client-hydrogen.md:49
+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-hydrogen.md:51
+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 ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po
new file mode 100644
index 000000000..dfe68ae18
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po
@@ -0,0 +1,146 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:1
+msgid "Setting up SchildiChat Web (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:3
+msgid "This playbook can install the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) Matrix client for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:5
+msgid "SchildiChat Web is a feature-rich messenger for Matrix based on Element Web with some extras and tweaks. It can be installed alongside or instead of Element Web."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:7
+msgid "💡 **Note**: the latest version of SchildiChat Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Application, you can consider using it from there:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:9
+msgid "[app.schildi.chat](https://app.schildi.chat/), hosted by the [SchildiChat](https://schildi.chat/) developers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:13
+msgid "To enable SchildiChat Web, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:19
+msgid "The playbook provides some customization variables you could use to change SchildiChat Web's settings."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:21
+msgid "Their defaults are defined in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml) and they ultimately end up in the generated `/matrix/schildichat/config.json` file (on the server). This file is generated from the [`roles/custom/matrix-client-schildichat/templates/config.json.j2`](../roles/custom/matrix-client-schildichat/templates/config.json.j2) template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:23
+msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:25
+msgid "Alternatively, **if there is no pre-defined variable** for a SchildiChat Web setting you wish to change:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:27
+msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of SchildiChat Web's various settings that rarely get used."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:29
+msgid "or, you can **extend and override the default configuration** ([`config.json.j2`](../roles/custom/matrix-client-schildichat/templates/config.json.j2)) by making use of the `matrix_client_schildichat_configuration_extension_json_` variable. You can find information about this in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:31
+msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_schildichat_configuration_default` (or `matrix_client_schildichat_configuration`). You can find information about this in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:33
+msgid "Themes"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:35
+msgid "To change the look of SchildiChat Web, you can define your own themes manually by using the `matrix_client_schildichat_setting_defaults_custom_themes` setting."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:37
+msgid "Or better yet, you can automatically pull it all themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project by simply flipping a flag (`matrix_client_schildichat_themes_enabled: true`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:39
+msgid "If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:41
+msgid "Note that for a custom theme to work well, all SchildiChat Web instances that you use must have the same theme installed."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:43
+msgid "Adjusting the SchildiChat Web URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:45
+msgid "By default, this playbook installs SchildiChat Web on the `schildichat.` subdomain (`schildichat.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:47
+msgid "By tweaking the `matrix_client_schildichat_hostname` and `matrix_client_schildichat_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-client-schildichat-web.md:49
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:60
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:62
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the SchildiChat Web domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:64
+msgid "By default, you will need to create a CNAME record for `schildichat`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:66
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:68
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:70
+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-client-schildichat-web.md:77
+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-schildichat-web.md:79
+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 ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduit.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduit.po
new file mode 100644
index 000000000..5142b6b0c
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-conduit.po
@@ -0,0 +1,98 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-conduit.md:1
+msgid "Configuring Conduit (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:3
+msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Conduit](https://conduit.rs)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:5
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:7
+msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:9
+msgid "**homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:13
+msgid "To use Conduit, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:19
+msgid "Creating the first user account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:21
+msgid "Since it is difficult to create the first user account on Conduit (see [famedly/conduit#276](https://gitlab.com/famedly/conduit/-/issues/276) and [famedly/conduit#354](https://gitlab.com/famedly/conduit/-/merge_requests/354)) and it does not support [registering users](registering-users.md) (via the command line or via the playbook) like Synapse and Dendrite do, we recommend the following procedure:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:23
+msgid "Add `matrix_conduit_allow_registration: true` to your `vars.yml` the first time around, temporarily"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:24
+msgid "Run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start` - see [Installing](installing.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:25
+msgid "Create your first user via Element Web or any other client which supports creating users"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:26
+msgid "Get rid of `matrix_conduit_allow_registration: true` from your `vars.yml`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:27
+msgid "Run the playbook again (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-conduit,start` would be enough this time)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:28
+msgid "You can now use your server safely. Additional users can be created by messaging the internal Conduit bot"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:30
+msgid "Configuring bridges / appservices"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:32
+msgid "Automatic appservice setup is currently unsupported when using Conduit. After setting up the service as usual you may notice that it is unable to start."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:34
+msgid "You will have to manually register appservices using the the [register-appservice](https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.md) command."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:36
+msgid "Find the `registration.yaml` in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`, then pass the content to Conduit:"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dendrite.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dendrite.po
new file mode 100644
index 000000000..35c0c5383
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dendrite.po
@@ -0,0 +1,94 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-dendrite.md:1
+msgid "Configuring Dendrite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:3
+msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Dendrite](https://github.com/matrix-org/dendrite)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:5
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:7
+msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Dendrite). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:9
+msgid "**homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:13
+msgid "To use Dendrite, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:19
+msgid "The playbook provides lots of customization variables you could use to change Dendrite's settings."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:21
+msgid "Their defaults are defined in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml) and they ultimately end up in the generated `/matrix/dendrite/config/dendrite.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2) template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:23
+msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:25
+msgid "Alternatively, **if there is no pre-defined variable** for a Dendrite setting you wish to change:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:27
+msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Dendrite's various settings that rarely get used."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:29
+msgid "or, you can **extend and override the default configuration** ([`dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2)) by making use of the `matrix_dendrite_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:31
+msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_dendrite_configuration` (or `matrix_dendrite_configuration_yaml`). You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:33
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:35
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:42
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:44
+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 ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dimension.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dimension.po
new file mode 100644
index 000000000..6bc7248aa
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dimension.po
@@ -0,0 +1,183 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-dimension.md:1
+msgid "Setting up Dimension integration manager (optional, unmaintained)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:3
+#: ../../../docs/configuring-playbook-dimension.md:91
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:4
+msgid "Dimension is **[officially unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299)**. We recommend not bothering with installing it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:5
+msgid "This playbook now supports running Dimension in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`. Enabling Dimension, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:7
+msgid "The playbook can install and configure the [Dimension](https://dimension.t2bot.io) integration manager for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:9
+msgid "See the project's [documentation](https://github.com/turt2live/matrix-dimension/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:13
+msgid "Install Matrix services"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:15
+msgid "Dimension can only be installed after Matrix services are installed and running. If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) and come back here later."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:17
+msgid "Register a dedicated Matrix user (optional, recommended)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:19
+msgid "We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:21
+msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:23
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:29
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:31
+msgid "Dimension requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:33
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:35
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:37
+msgid "To enable Dimension, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`). Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:45
+msgid "Define admin users"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:47
+msgid "These users can modify the integrations this Dimension supports. Add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:55
+msgid "The admin interface is accessible within Element Web by accessing it in any room and clicking the cog wheel/settings icon in the top right. Currently, Dimension can be opened in Element Web by the \"Add widgets, bridges, & bots\" link in the room information."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:57
+msgid "Adjusting the Dimension URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:59
+msgid "By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:61
+msgid "By tweaking the `matrix_dimension_hostname` and `matrix_dimension_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-dimension.md:63
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:74
+msgid "**Note**: While there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You must serve Dimension at a dedicated subdomain."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:76
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:78
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:80
+msgid "By default, you will need to create a CNAME record for `dimension`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:82
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:84
+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-dimension.md:93
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:95
+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-dimension.md:97
+msgid "After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:99
+msgid "Jitsi domain"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:101
+msgid "By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](./configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance. Currently there is no way to configure this via the playbook, see [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:103
+msgid "In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element Web, go to *Manage Integrations* &rightarrow; *Settings* &rightarrow; *Widgets* &rightarrow; *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:105
+msgid "Additional features"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:107
+msgid "To use a more custom configuration, you can define a `matrix_dimension_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_dimension_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-dimension/defaults/main.yml) of the Dimension component."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:109
+msgid "You can find all configuration options on [GitHub page of Dimension project](https://github.com/turt2live/matrix-dimension/blob/master/config/default.yaml)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po
new file mode 100644
index 000000000..e37cf2462
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po
@@ -0,0 +1,78 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:1
+msgid "Setting up Dynamic DNS (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:3
+msgid "The playbook can configure Dynamic DNS with [ddclient⁠](https://github.com/ddclient/ddclient) for you. It is a Perl client used to update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:5
+msgid "Most cloud providers / ISPs will charge you extra for a static IP address. If you're not hosting a highly reliable homeserver you can workaround this via dynamic DNS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:7
+msgid "Prerequisite"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:9
+msgid "You'll need to get a username and password from your DNS provider. Please consult with the provider about how to retrieve them."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:13
+msgid "To enable dynamic DNS, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:26
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:28
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:35
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:37
+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-dynamic-dns.md:39
+msgid "Additional Reading"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:41
+msgid "Additional resources:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:43
+msgid "https://matrix.org/docs/guides/free-small-matrix-server"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email.po
new file mode 100644
index 000000000..d6bc0411f
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email.po
@@ -0,0 +1,90 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-email.md:1
+msgid "Adjusting email-sending settings (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:3
+msgid "By default, this playbook sets up an [Exim](https://www.exim.org/) email server through which all Matrix services send emails."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:5
+msgid "The email server would attempt to deliver emails directly to their final destination. This may or may not work, depending on your domain configuration (SPF settings, etc.)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:7
+msgid "By default, emails are sent from `matrix@matrix.example.com`, as specified by the `exim_relay_sender_address` playbook variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:9
+msgid "⚠️ **Warning**: On some cloud providers (Google Cloud, etc.), [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible. You will need to [relay email through another SMTP server](#relaying-email-through-another-smtp-server)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:11
+msgid "💡 To improve deliverability, we recommend [relaying email through another SMTP server](#relaying-email-through-another-smtp-server) anyway."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:13
+msgid "Firewall settings"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:15
+msgid "No matter whether you send email directly (the default) or you relay email through another host (see how below), you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:17
+msgid "Relaying email through another SMTP server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:19
+msgid "If you'd like to relay email through another SMTP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:31
+msgid "**Note**: only the secure submission protocol (using `STARTTLS`, usually on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port `465`) **is not supported**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:33
+msgid "Configuations for sending emails using Sendgrid"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:35
+msgid "An easy and free SMTP service to set up is [Sendgrid](https://sendgrid.com/), the free tier allows for up to 100 emails per day to be sent. In the settings below you can provide any email for `exim_relay_sender_address`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:37
+msgid "The only other thing you need to change is the `exim_relay_relay_auth_password`, which you can generate at https://app.sendgrid.com/settings/api_keys. The API key password looks something like `SG.955oW1mLSfwds7i9Yd6IA5Q.q8GTaB8q9kGDzasegdG6u95fQ-6zkdwrPP8bOeuI`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:39
+msgid "Note that the `exim_relay_relay_auth_username` is literally the string `apikey`, it's always the same for Sendgrid."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:51
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:53
+msgid "If you're having trouble with email not being delivered, it may be useful to inspect the mailer logs: `journalctl -f -u matrix-exim-relay`."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po
new file mode 100644
index 000000000..aa97b41e9
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-email2matrix.po
@@ -0,0 +1,198 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-email2matrix.md:1
+msgid "Setting up Email2Matrix (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:3
+msgid "**Note**: email bridging can also happen via the [Postmoogle](configuring-playbook-bridge-postmoogle.md) bridge supported by the playbook. Postmoogle is much more powerful and easier to use, so we recommend that you use it, instead of Email2Matrix."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:5
+msgid "The playbook can install and configure [email2matrix](https://github.com/devture/email2matrix) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:7
+msgid "See the project's [documentation](https://github.com/devture/email2matrix/blob/master/docs/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:9
+msgid "Preparation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:11
+msgid "DNS configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:13
+msgid "It's not strictly necessary, but you may increase the chances that incoming emails reach your server by adding an `MX` record for `matrix.example.com`, as described in the [Configuring DNS](configuring-dns.md) documentation page."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:15
+msgid "Port availability"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:17
+msgid "Ensure that port 25 is available on your Matrix server and open in your firewall."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:19
+msgid "If you have `postfix` or some other email server software installed, you may need to manually remove it first (unless you need it, of course)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:21
+msgid "If you really need to run an email server on the Matrix machine for other purposes, it may be possible to run Email2Matrix on another port (with a configuration like `matrix_email2matrix_smtp_host_bind_port: \"127.0.0.01:2525\"`) and have your other email server relay messages there."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:23
+msgid "For details about using Email2Matrix alongside [Postfix](http://www.postfix.org/), see [here](https://github.com/devture/email2matrix/blob/master/docs/setup_with_postfix.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:25
+msgid "Register a dedicated Matrix user (optional, recommended)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:27
+msgid "We recommend that you create a dedicated Matrix user for Email2Matrix."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:29
+msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:31
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:37
+msgid "Take note of the user's ID as it needs to be specified as `MatrixUserId` on your `inventory/host_vars/matrix.example.com/vars.yml` file later."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:39
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:41
+msgid "Email2Matrix requires an access token for the sender user to be able to send messages to the room. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:43
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:45
+msgid "Join to rooms as the sender user manually"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:47
+msgid "ℹ️ **Email2Matrix does not accept room invitations automatically**. To deliver messages to rooms, the sender user must be joined to all rooms manually."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:49
+msgid "For each new room you would like the user to deliver messages to, invite the user to the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:51
+msgid "Then, log in as the sender user using any Matrix client of your choosing, accept the room invitation from the user's account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:53
+msgid "Make sure that you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there, then log out."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:55
+msgid "Take note of each room's room ID (different clients show the room ID in a different place). You'll need the room ID when [configuring the playbook](#adjusting-the-playbook-configuration) below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:57
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:59
+msgid "To enable Email2Matrix, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE` and `ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE` with the ones created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:85
+msgid "where:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:87
+msgid "MailboxName - local-part of the email address, through which emails are bridged to the room whose ID is defined with MatrixRoomId"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:88
+msgid "MatrixRoomId - internal ID of the room, to which received emails are sent as Matrix message"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:89
+msgid "MatrixHomeserverUrl - URL of your Matrix homeserver, through which to send Matrix messages. You can also set `MatrixHomeserverUrl` to the container URL where your homeserver's Client-Server API lives by using the `{{ matrix_addons_homeserver_client_api_url }}` variable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:90
+msgid "MatrixUserId - the full ID of the sender user which sends bridged messages to the room. On this configuration it is `@email2matrix1:example.com` and `@email2matrix2:example.com` (where `example.com` is your base domain, not the `matrix.` domain)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:91
+msgid "MatrixAccessToken - sender user's access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:92
+msgid "IgnoreSubject - if set to \"true\", the subject is not bridged to Matrix"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:93
+msgid "IgnoreBody - if set to \"true\", the message body is not bridged to Matrix"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:94
+msgid "SkipMarkdown - if set to \"true\", emails are bridged as plain text Matrix message instead of Markdown (actually HTML)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:96
+msgid "Refer to the official documentation [here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:98
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:100
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:107
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:109
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service email2matrix` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:111
+msgid "`just install-service email2matrix` is useful for maintaining your setup quickly 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 `just setup-all` runs the `ensure-matrix-users-created` tag too."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:113
+msgid "After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-etherpad.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-etherpad.po
new file mode 100644
index 000000000..8c8626914
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-etherpad.po
@@ -0,0 +1,174 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-etherpad.md:1
+msgid "Setting up Etherpad (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:3
+msgid "[Etherpad](https://etherpad.org) is an open source collaborative text editor that can be embedded in a Matrix chat room using the [Dimension integration manager](https://dimension.t2bot.io) or used as standalone web app."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:5
+msgid "When enabled together with the Jitsi audio/video conferencing system (see [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made available as an option during the conferences."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:9
+msgid "To enable Etherpad, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:19
+msgid "Adjusting the Etherpad URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:21
+msgid "By default, this playbook installs Etherpad on the `etherpad.` subdomain (`etherpad.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:23
+msgid "By tweaking the `etherpad_hostname` and `etherpad_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-etherpad.md:25
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:36
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:38
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Etherpad domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:40
+msgid "By default, you will need to create a CNAME record for `etherpad`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:42
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:44
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:46
+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-etherpad.md:53
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:55
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the Etherpad admin user (`etherpad_admin_username`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:57
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:59
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:61
+msgid "If you change the Etherpad admin user's password (`etherpad_admin_password` in your `vars.yml` file) subsequently, the admin user's credentials on the homeserver won't be updated automatically. If you'd like to change the admin user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `etherpad_admin_password` to let the admin user know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:63
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:65
+msgid "The Etherpad UI should be available at `https://etherpad.example.com`, while the admin UI (if enabled) should then be available at `https://etherpad.example.com/admin`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:67
+msgid "If you've [decided on another hostname or path-prefix](#adjusting-the-etherpad-url) (e.g. `https://matrix.example.com/etherpad`), adjust these URLs accordingly before usage."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:69
+msgid "Managing / Deleting old pads"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:71
+msgid "If you want to manage and remove old unused pads from Etherpad, you will first need to able Admin access as described above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:73
+msgid "Then from the plugin manager page (`https://etherpad.example.com/admin/plugins`, install the `adminpads2` plugin. Once installed, you should have a \"Manage pads\" section in the Admin web-UI."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:75
+msgid "How to use Etherpad widgets without an integration manager (like Dimension)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:77
+msgid "This is how it works in Element Web, it might work quite similar with other clients:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:79
+msgid "To integrate a standalone Etherpad in a room, create your pad by visiting `https://etherpad.example.com`. When the pad opens, copy the URL and send a command like this to the room: `/addwidget URL`. You will then find your integrated Etherpad within the right sidebar in the `Widgets` section."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:81
+msgid "Set Dimension default to the self-hosted Etherpad (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:83
+msgid "If you decided to install [Dimension integration manager](configuring-playbook-dimension.md) alongside Etherpad, the Dimension administrator users can configure the default URL template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:85
+msgid "The Dimension configuration menu can be accessed with the sprocket icon as you begin to add a widget to a room in Element Web. There you will find the Etherpad Widget Configuration action beneath the _Widgets_ tab."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:87
+msgid "Removing the integrated Etherpad chat"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:89
+msgid "If you wish to disable the Etherpad chat button, you can do it by appending `?showChat=false` to the end of the pad URL, or the template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:91
+msgid "Example: `https://etherpad.example.com/p/$roomId_$padName?showChat=false`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:93
+msgid "Known issues"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:95
+msgid "If your Etherpad widget fails to load, this might be due to Dimension generating a Pad name so long, the Etherpad app rejects it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:97
+msgid "`$roomId_$padName` can end up being longer than 50 characters. You can avoid having this problem by altering the template so it only contains the three word random identifier `$padName`."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-external-postgres.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-external-postgres.po
new file mode 100644
index 000000000..f0f9f2c1e
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-external-postgres.po
@@ -0,0 +1,46 @@
+# Translations template for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\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"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-external-postgres.md:1
+msgid "Using an external PostgreSQL server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:3
+msgid "By default, this playbook would set up a PostgreSQL database server on your machine, running in a Docker container. If that's okay, you can skip this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:5
+msgid "**Note**: using **an external Postgres server is currently [not very seamless](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1682#issuecomment-1061461683) when it comes to enabling various other playbook services** - you will need to create a new database/credentials for each service and to point each service to its corresponding database using custom `vars.yml` configuration. **For the best experience with the playbook, stick to using the integrated Postgres server**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:7
+msgid "If you'd like to use an external Postgres server that you manage, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:23
+msgid "The database (as specified in `matrix_synapse_database_database`) must exist and be accessible with the given credentials. It must be empty or contain a valid Synapse database. If empty, Synapse would populate it the first time it runs."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:25
+msgid "**Note**: the external server that you specify in `matrix_synapse_database_host` must be accessible from within the `matrix-synapse` Docker container (and possibly other containers too). This means that it either needs to be a publicly accessible hostname or that it's a hostname on the same Docker network where all containers installed by this playbook run (a network called `matrix` by default). Using a local PostgreSQL instance on the host (running on the same machine, but not in a container) is not possible."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:27
+msgid "The connection to your external Postgres server **will not be SSL encrypted**, as [we don't support that yet](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/89)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-federation.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-federation.po
new file mode 100644
index 000000000..ca5aac059
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-federation.po
@@ -0,0 +1,90 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-federation.md:1
+msgid "Controlling Matrix federation (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:3
+msgid "By default, your server federates with the whole Matrix network. That is, people on your server can communicate with people on any other Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:5
+msgid "**Note**: in the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com` and set up [server delegation](howto-server-delegation.md) / redirection. Without a proper configuration, your server will effectively not be part of the Matrix network. If you find your server is not federated, make sure to [check whether services work](maintenance-checking-services.md) and your server is properly delegated."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:7
+msgid "Federating only with select servers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:9
+msgid "To make your server only federate with servers of your choosing, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:17
+msgid "If you wish to disable federation, you can do that with an empty list (`[]`), or better yet by completely disabling federation (see below)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:19
+msgid "Exposing the room directory over federation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:21
+msgid "By default, your server's public rooms directory is not exposed to other servers via federation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:23
+msgid "If you wish to expose it, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:29
+msgid "Disabling federation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:31
+msgid "To completely disable federation, isolating your server from the rest of the Matrix network, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:37
+msgid "With that, your server's users will only be able to talk among themselves, but not to anyone who is on another server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:39
+msgid "**Disabling federation does not necessarily disable the federation port** (`8448`). Services like [Dimension](configuring-playbook-dimension.md) and [ma1sd](configuring-playbook-ma1sd.md) normally rely on `openid` APIs exposed on that port. Even if you disable federation and only if necessary, we may still be exposing the federation port and serving the `openid` APIs there. To override this and completely disable Synapse's federation port use:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:51
+msgid "Changing the federation port from 8448 to a different port to use a CDN that only accepts 443/80 ports"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:53
+msgid "Why? This change could be useful for people running small Synapse instances on small severs/VPSes to avoid being impacted by a simple DOS/DDOS when bandwidth, RAM, an CPU resources are limited and if your hosting provider does not provide a DOS/DDOS protection."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:55
+msgid "The following changes in the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) will allow this and make it possible to proxy the federation through a CDN such as CloudFlare or any other:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:66
+msgid "**Use this at you own risk as all the possible side-effects of doing this are not fully known. However, it has been tested and works fine and passes all the tests on <https://federationtester.matrix.org/> without issues.**"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jitsi.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jitsi.po
new file mode 100644
index 000000000..05f28ca05
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-jitsi.po
@@ -0,0 +1,366 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-jitsi.md:1
+msgid "Setting up the Jitsi video-conferencing platform (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:3
+msgid "The playbook can install the [Jitsi](https://jitsi.org/) video-conferencing platform and integrate it with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:5
+msgid "Jitsi installation is **not enabled by default**, because it's not a core component of Matrix services."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:7
+msgid "The setup done by the playbook is very similar to [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the documentation there for many of the options here."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:11
+msgid "You may need to open the following ports to your server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:13
+msgid "`4443/tcp` - RTP media fallback over TCP"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:14
+msgid "`10000/udp` - RTP media over UDP. Depending on your firewall/NAT setup, incoming RTP packets on port `10000` may have the external IP of your firewall as destination address, due to the usage of STUN in JVB (see [`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/defaults/main.yml))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:16
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:18
+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:24
+msgid "Adjusting the Jitsi URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:26
+msgid "By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:28
+msgid "By tweaking the `jitsi_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:30
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:37
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:39
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Jitsi domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:41
+msgid "By default, you will need to create a CNAME record for `jitsi`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:43
+msgid "Configure Jitsi authentication and guests mode (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:45
+msgid "By default the Jitsi Meet instance does not require any kind of login and is open to use for anyone without registration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:47
+msgid "If you're fine with such an open Jitsi instance, please skip to [Installing](#installing)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:49
+msgid "If you would like to control who is allowed to open meetings on your new Jitsi instance, then please follow the following steps to enable Jitsi's authentication and optionally guests mode."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:51
+msgid "Currently, there are three supported authentication modes: 'internal' (default), 'matrix' and 'ldap'."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:53
+msgid "**Note**: Authentication is not tested via the playbook's self-checks. We therefore recommend that you manually verify if authentication is required by jitsi. For this, try to manually create a conference on jitsi.example.com in your browser."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:55
+msgid "Authenticate using Jitsi accounts (Auth-Type 'internal')"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:57
+msgid "The default authentication mechanism is 'internal' auth, which requires jitsi-accounts to be setup and is the recommended setup, as it also works in federated rooms. With authentication enabled, all meeting rooms have to be opened by a registered user, after which guests are free to join. If a registered host is not yet present, guests are put on hold in individual waiting rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:59
+msgid "Add these lines to your `inventory/host_vars/matrix.example.com/vars.yml` configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:71
+msgid "**Caution**: Accounts added here and subsequently removed will not be automatically removed from the Prosody server until user account cleaning is integrated into the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:73
+msgid "**If you get an error** like this: \"Error: Account creation/modification not supported.\", it's likely that you had previously installed Jitsi without auth/guest support. In such a case, you should look into [Rebuilding your Jitsi installation](#rebuilding-your-jitsi-installation)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:75
+msgid "Authenticate using Matrix OpenID (Auth-Type 'matrix')"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:77
+msgid "**Attention: Probably breaks Jitsi in federated rooms and does not allow sharing conference links with guests.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:79
+msgid "Using this authentication type require a [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service). By default, this playbook creates and configures a user-verification-service to run locally, see [configuring-user-verification-service](configuring-playbook-user-verification-service.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:81
+msgid "To enable set this configuration at host level:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:89
+msgid "For more information see also [https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification](https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:91
+msgid "Authenticate using LDAP (Auth-Type 'ldap')"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:93
+msgid "An example LDAP configuration could be:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:113
+msgid "For more information refer to the [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:115
+msgid "Making your Jitsi server work on a LAN (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:117
+msgid "By default the Jitsi Meet instance does not work with a client in LAN (Local Area Network), even if others are connected from WAN. There are no video and audio. In the case of WAN to WAN everything is ok."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:119
+msgid "The reason is the Jitsi VideoBridge git to LAN client the IP address of the docker image instead of the host. The [documentation](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/#running-behind-nat-or-on-a-lan-environment) of Jitsi in docker suggest to add `JVB_ADVERTISE_IPS` in enviornment variable to make it work."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:121
+msgid "Here is how to do it in the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:123
+msgid "Add these two lines to your `inventory/host_vars/matrix.example.com/vars.yml` configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:130
+msgid "Fine tune Jitsi (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:132
+msgid "Sample **additional** `inventory/host_vars/matrix.example.com/vars.yml` configuration to save up resources (explained below):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:147
+msgid "You may want to **suspend unused video layers** until they are requested again, to save up resources on both server and clients. Read more on this feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-feature/)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:149
+msgid "You may wish to **disable audio levels** to avoid excessive refresh of the client-side page and decrease the CPU consumption involved."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:151
+msgid "You may want to **limit the number of video feeds forwarded to each client**, to save up resources on both server and clients. As clients’ bandwidth and CPU may not bear the load, use this setting to avoid lag and crashes. This feature is found by default in other webconference applications such as Office 365 Teams (limit is set to 4). Read how it works [here](https://github.com/jitsi/jitsi-videobridge/blob/master/doc/last-n.md) and performance evaluation on this [study](https://jitsi.org/wp-content/uploads/2016/12/nossdav2015lastn.pdf)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:153
+msgid "You may want to **limit the maximum video resolution**, to save up resources on both server and clients."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:155
+msgid "Specify a Max number of participants on a Jitsi conference (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:157
+msgid "The playbook allows a user to set a max number of participants allowed to join a Jitsi conference. By default there is no limit."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:159
+msgid "In order to set the max number of participants use the following **additional** configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:165
+msgid "Additional JVBs (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:167
+msgid "By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)) is deployed on the same host as the Matrix server. To allow more video-conferences to happen at the same time, you may need to provision additional JVB services on other hosts."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:169
+msgid "There is an ansible playbook that can be run with the following tag: `ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:171
+msgid "For this role to work you will need an additional section in the ansible hosts file with the details of the JVB hosts, for example:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:178
+msgid "Each JVB will require a server ID to be set so that it can be uniquely identified and this allows Jitsi to keep track of which conferences are on which JVB. The server ID is set with the variable `jitsi_jvb_server_id` which ends up as the JVB_WS_SERVER_ID environment variables in the JVB docker container. This variable can be set via the host file, a parameter to the ansible command or in the `vars.yaml` for the host which will have the additional JVB. For example:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:190
+msgid "Note that the server ID `jvb-1` is reserved for the JVB instance running on the Matrix host and therefore should not be used as the ID of an additional jvb host."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:192
+msgid "The additional JVB will also need to expose the colibri web socket port and this can be done with the following variable:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:198
+msgid "The JVB will also need to know where the prosody xmpp server is located, similar to the server ID this can be set in the vars for the JVB by using the variable `jitsi_xmpp_server`. The Jitsi prosody container is deployed on the Matrix server by default so the value can be set to the Matrix domain. For example:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:204
+msgid "However, it can also be set the ip address of the Matrix server. This can be useful if you wish to use a private ip. For example:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:210
+msgid "For the JVB to be able to contact the XMPP server, the latter must expose the XMPP port (5222). By default, the Matrix server does not expose the port; only the XMPP container exposes it internally inside the host, which means that the first JVB (which runs on the Matrix server) can reach it but the additional JVB cannot. The port is exposed by setting `jitsi_prosody_container_jvb_host_bind_port` like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:216
+msgid "(The default is empty; if it's set then docker forwards the port.)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:218
+msgid "Applied together this will allow you to provision extra JVB instances which will register themselves with the prosody service and be available for jicofo to route conferences too."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:220
+msgid "To make Traefik reverse-proxy to these additional JVBs (living on other hosts), **you would need to add the following Traefik configuration extension**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:256
+msgid "Enable Gravatar (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:258
+msgid "In the default Jisti Meet configuration, gravatar.com is enabled as an avatar service. This results in third party request leaking data to gravatar. Since Element clients already send the url of configured Matrix avatars to Jitsi, we disabled gravatar."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:260
+msgid "To enable Gravatar set:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:266
+msgid "**Beware**: This leaks information to a third party, namely the Gravatar-Service (unless configured otherwise: gravatar.com). Besides metadata, this includes the Matrix user_id and possibly the room identifier (via `referrer` header)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:268
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:270
+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:277
+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:279
+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:281
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:283
+msgid "You can use the self-hosted Jitsi server in multiple ways:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:285
+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:287
+msgid "**by adding a widget to a room via the Dimension integration manager**. You'll have to point the widget to your own Jitsi server manually. See our [Dimension integration manager](./configuring-playbook-dimension.md) documentation page for more details. Naturally, Dimension would need to be installed first (the playbook doesn't install it by default)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:289
+msgid "**directly (without any Matrix integration)**. Just go to `https://jitsi.example.com`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:291
+msgid "**Note**: Element apps on mobile devices currently [don't support joining meetings on a self-hosted Jitsi server](https://github.com/element-hq/riot-web/blob/601816862f7d84ac47547891bd53effa73d32957/docs/jitsi.md#mobile-app-support)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:293
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:295
+msgid "Rebuilding your Jitsi installation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:297
+msgid "**If you ever run into any trouble** or **if you change configuration (`jitsi_*` variables) too much**, we urge you to rebuild your Jitsi setup."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:299
+msgid "We normally don't require such manual intervention for other services, but Jitsi services generate a lot of configuration files on their own."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:301
+msgid "These files are not all managed by Ansible (at least not yet), so you may sometimes need to delete them all and start fresh."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:303
+msgid "To rebuild your Jitsi configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:305
+msgid "ask Ansible to stop all Jitsi services: `just run-tags stop-group --extra-vars=group=jitsi`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:306
+msgid "SSH into the server and do this and remove all Jitsi configuration & data (`rm -rf /matrix/jitsi`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:307
+msgid "ask Ansible to set up Jitsi anew and restart services (`just install-service jitsi`)"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po
new file mode 100644
index 000000000..bcbd4040f
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po
@@ -0,0 +1,62 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:1
+msgid "Setting up the LDAP authentication password provider module (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:3
+msgid "The playbook can install and configure the [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) LDAP Auth password provider for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:5
+msgid "See the project's [documentation](https://github.com/matrix-org/matrix-synapse-ldap3/blob/main/README.rst) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:7
+msgid "If you decide that you'd like to let this playbook install it for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:24
+msgid "Authenticating only using a password provider"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:26
+msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:32
+msgid "Using ma1sd Identity Server for authentication"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:34
+msgid "If you wish to use the ma1sd Identity Server for LDAP authentication instead of [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) consult [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md#authentication)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:36
+msgid "Handling user registration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:38
+msgid "If you wish for users to also be able to make new registrations against LDAP, you may **also** wish to [set up the ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ma1sd.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ma1sd.po
new file mode 100644
index 000000000..16c0ce771
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ma1sd.po
@@ -0,0 +1,214 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-ma1sd.md:1
+msgid "Setting up ma1sd Identity Server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:3
+msgid "**⚠️Note**: ma1sd itself has also been unmaintained for years (the latest commit and release being from 2021). The role of identity servers in the Matrix specification also has an uncertain future. **We recommend not bothering with installing it unless it's the only way you can do what you need to do**. For example, certain things like LDAP integration can also be implemented via [the LDAP provider module for Synapse](./configuring-playbook-ldap-auth.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:5
+msgid "The playbook can configure the [ma1sd](https://github.com/ma1uta/ma1sd) Identity Server for you. It is a fork of [mxisd](https://github.com/kamax-io/mxisd) which was pronounced end of life 2019-06-21."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:7
+msgid "ma1sd is used for 3PIDs (3rd party identifiers like E-mail and phone numbers) and some [enhanced features](https://github.com/ma1uta/ma1sd/#features). It is private by default, potentially at the expense of user discoverability."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:9
+msgid "See the project's [documentation](https://github.com/ma1uta/ma1sd/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:11
+msgid "**Note**: enabling ma1sd, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:13
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:15
+msgid "To make the ma1sd Identity Server enable its federation features, set up a SRV record that looks like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:17
+msgid "Name: `_matrix-identity._tcp` (use this text as-is)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:18
+msgid "Content: `10 0 443 matrix.example.com` (replace `example.com` with your own)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:20
+msgid "See [ma1sd's documentation](https://github.com/ma1uta/ma1sd/wiki/mxisd-and-your-privacy#choices-are-never-easy) for information on the privacy implications of setting up this SRV record."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:22
+msgid "**Note**: This `_matrix-identity._tcp` SRV record for the identity server is different from the `_matrix._tcp` that can be used for Synapse delegation. See [howto-server-delegation.md](howto-server-delegation.md) for more information about delegation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:24
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:26
+msgid "To enable ma1sd, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:32
+msgid "Matrix.org lookup forwarding"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:34
+msgid "To ensure maximum discovery, you can make your identity server also forward lookups to the central matrix.org Identity server (at the cost of potentially leaking all your contacts information)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:36
+msgid "Enabling this is discouraged and you'd better [learn more](https://github.com/ma1uta/ma1sd/blob/master/docs/features/identity.md#lookups) before proceeding."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:38
+msgid "To enable matrix.org forwarding, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:44
+msgid "Additional features"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:46
+msgid "What this playbook configures for your is some bare minimum Identity Server functionality, so that you won't need to rely on external 3rd party services."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:48
+msgid "A few variables can be toggled in this playbook to alter the ma1sd configuration that gets generated."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:50
+msgid "Still, ma1sd can do much more. You can refer to the [ma1sd website](https://github.com/ma1uta/ma1sd) for more details and configuration options."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:52
+msgid "To use a more custom configuration, you can define a `matrix_ma1sd_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_ma1sd_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-ma1sd/defaults/main.yml) of the ma1sd component."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:54
+msgid "Customizing email templates"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:56
+msgid "If you'd like to change the default email templates used by ma1sd, take a look at the `matrix_ma1sd_threepid_medium_email_custom_` variables (in the `roles/custom/matrix-ma1sd/defaults/main.yml` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:58
+msgid "ma1sd-controlled Registration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:60
+msgid "To use the [Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) feature of ma1sd, you can make use of the following variables:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:62
+msgid "`matrix_synapse_enable_registration` - to enable user-initiated registration in Synapse"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:64
+msgid "`matrix_synapse_enable_registration_captcha` - to validate registering users using reCAPTCHA, as described in the [enabling reCAPTCHA](configuring-captcha.md) documentation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:66
+msgid "`matrix_synapse_registrations_require_3pid` - a list of 3pid types (among `'email'`, `'msisdn'`) required by the Synapse server for registering"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:68
+msgid "variables prefixed with `matrix_ma1sd_container_labels_` (e.g. `matrix_ma1sd_container_labels_matrix_client_3pid_registration_enabled`) - to configure the Traefik reverse-proxy to capture and send registration requests to ma1sd (instead of Synapse), so it can apply its additional functionality"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:70
+msgid "`matrix_ma1sd_configuration_extension_yaml` - to configure ma1sd as required. See the [Registration feature's docs](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) for inspiration. Also see the [Additional features](#additional-features) section below to learn more about how to use `matrix_ma1sd_configuration_extension_yaml`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:72
+msgid "**Note**: For this to work, either the homeserver needs to [federate](configuring-playbook-federation.md) or the `openid` APIs need to exposed on the federation port. When federation is disabled and ma1sd is enabled, we automatically expose the `openid` APIs (only!) on the federation port. Make sure the federation port (usually `https://matrix.example.com:8448`) is whitelisted in your firewall (even if you don't actually use/need federation)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:74
+msgid "Authentication"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:76
+msgid "[Authentication](https://github.com/ma1uta/ma1sd/blob/master/docs/features/authentication.md) provides the possibility to use your own [Identity Stores](https://github.com/ma1uta/ma1sd/blob/master/docs/stores/README.md) (for example LDAP) to authenticate users on your Homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:78
+msgid "To enable authentication against an LDAP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:98
+msgid "Example: SMS verification"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:100
+msgid "If your use case requires mobile verification, it is quite simple to integrate ma1sd with [Twilio](https://www.twilio.com/), an online telephony services gateway. Their prices are reasonable for low-volume projects and integration can be done with the following configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:114
+msgid "Example: Open Registration for every Domain"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:116
+msgid "If you want to open registration for any domain, you have to setup the allowed domains with ma1sd's `blacklist` and `whitelist`. The default behavior when neither the `blacklist`, nor the `whitelist` match, is to allow registration. Beware: you can't block toplevel domains (aka `.xy`) because the internal architecture of ma1sd doesn't allow that."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:130
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:132
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:139
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:141
+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-ma1sd.md:143
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:145
+msgid "If email address validation emails sent by ma1sd are not reaching you, you should look into [Adjusting email-sending settings](configuring-playbook-email.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:147
+msgid "If you'd like additional logging information, temporarily enable verbose logging for ma1sd."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:149
+msgid "To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po
new file mode 100644
index 000000000..3420a45fc
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po
@@ -0,0 +1,623 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:1
+msgid "Setting up Matrix Authentication Service (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:3
+msgid "This playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) - a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:5
+msgid "Matrix Authentication Service is an implementation of [MSC3861: Next-generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:7
+msgid "**Before going through with starting to use Matrix Authentication Service**, make sure to read:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:9
+msgid "the [Reasons to use Matrix Authentication Service](#reasons-to-use-matrix-authentication-service) section below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:10
+msgid "the [Expectations](#expectations) section below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:11
+msgid "the [FAQ section on areweoidcyet.com](https://areweoidcyet.com/#faqs)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:13
+msgid "**If you've already been using Synapse** and have user accounts in its database, you can [migrate to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:15
+msgid "Reasons to use Matrix Authentication Service"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:17
+msgid "You may be wondering whether you should make the switch to Matrix Authentication Service (MAS) or keep using your existing authentication flow via Synapse (password-based or [OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)-enabled)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:19
+msgid "Matrix Authentication Service is **still an experimental service** and **not a default** for this Ansible playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:21
+msgid "The [Expectations](#expectations) section contains a list of what works and what doesn't (**some services don't work with MAS yet**), as well as the **relative irreversability** of the migration process."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:23
+msgid "Below, we'll try to **highlight some potential reasons for switching** to Matrix Authentication Service:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:25
+msgid "To use SSO in [Element X](https://element.io/blog/element-x-ignition/). The old [Synapse OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) login flow is only supported in old Element clients and will not be supported in Element X. Element X will only support the new SSO-based login flow provided by MAS, so if you want to use SSO with Element X, you will need to switch to MAS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:27
+msgid "To help drive adoption of the \"Next-generation auth for Matrix\" by switching to what's ultimately coming anyway"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:29
+msgid "To help discover (and potentially fix) MAS integration issues with this Ansible playbook"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:31
+msgid "To help discover (and potentially fix) MAS integration issues with various other Matrix components (bridges, bots, clients, etc.)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:33
+msgid "To reap some of the security benefits that Matrix Authentication Service offers, as outlined in the [Better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/) article."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:35
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:37
+msgid "⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:39
+msgid "⚠️ **email sending** configured (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:41
+msgid "❌ **disabling all password providers** for Synapse (things like [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc.) More details about this are available in the [Expectations](#expectations) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:43
+msgid "Expectations"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:45
+msgid "This section details what you can expect when switching to the Matrix Authentication Service (MAS)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:47
+msgid "❌ **Synapse password providers will need to be disabled**. You can no longer use [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc. When the authentication flow is handled by MAS (not by Synapse anymore), it doesn't make sense to extend the Synapse authentication flow with additional modules. Many bridges used to rely on shared-secret-auth for doing double-puppeting (impersonating other users), but most (at least the mautrix bridges) nowadays use [Appservice Double Puppet](./configuring-playbook-appservice-double-puppet.md) as a better alternative. Older/maintained bridges may still rely on shared-secret-auth, as do other services like [matrix-corporal](./configuring-playbook-matrix-corporal.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:49
+msgid "❌ Certain **tools like [synapse-admin](./configuring-playbook-synapse-admin.md) do not have full compatibility with MAS yet**. synapse-admin already supports [login with access token](https://github.com/etkecc/synapse-admin/pull/58), browsing users (which Synapse will internally fetch from MAS) and updating user avatars. However, editing users (passwords, etc.) now needs to happen directly against MAS using the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html), which synapse-admin cannot interact with yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:51
+msgid "❌ **Some services experience issues when authenticating via MAS**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:53
+msgid "[Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first time around, but it consistently fails after restarting:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:55
+msgid "cannot initialize matrix bot error=\"olm account is marked as shared, keys seem to have disappeared from the server\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:57
+msgid "[matrix-reminder-bot](./configuring-playbook-bot-matrix-reminder-bot.md) fails to start (see [element-hq/matrix-authentication-service#3439](https://github.com/element-hq/matrix-authentication-service/issues/3439))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:58
+msgid "Other services may be similarly affected. This list is not exhaustive."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:60
+msgid "❌ **Encrypted appservices** do not work yet (related to [MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) and [PR 17705 for Synapse](https://github.com/element-hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will fail to start (see [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3658) for Hookshot). You can use these bridges/bots only if you **keep end-to-bridge encryption disabled** (which is the default setting)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:62
+msgid "⚠️ **You will need to have email sending configured** (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:64
+msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:66
+msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) does not currently seem to preserve the \"admin\" flag for users (as found in the Synapse database). All users are imported as non-admin - see [element-hq/matrix-authentication-service#3440](https://github.com/element-hq/matrix-authentication-service/issues/3440). You may need update the Matrix Authentication Service's database manually and adjust the `can_request_admin` column in the `users` table to `true` for users that need to be administrators (e.g. `UPDATE users SET can_request_admin = true WHERE username = 'someone';`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:68
+msgid "⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependant on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:70
+msgid "⚠️ If you've got [OIDC configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to migrate your OIDC configuration to MAS by adding an [Upstream OAuth2 configuration](#upstream-oauth2-configuration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:72
+msgid "⚠️ A [compatibility layer](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) is installed - all `/_matrix/client/*/login` (etc.) requests will be routed to MAS instead of going to the homeserver. This is done both publicly (e.g. `https://matrix.example.com/_matrix/client/*/login`) and on the internal Traefik entrypoint (e.g. `https://matrix-traefik:8008/_matrix/client/*/login`) which helps addon services reach the homeserver's Client-Server API. You typically don't need to do anything to make this work, but it's good to be aware of it, especially if you have a [custom webserver setup](./configuring-playbook-own-webserver.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:74
+msgid "✅ Your **existing login sessions will continue to work** (you won't get logged out). Migration will require a bit of manual work and minutes of downtime, but it's not too bad."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:76
+msgid "✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), [Element Web](./configuring-playbook-client-element-web.md), Element X, FluffyChat) will be able to use the **new SSO-based login flow** provided by Matrix Authentication Service"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:78
+msgid "✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work. Going through the old login flow does not require users to have a verified email address, as [is the case](https://github.com/element-hq/matrix-authentication-service/issues/1505) for the new SSO-based login flow."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:80
+msgid "✅ [Registering users](./registering-users.md) via **the playbook's `register-user` tag remains unchanged**. The playbook automatically does the right thing regardless of homeserver implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, the playbook will forward user-registration requests to MAS. Registering users via the command-line is no longer done via the `/matrix/synapse/bin/register` script, but via `/matrix/matrix-authentication-service/bin/register-user`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:82
+msgid "✅ Users that are prepared by the playbook (for bots, bridges, etc.) will continue to be registered automatically as expected. The playbook automatically does the right thing regardless of homeserver implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, the playbook will forward user-registration requests to MAS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:84
+msgid "Installation flows"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:86
+msgid "New homeserver"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:88
+msgid "For new homeservers (which don't have any users in their Synapse database yet), follow the [Adjusting the playbook configuration](#adjusting-the-playbook-configuration) instructions and then proceed with [Installing](#installing)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:90
+msgid "Existing homeserver"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:92
+msgid "Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:94
+msgid "For existing Synapse homeservers:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:96
+msgid "when following the [Adjusting the playbook configuration](#adjusting-the-playbook-configuration) instructions, make sure to **disable the integration between Synapse and MAS** by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line as described in the [Marking an existing homeserver for migration](#marking-an-existing-homeserver-for-migration) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:98
+msgid "then follow the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) instructions to perform the installation and migration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:100
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:102
+msgid "To enable Matrix Authentication Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:116
+msgid "In the sub-sections that follow, we'll cover some additional configuration options that you may wish to adjust."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:118
+msgid "There are many other configuration options available. Consult the [`defaults/main.yml` file](../roles/custom/matrix-authentication-service/defaults/main.yml) in the [matrix-authentication-service role](../roles/custom/matrix-authentication-service/) to discover them."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:120
+msgid "Adjusting the Matrix Authentication Service URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:122
+msgid "By default, this playbook installs the Matrix Authentication Service on the `matrix.` subdomain, at the `/auth` path (https://matrix.example.com/auth). 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-matrix-authentication-service.md:124
+msgid "By tweaking the `matrix_authentication_service_hostname` and `matrix_authentication_service_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-matrix-authentication-service.md:126
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:149
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:134
+msgid "Marking an existing homeserver for migration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:136
+msgid "The [configuration above](#adjusting-the-playbook-configuration) instructs existing users wishing to migrate to add `matrix_authentication_service_migration_in_progress: true` to their configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:138
+msgid "This is done temporarily. The migration steps are described in more detail in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:140
+msgid "Upstream OAuth2 configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:142
+msgid "To make Matrix Authentication Service delegate to an existing upstream OAuth 2.0/OIDC provider, you can use its [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:144
+msgid "The playbook exposes a `matrix_authentication_service_config_upstream_oauth2_providers` variable for controlling this setting."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:261
+msgid "💡 Refer to the [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers) for the most up-to-date schema and example for providers. The value shown above here may be out of date."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:263
+msgid "⚠️ The syntax for existing [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) is slightly different, so you will need to adjust your configuration when switching from Synapse OIDC to MAS upstream OAuth2."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:265
+msgid "⚠️ When [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) which contains OIDC-sourced users, you will need to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:267
+msgid "[Configure upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:268
+msgid "go through the [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) process"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:269
+msgid "remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:271
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:273
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Matrix Authentication Service domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:275
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:277
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:279
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:281
+msgid "Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:288
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:290
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:292
+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-matrix-authentication-service.md:294
+msgid "If you're in the process of migrating an existing Synapse homeserver to MAS, you should now follow the rest of the steps in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) guide."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:296
+msgid "💡 After installation, you should [verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:298
+msgid "Migrating an existing Synapse homeserver to Matrix Authentication Service"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:300
+msgid "Our migration guide is loosely based on the upstream [Migrating an existing homeserver](https://element-hq.github.io/matrix-authentication-service/setup/migration.html) guide."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:302
+msgid "Migration is done via a tool called `syn2mas`, which the playbook could run for you (in a container)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:304
+msgid "The installation + migration steps are like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:306
+msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) to **disable the integration between the homeserver and MAS**. This is done by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:308
+msgid "Perform the initial [installation](#installing). At this point:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:310
+msgid "Matrix Authentication Service will be installed. Its database will be empty, so it cannot validate existing access tokens or authentication users yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:312
+msgid "The homeserver will still continue to use its local database for validating existing access tokens."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:314
+msgid "Various [compatibility layer URLs](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) are not yet installed. New login sessions will still be forwarded to the homeserver, which is capable of completing them."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:316
+msgid "The `matrix-user-creator` role would be suppressed, so that it doesn't automatically attempt to create users (for bots, etc.) in the MAS database. These user accounts likely already exist in Synapse's user database and could be migrated over (via syn2mas, as per the steps below), so creating them in the MAS database would have been unnecessary and potentially problematic (conflicts during the syn2mas migration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:318
+msgid "Consider taking a full [backup of your Postgres database](./maintenance-postgres.md#backing-up-postgresql). This is done just in case. The **syn2mas migration tool does not delete any data**, so it should be possible to revert to your previous setup by merely disabling MAS and re-running the playbook (no need to restore a Postgres backup). However, do note that as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:320
+msgid "[Migrate your data from Synapse to Matrix Authentication Service using syn2mas](#migrate-your-data-from-synapse-to-matrix-authentication-service-using-syn2mas)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:322
+msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) again, to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:324
+msgid "remove the `matrix_authentication_service_migration_in_progress: false` line"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:326
+msgid "if you had been using [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:328
+msgid "Perform the [installation](#installing) again. At this point:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:330
+msgid "The homeserver will start delegating authentication to MAS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:332
+msgid "The compatibility layer URLs will be installed. New login sessions will be completed by MAS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:334
+msgid "[Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:336
+msgid "Migrate your data from Synapse to Matrix Authentication Service using syn2mas"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:338
+msgid "We **don't** ask you to [run the `syn2mas` migration advisor command](https://element-hq.github.io/matrix-authentication-service/setup/migration.html#run-the-migration-advisor), because it only gives you the green light if your Synapse configuration (`homeserver.yaml`) is configured in a way that's compatible with MAS (delegating authentication to MAS; disabling Synapse's password config; etc.). Until we migrate your data with the `syn2mas` tool, we intentionally avoid doing these changes to allow existing user sessions to work."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:340
+msgid "You can invoke the `syn2mas` tool via the playbook by running the playbook's `matrix-authentication-service-syn2mas` tag. We recommend first doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:342
+msgid "Configuring syn2mas"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:344
+msgid "If you're using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to [Configuring upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:346
+msgid "If you only have local (non-OIDC) users in your Synapse database, you can likely run `syn2mas` as-is (without doing additional configuration changes)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:348
+msgid "When you're done with potentially configuring `syn2mas`, proceed to doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:350
+msgid "Configuring upstream OIDC provider mapping for syn2mas"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:352
+msgid "If you have existing OIDC users in your Synapse user database (which will be the case if when using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)), you may need to pass an additional `--upstreamProviderMapping` argument to the `syn2mas` tool to tell it which provider (on the Synapse side) maps to which other provider on the MAS side."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:354
+msgid "If you don't do this, `syn2mas` would report errors like this one:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:356
+msgid "[FATAL] migrate - [Failed to import external id 4264b0f0-4f11-4ddd-aedb-b500e4d07c25 with oidc-keycloak for user @alice:example.com: Error: Unknown upstream provider oidc-keycloak]"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:358
+msgid "Below is an example situation and a guide for how to solve it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:360
+msgid "If in `matrix_synapse_oidc_providers` your provider `idp_id` is (was) named `keycloak`, in the Synapse database users would be associated with the `oidc-keycloak` provider (note the `oidc-` prefix that was added automatically by Synapse to your `idp_id` value)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:362
+msgid "The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` on the MAS side, as defined in `matrix_authentication_service_config_upstream_oauth2_providers` (see the [Upstream OAuth2 configuration](#upstream-oauth2-configuration) section above)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:364
+msgid "To tell `syn2mas` how the Synapse-configured OIDC provider maps to the new MAS-configured OIDC provider, add this additional configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:373
+msgid "Performing a syn2mas dry-run"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:375
+msgid "Having [configured syn2mas](#configuring-syn2mas), we recommend doing a [dry-run](https://en.wikipedia.org/wiki/Dry_run_(testing)) first to verify that everything will work out as expected."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:377
+msgid "A dry-run would not cause downtime, because it avoids stopping Synapse."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:379
+msgid "To perform a dry-run, run:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:385
+msgid "Observe the command output (especially the last line of the the syn2mas output). If you are confident that the migration will work out as expected, you can proceed with a [real migration](#performing-a-real-syn2mas-migration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:387
+msgid "Performing a real syn2mas migration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:389
+msgid "Before performing a real migration make sure:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:391
+msgid "you've familiarized yourself with the [expectations](#expectations)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:393
+msgid "you've performed a Postgres backup, just in case"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:395
+msgid "you're aware of the irreversibility of the migration process without disruption after users have created new login sessions via the new MAS setup"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:397
+msgid "you've [configured syn2mas](#configuring-syn2mas), especially if you've used [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:399
+msgid "you've performed a [syn2mas dry-run](#performing-a-syn2mas-dry-run) and don't see any issues in its output"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:401
+msgid "To perform a real migration, run the `matrix-authentication-service-syn2mas` tag **without** the `matrix_authentication_service_syn2mas_dry_run` variable:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:407
+msgid "Having performed a `syn2mas` migration once, trying to do it again will report errors for users that were already migrated (e.g. \"Error: Unknown upstream provider oauth-delegated\")."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:409
+msgid "Verify that Matrix Authentication Service is installed correctly"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:411
+msgid "After [installation](#installing), run the `doctor` subcommand of the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) to verify that MAS is installed correctly."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:413
+msgid "You can do it:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:415
+msgid "either via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag: `just run-tags matrix-authentication-service-mas-cli-doctor`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:417
+msgid "or by running the `mas-cli` script on the server (which invokes the `mas-cli` tool inside a container): `/matrix/matrix-authentication-service/bin/mas-cli doctor`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:419
+msgid "If successful, you should see some output that looks like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:431
+msgid "Management"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:433
+msgid "You can use the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) (exposed via the `/matrix/matrix-authentication-service/bin/mas-cli` script) to perform administrative tasks against MAS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:435
+msgid "This documentation page already mentions:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:437
+msgid "the `mas-cli doctor` sub-command in the [Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly) section, which you can run via the CLI and via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:439
+msgid "the `mas-cli manage register-user` sub-command in the [Registering users](./registering-users.md) documentation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:441
+msgid "There are other sub-commands available. Run `/matrix/matrix-authentication-service/bin/mas-cli` to get an overview."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:443
+msgid "User registration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:445
+msgid "After Matrix Authentication Service is [installed](#installing), users need to be managed there (unless you're managing them in an [upstream OAuth2 provider](#upstream-oauth2-configuration))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:447
+msgid "You can register users new users as described in the [Registering users](./registering-users.md) documentation (via `mas-cli manage register-user` or the Ansible playbook's `register-user` tag)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:449
+msgid "Working around email deliverability issues"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:451
+msgid "Because Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user, you may need to work around email deliverability issues if [your email-sending configuration](./configuring-playbook-email.md) is not working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:453
+msgid "Matrix Authentication Service attempts to verify email addresses by sending a verification email to the address specified by the user whenever they log in to an account without a verified email address."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:455
+msgid "If email delivery is not working, **you can retrieve the email configuration code from the Matrix Authentication Service's logs** (`journalctl -fu matrix-authentication-service`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:457
+msgid "Alternatively, you can use the [`mas-cli` management tool](#management) to manually verify email addresses for users. Example: `/matrix/matrix-authentication-service/bin/mas-cli manage verify-email some.username email@example.com`"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po
new file mode 100644
index 000000000..45f650bac
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po
@@ -0,0 +1,130 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:1
+msgid "Setting up Matrix Corporal (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:5
+msgid "**WARNING**: This is an advanced feature! It requires prior experience with Matrix and a specific need for using [Matrix Corporal](https://github.com/devture/matrix-corporal). If you're unsure whether you have such a need, you most likely don't."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:9
+msgid "The playbook can install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:11
+msgid "In short, it's a sort of automation and firewalling service, which is helpful if you're instaling Matrix services in a controlled corporate environment."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:13
+msgid "See the project's [documentation](https://github.com/devture/matrix-corporal/blob/main/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:15
+msgid "If you decide that you'd like to let this playbook install it for you, you'd need to also:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:16
+msgid "(required) [set up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:17
+msgid "(optional, but encouraged) [set up the REST authentication password provider module](configuring-playbook-rest-auth.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:19
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:21
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:74
+msgid "Matrix Corporal operates with a specific Matrix user on your server. By default, it's `matrix-corporal` (controllable by the `matrix_corporal_reconciliation_user_id_local_part` setting, see above)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:76
+msgid "No matter what Matrix user ID you configure to run it with, make sure that:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:78
+msgid "the Matrix Corporal user is created by [registering it](registering-users.md) **with administrator privileges**. Use a password you remember, as you'll need to log in from time to time to create or join rooms"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:80
+msgid "the Matrix Corporal user is joined and has Admin/Moderator-level access to any rooms you want it to manage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:82
+msgid "Using a locally-stored static policy"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:84
+msgid "If you'd like to use a [static policy file](https://github.com/devture/matrix-corporal/blob/master/docs/policy-providers.md#static-file-pull-style-policy-provider), you can use a configuration like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:116
+msgid "To learn more about what the policy configuration, see the matrix-corporal documentation on [policy](https://github.com/devture/matrix-corporal/blob/master/docs/policy.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:118
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:120
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:127
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-aux-files,setup-corporal,start` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:129
+msgid "`just run-tags setup-aux-files,setup-corporal,start` is useful for maintaining your setup quickly 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 `just setup-all` runs the `ensure-matrix-users-created` tag too."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:131
+msgid "Matrix Corporal files"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:133
+msgid "The following local filesystem paths are mounted in the `matrix-corporal` container and can be used in your configuration (or policy):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:135
+msgid "`/matrix/corporal/config` is mounted at `/etc/matrix-corporal` (read-only)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:137
+msgid "`/matrix/corporal/var` is mounted at `/var/matrix-corporal` (read and write)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:139
+msgid "`/matrix/corporal/cache` is mounted at `/var/cache/matrix-corporal` (read and write)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:141
+msgid "As an example: you can create your own configuration files in `/matrix/corporal/config` and they will appear in `/etc/matrix-corporal` in the Docker container. Your configuration (stuff in `matrix_corporal_policy_provider_config`) needs to refer to these files via the local container paths - `/etc/matrix-corporal` (read-only), `/var/matrix-corporal` (read and write), `/var/cache/matrix-corporal` (read and write)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po
new file mode 100644
index 000000000..c2d7ae3d9
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po
@@ -0,0 +1,66 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:1
+msgid "Setting up matrix-ldap-registration-proxy (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:3
+msgid "The playbook can install and configure [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:5
+msgid "This proxy handles Matrix registration requests and forwards them to LDAP."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:7
+msgid "**Note**: This does support the full Matrix specification for registrations. It only provide a very coarse implementation of a basic password registration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:9
+msgid "Quickstart"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:11
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:22
+msgid "If you already use the [synapse external password provider via LDAP](configuring-playbook-ldap-auth.md) (that is, you have `matrix_synapse_ext_password_provider_ldap_enabled: true` and other options in your configuration) you can use the following values as configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:35
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:37
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:44
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:46
+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 ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po
new file mode 100644
index 000000000..3acc935c1
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po
@@ -0,0 +1,169 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:1
+msgid "Storing Matrix media files using matrix-media-repo (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:3
+msgid "[matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often abbreviated \"MMR\") is a highly customizable multi-domain media repository for Matrix. Intended for medium to large environments consisting of several homeservers, this media repo de-duplicates media (including remote media) while being fully compliant with the specification."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:5
+msgid "Smaller/individual homeservers can still make use of this project's features, though it may be difficult to set up or have higher than expected resource consumption. Please do your research before deploying this as this project may not be useful for your environment."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:7
+msgid "For a simpler alternative (which allows you to offload your media repository storage to S3, etc.), you can [configure S3 storage](configuring-playbook-s3.md) instead of setting up matrix-media-repo."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md
+msgid "**Table of Contents**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md
+msgid "[Quickstart](#quickstart)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md
+msgid "[Additional configuration options](#configuring-the-media-repo)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md
+msgid "[Importing data from an existing media store](#importing-data-from-an-existing-media-store)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:15
+msgid "Quickstart"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:17
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file and [re-run the installation process](./installing.md) for the playbook:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:26
+msgid "The repo is pre-configured for integrating with the Postgres database, Traefik proxy and [Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) (if metrics enabled) from this playbook for all the available homeserver roles. When the media repo is enabled, other media store roles should be disabled (if using Synapse with other media store roles)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:28
+msgid "By default, the media-repo will use the local filesystem for data storage. You can alternatively use a `s3` cloud backend as well. Access token caching is also enabled by default since the logout endpoints are proxied through the media repo."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:30
+msgid "Configuring the media-repo"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:32
+msgid "Additional common configuration options:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:91
+msgid "Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](../roles/custom/matrix-media-repo/defaults/main.yml)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:93
+msgid "Signing Keys"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:95
+msgid "Authenticated media endpoints ([MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916)) requires MMR to have a configured signing key to authorize outbound federation requests. Additionally, the signing key must be merged with your homeserver's signing key file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:97
+msgid "The playbook default is to generate a MMR signing key when invoking the setup role and merge it with your homeserver if you are using Synapse or Dendrite. This can be disabled if desired by setting the option in your inventory:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:103
+msgid "If you wish to manually generate the signing key and merge it with your homeserver's signing key file, see https://docs.t2bot.io/matrix-media-repo/v1.3.5/installation/signing-key/ for more details."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:105
+msgid "**Note that if you uninstall MMR from the playbook, it will not remove the old MMR signing key from your homeserver's signing key file. You will have to remove it manually.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:107
+msgid "Key backup and revoking"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:109
+msgid "Since your homeserver signing key file is modified by the playbook, a backup will be created in `HOMESERVER_DIR/config/example.com.signing.key.backup`. If you need to remove/revoke old keys, you can restore from this backup or remove the MMR key ID from your `example.com.signing.key` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:111
+msgid "Additionally, its recommended after revoking a signing key to update your homeserver config file (`old_signing_keys` field for Synapse and `old_private_keys` for Dendrite). See your homeserver config file for further documentation on how to populate the field."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:113
+msgid "Importing data from an existing media store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:115
+msgid "If you want to add this repo to an existing homeserver managed by the playbook, you will need to import existing media into MMR's database or you will lose access to older media while it is active. MMR versions up to `v1.3.3` only support importing from Synapse, but newer versions (at time of writing: only `latest`) also support importing from Dendrite."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:117
+msgid "**Before importing**: ensure you have an initial matrix-media-repo deployment by following the [quickstart](#quickstart) guide above"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:119
+msgid "Depending on the homeserver implementation yu're using (Synapse, Dendrite), you'll need to use a different import tool (part of matrix-media-repo) and point it to the homeserver's database."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:121
+msgid "Importing data from the Synapse media store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:123
+msgid "To import the Synapse media store, you're supposed to invoke the `import_synapse` tool which is part of the matrix-media-repo container image. Your Synapse database is called `synapse` by default, unless you've changed it by modifying `matrix_synapse_database_database`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:125
+msgid "This guide here is adapted from the [upstream documentation about the import_synapse script](https://github.com/turt2live/matrix-media-repo#importing-media-from-synapse)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:127
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:149
+msgid "Run the following command on the server (after replacing `postgres_connection_password` in it with the value found in your `vars.yml` file):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:139
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:161
+msgid "Enter `1` for the Machine ID when prompted (you are not doing any horizontal scaling) unless you know what you're doing."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:141
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:163
+msgid "This should output a `msg=\"Import completed\"` when finished successfully!"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:143
+msgid "Importing data from the Dendrite media store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:145
+msgid "If you're using the [Dendrite](configuring-playbook-dendrite.md) homeserver instead of the default for this playbook (Synapse), follow this importing guide here."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:147
+msgid "To import the Dendrite media store, you're supposed to invoke the `import_dendrite` tool which is part of the matrix-media-repo container image. Your Dendrite database is called `dendrite_mediaapi` by default, unless you've changed it by modifying `matrix_dendrite_media_api_database`."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po
new file mode 100644
index 000000000..64f9e90c3
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po
@@ -0,0 +1,158 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:1
+msgid "Setting up matrix-registration (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:3
+msgid "The playbook can install and configure [matrix-registration](https://github.com/ZerataX/matrix-registration) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:5
+msgid "**WARNING**: this is a poorly maintained and buggy project. It's better to avoid using it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:7
+msgid "**WARNING**: this is not related to [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:9
+msgid "matrix-registration is a simple python application to have a token based Matrix registration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:11
+msgid "Use matrix-registration to **create unique registration links**, which people can use to register on your Matrix server. It allows you to **keep your server's registration closed (private)**, but still allow certain people (these having a special link) to register a user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:13
+msgid "**matrix-registration** provides 2 things:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:15
+msgid "**an API for creating registration tokens** (unique registration links). This API can be used via `curl` or via the playbook (see [Usage](#usage) below)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:17
+msgid "**a user registration page**, where people can use these registration tokens. By default, exposed at `https://matrix.example.com/matrix-registration`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:19
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:21
+msgid "To enable matrix-registration, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:30
+msgid "Adjusting the matrix-registration URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:32
+msgid "By default, this playbook installs the matrix-registration on the `matrix.` subdomain, at the `/matrix-registration` path (https://matrix.example.com/matrix-registration). 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-matrix-registration.md:34
+msgid "By tweaking the `matrix_registration_hostname` and `matrix_registration_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-matrix-registration.md:36
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:44
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:46
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-registration domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:48
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:50
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:52
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:54
+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-matrix-registration.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-matrix-registration.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-matrix-registration.md:65
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:67
+msgid "**matrix-registration** gets exposed at `https://matrix.example.com/matrix-registration`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:69
+msgid "It provides various [APIs](https://github.com/ZerataX/matrix-registration/wiki/api) - for creating registration tokens, listing tokens, disabling tokens, etc. To make use of all of its capabilities, consider using `curl`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:71
+msgid "We make the most common APIs easy to use via the playbook (see below)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:73
+msgid "Creating registration tokens"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:75
+msgid "To **create a new user registration token (link)**, use this command:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:83
+msgid "The above command creates and returns a **one-time use** token, which **expires** on the 31st of December 2021. Adjust the `one_time` and `ex_date` variables as you see fit."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:85
+msgid "Share the unique registration link (generated by the command above) with users to let them register on your Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:87
+msgid "Listing registration tokens"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:89
+msgid "To **list the existing user registration tokens**, use this command:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:96
+msgid "The shortcut command with `just` program is also available: `just run-tags list-matrix-registration-tokens`"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po
new file mode 100644
index 000000000..3435536f2
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po
@@ -0,0 +1,183 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:1
+msgid "Setting up a Generic Mautrix Bridge (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:3
+msgid "The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, facebook, instagram, signal, hangouts, googlechat, etc.), as well as many other (non-mautrix) bridges. This is a common guide for configuring mautrix bridges."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:5
+msgid "You can see each bridge's features at in the `ROADMAP.md` file in its corresponding [mautrix](https://github.com/mautrix) repository."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:9
+msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:16
+msgid "There are some additional things you may wish to configure about the bridge before you continue. Each bridge may have additional requirements besides `_enabled: true`. For example, the mautrix-telegram bridge (our documentation page about it is [here](configuring-playbook-bridge-mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and `matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each bridge's individual documentation page for details about enabling bridges."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:18
+msgid "To **configure a user as an administrator for all bridges**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:24
+msgid "**Alternatively** (more verbose, but allows multiple admins to be configured), you can do the same on a per-bridge basis with:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:33
+msgid "encryption"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:35
+msgid "Encryption support is off by default. If you would like to enable encryption, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:37
+msgid "**for all bridges with encryption support**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:44
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:61
+msgid "**Alternatively**, for a specific bridge:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:51
+msgid "relay mode"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:53
+msgid "Relay mode is off by default. If you would like to enable relay mode, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:55
+msgid "**for all bridges with relay mode support**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:70
+msgid "You can only have one `matrix_mautrix_SERVICENAME_configuration_extension_yaml` definition in `vars.yml` per bridge, so if you need multiple pieces of configuration there, just merge them like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:82
+msgid "Setting the bot's username"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:88
+msgid "Can be used to set the username for the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:90
+msgid "Discovering additional configuration options"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:92
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-SERVICENAME/defaults/main.yml` to find other things you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:94
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:96
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:103
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:105
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:107
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:109
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:111
+msgid "Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:113
+msgid "To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:115
+msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) is configured and enabled on the server for this playbook by adding"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:121
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:123
+msgid "Controlling the logging level"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:129
+msgid "to `vars.yml` to control the logging level, where you may replace WARN with one of the following to control the verbosity of the logs generated: TRACE, DEBUG, INFO, WARN, ERROR, or FATAL."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:131
+msgid "If you have issues with a service, and are requesting support, the higher levels of logging will generally be more helpful."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:133
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:135
+msgid "To use the bridge, you need to start a chat with `@SERVICENAMEbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:137
+msgid "Send `login` to the bridge bot to get started. You can learn more here about authentication from the bridge's official documentation on Authentication: https://docs.mau.fi/bridges/python/SERVICENAME/authentication.html"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:139
+msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:141
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:143
+msgid "For troubleshooting information with a specific bridge, please see the playbook documentation about it (some other document in in `docs/`) and the upstream ([mautrix](https://github.com/mautrix)) bridge documentation for that specific bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:145
+msgid "Reporting bridge bugs should happen upstream, in the corresponding mautrix repository, not to us."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-nginx.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-nginx.po
new file mode 100644
index 000000000..db6c60afb
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-nginx.po
@@ -0,0 +1,30 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-nginx.md:1
+msgid "Configure Nginx (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-nginx.md:3
+msgid "Since 2024-01, this playbook no longer uses nginx as its reverse-proxy."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ntfy.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ntfy.po
new file mode 100644
index 000000000..daed6d5af
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ntfy.po
@@ -0,0 +1,238 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-ntfy.md:1
+msgid "Setting up the ntfy push notifications server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:3
+msgid "The playbook can install and configure the [ntfy](https://ntfy.sh/) push notifications server for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:5
+msgid "Using the [UnifiedPush](https://unifiedpush.org) standard, ntfy enables self-hosted (Google-free) push notifications from Matrix (and other) servers to UnifiedPush-compatible Matrix compatible client apps running on Android and other devices."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:7
+msgid "This role is intended to support UnifiedPush notifications for use with the Matrix and Matrix-related services that this playbook installs. This role is not intended to support all of ntfy's other features."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:9
+msgid "**Note**: In contrast to push notifications using Google's FCM or Apple's APNs, the use of UnifiedPush allows each end-user to choose the push notification server that they prefer.  As a consequence, deploying this ntfy server does not by itself ensure any particular user or device or client app will use it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:13
+msgid "To enable ntfy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:27
+msgid "For a more complete list of variables that you could override, see the [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/defaults/main.yml) of the ntfy Ansible role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:29
+msgid "For a complete list of ntfy config options that you could put in `ntfy_configuration_extension_yaml`, see the [ntfy config documentation](https://ntfy.sh/docs/config/#config-options)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:31
+msgid "Adjusting the ntfy URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:33
+msgid "By default, this playbook installs ntfy on the `ntfy.` subdomain (`ntfy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:35
+msgid "By tweaking the `ntfy_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:37
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:44
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:46
+msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the ntfy domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:48
+msgid "By default, you will need to create a CNAME record for `ntfy`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:50
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:52
+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-ntfy.md:59
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:61
+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-ntfy.md:63
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:65
+msgid "To make use of your ntfy installation, on Android for example, you need two things:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:67
+msgid "the `ntfy` app"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:68
+msgid "a UnifiedPush-compatible Matrix app"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:70
+msgid "You need to install the `ntfy` app on each device on which you want to receive push notifications through your ntfy server. The `ntfy` app will provide UnifiedPush notifications to any number of UnifiedPush-compatible messaging apps installed on the same device."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:72
+msgid "Setting up the `ntfy` Android app"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:74
+msgid "Install the [ntfy Android app](https://ntfy.sh/docs/subscribe/phone/) from F-droid or Google Play."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:75
+msgid "In its Settings -> `General: Default server`, enter your ntfy server URL, such as `https://ntfy.example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:76
+msgid "In its Settings -> `Advanced: Connection protocol`, choose `WebSockets`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:78
+msgid "That is all you need to do in the ntfy app. It has many other features, but for our purposes you can ignore them. In particular you do not need to follow any instructions about subscribing to a notification topic as UnifiedPush will do that automatically."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:80
+msgid "Setting up a UnifiedPush-compatible Matrix app"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:82
+msgid "Install any UnifiedPush-enabled Matrix app on that same device. The Matrix app will learn from the `ntfy` app that you have configured UnifiedPush on this device, and then it will tell your Matrix server to use it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:84
+msgid "Steps needed for specific Matrix apps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:86
+msgid "FluffyChat-android:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:87
+msgid "Should auto-detect and use it. No manual settings."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:89
+msgid "SchildiChat-android:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:90
+msgid "enable `Settings` -> `Notifications` -> `UnifiedPush: Force custom push gateway`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:91
+msgid "choose `Settings` -> `Notifications` -> `UnifiedPush: Re-register push distributor`. *(For info, a more complex alternative to achieve the same is: delete the relevant unifiedpush registration in `ntfy` app, force-close SchildiChat, re-open it.)*"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:92
+msgid "verify `Settings` -> `Notifications` -> `UnifiedPush: Notification targets` as described below in the \"Troubleshooting\" section."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:94
+msgid "Element-android v1.4.26+:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:95
+msgid "choose `Settings` -> `Notifications` -> `Notification method` -> `ntfy`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:96
+msgid "verify `Settings` -> `Troubleshoot` -> `Troubleshoot notification settings`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:98
+msgid "If the Matrix app asks, \"Choose a distributor: FCM Fallback or ntfy\", then choose \"ntfy\"."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:100
+msgid "If the Matrix app doesn't seem to pick it up, try restarting it and try the Troubleshooting section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:102
+msgid "Web App"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:104
+msgid "ntfy also has a web app to subscribe to and push to topics from the browser. This may be helpful to further troubleshoot UnifiedPush problems or to use ntfy for other purposes. The web app only runs in the browser locally (after downloading the JavaScript)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:106
+msgid "The web app is disabled in this playbook by default as the expectation is that most users won't use it. You can either use the [official hosted one](https://ntfy.sh/app) (it supports using other public reachable ntfy instances) or host it yourself by setting `ntfy_web_root: \"app\"` and re-running Ansible."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:108
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:110
+msgid "First check that the Matrix client app you are using supports UnifiedPush. There may well be different variants of the app."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:112
+msgid "Set the ntfy server's log level to 'DEBUG', as shown in the example settings above, and watch the server's logs with `sudo journalctl -fu matrix-ntfy`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:114
+msgid "To check if UnifiedPush is correctly configured on the client device, look at \"Settings -> Notifications -> Notification Targets\" in Element Android or SchildiChat Android, or \"Settings -> Notifications -> Devices\" in FluffyChat. There should be one entry for each Matrix client app that has enabled push notifications, and when that client is using UnifiedPush you should see a URL that begins with your ntfy server's URL."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:116
+msgid "In the \"Notification Targets\" screen in Element Android or SchildiChat Android, two relevant URLs are shown, \"push\\_key\" and \"Url\", and both should begin with your ntfy server's URL. If \"push\\_key\" shows your server but \"Url\" shows an external server such as `up.schildi.chat` then push notifications will still work but are being routed through that external server before they reach your ntfy server. To rectify that, in SchildiChat (at least around version 1.4.20.sc55) you must enable the `Force custom push gateway` setting as described in the \"Usage\" section above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:118
+msgid "If it is not working, useful tools are \"Settings -> Notifications -> Re-register push distributor\" and \"Settings -> Notifications -> Troubleshoot Notifications\" in SchildiChat Android (possibly also Element Android). In particular the \"Endpoint/FCM\" step of that troubleshooter should display your ntfy server's URL that it has discovered from the ntfy client app."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:120
+msgid "The simple [UnifiedPush troubleshooting](https://unifiedpush.org/users/troubleshooting/) app [UP-Example](https://f-droid.org/en/packages/org.unifiedpush.example/) can be used to manually test UnifiedPush registration and operation on an Android device."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-own-webserver.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-own-webserver.po
new file mode 100644
index 000000000..f84aa080d
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-own-webserver.po
@@ -0,0 +1,194 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-own-webserver.md:1
+msgid "Using your own webserver, instead of this playbook's Traefik reverse-proxy (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:3
+msgid "By default, this playbook installs its own [Traefik](https://traefik.io/) reverse-proxy server (in a Docker container) which listens on ports 80 and 443. If that's okay, you can skip this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:5
+msgid "Traefik"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:7
+msgid "[Traefik](https://traefik.io/) is the default reverse-proxy for the playbook since [2023-02-26](../CHANGELOG.md/#2023-02-26) and serves **2 purposes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:9
+msgid "serving public traffic and providing SSL-termination with certificates obtained from [Let's Encrypt](https://letsencrypt.org/). See [Adjusting SSL certificate retrieval](./configuring-playbook-ssl-certificates.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:11
+msgid "assists internal communication between addon services (briges, bots, etc.) and the homeserver via an internal entrypoint (`matrix-internal-matrix-client-api`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:13
+msgid "There are 2 ways to use Traefik with this playbook, as described below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:15
+msgid "Traefik managed by the playbook"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:17
+msgid "To have the playbook install and use Traefik, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:25
+msgid "Traefik will manage SSL certificates for all services seamlessly."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:27
+msgid "Traefik managed by you"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:53
+msgid "In this mode all roles will still have Traefik labels attached. You will, however, need to configure your Traefik instance and its entrypoints."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:55
+msgid "By default, the playbook configured a `default` certificate resolver and multiple entrypoints."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:57
+msgid "You need to configure 4 entrypoints for your Traefik server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:59
+msgid "`web` (TCP port `80`) - used for redirecting to HTTPS (`web-secure`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:60
+msgid "`web-secure` (TCP port `443`) - used for exposing the Matrix Client-Server API and all other services"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:61
+msgid "`matrix-federation` (TCP port `8448`) - used for exposing the Matrix Federation API"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:62
+msgid "`matrix-internal-matrix-client-api` (TCP port `8008`) - used internally for addon services (bridges, bots) to communicate with the homserver"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:64
+msgid "Below is some configuration for running Traefik yourself, although we recommend using [Traefik managed by the playbook](#traefik-managed-by-the-playbook)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:66
+msgid "Note that this configuration on its own does **not** redirect traffic on port 80 (plain HTTP) to port 443 for HTTPS. If you are not already doing this in Traefik, it can be added to Traefik in a [file provider](https://docs.traefik.io/v2.0/providers/file/) as follows:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:86
+msgid "You can use the following `docker-compose.yml` as example to launch Traefik."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:122
+msgid "Another webserver"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:124
+msgid "If you don't wish to use Traefik, you can also use your own webserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:126
+msgid "Doing this is possible, but requires manual work."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:128
+msgid "There are 2 ways to go about it:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:130
+msgid "(recommended) [Fronting the integrated reverse-proxy webserver with another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) - using the playbook-managed reverse-proxy (Traefik), but disabling SSL termination for it, exposing this reverse-proxy on a few local ports (e.g. `127.0.0.1:81`, etc.) and forwarding traffic from your own webserver to those few ports"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:132
+msgid "(difficult) [Using no reverse-proxy on the Matrix side at all](#using-no-reverse-proxy-on-the-matrix-side-at-all) disabling the playbook-managed reverse-proxy (Traefik), exposing services one by one using `_host_bind_port` variables and forwarding traffic from your own webserver to those ports"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:134
+msgid "Fronting the integrated reverse-proxy webserver with another reverse-proxy"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:136
+msgid "This method is about leaving the integrated reverse-proxy webserver be, but making it not get in the way (using up important ports, trying to retrieve SSL certificates, etc.)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:138
+msgid "If you wish to use another webserver, the integrated reverse-proxy webserver usually gets in the way because it attempts to fetch SSL certificates and binds to ports 80, 443 and 8448 (if Matrix Federation is enabled)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:140
+msgid "You can disable such behavior and make the integrated reverse-proxy webserver only serve traffic locally on the host itself (or over a local network)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:142
+msgid "This is the recommended way for using another reverse-proxy, because the integrated one would act as a black box and wire all Matrix services correctly. You would then only need to reverse-proxy a few individual domains and ports over to it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:144
+msgid "To front Traefik with another reverse-proxy, you would need some configuration like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:194
+msgid "Such a configuration would expose all services on a local port `81` and Matrix Federation on a local port `8449`. Your reverse-proxy configuration needs to send traffic to these ports. [`examples/reverse-proxies`](../examples/reverse-proxies/) contains examples for various webservers such as Apache2, Caddy, HAproxy, nginx and Nginx Proxy Manager."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:196
+msgid "It's important that these webservers proxy-pass requests to the correct `ip:port` and also set the `Host` HTTP header appropriately. If you don't pass the `Host` header correctly, Traefik will return a `404 - not found` error."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:198
+msgid "To put it another way:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:199
+msgid "`curl http://127.0.0.1:81` will result in a `404 - not found` error"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:200
+msgid "but `curl -H 'Host: matrix.example.com' http://127.0.0.1:81` should work."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:202
+msgid "Using no reverse-proxy on the Matrix side at all"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:204
+msgid "Instead of [Fronting the integrated reverse-proxy webserver with another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy), you can also go another way -- completely disabling the playbook-managed Traefik reverse-proxy. You would then need to reverse-proxy from your own webserver directly to each individual Matrix service."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:206
+msgid "This is more difficult, as you would need to handle the configuration for each service manually. Enabling additional services would come with extra manual work you need to do."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:208
+msgid "Also, the Traefik reverse-proxy, besides fronting everything is also serving a 2nd purpose of allowing addons services to communicate with the Matrix homeserver thanks to its `matrix-internal-matrix-client-api` entrypoint (read more about it above). Disabling Traefik completely means the playbook would wire services to directly talk to the homeserver. This can work for basic setups, but not for more complex setups involving [matrix-media-repo](./configuring-playbook-matrix-media-repo.md), [matrix-corporal](./configuring-playbook-matrix-corporal.md) or other such services that need to \"steal routes\" from the homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:210
+msgid "If your webserver is on the same machine, ensure your web server user (something like `http`, `apache`, `www-data`, `nginx`) is part of the `matrix` group. You should run something like this: `usermod -a -G matrix nginx`. This allows your webserver user to access files owned by the `matrix` group, so that it can serve static files from `/matrix/static-files`."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po
new file mode 100644
index 000000000..b8e55d975
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po
@@ -0,0 +1,66 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:1
+msgid "Setting up Pantalaimon (E2EE aware proxy daemon) (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:3
+msgid "The playbook can install and configure the [pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:5
+msgid "See the project's [documentation](https://github.com/matrix-org/pantalaimon/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:7
+msgid "This role exposes Pantalaimon's API only within the container network, so bots and clients installed on the same machine can use it. In particular the [Draupnir](configuring-playbook-bot-draupnir.md) and [Mjolnir](configuring-playbook-bot-mjolnir.md) roles (and possibly others) can use it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:11
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:17
+msgid "The default configuration should suffice. For advanced configuration, you can override the variables documented in the role's [defaults](../roles/custom/matrix-pantalaimon/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:19
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:21
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:28
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:30
+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 ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po
new file mode 100644
index 000000000..df09dce7b
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po
@@ -0,0 +1,158 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:1
+msgid "Setting up postgres backup (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:3
+msgid "The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you via the [ansible-role-postgres-backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup) Ansible role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:5
+msgid "For a more complete backup solution (one that includes not only Postgres, but also other configuration/data files), you may wish to look into [BorgBackup](configuring-playbook-backup-borg.md) instead."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:9
+msgid "To enable Postgres backup, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:15
+msgid "Refer to the table below for additional configuration variables and their default values."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Name"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Default value"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Description"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`postgres_backup_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`false`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Set to true to use [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) to create automatic database backups"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`postgres_backup_schedule`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`'@daily'`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Cron-schedule specifying the interval between postgres backups."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`postgres_backup_keep_days`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`7`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Number of daily backups to keep"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`postgres_backup_keep_weeks`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`4`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Number of weekly backups to keep"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`postgres_backup_keep_months`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`12`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Number of monthly backups to keep"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`postgres_backup_base_path`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`\"{{ matrix_base_data_path }}/postgres-backup\"`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Base path for postgres-backup. Also see `postgres_backup_data_path`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`postgres_backup_data_path`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`\"{{ postgres_backup_base_path }}/data\"`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Storage path for postgres-backup database backups"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:27
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:29
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:36
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:38
+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 ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po
new file mode 100644
index 000000000..45ed22103
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po
@@ -0,0 +1,346 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:1
+msgid "Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:3
+msgid "The playbook can install [Grafana](https://grafana.com/) with [Prometheus](https://prometheus.io/) and configure performance metrics of your homeserver with graphs for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:5
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:7
+msgid "To enable Grafana and/or Prometheus, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:33
+msgid "The retention policy of Prometheus metrics is [15 days by default](https://prometheus.io/docs/prometheus/latest/storage/#operational-aspects). Older data gets deleted automatically."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:35
+msgid "Adjusting the Grafana URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:37
+msgid "By default, this playbook installs Grafana web user-interface on the `stats.` subdomain (`stats.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:39
+msgid "By tweaking the `grafana_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:41
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:48
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:50
+msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the Grafana domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:52
+msgid "By default, you will need to create a CNAME record for `stats`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:54
+msgid "**Note**: It is possible to install Prometheus without installing Grafana. This case it is not required to create the CNAME record."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:56
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:58
+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-prometheus-grafana.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-prometheus-grafana.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-prometheus-grafana.md:69
+msgid "What does it do?"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Name"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Description"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`prometheus_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`prometheus_node_exporter_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "[Node Exporter](https://prometheus.io/docs/guides/node-exporter/) is an addon of sorts to Prometheus that collects generic system information such as CPU, memory, filesystem, and even system temperatures"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`prometheus_postgres_exporter_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an addon of sorts to expose Postgres database metrics to Prometheus."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_prometheus_nginxlog_exporter_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "[NGINX Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose NGINX logs to Prometheus."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`grafana_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "[Grafana](https://grafana.com/) is the visual component. It shows (on the `stats.example.com` subdomain) the dashboards with the graphs that we're interested in"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`grafana_anonymous_access`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`grafana_default_admin_user`<br>`grafana_default_admin_password`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "By default Grafana creates a user with `admin` as the username and password. If you feel this is insecure and you want to change it beforehand, you can do that here"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:81
+msgid "Security and privacy"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:83
+msgid "Metrics and resulting graphs can contain a lot of information. This includes system specs but also usage patterns. This applies especially to small personal/family scale homeservers. Someone might be able to figure out when you wake up and go to sleep by looking at the graphs over time. Think about this before enabling anonymous access. And you should really not forget to change your Grafana password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:85
+msgid "Most of our docker containers run with limited system access, but the `prometheus-node-exporter` has access to the host network stack and (readonly) root filesystem. This is required to report on them. If you don't like that, you can set `prometheus_node_exporter_enabled: false` (which is actually the default). You will still get Synapse metrics with this container disabled. Both of the dashboards will always be enabled, so you can still look at historical data after disabling either source."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:87
+msgid "Collecting metrics to an external Prometheus server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:89
+msgid "**If the integrated Prometheus server is enabled** (`prometheus_enabled: true`), metrics are collected by it from each service via communication that happens over the container network. Each service does not need to expose its metrics \"publicly\"."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:91
+msgid "When you'd like **to collect metrics from an external Prometheus server**, you need to expose service metrics outside of the container network."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:93
+msgid "The playbook provides a single endpoint (`https://matrix.example.com/metrics/*`), under which various services may expose their metrics (e.g. `/metrics/node-exporter`, `/metrics/postgres-exporter`, `/metrics/hookshot`, etc). To expose all services on this `/metrics/*` feature, use `matrix_metrics_exposure_enabled`. To protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication), see `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users` below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:95
+msgid "When using `matrix_metrics_exposure_enabled`, you don't need to expose metrics for individual services one by one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:97
+msgid "The following variables may be of interest:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_metrics_exposure_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to **enable metrics exposure for all services** on `https://matrix.example.com/metrics/*`. If you think this is too much, refer to the helpful (but nonexhaustive) list of individual `matrix_SERVICE_metrics_proxying_enabled` (or similar) variables below for exposing metrics on a per-service basis."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_metrics_exposure_http_basic_auth_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to protect all `https://matrix.example.com/metrics/*` endpoints with [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) (see the other variables below for supplying the actual credentials). When enabled, all endpoints beneath `/metrics` will be protected with the same credentials"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_metrics_exposure_http_basic_auth_users`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to the Basic Authentication credentials (raw `htpasswd` file content) used to protect `/metrics/*`. This htpasswd-file needs to be generated with the `htpasswd` tool and can include multiple username/password pairs."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_synapse_metrics_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to make Synapse expose metrics (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_synapse_metrics_proxying_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to expose Synapse's metrics on `https://matrix.example.com/metrics/synapse/main-process` and `https://matrix.example.com/metrics/synapse/worker/TYPE-ID`. Read [below](#collecting-synapse-worker-metrics-to-an-external-prometheus-server) if you're running a Synapse worker setup (`matrix_synapse_workers_enabled: true`). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to enable the node (general system stats) exporter (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`prometheus_node_exporter_container_labels_traefik_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to expose the node (general system stats) metrics on `https://matrix.example.com/metrics/node-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to enable the [Postgres exporter](configuring-playbook-prometheus-postgres.md) (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to expose the [Postgres exporter](configuring-playbook-prometheus-postgres.md) metrics on `https://matrix.example.com/metrics/postgres-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to enable the [NGINX Log exporter](configuring-playbook-prometheus-nginxlog.md) (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_sliding_sync_metrics_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) expose metrics (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_sliding_sync_metrics_proxying_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to expose the [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) metrics on `https://matrix.example.com/metrics/sliding-sync`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_bridge_hookshot_metrics_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to make [Hookshot](configuring-playbook-bridge-hookshot.md) expose metrics (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_bridge_hookshot_metrics_proxying_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to expose the [Hookshot](configuring-playbook-bridge-hookshot.md) metrics on `https://matrix.example.com/metrics/hookshot`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_SERVICE_metrics_proxying_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Various other services/roles may provide similar `_metrics_enabled` and `_metrics_proxying_enabled` variables for exposing their metrics. Refer to each role for details. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above or `matrix_SERVICE_container_labels_metrics_middleware_basic_auth_enabled`/`matrix_SERVICE_container_labels_metrics_middleware_basic_auth_users` variables provided by each role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_media_repo_metrics_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to make media-repo expose metrics (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:118
+msgid "Collecting Synapse worker metrics to an external Prometheus server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:120
+msgid "If you are using workers (`matrix_synapse_workers_enabled: true`) and have enabled `matrix_synapse_metrics_proxying_enabled` as described above, the playbook will also automatically expose all Synapse worker threads' metrics to `https://matrix.example.com/metrics/synapse/worker/ID`, where `ID` corresponds to the worker `id` as exemplified in `matrix_synapse_workers_enabled_list`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:122
+msgid "The playbook also generates an exemplary config file (`/matrix/synapse/external_prometheus.yml.template`) with all the correct paths which you can copy to your Prometheus server and adapt to your needs. Make sure to edit the specified `password_file` path and contents and path to your `synapse-v2.rules`. It will look a bit like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:150
+msgid "More information"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:152
+msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:153
+msgid "[Understanding Synapse Performance Issues Through Grafana Graphs](https://element-hq.github.io/synapse/latest/usage/administration/understanding_synapse_through_grafana_graphs.html) at the Synapse Github Wiki"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:154
+msgid "[The Prometheus scraping rules](https://github.com/element-hq/synapse/tree/master/contrib/prometheus) (we use v2)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:155
+msgid "[The Synapse Grafana dashboard](https://github.com/element-hq/synapse/tree/master/contrib/grafana)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:156
+msgid "[The Node Exporter dashboard](https://github.com/rfrail3/grafana-dashboards) (for generic non-synapse performance graphs)"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po
new file mode 100644
index 000000000..9b64b1d1e
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po
@@ -0,0 +1,114 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:1
+msgid "Enabling metrics and graphs for NginX logs (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:3
+msgid "It can be useful to have some (visual) insight into [nginx](https://nginx.org/) logs."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:5
+msgid "This adds [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) to your Matrix deployment."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:7
+msgid "It will collect access logs from various nginx reverse-proxies which may be used internally (e.g. `matrix-synapse-reverse-proxy-companion`, if Synapse workers are enabled) and will make them available at a Prometheus-compatible `/metrics` endpoint."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:9
+msgid "**Note**: nginx is only used internally by this Ansible playbook. With Traefik being our default reverse-proxy, collecting nginx metrics is less relevant."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:11
+msgid "To make use of this, you need to install [Prometheus](./configuring-playbook-prometheus-grafana.md) either via the playbook or externally. When using an external Prometheus, configuration adjustments are necessary - see [Save metrics on an external Prometheus server](#save-metrics-on-an-external-prometheus-server)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:13
+msgid "If your setup includes [Grafana](./configuring-playbook-prometheus-grafana.md), a dedicated `NGINX PROXY` Grafana dashboard will be created."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:15
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:17
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:23
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:25
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:32
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:34
+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-prometheus-nginxlog.md:36
+msgid "Docker Image Compatibility"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:38
+msgid "At the moment of writing only images for `amd64` and `arm64` architectures are available. The playbook currently does not support [self-building](./self-building.md) a container image on other architectures. You can however use a custom-build image by setting:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:45
+msgid "Security and privacy"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:47
+msgid "Metrics and resulting graphs can contain a lot of information. NginX logs contain information like IP address, URLs, UserAgents and more. This information can reveal usage patterns and could be considered Personally Identifiable Information (PII). Think about this before enabling (anonymous) access. Please make sure you change the default Grafana password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:49
+msgid "Save metrics on an external Prometheus server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:51
+msgid "The playbook will automatically integrate the metrics into the [Prometheus](./configuring-playbook-prometheus-grafana.md) server provided with this playbook (if enabled). In such cases, the metrics endpoint is not exposed publicly - it's only available on the container network."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:53
+msgid "When using an external Prometheus server, you'll need to expose metrics publicly. See [Collecting metrics to an external Prometheus server](./configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:55
+msgid "You can either use `matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled: true` to expose just this one service, or `matrix_metrics_exposure_enabled: true` to expose all services."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:57
+msgid "Whichever way you go with, this service will expose its metrics endpoint **without password-protection** at `https://matrix.example.com/metrics/nginxlog` by default."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:59
+msgid "For password-protection, use (`matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`) or (`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po
new file mode 100644
index 000000000..f0e689f1a
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po
@@ -0,0 +1,106 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:1
+msgid "Enabling metrics and graphs for Postgres (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:3
+msgid "Expanding on the metrics exposed by the [synapse exporter and the node exporter](configuring-playbook-prometheus-grafana.md), the playbook enables the [postgres exporter](https://github.com/prometheus-community/postgres_exporter) that exposes more detailed information about what's happening on your postgres database."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:5
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:7
+msgid "To enable the postgres exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:13
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:15
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:22
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:24
+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-prometheus-postgres.md:26
+msgid "What does it do?"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "Name"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "Description"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "`prometheus_postgres_exporter_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "Enable the postgres prometheus exporter. This sets up the docker container, connects it to the database and adds a 'job' to the prometheus config which tells prometheus about this new exporter. The default is 'false'"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "`prometheus_postgres_exporter_database_username`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "The 'username' for the user that the exporter uses to connect to the database. The default is 'matrix_prometheus_postgres_exporter'"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "`prometheus_postgres_exporter_database_password`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "The 'password' for the user that the exporter uses to connect to the database. By default, this is auto-generated by the playbook"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "If set to `true`, exposes the Postgres exporter metrics on `https://matrix.example.com/metrics/postgres-exporter` for usage with an [external Prometheus server](configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` on that other documentation page."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:35
+msgid "More information"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:37
+msgid "[The PostgresSQL dashboard](https://grafana.com/grafana/dashboards/9628) (generic postgres dashboard)"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rageshake.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rageshake.po
new file mode 100644
index 000000000..f9ff03223
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rageshake.po
@@ -0,0 +1,106 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-rageshake.md:1
+msgid "Setting up the rageshake bug report server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:3
+msgid "The playbook can install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:5
+msgid "This is useful if you're developing your own applications and would like to collect bug reports for them."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:9
+msgid "To enable rageshake, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:15
+msgid "rageshake has various options which don't have dedicated Ansible variables. You can see the full list of options in the [`rageshake.sample.yaml` file](https://github.com/matrix-org/rageshake/blob/master/rageshake.sample.yaml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:17
+msgid "To set these, you can make use of the  `matrix_rageshake_configuration_extension_yaml` variable like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:27
+msgid "Adjusting the rageshake URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:29
+msgid "By default, this playbook installs rageshake on the `rageshake.` subdomain (`rageshake.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:31
+msgid "By tweaking the `matrix_rageshake_hostname` and `matrix_rageshake_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-rageshake.md:33
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:44
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:46
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the rageshake domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:48
+msgid "By default, you will need to create a CNAME record for `rageshake`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:50
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:52
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:54
+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-rageshake.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-rageshake.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-rageshake.md:65
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:67
+msgid "Refer to the [rageshake documentation](https://github.com/matrix-org/rageshake) for available APIs, etc."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rest-auth.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rest-auth.po
new file mode 100644
index 000000000..df2795e33
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-rest-auth.po
@@ -0,0 +1,62 @@
+# Translations template for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\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"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-rest-auth.md:1
+msgid "Setting up the REST authentication password provider module (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:3
+msgid "The playbook can install and configure [matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:5
+msgid "See the project's [documentation](https://github.com/ma1uta/matrix-synapse-rest-password-provider/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:9
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:19
+msgid "Authenticating only using a password provider"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:21
+msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:27
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:29
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:36
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:38
+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 ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-riot-web.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-riot-web.po
new file mode 100644
index 000000000..ea4db761c
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-riot-web.po
@@ -0,0 +1,94 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-riot-web.md:1
+msgid "Configuring Riot-web (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:3
+msgid "By default, this playbook **used to install** the [Riot-web](https://github.com/element-hq/riot-web) Matrix client web application."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:5
+msgid "Riot has since been [renamed to Element](https://element.io/blog/welcome-to-element/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:7
+msgid "to learn more about Element Web and its configuration, see our dedicated [Configuring Element Web](configuring-playbook-client-element-web.md) documentation page"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:8
+msgid "to learn how to migrate from Riot to Element Web, see [Migrating to Element Web](#migrating-to-element-web) below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:10
+msgid "Migrating to Element Web"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:12
+msgid "Migrating your custom settings"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:14
+msgid "If you have custom `matrix_riot_web_` variables in your `inventory/host_vars/matrix.example.com/vars.yml` file, you'll need to rename them (`matrix_riot_web_` -> `matrix_client_element_`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:16
+msgid "Some other playbook variables (but not all) with `riot` in their name are also renamed. The playbook checks and warns if you are using the old name for some commonly used ones."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:18
+msgid "Domain migration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:20
+msgid "We used to set up Riot at the `riot.example.com` domain. The playbook now sets up Element Web at `element.example.com` by default."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:22
+msgid "There are a few options for handling this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:24
+msgid "(**avoiding changes** - using the old `riot.example.com` domain and avoiding DNS changes) -- to keep using `riot.example.com` instead of `element.example.com`, override the domain at which the playbook serves Element Web: `matrix_server_fqn_element: \"riot.{{ matrix_domain }}\"`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:26
+msgid "(**embracing changes** - using only `element.example.com`) - set up the `element.example.com` DNS record (see [Configuring DNS](configuring-dns.md)). You can drop the `riot.example.com` in this case."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:28
+msgid "Re-running the playbook"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:30
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:37
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:39
+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 ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po
new file mode 100644
index 000000000..69b21cad4
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po
@@ -0,0 +1,183 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:1
+msgid "Storing Matrix media files on Amazon S3 with Goofys (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:3
+msgid "If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service), you can let this playbook configure [Goofys](https://github.com/kahing/goofys) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:5
+msgid "Another (and better performing) way to use S3 storage with Synapse is [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:7
+msgid "Using a Goofys-backed media store works, but performance may not be ideal. If possible, try to use a region which is close to your Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:9
+msgid "If you'd like to move your locally-stored media store data to Amazon S3 (or another S3-compatible object store), we also provide some migration instructions below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:13
+msgid "After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:23
+msgid "You can use any S3-compatible object store by **additionally** configuring these variables:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:30
+msgid "If you have local media store files and wish to migrate to Backblaze B2 subsequently, follow our [migration guide to Backblaze B2](#migrating-to-backblaze-b2) below instead of applying this configuration as-is."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:32
+msgid "Migrating from local filesystem storage to S3"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:34
+msgid "It's a good idea to [make a complete server backup](faq.md#how-do-i-back-up-the-data-on-my-server) before migrating your local media store to an S3-backed one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:36
+msgid "After making the backup, follow one of the guides below for a migration path from a locally-stored media store to one stored on S3-compatible storage:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:38
+msgid "[Migrating to any S3-compatible storage (universal, but likely slow)](#migrating-to-any-s3-compatible-storage-universal-but-likely-slow)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:39
+msgid "[Migrating to Backblaze B2](#migrating-to-backblaze-b2)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:41
+msgid "Migrating to any S3-compatible storage (universal, but likely slow)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:43
+msgid "Proceed with the steps below without stopping Matrix services"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:45
+msgid "Start by adding the base S3 configuration in your `vars.yml` file (seen above, may be different depending on the S3 provider of your choice)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:47
+msgid "In addition to the base configuration you see above, add this to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:53
+msgid "This enables S3 support, but mounts the S3 storage bucket to `/matrix/s3-media-store` without hooking it to your homeserver yet. Your homeserver will still continue using your local filesystem for its media store."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:55
+msgid "Run the playbook to apply the changes: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:57
+msgid "Do an **initial sync of your files** by running this **on the server** (it may take a very long time):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:63
+msgid "You may need to install `rsync` manually."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:65
+#: ../../../docs/configuring-playbook-s3-goofys.md:106
+msgid "Stop all Matrix services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:67
+msgid "Start the S3 service by running this **on the server**: `systemctl start matrix-goofys`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:69
+msgid "Sync the files again by re-running the `rsync` command you see in step #5"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:71
+msgid "Stop the S3 service by running this **on the server**: `systemctl stop matrix-goofys`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:73
+#: ../../../docs/configuring-playbook-s3-goofys.md:114
+msgid "Get the old media store out of the way by running this command on the server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:79
+msgid "Remove the `matrix_s3_media_store_path` configuration from your `vars.yml` file (undoing step #3 above)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:81
+#: ../../../docs/configuring-playbook-s3-goofys.md:122
+msgid "Run the playbook: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:83
+#: ../../../docs/configuring-playbook-s3-goofys.md:124
+msgid "You're done! Verify that loading existing (old) media files works and that you can upload new ones."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:85
+#: ../../../docs/configuring-playbook-s3-goofys.md:126
+msgid "When confident that it all works, get rid of the local media store directory: `rm -rf /matrix/synapse/storage/media-store-local-backup`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:87
+msgid "Migrating to Backblaze B2"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:89
+msgid "While all Matrix services are running, run the following command on the server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:91
+msgid "(you need to adjust the 3 `--env` line below with your own data)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:104
+msgid "This is some initial file sync, which may take a very long time."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:108
+msgid "Run the command from step #1 again."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:110
+msgid "Doing this will sync any new files that may have been created locally in the meantime."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:112
+msgid "Now that Matrix services aren't running, we're sure to get Backblaze B2 and your local media store fully in sync."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:120
+msgid "Put the [Backblaze B2 settings](configuring-playbook-s3.md#backblaze-b2) in your `vars.yml` file"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3.po
new file mode 100644
index 000000000..c097ff4d3
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-s3.po
@@ -0,0 +1,218 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-s3.md:1
+msgid "Storing Synapse media files on Amazon S3 or another compatible Object Storage (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:3
+msgid "By default, this playbook configures your server to store Synapse's content repository (`media_store`) files on the local filesystem. If that's okay, you can skip this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:5
+msgid "As an alternative to storing media files on the local filesystem, you can store them on [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object store."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:7
+msgid "You can do this either by sticking to Synapse's media repository and making that use S3 (read below for this method), or by switching to an external media storage implementation like [matrix-media-repo](configuring-playbook-matrix-media-repo.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:9
+msgid "First, [choose an Object Storage provider](#choosing-an-object-storage-provider)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:11
+msgid "Then, [create the S3 bucket](#bucket-creation-and-security-configuration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:13
+msgid "Finally, [set up S3 storage for Synapse](#setting-up) (with [Goofys](configuring-playbook-s3-goofys.md), [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md), or use s3 datastore with the [matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/configuration/s3-datastore.html))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:15
+msgid "Choosing an Object Storage provider"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:17
+msgid "You can create [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object storage like [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html), [Storj](https://storj.io), [Wasabi](https://wasabi.com), [Digital Ocean Spaces](https://www.digitalocean.com/products/spaces), etc."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:19
+msgid "Amazon S3, Backblaze B2, and Storj are pay-as-you with no minimum charges for storing too little data."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:21
+msgid "All these providers have different prices, with Storj appearing to be the cheapest (as of 2024-10, storage fee is $0.004 per GB/month, and egress fee is $0.007 per GB). Backblaze egress is free, but for only certain users for up to 3x the amount of data stored. Beyond that you will pay $0.01/GB of egress."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:23
+msgid "Wasabi has a minimum charge of 1TB if you're storing less than 1TB, which becomes expensive if you need to store less data than that. Likewise, Digital Ocean Spaces has also a minimum charge of 250GB ($5/month as of 2022-10)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:25
+msgid "Here are some of the important aspects of choosing the right provider:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:27
+msgid "if a provider is a company you like and trust (or dislike less than the others)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:28
+msgid "if a provider implements end-to-end encryption of your data"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:29
+msgid "if a provider has a data region close to your Matrix server (if it's farther away, high latency may cause slowdowns)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:30
+msgid "if a provider's infrastructure such as data center is centralized or distributed"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:31
+msgid "if a provider's price model is transparent (whether it includes hidden costs like minimum charge, minimum storage term, etc.)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:32
+msgid "if a provider has free or cheap egress fee (in case you need to get the data out often, for some reason) - likely not too important for the common use-case"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:34
+msgid "Bucket creation and Security Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:36
+msgid "Now that you've [chosen an Object Storage provider](#choosing-an-object-storage-provider), you need to create a storage bucket."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:38
+msgid "How you do this varies from provider to provider, with Amazon S3 being the most complicated due to its vast number of services and complicated security policies."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:40
+msgid "Below, we provider some guides for common providers. If you don't see yours, look at the others for inspiration or read some guides online about how to create a bucket. Feel free to contribute to this documentation with an update!"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:42
+msgid "Amazon S3"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:44
+msgid "You'll need an Amazon S3 bucket and some IAM user credentials (access key + secret key) with full write access to the bucket. Example IAM security policy:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:65
+msgid "**Note**: This policy needs to be attached to an IAM user created from the **Security Credentials** menu. This is not a **Bucket Policy**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:67
+msgid "Backblaze B2"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:69
+msgid "To use [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html) you first need to sign up."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:71
+msgid "You [can't easily change which region (US, Europe) your Backblaze account stores files in](https://old.reddit.com/r/backblaze/comments/hi1v90/make_the_choice_for_the_b2_data_center_region/), so make sure to carefully choose the region when signing up (hint: it's a hard to see dropdown below the username/password fields in the signup form)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:73
+msgid "After logging in to Backblaze:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:75
+msgid "create a new **private** bucket through its user interface (you can call it something like `matrix-example-media-store`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:76
+msgid "note the **Endpoint** for your bucket (something like `s3.us-west-002.backblazeb2.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:77
+msgid "adjust its Lifecycle Rules to: Keep only the last version of the file"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:78
+msgid "go to [App Keys](https://secure.backblaze.com/app_keys.htm) and use the **Add a New Application Key** to create a new one"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:79
+msgid "restrict it to the previously created bucket (e.g. `matrix-example-media-store`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:80
+msgid "give it *Read & Write* access"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:82
+msgid "The `keyID` value is your **Access Key** and `applicationKey` is your **Secret Key**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:84
+msgid "For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3-synapse-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) you will need:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:86
+msgid "**Endpoint URL** - this is the  **Endpoint** value you saw above, but prefixed with `https://`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:88
+msgid "**Region** - use the value you see in the Endpoint (e.g. `us-west-002`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:90
+msgid "**Storage Class** - use `STANDARD`. Backblaze B2 does not have different storage classes, so it doesn't make sense to use any other value."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:92
+msgid "Other providers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:94
+msgid "For other S3-compatible providers, you may not need to configure security policies, etc. (just like for [Backblaze B2](#backblaze-b2))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:96
+msgid "You most likely just need to create an S3 bucket and get some credentials (access key and secret key) for accessing the bucket in a read/write manner."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:98
+msgid "Setting up"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:100
+msgid "To set up Synapse to store files in S3, follow the instructions for the method of your choice:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:102
+msgid "using [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) (recommended)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:103
+msgid "using [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:104
+msgid "using [matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po
new file mode 100644
index 000000000..6622bf13e
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po
@@ -0,0 +1,66 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:1
+msgid "Setting up the Shared Secret Auth password provider module (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:3
+msgid "The playbook can install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:5
+msgid "See the project's [documentation](https://github.com/devture/matrix-synapse-shared-secret-auth/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:9
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:18
+msgid "Authenticating only using a password provider"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:20
+msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:26
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:28
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:35
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:37
+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 ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po
new file mode 100644
index 000000000..a89308ff2
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po
@@ -0,0 +1,118 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:1
+msgid "Setting up the Sliding Sync proxy (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:3
+msgid "**Note**: The sliding-sync proxy is **not required** anymore as it's been replaced with a different method (called Simplified Sliding Sync) which is integrated into newer homeservers by default (**Conduit** homeserver from version `0.6.0` or **Synapse** from version `1.114`). This component and documentation remain here for historical purposes, but **installing this old sliding-sync proxy is generally not recommended anymore**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:5
+msgid "The playbook can install and configure [sliding-sync](https://github.com/matrix-org/sliding-sync) proxy for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:7
+msgid "Sliding Sync is an implementation of [MSC3575](https://github.com/matrix-org/matrix-spec-proposals/blob/kegan/sync-v3/proposals/3575-sync.md) and a prerequisite for running Element X clients ([Element X iOS](https://github.com/element-hq/element-x-ios) and [Element X Android](https://github.com/element-hq/element-x-android)). See the project's [documentation](https://github.com/matrix-org/sliding-sync) to learn more."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:11
+msgid "To enable Sliding Sync proxy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:17
+msgid "Adjusting the Sliding Sync proxy URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:19
+msgid "By default, this playbook installs the Sliding Sync proxy on the `matrix.` subdomain, at the `/sliding-sync` path (https://matrix.example.com/sliding-sync). 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-sliding-sync-proxy.md:21
+msgid "By tweaking the `matrix_sliding_sync_hostname` and `matrix_sliding_sync_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-sliding-sync-proxy.md:23
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:31
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:33
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Honoroit domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:35
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:37
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:39
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:41
+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-sliding-sync-proxy.md:48
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:50
+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-sliding-sync-proxy.md:52
+msgid "External databases"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:54
+msgid "Please note that, if your setup utilizes an external database, you must also establish configuration for the sliding sync proxy. Alter the defaults below to suit your configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:64
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:66
+msgid "You **don't need to do anything special** to make use of the Sliding Sync proxy. Simply open your client which supports Sliding Sync (like Element X) and log in."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:68
+msgid "When the Sliding Sync proxy is [installed](#installing), your `/.well-known/matrix/client` file is also updated. A new `org.matrix.msc3575.proxy` section and `url` property are added there and made to point to your Sliding Sync proxy's base URL (e.g. `https://matrix.example.com/sliding-sync`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:70
+msgid "This allows clients which support Sliding Sync to detect the Sliding Sync proxy's URL and make use of it."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po
new file mode 100644
index 000000000..5009ae9dd
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po
@@ -0,0 +1,123 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:1
+msgid "Adjusting SSL certificate retrieval (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:3
+msgid "By default, this playbook retrieves and auto-renews free SSL certificates from [Let's Encrypt](https://letsencrypt.org/) for the domains it needs (e.g. `matrix.example.com` and others)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:5
+msgid "This guide is about using the integrated Traefik server and doesn't apply if you're using [your own webserver](configuring-playbook-own-webserver.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:7
+msgid "Using staging Let's Encrypt certificates instead of real ones"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:9
+msgid "For testing purposes, you may wish to use staging certificates provide by Let's Encrypt."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:11
+#: ../../../docs/configuring-playbook-ssl-certificates.md:21
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:17
+msgid "Disabling SSL termination"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:19
+msgid "For testing or other purposes, you may wish to install services without SSL termination and have services exposed to `http://` instead of `https://`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:27
+msgid "Using self-signed SSL certificates"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:29
+msgid "If you'd like to use your own SSL certificates, instead of the default (SSL certificates obtained automatically via [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) from [Let's Encrypt](https://letsencrypt.org/)):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:31
+msgid "generate your self-signed certificate files"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:32
+msgid "follow the [Using your own SSL certificates](#using-your-own-ssl-certificates) documentation below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:34
+msgid "Using your own SSL certificates"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:36
+msgid "To use your own SSL certificates with Traefik, you need to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:38
+msgid "disable [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) / [Let's Encrypt](https://letsencrypt.org/) support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:39
+msgid "put a custom Traefik configuration file on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:40
+msgid "register your custom configuration file with Traefik, by adding an extra provider of type [file](https://doc.traefik.io/traefik/providers/file/)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:41
+msgid "put the SSL files on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:89
+msgid "Using a DNS-01 ACME challenge type, instead of HTTP-01"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:91
+msgid "You can configure Traefik to use the [DNS-01 challenge type](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) for Let's Encrypt. This is less commonly used than the default [HTTP-01 challenge type](https://letsencrypt.org/docs/challenge-types/#http-01-challenge), but it can be helpful to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:93
+msgid "hide your public IP from Let's Encrypt logs"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:94
+msgid "allow you to obtain SSL certificates for servers which are not accessible (via HTTP) from the public internet (and for which the HTTP-01 challenge would fail)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:96
+msgid "This is an example for how to edit the `vars.yml` file if you're using Cloudflare:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:111
+msgid "Make sure to change the value of \"provider\" to your particular DNS solution, and provide the appropriate environment variables. The full list of supported providers is available [here](https://doc.traefik.io/traefik/https/acme/#providers)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:113
+msgid "This example assumes you're using Cloudflare to manage your DNS zone. Note that it requires the use of two tokens: one for reading all zones (`CF_ZONE_API_TOKEN`) and another that must be able to edit the particular domain you're using (`CF_DNS_API_TOKEN`). For security, it's recommended that you create two fine-grained tokens for this purpose, but you might choose to use the same token for both."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sygnal.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sygnal.po
new file mode 100644
index 000000000..4194057d0
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-sygnal.po
@@ -0,0 +1,134 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-sygnal.md:1
+msgid "Setting up the Sygnal push gateway (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:3
+msgid "The playbook can install and configure the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:5
+msgid "See the project's [documentation](https://github.com/matrix-org/sygnal/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:7
+msgid "**Note**: most people don't need to install their own gateway. As Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) documentation says:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:9
+msgid "It is not feasible to allow end-users to configure their own Sygnal instance, because the Sygnal instance needs the appropriate FCM or APNs secrets that belong to the application."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:11
+msgid "This optional playbook component is only useful to people who develop/build their own Matrix client applications themselves."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:15
+msgid "To enable Sygnal, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:43
+msgid "For a more complete example of available fields and values they can take, see `roles/custom/matrix-sygnal/templates/sygnal.yaml.j2` (or the [upstream `sygnal.yaml.sample` configuration file](https://github.com/matrix-org/sygnal/blob/master/sygnal.yaml.sample))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:45
+msgid "Configuring [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/) is easier, as it only requires that you provide some config values."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:47
+msgid "To configure [APNS](https://developer.apple.com/notifications/) (Apple Push Notification Service), you'd need to provide one or more certificate files. To do that, the above example configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:49
+msgid "makes use of the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) (and its `aux_file_definitions` variable) to make the playbook install files into `/matrix/sygnal/data` (the `matrix_sygnal_data_path` variable). See [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml) of the `aux` role for usage examples. It also makes sure the files are owned by `matrix:matrix`, so that Sygnal can read them. Of course, you can also install these files manually yourself, if you'd rather not use `aux`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:51
+msgid "references these files in the Sygnal configuration (`matrix_sygnal_apps`) using a path like `/data/..` (the `/matrix/sygnal/data` directory on the host system is mounted into the `/data` directory inside the container)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:53
+msgid "Adjusting the Sygnal URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:55
+msgid "By default, this playbook installs Sygnal on the `sygnal.` subdomain (`sygnal.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:57
+msgid "By tweaking the `matrix_sygnal_hostname` and `matrix_sygnal_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-sygnal.md:59
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:70
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:72
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Sygnal domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:74
+msgid "By default, you will need to create a CNAME record for `sygnal`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:76
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:78
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:80
+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-sygnal.md:87
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:89
+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-sygnal.md:91
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:93
+msgid "To make use of your Sygnal installation, you'd need to build your own Matrix client application, which uses the same API keys (for [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/)) and certificates (for [APNS](https://developer.apple.com/notifications/)) and is to your Sygnal URL endpoint (e.g. `https://sygnal.example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:95
+msgid "Refer to Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) document."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po
new file mode 100644
index 000000000..79fa31889
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po
@@ -0,0 +1,126 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:1
+msgid "Setting up Synapse Admin (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:3
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:5
+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://matrix-org.github.io/dendrite/administration/adminapi) differs from [Synapse Admin API](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:7
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:11
+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:17
+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:19
+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:20
+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:22
+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:24
+msgid "⚠️ **Warning**: If you're using [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS) for authentication, you will be able to [log into synapse-admin with an access token](https://github.com/etkecc/synapse-admin/pull/58), but certain synapse-admin features (especially those around user management) will be limited or not work at all."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:26
+msgid "Adjusting the Synapse Admin URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:28
+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:30
+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:32
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:40
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:42
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Synapse Admin domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:44
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:46
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:48
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:50
+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:57
+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:59
+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:61
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:63
+msgid "After installation, Synapse Admin will be accessible at: `https://matrix.example.com/synapse-admin/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:65
+msgid "To use Synapse Admin, you need to have [registered at least one administrator account](registering-users.md) on your server."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po
new file mode 100644
index 000000000..bab4c606a
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po
@@ -0,0 +1,74 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:1
+msgid "Setting up Synapse Auto Invite Accept (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:3
+msgid "The playbook can install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:5
+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:7
+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:9
+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:11
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:13
+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:21
+msgid "Synapse worker deployments"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:23
+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:29
+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:31
+msgid "Native alternative"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:33
+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:35
+msgid "Here's example configuration for using the **native** Synapse feature:"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po
new file mode 100644
index 000000000..df3897dff
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po
@@ -0,0 +1,78 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:1
+msgid "Setting up synapse-auto-compressor (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:3
+msgid "The playbook can install and configure [synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:5
+msgid "It's a CLI tool that automatically compresses Synapse's `state_groups` database table in the background."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:7
+msgid "See the project's [documentation](https://github.com/matrix-org/rust-synapse-compress-state/blob/master/README.md#automated-tool-synapse_auto_compressor) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:11
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:17
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:19
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:26
+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-auto-compressor.md:28
+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-auto-compressor.md:30
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:32
+msgid "After installation, `synapse_auto_compressor` will run automatically every day at `00:00:00` (as defined in `matrix_synapse_auto_compressor_calendar` by default)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:34
+msgid "Manually start the tool"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:36
+msgid "For testing your setup it can be helpful to not wait until 00:00. If you want to run the tool immediately, log onto the server and run `systemctl start matrix-synapse-auto-compressor`. Running this command will not return control to your terminal until the compression run is done, which may take a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po
new file mode 100644
index 000000000..088ddec64
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po
@@ -0,0 +1,258 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:1
+msgid "Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:3
+msgid "If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service), you can use the [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) media provider module for Synapse."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:5
+msgid "An alternative (which has worse performance) is to use [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:7
+msgid "How it works?"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:9
+msgid "Summarized writings here are inspired by [this article](https://quentin.dufour.io/blog/2021-09-14/matrix-synapse-s3-storage/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:11
+msgid "The way media storage providers in Synapse work has some caveats:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:13
+msgid "Synapse still continues to use locally-stored files (for creating thumbnails, serving files, etc)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:14
+msgid "the media storage provider is just an extra storage mechanism (in addition to the local filesystem)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:15
+msgid "all files are stored locally at first, and then copied to the media storage provider (either synchronously or asynchronously)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:16
+msgid "if a file is not available on the local filesystem, it's pulled from a media storage provider"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:18
+msgid "You may be thinking **if all files are stored locally as well, what's the point**?"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:20
+msgid "You can run some scripts to delete the local files once in a while (which we do automatically by default - see [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem)), thus freeing up local disk space. If these files are needed in the future (for serving them to users, etc.), Synapse will pull them from the media storage provider on demand."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:22
+msgid "While you will need some local disk space around, it's only to accommodate usage, etc., and won't grow as large as your S3 store."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:24
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:26
+msgid "After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), you can proceed to configure `s3-storage-provider` in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:50
+msgid "If you have existing files in Synapse's media repository (`/matrix/synapse/media-store/..`):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:52
+msgid "new files will start being stored both locally and on the S3 store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:53
+msgid "the existing files will remain on the local filesystem only until [migrating them to the S3 store](#migrating-your-existing-media-files-to-the-s3-store)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:54
+msgid "at some point (and periodically in the future), you can delete local files which have been uploaded to the S3 store already"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:56
+msgid "Regardless of whether you need to [Migrate your existing files to the S3 store](#migrating-your-existing-media-files-to-the-s3-store) or not, make sure you've familiarized yourself with [How it works?](#how-it-works) above and [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem) below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:58
+msgid "Migrating your existing media files to the S3 store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:60
+msgid "Migrating your existing data can happen in multiple ways:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:62
+msgid "[using the `s3_media_upload` script from `synapse-s3-storage-provider`](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (very slow when dealing with lots of data)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:63
+msgid "[using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload) (quicker when dealing with lots of data)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:65
+msgid "Using the `s3_media_upload` script from `synapse-s3-storage-provider`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:67
+msgid "Instead of using `s3_media_upload` directly, which is very slow and painful for an initial data migration, we recommend [using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:69
+msgid "To copy your existing files, SSH into the server and run `/matrix/synapse/ext/s3-storage-provider/bin/shell`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:71
+msgid "This launches a Synapse container, which has access to the local media store, Postgres database, S3 store and has some convenient environment variables configured for you to use (`MEDIA_PATH`, `BUCKET`, `ENDPOINT`, `UPDATE_DB_DAYS`, etc)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:73
+msgid "Then use the following commands (`$` values come from environment variables - they're **not placeholders** that you need to substitute):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:75
+msgid "`s3_media_upload update-db $UPDATE_DB_DURATION` - create a local SQLite database (`cache.db`) with a list of media repository files (from the `synapse` Postgres database) eligible for operating on"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:76
+msgid "`$UPDATE_DB_DURATION` is influenced by the `matrix_synapse_ext_synapse_s3_storage_provider_update_db_day_count` variable (defaults to `0`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:77
+msgid "`$UPDATE_DB_DURATION` defaults to `0d` (0 days), which means **include files which haven't been accessed for more than 0 days** (that is, **all files will be included**)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:78
+msgid "`s3_media_upload check-deleted $MEDIA_PATH` - check whether files in the local cache still exist in the local media repository directory"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:79
+msgid "`s3_media_upload upload $MEDIA_PATH $BUCKET --delete --storage-class $STORAGE_CLASS --endpoint-url $ENDPOINT` - uploads locally-stored files to S3 and deletes them from the local media repository directory"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:81
+msgid "The `s3_media_upload upload` command may take a lot of time to complete."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:83
+msgid "Instead of running the above commands manually in the shell, you can also run the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script which will run the same commands automatically. We demonstrate how to do it manually, because:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:85
+msgid "it's what the upstream project demonstrates and it teaches you how to use the `s3_media_upload` tool"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:86
+msgid "allows you to check and verify the output of each command, to catch mistakes"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:87
+msgid "includes progress bars and detailed output for each command"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:88
+msgid "allows you to easily interrupt slow-running commands, etc. (the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container without interactive TTY support, so `Ctrl+C` may not work and you and require killing via `docker kill ..`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:90
+msgid "Using another tool in combination with `s3_media_upload`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:92
+msgid "To migrate your existing local data to S3, we recommend to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:94
+msgid "**first** use another tool ([`aws s3`](#copying-data-to-amazon-s3) or [`b2 sync`](#copying-data-to-backblaze-b2), etc.) to copy the local files to the S3 bucket"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:96
+msgid "**only then** [use the `s3_media_upload` tool to finish the migration](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (this checks to ensure all files are uploaded and then deletes the local files)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:98
+msgid "Copying data to Amazon S3"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:100
+msgid "To copy to AWS S3, start a container on the Matrix server like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:112
+msgid "Copying data to an S3 alternative using the aws-s3 tool"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:114
+msgid "To copy to a provider other than AWS S3 (e.g. Wasabi, Digital Ocean Spaces, etc.), you can use the command for [Copying data to Amazon S3](#copying-data-to-amazon-s3) with an added `--endpoint-url=$ENDPOINT` argument."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:116
+msgid "Add this argument to the command **as-is** (`$ENDPOINT` is an environment variable corresponding to `matrix_synapse_ext_synapse_s3_storage_provider_config_endpoint_url`, so you don't need to touch it). Make sure to add the argument **before** the final quote (`'`) of the command."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:118
+msgid "Copying data to Backblaze B2"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:120
+msgid "You can copy files to Backblaze B2 either by following the [Copying data to an S3 alternative using the aws-s3 tool](#copying-data-to-an-s3-alternative-using-the-aws-s3-tool) or by using the B2-specific [b2 command-line tool](https://www.backblaze.com/b2/docs/quick_command_line.html) as described below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:122
+msgid "To copy the data using the `b2` tool, start a container on the Matrix server like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:136
+msgid "Periodically cleaning up the local filesystem"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:138
+msgid "As described in [How it works?](#how-it-works) above, when new media is uploaded to the Synapse homeserver, it's first stored locally and then also stored on the remote S3 storage."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:140
+msgid "By default, we periodically ensure that all local files are uploaded to S3 and are then removed from the local filesystem. This is done automatically using:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:142
+msgid "the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:143
+msgid ".. invoked via the `matrix-synapse-s3-storage-provider-migrate.service` service"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:144
+msgid ".. triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` timer, every day at 05:00"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:146
+msgid "So.. you don't need to perform any maintenance yourself."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po
new file mode 100644
index 000000000..d4be5dc5e
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po
@@ -0,0 +1,46 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:1
+msgid "Setting up Synapse Simple Antispam (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:3
+msgid "The playbook can install and configure [synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:5
+msgid "It lets you fight invite-spam by automatically blocking invitiations from a list of servers specified by you (blacklisting)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:7
+msgid "See the project's [documentation](https://github.com/t2bot/synapse-simple-antispam/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:11
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po
new file mode 100644
index 000000000..6cf2793d2
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po
@@ -0,0 +1,110 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:1
+msgid "Enabling synapse-usage-exporter for Synapse usage statistics (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:3
+msgid "[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) allows you to export the usage statistics of a Synapse homeserver to this container service and for the collected metrics to later be scraped by Prometheus."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:5
+msgid "Synapse does not include usage statistics in its Prometheus metrics. They can be reported to an HTTP `PUT` endpoint 5 minutes after startup and from then on at a fixed interval of once every three hours. This role integrates a simple [Flask](https://flask.palletsprojects.com) project that offers an HTTP `PUT` endpoint and holds the most recent received record available to be scraped by Prometheus."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:7
+msgid "Enabling this service will automatically:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:9
+msgid "install the synapse-usage-exporter service"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:10
+msgid "re-configure Synapse to push (via HTTP `PUT`) usage statistics information to synapse-usage-exporter"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:11
+msgid "re-configure [Prometheus](./configuring-playbook-prometheus-grafana.md) (if Prometheus is enabled), to periodically scrape metrics from synapse-usage-exporter"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:12
+msgid "add a new [Grafana](./configuring-playbook-prometheus-grafana.md) dashboard (if Grafana is enabled) containing Synapse usage statistics"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:14
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:16
+msgid "To enable synapse-usage-exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:28
+msgid "Adjusting the synapse-usage-exporter URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:30
+msgid "By default, this playbook installs synapse-usage-exporter on the `matrix.` subdomain, at the `/report-usage-stats/push` path (https://matrix.example.com/report-usage-stats/push). 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-usage-exporter.md:32
+msgid "By tweaking the `matrix_synapse_usage_exporter_hostname` and `matrix_synapse_usage_exporter_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-usage-exporter.md:34
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:43
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:45
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the synapse-usage-exporter domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:47
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:49
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:51
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:53
+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-usage-exporter.md:60
+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-usage-exporter.md:62
+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 ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse.po
new file mode 100644
index 000000000..423c85fd5
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse.po
@@ -0,0 +1,259 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-synapse.md:1
+msgid "Configuring Synapse (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:3
+msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, so that it works for the general case. If that's okay, you can skip this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:5
+msgid "The playbook provides lots of customization variables you could use to change Synapse's settings."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:7
+msgid "Their defaults are defined in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml) and they ultimately end up in the generated `/matrix/synapse/config/homeserver.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2`](../roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2) template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:9
+msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:11
+msgid "Alternatively, **if there is no pre-defined variable** for a Synapse setting you wish to change:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:13
+msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Synapse's various settings that rarely get used."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:15
+msgid "or, you can **extend and override the default configuration** ([`homeserver.yaml.j2`](../roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2)) by making use of the `matrix_synapse_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:17
+msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`). You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:19
+msgid "Load balancing with workers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:21
+msgid "To have Synapse gracefully handle thousands of users, worker support should be enabled. It factors out some homeserver tasks and spreads the load of incoming client and server-to-server traffic between multiple processes. More information can be found in the [official Synapse workers documentation](https://github.com/element-hq/synapse/blob/master/docs/workers.md) and [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:23
+msgid "To enable Synapse worker support, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:31
+msgid "By default, this enables the `one-of-each` [worker preset](#worker-presets), but you may wish to use another preset or [control the number of worker instances](#controlling-the-number-of-worker-instances)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:33
+msgid "Worker presets"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:35
+msgid "We support a few configuration presets (`matrix_synapse_workers_preset: one-of-each` being the default configuration right now):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:37
+msgid "(federation-only) `little-federation-helper` - a very minimal worker configuration to improve federation performance"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:38
+msgid "(generic) `one-of-each` - defaults to one worker of each supported type - no smart routing, just generic workers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:39
+msgid "(specialized) `specialized-workers` - defaults to one worker of each supported type, but disables generic workers and uses [specialized workers](#specialized-workers) instead"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:41
+msgid "These presets represent a few common configurations. There are many worker types which can be mixed and matched based on your needs."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:43
+msgid "Generic workers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:45
+msgid "Previously, the playbook only supported the most basic type of load-balancing. We call it **generic load-balancing** below, because incoming HTTP requests are sent to a generic worker. Load-balancing was done based on the requestor's IP address. This is simple, but not necessarily optimal. If you're accessing your account from multiple IP addresses (e.g. your mobile phone being on a different network than your PC), these separate requests may potentially be routed to different workers, each of which would need to cache roughly the same data."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:47
+msgid "This is **still the default load-balancing method (preset) used by the playbook**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:49
+msgid "To use generic load-balancing, do not specify `matrix_synapse_workers_preset` to make it use the default value (`one-of-each`), or better yet - explicitly set it as `one-of-each`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:51
+msgid "You may also consider [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:53
+msgid "Specialized workers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:55
+msgid "The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requestor's IP adddress, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** - the access token (username) of the requestor and/or on the resource (room, etc.) being requested."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:57
+msgid "The playbook supports these **4 types** of specialized workers:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:59
+msgid "Room workers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) & [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs dedicated to handling specific rooms"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:60
+msgid "Sync workers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to synchronization (most notably [the `/sync` endpoint](https://spec.matrix.org/v1.9/client-server-api/#get_matrixclientv3sync))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:61
+msgid "Client readers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are not for specific rooms (handled by **room workers**) or for synchronization (handled by **sync workers**)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:62
+msgid "Federation readers - handles various [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which are not for specific rooms (handled by **room workers**)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:64
+msgid "To use specialized load-balancing, consider enabling the `specialized-workers` [worker preset](#worker-presets) and potentially [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:66
+msgid "Controlling the number of worker instances"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:68
+msgid "If you'd like more customization power, you can start with one of the [worker presets](#worker-presets) and then tweak various `matrix_synapse_workers_*_count` variables manually."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:70
+msgid "To find what variables are available for you to override in your own `vars.yml` configuration file, see the [`defaults/main.yml` file for the `matrix-synapse` Ansible role](../roles/custom/matrix-synapse/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:72
+msgid "The only thing you **cannot** do is mix [generic workers](#generic-workers) and [specialized workers](#specialized-workers)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:74
+msgid "Effect of enabling workers on the rest of your server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:76
+msgid "When Synapse workers are enabled, the integrated [Postgres database is tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum number of Postgres connections are increased from `200` to `500`. If you need to decrease or increase the number of maximum Postgres connections further, use the `postgres_max_connections` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:78
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:80
+msgid "In case any problems occur, make sure to have a look at the [list of synapse issues about workers](https://github.com/element-hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit 'matrix-*'`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:82
+msgid "Synapse Admin"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:84
+msgid "Certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace, if you install [Synapse Admin](configuring-playbook-synapse-admin.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:86
+msgid "Synapse + OpenID Connect for Single-Sign-On"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:88
+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:90
+msgid "If you'd like to use OpenID Connect authentication with Synapse, you'll need some additional configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:92
+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:94
+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:96
+#, python-format
+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:117
+msgid "Customizing templates"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:119
+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:121
+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:123
+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:125
+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:127
+msgid "To enable template customizations, use a configuration (`inventory/host_vars/matrix.example.com/vars.yml`) like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:153
+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:155
+msgid "Monitoring Synapse Metrics with Prometheus and Grafana"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:157
+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:159
+msgid "To enable Synapse runtime metrics see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:161
+msgid "To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-telemetry.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-telemetry.po
new file mode 100644
index 000000000..e2736973a
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-telemetry.po
@@ -0,0 +1,54 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-telemetry.md:1
+msgid "Enabling Telemetry for your Matrix server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:3
+msgid "By default, this playbook configures your Matrix homeserver to not send any telemetry data anywhere."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:5
+msgid "The [matrix.org](https://matrix.org) team would really appreciate it if you could help the project out by reporting usage statistics from your homeserver. Enabling usage statistics helps track the growth of the Matrix community, and helps to make Matrix a success."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:7
+msgid "Enabling Telemetry"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:9
+msgid "If you'd like to **help by enabling submission of general usage statistics** for your homeserver, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:17
+msgid "Usage statistics being submitted"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:19
+msgid "When enabled, your homeserver will regularly upload a few dozen statistics about your server. This data includes your homeserver's domain, the total number of users, the number of active users, the total number of rooms, and the number of messages sent per day on your homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:21
+msgid "See [Synapse's documentation](https://github.com/element-hq/synapse/blob/develop/docs/usage/administration/monitoring/reporting_homeserver_usage_statistics.md#available-statistics) or [Dendrite's documentation](https://github.com/matrix-org/dendrite/blob/main/docs/FAQ.md#what-is-being-reported-when-enabling-phone-home-statistics) for the full list of statistics that are reported."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-traefik.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-traefik.po
new file mode 100644
index 000000000..f33124d44
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-traefik.po
@@ -0,0 +1,139 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-traefik.md:1
+msgid "Configuring the Traefik reverse-proxy (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:3
+msgid "By default, this playbook installs and manages a [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered by the [ansible-role-traefik](https://github.com/mother-of-all-self-hosting/ansible-role-traefik) Ansible role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:5
+msgid "This Ansible role support various configuration options. Feel free to consult its `default/main.yml` variables file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:7
+msgid "Adjusting SSL certificate retrieval"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:9
+msgid "See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:11
+msgid "Increase logging verbosity"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:17
+msgid "Disable access logs"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:19
+msgid "This will disable access logging."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:25
+msgid "Enable Traefik Dashboard"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:27
+msgid "This will enable a Traefik [Dashboard](https://doc.traefik.io/traefik/operations/dashboard/) UI at `https://matrix.example.com/dashboard/` (note the trailing `/`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:37
+msgid "**WARNING**: Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:39
+msgid "Additional configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:41
+msgid "Use the `traefik_configuration_extension_yaml` variable provided by the Traefik Ansible role to override or inject additional settings, even when no dedicated variable exists."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:51
+msgid "Reverse-proxying another service behind Traefik"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:53
+msgid "The preferred way to reverse-proxy additional services behind Traefik would be to start the service as another container, configure the container with the corresponding Traefik [container labels](https://docs.docker.com/config/labels-custom-metadata/) (see [Traefik & Docker](https://doc.traefik.io/traefik/routing/providers/docker/)), and connect the service to the `traefik` network. Some services are also already available via the compatible [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook), but take a look at the minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:55
+msgid "However, if your service does not run on a container or runs on another machine, the following configuration might be what you are looking for."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:57
+msgid "Reverse-proxying a remote HTTP/HTTPS service behind Traefik"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:59
+msgid "If you want to host another webserver would be reachable via `my-fancy-website.example.net` from the internet and via `https://<internal webserver IP address>:<internal port>` from inside your network, you can make the playbook's integrated Traefik instance reverse-proxy the traffic to the correct host."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:61
+msgid "Prerequisites: DNS and routing for the domain `my-fancy-website.example.net` need to be set up correctly. In this case, you'd be pointing the domain name to your Matrix server - `my-fancy-website.example.net` would be a CNAME going to `matrix.example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:63
+msgid "First, we have to adjust the static configuration of Traefik, so that we can add additional configuration files:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:77
+msgid "If you are using a self-signed certificate on your webserver, you can tell Traefik to trust your own backend servers by adding more configuration to the static configuration file. If you do so, bear in mind the security implications of disabling the certificate validity checks towards your back end."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:91
+msgid "Next, you have to add a new dynamic configuration file for Traefik that contains the actual information of the server using the `aux_file_definitions` variable. In this example, we will terminate SSL at the Traefik instance and connect to the other server via HTTPS. Traefik will now take care of managing the certificates."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:110
+#: ../../../docs/configuring-playbook-traefik.md:133
+msgid "Changing the `url` to one with an `http://` prefix would allow to connect to the server via HTTP."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:112
+msgid "Reverse-proxying another service behind Traefik without terminating SSL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:114
+msgid "If you do not want to terminate SSL at the Traefik instance (for example, because you're already terminating SSL at other webserver), you need to adjust the static configuration in the same way as in the previous chapter in order to be able to add our own dynamic configuration files. Afterwards, you can add the following configuration to your `vars.yml` configuration file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:135
+msgid "With these changes, all TCP traffic will be reverse-proxied to the target system."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:137
+msgid "**WARNING**: This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:139
+msgid "Traefik behind a `proxy_protocol` reverse-proxy"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:141
+msgid "If you run a reverse-proxy which speaks `proxy_protocol`, add the following to your configuration file:"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-turn.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-turn.po
new file mode 100644
index 000000000..8fbfe1733
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-turn.po
@@ -0,0 +1,110 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-turn.md:1
+msgid "Adjusting TURN server configuration (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:3
+msgid "The playbook installs a [Coturn](https://github.com/coturn/coturn) TURN server by default, so that clients can make audio/video calls even from [NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed networks."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:5
+msgid "By default, the Synapse chat server is configured, so that it points to the Coturn TURN server installed by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:7
+msgid "Disabling Coturn"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:9
+msgid "If, for some reason, you'd like to prevent the playbook from installing Coturn, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:15
+msgid "In that case, Synapse would not point to any Coturn servers and audio/video call functionality may fail."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:17
+msgid "Manually defining your public IP"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:19
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:21
+msgid "If you'd rather use a local IP for `ansible_host`, make sure to set up `matrix_coturn_turn_external_ip_address` replacing `YOUR_PUBLIC_IP` with the pubic IP used by the server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:27
+msgid "If you'd like to rely on external IP address auto-detection (not recommended unless you need it), set `matrix_coturn_turn_external_ip_address` to an empty value. 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 `matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:29
+msgid "If your server has multiple external IP addresses, the Coturn role offers a different variable for specifying them:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:36
+msgid "Changing the authentication mechanism"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:38
+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:40
+msgid "To do so, add this override to your configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:46
+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:48
+msgid "If you're using [Jitsi](./configuring-playbook-jitsi.md), note that switching to `lt-cred-mech` will remove the integration between Jitsi and your own Coturn server, because Jitsi only seems to support the `auth-secret` authentication method."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:50
+msgid "Using your own external Coturn server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:52
+msgid "If you'd like to use another TURN server (be it Coturn or some other one), you can configure the playbook like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:66
+msgid "If you have or want to enable [Jitsi](configuring-playbook-jitsi.md), 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:72
+msgid "You can put multiple host/port combinations if you like."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:74
+msgid "Further variables and configuration options"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:75
+msgid "To see all the available configuration options, check roles/custom/matrix-coturn/defaults/main.yml"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po
new file mode 100644
index 000000000..25c018878
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po
@@ -0,0 +1,218 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:1
+msgid "Setting up Matrix User Verification Service (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:3
+msgid "**[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (hereafter: UVS) can only be installed after Matrix services are installed and running.** If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) flow and come back here later."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:5
+msgid "Currently, the main purpose of this role is to allow Jitsi to authenticate Matrix users and check if they are authorized to join a conference. Please refer to the documentation of the [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) to understand how it works."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:7
+msgid "**Note**: enabling Matrix User Verification Service, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:9
+msgid "If the Jitsi server is also configured by this playbook, all plugging of variables and secrets is handled in `group_vars/matrix_servers`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:11
+msgid "__Some general concepts of UVS may be helpful to understand the rest, so here they are:__"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:13
+msgid "UVS can be used to verify two claims:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:15
+msgid "(A) Whether a given OpenID token is valid for a given server and"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:16
+msgid "(B) whether a user is member of a given room and the corresponding PowerLevel"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:18
+msgid "Verifying an OpenID token ID done by finding the corresponding Homeserver via  '.well-known/matrix/server' for the given domain. The configured `matrix_user_verification_service_uvs_homeserver_url` does **not** factor into this. By default, this playbook only checks against `matrix_server_fqn_matrix`. Therefore, the request will be made against the public openid API for `matrix_server_fqn_matrix`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:20
+msgid "Verifying RoomMembership and PowerLevel is done against `matrix_user_verification_service_uvs_homeserver_url` which is by default done via the docker network. UVS will verify the validity of the token beforehand though."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:22
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:24
+msgid "In order to use UVS, an admin token for the configured homeserver must be supplied. For now this means configuring Synapse and creating the token before installing UVS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:26
+msgid "Enable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:28
+msgid "To enable Matrix User Verification Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:34
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:36
+msgid "The only required configuration variable is `matrix_user_verification_service_uvs_access_token` (see below)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:38
+msgid "For a list of all configuration options see the role defaults [`roles/matrix-user-verification-service/defaults/main.yml`](../roles/custom/matrix-user-verification-service/defaults/main.yml). But be aware of all the plugging happening in `group_vars/matrix_servers`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:40
+msgid "In the default configuration, the UVS Server is only reachable via the docker network, which is fine if e.g. Jitsi is also running in a container on the host. However, it is possible to expose UVS via setting `matrix_user_verification_service_container_http_host_bind_port`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:42
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:44
+msgid "The Synapse Access Token is used to verify RoomMembership and PowerLevel against `matrix_user_verification_service_uvs_homeserver_url`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:46
+msgid "We recommend that you create a dedicated Matrix user for uvs (`uvs` is a good username). Follow our [Registering users](registering-users.md) guide to register a user with administration privileges."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:48
+msgid "You are required to specify an access token (belonging to this new user) for UVS to work. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:50
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:56
+msgid "Custom Auth Token (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:58
+msgid "It is possible to set an API Auth Token to restrict access to the UVS. If this is enabled, anyone making a request to UVS must provide it via the header \"Authorization: Bearer TOKEN\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:60
+msgid "By default, the token will be derived from `matrix_homeserver_generic_secret_key` in `group_vars/matrix_servers`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:62
+msgid "To set your own Token, add the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:68
+msgid "In case Jitsi is also managed by this playbook and 'matrix' authentication in Jitsi is enabled, this collection will automatically configure Jitsi to use the configured auth token."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:70
+msgid "Disable Auth (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:72
+msgid "Authorization is enabled by default. To disable it, add the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:78
+msgid "Federation (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:80
+msgid "In theory (however currently untested), UVS can handle federation. To enable it, add the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:86
+msgid "This will instruct UVS to verify the OpenID token against any domain given in a request. Homeserver discovery is done via '.well-known/matrix/server' of the given domain."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:88
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:90
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:97
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service matrix-user-verification-service` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:99
+msgid "`just install-service matrix-user-verification-service` is useful for maintaining your setup quickly 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 `just setup-all` runs the `ensure-matrix-users-created` tag too."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:101
+msgid "Logging"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:103
+msgid "The configuration variable `UVS_LOG_LEVEL` can be set to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:104
+msgid "warning"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:105
+msgid "info"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:106
+msgid "debug"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:108
+msgid "TLS Certificate Checking"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:110
+msgid "If the Matrix Homeserver does not provide a valid TLS certificate, UVS will fail with the following error message:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:112
+msgid "message: 'No response received: [object Object]',"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:114
+msgid "This also applies to self-signed and let's encrypt staging certificates."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:116
+msgid "To disable certificate validation altogether (INSECURE! Not suitable for production use!) set: `NODE_TLS_REJECT_UNAUTHORIZED=0`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:118
+msgid "Alternatively, it is possible to inject your own CA certificates into the container by mounting a PEM file with additional trusted CAs into the container and pointing the `NODE_EXTRA_CA_CERTS` environment variable to it."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook.po
new file mode 100644
index 000000000..f75851e6b
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook.po
@@ -0,0 +1,534 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook.md:1
+msgid "Configuring the playbook"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:3
+msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md)</sup>"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:5
+msgid "If you've configured your DNS records and retrieved the playbook's source code to your computer, you can start configuring the playbook. To do so, follow these steps inside the playbook directory:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:7
+msgid "create a directory to hold your configuration (`mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\")"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:9
+msgid "copy the sample configuration file (`cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:11
+msgid "edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You may also take a look at the various `roles/*/ROLE_NAME_HERE/defaults/main.yml` files and see if there's something you'd like to copy over and override in your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:13
+msgid "copy the sample inventory hosts file (`cp examples/hosts inventory/hosts`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:15
+msgid "edit the inventory hosts file (`inventory/hosts`) to your liking"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:17
+msgid "(optional, advanced) you may wish to keep your `inventory` directory under version control with [git](https://git-scm.com/) or any other version-control system."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:19
+msgid "(optional, advanced) to run Ansible against multiple servers with different `sudo` credentials, you can copy the sample inventory hosts yaml file for each of your hosts: (`cp examples/host.yml inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin/ansible-all-hosts.sh) script [in the installation step](installing.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:21
+msgid "For a basic Matrix installation, that's all you need."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:23
+msgid "For a more custom setup, see the [Other configuration options](#other-configuration-options) below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:25
+msgid "[▶️](installing.md) When you're done with all the configuration you'd like to do, continue with [Installing](installing.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:27
+msgid "Other configuration options"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:29
+msgid "Core service adjustments"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:31
+msgid "Homeserver configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:32
+msgid "[Configuring Synapse](configuring-playbook-synapse.md), if you're going with the default/recommended homeserver implementation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:34
+msgid "[Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:36
+msgid "[Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:38
+msgid "Server components:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:39
+msgid "[Using an external PostgreSQL server](configuring-playbook-external-postgres.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:41
+msgid "[Adjusting TURN server configuration](configuring-playbook-turn.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:43
+msgid "[Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:45
+msgid "[Using your own webserver, instead of this playbook's Traefik reverse-proxy](configuring-playbook-own-webserver.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:47
+msgid "[Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:49
+msgid "[Adjusting email-sending settings](configuring-playbook-email.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:51
+msgid "[Setting up ma1sd Identity Server](configuring-playbook-ma1sd.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:53
+msgid "[Setting up Dynamic DNS](configuring-playbook-dynamic-dns.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:55
+msgid "Server connectivity:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:56
+msgid "[Enabling Telemetry for your Matrix server](configuring-playbook-telemetry.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:58
+msgid "[Controlling Matrix federation](configuring-playbook-federation.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:60
+msgid "Clients"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:62
+msgid "Web clients for Matrix that you can host on your own domains."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:64
+msgid "[Configuring Element Web](configuring-playbook-client-element-web.md), if you're going with the default/recommended client"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:66
+msgid "[Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a lightweight Matrix client with legacy and mobile browser support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:68
+msgid "[Setting up Cinny](configuring-playbook-client-cinny.md), if you've enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing primarily on simple, elegant and secure interface"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:70
+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:72
+msgid "Authentication and user-related"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:74
+msgid "Extend and modify how users are authenticated on your homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:76
+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:78
+msgid "[Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:80
+msgid "[Setting up Synapse Admin](configuring-playbook-synapse-admin.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:82
+msgid "[Setting up matrix-registration](configuring-playbook-matrix-registration.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:84
+msgid "[Setting up the REST authentication password provider module](configuring-playbook-rest-auth.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:86
+msgid "[Setting up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:88
+msgid "[Setting up the LDAP authentication password provider module](configuring-playbook-ldap-auth.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:90
+msgid "[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:92
+msgid "[Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:94
+msgid "[Setting up Matrix User Verification Service](configuring-playbook-user-verification-service.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:96
+msgid "File Storage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:98
+msgid "Use alternative file storage to the default `media_store` folder."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:100
+msgid "[Storing Matrix media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:102
+msgid "[Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:104
+msgid "[Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:106
+msgid "Bridging other networks"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:108
+msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:110
+msgid "[Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:112
+msgid "[Setting up Mautrix Telegram bridging](configuring-playbook-bridge-mautrix-telegram.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:114
+msgid "[Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:116
+msgid "[Setting up Mautrix Google Messages bridging](configuring-playbook-bridge-mautrix-gmessages.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:118
+msgid "[Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-mautrix-whatsapp.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:120
+msgid "[Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:122
+msgid "[Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:124
+msgid "[Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-mautrix-googlechat.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:126
+msgid "[Setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:128
+msgid "[Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-signal.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:130
+msgid "[Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](configuring-playbook-bridge-mautrix-wsproxy.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:132
+msgid "[Setting up Appservice IRC bridging](configuring-playbook-bridge-appservice-irc.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:134
+msgid "[Setting up Appservice Discord bridging](configuring-playbook-bridge-appservice-discord.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:136
+msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:138
+msgid "[Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-appservice-kakaotalk.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:140
+msgid "[Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-linkedin.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:142
+msgid "[Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) - a bridge between Matrix and multiple project management services, such as [GitHub](https://github.com), [GitLab](https://about.gitlab.com) and [JIRA](https://www.atlassian.com/software/jira)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:144
+msgid "[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:146
+msgid "[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-puppet-instagram.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:148
+msgid "[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:150
+msgid "[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-puppet-discord.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:152
+msgid "[Setting up MX Puppet GroupMe bridging](configuring-playbook-bridge-mx-puppet-groupme.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:154
+msgid "[Setting up MX Puppet Steam bridging](configuring-playbook-bridge-mx-puppet-steam.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:156
+msgid "[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:158
+msgid "[Setting up Email2Matrix](configuring-playbook-email2matrix.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:160
+msgid "[Setting up Postmoogle email bridging](configuring-playbook-bridge-postmoogle.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:162
+msgid "[Setting up Matrix SMS bridging](configuring-playbook-bridge-matrix-bridge-sms.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:164
+msgid "[Setting up Heisenbridge bouncer-style IRC bridging](configuring-playbook-bridge-heisenbridge.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:166
+msgid "[Setting up WeChat bridging](configuring-playbook-bridge-wechat.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:168
+msgid "Bots"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:170
+msgid "Bots provide various additional functionality to your installation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:172
+msgid "[Setting up baibot](configuring-playbook-bot-baibot.md) - a bot through which you can talk to various [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) services ([OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) and [others](https://github.com/etkecc/baibot/blob/main/docs/providers.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:174
+msgid "[Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md) - a bot to remind you about stuff"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:176
+msgid "[Setting up matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) - a bot to create and manage registration tokens to invite users"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:178
+msgid "[Setting up maubot](configuring-playbook-bot-maubot.md) - a plugin-based Matrix bot system"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:180
+msgid "[Setting up Honoroit](configuring-playbook-bot-honoroit.md) - a helpdesk bot"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:182
+msgid "[Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) - a moderation tool/bot"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:184
+msgid "[Setting up Draupnir](configuring-playbook-bot-draupnir.md) - a moderation tool/bot, forked from Mjolnir and maintained by its former leader developer"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:186
+msgid "[Setting up Draupnir for all/D4A](configuring-playbook-appservice-draupnir-for-all.md) - like the [Draupnir bot](configuring-playbook-bot-draupnir.md) mentioned above, but running in appservice mode and supporting multiple instances"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:188
+msgid "[Setting up Buscarron](configuring-playbook-bot-buscarron.md) - a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:190
+msgid "Administration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:192
+msgid "Services that help you in administrating and monitoring your Matrix installation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:194
+msgid "[Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:196
+msgid "[Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:198
+msgid "[Enabling metrics and graphs for NginX logs](configuring-playbook-prometheus-nginxlog.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:200
+msgid "[Setting up the rageshake bug report server](configuring-playbook-rageshake.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:202
+msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:204
+msgid "Backups:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:205
+msgid "[Setting up BorgBackup](configuring-playbook-backup-borg.md) - a full Matrix server backup solution, including the Postgres database"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:207
+msgid "[Setting up postgres backup](configuring-playbook-postgres-backup.md) - a Postgres-database backup solution (note: does not include other files)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:209
+msgid "Other specialized services"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:211
+msgid "Various services that don't fit any other categories."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:213
+msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:215
+msgid "[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:217
+msgid "[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:219
+msgid "[Setting up Etherpad](configuring-playbook-etherpad.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:221
+msgid "[Setting up the Jitsi video-conferencing platform](configuring-playbook-jitsi.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:223
+msgid "[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) - a federated comment system built on Matrix"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:225
+msgid "[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-pantalaimon.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:227
+msgid "[Setting up the Sygnal push gateway](configuring-playbook-sygnal.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:229
+msgid "[Setting up the ntfy push notifications server](configuring-playbook-ntfy.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:231
+msgid "Deprecated / unmaintained / removed services"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:233
+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:235
+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:237
+msgid "[Setting up Appservice Webhooks bridging](configuring-playbook-bridge-appservice-webhooks.md) (deprecated; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:239
+msgid "[Setting up the Dimension integration manager](configuring-playbook-dimension.md) ([unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299); after [installing](installing.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:241
+msgid "[Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:243
+msgid "[Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) (unmaintained; the bridge's author suggests taking a look at [baibot](https://github.com/etkecc/baibot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bot-baibot.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:245
+msgid "[Setting up Mautrix Facebook bridging](configuring-playbook-bridge-mautrix-facebook.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-messenger](configuring-playbook-bridge-mautrix-meta-messenger.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:247
+msgid "[Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-mautrix-hangouts.md) (deprecated in favor of the Google Chat bridge with [mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:249
+msgid "[Setting up Mautrix Instagram bridging](configuring-playbook-bridge-mautrix-instagram.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-instagram](configuring-playbook-bridge-mautrix-meta-instagram.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:251
+msgid "[Setting up MX Puppet Skype bridging](configuring-playbook-bridge-mx-puppet-skype.md) (removed; this component has been broken for a long time, so it has been removed from the playbook. Consider [setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md))"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po b/i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po
new file mode 100644
index 000000000..9711ff1b9
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/configuring-well-known.po
@@ -0,0 +1,254 @@
+# Translations template for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\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"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-well-known.md:1
+msgid "Configuring Service Discovery via .well-known"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:3
+msgid "This documentation page explains how to configure Service discovery via `/.well-known/` files. Service discovery is a way for the Matrix network to discover where a Matrix server is."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:5
+msgid "Types of well-known service discovery mechanism"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:7
+msgid "There are 3 types of well-known service discovery mechanism that Matrix makes use of:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:9
+msgid "(important) **Federation Server discovery** (`/.well-known/matrix/server`) -- assists other servers in the Matrix network with finding your server. With the default playbook configuration specified on the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), this is necessary for federation to work. Without a proper configuration, your server will effectively not be part of the Matrix network."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:11
+msgid "(less important) **Client Server discovery** (`/.well-known/matrix/client`) -- assists programs that you use to connect to your server (e.g. Element Web), so that they can make it more convenient for you by automatically configuring the \"Homeserver URL\" and \"Identity Server URL\" addresses."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:13
+msgid "(optional) **Support service discovery** (`/.well-known/matrix/support`) -- returns server admin contact and support page of the domain."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:15
+msgid "Federation Server Discovery"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:17
+msgid "All services created by this playbook are meant to be installed on their own server (such as `matrix.example.com`), instead of the base domain (`example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:19
+msgid "As [per the Server-Server specification](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), in order to use a short Matrix user ID like `@alice:example.com` instead of `@alice:matrix.example.com` while hosting services on a subdomain such as `matrix.example.com`, the Matrix network needs to be instructed of [server delegation](howto-server-delegation.md) / redirection."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:21
+msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:23
+msgid "If you set up the DNS SRV record for server delegation instead, take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:25
+msgid "Client Server Discovery"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:27
+msgid "Client Server Service discovery lets various client programs which support it, to receive a full user ID (e.g. `@alice:example.com`) and determine where the Matrix server is automatically (e.g. `https://matrix.example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:29
+msgid "This lets you (and your users) easily connect to your Matrix server without having to customize connection URLs. When using client programs that support it, you won't need to point them to `https://matrix.example.com` in Custom Server options manually anymore. The connection URL would be discovered automatically from your full username."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:31
+msgid "Without /.well-known/matrix/client, the client will make the wrong \"homeserver URL\" assumption (it will default to using https://example.com, and users will need to notice and adjust it manually (changing it to https://matrix.example.com)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:33
+msgid "As [per the Client-Server specification](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery) Matrix does Client Server service discovery using a `/.well-known/matrix/client` file hosted on the base domain (e.g. `example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:35
+msgid "However, this playbook installs your Matrix server on another domain (e.g. `matrix.example.com`) and not on the base domain (e.g. `example.com`), so it takes a little extra manual effort to set up the file."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:37
+msgid "Support Service Discovery (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:39
+msgid "[MSC 1929](https://github.com/matrix-org/matrix-spec-proposals/pull/1929), which was added to [Matrix Specification version v1.10](https://spec.matrix.org/v1.10/client-server-api/#getwell-knownmatrixsupport), specifies a way to add contact details of admins, as well as a link to a support page for users who are having issues with the service. Automated services may also index this information and use it for abuse reports, etc."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:41
+msgid "To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:62
+msgid "Installing well-known files on the base domain's server"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:64
+msgid "To implement the service discovery mechanisms, your base domain's server (e.g. `example.com`) needs to run an HTTPS-capable webserver."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:66
+msgid "Serving the base domain from the Matrix server via the playbook"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:68
+msgid "If you don't have a server for your base domain at all, you can use the Matrix server for this. If you don't need the base domain (e.g. `example.com`) for anything else (hosting a website, etc.), you can point it to the Matrix server's IP address and tell the playbook to configure it."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:70
+msgid "**This is the easiest way to set up well-known serving** -- letting the playbook handle the whole base domain for you (including SSL certificates, etc.) and take care to serve the appropriate well-known files automatically."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:72
+msgid "If you decide to go this route, you don't need to read ahead in this document. Instead, go to [Serving the base domain](configuring-playbook-base-domain-serving.md) to learn how the playbook can help you set it up."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:74
+msgid "However, if you need to use the base domain for other things, this method is less suitable than the one explained below."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:76
+msgid "Manually installing well-known files on the base domain's server"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:78
+msgid "If you're managing the base domain by yourself somehow, you'll need to set up serving of some `/.well-known/matrix/*` files from it via HTTPS."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:80
+msgid "To make things easy for you to set up, this playbook generates and hosts a few well-known files on the Matrix domain's server. The files are generated at the `/matrix/static-files/public/.well-known/matrix/` path on the server and hosted at URLs like `https://matrix.example.com/.well-known/matrix/server` and `https://matrix.example.com/.well-known/matrix/client`, even though this is the wrong place to host them."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:82
+msgid "You have two options when it comes to installing the files on the base domain's server:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:84
+msgid "(Option 1): **Copying the files manually** to your base domain's server"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:86
+msgid "**Hint**: Option 2 is generally a better way to do this. Make sure to go with it, if possible."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:88
+msgid "All you need to do is:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:90
+msgid "copy `/.well-known/matrix/server` and `/.well-known/matrix/client` from the Matrix server (e.g. `matrix.example.com`) to your base domain's server (`example.com`). You can find these files in the `/matrix/static-files/.well-known/matrix` directory on the Matrix server. They are also accessible on URLs like this: `https://matrix.example.com/.well-known/matrix/server` (same for `client`)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:92
+msgid "set up the server at your base domain (e.g. `example.com`) so that it adds an extra HTTP header when serving the `/.well-known/matrix/client` file. [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS), the `Access-Control-Allow-Origin` header should be set with a value of `*`. If you don't do this step, web-based Matrix clients (like Element Web) may fail to work. Setting up headers for the `/.well-known/matrix/server` file is not necessary, as this file is only consumed by non-browsers, which don't care about CORS."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:94
+msgid "This is relatively easy to do and possibly your only choice if you can only host static files from the base domain's server. It is, however, **a little fragile**, as future updates performed by this playbook may regenerate the well-known files and you may need to notice that and copy them over again."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:96
+msgid "(Option 2): **Setting up reverse-proxying** of the well-known files from the base domain's server to the Matrix server"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:98
+msgid "This option is less fragile and generally better."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:100
+msgid "On the base domain's server (e.g. `example.com`), you can set up reverse-proxying, so that any access for the `/.well-known/matrix` location prefix is forwarded to the Matrix domain's server (e.g. `matrix.example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:102
+msgid "With this method, you **don't need** to add special HTTP headers for [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) reasons (like `Access-Control-Allow-Origin`), because your Matrix server (where requests ultimately go) will be configured by this playbook correctly."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:104
+msgid "**For nginx**, it would be something like this:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:121
+msgid "**For Apache2**, it would be something like this:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:135
+msgid "**For Caddy 2**, it would be something like this:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:145
+msgid "**For HAProxy**, it would be something like this:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:164
+msgid "**For Netlify**, configure a [redirect](https://docs.netlify.com/routing/redirects/) using a `_redirects` file in the [publish directory](https://docs.netlify.com/configure-builds/overview/#definitions) with contents like this:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:170
+msgid "**For AWS CloudFront**"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:172
+msgid "Add a custom origin with matrix.example.com to your distribution"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:173
+msgid "Add two behaviors, one for `.well-known/matrix/client` and one for `.well-known/matrix/server` and point them to your new origin."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:175
+msgid "Make sure to:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:177
+msgid "**replace `example.com`** in the server configuration with your actual domain name"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:178
+msgid "and: to **do this for the HTTPS-enabled server block**, as that's where Matrix expects the file to be"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:180
+msgid "Confirming it works"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:182
+msgid "No matter which method you've used to set up the well-known files, if you've done it correctly you should be able to see a JSON file at these URLs:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:184
+msgid "`https://example.com/.well-known/matrix/server`"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:185
+msgid "`https://example.com/.well-known/matrix/client`"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:186
+msgid "`https://example.com/.well-known/matrix/support`"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:188
+msgid "You can also check if everything is configured correctly, by [checking if services work](maintenance-checking-services.md)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/container-images.po b/i18n/locales/bg/LC_MESSAGES/docs/container-images.po
new file mode 100644
index 000000000..9fd9bdc81
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/container-images.po
@@ -0,0 +1,1158 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/container-images.md:1
+msgid "Container images used by the playbook"
+msgstr ""
+
+#: ../../../docs/container-images.md:3
+msgid "This page summarizes the container ([Docker](https://www.docker.com/)) images used by the playbook when setting up your server."
+msgstr ""
+
+#: ../../../docs/container-images.md:5
+msgid "We try to stick to official images (provided by their respective projects) as much as possible."
+msgstr ""
+
+#: ../../../docs/container-images.md:7
+msgid "Homeserver"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Service"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Container image"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Default?"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Description"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Synapse](configuring-playbook-synapse.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[element-hq/synapse](https://ghcr.io/element-hq/synapse)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "✅"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Conduit](configuring-playbook-conduit.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixconduit/matrix-conduit](https://hub.docker.com/r/matrixconduit/matrix-conduit)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "❌"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Dendrite](configuring-playbook-dendrite.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/dendrite-monolith](https://hub.docker.com/r/matrixdotorg/dendrite-monolith/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse."
+msgstr ""
+
+#: ../../../docs/container-images.md:15
+msgid "Clients"
+msgstr ""
+
+#: ../../../docs/container-images.md:17
+msgid "Web clients for Matrix that you can host on your own domains."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Element Web](configuring-playbook-client-element-web.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[vectorim/element-web](https://hub.docker.com/r/vectorim/element-web/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Default Matrix web client, configured to connect to your own Synapse server"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Hydrogen](configuring-playbook-client-hydrogen.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[element-hq/hydrogen-web](https://ghcr.io/element-hq/hydrogen-web)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Lightweight Matrix client with legacy and mobile browser support"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Cinny](configuring-playbook-client-cinny.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[ajbura/cinny](https://hub.docker.com/r/ajbura/cinny)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Simple, elegant and secure web client"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[etke.cc/schildichat-web](https://ghcr.io/etkecc/schildichat-web)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Based on Element Web, with a more traditional instant messaging experience"
+msgstr ""
+
+#: ../../../docs/container-images.md:26
+msgid "Server Components"
+msgstr ""
+
+#: ../../../docs/container-images.md:28
+msgid "Services that run on the server to make the various parts of your installation work."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[PostgreSQL](configuring-playbook-external-postgres.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[postgres](https://hub.docker.com/_/postgres/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Database for Synapse. [Using an external PostgreSQL server](configuring-playbook-external-postgres.md) is also possible."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Coturn](configuring-playbook-turn.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[coturn/coturn](https://hub.docker.com/r/coturn/coturn/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "STUN/TURN server for WebRTC audio/video calls"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Traefik](configuring-playbook-traefik.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Traefik](https://hub.docker.com/_/traefik/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](configuring-playbook-own-webserver.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Let's Encrypt](configuring-playbook-ssl-certificates.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[certbot/certbot](https://hub.docker.com/r/certbot/certbot/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "The [certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Exim](configuring-playbook-email.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[devture/exim-relay](https://hub.docker.com/r/devture/exim-relay/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[ma1sd](configuring-playbook-ma1sd.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Matrix Identity Server"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[ddclient](configuring-playbook-dynamic-dns.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[linuxserver/ddclient](https://hub.docker.com/r/linuxserver/ddclient)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider"
+msgstr ""
+
+#: ../../../docs/container-images.md:40
+msgid "Authentication"
+msgstr ""
+
+#: ../../../docs/container-images.md:42
+msgid "Extend and modify how users are authenticated on your homeserver."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-synapse-rest-auth](configuring-playbook-rest-auth.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "(N/A)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "REST authentication password provider module"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-synapse-shared-secret-auth](configuring-playbook-shared-secret-auth.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Password provider module"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-synapse-ldap3](configuring-playbook-ldap-auth.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "LDAP Auth password provider module"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[activism.international/matrix_ldap_registration_proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A proxy that handles Matrix registration requests and forwards them to LDAP."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-registration](configuring-playbook-matrix-registration.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-matrix-registration/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A simple python application to have a token based Matrix registration"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Matrix User Verification Service](configuring-playbook-user-verification-service.md) (UVS)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/matrix-user-verification-service](https://hub.docker.com/r/atrixdotorg/matrix-user-verification-service)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Service to verify details of a user based on an Open ID token"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[synapse-simple-antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A spam checker module"
+msgstr ""
+
+#: ../../../docs/container-images.md:54
+msgid "File Storage"
+msgstr ""
+
+#: ../../../docs/container-images.md:56
+msgid "Use alternative file storage to the default `media_store` folder."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Goofys](configuring-playbook-s3-goofys.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[ewoutp/goofys](https://hub.docker.com/r/ewoutp/goofys/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[synapse-s3-storage-provider](configuring-playbook-s3.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[t2bot/matrix-media-repo](https://ghcr.io/t2bot/matrix-media-repo)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "matrix-media-repo is a 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:64
+msgid "Bridges"
+msgstr ""
+
+#: ../../../docs/container-images.md:66
+msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-discord](configuring-playbook-bridge-mautrix-discord.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/discord](https://mau.dev/mautrix/discord/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Discord](https://discord.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-slack](configuring-playbook-bridge-mautrix-slack.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/slack](https://mau.dev/mautrix/slack/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Slack](https://slack.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-telegram](configuring-playbook-bridge-mautrix-telegram.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/telegram](https://mau.dev/mautrix/telegram/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Telegram](https://telegram.org/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-gmessages](configuring-playbook-bridge-mautrix-gmessages.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/gmessages](https://mau.dev/mautrix/gmessages/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Google Messages](https://messages.google.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-whatsapp](configuring-playbook-bridge-mautrix-whatsapp.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/whatsapp](https://mau.dev/mautrix/whatsapp/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [WhatsApp](https://www.whatsapp.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-wsproxy](configuring-playbook-bridge-mautrix-wsproxy.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/wsproxy](https://mau.dev/mautrix/wsproxy/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to Android SMS or Apple iMessage"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-twitter](configuring-playbook-bridge-mautrix-twitter.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/twitter](https://mau.dev/mautrix/twitter/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Twitter](https://twitter.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/googlechat](https://mau.dev/mautrix/googlechat/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "mautrix-meta (for [Messenger](configuring-playbook-bridge-mautrix-meta-messenger.md) and [Instagram](configuring-playbook-bridge-mautrix-meta-instagram.md))"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/meta](https://mau.dev/mautrix/meta/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-signal](configuring-playbook-bridge-mautrix-signal.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/signal](https://mau.dev/mautrix/signal/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Signal](https://www.signal.org/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[beeper-linkedin](configuring-playbook-bridge-beeper-linkedin.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[beeper/linkedin](https://ghcr.io/beeper/linkedin)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [LinkedIn](https://www.linkedin.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/matrix-appservice-irc](https://hub.docker.com/r/matrixdotorg/matrix-appservice-irc)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-appservice-kakaotalk](configuring-playbook-bridge-appservice-kakaotalk.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Self-building"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-org/matrix-appservice-discord](https://ghcr.io/matrix-org/matrix-appservice-discord)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Discord](https://discordapp.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-hookshot](configuring-playbook-bridge-hookshot.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[halfshot/matrix-hookshot](https://hub.docker.com/r/halfshot/matrix-hookshot)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-sms-bridge](configuring-playbook-bridge-matrix-bridge-sms.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[folivonet/matrix-sms-bridge](https://hub.docker.com/repository/docker/folivonet/matrix-sms-bridge)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to SMS"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-wechat](configuring-playbook-bridge-wechat.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[lxduo/matrix-wechat](https://hub.docker.com/r/lxduo/matrix-wechat)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [WeChat](https://www.wechat.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Heisenbridge](configuring-playbook-bridge-heisenbridge.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[hif1/heisenbridge](https://hub.docker.com/r/hif1/heisenbridge)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[nodefyme/go-skype-bridge](https://hub.docker.com/r/nodefyme/go-skype-bridge)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Skype](https://www.skype.com)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Slack](https://slack.com)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-puppet-instagram)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-groupme](configuring-playbook-bridge-mx-puppet-groupme.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[xangelix/mx-puppet-groupme](https://hub.docker.com/r/xangelix/mx-puppet-groupme)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [GroupMe](https://groupme.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-steam](configuring-playbook-bridge-mx-puppet-steam.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[icewind1991/mx-puppet-steam](https://hub.docker.com/r/icewind1991/mx-puppet-steam)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Steam](https://steamapp.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Email2Matrix](configuring-playbook-email2matrix.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[devture/email2matrix](https://hub.docker.com/r/devture/email2matrix/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge for relaying emails to Matrix rooms"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[etke.cc/postmoogle](https://github.com/etkecc/postmoogle/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Email to Matrix bridge"
+msgstr ""
+
+#: ../../../docs/container-images.md:99
+msgid "Bots"
+msgstr ""
+
+#: ../../../docs/container-images.md:101
+msgid "Bots provide various additional functionality to your installation."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[baibot](configuring-playbook-bot-baibot.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[etke.cc/baibot](https://ghcr.io/etkecc/baibot)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[anoa/matrix-reminder-bot](https://hub.docker.com/r/anoa/matrix-reminder-bot)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bot for scheduling one-off & recurring reminders and alarms"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[moanos/matrix-registration-bot](https://hub.docker.com/r/moanos/matrix-registration-bot/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bot for invitations by creating and managing registration tokens"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[maubot](configuring-playbook-bot-maubot.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[dock.mau.dev/maubot/maubot](https://mau.dev/maubot/maubot/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A plugin-based Matrix bot system"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Honoroit](configuring-playbook-bot-honoroit.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[etke.cc/honoroit](https://github.com/etkecc/honoroit/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A helpdesk bot"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Mjolnir](configuring-playbook-bot-mjolnir.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/mjolnir](https://hub.docker.com/r/matrixdotorg/mjolnir)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A moderation tool for Matrix"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Draupnir](configuring-playbook-bot-draupnir.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[gnuxie/draupnir](https://hub.docker.com/r/gnuxie/draupnir)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A moderation tool for Matrix (Fork of Mjolnir)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Buscarron](configuring-playbook-bot-buscarron.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[etke.cc/buscarron](https://ghcr.io/etkecc/buscarron)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Web forms (HTTP POST) to Matrix"
+msgstr ""
+
+#: ../../../docs/container-images.md:114
+msgid "Administration"
+msgstr ""
+
+#: ../../../docs/container-images.md:116
+msgid "Services that help you in administrating and monitoring your Matrix installation."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[metio/matrix-alertmanager-receiver](https://hub.docker.com/r/metio/matrix-alertmanager-receiver)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[element-hq/matrix-authentication-service](https://ghcr.io/element-hq/matrix-authentication-service)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "OAuth 2.0 and OpenID Provider server"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[synapse-admin](configuring-playbook-synapse-admin.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[etke.cc/synapse-admin](https://ghcr.io/etkecc/synapse-admin)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A web UI tool for administrating users and rooms on your Matrix server"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Metrics and Graphs](configuring-playbook-prometheus-grafana.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[prom/prometheus](https://hub.docker.com/r/prom/prometheus/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Prometheus](https://prometheus.io) time-series database server"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[prom/node-exporter](https://hub.docker.com/r/prom/node-exporter/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[grafana/grafana](https://hub.docker.com/r/grafana/grafana/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Graphing tool that works well with the above two images. Our playbook also adds two dashboards for [Synapse](https://github.com/element-hq/synapse/tree/master/contrib/grafana) and [Node Exporter](https://github.com/rfrail3/grafana-dashboards)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Metrics and Graphs](configuring-playbook-prometheus-nginxlog.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[martin-helmich/prometheus-nginxlog-exporter/exporter](https://ghcr.io/martin-helmich/prometheus-nginxlog-exporter/exporter)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Addon for Prometheus that gathers access logs from various nginx reverse-proxies"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Borg](configuring-playbook-backup-borg.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Backups"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[rageshake](configuring-playbook-rageshake.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-org/rageshake](https://ghcr.io/matrix-org/rageshake)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bug report server"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[synapse-usage-exporter](configuring-playbook-synapse-usage-exporter.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus."
+msgstr ""
+
+#: ../../../docs/container-images.md:131
+msgid "Misc"
+msgstr ""
+
+#: ../../../docs/container-images.md:133
+msgid "Various services that don't fit any other categories."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[sliding-sync](configuring-playbook-sliding-sync-proxy.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+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
+msgid "[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A Synapse module to automatically accept invites."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[synapse_auto_compressor](configuring-playbook-synapse-auto-compressor.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[etke.cc/rust-synapse-compress-state](https://gitlab.com/etke.cc/rust-synapse-compress-state/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A cli tool that automatically compresses `state_groups` database table in background."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-corporal/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Reconciliator and gateway for a managed Matrix server"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Etherpad](configuring-playbook-etherpad.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[etherpad/etherpad](https://hub.docker.com/r/etherpad/etherpad/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "An open source collaborative text editor"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Jitsi](configuring-playbook-jitsi.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[jitsi/web](https://hub.docker.com/r/jitsi/web)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "the [Jitsi](https://jitsi.org/) web UI"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[jitsi/jicofo](https://hub.docker.com/r/jitsi/jicofo)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "the [Jitsi](https://jitsi.org/) Focus component"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[jitsi/prosody](https://hub.docker.com/r/jitsi/prosody)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "the [Jitsi](https://jitsi.org/) Prosody XMPP server component"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[jitsi/jvb](https://hub.docker.com/r/jitsi/jvb)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "the [Jitsi](https://jitsi.org/) Video Bridge component"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Cactus Comments](configuring-playbook-cactus-comments.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[cactuscomments/cactus-appservice](https://hub.docker.com/r/cactuscomments/cactus-appservice/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A federated comment system built on Matrix"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[joseluisq/static-web-server](https://hub.docker.com/r/joseluisq/static-web-server)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Pantalaimon](configuring-playbook-pantalaimon.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/pantalaimon](https://hub.docker.com/r/matrixdotorg/pantalaimon)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "An E2EE aware proxy daemon"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Sygnal](configuring-playbook-sygnal.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/sygnal](https://hub.docker.com/r/matrixdotorg/sygnal/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Reference Push Gateway for Matrix"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[ntfy](configuring-playbook-ntfy.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[binwiederhier/ntfy](https://hub.docker.com/r/binwiederhier/ntfy/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Self-hosted, UnifiedPush-compatible push notifications server"
+msgstr ""
+
+#: ../../../docs/container-images.md:152
+msgid "Container images of deprecated / unmaintained services"
+msgstr ""
+
+#: ../../../docs/container-images.md:154
+msgid "The list of the deprecated or unmaintained services is available [here](configuring-playbook.md#deprecated--unmaintained--removed-services)."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Dimension](configuring-playbook-dimension.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-dimension)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "An open source integration manager for Matrix clients"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Go-NEB](configuring-playbook-bot-go-neb.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/go-neb](https://hub.docker.com/r/matrixdotorg/go-neb)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A multi functional bot written in Go"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-chatgpt-bot](configuring-playbook-bot-chatgpt.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixgpt/matrix-chatgpt-bot](https://ghcr.io/matrixgpt/matrix-chatgpt-bot)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Accessing ChatGPT via your favourite Matrix client"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-facebook](configuring-playbook-bridge-mautrix-facebook.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/facebook](https://mau.dev/mautrix/facebook/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Facebook](https://facebook.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-hangouts](configuring-playbook-bridge-mautrix-hangouts.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/hangouts](https://mau.dev/mautrix/hangouts/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Google Hangouts](https://en.wikipedia.org/wiki/Google_Hangouts)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-instagram](configuring-playbook-bridge-mautrix-instagram.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/instagram](https://mau.dev/mautrix/instagram/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Instagram](https://instagram.com/)"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/faq.po b/i18n/locales/bg/LC_MESSAGES/docs/faq.po
new file mode 100644
index 000000000..0c06ff7b1
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/faq.po
@@ -0,0 +1,878 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/faq.md:1
+msgid "Frequently Asked Questions"
+msgstr ""
+
+#: ../../../docs/faq.md:3
+msgid "This documentation page tries to answer various Frequently Asked Questions about all things [Matrix](https://matrix.org/), with a focus on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work))."
+msgstr ""
+
+#: ../../../docs/faq.md:5
+msgid "This FAQ page does not intend to replace the [matrix.org FAQ](https://matrix.org/faq/) (please see that one too)."
+msgstr ""
+
+#: ../../../docs/faq.md:7
+msgid "We've only started this FAQ recently, so it's still somewhat empty."
+msgstr ""
+
+#: ../../../docs/faq.md:9
+msgid "Also, we encourage you to not dig yourself into a hole by reading way too much. When you've heard enough, proceed to installation. To get started, see [below](#how-do-i-run-the-installation) about our installation guides."
+msgstr ""
+
+#: ../../../docs/faq.md:11
+msgid "Introductory"
+msgstr ""
+
+#: ../../../docs/faq.md:13
+msgid "Where do I find more questions and answers about Matrix?"
+msgstr ""
+
+#: ../../../docs/faq.md:15
+msgid "This is a Frequently Asked Questions page focused on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work)) for deploying a [Matrix](https://matrix.org/) server."
+msgstr ""
+
+#: ../../../docs/faq.md:17
+msgid "For a lot more generic questions and answers, see the [matrix.org FAQ](https://matrix.org/faq/)."
+msgstr ""
+
+#: ../../../docs/faq.md:19
+msgid "What is Matrix? What is Element? What is Synapse? Why are you confusing me with so many terms?"
+msgstr ""
+
+#: ../../../docs/faq.md:21
+msgid "[Matrix](https://matrix.org/) is a new type of realtime communication (chat) network, the closest analogy to which is probably \"email\"."
+msgstr ""
+
+#: ../../../docs/faq.md:23
+msgid "You don't just use the \"email\" protocols (SMTP, POP3, IMAP) directly though. There's a *server* somewhere which stores your data (`@gmail.com`, `@yahoo.com`, `@hotmail.com`, `@your-company.com`) and you access it by using these \"email\" protocols via some *client* program (Outlook, Thunderbird, some website, etc)."
+msgstr ""
+
+#: ../../../docs/faq.md:25
+msgid "In the world of the Matrix chat protocol, there are various client programs. The first and currently most full-featured one is called [Element](https://element.io/) (used to be called Riot.im and Vector.im in the past). There are [many other clients](https://matrix.org/clients/). You can switch clients as much as you want until you find the one that is right for you on a given platform (you may use Element Desktop on your desktop, but Fluffychat on your phone, etc)."
+msgstr ""
+
+#: ../../../docs/faq.md:27
+msgid "Matrix is also like email due to the fact that there are many servers around the world which can all talk to each other (you can send email from `@gmail.com` addresses to `@yahoo.com` and `@hotmail.com` addresses). It's the same with Matrix (`@bob:example.com` can talk to `@alice:example.org`)."
+msgstr ""
+
+#: ../../../docs/faq.md:29
+msgid "If someone else is hosting your Matrix server (you being `@alice:matrix.org` or some other public server like this), all you need is a Matrix client program, like Element Web or Element X Android."
+msgstr ""
+
+#: ../../../docs/faq.md:31
+msgid "If you'd like to host your own server (you being `@alice:example.com`), you'd need to set up a Matrix server program, like Synapse."
+msgstr ""
+
+#: ../../../docs/faq.md:33
+msgid "In short:"
+msgstr ""
+
+#: ../../../docs/faq.md:35
+msgid "Matrix is the protocol - a set of rules about how the chat network operates"
+msgstr ""
+
+#: ../../../docs/faq.md:36
+msgid "Element is a client program you can use to participate on the Matrix chat network via some server (yours or someone else's). There are also [many other client programs](https://matrix.org/clients/)."
+msgstr ""
+
+#: ../../../docs/faq.md:37
+msgid "Synapse is a server program you can use to host your very own Matrix server."
+msgstr ""
+
+#: ../../../docs/faq.md:39
+msgid "This FAQ here mostly focuses on installing various Matrix services using the Ansible automation tool. You can learn much more about Matrix in the [matrix.org FAQ](https://matrix.org/faq/)."
+msgstr ""
+
+#: ../../../docs/faq.md:41
+msgid "People I wish to talk to are not on Matrix. Can I talk to them?"
+msgstr ""
+
+#: ../../../docs/faq.md:43
+msgid "You most likely can. Besides Matrix-native chats, Matrix also supports the concept of \"bridging\", which allows you to plug other networks into it."
+msgstr ""
+
+#: ../../../docs/faq.md:45
+msgid "This Ansible playbook can help you install [tens of bridges for various networks](configuring-playbook.md#bridging-other-networks)."
+msgstr ""
+
+#: ../../../docs/faq.md:47
+msgid "Besides setting up your own bridges (preferable), you can also use some [public bridges hosted by others](https://publiclist.anchel.nl/#bridges)."
+msgstr ""
+
+#: ../../../docs/faq.md:49
+msgid "How do I get started with Matrix?"
+msgstr ""
+
+#: ../../../docs/faq.md:51
+msgid "One of [Matrix](https://matrix.org/)'s distinguishing strengths (compared to other chat networks) is its decentralized nature. There's not just one entity (company, organization) controlling the servers. Rather there's thousands of servers operated by different people - one server being insecure, slow or disrespective toward its users does not affect the rest of the network. To participate in that decentralization in its fullest, consider hosting your own server or using some public server other than the largest/default one (`matrix.org`)."
+msgstr ""
+
+#: ../../../docs/faq.md:53
+msgid "There are 3 ways to get into Matrix, depending on your technical ability and needs:"
+msgstr ""
+
+#: ../../../docs/faq.md:55
+msgid "**using the existing default server** - the easiest way is to use an existing server. The largest public Matrix server is `matrix.org` and it's configured as a default server in clients such as [Element Web](https://app.element.io) and many others. Just use Element Web on the browser via that link (or [download client apps for your Desktop or smartphone](https://element.io/app-for-productivity)), create an account and start chatting."
+msgstr ""
+
+#: ../../../docs/faq.md:57
+msgid "**using some other server** - instead of using the largest public server (`matrix.org`), you can use another public one. Here's a [list of public Matrix servers](https://joinmatrix.org/servers/) to choose from. Go to [Element Web](https://app.element.io) or download [some other client](https://matrix.org/clients/) of your choosing and adjust the homeserver URL during login."
+msgstr ""
+
+#: ../../../docs/faq.md:59
+msgid "**using your own server** - running your own server puts you in ultimate control of your data. It also lets you have your own user IDs (e.g. `@bob:example.com`). See [How do I set up my own Matrix server](#how-do-i-set-up-my-own-matrix-server)."
+msgstr ""
+
+#: ../../../docs/faq.md:61
+msgid "How do I set up my own Matrix server?"
+msgstr ""
+
+#: ../../../docs/faq.md:63
+msgid "Normally, you'd first choose the [Matrix](https://matrix.org/) server software you'd like to run. At the time of this writing (January/2021), there's only one fully-featured server program, so there's only one reasonable choice. That's [Synapse](https://github.com/element-hq/synapse)."
+msgstr ""
+
+#: ../../../docs/faq.md:65
+msgid "There are [many guides about installing Synapse](https://matrix.org/docs/guides/#installing-synapse). Using this Ansible playbook is just one way of doing it."
+msgstr ""
+
+#: ../../../docs/faq.md:67
+msgid "Naturally, we're biased, so our usual recommendation is to go with this [Ansible](https://www.ansible.com/) playbook, instead of installing Synapse (and many many other things around it) manually."
+msgstr ""
+
+#: ../../../docs/faq.md:69
+msgid "To get started with the playbook, check out the [Quick start](quick-start.md) or full installation guide (starting at the [Prerequisites](prerequisites.md) page)."
+msgstr ""
+
+#: ../../../docs/faq.md:71
+msgid "What is Ansible? How does it work?"
+msgstr ""
+
+#: ../../../docs/faq.md:73
+msgid "[Ansible](https://www.ansible.com/) is an automation program. This \"playbook\" is a collection of tasks/scripts that will set up a [Matrix](https://matrix.org/) server for you, so you don't have to perform these tasks manually."
+msgstr ""
+
+#: ../../../docs/faq.md:75
+msgid "We have written these automated tasks for you and all you need to do is execute them using the Ansible program."
+msgstr ""
+
+#: ../../../docs/faq.md:77
+msgid "You can install Ansible and this playbook code repository on your own computer and tell it to install Matrix services at the server living at `matrix.example.com`. We recommend installing Ansible on your own computer."
+msgstr ""
+
+#: ../../../docs/faq.md:79
+msgid "Alternatively, you can download Ansible and the playbook itself directly on the `matrix.example.com` server."
+msgstr ""
+
+#: ../../../docs/faq.md:81
+msgid "To learn more, see our [dedicated Ansible documentation page](ansible.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:83
+msgid "What is `just`?"
+msgstr ""
+
+#: ../../../docs/faq.md:85
+msgid "[`just`](https://github.com/casey/just) is a modern command-runner alternative to [make](https://www.gnu.org/software/make/). It can be used to invoke commands with less typing."
+msgstr ""
+
+#: ../../../docs/faq.md:87
+msgid "The `just` utility executes shortcut commands (called \"recipes\"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile)."
+msgstr ""
+
+#: ../../../docs/faq.md:89
+msgid "For details about `just` commands, take a look at: [Running `just` commands](just.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:91
+msgid "The playbook also contains a `Makefile` for the `make` tool, but most of the just recipes are not available as targets in the `Makefile`."
+msgstr ""
+
+#: ../../../docs/faq.md:93
+msgid "Why use this playbook and not install Synapse and other things manually?"
+msgstr ""
+
+#: ../../../docs/faq.md:95
+msgid "There are various guides telling you how easy it is to install [Synapse](https://github.com/element-hq/synapse)."
+msgstr ""
+
+#: ../../../docs/faq.md:97
+msgid "Reading the documentation of this Ansible playbook, you may also be thinking:"
+msgstr ""
+
+#: ../../../docs/faq.md:99
+msgid "I don't know what [Ansible](https://www.ansible.com/) is. I don't know what [Docker](https://www.docker.com/) is. This looks more complicated."
+msgstr ""
+
+#: ../../../docs/faq.md:101
+msgid ".. so you may be leaning toward [installing Synapse manually](https://github.com/element-hq/synapse/blob/master/INSTALL.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:103
+msgid "The problem with a manual installation is:"
+msgstr ""
+
+#: ../../../docs/faq.md:105
+msgid "Synapse is written in Python. If not packaged for your distribution, you'd need to install various Python modules, etc., and keep them updated."
+msgstr ""
+
+#: ../../../docs/faq.md:106
+msgid "Synapse requires a [Postgres](https://www.postgresql.org/) database (it can run on SQLite, but that's very much discouraged). So you'd need to install Postgres as well."
+msgstr ""
+
+#: ../../../docs/faq.md:107
+msgid "you may also need a reverse-proxy server in front of it (nginx, Apache), so you'd need to be familiar with that"
+msgstr ""
+
+#: ../../../docs/faq.md:108
+msgid "SSL is required, so you'd need to obtain Let's Encrypt (or other free or non-free) certificates for one or more domain names. You'd need to be familiar with [certbot](https://certbot.eff.org/) (when using Let's Encrypt) or similar software."
+msgstr ""
+
+#: ../../../docs/faq.md:109
+msgid "for each additional component you'd like to add (client like [Element](https://element.io), bridge to some other chat network, integration manager (stickers, other services, Identity Manager, etc.), you'll need to spend extra time installing and wiring it with the rest of the system in a way that works."
+msgstr ""
+
+#: ../../../docs/faq.md:110
+msgid "you'll likely get slower updates for all of these components, depending on your distro packaging or your own time and ability"
+msgstr ""
+
+#: ../../../docs/faq.md:112
+msgid "The playbook, on the other hand, installs a bunch of components for you by default, obtains SSL certificates for you, etc. If you'd like, you can enable various bridges and other services with very little effort. All the components are wired to work together."
+msgstr ""
+
+#: ../../../docs/faq.md:114
+msgid "All services run in Docker containers (most being officially provided by each component's developers), so we're not at the mercy of distro packaging."
+msgstr ""
+
+#: ../../../docs/faq.md:116
+msgid "Why use this playbook and not just use the Docker image directly?"
+msgstr ""
+
+#: ../../../docs/faq.md:118
+msgid "Reasons are similar to the reasons for not installing manually."
+msgstr ""
+
+#: ../../../docs/faq.md:120
+msgid "Besides Synapse, you'd need other things - a Postgres database, likely the [Element](https://element.io) client, etc., etc."
+msgstr ""
+
+#: ../../../docs/faq.md:122
+msgid "Using the playbook, you get all these components in a way that works well together out of the box."
+msgstr ""
+
+#: ../../../docs/faq.md:124
+msgid "Occasionally I see some people are talking about \"MDAD\". What is it?"
+msgstr ""
+
+#: ../../../docs/faq.md:126
+msgid "It is the acronym of us: **m**atrix-**d**ocker-**a**nsible-**d**eploy."
+msgstr ""
+
+#: ../../../docs/faq.md:128
+msgid "What's different about this Ansible playbook compared to [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy)?"
+msgstr ""
+
+#: ../../../docs/faq.md:130
+msgid "This is similar to the [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy) Ansible deployment, but:"
+msgstr ""
+
+#: ../../../docs/faq.md:132
+msgid "this one is a complete Ansible playbook (instead of just a role), so it's **easier to run** - especially for folks not familiar with Ansible"
+msgstr ""
+
+#: ../../../docs/faq.md:134
+msgid "this one installs and hooks together **a lot more Matrix-related services** for you (see above)"
+msgstr ""
+
+#: ../../../docs/faq.md:136
+msgid "this one **can be executed more than once** without causing trouble"
+msgstr ""
+
+#: ../../../docs/faq.md:138
+msgid "works on various distros: **CentOS** (7.0+), Debian-based distributions (**Debian** 10/Buster+, **Ubuntu** 18.04+), **Archlinux**"
+msgstr ""
+
+#: ../../../docs/faq.md:140
+msgid "this one installs everything in a single directory (`/matrix` by default) and **doesn't \"contaminate\" your server** with files all over the place"
+msgstr ""
+
+#: ../../../docs/faq.md:142
+msgid "this one **doesn't necessarily take over** ports 80 and 443. By default, it sets up [Traefik](https://doc.traefik.io/traefik/) for you there, but you can also [use your own webserver](configuring-playbook-own-webserver.md)"
+msgstr ""
+
+#: ../../../docs/faq.md:144
+msgid "this one **runs everything in Docker containers**, so it's likely more predictable and less fragile (see [Docker images used by this playbook](container-images.md))"
+msgstr ""
+
+#: ../../../docs/faq.md:146
+msgid "this one retrieves and automatically renews free [Let's Encrypt](https://letsencrypt.org/) **SSL certificates** for you"
+msgstr ""
+
+#: ../../../docs/faq.md:148
+msgid "this one optionally can store the `media_store` content repository files on [Amazon S3](https://aws.amazon.com/s3/) (but defaults to storing files on the server's filesystem)"
+msgstr ""
+
+#: ../../../docs/faq.md:150
+msgid "this one optionally **allows you to use an external PostgreSQL server** for Synapse's database (but defaults to running one in a container)"
+msgstr ""
+
+#: ../../../docs/faq.md:152
+msgid "helps you **import data from a previous installation** (so you can migrate your manual virtualenv/Docker setup to a more managed one)"
+msgstr ""
+
+#: ../../../docs/faq.md:154
+msgid "this one is actually **maintained**"
+msgstr ""
+
+#: ../../../docs/faq.md:156
+msgid "Server-related"
+msgstr ""
+
+#: ../../../docs/faq.md:158
+msgid "What kind of server do I need to install Matrix using this Ansible playbook?"
+msgstr ""
+
+#: ../../../docs/faq.md:160
+msgid "We list our server requirements in [Prerequisites](prerequisites.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:162
+msgid "Why not run Matrix on Kubernetes?"
+msgstr ""
+
+#: ../../../docs/faq.md:164
+msgid "There's no reason not to run Matrix on [Kubernetes](https://kubernetes.io/)."
+msgstr ""
+
+#: ../../../docs/faq.md:166
+msgid "However, that's overly complicated for thousands of us who just want to run a single small (and sometimes not so small) Matrix server, either using \"cloud\" servers or even a [Raspberry Pi](https://www.raspberrypi.org/) at home."
+msgstr ""
+
+#: ../../../docs/faq.md:168
+msgid "For us, a Kubernetes-based setup which requires a cluster of multiple computers and is more technically-involved is a no-go."
+msgstr ""
+
+#: ../../../docs/faq.md:170
+msgid "There are others working on automating a Matrix-on-Kubernetes setup, such as this [Helm](https://helm.sh/) chart: https://github.com/dacruz21/matrix-chart."
+msgstr ""
+
+#: ../../../docs/faq.md:172
+msgid "Why don't you use Podman instead of Docker?"
+msgstr ""
+
+#: ../../../docs/faq.md:174
+msgid "We like the philosophy of a daemonless container runtime, but [Podman](https://podman.io) is just not ready for our use case yet."
+msgstr ""
+
+#: ../../../docs/faq.md:176
+msgid "Learn more about our past experiences/attempts to give Podman a chance, by reading [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/520)."
+msgstr ""
+
+#: ../../../docs/faq.md:178
+msgid "In short, `alias podman=docker` is a lie (for us)."
+msgstr ""
+
+#: ../../../docs/faq.md:180
+msgid "Why use Docker?"
+msgstr ""
+
+#: ../../../docs/faq.md:182
+msgid "[Docker](https://www.docker.com/) is one of our 2 hard dependencies (the other one being [systemd](https://systemd.io/))."
+msgstr ""
+
+#: ../../../docs/faq.md:184
+msgid "It lets us run services in an isolated manner and independently of the (usually old) packages available for distributions."
+msgstr ""
+
+#: ../../../docs/faq.md:186
+msgid "It also lets us have a unified setup which runs the same across various supported distros (see them on [Prerequisites](prerequisites.md))."
+msgstr ""
+
+#: ../../../docs/faq.md:188
+msgid "Is Docker a hard requirement?"
+msgstr ""
+
+#: ../../../docs/faq.md:190
+msgid "Yes. See [Why don't you use Podman instead of Docker?](#why-dont-you-use-podman-instead-of-docker) for why we're not using another container runtime."
+msgstr ""
+
+#: ../../../docs/faq.md:192
+msgid "All of our services run in containers. It's how we achieve predictability and also how we support tens of different services across lots of distros."
+msgstr ""
+
+#: ../../../docs/faq.md:194
+msgid "The only thing we need on the distro is systemd and Python (we install Docker ourselves, unless you ask us not to)."
+msgstr ""
+
+#: ../../../docs/faq.md:196
+msgid "Why don't you use docker-compose?"
+msgstr ""
+
+#: ../../../docs/faq.md:198
+msgid "Instead of using [docker-compose](https://docs.docker.com/compose/), we prefer installing systemd services and scheduling those independently."
+msgstr ""
+
+#: ../../../docs/faq.md:200
+msgid "There are people who have worked on turning this setup into a docker-compose-based one. See these experiments [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/64#issuecomment-603164625). There is also a demo project ([element-docker-demo](https://github.com/element-hq/element-docker-demo)) by Element."
+msgstr ""
+
+#: ../../../docs/faq.md:202
+msgid "Can I run this on a distro without systemd?"
+msgstr ""
+
+#: ../../../docs/faq.md:204
+msgid "No. [systemd](https://systemd.io/) is one of our 2 hard dependencies (the other one being [Docker](https://www.docker.com/))."
+msgstr ""
+
+#: ../../../docs/faq.md:206
+msgid "Can I install this on a Raspberry Pi?"
+msgstr ""
+
+#: ../../../docs/faq.md:208
+msgid "Yes, you can. See our [Alternative Architectures](alternative-architectures.md) documentation page."
+msgstr ""
+
+#: ../../../docs/faq.md:210
+msgid "Whether a Raspberry Pi has enough power to give you a good experience is another question. It depends on your use case."
+msgstr ""
+
+#: ../../../docs/faq.md:212
+msgid "Also see: [What kind of server specs do I need?](#what-kind-of-server-specs-do-i-need)."
+msgstr ""
+
+#: ../../../docs/faq.md:214
+msgid "What kind of server specs do I need?"
+msgstr ""
+
+#: ../../../docs/faq.md:216
+msgid "This largely depends on your use case. It's not so much the number of users that you plan to host, but rather the number of large rooms they will join."
+msgstr ""
+
+#: ../../../docs/faq.md:218
+msgid "Federated rooms with lots of history and containing hundreds of other servers are very heavy CPU-wise and memory-wise."
+msgstr ""
+
+#: ../../../docs/faq.md:220
+msgid "You can probably use a 1 CPU + 1GB memory server to host hundreds of local users just fine, but as soon as one of them joins a federated room like `#matrix:matrix.org` (Matrix HQ) or some IRC-bridged room (say `##linux`), your server will get the need for a lot more power (at least 2GB RAM, etc)."
+msgstr ""
+
+#: ../../../docs/faq.md:222
+msgid "Running Matrix on a server with 1GB of memory is possible (especially if you disable some not-so-important services). See [How do I optimize this setup for a low-power server?](#how-do-i-optimize-this-setup-for-a-low-power-server)."
+msgstr ""
+
+#: ../../../docs/faq.md:224
+msgid "**We recommend starting with a server having at least 2GB of memory** and even then using it sparingly. If you know for sure you'll be joining various large rooms, etc., then going for 4GB of memory or more is a good idea."
+msgstr ""
+
+#: ../../../docs/faq.md:226
+msgid "Besides the regular Matrix stuff, we also support things like video-conferencing using [Jitsi](configuring-playbook-jitsi.md) and other additional services which (when installed) may use up a lot of memory. Things do add up. Besides the Synapse Matrix server, Jitsi is especially notorious for consuming a lot of resources. If you plan on running Jitsi, we recommend a server with at least 2GB of memory (preferrably more). See our [Jitsi documentation page](configuring-playbook-jitsi.md) to learn how to optimize its memory/CPU usage."
+msgstr ""
+
+#: ../../../docs/faq.md:228
+msgid "Can I run this in an LXC container?"
+msgstr ""
+
+#: ../../../docs/faq.md:230
+msgid "If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container."
+msgstr ""
+
+#: ../../../docs/faq.md:232
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/faq.md:234
+msgid "Why install my server at matrix.example.com and not at the base domain?"
+msgstr ""
+
+#: ../../../docs/faq.md:236
+msgid "It's the same with email servers. Your email address is likely `name@company.com`, not `name@mail.company.com`, even though it's `mail.company.com` that is really handling your data for `@company.com` email to work."
+msgstr ""
+
+#: ../../../docs/faq.md:238
+msgid "Using a separate domain name is easier to manage (although it's a little hard to get right at first) and keeps your Matrix server isolated from your website (if you have one), from your email server (if you have one), etc. Therefore, this playbook sets up services on your Matrix server (`matrix.example.com`) by default."
+msgstr ""
+
+#: ../../../docs/faq.md:240
+msgid "I don't control anything on the base domain and can't set up delegation to matrix.example.com. What do I do?"
+msgstr ""
+
+#: ../../../docs/faq.md:242
+msgid "If you're not in control of your base domain (or the server handling it) at all, you can take a look at [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:244
+msgid "I can't set up HTTPS on the base domain. How will I get Matrix federating?"
+msgstr ""
+
+#: ../../../docs/faq.md:246
+msgid "If you really can't obtain an HTTPS certificate for your base domain, you can take a look at [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:248
+msgid "How do I install on matrix.example.com without involving the base domain?"
+msgstr ""
+
+#: ../../../docs/faq.md:250
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/faq.md:271
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/faq.md:278
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/faq.md:280
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/faq.md:282
+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/faq.md:284
+msgid "Without setting up [server delegation](howto-server-delegation.md) to `matrix.example.com`, your user IDs will be like `@alice:matrix.example.com`. This is equivalent to having an email address like `bob@mail.company.com`, instead of just `bob@company.com`."
+msgstr ""
+
+#: ../../../docs/faq.md:286
+msgid "I don't use the base domain for anything. How am I supposed to set up Server Delegation for Matrix services?"
+msgstr ""
+
+#: ../../../docs/faq.md:288
+msgid "If you don't use your base domain for anything, then it's hard for you to \"serve files over HTTPS\" on it -- something we ask you to do for the [.well-known](configuring-well-known.md) setup (needed for [Server Delegation](howto-server-delegation.md))."
+msgstr ""
+
+#: ../../../docs/faq.md:290
+msgid "Luckily, the playbook can set up your Matrix server (at `matrix.example.com`) to also handle traffic for the base domain (`example.com`)."
+msgstr ""
+
+#: ../../../docs/faq.md:292
+msgid "See [Serving the base domain](configuring-playbook-base-domain-serving.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:294
+msgid "How do I optimize this setup for a low-power server?"
+msgstr ""
+
+#: ../../../docs/faq.md:296
+msgid "You can disable some not-so-important services to save on memory."
+msgstr ""
+
+#: ../../../docs/faq.md:318
+msgid "You can also consider implementing a restriction on room complexity, in order to prevent users from joining very heavy rooms:"
+msgstr ""
+
+#: ../../../docs/faq.md:328
+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:330
+msgid "I already have Docker on my server. Can you stop installing Docker via the playbook?"
+msgstr ""
+
+#: ../../../docs/faq.md:332
+msgid "Yes, we can stop installing Docker ourselves. Just use this in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/faq.md:338
+msgid "I run another webserver on the same server where I wish to install Matrix. What now?"
+msgstr ""
+
+#: ../../../docs/faq.md:340
+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:342
+msgid "How is the effective configuration determined?"
+msgstr ""
+
+#: ../../../docs/faq.md:344
+msgid "Configuration variables are defined in multiple places in this playbook and are considered in this order:"
+msgstr ""
+
+#: ../../../docs/faq.md:346
+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:348
+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:350
+msgid "finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` file, which is the ultimate override"
+msgstr ""
+
+#: ../../../docs/faq.md:352
+msgid "What configuration variables are available?"
+msgstr ""
+
+#: ../../../docs/faq.md:354
+msgid "You can discover the variables you can override in each role (`roles/*/*/defaults/main.yml`)."
+msgstr ""
+
+#: ../../../docs/faq.md:356
+msgid "As described in [How is the effective configuration determined?](#how-is-the-effective-configuration-determined), these role-defaults may be overriden by values defined in `group_vars/matrix_servers`."
+msgstr ""
+
+#: ../../../docs/faq.md:358
+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:360 ../../../docs/faq.md:372
+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:362
+msgid "I'd like to adjust some configuration which doesn't have a corresponding variable. How do I do it?"
+msgstr ""
+
+#: ../../../docs/faq.md:364
+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:366
+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:368
+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:370
+msgid "Check each role's `roles/*/*/defaults/main.yml` for the corresponding variable and an example for how use it."
+msgstr ""
+
+#: ../../../docs/faq.md:374
+msgid "Installation"
+msgstr ""
+
+#: ../../../docs/faq.md:376
+msgid "How do I run the installation?"
+msgstr ""
+
+#: ../../../docs/faq.md:378
+msgid "See [Installing](installing.md) to learn how to use Ansible to install Matrix services."
+msgstr ""
+
+#: ../../../docs/faq.md:380
+msgid "However, we recommend you to follow our installation guide, instead of jumping straight to installing."
+msgstr ""
+
+#: ../../../docs/faq.md:382
+msgid "There are two guides available:"
+msgstr ""
+
+#: ../../../docs/faq.md:384
+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:386
+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:388
+msgid "I installed Synapse some other way. Can I migrate such a setup to the playbook?"
+msgstr ""
+
+#: ../../../docs/faq.md:390
+msgid "Yes, you can."
+msgstr ""
+
+#: ../../../docs/faq.md:392
+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:394
+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:396
+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:398
+msgid "I've downloaded Ansible and the playbook on the server. It can't connect using SSH."
+msgstr ""
+
+#: ../../../docs/faq.md:400
+msgid "If you're using the playbook directly on the server, then Ansible doesn't need to connect using SSH."
+msgstr ""
+
+#: ../../../docs/faq.md:402
+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:404
+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:406
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/faq.md:408
+msgid "I get \"Error response from daemon: configured logging driver does not support reading\" when I do `docker logs matrix-synapse`."
+msgstr ""
+
+#: ../../../docs/faq.md:410
+msgid "See [How can I see the logs?](#how-can-i-see-the-logs)."
+msgstr ""
+
+#: ../../../docs/faq.md:412
+msgid "How can I see the logs?"
+msgstr ""
+
+#: ../../../docs/faq.md:414
+msgid "We utilize [systemd/journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html#Description) for logging."
+msgstr ""
+
+#: ../../../docs/faq.md:416
+msgid "To see logs for Synapse, run `journalctl -fu matrix-synapse.service`. You may wish to see the [manual page for journalctl](https://www.commandlinux.com/man-page/man1/journalctl.1.html)."
+msgstr ""
+
+#: ../../../docs/faq.md:418
+msgid "Available service names can be seen by doing `ls /etc/systemd/system/matrix*.service` on the server."
+msgstr ""
+
+#: ../../../docs/faq.md:420
+msgid "Some services also log to files in `/matrix/*/data/..`, but we're slowly moving away from that."
+msgstr ""
+
+#: ../../../docs/faq.md:422
+msgid "We also disable Docker logging, so you can't use `docker logs matrix-*` either. We do this to prevent useless double (or even triple) logging and to avoid having to rotate log files."
+msgstr ""
+
+#: ../../../docs/faq.md:424
+msgid "We just simply delegate logging to journald and it takes care of persistence and expiring old data."
+msgstr ""
+
+#: ../../../docs/faq.md:426
+msgid "Also see: [How long do systemd/journald logs persist for?](#how-long-do-systemdjournald-logs-persist-for)"
+msgstr ""
+
+#: ../../../docs/faq.md:428
+msgid "How long do systemd/journald logs persist for?"
+msgstr ""
+
+#: ../../../docs/faq.md:430
+msgid "On some distros, the journald logs are just in-memory and not persisted to disk."
+msgstr ""
+
+#: ../../../docs/faq.md:432
+msgid "Consult (and feel free to adjust) your distro's journald logging configuration in `/etc/systemd/journald.conf`."
+msgstr ""
+
+#: ../../../docs/faq.md:434
+msgid "To enable persistence and put some limits on how large the journal log files can become, adjust your configuration like this:"
+msgstr ""
+
+#: ../../../docs/faq.md:445
+msgid "Maintenance"
+msgstr ""
+
+#: ../../../docs/faq.md:447
+msgid "Do I need to do anything to keep my Matrix server updated?"
+msgstr ""
+
+#: ../../../docs/faq.md:449
+msgid "Yes. We don't update anything for you automatically."
+msgstr ""
+
+#: ../../../docs/faq.md:451
+msgid "See our [documentation page about upgrading services](maintenance-upgrading-services.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:453
+msgid "How do I move my existing installation to another (VM) server?"
+msgstr ""
+
+#: ../../../docs/faq.md:455
+msgid "If you have an existing installation done using this Ansible playbook, you can easily migrate that to another server using [our dedicated server migration guide](maintenance-migrating.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:457
+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:459
+msgid "How do I back up the data on my server?"
+msgstr ""
+
+#: ../../../docs/faq.md:461
+msgid "We haven't documented this properly yet, but the general advice is to:"
+msgstr ""
+
+#: ../../../docs/faq.md:463
+msgid "back up Postgres by making a database dump. See [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql)"
+msgstr ""
+
+#: ../../../docs/faq.md:465
+msgid "back up all `/matrix` files, except for `/matrix/postgres/data` (you already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` (this directory may exist and contain your old data if you've [performed a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql))."
+msgstr ""
+
+#: ../../../docs/faq.md:467
+msgid "You can later restore these by:"
+msgstr ""
+
+#: ../../../docs/faq.md:469
+msgid "Restoring the `/matrix` directory and files on the new server manually"
+msgstr ""
+
+#: ../../../docs/faq.md:470
+msgid "Following the instruction described on [Installing a server into which you'll import old data](installing.md#installing-a-server-into-which-youll-import-old-data)"
+msgstr ""
+
+#: ../../../docs/faq.md:472
+msgid "If your server's IP address has changed, you may need to [set up DNS](configuring-dns.md) again."
+msgstr ""
+
+#: ../../../docs/faq.md:474
+msgid "What is this `/matrix/postgres/data-auto-upgrade-backup` directory that is taking up so much space?"
+msgstr ""
+
+#: ../../../docs/faq.md:476
+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:478
+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:480
+msgid "How do I debug or force SSL certificate renewal?"
+msgstr ""
+
+#: ../../../docs/faq.md:482
+msgid "SSL certificates are managed automatically by the [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server."
+msgstr ""
+
+#: ../../../docs/faq.md:484
+msgid "If you're having trouble with SSL certificate renewal, check the Traefik logs (`journalctl -fu matrix-traefik`)."
+msgstr ""
+
+#: ../../../docs/faq.md:486
+msgid "If you're [using your own webserver](configuring-playbook-own-webserver.md) instead of the integrated one (Traefik), you should investigate in another way."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/getting-the-playbook.po b/i18n/locales/bg/LC_MESSAGES/docs/getting-the-playbook.po
new file mode 100644
index 000000000..f381493e5
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/getting-the-playbook.po
@@ -0,0 +1,86 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/getting-the-playbook.md:1
+msgid "Getting the playbook"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:3
+msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > Getting the playbook > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)</sup>"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:5
+msgid "This Ansible playbook is meant to be executed on your own computer (not the Matrix server)."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:7
+msgid "In special cases (if your computer cannot run Ansible, etc.) you may put the playbook on the server as well."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:9
+msgid "You can retrieve the playbook's source code by:"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:11
+msgid "[Using git to get the playbook](#using-git-to-get-the-playbook) (recommended)"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:13
+msgid "[Downloading the playbook as a ZIP archive](#downloading-the-playbook-as-a-zip-archive) (not recommended)"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:15
+msgid "Using git to get the playbook"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:17
+msgid "We recommend using the [git](https://git-scm.com/) tool to get the playbook's source code, because it lets you easily keep up to date in the future when [Maintaining services](maintenance-upgrading-services.md)."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:19
+msgid "Once you've installed git on your computer, you can go to any directory of your choosing and run the following command to retrieve the playbook's source code:"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:25
+msgid "This will create a new `matrix-docker-ansible-deploy` directory. You're supposed to execute all other installation commands inside that directory."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:27
+msgid "Downloading the playbook as a ZIP archive"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:29
+msgid "Alternatively, you can download the playbook as a ZIP archive. This is not recommended, as it's not easy to keep up to date with future updates. We suggest you [use git](#using-git-to-get-the-playbook) instead."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:31
+msgid "The latest version is always at the following URL: https://github.com/spantaleev/matrix-docker-ansible-deploy/archive/master.zip"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:33
+msgid "You can extract this archive anywhere. You'll get a directory called `matrix-docker-ansible-deploy-master`. You're supposed to execute all other installation commands inside that directory."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:37
+msgid "[▶️](configuring-playbook.md) No matter which method you've used to download the playbook, you can proceed by [Configuring the playbook](configuring-playbook.md)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/howto-server-delegation.po b/i18n/locales/bg/LC_MESSAGES/docs/howto-server-delegation.po
new file mode 100644
index 000000000..3572ebe44
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/howto-server-delegation.po
@@ -0,0 +1,190 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-23 13:09+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/howto-server-delegation.md:1
+msgid "Server Delegation"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:3
+msgid "By default, this playbook sets up services on your Matrix server (`matrix.example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:5
+msgid "Server delegation can be configured in either of these ways:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:7
+msgid "[Setting up a `/.well-known/matrix/server` file](#server-delegation-via-a-well-known-file) on the base domain (`example.com`)"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:8
+msgid "[Setting up a `_matrix._tcp` DNS SRV record](#server-delegation-via-a-dns-srv-record-advanced)"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:10
+msgid "Both methods have their place and will continue to do so. You only need to use just one of these delegation methods."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:12
+msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file. However, that method may have some downsides that are not to your liking. Hence this guide about alternative ways to set up Server Delegation."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:14
+msgid "**Note**: as an alternative, it is possible to install the server such that it uses only the `matrix.example.com` domain (instead of identifying as the shorter base domain - `example.com`). This should be helpful if you are not in control of anything on the base domain (`example.com`). In this case, you would not need to configure server delegation, but you would need to add other configuration. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:16
+msgid "Server Delegation via a well-known file"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:18
+msgid "This playbook recommends you to set up server delegation by means of a `/.well-known/matrix/server` file served from the base domain (`example.com`), as this is the most straightforward way to set up the delegation."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:20
+msgid "To configure server delegation with the well-known file, check this section on [Configuring Service Discovery via .well-known](configuring-well-known.md): [Installing well-known files on the base domain's server](configuring-well-known.md#installing-well-known-files-on-the-base-domain-s-server)"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:22
+msgid "Downsides of well-known-based Server Delegation"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:24
+msgid "Server Delegation by means of a `/.well-known/matrix/server` file is the most straightforward, but suffers from the following downsides:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:26
+msgid "you need to have a working HTTPS server for the base domain (`example.com`). If you don't have any server for the base domain at all, you can easily solve it by making the playbook [serve the base domain from the Matrix server](configuring-playbook-base-domain-serving.md)."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:28
+msgid "any downtime on the base domain (`example.com`) or network trouble between the Matrix subdomain (`matrix.example.com`) and the base `example.com` may cause Matrix Federation outages. As the [Server-Server spec says](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery):"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:30
+msgid "Errors are recommended to be cached for up to an hour, and servers are encouraged to exponentially back off for repeated failures."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:32
+msgid "**For most people, this is a reasonable tradeoff** given that it's easy and straightforward to set up. We recommend you stay on this path."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:34
+msgid "Otherwise, you can decide to go against the default for this playbook, and instead set up [Server Delegation via a DNS SRV record (advanced)](#server-delegation-via-a-dns-srv-record-advanced) (much more complicated)."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:36
+msgid "Server Delegation via a DNS SRV record (advanced)"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:38
+msgid "**Note**: doing Server Delegation via a DNS SRV record is a more **advanced** way to do it and is not the default for this playbook. This is usually **much more complicated** to set up, so **we don't recommend it**. If you're not an experienced sysadmin, you'd better stay away from this."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:40
+msgid "As per the [Server-Server spec](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), it's possible to do Server Delegation using only a SRV record (without a `/.well-known/matrix/server` file)."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:42
+msgid "This prevents you from suffering the [Downsides of well-known-based Server Delegation](#downsides-of-well-known-based-server-delegation)."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:44
+msgid "To use DNS SRV record validation, you need to:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:46
+msgid "ensure that `/.well-known/matrix/server` is **not served** from the base domain, as that would interfere with DNS SRV record Server Delegation. To make the playbook **not** generate and serve the file, use the following configuration: `matrix_static_files_file_matrix_server_enabled: false`."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:48
+msgid "ensure that you have a `_matrix._tcp` DNS SRV record for your base domain (`example.com`) with a value of `10 0 8448 matrix.example.com`"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:50
+msgid "ensure that you are serving the Matrix Federation API (tcp/8448) with a certificate for `example.com` (not `matrix.example.com`!). Getting this certificate to the `matrix.example.com` server may be complicated. The playbook's automatic SSL obtaining/renewal flow will likely not work and you'll need to copy certificates around manually. See below."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:52
+msgid "For more details on how to configure the playbook to work with SRV delegation, take a look at this documentation: [Server Delegation via a DNS SRV record (advanced)](howto-srv-server-delegation.md)"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:54
+msgid "Obtain certificates"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:56
+msgid "How you can obtain a valid certificate for `example.com` on the `matrix.example.com` server is up to you."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:58
+msgid "If `example.com` and `matrix.example.com` are hosted on the same machine, you can let the playbook obtain the certificate for you, by following our [Obtaining SSL certificates for additional domains](configuring-playbook-ssl-certificates.md#obtaining-ssl-certificates-for-additional-domains) guide."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:60
+msgid "If `example.com` and `matrix.example.com` are not hosted on the same machine, you can copy over the certificate files manually. Don't forget that they may get renewed once in a while, so you may also have to transfer them periodically. How often you do that is up to you, as long as the certificate files don't expire."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:62
+msgid "Serving the Federation API with your certificates"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:64
+msgid "Regardless of which method for obtaining certificates you've used, once you've managed to get certificates for your base domain onto the `matrix.example.com` machine you can put them to use."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:66
+msgid "Based on your setup, you have different ways to go about it:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:68
+msgid "Serving the Federation API with your certificates and Synapse handling Federation"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:70
+msgid "You can let Synapse handle Federation by itself."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:72
+msgid "To do that, make sure the certificate files are mounted into the Synapse container:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:79
+msgid "You can then tell Synapse to serve Federation traffic over TLS on `tcp/8448`:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:87
+msgid "Make sure to reload Synapse once in a while (`systemctl reload matrix-synapse`), so that newer certificates can kick in. Reloading doesn't cause any downtime."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:89
+msgid "Serving the Federation API with your certificates and another webserver"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:91
+msgid "**Alternatively**, if you are using another webserver, you can set up reverse-proxying for the `tcp/8448` port by yourself. Make sure to use the proper certificates for `example.com` (not for `matrix.example.com`) when serving the `tcp/8448` port."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:93
+msgid "As recommended in our [Fronting the integrated reverse-proxy webserver with another reverse-proxy](./configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) documentation section, we recommend you to expose the Matrix Federation entrypoint from traffic at a local port (e.g. `127.0.0.1:8449`), so your reverese-proxy should send traffic there."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/howto-srv-server-delegation.po b/i18n/locales/bg/LC_MESSAGES/docs/howto-srv-server-delegation.po
new file mode 100644
index 000000000..e315fb1c8
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/howto-srv-server-delegation.po
@@ -0,0 +1,150 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/howto-srv-server-delegation.md:1
+msgid "Server Delegation via a DNS SRV record (advanced)"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:3
+msgid "**Reminder** : unless you are affected by the [Downsides of well-known-based Server Delegation](howto-server-delegation.md#downsides-of-well-known-based-server-delegation), we suggest you **stay on the simple/default path**: [Server Delegation](howto-server-delegation.md) by [configuring well-known files](configuring-well-known.md) at the base domain."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:5
+msgid "This guide is about configuring Server Delegation using DNS SRV records (for the [Traefik](https://doc.traefik.io/traefik/) webserver). This method has special requirements when it comes to SSL certificates, so various changes are required."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:7
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:9
+msgid "SRV delegation while still using the playbook provided Traefik to get / renew the certificate requires a wildcard certificate."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:11
+msgid "To obtain / renew one from [Let's Encrypt](https://letsencrypt.org/), one needs to use a [DNS-01 challenge](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) method instead of the default [HTTP-01](https://letsencrypt.org/docs/challenge-types/#http-01-challenge)."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:13
+msgid "This means that this is **limited to the list of DNS providers supported by Traefik**, unless you bring in your own certificate."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:15
+msgid "The up-to-date list can be accessed on [traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers)"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:17
+msgid "The changes"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:19
+msgid "**Note**: the changes below instruct you how to do this for a basic Synapse installation. You will need to adapt the variable name and the content of the labels:"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:21
+msgid "if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md) or [Dendrite](./configuring-playbook-dendrite.md))"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:22
+msgid "if you're using [Synapse with workers enabled](./configuring-playbook-synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled: true`). In that case, it's actually the `matrix-synapse-reverse-proxy-companion` service which has Traefik labels attached"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:24
+msgid "Also, all instructions below are from an older version of the playbook and may not work anymore."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:26
+msgid "Federation Endpoint"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:33
+msgid "This is because with SRV federation, some servers / tools (one of which being the federation tester) try to access the federation API using the resolved IP address instead of the domain name (or they are not using SNI). This change will make Traefik route all traffic for which the path match this rule go to the federation endpoint."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:35
+msgid "Tell Traefik which certificate to serve for the federation endpoint"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:37
+msgid "Now that the federation endpoint is not bound to a domain anymore we need to explicitely tell Traefik to use a wildcard certificate in addition to one containing the base name."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:39
+msgid "This is because the Matrix specification expects the federation endpoint to be served using a certificate compatible with the base domain, however, the other resources on the endpoint still need a valid certificate to work."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:48
+msgid "Configure the DNS-01 challenge for let's encrypt"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:50
+msgid "Since we're now requesting a wildcard certificate, we need to change the ACME challenge method. To request a wildcard certificate from Let's Encrypt we are required to use the DNS-01 challenge."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:52
+msgid "This will need 3 changes:"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:53
+msgid "Add a new certificate resolver that works with DNS-01"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:54
+msgid "Configure the resolver to allow access to the DNS zone to configure the records to answer the challenge (refer to [Traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers) to know which environment variables to set)"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:55
+msgid "Tell the playbook to use the new resolver as default"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:57
+msgid "We cannot just disable the default resolver as that would disable SSL in quite a few places in the playbook."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:86
+msgid "Adjust Coturn's configuration"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:88
+msgid "The last step is to alter the generated Coturn configuration."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:90
+msgid "By default, Coturn is configured to wait on the certificate for the `matrix.` subdomain using an [instantiated systemd service](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Service%20Templates) using the domain name as the parameter for this service. However, we need to serve the wildcard certificate, which is incompatible with systemd, it will try to expand the `*`, which will break and prevent Coturn from starting."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:92
+msgid "We also need to indicate to Coturn where the wildcard certificate is."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:94
+msgid "**⚠️ WARNING ⚠️** : On first start of the services, Coturn might still fail to start because Traefik is still in the process of obtaining the certificates. If you still get an error, make sure Traefik obtained the certificates and restart the Coturn service (`just start-group coturn`)."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:96
+msgid "This should not happen again afterwards as Traefik will renew certificates well before their expiry date, and the Coturn service is setup to restart periodically."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:122
+msgid "Full example of a working configuration"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/importing-postgres.po b/i18n/locales/bg/LC_MESSAGES/docs/importing-postgres.po
new file mode 100644
index 000000000..f6a164585
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/importing-postgres.po
@@ -0,0 +1,150 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/importing-postgres.md:1
+msgid "Importing an existing Postgres database from another installation (optional)"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:3
+msgid "Run this if you'd like to import your database from a previous installation. (don't forget to import your Synapse `media_store` files as well - see [the importing-synape-media-store guide](importing-synapse-media-store.md))."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:6
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:8
+msgid "For this to work, **the database name in Postgres must match** what this playbook uses. This playbook uses a Postgres database name of `synapse` by default (controlled by the `matrix_synapse_database_database` variable). If your database name differs, be sure to change `matrix_synapse_database_database` to your desired name and to re-run the playbook before proceeding."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:10
+msgid "The playbook supports importing Postgres dump files in **text** (e.g. `pg_dump > dump.sql`) or **gzipped** formats (e.g. `pg_dump | gzip -c > dump.sql.gz`). Importing multiple databases (as dumped by `pg_dumpall`) is also supported."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:12
+msgid "The migration might be a good moment, to \"reset\" a not properly working bridge. Be aware, that it might affect all users (new link to bridge, new rooms, …)"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:14
+msgid "Before doing the actual import, **you need to upload your Postgres dump file to the server** (any path is okay)."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:16
+msgid "Importing"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:18
+msgid "To import, run this command (make sure to replace `SERVER_PATH_TO_POSTGRES_DUMP_FILE` with a file path on your server):"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:26
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:28
+msgid "`SERVER_PATH_TO_POSTGRES_DUMP_FILE` must be a file path to a Postgres dump file on the server (not on your local machine!)"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:29
+msgid "`postgres_default_import_database` defaults to `matrix`, which is useful for importing multiple databases (for dumps made with `pg_dumpall`). If you're importing a single database (e.g. `synapse`), consider changing `postgres_default_import_database` accordingly"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:30
+msgid "after importing a large database, it's a good idea to run [an `ANALYZE` operation](https://www.postgresql.org/docs/current/sql-analyze.html) to make Postgres rebuild its database statistics and optimize its query planner. You can easily do this via the playbook by running `just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze` (see [Vacuuming PostgreSQL](maintenance-postgres.md#vacuuming-postgresql) for more details)."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:32
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:34
+msgid "Table Ownership"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:36
+msgid "A table ownership issue can occur if you are importing from a Synapse installation which was both:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:38
+msgid "migrated from SQLite to Postgres, and"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:39
+msgid "used a username other than 'synapse'"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:41
+msgid "In this case you may run into the following error during the import task:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:47
+msgid "where `synapse_user` is the database username from the previous Synapse installation."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:49
+msgid "This can be verified by examining the dump for ALTER TABLE statements which set OWNER TO that username:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:61
+msgid "It can be worked around by changing the username to `synapse`, for example by using `sed`:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:67
+msgid "This uses sed to perform an 'in-place' (`-i`) replacement globally (`/g`), searching for `synapse_user` and replacing with `synapse` (`s/synapse_user/synapse`). If your database username was different, change `synapse_user` to that username instead. Expand search/replace statement as shown in example above, in case of old user name like `matrix` - replacing `matrix` only would… well - you can imagine."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:69
+msgid "Note that if the previous import failed with an error it may have made changes which are incompatible with re-running the import task right away; if you do so it may fail with an error such as:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:75
+msgid "Repeat import"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:77
+msgid "In this case you can use the command suggested in the import task to clear the database before retrying the import:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:85
+msgid "Now on your local machine run `just run-tags setup-postgres` to prepare the database roles etc."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:87
+msgid "If not, you probably get this error. `synapse` is the correct table owner, but the role is missing in database."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:93
+msgid "Once the database is clear and the ownership of the tables has been fixed in the SQL file, the import task should succeed."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:95
+msgid "Check, if `--dbname` is set to `synapse` (not `matrix`) and replace paths (or even better, copy this line from your terminal)"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:101
+msgid "Hints"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:103
+msgid "To open psql terminal run `/matrix/postgres/bin/cli`"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-media-store.po b/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-media-store.po
new file mode 100644
index 000000000..345710043
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-media-store.po
@@ -0,0 +1,62 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/importing-synapse-media-store.md:1
+msgid "Importing `media_store` data files from an existing Synapse installation (optional)"
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:3
+msgid "Run this if you'd like to import your `media_store` files from a previous installation of Synapse."
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:5
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:7
+msgid "Before doing the actual data restore, **you need to upload your media store directory to the server** (any path is okay)."
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:9
+msgid "If you are [storing Matrix media files on Amazon S3](configuring-playbook-s3.md) (optional), restoring with this tool is not possible right now."
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:11
+msgid "As an alternative, you can perform a manual restore using the [AWS CLI tool](https://aws.amazon.com/cli/) (e.g. `aws s3 sync /path/to/server/media_store/. s3://name-of-bucket/`)"
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:13
+msgid "**Note for Mac users**: Due to case-sensitivity issues on certain Mac filesystems (HFS or HFS+), filename corruption may occur if you copy a `media_store` directory to your Mac. If you're transferring a `media_store` directory between 2 servers, make sure you do it directly (from server to server with a tool such as [rsync](https://rsync.samba.org/)), and not by downloading the files to your Mac."
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:15
+msgid "Importing"
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:17
+msgid "Run this command (make sure to replace `<server-path-to-media_store>` with a path on your server):"
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:23
+msgid "**Note**: `<server-path-to-media_store>` must be a file path to a `media_store` directory on the server (not on your local machine!)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-sqlite.po b/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-sqlite.po
new file mode 100644
index 000000000..c14221242
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/importing-synapse-sqlite.po
@@ -0,0 +1,74 @@
+# Translations template for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\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"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/importing-synapse-sqlite.md:1
+msgid "Importing an existing SQLite database from another Synapse installation (optional)"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:3
+msgid "Run this if you'd like to import your database from a previous default installation of Synapse (don't forget to import your `media_store` files as well - see [the importing-synapse-media-store guide](importing-synapse-media-store.md))."
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:5
+msgid "While this playbook only supports running Synapse in combination with PostgreSQL, a Synapse instance installed manually usually defaults to using an SQLite database."
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:7
+msgid "If you have such a Synapse setup and wish to migrate it to one managed by the playbook (and over to PostgreSQL), this documentation page is for you."
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:11
+msgid "Before doing the actual import:"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:13
+msgid "**ensure you have NOT started Synapse yet**. That is, make sure you have followed the [Installing step](installing.md), but haven't run the playbook's `start` tag yet. If you had started your new Synapse instance, it may have already initialized your Postgres database and importing onto it may not work. In such cases, you may need to clean up the `synapse` database first."
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:14
+msgid "**ensure you have uploaded your SQLite database file to the server** (any path is okay)"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:15
+msgid "if you're using the integrated Postgres server (**by default, you are** using it, unless you've explicitly switched to [Using an external PostgreSQL server](configuring-playbook-external-postgres.md)), **make sure Postgres is started** by running `just start-group postgres`"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:17
+msgid "Importing"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:19
+msgid "Run this command (make sure to replace `<server-path-to-homeserver.db>` with a file path on your server):"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:25
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:27
+msgid "`<server-path-to-homeserver.db>` must be replaced with a file path to a `homeserver.db` **file on the server** (not on your local machine!)."
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:28
+msgid "if the SQLite database is from an older version of Synapse, the **importing procedure may run migrations on it to bring it up to date**. That is, your SQLite database file may get modified and become unusable with your older Synapse version. Keeping a copy of the original is probably wise."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/installing.po b/i18n/locales/bg/LC_MESSAGES/docs/installing.po
new file mode 100644
index 000000000..7240f0158
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/installing.po
@@ -0,0 +1,306 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/installing.md:1
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/installing.md:3
+msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > Installing</sup>"
+msgstr ""
+
+#: ../../../docs/installing.md:5
+msgid "If you've configured your DNS records and the playbook, you can start the installation procedure."
+msgstr ""
+
+#: ../../../docs/installing.md:7
+msgid "Update Ansible roles"
+msgstr ""
+
+#: ../../../docs/installing.md:9
+msgid "Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside."
+msgstr ""
+
+#: ../../../docs/installing.md:11
+msgid "To update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file), run:"
+msgstr ""
+
+#: ../../../docs/installing.md:13
+msgid "either: `just update`"
+msgstr ""
+
+#: ../../../docs/installing.md:14
+msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)"
+msgstr ""
+
+#: ../../../docs/installing.md:16
+msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`"
+msgstr ""
+
+#: ../../../docs/installing.md:18
+msgid "For details about `just` commands, take a look at: [Running `just` commands](just.md)."
+msgstr ""
+
+#: ../../../docs/installing.md:20
+msgid "Install Matrix server and services"
+msgstr ""
+
+#: ../../../docs/installing.md:22
+msgid "The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks."
+msgstr ""
+
+#: ../../../docs/installing.md:24
+msgid "The general command syntax for installation (and also maintenance) is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`. It is recommended to get yourself familiar with the [playbook tags](playbook-tags.md) before proceeding."
+msgstr ""
+
+#: ../../../docs/installing.md:26
+msgid "If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the all Ansible commands."
+msgstr ""
+
+#: ../../../docs/installing.md:28
+msgid "If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to all Ansible commands."
+msgstr ""
+
+#: ../../../docs/installing.md:30
+msgid "There 2 ways to start the installation process - depending on whether you're [Installing a brand new server (without importing data)](#installing-a-brand-new-server-without-importing-data) or [Installing a server into which you'll import old data](#installing-a-server-into-which-youll-import-old-data)."
+msgstr ""
+
+#: ../../../docs/installing.md:32
+msgid "**Note**: if you are migrating from an old server to a new one, take a look at [this guide](maintenance-migrating.md) instead. This is an easier and more straightforward way than installing a server and importing old data into it."
+msgstr ""
+
+#: ../../../docs/installing.md:34
+msgid "Installing a brand new server (without importing data)"
+msgstr ""
+
+#: ../../../docs/installing.md:36
+msgid "If this is **a brand new** Matrix server and you **won't be importing old data into it**, run all these tags:"
+msgstr ""
+
+#: ../../../docs/installing.md:42
+msgid "This will do a full installation and start all Matrix services."
+msgstr ""
+
+#: ../../../docs/installing.md:44
+msgid "**Note**: if the command does not work as expected, make sure that you have properly installed and configured software required to run the playbook, as described on [Prerequisites](prerequisites.md)."
+msgstr ""
+
+#: ../../../docs/installing.md:46
+msgid "Installing a server into which you'll import old data"
+msgstr ""
+
+#: ../../../docs/installing.md:48
+msgid "If you will be importing data into your newly created Matrix server, install it, but **do not** start its services just yet. Starting its services or messing with its database now will affect your data import later on."
+msgstr ""
+
+#: ../../../docs/installing.md:50
+msgid "To do the installation **without** starting services, run `ansible-playbook` with the `install-all` tag only:"
+msgstr ""
+
+#: ../../../docs/installing.md:56
+msgid "⚠️ **Warning**: do not run the just \"recipe\" `just install-all` instead, because it automatically starts services at the end of execution. See: [Difference between playbook tags and shortcuts](just.md#difference-between-playbook-tags-and-shortcuts)"
+msgstr ""
+
+#: ../../../docs/installing.md:58
+msgid "When this command completes, services won't be running yet."
+msgstr ""
+
+#: ../../../docs/installing.md:60
+msgid "You can now:"
+msgstr ""
+
+#: ../../../docs/installing.md:62
+msgid "[Importing an existing SQLite database (from another Synapse installation)](importing-synapse-sqlite.md) (optional)"
+msgstr ""
+
+#: ../../../docs/installing.md:64
+msgid "[Importing an existing Postgres database (from another installation)](importing-postgres.md) (optional)"
+msgstr ""
+
+#: ../../../docs/installing.md:66
+msgid "[Importing `media_store` data files from an existing Synapse installation](importing-synapse-media-store.md) (optional)"
+msgstr ""
+
+#: ../../../docs/installing.md:68
+msgid ".. and then proceed to starting all services:"
+msgstr ""
+
+#: ../../../docs/installing.md:74
+msgid "Create your user account"
+msgstr ""
+
+#: ../../../docs/installing.md:76
+msgid "ℹ️ *You can skip this step if you have installed a server and imported old data to it.*"
+msgstr ""
+
+#: ../../../docs/installing.md:78
+msgid "As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server."
+msgstr ""
+
+#: ../../../docs/installing.md:80
+msgid "After creating the user account, you can log in to it with [Element Web](configuring-playbook-client-element-web.md) that this playbook has installed for you at this URL: `https://element.example.com/`."
+msgstr ""
+
+#: ../../../docs/installing.md:82
+msgid "To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer."
+msgstr ""
+
+#: ../../../docs/installing.md:84
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/installing.md:85
+msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`"
+msgstr ""
+
+#: ../../../docs/installing.md:86
+msgid "For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)"
+msgstr ""
+
+#: ../../../docs/installing.md:87
+msgid "Use `admin=yes` to make your user account an administrator of the Matrix server"
+msgstr ""
+
+#: ../../../docs/installing.md:95
+msgid "Feel free to create as many accounts (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your account only (with `admin=yes`), and others should be created with `admin=no`."
+msgstr ""
+
+#: ../../../docs/installing.md:97
+msgid "For more information, see the documentation for [registering users](registering-users.md)."
+msgstr ""
+
+#: ../../../docs/installing.md:99
+msgid "Finalize the installation"
+msgstr ""
+
+#: ../../../docs/installing.md:101
+msgid "Now you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network."
+msgstr ""
+
+#: ../../../docs/installing.md:103
+msgid "This is required for federation to work! Without a proper configuration, your server will effectively not be part of the Matrix network."
+msgstr ""
+
+#: ../../../docs/installing.md:105
+msgid "To configure the delegation, you have these two options. Choose one of them according to your situation."
+msgstr ""
+
+#: ../../../docs/installing.md:107
+msgid "If you can afford to point the base domain at the Matrix server, follow the instructions below which guide you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server. It will enable you to use a Matrix user ID like `@alice:example.com` while hosting services on a subdomain like `matrix.example.com`."
+msgstr ""
+
+#: ../../../docs/installing.md:108
+msgid "Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot \"serve the base domain\" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server), but feel free to familiarize yourself with all [server delegation (redirection) options](howto-server-delegation.md)."
+msgstr ""
+
+#: ../../../docs/installing.md:110
+msgid "To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/installing.md:116
+msgid "After configuring the playbook, run the command below:"
+msgstr ""
+
+#: ../../../docs/installing.md:122
+msgid "Things to do next"
+msgstr ""
+
+#: ../../../docs/installing.md:124
+msgid "After finilizing the installation, you can:"
+msgstr ""
+
+#: ../../../docs/installing.md:126
+msgid "[check if services work](maintenance-checking-services.md)"
+msgstr ""
+
+#: ../../../docs/installing.md:127
+msgid "or [set up additional services](configuring-playbook.md#other-configuration-options) (bridges to other chat networks, bots, etc.)"
+msgstr ""
+
+#: ../../../docs/installing.md:128
+msgid "or learn how to [upgrade services when new versions are released](maintenance-upgrading-services.md)"
+msgstr ""
+
+#: ../../../docs/installing.md:129
+msgid "or learn how to [maintain your server](faq.md#maintenance)"
+msgstr ""
+
+#: ../../../docs/installing.md:130
+msgid "or join some Matrix rooms:"
+msgstr ""
+
+#: ../../../docs/installing.md:131
+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."
+msgstr ""
+
+#: ../../../docs/installing.md:132
+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:133
+msgid "or help make this playbook better by contributing (code, documentation, or [coffee/beer](https://liberapay.com/s.pantaleev/donate))"
+msgstr ""
+
+#: ../../../docs/installing.md:135
+msgid "Maintaining your setup in the future"
+msgstr ""
+
+#: ../../../docs/installing.md:137
+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:139
+msgid "The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities."
+msgstr ""
+
+#: ../../../docs/installing.md:141
+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:143
+msgid "For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)"
+msgstr ""
+
+#: ../../../docs/installing.md:145
+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:151
+msgid "**Note**: see [this page on the playbook tags](playbook-tags.md) for more information about those tags."
+msgstr ""
+
+#: ../../../docs/installing.md:153
+msgid "Make full use of `just` shortcut commands"
+msgstr ""
+
+#: ../../../docs/installing.md:155
+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:157
+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:159
+msgid "You can learn about the shortcut commands on this page: [Running `just` commands](just.md)"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/just.po b/i18n/locales/bg/LC_MESSAGES/docs/just.po
new file mode 100644
index 000000000..b6a4f5f16
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/just.po
@@ -0,0 +1,162 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/just.md:1
+msgid "Running `just` commands"
+msgstr ""
+
+#: ../../../docs/just.md:3
+msgid "We have previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers [`ansible-galaxy`](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html)). Our [`Makefile`](../Makefile) is still around, and you can still run these commands."
+msgstr ""
+
+#: ../../../docs/just.md:5
+msgid "In addition, we have added support for running commands via [`just`](https://github.com/casey/just) - a more modern command-runner alternative to `make`. It can be used to invoke `ansible-playbook` commands with less typing."
+msgstr ""
+
+#: ../../../docs/just.md:7
+msgid "The `just` utility executes shortcut commands (called as \"recipes\"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile). Most of the just recipes have no corresponding `Makefile` targets."
+msgstr ""
+
+#: ../../../docs/just.md:9
+msgid "For some recipes such as `just update`, our `justfile` recommends installing [`agru`](https://github.com/etkecc/agru) (a faster alternative to `ansible-galaxy`) to speed up the process."
+msgstr ""
+
+#: ../../../docs/just.md:11
+msgid "Here are some examples of shortcuts:"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Shortcut"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Result"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just roles`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Install the necessary Ansible roles pinned in [`requirements.yml`](../requirements.yml)"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just update`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Run `git pull` (to update the playbook) and install the Ansible roles"
+msgstr ""
+
+#: ../../../docs/just.md ../../../docs/just.md:33
+msgid "`just install-all`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just setup-all`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just install-all --ask-vault-pass`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Run commands with additional arguments (`--ask-vault-pass` will be appended to the above installation command)"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just run-tags install-mautrix-slack,start`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Run specific playbook tags (here `install-mautrix-slack` and `start`)"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just install-service mautrix-slack`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Run `just run-tags install-mautrix-slack,start` with even less typing"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just start-all`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "(Re-)starts all services"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just stop-group postgres`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Stop only the Postgres service"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just register-user alice secret-password yes`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)"
+msgstr ""
+
+#: ../../../docs/just.md:26
+msgid "While [our documentation on prerequisites](prerequisites.md) lists `just` as one of the requirements for installation, using `just` is optional. If you find it difficult to install it, do not find it useful, or want to prefer raw `ansible-playbook` commands for some reason, feel free to run all commands manually. For example, you can run `ansible-galaxy` directly to install the Ansible roles: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`."
+msgstr ""
+
+#: ../../../docs/just.md:28
+msgid "Difference between playbook tags and shortcuts"
+msgstr ""
+
+#: ../../../docs/just.md:30
+msgid "It is worth noting that `just` \"recipes\" are different from [playbook tags](playbook-tags.md). The recipes are shortcuts of commands defined in `justfile` and can be executed by the `just` program only, while the playbook tags are available for the raw `ansible-playbook` commands as well. Please be careful not to confuse them."
+msgstr ""
+
+#: ../../../docs/just.md:32
+msgid "For example, these two commands are different:"
+msgstr ""
+
+#: ../../../docs/just.md:34
+msgid "`ansible-playbook -i inventory/hosts setup.yml --tags=install-all`"
+msgstr ""
+
+#: ../../../docs/just.md:36
+msgid "The just recipe runs `ensure-matrix-users-created` and `start` tags after `install-all`, while the latter runs only `install-all` tag. The correct shortcut of the latter is `just run-tags install-all`."
+msgstr ""
+
+#: ../../../docs/just.md:38
+msgid "Such kind of difference sometimes matters. For example, when you install a Matrix server into which you will import old data (see [here](installing.md#installing-a-server-into-which-youll-import-old-data)), you are not supposed to run `just install-all` or `just setup-all`, because these commands start services immediately after installing components which may prevent your from importing old data."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-and-troubleshooting.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-and-troubleshooting.po
new file mode 100644
index 000000000..0cac254c2
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-and-troubleshooting.po
@@ -0,0 +1,94 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/maintenance-and-troubleshooting.md:1
+msgid "Maintenance and Troubleshooting"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:3
+msgid "How to see the current status of your services"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:5
+msgid "You can check the status of your services by using `systemctl status`. Example:"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:15
+msgid "Docker containers that the playbook configures are supervised by [systemd](https://wiki.archlinux.org/title/Systemd) and their logs are configured to go to [systemd-journald](https://wiki.archlinux.org/title/Systemd/Journal)."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:17
+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`."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:19
+msgid "To view systemd-journald logs using [journalctl](https://man.archlinux.org/man/journalctl.1), run a command like this:"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:25
+msgid "Increasing Synapse logging"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:27
+msgid "Because the [Synapse](https://github.com/element-hq/synapse) Matrix server 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/maintenance-and-troubleshooting.md:29
+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 increasing the logging level to `INFO`."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:31
+msgid "Example configuration (`inventory/host_vars/matrix.example.com/vars.yml`):"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:39
+msgid "Re-run the playbook after making these configuration changes."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:41
+msgid "Remove unused Docker data"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:43
+msgid "You can free some disk space from Docker, see [docker system prune](https://docs.docker.com/engine/reference/commandline/system_prune/) for more information."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:49
+msgid "The shortcut command with `just` program is also available: `just run-tags run-docker-prune`"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:51
+msgid "Postgres"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:53
+msgid "See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) documentation page."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:55
+msgid "Ma1sd"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:57
+msgid "See the dedicated [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md) documentation page."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-checking-services.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-checking-services.po
new file mode 100644
index 000000000..fe81bb15d
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-checking-services.po
@@ -0,0 +1,46 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/maintenance-checking-services.md:1
+msgid "Checking if services work"
+msgstr ""
+
+#: ../../../docs/maintenance-checking-services.md:3
+msgid "This playbook can perform a check to ensure that you've configured things correctly and that services are running."
+msgstr ""
+
+#: ../../../docs/maintenance-checking-services.md:5
+msgid "To perform the check, run:"
+msgstr ""
+
+#: ../../../docs/maintenance-checking-services.md:11
+msgid "The shortcut command with `just` program is also available: `just run-tags self-check`"
+msgstr ""
+
+#: ../../../docs/maintenance-checking-services.md:13
+msgid "If it's all green, everything is probably running correctly."
+msgstr ""
+
+#: ../../../docs/maintenance-checking-services.md:15
+msgid "Besides this self-check, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-migrating.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-migrating.po
new file mode 100644
index 000000000..a82fdaf44
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-migrating.po
@@ -0,0 +1,138 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/maintenance-migrating.md:1
+msgid "Migrating to new server"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:3
+msgid "This documentation explains how to migrate your Matrix services (server, client, bridges, etc.) and data **from an old server to a new server**."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:5
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:6
+msgid "This migration guide is applicable if you migrate from one server to another server having the same CPU architecture (e.g. both servers being `amd64`)."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:8
+msgid "If you're trying to migrate between different architectures (e.g. `amd64` --> `arm64`), simply copying the complete `/matrix` directory is **not** possible as it would move the raw PostgreSQL data (`/matrix/postgres/data`) between different architectures. In this specific case, you can use the guide below as a reference, but you would also need to avoid syncing `/matrix/postgres/data` to the new host, and also dump the database on your current server and import it properly on the new server. See our [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql) docs for help with PostgreSQL backup/restore."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:9
+msgid "If you have any questions about migration or encountered an issue during migration, do not hesitate to ask for help on [our Matrix room](https://matrix.to/#/%23matrix-docker-ansible-deploy:devture.com). You probably might want to prepare a temporary/sub account on another Matrix server in case it becomes impossible to use your server due to migration failure by any chance."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:11
+msgid "You can't change the domain (specified in the `matrix_domain` variable) after the initial deployment."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:13
+msgid "Lower DNS TTL"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:15
+msgid "Prepare by lowering DNS TTL for your domains (`matrix.example.com`, etc.), so that DNS record changes would happen faster, leading to less downtime."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:17
+msgid "Stop services on the old server completely"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:19
+msgid "Before migrating, you need to stop all services on the old server and make sure they won't be starting again."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:21
+msgid "To do so, it is recommended to run the `systemctl` command on the server. Running the playbook's `stop` tag also stops the services, but just once; they will start again if you reboot the server."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:23
+msgid "Log in to the old server and run the command as `root` (or a user that can run it with `sudo`):"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:29
+msgid "Copy data directory to the new server"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:31
+msgid "After you've confirmed that all services were stopped, copy the `/matrix` directory from the old server to the new server. When copying, make sure to preserve ownership and permissions (use `cp -p` or `rsync -ar`)!"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:33
+msgid "Adjust DNS records"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:35
+msgid "Make sure your DNS records are adjusted to point to the new server's IP address."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:37
+msgid "Update `inventory/hosts` file"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:39
+msgid "Having adjusted DNS records, replace the old server's external IP address on the `inventory/hosts` file with that of the new server."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:41
+msgid "Create `matrix` user and group on the new server"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:43
+msgid "Then, run the command below on your local computer to create the `matrix` user and group on the new server:"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:49
+msgid "The shortcut command with `just` program is also available: `just run-tags setup-system-user`"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:51
+msgid "**Note**: because the `matrix` user and group are created dynamically on each server, the user/group ID may differ between the old and new server. We suggest that you adjust ownership of `/matrix` files. To adjust the ownership, log in to the new server and run the command:"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:57
+msgid "Install and start all services on the new server"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:59
+msgid "Finally, run the command below on your local computer to finish the installation and start all services:"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:65
+msgid "The shortcut command with `just` program is also available: `just run-tags install-all,start`"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:67
+msgid "Check if services work"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:69
+msgid "After starting the services, you probably might want to ensure that you've migrated things correctly and that services are running. For instructions, see: [check if services work](maintenance-checking-services.md)"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:71
+msgid "Having make sure that both services and federation work as expected, you can safely shutdown the old server."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-postgres.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-postgres.po
new file mode 100644
index 000000000..5cea97a95
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-postgres.po
@@ -0,0 +1,222 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/maintenance-postgres.md:1
+msgid "PostgreSQL maintenance"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:3
+msgid "This document shows you how to perform various maintenance tasks related to the Postgres database server used by Matrix."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:5
+msgid "Table of contents:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:7
+msgid "[Getting a database terminal](#getting-a-database-terminal), for when you wish to execute SQL queries"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:9
+msgid "[Vacuuming PostgreSQL](#vacuuming-postgresql), for when you wish to run a Postgres [VACUUM](https://www.postgresql.org/docs/current/sql-vacuum.html) (optimizing disk space)"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:11
+msgid "[Backing up PostgreSQL](#backing-up-postgresql), for when you wish to make a backup"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:13
+msgid "[Upgrading PostgreSQL](#upgrading-postgresql), for upgrading to new major versions of PostgreSQL. Such **manual upgrades are sometimes required**."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:15
+msgid "[Tuning PostgreSQL](#tuning-postgresql) to make it run faster"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:17
+msgid "Getting a database terminal"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:19
+msgid "You can use the `/matrix/postgres/bin/cli` tool to get interactive terminal access ([psql](https://www.postgresql.org/docs/11/app-psql.html)) to the PostgreSQL server."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:21
+msgid "If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above tool will not be available."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:23
+msgid "By default, this tool puts you in the `matrix` database, which contains nothing."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:25
+msgid "To see the available databases, run `\\list` (or just `\\l`)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:27
+msgid "To change to another database (for example `synapse`), run `\\connect synapse` (or just `\\c synapse`)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:29
+msgid "You can then proceed to write queries. Example: `SELECT COUNT(*) FROM users;`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:31
+msgid "**Be careful**. Modifying the database directly (especially as services are running) is dangerous and may lead to irreversible database corruption. When in doubt, consider [making a backup](#backing-up-postgresql)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:33
+msgid "Vacuuming PostgreSQL"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:35
+msgid "Deleting lots data from Postgres does not make it release disk space, until you perform a [`VACUUM` operation](https://www.postgresql.org/docs/current/sql-vacuum.html)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:37
+msgid "You can run different `VACUUM` operations via the playbook, with the default preset being `vacuum-complete`:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:39
+msgid "(default) `vacuum-complete`: stops all services temporarily and runs `VACUUM FULL VERBOSE ANALYZE`."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:40
+msgid "`vacuum-full`: stops all services temporarily and runs `VACUUM FULL VERBOSE`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:41
+msgid "`vacuum`: runs `VACUUM VERBOSE` without stopping any services"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:42
+msgid "`vacuum-analyze` runs `VACUUM VERBOSE ANALYZE` without stopping any services"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:43
+msgid "`analyze` runs `ANALYZE VERBOSE` without stopping any services (this is just [ANALYZE](https://www.postgresql.org/docs/current/sql-analyze.html) without doing a vacuum, so it's faster)"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:45
+msgid "**Note**: for the `vacuum-complete` and `vacuum-full` presets, you'll need plenty of available disk space in your Postgres data directory (usually `/matrix/postgres/data`). These presets also stop all services (e.g. Synapse, etc.) while the vacuum operation is running."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:47
+msgid "Example playbook invocations:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:49
+msgid "`just run-tags run-postgres-vacuum`: runs the default `vacuum-complete` preset and restarts all services"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:50
+msgid "`just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze`: runs the `analyze` preset with all services remaining operational at all times"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:52
+msgid "Backing up PostgreSQL"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:54
+msgid "To automatically make Postgres database backups on a fixed schedule, see [Setting up postgres backup](configuring-playbook-postgres-backup.md)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:56
+msgid "To make a one off back up of the current PostgreSQL database, make sure it's running and then execute a command like this on the server:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:67
+msgid "If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above command will not work, because neither the credentials file (`/matrix/postgres/env-postgres-psql`), nor the `matrix-postgres` container is available."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:69
+msgid "Restoring a backup made this way can be done by [importing it](importing-postgres.md)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:71
+msgid "Upgrading PostgreSQL"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:73
+msgid "Unless you are using an [external Postgres server](configuring-playbook-external-postgres.md), this playbook initially installs Postgres for you."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:75
+msgid "Once installed, the playbook attempts to preserve the Postgres version it starts with. This is because newer Postgres versions cannot start with data generated by older Postgres versions."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:77
+msgid "Upgrades must be performed manually."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:79
+msgid "This playbook can upgrade your existing Postgres setup with the following command:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:85
+msgid "**The old Postgres data directory is backed up** automatically, by renaming it to `/matrix/postgres/data-auto-upgrade-backup`. To rename to a different path, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_auto_upgrade_backup_data_path=/another/disk/matrix-postgres-before-upgrade\"`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:87
+msgid "The auto-upgrade-backup directory stays around forever, until you **manually decide to delete it**."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:89
+msgid "As part of the upgrade, the database is dumped to `/tmp`, an upgraded and empty Postgres server is started, and then the dump is restored into the new server. To use a different directory for the dump, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_dump_dir=/directory/to/dump/here\"`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:91
+msgid "To save disk space in `/tmp`, the dump file is gzipped on the fly at the expense of CPU usage. If you have plenty of space in `/tmp` and would rather avoid gzipping, you can explicitly pass a dump filename which doesn't end in `.gz`. Example: `--extra-vars=\"postgres_dump_name=matrix-postgres-dump.sql\"`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:93
+msgid "**All databases, roles, etc. on the Postgres server are migrated**."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:95
+msgid "Tuning PostgreSQL"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:97
+msgid "PostgreSQL can be [tuned](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) to make it run faster. This is done by passing extra arguments to the Postgres process."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:99
+msgid "The [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) **already does some tuning by default**, which matches the [tuning logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) done by websites like https://pgtune.leopard.in.ua/. You can manually influence some of the tuning variables. These parameters (variables) are injected via the `postgres_postgres_process_extra_arguments_auto` variable."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:101
+msgid "Most users should be fine with the automatically-done tuning. However, you may wish to:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:103
+msgid "**adjust the automatically-determined tuning parameters manually**: change the values for the tuning variables defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) (see `postgres_max_connections`, `postgres_data_storage` etc). These variables are ultimately passed to Postgres via a `postgres_postgres_process_extra_arguments_auto` variable"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:105
+msgid "**turn automatically-performed tuning off**: override it like this: `postgres_postgres_process_extra_arguments_auto: []`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:107
+msgid "**add additional tuning parameters**: define your additional Postgres configuration parameters in `postgres_postgres_process_extra_arguments_custom`. See `postgres_postgres_process_extra_arguments_auto` defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) for inspiration"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-synapse.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-synapse.po
new file mode 100644
index 000000000..2463c4eb2
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-synapse.po
@@ -0,0 +1,202 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/maintenance-synapse.md:1
+msgid "Synapse maintenance"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:3
+msgid "This document shows you how to perform various maintenance tasks related to the Synapse chat server."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:5
+msgid "Table of contents:"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:7
+msgid "[Purging old data with the Purge History API](#purging-old-data-with-the-purge-history-api), for when you wish to delete in-use (but old) data from the Synapse database"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:9
+msgid "[Compressing state with rust-synapse-compress-state](#compressing-state-with-rust-synapse-compress-state)"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:11
+msgid "[Browse and manipulate the database](#browse-and-manipulate-the-database), for when you really need to take matters into your own hands"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:13
+msgid "[Make Synapse faster](#make-synapse-faster)"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:15
+msgid "Purging old data with the Purge History API"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:17
+msgid "You can use the **[Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md)** to delete old messages on a per-room basis. **This is destructive** (especially for non-federated rooms), because it means **people will no longer have access to history past a certain point**."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:19
+msgid "To make use of this Synapse Admin API, **you'll need an admin access token** first. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:21
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:23
+msgid "Synapse's Admin API is not exposed to the internet by default, following [official Synapse reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints). To expose it you will need to add `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` to your `vars.yml` file."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:25
+msgid "Follow the [Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md) documentation page for the actual purging instructions."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:27
+msgid "After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:29
+msgid "Compressing state with rust-synapse-compress-state"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:31
+msgid "[rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) can be used to optimize some `_state` tables used by Synapse. If your server participates in large rooms this is the most effective way to reduce the size of your database."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:33
+msgid "**Note**: besides running the `rust-synapse-compress-state` tool manually, you can also enable its `synapse-auto-compressor` tool by [Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md). The automatic tool will run on a schedule every day and you won't have to compress state manually ever again."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:35
+msgid "`rust-synapse-compress-state` should be safe to use (even when Synapse is running), but it's always a good idea to [make Postgres backups](./maintenance-postgres.md#backing-up-postgresql) first."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:37
+msgid "To ask the playbook to run rust-synapse-compress-state, execute:"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:43
+msgid "The shortcut command with `just` program is also available: `just run-tags rust-synapse-compress-state`"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:45
+msgid "By default, all rooms with more than `100000` state group rows will be compressed. If you need to adjust this, pass: `--extra-vars='matrix_synapse_rust_synapse_compress_state_min_state_groups_required=SOME_NUMBER_HERE'` to the command above."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:47
+msgid "After state compression, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:49
+msgid "Browse and manipulate the database"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:51
+msgid "When the [Synapse Admin API](https://github.com/element-hq/synapse/tree/master/docs/admin_api) and the other tools do not provide a more convenient way, having a look at synapse's postgresql database can satisfy a lot of admins' needs."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:53
+msgid "Editing the database manually is not recommended or supported by the Synapse developers. If you are going to do so you should [make a database backup](./maintenance-postgres.md#backing-up-postgresql)."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:55
+msgid "First, set up an SSH tunnel to your Matrix server (skip if it is your local machine):"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:62
+msgid "Then start up an ephemeral [adminer](https://www.adminer.org/) container on the Matrix server, connecting it to the `matrix` network and linking the postgresql container:"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:68
+msgid "You should then be able to browse the adminer database administration GUI at http://localhost:1799/ after entering your DB credentials (found in the `host_vars` or on the server in `{{matrix_synapse_config_dir_path}}/homeserver.yaml` under `database.args`)"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:70
+msgid "⚠️️ Be **very careful** with this, there is **no undo** for impromptu DB operations."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:72
+msgid "Make Synapse faster"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:74
+msgid "Synapse's presence feature which tracks which users are online and which are offline can use a lot of processing power. You can disable presence by adding `matrix_synapse_presence_enabled: false` to your `vars.yml` file."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:76
+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:78
+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:80
+msgid "Tuning caches and cache autotuning"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:82
+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:84
+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:86
+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:88
+msgid "Cache autotuning is **enabled by default** and controlled via the following variables:"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:90
+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:91
+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:92
+msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:94
+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:96
+msgid "To **disable cache auto-tuning**, unset all values:"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:104
+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:106
+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 ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/maintenance-upgrading-services.po b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-upgrading-services.po
new file mode 100644
index 000000000..495acd2e7
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/maintenance-upgrading-services.po
@@ -0,0 +1,126 @@
+# Translations template for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\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"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/maintenance-upgrading-services.md:1
+msgid "Upgrading the Matrix services"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:3
+msgid "This playbook not only installs the various Matrix services for you, but can also upgrade them as new versions are made available."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:5
+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/maintenance-upgrading-services.md:7
+msgid "The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities (for example, see [here](https://github.com/element-hq/element-web/security) for known ones on Element Web)."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:9
+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/maintenance-upgrading-services.md:11
+msgid "The developers of this playbook strive to maintain the playbook updated, so that you can re-run the playbook to address such vulnerabilities. It is **your responsibility** to keep your server and the services on it up-to-date."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:13
+msgid "If you want to be notified when new versions of Synapse are released, you should join the Synapse Homeowners room: [#homeowners:matrix.org](https://matrix.to/#/#homeowners:matrix.org)."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:15
+msgid "Steps to upgrade the Matrix services"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:17
+msgid "Check the changelog"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:19
+msgid "Before updating the playbook and the Ansible roles in the playbook, take a look at [the changelog](../CHANGELOG.md) to see if there have been any backward-incompatible changes that you need to take care of."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:21
+msgid "Update the playbook and the Ansible roles"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:23
+msgid "If it looks good to you, go to the `matrix-docker-ansible-deploy` directory, update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file) by running:"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:25
+msgid "either: `just update`"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:26
+msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:28
+msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:30
+msgid "**Note**: for details about `just` commands, take a look at: [Running `just` commands](just.md)."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:32
+msgid "Re-run the playbook setup"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:34
+msgid "After updating the Ansible roles, then re-run the [playbook setup](installing.md#maintaining-your-setup-in-the-future) and restart all services:"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:40
+msgid "If you remove components from `vars.yml`, or if we switch some component from being installed by default to not being installed by default anymore, you'd need to run the setup command with the `setup-all` tag as below:"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:46
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:48
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account, if any."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:50
+msgid "Our estimation is that running `--tags=install-all,start` is approximately from **2 to 5 times faster** than running `setup-all,ensure-matrix-users-created,start`. See [this entry](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) on `CHANGELOG.md` for more information."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:52
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`. Note these shortcuts run the `ensure-matrix-users-created` tag too."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:54
+msgid "See [this page on the playbook tags](playbook-tags.md) for more information about those tags."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:56
+msgid "PostgreSQL major version upgrade"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:58
+msgid "Major version upgrades to the internal PostgreSQL database are not done automatically. Upgrades must be performed manually."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:60
+msgid "For details about upgrading it, refer to the [upgrading PostgreSQL guide](maintenance-postgres.md#upgrading-postgresql)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/obtaining-access-tokens.po b/i18n/locales/bg/LC_MESSAGES/docs/obtaining-access-tokens.po
new file mode 100644
index 000000000..3a94222d7
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/obtaining-access-tokens.po
@@ -0,0 +1,98 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/obtaining-access-tokens.md:1
+msgid "Obtaining an Access Token"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:3
+msgid "When setting up some optional features like bots and bridges you will need to provide an access token for some user. This document provides documentation on how to obtain such an access token."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:5
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:7
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:9
+msgid "The user for whom you want to obtain an access token needs to already exist. You can use this playbook to [register a new user](registering-users.md), if you have not already."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:11
+msgid "Below, we describe 2 ways to generate an access token for a user - using [Element Web](#obtain-an-access-token-via-element-web) or [curl](#obtain-an-access-token-via-curl). For both ways you need the user's password."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:13
+msgid "Obtain an access token via Element Web"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:15
+msgid "In a private browsing session (incognito window), open Element Web."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:16
+msgid "Log in with the user's credentials."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:17
+msgid "In the settings page, choose \"Help & About\", scroll down to the bottom and expand the `Access Token` section (see screenshot below)."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:18
+msgid "Copy the access token to your configuration."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:19
+msgid "Close the private browsing session. **Do not log out**. Logging out will invalidate the token, making it not work."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:21
+msgid "![Obtaining an access token with Element Web](assets/obtain_admin_access_token_element_web.png)"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:21
+msgid "Obtaining an access token with Element Web"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:23
+msgid "Obtain an access token via curl"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:25
+msgid "You can use the following command to get an access token for your user directly from the [Matrix Client-Server API](https://www.matrix.org/docs/guides/client-server-api#login):"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:35
+msgid "Change `USERNAME`, `PASSWORD`, and `example.com` accordingly."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:37
+msgid "`YOURDEVICEID` is optional and can be used to more easily identify the session later. When omitted (mind the commas in the JSON payload if you'll be omitting it), a random device ID will be generated."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:39
+msgid "Your response will look like this (prettified):"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/playbook-tags.po b/i18n/locales/bg/LC_MESSAGES/docs/playbook-tags.po
new file mode 100644
index 000000000..d25b07a92
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/playbook-tags.po
@@ -0,0 +1,78 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/playbook-tags.md:1
+msgid "Playbook tags"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:3
+msgid "The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks."
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:5
+msgid "The general command syntax is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:7
+msgid "Here are some playbook tags that you should be familiar with:"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:9
+msgid "`setup-all` - runs all setup tasks (installation and uninstallation) for all components, but does not start/restart services"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:11
+msgid "`install-all` - like `setup-all`, but skips uninstallation tasks. Useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove components, you'd need to run `setup-all` though, or these components will still remain installed"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:13
+msgid "`setup-SERVICE` (e.g. `setup-postmoogle`) - runs the setup tasks only for a given role, but does not start/restart services. You can discover these additional tags in each role (`roles/**/tasks/main.yml`). Running per-component setup tasks is **not recommended**, as components sometimes depend on each other and running just the setup tasks for a given component may not be enough. For example, setting up the [mautrix-telegram bridge](configuring-playbook-bridge-mautrix-telegram.md), in addition to the `setup-mautrix-telegram` tag, requires database changes (the `setup-postgres` tag) as well as reverse-proxy changes (the `setup-nginx-proxy` tag)."
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:15
+msgid "`install-SERVICE` (e.g. `install-postmoogle`) - like `setup-SERVICE`, but skips uninstallation tasks. See `install-all` above for additional information."
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:17
+msgid "`start` - starts all systemd services and makes them start automatically in the future"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:19
+msgid "`stop` - stops all systemd services"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:21
+msgid "`ensure-matrix-users-created` - a special tag which ensures that all special users needed by the playbook (for bots, etc.) are created"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:23
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:24
+msgid "`setup-*` tags and `install-*` tags **do not start services** automatically, because you may wish to do things before starting services, such as importing a database dump, restoring data from another server, etc."
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:25
+msgid "Please be careful not to confuse the playbook tags with the `just` shortcut commands (\"recipes\"). For details about `just` commands, see: [Running `just` commands](just.md)"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/prerequisites.po b/i18n/locales/bg/LC_MESSAGES/docs/prerequisites.po
new file mode 100644
index 000000000..9ae3849bd
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/prerequisites.po
@@ -0,0 +1,166 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/prerequisites.md:1
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:3
+msgid "<sup>Prerequisites > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)</sup>"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:5
+msgid "To install Matrix services using this Ansible playbook, you need to prepare several requirements both on your local computer (where you will run the playbook to configure the server) and the server (where the playbook will install the Matrix services for you). **These requirements need to be set up manually** before proceeding to the next step."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:7
+msgid "We will be using `example.com` as the domain in the following instruction. Please remember to replace it with your own domain before running any commands."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:9
+msgid "**Note**: if you do not have an existing Matrix server and want to start quickly with \"opinionated defaults\", we suggest you to follow ⚡ **[Quick start](quick-start.md)** installation guide."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:11
+msgid "Your local computer"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:13
+msgid "[Ansible](http://ansible.com/) program. It's used to run this playbook and configures your server for you. Take a look at [our guide about Ansible](ansible.md) for more information, as well as [version requirements](ansible.md#supported-ansible-versions) and alternative ways to run Ansible."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:15
+msgid "[passlib](https://passlib.readthedocs.io/en/stable/index.html) Python library. See [this official documentation](https://passlib.readthedocs.io/en/stable/install.html#installation-instructions) for an instruction to install it. On most distros, you need to install some `python-passlib` or `py3-passlib` package, etc."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:17
+msgid "[`git`](https://git-scm.com/) as the recommended way to download the playbook. `git` may also be required on the server if you will be [self-building](self-building.md) components."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:19
+msgid "[`just`](https://github.com/casey/just) for running `just roles`, `just update`, etc. (see [`justfile`](../justfile)), although you can also run these commands manually. Take at look at this documentation for more information: [Running `just` commands](just.md)."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:21
+msgid "Strong password (random strings) generator. The playbook often requires you to create a strong password and use it for settings on `vars.yml`, components, etc. As any tools should be fine, this playbook has adopted [`pwgen`](https://linux.die.net/man/1/pwgen) (running `pwgen -s 64 1`). [Password Tech](https://pwgen-win.sourceforge.io/), formerly known as \"PWGen for Windows\", is available as free and open source password generator for Windows. Generally, using a random generator available on the internet is not recommended."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:23
+msgid "Server"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:25
+msgid "(Recommended) An **x86** server ([What kind of server specs do I need?](faq.md#what-kind-of-server-specs-do-i-need)) running one of these operating systems that make use of [systemd](https://systemd.io/):"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:26
+msgid "**Archlinux**"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:27
+msgid "**CentOS**, **Rocky Linux**, **AlmaLinux**, or possibly other RHEL alternatives (although your mileage may vary)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:28
+msgid "**Debian** (10/Buster or newer)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:29
+msgid "**Ubuntu** (18.04 or newer, although [20.04 may be problematic](ansible.md#supported-ansible-versions) if you run the Ansible playbook on it)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:31
+msgid "Generally, newer is better. We only strive to support released stable versions of distributions, not betas or pre-releases. This playbook can take over your whole server or co-exist with other services that you have there."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:33
+msgid "This playbook somewhat supports running on non-`amd64` architectures like ARM. See [Alternative Architectures](alternative-architectures.md)."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:35
+msgid "If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:37
+msgid "`root` access to your server (or a user capable of elevating to `root` via `sudo`)."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:39
+msgid "[Python](https://www.python.org/). Most distributions install Python by default, but some don't (e.g. Ubuntu 18.04) and require manual installation (something like `apt-get install python3`). On some distros, Ansible may incorrectly [detect the Python version](https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html) (2 vs 3) and you may need to explicitly specify the interpreter path in `inventory/hosts` during installation (e.g. `ansible_python_interpreter=/usr/bin/python3`)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:41
+msgid "[sudo](https://www.sudo.ws/), even when you've configured Ansible to log in as `root`. Some distributions, like a minimal Debian net install, do not include the `sudo` package by default."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:43
+msgid "An HTTPS-capable web server at the base domain name (`example.com`) which is capable of serving static files. Unless you decide to [Serve the base domain from the Matrix server](configuring-playbook-base-domain-serving.md) or alternatively, to use DNS SRV records for [Server Delegation](howto-server-delegation.md)."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:45
+msgid "Properly configured DNS records for `example.com` (details in [Configuring DNS](configuring-dns.md))."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:47
+msgid "Some TCP/UDP ports open. This playbook (actually [Docker itself](https://docs.docker.com/network/iptables/)) configures the server's internal firewall for you. In most cases, you don't need to do anything special. But **if your server is running behind another firewall**, you'd need to open these ports:"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:49
+msgid "`80/tcp`: HTTP webserver"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:50
+msgid "`443/tcp` and `443/udp`: HTTPS webserver"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:51
+msgid "`3478/tcp`: TURN over TCP (used by Coturn)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:52
+msgid "`3478/udp`: TURN over UDP (used by Coturn)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:53
+msgid "`5349/tcp`: TURN over TCP (used by Coturn)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:54
+msgid "`5349/udp`: TURN over UDP (used by Coturn)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:55
+msgid "`8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. In some cases, this **may necessary even with federation disabled**. Integration Servers (like Dimension) and Identity Servers (like ma1sd) may need to access `openid` APIs on the federation port."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:56
+msgid "the range `49152-49172/udp`: TURN over UDP"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:57
+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:61
+msgid "[▶️](configuring-dns.md) When ready to proceed, continue with [Configuring DNS](configuring-dns.md)."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/quick-start.po b/i18n/locales/bg/LC_MESSAGES/docs/quick-start.po
new file mode 100644
index 000000000..c92e29a4e
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/quick-start.po
@@ -0,0 +1,435 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: 2024-12-20 15:23+0200\n"
+"Last-Translator: \n"
+"Language-Team: bg <LL@li.org>\n"
+"Language: bg\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"Generated-By: Babel 2.16.0\n"
+"X-Generator: Poedit 3.4.2\n"
+
+#: ../../../docs/quick-start.md:1
+msgid "Quick start"
+msgstr "Бърза инсталация"
+
+#: ../../../docs/quick-start.md:9
+msgid "This page explains how to use this Ansible playbook to install Matrix services on your server with a minimal set of core services."
+msgstr "Тази страница показва как да използвате Ansible плейбука за да инсталирате минимален брой от важните Matrix услуги на ваш собствен сървър."
+
+#: ../../../docs/quick-start.md:11
+msgid "We will be using `example.com` as the \"base domain\" in the following instruction."
+msgstr "Ще използваме `example.com` като \"базов домейн\" в инструкциите по-долу."
+
+#: ../../../docs/quick-start.md:13
+msgid "By following the instruction on this page, you will set up:"
+msgstr "Следвайки инструкциите на тази страница, ще настройте:"
+
+#: ../../../docs/quick-start.md:15
+msgid "**your own Matrix server** on a `matrix.example.com` server, which is configured to present itself as `example.com`"
+msgstr "**ваш собствен Matrix сървър** на `matrix.example.com` сървъра, който е настроен да се представя за `example.com`"
+
+#: ../../../docs/quick-start.md:16
+msgid "**your user account** like `@alice:example.com` on the server"
+msgstr "**ваш потребителски профил** като `@alice:example.com` на сървъра"
+
+#: ../../../docs/quick-start.md:17
+msgid "a **self-hosted Matrix client**, [Element Web](configuring-playbook-client-element-web.md) with the default subdomain at `element.example.com`"
+msgstr "**самостоятелно-хостван Matrix клиент**, [Element Web](configuring-playbook-client-element-web.md) на поддомейн по подразбиране `element.example.com`"
+
+#: ../../../docs/quick-start.md:18
+msgid "Matrix delegation, so that your `matrix.example.com` server (presenting itself as `example.com`) can join the Matrix Federation and communicate with any other server in the Matrix network"
+msgstr "Matrix делегиране, така че `matrix.example.com` сървърът ви (представящ се за `example.com`) да може да се включи в Matrix Федерацията и да комуникира с други сървъри в Matrix мрежата"
+
+#: ../../../docs/quick-start.md:20
+msgid "Please remember to replace `example.com` with your own domain before running any commands."
+msgstr "Моля, помнете да замените `example.com` със собствения си домейн преди да изпълните командите по-долу."
+
+#: ../../../docs/quick-start.md:22
+msgid "Prerequisites"
+msgstr "Предварителни условия"
+
+#: ../../../docs/quick-start.md:24
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Prerequisites](prerequisites.md)</sup>"
+msgstr "<sup>Този раздел е оптимизиран за този наръчник за бърза инсталация на базата на следната страница от пълната документация: [Предварителни условия](prerequisites.md)</sup>"
+
+#: ../../../docs/quick-start.md:26
+msgid "At first, **check prerequisites** and prepare for installation by setting up programs [on your own computer](prerequisites.md#your-local-computer) and [your server](prerequisites.md#server). You also need `root` access on your server (a user that could elevate to `root` via `sudo` also works)."
+msgstr ""
+
+#: ../../../docs/quick-start.md:28
+msgid "When preparing your server, make sure to check [the server specs you need](faq.md#what-kind-of-server-specs-do-i-need). We recommend starting with a server having at least 2GB of memory."
+msgstr ""
+
+#: ../../../docs/quick-start.md:34
+msgid "If you encounter an error during installation, please make sure that you have installed and configured programs correctly."
+msgstr ""
+
+#: ../../../docs/quick-start.md:36
+msgid "One of the main reasons of basic errors is using an incompatible version of required software such as Ansible. Take a look at [our guide about Ansible](ansible.md) for more information. In short: installing the latest available version is recommended."
+msgstr ""
+
+#: ../../../docs/quick-start.md:38
+msgid "Configure your DNS settings"
+msgstr ""
+
+#: ../../../docs/quick-start.md:40
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Configuring your DNS settings](configuring-dns.md)</sup>"
+msgstr "<sup>Този раздел е оптимизиран за този наръчник за бърза инсталация на базата на следната страница от пълната документация: [Конфигуриране на DNS настройките](configuring-dns.md)</sup>"
+
+#: ../../../docs/quick-start.md:42
+msgid "After installing and configuring prerequisites, you will need to **configure DNS records**."
+msgstr ""
+
+#: ../../../docs/quick-start.md:44
+msgid "To configure Matrix services in the default settings, go to your DNS service provider, and adjust DNS records as below."
+msgstr ""
+
+#: ../../../docs/quick-start.md
+msgid "Type"
+msgstr "Тип"
+
+#: ../../../docs/quick-start.md
+msgid "Host"
+msgstr "Домейн"
+
+#: ../../../docs/quick-start.md
+msgid "Priority"
+msgstr "Приоритет"
+
+#: ../../../docs/quick-start.md
+msgid "Weight"
+msgstr "Тегло"
+
+#: ../../../docs/quick-start.md
+msgid "Port"
+msgstr "Порт"
+
+#: ../../../docs/quick-start.md
+msgid "Target"
+msgstr "Цел"
+
+#: ../../../docs/quick-start.md
+msgid "A"
+msgstr "A"
+
+#: ../../../docs/quick-start.md
+msgid "`matrix`"
+msgstr "`matrix`"
+
+#: ../../../docs/quick-start.md
+msgid "-"
+msgstr "-"
+
+#: ../../../docs/quick-start.md
+msgid "`matrix-server-IP`"
+msgstr "`IP-на-matrix-сървъра`"
+
+#: ../../../docs/quick-start.md
+msgid "CNAME"
+msgstr "CNAME"
+
+#: ../../../docs/quick-start.md
+msgid "`element`"
+msgstr "`element`"
+
+#: ../../../docs/quick-start.md
+msgid "`matrix.example.com`"
+msgstr "`matrix.example.com`"
+
+#: ../../../docs/quick-start.md:51
+msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)."
+msgstr "Както показва таблицата, необходимо е да създадете 2 поддомейна (`matrix.example.com` и `element.example.com`) и да ги насочите към IP адреса на сървъра (чрез DNS `A` запис или `CNAME` запис)."
+
+#: ../../../docs/quick-start.md:53
+msgid "It might take some time for the DNS records to propagate after creation."
+msgstr "Може да отнеме известно време след създаване на DNS записите докато се отразят."
+
+#: ../../../docs/quick-start.md:55
+msgid "**💡 Note**: if you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\""
+msgstr ""
+
+#: ../../../docs/quick-start.md:57
+msgid "Get the playbook"
+msgstr ""
+
+#: ../../../docs/quick-start.md:59
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Getting the playbook](getting-the-playbook.md)</sup>"
+msgstr "<sup>Този раздел е оптимизиран за този наръчник за бърза инсталация на базата на следната страница от пълната документация: [Изтегляне на плейбука](getting-the-playbook.md)</sup>"
+
+#: ../../../docs/quick-start.md:61
+msgid "Next, let's **get the playbook's source code**."
+msgstr ""
+
+#: ../../../docs/quick-start.md:63
+msgid "We recommend to do so with [git](https://git-scm.com/) as it enables you to keep it up to date with the latest source code. While it is possible to download the playbook as a ZIP archive, it is not recommended."
+msgstr ""
+
+#: ../../../docs/quick-start.md:65
+msgid "To get the playbook with git, install git on your computer, go to a directory, and run the command:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:71
+msgid "It will fetch the playbook to a new `matrix-docker-ansible-deploy` directory underneath the directory you are currently in."
+msgstr ""
+
+#: ../../../docs/quick-start.md:73
+msgid "Configure the playbook"
+msgstr ""
+
+#: ../../../docs/quick-start.md:75
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Configuring the playbook](configuring-playbook.md)</sup>"
+msgstr "<sup>Този раздел е оптимизиран за този наръчник за бърза инсталация на базата на следната страница от пълната документация: [Конфигуриране на плейбука](configuring-playbook.md)</sup>"
+
+#: ../../../docs/quick-start.md:77
+msgid "Now that the playbook was fetched, it is time to **configure** it per your needs."
+msgstr ""
+
+#: ../../../docs/quick-start.md:79
+msgid "To install Matrix services with this playbook, you would at least need 2 configuration files."
+msgstr ""
+
+#: ../../../docs/quick-start.md:81
+msgid "For your convenience, we have prepared example files of them ([`vars.yml`](../examples/vars.yml) and [`hosts`](../examples/hosts))."
+msgstr ""
+
+#: ../../../docs/quick-start.md:83
+msgid "To start quickly based on these example files, go into the `matrix-docker-ansible-deploy` directory and follow the instructions below:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:85
+msgid "Create a directory to hold your configuration: `mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\""
+msgstr ""
+
+#: ../../../docs/quick-start.md:86
+msgid "Copy the sample configuration file: `cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:87
+msgid "Copy the sample inventory hosts file: `cp examples/hosts inventory/hosts`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:88
+msgid "Edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`)"
+msgstr ""
+
+#: ../../../docs/quick-start.md:89
+msgid "Edit the inventory hosts file (`inventory/hosts`)"
+msgstr ""
+
+#: ../../../docs/quick-start.md:91
+msgid "Before editing these 2 files, make sure to read explanations on them to understand what needs to be configured."
+msgstr ""
+
+#: ../../../docs/quick-start.md:93
+msgid "**💡 Notes:**"
+msgstr ""
+
+#: ../../../docs/quick-start.md:94
+msgid "If you are not in control of anything on the base domain, you would need to set additional configuration on `vars.yml`. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ."
+msgstr ""
+
+#: ../../../docs/quick-start.md:95
+msgid "Certain configuration decisions (like the base domain configured in `matrix_domain` and homeserver implementation configured in `matrix_homeserver_implementation`) are final. If you make the wrong choice and wish to change it, you'll have to run the Uninstalling step and start over."
+msgstr ""
+
+#: ../../../docs/quick-start.md:96
+msgid "Instead of configuring a lot of things all at once, we recommend starting with the basic (default) settings in order to get yourself familiar with how the playbook works. After making sure that everything works as expected, you can add (and remove) advanced settings / features and run the playbook as many times as you wish."
+msgstr ""
+
+#: ../../../docs/quick-start.md:98
+msgid "Install"
+msgstr ""
+
+#: ../../../docs/quick-start.md:100
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Installing](installing.md)</sup>"
+msgstr "<sup>Този раздел е оптимизиран за този наръчник за бърза инсталация на базата на следната страница от пълната документация: [Инсталиране](installing.md)</sup>"
+
+#: ../../../docs/quick-start.md:102
+msgid "After editing `vars.yml` and `hosts` files, let's start the **installation** procedure."
+msgstr ""
+
+#: ../../../docs/quick-start.md:104
+msgid "Update Ansible roles"
+msgstr ""
+
+#: ../../../docs/quick-start.md:106
+msgid "Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside."
+msgstr ""
+
+#: ../../../docs/quick-start.md:108
+msgid "To update your playbook directory and all upstream Ansible roles, run:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:110
+msgid "either: `just update`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:111
+msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)"
+msgstr ""
+
+#: ../../../docs/quick-start.md:113
+msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:115
+msgid "Run installation command"
+msgstr ""
+
+#: ../../../docs/quick-start.md:117
+msgid "Then, run the command below to start installation:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:123
+msgid "If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the command."
+msgstr ""
+
+#: ../../../docs/quick-start.md:125
+msgid "If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to the command."
+msgstr ""
+
+#: ../../../docs/quick-start.md:127
+msgid "Wait until the command completes. If it's all green, everything should be running properly."
+msgstr ""
+
+#: ../../../docs/quick-start.md:129
+msgid "Create your user account"
+msgstr ""
+
+#: ../../../docs/quick-start.md:131
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Registering users](registering-users.md)</sup>"
+msgstr ""
+
+#: ../../../docs/quick-start.md:133
+msgid "As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server."
+msgstr ""
+
+#: ../../../docs/quick-start.md:135
+msgid "To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer."
+msgstr ""
+
+#: ../../../docs/quick-start.md:137
+msgid "**💡 Notes**:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:138
+msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:139
+msgid "For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)"
+msgstr ""
+
+#: ../../../docs/quick-start.md:151
+msgid "Finalize server installation"
+msgstr ""
+
+#: ../../../docs/quick-start.md:153
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Server Delegation](howto-server-delegation.md)</sup>"
+msgstr ""
+
+#: ../../../docs/quick-start.md:155
+msgid "Now that you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network."
+msgstr ""
+
+#: ../../../docs/quick-start.md:157
+msgid "**This is required for federation to work!** Without a proper configuration, your server will effectively not be part of the Matrix network."
+msgstr ""
+
+#: ../../../docs/quick-start.md:159
+msgid "To configure the delegation, you have these two options. Choose one of them according to your situation."
+msgstr ""
+
+#: ../../../docs/quick-start.md:161
+msgid "If you can afford to point the base domain at the Matrix server, follow the instruction below which guides you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server."
+msgstr ""
+
+#: ../../../docs/quick-start.md:162
+msgid "Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot \"serve the base domain\" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server)."
+msgstr ""
+
+#: ../../../docs/quick-start.md:164
+msgid "To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:170
+msgid "After configuring the playbook, run the command below and wait until it finishes:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:176
+msgid "💡 Running the `install-matrix-static-files` playbook tag (as done here) is an optimized version of running [the full setup command](#run-installation-command)."
+msgstr ""
+
+#: ../../../docs/quick-start.md:178
+msgid "After the command finishes, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain."
+msgstr ""
+
+#: ../../../docs/quick-start.md:180
+msgid "Re-run the full setup command any time"
+msgstr ""
+
+#: ../../../docs/quick-start.md:182
+msgid "If you think something is wrong with the server configuration, feel free to re-run the setup command any time:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:188
+msgid "Log in to your user account"
+msgstr ""
+
+#: ../../../docs/quick-start.md:190
+msgid "Finally, let's make sure that you can log in to the created account with the specified password."
+msgstr ""
+
+#: ../../../docs/quick-start.md:192
+msgid "You should be able to log in to it with your own [Element Web](configuring-playbook-client-element-web.md) client which you have set up at `element.example.com` by running the playbook. Open the URL (`https://element.example.com`) in a web browser and enter your credentials to log in."
+msgstr ""
+
+#: ../../../docs/quick-start.md:194
+msgid "**If you successfully logged in to your account, installing and configuring is complete**🎉"
+msgstr ""
+
+#: ../../../docs/quick-start.md:196
+msgid "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/quick-start.md:198
+msgid "Things to do next"
+msgstr ""
+
+#: ../../../docs/quick-start.md:200
+msgid "Once you get familiar with the playbook, you might probably want to set up additional services such as a bridge on your server."
+msgstr ""
+
+#: ../../../docs/quick-start.md:202
+msgid "As this page intends to be a quick start guide which explains how to start the core Matrix services, it does not cover a topic like how to set them up. Take a look at the list of [things to do next](installing.md#things-to-do-next) to learn more."
+msgstr ""
+
+#: ../../../docs/quick-start.md:204
+msgid "⚠️Keep the playbook and services up-to-date"
+msgstr ""
+
+#: ../../../docs/quick-start.md:206
+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/quick-start.md:208
+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/quick-start.md:210
+msgid "For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/registering-users.po b/i18n/locales/bg/LC_MESSAGES/docs/registering-users.po
new file mode 100644
index 000000000..f8e0f8d37
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/registering-users.po
@@ -0,0 +1,246 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/registering-users.md:1
+msgid "Registering users"
+msgstr ""
+
+#: ../../../docs/registering-users.md:3
+msgid "This documentation page tells you how to create user accounts on your Matrix server."
+msgstr ""
+
+#: ../../../docs/registering-users.md:5
+msgid "Table of contents:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:7
+msgid "[Registering users](#registering-users)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:8
+msgid "[Registering users manually](#registering-users-manually)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:9
+msgid "[Managing users via a Web UI](#managing-users-via-a-web-ui)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:10
+msgid "[Letting certain users register on your private server](#letting-certain-users-register-on-your-private-server)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:11
+msgid "[Enabling public user registration](#enabling-public-user-registration)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:12
+msgid "[Adding/Removing Administrator privileges to an existing user](#addingremoving-administrator-privileges-to-an-existing-user)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:14
+msgid "Registering users manually"
+msgstr ""
+
+#: ../../../docs/registering-users.md:16 ../../../docs/registering-users.md:118
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:17
+msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`"
+msgstr ""
+
+#: ../../../docs/registering-users.md:18
+msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:19
+msgid "Use `admin=yes` or `admin=no` depending on whether you wish to make the user an administrator of the Matrix server"
+msgstr ""
+
+#: ../../../docs/registering-users.md:21
+msgid "After registering a user (using one of the methods below), **you can log in with that user** via the [Element Web](configuring-playbook-client-element-web.md) service that this playbook has installed for you at a URL like this: `https://element.example.com/`."
+msgstr ""
+
+#: ../../../docs/registering-users.md:23
+msgid "Registering users via the Ansible playbook"
+msgstr ""
+
+#: ../../../docs/registering-users.md:25
+msgid "It's best to register users via the Ansible playbook, because it works regardless of homeserver implementation (Synapse, Dendrite, etc) or usage of [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (MAS)."
+msgstr ""
+
+#: ../../../docs/registering-users.md:27
+msgid "To register a user via this Ansible playbook:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:35
+msgid "**or** by invoking `ansible-playbook` manually:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:43
+msgid "Feel free to register as many users (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your user account only (with `admin=yes`), and others should be created with `admin=no`."
+msgstr ""
+
+#: ../../../docs/registering-users.md:45
+msgid "⚠️ **Warning**: If you're registering users against Matrix Authentication Service, do note that it [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information."
+msgstr ""
+
+#: ../../../docs/registering-users.md:47
+msgid "Registering users manually for Synapse"
+msgstr ""
+
+#: ../../../docs/registering-users.md:49
+msgid "If you're using the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default), you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
+msgstr ""
+
+#: ../../../docs/registering-users.md:57
+msgid "Registering users manually for Dendrite"
+msgstr ""
+
+#: ../../../docs/registering-users.md:59
+msgid "If you're using the [Dendrite](./configuring-playbook-dendrite.md) homeserver implementation, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
+msgstr ""
+
+#: ../../../docs/registering-users.md:67
+msgid "Registering users manually for Matrix Authentication Service"
+msgstr ""
+
+#: ../../../docs/registering-users.md:69
+msgid "If you're using the [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) and your existing homeserver (most likely [Synapse](./configuring-playbook-synapse.md)) is delegating authentication to it, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
+msgstr ""
+
+#: ../../../docs/registering-users.md:77
+msgid "This `register-user` script actually invokes the `mas-cli manage register-user` command under the hood. If you'd like more control over the registration process, consider invoking the `mas-cli` command directly:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:83
+msgid "⚠️ **Warning**: Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information."
+msgstr ""
+
+#: ../../../docs/registering-users.md:85
+msgid "Managing users via a Web UI"
+msgstr ""
+
+#: ../../../docs/registering-users.md:87
+msgid "To manage users more easily (via a web user-interace), you can install [Synapse Admin](configuring-playbook-synapse-admin.md)."
+msgstr ""
+
+#: ../../../docs/registering-users.md:89
+msgid "⚠️ **Warning**: If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information."
+msgstr ""
+
+#: ../../../docs/registering-users.md:91
+msgid "Letting certain users register on your private server"
+msgstr ""
+
+#: ../../../docs/registering-users.md:93
+msgid "If you'd rather **keep your server private** (public registration closed, as is the default), and **let certain people create accounts by themselves** (instead of creating user accounts manually like this), consider installing and making use of [matrix-registration](configuring-playbook-matrix-registration.md)."
+msgstr ""
+
+#: ../../../docs/registering-users.md:95
+msgid "Enabling public user registration"
+msgstr ""
+
+#: ../../../docs/registering-users.md:97
+msgid "To **open up user registration publicly** (usually **not recommended**), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:99
+msgid "For Synapse:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:105
+msgid "For Dendrite:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:111
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:120
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/registering-users.md:122
+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/registering-users.md:124
+msgid "If you're opening up registrations publicly like this, you might also wish to [configure CAPTCHA protection](configuring-captcha.md)."
+msgstr ""
+
+#: ../../../docs/registering-users.md:126
+msgid "Adding/Removing Administrator privileges to an existing user"
+msgstr ""
+
+#: ../../../docs/registering-users.md:128
+msgid "Adding/Removing Administrator privileges to an existing user in Synapse"
+msgstr ""
+
+#: ../../../docs/registering-users.md:130
+msgid "To change the admin privileges for a user in Synapse's local database, you need to run an SQL query like this against the `synapse` database:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:136
+msgid "where:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:138
+msgid "`ADMIN_VALUE` being either `0` (regular user) or `1` (admin)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:139
+msgid "`USER` and `example.com` pointing to a valid user on your server"
+msgstr ""
+
+#: ../../../docs/registering-users.md:141
+msgid "If you're using the integrated Postgres server and not an [external Postgres server](configuring-playbook-external-postgres.md), you can launch a Postgres into the `synapse` database by:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:143
+msgid "running `/matrix/postgres/bin/cli` - to launch [`psql`](https://www.postgresql.org/docs/current/app-psql.html)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:144
+msgid "running `\\c synapse` - to change to the `synapse` database"
+msgstr ""
+
+#: ../../../docs/registering-users.md:146
+msgid "You can then proceed to run the query above."
+msgstr ""
+
+#: ../../../docs/registering-users.md:148
+msgid "**Note**: directly modifying the raw data of Synapse (or any other software) could cause the software to break. You've been warned!"
+msgstr ""
+
+#: ../../../docs/registering-users.md:150
+msgid "Adding/Removing Administrator privileges to an existing user in Matrix Authentication Service"
+msgstr ""
+
+#: ../../../docs/registering-users.md:152
+msgid "Promoting/demoting a user in Matrix Authentication Service cannot currently (2024-10-19) be done via the [`mas-cli` Management tool](./configuring-playbook-matrix-authentication-service.md#management)."
+msgstr ""
+
+#: ../../../docs/registering-users.md:154
+msgid "You can do it via the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html)'s `POST /api/admin/v1/users/{id}/set-admin` endpoint."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/self-building.po b/i18n/locales/bg/LC_MESSAGES/docs/self-building.po
new file mode 100644
index 000000000..89bf5c0f5
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/self-building.po
@@ -0,0 +1,178 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/self-building.md:1
+msgid "Self-building"
+msgstr ""
+
+#: ../../../docs/self-building.md:3
+msgid "**Caution: self-building does not have to be used on its own. See the [Alternative Architectures](alternative-architectures.md) page.**"
+msgstr ""
+
+#: ../../../docs/self-building.md:5
+msgid "The playbook supports self-building of various components, which don't have a container image for your architecture (see the [container images we use](container-images.md)). For `amd64`, self-building is not required."
+msgstr ""
+
+#: ../../../docs/self-building.md:7
+msgid "For other architectures (e.g. `arm32`, `arm64`), ready-made container images are used when available. If there's no ready-made image for a specific component and said component supports self-building, an image will be built on the host. Building images like this takes more time and resources (some build tools need to get installed by the playbook to assist building)."
+msgstr ""
+
+#: ../../../docs/self-building.md:9
+msgid "To make use of self-building, you don't need to do anything. If a component has an image for the specified architecture, the playbook will use it directly. If not, it will build the image on the server itself."
+msgstr ""
+
+#: ../../../docs/self-building.md:11
+msgid "Note that **not all components support self-building yet**."
+msgstr ""
+
+#: ../../../docs/self-building.md:13
+msgid "Possibly outdated list of roles where self-building the Docker image is currently possible:"
+msgstr ""
+
+#: ../../../docs/self-building.md:14
+msgid "`matrix-synapse`"
+msgstr ""
+
+#: ../../../docs/self-building.md:15
+msgid "`matrix-synapse-admin`"
+msgstr ""
+
+#: ../../../docs/self-building.md:16
+msgid "`matrix-client-element`"
+msgstr ""
+
+#: ../../../docs/self-building.md:17
+msgid "`matrix-client-hydrogen`"
+msgstr ""
+
+#: ../../../docs/self-building.md:18
+msgid "`matrix-client-cinny`"
+msgstr ""
+
+#: ../../../docs/self-building.md:19
+msgid "`matrix-registration`"
+msgstr ""
+
+#: ../../../docs/self-building.md:20
+msgid "`matrix-coturn`"
+msgstr ""
+
+#: ../../../docs/self-building.md:21
+msgid "`matrix-corporal`"
+msgstr ""
+
+#: ../../../docs/self-building.md:22
+msgid "`matrix-dimension`"
+msgstr ""
+
+#: ../../../docs/self-building.md:23
+msgid "`matrix-ma1sd`"
+msgstr ""
+
+#: ../../../docs/self-building.md:24
+msgid "`exim-relay`"
+msgstr ""
+
+#: ../../../docs/self-building.md:25
+msgid "`matrix-bridge-hookshot`"
+msgstr ""
+
+#: ../../../docs/self-building.md:26
+msgid "`matrix-bridge-appservice-irc`"
+msgstr ""
+
+#: ../../../docs/self-building.md:27
+msgid "`matrix-bridge-appservice-slack`"
+msgstr ""
+
+#: ../../../docs/self-building.md:28
+msgid "`matrix-bridge-appservice-webhooks`"
+msgstr ""
+
+#: ../../../docs/self-building.md:29
+msgid "`matrix-bridge-beeper-linkedin`"
+msgstr ""
+
+#: ../../../docs/self-building.md:30
+msgid "`matrix-bridge-mautrix-facebook`"
+msgstr ""
+
+#: ../../../docs/self-building.md:31
+msgid "`matrix-bridge-mautrix-hangouts`"
+msgstr ""
+
+#: ../../../docs/self-building.md:32
+msgid "`matrix-bridge-mautrix-googlechat`"
+msgstr ""
+
+#: ../../../docs/self-building.md:33
+msgid "`matrix-bridge-mautrix-telegram`"
+msgstr ""
+
+#: ../../../docs/self-building.md:34
+msgid "`matrix-bridge-mautrix-signal`"
+msgstr ""
+
+#: ../../../docs/self-building.md:35
+msgid "`matrix-bridge-mautrix-gmessages`"
+msgstr ""
+
+#: ../../../docs/self-building.md:36
+msgid "`matrix-bridge-mautrix-whatsapp`"
+msgstr ""
+
+#: ../../../docs/self-building.md:37
+msgid "`matrix-bridge-mx-puppet-steam`"
+msgstr ""
+
+#: ../../../docs/self-building.md:38
+msgid "`matrix-bot-mjolnir`"
+msgstr ""
+
+#: ../../../docs/self-building.md:39
+msgid "`matrix-bot-honoroit`"
+msgstr ""
+
+#: ../../../docs/self-building.md:40
+msgid "`matrix-bot-matrix-reminder-bot`"
+msgstr ""
+
+#: ../../../docs/self-building.md:41
+msgid "`matrix-bot-maubot`"
+msgstr ""
+
+#: ../../../docs/self-building.md:42
+msgid "`matrix-email2matrix`"
+msgstr ""
+
+#: ../../../docs/self-building.md:43
+msgid "`matrix-pantalaimon`"
+msgstr ""
+
+#: ../../../docs/self-building.md:45
+msgid "Adding self-building support to other roles is welcome. Feel free to contribute!"
+msgstr ""
+
+#: ../../../docs/self-building.md:47
+msgid "If you'd like **to force self-building** even if an image is available for your architecture, look into the `matrix_*_self_build` variables provided by individual roles."
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/uninstalling.po b/i18n/locales/bg/LC_MESSAGES/docs/uninstalling.po
new file mode 100644
index 000000000..3215c013b
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/uninstalling.po
@@ -0,0 +1,82 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/uninstalling.md:1
+msgid "Uninstalling"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:3
+msgid "**Warnings**:"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:5
+msgid "If your server federates with others, make sure to **leave any federated rooms before nuking your Matrix server's data**. Otherwise, the next time you set up a Matrix server for this domain (regardless of the installation method you use), you'll encounter trouble federating."
+msgstr ""
+
+#: ../../../docs/uninstalling.md:7
+msgid "If you have some trouble with your installation, you can just [re-run the playbook](installing.md) and it will try to set things up again. **Uninstalling and then installing anew rarely solves anything**."
+msgstr ""
+
+#: ../../../docs/uninstalling.md:11
+msgid "Uninstalling using a script"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:13
+msgid "Installing places a `/matrix/bin/remove-all` script on the server."
+msgstr ""
+
+#: ../../../docs/uninstalling.md:15
+msgid "You can run it to to have it uninstall things for you automatically (see below). **Use with caution!**"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:17
+msgid "Uninstalling manually"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:19
+msgid "If you prefer to uninstall manually, run these commands (most are meant to be executed on the Matrix server itself):"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:21
+msgid "ensure all Matrix services are stopped: `ansible-playbook -i inventory/hosts setup.yml --tags=stop` (if you can't get Ansible working to run this command, you can run `systemctl stop 'matrix*'` manually on the server)"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:23
+msgid "delete the Matrix-related systemd `.service` and `.timer` files (`rm -f /etc/systemd/system/matrix*.{service,timer}`) and reload systemd (`systemctl daemon-reload`)"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:25
+msgid "delete some cached Docker images (`docker system prune -a`) or just delete them all (`docker rmi $(docker images -aq)`)"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:27
+msgid "delete the Docker networks: `docker network rm matrix matrix-coturn` (might have been deleted already if you ran the `docker system prune` command)"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:29
+msgid "uninstall Docker itself, if necessary"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:31
+msgid "delete the `/matrix` directory (`rm -rf /matrix`)"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/docs/updating-users-passwords.po b/i18n/locales/bg/LC_MESSAGES/docs/updating-users-passwords.po
new file mode 100644
index 000000000..7c381ab52
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/docs/updating-users-passwords.po
@@ -0,0 +1,90 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: bg\n"
+"Language-Team: bg <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/updating-users-passwords.md:1
+msgid "Updating users passwords"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:3
+msgid "Option 1 (if you are using the integrated Postgres database):"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:5
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:6
+msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:7
+msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:9
+msgid "You can reset a user's password via the Ansible playbook:"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:15
+msgid "**You can then log in with that user** via Element Web that this playbook has created for you at a URL like this: `https://element.example.com/`."
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:17
+msgid "Option 2 (if you are using an external Postgres server):"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:19
+msgid "You can manually generate the password hash by using the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#finalize-the-installation):"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:25
+msgid "and then connecting to the postgres server and executing:"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:31
+msgid "where `<password-hash>` is the hash returned by the docker command above."
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:33
+msgid "Option 3:"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:35
+msgid "Use the Synapse User Admin API as described here: https://github.com/element-hq/synapse/blob/master/docs/admin_api/user_admin_api.rst#reset-password"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:37
+msgid "This requires an [access token](obtaining-access-tokens.md) from a server admin account. *This method will also log the user out of all of their clients while the other options do not.*"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:39
+msgid "If you didn't make your account a server admin when you created it, you can learn how to switch it now by reading about it in [Adding/Removing Administrator privileges to an existing user in Synapse](registering-users.md#addingremoving-administrator-privileges-to-an-existing-user-in-synapse)."
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:41
+msgid "Example:"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:43
+msgid "To set @alice:example.com's password to `correct_horse_battery_staple` you could use this curl command:"
+msgstr ""
diff --git a/i18n/locales/bg/LC_MESSAGES/i18n/README.po b/i18n/locales/bg/LC_MESSAGES/i18n/README.po
new file mode 100644
index 000000000..c5e6d158e
--- /dev/null
+++ b/i18n/locales/bg/LC_MESSAGES/i18n/README.po
@@ -0,0 +1,210 @@
+# Translations template for PROJECT.
+# Copyright (C) 2024 ORGANIZATION
+# This file is distributed under the same license as the PROJECT project.
+# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: PROJECT VERSION\n"
+"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
+"POT-Creation-Date: 2024-12-20 15:27+0200\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"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../README.md:8
+msgid "Internationalization"
+msgstr ""
+
+#: ../../README.md:10
+msgid "Translated documentation files are published and maintained in [`translations/`](translations/) directory."
+msgstr ""
+
+#: ../../README.md:12
+msgid "Currently, we support translation of:"
+msgstr ""
+
+#: ../../README.md:14
+msgid "Markdown files found at the top level project directory"
+msgstr ""
+
+#: ../../README.md:15
+msgid "Markdown files found in the [`docs`](../docs/) directory (this is where the bulk of the documentation is)"
+msgstr ""
+
+#: ../../README.md:16
+msgid "this current document in the `i18n` directory"
+msgstr ""
+
+#: ../../README.md:18
+msgid "💡 For readers' sake, we only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold (requiring that at least the project README and core installation guides are translated)."
+msgstr ""
+
+#: ../../README.md:20
+msgid "Organization of this `i18n` directory is as follows:"
+msgstr ""
+
+#: ../../README.md:22
+msgid "[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translations/](translations/) directory)"
+msgstr ""
+
+#: ../../README.md:23
+msgid "[.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionaly ignore translated results (`translations/<language>` directories) for languages taht are still in progress. We only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold."
+msgstr ""
+
+#: ../../README.md:24
+msgid "[justfile](justfile): a list of recipes for [just](https://github.com/casey/just) command runner"
+msgstr ""
+
+#: ../../README.md:25
+msgid "[requirements.txt](requirements.txt): a list of Python packages required to work with translations"
+msgstr ""
+
+#: ../../README.md:26
+msgid "[translation-templates/](translation-templates/): a list of English translation templates - strings extracted from Markdown files"
+msgstr ""
+
+#: ../../README.md:27
+msgid "[locales/](locales/): localization files for languages"
+msgstr ""
+
+#: ../../README.md:28
+msgid "[translations/](translations/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language))"
+msgstr ""
+
+#: ../../README.md:30
+msgid "Guide for translators"
+msgstr ""
+
+#: ../../README.md:32
+msgid "This project uses [Sphinx](https://www.sphinx-doc.org/) to generate translated documents."
+msgstr ""
+
+#: ../../README.md:34
+msgid "For details about using Sphinx for translation, refer [this official document](https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) as well."
+msgstr ""
+
+#: ../../README.md:36
+msgid "For now, translations are handled manually by editing `.po` files in the `locales/<language>` directory. In the future, we plan on integrating with [Weblate](https://weblate.org/) to allow for translating from a web interface."
+msgstr ""
+
+#: ../../README.md:38
+msgid "(Recommended) Using the uv package manager and just command runner"
+msgstr ""
+
+#: ../../README.md:40
+msgid "If you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed, you can use our [justfile](justfile) recipes to easily manage translation files and build translated documents."
+msgstr ""
+
+#: ../../README.md:42
+msgid "The recipes will use [uv](https://github.com/astral-sh/uv) to auto-create [a Python virtual environment](https://docs.astral.sh/uv/pip/environments/) in the `.venv` directory and install the required Python packages (as per [requirements.txt](requirements.txt)) to it."
+msgstr ""
+
+#: ../../README.md:44 ../../README.md:71
+msgid "Preparation"
+msgstr ""
+
+#: ../../README.md:46
+msgid "Make sure you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed."
+msgstr ""
+
+#: ../../README.md:48 ../../README.md:79
+msgid "Translation"
+msgstr ""
+
+#: ../../README.md:50 ../../README.md:81
+msgid "Recommended flow when working on a new language (replace `<language>` with the language code, e.g. `bg`):"
+msgstr ""
+
+#: ../../README.md:52
+msgid "Update the locale files for your language: `just sync-for-language <language>` (internally, this automatically runs `just extract-translation-templates` to make sure the translation templates are up-to-date)"
+msgstr ""
+
+#: ../../README.md:54 ../../README.md:87
+msgid "Use an editor to translate the files in the `locales/<language>` directory"
+msgstr ""
+
+#: ../../README.md:56
+msgid "Build translated documents: `just build-for-language <language>`"
+msgstr ""
+
+#: ../../README.md:58 ../../README.md:91
+msgid "Preview the result in the `translations/<language>` directory"
+msgstr ""
+
+#: ../../README.md:60 ../../README.md:93
+msgid "Commit your changes done to the `locales/<language>` directory"
+msgstr ""
+
+#: ../../README.md:62 ../../README.md:95
+msgid "If you have progressed with the translation beyond a certain threshold, consider [Publishing translations in a new language](#publish-translations-in-a-new-language)"
+msgstr ""
+
+#: ../../README.md:64
+msgid "Using any other package manager and manual scripts"
+msgstr ""
+
+#: ../../README.md:66
+msgid "If you cannot use [uv](https://docs.astral.sh/uv/) and/or [just](https://github.com/casey/just), you can:"
+msgstr ""
+
+#: ../../README.md:68
+msgid "manage Python packages in another way ([pip](https://pip.pypa.io/en/stable/), [Poetry](https://python-poetry.org/), etc.)"
+msgstr ""
+
+#: ../../README.md:69
+msgid "manage translation strings and build translated documents manually by invoking scripts from the [bin](bin/) directory"
+msgstr ""
+
+#: ../../README.md:73
+msgid "virtualenv and pip"
+msgstr ""
+
+#: ../../README.md:75
+msgid "Create a Python virtual environment in the `.venv` directory: `virtualenv .venv`"
+msgstr ""
+
+#: ../../README.md:76
+msgid "Activate the virtual environment: `source .venv/bin/activate`"
+msgstr ""
+
+#: ../../README.md:77
+msgid "Install the required Python packages using [pip](https://pip.pypa.io/en/stable/): `pip install -r requirements.txt`"
+msgstr ""
+
+#: ../../README.md:83
+msgid "Ensure the English translation templates ([translation-templates/](translation-templates/)) are extracted: `./bin/extract-translation-templates.sh`"
+msgstr ""
+
+#: ../../README.md:85
+msgid "Update the locale files for your language: `./bin/sync-translation-templates-to-locales.sh <language>`"
+msgstr ""
+
+#: ../../README.md:89
+msgid "Build translated documents: `./bin/build-translated-result.sh <language>`"
+msgstr ""
+
+#: ../../README.md:97
+msgid "Publish translations in a new language"
+msgstr ""
+
+#: ../../README.md:99
+msgid "To publish prebuilt documents translated in a new language to the `translations/<language>` directory:"
+msgstr ""
+
+#: ../../README.md:101
+msgid "add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file"
+msgstr ""
+
+#: ../../README.md:102
+msgid "whitelist its `translations/<language>` directory by adding a `!translations/<language>` rule to the [.gitignore](.gitignore) file"
+msgstr ""
+
+#: ../../README.md:104
+msgid "💡 Leave a trailing new line at the end of the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/CHANGELOG.po b/i18n/locales/jp/LC_MESSAGES/CHANGELOG.po
new file mode 100644
index 000000000..b142bce39
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/CHANGELOG.po
@@ -0,0 +1,6961 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-22 17:53+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../CHANGELOG.md:1
+msgid "2024-11-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3
+msgid "(Backward Compatibility Break) Synapse now defaults to enabling authenticated media"
+msgstr ""
+
+#: ../../../CHANGELOG.md:5
+msgid "**TLDR**: with this update, your Synapse homeserver will start requiring authentication for newly-uploaded media files. While the majority of the ecosystem (clients, bots, etc.) should support this, certain software may lack support for it (and you may wish to turn it off, if it's causing issues)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:7
+msgid "The default configuration for the Synapse homeserver now [enforces Authenticated media by default](https://element-hq.github.io/synapse/v1.120/upgrade.html#authenticated-media-is-now-enforced-by-default)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:9
+msgid "Servers like `matrix.org` have already [sunset unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) months ago."
+msgstr ""
+
+#: ../../../CHANGELOG.md:11
+msgid "Now that **various clients, bots, bridges and extra services have caught up with authenticated media support**, Synapse developers seem confident that it's time to enable authenticated media by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:13
+msgid "We're changing the playbook configuration for authenticated media to keep up with upstream defaults changing."
+msgstr ""
+
+#: ../../../CHANGELOG.md:15
+msgid "Old and unmaintained bridges (like all mx-puppet bridges, etc.) do not support authenticated media. Other software may be similarly affected. If you experience issues with some Matrix-related software, you may wish to disable authenticated media and contact the software maintainers to let them know."
+msgstr ""
+
+#: ../../../CHANGELOG.md:17
+msgid "You can disable authenticated media at any time by setting `matrix_synapse_enable_authenticated_media: false` in your `vars.yml` configuration file and re-running the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:20
+msgid "2024-11-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:22
+msgid "(Backward Compatibility Break) The playbook now defaults to Valkey, instead of KeyDB"
+msgstr ""
+
+#: ../../../CHANGELOG.md:24
+msgid "**TLDR**: if the playbook installed KeyDB (or Redis) as a dependency for you before, it will now replace it with [Valkey](https://valkey.io/) (a drop-in alternative). We [previously switched from Redis to KeyDB](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis), but Valkey is a better alternative, so we're switching again."
+msgstr ""
+
+#: ../../../CHANGELOG.md:26
+msgid "The playbook used to install Redis or KeyDB if services have a need for a Redis-compatible implementation ([enabling worker support for Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-workers), [enabling Hookshot encryption](docs/configuring-playbook-bridge-hookshot.md#end-to-bridge-encryption), etc.)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:28
+msgid "Earlier this year, we switched from Redis to KeyDB - see [(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:30
+msgid "Because Valkey seems to be a better successor to Redis (than KeyDB) and likely doesn't suffer from [issues like this one](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3544), we now replace KeyDB with Valkey."
+msgstr ""
+
+#: ../../../CHANGELOG.md:32
+msgid "Valkey (like KeyDB and Redis in the past) is an implicitly enabled dependency - you don't need custom configuration in `vars.yml` to enable it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:34
+msgid "Next time your run the playbook (via the `setup-all` tag), **KeyDB will be automatically uninstalled and replaced with Valkey**. Some Synapse downtime may occur while the switch happens."
+msgstr ""
+
+#: ../../../CHANGELOG.md:36
+msgid "Users on `arm32` should be aware that there's **neither a prebuilt `arm32` container image for Valkey**, nor the Valkey role supports self-building yet. Users on this architecture likely don't run Synapse with workers, etc., so they're likely in no need of Valkey (or Redis/KeyDB). If Redis is necessary in an `arm32` deployment, disabling Valkey and making the playbook fall back to Redis is possible (see below)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:38 ../../../CHANGELOG.md:378
+msgid "**The playbook still supports Redis** and you can keep using Redis (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:49
+msgid "**The playbook still supports KeyDB** and you can keep using KeyDB (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:59
+msgid "At some point in time in the future, we'll remove both KeyDB and Redis from the playbook, so we recommend that you migrate to Valkey earlier anyway."
+msgstr ""
+
+#: ../../../CHANGELOG.md:62
+msgid "2024-11-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:64
+msgid "HTTP-compression support for Traefik-based setups"
+msgstr ""
+
+#: ../../../CHANGELOG.md:66
+msgid "The playbook now **automatically enables HTTP-compression support** for major services powered by the playbook, like [Cinny](./docs/configuring-playbook-client-cinny.md), [Element Web](./docs/configuring-playbook-client-element-web.md), [Hydrogen](./docs/configuring-playbook-client-hydrogen.md), as well as for Matrix Client-Server and Federation APIs (`matrix.example.com`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:68
+msgid "Other services installed by the playbook are currently not compression-enabled, but may become so over time. This change is rolled out on a per-service basis (as opposed to doing it globally, at the Traefik entrypoint level) to allow certain services or route endpoints which do not behave well when compressed (e.g. [issue 3749](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3749)) to be excluded from compression."
+msgstr ""
+
+#: ../../../CHANGELOG.md:70
+msgid "A long time ago, various services were operating with `gzip`-compression enabled at the nginx level. Since the switch to Traefik (see [Goodbye, `matrix-nginx-proxy` 🪦](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/57c5271d9d6265a34a9d9cceb93365f685074f96/CHANGELOG.md#goodbye-matrix-nginx-proxy-)), all services (with the exception of Matrix APIs for Synapse worker-enabled setups which are powered by `nginx` via `synapse-reverse-proxy-companion`) have been operating without HTTP-compression support."
+msgstr ""
+
+#: ../../../CHANGELOG.md:72
+msgid "HTTP-compression is now done via Traefik's [compress](https://doc.traefik.io/traefik/middlewares/http/compress/) middleware. We use the default configuration for this middleware, which enables `zstd`, `br` and `gzip` support (in this order). This middleware's configuration can be configured via variables in the Traefik role (see `traefik_config_http_middlewares_compression_middleware_options`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:74
+msgid "If you're using your own Traefik reverse-proxy server ([Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)) instead of the playbook's integrated Traefik service, you can benefit from the same by:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:76
+msgid "defining a [compress](https://doc.traefik.io/traefik/middlewares/http/compress/) middleware (via the [file](https://doc.traefik.io/traefik/providers/file/) or [Docker](https://doc.traefik.io/traefik/providers/docker/) providers)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:77
+msgid "setting `matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled` to `true`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:78
+msgid "specifying the middleware's name in `matrix_playbook_reverse_proxy_traefik_middleware_compression_name` (e.g. `matrix_playbook_reverse_proxy_traefik_middleware_compression_name: my-compression-middleware@file`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:80
+msgid "Timeout adjustments for Traefik-based setups"
+msgstr ""
+
+#: ../../../CHANGELOG.md:82
+msgid "The playbook now supports configuring various [transport.respondingTimeouts](https://doc.traefik.io/traefik/routing/entrypoints/#respondingtimeouts) timeout values (`readTimeout`, `writeTimeout`, `idleTimeout`) for the `web`, `web-secure` and `matrix-federation` entrypoints."
+msgstr ""
+
+#: ../../../CHANGELOG.md:84
+msgid "If you're using your own Traefik reverse-proxy server ([Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)) instead of the playbook's integrated Traefik service, you may wish to do similar configuration changes to your setup manually."
+msgstr ""
+
+#: ../../../CHANGELOG.md:86
+msgid "The most interesting of these is the `readTimeout` configuration value (the maximum duration for reading the entire request, including the body), which used to default to `60s`. For large and slowly progressing file uploads, `60s` would often not be enough for the transfer to finish and uploads would end up being interrupted. The playbook now raises the `readTimeout` value to 5 minutes (`300s`) to improve this use-case."
+msgstr ""
+
+#: ../../../CHANGELOG.md:88
+msgid "The `traefik_config_entrypoint_web_transport_respondingTimeouts_*` variables (for the `web` entrypoint) cascade to affecting the timeout values for the `web-secure` and `matrix-federation` entrypoints, so you can easily adjust all timeout values using them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:90
+msgid "Example of the default timeout values used by the playbook:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:101
+msgid "Alternatively, you may adjust the timeout values for specific entrypoints (like `web-secure` and `matrix-federation`) using dedicated variables (like `traefik_config_entrypoint_web_secure_transport_respondingTimeouts_readTimeout` and `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_readTimeout`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:104
+msgid "2024-11-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:106
+msgid "Support for synapse-admin auto-configuration via /.well-known/matrix/client"
+msgstr ""
+
+#: ../../../CHANGELOG.md:108
+msgid "You can administrate your Synapse-powered homeserver using synapse-admin hosted externally (e.g. [admin.etke.cc](https://admin.etke.cc/)) and the synapse-admin instance would still auto-configure itself correctly for your server by [reading its `/.well-known/matrix/client` file](https://github.com/etkecc/synapse-admin/pull/126)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:110
+msgid "The playbook now configures the `/.well-known/matrix/client` file for this by default, injecting into it a `cc.etke.synapse-admin` section that contains the full synapse-admin configuration. This is done even if you don't enable the synapse-admin service in your configuration. The reason for always doing it is to allow users to skip the (small) overhead of self-hosting the non-core synapse-admin service, yet still be able to use it from elsewhere when needed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:112
+msgid "If you don't ever plan on using synapse-admin from other servers (besides your own due to [self-hosting synapse-admin](./docs/configuring-playbook-synapse-admin.md)), you **can disable this** `/.well-known/matrix/client` configuration via `matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_enabled: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:115
+msgid "2024-10-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:117
+msgid "(BC Break) Postmoogle's variable names need adjustments"
+msgstr ""
+
+#: ../../../CHANGELOG.md:119
+msgid "Due to the recategorization of [Postmoogle](./docs/configuring-playbook-bridge-postmoogle.md) from the bot to the bridge, its variables were renamed (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`). You need to adjust your `vars.yml` configuration accordingly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:121
+msgid "2024-10-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:123
+msgid "Support for Matrix Authentication Service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:125
+msgid "The playbook now supports installing and configuring [Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) (MAS)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:127
+msgid "Huge thanks to [Quentin Gliech](https://github.com/sandhose) from the [Element](https://element.io/) / [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service) team for answering our numerous questions about MAS."
+msgstr ""
+
+#: ../../../CHANGELOG.md:129
+msgid "This is an **experimental service** and there are **still certain issues with it** (see [Expectations](./docs/configuring-playbook-matrix-authentication-service.md#expectations)). Matrix server administrators should only consider switching if they identify with one or more [reasons to use Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md#reasons-to-use-matrix-authentication-service). As MAS adoption improves and more services are adjusted to support it, we expect that using MAS will become the norm."
+msgstr ""
+
+#: ../../../CHANGELOG.md:131
+msgid "Our [Setting up Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) documentation page has more details about this new service, what you might expect from the switch and how you can migrate your existing (Synapse) homeserver setup to MAS."
+msgstr ""
+
+#: ../../../CHANGELOG.md:134
+msgid "2024-09-27"
+msgstr ""
+
+#: ../../../CHANGELOG.md:136
+msgid "(BC Break) Postgres & Traefik roles have been relocated and variable names need adjustments"
+msgstr ""
+
+#: ../../../CHANGELOG.md:138
+msgid "Various roles have been relocated from the [devture](https://github.com/devture) organization to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization."
+msgstr ""
+
+#: ../../../CHANGELOG.md:140
+msgid "Along with the relocation, the `devture_` prefix was dropped from their variable names, so you need to adjust your `vars.yml` configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:142
+msgid "You need to do the following replacements:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:144
+msgid "`devture_postgres_` -> `postgres_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:145
+msgid "`devture_traefik_` -> `traefik_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:147
+msgid "As always, the playbook would let you know about this and point out any variables you may have missed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:150
+msgid "2024-09-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:152
+msgid "Support for baibot"
+msgstr ""
+
+#: ../../../CHANGELOG.md:154
+msgid "The playbook now supports installing [baibot](./docs/configuring-playbook-bot-baibot.md) (pronounced bye-bot) - a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖"
+msgstr ""
+
+#: ../../../CHANGELOG.md:156
+msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as well as many other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:158
+msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to the now-unmaintained [matrix-chatgpt-bot](./docs/configuring-playbook-bot-chatgpt.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:160
+msgid "To get started, see the [Setting up baibot](./docs/configuring-playbook-bot-baibot.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:162
+msgid "Switching synapse-admin to etke.cc's fork"
+msgstr ""
+
+#: ../../../CHANGELOG.md:164
+msgid "The playbook now installs [etke.cc](https://etke.cc/)'s [fork](https://github.com/etkecc/synapse-admin) of [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin) (originally developed by [Awesome-Technologies](https://github.com/Awesome-Technologies)). This fork is a drop-in replacement for the original software."
+msgstr ""
+
+#: ../../../CHANGELOG.md:166
+msgid "The creation of the fork has been provoked by users frequently encountering issues with the original synapse-admin software, such as unintentionally deleting their one-and-only admin user account (fixed [here](https://github.com/etkecc/synapse-admin/pull/1) and also contributed upstream [here](https://github.com/Awesome-Technologies/synapse-admin/pull/608) - to no avail for now). Since its inception, [a bunch of other quality-of-life improvements](https://github.com/etkecc/synapse-admin?tab=readme-ov-file#changes) have been made to the fork."
+msgstr ""
+
+#: ../../../CHANGELOG.md:168
+msgid "If upstream synapse-admin picks up the pace and improves, the etke.cc fork may disappear and the playbook may switch to the original software again. Until that time comes, we believe that etke.cc's fork is the better software to use right now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:170
+msgid "If you'd like to switch back to the original synapse-admin software, you can do so by adding the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:183
+msgid "2024-08-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:185
+msgid "New appservice-double-puppet service for better double-puppeting"
+msgstr ""
+
+#: ../../../CHANGELOG.md:187
+msgid "Mautrix bridges are undergoing large changes as announced in the [August 2024 releases & progress](https://mau.fi/blog/2024-08-mautrix-release/) blog post."
+msgstr ""
+
+#: ../../../CHANGELOG.md:189
+msgid "The playbook has already upgraded to the rewritten mautrix-slack ([v0.1.0](https://github.com/mautrix/slack/releases/tag/v0.1.0)) and mautrix-signal ([v0.7.0](https://github.com/mautrix/signal/releases/tag/v0.7.0)) bridges."
+msgstr ""
+
+#: ../../../CHANGELOG.md:191
+msgid "The newly rewritten bridges do not support double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) anymore, which has prompted us to switch to the new & better [appservice method](https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new) for double-puppeting. The playbook automates this double-puppeting setup for you if you enable the new [Appservice Double Puppet](./docs/configuring-playbook-appservice-double-puppet.md) service."
+msgstr ""
+
+#: ../../../CHANGELOG.md:193
+msgid "All non-deprecated mautrix bridges in the playbook have been reworked to support double-puppeting via an Appservice. Most bridges still support double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md), so the playbook supports it too. If only Shared Secret Auth is enabled, double-puppeting will be configured using that method (for the bridges that support it). That said, **Shared Secret Auth double-puppeting is being phased out and we recommend replacing it with the new Appservice method**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:195
+msgid "We recommend **enabling double-puppeting via the new Appservice method** by adding the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:201
+msgid "You can still **keep** [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) enabled. Non-mautrix bridges and other services (e.g. [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) may still require it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:203
+msgid "When both double-puppeting methods are enabled, the playbook will automatically choose the new and better Appservice method for bridges that support it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:206
+msgid "2024-08-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:208
+msgid "matrix-media-repo now configured for Authenticated Media"
+msgstr ""
+
+#: ../../../CHANGELOG.md:210
+msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), our matrix-media-repo implementation now automatically [sets up signing keys](https://docs.t2bot.io/matrix-media-repo/v1.3.5/installation/signing-key/) for Authenticated Media (as per [MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:212
+msgid "If you had never heard of Authenticated Media before, the [Sunsetting unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) article on [matrix.org](https://matrix.org/) is a good introduction."
+msgstr ""
+
+#: ../../../CHANGELOG.md:214
+msgid "This feature is enabled for matrix-media-repo installations by default and will append an additional (matrix-media-repo-generated signing key) to your homeserver's (Synapse or Dendrite) signing key. See the [Signing keys](./docs/configuring-playbook-matrix-media-repo.md#signing-keys) and [Key backup and revoking](./docs/configuring-playbook-matrix-media-repo.md#key-backup-and-revoking) sections of the matrix-media-repo documentation for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:216
+msgid "If you'd like to avoid this new feature, you can disable it by setting `matrix_media_repo_generate_signing_key: false` in your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:219
+msgid "2024-08-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:221
+msgid "(Backward Compatibility Break) matrix-corporal has been upgraded to v3"
+msgstr ""
+
+#: ../../../CHANGELOG.md:223
+msgid "The playbook now installs [matrix-corporal](https://github.com/devture/matrix-corporal) v3.0.0, which brings support for **power-level management** (thanks to [this PR](https://github.com/devture/matrix-corporal/pull/32))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:225
+msgid "This upgrade necessitates configuration policy changes as described in [matrix-corporal's changelog entry](https://github.com/devture/matrix-corporal/blob/5287cb81c82cd3b951c2a099b4697c3e0b384559/CHANGELOG.md#version-300-2024-08-08)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:227
+msgid "If you'd like to remain on the old (v2) version of matrix-corporal, you can do so by adding the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:233
+msgid "2024-07-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:235
+msgid "synapse-usage-exporter support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:237
+msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) - a small [Flask](https://flask.palletsprojects.com)-based webservice which can capture usage statistics from Synapse (via HTTP `PUT`) and then make them available for Prometheus to scrape."
+msgstr ""
+
+#: ../../../CHANGELOG.md:239
+msgid "To learn more see our [Enabling synapse-usage-exporter for Synapse usage statistics](docs/configuring-playbook-synapse-usage-exporter.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:242
+msgid "2024-07-06"
+msgstr ""
+
+#: ../../../CHANGELOG.md:244
+msgid "matrix-alertmanager-receiver support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:246
+msgid "For those wishing to more easily integrate [Prometheus](https://prometheus.io/)' alerting service ([Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/)) with Matrix, the playbook can now set up [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:248
+msgid "See [Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](./docs/configuring-playbook-alertmanager-receiver.md) for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:250
+msgid "Traefik v3 and HTTP/3 are here now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:252
+msgid "**TLDR**: Traefik was migrated from v2 to v3. Minor changes were done to the playbook. Mostly everything else worked out of the box. Most people will not have to do any tweaks to their configuration. In addition, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is now auto-enabled for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints. If you have a firewall in front of your server and you wish to benefit from `HTTP3`, you will need to open the `443` and `8448` UDP ports in it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:254
+msgid "Traefik v3"
+msgstr ""
+
+#: ../../../CHANGELOG.md:256
+msgid "The reverse-proxy that the playbook uses by default (Traefik) has recently been upgraded to v3 (see [this blog post](https://traefik.io/blog/announcing-traefik-proxy-v3-rc/) to learn about its new features). Version 3 includes some small breaking configuration changes requiring a [migration](https://doc.traefik.io/traefik/migration/v2-to-v3/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:258
+msgid "We have **updated the playbook to Traefik v3** (make sure to run `just roles` / `make roles` to get it)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:260
+msgid "There were **only minor playbook changes required** to adapt to Traefik v3, and only to the Ansible role for [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) where we changed a few [`PathPrefix` instances to `PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-pathprefix-and-pathregexp), because these instances were using a regular expression instead of a fixed path. For fixed-path values, `PathPrefix` is still the preferred matcher function to use."
+msgstr ""
+
+#: ../../../CHANGELOG.md:262
+msgid "**Most people using the playbook should not have to do any changes**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:264
+msgid "If you're using the playbook's Traefik instance to reverse-proxy to some other services of your own (not managed by the playbook), you may wish to review their Traefik labels and make sure they're in line with the [Traefik v2 to v3 migration guide](https://doc.traefik.io/traefik/migration/v2-to-v3/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:266
+msgid "If you've tweaked any of this playbook's `_path_prefix` variables and made them use a regular expression, you will now need to make additional adjustments. The playbook makes extensive use of `PathPrefix()` matchers in Traefik rules and `PathPrefix` does not support regular expressions anymore. To work around it, you may now need to override a whole `_traefik_rule` variable and switch it from [`PathPrefix` to `PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-pathprefix-and-pathregexp)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:268
+msgid "If you're not using [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) (the only role we had to tweak to adapt it to Traefik v3), you **may potentially downgrade to Traefik v2** (if necessary) by adding `traefik_verison: v2.11.4` to your configuration. People using `matrix-media-repo` cannot downgrade this way, because `matrix-media-repo` has been adjusted to use `PathRegexp` - a [routing matcher](https://doc.traefik.io/traefik/v2.11/routing/routers/#rule) that Traefik v2 does not understand."
+msgstr ""
+
+#: ../../../CHANGELOG.md:270
+msgid "HTTP/3 is enabled by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:272
+msgid "In Traefik v3, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is no longer considered experimental now. Due to this, **the playbook auto-enables HTTP3** for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints."
+msgstr ""
+
+#: ../../../CHANGELOG.md:274
+msgid "HTTP3 uses the UDP protocol and **the playbook (together with Docker) will make sure that the appropriate ports** (`443` over UDP & `8448` over UDP) **are exposed and whitelisted in your server's firewall**. However, **if you have another firewall in front of your server** (as is the case for many cloud providers), **you will need to manually open these UDP ports**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:276
+msgid "If you do not open the UDP ports correctly or there is some other issue, clients (browsers, mostly) will fall-back to [HTTP/2](https://en.wikipedia.org/wiki/HTTP/2) or even [HTTP/1.1](https://en.wikipedia.org/wiki/HTTP)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:278
+msgid "Still, if HTTP/3 cannot function correctly in your setup, it's best to disable advertising support for it (and misleading clients into trying to use HTTP/3)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:280
+msgid "To **disable HTTP/3**, you can use the following configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:294
+msgid "If you are using [your own webserver](./docs/configuring-playbook-own-webserver.md) (in front of Traefik), port binding on UDP port `8448` by default due to HTTP/3 is either unnecessary or [may get in the way](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3402). If it does, you can disable it:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:307
+msgid "2024-07-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:309
+msgid "synapse-admin is now restricted to your homeserver's URL by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:311
+msgid "A new feature introduced in synapse-admin [v0.10.0](https://github.com/Awesome-Technologies/synapse-admin/releases/tag/0.10.0) (released and supported by the playbook since a a few months ago) provides the ability to [restrict its usage to a specific homeserver](https://github.com/Awesome-Technologies/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) (or multiple homeservers)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:313
+msgid "The playbook has just started making use of this feature. **From now on, your synapse-admin instance will be restricted to the homeserver you're managing via the playbook**. When configured like this, the *Homeserver URL* field in synapse-admin's web UI changes from a text field to a dropdown having a single value (the URL of your homeserver). This makes usage simpler for most people, as they won't need to manually enter a *Homeserver URL* anymore."
+msgstr ""
+
+#: ../../../CHANGELOG.md:315
+msgid "If you'd like **to go back to the old unrestricted behavior**, use the following configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:323
+msgid "2024-06-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:325
+msgid "The URL-prefix for Hookshot generic webhooks has changed"
+msgstr ""
+
+#: ../../../CHANGELOG.md:327
+msgid "Until now, generic Hookshot webhook URLs looked like this: `https://matrix.example.com/hookshot/webhooks/:hookId`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:329
+msgid "The `/hookshot/webhooks` common prefix gets stripped by Traefik automatically, so Hookshot only sees the part that comes after (`/:hookId`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:331
+msgid "[A few years ago](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1681), Hookshot started to prefer to handle webhooks at a `/webhook/:hookId` path (instead of directly at `/:hookId`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:333
+msgid "To avoid future problems, we've [reconfigured](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/4704a60718946fd469aeee7fc3ae8127c633bb6b) our Hookshot configuration to use webhook URLs that include `/webhook` in the URL suffix (e.g. `/hookshot/webhooks/webhook/:hookId`, instead of `/hookshot/webhooks/:hookId`). This means that when we strip the common prefi (`/hookshot/webhooks`), we'll end up sending `/webhook/:hookId` to Hookshot, just like recommended."
+msgstr ""
+
+#: ../../../CHANGELOG.md:335
+msgid "When generating new webhooks, you should start seeing the new URLs being used."
+msgstr ""
+
+#: ../../../CHANGELOG.md:337
+msgid "**For now**, **both** old URLs (`/hookshot/webhooks/:hookId`) and new URLs (`/hookshot/webhooks/webhook/:hookId`) **continue to work**, so your webhooks will not break just yet."
+msgstr ""
+
+#: ../../../CHANGELOG.md:339
+msgid "However, **we recommend that you update all your old webhook URLs** (configured in other systems) to include the new `/webhook` path component, so that future Hookshot changes (whenever they come) will not break your webhooks. You don't need to do anything on the Hookshot side - you merely need to reconfigure the remote systems that use your webhook URLs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:342
+msgid "2024-06-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:344
+msgid "The maubot user is now managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:346
+msgid "To make things easier and to be consistent with other roles, the [maubot](./docs/configuring-playbook-bot-maubot.md) user (`bot.maubot` by default) is [now](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3376) automatically created be the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:348
+msgid "If you have an existing maubot installation, you will need to specify `matrix_bot_maubot_initial_password` in your `vars.yml` file to make the playbook not complain about it being undefined. Since the bot is already registered in your installation, there's nothing for the playbook to do anyway. In case you don't remember the password you've registered your maubot user account with, you can specify any value for this variable."
+msgstr ""
+
+#: ../../../CHANGELOG.md:350
+msgid "If you've registered another username for the bot (other than the recommended default of `bot.maubot`), consider adjusting the `matrix_bot_maubot_login` variable (e.g. `matrix_bot_maubot_login: my.maubot.username`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:353
+msgid "2024-06-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:355
+msgid "WeChat bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:357
+msgid "Thanks to [Tobias Diez](https://github.com/tobiasdiez)'s [efforts](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3241), the playbook now supports bridging to [WeChat](https://www.wechat.com/) via the [matrix-wechat](https://github.com/duo/matrix-wechat) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:359
+msgid "See our [Setting up WeChat bridging](docs/configuring-playbook-bridge-wechat.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:362
+msgid "2024-03-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:364
+msgid "(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis"
+msgstr ""
+
+#: ../../../CHANGELOG.md:366
+msgid "**TLDR**: if the playbook used installed Redis as a dependency for you before, it will now replace it with [KeyDB](https://docs.keydb.dev/) (a drop-in alternative) due to [Redis having changed its license](https://redis.com/blog/redis-adopts-dual-source-available-licensing/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:368
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now uses [KeyDB](https://docs.keydb.dev/) (a drop-in alternative for Redis), instead of [Redis](https://redis.io/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:370
+msgid "The playbook used to install Redis (and now installs KeyDB in its place) if services have a need for it ([enabling worker support for Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-workers), [enabling Hookshot encryption](docs/configuring-playbook-bridge-hookshot.md#end-to-bridge-encryption), etc.) or if you explicitly enabled the service (`redis_enabled: true` or `keydb_enabled: true`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:372
+msgid "This change is provoked by the fact that [Redis is now \"source available\"](https://redis.com/blog/redis-adopts-dual-source-available-licensing/). According to the Limitations of [the new license](https://redis.com/legal/rsalv2-agreement/) (as best as we understand them, given that we're not lawyers), using Redis in the playbook (even in a commercial FOSS service like [etke.cc](https://etke.cc/)) does not violate the new Redis license. That said, we'd rather neither risk it, nor endorse shady licenses and products that pretend to be free-software. Another high-quality alternative to Redis seems to be [Dragonfly](https://www.dragonflydb.io/), but the [Dragonfly license](https://github.com/dragonflydb/dragonfly?tab=License-1-ov-file#readme) is no better than Redis's."
+msgstr ""
+
+#: ../../../CHANGELOG.md:374
+msgid "Next time your run the playbook (via the `setup-all` tag), **Redis will be automatically uninstalled and replaced with KeyDB**. Some Synapse downtime may occur while the switch happens."
+msgstr ""
+
+#: ../../../CHANGELOG.md:376
+msgid "Users on `arm32` should be aware that there's **neither a prebuilt `arm32` container image for KeyDB**, nor the KeyDB role supports self-building yet. Users on this architecture likely don't run Synapse with workers, etc., so they're likely in no need of KeyDB (or Redis). If Redis is necessary in an `arm32` deployment, disabling KeyDB and making the playbook fall back to Redis is possible (see below)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:387
+msgid "2024-03-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:389
+msgid "Initial work on IPv6 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:391
+msgid "Thanks to [Tilo Spannagel](https://github.com/tilosp), the playbook can now enable IPv6 for container networks for various components (roles) via [the `devture_systemd_docker_base_ipv6_enabled` variable](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L14-L31)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:393
+msgid "It should be noted that:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:395
+msgid "Matrix roles (`roles/custom/matrix-*`) respect this variable, but external roles (those defined in `requirements.yml` and installed via `just roles`) do not respect it yet. Additional work is necessary"
+msgstr ""
+
+#: ../../../CHANGELOG.md:396
+msgid "changing the variable subsequently may not change existing container networks. Refer to [these instructions](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L26-L30)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:397
+msgid "this is all very new and untested"
+msgstr ""
+
+#: ../../../CHANGELOG.md:399
+msgid "Pantalaimon support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:401
+msgid "Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the playbook can now install the [Pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you. It's already possible to integrate it with [Draupnir](docs/configuring-playbook-bot-draupnir.md) to allow it to work in E2EE rooms - see our Draupnir docs for details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:403
+msgid "See our [Setting up Pantalaimon](docs/configuring-playbook-pantalaimon.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:406
+msgid "2024-03-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:408
+msgid "Support for Draupnir-for-all"
+msgstr ""
+
+#: ../../../CHANGELOG.md:410
+msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now install [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) (aka multi-instance Draupnir running in appservice mode)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:412
+msgid "This is an alternative to [running Draupnir in bot mode](./docs/configuring-playbook-bot-draupnir.md), which is still supported by the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:414
+msgid "The documentation page for [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) contains more information on how to install it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:417
+msgid "2024-02-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:419
+msgid "Support for bridging to Facebook/Messenger via the new mautrix-meta bridge"
+msgstr ""
+
+#: ../../../CHANGELOG.md:421
+msgid "The [mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-facebook.md) and [mautrix-instagram](./docs/configuring-playbook-bridge-mautrix-instagram.md) bridges are being [superseded by a new bridge](https://github.com/mautrix/facebook/issues/332) - the [mautrix-meta](https://github.com/mautrix/meta) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:423
+msgid "The playbook now supports the new mautrix-meta bridge - a single bridge, which can run in different modes and bridge to Messenger (via [Facebook](https://facebook.com/), Facebook over [Tor](https://www.torproject.org/) or via [Messenger](https://messenger.com/)) and [Instagram](https://instagram.com/). The playbook makes this bridge available via 2 separate Ansible roles, allowing you to easily run 2 instances of mautrix-meta, for bridging to both services at the same time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:425
+msgid "If you're using mautrix-facebook or mautrix-instagram right now, **you can still continue using the old bridges, but may wish to change to the new bridge implementations**. See:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:427
+msgid "[Setting up Instagram bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:429
+msgid "[Setting up Messenger bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-messenger.md)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:431
+msgid "The documentation pages contain more information on how to migrate."
+msgstr ""
+
+#: ../../../CHANGELOG.md:434
+msgid "2024-02-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:436
+msgid "Much larger Synapse caches and cache auto-tuning enabled by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:438
+msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook now uses much larger caches and enables Synapse's [cache auto-tuning functionality](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values). This work and the default values used by the playbook are inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/deployment/synapse.html)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:440
+msgid "The playbook has always used a very conservative cache factor (`matrix_synapse_caches_global_factor`) value of `0.5`, which may be OK for small and underactive deployments, but is not ideal for larger servers. Paradoxically, a small global cache factor value [does not necessarily decrease RAM usage as a whole](https://github.com/matrix-org/synapse/issues/3939)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:442
+msgid "The playbook now uses **a 20x larger cache factor** (currently `10`), adjusts a few other cache-related variables, and **enables cache auto-tuning** via the following variables:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:444
+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 ""
+
+#: ../../../CHANGELOG.md:445
+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 ""
+
+#: ../../../CHANGELOG.md:446
+msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:448
+msgid "These values should be good defaults for most servers, but may change over time as we experiment further."
+msgstr ""
+
+#: ../../../CHANGELOG.md:450
+msgid "Refer to our new [Tuning caches and cache autotuning](docs/maintenance-synapse.md#tuning-caches-and-cache-autotuning) documentation section for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:453
+msgid "2024-01-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:455
+msgid "(Backward-compatibility break) Minor changes necessary for some people serving a static website at the base domain"
+msgstr ""
+
+#: ../../../CHANGELOG.md:457
+msgid "This only affects people who are [Serving a static website at the base domain](./docs/configuring-playbook-base-domain-serving.md#serving-a-static-website-at-the-base-domain), but not managing its `index.html` through the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:459
+msgid "That is, for people who have `matrix_static_files_file_index_html_enabled: false` in their `vars.yml` configuration, the playbook has a new default behavior. Since the playbook is not managing the `index.html` file, it will default to a more sensible way of handling the base domain  - redirecting `https://example.com/` to `https://matrix.example.com/`, instead of serving a 404 page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:461
+msgid "If you are managing your static website by yourself (by dropping files into `/matrix/static-files/public` somehow), then you probably don't wish for such redirection to happen. You can disable it by adding `matrix_static_files_container_labels_base_domain_root_path_redirection_enabled: false` to your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:464
+msgid "2024-01-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:466
+msgid "Support for more efficient (specialized) Synapse workers"
+msgstr ""
+
+#: ../../../CHANGELOG.md:468
+msgid "Thanks to [Charles Wright](https://github.com/cvwright) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook has [received support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3100) for load-balancing the Synapse workload via [specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) which are supposed to work better than our old [generic workers](./docs/configuring-playbook-synapse.md#generic-workers) implementation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:470
+msgid "For now, playbook defaults remain unchanged and the `one-of-each` [workers preset](./docs/configuring-playbook-synapse.md#worker-presets) continues being the default. However, the default may change in the future. If you'd like to remain on this preset even if/when the defaults change, consider explicitly adding `matrix_synapse_workers_preset: one-of-each` to your `vars.yml` configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:472
+msgid "Our specialized workers setup is based on recommendations found in [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). What's special about our new setup is that we try to parse information out of the request (who the user is; which room is being operated on) and try to forward similar requests to the same worker. As an example, this means that once a worker caches some room information, subsequent requests for the same room will be routed to the same worker (which supposedly still has the room's state cached)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:474
+msgid "To get started, refer to our [Specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) documentation section."
+msgstr ""
+
+#: ../../../CHANGELOG.md:477
+msgid "2024-01-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:479
+msgid "Switching to Element's AGPLv3-licensed Synapse release"
+msgstr ""
+
+#: ../../../CHANGELOG.md:481
+msgid "A few months ago, the [Element](https://element.io/) company has [announced](https://element.io/blog/element-to-adopt-agplv3/) that their work on the Synapse homeserver would no longer be available under the permissive [Apache-2.0 license](https://www.apache.org/licenses/LICENSE-2.0), but only under:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:483
+msgid "the [AGPLv3](https://www.gnu.org/licenses/agpl-3.0.en.html) free-software license - the same license that this Ansible playbook has always used"
+msgstr ""
+
+#: ../../../CHANGELOG.md:484
+msgid "a proprietary license, for those wishing for Element to [sell them an exception](https://gnu.org/philosophy/selling-exceptions.html) to the AGPLv3 license"
+msgstr ""
+
+#: ../../../CHANGELOG.md:486
+msgid "You can also learn more in [this post](https://matrix.org/blog/2023/11/06/future-of-synapse-dendrite/) by the Matrix Foundation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:488
+msgid "The change has [already happened](https://element.io/blog/synapse-now-lives-at-github-com-element-hq-synapse/) and the first Synapse release under the new license is here: [v1.99.0](https://github.com/element-hq/synapse/releases/tag/v1.99.0)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:490
+msgid "There is no up-to-date alternative Synapse fork right now and this free-software (AGPLv3-licensed) playbook is definitely not against free-software licenses, so we are now switching to the Element-maintained Synapse release."
+msgstr ""
+
+#: ../../../CHANGELOG.md:492
+msgid "**What does this mean to you?**"
+msgstr ""
+
+#: ../../../CHANGELOG.md:494
+msgid "For most home users, it doesn't mean anything. Your installation will continue working as it should and you don't need to do anything."
+msgstr ""
+
+#: ../../../CHANGELOG.md:496
+msgid "For people building commercial products on top of Synapse, they may have to either buy a license exception from Element (from what we hear, the fee depends on the number of monthly-active users on your instance) or they may need to release all related code as free-software (which is what we've been doing at [etke.cc](https://etke.cc/) ([here](https://gitlab.com/etke.cc)) all along)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:498
+msgid "We're no lawyers and this changelog entry does not aim to give you the best legal advice, so please research on your own!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:500
+msgid "If you'd like to continue using the old Apache-2.0-licensed Synapse (for a while longer anyway), the playbook makes it possible by intruducing a new Ansible variable. You can do it like this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:512
+msgid "Notes:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:514
+msgid "if you had already upgraded Synapse to `v1.99.0` by running this playbook, you will still be able to downgrade to `v1.98.0`, because both releases use the same database schema version (`SCHEMA_COMPAT_VERSION = 83` - see [here for v1.98.0](https://github.com/element-hq/synapse/blob/v1.98.0/synapse/storage/schema/__init__.py#L131-L134) and [here for v1.99.0](https://github.com/element-hq/synapse/blob/v1.99.0/synapse/storage/schema/__init__.py#L137-L140)). More details on Synapse's database schema are available [here](https://element-hq.github.io/synapse/develop/development/database_schema.html). It appears that there are no new database migrations introduced in `v1.99.0`, so going back to the older release is possible. This is not guaranteed to hold true for future Synapse releases, so if you're seeing this early-enough, consider pinning the version and organization before re-running the playbook and getting upgraded to the latest version"
+msgstr ""
+
+#: ../../../CHANGELOG.md:516
+msgid "running an outdated homeserver exposes you to security issues and incompatibilities. Only consider doing this as a short-term solution."
+msgstr ""
+
+#: ../../../CHANGELOG.md:518
+msgid "2024-01-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:520
+msgid "`Draupnir` has been relicensed to AFL-3.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:522
+msgid "As of [#204](https://github.com/the-draupnir-project/Draupnir/pull/204) Draupnir changed its licence to AFL-3.0 from the CSL licence. This change affects playbook users who could not run Draupnir under the old license restrictions. The new license is considerably less restrictive and is OSI approved. Draupnir version v1.86.0 and later are covered by this license change."
+msgstr ""
+
+#: ../../../CHANGELOG.md:524
+msgid "2024-01-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:526
+msgid "Goodbye, `matrix-nginx-proxy` 🪦"
+msgstr ""
+
+#: ../../../CHANGELOG.md:528
+msgid "**TLDR**: All traces of the `matrix-nginx-proxy` reverse-proxy component are now gone. This brought about many other internal changes (and security improvements), so setups may need minor adjustments or suffer some (temporary) breakage. People who have been on the Traefik-native setup may upgrade without much issues. Those running their own Traefik instance may need minor changes. People who have been postponing the migration away from `matrix-nginx-proxy` (for more than a year already!) will now finally need to do something about it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:530
+msgid "Backstory on `matrix-nginx-proxy`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:532
+msgid "We gather here today to celebrate the loss of a once-beloved component in our stack - `matrix-nginx-proxy`. It's been our [nginx](https://nginx.org/)-based reverse-proxy of choice since the [first commit](https://github.com/spantaleev/matrix-docker-ansible-deploy/tree/87f5883f2455fb115457b65f267f17de305c053c) of this playbook, 7 years ago."
+msgstr ""
+
+#: ../../../CHANGELOG.md:534
+msgid "For 6 years, `matrix-nginx-proxy` has been the front-most reverse-proxy in our setup (doing SSL termination, etc.). After [transitioning to Traefik last year](#traefik-is-the-default-reverse-proxy-now), `matrix-nginx-proxy` took a step back. Nevertheless, since it was so ingrained into the playbook, it still remained in use - even if only internally. Despite our warnings of its imminent death, many of you have indubitably continued to use it instead of Traefik. Its suffering continued for too long, because it served many different purposes and massive effort was required to transition them to others."
+msgstr ""
+
+#: ../../../CHANGELOG.md:536
+msgid "To us, `matrix-nginx-proxy` was:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:538
+msgid "an [nginx](https://nginx.org/)-based reverse-proxy"
+msgstr ""
+
+#: ../../../CHANGELOG.md:539
+msgid "an Ansible role organizing the work of [certbot](https://certbot.eff.org/) - retrieving free [Let's Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-proxy` and for the [Coturn TURN server](./docs/configuring-playbook-turn.md)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:540
+msgid "a central component for reverse-proxying to the [long list of services](./docs/configuring-playbook.md) supported by the playbook. As such, it became a dependency that all these services had to inject themselves into during runtime"
+msgstr ""
+
+#: ../../../CHANGELOG.md:541
+msgid "an intermediary through which addons (bridges, bots) communicated with the homeserver. Going through an intermediary (instead of directly talking to the homeserver) is useful when certain components (like [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) are enabled, because it lets these services \"steal routes\" from the homeserver"
+msgstr ""
+
+#: ../../../CHANGELOG.md:542
+msgid "a webserver for serving the `/.well-known/matrix` static files (generated by the `matrix-base` role until now)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:543
+msgid "a webserver [serving your base domain](./docs/configuring-playbook-base-domain-serving.md) (and also generating the `index.html` page for it)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:544
+msgid "a central component providing global [HTTP Basic Auth](https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication) password-protection for all `/metrics` endpoints when metrics were exposed publicly for consumption from a remote Prometheus server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:546
+msgid "Talk about a jack of all trades! The [UNIX philosophy](https://en.wikipedia.org/wiki/Unix_philosophy) (and Docker container philosophy) of \"do one thing and do it well\" had been severely violated for too long."
+msgstr ""
+
+#: ../../../CHANGELOG.md:548
+msgid "On a related note, we also had a large chain of reverse-proxies in the mix. In the worst case, it was something like this: (Traefik -> `matrix-nginx-proxy:8080` -> `matrix-nginx-proxy:12080` -> `matrix-synapse-reverse-proxy-companion:8008` -> `matrix-synapse:8008`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:550
+msgid "Due to complexity and the playbook's flexibility (trying to accommodate a mix of tens of components), many layers of indirection were necessary. We do like reverse-proxies, but.. not quite enough to enjoy going through a chain of ~4 of them before reaching the target service."
+msgstr ""
+
+#: ../../../CHANGELOG.md:552
+msgid "After **a ton of work** in the last weeks (200+ commits, which changed 467 files - 8684 insertions and 8913 deletions), **we're finally saying goodbye** to `matrix-nginx-proxy`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:554
+msgid "Going Traefik-native and cutting out all middlemen"
+msgstr ""
+
+#: ../../../CHANGELOG.md:556
+msgid "In our new setup, you'll see the bare minimum number of reverse-proxies."
+msgstr ""
+
+#: ../../../CHANGELOG.md:558
+msgid "In most cases, there's only Traefik and all services being registered directly with it. When [Synapse workers](./docs/configuring-playbook-synapse.md#load-balancing-with-workers) are enabled, `matrix-synapse-reverse-proxy-companion` remains as an extra reverse-proxy that requests go through (for load-balancing to the correct Synapse worker), but in all other cases services are exposed directly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:560
+msgid "This reduces \"network\" hops (improving performance) and also decreases the number of components (containers). Each Ansible role in our setup is now independent and doesn't need to interact with other roles during runtime."
+msgstr ""
+
+#: ../../../CHANGELOG.md:562
+msgid "Traefik now has an extra job"
+msgstr ""
+
+#: ../../../CHANGELOG.md:564
+msgid "Previously, **Traefik had a single purpose** - being the main reverse-proxy. It was either front-most (terminating SSL, etc.) or you were [fronting Traefik with your own other reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy). In any case - it had this central (yet decentralized) job."
+msgstr ""
+
+#: ../../../CHANGELOG.md:566
+msgid "Now, **Traefik has one more role** - it serves as an intermediary which allows addon services (bridges, bots, etc.) to communicate with the homeserver. As mentioned above, such an intermediary service is not strictly necessary in all kinds of setups, but more complex setups (including [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) benefit from it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:568
+msgid "To perform this new role, Traefik now has a new internal [entrypoint](https://doc.traefik.io/traefik/routing/entrypoints/) called `matrix-internal-matrix-client-api`. All homeservers (Conduit, Dendrite, Synapse and even `matrix-synapse-reverse-proxy-companion`) and homeserver-related core services ([matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md), [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md) and potentially others) register their routes (using [container labels](https://docs.docker.com/config/labels-custom-metadata/)) not only on the public entrypoints (`web-secure`, `matrix-federation`), but also on this new internal entrypoint."
+msgstr ""
+
+#: ../../../CHANGELOG.md:570
+msgid "Doing so, services can contact Traefik on this entrypoint's dedicated port (the URL defaults to `http://matrix-traefik:8008`) and reach the homeserver Client-Server API as they expect. Internally, Traefik takes care of the routing to the correct service."
+msgstr ""
+
+#: ../../../CHANGELOG.md:572
+msgid "We've also considered keeping it simple and having services talk to the homeserver over the public internet (e.g. `https://matrix.example.com`) thus reusing all existing Traefik routing labels. In this scenario, performance was incredibly poor (e.g. 70 rps, instead of 1400 rps) due to TLS and networking overhead. The need for fast internal communication (via the new internal non-TLS-enabled Traefik entrypoint) is definitely there. In our benchmarks, Traefik even proved more efficient than nginx at doing this: ~1200 rps for Traefik compared to ~900 rps for nginx (out of ~1400 rps when talking to the Synapse homeserver directly)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:574
+msgid "Traefik serving this second purpose has a few downsides:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:576
+msgid "Traefik becomes a runtime dependency for all homeserver-dependant container services"
+msgstr ""
+
+#: ../../../CHANGELOG.md:577
+msgid "all homeserver-dependant services now need to be connected to the `traefik` container network, even if they don't need public internet exposure"
+msgstr ""
+
+#: ../../../CHANGELOG.md:579
+msgid "Despite these downsides (which the playbook manages automatically), we believe it's still a good compromise given the amount of complexity it eliminates and the performance benefits it yields. One alternative we've [considered](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3045#issuecomment-1867327001) was adding a new intermediary service (e.g. `matrix-homeserver-proxy` powered by nginx), but this both had much higher complexity (one more component in the mix; duplication of effort to produce nginx-compatible route definitions for it) and slightly worse performance (see above)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:581
+msgid "People running the default Traefik setup do not need to do anything to make Traefik take on this extra job. Your Traefik configuration will be updated automatically."
+msgstr ""
+
+#: ../../../CHANGELOG.md:583
+msgid "**People runnning their own Traefik reverse-proxy need to do [minor adjustments](#people-managing-their-own-traefik-instance-need-to-do-minor-changes)**, as described in the section below."
+msgstr ""
+
+#: ../../../CHANGELOG.md:585
+msgid "You may disable Traefik acting as an intermediary by explicitly setting `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_enabled` to `false`. Services would then be configured to talk to the homeserver directly, giving you a slight performance boost and a \"simpler\" Traefik setup. However, such a configuration is less tested and will cause troubles, especially if you enable more services (like `matrix-media-repo`, etc.) in the future. As such, it's not recommended."
+msgstr ""
+
+#: ../../../CHANGELOG.md:587
+msgid "People managing their own Traefik instance need to do minor changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:589
+msgid "This section is for people [managing their own Traefik instance on the Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you). Those [using Traefik managed by the playbook](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) don't need to do any changes."
+msgstr ""
+
+#: ../../../CHANGELOG.md:591
+msgid "Because [Traefik has an extra job now](#traefik-now-has-an-extra-job), you need to adapt your configuration to add the additional `matrix-internal-matrix-client-api` entrypoint and potentially configure the `matrix_playbook_reverse_proxy_container_network` variable. See the [Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you) documentation section for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:593
+msgid "People fronting Traefik with another reverse proxy need to do minor changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:595
+msgid "We've already previously mentioned that you need to do some minor [configuration changes related to `traefik_additional_entrypoints_auto`](#backward-compatibility-configuration-changes-required-for-people-fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:597
+msgid "If you don't do these changes (switching from `traefik_additional_entrypoints_auto` to multiple other variables), your Traefik setup will not automatically receive the new `matrix-internal-matrix-client-api` Traefik entrypoint and Traefik would not be able to perform [its new duty of connecting addons with the homeserver](#traefik-now-has-an-extra-job)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:599
+msgid "Supported reverse proxy types are now fewer"
+msgstr ""
+
+#: ../../../CHANGELOG.md:601
+msgid "This section is for people using a more custom reverse-proxy setup - those having `matrix_playbook_reverse_proxy_type` set to a value different than the default (`playbook-managed-traefik`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:603
+msgid "Previously, we allowed you to set `matrix_playbook_reverse_proxy_type` to 7 different values to accommodate various reverse-proxy setups."
+msgstr ""
+
+#: ../../../CHANGELOG.md:605
+msgid "The complexity of this is too high, so we only support 3 values right now:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:607
+msgid "(the default) `playbook-managed-traefik`, when you're [using Traefik managed by the playbook](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:608
+msgid "`other-traefik-container`, when you're [managing your own Traefik instance on the Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:609
+msgid "`none`, when you wish for [no reverse-proxy integration to be done at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:611
+msgid "The `none` value is not recommended and may not work adequately, due to lack of testing and [Traefik's new responsibilities](#traefik-now-has-an-extra-job) in our setup."
+msgstr ""
+
+#: ../../../CHANGELOG.md:613
+msgid "**Previous values that are now gone** (and the playbook would report them as such) are: `playbook-managed-nginx`, `other-nginx-non-container`, `other-on-same-host` and `other-on-another-host`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:615
+msgid "If you were using these values as a way to stay away from Traefik, you now have 2 options:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:617
+msgid "(recommended) [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:618
+msgid "(not recommended) [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all) and reverse-proxying to each and every service manually"
+msgstr ""
+
+#: ../../../CHANGELOG.md:620
+msgid "Container networking changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:622
+msgid "Now that `matrix-nginx-proxy` is not in the mix, it became easier to clear out some other long-overdue technical debt."
+msgstr ""
+
+#: ../../../CHANGELOG.md:624
+msgid "Since the very beginning of this playbook, all playbook services were connected to a single (shared) `matrix` container network. Later on, some additional container networks appeared, but most services (database, etc.) still remained in the `matrix` container network.  This meant that any random container in this network could try to talk (or attack) the Postgres database operating in the same `matrix` network."
+msgstr ""
+
+#: ../../../CHANGELOG.md:626
+msgid "Moving components (especially the database) into other container networks was difficult - it required changes to many other components to ensure correct connectivity."
+msgstr ""
+
+#: ../../../CHANGELOG.md:628
+msgid "All the hard work has been done now. We've added much more isolation between services by splitting them up into separate networks (`matrix-homeserver`, `matrix-addons`, `matrix-monitoring`, `matrix-exim-relay`, etc). Components are only joined to the networks they need and should (for the most part) not be able to access unrelated things."
+msgstr ""
+
+#: ../../../CHANGELOG.md:630
+msgid "Carrying out these container networking changes necessitated modifying many components, so **we're hoping not too many bugs were introduced in the process**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:632
+msgid "We've refrained from creating too many container networks (e.g. one for each component), to avoid exhausting Docker's default network pool and contaminating the container networks list too much."
+msgstr ""
+
+#: ../../../CHANGELOG.md:634
+msgid "Metrics exposure changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:636
+msgid "This section is for people who are exposing monitoring metrics publicly, to be consumed by an external Prometheus server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:638
+msgid "Previously, `matrix-nginx-proxy` was potentially password-protecting all `/metrics/*` endpoints with the same username and password (specified as plain-text in your `vars.yml` configuration file)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:640
+msgid "From now on, there are new variables for doing roughly the same - `matrix_metrics_exposure_enabled`, `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`. See the [Prometheus & Grafana](./docs/configuring-playbook-prometheus-grafana.md) docs page for details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:642
+msgid "`matrix-nginx-proxy` is not acting as a \"global guardian\" anymore. Now, each role provides its own metrics exposure and protection by registering with Traefik. Nevertheless, all roles are wired (via playbook configuration in `group_vars/matrix_servers`) to obey these new `matrix_metrics_exposure_*` variables. We've eliminated the centralization, but have kept the ease of use. Now, you can also do per-service password-protection (with different credentials), should you need to do that for some reason."
+msgstr ""
+
+#: ../../../CHANGELOG.md:644
+msgid "The playbook will tell you about all variables that you need to migrate during runtime, so rest assured - you shouldn't be able to miss anything!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:646
+msgid "Matrix static files"
+msgstr ""
+
+#: ../../../CHANGELOG.md:648
+msgid "As mentioned above, static files like `/.well-known/matrix/*` or your base domain's `index.html` file (when [serving the base domain via the Matrix server](./docs/configuring-playbook-base-domain-serving.md) was enabled) were generated by the `matrix-base` or `matrix-nginx-proxy` roles and put into a `/matrix/static-files` directory on the server. Then `matrix-nginx-proxy` was serving all these static files."
+msgstr ""
+
+#: ../../../CHANGELOG.md:650
+msgid "All of this has been extracted into a new `matrix-static-files` Ansible role that's part of the playbook. The static files generated by this new role still live at roughly the same place (`/matrix/static-files/public` directory, instead of `/matrix/static-files`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:652
+msgid "The playbook will migrate and update the `/.well-known/matrix/*` files automatically but not your own files in `nginx-proxy/data/matrix-domain/` you will need to back these up yourself otherwise they will be lost. It will also warn you about usage of old variable names, so you can adapt to the new names."
+msgstr ""
+
+#: ../../../CHANGELOG.md:654
+msgid "A note on performance"
+msgstr ""
+
+#: ../../../CHANGELOG.md:656
+msgid "Some of you have been voicing their concerns (for a long time) about Traefik being too slow and nginx being better."
+msgstr ""
+
+#: ../../../CHANGELOG.md:658
+msgid "Some online benchmarks support this by demonstrating slightly higher SSL-termination performance in favor of nginx. The upcoming Traefik v3 release is [said to](https://medium.com/beyn-technology/is-nginx-dead-is-traefik-v3-20-faster-than-traefik-v2-f28ffb7eed3e) improve Traefik's SSL performance by some 20%, but that still ends up being somewhat slower than nginx."
+msgstr ""
+
+#: ../../../CHANGELOG.md:660
+msgid "We believe that using Traefik provides way too many benefits to worry about this minor performance impairment."
+msgstr ""
+
+#: ../../../CHANGELOG.md:662
+msgid "The heaviest part of running a Matrix homeserver is all the slow and potentially inefficient things the homeserver (e.g. Synapse) is doing. These things affect performance much more than whatever reverse-proxy is in front. Your server will die the same way by joining the famously large **Matrix HQ** room, no matter which reverse-proxy you put in front."
+msgstr ""
+
+#: ../../../CHANGELOG.md:664
+msgid "Even our previously mentioned benchmarks (yielding ~1300 rps) are synthetic - hitting a useless `/_matrix/client/versions` endpoint. Real-use does much more than this."
+msgstr ""
+
+#: ../../../CHANGELOG.md:666
+msgid "If this is still not convincing enough for you and you want the best possible performance, consider [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) (thus having the slowest part - SSL termination - happen elsewhere) or [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all). The playbook will not get in your way of doing that, but these options may make your life much harder. Performance comes at a cost, after all."
+msgstr ""
+
+#: ../../../CHANGELOG.md:668
+msgid "Migration procedure"
+msgstr ""
+
+#: ../../../CHANGELOG.md:670
+msgid "The updated playbook will automatically perform some migration tasks for you:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:672
+msgid "It will stop and remove the `matrix-nginx-proxy` systemd service and container for you. This behavior cannot be disabled. It's essential that this service gets stopped, because it remaining running (and having container labels) may confuse Traefik as to where to route HTTP requests."
+msgstr ""
+
+#: ../../../CHANGELOG.md:674
+msgid "It will delete the `/matrix/nginx-proxy` directory and all files within it. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_uninstallation_enabled: false` to your `vars.yml` configuration file. Doing so will leave its data around."
+msgstr ""
+
+#: ../../../CHANGELOG.md:676
+msgid "It will delete the `/matrix/ssl` directory and all files within it. You can disable this behavior by adding `matrix_playbook_migration_matrix_ssl_uninstallation_enabled: false` to your `vars.yml` configuration file. If you have some important certificates there for some reason, take them out or temporarily disable removal of these files until you do."
+msgstr ""
+
+#: ../../../CHANGELOG.md:678
+msgid "It will tell you about all variables (`matrix_nginx_proxy_*` and many others - even from other roles) that have changed during this large nginx-elimination upgrade. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_elimination_variable_transition_checks_enabled: false` to your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:680
+msgid "It will tell you about any leftover `matrix_nginx_proxy_*` variables in your `vars.yml` file. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_leftover_variable_validation_checks_enabled: false` to your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:682
+msgid "It will tell you about any leftover `matrix_ssl_*` variables in your `vars.yml` file. You can disable this behavior by adding `matrix_playbook_migration_matrix_ssl_leftover_variable_checks_enabled: false` to your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:684
+msgid "We don't recommend changing these variables and suppressing warnings, unless you know what you're doing."
+msgstr ""
+
+#: ../../../CHANGELOG.md:686
+msgid "**Most people should just upgrade as per-normal**, bearing in mind that a lot has changed and some issues may arise. The playbook would guide you through renamed variables automatically."
+msgstr ""
+
+#: ../../../CHANGELOG.md:688
+msgid "Conclusion"
+msgstr ""
+
+#: ../../../CHANGELOG.md:690
+msgid "Thousands of lines of code were changed across hundreds of files. All addons (bridges, bots) were rewired in terms of container networking and in terms of how they reach the homeserver."
+msgstr ""
+
+#: ../../../CHANGELOG.md:692
+msgid "I don't actively use all the ~100 components offered by the playbook (no one does), nor do I operate servers exercising all edge-cases. As such, issues may arise. Please have patience and report (or try to fix) these issues!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:695
+msgid "2024-01-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:697
+msgid "(Backward Compatibility) Configuration changes required for people fronting the integrated reverse-proxy webserver with another reverse-proxy"
+msgstr ""
+
+#: ../../../CHANGELOG.md:699
+msgid "If you're on the default setup (using the Traefik reverse-proxy as installed by the playbook), you don't need to do anything."
+msgstr ""
+
+#: ../../../CHANGELOG.md:701
+msgid "People who are [Fronting the integrated Traefik reverse-proxy webserver with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy), as per our previous instructions are redefining `traefik_additional_entrypoints_auto` in their `vars.yml` configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:703
+msgid "Such a full variable redefinion is intrustive, because it prevents the playbook from injecting additional entrypoints into the Traefik webserver. In the future, the playbook may have a need to do so."
+msgstr ""
+
+#: ../../../CHANGELOG.md:705
+msgid "For this reason, we no longer recommend completely redefining `traefik_additional_entrypoints_auto`. The playbook now defines [various `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_*` variables in the `defaults/main.yml` file](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-base/defaults/main.yml) of the `matrix-base` role which can be used as a safer alternative to `traefik_additional_entrypoints_auto`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:707
+msgid "Adapt your configuration as seen below:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:740
+msgid "Also, feel free to read the [Fronting the integrated Traefik reverse-proxy webserver with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) documentation section again for additional details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:743
+msgid "2024-01-13"
+msgstr ""
+
+#: ../../../CHANGELOG.md:745
+msgid "matrix-reminder-bot update with more secure (backward-incompatible) default settings"
+msgstr ""
+
+#: ../../../CHANGELOG.md:747
+msgid "**TLDR**: your updated (to [v0.3.0](https://github.com/anoadragon453/matrix-reminder-bot/releases/tag/v0.3.0)) [matrix-reminder-bot](./docs/configuring-playbook-bot-matrix-reminder-bot.md) is now more secure. By default, like other bridges/bots managed by the playbook, it will only provide its services to users of your own server (not to anyone, even across the Matrix Federation). If that's fine, there's nothing you need to do."
+msgstr ""
+
+#: ../../../CHANGELOG.md:749
+msgid "Maintenance of [matrix-reminder-bot](./docs/configuring-playbook-bot-matrix-reminder-bot.md) has been picked up by [Kim Brose](https://github.com/HarHarLinks) and [@svierne](https://github.com/svierne)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:751
+msgid "Thanks to them, a new [v0.3.0](https://github.com/anoadragon453/matrix-reminder-bot/releases/tag/v0.3.0) release is out. The new version is now available for the ARM64 architecture, so playbook users on this architecture will no longer need to wait for [self-building](./docs/self-building.md) to happen."
+msgstr ""
+
+#: ../../../CHANGELOG.md:753
+msgid "The new version also comes with new `allowlist` and `blocklist` settings, which make it possible to restrict who can use the bot. Previously anyone, even across the Matrix Federation could talk to it and schedule reminders."
+msgstr ""
+
+#: ../../../CHANGELOG.md:755
+msgid "The playbook defaults all bridges and bots (where possible) to only be exposed to users of the current homeserver, not users across federation. Thanks to the new version of this bot making such a restriction possible, we're now making use of it. The playbook (via its `group_vars/matrix_servers` file) automatically enables the `allowlist` (`matrix_bot_matrix_reminder_bot_allowlist_enabled: true`) and configures it in such a way (`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) so as to restrict the bot to your homeserver's users."
+msgstr ""
+
+#: ../../../CHANGELOG.md:757
+msgid "If you need **to undo or tweak these security improvements**, you can change your `vars.yml` file to:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:759
+msgid "disable the allowlist (`matrix_bot_matrix_reminder_bot_allowlist_enabled: false`), making the bot allow usage by anyone, anywhere"
+msgstr ""
+
+#: ../../../CHANGELOG.md:761
+msgid "inject additional allowed servers or users by adding **additional** (on top of the default allowlist in `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) custom regexes in the `matrix_bot_matrix_reminder_bot_allowlist_regexes_custom` list variable (see the [syntax reference](https://github.com/anoadragon453/matrix-reminder-bot/blob/1e910c0aa3469d280d93ee7e6c6d577227a3460c/sample.config.yaml#L43-L49))"
+msgstr ""
+
+#: ../../../CHANGELOG.md:763
+msgid "override the default allowlist (in the `group_vars/matrix_servers` file) by redefining `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:766
+msgid "2024-01-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:768
+msgid "matrix-mailer has been replaced by the exim-relay external role"
+msgstr ""
+
+#: ../../../CHANGELOG.md:770 ../../../CHANGELOG.md:1410
+msgid "We're continuing our effort to make [the playbook use external roles for some things](#the-playbook-now-uses-external-roles-for-some-things), so as to avoid doing everything ourselves and to facilitate code re-use."
+msgstr ""
+
+#: ../../../CHANGELOG.md:772
+msgid "The `matrix-mailer` role has been moved to its own repository ([ansible-role-exim-relay](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay)) that this playbook now includes."
+msgstr ""
+
+#: ../../../CHANGELOG.md:774
+msgid "To migrate:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:776
+msgid "pull the playbook changes, as usual"
+msgstr ""
+
+#: ../../../CHANGELOG.md:777
+msgid "update your roles (run `just roles` or `make roles`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:778
+msgid "update your `vars.yml`, renaming `matrix_mailer`-prefixed variables to `exim_relay`-prefixed ones (e.g. `matrix_mailer_sender_address` -> `exim_relay_sender_address`). If you find none, it means you're using the default configuration and your migraiton job is even simpler."
+msgstr ""
+
+#: ../../../CHANGELOG.md:779
+msgid "re-run the playbook (`install-all` or `setup-all`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:781
+msgid "The playbook will take care of stopping the old `matrix-mailer` systemd service, relocating its directory and restarting it under the new name (`matrix-exim-relay.service`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:784
+msgid "2024-01-02"
+msgstr ""
+
+#: ../../../CHANGELOG.md:786
+msgid "mautrix-signal now powered by the new Go-based bridge"
+msgstr ""
+
+#: ../../../CHANGELOG.md:788
+msgid "The old Python-based [mautrix-signal](https://github.com/mautrix/signal) bridge is no longer maintained upstream. It's also known to have issues linking new devices."
+msgstr ""
+
+#: ../../../CHANGELOG.md:790
+msgid "It seems like the path forward is to switch to the new mautrix-signal bridge written in Golang, which we did thanks to [PR #3031](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3041) by [Pierre 'McFly' Marty](https://github.com/pm-McFly)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:792
+msgid "The playbook should **automatically migrate your mautrix-signal installation to the new bridge code**. You will **need to relink all your devices** to continue your bridged conversations."
+msgstr ""
+
+#: ../../../CHANGELOG.md:795
+msgid "2023-10-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:797
+msgid "Enabling `allow_public_rooms_over_federation` by default for Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:799
+msgid "**TDLR**: if your Matrix server is federating (which it mostly likely is, unless you've [disabled federation](docs/configuring-playbook-federation.md#disabling-federation)), your public rooms will not only be joinable across federation (as they've always been), but from now on will be discoverable (made available as a list across federation). We're changing this by flipping the value for Synapse's `allow_public_rooms_over_federation` setting to `true`, going against the upstream default. Servers that disable federation are not affected. Servers that have public rooms which are not published to the room directory are also not affected."
+msgstr ""
+
+#: ../../../CHANGELOG.md:801
+msgid "We generally try to stick to the default configuration for Synapse (and all other components), unless these defaults seem wrong or harmful. One such previous case from a few months ago was us [Enabling `forget_rooms_on_leave` by default for Synapse](#enabling-forget_rooms_on_leave-by-default-for-synapse) - the default value was making Synapse more wasteful of resources by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:803
+msgid "Today, we're going against upstream defaults again and flipping the `allow_public_rooms_over_federation` configuration option to `true`. This way, public rooms on your server will be made discoverable by others via federation, using the [`GET /_matrix/federation/v1/publicRooms` of the Server-Server API](https://spec.matrix.org/v1.8/server-server-api/#get_matrixfederationv1publicrooms)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:805
+msgid "The upstream Synapse default is `false` (disabled), so that public rooms are not exposed for other servers to discover (learn about their existence). Nevertheless, even if these rooms are not exposed (listed) for discovery, they are **still joinable** by anyone who knows their address or is invited to the room by an existing member."
+msgstr ""
+
+#: ../../../CHANGELOG.md:807
+msgid "**We go against the upstream default** in an effort to make Matrix federation more useful - a public room should be globally public - not only joinable, but also discoverable across federation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:809
+msgid "The **historical reasoning** behind this change is as follows:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:811
+msgid "`allow_public_rooms_over_federation` seems to have been enabled by default for Synapse until v1.7.0 (~2019), just like we believe it should be for a globally-federating network - rooms should be joinable and discoverable across federation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:813
+msgid "In Synapse v1.7.0 (~2019), `allow_public_rooms_over_federation` [got disabled](https://github.com/element-hq/synapse/blob/e9069c9f919685606506f04527332e83fbfa44d9/docs/upgrade.md?plain=1#L1877-L1891) by default in a [security-by-obscurity](https://en.wikipedia.org/wiki/Security_through_obscurity) workaround for misconfigured servers. See the [Avoiding unwelcome visitors on private Matrix servers](https://matrix.org/blog/2019/11/09/avoiding-unwelcome-visitors-on-private-matrix-servers/) `matrix.org` blog article. We believe that people wishing for a truly private server, should [disable federation](docs/configuring-playbook-federation.md#disabling-federation), instead of having a fully-federating server and trying to hide its public rooms. We also provide other workarounds below. We (and the Synapse team, obviously) believe that Matrix should federate by default, so federating the public room list seems to make sense."
+msgstr ""
+
+#: ../../../CHANGELOG.md:815
+#, python-format
+msgid "[etke.cc](https://etke.cc/) has been developing the free-software [Matrix Rooms Search](https://github.com/etkecc/mrs) project for a while now. One public (demo) instance of it is hosted at [matrixrooms.info](https://matrixrooms.info/). This search engine tries to go through the Matrix federation and discover & index public rooms to allow people to find them. We believe it's vital for Matrix (and any chat or social network for that matter) to be more discoverable, so that people can find communities and others to talk to. Today (on 23rd of October 2023), `matrixrooms.info` is indexing `23066` Matrix servers. Of these, only `1567` servers (7%) are making their public rooms discoverable. Who knows what wonderful communities and rooms are available on these 93% other Matrix servers that are supposedly federating, but are still gate-keeping their public room list. Indubitably, many of these servers are hosted via matrix-docker-ansible-deploy, so we feel partially responsible for making Matrix federation less useful."
+msgstr ""
+
+#: ../../../CHANGELOG.md:817
+msgid "Here are **actions you may wish to take** as a result of this change:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:819
+msgid "(recommended) embrace the new default. If your Matrix server is federating, your public rooms have always been joinable across federation anyway. Exposing the list of public rooms does no harm and more-so does good by contributing to the usefulness of the Matrix network by facilitating room discovery."
+msgstr ""
+
+#: ../../../CHANGELOG.md:821
+msgid "(switch to a better way of doings things on your semi-private server) The problem that the Synapse team appears to have solved by flipping the `allow_public_rooms_over_federation` default in Synapse v1.7.0 seems to for \"mostly private\" servers, which federate and have a bunch of rooms made public (and published in their room directory) in an effort to allow people on the same homeserver to easily find and join them (self-onboarding). With the introduction of Matrix Spaces, you can reorganize your flow around spaces - you can auto-join your users to a Matrix Space (via Synapse's `auto_join_rooms` setting - controlled by our `matrix_synapse_auto_join_rooms` variable), then add a bunch of rooms to the space and make them joinable by people belonging to the space. That is to say, do not make rooms public and do not publish them to the room directory unless they are really public. Instead, use other mechanisms for semi-public rooms or private rooms. One alternative is to stick to what you're doing (public rooms published to your rooms directory) but having a `m.federate: true` flag set during creation (clients like Element Web have a nice UI checkbox for this) to explicitly disable federation for them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:823
+msgid "(keeping the old behavior) if you wish to keep doing what you're doing (keeping your Matrix server federating, but hiding its public rooms list), add `matrix_synapse_allow_public_rooms_over_federation: false` to your `vars.yml` configuration. This restores the old behavior. You may also consider [disabling federation](docs/configuring-playbook-federation.md#disabling-federation) completely instead of relying on security-by-obscurity measures."
+msgstr ""
+
+#: ../../../CHANGELOG.md:826
+msgid "2023-10-18"
+msgstr ""
+
+#: ../../../CHANGELOG.md:828
+msgid "Postgres parameters are automatically tuned now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:830
+msgid "The playbook has provided some hints about [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) for quite a while now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:832
+msgid "From now on, the [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) automatically tunes your Postgres configuration with the same [calculation logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) that powers https://pgtune.leopard.in.ua/."
+msgstr ""
+
+#: ../../../CHANGELOG.md:834
+msgid "Our [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) documentation page has details about how you can turn auto-tuning off or adjust the automatically-determined Postgres configuration parameters manually."
+msgstr ""
+
+#: ../../../CHANGELOG.md:836
+msgid "People who [enable load-balancing with Synapse workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) no longer need to increase the maximum number of Postgres connections manually (previously done via `postgres_process_extra_arguments`). There's a new variable (`postgres_max_connections`) for controlling this number and the playbook automatically raises its value from `200` to `500` for setups which enable workers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:839
+msgid "2023-08-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:841
+msgid "SchildiChat Web support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:843
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client."
+msgstr ""
+
+#: ../../../CHANGELOG.md:845
+msgid "See our [Configuring SchildiChat Web](docs/configuring-playbook-client-schildichat-web.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:848
+msgid "2023-08-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:850
+msgid "mautrix-wsproxy support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:852
+msgid "Thanks to [Johan Swetzén](https://github.com/jswetzen)'s efforts (who finished what was started by [James Reilly](https://github.com/hanthor) and [Shreyas Ajjarapu](https://github.com/shreyasajj)), the playbook now supports bridging to Android SMS and Apple iMessage via the [mautrix-wsproxy](https://github.com/mautrix/wsproxy) service (in combination with a [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android phone)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:854
+msgid "See our [Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](docs/configuring-playbook-bridge-mautrix-wsproxy.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:857
+msgid "2023-07-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:859
+msgid "matrix-registration-bot usage changed"
+msgstr ""
+
+#: ../../../CHANGELOG.md:861
+msgid "[matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) got some updates and now supports password-only-based login. Therefore the bot now doesn't need any manual configuration except setting a password in your `vars.yml`. The bot will be registered as admin and access tokens will be obtained automatically by the bot."
+msgstr ""
+
+#: ../../../CHANGELOG.md:863
+msgid "**For existing users** You need to set `matrix_bot_matrix_registration_bot_bot_password` if you previously only used `matrix_bot_matrix_registration_bot_bot_access_token`. Please also remove the following deprecated settings"
+msgstr ""
+
+#: ../../../CHANGELOG.md:865
+msgid "`matrix_bot_matrix_registration_bot_bot_access_token`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:866
+msgid "`matrix_bot_matrix_registration_bot_api_token`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:869
+msgid "2023-07-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:871
+msgid "mautrix-gmessages support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:873
+msgid "Thanks to [Shreyas Ajjarapu](https://github.com/shreyasajj)'s efforts, the playbook now supports bridging to [Google Messages](https://messages.google.com/) via the [mautrix-gmessages](https://github.com/mautrix/gmessages) bridge. See our [Setting up Mautrix Google Messages bridging](docs/configuring-playbook-bridge-mautrix-gmessages.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:876
+msgid "2023-07-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:878
+msgid "matrix-media-repo support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:880
+msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [matrix-media-repo](https://github.com/turt2live/matrix-media-repo) - an alternative way to store homeserver media files, powered by a homeserver-independent implementation which supports S3 storage, IPFS, deduplication and other advanced features."
+msgstr ""
+
+#: ../../../CHANGELOG.md:882
+msgid "To learn more see our [Storing Matrix media files using matrix-media-repo](docs/configuring-playbook-matrix-media-repo.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:885
+msgid "2023-05-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:887
+msgid "Enabling `forget_rooms_on_leave` by default for Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:889
+msgid "With the [Synapse v1.84.0 update](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2698), we've also **changed the default value** of the `forget_rooms_on_leave` setting of Synapse to a value of `true`. This way, **when you leave a room, Synapse will now forget it automatically**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:891
+msgid "The upstream Synapse default is `false` (disabled), so that you must forget rooms manually after leaving."
+msgstr ""
+
+#: ../../../CHANGELOG.md:893
+msgid "**We go against the upstream default** ([somewhat controversially](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2700)) in an effort to make Synapse leaner and potentially do what we believe most users would expect their homeserver to be doing."
+msgstr ""
+
+#: ../../../CHANGELOG.md:895
+msgid "If you'd like to go back to the old behavior, add the following to your configuration: `matrix_synapse_forget_rooms_on_leave: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:898
+msgid "2023-04-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:900
+msgid "The matrix-jitsi role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:902
+msgid "**TLDR**: the `matrix-jitsi` role is now included from the [ansible-role-jitsi](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi) repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:904
+msgid "The `matrix-jitsi` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project - an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Jitsi stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so."
+msgstr ""
+
+#: ../../../CHANGELOG.md:906
+msgid "As part of the extraction process of this role out of the Matrix playbook, a few other things improved:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:908
+msgid "**native Traefik support** has been added"
+msgstr ""
+
+#: ../../../CHANGELOG.md:909
+msgid "**support for hosting under a subpath** has been added, although it suffers from a few minor issues listed [here](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/jitsi.md#url)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:911
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Jitsi or not."
+msgstr ""
+
+#: ../../../CHANGELOG.md:913
+msgid "If you're making use of Jitsi via this playbook, you will need to update variable references in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:915
+msgid "`matrix_jitsi_*_docker_image_` -> `matrix_jitsi_*_container_image_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:916
+msgid "`matrix_jitsi_` -> `jitsi_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:917 ../../../CHANGELOG.md:944
+msgid "some other internal variables have changed, but the playbook will tell you about them"
+msgstr ""
+
+#: ../../../CHANGELOG.md:919
+msgid "2023-03-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:921
+msgid "ntfy Web App is disabled by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:923
+msgid "ntfy provides a web app, which is now disabled by default, because it may be unknown to and unused by most users of this playbook. You can enable it by setting `ntfy_web_root: \"app\"` (see [ntfy documentation](docs/configuring-playbook-ntfy.md))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:925
+msgid "This change was already applied a while before this entry, but as some users were reporting the missing web app, this entry was added (see [#2529](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2529))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:928
+msgid "2023-03-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:930
+msgid "The matrix-prometheus role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:932
+msgid "**TLDR**: the `matrix-prometheus` role is now included from the [ansible-role-prometheus](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus) repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:934
+msgid "The `matrix-prometheus` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project - an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Prometheus stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so."
+msgstr ""
+
+#: ../../../CHANGELOG.md:936
+msgid "Extracting the Prometheus role out of this Matrix playbook required huge internal refactoring to the way the Prometheus configuration (scraping jobs) is generated. If you notice any breakage after upgrading, let us know."
+msgstr ""
+
+#: ../../../CHANGELOG.md:938
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Prometheus or not."
+msgstr ""
+
+#: ../../../CHANGELOG.md:940
+msgid "If you're making use of Prometheus via this playbook, you will need to update variable references in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:942
+msgid "`matrix_prometheus_docker_image_` -> `matrix_prometheus_container_image_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:943
+msgid "`matrix_prometheus_` -> `prometheus_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:947
+msgid "2023-03-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:949
+msgid "synapse-auto-compressor support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:951
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state)'s `synapse_auto_compressor` tool to run periodically."
+msgstr ""
+
+#: ../../../CHANGELOG.md:953
+msgid "If enabled, `synapse_auto_compressor` runs on a schedule and compresses your Synapse database's `state_groups` table. It was possible to run `rust-synapse-compress-state` manually via the playbook even before - see [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state). However, using `synapse_auto_compressor` is better, because:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:955
+msgid "it runs on a more up-to-date version of `rust-synapse-compress-state`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:956
+msgid "it's a set-it-and-forget-it tool that you can enable and never have to deal with manual compression anymore"
+msgstr ""
+
+#: ../../../CHANGELOG.md:958
+msgid "This tool needs to be enabled manually, for now. In the future, we're considering enabling it by default for all Synapse installations."
+msgstr ""
+
+#: ../../../CHANGELOG.md:960
+msgid "See our [Setting up synapse-auto-compressor](docs/configuring-playbook-synapse-auto-compressor.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:963
+msgid "2023-03-07"
+msgstr ""
+
+#: ../../../CHANGELOG.md:965
+msgid "Sliding Sync proxy (Element X) support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:967
+msgid "Thanks to [Benjamin Kampmann](https://github.com/gnunicorn) for [getting it started](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2515), [FSG-Cat](https://github.com/FSG-Cat) for fixing it up and me ([Slavi](https://github.com/spantaleev)) for polishing it up, the playbook can now install and configure the [sliding-sync proxy](https://github.com/matrix-org/sliding-sync)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:969
+msgid "The upcoming Element X clients ([Element X iOS](https://github.com/vector-im/element-x-ios) and [Element X Android](https://github.com/vector-im/element-x-android)) require the `sliding-sync` proxy to do their job. **These clients are still in beta** (especially Element X Android, which requires manual compilation to get it working with a non-`matrix.org` homeseserver). Playbook users can now easily give these clients a try and help test them thanks to us having `sliding-sync` support."
+msgstr ""
+
+#: ../../../CHANGELOG.md:971
+msgid "To get started, see our [Setting up the Sliding Sync proxy](docs/configuring-playbook-sliding-sync-proxy.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:974
+msgid "2023-03-02"
+msgstr ""
+
+#: ../../../CHANGELOG.md:976
+msgid "The matrix-etherpad role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:978
+msgid "**TLDR**: the `matrix-etherpad` role is now included from [another repository](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:980
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Etherpad or not."
+msgstr ""
+
+#: ../../../CHANGELOG.md:982
+msgid "If you're making use of Etherpad via this playbook, you will need to update variable references in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:984
+msgid "Rename `matrix_etherpad_public_endpoint` to `etherpad_path_prefix`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:986
+msgid "Replace `matrix_etherpad_mode: dimension` with:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:987
+msgid "for `matrix-nginx-proxy` users:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:988
+msgid "`etherpad_nginx_proxy_dimension_integration_enabled: true`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:989
+msgid "`etherpad_hostname: \"{{ matrix_server_fqn_dimension }}\"`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:990
+msgid "for Traefik users:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:991
+msgid "define your own `etherpad_hostname` and `etherpad_path_prefix` as you see fit"
+msgstr ""
+
+#: ../../../CHANGELOG.md:993
+msgid "Rename all other variables:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:994
+msgid "`matrix_etherpad_docker_image_` -> `matrix_etherpad_container_image_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:995
+msgid "`matrix_etherpad_` -> `etherpad_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:997
+msgid "Along with this relocation, the new role also:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:999
+msgid "supports [self-building](docs/self-building.md), so it should work on `arm32` and `arm64` architectures"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1000
+msgid "has native Traefik reverse-proxy support (Etherpad requests no longer go through `matrix-nginx-proxy` when using Traefik)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1003
+msgid "2023-02-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1005
+msgid "Traefik is the default reverse-proxy now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1007
+msgid "**TLDR**: new installations will now default to Traefik as their reverse-proxy. Existing users need to explicitly choose their reverse-proxy type. [Switching to Traefik](#how-do-i-switch-my-existing-setup-to-traefik) is strongly encouraged. `matrix-nginx-proxy` may break over time and will ultimately be removed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1009
+msgid "As mentioned 2 weeks ago in [(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support](#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support), the playbook is moving to Traefik as its default SSL-terminating reverse-proxy."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1011
+msgid "Until now, we've been doing the migration gradually and keeping full backward compatibility. New installations were defaulting to `matrix-nginx-proxy` (just like before), while existing installations were allowed to remain on `matrix-nginx-proxy` as well. This makes things very difficult for us, because we need to maintain and think about lots of different setups:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1013
+msgid "Traefik managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1014
+msgid "Traefik managed by the user in another way"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1015
+msgid "another reverse-proxy on the same host (`127.0.0.1` port exposure)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1016
+msgid "another reverse-proxy on another host (`0.0.0.0` port exposure)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1017
+msgid "`matrix-nginx-proxy` - an `nginx` container managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1018
+msgid "`nginx` webserver operated by the user, running without a container on the same server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1020
+msgid "Each change we do and each new feature that comes in needs to support all these different ways of reverse-proxying. Because `matrix-nginx-proxy` was the default and pretty much everyone was (and still is) using it, means that new PRs also come with `matrix-nginx-proxy` as their main focus and Traefik as an afterthought, which means we need to spend hours fixing up Traefik support."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1022
+msgid "We can't spend all this time maintaining so many different configurations anymore. Traefik support has been an option for 2 weeks and lots of people have already migrated their server and have tested things out. Traefik is what we use and preferentially test for."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1024
+msgid "It's time for the **next step in our migration process** to Traefik and elimination of `matrix-nginx-proxy`:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1026
+msgid "Traefik is now the default reverse-proxy for new installations"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1027
+msgid "All existing users need to explicitly choose their reverse-proxy type by defining the `matrix_playbook_reverse_proxy_type` variable in their `vars.yml` configuration file. We strongly encourage existing users to [switch the Traefik](#how-to-switch-an-existing-setup-to-traefik), as the nginx setup is bound to become more and more broken over time until it's ultimately removed"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1029
+msgid "How do I switch my existing setup to Traefik?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1031
+msgid "**For users who are on `matrix-nginx-proxy`** (the default reverse-proxy provided by the playbook), switching to Traefik can happen with a simple configuration change. Follow this section from 2 weeks ago: [How do I explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-traefik-right-now)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1033
+msgid "If you experience trouble:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1035
+msgid "Follow [How do I remain on matrix-nginx-proxy?](#how-do-i-remain-on-matrix-nginx-proxy) to bring your server back online using the old reverse-proxy"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1036
+msgid "Ask for help in our [support channels](README.md#support)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1037
+msgid "Try switching to Traefik again later"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1039
+msgid "**For users with a more special reverse-proxying setup** (another nginx server, Apache, Caddy, etc.), the migration may not be so smooth. Follow the [Using your own webserver](docs/configuring-playbook-own-webserver.md) guide. Ideally, your custom reverse-proxy will be configured in such a way that it **fronts the Traefik reverse-proxy** provided by the playbook. Other means of reverse-proxying are more fragile and may be deprecated in the future."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1041
+msgid "I already use my own Traefik server. How do I plug that in?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1043
+msgid "See the [Traefik managed by the playbook](docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) section."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1045
+msgid "Why is matrix-nginx-proxy used even after switching to Traefik?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1047
+msgid "This playbook manages many different services. All these services were initially integrated with `matrix-nginx-proxy`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1049
+msgid "While we migrate all these components to have native Traefik support, some still go through nginx internally (Traefik -> local `matrix-nginx-proxy` -> component). As time goes on, internal reliance on `matrix-nginx-proxy` will gradually decrease until it's completely removed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1051
+msgid "How do I remain on matrix-nginx-proxy?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1053
+msgid "Most new work and testing targets Traefik, so remaining on nginx is **not** \"the good old stable\" option, but rather the \"still available, but largely untested and likely to be broken very soon\" option."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1055
+msgid "To proceed regardless of this warning, add `matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1057
+msgid "At some point in the **near** future (days, or even weeks at most), we hope to completely get rid of `matrix-nginx-proxy` (or break it enough to make it unusable), so you **will soon be forced to migrate** anyway. Plan your migration accordingly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1059
+msgid "How do I keep using my own other reverse-proxy?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1061
+msgid "We recommend that you follow the guide for [Fronting the integrated reverse-proxy webserver with another reverse-proxy](docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1064
+msgid "2023-02-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1066
+msgid "rageshake support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1068
+msgid "Thanks to [Benjamin Kampmann](https://github.com/gnunicorn), the playbook can now install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1070
+msgid "Additional details are available in [Setting up rageshake](docs/configuring-playbook-rageshake.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1073
+msgid "2023-02-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1075
+msgid "Synapse templates customization support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1077
+msgid "The playbook can now help you customize Synapse's templates."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1079
+msgid "Additional details are available in the [Customizing templates](docs/configuring-playbook-synapse.md#customizing-templates) section of our Synapse documentation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1081
+msgid "The matrix-redis role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1083
+msgid "**TLDR**: the `matrix-redis` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1085
+msgid "The `matrix-redis` role (which configures [Redis](https://redis.io/)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-redis). This makes it possible to easily use it in other Ansible playbooks."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1087
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Ntfy or not. If you're making use of Ntfy via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_redis_` -> `redis_`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1089
+msgid "The matrix-ntfy role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1091
+msgid "**TLDR**: the `matrix-ntfy` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1093
+msgid "The `matrix-ntfy` role (which configures [Ntfy](https://ntfy.sh/)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy). This makes it possible to easily use it in other Ansible playbooks."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1095
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Ntfy or not. If you're making use of Ntfy via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_ntfy_` -> `ntfy_`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1098
+msgid "2023-02-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1100
+msgid "The matrix-grafana role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1102
+msgid "**TLDR**: the `matrix-grafana` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1104
+msgid "The `matrix-grafana` role (which configures [Grafana](docs/configuring-playbook-prometheus-grafana.md)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-grafana). This makes it possible to easily use it in other Ansible playbooks."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1106
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Grafana or not. If you're making use of Grafana via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_grafana_` -> `grafana_`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1109
+msgid "2023-02-13"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1111
+msgid "The matrix-backup-borg role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1113
+msgid "**TLDR**: the `matrix-backup-borg` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1115
+msgid "Thanks to [moan0s](https://github.com/moan0s), the `matrix-backup-borg` role (which configures [BorgBackup](docs/configuring-playbook-backup-borg.md)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). This makes it possible to easily use it in other Ansible playbooks and will become part of [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) soon."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1117
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Borg's backup functionality or not. If you're making use of BorgBackup via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_backup_borg_` -> `backup_borg_`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1120
+msgid "2023-02-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1122
+msgid "(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1124
+msgid "**TLDR**:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1126
+msgid "there's a new `matrix_playbook_reverse_proxy_type` variable (see [roles/custom/matrix-base/defaults/main.yml](roles/custom/matrix-base/defaults/main.yml)), which lets you tell the playbook what reverse-proxy setup you'd like to have. This makes it easier for people who want to do reverse-proxying in other ways."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1127
+msgid "the default reverse-proxy (`matrix_playbook_reverse_proxy_type`) is still `playbook-managed-nginx` (via `matrix-nginx-proxy`), for now. **Existing `matrix-nginx-proxy` users should not observe any changes** and can stay on this for now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1128
+msgid "**Users who use their [own other webserver](docs/configuring-playbook-own-webserver.md) (e.g. Apache, etc.) need to change** `matrix_playbook_reverse_proxy_type` to something like `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1129
+msgid "we now have **optional [Traefik](https://traefik.io/) support**, so you could easily host Matrix and other Traefik-native services in containers on the same server. Traefik support is still experimental (albeit, good enough) and will improve over time. It does work, but certain esoteric features may not be there yet."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1130
+msgid "**Traefik will become the default reverse-proxy in the near future**. `matrix-nginx-proxy` will either remain as an option, or be completely removed to simplify the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1132
+msgid "Motivation for redoing our reverse-proxy setup"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1134
+msgid "The playbook has supported various reverse-proxy setups for a long time. We have various configuration variables (`matrix_nginx_proxy_enabled`, various `_host_bind_port` variables, etc.) which allow the playbook to adapt to these different setups. The whole situation was messy though - hard to figure out and with lots of variables to toggle to make things work as you'd expect - huge **operational complexity**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1136
+msgid "We love containers, proven by the fact that **everything** that this playbook manages runs in a container. Yet, we weren't allowing people to easily host other web-exposed containers alongside Matrix services on the same server. We were using `matrix-nginx-proxy` (our integrated [nginx](https://nginx.org/) server), which was handling web-exposure and SSL termination for our own services, but we **weren't helping you with all your other containers**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1138
+msgid "People who were **using `matrix-nginx-proxy`** were on the happy path on which everything worked well by default (Matrix-wise), **but** could not easily run other web-exposed services on their Matrix server because `matrix-nginx-proxy` was occupying ports `80` and `443`. Other services which wanted to get web exposure either had to be plugged into `matrix-nginx-proxy` (somewhat difficult) or people had to forgo using `matrix-nginx-proxy` in favor of something else."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1140
+msgid "Of those that decided to forgo `matrix-nginx-proxy`, many were **using nginx** on the same server without a container. This was likely some ancient nginx version, depending on your choice of distro. The Matrix playbook was trying to be helpful and even with `matrix_nginx_proxy_enabled: false` was still generating nginx configuration in `/matrix/nginx-proxy/conf.d`. Those configuration files were adapted for inclusion into an nginx server running locally. Disabling the `matrix-nginx-proxy` role like this, yet still having it produce files is a bit disgusting, but it's what we've had since the early beginnings of this playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1142
+msgid "Others still, wanted to run Matrix locally (no SSL certificates), regardless of which web server technology this relied on, and then **reverse-proxy from another machine on the network** which was doing SSL termination. These people were:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1144
+msgid "*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined with exposing services manually (setting `_bind_port` variables)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1145
+msgid "*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in `http`-only mode (no SSL certificate retrieval)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1147
+msgid "Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1149
+msgid "When using `matrix-nginx-proxy` as is, we still had another problem - one of **internal playbook complexity**. Too many services need to be web-exposed (port 80/443, SSL certificates). Because of this, they all had to integrate with the `matrix-nginx-proxy` role. Tens of different roles explicitly integrating with `matrix-nginx-proxy` is not what we call clean. The `matrix-nginx-proxy` role contains variables for many of these roles (yikes). Other roles were more decoupled from it and were injecting configuration into `matrix-nginx-proxy` at runtime - see all the `inject_into_nginx_proxy.yml` task files in this playbook (more decoupled, but still.. yikes)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1151
+msgid "The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1153
+msgid "[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy) for hosting the [Vaultwarden](https://github.com/dani-garcia/vaultwarden) server - an alternative implementation of the [Bitwarden](https://bitwarden.com/) password manager"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1154
+msgid "[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) - for hosting the [Gitea](https://gitea.io/) git source code hosting service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1155
+msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) - for hosting the [Nextcloud](https://nextcloud.com/) groupware platform"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1157
+msgid "We'd love for users to be able to **seamlessly use all these playbooks (and others, even) against a single server**. We don't want `matrix-nginx-proxy` to have a monopoly on port `80`/`443` and make it hard for other services to join in on the party. Such a thing forces people into running multiple servers (one for each service), which does provide nice security benefits, but is costly and ineffiecient. We'd like to make self-hosting these services cheap and easy."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1159
+msgid "These other playbooks have been using [Traefik](https://traefik.io/) as their default reverse-proxy for a long time. They can all coexist nicely together (as an example, see the [Interoperability](https://github.com/spantaleev/nextcloud-docker-ansible-deploy/blob/master/docs/configuring-playbook-interoperability.md) documentation for the [Nextcloud playbook](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)). Now that this playbook is gaining Traefik support, it will be able to interoperate with them. If you're going this way, make sure to have the Matrix playbook install Traefik and have the others use `*_reverse_proxy_type: other-traefik-container`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1161
+msgid "Finally, at [etke.cc - a managed Matrix server hosting service](https://etke.cc) (built on top of this playbook, and coincidentally [turning 2 years old today](https://etke.cc/news/upsyw4ykbtgmwhz8k7ukldx0zbbfq-fh0iqi3llixi0/) 🎉), we're allowing people to host some additional services besides Matrix components. Exposing these services to the web requires ugly hacks and configuration files being dropped into `/matrix/nginx-proxy/conf.d`. We believe that everything should run in independent containers and be exposed to the web via a Traefik server, without a huge Ansible role like `matrix-nginx-proxy` that everything else needs to integrate with."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1163
+msgid "How do these changes fix all these problems?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1165
+msgid "The new `matrix_playbook_reverse_proxy_type` lets you easily specify your preferred reverse-proxy type, including `other-on-same-host`, `other-on-another-host` and `none`, so people who'd like to reverse-proxy with their own web server have more options now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1167
+msgid "Using Traefik greatly simplifies things, so going forward we'll have a simpler and easier to maintain playbook, which is also interoperable with other services."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1169
+msgid "Traefik is a web server, which has been specifically **designed for reverse-proxying to services running in containers**. It's ideal for usage in an Ansible playbook which runs everything in containers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1171
+msgid "**Traefik obtains SSL certificates automatically**, so there's no need for plugging additional tools like [Certbot](https://certbot.eff.org/) into your web server (like we were doing in the `matrix-nginx-proxy` role). No more certificate renewal timers, web server reloading timers, etc. It's just simpler."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1173
+msgid "Traefik is a **modern web server**. [HTTP/3](https://doc.traefik.io/traefik/routing/entrypoints/#http3) is supported already (experimentally) and will move to stable soon, in the upcoming Traefik v3 release."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1175
+msgid "Traefik does not lock important functionality we'd like to use into [plus packages like nginx does](https://www.nginx.com/products/nginx/), leading us to resolve to configuration workarounds. The default Traefik package is good enough as it is."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1177
+msgid "Where we're at right now?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1179
+msgid "`matrix_playbook_reverse_proxy_type` still defaults to a value of `playbook-managed-nginx`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1181
+msgid "Unless we have some regression, **existing `matrix-nginx-proxy` users should be able to update their Matrix server and not observe any changes**. Their setup should still remain on nginx and everything should still work as expected."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1183
+msgid "**Users using [their own webservers](docs/configuring-playbook-own-webserver.md) will need to change `matrix_playbook_reverse_proxy_type`** to something like `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`. Previously, they could toggle `matrix_nginx_proxy_enabled` to `false`, and that made the playbook automatically expose services locally. Currently, we only do this if you change the reverse-proxy type to `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1185
+msgid "How do I explicitly switch to Traefik right now?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1187
+msgid "**Users who wish to migrate to Traefik** today, can do so by **adding** this to their configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1195
+msgid "You may still need to keep certain old `matrix_nginx_proxy_*` variables (like `matrix_nginx_proxy_base_domain_serving_enabled`), even when using Traefik. For now, we recommend keeping all `matrix_nginx_proxy_*` variables just in case. In the future, reliance on `matrix-nginx-proxy` will be removed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1197
+msgid "Switching to Traefik will obtain new SSL certificates from Let's Encrypt (stored in `/matrix/traefik/ssl/acme.json`). **The switch is reversible**. You can always go back to `playbook-managed-nginx` if Traefik is causing you trouble."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1199
+msgid "**Note**: toggling `matrix_playbook_reverse_proxy_type` between Traefik and nginx will uninstall the Traefik role and all of its data (under `/matrix/traefik`), so you may run into a Let's Encrypt rate limit if you do it often."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1201
+msgid "Treafik directly reverse-proxies to **some** services right now, but for most other services it goes through `matrix-nginx-proxy` (e.g. Traefik -> `matrix-nginx-proxy` -> [Ntfy](docs/configuring-playbook-ntfy.md)). So, even if you opt into Traefik, you'll still see `matrix-nginx-proxy` being installed in local-only mode. This will improve with time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1203
+msgid "Some services (like [Coturn](docs/configuring-playbook-turn.md) and [Postmoogle](docs/configuring-playbook-bridge-postmoogle.md)) cannot be reverse-proxied to directly from Traefik, so they require direct access to SSL certificate files extracted out of Traefik. The playbook does this automatically thanks to a new [com.devture.ansible.role.traefik_certs_dumper](https://github.com/devture/com.devture.ansible.role.traefik_certs_dumper) role utilizing the [traefik-certs-dumper](https://github.com/ldez/traefik-certs-dumper) tool."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1205
+msgid "Our Traefik setup mostly works, but certain esoteric features may not work. If you have a default setup, we expect you to have a good experience."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1207
+msgid "Where we're going in the near future?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1209
+msgid "The `matrix-nginx-proxy` role is quite messy. It manages both nginx and Certbot and its certificate renewal scripts and timers. It generates configuration even when the role is disabled (weird). Although it doesn't directly reach into variables from other roles, it has explicit awareness of various other services that it reverse-proxies to (`roles/custom/matrix-nginx-proxy/templates/nginx/conf.d/matrix-ntfy.conf.j2`, etc.). We'd like to clean this up. The only way is probably to just get rid of the whole thing at some point."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1211
+msgid "For now, `matrix-nginx-proxy` will stay around."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1213
+msgid "As mentioned above, Traefik still reverse-proxies to some (most) services by going through a local-only `matrix-nginx-proxy` server. This has allowed us to add Traefik support to the playbook early on (without having to rework all services), but is not the final goal. We'll **work on making each service support Traefik natively**, so that traffic will not need to go through `matrix-nginx-proxy` anymore. In the end, choosing Traefik should only give you a pure Traefik installation with no `matrix-nginx-proxy` in sight."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1215
+msgid "As Traefik support becomes complete and proves to be stable for a while, especially as a playbook default, we will **most likely remove `matrix-nginx-proxy` completely**. It will likely be some months before this happens though. Keeping support for both Traefik and nginx in the playbook will be a burden, especially with most of us running Traefik in the future. The Traefik role should do everything nginx does in a better and cleaner way. Users who use their own `nginx` server on the Matrix server will be inconvenienced, as nothing will generate ready-to-include nginx configuration for them. Still, we hope it won't be too hard to migrate their setup to another way of doing things, like:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1217
+msgid "not using nginx anymore. A common reason for using nginx until now was that you were running other containers and you need your own nginx to reverse-proxy to all of them. Just switch them to Traefik as well."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1218
+msgid "running Traefik in local-only mode (`traefik_config_entrypoint_web_secure_enabled: false`) and using some nginx configuration which reverse-proxies to Traefik (we should introduce examples for this in `examples/nginx`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1220
+msgid "How do I help?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1222
+msgid "You can help by:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1224
+msgid "**explicitly switching your server to Traefik** right now (see example configuration in [How do I explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-traefik-right-now) above), testing, reporting troubles"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1226
+msgid "**adding native Traefik support to a role** (requires adding Traefik labels, etc.) - for inspiration, see these roles ([prometheus_node_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter), [prometheus_postgres_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter)) and how they're hooked into the playbook via [group_vars/matrix_servers](group_vars/matrix_servers)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1228
+msgid "**adding reverse-proxying examples for nginx users** in `examples/nginx`. People who insist on using their own `nginx` server on the same Matrix host, can run Traefik in local-only mode (`traefik_config_entrypoint_web_secure_enabled: false`) and reverse-proxy to the Traefik server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1231
+msgid "2023-02-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1233
+msgid "Matrix Authentication Support for Jitsi"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1235
+msgid "Thanks to [Jakob S.](https://github.com/jakicoll) ([zakk gGmbH](https://github.com/zakk-it)), Jitsi can now use Matrix for authentication (via [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1237
+msgid "Additional details are available in the [Authenticate using Matrix OpenID (Auth-Type 'matrix')](docs/configuring-playbook-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1239
+msgid "Draupnir moderation tool (bot) support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1241
+msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (bot). Draupnir is a fork of [Mjolnir](docs/configuring-playbook-bot-mjolnir.md) (which the playbook has supported for a long time) maintained by Mjolnir's former lead developer."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1243
+msgid "Additional details are available in [Setting up Draupnir](docs/configuring-playbook-bot-draupnir.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1246
+msgid "2023-02-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1248
+msgid "The matrix-prometheus-postgres-exporter role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1250
+msgid "**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1252
+msgid "The `matrix-prometheus-postgres-exporter` role (which configures [Prometheus Postgres Exporter](https://github.com/prometheus-community/postgres_exporter)) has been extracted from the playbook and now lives in its own repository at https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1254
+msgid "It's still part of the playbook, but is now installed via `ansible-galaxy` (by running `just roles` / `make roles`). Some variables have been renamed (`matrix_prometheus_postgres_exporter_` -> `prometheus_postgres_exporter_`, etc.). The playbook will report all variables that you need to rename to get upgraded. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1256
+msgid "The `matrix-prometheus-services-proxy-connect` role has bee adjusted to help integrate the new `prometheus_postgres_exporter` role with our own services (`matrix-nginx-proxy`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1258 ../../../CHANGELOG.md:1300
+msgid "Other roles which aren't strictly related to Matrix are likely to follow this fate of moving to their own repositories. Extracting them out allows other Ansible playbooks to make use of these roles easily."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1261
+msgid "2023-01-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1263
+msgid "Coturn can now use host-networking"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1265
+msgid "Large Coturn deployments (with a huge range of ports specified via `matrix_coturn_turn_udp_min_port` and `matrix_coturn_turn_udp_max_port`) experience a huge slowdown with how Docker publishes all these ports (setting up firewall forwarding rules), which leads to a very slow Coturn service startup and shutdown."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1267
+msgid "Such deployments don't need to run Coturn within a private container network anymore. Coturn can now run with host-networking by using configuration like this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1273
+msgid "With such a configuration, **Docker no longer needs to configure thousands of firewall forwarding rules** each time Coturn starts and stops. This, however, means that **you will need to ensure these ports are open** in your firewall yourself."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1275
+msgid "Thanks to us [tightening Coturn security](#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues), running Coturn with host-networking should be safe and not expose neither other services running on the host, nor other services running on the local network."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1277
+msgid "(Backward Compatibility) Tightening Coturn security can lead to connectivity issues"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1279
+msgid "**TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default Coturn blocklists. They may need to override `matrix_coturn_denied_peer_ips` and remove some IP ranges from it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1281
+msgid "Inspired by [this security article](https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-access-control-protection/), we've decided to make use of Coturn's `denied-peer-ip` functionality to prevent relaying network traffic to certain private IP subnets. This ensures that your Coturn server won't accidentally try to forward traffic to certain services running on your local networks. We run Coturn in a container and in a private container network by default, which should prevent such access anyway, but having additional block layers in place is better."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1283
+msgid "If you access your Matrix server from a local network and need Coturn to relay to private IP addresses, you may observe that relaying is now blocked due to our new default `denied-peer-ip` lists (specified in `matrix_coturn_denied_peer_ips`). If you experience such connectivity problems, consider overriding this setting in your `vars.yml` file and removing certain networks from it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1285
+msgid "We've also added `no-multicast-peers` to the default Coturn configuration, but we don't expect this to cause trouble for most people."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1288
+msgid "2023-01-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1290
+msgid "The matrix-prometheus-node-exporter role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1292
+msgid "**TLDR**: the `matrix-prometheus-node-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1294
+msgid "The `matrix-prometheus-node-exporter` role (which configures [Prometheus node exporter](https://github.com/prometheus/node_exporter)) has been extracted from the playbook and now lives in its own repository at https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1296
+msgid "It's still part of the playbook, but is now installed via `ansible-galaxy` (by running `just roles` / `make roles`). Some variables have been renamed (`matrix_prometheus_node_exporter_` -> `prometheus_node_exporter_`, etc.). The playbook will report all variables that you need to rename to get upgraded. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1298
+msgid "A new `matrix-prometheus-services-proxy-connect` role was added to the playbook to help integrate the new `prometheus_node_exporter` role with our own services (`matrix-nginx-proxy`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1303
+msgid "2023-01-13"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1305
+msgid "Support for running commands via just"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1307
+msgid "We've previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers `ansible-galaxy`, see [Makefile](Makefile)). Our `Makefile` is still around and you can still run these commands."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1309
+msgid "In addition, we've added support for running commands via [just](https://github.com/casey/just) - a more modern command-runner alternative to `make`. Instead of `make roles`, you can now run `just roles` to accomplish the same."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1311
+msgid "Our [justfile](justfile) already defines some additional helpful **shortcut** commands that weren't part of our `Makefile`. Here are some examples:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1313
+msgid "`just install-all` to trigger the much longer `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start` command"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1314
+msgid "`just install-all --ask-vault-pass` - commands also support additional arguments (`--ask-vault-pass` will be appended to the above installation command)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1315
+msgid "`just run-tags install-mautrix-slack,start` - to run specific playbook tags"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1316
+msgid "`just start-all` - (re-)starts all services"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1317
+msgid "`just stop-group postgres` - to stop only the Postgres service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1318
+msgid "`just register-user alice secret-password yes` - registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1320
+msgid "Additional helpful commands and shortcuts may be defined in the future."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1322
+msgid "This is all completely optional. If you find it difficult to [install `just`](https://github.com/casey/just#installation) or don't find any of this convenient, feel free to run all commands manually."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1325
+msgid "2023-01-11"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1327
+msgid "mautrix-slack support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1329
+msgid "Thanks to [Cody Neiman](https://github.com/xangelix)'s efforts, the playbook now supports bridging to [Slack](https://slack.com/) via the [mautrix-slack](https://mau.dev/mautrix/slack) bridge. See our [Setting up Mautrix Slack bridging](docs/configuring-playbook-bridge-mautrix-slack.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1331
+msgid "**Note**: this is a new Slack bridge. The playbook still retains Slack bridging via [matrix-appservice-slack](docs/configuring-playbook-bridge-appservice-slack.md) and [mx-puppet-slack](docs/configuring-playbook-bridge-mx-puppet-slack.md). You're free to use the bridge that serves you better, or even all three of them (for different users and use-cases)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1334
+msgid "2023-01-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1336
+msgid "ChatGPT support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1338
+msgid "Thanks to [@bertybuttface](https://github.com/bertybuttface), the playbook can now help you set up [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) - a bot through which you can talk to the [ChatGPT](https://openai.com/blog/chatgpt/) model."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1340
+msgid "See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-chatgpt.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1343
+msgid "2022-11-30"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1345
+msgid "matrix-postgres-backup has been replaced by the ansible-role-postgres-backup external role"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1347
+msgid "Just like we've [replaced Postgres with an external role](#matrix-postgres-has-been-replaced-by-the-comdevtureansiblerolepostgres-external-role) on 2022-11-28, we're now replacing `matrix-postgres-backup` with an external role - [com.devture.ansible.role.postgres_backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres_backup)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1349
+msgid "You'll need to rename your `matrix_postgres_backup`-prefixed variables such that they use a `postgres_backup` prefix."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1352
+msgid "2022-11-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1354
+msgid "matrix-postgres has been replaced by the ansible-role-postgres external role"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1356
+msgid "**TLDR**: the tasks that install the integrated Postgres server now live in an external role - [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres). You'll need to run `make roles` to install it, and to also rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix (e.g. `matrix_postgres_connection_password` -> `postgres_connection_password`). All your data will still be there! Some scripts have moved (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1358
+msgid "The `matrix-postgres` role that has been part of the playbook for a long time has been replaced with the [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) role. This was done as part of our work to [use external roles for some things](#the-playbook-now-uses-external-roles-for-some-things) for better code re-use and maintainability."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1360
+msgid "The new role is an upgraded version of the old `matrix-postgres` role with these notable differences:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1362
+msgid "it uses different names for its variables (`matrix_postgres` -> `devture_postgres`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1363
+msgid "when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-postgresql), it will vacuum all your databases, not just the Synapse one"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1365
+msgid "You'll need to run `make roles` to install the new role. You would also need to rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1367
+msgid "Note: the systemd service still remains the same - `matrix-postgres.service`. Your data will still be in `/matrix/postgres`, etc. Postgres-related scripts will be moved to `/matrix/postgres/bin` (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`, etc). Also see [The playbook no longer installs scripts in /usr/local/bin](#the-playbook-no-longer-installs-scripts-in-usrlocalbin)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1369
+msgid "The playbook no longer installs scripts to /usr/local/bin"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1371
+msgid "The locations of various scripts installed by the playbook have changed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1373
+msgid "The playbook no longer contaminates your `/usr/local/bin` directory. All scripts installed by the playbook now live in `bin/` directories under `/matrix`. Some examples are below:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1375
+msgid "`/usr/local/bin/matrix-remove-all` -> `/matrix/bin/remove-all`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1376
+msgid "`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1377
+msgid "`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> `/matrix/ssl/bin/lets-encrypt-certificates-renew`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1378
+msgid "`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin/register-user`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1381
+msgid "2022-11-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1383
+msgid "2x-5x performance improvements in playbook runtime"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1385
+msgid "**TLDR**: the playbook is 2x faster for running `--tags=setup-all` (and various other tags). It also has new `--tags=install-*` tags (like `--tags=install-all`), which skip uninstallation tasks and bring an additional 2.5x speedup. In total, the playbook can maintain your server 5 times faster."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1387
+msgid "Our [etke.cc managed Matrix hosting service](https://etke.cc) runs maintenance against hundreds of servers, so the playbook being fast means a lot. The [etke.cc Ansible playbook](https://github.com/etkecc/ansible) (which is an extension of this one) is growing to support more and more services (besides just Matrix), so the Matrix playbook being leaner prevents runtimes from becoming too slow and improves the customer experience."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1389
+msgid "Even when running `ansible-playbook` manually (as most of us here do), it's beneficial not to waste time and CPU resources."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1391
+msgid "Recently, a few large optimizations have been done to this playbook and its external roles (see [The playbook now uses external roles for some things](#the-playbook-now-uses-external-roles-for-some-things) and don't forget to run `make roles`):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1393
+msgid "Replacing Ansible `import_tasks` calls with `include_tasks`, which decreased runtime in half. Using `import_tasks` is slower and causes Ansible to go through and skip way too many tasks (tasks which could have been skipped altogether by not having Ansible include them in the first place). On an experimental VM, **deployment time was decreased from ~530 seconds to ~250 seconds**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1395
+msgid "Introducing new `install-*` tags (`install-all` and `install-COMPONENT`, e.g. `install-synapse`, `install-bot-mjolnir`), which only run Ansible tasks pertaining to installation, while skipping uninstallation tasks. In most cases, people are maintaining the same setup or they're *adding* new components. Removing components is rare. Running thousands of uninstallation tasks each time is wasteful. On an experimental VM, **deployment time was decreased from ~250 seconds (`--tags=setup-all`) to ~100 seconds (`--tags=install-all`)**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1397
+msgid "You can still use `--tags=setup-all`. In fact, that's the best way to ensure your server is reconciled with the `vars.yml` configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1399
+msgid "If you know you haven't uninstalled any services since the last time you ran the playbook, you could run `--tags=install-all` instead and benefit from quicker runtimes. It should be noted that a service may become \"eligible for uninstallation\" even if your `vars.yml` file remains the same. In rare cases, we toggle services from being auto-installed to being optional, like we did on the 17th of March 2022 when we made [ma1sd not get installed by default](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/CHANGELOG.md#compatibility-break-ma1sd-identity-server-no-longer-installed-by-default). In such rare cases, you'd also need to run `--tags=setup-all`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1402
+msgid "2022-11-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1404
+msgid "Automatic `matrix_architecture` determination"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1406
+msgid "From now on, the playbook automatically determines your server's architecture and sets the `matrix_architecture` variable accordingly. You no longer need to set this variable manually in your `vars.yml` file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1408
+msgid "Docker and the Docker SDK for Python are now installed via external roles"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1412
+msgid "Docker will now be installed on the server via the [geerlingguy.docker](https://github.com/geerlingguy/ansible-role-docker) Ansible role. If you'd like to manage the Docker installation yourself, you can disable the playbook's installation of Docker by setting `matrix_playbook_docker_installation_enabled: false`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1414
+msgid "The Docker SDK for Python (named `docker-python`, `python-docker`, etc. on the different platforms) is now also installed by another role ([com.devture.ansible.role.docker_sdk_for_python](https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python)). To disable this role and install the necessary tools yourself, use `devture_docker_sdk_for_python_installation_enabled: false`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1416
+msgid "If you're hitting issues with Docker installation or Docker SDK for Python installation, consider reporting bugs or contributing to these other projects."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1418
+msgid "These additional roles are downloaded into the playbook directory (to `roles/galaxy`) via an `ansible-galaxy ..` command. `make roles` is an easy shortcut for invoking the `ansible-galaxy` command to download these roles."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1421
+msgid "2022-11-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1423
+msgid "(Backward Compatibility Break) Changing how reverse-proxying to Synapse works - now via a `matrix-synapse-reverse-proxy-companion` service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1425
+msgid "**TLDR**: There's now a `matrix-synapse-reverse-proxy-companion` nginx service, which helps with reverse-proxying to Synapse and its various worker processes (if workers are enabled), so that `matrix-nginx-proxy` can be relieved of this role. `matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. `matrix-synapse-reverse-proxy-companion` is just one more reverse-proxy thrown into the mix for convenience. People with a more custom reverse-proxying configuration may be affected - see [Webserver configuration](#webserver-configuration) below."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1427
+msgid "Background"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1429
+msgid "Previously, `matrix-nginx-proxy` forwarded requests to Synapse directly. When Synapse is running in worker mode, the reverse-proxying configuration is more complicated (different requests need to go to different Synapse worker processes). `matrix-nginx-proxy` had configuration for sending each URL endpoint to the correct Synapse worker responsible for handling it. However, sometimes people like to disable `matrix-nginx-proxy` (for whatever reason) as detailed in [Using your own webserver, instead of this playbook's nginx proxy](docs/configuring-playbook-own-webserver.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1431
+msgid "Because `matrix-nginx-proxy` was so central to request forwarding, when it was disabled and Synapse was running with workers enabled, there was nothing which could forward requests to the correct place anymore.. which caused [problems such as this one affecting Dimension](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2090)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1433
+msgid "Solution"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1435
+msgid "From now on, `matrix-nginx-proxy` is relieved of its function of reverse-proxying to Synapse and its various worker processes. This role is now handled by the new `matrix-synapse-reverse-proxy-companion` nginx service and works even if `matrix-nginx-proxy` is disabled. The purpose of the new `matrix-synapse-reverse-proxy-companion` service is to:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1437
+msgid "serve as a companion to Synapse and know how to reverse-proxy to Synapse correctly (no matter if workers are enabled or not)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1439
+msgid "provide a unified container address for reaching Synapse (no matter if workers are enabled or not)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1440
+msgid "`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server API traffic"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1441
+msgid "`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server (Federation) API traffic"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1443
+msgid "simplify `matrix-nginx-proxy` configuration - it now only needs to send requests to `matrix-synapse-reverse-proxy-companion` or `matrix-dendrite`, etc., without having to worry about workers"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1445
+msgid "allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is disabled"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1447
+msgid "`matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. All traffic goes through it before reaching any of the services. It's just that now the Synapse traffic is routed through `matrix-synapse-reverse-proxy-companion` like this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1449
+msgid "(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> (`matrix-synapse` or some Synapse worker))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1451
+msgid "Various services (like Dimension, etc.) still talk to Synapse via `matrix-nginx-proxy` (e.g. `http://matrix-nginx-proxy:12080`) preferentially. They only talk to Synapse via the reverse-proxy companion (e.g. `http://matrix-synapse-reverse-proxy-companion:8008`) if `matrix-nginx-proxy` is disabled. Services should not be talking to Synapse (e.g. `https://matrix-synapse:8008` directly anymore), because when workers are enabled, that's the Synapse `master` process and may not be serving all URL endpoints needed by the service."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1453
+msgid "Webserver configuration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1455
+msgid "if you're using `matrix-nginx-proxy` (`matrix_nginx_proxy_enabled: true`, which is the default for the playbook), you don't need to do anything"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1457
+msgid "if you're using your own `nginx` webserver running on the server, you shouldn't be affected. The `/matrix/nginx/conf.d` configuration and exposed ports that you're relying on will automatically be updated in a way that should work"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1459
+msgid "if you're using another local webserver (e.g. Apache, etc.) and haven't changed any ports (`matrix_*_host_bind_port` definitions), you shouldn't be affected. You're likely sending Matrix traffic to `127.0.0.1:8008` and `127.0.0.1:8048`. These ports (`8008` and `8048`) will still be exposed on `127.0.0.1` by default - just not by the `matrix-synapse` container from now on, but by the `matrix-synapse-reverse-proxy-companion` container instead"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1461
+msgid "if you've been exposing `matrix-synapse` ports (`matrix_synapse_container_client_api_host_bind_port`, etc.) manually, you should consider exposing `matrix-synapse-reverse-proxy-companion` ports instead"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1463
+msgid "if you're running Traefik and reverse-proxying directly to the `matrix-synapse` container, you should start reverse-proxying to the `matrix-synapse-reverse-proxy-companion` container instead. See [our updated Traefik example configuration](docs/configuring-playbook-own-webserver.md#sample-configuration-for-running-behind-traefik-20). Note: we now recommend calling the federation entry point `federation` (instead of `synapse`) and reverse-proxying the federation traffic via `matrix-nginx-proxy`, instead of sending it directly to Synapse (or `matrix-synapse-reverse-proxy-companion`). This makes the configuration simpler."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1466
+msgid "2022-11-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1468
+msgid "(Backward Compatibility Break) A new default standalone mode for Etherpad"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1470
+msgid "Until now, [Etherpad](https://etherpad.org/) (which [the playbook could install for you](docs/configuring-playbook-etherpad.md)) required the [Dimension integration manager](docs/configuring-playbook-dimension.md) to also be installed, because Etherpad was hosted on the Dimension domain (at `dimension.example.com/etherpad`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1472
+msgid "From now on, Etherpad can be installed in `standalone` mode on `etherpad.example.com` and used even without Dimension. This is much more versatile, so the playbook now defaults to this new mode (`etherpad_mode: standalone`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1474
+msgid "If you've already got both Etherpad and Dimension in use you could:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1476
+msgid "**either** keep hosting Etherpad under the Dimension domain by adding `etherpad_mode: dimension` to your `vars.yml` file. All your existing room widgets will continue working at the same URLs and no other changes will be necessary."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1478
+msgid "**or**, you could change to hosting Etherpad separately on `etherpad.example.com`. You will need to [configure a DNS record](docs/configuring-dns.md) for this new domain. You will also need to reconfigure Dimension to use the new pad URLs (`https://etherpad.example.com/…`) going forward (refer to our [configuring Etherpad documentation](docs/configuring-playbook-etherpad.md)). All your existing room widgets (which still use `https://dimension.example.com/etherpad/…`) will break as Etherpad is not hosted there anymore. You will need to re-add them or to consider not using `standalone` mode"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1481
+msgid "2022-11-04"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1483
+msgid "The playbook now uses external roles for some things"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1485
+msgid "**TLDR**: when updating the playbook and before running it, you'll need to run `make roles` to make [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) download dependency roles (see the [`requirements.yml` file](requirements.yml)) to the `roles/galaxy` directory. Without this, the playbook won't work."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1487
+msgid "We're in the process of trimming the playbook and making it reuse Ansible roles."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1489
+msgid "Starting now, the playbook is composed of 2 types of Ansible roles:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1491
+msgid "those that live within the playbook itself (`roles/custom/*`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1493
+msgid "those downloaded from other sources (using [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) to `roles/galaxy`, based on the [`requirements.yml` file](requirements.yml)). These roles are maintained by us or by other people from the Ansible community."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1495
+msgid "We're doing this for greater code-reuse (across Ansible playbooks, including our own related playbooks [gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) and [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)) and decreased maintenance burden. Until now, certain features were copy-pasted across playbooks or were maintained separately in each one, with improvements often falling behind. We've also tended to do too much by ourselves - installing Docker on the server from our `matrix-base` role, etc. - something that we'd rather not do anymore by switching to the [geerlingguy.docker](https://galaxy.ansible.com/geerlingguy/docker) role."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1497
+msgid "Some variable names will change during the transition to having more and more external (galaxy) roles. There's a new `custom/matrix_playbook_migration` role added to the playbook which will tell you about these changes each time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1499
+msgid "**From now on**, every time you update the playbook (well, every time the `requirements.yml` file changes), it's best to run `make roles` to update the roles downloaded from other sources. `make roles` is a shortcut (a `roles` target defined in [`Makefile`](Makefile) and executed by the [`make`](https://www.gnu.org/software/make/) utility) which ultimately runs [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) to download Ansible roles. If you don't have `make`, you can also manually run the commands seen in the `Makefile`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1502
+msgid "2022-10-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1504
+msgid "synapse-s3-storage-provider support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1506
+msgid "**`synapse-s3-storage-provider` support is very new and still relatively untested. Using it may cause data loss.**"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1508
+msgid "You can now store your Synapse media repository files on Amazon S3 (or another S3-compatible object store) using [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) - a media provider for Synapse (Python module), which should work faster and more reliably than our previous [Goofys](docs/configuring-playbook-s3-goofys.md) implementation (Goofys will continue to work)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1510
+msgid "This is not just for initial installations. Users with existing files (stored in the local filesystem) can also migrate their files to `synapse-s3-storage-provider`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1512
+msgid "To get started, see our [Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3-storage-provider.md) documentation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1514
+msgid "Synapse container image customization support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1516
+msgid "We now support customizing the Synapse container image by adding additional build steps to its [`Dockerfile`](https://docs.docker.com/engine/reference/builder/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1518
+msgid "Our [synapse-s3-storage-provider support](#synapse-s3-storage-provider-support) is actually built on this. When `s3-storage-provider` is enabled, we automatically add additional build steps to install its Python module into the Synapse image."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1520
+msgid "Besides this kind of auto-added build steps (for components supported by the playbook), we also let you inject your own custom build steps using configuration like this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1531
+msgid "People who have needed to customize Synapse previously had to fork the git repository, make their changes to the `Dockerfile` there, point the playbook to the new repository (`matrix_synapse_container_image_self_build_repo`) and enable self-building from scratch (`matrix_synapse_container_image_self_build: true`). This is harder and slower."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1533
+msgid "With the new Synapse-customization feature in the playbook, we use the original upstream (pre-built, if available) Synapse image and only build on top of it, right on the Matrix server. This is much faster than building all of Synapse from scratch."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1536
+msgid "2022-10-02"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1538
+msgid "matrix-ldap-registration-proxy support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1540
+msgid "Thanks to [@TheOneWithTheBraid](https://github.com/TheOneWithTheBraid), we now support installing [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) - a proxy which handles Matrix registration requests and forwards them to LDAP."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1542
+msgid "See our [Setting up matrix-ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1545
+msgid "2022-09-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1547
+msgid "(Potential Backward Compatibility Break) Major improvements to Synapse workers"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1549
+msgid "People who are interested in running a Synapse worker setup should know that **our Synapse worker implementation is much more powerful now**:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1551
+msgid "we've added support for [Stream writers](#stream-writers-support)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1552
+msgid "we've added support for [multiple federation sender workers](#multiple-federation-sender-workers-support)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1553
+msgid "we've added support for [multiple pusher workers](#multiple-pusher-workers-support)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1554
+msgid "we've added support for [running background tasks on a worker](#background-tasks-can-run-on-a-worker)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1555
+msgid "we've restored support for [`appservice` workers](#appservice-worker-support-is-back)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1556
+msgid "we've restored support for [`user_dir` workers](#user-directory-worker-support-is-back)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1557
+msgid "we've made it possible to [reliably use more than 1 `media_repository` worker](#using-more-than-1-media-repository-worker-is-now-more-reliable)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1558
+msgid "see the [Potential Backward Incompatibilities after these Synapse worker changes](#potential-backward-incompatibilities-after-these-synapse-worker-changes)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1560
+msgid "Stream writers support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1562
+msgid "From now on, the playbook lets you easily set up various [stream writer workers](https://matrix-org.github.io/synapse/latest/workers.html#stream-writers) which can handle different streams (`events` stream; `typing` URL endpoints, `to_device` URL endpoints, `account_data` URL endpoints, `receipts` URL endpoints, `presence` URL endpoints). All of this work was previously handled by the main Synapse process, but can now be offloaded to stream writer worker processes."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1564
+msgid "If you're using `matrix_synapse_workers_preset: one-of-each`, you'll automatically get 6 additional workers (one for each of the above stream types). Our `little-federation-helper` preset (meant to be quite minimal and focusing in improved federation performance) does not include stream writer workers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1566
+msgid "If you'd like to customize the number of workers we also make that possible using these variables:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1579
+msgid "Multiple federation sender workers support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1581
+msgid "Until now, we only supported a single `federation_sender` worker (`matrix_synapse_workers_federation_sender_workers_count` could either be `0` or `1`). From now on, you can have as many as you want to help with your federation traffic."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1583
+msgid "Multiple pusher workers support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1585
+msgid "Until now, we only supported a single `pusher` worker (`matrix_synapse_workers_pusher_workers_count` could either be `0` or `1`). From now on, you can have as many as you want to help with pushing notifications out."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1587
+msgid "Background tasks can run on a worker"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1589
+msgid "From now on, you can put [background task processing on a worker](https://matrix-org.github.io/synapse/latest/workers.html#background-tasks)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1591
+msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `background` worker automatically. You can also control the `background` workers count with `matrix_synapse_workers_background_workers_count`. Only  `0` or `1` workers of this type are supported by Synapse."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1593
+msgid "Appservice worker support is back"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1595
+msgid "We previously had an `appservice` worker type, which [Synapse deprecated in v1.59.0](https://github.com/element-hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-synapseappappservice-and-synapseappuser_dir-worker-application-types). So did we, at the time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1597
+msgid "The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of talking to Application Services. From now on, we have support for this."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1599
+msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `appservice` worker automatically. You can also control the `appservice` workers count with `matrix_synapse_workers_appservice_workers_count`. Only  `0` or `1` workers of this type are supported by Synapse."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1601
+msgid "User Directory worker support is back"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1603
+msgid "We previously had a `user_dir` worker type, which [Synapse deprecated in v1.59.0](https://github.com/element-hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-synapseappappservice-and-synapseappuser_dir-worker-application-types). So did we, at the time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1605
+msgid "The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of serving the user directory. From now on, we have support for this."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1607
+msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `user_dir` worker automatically. You can also control the `user_dir` workers count with `matrix_synapse_workers_user_dir_workers_count`. Only  `0` or `1` workers of this type are supported by Synapse."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1609
+msgid "Using more than 1 media repository worker is now more reliable"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1611
+msgid "With `matrix_synapse_workers_preset: one-of-each`, we only launch one `media_repository` worker."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1613
+msgid "If you've been configuring `matrix_synapse_workers_media_repository_workers_count` manually, you may have increased that to more workers. When multiple media repository workers are in use, background tasks related to the media repository must always be configured to run on a single `media_repository` worker via `media_instance_running_background_jobs`. Until now, we weren't doing this correctly, but we now are."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1615
+msgid "Potential Backward Incompatibilities after these Synapse worker changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1617
+msgid "Below we'll discuss **potential backward incompatibilities**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1619
+msgid "**Worker names** (container names, systemd services, worker configuration files) **have changed**. Workers are now labeled sequentially (e.g. `matrix-synapse-worker_generic_worker-18111` -> `matrix-synapse-worker-generic-0`). The playbook will handle these changes automatically."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1621
+msgid "Due to increased worker types support above, people who use `matrix_synapse_workers_preset: one-of-each` should be aware that with these changes, **the playbook will deploy 9 additional workers** (6 stream writers, 1 `appservice` worker, 1 `user_dir` worker, 1 background task worker). This **may increase RAM/CPU usage**, etc. If you find your server struggling, consider disabling some workers with the appropriate `matrix_synapse_workers_*_workers_count` variables."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1623
+msgid "**Metric endpoints have also changed** (`/metrics/synapse/worker/generic_worker-18111` -> `/metrics/synapse/worker/generic-worker-0`). If you're [collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server), consider revisiting our [Collecting Synapse worker metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-server) docs and updating your Prometheus configuration. **If you're collecting metrics to the integrated Prometheus server** (not enabled by default), **your Prometheus configuration will be updated automatically**. Old data (from before this change) may stick around though."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1625
+msgid "**the format of `matrix_synapse_workers_enabled_list` has changed**. You were never advised to use this variable for directly creating workers (we advise people to control workers using `matrix_synapse_workers_preset` or by tweaking `matrix_synapse_workers_*_workers_count` variables only), but some people may have started using the `matrix_synapse_workers_enabled_list` variable to gain more control over workers. If you're one of them, you'll need to adjust its value. See `roles/custom/matrix-synapse/defaults/main.yml` for more information on the new format. The playbook will also do basic validation and complain if you got something wrong."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1628
+msgid "2022-09-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1630
+msgid "Cactus Comments support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1632
+msgid "Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now set up [Cactus Comments](https://cactus.chat) - federated comment system for the web based on Matrix."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1634
+msgid "See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-comments.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1637
+msgid "2022-08-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1639
+msgid "Postmoogle email bridge support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1641
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the new [Postmoogle](https://github.com/etkecc/postmoogle) email bridge. Postmoogle is like the [email2matrix bridge](https://github.com/devture/email2matrix) (also [already supported by the playbook](docs/configuring-playbook-email2matrix.md)), but more capable and with the intention to soon support *sending* emails, not just receiving."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1643
+msgid "See our [Setting up Postmoogle email bridging](docs/configuring-playbook-bridge-postmoogle.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1646
+msgid "2022-08-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1648
+msgid "mautrix-whatsapp default configuration changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1650
+msgid "In [Pull Request #2012](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2012), we've made some changes to the default configuration used by the `mautrix-whatsapp` bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1652
+msgid "If you're using this bridge, you should look into this PR and see if the new configuration suits you. If not, you can always change individual preferences in your `vars.yml` file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1654
+msgid "Most notably, spaces support has been enabled by default. The bridge will now group rooms into a Matrix space. **If you've already bridged to Whatsapp** prior to this update, you will need to send `!wa sync space` to the bridge bot to make it create the space and put your existing rooms into it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1657
+msgid "2022-08-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1659
+msgid "Conduit support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1661
+msgid "Thanks to [Charles Wright](https://github.com/cvwright), we now have optional experimental [Conduit](https://conduit.rs) homeserver support for new installations. This comes as a follow-up to the playbook getting [Dendrite support](#dendrite-support) earlier this year."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1663
+msgid "Existing Synapse or Dendrite installations do **not** need to be updated. **Synapse is still the default homeserver implementation** installed by the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1665
+msgid "To try out Conduit, we recommend that you **use a new server** and the following `vars.yml` configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1671
+msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse or Dendrite to Conduit) without data loss."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1674
+msgid "2022-07-29"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1676
+msgid "mautrix-discord support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1678
+msgid "Thanks to [MdotAmaan](https://github.com/MdotAmaan)'s efforts, the playbook now supports bridging to [Discord](https://discordapp.com/) via the [mautrix-discord](https://mau.dev/mautrix/discord) bridge. See our [Setting up Mautrix Discord bridging](docs/configuring-playbook-bridge-mautrix-discord.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1680
+msgid "**Note**: this is a new Discord bridge. The playbook still retains Discord bridging via [matrix-appservice-discord](docs/configuring-playbook-bridge-appservice-discord.md) and [mx-puppet-discord](docs/configuring-playbook-bridge-mx-puppet-discord.md). You're free to use the bridge that serves you better, or even all three of them (for different users and use-cases)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1683
+msgid "2022-07-27"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1685
+msgid "matrix-appservice-kakaotalk support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1687
+msgid "The playbook now supports bridging to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) via [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) - a bridge based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code. Thanks to [hnarjis](https://github.com/hnarjis) for helping us add support for this!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1689
+msgid "See our [Setting up Appservice Kakaotalk bridging](docs/configuring-playbook-bridge-appservice-kakaotalk.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1692
+msgid "2022-07-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1694
+msgid "maubot support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1696
+msgid "Thanks to [Stuart Mumford (@Cadair)](https://github.com/cadair) for starting ([PR #373](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/373) and [PR #622](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/622)) and to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s) for finishing up (in [PR #1894](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1894)), the playbook can now help you set up [maubot](https://github.com/maubot/maubot) - a plugin-based Matrix bot system."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1698
+msgid "See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1701
+msgid "2022-07-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1703
+msgid "mx-puppet-skype removal"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1705
+msgid "The playbook no longer includes the [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge, because it has been broken and unmaintained for a long time. Users that have `matrix_mx_puppet_skype_enabled` in their configuration files will encounter an error when running the playbook until they remove references to this bridge from their configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1707
+msgid "To completely clean up your server from `mx-puppet-skype`'s presence on it:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1709
+msgid "ensure your Ansible configuration (`vars.yml` file) no longer contains `matrix_mx_puppet_skype_*` references"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1710
+msgid "stop and disable the systemd service (run `systemctl disable --now matrix-mx-puppet-skype` on the server)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1711
+msgid "delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-skype.service` on the server)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1712
+msgid "delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on the server)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1713
+msgid "drop the `matrix_mx_puppet_skype` database (run `/usr/local/bin/matrix-postgres-cli` on the server, and execute the `DROP DATABASE matrix_mx_puppet_skype;` query there)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1715
+msgid "If you still need bridging to [Skype](https://www.skype.com/), consider switching to [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) instead. See [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1717
+msgid "If you think this is a mistake and `mx-puppet-skype` works for you (or you get it to work somehow), let us know and we may reconsider this removal."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1719
+msgid "signald (0.19.0+) upgrade requires data migration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1721
+msgid "In [Pull Request #1921](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1921) we upgraded [signald](https://signald.org/) (used by the mautrix-signal bridge) from `v0.18.5` to `v0.20.0`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1723
+msgid "Back in the [`v0.19.0` released of signald](https://gitlab.com/signald/signald/-/blob/main/releases/0.19.0.md) (which we skipped and migrated straight to `v0.20.0`), a new `--migrate-data` command had been added that migrates avatars, group images, attachments, etc., into the database (those were previously stored in the filesystem)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1725
+msgid "If you've been using the mautrix-signal bridge for a while, you may have files stored in the local filesystem, which will need to be upgraded."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1727
+msgid "We attempt to do this data migration automatically every time Signald starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` systemd unit definition."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1729
+msgid "Keep an eye on your Signal bridge and let us know (in our [support room](README.md#support) or in [Pull Request #1921](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1921)) if you experience any trouble!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1732
+msgid "2022-07-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1734
+msgid "Ntfy push notifications support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1736
+msgid "Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the playbook can now install a [ntfy](https://ntfy.sh/) push notifications server for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1738
+msgid "See our [Setting up the ntfy push notifications server](docs/configuring-playbook-ntfy.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1741
+msgid "2022-06-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1743
+msgid "(Potential Backward Compatibility Break) Changes around metrics collection"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1745
+msgid "**TLDR**: we've made extensive **changes to metrics exposure/collection, which concern people using an external Prometheus server**. If you don't know what that is, you don't need to read below."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1747
+msgid "**Why do major changes to metrics**? Because various services were exposing metrics in different, hacky, ways. Synapse was exposing metrics at `/_synapse/metrics` and `/_synapse-worker-…/metrics` on the `matrix.example.com`. The Hookshot role was **repurposing** the Granana web UI domain (`stats.example.com`) for exposing its metrics on `stats.example.com/hookshot/metrics`, while protecting these routes using Basic Authentication **normally used for Synapse** (`/_synapse/metrics`). Node-exporter and Postgres-exporter roles were advising for more `stats.example.com` usage in manual ways. Each role was doing things differently and mixing variables from other roles. Each metrics endpoint was ending up in a different place, protected by who knows what Basic Authentication credentials (if protected at all)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1749
+msgid "**The solution**: a completely revamped way to expose metrics to an external Prometheus server. We are **introducing new `https://matrix.example.com/metrics/*` endpoints**, where various services *can* expose their metrics, for collection by external Prometheus servers. To enable the `/metrics/*` endpoints, use `matrix_nginx_proxy_proxy_matrix_metrics_enabled: true`. There's also a way to protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication). See the `matrix-nginx-proxy` role or our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation for additional variables around `matrix_nginx_proxy_proxy_matrix_metrics_enabled`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1751
+msgid "**If you are using the [Hookshot bridge](docs/configuring-playbook-bridge-hookshot.md)**, you may find that:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1752
+msgid "**Metrics may not be enabled by default anymore**:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1753
+msgid "If Prometheus is enabled (`prometheus_enabled: true`), then Hookshot metrics will be enabled automatically (`matrix_hookshot_metrics_enabled: true`). These metrics will be collected from the local (in-container) Prometheus over the container network."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1754
+msgid "**If Prometheus is not enabled** (you are either not using Prometheus or are using an external one), **Hookshot metrics will not be enabled by default anymore**. Feel free to enable them by setting `matrix_hookshot_metrics_enabled: true`. Also, see below."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1755
+msgid "When metrics are meant to be **consumed by an external Prometheus server**, `matrix_hookshot_metrics_proxying_enabled` needs to be set to `true`, so that metrics would be exposed (proxied) \"publicly\" on `https://matrix.example.com/metrics/hookshot`. To make use of this, you'll also need to enable the new `https://matrix.example.com/metrics/*` endpoints mentioned above, using `matrix_nginx_proxy_proxy_matrix_metrics_enabled`. Learn more in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1756
+msgid "**We've changed the URL we're exposing Hookshot metrics at** for external Prometheus servers. Until now, you were advised to consume Hookshot metrics from `https://stats.example.com/hookshot/metrics` (working in conjunction with `matrix_nginx_proxy_proxy_synapse_metrics`). From now on, **this no longer works**. As described above, you need to start consuming metrics from `https://matrix.example.com/metrics/hookshot`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1758
+msgid "**If you're using node-exporter** (`matrix_prometheus_node_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_node_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/node-exporter`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1760
+msgid "**If you're using [postgres-exporter](docs/configuring-playbook-prometheus-postgres.md)** (`prometheus_postgres_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/postgres-exporter`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1762
+msgid "**If you're using Synapse** and would like to collect its metrics from an external Prometheus server, you may find that:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1764
+msgid "Exposing metrics is now done using `matrix_synapse_metrics_proxying_enabled`, not `matrix_nginx_proxy_proxy_synapse_metrics: true`. You may still need to enable metrics using `matrix_synapse_metrics_enabled: true` before exposing them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1765
+msgid "Protecting metrics endpoints using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) is now done in another way. See our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1766
+msgid "If Synapse metrics are exposed, they will be made available at `https://matrix.example.com/metrics/synapse/main-process` or `https://matrix.example.com/metrics/synapse/worker/TYPE-ID` (when workers are enabled), not at `https://matrix.example.com/_synapse/metrics` and `https://matrix.example.com/_synapse-worker-…/metrics`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1767
+msgid "The playbook still generates an `external_prometheus.yml.example` sample file for scraping Synapse from Prometheus as described in [Collecting Synapse worker metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-server), but it's now saved under `/matrix/synapse` (not `/matrix`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1769
+msgid "**If you where already using a external Prometheus server** before this change, and you gave a hashed version of the password as a variable, the playbook will now take care of hashing the password for you. Thus, you need to provide the non-hashed version now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1771
+msgid "2022-06-13"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1773
+msgid "go-skype-bridge bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1775
+msgid "Thanks to [CyberShadow](https://github.com/CyberShadow), the playbook can now install the [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) bridge for bridging Matrix to [Skype](https://www.skype.com/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1777
+msgid "See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1779
+msgid "The playbook has supported [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridging (see [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md)) since [2020-04-09](#2020-04-09), but `mx-puppet-skype` is reportedly broken."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1782
+msgid "2022-06-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1784
+msgid "Running Ansible in a container can now happen on the Matrix server itself"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1786
+msgid "If you're tired of being on an old and problematic Ansible version, you can now run [run Ansible in a container on the Matrix server itself](docs/ansible.md#running-ansible-in-a-container-on-the-matrix-server-itself)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1789
+msgid "2022-05-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1791
+msgid "Synapse v1.60 upgrade may cause trouble and require manual intervention"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1793
+msgid "Synapse v1.60 will try to add a new unique index to `state_group_edges` upon startup and could fail if your database is corrupted."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1795
+msgid "We haven't observed this problem yet, but [the Synapse v1.60.0 upgrade notes](https://github.com/element-hq/synapse/blob/v1.60.0/docs/upgrade.md#adding-a-new-unique-index-to-state_group_edges-could-fail-if-your-database-is-corrupted) mention it, so we're giving you a heads up here in case you're unlucky."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1797
+msgid "**If Synapse fails to start** after your next playbook run, you'll need to:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1799
+msgid "SSH into the Matrix server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1800
+msgid "launch `/usr/local/bin/matrix-postgres-cli`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1801
+msgid "switch to the `synapse` database: `\\c synapse`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1802
+msgid "run the following SQL query:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1821
+msgid "You could then restart services: `ansible-playbook -i inventory/hosts setup.yml --tags=start`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1824
+msgid "2022-04-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1826
+msgid "Buscarron bot support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1828
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [the Buscarron bot](https://github.com/etkecc/buscarron). It's a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1830
+msgid "See our [Setting up Buscarron](docs/configuring-playbook-bot-buscarron.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1833
+msgid "2022-04-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1835
+msgid "matrix-registration-bot support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1837
+msgid "Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now help you set up [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) - a bot that is used to create and manage registration tokens for a Matrix server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1839
+msgid "See our [Setting up matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1842
+msgid "2022-04-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1844
+msgid "BorgBackup support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1846
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [Borg](https://www.borgbackup.org/) backups with [borgmatic](https://torsion.org/borgmatic/) of your Matrix server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1848
+msgid "See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1850
+msgid "(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1852
+msgid "If you're running a worker setup for Synapse (`matrix_synapse_workers_enabled: true`), the [Synapse v1.57 upgrade notes](https://github.com/element-hq/synapse/blob/v1.57.0rc1/docs/upgrade.md#changes-to-database-schema-for-application-services) say that you may need to take special care when upgrading:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1854
+msgid "Synapse v1.57.0 includes a change to the way transaction IDs are managed for application services. If your deployment uses a dedicated worker for application service traffic, **it must be stopped** when the database is upgraded (which normally happens when the main process is upgraded), to ensure the change is made safely without any risk of reusing transaction IDs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1856
+msgid "If you're not running an `appservice` worker (`matrix_synapse_workers_preset: little-federation-helper` or `matrix_synapse_workers_appservice_workers_count: 0`), you are probably safe to upgrade as per normal, without taking any special care."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1858
+msgid "If you are running a setup with an `appservice` worker, or otherwise want to be on the safe side, we recommend the following upgrade path:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1860
+msgid "Pull the latest playbook changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1861
+msgid "Stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1862
+msgid "Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1863
+msgid "Start Postgres (`systemctl start matrix-postgres` on the server)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1864
+msgid "Start the main Synapse process (`systemctl start matrix-synapse` on the server)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1865
+msgid "Wait a while so that Synapse can start and complete the database migrations. You can use `journalctl -fu matrix-synapse` on the server to get a clue. Waiting a few minutes should also be enough."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1866
+msgid "It should now be safe to start all other services. `ansible-playbook -i inventory/hosts setup.yml --tags=start` will do it for you"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1869
+msgid "2022-04-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1871
+msgid "(Compatibility Break) Changes to `docker-src` permissions necessitating manual action"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1873
+msgid "Users who build container images from source will need to manually correct file permissions of some directories on the server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1875
+msgid "When self-building, the playbook used to `git clone` repositories (into `/matrix/SERVICE/docker-src`) using the `root` user, but now uses `matrix` instead to work around [the following issue with git 2.35.2](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1749)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1877
+msgid "If you're on a non-`amd64` architecture (that is, you're overriding `matrix_architecture` in your `vars.yml` file) or you have enabled self-building for some service (e.g. `matrix_*_self_build: true`), you're certainly building some container images from source and have `docker-src` directories with mixed permissions lying around in various `/matrix/SERVICE` directories."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1879
+msgid "The playbook *could* correct these permissions automatically, but that requires additional Ansible tasks in some ~45 different places - something that takes considerable effort. So we ask users observing errors related to `docker-src` directories to correct the problem manually by **running this command on the Matrix server** (which deletes all `/matrix/*/docker-src` directories): `find /matrix -maxdepth 2 -name 'docker-src' | xargs rm -rf`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1882
+msgid "2022-03-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1884
+msgid "(Compatibility Break) ma1sd identity server no longer installed by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1886
+msgid "The playbook no longer installs the [ma1sd](https://github.com/ma1uta/ma1sd) identity server by default. The next time you run the playbook, ma1sd will be uninstalled from your server, unless you explicitly enable the ma1sd service (see how below)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1888
+msgid "The main reason we used to install ma1sd by default in the past was to prevent Element clients from talking to the `matrix.org` / `vector.im` identity servers, by forcing it to talk to our own self-hosted (but otherwise useless) identity server instead, thus preventing contact list leaks."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1890
+msgid "Since Element clients no longer default to using a public identity server if another one is not provided, we can stop installing ma1sd."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1892
+msgid "If you need to install the ma1sd identity server for some reason, you can explicitly enable it by adding this to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1899
+msgid "2022-02-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1901
+msgid "matrix_encryption_disabler support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1903
+msgid "We now support installing the [matrix_encryption_disabler](https://github.com/digitalentity/matrix_encryption_disabler) Synapse module, which lets you prevent End-to-End-Encryption from being enabled by users on your homeserver. The popular opinion is that this is dangerous and shouldn't be done, but there are valid use cases for disabling encryption discussed [here](https://github.com/matrix-org/synapse/issues/4401)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1905
+msgid "To enable this module (and prevent encryption from being used on your homserver), add `matrix_synapse_ext_encryption_disabler_enabled: true` to your configuration. This module provides further customization. Check its other configuration settings (and defaults) in `roles/custom/matrix-synapse/defaults/main.yml`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1908
+msgid "2022-02-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1910
+msgid "matrix-hookshot bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1912
+msgid "Thanks to [HarHarLinks](https://github.com/HarHarLinks), the playbook can now install the [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) bridge for bridging Matrix to multiple project management services, such as GitHub, GitLab and JIRA. See our [Setting up matrix-hookshot](docs/configuring-playbook-bridge-hookshot.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1915
+msgid "2022-01-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1917
+msgid "ARM support for matrix-corporal"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1919
+msgid "[matrix-corporal](https://github.com/devture/matrix-corporal) (as of version `2.2.3`) is now published to Docker Hub (see [devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-corporal)) as a multi-arch container image with support for all these platforms: `linux/amd64`, `linux/arm64/v8` and `linux/arm/v7`. The playbook no longer resorts to self-building matrix-corporal on these ARM architectures."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1922
+msgid "2022-01-07"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1924
+msgid "Dendrite support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1926
+msgid "**TLDR**: We now have optional experimental [Dendrite](https://github.com/matrix-org/dendrite) homeserver support for new installations. **Existing (Synapse) installations need to be updated**, because some internals changed. See [Adapting the configuration for existing Synapse installations](#adapting-the-configuration-for-existing-synapse-installations)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1928
+msgid "[Jip J. Dekker](https://github.com/Dekker1) did the [initial work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/818) of adding [Dendrite](https://github.com/matrix-org/dendrite) support to the playbook back in January 2021. Lots of work (and time) later, Dendrite support is finally ready for testing."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1930
+msgid "We believe that 2022 will be the year of the non-Synapse Matrix server!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1932
+msgid "The playbook was previously quite [Synapse](https://github.com/element-hq/synapse)-centric, but can now accommodate multiple homeserver implementations. Only one homeserver implementation can be active (installed) at a given time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1934
+msgid "**Synapse is still the default homeserver implementation** installed by the playbook. A new variable (`matrix_homeserver_implementation`) controls which server implementation is enabled (`synapse` or `dendrite` at the given moment)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1936
+msgid "Adapting the configuration for existing Synapse installations"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1938
+msgid "Because the playbook is not so Synapse-centric anymore, a small configuration change is necessary for existing installations to bring them up to date."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1940
+msgid "The `vars.yml` file for **existing installations will need to be updated** by adding this **additional configuration**:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1952
+msgid "Trying out Dendrite"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1954
+msgid "Finally, **to try out Dendrite**, we recommend that you **use a new server** and the following addition to your `vars.yml` configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1960
+msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse to Dendrite) without data loss."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1962
+msgid "We're excited to gain support for other homeserver implementations, like [Conduit](https://conduit.rs/), etc!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1964
+msgid "Honoroit bot support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1966
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now help you set up [Honoroit](https://github.com/etkecc/honoroit) - a helpdesk bot."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1968
+msgid "See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1971
+msgid "2022-01-06"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1973
+msgid "Cinny support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1975
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports [Cinny](https://cinny.in/) - a new simple, elegant and secure Matrix client."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1977
+msgid "By default, we still install Element Web. Still, people who'd like to try Cinny out can now install it via the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1979
+msgid "Additional details are available in [Setting up Cinny](docs/configuring-playbook-client-cinny.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1982
+msgid "2021-12-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1984
+msgid "Twitter bridging support via mautrix-twitter"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1986
+msgid "Thanks to [Matthew Cengia](https://github.com/mattcen) and [Shreyas Ajjarapu](https://github.com/shreyasajj), besides [mx-puppet-twitter](docs/configuring-playbook-bridge-mx-puppet-twitter.md), bridging to [Twitter](https://twitter.com/) can now also happen with [mautrix-twitter](docs/configuring-playbook-bridge-mautrix-twitter.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1989
+msgid "2021-12-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1991
+msgid "(Security) Users of the Signal bridge may wish to upgrade it to work around log4j vulnerability"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1993
+msgid "Recently, a security vulnerability affecting the Java logging package `log4j` [has been discovered](https://www.huntress.com/blog/rapid-response-critical-rce-vulnerability-is-affecting-java). Software that uses this Java package is potentially vulnerable."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1995
+msgid "One such piece of software that is part of the playbook is the [mautrix-signal bridge](./docs/configuring-playbook-bridge-mautrix-signal.md), which [has been patched already](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1452). If you're running this bridge, you may wish to [upgrade](./docs/maintenance-upgrading-services.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1998
+msgid "2021-11-11"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2000
+msgid "Dropped support for Postgres v9.6"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2002
+msgid "Postgres v9.6 reached its end of life today, so the playbook will refuse to run for you if you're still on that version."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2004
+msgid "Synapse still supports v9.6 (for now), but we're retiring support for it early, to avoid having to maintain support for so many Postgres versions. Users that are still on Postgres v9.6 can easily [upgrade Postgres](docs/maintenance-postgres.md#upgrading-postgresql) via the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2007
+msgid "2021-10-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2009
+msgid "Hangouts bridge no longer updated, superseded by a Googlechat bridge"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2011
+msgid "The mautrix-hangouts bridge is no longer receiving updates upstream and is likely to stop working in the future. We still retain support for this bridge in the playbook, but you're encouraged to switch away from it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2013
+msgid "There's a new [mautrix-googlechat](https://github.com/mautrix/googlechat) bridge that you can [install using the playbook](docs/configuring-playbook-bridge-mautrix-googlechat.md). Your **Hangouts bridge data will not be migrated**, however. You need to start fresh with the new bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2016
+msgid "2021-08-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2018
+msgid "LinkedIn bridging support via beeper-linkedin"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2020
+msgid "Thanks to [Alexandar Mechev](https://github.com/apmechev), the playbook can now install the [beeper-linkedin](https://gitlab.com/beeper/linkedin) bridge for bridging to [LinkedIn](https://www.linkedin.com/) Messaging."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2022
+msgid "This brings the total number of bridges supported by the playbook up to 20. See all supported bridges [here](docs/configuring-playbook.md#bridging-other-networks)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2024
+msgid "To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2027
+msgid "2021-08-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2029
+msgid "Sygnal upgraded - ARM support and no longer requires a database"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2031
+msgid "The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been upgraded from `v0.9.0` to `v0.10.1`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2033
+msgid "This is an optional component for the playbook, so most of our users wouldn't care about this announcement."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2035
+msgid "Since this feels like a relatively big (and untested, as of yet) Sygnal change, we're putting up this changelog entry."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2037
+msgid "The new version is also available for the ARM architecture. It also no longer requires a database anymore. If you need to downgrade to the previous version, changing `matrix_sygnal_version` or `matrix_sygnal_docker_image` will not be enough, as we've removed the `database` configuration completely. You'd need to switch to an earlier playbook commit."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2040
+msgid "2021-05-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2042
+msgid "Hydrogen support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2044
+msgid "Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook now supports [Hydrogen](https://github.com/vector-im/hydrogen-web) - a new lightweight Matrix client with legacy and mobile browser support."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2046
+msgid "By default, we still install Element Web, as Hydrogen is still not fully-featured. Still, people who'd like to try Hydrogen out can now install it via the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2048
+msgid "Additional details are available in [Setting up Hydrogen](docs/configuring-playbook-client-hydrogen.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2051
+msgid "2021-05-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2053
+msgid "Heisenbridge support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2055
+msgid "Thanks to [Toni Spets (hifi)](https://github.com/hifi), the playbook now supports bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) using yet another bridge (besides matrix-appservice-irc), called [Heisenbridge](https://github.com/hifi/heisenbridge)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2057
+msgid "Additional details are available in [Setting up Heisenbridge bouncer-style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2060
+msgid "2021-04-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2062
+msgid "Disabling TLSv1 and TLSv1.1 for Coturn"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2064
+msgid "To improve security, we've [removed TLSv1 and TLSv1.1 support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/999) from our default [Coturn](https://github.com/coturn/coturn) configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2066
+msgid "If you need to support old clients, you can re-enable both (or whichever one you need) with the following configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2074
+msgid "2021-04-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2076
+msgid "Automated local Postgres backup support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2078
+msgid "Thanks to [foxcris](https://github.com/foxcris), the playbook can now make automated local Postgres backups on a fixed schedule using [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2080
+msgid "Additional details are available in [Setting up postgres backup](docs/configuring-playbook-postgres-backup.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2083
+msgid "2021-04-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2085
+msgid "Mjolnir moderation tool (bot) support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2087
+msgid "Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook can now install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation tool (bot)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2089
+msgid "Additional details are available in [Setting up Mjolnir](docs/configuring-playbook-bot-mjolnir.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2092
+msgid "2021-03-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2094
+msgid "Sygnal push gateway support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2096
+msgid "The playbook can now install the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2098
+msgid "This is only useful to people who develop/build their own Matrix client applications."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2100
+msgid "Additional details are available in our [Setting up the Sygnal push gateway](docs/configuring-playbook-sygnal.md) docs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2103
+msgid "2021-03-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2105
+msgid "Go-NEB support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2107
+msgid "Thanks to [Zir0h](https://github.com/Zir0h), the playbook can now install and configure the [Go-NEB](https://github.com/matrix-org/go-neb) bot."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2109
+msgid "Additional details are available in [Setting up Go-NEB](docs/configuring-playbook-bot-go-neb.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2112
+msgid "2021-02-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2114
+msgid "GroupMe bridging support via mx-puppet-groupme"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2116
+msgid "Thanks to [Cody Neiman](https://github.com/xangelix), the playbook can now install the [mx-puppet-groupme](https://gitlab.com/robintown/mx-puppet-groupme) bridge for bridging to [GroupMe](https://groupme.com)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2118
+msgid "This brings the total number of bridges supported by the playbook up to 18. See all supported bridges [here](docs/configuring-playbook.md#bridging-other-networks)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2120
+msgid "To get started, follow our [Setting up MX Puppet GroupMe](docs/configuring-playbook-bridge-mx-puppet-groupme.md) docs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2122
+msgid "Mautrix Instagram bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2124
+msgid "The playbook now supports bridging with [Instagram](https://www.instagram.com/) by installing the [mautrix-instagram](https://github.com/tulir/mautrix-instagram) bridge. This playbook functionality is available thanks to [@MarcProe](https://github.com/MarcProe)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2126
+msgid "Additional details are available in [Setting up Mautrix Instagram bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2128
+msgid "Synapse workers support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2130
+msgid "After [lots and lots of work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/456) (done over many months by [Marcel Partap](https://github.com/eMPee584), [Max Klenk](https://github.com/maxklenk), a few others from the [Technical University of Dresden, Germany](https://tu-dresden.de/) and various other contributors), support for Synapse workers has finally landed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2132
+msgid "Having support for workers makes the playbook suitable for larger homeserver deployments."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2134
+msgid "Our setup is not yet perfect (we don't support all types of workers; scaling some of them (like `pusher`, `federation_sender`) beyond a single instance is not yet supported). Still, it's a great start and can already power homeservers with thousands of users, like the [Matrix deployment at TU Dresden](https://doc.matrix.tu-dresden.de/en/) discussed in [Matrix Live S06E09 - TU Dresden on their Matrix deployment](https://www.youtube.com/watch?v=UHJX2pmT2gk)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2136
+msgid "By default, workers are disabled and Synapse runs as a single process (homeservers don't necessarily need the complexity and increased memory requirements of running a worker-based setup)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2138
+msgid "To enable Synapse workers, follow our [Load balancing with workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) documentation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2141
+msgid "2021-02-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2143
+msgid "(Potential Breaking Change) Monitoring/metrics support using Prometheus and Grafana"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2145
+msgid "Thanks to [@Peetz0r](https://github.com/Peetz0r), the playbook can now install a bunch of tools for monitoring your Matrix server: the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2147
+msgid "To get get these installed, follow our [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](docs/configuring-playbook-prometheus-grafana.md) docs page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2149
+msgid "This update comes with a **potential breaking change** for people who were already exposing Synapse metrics (for consumption via another Prometheus installation). From now on, `matrix_synapse_metrics_enabled: true` no longer exposes metrics publicly via matrix-nginx-proxy (at `https://matrix.example.com/_synapse/metrics`). To do so, you'd need to explicitly set `matrix_nginx_proxy_proxy_synapse_metrics: true`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2152
+msgid "2021-01-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2154
+msgid "Etherpad support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2156
+msgid "Thanks to [@pushytoxin](https://github.com/pushytoxin), the playbook can now install the [Etherpad](https://etherpad.org) realtime collaborative text editor. It can be used in a [Jitsi](https://jitsi.org/) audio/video call or integrated as a widget into Matrix chat rooms via the [Dimension](https://dimension.t2bot.io) integration manager."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2158
+msgid "To get it installed, follow [our Etherpad docs page](docs/configuring-playbook-etherpad.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2161
+msgid "2021-01-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2163
+msgid "(Breaking Change) Postgres changes that require manual intervention"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2165
+msgid "We've made a lot of changes to our Postgres setup and some manual action is required (described below). Sorry about the hassle."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2167
+msgid "**TLDR**: people running an [external Postgres server](docs/configuring-playbook-external-postgres.md) don't need to change anything for now. Everyone else (the common/default case) is affected and manual intervention is required."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2169
+msgid "Why?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2171
+msgid "we had a default Postgres password (`matrix_postgres_connection_password: synapse-password`), which we think is **not ideal for security anymore**. We now ask you to generate/provide a strong password yourself. Postgres is normally not exposed outside the container network, making it relatively secure, but still:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2172
+msgid "by tweaking the configuration, you may end up intentionally or unintentionally exposing your Postgres server to the local network (or even publicly), while still using the default default credentials (`synapse` + `synapse-password`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2173
+msgid "we can't be sure we trust all these services (bridges, etc). Some of them may try to talk to or attack `matrix-postgres` using the default credentials (`synapse` + `synapse-password`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2174
+msgid "you may have other containers running on the same Docker network, which may try to talk to or attack `matrix-postgres` using the default credentials (`synapse` + `synapse-password`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2175
+msgid "our Postgres usage **was overly-focused on Synapse** (default username of `synapse` and default/main database of `homeserver`). Additional homeserver options are likely coming in the future ([Dendrite](https://matrix.org/docs/projects/server/dendrite), [Conduit](https://matrix.org/docs/projects/server/conduit), [The Construct](https://matrix.org/docs/projects/server/construct)), so being too focused on `matrix-synapse` is not great. From now on, Synapse is just another component of this playbook, which happens to have an *additional database* (called `synapse`) on the Postgres server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2176
+msgid "we try to reorganize things a bit, to make the playbook even friendlier to people running an [external Postgres server](docs/configuring-playbook-external-postgres.md). Work on this will proceed in the future."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2178
+msgid "So, this is some **effort to improve security** and to **prepare for a brighter future of having more homeserver options** than just Synapse."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2180
+msgid "What has really changed?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2182
+msgid "the default superuser Postgres username is now `matrix` (used to be `synapse`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2183
+msgid "the default Postgres database is now `matrix` (used to be `homeserver`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2184
+msgid "Synapse's database is now `synapse` (used to be `homeserver`). This is now just another \"additional database\" that the playbook manages for you"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2185
+msgid "Synapse's user called `synapse` is just a regular user that can only use the `synapse` database (not a superuser anymore)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2187
+msgid "What do I do if I'm using the integrated Postgres server (default)?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2189
+msgid "By default, the playbook runs an integrated Postgres server for you in a container (`matrix-postgres`). Unless you've explicitly configured an [external Postgres server](docs/configuring-playbook-external-postgres.md), these steps are meant for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2191
+msgid "To migrate to the new setup, expect a few minutes of downtime, while you follow these steps:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2193
+msgid "We believe the steps below are safe and you won't encounter any data loss, but consider [making a Postgres backup](docs/maintenance-postgres.md#backing-up-postgresql) anyway. If you've never backed up Postgres, now would be a good time to try it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2195
+msgid "Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can create one with a command like `pwgen -s 64 1`. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2197
+msgid "Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` file, adding a line like this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2202 ../../../CHANGELOG.md:2214
+msgid ".. where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2204
+msgid "Stop all services: `ansible-playbook -i inventory/hosts setup.yml --tags=stop`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2205
+msgid "Log in to the server via SSH. The next commands will be performed there."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2206
+msgid "Start the Postgres database server: `systemctl start matrix-postgres`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2207
+msgid "Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2208
+msgid "Execute the following query, while making sure to **change the password inside** (**don't forget the ending `;`**):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2216
+msgid "Execute the following queries as you see them (no modifications necessary, so you can just **paste them all at once**):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2234
+msgid "You may need to press *Enter* after pasting the lines above."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2236
+msgid "Re-run the playbook normally: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2238
+msgid "What do I do if I'm using an external Postgres server?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2240
+msgid "If you've explicitly configured an [external Postgres server](docs/configuring-playbook-external-postgres.md), there are **no changes** that you need to do at this time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2242
+msgid "The fact that we've renamed Synapse's database from `homeserver` to `synapse` (in our defaults) should not affect you, as you're already explicitly defining `matrix_synapse_database_database` (if you've followed our guide, that is). If you're not explicitly defining this variable, you may wish to do so (`matrix_synapse_database_database: homeserver`), to avoid the new `synapse` default and keep things as they were."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2245
+msgid "2021-01-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2247
+msgid "(Breaking Change) The mautrix-facebook bridge now requires a Postgres database"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2249
+msgid "**Update from 2021-11-15**: SQLite support has been re-added to the mautrix-facebook bridge in [v0.3.2](https://github.com/mautrix/facebook/releases/tag/v0.3.2). You can ignore this changelog entry."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2251
+msgid "A new version of the [mautrix-facebook](https://github.com/tulir/mautrix-facebook) bridge has been released. It's a full rewrite of its backend and the bridge now requires Postgres. New versions of the bridge can no longer run on SQLite."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2253
+msgid "**TLDR**: if you're NOT using an [external Postgres server](docs/configuring-playbook-external-postgres.md) and have NOT forcefully kept the bridge on SQLite during [The big move to all-on-Postgres (potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous), you will be automatically upgraded without manual intervention. All you need to do is send a `login` message to the Facebook bridge bot again."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2255
+msgid "Whether this change requires your intervention depends mostly on:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2256
+msgid "whether you're using an [external Postgres server](docs/configuring-playbook-external-postgres.md). If yes, then [you need to do something](#upgrade-path-for-people-running-an-external-postgres-server)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2257
+msgid "or whether you've force-changed the bridge's database engine to SQLite (`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) some time in the past (likely during [The big move to all-on-Postgres (potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2259
+msgid "As already mentioned above, you most likely don't need to do anything. If you rerun the playbook and don't get an error, you've been automatically upgraded. Just send a `login` message to the Facebook bridge bot again. Otherwise, read below for a solution."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2261
+msgid "Upgrade path for people NOT running an external Postgres server (default for the playbook)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2263
+msgid "If you're **not running an external Postgres server**, then this bridge either already works on Postgres for you, or you've intentionally kept it back on SQLite with custom configuration (`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) ."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2265
+msgid "Simply remove that custom configuration from your `vars.yml` file (if it's there) and re-run the playbook. It should upgrade you automatically. You'll need to send a `login` message to the Facebook bridge bot again."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2267
+msgid "Alternatively, [you can stay on SQLite for a little longer](#staying-on-sqlite-for-a-little-longer-temporary-solution)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2269
+msgid "Upgrade path for people running an external Postgres server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2271
+msgid "For people using the internal Postgres server (the default for the playbook):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2272
+msgid "we automatically create an additional `matrix_mautrix_facebook` Postgres database and credentials to access it"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2273
+msgid "we automatically adjust the bridge's `matrix_mautrix_facebook_database_*` variables to point the bridge to that Postgres database"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2274
+msgid "we use [pgloader](https://pgloader.io/) to automatically import the existing SQLite data for the bridge into the `matrix_mautrix_facebook` Postgres database"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2276
+msgid "If you are using an [external Postgres server](docs/configuring-playbook-external-postgres.md), unfortunately we currently can't do any of that for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2278
+msgid "You have 3 ways to proceed:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2280
+msgid "contribute to the playbook to make this possible (difficult)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2281
+msgid "or, do the migration \"steps\" manually:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2282
+msgid "stop the bridge (`systemctl stop matrix-mautrix-facebook`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2283
+msgid "create a new `matrix_mautrix_facebook` Postgres database for it"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2284
+msgid "run [pgloader](https://pgloader.io/) manually (we import this bridge's data using default settings and it works well)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2285
+msgid "define `matrix_mautrix_facebook_database_*` variables in your `vars.yml` file (credentials, etc.) - you can find their defaults in `roles/custom/matrix-mautrix-facebook/defaults/main.yml`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2286
+msgid "switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: 'postgres'` in your `vars.yml` file)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2287
+msgid "re-run the playbook (`--tags=setup-all,start`) and ensure the bridge works (`systemctl status matrix-mautrix-facebook` and `journalctl -fu matrix-mautrix-facebook`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2288
+msgid "send a `login` message to the Facebook bridge bot again"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2289
+msgid "or, [stay on SQLite for a little longer (temporary solution)](#staying-on-sqlite-for-a-little-longer-temporary-solution)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2291
+msgid "Staying on SQLite for a little longer (temporary solution)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2293
+msgid "To keep using this bridge with SQLite for a little longer (**not recommended**), use the following configuration in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2303
+msgid "If you do this, keep in mind that **you can't run this forever**. This SQLite-supporting bridge version is not getting any updates and will break sooner or later. The playbook will also drop support for SQLite at some point in the future."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2306
+msgid "2021-01-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2308
+msgid "matrix-corporal goes 2.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2310
+msgid "[matrix-corporal v2 has been released](https://github.com/devture/matrix-corporal/releases/tag/2.0.0) and the playbook also supports it now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2312
+msgid "No manual intervention is required in the common case."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2314
+msgid "The new [matrix-corporal](https://github.com/devture/matrix-corporal) version is also the first one to support Interactive Authentication. If you wish to enable that (hint: you should), you'll need to set up the [REST auth password provider](docs/configuring-playbook-rest-auth.md). There's more information in [our matrix-corporal docs](docs/configuring-playbook-matrix-corporal.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2317
+msgid "2021-01-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2319
+msgid "Moving from cronjobs to systemd timers"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2321
+msgid "We no longer use cronjobs for Let's Encrypt SSL renewal and `matrix-nginx-proxy`/`matrix-coturn` reloading. Instead, we've switched to systemd timers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2323
+msgid "The largest benefit of this is that we no longer require you to install a cron daemon, thus simplifying our install procedure."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2325
+msgid "The playbook will migrate you from cronjobs to systemd timers automatically. This is just a heads up."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2328
+msgid "2021-01-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2330
+msgid "(Breaking Change) New SSL configuration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2332
+msgid "SSL configuration (protocols, ciphers) can now be more easily controlled thanks to us making use of configuration presets."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2334
+msgid "We define a few presets (old, intermediate, modern), following the [Mozilla SSL Configuration Generator](https://ssl-config.mozilla.org/#server=nginx)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2336
+msgid "A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is used (defaults to `\"intermediate\"`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2338
+msgid "Compared to before, this changes nginx's `ssl_prefer_server_ciphers` to `off`  (used to default to `on`). It also add some more ciphers to the list, giving better performance on mobile devices, and removes some weak ciphers. More information in the [documentation](docs/configuring-playbook-nginx.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2340
+msgid "To revert to the old behaviour, set the following variables:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2347
+msgid "Just like before, you can still use your own custom protocols by specifying them in `matrix_nginx_proxy_ssl_protocols`. Doing so overrides the values coming from the preset."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2350
+msgid "2021-01-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2352
+msgid "Signal bridging support via mautrix-signal"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2354
+msgid "Thanks to [laszabine](https://github.com/laszabine)'s efforts, the playbook now supports bridging to [Signal](https://www.signal.org/) via the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge. See our [Setting up Mautrix Signal bridging](docs/configuring-playbook-bridge-mautrix-signal.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2356
+msgid "If you had installed the mautrix-signal bridge while its Pull Request was still work-in-progress, you can migrate your data to the new and final setup by referring to [this comment](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/686#issuecomment-753510789)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2359
+msgid "2020-12-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2361
+msgid "The big move to all-on-Postgres (potentially dangerous)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2363
+msgid "**TLDR**: all your bridges (and other services) will likely be auto-migrated from SQLite/nedb to Postgres, hopefully without trouble. You can opt-out (see how below), if too worried about breakage."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2365
+msgid "Until now, we've only used Postgres as a database for Synapse. All other services (bridges, bots, etc.) were kept simple and used a file-based database (SQLite or nedb)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2367
+msgid "Since [this huge pull request](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/740), **all of our services now use Postgres by default**. Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann) for starting the work on it and for providing great input!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2369
+msgid "Moving all services to Postgres brings a few **benefits** to us:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2371
+msgid "**improved performance**"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2372
+msgid "**improved compatibility**. Most bridges are deprecating SQLite/nedb support or offer less features when not on Postgres."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2373
+msgid "**easier backups**. It's still some effort to take a proper backup (Postgres dump + various files, keys), but a Postgres dump now takes you much further."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2374
+msgid "we're now **more prepared to introduce other services** that need a Postgres database - [Dendrite](https://github.com/matrix-org/dendrite), the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge (existing [pull request](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/686)), etc."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2376
+msgid "Key takeway"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2378
+msgid "existing installations that use an [external Postgres](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-external-postgres.md) server should be unaffected (they remain on SQLite/nedb for all services, except Synapse)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2380
+msgid "for existing installations which use our integrated Postgres database server (`matrix-postgres`, which is the default), **we automatically migrate data** from SQLite/nedb to Postgres and **archive the database files** (`something.db` -> `something.db.backup`), so you can restore them if you need to go back (see how below)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2382
+msgid "Opting-out of the Postgres migration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2384
+msgid "This is a **very large and somewhat untested change** (potentially dangerous), so **if you're not feeling confident/experimental, opt-out** of it for now. Still, it's the new default and what we (and various bridges) will focus on going forward, so don't stick to old ways for too long."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2386
+msgid "You can remain on SQLite/nedb (at least for now) by adding a variable like this to your `vars.yml` file for each service you use: `matrix_COMPONENT_database_engine: sqlite` (e.g. `matrix_mautrix_facebook_database_engine: sqlite`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2388
+msgid "Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2390
+msgid "Going back to SQLite/nedb if things went wrong"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2392
+msgid "If you went with the Postgres migration and it went badly for you (some bridge not working as expected or not working at all), do this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2394
+msgid "stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2395
+msgid "SSH into the server and rename the old database files (`something.db.backup` -> `something.db`). Example: `mv /matrix/mautrix-facebook/data/mautrix-facebook.db.backup /matrix/mautrix-facebook/data/mautrix-facebook.db`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2396
+msgid "switch the affected service back to SQLite (e.g. `matrix_mautrix_facebook_database_engine: sqlite`). Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2397
+msgid "re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2398
+msgid "[get in touch](README.md#support) with us"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2400
+msgid "2020-12-11"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2402
+msgid "synapse-janitor support removed"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2404
+msgid "We've removed support for the unmaintained [synapse-janitor](https://github.com/xwiki-labs/synapse_scripts) script. There's been past reports of it corrupting the Synapse database. Since there hasn't been any new development on it and it doesn't seem too useful nowadays, there's no point in including it in the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2406
+msgid "If you need to clean up or compact your database, consider using the Synapse Admin APIs directly. See our [Synapse maintenance](docs/maintenance-synapse.md) and [Postgres maintenance](docs/maintenance-postgres.md) documentation pages for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2408
+msgid "Docker 20.10 is here"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2410
+msgid "(No need to do anything special in relation to this. Just something to keep in mind)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2412
+msgid "Docker 20.10 got released recently and your server will likely get it the next time you update."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2414
+msgid "This is the first major Docker update in a long time and it packs a lot of changes. Some of them introduced some breakage for us initially (see [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/d08b27784f222effcbce2abf924bf07bbe0893be) and [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/7593d969e316cc0144bce378a5be58c76c2c37ee)), but it should be all good now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2417
+msgid "2020-12-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2419
+msgid "openid APIs exposed by default on the federation port when federation disabled"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2421
+msgid "We've changed some defaults. People running with our default configuration (federation enabled), are not affected at all."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2423
+msgid "If you are running an unfederated server (`matrix_synapse_federation_enabled: false`), this may be of interest to you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2425
+msgid "When federation is disabled, but ma1sd or Dimension are enabled, we'll now expose the `openid` APIs on the federation port. These APIs are necessary for some ma1sd features to work. If you'd like to prevent this, you can: `matrix_synapse_federation_port_openid_resource_required: false`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2428
+msgid "2020-11-27"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2430
+msgid "Recent Jitsi updates may require configuration changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2432
+msgid "We've recently [updated from Jitsi build 4857 to build 5142](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/719), which brings a lot of configuration changes."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2434
+msgid "**If you use our default Jitsi settings, you won't have to do anything.**"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2436
+msgid "People who have [fine-tuned Jitsi](docs/configuring-playbook-jitsi.md#optional-fine-tune-jitsi) may find that some options got renamed now, others are gone and yet others still need to be defined in another way."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2438
+msgid "The next time you run the playbook [installation](docs/installing.md) command, our validation logic will tell you if you're using some variables like that and will recommend a migration path for each one."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2440
+msgid "Additionally, we've recently disabled transcriptions (`jitsi_enable_transcriptions: false`) and recording (`jitsi_enable_recording: false`) by default. These features did not work anyway, because we don't install the required dependencies for them (Jigasi and Jibri, respectively). If you've been somehow pointing your Jitsi installation to some manually installed Jigasi/Jibri service, you may need to toggle these flags back to enabled to have transcriptions and recordings working."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2443
+msgid "2020-11-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2445 ../../../CHANGELOG.md:2453
+msgid "Breaking change matrix-sms-bridge"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2447
+msgid "Because of many problems using gammu as SMS provider, matrix-sms-bridge now uses (https://github.com/RebekkaMa/android-sms-gateway-server) by default. See (the docs)[./docs/configuring-playbook-bridge-matrix-bridge-sms.md] which new vars you need to add."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2449
+msgid "If you are using this playbook to deploy matrix-sms-bridge and still really want to use gammu as SMS provider, we could possibly add support for both android-sms-gateway-server and gammu."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2451
+msgid "2020-11-13"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2455
+msgid "The new version of [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) changed its database from neo4j to h2. You need to sync the bridge at the first start. Note that this only will sync rooms where the @smsbot:yourServer is member. For rooms without @smsbot:yourServer you need to kick and invite the telephone number **or** invite @smsbot:yourServer."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2457
+msgid "Add the following to your `vars.yml` file: `matrix_sms_bridge_container_extra_arguments=['--env SPRING_PROFILES_ACTIVE=initialsync']`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2458
+msgid "Login to your host shell and remove old systemd file from your host: `rm /etc/systemd/system/matrix-sms-bridge-database.service`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2459
+msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-sms-bridge,start`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2460
+msgid "Login to your host shell and check the logs with `journalctl -u matrix-sms-bridge` until the sync finished."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2461
+msgid "Remove the var from the first step."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2462
+msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2464
+msgid "2020-11-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2466
+msgid "Dynamic DNS support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2468
+msgid "Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook can now manage Dynamic DNS for you using [ddclient](https://ddclient.net/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2470
+msgid "To learn more, follow our [Dynamic DNS docs page](docs/configuring-playbook-dynamic-dns.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2473
+msgid "2020-10-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2475
+msgid "(Compatibility Break) https://matrix.example.com/ now redirects to https://element.example.com/"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2477
+msgid "Until now, we used to serve a static page coming from Synapse at `https://matrix.example.com/`. This page was not very useful to anyone."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2479
+msgid "Since `matrix.example.com` may be accessed by regular users in certain conditions, it's probably better to redirect them to a better place (e.g. to [Element Web](docs/configuring-playbook-client-element-web.md))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2481
+msgid "If Element Web is installed (`matrix_client_element_enabled: true`, which it is by default), we now redirect people to it, instead of showing them a Synapse static page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2483
+msgid "If you'd like to control where the redirect goes, use the `matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain` variable. To restore the old behavior of not redirecting anywhere and serving the Synapse static page, set it to an empty value (`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain: \"\"`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2486
+msgid "2020-10-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2488
+msgid "(Compatibility Break) /_synapse/admin is no longer publicly exposed by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2490
+msgid "We used to expose the Synapse Admin APIs publicly (at `https://matrix.example.com/_synapse/admin`). These APIs require authentication with a valid access token, so it's not that big a deal to expose them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2492
+msgid "However, following [official Synapse's reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints), we're no longer exposing `/_synapse/admin` by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2494
+msgid "If you'd like to restore restore the old behavior and expose `/_synapse/admin` publicly, you can use the following configuration (in your `vars.yml`):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2501
+msgid "2020-10-02"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2503
+msgid "Minimum Ansible version raised to v2.7.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2505
+msgid "We were claiming to support [Ansible](https://www.ansible.com/) v2.5.2 and higher, but issues like [#662](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/662) demonstrate that we need at least v2.7.0."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2507
+msgid "If you've been using the playbook without getting any errors until now, you're probably on a version higher than that already (or you're not using the `matrix-ma1sd` and `matrix-client-element` roles)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2509
+msgid "Our [Ansible docs page](docs/ansible.md) contains information on how to run a more up-to-date version of Ansible."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2512
+msgid "2020-10-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2514
+msgid "Postgres 13 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2516
+msgid "The playbook now installs [Postgres 13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2518
+msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x, 10.x, 11.x or 12.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2520
+msgid "2020-09-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2522
+msgid "matrix-registration support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2524
+msgid "The playbook can now help you set up [matrix-registration](https://github.com/ZerataX/matrix-registration) - an application that lets you keep your Matrix server's registration private, but still allow certain users (those having a unique registration link) to register by themselves."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2526
+msgid "See our [Setting up matrix-registration](docs/configuring-playbook-matrix-registration.md) documentation page to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2529
+msgid "2020-08-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2531
+msgid "rust-synapse-compress-state support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2533
+msgid "The playbook can now help you use [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) to compress the state groups in your Synapse database."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2535
+msgid "See our [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state) documentation page to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2538
+msgid "2020-07-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2540
+msgid "Synapse Admin support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2542
+msgid "The playbook can now help you set up [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2544
+msgid "See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-admin.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2547
+msgid "2020-07-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2549
+msgid "matrix-reminder-bot support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2551
+msgid "The playbook can now help you set up [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2553
+msgid "See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-matrix-reminder-bot.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2556
+msgid "2020-07-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2558
+msgid "(Compatibility Break) Riot is now Element"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2560
+msgid "As per the official announcement, [Riot has been rebraned to Element](https://element.io/blog/welcome-to-element/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2562
+msgid "The playbook follows suit. Existing installations have a few options for how to handle this."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2564
+msgid "See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md#migrating-to-element) documentation page for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2567
+msgid "2020-07-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2569
+msgid "Steam bridging support via mx-puppet-steam"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2571
+msgid "Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the playbook now supports bridging to [Steam](https://steamapp.com/) via the [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) bridge. See our [Setting up MX Puppet Steam bridging](docs/configuring-playbook-bridge-mx-puppet-steam.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2574
+msgid "2020-07-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2576
+msgid "Discord bridging support via mx-puppet-discord"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2578
+msgid "Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the playbook now supports bridging to [Discord](https://discordapp.com/) via the [mx-puppet-discord](https://github.com/Sorunome/mx-puppet-discord) bridge. See our [Setting up MX Puppet Discord bridging](docs/configuring-playbook-bridge-mx-puppet-discord.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2580
+msgid "**Note**: this is a new Discord bridge. The playbook still retains Discord bridging via [matrix-appservice-discord](docs/configuring-playbook-bridge-appservice-discord.md). You're free too use the bridge that serves you better, or even both (for different users and use-cases)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2583
+msgid "2020-06-30"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2585
+msgid "Instagram and Twitter bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2587
+msgid "Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann)'s efforts, the playbook now supports bridging to [Instagram](https://www.instagram.com/) via the [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) bridge. See our [Setting up MX Puppet Instagram bridging](docs/configuring-playbook-bridge-mx-puppet-instagram.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2589
+msgid "Thanks to [Tulir Asokan](https://github.com/tulir)'s efforts, the playbook now supports bridging to [Twitter](https://twitter.com/) via the [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) bridge. See our [Setting up MX Puppet Twitter bridging](docs/configuring-playbook-bridge-mx-puppet-twitter.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2592
+msgid "2020-06-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2594
+msgid "(Post Mortem / fixed Security Issue) Re-enabling User Directory search powered by the ma1sd Identity Server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2596 ../../../CHANGELOG.md:2625
+msgid "User Directory search requests used to go to the ma1sd identity server by default, which queried its own stores and the Synapse database."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2598
+msgid "ma1sd's [security issue](https://github.com/ma1uta/ma1sd/issues/44) has been fixed in version `2.4.0`, with [this commit](ma1uta/ma1sd@2bb5a734d11662b06471113cf3d6b4cee5e33a85). `ma1sd 2.4.0` is now the default version for this playbook. For more information on what happened, please check the mentioned issue."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2600
+msgid "We are re-enabling user directory search with this update. Those who would like to keep it disabled can use this configuration: `matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2602
+msgid "As always, re-running the playbook is enough to get the updated bits."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2604
+msgid "2020-06-11"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2606
+msgid "SMS bridging requires db reset"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2608
+msgid "The current version of [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) needs you to delete the database to work as expected. Just remove `/matrix/matrix-sms-bridge/database/*`. It also adds a new requried var `matrix_sms_bridge_default_region`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2610
+msgid "To reuse your existing rooms, invite `@smsbot:yourServer` to the room or write a message. You are also able to use automated room creation with telephonenumers by writing `sms send -t 01749292923 \"Hello World\"` in a room with `@smsbot:yourServer`. See [the docs](https://github.com/benkuly/matrix-sms-bridge) for more information."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2612
+msgid "2020-06-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2614
+msgid "SMS bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2616
+msgid "Thanks to [benkuly](https://github.com/benkuly)'s efforts, the playbook now supports bridging to SMS (with one telephone number only) via [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2618
+msgid "See our [Setting up Matrix SMS bridging](docs/configuring-playbook-bridge-matrix-bridge-sms.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2621
+msgid "2020-05-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2623
+msgid "(Compatibility Break / Security Issue) Disabling User Directory search powered by the ma1sd Identity Server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2627
+msgid "ma1sd current has [a security issue](https://github.com/ma1uta/ma1sd/issues/44), which made it leak information about all users - including users created by bridges, etc."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2629
+msgid "Until the issue gets fixed, we're making User Directory search not go to ma1sd by default. You **need to re-run the playbook and restart services to apply this workaround**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2631
+msgid "*If you insist on restoring the old behavior* (**which has a security issue!**), you *might* use this configuration: `matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: \"{{ matrix_ma1sd_enabled }}\"`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2634
+msgid "2020-04-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2636
+msgid "Newer IRC bridge (with potential breaking change)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2638
+msgid "This upgrades matrix-appservice-irc from 0.14.1 to 0.16.0.  Upstream made a change to how you define manual mappings.  If you added a `mapping` to your configuration, you will need to update it accoring to the [upstream instructions](https://github.com/matrix-org/matrix-appservice-irc/blob/master/CHANGELOG.md#0150-2020-02-05). If you did not include `mappings` in your configuration for IRC, no change is necessary.  `mappings` is not part of the default configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2647
+msgid "2020-04-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2649 ../../../CHANGELOG.md:2880
+msgid "Slack bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2651
+msgid "Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the playbook now supports bridging to [Slack](https://slack.com) via the [mx-puppet-slack](https://github.com/Sorunome/mx-puppet-slack) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2653
+msgid "See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-bridge-mx-puppet-slack.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2656
+msgid "2020-04-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2658
+msgid "Skype bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2660
+msgid "Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the playbook now supports bridging to [Skype](https://www.skype.com) via the [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2662
+msgid "See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2665
+msgid "2020-04-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2667
+msgid "Private Jitsi support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2669
+msgid "The [Jitsi support](#jitsi-support) we had landed a few weeks ago was working well, but it was always open to the whole world."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2671
+msgid "Running such an open instance is not desirable to most people, so [teutat3s](https://github.com/teutat3s) has contributed support for making Jitsi use authentication."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2673
+msgid "To make your Jitsi server more private, see the [configure internal Jitsi authentication and guests mode](docs/configuring-playbook-jitsi.md#optional-configure-internal-jitsi-authentication-and-guests-mode) section in our Jitsi documentation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2676
+msgid "2020-04-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2678
+msgid "(Potential Backward Compatibility Break) ma1sd replaces mxisd"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2680
+msgid "Thanks to [Marcel Partap](https://github.com/eMPee584)'s efforts, the [mxisd](https://github.com/kamax-io/mxisd) identity server, which has been deprecated for a long time, has finally been replaced by [ma1sd](https://github.com/ma1uta/ma1sd), a compatible fork."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2682
+msgid "**If you're using the default playbook configuration**, you don't need to do anything -- your mxisd installation will be replaced with ma1sd and all existing data will be migrated automatically the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2684
+msgid "**If you're doing something more special** (defining custom `matrix_mxisd_*` variables), the playbook will ask you to rename them to `matrix_ma1sd_*`. You're also encouraged to test that ma1sd works well for such a more custom setup."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2687
+msgid "2020-03-29"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2689
+msgid "Archlinux support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2691
+msgid "Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts, the playbook now supports installing to an [Archlinux](https://www.archlinux.org/) server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2694
+msgid "2020-03-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2696
+msgid "Jitsi support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2698
+msgid "The playbook can now (optionally) install the [Jitsi](https://jitsi.org/) video-conferencing platform and integrate it with [Riot](docs/configuring-playbook-riot-web.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2700
+msgid "See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2703
+msgid "2020-03-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2705
+msgid "Raspberry Pi support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2707
+msgid "Thanks to [Gergely Horváth](https://github.com/hooger)'s effort, the playbook supports installing to a Raspberry Pi server, for at least some of the services."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2709
+msgid "Since most ready-made container images do not support that architecture, we achieve this by building images locally on the device itself. See our [Self-building documentation page](docs/self-building.md) for how to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2712
+msgid "2020-02-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2714
+msgid "Riot-web themes are here"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2716
+msgid "The playbook now makes it easy to install custom riot-web themes."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2718
+msgid "To learn more, take a look at our [riot-web documentation on Themes](docs/configuring-playbook-riot-web.md#themes)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2721
+msgid "2020-02-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2723
+msgid "Customize the server name in Riot's login page"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2725
+msgid "You can now customize the server name string that Riot-web displays in its login page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2727
+msgid "These playbook variables, with these default values, have been added:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2733
+msgid "The login page previously said \"Sign in to your Matrix account on matrix.example.org\" (the homeserver's domain name). It will now say \"Sign in … on example.org\" (the server name) by default, or \"Sign in … on Our Server\" if you set the variable to \"Our Server\"."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2735
+msgid "To support this, the config.json template is changed to use the configuration key `default_server_config` for setting the default HS/IS, and the new configuration key `server_name` is added in there."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2738
+msgid "2020-01-30"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2740
+msgid "Disabling TLSv1.1"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2742
+msgid "To improve security, we've removed TLSv1.1 support from our default matrix-nginx-proxy configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2744
+msgid "If you need to support old clients, you can re-enable it with the following configuration: `matrix_nginx_proxy_ssl_protocols: \"TLSv1.1 TLSv1.2 TLSv1.3\"`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2747
+msgid "2020-01-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2749
+msgid "Postgres collation changes (action required!)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2751
+msgid "By default, we've been using a UTF-8 collation for Postgres. This is known to cause Synapse some troubles (see the [relevant issue](https://github.com/matrix-org/synapse/issues/6722)) on systems that use [glibc](https://www.gnu.org/software/libc/). We run Postgres in an [Alpine Linux](https://alpinelinux.org/) container (which uses [musl](https://www.musl-libc.org/), and not glibc), so our users are likely not affected by the index corruption problem observed by others."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2753
+msgid "Still, we might become affected in the future. In any case, it's imminent that Synapse will complain about databases which do not use a C collation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2755
+msgid "To avoid future problems, we recommend that you run the following command:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2761
+msgid "It forces a [Postgres database upgrade](docs/maintenance-postgres.md#upgrading-postgresql), which would recreate your Postgres database using the proper (`C`) collation. If you are low on disk space, or run into trouble, refer to the Postgres database upgrade documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2764
+msgid "2020-01-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2766
+msgid "Added support for Appservice Webhooks"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2768
+msgid "Thanks to a contribution from [Björn Marten](https://github.com/tripleawwy) from [netresearch](https://www.netresearch.de/), the playbook can now install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2770
+msgid "Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-playbook-bridge-appservice-webhooks.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2773
+msgid "2020-01-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2775
+msgid "Added support for automatic Double Puppeting for all Mautrix bridges"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2777
+msgid "Double Puppeting can now be easily enabled for all Mautrix bridges supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2779
+msgid "This is possible due to those bridges' integration with [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) - yet another component that this playbook can install for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2781
+msgid "To get started, following the playbook's documentation for the bridge you'd like to configure."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2784
+msgid "2019-12-06"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2786
+msgid "Added support for an alternative method for using another webserver"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2788
+msgid "We have added support for making `matrix-nginx-proxy` not being so invasive, so that it would be easier to [use your own webserver](docs/configuring-playbook-own-webserver.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2790
+msgid "The documentation has been updated with a **Method 2**, which might make \"own webserver\" setup easier in some cases (such as [reverse-proxying using Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/296))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2792
+msgid "**Existing users** are not affected by this and **don't need to change anything**. The defaults are still the same (`matrix-nginx-proxy` obtaining SSL certificates and doing everything for you automatically)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2795
+msgid "2019-11-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2797
+msgid "Tightened security around room directory publishing"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2799
+msgid "As per this [advisory blog post](https://matrix.org/blog/2019/11/09/avoiding-unwelcome-visitors-on-private-matrix-servers), we've decided to change the default publishing rules for the Matrix room directory."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2801
+msgid "Our general goal is to favor privacy and security when running personal (family & friends) and corporate homeservers. Both of these likely benefit from having a more secure default of **not showing the room directory without authentication** and **not publishing the room directory over federation**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2803
+msgid "As with anything else, these new defaults can be overriden by changing the `matrix_synapse_allow_public_rooms_without_auth` and `matrix_synapse_allow_public_rooms_over_federation` variables, respectively."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2806
+msgid "2019-10-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2808
+msgid "Improved Postgres upgrading/importing"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2810
+msgid "Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) and [importing](docs/importing-postgres.md) have been improved to add support for multiple databases and roles."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2812
+msgid "Previously, the playbook would only take care of the `homeserver` database and `synapse` user. We now back up and restore all databases and users on the Postgres server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2814
+msgid "For now, the playbook only uses that one database (`homeserver`) and that one single user (`synapse`), so it's all the same. However, in the future, additional components besides Synapse may also make use the Postgres database server. One such example is the [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge, which strongly encourages use of Postgres in its v1.0 release. We are yet to upgrade to it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2816
+msgid "Additionally, Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) now uses gzipped dump files by default, to minimize disk space usage."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2819
+msgid "2019-10-04"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2821
+msgid "Postgres 12 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2823
+msgid "The playbook now installs [Postgres 12](https://www.postgresql.org/about/news/1976/) by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2825
+msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x, 10.x or 11.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2828
+msgid "2019-10-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2830
+msgid "Synapse 1.4.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2832
+msgid "Synapse 1.4.0 [is out](https://matrix.org/blog/2019/10/03/synapse-1-4-0-released) with lots of changes related to privacy."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2834
+msgid "Its new defaults (which we adopt as well) mean that certain old data will automatically get purged after a certain number of days. 1.4.0 automatically garbage collects redacted messages (defaults to 7 days) and removes unused IP and user agent information stored in the user_ips table (defaults to 30 days). If you'd like to preserve this data, we encourage you to look at the `redaction_retention_period` and `user_ips_max_age` options (controllable by the `matrix_synapse_redaction_retention_period` and `matrix_synapse_user_ips_max_age` playbook variables, respectively) before doing the upgrade. If you'd like to keep data indefinitely, set these variables to `null` (e.g. `matrix_synapse_redaction_retention_period: ~`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2836
+msgid "From now on the `trusted_key_servers` setting for Synapse is configurable. It still defaults to `matrix.org` just like it always has, but in a more explicit way now. If you'd like to use another trusted key server, adjust the `matrix_synapse_trusted_key_servers` playbook variable."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2838
+msgid "Synapse 1.4.0 also changes lots of things related to identity server integration. Because Synapse will now by default be responsible for validating email addresses for user accounts, running without an identity server looks more feasible. We still [have concerns](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/275/files#r331104117) over disabling the identity server by default, so for now it remains enabled."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2841
+msgid "2019-09-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2843
+msgid "Synapse Simple Antispam support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2845
+msgid "There have been lots of invite-spam attacks lately and [Travis](https://github.com/t2bot) has created a Synapse module ([synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam)) to let people protect themselves."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2847
+msgid "From now on, you can easily install and configure this spam checker module through the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2849
+msgid "Learn more in [Setting up Synapse Simple Antispam](docs/configuring-playbook-synapse-simple-antispam.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2852
+msgid "2019-08-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2854
+msgid "Extensible Riot-web configuration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2856
+msgid "Similarly to [Extensible Synapse configuration](#extensible-synapse-configuration) (below), Riot-web configuration is also extensible now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2858
+msgid "From now on, you can extend/override Riot-web's configuration by making use of the `matrix_riot_web_configuration_extension_json` variable. This should be enough for most customization needs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2860
+msgid "If you need even more power, you can now also take full control and override `matrix_riot_web_configuration_default` (or `matrix_riot_web_configuration`) directly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2862
+msgid "Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-web.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2865
+msgid "2019-08-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2867
+msgid "Extensible Synapse configuration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2869
+msgid "Previously, we had to create custom Ansible variables for each and every Synapse setting. This lead to too much effort (and configuration ugliness) to all of Synapse's settings, so naturally, not all features of Synapse could be controlled through the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2871
+msgid "From now on, you can extend/override the Synapse server's configuration by making use of the `matrix_synapse_configuration_extension_yaml` variable. This should be enough for most customization needs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2873
+msgid "If you need even more power, you can now also take full control and override `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`) directly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2875
+msgid "Learn more here in [Configuring Synapse](docs/configuring-playbook-synapse.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2878
+msgid "2019-08-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2882
+msgid "Thanks to the [great work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/205) of [kingoftheconnors](https://github.com/kingoftheconnors) and [Stuart Mumford (Cadair)](https://github.com/Cadair), the playbook now supports bridging to [Slack](https://slack.com) via the [appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2884
+msgid "Additional details are available in [Setting up Appservice Slack bridging](docs/configuring-playbook-bridge-appservice-slack.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2886
+msgid "Google Hangouts bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2888
+msgid "Thanks to the [great work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/251) of [Eduardo Beltrame (Munfred)](https://github.com/Munfred) and [Robbie D (microchipster)](https://github.com/microchipster), the playbook now supports bridging to [Google Hangouts](https://hangouts.google.com/) via the [mautrix-hangouts](https://mau.dev/tulir/mautrix-hangouts) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2890
+msgid "Additional details are available in [Setting up Mautrix Hangouts bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2893
+msgid "2019-08-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2895
+msgid "Email2Matrix support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2897
+msgid "Support for [Email2Matrix](https://github.com/devture/email2matrix) has been added."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2899
+msgid "It's an optional feature that you can enable via the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2901
+msgid "To learn more, see the [playbook's documentation on Email2Matrix](./docs/configuring-playbook-email2matrix.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2904
+msgid "2019-08-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2906
+msgid "Synapse logging level has been reduced to WARNING"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2908
+msgid "After [some discussion in our support room](https://matrix.to/#/!PukFFdIcHgtaaHZflT:devture.com/$156476852524179TBeKy:matrix.org?via=devture.com&via=matrix.org&via=librem.one), we've decided to change the default logging level for Synapse from `INFO` to `WARNING`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2910
+msgid "This greatly reduces the number of log messages that are being logged, leading to:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2912
+msgid "much less disk space dedicated to Synapse and thus, logs kept for longer"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2913
+msgid "easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages, as they're not longer buried in thousands of non-important `INFO` messages"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2915
+msgid "If you'd like to track down an issue, you [can always increase the logging level as described here](./docs/maintenance-and-troubleshooting.md#increasing-synapse-logging)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2918
+msgid "2019-07-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2920
+msgid "Synapse Maintenance docs and synapse-janitor support are available"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2922
+msgid "The playbook can now help you with Synapse's maintenance."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2924
+msgid "There's a new documentation page about [Synapse maintenance](./docs/maintenance-synapse.md) and another section on [Postgres vacuuming](./docs/maintenance-postgres.md#vacuuming-postgresql)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2926
+msgid "Among other things, if your Postgres database has grown significantly over time, you may wish to [ask the playbook to purge unused data with synapse-janitor](./docs/maintenance-synapse.md#purging-unused-data-with-synapse-janitor) for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2928
+msgid "(BC Break) Rename run control variables"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2930
+msgid "Some internal playbook control variables have been renamed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2932
+msgid "This change **only affects people who run this playbook's roles from another playbook**. If you're using this playbook as-is, you're not affected and don't need to do anything."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2934
+msgid "The following variables have been renamed:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2936
+msgid "from `run_import_postgres` to `run_postgres_import`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2937
+msgid "from `run_import_sqlite_db` to `run_postgres_import_sqlite_db`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2938
+msgid "from `run_upgrade_postgres` to `run_postgres_upgrade`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2939
+msgid "from `run_import_media_store` to `run_synapse_import_media_store`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2940
+msgid "from `run_register_user` to `run_synapse_register_user`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2941
+msgid "from `run_update_user_password` to `run_synapse_update_user_password`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2944
+msgid "2019-07-04"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2946
+msgid "Synapse no longer logs to text files"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2948
+msgid "Following what the official Synapse Docker image is doing ([#5565](https://github.com/matrix-org/synapse/pull/5565)) and what we've been doing for mostly everything installed by this playbook, **Synapse no longer logs to text files** (`/matrix/synapse/run/homeserver.log*`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2950
+msgid "From now on, Synapse would only log to console, which goes to systemd's journald. To see Synapse's logs, execute: `journalctl -fu matrix-synapse`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2952
+msgid "Because of this, the following variables have become obsolete and were removed:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2954
+msgid "`matrix_synapse_max_log_file_size_mb`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2955
+msgid "`matrix_synapse_max_log_files_count`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2957
+msgid "To prevent confusion, it'd be better if you delete all old files manually after you've upgraded (`rm -f /matrix/synapse/run/homeserver.log*`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2959
+msgid "Because Synapse is incredibly chatty when it comes to logging (here's [one such issue](https://github.com/matrix-org/synapse/issues/4751) describing the problem), if you're running an ancient distribution (like CentOS 7.0), be advised that systemd's journald default logging restrictions may not be high enough to capture all log messages generated by Synapse. This is especially true if you've got a busy (Synapse) server. We advise that you manually add `RateLimitInterval=0` and `RateLimitBurst=0` under `[Storage]` in the `/etc/systemd/journald.conf` file, followed by restarting the logging service (`systemctl restart systemd-journald`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2962
+msgid "2019-06-27"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2964
+msgid "(BC Break) Discord bridge configuration is now entirely managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2966
+msgid "Until now, the `config.yaml` file for the [Discord bridge](docs/configuring-playbook-bridge-appservice-discord.md) was managed by the playbook, but the `registration.yaml` file was not."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2968
+msgid "From now on, the playbook will keep both configuration files sync for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2970
+msgid "This means that if you were making manual changes to the `/matrix/appservice-discord/discord-registration.yaml` configuration file, those would be lost the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2972
+msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-discord/config`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2974
+msgid "Likewise, data is now also stored in a subdirectory (`/matrix/appservice-discord/data`). When you run the playbook with an existing database file (`/matrix/appservice-discord/discord.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2976
+msgid "The main directory (`/matrix/appservice-discord`) may contain some leftover files (`user-store.db`, `room-store.db`, `config.yaml`, `discord-registration.yaml`, `invite_link`). These are no longer necessary and can be deleted manually."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2978
+msgid "We're now following the default sample configuration for the Discord bridge. If you need to override some values, define them in `matrix_appservice_discord_configuration_extension_yaml`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2981
+msgid "2019-06-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2983
+msgid "(BC Break) WhatsApp bridge configuration is now entirely managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2985
+msgid "Until now, configuration files for the [WhatsApp bridge](docs/configuring-playbook-bridge-mautrix-whatsapp.md) were created by the playbook initially, but never modified later on."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2987 ../../../CHANGELOG.md:3004
+#: ../../../CHANGELOG.md:3023 ../../../CHANGELOG.md:3062
+msgid "From now on, the playbook will keep the configuration in sync for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2989
+msgid "This means that if you were making manual changes to the `/matrix/mautrix-whatsapp/config.yaml` or `/matrix/mautrix-whatsapp/registration.yaml` configuration files, those would be lost the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2991
+msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-whatsapp/config`), so your old configuration remains in the base directory (`/matrix/mautrix-whatsapp`). You need to migrate any manual changes over to the new `matrix_mautrix_whatsapp_configuration_extension_yaml` variable, so that the playbook would apply them for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2993
+msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-whatsapp/data`). When you run the playbook with an existing database file (`/matrix/mautrix-whatsapp/mautrix-whatsapp.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2995
+msgid "We're now following the default configuration for the WhatsApp bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2998
+msgid "2019-06-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3000
+msgid "(BC Break) IRC bridge configuration is now entirely managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3002
+msgid "Until now, configuration files for the [IRC bridge](docs/configuring-playbook-bridge-appservice-irc.md) were created by the playbook initially, but never modified later on."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3006
+msgid "This means that if you were making manual changes to the `/matrix/appservice-irc/config.yaml` or `/matrix/appservice-irc/registration.yaml` configuration files, those would be lost the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3008
+msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-irc/config`), so your old configuration remains in the base directory (`/matrix/appservice-irc`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3010
+msgid "Previously, we asked people to configure bridged IRC servers by extending the bridge configuration (`matrix_appservice_irc_configuration_extension_yaml`). While this is still possible and will continue working forever, **we now recommend defining IRC servers in the easier to use `matrix_appservice_irc_ircService_servers` variable**. See [our IRC bridge documentation page](docs/configuring-playbook-bridge-appservice-irc.md) for an example."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3012
+msgid "If you decide to continue using `matrix_appservice_irc_configuration_extension_yaml`, you might be interested to know that `ircService.databaseUri` and a few other keys now have default values in the base configuration (`matrix_appservice_irc_configuration_yaml`). You may wish to stop redefining those keys, unless you really intend to override them. You most likely only need to override `ircService.servers`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3014
+msgid "Bridge data (`passkey.pem` and database files) is now also stored in a subdirectory (`/matrix/appservice-irc/data`). When you run the playbook with an existing `/matrix/appservice-irc/passkey.pem` file, the playbook will stop the bridge and relocate the passkey and database files (`rooms.db` and `users.db`) to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3017
+msgid "2019-06-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3019
+msgid "(BC Break) Telegram bridge configuration is now entirely managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3021
+msgid "Until now, configuration files for the [Telegram bridge](docs/configuring-playbook-bridge-mautrix-telegram.md) were created by the playbook initially, but never modified later on."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3025
+msgid "This means that if you were making manual changes to the `/matrix/mautrix-telegram/config.yaml` or `/matrix/mautrix-telegram/registration.yaml` configuration files, those would be lost the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3027
+msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-telegram/config`), so your old configuration remains in the base directory (`/matrix/mautrix-telegram`). You need to migrate any manual changes over to the new `matrix_mautrix_telegram_configuration_extension_yaml` variable, so that the playbook would apply them for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3029
+msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-telegram/data`). When you run the playbook with an existing database file (`/matrix/mautrix-telegram/mautrix-telegram.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3031
+msgid "Also, we're now following the default configuration for the Telegram bridge, so some default configuration values are different:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3033
+msgid "`edits_as_replies` (used to be `false`, now `true`) - previously replies were not sent over to Matrix at all; ow they are sent over as a reply to the original message"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3034
+msgid "`inline_images` (used to be `true`, now `false`) - this has to do with captioned images. Inline-image (included caption) are said to exhibit troubles on Riot iOS. When `false`, the caption arrives on the Matrix side as a separate message."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3035
+msgid "`authless_portals` (used to be `false`, now `true`) - creating portals from the Telegram side is now possible"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3036
+msgid "`whitelist_group_admins` (used to be `false`, now `true`) - allows Telegram group admins to use the bot commands"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3038
+msgid "If the new values are not to your liking, use `matrix_mautrix_telegram_configuration_extension_yaml` to specify an override (refer to `matrix_mautrix_telegram_configuration_yaml` to figure out which variable goes where)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3041
+msgid "2019-06-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3043
+msgid "Synapse v1.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3045
+msgid "With [Synapse v1.0 now available](https://matrix.org/blog/2019/06/11/introducing-matrix-1-0-and-the-matrix-org-foundation) and most people being on at least Synapse v0.99, it's time to remove the `_matrix._tcp` DNS SRV record that we've been keeping for compatibility with old Synapse versions (<= 0.34)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3047
+msgid "According to the [Server Discovery specification](https://matrix.org/docs/spec/server_server/r0.1.2.html#server-discovery), it's no harm to keep the DNS SRV record. But since it's not necessary for federating with the larger Matrix network anymore, you should be safe to get rid of it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3049
+msgid "**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` DNS SRV records. The latter, **must not** be removed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3051
+msgid "For completeness, we must say that using a `_matrix._tcp` [SRV record for Server Delegation](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced) is still valid and useful for certain deployments. It's just that our guide recommends the [`/.well-known/matrix/server` Server Delegation method](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), due to its easier implementation when using this playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3053
+msgid "Besides this optional/non-urgent DNS change, assuming you're already on Synapse v0.99, upgrading to Synapse v1.0 should be as simple as [re-running the playbook](docs/maintenance-upgrading-services.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3056
+msgid "2019-06-07"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3058
+msgid "(BC Break) Facebook bridge configuration is now entirely managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3060
+msgid "Until now, configuration files for the [Facebook bridge](docs/configuring-playbook-bridge-mautrix-facebook.md) were created by the playbook initially, but never modified later on."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3064
+msgid "This means that if you were making manual changes to the `/matrix/mautrix-facebook/config.yaml` or `/matrix/mautrix-facebook/registration.yaml` configuration files, those would be lost the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3066
+msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-facebook/config`), so your old configuration remains in the base directory (`/matrix/mautrix-facebook`). You need to migrate any manual changes over to the new `matrix_mautrix_facebook_configuration_extension_yaml` variable, so that the playbook would apply them for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3068
+msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-facebook/data`). When you run the playbook with an existing database file (`/matrix/mautrix-facebook/mautrix-facebook.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3071
+msgid "2019-05-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3073
+msgid "Support for exposing container ports publicly (not just to the host)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3075
+msgid "Until now, various roles supported a `matrix_*_expose_port` variable, which would expose their container's port to the host. This was mostly useful for reverse-proxying manually (in case `matrix-nginx-proxy` was disabled). It could also be used for installing some playbook services (e.g. bridges, etc.) and wiring them to a separate (manual) Matrix setup."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3077
+msgid "`matrix_*_expose_port` variables were not granular enough - sometimes they would expose one port, other times multiple. They also didn't provide control over **where** to expose (to which port number and to which network interface), because they would usually hardcode something like `127.0.0.1:8080`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3079
+msgid "All such variables have been superseded by a better (more flexible) way to do it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3081
+msgid "**Most** people (including those not using `matrix-nginx-proxy`), **don't need** to bother with this."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3083
+msgid "Porting examples follow for people having more customized setups:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3085
+msgid "**from** `matrix_synapse_container_expose_client_api_port: true` **to** `matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3087
+msgid "**from** `matrix_synapse_container_expose_federation_api_port: true` **to** `matrix_synapse_container_federation_api_plain_host_bind_port: '127.0.0.1:8048'` and possibly `matrix_synapse_container_federation_api_tls_host_bind_port: '8448'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3089
+msgid "**from** `matrix_synapse_container_expose_metrics_port: true` **to** `matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3091
+msgid "**from** `matrix_riot_web_container_expose_port: true` **to** `matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3093
+msgid "**from** `matrix_mxisd_container_expose_port: true` **to** `matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3095
+msgid "**from** `matrix_dimension_container_expose_port: true` **to** `matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3097
+msgid "**from** `matrix_corporal_container_expose_ports: true` **to** `matrix_corporal_container_http_gateway_host_bind_port: '127.0.0.1:41080'` and possibly `matrix_corporal_container_http_api_host_bind_port: '127.0.0.1:41081'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3099
+msgid "**from** `matrix_appservice_irc_container_expose_client_server_api_port: true` **to** `matrix_appservice_irc_container_http_host_bind_port: '127.0.0.1:9999'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3101
+msgid "**from** `matrix_appservice_discord_container_expose_client_server_api_port: true` **to** `matrix_appservice_discord_container_http_host_bind_port: '127.0.0.1:9005'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3103
+msgid "As always, if you forget to remove usage of some outdated variable, the playbook will warn you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3106
+msgid "2019-05-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3108
+msgid "(BC Break) Ansible 2.8 compatibility"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3110
+msgid "Thanks to [@danbob](https://github.com/danbob), the playbook now [supports the new Ansible 2.8](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/187)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3112
+msgid "A manual change is required to the `inventory/hosts` file, changing the group name from `matrix-servers` to `matrix_servers` (dash to underscore)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3114
+msgid "To avoid doing it manually, run this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3115
+msgid "Linux: `sed -i 's/matrix-servers/matrix_servers/g' inventory/hosts`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3116
+msgid "Mac: `sed -i '' 's/matrix-servers/matrix_servers/g' inventory/hosts`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3119
+msgid "2019-05-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3121
+msgid "Synapse no longer required"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3123
+msgid "The playbook no longer insists on installing [Synapse](https://github.com/element-hq/synapse) via the `matrix-synapse` role."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3125
+msgid "If you would prefer to install Synapse another way and just use the playbook to install other services, it should be possible (`matrix_synapse_enabled: false`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3127
+msgid "Note that it won't necessarily be the best experience, since the playbook wires things to Synapse by default. If you're using your own Synapse instance (especially one not running in a container), you may have to override many variables to point them to the correct place."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3129
+msgid "Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3131
+msgid "Bridges are now separate from the Synapse role"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3133
+msgid "Bridges are no longer part of the `matrix-synapse` role. Each bridge now lives in its own separate role (`roles/custom/matrix-bridge-*`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3135
+msgid "These bridge roles are independent of the `matrix-synapse` role, so it should be possible to use them with a Synapse instance installed another way (not through the playbook)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3137
+msgid "Renaming inconsistently-named Synapse variables"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3139
+msgid "For better consistency, the following variables have been renamed:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3141
+msgid "`matrix_enable_room_list_search` was renamed to `matrix_synapse_enable_room_list_search`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3142
+msgid "`matrix_alias_creation_rules` was renamed to `matrix_synapse_alias_creation_rules`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3143
+msgid "`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was renamed to `matrix_synapse_room_list_publication_rules`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3146
+msgid "2019-05-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3148
+msgid "Besides a myriad of bug fixes and minor improvements, here are the more notable (bigger) features we can announce today."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3150
+msgid "Mautrix Facebook/Messenger bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3152
+msgid "The playbook now supports bridging with [Facebook](https://www.facebook.com/) by installing the [mautrix-facebook](https://github.com/tulir/mautrix-facebook) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3154
+msgid "Additional details are available in [Setting up Mautrix Facebook bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3156
+msgid "mxisd Registration feature integration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3158
+msgid "The playbook can now help you integrate with mxisd's [Registration](https://github.com/kamax-matrix/mxisd/blob/master/docs/features/registration.md) feature."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3160
+msgid "Learn more in [mxisd-controlled Registration](docs/configuring-playbook-mxisd.md#mxisd-controlled-registration)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3163
+msgid "2019-04-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3165
+msgid "Caddy webserver examples"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3167
+msgid "If you prefer using the [Caddy](https://caddyserver.com/) webserver instead of our own integrated nginx, we now have examples for it in the [`examples/caddy`](examples/caddy) directory"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3169
+msgid "2019-04-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3171
+msgid "Goofys support for other S3-compatible object stores"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3173
+msgid "Until now, you could optionally host Synapse's media repository on Amazon S3, but we now also support [using other S3-compatible object stores](docs/configuring-playbook-s3.md),"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3176
+msgid "2019-04-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3178
+msgid "Ansible >= 2.5 is required"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3180
+msgid "Due to recent playbook improvements and the fact that the world keeps turning, we're bumping the [version requirement for Ansible](docs/ansible.md#supported-ansible-versions) (2.4 -> 2.5)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3182
+msgid "We've also started building our own Docker image of Ansible ([devture/ansible](https://hub.docker.com/r/devture/ansible/)), which is useful for people who can't upgrade their local Ansible installation (see [Using Ansible via Docker](docs/ansible.md#using-ansible-via-docker))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3185
+msgid "2019-03-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3187
+msgid "TLS support for Coturn"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3189
+msgid "We've added TLS support to the Coturn TURN server installed by the playbook by default. The certificates from the Matrix domain will be used for the Coturn server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3191
+msgid "This feature is enabled by default for new installations. To make use of TLS support for your existing Matrix server's Coturn, make sure to rebuild both Coturn and Synapse:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3197
+msgid "People who have an extra firewall (besides the iptables firewall, which Docker manages automatically), will need to open these additional firewall ports: `5349/tcp` (TURN over TCP) and `5349/udp` (TURN over UDP)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3199
+msgid "People who build their own custom playbook from our roles should be aware that:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3201
+msgid "the `matrix-coturn` role and actually starting Coturn (e.g. `--tags=start`), requires that certificates are already put in place. For this reason, it's usually a good idea to have the `matrix-coturn` role execute after `matrix-nginx-proxy` (which retrieves the certificates)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3203
+msgid "there are a few variables that can help you enable TLS support for Coturn. See the `matrix-coturn` section in [group_vars/matrix-servers](./group_vars/matrix-servers)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3206
+msgid "2019-03-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3208
+msgid "matrix-nginx-proxy support for serving the base domain"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3210
+msgid "If you don't have a dedicated server for your base domain and want to set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), the playbook has got you covered now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3212
+msgid "It's now possible for the playbook to obtain an SSL certificate and serve the necessary files for Matrix Server Delegation on your base domain. Take a look at the new [Serving the base domain](docs/configuring-playbook-base-domain-serving.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3214
+msgid "(BC break) matrix-nginx-proxy data variable renamed"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3216
+msgid "`matrix_nginx_proxy_data_path` was renamed to `matrix_nginx_proxy_base_path`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3218
+msgid "There's a new `matrix_nginx_proxy_data_path` variable, which has a different use-purpose now (it's a subdirectory of `matrix_nginx_proxy_base_path` and is meant for storing various data files)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3221
+msgid "2019-03-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3223
+msgid "Dimension integration manager support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3225
+msgid "Thanks to [NullIsNot0](https://github.com/NullIsNot0), the playbook can now (optionally) install the [Dimension](https://dimension.t2bot.io/) integration manager. To learn more, see the [Setting up Dimension](docs/configuring-playbook-dimension.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3228
+msgid "2019-03-07"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3230
+msgid "Ability to customize mxisd's email templates"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3232
+msgid "Thanks to [Sylvia van Os](https://github.com/TheLastProject), mxisd's email templates can now be customized easily. To learn more, see the [Customizing email templates](docs/configuring-playbook-mxisd.md#customizing-email-templates) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3235
+msgid "2019-03-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3237
+msgid "Discord bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3239
+msgid "[@Lionstiger](https://github.com/Lionstiger) has done some great work adding Discord bridging support via [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord). To learn more, see the [Setting up Appservice Discord bridging](docs/configuring-playbook-bridge-appservice-discord.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3242
+msgid "2019-02-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3244
+msgid "Renaming variables"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3246 ../../../CHANGELOG.md:3563
+#: ../../../CHANGELOG.md:3648 ../../../CHANGELOG.md:3768
+msgid "The following playbook variables were renamed:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3248
+msgid "from `host_specific_hostname_identity` to `matrix_domain`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3249
+msgid "from `hostname_identity` to `matrix_domain`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3250
+msgid "from `hostname_matrix` to `matrix_server_fqn_matrix`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3251
+msgid "from `hostname_riot` to `matrix_server_fqn_riot`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3252
+msgid "from `host_specific_matrix_ssl_lets_encrypt_support_email` to `matrix_ssl_lets_encrypt_support_email`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3254
+msgid "Doing that, we've simplified things, made names less confusing (hopefully) and moved all variable names under the `matrix_` prefix."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3257
+msgid "2019-02-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3259
+msgid "Riot v1.0.1 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3261
+msgid "You can now use the brand new and redesigned Riot."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3263
+msgid "The new version no longer has a homepage by default, so we've also removed the custom homepage that we've been installing."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3265
+msgid "However, we still provide you with hooks to install your own `home.html` file by specifying the `matrix_riot_web_embedded_pages_home_path` variable (used to be called `matrix_riot_web_homepage_template` before)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3268
+msgid "2019-02-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3270
+msgid "Synapse v0.99.1"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3272
+msgid "As we're moving toward Synapse v1.0, things are beginning to stabilize. Upgrading from v0.99.0 to v0.99.1 should be painless."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3274
+msgid "If you've been overriding the default configuration so that you can terminate TLS at the Synapse side (`matrix_synapse_no_tls: false`), you'll now have to replace this custom configuration with `matrix_synapse_tls_federation_listener_enabled: true`. The `matrix_synapse_no_tls` variable is no more."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3277
+msgid "2019-02-06"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3279
+msgid "Synapse v0.99 support and preparation for Synapse v1.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3281
+msgid "Matrix is undergoing a lot of changes as it matures towards Synapse v1.0. The first step is the Synapse v0.99 transitional release, which this playbook now supports."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3283
+msgid "If you've been using this playbook successfully until now, you'd be aware that we've been doing [Server Delegation](docs/howto-server-delegation.md) using a `_matrix._tcp` DNS SRV record (as per [Configuring DNS](docs/configuring-dns.md))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3285
+msgid "Due to changes related to certificate file requirements that will affect us at Synapse v1.0, we'll have to stop using a **`_matrix._tcp` DNS SRV record in the future** (when Synapse goes to v1.0 - around 5th of March 2019). We **still need to keep the SRV record for now**, for backward compatibility with older Synapse versions (lower than v0.99)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3287
+msgid "**What you need to do now** is make use of this transitional Synapse v0.99 release to **prepare your federation settings for the future**. You have 2 choices to prepare yourself for compatibility with the future Synapse v1.0:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3289
+msgid "(recommended) set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), unless you are affected by the [Downsides of well-known-based Server Delegation](docs/howto-server-delegation.md#downsides-of-well-known-based-server-delegation). If you had previously set up the well-known `client` file, depending on how you've done it, it may be that there is nothing new required of you (besides [upgrading](docs/maintenance-upgrading-services.md)). After upgrading, you can [run a self-check](docs/maintenance-checking-services.md), which will tell you if you need to do anything extra with regard to setting up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file). After some time, when most people have upgraded to Synapse v0.99 and older releases have disappeared, be prepared to drop your `_matrix._tcp` SRV record."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3291
+msgid "(more advanced) if the [Downsides of well-known-based Server Delegation](docs/howto-server-delegation.md#downsides-of-well-known-based-server-delegation) are not to your liking, **as an alternative**, you can set up [Server Delegation via a DNS SRV record](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced). In such a case, you get to keep using your existing `_matrix._tcp` DNS SRV record forever and need to NOT set up a `/.well-known/matrix/server` file. Don't forget that you need to do certificate changes though. Follow the guide at [Server Delegation via a DNS SRV record](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3294
+msgid "2019-02-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3296
+msgid "TLS v1.3 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3298
+msgid "Now that the [nginx Docker image](https://hub.docker.com/_/nginx) has [added support for TLS v1.3](https://github.com/nginxinc/docker-nginx/issues/190), we have enabled that protocol by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3300
+msgid "When using:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3302
+msgid "the **integrated nginx server**: TLS v1.3 support might not kick in immediately, because the nginx version hasn't been bumped and you may have an older build of the nginx Docker image (currently `nginx:1.15.8-alpine`). Typically, we do not re-pull images that you already have. When the nginx version gets bumped in the future, everyone will get the update. Until then, you could manually force-pull the rebuilt Docker image by running this on the server: `docker pull nginx:1.15.8-alpine`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3304
+msgid "**your own external nginx server**: if your external nginx server is too old, the new configuration we generate for you in `/matrix/nginx-proxy/conf.d/` might not work anymore, because it mentions `TLSv1.3` and your nginx version might not support that. You can adjust the SSL protocol list by overriding the `matrix_nginx_proxy_ssl_protocols` variable. Learn more in the documentation page for [Using your own webserver, instead of this playbook's nginx proxy](docs/configuring-playbook-own-webserver.md)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3306
+msgid "**another web server**: you don't need to do anything to accommodate this change"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3309
+msgid "2019-01-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3311
+msgid "IRC bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3313
+msgid "[Devon Maloney (@Plailect)](https://github.com/Plailect) has done some great work bringing IRC bridging support via [matrix-appservice-irc](https://github.com/TeDomum/matrix-appservice-irc). To learn more, see the [Setting up Appservice IRC bridging](docs/configuring-playbook-bridge-appservice-irc.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3316
+msgid "2019-01-29"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3318
+msgid "Running container processes as non-root, without capabilities and read-only"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3320
+msgid "To improve security, this playbook no longer starts container processes as the `root` user. Most containers were dropping privileges anyway, but we were trusting them with `root` privileges until they would do that. Not anymore -- container processes now start as a non-root user (usually `matrix`) from the get-go."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3322
+msgid "For additional security, various capabilities are also dropped (see [why it's important](https://github.com/projectatomic/atomic-site/issues/203)) for all containers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3324
+msgid "Additionally, most containers now use a read-only filesystem (see [why it's important](https://www.projectatomic.io/blog/2015/12/making-docker-images-write-only-in-production/)). Containers are given write access only to the directories they need to write to."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3326
+msgid "A minor breaking change is the `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size` variable having being renamed to `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size_mb` (note the `_mb` suffix). The new variable expects a number value (e.g. `25M` -> `25`). If you weren't customizing this variable, this wouldn't affect you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3328
+msgid "matrix-mailer is now based on Exim, not Postfix"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3330
+msgid "While we would have preferred to stay with [Postfix](http://www.postfix.org/), we found out that it cannot run as a non-root user. We've had to replace it with [Exim](https://www.exim.org/) (via the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3332
+msgid "The internal `matrix-mailer` service (running in a container) now listens on port `8025` (used to be `587` before). The playbook will update your Synapse and mxisd email settings to match (`matrix-mailer:587` -> `matrix-mailer:8025`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3334
+msgid "Using the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image instead of [panubo/postfix](https://hub.docker.com/r/panubo/postfix/) also gives us a nice disk usage reduction (~200MB -> 8MB)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3337
+msgid "2019-01-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3339
+msgid "(BC Break) Making the playbook's roles more independent of one another"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3341
+msgid "The following change **affects people running a more non-standard setup** - external Postgres or using our roles in their own other playbook. **Most users don't need to do anything**, besides becoming aware of the new glue variables file [`group_vars/matrix-servers`](group_vars/matrix-servers)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3344
+msgid "Because people like using the playbook's components independently (outside of this playbook) and because it's much better for maintainability, we've continued working on separating them. Still, we'd like to offer a turnkey solution for running a fully-featured Matrix server, so this playbook remains important for wiring up the various components."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3346
+msgid "With the new changes, **all roles are now only dependent on the minimal `matrix-base` role**. They are no longer dependent among themselves."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3348
+msgid "In addition, the following components can now be completely disabled (for those who want/need to):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3349
+msgid "`matrix-coturn` by using `matrix_coturn_enabled: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3350
+msgid "`matrix-mailer` by using `matrix_mailer_enabled: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3351
+msgid "`matrix-postgres` by using `matrix_postgres_enabled: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3353
+msgid "The following changes had to be done:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3355
+msgid "glue variables had to be introduced to the playbook, so it can wire together the various components. Those glue vars are stored in the [`group_vars/matrix-servers`](group_vars/matrix-servers) file. When overriding variables for a given component (role), you need to be aware of both the role defaults (`role/ROLE/defaults/main.yml`) and the role's corresponding section in the [`group_vars/matrix-servers`](group_vars/matrix-servers) file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3357
+msgid "`matrix_postgres_use_external` has been superceeded by the more consistently named `matrix_postgres_enabled` variable and a few other `matrix_synapse_database_` variables. See the [Using an external PostgreSQL server (optional)](docs/configuring-playbook-external-postgres.md) documentation page for an up-to-date replacement."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3359
+msgid "Postgres tools (`matrix-postgres-cli` and `matrix-make-user-admin`) are no longer installed if you're not enabling the `matrix-postgres` role (`matrix_postgres_enabled: false`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3361
+msgid "roles, being more independent now, are more minimal and do not do so much magic for you. People that are building their own playbook using our roles will definitely need to take a look at the [`group_vars/matrix-servers`](group_vars/matrix-servers) file and adapt their playbooks with the same (or similar) wiring logic."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3364
+msgid "2019-01-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3366
+msgid "Splitting the playbook into multiple roles"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3368
+msgid "For better maintainability, the playbook logic (which all used to reside in a single `matrix-server` role) has been split out into a number of different roles: `matrix-synapse`, `matrix-postgres`, `matrix-riot-web`, `matrix-mxisd`, etc. (see the `roles/` directory)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3371
+msgid "To keep the filesystem more consistent with this separation, the **Postgres data had to be relocated**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3373
+msgid "The default value of `matrix_postgres_data_path` was changed from `/matrix/postgres` to `/matrix/postgres/data`. The `/matrix/postgres` directory is what we consider a base path now (new variable `matrix_postgres_base_path`). **Your Postgres data files will automatically be relocated by the playbook** (`/matrix/postgres/*` -> `/matrix/postgres/data/`) when you run with `--tags=setup-all` (or `--tags=setup-postgres`). While this shouldn't cause data-loss, **it's better if you do a Postgres backup just in case**. You'd need to restart all services after this migration (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3376
+msgid "2019-01-11"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3378
+msgid "(BC Break) mxisd configuration changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3380
+msgid "To be more flexible and to support the upcoming [mxisd](https://github.com/kamax-io/mxisd) 1.3.0 (when it gets released), we've had to redo how mxisd gets configured."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3383
+msgid "The following variables are no longer supported by this playbook:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3385
+msgid "`matrix_mxisd_ldap_enabled`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3386
+msgid "`matrix_mxisd_ldap_connection_host`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3387
+msgid "`matrix_mxisd_ldap_connection_tls`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3388
+msgid "`matrix_mxisd_ldap_connection_port`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3389
+msgid "`matrix_mxisd_ldap_connection_baseDn`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3390
+msgid "`matrix_mxisd_ldap_connection_baseDns`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3391 ../../../CHANGELOG.md:3392
+msgid "`matrix_mxisd_ldap_connection_bindDn`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3393 ../../../CHANGELOG.md:3397
+msgid "`matrix_mxisd_ldap_connection_bindPassword`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3394
+msgid "`matrix_mxisd_ldap_filter`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3395
+msgid "`matrix_mxisd_ldap_attribute_uid_type`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3396
+msgid "`matrix_mxisd_ldap_attribute_uid_value`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3398
+msgid "`matrix_mxisd_ldap_attribute_name`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3399
+msgid "`matrix_mxisd_ldap_attribute_threepid_email`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3400
+msgid "`matrix_mxisd_ldap_attribute_threepid_msisdn`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3401
+msgid "`matrix_mxisd_ldap_identity_filter`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3402
+msgid "`matrix_mxisd_ldap_identity_medium`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3403
+msgid "`matrix_mxisd_ldap_auth_filter`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3404
+msgid "`matrix_mxisd_ldap_directory_filter`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3405
+msgid "`matrix_mxisd_template_config`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3407
+msgid "You are encouraged to use the `matrix_mxisd_configuration_extension_yaml` variable to define your own mxisd configuration additions and overrides. Refer to the [default variables file](roles/custom/matrix-mxisd/defaults/main.yml) for more information."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3409
+msgid "This new way of configuring mxisd is beneficial because:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3411
+msgid "it lets us support all mxisd configuration options, as the playbook simply forwards them to mxisd without needing to care or understand them"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3412
+msgid "it lets you upgrade to newer mxisd versions and make use of their features, without us having to add support for them explicitly"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3415
+msgid "2019-01-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3417
+msgid "(BC Break) Cronjob schedule no longer configurable"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3419
+msgid "Due to the way we manage cronjobs now, you can no longer configure the schedule they're invoked at."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3421
+msgid "If you were previously using `matrix_ssl_lets_encrypt_renew_cron_time_definition` or `matrix_nginx_proxy_reload_cron_time_definition` to set a custom schedule, you should note that these variables don't affect anything anymore."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3424
+msgid "If you miss this functionality, please [open an Issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/new) and let us know about your use case!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3427
+msgid "2018-12-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3429
+msgid "(BC Break) More SSL certificate retrieval methods"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3431
+msgid "The playbook now lets you decide between 3 different SSL certificate retrieval methods:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3432
+msgid "(default) obtaining free SSL certificates from Let's Encrypt"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3433
+msgid "generating self-signed SSL certificates"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3434
+msgid "managing SSL certificates manually"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3436
+msgid "Learn more in [Adjusting SSL certificate retrieval](docs/configuring-playbook-ssl-certificates.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3438
+msgid "For people who use Let's Encrypt (mostly everyone, since it's the default), you'll also have to rename a variable in your configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3440
+msgid "before: `host_specific_matrix_ssl_support_email`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3441
+msgid "after: `host_specific_matrix_ssl_lets_encrypt_support_email`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3443
+msgid "(BC Break) mxisd upgrade with multiple base DN support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3445
+msgid "mxisd has bee upgraded to [version 1.2.2](https://github.com/kamax-matrix/mxisd/releases/tag/v1.2.2), which supports [multiple base DNs](https://github.com/kamax-matrix/mxisd/blob/v1.2.2/docs/stores/ldap.md#base)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3447
+msgid "If you were configuring this playbook's `matrix_mxisd_ldap_connection_baseDn` variable until now (a string containing a single base DN), you'll need to change to configuring the `matrix_mxisd_ldap_connection_baseDns` variable (an array containing multiple base DNs)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3449
+msgid "Example change:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3451
+msgid "before: `matrix_mxisd_ldap_connection_baseDn: OU=Users,DC=example,DC=org`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3452
+msgid "after: `matrix_mxisd_ldap_connection_baseDns: ['OU=Users,DC=example,DC=org']`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3455
+msgid "2018-12-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3457
+msgid "Synapse 0.34.0 and Python 3"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3459
+msgid "Synapse has been upgraded to 0.34.0 and now uses Python 3. Based on feedback from others, running Synapse on Python 3 is supposed to decrease memory usage significantly (~2x)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3462
+msgid "2018-12-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3464
+msgid "Riot homepage customization"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3466
+msgid "You can now customize some parts of the Riot homepage (or even completely replace it with your own custom page). See the `matrix_riot_web_homepage_` variables in `roles/custom/matrix-riot-web/defaults/main.yml`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3469
+msgid "2018-12-04"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3471
+msgid "mxisd extensibility"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3473
+msgid "The [LDAP identity store for mxisd](https://github.com/kamax-matrix/mxisd/blob/master/docs/stores/ldap.md) can now be configured easily using playbook variables (see the `matrix_mxisd_ldap_` variables in `roles/custom/matrix-server/defaults/main.yml`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3476
+msgid "2018-11-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3478
+msgid "More scripts"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3480
+msgid "matrix-remove-all allows to uninstall everything with a single command"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3481
+msgid "matrix-make-user-admin allows to upgrade a user's privileges"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3483
+msgid "LDAP auth support via matrix-synapse-ldap3"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3485
+msgid "The playbook can now install and configure [LDAP auth support](https://github.com/matrix-org/matrix-synapse-ldap3) for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3487
+msgid "Additional details are available in [Setting up the LDAP authentication password provider module](docs/configuring-playbook-ldap-auth.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3490
+msgid "2018-11-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3492
+msgid "Support for controlling public registration and room auto-join"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3494
+msgid "The playbook now lets you enable public registration for users (controlled via `matrix_synapse_enable_registration`). By default, public registration is forbidden."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3496
+msgid "You can also make people automatically get auto-joined to rooms (controlled via `matrix_synapse_auto_join_rooms`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3498
+msgid "Support for changing the welcome user ID (welcome bot)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3500
+msgid "By default, `@riot-bot:matrix.org` is used to welcome newly registered users. This can be changed to something else (or disabled) via the new `matrix_riot_web_welcome_user_id` variable."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3503
+msgid "2018-11-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3505
+msgid "Ability to set Synapse log levels"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3507
+msgid "The playbook now allows you to set the log levels used by Synapse. The default logging levels remain the same."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3509
+msgid "You can now override following variables with any of the supported log levels listed here: https://docs.python.org/3/library/logging.html#logging-levels"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3518
+msgid "2018-11-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3520
+msgid "Customize parts of Riot's config"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3522
+msgid "You can now customize some parts of Riot's `config.json`. These playbook variables, with these default values, have been added:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3533
+msgid "This now allows you use a custom integration manager like [Dimension](https://dimension.t2bot.io). For example, if you wish to use the Dimension instance hosted at dimension.t2bot.io, you can set the following in your vars.yml file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3542
+msgid "SSL protocols used to serve Riot and Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3544
+msgid "There's now a new `matrix_nginx_proxy_ssl_protocols` playbook variable, which controls the SSL protocols used to serve Riot and Synapse. Its default value is `TLSv1.1 TLSv1.2`. This playbook previously used `TLSv1 TLSv1.1 TLSv1.2` to serve Riot and Synapse."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3546
+msgid "You may wish to reenable TLSv1 if you need to access Riot in older browsers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3548
+msgid "Note: Currently the dockerized nginx doesn't support TLSv1.3. See https://github.com/nginxinc/docker-nginx/issues/190 for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3551
+msgid "2018-11-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3553
+msgid "Postgres 11 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3555
+msgid "The playbook now installs [Postgres 11](https://www.postgresql.org/about/news/1894/) by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3557
+msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x or 10.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3559 ../../../CHANGELOG.md:3646
+#: ../../../CHANGELOG.md:3766
+msgid "(BC Break) Renaming playbook variables"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3561
+msgid "Due to the large amount of features added to this playbook lately, to keep things manageable we've had to reorganize its configuration variables a bit."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3565
+msgid "from `matrix_docker_image_mxisd` to `matrix_mxisd_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3566
+msgid "from `matrix_docker_image_mautrix_telegram` to `matrix_mautrix_telegram_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3567
+msgid "from `matrix_docker_image_mautrix_whatsapp` to `matrix_mautrix_whatsapp_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3568
+msgid "from `matrix_docker_image_mailer` to `matrix_mailer_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3569
+msgid "from `matrix_docker_image_coturn` to `matrix_coturn_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3570
+msgid "from `matrix_docker_image_goofys` to `matrix_s3_goofys_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3571
+msgid "from `matrix_docker_image_riot` to `matrix_riot_web_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3572
+msgid "from `matrix_docker_image_nginx` to `matrix_nginx_proxy_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3573
+msgid "from `matrix_docker_image_synapse` to `matrix_synapse_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3574
+msgid "from `matrix_docker_image_postgres_v9` to `matrix_postgres_docker_image_v9`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3575
+msgid "from `matrix_docker_image_postgres_v10` to `matrix_postgres_docker_image_v10`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3576
+msgid "from `matrix_docker_image_postgres_latest` to `matrix_postgres_docker_image_latest`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3579
+msgid "2018-10-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3581
+msgid "Mautrix Whatsapp bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3583
+msgid "The playbook now supports bridging with [Whatsapp](https://www.whatsapp.com/) by installing the [mautrix-whatsapp](https://github.com/tulir/mautrix-whatsapp) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3585
+msgid "Additional details are available in [Setting up Mautrix Whatsapp bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3588
+msgid "2018-10-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3590
+msgid "Support for controlling Matrix federation"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3592
+msgid "The playbook can now help you with [Controlling Matrix federation](docs/configuring-playbook-federation), should you wish to run a more private (isolated) server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3595
+msgid "2018-10-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3597
+msgid "Disabling riot-web guests"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3599
+msgid "From now on, Riot's configuration setting `disable_guests` would be set to `true`. The homeserver was rejecting guests anyway, so this is just a cosmetic change affecting Riot's UI."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3602
+msgid "2018-10-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3604
+msgid "Self-check maintenance command"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3606
+msgid "The playbook can now [check if services are configured correctly](docs/maintenance-checking-services.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3609
+msgid "2018-10-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3611
+msgid "Presence tracking made configurable"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3613
+msgid "The playbook can now enable/disable user presence-status tracking in Synapse, through the playbook's `matrix_synapse_use_presence` variable (having a default value of `true` - enabled)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3615
+msgid "If users participate in large rooms with many other servers, disabling presence will decrease server load significantly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3618
+msgid "2018-09-27"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3620
+msgid "Synapse Cache Factor made configurable"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3622
+msgid "The playbook now makes the Synapse cache factor configurable, through the playbook's `matrix_synapse_cache_factor` variable (having a default value of `0.5`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3624
+msgid "Changing that value allows you to potentially decrease RAM usage or to increase performance by caching more stuff. Some information on it is available here: https://github.com/element-hq/synapse#help-synapse-eats-all-my-ram"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3627
+msgid "2018-09-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3629
+msgid "Disabling Docker container logging"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3631
+msgid "`--log-driver=none` is used for all Docker containers now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3633
+msgid "All these containers are started through systemd anyway and get logged in journald, so there's no need for Docker to be logging the same thing using the default `json-file` driver. Doing that was growing `/var/lib/docker/containers/..` infinitely until service/container restart."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3635
+msgid "As a result of this, things like `docker logs matrix-synapse` won't work anymore. `journalctl -u matrix-synapse` is how one can see the logs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3638
+msgid "2018-09-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3640
+msgid "Service discovery support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3642
+msgid "The playbook now helps you set up [service discovery](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery) using a `/.well-known/matrix/client` file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3644
+msgid "Additional details are available in [Configuring service discovery via .well-known](docs/configuring-well-known.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3650
+msgid "from `matrix_nginx_riot_web_data_path` to `matrix_riot_web_data_path`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3651
+msgid "from `matrix_riot_web_default_identity_server_url` to `matrix_identity_server_url`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3654
+msgid "2018-09-07"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3656
+msgid "Mautrix Telegram bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3658
+msgid "The playbook now supports bridging with [Telegram](https://telegram.org/) by installing the [mautrix-telegram](https://github.com/tulir/mautrix-telegram) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3660
+msgid "Additional details are available in [Setting up Mautrix Telegram bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3662
+msgid "Events cache size increase and configurability for Matrix Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3664
+msgid "The playbook now lets you configure Matrix Synapse's `event_cache_size` configuration via the `matrix_synapse_event_cache_size` playbook variable."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3666
+msgid "Previously, this value was hardcoded to `\"10K\"`. From now on, a more reasonable default of `\"100K\"` is used."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3668
+msgid "Password-peppering support for Matrix Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3670
+msgid "The playbook now supports enabling password-peppering for increased security in Matrix Synapse via the `matrix_synapse_password_config_pepper` playbook variable. Using a password pepper is disabled by default (just like it used to be before this playbook variable got introduced) and is not to be enabled/disabled after initial setup, as that would invalidate all existing passwords."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3672
+msgid "Statistics-reporting support for Matrix Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3674
+msgid "There's now a new `matrix_synapse_report_stats` playbook variable, which controls the `report_stats` configuration option for Matrix Synapse. It defaults to `false`, so no change is required to retain your privacy."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3676
+msgid "If you'd like to start reporting statistics about your homeserver (things like number of users, number of messages sent, uptime, load, etc.) to matrix.org, you can turn on stats reporting."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3679
+msgid "2018-08-29"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3681
+msgid "Changing the way SSL certificates are retrieved"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3683
+msgid "We've been using [acmetool](https://github.com/hlandau/acme) (with the [willwill/acme-docker](https://hub.docker.com/r/willwill/acme-docker/) Docker image) until now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3685
+msgid "Due to the Docker image being deprecated, and things looking bleak for acmetool's support of the newer ACME v2 API endpoint, we've switched to using [certbot](https://certbot.eff.org/) (with the [certbot/certbot](https://hub.docker.com/r/certbot/certbot/) Docker image)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3687
+msgid "Simply re-running the playbook will retrieve new certificates (via certbot) for you. To ensure you don't leave any old files behind, though, you'd better do this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3689
+msgid "`systemctl stop 'matrix*'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3690
+msgid "stop your custom webserver, if you're running one (only affects you if you've installed with `matrix_nginx_proxy_enabled: false`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3691
+msgid "`mv /matrix/ssl /matrix/ssl-acmetool-delete-later`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3692
+msgid "re-run the playbook's [installation](docs/installing.md)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3693
+msgid "possibly delete `/matrix/ssl-acmetool-delete-later`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3696
+msgid "2018-08-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3698
+msgid "Matrix Corporal support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3700
+msgid "The playbook can now install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3702
+msgid "Additional details are available in [Setting up Matrix Corporal](docs/configuring-playbook-matrix-corporal.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3705
+msgid "2018-08-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3707
+msgid "Matrix Synapse rate limit control variables"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3709
+msgid "The following new variables can now be configured to control Matrix Synapse's rate-limiting (default values are shown below)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3716
+msgid "Shared Secret Auth support via matrix-synapse-shared-secret-auth"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3718
+msgid "The playbook can now install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3720
+msgid "Additional details are available in [Setting up the Shared Secret Auth password provider module](docs/configuring-playbook-shared-secret-auth.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3723
+msgid "2018-08-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3725
+msgid "REST auth support via matrix-synapse-rest-auth"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3727
+msgid "The playbook can now install and configure [matrix-synapse-rest-auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3729
+msgid "Additional details are available in [Setting up the REST authentication password provider module](docs/configuring-playbook-rest-auth.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3731
+msgid "Compression improvements"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3733
+msgid "Shifted Matrix Synapse compression from happening in the Matrix Synapse, to happening in the nginx proxy that's in front of it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3736
+msgid "Additionally, `riot-web` also gets compressed now (in the nginx proxy), which drops the initial page load's size from 5.31MB to 1.86MB."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3739
+msgid "Disabling some unnecessary Synapse services"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3741
+msgid "The following services are not necessary, so they have been disabled:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3742
+msgid "on the federation port (8448): the `client` service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3743
+msgid "on the http port (8008, exposed over 443): the old Angular `webclient` and the `federation` service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3745
+msgid "Federation runs only on the federation port (8448) now. The Client APIs run only on the http port (8008) now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3748
+msgid "2018-08-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3750
+msgid "mxisd Identity Server support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3752
+msgid "The playbook now sets up an [mxisd](https://github.com/kamax-io/mxisd) Identity Server for you by default. Additional details are available in [Setting up ma1sd Identity Server](docs/configuring-playbook-mxisd.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3755
+msgid "2018-08-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3757
+msgid "Email-sending support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3759
+msgid "The playbook now configures an email-sending service (postfix) by default. Additional details are available in [Adjusting email-sending settings](docs/configuring-playbook-email.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3761
+msgid "With this, Matrix Synapse is able to send email notifications for missed messages, etc."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3764
+msgid "2018-08-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3770
+msgid "from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3771
+msgid "from `matrix_max_log_file_size_mb` to `matrix_synapse_max_log_file_size_mb`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3772
+msgid "from `matrix_max_log_files_count` to `matrix_synapse_max_log_files_count`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3773
+msgid "from `docker_matrix_image` to `matrix_docker_image_synapse`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3774
+msgid "from `docker_nginx_image` to `matrix_docker_image_nginx`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3775
+msgid "from `docker_riot_image` to `matrix_docker_image_riot`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3776
+msgid "from `docker_goofys_image` to `matrix_docker_image_goofys`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3777
+msgid "from `docker_coturn_image` to `matrix_docker_image_coturn`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3779
+msgid "If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3781
+msgid "Renaming Ansible playbook tag"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3783
+msgid "The command for executing the whole playbook has changed. The `setup-main` tag got renamed to `setup-all`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3785
+msgid "Docker container linking"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3787
+msgid "Changed the way the Docker containers are linked together. The ones that need to communicate with others operate in a `matrix` network now and not in the default bridge network."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/README.po b/i18n/locales/jp/LC_MESSAGES/README.po
new file mode 100644
index 000000000..7d8aa909d
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/README.po
@@ -0,0 +1,1181 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../README.md:1
+msgid "[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)"
+msgstr ""
+
+#: ../../../README.md:1
+msgid "Support room on Matrix"
+msgstr ""
+
+#: ../../../README.md:1
+msgid "donate"
+msgstr ""
+
+#: ../../../README.md:3
+msgid "Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker"
+msgstr ""
+
+#: ../../../README.md:5
+msgid "🎯 Purpose"
+msgstr ""
+
+#: ../../../README.md:7
+msgid "This [Ansible](https://www.ansible.com/) playbook is meant to help you run your own [Matrix](http://matrix.org/) homeserver, along with the [various services](#supported-services) related to that."
+msgstr "この [Ansible](https://www.ansible.com/) Playbook は、独自の [Matrix](http://matrix.org/) ホームサーバーと、それに関連する [さまざまなサービス](#supported-services) を実行するのに役立つことを目的としています。"
+
+#: ../../../README.md:9
+msgid "That is, it lets you join the Matrix network using your own user ID like `@alice:example.com`, all hosted on your own server (see [prerequisites](docs/prerequisites.md))."
+msgstr ""
+
+#: ../../../README.md:11
+msgid "We run all [supported services](#-supported-services) in [Docker](https://www.docker.com/) containers (see [the container images we use](docs/container-images.md)), which lets us have a predictable and up-to-date setup, across multiple supported distros (see [prerequisites](docs/prerequisites.md)) and [architectures](docs/alternative-architectures.md) (x86/amd64 being recommended)."
+msgstr ""
+
+#: ../../../README.md:13
+msgid "Installation (upgrades) and some maintenance tasks are automated using [Ansible](https://www.ansible.com/) (see [our Ansible guide](docs/ansible.md))."
+msgstr ""
+
+#: ../../../README.md:15
+msgid "☁ Self-hosting or Managed / SaaS"
+msgstr ""
+
+#: ../../../README.md:17
+msgid "This Ansible playbook tries to make self-hosting and maintaining a Matrix server fairly easy (see [Getting started](#-getting-started)). Still, running any service smoothly requires knowledge, time and effort."
+msgstr ""
+
+#: ../../../README.md:19
+msgid "If you like the [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) spirit of this Ansible playbook, but prefer to put the responsibility on someone else, you can also [get a managed Matrix server from etke.cc](https://etke.cc?utm_source=github&utm_medium=readme&utm_campaign=mdad) (both hosting and on-premises) - a service built on top of this Ansible playbook but with [additional components](https://etke.cc/help/extras/?utm_source=github&utm_medium=readme&utm_campaign=mdad) and [services](https://etke.cc/services/?utm_source=github&utm_medium=readme&utm_campaign=mdad) which all help you run a Matrix server with ease. Be advised that etke.cc operates on a subscription-based approach and there is no \"just set up my server once and be done with it\" option."
+msgstr ""
+
+#: ../../../README.md:21
+msgid "🚀 Getting started"
+msgstr ""
+
+#: ../../../README.md:23
+msgid "We have detailed documentation in the [docs/](./docs) directory - see the Table of Contents in the [documentation README](./docs/README.md)."
+msgstr ""
+
+#: ../../../README.md:25
+msgid "While the [list of supported services](#-supported-services) and documentation is very extensive, you don't need to read through everything. We recommend:"
+msgstr ""
+
+#: ../../../README.md:27
+msgid "Starting with the basics. You can always add/remove or tweak services later on."
+msgstr ""
+
+#: ../../../README.md:29
+msgid "Following our installation guide. There are two guides available for beginners and advanced users:"
+msgstr ""
+
+#: ../../../README.md:31
+msgid "⚡ **[Quick start](./docs/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 ""
+
+#: ../../../README.md:33
+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](./docs/prerequisites.md)** documentation page."
+msgstr ""
+
+#: ../../../README.md:35
+msgid "If you experience an issue on configuring the playbook, setting up your server, maintaining services on it, etc., please take a look at our [FAQ](./docs/faq.md). If you cannot find an answer to your question, feel free to ask for [help and support](#-support)."
+msgstr ""
+
+#: ../../../README.md:37
+msgid "✔ Supported services"
+msgstr ""
+
+#: ../../../README.md:39
+msgid "Using this playbook, you can get the following list of services configured on your server. Basically, this playbook aims to get you up-and-running with all the necessities around Matrix, without you having to do anything else."
+msgstr ""
+
+#: ../../../README.md:41
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../README.md:43
+msgid "The list below is exhaustive. It includes optional or even some advanced components that you will most likely not need. Sticking with the defaults (which install a subset of the above components) is the best choice, especially for a new installation. You can always re-run the playbook later to add or remove components."
+msgstr ""
+
+#: ../../../README.md:45
+msgid "Deprecated or unmaintained services are not listed. You can find documentations for them [here](docs/configuring-playbook.md#deprecated--unmaintained--removed-services)."
+msgstr ""
+
+#: ../../../README.md:47
+msgid "Homeserver"
+msgstr ""
+
+#: ../../../README.md:49
+msgid "The homeserver is the backbone of your Matrix system. Choose one from the following list."
+msgstr ""
+
+#: ../../../README.md
+msgid "Name"
+msgstr ""
+
+#: ../../../README.md
+msgid "Default?"
+msgstr ""
+
+#: ../../../README.md
+msgid "Description"
+msgstr ""
+
+#: ../../../README.md
+msgid "Documentation"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Synapse](https://github.com/element-hq/synapse)"
+msgstr ""
+
+#: ../../../README.md
+msgid "✅"
+msgstr ""
+
+#: ../../../README.md
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-synapse.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Conduit](https://conduit.rs)"
+msgstr ""
+
+#: ../../../README.md
+msgid "❌"
+msgstr ""
+
+#: ../../../README.md
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-conduit.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Dendrite](https://github.com/matrix-org/dendrite)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-dendrite.md)"
+msgstr ""
+
+#: ../../../README.md:57
+msgid "Clients"
+msgstr ""
+
+#: ../../../README.md:59
+msgid "Web clients for Matrix that you can host on your own domains."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Element Web](https://github.com/element-hq/element-web)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Default Matrix web client, configured to connect to your own Synapse server"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-client-element-web.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Hydrogen](https://github.com/element-hq/hydrogen-web)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Lightweight Matrix client with legacy and mobile browser support"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-client-hydrogen.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Cinny](https://github.com/ajbura/cinny)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Simple, elegant and secure web client"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-client-cinny.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[SchildiChat Web](https://schildi.chat/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Based on Element Web, with a more traditional instant messaging experience"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-client-schildichat-web.md)"
+msgstr ""
+
+#: ../../../README.md:68
+msgid "Server Components"
+msgstr ""
+
+#: ../../../README.md:70
+msgid "Services that run on the server to make the various parts of your installation work."
+msgstr ""
+
+#: ../../../README.md
+msgid "[PostgreSQL](https://www.postgresql.org/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Database for Synapse. [Using an external PostgreSQL server](docs/configuring-playbook-external-postgres.md) is also possible."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-external-postgres.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Coturn](https://github.com/coturn/coturn)"
+msgstr ""
+
+#: ../../../README.md
+msgid "STUN/TURN server for WebRTC audio/video calls"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-turn.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Traefik](https://doc.traefik.io/traefik/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](docs/configuring-playbook-own-webserver.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-traefik.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Let's Encrypt](https://letsencrypt.org/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Free SSL certificate, which secures the connection to all components"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-ssl-certificates.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Exim](https://www.exim.org/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-email.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[ma1sd](https://github.com/ma1uta/ma1sd)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Matrix Identity Server"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-ma1sd.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[ddclient](https://github.com/linuxserver/docker-ddclient)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Dynamic DNS"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-dynamic-dns.md)"
+msgstr ""
+
+#: ../../../README.md:82
+msgid "Authentication"
+msgstr ""
+
+#: ../../../README.md:84
+msgid "Extend and modify how users are authenticated on your homeserver."
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) (advanced)"
+msgstr ""
+
+#: ../../../README.md
+msgid "REST authentication password provider module"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-rest-auth.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) (advanced)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Password provider module"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-shared-secret-auth.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) (advanced)"
+msgstr ""
+
+#: ../../../README.md
+msgid "LDAP Auth password provider module"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-ldap-auth.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) (advanced)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A proxy that handles Matrix registration requests and forwards them to LDAP."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-matrix-ldap-registration-proxy.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-registration](https://github.com/ZerataX/matrix-registration)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A simple python application to have a token based Matrix registration"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-matrix-registration.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (UVS)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Service to verify details of a user based on an Open ID token"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-user-verification-service.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) (advanced)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A spam checker module"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-synapse-simple-antispam.md)"
+msgstr ""
+
+#: ../../../README.md:96
+msgid "File Storage"
+msgstr ""
+
+#: ../../../README.md:98
+msgid "Use alternative file storage to the default `media_store` folder."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Goofys](https://github.com/kahing/goofys)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-s3-goofys.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-s3.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-media-repo](https://github.com/turt2live/matrix-media-repo)"
+msgstr ""
+
+#: ../../../README.md
+msgid "matrix-media-repo is a 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 ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-matrix-media-repo.md)"
+msgstr ""
+
+#: ../../../README.md:106
+msgid "Bridges"
+msgstr ""
+
+#: ../../../README.md:108
+msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-discord](https://github.com/mautrix/discord)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Discord](https://discord.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-discord.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-slack](https://github.com/mautrix/slack)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Slack](https://slack.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-slack.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-telegram](https://github.com/mautrix/telegram)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Telegram](https://telegram.org/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-telegram.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-gmessages](https://github.com/mautrix/gmessages)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Google Messages](https://messages.google.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-gmessages.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-whatsapp](https://github.com/mautrix/whatsapp)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [WhatsApp](https://www.whatsapp.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-whatsapp.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-wsproxy](https://github.com/mautrix/wsproxy)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to Android SMS or Apple iMessage"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-wsproxy.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-twitter](https://github.com/mautrix/twitter)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Twitter](https://twitter.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-twitter.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-googlechat](https://github.com/mautrix/googlechat)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-googlechat.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-meta](https://github.com/mautrix/instagram)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Link for [Messenger](docs/configuring-playbook-bridge-mautrix-meta-messenger.md) / [Instagram](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mautrix-signal](https://github.com/mautrix/signal)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Signal](https://www.signal.org/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-signal.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[beeper-linkedin](https://github.com/beeper/linkedin)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [LinkedIn](https://www.linkedin.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-beeper-linkedin.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-appservice-irc.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-appservice-kakaotalk.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Discord](https://discordapp.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-appservice-discord.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-appservice-slack.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-hookshot](https://github.com/matrix-org/matrix-hookshot)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-hookshot.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to SMS"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-matrix-bridge-sms.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-wechat](https://github.com/duo/matrix-wechat)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [WeChat](https://www.wechat.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-wechat.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Heisenbridge](https://github.com/hifi/heisenbridge)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-heisenbridge.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[go-skype-bridge](https://github.com/kelaresg/go-skype-bridge)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Skype](https://www.skype.com)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-go-skype-bridge.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Slack](https://slack.com)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-slack.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-instagram.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-twitter.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-discord.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [GroupMe](https://groupme.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-groupme.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Steam](https://steamapp.com/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-steam.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Email2Matrix](https://github.com/devture/email2matrix)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge for relaying emails to Matrix rooms"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-email2matrix.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Postmoogle](https://github.com/etkecc/postmoogle)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Email to Matrix bridge"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-postmoogle.md)"
+msgstr ""
+
+#: ../../../README.md:141
+msgid "Bots"
+msgstr ""
+
+#: ../../../README.md:143
+msgid "Bots provide various additional functionality to your installation."
+msgstr ""
+
+#: ../../../README.md
+msgid "[baibot](https://github.com/etkecc/baibot)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bot-baibot.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bot for scheduling one-off & recurring reminders and alarms"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bot-matrix-reminder-bot.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bot for invitations by creating and managing registration tokens"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bot-matrix-registration-bot.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[maubot](https://github.com/maubot/maubot)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A plugin-based Matrix bot system"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bot-maubot.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Honoroit](https://github.com/etkecc/honoroit)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A helpdesk bot"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bot-honoroit.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Mjolnir](https://github.com/matrix-org/mjolnir)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A moderation tool for Matrix"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bot-mjolnir.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Draupnir](https://github.com/the-draupnir-project/Draupnir)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A moderation tool for Matrix (Fork of Mjolnir)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bot-draupnir.md) (for [appservice mode](docs/configuring-playbook-appservice-draupnir-for-all.md))"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Buscarron](https://github.com/etkecc/buscarron)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Web forms (HTTP POST) to Matrix"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bot-buscarron.md)"
+msgstr ""
+
+#: ../../../README.md:156
+msgid "Administration"
+msgstr ""
+
+#: ../../../README.md:158
+msgid "Services that help you in administrating and monitoring your Matrix installation."
+msgstr ""
+
+#: ../../../README.md
+msgid "[matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-alertmanager-receiver.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "OAuth 2.0 and OpenID Provider server"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-matrix-authentication-service.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[synapse-admin](https://github.com/etkecc/synapse-admin)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A web UI tool for administrating users and rooms on your Matrix server"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-synapse-admin.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Metrics and Graphs"
+msgstr ""
+
+#: ../../../README.md
+msgid "Consists of the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI, with [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) being available too"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-nginxlog.md))"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Borg](https://borgbackup.org)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Backups"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-backup-borg.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[rageshake](https://github.com/matrix-org/rageshake)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bug report server"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-rageshake.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-synapse-usage-exporter.md)"
+msgstr ""
+
+#: ../../../README.md:170
+msgid "Misc"
+msgstr ""
+
+#: ../../../README.md:172
+msgid "Various services that don't fit any other categories."
+msgstr ""
+
+#: ../../../README.md
+msgid "[sliding-sync](https://github.com/matrix-org/sliding-sync)"
+msgstr ""
+
+#: ../../../README.md
+msgid "(Superseded by Simplified Sliding Sync integrated into Synapse > `1.114` and Conduit > `0.6.0`) Sliding Sync support for clients which require it (e.g. old Element X versions before Simplified Sliding Sync was developed)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-sliding-sync-proxy.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-accept-invite)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A Synapse module to automatically accept invites."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-synapse-auto-accept-invite.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A cli tool that automatically compresses `state_groups` database table in background."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-synapse-auto-compressor.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Matrix Corporal](https://github.com/devture/matrix-corporal) (advanced)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Reconciliator and gateway for a managed Matrix server"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-matrix-corporal.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Etherpad](https://etherpad.org)"
+msgstr ""
+
+#: ../../../README.md
+msgid "An open source collaborative text editor"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-etherpad.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Jitsi](https://jitsi.org/)"
+msgstr ""
+
+#: ../../../README.md
+msgid "An open source video-conferencing platform"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-jitsi.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Cactus Comments](https://cactus.chat)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A federated comment system built on Matrix"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-cactus-comments.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Pantalaimon](https://github.com/matrix-org/pantalaimon)"
+msgstr ""
+
+#: ../../../README.md
+msgid "An E2EE aware proxy daemon"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-pantalaimon.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Sygnal](https://github.com/matrix-org/sygnal)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Push gateway"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-sygnal.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[ntfy](https://ntfy.sh)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Push notifications server"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-ntfy.md)"
+msgstr ""
+
+#: ../../../README.md:187
+msgid "🆕 Changes"
+msgstr ""
+
+#: ../../../README.md:189
+msgid "This playbook evolves over time, sometimes with backward-incompatible changes."
+msgstr ""
+
+#: ../../../README.md:191
+msgid "When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up with what's new."
+msgstr ""
+
+#: ../../../README.md:193
+msgid "🆘 Support"
+msgstr ""
+
+#: ../../../README.md:195
+msgid "Matrix room: [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)"
+msgstr ""
+
+#: ../../../README.md:197
+msgid "IRC channel: `#matrix-docker-ansible-deploy` on the [Libera Chat](https://libera.chat/) IRC network (irc.libera.chat:6697)"
+msgstr ""
+
+#: ../../../README.md:199
+msgid "GitHub issues: [spantaleev/matrix-docker-ansible-deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues)"
+msgstr ""
+
+#: ../../../README.md:201
+msgid "🌐 Translation"
+msgstr ""
+
+#: ../../../README.md:203
+msgid "See the [i18n/README.md](i18n/README.md) file for more information about translation."
+msgstr ""
+
+#: ../../../README.md:205
+msgid "Translations are still work in progress."
+msgstr ""
+
+#: ../../../README.md:207
+msgid "🤝 Related"
+msgstr ""
+
+#: ../../../README.md:209
+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
+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 ""
diff --git a/i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po b/i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po
new file mode 100644
index 000000000..4b5536dfb
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/YEAR-IN-REVIEW.po
@@ -0,0 +1,293 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../YEAR-IN-REVIEW.md:1
+msgid "2023"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:3
+msgid "2023 was a year filled with many changes for matrix-docker-ansible-deploy. In this post, we're looking backward at some of the major changes that happened this year, as well as taking a glimpse of what's ahead in 2024."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:5
+msgid "2023 is probably [the year of AI](https://journal.everypixel.com/2023-the-year-of-ai), with millions of people jumping aboard [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/chatgpt) train. matrix-docker-ansible-deploy is no stranger to this and 2023 began with a PR from [bertybuttface](https://github.com/bertybuttface) who added support for [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#chatgpt-support)). While OpenAI's chat GPT website was frequently overloaded in the past, their API was up which made using this bot both convenient and more reliable."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:7
+msgid "AI aside, with the playbook's focus being containers, we're **doubling down on being \"container native\"** and becoming more interoperable for people hosting other containers on the Matrix server. In [2022](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/YEAR-IN-REVIEW.md#2022), we've announced a few sibling Ansible playbooks, their use of [Traefik](https://doc.traefik.io/traefik/) and the possiblity of matrix-docker-ansible-deploy also switching to this reverse-proxy. This prediction materialized quickly. The **largest change** in the playbook in 2023 happened way back in February - matrix-docker-ansible-deploy [starting the switch from nginx to Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support) and then quickly [making Treafik the default reverse-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#traefik-is-the-default-reverse-proxy-now). As noted in the changelog entries, we envisioned a quick and complete elimination of `matrix-nginx-proxy`, but at the end of 2023, it hasn't happened yet. The playbook is already using Traefik as the front-most reverse-proxy, but nginx (via `matrix-nginx-proxy`) is still around - it has taken a step back and is only used internally for new setups. Work got to a stall due to:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:9
+msgid "complexity: untangling the overly large and messy `matrix-nginx-proxy` component is difficult"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:10
+msgid "the current setup became \"good enough\" because nginx has become an internal implementation detail for those who have migrated to Traefik. Traefik is already the default public reverse-proxy and gives better possibilities to people wishing to run other web-exposed containers on their Matrix server via [Docker Compose](https://docs.docker.com/compose/), other Ansible playbooks like [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) (more about this one, below) or any other way."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:12
+msgid "`matrix-nginx-proxy` is no longer in the way of us being interoperable, but its ugly internal details are still there. It is one more proxy in the long chain of reverse-proxies we have and we'd like to cut it out. This would both make things simpler and also boost performance."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:14
+msgid "The delay in eliminating `matrix-nginx-proxy` has probably been welcome by many existing users who decided to postpone the Traefik migration a bit longer. In 2024, work on eliminating `matrix-nginx-proxy` will continue with rapid pace. People who are still using `matrix-nginx-proxy` as their front-most reverse-proxy will need to rework their setup. About a year of putting it off has been long enough."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:16
+msgid "This large Traefik reverse-proxy change was also accompanied by another internal change which began in 2022, but continued in 2023 - **moving non-Matrix-related roles from being internal to the playbook to living their own life outside of it**. Various roles were made more decoupled and moved outside of the playbook, so that other projects (like the [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook or other Ansible playbooks) could benefit from them. This led to the **death of a few sibling playbooks** ([gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy), [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), [peertube-docker-ansible-deploy](https://github.com/spantaleev/peertube-docker-ansible-deploy), [vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy)), but brought life to something better, which supports all these services and more."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:18
+msgid "[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) is a new Ansible playbook that a few of us (matrix-docker-ansible-deploy contributors) have launched in 2023. It has quickly grown to supports [60+ services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md) and aims to do the same for [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) service hosting, as matrix-docker-ansible-deploy has done for Matrix - providing a clean and secure way to run a bunch of services in containers on a regular server (that is to say, without Kubernetes, etc.). Thanks to Traefik and Ansible role reuse, it's easy to host both mash-playbook services and matrix-docker-ansible-deploy services on the same server - see mash-playbook's [interoperability](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md) documentation page. If you've been looking for a holiday project or your New Year's Resolutions list contains \"self-hosting more services\", then you're welcome to give this new playbook a try and join its Matrix room ([#mash-playbook:devture.com](https://matrix.to/#/#mash-playbook:devture.com))."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:20
+msgid "Because many of the roles are now external to this playbook (defined in the [requirements.yml](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/da27655ef34999fa924bc0a5e641dbd9ba06f133/requirements.yml) file), running `make roles` (or better yet `just roles` via the [just tool](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#support-for-running-commands-via-just)) becomes a necessity each time one pulls playbook updates (`git pull`). Pulling external roles happens via the [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) command-line tool, but if available, the playbook would also use the much faster [agru](https://github.com/etkecc/agru) tool (developed by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) this year)."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:22
+msgid "With the internal (but important) details out of the way, we can now talk more about **new features that landed in matrix-docker-ansible-deploy in 2023**."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:24
+msgid "The following **new** **bridges** were added to the playbook in 2023:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:26
+msgid "(2023-01-11) [mautrix-slack](https://mau.dev/mautrix/slack), thanks to a PR by [Cody Neiman](https://github.com/xangelix) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#mautrix-slack-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:27
+msgid "(2023-07-21) [mautrix-gmessages](https://github.com/mautrix/gmessages), thanks to a PR by [Shreyas Ajjarapu](https://github.com/shreyasajj) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#mautrix-gmessages-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:28
+msgid "(2023-08-23) [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for Apple iMessage bridging (when combined with the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android phone), thanks to a PR by [Johan Swetzén](https://github.com/jswetzen)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:30
+msgid "This brings the total number of **[bridges that the playbook supports](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/docs/configuring-playbook.md#bridging-other-networks) up to 30**. There are alternative bridge implementations for various networks and protocols, so the number of \"unique bridged networks\" is surely much smaller."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:32
+msgid "A few other **major components and changes** landed in 2023:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:34
+msgid "(2023-02-10) The [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (successor to [Mjolnir](https://github.com/matrix-org/mjolnir)), thanks to a PR by [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#draupnir-moderation-tool-bot-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:35
+msgid "(2023-02-10) [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) to add Matrix Authentication Support to our Jitsi setup, thanks to a PR by [Jakob S.](https://github.com/jakicoll) from [zakk gGmbH](https://github.com/zakk-it) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-authentication-support-for-jitsi))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:36
+msgid "(2023-02-25) The [rageshake](https://github.com/matrix-org/rageshake) bug report server, thanks to a PR by [Benjamin Kampmann](https://github.com/gnunicorn) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#rageshake-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:37
+msgid "(2023-03-07) [Sliding Sync proxy](https://github.com/matrix-org/sliding-sync) (currently a necessary component for [Element X](https://element.io/labs/element-x) to work), thanks to: [Benjamin Kampmann](https://github.com/gnunicorn) and [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#sliding-sync-proxy-element-x-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:38
+msgid "(2023-03-12) synapse-auto-compressor to periodically and automatically run [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#synapse-auto-compressor-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:39
+msgid "(2023-07-17) [matrix-media-repo](https://github.com/turt2live/matrix-media-repo),  thanks to a PR by [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-media-repo-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:40
+msgid "(2023-08-31) [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client app (fork of [Element Web)](https://github.com/element-hq/element-web), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#schildichat-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:41
+msgid "(2023-10-18) Postgres parameters auto-tuning, thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#postgres-parameters-are-automatically-tuned-now))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:42
+msgid "(2023-10-23) Enabling federation of the room directory for Synapse (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#enabling-allow_public_rooms_over_federation-by-default-for-synapse))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:44
+msgid "The most recent change in the list above (Enabling federation of the room directory for Synapse) has been somewhat **controversial** as it goes against upstream defaults for Synapse. Nevertheless, we believe it **promotes the well-being of the Matrix Federation by improving room discovery**."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:46
+msgid "**Matrix Federation Stats** (containing the percentage of servers publishing their room directory publicly) are posted to [TWIM](https://matrix.org/category/this-week-in-matrix/) each week by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/). The number of servers which [currently published their room directory publicly](https://matrix.org/blog/2023/12/2/this-week-in-matrix-2023-12-22/#matrix-federation-stats) stands at `26.6%`, which is:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:48
+msgid "**2.4% more** than when it was when [first published to TWIM](https://matrix.org/blog/2023/11/03/this-week-in-matrix-2023-11-03/#matrix-federation-stats) (1 month earlier, in November)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:49
+msgid "likely about **15+% more** than from before we flipped the switch (in October)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:51
+msgid "Hopefully, Synapse defaults would also change the same way and we'd see the number of servers publicly listing their room directory grow faster."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:53
+msgid "With this configuration change in place, projects like [MatrixRooms.info](https://matrixrooms.info/) (made by [etke.cc](https://etke.cc/)) and potentially others in the future, can discover, index the metadata (room address, title, topic, number of users, etc.) and make public rooms browsable & searchable across the whole Matrix Federation. It'd be great if users joining Matrix could more easily find interesting communities that match their interests!"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:55
+msgid "On the **media side of things**, besides Jitsi getting better Matrix integration (via the aforementioned Matrix User Verification Service), we've also had some [Coturn security tightening](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues) as well as [performance optimizations](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#coturn-can-now-use-host-networking) for configurations exposing lots of network ports."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:57
+msgid "[Element Call](https://github.com/element-hq/element-call) seems to have become a nice and polished product lately (as proclaimed in [The Matrix Holiday Update 2023](https://matrix.org/blog/2023/12/25/the-matrix-holiday-update-2023/)), so 2024 is likely the year we'll see support for it in the playbook. Element Call depends on the [LiveKit](https://livekit.io/) streaming server (which is also useful to developers even by itself), so the first step is likely to see LiveKit support in mash-playbook via a reusable Ansible role. Such a LiveKit Ansible role could later easily land in matrix-docker-ansible-deploy and an Element Call static website could be hooked to it."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:59
+msgid "Besides these highlights, there were many other relatively large changes announced in our [CHANGELOG](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md) and hundreds of other more minor (but still important) playbook changes that didn't get a mention."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:61
+msgid "We have **hundreds of contributors to thank for their hard work** on making Matrix self-hosting better for all of us! It should be noted that **support comes in many shapes**, not only in raw code commits and financial help (via [donations](https://liberapay.com/s.pantaleev) or using the [etke.cc managed Matrix hosting service](https://etke.cc/) which is based on matrix-docker-ansible-deploy). It also comes in the shape of code reviews, helping others with [issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues), reporting new issues, participating in our support room on Matrix ([#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)), etc. To everyone who has been there to make matrix-docker-ansible-deploy better in 2023, thank you! 🙇‍♂️"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:64
+msgid "2022"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:66
+msgid "For [matrix-docker-ansible-deploy](https://github.com/spantaleev/matrix-docker-ansible-deploy/), 2022 started with **breaking the** [**Synapse**](https://github.com/element-hq/synapse) **monopoly** by [adding support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#dendrite-support) for the [Dendrite](https://github.com/matrix-org/dendrite) Matrix homeserver in early January. This required various internal changes so that the [Ansible](https://www.ansible.com/) playbook would not be Synapse-centric anymore. This groundwork paved the way for continuing in this direction and we [added support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#conduit-support) for [Conduit](https://conduit.rs/) in August."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:68
+msgid "When it comes to the `matrix-docker-ansible-deploy` Ansible playbook, 2022 was the year of the non-Synapse homeserver implementation. In practice, none of these homeserver implementations seem ready for prime-time yet and there is no migration path when coming from Synapse. Having done our job of adding support for these alternative homeserver implementations, we can say that we're not getting in the way of future progress. It's time for the Dendrite developers to push harder (development-wise) and for the Synapse developers to take a well-deserved long (infinite) break, and we may get to see more people migrating away from Synapse in the next year(s)."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:70
+msgid "Support for the following new **bridges** was added:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:72
+msgid "[Postmoogle](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#postmoogle-email-bridge-support) for bi-directional email bridging, which supersedes my old and simplistic [email2matrix](https://github.com/devture/email2matrix) one-way bridge-bot"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:73
+msgid "[mautrix-discord](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#mautrix-discord-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:74
+msgid "[go-skype-bridge](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#go-skype-bridge-bridging-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:75
+msgid "[matrix-appservice-kakaotalk](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-appservice-kakaotalk-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:77
+msgid "Support for the following new **bots** was added:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:79
+msgid "[buscarron bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#buscarron-bot-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:80
+msgid "[Honoroit bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#honoroit-bot-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:81
+msgid "[matrix-registration-bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-registration-bot-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:82
+msgid "[matrix-hookshot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-hookshot-bridging-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:83
+msgid "[maubot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#maubot-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:85
+msgid "Support for the following new **components and services** was added:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:87
+msgid "[BorgBackup](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#borg-backup-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:88
+msgid "[Cactus Comments](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cactus-comments-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:89
+msgid "[Cinny](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cinny-support) client support"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:90
+msgid "[ntfy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#ntfy-push-notifications-support) notifications"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:91
+msgid "[matrix-ldap-registration-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-ldap-registration-proxy-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:92
+msgid "[matrix\\_encryption\\_disabler support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix_encryption_disabler-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:93
+msgid "[synapse-s3-storage-provider](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-s3-storage-provider-support) to stop the Synapse media store from being a scalability problem. This brought along [another feature](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-container-image-customization-support) - an easier way to customize the Synapse container image without having to fork and self-build all of it from scratch"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:95
+msgid "Besides these major user-visible changes, a lot of work also happened **under the hood**:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:97
+msgid "we made [major improvements to Synapse workers](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#potential-backward-compatibility-break-major-improvements-to-synapse-workers) - adding support for stream writers and for running multiple workers of various kinds (federation senders, pushers, background task processing workers, etc.)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:98
+msgid "we [improved the compatibility of (Synapse + workers) with the rest of the playbook](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#backward-compatibility-break-changing-how-reverse-proxying-to-synapse-works---now-via-a-matrix-synapse-reverse-proxy-companion-service) by introducing a new `matrix-synapse-reverse-proxy-companion-service` service"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:99
+msgid "we started [splitting various Ansible roles out of the Matrix playbook and into independent roles](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#the-playbook-now-uses-external-roles-for-some-things) (e.g. `matrix-postgres` -> [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres)), which could be included in other Ansible playbooks. In fact, these roles already power a few **interesting other sibling playbooks**:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:100
+msgid "[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy), for deploying a [Gitea](https://gitea.io/) (self-hosted [Git](https://git-scm.com/) service) server"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:101
+msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), for deploying a [Nextcloud](https://nextcloud.com/) groupware server"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:102
+msgid "[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy), for deploying a [Vaultwarden](https://github.com/dani-garcia/vaultwarden) password manager server (unofficial [Bitwarden](https://bitwarden.com/) compatible server)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:104
+msgid "These sibling playbooks co-exist nicely with one another due to using [Traefik](https://traefik.io/) for reverse-proxying, instead of trying to overtake the whole server by running their own [nginx](https://nginx.org/) reverse-proxy. Hopefully soon, the Matrix playbook will follow suit and be powered by Traefik by default."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:106
+msgid "Last, but not least, to optimize our [etke.cc managed Matrix hosting service](https://etke.cc/)'s performance (but also individual Ansible playbook runs for people self-hosting by themselves using the playbook), we've [improved playbook runtime 2-5x](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) by employing various Ansible tricks."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/README.po b/i18n/locales/jp/LC_MESSAGES/docs/README.po
new file mode 100644
index 000000000..bec80a71d
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/README.po
@@ -0,0 +1,173 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/README.md:1
+msgid "Table of Contents"
+msgstr ""
+
+#: ../../../docs/README.md:3
+msgid "⬇️ Installaton guides <!-- NOTE: the 🚀 emoji is used by \"Getting started\" on README.md -->"
+msgstr ""
+
+#: ../../../docs/README.md:5
+msgid "There are two installation guides available for beginners and advanced users."
+msgstr ""
+
+#: ../../../docs/README.md:7
+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/README.md:9
+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."
+msgstr ""
+
+#: ../../../docs/README.md:11
+msgid "[Prerequisites](prerequisites.md)"
+msgstr ""
+
+#: ../../../docs/README.md:13
+msgid "[Configuring your DNS settings](configuring-dns.md)"
+msgstr ""
+
+#: ../../../docs/README.md:15
+msgid "[Getting the playbook](getting-the-playbook.md)"
+msgstr ""
+
+#: ../../../docs/README.md:17
+msgid "[Configuring the playbook](configuring-playbook.md)"
+msgstr ""
+
+#: ../../../docs/README.md:19
+msgid "[Installing](installing.md)"
+msgstr ""
+
+#: ../../../docs/README.md:21
+msgid "🛠️ Configuration options"
+msgstr ""
+
+#: ../../../docs/README.md:28
+msgid "You can check useful documentation for configuring components here: [Configuring the playbook](configuring-playbook.md)"
+msgstr ""
+
+#: ../../../docs/README.md:30
+msgid "[Administration](configuring-playbook.md#administration) - services that help you in administrating and monitoring your Matrix installation"
+msgstr ""
+
+#: ../../../docs/README.md:32
+msgid "[Authentication and user-related](configuring-playbook.md#authentication-and-user-related) - extend and modify how users are authenticated on your homeserver"
+msgstr ""
+
+#: ../../../docs/README.md:34
+msgid "[Bots](configuring-playbook.md#bots) - bots provide various additional functionality to your installation"
+msgstr ""
+
+#: ../../../docs/README.md:36
+msgid "[Bridges](configuring-playbook.md#bridging-other-networks) - bridges can be used to connect your Matrix installation with third-party communication networks"
+msgstr ""
+
+#: ../../../docs/README.md:38
+msgid "[Clients](configuring-playbook.md#clients) - web clients for Matrix that you can host on your own domains"
+msgstr ""
+
+#: ../../../docs/README.md:40
+msgid "[Core service adjustments](configuring-playbook.md#core-service-adjustments) - backbone of your Matrix system"
+msgstr ""
+
+#: ../../../docs/README.md:42
+msgid "[File Storage](configuring-playbook.md#file-storage) - use alternative file storage to the default `media_store` folder"
+msgstr ""
+
+#: ../../../docs/README.md:46
+msgid "[Other specialized services](configuring-playbook.md#other-specialized-services) - various services that don't fit any other categories"
+msgstr ""
+
+#: ../../../docs/README.md:48
+msgid "👨‍🔧 Maintenance"
+msgstr ""
+
+#: ../../../docs/README.md:50
+msgid "If your server and services experience issues, feel free to come to [our support room](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) and ask for help."
+msgstr ""
+
+#: ../../../docs/README.md:54
+msgid "[Checking if services work](maintenance-checking-services.md)"
+msgstr ""
+
+#: ../../../docs/README.md:56
+msgid "[Maintenance and Troubleshooting](maintenance-and-troubleshooting.md)"
+msgstr ""
+
+#: ../../../docs/README.md:58
+msgid "[PostgreSQL maintenance](maintenance-postgres.md)"
+msgstr ""
+
+#: ../../../docs/README.md:60
+msgid "[Synapse maintenance](maintenance-synapse.md)"
+msgstr ""
+
+#: ../../../docs/README.md:62
+msgid "[Upgrading services](maintenance-upgrading-services.md)"
+msgstr ""
+
+#: ../../../docs/README.md:64
+msgid "Other documentation pages <!-- NOTE: this header's title and the section below need optimization -->"
+msgstr ""
+
+#: ../../../docs/README.md:66
+msgid "ℹ️ **[FAQ](faq.md)** - various Frequently Asked Questions about Matrix, with a focus on this Ansible playbook"
+msgstr ""
+
+#: ../../../docs/README.md:70
+msgid "[Alternative architectures](alternative-architectures.md)"
+msgstr ""
+
+#: ../../../docs/README.md:72
+msgid "[Container images used by the playbook](container-images.md)"
+msgstr ""
+
+#: ../../../docs/README.md:74
+msgid "[Obtaining an Access Token](obtaining-access-tokens.md)"
+msgstr ""
+
+#: ../../../docs/README.md:76
+msgid "[Playbook tags](playbook-tags.md)"
+msgstr ""
+
+#: ../../../docs/README.md:78
+msgid "[Registering users](registering-users.md)"
+msgstr ""
+
+#: ../../../docs/README.md:80
+msgid "[Running `just` commands](just.md)"
+msgstr ""
+
+#: ../../../docs/README.md:82
+msgid "[Self-building](self-building.md)"
+msgstr ""
+
+#: ../../../docs/README.md:84
+msgid "[Uninstalling](uninstalling.md)"
+msgstr ""
+
+#: ../../../docs/README.md:86
+msgid "[Updating users passwords](updating-users-passwords.md)"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/alternative-architectures.po b/i18n/locales/jp/LC_MESSAGES/docs/alternative-architectures.po
new file mode 100644
index 000000000..3d849ba01
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/alternative-architectures.po
@@ -0,0 +1,61 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/alternative-architectures.md:1
+msgid "Alternative architectures"
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:3
+msgid "As stated in the [Prerequisites](prerequisites.md), currently only `amd64` (`x86_64`) is fully supported."
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:5
+msgid "The playbook automatically determines the target server's architecture (the `matrix_architecture` variable) to be one of the following:"
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:7
+msgid "`amd64` (`x86_64`)"
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:8
+msgid "`arm32`"
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:9
+msgid "`arm64`"
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:11
+msgid "Some tools and container images can be built on the host or other measures can be used to install on that architecture."
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:13
+msgid "Implementation details"
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:15
+msgid "For `amd64`, prebuilt container images (see the [container images we use](container-images.md)) are used for all components (except [Hydrogen](configuring-playbook-client-hydrogen.md), which goes through self-building)."
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:17
+msgid "For other architecture (`arm64`, `arm32`), components which have a prebuilt image make use of it. If the component is not available for the specific architecture, [self-building](self-building.md) will be used. Not all components support self-building though, so your mileage may vary."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/ansible.po b/i18n/locales/jp/LC_MESSAGES/docs/ansible.po
new file mode 100644
index 000000000..f976b2a7d
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/ansible.po
@@ -0,0 +1,181 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/ansible.md:2
+msgid "Running this playbook"
+msgstr ""
+
+#: ../../../docs/ansible.md:4
+msgid "This playbook is meant to be run using [Ansible](https://www.ansible.com/)."
+msgstr ""
+
+#: ../../../docs/ansible.md:6
+msgid "Ansible typically runs on your local computer and carries out tasks on a remote server. If your local computer cannot run Ansible, you can also run Ansible on some server somewhere (including the server you wish to install to)."
+msgstr ""
+
+#: ../../../docs/ansible.md:8
+msgid "Supported Ansible versions"
+msgstr ""
+
+#: ../../../docs/ansible.md:10
+msgid "To manually check which version of Ansible you're on, run: `ansible --version`."
+msgstr ""
+
+#: ../../../docs/ansible.md:12
+msgid "For the **best experience**, we recommend getting the **latest version of Ansible available**."
+msgstr ""
+
+#: ../../../docs/ansible.md:14
+msgid "We're not sure what's the minimum version of Ansible that can run this playbook successfully. The lowest version that we've confirmed (on 2022-11-26) to be working fine is: `ansible-core` (`2.11.7`) combined with `ansible` (`4.10.0`)."
+msgstr ""
+
+#: ../../../docs/ansible.md:16
+msgid "If your distro ships with an Ansible version older than this, you may run into issues. Consider [Upgrading Ansible](#upgrading-ansible) or [using Ansible via Docker](#using-ansible-via-docker)."
+msgstr ""
+
+#: ../../../docs/ansible.md:18
+msgid "Upgrading Ansible"
+msgstr ""
+
+#: ../../../docs/ansible.md:20
+msgid "Depending on your distribution, you may be able to upgrade Ansible in a few different ways:"
+msgstr ""
+
+#: ../../../docs/ansible.md:22
+msgid "by using an additional repository (PPA, etc.), which provides newer Ansible versions. See instructions for [CentOS](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-rhel-centos-or-fedora), [Debian](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-debian), or [Ubuntu](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-ubuntu) on the Ansible website."
+msgstr ""
+
+#: ../../../docs/ansible.md:24
+msgid "by removing the Ansible package (`yum remove ansible` or `apt-get remove ansible`) and installing via [pip](https://pip.pypa.io/en/stable/installation/) (`pip install ansible`)."
+msgstr ""
+
+#: ../../../docs/ansible.md:26
+msgid "If using the `pip` method, do note that the `ansible-playbook` binary may not be on the `$PATH` (https://linuxconfig.org/linux-path-environment-variable), but in some more special location like `/usr/local/bin/ansible-playbook`. You may need to invoke it using the full path."
+msgstr ""
+
+#: ../../../docs/ansible.md:28
+msgid "**Note**: Both of the above methods are a bad way to run system software such as Ansible. If you find yourself needing to resort to such hacks, please consider reporting a bug to your distribution and/or switching to a sane distribution, which provides up-to-date software."
+msgstr ""
+
+#: ../../../docs/ansible.md:30
+msgid "Using Ansible via Docker"
+msgstr ""
+
+#: ../../../docs/ansible.md:32
+msgid "Alternatively, you can run Ansible inside a Docker container (powered by the [devture/ansible](https://hub.docker.com/r/devture/ansible/) Docker image)."
+msgstr ""
+
+#: ../../../docs/ansible.md:34
+msgid "This ensures that you're using a very recent Ansible version, which is less likely to be incompatible with the playbook."
+msgstr ""
+
+#: ../../../docs/ansible.md:36
+msgid "You can either [run Ansible in a container on the Matrix server itself](#running-ansible-in-a-container-on-the-matrix-server-itself) or [run Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)."
+msgstr ""
+
+#: ../../../docs/ansible.md:38
+msgid "Running Ansible in a container on the Matrix server itself"
+msgstr ""
+
+#: ../../../docs/ansible.md:40
+msgid "To run Ansible in a (Docker) container on the Matrix server itself, you need to have a working Docker installation. Docker is normally installed by the playbook, so this may be a bit of a chicken and egg problem. To solve it:"
+msgstr ""
+
+#: ../../../docs/ansible.md:42
+msgid "you **either** need to install Docker manually first. Follow [the upstream instructions](https://docs.docker.com/engine/install/) for your distribution and consider setting `matrix_playbook_docker_installation_enabled: false` in your `vars.yml` file, to prevent the playbook from installing Docker"
+msgstr ""
+
+#: ../../../docs/ansible.md:43
+msgid "**or** you need to run the playbook in another way (e.g. [Running Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)) at least the first time around"
+msgstr ""
+
+#: ../../../docs/ansible.md:45
+msgid "Once you have a working Docker installation on the server, **clone the playbook** somewhere on the server and configure it as per usual (`inventory/hosts`, `inventory/host_vars/..`, etc.), as described in [configuring the playbook](configuring-playbook.md)."
+msgstr ""
+
+#: ../../../docs/ansible.md:47
+msgid "You would then need to add `ansible_connection=community.docker.nsenter` to the host line in `inventory/hosts`. This tells Ansible to connect to the \"remote\" machine by switching Linux namespaces with [nsenter](https://man7.org/linux/man-pages/man1/nsenter.1.html), instead of using SSH."
+msgstr ""
+
+#: ../../../docs/ansible.md:49
+msgid "Alternatively, you can leave your `inventory/hosts` as is and specify the connection type in **each** `ansible-playbook` call you do later, like this: `ansible-playbook --connection=community.docker.nsenter …`"
+msgstr ""
+
+#: ../../../docs/ansible.md:51 ../../../docs/ansible.md:71
+msgid "Run this from the playbook's directory:"
+msgstr ""
+
+#: ../../../docs/ansible.md:63 ../../../docs/ansible.md:84
+msgid "Once you execute the above command, you'll be dropped into a `/work` directory inside a Docker container. The `/work` directory contains the playbook's code."
+msgstr ""
+
+#: ../../../docs/ansible.md:65 ../../../docs/ansible.md:86
+msgid "First, consider running `git config --global --add safe.directory /work` to [resolve directory ownership issues](#resolve-directory-ownership-issues)."
+msgstr ""
+
+#: ../../../docs/ansible.md:67
+msgid "Finally, you can execute `ansible-playbook …` (or `ansible-playbook --connection=community.docker.nsenter …`) commands as per normal now."
+msgstr ""
+
+#: ../../../docs/ansible.md:69
+msgid "Running Ansible in a container on another computer (not the Matrix server)"
+msgstr ""
+
+#: ../../../docs/ansible.md:82
+msgid "The above command tries to mount an SSH key (`$HOME/.ssh/id_rsa`) into the container (at `/root/.ssh/id_rsa`). If your SSH key is at a different path (not in `$HOME/.ssh/id_rsa`), adjust that part."
+msgstr ""
+
+#: ../../../docs/ansible.md:88
+msgid "Finally, you execute `ansible-playbook …` commands as per normal now."
+msgstr ""
+
+#: ../../../docs/ansible.md:90
+msgid "If you don't use SSH keys for authentication"
+msgstr ""
+
+#: ../../../docs/ansible.md:92
+msgid "If you don't use SSH keys for authentication, simply remove that whole line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`)."
+msgstr ""
+
+#: ../../../docs/ansible.md:94
+msgid "To authenticate at your server using a password, you need to add a package. So, when you are in the shell of the ansible docker container (the previously used `docker run -it …` command), run:"
+msgstr ""
+
+#: ../../../docs/ansible.md:100
+msgid "Then, to be asked for the password whenever running an  `ansible-playbook` command add `--ask-pass` to the arguments of the command."
+msgstr ""
+
+#: ../../../docs/ansible.md:102
+msgid "Resolve directory ownership issues"
+msgstr ""
+
+#: ../../../docs/ansible.md:104
+msgid "Because you're `root` in the container running Ansible and this likely differs fom the owner (your regular user account) of the playbook directory outside of the container, certain playbook features which use `git` locally may report warnings such as:"
+msgstr ""
+
+#: ../../../docs/ansible.md:106
+msgid "fatal: unsafe repository ('/work' is owned by someone else) To add an exception for this directory, call:  git config --global --add safe.directory /work"
+msgstr ""
+
+#: ../../../docs/ansible.md:110
+msgid "These errors can be resolved by making `git` trust the playbook directory by running `git config --global --add safe.directory /work`"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-captcha.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-captcha.po
new file mode 100644
index 000000000..b5f7221c0
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-captcha.po
@@ -0,0 +1,79 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-captcha.md:1
+msgid "(Adapted from the [upstream project](https://github.com/element-hq/synapse/blob/develop/docs/CAPTCHA_SETUP.md))"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:3
+msgid "Overview"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:5
+msgid "Captcha can be enabled for this home server. This file explains how to do that."
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:7
+msgid "The captcha mechanism used is Google's [ReCaptcha](https://www.google.com/recaptcha/). This requires API keys from Google. If your homeserver is Dendrite then [hCapcha](https://www.hcaptcha.com) can be used instead."
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:9
+msgid "ReCaptcha"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:11
+#: ../../../docs/configuring-captcha.md:37
+msgid "Getting keys"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:13
+#: ../../../docs/configuring-captcha.md:39
+msgid "Requires a site/secret key pair from:"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:15
+msgid "<http://www.google.com/recaptcha/admin>"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:17
+msgid "Must be a reCAPTCHA **v2** key using the \"I'm not a robot\" Checkbox option"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:19
+msgid "Setting ReCaptcha keys"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:21
+msgid "Once registered as above, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:35
+msgid "hCaptcha"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:41
+msgid "<https://dashboard.hcaptcha.com/sites/new>"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:43
+msgid "Setting hCaptcha keys"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-dns.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-dns.po
new file mode 100644
index 000000000..fbedb7d24
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-dns.po
@@ -0,0 +1,345 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-dns.md:1
+msgid "Configuring your DNS settings"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:3
+msgid "<sup>[Prerequisites](prerequisites.md) > Configuring your DNS settings > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)</sup>"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:5
+msgid "To set up Matrix on your domain, you'd need to do some DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:7
+msgid "DNS setting for server delegation (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:9
+msgid "In the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:11
+msgid "To use such an ID, you don't need to install anything on the actual `example.com` server. Instead, you need to instruct the Matrix network that Matrix services for `example.com` are redirected over to `matrix.example.com`. This redirection is also known as \"delegation\"."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:13
+msgid "As we discuss in [Server Delegation](howto-server-delegation.md), server delegation can be configured in either of these ways:"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:15
+msgid "Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:16
+msgid "Setting up a `_matrix._tcp` DNS SRV record"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:18
+msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file, instead of using a DNS SRV record."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:20
+msgid "If you choose the recommended method (file-based delegation), you do not need to configure the DNS record to enable server delegation. You will need to add a necessary configuration later, when you [finalize the installation](installing.md#finalize-the-installation) after installing and starting Matrix services."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:22
+msgid "On the other hand, if you choose this method (setting up a DNS SRV record), you need to configure the additional DNS record as well as adjust SSL certificate handling. Take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:24
+msgid "DNS settings for services enabled by default"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:26
+msgid "To serve the base domain (`example.com`) and [Element Web](configuring-playbook-client-element-web.md) with the default subdomain, adjust DNS records as below."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "Type"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "Host"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "Priority"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "Weight"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "Port"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "Target"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "A"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`matrix`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "-"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`matrix-server-IP`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "CNAME"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`element`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`matrix.example.com`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:33
+msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:35
+msgid "The `element.example.com` subdomain is necessary, because this playbook installs the [Element Web](https://github.com/element-hq/element-web) client for you by default. If you'd rather instruct the playbook not to install Element Web (`matrix_client_element_enabled: false` when [Configuring the playbook](configuring-playbook.md) later), feel free to skip the `element.example.com` DNS record."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:37
+msgid "Be mindful as to how long it will take for the DNS records to propagate."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:39
+msgid "If you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\". Otherwise, fetching certificates will fail."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:41
+msgid "DNS settings for optional services/features"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:43
+msgid "For other services which may need subdomain settings, see the table below and configure the DNS (`CNAME`) records accordingly."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "Used by component"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Dimension](configuring-playbook-dimension.md) integration server"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`dimension`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Jitsi](configuring-playbook-jitsi.md) video-conferencing platform"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`jitsi`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) monitoring system"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`stats`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Go-NEB](configuring-playbook-bot-go-neb.md) bot"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`goneb`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Sygnal](configuring-playbook-sygnal.md) push notification gateway"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`sygnal`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[ntfy](configuring-playbook-ntfy.md) push notifications server"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`ntfy`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Etherpad](configuring-playbook-etherpad.md) collaborative text editor"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`etherpad`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Hydrogen](configuring-playbook-client-hydrogen.md) web client"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`hydrogen`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Cinny](configuring-playbook-client-cinny.md) web client"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`cinny`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md) client"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`schildichat`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[wsproxy](configuring-playbook-bridge-mautrix-wsproxy.md) sms bridge"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`wsproxy`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Buscarron](configuring-playbook-bot-buscarron.md) helpdesk bot"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`buscarron`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[rageshake](configuring-playbook-rageshake.md) bug report server"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`rageshake`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[ma1sd](configuring-playbook-ma1sd.md) identity server"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "SRV"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`_matrix-identity._tcp`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "10"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "0"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "443"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md)/[Email2Matrix](configuring-playbook-email2matrix.md) email bridges"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "MX"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md) email bridge"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "TXT"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`v=spf1 ip4:matrix-server-IP -all`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`_dmarc.matrix`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`v=DMARC1; p=quarantine;`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "`postmoogle._domainkey.matrix`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md
+msgid "get it from `!pm dkim`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:66
+msgid "SRV record for ma1sd"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:68
+msgid "To make ma1sd enable its federation features, you need to set up a `_matrix-identity._tcp` SRV record. Don't confuse this with the `_matrix._tcp` SRV record for server delegation. See the table above and [this section](configuring-playbook-ma1sd.md#adjusting-dns-records) for values which need to be specified."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:70
+msgid "When setting up a SRV record, if you are asked for a service and protocol instead of a hostname split the host value from the table where the period is. For example use service as `_matrix-identity` and protocol as `_tcp`."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:72
+msgid "MX and TXT records for Postmoogle"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:74
+msgid "To make Postmoogle enable its email sending features, you need to configure MX and TXT (SPF, DMARC, and DKIM) records. See the table above for values which need to be specified."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:78
+msgid "[▶️](getting-the-playbook.md) When you're done with the DNS configuration and ready to proceed, continue with [Getting the playbook](getting-the-playbook.md)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po
new file mode 100644
index 000000000..bd7e7f512
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-alertmanager-receiver.po
@@ -0,0 +1,169 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:1
+msgid "Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:3
+msgid "The playbook can install and configure the [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver) service for you. It's a [client](https://prometheus.io/docs/alerting/latest/clients/) for Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/), allowing you to deliver alerts to Matrix rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:5
+msgid "See the project's [documentation](https://github.com/metio/matrix-alertmanager-receiver/blob/main/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:7
+msgid "This service is meant to be used with an external [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) instance. It's **not** meant to be integrated with the [Prometheus & Grafana stack](./configuring-playbook-prometheus-grafana.md) installed by this playbook, because the Alertmanager component is not installed by it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:11
+msgid "Register the bot account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:13
+msgid "This service uses a bot (with a username specified in `matrix_alertmanager_receiver_config_matrix_user_id_localpart`) for delivering messages."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:15
+msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:17
+msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:19
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:25
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:27
+msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:29
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:31
+msgid "Join to rooms as the bot manually"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:33
+msgid "ℹ️ **This bot does not accept room invitations automatically**. To deliver messages to rooms, the bot must be joined to all rooms manually."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:35
+msgid "For each new room you would like the bot to deliver alerts to, invite the bot to the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:37
+msgid "Then, log in as the bot using any Matrix client of your choosing, accept the room invitation from the bot's account, and log out."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:39
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:41
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:62
+msgid "See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for additional configuration variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:64
+msgid "Adjusting the matrix-alertmanager-receiver URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:66
+msgid "By default, this playbook installs matrix-alertmanager-receiver on the `matrix.` subdomain, at the `/matrix-alertmanager-receiver` path (https://matrix.example.com/matrix-alertmanager-receiver). 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-alertmanager-receiver.md:68
+msgid "By tweaking the `matrix_alertmanager_receiver_hostname` and `matrix_alertmanager_receiver_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-alertmanager-receiver.md:70
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:78
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:80
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-alertmanager-receiver domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:82
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:84
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:86
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:88
+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-alertmanager-receiver.md:95
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:97
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:99
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:101
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:103
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:105
+msgid "Configure your Prometheus Alertmanager with configuration like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:124
+msgid "where `URL_HERE` looks like `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/some-room-name` or `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/!qporfwt:example.com`."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po
new file mode 100644
index 000000000..a52e548fe
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-double-puppet.po
@@ -0,0 +1,77 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:1
+msgid "Setting up Appservice Double Puppet (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:3
+msgid "Appservice Double Puppet is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:5
+msgid "This is useful for performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via the [appservice method](https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new). The Appservice Double Puppet service is an implementation of this approach."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:7
+msgid "Previously, bridges supported performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but this old and hacky solution has been superseded by this Appservice Double Puppet method."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:11
+msgid "To enable the Appservice Double Puppet service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:17
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:19
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:26
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:28
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:30
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:32
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:34
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:36
+msgid "When enabled, double puppeting will automatically be enabled for all bridges that support double puppeting via the appservice method."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po
new file mode 100644
index 000000000..356109443
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po
@@ -0,0 +1,194 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:1
+msgid "Setting up Draupnir for All/D4A (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:3
+msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool for you in appservice mode."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:5
+msgid "Appservice mode can be used together with the regular [Draupnir bot](configuring-playbook-bot-draupnir.md) or independently. Details about the differences between the 2 modes are described below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:7
+msgid "Draupnir Appservice mode compared to Draupnir bot mode"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:9
+msgid "The administrative functions for managing the appservice are alpha quality and very limited. However, the experience of using an appservice-provisioned Draupnir is on par with the experience of using Draupnir from bot mode except in the case of avatar customisation as described later on in this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:11
+msgid "Draupnir for all is the way to go if you need more than 1 Draupnir instance, but you don't need access to Synapse Admin features as they are not accessible through Draupnir for All (Even though the commands do show up in help)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:13
+msgid "Draupnir for all in the playbook is rate-limit-exempt automatically as its appservice configuration file does not specify any rate limits."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:15
+msgid "Normal Draupnir does come with the benefit of access to Synapse Admin features. You are also able to more easily customise your normal Draupnir than D4A as D4A even on the branch with the Avatar command (To be Upstreamed to Mainline Draupnir) that command is clunky as it requires the use of things like Element Web devtools. In normal Draupnir this is a quick operation where you login to Draupnir with a normal client and set Avatar and Display name normally."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:17
+msgid "Draupnir for all does not support external tooling like [MRU](https://mru.rory.gay) as it can't access Draupnir's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:19
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:21
+msgid "Create a main management room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:23
+msgid "The playbook does not create a management room for your Main Draupnir. You **need to create the room manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:25
+msgid "Note that the room must be unencrypted."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:29
+msgid "The management room has to be given an alias and be public when you are setting up the bot for the first time as the bot does not differentiate between invites and invites to the management room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:31
+msgid "This management room is used to control who has access to your D4A deployment. The room stores this data inside of the control room state so your bot must have sufficient powerlevel to send custom state events. This is default 50 or moderator as Element clients call this powerlevel."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:33
+msgid "As noted in the Draupnir install instructions the control room is sensitive. **Anyone in this room can control the bot so it is important that you only invite trusted users to this room.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:35
+msgid "Set an alias to the management room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:37
+msgid "Next, set an alias to the management room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:39
+msgid "This alias can be anything you want. However, for increased security during the setup phase, it is recommended to make this alias be a random string. When it has been locked down after setup phase, you can give your room a secondary human readable alias."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:41
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:43
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ALIAS_HERE`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:51
+msgid "Extending the configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:53
+msgid "You can configure additional options by adding the `matrix_appservice_draupnir_for_all_extension_yaml` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:55
+msgid "For example, to change Draupnir's `protectAllJoinedRooms` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:69
+msgid "You can refer to the upstream [documentation](https://github.com/the-draupnir-project/Draupnir) for more configuration documentation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:71
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:86
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:73
+msgid "The playbook ships a full copy of the example config that does transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in the template directory of the role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:75
+msgid "Config extension does not affect the appservices config as this config is not extensible in current Draupnir anyway. It instead touches the config passed to the Draupnirs that your Appservice creates. So the example above (`protectAllJoinedRooms: true`) makes all provisioned Draupnirs protect all joined rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:77
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:79
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:88
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:90
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:92
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:94
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:96
+msgid "If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com` you have succesfully installed Draupnir for All and can now start using it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:98
+msgid "The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot mode."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:100
+msgid "Granting Users the ability to use D4A"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:102
+msgid "Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recomendation. Using the chat is recomended."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:104
+msgid "The bot requires a powerlevel of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:106
+msgid "To allow users or whole homeservers you type /plain @draupnir-main:example.com allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:108
+msgid "How to provision a D4A once you are allowed to"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:110
+msgid "To provision a D4A, you need to start a chat with `@draupnir-main:example.com`. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:112
+msgid "Congratulations if you made it all the way here because you now have a fully working Draupnir for all deployment."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-backup-borg.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-backup-borg.po
new file mode 100644
index 000000000..ea0595781
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-backup-borg.po
@@ -0,0 +1,141 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-22 17:53+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-backup-borg.md:1
+msgid "Setting up BorgBackup (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:3
+msgid "The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) (short: Borg) with [borgmatic](https://torsion.org/borgmatic/) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:5
+msgid "BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:7
+msgid "You will need a remote server where BorgBackup will store the backups. There are hosted, BorgBackup compatible solutions available, such as [BorgBase](https://www.borgbase.com)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:9
+msgid "The backup will run based on `backup_borg_schedule` var (systemd timer calendar), default: 4am every day."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:11
+msgid "By default, if you're using the integrated Postgres database server (as opposed to [an external Postgres server](configuring-playbook-external-postgres.md)), backups with BorgBackup will also include dumps of your Postgres database. An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md). If you decide to go with another solution, you can disable Postgres-backup support for BorgBackup using the `backup_borg_postgresql_enabled` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:13
+msgid "**Note**: the component is not managed by this repository but its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:15
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:17
+msgid "If you do not disable Postgres-backup support, make sure that the Postgres version of your homeserver's database is compatible with borgmatic."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:19
+msgid "Create a new SSH key:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:25
+msgid "This can be done on any machine and you don't need to place the key in the `.ssh` folder. It will be added to the Ansible config later."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:27
+msgid "Add the **public** part of this SSH key (the `matrix-borg-backup.pub` file) to your BorgBackup provider/server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:29
+msgid "If you plan to use a hosted solution, follow their instructions. If you have your own server, copy the key over:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:39
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:41
+msgid "Minimal working configuration (`inventory/host_vars/matrix.example.com/vars.yml`) to enable BorgBackup:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:58
+msgid "where:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:60
+msgid "USER - SSH user of a provider/server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:61
+msgid "HOST - SSH host of a provider/server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:62
+msgid "REPO - BorgBackup repository name, it will be initialized on backup start, eg: `matrix`, regarding Syntax see [Remote repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html#repository-urls)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:63
+msgid "PASSPHRASE - passphrase used for encrypting backups. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:64
+msgid "PRIVATE KEY - the content of the **private** part of the SSH key you created before. The whole key (all of its belonging lines) under `backup_borg_ssh_key_private` needs to be indented with 2 spaces"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:66
+msgid "To backup without encryption, add `backup_borg_encryption: 'none'` to your vars. This will also enable the `backup_borg_unknown_unencrypted_repo_access_is_ok` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:68
+msgid "`backup_borg_location_source_directories` defines the list of directories to back up: it's set to `{{ matrix_base_data_path }}` by default, which is the base directory for every service's data, such as Synapse, Postgres and the bridges. You might want to exclude certain directories or file patterns from the backup using the `backup_borg_location_exclude_patterns` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:70
+msgid "Check the [backup_borg role](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)'s [defaults/main.yml](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml) file for the full list of available options."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:72
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:74
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:81
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:83
+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-backup-borg.md:85
+msgid "Manually start a backup"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:87
+msgid "For testing your setup it can be helpful to not wait until 4am. If you want to run the backup immediately, log onto the server and run `systemctl start matrix-backup-borg`. This will not return until the backup is done, so possibly a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po
new file mode 100644
index 000000000..efd13268e
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-base-domain-serving.po
@@ -0,0 +1,161 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:1
+msgid "Serving the base domain (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:3
+msgid "By default, this playbook sets up services on your Matrix server (`matrix.example.com`), but has it configured so that it presents itself as the base domain (`example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:5
+msgid "As we discuss in [Server Delegation](howto-server-delegation.md), server delegation / redirection can be configured in either of these ways:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:7
+msgid "Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:8
+msgid "Setting up a `_matrix._tcp` DNS SRV record"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:10
+msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:12
+msgid "However, those who don't have a separate server to dedicate to the base domain have trouble arranging this."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:14
+msgid "Usually, there are 2 options:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:16
+msgid "either get a separate server for the base domain, just for serving the files necessary for [Server Delegation via a well-known file](howto-server-delegation.md#server-delegation-via-a-well-known-file)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:18
+msgid "or, arrange for the Matrix server to serve the base domain. This either involves you [using your own webserver](configuring-playbook-own-webserver.md) or making the integrated webserver serve the base domain for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:20
+msgid "This documentation page tells you how to do the latter. With some easy changes, we make it possible to serve the base domain from the Matrix server via the integrated webserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:22
+msgid "Just [**adjust your DNS records**](configuring-dns.md), so that your base domain is pointed to the Matrix server's IP address (using a DNS `A` record) **and then add the following configuration** to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:28
+msgid "Doing this, the playbook will:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:30
+msgid "obtain an SSL certificate for the base domain, just like it does for all other domains (see [how we handle SSL certificates](configuring-playbook-ssl-certificates.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:32
+msgid "serve the `/.well-known/matrix/*` files which are necessary for [Federation Server Discovery](configuring-well-known.md#federation-server-discovery) (also see [Server Delegation](howto-server-delegation.md)) and [Client-Server discovery](configuring-well-known.md#client-server-discovery)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:34
+msgid "serve a simple homepage at `https://example.com` with content `Hello from example.com` (configurable via the `matrix_static_files_file_index_html_template` variable). You can also [serve a more complicated static website](#serving-a-static-website-at-the-base-domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:36
+msgid "Serving a static website at the base domain"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:38
+msgid "By default, when \"serving the base domain\" is enabled, the playbook hosts a simple `index.html` webpage at `/matrix/static-files/public/index.html`. The content of this page is taken from the `matrix_static_files_file_index_html_template` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:40
+msgid "If you'd like to host your own static website (more than a single `index.html` page) at the base domain, you can disable the creation of this default `index.html` page like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:54
+msgid "With this configuration, Ansible will no longer mess around with the `/matrix/static-files/public/index.html` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:56
+msgid "You are then free to upload any static website files to `/matrix/static-files/public` and they will get served at the base domain. You can do so manually or by using the [ansible-role-aux](https://github.com/mother-of-all-self-hosting/ansible-role-aux) Ansible role, which is part of this playbook already."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:58
+msgid "Serving a more complicated website at the base domain"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:60
+msgid "If you'd like to serve an even more complicated (dynamic) website from the Matrix server, relying on the playbook to serve the base domain is not the best choice."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:62
+msgid "You have 2 options."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:64
+msgid "**One way is to host your base domain elsewhere**. This involves:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:65
+msgid "you stopping to serve it from the Matrix server: remove `matrix_static_files_container_labels_base_domain_enabled` from your configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:66
+msgid "[configuring Matrix Delegation via well-known](./configuring-well-known.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:68
+msgid "**Another way is to serve the base domain from another (your own) container on the Matrix server**. This involves:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:69
+msgid "telling the playbook to only serve `example.com/.well-known/matrix` files by adjusting your `vars.yml` configuration like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:70
+msgid "keep `matrix_static_files_container_labels_base_domain_enabled: true`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:71
+msgid "add an extra: `matrix_static_files_container_labels_base_domain_traefik_path_prefix: /.well-known/matrix`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:72
+msgid "building and running a new container on the Matrix server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:73
+msgid "it should be connected to the `traefik` network, so that Traefik can reverse-proxy to it"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:74
+msgid "it should have appropriate [container labels](https://docs.docker.com/config/labels-custom-metadata/), which instruct Traefik to reverse-proxy to it"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:76
+msgid "How you'll be managing building and running this container is up-to-you. You may use of the primitives from [ansible-role-aux](https://github.com/mother-of-all-self-hosting/ansible-role-aux) Ansible role to organize it yourself, or you can set it up in another way."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po
new file mode 100644
index 000000000..5e7d91371
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po
@@ -0,0 +1,428 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-23 13:09+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:1
+msgid "Setting up baibot (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:8
+msgid "🤖 [baibot](https://github.com/etkecc/baibot) (pronounced bye-bot) is a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:10
+msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as many well as other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:12
+msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to [matrix-chatgpt-bot](./configuring-playbook-bot-chatgpt.md). See the [baibot](https://github.com/etkecc/baibot) project and its documentation for more information."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:14
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:16
+msgid "API access to one or more LLM [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:18
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:20
+msgid "There are **a lot of configuration options** (some required, some possibly required, some optional), so they're **split into multiple sections below**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:23
+msgid "[Base configuration](#base-configuration)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:24
+msgid "[👮‍♂️ Administrator configuration](#️-administrator-configuration)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:25
+msgid "[👥 Initial users configuration](#-initial-users-configuration)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:26
+msgid "[🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:27
+msgid "[🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:29
+msgid "Depending on your current `vars.yml` file and desired configuration, **you may require more than just the [base configuration](#base-configuration)**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:31
+msgid "Base configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:33
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:71
+msgid "As mentioned above, **this may not be enough**. Continue with the configuration sections below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:73
+msgid "👮‍♂️ Administrator configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:75
+#: ../../../docs/configuring-playbook-bot-baibot.md:99
+msgid "This is an addition to the [base configuration](#base-configuration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:77
+msgid "To specify who is considered a bot [👮‍♂️ Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators), you either need to specify `matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The latter is a single variable which affects all bridges and bots."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:79
+msgid "If `matrix_admin` is already configured in your `vars.yml` configuration, you can skip this section."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:81
+#: ../../../docs/configuring-playbook-bot-baibot.md:110
+msgid "**If necessary**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:95
+msgid "👥 Initial users configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:97
+msgid "By default, **all users on your homeserver are considered allowed users**. If that's OK, you can skip this section."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:101
+msgid "To specify who is considered a bot [👥 User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), you may:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:103
+msgid "define an **initial** value for `matrix_bot_baibot_config_initial_global_config_user_patterns` Ansible variable, as shown below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:104
+msgid "configure the list at runtime via the bot's `!bai access set-users SPACE_SEPARATED_PATTERNS` command"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:106
+msgid "Configuring `matrix_bot_baibot_config_initial_global_config_user_patterns` is optional, but it can be useful to pre-configure the bot with a list of users who should have access to the bot's features."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:108
+msgid "**Note**: Once initially configured, the allowed users list **cannot be managed via Ansible anymore**. It can only be managed subsequently via bot commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:122
+msgid "🤖 Configuring agents via Ansible"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:124
+msgid "You are **not required** to define agents [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration) via Ansible. **To get started quickly**, you can **skip this section and define agents at runtime via chat commands** (following the bot's guidance)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:126
+msgid "Privileged users (like the [👮‍♂️ Administrator](#️-administrator-configuration), but potentially others too - see the upstream [🔒 access](https://github.com/etkecc/baibot/blob/main/docs/access.md) documentation) can **define agents dynamically at any time** via chat commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:128
+msgid "The Ansible role includes preset variables for easily enabling some [🤖 agents](https://github.com/etkecc/baibot/blob/main/docs/agents.md) on various [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md) (e.g. OpenAI, etc)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:130
+msgid "Besides the presets, the Ansible role also includes support for configuring additional statically-defined agents via the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:132
+msgid "Agents defined statically and those created dynamically (via chat) are named differently, so **conflict cannot arise**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:134
+msgid "Depending on your propensity for [GitOps](https://en.wikipedia.org/wiki/DevOps#GitOps), you may prefer to define agents statically via Ansible, or you may wish to do it dynamically via chat."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:136
+msgid "Before proceeding, we recommend reading the upstream documentation on [How to choose a provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#how-to-choose-a-provider). In short, it's probably best to go with [OpenAI](#openai)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:138
+msgid "Anthropic"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:140
+msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Anthropic provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic) with the help of the playbook's preset variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:142
+#: ../../../docs/configuring-playbook-bot-baibot.md:168
+#: ../../../docs/configuring-playbook-bot-baibot.md:201
+#: ../../../docs/configuring-playbook-bot-baibot.md:231
+msgid "Here's an example **addition** to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:160
+#: ../../../docs/configuring-playbook-bot-baibot.md:193
+#: ../../../docs/configuring-playbook-bot-baibot.md:221
+#: ../../../docs/configuring-playbook-bot-baibot.md:251
+msgid "If you'd like to use more than one model, take a look at the [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:162
+#: ../../../docs/configuring-playbook-bot-baibot.md:195
+#: ../../../docs/configuring-playbook-bot-baibot.md:223
+#: ../../../docs/configuring-playbook-bot-baibot.md:253
+msgid "💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:164
+msgid "Groq"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:166
+msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Groq provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq) with the help of the playbook's preset variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:191
+msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/groq`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:197
+msgid "Mistral"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:199
+msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [🇫🇷 Mistral provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral) with the help of the playbook's preset variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:219
+msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/mistral`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:225
+msgid "OpenAI"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:227
+msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai) with the help of the playbook's preset variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:229
+msgid "The OpenAI provider is **only meant to be used with OpenAI's official API** and compatibility with other services (which do not fully adhere to the OpenAI API spec completely) is limited. **If you're targeting an OpenAI-compatible service**, use the [OpenAI Compatible](#openai-compatible) provider instead."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:249
+msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/openai`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:255
+msgid "OpenAI Compatible"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:257
+msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI Compatible provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai-compatible) with the help of the playbook's preset variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:259
+msgid "This provider allows you to use OpenAI-compatible API services like [OpenRouter](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openrouter), [Together AI](https://github.com/etkecc/baibot/blob/main/docs/providers.md#together-ai), etc."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:261
+msgid "Some of these popular services already have **shortcut** providers (see [supported providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md#supported-providers) leading to this one behind the scenes - this make it easier to get started."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:263
+msgid "As of this moment, the playbook does not include presets for any of these services, so you'll need to [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:265
+msgid "Configuring additional agents (without a preset)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:267
+msgid "The Ansible role may be lacking preset variables for some [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), or you may wish to statically-define an agent on the same provider twice (or more) with different configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:269
+msgid "It's possible to inject your own agent configuration using the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:271
+msgid "You can also define providers at runtime, by chatting with the bot, so using Ansible is not a requirement."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:273
+msgid "Below is an an **example** demonstrating **statically-defining agents via Ansible without using presets**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:312
+msgid "Because these are [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agents, they will be given a `static/` ID prefix and will be named `static/my-openai-gpt-3.5-turbo-agent` and `static/my-ollama-agent`, respectively."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:314
+msgid "💡 To figure out what to put in the `config` section, refer to the [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md) page, which contains **sample configuration YAML for each provider**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:316
+msgid "As with any [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), defining them means they exist. To actually make use of them, they need to be configured as handlers globally or in a specific room - see [Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:318
+msgid "💡 You may also wish to use these new agents for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:320
+msgid "🤝 Configuring initial default handlers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:322
+msgid "This section is only useful if you're [🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible), as it lets you put these agents to use as soon as the bot starts (by adjusting the bot's **initial global configuration**)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:324
+msgid "If you're not configuring agents via Ansible, you can skip this section."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:326
+msgid "This section is only useful the first time around. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:328
+msgid "baibot supports [various purposes](https://github.com/etkecc/baibot/blob/main/docs/features.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:330
+msgid "[💬 text-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-generation): communicating with you via text"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:332
+msgid "[🦻 speech-to-text](https://github.com/etkecc/baibot/blob/main/docs/features.md#-speech-to-text): turning your voice messages into text"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:334
+msgid "[🗣️ text-to-speech](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-to-speech): turning bot or users text messages into voice messages"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:336
+msgid "[🖌️ image-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-image-generation): generating images based on instructions"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:338
+msgid "❓ catch-all: special purposes, indicating use as a fallback (when no specific handler is configured)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:340
+msgid "[Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models) is made possible by the bot's ability to have different [🤝 handlers](https://github.com/etkecc/baibot/blob/main/docs/configuration/handlers.md) configured for different purposes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:342
+msgid "This configuration can be done as a global fallback, or per-room. Both of these [🛠️ configurations](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md) are managed at runtime (viat chat), but **the global configuration can have some initial defaults configured via Ansible**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:344
+msgid "You can configure the **initial values** for these via Ansible, via the `matrix_bot_baibot_config_initial_global_config_handler_*` variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:346
+msgid "Example **additional** `vars.yml` configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:363
+msgid "**Note**: these are initial defaults for the bot's global configuration. As such, changing any of these values subsequently has no effect on the bot's behavior. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:365
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:367
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:374
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:376
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:378
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:380
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:382
+msgid "If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:384
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:386
+msgid "To use the bot, invite it to any existing Matrix room (`/invite @baibot:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:388
+msgid "If you're an allowed bot [👥 user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) (see [👥 Initial users configuration](#-initial-users-configuration)), the bot will accept your invitation and join the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:390
+msgid "After joining, the bot will introduce itself and show information about the [✨ features](https://github.com/etkecc/baibot/blob/main/docs/features.md) that are enabled for it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:392
+msgid "If you've [🤖 configured one or more agents via Ansible](#-configuring-agents-via-ansible) and have [🤝 configured initial default handlers](#configuring-initial-default-handlers), the bot will immediately be able to make use of these agents for this new room. Otherwise, you will need to configure agents and/or handlers via chat commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:394
+msgid "Send `!bai help` to the bot in the room to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:396
+msgid "You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) project's documentation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:398
+msgid "Debugging"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:400
+msgid "As with all other services, you can find service logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-bot-baibot`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:402
+msgid "The default logging level for this service is `info`, but you can increase it to `debug` (or even `trace`) with the following additional configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:416
+msgid "**Alternatively**, you can use a single variable to set the logging level for all of the above (bot + all libraries):"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po
new file mode 100644
index 000000000..6822a51fb
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po
@@ -0,0 +1,141 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-23 13:09+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:1
+msgid "Setting up Buscarron (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:3
+msgid "The playbook can install and configure [Buscarron](https://github.com/etkecc/buscarron) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:5
+msgid "Buscarron is bot that receives HTTP POST submissions of web forms and forwards them to a Matrix room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:9
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:32
+msgid "Adjusting the Buscarron URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:34
+msgid "By default, this playbook installs Buscarron on the `buscarron.` subdomain (`buscarron.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:36
+msgid "By tweaking the `matrix_bot_buscarron_hostname` and `matrix_bot_buscarron_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-bot-buscarron.md:38
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:49
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:51
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Buscarron domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:53
+msgid "By default, you will need to create a CNAME record for `buscarron`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:55
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:57
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:59
+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-bot-buscarron.md:66
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:68
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:70
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:72
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:74
+msgid "If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:76
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:78
+msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.buscarron:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:80
+msgid "After the bot joins the room, anyone can call the web form via HTTP POST method."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:82
+msgid "Here is an example for the `contact` form:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:90
+msgid "**Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:92
+msgid "you hit the homepage (HTTP `GET` request to `/`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:93
+msgid "you submit a form to the wrong URL (`POST` request to `/non-existing-form`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:94
+msgid "`hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:96
+msgid "If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:98
+msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/buscarron)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po
new file mode 100644
index 000000000..6b6d46434
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-chatgpt.po
@@ -0,0 +1,129 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:1
+msgid "Setting up matrix-bot-chatgpt (optional, unmaintained)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:3
+msgid "**Note**: [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) is now an archived (**unmaintained**) project. Talking to ChatGPT (and many other LLM providers) can happen via the much more featureful [baibot](https://github.com/etkecc/baibot), which can be installed using [this playbook](configuring-playbook-bot-baibot.md). Consider using that bot instead of this one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:5
+msgid "The playbook can install and configure [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:7
+msgid "Talk to [ChatGPT](https://openai.com/blog/chatgpt/) via your favourite Matrix client!"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:11
+msgid "Obtain an OpenAI API key"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:13
+msgid "To use the bot, you'd need to obtain an API key from [https://platform.openai.com/account/api-keys](https://platform.openai.com/account/api-keys)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:15
+msgid "Register the bot account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:17
+msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:19
+msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:21
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:27
+msgid "Obtain an access token and create encryption keys"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:29
+msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:31
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:33
+msgid "To make sure the bot can read encrypted messages, it will need an encryption key, just like any other new user. While obtaining the access token, follow the prompts to setup a backup key. More information can be found in the [Element documentation](https://element.io/help#encryption6)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:35
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:37
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `API_KEY_HERE` with the API key retrieved [here](#obtain-an-openai-api-key) and `ACCESS_TOKEN_HERE` with the access token created [here](#obtain-an-access-token-and-create-encryption-keys), respectively."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:54
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:56
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:63
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:65
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:67
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:69
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:71
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:73
+msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.chatgpt:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:75
+msgid "After the bot joins the room, you can send a message to it. When you do so, use the prefix if you configured it or mention the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:77
+msgid "You can also refer to the upstream [documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po
new file mode 100644
index 000000000..70ab42f91
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po
@@ -0,0 +1,385 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:1
+msgid "Setting up Draupnir (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:3
+msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation bot for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:5
+msgid "See the project's [documentation](https://github.com/the-draupnir-project/Draupnir/blob/main/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:7
+msgid "This documentation page is about installing Draupnir in bot mode. As an alternative, you can run a multi-instance Draupnir deployment by installing [Draupnir in appservice mode](./configuring-playbook-appservice-draupnir-for-all.md) (called Draupnir-for-all) instead."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:9
+msgid "If your migrating from Mjolnir skip to [this section](#migrating-from-mjolnir-only-required-if-migrating)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:13
+msgid "Register the bot account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:15
+msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:17
+msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:19
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:25
+msgid "If you would like Draupnir to be able to deactivate users, move aliases, shutdown rooms, show abuse reports (see [below](#abuse-reports)), etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:27
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:29
+msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:31
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:33
+msgid "Make sure the account is free from rate limiting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:35
+msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Draupnir will crash.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:37
+msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:39
+msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:45
+msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. 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-bot-draupnir.md:47
+msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:49
+msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:55
+msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Draupnir itself. If you have made Draupnir an admin, you can just use the Draupnir token."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:57
+msgid "Create a management room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:59
+msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:61
+msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:63
+msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:65
+msgid "Finally invite the `@bot.draupnir:example.com` account you created earlier into the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:67
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:69
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:78
+msgid "End-to-End Encryption support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:80
+msgid "Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:82
+msgid "To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:84
+msgid "Configuration with E2EE support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:86
+msgid "When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:88
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:102
+msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Draupnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:114
+msgid "Configuration without E2EE support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:116
+msgid "When NOT using Pantalaimon, Draupnir does not log in by itself and you must give it an access token for its bot account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:118
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:124
+msgid "Abuse Reports"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:126
+msgid "Draupnir supports two methods to receive reports in the management room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:128
+msgid "The first method intercepts the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using traefik, this playbook can set this up for you:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:134
+msgid "The other method polls an Synapse Admin API endpoint, hence it is available only if using Synapse and if the Draupnir user is an admin (see [above](#register-the-bot-account)). To enable it, set `pollReports: true` on `vars.yml` file as below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:136
+msgid "Extending the configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:138
+msgid "You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:140
+msgid "For example, to change Draupnir's `pollReports` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:154
+msgid "Migrating from Mjolnir (Only required if migrating)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:156
+msgid "Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:158
+msgid "That is all you need to do due to that Draupnir can complete migration on its own."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:160
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:162
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:169
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:171
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:173
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:175
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:177
+msgid "If you change the Pantalaimon's password (`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:179
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:181
+msgid "You can refer to the upstream [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) for additional ways to use and configure Draupnir and for a more detailed usage guide."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:183
+msgid "Below is a **non-exhaustive quick-start guide** for the impatient."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:185
+msgid "Making Draupnir join and protect a room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:187
+msgid "Draupnir can be told to self-join public rooms, but it's better to follow this flow which works well for all kinds of rooms:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:189
+msgid "Invite the bot to the room manually ([inviting Draupnir to rooms](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#inviting-draupnir-to-rooms)). Before joining, the bot *may* ask for confirmation in the Management Room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:191
+msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:193
+msgid "Tell it to protect the room (using the [rooms command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#using-the-draupnir-rooms-command)) by sending the following command to the Management Room: `!draupnir rooms add !qporfwt:example.com`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:195
+msgid "To have Draupnir provide useful room protection, you need do to a bit more work (at least the first time around). You may wish to [Subscribe to a public policy list](#subscribing-to-a-public-policy-list), [Create your own own policy and rules](#creating-your-own-policy-lists-and-rules) and [Enabling built-in protections](#enabling-built-in-protections)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:197
+msgid "Giving Draupnir permissions to do its job"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:199
+msgid "For Draupnir to do its job, you need to [give it permissions](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#giving-draupnir-permissions) in rooms it's protecting. This involves **giving it an Administrator power level**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:201
+msgid "**We recommend setting this power level as soon as the bot joins your room** (and before you create new rules), so that it can apply rules as soon as they are available. If the bot is under-privileged, it may fail to apply protections and may not retry for a while (or until your restart it)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:203
+msgid "Subscribing to a public policy list"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:205
+msgid "We recommend **subscribing to a public [policy list](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists)** using the [watch command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-watch-command-to-subscribe-to-policy-rooms)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:207
+msgid "Polcy lists are maintained in Matrix rooms. A popular policy list is maintained in the public `#community-moderation-effort-bl:neko.dev` room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:209
+msgid "You can tell Draupnir to subscribe to it by sending the following command to the Management Room: `!draupnir watch #community-moderation-effort-bl:neko.dev`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:211
+msgid "Creating your own policy lists and rules"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:213
+msgid "We also recommend **creating your own policy lists** with the [list create](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-list-create-command-to-create-a-policy-room) command."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:215
+msgid "You can do so by sending the following command to the Management Room: `!draupnir list create my-bans my-bans-bl`. This will create a policy list having a name (shortcode) of `my-bans` and stored in a public `#my-bans-bl:example.com` room on your server. As soon as you run this command, the bot will invite you to the policy list room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:217
+msgid "A policy list does nothing by itself, so the next step is **adding some rules to your policy list**. Policies target a so-called `entity` (one of: `user`, `room` or `server`). These entities are mentioned on the [policy lists](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists) documentation page and in the Matrix Spec [here](https://spec.matrix.org/v1.11/client-server-api/#mban-recommendation)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:219
+msgid "The simplest and most useful entity to target is `user`. Below are a few examples using the [ban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-ban-command) and targeting users."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:221
+msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:223
+msgid "(ban a single user on a given homeserver): `!draupnir ban @charles:example.com my-bans Rude to others`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:224
+msgid "(ban all users on a given homeserver by using a [wildcard](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - all users are fake`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:226
+msgid "As a result of running these commands, you may observe:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:228
+msgid "Draupnir creating `m.policy.rule.user` state events in the `#my-bans-bl:example.com` room on your server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:229
+msgid "applying these rules against all rooms that Draupnir is an Administrator in"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:231
+msgid "You can undo bans with the [unban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-unban-command)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:233
+msgid "Enabling built-in protections"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:235
+msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the room to invite-only\")."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:237
+msgid "To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:239
+msgid "To **see the configuration options for a given protection**, send a `!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get JoinWaveShortCircuit`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:241
+msgid "To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:243
+msgid "To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:245
+msgid "To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po
new file mode 100644
index 000000000..2009436c9
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-go-neb.po
@@ -0,0 +1,157 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:1
+msgid "Setting up Go-NEB (optional, unmaintained)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:3
+msgid "**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an archived (**unmaintained**) project. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bot instead of this one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:5
+msgid "The playbook can install and configure [Go-NEB](https://github.com/matrix-org/go-neb) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:7
+msgid "Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, the original Matrix bot written in Python."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:9
+msgid "See the project's [documentation](https://github.com/matrix-org/go-neb/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:13
+msgid "Register the bot account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:15
+msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:17
+msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:19
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:25
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:27
+msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:29
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:31
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:33
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_GONEB_HERE` and `ACCESS_TOKEN_FOR_ANOTHER_GONEB_HERE` with the ones created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:197
+msgid "Adjusting the Go-NEB URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:199
+msgid "By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:201
+msgid "By tweaking the `matrix_bot_go_neb_hostname` and `matrix_bot_go_neb_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-bot-go-neb.md:203
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:214
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:216
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Go-NEB domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:218
+msgid "By default, you will need to create a CNAME record for `goneb`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:220
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:222
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:224
+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-bot-go-neb.md:231
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:233
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:235
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:237
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:239
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:241
+msgid "To use the bot, invite it to any existing Matrix room (`/invite @bot.go-neb:example.com` where `example.com` is your base domain, not the `matrix.` domain). Make sure you are granted with the sufficient permission if you are not the room owner."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:243
+msgid "Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy matrix`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:245
+msgid "If you enabled the github_cmd service, send `!github help` to the bot in the room to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:247
+msgid "You can also refer to the upstream [Documentation](https://github.com/matrix-org/go-neb)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po
new file mode 100644
index 000000000..2cf15ee0d
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po
@@ -0,0 +1,125 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-23 13:09+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:1
+msgid "Setting up Honoroit (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:3
+msgid "The playbook can install and configure [Honoroit](https://github.com/etkecc/honoroit) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:5
+msgid "It's a bot you can use to setup **your own helpdesk on matrix**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:7
+msgid "See the project's [documentation](https://github.com/etkecc/honoroit/blob/main/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:11
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:26
+msgid "Adjusting the Honoroit URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:28
+msgid "By default, this playbook installs Honoroit on the `matrix.` subdomain, at the `/honoroit` path (https://matrix.example.com/honoroit). 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-bot-honoroit.md:30
+msgid "By tweaking the `matrix_bot_honoroit_hostname` and `matrix_bot_honoroit_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-bot-honoroit.md:32
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:40
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:42
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Honoroit domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:44
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:46
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:48
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:50
+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-bot-honoroit.md:57
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:59
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.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-bot-honoroit.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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:65
+msgid "If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:67
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:69
+msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @honoroit:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:71
+msgid "After the bot joins the room, any Matrix user can send a message to it to start a new thread in that room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:73
+msgid "Send `!ho help` to the bot in the room to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:75
+msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/honoroit#features)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po
new file mode 100644
index 000000000..b3110a4dc
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po
@@ -0,0 +1,101 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-23 13:09+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:1
+msgid "Setting up matrix-registration-bot (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:3
+msgid "The playbook can install and configure [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:5
+msgid "The bot allows you to easily **create and manage registration tokens** aka. invitation codes. It can be used for an invitation-based server, where you invite someone by sending them a registration token (tokens look like this: `rbalQ0zkaDSRQCOp`). They can register as per normal but have to provide a valid registration token in the final step of the registration process."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:7
+msgid "See the project's [documentation](https://github.com/moan0s/matrix-registration-bot/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:11
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:30
+msgid "The bot account will be created automatically."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:32
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:34
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:41
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:43
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:45
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:47
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:49
+msgid "If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:51
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:53
+msgid "To use the bot, start a chat with `@bot.matrix-registration-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57
+msgid "You can also refer to the upstream [Usage documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:59
+msgid "If you have any questions, or if you need help setting it up, read the [troublshooting guide](https://github.com/moan0s/matrix-registration-bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:61
+msgid "To clean the cache (session & encryption data) after you changed the bot's username, changed the login method from access_token to password etc… you can use:"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po
new file mode 100644
index 000000000..20f7e1e24
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po
@@ -0,0 +1,97 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-23 13:09+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:1
+msgid "Setting up matrix-reminder-bot (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:3
+msgid "The playbook can install and configure [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:5
+msgid "It's a bot you can use to **schedule one-off & recurring reminders and alarms**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:7
+msgid "See the project's [documentation](https://github.com/anoadragon453/matrix-reminder-bot/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:26
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:28
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:35
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:37
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:39
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:41
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:43
+msgid "If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:45
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:47
+msgid "To use the bot, start a chat with `@bot.matrix-reminder-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:49
+msgid "You can also add the bot to any existing Matrix room (`/invite @bot.matrix-reminder-bot:example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:51
+msgid "Basic usage is like this: `!remindme in 2 minutes; This is a test`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:53
+msgid "Send `!help reminders` to the room to see the bot's help menu for additional commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:55
+msgid "You can also refer to the upstream [Usage documentation](https://github.com/anoadragon453/matrix-reminder-bot#usage)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po
new file mode 100644
index 000000000..2ea984e1e
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po
@@ -0,0 +1,166 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:1
+msgid "Setting up maubot (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:3
+msgid "The playbook can install and configure [maubot](https://github.com/maubot/maubot) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:5
+msgid "After setting up maubot, you can use the web management interface to make it do things. The default location of the management interface is `matrix.example.com/_matrix/maubot/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:7
+msgid "See the project's [documentation](https://docs.mau.fi/maubot/usage/basic.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:11
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:26
+msgid "You can add multiple admins. The admin accounts are only used to access the maubot administration interface."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:28
+msgid "Adjusting the maubot URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:30
+msgid "By default, this playbook installs maubot on the `matrix.` subdomain, at the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/). 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-bot-maubot.md:32
+msgid "By tweaking the `matrix_bot_maubot_hostname` and `matrix_bot_maubot_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-bot-maubot.md:34
+#: ../../../docs/configuring-playbook-bot-maubot.md:56
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:42
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:44
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the maubot domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:46
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:48
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:50
+msgid "Customizing the maubot container image"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:52
+msgid "Certain [maubot plugins](https://plugins.mau.bot/) require additional dependencies to be installed."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:54
+msgid "You can customize the default maubot container image and install your own dependencies."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:67
+msgid "Consult the [Dockerfile reference](https://docs.docker.com/reference/dockerfile/) for more information about the syntax."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:69
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:71
+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-bot-maubot.md:78
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:80
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:82
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:84
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:86
+msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:88
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:90
+msgid "By default, you can visit `matrix.example.com/_matrix/maubot/` to manage your available plugins, clients and instances."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:92
+msgid "You should start in the following order"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:93
+msgid "**Create one or more clients**: A client is a Matrix account which the bot will use to message. By default, the playbook creates a `bot.maubot` account (as per the configuration above). You only need to [obtain an access token](#obtaining-an-access-token) for it"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:94
+msgid "**Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:95
+msgid "**Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:97
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:99
+msgid "This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:101
+msgid "Alternatively, you can refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will causes issues to your bot in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:103
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po
new file mode 100644
index 000000000..2cac78d7c
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po
@@ -0,0 +1,225 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:1
+msgid "Setting up Mjolnir (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:3
+msgid "The playbook can install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation bot for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:5
+msgid "See the project's [documentation](https://github.com/matrix-org/mjolnir/blob/main/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:7
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:9
+msgid "Register the bot account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:11
+msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:13
+msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:15
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:21
+msgid "If you would like Mjolnir to be able to deactivate users, move aliases, shutdown rooms, etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:23
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:25
+msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:27
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:29
+msgid "Make sure the account is free from rate limiting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:31
+msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:33
+msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:35
+msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:41
+msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. 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-bot-mjolnir.md:43
+msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:45
+msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:51
+msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Mjolnir itself. If you have made Mjolnir an admin, you can just use the Mjolnir token."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:53
+msgid "Create a management room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:55
+msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:57
+msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:59
+msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:61
+msgid "Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:63
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:65
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:74
+msgid "End-to-End Encryption support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:76
+msgid "Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:78
+msgid "To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:80
+msgid "Configuration with E2EE support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:82
+msgid "When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:84
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:98
+msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Mjolnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:110
+msgid "Configuration without E2EE support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:112
+msgid "When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:114
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:120
+msgid "Adding Mjolnir synapse antispam module (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:122
+msgid "To enable Mjolnir synapse antispam module, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:132
+msgid "Extending the configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:134
+msgid "You can configure additional options by adding the `matrix_bot_mjolnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:136
+msgid "For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:150
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:152
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:159
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:161
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:163
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:165
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:167
+msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:169
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:171
+msgid "You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po
new file mode 100644
index 000000000..555b4be9c
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-discord.po
@@ -0,0 +1,170 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:1
+msgid "Setting up Appservice Discord bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:3
+msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:4
+msgid "For using as a Bot we are recommend the Appservice Discord bridge (the one being discussed here), because it supports plumbing."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:5
+msgid "For personal use we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:7
+msgid "The playbook can install and configure [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:9
+msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-discord/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:13
+msgid "Create a Discord Application [here](https://discordapp.com/developers/applications). Then retrieve Client ID, and create a bot from the Bot tab and retrieve the Bot token."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:15
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:17
+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-discord.md:31
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:33
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:40
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:42
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:44
+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-discord.md:46
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:48
+msgid "Self-Service Bridging (Manual)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:50
+msgid "Self-service bridging allows you to bridge specific and existing Matrix rooms to specific Discord rooms. To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:56
+msgid "**Note**: If self-service bridging is not enabled, `!discord help` commands will return no results."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:58
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:82
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:60
+msgid "Once self-service is enabled, start a chat with `@_discord_bot:example.com` and say `!discord help bridge`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:62
+msgid "Then, follow the instructions in the help output message."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:64
+msgid "If the bot is not already in the Discord server, follow the provided invite link. This may require you to be a administrator of the Discord server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:66
+msgid "On the Discord side, send `!matrix help` to the bot to see the available commands for managing the bridge and Matrix users."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:68
+msgid "**Note**: Encrypted Matrix rooms are not supported as of writing."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:70
+msgid "Portal Bridging (Automatic)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:72
+msgid "Through portal bridging, Matrix rooms will automatically be created by the bot and bridged to the relevant Discord room. This is done by simply joining a room with a specific name pattern (`#_discord_<guildID>_<channelID>`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:74
+msgid "All Matrix rooms created this way are **listed publicly** by default, and you will not have admin permissions to change this. To get more control, [make yourself a room Administrator](#getting-administrator-access-in-a-portal-bridged-room). You can then unlist the room from the directory and change the join rules."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:76
+msgid "To disable portal bridging, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:84
+msgid "To get started with Portal Bridging:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:86
+msgid "To invite the bot to Discord, retrieve the invite link from the `{{ matrix_appservice_discord_config_path }}/invite_link` file on the server (this defaults to `/matrix/appservice-discord/config/invite_link`). You need to peek at the file on the server via SSH, etc., because it's not available via HTTP(S)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:87
+msgid "Room addresses follow this syntax: `#_discord_<guildID>_<channelID>`. You can easily find the guild and channel IDs by logging into Discord in a browser and opening the desired channel. The URL will have this format: `discord.com/channels/<guildID>/<channelID>`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:88
+msgid "Once you have figured out the appropriate room address, you can join by doing `/join #_discord_<guildID>_<channelID>` in your Matrix client."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:90
+msgid "Getting Administrator access in a portal bridged room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:92
+msgid "By default, you won't have Administrator access in rooms created by the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:94
+msgid "To adjust room access privileges or do various other things (change the room name subsequently, etc.), you'd wish to become an Administrator."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:96
+msgid "There's the Discord bridge's guide for [setting privileges on bridge managed rooms](https://github.com/matrix-org/matrix-appservice-discord/blob/master/docs/howto.md#set-privileges-on-bridge-managed-rooms). To do the same with our container setup, run the following command on the server:"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po
new file mode 100644
index 000000000..21ade5894
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-irc.po
@@ -0,0 +1,77 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:1
+msgid "Setting up Appservice IRC bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:3
+msgid "**Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [Heisenbridge](configuring-playbook-bridge-heisenbridge.md) bridge supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:5
+msgid "The playbook can install and configure the [matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc) bridge for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:7
+msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-irc/blob/master/HOWTO.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:11
+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-irc.md:63
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:65
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:72
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:74
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:76
+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-irc.md:78
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:80
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:82
+msgid "To use the bridge, you need to start a chat with `@irc_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po
new file mode 100644
index 000000000..879f96227
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-kakaotalk.po
@@ -0,0 +1,161 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:1
+msgid "Setting up Appservice Kakaotalk bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:3
+msgid "The playbook can install and configure [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) for you. `matrix-appservice-kakaotalk` is a bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:5
+msgid "⚠️ **Warning**: there have been recent reports (~2022-09-16) that **using this bridge may get your account banned**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:7
+msgid "See the project's [documentation](https://src.miscworks.net/fair/matrix-appservice-kakaotalk/src/branch/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:9
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:11
+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 [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:13
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:15
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:17
+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-kakaotalk.md:23
+msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:25
+msgid "Additional configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:27
+msgid "There are some additional things you may wish to configure about the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:29
+msgid "Take a look at:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:31
+msgid "`roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:32
+msgid "`roles/custom/matrix-bridge-appservice-kakaotalk/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_kakaotalk_configuration_extension_yaml` variable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:34
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:36
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:43
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:45
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:47
+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-kakaotalk.md:49
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:51
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:53
+msgid "To use the bridge, you need to start a chat with `@kakaotalkbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:55
+msgid "Send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable bridging for your Kakaotalk account. The `--save` flag may be omitted, if you'd rather not save your password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:57
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:59
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:61
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:63
+msgid "Method 1: automatically, by enabling Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:65
+msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:67
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:69
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:71
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:73
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:75
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:77
+msgid "make sure you don't log out the `Appservice-Kakaotalk` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po
new file mode 100644
index 000000000..de682447f
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po
@@ -0,0 +1,247 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:1
+msgid "Setting up Appservice Slack bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:3
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:75
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:4
+msgid "Bridging to [Slack](https://slack.com) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:5
+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:7
+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:9
+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:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:13
+msgid "Create a Classic Slack App"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:15
+msgid "First, you need to create a Classic Slack App [here](https://api.slack.com/apps?new_classic_app=1)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:17
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:19
+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:21
+msgid "Add the following events as `Bot User Events` and save:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:23
+msgid "team_domain_change"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:24
+msgid "message.channels"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:25
+msgid "message.groups (if you want to bridge private channels)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:26
+msgid "reaction_added"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:27
+msgid "reaction_removed"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:29
+msgid "Next, click on \"OAuth & Permissions\" and add the following scopes:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:31
+msgid "chat:write:bot"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:32
+msgid "users:read"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:33
+msgid "reactions:write"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:34
+msgid "files:write:user (if you want to bridge files)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:36
+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:38
+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:40
+msgid "Create an administration control room on Matrix"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:42
+msgid "Create a new Matrix room to act as the administration control room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:44
+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:46
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:48
+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:64
+msgid "Other configuration options are available via the `matrix_appservice_slack_configuration_extension_yaml` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:66
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:68
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:77
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.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-bridge-appservice-slack.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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:83
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:85
+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:87
+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:89
+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:90
+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:91
+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:92
+msgid "Issue a link command in the administration control room with these collected values as arguments:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:94
+msgid "with file bridging:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:100
+msgid "without file bridging:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:106
+msgid "These arguments can be shortened to single-letter forms:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:112
+msgid "Unlinking"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:114
+msgid "Channels can be unlinked again by sending this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:120
+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:122
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:124
+msgid "As always, check the logs: `journalctl -fu matrix-appservice-slack`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:126
+msgid "Linking: \"Room is now pending-name\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:128
+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:130
+msgid "Messages work from Matrix to Slack, but not the other way around"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:132
+msgid "Check you logs, if they say something like"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:134
+#, python-format
+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:136
+msgid "then unlink your room, reinvite the bot and re-link it again. This may particularly hit you, if you tried to unsuccessfully link your room multiple times without unlinking it after each failed attempt."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po
new file mode 100644
index 000000000..416e522f8
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-webhooks.po
@@ -0,0 +1,113 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:1
+msgid "Setting up Appservice Webhooks bridging (optional, deprecated)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:3
+msgid "**Note**: This bridge has been deprecated. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bridge instead of this one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:5
+msgid "The playbook can install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:7
+msgid "See the project's [documentation](https://github.com/turt2live/matrix-appservice-webhooks/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:11
+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-webhooks.md:27
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:29
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:36
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:38
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:40
+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-webhooks.md:42
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:44
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:46
+msgid "To use the bridge, you need to invite the bridge bot user to your room in either way."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:48
+msgid "Send `/invite @_webhook:example.com` (**Note**: Make sure you have administration permissions in your room)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:49
+msgid "Add the bridge bot to a private channel (personal channels imply you being an administrator)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:51
+msgid "You then need to send a message to the bridge bot in order to receive a private message including the webhook link:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:57
+msgid "The JSON body for posting messages will have to look like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:68
+msgid "You can test this via curl like so:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:81
+msgid "Setting Webhooks with Dimension integration manager"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:83
+msgid "If you're using the [Dimension integration manager](configuring-playbook-dimension.md), you can configure the Webhooks bridge with it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:85
+msgid "To configure it, open the Dimension integration manager, and go to \"Settings\" and \"Bridges\", then select edit action for \"Webhook Bridge\"."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:87
+msgid "On the UI, press \"Add self-hosted Bridge\" button and populate \"Provisioning URL\"  and \"Shared Secret\" values from `/matrix/appservice-webhooks/config/config.yaml` file's homeserver URL value and provisioning secret value, respectively."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po
new file mode 100644
index 000000000..db756b10b
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-beeper-linkedin.po
@@ -0,0 +1,129 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:1
+msgid "Setting up Beeper Linkedin bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:3
+msgid "The playbook can install and configure [beeper-linkedin](https://github.com/beeper/linkedin) for you, for bridging to [LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on the mautrix-python framework and can be configured in a similar way to the other mautrix bridges"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:5
+msgid "See the project's [documentation](https://github.com/beeper/linkedin/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:9
+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-beeper-linkedin.md:15
+msgid "There are some additional things you may wish to configure about the bridge before you continue."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:17
+msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:24
+msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:33
+msgid "You may wish to look at `roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2` to find other things you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:35
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:37
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:44
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:46
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:48
+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-beeper-linkedin.md:50
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:52
+msgid "Set up Double Puppeting by enabling Appservice Double Puppet or Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:54
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:56
+msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:58
+msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:60
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:62
+msgid "To use the bridge, you need to start a chat with `@linkedinbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:64
+msgid "Send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to enable bridging for your LinkedIn account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:66
+msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:68
+msgid "After successfully enabling bridging, you may wish to [set up Double Puppeting](#set-up-double-puppeting-by-enabling-appservice-double-puppet-or-shared-secret-auth), if you haven't already done so."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:70
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:72
+msgid "Bridge asking for 2FA even if you don't have 2FA enabled"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:74
+msgid "If you don't have 2FA enabled and are logging in from a strange IP for the first time, LinkedIn will send an email with a one-time code. You can use this code to authorize the bridge session. In my experience, once the IP is authorized, you will not be asked again."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po
new file mode 100644
index 000000000..4cf9ddce5
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-go-skype-bridge.po
@@ -0,0 +1,77 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:1
+msgid "Setting up Go Skype Bridge bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:3
+msgid "The playbook can install and configure [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:5
+msgid "See the project's [documentation](https://github.com/kelaresg/go-skype-bridge/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:9
+msgid "To enable the [Skype](https://www.skype.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:15
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:17
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:24
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:26
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:28
+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-go-skype-bridge.md:30
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:32
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:34
+msgid "To use the bridge, you need to start a chat with `Skype bridge bot` with the handle `@skypebridgebot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:36
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po
new file mode 100644
index 000000000..ec26b7f68
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-heisenbridge.po
@@ -0,0 +1,129 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:1
+msgid "Setting up Heisenbridge bouncer-style IRC bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:3
+msgid "**Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md) bridge supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:5
+msgid "The playbook can install and configure [Heisenbridge](https://github.com/hifi/heisenbridge) - the bouncer-style [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) bridge for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:7
+msgid "See the project's [documentation](https://github.com/hifi/heisenbridge/blob/master/README.md) to learn what it does and why it might be useful to you. You can also take a look at [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:9
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:11
+msgid "To enable Heisenbridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:24
+msgid "For a more complete list of variables that you could override, see the [`defaults/main.yml` file](../roles/custom/matrix-bridge-heisenbridge/defaults/main.yml) of the Heisenbridge Ansible role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:26
+msgid "Adjusting the Heisenbridge URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:28
+msgid "By default, this playbook installs Heisenbridge on the `matrix.` subdomain, at the `/heisenbridge` path (https://matrix.example.com/heisenbridge). It would handle media requests there (see the [release notes for Heisenbridge v1.15.0](https://github.com/hifi/heisenbridge/releases/tag/v1.15.0))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:30
+msgid "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-bridge-heisenbridge.md:32
+msgid "By tweaking the `matrix_heisenbridge_hostname` and `matrix_heisenbridge_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-bridge-heisenbridge.md:34
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:42
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:44
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Heisenbridge domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:46
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:48
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:50
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:52
+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-bridge-heisenbridge.md:59
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:61
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:63
+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-heisenbridge.md:65
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:67
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:69
+msgid "To use the bridge, you need to start a chat with `@heisenbridge:example.com` (where `example.com` is your base domain, not the `matrix.` domain). If the bridge ignores you and a DM is not accepted then the owner setting may be wrong."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:71
+msgid "Help is available for all commands with the `-h` switch."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:73
+msgid "You can also learn the basics by watching [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:75
+msgid "If you encounter issues or feel lost you can join the project room at [#heisenbridge:vi.fi](https://matrix.to/#/#heisenbridge:vi.fi) for help."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po
new file mode 100644
index 000000000..cd25974f7
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-hookshot.po
@@ -0,0 +1,385 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:1
+msgid "Setting up matrix-hookshot (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:3
+msgid "The playbook can install and configure [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:5
+msgid "Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) from software project management services such as GitHub, GitLab, Jira, and Figma, as well as generic webhooks."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:7
+msgid "See the project's [documentation](https://matrix-org.github.io/matrix-hookshot/latest/hookshot.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:9
+msgid "**Note**: the playbook also supports [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), which however was deprecated by its author."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:13
+msgid "Download GitHub app private key (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:15
+msgid "If you're setting up the GitHub bridge, you need to create your GitHub app, and generate a private key file of it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:17
+msgid "You need to download the private key file, if you will install the file manually or with the `aux` role. For details, see [the section below](#manage-github-private-key-with-aux-role)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:19
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:21
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `GITHUB_PRIVATE_KEY_HERE` with the one created [above](#download-github-app-private-key)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:35
+msgid "For each of the services (GitHub, GitLab, Jira, Figma, and generic webhooks) fill in the respective variables `matrix_hookshot_service_*` listed in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) as required."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:37
+msgid "Take special note of the `matrix_hookshot_*_enabled` variables. Services that need no further configuration are enabled by default (GitLab and generic webhooks), while you must first add the required configuration and enable the others (GitHub, Jira, and Figma)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:39
+msgid "Extending the configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:41
+msgid "You can configure additional options by adding the `matrix_hookshot_configuration_extension_yaml` and `matrix_hookshot_registration_extension_yaml` variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:43
+msgid "Refer the [official instructions](https://matrix-org.github.io/matrix-hookshot/latest/setup.html) and the comments in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) to learn what the individual options do."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:45
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:47
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:54
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service hookshot` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:56
+msgid "`just install-service hookshot` is useful for maintaining your setup quickly 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 `just setup-all` runs the `ensure-matrix-users-created` tag too."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:58
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:60
+msgid "To use the bridge, you need to create a room and invite the Hookshot bot (`@hookshot:example.com`) to it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:62
+msgid "Make sure the bot is able to send state events (usually the Moderator power level in clients)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:64
+msgid "Send `!hookshot help` to the bot to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:66
+msgid "Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-hookshot/latest/usage.html) for more details about using the bridge's various features."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:68
+msgid "💡 **Note**: the different listeners are bound to certain paths which might differ from those assumed by the hookshot documentation. See [URLs for bridges setup](#urls-for-bridges-setup) below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:70
+msgid "Reset crypto store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:72
+msgid "Should the crypto store be corrupted, you can reset it by executing this Ansible playbook with the tag `reset-hookshot-encryption` added:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:78
+msgid "More setup documentation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:80
+msgid "URLs for bridges setup"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:82
+msgid "Unless indicated otherwise, the following endpoints are reachable on your `matrix.` subdomain (if the feature is enabled)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Listener"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Default path"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Variable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Used as"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "-"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/hookshot/webhooks/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_webhook_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Webhook-prefix, which affects all webhook-related URLs below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "generic"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/hookshot/webhooks/webhook`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_generic_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Generic webhooks"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "github oauth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/hookshot/webhooks/oauth`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_github_oauth_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "GitHub \"Callback URL\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "jira oauth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/hookshot/webhooks/jira/oauth`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_jira_oauth_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Jira OAuth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "figma endpoint"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/hookshot/webhooks/figma/webhook`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_figma_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Figma"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "provisioning"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/hookshot/v1/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_provisioning_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Dimension [provisioning](#provisioning-api)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "appservice"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/hookshot/_matrix/app/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_appservice_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Matrix server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "widgets"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/hookshot/widgetapi/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_widgets_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Widgets"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "metrics"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`/metrics/hookshot`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "`matrix_hookshot_metrics_enabled` and exposure enabled via `matrix_hookshot_metrics_proxying_enabled` or `matrix_metrics_exposure_enabled`. Read more in the [Metrics section](#metrics) below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md
+msgid "Prometheus"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:96
+msgid "Also see the various `matrix_hookshot_container_labels_*` variables in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), which expose URLs publicly"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:98
+msgid "The different listeners are also reachable *internally* in the docker-network via the container's name (configured by `matrix_hookshot_container_url`) and on different ports (e.g. `matrix_hookshot_appservice_port`). Read [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) in detail for more info."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:100
+msgid "Manage GitHub Private Key with aux role"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:102
+msgid "The GitHub bridge requires you to install a private key file. This can be done in multiple ways:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:104
+msgid "copy the *contents* of the downloaded file and set the variable `matrix_hookshot_github_private_key` to the contents (see example in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:105
+msgid "somehow copy the file to the path `{{ matrix_hookshot_base_path }}/{{ matrix_hookshot_github_private_key_file }}` (default: `/matrix/hookshot/private-key.pem`) on the server manually."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:106
+msgid "use the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) to copy the file from an arbitrary path on your ansible client to the correct path on the server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:108
+msgid "To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:119
+msgid "For more information, see the documentation in the [default configuration of the aux role](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:121
+msgid "Provisioning API"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:123
+msgid "The provisioning API will be enabled automatically if you set `matrix_dimension_enabled: true` and provided a `matrix_hookshot_provisioning_secret`, unless you override it either way. To use hookshot with dimension, you will need to enter as \"Provisioning URL\": `http://matrix-hookshot:9002`, which is made up of the variables `matrix_hookshot_container_url` and `matrix_hookshot_provisioning_port`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:125
+msgid "Metrics"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:127
+msgid "Metrics are **only enabled by default** if the builtin [Prometheus](configuring-playbook-prometheus-grafana.md) is enabled (by default, Prometheus isn't enabled). If so, metrics will automatically be collected by Prometheus and made available in Grafana. You will, however, need to set up your own Dashboard for displaying them."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:129
+msgid "To explicitly enable metrics, use `matrix_hookshot_metrics_enabled: true`. This only exposes metrics over the container network, however."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:131
+msgid "**To collect metrics from an external Prometheus server**, besides enabling metrics as described above, you will also need to enable metrics exposure on `https://matrix.example.com/metrics/hookshot` by:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:133
+msgid "either enabling metrics exposure for Hookshot via `matrix_hookshot_metrics_proxying_enabled: true`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:134
+msgid "or enabling metrics exposure for all services via `matrix_metrics_exposure_enabled: true`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:136
+msgid "Whichever one you go with, by default metrics are exposed publicly **without** password-protection. See [the Prometheus and Grafana docs](configuring-playbook-prometheus-grafana.md) for details about password-protection for metrics."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:138
+msgid "Collision with matrix-appservice-webhooks"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:140
+msgid "If you are also running [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), it reserves its namespace by the default setting `matrix_appservice_webhooks_user_prefix: '_webhook_'`. You should take care if you modify its or hookshot's prefix that they do not collide with each other's namespace (default `matrix_hookshot_generic_userIdPrefix: '_webhooks_'`)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po
new file mode 100644
index 000000000..6b3ec344e
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-matrix-bridge-sms.po
@@ -0,0 +1,77 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:1
+msgid "Setting up Matrix SMS bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:3
+msgid "The playbook can install and configure [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:5
+msgid "See the project's [documentation](https://github.com/benkuly/matrix-sms-bridge/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:7
+msgid "**The bridge uses [android-sms-gateway-server](https://github.com/RebekkaMa/android-sms-gateway-server). You need to configure it first.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:11
+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-matrix-bridge-sms.md:34
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:36
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:43
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:45
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:47
+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-matrix-bridge-sms.md:49
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:51
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:53
+msgid "Read the [user guide](https://github.com/benkuly/matrix-sms-bridge/blob/master/README.md#user-guide) to see how this bridge works."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po
new file mode 100644
index 000000000..c37fee3cc
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-discord.po
@@ -0,0 +1,245 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:1
+msgid "Setting up Mautrix Discord bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:3
+msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md) bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:4
+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:5
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:7
+msgid "The playbook can install and configure [mautrix-discord](https://github.com/mautrix/discord) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:9
+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:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:13
+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)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:15
+msgid "If this is a dealbreaker for you, consider using one of the other Discord bridges supported by the playbook: [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) or [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md). These come with their own complexity and limitations, however, so we recommend that you proceed with this one if possible."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:17
+msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:19
+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:21
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:23
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:25
+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:31
+msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:33
+msgid "Additional configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:35
+msgid "There are some additional things you may wish to configure about the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:37
+msgid "Take a look at:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:39
+msgid "`roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:40
+msgid "`roles/custom/matrix-bridge-mautrix-discord/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_mautrix_discord_configuration_extension_yaml` variable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:42
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:44
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:51
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:53
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.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-discord.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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:59
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:61
+msgid "Logging in"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:63
+msgid "Method 1: Login using QR code (recommended)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:65
+msgid "For using this bridge, you would need to authenticate by **scanning a QR code** with the Discord app on your phone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:67
+msgid "You can delete the Discord app after the authentication process."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:69
+msgid "Method 2: Login using Discord token (not recommended)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:71
+msgid "To acquire the token, open Discord in a private browser window. Then open the developer settings (keyboard shortcut might be \"ctrl+shift+i\" or by pressing \"F12\"). Navigate to the \"Network\" tab then reload the page. In the URL filter or search bar type \"/api\" and find the response with the file name of \"library\". Under the request headers you should find a variable called \"Authorization\", this is the token to your Discord account. After copying the token, you can close the browser window."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:73
+msgid "Bridging"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:75
+msgid "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:76
+msgid "If you would like to login to Discord using a token, send `login-token` command, otherwise, send `login-qr` command."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:77
+msgid "You'll see a QR code which you need to scan with the Discord app on your phone. You can scan it with the camera app too, which will open Discord, which will then instruct you to scan it a 2nd time in the Discord app."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:78
+msgid "After confirming (in the Discord app) that you'd like to allow this login, the bot should respond with \"Succcessfully authenticated as …\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:79
+msgid "Now that you're logged in, you can send `help` to the bot to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:80
+msgid "Some Direct Messages from Discord should start syncing automatically"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:81
+msgid "If you'd like to bridge guilds:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:82
+msgid "send `guilds status` to see the list of guilds"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:83
+msgid "for each guild that you'd like bridged, send `guilds bridge GUILD_ID --entire`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:84
+msgid "You may wish to uninstall the Discord app from your phone now. It's not needed for the bridge to function."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:86
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:88
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:90
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:92
+msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:94
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:96
+msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:98
+msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:100
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:102
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:104
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:106
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:108
+msgid "make sure you don't log out the `Mautrix-Discord` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po
new file mode 100644
index 000000000..bb31537fd
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-facebook.po
@@ -0,0 +1,201 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:1
+msgid "Setting up Mautrix Facebook bridging (optional, deprecated)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:3
+msgid "**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md). Consider using that bridge instead of this one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:5
+msgid "The playbook can install and configure [mautrix-facebook](https://github.com/mautrix/facebook) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:7
+msgid "See the project's [documentation](https://github.com/mautrix/facebook/blob/master/ROADMAP.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:9
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:11
+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 [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:13
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:15
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:17
+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-facebook.md:23
+msgid "There are some additional things you may wish to configure about the bridge before you continue."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:25
+msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:35
+msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:44
+msgid "Using both would look like"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:56
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml` to find other things you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:58
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:60
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:67
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:69
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:71
+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-facebook.md:73
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:75
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:77
+msgid "To use the bridge, you need to start a chat with `@facebookbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:79
+msgid "Send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable bridging for your Facebook Messenger account. You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/facebook/authentication.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:81
+msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:83
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:85
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:87
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:89
+msgid "Method 1: automatically, by enabling Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:91
+msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:93
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:95
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:97
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:99
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:101
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:103
+msgid "make sure you don't log out the `Mautrix-Facebook` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:105
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:107
+msgid "Facebook rejecting login attempts and forcing you to change password"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:109
+msgid "If your Matrix server is in a wildly different location than where you usually use your Facebook account from, the bridge's login attempts may be outright rejected by Facebook. Along with that, Facebook may even force you to change the account's password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:111
+msgid "If you happen to run into this problem while [setting up bridging](#usage), try to first get a successful session up by logging in to Facebook through the Matrix server's IP address."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:113
+msgid "The easiest way to do this may be to use [sshuttle](https://sshuttle.readthedocs.io/) to proxy your traffic through the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:115
+msgid "Example command for proxying your traffic through the Matrix server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:121
+msgid "Once connected, you should be able to verify that you're browsing the web through the Matrix server's IP by checking [icanhazip](https://icanhazip.com/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:123
+msgid "Then proceed to log in to [Facebook/Messenger](https://www.facebook.com/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:125
+msgid "Once logged in, proceed to [set up bridging](#usage)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:127
+msgid "If that doesn't work, enable 2FA (see: [Facebook help page on enabling 2FA](https://www.facebook.com/help/148233965247823)) and try to login again with a new password, and entering the 2FA code when prompted, it may take more then one try, in between attempts, check facebook.com to see if they are requiring another password change"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po
new file mode 100644
index 000000000..9ddab67b7
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-gmessages.po
@@ -0,0 +1,129 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:1
+msgid "Setting up Mautrix Google Messages bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:3
+msgid "The playbook can install and configure [mautrix-gmessages](https://github.com/mautrix/gmessages) for you, for bridging to [Google Messages](https://messages.google.com/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:5
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/gmessages/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:7
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:9
+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) for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:11
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:15
+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-gmessages.md:21
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:23
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:30
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:32
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:34
+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-gmessages.md:36
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:38
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:40
+msgid "To use the bridge, you need to start a chat with `@gmessagesbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:42
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:44
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:46
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:48
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:50
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:52
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:54
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:56
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:58
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:60
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:62
+msgid "make sure you don't log out the `Mautrix-gmessages` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po
new file mode 100644
index 000000000..843db4c5a
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-googlechat.po
@@ -0,0 +1,149 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:1
+msgid "Setting up Mautrix Google Chat bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:3
+msgid "The playbook can install and configure [mautrix-googlechat](https://github.com/mautrix/googlechat) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:5
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/googlechat/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:7
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:9
+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-googlechat.md:11
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:15
+msgid "To enable the [Google Chat](https://chat.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:21
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:23
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:30
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:32
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:34
+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-googlechat.md:36
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:38
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:40
+msgid "To use the bridge, you need to start a chat with `googlechat bridge bot` with handle `@googlechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:42
+msgid "Send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:44
+msgid "Automatic login may not work. If it does not, reload the page and select the \"Manual login\" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:46
+msgid "Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:48
+msgid "You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:50
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:52
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:54
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:56
+msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:58
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:60
+msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:62
+msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:64
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:66
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:68
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:70
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:72
+msgid "make sure you don't log out the `Mautrix-googlechat` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po
new file mode 100644
index 000000000..1bfea7e5b
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-hangouts.po
@@ -0,0 +1,149 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:1
+msgid "Setting up Mautrix Hangouts bridging (optional, deprecated)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:3
+msgid "💡 **Note**: This bridge has been deprecated in favor of [Google Chat bridge](https://github.com/mautrix/googlechat), which can be installed using [this playbook](configuring-playbook-bridge-mautrix-googlechat.md). Installing the mautrix-hangouts bridge is **no longer possible**. For now, this documentation page remains here for historical purposes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:5
+msgid "The playbook can install and configure [mautrix-hangouts](https://github.com/mautrix/hangouts) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:7
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/hangouts/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:9
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:11
+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 [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:13
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:15
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:17
+msgid "To enable the [Google Hangouts](https://hangouts.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:23
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:25
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:32
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:34
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:36
+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-hangouts.md:38
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:40
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:42
+msgid "To use the bridge, you need to start a chat with `Hangouts bridge bot` with handle `@hangoutsbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:44
+msgid "Send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:46
+msgid "Automatic login may not work. If it does not, reload the page and select the \"Manual login\" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:48
+msgid "Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:50
+msgid "You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/hangouts/authentication.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:52
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:54
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:56
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:58
+msgid "Method 1: automatically, by enabling Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:60
+msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:62
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:64
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:66
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:68
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:70
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:72
+msgid "make sure you don't log out the `Mautrix-Hangouts` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po
new file mode 100644
index 000000000..6072174c9
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-instagram.po
@@ -0,0 +1,101 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:1
+msgid "Setting up Mautrix Instagram bridging (optional, deprecated)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:3
+msgid "**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-instagram.md). Consider using that bridge instead of this one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:5
+msgid "The playbook can install and configure [mautrix-instagram](https://github.com/mautrix/instagram) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:7
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/instagram/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:11
+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-instagram.md:17
+msgid "There are some additional things you may wish to configure about the bridge before you continue."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:19
+msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:29
+msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:43
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml` to find other things you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:45
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:47
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:54
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:56
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:58
+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-instagram.md:60
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:62
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:64
+msgid "To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:66
+msgid "Send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the bridge bot to enable bridging for your instagram/Messenger account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:68
+msgid "You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/instagram/authentication.html)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po
new file mode 100644
index 000000000..162d6c528
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-instagram.po
@@ -0,0 +1,209 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:1
+msgid "Setting up Instagram bridging via Mautrix Meta (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:3
+msgid "The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:5
+msgid "Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:7
+msgid "This documentation page only deals with the bridge's ability to bridge to Instagram. For bridging to Facebook/Messenger, see [Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:11
+msgid "Migrating from the old mautrix-instagram bridge"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:13
+msgid "If you've been using the [mautrix-instagram](./configuring-playbook-bridge-mautrix-instagram.md) bridge, **you'd better get rid of it first** or the 2 bridges will be in conflict:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:15
+msgid "both trying to use `@instagrambot:example.com` as their username. This conflict may be resolved by adjusting `matrix_mautrix_instagram_appservice_bot_username` or `matrix_mautrix_meta_instagram_appservice_username`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:16
+msgid "both trying to bridge the same DMs"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:18
+msgid "To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@instagrambot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:20
+msgid "Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:22
+msgid "Enable Appservice Double Puppet (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:24
+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-meta-instagram.md:26
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:28
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:30
+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-meta-instagram.md:36
+msgid "Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:38
+msgid "Bridge permissions"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:40
+msgid "By default, any user on your homeserver will be able to use the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:42
+msgid "Different levels of permission can be granted to users:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:44
+msgid "`relay` - Allowed to be relayed through the bridge, no access to commands"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:45
+msgid "`user` - Use the bridge with puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:46
+msgid "`admin` - Use and administer the bridge"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:48
+msgid "The permissions are following the sequence: nothing < `relay` < `user` < `admin`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:50
+msgid "The default permissions are set via `matrix_mautrix_meta_instagram_bridge_permissions_default` and are somewhat like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:59
+msgid "If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:61
+msgid "You may redefine `matrix_mautrix_meta_instagram_bridge_permissions_default` any way you see fit, or add extra permissions using `matrix_mautrix_meta_instagram_bridge_permissions_custom` like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:68
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-instagram/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:70
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:72
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:79
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:81
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:83
+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-meta-instagram.md:85
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:87
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:89
+msgid "To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:91
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:93
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:95
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:97
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:99
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:101
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:103
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:105
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:107
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:109
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:111
+msgid "make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po
new file mode 100644
index 000000000..62e9ae19b
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-meta-messenger.po
@@ -0,0 +1,245 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:1
+msgid "Setting up Messenger bridging via Mautrix Meta (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:3
+msgid "The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:5
+msgid "Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:7
+msgid "This documentation page only deals with the bridge's ability to bridge to Facebook Messenger. For bridging to Instagram, see [Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:11
+msgid "Migrating from the old mautrix-facebook bridge"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:13
+msgid "If you've been using the [mautrix-facebook](./configuring-playbook-bridge-mautrix-facebook.md) bridge, it's possible to migrate the database using [instructions from the bridge documentation](https://docs.mau.fi/bridges/go/meta/facebook-migration.html) (advanced)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:15
+msgid "Then you may wish to get rid of the Facebook bridge. To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@facebookbot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:17
+msgid "Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:19
+msgid "**Note**: the user ID of the new bridge bot is `@messengerbot:example.com`, not `@facebookbot:example.com`. After disabling the old bridge, its bot user will stop responding to a command."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:21
+msgid "Enable Appservice Double Puppet (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:23
+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-meta-messenger.md:25
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:27
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:29
+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-meta-messenger.md:35
+msgid "Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:37
+msgid "Bridge mode"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:39
+msgid "As mentioned above, the [mautrix-meta](https://github.com/mautrix/meta) bridge supports multiple modes of operation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:41
+msgid "The bridge can pull your Messenger messages via 3 different methods:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:43
+msgid "(`facebook`) Facebook via `facebook.com`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:44
+msgid "(`facebook-tor`) Facebook via `facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion` ([Tor](https://www.torproject.org/)) - does not currently proxy media downloads"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:45
+msgid "(default) (`messenger`) Messenger via `messenger.com` - usable even without a Facebook account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:47
+msgid "You may switch the mode via the `matrix_mautrix_meta_messenger_meta_mode` variable. The playbook defaults to the `messenger` mode, because it's most universal (every Facebook user has a Messenger account, but the opposite is not true)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:49
+msgid "Note that switching the mode (especially between `facebook*` and `messenger`) will intentionally make the bridge use another database (`matrix_mautrix_meta_facebook` or `matrix_mautrix_meta_messenger`) to isolate the 2 instances. Switching between Tor and non-Tor may be possible without dataloss, but your mileage may vary. Before switching to a new mode, you may wish to de-configure the old one (send `help` to the bridge bot and unbridge your portals, etc.)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:51
+msgid "Bridge permissions"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:53
+msgid "By default, any user on your homeserver will be able to use the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:55
+msgid "Different levels of permission can be granted to users:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:57
+msgid "`relay` - Allowed to be relayed through the bridge, no access to commands"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:58
+msgid "`user` - Use the bridge with puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:59
+msgid "`admin` - Use and administer the bridge"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:61
+msgid "The permissions are following the sequence: nothing < `relay` < `user` < `admin`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:63
+msgid "The default permissions are set via `matrix_mautrix_meta_messenger_bridge_permissions_default` and are somewhat like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:72
+msgid "If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:74
+msgid "You may redefine `matrix_mautrix_meta_messenger_bridge_permissions_default` any way you see fit, or add extra permissions using `matrix_mautrix_meta_messenger_bridge_permissions_custom` like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:81
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:83
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:85
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:92
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:94
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:96
+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-meta-messenger.md:98
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:100
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:102
+msgid "To use the bridge, you need to start a chat with `@messengerbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). Note that the user ID of the bridge's bot is not `@facebookbot:example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:104
+msgid "You then need to send a `login` command and follow the bridge bot's instructions."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:106
+msgid "Given that the bot is configured in `messenger` [bridge mode](#bridge-mode) by default, you will need to log in to [messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain the cookies from there as per [the bridge's authentication instructions](https://docs.mau.fi/bridges/go/meta/authentication.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:108
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:110
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:112
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:114
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:116
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:118
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:120
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:122
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:124
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:126
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:128
+msgid "make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po
new file mode 100644
index 000000000..cd3278b10
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-signal.po
@@ -0,0 +1,197 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:1
+msgid "Setting up Mautrix Signal bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:3
+msgid "The playbook can install and configure [mautrix-signal](https://github.com/mautrix/signal) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:5
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/signal/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:7
+msgid "**Note**: This revamped version of the [mautrix-signal (legacy)](configuring-playbook-bridge-mautrix-signal.md) may increase the CPU usage of your homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:9
+msgid "Prerequisites (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:11
+msgid "Prepare Postgres database on external Postgres server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:13
+msgid "If you're running with the Postgres database server integrated by the playbook (which is the default), you don't need to do anything special and can easily proceed with installing."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:15
+msgid "However, if you're [using an external Postgres server](configuring-playbook-external-postgres.md), you'd need to manually prepare a Postgres database for this bridge and adjust the variables related to that (`matrix_mautrix_signal_database_*`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:17
+msgid "Enable Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:19
+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-signal.md:21
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:23
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:25
+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-signal.md:31
+msgid "There are some additional things you may wish to configure about the bridge before you continue."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:33
+msgid "By default, any user on your homeserver will be able to use the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:35
+msgid "Different levels of permission can be granted to users:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:37
+msgid "relay - Allowed to be relayed through the bridge, no access to commands;"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:38
+msgid "user - Use the bridge with puppeting;"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:39
+msgid "admin - Use and administer the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:41
+msgid "The permissions are following the sequence: nothing < relay < user < admin."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:43
+msgid "The default permissions are set as follows:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:51
+msgid "If you want to augment the preset permissions, you might want to set the additional permissions with the following settings in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:60
+msgid "This will add the admin permission to the specific user, while keeping the default permissions."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:62
+msgid "In case you want to replace the default permissions settings **completely**, populate the following item within your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:70
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-signal/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:72
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:74
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:81
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:83
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:85
+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-signal.md:87
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:89
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:91
+msgid "To use the bridge, you need to start a chat with `@signalbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:93
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:95
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:97
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:99
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:101
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:103
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:105
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:107
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:109
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:111
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:113
+msgid "make sure you don't log out the `Mautrix-Signal` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po
new file mode 100644
index 000000000..13eb94f02
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-slack.po
@@ -0,0 +1,197 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:1
+msgid "Setting up Mautrix Slack bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:3
+msgid "**Note**: bridging to [Slack](https://slack.com/) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:4
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:5
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:7
+msgid "The playbook can install and configure [mautrix-slack](https://github.com/mautrix/slack) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:9
+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:11
+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:13
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:15
+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:17
+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:19
+msgid "Enable Appservice Double Puppet (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:21
+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:23
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:25
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:27
+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:33
+msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:35
+msgid "Additional configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:37
+msgid "There are some additional options you may wish to configure with the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:39
+msgid "Take a look at:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:41
+msgid "`roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:42
+msgid "`roles/custom/matrix-bridge-mautrix-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_mautrix_slack_configuration_extension_yaml` variable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:44
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:46
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:53
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:55
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:57
+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:59
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:61
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:63
+msgid "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:64
+msgid "If you would like to login to Slack using a token, send the `login-token` command, otherwise, send the `login-password` command. Read [here](https://docs.mau.fi/bridges/go/slack/authentication.html) on how to retrieve your token and cookie token."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:65
+msgid "The bot should respond with \"Successfully logged into <email> for team <workspace>\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:66
+msgid "Now that you're logged in, you can send `help` to the bot to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:67
+msgid "Slack channels should automatically begin bridging if you authenticated using a token. Otherwise, you must wait to receive a message in the channel if you used password authentication."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:69
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:71
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:73
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:75
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:77
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:79
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:81
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:83
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:85
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:87
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:89
+msgid "make sure you don't log out the `Mautrix-Slack` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po
new file mode 100644
index 000000000..1246af68f
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po
@@ -0,0 +1,153 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:1
+msgid "Setting up Mautrix Telegram bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:3
+msgid "The playbook can install and configure [mautrix-telegram](https://github.com/mautrix/telegram) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:5
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/telegram/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:7
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:9
+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-telegram.md:11
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:15
+msgid "You'll need to obtain API keys from [https://my.telegram.org/apps](https://my.telegram.org/apps) and then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:23
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:25
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:32
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:34
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:36
+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-telegram.md:38
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:40
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:42
+msgid "To use the bridge, you need to start a chat with `@telegrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:44
+msgid "If you want to use the relay-bot feature ([relay bot documentation](https://docs.mau.fi/bridges/python/telegram/relay-bot.html)), which allows anonymous user to chat with telegram users, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:54
+msgid "You might also want to give permissions to administrate the bot:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:63
+msgid "More details about permissions in this example: https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-config.yaml#L410"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:65
+msgid "If you like to exclude all groups from syncing and use the Telgeram-Bridge only for direct chats, you can add the following additional playbook configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:71
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:73
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:75
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:77
+msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:79
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:81
+msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:83
+msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:85
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:87
+msgid "**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:89
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:91
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:93
+msgid "send `login-matrix` to the bot and follow instructions about how to send the access token to it"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:95
+msgid "make sure you don't log out the `Mautrix-Telegram` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po
new file mode 100644
index 000000000..f2c461f42
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-twitter.po
@@ -0,0 +1,145 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:1
+msgid "Setting up Mautrix Twitter bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:3
+msgid "**Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md) bridge supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:5
+msgid "The playbook can install and configure [mautrix-twitter](https://github.com/mautrix/twitter) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:7
+msgid "See the project's [documentation](https://github.com/mautrix/twitter/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:9
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:11
+msgid "Enable Appservice Double Puppet (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:13
+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-twitter.md:15
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:17
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:19
+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-twitter.md:25
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:27
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:38
+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-twitter.md:40
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:42
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:44
+msgid "You then need to start a chat with `@twitterbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:45
+msgid "Send login-cookie to start the login. The bot should respond with instructions on how to proceed."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:47
+msgid "You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/twitter/authentication.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:49
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:51
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:53
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:55
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:57
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:59
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:61
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:63
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:65
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:67
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:69
+msgid "make sure you don't log out the `Mautrix-Slack` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po
new file mode 100644
index 000000000..2e12be38c
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-whatsapp.po
@@ -0,0 +1,149 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:1
+msgid "Setting up Mautrix Whatsapp bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:3
+msgid "The playbook can install and configure [mautrix-whatsapp](https://github.com/mautrix/whatsapp) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:5
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/whatsapp/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:7
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:9
+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-whatsapp.md:11
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:15
+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-whatsapp.md:21
+msgid "Whatsapp multidevice beta is required, now it is enough if Whatsapp is connected to the Internet every 2 weeks."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:23
+msgid "The relay bot functionality is off by default. If you would like to enable the relay bot, add the following to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:29
+msgid "By default, only admins are allowed to set themselves as relay users. To allow anyone on your homeserver to set themselves as relay users add this to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:35
+msgid "If you want to activate the relay bot in a room, send `!wa set-relay`. To deactivate, send `!wa unset-relay`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:37
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:39
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:46
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:48
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:50
+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-whatsapp.md:52
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:54
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:56
+msgid "To use the bridge, you need to start a chat with `@whatsappbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:58
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:60
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:62
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:64
+msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:66
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:68
+msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:70
+msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:72
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:74
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:76
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:78
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:80
+msgid "make sure you don't log out the `Mautrix-Whatsapp` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po
new file mode 100644
index 000000000..ff93dfd70
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-wsproxy.po
@@ -0,0 +1,105 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:1
+msgid "Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:3
+msgid "The playbook can install and configure [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:5
+msgid "See the project's [documentation](https://github.com/mautrix/wsproxy/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:9
+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-wsproxy.md:21
+msgid "Note that the tokens must match what is compiled into the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android device."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:23
+msgid "Adjusting the wsproxy URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:25
+msgid "By default, this playbook installs wsproxy on the `wsproxy.` subdomain (`wsproxy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:27
+msgid "By tweaking the `matrix_mautrix_wsproxy_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:29
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:36
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:38
+msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the wsproxy domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:40
+msgid "By default, you will need to create a CNAME record for `wsproxy`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:42
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:44
+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-bridge-mautrix-wsproxy.md:51
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:53
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.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-wsproxy.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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:59
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:61
+msgid "Follow the [matrix-imessage documenation](https://docs.mau.fi/bridges/go/imessage/index.html) for running `android-sms` and/or `matrix-imessage` on your device(s)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po
new file mode 100644
index 000000000..fc6d17c55
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-discord.po
@@ -0,0 +1,101 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:1
+msgid "Setting up MX Puppet Discord bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:3
+msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md)and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:4
+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-mx-puppet-discord.md:5
+msgid "For personal use with a discord account we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:7
+msgid "The playbook can install and configure [mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:9
+msgid "See the project's [documentation](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:13
+msgid "To enable the [Discord](https://discordapp.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:19
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:21
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:28
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:30
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:32
+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-mx-puppet-discord.md:34
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:36
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:38
+msgid "To use the bridge, you need to start a chat with `Discord Puppet Bridge` with the handle `@_discordpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:40
+msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-discord [documentation](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) for more information about how to configure the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:42
+msgid "Once logged in, send `list` to the bot user to list the available rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:44
+msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:46
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po
new file mode 100644
index 000000000..c59253dc7
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-groupme.po
@@ -0,0 +1,93 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:1
+msgid "Setting up MX Puppet GroupMe bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:3
+msgid "The playbook can install and configure [mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:5
+msgid "See the project's [documentation](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:9
+msgid "To enable the [GroupMe](https://groupme.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:15
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:17
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:24
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:26
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:28
+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-mx-puppet-groupme.md:30
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:32
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:34
+msgid "To use the bridge, you need to start a chat with `GroupMe Puppet Bridge` with the handle `@_groupmepuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:36
+msgid "One authentication method is available."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:38
+msgid "To link your GroupMe account, go to [dev.groupme.com](https://dev.groupme.com/), sign in, and select \"Access Token\" from the top menu. Copy the token and message the bridge with:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:44
+msgid "Once logged in, send `listrooms` to the bot user to list the available rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:46
+msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:48
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po
new file mode 100644
index 000000000..3b479cfdc
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-instagram.po
@@ -0,0 +1,105 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:1
+msgid "Setting up MX Puppet Instagram bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:3
+msgid "The playbook can install and configure [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:5
+msgid "This allows you to bridge Instagram DirectMessages into Matrix."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:9
+msgid "To enable the [Instagram](https://www.instagram.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:15
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:17
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:24
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:26
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:28
+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-mx-puppet-instagram.md:30
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:32
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:34
+msgid "To use the bridge, you need to start a chat with `Instagram Puppet Bridge` with the handle `@_instagrampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:36
+msgid "Send `link <username> <password>` to the bridge bot to link your instagram account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:38
+msgid "The `list` commands shows which accounts are linked and which `puppetId` is associated."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:40
+msgid "For double-puppeting, you probably want to issue these commands:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:42
+msgid "`settype $puppetId puppet` to enable puppeting for the link (instead of relaying)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:43
+msgid "`setautoinvite $puppetId 1` to automatically invite you to chats"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:44
+msgid "`setmatrixtoken $accessToken` to set the access token to enable puppeting from the other side (the \"double\" in double puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:46
+msgid "If you are linking only one Instagram account, your `$puppetId` is probably 1, but use the `list` command find out."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:48
+msgid "Send `help` to the bot to see the available commands. At the time of writing, not every command is fully implemented."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po
new file mode 100644
index 000000000..7d7cd399b
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-skype.po
@@ -0,0 +1,33 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:1
+msgid "Setting up MX Puppet Skype bridging (optional, removed)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:3
+msgid "The playbook used to be able to install and configure [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype), but no longer includes this component, because it has been broken and unmaintained for a long time."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:5
+msgid "Bridging to [Skype](https://www.skype.com/) can also happen via the [go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md) bridge supported by the playbook."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po
new file mode 100644
index 000000000..9b7f2c028
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-slack.po
@@ -0,0 +1,101 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:1
+msgid "Setting up MX Puppet Slack bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:3
+msgid "**Note**: bridging to [Slack](https://slack.com) can also happen via the [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook. Note that `matrix-appservice-slack` 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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:5
+msgid "The playbook can install and configure [mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:7
+msgid "See the project's [documentation](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:9
+msgid "Prerequisite"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:11
+msgid "Follow the [OAuth credentials](https://gitlab.com/mx-puppet/slack/mx-puppet-slack#option-2-oauth) instructions to create a new Slack app, setting the redirect URL to `https://matrix.example.com/slack/oauth`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:15
+msgid "To enable the [Slack](https://slack.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:24
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:26
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:33
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:35
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:37
+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-mx-puppet-slack.md:39
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:41
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:43
+msgid "To use the bridge, you need to start a chat with `Slack Puppet Bridge` with the handle `@_slackpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:45
+msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-slack [documentation](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for more information about how to configure the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:47
+msgid "Once logged in, send `list` to the bot user to list the available rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:49
+msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:51
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po
new file mode 100644
index 000000000..9b162ca65
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-steam.po
@@ -0,0 +1,89 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:1
+msgid "Setting up MX Puppet Steam bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:3
+msgid "The playbook can install and configure [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:5
+msgid "See the project's [documentation](https://github.com/icewind1991/mx-puppet-steam/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:9
+msgid "To enable the [Steam](https://steampowered.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:15
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:17
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:24
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:26
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:28
+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-mx-puppet-steam.md:30
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:32
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:34
+msgid "To use the bridge, you need to start a chat with `Steam Puppet Bridge` with the handle `@_steampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:36
+msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-steam [documentation](https://github.com/icewind1991/mx-puppet-steam) for more information about how to configure the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:38
+msgid "Once logged in, send `list` to the bot user to list the available rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:40
+msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:42
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po
new file mode 100644
index 000000000..00f617467
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mx-puppet-twitter.po
@@ -0,0 +1,101 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:1
+msgid "Setting up MX Puppet Twitter bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:3
+msgid "**Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mautrix-twitter](configuring-playbook-bridge-mautrix-twitter.md) bridge supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:5
+msgid "The playbook can install and configure [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:7
+msgid "See the project's [documentation](https://github.com/Sorunome/mx-puppet-twitter/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:9
+msgid "Prerequisite"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:11
+msgid "Make an app on [developer.twitter.com](https://developer.twitter.com/en/apps)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:15
+msgid "To enable the [Twitter](https://twitter.com) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:26
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:28
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:35
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:37
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:39
+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-mx-puppet-twitter.md:41
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:43
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:45
+msgid "To use the bridge, you need to start a chat with `Twitter Puppet Bridge` with the handle `@_twitterpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:47
+msgid "To log in, use `link` and click the link."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:49
+msgid "Once logged in, send `list` to the bot user to list the available rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:51
+msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:53
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po
new file mode 100644
index 000000000..6e8b01d9e
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po
@@ -0,0 +1,141 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:1
+msgid "Setting up Postmoogle email bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:3
+msgid "**Note**: email bridging can also happen via the [email2matrix](configuring-playbook-email2matrix.md) bridge supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:5
+msgid "The playbook can install and configure [Postmoogle](https://github.com/etkecc/postmoogle) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:7
+msgid "Postmoogle is a bridge you can use to have its bot user forward emails to Matrix rooms. It runs an SMTP email server and allows you to assign mailbox addresses to the rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:9
+msgid "See the project's [documentation](https://github.com/etkecc/postmoogle/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:13
+msgid "Open the following ports on your server to be able to receive incoming emails:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:15
+msgid "`25/tcp`: SMTP"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:16
+msgid "`587/tcp`: Submission (TLS-encrypted SMTP)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:18
+msgid "If you don't open these ports, you will still be able to send emails, but not receive any."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:20
+msgid "These port numbers are configurable via the `matrix_postmoogle_smtp_host_bind_port` and `matrix_postmoogle_submission_host_bind_port` variables, but other email servers will try to deliver on these default (standard) ports, so changing them is of little use."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:22
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:24
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:45
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:47
+msgid "You will also need to add several DNS records so that Postmoogle can send emails. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:49
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:51
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:58
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:60
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create a user account of the bridge's bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:62
+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-postmoogle.md:64
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:66
+msgid "If you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:68
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:70
+msgid "To use the bridge, invite the `@postmoogle:example.com` bot user into a room you want to use as a mailbox."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:72
+msgid "Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with the email address `NAME@matrix.example.com`. Emails sent to that email address will be forwarded to the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:74
+msgid "Send `!pm help` to the bot in the room to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:76
+msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/postmoogle)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:78
+msgid "Debug/Logs"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:80
+msgid "As with all other services, you can find their logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-postmoogle`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:82
+msgid "The default logging level for this bridge is `INFO`, but you can increase it to `DEBUG` with the following additional configuration:"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po
new file mode 100644
index 000000000..40bd7b501
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-wechat.po
@@ -0,0 +1,77 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:1
+msgid "Setting up WeChat bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:3
+msgid "The playbook can install and configure the [matrix-wechat](https://github.com/duo/matrix-wechat) bridge for you (for bridging to the [WeChat](https://www.wechat.com/) network)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:5
+msgid "See the project's [documentation](https://github.com/duo/matrix-wechat/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:9
+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-wechat.md:15
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:17
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:24
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:26
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:28
+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-wechat.md:30
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:32
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:34
+msgid "Once the bridge is installed, start a chat with `@wechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:36
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po
new file mode 100644
index 000000000..77b63cfc0
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-cactus-comments.po
@@ -0,0 +1,169 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 23:17+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:1
+msgid "Setting up Cactus Comments (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:3
+msgid "The playbook can install and configure the [Cactus Comments](https://cactus.chat) system for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:5
+msgid "Cactus Comments is a **federated comment system** built on Matrix. It respects your privacy, and puts you in control."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:7
+msgid "See the project's [documentation](https://cactus.chat/docs/getting-started/introduction/) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:9
+msgid "The playbook contains 2 roles for configuring different pieces of the Cactus Comments system:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:11
+msgid "`matrix-cactus-comments` - the backend appservice integrating with the Matrix homeserver"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:13
+msgid "`matrix-cactus-comments-client` - a static website server serving the [cactus-client](https://cactus.chat/docs/client/introduction/) static assets (`cactus.js` and `styles.css`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:15
+msgid "You can enable whichever component you need (typically both)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:17
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:19
+msgid "To enable Cactus Comments, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:41
+msgid "Adjusting the Cactus Comments' client URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:43
+msgid "By default, this playbook installs Cactus Comments' client on the `matrix.` subdomain, at the `/cactus-comments` path (https://matrix.example.com/cactus-comments). 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-cactus-comments.md:45
+msgid "By tweaking the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_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-cactus-comments.md:47
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:56
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:58
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Cactus Comments' client domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:60
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:62
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:64
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:66
+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-cactus-comments.md:73
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:75
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:77
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:79
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:81
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:83
+msgid "Upon starting Cactus Comments, a `bot.cactusbot` user account is created automatically."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:85
+msgid "To get started, send `help` to the `@bot.cactusbot:example.com` bot to confirm it's working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:87
+msgid "Then, register a site by sending `register <YourSiteName>` (where `<YourSiteName>` is a unique identifier you choose. It does not have to match your domain). You will then be invited into a moderation room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:89
+msgid "Now you are good to go and can embed the comment section on your website!"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:91
+msgid "Embed Cactus Comments"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:93
+msgid "The official [documentation](https://cactus.chat/docs/getting-started/quick-start/) provides a useful guide to embed Cactus Comments on your website."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:95
+msgid "After including the JavaScript and CSS asset files, insert a `<div>` where you'd like to display the comment section:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:101
+msgid "Then, you need to initialize the comment section. Make sure to replace `example.com` with your base domain and `<YourSiteName>` with the one that has been registered above:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:115
+msgid "Adjust the domain name for self-hosting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:117
+msgid "To have the assets served from your homeserver (not from `cactus.chat`), you need to adjust the domain name on the official documentation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:119
+msgid "Make sure to replace `example.com` with your base domain before you include the following lines, instead of the one provided by the official documentation:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:126
+msgid "**Note**: if the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_path_prefix` variables are tweaked, you would need to adjust the URLs of the assets accordingly."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-cinny.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-cinny.po
new file mode 100644
index 000000000..8e8c3fdad
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-cinny.po
@@ -0,0 +1,101 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-client-cinny.md:1
+msgid "Setting up Cinny (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:3
+msgid "This playbook can install the [Cinny](https://github.com/ajbura/cinny) Matrix web client for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:5
+msgid "Cinny 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)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:7
+msgid "💡 **Note**: the latest version of Cinny is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:9
+msgid "[app.cinny.in](https://app.cinny.in), hosted by the [Cinny](https://cinny.in/) developers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:13
+msgid "To enable Cinny, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:19
+msgid "Adjusting the Cinny URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:21
+msgid "By default, this playbook installs Cinny on the `cinny.` subdomain (`cinny.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:23
+msgid "By tweaking the `matrix_client_cinny_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:25
+msgid "While a `matrix_client_cinny_path_prefix` variable exists for tweaking the path-prefix, it's [not supported anymore](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Cinny requires an application rebuild (with a tweaked build config) to be functional under a custom path."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:27
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:34
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:36
+msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the Cinny domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:38
+msgid "By default, you will need to create a CNAME record for `cinny`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:40
+msgid "If you've adjusted `matrix_client_cinny_hostname`, you will need to adjust your DNS configuration accordingly."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:42
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:44
+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-cinny.md:51
+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-cinny.md:53
+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 ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-element-web.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-element-web.po
new file mode 100644
index 000000000..8ac70be44
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-element-web.po
@@ -0,0 +1,149 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-client-element-web.md:1
+msgid "Configuring Element Web (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:3
+msgid "By default, this playbook installs the [Element Web](https://github.com/element-hq/element-web) Matrix client for you. If that's okay, you can skip this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:5
+msgid "💡 **Note**: the latest version of Element Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting (by [disabling Element Web](#disabling-element-web)):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:7
+msgid "[app.element.io](https://app.element.io/), hosted by [Element](https://element.io/)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:8
+msgid "[app.etke.cc](https://app.etke.cc/), hosted by [etke.cc](https://etke.cc/)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:10
+msgid "Disabling Element Web"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:12
+msgid "If you'd like for the playbook to not install Element Web (or to uninstall it if it was previously installed), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:18
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:20
+msgid "The playbook provides some customization variables you could use to change Element Web's settings."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:22
+msgid "Their defaults are defined in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml) and they ultimately end up in the generated `/matrix/element/config.json` file (on the server). This file is generated from the [`roles/custom/matrix-client-element/templates/config.json.j2`](../roles/custom/matrix-client-element/templates/config.json.j2) template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:24
+msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:26
+msgid "Alternatively, **if there is no pre-defined variable** for an Element Web setting you wish to change:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:28
+msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Element Web's various settings that rarely get used."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:30
+msgid "or, you can **extend and override the default configuration** ([`config.json.j2`](../roles/custom/matrix-client-element/templates/config.json.j2)) by making use of the `matrix_client_element_configuration_extension_json_` variable. You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:32
+msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_element_configuration_default` (or `matrix_client_element_configuration`). You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:34
+msgid "Themes"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:36
+msgid "To change the look of Element Web, you can define your own themes manually by using the `matrix_client_element_setting_defaults_custom_themes` setting."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:38
+msgid "Or better yet, you can automatically pull it all themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project by simply flipping a flag (`matrix_client_element_themes_enabled: true`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:40
+msgid "If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:42
+msgid "Note that for a custom theme to work well, all Element Web instances that you use must have the same theme installed."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:44
+msgid "Adjusting the Element Web URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:46
+msgid "By default, this playbook installs Element Web on the `element.` subdomain (`element.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:48
+msgid "By tweaking the `matrix_client_element_hostname` and `matrix_client_element_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-client-element-web.md:50
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:61
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:63
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Element Web domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:65
+msgid "By default, you will need to create a CNAME record for `element`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:67
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:69
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:71
+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-client-element-web.md:78
+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-element-web.md:80
+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 ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po
new file mode 100644
index 000000000..bcdae88b9
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-hydrogen.po
@@ -0,0 +1,89 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:1
+msgid "Setting up Hydrogen (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:3
+msgid "This playbook can install the [Hydrogen](https://github.com/element-hq/hydrogen-web) Matrix web client for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:5
+msgid "Hydrogen is a lightweight web client that supports mobile and legacy web browsers. It can be installed alongside or instead of Element Web."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:9
+msgid "To enable Hydrogen, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:15
+msgid "Adjusting the Hydrogen URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:17
+msgid "By default, this playbook installs Hydrogen on the `hydrogen.` subdomain (`hydrogen.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:19
+msgid "By tweaking the `matrix_client_hydrogen_hostname` and `matrix_client_hydrogen_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-client-hydrogen.md:21
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:32
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:34
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Hydrogen domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:36
+msgid "By default, you will need to create a CNAME record for `hydrogen`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:38
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:40
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:42
+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-client-hydrogen.md:49
+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-hydrogen.md:51
+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 ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po
new file mode 100644
index 000000000..248053755
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-client-schildichat-web.po
@@ -0,0 +1,145 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:1
+msgid "Setting up SchildiChat Web (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:3
+msgid "This playbook can install the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) Matrix client for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:5
+msgid "SchildiChat Web is a feature-rich messenger for Matrix based on Element Web with some extras and tweaks. It can be installed alongside or instead of Element Web."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:7
+msgid "💡 **Note**: the latest version of SchildiChat Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Application, you can consider using it from there:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:9
+msgid "[app.schildi.chat](https://app.schildi.chat/), hosted by the [SchildiChat](https://schildi.chat/) developers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:13
+msgid "To enable SchildiChat Web, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:19
+msgid "The playbook provides some customization variables you could use to change SchildiChat Web's settings."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:21
+msgid "Their defaults are defined in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml) and they ultimately end up in the generated `/matrix/schildichat/config.json` file (on the server). This file is generated from the [`roles/custom/matrix-client-schildichat/templates/config.json.j2`](../roles/custom/matrix-client-schildichat/templates/config.json.j2) template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:23
+msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:25
+msgid "Alternatively, **if there is no pre-defined variable** for a SchildiChat Web setting you wish to change:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:27
+msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of SchildiChat Web's various settings that rarely get used."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:29
+msgid "or, you can **extend and override the default configuration** ([`config.json.j2`](../roles/custom/matrix-client-schildichat/templates/config.json.j2)) by making use of the `matrix_client_schildichat_configuration_extension_json_` variable. You can find information about this in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:31
+msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_schildichat_configuration_default` (or `matrix_client_schildichat_configuration`). You can find information about this in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:33
+msgid "Themes"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:35
+msgid "To change the look of SchildiChat Web, you can define your own themes manually by using the `matrix_client_schildichat_setting_defaults_custom_themes` setting."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:37
+msgid "Or better yet, you can automatically pull it all themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project by simply flipping a flag (`matrix_client_schildichat_themes_enabled: true`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:39
+msgid "If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:41
+msgid "Note that for a custom theme to work well, all SchildiChat Web instances that you use must have the same theme installed."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:43
+msgid "Adjusting the SchildiChat Web URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:45
+msgid "By default, this playbook installs SchildiChat Web on the `schildichat.` subdomain (`schildichat.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:47
+msgid "By tweaking the `matrix_client_schildichat_hostname` and `matrix_client_schildichat_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-client-schildichat-web.md:49
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:60
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:62
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the SchildiChat Web domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:64
+msgid "By default, you will need to create a CNAME record for `schildichat`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:66
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:68
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:70
+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-client-schildichat-web.md:77
+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-schildichat-web.md:79
+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 ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduit.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduit.po
new file mode 100644
index 000000000..d2b467cfa
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-conduit.po
@@ -0,0 +1,97 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-conduit.md:1
+msgid "Configuring Conduit (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:3
+msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Conduit](https://conduit.rs)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:5
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:7
+msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:9
+msgid "**homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:13
+msgid "To use Conduit, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:19
+msgid "Creating the first user account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:21
+msgid "Since it is difficult to create the first user account on Conduit (see [famedly/conduit#276](https://gitlab.com/famedly/conduit/-/issues/276) and [famedly/conduit#354](https://gitlab.com/famedly/conduit/-/merge_requests/354)) and it does not support [registering users](registering-users.md) (via the command line or via the playbook) like Synapse and Dendrite do, we recommend the following procedure:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:23
+msgid "Add `matrix_conduit_allow_registration: true` to your `vars.yml` the first time around, temporarily"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:24
+msgid "Run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start` - see [Installing](installing.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:25
+msgid "Create your first user via Element Web or any other client which supports creating users"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:26
+msgid "Get rid of `matrix_conduit_allow_registration: true` from your `vars.yml`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:27
+msgid "Run the playbook again (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-conduit,start` would be enough this time)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:28
+msgid "You can now use your server safely. Additional users can be created by messaging the internal Conduit bot"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:30
+msgid "Configuring bridges / appservices"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:32
+msgid "Automatic appservice setup is currently unsupported when using Conduit. After setting up the service as usual you may notice that it is unable to start."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:34
+msgid "You will have to manually register appservices using the the [register-appservice](https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.md) command."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:36
+msgid "Find the `registration.yaml` in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`, then pass the content to Conduit:"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dendrite.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dendrite.po
new file mode 100644
index 000000000..ad5a7c023
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dendrite.po
@@ -0,0 +1,93 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-dendrite.md:1
+msgid "Configuring Dendrite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:3
+msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Dendrite](https://github.com/matrix-org/dendrite)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:5
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:7
+msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Dendrite). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:9
+msgid "**homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:13
+msgid "To use Dendrite, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:19
+msgid "The playbook provides lots of customization variables you could use to change Dendrite's settings."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:21
+msgid "Their defaults are defined in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml) and they ultimately end up in the generated `/matrix/dendrite/config/dendrite.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2) template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:23
+msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:25
+msgid "Alternatively, **if there is no pre-defined variable** for a Dendrite setting you wish to change:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:27
+msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Dendrite's various settings that rarely get used."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:29
+msgid "or, you can **extend and override the default configuration** ([`dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2)) by making use of the `matrix_dendrite_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:31
+msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_dendrite_configuration` (or `matrix_dendrite_configuration_yaml`). You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:33
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:35
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:42
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:44
+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 ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dimension.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dimension.po
new file mode 100644
index 000000000..70fd29702
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dimension.po
@@ -0,0 +1,182 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-dimension.md:1
+msgid "Setting up Dimension integration manager (optional, unmaintained)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:3
+#: ../../../docs/configuring-playbook-dimension.md:91
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:4
+msgid "Dimension is **[officially unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299)**. We recommend not bothering with installing it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:5
+msgid "This playbook now supports running Dimension in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`. Enabling Dimension, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:7
+msgid "The playbook can install and configure the [Dimension](https://dimension.t2bot.io) integration manager for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:9
+msgid "See the project's [documentation](https://github.com/turt2live/matrix-dimension/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:13
+msgid "Install Matrix services"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:15
+msgid "Dimension can only be installed after Matrix services are installed and running. If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) and come back here later."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:17
+msgid "Register a dedicated Matrix user (optional, recommended)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:19
+msgid "We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:21
+msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:23
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:29
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:31
+msgid "Dimension requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:33
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:35
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:37
+msgid "To enable Dimension, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`). Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:45
+msgid "Define admin users"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:47
+msgid "These users can modify the integrations this Dimension supports. Add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:55
+msgid "The admin interface is accessible within Element Web by accessing it in any room and clicking the cog wheel/settings icon in the top right. Currently, Dimension can be opened in Element Web by the \"Add widgets, bridges, & bots\" link in the room information."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:57
+msgid "Adjusting the Dimension URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:59
+msgid "By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:61
+msgid "By tweaking the `matrix_dimension_hostname` and `matrix_dimension_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-dimension.md:63
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:74
+msgid "**Note**: While there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You must serve Dimension at a dedicated subdomain."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:76
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:78
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:80
+msgid "By default, you will need to create a CNAME record for `dimension`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:82
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:84
+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-dimension.md:93
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:95
+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-dimension.md:97
+msgid "After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:99
+msgid "Jitsi domain"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:101
+msgid "By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](./configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance. Currently there is no way to configure this via the playbook, see [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:103
+msgid "In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element Web, go to *Manage Integrations* &rightarrow; *Settings* &rightarrow; *Widgets* &rightarrow; *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:105
+msgid "Additional features"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:107
+msgid "To use a more custom configuration, you can define a `matrix_dimension_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_dimension_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-dimension/defaults/main.yml) of the Dimension component."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:109
+msgid "You can find all configuration options on [GitHub page of Dimension project](https://github.com/turt2live/matrix-dimension/blob/master/config/default.yaml)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po
new file mode 100644
index 000000000..40444b011
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-dynamic-dns.po
@@ -0,0 +1,77 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:1
+msgid "Setting up Dynamic DNS (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:3
+msgid "The playbook can configure Dynamic DNS with [ddclient⁠](https://github.com/ddclient/ddclient) for you. It is a Perl client used to update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:5
+msgid "Most cloud providers / ISPs will charge you extra for a static IP address. If you're not hosting a highly reliable homeserver you can workaround this via dynamic DNS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:7
+msgid "Prerequisite"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:9
+msgid "You'll need to get a username and password from your DNS provider. Please consult with the provider about how to retrieve them."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:13
+msgid "To enable dynamic DNS, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:26
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:28
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:35
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:37
+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-dynamic-dns.md:39
+msgid "Additional Reading"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:41
+msgid "Additional resources:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:43
+msgid "https://matrix.org/docs/guides/free-small-matrix-server"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email.po
new file mode 100644
index 000000000..cbccf36f9
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email.po
@@ -0,0 +1,89 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-email.md:1
+msgid "Adjusting email-sending settings (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:3
+msgid "By default, this playbook sets up an [Exim](https://www.exim.org/) email server through which all Matrix services send emails."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:5
+msgid "The email server would attempt to deliver emails directly to their final destination. This may or may not work, depending on your domain configuration (SPF settings, etc.)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:7
+msgid "By default, emails are sent from `matrix@matrix.example.com`, as specified by the `exim_relay_sender_address` playbook variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:9
+msgid "⚠️ **Warning**: On some cloud providers (Google Cloud, etc.), [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible. You will need to [relay email through another SMTP server](#relaying-email-through-another-smtp-server)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:11
+msgid "💡 To improve deliverability, we recommend [relaying email through another SMTP server](#relaying-email-through-another-smtp-server) anyway."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:13
+msgid "Firewall settings"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:15
+msgid "No matter whether you send email directly (the default) or you relay email through another host (see how below), you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:17
+msgid "Relaying email through another SMTP server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:19
+msgid "If you'd like to relay email through another SMTP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:31
+msgid "**Note**: only the secure submission protocol (using `STARTTLS`, usually on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port `465`) **is not supported**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:33
+msgid "Configuations for sending emails using Sendgrid"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:35
+msgid "An easy and free SMTP service to set up is [Sendgrid](https://sendgrid.com/), the free tier allows for up to 100 emails per day to be sent. In the settings below you can provide any email for `exim_relay_sender_address`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:37
+msgid "The only other thing you need to change is the `exim_relay_relay_auth_password`, which you can generate at https://app.sendgrid.com/settings/api_keys. The API key password looks something like `SG.955oW1mLSfwds7i9Yd6IA5Q.q8GTaB8q9kGDzasegdG6u95fQ-6zkdwrPP8bOeuI`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:39
+msgid "Note that the `exim_relay_relay_auth_username` is literally the string `apikey`, it's always the same for Sendgrid."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:51
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:53
+msgid "If you're having trouble with email not being delivered, it may be useful to inspect the mailer logs: `journalctl -f -u matrix-exim-relay`."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po
new file mode 100644
index 000000000..8fcce52cb
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-email2matrix.po
@@ -0,0 +1,197 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-email2matrix.md:1
+msgid "Setting up Email2Matrix (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:3
+msgid "**Note**: email bridging can also happen via the [Postmoogle](configuring-playbook-bridge-postmoogle.md) bridge supported by the playbook. Postmoogle is much more powerful and easier to use, so we recommend that you use it, instead of Email2Matrix."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:5
+msgid "The playbook can install and configure [email2matrix](https://github.com/devture/email2matrix) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:7
+msgid "See the project's [documentation](https://github.com/devture/email2matrix/blob/master/docs/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:9
+msgid "Preparation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:11
+msgid "DNS configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:13
+msgid "It's not strictly necessary, but you may increase the chances that incoming emails reach your server by adding an `MX` record for `matrix.example.com`, as described in the [Configuring DNS](configuring-dns.md) documentation page."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:15
+msgid "Port availability"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:17
+msgid "Ensure that port 25 is available on your Matrix server and open in your firewall."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:19
+msgid "If you have `postfix` or some other email server software installed, you may need to manually remove it first (unless you need it, of course)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:21
+msgid "If you really need to run an email server on the Matrix machine for other purposes, it may be possible to run Email2Matrix on another port (with a configuration like `matrix_email2matrix_smtp_host_bind_port: \"127.0.0.01:2525\"`) and have your other email server relay messages there."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:23
+msgid "For details about using Email2Matrix alongside [Postfix](http://www.postfix.org/), see [here](https://github.com/devture/email2matrix/blob/master/docs/setup_with_postfix.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:25
+msgid "Register a dedicated Matrix user (optional, recommended)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:27
+msgid "We recommend that you create a dedicated Matrix user for Email2Matrix."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:29
+msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:31
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:37
+msgid "Take note of the user's ID as it needs to be specified as `MatrixUserId` on your `inventory/host_vars/matrix.example.com/vars.yml` file later."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:39
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:41
+msgid "Email2Matrix requires an access token for the sender user to be able to send messages to the room. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:43
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:45
+msgid "Join to rooms as the sender user manually"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:47
+msgid "ℹ️ **Email2Matrix does not accept room invitations automatically**. To deliver messages to rooms, the sender user must be joined to all rooms manually."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:49
+msgid "For each new room you would like the user to deliver messages to, invite the user to the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:51
+msgid "Then, log in as the sender user using any Matrix client of your choosing, accept the room invitation from the user's account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:53
+msgid "Make sure that you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there, then log out."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:55
+msgid "Take note of each room's room ID (different clients show the room ID in a different place). You'll need the room ID when [configuring the playbook](#adjusting-the-playbook-configuration) below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:57
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:59
+msgid "To enable Email2Matrix, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE` and `ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE` with the ones created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:85
+msgid "where:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:87
+msgid "MailboxName - local-part of the email address, through which emails are bridged to the room whose ID is defined with MatrixRoomId"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:88
+msgid "MatrixRoomId - internal ID of the room, to which received emails are sent as Matrix message"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:89
+msgid "MatrixHomeserverUrl - URL of your Matrix homeserver, through which to send Matrix messages. You can also set `MatrixHomeserverUrl` to the container URL where your homeserver's Client-Server API lives by using the `{{ matrix_addons_homeserver_client_api_url }}` variable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:90
+msgid "MatrixUserId - the full ID of the sender user which sends bridged messages to the room. On this configuration it is `@email2matrix1:example.com` and `@email2matrix2:example.com` (where `example.com` is your base domain, not the `matrix.` domain)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:91
+msgid "MatrixAccessToken - sender user's access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:92
+msgid "IgnoreSubject - if set to \"true\", the subject is not bridged to Matrix"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:93
+msgid "IgnoreBody - if set to \"true\", the message body is not bridged to Matrix"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:94
+msgid "SkipMarkdown - if set to \"true\", emails are bridged as plain text Matrix message instead of Markdown (actually HTML)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:96
+msgid "Refer to the official documentation [here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:98
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:100
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:107
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:109
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service email2matrix` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:111
+msgid "`just install-service email2matrix` is useful for maintaining your setup quickly 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 `just setup-all` runs the `ensure-matrix-users-created` tag too."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:113
+msgid "After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-etherpad.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-etherpad.po
new file mode 100644
index 000000000..4afdc7bb9
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-etherpad.po
@@ -0,0 +1,173 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-etherpad.md:1
+msgid "Setting up Etherpad (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:3
+msgid "[Etherpad](https://etherpad.org) is an open source collaborative text editor that can be embedded in a Matrix chat room using the [Dimension integration manager](https://dimension.t2bot.io) or used as standalone web app."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:5
+msgid "When enabled together with the Jitsi audio/video conferencing system (see [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made available as an option during the conferences."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:9
+msgid "To enable Etherpad, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:19
+msgid "Adjusting the Etherpad URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:21
+msgid "By default, this playbook installs Etherpad on the `etherpad.` subdomain (`etherpad.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:23
+msgid "By tweaking the `etherpad_hostname` and `etherpad_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-etherpad.md:25
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:36
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:38
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Etherpad domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:40
+msgid "By default, you will need to create a CNAME record for `etherpad`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:42
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:44
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:46
+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-etherpad.md:53
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:55
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the Etherpad admin user (`etherpad_admin_username`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:57
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:59
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:61
+msgid "If you change the Etherpad admin user's password (`etherpad_admin_password` in your `vars.yml` file) subsequently, the admin user's credentials on the homeserver won't be updated automatically. If you'd like to change the admin user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `etherpad_admin_password` to let the admin user know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:63
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:65
+msgid "The Etherpad UI should be available at `https://etherpad.example.com`, while the admin UI (if enabled) should then be available at `https://etherpad.example.com/admin`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:67
+msgid "If you've [decided on another hostname or path-prefix](#adjusting-the-etherpad-url) (e.g. `https://matrix.example.com/etherpad`), adjust these URLs accordingly before usage."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:69
+msgid "Managing / Deleting old pads"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:71
+msgid "If you want to manage and remove old unused pads from Etherpad, you will first need to able Admin access as described above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:73
+msgid "Then from the plugin manager page (`https://etherpad.example.com/admin/plugins`, install the `adminpads2` plugin. Once installed, you should have a \"Manage pads\" section in the Admin web-UI."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:75
+msgid "How to use Etherpad widgets without an integration manager (like Dimension)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:77
+msgid "This is how it works in Element Web, it might work quite similar with other clients:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:79
+msgid "To integrate a standalone Etherpad in a room, create your pad by visiting `https://etherpad.example.com`. When the pad opens, copy the URL and send a command like this to the room: `/addwidget URL`. You will then find your integrated Etherpad within the right sidebar in the `Widgets` section."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:81
+msgid "Set Dimension default to the self-hosted Etherpad (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:83
+msgid "If you decided to install [Dimension integration manager](configuring-playbook-dimension.md) alongside Etherpad, the Dimension administrator users can configure the default URL template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:85
+msgid "The Dimension configuration menu can be accessed with the sprocket icon as you begin to add a widget to a room in Element Web. There you will find the Etherpad Widget Configuration action beneath the _Widgets_ tab."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:87
+msgid "Removing the integrated Etherpad chat"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:89
+msgid "If you wish to disable the Etherpad chat button, you can do it by appending `?showChat=false` to the end of the pad URL, or the template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:91
+msgid "Example: `https://etherpad.example.com/p/$roomId_$padName?showChat=false`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:93
+msgid "Known issues"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:95
+msgid "If your Etherpad widget fails to load, this might be due to Dimension generating a Pad name so long, the Etherpad app rejects it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:97
+msgid "`$roomId_$padName` can end up being longer than 50 characters. You can avoid having this problem by altering the template so it only contains the three word random identifier `$padName`."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-external-postgres.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-external-postgres.po
new file mode 100644
index 000000000..e9472e140
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-external-postgres.po
@@ -0,0 +1,49 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-external-postgres.md:1
+msgid "Using an external PostgreSQL server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:3
+msgid "By default, this playbook would set up a PostgreSQL database server on your machine, running in a Docker container. If that's okay, you can skip this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:5
+msgid "**Note**: using **an external Postgres server is currently [not very seamless](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1682#issuecomment-1061461683) when it comes to enabling various other playbook services** - you will need to create a new database/credentials for each service and to point each service to its corresponding database using custom `vars.yml` configuration. **For the best experience with the playbook, stick to using the integrated Postgres server**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:7
+msgid "If you'd like to use an external Postgres server that you manage, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:23
+msgid "The database (as specified in `matrix_synapse_database_database`) must exist and be accessible with the given credentials. It must be empty or contain a valid Synapse database. If empty, Synapse would populate it the first time it runs."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:25
+msgid "**Note**: the external server that you specify in `matrix_synapse_database_host` must be accessible from within the `matrix-synapse` Docker container (and possibly other containers too). This means that it either needs to be a publicly accessible hostname or that it's a hostname on the same Docker network where all containers installed by this playbook run (a network called `matrix` by default). Using a local PostgreSQL instance on the host (running on the same machine, but not in a container) is not possible."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:27
+msgid "The connection to your external Postgres server **will not be SSL encrypted**, as [we don't support that yet](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/89)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-federation.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-federation.po
new file mode 100644
index 000000000..2df5135eb
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-federation.po
@@ -0,0 +1,89 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-federation.md:1
+msgid "Controlling Matrix federation (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:3
+msgid "By default, your server federates with the whole Matrix network. That is, people on your server can communicate with people on any other Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:5
+msgid "**Note**: in the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com` and set up [server delegation](howto-server-delegation.md) / redirection. Without a proper configuration, your server will effectively not be part of the Matrix network. If you find your server is not federated, make sure to [check whether services work](maintenance-checking-services.md) and your server is properly delegated."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:7
+msgid "Federating only with select servers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:9
+msgid "To make your server only federate with servers of your choosing, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:17
+msgid "If you wish to disable federation, you can do that with an empty list (`[]`), or better yet by completely disabling federation (see below)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:19
+msgid "Exposing the room directory over federation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:21
+msgid "By default, your server's public rooms directory is not exposed to other servers via federation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:23
+msgid "If you wish to expose it, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:29
+msgid "Disabling federation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:31
+msgid "To completely disable federation, isolating your server from the rest of the Matrix network, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:37
+msgid "With that, your server's users will only be able to talk among themselves, but not to anyone who is on another server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:39
+msgid "**Disabling federation does not necessarily disable the federation port** (`8448`). Services like [Dimension](configuring-playbook-dimension.md) and [ma1sd](configuring-playbook-ma1sd.md) normally rely on `openid` APIs exposed on that port. Even if you disable federation and only if necessary, we may still be exposing the federation port and serving the `openid` APIs there. To override this and completely disable Synapse's federation port use:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:51
+msgid "Changing the federation port from 8448 to a different port to use a CDN that only accepts 443/80 ports"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:53
+msgid "Why? This change could be useful for people running small Synapse instances on small severs/VPSes to avoid being impacted by a simple DOS/DDOS when bandwidth, RAM, an CPU resources are limited and if your hosting provider does not provide a DOS/DDOS protection."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:55
+msgid "The following changes in the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) will allow this and make it possible to proxy the federation through a CDN such as CloudFlare or any other:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:66
+msgid "**Use this at you own risk as all the possible side-effects of doing this are not fully known. However, it has been tested and works fine and passes all the tests on <https://federationtester.matrix.org/> without issues.**"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jitsi.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jitsi.po
new file mode 100644
index 000000000..00813eb43
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-jitsi.po
@@ -0,0 +1,365 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-jitsi.md:1
+msgid "Setting up the Jitsi video-conferencing platform (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:3
+msgid "The playbook can install the [Jitsi](https://jitsi.org/) video-conferencing platform and integrate it with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:5
+msgid "Jitsi installation is **not enabled by default**, because it's not a core component of Matrix services."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:7
+msgid "The setup done by the playbook is very similar to [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the documentation there for many of the options here."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:11
+msgid "You may need to open the following ports to your server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:13
+msgid "`4443/tcp` - RTP media fallback over TCP"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:14
+msgid "`10000/udp` - RTP media over UDP. Depending on your firewall/NAT setup, incoming RTP packets on port `10000` may have the external IP of your firewall as destination address, due to the usage of STUN in JVB (see [`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/defaults/main.yml))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:16
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:18
+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:24
+msgid "Adjusting the Jitsi URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:26
+msgid "By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:28
+msgid "By tweaking the `jitsi_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:30
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:37
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:39
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Jitsi domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:41
+msgid "By default, you will need to create a CNAME record for `jitsi`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:43
+msgid "Configure Jitsi authentication and guests mode (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:45
+msgid "By default the Jitsi Meet instance does not require any kind of login and is open to use for anyone without registration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:47
+msgid "If you're fine with such an open Jitsi instance, please skip to [Installing](#installing)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:49
+msgid "If you would like to control who is allowed to open meetings on your new Jitsi instance, then please follow the following steps to enable Jitsi's authentication and optionally guests mode."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:51
+msgid "Currently, there are three supported authentication modes: 'internal' (default), 'matrix' and 'ldap'."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:53
+msgid "**Note**: Authentication is not tested via the playbook's self-checks. We therefore recommend that you manually verify if authentication is required by jitsi. For this, try to manually create a conference on jitsi.example.com in your browser."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:55
+msgid "Authenticate using Jitsi accounts (Auth-Type 'internal')"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:57
+msgid "The default authentication mechanism is 'internal' auth, which requires jitsi-accounts to be setup and is the recommended setup, as it also works in federated rooms. With authentication enabled, all meeting rooms have to be opened by a registered user, after which guests are free to join. If a registered host is not yet present, guests are put on hold in individual waiting rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:59
+msgid "Add these lines to your `inventory/host_vars/matrix.example.com/vars.yml` configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:71
+msgid "**Caution**: Accounts added here and subsequently removed will not be automatically removed from the Prosody server until user account cleaning is integrated into the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:73
+msgid "**If you get an error** like this: \"Error: Account creation/modification not supported.\", it's likely that you had previously installed Jitsi without auth/guest support. In such a case, you should look into [Rebuilding your Jitsi installation](#rebuilding-your-jitsi-installation)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:75
+msgid "Authenticate using Matrix OpenID (Auth-Type 'matrix')"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:77
+msgid "**Attention: Probably breaks Jitsi in federated rooms and does not allow sharing conference links with guests.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:79
+msgid "Using this authentication type require a [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service). By default, this playbook creates and configures a user-verification-service to run locally, see [configuring-user-verification-service](configuring-playbook-user-verification-service.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:81
+msgid "To enable set this configuration at host level:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:89
+msgid "For more information see also [https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification](https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:91
+msgid "Authenticate using LDAP (Auth-Type 'ldap')"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:93
+msgid "An example LDAP configuration could be:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:113
+msgid "For more information refer to the [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:115
+msgid "Making your Jitsi server work on a LAN (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:117
+msgid "By default the Jitsi Meet instance does not work with a client in LAN (Local Area Network), even if others are connected from WAN. There are no video and audio. In the case of WAN to WAN everything is ok."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:119
+msgid "The reason is the Jitsi VideoBridge git to LAN client the IP address of the docker image instead of the host. The [documentation](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/#running-behind-nat-or-on-a-lan-environment) of Jitsi in docker suggest to add `JVB_ADVERTISE_IPS` in enviornment variable to make it work."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:121
+msgid "Here is how to do it in the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:123
+msgid "Add these two lines to your `inventory/host_vars/matrix.example.com/vars.yml` configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:130
+msgid "Fine tune Jitsi (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:132
+msgid "Sample **additional** `inventory/host_vars/matrix.example.com/vars.yml` configuration to save up resources (explained below):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:147
+msgid "You may want to **suspend unused video layers** until they are requested again, to save up resources on both server and clients. Read more on this feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-feature/)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:149
+msgid "You may wish to **disable audio levels** to avoid excessive refresh of the client-side page and decrease the CPU consumption involved."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:151
+msgid "You may want to **limit the number of video feeds forwarded to each client**, to save up resources on both server and clients. As clients’ bandwidth and CPU may not bear the load, use this setting to avoid lag and crashes. This feature is found by default in other webconference applications such as Office 365 Teams (limit is set to 4). Read how it works [here](https://github.com/jitsi/jitsi-videobridge/blob/master/doc/last-n.md) and performance evaluation on this [study](https://jitsi.org/wp-content/uploads/2016/12/nossdav2015lastn.pdf)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:153
+msgid "You may want to **limit the maximum video resolution**, to save up resources on both server and clients."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:155
+msgid "Specify a Max number of participants on a Jitsi conference (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:157
+msgid "The playbook allows a user to set a max number of participants allowed to join a Jitsi conference. By default there is no limit."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:159
+msgid "In order to set the max number of participants use the following **additional** configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:165
+msgid "Additional JVBs (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:167
+msgid "By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)) is deployed on the same host as the Matrix server. To allow more video-conferences to happen at the same time, you may need to provision additional JVB services on other hosts."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:169
+msgid "There is an ansible playbook that can be run with the following tag: `ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:171
+msgid "For this role to work you will need an additional section in the ansible hosts file with the details of the JVB hosts, for example:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:178
+msgid "Each JVB will require a server ID to be set so that it can be uniquely identified and this allows Jitsi to keep track of which conferences are on which JVB. The server ID is set with the variable `jitsi_jvb_server_id` which ends up as the JVB_WS_SERVER_ID environment variables in the JVB docker container. This variable can be set via the host file, a parameter to the ansible command or in the `vars.yaml` for the host which will have the additional JVB. For example:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:190
+msgid "Note that the server ID `jvb-1` is reserved for the JVB instance running on the Matrix host and therefore should not be used as the ID of an additional jvb host."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:192
+msgid "The additional JVB will also need to expose the colibri web socket port and this can be done with the following variable:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:198
+msgid "The JVB will also need to know where the prosody xmpp server is located, similar to the server ID this can be set in the vars for the JVB by using the variable `jitsi_xmpp_server`. The Jitsi prosody container is deployed on the Matrix server by default so the value can be set to the Matrix domain. For example:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:204
+msgid "However, it can also be set the ip address of the Matrix server. This can be useful if you wish to use a private ip. For example:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:210
+msgid "For the JVB to be able to contact the XMPP server, the latter must expose the XMPP port (5222). By default, the Matrix server does not expose the port; only the XMPP container exposes it internally inside the host, which means that the first JVB (which runs on the Matrix server) can reach it but the additional JVB cannot. The port is exposed by setting `jitsi_prosody_container_jvb_host_bind_port` like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:216
+msgid "(The default is empty; if it's set then docker forwards the port.)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:218
+msgid "Applied together this will allow you to provision extra JVB instances which will register themselves with the prosody service and be available for jicofo to route conferences too."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:220
+msgid "To make Traefik reverse-proxy to these additional JVBs (living on other hosts), **you would need to add the following Traefik configuration extension**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:256
+msgid "Enable Gravatar (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:258
+msgid "In the default Jisti Meet configuration, gravatar.com is enabled as an avatar service. This results in third party request leaking data to gravatar. Since Element clients already send the url of configured Matrix avatars to Jitsi, we disabled gravatar."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:260
+msgid "To enable Gravatar set:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:266
+msgid "**Beware**: This leaks information to a third party, namely the Gravatar-Service (unless configured otherwise: gravatar.com). Besides metadata, this includes the Matrix user_id and possibly the room identifier (via `referrer` header)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:268
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:270
+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:277
+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:279
+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:281
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:283
+msgid "You can use the self-hosted Jitsi server in multiple ways:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:285
+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:287
+msgid "**by adding a widget to a room via the Dimension integration manager**. You'll have to point the widget to your own Jitsi server manually. See our [Dimension integration manager](./configuring-playbook-dimension.md) documentation page for more details. Naturally, Dimension would need to be installed first (the playbook doesn't install it by default)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:289
+msgid "**directly (without any Matrix integration)**. Just go to `https://jitsi.example.com`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:291
+msgid "**Note**: Element apps on mobile devices currently [don't support joining meetings on a self-hosted Jitsi server](https://github.com/element-hq/riot-web/blob/601816862f7d84ac47547891bd53effa73d32957/docs/jitsi.md#mobile-app-support)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:293
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:295
+msgid "Rebuilding your Jitsi installation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:297
+msgid "**If you ever run into any trouble** or **if you change configuration (`jitsi_*` variables) too much**, we urge you to rebuild your Jitsi setup."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:299
+msgid "We normally don't require such manual intervention for other services, but Jitsi services generate a lot of configuration files on their own."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:301
+msgid "These files are not all managed by Ansible (at least not yet), so you may sometimes need to delete them all and start fresh."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:303
+msgid "To rebuild your Jitsi configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:305
+msgid "ask Ansible to stop all Jitsi services: `just run-tags stop-group --extra-vars=group=jitsi`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:306
+msgid "SSH into the server and do this and remove all Jitsi configuration & data (`rm -rf /matrix/jitsi`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:307
+msgid "ask Ansible to set up Jitsi anew and restart services (`just install-service jitsi`)"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po
new file mode 100644
index 000000000..02a6f75ea
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ldap-auth.po
@@ -0,0 +1,61 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:1
+msgid "Setting up the LDAP authentication password provider module (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:3
+msgid "The playbook can install and configure the [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) LDAP Auth password provider for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:5
+msgid "See the project's [documentation](https://github.com/matrix-org/matrix-synapse-ldap3/blob/main/README.rst) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:7
+msgid "If you decide that you'd like to let this playbook install it for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:24
+msgid "Authenticating only using a password provider"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:26
+msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:32
+msgid "Using ma1sd Identity Server for authentication"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:34
+msgid "If you wish to use the ma1sd Identity Server for LDAP authentication instead of [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) consult [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md#authentication)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:36
+msgid "Handling user registration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:38
+msgid "If you wish for users to also be able to make new registrations against LDAP, you may **also** wish to [set up the ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ma1sd.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ma1sd.po
new file mode 100644
index 000000000..916e35d94
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ma1sd.po
@@ -0,0 +1,213 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-ma1sd.md:1
+msgid "Setting up ma1sd Identity Server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:3
+msgid "**⚠️Note**: ma1sd itself has also been unmaintained for years (the latest commit and release being from 2021). The role of identity servers in the Matrix specification also has an uncertain future. **We recommend not bothering with installing it unless it's the only way you can do what you need to do**. For example, certain things like LDAP integration can also be implemented via [the LDAP provider module for Synapse](./configuring-playbook-ldap-auth.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:5
+msgid "The playbook can configure the [ma1sd](https://github.com/ma1uta/ma1sd) Identity Server for you. It is a fork of [mxisd](https://github.com/kamax-io/mxisd) which was pronounced end of life 2019-06-21."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:7
+msgid "ma1sd is used for 3PIDs (3rd party identifiers like E-mail and phone numbers) and some [enhanced features](https://github.com/ma1uta/ma1sd/#features). It is private by default, potentially at the expense of user discoverability."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:9
+msgid "See the project's [documentation](https://github.com/ma1uta/ma1sd/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:11
+msgid "**Note**: enabling ma1sd, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:13
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:15
+msgid "To make the ma1sd Identity Server enable its federation features, set up a SRV record that looks like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:17
+msgid "Name: `_matrix-identity._tcp` (use this text as-is)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:18
+msgid "Content: `10 0 443 matrix.example.com` (replace `example.com` with your own)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:20
+msgid "See [ma1sd's documentation](https://github.com/ma1uta/ma1sd/wiki/mxisd-and-your-privacy#choices-are-never-easy) for information on the privacy implications of setting up this SRV record."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:22
+msgid "**Note**: This `_matrix-identity._tcp` SRV record for the identity server is different from the `_matrix._tcp` that can be used for Synapse delegation. See [howto-server-delegation.md](howto-server-delegation.md) for more information about delegation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:24
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:26
+msgid "To enable ma1sd, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:32
+msgid "Matrix.org lookup forwarding"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:34
+msgid "To ensure maximum discovery, you can make your identity server also forward lookups to the central matrix.org Identity server (at the cost of potentially leaking all your contacts information)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:36
+msgid "Enabling this is discouraged and you'd better [learn more](https://github.com/ma1uta/ma1sd/blob/master/docs/features/identity.md#lookups) before proceeding."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:38
+msgid "To enable matrix.org forwarding, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:44
+msgid "Additional features"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:46
+msgid "What this playbook configures for your is some bare minimum Identity Server functionality, so that you won't need to rely on external 3rd party services."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:48
+msgid "A few variables can be toggled in this playbook to alter the ma1sd configuration that gets generated."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:50
+msgid "Still, ma1sd can do much more. You can refer to the [ma1sd website](https://github.com/ma1uta/ma1sd) for more details and configuration options."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:52
+msgid "To use a more custom configuration, you can define a `matrix_ma1sd_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_ma1sd_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-ma1sd/defaults/main.yml) of the ma1sd component."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:54
+msgid "Customizing email templates"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:56
+msgid "If you'd like to change the default email templates used by ma1sd, take a look at the `matrix_ma1sd_threepid_medium_email_custom_` variables (in the `roles/custom/matrix-ma1sd/defaults/main.yml` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:58
+msgid "ma1sd-controlled Registration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:60
+msgid "To use the [Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) feature of ma1sd, you can make use of the following variables:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:62
+msgid "`matrix_synapse_enable_registration` - to enable user-initiated registration in Synapse"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:64
+msgid "`matrix_synapse_enable_registration_captcha` - to validate registering users using reCAPTCHA, as described in the [enabling reCAPTCHA](configuring-captcha.md) documentation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:66
+msgid "`matrix_synapse_registrations_require_3pid` - a list of 3pid types (among `'email'`, `'msisdn'`) required by the Synapse server for registering"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:68
+msgid "variables prefixed with `matrix_ma1sd_container_labels_` (e.g. `matrix_ma1sd_container_labels_matrix_client_3pid_registration_enabled`) - to configure the Traefik reverse-proxy to capture and send registration requests to ma1sd (instead of Synapse), so it can apply its additional functionality"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:70
+msgid "`matrix_ma1sd_configuration_extension_yaml` - to configure ma1sd as required. See the [Registration feature's docs](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) for inspiration. Also see the [Additional features](#additional-features) section below to learn more about how to use `matrix_ma1sd_configuration_extension_yaml`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:72
+msgid "**Note**: For this to work, either the homeserver needs to [federate](configuring-playbook-federation.md) or the `openid` APIs need to exposed on the federation port. When federation is disabled and ma1sd is enabled, we automatically expose the `openid` APIs (only!) on the federation port. Make sure the federation port (usually `https://matrix.example.com:8448`) is whitelisted in your firewall (even if you don't actually use/need federation)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:74
+msgid "Authentication"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:76
+msgid "[Authentication](https://github.com/ma1uta/ma1sd/blob/master/docs/features/authentication.md) provides the possibility to use your own [Identity Stores](https://github.com/ma1uta/ma1sd/blob/master/docs/stores/README.md) (for example LDAP) to authenticate users on your Homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:78
+msgid "To enable authentication against an LDAP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:98
+msgid "Example: SMS verification"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:100
+msgid "If your use case requires mobile verification, it is quite simple to integrate ma1sd with [Twilio](https://www.twilio.com/), an online telephony services gateway. Their prices are reasonable for low-volume projects and integration can be done with the following configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:114
+msgid "Example: Open Registration for every Domain"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:116
+msgid "If you want to open registration for any domain, you have to setup the allowed domains with ma1sd's `blacklist` and `whitelist`. The default behavior when neither the `blacklist`, nor the `whitelist` match, is to allow registration. Beware: you can't block toplevel domains (aka `.xy`) because the internal architecture of ma1sd doesn't allow that."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:130
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:132
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:139
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:141
+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-ma1sd.md:143
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:145
+msgid "If email address validation emails sent by ma1sd are not reaching you, you should look into [Adjusting email-sending settings](configuring-playbook-email.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:147
+msgid "If you'd like additional logging information, temporarily enable verbose logging for ma1sd."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:149
+msgid "To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po
new file mode 100644
index 000000000..7cc448789
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po
@@ -0,0 +1,622 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:1
+msgid "Setting up Matrix Authentication Service (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:3
+msgid "This playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) - a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:5
+msgid "Matrix Authentication Service is an implementation of [MSC3861: Next-generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:7
+msgid "**Before going through with starting to use Matrix Authentication Service**, make sure to read:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:9
+msgid "the [Reasons to use Matrix Authentication Service](#reasons-to-use-matrix-authentication-service) section below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:10
+msgid "the [Expectations](#expectations) section below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:11
+msgid "the [FAQ section on areweoidcyet.com](https://areweoidcyet.com/#faqs)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:13
+msgid "**If you've already been using Synapse** and have user accounts in its database, you can [migrate to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:15
+msgid "Reasons to use Matrix Authentication Service"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:17
+msgid "You may be wondering whether you should make the switch to Matrix Authentication Service (MAS) or keep using your existing authentication flow via Synapse (password-based or [OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)-enabled)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:19
+msgid "Matrix Authentication Service is **still an experimental service** and **not a default** for this Ansible playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:21
+msgid "The [Expectations](#expectations) section contains a list of what works and what doesn't (**some services don't work with MAS yet**), as well as the **relative irreversability** of the migration process."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:23
+msgid "Below, we'll try to **highlight some potential reasons for switching** to Matrix Authentication Service:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:25
+msgid "To use SSO in [Element X](https://element.io/blog/element-x-ignition/). The old [Synapse OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) login flow is only supported in old Element clients and will not be supported in Element X. Element X will only support the new SSO-based login flow provided by MAS, so if you want to use SSO with Element X, you will need to switch to MAS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:27
+msgid "To help drive adoption of the \"Next-generation auth for Matrix\" by switching to what's ultimately coming anyway"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:29
+msgid "To help discover (and potentially fix) MAS integration issues with this Ansible playbook"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:31
+msgid "To help discover (and potentially fix) MAS integration issues with various other Matrix components (bridges, bots, clients, etc.)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:33
+msgid "To reap some of the security benefits that Matrix Authentication Service offers, as outlined in the [Better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/) article."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:35
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:37
+msgid "⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:39
+msgid "⚠️ **email sending** configured (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:41
+msgid "❌ **disabling all password providers** for Synapse (things like [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc.) More details about this are available in the [Expectations](#expectations) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:43
+msgid "Expectations"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:45
+msgid "This section details what you can expect when switching to the Matrix Authentication Service (MAS)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:47
+msgid "❌ **Synapse password providers will need to be disabled**. You can no longer use [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc. When the authentication flow is handled by MAS (not by Synapse anymore), it doesn't make sense to extend the Synapse authentication flow with additional modules. Many bridges used to rely on shared-secret-auth for doing double-puppeting (impersonating other users), but most (at least the mautrix bridges) nowadays use [Appservice Double Puppet](./configuring-playbook-appservice-double-puppet.md) as a better alternative. Older/maintained bridges may still rely on shared-secret-auth, as do other services like [matrix-corporal](./configuring-playbook-matrix-corporal.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:49
+msgid "❌ Certain **tools like [synapse-admin](./configuring-playbook-synapse-admin.md) do not have full compatibility with MAS yet**. synapse-admin already supports [login with access token](https://github.com/etkecc/synapse-admin/pull/58), browsing users (which Synapse will internally fetch from MAS) and updating user avatars. However, editing users (passwords, etc.) now needs to happen directly against MAS using the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html), which synapse-admin cannot interact with yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:51
+msgid "❌ **Some services experience issues when authenticating via MAS**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:53
+msgid "[Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first time around, but it consistently fails after restarting:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:55
+msgid "cannot initialize matrix bot error=\"olm account is marked as shared, keys seem to have disappeared from the server\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:57
+msgid "[matrix-reminder-bot](./configuring-playbook-bot-matrix-reminder-bot.md) fails to start (see [element-hq/matrix-authentication-service#3439](https://github.com/element-hq/matrix-authentication-service/issues/3439))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:58
+msgid "Other services may be similarly affected. This list is not exhaustive."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:60
+msgid "❌ **Encrypted appservices** do not work yet (related to [MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) and [PR 17705 for Synapse](https://github.com/element-hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will fail to start (see [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3658) for Hookshot). You can use these bridges/bots only if you **keep end-to-bridge encryption disabled** (which is the default setting)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:62
+msgid "⚠️ **You will need to have email sending configured** (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:64
+msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:66
+msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) does not currently seem to preserve the \"admin\" flag for users (as found in the Synapse database). All users are imported as non-admin - see [element-hq/matrix-authentication-service#3440](https://github.com/element-hq/matrix-authentication-service/issues/3440). You may need update the Matrix Authentication Service's database manually and adjust the `can_request_admin` column in the `users` table to `true` for users that need to be administrators (e.g. `UPDATE users SET can_request_admin = true WHERE username = 'someone';`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:68
+msgid "⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependant on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:70
+msgid "⚠️ If you've got [OIDC configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to migrate your OIDC configuration to MAS by adding an [Upstream OAuth2 configuration](#upstream-oauth2-configuration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:72
+msgid "⚠️ A [compatibility layer](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) is installed - all `/_matrix/client/*/login` (etc.) requests will be routed to MAS instead of going to the homeserver. This is done both publicly (e.g. `https://matrix.example.com/_matrix/client/*/login`) and on the internal Traefik entrypoint (e.g. `https://matrix-traefik:8008/_matrix/client/*/login`) which helps addon services reach the homeserver's Client-Server API. You typically don't need to do anything to make this work, but it's good to be aware of it, especially if you have a [custom webserver setup](./configuring-playbook-own-webserver.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:74
+msgid "✅ Your **existing login sessions will continue to work** (you won't get logged out). Migration will require a bit of manual work and minutes of downtime, but it's not too bad."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:76
+msgid "✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), [Element Web](./configuring-playbook-client-element-web.md), Element X, FluffyChat) will be able to use the **new SSO-based login flow** provided by Matrix Authentication Service"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:78
+msgid "✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work. Going through the old login flow does not require users to have a verified email address, as [is the case](https://github.com/element-hq/matrix-authentication-service/issues/1505) for the new SSO-based login flow."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:80
+msgid "✅ [Registering users](./registering-users.md) via **the playbook's `register-user` tag remains unchanged**. The playbook automatically does the right thing regardless of homeserver implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, the playbook will forward user-registration requests to MAS. Registering users via the command-line is no longer done via the `/matrix/synapse/bin/register` script, but via `/matrix/matrix-authentication-service/bin/register-user`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:82
+msgid "✅ Users that are prepared by the playbook (for bots, bridges, etc.) will continue to be registered automatically as expected. The playbook automatically does the right thing regardless of homeserver implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, the playbook will forward user-registration requests to MAS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:84
+msgid "Installation flows"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:86
+msgid "New homeserver"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:88
+msgid "For new homeservers (which don't have any users in their Synapse database yet), follow the [Adjusting the playbook configuration](#adjusting-the-playbook-configuration) instructions and then proceed with [Installing](#installing)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:90
+msgid "Existing homeserver"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:92
+msgid "Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:94
+msgid "For existing Synapse homeservers:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:96
+msgid "when following the [Adjusting the playbook configuration](#adjusting-the-playbook-configuration) instructions, make sure to **disable the integration between Synapse and MAS** by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line as described in the [Marking an existing homeserver for migration](#marking-an-existing-homeserver-for-migration) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:98
+msgid "then follow the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) instructions to perform the installation and migration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:100
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:102
+msgid "To enable Matrix Authentication Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:116
+msgid "In the sub-sections that follow, we'll cover some additional configuration options that you may wish to adjust."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:118
+msgid "There are many other configuration options available. Consult the [`defaults/main.yml` file](../roles/custom/matrix-authentication-service/defaults/main.yml) in the [matrix-authentication-service role](../roles/custom/matrix-authentication-service/) to discover them."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:120
+msgid "Adjusting the Matrix Authentication Service URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:122
+msgid "By default, this playbook installs the Matrix Authentication Service on the `matrix.` subdomain, at the `/auth` path (https://matrix.example.com/auth). 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-matrix-authentication-service.md:124
+msgid "By tweaking the `matrix_authentication_service_hostname` and `matrix_authentication_service_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-matrix-authentication-service.md:126
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:149
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:134
+msgid "Marking an existing homeserver for migration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:136
+msgid "The [configuration above](#adjusting-the-playbook-configuration) instructs existing users wishing to migrate to add `matrix_authentication_service_migration_in_progress: true` to their configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:138
+msgid "This is done temporarily. The migration steps are described in more detail in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:140
+msgid "Upstream OAuth2 configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:142
+msgid "To make Matrix Authentication Service delegate to an existing upstream OAuth 2.0/OIDC provider, you can use its [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:144
+msgid "The playbook exposes a `matrix_authentication_service_config_upstream_oauth2_providers` variable for controlling this setting."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:261
+msgid "💡 Refer to the [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers) for the most up-to-date schema and example for providers. The value shown above here may be out of date."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:263
+msgid "⚠️ The syntax for existing [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) is slightly different, so you will need to adjust your configuration when switching from Synapse OIDC to MAS upstream OAuth2."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:265
+msgid "⚠️ When [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) which contains OIDC-sourced users, you will need to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:267
+msgid "[Configure upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:268
+msgid "go through the [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) process"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:269
+msgid "remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:271
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:273
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Matrix Authentication Service domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:275
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:277
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:279
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:281
+msgid "Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:288
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:290
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:292
+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-matrix-authentication-service.md:294
+msgid "If you're in the process of migrating an existing Synapse homeserver to MAS, you should now follow the rest of the steps in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) guide."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:296
+msgid "💡 After installation, you should [verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:298
+msgid "Migrating an existing Synapse homeserver to Matrix Authentication Service"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:300
+msgid "Our migration guide is loosely based on the upstream [Migrating an existing homeserver](https://element-hq.github.io/matrix-authentication-service/setup/migration.html) guide."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:302
+msgid "Migration is done via a tool called `syn2mas`, which the playbook could run for you (in a container)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:304
+msgid "The installation + migration steps are like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:306
+msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) to **disable the integration between the homeserver and MAS**. This is done by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:308
+msgid "Perform the initial [installation](#installing). At this point:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:310
+msgid "Matrix Authentication Service will be installed. Its database will be empty, so it cannot validate existing access tokens or authentication users yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:312
+msgid "The homeserver will still continue to use its local database for validating existing access tokens."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:314
+msgid "Various [compatibility layer URLs](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) are not yet installed. New login sessions will still be forwarded to the homeserver, which is capable of completing them."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:316
+msgid "The `matrix-user-creator` role would be suppressed, so that it doesn't automatically attempt to create users (for bots, etc.) in the MAS database. These user accounts likely already exist in Synapse's user database and could be migrated over (via syn2mas, as per the steps below), so creating them in the MAS database would have been unnecessary and potentially problematic (conflicts during the syn2mas migration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:318
+msgid "Consider taking a full [backup of your Postgres database](./maintenance-postgres.md#backing-up-postgresql). This is done just in case. The **syn2mas migration tool does not delete any data**, so it should be possible to revert to your previous setup by merely disabling MAS and re-running the playbook (no need to restore a Postgres backup). However, do note that as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:320
+msgid "[Migrate your data from Synapse to Matrix Authentication Service using syn2mas](#migrate-your-data-from-synapse-to-matrix-authentication-service-using-syn2mas)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:322
+msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) again, to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:324
+msgid "remove the `matrix_authentication_service_migration_in_progress: false` line"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:326
+msgid "if you had been using [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:328
+msgid "Perform the [installation](#installing) again. At this point:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:330
+msgid "The homeserver will start delegating authentication to MAS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:332
+msgid "The compatibility layer URLs will be installed. New login sessions will be completed by MAS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:334
+msgid "[Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:336
+msgid "Migrate your data from Synapse to Matrix Authentication Service using syn2mas"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:338
+msgid "We **don't** ask you to [run the `syn2mas` migration advisor command](https://element-hq.github.io/matrix-authentication-service/setup/migration.html#run-the-migration-advisor), because it only gives you the green light if your Synapse configuration (`homeserver.yaml`) is configured in a way that's compatible with MAS (delegating authentication to MAS; disabling Synapse's password config; etc.). Until we migrate your data with the `syn2mas` tool, we intentionally avoid doing these changes to allow existing user sessions to work."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:340
+msgid "You can invoke the `syn2mas` tool via the playbook by running the playbook's `matrix-authentication-service-syn2mas` tag. We recommend first doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:342
+msgid "Configuring syn2mas"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:344
+msgid "If you're using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to [Configuring upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:346
+msgid "If you only have local (non-OIDC) users in your Synapse database, you can likely run `syn2mas` as-is (without doing additional configuration changes)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:348
+msgid "When you're done with potentially configuring `syn2mas`, proceed to doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:350
+msgid "Configuring upstream OIDC provider mapping for syn2mas"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:352
+msgid "If you have existing OIDC users in your Synapse user database (which will be the case if when using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)), you may need to pass an additional `--upstreamProviderMapping` argument to the `syn2mas` tool to tell it which provider (on the Synapse side) maps to which other provider on the MAS side."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:354
+msgid "If you don't do this, `syn2mas` would report errors like this one:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:356
+msgid "[FATAL] migrate - [Failed to import external id 4264b0f0-4f11-4ddd-aedb-b500e4d07c25 with oidc-keycloak for user @alice:example.com: Error: Unknown upstream provider oidc-keycloak]"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:358
+msgid "Below is an example situation and a guide for how to solve it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:360
+msgid "If in `matrix_synapse_oidc_providers` your provider `idp_id` is (was) named `keycloak`, in the Synapse database users would be associated with the `oidc-keycloak` provider (note the `oidc-` prefix that was added automatically by Synapse to your `idp_id` value)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:362
+msgid "The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` on the MAS side, as defined in `matrix_authentication_service_config_upstream_oauth2_providers` (see the [Upstream OAuth2 configuration](#upstream-oauth2-configuration) section above)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:364
+msgid "To tell `syn2mas` how the Synapse-configured OIDC provider maps to the new MAS-configured OIDC provider, add this additional configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:373
+msgid "Performing a syn2mas dry-run"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:375
+msgid "Having [configured syn2mas](#configuring-syn2mas), we recommend doing a [dry-run](https://en.wikipedia.org/wiki/Dry_run_(testing)) first to verify that everything will work out as expected."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:377
+msgid "A dry-run would not cause downtime, because it avoids stopping Synapse."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:379
+msgid "To perform a dry-run, run:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:385
+msgid "Observe the command output (especially the last line of the the syn2mas output). If you are confident that the migration will work out as expected, you can proceed with a [real migration](#performing-a-real-syn2mas-migration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:387
+msgid "Performing a real syn2mas migration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:389
+msgid "Before performing a real migration make sure:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:391
+msgid "you've familiarized yourself with the [expectations](#expectations)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:393
+msgid "you've performed a Postgres backup, just in case"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:395
+msgid "you're aware of the irreversibility of the migration process without disruption after users have created new login sessions via the new MAS setup"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:397
+msgid "you've [configured syn2mas](#configuring-syn2mas), especially if you've used [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:399
+msgid "you've performed a [syn2mas dry-run](#performing-a-syn2mas-dry-run) and don't see any issues in its output"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:401
+msgid "To perform a real migration, run the `matrix-authentication-service-syn2mas` tag **without** the `matrix_authentication_service_syn2mas_dry_run` variable:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:407
+msgid "Having performed a `syn2mas` migration once, trying to do it again will report errors for users that were already migrated (e.g. \"Error: Unknown upstream provider oauth-delegated\")."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:409
+msgid "Verify that Matrix Authentication Service is installed correctly"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:411
+msgid "After [installation](#installing), run the `doctor` subcommand of the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) to verify that MAS is installed correctly."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:413
+msgid "You can do it:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:415
+msgid "either via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag: `just run-tags matrix-authentication-service-mas-cli-doctor`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:417
+msgid "or by running the `mas-cli` script on the server (which invokes the `mas-cli` tool inside a container): `/matrix/matrix-authentication-service/bin/mas-cli doctor`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:419
+msgid "If successful, you should see some output that looks like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:431
+msgid "Management"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:433
+msgid "You can use the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) (exposed via the `/matrix/matrix-authentication-service/bin/mas-cli` script) to perform administrative tasks against MAS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:435
+msgid "This documentation page already mentions:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:437
+msgid "the `mas-cli doctor` sub-command in the [Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly) section, which you can run via the CLI and via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:439
+msgid "the `mas-cli manage register-user` sub-command in the [Registering users](./registering-users.md) documentation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:441
+msgid "There are other sub-commands available. Run `/matrix/matrix-authentication-service/bin/mas-cli` to get an overview."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:443
+msgid "User registration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:445
+msgid "After Matrix Authentication Service is [installed](#installing), users need to be managed there (unless you're managing them in an [upstream OAuth2 provider](#upstream-oauth2-configuration))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:447
+msgid "You can register users new users as described in the [Registering users](./registering-users.md) documentation (via `mas-cli manage register-user` or the Ansible playbook's `register-user` tag)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:449
+msgid "Working around email deliverability issues"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:451
+msgid "Because Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user, you may need to work around email deliverability issues if [your email-sending configuration](./configuring-playbook-email.md) is not working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:453
+msgid "Matrix Authentication Service attempts to verify email addresses by sending a verification email to the address specified by the user whenever they log in to an account without a verified email address."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:455
+msgid "If email delivery is not working, **you can retrieve the email configuration code from the Matrix Authentication Service's logs** (`journalctl -fu matrix-authentication-service`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:457
+msgid "Alternatively, you can use the [`mas-cli` management tool](#management) to manually verify email addresses for users. Example: `/matrix/matrix-authentication-service/bin/mas-cli manage verify-email some.username email@example.com`"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po
new file mode 100644
index 000000000..a70b79d26
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-corporal.po
@@ -0,0 +1,129 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:1
+msgid "Setting up Matrix Corporal (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:5
+msgid "**WARNING**: This is an advanced feature! It requires prior experience with Matrix and a specific need for using [Matrix Corporal](https://github.com/devture/matrix-corporal). If you're unsure whether you have such a need, you most likely don't."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:9
+msgid "The playbook can install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:11
+msgid "In short, it's a sort of automation and firewalling service, which is helpful if you're instaling Matrix services in a controlled corporate environment."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:13
+msgid "See the project's [documentation](https://github.com/devture/matrix-corporal/blob/main/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:15
+msgid "If you decide that you'd like to let this playbook install it for you, you'd need to also:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:16
+msgid "(required) [set up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:17
+msgid "(optional, but encouraged) [set up the REST authentication password provider module](configuring-playbook-rest-auth.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:19
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:21
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:74
+msgid "Matrix Corporal operates with a specific Matrix user on your server. By default, it's `matrix-corporal` (controllable by the `matrix_corporal_reconciliation_user_id_local_part` setting, see above)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:76
+msgid "No matter what Matrix user ID you configure to run it with, make sure that:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:78
+msgid "the Matrix Corporal user is created by [registering it](registering-users.md) **with administrator privileges**. Use a password you remember, as you'll need to log in from time to time to create or join rooms"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:80
+msgid "the Matrix Corporal user is joined and has Admin/Moderator-level access to any rooms you want it to manage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:82
+msgid "Using a locally-stored static policy"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:84
+msgid "If you'd like to use a [static policy file](https://github.com/devture/matrix-corporal/blob/master/docs/policy-providers.md#static-file-pull-style-policy-provider), you can use a configuration like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:116
+msgid "To learn more about what the policy configuration, see the matrix-corporal documentation on [policy](https://github.com/devture/matrix-corporal/blob/master/docs/policy.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:118
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:120
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:127
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-aux-files,setup-corporal,start` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:129
+msgid "`just run-tags setup-aux-files,setup-corporal,start` is useful for maintaining your setup quickly 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 `just setup-all` runs the `ensure-matrix-users-created` tag too."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:131
+msgid "Matrix Corporal files"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:133
+msgid "The following local filesystem paths are mounted in the `matrix-corporal` container and can be used in your configuration (or policy):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:135
+msgid "`/matrix/corporal/config` is mounted at `/etc/matrix-corporal` (read-only)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:137
+msgid "`/matrix/corporal/var` is mounted at `/var/matrix-corporal` (read and write)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:139
+msgid "`/matrix/corporal/cache` is mounted at `/var/cache/matrix-corporal` (read and write)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:141
+msgid "As an example: you can create your own configuration files in `/matrix/corporal/config` and they will appear in `/etc/matrix-corporal` in the Docker container. Your configuration (stuff in `matrix_corporal_policy_provider_config`) needs to refer to these files via the local container paths - `/etc/matrix-corporal` (read-only), `/var/matrix-corporal` (read and write), `/var/cache/matrix-corporal` (read and write)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po
new file mode 100644
index 000000000..8996149c8
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-ldap-registration-proxy.po
@@ -0,0 +1,65 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:1
+msgid "Setting up matrix-ldap-registration-proxy (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:3
+msgid "The playbook can install and configure [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:5
+msgid "This proxy handles Matrix registration requests and forwards them to LDAP."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:7
+msgid "**Note**: This does support the full Matrix specification for registrations. It only provide a very coarse implementation of a basic password registration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:9
+msgid "Quickstart"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:11
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:22
+msgid "If you already use the [synapse external password provider via LDAP](configuring-playbook-ldap-auth.md) (that is, you have `matrix_synapse_ext_password_provider_ldap_enabled: true` and other options in your configuration) you can use the following values as configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:35
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:37
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:44
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:46
+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 ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po
new file mode 100644
index 000000000..82cecc0af
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-media-repo.po
@@ -0,0 +1,168 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:1
+msgid "Storing Matrix media files using matrix-media-repo (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:3
+msgid "[matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often abbreviated \"MMR\") is a highly customizable multi-domain media repository for Matrix. Intended for medium to large environments consisting of several homeservers, this media repo de-duplicates media (including remote media) while being fully compliant with the specification."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:5
+msgid "Smaller/individual homeservers can still make use of this project's features, though it may be difficult to set up or have higher than expected resource consumption. Please do your research before deploying this as this project may not be useful for your environment."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:7
+msgid "For a simpler alternative (which allows you to offload your media repository storage to S3, etc.), you can [configure S3 storage](configuring-playbook-s3.md) instead of setting up matrix-media-repo."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md
+msgid "**Table of Contents**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md
+msgid "[Quickstart](#quickstart)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md
+msgid "[Additional configuration options](#configuring-the-media-repo)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md
+msgid "[Importing data from an existing media store](#importing-data-from-an-existing-media-store)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:15
+msgid "Quickstart"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:17
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file and [re-run the installation process](./installing.md) for the playbook:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:26
+msgid "The repo is pre-configured for integrating with the Postgres database, Traefik proxy and [Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) (if metrics enabled) from this playbook for all the available homeserver roles. When the media repo is enabled, other media store roles should be disabled (if using Synapse with other media store roles)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:28
+msgid "By default, the media-repo will use the local filesystem for data storage. You can alternatively use a `s3` cloud backend as well. Access token caching is also enabled by default since the logout endpoints are proxied through the media repo."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:30
+msgid "Configuring the media-repo"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:32
+msgid "Additional common configuration options:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:91
+msgid "Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](../roles/custom/matrix-media-repo/defaults/main.yml)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:93
+msgid "Signing Keys"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:95
+msgid "Authenticated media endpoints ([MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916)) requires MMR to have a configured signing key to authorize outbound federation requests. Additionally, the signing key must be merged with your homeserver's signing key file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:97
+msgid "The playbook default is to generate a MMR signing key when invoking the setup role and merge it with your homeserver if you are using Synapse or Dendrite. This can be disabled if desired by setting the option in your inventory:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:103
+msgid "If you wish to manually generate the signing key and merge it with your homeserver's signing key file, see https://docs.t2bot.io/matrix-media-repo/v1.3.5/installation/signing-key/ for more details."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:105
+msgid "**Note that if you uninstall MMR from the playbook, it will not remove the old MMR signing key from your homeserver's signing key file. You will have to remove it manually.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:107
+msgid "Key backup and revoking"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:109
+msgid "Since your homeserver signing key file is modified by the playbook, a backup will be created in `HOMESERVER_DIR/config/example.com.signing.key.backup`. If you need to remove/revoke old keys, you can restore from this backup or remove the MMR key ID from your `example.com.signing.key` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:111
+msgid "Additionally, its recommended after revoking a signing key to update your homeserver config file (`old_signing_keys` field for Synapse and `old_private_keys` for Dendrite). See your homeserver config file for further documentation on how to populate the field."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:113
+msgid "Importing data from an existing media store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:115
+msgid "If you want to add this repo to an existing homeserver managed by the playbook, you will need to import existing media into MMR's database or you will lose access to older media while it is active. MMR versions up to `v1.3.3` only support importing from Synapse, but newer versions (at time of writing: only `latest`) also support importing from Dendrite."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:117
+msgid "**Before importing**: ensure you have an initial matrix-media-repo deployment by following the [quickstart](#quickstart) guide above"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:119
+msgid "Depending on the homeserver implementation yu're using (Synapse, Dendrite), you'll need to use a different import tool (part of matrix-media-repo) and point it to the homeserver's database."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:121
+msgid "Importing data from the Synapse media store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:123
+msgid "To import the Synapse media store, you're supposed to invoke the `import_synapse` tool which is part of the matrix-media-repo container image. Your Synapse database is called `synapse` by default, unless you've changed it by modifying `matrix_synapse_database_database`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:125
+msgid "This guide here is adapted from the [upstream documentation about the import_synapse script](https://github.com/turt2live/matrix-media-repo#importing-media-from-synapse)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:127
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:149
+msgid "Run the following command on the server (after replacing `postgres_connection_password` in it with the value found in your `vars.yml` file):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:139
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:161
+msgid "Enter `1` for the Machine ID when prompted (you are not doing any horizontal scaling) unless you know what you're doing."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:141
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:163
+msgid "This should output a `msg=\"Import completed\"` when finished successfully!"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:143
+msgid "Importing data from the Dendrite media store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:145
+msgid "If you're using the [Dendrite](configuring-playbook-dendrite.md) homeserver instead of the default for this playbook (Synapse), follow this importing guide here."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:147
+msgid "To import the Dendrite media store, you're supposed to invoke the `import_dendrite` tool which is part of the matrix-media-repo container image. Your Dendrite database is called `dendrite_mediaapi` by default, unless you've changed it by modifying `matrix_dendrite_media_api_database`."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po
new file mode 100644
index 000000000..40876be5f
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-registration.po
@@ -0,0 +1,157 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:1
+msgid "Setting up matrix-registration (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:3
+msgid "The playbook can install and configure [matrix-registration](https://github.com/ZerataX/matrix-registration) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:5
+msgid "**WARNING**: this is a poorly maintained and buggy project. It's better to avoid using it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:7
+msgid "**WARNING**: this is not related to [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:9
+msgid "matrix-registration is a simple python application to have a token based Matrix registration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:11
+msgid "Use matrix-registration to **create unique registration links**, which people can use to register on your Matrix server. It allows you to **keep your server's registration closed (private)**, but still allow certain people (these having a special link) to register a user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:13
+msgid "**matrix-registration** provides 2 things:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:15
+msgid "**an API for creating registration tokens** (unique registration links). This API can be used via `curl` or via the playbook (see [Usage](#usage) below)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:17
+msgid "**a user registration page**, where people can use these registration tokens. By default, exposed at `https://matrix.example.com/matrix-registration`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:19
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:21
+msgid "To enable matrix-registration, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:30
+msgid "Adjusting the matrix-registration URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:32
+msgid "By default, this playbook installs the matrix-registration on the `matrix.` subdomain, at the `/matrix-registration` path (https://matrix.example.com/matrix-registration). 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-matrix-registration.md:34
+msgid "By tweaking the `matrix_registration_hostname` and `matrix_registration_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-matrix-registration.md:36
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:44
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:46
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-registration domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:48
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:50
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:52
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:54
+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-matrix-registration.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-matrix-registration.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-matrix-registration.md:65
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:67
+msgid "**matrix-registration** gets exposed at `https://matrix.example.com/matrix-registration`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:69
+msgid "It provides various [APIs](https://github.com/ZerataX/matrix-registration/wiki/api) - for creating registration tokens, listing tokens, disabling tokens, etc. To make use of all of its capabilities, consider using `curl`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:71
+msgid "We make the most common APIs easy to use via the playbook (see below)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:73
+msgid "Creating registration tokens"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:75
+msgid "To **create a new user registration token (link)**, use this command:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:83
+msgid "The above command creates and returns a **one-time use** token, which **expires** on the 31st of December 2021. Adjust the `one_time` and `ex_date` variables as you see fit."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:85
+msgid "Share the unique registration link (generated by the command above) with users to let them register on your Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:87
+msgid "Listing registration tokens"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:89
+msgid "To **list the existing user registration tokens**, use this command:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:96
+msgid "The shortcut command with `just` program is also available: `just run-tags list-matrix-registration-tokens`"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po
new file mode 100644
index 000000000..be3cde9a5
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-mautrix-bridges.po
@@ -0,0 +1,182 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:1
+msgid "Setting up a Generic Mautrix Bridge (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:3
+msgid "The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, facebook, instagram, signal, hangouts, googlechat, etc.), as well as many other (non-mautrix) bridges. This is a common guide for configuring mautrix bridges."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:5
+msgid "You can see each bridge's features at in the `ROADMAP.md` file in its corresponding [mautrix](https://github.com/mautrix) repository."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:9
+msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:16
+msgid "There are some additional things you may wish to configure about the bridge before you continue. Each bridge may have additional requirements besides `_enabled: true`. For example, the mautrix-telegram bridge (our documentation page about it is [here](configuring-playbook-bridge-mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and `matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each bridge's individual documentation page for details about enabling bridges."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:18
+msgid "To **configure a user as an administrator for all bridges**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:24
+msgid "**Alternatively** (more verbose, but allows multiple admins to be configured), you can do the same on a per-bridge basis with:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:33
+msgid "encryption"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:35
+msgid "Encryption support is off by default. If you would like to enable encryption, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:37
+msgid "**for all bridges with encryption support**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:44
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:61
+msgid "**Alternatively**, for a specific bridge:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:51
+msgid "relay mode"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:53
+msgid "Relay mode is off by default. If you would like to enable relay mode, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:55
+msgid "**for all bridges with relay mode support**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:70
+msgid "You can only have one `matrix_mautrix_SERVICENAME_configuration_extension_yaml` definition in `vars.yml` per bridge, so if you need multiple pieces of configuration there, just merge them like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:82
+msgid "Setting the bot's username"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:88
+msgid "Can be used to set the username for the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:90
+msgid "Discovering additional configuration options"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:92
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-SERVICENAME/defaults/main.yml` to find other things you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:94
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:96
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:103
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:105
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:107
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:109
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:111
+msgid "Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:113
+msgid "To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:115
+msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) is configured and enabled on the server for this playbook by adding"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:121
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:123
+msgid "Controlling the logging level"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:129
+msgid "to `vars.yml` to control the logging level, where you may replace WARN with one of the following to control the verbosity of the logs generated: TRACE, DEBUG, INFO, WARN, ERROR, or FATAL."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:131
+msgid "If you have issues with a service, and are requesting support, the higher levels of logging will generally be more helpful."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:133
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:135
+msgid "To use the bridge, you need to start a chat with `@SERVICENAMEbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:137
+msgid "Send `login` to the bridge bot to get started. You can learn more here about authentication from the bridge's official documentation on Authentication: https://docs.mau.fi/bridges/python/SERVICENAME/authentication.html"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:139
+msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:141
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:143
+msgid "For troubleshooting information with a specific bridge, please see the playbook documentation about it (some other document in in `docs/`) and the upstream ([mautrix](https://github.com/mautrix)) bridge documentation for that specific bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:145
+msgid "Reporting bridge bugs should happen upstream, in the corresponding mautrix repository, not to us."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-nginx.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-nginx.po
new file mode 100644
index 000000000..b5899561a
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-nginx.po
@@ -0,0 +1,29 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-nginx.md:1
+msgid "Configure Nginx (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-nginx.md:3
+msgid "Since 2024-01, this playbook no longer uses nginx as its reverse-proxy."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ntfy.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ntfy.po
new file mode 100644
index 000000000..5caa7e81c
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ntfy.po
@@ -0,0 +1,237 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-ntfy.md:1
+msgid "Setting up the ntfy push notifications server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:3
+msgid "The playbook can install and configure the [ntfy](https://ntfy.sh/) push notifications server for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:5
+msgid "Using the [UnifiedPush](https://unifiedpush.org) standard, ntfy enables self-hosted (Google-free) push notifications from Matrix (and other) servers to UnifiedPush-compatible Matrix compatible client apps running on Android and other devices."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:7
+msgid "This role is intended to support UnifiedPush notifications for use with the Matrix and Matrix-related services that this playbook installs. This role is not intended to support all of ntfy's other features."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:9
+msgid "**Note**: In contrast to push notifications using Google's FCM or Apple's APNs, the use of UnifiedPush allows each end-user to choose the push notification server that they prefer.  As a consequence, deploying this ntfy server does not by itself ensure any particular user or device or client app will use it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:13
+msgid "To enable ntfy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:27
+msgid "For a more complete list of variables that you could override, see the [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/defaults/main.yml) of the ntfy Ansible role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:29
+msgid "For a complete list of ntfy config options that you could put in `ntfy_configuration_extension_yaml`, see the [ntfy config documentation](https://ntfy.sh/docs/config/#config-options)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:31
+msgid "Adjusting the ntfy URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:33
+msgid "By default, this playbook installs ntfy on the `ntfy.` subdomain (`ntfy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:35
+msgid "By tweaking the `ntfy_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:37
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:44
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:46
+msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the ntfy domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:48
+msgid "By default, you will need to create a CNAME record for `ntfy`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:50
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:52
+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-ntfy.md:59
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:61
+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-ntfy.md:63
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:65
+msgid "To make use of your ntfy installation, on Android for example, you need two things:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:67
+msgid "the `ntfy` app"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:68
+msgid "a UnifiedPush-compatible Matrix app"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:70
+msgid "You need to install the `ntfy` app on each device on which you want to receive push notifications through your ntfy server. The `ntfy` app will provide UnifiedPush notifications to any number of UnifiedPush-compatible messaging apps installed on the same device."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:72
+msgid "Setting up the `ntfy` Android app"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:74
+msgid "Install the [ntfy Android app](https://ntfy.sh/docs/subscribe/phone/) from F-droid or Google Play."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:75
+msgid "In its Settings -> `General: Default server`, enter your ntfy server URL, such as `https://ntfy.example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:76
+msgid "In its Settings -> `Advanced: Connection protocol`, choose `WebSockets`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:78
+msgid "That is all you need to do in the ntfy app. It has many other features, but for our purposes you can ignore them. In particular you do not need to follow any instructions about subscribing to a notification topic as UnifiedPush will do that automatically."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:80
+msgid "Setting up a UnifiedPush-compatible Matrix app"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:82
+msgid "Install any UnifiedPush-enabled Matrix app on that same device. The Matrix app will learn from the `ntfy` app that you have configured UnifiedPush on this device, and then it will tell your Matrix server to use it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:84
+msgid "Steps needed for specific Matrix apps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:86
+msgid "FluffyChat-android:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:87
+msgid "Should auto-detect and use it. No manual settings."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:89
+msgid "SchildiChat-android:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:90
+msgid "enable `Settings` -> `Notifications` -> `UnifiedPush: Force custom push gateway`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:91
+msgid "choose `Settings` -> `Notifications` -> `UnifiedPush: Re-register push distributor`. *(For info, a more complex alternative to achieve the same is: delete the relevant unifiedpush registration in `ntfy` app, force-close SchildiChat, re-open it.)*"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:92
+msgid "verify `Settings` -> `Notifications` -> `UnifiedPush: Notification targets` as described below in the \"Troubleshooting\" section."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:94
+msgid "Element-android v1.4.26+:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:95
+msgid "choose `Settings` -> `Notifications` -> `Notification method` -> `ntfy`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:96
+msgid "verify `Settings` -> `Troubleshoot` -> `Troubleshoot notification settings`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:98
+msgid "If the Matrix app asks, \"Choose a distributor: FCM Fallback or ntfy\", then choose \"ntfy\"."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:100
+msgid "If the Matrix app doesn't seem to pick it up, try restarting it and try the Troubleshooting section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:102
+msgid "Web App"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:104
+msgid "ntfy also has a web app to subscribe to and push to topics from the browser. This may be helpful to further troubleshoot UnifiedPush problems or to use ntfy for other purposes. The web app only runs in the browser locally (after downloading the JavaScript)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:106
+msgid "The web app is disabled in this playbook by default as the expectation is that most users won't use it. You can either use the [official hosted one](https://ntfy.sh/app) (it supports using other public reachable ntfy instances) or host it yourself by setting `ntfy_web_root: \"app\"` and re-running Ansible."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:108
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:110
+msgid "First check that the Matrix client app you are using supports UnifiedPush. There may well be different variants of the app."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:112
+msgid "Set the ntfy server's log level to 'DEBUG', as shown in the example settings above, and watch the server's logs with `sudo journalctl -fu matrix-ntfy`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:114
+msgid "To check if UnifiedPush is correctly configured on the client device, look at \"Settings -> Notifications -> Notification Targets\" in Element Android or SchildiChat Android, or \"Settings -> Notifications -> Devices\" in FluffyChat. There should be one entry for each Matrix client app that has enabled push notifications, and when that client is using UnifiedPush you should see a URL that begins with your ntfy server's URL."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:116
+msgid "In the \"Notification Targets\" screen in Element Android or SchildiChat Android, two relevant URLs are shown, \"push\\_key\" and \"Url\", and both should begin with your ntfy server's URL. If \"push\\_key\" shows your server but \"Url\" shows an external server such as `up.schildi.chat` then push notifications will still work but are being routed through that external server before they reach your ntfy server. To rectify that, in SchildiChat (at least around version 1.4.20.sc55) you must enable the `Force custom push gateway` setting as described in the \"Usage\" section above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:118
+msgid "If it is not working, useful tools are \"Settings -> Notifications -> Re-register push distributor\" and \"Settings -> Notifications -> Troubleshoot Notifications\" in SchildiChat Android (possibly also Element Android). In particular the \"Endpoint/FCM\" step of that troubleshooter should display your ntfy server's URL that it has discovered from the ntfy client app."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:120
+msgid "The simple [UnifiedPush troubleshooting](https://unifiedpush.org/users/troubleshooting/) app [UP-Example](https://f-droid.org/en/packages/org.unifiedpush.example/) can be used to manually test UnifiedPush registration and operation on an Android device."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-own-webserver.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-own-webserver.po
new file mode 100644
index 000000000..290a02620
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-own-webserver.po
@@ -0,0 +1,193 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-own-webserver.md:1
+msgid "Using your own webserver, instead of this playbook's Traefik reverse-proxy (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:3
+msgid "By default, this playbook installs its own [Traefik](https://traefik.io/) reverse-proxy server (in a Docker container) which listens on ports 80 and 443. If that's okay, you can skip this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:5
+msgid "Traefik"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:7
+msgid "[Traefik](https://traefik.io/) is the default reverse-proxy for the playbook since [2023-02-26](../CHANGELOG.md/#2023-02-26) and serves **2 purposes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:9
+msgid "serving public traffic and providing SSL-termination with certificates obtained from [Let's Encrypt](https://letsencrypt.org/). See [Adjusting SSL certificate retrieval](./configuring-playbook-ssl-certificates.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:11
+msgid "assists internal communication between addon services (briges, bots, etc.) and the homeserver via an internal entrypoint (`matrix-internal-matrix-client-api`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:13
+msgid "There are 2 ways to use Traefik with this playbook, as described below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:15
+msgid "Traefik managed by the playbook"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:17
+msgid "To have the playbook install and use Traefik, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:25
+msgid "Traefik will manage SSL certificates for all services seamlessly."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:27
+msgid "Traefik managed by you"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:53
+msgid "In this mode all roles will still have Traefik labels attached. You will, however, need to configure your Traefik instance and its entrypoints."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:55
+msgid "By default, the playbook configured a `default` certificate resolver and multiple entrypoints."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:57
+msgid "You need to configure 4 entrypoints for your Traefik server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:59
+msgid "`web` (TCP port `80`) - used for redirecting to HTTPS (`web-secure`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:60
+msgid "`web-secure` (TCP port `443`) - used for exposing the Matrix Client-Server API and all other services"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:61
+msgid "`matrix-federation` (TCP port `8448`) - used for exposing the Matrix Federation API"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:62
+msgid "`matrix-internal-matrix-client-api` (TCP port `8008`) - used internally for addon services (bridges, bots) to communicate with the homserver"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:64
+msgid "Below is some configuration for running Traefik yourself, although we recommend using [Traefik managed by the playbook](#traefik-managed-by-the-playbook)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:66
+msgid "Note that this configuration on its own does **not** redirect traffic on port 80 (plain HTTP) to port 443 for HTTPS. If you are not already doing this in Traefik, it can be added to Traefik in a [file provider](https://docs.traefik.io/v2.0/providers/file/) as follows:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:86
+msgid "You can use the following `docker-compose.yml` as example to launch Traefik."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:122
+msgid "Another webserver"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:124
+msgid "If you don't wish to use Traefik, you can also use your own webserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:126
+msgid "Doing this is possible, but requires manual work."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:128
+msgid "There are 2 ways to go about it:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:130
+msgid "(recommended) [Fronting the integrated reverse-proxy webserver with another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) - using the playbook-managed reverse-proxy (Traefik), but disabling SSL termination for it, exposing this reverse-proxy on a few local ports (e.g. `127.0.0.1:81`, etc.) and forwarding traffic from your own webserver to those few ports"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:132
+msgid "(difficult) [Using no reverse-proxy on the Matrix side at all](#using-no-reverse-proxy-on-the-matrix-side-at-all) disabling the playbook-managed reverse-proxy (Traefik), exposing services one by one using `_host_bind_port` variables and forwarding traffic from your own webserver to those ports"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:134
+msgid "Fronting the integrated reverse-proxy webserver with another reverse-proxy"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:136
+msgid "This method is about leaving the integrated reverse-proxy webserver be, but making it not get in the way (using up important ports, trying to retrieve SSL certificates, etc.)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:138
+msgid "If you wish to use another webserver, the integrated reverse-proxy webserver usually gets in the way because it attempts to fetch SSL certificates and binds to ports 80, 443 and 8448 (if Matrix Federation is enabled)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:140
+msgid "You can disable such behavior and make the integrated reverse-proxy webserver only serve traffic locally on the host itself (or over a local network)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:142
+msgid "This is the recommended way for using another reverse-proxy, because the integrated one would act as a black box and wire all Matrix services correctly. You would then only need to reverse-proxy a few individual domains and ports over to it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:144
+msgid "To front Traefik with another reverse-proxy, you would need some configuration like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:194
+msgid "Such a configuration would expose all services on a local port `81` and Matrix Federation on a local port `8449`. Your reverse-proxy configuration needs to send traffic to these ports. [`examples/reverse-proxies`](../examples/reverse-proxies/) contains examples for various webservers such as Apache2, Caddy, HAproxy, nginx and Nginx Proxy Manager."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:196
+msgid "It's important that these webservers proxy-pass requests to the correct `ip:port` and also set the `Host` HTTP header appropriately. If you don't pass the `Host` header correctly, Traefik will return a `404 - not found` error."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:198
+msgid "To put it another way:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:199
+msgid "`curl http://127.0.0.1:81` will result in a `404 - not found` error"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:200
+msgid "but `curl -H 'Host: matrix.example.com' http://127.0.0.1:81` should work."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:202
+msgid "Using no reverse-proxy on the Matrix side at all"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:204
+msgid "Instead of [Fronting the integrated reverse-proxy webserver with another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy), you can also go another way -- completely disabling the playbook-managed Traefik reverse-proxy. You would then need to reverse-proxy from your own webserver directly to each individual Matrix service."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:206
+msgid "This is more difficult, as you would need to handle the configuration for each service manually. Enabling additional services would come with extra manual work you need to do."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:208
+msgid "Also, the Traefik reverse-proxy, besides fronting everything is also serving a 2nd purpose of allowing addons services to communicate with the Matrix homeserver thanks to its `matrix-internal-matrix-client-api` entrypoint (read more about it above). Disabling Traefik completely means the playbook would wire services to directly talk to the homeserver. This can work for basic setups, but not for more complex setups involving [matrix-media-repo](./configuring-playbook-matrix-media-repo.md), [matrix-corporal](./configuring-playbook-matrix-corporal.md) or other such services that need to \"steal routes\" from the homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:210
+msgid "If your webserver is on the same machine, ensure your web server user (something like `http`, `apache`, `www-data`, `nginx`) is part of the `matrix` group. You should run something like this: `usermod -a -G matrix nginx`. This allows your webserver user to access files owned by the `matrix` group, so that it can serve static files from `/matrix/static-files`."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po
new file mode 100644
index 000000000..ace9e5689
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-pantalaimon.po
@@ -0,0 +1,65 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:1
+msgid "Setting up Pantalaimon (E2EE aware proxy daemon) (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:3
+msgid "The playbook can install and configure the [pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:5
+msgid "See the project's [documentation](https://github.com/matrix-org/pantalaimon/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:7
+msgid "This role exposes Pantalaimon's API only within the container network, so bots and clients installed on the same machine can use it. In particular the [Draupnir](configuring-playbook-bot-draupnir.md) and [Mjolnir](configuring-playbook-bot-mjolnir.md) roles (and possibly others) can use it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:11
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:17
+msgid "The default configuration should suffice. For advanced configuration, you can override the variables documented in the role's [defaults](../roles/custom/matrix-pantalaimon/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:19
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:21
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:28
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:30
+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 ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po
new file mode 100644
index 000000000..b5aa2c366
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-postgres-backup.po
@@ -0,0 +1,157 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:1
+msgid "Setting up postgres backup (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:3
+msgid "The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you via the [ansible-role-postgres-backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup) Ansible role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:5
+msgid "For a more complete backup solution (one that includes not only Postgres, but also other configuration/data files), you may wish to look into [BorgBackup](configuring-playbook-backup-borg.md) instead."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:9
+msgid "To enable Postgres backup, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:15
+msgid "Refer to the table below for additional configuration variables and their default values."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Name"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Default value"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Description"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`postgres_backup_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`false`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Set to true to use [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) to create automatic database backups"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`postgres_backup_schedule`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`'@daily'`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Cron-schedule specifying the interval between postgres backups."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`postgres_backup_keep_days`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`7`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Number of daily backups to keep"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`postgres_backup_keep_weeks`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`4`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Number of weekly backups to keep"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`postgres_backup_keep_months`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`12`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Number of monthly backups to keep"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`postgres_backup_base_path`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`\"{{ matrix_base_data_path }}/postgres-backup\"`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Base path for postgres-backup. Also see `postgres_backup_data_path`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`postgres_backup_data_path`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "`\"{{ postgres_backup_base_path }}/data\"`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md
+msgid "Storage path for postgres-backup database backups"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:27
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:29
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:36
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:38
+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 ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po
new file mode 100644
index 000000000..9c69c7e0d
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-grafana.po
@@ -0,0 +1,345 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:1
+msgid "Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:3
+msgid "The playbook can install [Grafana](https://grafana.com/) with [Prometheus](https://prometheus.io/) and configure performance metrics of your homeserver with graphs for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:5
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:7
+msgid "To enable Grafana and/or Prometheus, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:33
+msgid "The retention policy of Prometheus metrics is [15 days by default](https://prometheus.io/docs/prometheus/latest/storage/#operational-aspects). Older data gets deleted automatically."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:35
+msgid "Adjusting the Grafana URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:37
+msgid "By default, this playbook installs Grafana web user-interface on the `stats.` subdomain (`stats.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:39
+msgid "By tweaking the `grafana_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:41
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:48
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:50
+msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the Grafana domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:52
+msgid "By default, you will need to create a CNAME record for `stats`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:54
+msgid "**Note**: It is possible to install Prometheus without installing Grafana. This case it is not required to create the CNAME record."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:56
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:58
+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-prometheus-grafana.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-prometheus-grafana.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-prometheus-grafana.md:69
+msgid "What does it do?"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Name"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Description"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`prometheus_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`prometheus_node_exporter_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "[Node Exporter](https://prometheus.io/docs/guides/node-exporter/) is an addon of sorts to Prometheus that collects generic system information such as CPU, memory, filesystem, and even system temperatures"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`prometheus_postgres_exporter_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an addon of sorts to expose Postgres database metrics to Prometheus."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_prometheus_nginxlog_exporter_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "[NGINX Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose NGINX logs to Prometheus."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`grafana_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "[Grafana](https://grafana.com/) is the visual component. It shows (on the `stats.example.com` subdomain) the dashboards with the graphs that we're interested in"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`grafana_anonymous_access`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`grafana_default_admin_user`<br>`grafana_default_admin_password`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "By default Grafana creates a user with `admin` as the username and password. If you feel this is insecure and you want to change it beforehand, you can do that here"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:81
+msgid "Security and privacy"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:83
+msgid "Metrics and resulting graphs can contain a lot of information. This includes system specs but also usage patterns. This applies especially to small personal/family scale homeservers. Someone might be able to figure out when you wake up and go to sleep by looking at the graphs over time. Think about this before enabling anonymous access. And you should really not forget to change your Grafana password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:85
+msgid "Most of our docker containers run with limited system access, but the `prometheus-node-exporter` has access to the host network stack and (readonly) root filesystem. This is required to report on them. If you don't like that, you can set `prometheus_node_exporter_enabled: false` (which is actually the default). You will still get Synapse metrics with this container disabled. Both of the dashboards will always be enabled, so you can still look at historical data after disabling either source."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:87
+msgid "Collecting metrics to an external Prometheus server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:89
+msgid "**If the integrated Prometheus server is enabled** (`prometheus_enabled: true`), metrics are collected by it from each service via communication that happens over the container network. Each service does not need to expose its metrics \"publicly\"."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:91
+msgid "When you'd like **to collect metrics from an external Prometheus server**, you need to expose service metrics outside of the container network."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:93
+msgid "The playbook provides a single endpoint (`https://matrix.example.com/metrics/*`), under which various services may expose their metrics (e.g. `/metrics/node-exporter`, `/metrics/postgres-exporter`, `/metrics/hookshot`, etc). To expose all services on this `/metrics/*` feature, use `matrix_metrics_exposure_enabled`. To protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication), see `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users` below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:95
+msgid "When using `matrix_metrics_exposure_enabled`, you don't need to expose metrics for individual services one by one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:97
+msgid "The following variables may be of interest:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_metrics_exposure_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to **enable metrics exposure for all services** on `https://matrix.example.com/metrics/*`. If you think this is too much, refer to the helpful (but nonexhaustive) list of individual `matrix_SERVICE_metrics_proxying_enabled` (or similar) variables below for exposing metrics on a per-service basis."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_metrics_exposure_http_basic_auth_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to protect all `https://matrix.example.com/metrics/*` endpoints with [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) (see the other variables below for supplying the actual credentials). When enabled, all endpoints beneath `/metrics` will be protected with the same credentials"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_metrics_exposure_http_basic_auth_users`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to the Basic Authentication credentials (raw `htpasswd` file content) used to protect `/metrics/*`. This htpasswd-file needs to be generated with the `htpasswd` tool and can include multiple username/password pairs."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_synapse_metrics_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to make Synapse expose metrics (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_synapse_metrics_proxying_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to expose Synapse's metrics on `https://matrix.example.com/metrics/synapse/main-process` and `https://matrix.example.com/metrics/synapse/worker/TYPE-ID`. Read [below](#collecting-synapse-worker-metrics-to-an-external-prometheus-server) if you're running a Synapse worker setup (`matrix_synapse_workers_enabled: true`). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to enable the node (general system stats) exporter (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`prometheus_node_exporter_container_labels_traefik_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to expose the node (general system stats) metrics on `https://matrix.example.com/metrics/node-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to enable the [Postgres exporter](configuring-playbook-prometheus-postgres.md) (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to expose the [Postgres exporter](configuring-playbook-prometheus-postgres.md) metrics on `https://matrix.example.com/metrics/postgres-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to enable the [NGINX Log exporter](configuring-playbook-prometheus-nginxlog.md) (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_sliding_sync_metrics_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) expose metrics (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_sliding_sync_metrics_proxying_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to expose the [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) metrics on `https://matrix.example.com/metrics/sliding-sync`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_bridge_hookshot_metrics_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to make [Hookshot](configuring-playbook-bridge-hookshot.md) expose metrics (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_bridge_hookshot_metrics_proxying_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to expose the [Hookshot](configuring-playbook-bridge-hookshot.md) metrics on `https://matrix.example.com/metrics/hookshot`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_SERVICE_metrics_proxying_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Various other services/roles may provide similar `_metrics_enabled` and `_metrics_proxying_enabled` variables for exposing their metrics. Refer to each role for details. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above or `matrix_SERVICE_container_labels_metrics_middleware_basic_auth_enabled`/`matrix_SERVICE_container_labels_metrics_middleware_basic_auth_users` variables provided by each role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "`matrix_media_repo_metrics_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md
+msgid "Set this to `true` to make media-repo expose metrics (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:118
+msgid "Collecting Synapse worker metrics to an external Prometheus server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:120
+msgid "If you are using workers (`matrix_synapse_workers_enabled: true`) and have enabled `matrix_synapse_metrics_proxying_enabled` as described above, the playbook will also automatically expose all Synapse worker threads' metrics to `https://matrix.example.com/metrics/synapse/worker/ID`, where `ID` corresponds to the worker `id` as exemplified in `matrix_synapse_workers_enabled_list`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:122
+msgid "The playbook also generates an exemplary config file (`/matrix/synapse/external_prometheus.yml.template`) with all the correct paths which you can copy to your Prometheus server and adapt to your needs. Make sure to edit the specified `password_file` path and contents and path to your `synapse-v2.rules`. It will look a bit like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:150
+msgid "More information"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:152
+msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:153
+msgid "[Understanding Synapse Performance Issues Through Grafana Graphs](https://element-hq.github.io/synapse/latest/usage/administration/understanding_synapse_through_grafana_graphs.html) at the Synapse Github Wiki"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:154
+msgid "[The Prometheus scraping rules](https://github.com/element-hq/synapse/tree/master/contrib/prometheus) (we use v2)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:155
+msgid "[The Synapse Grafana dashboard](https://github.com/element-hq/synapse/tree/master/contrib/grafana)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:156
+msgid "[The Node Exporter dashboard](https://github.com/rfrail3/grafana-dashboards) (for generic non-synapse performance graphs)"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po
new file mode 100644
index 000000000..24ad7ec2b
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-nginxlog.po
@@ -0,0 +1,113 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:1
+msgid "Enabling metrics and graphs for NginX logs (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:3
+msgid "It can be useful to have some (visual) insight into [nginx](https://nginx.org/) logs."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:5
+msgid "This adds [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) to your Matrix deployment."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:7
+msgid "It will collect access logs from various nginx reverse-proxies which may be used internally (e.g. `matrix-synapse-reverse-proxy-companion`, if Synapse workers are enabled) and will make them available at a Prometheus-compatible `/metrics` endpoint."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:9
+msgid "**Note**: nginx is only used internally by this Ansible playbook. With Traefik being our default reverse-proxy, collecting nginx metrics is less relevant."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:11
+msgid "To make use of this, you need to install [Prometheus](./configuring-playbook-prometheus-grafana.md) either via the playbook or externally. When using an external Prometheus, configuration adjustments are necessary - see [Save metrics on an external Prometheus server](#save-metrics-on-an-external-prometheus-server)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:13
+msgid "If your setup includes [Grafana](./configuring-playbook-prometheus-grafana.md), a dedicated `NGINX PROXY` Grafana dashboard will be created."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:15
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:17
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:23
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:25
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:32
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:34
+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-prometheus-nginxlog.md:36
+msgid "Docker Image Compatibility"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:38
+msgid "At the moment of writing only images for `amd64` and `arm64` architectures are available. The playbook currently does not support [self-building](./self-building.md) a container image on other architectures. You can however use a custom-build image by setting:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:45
+msgid "Security and privacy"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:47
+msgid "Metrics and resulting graphs can contain a lot of information. NginX logs contain information like IP address, URLs, UserAgents and more. This information can reveal usage patterns and could be considered Personally Identifiable Information (PII). Think about this before enabling (anonymous) access. Please make sure you change the default Grafana password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:49
+msgid "Save metrics on an external Prometheus server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:51
+msgid "The playbook will automatically integrate the metrics into the [Prometheus](./configuring-playbook-prometheus-grafana.md) server provided with this playbook (if enabled). In such cases, the metrics endpoint is not exposed publicly - it's only available on the container network."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:53
+msgid "When using an external Prometheus server, you'll need to expose metrics publicly. See [Collecting metrics to an external Prometheus server](./configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:55
+msgid "You can either use `matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled: true` to expose just this one service, or `matrix_metrics_exposure_enabled: true` to expose all services."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:57
+msgid "Whichever way you go with, this service will expose its metrics endpoint **without password-protection** at `https://matrix.example.com/metrics/nginxlog` by default."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:59
+msgid "For password-protection, use (`matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`) or (`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po
new file mode 100644
index 000000000..c512d1462
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-prometheus-postgres.po
@@ -0,0 +1,105 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:1
+msgid "Enabling metrics and graphs for Postgres (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:3
+msgid "Expanding on the metrics exposed by the [synapse exporter and the node exporter](configuring-playbook-prometheus-grafana.md), the playbook enables the [postgres exporter](https://github.com/prometheus-community/postgres_exporter) that exposes more detailed information about what's happening on your postgres database."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:5
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:7
+msgid "To enable the postgres exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:13
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:15
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:22
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:24
+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-prometheus-postgres.md:26
+msgid "What does it do?"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "Name"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "Description"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "`prometheus_postgres_exporter_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "Enable the postgres prometheus exporter. This sets up the docker container, connects it to the database and adds a 'job' to the prometheus config which tells prometheus about this new exporter. The default is 'false'"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "`prometheus_postgres_exporter_database_username`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "The 'username' for the user that the exporter uses to connect to the database. The default is 'matrix_prometheus_postgres_exporter'"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "`prometheus_postgres_exporter_database_password`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "The 'password' for the user that the exporter uses to connect to the database. By default, this is auto-generated by the playbook"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md
+msgid "If set to `true`, exposes the Postgres exporter metrics on `https://matrix.example.com/metrics/postgres-exporter` for usage with an [external Prometheus server](configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` on that other documentation page."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:35
+msgid "More information"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:37
+msgid "[The PostgresSQL dashboard](https://grafana.com/grafana/dashboards/9628) (generic postgres dashboard)"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rageshake.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rageshake.po
new file mode 100644
index 000000000..c2afab62c
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rageshake.po
@@ -0,0 +1,105 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-rageshake.md:1
+msgid "Setting up the rageshake bug report server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:3
+msgid "The playbook can install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:5
+msgid "This is useful if you're developing your own applications and would like to collect bug reports for them."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:9
+msgid "To enable rageshake, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:15
+msgid "rageshake has various options which don't have dedicated Ansible variables. You can see the full list of options in the [`rageshake.sample.yaml` file](https://github.com/matrix-org/rageshake/blob/master/rageshake.sample.yaml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:17
+msgid "To set these, you can make use of the  `matrix_rageshake_configuration_extension_yaml` variable like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:27
+msgid "Adjusting the rageshake URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:29
+msgid "By default, this playbook installs rageshake on the `rageshake.` subdomain (`rageshake.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:31
+msgid "By tweaking the `matrix_rageshake_hostname` and `matrix_rageshake_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-rageshake.md:33
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:44
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:46
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the rageshake domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:48
+msgid "By default, you will need to create a CNAME record for `rageshake`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:50
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:52
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:54
+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-rageshake.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-rageshake.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-rageshake.md:65
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:67
+msgid "Refer to the [rageshake documentation](https://github.com/matrix-org/rageshake) for available APIs, etc."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rest-auth.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rest-auth.po
new file mode 100644
index 000000000..770a8ef1c
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-rest-auth.po
@@ -0,0 +1,65 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-rest-auth.md:1
+msgid "Setting up the REST authentication password provider module (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:3
+msgid "The playbook can install and configure [matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:5
+msgid "See the project's [documentation](https://github.com/ma1uta/matrix-synapse-rest-password-provider/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:9
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:19
+msgid "Authenticating only using a password provider"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:21
+msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:27
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:29
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:36
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:38
+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 ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-riot-web.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-riot-web.po
new file mode 100644
index 000000000..6af9a9d9d
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-riot-web.po
@@ -0,0 +1,93 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-riot-web.md:1
+msgid "Configuring Riot-web (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:3
+msgid "By default, this playbook **used to install** the [Riot-web](https://github.com/element-hq/riot-web) Matrix client web application."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:5
+msgid "Riot has since been [renamed to Element](https://element.io/blog/welcome-to-element/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:7
+msgid "to learn more about Element Web and its configuration, see our dedicated [Configuring Element Web](configuring-playbook-client-element-web.md) documentation page"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:8
+msgid "to learn how to migrate from Riot to Element Web, see [Migrating to Element Web](#migrating-to-element-web) below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:10
+msgid "Migrating to Element Web"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:12
+msgid "Migrating your custom settings"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:14
+msgid "If you have custom `matrix_riot_web_` variables in your `inventory/host_vars/matrix.example.com/vars.yml` file, you'll need to rename them (`matrix_riot_web_` -> `matrix_client_element_`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:16
+msgid "Some other playbook variables (but not all) with `riot` in their name are also renamed. The playbook checks and warns if you are using the old name for some commonly used ones."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:18
+msgid "Domain migration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:20
+msgid "We used to set up Riot at the `riot.example.com` domain. The playbook now sets up Element Web at `element.example.com` by default."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:22
+msgid "There are a few options for handling this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:24
+msgid "(**avoiding changes** - using the old `riot.example.com` domain and avoiding DNS changes) -- to keep using `riot.example.com` instead of `element.example.com`, override the domain at which the playbook serves Element Web: `matrix_server_fqn_element: \"riot.{{ matrix_domain }}\"`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:26
+msgid "(**embracing changes** - using only `element.example.com`) - set up the `element.example.com` DNS record (see [Configuring DNS](configuring-dns.md)). You can drop the `riot.example.com` in this case."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:28
+msgid "Re-running the playbook"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:30
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:37
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:39
+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 ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po
new file mode 100644
index 000000000..17fd21dbe
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3-goofys.po
@@ -0,0 +1,182 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:1
+msgid "Storing Matrix media files on Amazon S3 with Goofys (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:3
+msgid "If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service), you can let this playbook configure [Goofys](https://github.com/kahing/goofys) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:5
+msgid "Another (and better performing) way to use S3 storage with Synapse is [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:7
+msgid "Using a Goofys-backed media store works, but performance may not be ideal. If possible, try to use a region which is close to your Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:9
+msgid "If you'd like to move your locally-stored media store data to Amazon S3 (or another S3-compatible object store), we also provide some migration instructions below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:13
+msgid "After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:23
+msgid "You can use any S3-compatible object store by **additionally** configuring these variables:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:30
+msgid "If you have local media store files and wish to migrate to Backblaze B2 subsequently, follow our [migration guide to Backblaze B2](#migrating-to-backblaze-b2) below instead of applying this configuration as-is."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:32
+msgid "Migrating from local filesystem storage to S3"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:34
+msgid "It's a good idea to [make a complete server backup](faq.md#how-do-i-back-up-the-data-on-my-server) before migrating your local media store to an S3-backed one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:36
+msgid "After making the backup, follow one of the guides below for a migration path from a locally-stored media store to one stored on S3-compatible storage:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:38
+msgid "[Migrating to any S3-compatible storage (universal, but likely slow)](#migrating-to-any-s3-compatible-storage-universal-but-likely-slow)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:39
+msgid "[Migrating to Backblaze B2](#migrating-to-backblaze-b2)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:41
+msgid "Migrating to any S3-compatible storage (universal, but likely slow)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:43
+msgid "Proceed with the steps below without stopping Matrix services"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:45
+msgid "Start by adding the base S3 configuration in your `vars.yml` file (seen above, may be different depending on the S3 provider of your choice)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:47
+msgid "In addition to the base configuration you see above, add this to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:53
+msgid "This enables S3 support, but mounts the S3 storage bucket to `/matrix/s3-media-store` without hooking it to your homeserver yet. Your homeserver will still continue using your local filesystem for its media store."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:55
+msgid "Run the playbook to apply the changes: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:57
+msgid "Do an **initial sync of your files** by running this **on the server** (it may take a very long time):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:63
+msgid "You may need to install `rsync` manually."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:65
+#: ../../../docs/configuring-playbook-s3-goofys.md:106
+msgid "Stop all Matrix services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:67
+msgid "Start the S3 service by running this **on the server**: `systemctl start matrix-goofys`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:69
+msgid "Sync the files again by re-running the `rsync` command you see in step #5"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:71
+msgid "Stop the S3 service by running this **on the server**: `systemctl stop matrix-goofys`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:73
+#: ../../../docs/configuring-playbook-s3-goofys.md:114
+msgid "Get the old media store out of the way by running this command on the server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:79
+msgid "Remove the `matrix_s3_media_store_path` configuration from your `vars.yml` file (undoing step #3 above)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:81
+#: ../../../docs/configuring-playbook-s3-goofys.md:122
+msgid "Run the playbook: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:83
+#: ../../../docs/configuring-playbook-s3-goofys.md:124
+msgid "You're done! Verify that loading existing (old) media files works and that you can upload new ones."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:85
+#: ../../../docs/configuring-playbook-s3-goofys.md:126
+msgid "When confident that it all works, get rid of the local media store directory: `rm -rf /matrix/synapse/storage/media-store-local-backup`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:87
+msgid "Migrating to Backblaze B2"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:89
+msgid "While all Matrix services are running, run the following command on the server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:91
+msgid "(you need to adjust the 3 `--env` line below with your own data)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:104
+msgid "This is some initial file sync, which may take a very long time."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:108
+msgid "Run the command from step #1 again."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:110
+msgid "Doing this will sync any new files that may have been created locally in the meantime."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:112
+msgid "Now that Matrix services aren't running, we're sure to get Backblaze B2 and your local media store fully in sync."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:120
+msgid "Put the [Backblaze B2 settings](configuring-playbook-s3.md#backblaze-b2) in your `vars.yml` file"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3.po
new file mode 100644
index 000000000..442e2d3c8
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-s3.po
@@ -0,0 +1,217 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-s3.md:1
+msgid "Storing Synapse media files on Amazon S3 or another compatible Object Storage (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:3
+msgid "By default, this playbook configures your server to store Synapse's content repository (`media_store`) files on the local filesystem. If that's okay, you can skip this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:5
+msgid "As an alternative to storing media files on the local filesystem, you can store them on [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object store."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:7
+msgid "You can do this either by sticking to Synapse's media repository and making that use S3 (read below for this method), or by switching to an external media storage implementation like [matrix-media-repo](configuring-playbook-matrix-media-repo.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:9
+msgid "First, [choose an Object Storage provider](#choosing-an-object-storage-provider)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:11
+msgid "Then, [create the S3 bucket](#bucket-creation-and-security-configuration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:13
+msgid "Finally, [set up S3 storage for Synapse](#setting-up) (with [Goofys](configuring-playbook-s3-goofys.md), [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md), or use s3 datastore with the [matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/configuration/s3-datastore.html))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:15
+msgid "Choosing an Object Storage provider"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:17
+msgid "You can create [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object storage like [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html), [Storj](https://storj.io), [Wasabi](https://wasabi.com), [Digital Ocean Spaces](https://www.digitalocean.com/products/spaces), etc."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:19
+msgid "Amazon S3, Backblaze B2, and Storj are pay-as-you with no minimum charges for storing too little data."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:21
+msgid "All these providers have different prices, with Storj appearing to be the cheapest (as of 2024-10, storage fee is $0.004 per GB/month, and egress fee is $0.007 per GB). Backblaze egress is free, but for only certain users for up to 3x the amount of data stored. Beyond that you will pay $0.01/GB of egress."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:23
+msgid "Wasabi has a minimum charge of 1TB if you're storing less than 1TB, which becomes expensive if you need to store less data than that. Likewise, Digital Ocean Spaces has also a minimum charge of 250GB ($5/month as of 2022-10)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:25
+msgid "Here are some of the important aspects of choosing the right provider:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:27
+msgid "if a provider is a company you like and trust (or dislike less than the others)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:28
+msgid "if a provider implements end-to-end encryption of your data"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:29
+msgid "if a provider has a data region close to your Matrix server (if it's farther away, high latency may cause slowdowns)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:30
+msgid "if a provider's infrastructure such as data center is centralized or distributed"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:31
+msgid "if a provider's price model is transparent (whether it includes hidden costs like minimum charge, minimum storage term, etc.)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:32
+msgid "if a provider has free or cheap egress fee (in case you need to get the data out often, for some reason) - likely not too important for the common use-case"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:34
+msgid "Bucket creation and Security Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:36
+msgid "Now that you've [chosen an Object Storage provider](#choosing-an-object-storage-provider), you need to create a storage bucket."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:38
+msgid "How you do this varies from provider to provider, with Amazon S3 being the most complicated due to its vast number of services and complicated security policies."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:40
+msgid "Below, we provider some guides for common providers. If you don't see yours, look at the others for inspiration or read some guides online about how to create a bucket. Feel free to contribute to this documentation with an update!"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:42
+msgid "Amazon S3"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:44
+msgid "You'll need an Amazon S3 bucket and some IAM user credentials (access key + secret key) with full write access to the bucket. Example IAM security policy:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:65
+msgid "**Note**: This policy needs to be attached to an IAM user created from the **Security Credentials** menu. This is not a **Bucket Policy**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:67
+msgid "Backblaze B2"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:69
+msgid "To use [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html) you first need to sign up."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:71
+msgid "You [can't easily change which region (US, Europe) your Backblaze account stores files in](https://old.reddit.com/r/backblaze/comments/hi1v90/make_the_choice_for_the_b2_data_center_region/), so make sure to carefully choose the region when signing up (hint: it's a hard to see dropdown below the username/password fields in the signup form)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:73
+msgid "After logging in to Backblaze:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:75
+msgid "create a new **private** bucket through its user interface (you can call it something like `matrix-example-media-store`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:76
+msgid "note the **Endpoint** for your bucket (something like `s3.us-west-002.backblazeb2.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:77
+msgid "adjust its Lifecycle Rules to: Keep only the last version of the file"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:78
+msgid "go to [App Keys](https://secure.backblaze.com/app_keys.htm) and use the **Add a New Application Key** to create a new one"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:79
+msgid "restrict it to the previously created bucket (e.g. `matrix-example-media-store`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:80
+msgid "give it *Read & Write* access"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:82
+msgid "The `keyID` value is your **Access Key** and `applicationKey` is your **Secret Key**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:84
+msgid "For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3-synapse-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) you will need:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:86
+msgid "**Endpoint URL** - this is the  **Endpoint** value you saw above, but prefixed with `https://`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:88
+msgid "**Region** - use the value you see in the Endpoint (e.g. `us-west-002`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:90
+msgid "**Storage Class** - use `STANDARD`. Backblaze B2 does not have different storage classes, so it doesn't make sense to use any other value."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:92
+msgid "Other providers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:94
+msgid "For other S3-compatible providers, you may not need to configure security policies, etc. (just like for [Backblaze B2](#backblaze-b2))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:96
+msgid "You most likely just need to create an S3 bucket and get some credentials (access key and secret key) for accessing the bucket in a read/write manner."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:98
+msgid "Setting up"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:100
+msgid "To set up Synapse to store files in S3, follow the instructions for the method of your choice:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:102
+msgid "using [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) (recommended)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:103
+msgid "using [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:104
+msgid "using [matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po
new file mode 100644
index 000000000..05095e33e
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-shared-secret-auth.po
@@ -0,0 +1,65 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:1
+msgid "Setting up the Shared Secret Auth password provider module (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:3
+msgid "The playbook can install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:5
+msgid "See the project's [documentation](https://github.com/devture/matrix-synapse-shared-secret-auth/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:9
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:18
+msgid "Authenticating only using a password provider"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:20
+msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:26
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:28
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:35
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:37
+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 ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po
new file mode 100644
index 000000000..4cefcae41
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sliding-sync-proxy.po
@@ -0,0 +1,117 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:1
+msgid "Setting up the Sliding Sync proxy (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:3
+msgid "**Note**: The sliding-sync proxy is **not required** anymore as it's been replaced with a different method (called Simplified Sliding Sync) which is integrated into newer homeservers by default (**Conduit** homeserver from version `0.6.0` or **Synapse** from version `1.114`). This component and documentation remain here for historical purposes, but **installing this old sliding-sync proxy is generally not recommended anymore**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:5
+msgid "The playbook can install and configure [sliding-sync](https://github.com/matrix-org/sliding-sync) proxy for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:7
+msgid "Sliding Sync is an implementation of [MSC3575](https://github.com/matrix-org/matrix-spec-proposals/blob/kegan/sync-v3/proposals/3575-sync.md) and a prerequisite for running Element X clients ([Element X iOS](https://github.com/element-hq/element-x-ios) and [Element X Android](https://github.com/element-hq/element-x-android)). See the project's [documentation](https://github.com/matrix-org/sliding-sync) to learn more."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:11
+msgid "To enable Sliding Sync proxy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:17
+msgid "Adjusting the Sliding Sync proxy URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:19
+msgid "By default, this playbook installs the Sliding Sync proxy on the `matrix.` subdomain, at the `/sliding-sync` path (https://matrix.example.com/sliding-sync). 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-sliding-sync-proxy.md:21
+msgid "By tweaking the `matrix_sliding_sync_hostname` and `matrix_sliding_sync_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-sliding-sync-proxy.md:23
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:31
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:33
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Honoroit domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:35
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:37
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:39
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:41
+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-sliding-sync-proxy.md:48
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:50
+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-sliding-sync-proxy.md:52
+msgid "External databases"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:54
+msgid "Please note that, if your setup utilizes an external database, you must also establish configuration for the sliding sync proxy. Alter the defaults below to suit your configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:64
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:66
+msgid "You **don't need to do anything special** to make use of the Sliding Sync proxy. Simply open your client which supports Sliding Sync (like Element X) and log in."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:68
+msgid "When the Sliding Sync proxy is [installed](#installing), your `/.well-known/matrix/client` file is also updated. A new `org.matrix.msc3575.proxy` section and `url` property are added there and made to point to your Sliding Sync proxy's base URL (e.g. `https://matrix.example.com/sliding-sync`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:70
+msgid "This allows clients which support Sliding Sync to detect the Sliding Sync proxy's URL and make use of it."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po
new file mode 100644
index 000000000..65363b1cf
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ssl-certificates.po
@@ -0,0 +1,122 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:1
+msgid "Adjusting SSL certificate retrieval (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:3
+msgid "By default, this playbook retrieves and auto-renews free SSL certificates from [Let's Encrypt](https://letsencrypt.org/) for the domains it needs (e.g. `matrix.example.com` and others)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:5
+msgid "This guide is about using the integrated Traefik server and doesn't apply if you're using [your own webserver](configuring-playbook-own-webserver.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:7
+msgid "Using staging Let's Encrypt certificates instead of real ones"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:9
+msgid "For testing purposes, you may wish to use staging certificates provide by Let's Encrypt."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:11
+#: ../../../docs/configuring-playbook-ssl-certificates.md:21
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:17
+msgid "Disabling SSL termination"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:19
+msgid "For testing or other purposes, you may wish to install services without SSL termination and have services exposed to `http://` instead of `https://`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:27
+msgid "Using self-signed SSL certificates"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:29
+msgid "If you'd like to use your own SSL certificates, instead of the default (SSL certificates obtained automatically via [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) from [Let's Encrypt](https://letsencrypt.org/)):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:31
+msgid "generate your self-signed certificate files"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:32
+msgid "follow the [Using your own SSL certificates](#using-your-own-ssl-certificates) documentation below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:34
+msgid "Using your own SSL certificates"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:36
+msgid "To use your own SSL certificates with Traefik, you need to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:38
+msgid "disable [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) / [Let's Encrypt](https://letsencrypt.org/) support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:39
+msgid "put a custom Traefik configuration file on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:40
+msgid "register your custom configuration file with Traefik, by adding an extra provider of type [file](https://doc.traefik.io/traefik/providers/file/)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:41
+msgid "put the SSL files on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:89
+msgid "Using a DNS-01 ACME challenge type, instead of HTTP-01"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:91
+msgid "You can configure Traefik to use the [DNS-01 challenge type](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) for Let's Encrypt. This is less commonly used than the default [HTTP-01 challenge type](https://letsencrypt.org/docs/challenge-types/#http-01-challenge), but it can be helpful to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:93
+msgid "hide your public IP from Let's Encrypt logs"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:94
+msgid "allow you to obtain SSL certificates for servers which are not accessible (via HTTP) from the public internet (and for which the HTTP-01 challenge would fail)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:96
+msgid "This is an example for how to edit the `vars.yml` file if you're using Cloudflare:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:111
+msgid "Make sure to change the value of \"provider\" to your particular DNS solution, and provide the appropriate environment variables. The full list of supported providers is available [here](https://doc.traefik.io/traefik/https/acme/#providers)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:113
+msgid "This example assumes you're using Cloudflare to manage your DNS zone. Note that it requires the use of two tokens: one for reading all zones (`CF_ZONE_API_TOKEN`) and another that must be able to edit the particular domain you're using (`CF_DNS_API_TOKEN`). For security, it's recommended that you create two fine-grained tokens for this purpose, but you might choose to use the same token for both."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sygnal.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sygnal.po
new file mode 100644
index 000000000..06a8925bd
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-sygnal.po
@@ -0,0 +1,133 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-sygnal.md:1
+msgid "Setting up the Sygnal push gateway (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:3
+msgid "The playbook can install and configure the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:5
+msgid "See the project's [documentation](https://github.com/matrix-org/sygnal/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:7
+msgid "**Note**: most people don't need to install their own gateway. As Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) documentation says:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:9
+msgid "It is not feasible to allow end-users to configure their own Sygnal instance, because the Sygnal instance needs the appropriate FCM or APNs secrets that belong to the application."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:11
+msgid "This optional playbook component is only useful to people who develop/build their own Matrix client applications themselves."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:15
+msgid "To enable Sygnal, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:43
+msgid "For a more complete example of available fields and values they can take, see `roles/custom/matrix-sygnal/templates/sygnal.yaml.j2` (or the [upstream `sygnal.yaml.sample` configuration file](https://github.com/matrix-org/sygnal/blob/master/sygnal.yaml.sample))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:45
+msgid "Configuring [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/) is easier, as it only requires that you provide some config values."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:47
+msgid "To configure [APNS](https://developer.apple.com/notifications/) (Apple Push Notification Service), you'd need to provide one or more certificate files. To do that, the above example configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:49
+msgid "makes use of the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) (and its `aux_file_definitions` variable) to make the playbook install files into `/matrix/sygnal/data` (the `matrix_sygnal_data_path` variable). See [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml) of the `aux` role for usage examples. It also makes sure the files are owned by `matrix:matrix`, so that Sygnal can read them. Of course, you can also install these files manually yourself, if you'd rather not use `aux`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:51
+msgid "references these files in the Sygnal configuration (`matrix_sygnal_apps`) using a path like `/data/..` (the `/matrix/sygnal/data` directory on the host system is mounted into the `/data` directory inside the container)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:53
+msgid "Adjusting the Sygnal URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:55
+msgid "By default, this playbook installs Sygnal on the `sygnal.` subdomain (`sygnal.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:57
+msgid "By tweaking the `matrix_sygnal_hostname` and `matrix_sygnal_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-sygnal.md:59
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:70
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:72
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Sygnal domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:74
+msgid "By default, you will need to create a CNAME record for `sygnal`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:76
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:78
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:80
+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-sygnal.md:87
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:89
+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-sygnal.md:91
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:93
+msgid "To make use of your Sygnal installation, you'd need to build your own Matrix client application, which uses the same API keys (for [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/)) and certificates (for [APNS](https://developer.apple.com/notifications/)) and is to your Sygnal URL endpoint (e.g. `https://sygnal.example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:95
+msgid "Refer to Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) document."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po
new file mode 100644
index 000000000..4d5ddd2c4
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-admin.po
@@ -0,0 +1,125 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:1
+msgid "Setting up Synapse Admin (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:3
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:5
+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://matrix-org.github.io/dendrite/administration/adminapi) differs from [Synapse Admin API](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:7
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:11
+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:17
+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:19
+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:20
+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:22
+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:24
+msgid "⚠️ **Warning**: If you're using [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS) for authentication, you will be able to [log into synapse-admin with an access token](https://github.com/etkecc/synapse-admin/pull/58), but certain synapse-admin features (especially those around user management) will be limited or not work at all."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:26
+msgid "Adjusting the Synapse Admin URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:28
+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:30
+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:32
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:40
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:42
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Synapse Admin domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:44
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:46
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:48
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:50
+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:57
+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:59
+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:61
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:63
+msgid "After installation, Synapse Admin will be accessible at: `https://matrix.example.com/synapse-admin/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:65
+msgid "To use Synapse Admin, you need to have [registered at least one administrator account](registering-users.md) on your server."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po
new file mode 100644
index 000000000..e239aed5b
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-accept-invite.po
@@ -0,0 +1,73 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:1
+msgid "Setting up Synapse Auto Invite Accept (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:3
+msgid "The playbook can install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:5
+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:7
+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:9
+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:11
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:13
+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:21
+msgid "Synapse worker deployments"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:23
+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:29
+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:31
+msgid "Native alternative"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:33
+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:35
+msgid "Here's example configuration for using the **native** Synapse feature:"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po
new file mode 100644
index 000000000..6708ae642
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-auto-compressor.po
@@ -0,0 +1,77 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:1
+msgid "Setting up synapse-auto-compressor (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:3
+msgid "The playbook can install and configure [synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:5
+msgid "It's a CLI tool that automatically compresses Synapse's `state_groups` database table in the background."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:7
+msgid "See the project's [documentation](https://github.com/matrix-org/rust-synapse-compress-state/blob/master/README.md#automated-tool-synapse_auto_compressor) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:11
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:17
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:19
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:26
+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-auto-compressor.md:28
+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-auto-compressor.md:30
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:32
+msgid "After installation, `synapse_auto_compressor` will run automatically every day at `00:00:00` (as defined in `matrix_synapse_auto_compressor_calendar` by default)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:34
+msgid "Manually start the tool"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:36
+msgid "For testing your setup it can be helpful to not wait until 00:00. If you want to run the tool immediately, log onto the server and run `systemctl start matrix-synapse-auto-compressor`. Running this command will not return control to your terminal until the compression run is done, which may take a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po
new file mode 100644
index 000000000..f31fa54e9
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-s3-storage-provider.po
@@ -0,0 +1,257 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:1
+msgid "Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:3
+msgid "If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service), you can use the [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) media provider module for Synapse."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:5
+msgid "An alternative (which has worse performance) is to use [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:7
+msgid "How it works?"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:9
+msgid "Summarized writings here are inspired by [this article](https://quentin.dufour.io/blog/2021-09-14/matrix-synapse-s3-storage/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:11
+msgid "The way media storage providers in Synapse work has some caveats:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:13
+msgid "Synapse still continues to use locally-stored files (for creating thumbnails, serving files, etc)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:14
+msgid "the media storage provider is just an extra storage mechanism (in addition to the local filesystem)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:15
+msgid "all files are stored locally at first, and then copied to the media storage provider (either synchronously or asynchronously)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:16
+msgid "if a file is not available on the local filesystem, it's pulled from a media storage provider"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:18
+msgid "You may be thinking **if all files are stored locally as well, what's the point**?"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:20
+msgid "You can run some scripts to delete the local files once in a while (which we do automatically by default - see [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem)), thus freeing up local disk space. If these files are needed in the future (for serving them to users, etc.), Synapse will pull them from the media storage provider on demand."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:22
+msgid "While you will need some local disk space around, it's only to accommodate usage, etc., and won't grow as large as your S3 store."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:24
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:26
+msgid "After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), you can proceed to configure `s3-storage-provider` in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:50
+msgid "If you have existing files in Synapse's media repository (`/matrix/synapse/media-store/..`):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:52
+msgid "new files will start being stored both locally and on the S3 store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:53
+msgid "the existing files will remain on the local filesystem only until [migrating them to the S3 store](#migrating-your-existing-media-files-to-the-s3-store)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:54
+msgid "at some point (and periodically in the future), you can delete local files which have been uploaded to the S3 store already"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:56
+msgid "Regardless of whether you need to [Migrate your existing files to the S3 store](#migrating-your-existing-media-files-to-the-s3-store) or not, make sure you've familiarized yourself with [How it works?](#how-it-works) above and [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem) below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:58
+msgid "Migrating your existing media files to the S3 store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:60
+msgid "Migrating your existing data can happen in multiple ways:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:62
+msgid "[using the `s3_media_upload` script from `synapse-s3-storage-provider`](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (very slow when dealing with lots of data)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:63
+msgid "[using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload) (quicker when dealing with lots of data)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:65
+msgid "Using the `s3_media_upload` script from `synapse-s3-storage-provider`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:67
+msgid "Instead of using `s3_media_upload` directly, which is very slow and painful for an initial data migration, we recommend [using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:69
+msgid "To copy your existing files, SSH into the server and run `/matrix/synapse/ext/s3-storage-provider/bin/shell`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:71
+msgid "This launches a Synapse container, which has access to the local media store, Postgres database, S3 store and has some convenient environment variables configured for you to use (`MEDIA_PATH`, `BUCKET`, `ENDPOINT`, `UPDATE_DB_DAYS`, etc)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:73
+msgid "Then use the following commands (`$` values come from environment variables - they're **not placeholders** that you need to substitute):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:75
+msgid "`s3_media_upload update-db $UPDATE_DB_DURATION` - create a local SQLite database (`cache.db`) with a list of media repository files (from the `synapse` Postgres database) eligible for operating on"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:76
+msgid "`$UPDATE_DB_DURATION` is influenced by the `matrix_synapse_ext_synapse_s3_storage_provider_update_db_day_count` variable (defaults to `0`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:77
+msgid "`$UPDATE_DB_DURATION` defaults to `0d` (0 days), which means **include files which haven't been accessed for more than 0 days** (that is, **all files will be included**)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:78
+msgid "`s3_media_upload check-deleted $MEDIA_PATH` - check whether files in the local cache still exist in the local media repository directory"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:79
+msgid "`s3_media_upload upload $MEDIA_PATH $BUCKET --delete --storage-class $STORAGE_CLASS --endpoint-url $ENDPOINT` - uploads locally-stored files to S3 and deletes them from the local media repository directory"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:81
+msgid "The `s3_media_upload upload` command may take a lot of time to complete."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:83
+msgid "Instead of running the above commands manually in the shell, you can also run the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script which will run the same commands automatically. We demonstrate how to do it manually, because:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:85
+msgid "it's what the upstream project demonstrates and it teaches you how to use the `s3_media_upload` tool"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:86
+msgid "allows you to check and verify the output of each command, to catch mistakes"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:87
+msgid "includes progress bars and detailed output for each command"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:88
+msgid "allows you to easily interrupt slow-running commands, etc. (the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container without interactive TTY support, so `Ctrl+C` may not work and you and require killing via `docker kill ..`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:90
+msgid "Using another tool in combination with `s3_media_upload`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:92
+msgid "To migrate your existing local data to S3, we recommend to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:94
+msgid "**first** use another tool ([`aws s3`](#copying-data-to-amazon-s3) or [`b2 sync`](#copying-data-to-backblaze-b2), etc.) to copy the local files to the S3 bucket"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:96
+msgid "**only then** [use the `s3_media_upload` tool to finish the migration](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (this checks to ensure all files are uploaded and then deletes the local files)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:98
+msgid "Copying data to Amazon S3"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:100
+msgid "To copy to AWS S3, start a container on the Matrix server like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:112
+msgid "Copying data to an S3 alternative using the aws-s3 tool"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:114
+msgid "To copy to a provider other than AWS S3 (e.g. Wasabi, Digital Ocean Spaces, etc.), you can use the command for [Copying data to Amazon S3](#copying-data-to-amazon-s3) with an added `--endpoint-url=$ENDPOINT` argument."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:116
+msgid "Add this argument to the command **as-is** (`$ENDPOINT` is an environment variable corresponding to `matrix_synapse_ext_synapse_s3_storage_provider_config_endpoint_url`, so you don't need to touch it). Make sure to add the argument **before** the final quote (`'`) of the command."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:118
+msgid "Copying data to Backblaze B2"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:120
+msgid "You can copy files to Backblaze B2 either by following the [Copying data to an S3 alternative using the aws-s3 tool](#copying-data-to-an-s3-alternative-using-the-aws-s3-tool) or by using the B2-specific [b2 command-line tool](https://www.backblaze.com/b2/docs/quick_command_line.html) as described below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:122
+msgid "To copy the data using the `b2` tool, start a container on the Matrix server like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:136
+msgid "Periodically cleaning up the local filesystem"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:138
+msgid "As described in [How it works?](#how-it-works) above, when new media is uploaded to the Synapse homeserver, it's first stored locally and then also stored on the remote S3 storage."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:140
+msgid "By default, we periodically ensure that all local files are uploaded to S3 and are then removed from the local filesystem. This is done automatically using:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:142
+msgid "the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:143
+msgid ".. invoked via the `matrix-synapse-s3-storage-provider-migrate.service` service"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:144
+msgid ".. triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` timer, every day at 05:00"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:146
+msgid "So.. you don't need to perform any maintenance yourself."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po
new file mode 100644
index 000000000..32fbdb473
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-simple-antispam.po
@@ -0,0 +1,45 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 09:53+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:1
+msgid "Setting up Synapse Simple Antispam (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:3
+msgid "The playbook can install and configure [synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:5
+msgid "It lets you fight invite-spam by automatically blocking invitiations from a list of servers specified by you (blacklisting)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:7
+msgid "See the project's [documentation](https://github.com/t2bot/synapse-simple-antispam/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:11
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po
new file mode 100644
index 000000000..6e5ae6f1b
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse-usage-exporter.po
@@ -0,0 +1,109 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:1
+msgid "Enabling synapse-usage-exporter for Synapse usage statistics (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:3
+msgid "[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) allows you to export the usage statistics of a Synapse homeserver to this container service and for the collected metrics to later be scraped by Prometheus."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:5
+msgid "Synapse does not include usage statistics in its Prometheus metrics. They can be reported to an HTTP `PUT` endpoint 5 minutes after startup and from then on at a fixed interval of once every three hours. This role integrates a simple [Flask](https://flask.palletsprojects.com) project that offers an HTTP `PUT` endpoint and holds the most recent received record available to be scraped by Prometheus."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:7
+msgid "Enabling this service will automatically:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:9
+msgid "install the synapse-usage-exporter service"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:10
+msgid "re-configure Synapse to push (via HTTP `PUT`) usage statistics information to synapse-usage-exporter"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:11
+msgid "re-configure [Prometheus](./configuring-playbook-prometheus-grafana.md) (if Prometheus is enabled), to periodically scrape metrics from synapse-usage-exporter"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:12
+msgid "add a new [Grafana](./configuring-playbook-prometheus-grafana.md) dashboard (if Grafana is enabled) containing Synapse usage statistics"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:14
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:16
+msgid "To enable synapse-usage-exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:28
+msgid "Adjusting the synapse-usage-exporter URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:30
+msgid "By default, this playbook installs synapse-usage-exporter on the `matrix.` subdomain, at the `/report-usage-stats/push` path (https://matrix.example.com/report-usage-stats/push). 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-usage-exporter.md:32
+msgid "By tweaking the `matrix_synapse_usage_exporter_hostname` and `matrix_synapse_usage_exporter_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-usage-exporter.md:34
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:43
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:45
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the synapse-usage-exporter domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:47
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:49
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:51
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:53
+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-usage-exporter.md:60
+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-usage-exporter.md:62
+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 ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse.po
new file mode 100644
index 000000000..60b44510c
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse.po
@@ -0,0 +1,258 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-synapse.md:1
+msgid "Configuring Synapse (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:3
+msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, so that it works for the general case. If that's okay, you can skip this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:5
+msgid "The playbook provides lots of customization variables you could use to change Synapse's settings."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:7
+msgid "Their defaults are defined in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml) and they ultimately end up in the generated `/matrix/synapse/config/homeserver.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2`](../roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2) template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:9
+msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:11
+msgid "Alternatively, **if there is no pre-defined variable** for a Synapse setting you wish to change:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:13
+msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Synapse's various settings that rarely get used."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:15
+msgid "or, you can **extend and override the default configuration** ([`homeserver.yaml.j2`](../roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2)) by making use of the `matrix_synapse_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:17
+msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`). You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:19
+msgid "Load balancing with workers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:21
+msgid "To have Synapse gracefully handle thousands of users, worker support should be enabled. It factors out some homeserver tasks and spreads the load of incoming client and server-to-server traffic between multiple processes. More information can be found in the [official Synapse workers documentation](https://github.com/element-hq/synapse/blob/master/docs/workers.md) and [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:23
+msgid "To enable Synapse worker support, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:31
+msgid "By default, this enables the `one-of-each` [worker preset](#worker-presets), but you may wish to use another preset or [control the number of worker instances](#controlling-the-number-of-worker-instances)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:33
+msgid "Worker presets"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:35
+msgid "We support a few configuration presets (`matrix_synapse_workers_preset: one-of-each` being the default configuration right now):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:37
+msgid "(federation-only) `little-federation-helper` - a very minimal worker configuration to improve federation performance"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:38
+msgid "(generic) `one-of-each` - defaults to one worker of each supported type - no smart routing, just generic workers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:39
+msgid "(specialized) `specialized-workers` - defaults to one worker of each supported type, but disables generic workers and uses [specialized workers](#specialized-workers) instead"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:41
+msgid "These presets represent a few common configurations. There are many worker types which can be mixed and matched based on your needs."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:43
+msgid "Generic workers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:45
+msgid "Previously, the playbook only supported the most basic type of load-balancing. We call it **generic load-balancing** below, because incoming HTTP requests are sent to a generic worker. Load-balancing was done based on the requestor's IP address. This is simple, but not necessarily optimal. If you're accessing your account from multiple IP addresses (e.g. your mobile phone being on a different network than your PC), these separate requests may potentially be routed to different workers, each of which would need to cache roughly the same data."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:47
+msgid "This is **still the default load-balancing method (preset) used by the playbook**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:49
+msgid "To use generic load-balancing, do not specify `matrix_synapse_workers_preset` to make it use the default value (`one-of-each`), or better yet - explicitly set it as `one-of-each`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:51
+msgid "You may also consider [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:53
+msgid "Specialized workers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:55
+msgid "The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requestor's IP adddress, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** - the access token (username) of the requestor and/or on the resource (room, etc.) being requested."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:57
+msgid "The playbook supports these **4 types** of specialized workers:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:59
+msgid "Room workers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) & [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs dedicated to handling specific rooms"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:60
+msgid "Sync workers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to synchronization (most notably [the `/sync` endpoint](https://spec.matrix.org/v1.9/client-server-api/#get_matrixclientv3sync))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:61
+msgid "Client readers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are not for specific rooms (handled by **room workers**) or for synchronization (handled by **sync workers**)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:62
+msgid "Federation readers - handles various [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which are not for specific rooms (handled by **room workers**)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:64
+msgid "To use specialized load-balancing, consider enabling the `specialized-workers` [worker preset](#worker-presets) and potentially [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:66
+msgid "Controlling the number of worker instances"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:68
+msgid "If you'd like more customization power, you can start with one of the [worker presets](#worker-presets) and then tweak various `matrix_synapse_workers_*_count` variables manually."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:70
+msgid "To find what variables are available for you to override in your own `vars.yml` configuration file, see the [`defaults/main.yml` file for the `matrix-synapse` Ansible role](../roles/custom/matrix-synapse/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:72
+msgid "The only thing you **cannot** do is mix [generic workers](#generic-workers) and [specialized workers](#specialized-workers)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:74
+msgid "Effect of enabling workers on the rest of your server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:76
+msgid "When Synapse workers are enabled, the integrated [Postgres database is tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum number of Postgres connections are increased from `200` to `500`. If you need to decrease or increase the number of maximum Postgres connections further, use the `postgres_max_connections` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:78
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:80
+msgid "In case any problems occur, make sure to have a look at the [list of synapse issues about workers](https://github.com/element-hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit 'matrix-*'`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:82
+msgid "Synapse Admin"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:84
+msgid "Certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace, if you install [Synapse Admin](configuring-playbook-synapse-admin.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:86
+msgid "Synapse + OpenID Connect for Single-Sign-On"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:88
+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:90
+msgid "If you'd like to use OpenID Connect authentication with Synapse, you'll need some additional configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:92
+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:94
+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:96
+#, python-format
+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:117
+msgid "Customizing templates"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:119
+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:121
+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:123
+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:125
+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:127
+msgid "To enable template customizations, use a configuration (`inventory/host_vars/matrix.example.com/vars.yml`) like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:153
+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:155
+msgid "Monitoring Synapse Metrics with Prometheus and Grafana"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:157
+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:159
+msgid "To enable Synapse runtime metrics see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:161
+msgid "To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-telemetry.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-telemetry.po
new file mode 100644
index 000000000..9c093c4dc
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-telemetry.po
@@ -0,0 +1,53 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-telemetry.md:1
+msgid "Enabling Telemetry for your Matrix server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:3
+msgid "By default, this playbook configures your Matrix homeserver to not send any telemetry data anywhere."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:5
+msgid "The [matrix.org](https://matrix.org) team would really appreciate it if you could help the project out by reporting usage statistics from your homeserver. Enabling usage statistics helps track the growth of the Matrix community, and helps to make Matrix a success."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:7
+msgid "Enabling Telemetry"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:9
+msgid "If you'd like to **help by enabling submission of general usage statistics** for your homeserver, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:17
+msgid "Usage statistics being submitted"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:19
+msgid "When enabled, your homeserver will regularly upload a few dozen statistics about your server. This data includes your homeserver's domain, the total number of users, the number of active users, the total number of rooms, and the number of messages sent per day on your homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:21
+msgid "See [Synapse's documentation](https://github.com/element-hq/synapse/blob/develop/docs/usage/administration/monitoring/reporting_homeserver_usage_statistics.md#available-statistics) or [Dendrite's documentation](https://github.com/matrix-org/dendrite/blob/main/docs/FAQ.md#what-is-being-reported-when-enabling-phone-home-statistics) for the full list of statistics that are reported."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-traefik.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-traefik.po
new file mode 100644
index 000000000..1de2b54a4
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-traefik.po
@@ -0,0 +1,138 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-traefik.md:1
+msgid "Configuring the Traefik reverse-proxy (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:3
+msgid "By default, this playbook installs and manages a [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered by the [ansible-role-traefik](https://github.com/mother-of-all-self-hosting/ansible-role-traefik) Ansible role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:5
+msgid "This Ansible role support various configuration options. Feel free to consult its `default/main.yml` variables file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:7
+msgid "Adjusting SSL certificate retrieval"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:9
+msgid "See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:11
+msgid "Increase logging verbosity"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:17
+msgid "Disable access logs"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:19
+msgid "This will disable access logging."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:25
+msgid "Enable Traefik Dashboard"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:27
+msgid "This will enable a Traefik [Dashboard](https://doc.traefik.io/traefik/operations/dashboard/) UI at `https://matrix.example.com/dashboard/` (note the trailing `/`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:37
+msgid "**WARNING**: Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:39
+msgid "Additional configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:41
+msgid "Use the `traefik_configuration_extension_yaml` variable provided by the Traefik Ansible role to override or inject additional settings, even when no dedicated variable exists."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:51
+msgid "Reverse-proxying another service behind Traefik"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:53
+msgid "The preferred way to reverse-proxy additional services behind Traefik would be to start the service as another container, configure the container with the corresponding Traefik [container labels](https://docs.docker.com/config/labels-custom-metadata/) (see [Traefik & Docker](https://doc.traefik.io/traefik/routing/providers/docker/)), and connect the service to the `traefik` network. Some services are also already available via the compatible [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook), but take a look at the minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:55
+msgid "However, if your service does not run on a container or runs on another machine, the following configuration might be what you are looking for."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:57
+msgid "Reverse-proxying a remote HTTP/HTTPS service behind Traefik"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:59
+msgid "If you want to host another webserver would be reachable via `my-fancy-website.example.net` from the internet and via `https://<internal webserver IP address>:<internal port>` from inside your network, you can make the playbook's integrated Traefik instance reverse-proxy the traffic to the correct host."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:61
+msgid "Prerequisites: DNS and routing for the domain `my-fancy-website.example.net` need to be set up correctly. In this case, you'd be pointing the domain name to your Matrix server - `my-fancy-website.example.net` would be a CNAME going to `matrix.example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:63
+msgid "First, we have to adjust the static configuration of Traefik, so that we can add additional configuration files:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:77
+msgid "If you are using a self-signed certificate on your webserver, you can tell Traefik to trust your own backend servers by adding more configuration to the static configuration file. If you do so, bear in mind the security implications of disabling the certificate validity checks towards your back end."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:91
+msgid "Next, you have to add a new dynamic configuration file for Traefik that contains the actual information of the server using the `aux_file_definitions` variable. In this example, we will terminate SSL at the Traefik instance and connect to the other server via HTTPS. Traefik will now take care of managing the certificates."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:110
+#: ../../../docs/configuring-playbook-traefik.md:133
+msgid "Changing the `url` to one with an `http://` prefix would allow to connect to the server via HTTP."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:112
+msgid "Reverse-proxying another service behind Traefik without terminating SSL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:114
+msgid "If you do not want to terminate SSL at the Traefik instance (for example, because you're already terminating SSL at other webserver), you need to adjust the static configuration in the same way as in the previous chapter in order to be able to add our own dynamic configuration files. Afterwards, you can add the following configuration to your `vars.yml` configuration file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:135
+msgid "With these changes, all TCP traffic will be reverse-proxied to the target system."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:137
+msgid "**WARNING**: This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:139
+msgid "Traefik behind a `proxy_protocol` reverse-proxy"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:141
+msgid "If you run a reverse-proxy which speaks `proxy_protocol`, add the following to your configuration file:"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-turn.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-turn.po
new file mode 100644
index 000000000..b8e523207
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-turn.po
@@ -0,0 +1,109 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-turn.md:1
+msgid "Adjusting TURN server configuration (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:3
+msgid "The playbook installs a [Coturn](https://github.com/coturn/coturn) TURN server by default, so that clients can make audio/video calls even from [NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed networks."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:5
+msgid "By default, the Synapse chat server is configured, so that it points to the Coturn TURN server installed by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:7
+msgid "Disabling Coturn"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:9
+msgid "If, for some reason, you'd like to prevent the playbook from installing Coturn, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:15
+msgid "In that case, Synapse would not point to any Coturn servers and audio/video call functionality may fail."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:17
+msgid "Manually defining your public IP"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:19
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:21
+msgid "If you'd rather use a local IP for `ansible_host`, make sure to set up `matrix_coturn_turn_external_ip_address` replacing `YOUR_PUBLIC_IP` with the pubic IP used by the server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:27
+msgid "If you'd like to rely on external IP address auto-detection (not recommended unless you need it), set `matrix_coturn_turn_external_ip_address` to an empty value. 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 `matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:29
+msgid "If your server has multiple external IP addresses, the Coturn role offers a different variable for specifying them:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:36
+msgid "Changing the authentication mechanism"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:38
+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:40
+msgid "To do so, add this override to your configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:46
+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:48
+msgid "If you're using [Jitsi](./configuring-playbook-jitsi.md), note that switching to `lt-cred-mech` will remove the integration between Jitsi and your own Coturn server, because Jitsi only seems to support the `auth-secret` authentication method."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:50
+msgid "Using your own external Coturn server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:52
+msgid "If you'd like to use another TURN server (be it Coturn or some other one), you can configure the playbook like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:66
+msgid "If you have or want to enable [Jitsi](configuring-playbook-jitsi.md), 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:72
+msgid "You can put multiple host/port combinations if you like."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:74
+msgid "Further variables and configuration options"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:75
+msgid "To see all the available configuration options, check roles/custom/matrix-coturn/defaults/main.yml"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po
new file mode 100644
index 000000000..55c520ed5
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-user-verification-service.po
@@ -0,0 +1,217 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:1
+msgid "Setting up Matrix User Verification Service (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:3
+msgid "**[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (hereafter: UVS) can only be installed after Matrix services are installed and running.** If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) flow and come back here later."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:5
+msgid "Currently, the main purpose of this role is to allow Jitsi to authenticate Matrix users and check if they are authorized to join a conference. Please refer to the documentation of the [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) to understand how it works."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:7
+msgid "**Note**: enabling Matrix User Verification Service, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:9
+msgid "If the Jitsi server is also configured by this playbook, all plugging of variables and secrets is handled in `group_vars/matrix_servers`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:11
+msgid "__Some general concepts of UVS may be helpful to understand the rest, so here they are:__"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:13
+msgid "UVS can be used to verify two claims:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:15
+msgid "(A) Whether a given OpenID token is valid for a given server and"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:16
+msgid "(B) whether a user is member of a given room and the corresponding PowerLevel"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:18
+msgid "Verifying an OpenID token ID done by finding the corresponding Homeserver via  '.well-known/matrix/server' for the given domain. The configured `matrix_user_verification_service_uvs_homeserver_url` does **not** factor into this. By default, this playbook only checks against `matrix_server_fqn_matrix`. Therefore, the request will be made against the public openid API for `matrix_server_fqn_matrix`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:20
+msgid "Verifying RoomMembership and PowerLevel is done against `matrix_user_verification_service_uvs_homeserver_url` which is by default done via the docker network. UVS will verify the validity of the token beforehand though."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:22
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:24
+msgid "In order to use UVS, an admin token for the configured homeserver must be supplied. For now this means configuring Synapse and creating the token before installing UVS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:26
+msgid "Enable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:28
+msgid "To enable Matrix User Verification Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:34
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:36
+msgid "The only required configuration variable is `matrix_user_verification_service_uvs_access_token` (see below)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:38
+msgid "For a list of all configuration options see the role defaults [`roles/matrix-user-verification-service/defaults/main.yml`](../roles/custom/matrix-user-verification-service/defaults/main.yml). But be aware of all the plugging happening in `group_vars/matrix_servers`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:40
+msgid "In the default configuration, the UVS Server is only reachable via the docker network, which is fine if e.g. Jitsi is also running in a container on the host. However, it is possible to expose UVS via setting `matrix_user_verification_service_container_http_host_bind_port`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:42
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:44
+msgid "The Synapse Access Token is used to verify RoomMembership and PowerLevel against `matrix_user_verification_service_uvs_homeserver_url`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:46
+msgid "We recommend that you create a dedicated Matrix user for uvs (`uvs` is a good username). Follow our [Registering users](registering-users.md) guide to register a user with administration privileges."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:48
+msgid "You are required to specify an access token (belonging to this new user) for UVS to work. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:50
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:56
+msgid "Custom Auth Token (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:58
+msgid "It is possible to set an API Auth Token to restrict access to the UVS. If this is enabled, anyone making a request to UVS must provide it via the header \"Authorization: Bearer TOKEN\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:60
+msgid "By default, the token will be derived from `matrix_homeserver_generic_secret_key` in `group_vars/matrix_servers`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:62
+msgid "To set your own Token, add the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:68
+msgid "In case Jitsi is also managed by this playbook and 'matrix' authentication in Jitsi is enabled, this collection will automatically configure Jitsi to use the configured auth token."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:70
+msgid "Disable Auth (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:72
+msgid "Authorization is enabled by default. To disable it, add the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:78
+msgid "Federation (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:80
+msgid "In theory (however currently untested), UVS can handle federation. To enable it, add the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:86
+msgid "This will instruct UVS to verify the OpenID token against any domain given in a request. Homeserver discovery is done via '.well-known/matrix/server' of the given domain."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:88
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:90
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:97
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service matrix-user-verification-service` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:99
+msgid "`just install-service matrix-user-verification-service` is useful for maintaining your setup quickly 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 `just setup-all` runs the `ensure-matrix-users-created` tag too."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:101
+msgid "Logging"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:103
+msgid "The configuration variable `UVS_LOG_LEVEL` can be set to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:104
+msgid "warning"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:105
+msgid "info"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:106
+msgid "debug"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:108
+msgid "TLS Certificate Checking"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:110
+msgid "If the Matrix Homeserver does not provide a valid TLS certificate, UVS will fail with the following error message:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:112
+msgid "message: 'No response received: [object Object]',"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:114
+msgid "This also applies to self-signed and let's encrypt staging certificates."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:116
+msgid "To disable certificate validation altogether (INSECURE! Not suitable for production use!) set: `NODE_TLS_REJECT_UNAUTHORIZED=0`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:118
+msgid "Alternatively, it is possible to inject your own CA certificates into the container by mounting a PEM file with additional trusted CAs into the container and pointing the `NODE_EXTRA_CA_CERTS` environment variable to it."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook.po
new file mode 100644
index 000000000..816d84ffc
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook.po
@@ -0,0 +1,533 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-playbook.md:1
+msgid "Configuring the playbook"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:3
+msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md)</sup>"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:5
+msgid "If you've configured your DNS records and retrieved the playbook's source code to your computer, you can start configuring the playbook. To do so, follow these steps inside the playbook directory:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:7
+msgid "create a directory to hold your configuration (`mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\")"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:9
+msgid "copy the sample configuration file (`cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:11
+msgid "edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You may also take a look at the various `roles/*/ROLE_NAME_HERE/defaults/main.yml` files and see if there's something you'd like to copy over and override in your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:13
+msgid "copy the sample inventory hosts file (`cp examples/hosts inventory/hosts`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:15
+msgid "edit the inventory hosts file (`inventory/hosts`) to your liking"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:17
+msgid "(optional, advanced) you may wish to keep your `inventory` directory under version control with [git](https://git-scm.com/) or any other version-control system."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:19
+msgid "(optional, advanced) to run Ansible against multiple servers with different `sudo` credentials, you can copy the sample inventory hosts yaml file for each of your hosts: (`cp examples/host.yml inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin/ansible-all-hosts.sh) script [in the installation step](installing.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:21
+msgid "For a basic Matrix installation, that's all you need."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:23
+msgid "For a more custom setup, see the [Other configuration options](#other-configuration-options) below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:25
+msgid "[▶️](installing.md) When you're done with all the configuration you'd like to do, continue with [Installing](installing.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:27
+msgid "Other configuration options"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:29
+msgid "Core service adjustments"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:31
+msgid "Homeserver configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:32
+msgid "[Configuring Synapse](configuring-playbook-synapse.md), if you're going with the default/recommended homeserver implementation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:34
+msgid "[Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:36
+msgid "[Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:38
+msgid "Server components:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:39
+msgid "[Using an external PostgreSQL server](configuring-playbook-external-postgres.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:41
+msgid "[Adjusting TURN server configuration](configuring-playbook-turn.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:43
+msgid "[Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:45
+msgid "[Using your own webserver, instead of this playbook's Traefik reverse-proxy](configuring-playbook-own-webserver.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:47
+msgid "[Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:49
+msgid "[Adjusting email-sending settings](configuring-playbook-email.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:51
+msgid "[Setting up ma1sd Identity Server](configuring-playbook-ma1sd.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:53
+msgid "[Setting up Dynamic DNS](configuring-playbook-dynamic-dns.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:55
+msgid "Server connectivity:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:56
+msgid "[Enabling Telemetry for your Matrix server](configuring-playbook-telemetry.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:58
+msgid "[Controlling Matrix federation](configuring-playbook-federation.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:60
+msgid "Clients"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:62
+msgid "Web clients for Matrix that you can host on your own domains."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:64
+msgid "[Configuring Element Web](configuring-playbook-client-element-web.md), if you're going with the default/recommended client"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:66
+msgid "[Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a lightweight Matrix client with legacy and mobile browser support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:68
+msgid "[Setting up Cinny](configuring-playbook-client-cinny.md), if you've enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing primarily on simple, elegant and secure interface"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:70
+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:72
+msgid "Authentication and user-related"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:74
+msgid "Extend and modify how users are authenticated on your homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:76
+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:78
+msgid "[Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:80
+msgid "[Setting up Synapse Admin](configuring-playbook-synapse-admin.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:82
+msgid "[Setting up matrix-registration](configuring-playbook-matrix-registration.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:84
+msgid "[Setting up the REST authentication password provider module](configuring-playbook-rest-auth.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:86
+msgid "[Setting up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:88
+msgid "[Setting up the LDAP authentication password provider module](configuring-playbook-ldap-auth.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:90
+msgid "[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:92
+msgid "[Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:94
+msgid "[Setting up Matrix User Verification Service](configuring-playbook-user-verification-service.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:96
+msgid "File Storage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:98
+msgid "Use alternative file storage to the default `media_store` folder."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:100
+msgid "[Storing Matrix media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:102
+msgid "[Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:104
+msgid "[Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:106
+msgid "Bridging other networks"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:108
+msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:110
+msgid "[Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:112
+msgid "[Setting up Mautrix Telegram bridging](configuring-playbook-bridge-mautrix-telegram.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:114
+msgid "[Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:116
+msgid "[Setting up Mautrix Google Messages bridging](configuring-playbook-bridge-mautrix-gmessages.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:118
+msgid "[Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-mautrix-whatsapp.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:120
+msgid "[Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:122
+msgid "[Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:124
+msgid "[Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-mautrix-googlechat.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:126
+msgid "[Setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:128
+msgid "[Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-signal.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:130
+msgid "[Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](configuring-playbook-bridge-mautrix-wsproxy.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:132
+msgid "[Setting up Appservice IRC bridging](configuring-playbook-bridge-appservice-irc.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:134
+msgid "[Setting up Appservice Discord bridging](configuring-playbook-bridge-appservice-discord.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:136
+msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:138
+msgid "[Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-appservice-kakaotalk.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:140
+msgid "[Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-linkedin.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:142
+msgid "[Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) - a bridge between Matrix and multiple project management services, such as [GitHub](https://github.com), [GitLab](https://about.gitlab.com) and [JIRA](https://www.atlassian.com/software/jira)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:144
+msgid "[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:146
+msgid "[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-puppet-instagram.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:148
+msgid "[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:150
+msgid "[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-puppet-discord.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:152
+msgid "[Setting up MX Puppet GroupMe bridging](configuring-playbook-bridge-mx-puppet-groupme.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:154
+msgid "[Setting up MX Puppet Steam bridging](configuring-playbook-bridge-mx-puppet-steam.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:156
+msgid "[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:158
+msgid "[Setting up Email2Matrix](configuring-playbook-email2matrix.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:160
+msgid "[Setting up Postmoogle email bridging](configuring-playbook-bridge-postmoogle.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:162
+msgid "[Setting up Matrix SMS bridging](configuring-playbook-bridge-matrix-bridge-sms.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:164
+msgid "[Setting up Heisenbridge bouncer-style IRC bridging](configuring-playbook-bridge-heisenbridge.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:166
+msgid "[Setting up WeChat bridging](configuring-playbook-bridge-wechat.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:168
+msgid "Bots"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:170
+msgid "Bots provide various additional functionality to your installation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:172
+msgid "[Setting up baibot](configuring-playbook-bot-baibot.md) - a bot through which you can talk to various [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) services ([OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) and [others](https://github.com/etkecc/baibot/blob/main/docs/providers.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:174
+msgid "[Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md) - a bot to remind you about stuff"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:176
+msgid "[Setting up matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) - a bot to create and manage registration tokens to invite users"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:178
+msgid "[Setting up maubot](configuring-playbook-bot-maubot.md) - a plugin-based Matrix bot system"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:180
+msgid "[Setting up Honoroit](configuring-playbook-bot-honoroit.md) - a helpdesk bot"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:182
+msgid "[Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) - a moderation tool/bot"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:184
+msgid "[Setting up Draupnir](configuring-playbook-bot-draupnir.md) - a moderation tool/bot, forked from Mjolnir and maintained by its former leader developer"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:186
+msgid "[Setting up Draupnir for all/D4A](configuring-playbook-appservice-draupnir-for-all.md) - like the [Draupnir bot](configuring-playbook-bot-draupnir.md) mentioned above, but running in appservice mode and supporting multiple instances"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:188
+msgid "[Setting up Buscarron](configuring-playbook-bot-buscarron.md) - a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:190
+msgid "Administration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:192
+msgid "Services that help you in administrating and monitoring your Matrix installation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:194
+msgid "[Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:196
+msgid "[Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:198
+msgid "[Enabling metrics and graphs for NginX logs](configuring-playbook-prometheus-nginxlog.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:200
+msgid "[Setting up the rageshake bug report server](configuring-playbook-rageshake.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:202
+msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:204
+msgid "Backups:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:205
+msgid "[Setting up BorgBackup](configuring-playbook-backup-borg.md) - a full Matrix server backup solution, including the Postgres database"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:207
+msgid "[Setting up postgres backup](configuring-playbook-postgres-backup.md) - a Postgres-database backup solution (note: does not include other files)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:209
+msgid "Other specialized services"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:211
+msgid "Various services that don't fit any other categories."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:213
+msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:215
+msgid "[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:217
+msgid "[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:219
+msgid "[Setting up Etherpad](configuring-playbook-etherpad.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:221
+msgid "[Setting up the Jitsi video-conferencing platform](configuring-playbook-jitsi.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:223
+msgid "[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) - a federated comment system built on Matrix"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:225
+msgid "[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-pantalaimon.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:227
+msgid "[Setting up the Sygnal push gateway](configuring-playbook-sygnal.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:229
+msgid "[Setting up the ntfy push notifications server](configuring-playbook-ntfy.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:231
+msgid "Deprecated / unmaintained / removed services"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:233
+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:235
+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:237
+msgid "[Setting up Appservice Webhooks bridging](configuring-playbook-bridge-appservice-webhooks.md) (deprecated; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:239
+msgid "[Setting up the Dimension integration manager](configuring-playbook-dimension.md) ([unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299); after [installing](installing.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:241
+msgid "[Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:243
+msgid "[Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) (unmaintained; the bridge's author suggests taking a look at [baibot](https://github.com/etkecc/baibot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bot-baibot.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:245
+msgid "[Setting up Mautrix Facebook bridging](configuring-playbook-bridge-mautrix-facebook.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-messenger](configuring-playbook-bridge-mautrix-meta-messenger.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:247
+msgid "[Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-mautrix-hangouts.md) (deprecated in favor of the Google Chat bridge with [mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:249
+msgid "[Setting up Mautrix Instagram bridging](configuring-playbook-bridge-mautrix-instagram.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-instagram](configuring-playbook-bridge-mautrix-meta-instagram.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:251
+msgid "[Setting up MX Puppet Skype bridging](configuring-playbook-bridge-mx-puppet-skype.md) (removed; this component has been broken for a long time, so it has been removed from the playbook. Consider [setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md))"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/configuring-well-known.po b/i18n/locales/jp/LC_MESSAGES/docs/configuring-well-known.po
new file mode 100644
index 000000000..20a45a880
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/configuring-well-known.po
@@ -0,0 +1,257 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/configuring-well-known.md:1
+msgid "Configuring Service Discovery via .well-known"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:3
+msgid "This documentation page explains how to configure Service discovery via `/.well-known/` files. Service discovery is a way for the Matrix network to discover where a Matrix server is."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:5
+msgid "Types of well-known service discovery mechanism"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:7
+msgid "There are 3 types of well-known service discovery mechanism that Matrix makes use of:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:9
+msgid "(important) **Federation Server discovery** (`/.well-known/matrix/server`) -- assists other servers in the Matrix network with finding your server. With the default playbook configuration specified on the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), this is necessary for federation to work. Without a proper configuration, your server will effectively not be part of the Matrix network."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:11
+msgid "(less important) **Client Server discovery** (`/.well-known/matrix/client`) -- assists programs that you use to connect to your server (e.g. Element Web), so that they can make it more convenient for you by automatically configuring the \"Homeserver URL\" and \"Identity Server URL\" addresses."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:13
+msgid "(optional) **Support service discovery** (`/.well-known/matrix/support`) -- returns server admin contact and support page of the domain."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:15
+msgid "Federation Server Discovery"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:17
+msgid "All services created by this playbook are meant to be installed on their own server (such as `matrix.example.com`), instead of the base domain (`example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:19
+msgid "As [per the Server-Server specification](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), in order to use a short Matrix user ID like `@alice:example.com` instead of `@alice:matrix.example.com` while hosting services on a subdomain such as `matrix.example.com`, the Matrix network needs to be instructed of [server delegation](howto-server-delegation.md) / redirection."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:21
+msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:23
+msgid "If you set up the DNS SRV record for server delegation instead, take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:25
+msgid "Client Server Discovery"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:27
+msgid "Client Server Service discovery lets various client programs which support it, to receive a full user ID (e.g. `@alice:example.com`) and determine where the Matrix server is automatically (e.g. `https://matrix.example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:29
+msgid "This lets you (and your users) easily connect to your Matrix server without having to customize connection URLs. When using client programs that support it, you won't need to point them to `https://matrix.example.com` in Custom Server options manually anymore. The connection URL would be discovered automatically from your full username."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:31
+msgid "Without /.well-known/matrix/client, the client will make the wrong \"homeserver URL\" assumption (it will default to using https://example.com, and users will need to notice and adjust it manually (changing it to https://matrix.example.com)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:33
+msgid "As [per the Client-Server specification](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery) Matrix does Client Server service discovery using a `/.well-known/matrix/client` file hosted on the base domain (e.g. `example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:35
+msgid "However, this playbook installs your Matrix server on another domain (e.g. `matrix.example.com`) and not on the base domain (e.g. `example.com`), so it takes a little extra manual effort to set up the file."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:37
+msgid "Support Service Discovery (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:39
+msgid "[MSC 1929](https://github.com/matrix-org/matrix-spec-proposals/pull/1929), which was added to [Matrix Specification version v1.10](https://spec.matrix.org/v1.10/client-server-api/#getwell-knownmatrixsupport), specifies a way to add contact details of admins, as well as a link to a support page for users who are having issues with the service. Automated services may also index this information and use it for abuse reports, etc."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:41
+msgid "To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:62
+msgid "Installing well-known files on the base domain's server"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:64
+msgid "To implement the service discovery mechanisms, your base domain's server (e.g. `example.com`) needs to run an HTTPS-capable webserver."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:66
+msgid "Serving the base domain from the Matrix server via the playbook"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:68
+msgid "If you don't have a server for your base domain at all, you can use the Matrix server for this. If you don't need the base domain (e.g. `example.com`) for anything else (hosting a website, etc.), you can point it to the Matrix server's IP address and tell the playbook to configure it."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:70
+msgid "**This is the easiest way to set up well-known serving** -- letting the playbook handle the whole base domain for you (including SSL certificates, etc.) and take care to serve the appropriate well-known files automatically."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:72
+msgid "If you decide to go this route, you don't need to read ahead in this document. Instead, go to [Serving the base domain](configuring-playbook-base-domain-serving.md) to learn how the playbook can help you set it up."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:74
+msgid "However, if you need to use the base domain for other things, this method is less suitable than the one explained below."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:76
+msgid "Manually installing well-known files on the base domain's server"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:78
+msgid "If you're managing the base domain by yourself somehow, you'll need to set up serving of some `/.well-known/matrix/*` files from it via HTTPS."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:80
+msgid "To make things easy for you to set up, this playbook generates and hosts a few well-known files on the Matrix domain's server. The files are generated at the `/matrix/static-files/public/.well-known/matrix/` path on the server and hosted at URLs like `https://matrix.example.com/.well-known/matrix/server` and `https://matrix.example.com/.well-known/matrix/client`, even though this is the wrong place to host them."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:82
+msgid "You have two options when it comes to installing the files on the base domain's server:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:84
+msgid "(Option 1): **Copying the files manually** to your base domain's server"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:86
+msgid "**Hint**: Option 2 is generally a better way to do this. Make sure to go with it, if possible."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:88
+msgid "All you need to do is:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:90
+msgid "copy `/.well-known/matrix/server` and `/.well-known/matrix/client` from the Matrix server (e.g. `matrix.example.com`) to your base domain's server (`example.com`). You can find these files in the `/matrix/static-files/.well-known/matrix` directory on the Matrix server. They are also accessible on URLs like this: `https://matrix.example.com/.well-known/matrix/server` (same for `client`)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:92
+msgid "set up the server at your base domain (e.g. `example.com`) so that it adds an extra HTTP header when serving the `/.well-known/matrix/client` file. [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS), the `Access-Control-Allow-Origin` header should be set with a value of `*`. If you don't do this step, web-based Matrix clients (like Element Web) may fail to work. Setting up headers for the `/.well-known/matrix/server` file is not necessary, as this file is only consumed by non-browsers, which don't care about CORS."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:94
+msgid "This is relatively easy to do and possibly your only choice if you can only host static files from the base domain's server. It is, however, **a little fragile**, as future updates performed by this playbook may regenerate the well-known files and you may need to notice that and copy them over again."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:96
+msgid "(Option 2): **Setting up reverse-proxying** of the well-known files from the base domain's server to the Matrix server"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:98
+msgid "This option is less fragile and generally better."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:100
+msgid "On the base domain's server (e.g. `example.com`), you can set up reverse-proxying, so that any access for the `/.well-known/matrix` location prefix is forwarded to the Matrix domain's server (e.g. `matrix.example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:102
+msgid "With this method, you **don't need** to add special HTTP headers for [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) reasons (like `Access-Control-Allow-Origin`), because your Matrix server (where requests ultimately go) will be configured by this playbook correctly."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:104
+msgid "**For nginx**, it would be something like this:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:121
+msgid "**For Apache2**, it would be something like this:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:135
+msgid "**For Caddy 2**, it would be something like this:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:145
+msgid "**For HAProxy**, it would be something like this:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:164
+msgid "**For Netlify**, configure a [redirect](https://docs.netlify.com/routing/redirects/) using a `_redirects` file in the [publish directory](https://docs.netlify.com/configure-builds/overview/#definitions) with contents like this:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:170
+msgid "**For AWS CloudFront**"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:172
+msgid "Add a custom origin with matrix.example.com to your distribution"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:173
+msgid "Add two behaviors, one for `.well-known/matrix/client` and one for `.well-known/matrix/server` and point them to your new origin."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:175
+msgid "Make sure to:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:177
+msgid "**replace `example.com`** in the server configuration with your actual domain name"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:178
+msgid "and: to **do this for the HTTPS-enabled server block**, as that's where Matrix expects the file to be"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:180
+msgid "Confirming it works"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:182
+msgid "No matter which method you've used to set up the well-known files, if you've done it correctly you should be able to see a JSON file at these URLs:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:184
+msgid "`https://example.com/.well-known/matrix/server`"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:185
+msgid "`https://example.com/.well-known/matrix/client`"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:186
+msgid "`https://example.com/.well-known/matrix/support`"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:188
+msgid "You can also check if everything is configured correctly, by [checking if services work](maintenance-checking-services.md)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/container-images.po b/i18n/locales/jp/LC_MESSAGES/docs/container-images.po
new file mode 100644
index 000000000..52d0a92fe
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/container-images.po
@@ -0,0 +1,1157 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/container-images.md:1
+msgid "Container images used by the playbook"
+msgstr ""
+
+#: ../../../docs/container-images.md:3
+msgid "This page summarizes the container ([Docker](https://www.docker.com/)) images used by the playbook when setting up your server."
+msgstr ""
+
+#: ../../../docs/container-images.md:5
+msgid "We try to stick to official images (provided by their respective projects) as much as possible."
+msgstr ""
+
+#: ../../../docs/container-images.md:7
+msgid "Homeserver"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Service"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Container image"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Default?"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Description"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Synapse](configuring-playbook-synapse.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[element-hq/synapse](https://ghcr.io/element-hq/synapse)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "✅"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Conduit](configuring-playbook-conduit.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixconduit/matrix-conduit](https://hub.docker.com/r/matrixconduit/matrix-conduit)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "❌"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Dendrite](configuring-playbook-dendrite.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/dendrite-monolith](https://hub.docker.com/r/matrixdotorg/dendrite-monolith/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse."
+msgstr ""
+
+#: ../../../docs/container-images.md:15
+msgid "Clients"
+msgstr ""
+
+#: ../../../docs/container-images.md:17
+msgid "Web clients for Matrix that you can host on your own domains."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Element Web](configuring-playbook-client-element-web.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[vectorim/element-web](https://hub.docker.com/r/vectorim/element-web/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Default Matrix web client, configured to connect to your own Synapse server"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Hydrogen](configuring-playbook-client-hydrogen.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[element-hq/hydrogen-web](https://ghcr.io/element-hq/hydrogen-web)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Lightweight Matrix client with legacy and mobile browser support"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Cinny](configuring-playbook-client-cinny.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[ajbura/cinny](https://hub.docker.com/r/ajbura/cinny)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Simple, elegant and secure web client"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[etke.cc/schildichat-web](https://ghcr.io/etkecc/schildichat-web)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Based on Element Web, with a more traditional instant messaging experience"
+msgstr ""
+
+#: ../../../docs/container-images.md:26
+msgid "Server Components"
+msgstr ""
+
+#: ../../../docs/container-images.md:28
+msgid "Services that run on the server to make the various parts of your installation work."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[PostgreSQL](configuring-playbook-external-postgres.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[postgres](https://hub.docker.com/_/postgres/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Database for Synapse. [Using an external PostgreSQL server](configuring-playbook-external-postgres.md) is also possible."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Coturn](configuring-playbook-turn.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[coturn/coturn](https://hub.docker.com/r/coturn/coturn/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "STUN/TURN server for WebRTC audio/video calls"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Traefik](configuring-playbook-traefik.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Traefik](https://hub.docker.com/_/traefik/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](configuring-playbook-own-webserver.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Let's Encrypt](configuring-playbook-ssl-certificates.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[certbot/certbot](https://hub.docker.com/r/certbot/certbot/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "The [certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Exim](configuring-playbook-email.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[devture/exim-relay](https://hub.docker.com/r/devture/exim-relay/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[ma1sd](configuring-playbook-ma1sd.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Matrix Identity Server"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[ddclient](configuring-playbook-dynamic-dns.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[linuxserver/ddclient](https://hub.docker.com/r/linuxserver/ddclient)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider"
+msgstr ""
+
+#: ../../../docs/container-images.md:40
+msgid "Authentication"
+msgstr ""
+
+#: ../../../docs/container-images.md:42
+msgid "Extend and modify how users are authenticated on your homeserver."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-synapse-rest-auth](configuring-playbook-rest-auth.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "(N/A)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "REST authentication password provider module"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-synapse-shared-secret-auth](configuring-playbook-shared-secret-auth.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Password provider module"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-synapse-ldap3](configuring-playbook-ldap-auth.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "LDAP Auth password provider module"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[activism.international/matrix_ldap_registration_proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A proxy that handles Matrix registration requests and forwards them to LDAP."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-registration](configuring-playbook-matrix-registration.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-matrix-registration/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A simple python application to have a token based Matrix registration"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Matrix User Verification Service](configuring-playbook-user-verification-service.md) (UVS)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/matrix-user-verification-service](https://hub.docker.com/r/atrixdotorg/matrix-user-verification-service)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Service to verify details of a user based on an Open ID token"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[synapse-simple-antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A spam checker module"
+msgstr ""
+
+#: ../../../docs/container-images.md:54
+msgid "File Storage"
+msgstr ""
+
+#: ../../../docs/container-images.md:56
+msgid "Use alternative file storage to the default `media_store` folder."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Goofys](configuring-playbook-s3-goofys.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[ewoutp/goofys](https://hub.docker.com/r/ewoutp/goofys/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[synapse-s3-storage-provider](configuring-playbook-s3.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[t2bot/matrix-media-repo](https://ghcr.io/t2bot/matrix-media-repo)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "matrix-media-repo is a 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:64
+msgid "Bridges"
+msgstr ""
+
+#: ../../../docs/container-images.md:66
+msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-discord](configuring-playbook-bridge-mautrix-discord.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/discord](https://mau.dev/mautrix/discord/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Discord](https://discord.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-slack](configuring-playbook-bridge-mautrix-slack.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/slack](https://mau.dev/mautrix/slack/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Slack](https://slack.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-telegram](configuring-playbook-bridge-mautrix-telegram.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/telegram](https://mau.dev/mautrix/telegram/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Telegram](https://telegram.org/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-gmessages](configuring-playbook-bridge-mautrix-gmessages.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/gmessages](https://mau.dev/mautrix/gmessages/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Google Messages](https://messages.google.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-whatsapp](configuring-playbook-bridge-mautrix-whatsapp.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/whatsapp](https://mau.dev/mautrix/whatsapp/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [WhatsApp](https://www.whatsapp.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-wsproxy](configuring-playbook-bridge-mautrix-wsproxy.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/wsproxy](https://mau.dev/mautrix/wsproxy/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to Android SMS or Apple iMessage"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-twitter](configuring-playbook-bridge-mautrix-twitter.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/twitter](https://mau.dev/mautrix/twitter/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Twitter](https://twitter.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/googlechat](https://mau.dev/mautrix/googlechat/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "mautrix-meta (for [Messenger](configuring-playbook-bridge-mautrix-meta-messenger.md) and [Instagram](configuring-playbook-bridge-mautrix-meta-instagram.md))"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/meta](https://mau.dev/mautrix/meta/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-signal](configuring-playbook-bridge-mautrix-signal.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/signal](https://mau.dev/mautrix/signal/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Signal](https://www.signal.org/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[beeper-linkedin](configuring-playbook-bridge-beeper-linkedin.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[beeper/linkedin](https://ghcr.io/beeper/linkedin)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [LinkedIn](https://www.linkedin.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/matrix-appservice-irc](https://hub.docker.com/r/matrixdotorg/matrix-appservice-irc)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-appservice-kakaotalk](configuring-playbook-bridge-appservice-kakaotalk.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Self-building"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-org/matrix-appservice-discord](https://ghcr.io/matrix-org/matrix-appservice-discord)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Discord](https://discordapp.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-hookshot](configuring-playbook-bridge-hookshot.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[halfshot/matrix-hookshot](https://hub.docker.com/r/halfshot/matrix-hookshot)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-sms-bridge](configuring-playbook-bridge-matrix-bridge-sms.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[folivonet/matrix-sms-bridge](https://hub.docker.com/repository/docker/folivonet/matrix-sms-bridge)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to SMS"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-wechat](configuring-playbook-bridge-wechat.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[lxduo/matrix-wechat](https://hub.docker.com/r/lxduo/matrix-wechat)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [WeChat](https://www.wechat.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Heisenbridge](configuring-playbook-bridge-heisenbridge.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[hif1/heisenbridge](https://hub.docker.com/r/hif1/heisenbridge)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[nodefyme/go-skype-bridge](https://hub.docker.com/r/nodefyme/go-skype-bridge)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Skype](https://www.skype.com)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Slack](https://slack.com)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-puppet-instagram)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-groupme](configuring-playbook-bridge-mx-puppet-groupme.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[xangelix/mx-puppet-groupme](https://hub.docker.com/r/xangelix/mx-puppet-groupme)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [GroupMe](https://groupme.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-steam](configuring-playbook-bridge-mx-puppet-steam.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[icewind1991/mx-puppet-steam](https://hub.docker.com/r/icewind1991/mx-puppet-steam)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Steam](https://steamapp.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Email2Matrix](configuring-playbook-email2matrix.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[devture/email2matrix](https://hub.docker.com/r/devture/email2matrix/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge for relaying emails to Matrix rooms"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[etke.cc/postmoogle](https://github.com/etkecc/postmoogle/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Email to Matrix bridge"
+msgstr ""
+
+#: ../../../docs/container-images.md:99
+msgid "Bots"
+msgstr ""
+
+#: ../../../docs/container-images.md:101
+msgid "Bots provide various additional functionality to your installation."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[baibot](configuring-playbook-bot-baibot.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[etke.cc/baibot](https://ghcr.io/etkecc/baibot)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[anoa/matrix-reminder-bot](https://hub.docker.com/r/anoa/matrix-reminder-bot)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bot for scheduling one-off & recurring reminders and alarms"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[moanos/matrix-registration-bot](https://hub.docker.com/r/moanos/matrix-registration-bot/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bot for invitations by creating and managing registration tokens"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[maubot](configuring-playbook-bot-maubot.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[dock.mau.dev/maubot/maubot](https://mau.dev/maubot/maubot/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A plugin-based Matrix bot system"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Honoroit](configuring-playbook-bot-honoroit.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[etke.cc/honoroit](https://github.com/etkecc/honoroit/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A helpdesk bot"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Mjolnir](configuring-playbook-bot-mjolnir.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/mjolnir](https://hub.docker.com/r/matrixdotorg/mjolnir)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A moderation tool for Matrix"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Draupnir](configuring-playbook-bot-draupnir.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[gnuxie/draupnir](https://hub.docker.com/r/gnuxie/draupnir)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A moderation tool for Matrix (Fork of Mjolnir)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Buscarron](configuring-playbook-bot-buscarron.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[etke.cc/buscarron](https://ghcr.io/etkecc/buscarron)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Web forms (HTTP POST) to Matrix"
+msgstr ""
+
+#: ../../../docs/container-images.md:114
+msgid "Administration"
+msgstr ""
+
+#: ../../../docs/container-images.md:116
+msgid "Services that help you in administrating and monitoring your Matrix installation."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[metio/matrix-alertmanager-receiver](https://hub.docker.com/r/metio/matrix-alertmanager-receiver)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[element-hq/matrix-authentication-service](https://ghcr.io/element-hq/matrix-authentication-service)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "OAuth 2.0 and OpenID Provider server"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[synapse-admin](configuring-playbook-synapse-admin.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[etke.cc/synapse-admin](https://ghcr.io/etkecc/synapse-admin)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A web UI tool for administrating users and rooms on your Matrix server"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Metrics and Graphs](configuring-playbook-prometheus-grafana.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[prom/prometheus](https://hub.docker.com/r/prom/prometheus/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Prometheus](https://prometheus.io) time-series database server"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[prom/node-exporter](https://hub.docker.com/r/prom/node-exporter/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[grafana/grafana](https://hub.docker.com/r/grafana/grafana/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Graphing tool that works well with the above two images. Our playbook also adds two dashboards for [Synapse](https://github.com/element-hq/synapse/tree/master/contrib/grafana) and [Node Exporter](https://github.com/rfrail3/grafana-dashboards)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Metrics and Graphs](configuring-playbook-prometheus-nginxlog.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[martin-helmich/prometheus-nginxlog-exporter/exporter](https://ghcr.io/martin-helmich/prometheus-nginxlog-exporter/exporter)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Addon for Prometheus that gathers access logs from various nginx reverse-proxies"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Borg](configuring-playbook-backup-borg.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Backups"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[rageshake](configuring-playbook-rageshake.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-org/rageshake](https://ghcr.io/matrix-org/rageshake)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bug report server"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[synapse-usage-exporter](configuring-playbook-synapse-usage-exporter.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus."
+msgstr ""
+
+#: ../../../docs/container-images.md:131
+msgid "Misc"
+msgstr ""
+
+#: ../../../docs/container-images.md:133
+msgid "Various services that don't fit any other categories."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[sliding-sync](configuring-playbook-sliding-sync-proxy.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+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
+msgid "[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A Synapse module to automatically accept invites."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[synapse_auto_compressor](configuring-playbook-synapse-auto-compressor.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[etke.cc/rust-synapse-compress-state](https://gitlab.com/etke.cc/rust-synapse-compress-state/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A cli tool that automatically compresses `state_groups` database table in background."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-corporal/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Reconciliator and gateway for a managed Matrix server"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Etherpad](configuring-playbook-etherpad.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[etherpad/etherpad](https://hub.docker.com/r/etherpad/etherpad/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "An open source collaborative text editor"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Jitsi](configuring-playbook-jitsi.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[jitsi/web](https://hub.docker.com/r/jitsi/web)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "the [Jitsi](https://jitsi.org/) web UI"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[jitsi/jicofo](https://hub.docker.com/r/jitsi/jicofo)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "the [Jitsi](https://jitsi.org/) Focus component"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[jitsi/prosody](https://hub.docker.com/r/jitsi/prosody)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "the [Jitsi](https://jitsi.org/) Prosody XMPP server component"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[jitsi/jvb](https://hub.docker.com/r/jitsi/jvb)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "the [Jitsi](https://jitsi.org/) Video Bridge component"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Cactus Comments](configuring-playbook-cactus-comments.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[cactuscomments/cactus-appservice](https://hub.docker.com/r/cactuscomments/cactus-appservice/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A federated comment system built on Matrix"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[joseluisq/static-web-server](https://hub.docker.com/r/joseluisq/static-web-server)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Pantalaimon](configuring-playbook-pantalaimon.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/pantalaimon](https://hub.docker.com/r/matrixdotorg/pantalaimon)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "An E2EE aware proxy daemon"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Sygnal](configuring-playbook-sygnal.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/sygnal](https://hub.docker.com/r/matrixdotorg/sygnal/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Reference Push Gateway for Matrix"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[ntfy](configuring-playbook-ntfy.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[binwiederhier/ntfy](https://hub.docker.com/r/binwiederhier/ntfy/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Self-hosted, UnifiedPush-compatible push notifications server"
+msgstr ""
+
+#: ../../../docs/container-images.md:152
+msgid "Container images of deprecated / unmaintained services"
+msgstr ""
+
+#: ../../../docs/container-images.md:154
+msgid "The list of the deprecated or unmaintained services is available [here](configuring-playbook.md#deprecated--unmaintained--removed-services)."
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Dimension](configuring-playbook-dimension.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-dimension)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "An open source integration manager for Matrix clients"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[Go-NEB](configuring-playbook-bot-go-neb.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/go-neb](https://hub.docker.com/r/matrixdotorg/go-neb)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A multi functional bot written in Go"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-chatgpt-bot](configuring-playbook-bot-chatgpt.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixgpt/matrix-chatgpt-bot](https://ghcr.io/matrixgpt/matrix-chatgpt-bot)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Accessing ChatGPT via your favourite Matrix client"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-facebook](configuring-playbook-bridge-mautrix-facebook.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/facebook](https://mau.dev/mautrix/facebook/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Facebook](https://facebook.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-hangouts](configuring-playbook-bridge-mautrix-hangouts.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/hangouts](https://mau.dev/mautrix/hangouts/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Google Hangouts](https://en.wikipedia.org/wiki/Google_Hangouts)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix-instagram](configuring-playbook-bridge-mautrix-instagram.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/instagram](https://mau.dev/mautrix/instagram/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Instagram](https://instagram.com/)"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/faq.po b/i18n/locales/jp/LC_MESSAGES/docs/faq.po
new file mode 100644
index 000000000..5fd864486
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/faq.po
@@ -0,0 +1,877 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/faq.md:1
+msgid "Frequently Asked Questions"
+msgstr ""
+
+#: ../../../docs/faq.md:3
+msgid "This documentation page tries to answer various Frequently Asked Questions about all things [Matrix](https://matrix.org/), with a focus on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work))."
+msgstr ""
+
+#: ../../../docs/faq.md:5
+msgid "This FAQ page does not intend to replace the [matrix.org FAQ](https://matrix.org/faq/) (please see that one too)."
+msgstr ""
+
+#: ../../../docs/faq.md:7
+msgid "We've only started this FAQ recently, so it's still somewhat empty."
+msgstr ""
+
+#: ../../../docs/faq.md:9
+msgid "Also, we encourage you to not dig yourself into a hole by reading way too much. When you've heard enough, proceed to installation. To get started, see [below](#how-do-i-run-the-installation) about our installation guides."
+msgstr ""
+
+#: ../../../docs/faq.md:11
+msgid "Introductory"
+msgstr ""
+
+#: ../../../docs/faq.md:13
+msgid "Where do I find more questions and answers about Matrix?"
+msgstr ""
+
+#: ../../../docs/faq.md:15
+msgid "This is a Frequently Asked Questions page focused on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work)) for deploying a [Matrix](https://matrix.org/) server."
+msgstr ""
+
+#: ../../../docs/faq.md:17
+msgid "For a lot more generic questions and answers, see the [matrix.org FAQ](https://matrix.org/faq/)."
+msgstr ""
+
+#: ../../../docs/faq.md:19
+msgid "What is Matrix? What is Element? What is Synapse? Why are you confusing me with so many terms?"
+msgstr ""
+
+#: ../../../docs/faq.md:21
+msgid "[Matrix](https://matrix.org/) is a new type of realtime communication (chat) network, the closest analogy to which is probably \"email\"."
+msgstr ""
+
+#: ../../../docs/faq.md:23
+msgid "You don't just use the \"email\" protocols (SMTP, POP3, IMAP) directly though. There's a *server* somewhere which stores your data (`@gmail.com`, `@yahoo.com`, `@hotmail.com`, `@your-company.com`) and you access it by using these \"email\" protocols via some *client* program (Outlook, Thunderbird, some website, etc)."
+msgstr ""
+
+#: ../../../docs/faq.md:25
+msgid "In the world of the Matrix chat protocol, there are various client programs. The first and currently most full-featured one is called [Element](https://element.io/) (used to be called Riot.im and Vector.im in the past). There are [many other clients](https://matrix.org/clients/). You can switch clients as much as you want until you find the one that is right for you on a given platform (you may use Element Desktop on your desktop, but Fluffychat on your phone, etc)."
+msgstr ""
+
+#: ../../../docs/faq.md:27
+msgid "Matrix is also like email due to the fact that there are many servers around the world which can all talk to each other (you can send email from `@gmail.com` addresses to `@yahoo.com` and `@hotmail.com` addresses). It's the same with Matrix (`@bob:example.com` can talk to `@alice:example.org`)."
+msgstr ""
+
+#: ../../../docs/faq.md:29
+msgid "If someone else is hosting your Matrix server (you being `@alice:matrix.org` or some other public server like this), all you need is a Matrix client program, like Element Web or Element X Android."
+msgstr ""
+
+#: ../../../docs/faq.md:31
+msgid "If you'd like to host your own server (you being `@alice:example.com`), you'd need to set up a Matrix server program, like Synapse."
+msgstr ""
+
+#: ../../../docs/faq.md:33
+msgid "In short:"
+msgstr ""
+
+#: ../../../docs/faq.md:35
+msgid "Matrix is the protocol - a set of rules about how the chat network operates"
+msgstr ""
+
+#: ../../../docs/faq.md:36
+msgid "Element is a client program you can use to participate on the Matrix chat network via some server (yours or someone else's). There are also [many other client programs](https://matrix.org/clients/)."
+msgstr ""
+
+#: ../../../docs/faq.md:37
+msgid "Synapse is a server program you can use to host your very own Matrix server."
+msgstr ""
+
+#: ../../../docs/faq.md:39
+msgid "This FAQ here mostly focuses on installing various Matrix services using the Ansible automation tool. You can learn much more about Matrix in the [matrix.org FAQ](https://matrix.org/faq/)."
+msgstr ""
+
+#: ../../../docs/faq.md:41
+msgid "People I wish to talk to are not on Matrix. Can I talk to them?"
+msgstr ""
+
+#: ../../../docs/faq.md:43
+msgid "You most likely can. Besides Matrix-native chats, Matrix also supports the concept of \"bridging\", which allows you to plug other networks into it."
+msgstr ""
+
+#: ../../../docs/faq.md:45
+msgid "This Ansible playbook can help you install [tens of bridges for various networks](configuring-playbook.md#bridging-other-networks)."
+msgstr ""
+
+#: ../../../docs/faq.md:47
+msgid "Besides setting up your own bridges (preferable), you can also use some [public bridges hosted by others](https://publiclist.anchel.nl/#bridges)."
+msgstr ""
+
+#: ../../../docs/faq.md:49
+msgid "How do I get started with Matrix?"
+msgstr ""
+
+#: ../../../docs/faq.md:51
+msgid "One of [Matrix](https://matrix.org/)'s distinguishing strengths (compared to other chat networks) is its decentralized nature. There's not just one entity (company, organization) controlling the servers. Rather there's thousands of servers operated by different people - one server being insecure, slow or disrespective toward its users does not affect the rest of the network. To participate in that decentralization in its fullest, consider hosting your own server or using some public server other than the largest/default one (`matrix.org`)."
+msgstr ""
+
+#: ../../../docs/faq.md:53
+msgid "There are 3 ways to get into Matrix, depending on your technical ability and needs:"
+msgstr ""
+
+#: ../../../docs/faq.md:55
+msgid "**using the existing default server** - the easiest way is to use an existing server. The largest public Matrix server is `matrix.org` and it's configured as a default server in clients such as [Element Web](https://app.element.io) and many others. Just use Element Web on the browser via that link (or [download client apps for your Desktop or smartphone](https://element.io/app-for-productivity)), create an account and start chatting."
+msgstr ""
+
+#: ../../../docs/faq.md:57
+msgid "**using some other server** - instead of using the largest public server (`matrix.org`), you can use another public one. Here's a [list of public Matrix servers](https://joinmatrix.org/servers/) to choose from. Go to [Element Web](https://app.element.io) or download [some other client](https://matrix.org/clients/) of your choosing and adjust the homeserver URL during login."
+msgstr ""
+
+#: ../../../docs/faq.md:59
+msgid "**using your own server** - running your own server puts you in ultimate control of your data. It also lets you have your own user IDs (e.g. `@bob:example.com`). See [How do I set up my own Matrix server](#how-do-i-set-up-my-own-matrix-server)."
+msgstr ""
+
+#: ../../../docs/faq.md:61
+msgid "How do I set up my own Matrix server?"
+msgstr ""
+
+#: ../../../docs/faq.md:63
+msgid "Normally, you'd first choose the [Matrix](https://matrix.org/) server software you'd like to run. At the time of this writing (January/2021), there's only one fully-featured server program, so there's only one reasonable choice. That's [Synapse](https://github.com/element-hq/synapse)."
+msgstr ""
+
+#: ../../../docs/faq.md:65
+msgid "There are [many guides about installing Synapse](https://matrix.org/docs/guides/#installing-synapse). Using this Ansible playbook is just one way of doing it."
+msgstr ""
+
+#: ../../../docs/faq.md:67
+msgid "Naturally, we're biased, so our usual recommendation is to go with this [Ansible](https://www.ansible.com/) playbook, instead of installing Synapse (and many many other things around it) manually."
+msgstr ""
+
+#: ../../../docs/faq.md:69
+msgid "To get started with the playbook, check out the [Quick start](quick-start.md) or full installation guide (starting at the [Prerequisites](prerequisites.md) page)."
+msgstr ""
+
+#: ../../../docs/faq.md:71
+msgid "What is Ansible? How does it work?"
+msgstr ""
+
+#: ../../../docs/faq.md:73
+msgid "[Ansible](https://www.ansible.com/) is an automation program. This \"playbook\" is a collection of tasks/scripts that will set up a [Matrix](https://matrix.org/) server for you, so you don't have to perform these tasks manually."
+msgstr ""
+
+#: ../../../docs/faq.md:75
+msgid "We have written these automated tasks for you and all you need to do is execute them using the Ansible program."
+msgstr ""
+
+#: ../../../docs/faq.md:77
+msgid "You can install Ansible and this playbook code repository on your own computer and tell it to install Matrix services at the server living at `matrix.example.com`. We recommend installing Ansible on your own computer."
+msgstr ""
+
+#: ../../../docs/faq.md:79
+msgid "Alternatively, you can download Ansible and the playbook itself directly on the `matrix.example.com` server."
+msgstr ""
+
+#: ../../../docs/faq.md:81
+msgid "To learn more, see our [dedicated Ansible documentation page](ansible.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:83
+msgid "What is `just`?"
+msgstr ""
+
+#: ../../../docs/faq.md:85
+msgid "[`just`](https://github.com/casey/just) is a modern command-runner alternative to [make](https://www.gnu.org/software/make/). It can be used to invoke commands with less typing."
+msgstr ""
+
+#: ../../../docs/faq.md:87
+msgid "The `just` utility executes shortcut commands (called \"recipes\"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile)."
+msgstr ""
+
+#: ../../../docs/faq.md:89
+msgid "For details about `just` commands, take a look at: [Running `just` commands](just.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:91
+msgid "The playbook also contains a `Makefile` for the `make` tool, but most of the just recipes are not available as targets in the `Makefile`."
+msgstr ""
+
+#: ../../../docs/faq.md:93
+msgid "Why use this playbook and not install Synapse and other things manually?"
+msgstr ""
+
+#: ../../../docs/faq.md:95
+msgid "There are various guides telling you how easy it is to install [Synapse](https://github.com/element-hq/synapse)."
+msgstr ""
+
+#: ../../../docs/faq.md:97
+msgid "Reading the documentation of this Ansible playbook, you may also be thinking:"
+msgstr ""
+
+#: ../../../docs/faq.md:99
+msgid "I don't know what [Ansible](https://www.ansible.com/) is. I don't know what [Docker](https://www.docker.com/) is. This looks more complicated."
+msgstr ""
+
+#: ../../../docs/faq.md:101
+msgid ".. so you may be leaning toward [installing Synapse manually](https://github.com/element-hq/synapse/blob/master/INSTALL.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:103
+msgid "The problem with a manual installation is:"
+msgstr ""
+
+#: ../../../docs/faq.md:105
+msgid "Synapse is written in Python. If not packaged for your distribution, you'd need to install various Python modules, etc., and keep them updated."
+msgstr ""
+
+#: ../../../docs/faq.md:106
+msgid "Synapse requires a [Postgres](https://www.postgresql.org/) database (it can run on SQLite, but that's very much discouraged). So you'd need to install Postgres as well."
+msgstr ""
+
+#: ../../../docs/faq.md:107
+msgid "you may also need a reverse-proxy server in front of it (nginx, Apache), so you'd need to be familiar with that"
+msgstr ""
+
+#: ../../../docs/faq.md:108
+msgid "SSL is required, so you'd need to obtain Let's Encrypt (or other free or non-free) certificates for one or more domain names. You'd need to be familiar with [certbot](https://certbot.eff.org/) (when using Let's Encrypt) or similar software."
+msgstr ""
+
+#: ../../../docs/faq.md:109
+msgid "for each additional component you'd like to add (client like [Element](https://element.io), bridge to some other chat network, integration manager (stickers, other services, Identity Manager, etc.), you'll need to spend extra time installing and wiring it with the rest of the system in a way that works."
+msgstr ""
+
+#: ../../../docs/faq.md:110
+msgid "you'll likely get slower updates for all of these components, depending on your distro packaging or your own time and ability"
+msgstr ""
+
+#: ../../../docs/faq.md:112
+msgid "The playbook, on the other hand, installs a bunch of components for you by default, obtains SSL certificates for you, etc. If you'd like, you can enable various bridges and other services with very little effort. All the components are wired to work together."
+msgstr ""
+
+#: ../../../docs/faq.md:114
+msgid "All services run in Docker containers (most being officially provided by each component's developers), so we're not at the mercy of distro packaging."
+msgstr ""
+
+#: ../../../docs/faq.md:116
+msgid "Why use this playbook and not just use the Docker image directly?"
+msgstr ""
+
+#: ../../../docs/faq.md:118
+msgid "Reasons are similar to the reasons for not installing manually."
+msgstr ""
+
+#: ../../../docs/faq.md:120
+msgid "Besides Synapse, you'd need other things - a Postgres database, likely the [Element](https://element.io) client, etc., etc."
+msgstr ""
+
+#: ../../../docs/faq.md:122
+msgid "Using the playbook, you get all these components in a way that works well together out of the box."
+msgstr ""
+
+#: ../../../docs/faq.md:124
+msgid "Occasionally I see some people are talking about \"MDAD\". What is it?"
+msgstr ""
+
+#: ../../../docs/faq.md:126
+msgid "It is the acronym of us: **m**atrix-**d**ocker-**a**nsible-**d**eploy."
+msgstr ""
+
+#: ../../../docs/faq.md:128
+msgid "What's different about this Ansible playbook compared to [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy)?"
+msgstr ""
+
+#: ../../../docs/faq.md:130
+msgid "This is similar to the [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy) Ansible deployment, but:"
+msgstr ""
+
+#: ../../../docs/faq.md:132
+msgid "this one is a complete Ansible playbook (instead of just a role), so it's **easier to run** - especially for folks not familiar with Ansible"
+msgstr ""
+
+#: ../../../docs/faq.md:134
+msgid "this one installs and hooks together **a lot more Matrix-related services** for you (see above)"
+msgstr ""
+
+#: ../../../docs/faq.md:136
+msgid "this one **can be executed more than once** without causing trouble"
+msgstr ""
+
+#: ../../../docs/faq.md:138
+msgid "works on various distros: **CentOS** (7.0+), Debian-based distributions (**Debian** 10/Buster+, **Ubuntu** 18.04+), **Archlinux**"
+msgstr ""
+
+#: ../../../docs/faq.md:140
+msgid "this one installs everything in a single directory (`/matrix` by default) and **doesn't \"contaminate\" your server** with files all over the place"
+msgstr ""
+
+#: ../../../docs/faq.md:142
+msgid "this one **doesn't necessarily take over** ports 80 and 443. By default, it sets up [Traefik](https://doc.traefik.io/traefik/) for you there, but you can also [use your own webserver](configuring-playbook-own-webserver.md)"
+msgstr ""
+
+#: ../../../docs/faq.md:144
+msgid "this one **runs everything in Docker containers**, so it's likely more predictable and less fragile (see [Docker images used by this playbook](container-images.md))"
+msgstr ""
+
+#: ../../../docs/faq.md:146
+msgid "this one retrieves and automatically renews free [Let's Encrypt](https://letsencrypt.org/) **SSL certificates** for you"
+msgstr ""
+
+#: ../../../docs/faq.md:148
+msgid "this one optionally can store the `media_store` content repository files on [Amazon S3](https://aws.amazon.com/s3/) (but defaults to storing files on the server's filesystem)"
+msgstr ""
+
+#: ../../../docs/faq.md:150
+msgid "this one optionally **allows you to use an external PostgreSQL server** for Synapse's database (but defaults to running one in a container)"
+msgstr ""
+
+#: ../../../docs/faq.md:152
+msgid "helps you **import data from a previous installation** (so you can migrate your manual virtualenv/Docker setup to a more managed one)"
+msgstr ""
+
+#: ../../../docs/faq.md:154
+msgid "this one is actually **maintained**"
+msgstr ""
+
+#: ../../../docs/faq.md:156
+msgid "Server-related"
+msgstr ""
+
+#: ../../../docs/faq.md:158
+msgid "What kind of server do I need to install Matrix using this Ansible playbook?"
+msgstr ""
+
+#: ../../../docs/faq.md:160
+msgid "We list our server requirements in [Prerequisites](prerequisites.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:162
+msgid "Why not run Matrix on Kubernetes?"
+msgstr ""
+
+#: ../../../docs/faq.md:164
+msgid "There's no reason not to run Matrix on [Kubernetes](https://kubernetes.io/)."
+msgstr ""
+
+#: ../../../docs/faq.md:166
+msgid "However, that's overly complicated for thousands of us who just want to run a single small (and sometimes not so small) Matrix server, either using \"cloud\" servers or even a [Raspberry Pi](https://www.raspberrypi.org/) at home."
+msgstr ""
+
+#: ../../../docs/faq.md:168
+msgid "For us, a Kubernetes-based setup which requires a cluster of multiple computers and is more technically-involved is a no-go."
+msgstr ""
+
+#: ../../../docs/faq.md:170
+msgid "There are others working on automating a Matrix-on-Kubernetes setup, such as this [Helm](https://helm.sh/) chart: https://github.com/dacruz21/matrix-chart."
+msgstr ""
+
+#: ../../../docs/faq.md:172
+msgid "Why don't you use Podman instead of Docker?"
+msgstr ""
+
+#: ../../../docs/faq.md:174
+msgid "We like the philosophy of a daemonless container runtime, but [Podman](https://podman.io) is just not ready for our use case yet."
+msgstr ""
+
+#: ../../../docs/faq.md:176
+msgid "Learn more about our past experiences/attempts to give Podman a chance, by reading [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/520)."
+msgstr ""
+
+#: ../../../docs/faq.md:178
+msgid "In short, `alias podman=docker` is a lie (for us)."
+msgstr ""
+
+#: ../../../docs/faq.md:180
+msgid "Why use Docker?"
+msgstr ""
+
+#: ../../../docs/faq.md:182
+msgid "[Docker](https://www.docker.com/) is one of our 2 hard dependencies (the other one being [systemd](https://systemd.io/))."
+msgstr ""
+
+#: ../../../docs/faq.md:184
+msgid "It lets us run services in an isolated manner and independently of the (usually old) packages available for distributions."
+msgstr ""
+
+#: ../../../docs/faq.md:186
+msgid "It also lets us have a unified setup which runs the same across various supported distros (see them on [Prerequisites](prerequisites.md))."
+msgstr ""
+
+#: ../../../docs/faq.md:188
+msgid "Is Docker a hard requirement?"
+msgstr ""
+
+#: ../../../docs/faq.md:190
+msgid "Yes. See [Why don't you use Podman instead of Docker?](#why-dont-you-use-podman-instead-of-docker) for why we're not using another container runtime."
+msgstr ""
+
+#: ../../../docs/faq.md:192
+msgid "All of our services run in containers. It's how we achieve predictability and also how we support tens of different services across lots of distros."
+msgstr ""
+
+#: ../../../docs/faq.md:194
+msgid "The only thing we need on the distro is systemd and Python (we install Docker ourselves, unless you ask us not to)."
+msgstr ""
+
+#: ../../../docs/faq.md:196
+msgid "Why don't you use docker-compose?"
+msgstr ""
+
+#: ../../../docs/faq.md:198
+msgid "Instead of using [docker-compose](https://docs.docker.com/compose/), we prefer installing systemd services and scheduling those independently."
+msgstr ""
+
+#: ../../../docs/faq.md:200
+msgid "There are people who have worked on turning this setup into a docker-compose-based one. See these experiments [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/64#issuecomment-603164625). There is also a demo project ([element-docker-demo](https://github.com/element-hq/element-docker-demo)) by Element."
+msgstr ""
+
+#: ../../../docs/faq.md:202
+msgid "Can I run this on a distro without systemd?"
+msgstr ""
+
+#: ../../../docs/faq.md:204
+msgid "No. [systemd](https://systemd.io/) is one of our 2 hard dependencies (the other one being [Docker](https://www.docker.com/))."
+msgstr ""
+
+#: ../../../docs/faq.md:206
+msgid "Can I install this on a Raspberry Pi?"
+msgstr ""
+
+#: ../../../docs/faq.md:208
+msgid "Yes, you can. See our [Alternative Architectures](alternative-architectures.md) documentation page."
+msgstr ""
+
+#: ../../../docs/faq.md:210
+msgid "Whether a Raspberry Pi has enough power to give you a good experience is another question. It depends on your use case."
+msgstr ""
+
+#: ../../../docs/faq.md:212
+msgid "Also see: [What kind of server specs do I need?](#what-kind-of-server-specs-do-i-need)."
+msgstr ""
+
+#: ../../../docs/faq.md:214
+msgid "What kind of server specs do I need?"
+msgstr ""
+
+#: ../../../docs/faq.md:216
+msgid "This largely depends on your use case. It's not so much the number of users that you plan to host, but rather the number of large rooms they will join."
+msgstr ""
+
+#: ../../../docs/faq.md:218
+msgid "Federated rooms with lots of history and containing hundreds of other servers are very heavy CPU-wise and memory-wise."
+msgstr ""
+
+#: ../../../docs/faq.md:220
+msgid "You can probably use a 1 CPU + 1GB memory server to host hundreds of local users just fine, but as soon as one of them joins a federated room like `#matrix:matrix.org` (Matrix HQ) or some IRC-bridged room (say `##linux`), your server will get the need for a lot more power (at least 2GB RAM, etc)."
+msgstr ""
+
+#: ../../../docs/faq.md:222
+msgid "Running Matrix on a server with 1GB of memory is possible (especially if you disable some not-so-important services). See [How do I optimize this setup for a low-power server?](#how-do-i-optimize-this-setup-for-a-low-power-server)."
+msgstr ""
+
+#: ../../../docs/faq.md:224
+msgid "**We recommend starting with a server having at least 2GB of memory** and even then using it sparingly. If you know for sure you'll be joining various large rooms, etc., then going for 4GB of memory or more is a good idea."
+msgstr ""
+
+#: ../../../docs/faq.md:226
+msgid "Besides the regular Matrix stuff, we also support things like video-conferencing using [Jitsi](configuring-playbook-jitsi.md) and other additional services which (when installed) may use up a lot of memory. Things do add up. Besides the Synapse Matrix server, Jitsi is especially notorious for consuming a lot of resources. If you plan on running Jitsi, we recommend a server with at least 2GB of memory (preferrably more). See our [Jitsi documentation page](configuring-playbook-jitsi.md) to learn how to optimize its memory/CPU usage."
+msgstr ""
+
+#: ../../../docs/faq.md:228
+msgid "Can I run this in an LXC container?"
+msgstr ""
+
+#: ../../../docs/faq.md:230
+msgid "If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container."
+msgstr ""
+
+#: ../../../docs/faq.md:232
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/faq.md:234
+msgid "Why install my server at matrix.example.com and not at the base domain?"
+msgstr ""
+
+#: ../../../docs/faq.md:236
+msgid "It's the same with email servers. Your email address is likely `name@company.com`, not `name@mail.company.com`, even though it's `mail.company.com` that is really handling your data for `@company.com` email to work."
+msgstr ""
+
+#: ../../../docs/faq.md:238
+msgid "Using a separate domain name is easier to manage (although it's a little hard to get right at first) and keeps your Matrix server isolated from your website (if you have one), from your email server (if you have one), etc. Therefore, this playbook sets up services on your Matrix server (`matrix.example.com`) by default."
+msgstr ""
+
+#: ../../../docs/faq.md:240
+msgid "I don't control anything on the base domain and can't set up delegation to matrix.example.com. What do I do?"
+msgstr ""
+
+#: ../../../docs/faq.md:242
+msgid "If you're not in control of your base domain (or the server handling it) at all, you can take a look at [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:244
+msgid "I can't set up HTTPS on the base domain. How will I get Matrix federating?"
+msgstr ""
+
+#: ../../../docs/faq.md:246
+msgid "If you really can't obtain an HTTPS certificate for your base domain, you can take a look at [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:248
+msgid "How do I install on matrix.example.com without involving the base domain?"
+msgstr ""
+
+#: ../../../docs/faq.md:250
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/faq.md:271
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/faq.md:278
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/faq.md:280
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/faq.md:282
+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/faq.md:284
+msgid "Without setting up [server delegation](howto-server-delegation.md) to `matrix.example.com`, your user IDs will be like `@alice:matrix.example.com`. This is equivalent to having an email address like `bob@mail.company.com`, instead of just `bob@company.com`."
+msgstr ""
+
+#: ../../../docs/faq.md:286
+msgid "I don't use the base domain for anything. How am I supposed to set up Server Delegation for Matrix services?"
+msgstr ""
+
+#: ../../../docs/faq.md:288
+msgid "If you don't use your base domain for anything, then it's hard for you to \"serve files over HTTPS\" on it -- something we ask you to do for the [.well-known](configuring-well-known.md) setup (needed for [Server Delegation](howto-server-delegation.md))."
+msgstr ""
+
+#: ../../../docs/faq.md:290
+msgid "Luckily, the playbook can set up your Matrix server (at `matrix.example.com`) to also handle traffic for the base domain (`example.com`)."
+msgstr ""
+
+#: ../../../docs/faq.md:292
+msgid "See [Serving the base domain](configuring-playbook-base-domain-serving.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:294
+msgid "How do I optimize this setup for a low-power server?"
+msgstr ""
+
+#: ../../../docs/faq.md:296
+msgid "You can disable some not-so-important services to save on memory."
+msgstr ""
+
+#: ../../../docs/faq.md:318
+msgid "You can also consider implementing a restriction on room complexity, in order to prevent users from joining very heavy rooms:"
+msgstr ""
+
+#: ../../../docs/faq.md:328
+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:330
+msgid "I already have Docker on my server. Can you stop installing Docker via the playbook?"
+msgstr ""
+
+#: ../../../docs/faq.md:332
+msgid "Yes, we can stop installing Docker ourselves. Just use this in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/faq.md:338
+msgid "I run another webserver on the same server where I wish to install Matrix. What now?"
+msgstr ""
+
+#: ../../../docs/faq.md:340
+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:342
+msgid "How is the effective configuration determined?"
+msgstr ""
+
+#: ../../../docs/faq.md:344
+msgid "Configuration variables are defined in multiple places in this playbook and are considered in this order:"
+msgstr ""
+
+#: ../../../docs/faq.md:346
+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:348
+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:350
+msgid "finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` file, which is the ultimate override"
+msgstr ""
+
+#: ../../../docs/faq.md:352
+msgid "What configuration variables are available?"
+msgstr ""
+
+#: ../../../docs/faq.md:354
+msgid "You can discover the variables you can override in each role (`roles/*/*/defaults/main.yml`)."
+msgstr ""
+
+#: ../../../docs/faq.md:356
+msgid "As described in [How is the effective configuration determined?](#how-is-the-effective-configuration-determined), these role-defaults may be overriden by values defined in `group_vars/matrix_servers`."
+msgstr ""
+
+#: ../../../docs/faq.md:358
+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:360 ../../../docs/faq.md:372
+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:362
+msgid "I'd like to adjust some configuration which doesn't have a corresponding variable. How do I do it?"
+msgstr ""
+
+#: ../../../docs/faq.md:364
+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:366
+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:368
+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:370
+msgid "Check each role's `roles/*/*/defaults/main.yml` for the corresponding variable and an example for how use it."
+msgstr ""
+
+#: ../../../docs/faq.md:374
+msgid "Installation"
+msgstr ""
+
+#: ../../../docs/faq.md:376
+msgid "How do I run the installation?"
+msgstr ""
+
+#: ../../../docs/faq.md:378
+msgid "See [Installing](installing.md) to learn how to use Ansible to install Matrix services."
+msgstr ""
+
+#: ../../../docs/faq.md:380
+msgid "However, we recommend you to follow our installation guide, instead of jumping straight to installing."
+msgstr ""
+
+#: ../../../docs/faq.md:382
+msgid "There are two guides available:"
+msgstr ""
+
+#: ../../../docs/faq.md:384
+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:386
+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:388
+msgid "I installed Synapse some other way. Can I migrate such a setup to the playbook?"
+msgstr ""
+
+#: ../../../docs/faq.md:390
+msgid "Yes, you can."
+msgstr ""
+
+#: ../../../docs/faq.md:392
+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:394
+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:396
+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:398
+msgid "I've downloaded Ansible and the playbook on the server. It can't connect using SSH."
+msgstr ""
+
+#: ../../../docs/faq.md:400
+msgid "If you're using the playbook directly on the server, then Ansible doesn't need to connect using SSH."
+msgstr ""
+
+#: ../../../docs/faq.md:402
+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:404
+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:406
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/faq.md:408
+msgid "I get \"Error response from daemon: configured logging driver does not support reading\" when I do `docker logs matrix-synapse`."
+msgstr ""
+
+#: ../../../docs/faq.md:410
+msgid "See [How can I see the logs?](#how-can-i-see-the-logs)."
+msgstr ""
+
+#: ../../../docs/faq.md:412
+msgid "How can I see the logs?"
+msgstr ""
+
+#: ../../../docs/faq.md:414
+msgid "We utilize [systemd/journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html#Description) for logging."
+msgstr ""
+
+#: ../../../docs/faq.md:416
+msgid "To see logs for Synapse, run `journalctl -fu matrix-synapse.service`. You may wish to see the [manual page for journalctl](https://www.commandlinux.com/man-page/man1/journalctl.1.html)."
+msgstr ""
+
+#: ../../../docs/faq.md:418
+msgid "Available service names can be seen by doing `ls /etc/systemd/system/matrix*.service` on the server."
+msgstr ""
+
+#: ../../../docs/faq.md:420
+msgid "Some services also log to files in `/matrix/*/data/..`, but we're slowly moving away from that."
+msgstr ""
+
+#: ../../../docs/faq.md:422
+msgid "We also disable Docker logging, so you can't use `docker logs matrix-*` either. We do this to prevent useless double (or even triple) logging and to avoid having to rotate log files."
+msgstr ""
+
+#: ../../../docs/faq.md:424
+msgid "We just simply delegate logging to journald and it takes care of persistence and expiring old data."
+msgstr ""
+
+#: ../../../docs/faq.md:426
+msgid "Also see: [How long do systemd/journald logs persist for?](#how-long-do-systemdjournald-logs-persist-for)"
+msgstr ""
+
+#: ../../../docs/faq.md:428
+msgid "How long do systemd/journald logs persist for?"
+msgstr ""
+
+#: ../../../docs/faq.md:430
+msgid "On some distros, the journald logs are just in-memory and not persisted to disk."
+msgstr ""
+
+#: ../../../docs/faq.md:432
+msgid "Consult (and feel free to adjust) your distro's journald logging configuration in `/etc/systemd/journald.conf`."
+msgstr ""
+
+#: ../../../docs/faq.md:434
+msgid "To enable persistence and put some limits on how large the journal log files can become, adjust your configuration like this:"
+msgstr ""
+
+#: ../../../docs/faq.md:445
+msgid "Maintenance"
+msgstr ""
+
+#: ../../../docs/faq.md:447
+msgid "Do I need to do anything to keep my Matrix server updated?"
+msgstr ""
+
+#: ../../../docs/faq.md:449
+msgid "Yes. We don't update anything for you automatically."
+msgstr ""
+
+#: ../../../docs/faq.md:451
+msgid "See our [documentation page about upgrading services](maintenance-upgrading-services.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:453
+msgid "How do I move my existing installation to another (VM) server?"
+msgstr ""
+
+#: ../../../docs/faq.md:455
+msgid "If you have an existing installation done using this Ansible playbook, you can easily migrate that to another server using [our dedicated server migration guide](maintenance-migrating.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:457
+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:459
+msgid "How do I back up the data on my server?"
+msgstr ""
+
+#: ../../../docs/faq.md:461
+msgid "We haven't documented this properly yet, but the general advice is to:"
+msgstr ""
+
+#: ../../../docs/faq.md:463
+msgid "back up Postgres by making a database dump. See [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql)"
+msgstr ""
+
+#: ../../../docs/faq.md:465
+msgid "back up all `/matrix` files, except for `/matrix/postgres/data` (you already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` (this directory may exist and contain your old data if you've [performed a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql))."
+msgstr ""
+
+#: ../../../docs/faq.md:467
+msgid "You can later restore these by:"
+msgstr ""
+
+#: ../../../docs/faq.md:469
+msgid "Restoring the `/matrix` directory and files on the new server manually"
+msgstr ""
+
+#: ../../../docs/faq.md:470
+msgid "Following the instruction described on [Installing a server into which you'll import old data](installing.md#installing-a-server-into-which-youll-import-old-data)"
+msgstr ""
+
+#: ../../../docs/faq.md:472
+msgid "If your server's IP address has changed, you may need to [set up DNS](configuring-dns.md) again."
+msgstr ""
+
+#: ../../../docs/faq.md:474
+msgid "What is this `/matrix/postgres/data-auto-upgrade-backup` directory that is taking up so much space?"
+msgstr ""
+
+#: ../../../docs/faq.md:476
+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:478
+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:480
+msgid "How do I debug or force SSL certificate renewal?"
+msgstr ""
+
+#: ../../../docs/faq.md:482
+msgid "SSL certificates are managed automatically by the [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server."
+msgstr ""
+
+#: ../../../docs/faq.md:484
+msgid "If you're having trouble with SSL certificate renewal, check the Traefik logs (`journalctl -fu matrix-traefik`)."
+msgstr ""
+
+#: ../../../docs/faq.md:486
+msgid "If you're [using your own webserver](configuring-playbook-own-webserver.md) instead of the integrated one (Traefik), you should investigate in another way."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/getting-the-playbook.po b/i18n/locales/jp/LC_MESSAGES/docs/getting-the-playbook.po
new file mode 100644
index 000000000..4a6bfe641
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/getting-the-playbook.po
@@ -0,0 +1,85 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/getting-the-playbook.md:1
+msgid "Getting the playbook"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:3
+msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > Getting the playbook > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)</sup>"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:5
+msgid "This Ansible playbook is meant to be executed on your own computer (not the Matrix server)."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:7
+msgid "In special cases (if your computer cannot run Ansible, etc.) you may put the playbook on the server as well."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:9
+msgid "You can retrieve the playbook's source code by:"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:11
+msgid "[Using git to get the playbook](#using-git-to-get-the-playbook) (recommended)"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:13
+msgid "[Downloading the playbook as a ZIP archive](#downloading-the-playbook-as-a-zip-archive) (not recommended)"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:15
+msgid "Using git to get the playbook"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:17
+msgid "We recommend using the [git](https://git-scm.com/) tool to get the playbook's source code, because it lets you easily keep up to date in the future when [Maintaining services](maintenance-upgrading-services.md)."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:19
+msgid "Once you've installed git on your computer, you can go to any directory of your choosing and run the following command to retrieve the playbook's source code:"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:25
+msgid "This will create a new `matrix-docker-ansible-deploy` directory. You're supposed to execute all other installation commands inside that directory."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:27
+msgid "Downloading the playbook as a ZIP archive"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:29
+msgid "Alternatively, you can download the playbook as a ZIP archive. This is not recommended, as it's not easy to keep up to date with future updates. We suggest you [use git](#using-git-to-get-the-playbook) instead."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:31
+msgid "The latest version is always at the following URL: https://github.com/spantaleev/matrix-docker-ansible-deploy/archive/master.zip"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:33
+msgid "You can extract this archive anywhere. You'll get a directory called `matrix-docker-ansible-deploy-master`. You're supposed to execute all other installation commands inside that directory."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:37
+msgid "[▶️](configuring-playbook.md) No matter which method you've used to download the playbook, you can proceed by [Configuring the playbook](configuring-playbook.md)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/howto-server-delegation.po b/i18n/locales/jp/LC_MESSAGES/docs/howto-server-delegation.po
new file mode 100644
index 000000000..f31b86f09
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/howto-server-delegation.po
@@ -0,0 +1,189 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-23 13:09+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/howto-server-delegation.md:1
+msgid "Server Delegation"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:3
+msgid "By default, this playbook sets up services on your Matrix server (`matrix.example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:5
+msgid "Server delegation can be configured in either of these ways:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:7
+msgid "[Setting up a `/.well-known/matrix/server` file](#server-delegation-via-a-well-known-file) on the base domain (`example.com`)"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:8
+msgid "[Setting up a `_matrix._tcp` DNS SRV record](#server-delegation-via-a-dns-srv-record-advanced)"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:10
+msgid "Both methods have their place and will continue to do so. You only need to use just one of these delegation methods."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:12
+msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file. However, that method may have some downsides that are not to your liking. Hence this guide about alternative ways to set up Server Delegation."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:14
+msgid "**Note**: as an alternative, it is possible to install the server such that it uses only the `matrix.example.com` domain (instead of identifying as the shorter base domain - `example.com`). This should be helpful if you are not in control of anything on the base domain (`example.com`). In this case, you would not need to configure server delegation, but you would need to add other configuration. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:16
+msgid "Server Delegation via a well-known file"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:18
+msgid "This playbook recommends you to set up server delegation by means of a `/.well-known/matrix/server` file served from the base domain (`example.com`), as this is the most straightforward way to set up the delegation."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:20
+msgid "To configure server delegation with the well-known file, check this section on [Configuring Service Discovery via .well-known](configuring-well-known.md): [Installing well-known files on the base domain's server](configuring-well-known.md#installing-well-known-files-on-the-base-domain-s-server)"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:22
+msgid "Downsides of well-known-based Server Delegation"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:24
+msgid "Server Delegation by means of a `/.well-known/matrix/server` file is the most straightforward, but suffers from the following downsides:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:26
+msgid "you need to have a working HTTPS server for the base domain (`example.com`). If you don't have any server for the base domain at all, you can easily solve it by making the playbook [serve the base domain from the Matrix server](configuring-playbook-base-domain-serving.md)."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:28
+msgid "any downtime on the base domain (`example.com`) or network trouble between the Matrix subdomain (`matrix.example.com`) and the base `example.com` may cause Matrix Federation outages. As the [Server-Server spec says](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery):"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:30
+msgid "Errors are recommended to be cached for up to an hour, and servers are encouraged to exponentially back off for repeated failures."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:32
+msgid "**For most people, this is a reasonable tradeoff** given that it's easy and straightforward to set up. We recommend you stay on this path."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:34
+msgid "Otherwise, you can decide to go against the default for this playbook, and instead set up [Server Delegation via a DNS SRV record (advanced)](#server-delegation-via-a-dns-srv-record-advanced) (much more complicated)."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:36
+msgid "Server Delegation via a DNS SRV record (advanced)"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:38
+msgid "**Note**: doing Server Delegation via a DNS SRV record is a more **advanced** way to do it and is not the default for this playbook. This is usually **much more complicated** to set up, so **we don't recommend it**. If you're not an experienced sysadmin, you'd better stay away from this."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:40
+msgid "As per the [Server-Server spec](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), it's possible to do Server Delegation using only a SRV record (without a `/.well-known/matrix/server` file)."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:42
+msgid "This prevents you from suffering the [Downsides of well-known-based Server Delegation](#downsides-of-well-known-based-server-delegation)."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:44
+msgid "To use DNS SRV record validation, you need to:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:46
+msgid "ensure that `/.well-known/matrix/server` is **not served** from the base domain, as that would interfere with DNS SRV record Server Delegation. To make the playbook **not** generate and serve the file, use the following configuration: `matrix_static_files_file_matrix_server_enabled: false`."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:48
+msgid "ensure that you have a `_matrix._tcp` DNS SRV record for your base domain (`example.com`) with a value of `10 0 8448 matrix.example.com`"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:50
+msgid "ensure that you are serving the Matrix Federation API (tcp/8448) with a certificate for `example.com` (not `matrix.example.com`!). Getting this certificate to the `matrix.example.com` server may be complicated. The playbook's automatic SSL obtaining/renewal flow will likely not work and you'll need to copy certificates around manually. See below."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:52
+msgid "For more details on how to configure the playbook to work with SRV delegation, take a look at this documentation: [Server Delegation via a DNS SRV record (advanced)](howto-srv-server-delegation.md)"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:54
+msgid "Obtain certificates"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:56
+msgid "How you can obtain a valid certificate for `example.com` on the `matrix.example.com` server is up to you."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:58
+msgid "If `example.com` and `matrix.example.com` are hosted on the same machine, you can let the playbook obtain the certificate for you, by following our [Obtaining SSL certificates for additional domains](configuring-playbook-ssl-certificates.md#obtaining-ssl-certificates-for-additional-domains) guide."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:60
+msgid "If `example.com` and `matrix.example.com` are not hosted on the same machine, you can copy over the certificate files manually. Don't forget that they may get renewed once in a while, so you may also have to transfer them periodically. How often you do that is up to you, as long as the certificate files don't expire."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:62
+msgid "Serving the Federation API with your certificates"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:64
+msgid "Regardless of which method for obtaining certificates you've used, once you've managed to get certificates for your base domain onto the `matrix.example.com` machine you can put them to use."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:66
+msgid "Based on your setup, you have different ways to go about it:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:68
+msgid "Serving the Federation API with your certificates and Synapse handling Federation"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:70
+msgid "You can let Synapse handle Federation by itself."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:72
+msgid "To do that, make sure the certificate files are mounted into the Synapse container:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:79
+msgid "You can then tell Synapse to serve Federation traffic over TLS on `tcp/8448`:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:87
+msgid "Make sure to reload Synapse once in a while (`systemctl reload matrix-synapse`), so that newer certificates can kick in. Reloading doesn't cause any downtime."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:89
+msgid "Serving the Federation API with your certificates and another webserver"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:91
+msgid "**Alternatively**, if you are using another webserver, you can set up reverse-proxying for the `tcp/8448` port by yourself. Make sure to use the proper certificates for `example.com` (not for `matrix.example.com`) when serving the `tcp/8448` port."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:93
+msgid "As recommended in our [Fronting the integrated reverse-proxy webserver with another reverse-proxy](./configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) documentation section, we recommend you to expose the Matrix Federation entrypoint from traffic at a local port (e.g. `127.0.0.1:8449`), so your reverese-proxy should send traffic there."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/howto-srv-server-delegation.po b/i18n/locales/jp/LC_MESSAGES/docs/howto-srv-server-delegation.po
new file mode 100644
index 000000000..a97672f4a
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/howto-srv-server-delegation.po
@@ -0,0 +1,149 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/howto-srv-server-delegation.md:1
+msgid "Server Delegation via a DNS SRV record (advanced)"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:3
+msgid "**Reminder** : unless you are affected by the [Downsides of well-known-based Server Delegation](howto-server-delegation.md#downsides-of-well-known-based-server-delegation), we suggest you **stay on the simple/default path**: [Server Delegation](howto-server-delegation.md) by [configuring well-known files](configuring-well-known.md) at the base domain."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:5
+msgid "This guide is about configuring Server Delegation using DNS SRV records (for the [Traefik](https://doc.traefik.io/traefik/) webserver). This method has special requirements when it comes to SSL certificates, so various changes are required."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:7
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:9
+msgid "SRV delegation while still using the playbook provided Traefik to get / renew the certificate requires a wildcard certificate."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:11
+msgid "To obtain / renew one from [Let's Encrypt](https://letsencrypt.org/), one needs to use a [DNS-01 challenge](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) method instead of the default [HTTP-01](https://letsencrypt.org/docs/challenge-types/#http-01-challenge)."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:13
+msgid "This means that this is **limited to the list of DNS providers supported by Traefik**, unless you bring in your own certificate."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:15
+msgid "The up-to-date list can be accessed on [traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers)"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:17
+msgid "The changes"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:19
+msgid "**Note**: the changes below instruct you how to do this for a basic Synapse installation. You will need to adapt the variable name and the content of the labels:"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:21
+msgid "if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md) or [Dendrite](./configuring-playbook-dendrite.md))"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:22
+msgid "if you're using [Synapse with workers enabled](./configuring-playbook-synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled: true`). In that case, it's actually the `matrix-synapse-reverse-proxy-companion` service which has Traefik labels attached"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:24
+msgid "Also, all instructions below are from an older version of the playbook and may not work anymore."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:26
+msgid "Federation Endpoint"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:33
+msgid "This is because with SRV federation, some servers / tools (one of which being the federation tester) try to access the federation API using the resolved IP address instead of the domain name (or they are not using SNI). This change will make Traefik route all traffic for which the path match this rule go to the federation endpoint."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:35
+msgid "Tell Traefik which certificate to serve for the federation endpoint"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:37
+msgid "Now that the federation endpoint is not bound to a domain anymore we need to explicitely tell Traefik to use a wildcard certificate in addition to one containing the base name."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:39
+msgid "This is because the Matrix specification expects the federation endpoint to be served using a certificate compatible with the base domain, however, the other resources on the endpoint still need a valid certificate to work."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:48
+msgid "Configure the DNS-01 challenge for let's encrypt"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:50
+msgid "Since we're now requesting a wildcard certificate, we need to change the ACME challenge method. To request a wildcard certificate from Let's Encrypt we are required to use the DNS-01 challenge."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:52
+msgid "This will need 3 changes:"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:53
+msgid "Add a new certificate resolver that works with DNS-01"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:54
+msgid "Configure the resolver to allow access to the DNS zone to configure the records to answer the challenge (refer to [Traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers) to know which environment variables to set)"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:55
+msgid "Tell the playbook to use the new resolver as default"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:57
+msgid "We cannot just disable the default resolver as that would disable SSL in quite a few places in the playbook."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:86
+msgid "Adjust Coturn's configuration"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:88
+msgid "The last step is to alter the generated Coturn configuration."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:90
+msgid "By default, Coturn is configured to wait on the certificate for the `matrix.` subdomain using an [instantiated systemd service](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Service%20Templates) using the domain name as the parameter for this service. However, we need to serve the wildcard certificate, which is incompatible with systemd, it will try to expand the `*`, which will break and prevent Coturn from starting."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:92
+msgid "We also need to indicate to Coturn where the wildcard certificate is."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:94
+msgid "**⚠️ WARNING ⚠️** : On first start of the services, Coturn might still fail to start because Traefik is still in the process of obtaining the certificates. If you still get an error, make sure Traefik obtained the certificates and restart the Coturn service (`just start-group coturn`)."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:96
+msgid "This should not happen again afterwards as Traefik will renew certificates well before their expiry date, and the Coturn service is setup to restart periodically."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:122
+msgid "Full example of a working configuration"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/importing-postgres.po b/i18n/locales/jp/LC_MESSAGES/docs/importing-postgres.po
new file mode 100644
index 000000000..3fb66cefc
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/importing-postgres.po
@@ -0,0 +1,149 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/importing-postgres.md:1
+msgid "Importing an existing Postgres database from another installation (optional)"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:3
+msgid "Run this if you'd like to import your database from a previous installation. (don't forget to import your Synapse `media_store` files as well - see [the importing-synape-media-store guide](importing-synapse-media-store.md))."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:6
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:8
+msgid "For this to work, **the database name in Postgres must match** what this playbook uses. This playbook uses a Postgres database name of `synapse` by default (controlled by the `matrix_synapse_database_database` variable). If your database name differs, be sure to change `matrix_synapse_database_database` to your desired name and to re-run the playbook before proceeding."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:10
+msgid "The playbook supports importing Postgres dump files in **text** (e.g. `pg_dump > dump.sql`) or **gzipped** formats (e.g. `pg_dump | gzip -c > dump.sql.gz`). Importing multiple databases (as dumped by `pg_dumpall`) is also supported."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:12
+msgid "The migration might be a good moment, to \"reset\" a not properly working bridge. Be aware, that it might affect all users (new link to bridge, new rooms, …)"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:14
+msgid "Before doing the actual import, **you need to upload your Postgres dump file to the server** (any path is okay)."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:16
+msgid "Importing"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:18
+msgid "To import, run this command (make sure to replace `SERVER_PATH_TO_POSTGRES_DUMP_FILE` with a file path on your server):"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:26
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:28
+msgid "`SERVER_PATH_TO_POSTGRES_DUMP_FILE` must be a file path to a Postgres dump file on the server (not on your local machine!)"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:29
+msgid "`postgres_default_import_database` defaults to `matrix`, which is useful for importing multiple databases (for dumps made with `pg_dumpall`). If you're importing a single database (e.g. `synapse`), consider changing `postgres_default_import_database` accordingly"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:30
+msgid "after importing a large database, it's a good idea to run [an `ANALYZE` operation](https://www.postgresql.org/docs/current/sql-analyze.html) to make Postgres rebuild its database statistics and optimize its query planner. You can easily do this via the playbook by running `just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze` (see [Vacuuming PostgreSQL](maintenance-postgres.md#vacuuming-postgresql) for more details)."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:32
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:34
+msgid "Table Ownership"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:36
+msgid "A table ownership issue can occur if you are importing from a Synapse installation which was both:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:38
+msgid "migrated from SQLite to Postgres, and"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:39
+msgid "used a username other than 'synapse'"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:41
+msgid "In this case you may run into the following error during the import task:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:47
+msgid "where `synapse_user` is the database username from the previous Synapse installation."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:49
+msgid "This can be verified by examining the dump for ALTER TABLE statements which set OWNER TO that username:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:61
+msgid "It can be worked around by changing the username to `synapse`, for example by using `sed`:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:67
+msgid "This uses sed to perform an 'in-place' (`-i`) replacement globally (`/g`), searching for `synapse_user` and replacing with `synapse` (`s/synapse_user/synapse`). If your database username was different, change `synapse_user` to that username instead. Expand search/replace statement as shown in example above, in case of old user name like `matrix` - replacing `matrix` only would… well - you can imagine."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:69
+msgid "Note that if the previous import failed with an error it may have made changes which are incompatible with re-running the import task right away; if you do so it may fail with an error such as:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:75
+msgid "Repeat import"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:77
+msgid "In this case you can use the command suggested in the import task to clear the database before retrying the import:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:85
+msgid "Now on your local machine run `just run-tags setup-postgres` to prepare the database roles etc."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:87
+msgid "If not, you probably get this error. `synapse` is the correct table owner, but the role is missing in database."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:93
+msgid "Once the database is clear and the ownership of the tables has been fixed in the SQL file, the import task should succeed."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:95
+msgid "Check, if `--dbname` is set to `synapse` (not `matrix`) and replace paths (or even better, copy this line from your terminal)"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:101
+msgid "Hints"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:103
+msgid "To open psql terminal run `/matrix/postgres/bin/cli`"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-media-store.po b/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-media-store.po
new file mode 100644
index 000000000..e267284e4
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-media-store.po
@@ -0,0 +1,61 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/importing-synapse-media-store.md:1
+msgid "Importing `media_store` data files from an existing Synapse installation (optional)"
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:3
+msgid "Run this if you'd like to import your `media_store` files from a previous installation of Synapse."
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:5
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:7
+msgid "Before doing the actual data restore, **you need to upload your media store directory to the server** (any path is okay)."
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:9
+msgid "If you are [storing Matrix media files on Amazon S3](configuring-playbook-s3.md) (optional), restoring with this tool is not possible right now."
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:11
+msgid "As an alternative, you can perform a manual restore using the [AWS CLI tool](https://aws.amazon.com/cli/) (e.g. `aws s3 sync /path/to/server/media_store/. s3://name-of-bucket/`)"
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:13
+msgid "**Note for Mac users**: Due to case-sensitivity issues on certain Mac filesystems (HFS or HFS+), filename corruption may occur if you copy a `media_store` directory to your Mac. If you're transferring a `media_store` directory between 2 servers, make sure you do it directly (from server to server with a tool such as [rsync](https://rsync.samba.org/)), and not by downloading the files to your Mac."
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:15
+msgid "Importing"
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:17
+msgid "Run this command (make sure to replace `<server-path-to-media_store>` with a path on your server):"
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:23
+msgid "**Note**: `<server-path-to-media_store>` must be a file path to a `media_store` directory on the server (not on your local machine!)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-sqlite.po b/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-sqlite.po
new file mode 100644
index 000000000..7bc36c39e
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/importing-synapse-sqlite.po
@@ -0,0 +1,77 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/importing-synapse-sqlite.md:1
+msgid "Importing an existing SQLite database from another Synapse installation (optional)"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:3
+msgid "Run this if you'd like to import your database from a previous default installation of Synapse (don't forget to import your `media_store` files as well - see [the importing-synapse-media-store guide](importing-synapse-media-store.md))."
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:5
+msgid "While this playbook only supports running Synapse in combination with PostgreSQL, a Synapse instance installed manually usually defaults to using an SQLite database."
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:7
+msgid "If you have such a Synapse setup and wish to migrate it to one managed by the playbook (and over to PostgreSQL), this documentation page is for you."
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:11
+msgid "Before doing the actual import:"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:13
+msgid "**ensure you have NOT started Synapse yet**. That is, make sure you have followed the [Installing step](installing.md), but haven't run the playbook's `start` tag yet. If you had started your new Synapse instance, it may have already initialized your Postgres database and importing onto it may not work. In such cases, you may need to clean up the `synapse` database first."
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:14
+msgid "**ensure you have uploaded your SQLite database file to the server** (any path is okay)"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:15
+msgid "if you're using the integrated Postgres server (**by default, you are** using it, unless you've explicitly switched to [Using an external PostgreSQL server](configuring-playbook-external-postgres.md)), **make sure Postgres is started** by running `just start-group postgres`"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:17
+msgid "Importing"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:19
+msgid "Run this command (make sure to replace `<server-path-to-homeserver.db>` with a file path on your server):"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:25
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:27
+msgid "`<server-path-to-homeserver.db>` must be replaced with a file path to a `homeserver.db` **file on the server** (not on your local machine!)."
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:28
+msgid "if the SQLite database is from an older version of Synapse, the **importing procedure may run migrations on it to bring it up to date**. That is, your SQLite database file may get modified and become unusable with your older Synapse version. Keeping a copy of the original is probably wise."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/installing.po b/i18n/locales/jp/LC_MESSAGES/docs/installing.po
new file mode 100644
index 000000000..44dede432
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/installing.po
@@ -0,0 +1,305 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/installing.md:1
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/installing.md:3
+msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > Installing</sup>"
+msgstr ""
+
+#: ../../../docs/installing.md:5
+msgid "If you've configured your DNS records and the playbook, you can start the installation procedure."
+msgstr ""
+
+#: ../../../docs/installing.md:7
+msgid "Update Ansible roles"
+msgstr ""
+
+#: ../../../docs/installing.md:9
+msgid "Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside."
+msgstr ""
+
+#: ../../../docs/installing.md:11
+msgid "To update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file), run:"
+msgstr ""
+
+#: ../../../docs/installing.md:13
+msgid "either: `just update`"
+msgstr ""
+
+#: ../../../docs/installing.md:14
+msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)"
+msgstr ""
+
+#: ../../../docs/installing.md:16
+msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`"
+msgstr ""
+
+#: ../../../docs/installing.md:18
+msgid "For details about `just` commands, take a look at: [Running `just` commands](just.md)."
+msgstr ""
+
+#: ../../../docs/installing.md:20
+msgid "Install Matrix server and services"
+msgstr ""
+
+#: ../../../docs/installing.md:22
+msgid "The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks."
+msgstr ""
+
+#: ../../../docs/installing.md:24
+msgid "The general command syntax for installation (and also maintenance) is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`. It is recommended to get yourself familiar with the [playbook tags](playbook-tags.md) before proceeding."
+msgstr ""
+
+#: ../../../docs/installing.md:26
+msgid "If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the all Ansible commands."
+msgstr ""
+
+#: ../../../docs/installing.md:28
+msgid "If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to all Ansible commands."
+msgstr ""
+
+#: ../../../docs/installing.md:30
+msgid "There 2 ways to start the installation process - depending on whether you're [Installing a brand new server (without importing data)](#installing-a-brand-new-server-without-importing-data) or [Installing a server into which you'll import old data](#installing-a-server-into-which-youll-import-old-data)."
+msgstr ""
+
+#: ../../../docs/installing.md:32
+msgid "**Note**: if you are migrating from an old server to a new one, take a look at [this guide](maintenance-migrating.md) instead. This is an easier and more straightforward way than installing a server and importing old data into it."
+msgstr ""
+
+#: ../../../docs/installing.md:34
+msgid "Installing a brand new server (without importing data)"
+msgstr ""
+
+#: ../../../docs/installing.md:36
+msgid "If this is **a brand new** Matrix server and you **won't be importing old data into it**, run all these tags:"
+msgstr ""
+
+#: ../../../docs/installing.md:42
+msgid "This will do a full installation and start all Matrix services."
+msgstr ""
+
+#: ../../../docs/installing.md:44
+msgid "**Note**: if the command does not work as expected, make sure that you have properly installed and configured software required to run the playbook, as described on [Prerequisites](prerequisites.md)."
+msgstr ""
+
+#: ../../../docs/installing.md:46
+msgid "Installing a server into which you'll import old data"
+msgstr ""
+
+#: ../../../docs/installing.md:48
+msgid "If you will be importing data into your newly created Matrix server, install it, but **do not** start its services just yet. Starting its services or messing with its database now will affect your data import later on."
+msgstr ""
+
+#: ../../../docs/installing.md:50
+msgid "To do the installation **without** starting services, run `ansible-playbook` with the `install-all` tag only:"
+msgstr ""
+
+#: ../../../docs/installing.md:56
+msgid "⚠️ **Warning**: do not run the just \"recipe\" `just install-all` instead, because it automatically starts services at the end of execution. See: [Difference between playbook tags and shortcuts](just.md#difference-between-playbook-tags-and-shortcuts)"
+msgstr ""
+
+#: ../../../docs/installing.md:58
+msgid "When this command completes, services won't be running yet."
+msgstr ""
+
+#: ../../../docs/installing.md:60
+msgid "You can now:"
+msgstr ""
+
+#: ../../../docs/installing.md:62
+msgid "[Importing an existing SQLite database (from another Synapse installation)](importing-synapse-sqlite.md) (optional)"
+msgstr ""
+
+#: ../../../docs/installing.md:64
+msgid "[Importing an existing Postgres database (from another installation)](importing-postgres.md) (optional)"
+msgstr ""
+
+#: ../../../docs/installing.md:66
+msgid "[Importing `media_store` data files from an existing Synapse installation](importing-synapse-media-store.md) (optional)"
+msgstr ""
+
+#: ../../../docs/installing.md:68
+msgid ".. and then proceed to starting all services:"
+msgstr ""
+
+#: ../../../docs/installing.md:74
+msgid "Create your user account"
+msgstr ""
+
+#: ../../../docs/installing.md:76
+msgid "ℹ️ *You can skip this step if you have installed a server and imported old data to it.*"
+msgstr ""
+
+#: ../../../docs/installing.md:78
+msgid "As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server."
+msgstr ""
+
+#: ../../../docs/installing.md:80
+msgid "After creating the user account, you can log in to it with [Element Web](configuring-playbook-client-element-web.md) that this playbook has installed for you at this URL: `https://element.example.com/`."
+msgstr ""
+
+#: ../../../docs/installing.md:82
+msgid "To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer."
+msgstr ""
+
+#: ../../../docs/installing.md:84
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/installing.md:85
+msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`"
+msgstr ""
+
+#: ../../../docs/installing.md:86
+msgid "For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)"
+msgstr ""
+
+#: ../../../docs/installing.md:87
+msgid "Use `admin=yes` to make your user account an administrator of the Matrix server"
+msgstr ""
+
+#: ../../../docs/installing.md:95
+msgid "Feel free to create as many accounts (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your account only (with `admin=yes`), and others should be created with `admin=no`."
+msgstr ""
+
+#: ../../../docs/installing.md:97
+msgid "For more information, see the documentation for [registering users](registering-users.md)."
+msgstr ""
+
+#: ../../../docs/installing.md:99
+msgid "Finalize the installation"
+msgstr ""
+
+#: ../../../docs/installing.md:101
+msgid "Now you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network."
+msgstr ""
+
+#: ../../../docs/installing.md:103
+msgid "This is required for federation to work! Without a proper configuration, your server will effectively not be part of the Matrix network."
+msgstr ""
+
+#: ../../../docs/installing.md:105
+msgid "To configure the delegation, you have these two options. Choose one of them according to your situation."
+msgstr ""
+
+#: ../../../docs/installing.md:107
+msgid "If you can afford to point the base domain at the Matrix server, follow the instructions below which guide you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server. It will enable you to use a Matrix user ID like `@alice:example.com` while hosting services on a subdomain like `matrix.example.com`."
+msgstr ""
+
+#: ../../../docs/installing.md:108
+msgid "Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot \"serve the base domain\" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server), but feel free to familiarize yourself with all [server delegation (redirection) options](howto-server-delegation.md)."
+msgstr ""
+
+#: ../../../docs/installing.md:110
+msgid "To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/installing.md:116
+msgid "After configuring the playbook, run the command below:"
+msgstr ""
+
+#: ../../../docs/installing.md:122
+msgid "Things to do next"
+msgstr ""
+
+#: ../../../docs/installing.md:124
+msgid "After finilizing the installation, you can:"
+msgstr ""
+
+#: ../../../docs/installing.md:126
+msgid "[check if services work](maintenance-checking-services.md)"
+msgstr ""
+
+#: ../../../docs/installing.md:127
+msgid "or [set up additional services](configuring-playbook.md#other-configuration-options) (bridges to other chat networks, bots, etc.)"
+msgstr ""
+
+#: ../../../docs/installing.md:128
+msgid "or learn how to [upgrade services when new versions are released](maintenance-upgrading-services.md)"
+msgstr ""
+
+#: ../../../docs/installing.md:129
+msgid "or learn how to [maintain your server](faq.md#maintenance)"
+msgstr ""
+
+#: ../../../docs/installing.md:130
+msgid "or join some Matrix rooms:"
+msgstr ""
+
+#: ../../../docs/installing.md:131
+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."
+msgstr ""
+
+#: ../../../docs/installing.md:132
+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:133
+msgid "or help make this playbook better by contributing (code, documentation, or [coffee/beer](https://liberapay.com/s.pantaleev/donate))"
+msgstr ""
+
+#: ../../../docs/installing.md:135
+msgid "Maintaining your setup in the future"
+msgstr ""
+
+#: ../../../docs/installing.md:137
+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:139
+msgid "The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities."
+msgstr ""
+
+#: ../../../docs/installing.md:141
+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:143
+msgid "For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)"
+msgstr ""
+
+#: ../../../docs/installing.md:145
+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:151
+msgid "**Note**: see [this page on the playbook tags](playbook-tags.md) for more information about those tags."
+msgstr ""
+
+#: ../../../docs/installing.md:153
+msgid "Make full use of `just` shortcut commands"
+msgstr ""
+
+#: ../../../docs/installing.md:155
+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:157
+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:159
+msgid "You can learn about the shortcut commands on this page: [Running `just` commands](just.md)"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/just.po b/i18n/locales/jp/LC_MESSAGES/docs/just.po
new file mode 100644
index 000000000..5db4caac8
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/just.po
@@ -0,0 +1,161 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/just.md:1
+msgid "Running `just` commands"
+msgstr ""
+
+#: ../../../docs/just.md:3
+msgid "We have previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers [`ansible-galaxy`](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html)). Our [`Makefile`](../Makefile) is still around, and you can still run these commands."
+msgstr ""
+
+#: ../../../docs/just.md:5
+msgid "In addition, we have added support for running commands via [`just`](https://github.com/casey/just) - a more modern command-runner alternative to `make`. It can be used to invoke `ansible-playbook` commands with less typing."
+msgstr ""
+
+#: ../../../docs/just.md:7
+msgid "The `just` utility executes shortcut commands (called as \"recipes\"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile). Most of the just recipes have no corresponding `Makefile` targets."
+msgstr ""
+
+#: ../../../docs/just.md:9
+msgid "For some recipes such as `just update`, our `justfile` recommends installing [`agru`](https://github.com/etkecc/agru) (a faster alternative to `ansible-galaxy`) to speed up the process."
+msgstr ""
+
+#: ../../../docs/just.md:11
+msgid "Here are some examples of shortcuts:"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Shortcut"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Result"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just roles`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Install the necessary Ansible roles pinned in [`requirements.yml`](../requirements.yml)"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just update`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Run `git pull` (to update the playbook) and install the Ansible roles"
+msgstr ""
+
+#: ../../../docs/just.md ../../../docs/just.md:33
+msgid "`just install-all`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just setup-all`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just install-all --ask-vault-pass`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Run commands with additional arguments (`--ask-vault-pass` will be appended to the above installation command)"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just run-tags install-mautrix-slack,start`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Run specific playbook tags (here `install-mautrix-slack` and `start`)"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just install-service mautrix-slack`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Run `just run-tags install-mautrix-slack,start` with even less typing"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just start-all`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "(Re-)starts all services"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just stop-group postgres`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Stop only the Postgres service"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "`just register-user alice secret-password yes`"
+msgstr ""
+
+#: ../../../docs/just.md
+msgid "Registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)"
+msgstr ""
+
+#: ../../../docs/just.md:26
+msgid "While [our documentation on prerequisites](prerequisites.md) lists `just` as one of the requirements for installation, using `just` is optional. If you find it difficult to install it, do not find it useful, or want to prefer raw `ansible-playbook` commands for some reason, feel free to run all commands manually. For example, you can run `ansible-galaxy` directly to install the Ansible roles: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`."
+msgstr ""
+
+#: ../../../docs/just.md:28
+msgid "Difference between playbook tags and shortcuts"
+msgstr ""
+
+#: ../../../docs/just.md:30
+msgid "It is worth noting that `just` \"recipes\" are different from [playbook tags](playbook-tags.md). The recipes are shortcuts of commands defined in `justfile` and can be executed by the `just` program only, while the playbook tags are available for the raw `ansible-playbook` commands as well. Please be careful not to confuse them."
+msgstr ""
+
+#: ../../../docs/just.md:32
+msgid "For example, these two commands are different:"
+msgstr ""
+
+#: ../../../docs/just.md:34
+msgid "`ansible-playbook -i inventory/hosts setup.yml --tags=install-all`"
+msgstr ""
+
+#: ../../../docs/just.md:36
+msgid "The just recipe runs `ensure-matrix-users-created` and `start` tags after `install-all`, while the latter runs only `install-all` tag. The correct shortcut of the latter is `just run-tags install-all`."
+msgstr ""
+
+#: ../../../docs/just.md:38
+msgid "Such kind of difference sometimes matters. For example, when you install a Matrix server into which you will import old data (see [here](installing.md#installing-a-server-into-which-youll-import-old-data)), you are not supposed to run `just install-all` or `just setup-all`, because these commands start services immediately after installing components which may prevent your from importing old data."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-and-troubleshooting.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-and-troubleshooting.po
new file mode 100644
index 000000000..0f39a05f2
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-and-troubleshooting.po
@@ -0,0 +1,93 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/maintenance-and-troubleshooting.md:1
+msgid "Maintenance and Troubleshooting"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:3
+msgid "How to see the current status of your services"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:5
+msgid "You can check the status of your services by using `systemctl status`. Example:"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:15
+msgid "Docker containers that the playbook configures are supervised by [systemd](https://wiki.archlinux.org/title/Systemd) and their logs are configured to go to [systemd-journald](https://wiki.archlinux.org/title/Systemd/Journal)."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:17
+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`."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:19
+msgid "To view systemd-journald logs using [journalctl](https://man.archlinux.org/man/journalctl.1), run a command like this:"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:25
+msgid "Increasing Synapse logging"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:27
+msgid "Because the [Synapse](https://github.com/element-hq/synapse) Matrix server 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/maintenance-and-troubleshooting.md:29
+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 increasing the logging level to `INFO`."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:31
+msgid "Example configuration (`inventory/host_vars/matrix.example.com/vars.yml`):"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:39
+msgid "Re-run the playbook after making these configuration changes."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:41
+msgid "Remove unused Docker data"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:43
+msgid "You can free some disk space from Docker, see [docker system prune](https://docs.docker.com/engine/reference/commandline/system_prune/) for more information."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:49
+msgid "The shortcut command with `just` program is also available: `just run-tags run-docker-prune`"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:51
+msgid "Postgres"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:53
+msgid "See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) documentation page."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:55
+msgid "Ma1sd"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:57
+msgid "See the dedicated [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md) documentation page."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-checking-services.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-checking-services.po
new file mode 100644
index 000000000..025ea7aa4
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-checking-services.po
@@ -0,0 +1,45 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/maintenance-checking-services.md:1
+msgid "Checking if services work"
+msgstr ""
+
+#: ../../../docs/maintenance-checking-services.md:3
+msgid "This playbook can perform a check to ensure that you've configured things correctly and that services are running."
+msgstr ""
+
+#: ../../../docs/maintenance-checking-services.md:5
+msgid "To perform the check, run:"
+msgstr ""
+
+#: ../../../docs/maintenance-checking-services.md:11
+msgid "The shortcut command with `just` program is also available: `just run-tags self-check`"
+msgstr ""
+
+#: ../../../docs/maintenance-checking-services.md:13
+msgid "If it's all green, everything is probably running correctly."
+msgstr ""
+
+#: ../../../docs/maintenance-checking-services.md:15
+msgid "Besides this self-check, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-migrating.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-migrating.po
new file mode 100644
index 000000000..77987e292
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-migrating.po
@@ -0,0 +1,137 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/maintenance-migrating.md:1
+msgid "Migrating to new server"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:3
+msgid "This documentation explains how to migrate your Matrix services (server, client, bridges, etc.) and data **from an old server to a new server**."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:5
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:6
+msgid "This migration guide is applicable if you migrate from one server to another server having the same CPU architecture (e.g. both servers being `amd64`)."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:8
+msgid "If you're trying to migrate between different architectures (e.g. `amd64` --> `arm64`), simply copying the complete `/matrix` directory is **not** possible as it would move the raw PostgreSQL data (`/matrix/postgres/data`) between different architectures. In this specific case, you can use the guide below as a reference, but you would also need to avoid syncing `/matrix/postgres/data` to the new host, and also dump the database on your current server and import it properly on the new server. See our [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql) docs for help with PostgreSQL backup/restore."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:9
+msgid "If you have any questions about migration or encountered an issue during migration, do not hesitate to ask for help on [our Matrix room](https://matrix.to/#/%23matrix-docker-ansible-deploy:devture.com). You probably might want to prepare a temporary/sub account on another Matrix server in case it becomes impossible to use your server due to migration failure by any chance."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:11
+msgid "You can't change the domain (specified in the `matrix_domain` variable) after the initial deployment."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:13
+msgid "Lower DNS TTL"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:15
+msgid "Prepare by lowering DNS TTL for your domains (`matrix.example.com`, etc.), so that DNS record changes would happen faster, leading to less downtime."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:17
+msgid "Stop services on the old server completely"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:19
+msgid "Before migrating, you need to stop all services on the old server and make sure they won't be starting again."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:21
+msgid "To do so, it is recommended to run the `systemctl` command on the server. Running the playbook's `stop` tag also stops the services, but just once; they will start again if you reboot the server."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:23
+msgid "Log in to the old server and run the command as `root` (or a user that can run it with `sudo`):"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:29
+msgid "Copy data directory to the new server"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:31
+msgid "After you've confirmed that all services were stopped, copy the `/matrix` directory from the old server to the new server. When copying, make sure to preserve ownership and permissions (use `cp -p` or `rsync -ar`)!"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:33
+msgid "Adjust DNS records"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:35
+msgid "Make sure your DNS records are adjusted to point to the new server's IP address."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:37
+msgid "Update `inventory/hosts` file"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:39
+msgid "Having adjusted DNS records, replace the old server's external IP address on the `inventory/hosts` file with that of the new server."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:41
+msgid "Create `matrix` user and group on the new server"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:43
+msgid "Then, run the command below on your local computer to create the `matrix` user and group on the new server:"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:49
+msgid "The shortcut command with `just` program is also available: `just run-tags setup-system-user`"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:51
+msgid "**Note**: because the `matrix` user and group are created dynamically on each server, the user/group ID may differ between the old and new server. We suggest that you adjust ownership of `/matrix` files. To adjust the ownership, log in to the new server and run the command:"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:57
+msgid "Install and start all services on the new server"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:59
+msgid "Finally, run the command below on your local computer to finish the installation and start all services:"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:65
+msgid "The shortcut command with `just` program is also available: `just run-tags install-all,start`"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:67
+msgid "Check if services work"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:69
+msgid "After starting the services, you probably might want to ensure that you've migrated things correctly and that services are running. For instructions, see: [check if services work](maintenance-checking-services.md)"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:71
+msgid "Having make sure that both services and federation work as expected, you can safely shutdown the old server."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-postgres.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-postgres.po
new file mode 100644
index 000000000..ff051ce43
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-postgres.po
@@ -0,0 +1,221 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/maintenance-postgres.md:1
+msgid "PostgreSQL maintenance"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:3
+msgid "This document shows you how to perform various maintenance tasks related to the Postgres database server used by Matrix."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:5
+msgid "Table of contents:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:7
+msgid "[Getting a database terminal](#getting-a-database-terminal), for when you wish to execute SQL queries"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:9
+msgid "[Vacuuming PostgreSQL](#vacuuming-postgresql), for when you wish to run a Postgres [VACUUM](https://www.postgresql.org/docs/current/sql-vacuum.html) (optimizing disk space)"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:11
+msgid "[Backing up PostgreSQL](#backing-up-postgresql), for when you wish to make a backup"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:13
+msgid "[Upgrading PostgreSQL](#upgrading-postgresql), for upgrading to new major versions of PostgreSQL. Such **manual upgrades are sometimes required**."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:15
+msgid "[Tuning PostgreSQL](#tuning-postgresql) to make it run faster"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:17
+msgid "Getting a database terminal"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:19
+msgid "You can use the `/matrix/postgres/bin/cli` tool to get interactive terminal access ([psql](https://www.postgresql.org/docs/11/app-psql.html)) to the PostgreSQL server."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:21
+msgid "If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above tool will not be available."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:23
+msgid "By default, this tool puts you in the `matrix` database, which contains nothing."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:25
+msgid "To see the available databases, run `\\list` (or just `\\l`)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:27
+msgid "To change to another database (for example `synapse`), run `\\connect synapse` (or just `\\c synapse`)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:29
+msgid "You can then proceed to write queries. Example: `SELECT COUNT(*) FROM users;`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:31
+msgid "**Be careful**. Modifying the database directly (especially as services are running) is dangerous and may lead to irreversible database corruption. When in doubt, consider [making a backup](#backing-up-postgresql)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:33
+msgid "Vacuuming PostgreSQL"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:35
+msgid "Deleting lots data from Postgres does not make it release disk space, until you perform a [`VACUUM` operation](https://www.postgresql.org/docs/current/sql-vacuum.html)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:37
+msgid "You can run different `VACUUM` operations via the playbook, with the default preset being `vacuum-complete`:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:39
+msgid "(default) `vacuum-complete`: stops all services temporarily and runs `VACUUM FULL VERBOSE ANALYZE`."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:40
+msgid "`vacuum-full`: stops all services temporarily and runs `VACUUM FULL VERBOSE`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:41
+msgid "`vacuum`: runs `VACUUM VERBOSE` without stopping any services"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:42
+msgid "`vacuum-analyze` runs `VACUUM VERBOSE ANALYZE` without stopping any services"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:43
+msgid "`analyze` runs `ANALYZE VERBOSE` without stopping any services (this is just [ANALYZE](https://www.postgresql.org/docs/current/sql-analyze.html) without doing a vacuum, so it's faster)"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:45
+msgid "**Note**: for the `vacuum-complete` and `vacuum-full` presets, you'll need plenty of available disk space in your Postgres data directory (usually `/matrix/postgres/data`). These presets also stop all services (e.g. Synapse, etc.) while the vacuum operation is running."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:47
+msgid "Example playbook invocations:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:49
+msgid "`just run-tags run-postgres-vacuum`: runs the default `vacuum-complete` preset and restarts all services"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:50
+msgid "`just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze`: runs the `analyze` preset with all services remaining operational at all times"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:52
+msgid "Backing up PostgreSQL"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:54
+msgid "To automatically make Postgres database backups on a fixed schedule, see [Setting up postgres backup](configuring-playbook-postgres-backup.md)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:56
+msgid "To make a one off back up of the current PostgreSQL database, make sure it's running and then execute a command like this on the server:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:67
+msgid "If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above command will not work, because neither the credentials file (`/matrix/postgres/env-postgres-psql`), nor the `matrix-postgres` container is available."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:69
+msgid "Restoring a backup made this way can be done by [importing it](importing-postgres.md)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:71
+msgid "Upgrading PostgreSQL"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:73
+msgid "Unless you are using an [external Postgres server](configuring-playbook-external-postgres.md), this playbook initially installs Postgres for you."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:75
+msgid "Once installed, the playbook attempts to preserve the Postgres version it starts with. This is because newer Postgres versions cannot start with data generated by older Postgres versions."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:77
+msgid "Upgrades must be performed manually."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:79
+msgid "This playbook can upgrade your existing Postgres setup with the following command:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:85
+msgid "**The old Postgres data directory is backed up** automatically, by renaming it to `/matrix/postgres/data-auto-upgrade-backup`. To rename to a different path, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_auto_upgrade_backup_data_path=/another/disk/matrix-postgres-before-upgrade\"`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:87
+msgid "The auto-upgrade-backup directory stays around forever, until you **manually decide to delete it**."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:89
+msgid "As part of the upgrade, the database is dumped to `/tmp`, an upgraded and empty Postgres server is started, and then the dump is restored into the new server. To use a different directory for the dump, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_dump_dir=/directory/to/dump/here\"`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:91
+msgid "To save disk space in `/tmp`, the dump file is gzipped on the fly at the expense of CPU usage. If you have plenty of space in `/tmp` and would rather avoid gzipping, you can explicitly pass a dump filename which doesn't end in `.gz`. Example: `--extra-vars=\"postgres_dump_name=matrix-postgres-dump.sql\"`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:93
+msgid "**All databases, roles, etc. on the Postgres server are migrated**."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:95
+msgid "Tuning PostgreSQL"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:97
+msgid "PostgreSQL can be [tuned](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) to make it run faster. This is done by passing extra arguments to the Postgres process."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:99
+msgid "The [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) **already does some tuning by default**, which matches the [tuning logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) done by websites like https://pgtune.leopard.in.ua/. You can manually influence some of the tuning variables. These parameters (variables) are injected via the `postgres_postgres_process_extra_arguments_auto` variable."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:101
+msgid "Most users should be fine with the automatically-done tuning. However, you may wish to:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:103
+msgid "**adjust the automatically-determined tuning parameters manually**: change the values for the tuning variables defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) (see `postgres_max_connections`, `postgres_data_storage` etc). These variables are ultimately passed to Postgres via a `postgres_postgres_process_extra_arguments_auto` variable"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:105
+msgid "**turn automatically-performed tuning off**: override it like this: `postgres_postgres_process_extra_arguments_auto: []`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:107
+msgid "**add additional tuning parameters**: define your additional Postgres configuration parameters in `postgres_postgres_process_extra_arguments_custom`. See `postgres_postgres_process_extra_arguments_auto` defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) for inspiration"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-synapse.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-synapse.po
new file mode 100644
index 000000000..92a7ac762
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-synapse.po
@@ -0,0 +1,201 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/maintenance-synapse.md:1
+msgid "Synapse maintenance"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:3
+msgid "This document shows you how to perform various maintenance tasks related to the Synapse chat server."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:5
+msgid "Table of contents:"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:7
+msgid "[Purging old data with the Purge History API](#purging-old-data-with-the-purge-history-api), for when you wish to delete in-use (but old) data from the Synapse database"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:9
+msgid "[Compressing state with rust-synapse-compress-state](#compressing-state-with-rust-synapse-compress-state)"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:11
+msgid "[Browse and manipulate the database](#browse-and-manipulate-the-database), for when you really need to take matters into your own hands"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:13
+msgid "[Make Synapse faster](#make-synapse-faster)"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:15
+msgid "Purging old data with the Purge History API"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:17
+msgid "You can use the **[Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md)** to delete old messages on a per-room basis. **This is destructive** (especially for non-federated rooms), because it means **people will no longer have access to history past a certain point**."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:19
+msgid "To make use of this Synapse Admin API, **you'll need an admin access token** first. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:21
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:23
+msgid "Synapse's Admin API is not exposed to the internet by default, following [official Synapse reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints). To expose it you will need to add `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` to your `vars.yml` file."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:25
+msgid "Follow the [Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md) documentation page for the actual purging instructions."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:27
+msgid "After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:29
+msgid "Compressing state with rust-synapse-compress-state"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:31
+msgid "[rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) can be used to optimize some `_state` tables used by Synapse. If your server participates in large rooms this is the most effective way to reduce the size of your database."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:33
+msgid "**Note**: besides running the `rust-synapse-compress-state` tool manually, you can also enable its `synapse-auto-compressor` tool by [Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md). The automatic tool will run on a schedule every day and you won't have to compress state manually ever again."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:35
+msgid "`rust-synapse-compress-state` should be safe to use (even when Synapse is running), but it's always a good idea to [make Postgres backups](./maintenance-postgres.md#backing-up-postgresql) first."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:37
+msgid "To ask the playbook to run rust-synapse-compress-state, execute:"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:43
+msgid "The shortcut command with `just` program is also available: `just run-tags rust-synapse-compress-state`"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:45
+msgid "By default, all rooms with more than `100000` state group rows will be compressed. If you need to adjust this, pass: `--extra-vars='matrix_synapse_rust_synapse_compress_state_min_state_groups_required=SOME_NUMBER_HERE'` to the command above."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:47
+msgid "After state compression, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:49
+msgid "Browse and manipulate the database"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:51
+msgid "When the [Synapse Admin API](https://github.com/element-hq/synapse/tree/master/docs/admin_api) and the other tools do not provide a more convenient way, having a look at synapse's postgresql database can satisfy a lot of admins' needs."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:53
+msgid "Editing the database manually is not recommended or supported by the Synapse developers. If you are going to do so you should [make a database backup](./maintenance-postgres.md#backing-up-postgresql)."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:55
+msgid "First, set up an SSH tunnel to your Matrix server (skip if it is your local machine):"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:62
+msgid "Then start up an ephemeral [adminer](https://www.adminer.org/) container on the Matrix server, connecting it to the `matrix` network and linking the postgresql container:"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:68
+msgid "You should then be able to browse the adminer database administration GUI at http://localhost:1799/ after entering your DB credentials (found in the `host_vars` or on the server in `{{matrix_synapse_config_dir_path}}/homeserver.yaml` under `database.args`)"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:70
+msgid "⚠️️ Be **very careful** with this, there is **no undo** for impromptu DB operations."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:72
+msgid "Make Synapse faster"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:74
+msgid "Synapse's presence feature which tracks which users are online and which are offline can use a lot of processing power. You can disable presence by adding `matrix_synapse_presence_enabled: false` to your `vars.yml` file."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:76
+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:78
+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:80
+msgid "Tuning caches and cache autotuning"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:82
+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:84
+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:86
+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:88
+msgid "Cache autotuning is **enabled by default** and controlled via the following variables:"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:90
+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:91
+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:92
+msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:94
+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:96
+msgid "To **disable cache auto-tuning**, unset all values:"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:104
+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:106
+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 ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/maintenance-upgrading-services.po b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-upgrading-services.po
new file mode 100644
index 000000000..e73b0da3e
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/maintenance-upgrading-services.po
@@ -0,0 +1,129 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/maintenance-upgrading-services.md:1
+msgid "Upgrading the Matrix services"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:3
+msgid "This playbook not only installs the various Matrix services for you, but can also upgrade them as new versions are made available."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:5
+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/maintenance-upgrading-services.md:7
+msgid "The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities (for example, see [here](https://github.com/element-hq/element-web/security) for known ones on Element Web)."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:9
+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/maintenance-upgrading-services.md:11
+msgid "The developers of this playbook strive to maintain the playbook updated, so that you can re-run the playbook to address such vulnerabilities. It is **your responsibility** to keep your server and the services on it up-to-date."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:13
+msgid "If you want to be notified when new versions of Synapse are released, you should join the Synapse Homeowners room: [#homeowners:matrix.org](https://matrix.to/#/#homeowners:matrix.org)."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:15
+msgid "Steps to upgrade the Matrix services"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:17
+msgid "Check the changelog"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:19
+msgid "Before updating the playbook and the Ansible roles in the playbook, take a look at [the changelog](../CHANGELOG.md) to see if there have been any backward-incompatible changes that you need to take care of."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:21
+msgid "Update the playbook and the Ansible roles"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:23
+msgid "If it looks good to you, go to the `matrix-docker-ansible-deploy` directory, update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file) by running:"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:25
+msgid "either: `just update`"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:26
+msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:28
+msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:30
+msgid "**Note**: for details about `just` commands, take a look at: [Running `just` commands](just.md)."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:32
+msgid "Re-run the playbook setup"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:34
+msgid "After updating the Ansible roles, then re-run the [playbook setup](installing.md#maintaining-your-setup-in-the-future) and restart all services:"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:40
+msgid "If you remove components from `vars.yml`, or if we switch some component from being installed by default to not being installed by default anymore, you'd need to run the setup command with the `setup-all` tag as below:"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:46
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:48
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account, if any."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:50
+msgid "Our estimation is that running `--tags=install-all,start` is approximately from **2 to 5 times faster** than running `setup-all,ensure-matrix-users-created,start`. See [this entry](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) on `CHANGELOG.md` for more information."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:52
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`. Note these shortcuts run the `ensure-matrix-users-created` tag too."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:54
+msgid "See [this page on the playbook tags](playbook-tags.md) for more information about those tags."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:56
+msgid "PostgreSQL major version upgrade"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:58
+msgid "Major version upgrades to the internal PostgreSQL database are not done automatically. Upgrades must be performed manually."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:60
+msgid "For details about upgrading it, refer to the [upgrading PostgreSQL guide](maintenance-postgres.md#upgrading-postgresql)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/obtaining-access-tokens.po b/i18n/locales/jp/LC_MESSAGES/docs/obtaining-access-tokens.po
new file mode 100644
index 000000000..9eda037b9
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/obtaining-access-tokens.po
@@ -0,0 +1,97 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-28 10:25+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/obtaining-access-tokens.md:1
+msgid "Obtaining an Access Token"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:3
+msgid "When setting up some optional features like bots and bridges you will need to provide an access token for some user. This document provides documentation on how to obtain such an access token."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:5
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:7
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:9
+msgid "The user for whom you want to obtain an access token needs to already exist. You can use this playbook to [register a new user](registering-users.md), if you have not already."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:11
+msgid "Below, we describe 2 ways to generate an access token for a user - using [Element Web](#obtain-an-access-token-via-element-web) or [curl](#obtain-an-access-token-via-curl). For both ways you need the user's password."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:13
+msgid "Obtain an access token via Element Web"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:15
+msgid "In a private browsing session (incognito window), open Element Web."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:16
+msgid "Log in with the user's credentials."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:17
+msgid "In the settings page, choose \"Help & About\", scroll down to the bottom and expand the `Access Token` section (see screenshot below)."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:18
+msgid "Copy the access token to your configuration."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:19
+msgid "Close the private browsing session. **Do not log out**. Logging out will invalidate the token, making it not work."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:21
+msgid "![Obtaining an access token with Element Web](assets/obtain_admin_access_token_element_web.png)"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:21
+msgid "Obtaining an access token with Element Web"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:23
+msgid "Obtain an access token via curl"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:25
+msgid "You can use the following command to get an access token for your user directly from the [Matrix Client-Server API](https://www.matrix.org/docs/guides/client-server-api#login):"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:35
+msgid "Change `USERNAME`, `PASSWORD`, and `example.com` accordingly."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:37
+msgid "`YOURDEVICEID` is optional and can be used to more easily identify the session later. When omitted (mind the commas in the JSON payload if you'll be omitting it), a random device ID will be generated."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:39
+msgid "Your response will look like this (prettified):"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/playbook-tags.po b/i18n/locales/jp/LC_MESSAGES/docs/playbook-tags.po
new file mode 100644
index 000000000..7f7923611
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/playbook-tags.po
@@ -0,0 +1,77 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/playbook-tags.md:1
+msgid "Playbook tags"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:3
+msgid "The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks."
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:5
+msgid "The general command syntax is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:7
+msgid "Here are some playbook tags that you should be familiar with:"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:9
+msgid "`setup-all` - runs all setup tasks (installation and uninstallation) for all components, but does not start/restart services"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:11
+msgid "`install-all` - like `setup-all`, but skips uninstallation tasks. Useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove components, you'd need to run `setup-all` though, or these components will still remain installed"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:13
+msgid "`setup-SERVICE` (e.g. `setup-postmoogle`) - runs the setup tasks only for a given role, but does not start/restart services. You can discover these additional tags in each role (`roles/**/tasks/main.yml`). Running per-component setup tasks is **not recommended**, as components sometimes depend on each other and running just the setup tasks for a given component may not be enough. For example, setting up the [mautrix-telegram bridge](configuring-playbook-bridge-mautrix-telegram.md), in addition to the `setup-mautrix-telegram` tag, requires database changes (the `setup-postgres` tag) as well as reverse-proxy changes (the `setup-nginx-proxy` tag)."
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:15
+msgid "`install-SERVICE` (e.g. `install-postmoogle`) - like `setup-SERVICE`, but skips uninstallation tasks. See `install-all` above for additional information."
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:17
+msgid "`start` - starts all systemd services and makes them start automatically in the future"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:19
+msgid "`stop` - stops all systemd services"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:21
+msgid "`ensure-matrix-users-created` - a special tag which ensures that all special users needed by the playbook (for bots, etc.) are created"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:23
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:24
+msgid "`setup-*` tags and `install-*` tags **do not start services** automatically, because you may wish to do things before starting services, such as importing a database dump, restoring data from another server, etc."
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:25
+msgid "Please be careful not to confuse the playbook tags with the `just` shortcut commands (\"recipes\"). For details about `just` commands, see: [Running `just` commands](just.md)"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/prerequisites.po b/i18n/locales/jp/LC_MESSAGES/docs/prerequisites.po
new file mode 100644
index 000000000..6192e8a8c
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/prerequisites.po
@@ -0,0 +1,165 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/prerequisites.md:1
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:3
+msgid "<sup>Prerequisites > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)</sup>"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:5
+msgid "To install Matrix services using this Ansible playbook, you need to prepare several requirements both on your local computer (where you will run the playbook to configure the server) and the server (where the playbook will install the Matrix services for you). **These requirements need to be set up manually** before proceeding to the next step."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:7
+msgid "We will be using `example.com` as the domain in the following instruction. Please remember to replace it with your own domain before running any commands."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:9
+msgid "**Note**: if you do not have an existing Matrix server and want to start quickly with \"opinionated defaults\", we suggest you to follow ⚡ **[Quick start](quick-start.md)** installation guide."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:11
+msgid "Your local computer"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:13
+msgid "[Ansible](http://ansible.com/) program. It's used to run this playbook and configures your server for you. Take a look at [our guide about Ansible](ansible.md) for more information, as well as [version requirements](ansible.md#supported-ansible-versions) and alternative ways to run Ansible."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:15
+msgid "[passlib](https://passlib.readthedocs.io/en/stable/index.html) Python library. See [this official documentation](https://passlib.readthedocs.io/en/stable/install.html#installation-instructions) for an instruction to install it. On most distros, you need to install some `python-passlib` or `py3-passlib` package, etc."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:17
+msgid "[`git`](https://git-scm.com/) as the recommended way to download the playbook. `git` may also be required on the server if you will be [self-building](self-building.md) components."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:19
+msgid "[`just`](https://github.com/casey/just) for running `just roles`, `just update`, etc. (see [`justfile`](../justfile)), although you can also run these commands manually. Take at look at this documentation for more information: [Running `just` commands](just.md)."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:21
+msgid "Strong password (random strings) generator. The playbook often requires you to create a strong password and use it for settings on `vars.yml`, components, etc. As any tools should be fine, this playbook has adopted [`pwgen`](https://linux.die.net/man/1/pwgen) (running `pwgen -s 64 1`). [Password Tech](https://pwgen-win.sourceforge.io/), formerly known as \"PWGen for Windows\", is available as free and open source password generator for Windows. Generally, using a random generator available on the internet is not recommended."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:23
+msgid "Server"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:25
+msgid "(Recommended) An **x86** server ([What kind of server specs do I need?](faq.md#what-kind-of-server-specs-do-i-need)) running one of these operating systems that make use of [systemd](https://systemd.io/):"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:26
+msgid "**Archlinux**"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:27
+msgid "**CentOS**, **Rocky Linux**, **AlmaLinux**, or possibly other RHEL alternatives (although your mileage may vary)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:28
+msgid "**Debian** (10/Buster or newer)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:29
+msgid "**Ubuntu** (18.04 or newer, although [20.04 may be problematic](ansible.md#supported-ansible-versions) if you run the Ansible playbook on it)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:31
+msgid "Generally, newer is better. We only strive to support released stable versions of distributions, not betas or pre-releases. This playbook can take over your whole server or co-exist with other services that you have there."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:33
+msgid "This playbook somewhat supports running on non-`amd64` architectures like ARM. See [Alternative Architectures](alternative-architectures.md)."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:35
+msgid "If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:37
+msgid "`root` access to your server (or a user capable of elevating to `root` via `sudo`)."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:39
+msgid "[Python](https://www.python.org/). Most distributions install Python by default, but some don't (e.g. Ubuntu 18.04) and require manual installation (something like `apt-get install python3`). On some distros, Ansible may incorrectly [detect the Python version](https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html) (2 vs 3) and you may need to explicitly specify the interpreter path in `inventory/hosts` during installation (e.g. `ansible_python_interpreter=/usr/bin/python3`)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:41
+msgid "[sudo](https://www.sudo.ws/), even when you've configured Ansible to log in as `root`. Some distributions, like a minimal Debian net install, do not include the `sudo` package by default."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:43
+msgid "An HTTPS-capable web server at the base domain name (`example.com`) which is capable of serving static files. Unless you decide to [Serve the base domain from the Matrix server](configuring-playbook-base-domain-serving.md) or alternatively, to use DNS SRV records for [Server Delegation](howto-server-delegation.md)."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:45
+msgid "Properly configured DNS records for `example.com` (details in [Configuring DNS](configuring-dns.md))."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:47
+msgid "Some TCP/UDP ports open. This playbook (actually [Docker itself](https://docs.docker.com/network/iptables/)) configures the server's internal firewall for you. In most cases, you don't need to do anything special. But **if your server is running behind another firewall**, you'd need to open these ports:"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:49
+msgid "`80/tcp`: HTTP webserver"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:50
+msgid "`443/tcp` and `443/udp`: HTTPS webserver"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:51
+msgid "`3478/tcp`: TURN over TCP (used by Coturn)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:52
+msgid "`3478/udp`: TURN over UDP (used by Coturn)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:53
+msgid "`5349/tcp`: TURN over TCP (used by Coturn)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:54
+msgid "`5349/udp`: TURN over UDP (used by Coturn)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:55
+msgid "`8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. In some cases, this **may necessary even with federation disabled**. Integration Servers (like Dimension) and Identity Servers (like ma1sd) may need to access `openid` APIs on the federation port."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:56
+msgid "the range `49152-49172/udp`: TURN over UDP"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:57
+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:61
+msgid "[▶️](configuring-dns.md) When ready to proceed, continue with [Configuring DNS](configuring-dns.md)."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/quick-start.po b/i18n/locales/jp/LC_MESSAGES/docs/quick-start.po
new file mode 100644
index 000000000..680f8b634
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/quick-start.po
@@ -0,0 +1,433 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/quick-start.md:1
+msgid "Quick start"
+msgstr ""
+
+#: ../../../docs/quick-start.md:9
+msgid "This page explains how to use this Ansible playbook to install Matrix services on your server with a minimal set of core services."
+msgstr ""
+
+#: ../../../docs/quick-start.md:11
+msgid "We will be using `example.com` as the \"base domain\" in the following instruction."
+msgstr ""
+
+#: ../../../docs/quick-start.md:13
+msgid "By following the instruction on this page, you will set up:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:15
+msgid "**your own Matrix server** on a `matrix.example.com` server, which is configured to present itself as `example.com`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:16
+msgid "**your user account** like `@alice:example.com` on the server"
+msgstr ""
+
+#: ../../../docs/quick-start.md:17
+msgid "a **self-hosted Matrix client**, [Element Web](configuring-playbook-client-element-web.md) with the default subdomain at `element.example.com`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:18
+msgid "Matrix delegation, so that your `matrix.example.com` server (presenting itself as `example.com`) can join the Matrix Federation and communicate with any other server in the Matrix network"
+msgstr ""
+
+#: ../../../docs/quick-start.md:20
+msgid "Please remember to replace `example.com` with your own domain before running any commands."
+msgstr ""
+
+#: ../../../docs/quick-start.md:22
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/quick-start.md:24
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Prerequisites](prerequisites.md)</sup>"
+msgstr ""
+
+#: ../../../docs/quick-start.md:26
+msgid "At first, **check prerequisites** and prepare for installation by setting up programs [on your own computer](prerequisites.md#your-local-computer) and [your server](prerequisites.md#server). You also need `root` access on your server (a user that could elevate to `root` via `sudo` also works)."
+msgstr ""
+
+#: ../../../docs/quick-start.md:28
+msgid "When preparing your server, make sure to check [the server specs you need](faq.md#what-kind-of-server-specs-do-i-need). We recommend starting with a server having at least 2GB of memory."
+msgstr ""
+
+#: ../../../docs/quick-start.md:34
+msgid "If you encounter an error during installation, please make sure that you have installed and configured programs correctly."
+msgstr ""
+
+#: ../../../docs/quick-start.md:36
+msgid "One of the main reasons of basic errors is using an incompatible version of required software such as Ansible. Take a look at [our guide about Ansible](ansible.md) for more information. In short: installing the latest available version is recommended."
+msgstr ""
+
+#: ../../../docs/quick-start.md:38
+msgid "Configure your DNS settings"
+msgstr ""
+
+#: ../../../docs/quick-start.md:40
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Configuring your DNS settings](configuring-dns.md)</sup>"
+msgstr ""
+
+#: ../../../docs/quick-start.md:42
+msgid "After installing and configuring prerequisites, you will need to **configure DNS records**."
+msgstr ""
+
+#: ../../../docs/quick-start.md:44
+msgid "To configure Matrix services in the default settings, go to your DNS service provider, and adjust DNS records as below."
+msgstr ""
+
+#: ../../../docs/quick-start.md
+msgid "Type"
+msgstr ""
+
+#: ../../../docs/quick-start.md
+msgid "Host"
+msgstr ""
+
+#: ../../../docs/quick-start.md
+msgid "Priority"
+msgstr ""
+
+#: ../../../docs/quick-start.md
+msgid "Weight"
+msgstr ""
+
+#: ../../../docs/quick-start.md
+msgid "Port"
+msgstr ""
+
+#: ../../../docs/quick-start.md
+msgid "Target"
+msgstr ""
+
+#: ../../../docs/quick-start.md
+msgid "A"
+msgstr ""
+
+#: ../../../docs/quick-start.md
+msgid "`matrix`"
+msgstr ""
+
+#: ../../../docs/quick-start.md
+msgid "-"
+msgstr ""
+
+#: ../../../docs/quick-start.md
+msgid "`matrix-server-IP`"
+msgstr ""
+
+#: ../../../docs/quick-start.md
+msgid "CNAME"
+msgstr ""
+
+#: ../../../docs/quick-start.md
+msgid "`element`"
+msgstr ""
+
+#: ../../../docs/quick-start.md
+msgid "`matrix.example.com`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:51
+msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)."
+msgstr ""
+
+#: ../../../docs/quick-start.md:53
+msgid "It might take some time for the DNS records to propagate after creation."
+msgstr ""
+
+#: ../../../docs/quick-start.md:55
+msgid "**💡 Note**: if you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\""
+msgstr ""
+
+#: ../../../docs/quick-start.md:57
+msgid "Get the playbook"
+msgstr ""
+
+#: ../../../docs/quick-start.md:59
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Getting the playbook](getting-the-playbook.md)</sup>"
+msgstr ""
+
+#: ../../../docs/quick-start.md:61
+msgid "Next, let's **get the playbook's source code**."
+msgstr ""
+
+#: ../../../docs/quick-start.md:63
+msgid "We recommend to do so with [git](https://git-scm.com/) as it enables you to keep it up to date with the latest source code. While it is possible to download the playbook as a ZIP archive, it is not recommended."
+msgstr ""
+
+#: ../../../docs/quick-start.md:65
+msgid "To get the playbook with git, install git on your computer, go to a directory, and run the command:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:71
+msgid "It will fetch the playbook to a new `matrix-docker-ansible-deploy` directory underneath the directory you are currently in."
+msgstr ""
+
+#: ../../../docs/quick-start.md:73
+msgid "Configure the playbook"
+msgstr ""
+
+#: ../../../docs/quick-start.md:75
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Configuring the playbook](configuring-playbook.md)</sup>"
+msgstr ""
+
+#: ../../../docs/quick-start.md:77
+msgid "Now that the playbook was fetched, it is time to **configure** it per your needs."
+msgstr ""
+
+#: ../../../docs/quick-start.md:79
+msgid "To install Matrix services with this playbook, you would at least need 2 configuration files."
+msgstr ""
+
+#: ../../../docs/quick-start.md:81
+msgid "For your convenience, we have prepared example files of them ([`vars.yml`](../examples/vars.yml) and [`hosts`](../examples/hosts))."
+msgstr ""
+
+#: ../../../docs/quick-start.md:83
+msgid "To start quickly based on these example files, go into the `matrix-docker-ansible-deploy` directory and follow the instructions below:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:85
+msgid "Create a directory to hold your configuration: `mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\""
+msgstr ""
+
+#: ../../../docs/quick-start.md:86
+msgid "Copy the sample configuration file: `cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:87
+msgid "Copy the sample inventory hosts file: `cp examples/hosts inventory/hosts`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:88
+msgid "Edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`)"
+msgstr ""
+
+#: ../../../docs/quick-start.md:89
+msgid "Edit the inventory hosts file (`inventory/hosts`)"
+msgstr ""
+
+#: ../../../docs/quick-start.md:91
+msgid "Before editing these 2 files, make sure to read explanations on them to understand what needs to be configured."
+msgstr ""
+
+#: ../../../docs/quick-start.md:93
+msgid "**💡 Notes:**"
+msgstr ""
+
+#: ../../../docs/quick-start.md:94
+msgid "If you are not in control of anything on the base domain, you would need to set additional configuration on `vars.yml`. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ."
+msgstr ""
+
+#: ../../../docs/quick-start.md:95
+msgid "Certain configuration decisions (like the base domain configured in `matrix_domain` and homeserver implementation configured in `matrix_homeserver_implementation`) are final. If you make the wrong choice and wish to change it, you'll have to run the Uninstalling step and start over."
+msgstr ""
+
+#: ../../../docs/quick-start.md:96
+msgid "Instead of configuring a lot of things all at once, we recommend starting with the basic (default) settings in order to get yourself familiar with how the playbook works. After making sure that everything works as expected, you can add (and remove) advanced settings / features and run the playbook as many times as you wish."
+msgstr ""
+
+#: ../../../docs/quick-start.md:98
+msgid "Install"
+msgstr ""
+
+#: ../../../docs/quick-start.md:100
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Installing](installing.md)</sup>"
+msgstr ""
+
+#: ../../../docs/quick-start.md:102
+msgid "After editing `vars.yml` and `hosts` files, let's start the **installation** procedure."
+msgstr ""
+
+#: ../../../docs/quick-start.md:104
+msgid "Update Ansible roles"
+msgstr ""
+
+#: ../../../docs/quick-start.md:106
+msgid "Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside."
+msgstr ""
+
+#: ../../../docs/quick-start.md:108
+msgid "To update your playbook directory and all upstream Ansible roles, run:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:110
+msgid "either: `just update`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:111
+msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)"
+msgstr ""
+
+#: ../../../docs/quick-start.md:113
+msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:115
+msgid "Run installation command"
+msgstr ""
+
+#: ../../../docs/quick-start.md:117
+msgid "Then, run the command below to start installation:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:123
+msgid "If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the command."
+msgstr ""
+
+#: ../../../docs/quick-start.md:125
+msgid "If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to the command."
+msgstr ""
+
+#: ../../../docs/quick-start.md:127
+msgid "Wait until the command completes. If it's all green, everything should be running properly."
+msgstr ""
+
+#: ../../../docs/quick-start.md:129
+msgid "Create your user account"
+msgstr ""
+
+#: ../../../docs/quick-start.md:131
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Registering users](registering-users.md)</sup>"
+msgstr ""
+
+#: ../../../docs/quick-start.md:133
+msgid "As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server."
+msgstr ""
+
+#: ../../../docs/quick-start.md:135
+msgid "To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer."
+msgstr ""
+
+#: ../../../docs/quick-start.md:137
+msgid "**💡 Notes**:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:138
+msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:139
+msgid "For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)"
+msgstr ""
+
+#: ../../../docs/quick-start.md:151
+msgid "Finalize server installation"
+msgstr ""
+
+#: ../../../docs/quick-start.md:153
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Server Delegation](howto-server-delegation.md)</sup>"
+msgstr ""
+
+#: ../../../docs/quick-start.md:155
+msgid "Now that you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network."
+msgstr ""
+
+#: ../../../docs/quick-start.md:157
+msgid "**This is required for federation to work!** Without a proper configuration, your server will effectively not be part of the Matrix network."
+msgstr ""
+
+#: ../../../docs/quick-start.md:159
+msgid "To configure the delegation, you have these two options. Choose one of them according to your situation."
+msgstr ""
+
+#: ../../../docs/quick-start.md:161
+msgid "If you can afford to point the base domain at the Matrix server, follow the instruction below which guides you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server."
+msgstr ""
+
+#: ../../../docs/quick-start.md:162
+msgid "Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot \"serve the base domain\" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server)."
+msgstr ""
+
+#: ../../../docs/quick-start.md:164
+msgid "To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:170
+msgid "After configuring the playbook, run the command below and wait until it finishes:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:176
+msgid "💡 Running the `install-matrix-static-files` playbook tag (as done here) is an optimized version of running [the full setup command](#run-installation-command)."
+msgstr ""
+
+#: ../../../docs/quick-start.md:178
+msgid "After the command finishes, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain."
+msgstr ""
+
+#: ../../../docs/quick-start.md:180
+msgid "Re-run the full setup command any time"
+msgstr ""
+
+#: ../../../docs/quick-start.md:182
+msgid "If you think something is wrong with the server configuration, feel free to re-run the setup command any time:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:188
+msgid "Log in to your user account"
+msgstr ""
+
+#: ../../../docs/quick-start.md:190
+msgid "Finally, let's make sure that you can log in to the created account with the specified password."
+msgstr ""
+
+#: ../../../docs/quick-start.md:192
+msgid "You should be able to log in to it with your own [Element Web](configuring-playbook-client-element-web.md) client which you have set up at `element.example.com` by running the playbook. Open the URL (`https://element.example.com`) in a web browser and enter your credentials to log in."
+msgstr ""
+
+#: ../../../docs/quick-start.md:194
+msgid "**If you successfully logged in to your account, installing and configuring is complete**🎉"
+msgstr ""
+
+#: ../../../docs/quick-start.md:196
+msgid "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/quick-start.md:198
+msgid "Things to do next"
+msgstr ""
+
+#: ../../../docs/quick-start.md:200
+msgid "Once you get familiar with the playbook, you might probably want to set up additional services such as a bridge on your server."
+msgstr ""
+
+#: ../../../docs/quick-start.md:202
+msgid "As this page intends to be a quick start guide which explains how to start the core Matrix services, it does not cover a topic like how to set them up. Take a look at the list of [things to do next](installing.md#things-to-do-next) to learn more."
+msgstr ""
+
+#: ../../../docs/quick-start.md:204
+msgid "⚠️Keep the playbook and services up-to-date"
+msgstr ""
+
+#: ../../../docs/quick-start.md:206
+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/quick-start.md:208
+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/quick-start.md:210
+msgid "For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/registering-users.po b/i18n/locales/jp/LC_MESSAGES/docs/registering-users.po
new file mode 100644
index 000000000..5a62a9d95
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/registering-users.po
@@ -0,0 +1,245 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/registering-users.md:1
+msgid "Registering users"
+msgstr ""
+
+#: ../../../docs/registering-users.md:3
+msgid "This documentation page tells you how to create user accounts on your Matrix server."
+msgstr ""
+
+#: ../../../docs/registering-users.md:5
+msgid "Table of contents:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:7
+msgid "[Registering users](#registering-users)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:8
+msgid "[Registering users manually](#registering-users-manually)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:9
+msgid "[Managing users via a Web UI](#managing-users-via-a-web-ui)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:10
+msgid "[Letting certain users register on your private server](#letting-certain-users-register-on-your-private-server)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:11
+msgid "[Enabling public user registration](#enabling-public-user-registration)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:12
+msgid "[Adding/Removing Administrator privileges to an existing user](#addingremoving-administrator-privileges-to-an-existing-user)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:14
+msgid "Registering users manually"
+msgstr ""
+
+#: ../../../docs/registering-users.md:16 ../../../docs/registering-users.md:118
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:17
+msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`"
+msgstr ""
+
+#: ../../../docs/registering-users.md:18
+msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:19
+msgid "Use `admin=yes` or `admin=no` depending on whether you wish to make the user an administrator of the Matrix server"
+msgstr ""
+
+#: ../../../docs/registering-users.md:21
+msgid "After registering a user (using one of the methods below), **you can log in with that user** via the [Element Web](configuring-playbook-client-element-web.md) service that this playbook has installed for you at a URL like this: `https://element.example.com/`."
+msgstr ""
+
+#: ../../../docs/registering-users.md:23
+msgid "Registering users via the Ansible playbook"
+msgstr ""
+
+#: ../../../docs/registering-users.md:25
+msgid "It's best to register users via the Ansible playbook, because it works regardless of homeserver implementation (Synapse, Dendrite, etc) or usage of [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (MAS)."
+msgstr ""
+
+#: ../../../docs/registering-users.md:27
+msgid "To register a user via this Ansible playbook:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:35
+msgid "**or** by invoking `ansible-playbook` manually:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:43
+msgid "Feel free to register as many users (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your user account only (with `admin=yes`), and others should be created with `admin=no`."
+msgstr ""
+
+#: ../../../docs/registering-users.md:45
+msgid "⚠️ **Warning**: If you're registering users against Matrix Authentication Service, do note that it [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information."
+msgstr ""
+
+#: ../../../docs/registering-users.md:47
+msgid "Registering users manually for Synapse"
+msgstr ""
+
+#: ../../../docs/registering-users.md:49
+msgid "If you're using the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default), you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
+msgstr ""
+
+#: ../../../docs/registering-users.md:57
+msgid "Registering users manually for Dendrite"
+msgstr ""
+
+#: ../../../docs/registering-users.md:59
+msgid "If you're using the [Dendrite](./configuring-playbook-dendrite.md) homeserver implementation, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
+msgstr ""
+
+#: ../../../docs/registering-users.md:67
+msgid "Registering users manually for Matrix Authentication Service"
+msgstr ""
+
+#: ../../../docs/registering-users.md:69
+msgid "If you're using the [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) and your existing homeserver (most likely [Synapse](./configuring-playbook-synapse.md)) is delegating authentication to it, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
+msgstr ""
+
+#: ../../../docs/registering-users.md:77
+msgid "This `register-user` script actually invokes the `mas-cli manage register-user` command under the hood. If you'd like more control over the registration process, consider invoking the `mas-cli` command directly:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:83
+msgid "⚠️ **Warning**: Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information."
+msgstr ""
+
+#: ../../../docs/registering-users.md:85
+msgid "Managing users via a Web UI"
+msgstr ""
+
+#: ../../../docs/registering-users.md:87
+msgid "To manage users more easily (via a web user-interace), you can install [Synapse Admin](configuring-playbook-synapse-admin.md)."
+msgstr ""
+
+#: ../../../docs/registering-users.md:89
+msgid "⚠️ **Warning**: If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information."
+msgstr ""
+
+#: ../../../docs/registering-users.md:91
+msgid "Letting certain users register on your private server"
+msgstr ""
+
+#: ../../../docs/registering-users.md:93
+msgid "If you'd rather **keep your server private** (public registration closed, as is the default), and **let certain people create accounts by themselves** (instead of creating user accounts manually like this), consider installing and making use of [matrix-registration](configuring-playbook-matrix-registration.md)."
+msgstr ""
+
+#: ../../../docs/registering-users.md:95
+msgid "Enabling public user registration"
+msgstr ""
+
+#: ../../../docs/registering-users.md:97
+msgid "To **open up user registration publicly** (usually **not recommended**), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:99
+msgid "For Synapse:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:105
+msgid "For Dendrite:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:111
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:120
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/registering-users.md:122
+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/registering-users.md:124
+msgid "If you're opening up registrations publicly like this, you might also wish to [configure CAPTCHA protection](configuring-captcha.md)."
+msgstr ""
+
+#: ../../../docs/registering-users.md:126
+msgid "Adding/Removing Administrator privileges to an existing user"
+msgstr ""
+
+#: ../../../docs/registering-users.md:128
+msgid "Adding/Removing Administrator privileges to an existing user in Synapse"
+msgstr ""
+
+#: ../../../docs/registering-users.md:130
+msgid "To change the admin privileges for a user in Synapse's local database, you need to run an SQL query like this against the `synapse` database:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:136
+msgid "where:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:138
+msgid "`ADMIN_VALUE` being either `0` (regular user) or `1` (admin)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:139
+msgid "`USER` and `example.com` pointing to a valid user on your server"
+msgstr ""
+
+#: ../../../docs/registering-users.md:141
+msgid "If you're using the integrated Postgres server and not an [external Postgres server](configuring-playbook-external-postgres.md), you can launch a Postgres into the `synapse` database by:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:143
+msgid "running `/matrix/postgres/bin/cli` - to launch [`psql`](https://www.postgresql.org/docs/current/app-psql.html)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:144
+msgid "running `\\c synapse` - to change to the `synapse` database"
+msgstr ""
+
+#: ../../../docs/registering-users.md:146
+msgid "You can then proceed to run the query above."
+msgstr ""
+
+#: ../../../docs/registering-users.md:148
+msgid "**Note**: directly modifying the raw data of Synapse (or any other software) could cause the software to break. You've been warned!"
+msgstr ""
+
+#: ../../../docs/registering-users.md:150
+msgid "Adding/Removing Administrator privileges to an existing user in Matrix Authentication Service"
+msgstr ""
+
+#: ../../../docs/registering-users.md:152
+msgid "Promoting/demoting a user in Matrix Authentication Service cannot currently (2024-10-19) be done via the [`mas-cli` Management tool](./configuring-playbook-matrix-authentication-service.md#management)."
+msgstr ""
+
+#: ../../../docs/registering-users.md:154
+msgid "You can do it via the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html)'s `POST /api/admin/v1/users/{id}/set-admin` endpoint."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/self-building.po b/i18n/locales/jp/LC_MESSAGES/docs/self-building.po
new file mode 100644
index 000000000..1da0b78a1
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/self-building.po
@@ -0,0 +1,177 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/self-building.md:1
+msgid "Self-building"
+msgstr ""
+
+#: ../../../docs/self-building.md:3
+msgid "**Caution: self-building does not have to be used on its own. See the [Alternative Architectures](alternative-architectures.md) page.**"
+msgstr ""
+
+#: ../../../docs/self-building.md:5
+msgid "The playbook supports self-building of various components, which don't have a container image for your architecture (see the [container images we use](container-images.md)). For `amd64`, self-building is not required."
+msgstr ""
+
+#: ../../../docs/self-building.md:7
+msgid "For other architectures (e.g. `arm32`, `arm64`), ready-made container images are used when available. If there's no ready-made image for a specific component and said component supports self-building, an image will be built on the host. Building images like this takes more time and resources (some build tools need to get installed by the playbook to assist building)."
+msgstr ""
+
+#: ../../../docs/self-building.md:9
+msgid "To make use of self-building, you don't need to do anything. If a component has an image for the specified architecture, the playbook will use it directly. If not, it will build the image on the server itself."
+msgstr ""
+
+#: ../../../docs/self-building.md:11
+msgid "Note that **not all components support self-building yet**."
+msgstr ""
+
+#: ../../../docs/self-building.md:13
+msgid "Possibly outdated list of roles where self-building the Docker image is currently possible:"
+msgstr ""
+
+#: ../../../docs/self-building.md:14
+msgid "`matrix-synapse`"
+msgstr ""
+
+#: ../../../docs/self-building.md:15
+msgid "`matrix-synapse-admin`"
+msgstr ""
+
+#: ../../../docs/self-building.md:16
+msgid "`matrix-client-element`"
+msgstr ""
+
+#: ../../../docs/self-building.md:17
+msgid "`matrix-client-hydrogen`"
+msgstr ""
+
+#: ../../../docs/self-building.md:18
+msgid "`matrix-client-cinny`"
+msgstr ""
+
+#: ../../../docs/self-building.md:19
+msgid "`matrix-registration`"
+msgstr ""
+
+#: ../../../docs/self-building.md:20
+msgid "`matrix-coturn`"
+msgstr ""
+
+#: ../../../docs/self-building.md:21
+msgid "`matrix-corporal`"
+msgstr ""
+
+#: ../../../docs/self-building.md:22
+msgid "`matrix-dimension`"
+msgstr ""
+
+#: ../../../docs/self-building.md:23
+msgid "`matrix-ma1sd`"
+msgstr ""
+
+#: ../../../docs/self-building.md:24
+msgid "`exim-relay`"
+msgstr ""
+
+#: ../../../docs/self-building.md:25
+msgid "`matrix-bridge-hookshot`"
+msgstr ""
+
+#: ../../../docs/self-building.md:26
+msgid "`matrix-bridge-appservice-irc`"
+msgstr ""
+
+#: ../../../docs/self-building.md:27
+msgid "`matrix-bridge-appservice-slack`"
+msgstr ""
+
+#: ../../../docs/self-building.md:28
+msgid "`matrix-bridge-appservice-webhooks`"
+msgstr ""
+
+#: ../../../docs/self-building.md:29
+msgid "`matrix-bridge-beeper-linkedin`"
+msgstr ""
+
+#: ../../../docs/self-building.md:30
+msgid "`matrix-bridge-mautrix-facebook`"
+msgstr ""
+
+#: ../../../docs/self-building.md:31
+msgid "`matrix-bridge-mautrix-hangouts`"
+msgstr ""
+
+#: ../../../docs/self-building.md:32
+msgid "`matrix-bridge-mautrix-googlechat`"
+msgstr ""
+
+#: ../../../docs/self-building.md:33
+msgid "`matrix-bridge-mautrix-telegram`"
+msgstr ""
+
+#: ../../../docs/self-building.md:34
+msgid "`matrix-bridge-mautrix-signal`"
+msgstr ""
+
+#: ../../../docs/self-building.md:35
+msgid "`matrix-bridge-mautrix-gmessages`"
+msgstr ""
+
+#: ../../../docs/self-building.md:36
+msgid "`matrix-bridge-mautrix-whatsapp`"
+msgstr ""
+
+#: ../../../docs/self-building.md:37
+msgid "`matrix-bridge-mx-puppet-steam`"
+msgstr ""
+
+#: ../../../docs/self-building.md:38
+msgid "`matrix-bot-mjolnir`"
+msgstr ""
+
+#: ../../../docs/self-building.md:39
+msgid "`matrix-bot-honoroit`"
+msgstr ""
+
+#: ../../../docs/self-building.md:40
+msgid "`matrix-bot-matrix-reminder-bot`"
+msgstr ""
+
+#: ../../../docs/self-building.md:41
+msgid "`matrix-bot-maubot`"
+msgstr ""
+
+#: ../../../docs/self-building.md:42
+msgid "`matrix-email2matrix`"
+msgstr ""
+
+#: ../../../docs/self-building.md:43
+msgid "`matrix-pantalaimon`"
+msgstr ""
+
+#: ../../../docs/self-building.md:45
+msgid "Adding self-building support to other roles is welcome. Feel free to contribute!"
+msgstr ""
+
+#: ../../../docs/self-building.md:47
+msgid "If you'd like **to force self-building** even if an image is available for your architecture, look into the `matrix_*_self_build` variables provided by individual roles."
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/uninstalling.po b/i18n/locales/jp/LC_MESSAGES/docs/uninstalling.po
new file mode 100644
index 000000000..826bd0919
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/uninstalling.po
@@ -0,0 +1,81 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/uninstalling.md:1
+msgid "Uninstalling"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:3
+msgid "**Warnings**:"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:5
+msgid "If your server federates with others, make sure to **leave any federated rooms before nuking your Matrix server's data**. Otherwise, the next time you set up a Matrix server for this domain (regardless of the installation method you use), you'll encounter trouble federating."
+msgstr ""
+
+#: ../../../docs/uninstalling.md:7
+msgid "If you have some trouble with your installation, you can just [re-run the playbook](installing.md) and it will try to set things up again. **Uninstalling and then installing anew rarely solves anything**."
+msgstr ""
+
+#: ../../../docs/uninstalling.md:11
+msgid "Uninstalling using a script"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:13
+msgid "Installing places a `/matrix/bin/remove-all` script on the server."
+msgstr ""
+
+#: ../../../docs/uninstalling.md:15
+msgid "You can run it to to have it uninstall things for you automatically (see below). **Use with caution!**"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:17
+msgid "Uninstalling manually"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:19
+msgid "If you prefer to uninstall manually, run these commands (most are meant to be executed on the Matrix server itself):"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:21
+msgid "ensure all Matrix services are stopped: `ansible-playbook -i inventory/hosts setup.yml --tags=stop` (if you can't get Ansible working to run this command, you can run `systemctl stop 'matrix*'` manually on the server)"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:23
+msgid "delete the Matrix-related systemd `.service` and `.timer` files (`rm -f /etc/systemd/system/matrix*.{service,timer}`) and reload systemd (`systemctl daemon-reload`)"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:25
+msgid "delete some cached Docker images (`docker system prune -a`) or just delete them all (`docker rmi $(docker images -aq)`)"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:27
+msgid "delete the Docker networks: `docker network rm matrix matrix-coturn` (might have been deleted already if you ran the `docker system prune` command)"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:29
+msgid "uninstall Docker itself, if necessary"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:31
+msgid "delete the `/matrix` directory (`rm -rf /matrix`)"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/docs/updating-users-passwords.po b/i18n/locales/jp/LC_MESSAGES/docs/updating-users-passwords.po
new file mode 100644
index 000000000..e0720b62b
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/docs/updating-users-passwords.po
@@ -0,0 +1,89 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-16 12:05+0900\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../../docs/updating-users-passwords.md:1
+msgid "Updating users passwords"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:3
+msgid "Option 1 (if you are using the integrated Postgres database):"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:5
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:6
+msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:7
+msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:9
+msgid "You can reset a user's password via the Ansible playbook:"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:15
+msgid "**You can then log in with that user** via Element Web that this playbook has created for you at a URL like this: `https://element.example.com/`."
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:17
+msgid "Option 2 (if you are using an external Postgres server):"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:19
+msgid "You can manually generate the password hash by using the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#finalize-the-installation):"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:25
+msgid "and then connecting to the postgres server and executing:"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:31
+msgid "where `<password-hash>` is the hash returned by the docker command above."
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:33
+msgid "Option 3:"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:35
+msgid "Use the Synapse User Admin API as described here: https://github.com/element-hq/synapse/blob/master/docs/admin_api/user_admin_api.rst#reset-password"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:37
+msgid "This requires an [access token](obtaining-access-tokens.md) from a server admin account. *This method will also log the user out of all of their clients while the other options do not.*"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:39
+msgid "If you didn't make your account a server admin when you created it, you can learn how to switch it now by reading about it in [Adding/Removing Administrator privileges to an existing user in Synapse](registering-users.md#addingremoving-administrator-privileges-to-an-existing-user-in-synapse)."
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:41
+msgid "Example:"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:43
+msgid "To set @alice:example.com's password to `correct_horse_battery_staple` you could use this curl command:"
+msgstr ""
diff --git a/i18n/locales/jp/LC_MESSAGES/i18n/README.po b/i18n/locales/jp/LC_MESSAGES/i18n/README.po
new file mode 100644
index 000000000..f93ab6c11
--- /dev/null
+++ b/i18n/locales/jp/LC_MESSAGES/i18n/README.po
@@ -0,0 +1,213 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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>, 2024.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: matrix-docker-ansible-deploy \n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2024-12-20 15:27+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language: jp\n"
+"Language-Team: jp <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=utf-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Generated-By: Babel 2.16.0\n"
+
+#: ../../README.md:8
+msgid "Internationalization"
+msgstr ""
+
+#: ../../README.md:10
+msgid "Translated documentation files are published and maintained in [`translations/`](translations/) directory."
+msgstr ""
+
+#: ../../README.md:12
+msgid "Currently, we support translation of:"
+msgstr ""
+
+#: ../../README.md:14
+msgid "Markdown files found at the top level project directory"
+msgstr ""
+
+#: ../../README.md:15
+msgid "Markdown files found in the [`docs`](../docs/) directory (this is where the bulk of the documentation is)"
+msgstr ""
+
+#: ../../README.md:16
+msgid "this current document in the `i18n` directory"
+msgstr ""
+
+#: ../../README.md:18
+msgid "💡 For readers' sake, we only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold (requiring that at least the project README and core installation guides are translated)."
+msgstr ""
+
+#: ../../README.md:20
+msgid "Organization of this `i18n` directory is as follows:"
+msgstr ""
+
+#: ../../README.md:22
+msgid "[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translations/](translations/) directory)"
+msgstr ""
+
+#: ../../README.md:23
+msgid "[.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionaly ignore translated results (`translations/<language>` directories) for languages taht are still in progress. We only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold."
+msgstr ""
+
+#: ../../README.md:24
+msgid "[justfile](justfile): a list of recipes for [just](https://github.com/casey/just) command runner"
+msgstr ""
+
+#: ../../README.md:25
+msgid "[requirements.txt](requirements.txt): a list of Python packages required to work with translations"
+msgstr ""
+
+#: ../../README.md:26
+msgid "[translation-templates/](translation-templates/): a list of English translation templates - strings extracted from Markdown files"
+msgstr ""
+
+#: ../../README.md:27
+msgid "[locales/](locales/): localization files for languages"
+msgstr ""
+
+#: ../../README.md:28
+msgid "[translations/](translations/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language))"
+msgstr ""
+
+#: ../../README.md:30
+msgid "Guide for translators"
+msgstr ""
+
+#: ../../README.md:32
+msgid "This project uses [Sphinx](https://www.sphinx-doc.org/) to generate translated documents."
+msgstr ""
+
+#: ../../README.md:34
+msgid "For details about using Sphinx for translation, refer [this official document](https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) as well."
+msgstr ""
+
+#: ../../README.md:36
+msgid "For now, translations are handled manually by editing `.po` files in the `locales/<language>` directory. In the future, we plan on integrating with [Weblate](https://weblate.org/) to allow for translating from a web interface."
+msgstr ""
+
+#: ../../README.md:38
+msgid "(Recommended) Using the uv package manager and just command runner"
+msgstr ""
+
+#: ../../README.md:40
+msgid "If you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed, you can use our [justfile](justfile) recipes to easily manage translation files and build translated documents."
+msgstr ""
+
+#: ../../README.md:42
+msgid "The recipes will use [uv](https://github.com/astral-sh/uv) to auto-create [a Python virtual environment](https://docs.astral.sh/uv/pip/environments/) in the `.venv` directory and install the required Python packages (as per [requirements.txt](requirements.txt)) to it."
+msgstr ""
+
+#: ../../README.md:44 ../../README.md:71
+msgid "Preparation"
+msgstr ""
+
+#: ../../README.md:46
+msgid "Make sure you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed."
+msgstr ""
+
+#: ../../README.md:48 ../../README.md:79
+msgid "Translation"
+msgstr ""
+
+#: ../../README.md:50 ../../README.md:81
+msgid "Recommended flow when working on a new language (replace `<language>` with the language code, e.g. `bg`):"
+msgstr ""
+
+#: ../../README.md:52
+msgid "Update the locale files for your language: `just sync-for-language <language>` (internally, this automatically runs `just extract-translation-templates` to make sure the translation templates are up-to-date)"
+msgstr ""
+
+#: ../../README.md:54 ../../README.md:87
+msgid "Use an editor to translate the files in the `locales/<language>` directory"
+msgstr ""
+
+#: ../../README.md:56
+msgid "Build translated documents: `just build-for-language <language>`"
+msgstr ""
+
+#: ../../README.md:58 ../../README.md:91
+msgid "Preview the result in the `translations/<language>` directory"
+msgstr ""
+
+#: ../../README.md:60 ../../README.md:93
+msgid "Commit your changes done to the `locales/<language>` directory"
+msgstr ""
+
+#: ../../README.md:62 ../../README.md:95
+msgid "If you have progressed with the translation beyond a certain threshold, consider [Publishing translations in a new language](#publish-translations-in-a-new-language)"
+msgstr ""
+
+#: ../../README.md:64
+msgid "Using any other package manager and manual scripts"
+msgstr ""
+
+#: ../../README.md:66
+msgid "If you cannot use [uv](https://docs.astral.sh/uv/) and/or [just](https://github.com/casey/just), you can:"
+msgstr ""
+
+#: ../../README.md:68
+msgid "manage Python packages in another way ([pip](https://pip.pypa.io/en/stable/), [Poetry](https://python-poetry.org/), etc.)"
+msgstr ""
+
+#: ../../README.md:69
+msgid "manage translation strings and build translated documents manually by invoking scripts from the [bin](bin/) directory"
+msgstr ""
+
+#: ../../README.md:73
+msgid "virtualenv and pip"
+msgstr ""
+
+#: ../../README.md:75
+msgid "Create a Python virtual environment in the `.venv` directory: `virtualenv .venv`"
+msgstr ""
+
+#: ../../README.md:76
+msgid "Activate the virtual environment: `source .venv/bin/activate`"
+msgstr ""
+
+#: ../../README.md:77
+msgid "Install the required Python packages using [pip](https://pip.pypa.io/en/stable/): `pip install -r requirements.txt`"
+msgstr ""
+
+#: ../../README.md:83
+msgid "Ensure the English translation templates ([translation-templates/](translation-templates/)) are extracted: `./bin/extract-translation-templates.sh`"
+msgstr ""
+
+#: ../../README.md:85
+msgid "Update the locale files for your language: `./bin/sync-translation-templates-to-locales.sh <language>`"
+msgstr ""
+
+#: ../../README.md:89
+msgid "Build translated documents: `./bin/build-translated-result.sh <language>`"
+msgstr ""
+
+#: ../../README.md:97
+msgid "Publish translations in a new language"
+msgstr ""
+
+#: ../../README.md:99
+msgid "To publish prebuilt documents translated in a new language to the `translations/<language>` directory:"
+msgstr ""
+
+#: ../../README.md:101
+msgid "add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file"
+msgstr ""
+
+#: ../../README.md:102
+msgid "whitelist its `translations/<language>` directory by adding a `!translations/<language>` rule to the [.gitignore](.gitignore) file"
+msgstr ""
+
+#: ../../README.md:104
+msgid "💡 Leave a trailing new line at the end of the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file."
+msgstr ""
diff --git a/i18n/requirements.txt b/i18n/requirements.txt
new file mode 100644
index 000000000..b48a508f1
--- /dev/null
+++ b/i18n/requirements.txt
@@ -0,0 +1,33 @@
+alabaster==1.0.0
+babel==2.16.0
+certifi==2024.12.14
+charset-normalizer==3.4.1
+click==8.1.8
+docutils==0.21.2
+idna==3.10
+imagesize==1.4.1
+Jinja2==3.1.5
+linkify-it-py==2.0.3
+markdown-it-py==3.0.0
+MarkupSafe==3.0.2
+mdit-py-plugins==0.4.2
+mdurl==0.1.2
+myst-parser==4.0.0
+packaging==24.2
+Pygments==2.19.1
+PyYAML==6.0.2
+requests==2.32.3
+setuptools==75.8.0
+snowballstemmer==2.2.0
+Sphinx==8.1.3
+sphinx-intl==2.3.1
+sphinx-markdown-builder==0.6.8
+sphinxcontrib-applehelp==2.0.0
+sphinxcontrib-devhelp==2.0.0
+sphinxcontrib-htmlhelp==2.1.0
+sphinxcontrib-jsmath==1.0.1
+sphinxcontrib-qthelp==2.0.0
+sphinxcontrib-serializinghtml==2.0.0
+tabulate==0.9.0
+uc-micro-py==1.0.3
+urllib3==2.3.0
diff --git a/i18n/translation-templates/CHANGELOG.pot b/i18n/translation-templates/CHANGELOG.pot
new file mode 100644
index 000000000..502fcbe16
--- /dev/null
+++ b/i18n/translation-templates/CHANGELOG.pot
@@ -0,0 +1,6971 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-22 17:53+0900\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"
+
+#: ../../../CHANGELOG.md:1
+msgid "2024-11-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3
+msgid "(Backward Compatibility Break) Synapse now defaults to enabling authenticated media"
+msgstr ""
+
+#: ../../../CHANGELOG.md:5
+msgid "**TLDR**: with this update, your Synapse homeserver will start requiring authentication for newly-uploaded media files. While the majority of the ecosystem (clients, bots, etc.) should support this, certain software may lack support for it (and you may wish to turn it off, if it's causing issues)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:7
+msgid "The default configuration for the Synapse homeserver now [enforces Authenticated media by default](https://element-hq.github.io/synapse/v1.120/upgrade.html#authenticated-media-is-now-enforced-by-default)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:9
+msgid "Servers like `matrix.org` have already [sunset unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) months ago."
+msgstr ""
+
+#: ../../../CHANGELOG.md:11
+msgid "Now that **various clients, bots, bridges and extra services have caught up with authenticated media support**, Synapse developers seem confident that it's time to enable authenticated media by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:13
+msgid "We're changing the playbook configuration for authenticated media to keep up with upstream defaults changing."
+msgstr ""
+
+#: ../../../CHANGELOG.md:15
+msgid "Old and unmaintained bridges (like all mx-puppet bridges, etc.) do not support authenticated media. Other software may be similarly affected. If you experience issues with some Matrix-related software, you may wish to disable authenticated media and contact the software maintainers to let them know."
+msgstr ""
+
+#: ../../../CHANGELOG.md:17
+msgid "You can disable authenticated media at any time by setting `matrix_synapse_enable_authenticated_media: false` in your `vars.yml` configuration file and re-running the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:20
+msgid "2024-11-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:22
+msgid "(Backward Compatibility Break) The playbook now defaults to Valkey, instead of KeyDB"
+msgstr ""
+
+#: ../../../CHANGELOG.md:24
+msgid "**TLDR**: if the playbook installed KeyDB (or Redis) as a dependency for you before, it will now replace it with [Valkey](https://valkey.io/) (a drop-in alternative). We [previously switched from Redis to KeyDB](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis), but Valkey is a better alternative, so we're switching again."
+msgstr ""
+
+#: ../../../CHANGELOG.md:26
+msgid "The playbook used to install Redis or KeyDB if services have a need for a Redis-compatible implementation ([enabling worker support for Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-workers), [enabling Hookshot encryption](docs/configuring-playbook-bridge-hookshot.md#end-to-bridge-encryption), etc.)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:28
+msgid "Earlier this year, we switched from Redis to KeyDB - see [(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:30
+msgid "Because Valkey seems to be a better successor to Redis (than KeyDB) and likely doesn't suffer from [issues like this one](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3544), we now replace KeyDB with Valkey."
+msgstr ""
+
+#: ../../../CHANGELOG.md:32
+msgid "Valkey (like KeyDB and Redis in the past) is an implicitly enabled dependency - you don't need custom configuration in `vars.yml` to enable it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:34
+msgid "Next time your run the playbook (via the `setup-all` tag), **KeyDB will be automatically uninstalled and replaced with Valkey**. Some Synapse downtime may occur while the switch happens."
+msgstr ""
+
+#: ../../../CHANGELOG.md:36
+msgid "Users on `arm32` should be aware that there's **neither a prebuilt `arm32` container image for Valkey**, nor the Valkey role supports self-building yet. Users on this architecture likely don't run Synapse with workers, etc., so they're likely in no need of Valkey (or Redis/KeyDB). If Redis is necessary in an `arm32` deployment, disabling Valkey and making the playbook fall back to Redis is possible (see below)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:38
+#: ../../../CHANGELOG.md:378
+msgid "**The playbook still supports Redis** and you can keep using Redis (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:49
+msgid "**The playbook still supports KeyDB** and you can keep using KeyDB (for now) if you'd like, by adding this additional configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:59
+msgid "At some point in time in the future, we'll remove both KeyDB and Redis from the playbook, so we recommend that you migrate to Valkey earlier anyway."
+msgstr ""
+
+#: ../../../CHANGELOG.md:62
+msgid "2024-11-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:64
+msgid "HTTP-compression support for Traefik-based setups"
+msgstr ""
+
+#: ../../../CHANGELOG.md:66
+msgid "The playbook now **automatically enables HTTP-compression support** for major services powered by the playbook, like [Cinny](./docs/configuring-playbook-client-cinny.md), [Element Web](./docs/configuring-playbook-client-element-web.md), [Hydrogen](./docs/configuring-playbook-client-hydrogen.md), as well as for Matrix Client-Server and Federation APIs (`matrix.example.com`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:68
+msgid "Other services installed by the playbook are currently not compression-enabled, but may become so over time. This change is rolled out on a per-service basis (as opposed to doing it globally, at the Traefik entrypoint level) to allow certain services or route endpoints which do not behave well when compressed (e.g. [issue 3749](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3749)) to be excluded from compression."
+msgstr ""
+
+#: ../../../CHANGELOG.md:70
+msgid "A long time ago, various services were operating with `gzip`-compression enabled at the nginx level. Since the switch to Traefik (see [Goodbye, `matrix-nginx-proxy` 🪦](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/57c5271d9d6265a34a9d9cceb93365f685074f96/CHANGELOG.md#goodbye-matrix-nginx-proxy-)), all services (with the exception of Matrix APIs for Synapse worker-enabled setups which are powered by `nginx` via `synapse-reverse-proxy-companion`) have been operating without HTTP-compression support."
+msgstr ""
+
+#: ../../../CHANGELOG.md:72
+msgid "HTTP-compression is now done via Traefik's [compress](https://doc.traefik.io/traefik/middlewares/http/compress/) middleware. We use the default configuration for this middleware, which enables `zstd`, `br` and `gzip` support (in this order). This middleware's configuration can be configured via variables in the Traefik role (see `traefik_config_http_middlewares_compression_middleware_options`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:74
+msgid "If you're using your own Traefik reverse-proxy server ([Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)) instead of the playbook's integrated Traefik service, you can benefit from the same by:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:76
+msgid "defining a [compress](https://doc.traefik.io/traefik/middlewares/http/compress/) middleware (via the [file](https://doc.traefik.io/traefik/providers/file/) or [Docker](https://doc.traefik.io/traefik/providers/docker/) providers)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:77
+msgid "setting `matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled` to `true`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:78
+msgid "specifying the middleware's name in `matrix_playbook_reverse_proxy_traefik_middleware_compression_name` (e.g. `matrix_playbook_reverse_proxy_traefik_middleware_compression_name: my-compression-middleware@file`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:80
+msgid "Timeout adjustments for Traefik-based setups"
+msgstr ""
+
+#: ../../../CHANGELOG.md:82
+msgid "The playbook now supports configuring various [transport.respondingTimeouts](https://doc.traefik.io/traefik/routing/entrypoints/#respondingtimeouts) timeout values (`readTimeout`, `writeTimeout`, `idleTimeout`) for the `web`, `web-secure` and `matrix-federation` entrypoints."
+msgstr ""
+
+#: ../../../CHANGELOG.md:84
+msgid "If you're using your own Traefik reverse-proxy server ([Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)) instead of the playbook's integrated Traefik service, you may wish to do similar configuration changes to your setup manually."
+msgstr ""
+
+#: ../../../CHANGELOG.md:86
+msgid "The most interesting of these is the `readTimeout` configuration value (the maximum duration for reading the entire request, including the body), which used to default to `60s`. For large and slowly progressing file uploads, `60s` would often not be enough for the transfer to finish and uploads would end up being interrupted. The playbook now raises the `readTimeout` value to 5 minutes (`300s`) to improve this use-case."
+msgstr ""
+
+#: ../../../CHANGELOG.md:88
+msgid "The `traefik_config_entrypoint_web_transport_respondingTimeouts_*` variables (for the `web` entrypoint) cascade to affecting the timeout values for the `web-secure` and `matrix-federation` entrypoints, so you can easily adjust all timeout values using them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:90
+msgid "Example of the default timeout values used by the playbook:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:101
+msgid "Alternatively, you may adjust the timeout values for specific entrypoints (like `web-secure` and `matrix-federation`) using dedicated variables (like `traefik_config_entrypoint_web_secure_transport_respondingTimeouts_readTimeout` and `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_readTimeout`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:104
+msgid "2024-11-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:106
+msgid "Support for synapse-admin auto-configuration via /.well-known/matrix/client"
+msgstr ""
+
+#: ../../../CHANGELOG.md:108
+msgid "You can administrate your Synapse-powered homeserver using synapse-admin hosted externally (e.g. [admin.etke.cc](https://admin.etke.cc/)) and the synapse-admin instance would still auto-configure itself correctly for your server by [reading its `/.well-known/matrix/client` file](https://github.com/etkecc/synapse-admin/pull/126)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:110
+msgid "The playbook now configures the `/.well-known/matrix/client` file for this by default, injecting into it a `cc.etke.synapse-admin` section that contains the full synapse-admin configuration. This is done even if you don't enable the synapse-admin service in your configuration. The reason for always doing it is to allow users to skip the (small) overhead of self-hosting the non-core synapse-admin service, yet still be able to use it from elsewhere when needed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:112
+msgid "If you don't ever plan on using synapse-admin from other servers (besides your own due to [self-hosting synapse-admin](./docs/configuring-playbook-synapse-admin.md)), you **can disable this** `/.well-known/matrix/client` configuration via `matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_enabled: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:115
+msgid "2024-10-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:117
+msgid "(BC Break) Postmoogle's variable names need adjustments"
+msgstr ""
+
+#: ../../../CHANGELOG.md:119
+msgid "Due to the recategorization of [Postmoogle](./docs/configuring-playbook-bridge-postmoogle.md) from the bot to the bridge, its variables were renamed (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`). You need to adjust your `vars.yml` configuration accordingly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:121
+msgid "2024-10-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:123
+msgid "Support for Matrix Authentication Service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:125
+msgid "The playbook now supports installing and configuring [Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) (MAS)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:127
+msgid "Huge thanks to [Quentin Gliech](https://github.com/sandhose) from the [Element](https://element.io/) / [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service) team for answering our numerous questions about MAS."
+msgstr ""
+
+#: ../../../CHANGELOG.md:129
+msgid "This is an **experimental service** and there are **still certain issues with it** (see [Expectations](./docs/configuring-playbook-matrix-authentication-service.md#expectations)). Matrix server administrators should only consider switching if they identify with one or more [reasons to use Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md#reasons-to-use-matrix-authentication-service). As MAS adoption improves and more services are adjusted to support it, we expect that using MAS will become the norm."
+msgstr ""
+
+#: ../../../CHANGELOG.md:131
+msgid "Our [Setting up Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) documentation page has more details about this new service, what you might expect from the switch and how you can migrate your existing (Synapse) homeserver setup to MAS."
+msgstr ""
+
+#: ../../../CHANGELOG.md:134
+msgid "2024-09-27"
+msgstr ""
+
+#: ../../../CHANGELOG.md:136
+msgid "(BC Break) Postgres & Traefik roles have been relocated and variable names need adjustments"
+msgstr ""
+
+#: ../../../CHANGELOG.md:138
+msgid "Various roles have been relocated from the [devture](https://github.com/devture) organization to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization."
+msgstr ""
+
+#: ../../../CHANGELOG.md:140
+msgid "Along with the relocation, the `devture_` prefix was dropped from their variable names, so you need to adjust your `vars.yml` configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:142
+msgid "You need to do the following replacements:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:144
+msgid "`devture_postgres_` -> `postgres_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:145
+msgid "`devture_traefik_` -> `traefik_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:147
+msgid "As always, the playbook would let you know about this and point out any variables you may have missed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:150
+msgid "2024-09-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:152
+msgid "Support for baibot"
+msgstr ""
+
+#: ../../../CHANGELOG.md:154
+msgid "The playbook now supports installing [baibot](./docs/configuring-playbook-bot-baibot.md) (pronounced bye-bot) - a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖"
+msgstr ""
+
+#: ../../../CHANGELOG.md:156
+msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as well as many other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:158
+msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to the now-unmaintained [matrix-chatgpt-bot](./docs/configuring-playbook-bot-chatgpt.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:160
+msgid "To get started, see the [Setting up baibot](./docs/configuring-playbook-bot-baibot.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:162
+msgid "Switching synapse-admin to etke.cc's fork"
+msgstr ""
+
+#: ../../../CHANGELOG.md:164
+msgid "The playbook now installs [etke.cc](https://etke.cc/)'s [fork](https://github.com/etkecc/synapse-admin) of [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin) (originally developed by [Awesome-Technologies](https://github.com/Awesome-Technologies)). This fork is a drop-in replacement for the original software."
+msgstr ""
+
+#: ../../../CHANGELOG.md:166
+msgid "The creation of the fork has been provoked by users frequently encountering issues with the original synapse-admin software, such as unintentionally deleting their one-and-only admin user account (fixed [here](https://github.com/etkecc/synapse-admin/pull/1) and also contributed upstream [here](https://github.com/Awesome-Technologies/synapse-admin/pull/608) - to no avail for now). Since its inception, [a bunch of other quality-of-life improvements](https://github.com/etkecc/synapse-admin?tab=readme-ov-file#changes) have been made to the fork."
+msgstr ""
+
+#: ../../../CHANGELOG.md:168
+msgid "If upstream synapse-admin picks up the pace and improves, the etke.cc fork may disappear and the playbook may switch to the original software again. Until that time comes, we believe that etke.cc's fork is the better software to use right now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:170
+msgid "If you'd like to switch back to the original synapse-admin software, you can do so by adding the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:183
+msgid "2024-08-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:185
+msgid "New appservice-double-puppet service for better double-puppeting"
+msgstr ""
+
+#: ../../../CHANGELOG.md:187
+msgid "Mautrix bridges are undergoing large changes as announced in the [August 2024 releases & progress](https://mau.fi/blog/2024-08-mautrix-release/) blog post."
+msgstr ""
+
+#: ../../../CHANGELOG.md:189
+msgid "The playbook has already upgraded to the rewritten mautrix-slack ([v0.1.0](https://github.com/mautrix/slack/releases/tag/v0.1.0)) and mautrix-signal ([v0.7.0](https://github.com/mautrix/signal/releases/tag/v0.7.0)) bridges."
+msgstr ""
+
+#: ../../../CHANGELOG.md:191
+msgid "The newly rewritten bridges do not support double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) anymore, which has prompted us to switch to the new & better [appservice method](https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new) for double-puppeting. The playbook automates this double-puppeting setup for you if you enable the new [Appservice Double Puppet](./docs/configuring-playbook-appservice-double-puppet.md) service."
+msgstr ""
+
+#: ../../../CHANGELOG.md:193
+msgid "All non-deprecated mautrix bridges in the playbook have been reworked to support double-puppeting via an Appservice. Most bridges still support double-puppeting via [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md), so the playbook supports it too. If only Shared Secret Auth is enabled, double-puppeting will be configured using that method (for the bridges that support it). That said, **Shared Secret Auth double-puppeting is being phased out and we recommend replacing it with the new Appservice method**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:195
+msgid "We recommend **enabling double-puppeting via the new Appservice method** by adding the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:201
+msgid "You can still **keep** [Shared Secret Auth](./docs/configuring-playbook-shared-secret-auth.md) enabled. Non-mautrix bridges and other services (e.g. [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) may still require it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:203
+msgid "When both double-puppeting methods are enabled, the playbook will automatically choose the new and better Appservice method for bridges that support it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:206
+msgid "2024-08-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:208
+msgid "matrix-media-repo now configured for Authenticated Media"
+msgstr ""
+
+#: ../../../CHANGELOG.md:210
+msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), our matrix-media-repo implementation now automatically [sets up signing keys](https://docs.t2bot.io/matrix-media-repo/v1.3.5/installation/signing-key/) for Authenticated Media (as per [MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:212
+msgid "If you had never heard of Authenticated Media before, the [Sunsetting unauthenticated media](https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/) article on [matrix.org](https://matrix.org/) is a good introduction."
+msgstr ""
+
+#: ../../../CHANGELOG.md:214
+msgid "This feature is enabled for matrix-media-repo installations by default and will append an additional (matrix-media-repo-generated signing key) to your homeserver's (Synapse or Dendrite) signing key. See the [Signing keys](./docs/configuring-playbook-matrix-media-repo.md#signing-keys) and [Key backup and revoking](./docs/configuring-playbook-matrix-media-repo.md#key-backup-and-revoking) sections of the matrix-media-repo documentation for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:216
+msgid "If you'd like to avoid this new feature, you can disable it by setting `matrix_media_repo_generate_signing_key: false` in your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:219
+msgid "2024-08-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:221
+msgid "(Backward Compatibility Break) matrix-corporal has been upgraded to v3"
+msgstr ""
+
+#: ../../../CHANGELOG.md:223
+msgid "The playbook now installs [matrix-corporal](https://github.com/devture/matrix-corporal) v3.0.0, which brings support for **power-level management** (thanks to [this PR](https://github.com/devture/matrix-corporal/pull/32))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:225
+msgid "This upgrade necessitates configuration policy changes as described in [matrix-corporal's changelog entry](https://github.com/devture/matrix-corporal/blob/5287cb81c82cd3b951c2a099b4697c3e0b384559/CHANGELOG.md#version-300-2024-08-08)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:227
+msgid "If you'd like to remain on the old (v2) version of matrix-corporal, you can do so by adding the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:233
+msgid "2024-07-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:235
+msgid "synapse-usage-exporter support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:237
+msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) - a small [Flask](https://flask.palletsprojects.com)-based webservice which can capture usage statistics from Synapse (via HTTP `PUT`) and then make them available for Prometheus to scrape."
+msgstr ""
+
+#: ../../../CHANGELOG.md:239
+msgid "To learn more see our [Enabling synapse-usage-exporter for Synapse usage statistics](docs/configuring-playbook-synapse-usage-exporter.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:242
+msgid "2024-07-06"
+msgstr ""
+
+#: ../../../CHANGELOG.md:244
+msgid "matrix-alertmanager-receiver support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:246
+msgid "For those wishing to more easily integrate [Prometheus](https://prometheus.io/)' alerting service ([Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/)) with Matrix, the playbook can now set up [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:248
+msgid "See [Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](./docs/configuring-playbook-alertmanager-receiver.md) for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:250
+msgid "Traefik v3 and HTTP/3 are here now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:252
+msgid "**TLDR**: Traefik was migrated from v2 to v3. Minor changes were done to the playbook. Mostly everything else worked out of the box. Most people will not have to do any tweaks to their configuration. In addition, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is now auto-enabled for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints. If you have a firewall in front of your server and you wish to benefit from `HTTP3`, you will need to open the `443` and `8448` UDP ports in it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:254
+msgid "Traefik v3"
+msgstr ""
+
+#: ../../../CHANGELOG.md:256
+msgid "The reverse-proxy that the playbook uses by default (Traefik) has recently been upgraded to v3 (see [this blog post](https://traefik.io/blog/announcing-traefik-proxy-v3-rc/) to learn about its new features). Version 3 includes some small breaking configuration changes requiring a [migration](https://doc.traefik.io/traefik/migration/v2-to-v3/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:258
+msgid "We have **updated the playbook to Traefik v3** (make sure to run `just roles` / `make roles` to get it)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:260
+msgid "There were **only minor playbook changes required** to adapt to Traefik v3, and only to the Ansible role for [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) where we changed a few [`PathPrefix` instances to `PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-pathprefix-and-pathregexp), because these instances were using a regular expression instead of a fixed path. For fixed-path values, `PathPrefix` is still the preferred matcher function to use."
+msgstr ""
+
+#: ../../../CHANGELOG.md:262
+msgid "**Most people using the playbook should not have to do any changes**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:264
+msgid "If you're using the playbook's Traefik instance to reverse-proxy to some other services of your own (not managed by the playbook), you may wish to review their Traefik labels and make sure they're in line with the [Traefik v2 to v3 migration guide](https://doc.traefik.io/traefik/migration/v2-to-v3/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:266
+msgid "If you've tweaked any of this playbook's `_path_prefix` variables and made them use a regular expression, you will now need to make additional adjustments. The playbook makes extensive use of `PathPrefix()` matchers in Traefik rules and `PathPrefix` does not support regular expressions anymore. To work around it, you may now need to override a whole `_traefik_rule` variable and switch it from [`PathPrefix` to `PathRegexp`](https://doc.traefik.io/traefik/routing/routers/#path-pathprefix-and-pathregexp)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:268
+msgid "If you're not using [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) (the only role we had to tweak to adapt it to Traefik v3), you **may potentially downgrade to Traefik v2** (if necessary) by adding `traefik_verison: v2.11.4` to your configuration. People using `matrix-media-repo` cannot downgrade this way, because `matrix-media-repo` has been adjusted to use `PathRegexp` - a [routing matcher](https://doc.traefik.io/traefik/v2.11/routing/routers/#rule) that Traefik v2 does not understand."
+msgstr ""
+
+#: ../../../CHANGELOG.md:270
+msgid "HTTP/3 is enabled by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:272
+msgid "In Traefik v3, [HTTP/3](https://en.wikipedia.org/wiki/HTTP/3) support is no longer considered experimental now. Due to this, **the playbook auto-enables HTTP3** for the `web-secure` (port 443) and `matrix-federation` (port `8448`) entrypoints."
+msgstr ""
+
+#: ../../../CHANGELOG.md:274
+msgid "HTTP3 uses the UDP protocol and **the playbook (together with Docker) will make sure that the appropriate ports** (`443` over UDP & `8448` over UDP) **are exposed and whitelisted in your server's firewall**. However, **if you have another firewall in front of your server** (as is the case for many cloud providers), **you will need to manually open these UDP ports**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:276
+msgid "If you do not open the UDP ports correctly or there is some other issue, clients (browsers, mostly) will fall-back to [HTTP/2](https://en.wikipedia.org/wiki/HTTP/2) or even [HTTP/1.1](https://en.wikipedia.org/wiki/HTTP)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:278
+msgid "Still, if HTTP/3 cannot function correctly in your setup, it's best to disable advertising support for it (and misleading clients into trying to use HTTP/3)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:280
+msgid "To **disable HTTP/3**, you can use the following configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:294
+msgid "If you are using [your own webserver](./docs/configuring-playbook-own-webserver.md) (in front of Traefik), port binding on UDP port `8448` by default due to HTTP/3 is either unnecessary or [may get in the way](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3402). If it does, you can disable it:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:307
+msgid "2024-07-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:309
+msgid "synapse-admin is now restricted to your homeserver's URL by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:311
+msgid "A new feature introduced in synapse-admin [v0.10.0](https://github.com/Awesome-Technologies/synapse-admin/releases/tag/0.10.0) (released and supported by the playbook since a a few months ago) provides the ability to [restrict its usage to a specific homeserver](https://github.com/Awesome-Technologies/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) (or multiple homeservers)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:313
+msgid "The playbook has just started making use of this feature. **From now on, your synapse-admin instance will be restricted to the homeserver you're managing via the playbook**. When configured like this, the *Homeserver URL* field in synapse-admin's web UI changes from a text field to a dropdown having a single value (the URL of your homeserver). This makes usage simpler for most people, as they won't need to manually enter a *Homeserver URL* anymore."
+msgstr ""
+
+#: ../../../CHANGELOG.md:315
+msgid "If you'd like **to go back to the old unrestricted behavior**, use the following configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:323
+msgid "2024-06-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:325
+msgid "The URL-prefix for Hookshot generic webhooks has changed"
+msgstr ""
+
+#: ../../../CHANGELOG.md:327
+msgid "Until now, generic Hookshot webhook URLs looked like this: `https://matrix.example.com/hookshot/webhooks/:hookId`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:329
+msgid "The `/hookshot/webhooks` common prefix gets stripped by Traefik automatically, so Hookshot only sees the part that comes after (`/:hookId`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:331
+msgid "[A few years ago](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1681), Hookshot started to prefer to handle webhooks at a `/webhook/:hookId` path (instead of directly at `/:hookId`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:333
+msgid "To avoid future problems, we've [reconfigured](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/4704a60718946fd469aeee7fc3ae8127c633bb6b) our Hookshot configuration to use webhook URLs that include `/webhook` in the URL suffix (e.g. `/hookshot/webhooks/webhook/:hookId`, instead of `/hookshot/webhooks/:hookId`). This means that when we strip the common prefi (`/hookshot/webhooks`), we'll end up sending `/webhook/:hookId` to Hookshot, just like recommended."
+msgstr ""
+
+#: ../../../CHANGELOG.md:335
+msgid "When generating new webhooks, you should start seeing the new URLs being used."
+msgstr ""
+
+#: ../../../CHANGELOG.md:337
+msgid "**For now**, **both** old URLs (`/hookshot/webhooks/:hookId`) and new URLs (`/hookshot/webhooks/webhook/:hookId`) **continue to work**, so your webhooks will not break just yet."
+msgstr ""
+
+#: ../../../CHANGELOG.md:339
+msgid "However, **we recommend that you update all your old webhook URLs** (configured in other systems) to include the new `/webhook` path component, so that future Hookshot changes (whenever they come) will not break your webhooks. You don't need to do anything on the Hookshot side - you merely need to reconfigure the remote systems that use your webhook URLs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:342
+msgid "2024-06-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:344
+msgid "The maubot user is now managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:346
+msgid "To make things easier and to be consistent with other roles, the [maubot](./docs/configuring-playbook-bot-maubot.md) user (`bot.maubot` by default) is [now](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3376) automatically created be the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:348
+msgid "If you have an existing maubot installation, you will need to specify `matrix_bot_maubot_initial_password` in your `vars.yml` file to make the playbook not complain about it being undefined. Since the bot is already registered in your installation, there's nothing for the playbook to do anyway. In case you don't remember the password you've registered your maubot user account with, you can specify any value for this variable."
+msgstr ""
+
+#: ../../../CHANGELOG.md:350
+msgid "If you've registered another username for the bot (other than the recommended default of `bot.maubot`), consider adjusting the `matrix_bot_maubot_login` variable (e.g. `matrix_bot_maubot_login: my.maubot.username`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:353
+msgid "2024-06-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:355
+msgid "WeChat bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:357
+msgid "Thanks to [Tobias Diez](https://github.com/tobiasdiez)'s [efforts](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3241), the playbook now supports bridging to [WeChat](https://www.wechat.com/) via the [matrix-wechat](https://github.com/duo/matrix-wechat) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:359
+msgid "See our [Setting up WeChat bridging](docs/configuring-playbook-bridge-wechat.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:362
+msgid "2024-03-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:364
+msgid "(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis"
+msgstr ""
+
+#: ../../../CHANGELOG.md:366
+msgid "**TLDR**: if the playbook used installed Redis as a dependency for you before, it will now replace it with [KeyDB](https://docs.keydb.dev/) (a drop-in alternative) due to [Redis having changed its license](https://redis.com/blog/redis-adopts-dual-source-available-licensing/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:368
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now uses [KeyDB](https://docs.keydb.dev/) (a drop-in alternative for Redis), instead of [Redis](https://redis.io/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:370
+msgid "The playbook used to install Redis (and now installs KeyDB in its place) if services have a need for it ([enabling worker support for Synapse](docs/configuring-playbook-synapse.md#load-balancing-with-workers), [enabling Hookshot encryption](docs/configuring-playbook-bridge-hookshot.md#end-to-bridge-encryption), etc.) or if you explicitly enabled the service (`redis_enabled: true` or `keydb_enabled: true`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:372
+msgid "This change is provoked by the fact that [Redis is now \"source available\"](https://redis.com/blog/redis-adopts-dual-source-available-licensing/). According to the Limitations of [the new license](https://redis.com/legal/rsalv2-agreement/) (as best as we understand them, given that we're not lawyers), using Redis in the playbook (even in a commercial FOSS service like [etke.cc](https://etke.cc/)) does not violate the new Redis license. That said, we'd rather neither risk it, nor endorse shady licenses and products that pretend to be free-software. Another high-quality alternative to Redis seems to be [Dragonfly](https://www.dragonflydb.io/), but the [Dragonfly license](https://github.com/dragonflydb/dragonfly?tab=License-1-ov-file#readme) is no better than Redis's."
+msgstr ""
+
+#: ../../../CHANGELOG.md:374
+msgid "Next time your run the playbook (via the `setup-all` tag), **Redis will be automatically uninstalled and replaced with KeyDB**. Some Synapse downtime may occur while the switch happens."
+msgstr ""
+
+#: ../../../CHANGELOG.md:376
+msgid "Users on `arm32` should be aware that there's **neither a prebuilt `arm32` container image for KeyDB**, nor the KeyDB role supports self-building yet. Users on this architecture likely don't run Synapse with workers, etc., so they're likely in no need of KeyDB (or Redis). If Redis is necessary in an `arm32` deployment, disabling KeyDB and making the playbook fall back to Redis is possible (see below)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:387
+msgid "2024-03-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:389
+msgid "Initial work on IPv6 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:391
+msgid "Thanks to [Tilo Spannagel](https://github.com/tilosp), the playbook can now enable IPv6 for container networks for various components (roles) via [the `devture_systemd_docker_base_ipv6_enabled` variable](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L14-L31)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:393
+msgid "It should be noted that:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:395
+msgid "Matrix roles (`roles/custom/matrix-*`) respect this variable, but external roles (those defined in `requirements.yml` and installed via `just roles`) do not respect it yet. Additional work is necessary"
+msgstr ""
+
+#: ../../../CHANGELOG.md:396
+msgid "changing the variable subsequently may not change existing container networks. Refer to [these instructions](https://github.com/devture/com.devture.ansible.role.systemd_docker_base/blob/c11a526bb8e318b42eb52055056377bb31154f13/defaults/main.yml#L26-L30)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:397
+msgid "this is all very new and untested"
+msgstr ""
+
+#: ../../../CHANGELOG.md:399
+msgid "Pantalaimon support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:401
+msgid "Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the playbook can now install the [Pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you. It's already possible to integrate it with [Draupnir](docs/configuring-playbook-bot-draupnir.md) to allow it to work in E2EE rooms - see our Draupnir docs for details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:403
+msgid "See our [Setting up Pantalaimon](docs/configuring-playbook-pantalaimon.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:406
+msgid "2024-03-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:408
+msgid "Support for Draupnir-for-all"
+msgstr ""
+
+#: ../../../CHANGELOG.md:410
+msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now install [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) (aka multi-instance Draupnir running in appservice mode)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:412
+msgid "This is an alternative to [running Draupnir in bot mode](./docs/configuring-playbook-bot-draupnir.md), which is still supported by the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:414
+msgid "The documentation page for [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) contains more information on how to install it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:417
+msgid "2024-02-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:419
+msgid "Support for bridging to Facebook/Messenger via the new mautrix-meta bridge"
+msgstr ""
+
+#: ../../../CHANGELOG.md:421
+msgid "The [mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-facebook.md) and [mautrix-instagram](./docs/configuring-playbook-bridge-mautrix-instagram.md) bridges are being [superseded by a new bridge](https://github.com/mautrix/facebook/issues/332) - the [mautrix-meta](https://github.com/mautrix/meta) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:423
+msgid "The playbook now supports the new mautrix-meta bridge - a single bridge, which can run in different modes and bridge to Messenger (via [Facebook](https://facebook.com/), Facebook over [Tor](https://www.torproject.org/) or via [Messenger](https://messenger.com/)) and [Instagram](https://instagram.com/). The playbook makes this bridge available via 2 separate Ansible roles, allowing you to easily run 2 instances of mautrix-meta, for bridging to both services at the same time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:425
+msgid "If you're using mautrix-facebook or mautrix-instagram right now, **you can still continue using the old bridges, but may wish to change to the new bridge implementations**. See:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:427
+msgid "[Setting up Instagram bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:429
+msgid "[Setting up Messenger bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-messenger.md)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:431
+msgid "The documentation pages contain more information on how to migrate."
+msgstr ""
+
+#: ../../../CHANGELOG.md:434
+msgid "2024-02-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:436
+msgid "Much larger Synapse caches and cache auto-tuning enabled by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:438
+msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook now uses much larger caches and enables Synapse's [cache auto-tuning functionality](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values). This work and the default values used by the playbook are inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/deployment/synapse.html)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:440
+msgid "The playbook has always used a very conservative cache factor (`matrix_synapse_caches_global_factor`) value of `0.5`, which may be OK for small and underactive deployments, but is not ideal for larger servers. Paradoxically, a small global cache factor value [does not necessarily decrease RAM usage as a whole](https://github.com/matrix-org/synapse/issues/3939)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:442
+msgid "The playbook now uses **a 20x larger cache factor** (currently `10`), adjusts a few other cache-related variables, and **enables cache auto-tuning** via the following variables:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:444
+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 ""
+
+#: ../../../CHANGELOG.md:445
+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 ""
+
+#: ../../../CHANGELOG.md:446
+msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:448
+msgid "These values should be good defaults for most servers, but may change over time as we experiment further."
+msgstr ""
+
+#: ../../../CHANGELOG.md:450
+msgid "Refer to our new [Tuning caches and cache autotuning](docs/maintenance-synapse.md#tuning-caches-and-cache-autotuning) documentation section for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:453
+msgid "2024-01-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:455
+msgid "(Backward-compatibility break) Minor changes necessary for some people serving a static website at the base domain"
+msgstr ""
+
+#: ../../../CHANGELOG.md:457
+msgid "This only affects people who are [Serving a static website at the base domain](./docs/configuring-playbook-base-domain-serving.md#serving-a-static-website-at-the-base-domain), but not managing its `index.html` through the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:459
+msgid "That is, for people who have `matrix_static_files_file_index_html_enabled: false` in their `vars.yml` configuration, the playbook has a new default behavior. Since the playbook is not managing the `index.html` file, it will default to a more sensible way of handling the base domain  - redirecting `https://example.com/` to `https://matrix.example.com/`, instead of serving a 404 page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:461
+msgid "If you are managing your static website by yourself (by dropping files into `/matrix/static-files/public` somehow), then you probably don't wish for such redirection to happen. You can disable it by adding `matrix_static_files_container_labels_base_domain_root_path_redirection_enabled: false` to your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:464
+msgid "2024-01-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:466
+msgid "Support for more efficient (specialized) Synapse workers"
+msgstr ""
+
+#: ../../../CHANGELOG.md:468
+msgid "Thanks to [Charles Wright](https://github.com/cvwright) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook has [received support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3100) for load-balancing the Synapse workload via [specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) which are supposed to work better than our old [generic workers](./docs/configuring-playbook-synapse.md#generic-workers) implementation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:470
+msgid "For now, playbook defaults remain unchanged and the `one-of-each` [workers preset](./docs/configuring-playbook-synapse.md#worker-presets) continues being the default. However, the default may change in the future. If you'd like to remain on this preset even if/when the defaults change, consider explicitly adding `matrix_synapse_workers_preset: one-of-each` to your `vars.yml` configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:472
+msgid "Our specialized workers setup is based on recommendations found in [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). What's special about our new setup is that we try to parse information out of the request (who the user is; which room is being operated on) and try to forward similar requests to the same worker. As an example, this means that once a worker caches some room information, subsequent requests for the same room will be routed to the same worker (which supposedly still has the room's state cached)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:474
+msgid "To get started, refer to our [Specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) documentation section."
+msgstr ""
+
+#: ../../../CHANGELOG.md:477
+msgid "2024-01-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:479
+msgid "Switching to Element's AGPLv3-licensed Synapse release"
+msgstr ""
+
+#: ../../../CHANGELOG.md:481
+msgid "A few months ago, the [Element](https://element.io/) company has [announced](https://element.io/blog/element-to-adopt-agplv3/) that their work on the Synapse homeserver would no longer be available under the permissive [Apache-2.0 license](https://www.apache.org/licenses/LICENSE-2.0), but only under:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:483
+msgid "the [AGPLv3](https://www.gnu.org/licenses/agpl-3.0.en.html) free-software license - the same license that this Ansible playbook has always used"
+msgstr ""
+
+#: ../../../CHANGELOG.md:484
+msgid "a proprietary license, for those wishing for Element to [sell them an exception](https://gnu.org/philosophy/selling-exceptions.html) to the AGPLv3 license"
+msgstr ""
+
+#: ../../../CHANGELOG.md:486
+msgid "You can also learn more in [this post](https://matrix.org/blog/2023/11/06/future-of-synapse-dendrite/) by the Matrix Foundation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:488
+msgid "The change has [already happened](https://element.io/blog/synapse-now-lives-at-github-com-element-hq-synapse/) and the first Synapse release under the new license is here: [v1.99.0](https://github.com/element-hq/synapse/releases/tag/v1.99.0)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:490
+msgid "There is no up-to-date alternative Synapse fork right now and this free-software (AGPLv3-licensed) playbook is definitely not against free-software licenses, so we are now switching to the Element-maintained Synapse release."
+msgstr ""
+
+#: ../../../CHANGELOG.md:492
+msgid "**What does this mean to you?**"
+msgstr ""
+
+#: ../../../CHANGELOG.md:494
+msgid "For most home users, it doesn't mean anything. Your installation will continue working as it should and you don't need to do anything."
+msgstr ""
+
+#: ../../../CHANGELOG.md:496
+msgid "For people building commercial products on top of Synapse, they may have to either buy a license exception from Element (from what we hear, the fee depends on the number of monthly-active users on your instance) or they may need to release all related code as free-software (which is what we've been doing at [etke.cc](https://etke.cc/) ([here](https://gitlab.com/etke.cc)) all along)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:498
+msgid "We're no lawyers and this changelog entry does not aim to give you the best legal advice, so please research on your own!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:500
+msgid "If you'd like to continue using the old Apache-2.0-licensed Synapse (for a while longer anyway), the playbook makes it possible by intruducing a new Ansible variable. You can do it like this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:512
+msgid "Notes:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:514
+msgid "if you had already upgraded Synapse to `v1.99.0` by running this playbook, you will still be able to downgrade to `v1.98.0`, because both releases use the same database schema version (`SCHEMA_COMPAT_VERSION = 83` - see [here for v1.98.0](https://github.com/element-hq/synapse/blob/v1.98.0/synapse/storage/schema/__init__.py#L131-L134) and [here for v1.99.0](https://github.com/element-hq/synapse/blob/v1.99.0/synapse/storage/schema/__init__.py#L137-L140)). More details on Synapse's database schema are available [here](https://element-hq.github.io/synapse/develop/development/database_schema.html). It appears that there are no new database migrations introduced in `v1.99.0`, so going back to the older release is possible. This is not guaranteed to hold true for future Synapse releases, so if you're seeing this early-enough, consider pinning the version and organization before re-running the playbook and getting upgraded to the latest version"
+msgstr ""
+
+#: ../../../CHANGELOG.md:516
+msgid "running an outdated homeserver exposes you to security issues and incompatibilities. Only consider doing this as a short-term solution."
+msgstr ""
+
+#: ../../../CHANGELOG.md:518
+msgid "2024-01-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:520
+msgid "`Draupnir` has been relicensed to AFL-3.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:522
+msgid "As of [#204](https://github.com/the-draupnir-project/Draupnir/pull/204) Draupnir changed its licence to AFL-3.0 from the CSL licence. This change affects playbook users who could not run Draupnir under the old license restrictions. The new license is considerably less restrictive and is OSI approved. Draupnir version v1.86.0 and later are covered by this license change."
+msgstr ""
+
+#: ../../../CHANGELOG.md:524
+msgid "2024-01-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:526
+msgid "Goodbye, `matrix-nginx-proxy` 🪦"
+msgstr ""
+
+#: ../../../CHANGELOG.md:528
+msgid "**TLDR**: All traces of the `matrix-nginx-proxy` reverse-proxy component are now gone. This brought about many other internal changes (and security improvements), so setups may need minor adjustments or suffer some (temporary) breakage. People who have been on the Traefik-native setup may upgrade without much issues. Those running their own Traefik instance may need minor changes. People who have been postponing the migration away from `matrix-nginx-proxy` (for more than a year already!) will now finally need to do something about it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:530
+msgid "Backstory on `matrix-nginx-proxy`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:532
+msgid "We gather here today to celebrate the loss of a once-beloved component in our stack - `matrix-nginx-proxy`. It's been our [nginx](https://nginx.org/)-based reverse-proxy of choice since the [first commit](https://github.com/spantaleev/matrix-docker-ansible-deploy/tree/87f5883f2455fb115457b65f267f17de305c053c) of this playbook, 7 years ago."
+msgstr ""
+
+#: ../../../CHANGELOG.md:534
+msgid "For 6 years, `matrix-nginx-proxy` has been the front-most reverse-proxy in our setup (doing SSL termination, etc.). After [transitioning to Traefik last year](#traefik-is-the-default-reverse-proxy-now), `matrix-nginx-proxy` took a step back. Nevertheless, since it was so ingrained into the playbook, it still remained in use - even if only internally. Despite our warnings of its imminent death, many of you have indubitably continued to use it instead of Traefik. Its suffering continued for too long, because it served many different purposes and massive effort was required to transition them to others."
+msgstr ""
+
+#: ../../../CHANGELOG.md:536
+msgid "To us, `matrix-nginx-proxy` was:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:538
+msgid "an [nginx](https://nginx.org/)-based reverse-proxy"
+msgstr ""
+
+#: ../../../CHANGELOG.md:539
+msgid "an Ansible role organizing the work of [certbot](https://certbot.eff.org/) - retrieving free [Let's Encrypt](https://letsencrypt.org/) SSL certificates for `matrix-nginx-proxy` and for the [Coturn TURN server](./docs/configuring-playbook-turn.md)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:540
+msgid "a central component for reverse-proxying to the [long list of services](./docs/configuring-playbook.md) supported by the playbook. As such, it became a dependency that all these services had to inject themselves into during runtime"
+msgstr ""
+
+#: ../../../CHANGELOG.md:541
+msgid "an intermediary through which addons (bridges, bots) communicated with the homeserver. Going through an intermediary (instead of directly talking to the homeserver) is useful when certain components (like [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) are enabled, because it lets these services \"steal routes\" from the homeserver"
+msgstr ""
+
+#: ../../../CHANGELOG.md:542
+msgid "a webserver for serving the `/.well-known/matrix` static files (generated by the `matrix-base` role until now)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:543
+msgid "a webserver [serving your base domain](./docs/configuring-playbook-base-domain-serving.md) (and also generating the `index.html` page for it)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:544
+msgid "a central component providing global [HTTP Basic Auth](https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication) password-protection for all `/metrics` endpoints when metrics were exposed publicly for consumption from a remote Prometheus server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:546
+msgid "Talk about a jack of all trades! The [UNIX philosophy](https://en.wikipedia.org/wiki/Unix_philosophy) (and Docker container philosophy) of \"do one thing and do it well\" had been severely violated for too long."
+msgstr ""
+
+#: ../../../CHANGELOG.md:548
+msgid "On a related note, we also had a large chain of reverse-proxies in the mix. In the worst case, it was something like this: (Traefik -> `matrix-nginx-proxy:8080` -> `matrix-nginx-proxy:12080` -> `matrix-synapse-reverse-proxy-companion:8008` -> `matrix-synapse:8008`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:550
+msgid "Due to complexity and the playbook's flexibility (trying to accommodate a mix of tens of components), many layers of indirection were necessary. We do like reverse-proxies, but.. not quite enough to enjoy going through a chain of ~4 of them before reaching the target service."
+msgstr ""
+
+#: ../../../CHANGELOG.md:552
+msgid "After **a ton of work** in the last weeks (200+ commits, which changed 467 files - 8684 insertions and 8913 deletions), **we're finally saying goodbye** to `matrix-nginx-proxy`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:554
+msgid "Going Traefik-native and cutting out all middlemen"
+msgstr ""
+
+#: ../../../CHANGELOG.md:556
+msgid "In our new setup, you'll see the bare minimum number of reverse-proxies."
+msgstr ""
+
+#: ../../../CHANGELOG.md:558
+msgid "In most cases, there's only Traefik and all services being registered directly with it. When [Synapse workers](./docs/configuring-playbook-synapse.md#load-balancing-with-workers) are enabled, `matrix-synapse-reverse-proxy-companion` remains as an extra reverse-proxy that requests go through (for load-balancing to the correct Synapse worker), but in all other cases services are exposed directly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:560
+msgid "This reduces \"network\" hops (improving performance) and also decreases the number of components (containers). Each Ansible role in our setup is now independent and doesn't need to interact with other roles during runtime."
+msgstr ""
+
+#: ../../../CHANGELOG.md:562
+msgid "Traefik now has an extra job"
+msgstr ""
+
+#: ../../../CHANGELOG.md:564
+msgid "Previously, **Traefik had a single purpose** - being the main reverse-proxy. It was either front-most (terminating SSL, etc.) or you were [fronting Traefik with your own other reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy). In any case - it had this central (yet decentralized) job."
+msgstr ""
+
+#: ../../../CHANGELOG.md:566
+msgid "Now, **Traefik has one more role** - it serves as an intermediary which allows addon services (bridges, bots, etc.) to communicate with the homeserver. As mentioned above, such an intermediary service is not strictly necessary in all kinds of setups, but more complex setups (including [matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md) or [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md)) benefit from it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:568
+msgid "To perform this new role, Traefik now has a new internal [entrypoint](https://doc.traefik.io/traefik/routing/entrypoints/) called `matrix-internal-matrix-client-api`. All homeservers (Conduit, Dendrite, Synapse and even `matrix-synapse-reverse-proxy-companion`) and homeserver-related core services ([matrix-media-repo](./docs/configuring-playbook-matrix-media-repo.md), [matrix-corporal](./docs/configuring-playbook-matrix-corporal.md) and potentially others) register their routes (using [container labels](https://docs.docker.com/config/labels-custom-metadata/)) not only on the public entrypoints (`web-secure`, `matrix-federation`), but also on this new internal entrypoint."
+msgstr ""
+
+#: ../../../CHANGELOG.md:570
+msgid "Doing so, services can contact Traefik on this entrypoint's dedicated port (the URL defaults to `http://matrix-traefik:8008`) and reach the homeserver Client-Server API as they expect. Internally, Traefik takes care of the routing to the correct service."
+msgstr ""
+
+#: ../../../CHANGELOG.md:572
+msgid "We've also considered keeping it simple and having services talk to the homeserver over the public internet (e.g. `https://matrix.example.com`) thus reusing all existing Traefik routing labels. In this scenario, performance was incredibly poor (e.g. 70 rps, instead of 1400 rps) due to TLS and networking overhead. The need for fast internal communication (via the new internal non-TLS-enabled Traefik entrypoint) is definitely there. In our benchmarks, Traefik even proved more efficient than nginx at doing this: ~1200 rps for Traefik compared to ~900 rps for nginx (out of ~1400 rps when talking to the Synapse homeserver directly)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:574
+msgid "Traefik serving this second purpose has a few downsides:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:576
+msgid "Traefik becomes a runtime dependency for all homeserver-dependant container services"
+msgstr ""
+
+#: ../../../CHANGELOG.md:577
+msgid "all homeserver-dependant services now need to be connected to the `traefik` container network, even if they don't need public internet exposure"
+msgstr ""
+
+#: ../../../CHANGELOG.md:579
+msgid "Despite these downsides (which the playbook manages automatically), we believe it's still a good compromise given the amount of complexity it eliminates and the performance benefits it yields. One alternative we've [considered](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3045#issuecomment-1867327001) was adding a new intermediary service (e.g. `matrix-homeserver-proxy` powered by nginx), but this both had much higher complexity (one more component in the mix; duplication of effort to produce nginx-compatible route definitions for it) and slightly worse performance (see above)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:581
+msgid "People running the default Traefik setup do not need to do anything to make Traefik take on this extra job. Your Traefik configuration will be updated automatically."
+msgstr ""
+
+#: ../../../CHANGELOG.md:583
+msgid "**People runnning their own Traefik reverse-proxy need to do [minor adjustments](#people-managing-their-own-traefik-instance-need-to-do-minor-changes)**, as described in the section below."
+msgstr ""
+
+#: ../../../CHANGELOG.md:585
+msgid "You may disable Traefik acting as an intermediary by explicitly setting `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_enabled` to `false`. Services would then be configured to talk to the homeserver directly, giving you a slight performance boost and a \"simpler\" Traefik setup. However, such a configuration is less tested and will cause troubles, especially if you enable more services (like `matrix-media-repo`, etc.) in the future. As such, it's not recommended."
+msgstr ""
+
+#: ../../../CHANGELOG.md:587
+msgid "People managing their own Traefik instance need to do minor changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:589
+msgid "This section is for people [managing their own Traefik instance on the Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you). Those [using Traefik managed by the playbook](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) don't need to do any changes."
+msgstr ""
+
+#: ../../../CHANGELOG.md:591
+msgid "Because [Traefik has an extra job now](#traefik-now-has-an-extra-job), you need to adapt your configuration to add the additional `matrix-internal-matrix-client-api` entrypoint and potentially configure the `matrix_playbook_reverse_proxy_container_network` variable. See the [Traefik managed by you](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you) documentation section for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:593
+msgid "People fronting Traefik with another reverse proxy need to do minor changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:595
+msgid "We've already previously mentioned that you need to do some minor [configuration changes related to `traefik_additional_entrypoints_auto`](#backward-compatibility-configuration-changes-required-for-people-fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:597
+msgid "If you don't do these changes (switching from `traefik_additional_entrypoints_auto` to multiple other variables), your Traefik setup will not automatically receive the new `matrix-internal-matrix-client-api` Traefik entrypoint and Traefik would not be able to perform [its new duty of connecting addons with the homeserver](#traefik-now-has-an-extra-job)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:599
+msgid "Supported reverse proxy types are now fewer"
+msgstr ""
+
+#: ../../../CHANGELOG.md:601
+msgid "This section is for people using a more custom reverse-proxy setup - those having `matrix_playbook_reverse_proxy_type` set to a value different than the default (`playbook-managed-traefik`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:603
+msgid "Previously, we allowed you to set `matrix_playbook_reverse_proxy_type` to 7 different values to accommodate various reverse-proxy setups."
+msgstr ""
+
+#: ../../../CHANGELOG.md:605
+msgid "The complexity of this is too high, so we only support 3 values right now:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:607
+msgid "(the default) `playbook-managed-traefik`, when you're [using Traefik managed by the playbook](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:608
+msgid "`other-traefik-container`, when you're [managing your own Traefik instance on the Matrix server](./docs/configuring-playbook-own-webserver.md#traefik-managed-by-you)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:609
+msgid "`none`, when you wish for [no reverse-proxy integration to be done at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:611
+msgid "The `none` value is not recommended and may not work adequately, due to lack of testing and [Traefik's new responsibilities](#traefik-now-has-an-extra-job) in our setup."
+msgstr ""
+
+#: ../../../CHANGELOG.md:613
+msgid "**Previous values that are now gone** (and the playbook would report them as such) are: `playbook-managed-nginx`, `other-nginx-non-container`, `other-on-same-host` and `other-on-another-host`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:615
+msgid "If you were using these values as a way to stay away from Traefik, you now have 2 options:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:617
+msgid "(recommended) [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:618
+msgid "(not recommended) [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all) and reverse-proxying to each and every service manually"
+msgstr ""
+
+#: ../../../CHANGELOG.md:620
+msgid "Container networking changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:622
+msgid "Now that `matrix-nginx-proxy` is not in the mix, it became easier to clear out some other long-overdue technical debt."
+msgstr ""
+
+#: ../../../CHANGELOG.md:624
+msgid "Since the very beginning of this playbook, all playbook services were connected to a single (shared) `matrix` container network. Later on, some additional container networks appeared, but most services (database, etc.) still remained in the `matrix` container network.  This meant that any random container in this network could try to talk (or attack) the Postgres database operating in the same `matrix` network."
+msgstr ""
+
+#: ../../../CHANGELOG.md:626
+msgid "Moving components (especially the database) into other container networks was difficult - it required changes to many other components to ensure correct connectivity."
+msgstr ""
+
+#: ../../../CHANGELOG.md:628
+msgid "All the hard work has been done now. We've added much more isolation between services by splitting them up into separate networks (`matrix-homeserver`, `matrix-addons`, `matrix-monitoring`, `matrix-exim-relay`, etc). Components are only joined to the networks they need and should (for the most part) not be able to access unrelated things."
+msgstr ""
+
+#: ../../../CHANGELOG.md:630
+msgid "Carrying out these container networking changes necessitated modifying many components, so **we're hoping not too many bugs were introduced in the process**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:632
+msgid "We've refrained from creating too many container networks (e.g. one for each component), to avoid exhausting Docker's default network pool and contaminating the container networks list too much."
+msgstr ""
+
+#: ../../../CHANGELOG.md:634
+msgid "Metrics exposure changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:636
+msgid "This section is for people who are exposing monitoring metrics publicly, to be consumed by an external Prometheus server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:638
+msgid "Previously, `matrix-nginx-proxy` was potentially password-protecting all `/metrics/*` endpoints with the same username and password (specified as plain-text in your `vars.yml` configuration file)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:640
+msgid "From now on, there are new variables for doing roughly the same - `matrix_metrics_exposure_enabled`, `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`. See the [Prometheus & Grafana](./docs/configuring-playbook-prometheus-grafana.md) docs page for details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:642
+msgid "`matrix-nginx-proxy` is not acting as a \"global guardian\" anymore. Now, each role provides its own metrics exposure and protection by registering with Traefik. Nevertheless, all roles are wired (via playbook configuration in `group_vars/matrix_servers`) to obey these new `matrix_metrics_exposure_*` variables. We've eliminated the centralization, but have kept the ease of use. Now, you can also do per-service password-protection (with different credentials), should you need to do that for some reason."
+msgstr ""
+
+#: ../../../CHANGELOG.md:644
+msgid "The playbook will tell you about all variables that you need to migrate during runtime, so rest assured - you shouldn't be able to miss anything!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:646
+msgid "Matrix static files"
+msgstr ""
+
+#: ../../../CHANGELOG.md:648
+msgid "As mentioned above, static files like `/.well-known/matrix/*` or your base domain's `index.html` file (when [serving the base domain via the Matrix server](./docs/configuring-playbook-base-domain-serving.md) was enabled) were generated by the `matrix-base` or `matrix-nginx-proxy` roles and put into a `/matrix/static-files` directory on the server. Then `matrix-nginx-proxy` was serving all these static files."
+msgstr ""
+
+#: ../../../CHANGELOG.md:650
+msgid "All of this has been extracted into a new `matrix-static-files` Ansible role that's part of the playbook. The static files generated by this new role still live at roughly the same place (`/matrix/static-files/public` directory, instead of `/matrix/static-files`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:652
+msgid "The playbook will migrate and update the `/.well-known/matrix/*` files automatically but not your own files in `nginx-proxy/data/matrix-domain/` you will need to back these up yourself otherwise they will be lost. It will also warn you about usage of old variable names, so you can adapt to the new names."
+msgstr ""
+
+#: ../../../CHANGELOG.md:654
+msgid "A note on performance"
+msgstr ""
+
+#: ../../../CHANGELOG.md:656
+msgid "Some of you have been voicing their concerns (for a long time) about Traefik being too slow and nginx being better."
+msgstr ""
+
+#: ../../../CHANGELOG.md:658
+msgid "Some online benchmarks support this by demonstrating slightly higher SSL-termination performance in favor of nginx. The upcoming Traefik v3 release is [said to](https://medium.com/beyn-technology/is-nginx-dead-is-traefik-v3-20-faster-than-traefik-v2-f28ffb7eed3e) improve Traefik's SSL performance by some 20%, but that still ends up being somewhat slower than nginx."
+msgstr ""
+
+#: ../../../CHANGELOG.md:660
+msgid "We believe that using Traefik provides way too many benefits to worry about this minor performance impairment."
+msgstr ""
+
+#: ../../../CHANGELOG.md:662
+msgid "The heaviest part of running a Matrix homeserver is all the slow and potentially inefficient things the homeserver (e.g. Synapse) is doing. These things affect performance much more than whatever reverse-proxy is in front. Your server will die the same way by joining the famously large **Matrix HQ** room, no matter which reverse-proxy you put in front."
+msgstr ""
+
+#: ../../../CHANGELOG.md:664
+msgid "Even our previously mentioned benchmarks (yielding ~1300 rps) are synthetic - hitting a useless `/_matrix/client/versions` endpoint. Real-use does much more than this."
+msgstr ""
+
+#: ../../../CHANGELOG.md:666
+msgid "If this is still not convincing enough for you and you want the best possible performance, consider [Fronting Traefik with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) (thus having the slowest part - SSL termination - happen elsewhere) or [Using no reverse-proxy on the Matrix side at all](./docs/configuring-playbook-own-webserver.md#using-no-reverse-proxy-on-the-matrix-side-at-all). The playbook will not get in your way of doing that, but these options may make your life much harder. Performance comes at a cost, after all."
+msgstr ""
+
+#: ../../../CHANGELOG.md:668
+msgid "Migration procedure"
+msgstr ""
+
+#: ../../../CHANGELOG.md:670
+msgid "The updated playbook will automatically perform some migration tasks for you:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:672
+msgid "It will stop and remove the `matrix-nginx-proxy` systemd service and container for you. This behavior cannot be disabled. It's essential that this service gets stopped, because it remaining running (and having container labels) may confuse Traefik as to where to route HTTP requests."
+msgstr ""
+
+#: ../../../CHANGELOG.md:674
+msgid "It will delete the `/matrix/nginx-proxy` directory and all files within it. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_uninstallation_enabled: false` to your `vars.yml` configuration file. Doing so will leave its data around."
+msgstr ""
+
+#: ../../../CHANGELOG.md:676
+msgid "It will delete the `/matrix/ssl` directory and all files within it. You can disable this behavior by adding `matrix_playbook_migration_matrix_ssl_uninstallation_enabled: false` to your `vars.yml` configuration file. If you have some important certificates there for some reason, take them out or temporarily disable removal of these files until you do."
+msgstr ""
+
+#: ../../../CHANGELOG.md:678
+msgid "It will tell you about all variables (`matrix_nginx_proxy_*` and many others - even from other roles) that have changed during this large nginx-elimination upgrade. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_elimination_variable_transition_checks_enabled: false` to your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:680
+msgid "It will tell you about any leftover `matrix_nginx_proxy_*` variables in your `vars.yml` file. You can disable this behavior by adding `matrix_playbook_migration_matrix_nginx_proxy_leftover_variable_validation_checks_enabled: false` to your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:682
+msgid "It will tell you about any leftover `matrix_ssl_*` variables in your `vars.yml` file. You can disable this behavior by adding `matrix_playbook_migration_matrix_ssl_leftover_variable_checks_enabled: false` to your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:684
+msgid "We don't recommend changing these variables and suppressing warnings, unless you know what you're doing."
+msgstr ""
+
+#: ../../../CHANGELOG.md:686
+msgid "**Most people should just upgrade as per-normal**, bearing in mind that a lot has changed and some issues may arise. The playbook would guide you through renamed variables automatically."
+msgstr ""
+
+#: ../../../CHANGELOG.md:688
+msgid "Conclusion"
+msgstr ""
+
+#: ../../../CHANGELOG.md:690
+msgid "Thousands of lines of code were changed across hundreds of files. All addons (bridges, bots) were rewired in terms of container networking and in terms of how they reach the homeserver."
+msgstr ""
+
+#: ../../../CHANGELOG.md:692
+msgid "I don't actively use all the ~100 components offered by the playbook (no one does), nor do I operate servers exercising all edge-cases. As such, issues may arise. Please have patience and report (or try to fix) these issues!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:695
+msgid "2024-01-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:697
+msgid "(Backward Compatibility) Configuration changes required for people fronting the integrated reverse-proxy webserver with another reverse-proxy"
+msgstr ""
+
+#: ../../../CHANGELOG.md:699
+msgid "If you're on the default setup (using the Traefik reverse-proxy as installed by the playbook), you don't need to do anything."
+msgstr ""
+
+#: ../../../CHANGELOG.md:701
+msgid "People who are [Fronting the integrated Traefik reverse-proxy webserver with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy), as per our previous instructions are redefining `traefik_additional_entrypoints_auto` in their `vars.yml` configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:703
+msgid "Such a full variable redefinion is intrustive, because it prevents the playbook from injecting additional entrypoints into the Traefik webserver. In the future, the playbook may have a need to do so."
+msgstr ""
+
+#: ../../../CHANGELOG.md:705
+msgid "For this reason, we no longer recommend completely redefining `traefik_additional_entrypoints_auto`. The playbook now defines [various `matrix_playbook_public_matrix_federation_api_traefik_entrypoint_*` variables in the `defaults/main.yml` file](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/roles/custom/matrix-base/defaults/main.yml) of the `matrix-base` role which can be used as a safer alternative to `traefik_additional_entrypoints_auto`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:707
+msgid "Adapt your configuration as seen below:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:740
+msgid "Also, feel free to read the [Fronting the integrated Traefik reverse-proxy webserver with another reverse-proxy](./docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) documentation section again for additional details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:743
+msgid "2024-01-13"
+msgstr ""
+
+#: ../../../CHANGELOG.md:745
+msgid "matrix-reminder-bot update with more secure (backward-incompatible) default settings"
+msgstr ""
+
+#: ../../../CHANGELOG.md:747
+msgid "**TLDR**: your updated (to [v0.3.0](https://github.com/anoadragon453/matrix-reminder-bot/releases/tag/v0.3.0)) [matrix-reminder-bot](./docs/configuring-playbook-bot-matrix-reminder-bot.md) is now more secure. By default, like other bridges/bots managed by the playbook, it will only provide its services to users of your own server (not to anyone, even across the Matrix Federation). If that's fine, there's nothing you need to do."
+msgstr ""
+
+#: ../../../CHANGELOG.md:749
+msgid "Maintenance of [matrix-reminder-bot](./docs/configuring-playbook-bot-matrix-reminder-bot.md) has been picked up by [Kim Brose](https://github.com/HarHarLinks) and [@svierne](https://github.com/svierne)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:751
+msgid "Thanks to them, a new [v0.3.0](https://github.com/anoadragon453/matrix-reminder-bot/releases/tag/v0.3.0) release is out. The new version is now available for the ARM64 architecture, so playbook users on this architecture will no longer need to wait for [self-building](./docs/self-building.md) to happen."
+msgstr ""
+
+#: ../../../CHANGELOG.md:753
+msgid "The new version also comes with new `allowlist` and `blocklist` settings, which make it possible to restrict who can use the bot. Previously anyone, even across the Matrix Federation could talk to it and schedule reminders."
+msgstr ""
+
+#: ../../../CHANGELOG.md:755
+msgid "The playbook defaults all bridges and bots (where possible) to only be exposed to users of the current homeserver, not users across federation. Thanks to the new version of this bot making such a restriction possible, we're now making use of it. The playbook (via its `group_vars/matrix_servers` file) automatically enables the `allowlist` (`matrix_bot_matrix_reminder_bot_allowlist_enabled: true`) and configures it in such a way (`matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) so as to restrict the bot to your homeserver's users."
+msgstr ""
+
+#: ../../../CHANGELOG.md:757
+msgid "If you need **to undo or tweak these security improvements**, you can change your `vars.yml` file to:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:759
+msgid "disable the allowlist (`matrix_bot_matrix_reminder_bot_allowlist_enabled: false`), making the bot allow usage by anyone, anywhere"
+msgstr ""
+
+#: ../../../CHANGELOG.md:761
+msgid "inject additional allowed servers or users by adding **additional** (on top of the default allowlist in `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`) custom regexes in the `matrix_bot_matrix_reminder_bot_allowlist_regexes_custom` list variable (see the [syntax reference](https://github.com/anoadragon453/matrix-reminder-bot/blob/1e910c0aa3469d280d93ee7e6c6d577227a3460c/sample.config.yaml#L43-L49))"
+msgstr ""
+
+#: ../../../CHANGELOG.md:763
+msgid "override the default allowlist (in the `group_vars/matrix_servers` file) by redefining `matrix_bot_matrix_reminder_bot_allowlist_regexes_auto`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:766
+msgid "2024-01-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:768
+msgid "matrix-mailer has been replaced by the exim-relay external role"
+msgstr ""
+
+#: ../../../CHANGELOG.md:770
+#: ../../../CHANGELOG.md:1410
+msgid "We're continuing our effort to make [the playbook use external roles for some things](#the-playbook-now-uses-external-roles-for-some-things), so as to avoid doing everything ourselves and to facilitate code re-use."
+msgstr ""
+
+#: ../../../CHANGELOG.md:772
+msgid "The `matrix-mailer` role has been moved to its own repository ([ansible-role-exim-relay](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay)) that this playbook now includes."
+msgstr ""
+
+#: ../../../CHANGELOG.md:774
+msgid "To migrate:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:776
+msgid "pull the playbook changes, as usual"
+msgstr ""
+
+#: ../../../CHANGELOG.md:777
+msgid "update your roles (run `just roles` or `make roles`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:778
+msgid "update your `vars.yml`, renaming `matrix_mailer`-prefixed variables to `exim_relay`-prefixed ones (e.g. `matrix_mailer_sender_address` -> `exim_relay_sender_address`). If you find none, it means you're using the default configuration and your migraiton job is even simpler."
+msgstr ""
+
+#: ../../../CHANGELOG.md:779
+msgid "re-run the playbook (`install-all` or `setup-all`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:781
+msgid "The playbook will take care of stopping the old `matrix-mailer` systemd service, relocating its directory and restarting it under the new name (`matrix-exim-relay.service`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:784
+msgid "2024-01-02"
+msgstr ""
+
+#: ../../../CHANGELOG.md:786
+msgid "mautrix-signal now powered by the new Go-based bridge"
+msgstr ""
+
+#: ../../../CHANGELOG.md:788
+msgid "The old Python-based [mautrix-signal](https://github.com/mautrix/signal) bridge is no longer maintained upstream. It's also known to have issues linking new devices."
+msgstr ""
+
+#: ../../../CHANGELOG.md:790
+msgid "It seems like the path forward is to switch to the new mautrix-signal bridge written in Golang, which we did thanks to [PR #3031](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3041) by [Pierre 'McFly' Marty](https://github.com/pm-McFly)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:792
+msgid "The playbook should **automatically migrate your mautrix-signal installation to the new bridge code**. You will **need to relink all your devices** to continue your bridged conversations."
+msgstr ""
+
+#: ../../../CHANGELOG.md:795
+msgid "2023-10-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:797
+msgid "Enabling `allow_public_rooms_over_federation` by default for Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:799
+msgid "**TDLR**: if your Matrix server is federating (which it mostly likely is, unless you've [disabled federation](docs/configuring-playbook-federation.md#disabling-federation)), your public rooms will not only be joinable across federation (as they've always been), but from now on will be discoverable (made available as a list across federation). We're changing this by flipping the value for Synapse's `allow_public_rooms_over_federation` setting to `true`, going against the upstream default. Servers that disable federation are not affected. Servers that have public rooms which are not published to the room directory are also not affected."
+msgstr ""
+
+#: ../../../CHANGELOG.md:801
+msgid "We generally try to stick to the default configuration for Synapse (and all other components), unless these defaults seem wrong or harmful. One such previous case from a few months ago was us [Enabling `forget_rooms_on_leave` by default for Synapse](#enabling-forget_rooms_on_leave-by-default-for-synapse) - the default value was making Synapse more wasteful of resources by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:803
+msgid "Today, we're going against upstream defaults again and flipping the `allow_public_rooms_over_federation` configuration option to `true`. This way, public rooms on your server will be made discoverable by others via federation, using the [`GET /_matrix/federation/v1/publicRooms` of the Server-Server API](https://spec.matrix.org/v1.8/server-server-api/#get_matrixfederationv1publicrooms)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:805
+msgid "The upstream Synapse default is `false` (disabled), so that public rooms are not exposed for other servers to discover (learn about their existence). Nevertheless, even if these rooms are not exposed (listed) for discovery, they are **still joinable** by anyone who knows their address or is invited to the room by an existing member."
+msgstr ""
+
+#: ../../../CHANGELOG.md:807
+msgid "**We go against the upstream default** in an effort to make Matrix federation more useful - a public room should be globally public - not only joinable, but also discoverable across federation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:809
+msgid "The **historical reasoning** behind this change is as follows:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:811
+msgid "`allow_public_rooms_over_federation` seems to have been enabled by default for Synapse until v1.7.0 (~2019), just like we believe it should be for a globally-federating network - rooms should be joinable and discoverable across federation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:813
+msgid "In Synapse v1.7.0 (~2019), `allow_public_rooms_over_federation` [got disabled](https://github.com/element-hq/synapse/blob/e9069c9f919685606506f04527332e83fbfa44d9/docs/upgrade.md?plain=1#L1877-L1891) by default in a [security-by-obscurity](https://en.wikipedia.org/wiki/Security_through_obscurity) workaround for misconfigured servers. See the [Avoiding unwelcome visitors on private Matrix servers](https://matrix.org/blog/2019/11/09/avoiding-unwelcome-visitors-on-private-matrix-servers/) `matrix.org` blog article. We believe that people wishing for a truly private server, should [disable federation](docs/configuring-playbook-federation.md#disabling-federation), instead of having a fully-federating server and trying to hide its public rooms. We also provide other workarounds below. We (and the Synapse team, obviously) believe that Matrix should federate by default, so federating the public room list seems to make sense."
+msgstr ""
+
+#: ../../../CHANGELOG.md:815
+msgid "[etke.cc](https://etke.cc/) has been developing the free-software [Matrix Rooms Search](https://github.com/etkecc/mrs) project for a while now. One public (demo) instance of it is hosted at [matrixrooms.info](https://matrixrooms.info/). This search engine tries to go through the Matrix federation and discover & index public rooms to allow people to find them. We believe it's vital for Matrix (and any chat or social network for that matter) to be more discoverable, so that people can find communities and others to talk to. Today (on 23rd of October 2023), `matrixrooms.info` is indexing `23066` Matrix servers. Of these, only `1567` servers (7%) are making their public rooms discoverable. Who knows what wonderful communities and rooms are available on these 93% other Matrix servers that are supposedly federating, but are still gate-keeping their public room list. Indubitably, many of these servers are hosted via matrix-docker-ansible-deploy, so we feel partially responsible for making Matrix federation less useful."
+msgstr ""
+
+#: ../../../CHANGELOG.md:817
+msgid "Here are **actions you may wish to take** as a result of this change:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:819
+msgid "(recommended) embrace the new default. If your Matrix server is federating, your public rooms have always been joinable across federation anyway. Exposing the list of public rooms does no harm and more-so does good by contributing to the usefulness of the Matrix network by facilitating room discovery."
+msgstr ""
+
+#: ../../../CHANGELOG.md:821
+msgid "(switch to a better way of doings things on your semi-private server) The problem that the Synapse team appears to have solved by flipping the `allow_public_rooms_over_federation` default in Synapse v1.7.0 seems to for \"mostly private\" servers, which federate and have a bunch of rooms made public (and published in their room directory) in an effort to allow people on the same homeserver to easily find and join them (self-onboarding). With the introduction of Matrix Spaces, you can reorganize your flow around spaces - you can auto-join your users to a Matrix Space (via Synapse's `auto_join_rooms` setting - controlled by our `matrix_synapse_auto_join_rooms` variable), then add a bunch of rooms to the space and make them joinable by people belonging to the space. That is to say, do not make rooms public and do not publish them to the room directory unless they are really public. Instead, use other mechanisms for semi-public rooms or private rooms. One alternative is to stick to what you're doing (public rooms published to your rooms directory) but having a `m.federate: true` flag set during creation (clients like Element Web have a nice UI checkbox for this) to explicitly disable federation for them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:823
+msgid "(keeping the old behavior) if you wish to keep doing what you're doing (keeping your Matrix server federating, but hiding its public rooms list), add `matrix_synapse_allow_public_rooms_over_federation: false` to your `vars.yml` configuration. This restores the old behavior. You may also consider [disabling federation](docs/configuring-playbook-federation.md#disabling-federation) completely instead of relying on security-by-obscurity measures."
+msgstr ""
+
+#: ../../../CHANGELOG.md:826
+msgid "2023-10-18"
+msgstr ""
+
+#: ../../../CHANGELOG.md:828
+msgid "Postgres parameters are automatically tuned now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:830
+msgid "The playbook has provided some hints about [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) for quite a while now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:832
+msgid "From now on, the [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) automatically tunes your Postgres configuration with the same [calculation logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) that powers https://pgtune.leopard.in.ua/."
+msgstr ""
+
+#: ../../../CHANGELOG.md:834
+msgid "Our [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) documentation page has details about how you can turn auto-tuning off or adjust the automatically-determined Postgres configuration parameters manually."
+msgstr ""
+
+#: ../../../CHANGELOG.md:836
+msgid "People who [enable load-balancing with Synapse workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) no longer need to increase the maximum number of Postgres connections manually (previously done via `postgres_process_extra_arguments`). There's a new variable (`postgres_max_connections`) for controlling this number and the playbook automatically raises its value from `200` to `500` for setups which enable workers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:839
+msgid "2023-08-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:841
+msgid "SchildiChat Web support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:843
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client."
+msgstr ""
+
+#: ../../../CHANGELOG.md:845
+msgid "See our [Configuring SchildiChat Web](docs/configuring-playbook-client-schildichat-web.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:848
+msgid "2023-08-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:850
+msgid "mautrix-wsproxy support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:852
+msgid "Thanks to [Johan Swetzén](https://github.com/jswetzen)'s efforts (who finished what was started by [James Reilly](https://github.com/hanthor) and [Shreyas Ajjarapu](https://github.com/shreyasajj)), the playbook now supports bridging to Android SMS and Apple iMessage via the [mautrix-wsproxy](https://github.com/mautrix/wsproxy) service (in combination with a [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android phone)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:854
+msgid "See our [Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](docs/configuring-playbook-bridge-mautrix-wsproxy.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:857
+msgid "2023-07-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:859
+msgid "matrix-registration-bot usage changed"
+msgstr ""
+
+#: ../../../CHANGELOG.md:861
+msgid "[matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) got some updates and now supports password-only-based login. Therefore the bot now doesn't need any manual configuration except setting a password in your `vars.yml`. The bot will be registered as admin and access tokens will be obtained automatically by the bot."
+msgstr ""
+
+#: ../../../CHANGELOG.md:863
+msgid "**For existing users** You need to set `matrix_bot_matrix_registration_bot_bot_password` if you previously only used `matrix_bot_matrix_registration_bot_bot_access_token`. Please also remove the following deprecated settings"
+msgstr ""
+
+#: ../../../CHANGELOG.md:865
+msgid "`matrix_bot_matrix_registration_bot_bot_access_token`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:866
+msgid "`matrix_bot_matrix_registration_bot_api_token`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:869
+msgid "2023-07-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:871
+msgid "mautrix-gmessages support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:873
+msgid "Thanks to [Shreyas Ajjarapu](https://github.com/shreyasajj)'s efforts, the playbook now supports bridging to [Google Messages](https://messages.google.com/) via the [mautrix-gmessages](https://github.com/mautrix/gmessages) bridge. See our [Setting up Mautrix Google Messages bridging](docs/configuring-playbook-bridge-mautrix-gmessages.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:876
+msgid "2023-07-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:878
+msgid "matrix-media-repo support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:880
+msgid "Thanks to [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/), the playbook can now set up [matrix-media-repo](https://github.com/turt2live/matrix-media-repo) - an alternative way to store homeserver media files, powered by a homeserver-independent implementation which supports S3 storage, IPFS, deduplication and other advanced features."
+msgstr ""
+
+#: ../../../CHANGELOG.md:882
+msgid "To learn more see our [Storing Matrix media files using matrix-media-repo](docs/configuring-playbook-matrix-media-repo.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:885
+msgid "2023-05-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:887
+msgid "Enabling `forget_rooms_on_leave` by default for Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:889
+msgid "With the [Synapse v1.84.0 update](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2698), we've also **changed the default value** of the `forget_rooms_on_leave` setting of Synapse to a value of `true`. This way, **when you leave a room, Synapse will now forget it automatically**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:891
+msgid "The upstream Synapse default is `false` (disabled), so that you must forget rooms manually after leaving."
+msgstr ""
+
+#: ../../../CHANGELOG.md:893
+msgid "**We go against the upstream default** ([somewhat controversially](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2700)) in an effort to make Synapse leaner and potentially do what we believe most users would expect their homeserver to be doing."
+msgstr ""
+
+#: ../../../CHANGELOG.md:895
+msgid "If you'd like to go back to the old behavior, add the following to your configuration: `matrix_synapse_forget_rooms_on_leave: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:898
+msgid "2023-04-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:900
+msgid "The matrix-jitsi role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:902
+msgid "**TLDR**: the `matrix-jitsi` role is now included from the [ansible-role-jitsi](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi) repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:904
+msgid "The `matrix-jitsi` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project - an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Jitsi stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so."
+msgstr ""
+
+#: ../../../CHANGELOG.md:906
+msgid "As part of the extraction process of this role out of the Matrix playbook, a few other things improved:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:908
+msgid "**native Traefik support** has been added"
+msgstr ""
+
+#: ../../../CHANGELOG.md:909
+msgid "**support for hosting under a subpath** has been added, although it suffers from a few minor issues listed [here](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/jitsi.md#url)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:911
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Jitsi or not."
+msgstr ""
+
+#: ../../../CHANGELOG.md:913
+msgid "If you're making use of Jitsi via this playbook, you will need to update variable references in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:915
+msgid "`matrix_jitsi_*_docker_image_` -> `matrix_jitsi_*_container_image_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:916
+msgid "`matrix_jitsi_` -> `jitsi_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:917
+#: ../../../CHANGELOG.md:944
+msgid "some other internal variables have changed, but the playbook will tell you about them"
+msgstr ""
+
+#: ../../../CHANGELOG.md:919
+msgid "2023-03-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:921
+msgid "ntfy Web App is disabled by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:923
+msgid "ntfy provides a web app, which is now disabled by default, because it may be unknown to and unused by most users of this playbook. You can enable it by setting `ntfy_web_root: \"app\"` (see [ntfy documentation](docs/configuring-playbook-ntfy.md))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:925
+msgid "This change was already applied a while before this entry, but as some users were reporting the missing web app, this entry was added (see [#2529](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2529))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:928
+msgid "2023-03-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:930
+msgid "The matrix-prometheus role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:932
+msgid "**TLDR**: the `matrix-prometheus` role is now included from the [ansible-role-prometheus](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus) repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook). Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:934
+msgid "The `matrix-prometheus` role has been relocated in its own repository, part of the [MASH playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) project - an Ansible playbook for self-hosting [a growing list of FOSS software](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md). If hosting a Prometheus stack on the Matrix server itself did not stand right with you or you always wanted to host most stuff, you can now use this new playbook to do so."
+msgstr ""
+
+#: ../../../CHANGELOG.md:936
+msgid "Extracting the Prometheus role out of this Matrix playbook required huge internal refactoring to the way the Prometheus configuration (scraping jobs) is generated. If you notice any breakage after upgrading, let us know."
+msgstr ""
+
+#: ../../../CHANGELOG.md:938
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Prometheus or not."
+msgstr ""
+
+#: ../../../CHANGELOG.md:940
+msgid "If you're making use of Prometheus via this playbook, you will need to update variable references in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:942
+msgid "`matrix_prometheus_docker_image_` -> `matrix_prometheus_container_image_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:943
+msgid "`matrix_prometheus_` -> `prometheus_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:947
+msgid "2023-03-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:949
+msgid "synapse-auto-compressor support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:951
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state)'s `synapse_auto_compressor` tool to run periodically."
+msgstr ""
+
+#: ../../../CHANGELOG.md:953
+msgid "If enabled, `synapse_auto_compressor` runs on a schedule and compresses your Synapse database's `state_groups` table. It was possible to run `rust-synapse-compress-state` manually via the playbook even before - see [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state). However, using `synapse_auto_compressor` is better, because:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:955
+msgid "it runs on a more up-to-date version of `rust-synapse-compress-state`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:956
+msgid "it's a set-it-and-forget-it tool that you can enable and never have to deal with manual compression anymore"
+msgstr ""
+
+#: ../../../CHANGELOG.md:958
+msgid "This tool needs to be enabled manually, for now. In the future, we're considering enabling it by default for all Synapse installations."
+msgstr ""
+
+#: ../../../CHANGELOG.md:960
+msgid "See our [Setting up synapse-auto-compressor](docs/configuring-playbook-synapse-auto-compressor.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:963
+msgid "2023-03-07"
+msgstr ""
+
+#: ../../../CHANGELOG.md:965
+msgid "Sliding Sync proxy (Element X) support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:967
+msgid "Thanks to [Benjamin Kampmann](https://github.com/gnunicorn) for [getting it started](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2515), [FSG-Cat](https://github.com/FSG-Cat) for fixing it up and me ([Slavi](https://github.com/spantaleev)) for polishing it up, the playbook can now install and configure the [sliding-sync proxy](https://github.com/matrix-org/sliding-sync)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:969
+msgid "The upcoming Element X clients ([Element X iOS](https://github.com/vector-im/element-x-ios) and [Element X Android](https://github.com/vector-im/element-x-android)) require the `sliding-sync` proxy to do their job. **These clients are still in beta** (especially Element X Android, which requires manual compilation to get it working with a non-`matrix.org` homeseserver). Playbook users can now easily give these clients a try and help test them thanks to us having `sliding-sync` support."
+msgstr ""
+
+#: ../../../CHANGELOG.md:971
+msgid "To get started, see our [Setting up the Sliding Sync proxy](docs/configuring-playbook-sliding-sync-proxy.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:974
+msgid "2023-03-02"
+msgstr ""
+
+#: ../../../CHANGELOG.md:976
+msgid "The matrix-etherpad role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:978
+msgid "**TLDR**: the `matrix-etherpad` role is now included from [another repository](https://github.com/mother-of-all-self-hosting/ansible-role-etherpad). Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:980
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Etherpad or not."
+msgstr ""
+
+#: ../../../CHANGELOG.md:982
+msgid "If you're making use of Etherpad via this playbook, you will need to update variable references in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:984
+msgid "Rename `matrix_etherpad_public_endpoint` to `etherpad_path_prefix`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:986
+msgid "Replace `matrix_etherpad_mode: dimension` with:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:987
+msgid "for `matrix-nginx-proxy` users:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:988
+msgid "`etherpad_nginx_proxy_dimension_integration_enabled: true`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:989
+msgid "`etherpad_hostname: \"{{ matrix_server_fqn_dimension }}\"`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:990
+msgid "for Traefik users:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:991
+msgid "define your own `etherpad_hostname` and `etherpad_path_prefix` as you see fit"
+msgstr ""
+
+#: ../../../CHANGELOG.md:993
+msgid "Rename all other variables:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:994
+msgid "`matrix_etherpad_docker_image_` -> `matrix_etherpad_container_image_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:995
+msgid "`matrix_etherpad_` -> `etherpad_`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:997
+msgid "Along with this relocation, the new role also:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:999
+msgid "supports [self-building](docs/self-building.md), so it should work on `arm32` and `arm64` architectures"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1000
+msgid "has native Traefik reverse-proxy support (Etherpad requests no longer go through `matrix-nginx-proxy` when using Traefik)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1003
+msgid "2023-02-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1005
+msgid "Traefik is the default reverse-proxy now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1007
+msgid "**TLDR**: new installations will now default to Traefik as their reverse-proxy. Existing users need to explicitly choose their reverse-proxy type. [Switching to Traefik](#how-do-i-switch-my-existing-setup-to-traefik) is strongly encouraged. `matrix-nginx-proxy` may break over time and will ultimately be removed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1009
+msgid "As mentioned 2 weeks ago in [(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support](#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support), the playbook is moving to Traefik as its default SSL-terminating reverse-proxy."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1011
+msgid "Until now, we've been doing the migration gradually and keeping full backward compatibility. New installations were defaulting to `matrix-nginx-proxy` (just like before), while existing installations were allowed to remain on `matrix-nginx-proxy` as well. This makes things very difficult for us, because we need to maintain and think about lots of different setups:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1013
+msgid "Traefik managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1014
+msgid "Traefik managed by the user in another way"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1015
+msgid "another reverse-proxy on the same host (`127.0.0.1` port exposure)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1016
+msgid "another reverse-proxy on another host (`0.0.0.0` port exposure)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1017
+msgid "`matrix-nginx-proxy` - an `nginx` container managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1018
+msgid "`nginx` webserver operated by the user, running without a container on the same server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1020
+msgid "Each change we do and each new feature that comes in needs to support all these different ways of reverse-proxying. Because `matrix-nginx-proxy` was the default and pretty much everyone was (and still is) using it, means that new PRs also come with `matrix-nginx-proxy` as their main focus and Traefik as an afterthought, which means we need to spend hours fixing up Traefik support."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1022
+msgid "We can't spend all this time maintaining so many different configurations anymore. Traefik support has been an option for 2 weeks and lots of people have already migrated their server and have tested things out. Traefik is what we use and preferentially test for."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1024
+msgid "It's time for the **next step in our migration process** to Traefik and elimination of `matrix-nginx-proxy`:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1026
+msgid "Traefik is now the default reverse-proxy for new installations"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1027
+msgid "All existing users need to explicitly choose their reverse-proxy type by defining the `matrix_playbook_reverse_proxy_type` variable in their `vars.yml` configuration file. We strongly encourage existing users to [switch the Traefik](#how-to-switch-an-existing-setup-to-traefik), as the nginx setup is bound to become more and more broken over time until it's ultimately removed"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1029
+msgid "How do I switch my existing setup to Traefik?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1031
+msgid "**For users who are on `matrix-nginx-proxy`** (the default reverse-proxy provided by the playbook), switching to Traefik can happen with a simple configuration change. Follow this section from 2 weeks ago: [How do I explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-traefik-right-now)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1033
+msgid "If you experience trouble:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1035
+msgid "Follow [How do I remain on matrix-nginx-proxy?](#how-do-i-remain-on-matrix-nginx-proxy) to bring your server back online using the old reverse-proxy"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1036
+msgid "Ask for help in our [support channels](README.md#support)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1037
+msgid "Try switching to Traefik again later"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1039
+msgid "**For users with a more special reverse-proxying setup** (another nginx server, Apache, Caddy, etc.), the migration may not be so smooth. Follow the [Using your own webserver](docs/configuring-playbook-own-webserver.md) guide. Ideally, your custom reverse-proxy will be configured in such a way that it **fronts the Traefik reverse-proxy** provided by the playbook. Other means of reverse-proxying are more fragile and may be deprecated in the future."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1041
+msgid "I already use my own Traefik server. How do I plug that in?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1043
+msgid "See the [Traefik managed by the playbook](docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) section."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1045
+msgid "Why is matrix-nginx-proxy used even after switching to Traefik?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1047
+msgid "This playbook manages many different services. All these services were initially integrated with `matrix-nginx-proxy`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1049
+msgid "While we migrate all these components to have native Traefik support, some still go through nginx internally (Traefik -> local `matrix-nginx-proxy` -> component). As time goes on, internal reliance on `matrix-nginx-proxy` will gradually decrease until it's completely removed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1051
+msgid "How do I remain on matrix-nginx-proxy?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1053
+msgid "Most new work and testing targets Traefik, so remaining on nginx is **not** \"the good old stable\" option, but rather the \"still available, but largely untested and likely to be broken very soon\" option."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1055
+msgid "To proceed regardless of this warning, add `matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1057
+msgid "At some point in the **near** future (days, or even weeks at most), we hope to completely get rid of `matrix-nginx-proxy` (or break it enough to make it unusable), so you **will soon be forced to migrate** anyway. Plan your migration accordingly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1059
+msgid "How do I keep using my own other reverse-proxy?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1061
+msgid "We recommend that you follow the guide for [Fronting the integrated reverse-proxy webserver with another reverse-proxy](docs/configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1064
+msgid "2023-02-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1066
+msgid "rageshake support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1068
+msgid "Thanks to [Benjamin Kampmann](https://github.com/gnunicorn), the playbook can now install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1070
+msgid "Additional details are available in [Setting up rageshake](docs/configuring-playbook-rageshake.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1073
+msgid "2023-02-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1075
+msgid "Synapse templates customization support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1077
+msgid "The playbook can now help you customize Synapse's templates."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1079
+msgid "Additional details are available in the [Customizing templates](docs/configuring-playbook-synapse.md#customizing-templates) section of our Synapse documentation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1081
+msgid "The matrix-redis role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1083
+msgid "**TLDR**: the `matrix-redis` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1085
+msgid "The `matrix-redis` role (which configures [Redis](https://redis.io/)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-redis). This makes it possible to easily use it in other Ansible playbooks."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1087
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Ntfy or not. If you're making use of Ntfy via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_redis_` -> `redis_`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1089
+msgid "The matrix-ntfy role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1091
+msgid "**TLDR**: the `matrix-ntfy` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1093
+msgid "The `matrix-ntfy` role (which configures [Ntfy](https://ntfy.sh/)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy). This makes it possible to easily use it in other Ansible playbooks."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1095
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Ntfy or not. If you're making use of Ntfy via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_ntfy_` -> `ntfy_`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1098
+msgid "2023-02-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1100
+msgid "The matrix-grafana role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1102
+msgid "**TLDR**: the `matrix-grafana` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1104
+msgid "The `matrix-grafana` role (which configures [Grafana](docs/configuring-playbook-prometheus-grafana.md)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-grafana). This makes it possible to easily use it in other Ansible playbooks."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1106
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Grafana or not. If you're making use of Grafana via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_grafana_` -> `grafana_`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1109
+msgid "2023-02-13"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1111
+msgid "The matrix-backup-borg role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1113
+msgid "**TLDR**: the `matrix-backup-borg` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1115
+msgid "Thanks to [moan0s](https://github.com/moan0s), the `matrix-backup-borg` role (which configures [BorgBackup](docs/configuring-playbook-backup-borg.md)) has been extracted from the playbook and now lives in its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg). This makes it possible to easily use it in other Ansible playbooks and will become part of [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) soon."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1117
+msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're enabling Borg's backup functionality or not. If you're making use of BorgBackup via this playbook, you will need to update variable references in your `vars.yml` file (`matrix_backup_borg_` -> `backup_borg_`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1120
+msgid "2023-02-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1122
+msgid "(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1124
+msgid "**TLDR**:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1126
+msgid "there's a new `matrix_playbook_reverse_proxy_type` variable (see [roles/custom/matrix-base/defaults/main.yml](roles/custom/matrix-base/defaults/main.yml)), which lets you tell the playbook what reverse-proxy setup you'd like to have. This makes it easier for people who want to do reverse-proxying in other ways."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1127
+msgid "the default reverse-proxy (`matrix_playbook_reverse_proxy_type`) is still `playbook-managed-nginx` (via `matrix-nginx-proxy`), for now. **Existing `matrix-nginx-proxy` users should not observe any changes** and can stay on this for now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1128
+msgid "**Users who use their [own other webserver](docs/configuring-playbook-own-webserver.md) (e.g. Apache, etc.) need to change** `matrix_playbook_reverse_proxy_type` to something like `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1129
+msgid "we now have **optional [Traefik](https://traefik.io/) support**, so you could easily host Matrix and other Traefik-native services in containers on the same server. Traefik support is still experimental (albeit, good enough) and will improve over time. It does work, but certain esoteric features may not be there yet."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1130
+msgid "**Traefik will become the default reverse-proxy in the near future**. `matrix-nginx-proxy` will either remain as an option, or be completely removed to simplify the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1132
+msgid "Motivation for redoing our reverse-proxy setup"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1134
+msgid "The playbook has supported various reverse-proxy setups for a long time. We have various configuration variables (`matrix_nginx_proxy_enabled`, various `_host_bind_port` variables, etc.) which allow the playbook to adapt to these different setups. The whole situation was messy though - hard to figure out and with lots of variables to toggle to make things work as you'd expect - huge **operational complexity**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1136
+msgid "We love containers, proven by the fact that **everything** that this playbook manages runs in a container. Yet, we weren't allowing people to easily host other web-exposed containers alongside Matrix services on the same server. We were using `matrix-nginx-proxy` (our integrated [nginx](https://nginx.org/) server), which was handling web-exposure and SSL termination for our own services, but we **weren't helping you with all your other containers**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1138
+msgid "People who were **using `matrix-nginx-proxy`** were on the happy path on which everything worked well by default (Matrix-wise), **but** could not easily run other web-exposed services on their Matrix server because `matrix-nginx-proxy` was occupying ports `80` and `443`. Other services which wanted to get web exposure either had to be plugged into `matrix-nginx-proxy` (somewhat difficult) or people had to forgo using `matrix-nginx-proxy` in favor of something else."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1140
+msgid "Of those that decided to forgo `matrix-nginx-proxy`, many were **using nginx** on the same server without a container. This was likely some ancient nginx version, depending on your choice of distro. The Matrix playbook was trying to be helpful and even with `matrix_nginx_proxy_enabled: false` was still generating nginx configuration in `/matrix/nginx-proxy/conf.d`. Those configuration files were adapted for inclusion into an nginx server running locally. Disabling the `matrix-nginx-proxy` role like this, yet still having it produce files is a bit disgusting, but it's what we've had since the early beginnings of this playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1142
+msgid "Others still, wanted to run Matrix locally (no SSL certificates), regardless of which web server technology this relied on, and then **reverse-proxy from another machine on the network** which was doing SSL termination. These people were:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1144
+msgid "*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined with exposing services manually (setting `_bind_port` variables)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1145
+msgid "*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in `http`-only mode (no SSL certificate retrieval)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1147
+msgid "Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1149
+msgid "When using `matrix-nginx-proxy` as is, we still had another problem - one of **internal playbook complexity**. Too many services need to be web-exposed (port 80/443, SSL certificates). Because of this, they all had to integrate with the `matrix-nginx-proxy` role. Tens of different roles explicitly integrating with `matrix-nginx-proxy` is not what we call clean. The `matrix-nginx-proxy` role contains variables for many of these roles (yikes). Other roles were more decoupled from it and were injecting configuration into `matrix-nginx-proxy` at runtime - see all the `inject_into_nginx_proxy.yml` task files in this playbook (more decoupled, but still.. yikes)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1151
+msgid "The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1153
+msgid "[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy) for hosting the [Vaultwarden](https://github.com/dani-garcia/vaultwarden) server - an alternative implementation of the [Bitwarden](https://bitwarden.com/) password manager"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1154
+msgid "[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) - for hosting the [Gitea](https://gitea.io/) git source code hosting service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1155
+msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy) - for hosting the [Nextcloud](https://nextcloud.com/) groupware platform"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1157
+msgid "We'd love for users to be able to **seamlessly use all these playbooks (and others, even) against a single server**. We don't want `matrix-nginx-proxy` to have a monopoly on port `80`/`443` and make it hard for other services to join in on the party. Such a thing forces people into running multiple servers (one for each service), which does provide nice security benefits, but is costly and ineffiecient. We'd like to make self-hosting these services cheap and easy."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1159
+msgid "These other playbooks have been using [Traefik](https://traefik.io/) as their default reverse-proxy for a long time. They can all coexist nicely together (as an example, see the [Interoperability](https://github.com/spantaleev/nextcloud-docker-ansible-deploy/blob/master/docs/configuring-playbook-interoperability.md) documentation for the [Nextcloud playbook](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)). Now that this playbook is gaining Traefik support, it will be able to interoperate with them. If you're going this way, make sure to have the Matrix playbook install Traefik and have the others use `*_reverse_proxy_type: other-traefik-container`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1161
+msgid "Finally, at [etke.cc - a managed Matrix server hosting service](https://etke.cc) (built on top of this playbook, and coincidentally [turning 2 years old today](https://etke.cc/news/upsyw4ykbtgmwhz8k7ukldx0zbbfq-fh0iqi3llixi0/) 🎉), we're allowing people to host some additional services besides Matrix components. Exposing these services to the web requires ugly hacks and configuration files being dropped into `/matrix/nginx-proxy/conf.d`. We believe that everything should run in independent containers and be exposed to the web via a Traefik server, without a huge Ansible role like `matrix-nginx-proxy` that everything else needs to integrate with."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1163
+msgid "How do these changes fix all these problems?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1165
+msgid "The new `matrix_playbook_reverse_proxy_type` lets you easily specify your preferred reverse-proxy type, including `other-on-same-host`, `other-on-another-host` and `none`, so people who'd like to reverse-proxy with their own web server have more options now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1167
+msgid "Using Traefik greatly simplifies things, so going forward we'll have a simpler and easier to maintain playbook, which is also interoperable with other services."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1169
+msgid "Traefik is a web server, which has been specifically **designed for reverse-proxying to services running in containers**. It's ideal for usage in an Ansible playbook which runs everything in containers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1171
+msgid "**Traefik obtains SSL certificates automatically**, so there's no need for plugging additional tools like [Certbot](https://certbot.eff.org/) into your web server (like we were doing in the `matrix-nginx-proxy` role). No more certificate renewal timers, web server reloading timers, etc. It's just simpler."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1173
+msgid "Traefik is a **modern web server**. [HTTP/3](https://doc.traefik.io/traefik/routing/entrypoints/#http3) is supported already (experimentally) and will move to stable soon, in the upcoming Traefik v3 release."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1175
+msgid "Traefik does not lock important functionality we'd like to use into [plus packages like nginx does](https://www.nginx.com/products/nginx/), leading us to resolve to configuration workarounds. The default Traefik package is good enough as it is."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1177
+msgid "Where we're at right now?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1179
+msgid "`matrix_playbook_reverse_proxy_type` still defaults to a value of `playbook-managed-nginx`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1181
+msgid "Unless we have some regression, **existing `matrix-nginx-proxy` users should be able to update their Matrix server and not observe any changes**. Their setup should still remain on nginx and everything should still work as expected."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1183
+msgid "**Users using [their own webservers](docs/configuring-playbook-own-webserver.md) will need to change `matrix_playbook_reverse_proxy_type`** to something like `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`. Previously, they could toggle `matrix_nginx_proxy_enabled` to `false`, and that made the playbook automatically expose services locally. Currently, we only do this if you change the reverse-proxy type to `other-on-same-host`, `other-on-another-host` or `other-nginx-non-container`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1185
+msgid "How do I explicitly switch to Traefik right now?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1187
+msgid "**Users who wish to migrate to Traefik** today, can do so by **adding** this to their configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1195
+msgid "You may still need to keep certain old `matrix_nginx_proxy_*` variables (like `matrix_nginx_proxy_base_domain_serving_enabled`), even when using Traefik. For now, we recommend keeping all `matrix_nginx_proxy_*` variables just in case. In the future, reliance on `matrix-nginx-proxy` will be removed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1197
+msgid "Switching to Traefik will obtain new SSL certificates from Let's Encrypt (stored in `/matrix/traefik/ssl/acme.json`). **The switch is reversible**. You can always go back to `playbook-managed-nginx` if Traefik is causing you trouble."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1199
+msgid "**Note**: toggling `matrix_playbook_reverse_proxy_type` between Traefik and nginx will uninstall the Traefik role and all of its data (under `/matrix/traefik`), so you may run into a Let's Encrypt rate limit if you do it often."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1201
+msgid "Treafik directly reverse-proxies to **some** services right now, but for most other services it goes through `matrix-nginx-proxy` (e.g. Traefik -> `matrix-nginx-proxy` -> [Ntfy](docs/configuring-playbook-ntfy.md)). So, even if you opt into Traefik, you'll still see `matrix-nginx-proxy` being installed in local-only mode. This will improve with time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1203
+msgid "Some services (like [Coturn](docs/configuring-playbook-turn.md) and [Postmoogle](docs/configuring-playbook-bridge-postmoogle.md)) cannot be reverse-proxied to directly from Traefik, so they require direct access to SSL certificate files extracted out of Traefik. The playbook does this automatically thanks to a new [com.devture.ansible.role.traefik_certs_dumper](https://github.com/devture/com.devture.ansible.role.traefik_certs_dumper) role utilizing the [traefik-certs-dumper](https://github.com/ldez/traefik-certs-dumper) tool."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1205
+msgid "Our Traefik setup mostly works, but certain esoteric features may not work. If you have a default setup, we expect you to have a good experience."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1207
+msgid "Where we're going in the near future?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1209
+msgid "The `matrix-nginx-proxy` role is quite messy. It manages both nginx and Certbot and its certificate renewal scripts and timers. It generates configuration even when the role is disabled (weird). Although it doesn't directly reach into variables from other roles, it has explicit awareness of various other services that it reverse-proxies to (`roles/custom/matrix-nginx-proxy/templates/nginx/conf.d/matrix-ntfy.conf.j2`, etc.). We'd like to clean this up. The only way is probably to just get rid of the whole thing at some point."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1211
+msgid "For now, `matrix-nginx-proxy` will stay around."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1213
+msgid "As mentioned above, Traefik still reverse-proxies to some (most) services by going through a local-only `matrix-nginx-proxy` server. This has allowed us to add Traefik support to the playbook early on (without having to rework all services), but is not the final goal. We'll **work on making each service support Traefik natively**, so that traffic will not need to go through `matrix-nginx-proxy` anymore. In the end, choosing Traefik should only give you a pure Traefik installation with no `matrix-nginx-proxy` in sight."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1215
+msgid "As Traefik support becomes complete and proves to be stable for a while, especially as a playbook default, we will **most likely remove `matrix-nginx-proxy` completely**. It will likely be some months before this happens though. Keeping support for both Traefik and nginx in the playbook will be a burden, especially with most of us running Traefik in the future. The Traefik role should do everything nginx does in a better and cleaner way. Users who use their own `nginx` server on the Matrix server will be inconvenienced, as nothing will generate ready-to-include nginx configuration for them. Still, we hope it won't be too hard to migrate their setup to another way of doing things, like:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1217
+msgid "not using nginx anymore. A common reason for using nginx until now was that you were running other containers and you need your own nginx to reverse-proxy to all of them. Just switch them to Traefik as well."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1218
+msgid "running Traefik in local-only mode (`traefik_config_entrypoint_web_secure_enabled: false`) and using some nginx configuration which reverse-proxies to Traefik (we should introduce examples for this in `examples/nginx`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1220
+msgid "How do I help?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1222
+msgid "You can help by:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1224
+msgid "**explicitly switching your server to Traefik** right now (see example configuration in [How do I explicitly switch to Traefik right now?](#how-do-i-explicitly-switch-to-traefik-right-now) above), testing, reporting troubles"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1226
+msgid "**adding native Traefik support to a role** (requires adding Traefik labels, etc.) - for inspiration, see these roles ([prometheus_node_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter), [prometheus_postgres_exporter](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter)) and how they're hooked into the playbook via [group_vars/matrix_servers](group_vars/matrix_servers)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1228
+msgid "**adding reverse-proxying examples for nginx users** in `examples/nginx`. People who insist on using their own `nginx` server on the same Matrix host, can run Traefik in local-only mode (`traefik_config_entrypoint_web_secure_enabled: false`) and reverse-proxy to the Traefik server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1231
+msgid "2023-02-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1233
+msgid "Matrix Authentication Support for Jitsi"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1235
+msgid "Thanks to [Jakob S.](https://github.com/jakicoll) ([zakk gGmbH](https://github.com/zakk-it)), Jitsi can now use Matrix for authentication (via [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1237
+msgid "Additional details are available in the [Authenticate using Matrix OpenID (Auth-Type 'matrix')](docs/configuring-playbook-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1239
+msgid "Draupnir moderation tool (bot) support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1241
+msgid "Thanks to [FSG-Cat](https://github.com/FSG-Cat), the playbook can now install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (bot). Draupnir is a fork of [Mjolnir](docs/configuring-playbook-bot-mjolnir.md) (which the playbook has supported for a long time) maintained by Mjolnir's former lead developer."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1243
+msgid "Additional details are available in [Setting up Draupnir](docs/configuring-playbook-bot-draupnir.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1246
+msgid "2023-02-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1248
+msgid "The matrix-prometheus-postgres-exporter role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1250
+msgid "**TLDR**: the `matrix-prometheus-postgres-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1252
+msgid "The `matrix-prometheus-postgres-exporter` role (which configures [Prometheus Postgres Exporter](https://github.com/prometheus-community/postgres_exporter)) has been extracted from the playbook and now lives in its own repository at https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-postgres-exporter"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1254
+msgid "It's still part of the playbook, but is now installed via `ansible-galaxy` (by running `just roles` / `make roles`). Some variables have been renamed (`matrix_prometheus_postgres_exporter_` -> `prometheus_postgres_exporter_`, etc.). The playbook will report all variables that you need to rename to get upgraded. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1256
+msgid "The `matrix-prometheus-services-proxy-connect` role has bee adjusted to help integrate the new `prometheus_postgres_exporter` role with our own services (`matrix-nginx-proxy`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1258
+#: ../../../CHANGELOG.md:1300
+msgid "Other roles which aren't strictly related to Matrix are likely to follow this fate of moving to their own repositories. Extracting them out allows other Ansible playbooks to make use of these roles easily."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1261
+msgid "2023-01-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1263
+msgid "Coturn can now use host-networking"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1265
+msgid "Large Coturn deployments (with a huge range of ports specified via `matrix_coturn_turn_udp_min_port` and `matrix_coturn_turn_udp_max_port`) experience a huge slowdown with how Docker publishes all these ports (setting up firewall forwarding rules), which leads to a very slow Coturn service startup and shutdown."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1267
+msgid "Such deployments don't need to run Coturn within a private container network anymore. Coturn can now run with host-networking by using configuration like this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1273
+msgid "With such a configuration, **Docker no longer needs to configure thousands of firewall forwarding rules** each time Coturn starts and stops. This, however, means that **you will need to ensure these ports are open** in your firewall yourself."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1275
+msgid "Thanks to us [tightening Coturn security](#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues), running Coturn with host-networking should be safe and not expose neither other services running on the host, nor other services running on the local network."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1277
+msgid "(Backward Compatibility) Tightening Coturn security can lead to connectivity issues"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1279
+msgid "**TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default Coturn blocklists. They may need to override `matrix_coturn_denied_peer_ips` and remove some IP ranges from it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1281
+msgid "Inspired by [this security article](https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-access-control-protection/), we've decided to make use of Coturn's `denied-peer-ip` functionality to prevent relaying network traffic to certain private IP subnets. This ensures that your Coturn server won't accidentally try to forward traffic to certain services running on your local networks. We run Coturn in a container and in a private container network by default, which should prevent such access anyway, but having additional block layers in place is better."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1283
+msgid "If you access your Matrix server from a local network and need Coturn to relay to private IP addresses, you may observe that relaying is now blocked due to our new default `denied-peer-ip` lists (specified in `matrix_coturn_denied_peer_ips`). If you experience such connectivity problems, consider overriding this setting in your `vars.yml` file and removing certain networks from it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1285
+msgid "We've also added `no-multicast-peers` to the default Coturn configuration, but we don't expect this to cause trouble for most people."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1288
+msgid "2023-01-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1290
+msgid "The matrix-prometheus-node-exporter role lives independently now"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1292
+msgid "**TLDR**: the `matrix-prometheus-node-exporter` role is now included from another repository. Some variables have been renamed. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1294
+msgid "The `matrix-prometheus-node-exporter` role (which configures [Prometheus node exporter](https://github.com/prometheus/node_exporter)) has been extracted from the playbook and now lives in its own repository at https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1296
+msgid "It's still part of the playbook, but is now installed via `ansible-galaxy` (by running `just roles` / `make roles`). Some variables have been renamed (`matrix_prometheus_node_exporter_` -> `prometheus_node_exporter_`, etc.). The playbook will report all variables that you need to rename to get upgraded. All functionality remains intact."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1298
+msgid "A new `matrix-prometheus-services-proxy-connect` role was added to the playbook to help integrate the new `prometheus_node_exporter` role with our own services (`matrix-nginx-proxy`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1303
+msgid "2023-01-13"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1305
+msgid "Support for running commands via just"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1307
+msgid "We've previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers `ansible-galaxy`, see [Makefile](Makefile)). Our `Makefile` is still around and you can still run these commands."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1309
+msgid "In addition, we've added support for running commands via [just](https://github.com/casey/just) - a more modern command-runner alternative to `make`. Instead of `make roles`, you can now run `just roles` to accomplish the same."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1311
+msgid "Our [justfile](justfile) already defines some additional helpful **shortcut** commands that weren't part of our `Makefile`. Here are some examples:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1313
+msgid "`just install-all` to trigger the much longer `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start` command"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1314
+msgid "`just install-all --ask-vault-pass` - commands also support additional arguments (`--ask-vault-pass` will be appended to the above installation command)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1315
+msgid "`just run-tags install-mautrix-slack,start` - to run specific playbook tags"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1316
+msgid "`just start-all` - (re-)starts all services"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1317
+msgid "`just stop-group postgres` - to stop only the Postgres service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1318
+msgid "`just register-user alice secret-password yes` - registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1320
+msgid "Additional helpful commands and shortcuts may be defined in the future."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1322
+msgid "This is all completely optional. If you find it difficult to [install `just`](https://github.com/casey/just#installation) or don't find any of this convenient, feel free to run all commands manually."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1325
+msgid "2023-01-11"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1327
+msgid "mautrix-slack support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1329
+msgid "Thanks to [Cody Neiman](https://github.com/xangelix)'s efforts, the playbook now supports bridging to [Slack](https://slack.com/) via the [mautrix-slack](https://mau.dev/mautrix/slack) bridge. See our [Setting up Mautrix Slack bridging](docs/configuring-playbook-bridge-mautrix-slack.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1331
+msgid "**Note**: this is a new Slack bridge. The playbook still retains Slack bridging via [matrix-appservice-slack](docs/configuring-playbook-bridge-appservice-slack.md) and [mx-puppet-slack](docs/configuring-playbook-bridge-mx-puppet-slack.md). You're free to use the bridge that serves you better, or even all three of them (for different users and use-cases)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1334
+msgid "2023-01-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1336
+msgid "ChatGPT support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1338
+msgid "Thanks to [@bertybuttface](https://github.com/bertybuttface), the playbook can now help you set up [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) - a bot through which you can talk to the [ChatGPT](https://openai.com/blog/chatgpt/) model."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1340
+msgid "See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-chatgpt.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1343
+msgid "2022-11-30"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1345
+msgid "matrix-postgres-backup has been replaced by the ansible-role-postgres-backup external role"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1347
+msgid "Just like we've [replaced Postgres with an external role](#matrix-postgres-has-been-replaced-by-the-comdevtureansiblerolepostgres-external-role) on 2022-11-28, we're now replacing `matrix-postgres-backup` with an external role - [com.devture.ansible.role.postgres_backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres_backup)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1349
+msgid "You'll need to rename your `matrix_postgres_backup`-prefixed variables such that they use a `postgres_backup` prefix."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1352
+msgid "2022-11-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1354
+msgid "matrix-postgres has been replaced by the ansible-role-postgres external role"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1356
+msgid "**TLDR**: the tasks that install the integrated Postgres server now live in an external role - [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres). You'll need to run `make roles` to install it, and to also rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix (e.g. `matrix_postgres_connection_password` -> `postgres_connection_password`). All your data will still be there! Some scripts have moved (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1358
+msgid "The `matrix-postgres` role that has been part of the playbook for a long time has been replaced with the [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) role. This was done as part of our work to [use external roles for some things](#the-playbook-now-uses-external-roles-for-some-things) for better code re-use and maintainability."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1360
+msgid "The new role is an upgraded version of the old `matrix-postgres` role with these notable differences:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1362
+msgid "it uses different names for its variables (`matrix_postgres` -> `devture_postgres`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1363
+msgid "when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-postgresql), it will vacuum all your databases, not just the Synapse one"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1365
+msgid "You'll need to run `make roles` to install the new role. You would also need to rename your `matrix_postgres`-prefixed variables to use a `devture_postgres` prefix."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1367
+msgid "Note: the systemd service still remains the same - `matrix-postgres.service`. Your data will still be in `/matrix/postgres`, etc. Postgres-related scripts will be moved to `/matrix/postgres/bin` (`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`, etc). Also see [The playbook no longer installs scripts in /usr/local/bin](#the-playbook-no-longer-installs-scripts-in-usrlocalbin)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1369
+msgid "The playbook no longer installs scripts to /usr/local/bin"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1371
+msgid "The locations of various scripts installed by the playbook have changed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1373
+msgid "The playbook no longer contaminates your `/usr/local/bin` directory. All scripts installed by the playbook now live in `bin/` directories under `/matrix`. Some examples are below:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1375
+msgid "`/usr/local/bin/matrix-remove-all` -> `/matrix/bin/remove-all`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1376
+msgid "`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1377
+msgid "`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> `/matrix/ssl/bin/lets-encrypt-certificates-renew`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1378
+msgid "`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin/register-user`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1381
+msgid "2022-11-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1383
+msgid "2x-5x performance improvements in playbook runtime"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1385
+msgid "**TLDR**: the playbook is 2x faster for running `--tags=setup-all` (and various other tags). It also has new `--tags=install-*` tags (like `--tags=install-all`), which skip uninstallation tasks and bring an additional 2.5x speedup. In total, the playbook can maintain your server 5 times faster."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1387
+msgid "Our [etke.cc managed Matrix hosting service](https://etke.cc) runs maintenance against hundreds of servers, so the playbook being fast means a lot. The [etke.cc Ansible playbook](https://github.com/etkecc/ansible) (which is an extension of this one) is growing to support more and more services (besides just Matrix), so the Matrix playbook being leaner prevents runtimes from becoming too slow and improves the customer experience."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1389
+msgid "Even when running `ansible-playbook` manually (as most of us here do), it's beneficial not to waste time and CPU resources."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1391
+msgid "Recently, a few large optimizations have been done to this playbook and its external roles (see [The playbook now uses external roles for some things](#the-playbook-now-uses-external-roles-for-some-things) and don't forget to run `make roles`):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1393
+msgid "Replacing Ansible `import_tasks` calls with `include_tasks`, which decreased runtime in half. Using `import_tasks` is slower and causes Ansible to go through and skip way too many tasks (tasks which could have been skipped altogether by not having Ansible include them in the first place). On an experimental VM, **deployment time was decreased from ~530 seconds to ~250 seconds**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1395
+msgid "Introducing new `install-*` tags (`install-all` and `install-COMPONENT`, e.g. `install-synapse`, `install-bot-mjolnir`), which only run Ansible tasks pertaining to installation, while skipping uninstallation tasks. In most cases, people are maintaining the same setup or they're *adding* new components. Removing components is rare. Running thousands of uninstallation tasks each time is wasteful. On an experimental VM, **deployment time was decreased from ~250 seconds (`--tags=setup-all`) to ~100 seconds (`--tags=install-all`)**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1397
+msgid "You can still use `--tags=setup-all`. In fact, that's the best way to ensure your server is reconciled with the `vars.yml` configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1399
+msgid "If you know you haven't uninstalled any services since the last time you ran the playbook, you could run `--tags=install-all` instead and benefit from quicker runtimes. It should be noted that a service may become \"eligible for uninstallation\" even if your `vars.yml` file remains the same. In rare cases, we toggle services from being auto-installed to being optional, like we did on the 17th of March 2022 when we made [ma1sd not get installed by default](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/CHANGELOG.md#compatibility-break-ma1sd-identity-server-no-longer-installed-by-default). In such rare cases, you'd also need to run `--tags=setup-all`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1402
+msgid "2022-11-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1404
+msgid "Automatic `matrix_architecture` determination"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1406
+msgid "From now on, the playbook automatically determines your server's architecture and sets the `matrix_architecture` variable accordingly. You no longer need to set this variable manually in your `vars.yml` file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1408
+msgid "Docker and the Docker SDK for Python are now installed via external roles"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1412
+msgid "Docker will now be installed on the server via the [geerlingguy.docker](https://github.com/geerlingguy/ansible-role-docker) Ansible role. If you'd like to manage the Docker installation yourself, you can disable the playbook's installation of Docker by setting `matrix_playbook_docker_installation_enabled: false`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1414
+msgid "The Docker SDK for Python (named `docker-python`, `python-docker`, etc. on the different platforms) is now also installed by another role ([com.devture.ansible.role.docker_sdk_for_python](https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python)). To disable this role and install the necessary tools yourself, use `devture_docker_sdk_for_python_installation_enabled: false`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1416
+msgid "If you're hitting issues with Docker installation or Docker SDK for Python installation, consider reporting bugs or contributing to these other projects."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1418
+msgid "These additional roles are downloaded into the playbook directory (to `roles/galaxy`) via an `ansible-galaxy ..` command. `make roles` is an easy shortcut for invoking the `ansible-galaxy` command to download these roles."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1421
+msgid "2022-11-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1423
+msgid "(Backward Compatibility Break) Changing how reverse-proxying to Synapse works - now via a `matrix-synapse-reverse-proxy-companion` service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1425
+msgid "**TLDR**: There's now a `matrix-synapse-reverse-proxy-companion` nginx service, which helps with reverse-proxying to Synapse and its various worker processes (if workers are enabled), so that `matrix-nginx-proxy` can be relieved of this role. `matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. `matrix-synapse-reverse-proxy-companion` is just one more reverse-proxy thrown into the mix for convenience. People with a more custom reverse-proxying configuration may be affected - see [Webserver configuration](#webserver-configuration) below."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1427
+msgid "Background"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1429
+msgid "Previously, `matrix-nginx-proxy` forwarded requests to Synapse directly. When Synapse is running in worker mode, the reverse-proxying configuration is more complicated (different requests need to go to different Synapse worker processes). `matrix-nginx-proxy` had configuration for sending each URL endpoint to the correct Synapse worker responsible for handling it. However, sometimes people like to disable `matrix-nginx-proxy` (for whatever reason) as detailed in [Using your own webserver, instead of this playbook's nginx proxy](docs/configuring-playbook-own-webserver.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1431
+msgid "Because `matrix-nginx-proxy` was so central to request forwarding, when it was disabled and Synapse was running with workers enabled, there was nothing which could forward requests to the correct place anymore.. which caused [problems such as this one affecting Dimension](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2090)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1433
+msgid "Solution"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1435
+msgid "From now on, `matrix-nginx-proxy` is relieved of its function of reverse-proxying to Synapse and its various worker processes. This role is now handled by the new `matrix-synapse-reverse-proxy-companion` nginx service and works even if `matrix-nginx-proxy` is disabled. The purpose of the new `matrix-synapse-reverse-proxy-companion` service is to:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1437
+msgid "serve as a companion to Synapse and know how to reverse-proxy to Synapse correctly (no matter if workers are enabled or not)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1439
+msgid "provide a unified container address for reaching Synapse (no matter if workers are enabled or not)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1440
+msgid "`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server API traffic"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1441
+msgid "`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server (Federation) API traffic"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1443
+msgid "simplify `matrix-nginx-proxy` configuration - it now only needs to send requests to `matrix-synapse-reverse-proxy-companion` or `matrix-dendrite`, etc., without having to worry about workers"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1445
+msgid "allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is disabled"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1447
+msgid "`matrix-nginx-proxy` still remains as the public SSL-terminating reverse-proxy in the playbook. All traffic goes through it before reaching any of the services. It's just that now the Synapse traffic is routed through `matrix-synapse-reverse-proxy-companion` like this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1449
+msgid "(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> (`matrix-synapse` or some Synapse worker))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1451
+msgid "Various services (like Dimension, etc.) still talk to Synapse via `matrix-nginx-proxy` (e.g. `http://matrix-nginx-proxy:12080`) preferentially. They only talk to Synapse via the reverse-proxy companion (e.g. `http://matrix-synapse-reverse-proxy-companion:8008`) if `matrix-nginx-proxy` is disabled. Services should not be talking to Synapse (e.g. `https://matrix-synapse:8008` directly anymore), because when workers are enabled, that's the Synapse `master` process and may not be serving all URL endpoints needed by the service."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1453
+msgid "Webserver configuration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1455
+msgid "if you're using `matrix-nginx-proxy` (`matrix_nginx_proxy_enabled: true`, which is the default for the playbook), you don't need to do anything"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1457
+msgid "if you're using your own `nginx` webserver running on the server, you shouldn't be affected. The `/matrix/nginx/conf.d` configuration and exposed ports that you're relying on will automatically be updated in a way that should work"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1459
+msgid "if you're using another local webserver (e.g. Apache, etc.) and haven't changed any ports (`matrix_*_host_bind_port` definitions), you shouldn't be affected. You're likely sending Matrix traffic to `127.0.0.1:8008` and `127.0.0.1:8048`. These ports (`8008` and `8048`) will still be exposed on `127.0.0.1` by default - just not by the `matrix-synapse` container from now on, but by the `matrix-synapse-reverse-proxy-companion` container instead"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1461
+msgid "if you've been exposing `matrix-synapse` ports (`matrix_synapse_container_client_api_host_bind_port`, etc.) manually, you should consider exposing `matrix-synapse-reverse-proxy-companion` ports instead"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1463
+msgid "if you're running Traefik and reverse-proxying directly to the `matrix-synapse` container, you should start reverse-proxying to the `matrix-synapse-reverse-proxy-companion` container instead. See [our updated Traefik example configuration](docs/configuring-playbook-own-webserver.md#sample-configuration-for-running-behind-traefik-20). Note: we now recommend calling the federation entry point `federation` (instead of `synapse`) and reverse-proxying the federation traffic via `matrix-nginx-proxy`, instead of sending it directly to Synapse (or `matrix-synapse-reverse-proxy-companion`). This makes the configuration simpler."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1466
+msgid "2022-11-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1468
+msgid "(Backward Compatibility Break) A new default standalone mode for Etherpad"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1470
+msgid "Until now, [Etherpad](https://etherpad.org/) (which [the playbook could install for you](docs/configuring-playbook-etherpad.md)) required the [Dimension integration manager](docs/configuring-playbook-dimension.md) to also be installed, because Etherpad was hosted on the Dimension domain (at `dimension.example.com/etherpad`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1472
+msgid "From now on, Etherpad can be installed in `standalone` mode on `etherpad.example.com` and used even without Dimension. This is much more versatile, so the playbook now defaults to this new mode (`etherpad_mode: standalone`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1474
+msgid "If you've already got both Etherpad and Dimension in use you could:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1476
+msgid "**either** keep hosting Etherpad under the Dimension domain by adding `etherpad_mode: dimension` to your `vars.yml` file. All your existing room widgets will continue working at the same URLs and no other changes will be necessary."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1478
+msgid "**or**, you could change to hosting Etherpad separately on `etherpad.example.com`. You will need to [configure a DNS record](docs/configuring-dns.md) for this new domain. You will also need to reconfigure Dimension to use the new pad URLs (`https://etherpad.example.com/…`) going forward (refer to our [configuring Etherpad documentation](docs/configuring-playbook-etherpad.md)). All your existing room widgets (which still use `https://dimension.example.com/etherpad/…`) will break as Etherpad is not hosted there anymore. You will need to re-add them or to consider not using `standalone` mode"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1481
+msgid "2022-11-04"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1483
+msgid "The playbook now uses external roles for some things"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1485
+msgid "**TLDR**: when updating the playbook and before running it, you'll need to run `make roles` to make [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) download dependency roles (see the [`requirements.yml` file](requirements.yml)) to the `roles/galaxy` directory. Without this, the playbook won't work."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1487
+msgid "We're in the process of trimming the playbook and making it reuse Ansible roles."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1489
+msgid "Starting now, the playbook is composed of 2 types of Ansible roles:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1491
+msgid "those that live within the playbook itself (`roles/custom/*`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1493
+msgid "those downloaded from other sources (using [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) to `roles/galaxy`, based on the [`requirements.yml` file](requirements.yml)). These roles are maintained by us or by other people from the Ansible community."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1495
+msgid "We're doing this for greater code-reuse (across Ansible playbooks, including our own related playbooks [gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy) and [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy)) and decreased maintenance burden. Until now, certain features were copy-pasted across playbooks or were maintained separately in each one, with improvements often falling behind. We've also tended to do too much by ourselves - installing Docker on the server from our `matrix-base` role, etc. - something that we'd rather not do anymore by switching to the [geerlingguy.docker](https://galaxy.ansible.com/geerlingguy/docker) role."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1497
+msgid "Some variable names will change during the transition to having more and more external (galaxy) roles. There's a new `custom/matrix_playbook_migration` role added to the playbook which will tell you about these changes each time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1499
+msgid "**From now on**, every time you update the playbook (well, every time the `requirements.yml` file changes), it's best to run `make roles` to update the roles downloaded from other sources. `make roles` is a shortcut (a `roles` target defined in [`Makefile`](Makefile) and executed by the [`make`](https://www.gnu.org/software/make/) utility) which ultimately runs [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) to download Ansible roles. If you don't have `make`, you can also manually run the commands seen in the `Makefile`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1502
+msgid "2022-10-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1504
+msgid "synapse-s3-storage-provider support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1506
+msgid "**`synapse-s3-storage-provider` support is very new and still relatively untested. Using it may cause data loss.**"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1508
+msgid "You can now store your Synapse media repository files on Amazon S3 (or another S3-compatible object store) using [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) - a media provider for Synapse (Python module), which should work faster and more reliably than our previous [Goofys](docs/configuring-playbook-s3-goofys.md) implementation (Goofys will continue to work)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1510
+msgid "This is not just for initial installations. Users with existing files (stored in the local filesystem) can also migrate their files to `synapse-s3-storage-provider`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1512
+msgid "To get started, see our [Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3-storage-provider.md) documentation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1514
+msgid "Synapse container image customization support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1516
+msgid "We now support customizing the Synapse container image by adding additional build steps to its [`Dockerfile`](https://docs.docker.com/engine/reference/builder/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1518
+msgid "Our [synapse-s3-storage-provider support](#synapse-s3-storage-provider-support) is actually built on this. When `s3-storage-provider` is enabled, we automatically add additional build steps to install its Python module into the Synapse image."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1520
+msgid "Besides this kind of auto-added build steps (for components supported by the playbook), we also let you inject your own custom build steps using configuration like this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1531
+msgid "People who have needed to customize Synapse previously had to fork the git repository, make their changes to the `Dockerfile` there, point the playbook to the new repository (`matrix_synapse_container_image_self_build_repo`) and enable self-building from scratch (`matrix_synapse_container_image_self_build: true`). This is harder and slower."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1533
+msgid "With the new Synapse-customization feature in the playbook, we use the original upstream (pre-built, if available) Synapse image and only build on top of it, right on the Matrix server. This is much faster than building all of Synapse from scratch."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1536
+msgid "2022-10-02"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1538
+msgid "matrix-ldap-registration-proxy support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1540
+msgid "Thanks to [@TheOneWithTheBraid](https://github.com/TheOneWithTheBraid), we now support installing [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) - a proxy which handles Matrix registration requests and forwards them to LDAP."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1542
+msgid "See our [Setting up matrix-ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1545
+msgid "2022-09-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1547
+msgid "(Potential Backward Compatibility Break) Major improvements to Synapse workers"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1549
+msgid "People who are interested in running a Synapse worker setup should know that **our Synapse worker implementation is much more powerful now**:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1551
+msgid "we've added support for [Stream writers](#stream-writers-support)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1552
+msgid "we've added support for [multiple federation sender workers](#multiple-federation-sender-workers-support)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1553
+msgid "we've added support for [multiple pusher workers](#multiple-pusher-workers-support)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1554
+msgid "we've added support for [running background tasks on a worker](#background-tasks-can-run-on-a-worker)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1555
+msgid "we've restored support for [`appservice` workers](#appservice-worker-support-is-back)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1556
+msgid "we've restored support for [`user_dir` workers](#user-directory-worker-support-is-back)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1557
+msgid "we've made it possible to [reliably use more than 1 `media_repository` worker](#using-more-than-1-media-repository-worker-is-now-more-reliable)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1558
+msgid "see the [Potential Backward Incompatibilities after these Synapse worker changes](#potential-backward-incompatibilities-after-these-synapse-worker-changes)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1560
+msgid "Stream writers support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1562
+msgid "From now on, the playbook lets you easily set up various [stream writer workers](https://matrix-org.github.io/synapse/latest/workers.html#stream-writers) which can handle different streams (`events` stream; `typing` URL endpoints, `to_device` URL endpoints, `account_data` URL endpoints, `receipts` URL endpoints, `presence` URL endpoints). All of this work was previously handled by the main Synapse process, but can now be offloaded to stream writer worker processes."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1564
+msgid "If you're using `matrix_synapse_workers_preset: one-of-each`, you'll automatically get 6 additional workers (one for each of the above stream types). Our `little-federation-helper` preset (meant to be quite minimal and focusing in improved federation performance) does not include stream writer workers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1566
+msgid "If you'd like to customize the number of workers we also make that possible using these variables:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1579
+msgid "Multiple federation sender workers support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1581
+msgid "Until now, we only supported a single `federation_sender` worker (`matrix_synapse_workers_federation_sender_workers_count` could either be `0` or `1`). From now on, you can have as many as you want to help with your federation traffic."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1583
+msgid "Multiple pusher workers support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1585
+msgid "Until now, we only supported a single `pusher` worker (`matrix_synapse_workers_pusher_workers_count` could either be `0` or `1`). From now on, you can have as many as you want to help with pushing notifications out."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1587
+msgid "Background tasks can run on a worker"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1589
+msgid "From now on, you can put [background task processing on a worker](https://matrix-org.github.io/synapse/latest/workers.html#background-tasks)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1591
+msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `background` worker automatically. You can also control the `background` workers count with `matrix_synapse_workers_background_workers_count`. Only  `0` or `1` workers of this type are supported by Synapse."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1593
+msgid "Appservice worker support is back"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1595
+msgid "We previously had an `appservice` worker type, which [Synapse deprecated in v1.59.0](https://github.com/element-hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-synapseappappservice-and-synapseappuser_dir-worker-application-types). So did we, at the time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1597
+msgid "The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of talking to Application Services. From now on, we have support for this."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1599
+msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `appservice` worker automatically. You can also control the `appservice` workers count with `matrix_synapse_workers_appservice_workers_count`. Only  `0` or `1` workers of this type are supported by Synapse."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1601
+msgid "User Directory worker support is back"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1603
+msgid "We previously had a `user_dir` worker type, which [Synapse deprecated in v1.59.0](https://github.com/element-hq/synapse/blob/v1.59.0/docs/upgrade.md#deprecation-of-the-synapseappappservice-and-synapseappuser_dir-worker-application-types). So did we, at the time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1605
+msgid "The new way to implement such workers is by using a `generic_worker` and dedicating it to the task of serving the user directory. From now on, we have support for this."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1607
+msgid "With `matrix_synapse_workers_preset: one-of-each`, you'll get one `user_dir` worker automatically. You can also control the `user_dir` workers count with `matrix_synapse_workers_user_dir_workers_count`. Only  `0` or `1` workers of this type are supported by Synapse."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1609
+msgid "Using more than 1 media repository worker is now more reliable"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1611
+msgid "With `matrix_synapse_workers_preset: one-of-each`, we only launch one `media_repository` worker."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1613
+msgid "If you've been configuring `matrix_synapse_workers_media_repository_workers_count` manually, you may have increased that to more workers. When multiple media repository workers are in use, background tasks related to the media repository must always be configured to run on a single `media_repository` worker via `media_instance_running_background_jobs`. Until now, we weren't doing this correctly, but we now are."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1615
+msgid "Potential Backward Incompatibilities after these Synapse worker changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1617
+msgid "Below we'll discuss **potential backward incompatibilities**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1619
+msgid "**Worker names** (container names, systemd services, worker configuration files) **have changed**. Workers are now labeled sequentially (e.g. `matrix-synapse-worker_generic_worker-18111` -> `matrix-synapse-worker-generic-0`). The playbook will handle these changes automatically."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1621
+msgid "Due to increased worker types support above, people who use `matrix_synapse_workers_preset: one-of-each` should be aware that with these changes, **the playbook will deploy 9 additional workers** (6 stream writers, 1 `appservice` worker, 1 `user_dir` worker, 1 background task worker). This **may increase RAM/CPU usage**, etc. If you find your server struggling, consider disabling some workers with the appropriate `matrix_synapse_workers_*_workers_count` variables."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1623
+msgid "**Metric endpoints have also changed** (`/metrics/synapse/worker/generic_worker-18111` -> `/metrics/synapse/worker/generic-worker-0`). If you're [collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server), consider revisiting our [Collecting Synapse worker metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-server) docs and updating your Prometheus configuration. **If you're collecting metrics to the integrated Prometheus server** (not enabled by default), **your Prometheus configuration will be updated automatically**. Old data (from before this change) may stick around though."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1625
+msgid "**the format of `matrix_synapse_workers_enabled_list` has changed**. You were never advised to use this variable for directly creating workers (we advise people to control workers using `matrix_synapse_workers_preset` or by tweaking `matrix_synapse_workers_*_workers_count` variables only), but some people may have started using the `matrix_synapse_workers_enabled_list` variable to gain more control over workers. If you're one of them, you'll need to adjust its value. See `roles/custom/matrix-synapse/defaults/main.yml` for more information on the new format. The playbook will also do basic validation and complain if you got something wrong."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1628
+msgid "2022-09-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1630
+msgid "Cactus Comments support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1632
+msgid "Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now set up [Cactus Comments](https://cactus.chat) - federated comment system for the web based on Matrix."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1634
+msgid "See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-comments.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1637
+msgid "2022-08-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1639
+msgid "Postmoogle email bridge support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1641
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up the new [Postmoogle](https://github.com/etkecc/postmoogle) email bridge. Postmoogle is like the [email2matrix bridge](https://github.com/devture/email2matrix) (also [already supported by the playbook](docs/configuring-playbook-email2matrix.md)), but more capable and with the intention to soon support *sending* emails, not just receiving."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1643
+msgid "See our [Setting up Postmoogle email bridging](docs/configuring-playbook-bridge-postmoogle.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1646
+msgid "2022-08-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1648
+msgid "mautrix-whatsapp default configuration changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1650
+msgid "In [Pull Request #2012](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2012), we've made some changes to the default configuration used by the `mautrix-whatsapp` bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1652
+msgid "If you're using this bridge, you should look into this PR and see if the new configuration suits you. If not, you can always change individual preferences in your `vars.yml` file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1654
+msgid "Most notably, spaces support has been enabled by default. The bridge will now group rooms into a Matrix space. **If you've already bridged to Whatsapp** prior to this update, you will need to send `!wa sync space` to the bridge bot to make it create the space and put your existing rooms into it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1657
+msgid "2022-08-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1659
+msgid "Conduit support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1661
+msgid "Thanks to [Charles Wright](https://github.com/cvwright), we now have optional experimental [Conduit](https://conduit.rs) homeserver support for new installations. This comes as a follow-up to the playbook getting [Dendrite support](#dendrite-support) earlier this year."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1663
+msgid "Existing Synapse or Dendrite installations do **not** need to be updated. **Synapse is still the default homeserver implementation** installed by the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1665
+msgid "To try out Conduit, we recommend that you **use a new server** and the following `vars.yml` configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1671
+msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse or Dendrite to Conduit) without data loss."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1674
+msgid "2022-07-29"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1676
+msgid "mautrix-discord support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1678
+msgid "Thanks to [MdotAmaan](https://github.com/MdotAmaan)'s efforts, the playbook now supports bridging to [Discord](https://discordapp.com/) via the [mautrix-discord](https://mau.dev/mautrix/discord) bridge. See our [Setting up Mautrix Discord bridging](docs/configuring-playbook-bridge-mautrix-discord.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1680
+msgid "**Note**: this is a new Discord bridge. The playbook still retains Discord bridging via [matrix-appservice-discord](docs/configuring-playbook-bridge-appservice-discord.md) and [mx-puppet-discord](docs/configuring-playbook-bridge-mx-puppet-discord.md). You're free to use the bridge that serves you better, or even all three of them (for different users and use-cases)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1683
+msgid "2022-07-27"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1685
+msgid "matrix-appservice-kakaotalk support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1687
+msgid "The playbook now supports bridging to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) via [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) - a bridge based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code. Thanks to [hnarjis](https://github.com/hnarjis) for helping us add support for this!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1689
+msgid "See our [Setting up Appservice Kakaotalk bridging](docs/configuring-playbook-bridge-appservice-kakaotalk.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1692
+msgid "2022-07-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1694
+msgid "maubot support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1696
+msgid "Thanks to [Stuart Mumford (@Cadair)](https://github.com/cadair) for starting ([PR #373](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/373) and [PR #622](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/622)) and to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s) for finishing up (in [PR #1894](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1894)), the playbook can now help you set up [maubot](https://github.com/maubot/maubot) - a plugin-based Matrix bot system."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1698
+msgid "See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1701
+msgid "2022-07-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1703
+msgid "mx-puppet-skype removal"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1705
+msgid "The playbook no longer includes the [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge, because it has been broken and unmaintained for a long time. Users that have `matrix_mx_puppet_skype_enabled` in their configuration files will encounter an error when running the playbook until they remove references to this bridge from their configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1707
+msgid "To completely clean up your server from `mx-puppet-skype`'s presence on it:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1709
+msgid "ensure your Ansible configuration (`vars.yml` file) no longer contains `matrix_mx_puppet_skype_*` references"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1710
+msgid "stop and disable the systemd service (run `systemctl disable --now matrix-mx-puppet-skype` on the server)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1711
+msgid "delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-skype.service` on the server)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1712
+msgid "delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on the server)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1713
+msgid "drop the `matrix_mx_puppet_skype` database (run `/usr/local/bin/matrix-postgres-cli` on the server, and execute the `DROP DATABASE matrix_mx_puppet_skype;` query there)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1715
+msgid "If you still need bridging to [Skype](https://www.skype.com/), consider switching to [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) instead. See [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1717
+msgid "If you think this is a mistake and `mx-puppet-skype` works for you (or you get it to work somehow), let us know and we may reconsider this removal."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1719
+msgid "signald (0.19.0+) upgrade requires data migration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1721
+msgid "In [Pull Request #1921](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1921) we upgraded [signald](https://signald.org/) (used by the mautrix-signal bridge) from `v0.18.5` to `v0.20.0`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1723
+msgid "Back in the [`v0.19.0` released of signald](https://gitlab.com/signald/signald/-/blob/main/releases/0.19.0.md) (which we skipped and migrated straight to `v0.20.0`), a new `--migrate-data` command had been added that migrates avatars, group images, attachments, etc., into the database (those were previously stored in the filesystem)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1725
+msgid "If you've been using the mautrix-signal bridge for a while, you may have files stored in the local filesystem, which will need to be upgraded."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1727
+msgid "We attempt to do this data migration automatically every time Signald starts (`matrix-mautrix-signal-daemon.service`) using a `ExecStartPre` systemd unit definition."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1729
+msgid "Keep an eye on your Signal bridge and let us know (in our [support room](README.md#support) or in [Pull Request #1921](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1921)) if you experience any trouble!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1732
+msgid "2022-07-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1734
+msgid "Ntfy push notifications support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1736
+msgid "Thanks to [Julian Foad](https://matrix.to/#/@julian:foad.me.uk), the playbook can now install a [ntfy](https://ntfy.sh/) push notifications server for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1738
+msgid "See our [Setting up the ntfy push notifications server](docs/configuring-playbook-ntfy.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1741
+msgid "2022-06-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1743
+msgid "(Potential Backward Compatibility Break) Changes around metrics collection"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1745
+msgid "**TLDR**: we've made extensive **changes to metrics exposure/collection, which concern people using an external Prometheus server**. If you don't know what that is, you don't need to read below."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1747
+msgid "**Why do major changes to metrics**? Because various services were exposing metrics in different, hacky, ways. Synapse was exposing metrics at `/_synapse/metrics` and `/_synapse-worker-…/metrics` on the `matrix.example.com`. The Hookshot role was **repurposing** the Granana web UI domain (`stats.example.com`) for exposing its metrics on `stats.example.com/hookshot/metrics`, while protecting these routes using Basic Authentication **normally used for Synapse** (`/_synapse/metrics`). Node-exporter and Postgres-exporter roles were advising for more `stats.example.com` usage in manual ways. Each role was doing things differently and mixing variables from other roles. Each metrics endpoint was ending up in a different place, protected by who knows what Basic Authentication credentials (if protected at all)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1749
+msgid "**The solution**: a completely revamped way to expose metrics to an external Prometheus server. We are **introducing new `https://matrix.example.com/metrics/*` endpoints**, where various services *can* expose their metrics, for collection by external Prometheus servers. To enable the `/metrics/*` endpoints, use `matrix_nginx_proxy_proxy_matrix_metrics_enabled: true`. There's also a way to protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication). See the `matrix-nginx-proxy` role or our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation for additional variables around `matrix_nginx_proxy_proxy_matrix_metrics_enabled`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1751
+msgid "**If you are using the [Hookshot bridge](docs/configuring-playbook-bridge-hookshot.md)**, you may find that:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1752
+msgid "**Metrics may not be enabled by default anymore**:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1753
+msgid "If Prometheus is enabled (`prometheus_enabled: true`), then Hookshot metrics will be enabled automatically (`matrix_hookshot_metrics_enabled: true`). These metrics will be collected from the local (in-container) Prometheus over the container network."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1754
+msgid "**If Prometheus is not enabled** (you are either not using Prometheus or are using an external one), **Hookshot metrics will not be enabled by default anymore**. Feel free to enable them by setting `matrix_hookshot_metrics_enabled: true`. Also, see below."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1755
+msgid "When metrics are meant to be **consumed by an external Prometheus server**, `matrix_hookshot_metrics_proxying_enabled` needs to be set to `true`, so that metrics would be exposed (proxied) \"publicly\" on `https://matrix.example.com/metrics/hookshot`. To make use of this, you'll also need to enable the new `https://matrix.example.com/metrics/*` endpoints mentioned above, using `matrix_nginx_proxy_proxy_matrix_metrics_enabled`. Learn more in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1756
+msgid "**We've changed the URL we're exposing Hookshot metrics at** for external Prometheus servers. Until now, you were advised to consume Hookshot metrics from `https://stats.example.com/hookshot/metrics` (working in conjunction with `matrix_nginx_proxy_proxy_synapse_metrics`). From now on, **this no longer works**. As described above, you need to start consuming metrics from `https://matrix.example.com/metrics/hookshot`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1758
+msgid "**If you're using node-exporter** (`matrix_prometheus_node_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_node_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/node-exporter`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1760
+msgid "**If you're using [postgres-exporter](docs/configuring-playbook-prometheus-postgres.md)** (`prometheus_postgres_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/postgres-exporter`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1762
+msgid "**If you're using Synapse** and would like to collect its metrics from an external Prometheus server, you may find that:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1764
+msgid "Exposing metrics is now done using `matrix_synapse_metrics_proxying_enabled`, not `matrix_nginx_proxy_proxy_synapse_metrics: true`. You may still need to enable metrics using `matrix_synapse_metrics_enabled: true` before exposing them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1765
+msgid "Protecting metrics endpoints using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) is now done in another way. See our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1766
+msgid "If Synapse metrics are exposed, they will be made available at `https://matrix.example.com/metrics/synapse/main-process` or `https://matrix.example.com/metrics/synapse/worker/TYPE-ID` (when workers are enabled), not at `https://matrix.example.com/_synapse/metrics` and `https://matrix.example.com/_synapse-worker-…/metrics`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1767
+msgid "The playbook still generates an `external_prometheus.yml.example` sample file for scraping Synapse from Prometheus as described in [Collecting Synapse worker metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-synapse-worker-metrics-to-an-external-prometheus-server), but it's now saved under `/matrix/synapse` (not `/matrix`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1769
+msgid "**If you where already using a external Prometheus server** before this change, and you gave a hashed version of the password as a variable, the playbook will now take care of hashing the password for you. Thus, you need to provide the non-hashed version now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1771
+msgid "2022-06-13"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1773
+msgid "go-skype-bridge bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1775
+msgid "Thanks to [CyberShadow](https://github.com/CyberShadow), the playbook can now install the [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) bridge for bridging Matrix to [Skype](https://www.skype.com/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1777
+msgid "See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1779
+msgid "The playbook has supported [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridging (see [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md)) since [2020-04-09](#2020-04-09), but `mx-puppet-skype` is reportedly broken."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1782
+msgid "2022-06-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1784
+msgid "Running Ansible in a container can now happen on the Matrix server itself"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1786
+msgid "If you're tired of being on an old and problematic Ansible version, you can now run [run Ansible in a container on the Matrix server itself](docs/ansible.md#running-ansible-in-a-container-on-the-matrix-server-itself)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1789
+msgid "2022-05-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1791
+msgid "Synapse v1.60 upgrade may cause trouble and require manual intervention"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1793
+msgid "Synapse v1.60 will try to add a new unique index to `state_group_edges` upon startup and could fail if your database is corrupted."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1795
+msgid "We haven't observed this problem yet, but [the Synapse v1.60.0 upgrade notes](https://github.com/element-hq/synapse/blob/v1.60.0/docs/upgrade.md#adding-a-new-unique-index-to-state_group_edges-could-fail-if-your-database-is-corrupted) mention it, so we're giving you a heads up here in case you're unlucky."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1797
+msgid "**If Synapse fails to start** after your next playbook run, you'll need to:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1799
+msgid "SSH into the Matrix server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1800
+msgid "launch `/usr/local/bin/matrix-postgres-cli`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1801
+msgid "switch to the `synapse` database: `\\c synapse`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1802
+msgid "run the following SQL query:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1821
+msgid "You could then restart services: `ansible-playbook -i inventory/hosts setup.yml --tags=start`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1824
+msgid "2022-04-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1826
+msgid "Buscarron bot support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1828
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [the Buscarron bot](https://github.com/etkecc/buscarron). It's a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1830
+msgid "See our [Setting up Buscarron](docs/configuring-playbook-bot-buscarron.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1833
+msgid "2022-04-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1835
+msgid "matrix-registration-bot support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1837
+msgid "Thanks to [Julian-Samuel Gebühr (@moan0s)](https://github.com/moan0s), the playbook can now help you set up [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) - a bot that is used to create and manage registration tokens for a Matrix server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1839
+msgid "See our [Setting up matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1842
+msgid "2022-04-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1844
+msgid "BorgBackup support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1846
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [Borg](https://www.borgbackup.org/) backups with [borgmatic](https://torsion.org/borgmatic/) of your Matrix server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1848
+msgid "See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1850
+msgid "(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1852
+msgid "If you're running a worker setup for Synapse (`matrix_synapse_workers_enabled: true`), the [Synapse v1.57 upgrade notes](https://github.com/element-hq/synapse/blob/v1.57.0rc1/docs/upgrade.md#changes-to-database-schema-for-application-services) say that you may need to take special care when upgrading:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1854
+msgid "Synapse v1.57.0 includes a change to the way transaction IDs are managed for application services. If your deployment uses a dedicated worker for application service traffic, **it must be stopped** when the database is upgraded (which normally happens when the main process is upgraded), to ensure the change is made safely without any risk of reusing transaction IDs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1856
+msgid "If you're not running an `appservice` worker (`matrix_synapse_workers_preset: little-federation-helper` or `matrix_synapse_workers_appservice_workers_count: 0`), you are probably safe to upgrade as per normal, without taking any special care."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1858
+msgid "If you are running a setup with an `appservice` worker, or otherwise want to be on the safe side, we recommend the following upgrade path:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1860
+msgid "Pull the latest playbook changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1861
+msgid "Stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1862
+msgid "Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1863
+msgid "Start Postgres (`systemctl start matrix-postgres` on the server)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1864
+msgid "Start the main Synapse process (`systemctl start matrix-synapse` on the server)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1865
+msgid "Wait a while so that Synapse can start and complete the database migrations. You can use `journalctl -fu matrix-synapse` on the server to get a clue. Waiting a few minutes should also be enough."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1866
+msgid "It should now be safe to start all other services. `ansible-playbook -i inventory/hosts setup.yml --tags=start` will do it for you"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1869
+msgid "2022-04-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1871
+msgid "(Compatibility Break) Changes to `docker-src` permissions necessitating manual action"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1873
+msgid "Users who build container images from source will need to manually correct file permissions of some directories on the server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1875
+msgid "When self-building, the playbook used to `git clone` repositories (into `/matrix/SERVICE/docker-src`) using the `root` user, but now uses `matrix` instead to work around [the following issue with git 2.35.2](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1749)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1877
+msgid "If you're on a non-`amd64` architecture (that is, you're overriding `matrix_architecture` in your `vars.yml` file) or you have enabled self-building for some service (e.g. `matrix_*_self_build: true`), you're certainly building some container images from source and have `docker-src` directories with mixed permissions lying around in various `/matrix/SERVICE` directories."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1879
+msgid "The playbook *could* correct these permissions automatically, but that requires additional Ansible tasks in some ~45 different places - something that takes considerable effort. So we ask users observing errors related to `docker-src` directories to correct the problem manually by **running this command on the Matrix server** (which deletes all `/matrix/*/docker-src` directories): `find /matrix -maxdepth 2 -name 'docker-src' | xargs rm -rf`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1882
+msgid "2022-03-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1884
+msgid "(Compatibility Break) ma1sd identity server no longer installed by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1886
+msgid "The playbook no longer installs the [ma1sd](https://github.com/ma1uta/ma1sd) identity server by default. The next time you run the playbook, ma1sd will be uninstalled from your server, unless you explicitly enable the ma1sd service (see how below)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1888
+msgid "The main reason we used to install ma1sd by default in the past was to prevent Element clients from talking to the `matrix.org` / `vector.im` identity servers, by forcing it to talk to our own self-hosted (but otherwise useless) identity server instead, thus preventing contact list leaks."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1890
+msgid "Since Element clients no longer default to using a public identity server if another one is not provided, we can stop installing ma1sd."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1892
+msgid "If you need to install the ma1sd identity server for some reason, you can explicitly enable it by adding this to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1899
+msgid "2022-02-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1901
+msgid "matrix_encryption_disabler support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1903
+msgid "We now support installing the [matrix_encryption_disabler](https://github.com/digitalentity/matrix_encryption_disabler) Synapse module, which lets you prevent End-to-End-Encryption from being enabled by users on your homeserver. The popular opinion is that this is dangerous and shouldn't be done, but there are valid use cases for disabling encryption discussed [here](https://github.com/matrix-org/synapse/issues/4401)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1905
+msgid "To enable this module (and prevent encryption from being used on your homserver), add `matrix_synapse_ext_encryption_disabler_enabled: true` to your configuration. This module provides further customization. Check its other configuration settings (and defaults) in `roles/custom/matrix-synapse/defaults/main.yml`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1908
+msgid "2022-02-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1910
+msgid "matrix-hookshot bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1912
+msgid "Thanks to [HarHarLinks](https://github.com/HarHarLinks), the playbook can now install the [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) bridge for bridging Matrix to multiple project management services, such as GitHub, GitLab and JIRA. See our [Setting up matrix-hookshot](docs/configuring-playbook-bridge-hookshot.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1915
+msgid "2022-01-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1917
+msgid "ARM support for matrix-corporal"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1919
+msgid "[matrix-corporal](https://github.com/devture/matrix-corporal) (as of version `2.2.3`) is now published to Docker Hub (see [devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-corporal)) as a multi-arch container image with support for all these platforms: `linux/amd64`, `linux/arm64/v8` and `linux/arm/v7`. The playbook no longer resorts to self-building matrix-corporal on these ARM architectures."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1922
+msgid "2022-01-07"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1924
+msgid "Dendrite support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1926
+msgid "**TLDR**: We now have optional experimental [Dendrite](https://github.com/matrix-org/dendrite) homeserver support for new installations. **Existing (Synapse) installations need to be updated**, because some internals changed. See [Adapting the configuration for existing Synapse installations](#adapting-the-configuration-for-existing-synapse-installations)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1928
+msgid "[Jip J. Dekker](https://github.com/Dekker1) did the [initial work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/818) of adding [Dendrite](https://github.com/matrix-org/dendrite) support to the playbook back in January 2021. Lots of work (and time) later, Dendrite support is finally ready for testing."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1930
+msgid "We believe that 2022 will be the year of the non-Synapse Matrix server!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1932
+msgid "The playbook was previously quite [Synapse](https://github.com/element-hq/synapse)-centric, but can now accommodate multiple homeserver implementations. Only one homeserver implementation can be active (installed) at a given time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1934
+msgid "**Synapse is still the default homeserver implementation** installed by the playbook. A new variable (`matrix_homeserver_implementation`) controls which server implementation is enabled (`synapse` or `dendrite` at the given moment)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1936
+msgid "Adapting the configuration for existing Synapse installations"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1938
+msgid "Because the playbook is not so Synapse-centric anymore, a small configuration change is necessary for existing installations to bring them up to date."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1940
+msgid "The `vars.yml` file for **existing installations will need to be updated** by adding this **additional configuration**:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1952
+msgid "Trying out Dendrite"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1954
+msgid "Finally, **to try out Dendrite**, we recommend that you **use a new server** and the following addition to your `vars.yml` configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1960
+msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse to Dendrite) without data loss."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1962
+msgid "We're excited to gain support for other homeserver implementations, like [Conduit](https://conduit.rs/), etc!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1964
+msgid "Honoroit bot support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1966
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now help you set up [Honoroit](https://github.com/etkecc/honoroit) - a helpdesk bot."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1968
+msgid "See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1971
+msgid "2022-01-06"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1973
+msgid "Cinny support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1975
+msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports [Cinny](https://cinny.in/) - a new simple, elegant and secure Matrix client."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1977
+msgid "By default, we still install Element Web. Still, people who'd like to try Cinny out can now install it via the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1979
+msgid "Additional details are available in [Setting up Cinny](docs/configuring-playbook-client-cinny.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1982
+msgid "2021-12-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1984
+msgid "Twitter bridging support via mautrix-twitter"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1986
+msgid "Thanks to [Matthew Cengia](https://github.com/mattcen) and [Shreyas Ajjarapu](https://github.com/shreyasajj), besides [mx-puppet-twitter](docs/configuring-playbook-bridge-mx-puppet-twitter.md), bridging to [Twitter](https://twitter.com/) can now also happen with [mautrix-twitter](docs/configuring-playbook-bridge-mautrix-twitter.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1989
+msgid "2021-12-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1991
+msgid "(Security) Users of the Signal bridge may wish to upgrade it to work around log4j vulnerability"
+msgstr ""
+
+#: ../../../CHANGELOG.md:1993
+msgid "Recently, a security vulnerability affecting the Java logging package `log4j` [has been discovered](https://www.huntress.com/blog/rapid-response-critical-rce-vulnerability-is-affecting-java). Software that uses this Java package is potentially vulnerable."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1995
+msgid "One such piece of software that is part of the playbook is the [mautrix-signal bridge](./docs/configuring-playbook-bridge-mautrix-signal.md), which [has been patched already](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1452). If you're running this bridge, you may wish to [upgrade](./docs/maintenance-upgrading-services.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:1998
+msgid "2021-11-11"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2000
+msgid "Dropped support for Postgres v9.6"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2002
+msgid "Postgres v9.6 reached its end of life today, so the playbook will refuse to run for you if you're still on that version."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2004
+msgid "Synapse still supports v9.6 (for now), but we're retiring support for it early, to avoid having to maintain support for so many Postgres versions. Users that are still on Postgres v9.6 can easily [upgrade Postgres](docs/maintenance-postgres.md#upgrading-postgresql) via the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2007
+msgid "2021-10-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2009
+msgid "Hangouts bridge no longer updated, superseded by a Googlechat bridge"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2011
+msgid "The mautrix-hangouts bridge is no longer receiving updates upstream and is likely to stop working in the future. We still retain support for this bridge in the playbook, but you're encouraged to switch away from it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2013
+msgid "There's a new [mautrix-googlechat](https://github.com/mautrix/googlechat) bridge that you can [install using the playbook](docs/configuring-playbook-bridge-mautrix-googlechat.md). Your **Hangouts bridge data will not be migrated**, however. You need to start fresh with the new bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2016
+msgid "2021-08-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2018
+msgid "LinkedIn bridging support via beeper-linkedin"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2020
+msgid "Thanks to [Alexandar Mechev](https://github.com/apmechev), the playbook can now install the [beeper-linkedin](https://gitlab.com/beeper/linkedin) bridge for bridging to [LinkedIn](https://www.linkedin.com/) Messaging."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2022
+msgid "This brings the total number of bridges supported by the playbook up to 20. See all supported bridges [here](docs/configuring-playbook.md#bridging-other-networks)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2024
+msgid "To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2027
+msgid "2021-08-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2029
+msgid "Sygnal upgraded - ARM support and no longer requires a database"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2031
+msgid "The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been upgraded from `v0.9.0` to `v0.10.1`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2033
+msgid "This is an optional component for the playbook, so most of our users wouldn't care about this announcement."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2035
+msgid "Since this feels like a relatively big (and untested, as of yet) Sygnal change, we're putting up this changelog entry."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2037
+msgid "The new version is also available for the ARM architecture. It also no longer requires a database anymore. If you need to downgrade to the previous version, changing `matrix_sygnal_version` or `matrix_sygnal_docker_image` will not be enough, as we've removed the `database` configuration completely. You'd need to switch to an earlier playbook commit."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2040
+msgid "2021-05-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2042
+msgid "Hydrogen support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2044
+msgid "Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook now supports [Hydrogen](https://github.com/vector-im/hydrogen-web) - a new lightweight Matrix client with legacy and mobile browser support."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2046
+msgid "By default, we still install Element Web, as Hydrogen is still not fully-featured. Still, people who'd like to try Hydrogen out can now install it via the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2048
+msgid "Additional details are available in [Setting up Hydrogen](docs/configuring-playbook-client-hydrogen.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2051
+msgid "2021-05-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2053
+msgid "Heisenbridge support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2055
+msgid "Thanks to [Toni Spets (hifi)](https://github.com/hifi), the playbook now supports bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) using yet another bridge (besides matrix-appservice-irc), called [Heisenbridge](https://github.com/hifi/heisenbridge)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2057
+msgid "Additional details are available in [Setting up Heisenbridge bouncer-style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2060
+msgid "2021-04-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2062
+msgid "Disabling TLSv1 and TLSv1.1 for Coturn"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2064
+msgid "To improve security, we've [removed TLSv1 and TLSv1.1 support](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/999) from our default [Coturn](https://github.com/coturn/coturn) configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2066
+msgid "If you need to support old clients, you can re-enable both (or whichever one you need) with the following configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2074
+msgid "2021-04-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2076
+msgid "Automated local Postgres backup support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2078
+msgid "Thanks to [foxcris](https://github.com/foxcris), the playbook can now make automated local Postgres backups on a fixed schedule using [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2080
+msgid "Additional details are available in [Setting up postgres backup](docs/configuring-playbook-postgres-backup.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2083
+msgid "2021-04-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2085
+msgid "Mjolnir moderation tool (bot) support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2087
+msgid "Thanks to [Aaron Raimist](https://github.com/aaronraimist), the playbook can now install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation tool (bot)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2089
+msgid "Additional details are available in [Setting up Mjolnir](docs/configuring-playbook-bot-mjolnir.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2092
+msgid "2021-03-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2094
+msgid "Sygnal push gateway support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2096
+msgid "The playbook can now install the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2098
+msgid "This is only useful to people who develop/build their own Matrix client applications."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2100
+msgid "Additional details are available in our [Setting up the Sygnal push gateway](docs/configuring-playbook-sygnal.md) docs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2103
+msgid "2021-03-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2105
+msgid "Go-NEB support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2107
+msgid "Thanks to [Zir0h](https://github.com/Zir0h), the playbook can now install and configure the [Go-NEB](https://github.com/matrix-org/go-neb) bot."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2109
+msgid "Additional details are available in [Setting up Go-NEB](docs/configuring-playbook-bot-go-neb.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2112
+msgid "2021-02-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2114
+msgid "GroupMe bridging support via mx-puppet-groupme"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2116
+msgid "Thanks to [Cody Neiman](https://github.com/xangelix), the playbook can now install the [mx-puppet-groupme](https://gitlab.com/robintown/mx-puppet-groupme) bridge for bridging to [GroupMe](https://groupme.com)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2118
+msgid "This brings the total number of bridges supported by the playbook up to 18. See all supported bridges [here](docs/configuring-playbook.md#bridging-other-networks)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2120
+msgid "To get started, follow our [Setting up MX Puppet GroupMe](docs/configuring-playbook-bridge-mx-puppet-groupme.md) docs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2122
+msgid "Mautrix Instagram bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2124
+msgid "The playbook now supports bridging with [Instagram](https://www.instagram.com/) by installing the [mautrix-instagram](https://github.com/tulir/mautrix-instagram) bridge. This playbook functionality is available thanks to [@MarcProe](https://github.com/MarcProe)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2126
+msgid "Additional details are available in [Setting up Mautrix Instagram bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2128
+msgid "Synapse workers support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2130
+msgid "After [lots and lots of work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/456) (done over many months by [Marcel Partap](https://github.com/eMPee584), [Max Klenk](https://github.com/maxklenk), a few others from the [Technical University of Dresden, Germany](https://tu-dresden.de/) and various other contributors), support for Synapse workers has finally landed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2132
+msgid "Having support for workers makes the playbook suitable for larger homeserver deployments."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2134
+msgid "Our setup is not yet perfect (we don't support all types of workers; scaling some of them (like `pusher`, `federation_sender`) beyond a single instance is not yet supported). Still, it's a great start and can already power homeservers with thousands of users, like the [Matrix deployment at TU Dresden](https://doc.matrix.tu-dresden.de/en/) discussed in [Matrix Live S06E09 - TU Dresden on their Matrix deployment](https://www.youtube.com/watch?v=UHJX2pmT2gk)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2136
+msgid "By default, workers are disabled and Synapse runs as a single process (homeservers don't necessarily need the complexity and increased memory requirements of running a worker-based setup)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2138
+msgid "To enable Synapse workers, follow our [Load balancing with workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) documentation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2141
+msgid "2021-02-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2143
+msgid "(Potential Breaking Change) Monitoring/metrics support using Prometheus and Grafana"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2145
+msgid "Thanks to [@Peetz0r](https://github.com/Peetz0r), the playbook can now install a bunch of tools for monitoring your Matrix server: the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2147
+msgid "To get get these installed, follow our [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](docs/configuring-playbook-prometheus-grafana.md) docs page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2149
+msgid "This update comes with a **potential breaking change** for people who were already exposing Synapse metrics (for consumption via another Prometheus installation). From now on, `matrix_synapse_metrics_enabled: true` no longer exposes metrics publicly via matrix-nginx-proxy (at `https://matrix.example.com/_synapse/metrics`). To do so, you'd need to explicitly set `matrix_nginx_proxy_proxy_synapse_metrics: true`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2152
+msgid "2021-01-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2154
+msgid "Etherpad support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2156
+msgid "Thanks to [@pushytoxin](https://github.com/pushytoxin), the playbook can now install the [Etherpad](https://etherpad.org) realtime collaborative text editor. It can be used in a [Jitsi](https://jitsi.org/) audio/video call or integrated as a widget into Matrix chat rooms via the [Dimension](https://dimension.t2bot.io) integration manager."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2158
+msgid "To get it installed, follow [our Etherpad docs page](docs/configuring-playbook-etherpad.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2161
+msgid "2021-01-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2163
+msgid "(Breaking Change) Postgres changes that require manual intervention"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2165
+msgid "We've made a lot of changes to our Postgres setup and some manual action is required (described below). Sorry about the hassle."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2167
+msgid "**TLDR**: people running an [external Postgres server](docs/configuring-playbook-external-postgres.md) don't need to change anything for now. Everyone else (the common/default case) is affected and manual intervention is required."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2169
+msgid "Why?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2171
+msgid "we had a default Postgres password (`matrix_postgres_connection_password: synapse-password`), which we think is **not ideal for security anymore**. We now ask you to generate/provide a strong password yourself. Postgres is normally not exposed outside the container network, making it relatively secure, but still:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2172
+msgid "by tweaking the configuration, you may end up intentionally or unintentionally exposing your Postgres server to the local network (or even publicly), while still using the default default credentials (`synapse` + `synapse-password`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2173
+msgid "we can't be sure we trust all these services (bridges, etc). Some of them may try to talk to or attack `matrix-postgres` using the default credentials (`synapse` + `synapse-password`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2174
+msgid "you may have other containers running on the same Docker network, which may try to talk to or attack `matrix-postgres` using the default credentials (`synapse` + `synapse-password`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2175
+msgid "our Postgres usage **was overly-focused on Synapse** (default username of `synapse` and default/main database of `homeserver`). Additional homeserver options are likely coming in the future ([Dendrite](https://matrix.org/docs/projects/server/dendrite), [Conduit](https://matrix.org/docs/projects/server/conduit), [The Construct](https://matrix.org/docs/projects/server/construct)), so being too focused on `matrix-synapse` is not great. From now on, Synapse is just another component of this playbook, which happens to have an *additional database* (called `synapse`) on the Postgres server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2176
+msgid "we try to reorganize things a bit, to make the playbook even friendlier to people running an [external Postgres server](docs/configuring-playbook-external-postgres.md). Work on this will proceed in the future."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2178
+msgid "So, this is some **effort to improve security** and to **prepare for a brighter future of having more homeserver options** than just Synapse."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2180
+msgid "What has really changed?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2182
+msgid "the default superuser Postgres username is now `matrix` (used to be `synapse`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2183
+msgid "the default Postgres database is now `matrix` (used to be `homeserver`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2184
+msgid "Synapse's database is now `synapse` (used to be `homeserver`). This is now just another \"additional database\" that the playbook manages for you"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2185
+msgid "Synapse's user called `synapse` is just a regular user that can only use the `synapse` database (not a superuser anymore)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2187
+msgid "What do I do if I'm using the integrated Postgres server (default)?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2189
+msgid "By default, the playbook runs an integrated Postgres server for you in a container (`matrix-postgres`). Unless you've explicitly configured an [external Postgres server](docs/configuring-playbook-external-postgres.md), these steps are meant for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2191
+msgid "To migrate to the new setup, expect a few minutes of downtime, while you follow these steps:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2193
+msgid "We believe the steps below are safe and you won't encounter any data loss, but consider [making a Postgres backup](docs/maintenance-postgres.md#backing-up-postgresql) anyway. If you've never backed up Postgres, now would be a good time to try it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2195
+msgid "Generate a strong password to be used for your superuser Postgres user (called `matrix`). You can create one with a command like `pwgen -s 64 1`. The **maximum length** for a Postgres password is 100 bytes (characters). Don't go crazy!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2197
+msgid "Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` file, adding a line like this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2202
+#: ../../../CHANGELOG.md:2214
+msgid ".. where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2204
+msgid "Stop all services: `ansible-playbook -i inventory/hosts setup.yml --tags=stop`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2205
+msgid "Log in to the server via SSH. The next commands will be performed there."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2206
+msgid "Start the Postgres database server: `systemctl start matrix-postgres`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2207
+msgid "Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2208
+msgid "Execute the following query, while making sure to **change the password inside** (**don't forget the ending `;`**):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2216
+msgid "Execute the following queries as you see them (no modifications necessary, so you can just **paste them all at once**):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2234
+msgid "You may need to press *Enter* after pasting the lines above."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2236
+msgid "Re-run the playbook normally: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2238
+msgid "What do I do if I'm using an external Postgres server?"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2240
+msgid "If you've explicitly configured an [external Postgres server](docs/configuring-playbook-external-postgres.md), there are **no changes** that you need to do at this time."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2242
+msgid "The fact that we've renamed Synapse's database from `homeserver` to `synapse` (in our defaults) should not affect you, as you're already explicitly defining `matrix_synapse_database_database` (if you've followed our guide, that is). If you're not explicitly defining this variable, you may wish to do so (`matrix_synapse_database_database: homeserver`), to avoid the new `synapse` default and keep things as they were."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2245
+msgid "2021-01-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2247
+msgid "(Breaking Change) The mautrix-facebook bridge now requires a Postgres database"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2249
+msgid "**Update from 2021-11-15**: SQLite support has been re-added to the mautrix-facebook bridge in [v0.3.2](https://github.com/mautrix/facebook/releases/tag/v0.3.2). You can ignore this changelog entry."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2251
+msgid "A new version of the [mautrix-facebook](https://github.com/tulir/mautrix-facebook) bridge has been released. It's a full rewrite of its backend and the bridge now requires Postgres. New versions of the bridge can no longer run on SQLite."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2253
+msgid "**TLDR**: if you're NOT using an [external Postgres server](docs/configuring-playbook-external-postgres.md) and have NOT forcefully kept the bridge on SQLite during [The big move to all-on-Postgres (potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous), you will be automatically upgraded without manual intervention. All you need to do is send a `login` message to the Facebook bridge bot again."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2255
+msgid "Whether this change requires your intervention depends mostly on:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2256
+msgid "whether you're using an [external Postgres server](docs/configuring-playbook-external-postgres.md). If yes, then [you need to do something](#upgrade-path-for-people-running-an-external-postgres-server)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2257
+msgid "or whether you've force-changed the bridge's database engine to SQLite (`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) some time in the past (likely during [The big move to all-on-Postgres (potentially dangerous)](#the-big-move-to-all-on-postgres-potentially-dangerous))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2259
+msgid "As already mentioned above, you most likely don't need to do anything. If you rerun the playbook and don't get an error, you've been automatically upgraded. Just send a `login` message to the Facebook bridge bot again. Otherwise, read below for a solution."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2261
+msgid "Upgrade path for people NOT running an external Postgres server (default for the playbook)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2263
+msgid "If you're **not running an external Postgres server**, then this bridge either already works on Postgres for you, or you've intentionally kept it back on SQLite with custom configuration (`matrix_mautrix_facebook_database_engine: 'sqlite'` in your `vars.yml`) ."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2265
+msgid "Simply remove that custom configuration from your `vars.yml` file (if it's there) and re-run the playbook. It should upgrade you automatically. You'll need to send a `login` message to the Facebook bridge bot again."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2267
+msgid "Alternatively, [you can stay on SQLite for a little longer](#staying-on-sqlite-for-a-little-longer-temporary-solution)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2269
+msgid "Upgrade path for people running an external Postgres server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2271
+msgid "For people using the internal Postgres server (the default for the playbook):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2272
+msgid "we automatically create an additional `matrix_mautrix_facebook` Postgres database and credentials to access it"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2273
+msgid "we automatically adjust the bridge's `matrix_mautrix_facebook_database_*` variables to point the bridge to that Postgres database"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2274
+msgid "we use [pgloader](https://pgloader.io/) to automatically import the existing SQLite data for the bridge into the `matrix_mautrix_facebook` Postgres database"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2276
+msgid "If you are using an [external Postgres server](docs/configuring-playbook-external-postgres.md), unfortunately we currently can't do any of that for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2278
+msgid "You have 3 ways to proceed:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2280
+msgid "contribute to the playbook to make this possible (difficult)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2281
+msgid "or, do the migration \"steps\" manually:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2282
+msgid "stop the bridge (`systemctl stop matrix-mautrix-facebook`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2283
+msgid "create a new `matrix_mautrix_facebook` Postgres database for it"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2284
+msgid "run [pgloader](https://pgloader.io/) manually (we import this bridge's data using default settings and it works well)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2285
+msgid "define `matrix_mautrix_facebook_database_*` variables in your `vars.yml` file (credentials, etc.) - you can find their defaults in `roles/custom/matrix-mautrix-facebook/defaults/main.yml`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2286
+msgid "switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: 'postgres'` in your `vars.yml` file)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2287
+msgid "re-run the playbook (`--tags=setup-all,start`) and ensure the bridge works (`systemctl status matrix-mautrix-facebook` and `journalctl -fu matrix-mautrix-facebook`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2288
+msgid "send a `login` message to the Facebook bridge bot again"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2289
+msgid "or, [stay on SQLite for a little longer (temporary solution)](#staying-on-sqlite-for-a-little-longer-temporary-solution)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2291
+msgid "Staying on SQLite for a little longer (temporary solution)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2293
+msgid "To keep using this bridge with SQLite for a little longer (**not recommended**), use the following configuration in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2303
+msgid "If you do this, keep in mind that **you can't run this forever**. This SQLite-supporting bridge version is not getting any updates and will break sooner or later. The playbook will also drop support for SQLite at some point in the future."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2306
+msgid "2021-01-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2308
+msgid "matrix-corporal goes 2.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2310
+msgid "[matrix-corporal v2 has been released](https://github.com/devture/matrix-corporal/releases/tag/2.0.0) and the playbook also supports it now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2312
+msgid "No manual intervention is required in the common case."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2314
+msgid "The new [matrix-corporal](https://github.com/devture/matrix-corporal) version is also the first one to support Interactive Authentication. If you wish to enable that (hint: you should), you'll need to set up the [REST auth password provider](docs/configuring-playbook-rest-auth.md). There's more information in [our matrix-corporal docs](docs/configuring-playbook-matrix-corporal.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2317
+msgid "2021-01-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2319
+msgid "Moving from cronjobs to systemd timers"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2321
+msgid "We no longer use cronjobs for Let's Encrypt SSL renewal and `matrix-nginx-proxy`/`matrix-coturn` reloading. Instead, we've switched to systemd timers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2323
+msgid "The largest benefit of this is that we no longer require you to install a cron daemon, thus simplifying our install procedure."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2325
+msgid "The playbook will migrate you from cronjobs to systemd timers automatically. This is just a heads up."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2328
+msgid "2021-01-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2330
+msgid "(Breaking Change) New SSL configuration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2332
+msgid "SSL configuration (protocols, ciphers) can now be more easily controlled thanks to us making use of configuration presets."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2334
+msgid "We define a few presets (old, intermediate, modern), following the [Mozilla SSL Configuration Generator](https://ssl-config.mozilla.org/#server=nginx)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2336
+msgid "A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is used (defaults to `\"intermediate\"`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2338
+msgid "Compared to before, this changes nginx's `ssl_prefer_server_ciphers` to `off`  (used to default to `on`). It also add some more ciphers to the list, giving better performance on mobile devices, and removes some weak ciphers. More information in the [documentation](docs/configuring-playbook-nginx.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2340
+msgid "To revert to the old behaviour, set the following variables:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2347
+msgid "Just like before, you can still use your own custom protocols by specifying them in `matrix_nginx_proxy_ssl_protocols`. Doing so overrides the values coming from the preset."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2350
+msgid "2021-01-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2352
+msgid "Signal bridging support via mautrix-signal"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2354
+msgid "Thanks to [laszabine](https://github.com/laszabine)'s efforts, the playbook now supports bridging to [Signal](https://www.signal.org/) via the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge. See our [Setting up Mautrix Signal bridging](docs/configuring-playbook-bridge-mautrix-signal.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2356
+msgid "If you had installed the mautrix-signal bridge while its Pull Request was still work-in-progress, you can migrate your data to the new and final setup by referring to [this comment](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/686#issuecomment-753510789)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2359
+msgid "2020-12-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2361
+msgid "The big move to all-on-Postgres (potentially dangerous)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2363
+msgid "**TLDR**: all your bridges (and other services) will likely be auto-migrated from SQLite/nedb to Postgres, hopefully without trouble. You can opt-out (see how below), if too worried about breakage."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2365
+msgid "Until now, we've only used Postgres as a database for Synapse. All other services (bridges, bots, etc.) were kept simple and used a file-based database (SQLite or nedb)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2367
+msgid "Since [this huge pull request](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/740), **all of our services now use Postgres by default**. Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann) for starting the work on it and for providing great input!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2369
+msgid "Moving all services to Postgres brings a few **benefits** to us:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2371
+msgid "**improved performance**"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2372
+msgid "**improved compatibility**. Most bridges are deprecating SQLite/nedb support or offer less features when not on Postgres."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2373
+msgid "**easier backups**. It's still some effort to take a proper backup (Postgres dump + various files, keys), but a Postgres dump now takes you much further."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2374
+msgid "we're now **more prepared to introduce other services** that need a Postgres database - [Dendrite](https://github.com/matrix-org/dendrite), the [mautrix-signal](https://github.com/tulir/mautrix-signal) bridge (existing [pull request](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/686)), etc."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2376
+msgid "Key takeway"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2378
+msgid "existing installations that use an [external Postgres](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-external-postgres.md) server should be unaffected (they remain on SQLite/nedb for all services, except Synapse)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2380
+msgid "for existing installations which use our integrated Postgres database server (`matrix-postgres`, which is the default), **we automatically migrate data** from SQLite/nedb to Postgres and **archive the database files** (`something.db` -> `something.db.backup`), so you can restore them if you need to go back (see how below)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2382
+msgid "Opting-out of the Postgres migration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2384
+msgid "This is a **very large and somewhat untested change** (potentially dangerous), so **if you're not feeling confident/experimental, opt-out** of it for now. Still, it's the new default and what we (and various bridges) will focus on going forward, so don't stick to old ways for too long."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2386
+msgid "You can remain on SQLite/nedb (at least for now) by adding a variable like this to your `vars.yml` file for each service you use: `matrix_COMPONENT_database_engine: sqlite` (e.g. `matrix_mautrix_facebook_database_engine: sqlite`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2388
+msgid "Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2390
+msgid "Going back to SQLite/nedb if things went wrong"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2392
+msgid "If you went with the Postgres migration and it went badly for you (some bridge not working as expected or not working at all), do this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2394
+msgid "stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2395
+msgid "SSH into the server and rename the old database files (`something.db.backup` -> `something.db`). Example: `mv /matrix/mautrix-facebook/data/mautrix-facebook.db.backup /matrix/mautrix-facebook/data/mautrix-facebook.db`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2396
+msgid "switch the affected service back to SQLite (e.g. `matrix_mautrix_facebook_database_engine: sqlite`). Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2397
+msgid "re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2398
+msgid "[get in touch](README.md#support) with us"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2400
+msgid "2020-12-11"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2402
+msgid "synapse-janitor support removed"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2404
+msgid "We've removed support for the unmaintained [synapse-janitor](https://github.com/xwiki-labs/synapse_scripts) script. There's been past reports of it corrupting the Synapse database. Since there hasn't been any new development on it and it doesn't seem too useful nowadays, there's no point in including it in the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2406
+msgid "If you need to clean up or compact your database, consider using the Synapse Admin APIs directly. See our [Synapse maintenance](docs/maintenance-synapse.md) and [Postgres maintenance](docs/maintenance-postgres.md) documentation pages for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2408
+msgid "Docker 20.10 is here"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2410
+msgid "(No need to do anything special in relation to this. Just something to keep in mind)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2412
+msgid "Docker 20.10 got released recently and your server will likely get it the next time you update."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2414
+msgid "This is the first major Docker update in a long time and it packs a lot of changes. Some of them introduced some breakage for us initially (see [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/d08b27784f222effcbce2abf924bf07bbe0893be) and [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/commit/7593d969e316cc0144bce378a5be58c76c2c37ee)), but it should be all good now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2417
+msgid "2020-12-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2419
+msgid "openid APIs exposed by default on the federation port when federation disabled"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2421
+msgid "We've changed some defaults. People running with our default configuration (federation enabled), are not affected at all."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2423
+msgid "If you are running an unfederated server (`matrix_synapse_federation_enabled: false`), this may be of interest to you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2425
+msgid "When federation is disabled, but ma1sd or Dimension are enabled, we'll now expose the `openid` APIs on the federation port. These APIs are necessary for some ma1sd features to work. If you'd like to prevent this, you can: `matrix_synapse_federation_port_openid_resource_required: false`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2428
+msgid "2020-11-27"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2430
+msgid "Recent Jitsi updates may require configuration changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2432
+msgid "We've recently [updated from Jitsi build 4857 to build 5142](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/719), which brings a lot of configuration changes."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2434
+msgid "**If you use our default Jitsi settings, you won't have to do anything.**"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2436
+msgid "People who have [fine-tuned Jitsi](docs/configuring-playbook-jitsi.md#optional-fine-tune-jitsi) may find that some options got renamed now, others are gone and yet others still need to be defined in another way."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2438
+msgid "The next time you run the playbook [installation](docs/installing.md) command, our validation logic will tell you if you're using some variables like that and will recommend a migration path for each one."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2440
+msgid "Additionally, we've recently disabled transcriptions (`jitsi_enable_transcriptions: false`) and recording (`jitsi_enable_recording: false`) by default. These features did not work anyway, because we don't install the required dependencies for them (Jigasi and Jibri, respectively). If you've been somehow pointing your Jitsi installation to some manually installed Jigasi/Jibri service, you may need to toggle these flags back to enabled to have transcriptions and recordings working."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2443
+msgid "2020-11-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2445
+#: ../../../CHANGELOG.md:2453
+msgid "Breaking change matrix-sms-bridge"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2447
+msgid "Because of many problems using gammu as SMS provider, matrix-sms-bridge now uses (https://github.com/RebekkaMa/android-sms-gateway-server) by default. See (the docs)[./docs/configuring-playbook-bridge-matrix-bridge-sms.md] which new vars you need to add."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2449
+msgid "If you are using this playbook to deploy matrix-sms-bridge and still really want to use gammu as SMS provider, we could possibly add support for both android-sms-gateway-server and gammu."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2451
+msgid "2020-11-13"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2455
+msgid "The new version of [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) changed its database from neo4j to h2. You need to sync the bridge at the first start. Note that this only will sync rooms where the @smsbot:yourServer is member. For rooms without @smsbot:yourServer you need to kick and invite the telephone number **or** invite @smsbot:yourServer."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2457
+msgid "Add the following to your `vars.yml` file: `matrix_sms_bridge_container_extra_arguments=['--env SPRING_PROFILES_ACTIVE=initialsync']`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2458
+msgid "Login to your host shell and remove old systemd file from your host: `rm /etc/systemd/system/matrix-sms-bridge-database.service`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2459
+msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-sms-bridge,start`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2460
+msgid "Login to your host shell and check the logs with `journalctl -u matrix-sms-bridge` until the sync finished."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2461
+msgid "Remove the var from the first step."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2462
+msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2464
+msgid "2020-11-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2466
+msgid "Dynamic DNS support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2468
+msgid "Thanks to [Scott Crossen](https://github.com/scottcrossen), the playbook can now manage Dynamic DNS for you using [ddclient](https://ddclient.net/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2470
+msgid "To learn more, follow our [Dynamic DNS docs page](docs/configuring-playbook-dynamic-dns.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2473
+msgid "2020-10-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2475
+msgid "(Compatibility Break) https://matrix.example.com/ now redirects to https://element.example.com/"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2477
+msgid "Until now, we used to serve a static page coming from Synapse at `https://matrix.example.com/`. This page was not very useful to anyone."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2479
+msgid "Since `matrix.example.com` may be accessed by regular users in certain conditions, it's probably better to redirect them to a better place (e.g. to [Element Web](docs/configuring-playbook-client-element-web.md))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2481
+msgid "If Element Web is installed (`matrix_client_element_enabled: true`, which it is by default), we now redirect people to it, instead of showing them a Synapse static page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2483
+msgid "If you'd like to control where the redirect goes, use the `matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain` variable. To restore the old behavior of not redirecting anywhere and serving the Synapse static page, set it to an empty value (`matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain: \"\"`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2486
+msgid "2020-10-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2488
+msgid "(Compatibility Break) /_synapse/admin is no longer publicly exposed by default"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2490
+msgid "We used to expose the Synapse Admin APIs publicly (at `https://matrix.example.com/_synapse/admin`). These APIs require authentication with a valid access token, so it's not that big a deal to expose them."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2492
+msgid "However, following [official Synapse's reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints), we're no longer exposing `/_synapse/admin` by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2494
+msgid "If you'd like to restore restore the old behavior and expose `/_synapse/admin` publicly, you can use the following configuration (in your `vars.yml`):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2501
+msgid "2020-10-02"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2503
+msgid "Minimum Ansible version raised to v2.7.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2505
+msgid "We were claiming to support [Ansible](https://www.ansible.com/) v2.5.2 and higher, but issues like [#662](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/662) demonstrate that we need at least v2.7.0."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2507
+msgid "If you've been using the playbook without getting any errors until now, you're probably on a version higher than that already (or you're not using the `matrix-ma1sd` and `matrix-client-element` roles)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2509
+msgid "Our [Ansible docs page](docs/ansible.md) contains information on how to run a more up-to-date version of Ansible."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2512
+msgid "2020-10-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2514
+msgid "Postgres 13 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2516
+msgid "The playbook now installs [Postgres 13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2518
+msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x, 10.x, 11.x or 12.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2520
+msgid "2020-09-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2522
+msgid "matrix-registration support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2524
+msgid "The playbook can now help you set up [matrix-registration](https://github.com/ZerataX/matrix-registration) - an application that lets you keep your Matrix server's registration private, but still allow certain users (those having a unique registration link) to register by themselves."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2526
+msgid "See our [Setting up matrix-registration](docs/configuring-playbook-matrix-registration.md) documentation page to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2529
+msgid "2020-08-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2531
+msgid "rust-synapse-compress-state support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2533
+msgid "The playbook can now help you use [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) to compress the state groups in your Synapse database."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2535
+msgid "See our [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state) documentation page to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2538
+msgid "2020-07-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2540
+msgid "Synapse Admin support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2542
+msgid "The playbook can now help you set up [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2544
+msgid "See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-admin.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2547
+msgid "2020-07-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2549
+msgid "matrix-reminder-bot support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2551
+msgid "The playbook can now help you set up [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2553
+msgid "See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-matrix-reminder-bot.md) documentation to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2556
+msgid "2020-07-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2558
+msgid "(Compatibility Break) Riot is now Element"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2560
+msgid "As per the official announcement, [Riot has been rebraned to Element](https://element.io/blog/welcome-to-element/)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2562
+msgid "The playbook follows suit. Existing installations have a few options for how to handle this."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2564
+msgid "See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md#migrating-to-element) documentation page for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2567
+msgid "2020-07-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2569
+msgid "Steam bridging support via mx-puppet-steam"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2571
+msgid "Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the playbook now supports bridging to [Steam](https://steamapp.com/) via the [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) bridge. See our [Setting up MX Puppet Steam bridging](docs/configuring-playbook-bridge-mx-puppet-steam.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2574
+msgid "2020-07-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2576
+msgid "Discord bridging support via mx-puppet-discord"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2578
+msgid "Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the playbook now supports bridging to [Discord](https://discordapp.com/) via the [mx-puppet-discord](https://github.com/Sorunome/mx-puppet-discord) bridge. See our [Setting up MX Puppet Discord bridging](docs/configuring-playbook-bridge-mx-puppet-discord.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2580
+msgid "**Note**: this is a new Discord bridge. The playbook still retains Discord bridging via [matrix-appservice-discord](docs/configuring-playbook-bridge-appservice-discord.md). You're free too use the bridge that serves you better, or even both (for different users and use-cases)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2583
+msgid "2020-06-30"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2585
+msgid "Instagram and Twitter bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2587
+msgid "Thanks to [Johanna Dorothea Reichmann](https://github.com/jdreichmann)'s efforts, the playbook now supports bridging to [Instagram](https://www.instagram.com/) via the [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) bridge. See our [Setting up MX Puppet Instagram bridging](docs/configuring-playbook-bridge-mx-puppet-instagram.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2589
+msgid "Thanks to [Tulir Asokan](https://github.com/tulir)'s efforts, the playbook now supports bridging to [Twitter](https://twitter.com/) via the [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) bridge. See our [Setting up MX Puppet Twitter bridging](docs/configuring-playbook-bridge-mx-puppet-twitter.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2592
+msgid "2020-06-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2594
+msgid "(Post Mortem / fixed Security Issue) Re-enabling User Directory search powered by the ma1sd Identity Server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2596
+#: ../../../CHANGELOG.md:2625
+msgid "User Directory search requests used to go to the ma1sd identity server by default, which queried its own stores and the Synapse database."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2598
+msgid "ma1sd's [security issue](https://github.com/ma1uta/ma1sd/issues/44) has been fixed in version `2.4.0`, with [this commit](ma1uta/ma1sd@2bb5a734d11662b06471113cf3d6b4cee5e33a85). `ma1sd 2.4.0` is now the default version for this playbook. For more information on what happened, please check the mentioned issue."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2600
+msgid "We are re-enabling user directory search with this update. Those who would like to keep it disabled can use this configuration: `matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2602
+msgid "As always, re-running the playbook is enough to get the updated bits."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2604
+msgid "2020-06-11"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2606
+msgid "SMS bridging requires db reset"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2608
+msgid "The current version of [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) needs you to delete the database to work as expected. Just remove `/matrix/matrix-sms-bridge/database/*`. It also adds a new requried var `matrix_sms_bridge_default_region`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2610
+msgid "To reuse your existing rooms, invite `@smsbot:yourServer` to the room or write a message. You are also able to use automated room creation with telephonenumers by writing `sms send -t 01749292923 \"Hello World\"` in a room with `@smsbot:yourServer`. See [the docs](https://github.com/benkuly/matrix-sms-bridge) for more information."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2612
+msgid "2020-06-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2614
+msgid "SMS bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2616
+msgid "Thanks to [benkuly](https://github.com/benkuly)'s efforts, the playbook now supports bridging to SMS (with one telephone number only) via [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2618
+msgid "See our [Setting up Matrix SMS bridging](docs/configuring-playbook-bridge-matrix-bridge-sms.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2621
+msgid "2020-05-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2623
+msgid "(Compatibility Break / Security Issue) Disabling User Directory search powered by the ma1sd Identity Server"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2627
+msgid "ma1sd current has [a security issue](https://github.com/ma1uta/ma1sd/issues/44), which made it leak information about all users - including users created by bridges, etc."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2629
+msgid "Until the issue gets fixed, we're making User Directory search not go to ma1sd by default. You **need to re-run the playbook and restart services to apply this workaround**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2631
+msgid "*If you insist on restoring the old behavior* (**which has a security issue!**), you *might* use this configuration: `matrix_nginx_proxy_proxy_matrix_user_directory_search_enabled: \"{{ matrix_ma1sd_enabled }}\"`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2634
+msgid "2020-04-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2636
+msgid "Newer IRC bridge (with potential breaking change)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2638
+msgid "This upgrades matrix-appservice-irc from 0.14.1 to 0.16.0.  Upstream made a change to how you define manual mappings.  If you added a `mapping` to your configuration, you will need to update it accoring to the [upstream instructions](https://github.com/matrix-org/matrix-appservice-irc/blob/master/CHANGELOG.md#0150-2020-02-05). If you did not include `mappings` in your configuration for IRC, no change is necessary.  `mappings` is not part of the default configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2647
+msgid "2020-04-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2649
+#: ../../../CHANGELOG.md:2880
+msgid "Slack bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2651
+msgid "Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the playbook now supports bridging to [Slack](https://slack.com) via the [mx-puppet-slack](https://github.com/Sorunome/mx-puppet-slack) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2653
+msgid "See our [Setting up MX Puppet Slack bridging](docs/configuring-playbook-bridge-mx-puppet-slack.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2656
+msgid "2020-04-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2658
+msgid "Skype bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2660
+msgid "Thanks to [Rodrigo Belem](https://github.com/rbelem)'s efforts, the playbook now supports bridging to [Skype](https://www.skype.com) via the [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2662
+msgid "See our [Setting up MX Puppet Skype bridging](docs/configuring-playbook-bridge-mx-puppet-skype.md) documentation page for getting started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2665
+msgid "2020-04-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2667
+msgid "Private Jitsi support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2669
+msgid "The [Jitsi support](#jitsi-support) we had landed a few weeks ago was working well, but it was always open to the whole world."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2671
+msgid "Running such an open instance is not desirable to most people, so [teutat3s](https://github.com/teutat3s) has contributed support for making Jitsi use authentication."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2673
+msgid "To make your Jitsi server more private, see the [configure internal Jitsi authentication and guests mode](docs/configuring-playbook-jitsi.md#optional-configure-internal-jitsi-authentication-and-guests-mode) section in our Jitsi documentation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2676
+msgid "2020-04-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2678
+msgid "(Potential Backward Compatibility Break) ma1sd replaces mxisd"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2680
+msgid "Thanks to [Marcel Partap](https://github.com/eMPee584)'s efforts, the [mxisd](https://github.com/kamax-io/mxisd) identity server, which has been deprecated for a long time, has finally been replaced by [ma1sd](https://github.com/ma1uta/ma1sd), a compatible fork."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2682
+msgid "**If you're using the default playbook configuration**, you don't need to do anything -- your mxisd installation will be replaced with ma1sd and all existing data will be migrated automatically the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2684
+msgid "**If you're doing something more special** (defining custom `matrix_mxisd_*` variables), the playbook will ask you to rename them to `matrix_ma1sd_*`. You're also encouraged to test that ma1sd works well for such a more custom setup."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2687
+msgid "2020-03-29"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2689
+msgid "Archlinux support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2691
+msgid "Thanks to [Christian Lupus](https://github.com/christianlupus)'s efforts, the playbook now supports installing to an [Archlinux](https://www.archlinux.org/) server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2694
+msgid "2020-03-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2696
+msgid "Jitsi support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2698
+msgid "The playbook can now (optionally) install the [Jitsi](https://jitsi.org/) video-conferencing platform and integrate it with [Riot](docs/configuring-playbook-riot-web.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2700
+msgid "See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2703
+msgid "2020-03-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2705
+msgid "Raspberry Pi support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2707
+msgid "Thanks to [Gergely Horváth](https://github.com/hooger)'s effort, the playbook supports installing to a Raspberry Pi server, for at least some of the services."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2709
+msgid "Since most ready-made container images do not support that architecture, we achieve this by building images locally on the device itself. See our [Self-building documentation page](docs/self-building.md) for how to get started."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2712
+msgid "2020-02-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2714
+msgid "Riot-web themes are here"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2716
+msgid "The playbook now makes it easy to install custom riot-web themes."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2718
+msgid "To learn more, take a look at our [riot-web documentation on Themes](docs/configuring-playbook-riot-web.md#themes)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2721
+msgid "2020-02-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2723
+msgid "Customize the server name in Riot's login page"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2725
+msgid "You can now customize the server name string that Riot-web displays in its login page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2727
+msgid "These playbook variables, with these default values, have been added:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2733
+msgid "The login page previously said \"Sign in to your Matrix account on matrix.example.org\" (the homeserver's domain name). It will now say \"Sign in … on example.org\" (the server name) by default, or \"Sign in … on Our Server\" if you set the variable to \"Our Server\"."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2735
+msgid "To support this, the config.json template is changed to use the configuration key `default_server_config` for setting the default HS/IS, and the new configuration key `server_name` is added in there."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2738
+msgid "2020-01-30"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2740
+msgid "Disabling TLSv1.1"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2742
+msgid "To improve security, we've removed TLSv1.1 support from our default matrix-nginx-proxy configuration."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2744
+msgid "If you need to support old clients, you can re-enable it with the following configuration: `matrix_nginx_proxy_ssl_protocols: \"TLSv1.1 TLSv1.2 TLSv1.3\"`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2747
+msgid "2020-01-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2749
+msgid "Postgres collation changes (action required!)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2751
+msgid "By default, we've been using a UTF-8 collation for Postgres. This is known to cause Synapse some troubles (see the [relevant issue](https://github.com/matrix-org/synapse/issues/6722)) on systems that use [glibc](https://www.gnu.org/software/libc/). We run Postgres in an [Alpine Linux](https://alpinelinux.org/) container (which uses [musl](https://www.musl-libc.org/), and not glibc), so our users are likely not affected by the index corruption problem observed by others."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2753
+msgid "Still, we might become affected in the future. In any case, it's imminent that Synapse will complain about databases which do not use a C collation."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2755
+msgid "To avoid future problems, we recommend that you run the following command:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2761
+msgid "It forces a [Postgres database upgrade](docs/maintenance-postgres.md#upgrading-postgresql), which would recreate your Postgres database using the proper (`C`) collation. If you are low on disk space, or run into trouble, refer to the Postgres database upgrade documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2764
+msgid "2020-01-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2766
+msgid "Added support for Appservice Webhooks"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2768
+msgid "Thanks to a contribution from [Björn Marten](https://github.com/tripleawwy) from [netresearch](https://www.netresearch.de/), the playbook can now install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2770
+msgid "Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-playbook-bridge-appservice-webhooks.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2773
+msgid "2020-01-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2775
+msgid "Added support for automatic Double Puppeting for all Mautrix bridges"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2777
+msgid "Double Puppeting can now be easily enabled for all Mautrix bridges supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2779
+msgid "This is possible due to those bridges' integration with [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) - yet another component that this playbook can install for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2781
+msgid "To get started, following the playbook's documentation for the bridge you'd like to configure."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2784
+msgid "2019-12-06"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2786
+msgid "Added support for an alternative method for using another webserver"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2788
+msgid "We have added support for making `matrix-nginx-proxy` not being so invasive, so that it would be easier to [use your own webserver](docs/configuring-playbook-own-webserver.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2790
+msgid "The documentation has been updated with a **Method 2**, which might make \"own webserver\" setup easier in some cases (such as [reverse-proxying using Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/296))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2792
+msgid "**Existing users** are not affected by this and **don't need to change anything**. The defaults are still the same (`matrix-nginx-proxy` obtaining SSL certificates and doing everything for you automatically)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2795
+msgid "2019-11-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2797
+msgid "Tightened security around room directory publishing"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2799
+msgid "As per this [advisory blog post](https://matrix.org/blog/2019/11/09/avoiding-unwelcome-visitors-on-private-matrix-servers), we've decided to change the default publishing rules for the Matrix room directory."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2801
+msgid "Our general goal is to favor privacy and security when running personal (family & friends) and corporate homeservers. Both of these likely benefit from having a more secure default of **not showing the room directory without authentication** and **not publishing the room directory over federation**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2803
+msgid "As with anything else, these new defaults can be overriden by changing the `matrix_synapse_allow_public_rooms_without_auth` and `matrix_synapse_allow_public_rooms_over_federation` variables, respectively."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2806
+msgid "2019-10-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2808
+msgid "Improved Postgres upgrading/importing"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2810
+msgid "Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) and [importing](docs/importing-postgres.md) have been improved to add support for multiple databases and roles."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2812
+msgid "Previously, the playbook would only take care of the `homeserver` database and `synapse` user. We now back up and restore all databases and users on the Postgres server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2814
+msgid "For now, the playbook only uses that one database (`homeserver`) and that one single user (`synapse`), so it's all the same. However, in the future, additional components besides Synapse may also make use the Postgres database server. One such example is the [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge, which strongly encourages use of Postgres in its v1.0 release. We are yet to upgrade to it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2816
+msgid "Additionally, Postgres [upgrading](docs/maintenance-postgres.md#upgrading-postgresql) now uses gzipped dump files by default, to minimize disk space usage."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2819
+msgid "2019-10-04"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2821
+msgid "Postgres 12 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2823
+msgid "The playbook now installs [Postgres 12](https://www.postgresql.org/about/news/1976/) by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2825
+msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x, 10.x or 11.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2828
+msgid "2019-10-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2830
+msgid "Synapse 1.4.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2832
+msgid "Synapse 1.4.0 [is out](https://matrix.org/blog/2019/10/03/synapse-1-4-0-released) with lots of changes related to privacy."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2834
+msgid "Its new defaults (which we adopt as well) mean that certain old data will automatically get purged after a certain number of days. 1.4.0 automatically garbage collects redacted messages (defaults to 7 days) and removes unused IP and user agent information stored in the user_ips table (defaults to 30 days). If you'd like to preserve this data, we encourage you to look at the `redaction_retention_period` and `user_ips_max_age` options (controllable by the `matrix_synapse_redaction_retention_period` and `matrix_synapse_user_ips_max_age` playbook variables, respectively) before doing the upgrade. If you'd like to keep data indefinitely, set these variables to `null` (e.g. `matrix_synapse_redaction_retention_period: ~`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2836
+msgid "From now on the `trusted_key_servers` setting for Synapse is configurable. It still defaults to `matrix.org` just like it always has, but in a more explicit way now. If you'd like to use another trusted key server, adjust the `matrix_synapse_trusted_key_servers` playbook variable."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2838
+msgid "Synapse 1.4.0 also changes lots of things related to identity server integration. Because Synapse will now by default be responsible for validating email addresses for user accounts, running without an identity server looks more feasible. We still [have concerns](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/275/files#r331104117) over disabling the identity server by default, so for now it remains enabled."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2841
+msgid "2019-09-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2843
+msgid "Synapse Simple Antispam support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2845
+msgid "There have been lots of invite-spam attacks lately and [Travis](https://github.com/t2bot) has created a Synapse module ([synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam)) to let people protect themselves."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2847
+msgid "From now on, you can easily install and configure this spam checker module through the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2849
+msgid "Learn more in [Setting up Synapse Simple Antispam](docs/configuring-playbook-synapse-simple-antispam.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2852
+msgid "2019-08-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2854
+msgid "Extensible Riot-web configuration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2856
+msgid "Similarly to [Extensible Synapse configuration](#extensible-synapse-configuration) (below), Riot-web configuration is also extensible now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2858
+msgid "From now on, you can extend/override Riot-web's configuration by making use of the `matrix_riot_web_configuration_extension_json` variable. This should be enough for most customization needs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2860
+msgid "If you need even more power, you can now also take full control and override `matrix_riot_web_configuration_default` (or `matrix_riot_web_configuration`) directly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2862
+msgid "Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-web.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2865
+msgid "2019-08-22"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2867
+msgid "Extensible Synapse configuration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2869
+msgid "Previously, we had to create custom Ansible variables for each and every Synapse setting. This lead to too much effort (and configuration ugliness) to all of Synapse's settings, so naturally, not all features of Synapse could be controlled through the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2871
+msgid "From now on, you can extend/override the Synapse server's configuration by making use of the `matrix_synapse_configuration_extension_yaml` variable. This should be enough for most customization needs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2873
+msgid "If you need even more power, you can now also take full control and override `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`) directly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2875
+msgid "Learn more here in [Configuring Synapse](docs/configuring-playbook-synapse.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2878
+msgid "2019-08-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2882
+msgid "Thanks to the [great work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/205) of [kingoftheconnors](https://github.com/kingoftheconnors) and [Stuart Mumford (Cadair)](https://github.com/Cadair), the playbook now supports bridging to [Slack](https://slack.com) via the [appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2884
+msgid "Additional details are available in [Setting up Appservice Slack bridging](docs/configuring-playbook-bridge-appservice-slack.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2886
+msgid "Google Hangouts bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2888
+msgid "Thanks to the [great work](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/251) of [Eduardo Beltrame (Munfred)](https://github.com/Munfred) and [Robbie D (microchipster)](https://github.com/microchipster), the playbook now supports bridging to [Google Hangouts](https://hangouts.google.com/) via the [mautrix-hangouts](https://mau.dev/tulir/mautrix-hangouts) bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2890
+msgid "Additional details are available in [Setting up Mautrix Hangouts bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2893
+msgid "2019-08-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2895
+msgid "Email2Matrix support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2897
+msgid "Support for [Email2Matrix](https://github.com/devture/email2matrix) has been added."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2899
+msgid "It's an optional feature that you can enable via the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2901
+msgid "To learn more, see the [playbook's documentation on Email2Matrix](./docs/configuring-playbook-email2matrix.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2904
+msgid "2019-08-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2906
+msgid "Synapse logging level has been reduced to WARNING"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2908
+msgid "After [some discussion in our support room](https://matrix.to/#/!PukFFdIcHgtaaHZflT:devture.com/$156476852524179TBeKy:matrix.org?via=devture.com&via=matrix.org&via=librem.one), we've decided to change the default logging level for Synapse from `INFO` to `WARNING`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2910
+msgid "This greatly reduces the number of log messages that are being logged, leading to:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2912
+msgid "much less disk space dedicated to Synapse and thus, logs kept for longer"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2913
+msgid "easier to find some important `WARNING`, `ERROR` and `CRITICAL` messages, as they're not longer buried in thousands of non-important `INFO` messages"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2915
+msgid "If you'd like to track down an issue, you [can always increase the logging level as described here](./docs/maintenance-and-troubleshooting.md#increasing-synapse-logging)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2918
+msgid "2019-07-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2920
+msgid "Synapse Maintenance docs and synapse-janitor support are available"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2922
+msgid "The playbook can now help you with Synapse's maintenance."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2924
+msgid "There's a new documentation page about [Synapse maintenance](./docs/maintenance-synapse.md) and another section on [Postgres vacuuming](./docs/maintenance-postgres.md#vacuuming-postgresql)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2926
+msgid "Among other things, if your Postgres database has grown significantly over time, you may wish to [ask the playbook to purge unused data with synapse-janitor](./docs/maintenance-synapse.md#purging-unused-data-with-synapse-janitor) for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2928
+msgid "(BC Break) Rename run control variables"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2930
+msgid "Some internal playbook control variables have been renamed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2932
+msgid "This change **only affects people who run this playbook's roles from another playbook**. If you're using this playbook as-is, you're not affected and don't need to do anything."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2934
+msgid "The following variables have been renamed:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2936
+msgid "from `run_import_postgres` to `run_postgres_import`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2937
+msgid "from `run_import_sqlite_db` to `run_postgres_import_sqlite_db`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2938
+msgid "from `run_upgrade_postgres` to `run_postgres_upgrade`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2939
+msgid "from `run_import_media_store` to `run_synapse_import_media_store`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2940
+msgid "from `run_register_user` to `run_synapse_register_user`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2941
+msgid "from `run_update_user_password` to `run_synapse_update_user_password`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2944
+msgid "2019-07-04"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2946
+msgid "Synapse no longer logs to text files"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2948
+msgid "Following what the official Synapse Docker image is doing ([#5565](https://github.com/matrix-org/synapse/pull/5565)) and what we've been doing for mostly everything installed by this playbook, **Synapse no longer logs to text files** (`/matrix/synapse/run/homeserver.log*`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2950
+msgid "From now on, Synapse would only log to console, which goes to systemd's journald. To see Synapse's logs, execute: `journalctl -fu matrix-synapse`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2952
+msgid "Because of this, the following variables have become obsolete and were removed:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2954
+msgid "`matrix_synapse_max_log_file_size_mb`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2955
+msgid "`matrix_synapse_max_log_files_count`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2957
+msgid "To prevent confusion, it'd be better if you delete all old files manually after you've upgraded (`rm -f /matrix/synapse/run/homeserver.log*`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2959
+msgid "Because Synapse is incredibly chatty when it comes to logging (here's [one such issue](https://github.com/matrix-org/synapse/issues/4751) describing the problem), if you're running an ancient distribution (like CentOS 7.0), be advised that systemd's journald default logging restrictions may not be high enough to capture all log messages generated by Synapse. This is especially true if you've got a busy (Synapse) server. We advise that you manually add `RateLimitInterval=0` and `RateLimitBurst=0` under `[Storage]` in the `/etc/systemd/journald.conf` file, followed by restarting the logging service (`systemctl restart systemd-journald`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2962
+msgid "2019-06-27"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2964
+msgid "(BC Break) Discord bridge configuration is now entirely managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2966
+msgid "Until now, the `config.yaml` file for the [Discord bridge](docs/configuring-playbook-bridge-appservice-discord.md) was managed by the playbook, but the `registration.yaml` file was not."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2968
+msgid "From now on, the playbook will keep both configuration files sync for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2970
+msgid "This means that if you were making manual changes to the `/matrix/appservice-discord/discord-registration.yaml` configuration file, those would be lost the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2972
+msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-discord/config`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2974
+msgid "Likewise, data is now also stored in a subdirectory (`/matrix/appservice-discord/data`). When you run the playbook with an existing database file (`/matrix/appservice-discord/discord.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2976
+msgid "The main directory (`/matrix/appservice-discord`) may contain some leftover files (`user-store.db`, `room-store.db`, `config.yaml`, `discord-registration.yaml`, `invite_link`). These are no longer necessary and can be deleted manually."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2978
+msgid "We're now following the default sample configuration for the Discord bridge. If you need to override some values, define them in `matrix_appservice_discord_configuration_extension_yaml`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2981
+msgid "2019-06-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2983
+msgid "(BC Break) WhatsApp bridge configuration is now entirely managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:2985
+msgid "Until now, configuration files for the [WhatsApp bridge](docs/configuring-playbook-bridge-mautrix-whatsapp.md) were created by the playbook initially, but never modified later on."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2987
+#: ../../../CHANGELOG.md:3004
+#: ../../../CHANGELOG.md:3023
+#: ../../../CHANGELOG.md:3062
+msgid "From now on, the playbook will keep the configuration in sync for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2989
+msgid "This means that if you were making manual changes to the `/matrix/mautrix-whatsapp/config.yaml` or `/matrix/mautrix-whatsapp/registration.yaml` configuration files, those would be lost the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2991
+msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-whatsapp/config`), so your old configuration remains in the base directory (`/matrix/mautrix-whatsapp`). You need to migrate any manual changes over to the new `matrix_mautrix_whatsapp_configuration_extension_yaml` variable, so that the playbook would apply them for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2993
+msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-whatsapp/data`). When you run the playbook with an existing database file (`/matrix/mautrix-whatsapp/mautrix-whatsapp.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2995
+msgid "We're now following the default configuration for the WhatsApp bridge."
+msgstr ""
+
+#: ../../../CHANGELOG.md:2998
+msgid "2019-06-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3000
+msgid "(BC Break) IRC bridge configuration is now entirely managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3002
+msgid "Until now, configuration files for the [IRC bridge](docs/configuring-playbook-bridge-appservice-irc.md) were created by the playbook initially, but never modified later on."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3006
+msgid "This means that if you were making manual changes to the `/matrix/appservice-irc/config.yaml` or `/matrix/appservice-irc/registration.yaml` configuration files, those would be lost the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3008
+msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-irc/config`), so your old configuration remains in the base directory (`/matrix/appservice-irc`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3010
+msgid "Previously, we asked people to configure bridged IRC servers by extending the bridge configuration (`matrix_appservice_irc_configuration_extension_yaml`). While this is still possible and will continue working forever, **we now recommend defining IRC servers in the easier to use `matrix_appservice_irc_ircService_servers` variable**. See [our IRC bridge documentation page](docs/configuring-playbook-bridge-appservice-irc.md) for an example."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3012
+msgid "If you decide to continue using `matrix_appservice_irc_configuration_extension_yaml`, you might be interested to know that `ircService.databaseUri` and a few other keys now have default values in the base configuration (`matrix_appservice_irc_configuration_yaml`). You may wish to stop redefining those keys, unless you really intend to override them. You most likely only need to override `ircService.servers`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3014
+msgid "Bridge data (`passkey.pem` and database files) is now also stored in a subdirectory (`/matrix/appservice-irc/data`). When you run the playbook with an existing `/matrix/appservice-irc/passkey.pem` file, the playbook will stop the bridge and relocate the passkey and database files (`rooms.db` and `users.db`) to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3017
+msgid "2019-06-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3019
+msgid "(BC Break) Telegram bridge configuration is now entirely managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3021
+msgid "Until now, configuration files for the [Telegram bridge](docs/configuring-playbook-bridge-mautrix-telegram.md) were created by the playbook initially, but never modified later on."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3025
+msgid "This means that if you were making manual changes to the `/matrix/mautrix-telegram/config.yaml` or `/matrix/mautrix-telegram/registration.yaml` configuration files, those would be lost the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3027
+msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-telegram/config`), so your old configuration remains in the base directory (`/matrix/mautrix-telegram`). You need to migrate any manual changes over to the new `matrix_mautrix_telegram_configuration_extension_yaml` variable, so that the playbook would apply them for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3029
+msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-telegram/data`). When you run the playbook with an existing database file (`/matrix/mautrix-telegram/mautrix-telegram.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3031
+msgid "Also, we're now following the default configuration for the Telegram bridge, so some default configuration values are different:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3033
+msgid "`edits_as_replies` (used to be `false`, now `true`) - previously replies were not sent over to Matrix at all; ow they are sent over as a reply to the original message"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3034
+msgid "`inline_images` (used to be `true`, now `false`) - this has to do with captioned images. Inline-image (included caption) are said to exhibit troubles on Riot iOS. When `false`, the caption arrives on the Matrix side as a separate message."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3035
+msgid "`authless_portals` (used to be `false`, now `true`) - creating portals from the Telegram side is now possible"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3036
+msgid "`whitelist_group_admins` (used to be `false`, now `true`) - allows Telegram group admins to use the bot commands"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3038
+msgid "If the new values are not to your liking, use `matrix_mautrix_telegram_configuration_extension_yaml` to specify an override (refer to `matrix_mautrix_telegram_configuration_yaml` to figure out which variable goes where)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3041
+msgid "2019-06-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3043
+msgid "Synapse v1.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3045
+msgid "With [Synapse v1.0 now available](https://matrix.org/blog/2019/06/11/introducing-matrix-1-0-and-the-matrix-org-foundation) and most people being on at least Synapse v0.99, it's time to remove the `_matrix._tcp` DNS SRV record that we've been keeping for compatibility with old Synapse versions (<= 0.34)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3047
+msgid "According to the [Server Discovery specification](https://matrix.org/docs/spec/server_server/r0.1.2.html#server-discovery), it's no harm to keep the DNS SRV record. But since it's not necessary for federating with the larger Matrix network anymore, you should be safe to get rid of it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3049
+msgid "**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` DNS SRV records. The latter, **must not** be removed."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3051
+msgid "For completeness, we must say that using a `_matrix._tcp` [SRV record for Server Delegation](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced) is still valid and useful for certain deployments. It's just that our guide recommends the [`/.well-known/matrix/server` Server Delegation method](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), due to its easier implementation when using this playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3053
+msgid "Besides this optional/non-urgent DNS change, assuming you're already on Synapse v0.99, upgrading to Synapse v1.0 should be as simple as [re-running the playbook](docs/maintenance-upgrading-services.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3056
+msgid "2019-06-07"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3058
+msgid "(BC Break) Facebook bridge configuration is now entirely managed by the playbook"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3060
+msgid "Until now, configuration files for the [Facebook bridge](docs/configuring-playbook-bridge-mautrix-facebook.md) were created by the playbook initially, but never modified later on."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3064
+msgid "This means that if you were making manual changes to the `/matrix/mautrix-facebook/config.yaml` or `/matrix/mautrix-facebook/registration.yaml` configuration files, those would be lost the next time you run the playbook."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3066
+msgid "The bridge now stores configuration in a subdirectory (`/matrix/mautrix-facebook/config`), so your old configuration remains in the base directory (`/matrix/mautrix-facebook`). You need to migrate any manual changes over to the new `matrix_mautrix_facebook_configuration_extension_yaml` variable, so that the playbook would apply them for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3068
+msgid "Likewise, data is now also stored in a subdirectory (`/matrix/mautrix-facebook/data`). When you run the playbook with an existing database file (`/matrix/mautrix-facebook/mautrix-facebook.db`), the playbook will stop the bridge and relocate the database file to the `./data` directory. There's no data-loss involved. You'll need to restart the bridge manually though (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3071
+msgid "2019-05-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3073
+msgid "Support for exposing container ports publicly (not just to the host)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3075
+msgid "Until now, various roles supported a `matrix_*_expose_port` variable, which would expose their container's port to the host. This was mostly useful for reverse-proxying manually (in case `matrix-nginx-proxy` was disabled). It could also be used for installing some playbook services (e.g. bridges, etc.) and wiring them to a separate (manual) Matrix setup."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3077
+msgid "`matrix_*_expose_port` variables were not granular enough - sometimes they would expose one port, other times multiple. They also didn't provide control over **where** to expose (to which port number and to which network interface), because they would usually hardcode something like `127.0.0.1:8080`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3079
+msgid "All such variables have been superseded by a better (more flexible) way to do it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3081
+msgid "**Most** people (including those not using `matrix-nginx-proxy`), **don't need** to bother with this."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3083
+msgid "Porting examples follow for people having more customized setups:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3085
+msgid "**from** `matrix_synapse_container_expose_client_api_port: true` **to** `matrix_synapse_container_client_api_host_bind_port: '127.0.0.1:8008'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3087
+msgid "**from** `matrix_synapse_container_expose_federation_api_port: true` **to** `matrix_synapse_container_federation_api_plain_host_bind_port: '127.0.0.1:8048'` and possibly `matrix_synapse_container_federation_api_tls_host_bind_port: '8448'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3089
+msgid "**from** `matrix_synapse_container_expose_metrics_port: true` **to** `matrix_synapse_container_metrics_api_host_bind_port: '127.0.0.1:9100'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3091
+msgid "**from** `matrix_riot_web_container_expose_port: true` **to** `matrix_riot_web_container_http_host_bind_port: '127.0.0.1:8765'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3093
+msgid "**from** `matrix_mxisd_container_expose_port: true` **to** `matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3095
+msgid "**from** `matrix_dimension_container_expose_port: true` **to** `matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3097
+msgid "**from** `matrix_corporal_container_expose_ports: true` **to** `matrix_corporal_container_http_gateway_host_bind_port: '127.0.0.1:41080'` and possibly `matrix_corporal_container_http_api_host_bind_port: '127.0.0.1:41081'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3099
+msgid "**from** `matrix_appservice_irc_container_expose_client_server_api_port: true` **to** `matrix_appservice_irc_container_http_host_bind_port: '127.0.0.1:9999'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3101
+msgid "**from** `matrix_appservice_discord_container_expose_client_server_api_port: true` **to** `matrix_appservice_discord_container_http_host_bind_port: '127.0.0.1:9005'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3103
+msgid "As always, if you forget to remove usage of some outdated variable, the playbook will warn you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3106
+msgid "2019-05-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3108
+msgid "(BC Break) Ansible 2.8 compatibility"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3110
+msgid "Thanks to [@danbob](https://github.com/danbob), the playbook now [supports the new Ansible 2.8](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/187)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3112
+msgid "A manual change is required to the `inventory/hosts` file, changing the group name from `matrix-servers` to `matrix_servers` (dash to underscore)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3114
+msgid "To avoid doing it manually, run this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3115
+msgid "Linux: `sed -i 's/matrix-servers/matrix_servers/g' inventory/hosts`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3116
+msgid "Mac: `sed -i '' 's/matrix-servers/matrix_servers/g' inventory/hosts`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3119
+msgid "2019-05-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3121
+msgid "Synapse no longer required"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3123
+msgid "The playbook no longer insists on installing [Synapse](https://github.com/element-hq/synapse) via the `matrix-synapse` role."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3125
+msgid "If you would prefer to install Synapse another way and just use the playbook to install other services, it should be possible (`matrix_synapse_enabled: false`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3127
+msgid "Note that it won't necessarily be the best experience, since the playbook wires things to Synapse by default. If you're using your own Synapse instance (especially one not running in a container), you may have to override many variables to point them to the correct place."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3129
+msgid "Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3131
+msgid "Bridges are now separate from the Synapse role"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3133
+msgid "Bridges are no longer part of the `matrix-synapse` role. Each bridge now lives in its own separate role (`roles/custom/matrix-bridge-*`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3135
+msgid "These bridge roles are independent of the `matrix-synapse` role, so it should be possible to use them with a Synapse instance installed another way (not through the playbook)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3137
+msgid "Renaming inconsistently-named Synapse variables"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3139
+msgid "For better consistency, the following variables have been renamed:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3141
+msgid "`matrix_enable_room_list_search` was renamed to `matrix_synapse_enable_room_list_search`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3142
+msgid "`matrix_alias_creation_rules` was renamed to `matrix_synapse_alias_creation_rules`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3143
+msgid "`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was renamed to `matrix_synapse_room_list_publication_rules`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3146
+msgid "2019-05-09"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3148
+msgid "Besides a myriad of bug fixes and minor improvements, here are the more notable (bigger) features we can announce today."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3150
+msgid "Mautrix Facebook/Messenger bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3152
+msgid "The playbook now supports bridging with [Facebook](https://www.facebook.com/) by installing the [mautrix-facebook](https://github.com/tulir/mautrix-facebook) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3154
+msgid "Additional details are available in [Setting up Mautrix Facebook bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3156
+msgid "mxisd Registration feature integration"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3158
+msgid "The playbook can now help you integrate with mxisd's [Registration](https://github.com/kamax-matrix/mxisd/blob/master/docs/features/registration.md) feature."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3160
+msgid "Learn more in [mxisd-controlled Registration](docs/configuring-playbook-mxisd.md#mxisd-controlled-registration)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3163
+msgid "2019-04-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3165
+msgid "Caddy webserver examples"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3167
+msgid "If you prefer using the [Caddy](https://caddyserver.com/) webserver instead of our own integrated nginx, we now have examples for it in the [`examples/caddy`](examples/caddy) directory"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3169
+msgid "2019-04-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3171
+msgid "Goofys support for other S3-compatible object stores"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3173
+msgid "Until now, you could optionally host Synapse's media repository on Amazon S3, but we now also support [using other S3-compatible object stores](docs/configuring-playbook-s3.md),"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3176
+msgid "2019-04-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3178
+msgid "Ansible >= 2.5 is required"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3180
+msgid "Due to recent playbook improvements and the fact that the world keeps turning, we're bumping the [version requirement for Ansible](docs/ansible.md#supported-ansible-versions) (2.4 -> 2.5)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3182
+msgid "We've also started building our own Docker image of Ansible ([devture/ansible](https://hub.docker.com/r/devture/ansible/)), which is useful for people who can't upgrade their local Ansible installation (see [Using Ansible via Docker](docs/ansible.md#using-ansible-via-docker))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3185
+msgid "2019-03-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3187
+msgid "TLS support for Coturn"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3189
+msgid "We've added TLS support to the Coturn TURN server installed by the playbook by default. The certificates from the Matrix domain will be used for the Coturn server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3191
+msgid "This feature is enabled by default for new installations. To make use of TLS support for your existing Matrix server's Coturn, make sure to rebuild both Coturn and Synapse:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3197
+msgid "People who have an extra firewall (besides the iptables firewall, which Docker manages automatically), will need to open these additional firewall ports: `5349/tcp` (TURN over TCP) and `5349/udp` (TURN over UDP)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3199
+msgid "People who build their own custom playbook from our roles should be aware that:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3201
+msgid "the `matrix-coturn` role and actually starting Coturn (e.g. `--tags=start`), requires that certificates are already put in place. For this reason, it's usually a good idea to have the `matrix-coturn` role execute after `matrix-nginx-proxy` (which retrieves the certificates)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3203
+msgid "there are a few variables that can help you enable TLS support for Coturn. See the `matrix-coturn` section in [group_vars/matrix-servers](./group_vars/matrix-servers)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3206
+msgid "2019-03-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3208
+msgid "matrix-nginx-proxy support for serving the base domain"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3210
+msgid "If you don't have a dedicated server for your base domain and want to set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), the playbook has got you covered now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3212
+msgid "It's now possible for the playbook to obtain an SSL certificate and serve the necessary files for Matrix Server Delegation on your base domain. Take a look at the new [Serving the base domain](docs/configuring-playbook-base-domain-serving.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3214
+msgid "(BC break) matrix-nginx-proxy data variable renamed"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3216
+msgid "`matrix_nginx_proxy_data_path` was renamed to `matrix_nginx_proxy_base_path`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3218
+msgid "There's a new `matrix_nginx_proxy_data_path` variable, which has a different use-purpose now (it's a subdirectory of `matrix_nginx_proxy_base_path` and is meant for storing various data files)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3221
+msgid "2019-03-10"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3223
+msgid "Dimension integration manager support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3225
+msgid "Thanks to [NullIsNot0](https://github.com/NullIsNot0), the playbook can now (optionally) install the [Dimension](https://dimension.t2bot.io/) integration manager. To learn more, see the [Setting up Dimension](docs/configuring-playbook-dimension.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3228
+msgid "2019-03-07"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3230
+msgid "Ability to customize mxisd's email templates"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3232
+msgid "Thanks to [Sylvia van Os](https://github.com/TheLastProject), mxisd's email templates can now be customized easily. To learn more, see the [Customizing email templates](docs/configuring-playbook-mxisd.md#customizing-email-templates) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3235
+msgid "2019-03-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3237
+msgid "Discord bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3239
+msgid "[@Lionstiger](https://github.com/Lionstiger) has done some great work adding Discord bridging support via [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord). To learn more, see the [Setting up Appservice Discord bridging](docs/configuring-playbook-bridge-appservice-discord.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3242
+msgid "2019-02-19"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3244
+msgid "Renaming variables"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3246
+#: ../../../CHANGELOG.md:3563
+#: ../../../CHANGELOG.md:3648
+#: ../../../CHANGELOG.md:3768
+msgid "The following playbook variables were renamed:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3248
+msgid "from `host_specific_hostname_identity` to `matrix_domain`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3249
+msgid "from `hostname_identity` to `matrix_domain`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3250
+msgid "from `hostname_matrix` to `matrix_server_fqn_matrix`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3251
+msgid "from `hostname_riot` to `matrix_server_fqn_riot`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3252
+msgid "from `host_specific_matrix_ssl_lets_encrypt_support_email` to `matrix_ssl_lets_encrypt_support_email`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3254
+msgid "Doing that, we've simplified things, made names less confusing (hopefully) and moved all variable names under the `matrix_` prefix."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3257
+msgid "2019-02-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3259
+msgid "Riot v1.0.1 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3261
+msgid "You can now use the brand new and redesigned Riot."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3263
+msgid "The new version no longer has a homepage by default, so we've also removed the custom homepage that we've been installing."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3265
+msgid "However, we still provide you with hooks to install your own `home.html` file by specifying the `matrix_riot_web_embedded_pages_home_path` variable (used to be called `matrix_riot_web_homepage_template` before)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3268
+msgid "2019-02-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3270
+msgid "Synapse v0.99.1"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3272
+msgid "As we're moving toward Synapse v1.0, things are beginning to stabilize. Upgrading from v0.99.0 to v0.99.1 should be painless."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3274
+msgid "If you've been overriding the default configuration so that you can terminate TLS at the Synapse side (`matrix_synapse_no_tls: false`), you'll now have to replace this custom configuration with `matrix_synapse_tls_federation_listener_enabled: true`. The `matrix_synapse_no_tls` variable is no more."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3277
+msgid "2019-02-06"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3279
+msgid "Synapse v0.99 support and preparation for Synapse v1.0"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3281
+msgid "Matrix is undergoing a lot of changes as it matures towards Synapse v1.0. The first step is the Synapse v0.99 transitional release, which this playbook now supports."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3283
+msgid "If you've been using this playbook successfully until now, you'd be aware that we've been doing [Server Delegation](docs/howto-server-delegation.md) using a `_matrix._tcp` DNS SRV record (as per [Configuring DNS](docs/configuring-dns.md))."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3285
+msgid "Due to changes related to certificate file requirements that will affect us at Synapse v1.0, we'll have to stop using a **`_matrix._tcp` DNS SRV record in the future** (when Synapse goes to v1.0 - around 5th of March 2019). We **still need to keep the SRV record for now**, for backward compatibility with older Synapse versions (lower than v0.99)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3287
+msgid "**What you need to do now** is make use of this transitional Synapse v0.99 release to **prepare your federation settings for the future**. You have 2 choices to prepare yourself for compatibility with the future Synapse v1.0:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3289
+msgid "(recommended) set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), unless you are affected by the [Downsides of well-known-based Server Delegation](docs/howto-server-delegation.md#downsides-of-well-known-based-server-delegation). If you had previously set up the well-known `client` file, depending on how you've done it, it may be that there is nothing new required of you (besides [upgrading](docs/maintenance-upgrading-services.md)). After upgrading, you can [run a self-check](docs/maintenance-checking-services.md), which will tell you if you need to do anything extra with regard to setting up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file). After some time, when most people have upgraded to Synapse v0.99 and older releases have disappeared, be prepared to drop your `_matrix._tcp` SRV record."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3291
+msgid "(more advanced) if the [Downsides of well-known-based Server Delegation](docs/howto-server-delegation.md#downsides-of-well-known-based-server-delegation) are not to your liking, **as an alternative**, you can set up [Server Delegation via a DNS SRV record](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced). In such a case, you get to keep using your existing `_matrix._tcp` DNS SRV record forever and need to NOT set up a `/.well-known/matrix/server` file. Don't forget that you need to do certificate changes though. Follow the guide at [Server Delegation via a DNS SRV record](docs/howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3294
+msgid "2019-02-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3296
+msgid "TLS v1.3 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3298
+msgid "Now that the [nginx Docker image](https://hub.docker.com/_/nginx) has [added support for TLS v1.3](https://github.com/nginxinc/docker-nginx/issues/190), we have enabled that protocol by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3300
+msgid "When using:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3302
+msgid "the **integrated nginx server**: TLS v1.3 support might not kick in immediately, because the nginx version hasn't been bumped and you may have an older build of the nginx Docker image (currently `nginx:1.15.8-alpine`). Typically, we do not re-pull images that you already have. When the nginx version gets bumped in the future, everyone will get the update. Until then, you could manually force-pull the rebuilt Docker image by running this on the server: `docker pull nginx:1.15.8-alpine`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3304
+msgid "**your own external nginx server**: if your external nginx server is too old, the new configuration we generate for you in `/matrix/nginx-proxy/conf.d/` might not work anymore, because it mentions `TLSv1.3` and your nginx version might not support that. You can adjust the SSL protocol list by overriding the `matrix_nginx_proxy_ssl_protocols` variable. Learn more in the documentation page for [Using your own webserver, instead of this playbook's nginx proxy](docs/configuring-playbook-own-webserver.md)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3306
+msgid "**another web server**: you don't need to do anything to accommodate this change"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3309
+msgid "2019-01-31"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3311
+msgid "IRC bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3313
+msgid "[Devon Maloney (@Plailect)](https://github.com/Plailect) has done some great work bringing IRC bridging support via [matrix-appservice-irc](https://github.com/TeDomum/matrix-appservice-irc). To learn more, see the [Setting up Appservice IRC bridging](docs/configuring-playbook-bridge-appservice-irc.md) documentation page."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3316
+msgid "2019-01-29"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3318
+msgid "Running container processes as non-root, without capabilities and read-only"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3320
+msgid "To improve security, this playbook no longer starts container processes as the `root` user. Most containers were dropping privileges anyway, but we were trusting them with `root` privileges until they would do that. Not anymore -- container processes now start as a non-root user (usually `matrix`) from the get-go."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3322
+msgid "For additional security, various capabilities are also dropped (see [why it's important](https://github.com/projectatomic/atomic-site/issues/203)) for all containers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3324
+msgid "Additionally, most containers now use a read-only filesystem (see [why it's important](https://www.projectatomic.io/blog/2015/12/making-docker-images-write-only-in-production/)). Containers are given write access only to the directories they need to write to."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3326
+msgid "A minor breaking change is the `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size` variable having being renamed to `matrix_nginx_proxy_proxy_matrix_client_api_client_max_body_size_mb` (note the `_mb` suffix). The new variable expects a number value (e.g. `25M` -> `25`). If you weren't customizing this variable, this wouldn't affect you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3328
+msgid "matrix-mailer is now based on Exim, not Postfix"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3330
+msgid "While we would have preferred to stay with [Postfix](http://www.postfix.org/), we found out that it cannot run as a non-root user. We've had to replace it with [Exim](https://www.exim.org/) (via the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3332
+msgid "The internal `matrix-mailer` service (running in a container) now listens on port `8025` (used to be `587` before). The playbook will update your Synapse and mxisd email settings to match (`matrix-mailer:587` -> `matrix-mailer:8025`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3334
+msgid "Using the [devture/exim-relay](https://hub.docker.com/r/devture/exim-relay) container image instead of [panubo/postfix](https://hub.docker.com/r/panubo/postfix/) also gives us a nice disk usage reduction (~200MB -> 8MB)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3337
+msgid "2019-01-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3339
+msgid "(BC Break) Making the playbook's roles more independent of one another"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3341
+msgid "The following change **affects people running a more non-standard setup** - external Postgres or using our roles in their own other playbook. **Most users don't need to do anything**, besides becoming aware of the new glue variables file [`group_vars/matrix-servers`](group_vars/matrix-servers)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3344
+msgid "Because people like using the playbook's components independently (outside of this playbook) and because it's much better for maintainability, we've continued working on separating them. Still, we'd like to offer a turnkey solution for running a fully-featured Matrix server, so this playbook remains important for wiring up the various components."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3346
+msgid "With the new changes, **all roles are now only dependent on the minimal `matrix-base` role**. They are no longer dependent among themselves."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3348
+msgid "In addition, the following components can now be completely disabled (for those who want/need to):"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3349
+msgid "`matrix-coturn` by using `matrix_coturn_enabled: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3350
+msgid "`matrix-mailer` by using `matrix_mailer_enabled: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3351
+msgid "`matrix-postgres` by using `matrix_postgres_enabled: false`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3353
+msgid "The following changes had to be done:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3355
+msgid "glue variables had to be introduced to the playbook, so it can wire together the various components. Those glue vars are stored in the [`group_vars/matrix-servers`](group_vars/matrix-servers) file. When overriding variables for a given component (role), you need to be aware of both the role defaults (`role/ROLE/defaults/main.yml`) and the role's corresponding section in the [`group_vars/matrix-servers`](group_vars/matrix-servers) file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3357
+msgid "`matrix_postgres_use_external` has been superceeded by the more consistently named `matrix_postgres_enabled` variable and a few other `matrix_synapse_database_` variables. See the [Using an external PostgreSQL server (optional)](docs/configuring-playbook-external-postgres.md) documentation page for an up-to-date replacement."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3359
+msgid "Postgres tools (`matrix-postgres-cli` and `matrix-make-user-admin`) are no longer installed if you're not enabling the `matrix-postgres` role (`matrix_postgres_enabled: false`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3361
+msgid "roles, being more independent now, are more minimal and do not do so much magic for you. People that are building their own playbook using our roles will definitely need to take a look at the [`group_vars/matrix-servers`](group_vars/matrix-servers) file and adapt their playbooks with the same (or similar) wiring logic."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3364
+msgid "2019-01-16"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3366
+msgid "Splitting the playbook into multiple roles"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3368
+msgid "For better maintainability, the playbook logic (which all used to reside in a single `matrix-server` role) has been split out into a number of different roles: `matrix-synapse`, `matrix-postgres`, `matrix-riot-web`, `matrix-mxisd`, etc. (see the `roles/` directory)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3371
+msgid "To keep the filesystem more consistent with this separation, the **Postgres data had to be relocated**."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3373
+msgid "The default value of `matrix_postgres_data_path` was changed from `/matrix/postgres` to `/matrix/postgres/data`. The `/matrix/postgres` directory is what we consider a base path now (new variable `matrix_postgres_base_path`). **Your Postgres data files will automatically be relocated by the playbook** (`/matrix/postgres/*` -> `/matrix/postgres/data/`) when you run with `--tags=setup-all` (or `--tags=setup-postgres`). While this shouldn't cause data-loss, **it's better if you do a Postgres backup just in case**. You'd need to restart all services after this migration (`--tags=start`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3376
+msgid "2019-01-11"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3378
+msgid "(BC Break) mxisd configuration changes"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3380
+msgid "To be more flexible and to support the upcoming [mxisd](https://github.com/kamax-io/mxisd) 1.3.0 (when it gets released), we've had to redo how mxisd gets configured."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3383
+msgid "The following variables are no longer supported by this playbook:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3385
+msgid "`matrix_mxisd_ldap_enabled`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3386
+msgid "`matrix_mxisd_ldap_connection_host`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3387
+msgid "`matrix_mxisd_ldap_connection_tls`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3388
+msgid "`matrix_mxisd_ldap_connection_port`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3389
+msgid "`matrix_mxisd_ldap_connection_baseDn`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3390
+msgid "`matrix_mxisd_ldap_connection_baseDns`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3391
+#: ../../../CHANGELOG.md:3392
+msgid "`matrix_mxisd_ldap_connection_bindDn`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3393
+#: ../../../CHANGELOG.md:3397
+msgid "`matrix_mxisd_ldap_connection_bindPassword`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3394
+msgid "`matrix_mxisd_ldap_filter`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3395
+msgid "`matrix_mxisd_ldap_attribute_uid_type`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3396
+msgid "`matrix_mxisd_ldap_attribute_uid_value`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3398
+msgid "`matrix_mxisd_ldap_attribute_name`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3399
+msgid "`matrix_mxisd_ldap_attribute_threepid_email`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3400
+msgid "`matrix_mxisd_ldap_attribute_threepid_msisdn`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3401
+msgid "`matrix_mxisd_ldap_identity_filter`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3402
+msgid "`matrix_mxisd_ldap_identity_medium`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3403
+msgid "`matrix_mxisd_ldap_auth_filter`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3404
+msgid "`matrix_mxisd_ldap_directory_filter`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3405
+msgid "`matrix_mxisd_template_config`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3407
+msgid "You are encouraged to use the `matrix_mxisd_configuration_extension_yaml` variable to define your own mxisd configuration additions and overrides. Refer to the [default variables file](roles/custom/matrix-mxisd/defaults/main.yml) for more information."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3409
+msgid "This new way of configuring mxisd is beneficial because:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3411
+msgid "it lets us support all mxisd configuration options, as the playbook simply forwards them to mxisd without needing to care or understand them"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3412
+msgid "it lets you upgrade to newer mxisd versions and make use of their features, without us having to add support for them explicitly"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3415
+msgid "2019-01-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3417
+msgid "(BC Break) Cronjob schedule no longer configurable"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3419
+msgid "Due to the way we manage cronjobs now, you can no longer configure the schedule they're invoked at."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3421
+msgid "If you were previously using `matrix_ssl_lets_encrypt_renew_cron_time_definition` or `matrix_nginx_proxy_reload_cron_time_definition` to set a custom schedule, you should note that these variables don't affect anything anymore."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3424
+msgid "If you miss this functionality, please [open an Issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/new) and let us know about your use case!"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3427
+msgid "2018-12-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3429
+msgid "(BC Break) More SSL certificate retrieval methods"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3431
+msgid "The playbook now lets you decide between 3 different SSL certificate retrieval methods:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3432
+msgid "(default) obtaining free SSL certificates from Let's Encrypt"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3433
+msgid "generating self-signed SSL certificates"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3434
+msgid "managing SSL certificates manually"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3436
+msgid "Learn more in [Adjusting SSL certificate retrieval](docs/configuring-playbook-ssl-certificates.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3438
+msgid "For people who use Let's Encrypt (mostly everyone, since it's the default), you'll also have to rename a variable in your configuration:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3440
+msgid "before: `host_specific_matrix_ssl_support_email`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3441
+msgid "after: `host_specific_matrix_ssl_lets_encrypt_support_email`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3443
+msgid "(BC Break) mxisd upgrade with multiple base DN support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3445
+msgid "mxisd has bee upgraded to [version 1.2.2](https://github.com/kamax-matrix/mxisd/releases/tag/v1.2.2), which supports [multiple base DNs](https://github.com/kamax-matrix/mxisd/blob/v1.2.2/docs/stores/ldap.md#base)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3447
+msgid "If you were configuring this playbook's `matrix_mxisd_ldap_connection_baseDn` variable until now (a string containing a single base DN), you'll need to change to configuring the `matrix_mxisd_ldap_connection_baseDns` variable (an array containing multiple base DNs)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3449
+msgid "Example change:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3451
+msgid "before: `matrix_mxisd_ldap_connection_baseDn: OU=Users,DC=example,DC=org`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3452
+msgid "after: `matrix_mxisd_ldap_connection_baseDns: ['OU=Users,DC=example,DC=org']`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3455
+msgid "2018-12-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3457
+msgid "Synapse 0.34.0 and Python 3"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3459
+msgid "Synapse has been upgraded to 0.34.0 and now uses Python 3. Based on feedback from others, running Synapse on Python 3 is supposed to decrease memory usage significantly (~2x)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3462
+msgid "2018-12-12"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3464
+msgid "Riot homepage customization"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3466
+msgid "You can now customize some parts of the Riot homepage (or even completely replace it with your own custom page). See the `matrix_riot_web_homepage_` variables in `roles/custom/matrix-riot-web/defaults/main.yml`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3469
+msgid "2018-12-04"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3471
+msgid "mxisd extensibility"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3473
+msgid "The [LDAP identity store for mxisd](https://github.com/kamax-matrix/mxisd/blob/master/docs/stores/ldap.md) can now be configured easily using playbook variables (see the `matrix_mxisd_ldap_` variables in `roles/custom/matrix-server/defaults/main.yml`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3476
+msgid "2018-11-28"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3478
+msgid "More scripts"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3480
+msgid "matrix-remove-all allows to uninstall everything with a single command"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3481
+msgid "matrix-make-user-admin allows to upgrade a user's privileges"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3483
+msgid "LDAP auth support via matrix-synapse-ldap3"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3485
+msgid "The playbook can now install and configure [LDAP auth support](https://github.com/matrix-org/matrix-synapse-ldap3) for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3487
+msgid "Additional details are available in [Setting up the LDAP authentication password provider module](docs/configuring-playbook-ldap-auth.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3490
+msgid "2018-11-23"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3492
+msgid "Support for controlling public registration and room auto-join"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3494
+msgid "The playbook now lets you enable public registration for users (controlled via `matrix_synapse_enable_registration`). By default, public registration is forbidden."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3496
+msgid "You can also make people automatically get auto-joined to rooms (controlled via `matrix_synapse_auto_join_rooms`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3498
+msgid "Support for changing the welcome user ID (welcome bot)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3500
+msgid "By default, `@riot-bot:matrix.org` is used to welcome newly registered users. This can be changed to something else (or disabled) via the new `matrix_riot_web_welcome_user_id` variable."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3503
+msgid "2018-11-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3505
+msgid "Ability to set Synapse log levels"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3507
+msgid "The playbook now allows you to set the log levels used by Synapse. The default logging levels remain the same."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3509
+msgid "You can now override following variables with any of the supported log levels listed here: https://docs.python.org/3/library/logging.html#logging-levels"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3518
+msgid "2018-11-03"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3520
+msgid "Customize parts of Riot's config"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3522
+msgid "You can now customize some parts of Riot's `config.json`. These playbook variables, with these default values, have been added:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3533
+msgid "This now allows you use a custom integration manager like [Dimension](https://dimension.t2bot.io). For example, if you wish to use the Dimension instance hosted at dimension.t2bot.io, you can set the following in your vars.yml file:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3542
+msgid "SSL protocols used to serve Riot and Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3544
+msgid "There's now a new `matrix_nginx_proxy_ssl_protocols` playbook variable, which controls the SSL protocols used to serve Riot and Synapse. Its default value is `TLSv1.1 TLSv1.2`. This playbook previously used `TLSv1 TLSv1.1 TLSv1.2` to serve Riot and Synapse."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3546
+msgid "You may wish to reenable TLSv1 if you need to access Riot in older browsers."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3548
+msgid "Note: Currently the dockerized nginx doesn't support TLSv1.3. See https://github.com/nginxinc/docker-nginx/issues/190 for more details."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3551
+msgid "2018-11-01"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3553
+msgid "Postgres 11 support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3555
+msgid "The playbook now installs [Postgres 11](https://www.postgresql.org/about/news/1894/) by default."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3557
+msgid "If you have have an existing setup, it's likely running on an older Postgres version (9.x or 10.x). You can easily upgrade by following the [upgrading PostgreSQL guide](docs/maintenance-postgres.md#upgrading-postgresql)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3559
+#: ../../../CHANGELOG.md:3646
+#: ../../../CHANGELOG.md:3766
+msgid "(BC Break) Renaming playbook variables"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3561
+msgid "Due to the large amount of features added to this playbook lately, to keep things manageable we've had to reorganize its configuration variables a bit."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3565
+msgid "from `matrix_docker_image_mxisd` to `matrix_mxisd_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3566
+msgid "from `matrix_docker_image_mautrix_telegram` to `matrix_mautrix_telegram_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3567
+msgid "from `matrix_docker_image_mautrix_whatsapp` to `matrix_mautrix_whatsapp_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3568
+msgid "from `matrix_docker_image_mailer` to `matrix_mailer_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3569
+msgid "from `matrix_docker_image_coturn` to `matrix_coturn_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3570
+msgid "from `matrix_docker_image_goofys` to `matrix_s3_goofys_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3571
+msgid "from `matrix_docker_image_riot` to `matrix_riot_web_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3572
+msgid "from `matrix_docker_image_nginx` to `matrix_nginx_proxy_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3573
+msgid "from `matrix_docker_image_synapse` to `matrix_synapse_docker_image`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3574
+msgid "from `matrix_docker_image_postgres_v9` to `matrix_postgres_docker_image_v9`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3575
+msgid "from `matrix_docker_image_postgres_v10` to `matrix_postgres_docker_image_v10`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3576
+msgid "from `matrix_docker_image_postgres_latest` to `matrix_postgres_docker_image_latest`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3579
+msgid "2018-10-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3581
+msgid "Mautrix Whatsapp bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3583
+msgid "The playbook now supports bridging with [Whatsapp](https://www.whatsapp.com/) by installing the [mautrix-whatsapp](https://github.com/tulir/mautrix-whatsapp) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3585
+msgid "Additional details are available in [Setting up Mautrix Whatsapp bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3588
+msgid "2018-10-25"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3590
+msgid "Support for controlling Matrix federation"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3592
+msgid "The playbook can now help you with [Controlling Matrix federation](docs/configuring-playbook-federation), should you wish to run a more private (isolated) server."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3595
+msgid "2018-10-24"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3597
+msgid "Disabling riot-web guests"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3599
+msgid "From now on, Riot's configuration setting `disable_guests` would be set to `true`. The homeserver was rejecting guests anyway, so this is just a cosmetic change affecting Riot's UI."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3602
+msgid "2018-10-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3604
+msgid "Self-check maintenance command"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3606
+msgid "The playbook can now [check if services are configured correctly](docs/maintenance-checking-services.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3609
+msgid "2018-10-05"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3611
+msgid "Presence tracking made configurable"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3613
+msgid "The playbook can now enable/disable user presence-status tracking in Synapse, through the playbook's `matrix_synapse_use_presence` variable (having a default value of `true` - enabled)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3615
+msgid "If users participate in large rooms with many other servers, disabling presence will decrease server load significantly."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3618
+msgid "2018-09-27"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3620
+msgid "Synapse Cache Factor made configurable"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3622
+msgid "The playbook now makes the Synapse cache factor configurable, through the playbook's `matrix_synapse_cache_factor` variable (having a default value of `0.5`)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3624
+msgid "Changing that value allows you to potentially decrease RAM usage or to increase performance by caching more stuff. Some information on it is available here: https://github.com/element-hq/synapse#help-synapse-eats-all-my-ram"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3627
+msgid "2018-09-26"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3629
+msgid "Disabling Docker container logging"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3631
+msgid "`--log-driver=none` is used for all Docker containers now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3633
+msgid "All these containers are started through systemd anyway and get logged in journald, so there's no need for Docker to be logging the same thing using the default `json-file` driver. Doing that was growing `/var/lib/docker/containers/..` infinitely until service/container restart."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3635
+msgid "As a result of this, things like `docker logs matrix-synapse` won't work anymore. `journalctl -u matrix-synapse` is how one can see the logs."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3638
+msgid "2018-09-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3640
+msgid "Service discovery support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3642
+msgid "The playbook now helps you set up [service discovery](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery) using a `/.well-known/matrix/client` file."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3644
+msgid "Additional details are available in [Configuring service discovery via .well-known](docs/configuring-well-known.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3650
+msgid "from `matrix_nginx_riot_web_data_path` to `matrix_riot_web_data_path`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3651
+msgid "from `matrix_riot_web_default_identity_server_url` to `matrix_identity_server_url`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3654
+msgid "2018-09-07"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3656
+msgid "Mautrix Telegram bridging support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3658
+msgid "The playbook now supports bridging with [Telegram](https://telegram.org/) by installing the [mautrix-telegram](https://github.com/tulir/mautrix-telegram) bridge. This playbook functionality is available thanks to [@izissise](https://github.com/izissise)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3660
+msgid "Additional details are available in [Setting up Mautrix Telegram bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3662
+msgid "Events cache size increase and configurability for Matrix Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3664
+msgid "The playbook now lets you configure Matrix Synapse's `event_cache_size` configuration via the `matrix_synapse_event_cache_size` playbook variable."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3666
+msgid "Previously, this value was hardcoded to `\"10K\"`. From now on, a more reasonable default of `\"100K\"` is used."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3668
+msgid "Password-peppering support for Matrix Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3670
+msgid "The playbook now supports enabling password-peppering for increased security in Matrix Synapse via the `matrix_synapse_password_config_pepper` playbook variable. Using a password pepper is disabled by default (just like it used to be before this playbook variable got introduced) and is not to be enabled/disabled after initial setup, as that would invalidate all existing passwords."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3672
+msgid "Statistics-reporting support for Matrix Synapse"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3674
+msgid "There's now a new `matrix_synapse_report_stats` playbook variable, which controls the `report_stats` configuration option for Matrix Synapse. It defaults to `false`, so no change is required to retain your privacy."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3676
+msgid "If you'd like to start reporting statistics about your homeserver (things like number of users, number of messages sent, uptime, load, etc.) to matrix.org, you can turn on stats reporting."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3679
+msgid "2018-08-29"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3681
+msgid "Changing the way SSL certificates are retrieved"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3683
+msgid "We've been using [acmetool](https://github.com/hlandau/acme) (with the [willwill/acme-docker](https://hub.docker.com/r/willwill/acme-docker/) Docker image) until now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3685
+msgid "Due to the Docker image being deprecated, and things looking bleak for acmetool's support of the newer ACME v2 API endpoint, we've switched to using [certbot](https://certbot.eff.org/) (with the [certbot/certbot](https://hub.docker.com/r/certbot/certbot/) Docker image)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3687
+msgid "Simply re-running the playbook will retrieve new certificates (via certbot) for you. To ensure you don't leave any old files behind, though, you'd better do this:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3689
+msgid "`systemctl stop 'matrix*'`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3690
+msgid "stop your custom webserver, if you're running one (only affects you if you've installed with `matrix_nginx_proxy_enabled: false`)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3691
+msgid "`mv /matrix/ssl /matrix/ssl-acmetool-delete-later`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3692
+msgid "re-run the playbook's [installation](docs/installing.md)"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3693
+msgid "possibly delete `/matrix/ssl-acmetool-delete-later`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3696
+msgid "2018-08-21"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3698
+msgid "Matrix Corporal support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3700
+msgid "The playbook can now install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3702
+msgid "Additional details are available in [Setting up Matrix Corporal](docs/configuring-playbook-matrix-corporal.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3705
+msgid "2018-08-20"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3707
+msgid "Matrix Synapse rate limit control variables"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3709
+msgid "The following new variables can now be configured to control Matrix Synapse's rate-limiting (default values are shown below)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3716
+msgid "Shared Secret Auth support via matrix-synapse-shared-secret-auth"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3718
+msgid "The playbook can now install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3720
+msgid "Additional details are available in [Setting up the Shared Secret Auth password provider module](docs/configuring-playbook-shared-secret-auth.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3723
+msgid "2018-08-17"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3725
+msgid "REST auth support via matrix-synapse-rest-auth"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3727
+msgid "The playbook can now install and configure [matrix-synapse-rest-auth](https://github.com/kamax-io/matrix-synapse-rest-auth) for you."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3729
+msgid "Additional details are available in [Setting up the REST authentication password provider module](docs/configuring-playbook-rest-auth.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3731
+msgid "Compression improvements"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3733
+msgid "Shifted Matrix Synapse compression from happening in the Matrix Synapse, to happening in the nginx proxy that's in front of it."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3736
+msgid "Additionally, `riot-web` also gets compressed now (in the nginx proxy), which drops the initial page load's size from 5.31MB to 1.86MB."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3739
+msgid "Disabling some unnecessary Synapse services"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3741
+msgid "The following services are not necessary, so they have been disabled:"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3742
+msgid "on the federation port (8448): the `client` service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3743
+msgid "on the http port (8008, exposed over 443): the old Angular `webclient` and the `federation` service"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3745
+msgid "Federation runs only on the federation port (8448) now. The Client APIs run only on the http port (8008) now."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3748
+msgid "2018-08-15"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3750
+msgid "mxisd Identity Server support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3752
+msgid "The playbook now sets up an [mxisd](https://github.com/kamax-io/mxisd) Identity Server for you by default. Additional details are available in [Setting up ma1sd Identity Server](docs/configuring-playbook-mxisd.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3755
+msgid "2018-08-14"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3757
+msgid "Email-sending support"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3759
+msgid "The playbook now configures an email-sending service (postfix) by default. Additional details are available in [Adjusting email-sending settings](docs/configuring-playbook-email.md)."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3761
+msgid "With this, Matrix Synapse is able to send email notifications for missed messages, etc."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3764
+msgid "2018-08-08"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3770
+msgid "from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3771
+msgid "from `matrix_max_log_file_size_mb` to `matrix_synapse_max_log_file_size_mb`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3772
+msgid "from `matrix_max_log_files_count` to `matrix_synapse_max_log_files_count`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3773
+msgid "from `docker_matrix_image` to `matrix_docker_image_synapse`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3774
+msgid "from `docker_nginx_image` to `matrix_docker_image_nginx`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3775
+msgid "from `docker_riot_image` to `matrix_docker_image_riot`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3776
+msgid "from `docker_goofys_image` to `matrix_docker_image_goofys`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3777
+msgid "from `docker_coturn_image` to `matrix_docker_image_coturn`"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3779
+msgid "If you're overriding any of them in your `vars.yml` file, you'd need to change to the new names."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3781
+msgid "Renaming Ansible playbook tag"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3783
+msgid "The command for executing the whole playbook has changed. The `setup-main` tag got renamed to `setup-all`."
+msgstr ""
+
+#: ../../../CHANGELOG.md:3785
+msgid "Docker container linking"
+msgstr ""
+
+#: ../../../CHANGELOG.md:3787
+msgid "Changed the way the Docker containers are linked together. The ones that need to communicate with others operate in a `matrix` network now and not in the default bridge network."
+msgstr ""
diff --git a/i18n/translation-templates/README.pot b/i18n/translation-templates/README.pot
new file mode 100644
index 000000000..23cfe9a49
--- /dev/null
+++ b/i18n/translation-templates/README.pot
@@ -0,0 +1,1177 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 09:53+0200\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"
+
+#: ../../../README.md:1
+msgid "[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)"
+msgstr ""
+
+#: ../../../README.md:1
+msgid "Support room on Matrix"
+msgstr ""
+
+#: ../../../README.md:1
+msgid "donate"
+msgstr ""
+
+#: ../../../README.md:3
+msgid "Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker"
+msgstr ""
+
+#: ../../../README.md:5
+msgid "🎯 Purpose"
+msgstr ""
+
+#: ../../../README.md:7
+msgid "This [Ansible](https://www.ansible.com/) playbook is meant to help you run your own [Matrix](http://matrix.org/) homeserver, along with the [various services](#supported-services) related to that."
+msgstr ""
+
+#: ../../../README.md:9
+msgid "That is, it lets you join the Matrix network using your own user ID like `@alice:example.com`, all hosted on your own server (see [prerequisites](docs/prerequisites.md))."
+msgstr ""
+
+#: ../../../README.md:11
+msgid "We run all [supported services](#-supported-services) in [Docker](https://www.docker.com/) containers (see [the container images we use](docs/container-images.md)), which lets us have a predictable and up-to-date setup, across multiple supported distros (see [prerequisites](docs/prerequisites.md)) and [architectures](docs/alternative-architectures.md) (x86/amd64 being recommended)."
+msgstr ""
+
+#: ../../../README.md:13
+msgid "Installation (upgrades) and some maintenance tasks are automated using [Ansible](https://www.ansible.com/) (see [our Ansible guide](docs/ansible.md))."
+msgstr ""
+
+#: ../../../README.md:15
+msgid "☁ Self-hosting or Managed / SaaS"
+msgstr ""
+
+#: ../../../README.md:17
+msgid "This Ansible playbook tries to make self-hosting and maintaining a Matrix server fairly easy (see [Getting started](#-getting-started)). Still, running any service smoothly requires knowledge, time and effort."
+msgstr ""
+
+#: ../../../README.md:19
+msgid "If you like the [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) spirit of this Ansible playbook, but prefer to put the responsibility on someone else, you can also [get a managed Matrix server from etke.cc](https://etke.cc?utm_source=github&utm_medium=readme&utm_campaign=mdad) (both hosting and on-premises) - a service built on top of this Ansible playbook but with [additional components](https://etke.cc/help/extras/?utm_source=github&utm_medium=readme&utm_campaign=mdad) and [services](https://etke.cc/services/?utm_source=github&utm_medium=readme&utm_campaign=mdad) which all help you run a Matrix server with ease. Be advised that etke.cc operates on a subscription-based approach and there is no \"just set up my server once and be done with it\" option."
+msgstr ""
+
+#: ../../../README.md:21
+msgid "🚀 Getting started"
+msgstr ""
+
+#: ../../../README.md:23
+msgid "We have detailed documentation in the [docs/](./docs) directory - see the Table of Contents in the [documentation README](./docs/README.md)."
+msgstr ""
+
+#: ../../../README.md:25
+msgid "While the [list of supported services](#-supported-services) and documentation is very extensive, you don't need to read through everything. We recommend:"
+msgstr ""
+
+#: ../../../README.md:27
+msgid "Starting with the basics. You can always add/remove or tweak services later on."
+msgstr ""
+
+#: ../../../README.md:29
+msgid "Following our installation guide. There are two guides available for beginners and advanced users:"
+msgstr ""
+
+#: ../../../README.md:31
+msgid "⚡ **[Quick start](./docs/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 ""
+
+#: ../../../README.md:33
+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](./docs/prerequisites.md)** documentation page."
+msgstr ""
+
+#: ../../../README.md:35
+msgid "If you experience an issue on configuring the playbook, setting up your server, maintaining services on it, etc., please take a look at our [FAQ](./docs/faq.md). If you cannot find an answer to your question, feel free to ask for [help and support](#-support)."
+msgstr ""
+
+#: ../../../README.md:37
+msgid "✔ Supported services"
+msgstr ""
+
+#: ../../../README.md:39
+msgid "Using this playbook, you can get the following list of services configured on your server. Basically, this playbook aims to get you up-and-running with all the necessities around Matrix, without you having to do anything else."
+msgstr ""
+
+#: ../../../README.md:41
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../README.md:43
+msgid "The list below is exhaustive. It includes optional or even some advanced components that you will most likely not need. Sticking with the defaults (which install a subset of the above components) is the best choice, especially for a new installation. You can always re-run the playbook later to add or remove components."
+msgstr ""
+
+#: ../../../README.md:45
+msgid "Deprecated or unmaintained services are not listed. You can find documentations for them [here](docs/configuring-playbook.md#deprecated--unmaintained--removed-services)."
+msgstr ""
+
+#: ../../../README.md:47
+msgid "Homeserver"
+msgstr ""
+
+#: ../../../README.md:49
+msgid "The homeserver is the backbone of your Matrix system. Choose one from the following list."
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Name"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Default?"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Description"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Documentation"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Synapse](https://github.com/element-hq/synapse)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "✅"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-synapse.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Conduit](https://conduit.rs)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "❌"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-conduit.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Dendrite](https://github.com/matrix-org/dendrite)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse."
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-dendrite.md)"
+msgstr ""
+
+#: ../../../README.md:57
+msgid "Clients"
+msgstr ""
+
+#: ../../../README.md:59
+msgid "Web clients for Matrix that you can host on your own domains."
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Element Web](https://github.com/element-hq/element-web)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Default Matrix web client, configured to connect to your own Synapse server"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-client-element-web.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Hydrogen](https://github.com/element-hq/hydrogen-web)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Lightweight Matrix client with legacy and mobile browser support"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-client-hydrogen.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Cinny](https://github.com/ajbura/cinny)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Simple, elegant and secure web client"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-client-cinny.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[SchildiChat Web](https://schildi.chat/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Based on Element Web, with a more traditional instant messaging experience"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-client-schildichat-web.md)"
+msgstr ""
+
+#: ../../../README.md:68
+msgid "Server Components"
+msgstr ""
+
+#: ../../../README.md:70
+msgid "Services that run on the server to make the various parts of your installation work."
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[PostgreSQL](https://www.postgresql.org/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Database for Synapse. [Using an external PostgreSQL server](docs/configuring-playbook-external-postgres.md) is also possible."
+msgstr ""
+
+#: ../../../README.md:0
+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 ""
+
+#: ../../../README.md:0
+msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](docs/configuring-playbook-own-webserver.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-traefik.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Let's Encrypt](https://letsencrypt.org/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Free SSL certificate, which secures the connection to all components"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-ssl-certificates.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Exim](https://www.exim.org/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-email.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[ma1sd](https://github.com/ma1uta/ma1sd)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Matrix Identity Server"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-ma1sd.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[ddclient](https://github.com/linuxserver/docker-ddclient)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Dynamic DNS"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-dynamic-dns.md)"
+msgstr ""
+
+#: ../../../README.md:82
+msgid "Authentication"
+msgstr ""
+
+#: ../../../README.md:84
+msgid "Extend and modify how users are authenticated on your homeserver."
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) (advanced)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "REST authentication password provider module"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-rest-auth.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) (advanced)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Password provider module"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-shared-secret-auth.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) (advanced)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "LDAP Auth password provider module"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-ldap-auth.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) (advanced)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "A proxy that handles Matrix registration requests and forwards them to LDAP."
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-matrix-ldap-registration-proxy.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[matrix-registration](https://github.com/ZerataX/matrix-registration)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "A simple python application to have a token based Matrix registration"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-matrix-registration.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (UVS)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Service to verify details of a user based on an Open ID token"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-user-verification-service.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) (advanced)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "A spam checker module"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-synapse-simple-antispam.md)"
+msgstr ""
+
+#: ../../../README.md:96
+msgid "File Storage"
+msgstr ""
+
+#: ../../../README.md:98
+msgid "Use alternative file storage to the default `media_store` folder."
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Goofys](https://github.com/kahing/goofys)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-s3-goofys.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-s3.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[matrix-media-repo](https://github.com/turt2live/matrix-media-repo)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "matrix-media-repo is a 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 ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-matrix-media-repo.md)"
+msgstr ""
+
+#: ../../../README.md:106
+msgid "Bridges"
+msgstr ""
+
+#: ../../../README.md:108
+msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[mautrix-discord](https://github.com/mautrix/discord)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [Discord](https://discord.com/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-discord.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[mautrix-slack](https://github.com/mautrix/slack)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [Slack](https://slack.com/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-slack.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[mautrix-telegram](https://github.com/mautrix/telegram)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [Telegram](https://telegram.org/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-telegram.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[mautrix-gmessages](https://github.com/mautrix/gmessages)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [Google Messages](https://messages.google.com/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-gmessages.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[mautrix-whatsapp](https://github.com/mautrix/whatsapp)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [WhatsApp](https://www.whatsapp.com/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-whatsapp.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[mautrix-wsproxy](https://github.com/mautrix/wsproxy)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to Android SMS or Apple iMessage"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-wsproxy.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[mautrix-twitter](https://github.com/mautrix/twitter)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [Twitter](https://twitter.com/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-twitter.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[mautrix-googlechat](https://github.com/mautrix/googlechat)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-googlechat.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[mautrix-meta](https://github.com/mautrix/instagram)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Link for [Messenger](docs/configuring-playbook-bridge-mautrix-meta-messenger.md) / [Instagram](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[mautrix-signal](https://github.com/mautrix/signal)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [Signal](https://www.signal.org/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-mautrix-signal.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[beeper-linkedin](https://github.com/beeper/linkedin)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [LinkedIn](https://www.linkedin.com/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-beeper-linkedin.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-appservice-irc.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-appservice-kakaotalk.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [Discord](https://discordapp.com/)"
+msgstr ""
+
+#: ../../../README.md:0
+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 ""
+
+#: ../../../README.md:0
+msgid "Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-hookshot.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to SMS"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-matrix-bridge-sms.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[matrix-wechat](https://github.com/duo/matrix-wechat)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [WeChat](https://www.wechat.com/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-wechat.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Heisenbridge](https://github.com/hifi/heisenbridge)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-heisenbridge.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[go-skype-bridge](https://github.com/kelaresg/go-skype-bridge)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [Skype](https://www.skype.com)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-go-skype-bridge.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [Slack](https://slack.com)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-slack.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-instagram.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-twitter.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-discord.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [GroupMe](https://groupme.com/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-groupme.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge to [Steam](https://steamapp.com/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-steam.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Email2Matrix](https://github.com/devture/email2matrix)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bridge for relaying emails to Matrix rooms"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-email2matrix.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Postmoogle](https://github.com/etkecc/postmoogle)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Email to Matrix bridge"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bridge-postmoogle.md)"
+msgstr ""
+
+#: ../../../README.md:141
+msgid "Bots"
+msgstr ""
+
+#: ../../../README.md:143
+msgid "Bots provide various additional functionality to your installation."
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[baibot](https://github.com/etkecc/baibot)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bot-baibot.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bot for scheduling one-off & recurring reminders and alarms"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bot-matrix-reminder-bot.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bot for invitations by creating and managing registration tokens"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bot-matrix-registration-bot.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[maubot](https://github.com/maubot/maubot)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "A plugin-based Matrix bot system"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bot-maubot.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Honoroit](https://github.com/etkecc/honoroit)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "A helpdesk bot"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bot-honoroit.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Mjolnir](https://github.com/matrix-org/mjolnir)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "A moderation tool for Matrix"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bot-mjolnir.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Draupnir](https://github.com/the-draupnir-project/Draupnir)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "A moderation tool for Matrix (Fork of Mjolnir)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bot-draupnir.md) (for [appservice mode](docs/configuring-playbook-appservice-draupnir-for-all.md))"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Buscarron](https://github.com/etkecc/buscarron)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Web forms (HTTP POST) to Matrix"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-bot-buscarron.md)"
+msgstr ""
+
+#: ../../../README.md:156
+msgid "Administration"
+msgstr ""
+
+#: ../../../README.md:158
+msgid "Services that help you in administrating and monitoring your Matrix installation."
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-alertmanager-receiver.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "OAuth 2.0 and OpenID Provider server"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-matrix-authentication-service.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[synapse-admin](https://github.com/etkecc/synapse-admin)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "A web UI tool for administrating users and rooms on your Matrix server"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-synapse-admin.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Metrics and Graphs"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Consists of the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI, with [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) being available too"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-nginxlog.md))"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Borg](https://borgbackup.org)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Backups"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-backup-borg.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[rageshake](https://github.com/matrix-org/rageshake)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Bug report server"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-rageshake.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus."
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-synapse-usage-exporter.md)"
+msgstr ""
+
+#: ../../../README.md:170
+msgid "Misc"
+msgstr ""
+
+#: ../../../README.md:172
+msgid "Various services that don't fit any other categories."
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[sliding-sync](https://github.com/matrix-org/sliding-sync)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "(Superseded by Simplified Sliding Sync integrated into Synapse > `1.114` and Conduit > `0.6.0`) Sliding Sync support for clients which require it (e.g. old Element X versions before Simplified Sliding Sync was developed)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-sliding-sync-proxy.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-accept-invite)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "A 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 ""
+
+#: ../../../README.md:0
+msgid "A cli tool that automatically compresses `state_groups` database table in background."
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-synapse-auto-compressor.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Matrix Corporal](https://github.com/devture/matrix-corporal) (advanced)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Reconciliator and gateway for a managed Matrix server"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-matrix-corporal.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Etherpad](https://etherpad.org)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "An open source collaborative text editor"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-etherpad.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Jitsi](https://jitsi.org/)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "An open source video-conferencing platform"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-jitsi.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Cactus Comments](https://cactus.chat)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "A federated comment system built on Matrix"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-cactus-comments.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Pantalaimon](https://github.com/matrix-org/pantalaimon)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "An E2EE aware proxy daemon"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-pantalaimon.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Sygnal](https://github.com/matrix-org/sygnal)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Push gateway"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-sygnal.md)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[ntfy](https://ntfy.sh)"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "Push notifications server"
+msgstr ""
+
+#: ../../../README.md:0
+msgid "[Link](docs/configuring-playbook-ntfy.md)"
+msgstr ""
+
+#: ../../../README.md:187
+msgid "🆕 Changes"
+msgstr ""
+
+#: ../../../README.md:189
+msgid "This playbook evolves over time, sometimes with backward-incompatible changes."
+msgstr ""
+
+#: ../../../README.md:191
+msgid "When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up with what's new."
+msgstr ""
+
+#: ../../../README.md:193
+msgid "🆘 Support"
+msgstr ""
+
+#: ../../../README.md:195
+msgid "Matrix room: [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)"
+msgstr ""
+
+#: ../../../README.md:197
+msgid "IRC channel: `#matrix-docker-ansible-deploy` on the [Libera Chat](https://libera.chat/) IRC network (irc.libera.chat:6697)"
+msgstr ""
+
+#: ../../../README.md:199
+msgid "GitHub issues: [spantaleev/matrix-docker-ansible-deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues)"
+msgstr ""
+
+#: ../../../README.md:201
+msgid "🌐 Translation"
+msgstr ""
+
+#: ../../../README.md:203
+msgid "See the [i18n/README.md](i18n/README.md) file for more information about translation."
+msgstr ""
+
+#: ../../../README.md:205
+msgid "Translations are still work in progress."
+msgstr ""
+
+#: ../../../README.md:207
+msgid "🤝 Related"
+msgstr ""
+
+#: ../../../README.md:209
+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
+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 ""
diff --git a/i18n/translation-templates/YEAR-IN-REVIEW.pot b/i18n/translation-templates/YEAR-IN-REVIEW.pot
new file mode 100644
index 000000000..57712a5b0
--- /dev/null
+++ b/i18n/translation-templates/YEAR-IN-REVIEW.pot
@@ -0,0 +1,289 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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"
+
+#: ../../../YEAR-IN-REVIEW.md:1
+msgid "2023"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:3
+msgid "2023 was a year filled with many changes for matrix-docker-ansible-deploy. In this post, we're looking backward at some of the major changes that happened this year, as well as taking a glimpse of what's ahead in 2024."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:5
+msgid "2023 is probably [the year of AI](https://journal.everypixel.com/2023-the-year-of-ai), with millions of people jumping aboard [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/chatgpt) train. matrix-docker-ansible-deploy is no stranger to this and 2023 began with a PR from [bertybuttface](https://github.com/bertybuttface) who added support for [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#chatgpt-support)). While OpenAI's chat GPT website was frequently overloaded in the past, their API was up which made using this bot both convenient and more reliable."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:7
+msgid "AI aside, with the playbook's focus being containers, we're **doubling down on being \"container native\"** and becoming more interoperable for people hosting other containers on the Matrix server. In [2022](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/YEAR-IN-REVIEW.md#2022), we've announced a few sibling Ansible playbooks, their use of [Traefik](https://doc.traefik.io/traefik/) and the possiblity of matrix-docker-ansible-deploy also switching to this reverse-proxy. This prediction materialized quickly. The **largest change** in the playbook in 2023 happened way back in February - matrix-docker-ansible-deploy [starting the switch from nginx to Traefik](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-reverse-proxy-configuration-changes-and-initial-traefik-support) and then quickly [making Treafik the default reverse-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#traefik-is-the-default-reverse-proxy-now). As noted in the changelog entries, we envisioned a quick and complete elimination of `matrix-nginx-proxy`, but at the end of 2023, it hasn't happened yet. The playbook is already using Traefik as the front-most reverse-proxy, but nginx (via `matrix-nginx-proxy`) is still around - it has taken a step back and is only used internally for new setups. Work got to a stall due to:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:9
+msgid "complexity: untangling the overly large and messy `matrix-nginx-proxy` component is difficult"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:10
+msgid "the current setup became \"good enough\" because nginx has become an internal implementation detail for those who have migrated to Traefik. Traefik is already the default public reverse-proxy and gives better possibilities to people wishing to run other web-exposed containers on their Matrix server via [Docker Compose](https://docs.docker.com/compose/), other Ansible playbooks like [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) (more about this one, below) or any other way."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:12
+msgid "`matrix-nginx-proxy` is no longer in the way of us being interoperable, but its ugly internal details are still there. It is one more proxy in the long chain of reverse-proxies we have and we'd like to cut it out. This would both make things simpler and also boost performance."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:14
+msgid "The delay in eliminating `matrix-nginx-proxy` has probably been welcome by many existing users who decided to postpone the Traefik migration a bit longer. In 2024, work on eliminating `matrix-nginx-proxy` will continue with rapid pace. People who are still using `matrix-nginx-proxy` as their front-most reverse-proxy will need to rework their setup. About a year of putting it off has been long enough."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:16
+msgid "This large Traefik reverse-proxy change was also accompanied by another internal change which began in 2022, but continued in 2023 - **moving non-Matrix-related roles from being internal to the playbook to living their own life outside of it**. Various roles were made more decoupled and moved outside of the playbook, so that other projects (like the [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook or other Ansible playbooks) could benefit from them. This led to the **death of a few sibling playbooks** ([gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy), [nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), [peertube-docker-ansible-deploy](https://github.com/spantaleev/peertube-docker-ansible-deploy), [vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy)), but brought life to something better, which supports all these services and more."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:18
+msgid "[mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) is a new Ansible playbook that a few of us (matrix-docker-ansible-deploy contributors) have launched in 2023. It has quickly grown to supports [60+ services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md) and aims to do the same for [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) service hosting, as matrix-docker-ansible-deploy has done for Matrix - providing a clean and secure way to run a bunch of services in containers on a regular server (that is to say, without Kubernetes, etc.). Thanks to Traefik and Ansible role reuse, it's easy to host both mash-playbook services and matrix-docker-ansible-deploy services on the same server - see mash-playbook's [interoperability](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md) documentation page. If you've been looking for a holiday project or your New Year's Resolutions list contains \"self-hosting more services\", then you're welcome to give this new playbook a try and join its Matrix room ([#mash-playbook:devture.com](https://matrix.to/#/#mash-playbook:devture.com))."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:20
+msgid "Because many of the roles are now external to this playbook (defined in the [requirements.yml](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/da27655ef34999fa924bc0a5e641dbd9ba06f133/requirements.yml) file), running `make roles` (or better yet `just roles` via the [just tool](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#support-for-running-commands-via-just)) becomes a necessity each time one pulls playbook updates (`git pull`). Pulling external roles happens via the [ansible-galaxy](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html) command-line tool, but if available, the playbook would also use the much faster [agru](https://github.com/etkecc/agru) tool (developed by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) this year)."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:22
+msgid "With the internal (but important) details out of the way, we can now talk more about **new features that landed in matrix-docker-ansible-deploy in 2023**."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:24
+msgid "The following **new** **bridges** were added to the playbook in 2023:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:26
+msgid "(2023-01-11) [mautrix-slack](https://mau.dev/mautrix/slack), thanks to a PR by [Cody Neiman](https://github.com/xangelix) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#mautrix-slack-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:27
+msgid "(2023-07-21) [mautrix-gmessages](https://github.com/mautrix/gmessages), thanks to a PR by [Shreyas Ajjarapu](https://github.com/shreyasajj) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#mautrix-gmessages-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:28
+msgid "(2023-08-23) [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for Apple iMessage bridging (when combined with the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android phone), thanks to a PR by [Johan Swetzén](https://github.com/jswetzen)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:30
+msgid "This brings the total number of **[bridges that the playbook supports](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/docs/configuring-playbook.md#bridging-other-networks) up to 30**. There are alternative bridge implementations for various networks and protocols, so the number of \"unique bridged networks\" is surely much smaller."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:32
+msgid "A few other **major components and changes** landed in 2023:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:34
+msgid "(2023-02-10) The [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool (successor to [Mjolnir](https://github.com/matrix-org/mjolnir)), thanks to a PR by [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#draupnir-moderation-tool-bot-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:35
+msgid "(2023-02-10) [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) to add Matrix Authentication Support to our Jitsi setup, thanks to a PR by [Jakob S.](https://github.com/jakicoll) from [zakk gGmbH](https://github.com/zakk-it) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-authentication-support-for-jitsi))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:36
+msgid "(2023-02-25) The [rageshake](https://github.com/matrix-org/rageshake) bug report server, thanks to a PR by [Benjamin Kampmann](https://github.com/gnunicorn) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#rageshake-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:37
+msgid "(2023-03-07) [Sliding Sync proxy](https://github.com/matrix-org/sliding-sync) (currently a necessary component for [Element X](https://element.io/labs/element-x) to work), thanks to: [Benjamin Kampmann](https://github.com/gnunicorn) and [FSG-Cat](https://github.com/FSG-Cat) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#sliding-sync-proxy-element-x-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:38
+msgid "(2023-03-12) synapse-auto-compressor to periodically and automatically run [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#synapse-auto-compressor-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:39
+msgid "(2023-07-17) [matrix-media-repo](https://github.com/turt2live/matrix-media-repo),  thanks to a PR by [Michael Hollister](https://github.com/Michael-Hollister) from [FUTO](https://www.futo.org/), the creators of the [Circles app](https://circu.li/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#matrix-media-repo-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:40
+msgid "(2023-08-31) [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) client app (fork of [Element Web)](https://github.com/element-hq/element-web), thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#schildichat-support))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:41
+msgid "(2023-10-18) Postgres parameters auto-tuning, thanks to a PR by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/) (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#postgres-parameters-are-automatically-tuned-now))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:42
+msgid "(2023-10-23) Enabling federation of the room directory for Synapse (see the [changelog entry](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#enabling-allow_public_rooms_over_federation-by-default-for-synapse))"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:44
+msgid "The most recent change in the list above (Enabling federation of the room directory for Synapse) has been somewhat **controversial** as it goes against upstream defaults for Synapse. Nevertheless, we believe it **promotes the well-being of the Matrix Federation by improving room discovery**."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:46
+msgid "**Matrix Federation Stats** (containing the percentage of servers publishing their room directory publicly) are posted to [TWIM](https://matrix.org/category/this-week-in-matrix/) each week by [Aine](https://gitlab.com/etke.cc) from [etke.cc](https://etke.cc/). The number of servers which [currently published their room directory publicly](https://matrix.org/blog/2023/12/2/this-week-in-matrix-2023-12-22/#matrix-federation-stats) stands at `26.6%`, which is:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:48
+msgid "**2.4% more** than when it was when [first published to TWIM](https://matrix.org/blog/2023/11/03/this-week-in-matrix-2023-11-03/#matrix-federation-stats) (1 month earlier, in November)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:49
+msgid "likely about **15+% more** than from before we flipped the switch (in October)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:51
+msgid "Hopefully, Synapse defaults would also change the same way and we'd see the number of servers publicly listing their room directory grow faster."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:53
+msgid "With this configuration change in place, projects like [MatrixRooms.info](https://matrixrooms.info/) (made by [etke.cc](https://etke.cc/)) and potentially others in the future, can discover, index the metadata (room address, title, topic, number of users, etc.) and make public rooms browsable & searchable across the whole Matrix Federation. It'd be great if users joining Matrix could more easily find interesting communities that match their interests!"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:55
+msgid "On the **media side of things**, besides Jitsi getting better Matrix integration (via the aforementioned Matrix User Verification Service), we've also had some [Coturn security tightening](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#backward-compatibility-tightening-coturn-security-can-lead-to-connectivity-issues) as well as [performance optimizations](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md#coturn-can-now-use-host-networking) for configurations exposing lots of network ports."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:57
+msgid "[Element Call](https://github.com/element-hq/element-call) seems to have become a nice and polished product lately (as proclaimed in [The Matrix Holiday Update 2023](https://matrix.org/blog/2023/12/25/the-matrix-holiday-update-2023/)), so 2024 is likely the year we'll see support for it in the playbook. Element Call depends on the [LiveKit](https://livekit.io/) streaming server (which is also useful to developers even by itself), so the first step is likely to see LiveKit support in mash-playbook via a reusable Ansible role. Such a LiveKit Ansible role could later easily land in matrix-docker-ansible-deploy and an Element Call static website could be hooked to it."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:59
+msgid "Besides these highlights, there were many other relatively large changes announced in our [CHANGELOG](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/850078b7e37401ce91a0f9b686f60b945f6c3a96/CHANGELOG.md) and hundreds of other more minor (but still important) playbook changes that didn't get a mention."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:61
+msgid "We have **hundreds of contributors to thank for their hard work** on making Matrix self-hosting better for all of us! It should be noted that **support comes in many shapes**, not only in raw code commits and financial help (via [donations](https://liberapay.com/s.pantaleev) or using the [etke.cc managed Matrix hosting service](https://etke.cc/) which is based on matrix-docker-ansible-deploy). It also comes in the shape of code reviews, helping others with [issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues), reporting new issues, participating in our support room on Matrix ([#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)), etc. To everyone who has been there to make matrix-docker-ansible-deploy better in 2023, thank you! 🙇‍♂️"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:64
+msgid "2022"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:66
+msgid "For [matrix-docker-ansible-deploy](https://github.com/spantaleev/matrix-docker-ansible-deploy/), 2022 started with **breaking the** [**Synapse**](https://github.com/element-hq/synapse) **monopoly** by [adding support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#dendrite-support) for the [Dendrite](https://github.com/matrix-org/dendrite) Matrix homeserver in early January. This required various internal changes so that the [Ansible](https://www.ansible.com/) playbook would not be Synapse-centric anymore. This groundwork paved the way for continuing in this direction and we [added support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#conduit-support) for [Conduit](https://conduit.rs/) in August."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:68
+msgid "When it comes to the `matrix-docker-ansible-deploy` Ansible playbook, 2022 was the year of the non-Synapse homeserver implementation. In practice, none of these homeserver implementations seem ready for prime-time yet and there is no migration path when coming from Synapse. Having done our job of adding support for these alternative homeserver implementations, we can say that we're not getting in the way of future progress. It's time for the Dendrite developers to push harder (development-wise) and for the Synapse developers to take a well-deserved long (infinite) break, and we may get to see more people migrating away from Synapse in the next year(s)."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:70
+msgid "Support for the following new **bridges** was added:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:72
+msgid "[Postmoogle](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#postmoogle-email-bridge-support) for bi-directional email bridging, which supersedes my old and simplistic [email2matrix](https://github.com/devture/email2matrix) one-way bridge-bot"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:73
+msgid "[mautrix-discord](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#mautrix-discord-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:74
+msgid "[go-skype-bridge](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#go-skype-bridge-bridging-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:75
+msgid "[matrix-appservice-kakaotalk](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-appservice-kakaotalk-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:77
+msgid "Support for the following new **bots** was added:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:79
+msgid "[buscarron bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#buscarron-bot-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:80
+msgid "[Honoroit bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#honoroit-bot-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:81
+msgid "[matrix-registration-bot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-registration-bot-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:82
+msgid "[matrix-hookshot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-hookshot-bridging-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:83
+msgid "[maubot](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#maubot-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:85
+msgid "Support for the following new **components and services** was added:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:87
+msgid "[BorgBackup](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#borg-backup-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:88
+msgid "[Cactus Comments](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cactus-comments-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:89
+msgid "[Cinny](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#cinny-support) client support"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:90
+msgid "[ntfy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#ntfy-push-notifications-support) notifications"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:91
+msgid "[matrix-ldap-registration-proxy](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix-ldap-registration-proxy-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:92
+msgid "[matrix\\_encryption\\_disabler support](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#matrix_encryption_disabler-support)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:93
+msgid "[synapse-s3-storage-provider](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-s3-storage-provider-support) to stop the Synapse media store from being a scalability problem. This brought along [another feature](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#synapse-container-image-customization-support) - an easier way to customize the Synapse container image without having to fork and self-build all of it from scratch"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:95
+msgid "Besides these major user-visible changes, a lot of work also happened **under the hood**:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:97
+msgid "we made [major improvements to Synapse workers](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#potential-backward-compatibility-break-major-improvements-to-synapse-workers) - adding support for stream writers and for running multiple workers of various kinds (federation senders, pushers, background task processing workers, etc.)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:98
+msgid "we [improved the compatibility of (Synapse + workers) with the rest of the playbook](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#backward-compatibility-break-changing-how-reverse-proxying-to-synapse-works---now-via-a-matrix-synapse-reverse-proxy-companion-service) by introducing a new `matrix-synapse-reverse-proxy-companion-service` service"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:99
+msgid "we started [splitting various Ansible roles out of the Matrix playbook and into independent roles](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#the-playbook-now-uses-external-roles-for-some-things) (e.g. `matrix-postgres` -> [ansible-role-postgres](https://github.com/mother-of-all-self-hosting/ansible-role-postgres)), which could be included in other Ansible playbooks. In fact, these roles already power a few **interesting other sibling playbooks**:"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:100
+msgid "[gitea-docker-ansible-deploy](https://github.com/spantaleev/gitea-docker-ansible-deploy), for deploying a [Gitea](https://gitea.io/) (self-hosted [Git](https://git-scm.com/) service) server"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:101
+msgid "[nextcloud-docker-ansible-deploy](https://github.com/spantaleev/nextcloud-docker-ansible-deploy), for deploying a [Nextcloud](https://nextcloud.com/) groupware server"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:102
+msgid "[vaultwarden-docker-ansible-deploy](https://github.com/spantaleev/vaultwarden-docker-ansible-deploy), for deploying a [Vaultwarden](https://github.com/dani-garcia/vaultwarden) password manager server (unofficial [Bitwarden](https://bitwarden.com/) compatible server)"
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:104
+msgid "These sibling playbooks co-exist nicely with one another due to using [Traefik](https://traefik.io/) for reverse-proxying, instead of trying to overtake the whole server by running their own [nginx](https://nginx.org/) reverse-proxy. Hopefully soon, the Matrix playbook will follow suit and be powered by Traefik by default."
+msgstr ""
+
+#: ../../../YEAR-IN-REVIEW.md:106
+msgid "Last, but not least, to optimize our [etke.cc managed Matrix hosting service](https://etke.cc/)'s performance (but also individual Ansible playbook runs for people self-hosting by themselves using the playbook), we've [improved playbook runtime 2-5x](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/ba09705f7fbaf0108652ecbe209793b1d935eba7/CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) by employing various Ansible tricks."
+msgstr ""
diff --git a/i18n/translation-templates/docs/README.pot b/i18n/translation-templates/docs/README.pot
new file mode 100644
index 000000000..bb84c68d5
--- /dev/null
+++ b/i18n/translation-templates/docs/README.pot
@@ -0,0 +1,169 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/README.md:1
+msgid "Table of Contents"
+msgstr ""
+
+#: ../../../docs/README.md:3
+msgid "⬇️ Installaton guides <!-- NOTE: the 🚀 emoji is used by \"Getting started\" on README.md -->"
+msgstr ""
+
+#: ../../../docs/README.md:5
+msgid "There are two installation guides available for beginners and advanced users."
+msgstr ""
+
+#: ../../../docs/README.md:7
+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/README.md:9
+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."
+msgstr ""
+
+#: ../../../docs/README.md:11
+msgid "[Prerequisites](prerequisites.md)"
+msgstr ""
+
+#: ../../../docs/README.md:13
+msgid "[Configuring your DNS settings](configuring-dns.md)"
+msgstr ""
+
+#: ../../../docs/README.md:15
+msgid "[Getting the playbook](getting-the-playbook.md)"
+msgstr ""
+
+#: ../../../docs/README.md:17
+msgid "[Configuring the playbook](configuring-playbook.md)"
+msgstr ""
+
+#: ../../../docs/README.md:19
+msgid "[Installing](installing.md)"
+msgstr ""
+
+#: ../../../docs/README.md:21
+msgid "🛠️ Configuration options"
+msgstr ""
+
+#: ../../../docs/README.md:28
+msgid "You can check useful documentation for configuring components here: [Configuring the playbook](configuring-playbook.md)"
+msgstr ""
+
+#: ../../../docs/README.md:30
+msgid "[Administration](configuring-playbook.md#administration) - services that help you in administrating and monitoring your Matrix installation"
+msgstr ""
+
+#: ../../../docs/README.md:32
+msgid "[Authentication and user-related](configuring-playbook.md#authentication-and-user-related) - extend and modify how users are authenticated on your homeserver"
+msgstr ""
+
+#: ../../../docs/README.md:34
+msgid "[Bots](configuring-playbook.md#bots) - bots provide various additional functionality to your installation"
+msgstr ""
+
+#: ../../../docs/README.md:36
+msgid "[Bridges](configuring-playbook.md#bridging-other-networks) - bridges can be used to connect your Matrix installation with third-party communication networks"
+msgstr ""
+
+#: ../../../docs/README.md:38
+msgid "[Clients](configuring-playbook.md#clients) - web clients for Matrix that you can host on your own domains"
+msgstr ""
+
+#: ../../../docs/README.md:40
+msgid "[Core service adjustments](configuring-playbook.md#core-service-adjustments) - backbone of your Matrix system"
+msgstr ""
+
+#: ../../../docs/README.md:42
+msgid "[File Storage](configuring-playbook.md#file-storage) - use alternative file storage to the default `media_store` folder"
+msgstr ""
+
+#: ../../../docs/README.md:46
+msgid "[Other specialized services](configuring-playbook.md#other-specialized-services) - various services that don't fit any other categories"
+msgstr ""
+
+#: ../../../docs/README.md:48
+msgid "👨‍🔧 Maintenance"
+msgstr ""
+
+#: ../../../docs/README.md:50
+msgid "If your server and services experience issues, feel free to come to [our support room](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) and ask for help."
+msgstr ""
+
+#: ../../../docs/README.md:54
+msgid "[Checking if services work](maintenance-checking-services.md)"
+msgstr ""
+
+#: ../../../docs/README.md:56
+msgid "[Maintenance and Troubleshooting](maintenance-and-troubleshooting.md)"
+msgstr ""
+
+#: ../../../docs/README.md:58
+msgid "[PostgreSQL maintenance](maintenance-postgres.md)"
+msgstr ""
+
+#: ../../../docs/README.md:60
+msgid "[Synapse maintenance](maintenance-synapse.md)"
+msgstr ""
+
+#: ../../../docs/README.md:62
+msgid "[Upgrading services](maintenance-upgrading-services.md)"
+msgstr ""
+
+#: ../../../docs/README.md:64
+msgid "Other documentation pages <!-- NOTE: this header's title and the section below need optimization -->"
+msgstr ""
+
+#: ../../../docs/README.md:66
+msgid "ℹ️ **[FAQ](faq.md)** - various Frequently Asked Questions about Matrix, with a focus on this Ansible playbook"
+msgstr ""
+
+#: ../../../docs/README.md:70
+msgid "[Alternative architectures](alternative-architectures.md)"
+msgstr ""
+
+#: ../../../docs/README.md:72
+msgid "[Container images used by the playbook](container-images.md)"
+msgstr ""
+
+#: ../../../docs/README.md:74
+msgid "[Obtaining an Access Token](obtaining-access-tokens.md)"
+msgstr ""
+
+#: ../../../docs/README.md:76
+msgid "[Playbook tags](playbook-tags.md)"
+msgstr ""
+
+#: ../../../docs/README.md:78
+msgid "[Registering users](registering-users.md)"
+msgstr ""
+
+#: ../../../docs/README.md:80
+msgid "[Running `just` commands](just.md)"
+msgstr ""
+
+#: ../../../docs/README.md:82
+msgid "[Self-building](self-building.md)"
+msgstr ""
+
+#: ../../../docs/README.md:84
+msgid "[Uninstalling](uninstalling.md)"
+msgstr ""
+
+#: ../../../docs/README.md:86
+msgid "[Updating users passwords](updating-users-passwords.md)"
+msgstr ""
diff --git a/i18n/translation-templates/docs/alternative-architectures.pot b/i18n/translation-templates/docs/alternative-architectures.pot
new file mode 100644
index 000000000..19cc7ee20
--- /dev/null
+++ b/i18n/translation-templates/docs/alternative-architectures.pot
@@ -0,0 +1,57 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/alternative-architectures.md:1
+msgid "Alternative architectures"
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:3
+msgid "As stated in the [Prerequisites](prerequisites.md), currently only `amd64` (`x86_64`) is fully supported."
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:5
+msgid "The playbook automatically determines the target server's architecture (the `matrix_architecture` variable) to be one of the following:"
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:7
+msgid "`amd64` (`x86_64`)"
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:8
+msgid "`arm32`"
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:9
+msgid "`arm64`"
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:11
+msgid "Some tools and container images can be built on the host or other measures can be used to install on that architecture."
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:13
+msgid "Implementation details"
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:15
+msgid "For `amd64`, prebuilt container images (see the [container images we use](container-images.md)) are used for all components (except [Hydrogen](configuring-playbook-client-hydrogen.md), which goes through self-building)."
+msgstr ""
+
+#: ../../../docs/alternative-architectures.md:17
+msgid "For other architecture (`arm64`, `arm32`), components which have a prebuilt image make use of it. If the component is not available for the specific architecture, [self-building](self-building.md) will be used. Not all components support self-building though, so your mileage may vary."
+msgstr ""
diff --git a/i18n/translation-templates/docs/ansible.pot b/i18n/translation-templates/docs/ansible.pot
new file mode 100644
index 000000000..5b0c6c9cd
--- /dev/null
+++ b/i18n/translation-templates/docs/ansible.pot
@@ -0,0 +1,180 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/ansible.md:2
+msgid "Running this playbook"
+msgstr ""
+
+#: ../../../docs/ansible.md:4
+msgid "This playbook is meant to be run using [Ansible](https://www.ansible.com/)."
+msgstr ""
+
+#: ../../../docs/ansible.md:6
+msgid "Ansible typically runs on your local computer and carries out tasks on a remote server. If your local computer cannot run Ansible, you can also run Ansible on some server somewhere (including the server you wish to install to)."
+msgstr ""
+
+#: ../../../docs/ansible.md:8
+msgid "Supported Ansible versions"
+msgstr ""
+
+#: ../../../docs/ansible.md:10
+msgid "To manually check which version of Ansible you're on, run: `ansible --version`."
+msgstr ""
+
+#: ../../../docs/ansible.md:12
+msgid "For the **best experience**, we recommend getting the **latest version of Ansible available**."
+msgstr ""
+
+#: ../../../docs/ansible.md:14
+msgid "We're not sure what's the minimum version of Ansible that can run this playbook successfully. The lowest version that we've confirmed (on 2022-11-26) to be working fine is: `ansible-core` (`2.11.7`) combined with `ansible` (`4.10.0`)."
+msgstr ""
+
+#: ../../../docs/ansible.md:16
+msgid "If your distro ships with an Ansible version older than this, you may run into issues. Consider [Upgrading Ansible](#upgrading-ansible) or [using Ansible via Docker](#using-ansible-via-docker)."
+msgstr ""
+
+#: ../../../docs/ansible.md:18
+msgid "Upgrading Ansible"
+msgstr ""
+
+#: ../../../docs/ansible.md:20
+msgid "Depending on your distribution, you may be able to upgrade Ansible in a few different ways:"
+msgstr ""
+
+#: ../../../docs/ansible.md:22
+msgid "by using an additional repository (PPA, etc.), which provides newer Ansible versions. See instructions for [CentOS](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-rhel-centos-or-fedora), [Debian](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-debian), or [Ubuntu](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-on-ubuntu) on the Ansible website."
+msgstr ""
+
+#: ../../../docs/ansible.md:24
+msgid "by removing the Ansible package (`yum remove ansible` or `apt-get remove ansible`) and installing via [pip](https://pip.pypa.io/en/stable/installation/) (`pip install ansible`)."
+msgstr ""
+
+#: ../../../docs/ansible.md:26
+msgid "If using the `pip` method, do note that the `ansible-playbook` binary may not be on the `$PATH` (https://linuxconfig.org/linux-path-environment-variable), but in some more special location like `/usr/local/bin/ansible-playbook`. You may need to invoke it using the full path."
+msgstr ""
+
+#: ../../../docs/ansible.md:28
+msgid "**Note**: Both of the above methods are a bad way to run system software such as Ansible. If you find yourself needing to resort to such hacks, please consider reporting a bug to your distribution and/or switching to a sane distribution, which provides up-to-date software."
+msgstr ""
+
+#: ../../../docs/ansible.md:30
+msgid "Using Ansible via Docker"
+msgstr ""
+
+#: ../../../docs/ansible.md:32
+msgid "Alternatively, you can run Ansible inside a Docker container (powered by the [devture/ansible](https://hub.docker.com/r/devture/ansible/) Docker image)."
+msgstr ""
+
+#: ../../../docs/ansible.md:34
+msgid "This ensures that you're using a very recent Ansible version, which is less likely to be incompatible with the playbook."
+msgstr ""
+
+#: ../../../docs/ansible.md:36
+msgid "You can either [run Ansible in a container on the Matrix server itself](#running-ansible-in-a-container-on-the-matrix-server-itself) or [run Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)."
+msgstr ""
+
+#: ../../../docs/ansible.md:38
+msgid "Running Ansible in a container on the Matrix server itself"
+msgstr ""
+
+#: ../../../docs/ansible.md:40
+msgid "To run Ansible in a (Docker) container on the Matrix server itself, you need to have a working Docker installation. Docker is normally installed by the playbook, so this may be a bit of a chicken and egg problem. To solve it:"
+msgstr ""
+
+#: ../../../docs/ansible.md:42
+msgid "you **either** need to install Docker manually first. Follow [the upstream instructions](https://docs.docker.com/engine/install/) for your distribution and consider setting `matrix_playbook_docker_installation_enabled: false` in your `vars.yml` file, to prevent the playbook from installing Docker"
+msgstr ""
+
+#: ../../../docs/ansible.md:43
+msgid "**or** you need to run the playbook in another way (e.g. [Running Ansible in a container on another computer (not the Matrix server)](#running-ansible-in-a-container-on-another-computer-not-the-matrix-server)) at least the first time around"
+msgstr ""
+
+#: ../../../docs/ansible.md:45
+msgid "Once you have a working Docker installation on the server, **clone the playbook** somewhere on the server and configure it as per usual (`inventory/hosts`, `inventory/host_vars/..`, etc.), as described in [configuring the playbook](configuring-playbook.md)."
+msgstr ""
+
+#: ../../../docs/ansible.md:47
+msgid "You would then need to add `ansible_connection=community.docker.nsenter` to the host line in `inventory/hosts`. This tells Ansible to connect to the \"remote\" machine by switching Linux namespaces with [nsenter](https://man7.org/linux/man-pages/man1/nsenter.1.html), instead of using SSH."
+msgstr ""
+
+#: ../../../docs/ansible.md:49
+msgid "Alternatively, you can leave your `inventory/hosts` as is and specify the connection type in **each** `ansible-playbook` call you do later, like this: `ansible-playbook --connection=community.docker.nsenter …`"
+msgstr ""
+
+#: ../../../docs/ansible.md:51
+#: ../../../docs/ansible.md:71
+msgid "Run this from the playbook's directory:"
+msgstr ""
+
+#: ../../../docs/ansible.md:63
+#: ../../../docs/ansible.md:84
+msgid "Once you execute the above command, you'll be dropped into a `/work` directory inside a Docker container. The `/work` directory contains the playbook's code."
+msgstr ""
+
+#: ../../../docs/ansible.md:65
+#: ../../../docs/ansible.md:86
+msgid "First, consider running `git config --global --add safe.directory /work` to [resolve directory ownership issues](#resolve-directory-ownership-issues)."
+msgstr ""
+
+#: ../../../docs/ansible.md:67
+msgid "Finally, you can execute `ansible-playbook …` (or `ansible-playbook --connection=community.docker.nsenter …`) commands as per normal now."
+msgstr ""
+
+#: ../../../docs/ansible.md:69
+msgid "Running Ansible in a container on another computer (not the Matrix server)"
+msgstr ""
+
+#: ../../../docs/ansible.md:82
+msgid "The above command tries to mount an SSH key (`$HOME/.ssh/id_rsa`) into the container (at `/root/.ssh/id_rsa`). If your SSH key is at a different path (not in `$HOME/.ssh/id_rsa`), adjust that part."
+msgstr ""
+
+#: ../../../docs/ansible.md:88
+msgid "Finally, you execute `ansible-playbook …` commands as per normal now."
+msgstr ""
+
+#: ../../../docs/ansible.md:90
+msgid "If you don't use SSH keys for authentication"
+msgstr ""
+
+#: ../../../docs/ansible.md:92
+msgid "If you don't use SSH keys for authentication, simply remove that whole line (`-v $HOME/.ssh/id_rsa:/root/.ssh/id_rsa:ro`)."
+msgstr ""
+
+#: ../../../docs/ansible.md:94
+msgid "To authenticate at your server using a password, you need to add a package. So, when you are in the shell of the ansible docker container (the previously used `docker run -it …` command), run:"
+msgstr ""
+
+#: ../../../docs/ansible.md:100
+msgid "Then, to be asked for the password whenever running an  `ansible-playbook` command add `--ask-pass` to the arguments of the command."
+msgstr ""
+
+#: ../../../docs/ansible.md:102
+msgid "Resolve directory ownership issues"
+msgstr ""
+
+#: ../../../docs/ansible.md:104
+msgid "Because you're `root` in the container running Ansible and this likely differs fom the owner (your regular user account) of the playbook directory outside of the container, certain playbook features which use `git` locally may report warnings such as:"
+msgstr ""
+
+#: ../../../docs/ansible.md:106
+msgid "fatal: unsafe repository ('/work' is owned by someone else) To add an exception for this directory, call:  git config --global --add safe.directory /work"
+msgstr ""
+
+#: ../../../docs/ansible.md:110
+msgid "These errors can be resolved by making `git` trust the playbook directory by running `git config --global --add safe.directory /work`"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-captcha.pot b/i18n/translation-templates/docs/configuring-captcha.pot
new file mode 100644
index 000000000..7d6161f3d
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-captcha.pot
@@ -0,0 +1,75 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-captcha.md:1
+msgid "(Adapted from the [upstream project](https://github.com/element-hq/synapse/blob/develop/docs/CAPTCHA_SETUP.md))"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:3
+msgid "Overview"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:5
+msgid "Captcha can be enabled for this home server. This file explains how to do that."
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:7
+msgid "The captcha mechanism used is Google's [ReCaptcha](https://www.google.com/recaptcha/). This requires API keys from Google. If your homeserver is Dendrite then [hCapcha](https://www.hcaptcha.com) can be used instead."
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:9
+msgid "ReCaptcha"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:11
+#: ../../../docs/configuring-captcha.md:37
+msgid "Getting keys"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:13
+#: ../../../docs/configuring-captcha.md:39
+msgid "Requires a site/secret key pair from:"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:15
+msgid "<http://www.google.com/recaptcha/admin>"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:17
+msgid "Must be a reCAPTCHA **v2** key using the \"I'm not a robot\" Checkbox option"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:19
+msgid "Setting ReCaptcha keys"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:21
+msgid "Once registered as above, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:35
+msgid "hCaptcha"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:41
+msgid "<https://dashboard.hcaptcha.com/sites/new>"
+msgstr ""
+
+#: ../../../docs/configuring-captcha.md:43
+msgid "Setting hCaptcha keys"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-dns.pot b/i18n/translation-templates/docs/configuring-dns.pot
new file mode 100644
index 000000000..d46acdb00
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-dns.pot
@@ -0,0 +1,341 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-dns.md:1
+msgid "Configuring your DNS settings"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:3
+msgid "<sup>[Prerequisites](prerequisites.md) > Configuring your DNS settings > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)</sup>"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:5
+msgid "To set up Matrix on your domain, you'd need to do some DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:7
+msgid "DNS setting for server delegation (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:9
+msgid "In the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:11
+msgid "To use such an ID, you don't need to install anything on the actual `example.com` server. Instead, you need to instruct the Matrix network that Matrix services for `example.com` are redirected over to `matrix.example.com`. This redirection is also known as \"delegation\"."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:13
+msgid "As we discuss in [Server Delegation](howto-server-delegation.md), server delegation can be configured in either of these ways:"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:15
+msgid "Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:16
+msgid "Setting up a `_matrix._tcp` DNS SRV record"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:18
+msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file, instead of using a DNS SRV record."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:20
+msgid "If you choose the recommended method (file-based delegation), you do not need to configure the DNS record to enable server delegation. You will need to add a necessary configuration later, when you [finalize the installation](installing.md#finalize-the-installation) after installing and starting Matrix services."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:22
+msgid "On the other hand, if you choose this method (setting up a DNS SRV record), you need to configure the additional DNS record as well as adjust SSL certificate handling. Take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:24
+msgid "DNS settings for services enabled by default"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:26
+msgid "To serve the base domain (`example.com`) and [Element Web](configuring-playbook-client-element-web.md) with the default subdomain, adjust DNS records as below."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "Type"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "Host"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "Priority"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "Weight"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "Port"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "Target"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "A"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`matrix`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "-"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`matrix-server-IP`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "CNAME"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`element`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`matrix.example.com`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:33
+msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:35
+msgid "The `element.example.com` subdomain is necessary, because this playbook installs the [Element Web](https://github.com/element-hq/element-web) client for you by default. If you'd rather instruct the playbook not to install Element Web (`matrix_client_element_enabled: false` when [Configuring the playbook](configuring-playbook.md) later), feel free to skip the `element.example.com` DNS record."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:37
+msgid "Be mindful as to how long it will take for the DNS records to propagate."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:39
+msgid "If you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\". Otherwise, fetching certificates will fail."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:41
+msgid "DNS settings for optional services/features"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:43
+msgid "For other services which may need subdomain settings, see the table below and configure the DNS (`CNAME`) records accordingly."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "Used by component"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "[Dimension](configuring-playbook-dimension.md) integration server"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`dimension`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "[Jitsi](configuring-playbook-jitsi.md) video-conferencing platform"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`jitsi`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "[Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) monitoring system"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`stats`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "[Go-NEB](configuring-playbook-bot-go-neb.md) bot"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`goneb`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "[Sygnal](configuring-playbook-sygnal.md) push notification gateway"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`sygnal`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "[ntfy](configuring-playbook-ntfy.md) push notifications server"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`ntfy`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "[Etherpad](configuring-playbook-etherpad.md) collaborative text editor"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`etherpad`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "[Hydrogen](configuring-playbook-client-hydrogen.md) web client"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`hydrogen`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "[Cinny](configuring-playbook-client-cinny.md) web client"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`cinny`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md) client"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`schildichat`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "[wsproxy](configuring-playbook-bridge-mautrix-wsproxy.md) sms bridge"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`wsproxy`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "[Buscarron](configuring-playbook-bot-buscarron.md) helpdesk bot"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`buscarron`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "[rageshake](configuring-playbook-rageshake.md) bug report server"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`rageshake`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "[ma1sd](configuring-playbook-ma1sd.md) identity server"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "SRV"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`_matrix-identity._tcp`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "10"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "0"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "443"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md)/[Email2Matrix](configuring-playbook-email2matrix.md) email bridges"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "MX"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md) email bridge"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "TXT"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`v=spf1 ip4:matrix-server-IP -all`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`_dmarc.matrix`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`v=DMARC1; p=quarantine;`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "`postmoogle._domainkey.matrix`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:0
+msgid "get it from `!pm dkim`"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:66
+msgid "SRV record for ma1sd"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:68
+msgid "To make ma1sd enable its federation features, you need to set up a `_matrix-identity._tcp` SRV record. Don't confuse this with the `_matrix._tcp` SRV record for server delegation. See the table above and [this section](configuring-playbook-ma1sd.md#adjusting-dns-records) for values which need to be specified."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:70
+msgid "When setting up a SRV record, if you are asked for a service and protocol instead of a hostname split the host value from the table where the period is. For example use service as `_matrix-identity` and protocol as `_tcp`."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:72
+msgid "MX and TXT records for Postmoogle"
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:74
+msgid "To make Postmoogle enable its email sending features, you need to configure MX and TXT (SPF, DMARC, and DKIM) records. See the table above for values which need to be specified."
+msgstr ""
+
+#: ../../../docs/configuring-dns.md:78
+msgid "[▶️](getting-the-playbook.md) When you're done with the DNS configuration and ready to proceed, continue with [Getting the playbook](getting-the-playbook.md)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot b/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot
new file mode 100644
index 000000000..824ef02d4
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-alertmanager-receiver.pot
@@ -0,0 +1,165 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-alertmanager-receiver.md:1
+msgid "Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:3
+msgid "The playbook can install and configure the [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver) service for you. It's a [client](https://prometheus.io/docs/alerting/latest/clients/) for Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/), allowing you to deliver alerts to Matrix rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:5
+msgid "See the project's [documentation](https://github.com/metio/matrix-alertmanager-receiver/blob/main/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:7
+msgid "This service is meant to be used with an external [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) instance. It's **not** meant to be integrated with the [Prometheus & Grafana stack](./configuring-playbook-prometheus-grafana.md) installed by this playbook, because the Alertmanager component is not installed by it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:11
+msgid "Register the bot account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:13
+msgid "This service uses a bot (with a username specified in `matrix_alertmanager_receiver_config_matrix_user_id_localpart`) for delivering messages."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:15
+msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:17
+msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:19
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:25
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:27
+msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:29
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:31
+msgid "Join to rooms as the bot manually"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:33
+msgid "ℹ️ **This bot does not accept room invitations automatically**. To deliver messages to rooms, the bot must be joined to all rooms manually."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:35
+msgid "For each new room you would like the bot to deliver alerts to, invite the bot to the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:37
+msgid "Then, log in as the bot using any Matrix client of your choosing, accept the room invitation from the bot's account, and log out."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:39
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:41
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:62
+msgid "See `roles/custom/matrix-alertmanager-receiver/defaults/main.yml` for additional configuration variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:64
+msgid "Adjusting the matrix-alertmanager-receiver URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:66
+msgid "By default, this playbook installs matrix-alertmanager-receiver on the `matrix.` subdomain, at the `/matrix-alertmanager-receiver` path (https://matrix.example.com/matrix-alertmanager-receiver). 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-alertmanager-receiver.md:68
+msgid "By tweaking the `matrix_alertmanager_receiver_hostname` and `matrix_alertmanager_receiver_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-alertmanager-receiver.md:70
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:78
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:80
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-alertmanager-receiver domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:82
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:84
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:86
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:88
+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-alertmanager-receiver.md:95
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:97
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:99
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:101
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:103
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:105
+msgid "Configure your Prometheus Alertmanager with configuration like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-alertmanager-receiver.md:124
+msgid "where `URL_HERE` looks like `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/some-room-name` or `https://matrix.example.com/matrix-alertmanager-receiver-RANDOM_VALUE_HERE/alert/!qporfwt:example.com`."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-appservice-double-puppet.pot b/i18n/translation-templates/docs/configuring-playbook-appservice-double-puppet.pot
new file mode 100644
index 000000000..07218f273
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-appservice-double-puppet.pot
@@ -0,0 +1,73 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-appservice-double-puppet.md:1
+msgid "Setting up Appservice Double Puppet (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:3
+msgid "Appservice Double Puppet is a homeserver appservice through which bridges (and potentially other services) can impersonate any user on the homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:5
+msgid "This is useful for performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) via the [appservice method](https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method-new). The Appservice Double Puppet service is an implementation of this approach."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:7
+msgid "Previously, bridges supported performing [double-puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) with the help of the [Shared Secret Auth password provider module](./configuring-playbook-shared-secret-auth.md), but this old and hacky solution has been superseded by this Appservice Double Puppet method."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:11
+msgid "To enable the Appservice Double Puppet service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:17
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:19
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:26
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:28
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:30
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:32
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:34
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-double-puppet.md:36
+msgid "When enabled, double puppeting will automatically be enabled for all bridges that support double puppeting via the appservice method."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-appservice-draupnir-for-all.pot b/i18n/translation-templates/docs/configuring-playbook-appservice-draupnir-for-all.pot
new file mode 100644
index 000000000..5b480cc69
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-appservice-draupnir-for-all.pot
@@ -0,0 +1,190 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 09:53+0200\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-appservice-draupnir-for-all.md:1
+msgid "Setting up Draupnir for All/D4A (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:3
+msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool for you in appservice mode."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:5
+msgid "Appservice mode can be used together with the regular [Draupnir bot](configuring-playbook-bot-draupnir.md) or independently. Details about the differences between the 2 modes are described below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:7
+msgid "Draupnir Appservice mode compared to Draupnir bot mode"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:9
+msgid "The administrative functions for managing the appservice are alpha quality and very limited. However, the experience of using an appservice-provisioned Draupnir is on par with the experience of using Draupnir from bot mode except in the case of avatar customisation as described later on in this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:11
+msgid "Draupnir for all is the way to go if you need more than 1 Draupnir instance, but you don't need access to Synapse Admin features as they are not accessible through Draupnir for All (Even though the commands do show up in help)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:13
+msgid "Draupnir for all in the playbook is rate-limit-exempt automatically as its appservice configuration file does not specify any rate limits."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:15
+msgid "Normal Draupnir does come with the benefit of access to Synapse Admin features. You are also able to more easily customise your normal Draupnir than D4A as D4A even on the branch with the Avatar command (To be Upstreamed to Mainline Draupnir) that command is clunky as it requires the use of things like Element Web devtools. In normal Draupnir this is a quick operation where you login to Draupnir with a normal client and set Avatar and Display name normally."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:17
+msgid "Draupnir for all does not support external tooling like [MRU](https://mru.rory.gay) as it can't access Draupnir's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:19
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:21
+msgid "Create a main management room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:23
+msgid "The playbook does not create a management room for your Main Draupnir. You **need to create the room manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:25
+msgid "Note that the room must be unencrypted."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:29
+msgid "The management room has to be given an alias and be public when you are setting up the bot for the first time as the bot does not differentiate between invites and invites to the management room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:31
+msgid "This management room is used to control who has access to your D4A deployment. The room stores this data inside of the control room state so your bot must have sufficient powerlevel to send custom state events. This is default 50 or moderator as Element clients call this powerlevel."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:33
+msgid "As noted in the Draupnir install instructions the control room is sensitive. **Anyone in this room can control the bot so it is important that you only invite trusted users to this room.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:35
+msgid "Set an alias to the management room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:37
+msgid "Next, set an alias to the management room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:39
+msgid "This alias can be anything you want. However, for increased security during the setup phase, it is recommended to make this alias be a random string. When it has been locked down after setup phase, you can give your room a secondary human readable alias."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:41
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:43
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ALIAS_HERE`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:51
+msgid "Extending the configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:53
+msgid "You can configure additional options by adding the `matrix_appservice_draupnir_for_all_extension_yaml` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:55
+msgid "For example, to change Draupnir's `protectAllJoinedRooms` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:69
+msgid "You can refer to the upstream [documentation](https://github.com/the-draupnir-project/Draupnir) for more configuration documentation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:71
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:86
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:73
+msgid "The playbook ships a full copy of the example config that does transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in the template directory of the role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:75
+msgid "Config extension does not affect the appservices config as this config is not extensible in current Draupnir anyway. It instead touches the config passed to the Draupnirs that your Appservice creates. So the example above (`protectAllJoinedRooms: true`) makes all provisioned Draupnirs protect all joined rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:77
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:79
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:88
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:90
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:92
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:94
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:96
+msgid "If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com` you have succesfully installed Draupnir for All and can now start using it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:98
+msgid "The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot mode."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:100
+msgid "Granting Users the ability to use D4A"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:102
+msgid "Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recomendation. Using the chat is recomended."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:104
+msgid "The bot requires a powerlevel of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:106
+msgid "To allow users or whole homeservers you type /plain @draupnir-main:example.com allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:108
+msgid "How to provision a D4A once you are allowed to"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:110
+msgid "To provision a D4A, you need to start a chat with `@draupnir-main:example.com`. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:112
+msgid "Congratulations if you made it all the way here because you now have a fully working Draupnir for all deployment."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-backup-borg.pot b/i18n/translation-templates/docs/configuring-playbook-backup-borg.pot
new file mode 100644
index 000000000..e99b346ad
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-backup-borg.pot
@@ -0,0 +1,137 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-22 17:53+0900\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-backup-borg.md:1
+msgid "Setting up BorgBackup (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:3
+msgid "The playbook can install and configure [BorgBackup](https://www.borgbackup.org/) (short: Borg) with [borgmatic](https://torsion.org/borgmatic/) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:5
+msgid "BorgBackup is a deduplicating backup program with optional compression and encryption. That means your daily incremental backups can be stored in a fraction of the space and is safe whether you store it at home or on a cloud service."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:7
+msgid "You will need a remote server where BorgBackup will store the backups. There are hosted, BorgBackup compatible solutions available, such as [BorgBase](https://www.borgbase.com)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:9
+msgid "The backup will run based on `backup_borg_schedule` var (systemd timer calendar), default: 4am every day."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:11
+msgid "By default, if you're using the integrated Postgres database server (as opposed to [an external Postgres server](configuring-playbook-external-postgres.md)), backups with BorgBackup will also include dumps of your Postgres database. An alternative solution for backing up the Postgres database is [postgres backup](configuring-playbook-postgres-backup.md). If you decide to go with another solution, you can disable Postgres-backup support for BorgBackup using the `backup_borg_postgresql_enabled` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:13
+msgid "**Note**: the component is not managed by this repository but its [own repository](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:15
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:17
+msgid "If you do not disable Postgres-backup support, make sure that the Postgres version of your homeserver's database is compatible with borgmatic."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:19
+msgid "Create a new SSH key:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:25
+msgid "This can be done on any machine and you don't need to place the key in the `.ssh` folder. It will be added to the Ansible config later."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:27
+msgid "Add the **public** part of this SSH key (the `matrix-borg-backup.pub` file) to your BorgBackup provider/server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:29
+msgid "If you plan to use a hosted solution, follow their instructions. If you have your own server, copy the key over:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:39
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:41
+msgid "Minimal working configuration (`inventory/host_vars/matrix.example.com/vars.yml`) to enable BorgBackup:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:58
+msgid "where:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:60
+msgid "USER - SSH user of a provider/server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:61
+msgid "HOST - SSH host of a provider/server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:62
+msgid "REPO - BorgBackup repository name, it will be initialized on backup start, eg: `matrix`, regarding Syntax see [Remote repositories](https://borgbackup.readthedocs.io/en/stable/usage/general.html#repository-urls)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:63
+msgid "PASSPHRASE - passphrase used for encrypting backups. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:64
+msgid "PRIVATE KEY - the content of the **private** part of the SSH key you created before. The whole key (all of its belonging lines) under `backup_borg_ssh_key_private` needs to be indented with 2 spaces"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:66
+msgid "To backup without encryption, add `backup_borg_encryption: 'none'` to your vars. This will also enable the `backup_borg_unknown_unencrypted_repo_access_is_ok` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:68
+msgid "`backup_borg_location_source_directories` defines the list of directories to back up: it's set to `{{ matrix_base_data_path }}` by default, which is the base directory for every service's data, such as Synapse, Postgres and the bridges. You might want to exclude certain directories or file patterns from the backup using the `backup_borg_location_exclude_patterns` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:70
+msgid "Check the [backup_borg role](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg)'s [defaults/main.yml](https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg/blob/main/defaults/main.yml) file for the full list of available options."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:72
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:74
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:81
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:83
+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-backup-borg.md:85
+msgid "Manually start a backup"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-backup-borg.md:87
+msgid "For testing your setup it can be helpful to not wait until 4am. If you want to run the backup immediately, log onto the server and run `systemctl start matrix-backup-borg`. This will not return until the backup is done, so possibly a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-base-domain-serving.pot b/i18n/translation-templates/docs/configuring-playbook-base-domain-serving.pot
new file mode 100644
index 000000000..3fb9115c7
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-base-domain-serving.pot
@@ -0,0 +1,157 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-base-domain-serving.md:1
+msgid "Serving the base domain (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:3
+msgid "By default, this playbook sets up services on your Matrix server (`matrix.example.com`), but has it configured so that it presents itself as the base domain (`example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:5
+msgid "As we discuss in [Server Delegation](howto-server-delegation.md), server delegation / redirection can be configured in either of these ways:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:7
+msgid "Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:8
+msgid "Setting up a `_matrix._tcp` DNS SRV record"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:10
+msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:12
+msgid "However, those who don't have a separate server to dedicate to the base domain have trouble arranging this."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:14
+msgid "Usually, there are 2 options:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:16
+msgid "either get a separate server for the base domain, just for serving the files necessary for [Server Delegation via a well-known file](howto-server-delegation.md#server-delegation-via-a-well-known-file)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:18
+msgid "or, arrange for the Matrix server to serve the base domain. This either involves you [using your own webserver](configuring-playbook-own-webserver.md) or making the integrated webserver serve the base domain for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:20
+msgid "This documentation page tells you how to do the latter. With some easy changes, we make it possible to serve the base domain from the Matrix server via the integrated webserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:22
+msgid "Just [**adjust your DNS records**](configuring-dns.md), so that your base domain is pointed to the Matrix server's IP address (using a DNS `A` record) **and then add the following configuration** to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:28
+msgid "Doing this, the playbook will:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:30
+msgid "obtain an SSL certificate for the base domain, just like it does for all other domains (see [how we handle SSL certificates](configuring-playbook-ssl-certificates.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:32
+msgid "serve the `/.well-known/matrix/*` files which are necessary for [Federation Server Discovery](configuring-well-known.md#federation-server-discovery) (also see [Server Delegation](howto-server-delegation.md)) and [Client-Server discovery](configuring-well-known.md#client-server-discovery)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:34
+msgid "serve a simple homepage at `https://example.com` with content `Hello from example.com` (configurable via the `matrix_static_files_file_index_html_template` variable). You can also [serve a more complicated static website](#serving-a-static-website-at-the-base-domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:36
+msgid "Serving a static website at the base domain"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:38
+msgid "By default, when \"serving the base domain\" is enabled, the playbook hosts a simple `index.html` webpage at `/matrix/static-files/public/index.html`. The content of this page is taken from the `matrix_static_files_file_index_html_template` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:40
+msgid "If you'd like to host your own static website (more than a single `index.html` page) at the base domain, you can disable the creation of this default `index.html` page like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:54
+msgid "With this configuration, Ansible will no longer mess around with the `/matrix/static-files/public/index.html` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:56
+msgid "You are then free to upload any static website files to `/matrix/static-files/public` and they will get served at the base domain. You can do so manually or by using the [ansible-role-aux](https://github.com/mother-of-all-self-hosting/ansible-role-aux) Ansible role, which is part of this playbook already."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:58
+msgid "Serving a more complicated website at the base domain"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:60
+msgid "If you'd like to serve an even more complicated (dynamic) website from the Matrix server, relying on the playbook to serve the base domain is not the best choice."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:62
+msgid "You have 2 options."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:64
+msgid "**One way is to host your base domain elsewhere**. This involves:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:65
+msgid "you stopping to serve it from the Matrix server: remove `matrix_static_files_container_labels_base_domain_enabled` from your configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:66
+msgid "[configuring Matrix Delegation via well-known](./configuring-well-known.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:68
+msgid "**Another way is to serve the base domain from another (your own) container on the Matrix server**. This involves:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:69
+msgid "telling the playbook to only serve `example.com/.well-known/matrix` files by adjusting your `vars.yml` configuration like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:70
+msgid "keep `matrix_static_files_container_labels_base_domain_enabled: true`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:71
+msgid "add an extra: `matrix_static_files_container_labels_base_domain_traefik_path_prefix: /.well-known/matrix`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:72
+msgid "building and running a new container on the Matrix server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:73
+msgid "it should be connected to the `traefik` network, so that Traefik can reverse-proxy to it"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:74
+msgid "it should have appropriate [container labels](https://docs.docker.com/config/labels-custom-metadata/), which instruct Traefik to reverse-proxy to it"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-base-domain-serving.md:76
+msgid "How you'll be managing building and running this container is up-to-you. You may use of the primitives from [ansible-role-aux](https://github.com/mother-of-all-self-hosting/ansible-role-aux) Ansible role to organize it yourself, or you can set it up in another way."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot
new file mode 100644
index 000000000..6da583653
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bot-baibot.pot
@@ -0,0 +1,424 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-23 13:09+0900\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-bot-baibot.md:1
+msgid "Setting up baibot (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:8
+msgid "🤖 [baibot](https://github.com/etkecc/baibot) (pronounced bye-bot) is a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:10
+msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as many well as other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:12
+msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to [matrix-chatgpt-bot](./configuring-playbook-bot-chatgpt.md). See the [baibot](https://github.com/etkecc/baibot) project and its documentation for more information."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:14
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:16
+msgid "API access to one or more LLM [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:18
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:20
+msgid "There are **a lot of configuration options** (some required, some possibly required, some optional), so they're **split into multiple sections below**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:23
+msgid "[Base configuration](#base-configuration)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:24
+msgid "[👮‍♂️ Administrator configuration](#️-administrator-configuration)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:25
+msgid "[👥 Initial users configuration](#-initial-users-configuration)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:26
+msgid "[🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:27
+msgid "[🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:29
+msgid "Depending on your current `vars.yml` file and desired configuration, **you may require more than just the [base configuration](#base-configuration)**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:31
+msgid "Base configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:33
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:71
+msgid "As mentioned above, **this may not be enough**. Continue with the configuration sections below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:73
+msgid "👮‍♂️ Administrator configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:75
+#: ../../../docs/configuring-playbook-bot-baibot.md:99
+msgid "This is an addition to the [base configuration](#base-configuration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:77
+msgid "To specify who is considered a bot [👮‍♂️ Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators), you either need to specify `matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The latter is a single variable which affects all bridges and bots."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:79
+msgid "If `matrix_admin` is already configured in your `vars.yml` configuration, you can skip this section."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:81
+#: ../../../docs/configuring-playbook-bot-baibot.md:110
+msgid "**If necessary**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:95
+msgid "👥 Initial users configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:97
+msgid "By default, **all users on your homeserver are considered allowed users**. If that's OK, you can skip this section."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:101
+msgid "To specify who is considered a bot [👥 User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), you may:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:103
+msgid "define an **initial** value for `matrix_bot_baibot_config_initial_global_config_user_patterns` Ansible variable, as shown below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:104
+msgid "configure the list at runtime via the bot's `!bai access set-users SPACE_SEPARATED_PATTERNS` command"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:106
+msgid "Configuring `matrix_bot_baibot_config_initial_global_config_user_patterns` is optional, but it can be useful to pre-configure the bot with a list of users who should have access to the bot's features."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:108
+msgid "**Note**: Once initially configured, the allowed users list **cannot be managed via Ansible anymore**. It can only be managed subsequently via bot commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:122
+msgid "🤖 Configuring agents via Ansible"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:124
+msgid "You are **not required** to define agents [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration) via Ansible. **To get started quickly**, you can **skip this section and define agents at runtime via chat commands** (following the bot's guidance)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:126
+msgid "Privileged users (like the [👮‍♂️ Administrator](#️-administrator-configuration), but potentially others too - see the upstream [🔒 access](https://github.com/etkecc/baibot/blob/main/docs/access.md) documentation) can **define agents dynamically at any time** via chat commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:128
+msgid "The Ansible role includes preset variables for easily enabling some [🤖 agents](https://github.com/etkecc/baibot/blob/main/docs/agents.md) on various [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md) (e.g. OpenAI, etc)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:130
+msgid "Besides the presets, the Ansible role also includes support for configuring additional statically-defined agents via the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:132
+msgid "Agents defined statically and those created dynamically (via chat) are named differently, so **conflict cannot arise**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:134
+msgid "Depending on your propensity for [GitOps](https://en.wikipedia.org/wiki/DevOps#GitOps), you may prefer to define agents statically via Ansible, or you may wish to do it dynamically via chat."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:136
+msgid "Before proceeding, we recommend reading the upstream documentation on [How to choose a provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#how-to-choose-a-provider). In short, it's probably best to go with [OpenAI](#openai)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:138
+msgid "Anthropic"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:140
+msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Anthropic provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic) with the help of the playbook's preset variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:142
+#: ../../../docs/configuring-playbook-bot-baibot.md:168
+#: ../../../docs/configuring-playbook-bot-baibot.md:201
+#: ../../../docs/configuring-playbook-bot-baibot.md:231
+msgid "Here's an example **addition** to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:160
+#: ../../../docs/configuring-playbook-bot-baibot.md:193
+#: ../../../docs/configuring-playbook-bot-baibot.md:221
+#: ../../../docs/configuring-playbook-bot-baibot.md:251
+msgid "If you'd like to use more than one model, take a look at the [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:162
+#: ../../../docs/configuring-playbook-bot-baibot.md:195
+#: ../../../docs/configuring-playbook-bot-baibot.md:223
+#: ../../../docs/configuring-playbook-bot-baibot.md:253
+msgid "💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:164
+msgid "Groq"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:166
+msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Groq provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq) with the help of the playbook's preset variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:191
+msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/groq`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:197
+msgid "Mistral"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:199
+msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [🇫🇷 Mistral provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral) with the help of the playbook's preset variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:219
+msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/mistral`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:225
+msgid "OpenAI"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:227
+msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai) with the help of the playbook's preset variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:229
+msgid "The OpenAI provider is **only meant to be used with OpenAI's official API** and compatibility with other services (which do not fully adhere to the OpenAI API spec completely) is limited. **If you're targeting an OpenAI-compatible service**, use the [OpenAI Compatible](#openai-compatible) provider instead."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:249
+msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/openai`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:255
+msgid "OpenAI Compatible"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:257
+msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI Compatible provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai-compatible) with the help of the playbook's preset variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:259
+msgid "This provider allows you to use OpenAI-compatible API services like [OpenRouter](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openrouter), [Together AI](https://github.com/etkecc/baibot/blob/main/docs/providers.md#together-ai), etc."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:261
+msgid "Some of these popular services already have **shortcut** providers (see [supported providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md#supported-providers) leading to this one behind the scenes - this make it easier to get started."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:263
+msgid "As of this moment, the playbook does not include presets for any of these services, so you'll need to [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:265
+msgid "Configuring additional agents (without a preset)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:267
+msgid "The Ansible role may be lacking preset variables for some [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), or you may wish to statically-define an agent on the same provider twice (or more) with different configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:269
+msgid "It's possible to inject your own agent configuration using the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:271
+msgid "You can also define providers at runtime, by chatting with the bot, so using Ansible is not a requirement."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:273
+msgid "Below is an an **example** demonstrating **statically-defining agents via Ansible without using presets**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:312
+msgid "Because these are [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agents, they will be given a `static/` ID prefix and will be named `static/my-openai-gpt-3.5-turbo-agent` and `static/my-ollama-agent`, respectively."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:314
+msgid "💡 To figure out what to put in the `config` section, refer to the [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md) page, which contains **sample configuration YAML for each provider**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:316
+msgid "As with any [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), defining them means they exist. To actually make use of them, they need to be configured as handlers globally or in a specific room - see [Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:318
+msgid "💡 You may also wish to use these new agents for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:320
+msgid "🤝 Configuring initial default handlers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:322
+msgid "This section is only useful if you're [🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible), as it lets you put these agents to use as soon as the bot starts (by adjusting the bot's **initial global configuration**)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:324
+msgid "If you're not configuring agents via Ansible, you can skip this section."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:326
+msgid "This section is only useful the first time around. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:328
+msgid "baibot supports [various purposes](https://github.com/etkecc/baibot/blob/main/docs/features.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:330
+msgid "[💬 text-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-generation): communicating with you via text"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:332
+msgid "[🦻 speech-to-text](https://github.com/etkecc/baibot/blob/main/docs/features.md#-speech-to-text): turning your voice messages into text"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:334
+msgid "[🗣️ text-to-speech](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-to-speech): turning bot or users text messages into voice messages"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:336
+msgid "[🖌️ image-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-image-generation): generating images based on instructions"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:338
+msgid "❓ catch-all: special purposes, indicating use as a fallback (when no specific handler is configured)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:340
+msgid "[Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models) is made possible by the bot's ability to have different [🤝 handlers](https://github.com/etkecc/baibot/blob/main/docs/configuration/handlers.md) configured for different purposes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:342
+msgid "This configuration can be done as a global fallback, or per-room. Both of these [🛠️ configurations](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md) are managed at runtime (viat chat), but **the global configuration can have some initial defaults configured via Ansible**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:344
+msgid "You can configure the **initial values** for these via Ansible, via the `matrix_bot_baibot_config_initial_global_config_handler_*` variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:346
+msgid "Example **additional** `vars.yml` configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:363
+msgid "**Note**: these are initial defaults for the bot's global configuration. As such, changing any of these values subsequently has no effect on the bot's behavior. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:365
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:367
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:374
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:376
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:378
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:380
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:382
+msgid "If you change the bot password (`matrix_bot_baibot_config_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:384
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:386
+msgid "To use the bot, invite it to any existing Matrix room (`/invite @baibot:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:388
+msgid "If you're an allowed bot [👥 user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) (see [👥 Initial users configuration](#-initial-users-configuration)), the bot will accept your invitation and join the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:390
+msgid "After joining, the bot will introduce itself and show information about the [✨ features](https://github.com/etkecc/baibot/blob/main/docs/features.md) that are enabled for it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:392
+msgid "If you've [🤖 configured one or more agents via Ansible](#-configuring-agents-via-ansible) and have [🤝 configured initial default handlers](#configuring-initial-default-handlers), the bot will immediately be able to make use of these agents for this new room. Otherwise, you will need to configure agents and/or handlers via chat commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:394
+msgid "Send `!bai help` to the bot in the room to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:396
+msgid "You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) project's documentation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:398
+msgid "Debugging"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:400
+msgid "As with all other services, you can find service logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-bot-baibot`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:402
+msgid "The default logging level for this service is `info`, but you can increase it to `debug` (or even `trace`) with the following additional configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-baibot.md:416
+msgid "**Alternatively**, you can use a single variable to set the logging level for all of the above (bot + all libraries):"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-buscarron.pot b/i18n/translation-templates/docs/configuring-playbook-bot-buscarron.pot
new file mode 100644
index 000000000..1e36161dc
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bot-buscarron.pot
@@ -0,0 +1,137 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-23 13:09+0900\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-bot-buscarron.md:1
+msgid "Setting up Buscarron (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:3
+msgid "The playbook can install and configure [Buscarron](https://github.com/etkecc/buscarron) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:5
+msgid "Buscarron is bot that receives HTTP POST submissions of web forms and forwards them to a Matrix room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:9
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:32
+msgid "Adjusting the Buscarron URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:34
+msgid "By default, this playbook installs Buscarron on the `buscarron.` subdomain (`buscarron.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:36
+msgid "By tweaking the `matrix_bot_buscarron_hostname` and `matrix_bot_buscarron_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-bot-buscarron.md:38
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:49
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:51
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Buscarron domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:53
+msgid "By default, you will need to create a CNAME record for `buscarron`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:55
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:57
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:59
+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-bot-buscarron.md:66
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:68
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:70
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:72
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:74
+msgid "If you change the bot password (`matrix_bot_buscarron_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:76
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:78
+msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.buscarron:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:80
+msgid "After the bot joins the room, anyone can call the web form via HTTP POST method."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:82
+msgid "Here is an example for the `contact` form:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:90
+msgid "**Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:92
+msgid "you hit the homepage (HTTP `GET` request to `/`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:93
+msgid "you submit a form to the wrong URL (`POST` request to `/non-existing-form`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:94
+msgid "`hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:96
+msgid "If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-buscarron.md:98
+msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/buscarron)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot b/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot
new file mode 100644
index 000000000..bd944f467
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bot-chatgpt.pot
@@ -0,0 +1,125 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bot-chatgpt.md:1
+msgid "Setting up matrix-bot-chatgpt (optional, unmaintained)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:3
+msgid "**Note**: [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) is now an archived (**unmaintained**) project. Talking to ChatGPT (and many other LLM providers) can happen via the much more featureful [baibot](https://github.com/etkecc/baibot), which can be installed using [this playbook](configuring-playbook-bot-baibot.md). Consider using that bot instead of this one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:5
+msgid "The playbook can install and configure [matrix-chatgpt-bot](https://github.com/matrixgpt/matrix-chatgpt-bot) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:7
+msgid "Talk to [ChatGPT](https://openai.com/blog/chatgpt/) via your favourite Matrix client!"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:11
+msgid "Obtain an OpenAI API key"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:13
+msgid "To use the bot, you'd need to obtain an API key from [https://platform.openai.com/account/api-keys](https://platform.openai.com/account/api-keys)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:15
+msgid "Register the bot account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:17
+msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:19
+msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:21
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:27
+msgid "Obtain an access token and create encryption keys"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:29
+msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:31
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:33
+msgid "To make sure the bot can read encrypted messages, it will need an encryption key, just like any other new user. While obtaining the access token, follow the prompts to setup a backup key. More information can be found in the [Element documentation](https://element.io/help#encryption6)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:35
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:37
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `API_KEY_HERE` with the API key retrieved [here](#obtain-an-openai-api-key) and `ACCESS_TOKEN_HERE` with the access token created [here](#obtain-an-access-token-and-create-encryption-keys), respectively."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:54
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:56
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:63
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:65
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:67
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:69
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:71
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:73
+msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.chatgpt:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:75
+msgid "After the bot joins the room, you can send a message to it. When you do so, use the prefix if you configured it or mention the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-chatgpt.md:77
+msgid "You can also refer to the upstream [documentation](https://github.com/matrixgpt/matrix-chatgpt-bot)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot b/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot
new file mode 100644
index 000000000..952063e39
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot
@@ -0,0 +1,381 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bot-draupnir.md:1
+msgid "Setting up Draupnir (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:3
+msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation bot for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:5
+msgid "See the project's [documentation](https://github.com/the-draupnir-project/Draupnir/blob/main/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:7
+msgid "This documentation page is about installing Draupnir in bot mode. As an alternative, you can run a multi-instance Draupnir deployment by installing [Draupnir in appservice mode](./configuring-playbook-appservice-draupnir-for-all.md) (called Draupnir-for-all) instead."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:9
+msgid "If your migrating from Mjolnir skip to [this section](#migrating-from-mjolnir-only-required-if-migrating)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:13
+msgid "Register the bot account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:15
+msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:17
+msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:19
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:25
+msgid "If you would like Draupnir to be able to deactivate users, move aliases, shutdown rooms, show abuse reports (see [below](#abuse-reports)), etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:27
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:29
+msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:31
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:33
+msgid "Make sure the account is free from rate limiting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:35
+msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Draupnir will crash.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:37
+msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:39
+msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:45
+msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. 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-bot-draupnir.md:47
+msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:49
+msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.draupnir:example.com` with the MXID of your Draupnir:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:55
+msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Draupnir itself. If you have made Draupnir an admin, you can just use the Draupnir token."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:57
+msgid "Create a management room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:59
+msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:61
+msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:63
+msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:65
+msgid "Finally invite the `@bot.draupnir:example.com` account you created earlier into the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:67
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:69
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:78
+msgid "End-to-End Encryption support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:80
+msgid "Decide whether you want Draupnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:82
+msgid "To support E2EE, Draupnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:84
+msgid "Configuration with E2EE support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:86
+msgid "When using Pantalaimon, Draupnir will log in to its bot account itself through Pantalaimon, so configure its username and password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:88
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:102
+msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Draupnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:114
+msgid "Configuration without E2EE support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:116
+msgid "When NOT using Pantalaimon, Draupnir does not log in by itself and you must give it an access token for its bot account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:118
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:124
+msgid "Abuse Reports"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:126
+msgid "Draupnir supports two methods to receive reports in the management room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:128
+msgid "The first method intercepts the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using traefik, this playbook can set this up for you:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:134
+msgid "The other method polls an Synapse Admin API endpoint, hence it is available only if using Synapse and if the Draupnir user is an admin (see [above](#register-the-bot-account)). To enable it, set `pollReports: true` on `vars.yml` file as below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:136
+msgid "Extending the configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:138
+msgid "You can configure additional options by adding the `matrix_bot_draupnir_configuration_extension_yaml` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:140
+msgid "For example, to change Draupnir's `pollReports` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:154
+msgid "Migrating from Mjolnir (Only required if migrating)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:156
+msgid "Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:158
+msgid "That is all you need to do due to that Draupnir can complete migration on its own."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:160
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:162
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:169
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:171
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:173
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:175
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:177
+msgid "If you change the Pantalaimon's password (`matrix_bot_draupnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_pantalaimon_password` to let Pantalaimon know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:179
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:181
+msgid "You can refer to the upstream [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) for additional ways to use and configure Draupnir and for a more detailed usage guide."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:183
+msgid "Below is a **non-exhaustive quick-start guide** for the impatient."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:185
+msgid "Making Draupnir join and protect a room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:187
+msgid "Draupnir can be told to self-join public rooms, but it's better to follow this flow which works well for all kinds of rooms:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:189
+msgid "Invite the bot to the room manually ([inviting Draupnir to rooms](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#inviting-draupnir-to-rooms)). Before joining, the bot *may* ask for confirmation in the Management Room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:191
+msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:193
+msgid "Tell it to protect the room (using the [rooms command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#using-the-draupnir-rooms-command)) by sending the following command to the Management Room: `!draupnir rooms add !qporfwt:example.com`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:195
+msgid "To have Draupnir provide useful room protection, you need do to a bit more work (at least the first time around). You may wish to [Subscribe to a public policy list](#subscribing-to-a-public-policy-list), [Create your own own policy and rules](#creating-your-own-policy-lists-and-rules) and [Enabling built-in protections](#enabling-built-in-protections)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:197
+msgid "Giving Draupnir permissions to do its job"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:199
+msgid "For Draupnir to do its job, you need to [give it permissions](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#giving-draupnir-permissions) in rooms it's protecting. This involves **giving it an Administrator power level**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:201
+msgid "**We recommend setting this power level as soon as the bot joins your room** (and before you create new rules), so that it can apply rules as soon as they are available. If the bot is under-privileged, it may fail to apply protections and may not retry for a while (or until your restart it)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:203
+msgid "Subscribing to a public policy list"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:205
+msgid "We recommend **subscribing to a public [policy list](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists)** using the [watch command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-watch-command-to-subscribe-to-policy-rooms)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:207
+msgid "Polcy lists are maintained in Matrix rooms. A popular policy list is maintained in the public `#community-moderation-effort-bl:neko.dev` room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:209
+msgid "You can tell Draupnir to subscribe to it by sending the following command to the Management Room: `!draupnir watch #community-moderation-effort-bl:neko.dev`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:211
+msgid "Creating your own policy lists and rules"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:213
+msgid "We also recommend **creating your own policy lists** with the [list create](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-list-create-command-to-create-a-policy-room) command."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:215
+msgid "You can do so by sending the following command to the Management Room: `!draupnir list create my-bans my-bans-bl`. This will create a policy list having a name (shortcode) of `my-bans` and stored in a public `#my-bans-bl:example.com` room on your server. As soon as you run this command, the bot will invite you to the policy list room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:217
+msgid "A policy list does nothing by itself, so the next step is **adding some rules to your policy list**. Policies target a so-called `entity` (one of: `user`, `room` or `server`). These entities are mentioned on the [policy lists](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists) documentation page and in the Matrix Spec [here](https://spec.matrix.org/v1.11/client-server-api/#mban-recommendation)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:219
+msgid "The simplest and most useful entity to target is `user`. Below are a few examples using the [ban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-ban-command) and targeting users."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:221
+msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:223
+msgid "(ban a single user on a given homeserver): `!draupnir ban @charles:example.com my-bans Rude to others`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:224
+msgid "(ban all users on a given homeserver by using a [wildcard](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server - all users are fake`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:226
+msgid "As a result of running these commands, you may observe:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:228
+msgid "Draupnir creating `m.policy.rule.user` state events in the `#my-bans-bl:example.com` room on your server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:229
+msgid "applying these rules against all rooms that Draupnir is an Administrator in"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:231
+msgid "You can undo bans with the [unban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-unban-command)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:233
+msgid "Enabling built-in protections"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:235
+msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the room to invite-only\")."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:237
+msgid "To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:239
+msgid "To **see the configuration options for a given protection**, send a `!draupnir config get PROTECTION_NAME` (e.g. `!draupnir config get JoinWaveShortCircuit`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:241
+msgid "To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:243
+msgid "To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-draupnir.md:245
+msgid "To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot b/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot
new file mode 100644
index 000000000..6897302ae
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bot-go-neb.pot
@@ -0,0 +1,153 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bot-go-neb.md:1
+msgid "Setting up Go-NEB (optional, unmaintained)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:3
+msgid "**Note**: [Go-NEB](https://github.com/matrix-org/go-neb) is now an archived (**unmaintained**) project. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bot instead of this one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:5
+msgid "The playbook can install and configure [Go-NEB](https://github.com/matrix-org/go-neb) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:7
+msgid "Go-NEB is a Matrix bot written in Go. It is the successor to Matrix-NEB, the original Matrix bot written in Python."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:9
+msgid "See the project's [documentation](https://github.com/matrix-org/go-neb/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:13
+msgid "Register the bot account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:15
+msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:17
+msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:19
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:25
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:27
+msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:29
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:31
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:33
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_GONEB_HERE` and `ACCESS_TOKEN_FOR_ANOTHER_GONEB_HERE` with the ones created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:197
+msgid "Adjusting the Go-NEB URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:199
+msgid "By default, this playbook installs Go-NEB on the `goneb.` subdomain (`goneb.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:201
+msgid "By tweaking the `matrix_bot_go_neb_hostname` and `matrix_bot_go_neb_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-bot-go-neb.md:203
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:214
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:216
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Go-NEB domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:218
+msgid "By default, you will need to create a CNAME record for `goneb`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:220
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:222
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:224
+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-bot-go-neb.md:231
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:233
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:235
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:237
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:239
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:241
+msgid "To use the bot, invite it to any existing Matrix room (`/invite @bot.go-neb:example.com` where `example.com` is your base domain, not the `matrix.` domain). Make sure you are granted with the sufficient permission if you are not the room owner."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:243
+msgid "Basic usage is like this: `!echo hi` or `!imgur puppies` or `!giphy matrix`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:245
+msgid "If you enabled the github_cmd service, send `!github help` to the bot in the room to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-go-neb.md:247
+msgid "You can also refer to the upstream [Documentation](https://github.com/matrix-org/go-neb)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot b/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot
new file mode 100644
index 000000000..6b1ef24b1
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bot-honoroit.pot
@@ -0,0 +1,121 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-23 13:09+0900\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-bot-honoroit.md:1
+msgid "Setting up Honoroit (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:3
+msgid "The playbook can install and configure [Honoroit](https://github.com/etkecc/honoroit) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:5
+msgid "It's a bot you can use to setup **your own helpdesk on matrix**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:7
+msgid "See the project's [documentation](https://github.com/etkecc/honoroit/blob/main/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:11
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:26
+msgid "Adjusting the Honoroit URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:28
+msgid "By default, this playbook installs Honoroit on the `matrix.` subdomain, at the `/honoroit` path (https://matrix.example.com/honoroit). 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-bot-honoroit.md:30
+msgid "By tweaking the `matrix_bot_honoroit_hostname` and `matrix_bot_honoroit_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-bot-honoroit.md:32
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:40
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:42
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Honoroit domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:44
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:46
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:48
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:50
+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-bot-honoroit.md:57
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:59
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.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-bot-honoroit.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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:65
+msgid "If you change the bot password (`matrix_bot_honoroit_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:67
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:69
+msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @honoroit:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:71
+msgid "After the bot joins the room, any Matrix user can send a message to it to start a new thread in that room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:73
+msgid "Send `!ho help` to the bot in the room to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-honoroit.md:75
+msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/honoroit#features)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot
new file mode 100644
index 000000000..9773f005d
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-registration-bot.pot
@@ -0,0 +1,97 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-23 13:09+0900\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-bot-matrix-registration-bot.md:1
+msgid "Setting up matrix-registration-bot (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:3
+msgid "The playbook can install and configure [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:5
+msgid "The bot allows you to easily **create and manage registration tokens** aka. invitation codes. It can be used for an invitation-based server, where you invite someone by sending them a registration token (tokens look like this: `rbalQ0zkaDSRQCOp`). They can register as per normal but have to provide a valid registration token in the final step of the registration process."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:7
+msgid "See the project's [documentation](https://github.com/moan0s/matrix-registration-bot/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:11
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:30
+msgid "The bot account will be created automatically."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:32
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:34
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:41
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:43
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:45
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:47
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:49
+msgid "If you change the bot password (`matrix_bot_matrix_registration_bot_bot_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:51
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:53
+msgid "To use the bot, start a chat with `@bot.matrix-registration-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57
+msgid "You can also refer to the upstream [Usage documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:59
+msgid "If you have any questions, or if you need help setting it up, read the [troublshooting guide](https://github.com/moan0s/matrix-registration-bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:61
+msgid "To clean the cache (session & encryption data) after you changed the bot's username, changed the login method from access_token to password etc… you can use:"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-matrix-reminder-bot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-reminder-bot.pot
new file mode 100644
index 000000000..98bf509a9
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bot-matrix-reminder-bot.pot
@@ -0,0 +1,93 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-23 13:09+0900\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-bot-matrix-reminder-bot.md:1
+msgid "Setting up matrix-reminder-bot (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:3
+msgid "The playbook can install and configure [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:5
+msgid "It's a bot you can use to **schedule one-off & recurring reminders and alarms**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:7
+msgid "See the project's [documentation](https://github.com/anoadragon453/matrix-reminder-bot/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:26
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:28
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:35
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:37
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:39
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:41
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:43
+msgid "If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:45
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:47
+msgid "To use the bot, start a chat with `@bot.matrix-reminder-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:49
+msgid "You can also add the bot to any existing Matrix room (`/invite @bot.matrix-reminder-bot:example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:51
+msgid "Basic usage is like this: `!remindme in 2 minutes; This is a test`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:53
+msgid "Send `!help reminders` to the room to see the bot's help menu for additional commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:55
+msgid "You can also refer to the upstream [Usage documentation](https://github.com/anoadragon453/matrix-reminder-bot#usage)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-maubot.pot b/i18n/translation-templates/docs/configuring-playbook-bot-maubot.pot
new file mode 100644
index 000000000..463906876
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bot-maubot.pot
@@ -0,0 +1,162 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bot-maubot.md:1
+msgid "Setting up maubot (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:3
+msgid "The playbook can install and configure [maubot](https://github.com/maubot/maubot) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:5
+msgid "After setting up maubot, you can use the web management interface to make it do things. The default location of the management interface is `matrix.example.com/_matrix/maubot/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:7
+msgid "See the project's [documentation](https://docs.mau.fi/maubot/usage/basic.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:11
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:26
+msgid "You can add multiple admins. The admin accounts are only used to access the maubot administration interface."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:28
+msgid "Adjusting the maubot URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:30
+msgid "By default, this playbook installs maubot on the `matrix.` subdomain, at the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/). 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-bot-maubot.md:32
+msgid "By tweaking the `matrix_bot_maubot_hostname` and `matrix_bot_maubot_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-bot-maubot.md:34
+#: ../../../docs/configuring-playbook-bot-maubot.md:56
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:42
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:44
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the maubot domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:46
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:48
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:50
+msgid "Customizing the maubot container image"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:52
+msgid "Certain [maubot plugins](https://plugins.mau.bot/) require additional dependencies to be installed."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:54
+msgid "You can customize the default maubot container image and install your own dependencies."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:67
+msgid "Consult the [Dockerfile reference](https://docs.docker.com/reference/dockerfile/) for more information about the syntax."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:69
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:71
+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-bot-maubot.md:78
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:80
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:82
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:84
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:86
+msgid "If you change the bot password (`matrix_bot_maubot_initial_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:88
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:90
+msgid "By default, you can visit `matrix.example.com/_matrix/maubot/` to manage your available plugins, clients and instances."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:92
+msgid "You should start in the following order"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:93
+msgid "**Create one or more clients**: A client is a Matrix account which the bot will use to message. By default, the playbook creates a `bot.maubot` account (as per the configuration above). You only need to [obtain an access token](#obtaining-an-access-token) for it"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:94
+msgid "**Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:95
+msgid "**Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:97
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:99
+msgid "This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:101
+msgid "Alternatively, you can refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will causes issues to your bot in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-maubot.md:103
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot b/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot
new file mode 100644
index 000000000..e5d06bb95
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot
@@ -0,0 +1,221 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bot-mjolnir.md:1
+msgid "Setting up Mjolnir (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:3
+msgid "The playbook can install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation bot for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:5
+msgid "See the project's [documentation](https://github.com/matrix-org/mjolnir/blob/main/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:7
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:9
+msgid "Register the bot account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:11
+msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:13
+msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:15
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:21
+msgid "If you would like Mjolnir to be able to deactivate users, move aliases, shutdown rooms, etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:23
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:25
+msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:27
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:29
+msgid "Make sure the account is free from rate limiting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:31
+msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:33
+msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:35
+msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:41
+msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. 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-bot-mjolnir.md:43
+msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:45
+msgid "To discharge rate limiting, run the following command on systems that ship curl (note that it does not work on outdated Windows 10). Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally. Before running it, make sure to replace `@bot.mjolnir:example.com` with the MXID of your Mjolnir:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:51
+msgid "You can obtain an access token for a homeserver admin account in the same way as you can do so for Mjolnir itself. If you have made Mjolnir an admin, you can just use the Mjolnir token."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:53
+msgid "Create a management room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:55
+msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room. Anyone in this room can control the bot so it is important that you only invite trusted users to this room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:57
+msgid "If you make the management room encrypted (E2EE), then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:59
+msgid "Once you have created the room you need to copy the room ID so you can tell the bot to use that room. In Element Web you can do this by going to the room's settings, clicking Advanced, and then copying the internal room ID. The room ID will look something like `!qporfwt:example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:61
+msgid "Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:63
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:65
+msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:74
+msgid "End-to-End Encryption support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:76
+msgid "Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:78
+msgid "To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:80
+msgid "Configuration with E2EE support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:82
+msgid "When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:84
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:98
+msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Mjolnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:110
+msgid "Configuration without E2EE support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:112
+msgid "When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:114
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:120
+msgid "Adding Mjolnir synapse antispam module (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:122
+msgid "To enable Mjolnir synapse antispam module, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:132
+msgid "Extending the configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:134
+msgid "You can configure additional options by adding the `matrix_bot_mjolnir_configuration_extension_yaml` variable to your `inventory/host_vars/matrix.example.com/vars.yml` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:136
+msgid "For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:150
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:152
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:159
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:161
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:163
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:165
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:167
+msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:169
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:171
+msgid "You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-discord.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-discord.pot
new file mode 100644
index 000000000..81f55b679
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-discord.pot
@@ -0,0 +1,166 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 23:17+0900\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-bridge-appservice-discord.md:1
+msgid "Setting up Appservice Discord bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:3
+msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:4
+msgid "For using as a Bot we are recommend the Appservice Discord bridge (the one being discussed here), because it supports plumbing."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:5
+msgid "For personal use we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:7
+msgid "The playbook can install and configure [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:9
+msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-discord/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:13
+msgid "Create a Discord Application [here](https://discordapp.com/developers/applications). Then retrieve Client ID, and create a bot from the Bot tab and retrieve the Bot token."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:15
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:17
+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-discord.md:31
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:33
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:40
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:42
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:44
+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-discord.md:46
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:48
+msgid "Self-Service Bridging (Manual)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:50
+msgid "Self-service bridging allows you to bridge specific and existing Matrix rooms to specific Discord rooms. To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:56
+msgid "**Note**: If self-service bridging is not enabled, `!discord help` commands will return no results."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:58
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:82
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:60
+msgid "Once self-service is enabled, start a chat with `@_discord_bot:example.com` and say `!discord help bridge`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:62
+msgid "Then, follow the instructions in the help output message."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:64
+msgid "If the bot is not already in the Discord server, follow the provided invite link. This may require you to be a administrator of the Discord server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:66
+msgid "On the Discord side, send `!matrix help` to the bot to see the available commands for managing the bridge and Matrix users."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:68
+msgid "**Note**: Encrypted Matrix rooms are not supported as of writing."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:70
+msgid "Portal Bridging (Automatic)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:72
+msgid "Through portal bridging, Matrix rooms will automatically be created by the bot and bridged to the relevant Discord room. This is done by simply joining a room with a specific name pattern (`#_discord_<guildID>_<channelID>`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:74
+msgid "All Matrix rooms created this way are **listed publicly** by default, and you will not have admin permissions to change this. To get more control, [make yourself a room Administrator](#getting-administrator-access-in-a-portal-bridged-room). You can then unlist the room from the directory and change the join rules."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:76
+msgid "To disable portal bridging, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:84
+msgid "To get started with Portal Bridging:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:86
+msgid "To invite the bot to Discord, retrieve the invite link from the `{{ matrix_appservice_discord_config_path }}/invite_link` file on the server (this defaults to `/matrix/appservice-discord/config/invite_link`). You need to peek at the file on the server via SSH, etc., because it's not available via HTTP(S)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:87
+msgid "Room addresses follow this syntax: `#_discord_<guildID>_<channelID>`. You can easily find the guild and channel IDs by logging into Discord in a browser and opening the desired channel. The URL will have this format: `discord.com/channels/<guildID>/<channelID>`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:88
+msgid "Once you have figured out the appropriate room address, you can join by doing `/join #_discord_<guildID>_<channelID>` in your Matrix client."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:90
+msgid "Getting Administrator access in a portal bridged room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:92
+msgid "By default, you won't have Administrator access in rooms created by the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:94
+msgid "To adjust room access privileges or do various other things (change the room name subsequently, etc.), you'd wish to become an Administrator."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-discord.md:96
+msgid "There's the Discord bridge's guide for [setting privileges on bridge managed rooms](https://github.com/matrix-org/matrix-appservice-discord/blob/master/docs/howto.md#set-privileges-on-bridge-managed-rooms). To do the same with our container setup, run the following command on the server:"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-irc.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-irc.pot
new file mode 100644
index 000000000..5da520867
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-irc.pot
@@ -0,0 +1,73 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-bridge-appservice-irc.md:1
+msgid "Setting up Appservice IRC bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:3
+msgid "**Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [Heisenbridge](configuring-playbook-bridge-heisenbridge.md) bridge supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:5
+msgid "The playbook can install and configure the [matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc) bridge for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:7
+msgid "See the project's [documentation](https://github.com/matrix-org/matrix-appservice-irc/blob/master/HOWTO.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:11
+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-irc.md:63
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:65
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:72
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:74
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:76
+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-irc.md:78
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:80
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-irc.md:82
+msgid "To use the bridge, you need to start a chat with `@irc_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-kakaotalk.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-kakaotalk.pot
new file mode 100644
index 000000000..cb917fa11
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-kakaotalk.pot
@@ -0,0 +1,157 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bridge-appservice-kakaotalk.md:1
+msgid "Setting up Appservice Kakaotalk bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:3
+msgid "The playbook can install and configure [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) for you. `matrix-appservice-kakaotalk` is a bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) based on [node-kakao](https://github.com/storycraft/node-kakao) (now unmaintained) and some [mautrix-facebook](https://github.com/mautrix/facebook) code."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:5
+msgid "⚠️ **Warning**: there have been recent reports (~2022-09-16) that **using this bridge may get your account banned**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:7
+msgid "See the project's [documentation](https://src.miscworks.net/fair/matrix-appservice-kakaotalk/src/branch/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:9
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:11
+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 [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:13
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:15
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:17
+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-kakaotalk.md:23
+msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:25
+msgid "Additional configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:27
+msgid "There are some additional things you may wish to configure about the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:29
+msgid "Take a look at:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:31
+msgid "`roles/custom/matrix-bridge-appservice-kakaotalk/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:32
+msgid "`roles/custom/matrix-bridge-appservice-kakaotalk/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_kakaotalk_configuration_extension_yaml` variable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:34
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:36
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:43
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:45
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:47
+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-kakaotalk.md:49
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:51
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:53
+msgid "To use the bridge, you need to start a chat with `@kakaotalkbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:55
+msgid "Send `login --save EMAIL_OR_PHONE_NUMBER` to the bridge bot to enable bridging for your Kakaotalk account. The `--save` flag may be omitted, if you'd rather not save your password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:57
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:59
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:61
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:63
+msgid "Method 1: automatically, by enabling Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:65
+msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:67
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:69
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:71
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:73
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:75
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-kakaotalk.md:77
+msgid "make sure you don't log out the `Appservice-Kakaotalk` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-slack.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-slack.pot
new file mode 100644
index 000000000..ed9cf1703
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-slack.pot
@@ -0,0 +1,242 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-bridge-appservice-slack.md:1
+msgid "Setting up Appservice Slack bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:3
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:75
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:4
+msgid "Bridging to [Slack](https://slack.com) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:5
+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:7
+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:9
+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:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:13
+msgid "Create a Classic Slack App"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:15
+msgid "First, you need to create a Classic Slack App [here](https://api.slack.com/apps?new_classic_app=1)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:17
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:19
+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:21
+msgid "Add the following events as `Bot User Events` and save:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:23
+msgid "team_domain_change"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:24
+msgid "message.channels"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:25
+msgid "message.groups (if you want to bridge private channels)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:26
+msgid "reaction_added"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:27
+msgid "reaction_removed"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:29
+msgid "Next, click on \"OAuth & Permissions\" and add the following scopes:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:31
+msgid "chat:write:bot"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:32
+msgid "users:read"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:33
+msgid "reactions:write"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:34
+msgid "files:write:user (if you want to bridge files)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:36
+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:38
+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:40
+msgid "Create an administration control room on Matrix"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:42
+msgid "Create a new Matrix room to act as the administration control room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:44
+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:46
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:48
+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:64
+msgid "Other configuration options are available via the `matrix_appservice_slack_configuration_extension_yaml` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:66
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:68
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:77
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.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-bridge-appservice-slack.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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:83
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:85
+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:87
+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:89
+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:90
+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:91
+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:92
+msgid "Issue a link command in the administration control room with these collected values as arguments:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:94
+msgid "with file bridging:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:100
+msgid "without file bridging:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:106
+msgid "These arguments can be shortened to single-letter forms:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:112
+msgid "Unlinking"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:114
+msgid "Channels can be unlinked again by sending this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:120
+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:122
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:124
+msgid "As always, check the logs: `journalctl -fu matrix-appservice-slack`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:126
+msgid "Linking: \"Room is now pending-name\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:128
+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:130
+msgid "Messages work from Matrix to Slack, but not the other way around"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:132
+msgid "Check you logs, if they say something like"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:134
+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:136
+msgid "then unlink your room, reinvite the bot and re-link it again. This may particularly hit you, if you tried to unsuccessfully link your room multiple times without unlinking it after each failed attempt."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-webhooks.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-webhooks.pot
new file mode 100644
index 000000000..01b5b7121
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-appservice-webhooks.pot
@@ -0,0 +1,109 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-bridge-appservice-webhooks.md:1
+msgid "Setting up Appservice Webhooks bridging (optional, deprecated)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:3
+msgid "**Note**: This bridge has been deprecated. We recommend not bothering with installing it. While not a 1:1 replacement, the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md). Consider using that bridge instead of this one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:5
+msgid "The playbook can install and configure [matrix-appservice-webhooks](https://github.com/turt2live/matrix-appservice-webhooks) for you. This bridge provides support for Slack-compatible webhooks."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:7
+msgid "See the project's [documentation](https://github.com/turt2live/matrix-appservice-webhooks/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:11
+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-webhooks.md:27
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:29
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:36
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:38
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:40
+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-webhooks.md:42
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:44
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:46
+msgid "To use the bridge, you need to invite the bridge bot user to your room in either way."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:48
+msgid "Send `/invite @_webhook:example.com` (**Note**: Make sure you have administration permissions in your room)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:49
+msgid "Add the bridge bot to a private channel (personal channels imply you being an administrator)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:51
+msgid "You then need to send a message to the bridge bot in order to receive a private message including the webhook link:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:57
+msgid "The JSON body for posting messages will have to look like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:68
+msgid "You can test this via curl like so:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:81
+msgid "Setting Webhooks with Dimension integration manager"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:83
+msgid "If you're using the [Dimension integration manager](configuring-playbook-dimension.md), you can configure the Webhooks bridge with it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:85
+msgid "To configure it, open the Dimension integration manager, and go to \"Settings\" and \"Bridges\", then select edit action for \"Webhook Bridge\"."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-appservice-webhooks.md:87
+msgid "On the UI, press \"Add self-hosted Bridge\" button and populate \"Provisioning URL\"  and \"Shared Secret\" values from `/matrix/appservice-webhooks/config/config.yaml` file's homeserver URL value and provisioning secret value, respectively."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-beeper-linkedin.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-beeper-linkedin.pot
new file mode 100644
index 000000000..3863e6d9b
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-beeper-linkedin.pot
@@ -0,0 +1,125 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-bridge-beeper-linkedin.md:1
+msgid "Setting up Beeper Linkedin bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:3
+msgid "The playbook can install and configure [beeper-linkedin](https://github.com/beeper/linkedin) for you, for bridging to [LinkedIn](https://www.linkedin.com/) Messaging. This bridge is based on the mautrix-python framework and can be configured in a similar way to the other mautrix bridges"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:5
+msgid "See the project's [documentation](https://github.com/beeper/linkedin/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:9
+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-beeper-linkedin.md:15
+msgid "There are some additional things you may wish to configure about the bridge before you continue."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:17
+msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:24
+msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:33
+msgid "You may wish to look at `roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2` to find other things you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:35
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:37
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:44
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:46
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:48
+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-beeper-linkedin.md:50
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:52
+msgid "Set up Double Puppeting by enabling Appservice Double Puppet or Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:54
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:56
+msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:58
+msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:60
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:62
+msgid "To use the bridge, you need to start a chat with `@linkedinbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:64
+msgid "Send `login YOUR_LINKEDIN_EMAIL_ADDRESS` to the bridge bot to enable bridging for your LinkedIn account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:66
+msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:68
+msgid "After successfully enabling bridging, you may wish to [set up Double Puppeting](#set-up-double-puppeting-by-enabling-appservice-double-puppet-or-shared-secret-auth), if you haven't already done so."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:70
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:72
+msgid "Bridge asking for 2FA even if you don't have 2FA enabled"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-beeper-linkedin.md:74
+msgid "If you don't have 2FA enabled and are logging in from a strange IP for the first time, LinkedIn will send an email with a one-time code. You can use this code to authorize the bridge session. In my experience, once the IP is authorized, you will not be asked again."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-go-skype-bridge.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-go-skype-bridge.pot
new file mode 100644
index 000000000..77317e407
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-go-skype-bridge.pot
@@ -0,0 +1,73 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 23:17+0900\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-bridge-go-skype-bridge.md:1
+msgid "Setting up Go Skype Bridge bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:3
+msgid "The playbook can install and configure [go-skype-bridge](https://github.com/kelaresg/go-skype-bridge) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:5
+msgid "See the project's [documentation](https://github.com/kelaresg/go-skype-bridge/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:9
+msgid "To enable the [Skype](https://www.skype.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:15
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:17
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:24
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:26
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:28
+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-go-skype-bridge.md:30
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:32
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:34
+msgid "To use the bridge, you need to start a chat with `Skype bridge bot` with the handle `@skypebridgebot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-go-skype-bridge.md:36
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-heisenbridge.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-heisenbridge.pot
new file mode 100644
index 000000000..76127e7b9
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-heisenbridge.pot
@@ -0,0 +1,125 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 09:53+0200\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-bridge-heisenbridge.md:1
+msgid "Setting up Heisenbridge bouncer-style IRC bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:3
+msgid "**Note**: bridging to [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) can also happen via the [matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md) bridge supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:5
+msgid "The playbook can install and configure [Heisenbridge](https://github.com/hifi/heisenbridge) - the bouncer-style [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) bridge for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:7
+msgid "See the project's [documentation](https://github.com/hifi/heisenbridge/blob/master/README.md) to learn what it does and why it might be useful to you. You can also take a look at [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:9
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:11
+msgid "To enable Heisenbridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:24
+msgid "For a more complete list of variables that you could override, see the [`defaults/main.yml` file](../roles/custom/matrix-bridge-heisenbridge/defaults/main.yml) of the Heisenbridge Ansible role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:26
+msgid "Adjusting the Heisenbridge URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:28
+msgid "By default, this playbook installs Heisenbridge on the `matrix.` subdomain, at the `/heisenbridge` path (https://matrix.example.com/heisenbridge). It would handle media requests there (see the [release notes for Heisenbridge v1.15.0](https://github.com/hifi/heisenbridge/releases/tag/v1.15.0))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:30
+msgid "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-bridge-heisenbridge.md:32
+msgid "By tweaking the `matrix_heisenbridge_hostname` and `matrix_heisenbridge_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-bridge-heisenbridge.md:34
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:42
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:44
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Heisenbridge domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:46
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:48
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:50
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:52
+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-bridge-heisenbridge.md:59
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:61
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:63
+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-heisenbridge.md:65
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:67
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:69
+msgid "To use the bridge, you need to start a chat with `@heisenbridge:example.com` (where `example.com` is your base domain, not the `matrix.` domain). If the bridge ignores you and a DM is not accepted then the owner setting may be wrong."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:71
+msgid "Help is available for all commands with the `-h` switch."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:73
+msgid "You can also learn the basics by watching [this demonstration video](https://www.youtube.com/watch?v=nQk1Bp4tk4I)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-heisenbridge.md:75
+msgid "If you encounter issues or feel lost you can join the project room at [#heisenbridge:vi.fi](https://matrix.to/#/#heisenbridge:vi.fi) for help."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot
new file mode 100644
index 000000000..c720cf45b
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot
@@ -0,0 +1,381 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 23:17+0900\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-bridge-hookshot.md:1
+msgid "Setting up matrix-hookshot (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:3
+msgid "The playbook can install and configure [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:5
+msgid "Hookshot can bridge [Webhooks](https://en.wikipedia.org/wiki/Webhook) from software project management services such as GitHub, GitLab, Jira, and Figma, as well as generic webhooks."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:7
+msgid "See the project's [documentation](https://matrix-org.github.io/matrix-hookshot/latest/hookshot.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:9
+msgid "**Note**: the playbook also supports [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), which however was deprecated by its author."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:13
+msgid "Download GitHub app private key (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:15
+msgid "If you're setting up the GitHub bridge, you need to create your GitHub app, and generate a private key file of it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:17
+msgid "You need to download the private key file, if you will install the file manually or with the `aux` role. For details, see [the section below](#manage-github-private-key-with-aux-role)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:19
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:21
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `GITHUB_PRIVATE_KEY_HERE` with the one created [above](#download-github-app-private-key)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:35
+msgid "For each of the services (GitHub, GitLab, Jira, Figma, and generic webhooks) fill in the respective variables `matrix_hookshot_service_*` listed in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) as required."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:37
+msgid "Take special note of the `matrix_hookshot_*_enabled` variables. Services that need no further configuration are enabled by default (GitLab and generic webhooks), while you must first add the required configuration and enable the others (GitHub, Jira, and Figma)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:39
+msgid "Extending the configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:41
+msgid "You can configure additional options by adding the `matrix_hookshot_configuration_extension_yaml` and `matrix_hookshot_registration_extension_yaml` variables."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:43
+msgid "Refer the [official instructions](https://matrix-org.github.io/matrix-hookshot/latest/setup.html) and the comments in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) to learn what the individual options do."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:45
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:47
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:54
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service hookshot` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:56
+msgid "`just install-service hookshot` is useful for maintaining your setup quickly 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 `just setup-all` runs the `ensure-matrix-users-created` tag too."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:58
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:60
+msgid "To use the bridge, you need to create a room and invite the Hookshot bot (`@hookshot:example.com`) to it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:62
+msgid "Make sure the bot is able to send state events (usually the Moderator power level in clients)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:64
+msgid "Send `!hookshot help` to the bot to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:66
+msgid "Refer to [Hookshot's documentation](https://matrix-org.github.io/matrix-hookshot/latest/usage.html) for more details about using the bridge's various features."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:68
+msgid "💡 **Note**: the different listeners are bound to certain paths which might differ from those assumed by the hookshot documentation. See [URLs for bridges setup](#urls-for-bridges-setup) below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:70
+msgid "Reset crypto store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:72
+msgid "Should the crypto store be corrupted, you can reset it by executing this Ansible playbook with the tag `reset-hookshot-encryption` added:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:78
+msgid "More setup documentation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:80
+msgid "URLs for bridges setup"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:82
+msgid "Unless indicated otherwise, the following endpoints are reachable on your `matrix.` subdomain (if the feature is enabled)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "Listener"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "Default path"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "Variable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "Used as"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "-"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`/hookshot/webhooks/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`matrix_hookshot_webhook_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "Webhook-prefix, which affects all webhook-related URLs below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "generic"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`/hookshot/webhooks/webhook`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`matrix_hookshot_generic_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "Generic webhooks"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "github oauth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`/hookshot/webhooks/oauth`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`matrix_hookshot_github_oauth_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "GitHub \"Callback URL\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "jira oauth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`/hookshot/webhooks/jira/oauth`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`matrix_hookshot_jira_oauth_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "Jira OAuth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "figma endpoint"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`/hookshot/webhooks/figma/webhook`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`matrix_hookshot_figma_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "Figma"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "provisioning"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`/hookshot/v1/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`matrix_hookshot_provisioning_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "Dimension [provisioning](#provisioning-api)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "appservice"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`/hookshot/_matrix/app/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`matrix_hookshot_appservice_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "Matrix server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "widgets"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`/hookshot/widgetapi/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`matrix_hookshot_widgets_endpoint`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "Widgets"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "metrics"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`/metrics/hookshot`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "`matrix_hookshot_metrics_enabled` and exposure enabled via `matrix_hookshot_metrics_proxying_enabled` or `matrix_metrics_exposure_enabled`. Read more in the [Metrics section](#metrics) below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:0
+msgid "Prometheus"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:96
+msgid "Also see the various `matrix_hookshot_container_labels_*` variables in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml), which expose URLs publicly"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:98
+msgid "The different listeners are also reachable *internally* in the docker-network via the container's name (configured by `matrix_hookshot_container_url`) and on different ports (e.g. `matrix_hookshot_appservice_port`). Read [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) in detail for more info."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:100
+msgid "Manage GitHub Private Key with aux role"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:102
+msgid "The GitHub bridge requires you to install a private key file. This can be done in multiple ways:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:104
+msgid "copy the *contents* of the downloaded file and set the variable `matrix_hookshot_github_private_key` to the contents (see example in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:105
+msgid "somehow copy the file to the path `{{ matrix_hookshot_base_path }}/{{ matrix_hookshot_github_private_key_file }}` (default: `/matrix/hookshot/private-key.pem`) on the server manually."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:106
+msgid "use the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) to copy the file from an arbitrary path on your ansible client to the correct path on the server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:108
+msgid "To use the `aux` role, make sure the `matrix_hookshot_github_private_key` variable is empty. Then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:119
+msgid "For more information, see the documentation in the [default configuration of the aux role](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:121
+msgid "Provisioning API"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:123
+msgid "The provisioning API will be enabled automatically if you set `matrix_dimension_enabled: true` and provided a `matrix_hookshot_provisioning_secret`, unless you override it either way. To use hookshot with dimension, you will need to enter as \"Provisioning URL\": `http://matrix-hookshot:9002`, which is made up of the variables `matrix_hookshot_container_url` and `matrix_hookshot_provisioning_port`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:125
+msgid "Metrics"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:127
+msgid "Metrics are **only enabled by default** if the builtin [Prometheus](configuring-playbook-prometheus-grafana.md) is enabled (by default, Prometheus isn't enabled). If so, metrics will automatically be collected by Prometheus and made available in Grafana. You will, however, need to set up your own Dashboard for displaying them."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:129
+msgid "To explicitly enable metrics, use `matrix_hookshot_metrics_enabled: true`. This only exposes metrics over the container network, however."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:131
+msgid "**To collect metrics from an external Prometheus server**, besides enabling metrics as described above, you will also need to enable metrics exposure on `https://matrix.example.com/metrics/hookshot` by:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:133
+msgid "either enabling metrics exposure for Hookshot via `matrix_hookshot_metrics_proxying_enabled: true`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:134
+msgid "or enabling metrics exposure for all services via `matrix_metrics_exposure_enabled: true`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:136
+msgid "Whichever one you go with, by default metrics are exposed publicly **without** password-protection. See [the Prometheus and Grafana docs](configuring-playbook-prometheus-grafana.md) for details about password-protection for metrics."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:138
+msgid "Collision with matrix-appservice-webhooks"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-hookshot.md:140
+msgid "If you are also running [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md), it reserves its namespace by the default setting `matrix_appservice_webhooks_user_prefix: '_webhook_'`. You should take care if you modify its or hookshot's prefix that they do not collide with each other's namespace (default `matrix_hookshot_generic_userIdPrefix: '_webhooks_'`)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-matrix-bridge-sms.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-matrix-bridge-sms.pot
new file mode 100644
index 000000000..aed94e159
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-matrix-bridge-sms.pot
@@ -0,0 +1,73 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 09:53+0200\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-bridge-matrix-bridge-sms.md:1
+msgid "Setting up Matrix SMS bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:3
+msgid "The playbook can install and configure [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:5
+msgid "See the project's [documentation](https://github.com/benkuly/matrix-sms-bridge/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:7
+msgid "**The bridge uses [android-sms-gateway-server](https://github.com/RebekkaMa/android-sms-gateway-server). You need to configure it first.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:11
+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-matrix-bridge-sms.md:34
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:36
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:43
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:45
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:47
+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-matrix-bridge-sms.md:49
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:51
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-matrix-bridge-sms.md:53
+msgid "Read the [user guide](https://github.com/benkuly/matrix-sms-bridge/blob/master/README.md#user-guide) to see how this bridge works."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-discord.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-discord.pot
new file mode 100644
index 000000000..9a18465db
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-discord.pot
@@ -0,0 +1,241 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bridge-mautrix-discord.md:1
+msgid "Setting up Mautrix Discord bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:3
+msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) and [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md) bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:4
+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:5
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:7
+msgid "The playbook can install and configure [mautrix-discord](https://github.com/mautrix/discord) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:9
+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:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:13
+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)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:15
+msgid "If this is a dealbreaker for you, consider using one of the other Discord bridges supported by the playbook: [mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md) or [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md). These come with their own complexity and limitations, however, so we recommend that you proceed with this one if possible."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:17
+msgid "Enable Appservice Double Puppet or Shared Secret Auth (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:19
+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:21
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:23
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:25
+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:31
+msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:33
+msgid "Additional configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:35
+msgid "There are some additional things you may wish to configure about the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:37
+msgid "Take a look at:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:39
+msgid "`roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:40
+msgid "`roles/custom/matrix-bridge-mautrix-discord/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_mautrix_discord_configuration_extension_yaml` variable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:42
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:44
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:51
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:53
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.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-discord.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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:59
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:61
+msgid "Logging in"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:63
+msgid "Method 1: Login using QR code (recommended)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:65
+msgid "For using this bridge, you would need to authenticate by **scanning a QR code** with the Discord app on your phone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:67
+msgid "You can delete the Discord app after the authentication process."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:69
+msgid "Method 2: Login using Discord token (not recommended)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:71
+msgid "To acquire the token, open Discord in a private browser window. Then open the developer settings (keyboard shortcut might be \"ctrl+shift+i\" or by pressing \"F12\"). Navigate to the \"Network\" tab then reload the page. In the URL filter or search bar type \"/api\" and find the response with the file name of \"library\". Under the request headers you should find a variable called \"Authorization\", this is the token to your Discord account. After copying the token, you can close the browser window."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:73
+msgid "Bridging"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:75
+msgid "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:76
+msgid "If you would like to login to Discord using a token, send `login-token` command, otherwise, send `login-qr` command."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:77
+msgid "You'll see a QR code which you need to scan with the Discord app on your phone. You can scan it with the camera app too, which will open Discord, which will then instruct you to scan it a 2nd time in the Discord app."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:78
+msgid "After confirming (in the Discord app) that you'd like to allow this login, the bot should respond with \"Succcessfully authenticated as …\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:79
+msgid "Now that you're logged in, you can send `help` to the bot to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:80
+msgid "Some Direct Messages from Discord should start syncing automatically"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:81
+msgid "If you'd like to bridge guilds:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:82
+msgid "send `guilds status` to see the list of guilds"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:83
+msgid "for each guild that you'd like bridged, send `guilds bridge GUILD_ID --entire`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:84
+msgid "You may wish to uninstall the Discord app from your phone now. It's not needed for the bridge to function."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:86
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:88
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:90
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:92
+msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:94
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:96
+msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:98
+msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:100
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:102
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:104
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:106
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-discord.md:108
+msgid "make sure you don't log out the `Mautrix-Discord` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-facebook.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-facebook.pot
new file mode 100644
index 000000000..ac1d04009
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-facebook.pot
@@ -0,0 +1,197 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bridge-mautrix-facebook.md:1
+msgid "Setting up Mautrix Facebook bridging (optional, deprecated)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:3
+msgid "**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-messenger.md). Consider using that bridge instead of this one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:5
+msgid "The playbook can install and configure [mautrix-facebook](https://github.com/mautrix/facebook) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:7
+msgid "See the project's [documentation](https://github.com/mautrix/facebook/blob/master/ROADMAP.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:9
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:11
+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 [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:13
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:15
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:17
+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-facebook.md:23
+msgid "There are some additional things you may wish to configure about the bridge before you continue."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:25
+msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:35
+msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:44
+msgid "Using both would look like"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:56
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-facebook/defaults/main.yml` to find other things you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:58
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:60
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:67
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:69
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:71
+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-facebook.md:73
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:75
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:77
+msgid "To use the bridge, you need to start a chat with `@facebookbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:79
+msgid "Send `login YOUR_FACEBOOK_EMAIL_ADDRESS` to the bridge bot to enable bridging for your Facebook Messenger account. You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/facebook/authentication.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:81
+msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:83
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:85
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:87
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:89
+msgid "Method 1: automatically, by enabling Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:91
+msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:93
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:95
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:97
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:99
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:101
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:103
+msgid "make sure you don't log out the `Mautrix-Facebook` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:105
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:107
+msgid "Facebook rejecting login attempts and forcing you to change password"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:109
+msgid "If your Matrix server is in a wildly different location than where you usually use your Facebook account from, the bridge's login attempts may be outright rejected by Facebook. Along with that, Facebook may even force you to change the account's password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:111
+msgid "If you happen to run into this problem while [setting up bridging](#usage), try to first get a successful session up by logging in to Facebook through the Matrix server's IP address."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:113
+msgid "The easiest way to do this may be to use [sshuttle](https://sshuttle.readthedocs.io/) to proxy your traffic through the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:115
+msgid "Example command for proxying your traffic through the Matrix server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:121
+msgid "Once connected, you should be able to verify that you're browsing the web through the Matrix server's IP by checking [icanhazip](https://icanhazip.com/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:123
+msgid "Then proceed to log in to [Facebook/Messenger](https://www.facebook.com/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:125
+msgid "Once logged in, proceed to [set up bridging](#usage)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-facebook.md:127
+msgid "If that doesn't work, enable 2FA (see: [Facebook help page on enabling 2FA](https://www.facebook.com/help/148233965247823)) and try to login again with a new password, and entering the 2FA code when prompted, it may take more then one try, in between attempts, check facebook.com to see if they are requiring another password change"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-gmessages.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-gmessages.pot
new file mode 100644
index 000000000..f5fa7acb1
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-gmessages.pot
@@ -0,0 +1,125 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bridge-mautrix-gmessages.md:1
+msgid "Setting up Mautrix Google Messages bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:3
+msgid "The playbook can install and configure [mautrix-gmessages](https://github.com/mautrix/gmessages) for you, for bridging to [Google Messages](https://messages.google.com/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:5
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/gmessages/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:7
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:9
+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) for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:11
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:15
+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-gmessages.md:21
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:23
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:30
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:32
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:34
+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-gmessages.md:36
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:38
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:40
+msgid "To use the bridge, you need to start a chat with `@gmessagesbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:42
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:44
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:46
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:48
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:50
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:52
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:54
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:56
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:58
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:60
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-gmessages.md:62
+msgid "make sure you don't log out the `Mautrix-gmessages` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-googlechat.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-googlechat.pot
new file mode 100644
index 000000000..14dd76870
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-googlechat.pot
@@ -0,0 +1,145 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bridge-mautrix-googlechat.md:1
+msgid "Setting up Mautrix Google Chat bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:3
+msgid "The playbook can install and configure [mautrix-googlechat](https://github.com/mautrix/googlechat) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:5
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/googlechat/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:7
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:9
+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-googlechat.md:11
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:15
+msgid "To enable the [Google Chat](https://chat.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:21
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:23
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:30
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:32
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:34
+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-googlechat.md:36
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:38
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:40
+msgid "To use the bridge, you need to start a chat with `googlechat bridge bot` with handle `@googlechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:42
+msgid "Send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:44
+msgid "Automatic login may not work. If it does not, reload the page and select the \"Manual login\" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:46
+msgid "Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:48
+msgid "You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/googlechat/authentication.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:50
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:52
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:54
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:56
+msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:58
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:60
+msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:62
+msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:64
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:66
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:68
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:70
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-googlechat.md:72
+msgid "make sure you don't log out the `Mautrix-googlechat` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-hangouts.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-hangouts.pot
new file mode 100644
index 000000000..e05c6c2eb
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-hangouts.pot
@@ -0,0 +1,145 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bridge-mautrix-hangouts.md:1
+msgid "Setting up Mautrix Hangouts bridging (optional, deprecated)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:3
+msgid "💡 **Note**: This bridge has been deprecated in favor of [Google Chat bridge](https://github.com/mautrix/googlechat), which can be installed using [this playbook](configuring-playbook-bridge-mautrix-googlechat.md). Installing the mautrix-hangouts bridge is **no longer possible**. For now, this documentation page remains here for historical purposes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:5
+msgid "The playbook can install and configure [mautrix-hangouts](https://github.com/mautrix/hangouts) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:7
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/hangouts/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:9
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:11
+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 [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:13
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:15
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:17
+msgid "To enable the [Google Hangouts](https://hangouts.google.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:23
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:25
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:32
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:34
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:36
+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-hangouts.md:38
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:40
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:42
+msgid "To use the bridge, you need to start a chat with `Hangouts bridge bot` with handle `@hangoutsbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:44
+msgid "Send `login` to the bridge bot to receive a link to the portal from which you can enable the bridging. Open the link sent by the bot and follow the instructions."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:46
+msgid "Automatic login may not work. If it does not, reload the page and select the \"Manual login\" checkbox before starting. Manual login involves logging into your Google account normally and then manually getting the OAuth token from browser cookies with developer tools."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:48
+msgid "Once logged in, recent chats should show up as new conversations automatically. Other chats will get portals as you receive messages."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:50
+msgid "You can learn more about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/hangouts/authentication.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:52
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:54
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:56
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:58
+msgid "Method 1: automatically, by enabling Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:60
+msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:62
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:64
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:66
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:68
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:70
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-hangouts.md:72
+msgid "make sure you don't log out the `Mautrix-Hangouts` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-instagram.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-instagram.pot
new file mode 100644
index 000000000..83bc228d6
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-instagram.pot
@@ -0,0 +1,97 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-bridge-mautrix-instagram.md:1
+msgid "Setting up Mautrix Instagram bridging (optional, deprecated)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:3
+msgid "**Note**: This bridge has been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, which can be installed using [this playbook](configuring-playbook-bridge-mautrix-meta-instagram.md). Consider using that bridge instead of this one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:5
+msgid "The playbook can install and configure [mautrix-instagram](https://github.com/mautrix/instagram) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:7
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/instagram/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:11
+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-instagram.md:17
+msgid "There are some additional things you may wish to configure about the bridge before you continue."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:19
+msgid "Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:29
+msgid "If you would like to be able to administrate the bridge from your account it can be configured like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:43
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-instagram/defaults/main.yml` to find other things you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:45
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:47
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:54
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:56
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:58
+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-instagram.md:60
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:62
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:64
+msgid "To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:66
+msgid "Send `login YOUR_INSTAGRAM_EMAIL_ADDRESS YOUR_INSTAGRAM_PASSWORD` to the bridge bot to enable bridging for your instagram/Messenger account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-instagram.md:68
+msgid "You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/instagram/authentication.html)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-instagram.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-instagram.pot
new file mode 100644
index 000000000..6a658af27
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-instagram.pot
@@ -0,0 +1,205 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bridge-mautrix-meta-instagram.md:1
+msgid "Setting up Instagram bridging via Mautrix Meta (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:3
+msgid "The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:5
+msgid "Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:7
+msgid "This documentation page only deals with the bridge's ability to bridge to Instagram. For bridging to Facebook/Messenger, see [Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:11
+msgid "Migrating from the old mautrix-instagram bridge"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:13
+msgid "If you've been using the [mautrix-instagram](./configuring-playbook-bridge-mautrix-instagram.md) bridge, **you'd better get rid of it first** or the 2 bridges will be in conflict:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:15
+msgid "both trying to use `@instagrambot:example.com` as their username. This conflict may be resolved by adjusting `matrix_mautrix_instagram_appservice_bot_username` or `matrix_mautrix_meta_instagram_appservice_username`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:16
+msgid "both trying to bridge the same DMs"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:18
+msgid "To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@instagrambot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:20
+msgid "Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:22
+msgid "Enable Appservice Double Puppet (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:24
+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-meta-instagram.md:26
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:28
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:30
+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-meta-instagram.md:36
+msgid "Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:38
+msgid "Bridge permissions"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:40
+msgid "By default, any user on your homeserver will be able to use the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:42
+msgid "Different levels of permission can be granted to users:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:44
+msgid "`relay` - Allowed to be relayed through the bridge, no access to commands"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:45
+msgid "`user` - Use the bridge with puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:46
+msgid "`admin` - Use and administer the bridge"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:48
+msgid "The permissions are following the sequence: nothing < `relay` < `user` < `admin`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:50
+msgid "The default permissions are set via `matrix_mautrix_meta_instagram_bridge_permissions_default` and are somewhat like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:59
+msgid "If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:61
+msgid "You may redefine `matrix_mautrix_meta_instagram_bridge_permissions_default` any way you see fit, or add extra permissions using `matrix_mautrix_meta_instagram_bridge_permissions_custom` like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:68
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-instagram/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:70
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:72
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:79
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:81
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:83
+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-meta-instagram.md:85
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:87
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:89
+msgid "To use the bridge, you need to start a chat with `@instagrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:91
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:93
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:95
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:97
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:99
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:101
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:103
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:105
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:107
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:109
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-instagram.md:111
+msgid "make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-messenger.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-messenger.pot
new file mode 100644
index 000000000..16fece3ae
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-meta-messenger.pot
@@ -0,0 +1,241 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bridge-mautrix-meta-messenger.md:1
+msgid "Setting up Messenger bridging via Mautrix Meta (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:3
+msgid "The playbook can install and configure the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:5
+msgid "Since this bridge component can bridge to both [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/) and you may wish to do both at the same time, the playbook makes it available via 2 different Ansible roles (`matrix-bridge-mautrix-meta-messenger` and `matrix-bridge-mautrix-meta-instagram`). The latter is a reconfigured copy of the first one (created by `just rebuild-mautrix-meta-instagram` and `bin/rebuild-mautrix-meta-instagram.sh`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:7
+msgid "This documentation page only deals with the bridge's ability to bridge to Facebook Messenger. For bridging to Instagram, see [Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:11
+msgid "Migrating from the old mautrix-facebook bridge"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:13
+msgid "If you've been using the [mautrix-facebook](./configuring-playbook-bridge-mautrix-facebook.md) bridge, it's possible to migrate the database using [instructions from the bridge documentation](https://docs.mau.fi/bridges/go/meta/facebook-migration.html) (advanced)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:15
+msgid "Then you may wish to get rid of the Facebook bridge. To do so, send a `clean-rooms` command to the management room with the old bridge bot (`@facebookbot:example.com`). It gives you a list of portals and groups of portals you may purge. Proceed with sending commands like `clean recommended`, etc."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:17
+msgid "Then, consider disabling the old bridge in your configuration, so it won't recreate the portals when you receive new messages."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:19
+msgid "**Note**: the user ID of the new bridge bot is `@messengerbot:example.com`, not `@facebookbot:example.com`. After disabling the old bridge, its bot user will stop responding to a command."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:21
+msgid "Enable Appservice Double Puppet (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:23
+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-meta-messenger.md:25
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:27
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:29
+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-meta-messenger.md:35
+msgid "Before proceeding to [re-running the playbook](./installing.md), you may wish to adjust the configuration further. See below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:37
+msgid "Bridge mode"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:39
+msgid "As mentioned above, the [mautrix-meta](https://github.com/mautrix/meta) bridge supports multiple modes of operation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:41
+msgid "The bridge can pull your Messenger messages via 3 different methods:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:43
+msgid "(`facebook`) Facebook via `facebook.com`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:44
+msgid "(`facebook-tor`) Facebook via `facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion` ([Tor](https://www.torproject.org/)) - does not currently proxy media downloads"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:45
+msgid "(default) (`messenger`) Messenger via `messenger.com` - usable even without a Facebook account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:47
+msgid "You may switch the mode via the `matrix_mautrix_meta_messenger_meta_mode` variable. The playbook defaults to the `messenger` mode, because it's most universal (every Facebook user has a Messenger account, but the opposite is not true)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:49
+msgid "Note that switching the mode (especially between `facebook*` and `messenger`) will intentionally make the bridge use another database (`matrix_mautrix_meta_facebook` or `matrix_mautrix_meta_messenger`) to isolate the 2 instances. Switching between Tor and non-Tor may be possible without dataloss, but your mileage may vary. Before switching to a new mode, you may wish to de-configure the old one (send `help` to the bridge bot and unbridge your portals, etc.)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:51
+msgid "Bridge permissions"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:53
+msgid "By default, any user on your homeserver will be able to use the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:55
+msgid "Different levels of permission can be granted to users:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:57
+msgid "`relay` - Allowed to be relayed through the bridge, no access to commands"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:58
+msgid "`user` - Use the bridge with puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:59
+msgid "`admin` - Use and administer the bridge"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:61
+msgid "The permissions are following the sequence: nothing < `relay` < `user` < `admin`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:63
+msgid "The default permissions are set via `matrix_mautrix_meta_messenger_bridge_permissions_default` and are somewhat like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:72
+msgid "If you don't define the `matrix_admin` in your configuration (e.g. `matrix_admin: @alice:example.com`), then there's no admin by default."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:74
+msgid "You may redefine `matrix_mautrix_meta_messenger_bridge_permissions_default` any way you see fit, or add extra permissions using `matrix_mautrix_meta_messenger_bridge_permissions_custom` like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:81
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:83
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:85
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:92
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:94
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:96
+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-meta-messenger.md:98
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:100
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:102
+msgid "To use the bridge, you need to start a chat with `@messengerbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain). Note that the user ID of the bridge's bot is not `@facebookbot:example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:104
+msgid "You then need to send a `login` command and follow the bridge bot's instructions."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:106
+msgid "Given that the bot is configured in `messenger` [bridge mode](#bridge-mode) by default, you will need to log in to [messenger.com](https://messenger.com/) (not `facebook.com`!) and obtain the cookies from there as per [the bridge's authentication instructions](https://docs.mau.fi/bridges/go/meta/authentication.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:108
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:110
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:112
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:114
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:116
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:118
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:120
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:122
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:124
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:126
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-meta-messenger.md:128
+msgid "make sure you don't log out the session for which you obtained an access token some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-signal.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-signal.pot
new file mode 100644
index 000000000..732776d30
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-signal.pot
@@ -0,0 +1,193 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bridge-mautrix-signal.md:1
+msgid "Setting up Mautrix Signal bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:3
+msgid "The playbook can install and configure [mautrix-signal](https://github.com/mautrix/signal) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:5
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/signal/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:7
+msgid "**Note**: This revamped version of the [mautrix-signal (legacy)](configuring-playbook-bridge-mautrix-signal.md) may increase the CPU usage of your homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:9
+msgid "Prerequisites (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:11
+msgid "Prepare Postgres database on external Postgres server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:13
+msgid "If you're running with the Postgres database server integrated by the playbook (which is the default), you don't need to do anything special and can easily proceed with installing."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:15
+msgid "However, if you're [using an external Postgres server](configuring-playbook-external-postgres.md), you'd need to manually prepare a Postgres database for this bridge and adjust the variables related to that (`matrix_mautrix_signal_database_*`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:17
+msgid "Enable Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:19
+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-signal.md:21
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:23
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:25
+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-signal.md:31
+msgid "There are some additional things you may wish to configure about the bridge before you continue."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:33
+msgid "By default, any user on your homeserver will be able to use the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:35
+msgid "Different levels of permission can be granted to users:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:37
+msgid "relay - Allowed to be relayed through the bridge, no access to commands;"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:38
+msgid "user - Use the bridge with puppeting;"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:39
+msgid "admin - Use and administer the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:41
+msgid "The permissions are following the sequence: nothing < relay < user < admin."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:43
+msgid "The default permissions are set as follows:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:51
+msgid "If you want to augment the preset permissions, you might want to set the additional permissions with the following settings in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:60
+msgid "This will add the admin permission to the specific user, while keeping the default permissions."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:62
+msgid "In case you want to replace the default permissions settings **completely**, populate the following item within your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:70
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-signal/templates/config.yaml.j2` to find more information on the permissions settings and other options you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:72
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:74
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:81
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:83
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:85
+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-signal.md:87
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:89
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:91
+msgid "To use the bridge, you need to start a chat with `@signalbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:93
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:95
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:97
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:99
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:101
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:103
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:105
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:107
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:109
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:111
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-signal.md:113
+msgid "make sure you don't log out the `Mautrix-Signal` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-slack.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-slack.pot
new file mode 100644
index 000000000..30988952e
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-slack.pot
@@ -0,0 +1,193 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bridge-mautrix-slack.md:1
+msgid "Setting up Mautrix Slack bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:3
+msgid "**Note**: bridging to [Slack](https://slack.com/) can also happen via the [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:4
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:5
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:7
+msgid "The playbook can install and configure [mautrix-slack](https://github.com/mautrix/slack) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:9
+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:11
+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:13
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:15
+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:17
+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:19
+msgid "Enable Appservice Double Puppet (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:21
+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:23
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:25
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:27
+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:33
+msgid "You may optionally wish to add some [Additional configuration](#additional-configuration), or to [prepare for double-puppeting](#set-up-double-puppeting) before the initial installation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:35
+msgid "Additional configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:37
+msgid "There are some additional options you may wish to configure with the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:39
+msgid "Take a look at:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:41
+msgid "`roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:42
+msgid "`roles/custom/matrix-bridge-mautrix-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_mautrix_slack_configuration_extension_yaml` variable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:44
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:46
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:53
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:55
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:57
+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:59
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:61
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:63
+msgid "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:64
+msgid "If you would like to login to Slack using a token, send the `login-token` command, otherwise, send the `login-password` command. Read [here](https://docs.mau.fi/bridges/go/slack/authentication.html) on how to retrieve your token and cookie token."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:65
+msgid "The bot should respond with \"Successfully logged into <email> for team <workspace>\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:66
+msgid "Now that you're logged in, you can send `help` to the bot to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:67
+msgid "Slack channels should automatically begin bridging if you authenticated using a token. Otherwise, you must wait to receive a message in the channel if you used password authentication."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:69
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:71
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:73
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:75
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:77
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:79
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:81
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:83
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:85
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:87
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-slack.md:89
+msgid "make sure you don't log out the `Mautrix-Slack` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-telegram.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-telegram.pot
new file mode 100644
index 000000000..cf64deff8
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-telegram.pot
@@ -0,0 +1,149 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bridge-mautrix-telegram.md:1
+msgid "Setting up Mautrix Telegram bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:3
+msgid "The playbook can install and configure [mautrix-telegram](https://github.com/mautrix/telegram) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:5
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/telegram/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:7
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:9
+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-telegram.md:11
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:15
+msgid "You'll need to obtain API keys from [https://my.telegram.org/apps](https://my.telegram.org/apps) and then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:23
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:25
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:32
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:34
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:36
+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-telegram.md:38
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:40
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:42
+msgid "To use the bridge, you need to start a chat with `@telegrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:44
+msgid "If you want to use the relay-bot feature ([relay bot documentation](https://docs.mau.fi/bridges/python/telegram/relay-bot.html)), which allows anonymous user to chat with telegram users, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:54
+msgid "You might also want to give permissions to administrate the bot:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:63
+msgid "More details about permissions in this example: https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-config.yaml#L410"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:65
+msgid "If you like to exclude all groups from syncing and use the Telgeram-Bridge only for direct chats, you can add the following additional playbook configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:71
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:73
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:75
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:77
+msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:79
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:81
+msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:83
+msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:85
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:87
+msgid "**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:89
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:91
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:93
+msgid "send `login-matrix` to the bot and follow instructions about how to send the access token to it"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:95
+msgid "make sure you don't log out the `Mautrix-Telegram` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-twitter.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-twitter.pot
new file mode 100644
index 000000000..612714ca8
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-twitter.pot
@@ -0,0 +1,141 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bridge-mautrix-twitter.md:1
+msgid "Setting up Mautrix Twitter bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:3
+msgid "**Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md) bridge supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:5
+msgid "The playbook can install and configure [mautrix-twitter](https://github.com/mautrix/twitter) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:7
+msgid "See the project's [documentation](https://github.com/mautrix/twitter/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:9
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:11
+msgid "Enable Appservice Double Puppet (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:13
+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-twitter.md:15
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:17
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:19
+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-twitter.md:25
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:27
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:34
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:36
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:38
+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-twitter.md:40
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:42
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:44
+msgid "You then need to start a chat with `@twitterbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:45
+msgid "Send login-cookie to start the login. The bot should respond with instructions on how to proceed."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:47
+msgid "You can learn more here about authentication from the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/python/twitter/authentication.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:49
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:51
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:53
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:55
+msgid "Method 1: automatically, by enabling Appservice Double Puppet"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:57
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:59
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:61
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:63
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:65
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:67
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-twitter.md:69
+msgid "make sure you don't log out the `Mautrix-Slack` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-whatsapp.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-whatsapp.pot
new file mode 100644
index 000000000..b393ba2e3
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-whatsapp.pot
@@ -0,0 +1,145 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-bridge-mautrix-whatsapp.md:1
+msgid "Setting up Mautrix Whatsapp bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:3
+msgid "The playbook can install and configure [mautrix-whatsapp](https://github.com/mautrix/whatsapp) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:5
+msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/whatsapp/index.html) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:7
+msgid "Prerequisite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:9
+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-whatsapp.md:11
+msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:15
+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-whatsapp.md:21
+msgid "Whatsapp multidevice beta is required, now it is enough if Whatsapp is connected to the Internet every 2 weeks."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:23
+msgid "The relay bot functionality is off by default. If you would like to enable the relay bot, add the following to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:29
+msgid "By default, only admins are allowed to set themselves as relay users. To allow anyone on your homeserver to set themselves as relay users add this to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:35
+msgid "If you want to activate the relay bot in a room, send `!wa set-relay`. To deactivate, send `!wa unset-relay`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:37
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:39
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:46
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:48
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:50
+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-whatsapp.md:52
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:54
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:56
+msgid "To use the bridge, you need to start a chat with `@whatsappbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:58
+msgid "💡 Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:60
+msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:62
+msgid "To set it up, you have 2 ways of going about it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:64
+msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:66
+msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:68
+msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:70
+msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:72
+msgid "Method 2: manually, by asking each user to provide a working access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:74
+msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:76
+msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:78
+msgid "send the access token to the bot. Example: `login-matrix MATRIX_ACCESS_TOKEN_HERE`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-whatsapp.md:80
+msgid "make sure you don't log out the `Mautrix-Whatsapp` device some time in the future, as that would break the Double Puppeting feature"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-wsproxy.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-wsproxy.pot
new file mode 100644
index 000000000..2861d8a9a
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mautrix-wsproxy.pot
@@ -0,0 +1,101 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 09:53+0200\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-bridge-mautrix-wsproxy.md:1
+msgid "Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:3
+msgid "The playbook can install and configure [mautrix-wsproxy](https://github.com/mautrix/wsproxy) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:5
+msgid "See the project's [documentation](https://github.com/mautrix/wsproxy/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:9
+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-wsproxy.md:21
+msgid "Note that the tokens must match what is compiled into the [mautrix-imessage](https://github.com/mautrix/imessage) bridge running on your Mac or Android device."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:23
+msgid "Adjusting the wsproxy URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:25
+msgid "By default, this playbook installs wsproxy on the `wsproxy.` subdomain (`wsproxy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:27
+msgid "By tweaking the `matrix_mautrix_wsproxy_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:29
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:36
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:38
+msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the wsproxy domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:40
+msgid "By default, you will need to create a CNAME record for `wsproxy`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:42
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:44
+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-bridge-mautrix-wsproxy.md:51
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:53
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.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-wsproxy.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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:59
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mautrix-wsproxy.md:61
+msgid "Follow the [matrix-imessage documenation](https://docs.mau.fi/bridges/go/imessage/index.html) for running `android-sms` and/or `matrix-imessage` on your device(s)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-discord.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-discord.pot
new file mode 100644
index 000000000..75de1e07f
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-discord.pot
@@ -0,0 +1,97 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 23:17+0900\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-bridge-mx-puppet-discord.md:1
+msgid "Setting up MX Puppet Discord bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:3
+msgid "**Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md)and [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:4
+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-mx-puppet-discord.md:5
+msgid "For personal use with a discord account we recommend the [mautrix-discord](configuring-playbook-bridge-mautrix-discord.md) bridge, because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:7
+msgid "The playbook can install and configure [mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:9
+msgid "See the project's [documentation](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:13
+msgid "To enable the [Discord](https://discordapp.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:19
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:21
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:28
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:30
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:32
+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-mx-puppet-discord.md:34
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:36
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:38
+msgid "To use the bridge, you need to start a chat with `Discord Puppet Bridge` with the handle `@_discordpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:40
+msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-discord [documentation](https://gitlab.com/mx-puppet/discord/mx-puppet-discord) for more information about how to configure the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:42
+msgid "Once logged in, send `list` to the bot user to list the available rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:44
+msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-discord.md:46
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-groupme.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-groupme.pot
new file mode 100644
index 000000000..0ba57698d
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-groupme.pot
@@ -0,0 +1,89 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 23:17+0900\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-bridge-mx-puppet-groupme.md:1
+msgid "Setting up MX Puppet GroupMe bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:3
+msgid "The playbook can install and configure [mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:5
+msgid "See the project's [documentation](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:9
+msgid "To enable the [GroupMe](https://groupme.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:15
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:17
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:24
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:26
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:28
+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-mx-puppet-groupme.md:30
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:32
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:34
+msgid "To use the bridge, you need to start a chat with `GroupMe Puppet Bridge` with the handle `@_groupmepuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:36
+msgid "One authentication method is available."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:38
+msgid "To link your GroupMe account, go to [dev.groupme.com](https://dev.groupme.com/), sign in, and select \"Access Token\" from the top menu. Copy the token and message the bridge with:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:44
+msgid "Once logged in, send `listrooms` to the bot user to list the available rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:46
+msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-groupme.md:48
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-instagram.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-instagram.pot
new file mode 100644
index 000000000..a6405e758
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-instagram.pot
@@ -0,0 +1,101 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 23:17+0900\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-bridge-mx-puppet-instagram.md:1
+msgid "Setting up MX Puppet Instagram bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:3
+msgid "The playbook can install and configure [mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:5
+msgid "This allows you to bridge Instagram DirectMessages into Matrix."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:9
+msgid "To enable the [Instagram](https://www.instagram.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:15
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:17
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:24
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:26
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:28
+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-mx-puppet-instagram.md:30
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:32
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:34
+msgid "To use the bridge, you need to start a chat with `Instagram Puppet Bridge` with the handle `@_instagrampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:36
+msgid "Send `link <username> <password>` to the bridge bot to link your instagram account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:38
+msgid "The `list` commands shows which accounts are linked and which `puppetId` is associated."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:40
+msgid "For double-puppeting, you probably want to issue these commands:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:42
+msgid "`settype $puppetId puppet` to enable puppeting for the link (instead of relaying)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:43
+msgid "`setautoinvite $puppetId 1` to automatically invite you to chats"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:44
+msgid "`setmatrixtoken $accessToken` to set the access token to enable puppeting from the other side (the \"double\" in double puppeting)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:46
+msgid "If you are linking only one Instagram account, your `$puppetId` is probably 1, but use the `list` command find out."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-instagram.md:48
+msgid "Send `help` to the bot to see the available commands. At the time of writing, not every command is fully implemented."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-skype.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-skype.pot
new file mode 100644
index 000000000..4984df1cc
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-skype.pot
@@ -0,0 +1,29 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-bridge-mx-puppet-skype.md:1
+msgid "Setting up MX Puppet Skype bridging (optional, removed)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:3
+msgid "The playbook used to be able to install and configure [mx-puppet-skype](https://github.com/Sorunome/mx-puppet-skype), but no longer includes this component, because it has been broken and unmaintained for a long time."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-skype.md:5
+msgid "Bridging to [Skype](https://www.skype.com/) can also happen via the [go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md) bridge supported by the playbook."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-slack.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-slack.pot
new file mode 100644
index 000000000..3f32ada11
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-slack.pot
@@ -0,0 +1,97 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 23:17+0900\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-bridge-mx-puppet-slack.md:1
+msgid "Setting up MX Puppet Slack bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:3
+msgid "**Note**: bridging to [Slack](https://slack.com) can also happen via the [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) and [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges supported by the playbook. Note that `matrix-appservice-slack` 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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:5
+msgid "The playbook can install and configure [mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:7
+msgid "See the project's [documentation](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:9
+msgid "Prerequisite"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:11
+msgid "Follow the [OAuth credentials](https://gitlab.com/mx-puppet/slack/mx-puppet-slack#option-2-oauth) instructions to create a new Slack app, setting the redirect URL to `https://matrix.example.com/slack/oauth`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:15
+msgid "To enable the [Slack](https://slack.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:24
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:26
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:33
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:35
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:37
+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-mx-puppet-slack.md:39
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:41
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:43
+msgid "To use the bridge, you need to start a chat with `Slack Puppet Bridge` with the handle `@_slackpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:45
+msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-slack [documentation](https://gitlab.com/mx-puppet/slack/mx-puppet-slack) for more information about how to configure the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:47
+msgid "Once logged in, send `list` to the bot user to list the available rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:49
+msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-slack.md:51
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-steam.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-steam.pot
new file mode 100644
index 000000000..8d2710c66
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-steam.pot
@@ -0,0 +1,85 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 23:17+0900\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-bridge-mx-puppet-steam.md:1
+msgid "Setting up MX Puppet Steam bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:3
+msgid "The playbook can install and configure [mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:5
+msgid "See the project's [documentation](https://github.com/icewind1991/mx-puppet-steam/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:9
+msgid "To enable the [Steam](https://steampowered.com/) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:15
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:17
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:24
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:26
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:28
+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-mx-puppet-steam.md:30
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:32
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:34
+msgid "To use the bridge, you need to start a chat with `Steam Puppet Bridge` with the handle `@_steampuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:36
+msgid "Three authentication methods are available, Legacy Token, OAuth and xoxc token. See mx-puppet-steam [documentation](https://github.com/icewind1991/mx-puppet-steam) for more information about how to configure the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:38
+msgid "Once logged in, send `list` to the bot user to list the available rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:40
+msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-steam.md:42
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-twitter.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-twitter.pot
new file mode 100644
index 000000000..d0c946e5a
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-mx-puppet-twitter.pot
@@ -0,0 +1,97 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 23:17+0900\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-bridge-mx-puppet-twitter.md:1
+msgid "Setting up MX Puppet Twitter bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:3
+msgid "**Note**: bridging to [Twitter](https://twitter.com/) can also happen via the [mautrix-twitter](configuring-playbook-bridge-mautrix-twitter.md) bridge supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:5
+msgid "The playbook can install and configure [mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:7
+msgid "See the project's [documentation](https://github.com/Sorunome/mx-puppet-twitter/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:9
+msgid "Prerequisite"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:11
+msgid "Make an app on [developer.twitter.com](https://developer.twitter.com/en/apps)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:15
+msgid "To enable the [Twitter](https://twitter.com) bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:26
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:28
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:35
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:37
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:39
+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-mx-puppet-twitter.md:41
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:43
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:45
+msgid "To use the bridge, you need to start a chat with `Twitter Puppet Bridge` with the handle `@_twitterpuppet_bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:47
+msgid "To log in, use `link` and click the link."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:49
+msgid "Once logged in, send `list` to the bot user to list the available rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:51
+msgid "Clicking rooms in the list will result in you receiving an invitation to the bridged room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-mx-puppet-twitter.md:53
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-postmoogle.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-postmoogle.pot
new file mode 100644
index 000000000..b9b280c5d
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-postmoogle.pot
@@ -0,0 +1,137 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 23:17+0900\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-bridge-postmoogle.md:1
+msgid "Setting up Postmoogle email bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:3
+msgid "**Note**: email bridging can also happen via the [email2matrix](configuring-playbook-email2matrix.md) bridge supported by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:5
+msgid "The playbook can install and configure [Postmoogle](https://github.com/etkecc/postmoogle) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:7
+msgid "Postmoogle is a bridge you can use to have its bot user forward emails to Matrix rooms. It runs an SMTP email server and allows you to assign mailbox addresses to the rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:9
+msgid "See the project's [documentation](https://github.com/etkecc/postmoogle/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:13
+msgid "Open the following ports on your server to be able to receive incoming emails:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:15
+msgid "`25/tcp`: SMTP"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:16
+msgid "`587/tcp`: Submission (TLS-encrypted SMTP)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:18
+msgid "If you don't open these ports, you will still be able to send emails, but not receive any."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:20
+msgid "These port numbers are configurable via the `matrix_postmoogle_smtp_host_bind_port` and `matrix_postmoogle_submission_host_bind_port` variables, but other email servers will try to deliver on these default (standard) ports, so changing them is of little use."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:22
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:24
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:45
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:47
+msgid "You will also need to add several DNS records so that Postmoogle can send emails. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:49
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:51
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:58
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:60
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create a user account of the bridge's bot."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:62
+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-postmoogle.md:64
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:66
+msgid "If you change the bridge's bot password (`matrix_postmoogle_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:68
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:70
+msgid "To use the bridge, invite the `@postmoogle:example.com` bot user into a room you want to use as a mailbox."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:72
+msgid "Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with the email address `NAME@matrix.example.com`. Emails sent to that email address will be forwarded to the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:74
+msgid "Send `!pm help` to the bot in the room to see the available commands."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:76
+msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/postmoogle)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:78
+msgid "Debug/Logs"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:80
+msgid "As with all other services, you can find their logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-postmoogle`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:82
+msgid "The default logging level for this bridge is `INFO`, but you can increase it to `DEBUG` with the following additional configuration:"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-wechat.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-wechat.pot
new file mode 100644
index 000000000..4f6761621
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-bridge-wechat.pot
@@ -0,0 +1,73 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 09:53+0200\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-bridge-wechat.md:1
+msgid "Setting up WeChat bridging (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:3
+msgid "The playbook can install and configure the [matrix-wechat](https://github.com/duo/matrix-wechat) bridge for you (for bridging to the [WeChat](https://www.wechat.com/) network)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:5
+msgid "See the project's [documentation](https://github.com/duo/matrix-wechat/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:9
+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-wechat.md:15
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:17
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:24
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:26
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:28
+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-wechat.md:30
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:32
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:34
+msgid "Once the bridge is installed, start a chat with `@wechatbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bridge-wechat.md:36
+msgid "Send `help` to the bot to see the available commands."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-cactus-comments.pot b/i18n/translation-templates/docs/configuring-playbook-cactus-comments.pot
new file mode 100644
index 000000000..9e3e8c613
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-cactus-comments.pot
@@ -0,0 +1,165 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 23:17+0900\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-cactus-comments.md:1
+msgid "Setting up Cactus Comments (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:3
+msgid "The playbook can install and configure the [Cactus Comments](https://cactus.chat) system for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:5
+msgid "Cactus Comments is a **federated comment system** built on Matrix. It respects your privacy, and puts you in control."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:7
+msgid "See the project's [documentation](https://cactus.chat/docs/getting-started/introduction/) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:9
+msgid "The playbook contains 2 roles for configuring different pieces of the Cactus Comments system:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:11
+msgid "`matrix-cactus-comments` - the backend appservice integrating with the Matrix homeserver"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:13
+msgid "`matrix-cactus-comments-client` - a static website server serving the [cactus-client](https://cactus.chat/docs/client/introduction/) static assets (`cactus.js` and `styles.css`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:15
+msgid "You can enable whichever component you need (typically both)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:17
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:19
+msgid "To enable Cactus Comments, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:41
+msgid "Adjusting the Cactus Comments' client URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:43
+msgid "By default, this playbook installs Cactus Comments' client on the `matrix.` subdomain, at the `/cactus-comments` path (https://matrix.example.com/cactus-comments). 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-cactus-comments.md:45
+msgid "By tweaking the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_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-cactus-comments.md:47
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:56
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:58
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Cactus Comments' client domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:60
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:62
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:64
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:66
+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-cactus-comments.md:73
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:75
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:77
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:79
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:81
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:83
+msgid "Upon starting Cactus Comments, a `bot.cactusbot` user account is created automatically."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:85
+msgid "To get started, send `help` to the `@bot.cactusbot:example.com` bot to confirm it's working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:87
+msgid "Then, register a site by sending `register <YourSiteName>` (where `<YourSiteName>` is a unique identifier you choose. It does not have to match your domain). You will then be invited into a moderation room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:89
+msgid "Now you are good to go and can embed the comment section on your website!"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:91
+msgid "Embed Cactus Comments"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:93
+msgid "The official [documentation](https://cactus.chat/docs/getting-started/quick-start/) provides a useful guide to embed Cactus Comments on your website."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:95
+msgid "After including the JavaScript and CSS asset files, insert a `<div>` where you'd like to display the comment section:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:101
+msgid "Then, you need to initialize the comment section. Make sure to replace `example.com` with your base domain and `<YourSiteName>` with the one that has been registered above:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:115
+msgid "Adjust the domain name for self-hosting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:117
+msgid "To have the assets served from your homeserver (not from `cactus.chat`), you need to adjust the domain name on the official documentation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:119
+msgid "Make sure to replace `example.com` with your base domain before you include the following lines, instead of the one provided by the official documentation:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-cactus-comments.md:126
+msgid "**Note**: if the `matrix_cactus_comments_client_hostname` and `matrix_cactus_comments_client_path_prefix` variables are tweaked, you would need to adjust the URLs of the assets accordingly."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-client-cinny.pot b/i18n/translation-templates/docs/configuring-playbook-client-cinny.pot
new file mode 100644
index 000000000..082f75d13
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-client-cinny.pot
@@ -0,0 +1,97 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-cinny.md:1
+msgid "Setting up Cinny (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:3
+msgid "This playbook can install the [Cinny](https://github.com/ajbura/cinny) Matrix web client for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:5
+msgid "Cinny 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)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:7
+msgid "💡 **Note**: the latest version of Cinny is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:9
+msgid "[app.cinny.in](https://app.cinny.in), hosted by the [Cinny](https://cinny.in/) developers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:13
+msgid "To enable Cinny, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:19
+msgid "Adjusting the Cinny URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:21
+msgid "By default, this playbook installs Cinny on the `cinny.` subdomain (`cinny.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:23
+msgid "By tweaking the `matrix_client_cinny_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:25
+msgid "While a `matrix_client_cinny_path_prefix` variable exists for tweaking the path-prefix, it's [not supported anymore](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Cinny requires an application rebuild (with a tweaked build config) to be functional under a custom path."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:27
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:34
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:36
+msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the Cinny domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:38
+msgid "By default, you will need to create a CNAME record for `cinny`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:40
+msgid "If you've adjusted `matrix_client_cinny_hostname`, you will need to adjust your DNS configuration accordingly."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:42
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-cinny.md:44
+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-cinny.md:51
+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-cinny.md:53
+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 ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-client-element-web.pot b/i18n/translation-templates/docs/configuring-playbook-client-element-web.pot
new file mode 100644
index 000000000..62f9e84eb
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-client-element-web.pot
@@ -0,0 +1,145 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-element-web.md:1
+msgid "Configuring Element Web (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:3
+msgid "By default, this playbook installs the [Element Web](https://github.com/element-hq/element-web) Matrix client for you. If that's okay, you can skip this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:5
+msgid "💡 **Note**: the latest version of Element Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Applications, you can consider using it from there and avoiding the (small) overhead of self-hosting (by [disabling Element Web](#disabling-element-web)):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:7
+msgid "[app.element.io](https://app.element.io/), hosted by [Element](https://element.io/)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:8
+msgid "[app.etke.cc](https://app.etke.cc/), hosted by [etke.cc](https://etke.cc/)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:10
+msgid "Disabling Element Web"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:12
+msgid "If you'd like for the playbook to not install Element Web (or to uninstall it if it was previously installed), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:18
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:20
+msgid "The playbook provides some customization variables you could use to change Element Web's settings."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:22
+msgid "Their defaults are defined in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml) and they ultimately end up in the generated `/matrix/element/config.json` file (on the server). This file is generated from the [`roles/custom/matrix-client-element/templates/config.json.j2`](../roles/custom/matrix-client-element/templates/config.json.j2) template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:24
+msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:26
+msgid "Alternatively, **if there is no pre-defined variable** for an Element Web setting you wish to change:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:28
+msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Element Web's various settings that rarely get used."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:30
+msgid "or, you can **extend and override the default configuration** ([`config.json.j2`](../roles/custom/matrix-client-element/templates/config.json.j2)) by making use of the `matrix_client_element_configuration_extension_json_` variable. You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:32
+msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_element_configuration_default` (or `matrix_client_element_configuration`). You can find information about this in [`roles/custom/matrix-client-element/defaults/main.yml`](../roles/custom/matrix-client-element/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:34
+msgid "Themes"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:36
+msgid "To change the look of Element Web, you can define your own themes manually by using the `matrix_client_element_setting_defaults_custom_themes` setting."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:38
+msgid "Or better yet, you can automatically pull it all themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project by simply flipping a flag (`matrix_client_element_themes_enabled: true`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:40
+msgid "If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:42
+msgid "Note that for a custom theme to work well, all Element Web instances that you use must have the same theme installed."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:44
+msgid "Adjusting the Element Web URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:46
+msgid "By default, this playbook installs Element Web on the `element.` subdomain (`element.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:48
+msgid "By tweaking the `matrix_client_element_hostname` and `matrix_client_element_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-client-element-web.md:50
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:61
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:63
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Element Web domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:65
+msgid "By default, you will need to create a CNAME record for `element`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:67
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:69
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-element-web.md:71
+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-client-element-web.md:78
+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-element-web.md:80
+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 ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-client-hydrogen.pot b/i18n/translation-templates/docs/configuring-playbook-client-hydrogen.pot
new file mode 100644
index 000000000..7d010672a
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-client-hydrogen.pot
@@ -0,0 +1,85 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-hydrogen.md:1
+msgid "Setting up Hydrogen (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:3
+msgid "This playbook can install the [Hydrogen](https://github.com/element-hq/hydrogen-web) Matrix web client for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:5
+msgid "Hydrogen is a lightweight web client that supports mobile and legacy web browsers. It can be installed alongside or instead of Element Web."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:9
+msgid "To enable Hydrogen, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:15
+msgid "Adjusting the Hydrogen URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:17
+msgid "By default, this playbook installs Hydrogen on the `hydrogen.` subdomain (`hydrogen.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:19
+msgid "By tweaking the `matrix_client_hydrogen_hostname` and `matrix_client_hydrogen_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-client-hydrogen.md:21
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:32
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:34
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Hydrogen domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:36
+msgid "By default, you will need to create a CNAME record for `hydrogen`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:38
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:40
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-hydrogen.md:42
+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-client-hydrogen.md:49
+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-hydrogen.md:51
+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 ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-client-schildichat-web.pot b/i18n/translation-templates/docs/configuring-playbook-client-schildichat-web.pot
new file mode 100644
index 000000000..95c9e313d
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-client-schildichat-web.pot
@@ -0,0 +1,141 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-schildichat-web.md:1
+msgid "Setting up SchildiChat Web (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:3
+msgid "This playbook can install the [SchildiChat Web](https://github.com/SchildiChat/schildichat-desktop) Matrix client for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:5
+msgid "SchildiChat Web is a feature-rich messenger for Matrix based on Element Web with some extras and tweaks. It can be installed alongside or instead of Element Web."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:7
+msgid "💡 **Note**: the latest version of SchildiChat Web is also available on the web, hosted by 3rd parties. If you trust giving your credentials to the following 3rd party Single Page Application, you can consider using it from there:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:9
+msgid "[app.schildi.chat](https://app.schildi.chat/), hosted by the [SchildiChat](https://schildi.chat/) developers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:13
+msgid "To enable SchildiChat Web, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:19
+msgid "The playbook provides some customization variables you could use to change SchildiChat Web's settings."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:21
+msgid "Their defaults are defined in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml) and they ultimately end up in the generated `/matrix/schildichat/config.json` file (on the server). This file is generated from the [`roles/custom/matrix-client-schildichat/templates/config.json.j2`](../roles/custom/matrix-client-schildichat/templates/config.json.j2) template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:23
+msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:25
+msgid "Alternatively, **if there is no pre-defined variable** for a SchildiChat Web setting you wish to change:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:27
+msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of SchildiChat Web's various settings that rarely get used."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:29
+msgid "or, you can **extend and override the default configuration** ([`config.json.j2`](../roles/custom/matrix-client-schildichat/templates/config.json.j2)) by making use of the `matrix_client_schildichat_configuration_extension_json_` variable. You can find information about this in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:31
+msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_client_schildichat_configuration_default` (or `matrix_client_schildichat_configuration`). You can find information about this in [`roles/custom/matrix-client-schildichat/defaults/main.yml`](../roles/custom/matrix-client-schildichat/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:33
+msgid "Themes"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:35
+msgid "To change the look of SchildiChat Web, you can define your own themes manually by using the `matrix_client_schildichat_setting_defaults_custom_themes` setting."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:37
+msgid "Or better yet, you can automatically pull it all themes provided by the [aaronraimist/element-themes](https://github.com/aaronraimist/element-themes) project by simply flipping a flag (`matrix_client_schildichat_themes_enabled: true`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:39
+msgid "If you make your own theme, we encourage you to submit it to the **aaronraimist/element-themes** project, so that the whole community could easily enjoy it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:41
+msgid "Note that for a custom theme to work well, all SchildiChat Web instances that you use must have the same theme installed."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:43
+msgid "Adjusting the SchildiChat Web URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:45
+msgid "By default, this playbook installs SchildiChat Web on the `schildichat.` subdomain (`schildichat.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:47
+msgid "By tweaking the `matrix_client_schildichat_hostname` and `matrix_client_schildichat_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-client-schildichat-web.md:49
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:60
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:62
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the SchildiChat Web domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:64
+msgid "By default, you will need to create a CNAME record for `schildichat`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:66
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:68
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-client-schildichat-web.md:70
+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-client-schildichat-web.md:77
+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-schildichat-web.md:79
+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 ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-conduit.pot b/i18n/translation-templates/docs/configuring-playbook-conduit.pot
new file mode 100644
index 000000000..8368dfff9
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-conduit.pot
@@ -0,0 +1,93 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-conduit.md:1
+msgid "Configuring Conduit (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:3
+msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Conduit](https://conduit.rs)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:5
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:7
+msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:9
+msgid "**homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:13
+msgid "To use Conduit, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:19
+msgid "Creating the first user account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:21
+msgid "Since it is difficult to create the first user account on Conduit (see [famedly/conduit#276](https://gitlab.com/famedly/conduit/-/issues/276) and [famedly/conduit#354](https://gitlab.com/famedly/conduit/-/merge_requests/354)) and it does not support [registering users](registering-users.md) (via the command line or via the playbook) like Synapse and Dendrite do, we recommend the following procedure:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:23
+msgid "Add `matrix_conduit_allow_registration: true` to your `vars.yml` the first time around, temporarily"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:24
+msgid "Run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start` - see [Installing](installing.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:25
+msgid "Create your first user via Element Web or any other client which supports creating users"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:26
+msgid "Get rid of `matrix_conduit_allow_registration: true` from your `vars.yml`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:27
+msgid "Run the playbook again (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-conduit,start` would be enough this time)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:28
+msgid "You can now use your server safely. Additional users can be created by messaging the internal Conduit bot"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:30
+msgid "Configuring bridges / appservices"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:32
+msgid "Automatic appservice setup is currently unsupported when using Conduit. After setting up the service as usual you may notice that it is unable to start."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:34
+msgid "You will have to manually register appservices using the the [register-appservice](https://gitlab.com/famedly/conduit/-/blob/next/APPSERVICES.md) command."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-conduit.md:36
+msgid "Find the `registration.yaml` in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`, then pass the content to Conduit:"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-dendrite.pot b/i18n/translation-templates/docs/configuring-playbook-dendrite.pot
new file mode 100644
index 000000000..fc9470318
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-dendrite.pot
@@ -0,0 +1,89 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-dendrite.md:1
+msgid "Configuring Dendrite (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:3
+msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Dendrite](https://github.com/matrix-org/dendrite)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:5
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:7
+msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Dendrite). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:9
+msgid "**homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:13
+msgid "To use Dendrite, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:19
+msgid "The playbook provides lots of customization variables you could use to change Dendrite's settings."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:21
+msgid "Their defaults are defined in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml) and they ultimately end up in the generated `/matrix/dendrite/config/dendrite.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2) template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:23
+msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:25
+msgid "Alternatively, **if there is no pre-defined variable** for a Dendrite setting you wish to change:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:27
+msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Dendrite's various settings that rarely get used."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:29
+msgid "or, you can **extend and override the default configuration** ([`dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2)) by making use of the `matrix_dendrite_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:31
+msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_dendrite_configuration` (or `matrix_dendrite_configuration_yaml`). You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:33
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:35
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:42
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dendrite.md:44
+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 ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-dimension.pot b/i18n/translation-templates/docs/configuring-playbook-dimension.pot
new file mode 100644
index 000000000..3dbfc4bf3
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-dimension.pot
@@ -0,0 +1,178 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-dimension.md:1
+msgid "Setting up Dimension integration manager (optional, unmaintained)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:3
+#: ../../../docs/configuring-playbook-dimension.md:91
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:4
+msgid "Dimension is **[officially unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299)**. We recommend not bothering with installing it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:5
+msgid "This playbook now supports running Dimension in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`. Enabling Dimension, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:7
+msgid "The playbook can install and configure the [Dimension](https://dimension.t2bot.io) integration manager for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:9
+msgid "See the project's [documentation](https://github.com/turt2live/matrix-dimension/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:11
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:13
+msgid "Install Matrix services"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:15
+msgid "Dimension can only be installed after Matrix services are installed and running. If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) and come back here later."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:17
+msgid "Register a dedicated Matrix user (optional, recommended)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:19
+msgid "We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:21
+msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:23
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:29
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:31
+msgid "Dimension requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:33
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:35
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:37
+msgid "To enable Dimension, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`). Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:45
+msgid "Define admin users"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:47
+msgid "These users can modify the integrations this Dimension supports. Add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:55
+msgid "The admin interface is accessible within Element Web by accessing it in any room and clicking the cog wheel/settings icon in the top right. Currently, Dimension can be opened in Element Web by the \"Add widgets, bridges, & bots\" link in the room information."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:57
+msgid "Adjusting the Dimension URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:59
+msgid "By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:61
+msgid "By tweaking the `matrix_dimension_hostname` and `matrix_dimension_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-dimension.md:63
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:74
+msgid "**Note**: While there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You must serve Dimension at a dedicated subdomain."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:76
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:78
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:80
+msgid "By default, you will need to create a CNAME record for `dimension`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:82
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:84
+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-dimension.md:93
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:95
+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-dimension.md:97
+msgid "After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the Room info button (`i`) button in the top right corner of the screen, and then clicking Add widgets, bridges & bots."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:99
+msgid "Jitsi domain"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:101
+msgid "By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](./configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance. Currently there is no way to configure this via the playbook, see [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:103
+msgid "In the interim until the above limitation is resolved, an admin user needs to configure the domain via the admin ui once dimension is running. In Element Web, go to *Manage Integrations* &rightarrow; *Settings* &rightarrow; *Widgets* &rightarrow; *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:105
+msgid "Additional features"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:107
+msgid "To use a more custom configuration, you can define a `matrix_dimension_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_dimension_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-dimension/defaults/main.yml) of the Dimension component."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dimension.md:109
+msgid "You can find all configuration options on [GitHub page of Dimension project](https://github.com/turt2live/matrix-dimension/blob/master/config/default.yaml)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-dynamic-dns.pot b/i18n/translation-templates/docs/configuring-playbook-dynamic-dns.pot
new file mode 100644
index 000000000..274db91df
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-dynamic-dns.pot
@@ -0,0 +1,73 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-dynamic-dns.md:1
+msgid "Setting up Dynamic DNS (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:3
+msgid "The playbook can configure Dynamic DNS with [ddclient⁠](https://github.com/ddclient/ddclient) for you. It is a Perl client used to update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:5
+msgid "Most cloud providers / ISPs will charge you extra for a static IP address. If you're not hosting a highly reliable homeserver you can workaround this via dynamic DNS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:7
+msgid "Prerequisite"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:9
+msgid "You'll need to get a username and password from your DNS provider. Please consult with the provider about how to retrieve them."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:13
+msgid "To enable dynamic DNS, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:26
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:28
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:35
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:37
+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-dynamic-dns.md:39
+msgid "Additional Reading"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:41
+msgid "Additional resources:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-dynamic-dns.md:43
+msgid "https://matrix.org/docs/guides/free-small-matrix-server"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-email.pot b/i18n/translation-templates/docs/configuring-playbook-email.pot
new file mode 100644
index 000000000..7a23c69ef
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-email.pot
@@ -0,0 +1,85 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-email.md:1
+msgid "Adjusting email-sending settings (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:3
+msgid "By default, this playbook sets up an [Exim](https://www.exim.org/) email server through which all Matrix services send emails."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:5
+msgid "The email server would attempt to deliver emails directly to their final destination. This may or may not work, depending on your domain configuration (SPF settings, etc.)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:7
+msgid "By default, emails are sent from `matrix@matrix.example.com`, as specified by the `exim_relay_sender_address` playbook variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:9
+msgid "⚠️ **Warning**: On some cloud providers (Google Cloud, etc.), [port 25 is always blocked](https://cloud.google.com/compute/docs/tutorials/sending-mail/), so sending email directly from your server is not possible. You will need to [relay email through another SMTP server](#relaying-email-through-another-smtp-server)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:11
+msgid "💡 To improve deliverability, we recommend [relaying email through another SMTP server](#relaying-email-through-another-smtp-server) anyway."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:13
+msgid "Firewall settings"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:15
+msgid "No matter whether you send email directly (the default) or you relay email through another host (see how below), you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:17
+msgid "Relaying email through another SMTP server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:19
+msgid "If you'd like to relay email through another SMTP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:31
+msgid "**Note**: only the secure submission protocol (using `STARTTLS`, usually on port `587`) is supported. **SMTPS** (encrypted SMTP, usually on port `465`) **is not supported**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:33
+msgid "Configuations for sending emails using Sendgrid"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:35
+msgid "An easy and free SMTP service to set up is [Sendgrid](https://sendgrid.com/), the free tier allows for up to 100 emails per day to be sent. In the settings below you can provide any email for `exim_relay_sender_address`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:37
+msgid "The only other thing you need to change is the `exim_relay_relay_auth_password`, which you can generate at https://app.sendgrid.com/settings/api_keys. The API key password looks something like `SG.955oW1mLSfwds7i9Yd6IA5Q.q8GTaB8q9kGDzasegdG6u95fQ-6zkdwrPP8bOeuI`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:39
+msgid "Note that the `exim_relay_relay_auth_username` is literally the string `apikey`, it's always the same for Sendgrid."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:51
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email.md:53
+msgid "If you're having trouble with email not being delivered, it may be useful to inspect the mailer logs: `journalctl -f -u matrix-exim-relay`."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot b/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot
new file mode 100644
index 000000000..4b61b12f1
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-email2matrix.pot
@@ -0,0 +1,193 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-email2matrix.md:1
+msgid "Setting up Email2Matrix (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:3
+msgid "**Note**: email bridging can also happen via the [Postmoogle](configuring-playbook-bridge-postmoogle.md) bridge supported by the playbook. Postmoogle is much more powerful and easier to use, so we recommend that you use it, instead of Email2Matrix."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:5
+msgid "The playbook can install and configure [email2matrix](https://github.com/devture/email2matrix) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:7
+msgid "See the project's [documentation](https://github.com/devture/email2matrix/blob/master/docs/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:9
+msgid "Preparation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:11
+msgid "DNS configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:13
+msgid "It's not strictly necessary, but you may increase the chances that incoming emails reach your server by adding an `MX` record for `matrix.example.com`, as described in the [Configuring DNS](configuring-dns.md) documentation page."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:15
+msgid "Port availability"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:17
+msgid "Ensure that port 25 is available on your Matrix server and open in your firewall."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:19
+msgid "If you have `postfix` or some other email server software installed, you may need to manually remove it first (unless you need it, of course)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:21
+msgid "If you really need to run an email server on the Matrix machine for other purposes, it may be possible to run Email2Matrix on another port (with a configuration like `matrix_email2matrix_smtp_host_bind_port: \"127.0.0.01:2525\"`) and have your other email server relay messages there."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:23
+msgid "For details about using Email2Matrix alongside [Postfix](http://www.postfix.org/), see [here](https://github.com/devture/email2matrix/blob/master/docs/setup_with_postfix.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:25
+msgid "Register a dedicated Matrix user (optional, recommended)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:27
+msgid "We recommend that you create a dedicated Matrix user for Email2Matrix."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:29
+msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:31
+msgid "You can use the playbook to [register a new user](registering-users.md):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:37
+msgid "Take note of the user's ID as it needs to be specified as `MatrixUserId` on your `inventory/host_vars/matrix.example.com/vars.yml` file later."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:39
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:41
+msgid "Email2Matrix requires an access token for the sender user to be able to send messages to the room. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:43
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:45
+msgid "Join to rooms as the sender user manually"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:47
+msgid "ℹ️ **Email2Matrix does not accept room invitations automatically**. To deliver messages to rooms, the sender user must be joined to all rooms manually."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:49
+msgid "For each new room you would like the user to deliver messages to, invite the user to the room."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:51
+msgid "Then, log in as the sender user using any Matrix client of your choosing, accept the room invitation from the user's account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:53
+msgid "Make sure that you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there, then log out."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:55
+msgid "Take note of each room's room ID (different clients show the room ID in a different place). You'll need the room ID when [configuring the playbook](#adjusting-the-playbook-configuration) below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:57
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:59
+msgid "To enable Email2Matrix, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_FOR_EMAIL2MATRIX1_HERE` and `ACCESS_TOKEN_FOR_EMAIL2MATRIX2_HERE` with the ones created [above](#obtain-an-access-token)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:85
+msgid "where:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:87
+msgid "MailboxName - local-part of the email address, through which emails are bridged to the room whose ID is defined with MatrixRoomId"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:88
+msgid "MatrixRoomId - internal ID of the room, to which received emails are sent as Matrix message"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:89
+msgid "MatrixHomeserverUrl - URL of your Matrix homeserver, through which to send Matrix messages. You can also set `MatrixHomeserverUrl` to the container URL where your homeserver's Client-Server API lives by using the `{{ matrix_addons_homeserver_client_api_url }}` variable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:90
+msgid "MatrixUserId - the full ID of the sender user which sends bridged messages to the room. On this configuration it is `@email2matrix1:example.com` and `@email2matrix2:example.com` (where `example.com` is your base domain, not the `matrix.` domain)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:91
+msgid "MatrixAccessToken - sender user's access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:92
+msgid "IgnoreSubject - if set to \"true\", the subject is not bridged to Matrix"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:93
+msgid "IgnoreBody - if set to \"true\", the message body is not bridged to Matrix"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:94
+msgid "SkipMarkdown - if set to \"true\", emails are bridged as plain text Matrix message instead of Markdown (actually HTML)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:96
+msgid "Refer to the official documentation [here](https://github.com/devture/email2matrix/blob/master/docs/configuration.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:98
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:100
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:107
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:109
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service email2matrix` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:111
+msgid "`just install-service email2matrix` is useful for maintaining your setup quickly 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 `just setup-all` runs the `ensure-matrix-users-created` tag too."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-email2matrix.md:113
+msgid "After installation, you may wish to send a test email to the email address assigned to `mailbox1` (default: `mailbox1@matrix.example.com`) to make sure that Email2Matrix works as expected."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-etherpad.pot b/i18n/translation-templates/docs/configuring-playbook-etherpad.pot
new file mode 100644
index 000000000..0856a2a9d
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-etherpad.pot
@@ -0,0 +1,169 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-etherpad.md:1
+msgid "Setting up Etherpad (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:3
+msgid "[Etherpad](https://etherpad.org) is an open source collaborative text editor that can be embedded in a Matrix chat room using the [Dimension integration manager](https://dimension.t2bot.io) or used as standalone web app."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:5
+msgid "When enabled together with the Jitsi audio/video conferencing system (see [our docs on Jitsi](configuring-playbook-jitsi.md)), it will be made available as an option during the conferences."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:9
+msgid "To enable Etherpad, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:19
+msgid "Adjusting the Etherpad URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:21
+msgid "By default, this playbook installs Etherpad on the `etherpad.` subdomain (`etherpad.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:23
+msgid "By tweaking the `etherpad_hostname` and `etherpad_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-etherpad.md:25
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:36
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:38
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Etherpad domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:40
+msgid "By default, you will need to create a CNAME record for `etherpad`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:42
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:44
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:46
+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-etherpad.md:53
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:55
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the Etherpad admin user (`etherpad_admin_username`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:57
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:59
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:61
+msgid "If you change the Etherpad admin user's password (`etherpad_admin_password` in your `vars.yml` file) subsequently, the admin user's credentials on the homeserver won't be updated automatically. If you'd like to change the admin user's password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `etherpad_admin_password` to let the admin user know its new password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:63
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:65
+msgid "The Etherpad UI should be available at `https://etherpad.example.com`, while the admin UI (if enabled) should then be available at `https://etherpad.example.com/admin`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:67
+msgid "If you've [decided on another hostname or path-prefix](#adjusting-the-etherpad-url) (e.g. `https://matrix.example.com/etherpad`), adjust these URLs accordingly before usage."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:69
+msgid "Managing / Deleting old pads"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:71
+msgid "If you want to manage and remove old unused pads from Etherpad, you will first need to able Admin access as described above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:73
+msgid "Then from the plugin manager page (`https://etherpad.example.com/admin/plugins`, install the `adminpads2` plugin. Once installed, you should have a \"Manage pads\" section in the Admin web-UI."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:75
+msgid "How to use Etherpad widgets without an integration manager (like Dimension)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:77
+msgid "This is how it works in Element Web, it might work quite similar with other clients:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:79
+msgid "To integrate a standalone Etherpad in a room, create your pad by visiting `https://etherpad.example.com`. When the pad opens, copy the URL and send a command like this to the room: `/addwidget URL`. You will then find your integrated Etherpad within the right sidebar in the `Widgets` section."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:81
+msgid "Set Dimension default to the self-hosted Etherpad (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:83
+msgid "If you decided to install [Dimension integration manager](configuring-playbook-dimension.md) alongside Etherpad, the Dimension administrator users can configure the default URL template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:85
+msgid "The Dimension configuration menu can be accessed with the sprocket icon as you begin to add a widget to a room in Element Web. There you will find the Etherpad Widget Configuration action beneath the _Widgets_ tab."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:87
+msgid "Removing the integrated Etherpad chat"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:89
+msgid "If you wish to disable the Etherpad chat button, you can do it by appending `?showChat=false` to the end of the pad URL, or the template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:91
+msgid "Example: `https://etherpad.example.com/p/$roomId_$padName?showChat=false`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:93
+msgid "Known issues"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:95
+msgid "If your Etherpad widget fails to load, this might be due to Dimension generating a Pad name so long, the Etherpad app rejects it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-etherpad.md:97
+msgid "`$roomId_$padName` can end up being longer than 50 characters. You can avoid having this problem by altering the template so it only contains the three word random identifier `$padName`."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-external-postgres.pot b/i18n/translation-templates/docs/configuring-playbook-external-postgres.pot
new file mode 100644
index 000000000..525f188ed
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-external-postgres.pot
@@ -0,0 +1,45 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-external-postgres.md:1
+msgid "Using an external PostgreSQL server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:3
+msgid "By default, this playbook would set up a PostgreSQL database server on your machine, running in a Docker container. If that's okay, you can skip this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:5
+msgid "**Note**: using **an external Postgres server is currently [not very seamless](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1682#issuecomment-1061461683) when it comes to enabling various other playbook services** - you will need to create a new database/credentials for each service and to point each service to its corresponding database using custom `vars.yml` configuration. **For the best experience with the playbook, stick to using the integrated Postgres server**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:7
+msgid "If you'd like to use an external Postgres server that you manage, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:23
+msgid "The database (as specified in `matrix_synapse_database_database`) must exist and be accessible with the given credentials. It must be empty or contain a valid Synapse database. If empty, Synapse would populate it the first time it runs."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:25
+msgid "**Note**: the external server that you specify in `matrix_synapse_database_host` must be accessible from within the `matrix-synapse` Docker container (and possibly other containers too). This means that it either needs to be a publicly accessible hostname or that it's a hostname on the same Docker network where all containers installed by this playbook run (a network called `matrix` by default). Using a local PostgreSQL instance on the host (running on the same machine, but not in a container) is not possible."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-external-postgres.md:27
+msgid "The connection to your external Postgres server **will not be SSL encrypted**, as [we don't support that yet](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/89)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-federation.pot b/i18n/translation-templates/docs/configuring-playbook-federation.pot
new file mode 100644
index 000000000..f3ceaf31a
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-federation.pot
@@ -0,0 +1,85 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-federation.md:1
+msgid "Controlling Matrix federation (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:3
+msgid "By default, your server federates with the whole Matrix network. That is, people on your server can communicate with people on any other Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:5
+msgid "**Note**: in the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com` and set up [server delegation](howto-server-delegation.md) / redirection. Without a proper configuration, your server will effectively not be part of the Matrix network. If you find your server is not federated, make sure to [check whether services work](maintenance-checking-services.md) and your server is properly delegated."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:7
+msgid "Federating only with select servers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:9
+msgid "To make your server only federate with servers of your choosing, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:17
+msgid "If you wish to disable federation, you can do that with an empty list (`[]`), or better yet by completely disabling federation (see below)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:19
+msgid "Exposing the room directory over federation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:21
+msgid "By default, your server's public rooms directory is not exposed to other servers via federation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:23
+msgid "If you wish to expose it, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:29
+msgid "Disabling federation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:31
+msgid "To completely disable federation, isolating your server from the rest of the Matrix network, add this to your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:37
+msgid "With that, your server's users will only be able to talk among themselves, but not to anyone who is on another server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:39
+msgid "**Disabling federation does not necessarily disable the federation port** (`8448`). Services like [Dimension](configuring-playbook-dimension.md) and [ma1sd](configuring-playbook-ma1sd.md) normally rely on `openid` APIs exposed on that port. Even if you disable federation and only if necessary, we may still be exposing the federation port and serving the `openid` APIs there. To override this and completely disable Synapse's federation port use:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:51
+msgid "Changing the federation port from 8448 to a different port to use a CDN that only accepts 443/80 ports"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:53
+msgid "Why? This change could be useful for people running small Synapse instances on small severs/VPSes to avoid being impacted by a simple DOS/DDOS when bandwidth, RAM, an CPU resources are limited and if your hosting provider does not provide a DOS/DDOS protection."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:55
+msgid "The following changes in the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) will allow this and make it possible to proxy the federation through a CDN such as CloudFlare or any other:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-federation.md:66
+msgid "**Use this at you own risk as all the possible side-effects of doing this are not fully known. However, it has been tested and works fine and passes all the tests on <https://federationtester.matrix.org/> without issues.**"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-jitsi.pot b/i18n/translation-templates/docs/configuring-playbook-jitsi.pot
new file mode 100644
index 000000000..a6f074789
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-jitsi.pot
@@ -0,0 +1,361 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-jitsi.md:1
+msgid "Setting up the Jitsi video-conferencing platform (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:3
+msgid "The playbook can install the [Jitsi](https://jitsi.org/) video-conferencing platform and integrate it with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:5
+msgid "Jitsi installation is **not enabled by default**, because it's not a core component of Matrix services."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:7
+msgid "The setup done by the playbook is very similar to [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet). You can refer to the documentation there for many of the options here."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:11
+msgid "You may need to open the following ports to your server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:13
+msgid "`4443/tcp` - RTP media fallback over TCP"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:14
+msgid "`10000/udp` - RTP media over UDP. Depending on your firewall/NAT setup, incoming RTP packets on port `10000` may have the external IP of your firewall as destination address, due to the usage of STUN in JVB (see [`jitsi_jvb_stun_servers`](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/defaults/main.yml))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:16
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:18
+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:24
+msgid "Adjusting the Jitsi URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:26
+msgid "By default, this playbook installs Jitsi on the `jitsi.` subdomain (`jitsi.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:28
+msgid "By tweaking the `jitsi_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:30
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:37
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:39
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Jitsi domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:41
+msgid "By default, you will need to create a CNAME record for `jitsi`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:43
+msgid "Configure Jitsi authentication and guests mode (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:45
+msgid "By default the Jitsi Meet instance does not require any kind of login and is open to use for anyone without registration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:47
+msgid "If you're fine with such an open Jitsi instance, please skip to [Installing](#installing)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:49
+msgid "If you would like to control who is allowed to open meetings on your new Jitsi instance, then please follow the following steps to enable Jitsi's authentication and optionally guests mode."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:51
+msgid "Currently, there are three supported authentication modes: 'internal' (default), 'matrix' and 'ldap'."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:53
+msgid "**Note**: Authentication is not tested via the playbook's self-checks. We therefore recommend that you manually verify if authentication is required by jitsi. For this, try to manually create a conference on jitsi.example.com in your browser."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:55
+msgid "Authenticate using Jitsi accounts (Auth-Type 'internal')"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:57
+msgid "The default authentication mechanism is 'internal' auth, which requires jitsi-accounts to be setup and is the recommended setup, as it also works in federated rooms. With authentication enabled, all meeting rooms have to be opened by a registered user, after which guests are free to join. If a registered host is not yet present, guests are put on hold in individual waiting rooms."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:59
+msgid "Add these lines to your `inventory/host_vars/matrix.example.com/vars.yml` configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:71
+msgid "**Caution**: Accounts added here and subsequently removed will not be automatically removed from the Prosody server until user account cleaning is integrated into the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:73
+msgid "**If you get an error** like this: \"Error: Account creation/modification not supported.\", it's likely that you had previously installed Jitsi without auth/guest support. In such a case, you should look into [Rebuilding your Jitsi installation](#rebuilding-your-jitsi-installation)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:75
+msgid "Authenticate using Matrix OpenID (Auth-Type 'matrix')"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:77
+msgid "**Attention: Probably breaks Jitsi in federated rooms and does not allow sharing conference links with guests.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:79
+msgid "Using this authentication type require a [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service). By default, this playbook creates and configures a user-verification-service to run locally, see [configuring-user-verification-service](configuring-playbook-user-verification-service.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:81
+msgid "To enable set this configuration at host level:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:89
+msgid "For more information see also [https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification](https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:91
+msgid "Authenticate using LDAP (Auth-Type 'ldap')"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:93
+msgid "An example LDAP configuration could be:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:113
+msgid "For more information refer to the [docker-jitsi-meet](https://github.com/jitsi/docker-jitsi-meet#authentication-using-ldap) and the [saslauthd `LDAP_SASLAUTHD`](https://github.com/winlibs/cyrus-sasl/blob/master/saslauthd/LDAP_SASLAUTHD) documentation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:115
+msgid "Making your Jitsi server work on a LAN (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:117
+msgid "By default the Jitsi Meet instance does not work with a client in LAN (Local Area Network), even if others are connected from WAN. There are no video and audio. In the case of WAN to WAN everything is ok."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:119
+msgid "The reason is the Jitsi VideoBridge git to LAN client the IP address of the docker image instead of the host. The [documentation](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/#running-behind-nat-or-on-a-lan-environment) of Jitsi in docker suggest to add `JVB_ADVERTISE_IPS` in enviornment variable to make it work."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:121
+msgid "Here is how to do it in the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:123
+msgid "Add these two lines to your `inventory/host_vars/matrix.example.com/vars.yml` configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:130
+msgid "Fine tune Jitsi (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:132
+msgid "Sample **additional** `inventory/host_vars/matrix.example.com/vars.yml` configuration to save up resources (explained below):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:147
+msgid "You may want to **suspend unused video layers** until they are requested again, to save up resources on both server and clients. Read more on this feature [here](https://jitsi.org/blog/new-off-stage-layer-suppression-feature/)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:149
+msgid "You may wish to **disable audio levels** to avoid excessive refresh of the client-side page and decrease the CPU consumption involved."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:151
+msgid "You may want to **limit the number of video feeds forwarded to each client**, to save up resources on both server and clients. As clients’ bandwidth and CPU may not bear the load, use this setting to avoid lag and crashes. This feature is found by default in other webconference applications such as Office 365 Teams (limit is set to 4). Read how it works [here](https://github.com/jitsi/jitsi-videobridge/blob/master/doc/last-n.md) and performance evaluation on this [study](https://jitsi.org/wp-content/uploads/2016/12/nossdav2015lastn.pdf)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:153
+msgid "You may want to **limit the maximum video resolution**, to save up resources on both server and clients."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:155
+msgid "Specify a Max number of participants on a Jitsi conference (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:157
+msgid "The playbook allows a user to set a max number of participants allowed to join a Jitsi conference. By default there is no limit."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:159
+msgid "In order to set the max number of participants use the following **additional** configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:165
+msgid "Additional JVBs (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:167
+msgid "By default, a single JVB ([Jitsi VideoBridge](https://github.com/jitsi/jitsi-videobridge)) is deployed on the same host as the Matrix server. To allow more video-conferences to happen at the same time, you may need to provision additional JVB services on other hosts."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:169
+msgid "There is an ansible playbook that can be run with the following tag: `ansible-playbook -i inventory/hosts --limit jitsi_jvb_servers jitsi_jvb.yml --tags=common,setup-additional-jitsi-jvb,start`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:171
+msgid "For this role to work you will need an additional section in the ansible hosts file with the details of the JVB hosts, for example:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:178
+msgid "Each JVB will require a server ID to be set so that it can be uniquely identified and this allows Jitsi to keep track of which conferences are on which JVB. The server ID is set with the variable `jitsi_jvb_server_id` which ends up as the JVB_WS_SERVER_ID environment variables in the JVB docker container. This variable can be set via the host file, a parameter to the ansible command or in the `vars.yaml` for the host which will have the additional JVB. For example:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:190
+msgid "Note that the server ID `jvb-1` is reserved for the JVB instance running on the Matrix host and therefore should not be used as the ID of an additional jvb host."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:192
+msgid "The additional JVB will also need to expose the colibri web socket port and this can be done with the following variable:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:198
+msgid "The JVB will also need to know where the prosody xmpp server is located, similar to the server ID this can be set in the vars for the JVB by using the variable `jitsi_xmpp_server`. The Jitsi prosody container is deployed on the Matrix server by default so the value can be set to the Matrix domain. For example:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:204
+msgid "However, it can also be set the ip address of the Matrix server. This can be useful if you wish to use a private ip. For example:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:210
+msgid "For the JVB to be able to contact the XMPP server, the latter must expose the XMPP port (5222). By default, the Matrix server does not expose the port; only the XMPP container exposes it internally inside the host, which means that the first JVB (which runs on the Matrix server) can reach it but the additional JVB cannot. The port is exposed by setting `jitsi_prosody_container_jvb_host_bind_port` like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:216
+msgid "(The default is empty; if it's set then docker forwards the port.)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:218
+msgid "Applied together this will allow you to provision extra JVB instances which will register themselves with the prosody service and be available for jicofo to route conferences too."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:220
+msgid "To make Traefik reverse-proxy to these additional JVBs (living on other hosts), **you would need to add the following Traefik configuration extension**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:256
+msgid "Enable Gravatar (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:258
+msgid "In the default Jisti Meet configuration, gravatar.com is enabled as an avatar service. This results in third party request leaking data to gravatar. Since Element clients already send the url of configured Matrix avatars to Jitsi, we disabled gravatar."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:260
+msgid "To enable Gravatar set:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:266
+msgid "**Beware**: This leaks information to a third party, namely the Gravatar-Service (unless configured otherwise: gravatar.com). Besides metadata, this includes the Matrix user_id and possibly the room identifier (via `referrer` header)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:268
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:270
+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:277
+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:279
+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:281
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:283
+msgid "You can use the self-hosted Jitsi server in multiple ways:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:285
+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:287
+msgid "**by adding a widget to a room via the Dimension integration manager**. You'll have to point the widget to your own Jitsi server manually. See our [Dimension integration manager](./configuring-playbook-dimension.md) documentation page for more details. Naturally, Dimension would need to be installed first (the playbook doesn't install it by default)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:289
+msgid "**directly (without any Matrix integration)**. Just go to `https://jitsi.example.com`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:291
+msgid "**Note**: Element apps on mobile devices currently [don't support joining meetings on a self-hosted Jitsi server](https://github.com/element-hq/riot-web/blob/601816862f7d84ac47547891bd53effa73d32957/docs/jitsi.md#mobile-app-support)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:293
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:295
+msgid "Rebuilding your Jitsi installation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:297
+msgid "**If you ever run into any trouble** or **if you change configuration (`jitsi_*` variables) too much**, we urge you to rebuild your Jitsi setup."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:299
+msgid "We normally don't require such manual intervention for other services, but Jitsi services generate a lot of configuration files on their own."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:301
+msgid "These files are not all managed by Ansible (at least not yet), so you may sometimes need to delete them all and start fresh."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:303
+msgid "To rebuild your Jitsi configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:305
+msgid "ask Ansible to stop all Jitsi services: `just run-tags stop-group --extra-vars=group=jitsi`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:306
+msgid "SSH into the server and do this and remove all Jitsi configuration & data (`rm -rf /matrix/jitsi`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-jitsi.md:307
+msgid "ask Ansible to set up Jitsi anew and restart services (`just install-service jitsi`)"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-ldap-auth.pot b/i18n/translation-templates/docs/configuring-playbook-ldap-auth.pot
new file mode 100644
index 000000000..45732b593
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-ldap-auth.pot
@@ -0,0 +1,57 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 09:53+0200\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-ldap-auth.md:1
+msgid "Setting up the LDAP authentication password provider module (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:3
+msgid "The playbook can install and configure the [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) LDAP Auth password provider for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:5
+msgid "See the project's [documentation](https://github.com/matrix-org/matrix-synapse-ldap3/blob/main/README.rst) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:7
+msgid "If you decide that you'd like to let this playbook install it for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:24
+msgid "Authenticating only using a password provider"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:26
+msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:32
+msgid "Using ma1sd Identity Server for authentication"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:34
+msgid "If you wish to use the ma1sd Identity Server for LDAP authentication instead of [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) consult [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md#authentication)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:36
+msgid "Handling user registration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ldap-auth.md:38
+msgid "If you wish for users to also be able to make new registrations against LDAP, you may **also** wish to [set up the ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-ma1sd.pot b/i18n/translation-templates/docs/configuring-playbook-ma1sd.pot
new file mode 100644
index 000000000..0e2a2fc11
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-ma1sd.pot
@@ -0,0 +1,209 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 09:53+0200\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-ma1sd.md:1
+msgid "Setting up ma1sd Identity Server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:3
+msgid "**⚠️Note**: ma1sd itself has also been unmaintained for years (the latest commit and release being from 2021). The role of identity servers in the Matrix specification also has an uncertain future. **We recommend not bothering with installing it unless it's the only way you can do what you need to do**. For example, certain things like LDAP integration can also be implemented via [the LDAP provider module for Synapse](./configuring-playbook-ldap-auth.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:5
+msgid "The playbook can configure the [ma1sd](https://github.com/ma1uta/ma1sd) Identity Server for you. It is a fork of [mxisd](https://github.com/kamax-io/mxisd) which was pronounced end of life 2019-06-21."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:7
+msgid "ma1sd is used for 3PIDs (3rd party identifiers like E-mail and phone numbers) and some [enhanced features](https://github.com/ma1uta/ma1sd/#features). It is private by default, potentially at the expense of user discoverability."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:9
+msgid "See the project's [documentation](https://github.com/ma1uta/ma1sd/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:11
+msgid "**Note**: enabling ma1sd, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. It's something to be aware of, especially in terms of firewall whitelisting (make sure port `8448` is accessible)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:13
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:15
+msgid "To make the ma1sd Identity Server enable its federation features, set up a SRV record that looks like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:17
+msgid "Name: `_matrix-identity._tcp` (use this text as-is)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:18
+msgid "Content: `10 0 443 matrix.example.com` (replace `example.com` with your own)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:20
+msgid "See [ma1sd's documentation](https://github.com/ma1uta/ma1sd/wiki/mxisd-and-your-privacy#choices-are-never-easy) for information on the privacy implications of setting up this SRV record."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:22
+msgid "**Note**: This `_matrix-identity._tcp` SRV record for the identity server is different from the `_matrix._tcp` that can be used for Synapse delegation. See [howto-server-delegation.md](howto-server-delegation.md) for more information about delegation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:24
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:26
+msgid "To enable ma1sd, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:32
+msgid "Matrix.org lookup forwarding"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:34
+msgid "To ensure maximum discovery, you can make your identity server also forward lookups to the central matrix.org Identity server (at the cost of potentially leaking all your contacts information)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:36
+msgid "Enabling this is discouraged and you'd better [learn more](https://github.com/ma1uta/ma1sd/blob/master/docs/features/identity.md#lookups) before proceeding."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:38
+msgid "To enable matrix.org forwarding, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:44
+msgid "Additional features"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:46
+msgid "What this playbook configures for your is some bare minimum Identity Server functionality, so that you won't need to rely on external 3rd party services."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:48
+msgid "A few variables can be toggled in this playbook to alter the ma1sd configuration that gets generated."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:50
+msgid "Still, ma1sd can do much more. You can refer to the [ma1sd website](https://github.com/ma1uta/ma1sd) for more details and configuration options."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:52
+msgid "To use a more custom configuration, you can define a `matrix_ma1sd_configuration_extension_yaml` string variable and put your configuration in it. To learn more about how to do this, refer to the information about `matrix_ma1sd_configuration_extension_yaml` in the [default variables file](../roles/custom/matrix-ma1sd/defaults/main.yml) of the ma1sd component."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:54
+msgid "Customizing email templates"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:56
+msgid "If you'd like to change the default email templates used by ma1sd, take a look at the `matrix_ma1sd_threepid_medium_email_custom_` variables (in the `roles/custom/matrix-ma1sd/defaults/main.yml` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:58
+msgid "ma1sd-controlled Registration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:60
+msgid "To use the [Registration](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) feature of ma1sd, you can make use of the following variables:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:62
+msgid "`matrix_synapse_enable_registration` - to enable user-initiated registration in Synapse"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:64
+msgid "`matrix_synapse_enable_registration_captcha` - to validate registering users using reCAPTCHA, as described in the [enabling reCAPTCHA](configuring-captcha.md) documentation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:66
+msgid "`matrix_synapse_registrations_require_3pid` - a list of 3pid types (among `'email'`, `'msisdn'`) required by the Synapse server for registering"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:68
+msgid "variables prefixed with `matrix_ma1sd_container_labels_` (e.g. `matrix_ma1sd_container_labels_matrix_client_3pid_registration_enabled`) - to configure the Traefik reverse-proxy to capture and send registration requests to ma1sd (instead of Synapse), so it can apply its additional functionality"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:70
+msgid "`matrix_ma1sd_configuration_extension_yaml` - to configure ma1sd as required. See the [Registration feature's docs](https://github.com/ma1uta/ma1sd/blob/master/docs/features/registration.md) for inspiration. Also see the [Additional features](#additional-features) section below to learn more about how to use `matrix_ma1sd_configuration_extension_yaml`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:72
+msgid "**Note**: For this to work, either the homeserver needs to [federate](configuring-playbook-federation.md) or the `openid` APIs need to exposed on the federation port. When federation is disabled and ma1sd is enabled, we automatically expose the `openid` APIs (only!) on the federation port. Make sure the federation port (usually `https://matrix.example.com:8448`) is whitelisted in your firewall (even if you don't actually use/need federation)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:74
+msgid "Authentication"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:76
+msgid "[Authentication](https://github.com/ma1uta/ma1sd/blob/master/docs/features/authentication.md) provides the possibility to use your own [Identity Stores](https://github.com/ma1uta/ma1sd/blob/master/docs/stores/README.md) (for example LDAP) to authenticate users on your Homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:78
+msgid "To enable authentication against an LDAP server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:98
+msgid "Example: SMS verification"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:100
+msgid "If your use case requires mobile verification, it is quite simple to integrate ma1sd with [Twilio](https://www.twilio.com/), an online telephony services gateway. Their prices are reasonable for low-volume projects and integration can be done with the following configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:114
+msgid "Example: Open Registration for every Domain"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:116
+msgid "If you want to open registration for any domain, you have to setup the allowed domains with ma1sd's `blacklist` and `whitelist`. The default behavior when neither the `blacklist`, nor the `whitelist` match, is to allow registration. Beware: you can't block toplevel domains (aka `.xy`) because the internal architecture of ma1sd doesn't allow that."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:130
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:132
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:139
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:141
+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-ma1sd.md:143
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:145
+msgid "If email address validation emails sent by ma1sd are not reaching you, you should look into [Adjusting email-sending settings](configuring-playbook-email.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:147
+msgid "If you'd like additional logging information, temporarily enable verbose logging for ma1sd."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ma1sd.md:149
+msgid "To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-matrix-authentication-service.pot b/i18n/translation-templates/docs/configuring-playbook-matrix-authentication-service.pot
new file mode 100644
index 000000000..85a638778
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-matrix-authentication-service.pot
@@ -0,0 +1,618 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-matrix-authentication-service.md:1
+msgid "Setting up Matrix Authentication Service (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:3
+msgid "This playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) - a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:5
+msgid "Matrix Authentication Service is an implementation of [MSC3861: Next-generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:7
+msgid "**Before going through with starting to use Matrix Authentication Service**, make sure to read:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:9
+msgid "the [Reasons to use Matrix Authentication Service](#reasons-to-use-matrix-authentication-service) section below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:10
+msgid "the [Expectations](#expectations) section below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:11
+msgid "the [FAQ section on areweoidcyet.com](https://areweoidcyet.com/#faqs)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:13
+msgid "**If you've already been using Synapse** and have user accounts in its database, you can [migrate to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:15
+msgid "Reasons to use Matrix Authentication Service"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:17
+msgid "You may be wondering whether you should make the switch to Matrix Authentication Service (MAS) or keep using your existing authentication flow via Synapse (password-based or [OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)-enabled)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:19
+msgid "Matrix Authentication Service is **still an experimental service** and **not a default** for this Ansible playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:21
+msgid "The [Expectations](#expectations) section contains a list of what works and what doesn't (**some services don't work with MAS yet**), as well as the **relative irreversability** of the migration process."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:23
+msgid "Below, we'll try to **highlight some potential reasons for switching** to Matrix Authentication Service:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:25
+msgid "To use SSO in [Element X](https://element.io/blog/element-x-ignition/). The old [Synapse OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) login flow is only supported in old Element clients and will not be supported in Element X. Element X will only support the new SSO-based login flow provided by MAS, so if you want to use SSO with Element X, you will need to switch to MAS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:27
+msgid "To help drive adoption of the \"Next-generation auth for Matrix\" by switching to what's ultimately coming anyway"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:29
+msgid "To help discover (and potentially fix) MAS integration issues with this Ansible playbook"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:31
+msgid "To help discover (and potentially fix) MAS integration issues with various other Matrix components (bridges, bots, clients, etc.)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:33
+msgid "To reap some of the security benefits that Matrix Authentication Service offers, as outlined in the [Better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/) article."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:35
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:37
+msgid "⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:39
+msgid "⚠️ **email sending** configured (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:41
+msgid "❌ **disabling all password providers** for Synapse (things like [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc.) More details about this are available in the [Expectations](#expectations) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:43
+msgid "Expectations"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:45
+msgid "This section details what you can expect when switching to the Matrix Authentication Service (MAS)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:47
+msgid "❌ **Synapse password providers will need to be disabled**. You can no longer use [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc. When the authentication flow is handled by MAS (not by Synapse anymore), it doesn't make sense to extend the Synapse authentication flow with additional modules. Many bridges used to rely on shared-secret-auth for doing double-puppeting (impersonating other users), but most (at least the mautrix bridges) nowadays use [Appservice Double Puppet](./configuring-playbook-appservice-double-puppet.md) as a better alternative. Older/maintained bridges may still rely on shared-secret-auth, as do other services like [matrix-corporal](./configuring-playbook-matrix-corporal.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:49
+msgid "❌ Certain **tools like [synapse-admin](./configuring-playbook-synapse-admin.md) do not have full compatibility with MAS yet**. synapse-admin already supports [login with access token](https://github.com/etkecc/synapse-admin/pull/58), browsing users (which Synapse will internally fetch from MAS) and updating user avatars. However, editing users (passwords, etc.) now needs to happen directly against MAS using the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html), which synapse-admin cannot interact with yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:51
+msgid "❌ **Some services experience issues when authenticating via MAS**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:53
+msgid "[Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first time around, but it consistently fails after restarting:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:55
+msgid "cannot initialize matrix bot error=\"olm account is marked as shared, keys seem to have disappeared from the server\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:57
+msgid "[matrix-reminder-bot](./configuring-playbook-bot-matrix-reminder-bot.md) fails to start (see [element-hq/matrix-authentication-service#3439](https://github.com/element-hq/matrix-authentication-service/issues/3439))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:58
+msgid "Other services may be similarly affected. This list is not exhaustive."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:60
+msgid "❌ **Encrypted appservices** do not work yet (related to [MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) and [PR 17705 for Synapse](https://github.com/element-hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will fail to start (see [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3658) for Hookshot). You can use these bridges/bots only if you **keep end-to-bridge encryption disabled** (which is the default setting)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:62
+msgid "⚠️ **You will need to have email sending configured** (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:64
+msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:66
+msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) does not currently seem to preserve the \"admin\" flag for users (as found in the Synapse database). All users are imported as non-admin - see [element-hq/matrix-authentication-service#3440](https://github.com/element-hq/matrix-authentication-service/issues/3440). You may need update the Matrix Authentication Service's database manually and adjust the `can_request_admin` column in the `users` table to `true` for users that need to be administrators (e.g. `UPDATE users SET can_request_admin = true WHERE username = 'someone';`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:68
+msgid "⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependant on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:70
+msgid "⚠️ If you've got [OIDC configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to migrate your OIDC configuration to MAS by adding an [Upstream OAuth2 configuration](#upstream-oauth2-configuration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:72
+msgid "⚠️ A [compatibility layer](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) is installed - all `/_matrix/client/*/login` (etc.) requests will be routed to MAS instead of going to the homeserver. This is done both publicly (e.g. `https://matrix.example.com/_matrix/client/*/login`) and on the internal Traefik entrypoint (e.g. `https://matrix-traefik:8008/_matrix/client/*/login`) which helps addon services reach the homeserver's Client-Server API. You typically don't need to do anything to make this work, but it's good to be aware of it, especially if you have a [custom webserver setup](./configuring-playbook-own-webserver.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:74
+msgid "✅ Your **existing login sessions will continue to work** (you won't get logged out). Migration will require a bit of manual work and minutes of downtime, but it's not too bad."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:76
+msgid "✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), [Element Web](./configuring-playbook-client-element-web.md), Element X, FluffyChat) will be able to use the **new SSO-based login flow** provided by Matrix Authentication Service"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:78
+msgid "✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work. Going through the old login flow does not require users to have a verified email address, as [is the case](https://github.com/element-hq/matrix-authentication-service/issues/1505) for the new SSO-based login flow."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:80
+msgid "✅ [Registering users](./registering-users.md) via **the playbook's `register-user` tag remains unchanged**. The playbook automatically does the right thing regardless of homeserver implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, the playbook will forward user-registration requests to MAS. Registering users via the command-line is no longer done via the `/matrix/synapse/bin/register` script, but via `/matrix/matrix-authentication-service/bin/register-user`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:82
+msgid "✅ Users that are prepared by the playbook (for bots, bridges, etc.) will continue to be registered automatically as expected. The playbook automatically does the right thing regardless of homeserver implementation (Synapse, Dendrite, etc.) and whether MAS is enabled or not. When MAS is enabled, the playbook will forward user-registration requests to MAS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:84
+msgid "Installation flows"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:86
+msgid "New homeserver"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:88
+msgid "For new homeservers (which don't have any users in their Synapse database yet), follow the [Adjusting the playbook configuration](#adjusting-the-playbook-configuration) instructions and then proceed with [Installing](#installing)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:90
+msgid "Existing homeserver"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:92
+msgid "Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:94
+msgid "For existing Synapse homeservers:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:96
+msgid "when following the [Adjusting the playbook configuration](#adjusting-the-playbook-configuration) instructions, make sure to **disable the integration between Synapse and MAS** by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line as described in the [Marking an existing homeserver for migration](#marking-an-existing-homeserver-for-migration) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:98
+msgid "then follow the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) instructions to perform the installation and migration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:100
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:102
+msgid "To enable Matrix Authentication Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:116
+msgid "In the sub-sections that follow, we'll cover some additional configuration options that you may wish to adjust."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:118
+msgid "There are many other configuration options available. Consult the [`defaults/main.yml` file](../roles/custom/matrix-authentication-service/defaults/main.yml) in the [matrix-authentication-service role](../roles/custom/matrix-authentication-service/) to discover them."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:120
+msgid "Adjusting the Matrix Authentication Service URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:122
+msgid "By default, this playbook installs the Matrix Authentication Service on the `matrix.` subdomain, at the `/auth` path (https://matrix.example.com/auth). 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-matrix-authentication-service.md:124
+msgid "By tweaking the `matrix_authentication_service_hostname` and `matrix_authentication_service_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-matrix-authentication-service.md:126
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:149
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:134
+msgid "Marking an existing homeserver for migration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:136
+msgid "The [configuration above](#adjusting-the-playbook-configuration) instructs existing users wishing to migrate to add `matrix_authentication_service_migration_in_progress: true` to their configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:138
+msgid "This is done temporarily. The migration steps are described in more detail in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:140
+msgid "Upstream OAuth2 configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:142
+msgid "To make Matrix Authentication Service delegate to an existing upstream OAuth 2.0/OIDC provider, you can use its [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:144
+msgid "The playbook exposes a `matrix_authentication_service_config_upstream_oauth2_providers` variable for controlling this setting."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:261
+msgid "💡 Refer to the [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers) for the most up-to-date schema and example for providers. The value shown above here may be out of date."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:263
+msgid "⚠️ The syntax for existing [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) is slightly different, so you will need to adjust your configuration when switching from Synapse OIDC to MAS upstream OAuth2."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:265
+msgid "⚠️ When [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) which contains OIDC-sourced users, you will need to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:267
+msgid "[Configure upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:268
+msgid "go through the [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) process"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:269
+msgid "remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:271
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:273
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Matrix Authentication Service domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:275
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:277
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:279
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:281
+msgid "Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:288
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:290
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:292
+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-matrix-authentication-service.md:294
+msgid "If you're in the process of migrating an existing Synapse homeserver to MAS, you should now follow the rest of the steps in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) guide."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:296
+msgid "💡 After installation, you should [verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:298
+msgid "Migrating an existing Synapse homeserver to Matrix Authentication Service"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:300
+msgid "Our migration guide is loosely based on the upstream [Migrating an existing homeserver](https://element-hq.github.io/matrix-authentication-service/setup/migration.html) guide."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:302
+msgid "Migration is done via a tool called `syn2mas`, which the playbook could run for you (in a container)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:304
+msgid "The installation + migration steps are like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:306
+msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) to **disable the integration between the homeserver and MAS**. This is done by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:308
+msgid "Perform the initial [installation](#installing). At this point:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:310
+msgid "Matrix Authentication Service will be installed. Its database will be empty, so it cannot validate existing access tokens or authentication users yet."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:312
+msgid "The homeserver will still continue to use its local database for validating existing access tokens."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:314
+msgid "Various [compatibility layer URLs](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) are not yet installed. New login sessions will still be forwarded to the homeserver, which is capable of completing them."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:316
+msgid "The `matrix-user-creator` role would be suppressed, so that it doesn't automatically attempt to create users (for bots, etc.) in the MAS database. These user accounts likely already exist in Synapse's user database and could be migrated over (via syn2mas, as per the steps below), so creating them in the MAS database would have been unnecessary and potentially problematic (conflicts during the syn2mas migration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:318
+msgid "Consider taking a full [backup of your Postgres database](./maintenance-postgres.md#backing-up-postgresql). This is done just in case. The **syn2mas migration tool does not delete any data**, so it should be possible to revert to your previous setup by merely disabling MAS and re-running the playbook (no need to restore a Postgres backup). However, do note that as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:320
+msgid "[Migrate your data from Synapse to Matrix Authentication Service using syn2mas](#migrate-your-data-from-synapse-to-matrix-authentication-service-using-syn2mas)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:322
+msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) again, to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:324
+msgid "remove the `matrix_authentication_service_migration_in_progress: false` line"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:326
+msgid "if you had been using [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:328
+msgid "Perform the [installation](#installing) again. At this point:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:330
+msgid "The homeserver will start delegating authentication to MAS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:332
+msgid "The compatibility layer URLs will be installed. New login sessions will be completed by MAS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:334
+msgid "[Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:336
+msgid "Migrate your data from Synapse to Matrix Authentication Service using syn2mas"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:338
+msgid "We **don't** ask you to [run the `syn2mas` migration advisor command](https://element-hq.github.io/matrix-authentication-service/setup/migration.html#run-the-migration-advisor), because it only gives you the green light if your Synapse configuration (`homeserver.yaml`) is configured in a way that's compatible with MAS (delegating authentication to MAS; disabling Synapse's password config; etc.). Until we migrate your data with the `syn2mas` tool, we intentionally avoid doing these changes to allow existing user sessions to work."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:340
+msgid "You can invoke the `syn2mas` tool via the playbook by running the playbook's `matrix-authentication-service-syn2mas` tag. We recommend first doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:342
+msgid "Configuring syn2mas"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:344
+msgid "If you're using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to [Configuring upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:346
+msgid "If you only have local (non-OIDC) users in your Synapse database, you can likely run `syn2mas` as-is (without doing additional configuration changes)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:348
+msgid "When you're done with potentially configuring `syn2mas`, proceed to doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:350
+msgid "Configuring upstream OIDC provider mapping for syn2mas"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:352
+msgid "If you have existing OIDC users in your Synapse user database (which will be the case if when using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)), you may need to pass an additional `--upstreamProviderMapping` argument to the `syn2mas` tool to tell it which provider (on the Synapse side) maps to which other provider on the MAS side."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:354
+msgid "If you don't do this, `syn2mas` would report errors like this one:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:356
+msgid "[FATAL] migrate - [Failed to import external id 4264b0f0-4f11-4ddd-aedb-b500e4d07c25 with oidc-keycloak for user @alice:example.com: Error: Unknown upstream provider oidc-keycloak]"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:358
+msgid "Below is an example situation and a guide for how to solve it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:360
+msgid "If in `matrix_synapse_oidc_providers` your provider `idp_id` is (was) named `keycloak`, in the Synapse database users would be associated with the `oidc-keycloak` provider (note the `oidc-` prefix that was added automatically by Synapse to your `idp_id` value)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:362
+msgid "The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` on the MAS side, as defined in `matrix_authentication_service_config_upstream_oauth2_providers` (see the [Upstream OAuth2 configuration](#upstream-oauth2-configuration) section above)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:364
+msgid "To tell `syn2mas` how the Synapse-configured OIDC provider maps to the new MAS-configured OIDC provider, add this additional configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:373
+msgid "Performing a syn2mas dry-run"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:375
+msgid "Having [configured syn2mas](#configuring-syn2mas), we recommend doing a [dry-run](https://en.wikipedia.org/wiki/Dry_run_(testing)) first to verify that everything will work out as expected."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:377
+msgid "A dry-run would not cause downtime, because it avoids stopping Synapse."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:379
+msgid "To perform a dry-run, run:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:385
+msgid "Observe the command output (especially the last line of the the syn2mas output). If you are confident that the migration will work out as expected, you can proceed with a [real migration](#performing-a-real-syn2mas-migration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:387
+msgid "Performing a real syn2mas migration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:389
+msgid "Before performing a real migration make sure:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:391
+msgid "you've familiarized yourself with the [expectations](#expectations)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:393
+msgid "you've performed a Postgres backup, just in case"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:395
+msgid "you're aware of the irreversibility of the migration process without disruption after users have created new login sessions via the new MAS setup"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:397
+msgid "you've [configured syn2mas](#configuring-syn2mas), especially if you've used [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:399
+msgid "you've performed a [syn2mas dry-run](#performing-a-syn2mas-dry-run) and don't see any issues in its output"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:401
+msgid "To perform a real migration, run the `matrix-authentication-service-syn2mas` tag **without** the `matrix_authentication_service_syn2mas_dry_run` variable:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:407
+msgid "Having performed a `syn2mas` migration once, trying to do it again will report errors for users that were already migrated (e.g. \"Error: Unknown upstream provider oauth-delegated\")."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:409
+msgid "Verify that Matrix Authentication Service is installed correctly"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:411
+msgid "After [installation](#installing), run the `doctor` subcommand of the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) to verify that MAS is installed correctly."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:413
+msgid "You can do it:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:415
+msgid "either via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag: `just run-tags matrix-authentication-service-mas-cli-doctor`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:417
+msgid "or by running the `mas-cli` script on the server (which invokes the `mas-cli` tool inside a container): `/matrix/matrix-authentication-service/bin/mas-cli doctor`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:419
+msgid "If successful, you should see some output that looks like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:431
+msgid "Management"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:433
+msgid "You can use the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) (exposed via the `/matrix/matrix-authentication-service/bin/mas-cli` script) to perform administrative tasks against MAS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:435
+msgid "This documentation page already mentions:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:437
+msgid "the `mas-cli doctor` sub-command in the [Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly) section, which you can run via the CLI and via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:439
+msgid "the `mas-cli manage register-user` sub-command in the [Registering users](./registering-users.md) documentation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:441
+msgid "There are other sub-commands available. Run `/matrix/matrix-authentication-service/bin/mas-cli` to get an overview."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:443
+msgid "User registration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:445
+msgid "After Matrix Authentication Service is [installed](#installing), users need to be managed there (unless you're managing them in an [upstream OAuth2 provider](#upstream-oauth2-configuration))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:447
+msgid "You can register users new users as described in the [Registering users](./registering-users.md) documentation (via `mas-cli manage register-user` or the Ansible playbook's `register-user` tag)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:449
+msgid "Working around email deliverability issues"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:451
+msgid "Because Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user, you may need to work around email deliverability issues if [your email-sending configuration](./configuring-playbook-email.md) is not working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:453
+msgid "Matrix Authentication Service attempts to verify email addresses by sending a verification email to the address specified by the user whenever they log in to an account without a verified email address."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:455
+msgid "If email delivery is not working, **you can retrieve the email configuration code from the Matrix Authentication Service's logs** (`journalctl -fu matrix-authentication-service`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:457
+msgid "Alternatively, you can use the [`mas-cli` management tool](#management) to manually verify email addresses for users. Example: `/matrix/matrix-authentication-service/bin/mas-cli manage verify-email some.username email@example.com`"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-matrix-corporal.pot b/i18n/translation-templates/docs/configuring-playbook-matrix-corporal.pot
new file mode 100644
index 000000000..f4ea1d1c0
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-matrix-corporal.pot
@@ -0,0 +1,125 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 09:53+0200\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-matrix-corporal.md:1
+msgid "Setting up Matrix Corporal (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:5
+msgid "**WARNING**: This is an advanced feature! It requires prior experience with Matrix and a specific need for using [Matrix Corporal](https://github.com/devture/matrix-corporal). If you're unsure whether you have such a need, you most likely don't."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:9
+msgid "The playbook can install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:11
+msgid "In short, it's a sort of automation and firewalling service, which is helpful if you're instaling Matrix services in a controlled corporate environment."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:13
+msgid "See the project's [documentation](https://github.com/devture/matrix-corporal/blob/main/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:15
+msgid "If you decide that you'd like to let this playbook install it for you, you'd need to also:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:16
+msgid "(required) [set up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:17
+msgid "(optional, but encouraged) [set up the REST authentication password provider module](configuring-playbook-rest-auth.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:19
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:21
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:74
+msgid "Matrix Corporal operates with a specific Matrix user on your server. By default, it's `matrix-corporal` (controllable by the `matrix_corporal_reconciliation_user_id_local_part` setting, see above)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:76
+msgid "No matter what Matrix user ID you configure to run it with, make sure that:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:78
+msgid "the Matrix Corporal user is created by [registering it](registering-users.md) **with administrator privileges**. Use a password you remember, as you'll need to log in from time to time to create or join rooms"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:80
+msgid "the Matrix Corporal user is joined and has Admin/Moderator-level access to any rooms you want it to manage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:82
+msgid "Using a locally-stored static policy"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:84
+msgid "If you'd like to use a [static policy file](https://github.com/devture/matrix-corporal/blob/master/docs/policy-providers.md#static-file-pull-style-policy-provider), you can use a configuration like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:116
+msgid "To learn more about what the policy configuration, see the matrix-corporal documentation on [policy](https://github.com/devture/matrix-corporal/blob/master/docs/policy.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:118
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:120
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:127
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just run-tags setup-aux-files,setup-corporal,start` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:129
+msgid "`just run-tags setup-aux-files,setup-corporal,start` is useful for maintaining your setup quickly 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 `just setup-all` runs the `ensure-matrix-users-created` tag too."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:131
+msgid "Matrix Corporal files"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:133
+msgid "The following local filesystem paths are mounted in the `matrix-corporal` container and can be used in your configuration (or policy):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:135
+msgid "`/matrix/corporal/config` is mounted at `/etc/matrix-corporal` (read-only)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:137
+msgid "`/matrix/corporal/var` is mounted at `/var/matrix-corporal` (read and write)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:139
+msgid "`/matrix/corporal/cache` is mounted at `/var/cache/matrix-corporal` (read and write)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-corporal.md:141
+msgid "As an example: you can create your own configuration files in `/matrix/corporal/config` and they will appear in `/etc/matrix-corporal` in the Docker container. Your configuration (stuff in `matrix_corporal_policy_provider_config`) needs to refer to these files via the local container paths - `/etc/matrix-corporal` (read-only), `/var/matrix-corporal` (read and write), `/var/cache/matrix-corporal` (read and write)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-matrix-ldap-registration-proxy.pot b/i18n/translation-templates/docs/configuring-playbook-matrix-ldap-registration-proxy.pot
new file mode 100644
index 000000000..848607daa
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-matrix-ldap-registration-proxy.pot
@@ -0,0 +1,61 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-matrix-ldap-registration-proxy.md:1
+msgid "Setting up matrix-ldap-registration-proxy (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:3
+msgid "The playbook can install and configure [matrix-ldap-registration-proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:5
+msgid "This proxy handles Matrix registration requests and forwards them to LDAP."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:7
+msgid "**Note**: This does support the full Matrix specification for registrations. It only provide a very coarse implementation of a basic password registration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:9
+msgid "Quickstart"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:11
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:22
+msgid "If you already use the [synapse external password provider via LDAP](configuring-playbook-ldap-auth.md) (that is, you have `matrix_synapse_ext_password_provider_ldap_enabled: true` and other options in your configuration) you can use the following values as configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:35
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:37
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:44
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-ldap-registration-proxy.md:46
+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 ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-matrix-media-repo.pot b/i18n/translation-templates/docs/configuring-playbook-matrix-media-repo.pot
new file mode 100644
index 000000000..40aeb8401
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-matrix-media-repo.pot
@@ -0,0 +1,164 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-matrix-media-repo.md:1
+msgid "Storing Matrix media files using matrix-media-repo (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:3
+msgid "[matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/) (often abbreviated \"MMR\") is a highly customizable multi-domain media repository for Matrix. Intended for medium to large environments consisting of several homeservers, this media repo de-duplicates media (including remote media) while being fully compliant with the specification."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:5
+msgid "Smaller/individual homeservers can still make use of this project's features, though it may be difficult to set up or have higher than expected resource consumption. Please do your research before deploying this as this project may not be useful for your environment."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:7
+msgid "For a simpler alternative (which allows you to offload your media repository storage to S3, etc.), you can [configure S3 storage](configuring-playbook-s3.md) instead of setting up matrix-media-repo."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:0
+msgid "**Table of Contents**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:0
+msgid "[Quickstart](#quickstart)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:0
+msgid "[Additional configuration options](#configuring-the-media-repo)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:0
+msgid "[Importing data from an existing media store](#importing-data-from-an-existing-media-store)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:15
+msgid "Quickstart"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:17
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file and [re-run the installation process](./installing.md) for the playbook:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:26
+msgid "The repo is pre-configured for integrating with the Postgres database, Traefik proxy and [Prometheus/Grafana](configuring-playbook-prometheus-grafana.md) (if metrics enabled) from this playbook for all the available homeserver roles. When the media repo is enabled, other media store roles should be disabled (if using Synapse with other media store roles)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:28
+msgid "By default, the media-repo will use the local filesystem for data storage. You can alternatively use a `s3` cloud backend as well. Access token caching is also enabled by default since the logout endpoints are proxied through the media repo."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:30
+msgid "Configuring the media-repo"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:32
+msgid "Additional common configuration options:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:91
+msgid "Full list of configuration options with documentation can be found in [`roles/custom/matrix-media-repo/defaults/main.yml`](../roles/custom/matrix-media-repo/defaults/main.yml)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:93
+msgid "Signing Keys"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:95
+msgid "Authenticated media endpoints ([MSC3916](https://github.com/matrix-org/matrix-spec-proposals/pull/3916)) requires MMR to have a configured signing key to authorize outbound federation requests. Additionally, the signing key must be merged with your homeserver's signing key file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:97
+msgid "The playbook default is to generate a MMR signing key when invoking the setup role and merge it with your homeserver if you are using Synapse or Dendrite. This can be disabled if desired by setting the option in your inventory:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:103
+msgid "If you wish to manually generate the signing key and merge it with your homeserver's signing key file, see https://docs.t2bot.io/matrix-media-repo/v1.3.5/installation/signing-key/ for more details."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:105
+msgid "**Note that if you uninstall MMR from the playbook, it will not remove the old MMR signing key from your homeserver's signing key file. You will have to remove it manually.**"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:107
+msgid "Key backup and revoking"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:109
+msgid "Since your homeserver signing key file is modified by the playbook, a backup will be created in `HOMESERVER_DIR/config/example.com.signing.key.backup`. If you need to remove/revoke old keys, you can restore from this backup or remove the MMR key ID from your `example.com.signing.key` file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:111
+msgid "Additionally, its recommended after revoking a signing key to update your homeserver config file (`old_signing_keys` field for Synapse and `old_private_keys` for Dendrite). See your homeserver config file for further documentation on how to populate the field."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:113
+msgid "Importing data from an existing media store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:115
+msgid "If you want to add this repo to an existing homeserver managed by the playbook, you will need to import existing media into MMR's database or you will lose access to older media while it is active. MMR versions up to `v1.3.3` only support importing from Synapse, but newer versions (at time of writing: only `latest`) also support importing from Dendrite."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:117
+msgid "**Before importing**: ensure you have an initial matrix-media-repo deployment by following the [quickstart](#quickstart) guide above"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:119
+msgid "Depending on the homeserver implementation yu're using (Synapse, Dendrite), you'll need to use a different import tool (part of matrix-media-repo) and point it to the homeserver's database."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:121
+msgid "Importing data from the Synapse media store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:123
+msgid "To import the Synapse media store, you're supposed to invoke the `import_synapse` tool which is part of the matrix-media-repo container image. Your Synapse database is called `synapse` by default, unless you've changed it by modifying `matrix_synapse_database_database`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:125
+msgid "This guide here is adapted from the [upstream documentation about the import_synapse script](https://github.com/turt2live/matrix-media-repo#importing-media-from-synapse)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:127
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:149
+msgid "Run the following command on the server (after replacing `postgres_connection_password` in it with the value found in your `vars.yml` file):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:139
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:161
+msgid "Enter `1` for the Machine ID when prompted (you are not doing any horizontal scaling) unless you know what you're doing."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:141
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:163
+msgid "This should output a `msg=\"Import completed\"` when finished successfully!"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:143
+msgid "Importing data from the Dendrite media store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:145
+msgid "If you're using the [Dendrite](configuring-playbook-dendrite.md) homeserver instead of the default for this playbook (Synapse), follow this importing guide here."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-media-repo.md:147
+msgid "To import the Dendrite media store, you're supposed to invoke the `import_dendrite` tool which is part of the matrix-media-repo container image. Your Dendrite database is called `dendrite_mediaapi` by default, unless you've changed it by modifying `matrix_dendrite_media_api_database`."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-matrix-registration.pot b/i18n/translation-templates/docs/configuring-playbook-matrix-registration.pot
new file mode 100644
index 000000000..7e114683c
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-matrix-registration.pot
@@ -0,0 +1,153 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-matrix-registration.md:1
+msgid "Setting up matrix-registration (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:3
+msgid "The playbook can install and configure [matrix-registration](https://github.com/ZerataX/matrix-registration) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:5
+msgid "**WARNING**: this is a poorly maintained and buggy project. It's better to avoid using it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:7
+msgid "**WARNING**: this is not related to [matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:9
+msgid "matrix-registration is a simple python application to have a token based Matrix registration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:11
+msgid "Use matrix-registration to **create unique registration links**, which people can use to register on your Matrix server. It allows you to **keep your server's registration closed (private)**, but still allow certain people (these having a special link) to register a user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:13
+msgid "**matrix-registration** provides 2 things:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:15
+msgid "**an API for creating registration tokens** (unique registration links). This API can be used via `curl` or via the playbook (see [Usage](#usage) below)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:17
+msgid "**a user registration page**, where people can use these registration tokens. By default, exposed at `https://matrix.example.com/matrix-registration`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:19
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:21
+msgid "To enable matrix-registration, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:30
+msgid "Adjusting the matrix-registration URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:32
+msgid "By default, this playbook installs the matrix-registration on the `matrix.` subdomain, at the `/matrix-registration` path (https://matrix.example.com/matrix-registration). 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-matrix-registration.md:34
+msgid "By tweaking the `matrix_registration_hostname` and `matrix_registration_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-matrix-registration.md:36
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:44
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:46
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the matrix-registration domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:48
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:50
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:52
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:54
+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-matrix-registration.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-matrix-registration.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-matrix-registration.md:65
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:67
+msgid "**matrix-registration** gets exposed at `https://matrix.example.com/matrix-registration`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:69
+msgid "It provides various [APIs](https://github.com/ZerataX/matrix-registration/wiki/api) - for creating registration tokens, listing tokens, disabling tokens, etc. To make use of all of its capabilities, consider using `curl`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:71
+msgid "We make the most common APIs easy to use via the playbook (see below)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:73
+msgid "Creating registration tokens"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:75
+msgid "To **create a new user registration token (link)**, use this command:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:83
+msgid "The above command creates and returns a **one-time use** token, which **expires** on the 31st of December 2021. Adjust the `one_time` and `ex_date` variables as you see fit."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:85
+msgid "Share the unique registration link (generated by the command above) with users to let them register on your Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:87
+msgid "Listing registration tokens"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:89
+msgid "To **list the existing user registration tokens**, use this command:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-registration.md:96
+msgid "The shortcut command with `just` program is also available: `just run-tags list-matrix-registration-tokens`"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-mautrix-bridges.pot b/i18n/translation-templates/docs/configuring-playbook-mautrix-bridges.pot
new file mode 100644
index 000000000..f97eeeb58
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-mautrix-bridges.pot
@@ -0,0 +1,178 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-mautrix-bridges.md:1
+msgid "Setting up a Generic Mautrix Bridge (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:3
+msgid "The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, facebook, instagram, signal, hangouts, googlechat, etc.), as well as many other (non-mautrix) bridges. This is a common guide for configuring mautrix bridges."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:5
+msgid "You can see each bridge's features at in the `ROADMAP.md` file in its corresponding [mautrix](https://github.com/mautrix) repository."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:9
+msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:16
+msgid "There are some additional things you may wish to configure about the bridge before you continue. Each bridge may have additional requirements besides `_enabled: true`. For example, the mautrix-telegram bridge (our documentation page about it is [here](configuring-playbook-bridge-mautrix-telegram.md)) requires the `matrix_mautrix_telegram_api_id` and `matrix_mautrix_telegram_api_hash` variables to be defined. Refer to each bridge's individual documentation page for details about enabling bridges."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:18
+msgid "To **configure a user as an administrator for all bridges**, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:24
+msgid "**Alternatively** (more verbose, but allows multiple admins to be configured), you can do the same on a per-bridge basis with:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:33
+msgid "encryption"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:35
+msgid "Encryption support is off by default. If you would like to enable encryption, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:37
+msgid "**for all bridges with encryption support**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:44
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:61
+msgid "**Alternatively**, for a specific bridge:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:51
+msgid "relay mode"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:53
+msgid "Relay mode is off by default. If you would like to enable relay mode, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:55
+msgid "**for all bridges with relay mode support**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:70
+msgid "You can only have one `matrix_mautrix_SERVICENAME_configuration_extension_yaml` definition in `vars.yml` per bridge, so if you need multiple pieces of configuration there, just merge them like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:82
+msgid "Setting the bot's username"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:88
+msgid "Can be used to set the username for the bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:90
+msgid "Discovering additional configuration options"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:92
+msgid "You may wish to look at `roles/custom/matrix-bridge-mautrix-SERVICENAME/templates/config.yaml.j2` and `roles/custom/matrix-bridge-mautrix-SERVICENAME/defaults/main.yml` to find other things you would like to configure."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:94
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:96
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:103
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:105
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:107
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:109
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:111
+msgid "Set up Double Puppeting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:113
+msgid "To set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) enable the [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:115
+msgid "The bridge automatically performs Double Puppeting if [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) is configured and enabled on the server for this playbook by adding"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:121
+msgid "This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:123
+msgid "Controlling the logging level"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:129
+msgid "to `vars.yml` to control the logging level, where you may replace WARN with one of the following to control the verbosity of the logs generated: TRACE, DEBUG, INFO, WARN, ERROR, or FATAL."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:131
+msgid "If you have issues with a service, and are requesting support, the higher levels of logging will generally be more helpful."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:133
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:135
+msgid "To use the bridge, you need to start a chat with `@SERVICENAMEbot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:137
+msgid "Send `login` to the bridge bot to get started. You can learn more here about authentication from the bridge's official documentation on Authentication: https://docs.mau.fi/bridges/python/SERVICENAME/authentication.html"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:139
+msgid "If you run into trouble, check the [Troubleshooting](#troubleshooting) section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:141
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:143
+msgid "For troubleshooting information with a specific bridge, please see the playbook documentation about it (some other document in in `docs/`) and the upstream ([mautrix](https://github.com/mautrix)) bridge documentation for that specific bridge."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-mautrix-bridges.md:145
+msgid "Reporting bridge bugs should happen upstream, in the corresponding mautrix repository, not to us."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-nginx.pot b/i18n/translation-templates/docs/configuring-playbook-nginx.pot
new file mode 100644
index 000000000..9350df977
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-nginx.pot
@@ -0,0 +1,25 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-nginx.md:1
+msgid "Configure Nginx (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-nginx.md:3
+msgid "Since 2024-01, this playbook no longer uses nginx as its reverse-proxy."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-ntfy.pot b/i18n/translation-templates/docs/configuring-playbook-ntfy.pot
new file mode 100644
index 000000000..f9e46f031
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-ntfy.pot
@@ -0,0 +1,233 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-ntfy.md:1
+msgid "Setting up the ntfy push notifications server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:3
+msgid "The playbook can install and configure the [ntfy](https://ntfy.sh/) push notifications server for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:5
+msgid "Using the [UnifiedPush](https://unifiedpush.org) standard, ntfy enables self-hosted (Google-free) push notifications from Matrix (and other) servers to UnifiedPush-compatible Matrix compatible client apps running on Android and other devices."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:7
+msgid "This role is intended to support UnifiedPush notifications for use with the Matrix and Matrix-related services that this playbook installs. This role is not intended to support all of ntfy's other features."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:9
+msgid "**Note**: In contrast to push notifications using Google's FCM or Apple's APNs, the use of UnifiedPush allows each end-user to choose the push notification server that they prefer.  As a consequence, deploying this ntfy server does not by itself ensure any particular user or device or client app will use it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:13
+msgid "To enable ntfy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:27
+msgid "For a more complete list of variables that you could override, see the [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/defaults/main.yml) of the ntfy Ansible role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:29
+msgid "For a complete list of ntfy config options that you could put in `ntfy_configuration_extension_yaml`, see the [ntfy config documentation](https://ntfy.sh/docs/config/#config-options)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:31
+msgid "Adjusting the ntfy URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:33
+msgid "By default, this playbook installs ntfy on the `ntfy.` subdomain (`ntfy.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:35
+msgid "By tweaking the `ntfy_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:37
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:44
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:46
+msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the ntfy domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:48
+msgid "By default, you will need to create a CNAME record for `ntfy`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:50
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:52
+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-ntfy.md:59
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:61
+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-ntfy.md:63
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:65
+msgid "To make use of your ntfy installation, on Android for example, you need two things:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:67
+msgid "the `ntfy` app"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:68
+msgid "a UnifiedPush-compatible Matrix app"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:70
+msgid "You need to install the `ntfy` app on each device on which you want to receive push notifications through your ntfy server. The `ntfy` app will provide UnifiedPush notifications to any number of UnifiedPush-compatible messaging apps installed on the same device."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:72
+msgid "Setting up the `ntfy` Android app"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:74
+msgid "Install the [ntfy Android app](https://ntfy.sh/docs/subscribe/phone/) from F-droid or Google Play."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:75
+msgid "In its Settings -> `General: Default server`, enter your ntfy server URL, such as `https://ntfy.example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:76
+msgid "In its Settings -> `Advanced: Connection protocol`, choose `WebSockets`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:78
+msgid "That is all you need to do in the ntfy app. It has many other features, but for our purposes you can ignore them. In particular you do not need to follow any instructions about subscribing to a notification topic as UnifiedPush will do that automatically."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:80
+msgid "Setting up a UnifiedPush-compatible Matrix app"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:82
+msgid "Install any UnifiedPush-enabled Matrix app on that same device. The Matrix app will learn from the `ntfy` app that you have configured UnifiedPush on this device, and then it will tell your Matrix server to use it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:84
+msgid "Steps needed for specific Matrix apps:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:86
+msgid "FluffyChat-android:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:87
+msgid "Should auto-detect and use it. No manual settings."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:89
+msgid "SchildiChat-android:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:90
+msgid "enable `Settings` -> `Notifications` -> `UnifiedPush: Force custom push gateway`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:91
+msgid "choose `Settings` -> `Notifications` -> `UnifiedPush: Re-register push distributor`. *(For info, a more complex alternative to achieve the same is: delete the relevant unifiedpush registration in `ntfy` app, force-close SchildiChat, re-open it.)*"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:92
+msgid "verify `Settings` -> `Notifications` -> `UnifiedPush: Notification targets` as described below in the \"Troubleshooting\" section."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:94
+msgid "Element-android v1.4.26+:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:95
+msgid "choose `Settings` -> `Notifications` -> `Notification method` -> `ntfy`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:96
+msgid "verify `Settings` -> `Troubleshoot` -> `Troubleshoot notification settings`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:98
+msgid "If the Matrix app asks, \"Choose a distributor: FCM Fallback or ntfy\", then choose \"ntfy\"."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:100
+msgid "If the Matrix app doesn't seem to pick it up, try restarting it and try the Troubleshooting section below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:102
+msgid "Web App"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:104
+msgid "ntfy also has a web app to subscribe to and push to topics from the browser. This may be helpful to further troubleshoot UnifiedPush problems or to use ntfy for other purposes. The web app only runs in the browser locally (after downloading the JavaScript)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:106
+msgid "The web app is disabled in this playbook by default as the expectation is that most users won't use it. You can either use the [official hosted one](https://ntfy.sh/app) (it supports using other public reachable ntfy instances) or host it yourself by setting `ntfy_web_root: \"app\"` and re-running Ansible."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:108
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:110
+msgid "First check that the Matrix client app you are using supports UnifiedPush. There may well be different variants of the app."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:112
+msgid "Set the ntfy server's log level to 'DEBUG', as shown in the example settings above, and watch the server's logs with `sudo journalctl -fu matrix-ntfy`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:114
+msgid "To check if UnifiedPush is correctly configured on the client device, look at \"Settings -> Notifications -> Notification Targets\" in Element Android or SchildiChat Android, or \"Settings -> Notifications -> Devices\" in FluffyChat. There should be one entry for each Matrix client app that has enabled push notifications, and when that client is using UnifiedPush you should see a URL that begins with your ntfy server's URL."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:116
+msgid "In the \"Notification Targets\" screen in Element Android or SchildiChat Android, two relevant URLs are shown, \"push\\_key\" and \"Url\", and both should begin with your ntfy server's URL. If \"push\\_key\" shows your server but \"Url\" shows an external server such as `up.schildi.chat` then push notifications will still work but are being routed through that external server before they reach your ntfy server. To rectify that, in SchildiChat (at least around version 1.4.20.sc55) you must enable the `Force custom push gateway` setting as described in the \"Usage\" section above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:118
+msgid "If it is not working, useful tools are \"Settings -> Notifications -> Re-register push distributor\" and \"Settings -> Notifications -> Troubleshoot Notifications\" in SchildiChat Android (possibly also Element Android). In particular the \"Endpoint/FCM\" step of that troubleshooter should display your ntfy server's URL that it has discovered from the ntfy client app."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ntfy.md:120
+msgid "The simple [UnifiedPush troubleshooting](https://unifiedpush.org/users/troubleshooting/) app [UP-Example](https://f-droid.org/en/packages/org.unifiedpush.example/) can be used to manually test UnifiedPush registration and operation on an Android device."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-own-webserver.pot b/i18n/translation-templates/docs/configuring-playbook-own-webserver.pot
new file mode 100644
index 000000000..ed74fe60c
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-own-webserver.pot
@@ -0,0 +1,189 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-own-webserver.md:1
+msgid "Using your own webserver, instead of this playbook's Traefik reverse-proxy (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:3
+msgid "By default, this playbook installs its own [Traefik](https://traefik.io/) reverse-proxy server (in a Docker container) which listens on ports 80 and 443. If that's okay, you can skip this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:5
+msgid "Traefik"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:7
+msgid "[Traefik](https://traefik.io/) is the default reverse-proxy for the playbook since [2023-02-26](../CHANGELOG.md/#2023-02-26) and serves **2 purposes**:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:9
+msgid "serving public traffic and providing SSL-termination with certificates obtained from [Let's Encrypt](https://letsencrypt.org/). See [Adjusting SSL certificate retrieval](./configuring-playbook-ssl-certificates.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:11
+msgid "assists internal communication between addon services (briges, bots, etc.) and the homeserver via an internal entrypoint (`matrix-internal-matrix-client-api`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:13
+msgid "There are 2 ways to use Traefik with this playbook, as described below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:15
+msgid "Traefik managed by the playbook"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:17
+msgid "To have the playbook install and use Traefik, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:25
+msgid "Traefik will manage SSL certificates for all services seamlessly."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:27
+msgid "Traefik managed by you"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:53
+msgid "In this mode all roles will still have Traefik labels attached. You will, however, need to configure your Traefik instance and its entrypoints."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:55
+msgid "By default, the playbook configured a `default` certificate resolver and multiple entrypoints."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:57
+msgid "You need to configure 4 entrypoints for your Traefik server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:59
+msgid "`web` (TCP port `80`) - used for redirecting to HTTPS (`web-secure`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:60
+msgid "`web-secure` (TCP port `443`) - used for exposing the Matrix Client-Server API and all other services"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:61
+msgid "`matrix-federation` (TCP port `8448`) - used for exposing the Matrix Federation API"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:62
+msgid "`matrix-internal-matrix-client-api` (TCP port `8008`) - used internally for addon services (bridges, bots) to communicate with the homserver"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:64
+msgid "Below is some configuration for running Traefik yourself, although we recommend using [Traefik managed by the playbook](#traefik-managed-by-the-playbook)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:66
+msgid "Note that this configuration on its own does **not** redirect traffic on port 80 (plain HTTP) to port 443 for HTTPS. If you are not already doing this in Traefik, it can be added to Traefik in a [file provider](https://docs.traefik.io/v2.0/providers/file/) as follows:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:86
+msgid "You can use the following `docker-compose.yml` as example to launch Traefik."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:122
+msgid "Another webserver"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:124
+msgid "If you don't wish to use Traefik, you can also use your own webserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:126
+msgid "Doing this is possible, but requires manual work."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:128
+msgid "There are 2 ways to go about it:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:130
+msgid "(recommended) [Fronting the integrated reverse-proxy webserver with another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) - using the playbook-managed reverse-proxy (Traefik), but disabling SSL termination for it, exposing this reverse-proxy on a few local ports (e.g. `127.0.0.1:81`, etc.) and forwarding traffic from your own webserver to those few ports"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:132
+msgid "(difficult) [Using no reverse-proxy on the Matrix side at all](#using-no-reverse-proxy-on-the-matrix-side-at-all) disabling the playbook-managed reverse-proxy (Traefik), exposing services one by one using `_host_bind_port` variables and forwarding traffic from your own webserver to those ports"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:134
+msgid "Fronting the integrated reverse-proxy webserver with another reverse-proxy"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:136
+msgid "This method is about leaving the integrated reverse-proxy webserver be, but making it not get in the way (using up important ports, trying to retrieve SSL certificates, etc.)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:138
+msgid "If you wish to use another webserver, the integrated reverse-proxy webserver usually gets in the way because it attempts to fetch SSL certificates and binds to ports 80, 443 and 8448 (if Matrix Federation is enabled)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:140
+msgid "You can disable such behavior and make the integrated reverse-proxy webserver only serve traffic locally on the host itself (or over a local network)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:142
+msgid "This is the recommended way for using another reverse-proxy, because the integrated one would act as a black box and wire all Matrix services correctly. You would then only need to reverse-proxy a few individual domains and ports over to it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:144
+msgid "To front Traefik with another reverse-proxy, you would need some configuration like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:194
+msgid "Such a configuration would expose all services on a local port `81` and Matrix Federation on a local port `8449`. Your reverse-proxy configuration needs to send traffic to these ports. [`examples/reverse-proxies`](../examples/reverse-proxies/) contains examples for various webservers such as Apache2, Caddy, HAproxy, nginx and Nginx Proxy Manager."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:196
+msgid "It's important that these webservers proxy-pass requests to the correct `ip:port` and also set the `Host` HTTP header appropriately. If you don't pass the `Host` header correctly, Traefik will return a `404 - not found` error."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:198
+msgid "To put it another way:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:199
+msgid "`curl http://127.0.0.1:81` will result in a `404 - not found` error"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:200
+msgid "but `curl -H 'Host: matrix.example.com' http://127.0.0.1:81` should work."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:202
+msgid "Using no reverse-proxy on the Matrix side at all"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:204
+msgid "Instead of [Fronting the integrated reverse-proxy webserver with another reverse-proxy](#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy), you can also go another way -- completely disabling the playbook-managed Traefik reverse-proxy. You would then need to reverse-proxy from your own webserver directly to each individual Matrix service."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:206
+msgid "This is more difficult, as you would need to handle the configuration for each service manually. Enabling additional services would come with extra manual work you need to do."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:208
+msgid "Also, the Traefik reverse-proxy, besides fronting everything is also serving a 2nd purpose of allowing addons services to communicate with the Matrix homeserver thanks to its `matrix-internal-matrix-client-api` entrypoint (read more about it above). Disabling Traefik completely means the playbook would wire services to directly talk to the homeserver. This can work for basic setups, but not for more complex setups involving [matrix-media-repo](./configuring-playbook-matrix-media-repo.md), [matrix-corporal](./configuring-playbook-matrix-corporal.md) or other such services that need to \"steal routes\" from the homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-own-webserver.md:210
+msgid "If your webserver is on the same machine, ensure your web server user (something like `http`, `apache`, `www-data`, `nginx`) is part of the `matrix` group. You should run something like this: `usermod -a -G matrix nginx`. This allows your webserver user to access files owned by the `matrix` group, so that it can serve static files from `/matrix/static-files`."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-pantalaimon.pot b/i18n/translation-templates/docs/configuring-playbook-pantalaimon.pot
new file mode 100644
index 000000000..cfe438475
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-pantalaimon.pot
@@ -0,0 +1,61 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 09:53+0200\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-pantalaimon.md:1
+msgid "Setting up Pantalaimon (E2EE aware proxy daemon) (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:3
+msgid "The playbook can install and configure the [pantalaimon](https://github.com/matrix-org/pantalaimon) E2EE aware proxy daemon for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:5
+msgid "See the project's [documentation](https://github.com/matrix-org/pantalaimon/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:7
+msgid "This role exposes Pantalaimon's API only within the container network, so bots and clients installed on the same machine can use it. In particular the [Draupnir](configuring-playbook-bot-draupnir.md) and [Mjolnir](configuring-playbook-bot-mjolnir.md) roles (and possibly others) can use it."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:11
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:17
+msgid "The default configuration should suffice. For advanced configuration, you can override the variables documented in the role's [defaults](../roles/custom/matrix-pantalaimon/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:19
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:21
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:28
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-pantalaimon.md:30
+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 ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-postgres-backup.pot b/i18n/translation-templates/docs/configuring-playbook-postgres-backup.pot
new file mode 100644
index 000000000..80f120d2c
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-postgres-backup.pot
@@ -0,0 +1,153 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-postgres-backup.md:1
+msgid "Setting up postgres backup (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:3
+msgid "The playbook can install and configure [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) for you via the [ansible-role-postgres-backup](https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup) Ansible role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:5
+msgid "For a more complete backup solution (one that includes not only Postgres, but also other configuration/data files), you may wish to look into [BorgBackup](configuring-playbook-backup-borg.md) instead."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:9
+msgid "To enable Postgres backup, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:15
+msgid "Refer to the table below for additional configuration variables and their default values."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "Name"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "Default value"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "Description"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "`postgres_backup_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "`false`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "Set to true to use [docker-postgres-backup-local](https://github.com/prodrigestivill/docker-postgres-backup-local) to create automatic database backups"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "`postgres_backup_schedule`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "`'@daily'`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "Cron-schedule specifying the interval between postgres backups."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "`postgres_backup_keep_days`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "`7`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "Number of daily backups to keep"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "`postgres_backup_keep_weeks`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "`4`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "Number of weekly backups to keep"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "`postgres_backup_keep_months`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "`12`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "Number of monthly backups to keep"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "`postgres_backup_base_path`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "`\"{{ matrix_base_data_path }}/postgres-backup\"`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "Base path for postgres-backup. Also see `postgres_backup_data_path`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "`postgres_backup_data_path`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "`\"{{ postgres_backup_base_path }}/data\"`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:0
+msgid "Storage path for postgres-backup database backups"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:27
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:29
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:36
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-postgres-backup.md:38
+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 ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-prometheus-grafana.pot b/i18n/translation-templates/docs/configuring-playbook-prometheus-grafana.pot
new file mode 100644
index 000000000..28993edba
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-prometheus-grafana.pot
@@ -0,0 +1,341 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-prometheus-grafana.md:1
+msgid "Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:3
+msgid "The playbook can install [Grafana](https://grafana.com/) with [Prometheus](https://prometheus.io/) and configure performance metrics of your homeserver with graphs for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:5
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:7
+msgid "To enable Grafana and/or Prometheus, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:33
+msgid "The retention policy of Prometheus metrics is [15 days by default](https://prometheus.io/docs/prometheus/latest/storage/#operational-aspects). Older data gets deleted automatically."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:35
+msgid "Adjusting the Grafana URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:37
+msgid "By default, this playbook installs Grafana web user-interface on the `stats.` subdomain (`stats.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:39
+msgid "By tweaking the `grafana_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:41
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:48
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:50
+msgid "Once you've decided on the domain, **you may need to adjust your DNS** records to point the Grafana domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:52
+msgid "By default, you will need to create a CNAME record for `stats`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:54
+msgid "**Note**: It is possible to install Prometheus without installing Grafana. This case it is not required to create the CNAME record."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:56
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:58
+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-prometheus-grafana.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-prometheus-grafana.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-prometheus-grafana.md:69
+msgid "What does it do?"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Name"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Description"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`prometheus_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "[Prometheus](https://prometheus.io) is a time series database. It holds all the data we're going to talk about."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`prometheus_node_exporter_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "[Node Exporter](https://prometheus.io/docs/guides/node-exporter/) is an addon of sorts to Prometheus that collects generic system information such as CPU, memory, filesystem, and even system temperatures"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`prometheus_postgres_exporter_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "[Postgres Exporter](configuring-playbook-prometheus-postgres.md) is an addon of sorts to expose Postgres database metrics to Prometheus."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`matrix_prometheus_nginxlog_exporter_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "[NGINX Log Exporter](configuring-playbook-prometheus-nginxlog.md) is an addon of sorts to expose NGINX logs to Prometheus."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`grafana_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "[Grafana](https://grafana.com/) is the visual component. It shows (on the `stats.example.com` subdomain) the dashboards with the graphs that we're interested in"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`grafana_anonymous_access`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "By default you need to log in to see graphs. If you want to publicly share your graphs (e.g. when asking for help in [`#synapse:matrix.org`](https://matrix.to/#/#synapse:matrix.org?via=matrix.org&via=privacytools.io&via=mozilla.org)) you'll want to enable this option."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`grafana_default_admin_user`<br>`grafana_default_admin_password`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "By default Grafana creates a user with `admin` as the username and password. If you feel this is insecure and you want to change it beforehand, you can do that here"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:81
+msgid "Security and privacy"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:83
+msgid "Metrics and resulting graphs can contain a lot of information. This includes system specs but also usage patterns. This applies especially to small personal/family scale homeservers. Someone might be able to figure out when you wake up and go to sleep by looking at the graphs over time. Think about this before enabling anonymous access. And you should really not forget to change your Grafana password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:85
+msgid "Most of our docker containers run with limited system access, but the `prometheus-node-exporter` has access to the host network stack and (readonly) root filesystem. This is required to report on them. If you don't like that, you can set `prometheus_node_exporter_enabled: false` (which is actually the default). You will still get Synapse metrics with this container disabled. Both of the dashboards will always be enabled, so you can still look at historical data after disabling either source."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:87
+msgid "Collecting metrics to an external Prometheus server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:89
+msgid "**If the integrated Prometheus server is enabled** (`prometheus_enabled: true`), metrics are collected by it from each service via communication that happens over the container network. Each service does not need to expose its metrics \"publicly\"."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:91
+msgid "When you'd like **to collect metrics from an external Prometheus server**, you need to expose service metrics outside of the container network."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:93
+msgid "The playbook provides a single endpoint (`https://matrix.example.com/metrics/*`), under which various services may expose their metrics (e.g. `/metrics/node-exporter`, `/metrics/postgres-exporter`, `/metrics/hookshot`, etc). To expose all services on this `/metrics/*` feature, use `matrix_metrics_exposure_enabled`. To protect access using [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication), see `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users` below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:95
+msgid "When using `matrix_metrics_exposure_enabled`, you don't need to expose metrics for individual services one by one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:97
+msgid "The following variables may be of interest:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`matrix_metrics_exposure_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Set this to `true` to **enable metrics exposure for all services** on `https://matrix.example.com/metrics/*`. If you think this is too much, refer to the helpful (but nonexhaustive) list of individual `matrix_SERVICE_metrics_proxying_enabled` (or similar) variables below for exposing metrics on a per-service basis."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`matrix_metrics_exposure_http_basic_auth_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Set this to `true` to protect all `https://matrix.example.com/metrics/*` endpoints with [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) (see the other variables below for supplying the actual credentials). When enabled, all endpoints beneath `/metrics` will be protected with the same credentials"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`matrix_metrics_exposure_http_basic_auth_users`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Set this to the Basic Authentication credentials (raw `htpasswd` file content) used to protect `/metrics/*`. This htpasswd-file needs to be generated with the `htpasswd` tool and can include multiple username/password pairs."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`matrix_synapse_metrics_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Set this to `true` to make Synapse expose metrics (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`matrix_synapse_metrics_proxying_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Set this to `true` to expose Synapse's metrics on `https://matrix.example.com/metrics/synapse/main-process` and `https://matrix.example.com/metrics/synapse/worker/TYPE-ID`. Read [below](#collecting-synapse-worker-metrics-to-an-external-prometheus-server) if you're running a Synapse worker setup (`matrix_synapse_workers_enabled: true`). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Set this to `true` to enable the node (general system stats) exporter (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`prometheus_node_exporter_container_labels_traefik_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Set this to `true` to expose the node (general system stats) metrics on `https://matrix.example.com/metrics/node-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Set this to `true` to enable the [Postgres exporter](configuring-playbook-prometheus-postgres.md) (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Set this to `true` to expose the [Postgres exporter](configuring-playbook-prometheus-postgres.md) metrics on `https://matrix.example.com/metrics/postgres-exporter`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Set this to `true` to enable the [NGINX Log exporter](configuring-playbook-prometheus-nginxlog.md) (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`matrix_sliding_sync_metrics_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Set this to `true` to make [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) expose metrics (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`matrix_sliding_sync_metrics_proxying_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Set this to `true` to expose the [Sliding Sync](configuring-playbook-sliding-sync-proxy.md) metrics on `https://matrix.example.com/metrics/sliding-sync`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`matrix_bridge_hookshot_metrics_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Set this to `true` to make [Hookshot](configuring-playbook-bridge-hookshot.md) expose metrics (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`matrix_bridge_hookshot_metrics_proxying_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Set this to `true` to expose the [Hookshot](configuring-playbook-bridge-hookshot.md) metrics on `https://matrix.example.com/metrics/hookshot`. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`matrix_SERVICE_metrics_proxying_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Various other services/roles may provide similar `_metrics_enabled` and `_metrics_proxying_enabled` variables for exposing their metrics. Refer to each role for details. To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` above or `matrix_SERVICE_container_labels_metrics_middleware_basic_auth_enabled`/`matrix_SERVICE_container_labels_metrics_middleware_basic_auth_users` variables provided by each role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "`matrix_media_repo_metrics_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:0
+msgid "Set this to `true` to make media-repo expose metrics (locally, on the container network)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:118
+msgid "Collecting Synapse worker metrics to an external Prometheus server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:120
+msgid "If you are using workers (`matrix_synapse_workers_enabled: true`) and have enabled `matrix_synapse_metrics_proxying_enabled` as described above, the playbook will also automatically expose all Synapse worker threads' metrics to `https://matrix.example.com/metrics/synapse/worker/ID`, where `ID` corresponds to the worker `id` as exemplified in `matrix_synapse_workers_enabled_list`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:122
+msgid "The playbook also generates an exemplary config file (`/matrix/synapse/external_prometheus.yml.template`) with all the correct paths which you can copy to your Prometheus server and adapt to your needs. Make sure to edit the specified `password_file` path and contents and path to your `synapse-v2.rules`. It will look a bit like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:150
+msgid "More information"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:152
+msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:153
+msgid "[Understanding Synapse Performance Issues Through Grafana Graphs](https://element-hq.github.io/synapse/latest/usage/administration/understanding_synapse_through_grafana_graphs.html) at the Synapse Github Wiki"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:154
+msgid "[The Prometheus scraping rules](https://github.com/element-hq/synapse/tree/master/contrib/prometheus) (we use v2)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:155
+msgid "[The Synapse Grafana dashboard](https://github.com/element-hq/synapse/tree/master/contrib/grafana)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-grafana.md:156
+msgid "[The Node Exporter dashboard](https://github.com/rfrail3/grafana-dashboards) (for generic non-synapse performance graphs)"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-prometheus-nginxlog.pot b/i18n/translation-templates/docs/configuring-playbook-prometheus-nginxlog.pot
new file mode 100644
index 000000000..eda234799
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-prometheus-nginxlog.pot
@@ -0,0 +1,109 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-prometheus-nginxlog.md:1
+msgid "Enabling metrics and graphs for NginX logs (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:3
+msgid "It can be useful to have some (visual) insight into [nginx](https://nginx.org/) logs."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:5
+msgid "This adds [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) to your Matrix deployment."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:7
+msgid "It will collect access logs from various nginx reverse-proxies which may be used internally (e.g. `matrix-synapse-reverse-proxy-companion`, if Synapse workers are enabled) and will make them available at a Prometheus-compatible `/metrics` endpoint."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:9
+msgid "**Note**: nginx is only used internally by this Ansible playbook. With Traefik being our default reverse-proxy, collecting nginx metrics is less relevant."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:11
+msgid "To make use of this, you need to install [Prometheus](./configuring-playbook-prometheus-grafana.md) either via the playbook or externally. When using an external Prometheus, configuration adjustments are necessary - see [Save metrics on an external Prometheus server](#save-metrics-on-an-external-prometheus-server)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:13
+msgid "If your setup includes [Grafana](./configuring-playbook-prometheus-grafana.md), a dedicated `NGINX PROXY` Grafana dashboard will be created."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:15
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:17
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:23
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:25
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:32
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:34
+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-prometheus-nginxlog.md:36
+msgid "Docker Image Compatibility"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:38
+msgid "At the moment of writing only images for `amd64` and `arm64` architectures are available. The playbook currently does not support [self-building](./self-building.md) a container image on other architectures. You can however use a custom-build image by setting:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:45
+msgid "Security and privacy"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:47
+msgid "Metrics and resulting graphs can contain a lot of information. NginX logs contain information like IP address, URLs, UserAgents and more. This information can reveal usage patterns and could be considered Personally Identifiable Information (PII). Think about this before enabling (anonymous) access. Please make sure you change the default Grafana password."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:49
+msgid "Save metrics on an external Prometheus server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:51
+msgid "The playbook will automatically integrate the metrics into the [Prometheus](./configuring-playbook-prometheus-grafana.md) server provided with this playbook (if enabled). In such cases, the metrics endpoint is not exposed publicly - it's only available on the container network."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:53
+msgid "When using an external Prometheus server, you'll need to expose metrics publicly. See [Collecting metrics to an external Prometheus server](./configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:55
+msgid "You can either use `matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled: true` to expose just this one service, or `matrix_metrics_exposure_enabled: true` to expose all services."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:57
+msgid "Whichever way you go with, this service will expose its metrics endpoint **without password-protection** at `https://matrix.example.com/metrics/nginxlog` by default."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-nginxlog.md:59
+msgid "For password-protection, use (`matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users`) or (`matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_enabled` and `matrix_prometheus_nginxlog_exporter_container_labels_metrics_middleware_basic_auth_users`)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-prometheus-postgres.pot b/i18n/translation-templates/docs/configuring-playbook-prometheus-postgres.pot
new file mode 100644
index 000000000..07c9456bd
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-prometheus-postgres.pot
@@ -0,0 +1,101 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-prometheus-postgres.md:1
+msgid "Enabling metrics and graphs for Postgres (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:3
+msgid "Expanding on the metrics exposed by the [synapse exporter and the node exporter](configuring-playbook-prometheus-grafana.md), the playbook enables the [postgres exporter](https://github.com/prometheus-community/postgres_exporter) that exposes more detailed information about what's happening on your postgres database."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:5
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:7
+msgid "To enable the postgres exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:13
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:15
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:22
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:24
+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-prometheus-postgres.md:26
+msgid "What does it do?"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:0
+msgid "Name"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:0
+msgid "Description"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:0
+msgid "`prometheus_postgres_exporter_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:0
+msgid "Enable the postgres prometheus exporter. This sets up the docker container, connects it to the database and adds a 'job' to the prometheus config which tells prometheus about this new exporter. The default is 'false'"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:0
+msgid "`prometheus_postgres_exporter_database_username`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:0
+msgid "The 'username' for the user that the exporter uses to connect to the database. The default is 'matrix_prometheus_postgres_exporter'"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:0
+msgid "`prometheus_postgres_exporter_database_password`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:0
+msgid "The 'password' for the user that the exporter uses to connect to the database. By default, this is auto-generated by the playbook"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:0
+msgid "`prometheus_postgres_exporter_container_labels_traefik_enabled`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:0
+msgid "If set to `true`, exposes the Postgres exporter metrics on `https://matrix.example.com/metrics/postgres-exporter` for usage with an [external Prometheus server](configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server). To password-protect the metrics, see `matrix_metrics_exposure_http_basic_auth_users` on that other documentation page."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:35
+msgid "More information"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-prometheus-postgres.md:37
+msgid "[The PostgresSQL dashboard](https://grafana.com/grafana/dashboards/9628) (generic postgres dashboard)"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-rageshake.pot b/i18n/translation-templates/docs/configuring-playbook-rageshake.pot
new file mode 100644
index 000000000..1fa606dc9
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-rageshake.pot
@@ -0,0 +1,101 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-rageshake.md:1
+msgid "Setting up the rageshake bug report server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:3
+msgid "The playbook can install and configure the [rageshake](https://github.com/matrix-org/rageshake) bug report server for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:5
+msgid "This is useful if you're developing your own applications and would like to collect bug reports for them."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:9
+msgid "To enable rageshake, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:15
+msgid "rageshake has various options which don't have dedicated Ansible variables. You can see the full list of options in the [`rageshake.sample.yaml` file](https://github.com/matrix-org/rageshake/blob/master/rageshake.sample.yaml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:17
+msgid "To set these, you can make use of the  `matrix_rageshake_configuration_extension_yaml` variable like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:27
+msgid "Adjusting the rageshake URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:29
+msgid "By default, this playbook installs rageshake on the `rageshake.` subdomain (`rageshake.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:31
+msgid "By tweaking the `matrix_rageshake_hostname` and `matrix_rageshake_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-rageshake.md:33
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:44
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:46
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the rageshake domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:48
+msgid "By default, you will need to create a CNAME record for `rageshake`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:50
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:52
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:54
+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-rageshake.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-rageshake.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-rageshake.md:65
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rageshake.md:67
+msgid "Refer to the [rageshake documentation](https://github.com/matrix-org/rageshake) for available APIs, etc."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-rest-auth.pot b/i18n/translation-templates/docs/configuring-playbook-rest-auth.pot
new file mode 100644
index 000000000..18b3def98
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-rest-auth.pot
@@ -0,0 +1,61 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 09:53+0200\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-rest-auth.md:1
+msgid "Setting up the REST authentication password provider module (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:3
+msgid "The playbook can install and configure [matrix-synapse-rest-auth](https://github.com/ma1uta/matrix-synapse-rest-password-provider) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:5
+msgid "See the project's [documentation](https://github.com/ma1uta/matrix-synapse-rest-password-provider/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:9
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:19
+msgid "Authenticating only using a password provider"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:21
+msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:27
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:29
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:36
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-rest-auth.md:38
+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 ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-riot-web.pot b/i18n/translation-templates/docs/configuring-playbook-riot-web.pot
new file mode 100644
index 000000000..1e11e322b
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-riot-web.pot
@@ -0,0 +1,89 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-riot-web.md:1
+msgid "Configuring Riot-web (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:3
+msgid "By default, this playbook **used to install** the [Riot-web](https://github.com/element-hq/riot-web) Matrix client web application."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:5
+msgid "Riot has since been [renamed to Element](https://element.io/blog/welcome-to-element/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:7
+msgid "to learn more about Element Web and its configuration, see our dedicated [Configuring Element Web](configuring-playbook-client-element-web.md) documentation page"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:8
+msgid "to learn how to migrate from Riot to Element Web, see [Migrating to Element Web](#migrating-to-element-web) below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:10
+msgid "Migrating to Element Web"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:12
+msgid "Migrating your custom settings"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:14
+msgid "If you have custom `matrix_riot_web_` variables in your `inventory/host_vars/matrix.example.com/vars.yml` file, you'll need to rename them (`matrix_riot_web_` -> `matrix_client_element_`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:16
+msgid "Some other playbook variables (but not all) with `riot` in their name are also renamed. The playbook checks and warns if you are using the old name for some commonly used ones."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:18
+msgid "Domain migration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:20
+msgid "We used to set up Riot at the `riot.example.com` domain. The playbook now sets up Element Web at `element.example.com` by default."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:22
+msgid "There are a few options for handling this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:24
+msgid "(**avoiding changes** - using the old `riot.example.com` domain and avoiding DNS changes) -- to keep using `riot.example.com` instead of `element.example.com`, override the domain at which the playbook serves Element Web: `matrix_server_fqn_element: \"riot.{{ matrix_domain }}\"`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:26
+msgid "(**embracing changes** - using only `element.example.com`) - set up the `element.example.com` DNS record (see [Configuring DNS](configuring-dns.md)). You can drop the `riot.example.com` in this case."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:28
+msgid "Re-running the playbook"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:30
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:37
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-riot-web.md:39
+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 ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-s3-goofys.pot b/i18n/translation-templates/docs/configuring-playbook-s3-goofys.pot
new file mode 100644
index 000000000..768310b41
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-s3-goofys.pot
@@ -0,0 +1,178 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-s3-goofys.md:1
+msgid "Storing Matrix media files on Amazon S3 with Goofys (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:3
+msgid "If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service), you can let this playbook configure [Goofys](https://github.com/kahing/goofys) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:5
+msgid "Another (and better performing) way to use S3 storage with Synapse is [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:7
+msgid "Using a Goofys-backed media store works, but performance may not be ideal. If possible, try to use a region which is close to your Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:9
+msgid "If you'd like to move your locally-stored media store data to Amazon S3 (or another S3-compatible object store), we also provide some migration instructions below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:11
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:13
+msgid "After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:23
+msgid "You can use any S3-compatible object store by **additionally** configuring these variables:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:30
+msgid "If you have local media store files and wish to migrate to Backblaze B2 subsequently, follow our [migration guide to Backblaze B2](#migrating-to-backblaze-b2) below instead of applying this configuration as-is."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:32
+msgid "Migrating from local filesystem storage to S3"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:34
+msgid "It's a good idea to [make a complete server backup](faq.md#how-do-i-back-up-the-data-on-my-server) before migrating your local media store to an S3-backed one."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:36
+msgid "After making the backup, follow one of the guides below for a migration path from a locally-stored media store to one stored on S3-compatible storage:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:38
+msgid "[Migrating to any S3-compatible storage (universal, but likely slow)](#migrating-to-any-s3-compatible-storage-universal-but-likely-slow)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:39
+msgid "[Migrating to Backblaze B2](#migrating-to-backblaze-b2)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:41
+msgid "Migrating to any S3-compatible storage (universal, but likely slow)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:43
+msgid "Proceed with the steps below without stopping Matrix services"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:45
+msgid "Start by adding the base S3 configuration in your `vars.yml` file (seen above, may be different depending on the S3 provider of your choice)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:47
+msgid "In addition to the base configuration you see above, add this to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:53
+msgid "This enables S3 support, but mounts the S3 storage bucket to `/matrix/s3-media-store` without hooking it to your homeserver yet. Your homeserver will still continue using your local filesystem for its media store."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:55
+msgid "Run the playbook to apply the changes: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:57
+msgid "Do an **initial sync of your files** by running this **on the server** (it may take a very long time):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:63
+msgid "You may need to install `rsync` manually."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:65
+#: ../../../docs/configuring-playbook-s3-goofys.md:106
+msgid "Stop all Matrix services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:67
+msgid "Start the S3 service by running this **on the server**: `systemctl start matrix-goofys`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:69
+msgid "Sync the files again by re-running the `rsync` command you see in step #5"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:71
+msgid "Stop the S3 service by running this **on the server**: `systemctl stop matrix-goofys`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:73
+#: ../../../docs/configuring-playbook-s3-goofys.md:114
+msgid "Get the old media store out of the way by running this command on the server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:79
+msgid "Remove the `matrix_s3_media_store_path` configuration from your `vars.yml` file (undoing step #3 above)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:81
+#: ../../../docs/configuring-playbook-s3-goofys.md:122
+msgid "Run the playbook: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:83
+#: ../../../docs/configuring-playbook-s3-goofys.md:124
+msgid "You're done! Verify that loading existing (old) media files works and that you can upload new ones."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:85
+#: ../../../docs/configuring-playbook-s3-goofys.md:126
+msgid "When confident that it all works, get rid of the local media store directory: `rm -rf /matrix/synapse/storage/media-store-local-backup`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:87
+msgid "Migrating to Backblaze B2"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:89
+msgid "While all Matrix services are running, run the following command on the server:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:91
+msgid "(you need to adjust the 3 `--env` line below with your own data)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:104
+msgid "This is some initial file sync, which may take a very long time."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:108
+msgid "Run the command from step #1 again."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:110
+msgid "Doing this will sync any new files that may have been created locally in the meantime."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:112
+msgid "Now that Matrix services aren't running, we're sure to get Backblaze B2 and your local media store fully in sync."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3-goofys.md:120
+msgid "Put the [Backblaze B2 settings](configuring-playbook-s3.md#backblaze-b2) in your `vars.yml` file"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-s3.pot b/i18n/translation-templates/docs/configuring-playbook-s3.pot
new file mode 100644
index 000000000..9d2b4178e
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-s3.pot
@@ -0,0 +1,213 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-s3.md:1
+msgid "Storing Synapse media files on Amazon S3 or another compatible Object Storage (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:3
+msgid "By default, this playbook configures your server to store Synapse's content repository (`media_store`) files on the local filesystem. If that's okay, you can skip this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:5
+msgid "As an alternative to storing media files on the local filesystem, you can store them on [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object store."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:7
+msgid "You can do this either by sticking to Synapse's media repository and making that use S3 (read below for this method), or by switching to an external media storage implementation like [matrix-media-repo](configuring-playbook-matrix-media-repo.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:9
+msgid "First, [choose an Object Storage provider](#choosing-an-object-storage-provider)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:11
+msgid "Then, [create the S3 bucket](#bucket-creation-and-security-configuration)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:13
+msgid "Finally, [set up S3 storage for Synapse](#setting-up) (with [Goofys](configuring-playbook-s3-goofys.md), [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md), or use s3 datastore with the [matrix-media-repo](https://docs.t2bot.io/matrix-media-repo/configuration/s3-datastore.html))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:15
+msgid "Choosing an Object Storage provider"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:17
+msgid "You can create [Amazon S3](https://aws.amazon.com/s3/) or another S3-compatible object storage like [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html), [Storj](https://storj.io), [Wasabi](https://wasabi.com), [Digital Ocean Spaces](https://www.digitalocean.com/products/spaces), etc."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:19
+msgid "Amazon S3, Backblaze B2, and Storj are pay-as-you with no minimum charges for storing too little data."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:21
+msgid "All these providers have different prices, with Storj appearing to be the cheapest (as of 2024-10, storage fee is $0.004 per GB/month, and egress fee is $0.007 per GB). Backblaze egress is free, but for only certain users for up to 3x the amount of data stored. Beyond that you will pay $0.01/GB of egress."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:23
+msgid "Wasabi has a minimum charge of 1TB if you're storing less than 1TB, which becomes expensive if you need to store less data than that. Likewise, Digital Ocean Spaces has also a minimum charge of 250GB ($5/month as of 2022-10)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:25
+msgid "Here are some of the important aspects of choosing the right provider:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:27
+msgid "if a provider is a company you like and trust (or dislike less than the others)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:28
+msgid "if a provider implements end-to-end encryption of your data"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:29
+msgid "if a provider has a data region close to your Matrix server (if it's farther away, high latency may cause slowdowns)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:30
+msgid "if a provider's infrastructure such as data center is centralized or distributed"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:31
+msgid "if a provider's price model is transparent (whether it includes hidden costs like minimum charge, minimum storage term, etc.)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:32
+msgid "if a provider has free or cheap egress fee (in case you need to get the data out often, for some reason) - likely not too important for the common use-case"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:34
+msgid "Bucket creation and Security Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:36
+msgid "Now that you've [chosen an Object Storage provider](#choosing-an-object-storage-provider), you need to create a storage bucket."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:38
+msgid "How you do this varies from provider to provider, with Amazon S3 being the most complicated due to its vast number of services and complicated security policies."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:40
+msgid "Below, we provider some guides for common providers. If you don't see yours, look at the others for inspiration or read some guides online about how to create a bucket. Feel free to contribute to this documentation with an update!"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:42
+msgid "Amazon S3"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:44
+msgid "You'll need an Amazon S3 bucket and some IAM user credentials (access key + secret key) with full write access to the bucket. Example IAM security policy:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:65
+msgid "**Note**: This policy needs to be attached to an IAM user created from the **Security Credentials** menu. This is not a **Bucket Policy**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:67
+msgid "Backblaze B2"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:69
+msgid "To use [Backblaze B2](https://www.backblaze.com/b2/cloud-storage.html) you first need to sign up."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:71
+msgid "You [can't easily change which region (US, Europe) your Backblaze account stores files in](https://old.reddit.com/r/backblaze/comments/hi1v90/make_the_choice_for_the_b2_data_center_region/), so make sure to carefully choose the region when signing up (hint: it's a hard to see dropdown below the username/password fields in the signup form)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:73
+msgid "After logging in to Backblaze:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:75
+msgid "create a new **private** bucket through its user interface (you can call it something like `matrix-example-media-store`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:76
+msgid "note the **Endpoint** for your bucket (something like `s3.us-west-002.backblazeb2.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:77
+msgid "adjust its Lifecycle Rules to: Keep only the last version of the file"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:78
+msgid "go to [App Keys](https://secure.backblaze.com/app_keys.htm) and use the **Add a New Application Key** to create a new one"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:79
+msgid "restrict it to the previously created bucket (e.g. `matrix-example-media-store`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:80
+msgid "give it *Read & Write* access"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:82
+msgid "The `keyID` value is your **Access Key** and `applicationKey` is your **Secret Key**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:84
+msgid "For configuring [Goofys](configuring-playbook-s3-goofys.md) or [s3-synapse-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) you will need:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:86
+msgid "**Endpoint URL** - this is the  **Endpoint** value you saw above, but prefixed with `https://`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:88
+msgid "**Region** - use the value you see in the Endpoint (e.g. `us-west-002`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:90
+msgid "**Storage Class** - use `STANDARD`. Backblaze B2 does not have different storage classes, so it doesn't make sense to use any other value."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:92
+msgid "Other providers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:94
+msgid "For other S3-compatible providers, you may not need to configure security policies, etc. (just like for [Backblaze B2](#backblaze-b2))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:96
+msgid "You most likely just need to create an S3 bucket and get some credentials (access key and secret key) for accessing the bucket in a read/write manner."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:98
+msgid "Setting up"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:100
+msgid "To set up Synapse to store files in S3, follow the instructions for the method of your choice:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:102
+msgid "using [synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md) (recommended)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:103
+msgid "using [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-s3.md:104
+msgid "using [matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-shared-secret-auth.pot b/i18n/translation-templates/docs/configuring-playbook-shared-secret-auth.pot
new file mode 100644
index 000000000..126f05428
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-shared-secret-auth.pot
@@ -0,0 +1,61 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 09:53+0200\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-shared-secret-auth.md:1
+msgid "Setting up the Shared Secret Auth password provider module (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:3
+msgid "The playbook can install and configure [matrix-synapse-shared-secret-auth](https://github.com/devture/matrix-synapse-shared-secret-auth) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:5
+msgid "See the project's [documentation](https://github.com/devture/matrix-synapse-shared-secret-auth/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:7
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:9
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:18
+msgid "Authenticating only using a password provider"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:20
+msgid "If you wish for users to **authenticate only against configured password providers** (like this one), **without consulting Synapse's local database**, feel free to disable it:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:26
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:28
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:35
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-shared-secret-auth.md:37
+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 ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-sliding-sync-proxy.pot b/i18n/translation-templates/docs/configuring-playbook-sliding-sync-proxy.pot
new file mode 100644
index 000000000..a6693cf74
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-sliding-sync-proxy.pot
@@ -0,0 +1,113 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-sliding-sync-proxy.md:1
+msgid "Setting up the Sliding Sync proxy (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:3
+msgid "**Note**: The sliding-sync proxy is **not required** anymore as it's been replaced with a different method (called Simplified Sliding Sync) which is integrated into newer homeservers by default (**Conduit** homeserver from version `0.6.0` or **Synapse** from version `1.114`). This component and documentation remain here for historical purposes, but **installing this old sliding-sync proxy is generally not recommended anymore**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:5
+msgid "The playbook can install and configure [sliding-sync](https://github.com/matrix-org/sliding-sync) proxy for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:7
+msgid "Sliding Sync is an implementation of [MSC3575](https://github.com/matrix-org/matrix-spec-proposals/blob/kegan/sync-v3/proposals/3575-sync.md) and a prerequisite for running Element X clients ([Element X iOS](https://github.com/element-hq/element-x-ios) and [Element X Android](https://github.com/element-hq/element-x-android)). See the project's [documentation](https://github.com/matrix-org/sliding-sync) to learn more."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:11
+msgid "To enable Sliding Sync proxy, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:17
+msgid "Adjusting the Sliding Sync proxy URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:19
+msgid "By default, this playbook installs the Sliding Sync proxy on the `matrix.` subdomain, at the `/sliding-sync` path (https://matrix.example.com/sliding-sync). 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-sliding-sync-proxy.md:21
+msgid "By tweaking the `matrix_sliding_sync_hostname` and `matrix_sliding_sync_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-sliding-sync-proxy.md:23
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:31
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:33
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Honoroit domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:35
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:37
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:39
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:41
+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-sliding-sync-proxy.md:48
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:50
+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-sliding-sync-proxy.md:52
+msgid "External databases"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:54
+msgid "Please note that, if your setup utilizes an external database, you must also establish configuration for the sliding sync proxy. Alter the defaults below to suit your configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:64
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:66
+msgid "You **don't need to do anything special** to make use of the Sliding Sync proxy. Simply open your client which supports Sliding Sync (like Element X) and log in."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:68
+msgid "When the Sliding Sync proxy is [installed](#installing), your `/.well-known/matrix/client` file is also updated. A new `org.matrix.msc3575.proxy` section and `url` property are added there and made to point to your Sliding Sync proxy's base URL (e.g. `https://matrix.example.com/sliding-sync`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sliding-sync-proxy.md:70
+msgid "This allows clients which support Sliding Sync to detect the Sliding Sync proxy's URL and make use of it."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-ssl-certificates.pot b/i18n/translation-templates/docs/configuring-playbook-ssl-certificates.pot
new file mode 100644
index 000000000..3a34a243f
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-ssl-certificates.pot
@@ -0,0 +1,118 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-ssl-certificates.md:1
+msgid "Adjusting SSL certificate retrieval (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:3
+msgid "By default, this playbook retrieves and auto-renews free SSL certificates from [Let's Encrypt](https://letsencrypt.org/) for the domains it needs (e.g. `matrix.example.com` and others)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:5
+msgid "This guide is about using the integrated Traefik server and doesn't apply if you're using [your own webserver](configuring-playbook-own-webserver.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:7
+msgid "Using staging Let's Encrypt certificates instead of real ones"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:9
+msgid "For testing purposes, you may wish to use staging certificates provide by Let's Encrypt."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:11
+#: ../../../docs/configuring-playbook-ssl-certificates.md:21
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:17
+msgid "Disabling SSL termination"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:19
+msgid "For testing or other purposes, you may wish to install services without SSL termination and have services exposed to `http://` instead of `https://`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:27
+msgid "Using self-signed SSL certificates"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:29
+msgid "If you'd like to use your own SSL certificates, instead of the default (SSL certificates obtained automatically via [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) from [Let's Encrypt](https://letsencrypt.org/)):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:31
+msgid "generate your self-signed certificate files"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:32
+msgid "follow the [Using your own SSL certificates](#using-your-own-ssl-certificates) documentation below"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:34
+msgid "Using your own SSL certificates"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:36
+msgid "To use your own SSL certificates with Traefik, you need to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:38
+msgid "disable [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) / [Let's Encrypt](https://letsencrypt.org/) support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:39
+msgid "put a custom Traefik configuration file on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:40
+msgid "register your custom configuration file with Traefik, by adding an extra provider of type [file](https://doc.traefik.io/traefik/providers/file/)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:41
+msgid "put the SSL files on the server, with the help of this Ansible playbook (via the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux)) or manually"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:89
+msgid "Using a DNS-01 ACME challenge type, instead of HTTP-01"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:91
+msgid "You can configure Traefik to use the [DNS-01 challenge type](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) for Let's Encrypt. This is less commonly used than the default [HTTP-01 challenge type](https://letsencrypt.org/docs/challenge-types/#http-01-challenge), but it can be helpful to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:93
+msgid "hide your public IP from Let's Encrypt logs"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:94
+msgid "allow you to obtain SSL certificates for servers which are not accessible (via HTTP) from the public internet (and for which the HTTP-01 challenge would fail)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:96
+msgid "This is an example for how to edit the `vars.yml` file if you're using Cloudflare:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:111
+msgid "Make sure to change the value of \"provider\" to your particular DNS solution, and provide the appropriate environment variables. The full list of supported providers is available [here](https://doc.traefik.io/traefik/https/acme/#providers)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ssl-certificates.md:113
+msgid "This example assumes you're using Cloudflare to manage your DNS zone. Note that it requires the use of two tokens: one for reading all zones (`CF_ZONE_API_TOKEN`) and another that must be able to edit the particular domain you're using (`CF_DNS_API_TOKEN`). For security, it's recommended that you create two fine-grained tokens for this purpose, but you might choose to use the same token for both."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-sygnal.pot b/i18n/translation-templates/docs/configuring-playbook-sygnal.pot
new file mode 100644
index 000000000..e61b6a508
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-sygnal.pot
@@ -0,0 +1,129 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 09:53+0200\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-sygnal.md:1
+msgid "Setting up the Sygnal push gateway (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:3
+msgid "The playbook can install and configure the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:5
+msgid "See the project's [documentation](https://github.com/matrix-org/sygnal/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:7
+msgid "**Note**: most people don't need to install their own gateway. As Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) documentation says:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:9
+msgid "It is not feasible to allow end-users to configure their own Sygnal instance, because the Sygnal instance needs the appropriate FCM or APNs secrets that belong to the application."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:11
+msgid "This optional playbook component is only useful to people who develop/build their own Matrix client applications themselves."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:13
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:15
+msgid "To enable Sygnal, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:43
+msgid "For a more complete example of available fields and values they can take, see `roles/custom/matrix-sygnal/templates/sygnal.yaml.j2` (or the [upstream `sygnal.yaml.sample` configuration file](https://github.com/matrix-org/sygnal/blob/master/sygnal.yaml.sample))."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:45
+msgid "Configuring [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/) is easier, as it only requires that you provide some config values."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:47
+msgid "To configure [APNS](https://developer.apple.com/notifications/) (Apple Push Notification Service), you'd need to provide one or more certificate files. To do that, the above example configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:49
+msgid "makes use of the [`aux` role](https://github.com/mother-of-all-self-hosting/ansible-role-aux) (and its `aux_file_definitions` variable) to make the playbook install files into `/matrix/sygnal/data` (the `matrix_sygnal_data_path` variable). See [`defaults/main.yml` file](https://github.com/mother-of-all-self-hosting/ansible-role-aux/blob/main/defaults/main.yml) of the `aux` role for usage examples. It also makes sure the files are owned by `matrix:matrix`, so that Sygnal can read them. Of course, you can also install these files manually yourself, if you'd rather not use `aux`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:51
+msgid "references these files in the Sygnal configuration (`matrix_sygnal_apps`) using a path like `/data/..` (the `/matrix/sygnal/data` directory on the host system is mounted into the `/data` directory inside the container)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:53
+msgid "Adjusting the Sygnal URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:55
+msgid "By default, this playbook installs Sygnal on the `sygnal.` subdomain (`sygnal.example.com`) and requires you to [adjust your DNS records](#adjusting-dns-records)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:57
+msgid "By tweaking the `matrix_sygnal_hostname` and `matrix_sygnal_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-sygnal.md:59
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:70
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:72
+msgid "Once you've decided on the domain and path, **you may need to adjust your DNS** records to point the Sygnal domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:74
+msgid "By default, you will need to create a CNAME record for `sygnal`. See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:76
+msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:78
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:80
+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-sygnal.md:87
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:89
+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-sygnal.md:91
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:93
+msgid "To make use of your Sygnal installation, you'd need to build your own Matrix client application, which uses the same API keys (for [GCM/FCM](https://firebase.google.com/docs/cloud-messaging/)) and certificates (for [APNS](https://developer.apple.com/notifications/)) and is to your Sygnal URL endpoint (e.g. `https://sygnal.example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-sygnal.md:95
+msgid "Refer to Sygnal's [Notes for application developers](https://github.com/matrix-org/sygnal/blob/master/docs/applications.md) document."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-admin.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-admin.pot
new file mode 100644
index 000000000..e93e9cce0
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-synapse-admin.pot
@@ -0,0 +1,121 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-synapse-admin.md:1
+msgid "Setting up Synapse Admin (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:3
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:5
+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://matrix-org.github.io/dendrite/administration/adminapi) differs from [Synapse Admin API](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:7
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:11
+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:17
+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:19
+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:20
+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:22
+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:24
+msgid "⚠️ **Warning**: If you're using [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS) for authentication, you will be able to [log into synapse-admin with an access token](https://github.com/etkecc/synapse-admin/pull/58), but certain synapse-admin features (especially those around user management) will be limited or not work at all."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:26
+msgid "Adjusting the Synapse Admin URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:28
+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:30
+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:32
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:40
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:42
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the Synapse Admin domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:44
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:46
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:48
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:50
+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:57
+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:59
+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:61
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:63
+msgid "After installation, Synapse Admin will be accessible at: `https://matrix.example.com/synapse-admin/`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-admin.md:65
+msgid "To use Synapse Admin, you need to have [registered at least one administrator account](registering-users.md) on your server."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-auto-accept-invite.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-auto-accept-invite.pot
new file mode 100644
index 000000000..7b6295506
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-synapse-auto-accept-invite.pot
@@ -0,0 +1,69 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 09:53+0200\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-synapse-auto-accept-invite.md:1
+msgid "Setting up Synapse Auto Invite Accept (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:3
+msgid "The playbook can install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:5
+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:7
+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:9
+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:11
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:13
+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:21
+msgid "Synapse worker deployments"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:23
+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:29
+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:31
+msgid "Native alternative"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-accept-invite.md:33
+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:35
+msgid "Here's example configuration for using the **native** Synapse feature:"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-auto-compressor.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-auto-compressor.pot
new file mode 100644
index 000000000..389cc1136
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-synapse-auto-compressor.pot
@@ -0,0 +1,73 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 09:53+0200\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-synapse-auto-compressor.md:1
+msgid "Setting up synapse-auto-compressor (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:3
+msgid "The playbook can install and configure [synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:5
+msgid "It's a CLI tool that automatically compresses Synapse's `state_groups` database table in the background."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:7
+msgid "See the project's [documentation](https://github.com/matrix-org/rust-synapse-compress-state/blob/master/README.md#automated-tool-synapse_auto_compressor) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:11
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:17
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:19
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:26
+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-auto-compressor.md:28
+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-auto-compressor.md:30
+msgid "Usage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:32
+msgid "After installation, `synapse_auto_compressor` will run automatically every day at `00:00:00` (as defined in `matrix_synapse_auto_compressor_calendar` by default)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:34
+msgid "Manually start the tool"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-auto-compressor.md:36
+msgid "For testing your setup it can be helpful to not wait until 00:00. If you want to run the tool immediately, log onto the server and run `systemctl start matrix-synapse-auto-compressor`. Running this command will not return control to your terminal until the compression run is done, which may take a long time. Consider using [tmux](https://en.wikipedia.org/wiki/Tmux) if your SSH connection is unstable."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-s3-storage-provider.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-s3-storage-provider.pot
new file mode 100644
index 000000000..9bcc08ffd
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-synapse-s3-storage-provider.pot
@@ -0,0 +1,253 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-synapse-s3-storage-provider.md:1
+msgid "Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:3
+msgid "If you'd like to store Synapse's content repository (`media_store`) files on Amazon S3 (or other S3-compatible service), you can use the [synapse-s3-storage-provider](https://github.com/matrix-org/synapse-s3-storage-provider) media provider module for Synapse."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:5
+msgid "An alternative (which has worse performance) is to use [Goofys to mount the S3 store to the local filesystem](configuring-playbook-s3-goofys.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:7
+msgid "How it works?"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:9
+msgid "Summarized writings here are inspired by [this article](https://quentin.dufour.io/blog/2021-09-14/matrix-synapse-s3-storage/)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:11
+msgid "The way media storage providers in Synapse work has some caveats:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:13
+msgid "Synapse still continues to use locally-stored files (for creating thumbnails, serving files, etc)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:14
+msgid "the media storage provider is just an extra storage mechanism (in addition to the local filesystem)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:15
+msgid "all files are stored locally at first, and then copied to the media storage provider (either synchronously or asynchronously)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:16
+msgid "if a file is not available on the local filesystem, it's pulled from a media storage provider"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:18
+msgid "You may be thinking **if all files are stored locally as well, what's the point**?"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:20
+msgid "You can run some scripts to delete the local files once in a while (which we do automatically by default - see [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem)), thus freeing up local disk space. If these files are needed in the future (for serving them to users, etc.), Synapse will pull them from the media storage provider on demand."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:22
+msgid "While you will need some local disk space around, it's only to accommodate usage, etc., and won't grow as large as your S3 store."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:24
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:26
+msgid "After [creating the S3 bucket and configuring it](configuring-playbook-s3.md#bucket-creation-and-security-configuration), you can proceed to configure `s3-storage-provider` in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:50
+msgid "If you have existing files in Synapse's media repository (`/matrix/synapse/media-store/..`):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:52
+msgid "new files will start being stored both locally and on the S3 store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:53
+msgid "the existing files will remain on the local filesystem only until [migrating them to the S3 store](#migrating-your-existing-media-files-to-the-s3-store)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:54
+msgid "at some point (and periodically in the future), you can delete local files which have been uploaded to the S3 store already"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:56
+msgid "Regardless of whether you need to [Migrate your existing files to the S3 store](#migrating-your-existing-media-files-to-the-s3-store) or not, make sure you've familiarized yourself with [How it works?](#how-it-works) above and [Periodically cleaning up the local filesystem](#periodically-cleaning-up-the-local-filesystem) below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:58
+msgid "Migrating your existing media files to the S3 store"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:60
+msgid "Migrating your existing data can happen in multiple ways:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:62
+msgid "[using the `s3_media_upload` script from `synapse-s3-storage-provider`](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (very slow when dealing with lots of data)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:63
+msgid "[using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload) (quicker when dealing with lots of data)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:65
+msgid "Using the `s3_media_upload` script from `synapse-s3-storage-provider`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:67
+msgid "Instead of using `s3_media_upload` directly, which is very slow and painful for an initial data migration, we recommend [using another tool in combination with `s3_media_upload`](#using-another-tool-in-combination-with-s3_media_upload)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:69
+msgid "To copy your existing files, SSH into the server and run `/matrix/synapse/ext/s3-storage-provider/bin/shell`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:71
+msgid "This launches a Synapse container, which has access to the local media store, Postgres database, S3 store and has some convenient environment variables configured for you to use (`MEDIA_PATH`, `BUCKET`, `ENDPOINT`, `UPDATE_DB_DAYS`, etc)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:73
+msgid "Then use the following commands (`$` values come from environment variables - they're **not placeholders** that you need to substitute):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:75
+msgid "`s3_media_upload update-db $UPDATE_DB_DURATION` - create a local SQLite database (`cache.db`) with a list of media repository files (from the `synapse` Postgres database) eligible for operating on"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:76
+msgid "`$UPDATE_DB_DURATION` is influenced by the `matrix_synapse_ext_synapse_s3_storage_provider_update_db_day_count` variable (defaults to `0`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:77
+msgid "`$UPDATE_DB_DURATION` defaults to `0d` (0 days), which means **include files which haven't been accessed for more than 0 days** (that is, **all files will be included**)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:78
+msgid "`s3_media_upload check-deleted $MEDIA_PATH` - check whether files in the local cache still exist in the local media repository directory"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:79
+msgid "`s3_media_upload upload $MEDIA_PATH $BUCKET --delete --storage-class $STORAGE_CLASS --endpoint-url $ENDPOINT` - uploads locally-stored files to S3 and deletes them from the local media repository directory"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:81
+msgid "The `s3_media_upload upload` command may take a lot of time to complete."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:83
+msgid "Instead of running the above commands manually in the shell, you can also run the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script which will run the same commands automatically. We demonstrate how to do it manually, because:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:85
+msgid "it's what the upstream project demonstrates and it teaches you how to use the `s3_media_upload` tool"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:86
+msgid "allows you to check and verify the output of each command, to catch mistakes"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:87
+msgid "includes progress bars and detailed output for each command"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:88
+msgid "allows you to easily interrupt slow-running commands, etc. (the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` starts a container without interactive TTY support, so `Ctrl+C` may not work and you and require killing via `docker kill ..`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:90
+msgid "Using another tool in combination with `s3_media_upload`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:92
+msgid "To migrate your existing local data to S3, we recommend to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:94
+msgid "**first** use another tool ([`aws s3`](#copying-data-to-amazon-s3) or [`b2 sync`](#copying-data-to-backblaze-b2), etc.) to copy the local files to the S3 bucket"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:96
+msgid "**only then** [use the `s3_media_upload` tool to finish the migration](#using-the-s3_media_upload-script-from-synapse-s3-storage-provider) (this checks to ensure all files are uploaded and then deletes the local files)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:98
+msgid "Copying data to Amazon S3"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:100
+msgid "To copy to AWS S3, start a container on the Matrix server like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:112
+msgid "Copying data to an S3 alternative using the aws-s3 tool"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:114
+msgid "To copy to a provider other than AWS S3 (e.g. Wasabi, Digital Ocean Spaces, etc.), you can use the command for [Copying data to Amazon S3](#copying-data-to-amazon-s3) with an added `--endpoint-url=$ENDPOINT` argument."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:116
+msgid "Add this argument to the command **as-is** (`$ENDPOINT` is an environment variable corresponding to `matrix_synapse_ext_synapse_s3_storage_provider_config_endpoint_url`, so you don't need to touch it). Make sure to add the argument **before** the final quote (`'`) of the command."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:118
+msgid "Copying data to Backblaze B2"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:120
+msgid "You can copy files to Backblaze B2 either by following the [Copying data to an S3 alternative using the aws-s3 tool](#copying-data-to-an-s3-alternative-using-the-aws-s3-tool) or by using the B2-specific [b2 command-line tool](https://www.backblaze.com/b2/docs/quick_command_line.html) as described below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:122
+msgid "To copy the data using the `b2` tool, start a container on the Matrix server like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:136
+msgid "Periodically cleaning up the local filesystem"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:138
+msgid "As described in [How it works?](#how-it-works) above, when new media is uploaded to the Synapse homeserver, it's first stored locally and then also stored on the remote S3 storage."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:140
+msgid "By default, we periodically ensure that all local files are uploaded to S3 and are then removed from the local filesystem. This is done automatically using:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:142
+msgid "the `/matrix/synapse/ext/s3-storage-provider/bin/migrate` script"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:143
+msgid ".. invoked via the `matrix-synapse-s3-storage-provider-migrate.service` service"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:144
+msgid ".. triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` timer, every day at 05:00"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-s3-storage-provider.md:146
+msgid "So.. you don't need to perform any maintenance yourself."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-simple-antispam.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-simple-antispam.pot
new file mode 100644
index 000000000..aea18ce59
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-synapse-simple-antispam.pot
@@ -0,0 +1,41 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 09:53+0200\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-synapse-simple-antispam.md:1
+msgid "Setting up Synapse Simple Antispam (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:3
+msgid "The playbook can install and configure [synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispam) for you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:5
+msgid "It lets you fight invite-spam by automatically blocking invitiations from a list of servers specified by you (blacklisting)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:7
+msgid "See the project's [documentation](https://github.com/t2bot/synapse-simple-antispam/blob/master/README.md) to learn what it does and why it might be useful to you."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:9
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-simple-antispam.md:11
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your needs):"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse-usage-exporter.pot b/i18n/translation-templates/docs/configuring-playbook-synapse-usage-exporter.pot
new file mode 100644
index 000000000..18bb463a6
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-synapse-usage-exporter.pot
@@ -0,0 +1,105 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-synapse-usage-exporter.md:1
+msgid "Enabling synapse-usage-exporter for Synapse usage statistics (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:3
+msgid "[synapse-usage-exporter](https://github.com/loelkes/synapse-usage-exporter) allows you to export the usage statistics of a Synapse homeserver to this container service and for the collected metrics to later be scraped by Prometheus."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:5
+msgid "Synapse does not include usage statistics in its Prometheus metrics. They can be reported to an HTTP `PUT` endpoint 5 minutes after startup and from then on at a fixed interval of once every three hours. This role integrates a simple [Flask](https://flask.palletsprojects.com) project that offers an HTTP `PUT` endpoint and holds the most recent received record available to be scraped by Prometheus."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:7
+msgid "Enabling this service will automatically:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:9
+msgid "install the synapse-usage-exporter service"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:10
+msgid "re-configure Synapse to push (via HTTP `PUT`) usage statistics information to synapse-usage-exporter"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:11
+msgid "re-configure [Prometheus](./configuring-playbook-prometheus-grafana.md) (if Prometheus is enabled), to periodically scrape metrics from synapse-usage-exporter"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:12
+msgid "add a new [Grafana](./configuring-playbook-prometheus-grafana.md) dashboard (if Grafana is enabled) containing Synapse usage statistics"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:14
+msgid "Adjusting the playbook configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:16
+msgid "To enable synapse-usage-exporter, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:28
+msgid "Adjusting the synapse-usage-exporter URL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:30
+msgid "By default, this playbook installs synapse-usage-exporter on the `matrix.` subdomain, at the `/report-usage-stats/push` path (https://matrix.example.com/report-usage-stats/push). 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-usage-exporter.md:32
+msgid "By tweaking the `matrix_synapse_usage_exporter_hostname` and `matrix_synapse_usage_exporter_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-usage-exporter.md:34
+msgid "Example additional configuration for your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:43
+msgid "Adjusting DNS records"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:45
+msgid "If you've changed the default hostname, **you may need to adjust your DNS** records to point the synapse-usage-exporter domain to the Matrix server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:47
+msgid "See [Configuring DNS](configuring-dns.md) for details about DNS changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:49
+msgid "If you've decided to use the default hostname, you won't need to do any extra DNS configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:51
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse-usage-exporter.md:53
+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-usage-exporter.md:60
+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-usage-exporter.md:62
+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 ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-synapse.pot b/i18n/translation-templates/docs/configuring-playbook-synapse.pot
new file mode 100644
index 000000000..3f6dd4aae
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-synapse.pot
@@ -0,0 +1,253 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-synapse.md:1
+msgid "Configuring Synapse (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:3
+msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, so that it works for the general case. If that's okay, you can skip this document."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:5
+msgid "The playbook provides lots of customization variables you could use to change Synapse's settings."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:7
+msgid "Their defaults are defined in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml) and they ultimately end up in the generated `/matrix/synapse/config/homeserver.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2`](../roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2) template."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:9
+msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:11
+msgid "Alternatively, **if there is no pre-defined variable** for a Synapse setting you wish to change:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:13
+msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Synapse's various settings that rarely get used."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:15
+msgid "or, you can **extend and override the default configuration** ([`homeserver.yaml.j2`](../roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2)) by making use of the `matrix_synapse_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:17
+msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_synapse_configuration` (or `matrix_synapse_configuration_yaml`). You can find information about this in [`roles/custom/matrix-synapse/defaults/main.yml`](../roles/custom/matrix-synapse/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:19
+msgid "Load balancing with workers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:21
+msgid "To have Synapse gracefully handle thousands of users, worker support should be enabled. It factors out some homeserver tasks and spreads the load of incoming client and server-to-server traffic between multiple processes. More information can be found in the [official Synapse workers documentation](https://github.com/element-hq/synapse/blob/master/docs/workers.md) and [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:23
+msgid "To enable Synapse worker support, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:31
+msgid "By default, this enables the `one-of-each` [worker preset](#worker-presets), but you may wish to use another preset or [control the number of worker instances](#controlling-the-number-of-worker-instances)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:33
+msgid "Worker presets"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:35
+msgid "We support a few configuration presets (`matrix_synapse_workers_preset: one-of-each` being the default configuration right now):"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:37
+msgid "(federation-only) `little-federation-helper` - a very minimal worker configuration to improve federation performance"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:38
+msgid "(generic) `one-of-each` - defaults to one worker of each supported type - no smart routing, just generic workers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:39
+msgid "(specialized) `specialized-workers` - defaults to one worker of each supported type, but disables generic workers and uses [specialized workers](#specialized-workers) instead"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:41
+msgid "These presets represent a few common configurations. There are many worker types which can be mixed and matched based on your needs."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:43
+msgid "Generic workers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:45
+msgid "Previously, the playbook only supported the most basic type of load-balancing. We call it **generic load-balancing** below, because incoming HTTP requests are sent to a generic worker. Load-balancing was done based on the requestor's IP address. This is simple, but not necessarily optimal. If you're accessing your account from multiple IP addresses (e.g. your mobile phone being on a different network than your PC), these separate requests may potentially be routed to different workers, each of which would need to cache roughly the same data."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:47
+msgid "This is **still the default load-balancing method (preset) used by the playbook**."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:49
+msgid "To use generic load-balancing, do not specify `matrix_synapse_workers_preset` to make it use the default value (`one-of-each`), or better yet - explicitly set it as `one-of-each`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:51
+msgid "You may also consider [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:53
+msgid "Specialized workers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:55
+msgid "The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requestor's IP adddress, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** - the access token (username) of the requestor and/or on the resource (room, etc.) being requested."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:57
+msgid "The playbook supports these **4 types** of specialized workers:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:59
+msgid "Room workers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) & [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs dedicated to handling specific rooms"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:60
+msgid "Sync workers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to synchronization (most notably [the `/sync` endpoint](https://spec.matrix.org/v1.9/client-server-api/#get_matrixclientv3sync))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:61
+msgid "Client readers - handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are not for specific rooms (handled by **room workers**) or for synchronization (handled by **sync workers**)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:62
+msgid "Federation readers - handles various [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which are not for specific rooms (handled by **room workers**)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:64
+msgid "To use specialized load-balancing, consider enabling the `specialized-workers` [worker preset](#worker-presets) and potentially [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:66
+msgid "Controlling the number of worker instances"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:68
+msgid "If you'd like more customization power, you can start with one of the [worker presets](#worker-presets) and then tweak various `matrix_synapse_workers_*_count` variables manually."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:70
+msgid "To find what variables are available for you to override in your own `vars.yml` configuration file, see the [`defaults/main.yml` file for the `matrix-synapse` Ansible role](../roles/custom/matrix-synapse/defaults/main.yml)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:72
+msgid "The only thing you **cannot** do is mix [generic workers](#generic-workers) and [specialized workers](#specialized-workers)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:74
+msgid "Effect of enabling workers on the rest of your server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:76
+msgid "When Synapse workers are enabled, the integrated [Postgres database is tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum number of Postgres connections are increased from `200` to `500`. If you need to decrease or increase the number of maximum Postgres connections further, use the `postgres_max_connections` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:78
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:80
+msgid "In case any problems occur, make sure to have a look at the [list of synapse issues about workers](https://github.com/element-hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit 'matrix-*'`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:82
+msgid "Synapse Admin"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:84
+msgid "Certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace, if you install [Synapse Admin](configuring-playbook-synapse-admin.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:86
+msgid "Synapse + OpenID Connect for Single-Sign-On"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:88
+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:90
+msgid "If you'd like to use OpenID Connect authentication with Synapse, you'll need some additional configuration."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:92
+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:94
+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:96
+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:117
+msgid "Customizing templates"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:119
+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:121
+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:123
+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:125
+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:127
+msgid "To enable template customizations, use a configuration (`inventory/host_vars/matrix.example.com/vars.yml`) like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:153
+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:155
+msgid "Monitoring Synapse Metrics with Prometheus and Grafana"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:157
+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:159
+msgid "To enable Synapse runtime metrics see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-synapse.md:161
+msgid "To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-telemetry.pot b/i18n/translation-templates/docs/configuring-playbook-telemetry.pot
new file mode 100644
index 000000000..e9ada53e7
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-telemetry.pot
@@ -0,0 +1,49 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-telemetry.md:1
+msgid "Enabling Telemetry for your Matrix server (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:3
+msgid "By default, this playbook configures your Matrix homeserver to not send any telemetry data anywhere."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:5
+msgid "The [matrix.org](https://matrix.org) team would really appreciate it if you could help the project out by reporting usage statistics from your homeserver. Enabling usage statistics helps track the growth of the Matrix community, and helps to make Matrix a success."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:7
+msgid "Enabling Telemetry"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:9
+msgid "If you'd like to **help by enabling submission of general usage statistics** for your homeserver, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:17
+msgid "Usage statistics being submitted"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:19
+msgid "When enabled, your homeserver will regularly upload a few dozen statistics about your server. This data includes your homeserver's domain, the total number of users, the number of active users, the total number of rooms, and the number of messages sent per day on your homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-telemetry.md:21
+msgid "See [Synapse's documentation](https://github.com/element-hq/synapse/blob/develop/docs/usage/administration/monitoring/reporting_homeserver_usage_statistics.md#available-statistics) or [Dendrite's documentation](https://github.com/matrix-org/dendrite/blob/main/docs/FAQ.md#what-is-being-reported-when-enabling-phone-home-statistics) for the full list of statistics that are reported."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-traefik.pot b/i18n/translation-templates/docs/configuring-playbook-traefik.pot
new file mode 100644
index 000000000..e8324e3e6
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-traefik.pot
@@ -0,0 +1,134 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-traefik.md:1
+msgid "Configuring the Traefik reverse-proxy (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:3
+msgid "By default, this playbook installs and manages a [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server, powered by the [ansible-role-traefik](https://github.com/mother-of-all-self-hosting/ansible-role-traefik) Ansible role."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:5
+msgid "This Ansible role support various configuration options. Feel free to consult its `default/main.yml` variables file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:7
+msgid "Adjusting SSL certificate retrieval"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:9
+msgid "See the dedicated [Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) documentation page."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:11
+msgid "Increase logging verbosity"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:17
+msgid "Disable access logs"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:19
+msgid "This will disable access logging."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:25
+msgid "Enable Traefik Dashboard"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:27
+msgid "This will enable a Traefik [Dashboard](https://doc.traefik.io/traefik/operations/dashboard/) UI at `https://matrix.example.com/dashboard/` (note the trailing `/`)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:37
+msgid "**WARNING**: Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:39
+msgid "Additional configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:41
+msgid "Use the `traefik_configuration_extension_yaml` variable provided by the Traefik Ansible role to override or inject additional settings, even when no dedicated variable exists."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:51
+msgid "Reverse-proxying another service behind Traefik"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:53
+msgid "The preferred way to reverse-proxy additional services behind Traefik would be to start the service as another container, configure the container with the corresponding Traefik [container labels](https://docs.docker.com/config/labels-custom-metadata/) (see [Traefik & Docker](https://doc.traefik.io/traefik/routing/providers/docker/)), and connect the service to the `traefik` network. Some services are also already available via the compatible [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook), but take a look at the minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:55
+msgid "However, if your service does not run on a container or runs on another machine, the following configuration might be what you are looking for."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:57
+msgid "Reverse-proxying a remote HTTP/HTTPS service behind Traefik"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:59
+msgid "If you want to host another webserver would be reachable via `my-fancy-website.example.net` from the internet and via `https://<internal webserver IP address>:<internal port>` from inside your network, you can make the playbook's integrated Traefik instance reverse-proxy the traffic to the correct host."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:61
+msgid "Prerequisites: DNS and routing for the domain `my-fancy-website.example.net` need to be set up correctly. In this case, you'd be pointing the domain name to your Matrix server - `my-fancy-website.example.net` would be a CNAME going to `matrix.example.com`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:63
+msgid "First, we have to adjust the static configuration of Traefik, so that we can add additional configuration files:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:77
+msgid "If you are using a self-signed certificate on your webserver, you can tell Traefik to trust your own backend servers by adding more configuration to the static configuration file. If you do so, bear in mind the security implications of disabling the certificate validity checks towards your back end."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:91
+msgid "Next, you have to add a new dynamic configuration file for Traefik that contains the actual information of the server using the `aux_file_definitions` variable. In this example, we will terminate SSL at the Traefik instance and connect to the other server via HTTPS. Traefik will now take care of managing the certificates."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:110
+#: ../../../docs/configuring-playbook-traefik.md:133
+msgid "Changing the `url` to one with an `http://` prefix would allow to connect to the server via HTTP."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:112
+msgid "Reverse-proxying another service behind Traefik without terminating SSL"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:114
+msgid "If you do not want to terminate SSL at the Traefik instance (for example, because you're already terminating SSL at other webserver), you need to adjust the static configuration in the same way as in the previous chapter in order to be able to add our own dynamic configuration files. Afterwards, you can add the following configuration to your `vars.yml` configuration file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:135
+msgid "With these changes, all TCP traffic will be reverse-proxied to the target system."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:137
+msgid "**WARNING**: This configuration might lead to problems or need additional steps when a [certbot](https://certbot.eff.org/) behind Traefik also tries to manage [Let's Encrypt](https://letsencrypt.org/) certificates, as Traefik captures all traffic to ```PathPrefix(`/.well-known/acme-challenge/`)```."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:139
+msgid "Traefik behind a `proxy_protocol` reverse-proxy"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-traefik.md:141
+msgid "If you run a reverse-proxy which speaks `proxy_protocol`, add the following to your configuration file:"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-turn.pot b/i18n/translation-templates/docs/configuring-playbook-turn.pot
new file mode 100644
index 000000000..624bf85e0
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-turn.pot
@@ -0,0 +1,105 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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-turn.md:1
+msgid "Adjusting TURN server configuration (optional, advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:3
+msgid "The playbook installs a [Coturn](https://github.com/coturn/coturn) TURN server by default, so that clients can make audio/video calls even from [NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed networks."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:5
+msgid "By default, the Synapse chat server is configured, so that it points to the Coturn TURN server installed by the playbook."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:7
+msgid "Disabling Coturn"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:9
+msgid "If, for some reason, you'd like to prevent the playbook from installing Coturn, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:15
+msgid "In that case, Synapse would not point to any Coturn servers and audio/video call functionality may fail."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:17
+msgid "Manually defining your public IP"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:19
+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."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:21
+msgid "If you'd rather use a local IP for `ansible_host`, make sure to set up `matrix_coturn_turn_external_ip_address` replacing `YOUR_PUBLIC_IP` with the pubic IP used by the server."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:27
+msgid "If you'd like to rely on external IP address auto-detection (not recommended unless you need it), set `matrix_coturn_turn_external_ip_address` to an empty value. 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 `matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:29
+msgid "If your server has multiple external IP addresses, the Coturn role offers a different variable for specifying them:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:36
+msgid "Changing the authentication mechanism"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:38
+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:40
+msgid "To do so, add this override to your configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:46
+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:48
+msgid "If you're using [Jitsi](./configuring-playbook-jitsi.md), note that switching to `lt-cred-mech` will remove the integration between Jitsi and your own Coturn server, because Jitsi only seems to support the `auth-secret` authentication method."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:50
+msgid "Using your own external Coturn server"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:52
+msgid "If you'd like to use another TURN server (be it Coturn or some other one), you can configure the playbook like this:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:66
+msgid "If you have or want to enable [Jitsi](configuring-playbook-jitsi.md), 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:72
+msgid "You can put multiple host/port combinations if you like."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:74
+msgid "Further variables and configuration options"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-turn.md:75
+msgid "To see all the available configuration options, check roles/custom/matrix-coturn/defaults/main.yml"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook-user-verification-service.pot b/i18n/translation-templates/docs/configuring-playbook-user-verification-service.pot
new file mode 100644
index 000000000..04afcda54
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook-user-verification-service.pot
@@ -0,0 +1,213 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-user-verification-service.md:1
+msgid "Setting up Matrix User Verification Service (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:3
+msgid "**[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (hereafter: UVS) can only be installed after Matrix services are installed and running.** If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) flow and come back here later."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:5
+msgid "Currently, the main purpose of this role is to allow Jitsi to authenticate Matrix users and check if they are authorized to join a conference. Please refer to the documentation of the [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) to understand how it works."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:7
+msgid "**Note**: enabling Matrix User Verification Service, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:9
+msgid "If the Jitsi server is also configured by this playbook, all plugging of variables and secrets is handled in `group_vars/matrix_servers`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:11
+msgid "__Some general concepts of UVS may be helpful to understand the rest, so here they are:__"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:13
+msgid "UVS can be used to verify two claims:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:15
+msgid "(A) Whether a given OpenID token is valid for a given server and"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:16
+msgid "(B) whether a user is member of a given room and the corresponding PowerLevel"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:18
+msgid "Verifying an OpenID token ID done by finding the corresponding Homeserver via  '.well-known/matrix/server' for the given domain. The configured `matrix_user_verification_service_uvs_homeserver_url` does **not** factor into this. By default, this playbook only checks against `matrix_server_fqn_matrix`. Therefore, the request will be made against the public openid API for `matrix_server_fqn_matrix`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:20
+msgid "Verifying RoomMembership and PowerLevel is done against `matrix_user_verification_service_uvs_homeserver_url` which is by default done via the docker network. UVS will verify the validity of the token beforehand though."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:22
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:24
+msgid "In order to use UVS, an admin token for the configured homeserver must be supplied. For now this means configuring Synapse and creating the token before installing UVS."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:26
+msgid "Enable"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:28
+msgid "To enable Matrix User Verification Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:34
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:36
+msgid "The only required configuration variable is `matrix_user_verification_service_uvs_access_token` (see below)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:38
+msgid "For a list of all configuration options see the role defaults [`roles/matrix-user-verification-service/defaults/main.yml`](../roles/custom/matrix-user-verification-service/defaults/main.yml). But be aware of all the plugging happening in `group_vars/matrix_servers`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:40
+msgid "In the default configuration, the UVS Server is only reachable via the docker network, which is fine if e.g. Jitsi is also running in a container on the host. However, it is possible to expose UVS via setting `matrix_user_verification_service_container_http_host_bind_port`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:42
+msgid "Obtain an access token"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:44
+msgid "The Synapse Access Token is used to verify RoomMembership and PowerLevel against `matrix_user_verification_service_uvs_homeserver_url`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:46
+msgid "We recommend that you create a dedicated Matrix user for uvs (`uvs` is a good username). Follow our [Registering users](registering-users.md) guide to register a user with administration privileges."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:48
+msgid "You are required to specify an access token (belonging to this new user) for UVS to work. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:50
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:56
+msgid "Custom Auth Token (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:58
+msgid "It is possible to set an API Auth Token to restrict access to the UVS. If this is enabled, anyone making a request to UVS must provide it via the header \"Authorization: Bearer TOKEN\""
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:60
+msgid "By default, the token will be derived from `matrix_homeserver_generic_secret_key` in `group_vars/matrix_servers`."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:62
+msgid "To set your own Token, add the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:68
+msgid "In case Jitsi is also managed by this playbook and 'matrix' authentication in Jitsi is enabled, this collection will automatically configure Jitsi to use the configured auth token."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:70
+msgid "Disable Auth (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:72
+msgid "Authorization is enabled by default. To disable it, add the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:78
+msgid "Federation (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:80
+msgid "In theory (however currently untested), UVS can handle federation. To enable it, add the following configuration to your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:86
+msgid "This will instruct UVS to verify the OpenID token against any domain given in a request. Homeserver discovery is done via '.well-known/matrix/server' of the given domain."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:88
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:90
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:97
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service matrix-user-verification-service` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:99
+msgid "`just install-service matrix-user-verification-service` is useful for maintaining your setup quickly 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 `just setup-all` runs the `ensure-matrix-users-created` tag too."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:101
+msgid "Logging"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:103
+msgid "The configuration variable `UVS_LOG_LEVEL` can be set to:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:104
+msgid "warning"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:105
+msgid "info"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:106
+msgid "debug"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:108
+msgid "TLS Certificate Checking"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:110
+msgid "If the Matrix Homeserver does not provide a valid TLS certificate, UVS will fail with the following error message:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:112
+msgid "message: 'No response received: [object Object]',"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:114
+msgid "This also applies to self-signed and let's encrypt staging certificates."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:116
+msgid "To disable certificate validation altogether (INSECURE! Not suitable for production use!) set: `NODE_TLS_REJECT_UNAUTHORIZED=0`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-user-verification-service.md:118
+msgid "Alternatively, it is possible to inject your own CA certificates into the container by mounting a PEM file with additional trusted CAs into the container and pointing the `NODE_EXTRA_CA_CERTS` environment variable to it."
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-playbook.pot b/i18n/translation-templates/docs/configuring-playbook.pot
new file mode 100644
index 000000000..33265200b
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-playbook.pot
@@ -0,0 +1,529 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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.md:1
+msgid "Configuring the playbook"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:3
+msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md)</sup>"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:5
+msgid "If you've configured your DNS records and retrieved the playbook's source code to your computer, you can start configuring the playbook. To do so, follow these steps inside the playbook directory:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:7
+msgid "create a directory to hold your configuration (`mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\")"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:9
+msgid "copy the sample configuration file (`cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:11
+msgid "edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You may also take a look at the various `roles/*/ROLE_NAME_HERE/defaults/main.yml` files and see if there's something you'd like to copy over and override in your `vars.yml` configuration file."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:13
+msgid "copy the sample inventory hosts file (`cp examples/hosts inventory/hosts`)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:15
+msgid "edit the inventory hosts file (`inventory/hosts`) to your liking"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:17
+msgid "(optional, advanced) you may wish to keep your `inventory` directory under version control with [git](https://git-scm.com/) or any other version-control system."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:19
+msgid "(optional, advanced) to run Ansible against multiple servers with different `sudo` credentials, you can copy the sample inventory hosts yaml file for each of your hosts: (`cp examples/host.yml inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin/ansible-all-hosts.sh) script [in the installation step](installing.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:21
+msgid "For a basic Matrix installation, that's all you need."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:23
+msgid "For a more custom setup, see the [Other configuration options](#other-configuration-options) below."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:25
+msgid "[▶️](installing.md) When you're done with all the configuration you'd like to do, continue with [Installing](installing.md)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:27
+msgid "Other configuration options"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:29
+msgid "Core service adjustments"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:31
+msgid "Homeserver configuration:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:32
+msgid "[Configuring Synapse](configuring-playbook-synapse.md), if you're going with the default/recommended homeserver implementation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:34
+msgid "[Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:36
+msgid "[Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:38
+msgid "Server components:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:39
+msgid "[Using an external PostgreSQL server](configuring-playbook-external-postgres.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:41
+msgid "[Adjusting TURN server configuration](configuring-playbook-turn.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:43
+msgid "[Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:45
+msgid "[Using your own webserver, instead of this playbook's Traefik reverse-proxy](configuring-playbook-own-webserver.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:47
+msgid "[Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:49
+msgid "[Adjusting email-sending settings](configuring-playbook-email.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:51
+msgid "[Setting up ma1sd Identity Server](configuring-playbook-ma1sd.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:53
+msgid "[Setting up Dynamic DNS](configuring-playbook-dynamic-dns.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:55
+msgid "Server connectivity:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:56
+msgid "[Enabling Telemetry for your Matrix server](configuring-playbook-telemetry.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:58
+msgid "[Controlling Matrix federation](configuring-playbook-federation.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:60
+msgid "Clients"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:62
+msgid "Web clients for Matrix that you can host on your own domains."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:64
+msgid "[Configuring Element Web](configuring-playbook-client-element-web.md), if you're going with the default/recommended client"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:66
+msgid "[Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a lightweight Matrix client with legacy and mobile browser support"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:68
+msgid "[Setting up Cinny](configuring-playbook-client-cinny.md), if you've enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing primarily on simple, elegant and secure interface"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:70
+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:72
+msgid "Authentication and user-related"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:74
+msgid "Extend and modify how users are authenticated on your homeserver."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:76
+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:78
+msgid "[Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:80
+msgid "[Setting up Synapse Admin](configuring-playbook-synapse-admin.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:82
+msgid "[Setting up matrix-registration](configuring-playbook-matrix-registration.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:84
+msgid "[Setting up the REST authentication password provider module](configuring-playbook-rest-auth.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:86
+msgid "[Setting up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:88
+msgid "[Setting up the LDAP authentication password provider module](configuring-playbook-ldap-auth.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:90
+msgid "[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:92
+msgid "[Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:94
+msgid "[Setting up Matrix User Verification Service](configuring-playbook-user-verification-service.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:96
+msgid "File Storage"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:98
+msgid "Use alternative file storage to the default `media_store` folder."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:100
+msgid "[Storing Matrix media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:102
+msgid "[Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:104
+msgid "[Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:106
+msgid "Bridging other networks"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:108
+msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:110
+msgid "[Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:112
+msgid "[Setting up Mautrix Telegram bridging](configuring-playbook-bridge-mautrix-telegram.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:114
+msgid "[Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:116
+msgid "[Setting up Mautrix Google Messages bridging](configuring-playbook-bridge-mautrix-gmessages.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:118
+msgid "[Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-mautrix-whatsapp.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:120
+msgid "[Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:122
+msgid "[Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:124
+msgid "[Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-mautrix-googlechat.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:126
+msgid "[Setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:128
+msgid "[Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-signal.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:130
+msgid "[Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](configuring-playbook-bridge-mautrix-wsproxy.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:132
+msgid "[Setting up Appservice IRC bridging](configuring-playbook-bridge-appservice-irc.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:134
+msgid "[Setting up Appservice Discord bridging](configuring-playbook-bridge-appservice-discord.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:136
+msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:138
+msgid "[Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-appservice-kakaotalk.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:140
+msgid "[Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-linkedin.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:142
+msgid "[Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) - a bridge between Matrix and multiple project management services, such as [GitHub](https://github.com), [GitLab](https://about.gitlab.com) and [JIRA](https://www.atlassian.com/software/jira)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:144
+msgid "[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:146
+msgid "[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-puppet-instagram.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:148
+msgid "[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:150
+msgid "[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-puppet-discord.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:152
+msgid "[Setting up MX Puppet GroupMe bridging](configuring-playbook-bridge-mx-puppet-groupme.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:154
+msgid "[Setting up MX Puppet Steam bridging](configuring-playbook-bridge-mx-puppet-steam.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:156
+msgid "[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:158
+msgid "[Setting up Email2Matrix](configuring-playbook-email2matrix.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:160
+msgid "[Setting up Postmoogle email bridging](configuring-playbook-bridge-postmoogle.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:162
+msgid "[Setting up Matrix SMS bridging](configuring-playbook-bridge-matrix-bridge-sms.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:164
+msgid "[Setting up Heisenbridge bouncer-style IRC bridging](configuring-playbook-bridge-heisenbridge.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:166
+msgid "[Setting up WeChat bridging](configuring-playbook-bridge-wechat.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:168
+msgid "Bots"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:170
+msgid "Bots provide various additional functionality to your installation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:172
+msgid "[Setting up baibot](configuring-playbook-bot-baibot.md) - a bot through which you can talk to various [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) services ([OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) and [others](https://github.com/etkecc/baibot/blob/main/docs/providers.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:174
+msgid "[Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md) - a bot to remind you about stuff"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:176
+msgid "[Setting up matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) - a bot to create and manage registration tokens to invite users"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:178
+msgid "[Setting up maubot](configuring-playbook-bot-maubot.md) - a plugin-based Matrix bot system"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:180
+msgid "[Setting up Honoroit](configuring-playbook-bot-honoroit.md) - a helpdesk bot"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:182
+msgid "[Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) - a moderation tool/bot"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:184
+msgid "[Setting up Draupnir](configuring-playbook-bot-draupnir.md) - a moderation tool/bot, forked from Mjolnir and maintained by its former leader developer"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:186
+msgid "[Setting up Draupnir for all/D4A](configuring-playbook-appservice-draupnir-for-all.md) - like the [Draupnir bot](configuring-playbook-bot-draupnir.md) mentioned above, but running in appservice mode and supporting multiple instances"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:188
+msgid "[Setting up Buscarron](configuring-playbook-bot-buscarron.md) - a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:190
+msgid "Administration"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:192
+msgid "Services that help you in administrating and monitoring your Matrix installation."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:194
+msgid "[Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:196
+msgid "[Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:198
+msgid "[Enabling metrics and graphs for NginX logs](configuring-playbook-prometheus-nginxlog.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:200
+msgid "[Setting up the rageshake bug report server](configuring-playbook-rageshake.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:202
+msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:204
+msgid "Backups:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:205
+msgid "[Setting up BorgBackup](configuring-playbook-backup-borg.md) - a full Matrix server backup solution, including the Postgres database"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:207
+msgid "[Setting up postgres backup](configuring-playbook-postgres-backup.md) - a Postgres-database backup solution (note: does not include other files)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:209
+msgid "Other specialized services"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:211
+msgid "Various services that don't fit any other categories."
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:213
+msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:215
+msgid "[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:217
+msgid "[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:219
+msgid "[Setting up Etherpad](configuring-playbook-etherpad.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:221
+msgid "[Setting up the Jitsi video-conferencing platform](configuring-playbook-jitsi.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:223
+msgid "[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) - a federated comment system built on Matrix"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:225
+msgid "[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-pantalaimon.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:227
+msgid "[Setting up the Sygnal push gateway](configuring-playbook-sygnal.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:229
+msgid "[Setting up the ntfy push notifications server](configuring-playbook-ntfy.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:231
+msgid "Deprecated / unmaintained / removed services"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:233
+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:235
+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:237
+msgid "[Setting up Appservice Webhooks bridging](configuring-playbook-bridge-appservice-webhooks.md) (deprecated; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:239
+msgid "[Setting up the Dimension integration manager](configuring-playbook-dimension.md) ([unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299); after [installing](installing.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:241
+msgid "[Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:243
+msgid "[Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) (unmaintained; the bridge's author suggests taking a look at [baibot](https://github.com/etkecc/baibot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bot-baibot.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:245
+msgid "[Setting up Mautrix Facebook bridging](configuring-playbook-bridge-mautrix-facebook.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-messenger](configuring-playbook-bridge-mautrix-meta-messenger.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:247
+msgid "[Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-mautrix-hangouts.md) (deprecated in favor of the Google Chat bridge with [mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:249
+msgid "[Setting up Mautrix Instagram bridging](configuring-playbook-bridge-mautrix-instagram.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-instagram](configuring-playbook-bridge-mautrix-meta-instagram.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:251
+msgid "[Setting up MX Puppet Skype bridging](configuring-playbook-bridge-mx-puppet-skype.md) (removed; this component has been broken for a long time, so it has been removed from the playbook. Consider [setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md))"
+msgstr ""
diff --git a/i18n/translation-templates/docs/configuring-well-known.pot b/i18n/translation-templates/docs/configuring-well-known.pot
new file mode 100644
index 000000000..7b35a517d
--- /dev/null
+++ b/i18n/translation-templates/docs/configuring-well-known.pot
@@ -0,0 +1,253 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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-well-known.md:1
+msgid "Configuring Service Discovery via .well-known"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:3
+msgid "This documentation page explains how to configure Service discovery via `/.well-known/` files. Service discovery is a way for the Matrix network to discover where a Matrix server is."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:5
+msgid "Types of well-known service discovery mechanism"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:7
+msgid "There are 3 types of well-known service discovery mechanism that Matrix makes use of:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:9
+msgid "(important) **Federation Server discovery** (`/.well-known/matrix/server`) -- assists other servers in the Matrix network with finding your server. With the default playbook configuration specified on the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), this is necessary for federation to work. Without a proper configuration, your server will effectively not be part of the Matrix network."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:11
+msgid "(less important) **Client Server discovery** (`/.well-known/matrix/client`) -- assists programs that you use to connect to your server (e.g. Element Web), so that they can make it more convenient for you by automatically configuring the \"Homeserver URL\" and \"Identity Server URL\" addresses."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:13
+msgid "(optional) **Support service discovery** (`/.well-known/matrix/support`) -- returns server admin contact and support page of the domain."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:15
+msgid "Federation Server Discovery"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:17
+msgid "All services created by this playbook are meant to be installed on their own server (such as `matrix.example.com`), instead of the base domain (`example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:19
+msgid "As [per the Server-Server specification](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), in order to use a short Matrix user ID like `@alice:example.com` instead of `@alice:matrix.example.com` while hosting services on a subdomain such as `matrix.example.com`, the Matrix network needs to be instructed of [server delegation](howto-server-delegation.md) / redirection."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:21
+msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:23
+msgid "If you set up the DNS SRV record for server delegation instead, take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced)](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced)"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:25
+msgid "Client Server Discovery"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:27
+msgid "Client Server Service discovery lets various client programs which support it, to receive a full user ID (e.g. `@alice:example.com`) and determine where the Matrix server is automatically (e.g. `https://matrix.example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:29
+msgid "This lets you (and your users) easily connect to your Matrix server without having to customize connection URLs. When using client programs that support it, you won't need to point them to `https://matrix.example.com` in Custom Server options manually anymore. The connection URL would be discovered automatically from your full username."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:31
+msgid "Without /.well-known/matrix/client, the client will make the wrong \"homeserver URL\" assumption (it will default to using https://example.com, and users will need to notice and adjust it manually (changing it to https://matrix.example.com)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:33
+msgid "As [per the Client-Server specification](https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery) Matrix does Client Server service discovery using a `/.well-known/matrix/client` file hosted on the base domain (e.g. `example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:35
+msgid "However, this playbook installs your Matrix server on another domain (e.g. `matrix.example.com`) and not on the base domain (e.g. `example.com`), so it takes a little extra manual effort to set up the file."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:37
+msgid "Support Service Discovery (optional)"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:39
+msgid "[MSC 1929](https://github.com/matrix-org/matrix-spec-proposals/pull/1929), which was added to [Matrix Specification version v1.10](https://spec.matrix.org/v1.10/client-server-api/#getwell-knownmatrixsupport), specifies a way to add contact details of admins, as well as a link to a support page for users who are having issues with the service. Automated services may also index this information and use it for abuse reports, etc."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:41
+msgid "To enable it, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:62
+msgid "Installing well-known files on the base domain's server"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:64
+msgid "To implement the service discovery mechanisms, your base domain's server (e.g. `example.com`) needs to run an HTTPS-capable webserver."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:66
+msgid "Serving the base domain from the Matrix server via the playbook"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:68
+msgid "If you don't have a server for your base domain at all, you can use the Matrix server for this. If you don't need the base domain (e.g. `example.com`) for anything else (hosting a website, etc.), you can point it to the Matrix server's IP address and tell the playbook to configure it."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:70
+msgid "**This is the easiest way to set up well-known serving** -- letting the playbook handle the whole base domain for you (including SSL certificates, etc.) and take care to serve the appropriate well-known files automatically."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:72
+msgid "If you decide to go this route, you don't need to read ahead in this document. Instead, go to [Serving the base domain](configuring-playbook-base-domain-serving.md) to learn how the playbook can help you set it up."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:74
+msgid "However, if you need to use the base domain for other things, this method is less suitable than the one explained below."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:76
+msgid "Manually installing well-known files on the base domain's server"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:78
+msgid "If you're managing the base domain by yourself somehow, you'll need to set up serving of some `/.well-known/matrix/*` files from it via HTTPS."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:80
+msgid "To make things easy for you to set up, this playbook generates and hosts a few well-known files on the Matrix domain's server. The files are generated at the `/matrix/static-files/public/.well-known/matrix/` path on the server and hosted at URLs like `https://matrix.example.com/.well-known/matrix/server` and `https://matrix.example.com/.well-known/matrix/client`, even though this is the wrong place to host them."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:82
+msgid "You have two options when it comes to installing the files on the base domain's server:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:84
+msgid "(Option 1): **Copying the files manually** to your base domain's server"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:86
+msgid "**Hint**: Option 2 is generally a better way to do this. Make sure to go with it, if possible."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:88
+msgid "All you need to do is:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:90
+msgid "copy `/.well-known/matrix/server` and `/.well-known/matrix/client` from the Matrix server (e.g. `matrix.example.com`) to your base domain's server (`example.com`). You can find these files in the `/matrix/static-files/.well-known/matrix` directory on the Matrix server. They are also accessible on URLs like this: `https://matrix.example.com/.well-known/matrix/server` (same for `client`)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:92
+msgid "set up the server at your base domain (e.g. `example.com`) so that it adds an extra HTTP header when serving the `/.well-known/matrix/client` file. [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS), the `Access-Control-Allow-Origin` header should be set with a value of `*`. If you don't do this step, web-based Matrix clients (like Element Web) may fail to work. Setting up headers for the `/.well-known/matrix/server` file is not necessary, as this file is only consumed by non-browsers, which don't care about CORS."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:94
+msgid "This is relatively easy to do and possibly your only choice if you can only host static files from the base domain's server. It is, however, **a little fragile**, as future updates performed by this playbook may regenerate the well-known files and you may need to notice that and copy them over again."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:96
+msgid "(Option 2): **Setting up reverse-proxying** of the well-known files from the base domain's server to the Matrix server"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:98
+msgid "This option is less fragile and generally better."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:100
+msgid "On the base domain's server (e.g. `example.com`), you can set up reverse-proxying, so that any access for the `/.well-known/matrix` location prefix is forwarded to the Matrix domain's server (e.g. `matrix.example.com`)."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:102
+msgid "With this method, you **don't need** to add special HTTP headers for [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) reasons (like `Access-Control-Allow-Origin`), because your Matrix server (where requests ultimately go) will be configured by this playbook correctly."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:104
+msgid "**For nginx**, it would be something like this:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:121
+msgid "**For Apache2**, it would be something like this:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:135
+msgid "**For Caddy 2**, it would be something like this:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:145
+msgid "**For HAProxy**, it would be something like this:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:164
+msgid "**For Netlify**, configure a [redirect](https://docs.netlify.com/routing/redirects/) using a `_redirects` file in the [publish directory](https://docs.netlify.com/configure-builds/overview/#definitions) with contents like this:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:170
+msgid "**For AWS CloudFront**"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:172
+msgid "Add a custom origin with matrix.example.com to your distribution"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:173
+msgid "Add two behaviors, one for `.well-known/matrix/client` and one for `.well-known/matrix/server` and point them to your new origin."
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:175
+msgid "Make sure to:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:177
+msgid "**replace `example.com`** in the server configuration with your actual domain name"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:178
+msgid "and: to **do this for the HTTPS-enabled server block**, as that's where Matrix expects the file to be"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:180
+msgid "Confirming it works"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:182
+msgid "No matter which method you've used to set up the well-known files, if you've done it correctly you should be able to see a JSON file at these URLs:"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:184
+msgid "`https://example.com/.well-known/matrix/server`"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:185
+msgid "`https://example.com/.well-known/matrix/client`"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:186
+msgid "`https://example.com/.well-known/matrix/support`"
+msgstr ""
+
+#: ../../../docs/configuring-well-known.md:188
+msgid "You can also check if everything is configured correctly, by [checking if services work](maintenance-checking-services.md)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/container-images.pot b/i18n/translation-templates/docs/container-images.pot
new file mode 100644
index 000000000..a944a484a
--- /dev/null
+++ b/i18n/translation-templates/docs/container-images.pot
@@ -0,0 +1,1153 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/container-images.md:1
+msgid "Container images used by the playbook"
+msgstr ""
+
+#: ../../../docs/container-images.md:3
+msgid "This page summarizes the container ([Docker](https://www.docker.com/)) images used by the playbook when setting up your server."
+msgstr ""
+
+#: ../../../docs/container-images.md:5
+msgid "We try to stick to official images (provided by their respective projects) as much as possible."
+msgstr ""
+
+#: ../../../docs/container-images.md:7
+msgid "Homeserver"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Service"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Container image"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Default?"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Description"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Synapse](configuring-playbook-synapse.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[element-hq/synapse](https://ghcr.io/element-hq/synapse)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "✅"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Conduit](configuring-playbook-conduit.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrixconduit/matrix-conduit](https://hub.docker.com/r/matrixconduit/matrix-conduit)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "❌"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Dendrite](configuring-playbook-dendrite.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrixdotorg/dendrite-monolith](https://hub.docker.com/r/matrixdotorg/dendrite-monolith/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse."
+msgstr ""
+
+#: ../../../docs/container-images.md:15
+msgid "Clients"
+msgstr ""
+
+#: ../../../docs/container-images.md:17
+msgid "Web clients for Matrix that you can host on your own domains."
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Element Web](configuring-playbook-client-element-web.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[vectorim/element-web](https://hub.docker.com/r/vectorim/element-web/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Default Matrix web client, configured to connect to your own Synapse server"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Hydrogen](configuring-playbook-client-hydrogen.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[element-hq/hydrogen-web](https://ghcr.io/element-hq/hydrogen-web)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Lightweight Matrix client with legacy and mobile browser support"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Cinny](configuring-playbook-client-cinny.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[ajbura/cinny](https://hub.docker.com/r/ajbura/cinny)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Simple, elegant and secure web client"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[etke.cc/schildichat-web](https://ghcr.io/etkecc/schildichat-web)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Based on Element Web, with a more traditional instant messaging experience"
+msgstr ""
+
+#: ../../../docs/container-images.md:26
+msgid "Server Components"
+msgstr ""
+
+#: ../../../docs/container-images.md:28
+msgid "Services that run on the server to make the various parts of your installation work."
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[PostgreSQL](configuring-playbook-external-postgres.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[postgres](https://hub.docker.com/_/postgres/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Database for Synapse. [Using an external PostgreSQL server](configuring-playbook-external-postgres.md) is also possible."
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Coturn](configuring-playbook-turn.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[coturn/coturn](https://hub.docker.com/r/coturn/coturn/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "STUN/TURN server for WebRTC audio/video calls"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Traefik](configuring-playbook-traefik.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Traefik](https://hub.docker.com/_/traefik/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](configuring-playbook-own-webserver.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Let's Encrypt](configuring-playbook-ssl-certificates.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[certbot/certbot](https://hub.docker.com/r/certbot/certbot/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "The [certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Exim](configuring-playbook-email.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[devture/exim-relay](https://hub.docker.com/r/devture/exim-relay/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[ma1sd](configuring-playbook-ma1sd.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Matrix Identity Server"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[ddclient](configuring-playbook-dynamic-dns.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[linuxserver/ddclient](https://hub.docker.com/r/linuxserver/ddclient)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider"
+msgstr ""
+
+#: ../../../docs/container-images.md:40
+msgid "Authentication"
+msgstr ""
+
+#: ../../../docs/container-images.md:42
+msgid "Extend and modify how users are authenticated on your homeserver."
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-synapse-rest-auth](configuring-playbook-rest-auth.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "(N/A)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "REST authentication password provider module"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-synapse-shared-secret-auth](configuring-playbook-shared-secret-auth.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Password provider module"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-synapse-ldap3](configuring-playbook-ldap-auth.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "LDAP Auth password provider module"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[activism.international/matrix_ldap_registration_proxy](https://gitlab.com/activism.international/matrix_ldap_registration_proxy/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "A proxy that handles Matrix registration requests and forwards them to LDAP."
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-registration](configuring-playbook-matrix-registration.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-matrix-registration/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "A simple python application to have a token based Matrix registration"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Matrix User Verification Service](configuring-playbook-user-verification-service.md) (UVS)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrixdotorg/matrix-user-verification-service](https://hub.docker.com/r/atrixdotorg/matrix-user-verification-service)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Service to verify details of a user based on an Open ID token"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[synapse-simple-antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "A spam checker module"
+msgstr ""
+
+#: ../../../docs/container-images.md:54
+msgid "File Storage"
+msgstr ""
+
+#: ../../../docs/container-images.md:56
+msgid "Use alternative file storage to the default `media_store` folder."
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Goofys](configuring-playbook-s3-goofys.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[ewoutp/goofys](https://hub.docker.com/r/ewoutp/goofys/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Amazon S3](https://aws.amazon.com/s3/) (or other S3-compatible object store) storage for Synapse's content repository (`media_store`) files"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[synapse-s3-storage-provider](configuring-playbook-s3.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[t2bot/matrix-media-repo](https://ghcr.io/t2bot/matrix-media-repo)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "matrix-media-repo is a 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:64
+msgid "Bridges"
+msgstr ""
+
+#: ../../../docs/container-images.md:66
+msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix-discord](configuring-playbook-bridge-mautrix-discord.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix/discord](https://mau.dev/mautrix/discord/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [Discord](https://discord.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix-slack](configuring-playbook-bridge-mautrix-slack.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix/slack](https://mau.dev/mautrix/slack/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [Slack](https://slack.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix-telegram](configuring-playbook-bridge-mautrix-telegram.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix/telegram](https://mau.dev/mautrix/telegram/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [Telegram](https://telegram.org/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix-gmessages](configuring-playbook-bridge-mautrix-gmessages.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix/gmessages](https://mau.dev/mautrix/gmessages/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [Google Messages](https://messages.google.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix-whatsapp](configuring-playbook-bridge-mautrix-whatsapp.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix/whatsapp](https://mau.dev/mautrix/whatsapp/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [WhatsApp](https://www.whatsapp.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix-wsproxy](configuring-playbook-bridge-mautrix-wsproxy.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix/wsproxy](https://mau.dev/mautrix/wsproxy/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to Android SMS or Apple iMessage"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix-twitter](configuring-playbook-bridge-mautrix-twitter.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix/twitter](https://mau.dev/mautrix/twitter/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [Twitter](https://twitter.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix/googlechat](https://mau.dev/mautrix/googlechat/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [Google Chat](https://en.wikipedia.org/wiki/Google_Chat)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "mautrix-meta (for [Messenger](configuring-playbook-bridge-mautrix-meta-messenger.md) and [Instagram](configuring-playbook-bridge-mautrix-meta-instagram.md))"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix/meta](https://mau.dev/mautrix/meta/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [Messenger](https://messenger.com/) and [Instagram](https://instagram.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix-signal](configuring-playbook-bridge-mautrix-signal.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix/signal](https://mau.dev/mautrix/signal/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [Signal](https://www.signal.org/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[beeper-linkedin](configuring-playbook-bridge-beeper-linkedin.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[beeper/linkedin](https://ghcr.io/beeper/linkedin)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [LinkedIn](https://www.linkedin.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrixdotorg/matrix-appservice-irc](https://hub.docker.com/r/matrixdotorg/matrix-appservice-irc)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-appservice-kakaotalk](configuring-playbook-bridge-appservice-kakaotalk.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Self-building"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-org/matrix-appservice-discord](https://ghcr.io/matrix-org/matrix-appservice-discord)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+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 ""
+
+#: ../../../docs/container-images.md:0
+msgid "[halfshot/matrix-hookshot](https://hub.docker.com/r/halfshot/matrix-hookshot)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-sms-bridge](configuring-playbook-bridge-matrix-bridge-sms.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[folivonet/matrix-sms-bridge](https://hub.docker.com/repository/docker/folivonet/matrix-sms-bridge)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to SMS"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-wechat](configuring-playbook-bridge-wechat.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[lxduo/matrix-wechat](https://hub.docker.com/r/lxduo/matrix-wechat)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [WeChat](https://www.wechat.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Heisenbridge](configuring-playbook-bridge-heisenbridge.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[hif1/heisenbridge](https://hub.docker.com/r/hif1/heisenbridge)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[nodefyme/go-skype-bridge](https://hub.docker.com/r/nodefyme/go-skype-bridge)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [Skype](https://www.skype.com)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [Slack](https://slack.com)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-puppet-instagram)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mx-puppet-groupme](configuring-playbook-bridge-mx-puppet-groupme.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[xangelix/mx-puppet-groupme](https://hub.docker.com/r/xangelix/mx-puppet-groupme)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [GroupMe](https://groupme.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mx-puppet-steam](configuring-playbook-bridge-mx-puppet-steam.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[icewind1991/mx-puppet-steam](https://hub.docker.com/r/icewind1991/mx-puppet-steam)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [Steam](https://steamapp.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Email2Matrix](configuring-playbook-email2matrix.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[devture/email2matrix](https://hub.docker.com/r/devture/email2matrix/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge for relaying emails to Matrix rooms"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Postmoogle](configuring-playbook-bridge-postmoogle.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[etke.cc/postmoogle](https://github.com/etkecc/postmoogle/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Email to Matrix bridge"
+msgstr ""
+
+#: ../../../docs/container-images.md:99
+msgid "Bots"
+msgstr ""
+
+#: ../../../docs/container-images.md:101
+msgid "Bots provide various additional functionality to your installation."
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[baibot](configuring-playbook-bot-baibot.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[etke.cc/baibot](https://ghcr.io/etkecc/baibot)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[anoa/matrix-reminder-bot](https://hub.docker.com/r/anoa/matrix-reminder-bot)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bot for scheduling one-off & recurring reminders and alarms"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[moanos/matrix-registration-bot](https://hub.docker.com/r/moanos/matrix-registration-bot/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bot for invitations by creating and managing registration tokens"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[maubot](configuring-playbook-bot-maubot.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[dock.mau.dev/maubot/maubot](https://mau.dev/maubot/maubot/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "A plugin-based Matrix bot system"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Honoroit](configuring-playbook-bot-honoroit.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[etke.cc/honoroit](https://github.com/etkecc/honoroit/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "A helpdesk bot"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Mjolnir](configuring-playbook-bot-mjolnir.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrixdotorg/mjolnir](https://hub.docker.com/r/matrixdotorg/mjolnir)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "A moderation tool for Matrix"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Draupnir](configuring-playbook-bot-draupnir.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[gnuxie/draupnir](https://hub.docker.com/r/gnuxie/draupnir)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "A moderation tool for Matrix (Fork of Mjolnir)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Buscarron](configuring-playbook-bot-buscarron.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[etke.cc/buscarron](https://ghcr.io/etkecc/buscarron)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Web forms (HTTP POST) to Matrix"
+msgstr ""
+
+#: ../../../docs/container-images.md:114
+msgid "Administration"
+msgstr ""
+
+#: ../../../docs/container-images.md:116
+msgid "Services that help you in administrating and monitoring your Matrix installation."
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[metio/matrix-alertmanager-receiver](https://hub.docker.com/r/metio/matrix-alertmanager-receiver)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[element-hq/matrix-authentication-service](https://ghcr.io/element-hq/matrix-authentication-service)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "OAuth 2.0 and OpenID Provider server"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[synapse-admin](configuring-playbook-synapse-admin.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[etke.cc/synapse-admin](https://ghcr.io/etkecc/synapse-admin)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "A web UI tool for administrating users and rooms on your Matrix server"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Metrics and Graphs](configuring-playbook-prometheus-grafana.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[prom/prometheus](https://hub.docker.com/r/prom/prometheus/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Prometheus](https://prometheus.io) time-series database server"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[prom/node-exporter](https://hub.docker.com/r/prom/node-exporter/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[grafana/grafana](https://hub.docker.com/r/grafana/grafana/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Graphing tool that works well with the above two images. Our playbook also adds two dashboards for [Synapse](https://github.com/element-hq/synapse/tree/master/contrib/grafana) and [Node Exporter](https://github.com/rfrail3/grafana-dashboards)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Metrics and Graphs](configuring-playbook-prometheus-nginxlog.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[martin-helmich/prometheus-nginxlog-exporter/exporter](https://ghcr.io/martin-helmich/prometheus-nginxlog-exporter/exporter)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Addon for Prometheus that gathers access logs from various nginx reverse-proxies"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Borg](configuring-playbook-backup-borg.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Backups"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[rageshake](configuring-playbook-rageshake.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-org/rageshake](https://ghcr.io/matrix-org/rageshake)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bug report server"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[synapse-usage-exporter](configuring-playbook-synapse-usage-exporter.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus."
+msgstr ""
+
+#: ../../../docs/container-images.md:131
+msgid "Misc"
+msgstr ""
+
+#: ../../../docs/container-images.md:133
+msgid "Various services that don't fit any other categories."
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[sliding-sync](configuring-playbook-sliding-sync-proxy.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync)"
+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 "A Synapse module to automatically accept invites."
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[synapse_auto_compressor](configuring-playbook-synapse-auto-compressor.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[etke.cc/rust-synapse-compress-state](https://gitlab.com/etke.cc/rust-synapse-compress-state/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "A cli tool that automatically compresses `state_groups` database table in background."
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-corporal/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Reconciliator and gateway for a managed Matrix server"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Etherpad](configuring-playbook-etherpad.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[etherpad/etherpad](https://hub.docker.com/r/etherpad/etherpad/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "An open source collaborative text editor"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Jitsi](configuring-playbook-jitsi.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[jitsi/web](https://hub.docker.com/r/jitsi/web)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "the [Jitsi](https://jitsi.org/) web UI"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[jitsi/jicofo](https://hub.docker.com/r/jitsi/jicofo)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "the [Jitsi](https://jitsi.org/) Focus component"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[jitsi/prosody](https://hub.docker.com/r/jitsi/prosody)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "the [Jitsi](https://jitsi.org/) Prosody XMPP server component"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[jitsi/jvb](https://hub.docker.com/r/jitsi/jvb)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "the [Jitsi](https://jitsi.org/) Video Bridge component"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Cactus Comments](configuring-playbook-cactus-comments.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[cactuscomments/cactus-appservice](https://hub.docker.com/r/cactuscomments/cactus-appservice/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "A federated comment system built on Matrix"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[joseluisq/static-web-server](https://hub.docker.com/r/joseluisq/static-web-server)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Pantalaimon](configuring-playbook-pantalaimon.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrixdotorg/pantalaimon](https://hub.docker.com/r/matrixdotorg/pantalaimon)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "An E2EE aware proxy daemon"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Sygnal](configuring-playbook-sygnal.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrixdotorg/sygnal](https://hub.docker.com/r/matrixdotorg/sygnal/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Reference Push Gateway for Matrix"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[ntfy](configuring-playbook-ntfy.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[binwiederhier/ntfy](https://hub.docker.com/r/binwiederhier/ntfy/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Self-hosted, UnifiedPush-compatible push notifications server"
+msgstr ""
+
+#: ../../../docs/container-images.md:152
+msgid "Container images of deprecated / unmaintained services"
+msgstr ""
+
+#: ../../../docs/container-images.md:154
+msgid "The list of the deprecated or unmaintained services is available [here](configuring-playbook.md#deprecated--unmaintained--removed-services)."
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Dimension](configuring-playbook-dimension.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-dimension)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "An open source integration manager for Matrix clients"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[Go-NEB](configuring-playbook-bot-go-neb.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrixdotorg/go-neb](https://hub.docker.com/r/matrixdotorg/go-neb)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "A multi functional bot written in Go"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrix-chatgpt-bot](configuring-playbook-bot-chatgpt.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[matrixgpt/matrix-chatgpt-bot](https://ghcr.io/matrixgpt/matrix-chatgpt-bot)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Accessing ChatGPT via your favourite Matrix client"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix-facebook](configuring-playbook-bridge-mautrix-facebook.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix/facebook](https://mau.dev/mautrix/facebook/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [Facebook](https://facebook.com/)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix-hangouts](configuring-playbook-bridge-mautrix-hangouts.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix/hangouts](https://mau.dev/mautrix/hangouts/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [Google Hangouts](https://en.wikipedia.org/wiki/Google_Hangouts)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix-instagram](configuring-playbook-bridge-mautrix-instagram.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "[mautrix/instagram](https://mau.dev/mautrix/instagram/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md:0
+msgid "Bridge to [Instagram](https://instagram.com/)"
+msgstr ""
diff --git a/i18n/translation-templates/docs/faq.pot b/i18n/translation-templates/docs/faq.pot
new file mode 100644
index 000000000..a64544234
--- /dev/null
+++ b/i18n/translation-templates/docs/faq.pot
@@ -0,0 +1,874 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/faq.md:1
+msgid "Frequently Asked Questions"
+msgstr ""
+
+#: ../../../docs/faq.md:3
+msgid "This documentation page tries to answer various Frequently Asked Questions about all things [Matrix](https://matrix.org/), with a focus on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work))."
+msgstr ""
+
+#: ../../../docs/faq.md:5
+msgid "This FAQ page does not intend to replace the [matrix.org FAQ](https://matrix.org/faq/) (please see that one too)."
+msgstr ""
+
+#: ../../../docs/faq.md:7
+msgid "We've only started this FAQ recently, so it's still somewhat empty."
+msgstr ""
+
+#: ../../../docs/faq.md:9
+msgid "Also, we encourage you to not dig yourself into a hole by reading way too much. When you've heard enough, proceed to installation. To get started, see [below](#how-do-i-run-the-installation) about our installation guides."
+msgstr ""
+
+#: ../../../docs/faq.md:11
+msgid "Introductory"
+msgstr ""
+
+#: ../../../docs/faq.md:13
+msgid "Where do I find more questions and answers about Matrix?"
+msgstr ""
+
+#: ../../../docs/faq.md:15
+msgid "This is a Frequently Asked Questions page focused on this [Ansible](https://www.ansible.com/) playbook ([What is Ansible? How does it work?](#what-is-ansible-how-does-it-work)) for deploying a [Matrix](https://matrix.org/) server."
+msgstr ""
+
+#: ../../../docs/faq.md:17
+msgid "For a lot more generic questions and answers, see the [matrix.org FAQ](https://matrix.org/faq/)."
+msgstr ""
+
+#: ../../../docs/faq.md:19
+msgid "What is Matrix? What is Element? What is Synapse? Why are you confusing me with so many terms?"
+msgstr ""
+
+#: ../../../docs/faq.md:21
+msgid "[Matrix](https://matrix.org/) is a new type of realtime communication (chat) network, the closest analogy to which is probably \"email\"."
+msgstr ""
+
+#: ../../../docs/faq.md:23
+msgid "You don't just use the \"email\" protocols (SMTP, POP3, IMAP) directly though. There's a *server* somewhere which stores your data (`@gmail.com`, `@yahoo.com`, `@hotmail.com`, `@your-company.com`) and you access it by using these \"email\" protocols via some *client* program (Outlook, Thunderbird, some website, etc)."
+msgstr ""
+
+#: ../../../docs/faq.md:25
+msgid "In the world of the Matrix chat protocol, there are various client programs. The first and currently most full-featured one is called [Element](https://element.io/) (used to be called Riot.im and Vector.im in the past). There are [many other clients](https://matrix.org/clients/). You can switch clients as much as you want until you find the one that is right for you on a given platform (you may use Element Desktop on your desktop, but Fluffychat on your phone, etc)."
+msgstr ""
+
+#: ../../../docs/faq.md:27
+msgid "Matrix is also like email due to the fact that there are many servers around the world which can all talk to each other (you can send email from `@gmail.com` addresses to `@yahoo.com` and `@hotmail.com` addresses). It's the same with Matrix (`@bob:example.com` can talk to `@alice:example.org`)."
+msgstr ""
+
+#: ../../../docs/faq.md:29
+msgid "If someone else is hosting your Matrix server (you being `@alice:matrix.org` or some other public server like this), all you need is a Matrix client program, like Element Web or Element X Android."
+msgstr ""
+
+#: ../../../docs/faq.md:31
+msgid "If you'd like to host your own server (you being `@alice:example.com`), you'd need to set up a Matrix server program, like Synapse."
+msgstr ""
+
+#: ../../../docs/faq.md:33
+msgid "In short:"
+msgstr ""
+
+#: ../../../docs/faq.md:35
+msgid "Matrix is the protocol - a set of rules about how the chat network operates"
+msgstr ""
+
+#: ../../../docs/faq.md:36
+msgid "Element is a client program you can use to participate on the Matrix chat network via some server (yours or someone else's). There are also [many other client programs](https://matrix.org/clients/)."
+msgstr ""
+
+#: ../../../docs/faq.md:37
+msgid "Synapse is a server program you can use to host your very own Matrix server."
+msgstr ""
+
+#: ../../../docs/faq.md:39
+msgid "This FAQ here mostly focuses on installing various Matrix services using the Ansible automation tool. You can learn much more about Matrix in the [matrix.org FAQ](https://matrix.org/faq/)."
+msgstr ""
+
+#: ../../../docs/faq.md:41
+msgid "People I wish to talk to are not on Matrix. Can I talk to them?"
+msgstr ""
+
+#: ../../../docs/faq.md:43
+msgid "You most likely can. Besides Matrix-native chats, Matrix also supports the concept of \"bridging\", which allows you to plug other networks into it."
+msgstr ""
+
+#: ../../../docs/faq.md:45
+msgid "This Ansible playbook can help you install [tens of bridges for various networks](configuring-playbook.md#bridging-other-networks)."
+msgstr ""
+
+#: ../../../docs/faq.md:47
+msgid "Besides setting up your own bridges (preferable), you can also use some [public bridges hosted by others](https://publiclist.anchel.nl/#bridges)."
+msgstr ""
+
+#: ../../../docs/faq.md:49
+msgid "How do I get started with Matrix?"
+msgstr ""
+
+#: ../../../docs/faq.md:51
+msgid "One of [Matrix](https://matrix.org/)'s distinguishing strengths (compared to other chat networks) is its decentralized nature. There's not just one entity (company, organization) controlling the servers. Rather there's thousands of servers operated by different people - one server being insecure, slow or disrespective toward its users does not affect the rest of the network. To participate in that decentralization in its fullest, consider hosting your own server or using some public server other than the largest/default one (`matrix.org`)."
+msgstr ""
+
+#: ../../../docs/faq.md:53
+msgid "There are 3 ways to get into Matrix, depending on your technical ability and needs:"
+msgstr ""
+
+#: ../../../docs/faq.md:55
+msgid "**using the existing default server** - the easiest way is to use an existing server. The largest public Matrix server is `matrix.org` and it's configured as a default server in clients such as [Element Web](https://app.element.io) and many others. Just use Element Web on the browser via that link (or [download client apps for your Desktop or smartphone](https://element.io/app-for-productivity)), create an account and start chatting."
+msgstr ""
+
+#: ../../../docs/faq.md:57
+msgid "**using some other server** - instead of using the largest public server (`matrix.org`), you can use another public one. Here's a [list of public Matrix servers](https://joinmatrix.org/servers/) to choose from. Go to [Element Web](https://app.element.io) or download [some other client](https://matrix.org/clients/) of your choosing and adjust the homeserver URL during login."
+msgstr ""
+
+#: ../../../docs/faq.md:59
+msgid "**using your own server** - running your own server puts you in ultimate control of your data. It also lets you have your own user IDs (e.g. `@bob:example.com`). See [How do I set up my own Matrix server](#how-do-i-set-up-my-own-matrix-server)."
+msgstr ""
+
+#: ../../../docs/faq.md:61
+msgid "How do I set up my own Matrix server?"
+msgstr ""
+
+#: ../../../docs/faq.md:63
+msgid "Normally, you'd first choose the [Matrix](https://matrix.org/) server software you'd like to run. At the time of this writing (January/2021), there's only one fully-featured server program, so there's only one reasonable choice. That's [Synapse](https://github.com/element-hq/synapse)."
+msgstr ""
+
+#: ../../../docs/faq.md:65
+msgid "There are [many guides about installing Synapse](https://matrix.org/docs/guides/#installing-synapse). Using this Ansible playbook is just one way of doing it."
+msgstr ""
+
+#: ../../../docs/faq.md:67
+msgid "Naturally, we're biased, so our usual recommendation is to go with this [Ansible](https://www.ansible.com/) playbook, instead of installing Synapse (and many many other things around it) manually."
+msgstr ""
+
+#: ../../../docs/faq.md:69
+msgid "To get started with the playbook, check out the [Quick start](quick-start.md) or full installation guide (starting at the [Prerequisites](prerequisites.md) page)."
+msgstr ""
+
+#: ../../../docs/faq.md:71
+msgid "What is Ansible? How does it work?"
+msgstr ""
+
+#: ../../../docs/faq.md:73
+msgid "[Ansible](https://www.ansible.com/) is an automation program. This \"playbook\" is a collection of tasks/scripts that will set up a [Matrix](https://matrix.org/) server for you, so you don't have to perform these tasks manually."
+msgstr ""
+
+#: ../../../docs/faq.md:75
+msgid "We have written these automated tasks for you and all you need to do is execute them using the Ansible program."
+msgstr ""
+
+#: ../../../docs/faq.md:77
+msgid "You can install Ansible and this playbook code repository on your own computer and tell it to install Matrix services at the server living at `matrix.example.com`. We recommend installing Ansible on your own computer."
+msgstr ""
+
+#: ../../../docs/faq.md:79
+msgid "Alternatively, you can download Ansible and the playbook itself directly on the `matrix.example.com` server."
+msgstr ""
+
+#: ../../../docs/faq.md:81
+msgid "To learn more, see our [dedicated Ansible documentation page](ansible.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:83
+msgid "What is `just`?"
+msgstr ""
+
+#: ../../../docs/faq.md:85
+msgid "[`just`](https://github.com/casey/just) is a modern command-runner alternative to [make](https://www.gnu.org/software/make/). It can be used to invoke commands with less typing."
+msgstr ""
+
+#: ../../../docs/faq.md:87
+msgid "The `just` utility executes shortcut commands (called \"recipes\"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile)."
+msgstr ""
+
+#: ../../../docs/faq.md:89
+msgid "For details about `just` commands, take a look at: [Running `just` commands](just.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:91
+msgid "The playbook also contains a `Makefile` for the `make` tool, but most of the just recipes are not available as targets in the `Makefile`."
+msgstr ""
+
+#: ../../../docs/faq.md:93
+msgid "Why use this playbook and not install Synapse and other things manually?"
+msgstr ""
+
+#: ../../../docs/faq.md:95
+msgid "There are various guides telling you how easy it is to install [Synapse](https://github.com/element-hq/synapse)."
+msgstr ""
+
+#: ../../../docs/faq.md:97
+msgid "Reading the documentation of this Ansible playbook, you may also be thinking:"
+msgstr ""
+
+#: ../../../docs/faq.md:99
+msgid "I don't know what [Ansible](https://www.ansible.com/) is. I don't know what [Docker](https://www.docker.com/) is. This looks more complicated."
+msgstr ""
+
+#: ../../../docs/faq.md:101
+msgid ".. so you may be leaning toward [installing Synapse manually](https://github.com/element-hq/synapse/blob/master/INSTALL.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:103
+msgid "The problem with a manual installation is:"
+msgstr ""
+
+#: ../../../docs/faq.md:105
+msgid "Synapse is written in Python. If not packaged for your distribution, you'd need to install various Python modules, etc., and keep them updated."
+msgstr ""
+
+#: ../../../docs/faq.md:106
+msgid "Synapse requires a [Postgres](https://www.postgresql.org/) database (it can run on SQLite, but that's very much discouraged). So you'd need to install Postgres as well."
+msgstr ""
+
+#: ../../../docs/faq.md:107
+msgid "you may also need a reverse-proxy server in front of it (nginx, Apache), so you'd need to be familiar with that"
+msgstr ""
+
+#: ../../../docs/faq.md:108
+msgid "SSL is required, so you'd need to obtain Let's Encrypt (or other free or non-free) certificates for one or more domain names. You'd need to be familiar with [certbot](https://certbot.eff.org/) (when using Let's Encrypt) or similar software."
+msgstr ""
+
+#: ../../../docs/faq.md:109
+msgid "for each additional component you'd like to add (client like [Element](https://element.io), bridge to some other chat network, integration manager (stickers, other services, Identity Manager, etc.), you'll need to spend extra time installing and wiring it with the rest of the system in a way that works."
+msgstr ""
+
+#: ../../../docs/faq.md:110
+msgid "you'll likely get slower updates for all of these components, depending on your distro packaging or your own time and ability"
+msgstr ""
+
+#: ../../../docs/faq.md:112
+msgid "The playbook, on the other hand, installs a bunch of components for you by default, obtains SSL certificates for you, etc. If you'd like, you can enable various bridges and other services with very little effort. All the components are wired to work together."
+msgstr ""
+
+#: ../../../docs/faq.md:114
+msgid "All services run in Docker containers (most being officially provided by each component's developers), so we're not at the mercy of distro packaging."
+msgstr ""
+
+#: ../../../docs/faq.md:116
+msgid "Why use this playbook and not just use the Docker image directly?"
+msgstr ""
+
+#: ../../../docs/faq.md:118
+msgid "Reasons are similar to the reasons for not installing manually."
+msgstr ""
+
+#: ../../../docs/faq.md:120
+msgid "Besides Synapse, you'd need other things - a Postgres database, likely the [Element](https://element.io) client, etc., etc."
+msgstr ""
+
+#: ../../../docs/faq.md:122
+msgid "Using the playbook, you get all these components in a way that works well together out of the box."
+msgstr ""
+
+#: ../../../docs/faq.md:124
+msgid "Occasionally I see some people are talking about \"MDAD\". What is it?"
+msgstr ""
+
+#: ../../../docs/faq.md:126
+msgid "It is the acronym of us: **m**atrix-**d**ocker-**a**nsible-**d**eploy."
+msgstr ""
+
+#: ../../../docs/faq.md:128
+msgid "What's different about this Ansible playbook compared to [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy)?"
+msgstr ""
+
+#: ../../../docs/faq.md:130
+msgid "This is similar to the [EMnify/matrix-synapse-auto-deploy](https://github.com/EMnify/matrix-synapse-auto-deploy) Ansible deployment, but:"
+msgstr ""
+
+#: ../../../docs/faq.md:132
+msgid "this one is a complete Ansible playbook (instead of just a role), so it's **easier to run** - especially for folks not familiar with Ansible"
+msgstr ""
+
+#: ../../../docs/faq.md:134
+msgid "this one installs and hooks together **a lot more Matrix-related services** for you (see above)"
+msgstr ""
+
+#: ../../../docs/faq.md:136
+msgid "this one **can be executed more than once** without causing trouble"
+msgstr ""
+
+#: ../../../docs/faq.md:138
+msgid "works on various distros: **CentOS** (7.0+), Debian-based distributions (**Debian** 10/Buster+, **Ubuntu** 18.04+), **Archlinux**"
+msgstr ""
+
+#: ../../../docs/faq.md:140
+msgid "this one installs everything in a single directory (`/matrix` by default) and **doesn't \"contaminate\" your server** with files all over the place"
+msgstr ""
+
+#: ../../../docs/faq.md:142
+msgid "this one **doesn't necessarily take over** ports 80 and 443. By default, it sets up [Traefik](https://doc.traefik.io/traefik/) for you there, but you can also [use your own webserver](configuring-playbook-own-webserver.md)"
+msgstr ""
+
+#: ../../../docs/faq.md:144
+msgid "this one **runs everything in Docker containers**, so it's likely more predictable and less fragile (see [Docker images used by this playbook](container-images.md))"
+msgstr ""
+
+#: ../../../docs/faq.md:146
+msgid "this one retrieves and automatically renews free [Let's Encrypt](https://letsencrypt.org/) **SSL certificates** for you"
+msgstr ""
+
+#: ../../../docs/faq.md:148
+msgid "this one optionally can store the `media_store` content repository files on [Amazon S3](https://aws.amazon.com/s3/) (but defaults to storing files on the server's filesystem)"
+msgstr ""
+
+#: ../../../docs/faq.md:150
+msgid "this one optionally **allows you to use an external PostgreSQL server** for Synapse's database (but defaults to running one in a container)"
+msgstr ""
+
+#: ../../../docs/faq.md:152
+msgid "helps you **import data from a previous installation** (so you can migrate your manual virtualenv/Docker setup to a more managed one)"
+msgstr ""
+
+#: ../../../docs/faq.md:154
+msgid "this one is actually **maintained**"
+msgstr ""
+
+#: ../../../docs/faq.md:156
+msgid "Server-related"
+msgstr ""
+
+#: ../../../docs/faq.md:158
+msgid "What kind of server do I need to install Matrix using this Ansible playbook?"
+msgstr ""
+
+#: ../../../docs/faq.md:160
+msgid "We list our server requirements in [Prerequisites](prerequisites.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:162
+msgid "Why not run Matrix on Kubernetes?"
+msgstr ""
+
+#: ../../../docs/faq.md:164
+msgid "There's no reason not to run Matrix on [Kubernetes](https://kubernetes.io/)."
+msgstr ""
+
+#: ../../../docs/faq.md:166
+msgid "However, that's overly complicated for thousands of us who just want to run a single small (and sometimes not so small) Matrix server, either using \"cloud\" servers or even a [Raspberry Pi](https://www.raspberrypi.org/) at home."
+msgstr ""
+
+#: ../../../docs/faq.md:168
+msgid "For us, a Kubernetes-based setup which requires a cluster of multiple computers and is more technically-involved is a no-go."
+msgstr ""
+
+#: ../../../docs/faq.md:170
+msgid "There are others working on automating a Matrix-on-Kubernetes setup, such as this [Helm](https://helm.sh/) chart: https://github.com/dacruz21/matrix-chart."
+msgstr ""
+
+#: ../../../docs/faq.md:172
+msgid "Why don't you use Podman instead of Docker?"
+msgstr ""
+
+#: ../../../docs/faq.md:174
+msgid "We like the philosophy of a daemonless container runtime, but [Podman](https://podman.io) is just not ready for our use case yet."
+msgstr ""
+
+#: ../../../docs/faq.md:176
+msgid "Learn more about our past experiences/attempts to give Podman a chance, by reading [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/520)."
+msgstr ""
+
+#: ../../../docs/faq.md:178
+msgid "In short, `alias podman=docker` is a lie (for us)."
+msgstr ""
+
+#: ../../../docs/faq.md:180
+msgid "Why use Docker?"
+msgstr ""
+
+#: ../../../docs/faq.md:182
+msgid "[Docker](https://www.docker.com/) is one of our 2 hard dependencies (the other one being [systemd](https://systemd.io/))."
+msgstr ""
+
+#: ../../../docs/faq.md:184
+msgid "It lets us run services in an isolated manner and independently of the (usually old) packages available for distributions."
+msgstr ""
+
+#: ../../../docs/faq.md:186
+msgid "It also lets us have a unified setup which runs the same across various supported distros (see them on [Prerequisites](prerequisites.md))."
+msgstr ""
+
+#: ../../../docs/faq.md:188
+msgid "Is Docker a hard requirement?"
+msgstr ""
+
+#: ../../../docs/faq.md:190
+msgid "Yes. See [Why don't you use Podman instead of Docker?](#why-dont-you-use-podman-instead-of-docker) for why we're not using another container runtime."
+msgstr ""
+
+#: ../../../docs/faq.md:192
+msgid "All of our services run in containers. It's how we achieve predictability and also how we support tens of different services across lots of distros."
+msgstr ""
+
+#: ../../../docs/faq.md:194
+msgid "The only thing we need on the distro is systemd and Python (we install Docker ourselves, unless you ask us not to)."
+msgstr ""
+
+#: ../../../docs/faq.md:196
+msgid "Why don't you use docker-compose?"
+msgstr ""
+
+#: ../../../docs/faq.md:198
+msgid "Instead of using [docker-compose](https://docs.docker.com/compose/), we prefer installing systemd services and scheduling those independently."
+msgstr ""
+
+#: ../../../docs/faq.md:200
+msgid "There are people who have worked on turning this setup into a docker-compose-based one. See these experiments [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/64#issuecomment-603164625). There is also a demo project ([element-docker-demo](https://github.com/element-hq/element-docker-demo)) by Element."
+msgstr ""
+
+#: ../../../docs/faq.md:202
+msgid "Can I run this on a distro without systemd?"
+msgstr ""
+
+#: ../../../docs/faq.md:204
+msgid "No. [systemd](https://systemd.io/) is one of our 2 hard dependencies (the other one being [Docker](https://www.docker.com/))."
+msgstr ""
+
+#: ../../../docs/faq.md:206
+msgid "Can I install this on a Raspberry Pi?"
+msgstr ""
+
+#: ../../../docs/faq.md:208
+msgid "Yes, you can. See our [Alternative Architectures](alternative-architectures.md) documentation page."
+msgstr ""
+
+#: ../../../docs/faq.md:210
+msgid "Whether a Raspberry Pi has enough power to give you a good experience is another question. It depends on your use case."
+msgstr ""
+
+#: ../../../docs/faq.md:212
+msgid "Also see: [What kind of server specs do I need?](#what-kind-of-server-specs-do-i-need)."
+msgstr ""
+
+#: ../../../docs/faq.md:214
+msgid "What kind of server specs do I need?"
+msgstr ""
+
+#: ../../../docs/faq.md:216
+msgid "This largely depends on your use case. It's not so much the number of users that you plan to host, but rather the number of large rooms they will join."
+msgstr ""
+
+#: ../../../docs/faq.md:218
+msgid "Federated rooms with lots of history and containing hundreds of other servers are very heavy CPU-wise and memory-wise."
+msgstr ""
+
+#: ../../../docs/faq.md:220
+msgid "You can probably use a 1 CPU + 1GB memory server to host hundreds of local users just fine, but as soon as one of them joins a federated room like `#matrix:matrix.org` (Matrix HQ) or some IRC-bridged room (say `##linux`), your server will get the need for a lot more power (at least 2GB RAM, etc)."
+msgstr ""
+
+#: ../../../docs/faq.md:222
+msgid "Running Matrix on a server with 1GB of memory is possible (especially if you disable some not-so-important services). See [How do I optimize this setup for a low-power server?](#how-do-i-optimize-this-setup-for-a-low-power-server)."
+msgstr ""
+
+#: ../../../docs/faq.md:224
+msgid "**We recommend starting with a server having at least 2GB of memory** and even then using it sparingly. If you know for sure you'll be joining various large rooms, etc., then going for 4GB of memory or more is a good idea."
+msgstr ""
+
+#: ../../../docs/faq.md:226
+msgid "Besides the regular Matrix stuff, we also support things like video-conferencing using [Jitsi](configuring-playbook-jitsi.md) and other additional services which (when installed) may use up a lot of memory. Things do add up. Besides the Synapse Matrix server, Jitsi is especially notorious for consuming a lot of resources. If you plan on running Jitsi, we recommend a server with at least 2GB of memory (preferrably more). See our [Jitsi documentation page](configuring-playbook-jitsi.md) to learn how to optimize its memory/CPU usage."
+msgstr ""
+
+#: ../../../docs/faq.md:228
+msgid "Can I run this in an LXC container?"
+msgstr ""
+
+#: ../../../docs/faq.md:230
+msgid "If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container."
+msgstr ""
+
+#: ../../../docs/faq.md:232
+msgid "Configuration"
+msgstr ""
+
+#: ../../../docs/faq.md:234
+msgid "Why install my server at matrix.example.com and not at the base domain?"
+msgstr ""
+
+#: ../../../docs/faq.md:236
+msgid "It's the same with email servers. Your email address is likely `name@company.com`, not `name@mail.company.com`, even though it's `mail.company.com` that is really handling your data for `@company.com` email to work."
+msgstr ""
+
+#: ../../../docs/faq.md:238
+msgid "Using a separate domain name is easier to manage (although it's a little hard to get right at first) and keeps your Matrix server isolated from your website (if you have one), from your email server (if you have one), etc. Therefore, this playbook sets up services on your Matrix server (`matrix.example.com`) by default."
+msgstr ""
+
+#: ../../../docs/faq.md:240
+msgid "I don't control anything on the base domain and can't set up delegation to matrix.example.com. What do I do?"
+msgstr ""
+
+#: ../../../docs/faq.md:242
+msgid "If you're not in control of your base domain (or the server handling it) at all, you can take a look at [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:244
+msgid "I can't set up HTTPS on the base domain. How will I get Matrix federating?"
+msgstr ""
+
+#: ../../../docs/faq.md:246
+msgid "If you really can't obtain an HTTPS certificate for your base domain, you can take a look at [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:248
+msgid "How do I install on matrix.example.com without involving the base domain?"
+msgstr ""
+
+#: ../../../docs/faq.md:250
+msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/faq.md:271
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/faq.md:278
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/faq.md:280
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/faq.md:282
+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/faq.md:284
+msgid "Without setting up [server delegation](howto-server-delegation.md) to `matrix.example.com`, your user IDs will be like `@alice:matrix.example.com`. This is equivalent to having an email address like `bob@mail.company.com`, instead of just `bob@company.com`."
+msgstr ""
+
+#: ../../../docs/faq.md:286
+msgid "I don't use the base domain for anything. How am I supposed to set up Server Delegation for Matrix services?"
+msgstr ""
+
+#: ../../../docs/faq.md:288
+msgid "If you don't use your base domain for anything, then it's hard for you to \"serve files over HTTPS\" on it -- something we ask you to do for the [.well-known](configuring-well-known.md) setup (needed for [Server Delegation](howto-server-delegation.md))."
+msgstr ""
+
+#: ../../../docs/faq.md:290
+msgid "Luckily, the playbook can set up your Matrix server (at `matrix.example.com`) to also handle traffic for the base domain (`example.com`)."
+msgstr ""
+
+#: ../../../docs/faq.md:292
+msgid "See [Serving the base domain](configuring-playbook-base-domain-serving.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:294
+msgid "How do I optimize this setup for a low-power server?"
+msgstr ""
+
+#: ../../../docs/faq.md:296
+msgid "You can disable some not-so-important services to save on memory."
+msgstr ""
+
+#: ../../../docs/faq.md:318
+msgid "You can also consider implementing a restriction on room complexity, in order to prevent users from joining very heavy rooms:"
+msgstr ""
+
+#: ../../../docs/faq.md:328
+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:330
+msgid "I already have Docker on my server. Can you stop installing Docker via the playbook?"
+msgstr ""
+
+#: ../../../docs/faq.md:332
+msgid "Yes, we can stop installing Docker ourselves. Just use this in your `vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/faq.md:338
+msgid "I run another webserver on the same server where I wish to install Matrix. What now?"
+msgstr ""
+
+#: ../../../docs/faq.md:340
+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:342
+msgid "How is the effective configuration determined?"
+msgstr ""
+
+#: ../../../docs/faq.md:344
+msgid "Configuration variables are defined in multiple places in this playbook and are considered in this order:"
+msgstr ""
+
+#: ../../../docs/faq.md:346
+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:348
+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:350
+msgid "finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` file, which is the ultimate override"
+msgstr ""
+
+#: ../../../docs/faq.md:352
+msgid "What configuration variables are available?"
+msgstr ""
+
+#: ../../../docs/faq.md:354
+msgid "You can discover the variables you can override in each role (`roles/*/*/defaults/main.yml`)."
+msgstr ""
+
+#: ../../../docs/faq.md:356
+msgid "As described in [How is the effective configuration determined?](#how-is-the-effective-configuration-determined), these role-defaults may be overriden by values defined in `group_vars/matrix_servers`."
+msgstr ""
+
+#: ../../../docs/faq.md:358
+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:360
+#: ../../../docs/faq.md:372
+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:362
+msgid "I'd like to adjust some configuration which doesn't have a corresponding variable. How do I do it?"
+msgstr ""
+
+#: ../../../docs/faq.md:364
+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:366
+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:368
+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:370
+msgid "Check each role's `roles/*/*/defaults/main.yml` for the corresponding variable and an example for how use it."
+msgstr ""
+
+#: ../../../docs/faq.md:374
+msgid "Installation"
+msgstr ""
+
+#: ../../../docs/faq.md:376
+msgid "How do I run the installation?"
+msgstr ""
+
+#: ../../../docs/faq.md:378
+msgid "See [Installing](installing.md) to learn how to use Ansible to install Matrix services."
+msgstr ""
+
+#: ../../../docs/faq.md:380
+msgid "However, we recommend you to follow our installation guide, instead of jumping straight to installing."
+msgstr ""
+
+#: ../../../docs/faq.md:382
+msgid "There are two guides available:"
+msgstr ""
+
+#: ../../../docs/faq.md:384
+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:386
+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:388
+msgid "I installed Synapse some other way. Can I migrate such a setup to the playbook?"
+msgstr ""
+
+#: ../../../docs/faq.md:390
+msgid "Yes, you can."
+msgstr ""
+
+#: ../../../docs/faq.md:392
+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:394
+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:396
+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:398
+msgid "I've downloaded Ansible and the playbook on the server. It can't connect using SSH."
+msgstr ""
+
+#: ../../../docs/faq.md:400
+msgid "If you're using the playbook directly on the server, then Ansible doesn't need to connect using SSH."
+msgstr ""
+
+#: ../../../docs/faq.md:402
+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:404
+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:406
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/faq.md:408
+msgid "I get \"Error response from daemon: configured logging driver does not support reading\" when I do `docker logs matrix-synapse`."
+msgstr ""
+
+#: ../../../docs/faq.md:410
+msgid "See [How can I see the logs?](#how-can-i-see-the-logs)."
+msgstr ""
+
+#: ../../../docs/faq.md:412
+msgid "How can I see the logs?"
+msgstr ""
+
+#: ../../../docs/faq.md:414
+msgid "We utilize [systemd/journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html#Description) for logging."
+msgstr ""
+
+#: ../../../docs/faq.md:416
+msgid "To see logs for Synapse, run `journalctl -fu matrix-synapse.service`. You may wish to see the [manual page for journalctl](https://www.commandlinux.com/man-page/man1/journalctl.1.html)."
+msgstr ""
+
+#: ../../../docs/faq.md:418
+msgid "Available service names can be seen by doing `ls /etc/systemd/system/matrix*.service` on the server."
+msgstr ""
+
+#: ../../../docs/faq.md:420
+msgid "Some services also log to files in `/matrix/*/data/..`, but we're slowly moving away from that."
+msgstr ""
+
+#: ../../../docs/faq.md:422
+msgid "We also disable Docker logging, so you can't use `docker logs matrix-*` either. We do this to prevent useless double (or even triple) logging and to avoid having to rotate log files."
+msgstr ""
+
+#: ../../../docs/faq.md:424
+msgid "We just simply delegate logging to journald and it takes care of persistence and expiring old data."
+msgstr ""
+
+#: ../../../docs/faq.md:426
+msgid "Also see: [How long do systemd/journald logs persist for?](#how-long-do-systemdjournald-logs-persist-for)"
+msgstr ""
+
+#: ../../../docs/faq.md:428
+msgid "How long do systemd/journald logs persist for?"
+msgstr ""
+
+#: ../../../docs/faq.md:430
+msgid "On some distros, the journald logs are just in-memory and not persisted to disk."
+msgstr ""
+
+#: ../../../docs/faq.md:432
+msgid "Consult (and feel free to adjust) your distro's journald logging configuration in `/etc/systemd/journald.conf`."
+msgstr ""
+
+#: ../../../docs/faq.md:434
+msgid "To enable persistence and put some limits on how large the journal log files can become, adjust your configuration like this:"
+msgstr ""
+
+#: ../../../docs/faq.md:445
+msgid "Maintenance"
+msgstr ""
+
+#: ../../../docs/faq.md:447
+msgid "Do I need to do anything to keep my Matrix server updated?"
+msgstr ""
+
+#: ../../../docs/faq.md:449
+msgid "Yes. We don't update anything for you automatically."
+msgstr ""
+
+#: ../../../docs/faq.md:451
+msgid "See our [documentation page about upgrading services](maintenance-upgrading-services.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:453
+msgid "How do I move my existing installation to another (VM) server?"
+msgstr ""
+
+#: ../../../docs/faq.md:455
+msgid "If you have an existing installation done using this Ansible playbook, you can easily migrate that to another server using [our dedicated server migration guide](maintenance-migrating.md)."
+msgstr ""
+
+#: ../../../docs/faq.md:457
+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:459
+msgid "How do I back up the data on my server?"
+msgstr ""
+
+#: ../../../docs/faq.md:461
+msgid "We haven't documented this properly yet, but the general advice is to:"
+msgstr ""
+
+#: ../../../docs/faq.md:463
+msgid "back up Postgres by making a database dump. See [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql)"
+msgstr ""
+
+#: ../../../docs/faq.md:465
+msgid "back up all `/matrix` files, except for `/matrix/postgres/data` (you already have a dump) and `/matrix/postgres/data-auto-upgrade-backup` (this directory may exist and contain your old data if you've [performed a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql))."
+msgstr ""
+
+#: ../../../docs/faq.md:467
+msgid "You can later restore these by:"
+msgstr ""
+
+#: ../../../docs/faq.md:469
+msgid "Restoring the `/matrix` directory and files on the new server manually"
+msgstr ""
+
+#: ../../../docs/faq.md:470
+msgid "Following the instruction described on [Installing a server into which you'll import old data](installing.md#installing-a-server-into-which-youll-import-old-data)"
+msgstr ""
+
+#: ../../../docs/faq.md:472
+msgid "If your server's IP address has changed, you may need to [set up DNS](configuring-dns.md) again."
+msgstr ""
+
+#: ../../../docs/faq.md:474
+msgid "What is this `/matrix/postgres/data-auto-upgrade-backup` directory that is taking up so much space?"
+msgstr ""
+
+#: ../../../docs/faq.md:476
+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:478
+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:480
+msgid "How do I debug or force SSL certificate renewal?"
+msgstr ""
+
+#: ../../../docs/faq.md:482
+msgid "SSL certificates are managed automatically by the [Traefik](https://doc.traefik.io/traefik/) reverse-proxy server."
+msgstr ""
+
+#: ../../../docs/faq.md:484
+msgid "If you're having trouble with SSL certificate renewal, check the Traefik logs (`journalctl -fu matrix-traefik`)."
+msgstr ""
+
+#: ../../../docs/faq.md:486
+msgid "If you're [using your own webserver](configuring-playbook-own-webserver.md) instead of the integrated one (Traefik), you should investigate in another way."
+msgstr ""
diff --git a/i18n/translation-templates/docs/getting-the-playbook.pot b/i18n/translation-templates/docs/getting-the-playbook.pot
new file mode 100644
index 000000000..e931dc6d9
--- /dev/null
+++ b/i18n/translation-templates/docs/getting-the-playbook.pot
@@ -0,0 +1,81 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/getting-the-playbook.md:1
+msgid "Getting the playbook"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:3
+msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > Getting the playbook > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)</sup>"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:5
+msgid "This Ansible playbook is meant to be executed on your own computer (not the Matrix server)."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:7
+msgid "In special cases (if your computer cannot run Ansible, etc.) you may put the playbook on the server as well."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:9
+msgid "You can retrieve the playbook's source code by:"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:11
+msgid "[Using git to get the playbook](#using-git-to-get-the-playbook) (recommended)"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:13
+msgid "[Downloading the playbook as a ZIP archive](#downloading-the-playbook-as-a-zip-archive) (not recommended)"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:15
+msgid "Using git to get the playbook"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:17
+msgid "We recommend using the [git](https://git-scm.com/) tool to get the playbook's source code, because it lets you easily keep up to date in the future when [Maintaining services](maintenance-upgrading-services.md)."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:19
+msgid "Once you've installed git on your computer, you can go to any directory of your choosing and run the following command to retrieve the playbook's source code:"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:25
+msgid "This will create a new `matrix-docker-ansible-deploy` directory. You're supposed to execute all other installation commands inside that directory."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:27
+msgid "Downloading the playbook as a ZIP archive"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:29
+msgid "Alternatively, you can download the playbook as a ZIP archive. This is not recommended, as it's not easy to keep up to date with future updates. We suggest you [use git](#using-git-to-get-the-playbook) instead."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:31
+msgid "The latest version is always at the following URL: https://github.com/spantaleev/matrix-docker-ansible-deploy/archive/master.zip"
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:33
+msgid "You can extract this archive anywhere. You'll get a directory called `matrix-docker-ansible-deploy-master`. You're supposed to execute all other installation commands inside that directory."
+msgstr ""
+
+#: ../../../docs/getting-the-playbook.md:37
+msgid "[▶️](configuring-playbook.md) No matter which method you've used to download the playbook, you can proceed by [Configuring the playbook](configuring-playbook.md)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/howto-server-delegation.pot b/i18n/translation-templates/docs/howto-server-delegation.pot
new file mode 100644
index 000000000..735e493f0
--- /dev/null
+++ b/i18n/translation-templates/docs/howto-server-delegation.pot
@@ -0,0 +1,185 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-23 13:09+0900\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/howto-server-delegation.md:1
+msgid "Server Delegation"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:3
+msgid "By default, this playbook sets up services on your Matrix server (`matrix.example.com`). To have this server officially be responsible for Matrix services for the base domain (`example.com`), you need to set up server delegation / redirection."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:5
+msgid "Server delegation can be configured in either of these ways:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:7
+msgid "[Setting up a `/.well-known/matrix/server` file](#server-delegation-via-a-well-known-file) on the base domain (`example.com`)"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:8
+msgid "[Setting up a `_matrix._tcp` DNS SRV record](#server-delegation-via-a-dns-srv-record-advanced)"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:10
+msgid "Both methods have their place and will continue to do so. You only need to use just one of these delegation methods."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:12
+msgid "For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file. However, that method may have some downsides that are not to your liking. Hence this guide about alternative ways to set up Server Delegation."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:14
+msgid "**Note**: as an alternative, it is possible to install the server such that it uses only the `matrix.example.com` domain (instead of identifying as the shorter base domain - `example.com`). This should be helpful if you are not in control of anything on the base domain (`example.com`). In this case, you would not need to configure server delegation, but you would need to add other configuration. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:16
+msgid "Server Delegation via a well-known file"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:18
+msgid "This playbook recommends you to set up server delegation by means of a `/.well-known/matrix/server` file served from the base domain (`example.com`), as this is the most straightforward way to set up the delegation."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:20
+msgid "To configure server delegation with the well-known file, check this section on [Configuring Service Discovery via .well-known](configuring-well-known.md): [Installing well-known files on the base domain's server](configuring-well-known.md#installing-well-known-files-on-the-base-domain-s-server)"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:22
+msgid "Downsides of well-known-based Server Delegation"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:24
+msgid "Server Delegation by means of a `/.well-known/matrix/server` file is the most straightforward, but suffers from the following downsides:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:26
+msgid "you need to have a working HTTPS server for the base domain (`example.com`). If you don't have any server for the base domain at all, you can easily solve it by making the playbook [serve the base domain from the Matrix server](configuring-playbook-base-domain-serving.md)."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:28
+msgid "any downtime on the base domain (`example.com`) or network trouble between the Matrix subdomain (`matrix.example.com`) and the base `example.com` may cause Matrix Federation outages. As the [Server-Server spec says](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery):"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:30
+msgid "Errors are recommended to be cached for up to an hour, and servers are encouraged to exponentially back off for repeated failures."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:32
+msgid "**For most people, this is a reasonable tradeoff** given that it's easy and straightforward to set up. We recommend you stay on this path."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:34
+msgid "Otherwise, you can decide to go against the default for this playbook, and instead set up [Server Delegation via a DNS SRV record (advanced)](#server-delegation-via-a-dns-srv-record-advanced) (much more complicated)."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:36
+msgid "Server Delegation via a DNS SRV record (advanced)"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:38
+msgid "**Note**: doing Server Delegation via a DNS SRV record is a more **advanced** way to do it and is not the default for this playbook. This is usually **much more complicated** to set up, so **we don't recommend it**. If you're not an experienced sysadmin, you'd better stay away from this."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:40
+msgid "As per the [Server-Server spec](https://matrix.org/docs/spec/server_server/r0.1.0.html#server-discovery), it's possible to do Server Delegation using only a SRV record (without a `/.well-known/matrix/server` file)."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:42
+msgid "This prevents you from suffering the [Downsides of well-known-based Server Delegation](#downsides-of-well-known-based-server-delegation)."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:44
+msgid "To use DNS SRV record validation, you need to:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:46
+msgid "ensure that `/.well-known/matrix/server` is **not served** from the base domain, as that would interfere with DNS SRV record Server Delegation. To make the playbook **not** generate and serve the file, use the following configuration: `matrix_static_files_file_matrix_server_enabled: false`."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:48
+msgid "ensure that you have a `_matrix._tcp` DNS SRV record for your base domain (`example.com`) with a value of `10 0 8448 matrix.example.com`"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:50
+msgid "ensure that you are serving the Matrix Federation API (tcp/8448) with a certificate for `example.com` (not `matrix.example.com`!). Getting this certificate to the `matrix.example.com` server may be complicated. The playbook's automatic SSL obtaining/renewal flow will likely not work and you'll need to copy certificates around manually. See below."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:52
+msgid "For more details on how to configure the playbook to work with SRV delegation, take a look at this documentation: [Server Delegation via a DNS SRV record (advanced)](howto-srv-server-delegation.md)"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:54
+msgid "Obtain certificates"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:56
+msgid "How you can obtain a valid certificate for `example.com` on the `matrix.example.com` server is up to you."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:58
+msgid "If `example.com` and `matrix.example.com` are hosted on the same machine, you can let the playbook obtain the certificate for you, by following our [Obtaining SSL certificates for additional domains](configuring-playbook-ssl-certificates.md#obtaining-ssl-certificates-for-additional-domains) guide."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:60
+msgid "If `example.com` and `matrix.example.com` are not hosted on the same machine, you can copy over the certificate files manually. Don't forget that they may get renewed once in a while, so you may also have to transfer them periodically. How often you do that is up to you, as long as the certificate files don't expire."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:62
+msgid "Serving the Federation API with your certificates"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:64
+msgid "Regardless of which method for obtaining certificates you've used, once you've managed to get certificates for your base domain onto the `matrix.example.com` machine you can put them to use."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:66
+msgid "Based on your setup, you have different ways to go about it:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:68
+msgid "Serving the Federation API with your certificates and Synapse handling Federation"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:70
+msgid "You can let Synapse handle Federation by itself."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:72
+msgid "To do that, make sure the certificate files are mounted into the Synapse container:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:79
+msgid "You can then tell Synapse to serve Federation traffic over TLS on `tcp/8448`:"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:87
+msgid "Make sure to reload Synapse once in a while (`systemctl reload matrix-synapse`), so that newer certificates can kick in. Reloading doesn't cause any downtime."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:89
+msgid "Serving the Federation API with your certificates and another webserver"
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:91
+msgid "**Alternatively**, if you are using another webserver, you can set up reverse-proxying for the `tcp/8448` port by yourself. Make sure to use the proper certificates for `example.com` (not for `matrix.example.com`) when serving the `tcp/8448` port."
+msgstr ""
+
+#: ../../../docs/howto-server-delegation.md:93
+msgid "As recommended in our [Fronting the integrated reverse-proxy webserver with another reverse-proxy](./configuring-playbook-own-webserver.md#fronting-the-integrated-reverse-proxy-webserver-with-another-reverse-proxy) documentation section, we recommend you to expose the Matrix Federation entrypoint from traffic at a local port (e.g. `127.0.0.1:8449`), so your reverese-proxy should send traffic there."
+msgstr ""
diff --git a/i18n/translation-templates/docs/howto-srv-server-delegation.pot b/i18n/translation-templates/docs/howto-srv-server-delegation.pot
new file mode 100644
index 000000000..a8f731254
--- /dev/null
+++ b/i18n/translation-templates/docs/howto-srv-server-delegation.pot
@@ -0,0 +1,145 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/howto-srv-server-delegation.md:1
+msgid "Server Delegation via a DNS SRV record (advanced)"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:3
+msgid "**Reminder** : unless you are affected by the [Downsides of well-known-based Server Delegation](howto-server-delegation.md#downsides-of-well-known-based-server-delegation), we suggest you **stay on the simple/default path**: [Server Delegation](howto-server-delegation.md) by [configuring well-known files](configuring-well-known.md) at the base domain."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:5
+msgid "This guide is about configuring Server Delegation using DNS SRV records (for the [Traefik](https://doc.traefik.io/traefik/) webserver). This method has special requirements when it comes to SSL certificates, so various changes are required."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:7
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:9
+msgid "SRV delegation while still using the playbook provided Traefik to get / renew the certificate requires a wildcard certificate."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:11
+msgid "To obtain / renew one from [Let's Encrypt](https://letsencrypt.org/), one needs to use a [DNS-01 challenge](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) method instead of the default [HTTP-01](https://letsencrypt.org/docs/challenge-types/#http-01-challenge)."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:13
+msgid "This means that this is **limited to the list of DNS providers supported by Traefik**, unless you bring in your own certificate."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:15
+msgid "The up-to-date list can be accessed on [traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers)"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:17
+msgid "The changes"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:19
+msgid "**Note**: the changes below instruct you how to do this for a basic Synapse installation. You will need to adapt the variable name and the content of the labels:"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:21
+msgid "if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md) or [Dendrite](./configuring-playbook-dendrite.md))"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:22
+msgid "if you're using [Synapse with workers enabled](./configuring-playbook-synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled: true`). In that case, it's actually the `matrix-synapse-reverse-proxy-companion` service which has Traefik labels attached"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:24
+msgid "Also, all instructions below are from an older version of the playbook and may not work anymore."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:26
+msgid "Federation Endpoint"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:33
+msgid "This is because with SRV federation, some servers / tools (one of which being the federation tester) try to access the federation API using the resolved IP address instead of the domain name (or they are not using SNI). This change will make Traefik route all traffic for which the path match this rule go to the federation endpoint."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:35
+msgid "Tell Traefik which certificate to serve for the federation endpoint"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:37
+msgid "Now that the federation endpoint is not bound to a domain anymore we need to explicitely tell Traefik to use a wildcard certificate in addition to one containing the base name."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:39
+msgid "This is because the Matrix specification expects the federation endpoint to be served using a certificate compatible with the base domain, however, the other resources on the endpoint still need a valid certificate to work."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:48
+msgid "Configure the DNS-01 challenge for let's encrypt"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:50
+msgid "Since we're now requesting a wildcard certificate, we need to change the ACME challenge method. To request a wildcard certificate from Let's Encrypt we are required to use the DNS-01 challenge."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:52
+msgid "This will need 3 changes:"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:53
+msgid "Add a new certificate resolver that works with DNS-01"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:54
+msgid "Configure the resolver to allow access to the DNS zone to configure the records to answer the challenge (refer to [Traefik's documentation](https://doc.traefik.io/traefik/https/acme/#providers) to know which environment variables to set)"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:55
+msgid "Tell the playbook to use the new resolver as default"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:57
+msgid "We cannot just disable the default resolver as that would disable SSL in quite a few places in the playbook."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:86
+msgid "Adjust Coturn's configuration"
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:88
+msgid "The last step is to alter the generated Coturn configuration."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:90
+msgid "By default, Coturn is configured to wait on the certificate for the `matrix.` subdomain using an [instantiated systemd service](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Service%20Templates) using the domain name as the parameter for this service. However, we need to serve the wildcard certificate, which is incompatible with systemd, it will try to expand the `*`, which will break and prevent Coturn from starting."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:92
+msgid "We also need to indicate to Coturn where the wildcard certificate is."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:94
+msgid "**⚠️ WARNING ⚠️** : On first start of the services, Coturn might still fail to start because Traefik is still in the process of obtaining the certificates. If you still get an error, make sure Traefik obtained the certificates and restart the Coturn service (`just start-group coturn`)."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:96
+msgid "This should not happen again afterwards as Traefik will renew certificates well before their expiry date, and the Coturn service is setup to restart periodically."
+msgstr ""
+
+#: ../../../docs/howto-srv-server-delegation.md:122
+msgid "Full example of a working configuration"
+msgstr ""
diff --git a/i18n/translation-templates/docs/importing-postgres.pot b/i18n/translation-templates/docs/importing-postgres.pot
new file mode 100644
index 000000000..3bb07e120
--- /dev/null
+++ b/i18n/translation-templates/docs/importing-postgres.pot
@@ -0,0 +1,145 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/importing-postgres.md:1
+msgid "Importing an existing Postgres database from another installation (optional)"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:3
+msgid "Run this if you'd like to import your database from a previous installation. (don't forget to import your Synapse `media_store` files as well - see [the importing-synape-media-store guide](importing-synapse-media-store.md))."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:6
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:8
+msgid "For this to work, **the database name in Postgres must match** what this playbook uses. This playbook uses a Postgres database name of `synapse` by default (controlled by the `matrix_synapse_database_database` variable). If your database name differs, be sure to change `matrix_synapse_database_database` to your desired name and to re-run the playbook before proceeding."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:10
+msgid "The playbook supports importing Postgres dump files in **text** (e.g. `pg_dump > dump.sql`) or **gzipped** formats (e.g. `pg_dump | gzip -c > dump.sql.gz`). Importing multiple databases (as dumped by `pg_dumpall`) is also supported."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:12
+msgid "The migration might be a good moment, to \"reset\" a not properly working bridge. Be aware, that it might affect all users (new link to bridge, new rooms, …)"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:14
+msgid "Before doing the actual import, **you need to upload your Postgres dump file to the server** (any path is okay)."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:16
+msgid "Importing"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:18
+msgid "To import, run this command (make sure to replace `SERVER_PATH_TO_POSTGRES_DUMP_FILE` with a file path on your server):"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:26
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:28
+msgid "`SERVER_PATH_TO_POSTGRES_DUMP_FILE` must be a file path to a Postgres dump file on the server (not on your local machine!)"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:29
+msgid "`postgres_default_import_database` defaults to `matrix`, which is useful for importing multiple databases (for dumps made with `pg_dumpall`). If you're importing a single database (e.g. `synapse`), consider changing `postgres_default_import_database` accordingly"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:30
+msgid "after importing a large database, it's a good idea to run [an `ANALYZE` operation](https://www.postgresql.org/docs/current/sql-analyze.html) to make Postgres rebuild its database statistics and optimize its query planner. You can easily do this via the playbook by running `just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze` (see [Vacuuming PostgreSQL](maintenance-postgres.md#vacuuming-postgresql) for more details)."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:32
+msgid "Troubleshooting"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:34
+msgid "Table Ownership"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:36
+msgid "A table ownership issue can occur if you are importing from a Synapse installation which was both:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:38
+msgid "migrated from SQLite to Postgres, and"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:39
+msgid "used a username other than 'synapse'"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:41
+msgid "In this case you may run into the following error during the import task:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:47
+msgid "where `synapse_user` is the database username from the previous Synapse installation."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:49
+msgid "This can be verified by examining the dump for ALTER TABLE statements which set OWNER TO that username:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:61
+msgid "It can be worked around by changing the username to `synapse`, for example by using `sed`:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:67
+msgid "This uses sed to perform an 'in-place' (`-i`) replacement globally (`/g`), searching for `synapse_user` and replacing with `synapse` (`s/synapse_user/synapse`). If your database username was different, change `synapse_user` to that username instead. Expand search/replace statement as shown in example above, in case of old user name like `matrix` - replacing `matrix` only would… well - you can imagine."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:69
+msgid "Note that if the previous import failed with an error it may have made changes which are incompatible with re-running the import task right away; if you do so it may fail with an error such as:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:75
+msgid "Repeat import"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:77
+msgid "In this case you can use the command suggested in the import task to clear the database before retrying the import:"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:85
+msgid "Now on your local machine run `just run-tags setup-postgres` to prepare the database roles etc."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:87
+msgid "If not, you probably get this error. `synapse` is the correct table owner, but the role is missing in database."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:93
+msgid "Once the database is clear and the ownership of the tables has been fixed in the SQL file, the import task should succeed."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:95
+msgid "Check, if `--dbname` is set to `synapse` (not `matrix`) and replace paths (or even better, copy this line from your terminal)"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:101
+msgid "Hints"
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:103
+msgid "To open psql terminal run `/matrix/postgres/bin/cli`"
+msgstr ""
diff --git a/i18n/translation-templates/docs/importing-synapse-media-store.pot b/i18n/translation-templates/docs/importing-synapse-media-store.pot
new file mode 100644
index 000000000..6bf3b4e9c
--- /dev/null
+++ b/i18n/translation-templates/docs/importing-synapse-media-store.pot
@@ -0,0 +1,57 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/importing-synapse-media-store.md:1
+msgid "Importing `media_store` data files from an existing Synapse installation (optional)"
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:3
+msgid "Run this if you'd like to import your `media_store` files from a previous installation of Synapse."
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:5
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:7
+msgid "Before doing the actual data restore, **you need to upload your media store directory to the server** (any path is okay)."
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:9
+msgid "If you are [storing Matrix media files on Amazon S3](configuring-playbook-s3.md) (optional), restoring with this tool is not possible right now."
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:11
+msgid "As an alternative, you can perform a manual restore using the [AWS CLI tool](https://aws.amazon.com/cli/) (e.g. `aws s3 sync /path/to/server/media_store/. s3://name-of-bucket/`)"
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:13
+msgid "**Note for Mac users**: Due to case-sensitivity issues on certain Mac filesystems (HFS or HFS+), filename corruption may occur if you copy a `media_store` directory to your Mac. If you're transferring a `media_store` directory between 2 servers, make sure you do it directly (from server to server with a tool such as [rsync](https://rsync.samba.org/)), and not by downloading the files to your Mac."
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:15
+msgid "Importing"
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:17
+msgid "Run this command (make sure to replace `<server-path-to-media_store>` with a path on your server):"
+msgstr ""
+
+#: ../../../docs/importing-synapse-media-store.md:23
+msgid "**Note**: `<server-path-to-media_store>` must be a file path to a `media_store` directory on the server (not on your local machine!)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/importing-synapse-sqlite.pot b/i18n/translation-templates/docs/importing-synapse-sqlite.pot
new file mode 100644
index 000000000..03ffd5cad
--- /dev/null
+++ b/i18n/translation-templates/docs/importing-synapse-sqlite.pot
@@ -0,0 +1,73 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/importing-synapse-sqlite.md:1
+msgid "Importing an existing SQLite database from another Synapse installation (optional)"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:3
+msgid "Run this if you'd like to import your database from a previous default installation of Synapse (don't forget to import your `media_store` files as well - see [the importing-synapse-media-store guide](importing-synapse-media-store.md))."
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:5
+msgid "While this playbook only supports running Synapse in combination with PostgreSQL, a Synapse instance installed manually usually defaults to using an SQLite database."
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:7
+msgid "If you have such a Synapse setup and wish to migrate it to one managed by the playbook (and over to PostgreSQL), this documentation page is for you."
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:9
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:11
+msgid "Before doing the actual import:"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:13
+msgid "**ensure you have NOT started Synapse yet**. That is, make sure you have followed the [Installing step](installing.md), but haven't run the playbook's `start` tag yet. If you had started your new Synapse instance, it may have already initialized your Postgres database and importing onto it may not work. In such cases, you may need to clean up the `synapse` database first."
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:14
+msgid "**ensure you have uploaded your SQLite database file to the server** (any path is okay)"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:15
+msgid "if you're using the integrated Postgres server (**by default, you are** using it, unless you've explicitly switched to [Using an external PostgreSQL server](configuring-playbook-external-postgres.md)), **make sure Postgres is started** by running `just start-group postgres`"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:17
+msgid "Importing"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:19
+msgid "Run this command (make sure to replace `<server-path-to-homeserver.db>` with a file path on your server):"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:25
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:27
+msgid "`<server-path-to-homeserver.db>` must be replaced with a file path to a `homeserver.db` **file on the server** (not on your local machine!)."
+msgstr ""
+
+#: ../../../docs/importing-synapse-sqlite.md:28
+msgid "if the SQLite database is from an older version of Synapse, the **importing procedure may run migrations on it to bring it up to date**. That is, your SQLite database file may get modified and become unusable with your older Synapse version. Keeping a copy of the original is probably wise."
+msgstr ""
diff --git a/i18n/translation-templates/docs/installing.pot b/i18n/translation-templates/docs/installing.pot
new file mode 100644
index 000000000..281020067
--- /dev/null
+++ b/i18n/translation-templates/docs/installing.pot
@@ -0,0 +1,301 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/installing.md:1
+msgid "Installing"
+msgstr ""
+
+#: ../../../docs/installing.md:3
+msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > Installing</sup>"
+msgstr ""
+
+#: ../../../docs/installing.md:5
+msgid "If you've configured your DNS records and the playbook, you can start the installation procedure."
+msgstr ""
+
+#: ../../../docs/installing.md:7
+msgid "Update Ansible roles"
+msgstr ""
+
+#: ../../../docs/installing.md:9
+msgid "Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside."
+msgstr ""
+
+#: ../../../docs/installing.md:11
+msgid "To update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file), run:"
+msgstr ""
+
+#: ../../../docs/installing.md:13
+msgid "either: `just update`"
+msgstr ""
+
+#: ../../../docs/installing.md:14
+msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)"
+msgstr ""
+
+#: ../../../docs/installing.md:16
+msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`"
+msgstr ""
+
+#: ../../../docs/installing.md:18
+msgid "For details about `just` commands, take a look at: [Running `just` commands](just.md)."
+msgstr ""
+
+#: ../../../docs/installing.md:20
+msgid "Install Matrix server and services"
+msgstr ""
+
+#: ../../../docs/installing.md:22
+msgid "The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks."
+msgstr ""
+
+#: ../../../docs/installing.md:24
+msgid "The general command syntax for installation (and also maintenance) is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`. It is recommended to get yourself familiar with the [playbook tags](playbook-tags.md) before proceeding."
+msgstr ""
+
+#: ../../../docs/installing.md:26
+msgid "If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the all Ansible commands."
+msgstr ""
+
+#: ../../../docs/installing.md:28
+msgid "If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to all Ansible commands."
+msgstr ""
+
+#: ../../../docs/installing.md:30
+msgid "There 2 ways to start the installation process - depending on whether you're [Installing a brand new server (without importing data)](#installing-a-brand-new-server-without-importing-data) or [Installing a server into which you'll import old data](#installing-a-server-into-which-youll-import-old-data)."
+msgstr ""
+
+#: ../../../docs/installing.md:32
+msgid "**Note**: if you are migrating from an old server to a new one, take a look at [this guide](maintenance-migrating.md) instead. This is an easier and more straightforward way than installing a server and importing old data into it."
+msgstr ""
+
+#: ../../../docs/installing.md:34
+msgid "Installing a brand new server (without importing data)"
+msgstr ""
+
+#: ../../../docs/installing.md:36
+msgid "If this is **a brand new** Matrix server and you **won't be importing old data into it**, run all these tags:"
+msgstr ""
+
+#: ../../../docs/installing.md:42
+msgid "This will do a full installation and start all Matrix services."
+msgstr ""
+
+#: ../../../docs/installing.md:44
+msgid "**Note**: if the command does not work as expected, make sure that you have properly installed and configured software required to run the playbook, as described on [Prerequisites](prerequisites.md)."
+msgstr ""
+
+#: ../../../docs/installing.md:46
+msgid "Installing a server into which you'll import old data"
+msgstr ""
+
+#: ../../../docs/installing.md:48
+msgid "If you will be importing data into your newly created Matrix server, install it, but **do not** start its services just yet. Starting its services or messing with its database now will affect your data import later on."
+msgstr ""
+
+#: ../../../docs/installing.md:50
+msgid "To do the installation **without** starting services, run `ansible-playbook` with the `install-all` tag only:"
+msgstr ""
+
+#: ../../../docs/installing.md:56
+msgid "⚠️ **Warning**: do not run the just \"recipe\" `just install-all` instead, because it automatically starts services at the end of execution. See: [Difference between playbook tags and shortcuts](just.md#difference-between-playbook-tags-and-shortcuts)"
+msgstr ""
+
+#: ../../../docs/installing.md:58
+msgid "When this command completes, services won't be running yet."
+msgstr ""
+
+#: ../../../docs/installing.md:60
+msgid "You can now:"
+msgstr ""
+
+#: ../../../docs/installing.md:62
+msgid "[Importing an existing SQLite database (from another Synapse installation)](importing-synapse-sqlite.md) (optional)"
+msgstr ""
+
+#: ../../../docs/installing.md:64
+msgid "[Importing an existing Postgres database (from another installation)](importing-postgres.md) (optional)"
+msgstr ""
+
+#: ../../../docs/installing.md:66
+msgid "[Importing `media_store` data files from an existing Synapse installation](importing-synapse-media-store.md) (optional)"
+msgstr ""
+
+#: ../../../docs/installing.md:68
+msgid ".. and then proceed to starting all services:"
+msgstr ""
+
+#: ../../../docs/installing.md:74
+msgid "Create your user account"
+msgstr ""
+
+#: ../../../docs/installing.md:76
+msgid "ℹ️ *You can skip this step if you have installed a server and imported old data to it.*"
+msgstr ""
+
+#: ../../../docs/installing.md:78
+msgid "As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server."
+msgstr ""
+
+#: ../../../docs/installing.md:80
+msgid "After creating the user account, you can log in to it with [Element Web](configuring-playbook-client-element-web.md) that this playbook has installed for you at this URL: `https://element.example.com/`."
+msgstr ""
+
+#: ../../../docs/installing.md:82
+msgid "To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer."
+msgstr ""
+
+#: ../../../docs/installing.md:84
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/installing.md:85
+msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`"
+msgstr ""
+
+#: ../../../docs/installing.md:86
+msgid "For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)"
+msgstr ""
+
+#: ../../../docs/installing.md:87
+msgid "Use `admin=yes` to make your user account an administrator of the Matrix server"
+msgstr ""
+
+#: ../../../docs/installing.md:95
+msgid "Feel free to create as many accounts (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your account only (with `admin=yes`), and others should be created with `admin=no`."
+msgstr ""
+
+#: ../../../docs/installing.md:97
+msgid "For more information, see the documentation for [registering users](registering-users.md)."
+msgstr ""
+
+#: ../../../docs/installing.md:99
+msgid "Finalize the installation"
+msgstr ""
+
+#: ../../../docs/installing.md:101
+msgid "Now you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network."
+msgstr ""
+
+#: ../../../docs/installing.md:103
+msgid "This is required for federation to work! Without a proper configuration, your server will effectively not be part of the Matrix network."
+msgstr ""
+
+#: ../../../docs/installing.md:105
+msgid "To configure the delegation, you have these two options. Choose one of them according to your situation."
+msgstr ""
+
+#: ../../../docs/installing.md:107
+msgid "If you can afford to point the base domain at the Matrix server, follow the instructions below which guide you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server. It will enable you to use a Matrix user ID like `@alice:example.com` while hosting services on a subdomain like `matrix.example.com`."
+msgstr ""
+
+#: ../../../docs/installing.md:108
+msgid "Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot \"serve the base domain\" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server), but feel free to familiarize yourself with all [server delegation (redirection) options](howto-server-delegation.md)."
+msgstr ""
+
+#: ../../../docs/installing.md:110
+msgid "To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/installing.md:116
+msgid "After configuring the playbook, run the command below:"
+msgstr ""
+
+#: ../../../docs/installing.md:122
+msgid "Things to do next"
+msgstr ""
+
+#: ../../../docs/installing.md:124
+msgid "After finilizing the installation, you can:"
+msgstr ""
+
+#: ../../../docs/installing.md:126
+msgid "[check if services work](maintenance-checking-services.md)"
+msgstr ""
+
+#: ../../../docs/installing.md:127
+msgid "or [set up additional services](configuring-playbook.md#other-configuration-options) (bridges to other chat networks, bots, etc.)"
+msgstr ""
+
+#: ../../../docs/installing.md:128
+msgid "or learn how to [upgrade services when new versions are released](maintenance-upgrading-services.md)"
+msgstr ""
+
+#: ../../../docs/installing.md:129
+msgid "or learn how to [maintain your server](faq.md#maintenance)"
+msgstr ""
+
+#: ../../../docs/installing.md:130
+msgid "or join some Matrix rooms:"
+msgstr ""
+
+#: ../../../docs/installing.md:131
+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."
+msgstr ""
+
+#: ../../../docs/installing.md:132
+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:133
+msgid "or help make this playbook better by contributing (code, documentation, or [coffee/beer](https://liberapay.com/s.pantaleev/donate))"
+msgstr ""
+
+#: ../../../docs/installing.md:135
+msgid "Maintaining your setup in the future"
+msgstr ""
+
+#: ../../../docs/installing.md:137
+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:139
+msgid "The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities."
+msgstr ""
+
+#: ../../../docs/installing.md:141
+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:143
+msgid "For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)"
+msgstr ""
+
+#: ../../../docs/installing.md:145
+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:151
+msgid "**Note**: see [this page on the playbook tags](playbook-tags.md) for more information about those tags."
+msgstr ""
+
+#: ../../../docs/installing.md:153
+msgid "Make full use of `just` shortcut commands"
+msgstr ""
+
+#: ../../../docs/installing.md:155
+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:157
+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:159
+msgid "You can learn about the shortcut commands on this page: [Running `just` commands](just.md)"
+msgstr ""
diff --git a/i18n/translation-templates/docs/just.pot b/i18n/translation-templates/docs/just.pot
new file mode 100644
index 000000000..20170310a
--- /dev/null
+++ b/i18n/translation-templates/docs/just.pot
@@ -0,0 +1,158 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/just.md:1
+msgid "Running `just` commands"
+msgstr ""
+
+#: ../../../docs/just.md:3
+msgid "We have previously used [make](https://www.gnu.org/software/make/) for easily running some playbook commands (e.g. `make roles` which triggers [`ansible-galaxy`](https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html)). Our [`Makefile`](../Makefile) is still around, and you can still run these commands."
+msgstr ""
+
+#: ../../../docs/just.md:5
+msgid "In addition, we have added support for running commands via [`just`](https://github.com/casey/just) - a more modern command-runner alternative to `make`. It can be used to invoke `ansible-playbook` commands with less typing."
+msgstr ""
+
+#: ../../../docs/just.md:7
+msgid "The `just` utility executes shortcut commands (called as \"recipes\"), which invoke `ansible-playbook`, `ansible-galaxy` or [`agru`](https://github.com/etkecc/agru) (depending on what is available in your system). The targets of the recipes are defined in [`justfile`](../justfile). Most of the just recipes have no corresponding `Makefile` targets."
+msgstr ""
+
+#: ../../../docs/just.md:9
+msgid "For some recipes such as `just update`, our `justfile` recommends installing [`agru`](https://github.com/etkecc/agru) (a faster alternative to `ansible-galaxy`) to speed up the process."
+msgstr ""
+
+#: ../../../docs/just.md:11
+msgid "Here are some examples of shortcuts:"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "Shortcut"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "Result"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "`just roles`"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "Install the necessary Ansible roles pinned in [`requirements.yml`](../requirements.yml)"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "`just update`"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "Run `git pull` (to update the playbook) and install the Ansible roles"
+msgstr ""
+
+#: ../../../docs/just.md:0
+#: ../../../docs/just.md:33
+msgid "`just install-all`"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=install-all,ensure-matrix-users-created,start`"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "`just setup-all`"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start`"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "`just install-all --ask-vault-pass`"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "Run commands with additional arguments (`--ask-vault-pass` will be appended to the above installation command)"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "`just run-tags install-mautrix-slack,start`"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "Run specific playbook tags (here `install-mautrix-slack` and `start`)"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "`just install-service mautrix-slack`"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "Run `just run-tags install-mautrix-slack,start` with even less typing"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "`just start-all`"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "(Re-)starts all services"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "`just stop-group postgres`"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "Stop only the Postgres service"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "`just register-user alice secret-password yes`"
+msgstr ""
+
+#: ../../../docs/just.md:0
+msgid "Registers an `alice` user with the `secret-password` password and admin access (admin = `yes`)"
+msgstr ""
+
+#: ../../../docs/just.md:26
+msgid "While [our documentation on prerequisites](prerequisites.md) lists `just` as one of the requirements for installation, using `just` is optional. If you find it difficult to install it, do not find it useful, or want to prefer raw `ansible-playbook` commands for some reason, feel free to run all commands manually. For example, you can run `ansible-galaxy` directly to install the Ansible roles: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`."
+msgstr ""
+
+#: ../../../docs/just.md:28
+msgid "Difference between playbook tags and shortcuts"
+msgstr ""
+
+#: ../../../docs/just.md:30
+msgid "It is worth noting that `just` \"recipes\" are different from [playbook tags](playbook-tags.md). The recipes are shortcuts of commands defined in `justfile` and can be executed by the `just` program only, while the playbook tags are available for the raw `ansible-playbook` commands as well. Please be careful not to confuse them."
+msgstr ""
+
+#: ../../../docs/just.md:32
+msgid "For example, these two commands are different:"
+msgstr ""
+
+#: ../../../docs/just.md:34
+msgid "`ansible-playbook -i inventory/hosts setup.yml --tags=install-all`"
+msgstr ""
+
+#: ../../../docs/just.md:36
+msgid "The just recipe runs `ensure-matrix-users-created` and `start` tags after `install-all`, while the latter runs only `install-all` tag. The correct shortcut of the latter is `just run-tags install-all`."
+msgstr ""
+
+#: ../../../docs/just.md:38
+msgid "Such kind of difference sometimes matters. For example, when you install a Matrix server into which you will import old data (see [here](installing.md#installing-a-server-into-which-youll-import-old-data)), you are not supposed to run `just install-all` or `just setup-all`, because these commands start services immediately after installing components which may prevent your from importing old data."
+msgstr ""
diff --git a/i18n/translation-templates/docs/maintenance-and-troubleshooting.pot b/i18n/translation-templates/docs/maintenance-and-troubleshooting.pot
new file mode 100644
index 000000000..c4bcccb55
--- /dev/null
+++ b/i18n/translation-templates/docs/maintenance-and-troubleshooting.pot
@@ -0,0 +1,89 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/maintenance-and-troubleshooting.md:1
+msgid "Maintenance and Troubleshooting"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:3
+msgid "How to see the current status of your services"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:5
+msgid "You can check the status of your services by using `systemctl status`. Example:"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:15
+msgid "Docker containers that the playbook configures are supervised by [systemd](https://wiki.archlinux.org/title/Systemd) and their logs are configured to go to [systemd-journald](https://wiki.archlinux.org/title/Systemd/Journal)."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:17
+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`."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:19
+msgid "To view systemd-journald logs using [journalctl](https://man.archlinux.org/man/journalctl.1), run a command like this:"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:25
+msgid "Increasing Synapse logging"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:27
+msgid "Because the [Synapse](https://github.com/element-hq/synapse) Matrix server 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/maintenance-and-troubleshooting.md:29
+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 increasing the logging level to `INFO`."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:31
+msgid "Example configuration (`inventory/host_vars/matrix.example.com/vars.yml`):"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:39
+msgid "Re-run the playbook after making these configuration changes."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:41
+msgid "Remove unused Docker data"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:43
+msgid "You can free some disk space from Docker, see [docker system prune](https://docs.docker.com/engine/reference/commandline/system_prune/) for more information."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:49
+msgid "The shortcut command with `just` program is also available: `just run-tags run-docker-prune`"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:51
+msgid "Postgres"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:53
+msgid "See the dedicated [PostgreSQL Maintenance](maintenance-postgres.md) documentation page."
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:55
+msgid "Ma1sd"
+msgstr ""
+
+#: ../../../docs/maintenance-and-troubleshooting.md:57
+msgid "See the dedicated [Adjusting ma1sd Identity Server configuration](configuring-playbook-ma1sd.md) documentation page."
+msgstr ""
diff --git a/i18n/translation-templates/docs/maintenance-checking-services.pot b/i18n/translation-templates/docs/maintenance-checking-services.pot
new file mode 100644
index 000000000..b42b1f143
--- /dev/null
+++ b/i18n/translation-templates/docs/maintenance-checking-services.pot
@@ -0,0 +1,41 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/maintenance-checking-services.md:1
+msgid "Checking if services work"
+msgstr ""
+
+#: ../../../docs/maintenance-checking-services.md:3
+msgid "This playbook can perform a check to ensure that you've configured things correctly and that services are running."
+msgstr ""
+
+#: ../../../docs/maintenance-checking-services.md:5
+msgid "To perform the check, run:"
+msgstr ""
+
+#: ../../../docs/maintenance-checking-services.md:11
+msgid "The shortcut command with `just` program is also available: `just run-tags self-check`"
+msgstr ""
+
+#: ../../../docs/maintenance-checking-services.md:13
+msgid "If it's all green, everything is probably running correctly."
+msgstr ""
+
+#: ../../../docs/maintenance-checking-services.md:15
+msgid "Besides this self-check, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain."
+msgstr ""
diff --git a/i18n/translation-templates/docs/maintenance-migrating.pot b/i18n/translation-templates/docs/maintenance-migrating.pot
new file mode 100644
index 000000000..ad652d0ab
--- /dev/null
+++ b/i18n/translation-templates/docs/maintenance-migrating.pot
@@ -0,0 +1,133 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/maintenance-migrating.md:1
+msgid "Migrating to new server"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:3
+msgid "This documentation explains how to migrate your Matrix services (server, client, bridges, etc.) and data **from an old server to a new server**."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:5
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:6
+msgid "This migration guide is applicable if you migrate from one server to another server having the same CPU architecture (e.g. both servers being `amd64`)."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:8
+msgid "If you're trying to migrate between different architectures (e.g. `amd64` --> `arm64`), simply copying the complete `/matrix` directory is **not** possible as it would move the raw PostgreSQL data (`/matrix/postgres/data`) between different architectures. In this specific case, you can use the guide below as a reference, but you would also need to avoid syncing `/matrix/postgres/data` to the new host, and also dump the database on your current server and import it properly on the new server. See our [Backing up PostgreSQL](maintenance-postgres.md#backing-up-postgresql) docs for help with PostgreSQL backup/restore."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:9
+msgid "If you have any questions about migration or encountered an issue during migration, do not hesitate to ask for help on [our Matrix room](https://matrix.to/#/%23matrix-docker-ansible-deploy:devture.com). You probably might want to prepare a temporary/sub account on another Matrix server in case it becomes impossible to use your server due to migration failure by any chance."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:11
+msgid "You can't change the domain (specified in the `matrix_domain` variable) after the initial deployment."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:13
+msgid "Lower DNS TTL"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:15
+msgid "Prepare by lowering DNS TTL for your domains (`matrix.example.com`, etc.), so that DNS record changes would happen faster, leading to less downtime."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:17
+msgid "Stop services on the old server completely"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:19
+msgid "Before migrating, you need to stop all services on the old server and make sure they won't be starting again."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:21
+msgid "To do so, it is recommended to run the `systemctl` command on the server. Running the playbook's `stop` tag also stops the services, but just once; they will start again if you reboot the server."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:23
+msgid "Log in to the old server and run the command as `root` (or a user that can run it with `sudo`):"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:29
+msgid "Copy data directory to the new server"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:31
+msgid "After you've confirmed that all services were stopped, copy the `/matrix` directory from the old server to the new server. When copying, make sure to preserve ownership and permissions (use `cp -p` or `rsync -ar`)!"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:33
+msgid "Adjust DNS records"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:35
+msgid "Make sure your DNS records are adjusted to point to the new server's IP address."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:37
+msgid "Update `inventory/hosts` file"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:39
+msgid "Having adjusted DNS records, replace the old server's external IP address on the `inventory/hosts` file with that of the new server."
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:41
+msgid "Create `matrix` user and group on the new server"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:43
+msgid "Then, run the command below on your local computer to create the `matrix` user and group on the new server:"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:49
+msgid "The shortcut command with `just` program is also available: `just run-tags setup-system-user`"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:51
+msgid "**Note**: because the `matrix` user and group are created dynamically on each server, the user/group ID may differ between the old and new server. We suggest that you adjust ownership of `/matrix` files. To adjust the ownership, log in to the new server and run the command:"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:57
+msgid "Install and start all services on the new server"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:59
+msgid "Finally, run the command below on your local computer to finish the installation and start all services:"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:65
+msgid "The shortcut command with `just` program is also available: `just run-tags install-all,start`"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:67
+msgid "Check if services work"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:69
+msgid "After starting the services, you probably might want to ensure that you've migrated things correctly and that services are running. For instructions, see: [check if services work](maintenance-checking-services.md)"
+msgstr ""
+
+#: ../../../docs/maintenance-migrating.md:71
+msgid "Having make sure that both services and federation work as expected, you can safely shutdown the old server."
+msgstr ""
diff --git a/i18n/translation-templates/docs/maintenance-postgres.pot b/i18n/translation-templates/docs/maintenance-postgres.pot
new file mode 100644
index 000000000..80cd68776
--- /dev/null
+++ b/i18n/translation-templates/docs/maintenance-postgres.pot
@@ -0,0 +1,217 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/maintenance-postgres.md:1
+msgid "PostgreSQL maintenance"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:3
+msgid "This document shows you how to perform various maintenance tasks related to the Postgres database server used by Matrix."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:5
+msgid "Table of contents:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:7
+msgid "[Getting a database terminal](#getting-a-database-terminal), for when you wish to execute SQL queries"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:9
+msgid "[Vacuuming PostgreSQL](#vacuuming-postgresql), for when you wish to run a Postgres [VACUUM](https://www.postgresql.org/docs/current/sql-vacuum.html) (optimizing disk space)"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:11
+msgid "[Backing up PostgreSQL](#backing-up-postgresql), for when you wish to make a backup"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:13
+msgid "[Upgrading PostgreSQL](#upgrading-postgresql), for upgrading to new major versions of PostgreSQL. Such **manual upgrades are sometimes required**."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:15
+msgid "[Tuning PostgreSQL](#tuning-postgresql) to make it run faster"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:17
+msgid "Getting a database terminal"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:19
+msgid "You can use the `/matrix/postgres/bin/cli` tool to get interactive terminal access ([psql](https://www.postgresql.org/docs/11/app-psql.html)) to the PostgreSQL server."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:21
+msgid "If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above tool will not be available."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:23
+msgid "By default, this tool puts you in the `matrix` database, which contains nothing."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:25
+msgid "To see the available databases, run `\\list` (or just `\\l`)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:27
+msgid "To change to another database (for example `synapse`), run `\\connect synapse` (or just `\\c synapse`)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:29
+msgid "You can then proceed to write queries. Example: `SELECT COUNT(*) FROM users;`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:31
+msgid "**Be careful**. Modifying the database directly (especially as services are running) is dangerous and may lead to irreversible database corruption. When in doubt, consider [making a backup](#backing-up-postgresql)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:33
+msgid "Vacuuming PostgreSQL"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:35
+msgid "Deleting lots data from Postgres does not make it release disk space, until you perform a [`VACUUM` operation](https://www.postgresql.org/docs/current/sql-vacuum.html)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:37
+msgid "You can run different `VACUUM` operations via the playbook, with the default preset being `vacuum-complete`:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:39
+msgid "(default) `vacuum-complete`: stops all services temporarily and runs `VACUUM FULL VERBOSE ANALYZE`."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:40
+msgid "`vacuum-full`: stops all services temporarily and runs `VACUUM FULL VERBOSE`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:41
+msgid "`vacuum`: runs `VACUUM VERBOSE` without stopping any services"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:42
+msgid "`vacuum-analyze` runs `VACUUM VERBOSE ANALYZE` without stopping any services"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:43
+msgid "`analyze` runs `ANALYZE VERBOSE` without stopping any services (this is just [ANALYZE](https://www.postgresql.org/docs/current/sql-analyze.html) without doing a vacuum, so it's faster)"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:45
+msgid "**Note**: for the `vacuum-complete` and `vacuum-full` presets, you'll need plenty of available disk space in your Postgres data directory (usually `/matrix/postgres/data`). These presets also stop all services (e.g. Synapse, etc.) while the vacuum operation is running."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:47
+msgid "Example playbook invocations:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:49
+msgid "`just run-tags run-postgres-vacuum`: runs the default `vacuum-complete` preset and restarts all services"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:50
+msgid "`just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze`: runs the `analyze` preset with all services remaining operational at all times"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:52
+msgid "Backing up PostgreSQL"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:54
+msgid "To automatically make Postgres database backups on a fixed schedule, see [Setting up postgres backup](configuring-playbook-postgres-backup.md)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:56
+msgid "To make a one off back up of the current PostgreSQL database, make sure it's running and then execute a command like this on the server:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:67
+msgid "If you are using an [external Postgres server](configuring-playbook-external-postgres.md), the above command will not work, because neither the credentials file (`/matrix/postgres/env-postgres-psql`), nor the `matrix-postgres` container is available."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:69
+msgid "Restoring a backup made this way can be done by [importing it](importing-postgres.md)."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:71
+msgid "Upgrading PostgreSQL"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:73
+msgid "Unless you are using an [external Postgres server](configuring-playbook-external-postgres.md), this playbook initially installs Postgres for you."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:75
+msgid "Once installed, the playbook attempts to preserve the Postgres version it starts with. This is because newer Postgres versions cannot start with data generated by older Postgres versions."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:77
+msgid "Upgrades must be performed manually."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:79
+msgid "This playbook can upgrade your existing Postgres setup with the following command:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:85
+msgid "**The old Postgres data directory is backed up** automatically, by renaming it to `/matrix/postgres/data-auto-upgrade-backup`. To rename to a different path, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_auto_upgrade_backup_data_path=/another/disk/matrix-postgres-before-upgrade\"`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:87
+msgid "The auto-upgrade-backup directory stays around forever, until you **manually decide to delete it**."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:89
+msgid "As part of the upgrade, the database is dumped to `/tmp`, an upgraded and empty Postgres server is started, and then the dump is restored into the new server. To use a different directory for the dump, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_dump_dir=/directory/to/dump/here\"`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:91
+msgid "To save disk space in `/tmp`, the dump file is gzipped on the fly at the expense of CPU usage. If you have plenty of space in `/tmp` and would rather avoid gzipping, you can explicitly pass a dump filename which doesn't end in `.gz`. Example: `--extra-vars=\"postgres_dump_name=matrix-postgres-dump.sql\"`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:93
+msgid "**All databases, roles, etc. on the Postgres server are migrated**."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:95
+msgid "Tuning PostgreSQL"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:97
+msgid "PostgreSQL can be [tuned](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) to make it run faster. This is done by passing extra arguments to the Postgres process."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:99
+msgid "The [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) **already does some tuning by default**, which matches the [tuning logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) done by websites like https://pgtune.leopard.in.ua/. You can manually influence some of the tuning variables. These parameters (variables) are injected via the `postgres_postgres_process_extra_arguments_auto` variable."
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:101
+msgid "Most users should be fine with the automatically-done tuning. However, you may wish to:"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:103
+msgid "**adjust the automatically-determined tuning parameters manually**: change the values for the tuning variables defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) (see `postgres_max_connections`, `postgres_data_storage` etc). These variables are ultimately passed to Postgres via a `postgres_postgres_process_extra_arguments_auto` variable"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:105
+msgid "**turn automatically-performed tuning off**: override it like this: `postgres_postgres_process_extra_arguments_auto: []`"
+msgstr ""
+
+#: ../../../docs/maintenance-postgres.md:107
+msgid "**add additional tuning parameters**: define your additional Postgres configuration parameters in `postgres_postgres_process_extra_arguments_custom`. See `postgres_postgres_process_extra_arguments_auto` defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) for inspiration"
+msgstr ""
diff --git a/i18n/translation-templates/docs/maintenance-synapse.pot b/i18n/translation-templates/docs/maintenance-synapse.pot
new file mode 100644
index 000000000..a205c177a
--- /dev/null
+++ b/i18n/translation-templates/docs/maintenance-synapse.pot
@@ -0,0 +1,197 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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/maintenance-synapse.md:1
+msgid "Synapse maintenance"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:3
+msgid "This document shows you how to perform various maintenance tasks related to the Synapse chat server."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:5
+msgid "Table of contents:"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:7
+msgid "[Purging old data with the Purge History API](#purging-old-data-with-the-purge-history-api), for when you wish to delete in-use (but old) data from the Synapse database"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:9
+msgid "[Compressing state with rust-synapse-compress-state](#compressing-state-with-rust-synapse-compress-state)"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:11
+msgid "[Browse and manipulate the database](#browse-and-manipulate-the-database), for when you really need to take matters into your own hands"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:13
+msgid "[Make Synapse faster](#make-synapse-faster)"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:15
+msgid "Purging old data with the Purge History API"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:17
+msgid "You can use the **[Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md)** to delete old messages on a per-room basis. **This is destructive** (especially for non-federated rooms), because it means **people will no longer have access to history past a certain point**."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:19
+msgid "To make use of this Synapse Admin API, **you'll need an admin access token** first. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:21
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:23
+msgid "Synapse's Admin API is not exposed to the internet by default, following [official Synapse reverse-proxying recommendations](https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md#synapse-administration-endpoints). To expose it you will need to add `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true` to your `vars.yml` file."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:25
+msgid "Follow the [Purge History API](https://github.com/element-hq/synapse/blob/master/docs/admin_api/purge_history_api.md) documentation page for the actual purging instructions."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:27
+msgid "After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:29
+msgid "Compressing state with rust-synapse-compress-state"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:31
+msgid "[rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) can be used to optimize some `_state` tables used by Synapse. If your server participates in large rooms this is the most effective way to reduce the size of your database."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:33
+msgid "**Note**: besides running the `rust-synapse-compress-state` tool manually, you can also enable its `synapse-auto-compressor` tool by [Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md). The automatic tool will run on a schedule every day and you won't have to compress state manually ever again."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:35
+msgid "`rust-synapse-compress-state` should be safe to use (even when Synapse is running), but it's always a good idea to [make Postgres backups](./maintenance-postgres.md#backing-up-postgresql) first."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:37
+msgid "To ask the playbook to run rust-synapse-compress-state, execute:"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:43
+msgid "The shortcut command with `just` program is also available: `just run-tags rust-synapse-compress-state`"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:45
+msgid "By default, all rooms with more than `100000` state group rows will be compressed. If you need to adjust this, pass: `--extra-vars='matrix_synapse_rust_synapse_compress_state_min_state_groups_required=SOME_NUMBER_HERE'` to the command above."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:47
+msgid "After state compression, you may wish to run a [`FULL` Postgres `VACUUM`](./maintenance-postgres.md#vacuuming-postgresql)."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:49
+msgid "Browse and manipulate the database"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:51
+msgid "When the [Synapse Admin API](https://github.com/element-hq/synapse/tree/master/docs/admin_api) and the other tools do not provide a more convenient way, having a look at synapse's postgresql database can satisfy a lot of admins' needs."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:53
+msgid "Editing the database manually is not recommended or supported by the Synapse developers. If you are going to do so you should [make a database backup](./maintenance-postgres.md#backing-up-postgresql)."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:55
+msgid "First, set up an SSH tunnel to your Matrix server (skip if it is your local machine):"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:62
+msgid "Then start up an ephemeral [adminer](https://www.adminer.org/) container on the Matrix server, connecting it to the `matrix` network and linking the postgresql container:"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:68
+msgid "You should then be able to browse the adminer database administration GUI at http://localhost:1799/ after entering your DB credentials (found in the `host_vars` or on the server in `{{matrix_synapse_config_dir_path}}/homeserver.yaml` under `database.args`)"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:70
+msgid "⚠️️ Be **very careful** with this, there is **no undo** for impromptu DB operations."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:72
+msgid "Make Synapse faster"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:74
+msgid "Synapse's presence feature which tracks which users are online and which are offline can use a lot of processing power. You can disable presence by adding `matrix_synapse_presence_enabled: false` to your `vars.yml` file."
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:76
+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:78
+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:80
+msgid "Tuning caches and cache autotuning"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:82
+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:84
+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:86
+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:88
+msgid "Cache autotuning is **enabled by default** and controlled via the following variables:"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:90
+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:91
+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:92
+msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` - defaults to `30s`"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:94
+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:96
+msgid "To **disable cache auto-tuning**, unset all values:"
+msgstr ""
+
+#: ../../../docs/maintenance-synapse.md:104
+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:106
+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 ""
diff --git a/i18n/translation-templates/docs/maintenance-upgrading-services.pot b/i18n/translation-templates/docs/maintenance-upgrading-services.pot
new file mode 100644
index 000000000..072d69f28
--- /dev/null
+++ b/i18n/translation-templates/docs/maintenance-upgrading-services.pot
@@ -0,0 +1,125 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/maintenance-upgrading-services.md:1
+msgid "Upgrading the Matrix services"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:3
+msgid "This playbook not only installs the various Matrix services for you, but can also upgrade them as new versions are made available."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:5
+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/maintenance-upgrading-services.md:7
+msgid "The upstream projects, which this playbook makes use of, occasionally if not often suffer from security vulnerabilities (for example, see [here](https://github.com/element-hq/element-web/security) for known ones on Element Web)."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:9
+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/maintenance-upgrading-services.md:11
+msgid "The developers of this playbook strive to maintain the playbook updated, so that you can re-run the playbook to address such vulnerabilities. It is **your responsibility** to keep your server and the services on it up-to-date."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:13
+msgid "If you want to be notified when new versions of Synapse are released, you should join the Synapse Homeowners room: [#homeowners:matrix.org](https://matrix.to/#/#homeowners:matrix.org)."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:15
+msgid "Steps to upgrade the Matrix services"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:17
+msgid "Check the changelog"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:19
+msgid "Before updating the playbook and the Ansible roles in the playbook, take a look at [the changelog](../CHANGELOG.md) to see if there have been any backward-incompatible changes that you need to take care of."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:21
+msgid "Update the playbook and the Ansible roles"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:23
+msgid "If it looks good to you, go to the `matrix-docker-ansible-deploy` directory, update your playbook directory and all upstream Ansible roles (defined in the `requirements.yml` file) by running:"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:25
+msgid "either: `just update`"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:26
+msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:28
+msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:30
+msgid "**Note**: for details about `just` commands, take a look at: [Running `just` commands](just.md)."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:32
+msgid "Re-run the playbook setup"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:34
+msgid "After updating the Ansible roles, then re-run the [playbook setup](installing.md#maintaining-your-setup-in-the-future) and restart all services:"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:40
+msgid "If you remove components from `vars.yml`, or if we switch some component from being installed by default to not being installed by default anymore, you'd need to run the setup command with the `setup-all` tag as below:"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:46
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:48
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account, if any."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:50
+msgid "Our estimation is that running `--tags=install-all,start` is approximately from **2 to 5 times faster** than running `setup-all,ensure-matrix-users-created,start`. See [this entry](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) on `CHANGELOG.md` for more information."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:52
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`. Note these shortcuts run the `ensure-matrix-users-created` tag too."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:54
+msgid "See [this page on the playbook tags](playbook-tags.md) for more information about those tags."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:56
+msgid "PostgreSQL major version upgrade"
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:58
+msgid "Major version upgrades to the internal PostgreSQL database are not done automatically. Upgrades must be performed manually."
+msgstr ""
+
+#: ../../../docs/maintenance-upgrading-services.md:60
+msgid "For details about upgrading it, refer to the [upgrading PostgreSQL guide](maintenance-postgres.md#upgrading-postgresql)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/obtaining-access-tokens.pot b/i18n/translation-templates/docs/obtaining-access-tokens.pot
new file mode 100644
index 000000000..d0acfad7a
--- /dev/null
+++ b/i18n/translation-templates/docs/obtaining-access-tokens.pot
@@ -0,0 +1,93 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-28 10:25+0200\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/obtaining-access-tokens.md:1
+msgid "Obtaining an Access Token"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:3
+msgid "When setting up some optional features like bots and bridges you will need to provide an access token for some user. This document provides documentation on how to obtain such an access token."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:5
+msgid "⚠️ **Warning**: Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:7
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:9
+msgid "The user for whom you want to obtain an access token needs to already exist. You can use this playbook to [register a new user](registering-users.md), if you have not already."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:11
+msgid "Below, we describe 2 ways to generate an access token for a user - using [Element Web](#obtain-an-access-token-via-element-web) or [curl](#obtain-an-access-token-via-curl). For both ways you need the user's password."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:13
+msgid "Obtain an access token via Element Web"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:15
+msgid "In a private browsing session (incognito window), open Element Web."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:16
+msgid "Log in with the user's credentials."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:17
+msgid "In the settings page, choose \"Help & About\", scroll down to the bottom and expand the `Access Token` section (see screenshot below)."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:18
+msgid "Copy the access token to your configuration."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:19
+msgid "Close the private browsing session. **Do not log out**. Logging out will invalidate the token, making it not work."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:21
+msgid "![Obtaining an access token with Element Web](assets/obtain_admin_access_token_element_web.png)"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:21
+msgid "Obtaining an access token with Element Web"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:23
+msgid "Obtain an access token via curl"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:25
+msgid "You can use the following command to get an access token for your user directly from the [Matrix Client-Server API](https://www.matrix.org/docs/guides/client-server-api#login):"
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:35
+msgid "Change `USERNAME`, `PASSWORD`, and `example.com` accordingly."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:37
+msgid "`YOURDEVICEID` is optional and can be used to more easily identify the session later. When omitted (mind the commas in the JSON payload if you'll be omitting it), a random device ID will be generated."
+msgstr ""
+
+#: ../../../docs/obtaining-access-tokens.md:39
+msgid "Your response will look like this (prettified):"
+msgstr ""
diff --git a/i18n/translation-templates/docs/playbook-tags.pot b/i18n/translation-templates/docs/playbook-tags.pot
new file mode 100644
index 000000000..4f6d03c03
--- /dev/null
+++ b/i18n/translation-templates/docs/playbook-tags.pot
@@ -0,0 +1,73 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/playbook-tags.md:1
+msgid "Playbook tags"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:3
+msgid "The Ansible playbook's tasks are tagged, so that certain parts of the Ansible playbook can be run without running all other tasks."
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:5
+msgid "The general command syntax is: `ansible-playbook -i inventory/hosts setup.yml --tags=COMMA_SEPARATED_TAGS_GO_HERE`"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:7
+msgid "Here are some playbook tags that you should be familiar with:"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:9
+msgid "`setup-all` - runs all setup tasks (installation and uninstallation) for all components, but does not start/restart services"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:11
+msgid "`install-all` - like `setup-all`, but skips uninstallation tasks. Useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove components, you'd need to run `setup-all` though, or these components will still remain installed"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:13
+msgid "`setup-SERVICE` (e.g. `setup-postmoogle`) - runs the setup tasks only for a given role, but does not start/restart services. You can discover these additional tags in each role (`roles/**/tasks/main.yml`). Running per-component setup tasks is **not recommended**, as components sometimes depend on each other and running just the setup tasks for a given component may not be enough. For example, setting up the [mautrix-telegram bridge](configuring-playbook-bridge-mautrix-telegram.md), in addition to the `setup-mautrix-telegram` tag, requires database changes (the `setup-postgres` tag) as well as reverse-proxy changes (the `setup-nginx-proxy` tag)."
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:15
+msgid "`install-SERVICE` (e.g. `install-postmoogle`) - like `setup-SERVICE`, but skips uninstallation tasks. See `install-all` above for additional information."
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:17
+msgid "`start` - starts all systemd services and makes them start automatically in the future"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:19
+msgid "`stop` - stops all systemd services"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:21
+msgid "`ensure-matrix-users-created` - a special tag which ensures that all special users needed by the playbook (for bots, etc.) are created"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:23
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:24
+msgid "`setup-*` tags and `install-*` tags **do not start services** automatically, because you may wish to do things before starting services, such as importing a database dump, restoring data from another server, etc."
+msgstr ""
+
+#: ../../../docs/playbook-tags.md:25
+msgid "Please be careful not to confuse the playbook tags with the `just` shortcut commands (\"recipes\"). For details about `just` commands, see: [Running `just` commands](just.md)"
+msgstr ""
diff --git a/i18n/translation-templates/docs/prerequisites.pot b/i18n/translation-templates/docs/prerequisites.pot
new file mode 100644
index 000000000..61adad37c
--- /dev/null
+++ b/i18n/translation-templates/docs/prerequisites.pot
@@ -0,0 +1,161 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/prerequisites.md:1
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:3
+msgid "<sup>Prerequisites > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > [Configuring the playbook](configuring-playbook.md) > [Installing](installing.md)</sup>"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:5
+msgid "To install Matrix services using this Ansible playbook, you need to prepare several requirements both on your local computer (where you will run the playbook to configure the server) and the server (where the playbook will install the Matrix services for you). **These requirements need to be set up manually** before proceeding to the next step."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:7
+msgid "We will be using `example.com` as the domain in the following instruction. Please remember to replace it with your own domain before running any commands."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:9
+msgid "**Note**: if you do not have an existing Matrix server and want to start quickly with \"opinionated defaults\", we suggest you to follow ⚡ **[Quick start](quick-start.md)** installation guide."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:11
+msgid "Your local computer"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:13
+msgid "[Ansible](http://ansible.com/) program. It's used to run this playbook and configures your server for you. Take a look at [our guide about Ansible](ansible.md) for more information, as well as [version requirements](ansible.md#supported-ansible-versions) and alternative ways to run Ansible."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:15
+msgid "[passlib](https://passlib.readthedocs.io/en/stable/index.html) Python library. See [this official documentation](https://passlib.readthedocs.io/en/stable/install.html#installation-instructions) for an instruction to install it. On most distros, you need to install some `python-passlib` or `py3-passlib` package, etc."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:17
+msgid "[`git`](https://git-scm.com/) as the recommended way to download the playbook. `git` may also be required on the server if you will be [self-building](self-building.md) components."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:19
+msgid "[`just`](https://github.com/casey/just) for running `just roles`, `just update`, etc. (see [`justfile`](../justfile)), although you can also run these commands manually. Take at look at this documentation for more information: [Running `just` commands](just.md)."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:21
+msgid "Strong password (random strings) generator. The playbook often requires you to create a strong password and use it for settings on `vars.yml`, components, etc. As any tools should be fine, this playbook has adopted [`pwgen`](https://linux.die.net/man/1/pwgen) (running `pwgen -s 64 1`). [Password Tech](https://pwgen-win.sourceforge.io/), formerly known as \"PWGen for Windows\", is available as free and open source password generator for Windows. Generally, using a random generator available on the internet is not recommended."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:23
+msgid "Server"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:25
+msgid "(Recommended) An **x86** server ([What kind of server specs do I need?](faq.md#what-kind-of-server-specs-do-i-need)) running one of these operating systems that make use of [systemd](https://systemd.io/):"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:26
+msgid "**Archlinux**"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:27
+msgid "**CentOS**, **Rocky Linux**, **AlmaLinux**, or possibly other RHEL alternatives (although your mileage may vary)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:28
+msgid "**Debian** (10/Buster or newer)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:29
+msgid "**Ubuntu** (18.04 or newer, although [20.04 may be problematic](ansible.md#supported-ansible-versions) if you run the Ansible playbook on it)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:31
+msgid "Generally, newer is better. We only strive to support released stable versions of distributions, not betas or pre-releases. This playbook can take over your whole server or co-exist with other services that you have there."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:33
+msgid "This playbook somewhat supports running on non-`amd64` architectures like ARM. See [Alternative Architectures](alternative-architectures.md)."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:35
+msgid "If your distro runs within an [LXC container](https://linuxcontainers.org/), you may hit [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/703). It can be worked around, if absolutely necessary, but we suggest that you avoid running from within an LXC container."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:37
+msgid "`root` access to your server (or a user capable of elevating to `root` via `sudo`)."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:39
+msgid "[Python](https://www.python.org/). Most distributions install Python by default, but some don't (e.g. Ubuntu 18.04) and require manual installation (something like `apt-get install python3`). On some distros, Ansible may incorrectly [detect the Python version](https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html) (2 vs 3) and you may need to explicitly specify the interpreter path in `inventory/hosts` during installation (e.g. `ansible_python_interpreter=/usr/bin/python3`)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:41
+msgid "[sudo](https://www.sudo.ws/), even when you've configured Ansible to log in as `root`. Some distributions, like a minimal Debian net install, do not include the `sudo` package by default."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:43
+msgid "An HTTPS-capable web server at the base domain name (`example.com`) which is capable of serving static files. Unless you decide to [Serve the base domain from the Matrix server](configuring-playbook-base-domain-serving.md) or alternatively, to use DNS SRV records for [Server Delegation](howto-server-delegation.md)."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:45
+msgid "Properly configured DNS records for `example.com` (details in [Configuring DNS](configuring-dns.md))."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:47
+msgid "Some TCP/UDP ports open. This playbook (actually [Docker itself](https://docs.docker.com/network/iptables/)) configures the server's internal firewall for you. In most cases, you don't need to do anything special. But **if your server is running behind another firewall**, you'd need to open these ports:"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:49
+msgid "`80/tcp`: HTTP webserver"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:50
+msgid "`443/tcp` and `443/udp`: HTTPS webserver"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:51
+msgid "`3478/tcp`: TURN over TCP (used by Coturn)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:52
+msgid "`3478/udp`: TURN over UDP (used by Coturn)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:53
+msgid "`5349/tcp`: TURN over TCP (used by Coturn)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:54
+msgid "`5349/udp`: TURN over UDP (used by Coturn)"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:55
+msgid "`8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. In some cases, this **may necessary even with federation disabled**. Integration Servers (like Dimension) and Identity Servers (like ma1sd) may need to access `openid` APIs on the federation port."
+msgstr ""
+
+#: ../../../docs/prerequisites.md:56
+msgid "the range `49152-49172/udp`: TURN over UDP"
+msgstr ""
+
+#: ../../../docs/prerequisites.md:57
+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:61
+msgid "[▶️](configuring-dns.md) When ready to proceed, continue with [Configuring DNS](configuring-dns.md)."
+msgstr ""
diff --git a/i18n/translation-templates/docs/quick-start.pot b/i18n/translation-templates/docs/quick-start.pot
new file mode 100644
index 000000000..17c232b8a
--- /dev/null
+++ b/i18n/translation-templates/docs/quick-start.pot
@@ -0,0 +1,429 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/quick-start.md:1
+msgid "Quick start"
+msgstr ""
+
+#: ../../../docs/quick-start.md:9
+msgid "This page explains how to use this Ansible playbook to install Matrix services on your server with a minimal set of core services."
+msgstr ""
+
+#: ../../../docs/quick-start.md:11
+msgid "We will be using `example.com` as the \"base domain\" in the following instruction."
+msgstr ""
+
+#: ../../../docs/quick-start.md:13
+msgid "By following the instruction on this page, you will set up:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:15
+msgid "**your own Matrix server** on a `matrix.example.com` server, which is configured to present itself as `example.com`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:16
+msgid "**your user account** like `@alice:example.com` on the server"
+msgstr ""
+
+#: ../../../docs/quick-start.md:17
+msgid "a **self-hosted Matrix client**, [Element Web](configuring-playbook-client-element-web.md) with the default subdomain at `element.example.com`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:18
+msgid "Matrix delegation, so that your `matrix.example.com` server (presenting itself as `example.com`) can join the Matrix Federation and communicate with any other server in the Matrix network"
+msgstr ""
+
+#: ../../../docs/quick-start.md:20
+msgid "Please remember to replace `example.com` with your own domain before running any commands."
+msgstr ""
+
+#: ../../../docs/quick-start.md:22
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../../docs/quick-start.md:24
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Prerequisites](prerequisites.md)</sup>"
+msgstr ""
+
+#: ../../../docs/quick-start.md:26
+msgid "At first, **check prerequisites** and prepare for installation by setting up programs [on your own computer](prerequisites.md#your-local-computer) and [your server](prerequisites.md#server). You also need `root` access on your server (a user that could elevate to `root` via `sudo` also works)."
+msgstr ""
+
+#: ../../../docs/quick-start.md:28
+msgid "When preparing your server, make sure to check [the server specs you need](faq.md#what-kind-of-server-specs-do-i-need). We recommend starting with a server having at least 2GB of memory."
+msgstr ""
+
+#: ../../../docs/quick-start.md:34
+msgid "If you encounter an error during installation, please make sure that you have installed and configured programs correctly."
+msgstr ""
+
+#: ../../../docs/quick-start.md:36
+msgid "One of the main reasons of basic errors is using an incompatible version of required software such as Ansible. Take a look at [our guide about Ansible](ansible.md) for more information. In short: installing the latest available version is recommended."
+msgstr ""
+
+#: ../../../docs/quick-start.md:38
+msgid "Configure your DNS settings"
+msgstr ""
+
+#: ../../../docs/quick-start.md:40
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Configuring your DNS settings](configuring-dns.md)</sup>"
+msgstr ""
+
+#: ../../../docs/quick-start.md:42
+msgid "After installing and configuring prerequisites, you will need to **configure DNS records**."
+msgstr ""
+
+#: ../../../docs/quick-start.md:44
+msgid "To configure Matrix services in the default settings, go to your DNS service provider, and adjust DNS records as below."
+msgstr ""
+
+#: ../../../docs/quick-start.md:0
+msgid "Type"
+msgstr ""
+
+#: ../../../docs/quick-start.md:0
+msgid "Host"
+msgstr ""
+
+#: ../../../docs/quick-start.md:0
+msgid "Priority"
+msgstr ""
+
+#: ../../../docs/quick-start.md:0
+msgid "Weight"
+msgstr ""
+
+#: ../../../docs/quick-start.md:0
+msgid "Port"
+msgstr ""
+
+#: ../../../docs/quick-start.md:0
+msgid "Target"
+msgstr ""
+
+#: ../../../docs/quick-start.md:0
+msgid "A"
+msgstr ""
+
+#: ../../../docs/quick-start.md:0
+msgid "`matrix`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:0
+msgid "-"
+msgstr ""
+
+#: ../../../docs/quick-start.md:0
+msgid "`matrix-server-IP`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:0
+msgid "CNAME"
+msgstr ""
+
+#: ../../../docs/quick-start.md:0
+msgid "`element`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:0
+msgid "`matrix.example.com`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:51
+msgid "As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com`) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine)."
+msgstr ""
+
+#: ../../../docs/quick-start.md:53
+msgid "It might take some time for the DNS records to propagate after creation."
+msgstr ""
+
+#: ../../../docs/quick-start.md:55
+msgid "**💡 Note**: if you are using Cloudflare DNS, make sure to disable the proxy and set all records to \"DNS only\""
+msgstr ""
+
+#: ../../../docs/quick-start.md:57
+msgid "Get the playbook"
+msgstr ""
+
+#: ../../../docs/quick-start.md:59
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Getting the playbook](getting-the-playbook.md)</sup>"
+msgstr ""
+
+#: ../../../docs/quick-start.md:61
+msgid "Next, let's **get the playbook's source code**."
+msgstr ""
+
+#: ../../../docs/quick-start.md:63
+msgid "We recommend to do so with [git](https://git-scm.com/) as it enables you to keep it up to date with the latest source code. While it is possible to download the playbook as a ZIP archive, it is not recommended."
+msgstr ""
+
+#: ../../../docs/quick-start.md:65
+msgid "To get the playbook with git, install git on your computer, go to a directory, and run the command:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:71
+msgid "It will fetch the playbook to a new `matrix-docker-ansible-deploy` directory underneath the directory you are currently in."
+msgstr ""
+
+#: ../../../docs/quick-start.md:73
+msgid "Configure the playbook"
+msgstr ""
+
+#: ../../../docs/quick-start.md:75
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Configuring the playbook](configuring-playbook.md)</sup>"
+msgstr ""
+
+#: ../../../docs/quick-start.md:77
+msgid "Now that the playbook was fetched, it is time to **configure** it per your needs."
+msgstr ""
+
+#: ../../../docs/quick-start.md:79
+msgid "To install Matrix services with this playbook, you would at least need 2 configuration files."
+msgstr ""
+
+#: ../../../docs/quick-start.md:81
+msgid "For your convenience, we have prepared example files of them ([`vars.yml`](../examples/vars.yml) and [`hosts`](../examples/hosts))."
+msgstr ""
+
+#: ../../../docs/quick-start.md:83
+msgid "To start quickly based on these example files, go into the `matrix-docker-ansible-deploy` directory and follow the instructions below:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:85
+msgid "Create a directory to hold your configuration: `mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\""
+msgstr ""
+
+#: ../../../docs/quick-start.md:86
+msgid "Copy the sample configuration file: `cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:87
+msgid "Copy the sample inventory hosts file: `cp examples/hosts inventory/hosts`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:88
+msgid "Edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`)"
+msgstr ""
+
+#: ../../../docs/quick-start.md:89
+msgid "Edit the inventory hosts file (`inventory/hosts`)"
+msgstr ""
+
+#: ../../../docs/quick-start.md:91
+msgid "Before editing these 2 files, make sure to read explanations on them to understand what needs to be configured."
+msgstr ""
+
+#: ../../../docs/quick-start.md:93
+msgid "**💡 Notes:**"
+msgstr ""
+
+#: ../../../docs/quick-start.md:94
+msgid "If you are not in control of anything on the base domain, you would need to set additional configuration on `vars.yml`. For more information, see [How do I install on matrix.example.com without involving the base domain?](faq.md#how-do-i-install-on-matrix-example-com-without-involving-the-base-domain) on our FAQ."
+msgstr ""
+
+#: ../../../docs/quick-start.md:95
+msgid "Certain configuration decisions (like the base domain configured in `matrix_domain` and homeserver implementation configured in `matrix_homeserver_implementation`) are final. If you make the wrong choice and wish to change it, you'll have to run the Uninstalling step and start over."
+msgstr ""
+
+#: ../../../docs/quick-start.md:96
+msgid "Instead of configuring a lot of things all at once, we recommend starting with the basic (default) settings in order to get yourself familiar with how the playbook works. After making sure that everything works as expected, you can add (and remove) advanced settings / features and run the playbook as many times as you wish."
+msgstr ""
+
+#: ../../../docs/quick-start.md:98
+msgid "Install"
+msgstr ""
+
+#: ../../../docs/quick-start.md:100
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Installing](installing.md)</sup>"
+msgstr ""
+
+#: ../../../docs/quick-start.md:102
+msgid "After editing `vars.yml` and `hosts` files, let's start the **installation** procedure."
+msgstr ""
+
+#: ../../../docs/quick-start.md:104
+msgid "Update Ansible roles"
+msgstr ""
+
+#: ../../../docs/quick-start.md:106
+msgid "Before installing, you need to update the Ansible roles that this playbook uses and fetches from outside."
+msgstr ""
+
+#: ../../../docs/quick-start.md:108
+msgid "To update your playbook directory and all upstream Ansible roles, run:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:110
+msgid "either: `just update`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:111
+msgid "or: a combination of `git pull` and `just roles` (or `make roles` if you have `make` program on your computer instead of `just`)"
+msgstr ""
+
+#: ../../../docs/quick-start.md:113
+msgid "If you don't have either `just` tool or `make` program, you can run the `ansible-galaxy` tool directly: `rm -rf roles/galaxy; ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:115
+msgid "Run installation command"
+msgstr ""
+
+#: ../../../docs/quick-start.md:117
+msgid "Then, run the command below to start installation:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:123
+msgid "If you **don't** use SSH keys for authentication, but rather a regular password, you may need to add `--ask-pass` to the command."
+msgstr ""
+
+#: ../../../docs/quick-start.md:125
+msgid "If you **do** use SSH keys for authentication, **and** use a non-root user to *become* root (sudo), you may need to add `-K` (`--ask-become-pass`) to the command."
+msgstr ""
+
+#: ../../../docs/quick-start.md:127
+msgid "Wait until the command completes. If it's all green, everything should be running properly."
+msgstr ""
+
+#: ../../../docs/quick-start.md:129
+msgid "Create your user account"
+msgstr ""
+
+#: ../../../docs/quick-start.md:131
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Registering users](registering-users.md)</sup>"
+msgstr ""
+
+#: ../../../docs/quick-start.md:133
+msgid "As you have configured your brand new server and the client, you need to **create your user account** on your Matrix server."
+msgstr ""
+
+#: ../../../docs/quick-start.md:135
+msgid "To create your user account (as an administrator of the server) via this Ansible playbook, run the command below on your local computer."
+msgstr ""
+
+#: ../../../docs/quick-start.md:137
+msgid "**💡 Notes**:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:138
+msgid "Make sure to adjust `YOUR_USERNAME_HERE` and `YOUR_PASSWORD_HERE`"
+msgstr ""
+
+#: ../../../docs/quick-start.md:139
+msgid "For `YOUR_USERNAME_HERE`, use a plain username like `alice`, not your full ID (`@alice:example.com`)"
+msgstr ""
+
+#: ../../../docs/quick-start.md:151
+msgid "Finalize server installation"
+msgstr ""
+
+#: ../../../docs/quick-start.md:153
+msgid "<sup>This section is optimized for this quick-start guide and is derived from the following full-documentation page: [Server Delegation](howto-server-delegation.md)</sup>"
+msgstr ""
+
+#: ../../../docs/quick-start.md:155
+msgid "Now that you've configured Matrix services and your user account, you need to **finalize the installation process** by [setting up Matrix delegation (redirection)](howto-server-delegation.md), so that your Matrix server (`matrix.example.com`) can present itself as the base domain (`example.com`) in the Matrix network."
+msgstr ""
+
+#: ../../../docs/quick-start.md:157
+msgid "**This is required for federation to work!** Without a proper configuration, your server will effectively not be part of the Matrix network."
+msgstr ""
+
+#: ../../../docs/quick-start.md:159
+msgid "To configure the delegation, you have these two options. Choose one of them according to your situation."
+msgstr ""
+
+#: ../../../docs/quick-start.md:161
+msgid "If you can afford to point the base domain at the Matrix server, follow the instruction below which guides you into [serving the base domain](configuring-playbook-base-domain-serving.md) from the integrated web server."
+msgstr ""
+
+#: ../../../docs/quick-start.md:162
+msgid "Alternatively, if you're using the base domain for other purposes and cannot point it to the Matrix server (and thus cannot \"serve the base domain\" from it), you most likely need to [manually install well-known files on the base domain's server](configuring-well-known.md#manually-installing-well-known-files-on-the-base-domains-server)."
+msgstr ""
+
+#: ../../../docs/quick-start.md:164
+msgid "To have the base domain served from the integrated web server, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:170
+msgid "After configuring the playbook, run the command below and wait until it finishes:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:176
+msgid "💡 Running the `install-matrix-static-files` playbook tag (as done here) is an optimized version of running [the full setup command](#run-installation-command)."
+msgstr ""
+
+#: ../../../docs/quick-start.md:178
+msgid "After the command finishes, you can also check whether your server federates with the Matrix network by using the [Federation Tester](https://federationtester.matrix.org/) against your base domain (`example.com`), not the `matrix.example.com` subdomain."
+msgstr ""
+
+#: ../../../docs/quick-start.md:180
+msgid "Re-run the full setup command any time"
+msgstr ""
+
+#: ../../../docs/quick-start.md:182
+msgid "If you think something is wrong with the server configuration, feel free to re-run the setup command any time:"
+msgstr ""
+
+#: ../../../docs/quick-start.md:188
+msgid "Log in to your user account"
+msgstr ""
+
+#: ../../../docs/quick-start.md:190
+msgid "Finally, let's make sure that you can log in to the created account with the specified password."
+msgstr ""
+
+#: ../../../docs/quick-start.md:192
+msgid "You should be able to log in to it with your own [Element Web](configuring-playbook-client-element-web.md) client which you have set up at `element.example.com` by running the playbook. Open the URL (`https://element.example.com`) in a web browser and enter your credentials to log in."
+msgstr ""
+
+#: ../../../docs/quick-start.md:194
+msgid "**If you successfully logged in to your account, installing and configuring is complete**🎉"
+msgstr ""
+
+#: ../../../docs/quick-start.md:196
+msgid "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/quick-start.md:198
+msgid "Things to do next"
+msgstr ""
+
+#: ../../../docs/quick-start.md:200
+msgid "Once you get familiar with the playbook, you might probably want to set up additional services such as a bridge on your server."
+msgstr ""
+
+#: ../../../docs/quick-start.md:202
+msgid "As this page intends to be a quick start guide which explains how to start the core Matrix services, it does not cover a topic like how to set them up. Take a look at the list of [things to do next](installing.md#things-to-do-next) to learn more."
+msgstr ""
+
+#: ../../../docs/quick-start.md:204
+msgid "⚠️Keep the playbook and services up-to-date"
+msgstr ""
+
+#: ../../../docs/quick-start.md:206
+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/quick-start.md:208
+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/quick-start.md:210
+msgid "For more information about upgrading or maintaining services with the playbook, take at look at this page: [Upgrading the Matrix services](maintenance-upgrading-services.md)"
+msgstr ""
diff --git a/i18n/translation-templates/docs/registering-users.pot b/i18n/translation-templates/docs/registering-users.pot
new file mode 100644
index 000000000..6b8150c1d
--- /dev/null
+++ b/i18n/translation-templates/docs/registering-users.pot
@@ -0,0 +1,242 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/registering-users.md:1
+msgid "Registering users"
+msgstr ""
+
+#: ../../../docs/registering-users.md:3
+msgid "This documentation page tells you how to create user accounts on your Matrix server."
+msgstr ""
+
+#: ../../../docs/registering-users.md:5
+msgid "Table of contents:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:7
+msgid "[Registering users](#registering-users)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:8
+msgid "[Registering users manually](#registering-users-manually)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:9
+msgid "[Managing users via a Web UI](#managing-users-via-a-web-ui)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:10
+msgid "[Letting certain users register on your private server](#letting-certain-users-register-on-your-private-server)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:11
+msgid "[Enabling public user registration](#enabling-public-user-registration)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:12
+msgid "[Adding/Removing Administrator privileges to an existing user](#addingremoving-administrator-privileges-to-an-existing-user)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:14
+msgid "Registering users manually"
+msgstr ""
+
+#: ../../../docs/registering-users.md:16
+#: ../../../docs/registering-users.md:118
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:17
+msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`"
+msgstr ""
+
+#: ../../../docs/registering-users.md:18
+msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:19
+msgid "Use `admin=yes` or `admin=no` depending on whether you wish to make the user an administrator of the Matrix server"
+msgstr ""
+
+#: ../../../docs/registering-users.md:21
+msgid "After registering a user (using one of the methods below), **you can log in with that user** via the [Element Web](configuring-playbook-client-element-web.md) service that this playbook has installed for you at a URL like this: `https://element.example.com/`."
+msgstr ""
+
+#: ../../../docs/registering-users.md:23
+msgid "Registering users via the Ansible playbook"
+msgstr ""
+
+#: ../../../docs/registering-users.md:25
+msgid "It's best to register users via the Ansible playbook, because it works regardless of homeserver implementation (Synapse, Dendrite, etc) or usage of [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (MAS)."
+msgstr ""
+
+#: ../../../docs/registering-users.md:27
+msgid "To register a user via this Ansible playbook:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:35
+msgid "**or** by invoking `ansible-playbook` manually:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:43
+msgid "Feel free to register as many users (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your user account only (with `admin=yes`), and others should be created with `admin=no`."
+msgstr ""
+
+#: ../../../docs/registering-users.md:45
+msgid "⚠️ **Warning**: If you're registering users against Matrix Authentication Service, do note that it [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information."
+msgstr ""
+
+#: ../../../docs/registering-users.md:47
+msgid "Registering users manually for Synapse"
+msgstr ""
+
+#: ../../../docs/registering-users.md:49
+msgid "If you're using the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default), you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
+msgstr ""
+
+#: ../../../docs/registering-users.md:57
+msgid "Registering users manually for Dendrite"
+msgstr ""
+
+#: ../../../docs/registering-users.md:59
+msgid "If you're using the [Dendrite](./configuring-playbook-dendrite.md) homeserver implementation, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
+msgstr ""
+
+#: ../../../docs/registering-users.md:67
+msgid "Registering users manually for Matrix Authentication Service"
+msgstr ""
+
+#: ../../../docs/registering-users.md:69
+msgid "If you're using the [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) and your existing homeserver (most likely [Synapse](./configuring-playbook-synapse.md)) is delegating authentication to it, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
+msgstr ""
+
+#: ../../../docs/registering-users.md:77
+msgid "This `register-user` script actually invokes the `mas-cli manage register-user` command under the hood. If you'd like more control over the registration process, consider invoking the `mas-cli` command directly:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:83
+msgid "⚠️ **Warning**: Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information."
+msgstr ""
+
+#: ../../../docs/registering-users.md:85
+msgid "Managing users via a Web UI"
+msgstr ""
+
+#: ../../../docs/registering-users.md:87
+msgid "To manage users more easily (via a web user-interace), you can install [Synapse Admin](configuring-playbook-synapse-admin.md)."
+msgstr ""
+
+#: ../../../docs/registering-users.md:89
+msgid "⚠️ **Warning**: If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information."
+msgstr ""
+
+#: ../../../docs/registering-users.md:91
+msgid "Letting certain users register on your private server"
+msgstr ""
+
+#: ../../../docs/registering-users.md:93
+msgid "If you'd rather **keep your server private** (public registration closed, as is the default), and **let certain people create accounts by themselves** (instead of creating user accounts manually like this), consider installing and making use of [matrix-registration](configuring-playbook-matrix-registration.md)."
+msgstr ""
+
+#: ../../../docs/registering-users.md:95
+msgid "Enabling public user registration"
+msgstr ""
+
+#: ../../../docs/registering-users.md:97
+msgid "To **open up user registration publicly** (usually **not recommended**), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:99
+msgid "For Synapse:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:105
+msgid "For Dendrite:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:111
+msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:120
+msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
+msgstr ""
+
+#: ../../../docs/registering-users.md:122
+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/registering-users.md:124
+msgid "If you're opening up registrations publicly like this, you might also wish to [configure CAPTCHA protection](configuring-captcha.md)."
+msgstr ""
+
+#: ../../../docs/registering-users.md:126
+msgid "Adding/Removing Administrator privileges to an existing user"
+msgstr ""
+
+#: ../../../docs/registering-users.md:128
+msgid "Adding/Removing Administrator privileges to an existing user in Synapse"
+msgstr ""
+
+#: ../../../docs/registering-users.md:130
+msgid "To change the admin privileges for a user in Synapse's local database, you need to run an SQL query like this against the `synapse` database:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:136
+msgid "where:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:138
+msgid "`ADMIN_VALUE` being either `0` (regular user) or `1` (admin)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:139
+msgid "`USER` and `example.com` pointing to a valid user on your server"
+msgstr ""
+
+#: ../../../docs/registering-users.md:141
+msgid "If you're using the integrated Postgres server and not an [external Postgres server](configuring-playbook-external-postgres.md), you can launch a Postgres into the `synapse` database by:"
+msgstr ""
+
+#: ../../../docs/registering-users.md:143
+msgid "running `/matrix/postgres/bin/cli` - to launch [`psql`](https://www.postgresql.org/docs/current/app-psql.html)"
+msgstr ""
+
+#: ../../../docs/registering-users.md:144
+msgid "running `\\c synapse` - to change to the `synapse` database"
+msgstr ""
+
+#: ../../../docs/registering-users.md:146
+msgid "You can then proceed to run the query above."
+msgstr ""
+
+#: ../../../docs/registering-users.md:148
+msgid "**Note**: directly modifying the raw data of Synapse (or any other software) could cause the software to break. You've been warned!"
+msgstr ""
+
+#: ../../../docs/registering-users.md:150
+msgid "Adding/Removing Administrator privileges to an existing user in Matrix Authentication Service"
+msgstr ""
+
+#: ../../../docs/registering-users.md:152
+msgid "Promoting/demoting a user in Matrix Authentication Service cannot currently (2024-10-19) be done via the [`mas-cli` Management tool](./configuring-playbook-matrix-authentication-service.md#management)."
+msgstr ""
+
+#: ../../../docs/registering-users.md:154
+msgid "You can do it via the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html)'s `POST /api/admin/v1/users/{id}/set-admin` endpoint."
+msgstr ""
diff --git a/i18n/translation-templates/docs/self-building.pot b/i18n/translation-templates/docs/self-building.pot
new file mode 100644
index 000000000..1210370b6
--- /dev/null
+++ b/i18n/translation-templates/docs/self-building.pot
@@ -0,0 +1,173 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/self-building.md:1
+msgid "Self-building"
+msgstr ""
+
+#: ../../../docs/self-building.md:3
+msgid "**Caution: self-building does not have to be used on its own. See the [Alternative Architectures](alternative-architectures.md) page.**"
+msgstr ""
+
+#: ../../../docs/self-building.md:5
+msgid "The playbook supports self-building of various components, which don't have a container image for your architecture (see the [container images we use](container-images.md)). For `amd64`, self-building is not required."
+msgstr ""
+
+#: ../../../docs/self-building.md:7
+msgid "For other architectures (e.g. `arm32`, `arm64`), ready-made container images are used when available. If there's no ready-made image for a specific component and said component supports self-building, an image will be built on the host. Building images like this takes more time and resources (some build tools need to get installed by the playbook to assist building)."
+msgstr ""
+
+#: ../../../docs/self-building.md:9
+msgid "To make use of self-building, you don't need to do anything. If a component has an image for the specified architecture, the playbook will use it directly. If not, it will build the image on the server itself."
+msgstr ""
+
+#: ../../../docs/self-building.md:11
+msgid "Note that **not all components support self-building yet**."
+msgstr ""
+
+#: ../../../docs/self-building.md:13
+msgid "Possibly outdated list of roles where self-building the Docker image is currently possible:"
+msgstr ""
+
+#: ../../../docs/self-building.md:14
+msgid "`matrix-synapse`"
+msgstr ""
+
+#: ../../../docs/self-building.md:15
+msgid "`matrix-synapse-admin`"
+msgstr ""
+
+#: ../../../docs/self-building.md:16
+msgid "`matrix-client-element`"
+msgstr ""
+
+#: ../../../docs/self-building.md:17
+msgid "`matrix-client-hydrogen`"
+msgstr ""
+
+#: ../../../docs/self-building.md:18
+msgid "`matrix-client-cinny`"
+msgstr ""
+
+#: ../../../docs/self-building.md:19
+msgid "`matrix-registration`"
+msgstr ""
+
+#: ../../../docs/self-building.md:20
+msgid "`matrix-coturn`"
+msgstr ""
+
+#: ../../../docs/self-building.md:21
+msgid "`matrix-corporal`"
+msgstr ""
+
+#: ../../../docs/self-building.md:22
+msgid "`matrix-dimension`"
+msgstr ""
+
+#: ../../../docs/self-building.md:23
+msgid "`matrix-ma1sd`"
+msgstr ""
+
+#: ../../../docs/self-building.md:24
+msgid "`exim-relay`"
+msgstr ""
+
+#: ../../../docs/self-building.md:25
+msgid "`matrix-bridge-hookshot`"
+msgstr ""
+
+#: ../../../docs/self-building.md:26
+msgid "`matrix-bridge-appservice-irc`"
+msgstr ""
+
+#: ../../../docs/self-building.md:27
+msgid "`matrix-bridge-appservice-slack`"
+msgstr ""
+
+#: ../../../docs/self-building.md:28
+msgid "`matrix-bridge-appservice-webhooks`"
+msgstr ""
+
+#: ../../../docs/self-building.md:29
+msgid "`matrix-bridge-beeper-linkedin`"
+msgstr ""
+
+#: ../../../docs/self-building.md:30
+msgid "`matrix-bridge-mautrix-facebook`"
+msgstr ""
+
+#: ../../../docs/self-building.md:31
+msgid "`matrix-bridge-mautrix-hangouts`"
+msgstr ""
+
+#: ../../../docs/self-building.md:32
+msgid "`matrix-bridge-mautrix-googlechat`"
+msgstr ""
+
+#: ../../../docs/self-building.md:33
+msgid "`matrix-bridge-mautrix-telegram`"
+msgstr ""
+
+#: ../../../docs/self-building.md:34
+msgid "`matrix-bridge-mautrix-signal`"
+msgstr ""
+
+#: ../../../docs/self-building.md:35
+msgid "`matrix-bridge-mautrix-gmessages`"
+msgstr ""
+
+#: ../../../docs/self-building.md:36
+msgid "`matrix-bridge-mautrix-whatsapp`"
+msgstr ""
+
+#: ../../../docs/self-building.md:37
+msgid "`matrix-bridge-mx-puppet-steam`"
+msgstr ""
+
+#: ../../../docs/self-building.md:38
+msgid "`matrix-bot-mjolnir`"
+msgstr ""
+
+#: ../../../docs/self-building.md:39
+msgid "`matrix-bot-honoroit`"
+msgstr ""
+
+#: ../../../docs/self-building.md:40
+msgid "`matrix-bot-matrix-reminder-bot`"
+msgstr ""
+
+#: ../../../docs/self-building.md:41
+msgid "`matrix-bot-maubot`"
+msgstr ""
+
+#: ../../../docs/self-building.md:42
+msgid "`matrix-email2matrix`"
+msgstr ""
+
+#: ../../../docs/self-building.md:43
+msgid "`matrix-pantalaimon`"
+msgstr ""
+
+#: ../../../docs/self-building.md:45
+msgid "Adding self-building support to other roles is welcome. Feel free to contribute!"
+msgstr ""
+
+#: ../../../docs/self-building.md:47
+msgid "If you'd like **to force self-building** even if an image is available for your architecture, look into the `matrix_*_self_build` variables provided by individual roles."
+msgstr ""
diff --git a/i18n/translation-templates/docs/uninstalling.pot b/i18n/translation-templates/docs/uninstalling.pot
new file mode 100644
index 000000000..5c4b477ab
--- /dev/null
+++ b/i18n/translation-templates/docs/uninstalling.pot
@@ -0,0 +1,77 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/uninstalling.md:1
+msgid "Uninstalling"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:3
+msgid "**Warnings**:"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:5
+msgid "If your server federates with others, make sure to **leave any federated rooms before nuking your Matrix server's data**. Otherwise, the next time you set up a Matrix server for this domain (regardless of the installation method you use), you'll encounter trouble federating."
+msgstr ""
+
+#: ../../../docs/uninstalling.md:7
+msgid "If you have some trouble with your installation, you can just [re-run the playbook](installing.md) and it will try to set things up again. **Uninstalling and then installing anew rarely solves anything**."
+msgstr ""
+
+#: ../../../docs/uninstalling.md:11
+msgid "Uninstalling using a script"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:13
+msgid "Installing places a `/matrix/bin/remove-all` script on the server."
+msgstr ""
+
+#: ../../../docs/uninstalling.md:15
+msgid "You can run it to to have it uninstall things for you automatically (see below). **Use with caution!**"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:17
+msgid "Uninstalling manually"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:19
+msgid "If you prefer to uninstall manually, run these commands (most are meant to be executed on the Matrix server itself):"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:21
+msgid "ensure all Matrix services are stopped: `ansible-playbook -i inventory/hosts setup.yml --tags=stop` (if you can't get Ansible working to run this command, you can run `systemctl stop 'matrix*'` manually on the server)"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:23
+msgid "delete the Matrix-related systemd `.service` and `.timer` files (`rm -f /etc/systemd/system/matrix*.{service,timer}`) and reload systemd (`systemctl daemon-reload`)"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:25
+msgid "delete some cached Docker images (`docker system prune -a`) or just delete them all (`docker rmi $(docker images -aq)`)"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:27
+msgid "delete the Docker networks: `docker network rm matrix matrix-coturn` (might have been deleted already if you ran the `docker system prune` command)"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:29
+msgid "uninstall Docker itself, if necessary"
+msgstr ""
+
+#: ../../../docs/uninstalling.md:31
+msgid "delete the `/matrix` directory (`rm -rf /matrix`)"
+msgstr ""
diff --git a/i18n/translation-templates/docs/updating-users-passwords.pot b/i18n/translation-templates/docs/updating-users-passwords.pot
new file mode 100644
index 000000000..efce7ebd2
--- /dev/null
+++ b/i18n/translation-templates/docs/updating-users-passwords.pot
@@ -0,0 +1,85 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 07:23+0200\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/updating-users-passwords.md:1
+msgid "Updating users passwords"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:3
+msgid "Option 1 (if you are using the integrated Postgres database):"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:5
+msgid "**Notes**:"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:6
+msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:7
+msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:9
+msgid "You can reset a user's password via the Ansible playbook:"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:15
+msgid "**You can then log in with that user** via Element Web that this playbook has created for you at a URL like this: `https://element.example.com/`."
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:17
+msgid "Option 2 (if you are using an external Postgres server):"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:19
+msgid "You can manually generate the password hash by using the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#finalize-the-installation):"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:25
+msgid "and then connecting to the postgres server and executing:"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:31
+msgid "where `<password-hash>` is the hash returned by the docker command above."
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:33
+msgid "Option 3:"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:35
+msgid "Use the Synapse User Admin API as described here: https://github.com/element-hq/synapse/blob/master/docs/admin_api/user_admin_api.rst#reset-password"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:37
+msgid "This requires an [access token](obtaining-access-tokens.md) from a server admin account. *This method will also log the user out of all of their clients while the other options do not.*"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:39
+msgid "If you didn't make your account a server admin when you created it, you can learn how to switch it now by reading about it in [Adding/Removing Administrator privileges to an existing user in Synapse](registering-users.md#addingremoving-administrator-privileges-to-an-existing-user-in-synapse)."
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:41
+msgid "Example:"
+msgstr ""
+
+#: ../../../docs/updating-users-passwords.md:43
+msgid "To set @alice:example.com's password to `correct_horse_battery_staple` you could use this curl command:"
+msgstr ""
diff --git a/i18n/translation-templates/i18n/README.pot b/i18n/translation-templates/i18n/README.pot
new file mode 100644
index 000000000..4f94ba62b
--- /dev/null
+++ b/i18n/translation-templates/i18n/README.pot
@@ -0,0 +1,216 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2018-2024, 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: 2024-12-20 15:27+0200\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"
+
+#: ../../README.md:8
+msgid "Internationalization"
+msgstr ""
+
+#: ../../README.md:10
+msgid "Translated documentation files are published and maintained in [`translations/`](translations/) directory."
+msgstr ""
+
+#: ../../README.md:12
+msgid "Currently, we support translation of:"
+msgstr ""
+
+#: ../../README.md:14
+msgid "Markdown files found at the top level project directory"
+msgstr ""
+
+#: ../../README.md:15
+msgid "Markdown files found in the [`docs`](../docs/) directory (this is where the bulk of the documentation is)"
+msgstr ""
+
+#: ../../README.md:16
+msgid "this current document in the `i18n` directory"
+msgstr ""
+
+#: ../../README.md:18
+msgid "💡 For readers' sake, we only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold (requiring that at least the project README and core installation guides are translated)."
+msgstr ""
+
+#: ../../README.md:20
+msgid "Organization of this `i18n` directory is as follows:"
+msgstr ""
+
+#: ../../README.md:22
+msgid "[PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES): a list of languages that we publish translations for (in the [translations/](translations/) directory)"
+msgstr ""
+
+#: ../../README.md:23
+msgid "[.gitignore](.gitignore): a list of files and directories to ignore in the `i18n` directory. We intentionaly ignore translated results (`translations/<language>` directories) for languages taht are still in progress. We only [publish translations in a new language](#publish-translations-in-a-new-language) when the translation progresses beyond a certain threshold."
+msgstr ""
+
+#: ../../README.md:24
+msgid "[justfile](justfile): a list of recipes for [just](https://github.com/casey/just) command runner"
+msgstr ""
+
+#: ../../README.md:25
+msgid "[requirements.txt](requirements.txt): a list of Python packages required to work with translations"
+msgstr ""
+
+#: ../../README.md:26
+msgid "[translation-templates/](translation-templates/): a list of English translation templates - strings extracted from Markdown files"
+msgstr ""
+
+#: ../../README.md:27
+msgid "[locales/](locales/): localization files for languages"
+msgstr ""
+
+#: ../../README.md:28
+msgid "[translations/](translations/): translated documents for published languages (see [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) and [publish translations in a new language](#publish-translations-in-a-new-language))"
+msgstr ""
+
+#: ../../README.md:30
+msgid "Guide for translators"
+msgstr ""
+
+#: ../../README.md:32
+msgid "This project uses [Sphinx](https://www.sphinx-doc.org/) to generate translated documents."
+msgstr ""
+
+#: ../../README.md:34
+msgid "For details about using Sphinx for translation, refer [this official document](https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) as well."
+msgstr ""
+
+#: ../../README.md:36
+msgid "For now, translations are handled manually by editing `.po` files in the `locales/<language>` directory. In the future, we plan on integrating with [Weblate](https://weblate.org/) to allow for translating from a web interface."
+msgstr ""
+
+#: ../../README.md:38
+msgid "(Recommended) Using the uv package manager and just command runner"
+msgstr ""
+
+#: ../../README.md:40
+msgid "If you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed, you can use our [justfile](justfile) recipes to easily manage translation files and build translated documents."
+msgstr ""
+
+#: ../../README.md:42
+msgid "The recipes will use [uv](https://github.com/astral-sh/uv) to auto-create [a Python virtual environment](https://docs.astral.sh/uv/pip/environments/) in the `.venv` directory and install the required Python packages (as per [requirements.txt](requirements.txt)) to it."
+msgstr ""
+
+#: ../../README.md:44
+#: ../../README.md:71
+msgid "Preparation"
+msgstr ""
+
+#: ../../README.md:46
+msgid "Make sure you have the [uv](https://docs.astral.sh/uv/) package manager and [just](https://github.com/casey/just) command runner installed."
+msgstr ""
+
+#: ../../README.md:48
+#: ../../README.md:79
+msgid "Translation"
+msgstr ""
+
+#: ../../README.md:50
+#: ../../README.md:81
+msgid "Recommended flow when working on a new language (replace `<language>` with the language code, e.g. `bg`):"
+msgstr ""
+
+#: ../../README.md:52
+msgid "Update the locale files for your language: `just sync-for-language <language>` (internally, this automatically runs `just extract-translation-templates` to make sure the translation templates are up-to-date)"
+msgstr ""
+
+#: ../../README.md:54
+#: ../../README.md:87
+msgid "Use an editor to translate the files in the `locales/<language>` directory"
+msgstr ""
+
+#: ../../README.md:56
+msgid "Build translated documents: `just build-for-language <language>`"
+msgstr ""
+
+#: ../../README.md:58
+#: ../../README.md:91
+msgid "Preview the result in the `translations/<language>` directory"
+msgstr ""
+
+#: ../../README.md:60
+#: ../../README.md:93
+msgid "Commit your changes done to the `locales/<language>` directory"
+msgstr ""
+
+#: ../../README.md:62
+#: ../../README.md:95
+msgid "If you have progressed with the translation beyond a certain threshold, consider [Publishing translations in a new language](#publish-translations-in-a-new-language)"
+msgstr ""
+
+#: ../../README.md:64
+msgid "Using any other package manager and manual scripts"
+msgstr ""
+
+#: ../../README.md:66
+msgid "If you cannot use [uv](https://docs.astral.sh/uv/) and/or [just](https://github.com/casey/just), you can:"
+msgstr ""
+
+#: ../../README.md:68
+msgid "manage Python packages in another way ([pip](https://pip.pypa.io/en/stable/), [Poetry](https://python-poetry.org/), etc.)"
+msgstr ""
+
+#: ../../README.md:69
+msgid "manage translation strings and build translated documents manually by invoking scripts from the [bin](bin/) directory"
+msgstr ""
+
+#: ../../README.md:73
+msgid "virtualenv and pip"
+msgstr ""
+
+#: ../../README.md:75
+msgid "Create a Python virtual environment in the `.venv` directory: `virtualenv .venv`"
+msgstr ""
+
+#: ../../README.md:76
+msgid "Activate the virtual environment: `source .venv/bin/activate`"
+msgstr ""
+
+#: ../../README.md:77
+msgid "Install the required Python packages using [pip](https://pip.pypa.io/en/stable/): `pip install -r requirements.txt`"
+msgstr ""
+
+#: ../../README.md:83
+msgid "Ensure the English translation templates ([translation-templates/](translation-templates/)) are extracted: `./bin/extract-translation-templates.sh`"
+msgstr ""
+
+#: ../../README.md:85
+msgid "Update the locale files for your language: `./bin/sync-translation-templates-to-locales.sh <language>`"
+msgstr ""
+
+#: ../../README.md:89
+msgid "Build translated documents: `./bin/build-translated-result.sh <language>`"
+msgstr ""
+
+#: ../../README.md:97
+msgid "Publish translations in a new language"
+msgstr ""
+
+#: ../../README.md:99
+msgid "To publish prebuilt documents translated in a new language to the `translations/<language>` directory:"
+msgstr ""
+
+#: ../../README.md:101
+msgid "add its language code to the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file"
+msgstr ""
+
+#: ../../README.md:102
+msgid "whitelist its `translations/<language>` directory by adding a `!translations/<language>` rule to the [.gitignore](.gitignore) file"
+msgstr ""
+
+#: ../../README.md:104
+msgid "💡 Leave a trailing new line at the end of the [PUBLISHED_LANGUAGES](PUBLISHED_LANGUAGES) file."
+msgstr ""
diff --git a/justfile b/justfile
index 95a8e1006..ca57d6143 100644
--- a/justfile
+++ b/justfile
@@ -1,6 +1,6 @@
 # Shows help
 default:
-    @just --list --justfile {{ justfile() }}
+    @{{ just_executable() }} --list --justfile {{ justfile() }}
 
 # Pulls external Ansible roles
 roles:
@@ -17,18 +17,18 @@ roles:
 update *flags: update-playbook-only
     #!/usr/bin/env sh
     if [ -x "$(command -v agru)" ]; then
-        echo {{ if flags == "" { "Installing roles pinned in requirements.yml..." } else if flags == "-u" { "Updating roles and pinning new versions in requirements.yml..." } else { "Unknown flags passed" } }}
+        echo {{ if flags == "" { "Installing roles pinned in requirements.yml…" } else { if flags == "-u" { "Updating roles and pinning new versions in requirements.yml…" } else { "Unknown flags passed" } } }}
         agru {{ flags }}
     else
         echo "[NOTE] You are using the standard ansible-galaxy tool to install roles, which is slow and lacks other features. We recommend installing the 'agru' tool to speed up the process: https://github.com/etkecc/agru#where-to-get"
-        echo "Installing roles..."
+        echo "Installing roles…"
         rm -rf roles/galaxy
         ansible-galaxy install -r requirements.yml -p roles/galaxy/ --force
     fi
 
 # Updates the playbook without installing/updating Ansible roles
 update-playbook-only:
-    @echo "Updating playbook..."
+    @echo "Updating playbook…"
     @git stash -q
     @git pull -q
     @-git stash pop -q
@@ -42,7 +42,7 @@ install-all *extra_args: (run-tags "install-all,ensure-matrix-users-created,star
 
 # Runs installation tasks for a single service
 install-service service *extra_args:
-    just --justfile {{ justfile() }} run \
+    {{ just_executable() }} --justfile {{ justfile() }} run \
     --tags=install-{{ service }},start-group \
     --extra-vars=group={{ service }} \
     --extra-vars=devture_systemd_service_manager_service_restart_mode=one-by-one {{ extra_args }}
@@ -56,7 +56,7 @@ run +extra_args:
 
 # Runs the playbook with the given list of comma-separated tags and optional arguments
 run-tags tags *extra_args:
-    just --justfile {{ justfile() }} run --tags={{ tags }} {{ extra_args }}
+    {{ just_executable() }} --justfile {{ justfile() }} run --tags={{ tags }} {{ extra_args }}
 
 # Runs the playbook in user-registration mode
 register-user username password admin_yes_or_no *extra_args:
@@ -67,14 +67,14 @@ start-all *extra_args: (run-tags "start-all" extra_args)
 
 # Starts a specific service group
 start-group group *extra_args:
-    @just --justfile {{ justfile() }} run-tags start-group --extra-vars="group={{ group }}" {{ extra_args }}
+    @{{ just_executable() }} --justfile {{ justfile() }} run-tags start-group --extra-vars="group={{ group }}" {{ extra_args }}
 
 # Stops all services
 stop-all *extra_args: (run-tags "stop-all" extra_args)
 
 # Stops a specific service group
 stop-group group *extra_args:
-    @just --justfile {{ justfile() }} run-tags stop-group --extra-vars="group={{ group }}" {{ extra_args }}
+    @{{ just_executable() }} --justfile {{ justfile() }} run-tags stop-group --extra-vars="group={{ group }}" {{ extra_args }}
 
 # Rebuilds the mautrix-meta-instagram Ansible role using the mautrix-meta-messenger role as a source
 rebuild-mautrix-meta-instagram:
diff --git a/requirements.yml b/requirements.yml
index 8a4d68466..889643e58 100644
--- a/requirements.yml
+++ b/requirements.yml
@@ -1,37 +1,37 @@
 ---
 
 - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-aux.git
-  version: v1.0.0-3
+  version: v1.0.0-5
   name: auxiliary
 - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-backup_borg.git
-  version: v1.2.8-1.8.13-0
+  version: v1.4.0-1.9.6-0
   name: backup_borg
 - src: git+https://github.com/devture/com.devture.ansible.role.container_socket_proxy.git
   version: v0.2.0-0
   name: container_socket_proxy
 - src: git+https://github.com/geerlingguy/ansible-role-docker
-  version: 7.4.1
+  version: 7.4.4
   name: docker
 - src: git+https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python.git
   version: 129c8590e106b83e6f4c259649a613c6279e937a
   name: docker_sdk_for_python
 - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-etherpad.git
-  version: v2.2.5-0
+  version: v2.2.6-0
   name: etherpad
 - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay.git
-  version: v4.98-r0-1-1
+  version: v4.98-r0-3-0
   name: exim_relay
 - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-grafana.git
-  version: v11.2.2-0
+  version: v11.4.0-0
   name: grafana
 - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-jitsi.git
-  version: v9779-0
+  version: v9955-0
   name: jitsi
 - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-keydb.git
   version: v6.3.4-3
   name: keydb
 - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-ntfy.git
-  version: v2.10.0-2
+  version: v2.11.0-0
   name: ntfy
 - src: git+https://github.com/devture/com.devture.ansible.role.playbook_help.git
   version: 201c939eed363de269a83ba29784fc3244846048
@@ -43,13 +43,13 @@
   version: ff2fd42e1c1a9e28e3312bbd725395f9c2fc7f16
   name: playbook_state_preserver
 - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-postgres.git
-  version: v17.0-1
+  version: v17.2-0
   name: postgres
 - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-postgres-backup.git
-  version: v16-0
+  version: v17-0
   name: postgres_backup
 - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus.git
-  version: v2.54.1-1
+  version: v2.55.1-0
   name: prometheus
 - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-prometheus-node-exporter.git
   version: v1.8.2-2
@@ -70,8 +70,11 @@
   version: v1.0.0-0
   name: timesync
 - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik.git
-  version: v3.1.3-2
+  version: v3.3.2-0
   name: traefik
 - src: git+https://github.com/mother-of-all-self-hosting/ansible-role-traefik-certs-dumper.git
   version: v2.8.3-5
   name: traefik_certs_dumper
+- src: git+https://github.com/mother-of-all-self-hosting/ansible-role-valkey.git
+  version: v8.0.1-0
+  name: valkey
diff --git a/reuse.toml b/reuse.toml
new file mode 100644
index 000000000..77ad4587b
--- /dev/null
+++ b/reuse.toml
@@ -0,0 +1,25 @@
+# SPDX-FileCopyrightText: 2024 Suguru Hirahara
+#
+# SPDX-License-Identifier: AGPL-3.0-or-later
+
+version = 1
+
+# Computer-generated files and other files which cannot be copyrighted
+[[annotations]]
+path = [
+    "i18n/.gitignore",
+    "i18n/requirements.txt",
+    "i18n/PUBLISHED_LANGUAGES"
+]
+SPDX-FileCopyrightText = "NONE"
+SPDX-License-Identifier = "CC0-1.0"
+
+# See https://reuse.software/faq/#aggregate-info
+[[annotations]]
+path = [
+    "i18n/**/*.po",
+    "i18n/**/*.pot"
+]
+precedence = "aggregate"
+SPDX-FileCopyrightText = "Slavi Pantaleev, MDAD community members"
+SPDX-License-Identifier = "AGPL-3.0-or-later"
diff --git a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml
index a78dfaf4b..05e9c9705 100644
--- a/roles/custom/matrix-alertmanager-receiver/defaults/main.yml
+++ b/roles/custom/matrix-alertmanager-receiver/defaults/main.yml
@@ -6,7 +6,7 @@
 matrix_alertmanager_receiver_enabled: true
 
 # renovate: datasource=docker depName=docker.io/metio/matrix-alertmanager-receiver
-matrix_alertmanager_receiver_version: 2024.10.23
+matrix_alertmanager_receiver_version: 2024.12.18
 
 matrix_alertmanager_receiver_scheme: https
 
diff --git a/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml b/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml
index 0242edbda..0d2a0f575 100644
--- a/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml
+++ b/roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml
@@ -5,7 +5,7 @@
 matrix_appservice_draupnir_for_all_enabled: true
 
 # renovate: datasource=docker depName=gnuxie/draupnir
-matrix_appservice_draupnir_for_all_version: "1.87.0"
+matrix_appservice_draupnir_for_all_version: "v2.0.1"
 
 matrix_appservice_draupnir_for_all_container_image_self_build: false
 matrix_appservice_draupnir_for_all_container_image_self_build_repo: "https://github.com/the-draupnir-project/Draupnir.git"
@@ -40,7 +40,7 @@ matrix_appservice_draupnir_for_all_systemd_wanted_services_list: []
 # The room ID where people can use the bot. The bot has no access controls, so
 # anyone in this room can use the bot - secure your room!
 # This should be a room alias - not a matrix.to URL.
-# Note: draupnir is fairly verbose - expect a lot of messages from it.
+# Note: Draupnir is fairly verbose - expect a lot of messages from it.
 # This room is diffrent for Appservice Mode compared to normal mode.
 # In Appservice mode it provides functions like user management.
 matrix_appservice_draupnir_for_all_master_control_room_alias: ""
diff --git a/roles/custom/matrix-appservice-draupnir-for-all/tasks/setup_install.yml b/roles/custom/matrix-appservice-draupnir-for-all/tasks/setup_install.yml
index 1e716f264..6dc2bf95e 100644
--- a/roles/custom/matrix-appservice-draupnir-for-all/tasks/setup_install.yml
+++ b/roles/custom/matrix-appservice-draupnir-for-all/tasks/setup_install.yml
@@ -17,7 +17,7 @@
     - {path: "{{ matrix_appservice_draupnir_for_all_docker_src_files_path }}", when: "{{ matrix_appservice_draupnir_for_all_container_image_self_build }}"}
   when: "item.when | bool"
 
-- name: Ensure draupnir Docker image is pulled
+- name: Ensure Draupnir Docker image is pulled
   community.docker.docker_image:
     name: "{{ matrix_appservice_draupnir_for_all_docker_image }}"
     source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}"
@@ -29,7 +29,7 @@
   delay: "{{ devture_playbook_help_container_retries_delay }}"
   until: result is not failed
 
-- name: Ensure draupnir repository is present on self-build
+- name: Ensure Draupnir repository is present on self-build
   ansible.builtin.git:
     repo: "{{ matrix_appservice_draupnir_for_all_container_image_self_build_repo }}"
     dest: "{{ matrix_appservice_draupnir_for_all_docker_src_files_path }}"
@@ -40,7 +40,7 @@
   register: matrix_appservice_draupnir_for_all_git_pull_results
   when: "matrix_appservice_draupnir_for_all_container_image_self_build | bool"
 
-- name: Ensure draupnir Docker image is built
+- name: Ensure Draupnir Docker image is built
   community.docker.docker_image:
     name: "{{ matrix_appservice_draupnir_for_all_docker_image }}"
     source: build
diff --git a/roles/custom/matrix-appservice-draupnir-for-all/templates/production-bots.yaml.j2 b/roles/custom/matrix-appservice-draupnir-for-all/templates/production-bots.yaml.j2
index a40d7a105..46a7b4549 100644
--- a/roles/custom/matrix-appservice-draupnir-for-all/templates/production-bots.yaml.j2
+++ b/roles/custom/matrix-appservice-draupnir-for-all/templates/production-bots.yaml.j2
@@ -4,20 +4,10 @@
 # This should be at INFO or DEBUG in order to get support for Draupnir problems.
 logLevel: "INFO"
 
-# Whether or not Draupnir should synchronize policy lists immediately after startup.
-# Equivalent to running '!draupnir sync'.
-syncOnStartup: true
-
 # Whether or not Draupnir should check moderation permissions in all protected rooms on startup.
 # Equivalent to running `!draupnir verify`.
 verifyPermissionsOnStartup: true
 
-# Whether Draupnir should check member lists quicker (by using a different endpoint),
-# keep in mind that enabling this will miss invited (but not joined) users.
-#
-# Turn on if your bot is in (very) large rooms, or in large amounts of rooms.
-fasterMembershipChecks: false
-
 # A case-insensitive list of ban reasons to have the bot also automatically redact the user's messages for.
 #
 # If the bot sees you ban a user with a reason that is an (exact case-insensitive) match to this list,
@@ -70,14 +60,10 @@ commands:
     - "draupnir_bot"
     - "draupnir"
 
-  # Whether or not commands with a wildcard (*) will require an additional `--force` argument
-  # in the command to be able to be submitted.
-  confirmWildcardBan: true
-
   # The default reasons to be prompted with if the reason is missing from a ban command.
   ban:
-    defaultReasons: 
+    defaultReasons:
       - "spam"
       - "brigading"
       - "harassment"
-      - "disagreement"
\ No newline at end of file
+      - "disagreement"
diff --git a/roles/custom/matrix-base/defaults/main.yml b/roles/custom/matrix-base/defaults/main.yml
index 90fe71a53..e70328a40 100644
--- a/roles/custom/matrix-base/defaults/main.yml
+++ b/roles/custom/matrix-base/defaults/main.yml
@@ -1,7 +1,7 @@
 ---
 
 # The bare domain name which represents your Matrix identity.
-# Matrix user ids for your server will be of the form (`@user:example.com`).
+# Matrix user IDs for your server will be of the form (`@alice:example.com`).
 #
 # Note: this playbook does not touch the server referenced here.
 # Installation happens on another server ("matrix.example.com", see `matrix_server_fqn_matrix`).
@@ -10,7 +10,7 @@
 matrix_domain: ~
 
 # The optional Matrix admin MXID, used in bridges' configs to set bridge admin user
-# Example value: "@someone:{{ matrix_domain }}"
+# Example value: "@alice:{{ matrix_domain }}"
 matrix_admin: ''
 
 # Global var to enable/disable encryption across all bridges with encryption support
@@ -49,12 +49,12 @@ matrix_monitoring_container_network: matrix-monitoring
 matrix_homeserver_enabled: true
 
 # This will contain the homeserver implementation that is in use.
-# Valid values: synapse, dendrite, conduit
+# Valid values: synapse, dendrite, conduit, conduwuit
 #
 # By default, we use Synapse, because it's the only full-featured Matrix server at the moment.
 #
 # This value automatically influences other variables (`matrix_synapse_enabled`, `matrix_dendrite_enabled`, etc.).
-# The homeserver implementation of an existing server cannot be changed without data loss.
+# Note that the homeserver implementation of a server will not be able to be changed without data loss.
 matrix_homeserver_implementation: synapse
 
 # This contains a secret, which is used for generating various other secrets later on.
@@ -67,7 +67,7 @@ matrix_server_fqn_matrix: "matrix.{{ matrix_domain }}"
 # This is where you access federation API.
 matrix_server_fqn_matrix_federation: '{{ matrix_server_fqn_matrix }}'
 
-# This is where you access the Element web UI from (if enabled via matrix_client_element_enabled; enabled by default).
+# This is where you access the Element Web from (if enabled via matrix_client_element_enabled; enabled by default).
 # This and the Matrix FQN (see above) are expected to be on the same server.
 matrix_server_fqn_element: "element.{{ matrix_domain }}"
 
@@ -77,10 +77,10 @@ matrix_server_fqn_hydrogen: "hydrogen.{{ matrix_domain }}"
 # This is where you access the Cinny web client from (if enabled via matrix_client_cinny_enabled; disabled by default).
 matrix_server_fqn_cinny: "cinny.{{ matrix_domain }}"
 
-# This is where you access the SchildiChat web client from (if enabled via matrix_client_schildichat_enabled; disabled by default).
+# This is where you access the SchildiChat Web from (if enabled via matrix_client_schildichat_enabled; disabled by default).
 matrix_server_fqn_schildichat: "schildichat.{{ matrix_domain }}"
 
-# This is where you access the buscarron bot from (if enabled via matrix_bot_buscarron_enabled; disabled by default).
+# This is where you access the Buscarron bot from (if enabled via matrix_bot_buscarron_enabled; disabled by default).
 matrix_server_fqn_buscarron: "buscarron.{{ matrix_domain }}"
 
 # This is where you access the Dimension.
@@ -234,11 +234,18 @@ matrix_metrics_exposure_http_basic_auth_users: ''
 matrix_playbook_reverse_proxy_type: ''
 
 # Specifies the network that the reverse-proxy is operating at
-matrix_playbook_reverse_proxy_container_network: 'traefik'
+matrix_playbook_reverse_proxy_container_network: "{{ 'traefik' if matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] else '' }}"
 
 # Specifies the hostname that the reverse-proxy is available at
 matrix_playbook_reverse_proxy_hostname: 'matrix-traefik'
 
+# Specifies whether the Traefik reverse-proxy (if `matrix_playbook_reverse_proxy_type` indicates that Traefik is being used) defines a compression middleware.
+matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled: false
+
+# Specifies the name of the compression middleware defined for the Traefik reverse-proxy (if `matrix_playbook_reverse_proxy_type` indicates that Traefik is being used).
+# It's better to use a fully-qualified middleware name (e.g. `compression@docker` or `compression@file`) here to prevent ambiguity.
+matrix_playbook_reverse_proxy_traefik_middleware_compression_name: ''
+
 # Controls the additional network that reverse-proxyable services will be connected to.
 matrix_playbook_reverse_proxyable_services_additional_network: "{{ matrix_playbook_reverse_proxy_container_network }}"
 
@@ -267,11 +274,38 @@ matrix_playbook_public_matrix_federation_api_traefik_entrypoint_host_bind_port_u
 matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config: "{{ (matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_default | combine (matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_auto)) | combine(matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_custom, recursive=True) }}"
 matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_http3_enabled: true
 matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_http3_advertisedPort: "{{ matrix_playbook_public_matrix_federation_api_traefik_entrypoint_port }}"  # noqa var-naming
+matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_readTimeout: "{{ traefik_config_entrypoint_web_secure_transport_respondingTimeouts_readTimeout }}"  # noqa var-naming
+matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_writeTimeout: "{{ traefik_config_entrypoint_web_secure_transport_respondingTimeouts_writeTimeout }}"  # noqa var-naming
+matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_idleTimeout: "{{ traefik_config_entrypoint_web_secure_transport_respondingTimeouts_idleTimeout }}"  # noqa var-naming
 matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_default: |
   {{
-    ({'http3': {'advertisedPort': matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_http3_advertisedPort | int}})
-    if matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_http3_enabled
-    else {}
+    {}
+
+    | combine(
+      (
+        (
+          {
+            'http3': {
+              'advertisedPort': matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_http3_advertisedPort | int
+            }
+          }
+        )
+        if matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_http3_enabled
+        else {}
+      )
+    )
+
+    | combine(
+      {
+        'transport': {
+          'respondingTimeouts': {
+            'readTimeout': matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_readTimeout,
+            'writeTimeout': matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_writeTimeout,
+            'idleTimeout': matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_transport_respondingTimeouts_idleTimeout,
+          }
+        }
+      }
+    )
   }}
 matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_auto: {}
 matrix_playbook_public_matrix_federation_api_traefik_entrypoint_config_custom: {}
diff --git a/roles/custom/matrix-base/tasks/validate_config.yml b/roles/custom/matrix-base/tasks/validate_config.yml
index fd389cd1c..41320a5fb 100644
--- a/roles/custom/matrix-base/tasks/validate_config.yml
+++ b/roles/custom/matrix-base/tasks/validate_config.yml
@@ -3,7 +3,7 @@
 - name: Fail if invalid homeserver implementation
   ansible.builtin.fail:
     msg: "You need to set a valid homeserver implementation in `matrix_homeserver_implementation`"
-  when: "matrix_homeserver_implementation not in ['synapse', 'dendrite', 'conduit']"
+  when: "matrix_homeserver_implementation not in ['synapse', 'dendrite', 'conduit', 'conduwuit']"
 
 - name: (Deprecation) Catch and report renamed settings
   ansible.builtin.fail:
diff --git a/roles/custom/matrix-base/templates/bin/remove-all.j2 b/roles/custom/matrix-base/templates/bin/remove-all.j2
index 0a557c245..5a0579586 100644
--- a/roles/custom/matrix-base/templates/bin/remove-all.j2
+++ b/roles/custom/matrix-base/templates/bin/remove-all.j2
@@ -6,7 +6,7 @@ if [ "$(id -u)" != "0" ]; then
 	exit 1
 fi
 
-echo "WARNING! You are about to remove everything the playbook installs for {{ matrix_server_fqn_matrix }}: matrix, docker images,..."
+echo "WARNING! You are about to remove everything the playbook installs for {{ matrix_server_fqn_matrix }}: matrix, docker images, …"
 echo -n "If you're sure you want to do this, type: 'Yes, I really want to remove everything!'"
 read sure
 
diff --git a/roles/custom/matrix-bot-baibot/defaults/main.yml b/roles/custom/matrix-bot-baibot/defaults/main.yml
index 21a576d08..fba1cd908 100644
--- a/roles/custom/matrix-bot-baibot/defaults/main.yml
+++ b/roles/custom/matrix-bot-baibot/defaults/main.yml
@@ -11,7 +11,7 @@ matrix_bot_baibot_container_repo_version: "{{ 'main' if matrix_bot_baibot_versio
 matrix_bot_baibot_container_src_files_path: "{{ matrix_base_data_path }}/baibot/container-src"
 
 # renovate: datasource=docker depName=ghcr.io/etkecc/baibot
-matrix_bot_baibot_version: v1.3.1
+matrix_bot_baibot_version: v1.4.1
 matrix_bot_baibot_container_image: "{{ matrix_bot_baibot_container_image_name_prefix }}etkecc/baibot:{{ matrix_bot_baibot_version }}"
 matrix_bot_baibot_container_image_name_prefix: "{{ 'localhost/' if matrix_bot_baibot_container_image_self_build else 'ghcr.io/' }}"
 matrix_bot_baibot_container_image_force_pull: "{{ matrix_bot_baibot_container_image.endswith(':latest') }}"
diff --git a/roles/custom/matrix-bot-buscarron/defaults/main.yml b/roles/custom/matrix-bot-buscarron/defaults/main.yml
index 052f619e7..e8e2fa3e9 100644
--- a/roles/custom/matrix-bot-buscarron/defaults/main.yml
+++ b/roles/custom/matrix-bot-buscarron/defaults/main.yml
@@ -1,6 +1,6 @@
 ---
 
-# buscarron is a Web forms (HTTP POST) to Matrix service.
+# Buscarron is a Web forms (HTTP POST) to Matrix service.
 # Project source code URL: https://github.com/etkecc/buscarron
 
 matrix_bot_buscarron_enabled: true
@@ -186,7 +186,7 @@ matrix_bot_buscarron_smtp_from: ''
 # enforce SMTP validation
 matrix_bot_buscarron_smtp_validation: false
 
-# Additional environment variables to pass to the buscarron container
+# Additional environment variables to pass to the Buscarron container
 #
 # Example:
 # matrix_bot_buscarron_environment_variables_extension: |
diff --git a/roles/custom/matrix-bot-buscarron/tasks/setup_install.yml b/roles/custom/matrix-bot-buscarron/tasks/setup_install.yml
index 7742ab726..a011a016b 100644
--- a/roles/custom/matrix-bot-buscarron/tasks/setup_install.yml
+++ b/roles/custom/matrix-bot-buscarron/tasks/setup_install.yml
@@ -26,7 +26,7 @@
         - ansible.builtin.set_fact:
             matrix_bot_buscarron_requires_restart: true
 
-- name: Ensure buscarron paths exist
+- name: Ensure Buscarron paths exist
   ansible.builtin.file:
     path: "{{ item.path }}"
     state: directory
@@ -40,7 +40,7 @@
     - {path: "{{ matrix_bot_buscarron_docker_src_files_path }}", when: true}
   when: "item.when | bool"
 
-- name: Ensure buscarron support files installed
+- name: Ensure Buscarron support files installed
   ansible.builtin.template:
     src: "{{ role_path }}/templates/{{ item }}.j2"
     dest: "{{ matrix_bot_buscarron_config_path }}/{{ item }}"
@@ -51,7 +51,7 @@
     - env
     - labels
 
-- name: Ensure buscarron image is pulled
+- name: Ensure Buscarron image is pulled
   community.docker.docker_image:
     name: "{{ matrix_bot_buscarron_docker_image }}"
     source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}"
@@ -63,7 +63,7 @@
   delay: "{{ devture_playbook_help_container_retries_delay }}"
   until: result is not failed
 
-- name: Ensure buscarron repository is present on self-build
+- name: Ensure Buscarron repository is present on self-build
   ansible.builtin.git:
     repo: "{{ matrix_bot_buscarron_docker_repo }}"
     version: "{{ matrix_bot_buscarron_docker_repo_version }}"
@@ -74,7 +74,7 @@
   register: matrix_bot_buscarron_git_pull_results
   when: "matrix_bot_buscarron_container_image_self_build | bool"
 
-- name: Ensure buscarron image is built
+- name: Ensure Buscarron image is built
   community.docker.docker_image:
     name: "{{ matrix_bot_buscarron_docker_image }}"
     source: build
@@ -92,7 +92,7 @@
     dest: "{{ devture_systemd_docker_base_systemd_path }}/matrix-bot-buscarron.service"
     mode: 0644
 
-- name: Ensure buscarron container network is created
+- name: Ensure Buscarron container network is created
   community.general.docker_network:
     enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}"
     name: "{{ matrix_bot_buscarron_container_network }}"
diff --git a/roles/custom/matrix-bot-buscarron/tasks/setup_uninstall.yml b/roles/custom/matrix-bot-buscarron/tasks/setup_uninstall.yml
index 26d920f48..7a47471ef 100644
--- a/roles/custom/matrix-bot-buscarron/tasks/setup_uninstall.yml
+++ b/roles/custom/matrix-bot-buscarron/tasks/setup_uninstall.yml
@@ -19,7 +19,7 @@
         path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-bot-buscarron.service"
         state: absent
 
-    - name: Ensure Matrix buscarron paths don't exist
+    - name: Ensure Matrix Buscarron paths don't exist
       ansible.builtin.file:
         path: "{{ matrix_bot_buscarron_base_path }}"
         state: absent
diff --git a/roles/custom/matrix-bot-chatgpt/defaults/main.yml b/roles/custom/matrix-bot-chatgpt/defaults/main.yml
index 0cd01b518..50ca9c286 100644
--- a/roles/custom/matrix-bot-chatgpt/defaults/main.yml
+++ b/roles/custom/matrix-bot-chatgpt/defaults/main.yml
@@ -57,7 +57,7 @@ matrix_bot_chatgpt_keyv_bot_storage: true
 # Matrix Static Settings (required, see notes)
 # Defaults to "https://matrix.org"
 matrix_bot_chatgpt_matrix_homeserver_url: ""  # MATRIX_HOMESERVER_URL=
-# With the @ and :example.com, ie @SOMETHING:example.com, needs to be set, created manually beforehand.
+# With the @ and :example.com, ie @bot.chatgpt:example.com, needs to be set, created manually beforehand.
 matrix_bot_chatgpt_matrix_bot_username_localpart: 'bot.chatgpt'
 matrix_bot_chatgpt_matrix_bot_username: "@{{ matrix_bot_chatgpt_matrix_bot_username_localpart }}:{{ matrix_domain }}"  # MATRIX_BOT_USERNAME=
 # Set `MATRIX_BOT_PASSWORD` the bot will print an `MATRIX_ACCESS_TOKEN` to the terminal
@@ -87,8 +87,8 @@ matrix_bot_chatgpt_matrix_rich_text: true  # MATRIX_RICH_TEXT=true
 # A list of admins
 # Example set of rules:
 # matrix_bot_chatgpt_admins:
-# - @someone:example.com
-# - @another:example.com
+# - @alice:example.com
+# - @bob:example.com
 # - @bot.*:example.com
 # - @*:example.net
 # matrix_bot_chatgpt_admins: "{{ [matrix_admin] if matrix_admin else [] }}"
diff --git a/roles/custom/matrix-bot-chatgpt/templates/env.j2 b/roles/custom/matrix-bot-chatgpt/templates/env.j2
index a6f62cc67..375ef18f2 100644
--- a/roles/custom/matrix-bot-chatgpt/templates/env.j2
+++ b/roles/custom/matrix-bot-chatgpt/templates/env.j2
@@ -10,7 +10,7 @@ KEYV_URL={{ matrix_bot_chatgpt_keyv_url }}
 KEYV_BOT_ENCRYPTION={{ matrix_bot_chatgpt_keyv_bot_encryption|lower }}
 KEYV_BOT_STORAGE={{ matrix_bot_chatgpt_keyv_bot_storage|lower }}
 
-# With the @ and :example.com, ie @SOMETHING:example.com
+# With the @ and :example.com, ie @bot.chatgpt:example.com
 MATRIX_BOT_USERNAME={{ matrix_bot_chatgpt_matrix_bot_username }}
 MATRIX_BOT_PASSWORD={{ matrix_bot_chatgpt_matrix_bot_password }}
 
diff --git a/roles/custom/matrix-bot-draupnir/defaults/main.yml b/roles/custom/matrix-bot-draupnir/defaults/main.yml
index 639632edc..aa4da34f6 100644
--- a/roles/custom/matrix-bot-draupnir/defaults/main.yml
+++ b/roles/custom/matrix-bot-draupnir/defaults/main.yml
@@ -5,7 +5,7 @@
 matrix_bot_draupnir_enabled: true
 
 # renovate: datasource=docker depName=gnuxie/draupnir
-matrix_bot_draupnir_version: "v1.87.0"
+matrix_bot_draupnir_version: "v2.0.1"
 
 matrix_bot_draupnir_container_image_self_build: false
 matrix_bot_draupnir_container_image_self_build_repo: "https://github.com/the-draupnir-project/Draupnir.git"
@@ -49,8 +49,20 @@ matrix_bot_draupnir_systemd_wanted_services_list: []
 # Whether Draupnir should talk to the homeserver through Pantalaimon
 # If true, then other variables must be provided including pointing
 # `matrix_bot_draupnir_homeserver_url` to the Pantalaimon URL.
+# Enabling this option is discouraged, because Draupnir does not support
+# running with Pantalaimon as it would break all workflows that involve answering
+# prompts with reactions. (Hint: a lot of workflows rely on them.)
 matrix_bot_draupnir_pantalaimon_use: false
 
+# If you choose to accept the risks of using Pantalaimon in your installation
+# against the upstream advice, you can enable this to disable the warning about it.
+matrix_bot_draupnir_pantalaimon_breakage_ignore: false
+
+# Tells the bot if it should use its native E2EE support in the form of experimental Rust Crypto in the bot SDK.
+# This option is mutually exclusive with `matrix_bot_draupnir_pantalaimon_use`.
+# Rust Crypto requires a clean access token that has not touched E2EE so curl is recommended as a method to obtain it.
+matrix_bot_draupnir_enable_experimental_rust_crypto: false
+
 # The access token for the bot user. Required when NOT using Pantalaimon.
 # (Otherwise provide `matrix_bot_draupnir_pantalaimon_username` and `matrix_bot_draupnir_pantalaimon_password` instead.)
 matrix_bot_draupnir_access_token: ""
@@ -60,6 +72,15 @@ matrix_bot_draupnir_access_token: ""
 matrix_bot_draupnir_pantalaimon_username: ""
 matrix_bot_draupnir_pantalaimon_password: ""
 
+# Username and password the bot uses for logging in directly. If using Pantalimon
+# these values become the values of `matrix_bot_draupnir_pantalaimon_username` and `matrix_bot_draupnir_pantalaimon_password`
+matrix_bot_draupnir_login: "{{ matrix_bot_draupnir_pantalaimon_username if matrix_bot_draupnir_pantalaimon_use == 'true' else 'bot.draupnir' }}"
+matrix_bot_draupnir_password: "{{ matrix_bot_draupnir_pantalaimon_password }}"
+
+# Controls if we activate the pantalaimon config block for now. This configuration block is proable to change name for our usecase
+# due to a Draupnir push to scrub Pantalaimon from the codebase.
+matrix_bot_draupnir_login_native: ""
+
 # The room ID where people can use the bot. The bot has no access controls, so
 # anyone in this room can use the bot - secure your room!
 # This should be a room alias or room ID - not a matrix.to URL.
@@ -84,6 +105,11 @@ matrix_bot_draupnir_raw_homeserver_url: ""
 # Its Exposed here because its common enough to be valid to expose.
 matrix_bot_draupnir_disable_server_acl: "false"
 
+# Controls if the room state backing store is activated.
+# Room state backing store makes restarts of the bot lightning fast as the bot does not suffer from amnesia.
+# This config option has diminished improvements for bots on extremely fast homeservers or very very small bots on fast homeservers.
+matrix_bot_draupnir_enable_room_state_backing_store: "true"
+
 # Default configuration template which covers the generic use case.
 # You can customize it by controlling the various variables inside it.
 #
@@ -106,7 +132,7 @@ matrix_bot_draupnir_configuration_extension: "{{ matrix_bot_draupnir_configurati
 # You most likely don't need to touch this variable. Instead, see `matrix_bot_draupnir_configuration_yaml`.
 matrix_bot_draupnir_configuration: "{{ matrix_bot_draupnir_configuration_yaml | from_yaml | combine(matrix_bot_draupnir_configuration_extension, recursive=True) }}"
 
-# Controls whether labels will be added that redirect the /_matrix/client/../rooms/../report paths to draupnir
+# Controls whether labels will be added that redirect the /_matrix/client/../rooms/../report paths to Draupnir
 # Following these recommendations (https://github.com/element-hq/synapse/blob/master/docs/reverse_proxy.md), by default, we don't.
 # Regardless of whether this is enabled, it may or may not take effect due to the value of other variables.
 # See `matrix_synapse_container_labels_traefik_enabled` or `matrix_synapse_container_labels_matrix_related_labels_enabled`
diff --git a/roles/custom/matrix-bot-draupnir/tasks/setup_install.yml b/roles/custom/matrix-bot-draupnir/tasks/setup_install.yml
index 48fc2039c..0ddf994e7 100644
--- a/roles/custom/matrix-bot-draupnir/tasks/setup_install.yml
+++ b/roles/custom/matrix-bot-draupnir/tasks/setup_install.yml
@@ -28,7 +28,7 @@
     - src: "{{ role_path }}/templates/labels.j2"
       dest: "{{ matrix_bot_draupnir_base_path }}/labels"
 
-- name: Ensure draupnir Docker image is pulled
+- name: Ensure Draupnir Docker image is pulled
   community.docker.docker_image:
     name: "{{ matrix_bot_draupnir_docker_image }}"
     source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}"
@@ -40,7 +40,7 @@
   delay: "{{ devture_playbook_help_container_retries_delay }}"
   until: result is not failed
 
-- name: Ensure draupnir repository is present on self-build
+- name: Ensure Draupnir repository is present on self-build
   ansible.builtin.git:
     repo: "{{ matrix_bot_draupnir_container_image_self_build_repo }}"
     dest: "{{ matrix_bot_draupnir_docker_src_files_path }}"
@@ -51,7 +51,7 @@
   register: matrix_bot_draupnir_git_pull_results
   when: "matrix_bot_draupnir_container_image_self_build | bool"
 
-- name: Ensure draupnir Docker image is built
+- name: Ensure Draupnir Docker image is built
   community.docker.docker_image:
     name: "{{ matrix_bot_draupnir_docker_image }}"
     source: build
diff --git a/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml b/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml
index efc5e7ddc..20acf748d 100644
--- a/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml
+++ b/roles/custom/matrix-bot-draupnir/tasks/validate_config.yml
@@ -5,6 +5,7 @@
     msg: "The `{{ item.name }}` variable must be defined and have a non-null value."
   with_items:
     - {'name': 'matrix_bot_draupnir_access_token', when: "{{ not matrix_bot_draupnir_pantalaimon_use }}"}
+    - {'name': 'matrix_bot_draupnir_access_token', when: "{{ matrix_bot_draupnir_enable_experimental_rust_crypto }}"}
     - {'name': 'matrix_bot_draupnir_management_room', when: true}
     - {'name': 'matrix_bot_draupnir_container_network', when: true}
     - {'name': 'matrix_bot_draupnir_homeserver_url', when: true}
@@ -18,4 +19,19 @@
     msg: "The `{{ item.name }}` variable must be undefined or have a null value."
   with_items:
     - {'name': 'matrix_bot_draupnir_access_token', when: "{{ matrix_bot_draupnir_pantalaimon_use }}"}
+    - {'name': 'matrix_bot_draupnir_access_token', when: "{{ matrix_bot_draupnir_login_native }}"}
+    - {'name': 'matrix_bot_draupnir_pantalaimon_use', when: "{{  matrix_bot_draupnir_enable_experimental_rust_crypto }}"}
   when: "item.when | bool and not (vars[item.name] == '' or vars[item.name] is none)"
+
+- when: "matrix_bot_draupnir_pantalaimon_use == 'true' and matrix_bot_draupnir_pantalaimon_breakage_ignore == 'false'"
+  block:
+    - name: Inject warning if Pantalaimon is used together with Draupnir
+      ansible.builtin.set_fact:
+        devture_playbook_runtime_messages_list: |
+          {{
+            devture_playbook_runtime_messages_list | default([])
+            +
+            [
+              "Note: Draupnir does not support running with Pantalaimon as it would break all workflows that involve answering prompts with reactions. To enable E2EE for Draupnir, it is recommended to use matrix_bot_draupnir_enable_experimental_rust_crypto instead. This warning can be disabled by setting matrix_bot_draupnir_pantalaimon_breakage_ignore to true."
+            ]
+          }}
diff --git a/roles/custom/matrix-bot-draupnir/templates/production.yaml.j2 b/roles/custom/matrix-bot-draupnir/templates/production.yaml.j2
index acb2c508b..56b82e322 100644
--- a/roles/custom/matrix-bot-draupnir/templates/production.yaml.j2
+++ b/roles/custom/matrix-bot-draupnir/templates/production.yaml.j2
@@ -1,5 +1,4 @@
 # Endpoint URL that Draupnir uses to interact with the Matrix homeserver (client-server API),
-# set this to the pantalaimon URL if you're using that.
 homeserverUrl: {{ matrix_bot_draupnir_homeserver_url | to_json }}
 
 # Endpoint URL that Draupnir could use to fetch events related to reports (client-server API and /_synapse/),
@@ -7,29 +6,36 @@ homeserverUrl: {{ matrix_bot_draupnir_homeserver_url | to_json }}
 rawHomeserverUrl: {{ matrix_bot_draupnir_raw_homeserver_url | to_json }}
 
 # Matrix Access Token to use, Draupnir will only use this if pantalaimon.use is false.
+# This option can be loaded from a file by passing "--access-token-path <path>" at the command line,
+# which would allow using secret management systems such as systemd's service credentials.
 accessToken: {{ matrix_bot_draupnir_access_token | to_json }}
 
-{% if matrix_bot_draupnir_pantalaimon_use %}
+{% if matrix_bot_draupnir_pantalaimon_use or matrix_bot_draupnir_login_native %}
 # Options related to Pantalaimon (https://github.com/matrix-org/pantalaimon)
 pantalaimon:
-  # Whether or not Draupnir will use pantalaimon to access the Matrix homeserver,
-  # set to `true` if you're using pantalaimon.
-  #
-  # Be sure to point homeserverUrl to the pantalaimon instance.
+  # Set to `true` when the bot is to login and fetch the access token on its own.
   #
   # Draupnir will log in using the given username and password once,
   # then store the resulting access token in a file under dataPath.
   use: true
 
   # The username to login with.
-  username: {{ matrix_bot_draupnir_pantalaimon_username | to_json }}
+  username: {{ matrix_bot_draupnir_login | to_json }}
 
   # The password Draupnir will login with.
   #
   # After successfully logging in once, this will be ignored, so this value can be blanked after first startup.
-  password: {{ matrix_bot_draupnir_pantalaimon_password | to_json }}
+  # This option can be loaded from a file by passing "--password-path <path>" at the command line,
+  # which would allow using secret management systems such as systemd's service credentials.
+  password: {{ matrix_bot_draupnir_password | to_json }}
 {% endif %}
 
+# Experimental usage of the matrix-bot-sdk rust crypto. This can not be used with Pantalaimon.
+# Make sure Pantalaimon is disabled in Draupnir's configuration.
+#
+# Warning: At this time this is not considered production safe.
+experimentalRustCrypto: {{ matrix_bot_draupnir_enable_experimental_rust_crypto | to_json }}
+
 # The path Draupnir will store its state/data in, leave default ("/data/storage") when using containers.
 dataPath: "/data"
 
@@ -56,8 +62,8 @@ managementRoom: {{ matrix_bot_draupnir_management_room | to_json }}
 # Deprecated and will be removed in a future version.
 # Running with verboseLogging is unsupported.
 # Whether Draupnir should log a lot more messages in the room,
-# mainly involves "all-OK" messages, and debugging messages for when draupnir checks bans in a room.
-#verboseLogging: false
+# mainly involves "all-OK" messages, and debugging messages for when Draupnir checks bans in a room.
+verboseLogging: false
 
 # The log level of terminal (or container) output,
 # can be one of DEBUG, INFO, WARN and ERROR, in increasing order of importance and severity.
@@ -81,12 +87,6 @@ noop: false
 # DO NOT change this to `true` unless you are very confident that you know what you are doing.
 disableServerACL: {{ matrix_bot_draupnir_disable_server_acl | to_json }}
 
-# Whether Draupnir should check member lists quicker (by using a different endpoint),
-# keep in mind that enabling this will miss invited (but not joined) users.
-#
-# Turn on if your bot is in (very) large rooms, or in large amounts of rooms.
-fasterMembershipChecks: false
-
 # A case-insensitive list of ban reasons to have the bot also automatically redact the user's messages for.
 #
 # If the bot sees you ban a user with a reason that is an (exact case-insensitive) match to this list,
@@ -102,15 +102,6 @@ automaticallyRedactForReasons:
   - "spam"
   - "advertising"
 
-# A list of rooms to protect. Draupnir will add this to the list it knows from its account data.
-#
-# It won't, however, add it to the account data.
-# Manually add the room via '!draupnir rooms add' to have it stay protected regardless if this config value changes.
-#
-# Note: These must be matrix.to URLs
-#protectedRooms:
-#  - "https://matrix.to/#/#matrix:example.org"
-
 # Whether or not to add all joined rooms to the "protected rooms" list
 # (excluding the management room and watched policy list rooms, see below).
 #
@@ -131,15 +122,18 @@ protectAllJoinedRooms: false
 # of the homeserver may be more impacted.
 backgroundDelayMS: 500
 
+# FIXME: This configuration option is currently broken in the playbook as admin APIs cannot
+# be accessed from containers. See https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3389
+# and https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3308
 # Server administration commands, these commands will only work if Draupnir is
 # a global server administrator, and the bot's server is a Synapse instance.
-admin:
-  # Whether or not Draupnir can temporarily take control of any eligible account from the local homeserver who's in the room
-  # (with enough permissions) to "make" a user an admin.
-  #
-  # This only works if a local user with enough admin permissions is present in the room.
-  enableMakeRoomAdminCommand: false
-
+#admin:
+#  # Whether or not Draupnir can temporarily take control of any eligible account from the local homeserver who's in the room
+#  # (with enough permissions) to "make" a user an admin.
+#  #
+#  # This only works if a local user with enough admin permissions is present in the room.
+#  enableMakeRoomAdminCommand: false
+#
 # Misc options for command handling and commands
 commands:
   # Whether or not the `!draupnir` prefix is necessary to submit commands.
@@ -157,10 +151,6 @@ commands:
     - "draupnir_bot"
     - "draupnir"
 
-  # Whether or not commands with a wildcard (*) will require an additional `--force` argument
-  # in the command to be able to be submitted.
-  confirmWildcardBan: true
-
   # The default reasons to be prompted with if the reason is missing from a ban command.
   ban:
     defaultReasons:
@@ -178,10 +168,9 @@ commands:
 #    #
 #    # WordList will ban users who use these words when first joining a room, so take caution when selecting them.
 #    #
-#    # For advanced usage, regex can also be used, see the following links for more information;
-#    #  - https://www.digitalocean.com/community/tutorials/an-introduction-to-regular-expressions
-#    #  - https://regexr.com/
-#    #  - https://regexone.com/
+#    # The word list protection does not support regular expressions at this time.
+#    # The configuration in the past stated support for Regex erroneously.
+#    #
 #    words:
 #      - "LoReM"
 #      - "IpSuM"
@@ -196,6 +185,31 @@ commands:
 #    # (users will always be banned if they say a bad word)
 #    minutesBeforeTrusting: 20
 
+# The room state backing store writes a copy of the room state for all protected
+# rooms to the data directory.
+# It is recommended to enable this option unless you deploy Draupnir close to the
+# homeserver and know that Draupnir is starting up quickly. If your homeserver can
+# respond quickly to Draupnir's requests for `/state` then you might not need this option.
+roomStateBackingStore:
+  enabled: {{ matrix_bot_draupnir_enable_room_state_backing_store | to_json }}
+
+# Safe mode provides recovery options for some failure modes when Draupnir
+# fails to start. For example, if the bot fails to resolve a room alias in
+# a watched list, or if the server has parted from a protected room and can't
+# find a way back in. Safe mode will provide different options to recover from
+# these. Such as unprotecting the room or unwatching the policy list.
+# By default Draupnir will boot into safe mode only when the failure mode
+# is recoverable.
+# It may be desirable to prevent the bot from starting into safe mode if you have
+# a pager system when Draupnir is down, as Draupnir could prevent your monitoring
+# system from identifying a failure to start.
+#safeMode:
+#  # The option for entering safe mode when Draupnir fails to start up.
+#  # - "RecoveryOnly" will only start the bot in safe mode when there are recovery options available. This is the default.
+#  # - "Never" will never start the bot in safe mode when Draupnir fails to start normally.
+#  # - "Always" will always start the bot in safe mode when Draupnir fails to start normally.
+#  bootOption: RecoveryOnly
+
 # Options for advanced monitoring of the health of the bot.
 health:
   # healthz options. These options are best for use in container environments
@@ -227,6 +241,18 @@ health:
     # Defaults to 418.
     unhealthyStatus: 418
 
+  # Sentry options. Sentry is a tool used to receive/collate/triage runtime
+  # errors and performance issues. Skip this section if you do not wish to use
+  # Sentry.
+  sentry:
+    # The key used to upload Sentry data to the server.
+    # dsn: "https://XXXXXXXXX@example.com/YYY
+
+    # Frequency of performance monitoring.
+    # A number in [0.0, 1.0], where 0.0 means "don't bother with tracing"
+    # and 1.0 means "trace performance at every opportunity".
+    # tracesSampleRate: 0.5
+
 {% if matrix_bot_draupnir_web_enabled %}
 # Options for exposing web APIs.
 web:
@@ -238,7 +264,12 @@ web:
 
   # The address to listen for requests on. Defaults to only the current
   # computer.
-  address: 0.0.0.0
+  address: "0.0.0.0"
+
+  # Alternative setting to open to the entire web. Be careful,
+  # as this will increase your security perimeter:
+  #
+  #  address: "0.0.0.0"
 
   # A web API designed to intercept Matrix API
   # POST /_matrix/client/r0/rooms/{roomId}/report/{eventId}
@@ -251,10 +282,13 @@ web:
     enabled: {{ matrix_bot_draupnir_abuse_reporting_enabled | to_json }}
 {% endif %}
 
+# FIXME: This configuration option is currently broken in the playbook as admin APIs cannot
+# be accessed from containers. See https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3389
+# and https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3308
 # Whether or not to actively poll synapse for abuse reports, to be used
 # instead of intercepting client calls to synapse's abuse endpoint, when that
 # isn't possible/practical.
-pollReports: false
+#pollReports: false
 
 # Whether or not new reports, received either by webapi or polling,
 # should be printed to our managementRoom.
diff --git a/roles/custom/matrix-bot-go-neb/defaults/main.yml b/roles/custom/matrix-bot-go-neb/defaults/main.yml
index 2473f86f2..fd4bd9bd8 100644
--- a/roles/custom/matrix-bot-go-neb/defaults/main.yml
+++ b/roles/custom/matrix-bot-go-neb/defaults/main.yml
@@ -163,7 +163,7 @@ matrix_bot_go_neb_storage_database: "{{
 # The access tokens that the bot uses to authenticate.
 # Generate one as described in
 # https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-playbook-dimension.md#access-token
-# via curl. With the element method, you might run into decryption problems (see https://github.com/matrix-org/go-neb#quick-start)
+# via curl. With the Element method, you might run into decryption problems (see https://github.com/matrix-org/go-neb#quick-start)
 matrix_bot_go_neb_clients: []
 #  - UserID: "@goneb:{{ matrix_domain }}"
 #    AccessToken: "MDASDASJDIASDJASDAFGFRGER"
@@ -200,7 +200,7 @@ matrix_bot_go_neb_realms: []
 matrix_bot_go_neb_sessions: []
 #  - SessionID: "your_github_session"
 #    RealmID: "github_realm"
-#    UserID: "@YOUR_USER_ID:{{ matrix_domain }}" # This needs to be the username of the person that's allowed to use the !github commands
+#    UserID: "@alice:{{ matrix_domain }}" # This needs to be the username of the person that's allowed to use the !github commands
 #    Config:
 #      # Populate these fields by generating a "Personal Access Token" on github.com
 #      AccessToken: "YOUR_GITHUB_ACCESS_TOKEN"
@@ -286,7 +286,7 @@ matrix_bot_go_neb_services: []
 #    UserID: "@another_goneb:{{ matrix_domain }}"
 #    Config:
 #      RealmID: "github_realm"
-#      ClientUserID: "@YOUR_USER_ID:{{ matrix_domain }}" # needs to be an authenticated user so Go-NEB can create webhooks. Check the UserID field in the github_realm in matrix_bot_go_neb_sessions.
+#      ClientUserID: "@alice:{{ matrix_domain }}" # needs to be an authenticated user so Go-NEB can create webhooks. Check the UserID field in the github_realm in matrix_bot_go_neb_sessions.
 #      Rooms:
 #        "!qporfwt:example.com":
 #          Repos:
diff --git a/roles/custom/matrix-bot-honoroit/defaults/main.yml b/roles/custom/matrix-bot-honoroit/defaults/main.yml
index 5a1279bdc..850842db6 100644
--- a/roles/custom/matrix-bot-honoroit/defaults/main.yml
+++ b/roles/custom/matrix-bot-honoroit/defaults/main.yml
@@ -1,17 +1,17 @@
 ---
-# honoroit is a helpdesk bot
+# Honoroit is a helpdesk bot
 # Project source code URL: https://github.com/etkecc/honoroit
 
 matrix_bot_honoroit_enabled: true
 
-# The hostname at which honoroit is served.
+# The hostname at which Honoroit is served.
 matrix_bot_honoroit_hostname: ''
 
-# The path at which honoroit is exposed.
+# The path at which Honoroit is exposed.
 # This value must either be `/` or not end with a slash (e.g. `/honoroit`).
 matrix_bot_honoroit_path_prefix: /
 
-# The path at which honoroit will expose metrics
+# The path at which Honoroit will expose metrics
 # This value must either be `/` or not end with a slash (e.g. `/metrics`).
 matrix_bot_honoroit_metrics_path: /metrics
 
@@ -161,12 +161,12 @@ matrix_bot_honoroit_redmine_new_status_id: ''  # new status ID (e.g. 1)
 matrix_bot_honoroit_redmine_in_progress_status_id: ''  # in progress status ID (e.g. 2)
 matrix_bot_honoroit_redmine_done_status_id: ''  # done status ID (e.g. 3)
 
-# A list of whitelisted users allowed to use/invite honoroit
+# A list of whitelisted users allowed to use/invite a Honoroit bot
 # If not defined, everyone is allowed.
 # Example set of rules:
 # matrix_bot_honoroit_allowedusers:
-# - @someone:example.com
-# - @another:example.com
+# - @alice:example.com
+# - @bob:example.com
 # - @bot.*:example.com
 # - @*:example.net
 matrix_bot_honoroit_allowedusers:
diff --git a/roles/custom/matrix-bot-honoroit/tasks/setup_install.yml b/roles/custom/matrix-bot-honoroit/tasks/setup_install.yml
index 8dd647d1b..be96d021b 100644
--- a/roles/custom/matrix-bot-honoroit/tasks/setup_install.yml
+++ b/roles/custom/matrix-bot-honoroit/tasks/setup_install.yml
@@ -26,7 +26,7 @@
         - ansible.builtin.set_fact:
             matrix_bot_honoroit_requires_restart: true
 
-- name: Ensure honoroit paths exist
+- name: Ensure Honoroit paths exist
   ansible.builtin.file:
     path: "{{ item.path }}"
     state: directory
@@ -40,7 +40,7 @@
     - {path: "{{ matrix_bot_honoroit_docker_src_files_path }}", when: true}
   when: "item.when | bool"
 
-- name: Ensure honoroit support files installed
+- name: Ensure Honoroit support files installed
   ansible.builtin.template:
     src: "{{ role_path }}/templates/{{ item }}.j2"
     dest: "{{ matrix_bot_honoroit_config_path }}/{{ item }}"
@@ -51,7 +51,7 @@
     - env
     - labels
 
-- name: Ensure honoroit image is pulled
+- name: Ensure Honoroit image is pulled
   community.docker.docker_image:
     name: "{{ matrix_bot_honoroit_docker_image }}"
     source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}"
@@ -63,7 +63,7 @@
   delay: "{{ devture_playbook_help_container_retries_delay }}"
   until: result is not failed
 
-- name: Ensure honoroit repository is present on self-build
+- name: Ensure Honoroit repository is present on self-build
   ansible.builtin.git:
     repo: "{{ matrix_bot_honoroit_docker_repo }}"
     version: "{{ matrix_bot_honoroit_docker_repo_version }}"
@@ -74,7 +74,7 @@
   register: matrix_bot_honoroit_git_pull_results
   when: "matrix_bot_honoroit_container_image_self_build | bool"
 
-- name: Ensure honoroit image is built
+- name: Ensure Honoroit image is built
   community.docker.docker_image:
     name: "{{ matrix_bot_honoroit_docker_image }}"
     source: build
@@ -86,7 +86,7 @@
       pull: true
   when: "matrix_bot_honoroit_container_image_self_build | bool"
 
-- name: Ensure honoroit container network is created
+- name: Ensure Honoroit container network is created
   community.general.docker_network:
     enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}"
     name: "{{ matrix_bot_honoroit_container_network }}"
diff --git a/roles/custom/matrix-bot-honoroit/tasks/setup_uninstall.yml b/roles/custom/matrix-bot-honoroit/tasks/setup_uninstall.yml
index 757345861..72df4f013 100644
--- a/roles/custom/matrix-bot-honoroit/tasks/setup_uninstall.yml
+++ b/roles/custom/matrix-bot-honoroit/tasks/setup_uninstall.yml
@@ -19,7 +19,7 @@
         path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-bot-honoroit.service"
         state: absent
 
-    - name: Ensure Matrix honoroit paths don't exist
+    - name: Ensure Matrix Honoroit paths don't exist
       ansible.builtin.file:
         path: "{{ matrix_bot_honoroit_base_path }}"
         state: absent
diff --git a/roles/custom/matrix-bot-honoroit/tasks/validate_config.yml b/roles/custom/matrix-bot-honoroit/tasks/validate_config.yml
index d15411ab2..afd580c2a 100644
--- a/roles/custom/matrix-bot-honoroit/tasks/validate_config.yml
+++ b/roles/custom/matrix-bot-honoroit/tasks/validate_config.yml
@@ -1,6 +1,6 @@
 ---
 
-- name: Fail if required honoroit settings not defined
+- name: Fail if required Honoroit settings not defined
   ansible.builtin.fail:
     msg: >-
       You need to define a required configuration setting (`{{ item.name }}`).
diff --git a/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml b/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml
index 21f2061c5..ba1fc7273 100644
--- a/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml
+++ b/roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml
@@ -20,12 +20,19 @@ matrix_bot_matrix_registration_bot_config_path: "{{ matrix_bot_matrix_registrati
 matrix_bot_matrix_registration_bot_data_path: "{{ matrix_bot_matrix_registration_bot_base_path }}/data"
 
 matrix_bot_matrix_registration_bot_bot_server: "{{ matrix_homeserver_url }}"
-matrix_bot_matrix_registration_bot_api_base_url: "{{ matrix_homeserver_url }}"
 
+# The bot's username. This user needs to be created manually beforehand.
+# Also see `matrix_bot_matrix_registration_bot_user_password`.
+matrix_bot_matrix_registration_bot_matrix_user_id_localpart: "bot.matrix-registration-bot"
 
-# The bot's password (can also be used to login via a client like element)
+matrix_bot_matrix_registration_bot_matrix_user_id: '@{{ matrix_bot_matrix_registration_bot_matrix_user_id_localpart }}:{{ matrix_domain }}'
+
+# The bot's password (can also be used to login via a client like Element Web)
 matrix_bot_matrix_registration_bot_bot_password: ''
 
+# Homeserver base URL
+matrix_bot_matrix_registration_bot_api_base_url: "{{ matrix_homeserver_url }}"
+
 # Optional variable that only needs to be set if the bot account is not admin
 # Needs to be a valid access token of an admin account
 matrix_bot_matrix_registration_bot_api_token: ''
@@ -51,11 +58,3 @@ matrix_bot_matrix_registration_bot_systemd_required_services_list_custom: []
 
 # List of systemd services that matrix-bot-matrix-registration-bot.service wants
 matrix_bot_matrix_registration_bot_systemd_wanted_services_list: []
-
-# The bot's username. This user needs to be created manually beforehand.
-# Also see `matrix_bot_matrix_registration_bot_user_password`.
-matrix_bot_matrix_registration_bot_matrix_user_id_localpart: "bot.matrix-registration-bot"
-
-matrix_bot_matrix_registration_bot_matrix_user_id: '@{{ matrix_bot_matrix_registration_bot_matrix_user_id_localpart }}:{{ matrix_domain }}'
-
-matrix_bot_matrix_registration_bot_matrix_homeserver_url: ""
diff --git a/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml b/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml
index d50c0f860..0ac4e6a1f 100644
--- a/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml
+++ b/roles/custom/matrix-bot-matrix-registration-bot/tasks/setup_install.yml
@@ -10,12 +10,12 @@
   with_items:
     - {path: "{{ matrix_bot_matrix_registration_bot_config_path }}", when: true}
     - {path: "{{ matrix_bot_matrix_registration_bot_data_path }}", when: true}
-    - {path: "{{ matrix_bot_matrix_registration_bot_docker_src_files_path }}", when: true}
+    - {path: "{{ matrix_bot_matrix_registration_bot_docker_src_files_path }}", when: "{{ matrix_bot_matrix_registration_bot_container_image_self_build }}"}
   when: "item.when | bool"
 
 - name: Ensure matrix-registration-bot configuration file created
   ansible.builtin.template:
-    src: "{{ role_path }}/templates/config/config.yml.j2"
+    src: "{{ role_path }}/templates/config.yml.j2"
     dest: "{{ matrix_bot_matrix_registration_bot_config_path }}/config.yml"
     owner: "{{ matrix_user_username }}"
     group: "{{ matrix_user_groupname }}"
@@ -33,28 +33,28 @@
   delay: "{{ devture_playbook_help_container_retries_delay }}"
   until: result is not failed
 
-- name: Ensure matrix-registration-bot repository is present on self-build
-  ansible.builtin.git:
-    repo: "{{ matrix_bot_matrix_registration_bot_docker_repo }}"
-    version: "{{ matrix_bot_matrix_registration_bot_docker_repo_version }}"
-    dest: "{{ matrix_bot_matrix_registration_bot_docker_src_files_path }}"
-    force: "yes"
-  become: true
-  become_user: "{{ matrix_user_username }}"
-  register: matrix_bot_matrix_registration_bot_git_pull_results
-  when: "matrix_bot_matrix_registration_bot_container_image_self_build | bool"
+- when: matrix_bot_matrix_registration_bot_container_image_self_build | bool
+  block:
+    - name: Ensure matrix-registration-bot repository is present on self-build
+      ansible.builtin.git:
+        repo: "{{ matrix_bot_matrix_registration_bot_docker_repo }}"
+        version: "{{ matrix_bot_matrix_registration_bot_docker_repo_version }}"
+        dest: "{{ matrix_bot_matrix_registration_bot_docker_src_files_path }}"
+        force: "yes"
+      become: true
+      become_user: "{{ matrix_user_username }}"
+      register: matrix_bot_matrix_registration_bot_git_pull_results
 
-- name: Ensure matrix-registration-bot image is built
-  community.docker.docker_image:
-    name: "{{ matrix_bot_matrix_registration_bot_docker_image }}"
-    source: build
-    force_source: "{{ matrix_bot_matrix_registration_bot_git_pull_results.changed if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}"
-    force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_bot_matrix_registration_bot_git_pull_results.changed }}"
-    build:
-      dockerfile: Dockerfile
-      path: "{{ matrix_bot_matrix_registration_bot_docker_src_files_path }}"
-      pull: true
-  when: "matrix_bot_matrix_registration_bot_container_image_self_build | bool"
+    - name: Ensure matrix-registration-bot image is built
+      community.docker.docker_image:
+        name: "{{ matrix_bot_matrix_registration_bot_docker_image }}"
+        source: build
+        force_source: "{{ matrix_bot_matrix_registration_bot_git_pull_results.changed if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}"
+        force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_bot_matrix_registration_bot_git_pull_results.changed }}"
+        build:
+          dockerfile: Dockerfile
+          path: "{{ matrix_bot_matrix_registration_bot_docker_src_files_path }}"
+          pull: true
 
 - name: Ensure matrix-registration-bot container network is created
   community.general.docker_network:
diff --git a/roles/custom/matrix-bot-matrix-registration-bot/tasks/validate_config.yml b/roles/custom/matrix-bot-matrix-registration-bot/tasks/validate_config.yml
index 9830c5323..fb5e7de5c 100644
--- a/roles/custom/matrix-bot-matrix-registration-bot/tasks/validate_config.yml
+++ b/roles/custom/matrix-bot-matrix-registration-bot/tasks/validate_config.yml
@@ -7,12 +7,14 @@
   when: "vars[item] == ''"
   with_items:
     - "matrix_bot_matrix_registration_bot_bot_password"
-    - "matrix_bot_matrix_registration_bot_matrix_homeserver_url"
+    - "matrix_bot_matrix_registration_bot_api_base_url"
 
-- name: (Deprecation) Catch and report old settings
+- name: (Deprecation) Catch and report renamed settings
   ansible.builtin.fail:
     msg: >-
-      Your configuration contains a variable, which is deprecated - Please check the documentation on how to configure the matrix-registration-bot.
-  when: "item in vars"
+      Your configuration contains a variable, which now has a different name.
+      Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`).
+  when: "item.old in vars"
   with_items:
-    - "matrix_bot_matrix_registration_bot_bot_access_token"
+    - {'old': 'matrix_bot_matrix_registration_bot_bot_access_token', 'new': '<removed>'}
+    - {'old': 'matrix_bot_matrix_registration_bot_matrix_homeserver_url', 'new': 'matrix_bot_matrix_registration_bot_api_base_url'}
diff --git a/roles/custom/matrix-bot-matrix-registration-bot/templates/config/config.yml.j2 b/roles/custom/matrix-bot-matrix-registration-bot/templates/config.yml.j2
similarity index 100%
rename from roles/custom/matrix-bot-matrix-registration-bot/templates/config/config.yml.j2
rename to roles/custom/matrix-bot-matrix-registration-bot/templates/config.yml.j2
index 4a2242aa2..7ea2b9d0a 100644
--- a/roles/custom/matrix-bot-matrix-registration-bot/templates/config/config.yml.j2
+++ b/roles/custom/matrix-bot-matrix-registration-bot/templates/config.yml.j2
@@ -6,8 +6,8 @@ bot:
 api:
   # API endpoint of the registration tokens
   base_url: {{ matrix_bot_matrix_registration_bot_api_base_url|to_json }}
-  # Access token of an administrator on the server
 {% if matrix_bot_matrix_registration_bot_api_token | length > 0 %}
+  # Access token of an administrator on the server
   token: {{ matrix_bot_matrix_registration_bot_api_token|to_json }}
 {% endif %}
 
diff --git a/roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml b/roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml
index 66ec34fbd..e6074f70a 100644
--- a/roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml
+++ b/roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml
@@ -6,7 +6,7 @@ matrix_bot_matrix_reminder_bot_enabled: true
 
 matrix_bot_matrix_reminder_bot_container_image_self_build: false
 matrix_bot_matrix_reminder_bot_docker_repo: "https://github.com/anoadragon453/matrix-reminder-bot.git"
-matrix_bot_matrix_reminder_bot_docker_repo_version: "{{ matrix_bot_matrix_reminder_bot_version }}"
+matrix_bot_matrix_reminder_bot_docker_repo_version: "{{ 'master' if matrix_bot_matrix_reminder_bot_version == 'latest' else matrix_bot_matrix_reminder_bot_version }}"
 matrix_bot_matrix_reminder_bot_docker_src_files_path: "{{ matrix_base_data_path }}/matrix-reminder-bot/docker-src"
 
 # renovate: datasource=docker depName=ghcr.io/anoadragon453/matrix-reminder-bot
diff --git a/roles/custom/matrix-bot-maubot/defaults/main.yml b/roles/custom/matrix-bot-maubot/defaults/main.yml
index cf91011b4..48c5d7464 100644
--- a/roles/custom/matrix-bot-maubot/defaults/main.yml
+++ b/roles/custom/matrix-bot-maubot/defaults/main.yml
@@ -17,18 +17,34 @@ matrix_bot_maubot_path_prefix: /_matrix/maubot
 
 matrix_bot_maubot_container_image_self_build: false
 matrix_bot_maubot_docker_repo: "https://mau.dev/maubot/maubot.git"
-matrix_bot_maubot_docker_src_files_path: "{{ matrix_bot_maubot_base_path }}/docker-src"
 matrix_bot_maubot_docker_repo_version: "{{ 'master' if matrix_bot_maubot_version == 'latest' else matrix_bot_maubot_version }}"
 
 # renovate: datasource=docker depName=dock.mau.dev/maubot/maubot
-matrix_bot_maubot_version: v0.5.0
+matrix_bot_maubot_version: v0.5.1
 matrix_bot_maubot_docker_image: "{{ matrix_bot_maubot_docker_image_name_prefix }}maubot/maubot:{{ matrix_bot_maubot_version }}"
 matrix_bot_maubot_docker_image_name_prefix: "{{ 'localhost/' if matrix_bot_maubot_container_image_self_build else 'dock.mau.dev/' }}"
 matrix_bot_maubot_docker_image_force_pull: "{{ matrix_bot_maubot_docker_image.endswith(':latest') }}"
 
+# matrix_bot_maubot_docker_image_customized is the name of the locally built maubot image
+# which adds various customizations on top of the original (upstream) maubot image.
+# This image will be based on the upstream `matrix_bot_maubot_docker_image` image, only if `matrix_bot_maubot_container_image_customizations_enabled: true`.
+matrix_bot_maubot_docker_image_customized: "localhost/maubot/maubot:{{ matrix_bot_maubot_version }}-customized"
+
+# Controls whether the customized image (`matrix_bot_maubot_docker_image_customized`) is to be force-built without layer caching enabled.
+matrix_bot_maubot_docker_image_customized_build_nocache: false
+
+# Controls whether the customized image (`matrix_bot_maubot_docker_image_customized`) is to be built, even if it already exists.
+# Related to: matrix_bot_maubot_docker_image_customized_build_nocache
+matrix_bot_maubot_docker_image_customized_force_source: "{{ matrix_bot_maubot_docker_image_customized_build_nocache }}"
+
+# matrix_bot_maubot_docker_image_final holds the name of the maubot image to run depending on whether or not customizations are enabled.
+matrix_bot_maubot_docker_image_final: "{{ matrix_bot_maubot_docker_image_customized if matrix_bot_maubot_container_image_customizations_enabled else matrix_bot_maubot_docker_image }} "
+
 matrix_bot_maubot_base_path: "{{ matrix_base_data_path }}/maubot"
 matrix_bot_maubot_data_path: "{{ matrix_bot_maubot_base_path }}/data"
 matrix_bot_maubot_config_path: "{{ matrix_bot_maubot_base_path }}/config"
+matrix_bot_maubot_docker_src_files_path: "{{ matrix_bot_maubot_base_path }}/docker-src"
+matrix_bot_maubot_customized_docker_src_files_path: "{{ matrix_bot_maubot_base_path }}/customized-docker-src"
 
 matrix_bot_maubot_bot_server_public_url: "{{ matrix_bot_maubot_scheme }}://{{ matrix_bot_maubot_hostname }}"
 matrix_bot_maubot_bot_server_base_path: "{{ matrix_bot_maubot_path_prefix }}/v1"
@@ -87,6 +103,30 @@ matrix_bot_maubot_container_additional_networks: "{{ matrix_bot_maubot_container
 matrix_bot_maubot_container_additional_networks_auto: []
 matrix_bot_maubot_container_additional_networks_custom: []
 
+
+# matrix_bot_maubot_container_image_customizations_enabled controls whether a customized maubot image will be built.
+#
+# We toggle this variable to `true` when certain features which require a custom build are enabled.
+# Feel free to toggle this to `true` yourself and specify build steps in `matrix_bot_maubot_container_image_customizations_dockerfile_body_custom`.
+#
+# See:
+# - `roles/custom/matrix-bot-maubot/templates/maubot/customizations/Dockerfile.j2`
+# - `matrix_bot_maubot_container_image_customizations_dockerfile_body_custom`
+# - `matrix_bot_maubot_docker_image_customized`
+# - `matrix_bot_maubot_docker_image_final`
+matrix_bot_maubot_container_image_customizations_enabled: false
+
+# matrix_bot_maubot_container_image_customizations_dockerfile_body contains your custom Dockerfile steps
+# for building your customized maubot image based on the original (upstream) image (`matrix_bot_maubot_docker_image`).
+# A `FROM …` clause is included automatically so you don't have to.
+#
+# Example:
+# matrix_bot_maubot_container_image_customizations_dockerfile_body_custom: |
+#  RUN echo 'This is a custom step for building the customized container image for maubot.'
+#  RUN echo 'You can override matrix_bot_maubot_container_image_customizations_dockerfile_body_custom to add your own steps.'
+#  RUN echo 'You do NOT need to include a FROM clause yourself.'
+matrix_bot_maubot_container_image_customizations_dockerfile_body_custom: ''
+
 # matrix_bot_maubot_container_labels_traefik_enabled controls whether labels to assist a Traefik reverse-proxy will be attached to the container.
 # See `../templates/labels.j2` for details.
 #
diff --git a/roles/custom/matrix-bot-maubot/tasks/setup_install.yml b/roles/custom/matrix-bot-maubot/tasks/setup_install.yml
index 318879f9b..1c6f17404 100644
--- a/roles/custom/matrix-bot-maubot/tasks/setup_install.yml
+++ b/roles/custom/matrix-bot-maubot/tasks/setup_install.yml
@@ -15,11 +15,12 @@
     - {path: "{{ matrix_bot_maubot_data_path }}/dbs", when: true}
     - {path: "{{ matrix_bot_maubot_data_path }}/trash", when: true}
     - {path: "{{ matrix_bot_maubot_docker_src_files_path }}", when: "{{ matrix_bot_maubot_container_image_self_build }}"}
+    - {path: "{{ matrix_bot_maubot_customized_docker_src_files_path }}", when: "{{ matrix_bot_maubot_container_image_customizations_enabled }}"}
   when: "item.when|bool"
 
 - name: Ensure maubot configuration file created
   ansible.builtin.template:
-    src: "{{ role_path }}/templates/config/config.yaml.j2"
+    src: "{{ role_path }}/templates/config.yaml.j2"
     dest: "{{ matrix_bot_maubot_config_path }}/config.yaml"
     owner: "{{ matrix_user_username }}"
     group: "{{ matrix_user_groupname }}"
@@ -37,28 +38,49 @@
   delay: "{{ devture_playbook_help_container_retries_delay }}"
   until: result is not failed
 
-- name: Ensure maubot repository is present on self-build
-  ansible.builtin.git:
-    repo: "{{ matrix_bot_maubot_docker_repo }}"
-    version: "{{ matrix_bot_maubot_docker_repo_version }}"
-    dest: "{{ matrix_bot_maubot_docker_src_files_path }}"
-    force: "yes"
-  become: true
-  become_user: "{{ matrix_user_username }}"
-  register: matrix_bot_maubot_git_pull_results
-  when: "matrix_bot_maubot_container_image_self_build|bool"
+- when: matrix_bot_maubot_container_image_self_build | bool
+  block:
+    - name: Ensure maubot repository is present on self-build
+      ansible.builtin.git:
+        repo: "{{ matrix_bot_maubot_docker_repo }}"
+        version: "{{ matrix_bot_maubot_docker_repo_version }}"
+        dest: "{{ matrix_bot_maubot_docker_src_files_path }}"
+        force: "yes"
+      become: true
+      become_user: "{{ matrix_user_username }}"
+      register: matrix_bot_maubot_git_pull_results
 
-- name: Ensure maubot image is built
-  community.docker.docker_image:
-    name: "{{ matrix_bot_maubot_docker_image }}"
-    source: build
-    force_source: "{{ matrix_bot_maubot_git_pull_results.changed if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}"
-    force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_bot_maubot_git_pull_results.changed }}"
-    build:
-      dockerfile: Dockerfile
-      path: "{{ matrix_bot_maubot_docker_src_files_path }}"
-      pull: true
-  when: "matrix_bot_maubot_container_image_self_build|bool"
+    - name: Ensure maubot image is built
+      community.docker.docker_image:
+        name: "{{ matrix_bot_maubot_docker_image }}"
+        source: build
+        force_source: "{{ matrix_bot_maubot_git_pull_results.changed if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}"
+        force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_bot_maubot_git_pull_results.changed }}"
+        build:
+          dockerfile: Dockerfile
+          path: "{{ matrix_bot_maubot_docker_src_files_path }}"
+          pull: true
+
+- when: "matrix_bot_maubot_container_image_customizations_enabled | bool"
+  block:
+    - name: Ensure customizations Dockerfile is created
+      ansible.builtin.template:
+        src: "{{ role_path }}/templates/customizations/Dockerfile.j2"
+        dest: "{{ matrix_bot_maubot_customized_docker_src_files_path }}/Dockerfile"
+        owner: "{{ matrix_user_username }}"
+        group: "{{ matrix_user_groupname }}"
+        mode: 0640
+      register: matrix_bot_maubot_container_image_customizations_dockerfile_result
+
+    - name: Ensure customized Docker image for maubot is built
+      community.docker.docker_image:
+        name: "{{ matrix_bot_maubot_docker_image_customized }}"
+        source: build
+        force_source: "{{ matrix_bot_maubot_container_image_customizations_dockerfile_result.changed or matrix_bot_maubot_docker_image_customized_force_source }}"
+        build:
+          dockerfile: Dockerfile
+          path: "{{ matrix_bot_maubot_customized_docker_src_files_path }}"
+          nocache: "{{ matrix_bot_maubot_docker_image_customized_build_nocache }}"
 
 - name: Ensure maubot support files installed
   ansible.builtin.template:
diff --git a/roles/custom/matrix-bot-maubot/templates/config/config.yaml.j2 b/roles/custom/matrix-bot-maubot/templates/config.yaml.j2
similarity index 100%
rename from roles/custom/matrix-bot-maubot/templates/config/config.yaml.j2
rename to roles/custom/matrix-bot-maubot/templates/config.yaml.j2
diff --git a/roles/custom/matrix-bot-maubot/templates/customizations/Dockerfile.j2 b/roles/custom/matrix-bot-maubot/templates/customizations/Dockerfile.j2
new file mode 100644
index 000000000..0f2f4e508
--- /dev/null
+++ b/roles/custom/matrix-bot-maubot/templates/customizations/Dockerfile.j2
@@ -0,0 +1,4 @@
+#jinja2: lstrip_blocks: "True"
+FROM {{ matrix_bot_maubot_docker_image }}
+
+{{ matrix_bot_maubot_container_image_customizations_dockerfile_body_custom }}
diff --git a/roles/custom/matrix-bot-maubot/templates/systemd/matrix-bot-maubot.service.j2 b/roles/custom/matrix-bot-maubot/templates/systemd/matrix-bot-maubot.service.j2
index 4b9f782f7..25ba29a46 100644
--- a/roles/custom/matrix-bot-maubot/templates/systemd/matrix-bot-maubot.service.j2
+++ b/roles/custom/matrix-bot-maubot/templates/systemd/matrix-bot-maubot.service.j2
@@ -16,6 +16,10 @@ Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}"
 ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-maubot 2>/dev/null || true'
 ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-maubot 2>/dev/null || true'
 
+{#
+	We mount a tmpfs at /tmp, because some maubot plugins may wish to write to it.
+	It makes sense to provide at least some sort of temporary storage.
+#}
 ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \
 			--rm \
 			--name=matrix-bot-maubot \
@@ -25,6 +29,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \
 			--cap-drop=ALL \
 			--mount type=bind,src={{ matrix_bot_maubot_config_path }},dst=/config,ro \
 			--mount type=bind,src={{ matrix_bot_maubot_data_path }},dst=/data \
+			--tmpfs=/tmp:rw,noexec,nosuid,size=1024m \
 			--label-file={{ matrix_bot_maubot_base_path }}/labels \
 			{% for arg in matrix_bot_maubot_container_extra_arguments %}
 			{{ arg }} \
@@ -33,7 +38,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \
 			{% if matrix_bot_maubot_container_management_interface_http_bind_port %}
 			-p {{ matrix_bot_maubot_container_management_interface_http_bind_port }}:{{ matrix_bot_maubot_server_port }} \
 			{% endif %}
-			{{ matrix_bot_maubot_docker_image }} \
+			{{ matrix_bot_maubot_docker_image_final }} \
  			python3 -m maubot -c /config/config.yaml --no-update
 
 {% for network in matrix_bot_maubot_container_additional_networks %}
diff --git a/roles/custom/matrix-bot-mjolnir/defaults/main.yml b/roles/custom/matrix-bot-mjolnir/defaults/main.yml
index e1dce2ef1..9f7fea28c 100644
--- a/roles/custom/matrix-bot-mjolnir/defaults/main.yml
+++ b/roles/custom/matrix-bot-mjolnir/defaults/main.yml
@@ -5,7 +5,7 @@
 matrix_bot_mjolnir_enabled: true
 
 # renovate: datasource=docker depName=matrixdotorg/mjolnir
-matrix_bot_mjolnir_version: "v1.8.3"
+matrix_bot_mjolnir_version: "v1.9.1"
 
 matrix_bot_mjolnir_container_image_self_build: false
 matrix_bot_mjolnir_container_image_self_build_repo: "https://github.com/matrix-org/mjolnir.git"
diff --git a/roles/custom/matrix-bot-postmoogle/defaults/main.yml b/roles/custom/matrix-bot-postmoogle/defaults/main.yml
deleted file mode 100644
index c2163680f..000000000
--- a/roles/custom/matrix-bot-postmoogle/defaults/main.yml
+++ /dev/null
@@ -1,179 +0,0 @@
----
-# postmoogle is an email to Matrix bot
-# Project source code URL: https://github.com/etkecc/postmoogle
-
-matrix_bot_postmoogle_enabled: true
-
-matrix_bot_postmoogle_container_image_self_build: false
-matrix_bot_postmoogle_docker_repo: "https://github.com/etkecc/postmoogle.git"
-matrix_bot_postmoogle_docker_repo_version: "{{ 'main' if matrix_bot_postmoogle_version == 'latest' else matrix_bot_postmoogle_version }}"
-matrix_bot_postmoogle_docker_src_files_path: "{{ matrix_base_data_path }}/postmoogle/docker-src"
-
-# renovate: datasource=docker depName=ghcr.io/etkecc/postmoogle
-matrix_bot_postmoogle_version: v0.9.21
-matrix_bot_postmoogle_docker_image: "{{ matrix_bot_postmoogle_docker_image_name_prefix }}etkecc/postmoogle:{{ matrix_bot_postmoogle_version }}"
-matrix_bot_postmoogle_docker_image_name_prefix: "{{ 'localhost/' if matrix_bot_postmoogle_container_image_self_build else 'ghcr.io/' }}"
-matrix_bot_postmoogle_docker_image_force_pull: "{{ matrix_bot_postmoogle_docker_image.endswith(':latest') }}"
-
-matrix_bot_postmoogle_base_path: "{{ matrix_base_data_path }}/postmoogle"
-matrix_bot_postmoogle_config_path: "{{ matrix_bot_postmoogle_base_path }}/config"
-matrix_bot_postmoogle_data_path: "{{ matrix_bot_postmoogle_base_path }}/data"
-
-matrix_bot_postmoogle_container_network: ""
-
-matrix_bot_postmoogle_container_additional_networks: "{{ matrix_bot_postmoogle_container_additional_networks_auto + matrix_bot_postmoogle_container_additional_networks_custom }}"
-matrix_bot_postmoogle_container_additional_networks_auto: []
-matrix_bot_postmoogle_container_additional_networks_custom: []
-
-# A list of extra arguments to pass to the container
-matrix_bot_postmoogle_container_extra_arguments: []
-
-# List of systemd services that matrix-bot-postmoogle.service depends on
-matrix_bot_postmoogle_systemd_required_services_list: "{{ matrix_bot_postmoogle_systemd_required_services_list_default + matrix_bot_postmoogle_systemd_required_services_list_auto + matrix_bot_postmoogle_systemd_required_services_list_custom }}"
-matrix_bot_postmoogle_systemd_required_services_list_default: "{{ [devture_systemd_docker_base_docker_service_name] if devture_systemd_docker_base_docker_service_name else [] }}"
-matrix_bot_postmoogle_systemd_required_services_list_auto: []
-matrix_bot_postmoogle_systemd_required_services_list_custom: []
-
-# List of systemd services that matrix-bot-postmoogle.service wants
-matrix_bot_postmoogle_systemd_wanted_services_list: []
-
-# Database-related configuration fields.
-#
-# To use SQLite, stick to these defaults.
-#
-# To use Postgres:
-# - change the engine (`matrix_bot_postmoogle_database_engine: 'postgres'`)
-# - adjust your database credentials via the `matrix_bot_postmoogle_database_*` variables
-matrix_bot_postmoogle_database_engine: 'sqlite'
-
-matrix_bot_postmoogle_sqlite_database_path_local: "{{ matrix_bot_postmoogle_data_path }}/bot.db"
-matrix_bot_postmoogle_sqlite_database_path_in_container: "/data/bot.db"
-
-matrix_bot_postmoogle_database_username: 'postmoogle'
-matrix_bot_postmoogle_database_password: 'some-password'
-matrix_bot_postmoogle_database_hostname: ''
-matrix_bot_postmoogle_database_port: 5432
-matrix_bot_postmoogle_database_name: 'postmoogle'
-matrix_bot_postmoogle_database_sslmode: disable
-
-matrix_bot_postmoogle_database_connection_string: 'postgres://{{ matrix_bot_postmoogle_database_username }}:{{ matrix_bot_postmoogle_database_password }}@{{ matrix_bot_postmoogle_database_hostname }}:{{ matrix_bot_postmoogle_database_port }}/{{ matrix_bot_postmoogle_database_name }}?sslmode={{ matrix_bot_postmoogle_database_sslmode }}'
-
-matrix_bot_postmoogle_storage_database: "{{
-	{
-		'sqlite': matrix_bot_postmoogle_sqlite_database_path_in_container,
-		'postgres': matrix_bot_postmoogle_database_connection_string,
-	}[matrix_bot_postmoogle_database_engine]
-}}"
-
-matrix_bot_postmoogle_database_dialect: "{{
-  {
-    'sqlite': 'sqlite3',
-    'postgres': 'postgres',
-  }[matrix_bot_postmoogle_database_engine]
-}}"
-
-
-# The bot's username. This user needs to be created manually beforehand.
-# Also see `matrix_bot_postmoogle_password` or `matrix_bot_postmoogle_sharedsecret`
-matrix_bot_postmoogle_login: "postmoogle"
-
-# The password that the bot uses to authenticate.
-matrix_bot_postmoogle_password: ''
-
-# Alternative to password - shared secret requires matrix_bot_postmoogle_login to be MXID
-matrix_bot_postmoogle_sharedsecret: ''
-
-matrix_bot_postmoogle_homeserver: ""
-
-# Command prefix
-matrix_bot_postmoogle_prefix: '!pm'
-
-# Max email size in megabytes, including attachments
-matrix_bot_postmoogle_maxsize: '1024'
-
-# Optional SMTP relay mode
-matrix_bot_postmoogle_relay_host: ''
-matrix_bot_postmoogle_relay_port: ''
-matrix_bot_postmoogle_relay_username: ''
-matrix_bot_postmoogle_relay_password: ''
-
-# A list of admins
-# Example set of rules:
-# matrix_bot_postmoogle_admins:
-# - '@someone:example.com'
-# - '@another:example.com'
-# - '@bot.*:example.com'
-# - '@*:example.net'
-matrix_bot_postmoogle_admins: "{{ [matrix_admin] if matrix_admin else [] }}"
-
-# Sentry DSN. Deprecated, use matrix_bot_postmoogle_monitoring_sentry_dsn
-matrix_bot_postmoogle_sentry: ''
-
-# Sentry integration
-matrix_bot_postmoogle_monitoring_sentry_dsn: "{{ matrix_bot_postmoogle_sentry }}"
-matrix_bot_postmoogle_monitoring_sentry_rate: 20
-
-# healthchecks.io integration
-matrix_bot_postmoogle_monitoring_healthchecks_uuid: ''
-matrix_bot_postmoogle_monitoring_healthchecks_duration: 60
-
-# Log level
-matrix_bot_postmoogle_loglevel: 'INFO'
-
-# deprecated, use matrix_bot_postmoogle_domains
-matrix_bot_postmoogle_domain: "{{ matrix_server_fqn_matrix }}"
-
-matrix_bot_postmoogle_domains:
-  - "{{ matrix_bot_postmoogle_domain }}"  # backward compatibility
-
-# Password (passphrase) to encrypt account data
-matrix_bot_postmoogle_data_secret: ""
-
-# in-container ports
-matrix_bot_postmoogle_port: '2525'
-matrix_bot_postmoogle_tls_port: '25587'
-
-# on-host ports
-matrix_bot_postmoogle_smtp_host_bind_port: '25'
-matrix_bot_postmoogle_submission_host_bind_port: '587'
-
-### SSL
-## on-host SSL dir
-matrix_bot_postmoogle_ssl_path: ""
-
-## in-container SSL paths
-# matrix_bot_postmoogle_tls_cert is the SSL certificates' certificates.
-# This var is likely set via group_vars/matrix_servers, so you don't need to set certs manually.
-# If you do need to set it manually, note that this is an in-container path.
-# To mount a certificates volumes into the container, use matrix_bot_postmoogle_ssl_path
-# Example value: /ssl/live/{{ matrix_bot_postmoogle_domain }}/fullchain.pem
-matrix_bot_postmoogle_tls_cert: ""
-
-# matrix_bot_postmoogle_tls_key is the SSL certificates' keys.
-# This var is likely set via group_vars/matrix_servers, so you don't need to set keys manually.
-# If you do need to set it manually, note that this is an in-container path.
-# To mount a certificates volumes into the container, use matrix_bot_postmoogle_ssl_path
-# Example value: /ssl/live/{{ matrix_bot_postmoogle_domain }}/privkey.pem
-matrix_bot_postmoogle_tls_key: ""
-
-# Mandatory TLS, even on plain SMTP port
-matrix_bot_postmoogle_tls_required: false
-
-# trusted proxies
-matrix_bot_postmoogle_proxies: []
-
-# known forwarders
-matrix_bot_postmoogle_mailboxes_forwarded: []
-
-# reserved mailboxes
-matrix_bot_postmoogle_mailboxes_reserved: []
-
-# mailbox activation flow
-matrix_bot_postmoogle_mailboxes_activation: none
-
-# Additional environment variables to pass to the postmoogle container
-#
-# Example:
-# matrix_bot_postmoogle_environment_variables_extension: |
-#   postmoogle_TEXT_DONE=Done
-matrix_bot_postmoogle_environment_variables_extension: ''
diff --git a/roles/custom/matrix-bot-postmoogle/tasks/setup_install.yml b/roles/custom/matrix-bot-postmoogle/tasks/setup_install.yml
deleted file mode 100644
index 1ef5b22d7..000000000
--- a/roles/custom/matrix-bot-postmoogle/tasks/setup_install.yml
+++ /dev/null
@@ -1,94 +0,0 @@
----
-- when: "matrix_bot_postmoogle_database_engine == 'postgres'"
-  block:
-    - name: Check if an SQLite database already exists
-      ansible.builtin.stat:
-        path: "{{ matrix_bot_postmoogle_sqlite_database_path_local }}"
-      register: matrix_bot_postmoogle_sqlite_database_path_local_stat_result
-
-    - when: "matrix_bot_postmoogle_sqlite_database_path_local_stat_result.stat.exists | bool"
-      block:
-        - ansible.builtin.include_role:
-            name: galaxy/postgres
-            tasks_from: migrate_db_to_postgres
-          vars:
-            postgres_db_migration_request:
-              src: "{{ matrix_bot_postmoogle_sqlite_database_path_local }}"
-              dst: "{{ matrix_bot_postmoogle_database_connection_string }}"
-              caller: "{{ role_path | basename }}"
-              engine_variable_name: 'matrix_bot_postmoogle_database_engine'
-              engine_old: 'sqlite'
-              systemd_services_to_stop: ['matrix-bot-postmoogle.service']
-
-        - ansible.builtin.set_fact:
-            matrix_bot_postmoogle_requires_restart: true
-
-- name: Ensure postmoogle paths exist
-  ansible.builtin.file:
-    path: "{{ item.path }}"
-    state: directory
-    mode: 0750
-    owner: "{{ matrix_user_username }}"
-    group: "{{ matrix_user_groupname }}"
-  with_items:
-    - {path: "{{ matrix_bot_postmoogle_config_path }}", when: true}
-    - {path: "{{ matrix_bot_postmoogle_data_path }}", when: true}
-    - {path: "{{ matrix_bot_postmoogle_docker_src_files_path }}", when: matrix_bot_postmoogle_container_image_self_build}
-  when: "item.when | bool"
-
-- name: Ensure postmoogle environment variables file created
-  ansible.builtin.template:
-    src: "{{ role_path }}/templates/env.j2"
-    dest: "{{ matrix_bot_postmoogle_config_path }}/env"
-    owner: "{{ matrix_user_username }}"
-    group: "{{ matrix_user_groupname }}"
-    mode: 0640
-
-- name: Ensure postmoogle image is pulled
-  community.docker.docker_image:
-    name: "{{ matrix_bot_postmoogle_docker_image }}"
-    source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}"
-    force_source: "{{ matrix_bot_postmoogle_docker_image_force_pull if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}"
-    force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_bot_postmoogle_docker_image_force_pull }}"
-  when: "not matrix_bot_postmoogle_container_image_self_build | bool"
-  register: result
-  retries: "{{ devture_playbook_help_container_retries_count }}"
-  delay: "{{ devture_playbook_help_container_retries_delay }}"
-  until: result is not failed
-
-- name: Ensure postmoogle repository is present on self-build
-  ansible.builtin.git:
-    repo: "{{ matrix_bot_postmoogle_docker_repo }}"
-    version: "{{ matrix_bot_postmoogle_docker_repo_version }}"
-    dest: "{{ matrix_bot_postmoogle_docker_src_files_path }}"
-    force: "yes"
-  become: true
-  become_user: "{{ matrix_user_username }}"
-  register: matrix_bot_postmoogle_git_pull_results
-  when: "matrix_bot_postmoogle_container_image_self_build | bool"
-
-- name: Ensure postmoogle image is built
-  community.docker.docker_image:
-    name: "{{ matrix_bot_postmoogle_docker_image }}"
-    source: build
-    force_source: "{{ matrix_bot_postmoogle_git_pull_results.changed if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}"
-    force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_bot_postmoogle_git_pull_results.changed }}"
-    build:
-      dockerfile: Dockerfile
-      path: "{{ matrix_bot_postmoogle_docker_src_files_path }}"
-      pull: true
-  when: "matrix_bot_postmoogle_container_image_self_build | bool"
-
-- name: Ensure postmoogle container network is created
-  community.general.docker_network:
-    enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}"
-    name: "{{ matrix_bot_postmoogle_container_network }}"
-    driver: bridge
-    driver_options: "{{ devture_systemd_docker_base_container_networks_driver_options }}"
-
-- name: Ensure matrix-bot-postmoogle.service installed
-  ansible.builtin.template:
-    src: "{{ role_path }}/templates/systemd/matrix-bot-postmoogle.service.j2"
-    dest: "{{ devture_systemd_docker_base_systemd_path }}/matrix-bot-postmoogle.service"
-    mode: 0644
-  register: matrix_bot_postmoogle_systemd_service_result
diff --git a/roles/custom/matrix-bot-postmoogle/tasks/validate_config.yml b/roles/custom/matrix-bot-postmoogle/tasks/validate_config.yml
deleted file mode 100644
index 77f03356a..000000000
--- a/roles/custom/matrix-bot-postmoogle/tasks/validate_config.yml
+++ /dev/null
@@ -1,12 +0,0 @@
----
-
-- name: Fail if required Postmoogle settings not defined
-  ansible.builtin.fail:
-    msg: >-
-      You need to define a required configuration setting (`{{ item.name }}`).
-  when: "item.when | bool and vars[item.name] == ''"
-  with_items:
-    - {'name': 'matrix_bot_postmoogle_password', when: true}
-    - {'name': 'matrix_bot_postmoogle_container_network', when: true}
-    - {'name': 'matrix_bot_postmoogle_homeserver', when: true}
-    - {'name': 'matrix_bot_postmoogle_database_hostname', when: "{{ matrix_bot_postmoogle_database_engine == 'postgres' }}"}
diff --git a/roles/custom/matrix-bot-postmoogle/templates/env.j2 b/roles/custom/matrix-bot-postmoogle/templates/env.j2
deleted file mode 100644
index 8a3eb71b2..000000000
--- a/roles/custom/matrix-bot-postmoogle/templates/env.j2
+++ /dev/null
@@ -1,31 +0,0 @@
-POSTMOOGLE_LOGIN={{ matrix_bot_postmoogle_login }}
-POSTMOOGLE_PASSWORD={{ matrix_bot_postmoogle_password }}
-POSTMOOGLE_SHAREDSECRET={{ matrix_bot_postmoogle_sharedsecret }}
-POSTMOOGLE_HOMESERVER={{ matrix_bot_postmoogle_homeserver }}
-POSTMOOGLE_DOMAINS={{ matrix_bot_postmoogle_domains | join(' ') }}
-POSTMOOGLE_PORT={{ matrix_bot_postmoogle_port }}
-POSTMOOGLE_DB_DSN={{ matrix_bot_postmoogle_database_connection_string }}
-POSTMOOGLE_DB_DIALECT={{ matrix_bot_postmoogle_database_dialect }}
-POSTMOOGLE_PREFIX={{ matrix_bot_postmoogle_prefix }}
-POSTMOOGLE_MAXSIZE={{ matrix_bot_postmoogle_maxsize }}
-POSTMOOGLE_LOGLEVEL={{ matrix_bot_postmoogle_loglevel }}
-POSTMOOGLE_ADMINS={{ matrix_bot_postmoogle_admins | join(' ') }}
-POSTMOOGLE_TLS_PORT={{ matrix_bot_postmoogle_tls_port }}
-POSTMOOGLE_TLS_CERT={{ matrix_bot_postmoogle_tls_cert }}
-POSTMOOGLE_TLS_KEY={{ matrix_bot_postmoogle_tls_key }}
-POSTMOOGLE_TLS_REQUIRED={{ matrix_bot_postmoogle_tls_required }}
-POSTMOOGLE_DATA_SECRET={{ matrix_bot_postmoogle_data_secret }}
-POSTMOOGLE_PROXIES={{ matrix_bot_postmoogle_proxies | join(' ') }}
-POSTMOOGLE_RELAY_HOST={{ matrix_bot_postmoogle_relay_host }}
-POSTMOOGLE_RELAY_PORT={{ matrix_bot_postmoogle_relay_port }}
-POSTMOOGLE_RELAY_USERNAME={{ matrix_bot_postmoogle_relay_username }}
-POSTMOOGLE_RELAY_PASSWORD={{ matrix_bot_postmoogle_relay_password }}
-POSTMOOGLE_MONITORING_SENTRY_DSN={{ matrix_bot_postmoogle_monitoring_sentry_dsn }}
-POSTMOOGLE_MONITORING_SENTRY_RATE={{ matrix_bot_postmoogle_monitoring_sentry_rate }}
-POSTMOOGLE_MONITORING_HEALTHCHECKS_UUID={{ matrix_bot_postmoogle_monitoring_healthchecks_uuid }}
-POSTMOOGLE_MONITORING_HEALTHCHECKS_DURATION={{ matrix_bot_postmoogle_monitoring_healthchecks_duration }}
-POSTMOOGLE_MAILBOXES_FORWARDED={{ matrix_bot_postmoogle_mailboxes_forwarded | join(' ') }}
-POSTMOOGLE_MAILBOXES_RESERVED={{ matrix_bot_postmoogle_mailboxes_reserved | join(' ') }}
-POSTMOOGLE_MAILBOXES_ACTIVATION={{ matrix_bot_postmoogle_mailboxes_activation }}
-
-{{ matrix_bot_postmoogle_environment_variables_extension }}
diff --git a/roles/custom/matrix-bridge-appservice-discord/defaults/main.yml b/roles/custom/matrix-bridge-appservice-discord/defaults/main.yml
index 1ca26ee01..64b2d7db8 100644
--- a/roles/custom/matrix-bridge-appservice-discord/defaults/main.yml
+++ b/roles/custom/matrix-bridge-appservice-discord/defaults/main.yml
@@ -1,6 +1,6 @@
 ---
 # matrix-appservice-discord is a Matrix <-> Discord bridge
-# Project source code URL: https://github.com/Half-Shot/matrix-appservice-discord
+# Project source code URL: https://github.com/matrix-org/matrix-appservice-discord
 
 matrix_appservice_discord_enabled: false
 matrix_appservice_discord_container_image_self_build: false
diff --git a/roles/custom/matrix-bridge-appservice-discord/templates/config.yaml.j2 b/roles/custom/matrix-bridge-appservice-discord/templates/config.yaml.j2
index 2309be443..64f2923cc 100644
--- a/roles/custom/matrix-bridge-appservice-discord/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-appservice-discord/templates/config.yaml.j2
@@ -64,7 +64,7 @@ database:
   # You may either use SQLite or Postgresql for the bridge database, which contains
   # important mappings for events and user puppeting configurations.
   # Use the filename option for SQLite, or connString for Postgresql.
-  # If you are migrating, see https://github.com/Half-Shot/matrix-appservice-discord/blob/master/docs/howto.md#migrate-to-postgres-from-sqlite
+  # If you are migrating, see https://github.com/matrix-org/matrix-appservice-discord/blob/master/docs/howto.md#migrate-to-postgres-from-sqlite
   # WARNING: You will almost certainly be fine with sqlite unless your bridge
   # is in heavy demand and you suffer from IO slowness.
   {% if matrix_appservice_discord_database_engine == 'sqlite' %}
diff --git a/roles/custom/matrix-bridge-appservice-irc/defaults/main.yml b/roles/custom/matrix-bridge-appservice-irc/defaults/main.yml
index 0e6ffbc09..4ae0d8655 100644
--- a/roles/custom/matrix-bridge-appservice-irc/defaults/main.yml
+++ b/roles/custom/matrix-bridge-appservice-irc/defaults/main.yml
@@ -77,7 +77,7 @@ matrix_appservice_irc_ircService_servers: []  # noqa var-naming
 #     # networkId: "example"
 
 #     # URL to an icon used as the network icon whenever this network appear in
-#     # a network list. (Like in the riot room directory, for instance.)
+#     # a network list. (Like in the Riot room directory, for instance.)
 #     # icon: https://example.com/images/hash.png
 
 #     # The port to connect to. Optional.
@@ -95,7 +95,7 @@ matrix_appservice_irc_ircService_servers: []  # noqa var-naming
 #     # A specific CA to trust instead of the default CAs. Optional.
 #     #ca: |
 #     #  -----BEGIN CERTIFICATE-----
-#     #  ...
+#     #  …
 #     #  -----END CERTIFICATE-----
 
 #     #
diff --git a/roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2 b/roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2
index cf3644a9b..709a59934 100644
--- a/roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-appservice-kakaotalk/templates/config.yaml.j2
@@ -225,8 +225,8 @@ bridge:
         #
         # Available variables:
         #   $sender_displayname - The display name of the sender (e.g. Example User)
-        #   $sender_username    - The username (Matrix ID localpart) of the sender (e.g. exampleuser)
-        #   $sender_mxid        - The Matrix ID of the sender (e.g. @exampleuser:example.com)
+        #   $sender_username    - The username (Matrix ID localpart) of the sender (e.g. alice)
+        #   $sender_mxid        - The Matrix ID of the sender (e.g. @alice:example.com)
         #   $message            - The message content
         message_formats:
             m.text: '<b>$sender_displayname</b>: $message'
diff --git a/roles/custom/matrix-bridge-beeper-linkedin/defaults/main.yml b/roles/custom/matrix-bridge-beeper-linkedin/defaults/main.yml
index 936b2844a..fcba1e9b6 100644
--- a/roles/custom/matrix-bridge-beeper-linkedin/defaults/main.yml
+++ b/roles/custom/matrix-bridge-beeper-linkedin/defaults/main.yml
@@ -60,7 +60,8 @@ matrix_beeper_linkedin_appservice_token: ""
 matrix_beeper_linkedin_homeserver_token: ""
 
 matrix_beeper_linkedin_appservice_bot_username: linkedinbot
-
+matrix_beeper_linkedin_appservice_bot_displayname: LinkedIn bridge bot
+matrix_beeper_linkedin_appservice_bot_avatar: mxc://nevarro.space/cwsWnmeMpWSMZLUNblJHaIvP
 
 # Database-related configuration fields.
 # Only Postgres is supported.
@@ -87,9 +88,24 @@ matrix_beeper_linkedin_appservice_database_uri: "{{
 	}[matrix_beeper_linkedin_database_engine]
 }}"
 
+matrix_beeper_linkedin_bridge_login_shared_secret_map: "{{ matrix_beeper_linkedin_bridge_login_shared_secret_map_auto | combine(matrix_beeper_linkedin_bridge_login_shared_secret_map_custom) }}"
+matrix_beeper_linkedin_bridge_login_shared_secret_map_auto: {}
+matrix_beeper_linkedin_bridge_login_shared_secret_map_custom: {}
 
-# Can be set to enable automatic double-puppeting via Shared Secret Auth (https://github.com/devture/matrix-synapse-shared-secret-auth) or Appservice Double Puppet.
-matrix_beeper_linkedin_login_shared_secret: ''
+# Servers to always allow double puppeting from
+matrix_beeper_linkedin_bridge_double_puppet_server_map: "{{ matrix_beeper_linkedin_bridge_double_puppet_server_map_default | combine(matrix_beeper_linkedin_bridge_double_puppet_server_map_auto) | combine(matrix_beeper_linkedin_bridge_double_puppet_server_map_custom) }}"
+matrix_beeper_linkedin_bridge_double_puppet_server_map_default: |-
+  {{
+    {}
+    | combine({
+      matrix_beeper_linkedin_homeserver_domain: matrix_beeper_linkedin_homeserver_address
+    })
+  }}
+matrix_beeper_linkedin_bridge_double_puppet_server_map_auto: {}
+matrix_beeper_linkedin_bridge_double_puppet_server_map_custom: {}
+
+matrix_beeper_linkedin_provisioning_enabled: false
+matrix_beeper_linkedin_provisioning_shared_secret: ''
 
 # Specifies the default log level for all bridge loggers.
 matrix_beeper_linkedin_logging_level: WARNING
@@ -97,6 +113,8 @@ matrix_beeper_linkedin_logging_level: WARNING
 # Enable End-to-bridge encryption
 matrix_beeper_linkedin_bridge_encryption_allow: "{{ matrix_bridges_encryption_enabled }}"
 matrix_beeper_linkedin_bridge_encryption_default: "{{ matrix_bridges_encryption_default }}"
+matrix_beeper_linkedin_bridge_encryption_appservice: "{{ matrix_beeper_linkedin_bridge_encryption_default }}"
+matrix_beeper_linkedin_bridge_encryption_require: false
 matrix_beeper_linkedin_bridge_encryption_key_sharing_allow: "{{ matrix_beeper_linkedin_bridge_encryption_allow }}"
 
 # Default beeper-linkedin configuration template which covers the generic use case.
diff --git a/roles/custom/matrix-bridge-beeper-linkedin/tasks/setup_install.yml b/roles/custom/matrix-bridge-beeper-linkedin/tasks/setup_install.yml
index 1c8bfe965..7d27b1559 100644
--- a/roles/custom/matrix-bridge-beeper-linkedin/tasks/setup_install.yml
+++ b/roles/custom/matrix-bridge-beeper-linkedin/tasks/setup_install.yml
@@ -14,8 +14,23 @@
     - {path: "{{ matrix_beeper_linkedin_docker_src_files_path }}", when: "{{ matrix_beeper_linkedin_container_image_self_build }}"}
   when: "item.when | bool"
 
+- name: Ensure beeper-linkedin config.yaml installed
+  ansible.builtin.copy:
+    content: "{{ matrix_beeper_linkedin_configuration | to_nice_yaml(indent=2, width=999999) }}"
+    dest: "{{ matrix_beeper_linkedin_config_path }}/config.yaml"
+    mode: 0644
+    owner: "{{ matrix_user_username }}"
+    group: "{{ matrix_user_groupname }}"
 
-- name: Ensure Beeper LinkedIn image is pulled
+- name: Ensure beeper-linkedin registration.yaml installed
+  ansible.builtin.copy:
+    content: "{{ matrix_beeper_linkedin_registration | to_nice_yaml(indent=2, width=999999) }}"
+    dest: "{{ matrix_beeper_linkedin_config_path }}/registration.yaml"
+    mode: 0644
+    owner: "{{ matrix_user_username }}"
+    group: "{{ matrix_user_groupname }}"
+
+- name: Ensure Beeper LinkedIn container image is pulled
   community.docker.docker_image:
     name: "{{ matrix_beeper_linkedin_docker_image }}"
     source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}"
@@ -41,7 +56,7 @@
 
     # Building the container image (using the default Dockerfile) requires that a docker-requirements.txt file be generated.
     # See: https://github.com/beeper/linkedin/blob/94442db17ccb9769b377cdb8e4bf1cb3955781d7/.gitlab-ci.yml#L30-40
-    - name: Ensure docker-requirements.txt is generated before building Beeper LinkedIn Docker Image
+    - name: Ensure docker-requirements.txt is generated before building Beeper LinkedIn container image
       ansible.builtin.command:
         cmd: |
           {{ devture_systemd_docker_base_host_command_docker }} run
@@ -54,7 +69,7 @@
       register: matrix_beeper_linkedin_generate_docker_requirements_result
       changed_when: matrix_beeper_linkedin_generate_docker_requirements_result.rc == 0
 
-    - name: Ensure Beeper LinkedIn Docker image is built
+    - name: Ensure Beeper LinkedIn container image is built
       community.docker.docker_image:
         name: "{{ matrix_beeper_linkedin_docker_image }}"
         source: build
@@ -67,22 +82,6 @@
           args:
             TARGETARCH: "{{ matrix_architecture }}"
 
-- name: Ensure beeper-linkedin config.yaml installed
-  ansible.builtin.copy:
-    content: "{{ matrix_beeper_linkedin_configuration | to_nice_yaml(indent=2, width=999999) }}"
-    dest: "{{ matrix_beeper_linkedin_config_path }}/config.yaml"
-    mode: 0644
-    owner: "{{ matrix_user_username }}"
-    group: "{{ matrix_user_groupname }}"
-
-- name: Ensure beeper-linkedin registration.yaml installed
-  ansible.builtin.copy:
-    content: "{{ matrix_beeper_linkedin_registration | to_nice_yaml(indent=2, width=999999) }}"
-    dest: "{{ matrix_beeper_linkedin_config_path }}/registration.yaml"
-    mode: 0644
-    owner: "{{ matrix_user_username }}"
-    group: "{{ matrix_user_groupname }}"
-
 - name: Ensure beeper-linkedin container network is created
   community.general.docker_network:
     enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}"
diff --git a/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml b/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml
index afbf5c619..cbf77eb71 100644
--- a/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml
+++ b/roles/custom/matrix-bridge-beeper-linkedin/tasks/validate_config.yml
@@ -11,3 +11,12 @@
     - {'name': 'matrix_beeper_linkedin_homeserver_token', when: true}
     - {'name': 'matrix_beeper_linkedin_database_hostname', when: "{{ matrix_beeper_linkedin_database_engine == 'postgres' }}"}
     - {'name': 'matrix_beeper_linkedin_container_network', when: true}
+
+- name: (Deprecation) Catch and report renamed beeper-linkedin settings
+  ansible.builtin.fail:
+    msg: >-
+      Your configuration contains a variable, which now has a different name.
+      Please change your configuration to rename the variable (`{{ item.old }}` -> `{{ item.new }}`).
+  when: "item.old in vars"
+  with_items:
+    - {'old': 'matrix_beeper_linkedin_login_shared_secret', 'new': '<superseded by matrix_beeper_linkedin_bridge_login_shared_secret_map_*>'}
diff --git a/roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2 b/roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2
index 531adfd98..d73988cdf 100644
--- a/roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-beeper-linkedin/templates/config.yaml.j2
@@ -1,62 +1,74 @@
 #jinja2: lstrip_blocks: "True"
-# Homeserver details.
+# Homeserver details
 homeserver:
     # The address that this appservice can use to connect to the homeserver.
-    address: {{ matrix_beeper_linkedin_homeserver_address }}
+    address: {{ matrix_beeper_linkedin_homeserver_address | to_json }}
     # The domain of the homeserver (for MXIDs, etc).
-    domain: {{ matrix_beeper_linkedin_homeserver_domain }}
+    domain: {{ matrix_beeper_linkedin_homeserver_domain | to_json }}
     # Whether or not to verify the SSL certificate of the homeserver.
     # Only applies if address starts with https://
     verify_ssl: true
-    # Whether or not the homeserver supports asmux-specific endpoints,
-    # such as /_matrix/client/unstable/net.maunium.asmux/dms for atomically
-    # updating m.direct.
-    asmux: false
+    # What software is the homeserver running?
+    # Standard Matrix homeservers like Synapse, Dendrite and Conduit should just use "standard" here.
+    software: standard
     # Number of retries for all HTTP requests if the homeserver isn't reachable.
     http_retry_count: 4
+    # The URL to push real-time bridge status to.
+    # If set, the bridge will make POST requests to this URL whenever a user's Signal connection state changes.
+    # The bridge will use the appservice as_token to authorize requests.
+    status_endpoint: null
+    # Endpoint for reporting per-message status.
+    message_send_checkpoint_endpoint: null
+    # Whether asynchronous uploads via MSC2246 should be enabled for media.
+    # Requires a media repo that supports MSC2246.
+    async_media: false
 
-
+# Application service host/registration related details
+# Changing these values requires regeneration of the registration.
 appservice:
     # The address that the homeserver can use to connect to this appservice.
-    address: {{ matrix_beeper_linkedin_appservice_address }}
+    address: {{ matrix_beeper_linkedin_appservice_address | to_json }}
 
     # The hostname and port where this appservice should listen.
     hostname: 0.0.0.0
     port: 29319
-
     # The maximum body size of appservice API requests (from the homeserver) in mebibytes
     # Usually 1 is enough, but on high-traffic bridges you might need to increase this to avoid 413s
     max_body_size: 1
 
-    # The full URI to the database. Only Postgres is currently supported.
-    database: {{ matrix_beeper_linkedin_appservice_database_uri|to_json }}
-    # Additional arguments for asyncpg.create_pool()
+    # The full URI to the database. SQLite and Postgres are supported.
+    # Format examples:
+    #   SQLite:   sqlite:filename.db
+    #   Postgres: postgres://username:password@hostname/dbname
+    database: {{ matrix_beeper_linkedin_appservice_database_uri | to_json }}
+    # Additional arguments for asyncpg.create_pool() or sqlite3.connect()
     # https://magicstack.github.io/asyncpg/current/api/index.html#asyncpg.pool.create_pool
+    # https://docs.python.org/3/library/sqlite3.html#sqlite3.connect
+    # For sqlite, min_size is used as the connection thread pool size and max_size is ignored.
+    # Additionally, SQLite supports init_commands as an array of SQL queries to run on connect (e.g. to set PRAGMAs).
     database_opts:
-        min_size: 5
+        min_size: 1
         max_size: 10
 
     # Provisioning API part of the web server for automated portal creation and fetching information.
     # Used by things like mautrix-manager (https://github.com/tulir/mautrix-manager).
     provisioning:
         # Whether or not the provisioning API should be enabled.
-        enabled: true
+        enabled: {{ matrix_beeper_linkedin_provisioning_enabled | to_json }}
         # The prefix to use in the provisioning API endpoints.
         prefix: /_matrix/provision/v1
         # The shared secret to authorize users of the API.
         # Set to "generate" to generate and save a new token.
-        shared_secret: generate
+        shared_secret: {{ matrix_beeper_linkedin_provisioning_shared_secret | to_json }}
 
     # The unique ID of this appservice.
     id: beeper_linkedin
-    # Appservice bot details.
-    bot:
-        # Username of the appservice bot.
-        username: {{ matrix_beeper_linkedin_appservice_bot_username|to_json }}
-        # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty
-        # to leave display name/avatar as-is.
-        displayname: LinkedIn bridge bot
-        avatar: mxc://sumnerevans.com/XMtwdeUBnxYvWNFFrfeTSHqB
+    # Username of the appservice bot.
+    bot_username: {{ matrix_beeper_linkedin_appservice_bot_username | to_json }}
+    # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty
+    # to leave display name/avatar as-is.
+    bot_displayname: {{ matrix_beeper_linkedin_appservice_bot_displayname | to_json }}
+    bot_avatar: {{ matrix_beeper_linkedin_appservice_bot_avatar | to_json }}
 
     # Whether or not to receive ephemeral events via appservice transactions.
     # Requires MSC2409 support (i.e. Synapse 1.22+).
@@ -64,9 +76,17 @@ appservice:
     ephemeral_events: false
 
     # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify.
-    as_token: "{{ matrix_beeper_linkedin_appservice_token }}"
-    hs_token: "{{ matrix_beeper_linkedin_homeserver_token }}"
+    as_token: {{ matrix_beeper_linkedin_appservice_token | to_json }}
+    hs_token: {{ matrix_beeper_linkedin_homeserver_token | to_json }}
 
+# Segment-compatible analytics endpoint for tracking some events, like provisioning API login and encryption errors.
+analytics:
+    # Hostname of the tracking server. The path is hardcoded to /v1/track
+    host: api.segment.io
+    # API key to send with tracking requests. Tracking is disabled if this is null.
+    token: null
+    # Optional user ID for tracking events. If null, defaults to using Matrix user ID.
+    user_id: null
 
 # Prometheus telemetry config. Requires prometheus-client to be installed.
 metrics:
@@ -84,30 +104,41 @@ manhole:
     whitelist:
     - 0
 
-
 # Bridge config
 bridge:
     # Localpart template of MXIDs for LinkedIn users.
-    # {userid} is replaced with the user ID of the LinkedIn user
+    # {userid} is replaced with the user ID of the LinkedIn user.
     username_template: "linkedin_{userid}"
     # Settings for creating a space for every user.
     space_support:
         # Whether or not to enable creating a space per user and inviting the
         # user (as well as all of the puppets) to that space.
-        enable: {{ matrix_beeper_linkedin_bridge_space_support_enable|to_json }}
+        enable: {{ matrix_beeper_linkedin_bridge_space_support_enable | to_json }}
         # The name of the space
         name: "LinkedIn"
-
     # Displayname template for LinkedIn users.
     # {displayname} is replaced with the display name of the LinkedIn user
     #               as defined below in displayname_preference.
     # Keys available for displayname_preference are also available here.
     displayname_template: "{displayname} (LinkedIn)"
+    # Available keys:
+    # "name" (full name)
+    # "first_name"
+    # "last_name"
+    displayname_preference:
+    - name
+    - first_name
+
+    # Whether or not to set the topic on DMs to the user's occupation and a
+    # link to their profile.
+    set_topic_on_dms: true
+
+    # The prefix for commands. Only required in non-management rooms.
+    command_prefix: {{ matrix_beeper_linkedin_command_prefix | to_json }}
 
     # Number of chats to sync (and create portals for) on startup/login.
     # Set 0 to disable automatic syncing.
-    initial_chat_sync: 10
-
+    initial_chat_sync: 20
     # Whether or not the LinkedIn users of logged in Matrix users should be
     # invited to private chats when the user sends a message from another client.
     invite_own_puppet_to_pm: false
@@ -119,65 +150,112 @@ bridge:
     # and is therefore prone to race conditions.
     sync_direct_chat_list: false
     # Servers to always allow double puppeting from
-    double_puppet_server_map: {}
-    #    example.com: https://example.com
+    double_puppet_server_map: {{ matrix_beeper_linkedin_bridge_double_puppet_server_map | to_json }}
     # Allow using double puppeting from any server with a valid client .well-known file.
-
-    # Maximum number of seconds since last message in chat to skip
-    # syncing the chat in any case. This setting will take priority
-    # over both recovery_chat_sync_limit and initial_chat_sync_count.
-    # Default is 3 days = 259200 seconds
-    sync_max_chat_age: 259200
-
-    # Whether or not to sync with custom puppets to receive EDUs that
-    # are not normally sent to appservices.
-    sync_with_custom_puppets: true
-    # Shared secret for https://github.com/devture/matrix-synapse-shared-secret-auth
+    double_puppet_allow_discovery: false
+    # Shared secrets for https://github.com/devture/matrix-synapse-shared-secret-auth
     #
     # If set, custom puppets will be enabled automatically for local users
     # instead of users having to find an access token and run `login-matrix`
     # manually.
-    login_shared_secret: {{ matrix_beeper_linkedin_login_shared_secret|to_json }}
-
-    # Allow using double puppeting from any server with a valid client .well-known file.
-    double_puppet_allow_discovery: false
-
+    # If using this for other servers than the bridge's server,
+    # you must also set the URL in the double_puppet_server_map.
+    login_shared_secret_map: {{ matrix_beeper_linkedin_bridge_login_shared_secret_map | to_json }}
     # Whether or not to bridge presence in both directions. LinkedIn allows users not to broadcast
     # presence, but then it won't send other users' presence to the client.
-    presence: {{ matrix_beeper_linkedin_bridge_presence|to_json }}
+    presence: {{ matrix_beeper_linkedin_bridge_presence | to_json }}
     # Whether or not to update avatars when syncing all contacts at startup.
     update_avatar_initial_sync: true
+    # Whether or not created rooms should have federation enabled.
+    # If false, created portal rooms will never be federated.
+    federate_rooms: true
+    # Whether to explicitly set the avatar and room name for private chat portal rooms.
+    # If set to `default`, this will be enabled in encrypted rooms and disabled in unencrypted rooms.
+    # If set to `always`, all DM rooms will have explicit names and avatars set.
+    # If set to `never`, DM rooms will never have names and avatars set.
+    private_chat_portal_meta: default
 
-
-    # End-to-bridge encryption support options. These require matrix-nio to be installed with pip
-    # and login_shared_secret to be configured in order to get a device for the bridge bot.
+    # End-to-bridge encryption support options.
     #
-    # Additionally, https://github.com/matrix-org/synapse/pull/5758 is required if using a normal
-    # application service.
+    # See https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html for more info.
     encryption:
         # Allow encryption, work in group chat rooms with e2ee enabled
-        allow: {{ matrix_beeper_linkedin_bridge_encryption_allow|to_json }}
+        allow: {{ matrix_beeper_linkedin_bridge_encryption_allow | to_json }}
         # Default to encryption, force-enable encryption in all portals the bridge creates
         # This will cause the bridge bot to be in private chats for the encryption to work properly.
-        default: {{ matrix_beeper_linkedin_bridge_encryption_default|to_json }}
-        # Options for automatic key sharing.
-        key_sharing:
-            # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
-            # You must use a client that supports requesting keys from other users to use this feature.
-            allow: {{ matrix_beeper_linkedin_bridge_encryption_key_sharing_allow|to_json }}
-            # Require the requesting device to have a valid cross-signing signature?
-            # This doesn't require that the bridge has verified the device, only that the user has verified it.
-            # Not yet implemented.
-            require_cross_signing: false
-            # Require devices to be verified by the bridge?
-            # Verification by the bridge is not yet implemented.
-            require_verification: true
+        default: {{ matrix_beeper_linkedin_bridge_encryption_default | to_json }}
+        # Whether to use MSC2409/MSC3202 instead of /sync long polling for receiving encryption-related data.
+        appservice: {{ matrix_beeper_linkedin_bridge_encryption_appservice | to_json }}
+        # Require encryption, drop any unencrypted messages.
+        require: {{ matrix_beeper_linkedin_bridge_encryption_require | to_json }}
+        # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
+        # You must use a client that supports requesting keys from other users to use this feature.
+        allow_key_sharing: {{ matrix_beeper_linkedin_bridge_encryption_key_sharing_allow | to_json }}
+        # Options for deleting megolm sessions from the bridge.
+        delete_keys:
+            # Beeper-specific: delete outbound sessions when hungryserv confirms
+            # that the user has uploaded the key to key backup.
+            delete_outbound_on_ack: false
+            # Don't store outbound sessions in the inbound table.
+            dont_store_outbound: false
+            # Ratchet megolm sessions forward after decrypting messages.
+            ratchet_on_decrypt: false
+            # Delete fully used keys (index >= max_messages) after decrypting messages.
+            delete_fully_used_on_decrypt: false
+            # Delete previous megolm sessions from same device when receiving a new one.
+            delete_prev_on_new_session: false
+            # Delete megolm sessions received from a device when the device is deleted.
+            delete_on_device_delete: false
+            # Periodically delete megolm sessions when 2x max_age has passed since receiving the session.
+            periodically_delete_expired: false
+            # Delete inbound megolm sessions that don't have the received_at field used for
+            # automatic ratcheting and expired session deletion. This is meant as a migration
+            # to delete old keys prior to the bridge update.
+            delete_outdated_inbound: false
+        # What level of device verification should be required from users?
+        #
+        # Valid levels:
+        #   unverified - Send keys to all device in the room.
+        #   cross-signed-untrusted - Require valid cross-signing, but trust all cross-signing keys.
+        #   cross-signed-tofu - Require valid cross-signing, trust cross-signing keys on first use (and reject changes).
+        #   cross-signed-verified - Require valid cross-signing, plus a valid user signature from the bridge bot.
+        #                           Note that creating user signatures from the bridge bot is not currently possible.
+        #   verified - Require manual per-device verification
+        #              (currently only possible by modifying the `trust` column in the `crypto_device` database table).
+        verification_levels:
+            # Minimum level for which the bridge should send keys to when bridging messages from Telegram to Matrix.
+            receive: unverified
+            # Minimum level that the bridge should accept for incoming Matrix messages.
+            send: unverified
+            # Minimum level that the bridge should require for accepting key requests.
+            share: cross-signed-tofu
+        # Options for Megolm room key rotation. These options allow you to
+        # configure the m.room.encryption event content. See:
+        # https://spec.matrix.org/v1.3/client-server-api/#mroomencryption for
+        # more information about that event.
+        rotation:
+            # Enable custom Megolm room key rotation settings. Note that these
+            # settings will only apply to rooms created after this option is
+            # set.
+            enable_custom: false
+            # The maximum number of milliseconds a session should be used
+            # before changing it. The Matrix spec recommends 604800000 (a week)
+            # as the default.
+            milliseconds: 604800000
+            # The maximum number of messages that should be sent with a given a
+            # session before changing it. The Matrix spec recommends 100 as the
+            # default.
+            messages: 100
+
+            # Disable rotating keys when a user's devices change?
+            # You should not enable this option unless you understand all the implications.
+            disable_device_change_key_rotation: false
+
     # Whether or not the bridge should send a read receipt from the bridge bot when a message has
     # been sent to LinkedIn.
     delivery_receipts: false
     # Whether to allow inviting arbitrary mxids to portal rooms
     allow_invites: false
-
     # Settings for backfilling messages from LinkedIn.
     backfill:
         # Whether or not the LinkedIn users of logged in Matrix users should be
@@ -194,6 +272,10 @@ bridge:
         # If using double puppeting, should notifications be disabled
         # while the initial backfill is in progress?
         disable_notifications: false
+        # If this value is greater than 0, then (on backfill) if the
+        # conversation's last message was more than this number of hours ago,
+        # then the conversation will automatically be marked it as read.
+        unread_hours_threshold: 0
     periodic_reconnect:
         # TODO needed?
         # Interval in seconds in which to automatically reconnect all users.
@@ -224,23 +306,20 @@ bridge:
     # Whether or not mute status and tags should only be bridged when the portal room is created.
     tag_only_on_create: true
 
-
-    # The prefix for commands. Only required in non-management rooms.
-    command_prefix: "{{ matrix_beeper_linkedin_command_prefix }}"
-
     # Permissions for using the bridge.
     # Permitted values:
-    #     user - Access to use the bridge to chat with a Linkedin account.
-    #    admin - User level and some additional administration tools
+    #       user - Use the bridge with puppeting.
+    #      admin - Use and administrate the bridge.
     # Permitted keys:
     #        * - All Matrix users
     #   domain - All users on that homeserver
     #     mxid - Specific user
-    permissions: {{ matrix_beeper_linkedin_bridge_permissions|to_json }}
+    permissions: {{ matrix_beeper_linkedin_bridge_permissions | to_json }}
 
-
-
-# Logging config.
+# Python logging configuration.
+#
+# See section 16.7.2 of the Python documentation for more info:
+# https://docs.python.org/3.6/library/logging.config.html#configuration-dictionary-schema
 logging:
     version: 1
     formatters:
@@ -256,10 +335,8 @@ logging:
     loggers:
         mau:
             level: {{ matrix_beeper_linkedin_logging_level|to_json }}
-        paho:
-            level: {{ matrix_beeper_linkedin_logging_level|to_json }}
         aiohttp:
             level: {{ matrix_beeper_linkedin_logging_level|to_json }}
     root:
-        level: {{ matrix_beeper_linkedin_logging_level|to_json }}
+        level: DEBUG
         handlers: [console]
diff --git a/roles/custom/matrix-bridge-beeper-linkedin/templates/systemd/matrix-beeper-linkedin.service.j2 b/roles/custom/matrix-bridge-beeper-linkedin/templates/systemd/matrix-beeper-linkedin.service.j2
index 68d062594..1b1cc582b 100644
--- a/roles/custom/matrix-bridge-beeper-linkedin/templates/systemd/matrix-beeper-linkedin.service.j2
+++ b/roles/custom/matrix-bridge-beeper-linkedin/templates/systemd/matrix-beeper-linkedin.service.j2
@@ -23,13 +23,13 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \
 			--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
 			--cap-drop=ALL \
 			--network={{ matrix_beeper_linkedin_container_network }} \
-			--mount type=bind,src={{ matrix_beeper_linkedin_config_path }},dst=/data \
+			--mount type=bind,src={{ matrix_beeper_linkedin_config_path }},dst=/config,ro \
 			--workdir=/opt/linkedin-matrix \
 			{% for arg in matrix_beeper_linkedin_container_extra_arguments %}
 			{{ arg }} \
 			{% endfor %}
 			{{ matrix_beeper_linkedin_docker_image }} \
-			python3 -m linkedin_matrix -c /data/config.yaml -r /data/registration.yaml
+			python3 -m linkedin_matrix -c /config/config.yaml -r /config/registration.yaml --no-update
 
 {% for network in matrix_beeper_linkedin_container_additional_networks %}
 ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network connect {{ network }} matrix-beeper-linkedin
diff --git a/roles/custom/matrix-bridge-heisenbridge/defaults/main.yml b/roles/custom/matrix-bridge-heisenbridge/defaults/main.yml
index 438799842..ee1cea6b4 100644
--- a/roles/custom/matrix-bridge-heisenbridge/defaults/main.yml
+++ b/roles/custom/matrix-bridge-heisenbridge/defaults/main.yml
@@ -1,5 +1,5 @@
 ---
-# heisenbridge is a bouncer-style Matrix IRC bridge
+# Heisenbridge is a bouncer-style Matrix IRC bridge
 # Project source code URL: https://github.com/hifi/heisenbridge
 
 matrix_heisenbridge_enabled: true
@@ -93,7 +93,7 @@ matrix_heisenbridge_registration_yaml_heisenbridge:
   displayname: "{{ matrix_heisenbridge_config_displayname }}"
 
 # Default registration file consumed by both the homeserver and Heisenbridge.
-# Besides registration information, it contains configuration (see the heisenbridge key).
+# Besides registration information, it contains configuration (see the Heisenbridge key).
 matrix_heisenbridge_registration_yaml:
   id: heisenbridge
   url: http://matrix-heisenbridge:9898
diff --git a/roles/custom/matrix-bridge-heisenbridge/tasks/setup_install.yml b/roles/custom/matrix-bridge-heisenbridge/tasks/setup_install.yml
index c854689da..9ea3500ff 100644
--- a/roles/custom/matrix-bridge-heisenbridge/tasks/setup_install.yml
+++ b/roles/custom/matrix-bridge-heisenbridge/tasks/setup_install.yml
@@ -1,6 +1,6 @@
 ---
 
-- name: Ensure heisenbridge image is pulled
+- name: Ensure Heisenbridge image is pulled
   community.docker.docker_image:
     name: "{{ matrix_heisenbridge_docker_image }}"
     source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}"
@@ -11,7 +11,7 @@
   delay: "{{ devture_playbook_help_container_retries_delay }}"
   until: result is not failed
 
-- name: Ensure heisenbridge paths exist
+- name: Ensure Heisenbridge paths exist
   ansible.builtin.file:
     path: "{{ item }}"
     state: directory
@@ -21,7 +21,7 @@
   with_items:
     - "{{ matrix_heisenbridge_base_path }}"
 
-- name: Ensure heisenbridge registration.yaml installed if provided
+- name: Ensure Heisenbridge registration.yaml installed if provided
   ansible.builtin.copy:
     content: "{{ matrix_heisenbridge_registration | to_nice_yaml(indent=2, width=999999) }}"
     dest: "{{ matrix_heisenbridge_base_path }}/registration.yaml"
@@ -29,7 +29,7 @@
     owner: "{{ matrix_user_username }}"
     group: "{{ matrix_user_groupname }}"
 
-- name: Ensure heisenbridge support files installed
+- name: Ensure Heisenbridge support files installed
   ansible.builtin.template:
     src: "{{ role_path }}/templates/{{ item }}.j2"
     dest: "{{ matrix_heisenbridge_base_path }}/{{ item }}"
@@ -39,7 +39,7 @@
   with_items:
     - labels
 
-- name: Ensure heisenbridge container network is created
+- name: Ensure Heisenbridge container network is created
   community.general.docker_network:
     enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}"
     name: "{{ matrix_heisenbridge_container_network }}"
diff --git a/roles/custom/matrix-bridge-heisenbridge/tasks/validate_config.yml b/roles/custom/matrix-bridge-heisenbridge/tasks/validate_config.yml
index 6f9516e3d..604df5a56 100644
--- a/roles/custom/matrix-bridge-heisenbridge/tasks/validate_config.yml
+++ b/roles/custom/matrix-bridge-heisenbridge/tasks/validate_config.yml
@@ -1,6 +1,6 @@
 ---
 
-- name: Fail if required heisenbridge settings not defined
+- name: Fail if required Heisenbridge settings not defined
   ansible.builtin.fail:
     msg: >-
       You need to define a required configuration setting (`{{ item.name }}`).
diff --git a/roles/custom/matrix-bridge-hookshot/defaults/main.yml b/roles/custom/matrix-bridge-hookshot/defaults/main.yml
index d36dfd7a9..8dd61e973 100644
--- a/roles/custom/matrix-bridge-hookshot/defaults/main.yml
+++ b/roles/custom/matrix-bridge-hookshot/defaults/main.yml
@@ -17,10 +17,10 @@ matrix_hookshot_container_additional_networks_auto: []
 matrix_hookshot_container_additional_networks_custom: []
 
 # renovate: datasource=docker depName=halfshot/matrix-hookshot
-matrix_hookshot_version: 5.4.1
+matrix_hookshot_version: 6.0.1
 
-matrix_hookshot_docker_image: "{{ matrix_hookshot_docker_image_name_prefix }}halfshot/matrix-hookshot:{{ matrix_hookshot_version }}"
-matrix_hookshot_docker_image_name_prefix: "{{ 'localhost/' if matrix_hookshot_container_image_self_build else matrix_container_global_registry_prefix }}"
+matrix_hookshot_docker_image: "{{ matrix_hookshot_docker_image_name_prefix }}matrix-org/matrix-hookshot:{{ matrix_hookshot_version }}"
+matrix_hookshot_docker_image_name_prefix: "{{ 'localhost/' if matrix_hookshot_container_image_self_build else 'ghcr.io/' }}"
 matrix_hookshot_docker_image_force_pull: "{{ matrix_hookshot_docker_image.endswith(':latest') }}"
 
 matrix_hookshot_base_path: "{{ matrix_base_data_path }}/hookshot"
@@ -30,6 +30,9 @@ matrix_hookshot_docker_src_files_path: "{{ matrix_hookshot_base_path }}/docker-s
 matrix_hookshot_homeserver_address: ""
 matrix_hookshot_container_url: 'matrix-hookshot'
 
+# Sets the localpart of the Matrix ID for the hookshot bot
+matrix_hookshot_bot_localpart: "hookshot"
+
 matrix_hookshot_public_scheme: https
 matrix_hookshot_public_hostname: "{{ matrix_server_fqn_matrix }}"
 matrix_hookshot_public_endpoint: /hookshot
@@ -46,17 +49,18 @@ matrix_hookshot_appservice_hostname: "{{ matrix_hookshot_public_hostname }}"
 matrix_hookshot_appservice_endpoint: "{{ matrix_hookshot_public_endpoint }}/_matrix/app"
 
 # The variables below control the Redis cache parameters.
-# Using caching is required when experimental encryption is enabled (`matrix_hookshot_experimental_encryption_enabled`)
+# Using caching is required when encryption is enabled (`matrix_hookshot_encryption_enabled`)
 # but may also speed up Hookshot startup, etc.
 matrix_hookshot_cache_redis_host: ''
 matrix_hookshot_cache_redis_port: "6379"
 matrix_hookshot_cache_redisUri: "{{ ('redis://' + matrix_hookshot_cache_redis_host + ':' + matrix_hookshot_cache_redis_port) if matrix_hookshot_cache_redis_host else '' }}"  # noqa var-naming
 
-# Controls whether the experimental end-to-bridge encryption support is enabled.
+# Controls whether the end-to-bridge encryption support is enabled.
 # This requires that:
 # - support to also be enabled in the homeserver, see the documentation of Hookshot.
 # - Hookshot to be pointed at a Redis instance via the `matrix_hookshot_cache_redis*` variables.
-matrix_hookshot_experimental_encryption_enabled: false
+# See: https://matrix-org.github.io/matrix-hookshot/latest/advanced/encryption.html
+matrix_hookshot_encryption_enabled: false
 
 # Controls whether metrics are enabled in the bridge configuration.
 # Enabling them is usually enough for a local (in-container) Prometheus to consume them.
@@ -86,7 +90,7 @@ matrix_hookshot_github_auth_id: ''
 # Set this variable to the contents of the generated and downloaded GitHub private key:
 # matrix_hookshot_github_private_key: |
 #   -----BEGIN RSA PRIVATE KEY-----
-#   0123456789ABCDEF...
+#   0123456789ABCDEF…
 #   -----END RSA PRIVATE KEY-----
 # Alternatively, leave it empty and do it manually or use matrix-aux instead, see docs/matrix-bridge-hookshot.md for info.
 matrix_hookshot_github_private_key: ''
diff --git a/roles/custom/matrix-bridge-hookshot/tasks/reset_encryption.yml b/roles/custom/matrix-bridge-hookshot/tasks/reset_encryption.yml
index 5d3b7506d..2ae5e7f8f 100644
--- a/roles/custom/matrix-bridge-hookshot/tasks/reset_encryption.yml
+++ b/roles/custom/matrix-bridge-hookshot/tasks/reset_encryption.yml
@@ -1,5 +1,13 @@
 ---
 
+- name: Ensure matrix-hookshot is stopped
+  ansible.builtin.service:
+    name: matrix-hookshot
+    state: stopped
+  register: matrix_hookshot_stopped
+
+# `yarn start:resetcrypto` fails, as described here: https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3868
+# Also related to: https://github.com/matrix-org/matrix-hookshot/issues/730
 - name: Resetting Hookshot's crypto store
   ansible.builtin.command:
     cmd: |
@@ -8,7 +16,15 @@
       --name={{ matrix_hookshot_identifier }}-reset-crypto
       --user={{ matrix_user_uid }}:{{ matrix_user_gid }}
       --cap-drop=ALL
-      --mount type=bind,src={{ matrix_hookshot_base_path }}/config.yml,dst=/config.yml
+      --mount type=bind,src={{ matrix_hookshot_base_path }},dst=/data
       {{ matrix_hookshot_docker_image }}
-      yarn start:resetcrypto
+      node --require source-map-support/register /usr/bin/matrix-hookshot/App/ResetCryptoStore.js
   changed_when: true
+
+- name: Ensure matrix-hookshot is started, if it previously was
+  ansible.builtin.service:
+    name: matrix-hookshot
+    state: started
+    enabled: true
+    daemon_reload: true
+  when: matrix_hookshot_stopped.changed | bool
diff --git a/roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml b/roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml
index 33871b77b..de961c186 100644
--- a/roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml
+++ b/roles/custom/matrix-bridge-hookshot/tasks/validate_config.yml
@@ -31,6 +31,7 @@
     - {'old': 'matrix_hookshot_ident', 'new': 'matrix_hookshot_identifier'}
     - {'old': 'matrix_hookshot_queue_host', 'new': 'matrix_hookshot_cache_redis_host'}
     - {'old': 'matrix_hookshot_queue_port', 'new': 'matrix_hookshot_cache_redis_port'}
+    - {'old': 'matrix_hookshot_experimental_encryption_enabled', 'new': 'matrix_hookshot_encryption_enabled'}
 
 - name: Fail if required Hookshot settings not defined
   ansible.builtin.fail:
@@ -96,7 +97,7 @@
   ansible.builtin.fail:
     msg: >-
       You need to define a required configuration setting (`matrix_hookshot_cache_redis*`) to enable Hookshot encryption.
-  when: "matrix_hookshot_experimental_encryption_enabled and matrix_hookshot_cache_redisUri == ''"
+  when: "matrix_hookshot_encryption_enabled and matrix_hookshot_cache_redisUri == ''"
 
 - name: (Deprecation) Catch and report old metrics usage
   ansible.builtin.fail:
diff --git a/roles/custom/matrix-bridge-hookshot/templates/config.yml.j2 b/roles/custom/matrix-bridge-hookshot/templates/config.yml.j2
index 5f6ab67bf..c476f6b4b 100644
--- a/roles/custom/matrix-bridge-hookshot/templates/config.yml.j2
+++ b/roles/custom/matrix-bridge-hookshot/templates/config.yml.j2
@@ -113,8 +113,8 @@ metrics:
 cache:
   redisUri: {{ matrix_hookshot_cache_redisUri | to_json }}
 {% endif %}
-{% if matrix_hookshot_experimental_encryption_enabled %}
-experimentalEncryption:
+{% if matrix_hookshot_encryption_enabled %}
+encryption:
   storagePath: /data/encryption
 {% endif %}
 logging:
diff --git a/roles/custom/matrix-bridge-hookshot/templates/registration.yml.j2 b/roles/custom/matrix-bridge-hookshot/templates/registration.yml.j2
index 557bd85d6..2e617df76 100644
--- a/roles/custom/matrix-bridge-hookshot/templates/registration.yml.j2
+++ b/roles/custom/matrix-bridge-hookshot/templates/registration.yml.j2
@@ -25,11 +25,11 @@ namespaces:
     - regex: "#github_.+:{{ matrix_domain }}"
       exclusive: true
 
-sender_localpart: hookshot
+sender_localpart: {{ matrix_hookshot_bot_localpart | to_json }}
 url: "http://{{ matrix_hookshot_container_url }}:{{ matrix_hookshot_appservice_port }}" # This should match the bridge.port in your config file
 rate_limited: false
 
-{% if matrix_hookshot_experimental_encryption_enabled %}
+{% if matrix_hookshot_encryption_enabled %}
 de.sorunome.msc2409.push_ephemeral: true
 push_ephemeral: true
 org.matrix.msc3202: true
diff --git a/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml
index 6e691c163..779816b68 100644
--- a/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml
+++ b/roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml
@@ -4,12 +4,16 @@
 
 matrix_mautrix_discord_enabled: true
 
+matrix_mautrix_discord_hostname: ""
+matrix_mautrix_discord_path_prefix: /
+matrix_mautrix_discord_scheme: https
+
 matrix_mautrix_discord_container_image_self_build: false
 matrix_mautrix_discord_container_image_self_build_repo: "https://mau.dev/mautrix/discord.git"
 matrix_mautrix_discord_container_image_self_build_branch: "{{ 'main' if matrix_mautrix_discord_version == 'latest' else matrix_mautrix_discord_version }}"
 
 # renovate: datasource=docker depName=dock.mau.dev/mautrix/discord
-matrix_mautrix_discord_version: v0.7.0
+matrix_mautrix_discord_version: v0.7.2
 
 # See: https://mau.dev/mautrix/discord/container_registry
 matrix_mautrix_discord_docker_image: "{{ matrix_mautrix_discord_docker_image_name_prefix }}mautrix/discord:{{ matrix_mautrix_discord_version }}"
@@ -22,11 +26,31 @@ matrix_mautrix_discord_data_path: "{{ matrix_mautrix_discord_base_path }}/data"
 matrix_mautrix_discord_docker_src_files_path: "{{ matrix_mautrix_discord_base_path }}/docker-src"
 
 matrix_mautrix_discord_homeserver_address: ""
-matrix_mautrix_discord_homeserver_public_address: ''
 matrix_mautrix_discord_homeserver_domain: "{{ matrix_domain }}"
 matrix_mautrix_discord_appservice_address: "http://matrix-mautrix-discord:8080"
 
-matrix_mautrix_discord_command_prefix: "!discord"
+matrix_mautrix_discord_bridge_command_prefix: "!discord"
+
+# Publicly accessible base URL that Discord can use to reach the bridge, used for avatars in relay mode.
+# If not set, avatars will not be bridged. Only the /mautrix-discord/avatar/{server}/{id}/{hash} endpoint is used on this address.
+# This should not have a trailing slash, the endpoint above will be appended to the provided address.
+matrix_mautrix_discord_bridge_public_address: "{{ (matrix_mautrix_discord_scheme + '://' + matrix_mautrix_discord_hostname + (matrix_mautrix_discord_path_prefix if matrix_mautrix_discord_path_prefix != '/' else '')) if matrix_mautrix_discord_hostname else '' }}"
+
+# A random key used to sign the avatar URLs. The bridge will only accept requests with a valid signature.
+matrix_mautrix_discord_bridge_avatar_proxy_key: ''
+
+# Localpart template of MXIDs for Discord users.
+# {{ '{{.}}' }} is replaced with the internal ID of the Discord user.
+matrix_mautrix_discord_bridge_username_template: "{% raw %}discord_{{.}}{% endraw %}"
+
+# Displayname template for Discord users. This is also used as the room name in DMs if private_chat_portal_meta is enabled.
+matrix_mautrix_discord_bridge_displayname_template: "{% raw %}{{or .GlobalName .Username}}{{if .Bot}} (bot){{end}}{% endraw %}"
+
+# Displayname template for Discord channels (bridged as rooms, or spaces when type=4).
+matrix_mautrix_discord_bridge_channel_name_template: "{% raw %}{{if or (eq .Type 3) (eq .Type 4)}}{{.Name}}{{else}}#{{.Name}}{{end}}{% endraw %}"
+
+# Displayname template for Discord guilds (bridged as spaces).
+matrix_mautrix_discord_bridge_guild_name_template: "{% raw %}{{.Name}}{% endraw %}"
 
 matrix_mautrix_discord_bridge_permissions: |
   {{
@@ -40,6 +64,38 @@ matrix_mautrix_discord_container_additional_networks: "{{ matrix_mautrix_discord
 matrix_mautrix_discord_container_additional_networks_auto: []
 matrix_mautrix_discord_container_additional_networks_custom: []
 
+# matrix_mautrix_discord_container_labels_traefik_enabled controls whether labels to assist a Traefik reverse-proxy will be attached to the container.
+# See `../templates/labels.j2` for details.
+#
+# To inject your own other container labels, see `matrix_mautrix_discord_container_labels_additional_labels`.
+matrix_mautrix_discord_container_labels_traefik_enabled: true
+matrix_mautrix_discord_container_labels_traefik_docker_network: "{{ matrix_mautrix_discord_container_network }}"
+matrix_mautrix_discord_container_labels_traefik_hostname: "{{ matrix_mautrix_discord_hostname }}"
+# The path prefix must either be `/` or not end with a slash (e.g. `/matrix-alertmanager-receiver`).
+matrix_mautrix_discord_container_labels_traefik_path_prefix: "{{ matrix_mautrix_discord_path_prefix }}"
+matrix_mautrix_discord_container_labels_traefik_entrypoints: web-secure
+matrix_mautrix_discord_container_labels_traefik_tls_certResolver: default  # noqa var-naming
+
+# Controls whether labels will be added that expose the bridge's avatar proxy (`/mautrix-discord/avatar/{server}/{id}/{hash}`).
+# See: matrix_mautrix_discord_bridge_public_address
+matrix_mautrix_discord_container_labels_avatar_proxy_enabled: "{{ matrix_mautrix_discord_bridge_public_address != '' }}"
+matrix_mautrix_discord_container_labels_avatar_proxy_hostname: "{{ matrix_mautrix_discord_container_labels_traefik_hostname }}"
+matrix_mautrix_discord_container_labels_avatar_proxy_path_prefix: "{{ matrix_mautrix_discord_container_labels_traefik_path_prefix if matrix_mautrix_discord_container_labels_traefik_path_prefix == '/' else (matrix_mautrix_discord_container_labels_traefik_path_prefix + '/') }}mautrix-discord/avatar"
+matrix_mautrix_discord_container_labels_avatar_proxy_traefik_rule: "Host(`{{ matrix_mautrix_discord_container_labels_traefik_hostname }}`) && PathPrefix(`{{ matrix_mautrix_discord_container_labels_avatar_proxy_path_prefix }}`)"
+matrix_mautrix_discord_container_labels_avatar_proxy_traefik_priority: 0
+matrix_mautrix_discord_container_labels_avatar_proxy_traefik_entrypoints: "{{ matrix_mautrix_discord_container_labels_traefik_entrypoints }}"
+matrix_mautrix_discord_container_labels_avatar_proxy_traefik_tls: "{{ matrix_mautrix_discord_container_labels_avatar_proxy_traefik_entrypoints != 'web' }}"
+matrix_mautrix_discord_container_labels_avatar_proxy_traefik_tls_certResolver: "{{ matrix_mautrix_discord_container_labels_traefik_tls_certResolver }}"  # noqa var-naming
+
+# matrix_mautrix_discord_container_labels_additional_labels contains a multiline string with additional labels to add to the container label file.
+# See `../templates/labels.j2` for details.
+#
+# Example:
+# matrix_mautrix_discord_container_labels_additional_labels: |
+#   my.label=1
+#   another.label="here"
+matrix_mautrix_discord_container_labels_additional_labels: ''
+
 # A list of extra arguments to pass to the container
 matrix_mautrix_discord_container_extra_arguments: []
 
@@ -56,9 +112,13 @@ matrix_mautrix_discord_appservice_token: ''
 matrix_mautrix_discord_homeserver_token: ''
 
 matrix_mautrix_discord_appservice_bot_username: discordbot
+matrix_mautrix_discord_appservice_bot_displayname: Discord bridge bot
+matrix_mautrix_discord_appservice_bot_avatar: mxc://maunium.net/nIdEykemnwdisvHbpxflpDlC
+
+matrix_mautrix_discord_provisioning_shared_secret: disable
 
 # Minimum severity of journal log messages.
-# Options: debug, info, warn, error, fatal
+# Options: trace, debug, info, warn, error, fatal
 matrix_mautrix_discord_logging_level: 'warn'
 
 # Whether or not created rooms should have federation enabled.
@@ -104,9 +164,18 @@ matrix_mautrix_discord_bridge_login_shared_secret_map: "{{ matrix_mautrix_discor
 matrix_mautrix_discord_bridge_login_shared_secret_map_auto: {}
 matrix_mautrix_discord_bridge_login_shared_secret_map_custom: {}
 
+
 # Servers to always allow double puppeting from
-matrix_mautrix_discord_bridge_double_puppet_server_map:
-  "{{ matrix_mautrix_discord_homeserver_domain :  matrix_mautrix_discord_homeserver_address }}"
+matrix_mautrix_discord_bridge_double_puppet_server_map: "{{ matrix_mautrix_discord_bridge_double_puppet_server_map_default | combine(matrix_mautrix_discord_bridge_double_puppet_server_map_auto) | combine(matrix_mautrix_discord_bridge_double_puppet_server_map_custom) }}"
+matrix_mautrix_discord_bridge_double_puppet_server_map_default: |-
+  {{
+    {}
+    | combine({
+      matrix_beeper_linkedin_homeserver_domain: matrix_beeper_linkedin_homeserver_address
+    })
+  }}
+matrix_mautrix_discord_bridge_double_puppet_server_map_auto: {}
+matrix_mautrix_discord_bridge_double_puppet_server_map_custom: {}
 
 # Default mautrix-discord configuration template which covers the generic use case.
 # You can customize it by controlling the various variables inside it.
@@ -151,6 +220,9 @@ matrix_mautrix_discord_registration: "{{ matrix_mautrix_discord_registration_yam
 # Enable End-to-bridge encryption
 matrix_mautrix_discord_bridge_encryption_allow: "{{ matrix_bridges_encryption_enabled }}"
 matrix_mautrix_discord_bridge_encryption_default: "{{ matrix_bridges_encryption_default }}"
+matrix_mautrix_discord_bridge_encryption_require: false
+matrix_mautrix_discord_bridge_encryption_appservice: false
+matrix_mautrix_discord_bridge_encryption_plaintext_mentions: false
 matrix_mautrix_discord_bridge_encryption_key_sharing_allow: "{{ matrix_mautrix_discord_bridge_encryption_allow }}"
 
 # On Conduit versions before 0.5.0 this option prevented users from joining spaces created by the bridge.
diff --git a/roles/custom/matrix-bridge-mautrix-discord/tasks/setup_install.yml b/roles/custom/matrix-bridge-mautrix-discord/tasks/setup_install.yml
index 4775b5fee..a83092973 100644
--- a/roles/custom/matrix-bridge-mautrix-discord/tasks/setup_install.yml
+++ b/roles/custom/matrix-bridge-mautrix-discord/tasks/setup_install.yml
@@ -93,6 +93,16 @@
     owner: "{{ matrix_user_username }}"
     group: "{{ matrix_user_groupname }}"
 
+- name: Ensure mautrix-discord support files installed
+  ansible.builtin.template:
+    src: "{{ role_path }}/templates/{{ item }}.j2"
+    dest: "{{ matrix_mautrix_discord_base_path }}/{{ item }}"
+    mode: 0640
+    owner: "{{ matrix_user_username }}"
+    group: "{{ matrix_user_groupname }}"
+  with_items:
+    - labels
+
 - name: Ensure mautrix-discord container network is created
   community.general.docker_network:
     enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}"
diff --git a/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml
index 96cffd4a7..25b4773c9 100644
--- a/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml
+++ b/roles/custom/matrix-bridge-mautrix-discord/tasks/validate_config.yml
@@ -9,9 +9,11 @@
     - {'name': 'matrix_mautrix_discord_appservice_token', when: true}
     - {'name': 'matrix_mautrix_discord_homeserver_address', when: true}
     - {'name': 'matrix_mautrix_discord_homeserver_token', when: true}
-    - {'name': 'matrix_mautrix_discord_homeserver_public_address', when: true}
+    - {'name': 'matrix_mautrix_discord_bridge_public_address', when: true}
     - {'name': 'matrix_mautrix_discord_container_network', when: true}
     - {'name': 'matrix_mautrix_discord_database_hostname', when: "{{ matrix_mautrix_discord_database_engine == 'postgres' }}"}
+    - {'name': 'matrix_mautrix_discord_container_labels_avatar_proxy_hostname', when: "{{ matrix_mautrix_discord_container_labels_avatar_proxy_enabled }}"}
+    - {'name': 'matrix_mautrix_discord_container_labels_avatar_proxy_path_prefix', when: "{{ matrix_mautrix_discord_container_labels_avatar_proxy_enabled }}"}
 
 - name: (Deprecation) Catch and report renamed settings
   ansible.builtin.fail:
@@ -21,3 +23,5 @@
   when: "item.old in vars"
   with_items:
     - {'old': 'matrix_mautrix_discord_login_shared_secret', 'new': '<removed>'}
+    - {'old': 'matrix_mautrix_discord_homeserver_public_address', 'new': 'matrix_mautrix_discord_bridge_public_address'}
+    - {'old': 'matrix_mautrix_discord_command_prefix', 'new': 'matrix_mautrix_discord_bridge_command_prefix'}
diff --git a/roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2
index 56c3bcfb8..c859c1149 100644
--- a/roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-mautrix-discord/templates/config.yaml.j2
@@ -3,13 +3,12 @@
 homeserver:
     # The address that this appservice can use to connect to the homeserver.
     address: {{ matrix_mautrix_discord_homeserver_address | to_json }}
-    # Publicly accessible base URL for media, used for avatars in relay mode.
-    # If not set, the connection address above will be used.
-    public_address: {{ matrix_mautrix_discord_homeserver_public_address | to_json }}
-    # The domain of the homeserver (for MXIDs, etc).
+    # The domain of the homeserver (also known as server_name, used for MXIDs, etc).
     domain: {{ matrix_mautrix_discord_homeserver_domain | to_json }}
-    # Is the homeserver actually mautrix-asmux?
-    asmux: false
+
+    # What software is the homeserver running?
+    # Standard Matrix homeservers like Synapse, Dendrite and Conduit should just use "standard" here.
+    software: standard
     # The URL to push real-time bridge status to.
     # If set, the bridge will make POST requests to this URL whenever a user's discord connection state changes.
     # The bridge will use the appservice as_token to authorize requests.
@@ -19,6 +18,13 @@ homeserver:
     # Does the homeserver support https://github.com/matrix-org/matrix-spec-proposals/pull/2246?
     async_media: false
 
+    # Should the bridge use a websocket for connecting to the homeserver?
+    # The server side is currently not documented anywhere and is only implemented by mautrix-wsproxy,
+    # mautrix-asmux (deprecated), and hungryserv (proprietary).
+    websocket: false
+    # How often should the websocket be pinged? Pinging will be disabled if this is zero.
+    ping_interval_seconds: 0
+
 # Application service host/registration related details.
 # Changing these values requires regeneration of the registration.
 appservice:
@@ -31,13 +37,14 @@ appservice:
 
     # Database config.
     database:
-        # The database type. "sqlite3" and "postgres" are supported.
-        type: {{ matrix_mautrix_discord_appservice_database_type|to_json }}
+        # The database type. "sqlite3-fk-wal" and "postgres" are supported.
+        type: {{ matrix_mautrix_discord_appservice_database_type | to_json }}
         # The database URI.
-        #   SQLite: File name is enough. https://github.com/mattn/go-sqlite3#connection-string
+        #   SQLite: A raw file path is supported, but `file:<path>?_txlock=immediate` is recommended.
+        #           https://github.com/mattn/go-sqlite3#connection-string
         #   Postgres: Connection string. For example, postgres://user:password@host/database?sslmode=disable
         #             To connect via Unix socket, use something like postgres:///dbname?host=/var/run/postgresql
-        uri: {{ matrix_mautrix_discord_appservice_database_uri|to_json }}
+        uri: {{ matrix_mautrix_discord_appservice_database_uri | to_json }}
         # Maximum number of connections. Mostly relevant for Postgres.
         max_open_conns: 20
         max_idle_conns: 2
@@ -51,15 +58,21 @@ appservice:
     # Appservice bot details.
     bot:
         # Username of the appservice bot.
-        username: {{ matrix_mautrix_discord_appservice_bot_username|to_json }}
+        username: {{ matrix_mautrix_discord_appservice_bot_username | to_json }}
         # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty
         # to leave display name/avatar as-is.
-        displayname: Discord bridge bot
-        avatar: mxc://maunium.net/nIdEykemnwdisvHbpxflpDlC
+        displayname: {{ matrix_mautrix_discord_appservice_bot_displayname | to_json }}
+        avatar: {{ matrix_mautrix_discord_appservice_bot_avatar | to_json }}
+
     # Whether or not to receive ephemeral events via appservice transactions.
     # Requires MSC2409 support (i.e. Synapse 1.22+).
     ephemeral_events: true
 
+    # Should incoming events be handled asynchronously?
+    # This may be necessary for large public instances with lots of messages going through.
+    # However, messages will not be guaranteed to be bridged in the same order they were sent in.
+    async_transactions: false
+
     # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify.
     as_token: {{ matrix_mautrix_discord_appservice_token | to_json }}
     hs_token: {{ matrix_mautrix_discord_homeserver_token | to_json }}
@@ -67,51 +80,67 @@ appservice:
 # Bridge config
 bridge:
     # Localpart template of MXIDs for Discord users.
-    # {{ '{{.}}' }} is replaced with the internal ID of the Discord user.
-    username_template: "{{ 'discord_{{.}}' }}"
+    # {% raw %}{{.}}{% endraw %} is replaced with the internal ID of the Discord user.
+    username_template: {{ matrix_mautrix_discord_bridge_username_template | to_json }}
     # Displayname template for Discord users. This is also used as the room name in DMs if private_chat_portal_meta is enabled.
     # Available variables:
-    #  {{ '{{.ID}}' }} - Internal user ID
-    #  {{ '{{.Username}}' }} - Legacy display/username on Discord
-    #  {{ '{{.GlobalName}}' }} - New displayname on Discord
-    #  {{ '{{.Discriminator}}' }} - The 4 numbers after the name on Discord
-    #  {{ '{{.Bot}}' }} - Whether the user is a bot
-    #  {{ '{{.System}}' }} - Whether the user is an official system user
-    #  {{ '{{.Webhook}}' }} - Whether the user is a webhook and is not an application
-    #  {{ '{{.Application}}' }} - Whether the user is an application
-    displayname_template: "{{ '{{or .GlobalName .Username}}{{if .Bot}} (bot){{end}}' }}"
+    #   .ID - Internal user ID
+    #   .Username - Legacy display/username on Discord
+    #   .GlobalName - New displayname on Discord
+    #   .Discriminator - The 4 numbers after the name on Discord
+    #   .Bot - Whether the user is a bot
+    #   .System - Whether the user is an official system user
+    #   .Webhook - Whether the user is a webhook and is not an application
+    #   .Application - Whether the user is an application
+    displayname_template: {{ matrix_mautrix_discord_bridge_displayname_template | to_json }}
     # Displayname template for Discord channels (bridged as rooms, or spaces when type=4).
     # Available variables:
-    #  {{ '{{.Name}}' }} - Channel name, or user displayname (pre-formatted with displayname_template) in DMs.
-    #  {{ '{{.ParentName}}' }} - Parent channel name (used for categories).
-    #  {{ '{{.GuildName}}' }} - Guild name.
-    #  {{ '{{.NSFW}}' }} - Whether the channel is marked as NSFW.
-    #  {{ '{{.Type}}' }} - Channel type (see values at https://github.com/bwmarrin/discordgo/blob/v0.25.0/structs.go#L251-L267)
-    channel_name_template: "{{ '{{if or (eq .Type 3) (eq .Type 4)}}{{.Name}}{{else}}#{{.Name}}{{end}}' }}"
+    #   .Name - Channel name, or user displayname (pre-formatted with displayname_template) in DMs.
+    #   .ParentName - Parent channel name (used for categories).
+    #   .GuildName - Guild name.
+    #   .NSFW - Whether the channel is marked as NSFW.
+    #   .Type - Channel type (see values at https://github.com/bwmarrin/discordgo/blob/v0.25.0/structs.go#L251-L267)
+    channel_name_template: {{ matrix_mautrix_discord_bridge_channel_name_template | to_json }}
     # Displayname template for Discord guilds (bridged as spaces).
     # Available variables:
-    #  {{ '{{.Name}}' }} - Guild name
-    guild_name_template: "{{ '{{.Name}}' }}"
-    # Should the bridge explicitly set the avatar and room name for DM portal rooms?
-    # This is implicitly enabled in encrypted rooms.
+    #   .Name - Guild name
+    guild_name_template: {{ matrix_mautrix_discord_bridge_guild_name_template | to_json }}
     # Whether to explicitly set the avatar and room name for private chat portal rooms.
     # If set to `default`, this will be enabled in encrypted rooms and disabled in unencrypted rooms.
     # If set to `always`, all DM rooms will have explicit names and avatars set.
     # If set to `never`, DM rooms will never have names and avatars set.
     private_chat_portal_meta: default
+
+    # Publicly accessible base URL that Discord can use to reach the bridge, used for avatars in relay mode.
+    # If not set, avatars will not be bridged. Only the /mautrix-discord/avatar/{server}/{id}/{hash} endpoint is used on this address.
+    # This should not have a trailing slash, the endpoint above will be appended to the provided address.
+    public_address: {{ matrix_mautrix_discord_bridge_public_address | to_json }}
+    # A random key used to sign the avatar URLs. The bridge will only accept requests with a valid signature.
+    avatar_proxy_key: {{ matrix_mautrix_discord_bridge_avatar_proxy_key | to_json }}
+
     portal_message_buffer: 128
+
     # Number of private channel portals to create on bridge startup.
     # Other portals will be created when receiving messages.
     startup_private_channel_create_limit: 5
     # Should the bridge send a read receipt from the bridge bot when a message has been sent to Discord?
     delivery_receipts: false
     # Whether the bridge should send the message status as a custom com.beeper.message_send_status event.
-    message_status_events: true
+    message_status_events: false
     # Whether the bridge should send error notices via m.notice events when a message fails to bridge.
     message_error_notices: true
     # Should the bridge use space-restricted join rules instead of invite-only for guild rooms?
     # This can avoid unnecessary invite events in guild rooms when members are synced in.
-    restricted_rooms: {{ matrix_mautrix_discord_bridge_restricted_rooms|to_json }}
+    restricted_rooms: {{ matrix_mautrix_discord_bridge_restricted_rooms | to_json }}
+    # Should the bridge automatically join the user to threads on Discord when the thread is opened on Matrix?
+    # This only works with clients that support thread read receipts (MSC3771 added in Matrix v1.4).
+    autojoin_thread_on_open: true
+    # Should inline fields in Discord embeds be bridged as HTML tables to Matrix?
+    # Tables aren't supported in all clients, but are the only way to emulate the Discord inline field UI.
+    embed_fields_as_tables: true
+    # Should guild channels be muted when the portal is created? This only meant for single-user instances,
+    # it won't mute it for all users if there are multiple Matrix users in the same Discord guild.
+    mute_channels_on_create: false
     # Should the bridge update the m.direct account data event when double puppeting is enabled.
     # Note that updating the m.direct event is not atomic (except with mautrix-asmux)
     # and is therefore prone to race conditions.
@@ -120,7 +149,7 @@ bridge:
     # This field will automatically be changed back to false after it, except if the config file is not writable.
     resend_bridge_info: false
     # Should incoming custom emoji reactions be bridged as mxc:// URIs?
-    # If set to false, custom emoji reactions will be bridged as the shortcode instead, and the image wont be available.
+    # If set to false, custom emoji reactions will be bridged as the shortcode instead, and the image won't be available.
     custom_emoji_reactions: true
     # Should the bridge attempt to completely delete portal rooms when a channel is deleted on Discord?
     # If true, the bridge will try to kick Matrix users from the room. Otherwise, the bridge only makes ghosts leave.
@@ -130,7 +159,7 @@ bridge:
     delete_guild_on_leave: true
     # Whether or not created rooms should have federation enabled.
     # If false, created portal rooms will never be federated.
-    federate_rooms: {{ matrix_mautrix_discord_federate_rooms|to_json }}
+    federate_rooms: {{ matrix_mautrix_discord_federate_rooms | to_json }}
     # Prefix messages from webhooks with the profile info? This can be used along with a custom displayname_template
     # to better handle webhooks that change their name all the time (like ones used by bridges).
     prefix_webhook_messages: false
@@ -140,24 +169,29 @@ bridge:
     # like the official client does? The other option is sending the media in the message send request as a form part
     # (which is always used by bots and webhooks).
     use_discord_cdn_upload: true
+    # Proxy for Discord connections
+    proxy:
     # Should mxc uris copied from Discord be cached?
     # This can be `never` to never cache, `unencrypted` to only cache unencrypted mxc uris, or `always` to cache everything.
     # If you have a media repo that generates non-unique mxc uris, you should set this to never.
     cache_media: unencrypted
-    # Patterns for converting Discord media to custom mxc:// URIs instead of reuploading.
-    # Each of the patterns can be set to null to disable custom URIs for that type of media.
+    # Settings for converting Discord media to custom mxc:// URIs instead of reuploading.
     # More details can be found at https://docs.mau.fi/bridges/go/discord/direct-media.html
-    media_patterns:
+    direct_media:
         # Should custom mxc:// URIs be used instead of reuploading media?
         enabled: false
-        # Pattern for normal message attachments.
-        attachments: {% raw %}mxc://discord-media.mau.dev/attachments|{{.ChannelID}}|{{.AttachmentID}}|{{.FileName}}{% endraw %}
-        # Pattern for custom emojis.
-        emojis: {% raw %}mxc://discord-media.mau.dev/emojis|{{.ID}}.{{.Ext}}{% endraw %}
-        # Pattern for stickers. Note that animated lottie stickers will not be converted if this is enabled.
-        stickers: {% raw %}mxc://discord-media.mau.dev/stickers|{{.ID}}.{{.Ext}}{% endraw %}
-        # Pattern for static user avatars.
-        avatars: {% raw %}mxc://discord-media.mau.dev/avatars|{{.UserID}}|{{.AvatarID}}.{{.Ext}}{% endraw %}
+        # The server name to use for the custom mxc:// URIs.
+        # This server name will effectively be a real Matrix server, it just won't implement anything other than media.
+        # You must either set up .well-known delegation from this domain to the bridge, or proxy the domain directly to the bridge.
+        server_name: discord-media.example.com
+        # Optionally a custom .well-known response. This defaults to `server_name:443`
+        well_known_response:
+        # The bridge supports MSC3860 media download redirects and will use them if the requester supports it.
+        # Optionally, you can force redirects and not allow proxying at all by setting this to false.
+        allow_proxy: true
+        # Matrix server signing key to make the federation tester pass, same format as synapse's .signing.key file.
+        # This key is also used to sign the mxc:// URIs to ensure only the bridge can generate them.
+        server_key: ""
     # Settings for converting animated stickers.
     animated_sticker:
         # Format to which animated stickers should be converted.
@@ -173,8 +207,7 @@ bridge:
             height: 320
             fps: 25 # only for webm, webp and gif (2, 5, 10, 20 or 25 recommended)
     # Servers to always allow double puppeting from
-    double_puppet_server_map:
-        "{{ matrix_mautrix_discord_homeserver_domain }}": {{ matrix_mautrix_discord_homeserver_address }}
+    double_puppet_server_map: {{ matrix_mautrix_discord_bridge_double_puppet_server_map | to_json }}
     # Allow using double puppeting from any server with a valid client .well-known file.
     double_puppet_allow_discovery: false
     # Shared secrets for https://github.com/devture/matrix-synapse-shared-secret-auth
@@ -182,11 +215,10 @@ bridge:
     # If set, double puppeting will be enabled automatically for local users
     # instead of users having to find an access token and run `login-matrix`
     # manually.
-    login_shared_secret_map: {{ matrix_mautrix_discord_bridge_login_shared_secret_map|to_json }}
+    login_shared_secret_map: {{ matrix_mautrix_discord_bridge_login_shared_secret_map | to_json }}
 
     # The prefix for commands. Only required in non-management rooms.
-    command_prefix: "{{ matrix_mautrix_discord_command_prefix }}"
-
+    command_prefix: {{ matrix_mautrix_discord_bridge_command_prefix | to_json }}
     # Messages sent upon joining a management room.
     # Markdown is supported. The defaults are listed below.
     management_room_text:
@@ -228,15 +260,40 @@ bridge:
     # See https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html for more info.
     encryption:
         # Allow encryption, work in group chat rooms with e2ee enabled
-        allow: {{ matrix_mautrix_discord_bridge_encryption_allow|to_json }}
+        allow: {{ matrix_mautrix_discord_bridge_encryption_allow | to_json }}
         # Default to encryption, force-enable encryption in all portals the bridge creates
         # This will cause the bridge bot to be in private chats for the encryption to work properly.
-        default: {{ matrix_mautrix_discord_bridge_encryption_default|to_json }}
+        default: {{ matrix_mautrix_discord_bridge_encryption_default | to_json }}
+        # Whether to use MSC2409/MSC3202 instead of /sync long polling for receiving encryption-related data.
+        appservice: {{ matrix_mautrix_discord_bridge_encryption_appservice | to_json}}
         # Require encryption, drop any unencrypted messages.
-        require: false
+        require: {{ matrix_mautrix_discord_bridge_encryption_require | to_json }}
         # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
         # You must use a client that supports requesting keys from other users to use this feature.
-        allow_key_sharing: {{ matrix_mautrix_discord_bridge_encryption_key_sharing_allow|to_json }}
+        allow_key_sharing: {{ matrix_mautrix_discord_bridge_encryption_key_sharing_allow | to_json }}
+        # Should users mentions be in the event wire content to enable the server to send push notifications?
+        plaintext_mentions: {{ matrix_mautrix_discord_bridge_encryption_plaintext_mentions | to_json }}
+        # Options for deleting megolm sessions from the bridge.
+        delete_keys:
+            # Beeper-specific: delete outbound sessions when hungryserv confirms
+            # that the user has uploaded the key to key backup.
+            delete_outbound_on_ack: false
+            # Don't store outbound sessions in the inbound table.
+            dont_store_outbound: false
+            # Ratchet megolm sessions forward after decrypting messages.
+            ratchet_on_decrypt: false
+            # Delete fully used keys (index >= max_messages) after decrypting messages.
+            delete_fully_used_on_decrypt: false
+            # Delete previous megolm sessions from same device when receiving a new one.
+            delete_prev_on_new_session: false
+            # Delete megolm sessions received from a device when the device is deleted.
+            delete_on_device_delete: false
+            # Periodically delete megolm sessions when 2x max_age has passed since receiving the session.
+            periodically_delete_expired: false
+            # Delete inbound megolm sessions that don't have the received_at field used for
+            # automatic ratcheting and expired session deletion. This is meant as a migration
+            # to delete old keys prior to the bridge update.
+            delete_outdated_inbound: false
         # What level of device verification should be required from users?
         #
         # Valid levels:
@@ -272,13 +329,19 @@ bridge:
             # default.
             messages: 100
 
+            # Disable rotating keys when a user's devices change?
+            # You should not enable this option unless you understand all the implications.
+            disable_device_change_key_rotation: false
+
     # Settings for provisioning API
     provisioning:
         # Prefix for the provisioning API paths.
         prefix: /_matrix/provision
         # Shared secret for authentication. If set to "generate", a random secret will be generated,
         # or if set to "disable", the provisioning API will be disabled.
-        shared_secret: generate
+        shared_secret: {{ matrix_mautrix_discord_provisioning_shared_secret | to_json }}
+        # Enable debug API at /debug with provisioning authentication.
+        debug_endpoints: false
 
     # Permissions for using the bridge.
     # Permitted values:
@@ -291,12 +354,9 @@ bridge:
     #     mxid - Specific user
     permissions: {{ matrix_mautrix_discord_bridge_permissions|to_json }}
 
+# Logging config. See https://github.com/tulir/zeroconfig for details.
 logging:
-    directory: ./logs
-    file_name_format: ''
-    file_date_format: "2006-01-02"
-    file_mode: 384
-    timestamp_format: Jan _2, 2006 15:04:05
-    print_level: {{ matrix_mautrix_discord_logging_level | to_json }}
-    print_json: false
-    file_json: false
+    min_level: {{ matrix_mautrix_discord_logging_level | to_json }}
+    writers:
+    - type: stdout
+      format: pretty-colored
diff --git a/roles/custom/matrix-bridge-mautrix-discord/templates/labels.j2 b/roles/custom/matrix-bridge-mautrix-discord/templates/labels.j2
new file mode 100644
index 000000000..adc265db2
--- /dev/null
+++ b/roles/custom/matrix-bridge-mautrix-discord/templates/labels.j2
@@ -0,0 +1,58 @@
+{% if matrix_mautrix_discord_container_labels_traefik_enabled %}
+traefik.enable=true
+
+{% if matrix_mautrix_discord_container_labels_traefik_docker_network %}
+traefik.docker.network={{ matrix_mautrix_discord_container_labels_traefik_docker_network }}
+{% endif %}
+
+traefik.http.services.matrix-mautrix-discord.loadbalancer.server.port=8080
+
+{% if matrix_mautrix_discord_container_labels_avatar_proxy_enabled %}
+############################################################
+#                                                          #
+# Avatar proxy                                             #
+#                                                          #
+############################################################
+
+{% set middlewares = [] %}
+
+{% if matrix_mautrix_discord_container_labels_traefik_path_prefix != '/' %}
+traefik.http.middlewares.matrix-mautrix-discord-slashless-redirect.redirectregex.regex=({{ matrix_mautrix_discord_container_labels_traefik_path_prefix | quote }})$
+traefik.http.middlewares.matrix-mautrix-discord-slashless-redirect.redirectregex.replacement=${1}/
+{% set middlewares = middlewares + ['matrix-mautrix-discord-slashless-redirect'] %}
+{% endif %}
+
+{% if matrix_mautrix_discord_container_labels_traefik_path_prefix != '/' %}
+traefik.http.middlewares.matrix-mautrix-discord-strip-prefix.stripprefix.prefixes={{ matrix_mautrix_discord_container_labels_traefik_path_prefix }}
+{% set middlewares = middlewares + ['matrix-mautrix-discord-strip-prefix'] %}
+{% endif %}
+
+traefik.http.routers.matrix-mautrix-discord-avatar-proxy.rule={{ matrix_mautrix_discord_container_labels_avatar_proxy_traefik_rule }}
+
+{% if matrix_mautrix_discord_container_labels_avatar_proxy_traefik_priority | int > 0 %}
+traefik.http.routers.matrix-mautrix-discord-avatar-proxy.priority={{ matrix_mautrix_discord_container_labels_avatar_proxy_traefik_priority }}
+{% endif %}
+
+{% if middlewares | length > 0 %}
+traefik.http.routers.matrix-mautrix-discord-avatar-proxy.middlewares={{ middlewares | join(',') }}
+{% endif %}
+
+traefik.http.routers.matrix-mautrix-discord-avatar-proxy.service=matrix-mautrix-discord
+traefik.http.routers.matrix-mautrix-discord-avatar-proxy.entrypoints={{ matrix_mautrix_discord_container_labels_avatar_proxy_traefik_entrypoints }}
+
+traefik.http.routers.matrix-mautrix-discord-avatar-proxy.tls={{ matrix_mautrix_discord_container_labels_avatar_proxy_traefik_tls | to_json }}
+{% if matrix_mautrix_discord_container_labels_avatar_proxy_traefik_tls %}
+traefik.http.routers.matrix-mautrix-discord-avatar-proxy.tls.certResolver={{ matrix_mautrix_discord_container_labels_avatar_proxy_traefik_tls_certResolver }}
+{% endif %}
+
+############################################################
+#                                                          #
+# /Avatar proxy                                            #
+#                                                          #
+############################################################
+{% endif %}
+
+
+{% endif %}
+
+{{ matrix_mautrix_discord_container_labels_additional_labels }}
diff --git a/roles/custom/matrix-bridge-mautrix-discord/templates/systemd/matrix-mautrix-discord.service.j2 b/roles/custom/matrix-bridge-mautrix-discord/templates/systemd/matrix-mautrix-discord.service.j2
index 0a5167baf..cd853e1a9 100644
--- a/roles/custom/matrix-bridge-mautrix-discord/templates/systemd/matrix-mautrix-discord.service.j2
+++ b/roles/custom/matrix-bridge-mautrix-discord/templates/systemd/matrix-mautrix-discord.service.j2
@@ -23,6 +23,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \
 			--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
 			--cap-drop=ALL \
 			--network={{ matrix_mautrix_discord_container_network }} \
+			--label-file={{ matrix_mautrix_discord_base_path }}/labels \
 			--mount type=bind,src={{ matrix_mautrix_discord_config_path }},dst=/config,ro \
 			--mount type=bind,src={{ matrix_mautrix_discord_data_path }},dst=/data \
 			--workdir=/data \
diff --git a/roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2
index 968cbe162..7280ec12d 100644
--- a/roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-mautrix-facebook/templates/config.yaml.j2
@@ -211,8 +211,8 @@ bridge:
         #
         # Available variables:
         #   $sender_displayname - The display name of the sender (e.g. Example User)
-        #   $sender_username    - The username (Matrix ID localpart) of the sender (e.g. exampleuser)
-        #   $sender_mxid        - The Matrix ID of the sender (e.g. @exampleuser:example.com)
+        #   $sender_username    - The username (Matrix ID localpart) of the sender (e.g. alice)
+        #   $sender_mxid        - The Matrix ID of the sender (e.g. @alice:example.com)
         #   $message            - The message content
         message_formats:
             m.text: '<b>$sender_displayname</b>: $message'
diff --git a/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml
index d541fa117..2cde7487f 100644
--- a/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml
+++ b/roles/custom/matrix-bridge-mautrix-gmessages/defaults/main.yml
@@ -9,7 +9,7 @@ matrix_mautrix_gmessages_container_image_self_build_repo: "https://github.com/ma
 matrix_mautrix_gmessages_container_image_self_build_branch: "{{ 'main' if matrix_mautrix_gmessages_version == 'latest' else matrix_mautrix_gmessages_version }}"
 
 # renovate: datasource=docker depName=dock.mau.dev/mautrix/gmessages
-matrix_mautrix_gmessages_version: v0.5.1
+matrix_mautrix_gmessages_version: v0.6.0
 
 # See: https://mau.dev/mautrix/gmessages/container_registry
 matrix_mautrix_gmessages_docker_image: "{{ matrix_mautrix_gmessages_docker_image_name_prefix }}mautrix/gmessages:{{ matrix_mautrix_gmessages_version }}"
@@ -86,7 +86,7 @@ matrix_mautrix_gmessages_homeserver_token: ''
 matrix_mautrix_gmessages_appservice_bot_username: gmessagesbot
 
 # Minimum severity of journal log messages.
-# Options: debug, info, warn, error, fatal
+# Options: trace, debug, info, warn, error, fatal
 matrix_mautrix_gmessages_logging_level: 'warn'
 
 # Whether or not created rooms should have federation enabled.
diff --git a/roles/custom/matrix-bridge-mautrix-hangouts/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-hangouts/tasks/validate_config.yml
index dbdf82ba8..0d992175e 100644
--- a/roles/custom/matrix-bridge-mautrix-hangouts/tasks/validate_config.yml
+++ b/roles/custom/matrix-bridge-mautrix-hangouts/tasks/validate_config.yml
@@ -1,5 +1,18 @@
 ---
 
+- ansible.builtin.fail:
+    msg: |-
+      The Google Hangouts service was discontinued on November 1st, 2022.
+      The mautrix-hangouts bridge (which you have enabled via the `matrix_mautrix_hangouts_enabled` variable) will be removed from the playbook soon (in February 2025).
+
+      We suggest that you uninstall this bridge by:
+      1. Tweaking your `vars.yml` file - setting `matrix_mautrix_hangouts_enabled` to `false` or better yet removing all `matrix_mautrix_hangouts_*` variables
+      2. Re-running the playbook with the `setup-all` (e.g. `just setup-all`) or `setup-mautrix-hangouts` tag (e.g. `just run-tags setup-mautrix-hangouts`), so that uninstallation tasks will run.
+
+      In the future, an error will be raised for any `matrix_mautrix_hangouts_*` variables that the playbook detects in your `vars.yml` configuration file.
+
+      Also see: https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3863
+
 - name: Fail if required mautrix-hangouts settings not defined
   ansible.builtin.fail:
     msg: >-
diff --git a/roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2
index e3d4be521..d200ebcd6 100644
--- a/roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-mautrix-instagram/templates/config.yaml.j2
@@ -204,8 +204,8 @@ bridge:
     #
     # Available variables:
     #   $sender_displayname - The display name of the sender (e.g. Example User)
-    #   $sender_username    - The username (Matrix ID localpart) of the sender (e.g. exampleuser)
-    #   $sender_mxid        - The Matrix ID of the sender (e.g. @exampleuser:example.com)
+    #   $sender_username    - The username (Matrix ID localpart) of the sender (e.g. alice)
+    #   $sender_mxid        - The Matrix ID of the sender (e.g. @alice:example.com)
     #   $message            - The message content
     #
     # Note that Instagram doesn't support captions for images, so images won't include any indication of being relayed.
diff --git a/roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml
index 327e8b0ab..848e86bde 100644
--- a/roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml
+++ b/roles/custom/matrix-bridge-mautrix-meta-instagram/defaults/main.yml
@@ -13,7 +13,7 @@ matrix_mautrix_meta_instagram_enabled: true
 matrix_mautrix_meta_instagram_identifier: matrix-mautrix-meta-instagram
 
 # renovate: datasource=docker depName=dock.mau.dev/mautrix/meta
-matrix_mautrix_meta_instagram_version: v0.4.1
+matrix_mautrix_meta_instagram_version: v0.4.3
 
 matrix_mautrix_meta_instagram_base_path: "{{ matrix_base_data_path }}/mautrix-meta-instagram"
 matrix_mautrix_meta_instagram_config_path: "{{ matrix_mautrix_meta_instagram_base_path }}/config"
@@ -156,6 +156,8 @@ matrix_mautrix_meta_instagram_meta_mode: instagram
 # When in `instagram` mode (see `matrix_mautrix_meta_instagram_meta_mode`), should the bridge connect to WhatsApp servers for encrypted chats?
 matrix_mautrix_meta_instagram_meta_ig_e2ee: false
 
+matrix_mautrix_meta_instagram_provisioning_shared_secret: disable
+
 # Whether or not metrics endpoint should be enabled.
 # Enabling them is usually enough for a local (in-container) Prometheus to consume them.
 # If metrics need to be consumed by another (external) Prometheus server, consider exposing them via `matrix_mautrix_meta_instagram_metrics_proxying_enabled`.
diff --git a/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/config.yaml.j2
index 465a861fb..e905b1771 100644
--- a/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-mautrix-meta-instagram/templates/config.yaml.j2
@@ -263,7 +263,7 @@ provisioning:
     prefix: /_matrix/provision
     # Shared secret for authentication. If set to "generate" or null, a random secret will be generated,
     # or if set to "disable", the provisioning API will be disabled.
-    shared_secret: disable
+    shared_secret: {{ matrix_mautrix_meta_instagram_provisioning_shared_secret | to_json }}
     # Whether to allow provisioning API requests to be authed using Matrix access tokens.
     # This follows the same rules as double puppeting to determine which server to contact to check the token,
     # which means that by default, it only works for users on the same server as the bridge.
diff --git a/roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml
index 9b561f2df..ca951a333 100644
--- a/roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml
+++ b/roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml
@@ -13,7 +13,7 @@ matrix_mautrix_meta_messenger_enabled: true
 matrix_mautrix_meta_messenger_identifier: matrix-mautrix-meta-messenger
 
 # renovate: datasource=docker depName=dock.mau.dev/mautrix/meta
-matrix_mautrix_meta_messenger_version: v0.4.1
+matrix_mautrix_meta_messenger_version: v0.4.3
 
 matrix_mautrix_meta_messenger_base_path: "{{ matrix_base_data_path }}/mautrix-meta-messenger"
 matrix_mautrix_meta_messenger_config_path: "{{ matrix_mautrix_meta_messenger_base_path }}/config"
@@ -156,6 +156,8 @@ matrix_mautrix_meta_messenger_meta_mode: messenger
 # When in `instagram` mode (see `matrix_mautrix_meta_messenger_meta_mode`), should the bridge connect to WhatsApp servers for encrypted chats?
 matrix_mautrix_meta_messenger_meta_ig_e2ee: false
 
+matrix_mautrix_meta_messenger_provisioning_shared_secret: disable
+
 # Whether or not metrics endpoint should be enabled.
 # Enabling them is usually enough for a local (in-container) Prometheus to consume them.
 # If metrics need to be consumed by another (external) Prometheus server, consider exposing them via `matrix_mautrix_meta_messenger_metrics_proxying_enabled`.
diff --git a/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2
index dbfc69b35..b5f9404b3 100644
--- a/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-mautrix-meta-messenger/templates/config.yaml.j2
@@ -263,7 +263,7 @@ provisioning:
     prefix: /_matrix/provision
     # Shared secret for authentication. If set to "generate" or null, a random secret will be generated,
     # or if set to "disable", the provisioning API will be disabled.
-    shared_secret: disable
+    shared_secret: {{ matrix_mautrix_meta_messenger_provisioning_shared_secret | to_json }}
     # Whether to allow provisioning API requests to be authed using Matrix access tokens.
     # This follows the same rules as double puppeting to determine which server to contact to check the token,
     # which means that by default, it only works for users on the same server as the bridge.
diff --git a/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml
index b6265598b..b1aecf902 100644
--- a/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml
+++ b/roles/custom/matrix-bridge-mautrix-signal/defaults/main.yml
@@ -9,7 +9,7 @@ matrix_mautrix_signal_container_image_self_build_repo: "https://mau.dev/mautrix/
 matrix_mautrix_signal_container_image_self_build_branch: "{{ 'main' if matrix_mautrix_signal_version == 'latest' else matrix_mautrix_signal_version }}"
 
 # renovate: datasource=docker depName=dock.mau.dev/mautrix/signal
-matrix_mautrix_signal_version: v0.7.2
+matrix_mautrix_signal_version: v0.7.5
 
 # See: https://mau.dev/mautrix/signal/container_registry
 matrix_mautrix_signal_docker_image: "{{ matrix_mautrix_signal_docker_image_name_prefix }}mautrix/signal:{{ matrix_mautrix_signal_docker_image_tag }}"
@@ -93,7 +93,7 @@ matrix_mautrix_signal_homeserver_token: ''
 matrix_mautrix_signal_appservice_bot_username: signalbot
 
 # Minimum severity of journal log messages.
-# Options: debug, info, warn, error, fatal
+# Options: trace, debug, info, warn, error, fatal
 matrix_mautrix_signal_logging_level: 'warn'
 
 # Whether or not created rooms should have federation enabled.
diff --git a/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml
index b4d55b2fc..9b95d069f 100644
--- a/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml
+++ b/roles/custom/matrix-bridge-mautrix-slack/defaults/main.yml
@@ -9,7 +9,7 @@ matrix_mautrix_slack_container_image_self_build_repo: "https://mau.dev/mautrix/s
 matrix_mautrix_slack_container_image_self_build_branch: "{{ 'main' if matrix_mautrix_slack_version == 'latest' else matrix_mautrix_slack_version }}"
 
 # renovate: datasource=docker depName=dock.mau.dev/mautrix/slack
-matrix_mautrix_slack_version: v0.1.2
+matrix_mautrix_slack_version: v0.1.4
 # See: https://mau.dev/mautrix/slack/container_registry
 matrix_mautrix_slack_docker_image: "{{ matrix_mautrix_slack_docker_image_name_prefix }}mautrix/slack:{{ matrix_mautrix_slack_version }}"
 matrix_mautrix_slack_docker_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_slack_container_image_self_build else 'dock.mau.dev/' }}"
@@ -62,7 +62,7 @@ matrix_mautrix_slack_backfill_unread_hours_threshold: 720
 matrix_mautrix_slack_backfill_threads_max_initial_messages: 50
 
 # Minimum severity of journal log messages.
-# Options: debug, info, warn, error, fatal
+# Options: trace, debug, info, warn, error, fatal
 matrix_mautrix_slack_logging_level: 'warn'
 
 # Database-related configuration fields.
diff --git a/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml
index 3c5989b44..619dfee86 100644
--- a/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml
+++ b/roles/custom/matrix-bridge-mautrix-telegram/defaults/main.yml
@@ -136,6 +136,8 @@ matrix_mautrix_telegram_systemd_wanted_services_list: []
 matrix_mautrix_telegram_appservice_token: ''
 matrix_mautrix_telegram_homeserver_token: ''
 
+matrix_mautrix_telegram_provisioning_shared_secret: disable
+
 # Whether or not metrics endpoint should be enabled.
 # Enabling them is usually enough for a local (in-container) Prometheus to consume them.
 # If metrics need to be consumed by another (external) Prometheus server, consider exposing them via `matrix_mautrix_telegram_metrics_proxying_enabled`.
diff --git a/roles/custom/matrix-bridge-mautrix-telegram/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-telegram/templates/config.yaml.j2
index 30145b0e0..6cbd30130 100644
--- a/roles/custom/matrix-bridge-mautrix-telegram/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-mautrix-telegram/templates/config.yaml.j2
@@ -71,7 +71,7 @@ appservice:
         prefix: /_matrix/provision/v1
         # The shared secret to authorize users of the API.
         # Set to "generate" to generate and save a new token.
-        shared_secret: generate
+        shared_secret: {{ matrix_mautrix_telegram_provisioning_shared_secret | to_json }}
 
     # The unique ID of this appservice.
     id: telegram
@@ -122,7 +122,7 @@ bridge:
     # Default: {displayname} (Telegram)
     displayname_template: {{ matrix_mautrix_telegram_displayname_template|to_json }}
 
-    # Set the preferred order of user identifiers which to use in the Matrix puppet display name.
+    # Set the preferred order of user IDs which to use in the Matrix puppet display name.
     # In the (hopefully unlikely) scenario that none of the given keys are found, the numeric user
     # ID is used.
     #
@@ -450,8 +450,8 @@ bridge:
     #
     # Available variables:
     #   $sender_displayname - The display name of the sender (e.g. Example User)
-    #   $sender_username    - The username (Matrix ID localpart) of the sender (e.g. exampleuser)
-    #   $sender_mxid        - The Matrix ID of the sender (e.g. @exampleuser:example.com)
+    #   $sender_username    - The username (Matrix ID localpart) of the sender (e.g. alice)
+    #   $sender_mxid        - The Matrix ID of the sender (e.g. @alice:example.com)
     #   $distinguisher      - A random string from the options in the relay_user_distinguishers array.
     #   $message            - The message content
     message_formats:
diff --git a/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml
index d095b6a39..8a2fb4200 100644
--- a/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml
+++ b/roles/custom/matrix-bridge-mautrix-twitter/defaults/main.yml
@@ -9,7 +9,7 @@ matrix_mautrix_twitter_container_image_self_build_repo: "https://github.com/maut
 matrix_mautrix_twitter_container_image_self_build_repo_version: "{{ 'master' if matrix_mautrix_twitter_version == 'latest' else matrix_mautrix_twitter_version }}"
 
 # renovate: datasource=docker depName=dock.mau.dev/mautrix/twitter
-matrix_mautrix_twitter_version: v0.1.8
+matrix_mautrix_twitter_version: v0.2.1
 # See: https://mau.dev/tulir/mautrix-twitter/container_registry
 matrix_mautrix_twitter_docker_image: "{{ matrix_mautrix_twitter_docker_image_name_prefix }}mautrix/twitter:{{ matrix_mautrix_twitter_version }}"
 matrix_mautrix_twitter_docker_image_name_prefix: "{{ 'localhost/' if matrix_mautrix_twitter_container_image_self_build else 'dock.mau.dev/' }}"
@@ -24,7 +24,10 @@ matrix_mautrix_twitter_homeserver_address: ""
 matrix_mautrix_twitter_homeserver_domain: '{{ matrix_domain }}'
 matrix_mautrix_twitter_appservice_address: 'http://matrix-mautrix-twitter:29327'
 
-matrix_mautrix_twitter_command_prefix: "!tw"
+# A public address that external services can use to reach this appservice.
+matrix_mautrix_twitter_appservice_public_address: ''
+
+matrix_mautrix_twitter_bridge_command_prefix: "!tw"
 
 matrix_mautrix_twitter_bridge_permissions: |
   {{
@@ -84,7 +87,7 @@ matrix_mautrix_twitter_homeserver_token: ''
 
 # Whether or not created rooms should have federation enabled.
 # If false, created portal rooms will never be federated.
-matrix_mautrix_twitter_federate_rooms: true
+matrix_mautrix_twitter_matrix_federate_rooms: true
 
 # Database-related configuration fields.
 #
@@ -97,23 +100,38 @@ matrix_mautrix_twitter_database_password: 'some-password'
 matrix_mautrix_twitter_database_hostname: ''
 matrix_mautrix_twitter_database_port: 5432
 matrix_mautrix_twitter_database_name: 'matrix_mautrix_twitter'
+matrix_mautrix_twitter_database_sslmode: disable
 
-matrix_mautrix_twitter_database_connection_string: 'postgres://{{ matrix_mautrix_twitter_database_username }}:{{ matrix_mautrix_twitter_database_password }}@{{ matrix_mautrix_twitter_database_hostname }}:{{ matrix_mautrix_twitter_database_port }}/{{ matrix_mautrix_twitter_database_name }}'
+matrix_mautrix_twitter_database_connection_string: 'postgres://{{ matrix_mautrix_twitter_database_username }}:{{ matrix_mautrix_twitter_database_password }}@{{ matrix_mautrix_twitter_database_hostname }}:{{ matrix_mautrix_twitter_database_port }}/{{ matrix_mautrix_twitter_database_name }}?sslmode={{ matrix_mautrix_twitter_database_sslmode }}'
 
-matrix_mautrix_twitter_appservice_database: "{{
+matrix_mautrix_twitter_database_uri: "{{
 	{
 		'postgres': matrix_mautrix_twitter_database_connection_string,
 	}[matrix_mautrix_twitter_database_engine]
 }}"
 
-matrix_mautrix_twitter_bridge_login_shared_secret_map: "{{ matrix_mautrix_twitter_bridge_login_shared_secret_map_auto | combine(matrix_mautrix_twitter_bridge_login_shared_secret_map_custom) }}"
-matrix_mautrix_twitter_bridge_login_shared_secret_map_auto: {}
-matrix_mautrix_twitter_bridge_login_shared_secret_map_custom: {}
+matrix_mautrix_twitter_double_puppet_secrets: "{{ matrix_mautrix_twitter_double_puppet_secrets_auto | combine(matrix_mautrix_twitter_double_puppet_secrets_custom) }}"
+matrix_mautrix_twitter_double_puppet_secrets_auto: {}
+matrix_mautrix_twitter_double_puppet_secrets_custom: {}
 
 matrix_mautrix_twitter_appservice_bot_username: twitterbot
+matrix_mautrix_twitter_appservice_bot_displayname: Twitter bridge bot
+matrix_mautrix_twitter_appservice_bot_avatar: mxc://maunium.net/HVHcnusJkQcpVcsVGZRELLCn
 
-# Specifies the default log level for all bridge loggers.
-matrix_mautrix_twitter_logging_level: WARNING
+matrix_mautrix_twitter_backfill_enabled: true
+# Maximum number of messages to backfill in empty rooms
+matrix_mautrix_twitter_backfill_max_initial_messages: 50
+
+# Maximum number of missed messages to backfill after bridge restarts
+matrix_mautrix_twitter_backfill_max_catchup_messages: 500
+
+# Shared secret for authentication of provisioning API requests.
+# If set to "disable", the provisioning API will be disabled.
+matrix_mautrix_twitter_provisioning_shared_secret: disable
+
+# Minimum severity of journal log messages.
+# Options: trace, debug, info, warn, error, fatal
+matrix_mautrix_twitter_logging_level: 'warn'
 
 # Whether or not metrics endpoint should be enabled.
 # Enabling them is usually enough for a local (in-container) Prometheus to consume them.
@@ -162,10 +180,15 @@ matrix_mautrix_twitter_registration_yaml: |
   sender_localpart: _bot_{{ matrix_mautrix_twitter_appservice_bot_username }}
   rate_limited: false
   de.sorunome.msc2409.push_ephemeral: true
+  receive_ephemeral: true
 
 matrix_mautrix_twitter_registration: "{{ matrix_mautrix_twitter_registration_yaml | from_yaml }}"
 
 # Enable End-to-bridge encryption
 matrix_mautrix_twitter_bridge_encryption_allow: "{{ matrix_bridges_encryption_enabled }}"
 matrix_mautrix_twitter_bridge_encryption_default: "{{ matrix_bridges_encryption_default }}"
+matrix_mautrix_twitter_bridge_encryption_require: false
+matrix_mautrix_twitter_bridge_encryption_appservice: false
 matrix_mautrix_twitter_bridge_encryption_key_sharing_allow: "{{ matrix_mautrix_twitter_bridge_encryption_allow }}"
+# This pickle key value is compatible with the old mautrix-twitter bridge (before bridgev2).
+matrix_mautrix_twitter_bridge_encryption_pickle_key: mautrix.bridge.e2ee
diff --git a/roles/custom/matrix-bridge-mautrix-twitter/tasks/validate_config.yml b/roles/custom/matrix-bridge-mautrix-twitter/tasks/validate_config.yml
index e8e7de330..b63a61558 100644
--- a/roles/custom/matrix-bridge-mautrix-twitter/tasks/validate_config.yml
+++ b/roles/custom/matrix-bridge-mautrix-twitter/tasks/validate_config.yml
@@ -22,3 +22,9 @@
   when: "item.old in vars"
   with_items:
     - {'old': 'matrix_mautrix_twitter_login_shared_secret', 'new': '<removed>'}
+    - {'old': 'matrix_mautrix_twitter_appservice_database', 'new': 'matrix_mautrix_twitter_database_uri'}
+    - {'old': 'matrix_mautrix_twitter_bridge_login_shared_secret_map', 'new': 'matrix_mautrix_twitter_double_puppet_secrets'}
+    - {'old': 'matrix_mautrix_twitter_bridge_login_shared_secret_map_auto', 'new': 'matrix_mautrix_twitter_double_puppet_secrets_auto'}
+    - {'old': 'matrix_mautrix_twitter_bridge_login_shared_secret_map_custom', 'new': 'matrix_mautrix_twitter_double_puppet_secrets_custom'}
+    - {'old': 'matrix_mautrix_twitter_federate_rooms', 'new': 'matrix_mautrix_twitter_matrix_federate_rooms'}
+    - {'old': 'matrix_mautrix_twitter_command_prefix', 'new': 'matrix_mautrix_twitter_bridge_command_prefix'}
diff --git a/roles/custom/matrix-bridge-mautrix-twitter/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-twitter/templates/config.yaml.j2
index bfcfdecb4..1a0b474f4 100644
--- a/roles/custom/matrix-bridge-mautrix-twitter/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-mautrix-twitter/templates/config.yaml.j2
@@ -1,202 +1,428 @@
 #jinja2: lstrip_blocks: "True"
-# Homeserver details
-homeserver:
-    # The address that this appservice can use to connect to the homeserver.
-    address: {{ matrix_mautrix_twitter_homeserver_address }}
-    # The domain of the homeserver (for MXIDs, etc).
-    domain: {{ matrix_mautrix_twitter_homeserver_domain }}
-    # Whether or not to verify the SSL certificate of the homeserver.
-    # Only applies if address starts with https://
-    verify_ssl: true
-    asmux: false
+# Network-specific config options
+network:
+    # Proxy to use for all Twitter connections.
+    proxy: null
+    # Alternative to proxy: an HTTP endpoint that returns the proxy URL to use for Twitter connections.
+    get_proxy_url: null
 
-# Application service host/registration related details
-# Changing these values requires regeneration of the registration.
-appservice:
-    # The address that the homeserver can use to connect to this appservice.
-    address: {{ matrix_mautrix_twitter_appservice_address }}
-    # When using https:// the TLS certificate and key files for the address.
-    tls_cert: false
-    tls_key: false
-
-    # The hostname and port where this appservice should listen.
-    hostname: 0.0.0.0
-    port: 29327
-    # The maximum body size of appservice API requests (from the homeserver) in mebibytes
-    # Usually 1 is enough, but on high-traffic bridges you might need to increase this to avoid 413s
-    max_body_size: 1
-
-    # The full URI to the database. Only Postgres is currently supported.
-    database: {{ matrix_mautrix_twitter_appservice_database|to_json }}
-    # Additional arguments for asyncpg.create_pool()
-    # https://magicstack.github.io/asyncpg/current/api/index.html#asyncpg.pool.create_pool
-    database_opts:
-        min_size: 5
-        max_size: 10
-
-    # Provisioning API part of the web server for automated portal creation and fetching information.
-    # Used by things like mautrix-manager (https://github.com/tulir/mautrix-manager).
-    provisioning:
-        # Whether or not the provisioning API should be enabled.
-        enabled: true
-        # The prefix to use in the provisioning API endpoints.
-        prefix: /_matrix/provision/v1
-        # The shared secret to authorize users of the API.
-        # Set to "generate" to generate and save a new token.
-        shared_secret: generate
-
-    # The unique ID of this appservice.
-    id: twitter
-    # Username of the appservice bot.
-    bot_username: {{ matrix_mautrix_twitter_appservice_bot_username|to_json }}
-    # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty
-    # to leave display name/avatar as-is.
-    bot_displayname: Twitter bridge bot
-    bot_avatar: mxc://maunium.net/HVHcnusJkQcpVcsVGZRELLCn
-
-    # Whether or not to receive ephemeral events via appservice transactions.
-    # Requires MSC2409 support (i.e. Synapse 1.22+).
-    # You should disable bridge -> sync_with_custom_puppets when this is enabled.
-    ephemeral_events: false
-
-    # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify.
-    as_token: "{{ matrix_mautrix_twitter_appservice_token }}"
-    hs_token: "{{ matrix_mautrix_twitter_homeserver_token }}"
-
-# Prometheus telemetry config. Requires prometheus-client to be installed.
-metrics:
-    enabled: {{ matrix_mautrix_twitter_metrics_enabled | to_json }}
-    listen_port: 8000
-
-# Bridge config
-bridge:
-    # Localpart template of MXIDs for Twitter users.
-    # {userid} is replaced with the user ID of the Twitter user.
-    username_template: "twitter_{userid}"
     # Displayname template for Twitter users.
-    # {displayname} is replaced with the display name of the Twitter user.
-    # {username} is replaced with the username of the Twitter user.
-    displayname_template: "{displayname} (Twitter)"
+    # {% raw %}
+    # {{ .DisplayName }} is replaced with the display name of the Twitter user.
+    # {{ .Username }} is replaced with the username of the Twitter user.
+    # {% endraw %}
+    displayname_template: "{% raw %}{{ .DisplayName }}{% endraw %} (Twitter)"
 
-    # Maximum length of displayname
-    displayname_max_length: 100
+    # Maximum number of conversations to sync on startup
+    conversation_sync_limit: 20
 
-    # Number of conversations to sync (and create portals for) on login.
-    # Set 0 to disable automatic syncing.
-    initial_conversation_sync: 10
-    # Whether or not to use /sync to get read receipts and typing notifications
-    # when double puppeting is enabled
-    sync_with_custom_puppets: true
-    # Whether or not to update the m.direct account data event when double puppeting is enabled.
-    # Note that updating the m.direct event is not atomic (except with mautrix-asmux)
-    # and is therefore prone to race conditions.
-    sync_direct_chat_list: false
-    # Allow using double puppeting from any server with a valid client .well-known file.
-    double_puppet_allow_discovery: false
-    # Servers to allow double puppeting from, even if double_puppet_allow_discovery is false.
-    double_puppet_server_map: {}
-    # Shared secret for https://github.com/devture/matrix-synapse-shared-secret-auth
-    #
-    # If set, custom puppets will be enabled automatically for local users
-    # instead of users having to find an access token and run `login-matrix`
-    # manually.
-    # If using this for other servers than the bridge's server,
-    # you must also set the URL in the double_puppet_server_map.
-    login_shared_secret_map: {{ matrix_mautrix_twitter_bridge_login_shared_secret_map|to_json }}
-    # Whether or not created rooms should have federation enabled.
-    # If false, created portal rooms will never be federated.
-    federate_rooms: {{ matrix_mautrix_twitter_federate_rooms|to_json }}
-    # Settings for backfilling messages from Twitter.
-    #
-    # Missed message backfilling is currently based on receiving them from the Twitter polling API,
-    # rather than manually asking for messages in each conversation. Due to this, there's no way to
-    # set a limit for missed message backfilling.
-    backfill:
-        # Whether or not the Twitter users of logged in Matrix users should be
-        # invited to private chats when backfilling history from Twitter. This is
-        # usually needed to prevent rate limits and to allow timestamp massaging.
-        invite_own_puppet: true
-        # Maximum number of messages to backfill initially.
-        # Set to 0 to disable backfilling when creating portal.
-        initial_limit: 0
-        # If using double puppeting, should notifications be disabled
-        # while the initial backfill is in progress?
-        disable_notifications: true
-    # End-to-bridge encryption support options. You must install the e2be optional dependency for
-    # this to work. See https://github.com/tulir/mautrix-telegram/wiki/End‐to‐bridge-encryption
-    encryption:
-        # Allow encryption, work in group chat rooms with e2ee enabled
-        allow: {{ matrix_mautrix_twitter_bridge_encryption_allow|to_json }}
-        # Default to encryption, force-enable encryption in all portals the bridge creates
-        # This will cause the bridge bot to be in private chats for the encryption to work properly.
-        default: {{ matrix_mautrix_twitter_bridge_encryption_default|to_json }}
-        # Options for automatic key sharing.
-        key_sharing:
-            # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
-            # You must use a client that supports requesting keys from other users to use this feature.
-            allow: {{ matrix_mautrix_twitter_bridge_encryption_key_sharing_allow|to_json }}
-            # Require the requesting device to have a valid cross-signing signature?
-            # This doesn't require that the bridge has verified the device, only that the user has verified it.
-            # Not yet implemented.
-            require_cross_signing: false
-            # Require devices to be verified by the bridge?
-            # Verification by the bridge is not yet implemented.
-            require_verification: true
-    # Whether or not to explicitly set the avatar and room name for private
-    # chat portal rooms. This will be implicitly enabled if encryption.default is true.
-    private_chat_portal_meta: false
-    # Whether or not the bridge should send a read receipt from the bridge bot when a message has
-    # been sent to Twitter.
-    delivery_receipts: false
-    # Whether or not delivery errors should be reported as messages in the Matrix room.
-    delivery_error_reports: true
-    # Whether or not non-fatal polling errors should send notices to the notice room.
-    temporary_disconnect_notices: true
-    # Number of seconds to sleep more than the previous error when a polling error occurs.
-    # Growth is capped at 15 minutes.
-    error_sleep: 5
-    # Maximum number of polling errors before giving up. Set to -1 to retry forever.
-    max_poll_errors: 12
-    # Set this to true to tell the bridge to re-send m.bridge events to all rooms on the next run.
-    # This field will automatically be changed back to false after it,
-    # except if the config file is not writable.
+
+# Config options that affect the central bridge module.
+bridge:
+    # The prefix for commands. Only required in non-management rooms.
+    command_prefix: {{ matrix_mautrix_twitter_bridge_command_prefix | to_json }}
+    # Should the bridge create a space for each login containing the rooms that account is in?
+    personal_filtering_spaces: true
+    # Whether the bridge should set names and avatars explicitly for DM portals.
+    # This is only necessary when using clients that don't support MSC4171.
+    private_chat_portal_meta: true
+    # Should events be handled asynchronously within portal rooms?
+    # If true, events may end up being out of order, but slow events won't block other ones.
+    # This is not yet safe to use.
+    async_events: false
+    # Should every user have their own portals rather than sharing them?
+    # By default, users who are in the same group on the remote network will be
+    # in the same Matrix room bridged to that group. If this is set to true,
+    # every user will get their own Matrix room instead.
+    split_portals: false
+    # Should the bridge resend `m.bridge` events to all portals on startup?
     resend_bridge_info: false
 
-    # The prefix for commands. Only required in non-management rooms.
-    command_prefix: "{{ matrix_mautrix_twitter_command_prefix }}"
+    # Should leaving Matrix rooms be bridged as leaving groups on the remote network?
+    bridge_matrix_leave: false
+    # Should room tags only be synced when creating the portal? Tags mean things like favorite/pin and archive/low priority.
+    # Tags currently can't be synced back to the remote network, so a continuous sync means tagging from Matrix will be undone.
+    tag_only_on_create: true
+    # List of tags to allow bridging. If empty, no tags will be bridged.
+    only_bridge_tags: [m.favourite, m.lowpriority]
+    # Should room mute status only be synced when creating the portal?
+    # Like tags, mutes can't currently be synced back to the remote network.
+    mute_only_on_create: true
+
+    # What should be done to portal rooms when a user logs out or is logged out?
+    # Permitted values:
+    #   nothing - Do nothing, let the user stay in the portals
+    #   kick - Remove the user from the portal rooms, but don't delete them
+    #   unbridge - Remove all ghosts in the room and disassociate it from the remote chat
+    #   delete - Remove all ghosts and users from the room (i.e. delete it)
+    cleanup_on_logout:
+        # Should cleanup on logout be enabled at all?
+        enabled: false
+        # Settings for manual logouts (explicitly initiated by the Matrix user)
+        manual:
+            # Action for private portals which will never be shared with other Matrix users.
+            private: nothing
+            # Action for portals with a relay user configured.
+            relayed: nothing
+            # Action for portals which may be shared, but don't currently have any other Matrix users.
+            shared_no_users: nothing
+            # Action for portals which have other logged-in Matrix users.
+            shared_has_users: nothing
+        # Settings for credentials being invalidated (initiated by the remote network, possibly through user action).
+        # Keys have the same meanings as in the manual section.
+        bad_credentials:
+            private: nothing
+            relayed: nothing
+            shared_no_users: nothing
+            shared_has_users: nothing
+
+    # Settings for relay mode
+    relay:
+        # Whether relay mode should be allowed. If allowed, the set-relay command can be used to turn any
+        # authenticated user into a relaybot for that chat.
+        enabled: false
+        # Should only admins be allowed to set themselves as relay users?
+        # If true, non-admins can only set users listed in default_relays as relays in a room.
+        admin_only: true
+        # List of user login IDs which anyone can set as a relay, as long as the relay user is in the room.
+        default_relays: []
+        # The formats to use when sending messages via the relaybot.
+        # Available variables:
+        #   .Sender.UserID - The Matrix user ID of the sender.
+        #   .Sender.Displayname - The display name of the sender (if set).
+        #   .Sender.RequiresDisambiguation - Whether the sender's name may be confused with the name of another user in the room.
+        #   .Sender.DisambiguatedName - The disambiguated name of the sender. This will be the displayname if set,
+        #                               plus the user ID in parentheses if the displayname is not unique.
+        #                               If the displayname is not set, this is just the user ID.
+        #   .Message - The `formatted_body` field of the message.
+        #   .Caption - The `formatted_body` field of the message, if it's a caption. Otherwise an empty string.
+        #   .FileName - The name of the file being sent.
+        message_formats:
+            m.text: "{% raw %}<b>{{ .Sender.DisambiguatedName }}</b>: {{ .Message }}{% endraw %}"
+            m.notice: "{% raw %}<b>{{ .Sender.DisambiguatedName }}</b>: {{ .Message }}{% endraw %}"
+            m.emote: "{% raw %}* <b>{{ .Sender.DisambiguatedName }}</b> {{ .Message }}{% endraw %}"
+            m.file: "{% raw %}<b>{{ .Sender.DisambiguatedName }}</b> sent a file{{ if .Caption }}: {{ .Caption }}{{ end }}{% endraw %}"
+            m.image: "{% raw %}<b>{{ .Sender.DisambiguatedName }}</b> sent an image{{ if .Caption }}: {{ .Caption }}{{ end }}{% endraw %}"
+            m.audio: "{% raw %}<b>{{ .Sender.DisambiguatedName }}</b> sent an audio file{{ if .Caption }}: {{ .Caption }}{{ end }}{% endraw %}"
+            m.video: "{% raw %}<b>{{ .Sender.DisambiguatedName }}</b> sent a video{{ if .Caption }}: {{ .Caption }}{{ end }}{% endraw %}"
+            m.location: "{% raw %}<b>{{ .Sender.DisambiguatedName }}</b> sent a location{{ if .Caption }}: {{ .Caption }}{{ end }}{% endraw %}"
+        # For networks that support per-message displaynames (i.e. Slack and Discord), the template for those names.
+        # This has all the Sender variables available under message_formats (but without the .Sender prefix).
+        # Note that you need to manually remove the displayname from message_formats above.
+        displayname_format: "{% raw %}{{ .DisambiguatedName }}{% endraw %}"
 
     # Permissions for using the bridge.
     # Permitted values:
-    #       user - Use the bridge with puppeting.
-    #      admin - Use and administrate the bridge.
+    #    relay - Talk through the relaybot (if enabled), no access otherwise
+    # commands - Access to use commands in the bridge, but not login.
+    #     user - Access to use the bridge with puppeting.
+    #    admin - Full access, user level with some additional administration tools.
     # Permitted keys:
     #        * - All Matrix users
     #   domain - All users on that homeserver
     #     mxid - Specific user
-    permissions: {{ matrix_mautrix_twitter_bridge_permissions|to_json }}
+    permissions: {{ matrix_mautrix_twitter_bridge_permissions | to_json }}
 
+# Config for the bridge's database.
+database:
+    # The database type. "sqlite3-fk-wal" and "postgres" are supported.
+    type: postgres
+    # The database URI.
+    #   SQLite: A raw file path is supported, but `file:<path>?_txlock=immediate` is recommended.
+    #           https://github.com/mattn/go-sqlite3#connection-string
+    #   Postgres: Connection string. For example, postgres://user:password@host/database?sslmode=disable
+    #             To connect via Unix socket, use something like postgres:///dbname?host=/var/run/postgresql
+    uri: {{ matrix_mautrix_twitter_database_uri | to_json }}
+    # Maximum number of connections.
+    max_open_conns: 5
+    max_idle_conns: 1
+    # Maximum connection idle time and lifetime before they're closed. Disabled if null.
+    # Parsed with https://pkg.go.dev/time#ParseDuration
+    max_conn_idle_time: null
+    max_conn_lifetime: null
 
-# Python logging configuration.
+# Homeserver details.
+homeserver:
+    # The address that this appservice can use to connect to the homeserver.
+    # Local addresses without HTTPS are generally recommended when the bridge is running on the same machine,
+    # but https also works if they run on different machines.
+    address: {{ matrix_mautrix_twitter_homeserver_address | to_json }}
+    # The domain of the homeserver (also known as server_name, used for MXIDs, etc).
+    domain: {{ matrix_mautrix_twitter_homeserver_domain | to_json }}
+
+    # What software is the homeserver running?
+    # Standard Matrix homeservers like Synapse, Dendrite and Conduit should just use "standard" here.
+    software: standard
+    # The URL to push real-time bridge status to.
+    # If set, the bridge will make POST requests to this URL whenever a user's remote network connection state changes.
+    # The bridge will use the appservice as_token to authorize requests.
+    status_endpoint:
+    # Endpoint for reporting per-message status.
+    # If set, the bridge will make POST requests to this URL when processing a message from Matrix.
+    # It will make one request when receiving the message (step BRIDGE), one after decrypting if applicable
+    # (step DECRYPTED) and one after sending to the remote network (step REMOTE). Errors will also be reported.
+    # The bridge will use the appservice as_token to authorize requests.
+    message_send_checkpoint_endpoint:
+    # Does the homeserver support https://github.com/matrix-org/matrix-spec-proposals/pull/2246?
+    async_media: false
+
+    # Should the bridge use a websocket for connecting to the homeserver?
+    # The server side is currently not documented anywhere and is only implemented by mautrix-wsproxy,
+    # mautrix-asmux (deprecated), and hungryserv (proprietary).
+    websocket: false
+    # How often should the websocket be pinged? Pinging will be disabled if this is zero.
+    ping_interval_seconds: 0
+
+# Application service host/registration related details.
+# Changing these values requires regeneration of the registration (except when noted otherwise)
+appservice:
+    # The address that the homeserver can use to connect to this appservice.
+    # Like the homeserver address, a local non-https address is recommended when the bridge is on the same machine.
+    # If the bridge is elsewhere, you must secure the connection yourself (e.g. with https or wireguard)
+    # If you want to use https, you need to use a reverse proxy. The bridge does not have TLS support built in.
+    address: {{ matrix_mautrix_twitter_appservice_address | to_json }}
+    # A public address that external services can use to reach this appservice.
+    # This is only needed for things like public media. A reverse proxy is generally necessary when using this field.
+    # This value doesn't affect the registration file.
+    public_address: {{ matrix_mautrix_twitter_appservice_public_address | to_json }}
+
+    # The hostname and port where this appservice should listen.
+    # For Docker, you generally have to change the hostname to 0.0.0.0.
+    hostname: 0.0.0.0
+    port: 29327
+
+    # The unique ID of this appservice.
+    id: twitter
+    # Appservice bot details.
+    bot:
+        # Username of the appservice bot.
+        username: {{ matrix_mautrix_twitter_appservice_bot_username | to_json }}
+        # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty
+        # to leave display name/avatar as-is.
+        displayname: {{ matrix_mautrix_twitter_appservice_bot_displayname | to_json }}
+        avatar: {{ matrix_mautrix_twitter_appservice_bot_avatar | to_json }}
+
+    # Whether to receive ephemeral events via appservice transactions.
+    ephemeral_events: true
+    # Should incoming events be handled asynchronously?
+    # This may be necessary for large public instances with lots of messages going through.
+    # However, messages will not be guaranteed to be bridged in the same order they were sent in.
+    # This value doesn't affect the registration file.
+    async_transactions: false
+    # Whether to use MSC4190 instead of appservice login to create the bridge bot device.
+    # Requires the homeserver to support MSC4190 and the device masquerading parts of MSC3202.
+    # Only relevant when using end-to-bridge encryption, required when using encryption with next-gen auth (MSC3861).
+    msc4190: false
+
+    # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify.
+    as_token: {{ matrix_mautrix_twitter_appservice_token | to_json }}
+    hs_token: {{ matrix_mautrix_twitter_homeserver_token | to_json }}
+
+    # Localpart template of MXIDs for remote users.
+    # {% raw %}{{.}}{% endraw %} is replaced with the internal ID of the user.
+    username_template: "{% raw %}twitter_{{.}}{% endraw %}"
+
+# Config options that affect the Matrix connector of the bridge.
+matrix:
+    # Whether the bridge should send the message status as a custom com.beeper.message_send_status event.
+    message_status_events: false
+    # Whether the bridge should send a read receipt after successfully bridging a message.
+    delivery_receipts: false
+    # Whether the bridge should send error notices via m.notice events when a message fails to bridge.
+    message_error_notices: true
+    # Whether the bridge should update the m.direct account data event when double puppeting is enabled.
+    sync_direct_chat_list: true
+    # Whether created rooms should have federation enabled. If false, created portal rooms
+    # will never be federated. Changing this option requires recreating rooms.
+    federate_rooms: {{ matrix_mautrix_twitter_matrix_federate_rooms | to_json }}
+    # The threshold as bytes after which the bridge should roundtrip uploads via the disk
+    # rather than keeping the whole file in memory.
+    upload_file_threshold: 5242880
+
+# Segment-compatible analytics endpoint for tracking some events, like provisioning API login and encryption errors.
+analytics:
+    # API key to send with tracking requests. Tracking is disabled if this is null.
+    token: null
+    # Address to send tracking requests to.
+    url: https://api.segment.io/v1/track
+    # Optional user ID for tracking events. If null, defaults to using Matrix user ID.
+    user_id: null
+
+# Settings for provisioning API
+provisioning:
+    # Prefix for the provisioning API paths.
+    prefix: /_matrix/provision
+    # Shared secret for authentication. If set to "generate" or null, a random secret will be generated,
+    # or if set to "disable", the provisioning API will be disabled.
+    shared_secret: {{ matrix_mautrix_twitter_provisioning_shared_secret | to_json }}
+    # Whether to allow provisioning API requests to be authed using Matrix access tokens.
+    # This follows the same rules as double puppeting to determine which server to contact to check the token,
+    # which means that by default, it only works for users on the same server as the bridge.
+    allow_matrix_auth: true
+    # Enable debug API at /debug with provisioning authentication.
+    debug_endpoints: false
+
+# Some networks require publicly accessible media download links (e.g. for user avatars when using Discord webhooks).
+# These settings control whether the bridge will provide such public media access.
+public_media:
+    # Should public media be enabled at all?
+    # The public_address field under the appservice section MUST be set when enabling public media.
+    enabled: false
+    # A key for signing public media URLs.
+    # If set to "generate", a random key will be generated.
+    signing_key: ""
+    # Number of seconds that public media URLs are valid for.
+    # If set to 0, URLs will never expire.
+    expiry: 0
+    # Length of hash to use for public media URLs. Must be between 0 and 32.
+    hash_length: 32
+
+# Settings for converting remote media to custom mxc:// URIs instead of reuploading.
+# More details can be found at https://docs.mau.fi/bridges/go/discord/direct-media.html
+direct_media:
+    # Should custom mxc:// URIs be used instead of reuploading media?
+    enabled: false
+    # The server name to use for the custom mxc:// URIs.
+    # This server name will effectively be a real Matrix server, it just won't implement anything other than media.
+    # You must either set up .well-known delegation from this domain to the bridge, or proxy the domain directly to the bridge.
+    server_name: discord-media.example.com
+    # Optionally a custom .well-known response. This defaults to `server_name:443`
+    well_known_response:
+    # Optionally specify a custom prefix for the media ID part of the MXC URI.
+    media_id_prefix:
+    # If the remote network supports media downloads over HTTP, then the bridge will use MSC3860/MSC3916
+    # media download redirects if the requester supports it. Optionally, you can force redirects
+    # and not allow proxying at all by setting this to false.
+    # This option does nothing if the remote network does not support media downloads over HTTP.
+    allow_proxy: true
+    # Matrix server signing key to make the federation tester pass, same format as synapse's .signing.key file.
+    # This key is also used to sign the mxc:// URIs to ensure only the bridge can generate them.
+    server_key: ""
+
+# Settings for backfilling messages.
+# Note that the exact way settings are applied depends on the network connector.
+# See https://docs.mau.fi/bridges/general/backfill.html for more details.
+backfill:
+    # Whether to do backfilling at all.
+    enabled: {{ matrix_mautrix_twitter_backfill_enabled | to_json }}
+    # Maximum number of messages to backfill in empty rooms.
+    max_initial_messages: {{ matrix_mautrix_twitter_backfill_max_initial_messages | to_json }}
+    # Maximum number of missed messages to backfill after bridge restarts.
+    max_catchup_messages: {{ matrix_mautrix_twitter_backfill_max_catchup_messages | to_json }}
+    # If a backfilled chat is older than this number of hours,
+    # mark it as read even if it's unread on the remote network.
+    unread_hours_threshold: 720
+    # Settings for backfilling threads within other backfills.
+    threads:
+        # Maximum number of messages to backfill in a new thread.
+        max_initial_messages: 50
+    # Settings for the backwards backfill queue. This only applies when connecting to
+    # Beeper as standard Matrix servers don't support inserting messages into history.
+    queue:
+        # Should the backfill queue be enabled?
+        enabled: false
+        # Number of messages to backfill in one batch.
+        batch_size: 100
+        # Delay between batches in seconds.
+        batch_delay: 20
+        # Maximum number of batches to backfill per portal.
+        # If set to -1, all available messages will be backfilled.
+        max_batches: -1
+        # Optional network-specific overrides for max batches.
+        # Interpretation of this field depends on the network connector.
+        max_batches_override: {}
+
+# Settings for enabling double puppeting
+double_puppet:
+    # Servers to always allow double puppeting from.
+    # This is only for other servers and should NOT contain the server the bridge is on.
+    servers: {}
+    # Whether to allow client API URL discovery for other servers. When using this option,
+    # users on other servers can use double puppeting even if their server URLs aren't
+    # explicitly added to the servers map above.
+    allow_discovery: false
+    # Shared secrets for automatic double puppeting.
+    # See https://docs.mau.fi/bridges/general/double-puppeting.html for instructions.
+    secrets: {{ matrix_mautrix_twitter_double_puppet_secrets | to_json }}
+
+# End-to-bridge encryption support options.
 #
-# See section 16.7.2 of the Python documentation for more info:
-# https://docs.python.org/3.6/library/logging.config.html#configuration-dictionary-schema
+# See https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html for more info.
+encryption:
+    # Whether to enable encryption at all. If false, the bridge will not function in encrypted rooms.
+    allow: {{ matrix_mautrix_twitter_bridge_encryption_allow | to_json }}
+    # Whether to force-enable encryption in all bridged rooms.
+    default: {{ matrix_mautrix_twitter_bridge_encryption_default | to_json }}
+    # Whether to require all messages to be encrypted and drop any unencrypted messages.
+    require: {{ matrix_mautrix_twitter_bridge_encryption_require | to_json }}
+    # Whether to use MSC2409/MSC3202 instead of /sync long polling for receiving encryption-related data.
+    # This option is not yet compatible with standard Matrix servers like Synapse and should not be used.
+    appservice: {{ matrix_mautrix_twitter_bridge_encryption_appservice | to_json }}
+    # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
+    # You must use a client that supports requesting keys from other users to use this feature.
+    allow_key_sharing: {{ matrix_mautrix_twitter_bridge_encryption_key_sharing_allow | to_json }}
+    # Pickle key for encrypting encryption keys in the bridge database.
+    # If set to generate, a random key will be generated.
+    pickle_key: {{ matrix_mautrix_twitter_bridge_encryption_pickle_key | to_json }}
+    # Options for deleting megolm sessions from the bridge.
+    delete_keys:
+        # Beeper-specific: delete outbound sessions when hungryserv confirms
+        # that the user has uploaded the key to key backup.
+        delete_outbound_on_ack: false
+        # Don't store outbound sessions in the inbound table.
+        dont_store_outbound: false
+        # Ratchet megolm sessions forward after decrypting messages.
+        ratchet_on_decrypt: false
+        # Delete fully used keys (index >= max_messages) after decrypting messages.
+        delete_fully_used_on_decrypt: false
+        # Delete previous megolm sessions from same device when receiving a new one.
+        delete_prev_on_new_session: false
+        # Delete megolm sessions received from a device when the device is deleted.
+        delete_on_device_delete: false
+        # Periodically delete megolm sessions when 2x max_age has passed since receiving the session.
+        periodically_delete_expired: false
+        # Delete inbound megolm sessions that don't have the received_at field used for
+        # automatic ratcheting and expired session deletion. This is meant as a migration
+        # to delete old keys prior to the bridge update.
+        delete_outdated_inbound: false
+    # What level of device verification should be required from users?
+    #
+    # Valid levels:
+    #   unverified - Send keys to all device in the room.
+    #   cross-signed-untrusted - Require valid cross-signing, but trust all cross-signing keys.
+    #   cross-signed-tofu - Require valid cross-signing, trust cross-signing keys on first use (and reject changes).
+    #   cross-signed-verified - Require valid cross-signing, plus a valid user signature from the bridge bot.
+    #                           Note that creating user signatures from the bridge bot is not currently possible.
+    #   verified - Require manual per-device verification
+    #              (currently only possible by modifying the `trust` column in the `crypto_device` database table).
+    verification_levels:
+        # Minimum level for which the bridge should send keys to when bridging messages from the remote network to Matrix.
+        receive: unverified
+        # Minimum level that the bridge should accept for incoming Matrix messages.
+        send: unverified
+        # Minimum level that the bridge should require for accepting key requests.
+        share: cross-signed-tofu
+    # Options for Megolm room key rotation. These options allow you to configure the m.room.encryption event content.
+    # See https://spec.matrix.org/v1.10/client-server-api/#mroomencryption for more information about that event.
+    rotation:
+        # Enable custom Megolm room key rotation settings. Note that these
+        # settings will only apply to rooms created after this option is set.
+        enable_custom: false
+        # The maximum number of milliseconds a session should be used
+        # before changing it. The Matrix spec recommends 604800000 (a week)
+        # as the default.
+        milliseconds: 604800000
+        # The maximum number of messages that should be sent with a given a
+        # session before changing it. The Matrix spec recommends 100 as the
+        # default.
+        messages: 100
+        # Disable rotating keys when a user's devices change?
+        # You should not enable this option unless you understand all the implications.
+        disable_device_change_key_rotation: false
+
+# Logging config. See https://github.com/tulir/zeroconfig for details.
 logging:
-    version: 1
-    formatters:
-        colored:
-            (): mautrix_twitter.util.ColorFormatter
-            format: "[%(asctime)s] [%(levelname)s@%(name)s] %(message)s"
-        normal:
-            format: "[%(asctime)s] [%(levelname)s@%(name)s] %(message)s"
-    handlers:
-        console:
-            class: logging.StreamHandler
-            formatter: colored
-    loggers:
-        mau:
-            level: {{ matrix_mautrix_twitter_logging_level|to_json }}
-        aiohttp:
-            level: {{ matrix_mautrix_twitter_logging_level|to_json }}
-    root:
-        level: {{ matrix_mautrix_twitter_logging_level|to_json }}
-        handlers: [console]
+    min_level: {{ matrix_mautrix_twitter_logging_level | to_json }}
+    writers:
+        - type: stdout
+          format: pretty-colored
diff --git a/roles/custom/matrix-bridge-mautrix-twitter/templates/systemd/matrix-mautrix-twitter.service.j2 b/roles/custom/matrix-bridge-mautrix-twitter/templates/systemd/matrix-mautrix-twitter.service.j2
index a0ada77c5..ef16a675d 100644
--- a/roles/custom/matrix-bridge-mautrix-twitter/templates/systemd/matrix-mautrix-twitter.service.j2
+++ b/roles/custom/matrix-bridge-mautrix-twitter/templates/systemd/matrix-mautrix-twitter.service.j2
@@ -30,7 +30,7 @@ ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \
 			{{ arg }} \
 			{% endfor %}
 			{{ matrix_mautrix_twitter_docker_image }} \
-			python3 -m mautrix_twitter -c /config/config.yaml --no-update
+			/usr/bin/mautrix-twitter -c /config/config.yaml -r /config/registration.yaml --no-update
 
 {% for network in matrix_mautrix_twitter_container_additional_networks %}
 ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network connect {{ network }} matrix-mautrix-twitter
diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml b/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml
index bb2c8c5f3..2d2519338 100644
--- a/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml
+++ b/roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml
@@ -9,7 +9,7 @@ matrix_mautrix_whatsapp_container_image_self_build_repo: "https://mau.dev/mautri
 matrix_mautrix_whatsapp_container_image_self_build_branch: "{{ 'master' if matrix_mautrix_whatsapp_version == 'latest' else matrix_mautrix_whatsapp_version }}"
 
 # renovate: datasource=docker depName=dock.mau.dev/mautrix/whatsapp
-matrix_mautrix_whatsapp_version: v0.11.0
+matrix_mautrix_whatsapp_version: v0.11.2
 
 # See: https://mau.dev/mautrix/whatsapp/container_registry
 matrix_mautrix_whatsapp_docker_image: "{{ matrix_mautrix_whatsapp_docker_image_name_prefix }}mautrix/whatsapp:{{ matrix_mautrix_whatsapp_version }}"
@@ -82,7 +82,7 @@ matrix_mautrix_whatsapp_homeserver_token: ''
 matrix_mautrix_whatsapp_appservice_bot_username: whatsappbot
 
 # Minimum severity of journal log messages.
-# Options: debug, info, warn, error, fatal
+# Options: trace, debug, info, warn, error, fatal
 matrix_mautrix_whatsapp_logging_level: 'warn'
 
 # Whether or not created rooms should have federation enabled.
diff --git a/roles/custom/matrix-bridge-mautrix-whatsapp/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-whatsapp/templates/config.yaml.j2
index c6224525c..832234832 100644
--- a/roles/custom/matrix-bridge-mautrix-whatsapp/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-mautrix-whatsapp/templates/config.yaml.j2
@@ -384,7 +384,7 @@ direct_media:
     allow_proxy: true
     # Matrix server signing key to make the federation tester pass, same format as synapse's .signing.key file.
     # This key is also used to sign the mxc:// URIs to ensure only the bridge can generate them.
-    server_key: generate
+    server_key: ""
 
 # Settings for backfilling messages.
 # Note that the exact way settings are applied depends on the network connector.
diff --git a/roles/custom/matrix-bridge-mx-puppet-discord/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-discord/defaults/main.yml
index 3c825b351..faf1a770c 100644
--- a/roles/custom/matrix-bridge-mx-puppet-discord/defaults/main.yml
+++ b/roles/custom/matrix-bridge-mx-puppet-discord/defaults/main.yml
@@ -33,14 +33,14 @@ matrix_mx_puppet_discord_appservice_address: 'http://matrix-mx-puppet-discord:{{
 
 matrix_mx_puppet_discord_bridge_mediaUrl: "{{ matrix_homeserver_url }}"  # noqa var-naming
 
-# "@user:example.com" to allow a specific user
+# "@alice:example.com" to allow a specific user
 # "@.*:example.com" to allow users on a specific homeserver
 # "@.*" to allow anyone
 matrix_mx_puppet_discord_provisioning_whitelist:
   - "@.*:{{ matrix_domain | regex_escape }}"
 
 # Leave empty to disable blacklist
-# "@user:example.com" to disallow a specific user
+# "@bob:example.com" to disallow a specific user
 # "@.*:example.com" to disallow users on a specific homeserver
 matrix_mx_puppet_discord_provisioning_blacklist: []
 
diff --git a/roles/custom/matrix-bridge-mx-puppet-discord/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mx-puppet-discord/templates/config.yaml.j2
index 4940a469d..3db538127 100644
--- a/roles/custom/matrix-bridge-mx-puppet-discord/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-mx-puppet-discord/templates/config.yaml.j2
@@ -31,7 +31,7 @@ provisioning:
   # Regex of Matrix IDs allowed to use the puppet bridge
   whitelist: {{ matrix_mx_puppet_discord_provisioning_whitelist|to_json }}
     # Allow a specific user
-    #- "@user:example\\.com"
+    #- "@alice:example\\.com"
     # Allow users on a specific homeserver
     #- "@.*:example\\.com"
     # Allow anyone
@@ -39,7 +39,7 @@ provisioning:
   # Regex of Matrix IDs forbidden from using the puppet bridge
   #blacklist:
     # Disallow a specific user
-    #- "@user:example\\.com"
+    #- "@bob:example\\.com"
     # Disallow users on a specific homeserver
     #- "@.*:example\\.com"
   blacklist: {{ matrix_mx_puppet_discord_provisioning_blacklist|to_json }}
diff --git a/roles/custom/matrix-bridge-mx-puppet-groupme/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-groupme/defaults/main.yml
index 730123b0b..67ecd6cbd 100644
--- a/roles/custom/matrix-bridge-mx-puppet-groupme/defaults/main.yml
+++ b/roles/custom/matrix-bridge-mx-puppet-groupme/defaults/main.yml
@@ -29,14 +29,14 @@ matrix_mx_puppet_groupme_homeserver_address: ""
 matrix_mx_puppet_groupme_homeserver_domain: '{{ matrix_domain }}'
 matrix_mx_puppet_groupme_appservice_address: 'http://matrix-mx-puppet-groupme:{{ matrix_mx_puppet_groupme_appservice_port }}'
 
-# "@user:example.com" to allow a specific user
+# "@alice:example.com" to allow a specific user
 # "@.*:example.com" to allow users on a specific homeserver
 # "@.*" to allow anyone
 matrix_mx_puppet_groupme_provisioning_whitelist:
   - "@.*:{{ matrix_domain | regex_escape }}"
 
 # Leave empty to disable blacklist
-# "@user:example.com" to disallow a specific user
+# "@bob:example.com" to disallow a specific user
 # "@.*:example.com" to disallow users on a specific homeserver
 matrix_mx_puppet_groupme_provisioning_blacklist: []
 
diff --git a/roles/custom/matrix-bridge-mx-puppet-groupme/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mx-puppet-groupme/templates/config.yaml.j2
index 862397577..c3237513d 100644
--- a/roles/custom/matrix-bridge-mx-puppet-groupme/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-mx-puppet-groupme/templates/config.yaml.j2
@@ -31,7 +31,7 @@ provisioning:
   # Regex of Matrix IDs allowed to use the puppet bridge
   whitelist: {{ matrix_mx_puppet_groupme_provisioning_whitelist|to_json }}
     # Allow a specific user
-    #- "@user:example\\.com"
+    #- "@alice:example\\.com"
     # Allow users on a specific homeserver
     #- "@.*:example\\.com"
     # Allow anyone
@@ -39,7 +39,7 @@ provisioning:
   # Regex of Matrix IDs forbidden from using the puppet bridge
   #blacklist:
     # Disallow a specific user
-    #- "@user:example\\.com"
+    #- "@bob:example\\.com"
     # Disallow users on a specific homeserver
     #- "@.*:example\\.com"
   blacklist: {{ matrix_mx_puppet_groupme_provisioning_blacklist|to_json }}
diff --git a/roles/custom/matrix-bridge-mx-puppet-instagram/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-instagram/defaults/main.yml
index 54d56b3cd..168c4a3b3 100644
--- a/roles/custom/matrix-bridge-mx-puppet-instagram/defaults/main.yml
+++ b/roles/custom/matrix-bridge-mx-puppet-instagram/defaults/main.yml
@@ -24,14 +24,14 @@ matrix_mx_puppet_instagram_homeserver_address: ""
 matrix_mx_puppet_instagram_homeserver_domain: '{{ matrix_domain }}'
 matrix_mx_puppet_instagram_appservice_address: 'http://matrix-mx-puppet-instagram:{{ matrix_mx_puppet_instagram_appservice_port }}'
 
-# "@user:example.com" to allow a specific user
+# "@alice:example.com" to allow a specific user
 # "@.*:example.com" to allow users on a specific homeserver
 # "@.*" to allow anyone
 matrix_mx_puppet_instagram_provisioning_whitelist:
   - "@.*:{{ matrix_domain | regex_escape }}"
 
 # Leave empty to disable blacklist
-# "@user:example.com" to disallow a specific user
+# "@bob:example.com" to disallow a specific user
 # "@.*:example.com" to disallow users on a specific homeserver
 matrix_mx_puppet_instagram_provisioning_blacklist: []
 
diff --git a/roles/custom/matrix-bridge-mx-puppet-instagram/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mx-puppet-instagram/templates/config.yaml.j2
index 69943fe9b..2e15c5b0c 100644
--- a/roles/custom/matrix-bridge-mx-puppet-instagram/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-mx-puppet-instagram/templates/config.yaml.j2
@@ -24,7 +24,7 @@ provisioning:
   # Regex of Matrix IDs allowed to use the puppet bridge
   whitelist: {{ matrix_mx_puppet_instagram_provisioning_whitelist|to_json }}
     # Allow a specific user
-    #- "@user:example\\.com"
+    #- "@alice:example\\.com"
     # Allow users on a specific homeserver
     #- "@.*:example\\.com"
     # Allow anyone
@@ -32,7 +32,7 @@ provisioning:
   # Regex of Matrix IDs forbidden from using the puppet bridge
   #blacklist:
     # Disallow a specific user
-    #- "@user:example\\.com"
+    #- "@bob:example\\.com"
     # Disallow users on a specific homeserver
     #- "@.*:example\\.com"
   blacklist: {{ matrix_mx_puppet_instagram_provisioning_blacklist|to_json }}
diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml
index 307ee5b22..030ac871f 100644
--- a/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml
+++ b/roles/custom/matrix-bridge-mx-puppet-slack/defaults/main.yml
@@ -42,14 +42,14 @@ matrix_mx_puppet_slack_oauth_enabled: true
 matrix_mx_puppet_slack_oauth_redirect_path: "{{ matrix_mx_puppet_slack_path_prefix }}"
 matrix_mx_puppet_slack_oauth_redirect_uri: '{{ matrix_mx_puppet_slack_scheme }}://{{ matrix_mx_puppet_slack_hostname }}{{ matrix_mx_puppet_slack_oauth_redirect_path }}'
 
-# "@user:example.com" to allow a specific user
+# "@alice:example.com" to allow a specific user
 # "@.*:example.com" to allow users on a specific homeserver
 # "@.*" to allow anyone
 matrix_mx_puppet_slack_provisioning_whitelist:
   - "@.*:{{ matrix_domain | regex_escape }}"
 
 # Leave empty to disable blacklist
-# "@user:example.com" to disallow a specific user
+# "@bob:example.com" to disallow a specific user
 # "@.*:example.com" to disallow users on a specific homeserver
 matrix_mx_puppet_slack_provisioning_blacklist: []
 
diff --git a/roles/custom/matrix-bridge-mx-puppet-slack/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mx-puppet-slack/templates/config.yaml.j2
index b2ea9586d..ff965a172 100644
--- a/roles/custom/matrix-bridge-mx-puppet-slack/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-mx-puppet-slack/templates/config.yaml.j2
@@ -38,7 +38,7 @@ provisioning:
   # Regex of Matrix IDs allowed to use the puppet bridge
   whitelist: {{ matrix_mx_puppet_slack_provisioning_whitelist|to_json }}
     # Allow a specific user
-    #- "@user:example\\.com"
+    #- "@alice:example\\.com"
     # Allow users on a specific homeserver
     #- "@.*:example\\.com"
     # Allow anyone
@@ -46,7 +46,7 @@ provisioning:
   # Regex of Matrix IDs forbidden from using the puppet bridge
   #blacklist:
     # Disallow a specific user
-    #- "@user:example\\.com"
+    #- "@bob:example\\.com"
     # Disallow users on a specific homeserver
     #- "@.*:example\\.com"
   blacklist: {{ matrix_mx_puppet_slack_provisioning_blacklist|to_json }}
diff --git a/roles/custom/matrix-bridge-mx-puppet-steam/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-steam/defaults/main.yml
index 639537e0b..0e4ce1674 100644
--- a/roles/custom/matrix-bridge-mx-puppet-steam/defaults/main.yml
+++ b/roles/custom/matrix-bridge-mx-puppet-steam/defaults/main.yml
@@ -30,14 +30,14 @@ matrix_mx_puppet_steam_homeserver_address: ""
 matrix_mx_puppet_steam_homeserver_domain: '{{ matrix_domain }}'
 matrix_mx_puppet_steam_appservice_address: 'http://matrix-mx-puppet-steam:{{ matrix_mx_puppet_steam_appservice_port }}'
 
-# "@user:example.com" to allow a specific user
+# "@alice:example.com" to allow a specific user
 # "@.*:example.com" to allow users on a specific homeserver
 # "@.*" to allow anyone
 matrix_mx_puppet_steam_provisioning_whitelist:
   - "@.*:{{ matrix_domain | regex_escape }}"
 
 # Leave empty to disable blacklist
-# "@user:example.com" to disallow a specific user
+# "@bob:example.com" to disallow a specific user
 # "@.*:example.com" to disallow users on a specific homeserver
 matrix_mx_puppet_steam_provisioning_blacklist: []
 
diff --git a/roles/custom/matrix-bridge-mx-puppet-steam/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mx-puppet-steam/templates/config.yaml.j2
index 213d628d2..c2d089f7f 100644
--- a/roles/custom/matrix-bridge-mx-puppet-steam/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-mx-puppet-steam/templates/config.yaml.j2
@@ -31,7 +31,7 @@ provisioning:
   # Regex of Matrix IDs allowed to use the puppet bridge
   whitelist: {{ matrix_mx_puppet_steam_provisioning_whitelist|to_json }}
     # Allow a specific user
-    #- "@user:example\\.com"
+    #- "@alice:example\\.com"
     # Allow users on a specific homeserver
     #- "@.*:example\\.com"
     # Allow anyone
@@ -39,7 +39,7 @@ provisioning:
   # Regex of Matrix IDs forbidden from using the puppet bridge
   #blacklist:
     # Disallow a specific user
-    #- "@user:example\\.com"
+    #- "@bob:example\\.com"
     # Disallow users on a specific homeserver
     #- "@.*:example\\.com"
   blacklist: {{ matrix_mx_puppet_steam_provisioning_blacklist|to_json }}
diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml b/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml
index 4f806ff5d..24fc7fc07 100644
--- a/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml
+++ b/roles/custom/matrix-bridge-mx-puppet-twitter/defaults/main.yml
@@ -42,14 +42,14 @@ matrix_mx_puppet_twitter_environment: ''
 matrix_mx_puppet_twitter_server_path: "{{ matrix_mx_puppet_twitter_path_prefix }}"
 matrix_mx_puppet_twitter_server_url: '{{ matrix_homeserver_url }}{{ matrix_mx_puppet_twitter_server_path }}'
 
-# "@user:example.com" to allow a specific user
+# "@alice:example.com" to allow a specific user
 # "@.*:example.com" to allow users on a specific homeserver
 # "@.*" to allow anyone
 matrix_mx_puppet_twitter_provisioning_whitelist:
   - "@.*:{{ matrix_domain | regex_escape }}"
 
 # Leave empty to disable blacklist
-# "@user:example.com" to disallow a specific user
+# "@bob:example.com" to disallow a specific user
 # "@.*:example.com" to disallow users on a specific homeserver
 matrix_mx_puppet_twitter_provisioning_blacklist: []
 
diff --git a/roles/custom/matrix-bridge-mx-puppet-twitter/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mx-puppet-twitter/templates/config.yaml.j2
index c7dc8c32e..9cbcf2bc7 100644
--- a/roles/custom/matrix-bridge-mx-puppet-twitter/templates/config.yaml.j2
+++ b/roles/custom/matrix-bridge-mx-puppet-twitter/templates/config.yaml.j2
@@ -34,7 +34,7 @@ provisioning:
   # Regex of Matrix IDs allowed to use the puppet bridge
   whitelist: {{ matrix_mx_puppet_twitter_provisioning_whitelist|to_json }}
     # Allow a specific user
-    #- "@user:example\\.com"
+    #- "@alice:example\\.com"
     # Allow users on a specific homeserver
     #- "@.*:example\\.com"
     # Allow anyone
@@ -42,7 +42,7 @@ provisioning:
   # Regex of Matrix IDs forbidden from using the puppet bridge
   #blacklist:
     # Disallow a specific user
-    #- "@user:example\\.com"
+    #- "@bob:example\\.com"
     # Disallow users on a specific homeserver
     #- "@.*:example\\.com"
   blacklist: {{ matrix_mx_puppet_twitter_provisioning_blacklist|to_json }}
diff --git a/roles/custom/matrix-bridge-postmoogle/defaults/main.yml b/roles/custom/matrix-bridge-postmoogle/defaults/main.yml
new file mode 100644
index 000000000..99bd6085a
--- /dev/null
+++ b/roles/custom/matrix-bridge-postmoogle/defaults/main.yml
@@ -0,0 +1,179 @@
+---
+# postmoogle is an email to Matrix bridge using its bot user
+# Project source code URL: https://github.com/etkecc/postmoogle
+
+matrix_postmoogle_enabled: true
+
+matrix_postmoogle_container_image_self_build: false
+matrix_postmoogle_docker_repo: "https://github.com/etkecc/postmoogle.git"
+matrix_postmoogle_docker_repo_version: "{{ 'main' if matrix_postmoogle_version == 'latest' else matrix_postmoogle_version }}"
+matrix_postmoogle_docker_src_files_path: "{{ matrix_base_data_path }}/postmoogle/docker-src"
+
+# renovate: datasource=docker depName=ghcr.io/etkecc/postmoogle
+matrix_postmoogle_version: v0.9.24
+matrix_postmoogle_docker_image: "{{ matrix_postmoogle_docker_image_name_prefix }}etkecc/postmoogle:{{ matrix_postmoogle_version }}"
+matrix_postmoogle_docker_image_name_prefix: "{{ 'localhost/' if matrix_postmoogle_container_image_self_build else 'ghcr.io/' }}"
+matrix_postmoogle_docker_image_force_pull: "{{ matrix_postmoogle_docker_image.endswith(':latest') }}"
+
+matrix_postmoogle_base_path: "{{ matrix_base_data_path }}/postmoogle"
+matrix_postmoogle_config_path: "{{ matrix_postmoogle_base_path }}/config"
+matrix_postmoogle_data_path: "{{ matrix_postmoogle_base_path }}/data"
+
+matrix_postmoogle_container_network: ""
+
+matrix_postmoogle_container_additional_networks: "{{ matrix_postmoogle_container_additional_networks_auto + matrix_postmoogle_container_additional_networks_custom }}"
+matrix_postmoogle_container_additional_networks_auto: []
+matrix_postmoogle_container_additional_networks_custom: []
+
+# A list of extra arguments to pass to the container
+matrix_postmoogle_container_extra_arguments: []
+
+# List of systemd services that matrix-postmoogle.service depends on
+matrix_postmoogle_systemd_required_services_list: "{{ matrix_postmoogle_systemd_required_services_list_default + matrix_postmoogle_systemd_required_services_list_auto + matrix_postmoogle_systemd_required_services_list_custom }}"
+matrix_postmoogle_systemd_required_services_list_default: "{{ [devture_systemd_docker_base_docker_service_name] if devture_systemd_docker_base_docker_service_name else [] }}"
+matrix_postmoogle_systemd_required_services_list_auto: []
+matrix_postmoogle_systemd_required_services_list_custom: []
+
+# List of systemd services that matrix-postmoogle.service wants
+matrix_postmoogle_systemd_wanted_services_list: []
+
+# Database-related configuration fields.
+#
+# To use SQLite, stick to these defaults.
+#
+# To use Postgres:
+# - change the engine (`matrix_postmoogle_database_engine: 'postgres'`)
+# - adjust your database credentials via the `matrix_postmoogle_database_*` variables
+matrix_postmoogle_database_engine: 'sqlite'
+
+matrix_postmoogle_sqlite_database_path_local: "{{ matrix_postmoogle_data_path }}/bot.db"
+matrix_postmoogle_sqlite_database_path_in_container: "/data/bot.db"
+
+matrix_postmoogle_database_username: 'postmoogle'
+matrix_postmoogle_database_password: 'some-password'
+matrix_postmoogle_database_hostname: ''
+matrix_postmoogle_database_port: 5432
+matrix_postmoogle_database_name: 'postmoogle'
+matrix_postmoogle_database_sslmode: disable
+
+matrix_postmoogle_database_connection_string: 'postgres://{{ matrix_postmoogle_database_username }}:{{ matrix_postmoogle_database_password }}@{{ matrix_postmoogle_database_hostname }}:{{ matrix_postmoogle_database_port }}/{{ matrix_postmoogle_database_name }}?sslmode={{ matrix_postmoogle_database_sslmode }}'
+
+matrix_postmoogle_storage_database: "{{
+	{
+		'sqlite': matrix_postmoogle_sqlite_database_path_in_container,
+		'postgres': matrix_postmoogle_database_connection_string,
+	}[matrix_postmoogle_database_engine]
+}}"
+
+matrix_postmoogle_database_dialect: "{{
+  {
+    'sqlite': 'sqlite3',
+    'postgres': 'postgres',
+  }[matrix_postmoogle_database_engine]
+}}"
+
+
+# The bot's username. This user needs to be created manually beforehand.
+# Also see `matrix_postmoogle_password` or `matrix_postmoogle_sharedsecret`
+matrix_postmoogle_login: "postmoogle"
+
+# The password that the bot uses to authenticate.
+matrix_postmoogle_password: ''
+
+# Alternative to password - shared secret requires matrix_postmoogle_login to be MXID
+matrix_postmoogle_sharedsecret: ''
+
+matrix_postmoogle_homeserver: ""
+
+# Command prefix
+matrix_postmoogle_prefix: '!pm'
+
+# Max email size in megabytes, including attachments
+matrix_postmoogle_maxsize: '1024'
+
+# Optional SMTP relay mode
+matrix_postmoogle_relay_host: ''
+matrix_postmoogle_relay_port: ''
+matrix_postmoogle_relay_username: ''
+matrix_postmoogle_relay_password: ''
+
+# A list of admins
+# Example set of rules:
+# matrix_postmoogle_admins:
+# - '@alice:example.com'
+# - '@bob:example.com'
+# - '@bot.*:example.com'
+# - '@*:example.net'
+matrix_postmoogle_admins: "{{ [matrix_admin] if matrix_admin else [] }}"
+
+# Sentry DSN. Deprecated, use matrix_postmoogle_monitoring_sentry_dsn
+matrix_postmoogle_sentry: ''
+
+# Sentry integration
+matrix_postmoogle_monitoring_sentry_dsn: "{{ matrix_postmoogle_sentry }}"
+matrix_postmoogle_monitoring_sentry_rate: 20
+
+# healthchecks.io integration
+matrix_postmoogle_monitoring_healthchecks_uuid: ''
+matrix_postmoogle_monitoring_healthchecks_duration: 60
+
+# Log level
+matrix_postmoogle_loglevel: 'INFO'
+
+# deprecated, use matrix_postmoogle_domains
+matrix_postmoogle_domain: "{{ matrix_server_fqn_matrix }}"
+
+matrix_postmoogle_domains:
+  - "{{ matrix_postmoogle_domain }}"  # backward compatibility
+
+# Password (passphrase) to encrypt account data
+matrix_postmoogle_data_secret: ""
+
+# in-container ports
+matrix_postmoogle_port: '2525'
+matrix_postmoogle_tls_port: '25587'
+
+# on-host ports
+matrix_postmoogle_smtp_host_bind_port: '25'
+matrix_postmoogle_submission_host_bind_port: '587'
+
+### SSL
+## on-host SSL dir
+matrix_postmoogle_ssl_path: ""
+
+## in-container SSL paths
+# matrix_postmoogle_tls_cert is the SSL certificates' certificates.
+# This var is likely set via group_vars/matrix_servers, so you don't need to set certs manually.
+# If you do need to set it manually, note that this is an in-container path.
+# To mount a certificates volumes into the container, use matrix_postmoogle_ssl_path
+# Example value: /ssl/live/{{ matrix_postmoogle_domain }}/fullchain.pem
+matrix_postmoogle_tls_cert: ""
+
+# matrix_postmoogle_tls_key is the SSL certificates' keys.
+# This var is likely set via group_vars/matrix_servers, so you don't need to set keys manually.
+# If you do need to set it manually, note that this is an in-container path.
+# To mount a certificates volumes into the container, use matrix_postmoogle_ssl_path
+# Example value: /ssl/live/{{ matrix_postmoogle_domain }}/privkey.pem
+matrix_postmoogle_tls_key: ""
+
+# Mandatory TLS, even on plain SMTP port
+matrix_postmoogle_tls_required: false
+
+# trusted proxies
+matrix_postmoogle_proxies: []
+
+# known forwarders
+matrix_postmoogle_mailboxes_forwarded: []
+
+# reserved mailboxes
+matrix_postmoogle_mailboxes_reserved: []
+
+# mailbox activation flow
+matrix_postmoogle_mailboxes_activation: none
+
+# Additional environment variables to pass to the postmoogle container
+#
+# Example:
+# matrix_postmoogle_environment_variables_extension: |
+#   postmoogle_TEXT_DONE=Done
+matrix_postmoogle_environment_variables_extension: ''
diff --git a/roles/custom/matrix-bot-postmoogle/tasks/main.yml b/roles/custom/matrix-bridge-postmoogle/tasks/main.yml
similarity index 58%
rename from roles/custom/matrix-bot-postmoogle/tasks/main.yml
rename to roles/custom/matrix-bridge-postmoogle/tasks/main.yml
index b77040392..0b4dbc60b 100644
--- a/roles/custom/matrix-bot-postmoogle/tasks/main.yml
+++ b/roles/custom/matrix-bridge-postmoogle/tasks/main.yml
@@ -2,19 +2,19 @@
 
 - tags:
     - setup-all
-    - setup-bot-postmoogle
+    - setup-postmoogle
     - install-all
-    - install-bot-postmoogle
+    - install-postmoogle
   block:
-    - when: matrix_bot_postmoogle_enabled | bool
+    - when: matrix_postmoogle_enabled | bool
       ansible.builtin.include_tasks: "{{ role_path }}/tasks/validate_config.yml"
 
-    - when: matrix_bot_postmoogle_enabled | bool
+    - when: matrix_postmoogle_enabled | bool
       ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_install.yml"
 
 - tags:
     - setup-all
-    - setup-bot-postmoogle
+    - setup-postmoogle
   block:
-    - when: not matrix_bot_postmoogle_enabled | bool
+    - when: not matrix_postmoogle_enabled | bool
       ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_uninstall.yml"
diff --git a/roles/custom/matrix-bridge-postmoogle/tasks/setup_install.yml b/roles/custom/matrix-bridge-postmoogle/tasks/setup_install.yml
new file mode 100644
index 000000000..61a8e7873
--- /dev/null
+++ b/roles/custom/matrix-bridge-postmoogle/tasks/setup_install.yml
@@ -0,0 +1,119 @@
+---
+
+# Check and remove the legacy systemd service (`matrix-bot-postmoogle.service`).
+# This role uses `matrix-postmoogle.service` now.
+# Related to: https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3698
+
+- name: Check if matrix-bot-postmoogle.service exists
+  ansible.builtin.stat:
+    path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-bot-postmoogle.service"
+  register: matrix_bot_postmoogle_service_stat
+
+- name: Stop and remove legacy matrix-bot-postmoogle systemd service
+  when: matrix_bot_postmoogle_service_stat.stat.exists | bool
+  block:
+    - name: Ensure legacy matrix-bot-postmoogle service is stopped
+      ansible.builtin.service:
+        name: matrix-bot-postmoogle
+        state: stopped
+        enabled: false
+      failed_when: false
+
+    - name: Remove legacy matrix-bot-postmoogle service file
+      ansible.builtin.file:
+        path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-bot-postmoogle.service"
+        state: absent
+
+- when: "matrix_postmoogle_database_engine == 'postgres'"
+  block:
+    - name: Check if an SQLite database already exists
+      ansible.builtin.stat:
+        path: "{{ matrix_postmoogle_sqlite_database_path_local }}"
+      register: matrix_postmoogle_sqlite_database_path_local_stat_result
+
+    - when: "matrix_postmoogle_sqlite_database_path_local_stat_result.stat.exists | bool"
+      block:
+        - ansible.builtin.include_role:
+            name: galaxy/postgres
+            tasks_from: migrate_db_to_postgres
+          vars:
+            postgres_db_migration_request:
+              src: "{{ matrix_postmoogle_sqlite_database_path_local }}"
+              dst: "{{ matrix_postmoogle_database_connection_string }}"
+              caller: "{{ role_path | basename }}"
+              engine_variable_name: 'matrix_postmoogle_database_engine'
+              engine_old: 'sqlite'
+              systemd_services_to_stop: ['matrix-postmoogle.service']
+
+        - ansible.builtin.set_fact:
+            matrix_postmoogle_requires_restart: true
+
+- name: Ensure postmoogle paths exist
+  ansible.builtin.file:
+    path: "{{ item.path }}"
+    state: directory
+    mode: 0750
+    owner: "{{ matrix_user_username }}"
+    group: "{{ matrix_user_groupname }}"
+  with_items:
+    - {path: "{{ matrix_postmoogle_config_path }}", when: true}
+    - {path: "{{ matrix_postmoogle_data_path }}", when: true}
+    - {path: "{{ matrix_postmoogle_docker_src_files_path }}", when: matrix_postmoogle_container_image_self_build}
+  when: "item.when | bool"
+
+- name: Ensure postmoogle environment variables file created
+  ansible.builtin.template:
+    src: "{{ role_path }}/templates/env.j2"
+    dest: "{{ matrix_postmoogle_config_path }}/env"
+    owner: "{{ matrix_user_username }}"
+    group: "{{ matrix_user_groupname }}"
+    mode: 0640
+
+- name: Ensure postmoogle image is pulled
+  community.docker.docker_image:
+    name: "{{ matrix_postmoogle_docker_image }}"
+    source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}"
+    force_source: "{{ matrix_postmoogle_docker_image_force_pull if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}"
+    force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_postmoogle_docker_image_force_pull }}"
+  when: "not matrix_postmoogle_container_image_self_build | bool"
+  register: result
+  retries: "{{ devture_playbook_help_container_retries_count }}"
+  delay: "{{ devture_playbook_help_container_retries_delay }}"
+  until: result is not failed
+
+- name: Ensure postmoogle repository is present on self-build
+  ansible.builtin.git:
+    repo: "{{ matrix_postmoogle_docker_repo }}"
+    version: "{{ matrix_postmoogle_docker_repo_version }}"
+    dest: "{{ matrix_postmoogle_docker_src_files_path }}"
+    force: "yes"
+  become: true
+  become_user: "{{ matrix_user_username }}"
+  register: matrix_postmoogle_git_pull_results
+  when: "matrix_postmoogle_container_image_self_build | bool"
+
+- name: Ensure postmoogle image is built
+  community.docker.docker_image:
+    name: "{{ matrix_postmoogle_docker_image }}"
+    source: build
+    force_source: "{{ matrix_postmoogle_git_pull_results.changed if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}"
+    force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_postmoogle_git_pull_results.changed }}"
+    build:
+      dockerfile: Dockerfile
+      path: "{{ matrix_postmoogle_docker_src_files_path }}"
+      pull: true
+  when: "matrix_postmoogle_container_image_self_build | bool"
+
+- name: Ensure postmoogle container network is created
+  community.general.docker_network:
+    enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}"
+    name: "{{ matrix_postmoogle_container_network }}"
+    driver: bridge
+    driver_options: "{{ devture_systemd_docker_base_container_networks_driver_options }}"
+
+- name: Ensure matrix-postmoogle.service installed
+  ansible.builtin.template:
+    src: "{{ role_path }}/templates/systemd/matrix-postmoogle.service.j2"
+    dest: "{{ devture_systemd_docker_base_systemd_path }}/matrix-postmoogle.service"
+    mode: 0644
+  register: matrix_postmoogle_systemd_service_result
diff --git a/roles/custom/matrix-bot-postmoogle/tasks/setup_uninstall.yml b/roles/custom/matrix-bridge-postmoogle/tasks/setup_uninstall.yml
similarity index 62%
rename from roles/custom/matrix-bot-postmoogle/tasks/setup_uninstall.yml
rename to roles/custom/matrix-bridge-postmoogle/tasks/setup_uninstall.yml
index 93e00dda2..28b243429 100644
--- a/roles/custom/matrix-bot-postmoogle/tasks/setup_uninstall.yml
+++ b/roles/custom/matrix-bridge-postmoogle/tasks/setup_uninstall.yml
@@ -2,24 +2,24 @@
 
 - name: Check existence of matrix-postmoogle service
   ansible.builtin.stat:
-    path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-bot-postmoogle.service"
-  register: matrix_bot_postmoogle_service_stat
+    path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-postmoogle.service"
+  register: matrix_postmoogle_service_stat
 
-- when: matrix_bot_postmoogle_service_stat.stat.exists | bool
+- when: matrix_postmoogle_service_stat.stat.exists | bool
   block:
     - name: Ensure matrix-postmoogle is stopped
       ansible.builtin.service:
-        name: matrix-bot-postmoogle
+        name: matrix-postmoogle
         state: stopped
         enabled: false
         daemon_reload: true
 
-    - name: Ensure matrix-bot-postmoogle.service doesn't exist
+    - name: Ensure matrix-postmoogle.service doesn't exist
       ansible.builtin.file:
-        path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-bot-postmoogle.service"
+        path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-postmoogle.service"
         state: absent
 
     - name: Ensure Matrix postmoogle paths don't exist
       ansible.builtin.file:
-        path: "{{ matrix_bot_postmoogle_base_path }}"
+        path: "{{ matrix_postmoogle_base_path }}"
         state: absent
diff --git a/roles/custom/matrix-bridge-postmoogle/tasks/validate_config.yml b/roles/custom/matrix-bridge-postmoogle/tasks/validate_config.yml
new file mode 100644
index 000000000..d486923d3
--- /dev/null
+++ b/roles/custom/matrix-bridge-postmoogle/tasks/validate_config.yml
@@ -0,0 +1,12 @@
+---
+
+- name: Fail if required Postmoogle settings not defined
+  ansible.builtin.fail:
+    msg: >-
+      You need to define a required configuration setting (`{{ item.name }}`).
+  when: "item.when | bool and vars[item.name] == ''"
+  with_items:
+    - {'name': 'matrix_postmoogle_password', when: true}
+    - {'name': 'matrix_postmoogle_container_network', when: true}
+    - {'name': 'matrix_postmoogle_homeserver', when: true}
+    - {'name': 'matrix_postmoogle_database_hostname', when: "{{ matrix_postmoogle_database_engine == 'postgres' }}"}
diff --git a/roles/custom/matrix-bridge-postmoogle/templates/env.j2 b/roles/custom/matrix-bridge-postmoogle/templates/env.j2
new file mode 100644
index 000000000..b56f88ae2
--- /dev/null
+++ b/roles/custom/matrix-bridge-postmoogle/templates/env.j2
@@ -0,0 +1,31 @@
+POSTMOOGLE_LOGIN={{ matrix_postmoogle_login }}
+POSTMOOGLE_PASSWORD={{ matrix_postmoogle_password }}
+POSTMOOGLE_SHAREDSECRET={{ matrix_postmoogle_sharedsecret }}
+POSTMOOGLE_HOMESERVER={{ matrix_postmoogle_homeserver }}
+POSTMOOGLE_DOMAINS={{ matrix_postmoogle_domains | join(' ') }}
+POSTMOOGLE_PORT={{ matrix_postmoogle_port }}
+POSTMOOGLE_DB_DSN={{ matrix_postmoogle_database_connection_string }}
+POSTMOOGLE_DB_DIALECT={{ matrix_postmoogle_database_dialect }}
+POSTMOOGLE_PREFIX={{ matrix_postmoogle_prefix }}
+POSTMOOGLE_MAXSIZE={{ matrix_postmoogle_maxsize }}
+POSTMOOGLE_LOGLEVEL={{ matrix_postmoogle_loglevel }}
+POSTMOOGLE_ADMINS={{ matrix_postmoogle_admins | join(' ') }}
+POSTMOOGLE_TLS_PORT={{ matrix_postmoogle_tls_port }}
+POSTMOOGLE_TLS_CERT={{ matrix_postmoogle_tls_cert }}
+POSTMOOGLE_TLS_KEY={{ matrix_postmoogle_tls_key }}
+POSTMOOGLE_TLS_REQUIRED={{ matrix_postmoogle_tls_required }}
+POSTMOOGLE_DATA_SECRET={{ matrix_postmoogle_data_secret }}
+POSTMOOGLE_PROXIES={{ matrix_postmoogle_proxies | join(' ') }}
+POSTMOOGLE_RELAY_HOST={{ matrix_postmoogle_relay_host }}
+POSTMOOGLE_RELAY_PORT={{ matrix_postmoogle_relay_port }}
+POSTMOOGLE_RELAY_USERNAME={{ matrix_postmoogle_relay_username }}
+POSTMOOGLE_RELAY_PASSWORD={{ matrix_postmoogle_relay_password }}
+POSTMOOGLE_MONITORING_SENTRY_DSN={{ matrix_postmoogle_monitoring_sentry_dsn }}
+POSTMOOGLE_MONITORING_SENTRY_RATE={{ matrix_postmoogle_monitoring_sentry_rate }}
+POSTMOOGLE_MONITORING_HEALTHCHECKS_UUID={{ matrix_postmoogle_monitoring_healthchecks_uuid }}
+POSTMOOGLE_MONITORING_HEALTHCHECKS_DURATION={{ matrix_postmoogle_monitoring_healthchecks_duration }}
+POSTMOOGLE_MAILBOXES_FORWARDED={{ matrix_postmoogle_mailboxes_forwarded | join(' ') }}
+POSTMOOGLE_MAILBOXES_RESERVED={{ matrix_postmoogle_mailboxes_reserved | join(' ') }}
+POSTMOOGLE_MAILBOXES_ACTIVATION={{ matrix_postmoogle_mailboxes_activation }}
+
+{{ matrix_postmoogle_environment_variables_extension }}
diff --git a/roles/custom/matrix-bot-postmoogle/templates/systemd/matrix-bot-postmoogle.service.j2 b/roles/custom/matrix-bridge-postmoogle/templates/systemd/matrix-postmoogle.service.j2
similarity index 52%
rename from roles/custom/matrix-bot-postmoogle/templates/systemd/matrix-bot-postmoogle.service.j2
rename to roles/custom/matrix-bridge-postmoogle/templates/systemd/matrix-postmoogle.service.j2
index 4f6d0ced2..fa4c1bf36 100644
--- a/roles/custom/matrix-bot-postmoogle/templates/systemd/matrix-bot-postmoogle.service.j2
+++ b/roles/custom/matrix-bridge-postmoogle/templates/systemd/matrix-postmoogle.service.j2
@@ -1,11 +1,11 @@
 #jinja2: lstrip_blocks: "True"
 [Unit]
-Description=Matrix Postmoogle bot
-{% for service in matrix_bot_postmoogle_systemd_required_services_list %}
+Description=Matrix Postmoogle bridge
+{% for service in matrix_postmoogle_systemd_required_services_list %}
 Requires={{ service }}
 After={{ service }}
 {% endfor %}
-{% for service in matrix_bot_postmoogle_systemd_wanted_services_list %}
+{% for service in matrix_postmoogle_systemd_wanted_services_list %}
 Wants={{ service }}
 {% endfor %}
 DefaultDependencies=no
@@ -13,42 +13,42 @@ DefaultDependencies=no
 [Service]
 Type=simple
 Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}"
-ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-postmoogle 2>/dev/null || true'
-ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-postmoogle 2>/dev/null || true'
+ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-postmoogle 2>/dev/null || true'
+ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-postmoogle 2>/dev/null || true'
 
 ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \
 			--rm \
-			--name=matrix-bot-postmoogle \
+			--name=matrix-postmoogle \
 			--log-driver=none \
 			--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
 			--cap-drop=ALL \
 			--read-only \
-			--network={{ matrix_bot_postmoogle_container_network }} \
-			--env-file={{ matrix_bot_postmoogle_config_path }}/env \
-			-p {{ matrix_bot_postmoogle_smtp_host_bind_port }}:{{ matrix_bot_postmoogle_port }} \
-			{% if matrix_bot_postmoogle_ssl_path %}
-			-p {{ matrix_bot_postmoogle_submission_host_bind_port }}:{{ matrix_bot_postmoogle_tls_port }} \
+			--network={{ matrix_postmoogle_container_network }} \
+			--env-file={{ matrix_postmoogle_config_path }}/env \
+			-p {{ matrix_postmoogle_smtp_host_bind_port }}:{{ matrix_postmoogle_port }} \
+			{% if matrix_postmoogle_ssl_path %}
+			-p {{ matrix_postmoogle_submission_host_bind_port }}:{{ matrix_postmoogle_tls_port }} \
 			{% endif %}
-			--mount type=bind,src={{ matrix_bot_postmoogle_data_path }},dst=/data \
-			{% if matrix_bot_postmoogle_ssl_path %}
-			--mount type=bind,src={{ matrix_bot_postmoogle_ssl_path }},dst=/ssl \
+			--mount type=bind,src={{ matrix_postmoogle_data_path }},dst=/data \
+			{% if matrix_postmoogle_ssl_path %}
+			--mount type=bind,src={{ matrix_postmoogle_ssl_path }},dst=/ssl \
 			{% endif %}
-			{% for arg in matrix_bot_postmoogle_container_extra_arguments %}
+			{% for arg in matrix_postmoogle_container_extra_arguments %}
 			{{ arg }} \
 			{% endfor %}
-			{{ matrix_bot_postmoogle_docker_image }}
+			{{ matrix_postmoogle_docker_image }}
 
-{% for network in matrix_bot_postmoogle_container_additional_networks %}
-ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network connect {{ network }} matrix-bot-postmoogle
+{% for network in matrix_postmoogle_container_additional_networks %}
+ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network connect {{ network }} matrix-postmoogle
 {% endfor %}
 
-ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-bot-postmoogle
+ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-postmoogle
 
-ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-bot-postmoogle 2>/dev/null || true'
-ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-bot-postmoogle 2>/dev/null || true'
+ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-postmoogle 2>/dev/null || true'
+ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-postmoogle 2>/dev/null || true'
 Restart=always
 RestartSec=30
-SyslogIdentifier=matrix-bot-postmoogle
+SyslogIdentifier=matrix-postmoogle
 
 [Install]
 WantedBy=multi-user.target
diff --git a/roles/custom/matrix-cactus-comments-client/defaults/main.yml b/roles/custom/matrix-cactus-comments-client/defaults/main.yml
index f044a0cc8..6a43ba585 100644
--- a/roles/custom/matrix-cactus-comments-client/defaults/main.yml
+++ b/roles/custom/matrix-cactus-comments-client/defaults/main.yml
@@ -13,7 +13,7 @@ matrix_cactus_comments_client_public_path: "{{ matrix_cactus_comments_client_bas
 matrix_cactus_comments_client_public_path_file_permissions: "0644"
 
 # renovate: datasource=docker depName=joseluisq/static-web-server
-matrix_cactus_comments_client_version: 2.33.0
+matrix_cactus_comments_client_version: 2.35.0
 
 matrix_cactus_comments_client_container_image: "{{ matrix_container_global_registry_prefix }}joseluisq/static-web-server:{{ matrix_cactus_comments_client_container_image_tag }}"
 matrix_cactus_comments_client_container_image_tag: "{{ 'latest' if matrix_cactus_comments_client_version == 'latest' else (matrix_cactus_comments_client_version + '-alpine') }}"
diff --git a/roles/custom/matrix-client-cinny/defaults/main.yml b/roles/custom/matrix-client-cinny/defaults/main.yml
index d48cdcf9c..86e5d9ef9 100644
--- a/roles/custom/matrix-client-cinny/defaults/main.yml
+++ b/roles/custom/matrix-client-cinny/defaults/main.yml
@@ -7,7 +7,7 @@ matrix_client_cinny_container_image_self_build: false
 matrix_client_cinny_container_image_self_build_repo: "https://github.com/ajbura/cinny.git"
 
 # renovate: datasource=docker depName=ajbura/cinny
-matrix_client_cinny_version: v4.2.2
+matrix_client_cinny_version: v4.2.3
 matrix_client_cinny_docker_image: "{{ matrix_client_cinny_docker_image_name_prefix }}ajbura/cinny:{{ matrix_client_cinny_version }}"
 matrix_client_cinny_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_cinny_container_image_self_build else matrix_container_global_registry_prefix }}"
 matrix_client_cinny_docker_image_force_pull: "{{ matrix_client_cinny_docker_image.endswith(':latest') }}"
@@ -44,6 +44,11 @@ matrix_client_cinny_container_labels_traefik_entrypoints: web-secure
 matrix_client_cinny_container_labels_traefik_tls: "{{ matrix_client_cinny_container_labels_traefik_entrypoints != 'web' }}"
 matrix_client_cinny_container_labels_traefik_tls_certResolver: default  # noqa var-naming
 
+# Controls whether a compression middleware will be injected into the middlewares list.
+# This compression middleware is supposed to be defined elsewhere (using labels or a File provider, etc.) and is merely referenced by this router.
+matrix_client_cinny_container_labels_traefik_compression_middleware_enabled: false
+matrix_client_cinny_container_labels_traefik_compression_middleware_name: ""
+
 # Controls which additional headers to attach to all HTTP responses.
 # To add your own headers, use `matrix_client_cinny_container_labels_traefik_additional_response_headers_custom`
 matrix_client_cinny_container_labels_traefik_additional_response_headers: "{{ matrix_client_cinny_container_labels_traefik_additional_response_headers_auto | combine(matrix_client_cinny_container_labels_traefik_additional_response_headers_custom) }}"
@@ -138,9 +143,31 @@ matrix_client_cinny_path_prefix: /
 # Controls whether the self-check feature should validate SSL certificates.
 matrix_client_cinny_self_check_validate_certificates: true
 
-# config.json
+# Default homeserver URL to use in the `config.json` file.
+# See `matrix_client_cinny_config_homeserverList`.
 matrix_client_cinny_default_hs_url: ""
 
+# Controls the `defaultHomeserver` value in the `config.json` file.
+matrix_client_cinny_config_defaultHomeserver: 0  # noqa var-naming
+
+# Controls the `homeserverList` value in the `config.json` file.
+matrix_client_cinny_config_homeserverList: "{{ [matrix_client_cinny_default_hs_url] }}"  # noqa var-naming
+
+# Controls the `allowCustomHomeservers` value in the `config.json` file.
+matrix_client_cinny_config_allowCustomHomeservers: true  # noqa var-naming
+
+# Controls the `featuredCommunities.spaces` value in the `config.json` file.
+matrix_client_cinny_config_featuredCommunities_spaces: []  # noqa var-naming
+
+# Controls the `featuredCommunities.rooms` value in the `config.json` file.
+matrix_client_cinny_config_featuredCommunities_rooms: []  # noqa var-naming
+
+# Controls the `featuredCommunities.servers` value in the `config.json` file.
+matrix_client_cinny_config_featuredCommunities_servers: ["matrix.org"]  # noqa var-naming
+
+# Controls the `featuredCommunities.openAsDefault` value in the `config.json` file.
+matrix_client_cinny_config_featuredCommunities_openAsDefault: false  # noqa var-naming
+
 # Default Cinny configuration template which covers the generic use case.
 # You can customize it by controlling the various variables inside it.
 #
diff --git a/roles/custom/matrix-client-cinny/tasks/validate_config.yml b/roles/custom/matrix-client-cinny/tasks/validate_config.yml
index a6d7a9958..7a7ee2dfe 100644
--- a/roles/custom/matrix-client-cinny/tasks/validate_config.yml
+++ b/roles/custom/matrix-client-cinny/tasks/validate_config.yml
@@ -3,10 +3,19 @@
   ansible.builtin.fail:
     msg: >
       You need to define a required configuration setting (`{{ item }}`) to use Cinny.
-  when: "vars[item] == '' or vars[item] is none"
+  when: "item.when | bool and vars[item.name] == ''"
   with_items:
-    - matrix_client_cinny_default_hs_url
-    - matrix_client_cinny_container_network
+    - {'name': 'matrix_client_cinny_default_hs_url', when: true}
+    - {'name': 'matrix_client_cinny_container_network', when: true}
+    - {'name': 'matrix_client_cinny_container_labels_traefik_compression_middleware_name', when: "{{ matrix_client_cinny_container_labels_traefik_compression_middleware_enabled }}"}
+
+- name: Fail if matrix_client_cinny_path_prefix is not /
+  ansible.builtin.fail:
+    msg: >-
+      `matrix_client_cinny_path_prefix` is set to `{{ matrix_client_cinny_path_prefix }}` in your configuration, but Cinny no longer supports hosting under a path prefix without an application rebuild.
+      Consider removing your `matrix_client_cinny_path_prefix` override and adjusting the Cinny hostname via `matrix_server_fqn_cinny` or `matrix_client_cinny_hostname`.
+      See https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701
+  when: "matrix_client_cinny_path_prefix != '/'"
 
 - when: matrix_client_cinny_container_labels_traefik_enabled | bool
   block:
diff --git a/roles/custom/matrix-client-cinny/templates/config.json.j2 b/roles/custom/matrix-client-cinny/templates/config.json.j2
index 0da710acc..6c2b14313 100644
--- a/roles/custom/matrix-client-cinny/templates/config.json.j2
+++ b/roles/custom/matrix-client-cinny/templates/config.json.j2
@@ -1,6 +1,11 @@
 {
-  "defaultHomeserver": 0,
-  "homeserverList": [
-    {{ matrix_client_cinny_default_hs_url | string|to_json }}
-  ]
+  "defaultHomeserver": {{ matrix_client_cinny_config_defaultHomeserver | to_json }},
+  "homeserverList": {{ matrix_client_cinny_config_homeserverList | to_json }},
+  "allowCustomHomeservers": {{ matrix_client_cinny_config_allowCustomHomeservers | to_json }},
+  "featuredCommunities": {
+    "spaces": {{ matrix_client_cinny_config_featuredCommunities_spaces | to_json }},
+    "rooms": {{ matrix_client_cinny_config_featuredCommunities_rooms | to_json }},
+    "servers": {{ matrix_client_cinny_config_featuredCommunities_servers | to_json }},
+    "openAsDefault": {{ matrix_client_cinny_config_featuredCommunities_openAsDefault | to_json }}
+  }
 }
diff --git a/roles/custom/matrix-client-cinny/templates/labels.j2 b/roles/custom/matrix-client-cinny/templates/labels.j2
index ede967226..e18e804c0 100644
--- a/roles/custom/matrix-client-cinny/templates/labels.j2
+++ b/roles/custom/matrix-client-cinny/templates/labels.j2
@@ -9,6 +9,10 @@ traefik.http.services.matrix-client-cinny.loadbalancer.server.port=8080
 
 {% set middlewares = [] %}
 
+{% if matrix_client_cinny_container_labels_traefik_compression_middleware_enabled %}
+{% set middlewares = middlewares + [matrix_client_cinny_container_labels_traefik_compression_middleware_name] %}
+{% endif %}
+
 {% if matrix_client_cinny_container_labels_traefik_path_prefix != '/' %}
 traefik.http.middlewares.matrix-client-cinny-slashless-redirect.redirectregex.regex=({{ matrix_client_cinny_container_labels_traefik_path_prefix | quote }})$
 traefik.http.middlewares.matrix-client-cinny-slashless-redirect.redirectregex.replacement=${1}/
diff --git a/roles/custom/matrix-client-element/defaults/main.yml b/roles/custom/matrix-client-element/defaults/main.yml
index f3f23ff44..8f4e9cb67 100644
--- a/roles/custom/matrix-client-element/defaults/main.yml
+++ b/roles/custom/matrix-client-element/defaults/main.yml
@@ -11,7 +11,7 @@ matrix_client_element_container_image_self_build_repo: "https://github.com/eleme
 matrix_client_element_container_image_self_build_low_memory_system_patch_enabled: "{{ ansible_memtotal_mb < 4096 }}"
 
 # renovate: datasource=docker depName=vectorim/element-web
-matrix_client_element_version: v1.11.82
+matrix_client_element_version: v1.11.90
 
 matrix_client_element_docker_image: "{{ matrix_client_element_docker_image_name_prefix }}vectorim/element-web:{{ matrix_client_element_version }}"
 matrix_client_element_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_element_container_image_self_build else matrix_container_global_registry_prefix }}"
@@ -48,6 +48,11 @@ matrix_client_element_container_labels_traefik_entrypoints: web-secure
 matrix_client_element_container_labels_traefik_tls: "{{ matrix_client_element_container_labels_traefik_entrypoints != 'web' }}"
 matrix_client_element_container_labels_traefik_tls_certResolver: default  # noqa var-naming
 
+# Controls whether a compression middleware will be injected into the middlewares list.
+# This compression middleware is supposed to be defined elsewhere (using labels or a File provider, etc.) and is merely referenced by this router.
+matrix_client_element_container_labels_traefik_compression_middleware_enabled: false
+matrix_client_element_container_labels_traefik_compression_middleware_name: ""
+
 # Controls which additional headers to attach to all HTTP responses.
 # To add your own headers, use `matrix_client_element_container_labels_traefik_additional_response_headers_custom`
 matrix_client_element_container_labels_traefik_additional_response_headers: "{{ matrix_client_element_container_labels_traefik_additional_response_headers_auto | combine(matrix_client_element_container_labels_traefik_additional_response_headers_custom) }}"
@@ -130,14 +135,14 @@ matrix_client_element_floc_optout_enabled: true
 matrix_client_element_hsts_preload_enabled: false
 
 matrix_client_element_scheme: https
-# The hostname at which Element is served.
+# The hostname at which Element Web is served.
 matrix_client_element_hostname: "{{ matrix_server_fqn_element }}"
 
-# The path at which Element is exposed.
+# The path at which Element Web is exposed.
 # This value must either be `/` or not end with a slash (e.g. `/element`).
 matrix_client_element_path_prefix: /
 
-# Element config.json customizations
+# Element Web config.json customizations
 matrix_client_element_default_server_name: "{{ matrix_domain }}"
 matrix_client_element_default_hs_url: ""
 matrix_client_element_default_is_url: ~
@@ -177,7 +182,7 @@ matrix_client_element_branding_welcome_background_url: ~  # noqa var-naming
 
 matrix_client_element_page_template_welcome_path: "{{ role_path }}/templates/welcome.html.j2"
 
-# By default, there's no Element homepage (when logged in). If you wish to have one,
+# By default, there's no Element Web homepage (when logged in). If you wish to have one,
 # point this to a `home.html` template file on your local filesystem.
 matrix_client_element_embedded_pages_home_path: ~
 
@@ -195,7 +200,7 @@ matrix_client_element_default_country_code: "GB"
 # Controls whether presence will be enabled
 matrix_client_element_enable_presence_by_hs_url: ~
 
-# Controls whether custom Element themes will be installed.
+# Controls whether custom Element Web themes will be installed.
 # When enabled, all themes found in the `matrix_client_element_themes_repository_url` repository
 # will be installed and enabled automatically.
 matrix_client_element_themes_enabled: false
@@ -205,16 +210,16 @@ matrix_client_element_themes_repository_version: master
 # Controls the default theme
 matrix_client_element_default_theme: 'light'
 
-# Controls the `setting_defaults.custom_themes` setting of the Element configuration.
+# Controls the `setting_defaults.custom_themes` setting of the Element Web configuration.
 # You can use this setting to define custom themes.
 #
 # Also, look at `matrix_client_element_themes_enabled` for a way to pull in a bunch of custom themes automatically.
 # If you define your own themes here and set `matrix_client_element_themes_enabled: true`, your themes will be preserved as well.
 #
-# Note that for a custom theme to work well, all Element instances that you use must have the same theme installed.
+# Note that for a custom theme to work well, all Element Web instances that you use must have the same theme installed.
 matrix_client_element_setting_defaults_custom_themes: []  # noqa var-naming
 
-# Default Element configuration template which covers the generic use case.
+# Default Element Web configuration template which covers the generic use case.
 # You can customize it by controlling the various variables inside it.
 #
 # For a more advanced customization, you can extend the default (see `matrix_client_element_configuration_extension_json`)
@@ -224,7 +229,7 @@ matrix_client_element_setting_defaults_custom_themes: []  # noqa var-naming
 # This is unlike what it does when looking up YAML template files (no automatic parsing there).
 matrix_client_element_configuration_default: "{{ lookup('template', 'templates/config.json.j2') }}"
 
-# Your custom JSON configuration for Element should go to `matrix_client_element_configuration_extension_json`.
+# Your custom JSON configuration for Element Web should go to `matrix_client_element_configuration_extension_json`.
 # This configuration extends the default starting configuration (`matrix_client_element_configuration_default`).
 #
 # You can override individual variables from the default configuration, or introduce new ones.
@@ -243,7 +248,7 @@ matrix_client_element_configuration_extension_json: '{}'
 
 matrix_client_element_configuration_extension: "{{ matrix_client_element_configuration_extension_json | from_json if matrix_client_element_configuration_extension_json | from_json is mapping else {} }}"
 
-# Holds the final Element configuration (a combination of the default and its extension).
+# Holds the final Element Web configuration (a combination of the default and its extension).
 # You most likely don't need to touch this variable. Instead, see `matrix_client_element_configuration_default`.
 matrix_client_element_configuration: "{{ matrix_client_element_configuration_default | combine(matrix_client_element_configuration_extension, recursive=True) }}"
 
@@ -313,3 +318,7 @@ matrix_client_element_location_sharing_map_style_content_sources_localsource_til
 # matrix_client_element_location_sharing_map_style_content_sources_localsource_attribution: "&copy; <a href=\"https://www.openstreetmap.org/copyright\" target=\"_blank\">OpenStreetMap</a> contributors"
 # Leave blank, if map does not require attribution.
 matrix_client_element_location_sharing_map_style_content_sources_localsource_attribution: ""
+
+# Optional URL to redirect the user to after they have logged out.
+# See https://github.com/element-hq/element-web/blob/develop/docs/config.md#sso-setup
+matrix_client_element_logout_redirect_url: ''
diff --git a/roles/custom/matrix-client-element/tasks/prepare_themes.yml b/roles/custom/matrix-client-element/tasks/prepare_themes.yml
index 194335b2f..cb3bf2bd4 100644
--- a/roles/custom/matrix-client-element/tasks/prepare_themes.yml
+++ b/roles/custom/matrix-client-element/tasks/prepare_themes.yml
@@ -1,7 +1,7 @@
 ---
 
 #
-# Tasks related to setting up Element themes
+# Tasks related to setting up Element Web themes
 #
 
 - when: matrix_client_element_themes_enabled | bool
@@ -9,35 +9,35 @@
   delegate_to: 127.0.0.1
   become: false
   block:
-    - name: Ensure Element themes repository is pulled
+    - name: Ensure Element Web themes repository is pulled
       ansible.builtin.git:
         repo: "{{ matrix_client_element_themes_repository_url }}"
         version: "{{ matrix_client_element_themes_repository_version }}"
         dest: "{{ role_path }}/files/scratchpad/themes"
 
-    - name: Find all Element theme files
+    - name: Find all Element Web theme files
       ansible.builtin.find:
         paths: "{{ role_path }}/files/scratchpad/themes"
         patterns: "*.json"
         recurse: true
       register: matrix_client_element_theme_file_list
 
-    - name: Read Element theme
+    - name: Read Element Web theme
       ansible.builtin.slurp:
         path: "{{ item.path }}"
       register: "matrix_client_element_theme_file_contents"
       with_items: "{{ matrix_client_element_theme_file_list.files }}"
 
-    - name: Load Element theme
+    - name: Load Element Web theme
       ansible.builtin.set_fact:
         matrix_client_element_setting_defaults_custom_themes: "{{ matrix_client_element_setting_defaults_custom_themes + [item['content'] | b64decode | from_json] }}"  # noqa var-naming
       with_items: "{{ matrix_client_element_theme_file_contents.results }}"
 
 #
-# Tasks related to getting rid of Element themes (if it was previously enabled)
+# Tasks related to getting rid of Element Web themes (if it was previously enabled)
 #
 
-- name: Ensure Element themes repository is removed
+- name: Ensure Element Web themes repository is removed
   ansible.builtin.file:
     path: "{{ role_path }}/files/scratchpad/themes"
     state: absent
diff --git a/roles/custom/matrix-client-element/tasks/self_check.yml b/roles/custom/matrix-client-element/tasks/self_check.yml
index 619727b97..8a08d8d04 100644
--- a/roles/custom/matrix-client-element/tasks/self_check.yml
+++ b/roles/custom/matrix-client-element/tasks/self_check.yml
@@ -3,7 +3,7 @@
 - ansible.builtin.set_fact:
     matrix_client_element_url_endpoint_public: "{{ matrix_client_element_scheme }}://{{ matrix_client_element_hostname }}/config.json"
 
-- name: Check Element
+- name: Check Element Web
   ansible.builtin.uri:
     url: "{{ matrix_client_element_url_endpoint_public }}"
     follow_redirects: none
@@ -14,11 +14,11 @@
   delegate_to: 127.0.0.1
   become: false
 
-- name: Fail if Element not working
+- name: Fail if Element Web not working
   ansible.builtin.fail:
-    msg: "Failed checking Element is up at `{{ matrix_server_fqn_element }}` (checked endpoint: `{{ matrix_client_element_url_endpoint_public }}`). Is Element running? Is port 443 open in your firewall? Full error: {{ matrix_client_element_self_check_result }}"
+    msg: "Failed checking Element Web is up at `{{ matrix_server_fqn_element }}` (checked endpoint: `{{ matrix_client_element_url_endpoint_public }}`). Is Element Web running? Is port 443 open in your firewall? Full error: {{ matrix_client_element_self_check_result }}"
   when: "matrix_client_element_self_check_result.failed or 'json' not in matrix_client_element_self_check_result"
 
-- name: Report working Element
+- name: Report working Element Web
   ansible.builtin.debug:
-    msg: "Element at `{{ matrix_server_fqn_element }}` is working (checked endpoint: `{{ matrix_client_element_url_endpoint_public }}`)"
+    msg: "Element Web at `{{ matrix_server_fqn_element }}` is working (checked endpoint: `{{ matrix_client_element_url_endpoint_public }}`)"
diff --git a/roles/custom/matrix-client-element/tasks/setup_install.yml b/roles/custom/matrix-client-element/tasks/setup_install.yml
index 974e3d421..e528faa8b 100644
--- a/roles/custom/matrix-client-element/tasks/setup_install.yml
+++ b/roles/custom/matrix-client-element/tasks/setup_install.yml
@@ -1,6 +1,6 @@
 ---
 
-- name: Ensure Element paths exists
+- name: Ensure Element Web paths exists
   ansible.builtin.file:
     path: "{{ item.path }}"
     state: directory
@@ -12,7 +12,7 @@
     - {path: "{{ matrix_client_element_docker_src_files_path }}", when: "{{ matrix_client_element_container_image_self_build }}"}
   when: "item.when | bool"
 
-- name: Ensure Element Docker image is pulled
+- name: Ensure Element Web Docker image is pulled
   community.docker.docker_image:
     name: "{{ matrix_client_element_docker_image }}"
     source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}"
@@ -24,7 +24,7 @@
   delay: "{{ devture_playbook_help_container_retries_delay }}"
   until: result is not failed
 
-- name: Ensure Element repository is present on self-build
+- name: Ensure Element Web repository is present on self-build
   ansible.builtin.git:
     repo: "{{ matrix_client_element_container_image_self_build_repo }}"
     dest: "{{ matrix_client_element_docker_src_files_path }}"
@@ -49,7 +49,7 @@
     mode: '0644'
   when: "matrix_client_element_container_image_self_build | bool and matrix_client_element_container_image_self_build_low_memory_system_patch_enabled | bool"
 
-- name: Ensure Element Docker image is built
+- name: Ensure Element Web Docker image is built
   ansible.builtin.command:
     cmd: |-
       {{ devture_systemd_docker_base_host_command_docker }} buildx build
@@ -59,7 +59,7 @@
   changed_when: true
   when: matrix_client_element_container_image_self_build | bool
 
-- name: Ensure Element configuration installed
+- name: Ensure Element Web configuration installed
   ansible.builtin.copy:
     content: "{{ matrix_client_element_configuration | to_nice_json }}"
     dest: "{{ matrix_client_element_data_path }}/config.json"
@@ -76,7 +76,7 @@
     owner: "{{ matrix_user_username }}"
     group: "{{ matrix_user_groupname }}"
 
-- name: Ensure Element config files installed
+- name: Ensure Element Web config files installed
   ansible.builtin.template:
     src: "{{ item.src }}"
     dest: "{{ matrix_client_element_data_path }}/{{ item.name }}"
@@ -90,7 +90,7 @@
     - {src: "{{ matrix_client_element_embedded_pages_home_path }}", name: "home.html"}
   when: "item.src is not none"
 
-- name: Ensure Element config files removed
+- name: Ensure Element Web config files removed
   ansible.builtin.file:
     path: "{{ matrix_client_element_data_path }}/{{ item.name }}"
     state: absent
@@ -98,7 +98,7 @@
     - {src: "{{ matrix_client_element_embedded_pages_home_path }}", name: "home.html"}
   when: "item.src is none"
 
-- name: Ensure Element container network is created
+- name: Ensure Element Web container network is created
   community.general.docker_network:
     enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}"
     name: "{{ matrix_client_element_container_network }}"
diff --git a/roles/custom/matrix-client-element/tasks/setup_uninstall.yml b/roles/custom/matrix-client-element/tasks/setup_uninstall.yml
index e0930cc11..279dd8166 100644
--- a/roles/custom/matrix-client-element/tasks/setup_uninstall.yml
+++ b/roles/custom/matrix-client-element/tasks/setup_uninstall.yml
@@ -19,7 +19,7 @@
         path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-client-element.service"
         state: absent
 
-    - name: Ensure Element path doesn't exist
+    - name: Ensure Element Web path doesn't exist
       ansible.builtin.file:
         path: "{{ matrix_client_element_data_path }}"
         state: absent
diff --git a/roles/custom/matrix-client-element/tasks/validate_config.yml b/roles/custom/matrix-client-element/tasks/validate_config.yml
index bf90b3d03..a61d8bcaf 100644
--- a/roles/custom/matrix-client-element/tasks/validate_config.yml
+++ b/roles/custom/matrix-client-element/tasks/validate_config.yml
@@ -1,13 +1,14 @@
 ---
 
-- name: Fail if required Element settings not defined
+- name: Fail if required Element Web settings not defined
   ansible.builtin.fail:
     msg: >
-      You need to define a required configuration setting (`{{ item }}`) for using Element.
-  when: "vars[item] == ''"
+      You need to define a required configuration setting (`{{ item }}`) for using Element Web.
+  when: "item.when | bool and vars[item.name] == ''"
   with_items:
-    - matrix_client_element_default_hs_url
-    - matrix_client_element_container_network
+    - {'name': 'matrix_client_element_default_hs_url', when: true}
+    - {'name': 'matrix_client_element_container_network', when: true}
+    - {'name': 'matrix_client_element_container_labels_traefik_compression_middleware_name', when: "{{ matrix_client_element_container_labels_traefik_compression_middleware_enabled }}"}
 
 - name: Fail if Element location sharing enabled, but no tile server defined
   ansible.builtin.fail:
diff --git a/roles/custom/matrix-client-element/templates/config.json.j2 b/roles/custom/matrix-client-element/templates/config.json.j2
index e45e68065..9d354a3c2 100644
--- a/roles/custom/matrix-client-element/templates/config.json.j2
+++ b/roles/custom/matrix-client-element/templates/config.json.j2
@@ -40,6 +40,7 @@
 	{% if matrix_client_element_location_sharing_enabled %}
 	"map_style_url": {{ matrix_client_element_map_style_url | to_json }},
 	{% endif %}
+	"logout_redirect_url": {{ matrix_client_element_logout_redirect_url | to_json }},
 	"branding": {
 		"auth_footer_links": {{ matrix_client_element_branding_auth_footer_links | to_json }},
 		"auth_header_logo_url": {{ matrix_client_element_branding_auth_header_logo_url | to_json }},
diff --git a/roles/custom/matrix-client-element/templates/labels.j2 b/roles/custom/matrix-client-element/templates/labels.j2
index 8de199918..67ed2b95a 100644
--- a/roles/custom/matrix-client-element/templates/labels.j2
+++ b/roles/custom/matrix-client-element/templates/labels.j2
@@ -9,6 +9,10 @@ traefik.http.services.matrix-client-element.loadbalancer.server.port=8080
 
 {% set middlewares = [] %}
 
+{% if matrix_client_element_container_labels_traefik_compression_middleware_enabled %}
+{% set middlewares = middlewares + [matrix_client_element_container_labels_traefik_compression_middleware_name] %}
+{% endif %}
+
 {% if matrix_client_element_container_labels_traefik_path_prefix != '/' %}
 traefik.http.middlewares.matrix-client-element-slashless-redirect.redirectregex.regex=({{ matrix_client_element_container_labels_traefik_path_prefix | quote }})$
 traefik.http.middlewares.matrix-client-element-slashless-redirect.redirectregex.replacement=${1}/
diff --git a/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2 b/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2
index e70869db2..9748cfe7c 100644
--- a/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2
+++ b/roles/custom/matrix-client-element/templates/systemd/matrix-client-element.service.j2
@@ -1,6 +1,6 @@
 #jinja2: lstrip_blocks: "True"
 [Unit]
-Description=Matrix Element server
+Description=Matrix Element Web server
 {% for service in matrix_client_element_systemd_required_services_list %}
 Requires={{ service }}
 After={{ service }}
diff --git a/roles/custom/matrix-client-hydrogen/defaults/main.yml b/roles/custom/matrix-client-hydrogen/defaults/main.yml
index 480492b42..78d1b8618 100644
--- a/roles/custom/matrix-client-hydrogen/defaults/main.yml
+++ b/roles/custom/matrix-client-hydrogen/defaults/main.yml
@@ -43,6 +43,11 @@ matrix_client_hydrogen_container_labels_traefik_entrypoints: web-secure
 matrix_client_hydrogen_container_labels_traefik_tls: "{{ matrix_client_hydrogen_container_labels_traefik_entrypoints != 'web' }}"
 matrix_client_hydrogen_container_labels_traefik_tls_certResolver: default  # noqa var-naming
 
+# Controls whether a compression middleware will be injected into the middlewares list.
+# This compression middleware is supposed to be defined elsewhere (using labels or a File provider, etc.) and is merely referenced by this router.
+matrix_client_hydrogen_container_labels_traefik_compression_middleware_enabled: false
+matrix_client_hydrogen_container_labels_traefik_compression_middleware_name: ""
+
 # Controls which additional headers to attach to all HTTP responses.
 # To add your own headers, use `matrix_client_hydrogen_container_labels_traefik_additional_response_headers_custom`
 matrix_client_hydrogen_container_labels_traefik_additional_response_headers: "{{ matrix_client_hydrogen_container_labels_traefik_additional_response_headers_auto | combine(matrix_client_hydrogen_container_labels_traefik_additional_response_headers_custom) }}"
diff --git a/roles/custom/matrix-client-hydrogen/tasks/validate_config.yml b/roles/custom/matrix-client-hydrogen/tasks/validate_config.yml
index 73452f831..93b9354eb 100644
--- a/roles/custom/matrix-client-hydrogen/tasks/validate_config.yml
+++ b/roles/custom/matrix-client-hydrogen/tasks/validate_config.yml
@@ -4,10 +4,11 @@
   ansible.builtin.fail:
     msg: >
       You need to define a required configuration setting (`{{ item }}`) to use Hydrogen.
-  when: "(vars[item] == '' or vars[item] is none) and matrix_client_hydrogen_container_image_self_build | bool"
+  when: "item.when | bool and vars[item.name] == ''"
   with_items:
-    - matrix_client_hydrogen_default_hs_url
-    - matrix_client_hydrogen_container_network
+    - {'name': 'matrix_client_hydrogen_default_hs_url', when: "{{ matrix_client_hydrogen_container_image_self_build }}"}
+    - {'name': 'matrix_client_hydrogen_container_network', when: true}
+    - {'name': 'matrix_client_hydrogen_container_labels_traefik_compression_middleware_name', when: "{{ matrix_client_hydrogen_container_labels_traefik_compression_middleware_enabled }}"}
 
 - when: matrix_client_hydrogen_container_labels_traefik_enabled | bool
   block:
diff --git a/roles/custom/matrix-client-hydrogen/templates/labels.j2 b/roles/custom/matrix-client-hydrogen/templates/labels.j2
index f5ccf8c97..011d02d1d 100644
--- a/roles/custom/matrix-client-hydrogen/templates/labels.j2
+++ b/roles/custom/matrix-client-hydrogen/templates/labels.j2
@@ -9,6 +9,10 @@ traefik.http.services.matrix-client-hydrogen.loadbalancer.server.port=8080
 
 {% set middlewares = [] %}
 
+{% if matrix_client_hydrogen_container_labels_traefik_compression_middleware_enabled %}
+{% set middlewares = middlewares + [matrix_client_hydrogen_container_labels_traefik_compression_middleware_name] %}
+{% endif %}
+
 {% if matrix_client_hydrogen_container_labels_traefik_path_prefix != '/' %}
 traefik.http.middlewares.matrix-client-hydrogen-slashless-redirect.redirectregex.regex=({{ matrix_client_hydrogen_container_labels_traefik_path_prefix | quote }})$
 traefik.http.middlewares.matrix-client-hydrogen-slashless-redirect.redirectregex.replacement=${1}/
diff --git a/roles/custom/matrix-client-schildichat/defaults/main.yml b/roles/custom/matrix-client-schildichat/defaults/main.yml
index 83145dc4c..68f0e86b9 100644
--- a/roles/custom/matrix-client-schildichat/defaults/main.yml
+++ b/roles/custom/matrix-client-schildichat/defaults/main.yml
@@ -4,15 +4,21 @@
 matrix_client_schildichat_enabled: true
 
 matrix_client_schildichat_container_image_self_build: false
+matrix_client_schildichat_container_image_self_build_repo: "https://github.com/SchildiChat/schildichat-desktop.git"
+matrix_client_schildichat_container_image_self_build_version: "{{ 'lite' if matrix_client_schildichat_version == 'latest' else ('v' + matrix_client_schildichat_version) }}"
+# Controls whether to patch webpack.config.js when self-building, so that building can pass on low-memory systems (< 4 GB RAM):
+# - https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1357
+# - https://github.com/element-hq/element-web/issues/19544
+matrix_client_schildichat_container_image_self_build_low_memory_system_patch_enabled: "{{ ansible_memtotal_mb < 4096 }}"
 
 # renovate: datasource=docker depName=ghcr.io/etkecc/schildichat-web
-matrix_client_schildichat_version: 1.11.36-sc.3
+matrix_client_schildichat_version: 1.11.86-sc.0.test.0
 matrix_client_schildichat_docker_image: "{{ matrix_client_schildichat_docker_image_name_prefix }}etkecc/schildichat-web:{{ matrix_client_schildichat_version }}"
 matrix_client_schildichat_docker_image_name_prefix: "{{ 'localhost/' if matrix_client_schildichat_container_image_self_build else 'ghcr.io/' }}"
 matrix_client_schildichat_docker_image_force_pull: "{{ matrix_client_schildichat_docker_image.endswith(':latest') }}"
 
 matrix_client_schildichat_data_path: "{{ matrix_base_data_path }}/client-schildichat"
-matrix_client_schildichat_docker_src_files_path: "{{ matrix_client_schildichat_data_path }}/docker-src"
+matrix_client_schildichat_container_src_files_path: "{{ matrix_client_schildichat_data_path }}/docker-src"
 
 # The base container network
 matrix_client_schildichat_container_network: ''
@@ -124,14 +130,14 @@ matrix_client_schildichat_floc_optout_enabled: true
 matrix_client_schildichat_hsts_preload_enabled: false
 
 matrix_client_schildichat_scheme: https
-# The hostname at which SchildiChat is served.
+# The hostname at which SchildiChat Web is served.
 matrix_client_schildichat_hostname: "{{ matrix_server_fqn_schildichat }}"
 
-# The path at which SchildiChat is exposed.
+# The path at which SchildiChat Web is exposed.
 # This value must either be `/` or not end with a slash (e.g. `/schildichat`).
 matrix_client_schildichat_path_prefix: /
 
-# SchildiChat config.json customizations
+# SchildiChat Web config.json customizations
 matrix_client_schildichat_default_server_name: "{{ matrix_domain }}"
 matrix_client_schildichat_default_hs_url: ""
 matrix_client_schildichat_default_is_url: ~
@@ -145,9 +151,9 @@ matrix_client_schildichat_integrations_jitsi_widget_url: "https://scalar.vector.
 matrix_client_schildichat_permalink_prefix: "https://matrix.to"  # noqa var-naming
 matrix_client_schildichat_bug_report_endpoint_url: "https://element.io/bugreports/submit"
 matrix_client_schildichat_show_lab_settings: true  # noqa var-naming
-# SchildiChat public room directory server(s)
+# SchildiChat Web public room directory server(s)
 matrix_client_schildichat_room_directory_servers: ['matrix.org']
-# Branding of SchildiChat
+# Branding of SchildiChat Web
 matrix_client_schildichat_brand: "schildichat"
 
 # URL to Logo on welcome page
@@ -171,7 +177,7 @@ matrix_client_schildichat_branding_welcome_background_url: ~  # noqa var-naming
 
 matrix_client_schildichat_page_template_welcome_path: "{{ role_path }}/templates/welcome.html.j2"
 
-# By default, there's no SchildiChat homepage (when logged in). If you wish to have one,
+# By default, there's no SchildiChat Web homepage (when logged in). If you wish to have one,
 # point this to a `home.html` template file on your local filesystem.
 matrix_client_schildichat_embedded_pages_home_path: ~
 
@@ -189,7 +195,7 @@ matrix_client_schildichat_default_country_code: "GB"
 # Controls whether presence will be enabled
 matrix_client_schildichat_enable_presence_by_hs_url: ~
 
-# Controls whether custom SchildiChat themes will be installed.
+# Controls whether custom SchildiChat Web themes will be installed.
 # When enabled, all themes found in the `matrix_client_schildichat_themes_repository_url` repository
 # will be installed and enabled automatically.
 matrix_client_schildichat_themes_enabled: false
@@ -199,16 +205,16 @@ matrix_client_schildichat_themes_repository_version: master
 # Controls the default theme
 matrix_client_schildichat_default_theme: 'light'
 
-# Controls the `setting_defaults.custom_themes` setting of the SchildiChat configuration.
+# Controls the `setting_defaults.custom_themes` setting of the SchildiChat Web configuration.
 # You can use this setting to define custom themes.
 #
 # Also, look at `matrix_client_schildichat_themes_enabled` for a way to pull in a bunch of custom themes automatically.
 # If you define your own themes here and set `matrix_client_schildichat_themes_enabled: true`, your themes will be preserved as well.
 #
-# Note that for a custom theme to work well, all SchildiChat instances that you use must have the same theme installed.
+# Note that for a custom theme to work well, all SchildiChat Web instances that you use must have the same theme installed.
 matrix_client_schildichat_setting_defaults_custom_themes: []  # noqa var-naming
 
-# Default SchildiChat configuration template which covers the generic use case.
+# Default SchildiChat Web configuration template which covers the generic use case.
 # You can customize it by controlling the various variables inside it.
 #
 # For a more advanced customization, you can extend the default (see `matrix_client_schildichat_configuration_extension_json`)
@@ -218,7 +224,7 @@ matrix_client_schildichat_setting_defaults_custom_themes: []  # noqa var-naming
 # This is unlike what it does when looking up YAML template files (no automatic parsing there).
 matrix_client_schildichat_configuration_default: "{{ lookup('template', 'templates/config.json.j2') }}"
 
-# Your custom JSON configuration for SchildiChat should go to `matrix_client_schildichat_configuration_extension_json`.
+# Your custom JSON configuration for SchildiChat Web should go to `matrix_client_schildichat_configuration_extension_json`.
 # This configuration extends the default starting configuration (`matrix_client_schildichat_configuration_default`).
 #
 # You can override individual variables from the default configuration, or introduce new ones.
@@ -237,7 +243,7 @@ matrix_client_schildichat_configuration_extension_json: '{}'
 
 matrix_client_schildichat_configuration_extension: "{{ matrix_client_schildichat_configuration_extension_json | from_json if matrix_client_schildichat_configuration_extension_json | from_json is mapping else {} }}"
 
-# Holds the final SchildiChat configuration (a combination of the default and its extension).
+# Holds the final SchildiChat Web configuration (a combination of the default and its extension).
 # You most likely don't need to touch this variable. Instead, see `matrix_client_schildichat_configuration_default`.
 matrix_client_schildichat_configuration: "{{ matrix_client_schildichat_configuration_default | combine(matrix_client_schildichat_configuration_extension, recursive=True) }}"
 
diff --git a/roles/custom/matrix-client-schildichat/tasks/prepare_themes.yml b/roles/custom/matrix-client-schildichat/tasks/prepare_themes.yml
index cd3f3ecb1..521679bc0 100644
--- a/roles/custom/matrix-client-schildichat/tasks/prepare_themes.yml
+++ b/roles/custom/matrix-client-schildichat/tasks/prepare_themes.yml
@@ -1,7 +1,7 @@
 ---
 
 #
-# Tasks related to setting up SchildiChat themes
+# Tasks related to setting up SchildiChat Web themes
 #
 
 - when: matrix_client_schildichat_themes_enabled | bool
@@ -9,35 +9,35 @@
   delegate_to: 127.0.0.1
   become: false
   block:
-    - name: Ensure SchildiChat themes repository is pulled
+    - name: Ensure SchildiChat Web themes repository is pulled
       ansible.builtin.git:
         repo: "{{ matrix_client_schildichat_themes_repository_url }}"
         version: "{{ matrix_client_schildichat_themes_repository_version }}"
         dest: "{{ role_path }}/files/scratchpad/themes"
 
-    - name: Find all SchildiChat theme files
+    - name: Find all SchildiChat Web theme files
       ansible.builtin.find:
         paths: "{{ role_path }}/files/scratchpad/themes"
         patterns: "*.json"
         recurse: true
       register: matrix_client_schildichat_theme_file_list
 
-    - name: Read SchildiChat theme
+    - name: Read SchildiChat Web theme
       ansible.builtin.slurp:
         path: "{{ item.path }}"
       register: "matrix_client_schildichat_theme_file_contents"
       with_items: "{{ matrix_client_schildichat_theme_file_list.files }}"
 
-    - name: Load SchildiChat theme
+    - name: Load SchildiChat Web theme
       ansible.builtin.set_fact:
         matrix_client_schildichat_setting_defaults_custom_themes: "{{ matrix_client_schildichat_setting_defaults_custom_themes + [item['content'] | b64decode | from_json] }}"  # noqa var-naming
       with_items: "{{ matrix_client_schildichat_theme_file_contents.results }}"
 
 #
-# Tasks related to getting rid of SchildiChat themes (if it was previously enabled)
+# Tasks related to getting rid of SchildiChat Web themes (if it was previously enabled)
 #
 
-- name: Ensure SchildiChat themes repository is removed
+- name: Ensure SchildiChat Web themes repository is removed
   ansible.builtin.file:
     path: "{{ role_path }}/files/scratchpad/themes"
     state: absent
diff --git a/roles/custom/matrix-client-schildichat/tasks/self_check.yml b/roles/custom/matrix-client-schildichat/tasks/self_check.yml
index 11895e8c6..5e8771111 100644
--- a/roles/custom/matrix-client-schildichat/tasks/self_check.yml
+++ b/roles/custom/matrix-client-schildichat/tasks/self_check.yml
@@ -3,7 +3,7 @@
 - ansible.builtin.set_fact:
     matrix_client_schildichat_url_endpoint_public: "{{ matrix_client_schildichat_scheme }}://{{ matrix_client_schildichat_hostname }}/config.json"
 
-- name: Check SchildiChat
+- name: Check SchildiChat Web
   ansible.builtin.uri:
     url: "{{ matrix_client_schildichat_url_endpoint_public }}"
     follow_redirects: none
@@ -14,11 +14,11 @@
   delegate_to: 127.0.0.1
   become: false
 
-- name: Fail if SchildiChat not working
+- name: Fail if SchildiChat Web not working
   ansible.builtin.fail:
-    msg: "Failed checking SchildiChat is up at `{{ matrix_server_fqn_schildichat }}` (checked endpoint: `{{ matrix_client_schildichat_url_endpoint_public }}`). Is SchildiChat running? Is port 443 open in your firewall? Full error: {{ matrix_client_schildichat_self_check_result }}"
+    msg: "Failed checking SchildiChat Web is up at `{{ matrix_server_fqn_schildichat }}` (checked endpoint: `{{ matrix_client_schildichat_url_endpoint_public }}`). Is SchildiChat Web running? Is port 443 open in your firewall? Full error: {{ matrix_client_schildichat_self_check_result }}"
   when: "matrix_client_schildichat_self_check_result.failed or 'json' not in matrix_client_schildichat_self_check_result"
 
-- name: Report working SchildiChat
+- name: Report working SchildiChat Web
   ansible.builtin.debug:
-    msg: "SchildiChat at `{{ matrix_server_fqn_schildichat }}` is working (checked endpoint: `{{ matrix_client_schildichat_url_endpoint_public }}`)"
+    msg: "SchildiChat Web at `{{ matrix_server_fqn_schildichat }}` is working (checked endpoint: `{{ matrix_client_schildichat_url_endpoint_public }}`)"
diff --git a/roles/custom/matrix-client-schildichat/tasks/setup_install.yml b/roles/custom/matrix-client-schildichat/tasks/setup_install.yml
index 77c1b45c5..b27f5bc48 100644
--- a/roles/custom/matrix-client-schildichat/tasks/setup_install.yml
+++ b/roles/custom/matrix-client-schildichat/tasks/setup_install.yml
@@ -1,6 +1,6 @@
 ---
 
-- name: Ensure SchildiChat paths exists
+- name: Ensure SchildiChat Web paths exists
   ansible.builtin.file:
     path: "{{ item.path }}"
     state: directory
@@ -9,10 +9,10 @@
     group: "{{ matrix_user_groupname }}"
   with_items:
     - {path: "{{ matrix_client_schildichat_data_path }}", when: true}
-    - {path: "{{ matrix_client_schildichat_docker_src_files_path }}", when: "{{ matrix_client_schildichat_container_image_self_build }}"}
+    - {path: "{{ matrix_client_schildichat_container_src_files_path }}", when: "{{ matrix_client_schildichat_container_image_self_build }}"}
   when: "item.when | bool"
 
-- name: Ensure SchildiChat Docker image is pulled
+- name: Ensure SchildiChat Web container image is pulled
   community.docker.docker_image:
     name: "{{ matrix_client_schildichat_docker_image }}"
     source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}"
@@ -24,42 +24,42 @@
   delay: "{{ devture_playbook_help_container_retries_delay }}"
   until: result is not failed
 
-- name: Ensure SchildiChat repository is present on self-build
-  ansible.builtin.git:
-    repo: "{{ matrix_client_schildichat_container_image_self_build_repo }}"
-    dest: "{{ matrix_client_schildichat_docker_src_files_path }}"
-    version: "{{ matrix_client_schildichat_docker_image.split(':')[1] }}"
-    force: "yes"
-  become: true
-  become_user: "{{ matrix_user_username }}"
-  register: matrix_client_schildichat_git_pull_results
-  when: "matrix_client_schildichat_container_image_self_build | bool"
+- when: "matrix_client_schildichat_container_image_self_build | bool"
+  block:
+    - name: Ensure SchildiChat Web repository is present on self-build
+      ansible.builtin.git:
+        repo: "{{ matrix_client_schildichat_container_image_self_build_repo }}"
+        dest: "{{ matrix_client_schildichat_container_src_files_path }}"
+        version: "{{ matrix_client_schildichat_container_image_self_build_version }}"
+        force: "yes"
+      become: true
+      become_user: "{{ matrix_user_username }}"
+      register: matrix_client_schildichat_git_pull_results
 
-# See:
-# - https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1357
-# - https://github.com/vector-im/schildichat-web/issues/19544 -- # Update (2023-12-15): 404
-- name: Patch webpack.config.js to support building on low-memory (<4G RAM) devices
-  ansible.builtin.lineinfile:
-    path: "{{ matrix_client_schildichat_docker_src_files_path }}/webpack.config.js"
-    regexp: '(\s+)splitChunks: \{'
-    line: '\1splitChunks: { maxSize: 100000,'
-    backrefs: true
-    owner: root
-    group: root
-    mode: '0644'
-  when: "matrix_client_schildichat_container_image_self_build | bool and matrix_client_schildichat_container_image_self_build_low_memory_system_patch_enabled | bool"
+    # See:
+    # - https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1357
+    # - https://github.com/vector-im/schildichat-web/issues/19544 -- # Update (2023-12-15): 404
+    - name: Patch webpack.config.js to support building on low-memory (<4G RAM) devices
+      ansible.builtin.lineinfile:
+        path: "{{ matrix_client_schildichat_container_src_files_path }}/element-web/webpack.config.js"
+        regexp: '(\s+)splitChunks: \{'
+        line: '\1splitChunks: { maxSize: 100000,'
+        backrefs: true
+        owner: root
+        group: root
+        mode: '0644'
+      when: "matrix_client_schildichat_container_image_self_build_low_memory_system_patch_enabled | bool"
 
-- name: Ensure SchildiChat Docker image is built
-  ansible.builtin.command:
-    cmd: |-
-      {{ devture_systemd_docker_base_host_command_docker }} buildx build
-      --tag={{ matrix_client_schildichat_docker_image }}
-      --file={{ matrix_client_schildichat_docker_src_files_path }}/Dockerfile
-      {{ matrix_client_schildichat_docker_src_files_path }}
-  changed_when: true
-  when: matrix_client_schildichat_container_image_self_build | bool
+    - name: Ensure SchildiChat Web container image is built
+      ansible.builtin.command:
+        cmd: |-
+          {{ devture_systemd_docker_base_host_command_docker }} buildx build
+          --tag={{ matrix_client_schildichat_docker_image }}
+          --file={{ matrix_client_schildichat_container_src_files_path }}/Dockerfile
+          {{ matrix_client_schildichat_container_src_files_path }}
+      changed_when: true
 
-- name: Ensure SchildiChat configuration installed
+- name: Ensure SchildiChat Web configuration installed
   ansible.builtin.copy:
     content: "{{ matrix_client_schildichat_configuration | to_nice_json }}"
     dest: "{{ matrix_client_schildichat_data_path }}/config.json"
@@ -76,7 +76,7 @@
     owner: "{{ matrix_user_username }}"
     group: "{{ matrix_user_groupname }}"
 
-- name: Ensure SchildiChat config files installed
+- name: Ensure SchildiChat Web config files installed
   ansible.builtin.template:
     src: "{{ item.src }}"
     dest: "{{ matrix_client_schildichat_data_path }}/{{ item.name }}"
@@ -89,7 +89,7 @@
     - {src: "{{ matrix_client_schildichat_embedded_pages_home_path }}", name: "home.html"}
   when: "item.src is not none"
 
-- name: Ensure SchildiChat config files removed
+- name: Ensure SchildiChat Web config files removed
   ansible.builtin.file:
     path: "{{ matrix_client_schildichat_data_path }}/{{ item.name }}"
     state: absent
@@ -97,7 +97,7 @@
     - {src: "{{ matrix_client_schildichat_embedded_pages_home_path }}", name: "home.html"}
   when: "item.src is none"
 
-- name: Ensure SchildiChat container network is created
+- name: Ensure SchildiChat Web container network is created
   community.general.docker_network:
     enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}"
     name: "{{ matrix_client_schildichat_container_network }}"
diff --git a/roles/custom/matrix-client-schildichat/tasks/setup_uninstall.yml b/roles/custom/matrix-client-schildichat/tasks/setup_uninstall.yml
index 98a4ae494..67f6856ff 100644
--- a/roles/custom/matrix-client-schildichat/tasks/setup_uninstall.yml
+++ b/roles/custom/matrix-client-schildichat/tasks/setup_uninstall.yml
@@ -19,7 +19,7 @@
         path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-client-schildichat.service"
         state: absent
 
-    - name: Ensure SchildiChat path doesn't exist
+    - name: Ensure SchildiChat Web path doesn't exist
       ansible.builtin.file:
         path: "{{ matrix_client_schildichat_data_path }}"
         state: absent
diff --git a/roles/custom/matrix-client-schildichat/tasks/validate_config.yml b/roles/custom/matrix-client-schildichat/tasks/validate_config.yml
index 0e3b832a7..a9cb7358c 100644
--- a/roles/custom/matrix-client-schildichat/tasks/validate_config.yml
+++ b/roles/custom/matrix-client-schildichat/tasks/validate_config.yml
@@ -1,6 +1,6 @@
 ---
 
-- name: (Deprecation) Catch and report renamed Schildichat settings
+- name: (Deprecation) Catch and report renamed SchildiChat Web settings
   ansible.builtin.fail:
     msg: >-
       Your configuration contains a variable, which now has a different name.
@@ -9,10 +9,10 @@
   with_items:
     - {'old': 'matrix_client_schildichat_welcome_user_id', 'new': '<removed>'}
 
-- name: Fail if required SchildiChat settings not defined
+- name: Fail if required SchildiChat Web settings not defined
   ansible.builtin.fail:
     msg: >
-      You need to define a required configuration setting (`{{ item }}`) for using SchildiChat.
+      You need to define a required configuration setting (`{{ item }}`) for using SchildiChat Web.
   when: "vars[item] == ''"
   with_items:
     - matrix_client_schildichat_default_hs_url
diff --git a/roles/custom/matrix-client-schildichat/templates/systemd/matrix-client-schildichat.service.j2 b/roles/custom/matrix-client-schildichat/templates/systemd/matrix-client-schildichat.service.j2
index 74111ffa8..98941d47e 100644
--- a/roles/custom/matrix-client-schildichat/templates/systemd/matrix-client-schildichat.service.j2
+++ b/roles/custom/matrix-client-schildichat/templates/systemd/matrix-client-schildichat.service.j2
@@ -1,6 +1,6 @@
 #jinja2: lstrip_blocks: "True"
 [Unit]
-Description=Matrix SchildiChat server
+Description=Matrix SchildiChat Web server
 {% for service in matrix_client_schildichat_systemd_required_services_list %}
 Requires={{ service }}
 After={{ service }}
diff --git a/roles/custom/matrix-conduit/defaults/main.yml b/roles/custom/matrix-conduit/defaults/main.yml
index f8f53ba33..247c95751 100644
--- a/roles/custom/matrix-conduit/defaults/main.yml
+++ b/roles/custom/matrix-conduit/defaults/main.yml
@@ -113,7 +113,7 @@ matrix_conduit_container_extra_arguments: []
 # Specifies which template files to use when configuring Conduit.
 # If you'd like to have your own different configuration, feel free to copy and paste
 # the original files into your inventory (e.g. in `inventory/host_vars/matrix.example.com/`)
-# and then change the specific host's `vars.yaml` file like this:
+# and then change the specific host's `vars.yml` file like this:
 # matrix_conduit_template_conduit_config: "{{ playbook_dir }}/inventory/host_vars/matrix.example.com/conduit.toml.j2"
 matrix_conduit_template_conduit_config: "{{ role_path }}/templates/conduit.toml.j2"
 
@@ -131,7 +131,7 @@ matrix_conduit_allow_registration: false
 matrix_conduit_allow_federation: true
 
 # Enable the display name lightning bolt on registration.
-matrix_conduit_enable_lightning_bolt: true
+matrix_conduit_enable_lightning_bolt: false
 
 matrix_conduit_trusted_servers:
  - "matrix.org"
diff --git a/roles/custom/matrix-conduwuit/defaults/main.yml b/roles/custom/matrix-conduwuit/defaults/main.yml
new file mode 100644
index 000000000..f302ed664
--- /dev/null
+++ b/roles/custom/matrix-conduwuit/defaults/main.yml
@@ -0,0 +1,189 @@
+---
+# conduwuit is a very cool, featureful fork of conduit (https://gitlab.com/famedly/conduit).
+# Project source code URL: https://github.com/girlbossceo/conduwuit
+# See: https://conduwuit.puppyirl.gay/
+
+matrix_conduwuit_enabled: true
+
+matrix_conduwuit_hostname: ''
+
+matrix_conduwuit_docker_image: "{{ matrix_conduwuit_docker_image_registry_prefix }}girlbossceo/conduwuit:{{ matrix_conduwuit_docker_image_tag }}"
+matrix_conduwuit_docker_image_name_prefix: "docker.io/"
+# renovate: datasource=docker depName=ghcr.io/girlbossceo/conduwuit
+matrix_conduwuit_docker_image_tag: v0.4.6-8f7ade4c22533a3177bfd8f175e178573ba6c1d4
+matrix_conduwuit_docker_image_force_pull: "{{ matrix_conduwuit_docker_image.endswith(':latest') }}"
+matrix_conduwuit_docker_image_registry_prefix: ghcr.io/
+
+matrix_conduwuit_base_path: "{{ matrix_base_data_path }}/conduwuit"
+matrix_conduwuit_config_path: "{{ matrix_conduwuit_base_path }}/config"
+matrix_conduwuit_data_path: "{{ matrix_conduwuit_base_path }}/data"
+
+matrix_conduwuit_config_port_number: 6167
+
+matrix_conduwuit_tmp_directory_size_mb: 500
+
+# List of systemd services that matrix-conduwuit.service depends on
+matrix_conduwuit_systemd_required_services_list: "{{ matrix_conduwuit_systemd_required_services_list_default + matrix_conduwuit_systemd_required_services_list_auto + matrix_conduwuit_systemd_required_services_list_custom }}"
+matrix_conduwuit_systemd_required_services_list_default: "{{ [devture_systemd_docker_base_docker_service_name] if devture_systemd_docker_base_docker_service_name else [] }}"
+matrix_conduwuit_systemd_required_services_list_auto: []
+matrix_conduwuit_systemd_required_services_list_custom: []
+
+# List of systemd services that matrix-conduwuit.service wants
+matrix_conduwuit_systemd_wanted_services_list: []
+
+# Controls how long to sleep for after starting the matrix-synapse container.
+#
+# Delaying, so that the homeserver can manage to fully start and various services
+# that depend on it (`matrix_conduwuit_systemd_required_services_list` and `matrix_conduwuit_systemd_wanted_services_list`)
+# may only start after the homeserver is up and running.
+#
+# This can be set to 0 to remove the delay.
+matrix_conduwuit_systemd_service_post_start_delay_seconds: 3
+
+# The base container network. It will be auto-created by this role if it doesn't exist already.
+matrix_conduwuit_container_network: ""
+
+# A list of additional container networks that the container would be connected to.
+# The role does not create these networks, so make sure they already exist.
+# Use this to expose this container to another reverse proxy, which runs in a different container network.
+matrix_conduwuit_container_additional_networks: "{{ matrix_conduwuit_container_additional_networks_auto + matrix_conduwuit_container_additional_networks_custom }}"
+matrix_conduwuit_container_additional_networks_auto: []
+matrix_conduwuit_container_additional_networks_custom: []
+
+# matrix_conduwuit_container_labels_traefik_enabled controls whether labels to assist a Traefik reverse-proxy will be attached to the container.
+# See `../templates/labels.j2` for details.
+#
+# To inject your own other container labels, see `matrix_conduwuit_container_labels_additional_labels`.
+matrix_conduwuit_container_labels_traefik_enabled: true
+matrix_conduwuit_container_labels_traefik_docker_network: "{{ matrix_conduwuit_container_network }}"
+matrix_conduwuit_container_labels_traefik_entrypoints: web-secure
+matrix_conduwuit_container_labels_traefik_tls_certResolver: default  # noqa var-naming
+
+# Controls whether labels will be added for handling the root (/) path on a public Traefik entrypoint.
+matrix_conduwuit_container_labels_public_client_root_enabled: true
+matrix_conduwuit_container_labels_public_client_root_traefik_hostname: "{{ matrix_conduwuit_hostname }}"
+matrix_conduwuit_container_labels_public_client_root_traefik_rule: "Host(`{{ matrix_conduwuit_container_labels_public_client_root_traefik_hostname }}`) && Path(`/`)"
+matrix_conduwuit_container_labels_public_client_root_traefik_priority: 0
+matrix_conduwuit_container_labels_public_client_root_traefik_entrypoints: "{{ matrix_conduwuit_container_labels_traefik_entrypoints }}"
+matrix_conduwuit_container_labels_public_client_root_traefik_tls: "{{ matrix_conduwuit_container_labels_public_client_root_traefik_entrypoints != 'web' }}"
+matrix_conduwuit_container_labels_public_client_root_traefik_tls_certResolver: "{{ matrix_conduwuit_container_labels_traefik_tls_certResolver }}"  # noqa var-naming
+matrix_conduwuit_container_labels_public_client_root_redirection_enabled: false
+matrix_conduwuit_container_labels_public_client_root_redirection_url: ""
+
+# Controls whether labels will be added that expose the Client-Server API on a public Traefik entrypoint.
+matrix_conduwuit_container_labels_public_client_api_enabled: true
+matrix_conduwuit_container_labels_public_client_api_traefik_hostname: "{{ matrix_conduwuit_hostname }}"
+matrix_conduwuit_container_labels_public_client_api_traefik_path_prefix: /_matrix
+matrix_conduwuit_container_labels_public_client_api_traefik_rule: "Host(`{{ matrix_conduwuit_container_labels_public_client_api_traefik_hostname }}`) && PathPrefix(`{{ matrix_conduwuit_container_labels_public_client_api_traefik_path_prefix }}`)"
+matrix_conduwuit_container_labels_public_client_api_traefik_priority: 0
+matrix_conduwuit_container_labels_public_client_api_traefik_entrypoints: "{{ matrix_conduwuit_container_labels_traefik_entrypoints }}"
+matrix_conduwuit_container_labels_public_client_api_traefik_tls: "{{ matrix_conduwuit_container_labels_public_client_api_traefik_entrypoints != 'web' }}"
+matrix_conduwuit_container_labels_public_client_api_traefik_tls_certResolver: "{{ matrix_conduwuit_container_labels_traefik_tls_certResolver }}"  # noqa var-naming
+
+# Controls whether labels will be added that expose the Client-Server API on the internal Traefik entrypoint.
+# This is similar to `matrix_conduwuit_container_labels_public_client_api_enabled`, but the entrypoint and intent is different.
+matrix_conduwuit_container_labels_internal_client_api_enabled: false
+matrix_conduwuit_container_labels_internal_client_api_traefik_path_prefix: "{{ matrix_conduwuit_container_labels_public_client_api_traefik_path_prefix }}"
+matrix_conduwuit_container_labels_internal_client_api_traefik_rule: "PathPrefix(`{{ matrix_conduwuit_container_labels_internal_client_api_traefik_path_prefix }}`)"
+matrix_conduwuit_container_labels_internal_client_api_traefik_priority: "{{ matrix_conduwuit_container_labels_public_client_api_traefik_priority }}"
+matrix_conduwuit_container_labels_internal_client_api_traefik_entrypoints: ""
+
+# Controls whether labels will be added that expose the Server-Server API (Federation API) on a public Traefik entrypoint.
+matrix_conduwuit_container_labels_public_federation_api_enabled: "{{ matrix_conduwuit_config_allow_federation }}"
+matrix_conduwuit_container_labels_public_federation_api_traefik_hostname: "{{ matrix_conduwuit_hostname }}"
+matrix_conduwuit_container_labels_public_federation_api_traefik_path_prefix: /_matrix
+matrix_conduwuit_container_labels_public_federation_api_traefik_rule: "Host(`{{ matrix_conduwuit_container_labels_public_federation_api_traefik_hostname }}`) && PathPrefix(`{{ matrix_conduwuit_container_labels_public_federation_api_traefik_path_prefix }}`)"
+matrix_conduwuit_container_labels_public_federation_api_traefik_priority: 0
+matrix_conduwuit_container_labels_public_federation_api_traefik_entrypoints: ''
+# TLS is force-enabled here, because the spec (https://spec.matrix.org/v1.9/server-server-api/#tls) says that the federation API must use HTTPS.
+matrix_conduwuit_container_labels_public_federation_api_traefik_tls: true
+matrix_conduwuit_container_labels_public_federation_api_traefik_tls_certResolver: "{{ matrix_conduwuit_container_labels_traefik_tls_certResolver }}"  # noqa var-naming
+
+# Controls whether labels will be added that expose the `/_conduwuit` path prefix on a public Traefik entrypoint.
+matrix_conduwuit_container_labels_public_conduwuit_api_enabled: true
+matrix_conduwuit_container_labels_public_conduwuit_api_traefik_hostname: "{{ matrix_conduwuit_hostname }}"
+matrix_conduwuit_container_labels_public_conduwuit_api_traefik_path_prefix: /_conduwuit
+matrix_conduwuit_container_labels_public_conduwuit_api_traefik_rule: "Host(`{{ matrix_conduwuit_container_labels_public_conduwuit_api_traefik_hostname }}`) && PathPrefix(`{{ matrix_conduwuit_container_labels_public_conduwuit_api_traefik_path_prefix }}`)"
+matrix_conduwuit_container_labels_public_conduwuit_api_traefik_priority: 0
+matrix_conduwuit_container_labels_public_conduwuit_api_traefik_entrypoints: "{{ matrix_conduwuit_container_labels_traefik_entrypoints }}"
+matrix_conduwuit_container_labels_public_conduwuit_api_traefik_tls: "{{ matrix_conduwuit_container_labels_public_conduwuit_api_traefik_entrypoints != 'web' }}"
+matrix_conduwuit_container_labels_public_conduwuit_api_traefik_tls_certResolver: "{{ matrix_conduwuit_container_labels_traefik_tls_certResolver }}"  # noqa var-naming
+
+# matrix_conduwuit_container_labels_additional_labels contains a multiline string with additional labels to add to the container label file.
+# See `../templates/labels.j2` for details.
+#
+# Example:
+# matrix_conduwuit_container_labels_additional_labels: |
+#   my.label=1
+#   another.label="here"
+matrix_conduwuit_container_labels_additional_labels: ''
+
+# Extra arguments for the Docker container
+matrix_conduwuit_container_extra_arguments: []
+
+# Specifies which template files to use when configuring conduwuit.
+# If you'd like to have your own different configuration, feel free to copy and paste
+# the original files into your inventory (e.g. in `inventory/host_vars/matrix.example.com/`)
+# and then change the specific host's `vars.yml` file like this:
+# matrix_conduwuit_template_conduwuit_config: "{{ playbook_dir }}/inventory/host_vars/matrix.example.com/conduwuit.toml.j2"
+matrix_conduwuit_template_conduwuit_config: "{{ role_path }}/templates/conduwuit.toml.j2"
+
+# Max size for uploads, in bytes
+matrix_conduwuit_config_server_name: "{{ matrix_domain }}"
+
+# Max size for uploads, in bytes
+matrix_conduwuit_config_max_request_size: 20_000_000
+
+# Enables registration. If set to false, no users can register on this server.
+matrix_conduwuit_config_allow_registration: false
+
+# Controls the `yes_i_am_very_very_sure_i_want_an_open_registration_server_prone_to_abuse` setting.
+# This is only used when `matrix_conduwuit_config_allow_registration` is set to true and no registration token is configured.
+matrix_conduwuit_config_yes_i_am_very_very_sure_i_want_an_open_registration_server_prone_to_abuse: false
+
+# Controls the `registration_token` setting.
+# When registration is enabled (`matrix_conduwuit_config_allow_registration`) you:
+# - either need to set a token to protect registration from abuse
+# - or you need to enable the `yes_i_am_very_very_sure_i_want_an_open_registration_server_prone_to_abuse` setting
+#   (see `matrix_conduwuit_config_yes_i_am_very_very_sure_i_want_an_open_registration_server_prone_to_abuse`),
+#   to allow registration without any form of 2nd-step.
+matrix_conduwuit_config_registration_token: ''
+
+# Controls the `new_user_displayname_suffix` setting.
+# This is the suffix that will be added to the displayname of new users.
+# Upstream defaults this to "🏳️‍⚧️", but we keep this consistent across all homeserver implementations and do not enable a suffix.
+matrix_conduwuit_config_new_user_displayname_suffix: ""
+
+# Controls the `allow_check_for_updates` setting.
+matrix_conduwuit_config_allow_check_for_updates: false
+
+# Controls the `emergency_password` setting.
+matrix_conduwuit_config_emergency_password: ''
+
+# Controls the `allow_federation` setting.
+matrix_conduwuit_config_allow_federation: true
+
+matrix_conduwuit_trusted_servers:
+ - "matrix.org"
+
+matrix_conduwuit_config_log: "info,state_res=warn,rocket=off,_=off,sled=off"
+
+# TURN integration.
+# See: https://conduwuit.puppyirl.gay/turn.html
+matrix_conduwuit_config_turn_uris: []
+matrix_conduwuit_config_turn_secret: ''
+matrix_conduwuit_config_turn_username: ''
+matrix_conduwuit_config_turn_password: ''
+
+# Controls whether the self-check feature should validate SSL certificates.
+matrix_conduwuit_self_check_validate_certificates: true
+
+# Additional environment variables to pass to the container.
+#
+# Environment variables take priority over settings in the configuration file.
+#
+# Example:
+# matrix_conduwuit_environment_variables_extension: |
+#   CONDUWUIT_MAX_REQUEST_SIZE=50000000
+#   CONDUWUIT_REQUEST_TIMEOUT=60
+matrix_conduwuit_environment_variables_extension: ''
diff --git a/roles/custom/matrix-conduwuit/tasks/install.yml b/roles/custom/matrix-conduwuit/tasks/install.yml
new file mode 100644
index 000000000..91d244c25
--- /dev/null
+++ b/roles/custom/matrix-conduwuit/tasks/install.yml
@@ -0,0 +1,60 @@
+---
+
+- name: Ensure conduwuit config path exists
+  ansible.builtin.file:
+    path: "{{ matrix_conduwuit_config_path }}"
+    state: directory
+    mode: 0750
+    owner: "{{ matrix_user_username }}"
+    group: "{{ matrix_user_groupname }}"
+
+- name: Ensure conduwuit data path exists
+  ansible.builtin.file:
+    path: "{{ matrix_conduwuit_data_path }}"
+    state: directory
+    mode: 0770
+    owner: "{{ matrix_user_username }}"
+    group: "{{ matrix_user_groupname }}"
+
+- name: Ensure conduwuit configuration installed
+  ansible.builtin.template:
+    src: "{{ matrix_conduwuit_template_conduwuit_config }}"
+    dest: "{{ matrix_conduwuit_config_path }}/conduwuit.toml"
+    mode: 0644
+    owner: "{{ matrix_user_username }}"
+    group: "{{ matrix_user_groupname }}"
+
+- name: Ensure conduwuit support files installed
+  ansible.builtin.template:
+    src: "{{ role_path }}/templates/{{ item }}.j2"
+    dest: "{{ matrix_conduwuit_base_path }}/{{ item }}"
+    mode: 0640
+    owner: "{{ matrix_user_username }}"
+    group: "{{ matrix_user_groupname }}"
+  with_items:
+    - labels
+    - env
+
+- name: Ensure conduwuit container network is created
+  community.general.docker_network:
+    enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}"
+    name: "{{ matrix_conduwuit_container_network }}"
+    driver: bridge
+    driver_options: "{{ devture_systemd_docker_base_container_networks_driver_options }}"
+
+- name: Ensure conduwuit container image is pulled
+  community.docker.docker_image:
+    name: "{{ matrix_conduwuit_docker_image }}"
+    source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}"
+    force_source: "{{ matrix_conduwuit_docker_image_force_pull if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}"
+    force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_conduwuit_docker_image_force_pull }}"
+  register: result
+  retries: "{{ devture_playbook_help_container_retries_count }}"
+  delay: "{{ devture_playbook_help_container_retries_delay }}"
+  until: result is not failed
+
+- name: Ensure matrix-conduwuit.service installed
+  ansible.builtin.template:
+    src: "{{ role_path }}/templates/systemd/matrix-conduwuit.service.j2"
+    dest: "{{ devture_systemd_docker_base_systemd_path }}/matrix-conduwuit.service"
+    mode: 0644
diff --git a/roles/custom/matrix-conduwuit/tasks/main.yml b/roles/custom/matrix-conduwuit/tasks/main.yml
new file mode 100644
index 000000000..68d5daad1
--- /dev/null
+++ b/roles/custom/matrix-conduwuit/tasks/main.yml
@@ -0,0 +1,29 @@
+---
+
+- tags:
+    - setup-all
+    - setup-conduwuit
+    - install-all
+    - install-conduwuit
+  block:
+    - when: matrix_conduwuit_enabled | bool
+      ansible.builtin.include_tasks: "{{ role_path }}/tasks/validate_config.yml"
+
+    - when: matrix_conduwuit_enabled | bool
+      ansible.builtin.include_tasks: "{{ role_path }}/tasks/install.yml"
+
+- tags:
+    - setup-all
+    - setup-conduwuit
+  block:
+    - when: not matrix_conduwuit_enabled | bool
+      ansible.builtin.include_tasks: "{{ role_path }}/tasks/uninstall.yml"
+
+- tags:
+    - self-check
+  block:
+    - when: matrix_conduwuit_enabled | bool
+      ansible.builtin.include_tasks: "{{ role_path }}/tasks/self_check_client_api.yml"
+
+    - when: matrix_conduwuit_enabled | bool
+      ansible.builtin.include_tasks: "{{ role_path }}/tasks/self_check_federation_api.yml"
diff --git a/roles/custom/matrix-conduwuit/tasks/self_check_client_api.yml b/roles/custom/matrix-conduwuit/tasks/self_check_client_api.yml
new file mode 100644
index 000000000..a34c14fb4
--- /dev/null
+++ b/roles/custom/matrix-conduwuit/tasks/self_check_client_api.yml
@@ -0,0 +1,23 @@
+---
+
+- name: Check Matrix Client API
+  ansible.builtin.uri:
+    url: "{{ matrix_conduwuit_client_api_url_endpoint_public }}"
+    follow_redirects: none
+    validate_certs: "{{ matrix_conduwuit_self_check_validate_certificates }}"
+  register: result_matrix_conduwuit_client_api
+  ignore_errors: true
+  check_mode: false
+  when: matrix_conduwuit_enabled | bool
+  delegate_to: 127.0.0.1
+  become: false
+
+- name: Fail if Matrix Client API not working
+  ansible.builtin.fail:
+    msg: "Failed checking Matrix Client API is up at `{{ matrix_server_fqn_matrix }}` (checked endpoint: `{{ matrix_conduwuit_client_api_url_endpoint_public }}`). Is Conduwuit running? Is port 443 open in your firewall? Full error: {{ result_matrix_conduwuit_client_api }}"
+  when: "matrix_conduwuit_enabled | bool and (result_matrix_conduwuit_client_api.failed or 'json' not in result_matrix_conduwuit_client_api)"
+
+- name: Report working Matrix Client API
+  ansible.builtin.debug:
+    msg: "The Matrix Client API at `{{ matrix_server_fqn_matrix }}` (checked endpoint: `{{ matrix_conduwuit_client_api_url_endpoint_public }}`) is working"
+  when: matrix_conduwuit_enabled | bool
diff --git a/roles/custom/matrix-conduwuit/tasks/self_check_federation_api.yml b/roles/custom/matrix-conduwuit/tasks/self_check_federation_api.yml
new file mode 100644
index 000000000..fde73dae0
--- /dev/null
+++ b/roles/custom/matrix-conduwuit/tasks/self_check_federation_api.yml
@@ -0,0 +1,28 @@
+---
+
+- name: Check Matrix Federation API
+  ansible.builtin.uri:
+    url: "{{ matrix_synapse_federation_api_url_endpoint_public }}"
+    follow_redirects: none
+    validate_certs: "{{ matrix_synapse_self_check_validate_certificates }}"
+  register: result_matrix_synapse_federation_api
+  ignore_errors: true
+  check_mode: false
+  when: matrix_synapse_enabled | bool
+  delegate_to: 127.0.0.1
+  become: false
+
+- name: Fail if Matrix Federation API not working
+  ansible.builtin.fail:
+    msg: "Failed checking Matrix Federation API is up at `{{ matrix_server_fqn_matrix }}` (checked endpoint: `{{ matrix_synapse_federation_api_url_endpoint_public }}`). Is Synapse running? Is port {{ matrix_federation_public_port }} open in your firewall? Full error: {{ result_matrix_synapse_federation_api }}"
+  when: "matrix_synapse_enabled | bool and matrix_synapse_federation_enabled | bool and (result_matrix_synapse_federation_api.failed or 'json' not in result_matrix_synapse_federation_api)"
+
+- name: Fail if Matrix Federation API unexpectedly enabled
+  ansible.builtin.fail:
+    msg: "Matrix Federation API is up at `{{ matrix_server_fqn_matrix }}` (checked endpoint: `{{ matrix_synapse_federation_api_url_endpoint_public }}`) despite being disabled."
+  when: "matrix_synapse_enabled | bool and not matrix_synapse_federation_enabled | bool and not result_matrix_synapse_federation_api.failed"
+
+- name: Report working Matrix Federation API
+  ansible.builtin.debug:
+    msg: "The Matrix Federation API at `{{ matrix_server_fqn_matrix }}` (checked endpoint: `{{ matrix_synapse_federation_api_url_endpoint_public }}`) is working"
+  when: "matrix_synapse_enabled | bool and matrix_synapse_federation_enabled | bool"
diff --git a/roles/custom/matrix-conduwuit/tasks/setup_install.yml b/roles/custom/matrix-conduwuit/tasks/setup_install.yml
new file mode 100644
index 000000000..02b189986
--- /dev/null
+++ b/roles/custom/matrix-conduwuit/tasks/setup_install.yml
@@ -0,0 +1,59 @@
+---
+
+- name: Ensure conduwuit config path exists
+  ansible.builtin.file:
+    path: "{{ matrix_conduwuit_config_path }}"
+    state: directory
+    mode: 0750
+    owner: "{{ matrix_user_username }}"
+    group: "{{ matrix_user_groupname }}"
+
+- name: Ensure conduwuit data path exists
+  ansible.builtin.file:
+    path: "{{ matrix_conduwuit_data_path }}"
+    state: directory
+    mode: 0770
+    owner: "{{ matrix_user_username }}"
+    group: "{{ matrix_user_groupname }}"
+
+- name: Ensure conduwuit configuration installed
+  ansible.builtin.template:
+    src: "{{ matrix_conduwuit_template_conduwuit_config }}"
+    dest: "{{ matrix_conduwuit_config_path }}/conduwuit.toml"
+    mode: 0644
+    owner: "{{ matrix_user_username }}"
+    group: "{{ matrix_user_groupname }}"
+
+- name: Ensure conduwuit support files installed
+  ansible.builtin.template:
+    src: "{{ role_path }}/templates/{{ item }}.j2"
+    dest: "{{ matrix_conduwuit_base_path }}/{{ item }}"
+    mode: 0640
+    owner: "{{ matrix_user_username }}"
+    group: "{{ matrix_user_groupname }}"
+  with_items:
+    - labels
+
+- name: Ensure conduwuit container network is created
+  community.general.docker_network:
+    enable_ipv6: "{{ devture_systemd_docker_base_ipv6_enabled }}"
+    name: "{{ matrix_conduwuit_container_network }}"
+    driver: bridge
+    driver_options: "{{ devture_systemd_docker_base_container_networks_driver_options }}"
+
+- name: Ensure conduwuit container image is pulled
+  community.docker.docker_image:
+    name: "{{ matrix_conduwuit_docker_image }}"
+    source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}"
+    force_source: "{{ matrix_conduwuit_docker_image_force_pull if ansible_version.major > 2 or ansible_version.minor >= 8 else omit }}"
+    force: "{{ omit if ansible_version.major > 2 or ansible_version.minor >= 8 else matrix_conduwuit_docker_image_force_pull }}"
+  register: result
+  retries: "{{ devture_playbook_help_container_retries_count }}"
+  delay: "{{ devture_playbook_help_container_retries_delay }}"
+  until: result is not failed
+
+- name: Ensure matrix-conduwuit.service installed
+  ansible.builtin.template:
+    src: "{{ role_path }}/templates/systemd/matrix-conduwuit.service.j2"
+    dest: "{{ devture_systemd_docker_base_systemd_path }}/matrix-conduwuit.service"
+    mode: 0644
diff --git a/roles/custom/matrix-conduwuit/tasks/setup_uninstall.yml b/roles/custom/matrix-conduwuit/tasks/setup_uninstall.yml
new file mode 100644
index 000000000..dcf802b0a
--- /dev/null
+++ b/roles/custom/matrix-conduwuit/tasks/setup_uninstall.yml
@@ -0,0 +1,19 @@
+---
+
+- name: Check existence of matrix-conduwuit service
+  ansible.builtin.stat:
+    path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-conduwuit.service"
+  register: matrix_conduwuit_service_stat
+
+- when: matrix_conduwuit_service_stat.stat.exists | bool
+  block:
+    - name: Ensure matrix-conduwuit is stopped
+      ansible.builtin.systemd:
+        name: matrix-conduwuit
+        state: stopped
+        daemon_reload: true
+
+    - name: Ensure matrix-conduwuit.service doesn't exist
+      ansible.builtin.file:
+        path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-conduwuit.service"
+        state: absent
diff --git a/roles/custom/matrix-conduwuit/tasks/uninstall.yml b/roles/custom/matrix-conduwuit/tasks/uninstall.yml
new file mode 100644
index 000000000..dcf802b0a
--- /dev/null
+++ b/roles/custom/matrix-conduwuit/tasks/uninstall.yml
@@ -0,0 +1,19 @@
+---
+
+- name: Check existence of matrix-conduwuit service
+  ansible.builtin.stat:
+    path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-conduwuit.service"
+  register: matrix_conduwuit_service_stat
+
+- when: matrix_conduwuit_service_stat.stat.exists | bool
+  block:
+    - name: Ensure matrix-conduwuit is stopped
+      ansible.builtin.systemd:
+        name: matrix-conduwuit
+        state: stopped
+        daemon_reload: true
+
+    - name: Ensure matrix-conduwuit.service doesn't exist
+      ansible.builtin.file:
+        path: "{{ devture_systemd_docker_base_systemd_path }}/matrix-conduwuit.service"
+        state: absent
diff --git a/roles/custom/matrix-conduwuit/tasks/validate_config.yml b/roles/custom/matrix-conduwuit/tasks/validate_config.yml
new file mode 100644
index 000000000..26f3ab100
--- /dev/null
+++ b/roles/custom/matrix-conduwuit/tasks/validate_config.yml
@@ -0,0 +1,11 @@
+---
+
+- name: Fail if required conduwuit settings not defined
+  ansible.builtin.fail:
+    msg: >-
+      You need to define a required configuration setting (`{{ item.name }}`).
+  when: "item.when | bool and vars[item.name] == ''"
+  with_items:
+    - {'name': 'matrix_conduwuit_hostname', when: true}
+    - {'name': 'matrix_conduwuit_container_network', when: true}
+    - {'name': 'matrix_conduwuit_container_labels_internal_client_api_traefik_entrypoints', when: "{{ matrix_conduwuit_container_labels_internal_client_api_enabled }}"}
diff --git a/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2 b/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2
new file mode 100644
index 000000000..4b011448c
--- /dev/null
+++ b/roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2
@@ -0,0 +1,1538 @@
+### conduwuit Configuration
+### See:
+### https://conduwuit.puppyirl.gay/configuration.html
+
+[global]
+
+# The server_name is the pretty name of this server. It is used as a
+# suffix for user and room IDs/aliases.
+#
+# See the docs for reverse proxying and delegation:
+# https://conduwuit.puppyirl.gay/deploying/generic.html#setting-up-the-reverse-proxy
+#
+# Also see the `[global.well_known]` config section at the very bottom.
+#
+# Examples of delegation:
+# - https://puppygock.gay/.well-known/matrix/server
+# - https://puppygock.gay/.well-known/matrix/client
+#
+# YOU NEED TO EDIT THIS. THIS CANNOT BE CHANGED AFTER WITHOUT A DATABASE
+# WIPE.
+#
+# example: "conduwuit.woof"
+#
+server_name = {{ matrix_conduwuit_config_server_name | to_json }}
+
+# The default address (IPv4 or IPv6) conduwuit will listen on.
+#
+# If you are using Docker or a container NAT networking setup, this must
+# be "0.0.0.0".
+#
+# To listen on multiple addresses, specify a vector e.g. ["127.0.0.1",
+# "::1"]
+#
+address = "0.0.0.0"
+
+# The port(s) conduwuit will listen on.
+#
+# For reverse proxying, see:
+# https://conduwuit.puppyirl.gay/deploying/generic.html#setting-up-the-reverse-proxy
+#
+# If you are using Docker, don't change this, you'll need to map an
+# external port to this.
+#
+# To listen on multiple ports, specify a vector e.g. [8080, 8448]
+#
+port = {{ matrix_conduwuit_config_port_number }}
+
+# The UNIX socket conduwuit will listen on.
+#
+# conduwuit cannot listen on both an IP address and a UNIX socket. If
+# listening on a UNIX socket, you MUST remove/comment the `address` key.
+#
+# Remember to make sure that your reverse proxy has access to this socket
+# file, either by adding your reverse proxy to the 'conduwuit' group or
+# granting world R/W permissions with `unix_socket_perms` (666 minimum).
+#
+# example: "/run/conduwuit/conduwuit.sock"
+#
+#unix_socket_path =
+
+# The default permissions (in octal) to create the UNIX socket with.
+#
+#unix_socket_perms = 660
+
+# This is the only directory where conduwuit will save its data, including
+# media. Note: this was previously "/var/lib/matrix-conduit".
+#
+# YOU NEED TO EDIT THIS.
+#
+# example: "/var/lib/conduwuit"
+#
+database_path = "/var/lib/conduwuit"
+
+# conduwuit supports online database backups using RocksDB's Backup engine
+# API. To use this, set a database backup path that conduwuit can write
+# to.
+#
+# For more information, see:
+# https://conduwuit.puppyirl.gay/maintenance.html#backups
+#
+# example: "/opt/conduwuit-db-backups"
+#
+#database_backup_path =
+
+# The amount of online RocksDB database backups to keep/retain, if using
+# "database_backup_path", before deleting the oldest one.
+#
+#database_backups_to_keep = 1
+
+# Text which will be added to the end of the user's displayname upon
+# registration with a space before the text. In Conduit, this was the
+# lightning bolt emoji.
+#
+# To disable, set this to "" (an empty string).
+#
+# The default is the trans pride flag.
+#
+# example: "🏳️‍⚧️"
+#
+new_user_displayname_suffix = {{ matrix_conduwuit_config_new_user_displayname_suffix | to_json }}
+
+# If enabled, conduwuit will send a simple GET request periodically to
+# `https://pupbrain.dev/check-for-updates/stable` for any new
+# announcements made. Despite the name, this is not an update check
+# endpoint, it is simply an announcement check endpoint.
+#
+# This is disabled by default as this is rarely used except for security
+# updates or major updates.
+#
+allow_check_for_updates = {{ matrix_conduwuit_config_allow_check_for_updates | to_json }}
+
+# Set this to any float value to multiply conduwuit's in-memory LRU caches
+# with such as "auth_chain_cache_capacity".
+#
+# May be useful if you have significant memory to spare to increase
+# performance.
+#
+# If you have low memory, reducing this may be viable.
+#
+# By default, the individual caches such as "auth_chain_cache_capacity"
+# are scaled by your CPU core count.
+#
+#cache_capacity_modifier = 1.0
+
+# Set this to any float value in megabytes for conduwuit to tell the
+# database engine that this much memory is available for database read
+# caches.
+#
+# May be useful if you have significant memory to spare to increase
+# performance.
+#
+# Similar to the individual LRU caches, this is scaled up with your CPU
+# core count.
+#
+# This defaults to 128.0 + (64.0 * CPU core count).
+#
+#db_cache_capacity_mb = varies by system
+
+# Set this to any float value in megabytes for conduwuit to tell the
+# database engine that this much memory is available for database write
+# caches.
+#
+# May be useful if you have significant memory to spare to increase
+# performance.
+#
+# Similar to the individual LRU caches, this is scaled up with your CPU
+# core count.
+#
+# This defaults to 48.0 + (4.0 * CPU core count).
+#
+#db_write_buffer_capacity_mb = varies by system
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#pdu_cache_capacity = varies by system
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#auth_chain_cache_capacity = varies by system
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#shorteventid_cache_capacity = varies by system
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#eventidshort_cache_capacity = varies by system
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#eventid_pdu_cache_capacity = varies by system
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#shortstatekey_cache_capacity = varies by system
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#statekeyshort_cache_capacity = varies by system
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#servernameevent_data_cache_capacity = varies by system
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#server_visibility_cache_capacity = varies by system
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#user_visibility_cache_capacity = varies by system
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#stateinfo_cache_capacity = varies by system
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#roomid_spacehierarchy_cache_capacity = varies by system
+
+# Maximum entries stored in DNS memory-cache. The size of an entry may
+# vary so please take care if raising this value excessively. Only
+# decrease this when using an external DNS cache. Please note that
+# systemd-resolved does *not* count as an external cache, even when
+# configured to do so.
+#
+#dns_cache_entries = 32768
+
+# Minimum time-to-live in seconds for entries in the DNS cache. The
+# default may appear high to most administrators; this is by design as the
+# majority of NXDOMAINs are correct for a long time (e.g. the server is no
+# longer running Matrix). Only decrease this if you are using an external
+# DNS cache.
+#
+#dns_min_ttl = 10800
+
+# Minimum time-to-live in seconds for NXDOMAIN entries in the DNS cache.
+# This value is critical for the server to federate efficiently.
+# NXDOMAIN's are assumed to not be returning to the federation and
+# aggressively cached rather than constantly rechecked.
+#
+# Defaults to 3 days as these are *very rarely* false negatives.
+#
+#dns_min_ttl_nxdomain = 259200
+
+# Number of DNS nameserver retries after a timeout or error.
+#
+#dns_attempts = 10
+
+# The number of seconds to wait for a reply to a DNS query. Please note
+# that recursive queries can take up to several seconds for some domains,
+# so this value should not be too low, especially on slower hardware or
+# resolvers.
+#
+#dns_timeout = 10
+
+# Fallback to TCP on DNS errors. Set this to false if unsupported by
+# nameserver.
+#
+#dns_tcp_fallback = true
+
+# Enable to query all nameservers until the domain is found. Referred to
+# as "trust_negative_responses" in hickory_resolver. This can avoid
+# useless DNS queries if the first nameserver responds with NXDOMAIN or
+# an empty NOERROR response.
+#
+#query_all_nameservers = true
+
+# Enable using *only* TCP for querying your specified nameservers instead
+# of UDP.
+#
+# If you are running conduwuit in a container environment, this config
+# option may need to be enabled. For more details, see:
+# https://conduwuit.puppyirl.gay/troubleshooting.html#potential-dns-issues-when-using-docker
+#
+#query_over_tcp_only = false
+
+# DNS A/AAAA record lookup strategy
+#
+# Takes a number of one of the following options:
+# 1 - Ipv4Only (Only query for A records, no AAAA/IPv6)
+#
+# 2 - Ipv6Only (Only query for AAAA records, no A/IPv4)
+#
+# 3 - Ipv4AndIpv6 (Query for A and AAAA records in parallel, uses whatever
+# returns a successful response first)
+#
+# 4 - Ipv6thenIpv4 (Query for AAAA record, if that fails then query the A
+# record)
+#
+# 5 - Ipv4thenIpv6 (Query for A record, if that fails then query the AAAA
+# record)
+#
+# If you don't have IPv6 networking, then for better DNS performance it
+# may be suitable to set this to Ipv4Only (1) as you will never ever use
+# the AAAA record contents even if the AAAA record is successful instead
+# of the A record.
+#
+#ip_lookup_strategy = 5
+
+# Max request size for file uploads in bytes. Defaults to 20MB.
+#
+max_request_size = {{ matrix_conduwuit_config_max_request_size }}
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#max_fetch_prev_events = 192
+
+# Default/base connection timeout (seconds). This is used only by URL
+# previews and update/news endpoint checks.
+#
+#request_conn_timeout = 10
+
+# Default/base request timeout (seconds). The time waiting to receive more
+# data from another server. This is used only by URL previews,
+# update/news, and misc endpoint checks.
+#
+#request_timeout = 35
+
+# Default/base request total timeout (seconds). The time limit for a whole
+# request. This is set very high to not cancel healthy requests while
+# serving as a backstop. This is used only by URL previews and update/news
+# endpoint checks.
+#
+#request_total_timeout = 320
+
+# Default/base idle connection pool timeout (seconds). This is used only
+# by URL previews and update/news endpoint checks.
+#
+#request_idle_timeout = 5
+
+# Default/base max idle connections per host. This is used only by URL
+# previews and update/news endpoint checks. Defaults to 1 as generally the
+# same open connection can be re-used.
+#
+#request_idle_per_host = 1
+
+# Federation well-known resolution connection timeout (seconds).
+#
+#well_known_conn_timeout = 6
+
+# Federation HTTP well-known resolution request timeout (seconds).
+#
+#well_known_timeout = 10
+
+# Federation client request timeout (seconds). You most definitely want
+# this to be high to account for extremely large room joins, slow
+# homeservers, your own resources etc.
+#
+#federation_timeout = 300
+
+# Federation client idle connection pool timeout (seconds).
+#
+#federation_idle_timeout = 25
+
+# Federation client max idle connections per host. Defaults to 1 as
+# generally the same open connection can be re-used.
+#
+#federation_idle_per_host = 1
+
+# Federation sender request timeout (seconds). The time it takes for the
+# remote server to process sent transactions can take a while.
+#
+#sender_timeout = 180
+
+# Federation sender idle connection pool timeout (seconds).
+#
+#sender_idle_timeout = 180
+
+# Federation sender transaction retry backoff limit (seconds).
+#
+#sender_retry_backoff_limit = 86400
+
+# Appservice URL request connection timeout. Defaults to 35 seconds as
+# generally appservices are hosted within the same network.
+#
+#appservice_timeout = 35
+
+# Appservice URL idle connection pool timeout (seconds).
+#
+#appservice_idle_timeout = 300
+
+# Notification gateway pusher idle connection pool timeout.
+#
+#pusher_idle_timeout = 15
+
+# Enables registration. If set to false, no users can register on this
+# server.
+#
+# If set to true without a token configured, users can register with no
+# form of 2nd-step only if you set the following option to true:
+# `yes_i_am_very_very_sure_i_want_an_open_registration_server_prone_to_abuse`
+#
+# If you would like registration only via token reg, please configure
+# `registration_token` or `registration_token_file`.
+#
+allow_registration = {{ matrix_conduwuit_config_allow_registration | to_json }}
+
+yes_i_am_very_very_sure_i_want_an_open_registration_server_prone_to_abuse = {{ matrix_conduwuit_config_yes_i_am_very_very_sure_i_want_an_open_registration_server_prone_to_abuse | to_json }}
+
+allow_federation = {{ matrix_conduwuit_config_allow_federation | to_json }}
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#yes_i_am_very_very_sure_i_want_an_open_registration_server_prone_to_abuse = false
+
+# A static registration token that new users will have to provide when
+# creating an account. If unset and `allow_registration` is true,
+# registration is open without any condition.
+#
+# YOU NEED TO EDIT THIS OR USE registration_token_file.
+#
+# example: "o&^uCtes4HPf0Vu@F20jQeeWE7"
+#
+registration_token = {{ matrix_conduwuit_config_registration_token | to_json }}
+
+# Path to a file on the system that gets read for the registration token.
+# this config option takes precedence/priority over "registration_token".
+#
+# conduwuit must be able to access the file, and it must not be empty
+#
+# example: "/etc/conduwuit/.reg_token"
+#
+#registration_token_file =
+
+# Controls whether encrypted rooms and events are allowed.
+#
+#allow_encryption = true
+
+# Controls whether federation is allowed or not. It is not recommended to
+# disable this after the fact due to potential federation breakage.
+#
+#allow_federation = true
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#federation_loopback = false
+
+# Set this to true to require authentication on the normally
+# unauthenticated profile retrieval endpoints (GET)
+# "/_matrix/client/v3/profile/{userId}".
+#
+# This can prevent profile scraping.
+#
+#require_auth_for_profile_requests = false
+
+# Set this to true to allow your server's public room directory to be
+# federated. Set this to false to protect against /publicRooms spiders,
+# but will forbid external users from viewing your server's public room
+# directory. If federation is disabled entirely (`allow_federation`), this
+# is inherently false.
+#
+#allow_public_room_directory_over_federation = false
+
+# Set this to true to allow your server's public room directory to be
+# queried without client authentication (access token) through the Client
+# APIs. Set this to false to protect against /publicRooms spiders.
+#
+#allow_public_room_directory_without_auth = false
+
+# Allow guests/unauthenticated users to access TURN credentials.
+#
+# This is the equivalent of Synapse's `turn_allow_guests` config option.
+# This allows any unauthenticated user to call the endpoint
+# `/_matrix/client/v3/voip/turnServer`.
+#
+# It is unlikely you need to enable this as all major clients support
+# authentication for this endpoint and prevents misuse of your TURN server
+# from potential bots.
+#
+#turn_allow_guests = false
+
+# Set this to true to lock down your server's public room directory and
+# only allow admins to publish rooms to the room directory. Unpublishing
+# is still allowed by all users with this enabled.
+#
+#lockdown_public_room_directory = false
+
+# Set this to true to allow federating device display names / allow
+# external users to see your device display name. If federation is
+# disabled entirely (`allow_federation`), this is inherently false. For
+# privacy reasons, this is best left disabled.
+#
+#allow_device_name_federation = false
+
+# Config option to allow or disallow incoming federation requests that
+# obtain the profiles of our local users from
+# `/_matrix/federation/v1/query/profile`
+#
+# Increases privacy of your local user's such as display names, but some
+# remote users may get a false "this user does not exist" error when they
+# try to invite you to a DM or room. Also can protect against profile
+# spiders.
+#
+# This is inherently false if `allow_federation` is disabled
+#
+#allow_inbound_profile_lookup_federation_requests = true
+
+# Allow standard users to create rooms. Appservices and admins are always
+# allowed to create rooms
+#
+#allow_room_creation = true
+
+# Set to false to disable users from joining or creating room versions
+# that aren't officially supported by conduwuit.
+#
+# conduwuit officially supports room versions 6 - 11.
+#
+# conduwuit has slightly experimental (though works fine in practice)
+# support for versions 3 - 5.
+#
+#allow_unstable_room_versions = true
+
+# Default room version conduwuit will create rooms with.
+#
+# Per spec, room version 10 is the default.
+#
+#default_room_version = 10
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#allow_jaeger = false
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#jaeger_filter = "info"
+
+# If the 'perf_measurements' compile-time feature is enabled, enables
+# collecting folded stack trace profile of tracing spans using
+# tracing_flame. The resulting profile can be visualized with inferno[1],
+# speedscope[2], or a number of other tools.
+#
+# [1]: https://github.com/jonhoo/inferno
+# [2]: www.speedscope.app
+#
+#tracing_flame = false
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#tracing_flame_filter = "info"
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#tracing_flame_output_path = "./tracing.folded"
+
+# Examples:
+#
+# - No proxy (default):
+#
+#       proxy = "none"
+#
+# - For global proxy, create the section at the bottom of this file:
+#
+#       [global.proxy]
+#       global = { url = "socks5h://localhost:9050" }
+#
+# - To proxy some domains:
+#
+#       [global.proxy]
+#       [[global.proxy.by_domain]]
+#       url = "socks5h://localhost:9050"
+#       include = ["*.onion", "matrix.myspecial.onion"]
+#       exclude = ["*.myspecial.onion"]
+#
+# Include vs. Exclude:
+#
+# - If include is an empty list, it is assumed to be `["*"]`.
+#
+# - If a domain matches both the exclude and include list, the proxy will
+#   only be used if it was included because of a more specific rule than
+#   it was excluded. In the above example, the proxy would be used for
+#   `ordinary.onion`, `matrix.myspecial.onion`, but not
+#   `hello.myspecial.onion`.
+#
+#proxy = "none"
+
+# Servers listed here will be used to gather public keys of other servers
+# (notary trusted key servers).
+#
+# Currently, conduwuit doesn't support inbound batched key requests, so
+# this list should only contain other Synapse servers.
+#
+# example: ["matrix.org", "envs.net", "constellatory.net", "tchncs.de"]
+#
+trusted_servers = {{ matrix_conduwuit_trusted_servers | to_json }}
+
+# Whether to query the servers listed in trusted_servers first or query
+# the origin server first. For best security, querying the origin server
+# first is advised to minimize the exposure to a compromised trusted
+# server. For maximum federation/join performance this can be set to true,
+# however other options exist to query trusted servers first under
+# specific high-load circumstances and should be evaluated before setting
+# this to true.
+#
+#query_trusted_key_servers_first = false
+
+# Whether to query the servers listed in trusted_servers first
+# specifically on room joins. This option limits the exposure to a
+# compromised trusted server to room joins only. The join operation
+# requires gathering keys from many origin servers which can cause
+# significant delays. Therefor this defaults to true to mitigate
+# unexpected delays out-of-the-box. The security-paranoid or those willing
+# to tolerate delays are advised to set this to false. Note that setting
+# query_trusted_key_servers_first to true causes this option to be
+# ignored.
+#
+#query_trusted_key_servers_first_on_join = true
+
+# Only query trusted servers for keys and never the origin server. This is
+# intended for clusters or custom deployments using their trusted_servers
+# as forwarding-agents to cache and deduplicate requests. Notary servers
+# do not act as forwarding-agents by default, therefor do not enable this
+# unless you know exactly what you are doing.
+#
+#only_query_trusted_key_servers = false
+
+# Maximum number of keys to request in each trusted server batch query.
+#
+#trusted_server_batch_size = 1024
+
+# Max log level for conduwuit. Allows debug, info, warn, or error.
+#
+# See also:
+# https://docs.rs/tracing-subscriber/latest/tracing_subscriber/filter/struct.EnvFilter.html#directives
+#
+# **Caveat**:
+# For release builds, the tracing crate is configured to only implement
+# levels higher than error to avoid unnecessary overhead in the compiled
+# binary from trace macros. For debug builds, this restriction is not
+# applied.
+#
+log = {{ matrix_conduwuit_config_log | to_json }}
+
+# Output logs with ANSI colours.
+#
+#log_colors = true
+
+# Configures the span events which will be outputted with the log.
+#
+#log_span_events = "none"
+
+# Configures whether CONDUWUIT_LOG EnvFilter matches values using regular
+# expressions. See the tracing_subscriber documentation on Directives.
+#
+#log_filter_regex = true
+
+# Toggles the display of ThreadId in tracing log output.
+#
+#log_thread_ids = false
+
+# OpenID token expiration/TTL in seconds.
+#
+# These are the OpenID tokens that are primarily used for Matrix account
+# integrations (e.g. Vector Integrations in Element), *not* OIDC/OpenID
+# Connect/etc.
+#
+#openid_token_ttl = 3600
+
+# Allow an existing session to mint a login token for another client.
+# This requires interactive authentication, but has security ramifications
+# as a malicious client could use the mechanism to spawn more than one
+# session.
+# Enabled by default.
+#
+#login_via_existing_session = true
+
+# Login token expiration/TTL in milliseconds.
+#
+# These are short-lived tokens for the m.login.token endpoint.
+# This is used to allow existing sessions to create new sessions.
+# see login_via_existing_session.
+#
+#login_token_ttl = 120000
+
+# Static TURN username to provide the client if not using a shared secret
+# ("turn_secret"), It is recommended to use a shared secret over static
+# credentials.
+#
+#turn_username = false
+
+# Static TURN password to provide the client if not using a shared secret
+# ("turn_secret"). It is recommended to use a shared secret over static
+# credentials.
+#
+#turn_password = false
+
+# Vector list of TURN URIs/servers to use.
+#
+# Replace "example.turn.uri" with your TURN domain, such as the coturn
+# "realm" config option. If using TURN over TLS, replace the URI prefix
+# "turn:" with "turns:".
+#
+# example: ["turn:example.turn.uri?transport=udp",
+# "turn:example.turn.uri?transport=tcp"]
+#
+turn_uris = {{ matrix_conduwuit_config_turn_uris | to_json }}
+
+# TURN secret to use for generating the HMAC-SHA1 hash apart of username
+# and password generation.
+#
+# This is more secure, but if needed you can use traditional static
+# username/password credentials.
+#
+#turn_secret = false
+{% if matrix_conduwuit_config_turn_secret != '' %}
+turn_secret = {{ matrix_conduwuit_config_turn_secret | to_json }}
+{% endif %}
+
+# If you have your TURN server configured to use a username and password
+# you can provide these information too. In this case comment out `turn_secret above`!
+{% if matrix_conduwuit_config_turn_username != '' or matrix_conduwuit_config_turn_password != '' %}
+turn_username = {{ matrix_conduwuit_config_turn_username | to_json }}
+turn_password = {{ matrix_conduwuit_config_turn_password | to_json }}
+{% endif %}
+
+# TURN secret to use that's read from the file path specified.
+#
+# This takes priority over "turn_secret" first, and falls back to
+# "turn_secret" if invalid or failed to open.
+#
+# example: "/etc/conduwuit/.turn_secret"
+#
+#turn_secret_file =
+
+# TURN TTL, in seconds.
+#
+#turn_ttl = 86400
+
+# List/vector of room IDs or room aliases that conduwuit will make newly
+# registered users join. The rooms specified must be rooms that you have
+# joined at least once on the server, and must be public.
+#
+# example: ["#conduwuit:puppygock.gay",
+# "!eoIzvAvVwY23LPDay8:puppygock.gay"]
+#
+#auto_join_rooms = []
+
+# Config option to automatically deactivate the account of any user who
+# attempts to join a:
+# - banned room
+# - forbidden room alias
+# - room alias or ID with a forbidden server name
+#
+# This may be useful if all your banned lists consist of toxic rooms or
+# servers that no good faith user would ever attempt to join, and
+# to automatically remediate the problem without any admin user
+# intervention.
+#
+# This will also make the user leave all rooms. Federation (e.g. remote
+# room invites) are ignored here.
+#
+# Defaults to false as rooms can be banned for non-moderation-related
+# reasons and this performs a full user deactivation.
+#
+#auto_deactivate_banned_room_attempts = false
+
+# RocksDB log level. This is not the same as conduwuit's log level. This
+# is the log level for the RocksDB engine/library which show up in your
+# database folder/path as `LOG` files. conduwuit will log RocksDB errors
+# as normal through tracing or panics if severe for safety.
+#
+#rocksdb_log_level = "error"
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#rocksdb_log_stderr = false
+
+# Max RocksDB `LOG` file size before rotating in bytes. Defaults to 4MB in
+# bytes.
+#
+#rocksdb_max_log_file_size = 4194304
+
+# Time in seconds before RocksDB will forcibly rotate logs.
+#
+#rocksdb_log_time_to_roll = 0
+
+# Set this to true to use RocksDB config options that are tailored to HDDs
+# (slower device storage).
+#
+# It is worth noting that by default, conduwuit will use RocksDB with
+# Direct IO enabled. *Generally* speaking this improves performance as it
+# bypasses buffered I/O (system page cache). However there is a potential
+# chance that Direct IO may cause issues with database operations if your
+# setup is uncommon. This has been observed with FUSE filesystems, and
+# possibly ZFS filesystem. RocksDB generally deals/corrects these issues
+# but it cannot account for all setups. If you experience any weird
+# RocksDB issues, try enabling this option as it turns off Direct IO and
+# feel free to report in the conduwuit Matrix room if this option fixes
+# your DB issues.
+#
+# For more information, see:
+# https://github.com/facebook/rocksdb/wiki/Direct-IO
+#
+#rocksdb_optimize_for_spinning_disks = false
+
+# Enables direct-io to increase database performance via unbuffered I/O.
+#
+# For more details about direct I/O and RockDB, see:
+# https://github.com/facebook/rocksdb/wiki/Direct-IO
+#
+# Set this option to false if the database resides on a filesystem which
+# does not support direct-io like FUSE, or any form of complex filesystem
+# setup such as possibly ZFS.
+#
+#rocksdb_direct_io = true
+
+# Amount of threads that RocksDB will use for parallelism on database
+# operations such as cleanup, sync, flush, compaction, etc. Set to 0 to
+# use all your logical threads. Defaults to your CPU logical thread count.
+#
+#rocksdb_parallelism_threads = varies by system
+
+# Maximum number of LOG files RocksDB will keep. This must *not* be set to
+# 0. It must be at least 1. Defaults to 3 as these are not very useful
+# unless troubleshooting/debugging a RocksDB bug.
+#
+#rocksdb_max_log_files = 3
+
+# Type of RocksDB database compression to use.
+#
+# Available options are "zstd", "zlib", "bz2", "lz4", or "none".
+#
+# It is best to use ZSTD as an overall good balance between
+# speed/performance, storage, IO amplification, and CPU usage. For more
+# performance but less compression (more storage used) and less CPU usage,
+# use LZ4.
+#
+# For more details, see:
+# https://github.com/facebook/rocksdb/wiki/Compression
+#
+# "none" will disable compression.
+#
+#rocksdb_compression_algo = "zstd"
+
+# Level of compression the specified compression algorithm for RocksDB to
+# use.
+#
+# Default is 32767, which is internally read by RocksDB as the default
+# magic number and translated to the library's default compression level
+# as they all differ. See their `kDefaultCompressionLevel`.
+#
+#rocksdb_compression_level = 32767
+
+# Level of compression the specified compression algorithm for the
+# bottommost level/data for RocksDB to use. Default is 32767, which is
+# internally read by RocksDB as the default magic number and translated to
+# the library's default compression level as they all differ. See their
+# `kDefaultCompressionLevel`.
+#
+# Since this is the bottommost level (generally old and least used data),
+# it may be desirable to have a very high compression level here as it's
+# less likely for this data to be used. Research your chosen compression
+# algorithm.
+#
+#rocksdb_bottommost_compression_level = 32767
+
+# Whether to enable RocksDB's "bottommost_compression".
+#
+# At the expense of more CPU usage, this will further compress the
+# database to reduce more storage. It is recommended to use ZSTD
+# compression with this for best compression results. This may be useful
+# if you're trying to reduce storage usage from the database.
+#
+# See https://github.com/facebook/rocksdb/wiki/Compression for more details.
+#
+#rocksdb_bottommost_compression = false
+
+# Database recovery mode (for RocksDB WAL corruption).
+#
+# Use this option when the server reports corruption and refuses to start.
+# Set mode 2 (PointInTime) to cleanly recover from this corruption. The
+# server will continue from the last good state, several seconds or
+# minutes prior to the crash. Clients may have to run "clear-cache &
+# reload" to account for the rollback. Upon success, you may reset the
+# mode back to default and restart again. Please note in some cases the
+# corruption error may not be cleared for at least 30 minutes of operation
+# in PointInTime mode.
+#
+# As a very last ditch effort, if PointInTime does not fix or resolve
+# anything, you can try mode 3 (SkipAnyCorruptedRecord) but this will
+# leave the server in a potentially inconsistent state.
+#
+# The default mode 1 (TolerateCorruptedTailRecords) will automatically
+# drop the last entry in the database if corrupted during shutdown, but
+# nothing more. It is extraordinarily unlikely this will desynchronize
+# clients. To disable any form of silent rollback set mode 0
+# (AbsoluteConsistency).
+#
+# The options are:
+# 0 = AbsoluteConsistency
+# 1 = TolerateCorruptedTailRecords (default)
+# 2 = PointInTime (use me if trying to recover)
+# 3 = SkipAnyCorruptedRecord (you now voided your Conduwuit warranty)
+#
+# For more information on these modes, see:
+# https://github.com/facebook/rocksdb/wiki/WAL-Recovery-Modes
+#
+# For more details on recovering a corrupt database, see:
+# https://conduwuit.puppyirl.gay/troubleshooting.html#database-corruption
+#
+#rocksdb_recovery_mode = 1
+
+# Enables or disables paranoid SST file checks. This can improve RocksDB
+# database consistency at a potential performance impact due to further
+# safety checks ran.
+#
+# For more information, see:
+# https://github.com/facebook/rocksdb/wiki/Online-Verification#columnfamilyoptionsparanoid_file_checks
+#
+#rocksdb_paranoid_file_checks = false
+
+# Database repair mode (for RocksDB SST corruption).
+#
+# Use this option when the server reports corruption while running or
+# panics. If the server refuses to start use the recovery mode options
+# first. Corruption errors containing the acronym 'SST' which occur after
+# startup will likely require this option.
+#
+# - Backing up your database directory is recommended prior to running the
+#   repair.
+#
+# - Disabling repair mode and restarting the server is recommended after
+#   running the repair.
+#
+# See https://conduwuit.puppyirl.gay/troubleshooting.html#database-corruption for more details on recovering a corrupt database.
+#
+#rocksdb_repair = false
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#rocksdb_read_only = false
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#rocksdb_secondary = false
+
+# Enables idle CPU priority for compaction thread. This is not enabled by
+# default to prevent compaction from falling too far behind on busy
+# systems.
+#
+#rocksdb_compaction_prio_idle = false
+
+# Enables idle IO priority for compaction thread. This prevents any
+# unexpected lag in the server's operation and is usually a good idea.
+# Enabled by default.
+#
+#rocksdb_compaction_ioprio_idle = true
+
+# Disables RocksDB compaction. You should never ever have to set this
+# option to true. If you for some reason find yourself needing to use this
+# option as part of troubleshooting or a bug, please reach out to us in
+# the conduwuit Matrix room with information and details.
+#
+# Disabling compaction will lead to a significantly bloated and
+# explosively large database, gradually poor performance, unnecessarily
+# excessive disk read/writes, and slower shutdowns and startups.
+#
+#rocksdb_compaction = true
+
+# Level of statistics collection. Some admin commands to display database
+# statistics may require this option to be set. Database performance may
+# be impacted by higher settings.
+#
+# Option is a number ranging from 0 to 6:
+# 0 = No statistics.
+# 1 = No statistics in release mode (default).
+# 2 to 3 = Statistics with no performance impact.
+# 3 to 5 = Statistics with possible performance impact.
+# 6 = All statistics.
+#
+#rocksdb_stats_level = 1
+
+# This is a password that can be configured that will let you login to the
+# server bot account (currently `@conduit`) for emergency troubleshooting
+# purposes such as recovering/recreating your admin room, or inviting
+# yourself back.
+#
+# See https://conduwuit.puppyirl.gay/troubleshooting.html#lost-access-to-admin-room for other ways to get back into your admin room.
+#
+# Once this password is unset, all sessions will be logged out for
+# security purposes.
+#
+# example: "F670$2CP@Hw8mG7RY1$%!#Ic7YA"
+#
+emergency_password = {{ matrix_conduwuit_config_emergency_password | to_json }}
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#notification_push_path = "/_matrix/push/v1/notify"
+
+# Allow local (your server only) presence updates/requests.
+#
+# Note that presence on conduwuit is very fast unlike Synapse's. If using
+# outgoing presence, this MUST be enabled.
+#
+#allow_local_presence = true
+
+# Allow incoming federated presence updates/requests.
+#
+# This option receives presence updates from other servers, but does not
+# send any unless `allow_outgoing_presence` is true. Note that presence on
+# conduwuit is very fast unlike Synapse's.
+#
+#allow_incoming_presence = true
+
+# Allow outgoing presence updates/requests.
+#
+# This option sends presence updates to other servers, but does not
+# receive any unless `allow_incoming_presence` is true. Note that presence
+# on conduwuit is very fast unlike Synapse's. If using outgoing presence,
+# you MUST enable `allow_local_presence` as well.
+#
+#allow_outgoing_presence = true
+
+# How many seconds without presence updates before you become idle.
+# Defaults to 5 minutes.
+#
+#presence_idle_timeout_s = 300
+
+# How many seconds without presence updates before you become offline.
+# Defaults to 30 minutes.
+#
+#presence_offline_timeout_s = 1800
+
+# Enable the presence idle timer for remote users.
+#
+# Disabling is offered as an optimization for servers participating in
+# many large rooms or when resources are limited. Disabling it may cause
+# incorrect presence states (i.e. stuck online) to be seen for some remote
+# users.
+#
+#presence_timeout_remote_users = true
+
+# Allow receiving incoming read receipts from remote servers.
+#
+#allow_incoming_read_receipts = true
+
+# Allow sending read receipts to remote servers.
+#
+#allow_outgoing_read_receipts = true
+
+# Allow outgoing typing updates to federation.
+#
+#allow_outgoing_typing = true
+
+# Allow incoming typing updates from federation.
+#
+#allow_incoming_typing = true
+
+# Maximum time federation user can indicate typing.
+#
+#typing_federation_timeout_s = 30
+
+# Minimum time local client can indicate typing. This does not override a
+# client's request to stop typing. It only enforces a minimum value in
+# case of no stop request.
+#
+#typing_client_timeout_min_s = 15
+
+# Maximum time local client can indicate typing.
+#
+#typing_client_timeout_max_s = 45
+
+# Set this to true for conduwuit to compress HTTP response bodies using
+# zstd. This option does nothing if conduwuit was not built with
+# `zstd_compression` feature. Please be aware that enabling HTTP
+# compression may weaken TLS. Most users should not need to enable this.
+# See https://breachattack.com/ and https://wikipedia.org/wiki/BREACH
+# before deciding to enable this.
+#
+#zstd_compression = false
+
+# Set this to true for conduwuit to compress HTTP response bodies using
+# gzip. This option does nothing if conduwuit was not built with
+# `gzip_compression` feature. Please be aware that enabling HTTP
+# compression may weaken TLS. Most users should not need to enable this.
+# See https://breachattack.com/ and https://wikipedia.org/wiki/BREACH before
+# deciding to enable this.
+#
+# If you are in a large amount of rooms, you may find that enabling this
+# is necessary to reduce the significantly large response bodies.
+#
+#gzip_compression = false
+
+# Set this to true for conduwuit to compress HTTP response bodies using
+# brotli. This option does nothing if conduwuit was not built with
+# `brotli_compression` feature. Please be aware that enabling HTTP
+# compression may weaken TLS. Most users should not need to enable this.
+# See https://breachattack.com/ and https://wikipedia.org/wiki/BREACH
+# before deciding to enable this.
+#
+#brotli_compression = false
+
+# Set to true to allow user type "guest" registrations. Some clients like
+# Element attempt to register guest users automatically.
+#
+#allow_guest_registration = false
+
+# Set to true to log guest registrations in the admin room. Note that
+# these may be noisy or unnecessary if you're a public homeserver.
+#
+#log_guest_registrations = false
+
+# Set to true to allow guest registrations/users to auto join any rooms
+# specified in `auto_join_rooms`.
+#
+#allow_guests_auto_join_rooms = false
+
+# Enable the legacy unauthenticated Matrix media repository endpoints.
+# These endpoints consist of:
+# - /_matrix/media/*/config
+# - /_matrix/media/*/upload
+# - /_matrix/media/*/preview_url
+# - /_matrix/media/*/download/*
+# - /_matrix/media/*/thumbnail/*
+#
+# The authenticated equivalent endpoints are always enabled.
+#
+# Defaults to true for now, but this is highly subject to change, likely
+# in the next release.
+#
+#allow_legacy_media = true
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#freeze_legacy_media = true
+
+# Check consistency of the media directory at startup:
+# 1. When `media_compat_file_link` is enabled, this check will upgrade
+#    media when switching back and forth between Conduit and conduwuit.
+#    Both options must be enabled to handle this.
+# 2. When media is deleted from the directory, this check will also delete
+#    its database entry.
+#
+# If none of these checks apply to your use cases, and your media
+# directory is significantly large setting this to false may reduce
+# startup time.
+#
+#media_startup_check = true
+
+# Enable backward-compatibility with Conduit's media directory by creating
+# symlinks of media.
+#
+# This option is only necessary if you plan on using Conduit again.
+# Otherwise setting this to false reduces filesystem clutter and overhead
+# for managing these symlinks in the directory. This is now disabled by
+# default. You may still return to upstream Conduit but you have to run
+# conduwuit at least once with this set to true and allow the
+# media_startup_check to take place before shutting down to return to
+# Conduit.
+#
+#media_compat_file_link = false
+
+# Prune missing media from the database as part of the media startup
+# checks.
+#
+# This means if you delete files from the media directory the
+# corresponding entries will be removed from the database. This is
+# disabled by default because if the media directory is accidentally moved
+# or inaccessible, the metadata entries in the database will be lost with
+# sadness.
+#
+#prune_missing_media = false
+
+# Vector list of servers that conduwuit will refuse to download remote
+# media from.
+#
+#prevent_media_downloads_from = []
+
+# List of forbidden server names that we will block incoming AND outgoing
+# federation with, and block client room joins / remote user invites.
+#
+# This check is applied on the room ID, room alias, sender server name,
+# sender user's server name, inbound federation X-Matrix origin, and
+# outbound federation handler.
+#
+# Basically "global" ACLs.
+#
+#forbidden_remote_server_names = []
+
+# List of forbidden server names that we will block all outgoing federated
+# room directory requests for. Useful for preventing our users from
+# wandering into bad servers or spaces.
+#
+#forbidden_remote_room_directory_server_names = []
+
+# Vector list of IPv4 and IPv6 CIDR ranges / subnets *in quotes* that you
+# do not want conduwuit to send outbound requests to. Defaults to
+# RFC1918, unroutable, loopback, multicast, and testnet addresses for
+# security.
+#
+# Please be aware that this is *not* a guarantee. You should be using a
+# firewall with zones as doing this on the application layer may have
+# bypasses.
+#
+# Currently this does not account for proxies in use like Synapse does.
+#
+# To disable, set this to be an empty vector (`[]`).
+#
+# Defaults to:
+# ["127.0.0.0/8", "10.0.0.0/8", "172.16.0.0/12",
+# "192.168.0.0/16", "100.64.0.0/10", "192.0.0.0/24", "169.254.0.0/16",
+# "192.88.99.0/24", "198.18.0.0/15", "192.0.2.0/24", "198.51.100.0/24",
+# "203.0.113.0/24", "224.0.0.0/4", "::1/128", "fe80::/10", "fc00::/7",
+# "2001:db8::/32", "ff00::/8", "fec0::/10"]
+#
+#ip_range_denylist =
+
+# Optional IP address or network interface-name to bind as the source of
+# URL preview requests. If not set, it will not bind to a specific
+# address or interface.
+#
+# Interface names only supported on Linux, Android, and Fuchsia platforms;
+# all other platforms can specify the IP address. To list the interfaces
+# on your system, use the command `ip link show`.
+#
+# example: `"eth0"` or `"1.2.3.4"`
+#
+#url_preview_bound_interface =
+
+# Vector list of domains allowed to send requests to for URL previews.
+#
+# This is a *contains* match, not an explicit match. Putting "google.com"
+# will match "https://google.com" and
+# "http://mymaliciousdomainexamplegoogle.com" Setting this to "*" will
+# allow all URL previews. Please note that this opens up significant
+# attack surface to your server, you are expected to be aware of the risks
+# by doing so.
+#
+#url_preview_domain_contains_allowlist = []
+
+# Vector list of explicit domains allowed to send requests to for URL
+# previews.
+#
+# This is an *explicit* match, not a contains match. Putting "google.com"
+# will match "https://google.com", "http://google.com", but not
+# "https://mymaliciousdomainexamplegoogle.com". Setting this to "*" will
+# allow all URL previews. Please note that this opens up significant
+# attack surface to your server, you are expected to be aware of the risks
+# by doing so.
+#
+#url_preview_domain_explicit_allowlist = []
+
+# Vector list of explicit domains not allowed to send requests to for URL
+# previews.
+#
+# This is an *explicit* match, not a contains match. Putting "google.com"
+# will match "https://google.com", "http://google.com", but not
+# "https://mymaliciousdomainexamplegoogle.com". The denylist is checked
+# first before allowlist. Setting this to "*" will not do anything.
+#
+#url_preview_domain_explicit_denylist = []
+
+# Vector list of URLs allowed to send requests to for URL previews.
+#
+# Note that this is a *contains* match, not an explicit match. Putting
+# "google.com" will match "https://google.com/",
+# "https://google.com/url?q=https://mymaliciousdomainexample.com", and
+# "https://mymaliciousdomainexample.com/hi/google.com" Setting this to "*"
+# will allow all URL previews. Please note that this opens up significant
+# attack surface to your server, you are expected to be aware of the risks
+# by doing so.
+#
+#url_preview_url_contains_allowlist = []
+
+# Maximum amount of bytes allowed in a URL preview body size when
+# spidering. Defaults to 256KB in bytes.
+#
+#url_preview_max_spider_size = 256000
+
+# Option to decide whether you would like to run the domain allowlist
+# checks (contains and explicit) on the root domain or not. Does not apply
+# to URL contains allowlist. Defaults to false.
+#
+# Example usecase: If this is enabled and you have "wikipedia.org" allowed
+# in the explicit and/or contains domain allowlist, it will allow all
+# subdomains under "wikipedia.org" such as "en.m.wikipedia.org" as the
+# root domain is checked and matched. Useful if the domain contains
+# allowlist is still too broad for you but you still want to allow all the
+# subdomains under a root domain.
+#
+#url_preview_check_root_domain = false
+
+# List of forbidden room aliases and room IDs as strings of regex
+# patterns.
+#
+# Regex can be used or explicit contains matches can be done by just
+# specifying the words (see example).
+#
+# This is checked upon room alias creation, custom room ID creation if
+# used, and startup as warnings if any room aliases in your database have
+# a forbidden room alias/ID.
+#
+# example: ["19dollarfortnitecards", "b[4a]droom"]
+#
+#forbidden_alias_names = []
+
+# List of forbidden username patterns/strings.
+#
+# Regex can be used or explicit contains matches can be done by just
+# specifying the words (see example).
+#
+# This is checked upon username availability check, registration, and
+# startup as warnings if any local users in your database have a forbidden
+# username.
+#
+# example: ["administrator", "b[a4]dusernam[3e]"]
+#
+#forbidden_usernames = []
+
+# Retry failed and incomplete messages to remote servers immediately upon
+# startup. This is called bursting. If this is disabled, said messages may
+# not be delivered until more messages are queued for that server. Do not
+# change this option unless server resources are extremely limited or the
+# scale of the server's deployment is huge. Do not disable this unless you
+# know what you are doing.
+#
+#startup_netburst = true
+
+# Messages are dropped and not reattempted. The `startup_netburst` option
+# must be enabled for this value to have any effect. Do not change this
+# value unless you know what you are doing. Set this value to -1 to
+# reattempt every message without trimming the queues; this may consume
+# significant disk. Set this value to 0 to drop all messages without any
+# attempt at redelivery.
+#
+#startup_netburst_keep = 50
+
+# Block non-admin local users from sending room invites (local and
+# remote), and block non-admin users from receiving remote room invites.
+#
+# Admins are always allowed to send and receive all room invites.
+#
+#block_non_admin_invites = false
+
+# Allow admins to enter commands in rooms other than "#admins" (admin
+# room) by prefixing your message with "\!admin" or "\\!admin" followed up
+# a normal conduwuit admin command. The reply will be publicly visible to
+# the room, originating from the sender.
+#
+# example: \\!admin debug ping puppygock.gay
+#
+#admin_escape_commands = true
+
+# Automatically activate the conduwuit admin room console / CLI on
+# startup. This option can also be enabled with `--console` conduwuit
+# argument.
+#
+#admin_console_automatic = false
+
+# List of admin commands to execute on startup.
+#
+# This option can also be configured with the `--execute` conduwuit
+# argument and can take standard shell commands and environment variables
+#
+# For example: `./conduwuit --execute "server admin-notice conduwuit has
+# started up at $(date)"`
+#
+# example: admin_execute = ["debug ping puppygock.gay", "debug echo hi"]`
+#
+#admin_execute = []
+
+# Ignore errors in startup commands.
+#
+# If false, conduwuit will error and fail to start if an admin execute
+# command (`--execute` / `admin_execute`) fails.
+#
+#admin_execute_errors_ignore = false
+
+# Controls the max log level for admin command log captures (logs
+# generated from running admin commands). Defaults to "info" on release
+# builds, else "debug" on debug builds.
+#
+#admin_log_capture = "info"
+
+# The default room tag to apply on the admin room.
+#
+# On some clients like Element, the room tag "m.server_notice" is a
+# special pinned room at the very bottom of your room list. The conduwuit
+# admin room can be pinned here so you always have an easy-to-access
+# shortcut dedicated to your admin room.
+#
+#admin_room_tag = "m.server_notice"
+
+# Sentry.io crash/panic reporting, performance monitoring/metrics, etc.
+# This is NOT enabled by default. conduwuit's default Sentry reporting
+# endpoint domain is `o4506996327251968.ingest.us.sentry.io`.
+#
+#sentry = false
+
+# Sentry reporting URL, if a custom one is desired.
+#
+#sentry_endpoint = "https://fe2eb4536aa04949e28eff3128d64757@o4506996327251968.ingest.us.sentry.io/4506996334657536"
+
+# Report your conduwuit server_name in Sentry.io crash reports and
+# metrics.
+#
+#sentry_send_server_name = false
+
+# Performance monitoring/tracing sample rate for Sentry.io.
+#
+# Note that too high values may impact performance, and can be disabled by
+# setting it to 0.0 (0%) This value is read as a percentage to Sentry,
+# represented as a decimal. Defaults to 15% of traces (0.15)
+#
+#sentry_traces_sample_rate = 0.15
+
+# Whether to attach a stacktrace to Sentry reports.
+#
+#sentry_attach_stacktrace = false
+
+# Send panics to Sentry. This is true by default, but Sentry has to be
+# enabled. The global `sentry` config option must be enabled to send any
+# data.
+#
+#sentry_send_panic = true
+
+# Send errors to sentry. This is true by default, but sentry has to be
+# enabled. This option is only effective in release-mode; forced to false
+# in debug-mode.
+#
+#sentry_send_error = true
+
+# Controls the tracing log level for Sentry to send things like
+# breadcrumbs and transactions
+#
+#sentry_filter = "info"
+
+# Enable the tokio-console. This option is only relevant to developers.
+#
+#	For more information, see:
+# https://conduwuit.puppyirl.gay/development.html#debugging-with-tokio-console
+#
+#tokio_console = false
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#test = false
+
+# Controls whether admin room notices like account registrations, password
+# changes, account deactivations, room directory publications, etc will be
+# sent to the admin room. Update notices and normal admin command
+# responses will still be sent.
+#
+#admin_room_notices = true
+
+# Enable database pool affinity support. On supporting systems, block
+# device queue topologies are detected and the request pool is optimized
+# for the hardware; db_pool_workers is determined automatically.
+#
+#db_pool_affinity = true
+
+# Sets the number of worker threads in the frontend-pool of the database.
+# This number should reflect the I/O capabilities of the system,
+# such as the queue-depth or the number of simultaneous requests in
+# flight. Defaults to 32 or four times the number of CPU cores, whichever
+# is greater.
+#
+# Note: This value is only used if db_pool_affinity is disabled or not
+# detected on the system, otherwise it is determined automatically.
+#
+#db_pool_workers = 32
+
+# When db_pool_affinity is enabled and detected, the size of any worker
+# group will not exceed the determined value. This is necessary when
+# thread-pooling approach does not scale to the full capabilities of
+# high-end hardware; using detected values without limitation could
+# degrade performance.
+#
+# The value is multiplied by the number of cores which share a device
+# queue, since group workers can be scheduled on any of those cores.
+#
+#db_pool_workers_limit = 64
+
+# Determines the size of the queues feeding the database's frontend-pool.
+# The size of the queue is determined by multiplying this value with the
+# number of pool workers. When this queue is full, tokio tasks conducting
+# requests will yield until space is available; this is good for
+# flow-control by avoiding buffer-bloat, but can inhibit throughput if
+# too low.
+#
+#db_pool_queue_mult = 4
+
+# Sets the initial value for the concurrency of streams. This value simply
+# allows overriding the default in the code. The default is 32, which is
+# the same as the default in the code. Note this value is itself
+# overridden by the computed stream_width_scale, unless that is disabled;
+# this value can serve as a fixed-width instead.
+#
+#stream_width_default = 32
+
+# Scales the stream width starting from a base value detected for the
+# specific system. The base value is the database pool worker count
+# determined from the hardware queue size (e.g. 32 for SSD or 64 or 128+
+# for NVMe). This float allows scaling the width up or down by multiplying
+# it (e.g. 1.5, 2.0, etc). The maximum result can be the size of the pool
+# queue (see: db_pool_queue_mult) as any larger value will stall the tokio
+# task. The value can also be scaled down (e.g. 0.5)  to improve
+# responsiveness for many users at the cost of throughput for each.
+#
+# Setting this value to 0.0 causes the stream width to be fixed at the
+# value of stream_width_default. The default scale is 1.0 to match the
+# capabilities detected for the system.
+#
+#stream_width_scale = 1.0
+
+# Sets the initial amplification factor. This controls batch sizes of
+# requests made by each pool worker, multiplying the throughput of each
+# stream. This value is somewhat abstract from specific hardware
+# characteristics and can be significantly larger than any thread count or
+# queue size. This is because each database query may require several
+# index lookups, thus many database queries in a batch may make progress
+# independently while also sharing index and data blocks which may or may
+# not be cached. It is worthwhile to submit huge batches to reduce
+# complexity. The maximum value is 32768, though sufficient hardware is
+# still advised for that.
+#
+#stream_amplification = 1024
+
+# Number of sender task workers; determines sender parallelism. Default is
+# '0' which means the value is determined internally, likely matching the
+# number of tokio worker-threads or number of cores, etc. Override by
+# setting a non-zero value.
+#
+#sender_workers = 0
+
+[global.well_known]
+
+# The server URL that the client well-known file will serve. This should
+# not contain a port, and should just be a valid HTTPS URL.
+#
+# example: "https://matrix.example.com"
+#
+#client =
+
+# The server base domain of the URL with a specific port that the server
+# well-known file will serve. This should contain a port at the end, and
+# should not be a URL.
+#
+# example: "matrix.example.com:443"
+#
+#server =
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#support_page =
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#support_role =
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#support_email =
+
+# This item is undocumented. Please contribute documentation for it.
+#
+#support_mxid =
diff --git a/roles/custom/matrix-conduwuit/templates/env.j2 b/roles/custom/matrix-conduwuit/templates/env.j2
new file mode 100644
index 000000000..026bfe308
--- /dev/null
+++ b/roles/custom/matrix-conduwuit/templates/env.j2
@@ -0,0 +1 @@
+{{ matrix_conduwuit_environment_variables_extension }}
diff --git a/roles/custom/matrix-conduwuit/templates/labels.j2 b/roles/custom/matrix-conduwuit/templates/labels.j2
new file mode 100644
index 000000000..9ef9db4f8
--- /dev/null
+++ b/roles/custom/matrix-conduwuit/templates/labels.j2
@@ -0,0 +1,165 @@
+{% if matrix_conduwuit_container_labels_traefik_enabled %}
+traefik.enable=true
+
+{% if matrix_conduwuit_container_labels_traefik_docker_network %}
+traefik.docker.network={{ matrix_conduwuit_container_labels_traefik_docker_network }}
+{% endif %}
+
+traefik.http.services.matrix-conduwuit.loadbalancer.server.port={{ matrix_conduwuit_config_port_number }}
+
+
+{% if matrix_conduwuit_container_labels_public_client_root_enabled %}
+############################################################
+#                                                          #
+# Public Root path (/)                                     #
+#                                                          #
+############################################################
+
+{% set client_root_middlewares = [] %}
+
+{% if matrix_conduwuit_container_labels_public_client_root_redirection_enabled %}
+{% set client_root_middlewares = client_root_middlewares + ['matrix-conduwuit-client-root-redirect'] %}
+traefik.http.middlewares.matrix-conduwuit-client-root-redirect.redirectregex.regex=(.*)
+traefik.http.middlewares.matrix-conduwuit-client-root-redirect.redirectregex.replacement={{ matrix_conduwuit_container_labels_public_client_root_redirection_url }}
+{% endif %}
+
+traefik.http.routers.matrix-conduwuit-public-client-root.rule={{ matrix_conduwuit_container_labels_public_client_root_traefik_rule }}
+
+traefik.http.routers.matrix-conduwuit-public-client-root.middlewares={{ client_root_middlewares | join(',') }}
+
+{% if matrix_conduwuit_container_labels_public_client_root_traefik_priority | int > 0 %}
+traefik.http.routers.matrix-conduwuit-public-client-root.priority={{ matrix_conduwuit_container_labels_public_client_root_traefik_priority }}
+{% endif %}
+
+traefik.http.routers.matrix-conduwuit-public-client-root.service=matrix-conduwuit
+traefik.http.routers.matrix-conduwuit-public-client-root.entrypoints={{ matrix_conduwuit_container_labels_public_client_root_traefik_entrypoints }}
+traefik.http.routers.matrix-conduwuit-public-client-root.tls={{ matrix_conduwuit_container_labels_public_client_root_traefik_tls | to_json }}
+
+{% if matrix_conduwuit_container_labels_public_client_root_traefik_tls %}
+traefik.http.routers.matrix-conduwuit-public-client-root.tls.certResolver={{ matrix_conduwuit_container_labels_public_client_root_traefik_tls_certResolver }}
+{% endif %}
+
+############################################################
+#                                                          #
+# /Public Root path (/)                                    #
+#                                                          #
+############################################################
+{% endif %}
+
+
+{% if matrix_conduwuit_container_labels_public_client_api_enabled %}
+############################################################
+#                                                          #
+# Public Client-API (/_matrix)                             #
+#                                                          #
+############################################################
+
+traefik.http.routers.matrix-conduwuit-public-client-api.rule={{ matrix_conduwuit_container_labels_public_client_api_traefik_rule }}
+
+{% if matrix_conduwuit_container_labels_public_client_api_traefik_priority | int > 0 %}
+traefik.http.routers.matrix-conduwuit-public-client-api.priority={{ matrix_conduwuit_container_labels_public_client_api_traefik_priority }}
+{% endif %}
+
+traefik.http.routers.matrix-conduwuit-public-client-api.service=matrix-conduwuit
+traefik.http.routers.matrix-conduwuit-public-client-api.entrypoints={{ matrix_conduwuit_container_labels_public_client_api_traefik_entrypoints }}
+
+traefik.http.routers.matrix-conduwuit-public-client-api.tls={{ matrix_conduwuit_container_labels_public_client_api_traefik_tls | to_json }}
+{% if matrix_conduwuit_container_labels_public_client_api_traefik_tls %}
+traefik.http.routers.matrix-conduwuit-public-client-api.tls.certResolver={{ matrix_conduwuit_container_labels_public_client_api_traefik_tls_certResolver }}
+{% endif %}
+
+############################################################
+#                                                          #
+# /Public Client-API (/_matrix)                            #
+#                                                          #
+############################################################
+{% endif %}
+
+
+{% if matrix_conduwuit_container_labels_internal_client_api_enabled %}
+############################################################
+#                                                          #
+# Internal Client-API (/_matrix)                           #
+#                                                          #
+############################################################
+
+traefik.http.routers.matrix-conduwuit-internal-client-api.rule={{ matrix_conduwuit_container_labels_internal_client_api_traefik_rule }}
+
+{% if matrix_conduwuit_container_labels_internal_client_api_traefik_priority | int > 0 %}
+traefik.http.routers.matrix-conduwuit-internal-client-api.priority={{ matrix_conduwuit_container_labels_internal_client_api_traefik_priority }}
+{% endif %}
+
+traefik.http.routers.matrix-conduwuit-internal-client-api.service=matrix-conduwuit
+traefik.http.routers.matrix-conduwuit-internal-client-api.entrypoints={{ matrix_conduwuit_container_labels_internal_client_api_traefik_entrypoints }}
+
+############################################################
+#                                                          #
+# /Internal Client-API (/_matrix)                          #
+#                                                          #
+############################################################
+{% endif %}
+
+
+{% if matrix_conduwuit_container_labels_public_federation_api_enabled %}
+############################################################
+#                                                          #
+# Public Federation-API (/_matrix)                         #
+#                                                          #
+############################################################
+
+traefik.http.routers.matrix-conduwuit-public-federation-api.rule={{ matrix_conduwuit_container_labels_public_federation_api_traefik_rule }}
+
+{% if matrix_conduwuit_container_labels_public_federation_api_traefik_priority | int > 0 %}
+traefik.http.routers.matrix-conduwuit-public-federation-api.priority={{ matrix_conduwuit_container_labels_public_federation_api_traefik_priority }}
+{% endif %}
+
+traefik.http.routers.matrix-conduwuit-public-federation-api.service=matrix-conduwuit
+traefik.http.routers.matrix-conduwuit-public-federation-api.entrypoints={{ matrix_conduwuit_container_labels_public_federation_api_traefik_entrypoints }}
+
+traefik.http.routers.matrix-conduwuit-public-federation-api.tls={{ matrix_conduwuit_container_labels_public_federation_api_traefik_tls | to_json }}
+{% if matrix_conduwuit_container_labels_public_federation_api_traefik_tls %}
+traefik.http.routers.matrix-conduwuit-public-federation-api.tls.certResolver={{ matrix_conduwuit_container_labels_public_federation_api_traefik_tls_certResolver }}
+{% endif %}
+
+############################################################
+#                                                          #
+# /Public Federation-API (/_matrix)                        #
+#                                                          #
+############################################################
+{% endif %}
+
+
+
+
+{% if matrix_conduwuit_container_labels_public_conduwuit_api_enabled %}
+############################################################
+#                                                          #
+# Public Conduwuit-API (/_conduwuit)                       #
+#                                                          #
+############################################################
+
+traefik.http.routers.matrix-conduwuit-public-conduwuit-api.rule={{ matrix_conduwuit_container_labels_public_conduwuit_api_traefik_rule }}
+
+{% if matrix_conduwuit_container_labels_public_conduwuit_api_traefik_priority | int > 0 %}
+traefik.http.routers.matrix-conduwuit-public-conduwuit-api.priority={{ matrix_conduwuit_container_labels_public_conduwuit_api_traefik_priority }}
+{% endif %}
+
+traefik.http.routers.matrix-conduwuit-public-conduwuit-api.service=matrix-conduwuit
+traefik.http.routers.matrix-conduwuit-public-conduwuit-api.entrypoints={{ matrix_conduwuit_container_labels_public_conduwuit_api_traefik_entrypoints }}
+
+traefik.http.routers.matrix-conduwuit-public-conduwuit-api.tls={{ matrix_conduwuit_container_labels_public_conduwuit_api_traefik_tls | to_json }}
+{% if matrix_conduwuit_container_labels_public_conduwuit_api_traefik_tls %}
+traefik.http.routers.matrix-conduwuit-public-conduwuit-api.tls.certResolver={{ matrix_conduwuit_container_labels_public_conduwuit_api_traefik_tls_certResolver }}
+{% endif %}
+
+############################################################
+#                                                          #
+# /Public Conduwuit-API (/_conduwuit)                      #
+#                                                          #
+############################################################
+{% endif %}
+
+
+{% endif %}
+
+{{ matrix_conduwuit_container_labels_additional_labels }}
diff --git a/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2 b/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2
new file mode 100644
index 000000000..5291e33a8
--- /dev/null
+++ b/roles/custom/matrix-conduwuit/templates/systemd/matrix-conduwuit.service.j2
@@ -0,0 +1,51 @@
+#jinja2: lstrip_blocks: "True"
+[Unit]
+Description=conduwuit Matrix homeserver
+{% for service in matrix_conduwuit_systemd_required_services_list %}
+Requires={{ service }}
+After={{ service }}
+{% endfor %}
+
+[Service]
+Type=simple
+Environment="HOME={{ devture_systemd_docker_base_systemd_unit_home_path }}"
+ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-conduwuit 2>/dev/null || true'
+ExecStartPre=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-conduwuit 2>/dev/null || true'
+
+ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} create \
+			--rm \
+			--name=matrix-conduwuit \
+			--log-driver=none \
+			--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
+			--cap-drop=ALL \
+			--read-only \
+			--tmpfs=/tmp:rw,noexec,nosuid,size={{ matrix_conduwuit_tmp_directory_size_mb }}m \
+			--network={{ matrix_conduwuit_container_network }} \
+			--env CONDUWUIT_CONFIG=/etc/conduwuit/conduwuit.toml \
+			--label-file={{ matrix_conduwuit_base_path }}/labels \
+			--mount type=bind,src={{ matrix_conduwuit_data_path }},dst=/var/lib/conduwuit \
+			--mount type=bind,src={{ matrix_conduwuit_config_path }},dst=/etc/conduwuit,ro \
+			{% for arg in matrix_conduwuit_container_extra_arguments %}
+			{{ arg }} \
+			{% endfor %}
+			{{ matrix_conduwuit_docker_image }}
+
+{% for network in matrix_conduwuit_container_additional_networks %}
+ExecStartPre={{ devture_systemd_docker_base_host_command_docker }} network connect {{ network }} matrix-conduwuit
+{% endfor %}
+
+ExecStart={{ devture_systemd_docker_base_host_command_docker }} start --attach matrix-conduwuit
+
+{% if matrix_conduwuit_systemd_service_post_start_delay_seconds != 0 %}
+ExecStartPost=-{{ matrix_host_command_sleep }} {{ matrix_conduwuit_systemd_service_post_start_delay_seconds }}
+{% endif %}
+
+ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} stop --time={{ devture_systemd_docker_base_container_stop_grace_time_seconds }} matrix-conduwuit 2>/dev/null || true'
+ExecStop=-{{ devture_systemd_docker_base_host_command_sh }} -c '{{ devture_systemd_docker_base_host_command_docker }} rm matrix-conduwuit 2>/dev/null || true'
+ExecReload={{ devture_systemd_docker_base_host_command_docker }} exec matrix-conduwuit /bin/sh -c 'kill -HUP 1'
+Restart=always
+RestartSec=30
+SyslogIdentifier=matrix-conduwuit
+
+[Install]
+WantedBy=multi-user.target
diff --git a/roles/custom/matrix-conduwuit/vars/main.yml b/roles/custom/matrix-conduwuit/vars/main.yml
new file mode 100644
index 000000000..02684574c
--- /dev/null
+++ b/roles/custom/matrix-conduwuit/vars/main.yml
@@ -0,0 +1,4 @@
+---
+
+matrix_conduwuit_client_api_url_endpoint_public: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}://{{ matrix_conduwuit_hostname }}/_matrix/client/versions"
+matrix_conduwuit_federation_api_url_endpoint_public: "{{ 'https' if matrix_playbook_ssl_enabled else 'http' }}://{{ matrix_conduwuit_hostname }}:{{ matrix_federation_public_port }}/_matrix/federation/v1/version"
diff --git a/roles/custom/matrix-corporal/defaults/main.yml b/roles/custom/matrix-corporal/defaults/main.yml
index fbffad634..c6829a689 100644
--- a/roles/custom/matrix-corporal/defaults/main.yml
+++ b/roles/custom/matrix-corporal/defaults/main.yml
@@ -5,7 +5,7 @@
 matrix_corporal_enabled: true
 
 # renovate: datasource=docker depName=devture/matrix-corporal
-matrix_corporal_version: 3.0.0
+matrix_corporal_version: 3.1.2
 
 matrix_corporal_container_image_self_build: false
 matrix_corporal_container_image_self_build_repo: "https://github.com/devture/matrix-corporal.git"
diff --git a/roles/custom/matrix-coturn/defaults/main.yml b/roles/custom/matrix-coturn/defaults/main.yml
index edf616129..bda15196a 100644
--- a/roles/custom/matrix-coturn/defaults/main.yml
+++ b/roles/custom/matrix-coturn/defaults/main.yml
@@ -14,9 +14,9 @@ matrix_coturn_docker_image: "{{ matrix_coturn_docker_image_name_prefix }}coturn/
 matrix_coturn_docker_image_name_prefix: "{{ 'localhost/' if matrix_coturn_container_image_self_build else matrix_container_global_registry_prefix }}"
 matrix_coturn_docker_image_force_pull: "{{ matrix_coturn_docker_image.endswith(':latest') }}"
 
-# The Docker network that Coturn would be put into.
+# The Docker network that coturn would be put into.
 #
-# Because Coturn relays traffic to unvalidated IP addresses,
+# Because coturn relays traffic to unvalidated IP addresses,
 # using a dedicated network, isolated from other Docker (and local) services is preferrable.
 #
 # Setting up deny/allow rules with `matrix_coturn_allowed_peer_ips`/`matrix_coturn_denied_peer_ips` is also
@@ -24,7 +24,7 @@ matrix_coturn_docker_image_force_pull: "{{ matrix_coturn_docker_image.endswith('
 #
 # Setting `matrix_coturn_container_network` to 'host' will run the container with host networking,
 # which will drastically improve performance when thousands of ports are opened due to Docker not having to set up forwarding rules for each port.
-# Running with host networking can be dangerous, as it potentially exposes your local network and its services to Coturn peers.
+# Running with host networking can be dangerous, as it potentially exposes your local network and its services to coturn peers.
 # Regardless of the networking mode, we apply a deny list which via `matrix_coturn_denied_peer_ips`,
 # which hopefully prevents access to such private network ranges.
 # When running in host-networking mode, you need to adjust the firewall yourself, so that ports are opened.
@@ -51,17 +51,17 @@ matrix_coturn_container_additional_volumes: []
 # A list of extra arguments to pass to the container
 matrix_coturn_container_extra_arguments: []
 
-# Controls whether the Coturn container exposes its plain STUN port (tcp/3478 and udp/3478 in the container).
+# Controls whether the coturn container exposes its plain STUN port (tcp/3478 and udp/3478 in the container).
 #
 # Takes an "<ip>:<port>" or "<port>" value (e.g. "127.0.0.1:3478"), or empty string to not expose.
 matrix_coturn_container_stun_plain_host_bind_port: "{{ '3478' if matrix_coturn_container_network != 'host' else '' }}"
 
-# Controls whether the Coturn container exposes its TLS STUN port (tcp/5349 and udp/5349 in the container).
+# Controls whether the coturn container exposes its TLS STUN port (tcp/5349 and udp/5349 in the container).
 #
 # Takes an "<ip>:<port>" or "<port>" value (e.g. "127.0.0.1:5349"), or empty string to not expose.
 matrix_coturn_container_stun_tls_host_bind_port: "{{ '5349' if matrix_coturn_container_network != 'host' else '' }}"
 
-# Controls whether the Coturn container exposes its TURN UDP port range and which interface to do it on.
+# Controls whether the coturn container exposes its TURN UDP port range and which interface to do it on.
 #
 # Takes an interface "<ip address>" (e.g. "127.0.0.1"), or empty string to listen on all interfaces.
 # Takes a null/none value (`~`) or 'none' (as a string) to prevent listening.
@@ -85,7 +85,7 @@ matrix_coturn_turn_udp_max_port: 49172
 matrix_coturn_authentication_method: auth-secret
 
 # A shared secret used for authentication when `matrix_coturn_authentication_method` is `auth-secret`.
-# You can put any string here, but generating a strong one is preferred (e.g. `pwgen -s 64 1`).
+# You can put any string here, but generating a strong one is preferred. You can create one with a command like `pwgen -s 64 1`.
 matrix_coturn_turn_static_auth_secret: ""
 
 # A username used authentication when `matrix_coturn_authentication_method` is `lt-cred-mech`.
@@ -93,7 +93,7 @@ matrix_coturn_lt_cred_mech_username: ""
 # A password used authentication when `matrix_coturn_authentication_method` is `lt-cred-mech`.
 matrix_coturn_lt_cred_mech_password: ""
 
-# The external IP address of the machine where Coturn is.
+# The external IP address of the machine where coturn is.
 # If do not define an IP address here or in `matrix_coturn_turn_external_ip_addresses`, auto-detection via an EchoIP service will be done.
 # See `matrix_coturn_turn_external_ip_address_auto_detection_enabled`
 matrix_coturn_turn_external_ip_address: ''
@@ -117,11 +117,11 @@ matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_retries_del
 matrix_coturn_allowed_peer_ips: []
 
 # We block loopback interfaces and private networks by default to prevent private resources from being accessible.
-# This is especially important when Coturn does not run within a container network (e.g. `matrix_coturn_container_network: host`).
+# This is especially important when coturn does not run within a container network (e.g. `matrix_coturn_container_network: host`).
 #
 # Learn more: https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-access-control-protection/
 #
-# If you're running Coturn for local network peers, you may wish to override these rules.
+# If you're running coturn for local network peers, you may wish to override these rules.
 matrix_coturn_denied_peer_ips:
   - 0.0.0.0-0.255.255.255
   - 10.0.0.0-10.255.255.255
diff --git a/roles/custom/matrix-coturn/tasks/setup_install.yml b/roles/custom/matrix-coturn/tasks/setup_install.yml
index 8ee3d5606..30aa742cd 100644
--- a/roles/custom/matrix-coturn/tasks/setup_install.yml
+++ b/roles/custom/matrix-coturn/tasks/setup_install.yml
@@ -32,7 +32,7 @@
     - ansible.builtin.set_fact:
         matrix_coturn_turn_external_ip_address: "{{ result_matrix_coturn_turn_external_ip_address_auto_detection_echoip_response.json.ip }}"
 
-- name: Ensure Matrix Coturn path exists
+- name: Ensure Matrix coturn path exists
   ansible.builtin.file:
     path: "{{ item.path }}"
     state: directory
@@ -43,7 +43,7 @@
     - {path: "{{ matrix_coturn_docker_src_files_path }}", when: "{{ matrix_coturn_container_image_self_build }}"}
   when: "item.when | bool"
 
-- name: Ensure Coturn image is pulled
+- name: Ensure coturn image is pulled
   community.docker.docker_image:
     name: "{{ matrix_coturn_docker_image }}"
     source: "{{ 'pull' if ansible_version.major > 2 or ansible_version.minor > 7 else omit }}"
@@ -57,7 +57,7 @@
 
 - when: "matrix_coturn_container_image_self_build | bool"
   block:
-    - name: Ensure Coturn repository is present on self-build
+    - name: Ensure coturn repository is present on self-build
       ansible.builtin.git:
         repo: "{{ matrix_coturn_container_image_self_build_repo }}"
         dest: "{{ matrix_coturn_docker_src_files_path }}"
@@ -67,7 +67,7 @@
       become_user: "{{ matrix_user_username }}"
       register: matrix_coturn_git_pull_results
 
-    - name: Ensure Coturn Docker image is built
+    - name: Ensure coturn Docker image is built
       community.docker.docker_image:
         name: "{{ matrix_coturn_docker_image }}"
         source: build
@@ -78,7 +78,7 @@
           path: "{{ matrix_coturn_docker_src_files_path }}"
           pull: true
 
-- name: Ensure Coturn configuration path exists
+- name: Ensure coturn configuration path exists
   ansible.builtin.file:
     path: "{{ matrix_coturn_base_path }}"
     state: directory
@@ -94,7 +94,7 @@
     owner: "{{ matrix_user_username }}"
     group: "{{ matrix_user_groupname }}"
 
-- name: Ensure Coturn network is created in Docker
+- name: Ensure coturn network is created in Docker
   when: matrix_coturn_container_network not in ['', 'host']
   community.docker.docker_network:
     name: "{{ matrix_coturn_container_network }}"
diff --git a/roles/custom/matrix-coturn/tasks/validate_config.yml b/roles/custom/matrix-coturn/tasks/validate_config.yml
index 96205b0e0..7fd26e881 100644
--- a/roles/custom/matrix-coturn/tasks/validate_config.yml
+++ b/roles/custom/matrix-coturn/tasks/validate_config.yml
@@ -1,6 +1,6 @@
 ---
 
-- name: (Deprecation) Catch and report renamed Coturn settings
+- name: (Deprecation) Catch and report renamed coturn settings
   ansible.builtin.fail:
     msg: >-
       Your configuration contains a variable, which now has a different name.
@@ -15,7 +15,7 @@
       Invalid authentication method specified in `matrix_coturn_authentication_method`
   when: "matrix_coturn_authentication_method not in ['auth-secret', 'lt-cred-mech']"
 
-- name: Fail if required Coturn settings not defined
+- name: Fail if required coturn settings not defined
   ansible.builtin.fail:
     msg: >-
       You need to define a required configuration setting (`{{ item.name }}`).
diff --git a/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2 b/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2
index c72f2bc08..072975b2d 100644
--- a/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2
+++ b/roles/custom/matrix-coturn/templates/systemd/matrix-coturn.service.j2
@@ -1,6 +1,6 @@
 #jinja2: lstrip_blocks: "True"
 [Unit]
-Description=Matrix Coturn server
+Description=Matrix coturn server
 {% for service in matrix_coturn_systemd_required_services_list %}
 Requires={{ service }}
 After={{ service }}
diff --git a/roles/custom/matrix-dendrite/defaults/main.yml b/roles/custom/matrix-dendrite/defaults/main.yml
index fd6c50ed5..f57947252 100644
--- a/roles/custom/matrix-dendrite/defaults/main.yml
+++ b/roles/custom/matrix-dendrite/defaults/main.yml
@@ -13,7 +13,7 @@ matrix_dendrite_docker_image_path: "matrixdotorg/dendrite-monolith"
 matrix_dendrite_docker_image: "{{ matrix_dendrite_docker_image_name_prefix }}{{ matrix_dendrite_docker_image_path }}:{{ matrix_dendrite_docker_image_tag }}"
 matrix_dendrite_docker_image_name_prefix: "{{ 'localhost/' if matrix_dendrite_container_image_self_build else matrix_container_global_registry_prefix }}"
 # renovate: datasource=docker depName=matrixdotorg/dendrite-monolith
-matrix_dendrite_docker_image_tag: "v0.13.8"
+matrix_dendrite_docker_image_tag: "v0.14.1"
 matrix_dendrite_docker_image_force_pull: "{{ matrix_dendrite_docker_image.endswith(':latest') }}"
 
 matrix_dendrite_base_path: "{{ matrix_base_data_path }}/dendrite"
diff --git a/roles/custom/matrix-dendrite/templates/dendrite.yaml.j2 b/roles/custom/matrix-dendrite/templates/dendrite.yaml.j2
index 4f1c02f21..3b7947260 100644
--- a/roles/custom/matrix-dendrite/templates/dendrite.yaml.j2
+++ b/roles/custom/matrix-dendrite/templates/dendrite.yaml.j2
@@ -12,7 +12,7 @@
 # for "connection_string":
 #   SQLite:     file:filename.db
 #               file:///path/to/filename.db
-#   PostgreSQL: postgresql://user:pass@hostname/database?params=...
+#   PostgreSQL: postgresql://user:pass@hostname/database?params=…
 #
 # SQLite is embedded into Dendrite and therefore no further prerequisites are
 # needed for the database when using SQLite mode. However, performance with
@@ -213,7 +213,7 @@ client_api:
     threshold: {{ matrix_dendrite_client_api_rate_limiting_threshold | to_json }}
     cooloff_ms: {{ matrix_dendrite_client_api_rate_limiting_cooloff_ms | to_json }}
     exempt_user_ids:
-    #  - "@user:{{ matrix_domain }}"
+    #  - "@alice:{{ matrix_domain }}"
 
 # Configuration for the Federation API.
 federation_api:
diff --git a/roles/custom/matrix-dimension/defaults/main.yml b/roles/custom/matrix-dimension/defaults/main.yml
index 1a19e9452..136d9b9ec 100644
--- a/roles/custom/matrix-dimension/defaults/main.yml
+++ b/roles/custom/matrix-dimension/defaults/main.yml
@@ -16,7 +16,7 @@ matrix_dimension_path_prefix: /
 # For information on how to acquire an access token, visit https://t2bot.io/docs/access_tokens
 matrix_dimension_access_token: ""
 
-# Users in form: ['@user1:example.com', '@user2:example.com']
+# Users in form: ['@alice:example.com', '@bob:example.com']
 matrix_dimension_admins: []
 
 # Whether to allow Dimension widgets serve websites with invalid or self signed SSL certificates
diff --git a/roles/custom/matrix-dimension/templates/config.yaml.j2 b/roles/custom/matrix-dimension/templates/config.yaml.j2
index c387c91b6..7a426ad63 100644
--- a/roles/custom/matrix-dimension/templates/config.yaml.j2
+++ b/roles/custom/matrix-dimension/templates/config.yaml.j2
@@ -31,7 +31,7 @@ homeserver:
   accessToken: {{ matrix_dimension_access_token | to_json }}
 
 # These users can modify the integrations this Dimension supports.
-# To access the admin interface, open Dimension in Element and click the settings icon.
+# To access the admin interface, open Dimension in Element Web and click the settings icon.
 admins: {{ matrix_dimension_admins | to_json }}
 
 # IPs and CIDR ranges listed here will be blocked from being widgets.
diff --git a/roles/custom/matrix-email2matrix/defaults/main.yml b/roles/custom/matrix-email2matrix/defaults/main.yml
index 3f5d89d7b..2c55c6661 100644
--- a/roles/custom/matrix-email2matrix/defaults/main.yml
+++ b/roles/custom/matrix-email2matrix/defaults/main.yml
@@ -48,7 +48,7 @@ matrix_email2matrix_smtp_hostname: "{{ matrix_server_fqn_matrix }}"
 #  - MailboxName: "mailbox1"
 #    MatrixRoomId: "!qporfwt:{{ matrix_domain }}"
 #    MatrixHomeserverUrl: "{{ matrix_homeserver_url }}"
-#    MatrixUserId: "@email2matrix:{{ matrix_domain }}"
+#    MatrixUserId: "@email2matrix1:{{ matrix_domain }}"
 #    MatrixAccessToken: "MATRIX_ACCESS_TOKEN_HERE"
 #    IgnoreSubject: false
 #    IgnoreBody: false
@@ -57,7 +57,7 @@ matrix_email2matrix_smtp_hostname: "{{ matrix_server_fqn_matrix }}"
 #  - MailboxName: "mailbox2"
 #    MatrixRoomId: "!aaabaa:{{ matrix_domain }}"
 #    MatrixHomeserverUrl: "{{ matrix_homeserver_url }}"
-#    MatrixUserId: "@email2matrix:{{ matrix_domain }}"
+#    MatrixUserId: "@email2matrix2:{{ matrix_domain }}"
 #    MatrixAccessToken: "MATRIX_ACCESS_TOKEN_HERE"
 #    IgnoreSubject: true
 #    IgnoreBody: false
diff --git a/roles/custom/matrix-media-repo/defaults/main.yml b/roles/custom/matrix-media-repo/defaults/main.yml
index 606b5f245..f9fc4eaaf 100755
--- a/roles/custom/matrix-media-repo/defaults/main.yml
+++ b/roles/custom/matrix-media-repo/defaults/main.yml
@@ -19,7 +19,7 @@ matrix_media_repo_docker_image_path: "t2bot/matrix-media-repo"
 matrix_media_repo_docker_image: "{{ matrix_media_repo_docker_image_name_prefix }}{{ matrix_media_repo_docker_image_path }}:{{ matrix_media_repo_docker_image_tag }}"
 matrix_media_repo_docker_image_name_prefix: "{{ 'localhost/' if matrix_media_repo_container_image_self_build else 'ghcr.io/' }}"
 # renovate: datasource=docker depName=ghcr.io/t2bot/matrix-media-repo
-matrix_media_repo_docker_image_tag: "v1.3.7"
+matrix_media_repo_docker_image_tag: "v1.3.8"
 matrix_media_repo_docker_image_force_pull: "{{ matrix_media_repo_docker_image.endswith(':latest') }}"
 
 matrix_media_repo_base_path: "{{ matrix_base_data_path }}/{{ matrix_media_repo_identifier }}"
@@ -384,7 +384,7 @@ matrix_media_repo_access_tokens_appservices: []
 # See docs/admin.md for information on what these people can do. They must belong to one of the
 # configured homeservers above.
 # matrix_media_repo_admins: [
-#   "@your_username:example.org"
+#   "@alice:example.org"
 # ]
 
 matrix_media_repo_admins: []
diff --git a/roles/custom/matrix-media-repo/templates/media-repo/media-repo.yaml.j2 b/roles/custom/matrix-media-repo/templates/media-repo/media-repo.yaml.j2
index 01d38fc9b..6142bc95b 100644
--- a/roles/custom/matrix-media-repo/templates/media-repo/media-repo.yaml.j2
+++ b/roles/custom/matrix-media-repo/templates/media-repo/media-repo.yaml.j2
@@ -172,7 +172,7 @@ admins:
   | to_nice_yaml(indent=2, width=999999, sort_keys=false) | indent(width=2, first=true) }}
 {% else %}
 #admins:
-#  - "@your_username:example.org"
+#  - "@alice:example.org"
 {% endif %}
 
 # Shared secret auth is useful for applications building on top of the media repository, such
diff --git a/roles/custom/matrix-static-files/defaults/main.yml b/roles/custom/matrix-static-files/defaults/main.yml
index 43cb4e967..248062ab2 100644
--- a/roles/custom/matrix-static-files/defaults/main.yml
+++ b/roles/custom/matrix-static-files/defaults/main.yml
@@ -8,7 +8,7 @@ matrix_static_files_enabled: true
 matrix_static_files_identifier: matrix-static-files
 
 # renovate: datasource=docker depName=joseluisq/static-web-server
-matrix_static_files_version: 2.33.0
+matrix_static_files_version: 2.35.0
 
 matrix_static_files_base_path: "{{ matrix_base_data_path }}/{{ 'static-files' if matrix_static_files_identifier == 'matrix-static-files' else matrix_static_files_identifier }}"
 matrix_static_files_config_path: "{{ matrix_static_files_base_path }}/config"
@@ -161,7 +161,7 @@ matrix_static_files_file_matrix_client_property_m_tile_server_entries_enabled: f
 # Controls the m.tile_server/map_style_url property in the /.well-known/matrix/client file
 matrix_static_files_file_matrix_client_property_m_tile_server_map_style_url: ""
 
-# Controls whether element related entries (io.element.e2ee) should be added to the client well-known.
+# Controls whether Element related entries (io.element.e2ee) should be added to the client well-known.
 # By default if any of the following change from their default this would be set to true:
 # `matrix_static_files_file_matrix_client_property_io_element_e2ee_default`
 # `matrix_static_files_file_matrix_client_property_io_element_e2ee_secure_backup_required`
@@ -169,30 +169,40 @@ matrix_static_files_file_matrix_client_property_m_tile_server_map_style_url: ""
 matrix_static_files_file_matrix_client_property_io_element_e2ee_entries_enabled: "{{ not matrix_static_files_file_matrix_client_property_io_element_e2ee_default or matrix_static_files_file_matrix_client_property_io_element_e2ee_secure_backup_required or matrix_static_files_file_matrix_client_property_io_element_e2ee_secure_backup_setup_methods | length > 0 }}"
 
 # Controls the io.element.e2ee/default property in the /.well-known/matrix/client file,
-# which instructs Element whether it should use End-to-End Encryption by default.
+# which instructs Element clients whether they should use End-to-End Encryption by default.
 # Setting this to false will update `/.well-known/matrix/client` and tell Element clients to avoid E2EE.
 # See: https://github.com/element-hq/element-web/blob/develop/docs/e2ee.md
 matrix_static_files_file_matrix_client_property_io_element_e2ee_default: true
 
 # Controls the io.element.e2ee/secure_backup_required property in the /.well-known/matrix/client file,
-# which instructs Element whether it should require a secure backup set up before Element can be used.
-# Setting this to true will update `/.well-known/matrix/client` and tell Element require a secure backup.
+# which instructs Element clients whether they should require a secure backup set up before they can be used.
+# Setting this to true will update `/.well-known/matrix/client` and tell Element clients require a secure backup.
 # See: https://github.com/element-hq/element-web/blob/develop/docs/e2ee.md
 matrix_static_files_file_matrix_client_property_io_element_e2ee_secure_backup_required: false
 
 # Controls the io.element.e2ee/secure_backup_setup_methods property in the /.well-known/matrix/client file,
-# which instructs Element which backup methods from ["key", "passphrase"] should be used.
-# When an empty list is provided, Element defaults to using both.
-# Setting this to other than empty will update `/.well-known/matrix/client` and tell Element which method to use.
+# which instructs Element clients which backup methods from ["key", "passphrase"] should be used.
+# When an empty list is provided, Element clients default to using both.
+# Setting this to other than empty will update `/.well-known/matrix/client` and tell Element clients which method to use.
 # See: https://github.com/element-hq/element-web/blob/develop/docs/e2ee.md
 matrix_static_files_file_matrix_client_property_io_element_e2ee_secure_backup_setup_methods: []
 
 # Controls the io.element.e2ee/force_disable property in the /.well-known/matrix/client file,
-# which can be set to `true` to instruct Element whether to disable End-to-End Encryption by default
+# which can be set to `true` to instruct Element clients whether to disable End-to-End Encryption by default
 # and to not show encryption related-settings in room settings.
 # See: https://github.com/element-hq/element-web/blob/develop/docs/e2ee.md
 matrix_static_files_file_matrix_client_property_io_element_e2ee_force_disable: false
 
+# Controls whether `cc.etke.synapse-admin`-related entries should be added to the client well-known.
+# By default, if there are entries in `matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin`, we show them (by enabling this).
+matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_enabled: "{{ matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin | default({}) | dict2items | length > 0 }}"
+
+# Controls the cc.etke.synapse-admin property in the /.well-known/matrix/client file.
+# See `matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_entries_enabled`
+matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin: "{{ matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_auto | combine(matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_custom, recursive=True) }}"
+matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_auto: {}
+matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_custom: {}
+
 # Default /.well-known/matrix/client configuration template which covers the generic use case.
 # You can customize it by controlling the various variables inside it.
 #
diff --git a/roles/custom/matrix-static-files/templates/public/.well-known/matrix/client.j2 b/roles/custom/matrix-static-files/templates/public/.well-known/matrix/client.j2
index 99ed488fe..86882893a 100644
--- a/roles/custom/matrix-static-files/templates/public/.well-known/matrix/client.j2
+++ b/roles/custom/matrix-static-files/templates/public/.well-known/matrix/client.j2
@@ -54,4 +54,7 @@
 		"default": {{ matrix_static_files_file_matrix_client_property_io_element_e2ee_default|to_json }}
 	}
 	{% endif %}
+	{% if matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin_enabled %},
+	"cc.etke.synapse-admin": {{ matrix_static_files_file_matrix_client_property_cc_etke_synapse_admin | to_json }}
+	{% endif %}
 }
diff --git a/roles/custom/matrix-sygnal/defaults/main.yml b/roles/custom/matrix-sygnal/defaults/main.yml
index 4dbd8e505..3f9bc77fc 100644
--- a/roles/custom/matrix-sygnal/defaults/main.yml
+++ b/roles/custom/matrix-sygnal/defaults/main.yml
@@ -103,7 +103,7 @@ matrix_sygnal_metrics_prometheus_enabled: false
 #
 # For a more advanced customization, you can extend the default (see `matrix_sygnal_configuration_extension_yaml`)
 # or completely replace this variable with your own template.
-matrix_sygnal_configuration_yaml: "{{ lookup('template', 'templates/sygnal.yaml.j2') }}"
+matrix_sygnal_configuration_yaml: "{{ lookup('template', 'templates/config.yaml.j2') }}"
 
 matrix_sygnal_configuration_extension_yaml: |
   # Your custom YAML configuration for Sygnal goes here.
diff --git a/roles/custom/matrix-sygnal/templates/sygnal.yaml.j2 b/roles/custom/matrix-sygnal/templates/config.yaml.j2
similarity index 100%
rename from roles/custom/matrix-sygnal/templates/sygnal.yaml.j2
rename to roles/custom/matrix-sygnal/templates/config.yaml.j2
diff --git a/roles/custom/matrix-synapse-admin/defaults/main.yml b/roles/custom/matrix-synapse-admin/defaults/main.yml
index 347e83e39..48ccb74c2 100644
--- a/roles/custom/matrix-synapse-admin/defaults/main.yml
+++ b/roles/custom/matrix-synapse-admin/defaults/main.yml
@@ -14,7 +14,7 @@ matrix_synapse_admin_container_image_self_build: false
 matrix_synapse_admin_container_image_self_build_repo: "https://github.com/etkecc/synapse-admin.git"
 
 # renovate: datasource=docker depName=ghcr.io/etkecc/synapse-admin
-matrix_synapse_admin_version: v0.10.3-etke25
+matrix_synapse_admin_version: v0.10.3-etke36
 matrix_synapse_admin_docker_image: "{{ matrix_synapse_admin_docker_image_name_prefix }}etkecc/synapse-admin:{{ matrix_synapse_admin_version }}"
 matrix_synapse_admin_docker_image_name_prefix: "{{ 'localhost/' if matrix_synapse_admin_container_image_self_build else 'ghcr.io/' }}"
 matrix_synapse_admin_docker_image_force_pull: "{{ matrix_synapse_admin_docker_image.endswith(':latest') }}"
@@ -146,7 +146,10 @@ matrix_synapse_admin_path_prefix: /synapse-admin
 #
 # The side-effect of this lookup is that Ansible would even parse the JSON for us, returning a dict.
 # This is unlike what it does when looking up YAML template files (no automatic parsing there).
-matrix_synapse_admin_configuration_default: "{{ lookup('template', 'templates/config.json.j2') }}"
+matrix_synapse_admin_configuration_default:
+  restrictBaseUrl: "{{ matrix_synapse_admin_config_restrictBaseUrl }}"
+  asManagedUsers: "{{ matrix_synapse_admin_config_asManagedUsers }}"
+  menu: "{{ matrix_synapse_admin_config_menu }}"
 
 # Your custom JSON configuration for synapse-admin should go to `matrix_synapse_admin_configuration_extension_json`.
 # This configuration extends the default starting configuration (`matrix_synapse_admin_configuration_default`).
@@ -165,7 +168,10 @@ matrix_synapse_admin_configuration_default: "{{ lookup('template', 'templates/co
 #  }
 matrix_synapse_admin_configuration_extension_json: '{}'
 
-matrix_synapse_admin_configuration_extension: "{{ matrix_synapse_admin_configuration_extension_json | from_json if matrix_synapse_admin_configuration_extension_json | from_json is mapping else {} }}"
+# This is similar to `matrix_synapse_admin_configuration_extension_json`, but intended for use by playbook or group vars
+matrix_synapse_admin_configuration_extension_json_auto: {}
+
+matrix_synapse_admin_configuration_extension: "{{ matrix_synapse_admin_configuration_extension_json_auto | combine(matrix_synapse_admin_configuration_extension_json | from_json if matrix_synapse_admin_configuration_extension_json | from_json is mapping else {}, recursive=True) }}"
 
 # Holds the final synapse-admin configuration (a combination of the default and its extension).
 # You most likely don't need to touch this variable. Instead, see `matrix_synapse_admin_configuration_default`.
@@ -190,10 +196,6 @@ matrix_synapse_admin_config_restrictBaseUrl: "{{ [matrix_homeserver_url] }}"  #
 # ]
 matrix_synapse_admin_config_menu: []
 
-# Controls the supportURL configuration setting, which, if defined, replaces the default link to the Synapse Admin GitHub repository.
-# DEPRECATED: use matrix_synapse_admin_config_menu instead (migrated automatically).
-matrix_synapse_admin_config_supportURL: ''  # noqa var-naming
-
 # Controls the asManagedUsers configuration setting (managed by playbook), which, if defined,
 # restricts modifications of the specified users (e.g., bridge-managed).
 # You should use JS regex syntax to match the user IDs.
diff --git a/roles/custom/matrix-synapse-admin/templates/config.json.j2 b/roles/custom/matrix-synapse-admin/templates/config.json.j2
deleted file mode 100644
index 672a979c5..000000000
--- a/roles/custom/matrix-synapse-admin/templates/config.json.j2
+++ /dev/null
@@ -1,6 +0,0 @@
-{
-	"restrictBaseUrl": {{ matrix_synapse_admin_config_restrictBaseUrl | to_json }},
-	"asManagedUsers": {{ matrix_synapse_admin_config_asManagedUsers | to_json }},
-	"supportURL": {{ matrix_synapse_admin_config_supportURL | to_json }},
-	"menu": {{ matrix_synapse_admin_config_menu | to_json }},
-}
diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml b/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml
index 9be2f11a3..192ece0a2 100644
--- a/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml
+++ b/roles/custom/matrix-synapse-reverse-proxy-companion/defaults/main.yml
@@ -13,7 +13,7 @@
 matrix_synapse_reverse_proxy_companion_enabled: true
 
 # renovate: datasource=docker depName=nginx
-matrix_synapse_reverse_proxy_companion_version: 1.27.2-alpine
+matrix_synapse_reverse_proxy_companion_version: 1.27.3-alpine
 
 matrix_synapse_reverse_proxy_companion_base_path: "{{ matrix_synapse_base_path }}/reverse-proxy-companion"
 matrix_synapse_reverse_proxy_companion_confd_path: "{{ matrix_synapse_reverse_proxy_companion_base_path }}/conf.d"
@@ -61,6 +61,11 @@ matrix_synapse_reverse_proxy_companion_container_labels_traefik_entrypoints: web
 matrix_synapse_reverse_proxy_companion_container_labels_traefik_tls_certResolver: default  # noqa var-naming
 matrix_synapse_reverse_proxy_companion_container_labels_traefik_hostname: ''
 
+# Controls whether a compression middleware will be injected into the middlewares list.
+# This compression middleware is supposed to be defined elsewhere (using labels or a File provider, etc.) and is merely referenced by this router.
+matrix_synapse_reverse_proxy_companion_container_labels_traefik_compression_middleware_enabled: false
+matrix_synapse_reverse_proxy_companion_container_labels_traefik_compression_middleware_name: ""
+
 # Controls whether labels will be added that expose the Client-Server API on a public Traefik entrypoint.
 matrix_synapse_reverse_proxy_companion_container_labels_public_client_api_enabled: true
 matrix_synapse_reverse_proxy_companion_container_labels_public_client_api_traefik_hostname: "{{ matrix_synapse_reverse_proxy_companion_container_labels_traefik_hostname }}"
@@ -185,7 +190,7 @@ matrix_synapse_reverse_proxy_companion_send_timeout: 60
 # For OCSP purposes, we need to define a resolver at the `server{}` level or `http{}` level (we do the latter).
 #
 # Otherwise, we get warnings like this:
-# > [warn] 22#22: no resolver defined to resolve r3.o.lencr.org while requesting certificate status, responder: r3.o.lencr.org, certificate: "/matrix/ssl/config/live/.../fullchain.pem"
+# > [warn] 22#22: no resolver defined to resolve r3.o.lencr.org while requesting certificate status, responder: r3.o.lencr.org, certificate: "/matrix/ssl/config/live/…/fullchain.pem"
 #
 # We point it to the internal Docker resolver, which likely delegates to nameservers defined in `/etc/resolv.conf`.
 matrix_synapse_reverse_proxy_companion_http_level_resolver: 127.0.0.11
@@ -230,6 +235,9 @@ matrix_synapse_reverse_proxy_companion_synapse_media_repository_locations: []
 matrix_synapse_reverse_proxy_companion_synapse_user_dir_locations: []
 matrix_synapse_reverse_proxy_companion_client_server_main_override_locations_regex: ^/_matrix/client/(api/v1|r0|v3|unstable)/(account/3pid/|directory/list/room/|pushrules/|rooms/[^/]+/(forget|upgrade|report)|login/sso/redirect/|register)
 matrix_synapse_reverse_proxy_companion_client_server_sso_override_locations_regex: ^(/_matrix/client/(api/v1|r0|v3|unstable)/login/sso/redirect|/_synapse/client/(pick_username|(new_user_consent|oidc/callback|pick_idp|sso_register)$))
+# Related to MSC4108 (https://github.com/matrix-org/matrix-spec-proposals/pull/4108)
+matrix_synapse_reverse_proxy_companion_client_server_qr_code_login_locations_regex: ^(/_matrix/client/(unstable|v1)/org.matrix.msc4108/rendezvous|/_synapse/client/rendezvous)$
+
 matrix_synapse_reverse_proxy_companion_federation_override_locations_regex: ^/_matrix/federation/v1/openid/userinfo$
 
 # synapse content caching
diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/validate_config.yml b/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/validate_config.yml
index 92d89b57a..4da323182 100644
--- a/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/validate_config.yml
+++ b/roles/custom/matrix-synapse-reverse-proxy-companion/tasks/validate_config.yml
@@ -17,3 +17,5 @@
     - {'name': 'matrix_synapse_reverse_proxy_companion_container_labels_public_federation_api_traefik_entrypoints', when: "{{ matrix_synapse_reverse_proxy_companion_container_labels_public_federation_api_enabled }}"}
 
     - {'name': 'matrix_synapse_reverse_proxy_companion_container_labels_internal_client_api_traefik_entrypoints', when: "{{ matrix_synapse_reverse_proxy_companion_container_labels_internal_client_api_enabled }}"}
+
+    - {'name': 'matrix_synapse_reverse_proxy_companion_container_labels_traefik_compression_middleware_name', when: "{{ matrix_synapse_reverse_proxy_companion_container_labels_traefik_compression_middleware_enabled }}"}
diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/labels.j2 b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/labels.j2
index 44c7e7a82..5120b10e8 100644
--- a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/labels.j2
+++ b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/labels.j2
@@ -16,8 +16,18 @@ traefik.http.services.matrix-synapse-reverse-proxy-companion-federation-api.load
 #                                                          #
 ############################################################
 
+{% set client_api_middlewares = [] %}
+
+{% if matrix_synapse_reverse_proxy_companion_container_labels_traefik_compression_middleware_enabled %}
+{% set client_api_middlewares = client_api_middlewares + [matrix_synapse_reverse_proxy_companion_container_labels_traefik_compression_middleware_name] %}
+{% endif %}
+
 traefik.http.routers.matrix-synapse-reverse-proxy-companion-public-client-api.rule={{ matrix_synapse_reverse_proxy_companion_container_labels_public_client_api_traefik_rule }}
 
+{% if client_api_middlewares | length > 0 %}
+traefik.http.routers.matrix-synapse-reverse-proxy-companion-public-client-api.middlewares={{ client_api_middlewares | join(',') }}
+{% endif %}
+
 {% if matrix_synapse_reverse_proxy_companion_container_labels_public_client_api_traefik_priority | int > 0 %}
 traefik.http.routers.matrix-synapse-reverse-proxy-companion-public-client-api.priority={{ matrix_synapse_reverse_proxy_companion_container_labels_public_client_api_traefik_priority }}
 {% endif %}
@@ -65,12 +75,22 @@ traefik.http.routers.matrix-synapse-reverse-proxy-companion-internal-client-api.
 {% if matrix_synapse_reverse_proxy_companion_container_labels_public_client_synapse_client_api_enabled %}
 ############################################################
 #                                                          #
-# Public Synapse Admin API (/_synapse/client)              #
+# Public Synapse Client API (/_synapse/client)             #
 #                                                          #
 ############################################################
 
+{% set synapse_client_api_middlewares = [] %}
+
+{% if matrix_synapse_reverse_proxy_companion_container_labels_traefik_compression_middleware_enabled %}
+{% set synapse_client_api_middlewares = synapse_client_api_middlewares + [matrix_synapse_reverse_proxy_companion_container_labels_traefik_compression_middleware_name] %}
+{% endif %}
+
 traefik.http.routers.matrix-synapse-reverse-proxy-companion-public-client-synapse-client-api.rule={{ matrix_synapse_reverse_proxy_companion_container_labels_public_client_synapse_client_api_traefik_rule }}
 
+{% if synapse_client_api_middlewares | length > 0 %}
+traefik.http.routers.matrix-synapse-reverse-proxy-companion-public-client-synapse-client-api.middlewares={{ synapse_client_api_middlewares | join(',') }}
+{% endif %}
+
 {% if matrix_synapse_reverse_proxy_companion_container_labels_public_client_synapse_client_api_traefik_priority | int > 0 %}
 traefik.http.routers.matrix-synapse-reverse-proxy-companion-public-client-synapse-client-api.priority={{ matrix_synapse_reverse_proxy_companion_container_labels_public_client_synapse_client_api_traefik_priority }}
 {% endif %}
@@ -85,7 +105,7 @@ traefik.http.routers.matrix-synapse-reverse-proxy-companion-public-client-synaps
 
 ############################################################
 #                                                          #
-# /Public Synapse Admin API (/_synapse/client)             #
+# /Public Synapse Client API (/_synapse/client)            #
 #                                                          #
 ############################################################
 {% endif %}
@@ -98,8 +118,18 @@ traefik.http.routers.matrix-synapse-reverse-proxy-companion-public-client-synaps
 #                                                          #
 ############################################################
 
+{% set synapse_admin_api_middlewares = [] %}
+
+{% if matrix_synapse_reverse_proxy_companion_container_labels_traefik_compression_middleware_enabled %}
+{% set synapse_admin_api_middlewares = synapse_admin_api_middlewares + [matrix_synapse_reverse_proxy_companion_container_labels_traefik_compression_middleware_name] %}
+{% endif %}
+
 traefik.http.routers.matrix-synapse-reverse-proxy-companion-public-client-synapse-admin-api.rule={{ matrix_synapse_reverse_proxy_companion_container_labels_public_client_synapse_admin_api_traefik_rule }}
 
+{% if synapse_admin_api_middlewares | length > 0 %}
+traefik.http.routers.matrix-synapse-reverse-proxy-companion-public-client-synapse-admin-api.middlewares={{ synapse_admin_api_middlewares | join(',') }}
+{% endif %}
+
 {% if matrix_synapse_reverse_proxy_companion_container_labels_public_client_synapse_admin_api_traefik_priority | int > 0 %}
 traefik.http.routers.matrix-synapse-reverse-proxy-companion-public-client-synapse-admin-api.priority={{ matrix_synapse_reverse_proxy_companion_container_labels_public_client_synapse_admin_api_traefik_priority }}
 {% endif %}
@@ -127,8 +157,18 @@ traefik.http.routers.matrix-synapse-reverse-proxy-companion-public-client-synaps
 #                                                          #
 ############################################################
 
+{% set federation_api_middlewares = [] %}
+
+{% if matrix_synapse_reverse_proxy_companion_container_labels_traefik_compression_middleware_enabled %}
+{% set federation_api_middlewares = federation_api_middlewares + [matrix_synapse_reverse_proxy_companion_container_labels_traefik_compression_middleware_name] %}
+{% endif %}
+
 traefik.http.routers.matrix-synapse-reverse-proxy-companion-public-federation-api.rule={{ matrix_synapse_reverse_proxy_companion_container_labels_public_federation_api_traefik_rule }}
 
+{% if federation_api_middlewares | length > 0 %}
+traefik.http.routers.matrix-synapse-reverse-proxy-companion-public-federation-api.middlewares={{ federation_api_middlewares | join(',') }}
+{% endif %}
+
 {% if matrix_synapse_reverse_proxy_companion_container_labels_public_federation_api_traefik_priority | int > 0 %}
 traefik.http.routers.matrix-synapse-reverse-proxy-companion-public-federation-api.priority={{ matrix_synapse_reverse_proxy_companion_container_labels_public_federation_api_traefik_priority }}
 {% endif %}
diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2 b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2
index 0dac97120..d278267dc 100644
--- a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2
+++ b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/conf.d/matrix-synapse-reverse-proxy-companion.conf.j2
@@ -91,9 +91,6 @@ server {
 	server_tokens off;
 	root /dev/null;
 
-	gzip on;
-	gzip_types text/plain application/json;
-
 	{% if matrix_synapse_reverse_proxy_companion_synapse_workers_enabled %}
 		# Client-server overrides -- These locations must go to the main Synapse process
 		location ~ {{ matrix_synapse_reverse_proxy_companion_client_server_main_override_locations_regex }} {
@@ -125,6 +122,23 @@ server {
 			proxy_max_temp_file_size 0;
 		}
 
+		# QR code login (`rendezvous`) locations need to go to the same Synapse process.
+		# It doesn't necessarily need to be the main process, but it needs to be consistent.
+		# For simplicity, we'll send them to the main process though.
+		location ~ {{ matrix_synapse_reverse_proxy_companion_client_server_qr_code_login_locations_regex }} {
+			{# FIXME: This block was copied from the main Synapse fallback below.  It would be better to have it in one place and avoid duplication. #}
+			{# Use the embedded DNS resolver in Docker containers to discover the service #}
+			resolver {{ matrix_synapse_reverse_proxy_companion_http_level_resolver }} valid=5s;
+			set $backend "{{ matrix_synapse_reverse_proxy_companion_client_api_addr }}";
+			proxy_pass http://$backend;
+
+			proxy_set_header Host $host;
+
+			client_body_buffer_size 25M;
+			client_max_body_size {{ matrix_synapse_reverse_proxy_companion_client_api_client_max_body_size_mb }}M;
+			proxy_max_temp_file_size 0;
+		}
+
 		{# Workers redirects BEGIN #}
 
 		{% if generic_workers | length > 0 %}
@@ -235,9 +249,6 @@ server {
 
 	root /dev/null;
 
-	gzip on;
-	gzip_types text/plain application/json;
-
 	{% if matrix_synapse_reverse_proxy_companion_synapse_workers_enabled %}
 		# Federation overrides -- These locations must go to the main Synapse process
 		location ~ {{ matrix_synapse_reverse_proxy_companion_federation_override_locations_regex }} {
@@ -258,14 +269,12 @@ server {
 			# https://tcpipuk.github.io/synapse/deployment/workers.html
 			{{ render_locations_to_upstream(matrix_synapse_reverse_proxy_companion_synapse_room_worker_federation_locations, 'room_workers_upstream') }}
 		{% endif %}
-		{% if federation_reader_workers | length > 0 %}
-			# https://tcpipuk.github.io/synapse/deployment/workers.html
-			{{ render_locations_to_upstream(matrix_synapse_reverse_proxy_companion_synapse_federation_reader_federation_locations, 'federation_reader_workers_upstream') }}
-		{% endif %}
+
 		{% if generic_workers | length > 0 %}
 			# https://matrix-org.github.io/synapse/latest/workers.html#synapseappgeneric_worker
 			{{ render_locations_to_upstream(matrix_synapse_reverse_proxy_companion_synapse_generic_worker_federation_locations, 'generic_workers_upstream') }}
 		{% endif %}
+
 		{% if media_repository_workers | length > 0 %}
 			# https://matrix-org.github.io/synapse/latest/workers.html#synapseappmedia_repository
 			{% for location in matrix_synapse_reverse_proxy_companion_synapse_media_repository_locations %}
@@ -287,6 +296,20 @@ server {
 			}
 			{% endfor %}
 		{% endif %}
+
+		{#
+			This is last, because we'd like more-specific requests (e.g. `/_matrix/federation/v1/media/` that may be handled by a media repository worker, if enabled)
+			to be routed to more specialized workers via their respective `locations` defined earlier (above).
+
+			As https://nginx.org/en/docs/http/ngx_http_core_module.html#location says about location matching:
+			> .. Then regular expressions are checked, in the order of their appearance in the configuration file.
+
+			See: https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3918
+		#}
+		{% if federation_reader_workers | length > 0 %}
+			# https://tcpipuk.github.io/synapse/deployment/workers.html
+			{{ render_locations_to_upstream(matrix_synapse_reverse_proxy_companion_synapse_federation_reader_federation_locations, 'federation_reader_workers_upstream') }}
+		{% endif %}
 	{% endif %}
 
 	{% for configuration_block in matrix_synapse_reverse_proxy_companion_synapse_federation_api_additional_server_configuration_blocks %}
diff --git a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/nginx.conf.j2 b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/nginx.conf.j2
index 119227634..4c532d1fe 100644
--- a/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/nginx.conf.j2
+++ b/roles/custom/matrix-synapse-reverse-proxy-companion/templates/nginx/nginx.conf.j2
@@ -66,7 +66,6 @@ http {
 
 	server_tokens off;
 
-	#gzip on;
 	{# Map directive needed for proxied WebSocket upgrades #}
 	map $http_upgrade $connection_upgrade {
 		default upgrade;
diff --git a/roles/custom/matrix-synapse/defaults/main.yml b/roles/custom/matrix-synapse/defaults/main.yml
index 88ee9cf0a..b45381c56 100644
--- a/roles/custom/matrix-synapse/defaults/main.yml
+++ b/roles/custom/matrix-synapse/defaults/main.yml
@@ -16,7 +16,7 @@ matrix_synapse_enabled: true
 matrix_synapse_github_org_and_repo: element-hq/synapse
 
 # renovate: datasource=docker depName=ghcr.io/element-hq/synapse
-matrix_synapse_version: v1.117.0
+matrix_synapse_version: v1.122.0
 
 matrix_synapse_username: ''
 matrix_synapse_uid: ''
@@ -48,6 +48,10 @@ matrix_synapse_container_image_customizations_enabled: |-
 # The version that will be installed is specified in `matrix_synapse_ext_synapse_s3_storage_provider_version`.
 matrix_synapse_container_image_customizations_s3_storage_provider_installation_enabled: "{{ matrix_synapse_ext_synapse_s3_storage_provider_enabled }}"
 
+# Controls whether to install an old version of boto3 and botocore, to work around the following issue:
+# https://github.com/aws/aws-cli/issues/9214
+matrix_synapse_container_image_customizations_s3_storage_provider_installation_old_boto_workaround_enabled: true
+
 # Controls whether custom build steps will be added to the Dockerfile for installing auto-accept-invite module.
 # The version that will be installed is specified in `matrix_synapse_ext_synapse_auto_accept_invite_version`.
 matrix_synapse_container_image_customizations_auto_accept_invite_installation_enabled: "{{ matrix_synapse_ext_synapse_auto_accept_invite_enabled }}"
@@ -56,7 +60,7 @@ matrix_synapse_container_image_customizations_auto_accept_invite_installation_en
 #
 # Example usage:
 #
-# ```yml
+# ```yaml
 # matrix_synapse_container_image_customizations_templates_enabled: true
 # # The templates are expected to be in a `templates/` subdirectory in
 # matrix_synapse_container_image_customizations_templates_in_container_template_files_relative_path: templates/
@@ -78,7 +82,7 @@ matrix_synapse_container_image_customizations_templates_git_repository_keyscan_h
 
 # matrix_synapse_container_image_customizations_dockerfile_body contains your custom Dockerfile steps
 # for building your customized Synapse image based on the original (upstream) image (`matrix_synapse_docker_image`).
-# A `FROM ...` clause is included automatically so you don't have to.
+# A `FROM …` clause is included automatically so you don't have to.
 #
 # Example:
 # matrix_synapse_container_image_customizations_dockerfile_body_custom: |
@@ -186,6 +190,11 @@ matrix_synapse_container_labels_traefik_entrypoints: web-secure
 matrix_synapse_container_labels_traefik_tls_certResolver: default  # noqa var-naming
 matrix_synapse_container_labels_traefik_hostname: ''
 
+# Controls whether a compression middleware will be injected into the middlewares list.
+# This compression middleware is supposed to be defined elsewhere (using labels or a File provider, etc.) and is merely referenced by this router.
+matrix_synapse_container_labels_traefik_compression_middleware_enabled: false
+matrix_synapse_container_labels_traefik_compression_middleware_name: ""
+
 # Controls whether Matrix-related labels will be added.
 #
 # When set to false, variables like the following take no effect:
@@ -335,7 +344,7 @@ matrix_synapse_goofys_systemd_required_services_list_custom: []
 # This can be set to 0 to remove the delay.
 matrix_synapse_systemd_service_post_start_delay_seconds: 10
 
-matrix_synapse_in_container_python_packages_path: "/usr/local/lib/python3.11/site-packages"
+matrix_synapse_in_container_python_packages_path: "/usr/local/lib/python3.12/site-packages"
 
 # Specifies which template files to use when configuring Synapse.
 # If you'd like to have your own different configuration, feel free to copy and paste
@@ -362,6 +371,30 @@ matrix_synapse_media_retention_local_media_lifetime:
 # should be empty to disable
 matrix_synapse_media_retention_remote_media_lifetime:
 
+# Controls the list of additional oembed providers to be added to the homeserver.
+matrix_synapse_oembed_additional_providers: []
+
+# Controls message retention policies
+matrix_synapse_retention_enabled: false
+# "A single var to control them all" - applied to all retention period vars, applied only if a value is set, e.g. : "1d", "1w", "1m", "1y"
+matrix_synapse_retention_period: ""
+# The default min lifetime, applied only if a value is set, e.g. : "1d", "1w", "1m", "1y"
+matrix_synapse_retention_default_policy_min_lifetime: "{{ matrix_synapse_retention_period }}"
+# The default max lifetime, applied only if a value is set, e.g. : "1d", "1w", "1m", "1y"
+matrix_synapse_retention_default_policy_max_lifetime: "{{ matrix_synapse_retention_period }}"
+# The allowed min lifetime, applied only if a value is set, e.g. : "1d", "1w", "1m", "1y"
+matrix_synapse_retention_allowed_lifetime_min: "{{ matrix_synapse_retention_period }}"
+# The allowed max lifetime, applied only if a value is set, e.g. : "1d", "1w", "1m", "1y"
+matrix_synapse_retention_allowed_lifetime_max: "{{ matrix_synapse_retention_period }}"
+# The list of the purge jobs, structure (all fields are optional, example below contains all available variants):
+# - longest_max_lifetime: "1d"
+#   shortest_max_lifetime: "1d"
+#   interval: "12h"
+# - longest_max_lifetime: "1d"
+# - shortest_max_lifetime: "1d"
+# - interval: "12h"
+matrix_synapse_retention_purge_jobs: []
+
 # The tmpfs at /tmp needs to be large enough to handle multiple concurrent file uploads.
 matrix_synapse_tmp_directory_size_mb: "{{ matrix_synapse_max_upload_size_mb * 50 }}"
 
@@ -981,10 +1014,10 @@ matrix_synapse_workers_media_repository_workers_container_arguments: []
 # Adjusting this value manually is generally not necessary.
 matrix_synapse_enable_media_repo: "{{ not matrix_synapse_ext_media_repo_enabled and (not matrix_synapse_workers_enabled or (matrix_synapse_workers_enabled_list | selectattr('type', 'equalto', 'media_repository') | list | length == 0)) }}"
 
-# matrix_synapse_enable_authenticated_media controls if authenticated media is enabled. If enabled all "old" media remains accessible over the legacy endpoints but new media is blocked.
+# matrix_synapse_enable_authenticated_media controls if authenticated media is enabled.
+# If enabled all "old" media remains accessible over the legacy endpoints but new media is blocked.
 # while this option is enabled all media access and downloads have to be done via authenticated endpoints.
-# FIX_ME_WHEN_DEFAULT_TRUE: This option is going to become set to default true in Synapse at a later date.
-matrix_synapse_enable_authenticated_media: false
+matrix_synapse_enable_authenticated_media: true
 
 # matrix_synapse_media_instance_running_background_jobs populates the `media_instance_running_background_jobs` Synapse configuration used when Synapse workers are in use (`matrix_synapse_workers_enabled`).
 # `media_instance_running_background_jobs` is meant to point to a single media-repository worker, which is dedicated to running background tasks that maintain the media repository.
@@ -1177,6 +1210,10 @@ matrix_synapse_experimental_features_msc3861_admin_token: ''
 # URL to advertise to clients where users can self-manage their account.
 matrix_synapse_experimental_features_msc3861_account_management_url: ''
 
+# Controls whether to enable the "QR code login" experimental feature.
+# Enabling this requires that MSC3861 (see `matrix_synapse_experimental_features_msc3861_enabled`) is also enabled.
+matrix_synapse_experimental_features_msc4108_enabled: false
+
 ################################################################################
 #
 # /Next-generation auth for Matrix, based on OAuth 2.0/OIDC
@@ -1406,7 +1443,7 @@ matrix_synapse_media_storage_providers_auto: |
 # matrix_synapse_media_storage_providers_custom:
 # - module: module.SomeModule
 #   store_local: True
-#   # ...
+#   # …
 matrix_synapse_media_storage_providers_custom: []
 
 matrix_synapse_encryption_enabled_by_default_for_room_type: "off"
diff --git a/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/setup_install.yml b/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/setup_install.yml
index 384f16815..ede73ec9a 100644
--- a/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/setup_install.yml
+++ b/roles/custom/matrix-synapse/tasks/ext/s3-storage-provider/setup_install.yml
@@ -43,7 +43,7 @@
   ansible.builtin.template:
     src: "{{ role_path }}/templates/synapse/ext/s3-storage-provider/systemd/{{ item }}.j2"
     dest: "{{ devture_systemd_docker_base_systemd_path }}/{{ item }}"
-    mode: 0640
+    mode: 0644
   with_items:
     - matrix-synapse-s3-storage-provider-migrate.service
     - matrix-synapse-s3-storage-provider-migrate.timer
diff --git a/roles/custom/matrix-synapse/tasks/validate_config.yml b/roles/custom/matrix-synapse/tasks/validate_config.yml
index e9f02b44c..e1e6fbe27 100644
--- a/roles/custom/matrix-synapse/tasks/validate_config.yml
+++ b/roles/custom/matrix-synapse/tasks/validate_config.yml
@@ -39,6 +39,8 @@
     - {'name': 'matrix_synapse_experimental_features_msc3861_admin_token', when: "{{ matrix_synapse_experimental_features_msc3861_enabled }}"}
     - {'name': 'matrix_synapse_experimental_features_msc3861_account_management_url', when: "{{ matrix_synapse_experimental_features_msc3861_enabled }}"}
 
+    - {'name': 'matrix_synapse_container_labels_traefik_compression_middleware_name', when: "{{ matrix_synapse_container_labels_traefik_compression_middleware_enabled }}"}
+
 - name: Fail if asking for more than 1 instance of single-instance workers
   ansible.builtin.fail:
     msg: >-
@@ -154,3 +156,8 @@
   ansible.builtin.fail:
     msg: "When Synapse is delegating authentication to Matrix Authentication Service, it doesn't make sense to enable the password config (`matrix_synapse_password_config_enabled: true`), because it is not Synapse that is handling authentication. Please remove your `matrix_synapse_password_config_enabled: true` setting before enabling Matrix Authentication Service integration for Synapse. Synapse will refuse to start otherwise."
   when: matrix_synapse_experimental_features_msc3861_enabled and matrix_synapse_password_config_enabled
+
+- name: Fail if QR code login (MSC4108) is enabled while Next-Gen Auth (MSC3861) is not
+  ansible.builtin.fail:
+    msg: "When Synapse QR code login is enabled (MSC4108 via `matrix_synapse_experimental_features_msc4108_enabled`), Next-Gen auth (MSC3861 via `matrix_synapse_experimental_features_msc3861_enabled`) must also be enabled."
+  when: matrix_synapse_experimental_features_msc4108_enabled and not matrix_synapse_experimental_features_msc3861_enabled
diff --git a/roles/custom/matrix-synapse/templates/synapse/customizations/Dockerfile.j2 b/roles/custom/matrix-synapse/templates/synapse/customizations/Dockerfile.j2
index 39367fe09..d01268a4a 100644
--- a/roles/custom/matrix-synapse/templates/synapse/customizations/Dockerfile.j2
+++ b/roles/custom/matrix-synapse/templates/synapse/customizations/Dockerfile.j2
@@ -6,8 +6,12 @@ RUN pip install synapse-auto-accept-invite=={{ matrix_synapse_ext_synapse_auto_a
 {% endif %}
 
 {% if matrix_synapse_container_image_customizations_s3_storage_provider_installation_enabled %}
+{% if matrix_synapse_container_image_customizations_s3_storage_provider_installation_old_boto_workaround_enabled %}
+RUN pip install 'boto3<1.36.0' 'botocore<1.36.0' synapse-s3-storage-provider=={{ matrix_synapse_ext_synapse_s3_storage_provider_version }}
+{% else %}
 RUN pip install synapse-s3-storage-provider=={{ matrix_synapse_ext_synapse_s3_storage_provider_version }}
 {% endif %}
+{% endif %}
 
 {% if matrix_synapse_container_image_customizations_templates_enabled %}
 {#
diff --git a/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2 b/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2
index 89681142d..457726774 100644
--- a/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2
+++ b/roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2
@@ -30,7 +30,7 @@ modules: {{ matrix_synapse_modules|to_json }}
 #
 # The server_name name will appear at the end of usernames and room addresses
 # created on this server. For example if the server_name was example.com,
-# usernames on this server would be in the format @user:example.com
+# usernames on this server would be in the format @alice:example.com
 #
 # In most cases you should avoid using a Matrix specific subdomain such as
 # matrix.example.com or synapse.example.com as the server_name for the same
@@ -55,7 +55,7 @@ pid_file: /homeserver.pid
 #web_client_location: https://riot.example.com/
 
 # The public-facing base URL that clients use to access this Homeserver (not
-# including _matrix/...). This is the same URL a user might enter into the
+# including _matrix/…). This is the same URL a user might enter into the
 # 'Custom Homeserver URL' field on their client. If you use Synapse with a
 # reverse proxy, this should be the URL to reach Synapse via the proxy.
 # Otherwise, it should be the URL to reach Synapse's client HTTP listener (see
@@ -590,26 +590,37 @@ templates:
 # purged are ignored and not stored again.
 #
 retention:
+  {% if matrix_synapse_retention_enabled %}
   # The message retention policies feature is disabled by default. Uncomment the
   # following line to enable it.
   #
-  #enabled: true
+  enabled: {{ matrix_synapse_retention_enabled|to_json }}
 
   # Default retention policy. If set, Synapse will apply it to rooms that lack the
   # 'm.room.retention' state event. Currently, the value of 'min_lifetime' doesn't
   # matter much because Synapse doesn't take it into account yet.
   #
-  #default_policy:
-  #  min_lifetime: 1d
-  #  max_lifetime: 1y
+  {% if matrix_synapse_retention_default_policy_min_lifetime | length > 0 or matrix_synapse_retention_default_policy_max_lifetime | length > 0 %}
+  default_policy:
+  {% if matrix_synapse_retention_default_policy_min_lifetime | length > 0 %}
+    min_lifetime: {{ matrix_synapse_retention_default_policy_min_lifetime|to_json }}
+  {% endif %}
+  {% if matrix_synapse_retention_default_policy_max_lifetime | length > 0 %}
+    max_lifetime: {{ matrix_synapse_retention_default_policy_max_lifetime|to_json }}
+  {% endif %}
+  {% endif %}
 
   # Retention policy limits. If set, and the state of a room contains a
   # 'm.room.retention' event in its state which contains a 'min_lifetime' or a
   # 'max_lifetime' that's out of these bounds, Synapse will cap the room's policy
   # to these limits when running purge jobs.
   #
-  #allowed_lifetime_min: 1d
-  #allowed_lifetime_max: 1y
+  {% if matrix_synapse_retention_allowed_lifetime_min | length > 0 %}
+  allowed_lifetime_min: {{ matrix_synapse_retention_allowed_lifetime_min|to_json }}
+  {% endif %}
+  {% if matrix_synapse_retention_allowed_lifetime_max | length > 0 %}
+  allowed_lifetime_max: {{ matrix_synapse_retention_allowed_lifetime_max|to_json }}
+  {% endif %}
 
   # Server admins can define the settings of the background jobs purging the
   # events which lifetime has expired under the 'purge_jobs' section.
@@ -640,12 +651,8 @@ retention:
   # room's policy to these values is done after the policies are retrieved from
   # Synapse's database (which is done using the range specified in a purge job's
   # configuration).
-  #
-  #purge_jobs:
-  #  - longest_max_lifetime: 3d
-  #    interval: 12h
-  #  - shortest_max_lifetime: 3d
-  #    interval: 1d
+  purge_jobs: {{ matrix_synapse_retention_purge_jobs | to_json }}
+  {% endif %}
 
 
 ## TLS ##
@@ -1235,6 +1242,7 @@ oembed:
   #
   #additional_providers:
   #  - oembed/my_providers.json
+  additional_providers: {{ matrix_synapse_oembed_additional_providers|to_json }}
 
 
 ## Captcha ##
@@ -2454,34 +2462,34 @@ email:
     #
     # Subject to use to notify about one message from one or more user(s) in a
     # room which has a name.
-    #message_from_person_in_room: "[%(app)s] You have a message on %(app)s from %(person)s in the %(room)s room..."
+    #message_from_person_in_room: "[%(app)s] You have a message on %(app)s from %(person)s in the %(room)s room…"
     #
     # Subject to use to notify about one message from one or more user(s) in a
     # room which doesn't have a name.
-    #message_from_person: "[%(app)s] You have a message on %(app)s from %(person)s..."
+    #message_from_person: "[%(app)s] You have a message on %(app)s from %(person)s…"
     #
     # Subject to use to notify about multiple messages from one or more users in
     # a room which doesn't have a name.
-    #messages_from_person: "[%(app)s] You have messages on %(app)s from %(person)s..."
+    #messages_from_person: "[%(app)s] You have messages on %(app)s from %(person)s…"
     #
     # Subject to use to notify about multiple messages in a room which has a
     # name.
-    #messages_in_room: "[%(app)s] You have messages on %(app)s in the %(room)s room..."
+    #messages_in_room: "[%(app)s] You have messages on %(app)s in the %(room)s room…"
     #
     # Subject to use to notify about multiple messages in multiple rooms.
-    #messages_in_room_and_others: "[%(app)s] You have messages on %(app)s in the %(room)s room and others..."
+    #messages_in_room_and_others: "[%(app)s] You have messages on %(app)s in the %(room)s room and others…"
     #
     # Subject to use to notify about multiple messages from multiple persons in
     # multiple rooms. This is similar to the setting above except it's used when
     # the room in which the notification was triggered has no name.
-    #messages_from_person_and_others: "[%(app)s] You have messages on %(app)s from %(person)s and others..."
+    #messages_from_person_and_others: "[%(app)s] You have messages on %(app)s from %(person)s and others…"
     #
     # Subject to use to notify about an invite to a room which has a name.
-    #invite_from_person_to_room: "[%(app)s] %(person)s has invited you to join the %(room)s room on %(app)s..."
+    #invite_from_person_to_room: "[%(app)s] %(person)s has invited you to join the %(room)s room on %(app)s…"
     #
     # Subject to use to notify about an invite to a room which doesn't have a
     # name.
-    #invite_from_person: "[%(app)s] %(person)s has invited you to chat on %(app)s..."
+    #invite_from_person: "[%(app)s] %(person)s has invited you to chat on %(app)s…"
 
     # Subject for emails related to account administration.
     #
@@ -2838,8 +2846,8 @@ opentracing:
     # By default, the list is empty.
     #
     #force_tracing_for_users:
-    #  - "@user1:server_name"
-    #  - "@user2:server_name"
+    #  - "@alice:server_name"
+    #  - "@bob:server_name"
 
     # Jaeger can be configured to sample traces at different rates.
     # All configuration options provided by Jaeger can be set here.
@@ -2986,5 +2994,8 @@ experimental_features:
     admin_token: {{ matrix_synapse_experimental_features_msc3861_admin_token | to_json }}
     account_management_url: {{ matrix_synapse_experimental_features_msc3861_account_management_url | to_json }}
   {% endif %}
+  {% if matrix_synapse_experimental_features_msc4108_enabled %}
+  msc4108_enabled: true
+  {% endif %}
 
 # vim:ft=yaml
diff --git a/roles/custom/matrix-synapse/templates/synapse/labels.j2 b/roles/custom/matrix-synapse/templates/synapse/labels.j2
index fd472b3fc..dd4d776c1 100644
--- a/roles/custom/matrix-synapse/templates/synapse/labels.j2
+++ b/roles/custom/matrix-synapse/templates/synapse/labels.j2
@@ -19,6 +19,10 @@ traefik.http.services.matrix-synapse-metrics.loadbalancer.server.port={{ matrix_
 
 {% set client_root_middlewares = [] %}
 
+{% if matrix_synapse_container_labels_traefik_compression_middleware_enabled %}
+{% set client_root_middlewares = client_root_middlewares + [matrix_synapse_container_labels_traefik_compression_middleware_name] %}
+{% endif %}
+
 {% if matrix_synapse_container_labels_public_client_root_redirection_enabled %}
 {% set client_root_middlewares = client_root_middlewares + ['matrix-synapse-public-client-root-redirect'] %}
 traefik.http.middlewares.matrix-synapse-public-client-root-redirect.redirectregex.regex=(.*)
@@ -66,8 +70,18 @@ traefik.http.routers.matrix-synapse-public-client-root.tls.certResolver={{ matri
 #                                                          #
 ############################################################
 
+{% set client_api_middlewares = [] %}
+
+{% if matrix_synapse_container_labels_traefik_compression_middleware_enabled %}
+{% set client_api_middlewares = client_api_middlewares + [matrix_synapse_container_labels_traefik_compression_middleware_name] %}
+{% endif %}
+
 traefik.http.routers.matrix-synapse-public-client-api.rule={{ matrix_synapse_container_labels_public_client_api_traefik_rule }}
 
+{% if client_api_middlewares | length > 0 %}
+traefik.http.routers.matrix-synapse-public-client-api.middlewares={{ client_api_middlewares | join(',') }}
+{% endif %}
+
 {% if matrix_synapse_container_labels_public_client_api_traefik_priority | int > 0 %}
 traefik.http.routers.matrix-synapse-public-client-api.priority={{ matrix_synapse_container_labels_public_client_api_traefik_priority }}
 {% endif %}
@@ -116,12 +130,22 @@ traefik.http.routers.matrix-synapse-internal-client-api.entrypoints={{ matrix_sy
 {% if matrix_synapse_container_labels_public_client_synapse_client_api_enabled %}
 ############################################################
 #                                                          #
-# Public Synapse Admin API (/_synapse/client)              #
+# Public Synapse Client API (/_synapse/client)             #
 #                                                          #
 ############################################################
 
+{% set synapse_client_api_middlewares = [] %}
+
+{% if matrix_synapse_container_labels_traefik_compression_middleware_enabled %}
+{% set synapse_client_api_middlewares = synapse_client_api_middlewares + [matrix_synapse_container_labels_traefik_compression_middleware_name] %}
+{% endif %}
+
 traefik.http.routers.matrix-synapse-public-client-synapse-client-api.rule={{ matrix_synapse_container_labels_public_client_synapse_client_api_traefik_rule }}
 
+{% if synapse_client_api_middlewares | length > 0 %}
+traefik.http.routers.matrix-synapse-public-client-synapse-client-api.middlewares={{ synapse_client_api_middlewares | join(',') }}
+{% endif %}
+
 {% if matrix_synapse_container_labels_public_client_synapse_client_api_traefik_priority | int > 0 %}
 traefik.http.routers.matrix-synapse-public-client-synapse-client-api.priority={{ matrix_synapse_container_labels_public_client_synapse_client_api_traefik_priority }}
 {% endif %}
@@ -136,7 +160,7 @@ traefik.http.routers.matrix-synapse-public-client-synapse-client-api.tls.certRes
 
 ############################################################
 #                                                          #
-# /Public Synapse Admin API (/_synapse/client)             #
+# /Public Synapse Client API (/_synapse/client)            #
 #                                                          #
 ############################################################
 {% endif %}
@@ -149,8 +173,18 @@ traefik.http.routers.matrix-synapse-public-client-synapse-client-api.tls.certRes
 #                                                          #
 ############################################################
 
+{% set synapse_admin_api_middlewares = [] %}
+
+{% if matrix_synapse_container_labels_traefik_compression_middleware_enabled %}
+{% set synapse_admin_api_middlewares = synapse_admin_api_middlewares + [matrix_synapse_container_labels_traefik_compression_middleware_name] %}
+{% endif %}
+
 traefik.http.routers.matrix-synapse-public-client-synapse-admin-api.rule={{ matrix_synapse_container_labels_public_client_synapse_admin_api_traefik_rule }}
 
+{% if synapse_admin_api_middlewares | length > 0 %}
+traefik.http.routers.matrix-synapse-public-client-synapse-admin-api.middlewares={{ synapse_admin_api_middlewares | join(',') }}
+{% endif %}
+
 {% if matrix_synapse_container_labels_public_client_synapse_admin_api_traefik_priority | int > 0 %}
 traefik.http.routers.matrix-synapse-public-client-synapse-admin-api.priority={{ matrix_synapse_container_labels_public_client_synapse_admin_api_traefik_priority }}
 {% endif %}
@@ -178,8 +212,18 @@ traefik.http.routers.matrix-synapse-public-client-synapse-admin-api.tls.certReso
 #                                                          #
 ############################################################
 
+{% set federation_api_middlewares = [] %}
+
+{% if matrix_synapse_container_labels_traefik_compression_middleware_enabled %}
+{% set federation_api_middlewares = federation_api_middlewares + [matrix_synapse_container_labels_traefik_compression_middleware_name] %}
+{% endif %}
+
 traefik.http.routers.matrix-synapse-public-federation-api.rule={{ matrix_synapse_container_labels_public_federation_api_traefik_rule }}
 
+{% if federation_api_middlewares | length > 0 %}
+traefik.http.routers.matrix-synapse-public-federation-api.middlewares={{ federation_api_middlewares | join(',') }}
+{% endif %}
+
 {% if matrix_synapse_container_labels_public_federation_api_traefik_priority | int > 0 %}
 traefik.http.routers.matrix-synapse-public-federation-api.priority={{ matrix_synapse_container_labels_public_federation_api_traefik_priority }}
 {% endif %}
@@ -216,6 +260,10 @@ traefik.http.routers.matrix-synapse-public-federation-api.tls.certResolver={{ ma
 
 {% set metrics_middlewares = [] %}
 
+{% if matrix_synapse_container_labels_traefik_compression_middleware_enabled %}
+{% set metrics_middlewares = metrics_middlewares + [matrix_synapse_container_labels_traefik_compression_middleware_name] %}
+{% endif %}
+
 {% if matrix_synapse_container_labels_public_metrics_middleware_basic_auth_enabled %}
 {% set metrics_middlewares = metrics_middlewares + ['matrix-synapse-metrics-basic-auth'] %}
 traefik.http.middlewares.matrix-synapse-metrics-basic-auth.basicauth.users={{ matrix_synapse_container_labels_public_metrics_middleware_basic_auth_users }}
diff --git a/roles/custom/matrix-synapse/vars/main.yml b/roles/custom/matrix-synapse/vars/main.yml
index 88edcb187..f47a2e848 100644
--- a/roles/custom/matrix-synapse/vars/main.yml
+++ b/roles/custom/matrix-synapse/vars/main.yml
@@ -246,7 +246,7 @@ matrix_synapse_workers_media_repository_endpoints:
   - ^/_matrix/client/v1/media/
   - ^/_matrix/federation/v1/media/
 
-  # ... and the following regular expressions matching media-specific administration APIs:
+  # … and the following regular expressions matching media-specific administration APIs:
 
   - ^/_synapse/admin/v1/purge_media_cache$
   - ^/_synapse/admin/v1/room/.*/media.*$
diff --git a/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduwuit.yml b/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduwuit.yml
new file mode 100644
index 000000000..a44f982e4
--- /dev/null
+++ b/roles/custom/matrix-user-creator/tasks/util/ensure_user_registered_conduwuit.yml
@@ -0,0 +1,5 @@
+---
+
+- name: Ensure Conduwuit user registered - {{ user.username | quote }}
+  ansible.builtin.debug:
+    msg: "Not registering user. To register Conduwuit users, message the Conduwuit bot"
diff --git a/roles/custom/matrix-user-creator/vars/main.yml b/roles/custom/matrix-user-creator/vars/main.yml
index 7b65bb8aa..7bb3a1a66 100644
--- a/roles/custom/matrix-user-creator/vars/main.yml
+++ b/roles/custom/matrix-user-creator/vars/main.yml
@@ -18,7 +18,7 @@
 #     initial_password: some-password
 #     initial_type: admin
 #
-#   - username: john
+#   - username: alice
 #     initial_password: some-password
 #     initial_type: user
 #
diff --git a/roles/custom/matrix-user-verification-service/defaults/main.yml b/roles/custom/matrix-user-verification-service/defaults/main.yml
index dab9699fe..d46b99194 100644
--- a/roles/custom/matrix-user-verification-service/defaults/main.yml
+++ b/roles/custom/matrix-user-verification-service/defaults/main.yml
@@ -1,4 +1,8 @@
 ---
+
+# matrix-user-verification-service - Service to verify details of a user based on an Open ID token
+# Project source code URL: https://github.com/matrix-org/matrix-user-verification-service
+
 # Set this to the display name for ansible used in Output e.g. fail_msg
 matrix_user_verification_service_ansible_name: "Matrix User Verification Service"
 
diff --git a/roles/custom/matrix_playbook_migration/defaults/main.yml b/roles/custom/matrix_playbook_migration/defaults/main.yml
index b8b13a9e0..ba672d092 100644
--- a/roles/custom/matrix_playbook_migration/defaults/main.yml
+++ b/roles/custom/matrix_playbook_migration/defaults/main.yml
@@ -27,6 +27,9 @@ matrix_playbook_migration_matrix_aux_migration_validation_enabled: true
 # Controls if (`matrix_jitsi` -> `jitsi`) validation will run.
 matrix_playbook_migration_matrix_jitsi_migration_validation_enabled: true
 
+# Controls if (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`) validation will run.
+matrix_playbook_migration_matrix_postmoogle_migration_validation_enabled: true
+
 # Controls if the old apt repository (likely without a `signed-by` option) on Debian-based systems will be removed.
 #
 # Older versions of the Docker role (5.x, 6.x) used to install a repository at a path like: `/etc/apt/sources.list.d/download_docker_com_linux_*`
diff --git a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml
index dccc83816..b3b792a78 100644
--- a/roles/custom/matrix_playbook_migration/tasks/validate_config.yml
+++ b/roles/custom/matrix_playbook_migration/tasks/validate_config.yml
@@ -56,6 +56,7 @@
     - {'old': 'matrix_prometheus_scraper_hookshot_targets', 'new': '<superseded by matrix_prometheus_services_connect_scraper_hookshot_static_configs_target>'}
     - {'old': 'matrix_prometheus_scraper_nginxlog_enabled', 'new': 'matrix_prometheus_services_connect_scraper_nginxlog_enabled'}
     - {'old': 'matrix_prometheus_scraper_nginxlog_server_port', 'new': 'matrix_prometheus_services_connect_scraper_nginxlog_static_configs_target'}
+
     - {'old': 'matrix_prosody_jitsi_max_participants', 'new': 'jitsi_prosody_max_participants'}
     - {'old': 'jitsi_require_well_known', 'new': 'jitsi_web_well_known_element_jitsi_enabled'}
     - {'old': 'jitsi_wellknown_element_jitsi_json', 'new': 'jitsi_web_well_known_element_jitsi_json'}
@@ -63,6 +64,9 @@
     - {'old': 'exim_relay_docker_image_name_prefix', 'new': 'exim_relay_container_image_name_prefix'}
     - {'old': 'exim_relay_docker_image_force_pull', 'new': 'exim_relay_container_image_force_pull'}
 
+    - {'old': 'matrix_playbook_reverse_proxy_traefik_middleware_compession_enabled', 'new': 'matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled'}
+    - {'old': 'matrix_playbook_reverse_proxy_traefik_middleware_compession_name', 'new': 'matrix_playbook_reverse_proxy_traefik_middleware_compression_name'}
+
 - name: (Deprecation) Catch and report matrix_postgres variables
   ansible.builtin.fail:
     msg: |-
@@ -223,6 +227,20 @@
           We found usage of the following variables: {{ matrix_playbook_migration_jitsi_migration_vars.keys() | join(', ') }}
       when: "matrix_playbook_migration_jitsi_migration_vars | length > 0"
 
+- when: matrix_playbook_migration_matrix_postmoogle_migration_validation_enabled | bool
+  block:
+    - ansible.builtin.set_fact:
+        matrix_playbook_migration_postmoogle_migration_vars: |-
+          {{ vars | dict2items | selectattr('key', 'match', 'matrix_bot_postmoogle_.*') | list | items2dict }}
+
+    - name: (Deprecation) Catch and report matrix_bot_postmoogle variables
+      ansible.builtin.fail:
+        msg: >-
+          Your configuration contains a variable, which now has a different name.
+          Please change your configuration (vars.yml) to rename all variables (`matrix_bot_postmoogle_` -> `matrix_postmoogle_`).
+          We found usage of the following variables: {{ matrix_playbook_migration_postmoogle_migration_vars.keys() | join(', ') }}
+      when: "matrix_playbook_migration_postmoogle_migration_vars | length > 0"
+
 - when: matrix_playbook_migration_matrix_nginx_proxy_elimination_variable_transition_checks_enabled | bool
   block:
     - name: (Deprecation) Catch and report transitioned playbook settings during the matrix-nginx-proxy elimination
@@ -258,8 +276,8 @@
         - {'old': 'matrix_nginx_proxy_base_domain_homepage_enabled', 'new': 'matrix_static_files_file_index_html_enabled'}
         - {'old': 'matrix_nginx_proxy_base_domain_homepage_template', 'new': 'matrix_static_files_file_index_html_template'}
         - {'old': 'matrix_nginx_proxy_base_domain_create_directory', 'new': '<no longer necessary; see matrix_static_files_file_index_html_enabled>'}
-        - {'old': 'matrix_nginx_proxy_proxy_riot_compat_redirect_enabled', 'new': '<redirecting the riot domain to an element domain is no longer supported - you can implement it yourself using matrix_client_element_container_labels_additional_labels>'}
-        - {'old': 'matrix_nginx_proxy_proxy_riot_compat_redirect_hostname', 'new': '<redirecting the riot domain to an element domain is no longer supported - you can implement it yourself using matrix_client_element_container_labels_additional_labels>'}
+        - {'old': 'matrix_nginx_proxy_proxy_riot_compat_redirect_enabled', 'new': '<redirecting the Riot domain to an Element domain is no longer supported - you can implement it yourself using matrix_client_element_container_labels_additional_labels>'}
+        - {'old': 'matrix_nginx_proxy_proxy_riot_compat_redirect_hostname', 'new': '<redirecting the Riot domain to an Element domain is no longer supported - you can implement it yourself using matrix_client_element_container_labels_additional_labels>'}
         - {'old': 'matrix_nginx_proxy_proxy_matrix_client_redirect_enabled', 'new': '<superseded by matrix_synapse_container_labels_public_client_root_redirection_enabled or other equivalent variables based on the homeserver implementation you use>'}
         - {'old': 'matrix_nginx_proxy_proxy_matrix_client_redirect_root_uri_to_domain', 'new': '<superseded by matrix_synapse_container_labels_public_client_root_redirection_url or other equivalent variables based on the homeserver implementation you use>'}
         - {'old': 'matrix_nginx_proxy_proxy_matrix_client_api_forwarded_location_synapse_client_api_enabled', 'new': 'matrix_synapse_container_labels_public_client_synapse_client_api_enabled'}
diff --git a/setup.yml b/setup.yml
index 552665046..6cabc7962 100644
--- a/setup.yml
+++ b/setup.yml
@@ -49,6 +49,8 @@
 
     - galaxy/redis
     - galaxy/keydb
+    - galaxy/valkey
+
     - role: custom/matrix-authentication-service
     - custom/matrix-corporal
     - custom/matrix-appservice-draupnir-for-all
@@ -82,6 +84,7 @@
     - custom/matrix-bridge-mx-puppet-slack
     - custom/matrix-bridge-mx-puppet-twitter
     - custom/matrix-bridge-mx-puppet-instagram
+    - custom/matrix-bridge-postmoogle
     - custom/matrix-bridge-sms
     - custom/matrix-bridge-heisenbridge
     - custom/matrix-bridge-hookshot
@@ -91,7 +94,6 @@
     - custom/matrix-bot-buscarron
     - custom/matrix-bot-baibot
     - custom/matrix-bot-honoroit
-    - custom/matrix-bot-postmoogle
     - custom/matrix-bot-go-neb
     - custom/matrix-bot-mjolnir
     - custom/matrix-bot-draupnir
@@ -104,6 +106,7 @@
     - custom/matrix-synapse-reverse-proxy-companion
     - custom/matrix-dendrite
     - custom/matrix-conduit
+    - custom/matrix-conduwuit
     - custom/matrix-synapse-admin
     - custom/matrix-synapse-usage-exporter
     - galaxy/prometheus_node_exporter