Automatic translations update

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

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-06-29 17:11+0000\n"
+"POT-Creation-Date: 2026-07-19 03:41+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -72,86 +72,90 @@ msgstr ""
 msgid "for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:45
+#: ../../../docs/configuring-playbook-ketesa.md:44
+msgid "for [Tuwunel](./configuring-playbook-tuwunel.md): `matrix_tuwunel_container_labels_public_client_synapse_admin_api_enabled: true`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-ketesa.md:46
 msgid "By default, Ketesa installation will be [restricted to only work with one homeserver](https://github.com/etkecc/ketesa/blob/main/README.md#restricting-available-homeserver) — the one managed by the playbook. To adjust these restrictions, tweak the `matrix_ketesa_config_restrictBaseUrl` variable."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:47
+#: ../../../docs/configuring-playbook-ketesa.md:48
 msgid "Adjusting the Ketesa URL (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:49
+#: ../../../docs/configuring-playbook-ketesa.md:50
 msgid "By tweaking the `matrix_ketesa_hostname` and `matrix_ketesa_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-ketesa.md:51
+#: ../../../docs/configuring-playbook-ketesa.md:52
 msgid "We recommend updating the path prefix to `/ketesa` to align with the new branding, while the default `/synapse-admin` is kept for backward compatibility:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:57
+#: ../../../docs/configuring-playbook-ketesa.md:58
 msgid "Or to change the hostname entirely:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:65
+#: ../../../docs/configuring-playbook-ketesa.md:66
 msgid "If you've changed the default hostname, you may need to create a CNAME record for the Ketesa domain (`admin.example.com`), which targets `matrix.example.com`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:67
+#: ../../../docs/configuring-playbook-ketesa.md:68
 msgid "When setting, replace `example.com` with your own."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:69
+#: ../../../docs/configuring-playbook-ketesa.md:70
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:71
+#: ../../../docs/configuring-playbook-ketesa.md:72
 msgid "There are some additional things you may wish to configure about the component."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:73
+#: ../../../docs/configuring-playbook-ketesa.md:74
 msgid "Take a look at:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:75
+#: ../../../docs/configuring-playbook-ketesa.md:76
 msgid "`roles/custom/matrix-ketesa/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_ketesa_configuration_extension_json` variable"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:77
+#: ../../../docs/configuring-playbook-ketesa.md:78
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:79
+#: ../../../docs/configuring-playbook-ketesa.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-ketesa.md:86
+#: ../../../docs/configuring-playbook-ketesa.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-ketesa.md:88
+#: ../../../docs/configuring-playbook-ketesa.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-ketesa.md:90
+#: ../../../docs/configuring-playbook-ketesa.md:91
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:92
+#: ../../../docs/configuring-playbook-ketesa.md:93
 msgid "After installation, Ketesa will be accessible at: `https://matrix.example.com/synapse-admin/` (or `/ketesa/` if you updated the path prefix as recommended)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:94
+#: ../../../docs/configuring-playbook-ketesa.md:95
 msgid "To use Ketesa, you need to have [registered at least one administrator account](registering-users.md) on your server."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:96
+#: ../../../docs/configuring-playbook-ketesa.md:97
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:98
+#: ../../../docs/configuring-playbook-ketesa.md:99
 msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-ketesa`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-ketesa.md:100
+#: ../../../docs/configuring-playbook-ketesa.md:101
 msgid "If you have questions, you can join this community room and feel free to ask: [#ketesa:etke.cc](https://matrix.to/#/#ketesa:etke.cc)"
 msgstr ""

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

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-05-21 19:21+0000\n"
+"POT-Creation-Date: 2026-07-19 03:41+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -201,69 +201,97 @@ msgid "The role sets `default_room_version: '12'`, so newly created rooms defaul
 msgstr ""
 
 #: ../../../docs/configuring-playbook-tuwunel.md:183
-msgid "Creating the first user account"
+msgid "The `/_tuwunel` API path"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-tuwunel.md:185
+msgid "Besides `/_matrix`, Tuwunel serves its own first-party routes under `/_tuwunel`. This namespace carries ad-hoc endpoints such as `/_tuwunel/server_version` and `/_tuwunel/local_user_count`, and the [native OpenID Connect provider](https://matrix-construct.github.io/tuwunel/authentication/oidc-server.html) endpoints (`/_tuwunel/oidc/...`) that clients use when Tuwunel handles OIDC login itself, rather than delegating to an upstream provider as described above. The role routes `/_tuwunel` on the public entrypoint by default so these features work out of the box."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-tuwunel.md:187
+msgid "To keep this namespace off the public entrypoint and expose it only on the internal one, set:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-tuwunel.md:194
+msgid "Exposing the Administration API"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-tuwunel.md:196
+msgid "Tuwunel serves a Synapse-compatible Administration API under the `/_synapse/admin` path, so administration dashboards (such as synapse-admin and ketesa) and moderation bots (such as Draupnir and Meowlnir) work against it. The served endpoints are listed on the [Tuwunel Synapse Admin API page](https://matrix-construct.github.io/tuwunel/development/compliance/synapse-admin.html)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-tuwunel.md:198
+msgid "The API is not routed through the reverse proxy by default. Every endpoint requires an administrator access token, but you may still prefer to keep it off the public entrypoint. To reach it only from trusted networks, expose it on the internal Traefik entrypoint:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-tuwunel.md:204
+msgid "To expose it publicly instead (for example, when a dashboard runs in the browser), set:"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-tuwunel.md:210
+msgid "Creating the first user account"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-tuwunel.md:212
 msgid "Unlike Synapse and Dendrite, Tuwunel does not register users from the command line or via the playbook. On first startup it logs a one-time-use registration token to its journal:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-tuwunel.md:192
+#: ../../../docs/configuring-playbook-tuwunel.md:219
 msgid "Use the token to create your first account from any client that supports token-gated registration (e.g. [Element Web](configuring-playbook-client-element-web.md)). The account is auto-promoted to admin and invited to the admin room together with the `@conduit:<server_name>` server bot. The bot keeps the legacy `conduit` localpart due to the project's lineage from Conduit."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-tuwunel.md:194
+#: ../../../docs/configuring-playbook-tuwunel.md:221
 msgid "Configuring bridges and appservices"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-tuwunel.md:196
+#: ../../../docs/configuring-playbook-tuwunel.md:223
 msgid "The playbook does not auto-register appservices for Tuwunel. After your bridge has produced its `registration.yaml` (e.g. `/matrix/mautrix-signal/bridge/registration.yaml`), register it manually by sending the contents to the admin room, prefixed with `!admin appservices register` and wrapped in a fenced code block:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-tuwunel.md:217
+#: ../../../docs/configuring-playbook-tuwunel.md:244
 msgid "Registrations stored this way are persisted in the database and survive restarts. Re-running the command with the same `id` replaces the existing entry. See [Application services](https://matrix-construct.github.io/tuwunel/appservices.html) for the full reference and admin commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-tuwunel.md:219
+#: ../../../docs/configuring-playbook-tuwunel.md:246
 msgid "Migrating from conduwuit"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-tuwunel.md:221
+#: ../../../docs/configuring-playbook-tuwunel.md:248
 msgid "Tuwunel is a \"binary swap\" for conduwuit; it reads conduwuit's RocksDB layout directly, so migration is a data move, not an export/import."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-tuwunel.md:223
+#: ../../../docs/configuring-playbook-tuwunel.md:250
 msgid "Set `matrix_homeserver_implementation: tuwunel` on `vars.yml` and remove any `matrix_conduwuit_*` overrides."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-tuwunel.md:224
+#: ../../../docs/configuring-playbook-tuwunel.md:251
 msgid "Run a full installation so that the new service is created and the old one removed (e.g. `just setup-all`)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-tuwunel.md:225
+#: ../../../docs/configuring-playbook-tuwunel.md:252
 msgid "Run `just run-tags tuwunel-migrate-from-conduwuit`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-tuwunel.md:227
+#: ../../../docs/configuring-playbook-tuwunel.md:254
 msgid "The migration stops `matrix-conduwuit.service`, copies `/matrix/conduwuit` into `/matrix/tuwunel`, renames the config file, and starts `matrix-tuwunel.service`. The freshly generated tuwunel data directory is preserved alongside as `/matrix/tuwunel_old` until you remove it manually."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-tuwunel.md:230
+#: ../../../docs/configuring-playbook-tuwunel.md:257
 msgid "Migrating from any other Conduit derivative (Conduit itself, Continuwuity, or any other fork) is **not supported** and will corrupt your database. All Conduit forks share the same linear database version with no awareness of each other; switching between them produces unrecoverable damage. See the [upstream migration table](https://matrix-construct.github.io/tuwunel/#migrating-to-tuwunel)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-tuwunel.md:232
+#: ../../../docs/configuring-playbook-tuwunel.md:259
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-tuwunel.md:234
+#: ../../../docs/configuring-playbook-tuwunel.md:261
 msgid "As with all other services, the logs are available via [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html):"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-tuwunel.md:240
+#: ../../../docs/configuring-playbook-tuwunel.md:267
 msgid "Logging verbosity is controlled by `matrix_tuwunel_config_log` in [`tracing-subscriber` env-filter syntax](https://docs.rs/tracing-subscriber/latest/tracing_subscriber/filter/struct.EnvFilter.html). The default (`info,state_res=warn`) is reasonable for production; for debugging, try `debug` or scope it tighter, e.g. `info,tuwunel_service::sending=debug`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-tuwunel.md:242
+#: ../../../docs/configuring-playbook-tuwunel.md:269
 msgid "For RocksDB-level issues, online backups, and offline backup procedures, see the [Tuwunel maintenance guide](https://matrix-construct.github.io/tuwunel/maintenance.html). For protocol-compliance state across MSCs, the spec, and Complement, the project's [compliance dashboard](https://matrix-construct.github.io/tuwunel/development/compliance.html) is the authoritative tracker."
 msgstr ""