diff --git a/i18n/translation-templates/CHANGELOG.pot b/i18n/translation-templates/CHANGELOG.pot index 5c219c98e..40de00c89 100644 --- a/i18n/translation-templates/CHANGELOG.pot +++ b/i18n/translation-templates/CHANGELOG.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-01 17:14+0000\n" +"POT-Creation-Date: 2026-08-13 05:03+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -17,154 +17,214 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #: ../../../CHANGELOG.md:1 -msgid "2026-07-28" +msgid "2026-08-13" msgstr "" #: ../../../CHANGELOG.md:3 -msgid "(Backward Compatibility Break) ntfy users are now declared with hashed passwords" +msgid "The homeserver root path redirects to clients other than Element Web" msgstr "" #: ../../../CHANGELOG.md:5 -msgid "This only affects you if you have enabled authentication for [ntfy](docs/configuring-playbook-ntfy.md) via `ntfy_credentials`." +msgid "Visiting `https://matrix.example.com/` used to redirect you to [Element Web](docs/configuring-playbook-client-element-web.md), but only if Element Web was the client installed by the playbook. With any of the other web clients (Cinny, Commet, FluffyChat, Hydrogen, SchildiChat, Sable), you would land on a bare Synapse page." msgstr "" #: ../../../CHANGELOG.md:7 -msgid "The ntfy role used to create users by invoking `ntfy user` commands against the running container. Since v2.14.0, ntfy can provision users and access-control entries from its own configuration file, so the role now does that instead. Besides being a lot simpler, this fixes passwords containing spaces never arriving intact." +msgid "The redirection now follows whichever of these clients you have enabled. When several are enabled, Element Web wins, followed by the others in the order that [`group_vars/matrix_servers`](group_vars/matrix_servers) lists them." msgstr "" #: ../../../CHANGELOG.md:9 -msgid "Replace `ntfy_credentials` with `ntfy_auth_users_custom`, which takes bcrypt password hashes rather than plaintext passwords:" +msgid "To send people somewhere else (or nowhere at all), define `matrix_playbook_public_client_root_redirection_url` in your `vars.yml` file. An empty value disables the redirection." msgstr "" -#: ../../../CHANGELOG.md:18 -msgid "Generate a hash for each of your passwords by running the following command on any machine which has Docker installed. It asks for the password and prints its hash:" +#: ../../../CHANGELOG.md:11 +msgid "Support for Meowlnir" +msgstr "" + +#: ../../../CHANGELOG.md:13 +msgid "The playbook can now install [Meowlnir](https://github.com/maunium/meowlnir), an opinionated Matrix moderation bot, optimized for Synapse." +msgstr "" + +#: ../../../CHANGELOG.md:15 +msgid "Meowlnir joins [Draupnir](docs/configuring-playbook-bot-draupnir.md) and [Mjolnir](docs/configuring-playbook-bot-mjolnir.md) as a 3rd moderation option, speaking the same [policy list](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists) protocol so that it can subscribe to the same community ban lists. Unlike the others, it can override individual policies coming from lists you do not control (by way of an unban policy in a list of your own which is ordered ahead of other policy lists)." +msgstr "" + +#: ../../../CHANGELOG.md:17 +msgid "You can run it alongside Draupnir while evaluating it — see the documentation for the caveats, the main one being that both want the [synapse-http-antispam](https://github.com/maunium/synapse-http-antispam) module, which only reports to a single consumer." +msgstr "" + +#: ../../../CHANGELOG.md:19 +msgid "To get started, see the [Setting up Meowlnir](docs/configuring-playbook-bot-meowlnir.md) documentation page." +msgstr "" + +#: ../../../CHANGELOG.md:22 +msgid "2026-08-06" msgstr "" #: ../../../CHANGELOG.md:24 -msgid "The playbook will let you know if your configuration still uses `ntfy_credentials`." +msgid "(Backward Compatibility Break) Jitsi no longer uses Colibri WebSockets" msgstr "" #: ../../../CHANGELOG.md:26 -msgid "Your existing ntfy users are left alone and keep working until you declare them again this way. Note that ntfy manages declared users and access-control entries declaratively, so removing one from your configuration later deletes it from ntfy's user database." +msgid "This only affects you if you have [Jitsi](docs/configuring-playbook-jitsi.md) enabled." msgstr "" #: ../../../CHANGELOG.md:28 -msgid "Users with the `admin` role get access to all topics. Others start with no access at all, and can be granted access to specific topics via `ntfy_auth_access_custom`. It is also now possible to control what unauthenticated visitors may do (`ntfy_auth_default_access`) and whether users may log in at all (`ntfy_enable_login`, which follows your authentication setup by default). See the role's [documentation on access control](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/docs/configuring-ntfy.md#enable-access-control-with-authentication-optional) for details." +msgid "Jitsi has been updated to `stable-11146-1`, which [removes Colibri WebSocket support](https://github.com/jitsi/docker-jitsi-meet/pull/2285) in favour of SCTP data channels. The Jitsi Video Bridge no longer serves HTTP at all, so a few `jitsi_jvb_*` variables are gone. The playbook will tell you which ones, if your configuration still sets them." msgstr "" #: ../../../CHANGELOG.md:30 -msgid "Support for bridging to LinkedIn via mautrix-linkedin" +msgid "If you run [additional JVBs on other hosts](https://github.com/mother-of-all-self-hosting/ansible-role-jitsi/blob/main/docs/configuring-jitsi.md#set-up-additional-jvbs-for-more-video-conferences-optional), the Traefik configuration which routed `/colibri-ws//` to them is now dead and can be removed. Nothing will warn you about that one, as it lives in a free-form `traefik_provider_configuration_extension_yaml` block." msgstr "" #: ../../../CHANGELOG.md:32 -msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports bridging to [LinkedIn](https://www.linkedin.com/) via [mautrix-linkedin](https://github.com/mautrix/linkedin)." +msgid "2026-07-28" msgstr "" #: ../../../CHANGELOG.md:34 -msgid "Logging in requires copying a request out of your browser's developer tools, and only works with Chrome or another Chrome-based browser. To learn more, see our [Setting up Mautrix LinkedIn bridging](./docs/configuring-playbook-bridge-mautrix-linkedin.md) documentation page." +msgid "(Backward Compatibility Break) ntfy users are now declared with hashed passwords" msgstr "" #: ../../../CHANGELOG.md:36 -msgid "This bridge supersedes [beeper-linkedin](./docs/configuring-playbook-bridge-beeper-linkedin.md), which is now considered unmaintained (its [upstream repository](https://github.com/beeper/linkedin) has been archived). The old bridge remains installable, but you may wish to switch. Both bridges claim the same appservice namespaces, so the playbook refuses to install mautrix-linkedin while beeper-linkedin is still enabled." +msgid "This only affects you if you have enabled authentication for [ntfy](docs/configuring-playbook-ntfy.md) via `ntfy_credentials`." msgstr "" #: ../../../CHANGELOG.md:38 -msgid "Support for bridging to LINE via beeper-line" +msgid "The ntfy role used to create users by invoking `ntfy user` commands against the running container. Since v2.14.0, ntfy can provision users and access-control entries from its own configuration file, so the role now does that instead. Besides being a lot simpler, this fixes passwords containing spaces never arriving intact." msgstr "" #: ../../../CHANGELOG.md:40 -msgid "Thanks to [Co van Leeuwen](https://github.com/c00), the playbook can now bridge [LINE](https://line.me/) via [beeper-line](https://github.com/beeper/line), a bridge based on the modern mautrix bridge framework. It supports LINE accounts with Letter Sealing enabled or disabled and bridges messages, media, reactions, replies, receipts, and other common chat features." -msgstr "" - -#: ../../../CHANGELOG.md:42 -msgid "The bridge identifies itself as a LINE Chrome Extension client, so it cannot be used at the same time as the real LINE Chrome Extension. See [Setting up Beeper LINE bridging](docs/configuring-playbook-bridge-beeper-line.md) to get started." -msgstr "" - -#: ../../../CHANGELOG.md:45 -msgid "2026-07-19" -msgstr "" - -#: ../../../CHANGELOG.md:47 -msgid "Tuwunel now exposes its administration and /_tuwunel API paths" +msgid "Replace `ntfy_credentials` with `ntfy_auth_users_custom`, which takes bcrypt password hashes rather than plaintext passwords:" msgstr "" #: ../../../CHANGELOG.md:49 -msgid "The [Tuwunel](docs/configuring-playbook-tuwunel.md) role previously routed only the `/_matrix` path through the reverse proxy. It now also exposes the two other API paths that Tuwunel serves." +msgid "Generate a hash for each of your passwords by running the following command on any machine which has Docker installed. It asks for the password and prints its hash:" msgstr "" -#: ../../../CHANGELOG.md:51 -msgid "The Synapse-compatible administration API (`/_synapse/admin`) powers administration dashboards and moderation bots. As with Synapse and Dendrite, the playbook now exposes it automatically when such a tool is installed: publicly for [Ketesa](docs/configuring-playbook-ketesa.md) or [Element Admin](docs/configuring-playbook-element-admin.md), and on the internal entrypoint for [Draupnir](docs/configuring-playbook-bot-draupnir.md). To expose it yourself, set `matrix_tuwunel_container_labels_public_client_synapse_admin_api_enabled: true` (or the `internal_` variant)." +#: ../../../CHANGELOG.md:55 +msgid "The playbook will let you know if your configuration still uses `ntfy_credentials`." msgstr "" -#: ../../../CHANGELOG.md:53 -msgid "Tuwunel also serves first-party routes under `/_tuwunel`, including its native OpenID Connect provider endpoints, which the reverse proxy must route for OIDC login to work. This path is now routed on the public entrypoint by default. To keep it off the public entrypoint, set `matrix_tuwunel_container_labels_public_tuwunel_api_enabled: false`." +#: ../../../CHANGELOG.md:57 +msgid "Your existing ntfy users are left alone and keep working until you declare them again this way. Note that ntfy manages declared users and access-control entries declaratively, so removing one from your configuration later deletes it from ntfy's user database." msgstr "" -#: ../../../CHANGELOG.md:56 -msgid "2026-07-18" +#: ../../../CHANGELOG.md:59 +msgid "Users with the `admin` role get access to all topics. Others start with no access at all, and can be granted access to specific topics via `ntfy_auth_access_custom`. It is also now possible to control what unauthenticated visitors may do (`ntfy_auth_default_access`) and whether users may log in at all (`ntfy_enable_login`, which follows your authentication setup by default). See the role's [documentation on access control](https://github.com/mother-of-all-self-hosting/ansible-role-ntfy/blob/main/docs/configuring-ntfy.md#enable-access-control-with-authentication-optional) for details." msgstr "" -#: ../../../CHANGELOG.md:58 -msgid "LiveKit Server port configuration must be unambiguous now" +#: ../../../CHANGELOG.md:61 +msgid "Support for bridging to LinkedIn via mautrix-linkedin" msgstr "" -#: ../../../CHANGELOG.md:60 -msgid "This only affects you if you have configured a LiveKit Server RTC port range (`livekit_server_config_rtc_port_range_start` and `livekit_server_config_rtc_port_range_end`)." +#: ../../../CHANGELOG.md:63 +msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports bridging to [LinkedIn](https://www.linkedin.com/) via [mautrix-linkedin](https://github.com/mautrix/linkedin)." msgstr "" -#: ../../../CHANGELOG.md:62 -msgid "LiveKit only uses one of the two port configuration mechanisms: when a port range is defined, the multiplexed UDP port (`livekit_server_config_rtc_udp_port`) is ignored entirely. Previously, the role would silently render its default UDP port (7882) into the configuration alongside your port range, misleadingly suggesting that both are in effect." -msgstr "" - -#: ../../../CHANGELOG.md:64 -msgid "The role now asks you to make the choice explicit: if you define a port range, unset the UDP port by adding `livekit_server_config_rtc_udp_port: ''` to your `vars.yml` file. A validation error will guide you, if your configuration is affected." +#: ../../../CHANGELOG.md:65 +msgid "Logging in requires copying a request out of your browser's developer tools, and only works with Chrome or another Chrome-based browser. To learn more, see our [Setting up Mautrix LinkedIn bridging](./docs/configuring-playbook-bridge-mautrix-linkedin.md) documentation page." msgstr "" #: ../../../CHANGELOG.md:67 -msgid "2026-07-17" +msgid "This bridge supersedes [beeper-linkedin](./docs/configuring-playbook-bridge-beeper-linkedin.md), which is now considered unmaintained (its [upstream repository](https://github.com/beeper/linkedin) has been archived). The old bridge remains installable, but you may wish to switch. Both bridges claim the same appservice namespaces, so the playbook refuses to install mautrix-linkedin while beeper-linkedin is still enabled." msgstr "" #: ../../../CHANGELOG.md:69 -msgid "prometheus-nginxlog-exporter metric names have changed" +msgid "Support for bridging to LINE via beeper-line" msgstr "" #: ../../../CHANGELOG.md:71 -msgid "If you have enabled [metrics for nginx logs](docs/configuring-playbook-prometheus-grafana.md) (`prometheus_nginxlog_exporter_enabled: true`), note that the exporter's metric names have changed." +msgid "Thanks to [Co van Leeuwen](https://github.com/c00), the playbook can now bridge [LINE](https://line.me/) via [beeper-line](https://github.com/beeper/line), a bridge based on the modern mautrix bridge framework. It supports LINE accounts with Letter Sealing enabled or disabled and bridges messages, media, reactions, replies, receipts, and other common chat features." msgstr "" #: ../../../CHANGELOG.md:73 -msgid "The exporter's configuration used to ship a leftover `myprefix` placeholder as the metric name prefix, producing metrics like `myprefix_http_response_count_total`. The bundled Grafana dashboard queries unprefixed metric names (`http_response_count_total`), so it could never show any data (reported in [#3380](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3380))." +msgid "The bridge identifies itself as a LINE Chrome Extension client, so it cannot be used at the same time as the real LINE Chrome Extension. See [Setting up Beeper LINE bridging](docs/configuring-playbook-bridge-beeper-line.md) to get started." msgstr "" -#: ../../../CHANGELOG.md:75 -msgid "Metric names are now unprefixed, matching the bundled dashboard, which should start working. Each metric carries a `namespace` label, whose value is now `nginx` (previously `matrix`); it is configurable via `prometheus_nginxlog_exporter_config_namespace_name`. If you have built custom dashboards or alerts on top of the old `myprefix_*` metric names, adjust them accordingly, or restore the old behavior by setting `prometheus_nginxlog_exporter_config_namespace_metrics_prefix: myprefix` in your `vars.yml` file." +#: ../../../CHANGELOG.md:76 +msgid "2026-07-19" msgstr "" #: ../../../CHANGELOG.md:78 -msgid "2026-07-16" +msgid "Tuwunel now exposes its administration and /_tuwunel API paths" msgstr "" #: ../../../CHANGELOG.md:80 -msgid "(Backward Compatibility Break) Bridge variables have been renamed" +msgid "The [Tuwunel](docs/configuring-playbook-tuwunel.md) role previously routed only the `/_matrix` path through the reverse proxy. It now also exposes the two other API paths that Tuwunel serves." msgstr "" #: ../../../CHANGELOG.md:82 -msgid "All bridge roles (`roles/custom/matrix-bridge-*`) now use a uniform variable naming scheme, where the variable prefix matches the role directory name. This adopts the naming policy proposed in [#4705](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/4705) and requested in [#5096](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5096)." +msgid "The Synapse-compatible administration API (`/_synapse/admin`) powers administration dashboards and moderation bots. As with Synapse and Dendrite, the playbook now exposes it automatically when such a tool is installed: publicly for [Ketesa](docs/configuring-playbook-ketesa.md) or [Element Admin](docs/configuring-playbook-element-admin.md), and on the internal entrypoint for [Draupnir](docs/configuring-playbook-bot-draupnir.md). To expose it yourself, set `matrix_tuwunel_container_labels_public_client_synapse_admin_api_enabled: true` (or the `internal_` variant)." msgstr "" #: ../../../CHANGELOG.md:84 +msgid "Tuwunel also serves first-party routes under `/_tuwunel`, including its native OpenID Connect provider endpoints, which the reverse proxy must route for OIDC login to work. This path is now routed on the public entrypoint by default. To keep it off the public entrypoint, set `matrix_tuwunel_container_labels_public_tuwunel_api_enabled: false`." +msgstr "" + +#: ../../../CHANGELOG.md:87 +msgid "2026-07-18" +msgstr "" + +#: ../../../CHANGELOG.md:89 +msgid "LiveKit Server port configuration must be unambiguous now" +msgstr "" + +#: ../../../CHANGELOG.md:91 +msgid "This only affects you if you have configured a LiveKit Server RTC port range (`livekit_server_config_rtc_port_range_start` and `livekit_server_config_rtc_port_range_end`)." +msgstr "" + +#: ../../../CHANGELOG.md:93 +msgid "LiveKit only uses one of the two port configuration mechanisms: when a port range is defined, the multiplexed UDP port (`livekit_server_config_rtc_udp_port`) is ignored entirely. Previously, the role would silently render its default UDP port (7882) into the configuration alongside your port range, misleadingly suggesting that both are in effect." +msgstr "" + +#: ../../../CHANGELOG.md:95 +msgid "The role now asks you to make the choice explicit: if you define a port range, unset the UDP port by adding `livekit_server_config_rtc_udp_port: ''` to your `vars.yml` file. A validation error will guide you, if your configuration is affected." +msgstr "" + +#: ../../../CHANGELOG.md:98 +msgid "2026-07-17" +msgstr "" + +#: ../../../CHANGELOG.md:100 +msgid "prometheus-nginxlog-exporter metric names have changed" +msgstr "" + +#: ../../../CHANGELOG.md:102 +msgid "If you have enabled [metrics for nginx logs](docs/configuring-playbook-prometheus-grafana.md) (`prometheus_nginxlog_exporter_enabled: true`), note that the exporter's metric names have changed." +msgstr "" + +#: ../../../CHANGELOG.md:104 +msgid "The exporter's configuration used to ship a leftover `myprefix` placeholder as the metric name prefix, producing metrics like `myprefix_http_response_count_total`. The bundled Grafana dashboard queries unprefixed metric names (`http_response_count_total`), so it could never show any data (reported in [#3380](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3380))." +msgstr "" + +#: ../../../CHANGELOG.md:106 +msgid "Metric names are now unprefixed, matching the bundled dashboard, which should start working. Each metric carries a `namespace` label, whose value is now `nginx` (previously `matrix`); it is configurable via `prometheus_nginxlog_exporter_config_namespace_name`. If you have built custom dashboards or alerts on top of the old `myprefix_*` metric names, adjust them accordingly, or restore the old behavior by setting `prometheus_nginxlog_exporter_config_namespace_metrics_prefix: myprefix` in your `vars.yml` file." +msgstr "" + +#: ../../../CHANGELOG.md:109 +msgid "2026-07-16" +msgstr "" + +#: ../../../CHANGELOG.md:111 +msgid "(Backward Compatibility Break) Bridge variables have been renamed" +msgstr "" + +#: ../../../CHANGELOG.md:113 +msgid "All bridge roles (`roles/custom/matrix-bridge-*`) now use a uniform variable naming scheme, where the variable prefix matches the role directory name. This adopts the naming policy proposed in [#4705](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/4705) and requested in [#5096](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5096)." +msgstr "" + +#: ../../../CHANGELOG.md:115 msgid "Previously, bridge variable prefixes were all over the place (`matrix_mautrix_telegram_*`, `matrix_heisenbridge_*`, `matrix_steam_bridge_*`, etc.). Now, they all follow the same pattern that bot roles (`matrix_bot__*`) have been using for years: the `matrix-bridge-mautrix-telegram` role uses `matrix_bridge_mautrix_telegram_*` variables, the `matrix-bridge-steam` role uses `matrix_bridge_steam_*` variables, and so on." msgstr "" -#: ../../../CHANGELOG.md:86 +#: ../../../CHANGELOG.md:117 msgid "Only Ansible variables were renamed. Systemd service names, container names, `/matrix/*` directories, database names and usernames, and appservice registration contents (tokens, bot usernames) all remain the same. No data migration is necessary and bridges keep working as before, once you rename the variables in your `vars.yml` configuration file." msgstr "" -#: ../../../CHANGELOG.md:88 +#: ../../../CHANGELOG.md:119 msgid "The playbook will let you know if your configuration still uses old-style variable names." msgstr "" -#: ../../../CHANGELOG.md:90 +#: ../../../CHANGELOG.md:121 msgid "Here is the full rename map:" msgstr "" @@ -400,8603 +460,8603 @@ msgstr "" msgid "`matrix_bridge_wechat_`" msgstr "" -#: ../../../CHANGELOG.md:123 +#: ../../../CHANGELOG.md:154 msgid "A few special cases beyond the prefix map:" msgstr "" -#: ../../../CHANGELOG.md:125 +#: ../../../CHANGELOG.md:156 msgid "`matrix_mautrix_signal_wsproxy_syncproxy_connection_string` (a variable of the mautrix-wsproxy role, despite its name) is now `matrix_bridge_mautrix_wsproxy_syncproxy_connection_string`" msgstr "" -#: ../../../CHANGELOG.md:126 +#: ../../../CHANGELOG.md:157 msgid "`matrix_playbook_migration_matrix_postmoogle_migration_validation_enabled` is now `matrix_playbook_migration_matrix_bridge_postmoogle_migration_validation_enabled`" msgstr "" -#: ../../../CHANGELOG.md:128 +#: ../../../CHANGELOG.md:159 msgid "You can update your `vars.yml` file automatically with this `sed` command (on macOS, use `sed -i ''` instead of `sed -i`):" msgstr "" -#: ../../../CHANGELOG.md:165 +#: ../../../CHANGELOG.md:196 msgid "The `sed` command only replaces prefixes followed by an underscore, so values that intentionally match old prefixes (like the default database names, e.g. `matrix_mautrix_telegram`) are not affected." msgstr "" -#: ../../../CHANGELOG.md:167 +#: ../../../CHANGELOG.md:198 msgid "**Note**: if you have defined your own custom variables whose names embed an old prefix (e.g. `vault_matrix_postmoogle_password` referencing a secret in an Ansible Vault file), the `sed` command renames such references too. Either rename your custom variables to match (including their definitions in encrypted vault files, which `sed` cannot reach), or revert those spots manually." msgstr "" -#: ../../../CHANGELOG.md:169 +#: ../../../CHANGELOG.md:200 msgid "2026-07-15" msgstr "" -#: ../../../CHANGELOG.md:171 +#: ../../../CHANGELOG.md:202 msgid "Google Voice bridging" msgstr "" -#: ../../../CHANGELOG.md:173 +#: ../../../CHANGELOG.md:204 msgid "The playbook can now bridge [Google Voice](https://voice.google.com/) via the [mautrix-gvoice](https://github.com/mautrix/gvoice) bridge. Text and media flow both ways, and portal rooms build themselves for your recent conversations." msgstr "" -#: ../../../CHANGELOG.md:175 +#: ../../../CHANGELOG.md:206 msgid "Login is by cookie, not a paired phone: you copy the cookies from a browser signed in to voice.google.com and hand them to the bot. Google expires them on its own schedule, so expect to log in again every so often. See [Setting up Mautrix Google Voice bridging](./docs/configuring-playbook-bridge-mautrix-gvoice.md) to get started." msgstr "" -#: ../../../CHANGELOG.md:177 +#: ../../../CHANGELOG.md:208 msgid "matrix-appservice-kakaotalk has been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:179 +#: ../../../CHANGELOG.md:210 msgid "The [matrix-appservice-kakaotalk](./docs/configuring-playbook-bridge-appservice-kakaotalk.md) bridge has been removed from the playbook. This component could only be installed by self-building its source code, and its upstream repository has become unreachable, which makes installation impossible. The bridge was also based on the unmaintained node-kakao library, and there have been reports that using it may get KakaoTalk accounts banned." msgstr "" -#: ../../../CHANGELOG.md:181 +#: ../../../CHANGELOG.md:212 msgid "The playbook will let you know if you're using any `matrix_appservice_kakaotalk_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-bridge-appservice-kakaotalk.md#uninstalling-the-component-manually)." msgstr "" -#: ../../../CHANGELOG.md:183 +#: ../../../CHANGELOG.md:214 msgid "Dedicated CAPTCHA variables for Matrix Authentication Service" msgstr "" -#: ../../../CHANGELOG.md:185 +#: ../../../CHANGELOG.md:216 msgid "[Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) can now be protected with CAPTCHA (ReCaptcha v2, Cloudflare Turnstile, or hCaptcha) via dedicated variables, instead of going through `matrix_authentication_service_configuration_extension_yaml`. See the [captcha documentation](./docs/configuring-captcha.md#matrix-authentication-service) for details." msgstr "" -#: ../../../CHANGELOG.md:187 +#: ../../../CHANGELOG.md:218 msgid "2026-07-14" msgstr "" -#: ../../../CHANGELOG.md:189 +#: ../../../CHANGELOG.md:220 msgid "The playbook no longer ships a custom welcome page for Element Web" msgstr "" -#: ../../../CHANGELOG.md:191 +#: ../../../CHANGELOG.md:222 msgid "Element Web [redesigned its welcome page](https://github.com/element-hq/element-web/pull/33211) (the screen shown at `/#/welcome` before logging in) into a built-in component and no longer loads a custom `welcome.html` file by default. Since the playbook upgraded to an Element Web version containing that change (spring 2026), the custom welcome page the playbook installed (and the variables customizing it) had silently stopped having any effect." msgstr "" -#: ../../../CHANGELOG.md:193 +#: ../../../CHANGELOG.md:224 msgid "The playbook now embraces the new upstream behavior and no longer ships its own `welcome.html`. The following variables have been removed and the playbook will let you know if you're still using them: `matrix_client_element_welcome_headline`, `matrix_client_element_welcome_text`, `matrix_client_element_welcome_logo_link` and `matrix_client_element_page_template_welcome_path`." msgstr "" -#: ../../../CHANGELOG.md:195 +#: ../../../CHANGELOG.md:226 msgid "Most welcome page customizations keep working, because they go through Element Web's branding configuration, which the new welcome page still honors:" msgstr "" -#: ../../../CHANGELOG.md:197 +#: ../../../CHANGELOG.md:228 msgid "a custom logo, via `matrix_client_element_welcome_logo` (or `matrix_client_element_branding_auth_header_logo_url`)" msgstr "" -#: ../../../CHANGELOG.md:198 +#: ../../../CHANGELOG.md:229 msgid "a custom background, via `matrix_client_element_branding_welcome_background_url`" msgstr "" -#: ../../../CHANGELOG.md:200 +#: ../../../CHANGELOG.md:231 msgid "If you need a fully custom welcome page, you can self-host an HTML page and point Element Web at it, like this:" msgstr "" -#: ../../../CHANGELOG.md:211 +#: ../../../CHANGELOG.md:242 msgid "BorgBackup now includes Synapse's local thumbnails" msgstr "" -#: ../../../CHANGELOG.md:213 +#: ../../../CHANGELOG.md:244 msgid "For Synapse servers, the built-in [BorgBackup](./docs/configuring-playbook-backup-borg.md) integration no longer excludes the media store's `local_thumbnails` directory from backups." msgstr "" -#: ../../../CHANGELOG.md:215 +#: ../../../CHANGELOG.md:246 msgid "Synapse only generates thumbnails of local media at upload time (unless `dynamic_thumbnails` is enabled, which the playbook does not do), and there is no tooling to regenerate them. Restoring a backup made with the previous exclusion list therefore left all previously uploaded local images without thumbnails. The [official Synapse backup guide](https://element-hq.github.io/synapse/latest/usage/administration/backups.html) recommends backing this directory up, and the playbook now follows that recommendation." msgstr "" -#: ../../../CHANGELOG.md:217 +#: ../../../CHANGELOG.md:248 msgid "Expect your backups to grow somewhat, depending on how much image media your local users have uploaded. If you prefer the old behavior, you can redefine `backup_borg_location_exclude_patterns` in your `vars.yml`." msgstr "" -#: ../../../CHANGELOG.md:219 +#: ../../../CHANGELOG.md:250 msgid "2026-07-12" msgstr "" -#: ../../../CHANGELOG.md:221 +#: ../../../CHANGELOG.md:252 msgid "matrix-registration-bot has been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:223 +#: ../../../CHANGELOG.md:254 msgid "The [matrix-registration-bot](./docs/configuring-playbook-bot-matrix-registration-bot.md) service has been removed from the playbook, as it has been unmaintained." msgstr "" -#: ../../../CHANGELOG.md:225 +#: ../../../CHANGELOG.md:256 msgid "The playbook will let you know if you're using any `matrix_bot_matrix_registration_bot_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-bot-matrix-registration-bot.md#uninstalling-the-component-manually)." msgstr "" -#: ../../../CHANGELOG.md:227 +#: ../../../CHANGELOG.md:258 msgid "Continuwuity v26 no longer supports LDAP" msgstr "" -#: ../../../CHANGELOG.md:229 +#: ../../../CHANGELOG.md:260 msgid "The playbook now installs [Continuwuity](./docs/configuring-playbook-continuwuity.md) v26, a major upgrade from the v0.5.x series which **removes LDAP authentication support** (see the [v26.6.0 release notes](https://forgejo.ellis.link/continuwuation/continuwuity/releases/tag/v26.6.0))." msgstr "" -#: ../../../CHANGELOG.md:231 +#: ../../../CHANGELOG.md:262 msgid "The playbook never exposed dedicated variables for Continuwuity's LDAP support, so most people are unaffected. However, if you had enabled LDAP via `matrix_continuwuity_environment_variables_extension` or a custom configuration template, you'll need to migrate to another authentication method, such as the newly introduced [OpenID Connect support](https://continuwuity.org/guides/oidc)." msgstr "" -#: ../../../CHANGELOG.md:233 +#: ../../../CHANGELOG.md:264 msgid "2026-06-29" msgstr "" -#: ../../../CHANGELOG.md:235 +#: ../../../CHANGELOG.md:266 msgid "Support for running on Synology DSM" msgstr "" -#: ../../../CHANGELOG.md:237 +#: ../../../CHANGELOG.md:268 msgid "Thanks to [cksit](https://github.com/cksit), the playbook can now run on [Synology DSM](https://www.synology.com/dsm) 7 and later." msgstr "" -#: ../../../CHANGELOG.md:239 +#: ../../../CHANGELOG.md:270 msgid "Synology hosts are detected automatically (via `/etc/synoinfo.conf`), so other systems are unaffected. On DSM, the playbook uses the platform's native user management (`synouser`/`synogroup`), works around a Docker SDK incompatibility, and installs a small boot-fix service that handles a few DSM-specific boot quirks." msgstr "" -#: ../../../CHANGELOG.md:241 +#: ../../../CHANGELOG.md:272 msgid "To get started, see the new [Configuring Synology DSM](./docs/configuring-playbook-synology.md) documentation page." msgstr "" -#: ../../../CHANGELOG.md:243 +#: ../../../CHANGELOG.md:274 msgid "Mautrix bridges now expose their API (for Mautrix Manager and similar tools)" msgstr "" -#: ../../../CHANGELOG.md:245 +#: ../../../CHANGELOG.md:276 msgid "The playbook now exposes the HTTP API of each [mautrix](https://github.com/mautrix) bridge, so tools like [Mautrix Manager](https://github.com/mautrix/manager) can help you log into them. This is especially useful for [mautrix-gmessages](./docs/configuring-playbook-bridge-mautrix-gmessages.md): Google has removed its QR-code login, leaving a [manual cookie-extraction flow](https://docs.mau.fi/bridges/go/gmessages/authentication.html) that tools like Mautrix Manager can streamline." msgstr "" -#: ../../../CHANGELOG.md:247 +#: ../../../CHANGELOG.md:278 msgid "The API is exposed at `https://matrix.example.com/bridges/SERVICENAME` (for example, `https://matrix.example.com/bridges/gmessages`) and is advertised via a new `/.well-known/matrix/mautrix` file, so compatible tools can discover your bridges automatically. Such tools authenticate with your own Matrix access token, so no bridge secret needs to be shared with them." msgstr "" -#: ../../../CHANGELOG.md:249 +#: ../../../CHANGELOG.md:280 msgid "This affects all mautrix bridges based on the new bridge framework (bluesky, gmessages, meta-instagram, meta-messenger, signal, slack, telegram, twitter and whatsapp) and is enabled by default." msgstr "" -#: ../../../CHANGELOG.md:251 +#: ../../../CHANGELOG.md:282 msgid "To learn more (including how to turn it off), see the [Expose the bridge's API](./docs/configuring-playbook-bridge-mautrix-bridges.md#expose-the-bridges-api-for-mautrix-manager-and-similar-tools) section on our common mautrix bridges documentation page." msgstr "" -#: ../../../CHANGELOG.md:253 +#: ../../../CHANGELOG.md:284 msgid "2026-06-28" msgstr "" -#: ../../../CHANGELOG.md:255 +#: ../../../CHANGELOG.md:286 msgid "baibot now supports Venice, our recommended provider" msgstr "" -#: ../../../CHANGELOG.md:257 +#: ../../../CHANGELOG.md:288 msgid "[baibot](./docs/configuring-playbook-bot-baibot.md) now ships a preset for the [Venice](./docs/configuring-playbook-bot-baibot.md#venice) provider, and it's the one we recommend. It's the most capable provider baibot supports (text generation with vision, file inputs and web search, speech-to-text, text-to-speech, and image generation and editing), and the only one that runs inference with no logging and no training on your data." msgstr "" -#: ../../../CHANGELOG.md:259 +#: ../../../CHANGELOG.md:290 msgid "Enabling it takes a preset toggle and an API key:" msgstr "" -#: ../../../CHANGELOG.md:267 +#: ../../../CHANGELOG.md:298 msgid "[OpenAI](https://openai.com/) and baibot's other providers remain fully supported. To get started, see the [Setting up baibot](./docs/configuring-playbook-bot-baibot.md#venice) documentation page." msgstr "" -#: ../../../CHANGELOG.md:269 +#: ../../../CHANGELOG.md:300 msgid "2026-06-24" msgstr "" -#: ../../../CHANGELOG.md:271 +#: ../../../CHANGELOG.md:302 msgid "Support for bridging to iMessage via RustPush" msgstr "" -#: ../../../CHANGELOG.md:273 +#: ../../../CHANGELOG.md:304 msgid "Thanks to [jasonlaguidice](https://github.com/jasonlaguidice), the playbook now supports bridging to [iMessage](https://support.apple.com/messages) via a new [RustPush](https://github.com/OpenBubbles/rustpush)-based bridge ([jasonlaguidice/imessage](https://github.com/jasonlaguidice/imessage))." msgstr "" -#: ../../../CHANGELOG.md:275 +#: ../../../CHANGELOG.md:306 msgid "Unlike the existing [mautrix-wsproxy](./docs/configuring-playbook-bridge-mautrix-wsproxy.md) iMessage bridge, this one talks directly to Apple's push notification service, so it needs neither a running Mac nor a wsproxy on the homeserver. Each user supplies a hardware key extracted from a Mac through the bridge bot's login flow." msgstr "" -#: ../../../CHANGELOG.md:277 +#: ../../../CHANGELOG.md:308 msgid "To learn more, see our [Setting up RustPush (iMessage) bridging](./docs/configuring-playbook-bridge-rustpush.md) documentation page." msgstr "" -#: ../../../CHANGELOG.md:279 +#: ../../../CHANGELOG.md:310 msgid "2026-05-24" msgstr "" -#: ../../../CHANGELOG.md:281 +#: ../../../CHANGELOG.md:312 msgid "matrix-ldap-registration-proxy has been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:283 +#: ../../../CHANGELOG.md:314 msgid "The [matrix-ldap-registration-proxy](./docs/configuring-playbook-matrix-ldap-registration-proxy.md) service has been removed from the playbook, as the source code and the container image have become unavailable." msgstr "" -#: ../../../CHANGELOG.md:285 +#: ../../../CHANGELOG.md:316 msgid "The playbook will let you know if you're using any `matrix_ldap_registration_proxy_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-matrix-ldap-registration-proxy.md#uninstalling-the-component-manually)." msgstr "" -#: ../../../CHANGELOG.md:287 +#: ../../../CHANGELOG.md:318 msgid "2026-05-23" msgstr "" -#: ../../../CHANGELOG.md:289 +#: ../../../CHANGELOG.md:320 msgid "Go-NEB has been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:291 +#: ../../../CHANGELOG.md:322 msgid "[Go-NEB](./docs/configuring-playbook-bot-go-neb.md) has been removed from the playbook, as it has been discontinued since June 2023." msgstr "" -#: ../../../CHANGELOG.md:293 +#: ../../../CHANGELOG.md:324 msgid "The playbook will let you know if you're using any `matrix_bot_go_neb_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the bot manually](./docs/configuring-playbook-bot-go-neb.md#uninstalling-go-neb-manually)." msgstr "" -#: ../../../CHANGELOG.md:295 +#: ../../../CHANGELOG.md:326 msgid "2026-05-19" msgstr "" -#: ../../../CHANGELOG.md:297 +#: ../../../CHANGELOG.md:328 msgid "matrix-registration has been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:299 +#: ../../../CHANGELOG.md:330 msgid "The [matrix-registration](./docs/configuring-playbook-matrix-registration.md) service has been removed from the playbook, as it has been unmaintained (archived) since November, 2025." msgstr "" -#: ../../../CHANGELOG.md:301 +#: ../../../CHANGELOG.md:332 msgid "The playbook will let you know if you're using any `matrix_registration_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-matrix-registration.md#uninstalling-the-component-manually)." msgstr "" -#: ../../../CHANGELOG.md:303 +#: ../../../CHANGELOG.md:334 msgid "2026-05-18" msgstr "" -#: ../../../CHANGELOG.md:305 +#: ../../../CHANGELOG.md:336 msgid "LiveKit Server has been upgraded to v1.12.0" msgstr "" -#: ../../../CHANGELOG.md:307 +#: ../../../CHANGELOG.md:338 msgid "The playbook now ships [LiveKit Server](./docs/configuring-playbook-livekit-server.md) v1.12.0. See the [upstream release notes](https://github.com/livekit/livekit/releases/tag/v1.12.0) for details." msgstr "" -#: ../../../CHANGELOG.md:309 +#: ../../../CHANGELOG.md:340 msgid "This release tightens TURN security:" msgstr "" -#: ../../../CHANGELOG.md:311 +#: ../../../CHANGELOG.md:342 msgid "**TURN credentials now carry a TTL** (default: 300 seconds), exposed via `livekit_server_config_turn_ttl_seconds`." msgstr "" -#: ../../../CHANGELOG.md:312 +#: ../../../CHANGELOG.md:343 msgid "**TURN no longer relays traffic to restricted peer CIDRs** (loopback, link-local, multicast, private, unspecified) by default. If your setup legitimately requires it, list the ranges in `livekit_server_config_turn_allow_restricted_peer_cidrs`." msgstr "" -#: ../../../CHANGELOG.md:314 +#: ../../../CHANGELOG.md:345 msgid "For example, to allow TURN to reach the common [RFC1918](https://www.rfc-editor.org/rfc/rfc1918) private ranges, add to your `vars.yml`:" msgstr "" -#: ../../../CHANGELOG.md:322 +#: ../../../CHANGELOG.md:353 msgid "Adjust the ranges to match your network. To deny specific CIDRs (taking precedence over the allow list above), use `livekit_server_config_turn_deny_peer_cidrs` in the same shape." msgstr "" -#: ../../../CHANGELOG.md:325 +#: ../../../CHANGELOG.md:356 msgid "2026-05-07" msgstr "" -#: ../../../CHANGELOG.md:327 +#: ../../../CHANGELOG.md:358 msgid "Tuwunel support" msgstr "" -#: ../../../CHANGELOG.md:329 +#: ../../../CHANGELOG.md:360 msgid "Thanks to [Jason Volk](https://github.com/jevolk), the playbook now supports the [Tuwunel](./docs/configuring-playbook-tuwunel.md) homeserver as an optional alternative to Synapse." msgstr "" -#: ../../../CHANGELOG.md:331 +#: ../../../CHANGELOG.md:362 msgid "Tuwunel is a fork of [conduwuit](./docs/configuring-playbook-conduwuit.md) written in Rust. The former conduwuit maintainer [endorses Tuwunel as conduwuit's successor](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/5200#issuecomment-4396211185). Like [Continuwuity](./docs/configuring-playbook-continuwuity.md), Tuwunel continues development on top of conduwuit's database format." msgstr "" -#: ../../../CHANGELOG.md:333 -#: ../../../CHANGELOG.md:837 -#: ../../../CHANGELOG.md:1050 +#: ../../../CHANGELOG.md:364 +#: ../../../CHANGELOG.md:868 +#: ../../../CHANGELOG.md:1081 msgid "Existing installations do **not** need to be updated. **Synapse is still the default homeserver implementation** installed by the playbook." msgstr "" -#: ../../../CHANGELOG.md:335 +#: ../../../CHANGELOG.md:366 msgid "People that used to run conduwuit may wish to [migrate from conduwuit to Tuwunel](./docs/configuring-playbook-tuwunel.md#migrating-from-conduwuit) via the new `tuwunel-migrate-from-conduwuit` tag, which performs an in-place binary-swap migration that reads the conduwuit database directly." msgstr "" -#: ../../../CHANGELOG.md:337 +#: ../../../CHANGELOG.md:368 msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse/Conduit/Dendrite/Continuwuity to Tuwunel) without data loss. The exception is conduwuit, due to the shared database format." msgstr "" -#: ../../../CHANGELOG.md:340 +#: ../../../CHANGELOG.md:371 msgid "2026-04-24" msgstr "" -#: ../../../CHANGELOG.md:342 +#: ../../../CHANGELOG.md:373 msgid "Support for bridging to Meshtastic via meshtastic-matrix-relay" msgstr "" -#: ../../../CHANGELOG.md:344 +#: ../../../CHANGELOG.md:375 msgid "Thanks to [luschmar](https://github.com/luschmar), the playbook now supports bridging to [Meshtastic](https://meshtastic.org/) mesh networks via [meshtastic-matrix-relay](https://github.com/jeremiah-k/meshtastic-matrix-relay) (mmrelay)." msgstr "" -#: ../../../CHANGELOG.md:346 +#: ../../../CHANGELOG.md:377 msgid "To learn more, see our [Setting up a Matrix <-> Meshtastic bridge](./docs/configuring-playbook-bridge-meshtastic-relay.md) documentation page." msgstr "" -#: ../../../CHANGELOG.md:348 +#: ../../../CHANGELOG.md:379 msgid "(BC Break) mautrix-telegram has been rewritten in Go (bridgev2)" msgstr "" -#: ../../../CHANGELOG.md:350 +#: ../../../CHANGELOG.md:381 msgid "The [mautrix-telegram](./docs/configuring-playbook-bridge-mautrix-telegram.md) bridge has been [rewritten in Go](https://mau.fi/blog/2026-04-mautrix-release/) on top of the [bridgev2](https://docs.mau.fi/bridges/go/) architecture. See the [upstream v26.04 release notes](https://github.com/mautrix/telegram/releases/tag/v0.2604.0) for what changed in the bridge itself (shared-portal behavior, management-room state, new features, etc.)." msgstr "" -#: ../../../CHANGELOG.md:352 +#: ../../../CHANGELOG.md:383 msgid "**Most users won't have to do anything.** If you use the playbook's integrated Postgres (the default) and haven't customized telegram-bridge variables beyond `matrix_mautrix_telegram_api_id` and `matrix_mautrix_telegram_api_hash`, just re-run the playbook; the bridge will migrate itself on first start. Taking a backup beforehand is still a good idea." msgstr "" -#: ../../../CHANGELOG.md:354 +#: ../../../CHANGELOG.md:385 msgid "⚠️ **SQLite users: do not upgrade yet.** Upstream v0.2604.0 has a [known bug in the legacy SQLite migration](https://github.com/mautrix/telegram/releases/tag/v0.2604.0) that can corrupt your data. The playbook detects this case and will refuse to proceed. Either switch to Postgres first (set `matrix_mautrix_telegram_database_engine: postgres`; the playbook handles the pgloader migration), or wait for the next upstream release." msgstr "" -#: ../../../CHANGELOG.md:356 +#: ../../../CHANGELOG.md:387 msgid "Playbook-specific things to know. The playbook will fail loudly if you're affected:" msgstr "" -#: ../../../CHANGELOG.md:358 +#: ../../../CHANGELOG.md:389 msgid "Many `matrix_mautrix_telegram_*` variables have been **removed** (web-login endpoint, lottieconverter, username/alias/displayname templates, filter-mode, bot-token relaybot, Shared-Secret-Auth map). The deprecation check will tell you exactly what to rename or drop when you run the playbook." msgstr "" -#: ../../../CHANGELOG.md:359 +#: ../../../CHANGELOG.md:390 msgid "**Old-style relaybot users** (`matrix_mautrix_telegram_bot_token`): switch to the common [mautrix bridge relay mode](./docs/configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional) via `matrix_mautrix_telegram_bridge_relay_enabled: true`." msgstr "" -#: ../../../CHANGELOG.md:360 +#: ../../../CHANGELOG.md:391 msgid "**Shared-Secret-Auth double-puppeting users**: switch to [Appservice Double Puppet](./docs/configuring-playbook-appservice-double-puppet.md); the playbook wires it up automatically." msgstr "" -#: ../../../CHANGELOG.md:361 +#: ../../../CHANGELOG.md:392 msgid "**Custom `matrix_mautrix_telegram_bridge_permissions`**: map `relaybot` to `relay`, `puppeting` to `user`, `full` to `user`. Validated at playbook time." msgstr "" -#: ../../../CHANGELOG.md:363 +#: ../../../CHANGELOG.md:394 msgid "2026-04-03" msgstr "" -#: ../../../CHANGELOG.md:365 +#: ../../../CHANGELOG.md:396 msgid "(BC Break) Synapse Admin (fork by etke.cc) is now Ketesa" msgstr "" -#: ../../../CHANGELOG.md:367 +#: ../../../CHANGELOG.md:398 msgid "Synapse Admin has been rebranded to **[Ketesa](https://github.com/etkecc/ketesa)** — a landmark release that introduces a new identity, a full UI redesign, mobile-first layout, and deep Matrix Authentication Service (MAS) integration. For the full story behind the rename and a tour of what's new, see the [Ketesa v1.0.0 announcement](https://etke.cc/blog/introducing-ketesa/)." msgstr "" -#: ../../../CHANGELOG.md:369 +#: ../../../CHANGELOG.md:400 msgid "Ketesa is a zero-configuration drop-in replacement for Synapse Admin: no server-side changes required, just update the role variables." msgstr "" -#: ../../../CHANGELOG.md:371 +#: ../../../CHANGELOG.md:402 msgid "The `matrix-synapse-admin` role has been **renamed** to `matrix-ketesa`. All `matrix_synapse_admin_*` variables must be **renamed** to `matrix_ketesa_*` in your `vars.yml`." msgstr "" -#: ../../../CHANGELOG.md:373 +#: ../../../CHANGELOG.md:404 msgid "Additionally, the **Docker image** changed from `ghcr.io/etkecc/synapse-admin` to `ghcr.io/etkecc/ketesa`. The default path prefix remains `/synapse-admin` for backward compatibility — updating to `/ketesa` is recommended but not required." msgstr "" -#: ../../../CHANGELOG.md:375 +#: ../../../CHANGELOG.md:406 msgid "The playbook will automatically detect leftover `matrix_synapse_admin_*` variables and fail with a helpful message listing what needs to be renamed." msgstr "" -#: ../../../CHANGELOG.md:377 +#: ../../../CHANGELOG.md:408 msgid "The playbook handles reverse-proxy routing for subpath deployments (e.g. `/ketesa`), including MAS-enabled setups — though OIDC auth flows on real servers still have some rough edges. Feedback is appreciated in [#ketesa:etke.cc](https://matrix.to/#/#ketesa:etke.cc)." msgstr "" -#: ../../../CHANGELOG.md:379 +#: ../../../CHANGELOG.md:410 msgid "See the [Ketesa documentation](docs/configuring-playbook-ketesa.md) for details." msgstr "" -#: ../../../CHANGELOG.md:381 +#: ../../../CHANGELOG.md:412 msgid "2026-04-02" msgstr "" -#: ../../../CHANGELOG.md:383 +#: ../../../CHANGELOG.md:414 msgid "(BC Break) Draupnir for all Self Service Provisioning is now disabled by default" msgstr "" -#: ../../../CHANGELOG.md:385 +#: ../../../CHANGELOG.md:416 msgid "💡 If you don't use [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md), then this breaking change does not concern you.." msgstr "" -#: ../../../CHANGELOG.md:387 +#: ../../../CHANGELOG.md:418 msgid "[Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) now ships with `allowSelfServiceProvisioning: false` as default upstream and in this playbook." msgstr "" -#: ../../../CHANGELOG.md:389 +#: ../../../CHANGELOG.md:420 msgid "This means users can no longer provision Draupnir instances by inviting the appservice bot unless you explicitly opt in." msgstr "" -#: ../../../CHANGELOG.md:391 +#: ../../../CHANGELOG.md:422 msgid "Manual provisioning by administrators is now the recommended approach. You do not want to enable Self Service Provisioning unless you have additional custom safeguards like those used by asgard.chat in place." msgstr "" -#: ../../../CHANGELOG.md:393 +#: ../../../CHANGELOG.md:424 msgid "If you want to enable Self Service Provisioning, add the following to your `vars.yml`:" msgstr "" -#: ../../../CHANGELOG.md:400 +#: ../../../CHANGELOG.md:431 msgid "2026-03-23" msgstr "" -#: ../../../CHANGELOG.md:402 +#: ../../../CHANGELOG.md:433 msgid "Migration validation system introduced" msgstr "" -#: ../../../CHANGELOG.md:404 +#: ../../../CHANGELOG.md:435 msgid "Previously, when updating your setup, you had to remember to read the [CHANGELOG](CHANGELOG.md) file or risk breakage." msgstr "" -#: ../../../CHANGELOG.md:406 +#: ../../../CHANGELOG.md:437 msgid "Now, the playbook includes a migration validation system that ensures you're aware of breaking changes before they affect your deployment. You're now forced to acknowledge each breaking change, unless you wish to live dangerously (see below)." msgstr "" -#: ../../../CHANGELOG.md:409 +#: ../../../CHANGELOG.md:440 msgid "A new `matrix_playbook_migration_validated_version` variable has been introduced." msgstr "" -#: ../../../CHANGELOG.md:411 +#: ../../../CHANGELOG.md:442 msgid "**New users** who started from the [example `vars.yml`](examples/vars.yml) file already have this variable set and do not need to do anything." msgstr "" -#: ../../../CHANGELOG.md:413 +#: ../../../CHANGELOG.md:444 msgid "**Existing users** will need to add the following to their `vars.yml` file after reviewing all changelog entries up to now:" msgstr "" -#: ../../../CHANGELOG.md:419 +#: ../../../CHANGELOG.md:450 msgid "Going forward, whenever a breaking change is introduced the playbook will:" msgstr "" -#: ../../../CHANGELOG.md:421 +#: ../../../CHANGELOG.md:452 msgid "bump its expected version value (`matrix_playbook_migration_expected_version`), causing a discrepancy with what you validated (`matrix_playbook_migration_validated_version`)" msgstr "" -#: ../../../CHANGELOG.md:423 +#: ../../../CHANGELOG.md:454 msgid "fail when you run it with a helpful message listing what changed and linking to the relevant changelog entries" msgstr "" -#: ../../../CHANGELOG.md:425 +#: ../../../CHANGELOG.md:456 msgid "After reviewing and adapting your setup, you simply update the variable to the new version." msgstr "" -#: ../../../CHANGELOG.md:427 +#: ../../../CHANGELOG.md:458 msgid "If you'd like to live dangerously and skip these checks (not recommended), you can set this once and be done with it:" msgstr "" -#: ../../../CHANGELOG.md:433 +#: ../../../CHANGELOG.md:464 msgid "2026-03-19" msgstr "" -#: ../../../CHANGELOG.md:435 +#: ../../../CHANGELOG.md:466 msgid "Matrix Authentication Service now prefers UNIX sockets for playbook-managed Postgres" msgstr "" -#: ../../../CHANGELOG.md:437 +#: ../../../CHANGELOG.md:468 msgid "When [Matrix Authentication Service](docs/configuring-playbook-matrix-authentication-service.md) (MAS) uses the playbook-managed Postgres service, it now connects to it via a [UNIX socket](https://en.wikipedia.org/wiki/Unix_domain_socket) by default instead of TCP." msgstr "" -#: ../../../CHANGELOG.md:439 +#: ../../../CHANGELOG.md:470 msgid "This follows the same approach [applied to Synapse](#synapse-now-prefers-unix-sockets-for-playbook-managed-postgres-and-valkey) and reduces unnecessary container-network wiring, keeping local IPC off the network stack." msgstr "" -#: ../../../CHANGELOG.md:441 +#: ../../../CHANGELOG.md:472 msgid "If you use an external Postgres server for MAS, this does not change your setup." msgstr "" -#: ../../../CHANGELOG.md:443 -#: ../../../CHANGELOG.md:459 +#: ../../../CHANGELOG.md:474 +#: ../../../CHANGELOG.md:490 msgid "If you'd like to keep the previous TCP-based behavior, add the following configuration to your `vars.yml`:" msgstr "" -#: ../../../CHANGELOG.md:449 +#: ../../../CHANGELOG.md:480 msgid "2026-03-17" msgstr "" -#: ../../../CHANGELOG.md:451 +#: ../../../CHANGELOG.md:482 msgid "Synapse now prefers UNIX sockets for playbook-managed Postgres and Valkey" msgstr "" -#: ../../../CHANGELOG.md:453 +#: ../../../CHANGELOG.md:484 msgid "When Synapse uses the playbook-managed Postgres and Valkey services, it now connects to them via [UNIX sockets](https://en.wikipedia.org/wiki/Unix_domain_socket) by default instead of TCP." msgstr "" -#: ../../../CHANGELOG.md:455 +#: ../../../CHANGELOG.md:486 msgid "This reduces unnecessary container-network wiring and keeps local IPC off the network stack, which is a bit simpler and slightly more secure." msgstr "" -#: ../../../CHANGELOG.md:457 +#: ../../../CHANGELOG.md:488 msgid "If you use an external Postgres server or external Redis/Valkey for Synapse, this does not change your setup." msgstr "" -#: ../../../CHANGELOG.md:466 +#: ../../../CHANGELOG.md:497 msgid "2026-03-01" msgstr "" -#: ../../../CHANGELOG.md:468 +#: ../../../CHANGELOG.md:499 msgid "(Potential BC Break) Synapse S3 media prefix is now applied consistently" msgstr "" -#: ../../../CHANGELOG.md:470 +#: ../../../CHANGELOG.md:501 msgid "The `matrix_synapse_ext_synapse_s3_storage_provider_config_prefix` variable is now wired consistently for both:" msgstr "" -#: ../../../CHANGELOG.md:472 +#: ../../../CHANGELOG.md:503 msgid "the Synapse `s3_storage_provider` module configuration" msgstr "" -#: ../../../CHANGELOG.md:473 +#: ../../../CHANGELOG.md:504 msgid "the `matrix-synapse-s3-storage-provider-migrate` migration script (`s3_media_upload --prefix`)" msgstr "" -#: ../../../CHANGELOG.md:475 +#: ../../../CHANGELOG.md:506 msgid "Previously, this variable could be set, but was not effectively applied by either of these paths." msgstr "" -#: ../../../CHANGELOG.md:477 +#: ../../../CHANGELOG.md:508 msgid "**Affects**: users of [synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3-storage-provider.md) who have configured a non-empty `matrix_synapse_ext_synapse_s3_storage_provider_config_prefix` value." msgstr "" -#: ../../../CHANGELOG.md:479 +#: ../../../CHANGELOG.md:510 msgid "If your bucket data was uploaded without the prefix before this fix, enabling proper prefix usage can make existing objects appear missing until data is migrated/copied to the prefixed key namespace." msgstr "" -#: ../../../CHANGELOG.md:481 +#: ../../../CHANGELOG.md:512 msgid "2026-02-26" msgstr "" -#: ../../../CHANGELOG.md:483 +#: ../../../CHANGELOG.md:514 msgid "Internal refactor: merged the Synapse reverse-proxy companion role into `matrix-synapse`" msgstr "" -#: ../../../CHANGELOG.md:485 +#: ../../../CHANGELOG.md:516 msgid "The standalone `matrix-synapse-reverse-proxy-companion` role has been merged into the [matrix-synapse](roles/custom/matrix-synapse/) role." msgstr "" -#: ../../../CHANGELOG.md:487 +#: ../../../CHANGELOG.md:518 msgid "This is not a user-facing change and does not change variable names (`matrix_synapse_reverse_proxy_companion_*` remain the same). The split looked clean on paper, but in practice both parts are tightly coupled through worker routing, tags (`setup-synapse`/`install-synapse`), and lifecycle ordering, so keeping them separate added coordination overhead with little practical benefit." msgstr "" -#: ../../../CHANGELOG.md:489 +#: ../../../CHANGELOG.md:520 msgid "Compatibility note: existing companion-specific tags (`setup-synapse-reverse-proxy-companion` and `install-synapse-reverse-proxy-companion`) are still available." msgstr "" -#: ../../../CHANGELOG.md:491 +#: ../../../CHANGELOG.md:522 msgid "With this change, Synapse and its reverse-proxy companion are managed in one role (`matrix-synapse`) while still keeping companion logic in dedicated task/template subdirectories for maintainability." msgstr "" -#: ../../../CHANGELOG.md:493 +#: ../../../CHANGELOG.md:524 msgid "2026-02-21" msgstr "" -#: ../../../CHANGELOG.md:495 +#: ../../../CHANGELOG.md:526 msgid "(BC Break) coturn is no longer auto-enabled by default" msgstr "" -#: ../../../CHANGELOG.md:497 +#: ../../../CHANGELOG.md:528 msgid "By default, the [coturn](./docs/configuring-playbook-turn.md) TURN server component is no longer enabled for every deployment." msgstr "" -#: ../../../CHANGELOG.md:499 +#: ../../../CHANGELOG.md:530 msgid "This reduces resources and attach surface for deployments which:" msgstr "" -#: ../../../CHANGELOG.md:501 +#: ../../../CHANGELOG.md:532 msgid "either don't need calls at all" msgstr "" -#: ../../../CHANGELOG.md:502 +#: ../../../CHANGELOG.md:533 msgid "or use the modern [Matrix RTC](docs/configuring-playbook-matrix-rtc.md)/[Element Call](docs/configuring-playbook-element-call.md) stack." msgstr "" -#: ../../../CHANGELOG.md:504 +#: ../../../CHANGELOG.md:535 msgid "Coturn is still auto-enabled when [Jitsi](./docs/configuring-playbook-jitsi.md) is enabled (`jitsi_enabled: true`), because Jitsi still depends on TURN for legacy Matrix integration." msgstr "" -#: ../../../CHANGELOG.md:506 +#: ../../../CHANGELOG.md:537 msgid "Additionally, Coturn (when enabled) now defaults to using automatic IP detection of your server's external IP address, instead of assuming your Ansible inventory (`ansible_host`) points to a public address and using it for configuring `coturn_turn_external_ip_address`." msgstr "" -#: ../../../CHANGELOG.md:508 +#: ../../../CHANGELOG.md:539 msgid "To restore the old behavior (needed for legacy call setups), add the following configuration to your `vars.yml`:" msgstr "" -#: ../../../CHANGELOG.md:517 +#: ../../../CHANGELOG.md:548 msgid "LiveKit TURN TLS is now automatically fronted by playbook-managed Traefik" msgstr "" -#: ../../../CHANGELOG.md:519 +#: ../../../CHANGELOG.md:550 msgid "For deployments that use the playbook-managed Traefik reverse-proxy, LiveKit TURN over TCP is now SSL-terminated at Traefik and passed as plain TCP to LiveKit (`turn.external_tls = true`) by default." msgstr "" -#: ../../../CHANGELOG.md:521 +#: ../../../CHANGELOG.md:552 msgid "To disable this behavior, set `livekit_server_config_turn_external_tls: false` and the playbook will revert to the old behavior - using traefik-certs-dumper to extract SSL certificates out of Traefik and pass them to LiveKit for explicit SSL termination there." msgstr "" -#: ../../../CHANGELOG.md:523 +#: ../../../CHANGELOG.md:554 msgid "If you are using `other-traefik-container` or [another reverse-proxy](./configuring-playbook-own-webserver.md), this change does **not** switch behavior automatically. That mode remains using certificate files in the container (Traefik certificates dumper flow) unless you explicitly set the TURN-Traefik mode variables to opt in." msgstr "" -#: ../../../CHANGELOG.md:525 +#: ../../../CHANGELOG.md:556 msgid "2026-02-17" msgstr "" -#: ../../../CHANGELOG.md:527 +#: ../../../CHANGELOG.md:558 msgid "(BC Break) prometheus-nginxlog-exporter role has been relocated and variable names need adjustments" msgstr "" -#: ../../../CHANGELOG.md:529 +#: ../../../CHANGELOG.md:560 msgid "The role for prometheus-nginxlog-exporter has been relocated to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization." msgstr "" -#: ../../../CHANGELOG.md:531 +#: ../../../CHANGELOG.md:562 msgid "Along with the relocation, the `matrix_prometheus_nginxlog_exporter_` prefix on its variable names has been renamed to `prometheus_nginxlog_exporter_`, so you need to adjust your `vars.yml` configuration." msgstr "" -#: ../../../CHANGELOG.md:533 -#: ../../../CHANGELOG.md:595 -#: ../../../CHANGELOG.md:605 -#: ../../../CHANGELOG.md:666 -#: ../../../CHANGELOG.md:688 -#: ../../../CHANGELOG.md:1223 +#: ../../../CHANGELOG.md:564 +#: ../../../CHANGELOG.md:626 +#: ../../../CHANGELOG.md:636 +#: ../../../CHANGELOG.md:697 +#: ../../../CHANGELOG.md:719 +#: ../../../CHANGELOG.md:1254 msgid "As always, the playbook would let you know about this and point out any variables you may have missed." msgstr "" -#: ../../../CHANGELOG.md:535 +#: ../../../CHANGELOG.md:566 msgid "synapse-auto-invite-accept has been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:537 +#: ../../../CHANGELOG.md:568 msgid "[synapse-auto-invite-accept](./docs/configuring-playbook-synapse-auto-accept-invite.md) has been removed from the playbook, as the same functionality [has been integrated](https://github.com/element-hq/synapse/pull/17147) to Synapse since [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0)." msgstr "" -#: ../../../CHANGELOG.md:539 +#: ../../../CHANGELOG.md:570 msgid "See [this section](./docs/configuring-playbook-synapse-auto-accept-invite.md#native-alternative) for details about how to enable the function on Synapse." msgstr "" -#: ../../../CHANGELOG.md:541 +#: ../../../CHANGELOG.md:572 msgid "If you're using any `matrix_synapse_ext_synapse_auto_accept_invite_*` variables, the playbook will let you know which one you'll need to remove from `vars.yml`." msgstr "" -#: ../../../CHANGELOG.md:543 +#: ../../../CHANGELOG.md:574 msgid "2026-02-16" msgstr "" -#: ../../../CHANGELOG.md:545 +#: ../../../CHANGELOG.md:576 msgid "matrix-appservice-slack has been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:547 +#: ../../../CHANGELOG.md:578 msgid "[matrix-appservice-slack](./docs/configuring-playbook-bridge-appservice-slack.md) has been removed from the playbook, as it has been discontinued because the public Matrix.org Slack bridge has been decommissioned on January 14th, 2026." msgstr "" -#: ../../../CHANGELOG.md:549 +#: ../../../CHANGELOG.md:580 msgid "The playbook will let you know if you're using any `matrix_appservice_slack_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-bridge-appservice-slack.md#uninstalling-the-component-manually)." msgstr "" -#: ../../../CHANGELOG.md:551 +#: ../../../CHANGELOG.md:582 msgid "**Note**: Bridging to [Slack](https://slack.com) can also happen via the [mautrix-slack](./docs/configuring-playbook-bridge-mautrix-slack.md) bridge supported by the playbook." msgstr "" -#: ../../../CHANGELOG.md:553 +#: ../../../CHANGELOG.md:584 msgid "2026-02-13" msgstr "" -#: ../../../CHANGELOG.md:555 +#: ../../../CHANGELOG.md:586 msgid "Conditional service restart for `install-*` commands" msgstr "" -#: ../../../CHANGELOG.md:557 +#: ../../../CHANGELOG.md:588 msgid "When running `install-all` or `install-service` (whether via `just` or raw `ansible-playbook`), only services whose configuration or container image actually changed during the playbook run will now be restarted. Unchanged services are left running (or get started if they were stopped). This reduces unnecessary downtime — particularly for services like Traefik (the reverse proxy), which previously caused brief connectivity interruptions on every playbook run even when nothing changed." msgstr "" -#: ../../../CHANGELOG.md:559 +#: ../../../CHANGELOG.md:590 msgid "When running with `setup-*` tags (e.g. `setup-all`, `setup-synapse`), all services continue to be unconditionally restarted as before." msgstr "" -#: ../../../CHANGELOG.md:561 +#: ../../../CHANGELOG.md:592 msgid "Currently, only Traefik tracks its own changes and benefits from conditional restart. All other services default to being restarted (the previous behavior). This is just the beginning — as more roles gain change-tracking support, playbook performance will improve and downtime will decrease dramatically, especially for `install-all` runs where most services haven't changed." msgstr "" -#: ../../../CHANGELOG.md:563 +#: ../../../CHANGELOG.md:594 msgid "Some benchmarks for `just install-service traefik` when Traefik settings did not change:" msgstr "" -#: ../../../CHANGELOG.md:565 +#: ../../../CHANGELOG.md:596 msgid "**Before**:" msgstr "" -#: ../../../CHANGELOG.md:566 +#: ../../../CHANGELOG.md:597 msgid "total time: ~56 seconds 🐌" msgstr "" -#: ../../../CHANGELOG.md:567 +#: ../../../CHANGELOG.md:598 msgid "Traefik restarted: yes (unnecessarily) ❌" msgstr "" -#: ../../../CHANGELOG.md:568 +#: ../../../CHANGELOG.md:599 msgid "dependent services restarted: yes, all of them ❌" msgstr "" -#: ../../../CHANGELOG.md:569 +#: ../../../CHANGELOG.md:600 msgid "**After**:" msgstr "" -#: ../../../CHANGELOG.md:570 +#: ../../../CHANGELOG.md:601 msgid "total time: ~27 seconds ⚡" msgstr "" -#: ../../../CHANGELOG.md:571 +#: ../../../CHANGELOG.md:602 msgid "Traefik restarted: no ✅" msgstr "" -#: ../../../CHANGELOG.md:572 +#: ../../../CHANGELOG.md:603 msgid "dependent services restarted: no ✅" msgstr "" -#: ../../../CHANGELOG.md:574 +#: ../../../CHANGELOG.md:605 msgid "This behavior can be overridden via `--extra-vars='devture_systemd_service_manager_conditional_restart_enabled=false'` to force unconditional restarts. See [Conditional service restart](docs/just.md#conditional-service-restart) for details." msgstr "" -#: ../../../CHANGELOG.md:577 +#: ../../../CHANGELOG.md:608 msgid "2026-02-12" msgstr "" -#: ../../../CHANGELOG.md:579 +#: ../../../CHANGELOG.md:610 msgid "Dimension integration manager has been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:581 +#: ../../../CHANGELOG.md:612 msgid "The [Dimension integration manager](./docs/configuring-playbook-dimension.md) has been removed from the playbook, as it has been unmaintained." msgstr "" -#: ../../../CHANGELOG.md:583 +#: ../../../CHANGELOG.md:614 msgid "The playbook will let you know if you're using any `matrix_dimension_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-dimension.md#uninstalling-the-component-manually)." msgstr "" -#: ../../../CHANGELOG.md:585 +#: ../../../CHANGELOG.md:616 msgid "(BC Break) Hydrogen role has been relocated and variable names need adjustments" msgstr "" -#: ../../../CHANGELOG.md:587 +#: ../../../CHANGELOG.md:618 msgid "The role for Hydrogen has been relocated to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization." msgstr "" -#: ../../../CHANGELOG.md:589 +#: ../../../CHANGELOG.md:620 msgid "Along with the relocation, the `matrix_client_hydrogen_` prefix was dropped from its variable names, so you need to adjust your `vars.yml` configuration." msgstr "" -#: ../../../CHANGELOG.md:591 -#: ../../../CHANGELOG.md:684 +#: ../../../CHANGELOG.md:622 +#: ../../../CHANGELOG.md:715 msgid "You need to do the following replacement:" msgstr "" -#: ../../../CHANGELOG.md:593 +#: ../../../CHANGELOG.md:624 msgid "`matrix_client_hydrogen_` -> `hydrogen_`" msgstr "" -#: ../../../CHANGELOG.md:597 +#: ../../../CHANGELOG.md:628 msgid "2026-02-11" msgstr "" -#: ../../../CHANGELOG.md:599 +#: ../../../CHANGELOG.md:630 msgid "(BC Break) coturn role has been relocated and variable names need adjustments" msgstr "" -#: ../../../CHANGELOG.md:601 +#: ../../../CHANGELOG.md:632 msgid "The role for coturn has been relocated to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization." msgstr "" -#: ../../../CHANGELOG.md:603 +#: ../../../CHANGELOG.md:634 msgid "Along with the relocation, the `matrix_coturn_` prefix on its variable names has been renamed to `coturn_`, so you need to adjust your `vars.yml` configuration." msgstr "" -#: ../../../CHANGELOG.md:607 +#: ../../../CHANGELOG.md:638 msgid "conduwuit has been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:609 +#: ../../../CHANGELOG.md:640 msgid "[conduwuit](./docs/configuring-playbook-conduwuit.md) has been removed from the playbook, as it has been abandoned." msgstr "" -#: ../../../CHANGELOG.md:611 +#: ../../../CHANGELOG.md:642 msgid "The playbook will let you know if you're using any `matrix_conduwuit_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the service manually](./docs/configuring-playbook-conduwuit.md#uninstalling-the-service-manually)." msgstr "" -#: ../../../CHANGELOG.md:613 +#: ../../../CHANGELOG.md:644 msgid "Since [Continuwuity](configuring-playbook-continuwuity.md) is a drop-in replacement for conduwuit, migration is possible. Please refer to [this section](./configuring-playbook-continuwuity.md#migrating-from-conduwuit) for details." msgstr "" -#: ../../../CHANGELOG.md:615 +#: ../../../CHANGELOG.md:646 msgid "2026-02-09" msgstr "" -#: ../../../CHANGELOG.md:617 +#: ../../../CHANGELOG.md:648 msgid "(BC Break) matrix-media-repo datastore IDs are now required in `vars.yml`" msgstr "" -#: ../../../CHANGELOG.md:619 +#: ../../../CHANGELOG.md:650 msgid "**Affects**: users with [matrix-media-repo](docs/configuring-playbook-matrix-media-repo.md) enabled (`matrix_media_repo_enabled: true`)" msgstr "" -#: ../../../CHANGELOG.md:621 +#: ../../../CHANGELOG.md:652 msgid "The `matrix_media_repo_datastore_file_id` and `matrix_media_repo_datastore_s3_id` variables are no longer auto-configured with values. They must now be explicitly defined in your `vars.yml` file. The playbook will fail with a helpful error if they are not set (when needed)." msgstr "" -#: ../../../CHANGELOG.md:623 +#: ../../../CHANGELOG.md:654 msgid "These were never meant to be auto-configured. They were derived from `matrix_homeserver_generic_secret_key`, which is intended for secrets that are OK to change subsequently (and Ansible would assist in propagating these changes). matrix-media-repo datastore IDs are not secrets — they are static identifiers linking media to storage backends, and **must not change** after first use." msgstr "" -#: ../../../CHANGELOG.md:625 +#: ../../../CHANGELOG.md:656 msgid "**For existing installations**, retrieve your current values from the server:" msgstr "" -#: ../../../CHANGELOG.md:631 +#: ../../../CHANGELOG.md:662 msgid "Then add to your `vars.yml`:" msgstr "" -#: ../../../CHANGELOG.md:640 +#: ../../../CHANGELOG.md:671 msgid "**Why do this?**: This change allows us to **remove the [passlib](https://passlib.readthedocs.io/en/stable/index.html) Python library** from the [prerequisites](docs/prerequisites.md), as it was the last component that depended on it." msgstr "" -#: ../../../CHANGELOG.md:642 +#: ../../../CHANGELOG.md:673 msgid "2026-02-08" msgstr "" -#: ../../../CHANGELOG.md:644 +#: ../../../CHANGELOG.md:675 msgid "Zulip bridge has been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:646 +#: ../../../CHANGELOG.md:677 msgid "Zulip bridge has been removed from the playbook, as it doesn't work, and the maintainer seems to have abandoned it. See [this issue](https://github.com/GearKite/MatrixZulipBridge/issues/23) for more context." msgstr "" -#: ../../../CHANGELOG.md:648 +#: ../../../CHANGELOG.md:679 msgid "Switched to faster secret derivation for service passwords" msgstr "" -#: ../../../CHANGELOG.md:650 +#: ../../../CHANGELOG.md:681 msgid "We've switched the method used for deriving service passwords (database passwords, appservice tokens, etc.) from the `matrix_homeserver_generic_secret_key` variable." msgstr "" -#: ../../../CHANGELOG.md:652 +#: ../../../CHANGELOG.md:683 msgid "The old method used `password_hash('sha512', rounds=655555)` (655,555 rounds of SHA-512 hashing), which was designed for protecting low-entropy human passwords against brute-force attacks. For deriving secrets from an already high-entropy secret key, this many rounds provide no additional security - the secret key's entropy is what protects the derived passwords, not the computational cost of hashing." msgstr "" -#: ../../../CHANGELOG.md:654 +#: ../../../CHANGELOG.md:685 msgid "The new method uses a single-round `hash('sha512')` with a unique salt per service. This is equally secure for this use case (SHA-512 remains preimage-resistant; brute-forcing a high-entropy key is infeasible regardless of rounds), while being dramatically faster." msgstr "" -#: ../../../CHANGELOG.md:656 +#: ../../../CHANGELOG.md:687 msgid "On a fast mini PC, evaluating `postgres_managed_databases` (which references multiple database passwords) dropped from **~10.7 seconds to ~0.6 seconds**. The Postgres role evaluates this variable multiple times during a run, so the cumulative savings are significant. All other roles that reference derived passwords also benefit." msgstr "" -#: ../../../CHANGELOG.md:658 +#: ../../../CHANGELOG.md:689 msgid "**What this means for users**: all derived service passwords (database passwords, appservice tokens, etc.) will change on the next playbook run. The main/superuser database password (`postgres_connection_password`) is not affected, as it is hardcoded in inventory variables rather than derived via hashing. All services will receive their new passwords as part of the same run, so this should be a seamless, non-user-impacting change." msgstr "" -#: ../../../CHANGELOG.md:660 +#: ../../../CHANGELOG.md:691 msgid "(BC Break) Dynamic DNS role has been relocated and variable names need adjustments" msgstr "" -#: ../../../CHANGELOG.md:662 +#: ../../../CHANGELOG.md:693 msgid "The role for Dynamic DNS has been relocated to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization." msgstr "" -#: ../../../CHANGELOG.md:664 +#: ../../../CHANGELOG.md:695 msgid "Along with the relocation, the `matrix_dynamic_dns_` prefix on its variable names has been renamed to `ddclient_`, so you need to adjust your `vars.yml` configuration." msgstr "" -#: ../../../CHANGELOG.md:668 +#: ../../../CHANGELOG.md:699 msgid "ma1sd has been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:670 +#: ../../../CHANGELOG.md:701 msgid "[ma1sd](./docs/configuring-playbook-ma1sd.md) has been removed from the playbook, as it has been unmaintained for a long time." msgstr "" -#: ../../../CHANGELOG.md:672 +#: ../../../CHANGELOG.md:703 msgid "The playbook will let you know if you're using any `matrix_ma1sd_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-ma1sd.md#uninstalling-the-component-manually)." msgstr "" -#: ../../../CHANGELOG.md:674 +#: ../../../CHANGELOG.md:705 msgid "Please note that some of the functions can be achieved with other components. For example, if you wish to implement LDAP integration, you might as well check out [the LDAP provider module for Synapse](./docs/configuring-playbook-ldap-auth.md) instead." msgstr "" -#: ../../../CHANGELOG.md:676 +#: ../../../CHANGELOG.md:707 msgid "2026-02-07" msgstr "" -#: ../../../CHANGELOG.md:678 +#: ../../../CHANGELOG.md:709 msgid "(BC Break) Cinny role has been relocated and variable names need adjustments" msgstr "" -#: ../../../CHANGELOG.md:680 +#: ../../../CHANGELOG.md:711 msgid "The role for Cinny has been relocated to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization." msgstr "" -#: ../../../CHANGELOG.md:682 +#: ../../../CHANGELOG.md:713 msgid "Along with the relocation, the `matrix_client_cinny_` prefix was dropped from its variable names, so you need to adjust your `vars.yml` configuration." msgstr "" -#: ../../../CHANGELOG.md:686 +#: ../../../CHANGELOG.md:717 msgid "`matrix_client_cinny_` -> `cinny_`" msgstr "" -#: ../../../CHANGELOG.md:690 +#: ../../../CHANGELOG.md:721 msgid "The Sliding Sync proxy has been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:692 +#: ../../../CHANGELOG.md:723 msgid "The [Sliding Sync proxy](./docs/configuring-playbook-sliding-sync-proxy.md) has been removed from the playbook, as it's been replaced with a different method (called Simplified Sliding Sync) integrated to newer homeservers by default (**Conduit** homeserver from version `0.6.0` or **Synapse** from version `1.114`)." msgstr "" -#: ../../../CHANGELOG.md:694 +#: ../../../CHANGELOG.md:725 msgid "The playbook will let you know if you're using any `matrix_sliding_sync_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the proxy manually](./docs/configuring-playbook-sliding-sync-proxy.md#uninstalling-the-proxy-manually)." msgstr "" -#: ../../../CHANGELOG.md:696 +#: ../../../CHANGELOG.md:727 msgid "2026-02-04" msgstr "" -#: ../../../CHANGELOG.md:698 +#: ../../../CHANGELOG.md:729 msgid "baibot now supports OpenAI's built-in tools (Web Search and Code Interpreter)" msgstr "" -#: ../../../CHANGELOG.md:700 +#: ../../../CHANGELOG.md:731 msgid "**TLDR**: if you're using the [OpenAI provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai) with [baibot](docs/configuring-playbook-bot-baibot.md), you can now enable [built-in tools](https://github.com/etkecc/baibot/blob/61d18b2/docs/features.md#%EF%B8%8F-built-in-tools-openai-only) (`web_search` and `code_interpreter`) to extend the model's capabilities." msgstr "" -#: ../../../CHANGELOG.md:702 +#: ../../../CHANGELOG.md:733 msgid "These tools are **disabled by default** and can be enabled via Ansible variables for static agent configurations:" msgstr "" -#: ../../../CHANGELOG.md:709 +#: ../../../CHANGELOG.md:740 msgid "Users who define agents dynamically at runtime will need to [update their agents](https://github.com/etkecc/baibot/blob/61d18b2/docs/agents.md#updating-agents) to enable these tools. See the [baibot v1.14.0 changelog](https://github.com/etkecc/baibot/blob/61d18b2/CHANGELOG.md) for details." msgstr "" -#: ../../../CHANGELOG.md:711 +#: ../../../CHANGELOG.md:742 msgid "Whoami-based sync worker routing for improved sticky sessions for Synapse" msgstr "" -#: ../../../CHANGELOG.md:713 +#: ../../../CHANGELOG.md:744 msgid "Deployments using [Synapse workers](./docs/configuring-playbook-synapse.md#load-balancing-with-workers) now benefit from improved sync worker routing via a new whoami-based mechanism (making use of the [whoami Matrix Client-Server API](https://spec.matrix.org/v1.17/client-server-api/#get_matrixclientv3accountwhoami))." msgstr "" -#: ../../../CHANGELOG.md:715 +#: ../../../CHANGELOG.md:746 msgid "Previously, sticky routing for sync workers relied on parsing usernames from access tokens, which only worked with native Synapse tokens (`syt__...`). This approach failed for [Matrix Authentication Service](docs/configuring-playbook-matrix-authentication-service.md) (MAS) deployments, where tokens are opaque and don't contain username information. This resulted in device-level stickiness (same token → same worker) rather than user-level stickiness (same user → same worker regardless of device), leading to suboptimal cache utilization on sync workers." msgstr "" -#: ../../../CHANGELOG.md:717 +#: ../../../CHANGELOG.md:748 msgid "The new implementation calls Synapse's `/whoami` endpoint to resolve access tokens to usernames, enabling proper user-level sticky routing regardless of the authentication system in use (native Synapse auth, MAS, etc.). Results are cached to minimize overhead." msgstr "" -#: ../../../CHANGELOG.md:719 +#: ../../../CHANGELOG.md:750 msgid "This change:" msgstr "" -#: ../../../CHANGELOG.md:720 +#: ../../../CHANGELOG.md:751 msgid "**Automatically enables** when sync workers are configured (no action required)" msgstr "" -#: ../../../CHANGELOG.md:721 +#: ../../../CHANGELOG.md:752 msgid "**Works universally** with any authentication system" msgstr "" -#: ../../../CHANGELOG.md:722 +#: ../../../CHANGELOG.md:753 msgid "**Replaces the old implementation** entirely to keep the codebase simple" msgstr "" -#: ../../../CHANGELOG.md:723 +#: ../../../CHANGELOG.md:754 msgid "**Adds minimal overhead** (one cached internal subrequest per sync request) for non-MAS deployments" msgstr "" -#: ../../../CHANGELOG.md:725 +#: ../../../CHANGELOG.md:756 msgid "For debugging, you can enable verbose logging and/or response headers showing routing decisions:" msgstr "" -#: ../../../CHANGELOG.md:736 +#: ../../../CHANGELOG.md:767 msgid "2025-12-09" msgstr "" -#: ../../../CHANGELOG.md:738 +#: ../../../CHANGELOG.md:769 msgid "Traefik Cert Dumper upgrade" msgstr "" -#: ../../../CHANGELOG.md:740 +#: ../../../CHANGELOG.md:771 msgid "The variable `traefik_certs_dumper_ssl_dir_path` was renamed to `traefik_certs_dumper_ssl_path`. Users who use [their own webserver with Traefik](docs/configuring-playbook-own-webserver.md) may need to adjust their configuration." msgstr "" -#: ../../../CHANGELOG.md:742 +#: ../../../CHANGELOG.md:773 msgid "The variable `traefik_certs_dumper_dumped_certificates_dir_path` was renamed to `traefik_certs_dumper_dumped_certificates_path`. Users who use [SRV Server Delegation](docs/howto-srv-server-delegation.md) may need to adjust their configuration." msgstr "" -#: ../../../CHANGELOG.md:744 +#: ../../../CHANGELOG.md:775 msgid "2025-11-23" msgstr "" -#: ../../../CHANGELOG.md:746 +#: ../../../CHANGELOG.md:777 msgid "Matrix.to support" msgstr "" -#: ../../../CHANGELOG.md:748 +#: ../../../CHANGELOG.md:779 msgid "The playbook now supports [Matrix.to](https://github.com/matrix-org/matrix.to) — a simple URL redirection service which powers [matrix.to](https://matrix.to)." msgstr "" -#: ../../../CHANGELOG.md:750 +#: ../../../CHANGELOG.md:781 msgid "To learn more, see our [Setting up Matrix.to](docs/configuring-playbook-matrixto.md) documentation page." msgstr "" -#: ../../../CHANGELOG.md:752 +#: ../../../CHANGELOG.md:783 msgid "2025-11-09" msgstr "" -#: ../../../CHANGELOG.md:754 +#: ../../../CHANGELOG.md:785 msgid "matrix-appservice-webhooks has been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:756 +#: ../../../CHANGELOG.md:787 msgid "[matrix-appservice-webhooks](./docs/configuring-playbook-bridge-appservice-webhooks.md) has been removed from the playbook, as it has been deprecated since more than several years." msgstr "" -#: ../../../CHANGELOG.md:758 +#: ../../../CHANGELOG.md:789 msgid "The playbook will let you know if you're using any `matrix_appservice_webhooks_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the bridge manually](./docs/configuring-playbook-bridge-appservice-webhooks.md#uninstalling-the-bridge-manually)." msgstr "" -#: ../../../CHANGELOG.md:760 +#: ../../../CHANGELOG.md:791 msgid "mautrix-facebook and mautrix-instagram have been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:762 +#: ../../../CHANGELOG.md:793 msgid "[mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-facebook.md) and [mautrix-instagram](./docs/configuring-playbook-bridge-mautrix-instagram.md) have been removed from the playbook, as they have been deprecated in favor of the [mautrix-meta](https://github.com/mautrix/meta) Messenger/Instagram bridge, integrated to the playbook at [2024-02-19](#2024-02-19)." msgstr "" -#: ../../../CHANGELOG.md:764 -#: ../../../CHANGELOG.md:796 +#: ../../../CHANGELOG.md:795 +#: ../../../CHANGELOG.md:827 msgid "The playbook will let you know if you're using any variables for those bridges:" msgstr "" -#: ../../../CHANGELOG.md:766 +#: ../../../CHANGELOG.md:797 msgid "`matrix_mautrix_facebook_*`" msgstr "" -#: ../../../CHANGELOG.md:767 +#: ../../../CHANGELOG.md:798 msgid "`matrix_mautrix_instagram_*`" msgstr "" -#: ../../../CHANGELOG.md:769 -#: ../../../CHANGELOG.md:803 +#: ../../../CHANGELOG.md:800 +#: ../../../CHANGELOG.md:834 msgid "You'll need to remove them from `vars.yml` and potentially uninstall them manually. Consult pages below for details:" msgstr "" -#: ../../../CHANGELOG.md:771 +#: ../../../CHANGELOG.md:802 msgid "[Instruction for mautrix-facebook](./docs/configuring-playbook-bridge-mautrix-facebook.md#uninstalling-the-bridge-manually)" msgstr "" -#: ../../../CHANGELOG.md:772 +#: ../../../CHANGELOG.md:803 msgid "[Instruction for mautrix-instagram](./docs/configuring-playbook-bridge-mautrix-instagram.md#uninstalling-the-bridge-manually)" msgstr "" -#: ../../../CHANGELOG.md:774 +#: ../../../CHANGELOG.md:805 msgid "2025-11-08" msgstr "" -#: ../../../CHANGELOG.md:776 +#: ../../../CHANGELOG.md:807 msgid "MatrixZulipBridge support" msgstr "" -#: ../../../CHANGELOG.md:778 +#: ../../../CHANGELOG.md:809 msgid "Thanks to [Suguru Hirahara](https://github.com/luixxiul), the playbook now supports the [GearKite/MatrixZulipBridge](https://github.com/GearKite/MatrixZulipBridg) bridge for bridging Matrix to [Zulip](https://zulip.com/)." msgstr "" -#: ../../../CHANGELOG.md:780 +#: ../../../CHANGELOG.md:811 msgid "To learn more, see our [Setting up Zulip bridging](docs/configuring-playbook-bridge-zulip.md) documentation page." msgstr "" -#: ../../../CHANGELOG.md:782 +#: ../../../CHANGELOG.md:813 msgid "2025-11-07" msgstr "" -#: ../../../CHANGELOG.md:784 +#: ../../../CHANGELOG.md:815 msgid "The matrix-chatgpt-bot has been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:786 +#: ../../../CHANGELOG.md:817 msgid "The [matrix-bot-chatgpt](./docs/configuring-playbook-bot-chatgpt.md) has been removed from the playbook, as it has been deprecated since September 2024." msgstr "" -#: ../../../CHANGELOG.md:788 +#: ../../../CHANGELOG.md:819 msgid "The playbook will let you know if you're using any `matrix_bot_chatgpt_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the bot manually](./docs/configuring-playbook-bot-chatgpt.md#uninstalling-matrix-chatgpt-bot-manually)." msgstr "" -#: ../../../CHANGELOG.md:790 +#: ../../../CHANGELOG.md:821 msgid "2025-11-05" msgstr "" -#: ../../../CHANGELOG.md:792 +#: ../../../CHANGELOG.md:823 msgid "The MX Puppet bridges for Discord, Instagram, Slack, and Twitter have been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:794 +#: ../../../CHANGELOG.md:825 msgid "The MX Puppet bridges for Discord, Instagram, Slack, and Twitter have been removed from the playbook, as they have been unmaintained for more than several years and do not support important features like authenticated media. See [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3867) for the context." msgstr "" -#: ../../../CHANGELOG.md:798 +#: ../../../CHANGELOG.md:829 msgid "`matrix_mx_puppet_discord_*`" msgstr "" -#: ../../../CHANGELOG.md:799 +#: ../../../CHANGELOG.md:830 msgid "`matrix_mx_puppet_instagram_*`" msgstr "" -#: ../../../CHANGELOG.md:800 +#: ../../../CHANGELOG.md:831 msgid "`matrix_mx_puppet_slack_*`" msgstr "" -#: ../../../CHANGELOG.md:801 +#: ../../../CHANGELOG.md:832 msgid "`matrix_mx_puppet_twitter_*`" msgstr "" -#: ../../../CHANGELOG.md:805 +#: ../../../CHANGELOG.md:836 msgid "[Instruction for MX Puppet Discord bridge](./docs/configuring-playbook-bridge-mx-puppet-discord.md#uninstalling-the-bridge-manually)" msgstr "" -#: ../../../CHANGELOG.md:806 +#: ../../../CHANGELOG.md:837 msgid "[Instruction for MX Puppet Instagram bridge](./docs/configuring-playbook-bridge-mx-puppet-instagram.md#uninstalling-the-bridge-manually)" msgstr "" -#: ../../../CHANGELOG.md:807 +#: ../../../CHANGELOG.md:838 msgid "[Instruction for MX Puppet Slack bridge](./docs/configuring-playbook-bridge-mx-puppet-slack.md#uninstalling-the-bridge-manually)" msgstr "" -#: ../../../CHANGELOG.md:808 +#: ../../../CHANGELOG.md:839 msgid "[Instruction for MX Puppet Twitter bridge](./docs/configuring-playbook-bridge-mx-puppet-twitter.md#uninstalling-the-bridge-manually)" msgstr "" -#: ../../../CHANGELOG.md:810 +#: ../../../CHANGELOG.md:841 msgid "2025-11-04" msgstr "" -#: ../../../CHANGELOG.md:812 +#: ../../../CHANGELOG.md:843 msgid "The Go Skype bridge has been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:814 +#: ../../../CHANGELOG.md:845 msgid "The [go-skype-bridge](./docs/configuring-playbook-bridge-go-skype-bridge.md) has been removed from the playbook, as Skype has been discontinued since the May 2025." msgstr "" -#: ../../../CHANGELOG.md:816 +#: ../../../CHANGELOG.md:847 msgid "The playbook will let you know if you're using any `matrix_go_skype_bridge_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the bridge manually](./docs/configuring-playbook-bridge-go-skype-bridge.md#uninstalling-the-bridge-manually)." msgstr "" -#: ../../../CHANGELOG.md:818 +#: ../../../CHANGELOG.md:849 msgid "2025-10-02" msgstr "" -#: ../../../CHANGELOG.md:820 +#: ../../../CHANGELOG.md:851 msgid "Element Admin support" msgstr "" -#: ../../../CHANGELOG.md:822 +#: ../../../CHANGELOG.md:853 msgid "The playbook now supports [Element Admin](./docs/configuring-playbook-element-admin.md) - a new web-based administration panel for Synapse and [Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md)." msgstr "" -#: ../../../CHANGELOG.md:824 +#: ../../../CHANGELOG.md:855 msgid "Deployments based on Matrix Authentication Service may find it useful to run both Synapse Admin and Element Admin at the same time." msgstr "" -#: ../../../CHANGELOG.md:826 +#: ../../../CHANGELOG.md:857 msgid "Deployments that don't rely on Matrix Authentication Service are unlikely to find anything useful in Element Admin right now (it's too basic in its current form)." msgstr "" -#: ../../../CHANGELOG.md:829 +#: ../../../CHANGELOG.md:860 msgid "2025-04-26" msgstr "" -#: ../../../CHANGELOG.md:831 +#: ../../../CHANGELOG.md:862 msgid "Continuwuity support" msgstr "" -#: ../../../CHANGELOG.md:833 +#: ../../../CHANGELOG.md:864 msgid "Thanks to [Virkkunen](https://github.com/Virkkunen), we now have optional experimental [Continuwuity](./docs/configuring-playbook-continuwuity.md) homeserver support." msgstr "" -#: ../../../CHANGELOG.md:835 +#: ../../../CHANGELOG.md:866 msgid "Continuwuity is a fork of [conduwuit](./docs/configuring-playbook-conduwuit.md), which the playbook also supports. It appears that conduwuit has been abandoned and various forks (like Continuwuity, [Tuwunel](https://github.com/matrix-construct/tuwunel) and possibly others) are continuing in its path." msgstr "" -#: ../../../CHANGELOG.md:839 +#: ../../../CHANGELOG.md:870 msgid "People that used to run conduwuit, may wish to:" msgstr "" -#: ../../../CHANGELOG.md:841 +#: ../../../CHANGELOG.md:872 msgid "either [migrate from conduwuit to Continuwuity](./docs/configuring-playbook-continuwuity.md#migrating-from-conduwuit)" msgstr "" -#: ../../../CHANGELOG.md:842 +#: ../../../CHANGELOG.md:873 msgid "or wait for some of the other forks to progress and for support for them to get added to the playbook" msgstr "" -#: ../../../CHANGELOG.md:844 +#: ../../../CHANGELOG.md:875 msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse/Conduit/Dendrite to Continuwuity) without data loss." msgstr "" -#: ../../../CHANGELOG.md:847 +#: ../../../CHANGELOG.md:878 msgid "2025-04-09" msgstr "" -#: ../../../CHANGELOG.md:849 +#: ../../../CHANGELOG.md:880 msgid "Element Call frontend installation is now optional" msgstr "" -#: ../../../CHANGELOG.md:851 +#: ../../../CHANGELOG.md:882 msgid "Because all Element clients (Element Web and Element X mobile) now embed and use their own Element Call frontend application (and not the one hosted via the playbook), it makes little sense for the playbook to self-host the Element Call frontend for you. Setting up the frontend requires an additional hostname (DNS setup) and it won't be used by Element clients anyway, so **we now recommend not installing the Element Call frontend**." msgstr "" -#: ../../../CHANGELOG.md:853 +#: ../../../CHANGELOG.md:884 msgid "💡 A reason you may wish to continue installing the Element Call frontend (despite Matrix clients not making use of it), is if you need to use it standalone - directly via a browser (without a Matrix client)." msgstr "" -#: ../../../CHANGELOG.md:855 +#: ../../../CHANGELOG.md:886 msgid "The playbook now lets you [Decide between Element Call vs just the Matrix RTC stack](./docs/configuring-playbook-element-call.md#decide-between-element-call-vs-just-the-matrix-rtc-stack)." msgstr "" -#: ../../../CHANGELOG.md:857 +#: ../../../CHANGELOG.md:888 msgid "If you've already installed Element Call (via `matrix_element_call_enabled: true`), you can switch to installing just the [Matrix RTC (Real-Time Communication) stack](./docs/configuring-playbook-matrix-rtc.md) (all supporting services **without the Element Call frontend**) by:" msgstr "" -#: ../../../CHANGELOG.md:859 +#: ../../../CHANGELOG.md:890 msgid "Adjusting your `vars.yml` configuration like this:" msgstr "" -#: ../../../CHANGELOG.md:866 +#: ../../../CHANGELOG.md:897 msgid "[Re-running the playbook](./docs/installing.md) with the `setup-all` Ansible tag (e.g. `just setup-all`)" msgstr "" -#: ../../../CHANGELOG.md:868 +#: ../../../CHANGELOG.md:899 msgid "Getting rid of the `call.element.example.com` DNS record" msgstr "" -#: ../../../CHANGELOG.md:871 +#: ../../../CHANGELOG.md:902 msgid "2025-03-15" msgstr "" -#: ../../../CHANGELOG.md:873 +#: ../../../CHANGELOG.md:904 msgid "Element Call support" msgstr "" -#: ../../../CHANGELOG.md:875 +#: ../../../CHANGELOG.md:906 msgid "The playbook now supports [Element Call](https://github.com/element-hq/element-call) as an optional feature. Thanks to [wjbeckett](https://github.com/wjbeckett) for getting us started via [PR#3562](https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3562)." msgstr "" -#: ../../../CHANGELOG.md:877 +#: ../../../CHANGELOG.md:908 msgid "Element Call is a native Matrix video conferencing application developed by [Element](https://element.io/) that has the goal of replacing [Jitsi](./docs/configuring-playbook-jitsi.md) and the old WebRTC stack used in previous Element versions." msgstr "" -#: ../../../CHANGELOG.md:879 +#: ../../../CHANGELOG.md:910 msgid "💡 For now, Element Call is only supported with the [Synapse](docs/configuring-playbook-synapse.md) homeserver (with [federation](docs/configuring-playbook-federation.md) enabled) and [Element Web](docs/configuring-playbook-client-element-web.md) and Element X mobile clients. See the [Prerequisites](docs/configuring-playbook-element-call.md#prerequisites) section of the [Element Call documentation](docs/configuring-playbook-element-call.md) for more details." msgstr "" -#: ../../../CHANGELOG.md:881 +#: ../../../CHANGELOG.md:912 msgid "To get started, see the [Configuring Element Call](docs/configuring-playbook-element-call.md) documentation page." msgstr "" -#: ../../../CHANGELOG.md:884 +#: ../../../CHANGELOG.md:915 msgid "2025-03-08" msgstr "" -#: ../../../CHANGELOG.md:886 +#: ../../../CHANGELOG.md:917 msgid "6️⃣ IPv6 support enablement recommended by default" msgstr "" -#: ../../../CHANGELOG.md:888 +#: ../../../CHANGELOG.md:919 msgid "Our [default example configuration](./examples/vars.yml) and [Configuring DNS](./docs/configuring-dns.md) guides now recommend enabling [IPv6](https://en.wikipedia.org/wiki/IPv6) support. We recommend that everyone enables IPv6 support for their Matrix server, even if they don't have IPv6 connectivity yet." msgstr "" -#: ../../../CHANGELOG.md:890 +#: ../../../CHANGELOG.md:921 msgid "Our new [Configuring IPv6](./docs/configuring-ipv6.md) documentation page has more details about the playbook's IPv6 support." msgstr "" -#: ../../../CHANGELOG.md:892 +#: ../../../CHANGELOG.md:923 msgid "**Existing playbook users** will **need to do some manual work** to enable IPv6 support. This consists of:" msgstr "" -#: ../../../CHANGELOG.md:894 +#: ../../../CHANGELOG.md:925 msgid "enabling IPv6 support for the Docker container networks:" msgstr "" -#: ../../../CHANGELOG.md:895 +#: ../../../CHANGELOG.md:926 msgid "add `devture_systemd_docker_base_ipv6_enabled: true` to their `vars.yml` configuration file" msgstr "" -#: ../../../CHANGELOG.md:896 +#: ../../../CHANGELOG.md:927 msgid "stop all services (`just stop-all`)" msgstr "" -#: ../../../CHANGELOG.md:897 +#: ../../../CHANGELOG.md:928 msgid "delete all container networks on the server: `docker network rm $(docker network ls -q)`" msgstr "" -#: ../../../CHANGELOG.md:898 +#: ../../../CHANGELOG.md:929 msgid "re-run the playbook fully: `just install-all`" msgstr "" -#: ../../../CHANGELOG.md:900 +#: ../../../CHANGELOG.md:931 msgid "[configuring IPv6 (`AAAA`) DNS records](./docs/configuring-ipv6.md#configuring-dns-records-for-ipv6)" msgstr "" -#: ../../../CHANGELOG.md:902 +#: ../../../CHANGELOG.md:933 msgid "2025-02-26" msgstr "" -#: ../../../CHANGELOG.md:904 +#: ../../../CHANGELOG.md:935 msgid "🪦 Bye-bye, Email2Matrix" msgstr "" -#: ../../../CHANGELOG.md:906 +#: ../../../CHANGELOG.md:937 msgid "The [Email2Matrix](./docs/configuring-playbook-email2matrix.md) service has been superseded by the [Postmoogle](./docs/configuring-playbook-bridge-postmoogle.md) bridge for a long time now and was completely removed from the playbook today." msgstr "" -#: ../../../CHANGELOG.md:908 +#: ../../../CHANGELOG.md:939 msgid "If you still have the Email2Matrix component installed on your Matrix server, the playbook can no longer help you uninstall it and you will need to do it manually as described in the [Uninstalling Email2Matrix manually](./docs/configuring-playbook-email2matrix.md#uninstalling-email2matrix-manually) section of the documentation. The playbook will warn you if there are any `matrix_email2matrix_*` variables still remaining in your configuration." msgstr "" -#: ../../../CHANGELOG.md:911 +#: ../../../CHANGELOG.md:942 msgid "2025-02-23" msgstr "" -#: ../../../CHANGELOG.md:913 +#: ../../../CHANGELOG.md:944 msgid "The playbook defaults to exposing the Coturn STUN port (3478) over UDP once again" msgstr "" -#: ../../../CHANGELOG.md:915 +#: ../../../CHANGELOG.md:946 msgid "Recently, we made the playbook [default to exposing the Coturn STUN port (3478) only over TCP](#the-playbook-now-defaults-to-exposing-the-coturn-stun-port-3478-only-over-tcp) to reduce the severity of DDoS amplification/reflection attacks." msgstr "" -#: ../../../CHANGELOG.md:917 +#: ../../../CHANGELOG.md:948 msgid "It seems like old Element clients on mobile devices only support talking to the STUN port over UDP, not TCP. To accommodate such ancient clients, we're now **reversing this change** and **defaulting to exposing the Coturn STUN port (3478) over UDP once again**." msgstr "" -#: ../../../CHANGELOG.md:920 +#: ../../../CHANGELOG.md:951 msgid "In light of this new information, you have 2 options:" msgstr "" -#: ../../../CHANGELOG.md:922 +#: ../../../CHANGELOG.md:953 msgid "**If you already adapted to the previous change and would like to adapt to this change one again**:" msgstr "" -#: ../../../CHANGELOG.md:924 +#: ../../../CHANGELOG.md:955 msgid "make sure the `3478/udp` port is whitelisted in your external firewall (if you have one) once again." msgstr "" -#: ../../../CHANGELOG.md:926 +#: ../../../CHANGELOG.md:957 msgid "**If you don't care about old Element clients and wish to reduce the severity of DDoS amplification/reflection attacks**:" msgstr "" -#: ../../../CHANGELOG.md:928 +#: ../../../CHANGELOG.md:959 msgid "Consider closing the STUN/UDP port with the following configuration:" msgstr "" -#: ../../../CHANGELOG.md:934 +#: ../../../CHANGELOG.md:965 msgid "Consider keeping `3478/udp` blocked in your external firewall (if you have one)" msgstr "" -#: ../../../CHANGELOG.md:936 +#: ../../../CHANGELOG.md:967 msgid "2025-02-21" msgstr "" -#: ../../../CHANGELOG.md:938 +#: ../../../CHANGELOG.md:969 msgid "Docker daemon options are no longer adjusted when IPv6 is enabled" msgstr "" -#: ../../../CHANGELOG.md:940 +#: ../../../CHANGELOG.md:971 msgid "We landed [initial IPv6 support](#initial-work-on-ipv6-support) in the past via a `devture_systemd_docker_base_ipv6_enabled` variable that one had to toggle to `true`." msgstr "" -#: ../../../CHANGELOG.md:942 +#: ../../../CHANGELOG.md:973 msgid "This variable did **2 different things at once**:" msgstr "" -#: ../../../CHANGELOG.md:944 +#: ../../../CHANGELOG.md:975 msgid "ensured that container networks were created with IPv6 being enabled" msgstr "" -#: ../../../CHANGELOG.md:945 +#: ../../../CHANGELOG.md:976 msgid "adjusted the Docker daemon's configuration to set `experimental: true` and `ip6tables: true` (a necessary prerequisite for creating IPv6-enabled networks)" msgstr "" -#: ../../../CHANGELOG.md:947 +#: ../../../CHANGELOG.md:978 msgid "Since Docker 27.0.1's [changes to how it handles IPv6](https://docs.docker.com/engine/release-notes/27/#ipv6), **adjusting the Docker daemon's configuration is no longer necessary**, because:" msgstr "" -#: ../../../CHANGELOG.md:948 +#: ../../../CHANGELOG.md:979 msgid "`ip6tables` defaults to `true` for everyone" msgstr "" -#: ../../../CHANGELOG.md:949 +#: ../../../CHANGELOG.md:980 msgid "`ip6tables` is out of the experimental phase, so `experimental` is no longer necessary" msgstr "" -#: ../../../CHANGELOG.md:951 +#: ../../../CHANGELOG.md:982 msgid "In light of this, we're introducing a new variable (`devture_systemd_docker_base_ipv6_daemon_options_changing_enabled`) for controlling if IPv6 should be force-enabled in the Docker daemon's configuration options. Since most people should be on a modern enough Docker daemon version which doesn't require such changes, this variable defaults to `false`." msgstr "" -#: ../../../CHANGELOG.md:954 +#: ../../../CHANGELOG.md:985 msgid "This change affects you like this:" msgstr "" -#: ../../../CHANGELOG.md:956 +#: ../../../CHANGELOG.md:987 msgid "✅ if you're **not explicitly enabling IPv6** (via `devture_systemd_docker_base_ipv6_enabled` in your configuration): you're unaffected" msgstr "" -#: ../../../CHANGELOG.md:957 +#: ../../../CHANGELOG.md:988 msgid "❓ if you're **explicitly enabling IPv6** (via `devture_systemd_docker_base_ipv6_enabled` in your configuration):" msgstr "" -#: ../../../CHANGELOG.md:958 +#: ../../../CHANGELOG.md:989 msgid "✅ .. and you're on a modern enough Docker version (which you most likely are): the playbook will no longer mess with your Docker daemon options. You're unaffected." msgstr "" -#: ../../../CHANGELOG.md:959 +#: ../../../CHANGELOG.md:990 msgid "🔧 .. and you're on an old Docker version, you **are affected** and need to use the following configuration to restore the old behavior:" msgstr "" -#: ../../../CHANGELOG.md:970 +#: ../../../CHANGELOG.md:1001 msgid "Support for bridging to Bluesky via mautrix-bluesky" msgstr "" -#: ../../../CHANGELOG.md:972 +#: ../../../CHANGELOG.md:1003 msgid "Thanks to [Zepmann](https://github.com/Zepmann), the playbook now supports bridging to [Bluesky](https://bsky.app/) via [mautrix-bluesky](https://github.com/mautrix/bluesky)." msgstr "" -#: ../../../CHANGELOG.md:974 +#: ../../../CHANGELOG.md:1005 msgid "To learn more, see our [Setting up mautrix-bluesky](./docs/configuring-playbook-bridge-mautrix-bluesky.md) documentation page." msgstr "" -#: ../../../CHANGELOG.md:977 +#: ../../../CHANGELOG.md:1008 msgid "2025-02-19" msgstr "" -#: ../../../CHANGELOG.md:979 +#: ../../../CHANGELOG.md:1010 msgid "The playbook now defaults to exposing the Coturn STUN port (3478) only over TCP" msgstr "" -#: ../../../CHANGELOG.md:981 +#: ../../../CHANGELOG.md:1012 msgid "We've previously done some work to **decrease the severity** of DDoS amplification attacks done through the [Coturn](./docs/configuring-playbook-turn.md)'s STUN port (2.8x -> 1.6x) as reported in [coturn: Lower DDoS amplification/reflection factor from 2.8 to 1.6 #2592](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2592)." msgstr "" -#: ../../../CHANGELOG.md:983 +#: ../../../CHANGELOG.md:1014 msgid "To **completely eliminate the problem** of DDoS amplification attacks done through the [Coturn](./docs/configuring-playbook-turn.md) STUN port even further (read more about this in [this article](https://stormwall.network/resources/blog/protect-against-ddos-based-on-stun-exploit)), the playbook now **disables exposure of the Coturn STUN port (`3478`) over UDP**. This is a bit heavy-handed, but is probably the only way to completely eliminate the problem." msgstr "" -#: ../../../CHANGELOG.md:985 +#: ../../../CHANGELOG.md:1016 msgid "The playbook now **only exposes the Coturn STUN port (`3478`) over TCP by default**." msgstr "" -#: ../../../CHANGELOG.md:987 +#: ../../../CHANGELOG.md:1018 msgid "💡 Users may wish to further remove the (now unnecessary) firewall rule allowing access to `3478/udp`." msgstr "" -#: ../../../CHANGELOG.md:989 +#: ../../../CHANGELOG.md:1020 msgid "If you'd like the Coturn STUN port to be exposed over UDP like before, you can revert to the previous behavior by using the following configuration in your `vars.yml` file:" msgstr "" -#: ../../../CHANGELOG.md:996 +#: ../../../CHANGELOG.md:1027 msgid "People running Coturn directly on the `host` network (using `coturn_container_network: host`) will still have the STUN port exposed over UDP, as port exposure is done directly via Coturn and not via Docker. In such cases, the playbook cannot prevent `3478/udp` port exposure and you'd need to do it in another way (separate firewall rule, etc)." msgstr "" -#: ../../../CHANGELOG.md:999 +#: ../../../CHANGELOG.md:1030 msgid "2025-02-17" msgstr "" -#: ../../../CHANGELOG.md:1001 +#: ../../../CHANGELOG.md:1032 msgid "FluffyChat Web support" msgstr "" -#: ../../../CHANGELOG.md:1003 +#: ../../../CHANGELOG.md:1034 msgid "Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook now supports [FluffyChat Web](https://github.com/krille-chan/fluffychat) as an additional Matrix client you can self-host." msgstr "" -#: ../../../CHANGELOG.md:1005 +#: ../../../CHANGELOG.md:1036 msgid "To learn more, see our [Setting up FluffyChat Web](docs/configuring-playbook-client-fluffychat-web.md) documentation page." msgstr "" -#: ../../../CHANGELOG.md:1008 +#: ../../../CHANGELOG.md:1039 msgid "2025-02-03" msgstr "" -#: ../../../CHANGELOG.md:1010 +#: ../../../CHANGELOG.md:1041 msgid "The mautrix-hangouts bridge has been removed from the playbook" msgstr "" -#: ../../../CHANGELOG.md:1012 +#: ../../../CHANGELOG.md:1043 msgid "The [mautrix-hangouts](./docs/configuring-playbook-bridge-mautrix-hangouts.md) bridge has been deprecated in the playbook since December 2024 and finally got completely removed from the playbook in February 2025." msgstr "" -#: ../../../CHANGELOG.md:1014 +#: ../../../CHANGELOG.md:1045 msgid "This is because Google Hangouts has been discontinued since the 1st of November 2022." msgstr "" -#: ../../../CHANGELOG.md:1016 +#: ../../../CHANGELOG.md:1047 msgid "The playbook will let you know if you're using any `matrix_mautrix_hangouts_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the bridge manually](./docs/configuring-playbook-bridge-mautrix-hangouts.md#uninstalling-the-bridge-manually)." msgstr "" -#: ../../../CHANGELOG.md:1019 +#: ../../../CHANGELOG.md:1050 msgid "2025-01-27" msgstr "" -#: ../../../CHANGELOG.md:1021 +#: ../../../CHANGELOG.md:1052 msgid "Redis and KeyDB are no longer part of the playbook" msgstr "" -#: ../../../CHANGELOG.md:1023 +#: ../../../CHANGELOG.md:1054 msgid "**TLDR**: The playbook now exclusively uses Valkey as its Redis-compatible memorystore implementation, removing support for Redis and KeyDB. Most users are unaffected by this change unless they explicitly configured Redis or KeyDB variables. Only users that were explicitly defining `redis_*` or `keydb_*` variables will need to update their configuration to use `valkey_*` variables instead." msgstr "" -#: ../../../CHANGELOG.md:1025 +#: ../../../CHANGELOG.md:1056 msgid "The playbook has gone through several iterations of memorystore implementations:" msgstr "" -#: ../../../CHANGELOG.md:1027 +#: ../../../CHANGELOG.md:1058 msgid "It initially used Redis, auto-installing it when needed by features/services" msgstr "" -#: ../../../CHANGELOG.md:1028 +#: ../../../CHANGELOG.md:1059 msgid "[Switched to KeyDB](#backward-compatibility-break-the-playbook-now-defaults-to-keydb-instead-of-redis) as the default, while keeping Redis support for those who wished to remain on Redis" msgstr "" -#: ../../../CHANGELOG.md:1029 +#: ../../../CHANGELOG.md:1060 msgid "[Switched to Valkey](#backward-compatibility-break-the-playbook-now-defaults-to-valkey-instead-of-keydb) due to [KeyDB issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3544), while keeping Redis and KeyDB support, for those who wished to remain on them" msgstr "" -#: ../../../CHANGELOG.md:1031 +#: ../../../CHANGELOG.md:1062 msgid "To reduce configuration complexity and maintenance overhead, we are now:" msgstr "" -#: ../../../CHANGELOG.md:1033 +#: ../../../CHANGELOG.md:1064 msgid "removing Redis and KeyDB support entirely" msgstr "" -#: ../../../CHANGELOG.md:1034 +#: ../../../CHANGELOG.md:1065 msgid "using Valkey as the sole Redis-compatible memorystore implementation" msgstr "" -#: ../../../CHANGELOG.md:1036 +#: ../../../CHANGELOG.md:1067 msgid "To update your configuration:" msgstr "" -#: ../../../CHANGELOG.md:1038 +#: ../../../CHANGELOG.md:1069 msgid "**Most users** don't need to do anything" msgstr "" -#: ../../../CHANGELOG.md:1039 +#: ../../../CHANGELOG.md:1070 msgid "**Users that were explicitly sticking to Redis/KeyDB** need to update their `vars.yml` to use `valkey_*` variables instead" msgstr "" -#: ../../../CHANGELOG.md:1042 +#: ../../../CHANGELOG.md:1073 msgid "2025-01-19" msgstr "" -#: ../../../CHANGELOG.md:1044 +#: ../../../CHANGELOG.md:1075 msgid "conduwuit support" msgstr "" -#: ../../../CHANGELOG.md:1046 +#: ../../../CHANGELOG.md:1077 msgid "Thanks to [Virkkunen](https://github.com/Virkkunen), we now have optional experimental [conduwuit](https://conduwuit.puppyirl.gay/) homeserver support for new installations." msgstr "" -#: ../../../CHANGELOG.md:1048 +#: ../../../CHANGELOG.md:1079 msgid "conduwuit is a fork of [Conduit](./docs/configuring-playbook-conduit.md), which the playbook also supports. See [Differences from upstream Conduit](https://conduwuit.puppyirl.gay/differences.html)." msgstr "" -#: ../../../CHANGELOG.md:1052 +#: ../../../CHANGELOG.md:1083 msgid "To try out conduwuit, we recommend that you **use a new server**. Refer to our [Configuring conduwuit](./docs/configuring-playbook-conduwuit.md) guide for details." msgstr "" -#: ../../../CHANGELOG.md:1054 +#: ../../../CHANGELOG.md:1085 msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse/Conduit/Dendrite to conduwuit) without data loss." msgstr "" -#: ../../../CHANGELOG.md:1057 +#: ../../../CHANGELOG.md:1088 msgid "2025-01-14" msgstr "" -#: ../../../CHANGELOG.md:1059 +#: ../../../CHANGELOG.md:1090 msgid "(Backward Compatibility Break) Synapse v1.122.0 requires Postgres v13" msgstr "" -#: ../../../CHANGELOG.md:1061 +#: ../../../CHANGELOG.md:1092 msgid "The Synapse homeserver [requires Postgres v13 or newer](https://github.com/element-hq/synapse/issues/18034)." msgstr "" -#: ../../../CHANGELOG.md:1063 +#: ../../../CHANGELOG.md:1094 msgid "If you've been maintaining your setup for a while and you haven't been doing [Postgres upgrades](docs/maintenance-postgres.md#upgrading-postgresql), you may be on an old version of Postgres. The easiest way to check is to see the contents of the `/matrix/postgres/data/PG_VERSION` file." msgstr "" -#: ../../../CHANGELOG.md:1065 +#: ../../../CHANGELOG.md:1096 msgid "If you're on a Postgres version older than v13, you need to [upgrade your Postgres setup](docs/maintenance-postgres.md#upgrading-postgresql) or Synapse will produce an error on startup." msgstr "" -#: ../../../CHANGELOG.md:1067 +#: ../../../CHANGELOG.md:1098 msgid "If you're using an external Postgres server (not installed by this playbook), you'll need to figure out how to upgrade it yourself." msgstr "" -#: ../../../CHANGELOG.md:1069 +#: ../../../CHANGELOG.md:1100 msgid "If you're not ready to upgrade your Postgres setup yet, you can temporarily remain on an old Synapse version by adding the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../CHANGELOG.md:1077 +#: ../../../CHANGELOG.md:1108 msgid "2024-11-26" msgstr "" -#: ../../../CHANGELOG.md:1079 +#: ../../../CHANGELOG.md:1110 msgid "(Backward Compatibility Break) Synapse now defaults to enabling authenticated media" msgstr "" -#: ../../../CHANGELOG.md:1081 +#: ../../../CHANGELOG.md:1112 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:1083 +#: ../../../CHANGELOG.md:1114 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:1085 +#: ../../../CHANGELOG.md:1116 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:1087 +#: ../../../CHANGELOG.md:1118 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:1089 +#: ../../../CHANGELOG.md:1120 msgid "We're changing the playbook configuration for authenticated media to keep up with upstream defaults changing." msgstr "" -#: ../../../CHANGELOG.md:1091 +#: ../../../CHANGELOG.md:1122 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:1093 +#: ../../../CHANGELOG.md:1124 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:1096 +#: ../../../CHANGELOG.md:1127 msgid "2024-11-23" msgstr "" -#: ../../../CHANGELOG.md:1098 +#: ../../../CHANGELOG.md:1129 msgid "(Backward Compatibility Break) The playbook now defaults to Valkey, instead of KeyDB" msgstr "" -#: ../../../CHANGELOG.md:1100 +#: ../../../CHANGELOG.md:1131 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:1102 +#: ../../../CHANGELOG.md:1133 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:1104 +#: ../../../CHANGELOG.md:1135 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:1106 +#: ../../../CHANGELOG.md:1137 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:1108 +#: ../../../CHANGELOG.md:1139 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:1110 +#: ../../../CHANGELOG.md:1141 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:1112 +#: ../../../CHANGELOG.md:1143 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:1114 -#: ../../../CHANGELOG.md:1454 +#: ../../../CHANGELOG.md:1145 +#: ../../../CHANGELOG.md:1485 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:1125 +#: ../../../CHANGELOG.md:1156 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:1135 +#: ../../../CHANGELOG.md:1166 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:1138 +#: ../../../CHANGELOG.md:1169 msgid "2024-11-14" msgstr "" -#: ../../../CHANGELOG.md:1140 +#: ../../../CHANGELOG.md:1171 msgid "HTTP-compression support for Traefik-based setups" msgstr "" -#: ../../../CHANGELOG.md:1142 +#: ../../../CHANGELOG.md:1173 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:1144 +#: ../../../CHANGELOG.md:1175 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:1146 +#: ../../../CHANGELOG.md:1177 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:1148 +#: ../../../CHANGELOG.md:1179 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:1150 +#: ../../../CHANGELOG.md:1181 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:1152 +#: ../../../CHANGELOG.md:1183 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:1153 +#: ../../../CHANGELOG.md:1184 msgid "setting `matrix_playbook_reverse_proxy_traefik_middleware_compression_enabled` to `true`" msgstr "" -#: ../../../CHANGELOG.md:1154 +#: ../../../CHANGELOG.md:1185 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:1156 +#: ../../../CHANGELOG.md:1187 msgid "Timeout adjustments for Traefik-based setups" msgstr "" -#: ../../../CHANGELOG.md:1158 +#: ../../../CHANGELOG.md:1189 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:1160 +#: ../../../CHANGELOG.md:1191 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:1162 +#: ../../../CHANGELOG.md:1193 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:1164 +#: ../../../CHANGELOG.md:1195 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:1166 +#: ../../../CHANGELOG.md:1197 msgid "Example of the default timeout values used by the playbook:" msgstr "" -#: ../../../CHANGELOG.md:1177 +#: ../../../CHANGELOG.md:1208 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:1180 +#: ../../../CHANGELOG.md:1211 msgid "2024-11-08" msgstr "" -#: ../../../CHANGELOG.md:1182 +#: ../../../CHANGELOG.md:1213 msgid "Support for synapse-admin auto-configuration via /.well-known/matrix/client" msgstr "" -#: ../../../CHANGELOG.md:1184 +#: ../../../CHANGELOG.md:1215 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:1186 +#: ../../../CHANGELOG.md:1217 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:1188 +#: ../../../CHANGELOG.md:1219 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:1191 +#: ../../../CHANGELOG.md:1222 msgid "2024-10-28" msgstr "" -#: ../../../CHANGELOG.md:1193 +#: ../../../CHANGELOG.md:1224 msgid "(BC Break) Postmoogle's variable names need adjustments" msgstr "" -#: ../../../CHANGELOG.md:1195 +#: ../../../CHANGELOG.md:1226 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:1197 +#: ../../../CHANGELOG.md:1228 msgid "2024-10-19" msgstr "" -#: ../../../CHANGELOG.md:1199 +#: ../../../CHANGELOG.md:1230 msgid "Support for Matrix Authentication Service" msgstr "" -#: ../../../CHANGELOG.md:1201 +#: ../../../CHANGELOG.md:1232 msgid "The playbook now supports installing and configuring [Matrix Authentication Service](./docs/configuring-playbook-matrix-authentication-service.md) (MAS)." msgstr "" -#: ../../../CHANGELOG.md:1203 +#: ../../../CHANGELOG.md:1234 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:1205 +#: ../../../CHANGELOG.md:1236 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:1207 +#: ../../../CHANGELOG.md:1238 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:1210 +#: ../../../CHANGELOG.md:1241 msgid "2024-09-27" msgstr "" -#: ../../../CHANGELOG.md:1212 +#: ../../../CHANGELOG.md:1243 msgid "(BC Break) Postgres & Traefik roles have been relocated and variable names need adjustments" msgstr "" -#: ../../../CHANGELOG.md:1214 +#: ../../../CHANGELOG.md:1245 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:1216 +#: ../../../CHANGELOG.md:1247 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:1218 +#: ../../../CHANGELOG.md:1249 msgid "You need to do the following replacements:" msgstr "" -#: ../../../CHANGELOG.md:1220 +#: ../../../CHANGELOG.md:1251 msgid "`devture_postgres_` -> `postgres_`" msgstr "" -#: ../../../CHANGELOG.md:1221 +#: ../../../CHANGELOG.md:1252 msgid "`devture_traefik_` -> `traefik_`" msgstr "" -#: ../../../CHANGELOG.md:1226 +#: ../../../CHANGELOG.md:1257 msgid "2024-09-12" msgstr "" -#: ../../../CHANGELOG.md:1228 +#: ../../../CHANGELOG.md:1259 msgid "Support for baibot" msgstr "" -#: ../../../CHANGELOG.md:1230 +#: ../../../CHANGELOG.md:1261 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:1232 +#: ../../../CHANGELOG.md:1263 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:1234 +#: ../../../CHANGELOG.md:1265 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:1236 +#: ../../../CHANGELOG.md:1267 msgid "To get started, see the [Setting up baibot](./docs/configuring-playbook-bot-baibot.md) documentation page." msgstr "" -#: ../../../CHANGELOG.md:1238 +#: ../../../CHANGELOG.md:1269 msgid "Switching synapse-admin to etke.cc's fork" msgstr "" -#: ../../../CHANGELOG.md:1240 +#: ../../../CHANGELOG.md:1271 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:1242 +#: ../../../CHANGELOG.md:1273 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:1244 +#: ../../../CHANGELOG.md:1275 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:1246 +#: ../../../CHANGELOG.md:1277 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:1259 +#: ../../../CHANGELOG.md:1290 msgid "2024-08-17" msgstr "" -#: ../../../CHANGELOG.md:1261 +#: ../../../CHANGELOG.md:1292 msgid "New appservice-double-puppet service for better double-puppeting" msgstr "" -#: ../../../CHANGELOG.md:1263 +#: ../../../CHANGELOG.md:1294 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:1265 +#: ../../../CHANGELOG.md:1296 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:1267 +#: ../../../CHANGELOG.md:1298 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:1269 +#: ../../../CHANGELOG.md:1300 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:1271 +#: ../../../CHANGELOG.md:1302 msgid "We recommend **enabling double-puppeting via the new Appservice method** by adding the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../CHANGELOG.md:1277 +#: ../../../CHANGELOG.md:1308 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:1279 +#: ../../../CHANGELOG.md:1310 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:1282 +#: ../../../CHANGELOG.md:1313 msgid "2024-08-15" msgstr "" -#: ../../../CHANGELOG.md:1284 +#: ../../../CHANGELOG.md:1315 msgid "matrix-media-repo now configured for Authenticated Media" msgstr "" -#: ../../../CHANGELOG.md:1286 +#: ../../../CHANGELOG.md:1317 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:1288 +#: ../../../CHANGELOG.md:1319 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:1290 +#: ../../../CHANGELOG.md:1321 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:1292 +#: ../../../CHANGELOG.md:1323 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:1295 +#: ../../../CHANGELOG.md:1326 msgid "2024-08-08" msgstr "" -#: ../../../CHANGELOG.md:1297 +#: ../../../CHANGELOG.md:1328 msgid "(Backward Compatibility Break) matrix-corporal has been upgraded to v3" msgstr "" -#: ../../../CHANGELOG.md:1299 +#: ../../../CHANGELOG.md:1330 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:1301 +#: ../../../CHANGELOG.md:1332 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:1303 +#: ../../../CHANGELOG.md:1334 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:1309 +#: ../../../CHANGELOG.md:1340 msgid "2024-07-25" msgstr "" -#: ../../../CHANGELOG.md:1311 +#: ../../../CHANGELOG.md:1342 msgid "synapse-usage-exporter support" msgstr "" -#: ../../../CHANGELOG.md:1313 +#: ../../../CHANGELOG.md:1344 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:1315 +#: ../../../CHANGELOG.md:1346 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:1318 +#: ../../../CHANGELOG.md:1349 msgid "2024-07-06" msgstr "" -#: ../../../CHANGELOG.md:1320 +#: ../../../CHANGELOG.md:1351 msgid "matrix-alertmanager-receiver support" msgstr "" -#: ../../../CHANGELOG.md:1322 +#: ../../../CHANGELOG.md:1353 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:1324 +#: ../../../CHANGELOG.md:1355 msgid "See [Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](./docs/configuring-playbook-alertmanager-receiver.md) for more details." msgstr "" -#: ../../../CHANGELOG.md:1326 +#: ../../../CHANGELOG.md:1357 msgid "Traefik v3 and HTTP/3 are here now" msgstr "" -#: ../../../CHANGELOG.md:1328 +#: ../../../CHANGELOG.md:1359 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:1330 +#: ../../../CHANGELOG.md:1361 msgid "Traefik v3" msgstr "" -#: ../../../CHANGELOG.md:1332 +#: ../../../CHANGELOG.md:1363 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:1334 +#: ../../../CHANGELOG.md:1365 msgid "We have **updated the playbook to Traefik v3** (make sure to run `just roles` / `make roles` to get it)." msgstr "" -#: ../../../CHANGELOG.md:1336 +#: ../../../CHANGELOG.md:1367 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:1338 +#: ../../../CHANGELOG.md:1369 msgid "**Most people using the playbook should not have to do any changes**." msgstr "" -#: ../../../CHANGELOG.md:1340 +#: ../../../CHANGELOG.md:1371 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:1342 +#: ../../../CHANGELOG.md:1373 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:1344 +#: ../../../CHANGELOG.md:1375 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:1346 +#: ../../../CHANGELOG.md:1377 msgid "HTTP/3 is enabled by default" msgstr "" -#: ../../../CHANGELOG.md:1348 +#: ../../../CHANGELOG.md:1379 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:1350 +#: ../../../CHANGELOG.md:1381 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:1352 +#: ../../../CHANGELOG.md:1383 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:1354 +#: ../../../CHANGELOG.md:1385 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:1356 +#: ../../../CHANGELOG.md:1387 msgid "To **disable HTTP/3**, you can use the following configuration:" msgstr "" -#: ../../../CHANGELOG.md:1370 +#: ../../../CHANGELOG.md:1401 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:1383 +#: ../../../CHANGELOG.md:1414 msgid "2024-07-01" msgstr "" -#: ../../../CHANGELOG.md:1385 +#: ../../../CHANGELOG.md:1416 msgid "synapse-admin is now restricted to your homeserver's URL by default" msgstr "" -#: ../../../CHANGELOG.md:1387 +#: ../../../CHANGELOG.md:1418 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:1389 +#: ../../../CHANGELOG.md:1420 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:1391 +#: ../../../CHANGELOG.md:1422 msgid "If you'd like **to go back to the old unrestricted behavior**, use the following configuration:" msgstr "" -#: ../../../CHANGELOG.md:1399 +#: ../../../CHANGELOG.md:1430 msgid "2024-06-25" msgstr "" -#: ../../../CHANGELOG.md:1401 +#: ../../../CHANGELOG.md:1432 msgid "The URL-prefix for Hookshot generic webhooks has changed" msgstr "" -#: ../../../CHANGELOG.md:1403 +#: ../../../CHANGELOG.md:1434 msgid "Until now, generic Hookshot webhook URLs looked like this: `https://matrix.example.com/hookshot/webhooks/:hookId`." msgstr "" -#: ../../../CHANGELOG.md:1405 +#: ../../../CHANGELOG.md:1436 msgid "The `/hookshot/webhooks` common prefix gets stripped by Traefik automatically, so Hookshot only sees the part that comes after (`/:hookId`)." msgstr "" -#: ../../../CHANGELOG.md:1407 +#: ../../../CHANGELOG.md:1438 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:1409 +#: ../../../CHANGELOG.md:1440 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:1411 +#: ../../../CHANGELOG.md:1442 msgid "When generating new webhooks, you should start seeing the new URLs being used." msgstr "" -#: ../../../CHANGELOG.md:1413 +#: ../../../CHANGELOG.md:1444 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:1415 +#: ../../../CHANGELOG.md:1446 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:1418 +#: ../../../CHANGELOG.md:1449 msgid "2024-06-22" msgstr "" -#: ../../../CHANGELOG.md:1420 +#: ../../../CHANGELOG.md:1451 msgid "The maubot user is now managed by the playbook" msgstr "" -#: ../../../CHANGELOG.md:1422 +#: ../../../CHANGELOG.md:1453 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:1424 +#: ../../../CHANGELOG.md:1455 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:1426 +#: ../../../CHANGELOG.md:1457 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:1429 +#: ../../../CHANGELOG.md:1460 msgid "2024-06-03" msgstr "" -#: ../../../CHANGELOG.md:1431 +#: ../../../CHANGELOG.md:1462 msgid "WeChat bridging support" msgstr "" -#: ../../../CHANGELOG.md:1433 +#: ../../../CHANGELOG.md:1464 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:1435 +#: ../../../CHANGELOG.md:1466 msgid "See our [Setting up WeChat bridging](docs/configuring-playbook-bridge-wechat.md) documentation page for getting started." msgstr "" -#: ../../../CHANGELOG.md:1438 +#: ../../../CHANGELOG.md:1469 msgid "2024-03-26" msgstr "" -#: ../../../CHANGELOG.md:1440 +#: ../../../CHANGELOG.md:1471 msgid "(Backward Compatibility Break) The playbook now defaults to KeyDB, instead of Redis" msgstr "" -#: ../../../CHANGELOG.md:1442 +#: ../../../CHANGELOG.md:1473 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:1444 +#: ../../../CHANGELOG.md:1475 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:1446 +#: ../../../CHANGELOG.md:1477 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:1448 +#: ../../../CHANGELOG.md:1479 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:1450 +#: ../../../CHANGELOG.md:1481 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:1452 +#: ../../../CHANGELOG.md:1483 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:1463 +#: ../../../CHANGELOG.md:1494 msgid "2024-03-24" msgstr "" -#: ../../../CHANGELOG.md:1465 +#: ../../../CHANGELOG.md:1496 msgid "Initial work on IPv6 support" msgstr "" -#: ../../../CHANGELOG.md:1467 +#: ../../../CHANGELOG.md:1498 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:1469 +#: ../../../CHANGELOG.md:1500 msgid "It should be noted that:" msgstr "" -#: ../../../CHANGELOG.md:1471 +#: ../../../CHANGELOG.md:1502 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:1472 +#: ../../../CHANGELOG.md:1503 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:1473 +#: ../../../CHANGELOG.md:1504 msgid "this is all very new and untested" msgstr "" -#: ../../../CHANGELOG.md:1475 +#: ../../../CHANGELOG.md:1506 msgid "Pantalaimon support" msgstr "" -#: ../../../CHANGELOG.md:1477 +#: ../../../CHANGELOG.md:1508 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:1479 +#: ../../../CHANGELOG.md:1510 msgid "See our [Setting up Pantalaimon](docs/configuring-playbook-pantalaimon.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:1482 +#: ../../../CHANGELOG.md:1513 msgid "2024-03-05" msgstr "" -#: ../../../CHANGELOG.md:1484 +#: ../../../CHANGELOG.md:1515 msgid "Support for Draupnir-for-all" msgstr "" -#: ../../../CHANGELOG.md:1486 +#: ../../../CHANGELOG.md:1517 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:1488 +#: ../../../CHANGELOG.md:1519 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:1490 +#: ../../../CHANGELOG.md:1521 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:1493 +#: ../../../CHANGELOG.md:1524 msgid "2024-02-19" msgstr "" -#: ../../../CHANGELOG.md:1495 +#: ../../../CHANGELOG.md:1526 msgid "Support for bridging to Facebook/Messenger via the new mautrix-meta bridge" msgstr "" -#: ../../../CHANGELOG.md:1497 +#: ../../../CHANGELOG.md:1528 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:1499 +#: ../../../CHANGELOG.md:1530 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:1501 +#: ../../../CHANGELOG.md:1532 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:1503 +#: ../../../CHANGELOG.md:1534 msgid "[Setting up Instagram bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-instagram.md)" msgstr "" -#: ../../../CHANGELOG.md:1505 +#: ../../../CHANGELOG.md:1536 msgid "[Setting up Messenger bridging via Mautrix Meta](docs/configuring-playbook-bridge-mautrix-meta-messenger.md)" msgstr "" -#: ../../../CHANGELOG.md:1507 +#: ../../../CHANGELOG.md:1538 msgid "The documentation pages contain more information on how to migrate." msgstr "" -#: ../../../CHANGELOG.md:1510 +#: ../../../CHANGELOG.md:1541 msgid "2024-02-14" msgstr "" -#: ../../../CHANGELOG.md:1512 +#: ../../../CHANGELOG.md:1543 msgid "Much larger Synapse caches and cache auto-tuning enabled by default" msgstr "" -#: ../../../CHANGELOG.md:1514 +#: ../../../CHANGELOG.md:1545 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:1516 +#: ../../../CHANGELOG.md:1547 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:1518 +#: ../../../CHANGELOG.md:1549 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:1520 +#: ../../../CHANGELOG.md:1551 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:1521 +#: ../../../CHANGELOG.md:1552 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:1522 +#: ../../../CHANGELOG.md:1553 msgid "`matrix_synapse_cache_autotuning_min_cache_ttl` — defaults to `30s`" msgstr "" -#: ../../../CHANGELOG.md:1524 +#: ../../../CHANGELOG.md:1555 msgid "These values should be good defaults for most servers, but may change over time as we experiment further." msgstr "" -#: ../../../CHANGELOG.md:1526 +#: ../../../CHANGELOG.md:1557 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:1529 +#: ../../../CHANGELOG.md:1560 msgid "2024-01-31" msgstr "" -#: ../../../CHANGELOG.md:1531 +#: ../../../CHANGELOG.md:1562 msgid "(Backward-compatibility break) Minor changes necessary for some people serving a static website at the base domain" msgstr "" -#: ../../../CHANGELOG.md:1533 +#: ../../../CHANGELOG.md:1564 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:1535 +#: ../../../CHANGELOG.md:1566 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:1537 +#: ../../../CHANGELOG.md:1568 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:1540 +#: ../../../CHANGELOG.md:1571 msgid "2024-01-20" msgstr "" -#: ../../../CHANGELOG.md:1542 +#: ../../../CHANGELOG.md:1573 msgid "Support for more efficient (specialized) Synapse workers" msgstr "" -#: ../../../CHANGELOG.md:1544 +#: ../../../CHANGELOG.md:1575 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:1546 +#: ../../../CHANGELOG.md:1577 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:1548 +#: ../../../CHANGELOG.md:1579 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:1550 +#: ../../../CHANGELOG.md:1581 msgid "To get started, refer to our [Specialized workers](./docs/configuring-playbook-synapse.md#specialized-workers) documentation section." msgstr "" -#: ../../../CHANGELOG.md:1553 +#: ../../../CHANGELOG.md:1584 msgid "2024-01-17" msgstr "" -#: ../../../CHANGELOG.md:1555 +#: ../../../CHANGELOG.md:1586 msgid "Switching to Element's AGPLv3-licensed Synapse release" msgstr "" -#: ../../../CHANGELOG.md:1557 +#: ../../../CHANGELOG.md:1588 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:1559 +#: ../../../CHANGELOG.md:1590 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:1560 +#: ../../../CHANGELOG.md:1591 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:1562 +#: ../../../CHANGELOG.md:1593 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:1564 +#: ../../../CHANGELOG.md:1595 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:1566 +#: ../../../CHANGELOG.md:1597 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:1568 +#: ../../../CHANGELOG.md:1599 msgid "**What does this mean to you?**" msgstr "" -#: ../../../CHANGELOG.md:1570 +#: ../../../CHANGELOG.md:1601 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:1572 +#: ../../../CHANGELOG.md:1603 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:1574 +#: ../../../CHANGELOG.md:1605 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:1576 +#: ../../../CHANGELOG.md:1607 msgid "If you'd like to continue using the old Apache-2.0-licensed Synapse (for a while longer anyway), the playbook makes it possible by introducing a new Ansible variable. You can do it like this:" msgstr "" -#: ../../../CHANGELOG.md:1588 +#: ../../../CHANGELOG.md:1619 msgid "Notes:" msgstr "" -#: ../../../CHANGELOG.md:1590 +#: ../../../CHANGELOG.md:1621 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:1592 +#: ../../../CHANGELOG.md:1623 msgid "running an outdated homeserver exposes you to security issues and incompatibilities. Only consider doing this as a short-term solution." msgstr "" -#: ../../../CHANGELOG.md:1594 +#: ../../../CHANGELOG.md:1625 msgid "2024-01-16" msgstr "" -#: ../../../CHANGELOG.md:1596 +#: ../../../CHANGELOG.md:1627 msgid "`Draupnir` has been relicensed to AFL-3.0" msgstr "" -#: ../../../CHANGELOG.md:1598 +#: ../../../CHANGELOG.md:1629 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:1600 +#: ../../../CHANGELOG.md:1631 msgid "2024-01-15" msgstr "" -#: ../../../CHANGELOG.md:1602 +#: ../../../CHANGELOG.md:1633 msgid "Goodbye, `matrix-nginx-proxy` 🪦" msgstr "" -#: ../../../CHANGELOG.md:1604 +#: ../../../CHANGELOG.md:1635 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:1606 +#: ../../../CHANGELOG.md:1637 msgid "Backstory on `matrix-nginx-proxy`" msgstr "" -#: ../../../CHANGELOG.md:1608 +#: ../../../CHANGELOG.md:1639 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:1610 +#: ../../../CHANGELOG.md:1641 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:1612 +#: ../../../CHANGELOG.md:1643 msgid "To us, `matrix-nginx-proxy` was:" msgstr "" -#: ../../../CHANGELOG.md:1614 +#: ../../../CHANGELOG.md:1645 msgid "an [nginx](https://nginx.org/)-based reverse-proxy" msgstr "" -#: ../../../CHANGELOG.md:1615 +#: ../../../CHANGELOG.md:1646 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:1616 +#: ../../../CHANGELOG.md:1647 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:1617 +#: ../../../CHANGELOG.md:1648 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:1618 +#: ../../../CHANGELOG.md:1649 msgid "a webserver for serving the `/.well-known/matrix` static files (generated by the `matrix-base` role until now)" msgstr "" -#: ../../../CHANGELOG.md:1619 +#: ../../../CHANGELOG.md:1650 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:1620 +#: ../../../CHANGELOG.md:1651 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:1622 +#: ../../../CHANGELOG.md:1653 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:1624 +#: ../../../CHANGELOG.md:1655 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:1626 +#: ../../../CHANGELOG.md:1657 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:1628 +#: ../../../CHANGELOG.md:1659 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:1630 +#: ../../../CHANGELOG.md:1661 msgid "Going Traefik-native and cutting out all middlemen" msgstr "" -#: ../../../CHANGELOG.md:1632 +#: ../../../CHANGELOG.md:1663 msgid "In our new setup, you'll see the bare minimum number of reverse-proxies." msgstr "" -#: ../../../CHANGELOG.md:1634 +#: ../../../CHANGELOG.md:1665 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:1636 +#: ../../../CHANGELOG.md:1667 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:1638 +#: ../../../CHANGELOG.md:1669 msgid "Traefik now has an extra job" msgstr "" -#: ../../../CHANGELOG.md:1640 +#: ../../../CHANGELOG.md:1671 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:1642 +#: ../../../CHANGELOG.md:1673 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:1644 +#: ../../../CHANGELOG.md:1675 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:1646 +#: ../../../CHANGELOG.md:1677 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:1648 +#: ../../../CHANGELOG.md:1679 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:1650 +#: ../../../CHANGELOG.md:1681 msgid "Traefik serving this second purpose has a few downsides:" msgstr "" -#: ../../../CHANGELOG.md:1652 +#: ../../../CHANGELOG.md:1683 msgid "Traefik becomes a runtime dependency for all homeserver-dependant container services" msgstr "" -#: ../../../CHANGELOG.md:1653 +#: ../../../CHANGELOG.md:1684 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:1655 +#: ../../../CHANGELOG.md:1686 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:1657 +#: ../../../CHANGELOG.md:1688 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:1659 +#: ../../../CHANGELOG.md:1690 msgid "**People running their own Traefik reverse-proxy need to do [minor adjustments](#people-managing-their-own-traefik-instance-need-to-do-minor-changes)**, as described in the section below." msgstr "" -#: ../../../CHANGELOG.md:1661 +#: ../../../CHANGELOG.md:1692 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:1663 +#: ../../../CHANGELOG.md:1694 msgid "People managing their own Traefik instance need to do minor changes" msgstr "" -#: ../../../CHANGELOG.md:1665 +#: ../../../CHANGELOG.md:1696 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:1667 +#: ../../../CHANGELOG.md:1698 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:1669 +#: ../../../CHANGELOG.md:1700 msgid "People fronting Traefik with another reverse proxy need to do minor changes" msgstr "" -#: ../../../CHANGELOG.md:1671 +#: ../../../CHANGELOG.md:1702 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:1673 +#: ../../../CHANGELOG.md:1704 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:1675 +#: ../../../CHANGELOG.md:1706 msgid "Supported reverse proxy types are now fewer" msgstr "" -#: ../../../CHANGELOG.md:1677 +#: ../../../CHANGELOG.md:1708 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:1679 +#: ../../../CHANGELOG.md:1710 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:1681 +#: ../../../CHANGELOG.md:1712 msgid "The complexity of this is too high, so we only support 3 values right now:" msgstr "" -#: ../../../CHANGELOG.md:1683 +#: ../../../CHANGELOG.md:1714 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:1684 +#: ../../../CHANGELOG.md:1715 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:1685 +#: ../../../CHANGELOG.md:1716 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:1687 +#: ../../../CHANGELOG.md:1718 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:1689 +#: ../../../CHANGELOG.md:1720 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:1691 +#: ../../../CHANGELOG.md:1722 msgid "If you were using these values as a way to stay away from Traefik, you now have 2 options:" msgstr "" -#: ../../../CHANGELOG.md:1693 +#: ../../../CHANGELOG.md:1724 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:1694 +#: ../../../CHANGELOG.md:1725 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:1696 +#: ../../../CHANGELOG.md:1727 msgid "Container networking changes" msgstr "" -#: ../../../CHANGELOG.md:1698 +#: ../../../CHANGELOG.md:1729 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:1700 +#: ../../../CHANGELOG.md:1731 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:1702 +#: ../../../CHANGELOG.md:1733 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:1704 +#: ../../../CHANGELOG.md:1735 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:1706 +#: ../../../CHANGELOG.md:1737 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:1708 +#: ../../../CHANGELOG.md:1739 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:1710 +#: ../../../CHANGELOG.md:1741 msgid "Metrics exposure changes" msgstr "" -#: ../../../CHANGELOG.md:1712 +#: ../../../CHANGELOG.md:1743 msgid "This section is for people who are exposing monitoring metrics publicly, to be consumed by an external Prometheus server." msgstr "" -#: ../../../CHANGELOG.md:1714 +#: ../../../CHANGELOG.md:1745 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:1716 +#: ../../../CHANGELOG.md:1747 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:1718 +#: ../../../CHANGELOG.md:1749 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:1720 +#: ../../../CHANGELOG.md:1751 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:1722 +#: ../../../CHANGELOG.md:1753 msgid "Matrix static files" msgstr "" -#: ../../../CHANGELOG.md:1724 +#: ../../../CHANGELOG.md:1755 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:1726 +#: ../../../CHANGELOG.md:1757 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:1728 +#: ../../../CHANGELOG.md:1759 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:1730 +#: ../../../CHANGELOG.md:1761 msgid "A note on performance" msgstr "" -#: ../../../CHANGELOG.md:1732 +#: ../../../CHANGELOG.md:1763 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:1734 +#: ../../../CHANGELOG.md:1765 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:1736 +#: ../../../CHANGELOG.md:1767 msgid "We believe that using Traefik provides way too many benefits to worry about this minor performance impairment." msgstr "" -#: ../../../CHANGELOG.md:1738 +#: ../../../CHANGELOG.md:1769 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:1740 +#: ../../../CHANGELOG.md:1771 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:1742 +#: ../../../CHANGELOG.md:1773 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:1744 +#: ../../../CHANGELOG.md:1775 msgid "Migration procedure" msgstr "" -#: ../../../CHANGELOG.md:1746 +#: ../../../CHANGELOG.md:1777 msgid "The updated playbook will automatically perform some migration tasks for you:" msgstr "" -#: ../../../CHANGELOG.md:1748 +#: ../../../CHANGELOG.md:1779 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:1750 +#: ../../../CHANGELOG.md:1781 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:1752 +#: ../../../CHANGELOG.md:1783 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:1754 +#: ../../../CHANGELOG.md:1785 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:1756 +#: ../../../CHANGELOG.md:1787 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:1758 +#: ../../../CHANGELOG.md:1789 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:1760 +#: ../../../CHANGELOG.md:1791 msgid "We don't recommend changing these variables and suppressing warnings, unless you know what you're doing." msgstr "" -#: ../../../CHANGELOG.md:1762 +#: ../../../CHANGELOG.md:1793 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:1764 +#: ../../../CHANGELOG.md:1795 msgid "Conclusion" msgstr "" -#: ../../../CHANGELOG.md:1766 +#: ../../../CHANGELOG.md:1797 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:1768 +#: ../../../CHANGELOG.md:1799 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:1771 +#: ../../../CHANGELOG.md:1802 msgid "2024-01-14" msgstr "" -#: ../../../CHANGELOG.md:1773 +#: ../../../CHANGELOG.md:1804 msgid "(Backward Compatibility) Configuration changes required for people fronting the integrated reverse-proxy webserver with another reverse-proxy" msgstr "" -#: ../../../CHANGELOG.md:1775 +#: ../../../CHANGELOG.md:1806 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:1777 +#: ../../../CHANGELOG.md:1808 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:1779 +#: ../../../CHANGELOG.md:1810 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:1781 +#: ../../../CHANGELOG.md:1812 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:1783 +#: ../../../CHANGELOG.md:1814 msgid "Adapt your configuration as seen below:" msgstr "" -#: ../../../CHANGELOG.md:1816 +#: ../../../CHANGELOG.md:1847 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:1819 +#: ../../../CHANGELOG.md:1850 msgid "2024-01-13" msgstr "" -#: ../../../CHANGELOG.md:1821 +#: ../../../CHANGELOG.md:1852 msgid "matrix-reminder-bot update with more secure (backward-incompatible) default settings" msgstr "" -#: ../../../CHANGELOG.md:1823 +#: ../../../CHANGELOG.md:1854 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:1825 +#: ../../../CHANGELOG.md:1856 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:1827 +#: ../../../CHANGELOG.md:1858 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:1829 +#: ../../../CHANGELOG.md:1860 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:1831 +#: ../../../CHANGELOG.md:1862 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:1833 +#: ../../../CHANGELOG.md:1864 msgid "If you need **to undo or tweak these security improvements**, you can change your `vars.yml` file to:" msgstr "" -#: ../../../CHANGELOG.md:1835 +#: ../../../CHANGELOG.md:1866 msgid "disable the allowlist (`matrix_bot_matrix_reminder_bot_allowlist_enabled: false`), making the bot allow usage by anyone, anywhere" msgstr "" -#: ../../../CHANGELOG.md:1837 +#: ../../../CHANGELOG.md:1868 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:1839 +#: ../../../CHANGELOG.md:1870 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:1842 +#: ../../../CHANGELOG.md:1873 msgid "2024-01-05" msgstr "" -#: ../../../CHANGELOG.md:1844 +#: ../../../CHANGELOG.md:1875 msgid "matrix-mailer has been replaced by the exim-relay external role" msgstr "" -#: ../../../CHANGELOG.md:1846 -#: ../../../CHANGELOG.md:2484 +#: ../../../CHANGELOG.md:1877 +#: ../../../CHANGELOG.md:2515 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:1848 +#: ../../../CHANGELOG.md:1879 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:1850 +#: ../../../CHANGELOG.md:1881 msgid "To migrate:" msgstr "" -#: ../../../CHANGELOG.md:1852 +#: ../../../CHANGELOG.md:1883 msgid "pull the playbook changes, as usual" msgstr "" -#: ../../../CHANGELOG.md:1853 +#: ../../../CHANGELOG.md:1884 msgid "update your roles (run `just roles` or `make roles`)" msgstr "" -#: ../../../CHANGELOG.md:1854 +#: ../../../CHANGELOG.md:1885 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:1855 +#: ../../../CHANGELOG.md:1886 msgid "re-run the playbook (`install-all` or `setup-all`)" msgstr "" -#: ../../../CHANGELOG.md:1857 +#: ../../../CHANGELOG.md:1888 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:1860 +#: ../../../CHANGELOG.md:1891 msgid "2024-01-02" msgstr "" -#: ../../../CHANGELOG.md:1862 +#: ../../../CHANGELOG.md:1893 msgid "mautrix-signal now powered by the new Go-based bridge" msgstr "" -#: ../../../CHANGELOG.md:1864 +#: ../../../CHANGELOG.md:1895 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:1866 +#: ../../../CHANGELOG.md:1897 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:1868 +#: ../../../CHANGELOG.md:1899 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:1871 +#: ../../../CHANGELOG.md:1902 msgid "2023-10-23" msgstr "" -#: ../../../CHANGELOG.md:1873 +#: ../../../CHANGELOG.md:1904 msgid "Enabling `allow_public_rooms_over_federation` by default for Synapse" msgstr "" -#: ../../../CHANGELOG.md:1875 +#: ../../../CHANGELOG.md:1906 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:1877 +#: ../../../CHANGELOG.md:1908 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:1879 +#: ../../../CHANGELOG.md:1910 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:1881 +#: ../../../CHANGELOG.md:1912 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:1883 +#: ../../../CHANGELOG.md:1914 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:1885 +#: ../../../CHANGELOG.md:1916 msgid "The **historical reasoning** behind this change is as follows:" msgstr "" -#: ../../../CHANGELOG.md:1887 +#: ../../../CHANGELOG.md:1918 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:1889 +#: ../../../CHANGELOG.md:1920 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:1891 +#: ../../../CHANGELOG.md:1922 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:1893 +#: ../../../CHANGELOG.md:1924 msgid "Here are **actions you may wish to take** as a result of this change:" msgstr "" -#: ../../../CHANGELOG.md:1895 +#: ../../../CHANGELOG.md:1926 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:1897 +#: ../../../CHANGELOG.md:1928 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:1899 +#: ../../../CHANGELOG.md:1930 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:1902 +#: ../../../CHANGELOG.md:1933 msgid "2023-10-18" msgstr "" -#: ../../../CHANGELOG.md:1904 +#: ../../../CHANGELOG.md:1935 msgid "Postgres parameters are automatically tuned now" msgstr "" -#: ../../../CHANGELOG.md:1906 +#: ../../../CHANGELOG.md:1937 msgid "The playbook has provided some hints about [Tuning PostgreSQL](docs/maintenance-postgres.md#tuning-postgresql) for quite a while now." msgstr "" -#: ../../../CHANGELOG.md:1908 +#: ../../../CHANGELOG.md:1939 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:1910 +#: ../../../CHANGELOG.md:1941 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:1912 +#: ../../../CHANGELOG.md:1943 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:1915 +#: ../../../CHANGELOG.md:1946 msgid "2023-08-31" msgstr "" -#: ../../../CHANGELOG.md:1917 +#: ../../../CHANGELOG.md:1948 msgid "SchildiChat Web support" msgstr "" -#: ../../../CHANGELOG.md:1919 +#: ../../../CHANGELOG.md:1950 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:1921 +#: ../../../CHANGELOG.md:1952 msgid "See our [Configuring SchildiChat Web](docs/configuring-playbook-client-schildichat-web.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:1924 +#: ../../../CHANGELOG.md:1955 msgid "2023-08-23" msgstr "" -#: ../../../CHANGELOG.md:1926 +#: ../../../CHANGELOG.md:1957 msgid "mautrix-wsproxy support" msgstr "" -#: ../../../CHANGELOG.md:1928 +#: ../../../CHANGELOG.md:1959 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:1930 +#: ../../../CHANGELOG.md:1961 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:1933 +#: ../../../CHANGELOG.md:1964 msgid "2023-07-24" msgstr "" -#: ../../../CHANGELOG.md:1935 +#: ../../../CHANGELOG.md:1966 msgid "matrix-registration-bot usage changed" msgstr "" -#: ../../../CHANGELOG.md:1937 +#: ../../../CHANGELOG.md:1968 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:1939 +#: ../../../CHANGELOG.md:1970 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:1941 +#: ../../../CHANGELOG.md:1972 msgid "`matrix_bot_matrix_registration_bot_bot_access_token`" msgstr "" -#: ../../../CHANGELOG.md:1942 +#: ../../../CHANGELOG.md:1973 msgid "`matrix_bot_matrix_registration_bot_api_token`" msgstr "" -#: ../../../CHANGELOG.md:1945 +#: ../../../CHANGELOG.md:1976 msgid "2023-07-21" msgstr "" -#: ../../../CHANGELOG.md:1947 +#: ../../../CHANGELOG.md:1978 msgid "mautrix-gmessages support" msgstr "" -#: ../../../CHANGELOG.md:1949 +#: ../../../CHANGELOG.md:1980 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:1952 +#: ../../../CHANGELOG.md:1983 msgid "2023-07-17" msgstr "" -#: ../../../CHANGELOG.md:1954 +#: ../../../CHANGELOG.md:1985 msgid "matrix-media-repo support" msgstr "" -#: ../../../CHANGELOG.md:1956 +#: ../../../CHANGELOG.md:1987 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:1958 +#: ../../../CHANGELOG.md:1989 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:1961 +#: ../../../CHANGELOG.md:1992 msgid "2023-05-25" msgstr "" -#: ../../../CHANGELOG.md:1963 +#: ../../../CHANGELOG.md:1994 msgid "Enabling `forget_rooms_on_leave` by default for Synapse" msgstr "" -#: ../../../CHANGELOG.md:1965 +#: ../../../CHANGELOG.md:1996 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:1967 +#: ../../../CHANGELOG.md:1998 msgid "The upstream Synapse default is `false` (disabled), so that you must forget rooms manually after leaving." msgstr "" -#: ../../../CHANGELOG.md:1969 +#: ../../../CHANGELOG.md:2000 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:1971 +#: ../../../CHANGELOG.md:2002 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:1974 +#: ../../../CHANGELOG.md:2005 msgid "2023-04-03" msgstr "" -#: ../../../CHANGELOG.md:1976 +#: ../../../CHANGELOG.md:2007 msgid "The matrix-jitsi role lives independently now" msgstr "" -#: ../../../CHANGELOG.md:1978 +#: ../../../CHANGELOG.md:2009 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:1980 +#: ../../../CHANGELOG.md:2011 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:1982 +#: ../../../CHANGELOG.md:2013 msgid "As part of the extraction process of this role out of the Matrix playbook, a few other things improved:" msgstr "" -#: ../../../CHANGELOG.md:1984 +#: ../../../CHANGELOG.md:2015 msgid "**native Traefik support** has been added" msgstr "" -#: ../../../CHANGELOG.md:1985 +#: ../../../CHANGELOG.md:2016 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:1987 +#: ../../../CHANGELOG.md:2018 msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Jitsi or not." msgstr "" -#: ../../../CHANGELOG.md:1989 +#: ../../../CHANGELOG.md:2020 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:1991 +#: ../../../CHANGELOG.md:2022 msgid "`matrix_jitsi_*_docker_image_` -> `matrix_jitsi_*_container_image_`" msgstr "" -#: ../../../CHANGELOG.md:1992 +#: ../../../CHANGELOG.md:2023 msgid "`matrix_jitsi_` -> `jitsi_`" msgstr "" -#: ../../../CHANGELOG.md:1993 -#: ../../../CHANGELOG.md:2020 +#: ../../../CHANGELOG.md:2024 +#: ../../../CHANGELOG.md:2051 msgid "some other internal variables have changed, but the playbook will tell you about them" msgstr "" -#: ../../../CHANGELOG.md:1995 +#: ../../../CHANGELOG.md:2026 msgid "2023-03-22" msgstr "" -#: ../../../CHANGELOG.md:1997 +#: ../../../CHANGELOG.md:2028 msgid "ntfy Web App is disabled by default" msgstr "" -#: ../../../CHANGELOG.md:1999 +#: ../../../CHANGELOG.md:2030 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:2001 +#: ../../../CHANGELOG.md:2032 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:2004 +#: ../../../CHANGELOG.md:2035 msgid "2023-03-21" msgstr "" -#: ../../../CHANGELOG.md:2006 +#: ../../../CHANGELOG.md:2037 msgid "The matrix-prometheus role lives independently now" msgstr "" -#: ../../../CHANGELOG.md:2008 +#: ../../../CHANGELOG.md:2039 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:2010 +#: ../../../CHANGELOG.md:2041 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:2012 +#: ../../../CHANGELOG.md:2043 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:2014 +#: ../../../CHANGELOG.md:2045 msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Prometheus or not." msgstr "" -#: ../../../CHANGELOG.md:2016 +#: ../../../CHANGELOG.md:2047 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:2018 +#: ../../../CHANGELOG.md:2049 msgid "`matrix_prometheus_docker_image_` -> `matrix_prometheus_container_image_`" msgstr "" -#: ../../../CHANGELOG.md:2019 +#: ../../../CHANGELOG.md:2050 msgid "`matrix_prometheus_` -> `prometheus_`" msgstr "" -#: ../../../CHANGELOG.md:2023 +#: ../../../CHANGELOG.md:2054 msgid "2023-03-12" msgstr "" -#: ../../../CHANGELOG.md:2025 +#: ../../../CHANGELOG.md:2056 msgid "synapse-auto-compressor support" msgstr "" -#: ../../../CHANGELOG.md:2027 +#: ../../../CHANGELOG.md:2058 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:2029 +#: ../../../CHANGELOG.md:2060 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:2031 +#: ../../../CHANGELOG.md:2062 msgid "it runs on a more up-to-date version of `rust-synapse-compress-state`" msgstr "" -#: ../../../CHANGELOG.md:2032 +#: ../../../CHANGELOG.md:2063 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:2034 +#: ../../../CHANGELOG.md:2065 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:2036 +#: ../../../CHANGELOG.md:2067 msgid "See our [Setting up synapse-auto-compressor](docs/configuring-playbook-synapse-auto-compressor.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:2039 +#: ../../../CHANGELOG.md:2070 msgid "2023-03-07" msgstr "" -#: ../../../CHANGELOG.md:2041 +#: ../../../CHANGELOG.md:2072 msgid "Sliding Sync proxy (Element X) support" msgstr "" -#: ../../../CHANGELOG.md:2043 +#: ../../../CHANGELOG.md:2074 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:2045 +#: ../../../CHANGELOG.md:2076 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:2047 +#: ../../../CHANGELOG.md:2078 msgid "To get started, see our [Setting up the Sliding Sync proxy](docs/configuring-playbook-sliding-sync-proxy.md) documentation page." msgstr "" -#: ../../../CHANGELOG.md:2050 +#: ../../../CHANGELOG.md:2081 msgid "2023-03-02" msgstr "" -#: ../../../CHANGELOG.md:2052 +#: ../../../CHANGELOG.md:2083 msgid "The matrix-etherpad role lives independently now" msgstr "" -#: ../../../CHANGELOG.md:2054 +#: ../../../CHANGELOG.md:2085 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:2056 +#: ../../../CHANGELOG.md:2087 msgid "You need to **update your roles** (`just roles` or `make roles`) regardless of whether you're using Etherpad or not." msgstr "" -#: ../../../CHANGELOG.md:2058 +#: ../../../CHANGELOG.md:2089 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:2060 +#: ../../../CHANGELOG.md:2091 msgid "Rename `matrix_etherpad_public_endpoint` to `etherpad_path_prefix`" msgstr "" -#: ../../../CHANGELOG.md:2062 +#: ../../../CHANGELOG.md:2093 msgid "Replace `matrix_etherpad_mode: dimension` with:" msgstr "" -#: ../../../CHANGELOG.md:2063 +#: ../../../CHANGELOG.md:2094 msgid "for `matrix-nginx-proxy` users:" msgstr "" -#: ../../../CHANGELOG.md:2064 +#: ../../../CHANGELOG.md:2095 msgid "`etherpad_nginx_proxy_dimension_integration_enabled: true`" msgstr "" -#: ../../../CHANGELOG.md:2065 +#: ../../../CHANGELOG.md:2096 msgid "`etherpad_hostname: \"{{ matrix_server_fqn_dimension }}\"`" msgstr "" -#: ../../../CHANGELOG.md:2066 +#: ../../../CHANGELOG.md:2097 msgid "for Traefik users:" msgstr "" -#: ../../../CHANGELOG.md:2067 +#: ../../../CHANGELOG.md:2098 msgid "define your own `etherpad_hostname` and `etherpad_path_prefix` as you see fit" msgstr "" -#: ../../../CHANGELOG.md:2069 +#: ../../../CHANGELOG.md:2100 msgid "Rename all other variables:" msgstr "" -#: ../../../CHANGELOG.md:2070 +#: ../../../CHANGELOG.md:2101 msgid "`matrix_etherpad_docker_image_` -> `matrix_etherpad_container_image_`" msgstr "" -#: ../../../CHANGELOG.md:2071 +#: ../../../CHANGELOG.md:2102 msgid "`matrix_etherpad_` -> `etherpad_`" msgstr "" -#: ../../../CHANGELOG.md:2073 +#: ../../../CHANGELOG.md:2104 msgid "Along with this relocation, the new role also:" msgstr "" -#: ../../../CHANGELOG.md:2075 +#: ../../../CHANGELOG.md:2106 msgid "supports [self-building](docs/self-building.md), so it should work on `arm32` and `arm64` architectures" msgstr "" -#: ../../../CHANGELOG.md:2076 +#: ../../../CHANGELOG.md:2107 msgid "has native Traefik reverse-proxy support (Etherpad requests no longer go through `matrix-nginx-proxy` when using Traefik)" msgstr "" -#: ../../../CHANGELOG.md:2079 +#: ../../../CHANGELOG.md:2110 msgid "2023-02-26" msgstr "" -#: ../../../CHANGELOG.md:2081 +#: ../../../CHANGELOG.md:2112 msgid "Traefik is the default reverse-proxy now" msgstr "" -#: ../../../CHANGELOG.md:2083 +#: ../../../CHANGELOG.md:2114 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:2085 +#: ../../../CHANGELOG.md:2116 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:2087 +#: ../../../CHANGELOG.md:2118 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:2089 +#: ../../../CHANGELOG.md:2120 msgid "Traefik managed by the playbook" msgstr "" -#: ../../../CHANGELOG.md:2090 +#: ../../../CHANGELOG.md:2121 msgid "Traefik managed by the user in another way" msgstr "" -#: ../../../CHANGELOG.md:2091 +#: ../../../CHANGELOG.md:2122 msgid "another reverse-proxy on the same host (`127.0.0.1` port exposure)" msgstr "" -#: ../../../CHANGELOG.md:2092 +#: ../../../CHANGELOG.md:2123 msgid "another reverse-proxy on another host (`0.0.0.0` port exposure)" msgstr "" -#: ../../../CHANGELOG.md:2093 +#: ../../../CHANGELOG.md:2124 msgid "`matrix-nginx-proxy` — an `nginx` container managed by the playbook" msgstr "" -#: ../../../CHANGELOG.md:2094 +#: ../../../CHANGELOG.md:2125 msgid "`nginx` webserver operated by the user, running without a container on the same server" msgstr "" -#: ../../../CHANGELOG.md:2096 +#: ../../../CHANGELOG.md:2127 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:2098 +#: ../../../CHANGELOG.md:2129 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:2100 +#: ../../../CHANGELOG.md:2131 msgid "It's time for the **next step in our migration process** to Traefik and elimination of `matrix-nginx-proxy`:" msgstr "" -#: ../../../CHANGELOG.md:2102 +#: ../../../CHANGELOG.md:2133 msgid "Traefik is now the default reverse-proxy for new installations" msgstr "" -#: ../../../CHANGELOG.md:2103 +#: ../../../CHANGELOG.md:2134 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:2105 +#: ../../../CHANGELOG.md:2136 msgid "How do I switch my existing setup to Traefik?" msgstr "" -#: ../../../CHANGELOG.md:2107 +#: ../../../CHANGELOG.md:2138 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:2109 +#: ../../../CHANGELOG.md:2140 msgid "If you experience trouble:" msgstr "" -#: ../../../CHANGELOG.md:2111 +#: ../../../CHANGELOG.md:2142 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:2112 +#: ../../../CHANGELOG.md:2143 msgid "Ask for help in our [support channels](README.md#support)" msgstr "" -#: ../../../CHANGELOG.md:2113 +#: ../../../CHANGELOG.md:2144 msgid "Try switching to Traefik again later" msgstr "" -#: ../../../CHANGELOG.md:2115 +#: ../../../CHANGELOG.md:2146 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:2117 +#: ../../../CHANGELOG.md:2148 msgid "I already use my own Traefik server. How do I plug that in?" msgstr "" -#: ../../../CHANGELOG.md:2119 +#: ../../../CHANGELOG.md:2150 msgid "See the [Traefik managed by the playbook](docs/configuring-playbook-own-webserver.md#traefik-managed-by-the-playbook) section." msgstr "" -#: ../../../CHANGELOG.md:2121 +#: ../../../CHANGELOG.md:2152 msgid "Why is matrix-nginx-proxy used even after switching to Traefik?" msgstr "" -#: ../../../CHANGELOG.md:2123 +#: ../../../CHANGELOG.md:2154 msgid "This playbook manages many different services. All these services were initially integrated with `matrix-nginx-proxy`." msgstr "" -#: ../../../CHANGELOG.md:2125 +#: ../../../CHANGELOG.md:2156 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:2127 +#: ../../../CHANGELOG.md:2158 msgid "How do I remain on matrix-nginx-proxy?" msgstr "" -#: ../../../CHANGELOG.md:2129 +#: ../../../CHANGELOG.md:2160 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:2131 +#: ../../../CHANGELOG.md:2162 msgid "To proceed regardless of this warning, add `matrix_playbook_reverse_proxy_type: playbook-managed-nginx` to your configuration." msgstr "" -#: ../../../CHANGELOG.md:2133 +#: ../../../CHANGELOG.md:2164 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:2135 +#: ../../../CHANGELOG.md:2166 msgid "How do I keep using my own other reverse-proxy?" msgstr "" -#: ../../../CHANGELOG.md:2137 +#: ../../../CHANGELOG.md:2168 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:2140 +#: ../../../CHANGELOG.md:2171 msgid "2023-02-25" msgstr "" -#: ../../../CHANGELOG.md:2142 +#: ../../../CHANGELOG.md:2173 msgid "rageshake support" msgstr "" -#: ../../../CHANGELOG.md:2144 +#: ../../../CHANGELOG.md:2175 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:2146 +#: ../../../CHANGELOG.md:2177 msgid "Additional details are available in [Setting up rageshake](docs/configuring-playbook-rageshake.md)." msgstr "" -#: ../../../CHANGELOG.md:2149 +#: ../../../CHANGELOG.md:2180 msgid "2023-02-17" msgstr "" -#: ../../../CHANGELOG.md:2151 +#: ../../../CHANGELOG.md:2182 msgid "Synapse templates customization support" msgstr "" -#: ../../../CHANGELOG.md:2153 +#: ../../../CHANGELOG.md:2184 msgid "The playbook can now help you customize Synapse's templates." msgstr "" -#: ../../../CHANGELOG.md:2155 +#: ../../../CHANGELOG.md:2186 msgid "Additional details are available in the [Customizing templates](docs/configuring-playbook-synapse.md#customizing-templates) section of our Synapse documentation." msgstr "" -#: ../../../CHANGELOG.md:2157 +#: ../../../CHANGELOG.md:2188 msgid "The matrix-redis role lives independently now" msgstr "" -#: ../../../CHANGELOG.md:2159 +#: ../../../CHANGELOG.md:2190 msgid "**TLDR**: the `matrix-redis` role is now included from another repository. Some variables have been renamed. All functionality remains intact." msgstr "" -#: ../../../CHANGELOG.md:2161 +#: ../../../CHANGELOG.md:2192 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:2163 +#: ../../../CHANGELOG.md:2194 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:2165 +#: ../../../CHANGELOG.md:2196 msgid "The matrix-ntfy role lives independently now" msgstr "" -#: ../../../CHANGELOG.md:2167 +#: ../../../CHANGELOG.md:2198 msgid "**TLDR**: the `matrix-ntfy` role is now included from another repository. Some variables have been renamed. All functionality remains intact." msgstr "" -#: ../../../CHANGELOG.md:2169 +#: ../../../CHANGELOG.md:2200 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:2171 +#: ../../../CHANGELOG.md:2202 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:2174 +#: ../../../CHANGELOG.md:2205 msgid "2023-02-15" msgstr "" -#: ../../../CHANGELOG.md:2176 +#: ../../../CHANGELOG.md:2207 msgid "The matrix-grafana role lives independently now" msgstr "" -#: ../../../CHANGELOG.md:2178 +#: ../../../CHANGELOG.md:2209 msgid "**TLDR**: the `matrix-grafana` role is now included from another repository. Some variables have been renamed. All functionality remains intact." msgstr "" -#: ../../../CHANGELOG.md:2180 +#: ../../../CHANGELOG.md:2211 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:2182 +#: ../../../CHANGELOG.md:2213 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:2185 +#: ../../../CHANGELOG.md:2216 msgid "2023-02-13" msgstr "" -#: ../../../CHANGELOG.md:2187 +#: ../../../CHANGELOG.md:2218 msgid "The matrix-backup-borg role lives independently now" msgstr "" -#: ../../../CHANGELOG.md:2189 +#: ../../../CHANGELOG.md:2220 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:2191 +#: ../../../CHANGELOG.md:2222 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:2193 +#: ../../../CHANGELOG.md:2224 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:2196 +#: ../../../CHANGELOG.md:2227 msgid "2023-02-12" msgstr "" -#: ../../../CHANGELOG.md:2198 +#: ../../../CHANGELOG.md:2229 msgid "(Backward Compatibility) Reverse-proxy configuration changes and initial Traefik support" msgstr "" -#: ../../../CHANGELOG.md:2200 +#: ../../../CHANGELOG.md:2231 msgid "**TLDR**:" msgstr "" -#: ../../../CHANGELOG.md:2202 +#: ../../../CHANGELOG.md:2233 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:2203 +#: ../../../CHANGELOG.md:2234 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:2204 +#: ../../../CHANGELOG.md:2235 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:2205 +#: ../../../CHANGELOG.md:2236 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:2206 +#: ../../../CHANGELOG.md:2237 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:2208 +#: ../../../CHANGELOG.md:2239 msgid "Motivation for redoing our reverse-proxy setup" msgstr "" -#: ../../../CHANGELOG.md:2210 +#: ../../../CHANGELOG.md:2241 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:2212 +#: ../../../CHANGELOG.md:2243 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:2214 +#: ../../../CHANGELOG.md:2245 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:2216 +#: ../../../CHANGELOG.md:2247 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:2218 +#: ../../../CHANGELOG.md:2249 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:2220 +#: ../../../CHANGELOG.md:2251 msgid "*either* relying on `matrix_nginx_proxy_enabled: false` as well, combined with exposing services manually (setting `_bind_port` variables)" msgstr "" -#: ../../../CHANGELOG.md:2221 +#: ../../../CHANGELOG.md:2252 msgid "*or* better yet, they were keeping `matrix-nginx-proxy` enabled, but in `http`-only mode (no SSL certificate retrieval)." msgstr "" -#: ../../../CHANGELOG.md:2223 +#: ../../../CHANGELOG.md:2254 msgid "Despite this operational complexity, things worked and were reasonably flexible to adapt to all these situations." msgstr "" -#: ../../../CHANGELOG.md:2225 +#: ../../../CHANGELOG.md:2256 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:2227 +#: ../../../CHANGELOG.md:2258 msgid "The next problem is one of **efficiency, interoperability and cost-saving**. We're working on other playbooks:" msgstr "" -#: ../../../CHANGELOG.md:2229 +#: ../../../CHANGELOG.md:2260 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:2230 +#: ../../../CHANGELOG.md:2261 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:2231 +#: ../../../CHANGELOG.md:2262 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:2233 +#: ../../../CHANGELOG.md:2264 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:2235 +#: ../../../CHANGELOG.md:2266 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:2237 +#: ../../../CHANGELOG.md:2268 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:2239 +#: ../../../CHANGELOG.md:2270 msgid "How do these changes fix all these problems?" msgstr "" -#: ../../../CHANGELOG.md:2241 +#: ../../../CHANGELOG.md:2272 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:2243 +#: ../../../CHANGELOG.md:2274 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:2245 +#: ../../../CHANGELOG.md:2276 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:2247 +#: ../../../CHANGELOG.md:2278 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:2249 +#: ../../../CHANGELOG.md:2280 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:2251 +#: ../../../CHANGELOG.md:2282 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:2253 +#: ../../../CHANGELOG.md:2284 msgid "Where we're at right now?" msgstr "" -#: ../../../CHANGELOG.md:2255 +#: ../../../CHANGELOG.md:2286 msgid "`matrix_playbook_reverse_proxy_type` still defaults to a value of `playbook-managed-nginx`." msgstr "" -#: ../../../CHANGELOG.md:2257 +#: ../../../CHANGELOG.md:2288 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:2259 +#: ../../../CHANGELOG.md:2290 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:2261 +#: ../../../CHANGELOG.md:2292 msgid "How do I explicitly switch to Traefik right now?" msgstr "" -#: ../../../CHANGELOG.md:2263 +#: ../../../CHANGELOG.md:2294 msgid "**Users who wish to migrate to Traefik** today, can do so by **adding** this to their configuration:" msgstr "" -#: ../../../CHANGELOG.md:2269 +#: ../../../CHANGELOG.md:2300 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:2271 +#: ../../../CHANGELOG.md:2302 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:2273 +#: ../../../CHANGELOG.md:2304 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:2275 +#: ../../../CHANGELOG.md:2306 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:2277 +#: ../../../CHANGELOG.md:2308 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:2279 +#: ../../../CHANGELOG.md:2310 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:2281 +#: ../../../CHANGELOG.md:2312 msgid "Where we're going in the near future?" msgstr "" -#: ../../../CHANGELOG.md:2283 +#: ../../../CHANGELOG.md:2314 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:2285 +#: ../../../CHANGELOG.md:2316 msgid "For now, `matrix-nginx-proxy` will stay around." msgstr "" -#: ../../../CHANGELOG.md:2287 +#: ../../../CHANGELOG.md:2318 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:2289 +#: ../../../CHANGELOG.md:2320 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:2291 +#: ../../../CHANGELOG.md:2322 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:2292 +#: ../../../CHANGELOG.md:2323 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:2294 +#: ../../../CHANGELOG.md:2325 msgid "How do I help?" msgstr "" -#: ../../../CHANGELOG.md:2296 +#: ../../../CHANGELOG.md:2327 msgid "You can help by:" msgstr "" -#: ../../../CHANGELOG.md:2298 +#: ../../../CHANGELOG.md:2329 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:2300 +#: ../../../CHANGELOG.md:2331 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:2302 +#: ../../../CHANGELOG.md:2333 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:2305 +#: ../../../CHANGELOG.md:2336 msgid "2023-02-10" msgstr "" -#: ../../../CHANGELOG.md:2307 +#: ../../../CHANGELOG.md:2338 msgid "Matrix Authentication Support for Jitsi" msgstr "" -#: ../../../CHANGELOG.md:2309 +#: ../../../CHANGELOG.md:2340 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:2311 +#: ../../../CHANGELOG.md:2342 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:2313 +#: ../../../CHANGELOG.md:2344 msgid "Draupnir moderation tool (bot) support" msgstr "" -#: ../../../CHANGELOG.md:2315 +#: ../../../CHANGELOG.md:2346 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:2317 +#: ../../../CHANGELOG.md:2348 msgid "Additional details are available in [Setting up Draupnir](docs/configuring-playbook-bot-draupnir.md)." msgstr "" -#: ../../../CHANGELOG.md:2320 +#: ../../../CHANGELOG.md:2351 msgid "2023-02-05" msgstr "" -#: ../../../CHANGELOG.md:2322 +#: ../../../CHANGELOG.md:2353 msgid "The matrix-prometheus-postgres-exporter role lives independently now" msgstr "" -#: ../../../CHANGELOG.md:2324 +#: ../../../CHANGELOG.md:2355 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:2326 +#: ../../../CHANGELOG.md:2357 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:2328 +#: ../../../CHANGELOG.md:2359 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:2330 +#: ../../../CHANGELOG.md:2361 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:2332 -#: ../../../CHANGELOG.md:2374 +#: ../../../CHANGELOG.md:2363 +#: ../../../CHANGELOG.md:2405 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:2335 +#: ../../../CHANGELOG.md:2366 msgid "2023-01-26" msgstr "" -#: ../../../CHANGELOG.md:2337 +#: ../../../CHANGELOG.md:2368 msgid "coturn can now use host-networking" msgstr "" -#: ../../../CHANGELOG.md:2339 +#: ../../../CHANGELOG.md:2370 msgid "Large coturn deployments (with a huge range of ports specified via `coturn_turn_udp_min_port` and `coturn_turn_udp_max_port`) experience a huge slowdown with how Docker publishes all these ports (setting up firewall forwarding rules), which leads to a very slow coturn service startup and shutdown." msgstr "" -#: ../../../CHANGELOG.md:2341 +#: ../../../CHANGELOG.md:2372 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:2347 +#: ../../../CHANGELOG.md:2378 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:2349 +#: ../../../CHANGELOG.md:2380 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:2351 +#: ../../../CHANGELOG.md:2382 msgid "(Backward Compatibility) Tightening coturn security can lead to connectivity issues" msgstr "" -#: ../../../CHANGELOG.md:2353 +#: ../../../CHANGELOG.md:2384 msgid "**TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default coturn blocklists. They may need to override `coturn_denied_peer_ips` and remove some IP ranges from it." msgstr "" -#: ../../../CHANGELOG.md:2355 +#: ../../../CHANGELOG.md:2386 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:2357 +#: ../../../CHANGELOG.md:2388 msgid "If you access your Matrix server from a local network and need coturn to relay to private IP addresses, you may observe that relaying is now blocked due to our new default `denied-peer-ip` lists (specified in `coturn_denied_peer_ips`). If you experience such connectivity problems, consider overriding this setting in your `vars.yml` file and removing certain networks from it." msgstr "" -#: ../../../CHANGELOG.md:2359 +#: ../../../CHANGELOG.md:2390 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:2362 +#: ../../../CHANGELOG.md:2393 msgid "2023-01-21" msgstr "" -#: ../../../CHANGELOG.md:2364 +#: ../../../CHANGELOG.md:2395 msgid "The matrix-prometheus-node-exporter role lives independently now" msgstr "" -#: ../../../CHANGELOG.md:2366 +#: ../../../CHANGELOG.md:2397 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:2368 +#: ../../../CHANGELOG.md:2399 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:2370 +#: ../../../CHANGELOG.md:2401 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:2372 +#: ../../../CHANGELOG.md:2403 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:2377 +#: ../../../CHANGELOG.md:2408 msgid "2023-01-13" msgstr "" -#: ../../../CHANGELOG.md:2379 +#: ../../../CHANGELOG.md:2410 msgid "Support for running commands via just" msgstr "" -#: ../../../CHANGELOG.md:2381 +#: ../../../CHANGELOG.md:2412 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:2383 +#: ../../../CHANGELOG.md:2414 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:2385 +#: ../../../CHANGELOG.md:2416 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:2387 +#: ../../../CHANGELOG.md:2418 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:2388 +#: ../../../CHANGELOG.md:2419 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:2389 +#: ../../../CHANGELOG.md:2420 msgid "`just run-tags install-mautrix-slack,start` — to run specific playbook tags" msgstr "" -#: ../../../CHANGELOG.md:2390 +#: ../../../CHANGELOG.md:2421 msgid "`just start-all` — (re-)starts all services" msgstr "" -#: ../../../CHANGELOG.md:2391 +#: ../../../CHANGELOG.md:2422 msgid "`just stop-group postgres` — to stop only the Postgres service" msgstr "" -#: ../../../CHANGELOG.md:2392 +#: ../../../CHANGELOG.md:2423 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:2394 +#: ../../../CHANGELOG.md:2425 msgid "Additional helpful commands and shortcuts may be defined in the future." msgstr "" -#: ../../../CHANGELOG.md:2396 +#: ../../../CHANGELOG.md:2427 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:2399 +#: ../../../CHANGELOG.md:2430 msgid "2023-01-11" msgstr "" -#: ../../../CHANGELOG.md:2401 +#: ../../../CHANGELOG.md:2432 msgid "mautrix-slack support" msgstr "" -#: ../../../CHANGELOG.md:2403 +#: ../../../CHANGELOG.md:2434 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:2405 +#: ../../../CHANGELOG.md:2436 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:2408 +#: ../../../CHANGELOG.md:2439 msgid "2023-01-10" msgstr "" -#: ../../../CHANGELOG.md:2410 +#: ../../../CHANGELOG.md:2441 msgid "ChatGPT support" msgstr "" -#: ../../../CHANGELOG.md:2412 +#: ../../../CHANGELOG.md:2443 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:2414 +#: ../../../CHANGELOG.md:2445 msgid "See our [Setting up matrix-bot-chatgpt](docs/configuring-playbook-bot-chatgpt.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:2417 +#: ../../../CHANGELOG.md:2448 msgid "2022-11-30" msgstr "" -#: ../../../CHANGELOG.md:2419 +#: ../../../CHANGELOG.md:2450 msgid "matrix-postgres-backup has been replaced by the ansible-role-postgres-backup external role" msgstr "" -#: ../../../CHANGELOG.md:2421 +#: ../../../CHANGELOG.md:2452 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:2423 +#: ../../../CHANGELOG.md:2454 msgid "You'll need to rename your `matrix_postgres_backup`-prefixed variables such that they use a `postgres_backup` prefix." msgstr "" -#: ../../../CHANGELOG.md:2426 +#: ../../../CHANGELOG.md:2457 msgid "2022-11-28" msgstr "" -#: ../../../CHANGELOG.md:2428 +#: ../../../CHANGELOG.md:2459 msgid "matrix-postgres has been replaced by the ansible-role-postgres external role" msgstr "" -#: ../../../CHANGELOG.md:2430 +#: ../../../CHANGELOG.md:2461 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:2432 +#: ../../../CHANGELOG.md:2463 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:2434 +#: ../../../CHANGELOG.md:2465 msgid "The new role is an upgraded version of the old `matrix-postgres` role with these notable differences:" msgstr "" -#: ../../../CHANGELOG.md:2436 +#: ../../../CHANGELOG.md:2467 msgid "it uses different names for its variables (`matrix_postgres` -> `devture_postgres`)" msgstr "" -#: ../../../CHANGELOG.md:2437 +#: ../../../CHANGELOG.md:2468 msgid "when [Vacuuming PostgreSQL](docs/maintenance-postgres.md#vacuuming-postgresql), it will vacuum all your databases, not just the Synapse one" msgstr "" -#: ../../../CHANGELOG.md:2439 +#: ../../../CHANGELOG.md:2470 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:2441 +#: ../../../CHANGELOG.md:2472 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:2443 +#: ../../../CHANGELOG.md:2474 msgid "The playbook no longer installs scripts to /usr/local/bin" msgstr "" -#: ../../../CHANGELOG.md:2445 +#: ../../../CHANGELOG.md:2476 msgid "The locations of various scripts installed by the playbook have changed." msgstr "" -#: ../../../CHANGELOG.md:2447 +#: ../../../CHANGELOG.md:2478 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:2449 +#: ../../../CHANGELOG.md:2480 msgid "`/usr/local/bin/matrix-remove-all` -> `/matrix/bin/remove-all`" msgstr "" -#: ../../../CHANGELOG.md:2450 +#: ../../../CHANGELOG.md:2481 msgid "`/usr/local/bin/matrix-postgres-cli` -> `/matrix/postgres/bin/cli`" msgstr "" -#: ../../../CHANGELOG.md:2451 +#: ../../../CHANGELOG.md:2482 msgid "`/usr/local/bin/matrix-ssl-lets-encrypt-certificates-renew` -> `/matrix/ssl/bin/lets-encrypt-certificates-renew`" msgstr "" -#: ../../../CHANGELOG.md:2452 +#: ../../../CHANGELOG.md:2483 msgid "`/usr/local/bin/matrix-synapse-register-user` -> `/matrix/synapse/bin/register-user`" msgstr "" -#: ../../../CHANGELOG.md:2455 +#: ../../../CHANGELOG.md:2486 msgid "2022-11-25" msgstr "" -#: ../../../CHANGELOG.md:2457 +#: ../../../CHANGELOG.md:2488 msgid "2x-5x performance improvements in playbook runtime" msgstr "" -#: ../../../CHANGELOG.md:2459 +#: ../../../CHANGELOG.md:2490 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:2461 +#: ../../../CHANGELOG.md:2492 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:2463 +#: ../../../CHANGELOG.md:2494 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:2465 +#: ../../../CHANGELOG.md:2496 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:2467 +#: ../../../CHANGELOG.md:2498 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:2469 +#: ../../../CHANGELOG.md:2500 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:2471 +#: ../../../CHANGELOG.md:2502 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:2473 +#: ../../../CHANGELOG.md:2504 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:2476 +#: ../../../CHANGELOG.md:2507 msgid "2022-11-22" msgstr "" -#: ../../../CHANGELOG.md:2478 +#: ../../../CHANGELOG.md:2509 msgid "Automatic `matrix_architecture` determination" msgstr "" -#: ../../../CHANGELOG.md:2480 +#: ../../../CHANGELOG.md:2511 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:2482 +#: ../../../CHANGELOG.md:2513 msgid "Docker and the Docker SDK for Python are now installed via external roles" msgstr "" -#: ../../../CHANGELOG.md:2486 +#: ../../../CHANGELOG.md:2517 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:2488 +#: ../../../CHANGELOG.md:2519 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:2490 +#: ../../../CHANGELOG.md:2521 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:2492 +#: ../../../CHANGELOG.md:2523 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:2495 +#: ../../../CHANGELOG.md:2526 msgid "2022-11-20" msgstr "" -#: ../../../CHANGELOG.md:2497 +#: ../../../CHANGELOG.md:2528 msgid "(Backward Compatibility Break) Changing how reverse-proxying to Synapse works — now via a `matrix-synapse-reverse-proxy-companion` service" msgstr "" -#: ../../../CHANGELOG.md:2499 +#: ../../../CHANGELOG.md:2530 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:2501 +#: ../../../CHANGELOG.md:2532 msgid "Background" msgstr "" -#: ../../../CHANGELOG.md:2503 +#: ../../../CHANGELOG.md:2534 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:2505 +#: ../../../CHANGELOG.md:2536 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:2507 +#: ../../../CHANGELOG.md:2538 msgid "Solution" msgstr "" -#: ../../../CHANGELOG.md:2509 +#: ../../../CHANGELOG.md:2540 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:2511 +#: ../../../CHANGELOG.md:2542 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:2513 +#: ../../../CHANGELOG.md:2544 msgid "provide a unified container address for reaching Synapse (no matter if workers are enabled or not)" msgstr "" -#: ../../../CHANGELOG.md:2514 +#: ../../../CHANGELOG.md:2545 msgid "`matrix-synapse-reverse-proxy-companion:8008` for Synapse Client-Server API traffic" msgstr "" -#: ../../../CHANGELOG.md:2515 +#: ../../../CHANGELOG.md:2546 msgid "`matrix-synapse-reverse-proxy-companion:8048` for Synapse Server-Server (Federation) API traffic" msgstr "" -#: ../../../CHANGELOG.md:2517 +#: ../../../CHANGELOG.md:2548 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:2519 +#: ../../../CHANGELOG.md:2550 msgid "allow reverse-proxying to Synapse, even if `matrix-nginx-proxy` is disabled" msgstr "" -#: ../../../CHANGELOG.md:2521 +#: ../../../CHANGELOG.md:2552 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:2523 +#: ../../../CHANGELOG.md:2554 msgid "(`matrix-nginx-proxy` -> `matrix-synapse-reverse-proxy-companion` -> (`matrix-synapse` or some Synapse worker))." msgstr "" -#: ../../../CHANGELOG.md:2525 +#: ../../../CHANGELOG.md:2556 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:2527 +#: ../../../CHANGELOG.md:2558 msgid "Webserver configuration" msgstr "" -#: ../../../CHANGELOG.md:2529 +#: ../../../CHANGELOG.md:2560 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:2531 +#: ../../../CHANGELOG.md:2562 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:2533 +#: ../../../CHANGELOG.md:2564 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:2535 +#: ../../../CHANGELOG.md:2566 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:2537 +#: ../../../CHANGELOG.md:2568 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:2540 +#: ../../../CHANGELOG.md:2571 msgid "2022-11-05" msgstr "" -#: ../../../CHANGELOG.md:2542 +#: ../../../CHANGELOG.md:2573 msgid "(Backward Compatibility Break) A new default standalone mode for Etherpad" msgstr "" -#: ../../../CHANGELOG.md:2544 +#: ../../../CHANGELOG.md:2575 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:2546 +#: ../../../CHANGELOG.md:2577 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:2548 +#: ../../../CHANGELOG.md:2579 msgid "If you've already got both Etherpad and Dimension in use you could:" msgstr "" -#: ../../../CHANGELOG.md:2550 +#: ../../../CHANGELOG.md:2581 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:2552 +#: ../../../CHANGELOG.md:2583 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:2555 +#: ../../../CHANGELOG.md:2586 msgid "2022-11-04" msgstr "" -#: ../../../CHANGELOG.md:2557 +#: ../../../CHANGELOG.md:2588 msgid "The playbook now uses external roles for some things" msgstr "" -#: ../../../CHANGELOG.md:2559 +#: ../../../CHANGELOG.md:2590 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:2561 +#: ../../../CHANGELOG.md:2592 msgid "We're in the process of trimming the playbook and making it reuse Ansible roles." msgstr "" -#: ../../../CHANGELOG.md:2563 +#: ../../../CHANGELOG.md:2594 msgid "Starting now, the playbook is composed of 2 types of Ansible roles:" msgstr "" -#: ../../../CHANGELOG.md:2565 +#: ../../../CHANGELOG.md:2596 msgid "those that live within the playbook itself (`roles/custom/*`)" msgstr "" -#: ../../../CHANGELOG.md:2567 +#: ../../../CHANGELOG.md:2598 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:2569 +#: ../../../CHANGELOG.md:2600 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:2571 +#: ../../../CHANGELOG.md:2602 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:2573 +#: ../../../CHANGELOG.md:2604 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:2576 +#: ../../../CHANGELOG.md:2607 msgid "2022-10-14" msgstr "" -#: ../../../CHANGELOG.md:2578 +#: ../../../CHANGELOG.md:2609 msgid "synapse-s3-storage-provider support" msgstr "" -#: ../../../CHANGELOG.md:2580 +#: ../../../CHANGELOG.md:2611 msgid "**`synapse-s3-storage-provider` support is very new and still relatively untested. Using it may cause data loss.**" msgstr "" -#: ../../../CHANGELOG.md:2582 +#: ../../../CHANGELOG.md:2613 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:2584 +#: ../../../CHANGELOG.md:2615 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:2586 +#: ../../../CHANGELOG.md:2617 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:2588 +#: ../../../CHANGELOG.md:2619 msgid "Synapse container image customization support" msgstr "" -#: ../../../CHANGELOG.md:2590 +#: ../../../CHANGELOG.md:2621 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:2592 +#: ../../../CHANGELOG.md:2623 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:2594 +#: ../../../CHANGELOG.md:2625 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:2605 +#: ../../../CHANGELOG.md:2636 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:2607 +#: ../../../CHANGELOG.md:2638 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:2610 +#: ../../../CHANGELOG.md:2641 msgid "2022-10-02" msgstr "" -#: ../../../CHANGELOG.md:2612 +#: ../../../CHANGELOG.md:2643 msgid "matrix-ldap-registration-proxy support" msgstr "" -#: ../../../CHANGELOG.md:2614 +#: ../../../CHANGELOG.md:2645 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:2616 +#: ../../../CHANGELOG.md:2647 msgid "See our [Setting up matrix-ldap-registration-proxy](docs/configuring-playbook-matrix-ldap-registration-proxy.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:2619 +#: ../../../CHANGELOG.md:2650 msgid "2022-09-15" msgstr "" -#: ../../../CHANGELOG.md:2621 +#: ../../../CHANGELOG.md:2652 msgid "(Potential Backward Compatibility Break) Major improvements to Synapse workers" msgstr "" -#: ../../../CHANGELOG.md:2623 +#: ../../../CHANGELOG.md:2654 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:2625 +#: ../../../CHANGELOG.md:2656 msgid "we've added support for [Stream writers](#stream-writers-support)" msgstr "" -#: ../../../CHANGELOG.md:2626 +#: ../../../CHANGELOG.md:2657 msgid "we've added support for [multiple federation sender workers](#multiple-federation-sender-workers-support)" msgstr "" -#: ../../../CHANGELOG.md:2627 +#: ../../../CHANGELOG.md:2658 msgid "we've added support for [multiple pusher workers](#multiple-pusher-workers-support)" msgstr "" -#: ../../../CHANGELOG.md:2628 +#: ../../../CHANGELOG.md:2659 msgid "we've added support for [running background tasks on a worker](#background-tasks-can-run-on-a-worker)" msgstr "" -#: ../../../CHANGELOG.md:2629 +#: ../../../CHANGELOG.md:2660 msgid "we've restored support for [`appservice` workers](#appservice-worker-support-is-back)" msgstr "" -#: ../../../CHANGELOG.md:2630 +#: ../../../CHANGELOG.md:2661 msgid "we've restored support for [`user_dir` workers](#user-directory-worker-support-is-back)" msgstr "" -#: ../../../CHANGELOG.md:2631 +#: ../../../CHANGELOG.md:2662 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:2632 +#: ../../../CHANGELOG.md:2663 msgid "see the [Potential Backward Incompatibilities after these Synapse worker changes](#potential-backward-incompatibilities-after-these-synapse-worker-changes)" msgstr "" -#: ../../../CHANGELOG.md:2634 +#: ../../../CHANGELOG.md:2665 msgid "Stream writers support" msgstr "" -#: ../../../CHANGELOG.md:2636 +#: ../../../CHANGELOG.md:2667 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:2638 +#: ../../../CHANGELOG.md:2669 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:2640 +#: ../../../CHANGELOG.md:2671 msgid "If you'd like to customize the number of workers we also make that possible using these variables:" msgstr "" -#: ../../../CHANGELOG.md:2653 +#: ../../../CHANGELOG.md:2684 msgid "Multiple federation sender workers support" msgstr "" -#: ../../../CHANGELOG.md:2655 +#: ../../../CHANGELOG.md:2686 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:2657 +#: ../../../CHANGELOG.md:2688 msgid "Multiple pusher workers support" msgstr "" -#: ../../../CHANGELOG.md:2659 +#: ../../../CHANGELOG.md:2690 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:2661 +#: ../../../CHANGELOG.md:2692 msgid "Background tasks can run on a worker" msgstr "" -#: ../../../CHANGELOG.md:2663 +#: ../../../CHANGELOG.md:2694 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:2665 +#: ../../../CHANGELOG.md:2696 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:2667 +#: ../../../CHANGELOG.md:2698 msgid "Appservice worker support is back" msgstr "" -#: ../../../CHANGELOG.md:2669 +#: ../../../CHANGELOG.md:2700 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:2671 +#: ../../../CHANGELOG.md:2702 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:2673 +#: ../../../CHANGELOG.md:2704 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:2675 +#: ../../../CHANGELOG.md:2706 msgid "User Directory worker support is back" msgstr "" -#: ../../../CHANGELOG.md:2677 +#: ../../../CHANGELOG.md:2708 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:2679 +#: ../../../CHANGELOG.md:2710 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:2681 +#: ../../../CHANGELOG.md:2712 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:2683 +#: ../../../CHANGELOG.md:2714 msgid "Using more than 1 media repository worker is now more reliable" msgstr "" -#: ../../../CHANGELOG.md:2685 +#: ../../../CHANGELOG.md:2716 msgid "With `matrix_synapse_workers_preset: one-of-each`, we only launch one `media_repository` worker." msgstr "" -#: ../../../CHANGELOG.md:2687 +#: ../../../CHANGELOG.md:2718 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:2689 +#: ../../../CHANGELOG.md:2720 msgid "Potential Backward Incompatibilities after these Synapse worker changes" msgstr "" -#: ../../../CHANGELOG.md:2691 +#: ../../../CHANGELOG.md:2722 msgid "Below we'll discuss **potential backward incompatibilities**." msgstr "" -#: ../../../CHANGELOG.md:2693 +#: ../../../CHANGELOG.md:2724 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:2695 +#: ../../../CHANGELOG.md:2726 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:2697 +#: ../../../CHANGELOG.md:2728 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:2699 +#: ../../../CHANGELOG.md:2730 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:2702 +#: ../../../CHANGELOG.md:2733 msgid "2022-09-09" msgstr "" -#: ../../../CHANGELOG.md:2704 +#: ../../../CHANGELOG.md:2735 msgid "Cactus Comments support" msgstr "" -#: ../../../CHANGELOG.md:2706 +#: ../../../CHANGELOG.md:2737 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:2708 +#: ../../../CHANGELOG.md:2739 msgid "See our [Setting up Cactus Comments](docs/configuring-playbook-cactus-comments.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:2711 +#: ../../../CHANGELOG.md:2742 msgid "2022-08-23" msgstr "" -#: ../../../CHANGELOG.md:2713 +#: ../../../CHANGELOG.md:2744 msgid "Postmoogle email bridge support" msgstr "" -#: ../../../CHANGELOG.md:2715 +#: ../../../CHANGELOG.md:2746 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:2717 +#: ../../../CHANGELOG.md:2748 msgid "See our [Setting up Postmoogle email bridging](docs/configuring-playbook-bridge-postmoogle.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:2720 +#: ../../../CHANGELOG.md:2751 msgid "2022-08-10" msgstr "" -#: ../../../CHANGELOG.md:2722 +#: ../../../CHANGELOG.md:2753 msgid "mautrix-whatsapp default configuration changes" msgstr "" -#: ../../../CHANGELOG.md:2724 +#: ../../../CHANGELOG.md:2755 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:2726 +#: ../../../CHANGELOG.md:2757 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:2728 +#: ../../../CHANGELOG.md:2759 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:2731 +#: ../../../CHANGELOG.md:2762 msgid "2022-08-09" msgstr "" -#: ../../../CHANGELOG.md:2733 +#: ../../../CHANGELOG.md:2764 msgid "Conduit support" msgstr "" -#: ../../../CHANGELOG.md:2735 +#: ../../../CHANGELOG.md:2766 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:2737 +#: ../../../CHANGELOG.md:2768 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:2739 +#: ../../../CHANGELOG.md:2770 msgid "To try out Conduit, we recommend that you **use a new server** and the following `vars.yml` configuration:" msgstr "" -#: ../../../CHANGELOG.md:2745 +#: ../../../CHANGELOG.md:2776 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:2748 +#: ../../../CHANGELOG.md:2779 msgid "2022-07-29" msgstr "" -#: ../../../CHANGELOG.md:2750 +#: ../../../CHANGELOG.md:2781 msgid "mautrix-discord support" msgstr "" -#: ../../../CHANGELOG.md:2752 +#: ../../../CHANGELOG.md:2783 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:2754 +#: ../../../CHANGELOG.md:2785 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:2757 +#: ../../../CHANGELOG.md:2788 msgid "2022-07-27" msgstr "" -#: ../../../CHANGELOG.md:2759 +#: ../../../CHANGELOG.md:2790 msgid "matrix-appservice-kakaotalk support" msgstr "" -#: ../../../CHANGELOG.md:2761 +#: ../../../CHANGELOG.md:2792 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:2763 +#: ../../../CHANGELOG.md:2794 msgid "See our [Setting up Appservice Kakaotalk bridging](docs/configuring-playbook-bridge-appservice-kakaotalk.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:2766 +#: ../../../CHANGELOG.md:2797 msgid "2022-07-20" msgstr "" -#: ../../../CHANGELOG.md:2768 +#: ../../../CHANGELOG.md:2799 msgid "maubot support" msgstr "" -#: ../../../CHANGELOG.md:2770 +#: ../../../CHANGELOG.md:2801 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:2772 +#: ../../../CHANGELOG.md:2803 msgid "See our [Setting up maubot](docs/configuring-playbook-bot-maubot.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:2775 +#: ../../../CHANGELOG.md:2806 msgid "2022-07-14" msgstr "" -#: ../../../CHANGELOG.md:2777 +#: ../../../CHANGELOG.md:2808 msgid "mx-puppet-skype removal" msgstr "" -#: ../../../CHANGELOG.md:2779 +#: ../../../CHANGELOG.md:2810 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:2781 +#: ../../../CHANGELOG.md:2812 msgid "To completely clean up your server from `mx-puppet-skype`'s presence on it:" msgstr "" -#: ../../../CHANGELOG.md:2783 +#: ../../../CHANGELOG.md:2814 msgid "ensure your Ansible configuration (`vars.yml` file) no longer contains `matrix_mx_puppet_skype_*` references" msgstr "" -#: ../../../CHANGELOG.md:2784 +#: ../../../CHANGELOG.md:2815 msgid "stop and disable the systemd service (run `systemctl disable --now matrix-mx-puppet-skype` on the server)" msgstr "" -#: ../../../CHANGELOG.md:2785 +#: ../../../CHANGELOG.md:2816 msgid "delete the systemd service (run `rm /etc/systemd/system/matrix-mx-puppet-skype.service` on the server)" msgstr "" -#: ../../../CHANGELOG.md:2786 +#: ../../../CHANGELOG.md:2817 msgid "delete `/matrix/mx-puppet-skype` (run `rm -rf /matrix/mx-puppet-skype` on the server)" msgstr "" -#: ../../../CHANGELOG.md:2787 +#: ../../../CHANGELOG.md:2818 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:2789 +#: ../../../CHANGELOG.md:2820 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:2791 +#: ../../../CHANGELOG.md:2822 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:2793 +#: ../../../CHANGELOG.md:2824 msgid "signald (0.19.0+) upgrade requires data migration" msgstr "" -#: ../../../CHANGELOG.md:2795 +#: ../../../CHANGELOG.md:2826 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:2797 +#: ../../../CHANGELOG.md:2828 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:2799 +#: ../../../CHANGELOG.md:2830 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:2801 +#: ../../../CHANGELOG.md:2832 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:2803 +#: ../../../CHANGELOG.md:2834 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:2806 +#: ../../../CHANGELOG.md:2837 msgid "2022-07-05" msgstr "" -#: ../../../CHANGELOG.md:2808 +#: ../../../CHANGELOG.md:2839 msgid "Ntfy push notifications support" msgstr "" -#: ../../../CHANGELOG.md:2810 +#: ../../../CHANGELOG.md:2841 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:2812 +#: ../../../CHANGELOG.md:2843 msgid "See our [Setting up the ntfy push notifications server](docs/configuring-playbook-ntfy.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:2815 +#: ../../../CHANGELOG.md:2846 msgid "2022-06-23" msgstr "" -#: ../../../CHANGELOG.md:2817 +#: ../../../CHANGELOG.md:2848 msgid "(Potential Backward Compatibility Break) Changes around metrics collection" msgstr "" -#: ../../../CHANGELOG.md:2819 +#: ../../../CHANGELOG.md:2850 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:2821 +#: ../../../CHANGELOG.md:2852 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:2823 +#: ../../../CHANGELOG.md:2854 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:2825 +#: ../../../CHANGELOG.md:2856 msgid "**If you are using the [Hookshot bridge](docs/configuring-playbook-bridge-hookshot.md)**, you may find that:" msgstr "" -#: ../../../CHANGELOG.md:2826 +#: ../../../CHANGELOG.md:2857 msgid "**Metrics may not be enabled by default anymore**:" msgstr "" -#: ../../../CHANGELOG.md:2827 +#: ../../../CHANGELOG.md:2858 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:2828 +#: ../../../CHANGELOG.md:2859 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:2829 +#: ../../../CHANGELOG.md:2860 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:2830 +#: ../../../CHANGELOG.md:2861 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:2832 +#: ../../../CHANGELOG.md:2863 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:2834 +#: ../../../CHANGELOG.md:2865 msgid "**If you're using [postgres-exporter](docs/configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-postgres-optional)** (`prometheus_postgres_exporter_enabled: true`) and would like to collect its metrics from an external Prometheus server, see `matrix_prometheus_services_proxy_connect_prometheus_postgres_exporter_metrics_proxying_enabled` described in our [Collecting metrics to an external Prometheus server](docs/configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) documentation. You will be able to collect its metrics from `https://matrix.example.com/metrics/postgres-exporter`." msgstr "" -#: ../../../CHANGELOG.md:2836 +#: ../../../CHANGELOG.md:2867 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:2838 +#: ../../../CHANGELOG.md:2869 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:2839 +#: ../../../CHANGELOG.md:2870 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:2840 +#: ../../../CHANGELOG.md:2871 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:2841 +#: ../../../CHANGELOG.md:2872 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:2843 +#: ../../../CHANGELOG.md:2874 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:2845 +#: ../../../CHANGELOG.md:2876 msgid "2022-06-13" msgstr "" -#: ../../../CHANGELOG.md:2847 +#: ../../../CHANGELOG.md:2878 msgid "go-skype-bridge bridging support" msgstr "" -#: ../../../CHANGELOG.md:2849 +#: ../../../CHANGELOG.md:2880 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:2851 +#: ../../../CHANGELOG.md:2882 msgid "See our [Setting up Go Skype Bridge bridging](docs/configuring-playbook-bridge-go-skype-bridge.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:2853 +#: ../../../CHANGELOG.md:2884 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:2856 +#: ../../../CHANGELOG.md:2887 msgid "2022-06-09" msgstr "" -#: ../../../CHANGELOG.md:2858 +#: ../../../CHANGELOG.md:2889 msgid "Running Ansible in a container can now happen on the Matrix server itself" msgstr "" -#: ../../../CHANGELOG.md:2860 +#: ../../../CHANGELOG.md:2891 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:2863 +#: ../../../CHANGELOG.md:2894 msgid "2022-05-31" msgstr "" -#: ../../../CHANGELOG.md:2865 +#: ../../../CHANGELOG.md:2896 msgid "Synapse v1.60 upgrade may cause trouble and require manual intervention" msgstr "" -#: ../../../CHANGELOG.md:2867 +#: ../../../CHANGELOG.md:2898 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:2869 +#: ../../../CHANGELOG.md:2900 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:2871 +#: ../../../CHANGELOG.md:2902 msgid "**If Synapse fails to start** after your next playbook run, you'll need to:" msgstr "" -#: ../../../CHANGELOG.md:2873 +#: ../../../CHANGELOG.md:2904 msgid "SSH into the Matrix server" msgstr "" -#: ../../../CHANGELOG.md:2874 +#: ../../../CHANGELOG.md:2905 msgid "launch `/usr/local/bin/matrix-postgres-cli`" msgstr "" -#: ../../../CHANGELOG.md:2875 +#: ../../../CHANGELOG.md:2906 msgid "switch to the `synapse` database: `\\c synapse`" msgstr "" -#: ../../../CHANGELOG.md:2876 +#: ../../../CHANGELOG.md:2907 msgid "run the following SQL query:" msgstr "" -#: ../../../CHANGELOG.md:2895 +#: ../../../CHANGELOG.md:2926 msgid "You could then restart services: `ansible-playbook -i inventory/hosts setup.yml --tags=start`" msgstr "" -#: ../../../CHANGELOG.md:2898 +#: ../../../CHANGELOG.md:2929 msgid "2022-04-25" msgstr "" -#: ../../../CHANGELOG.md:2900 +#: ../../../CHANGELOG.md:2931 msgid "Buscarron bot support" msgstr "" -#: ../../../CHANGELOG.md:2902 +#: ../../../CHANGELOG.md:2933 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:2904 +#: ../../../CHANGELOG.md:2935 msgid "See our [Setting up Buscarron](docs/configuring-playbook-bot-buscarron.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:2907 +#: ../../../CHANGELOG.md:2938 msgid "2022-04-21" msgstr "" -#: ../../../CHANGELOG.md:2909 +#: ../../../CHANGELOG.md:2940 msgid "matrix-registration-bot support" msgstr "" -#: ../../../CHANGELOG.md:2911 +#: ../../../CHANGELOG.md:2942 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:2913 +#: ../../../CHANGELOG.md:2944 msgid "See our [Setting up matrix-registration-bot](docs/configuring-playbook-bot-matrix-registration-bot.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:2916 +#: ../../../CHANGELOG.md:2947 msgid "2022-04-19" msgstr "" -#: ../../../CHANGELOG.md:2918 +#: ../../../CHANGELOG.md:2949 msgid "BorgBackup support" msgstr "" -#: ../../../CHANGELOG.md:2920 +#: ../../../CHANGELOG.md:2951 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:2922 +#: ../../../CHANGELOG.md:2953 msgid "See our [Setting up BorgBackup](docs/configuring-playbook-backup-borg.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:2924 +#: ../../../CHANGELOG.md:2955 msgid "(Compatibility Break) Upgrading to Synapse v1.57 on setups using workers may require manual action" msgstr "" -#: ../../../CHANGELOG.md:2926 +#: ../../../CHANGELOG.md:2957 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:2928 +#: ../../../CHANGELOG.md:2959 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:2930 +#: ../../../CHANGELOG.md:2961 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:2932 +#: ../../../CHANGELOG.md:2963 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:2934 +#: ../../../CHANGELOG.md:2965 msgid "Pull the latest playbook changes" msgstr "" -#: ../../../CHANGELOG.md:2935 +#: ../../../CHANGELOG.md:2966 msgid "Stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)" msgstr "" -#: ../../../CHANGELOG.md:2936 +#: ../../../CHANGELOG.md:2967 msgid "Re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all`)" msgstr "" -#: ../../../CHANGELOG.md:2937 +#: ../../../CHANGELOG.md:2968 msgid "Start Postgres (`systemctl start matrix-postgres` on the server)" msgstr "" -#: ../../../CHANGELOG.md:2938 +#: ../../../CHANGELOG.md:2969 msgid "Start the main Synapse process (`systemctl start matrix-synapse` on the server)" msgstr "" -#: ../../../CHANGELOG.md:2939 +#: ../../../CHANGELOG.md:2970 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:2940 +#: ../../../CHANGELOG.md:2971 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:2943 +#: ../../../CHANGELOG.md:2974 msgid "2022-04-14" msgstr "" -#: ../../../CHANGELOG.md:2945 +#: ../../../CHANGELOG.md:2976 msgid "(Compatibility Break) Changes to `docker-src` permissions necessitating manual action" msgstr "" -#: ../../../CHANGELOG.md:2947 +#: ../../../CHANGELOG.md:2978 msgid "Users who build container images from source will need to manually correct file permissions of some directories on the server." msgstr "" -#: ../../../CHANGELOG.md:2949 +#: ../../../CHANGELOG.md:2980 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:2951 +#: ../../../CHANGELOG.md:2982 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:2953 +#: ../../../CHANGELOG.md:2984 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:2956 +#: ../../../CHANGELOG.md:2987 msgid "2022-03-17" msgstr "" -#: ../../../CHANGELOG.md:2958 +#: ../../../CHANGELOG.md:2989 msgid "(Compatibility Break) ma1sd identity server no longer installed by default" msgstr "" -#: ../../../CHANGELOG.md:2960 +#: ../../../CHANGELOG.md:2991 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:2962 +#: ../../../CHANGELOG.md:2993 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:2964 +#: ../../../CHANGELOG.md:2995 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:2966 +#: ../../../CHANGELOG.md:2997 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:2973 +#: ../../../CHANGELOG.md:3004 msgid "2022-02-12" msgstr "" -#: ../../../CHANGELOG.md:2975 +#: ../../../CHANGELOG.md:3006 msgid "matrix_encryption_disabler support" msgstr "" -#: ../../../CHANGELOG.md:2977 +#: ../../../CHANGELOG.md:3008 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:2979 +#: ../../../CHANGELOG.md:3010 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:2982 +#: ../../../CHANGELOG.md:3013 msgid "2022-02-01" msgstr "" -#: ../../../CHANGELOG.md:2984 +#: ../../../CHANGELOG.md:3015 msgid "matrix-hookshot bridging support" msgstr "" -#: ../../../CHANGELOG.md:2986 +#: ../../../CHANGELOG.md:3017 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:2989 +#: ../../../CHANGELOG.md:3020 msgid "2022-01-31" msgstr "" -#: ../../../CHANGELOG.md:2991 +#: ../../../CHANGELOG.md:3022 msgid "ARM support for matrix-corporal" msgstr "" -#: ../../../CHANGELOG.md:2993 +#: ../../../CHANGELOG.md:3024 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:2996 +#: ../../../CHANGELOG.md:3027 msgid "2022-01-07" msgstr "" -#: ../../../CHANGELOG.md:2998 +#: ../../../CHANGELOG.md:3029 msgid "Dendrite support" msgstr "" -#: ../../../CHANGELOG.md:3000 +#: ../../../CHANGELOG.md:3031 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:3002 +#: ../../../CHANGELOG.md:3033 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:3004 +#: ../../../CHANGELOG.md:3035 msgid "We believe that 2022 will be the year of the non-Synapse Matrix server!" msgstr "" -#: ../../../CHANGELOG.md:3006 +#: ../../../CHANGELOG.md:3037 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:3008 +#: ../../../CHANGELOG.md:3039 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:3010 +#: ../../../CHANGELOG.md:3041 msgid "Adapting the configuration for existing Synapse installations" msgstr "" -#: ../../../CHANGELOG.md:3012 +#: ../../../CHANGELOG.md:3043 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:3014 +#: ../../../CHANGELOG.md:3045 msgid "The `vars.yml` file for **existing installations will need to be updated** by adding this **additional configuration**:" msgstr "" -#: ../../../CHANGELOG.md:3026 +#: ../../../CHANGELOG.md:3057 msgid "Trying out Dendrite" msgstr "" -#: ../../../CHANGELOG.md:3028 +#: ../../../CHANGELOG.md:3059 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:3034 +#: ../../../CHANGELOG.md:3065 msgid "**The homeserver implementation of an existing server cannot be changed** (e.g. from Synapse to Dendrite) without data loss." msgstr "" -#: ../../../CHANGELOG.md:3036 +#: ../../../CHANGELOG.md:3067 msgid "We're excited to gain support for other homeserver implementations, like [Conduit](https://conduit.rs/), etc!" msgstr "" -#: ../../../CHANGELOG.md:3038 +#: ../../../CHANGELOG.md:3069 msgid "Honoroit bot support" msgstr "" -#: ../../../CHANGELOG.md:3040 +#: ../../../CHANGELOG.md:3071 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:3042 +#: ../../../CHANGELOG.md:3073 msgid "See our [Setting up Honoroit](docs/configuring-playbook-bot-honoroit.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:3045 +#: ../../../CHANGELOG.md:3076 msgid "2022-01-06" msgstr "" -#: ../../../CHANGELOG.md:3047 +#: ../../../CHANGELOG.md:3078 msgid "Cinny support" msgstr "" -#: ../../../CHANGELOG.md:3049 +#: ../../../CHANGELOG.md:3080 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:3051 +#: ../../../CHANGELOG.md:3082 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:3053 +#: ../../../CHANGELOG.md:3084 msgid "Additional details are available in [Setting up Cinny](docs/configuring-playbook-client-cinny.md)." msgstr "" -#: ../../../CHANGELOG.md:3056 +#: ../../../CHANGELOG.md:3087 msgid "2021-12-22" msgstr "" -#: ../../../CHANGELOG.md:3058 +#: ../../../CHANGELOG.md:3089 msgid "Twitter bridging support via mautrix-twitter" msgstr "" -#: ../../../CHANGELOG.md:3060 +#: ../../../CHANGELOG.md:3091 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:3063 +#: ../../../CHANGELOG.md:3094 msgid "2021-12-14" msgstr "" -#: ../../../CHANGELOG.md:3065 +#: ../../../CHANGELOG.md:3096 msgid "(Security) Users of the Signal bridge may wish to upgrade it to work around log4j vulnerability" msgstr "" -#: ../../../CHANGELOG.md:3067 +#: ../../../CHANGELOG.md:3098 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:3069 +#: ../../../CHANGELOG.md:3100 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:3072 +#: ../../../CHANGELOG.md:3103 msgid "2021-11-11" msgstr "" -#: ../../../CHANGELOG.md:3074 +#: ../../../CHANGELOG.md:3105 msgid "Dropped support for Postgres v9.6" msgstr "" -#: ../../../CHANGELOG.md:3076 +#: ../../../CHANGELOG.md:3107 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:3078 +#: ../../../CHANGELOG.md:3109 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:3081 +#: ../../../CHANGELOG.md:3112 msgid "2021-10-23" msgstr "" -#: ../../../CHANGELOG.md:3083 +#: ../../../CHANGELOG.md:3114 msgid "Hangouts bridge no longer updated, superseded by a Googlechat bridge" msgstr "" -#: ../../../CHANGELOG.md:3085 +#: ../../../CHANGELOG.md:3116 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:3087 +#: ../../../CHANGELOG.md:3118 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:3090 +#: ../../../CHANGELOG.md:3121 msgid "2021-08-23" msgstr "" -#: ../../../CHANGELOG.md:3092 +#: ../../../CHANGELOG.md:3123 msgid "LinkedIn bridging support via beeper-linkedin" msgstr "" -#: ../../../CHANGELOG.md:3094 +#: ../../../CHANGELOG.md:3125 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:3096 +#: ../../../CHANGELOG.md:3127 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:3098 +#: ../../../CHANGELOG.md:3129 msgid "To get started with bridging to LinkedIn, see [Setting up Beeper LinkedIn bridging](docs/configuring-playbook-bridge-beeper-linkedin.md)." msgstr "" -#: ../../../CHANGELOG.md:3101 +#: ../../../CHANGELOG.md:3132 msgid "2021-08-20" msgstr "" -#: ../../../CHANGELOG.md:3103 +#: ../../../CHANGELOG.md:3134 msgid "Sygnal upgraded — ARM support and no longer requires a database" msgstr "" -#: ../../../CHANGELOG.md:3105 +#: ../../../CHANGELOG.md:3136 msgid "The [Sygnal](docs/configuring-playbook-sygnal.md) push gateway has been upgraded from `v0.9.0` to `v0.10.1`." msgstr "" -#: ../../../CHANGELOG.md:3107 +#: ../../../CHANGELOG.md:3138 msgid "This is an optional component for the playbook, so most of our users wouldn't care about this announcement." msgstr "" -#: ../../../CHANGELOG.md:3109 +#: ../../../CHANGELOG.md:3140 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:3111 +#: ../../../CHANGELOG.md:3142 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:3114 +#: ../../../CHANGELOG.md:3145 msgid "2021-05-21" msgstr "" -#: ../../../CHANGELOG.md:3116 +#: ../../../CHANGELOG.md:3147 msgid "Hydrogen support" msgstr "" -#: ../../../CHANGELOG.md:3118 +#: ../../../CHANGELOG.md:3149 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:3120 +#: ../../../CHANGELOG.md:3151 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:3122 +#: ../../../CHANGELOG.md:3153 msgid "Additional details are available in [Setting up Hydrogen](docs/configuring-playbook-client-hydrogen.md)." msgstr "" -#: ../../../CHANGELOG.md:3125 +#: ../../../CHANGELOG.md:3156 msgid "2021-05-19" msgstr "" -#: ../../../CHANGELOG.md:3127 +#: ../../../CHANGELOG.md:3158 msgid "Heisenbridge support" msgstr "" -#: ../../../CHANGELOG.md:3129 +#: ../../../CHANGELOG.md:3160 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:3131 +#: ../../../CHANGELOG.md:3162 msgid "Additional details are available in [Setting up Heisenbridge bouncer-style IRC bridging](docs/configuring-playbook-bridge-heisenbridge.md)." msgstr "" -#: ../../../CHANGELOG.md:3134 +#: ../../../CHANGELOG.md:3165 msgid "2021-04-16" msgstr "" -#: ../../../CHANGELOG.md:3136 +#: ../../../CHANGELOG.md:3167 msgid "Disabling TLSv1 and TLSv1.1 for coturn" msgstr "" -#: ../../../CHANGELOG.md:3138 +#: ../../../CHANGELOG.md:3169 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:3140 +#: ../../../CHANGELOG.md:3171 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:3148 +#: ../../../CHANGELOG.md:3179 msgid "2021-04-05" msgstr "" -#: ../../../CHANGELOG.md:3150 +#: ../../../CHANGELOG.md:3181 msgid "Automated local Postgres backup support" msgstr "" -#: ../../../CHANGELOG.md:3152 +#: ../../../CHANGELOG.md:3183 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:3154 +#: ../../../CHANGELOG.md:3185 msgid "Additional details are available in [Setting up Postgres backup](docs/configuring-playbook-postgres-backup.md)." msgstr "" -#: ../../../CHANGELOG.md:3157 +#: ../../../CHANGELOG.md:3188 msgid "2021-04-03" msgstr "" -#: ../../../CHANGELOG.md:3159 +#: ../../../CHANGELOG.md:3190 msgid "Mjolnir moderation tool (bot) support" msgstr "" -#: ../../../CHANGELOG.md:3161 +#: ../../../CHANGELOG.md:3192 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:3163 +#: ../../../CHANGELOG.md:3194 msgid "Additional details are available in [Setting up Mjolnir](docs/configuring-playbook-bot-mjolnir.md)." msgstr "" -#: ../../../CHANGELOG.md:3166 +#: ../../../CHANGELOG.md:3197 msgid "2021-03-20" msgstr "" -#: ../../../CHANGELOG.md:3168 +#: ../../../CHANGELOG.md:3199 msgid "Sygnal push gateway support" msgstr "" -#: ../../../CHANGELOG.md:3170 +#: ../../../CHANGELOG.md:3201 msgid "The playbook can now install the [Sygnal](https://github.com/matrix-org/sygnal) push gateway for you." msgstr "" -#: ../../../CHANGELOG.md:3172 +#: ../../../CHANGELOG.md:3203 msgid "This is only useful to people who develop/build their own Matrix client applications." msgstr "" -#: ../../../CHANGELOG.md:3174 +#: ../../../CHANGELOG.md:3205 msgid "Additional details are available in our [Setting up the Sygnal push gateway](docs/configuring-playbook-sygnal.md) docs." msgstr "" -#: ../../../CHANGELOG.md:3177 +#: ../../../CHANGELOG.md:3208 msgid "2021-03-16" msgstr "" -#: ../../../CHANGELOG.md:3179 +#: ../../../CHANGELOG.md:3210 msgid "Go-NEB support" msgstr "" -#: ../../../CHANGELOG.md:3181 +#: ../../../CHANGELOG.md:3212 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:3183 +#: ../../../CHANGELOG.md:3214 msgid "Additional details are available in [Setting up Go-NEB](docs/configuring-playbook-bot-go-neb.md)." msgstr "" -#: ../../../CHANGELOG.md:3186 +#: ../../../CHANGELOG.md:3217 msgid "2021-02-19" msgstr "" -#: ../../../CHANGELOG.md:3188 +#: ../../../CHANGELOG.md:3219 msgid "GroupMe bridging support via mx-puppet-groupme" msgstr "" -#: ../../../CHANGELOG.md:3190 +#: ../../../CHANGELOG.md:3221 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:3192 +#: ../../../CHANGELOG.md:3223 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:3194 +#: ../../../CHANGELOG.md:3225 msgid "To get started, follow our [Setting up MX Puppet GroupMe](docs/configuring-playbook-bridge-mx-puppet-groupme.md) docs." msgstr "" -#: ../../../CHANGELOG.md:3196 +#: ../../../CHANGELOG.md:3227 msgid "Mautrix Instagram bridging support" msgstr "" -#: ../../../CHANGELOG.md:3198 +#: ../../../CHANGELOG.md:3229 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:3200 +#: ../../../CHANGELOG.md:3231 msgid "Additional details are available in [Setting up Mautrix Instagram bridging](docs/configuring-playbook-bridge-mautrix-instagram.md)." msgstr "" -#: ../../../CHANGELOG.md:3202 +#: ../../../CHANGELOG.md:3233 msgid "Synapse workers support" msgstr "" -#: ../../../CHANGELOG.md:3204 +#: ../../../CHANGELOG.md:3235 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:3206 +#: ../../../CHANGELOG.md:3237 msgid "Having support for workers makes the playbook suitable for larger homeserver deployments." msgstr "" -#: ../../../CHANGELOG.md:3208 +#: ../../../CHANGELOG.md:3239 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:3210 +#: ../../../CHANGELOG.md:3241 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:3212 +#: ../../../CHANGELOG.md:3243 msgid "To enable Synapse workers, follow our [Load balancing with workers](docs/configuring-playbook-synapse.md#load-balancing-with-workers) documentation." msgstr "" -#: ../../../CHANGELOG.md:3215 +#: ../../../CHANGELOG.md:3246 msgid "2021-02-12" msgstr "" -#: ../../../CHANGELOG.md:3217 +#: ../../../CHANGELOG.md:3248 msgid "(Potential Breaking Change) Monitoring/metrics support using Prometheus and Grafana" msgstr "" -#: ../../../CHANGELOG.md:3219 +#: ../../../CHANGELOG.md:3250 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:3221 +#: ../../../CHANGELOG.md:3252 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:3223 +#: ../../../CHANGELOG.md:3254 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:3226 +#: ../../../CHANGELOG.md:3257 msgid "2021-01-31" msgstr "" -#: ../../../CHANGELOG.md:3228 +#: ../../../CHANGELOG.md:3259 msgid "Etherpad support" msgstr "" -#: ../../../CHANGELOG.md:3230 +#: ../../../CHANGELOG.md:3261 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:3232 +#: ../../../CHANGELOG.md:3263 msgid "To get it installed, follow [our Etherpad docs page](docs/configuring-playbook-etherpad.md)." msgstr "" -#: ../../../CHANGELOG.md:3235 +#: ../../../CHANGELOG.md:3266 msgid "2021-01-22" msgstr "" -#: ../../../CHANGELOG.md:3237 +#: ../../../CHANGELOG.md:3268 msgid "(Breaking Change) Postgres changes that require manual intervention" msgstr "" -#: ../../../CHANGELOG.md:3239 +#: ../../../CHANGELOG.md:3270 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:3241 +#: ../../../CHANGELOG.md:3272 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:3243 +#: ../../../CHANGELOG.md:3274 msgid "Why?" msgstr "" -#: ../../../CHANGELOG.md:3245 +#: ../../../CHANGELOG.md:3276 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:3246 +#: ../../../CHANGELOG.md:3277 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:3247 +#: ../../../CHANGELOG.md:3278 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:3248 +#: ../../../CHANGELOG.md:3279 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:3249 +#: ../../../CHANGELOG.md:3280 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:3250 +#: ../../../CHANGELOG.md:3281 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:3252 +#: ../../../CHANGELOG.md:3283 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:3254 +#: ../../../CHANGELOG.md:3285 msgid "What has really changed?" msgstr "" -#: ../../../CHANGELOG.md:3256 +#: ../../../CHANGELOG.md:3287 msgid "the default superuser Postgres username is now `matrix` (used to be `synapse`)" msgstr "" -#: ../../../CHANGELOG.md:3257 +#: ../../../CHANGELOG.md:3288 msgid "the default Postgres database is now `matrix` (used to be `homeserver`)" msgstr "" -#: ../../../CHANGELOG.md:3258 +#: ../../../CHANGELOG.md:3289 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:3259 +#: ../../../CHANGELOG.md:3290 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:3261 +#: ../../../CHANGELOG.md:3292 msgid "What do I do if I'm using the integrated Postgres server (default)?" msgstr "" -#: ../../../CHANGELOG.md:3263 +#: ../../../CHANGELOG.md:3294 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:3265 +#: ../../../CHANGELOG.md:3296 msgid "To migrate to the new setup, expect a few minutes of downtime, while you follow these steps:" msgstr "" -#: ../../../CHANGELOG.md:3267 +#: ../../../CHANGELOG.md:3298 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:3269 +#: ../../../CHANGELOG.md:3300 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:3271 +#: ../../../CHANGELOG.md:3302 msgid "Update your playbook's `inventory/host_vars/matrix.example.com/vars.yml` file, adding a line like this:" msgstr "" -#: ../../../CHANGELOG.md:3276 -#: ../../../CHANGELOG.md:3288 +#: ../../../CHANGELOG.md:3307 +#: ../../../CHANGELOG.md:3319 msgid "… where `YOUR_POSTGRES_PASSWORD_HERE` is to be replaced with the password you generated during step #2." msgstr "" -#: ../../../CHANGELOG.md:3278 +#: ../../../CHANGELOG.md:3309 msgid "Stop all services: `ansible-playbook -i inventory/hosts setup.yml --tags=stop`" msgstr "" -#: ../../../CHANGELOG.md:3279 +#: ../../../CHANGELOG.md:3310 msgid "Log in to the server via SSH. The next commands will be performed there." msgstr "" -#: ../../../CHANGELOG.md:3280 +#: ../../../CHANGELOG.md:3311 msgid "Start the Postgres database server: `systemctl start matrix-postgres`" msgstr "" -#: ../../../CHANGELOG.md:3281 +#: ../../../CHANGELOG.md:3312 msgid "Open a Postgres shell: `/usr/local/bin/matrix-postgres-cli`" msgstr "" -#: ../../../CHANGELOG.md:3282 +#: ../../../CHANGELOG.md:3313 msgid "Execute the following query, while making sure to **change the password inside** (**don't forget the ending `;`**):" msgstr "" -#: ../../../CHANGELOG.md:3290 +#: ../../../CHANGELOG.md:3321 msgid "Execute the following queries as you see them (no modifications necessary, so you can just **paste them all at once**):" msgstr "" -#: ../../../CHANGELOG.md:3308 +#: ../../../CHANGELOG.md:3339 msgid "You may need to press *Enter* after pasting the lines above." msgstr "" -#: ../../../CHANGELOG.md:3310 +#: ../../../CHANGELOG.md:3341 msgid "Re-run the playbook normally: `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`" msgstr "" -#: ../../../CHANGELOG.md:3312 +#: ../../../CHANGELOG.md:3343 msgid "What do I do if I'm using an external Postgres server?" msgstr "" -#: ../../../CHANGELOG.md:3314 +#: ../../../CHANGELOG.md:3345 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:3316 +#: ../../../CHANGELOG.md:3347 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:3319 +#: ../../../CHANGELOG.md:3350 msgid "2021-01-20" msgstr "" -#: ../../../CHANGELOG.md:3321 +#: ../../../CHANGELOG.md:3352 msgid "(Breaking Change) The mautrix-facebook bridge now requires a Postgres database" msgstr "" -#: ../../../CHANGELOG.md:3323 +#: ../../../CHANGELOG.md:3354 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:3325 +#: ../../../CHANGELOG.md:3356 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:3327 +#: ../../../CHANGELOG.md:3358 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:3329 +#: ../../../CHANGELOG.md:3360 msgid "Whether this change requires your intervention depends mostly on:" msgstr "" -#: ../../../CHANGELOG.md:3330 +#: ../../../CHANGELOG.md:3361 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:3331 +#: ../../../CHANGELOG.md:3362 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:3333 +#: ../../../CHANGELOG.md:3364 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:3335 +#: ../../../CHANGELOG.md:3366 msgid "Upgrade path for people NOT running an external Postgres server (default for the playbook)" msgstr "" -#: ../../../CHANGELOG.md:3337 +#: ../../../CHANGELOG.md:3368 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:3339 +#: ../../../CHANGELOG.md:3370 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:3341 +#: ../../../CHANGELOG.md:3372 msgid "Alternatively, [you can stay on SQLite for a little longer](#staying-on-sqlite-for-a-little-longer-temporary-solution)." msgstr "" -#: ../../../CHANGELOG.md:3343 +#: ../../../CHANGELOG.md:3374 msgid "Upgrade path for people running an external Postgres server" msgstr "" -#: ../../../CHANGELOG.md:3345 +#: ../../../CHANGELOG.md:3376 msgid "For people using the internal Postgres server (the default for the playbook):" msgstr "" -#: ../../../CHANGELOG.md:3346 +#: ../../../CHANGELOG.md:3377 msgid "we automatically create an additional `matrix_mautrix_facebook` Postgres database and credentials to access it" msgstr "" -#: ../../../CHANGELOG.md:3347 +#: ../../../CHANGELOG.md:3378 msgid "we automatically adjust the bridge's `matrix_mautrix_facebook_database_*` variables to point the bridge to that Postgres database" msgstr "" -#: ../../../CHANGELOG.md:3348 +#: ../../../CHANGELOG.md:3379 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:3350 +#: ../../../CHANGELOG.md:3381 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:3352 +#: ../../../CHANGELOG.md:3383 msgid "You have 3 ways to proceed:" msgstr "" -#: ../../../CHANGELOG.md:3354 +#: ../../../CHANGELOG.md:3385 msgid "contribute to the playbook to make this possible (difficult)" msgstr "" -#: ../../../CHANGELOG.md:3355 +#: ../../../CHANGELOG.md:3386 msgid "or, do the migration \"steps\" manually:" msgstr "" -#: ../../../CHANGELOG.md:3356 +#: ../../../CHANGELOG.md:3387 msgid "stop the bridge (`systemctl stop matrix-mautrix-facebook`)" msgstr "" -#: ../../../CHANGELOG.md:3357 +#: ../../../CHANGELOG.md:3388 msgid "create a new `matrix_mautrix_facebook` Postgres database for it" msgstr "" -#: ../../../CHANGELOG.md:3358 +#: ../../../CHANGELOG.md:3389 msgid "run [pgloader](https://pgloader.io/) manually (we import this bridge's data using default settings and it works well)" msgstr "" -#: ../../../CHANGELOG.md:3359 +#: ../../../CHANGELOG.md:3390 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:3360 +#: ../../../CHANGELOG.md:3391 msgid "switch the bridge to Postgres (`matrix_mautrix_facebook_database_engine: 'postgres'` in your `vars.yml` file)" msgstr "" -#: ../../../CHANGELOG.md:3361 +#: ../../../CHANGELOG.md:3392 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:3362 +#: ../../../CHANGELOG.md:3393 msgid "send a `login` message to the Facebook bridge bot again" msgstr "" -#: ../../../CHANGELOG.md:3363 +#: ../../../CHANGELOG.md:3394 msgid "or, [stay on SQLite for a little longer (temporary solution)](#staying-on-sqlite-for-a-little-longer-temporary-solution)" msgstr "" -#: ../../../CHANGELOG.md:3365 +#: ../../../CHANGELOG.md:3396 msgid "Staying on SQLite for a little longer (temporary solution)" msgstr "" -#: ../../../CHANGELOG.md:3367 +#: ../../../CHANGELOG.md:3398 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:3377 +#: ../../../CHANGELOG.md:3408 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:3380 +#: ../../../CHANGELOG.md:3411 msgid "2021-01-17" msgstr "" -#: ../../../CHANGELOG.md:3382 +#: ../../../CHANGELOG.md:3413 msgid "matrix-corporal goes 2.0" msgstr "" -#: ../../../CHANGELOG.md:3384 +#: ../../../CHANGELOG.md:3415 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:3386 +#: ../../../CHANGELOG.md:3417 msgid "No manual intervention is required in the common case." msgstr "" -#: ../../../CHANGELOG.md:3388 +#: ../../../CHANGELOG.md:3419 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:3391 +#: ../../../CHANGELOG.md:3422 msgid "2021-01-14" msgstr "" -#: ../../../CHANGELOG.md:3393 +#: ../../../CHANGELOG.md:3424 msgid "Moving from cronjobs to systemd timers" msgstr "" -#: ../../../CHANGELOG.md:3395 +#: ../../../CHANGELOG.md:3426 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:3397 +#: ../../../CHANGELOG.md:3428 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:3399 +#: ../../../CHANGELOG.md:3430 msgid "The playbook will migrate you from cronjobs to systemd timers automatically. This is just a heads up." msgstr "" -#: ../../../CHANGELOG.md:3402 +#: ../../../CHANGELOG.md:3433 msgid "2021-01-08" msgstr "" -#: ../../../CHANGELOG.md:3404 +#: ../../../CHANGELOG.md:3435 msgid "(Breaking Change) New SSL configuration" msgstr "" -#: ../../../CHANGELOG.md:3406 +#: ../../../CHANGELOG.md:3437 msgid "SSL configuration (protocols, ciphers) can now be more easily controlled thanks to us making use of configuration presets." msgstr "" -#: ../../../CHANGELOG.md:3408 +#: ../../../CHANGELOG.md:3439 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:3410 +#: ../../../CHANGELOG.md:3441 msgid "A new variable `matrix_nginx_proxy_ssl_preset` controls which preset is used (defaults to `\"intermediate\"`)." msgstr "" -#: ../../../CHANGELOG.md:3412 +#: ../../../CHANGELOG.md:3443 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:3414 +#: ../../../CHANGELOG.md:3445 msgid "To revert to the old behaviour, set the following variables:" msgstr "" -#: ../../../CHANGELOG.md:3421 +#: ../../../CHANGELOG.md:3452 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:3424 +#: ../../../CHANGELOG.md:3455 msgid "2021-01-03" msgstr "" -#: ../../../CHANGELOG.md:3426 +#: ../../../CHANGELOG.md:3457 msgid "Signal bridging support via mautrix-signal" msgstr "" -#: ../../../CHANGELOG.md:3428 +#: ../../../CHANGELOG.md:3459 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:3430 +#: ../../../CHANGELOG.md:3461 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:3433 +#: ../../../CHANGELOG.md:3464 msgid "2020-12-23" msgstr "" -#: ../../../CHANGELOG.md:3435 +#: ../../../CHANGELOG.md:3466 msgid "The big move to all-on-Postgres (potentially dangerous)" msgstr "" -#: ../../../CHANGELOG.md:3437 +#: ../../../CHANGELOG.md:3468 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:3439 +#: ../../../CHANGELOG.md:3470 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:3441 +#: ../../../CHANGELOG.md:3472 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:3443 +#: ../../../CHANGELOG.md:3474 msgid "Moving all services to Postgres brings a few **benefits** to us:" msgstr "" -#: ../../../CHANGELOG.md:3445 +#: ../../../CHANGELOG.md:3476 msgid "**improved performance**" msgstr "" -#: ../../../CHANGELOG.md:3446 +#: ../../../CHANGELOG.md:3477 msgid "**improved compatibility**. Most bridges are deprecating SQLite/nedb support or offer less features when not on Postgres." msgstr "" -#: ../../../CHANGELOG.md:3447 +#: ../../../CHANGELOG.md:3478 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:3448 +#: ../../../CHANGELOG.md:3479 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:3450 +#: ../../../CHANGELOG.md:3481 msgid "Key takeway" msgstr "" -#: ../../../CHANGELOG.md:3452 +#: ../../../CHANGELOG.md:3483 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:3454 +#: ../../../CHANGELOG.md:3485 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:3456 +#: ../../../CHANGELOG.md:3487 msgid "Opting-out of the Postgres migration" msgstr "" -#: ../../../CHANGELOG.md:3458 +#: ../../../CHANGELOG.md:3489 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:3460 +#: ../../../CHANGELOG.md:3491 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:3462 +#: ../../../CHANGELOG.md:3493 msgid "Some services (like `appservice-irc` and `appservice-slack`) don't use SQLite, so use `nedb`, instead of `sqlite` for them." msgstr "" -#: ../../../CHANGELOG.md:3464 +#: ../../../CHANGELOG.md:3495 msgid "Going back to SQLite/nedb if things went wrong" msgstr "" -#: ../../../CHANGELOG.md:3466 +#: ../../../CHANGELOG.md:3497 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:3468 +#: ../../../CHANGELOG.md:3499 msgid "stop all services (`ansible-playbook -i inventory/hosts setup.yml --tags=stop`)" msgstr "" -#: ../../../CHANGELOG.md:3469 +#: ../../../CHANGELOG.md:3500 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:3470 +#: ../../../CHANGELOG.md:3501 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:3471 +#: ../../../CHANGELOG.md:3502 msgid "re-run the playbook (`ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`)" msgstr "" -#: ../../../CHANGELOG.md:3472 +#: ../../../CHANGELOG.md:3503 msgid "[get in touch](README.md#support) with us" msgstr "" -#: ../../../CHANGELOG.md:3474 +#: ../../../CHANGELOG.md:3505 msgid "2020-12-11" msgstr "" -#: ../../../CHANGELOG.md:3476 +#: ../../../CHANGELOG.md:3507 msgid "synapse-janitor support removed" msgstr "" -#: ../../../CHANGELOG.md:3478 +#: ../../../CHANGELOG.md:3509 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:3480 +#: ../../../CHANGELOG.md:3511 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:3482 +#: ../../../CHANGELOG.md:3513 msgid "Docker 20.10 is here" msgstr "" -#: ../../../CHANGELOG.md:3484 +#: ../../../CHANGELOG.md:3515 msgid "(No need to do anything special in relation to this. Just something to keep in mind)" msgstr "" -#: ../../../CHANGELOG.md:3486 +#: ../../../CHANGELOG.md:3517 msgid "Docker 20.10 got released recently and your server will likely get it the next time you update." msgstr "" -#: ../../../CHANGELOG.md:3488 +#: ../../../CHANGELOG.md:3519 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:3491 +#: ../../../CHANGELOG.md:3522 msgid "2020-12-08" msgstr "" -#: ../../../CHANGELOG.md:3493 +#: ../../../CHANGELOG.md:3524 msgid "openid APIs exposed by default on the federation port when federation disabled" msgstr "" -#: ../../../CHANGELOG.md:3495 +#: ../../../CHANGELOG.md:3526 msgid "We've changed some defaults. People running with our default configuration (federation enabled), are not affected at all." msgstr "" -#: ../../../CHANGELOG.md:3497 +#: ../../../CHANGELOG.md:3528 msgid "If you are running an unfederated server (`matrix_synapse_federation_enabled: false`), this may be of interest to you." msgstr "" -#: ../../../CHANGELOG.md:3499 +#: ../../../CHANGELOG.md:3530 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:3502 +#: ../../../CHANGELOG.md:3533 msgid "2020-11-27" msgstr "" -#: ../../../CHANGELOG.md:3504 +#: ../../../CHANGELOG.md:3535 msgid "Recent Jitsi updates may require configuration changes" msgstr "" -#: ../../../CHANGELOG.md:3506 +#: ../../../CHANGELOG.md:3537 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:3508 +#: ../../../CHANGELOG.md:3539 msgid "**If you use our default Jitsi settings, you won't have to do anything.**" msgstr "" -#: ../../../CHANGELOG.md:3510 +#: ../../../CHANGELOG.md:3541 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:3512 +#: ../../../CHANGELOG.md:3543 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:3514 +#: ../../../CHANGELOG.md:3545 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:3517 +#: ../../../CHANGELOG.md:3548 msgid "2020-11-23" msgstr "" -#: ../../../CHANGELOG.md:3519 -#: ../../../CHANGELOG.md:3527 +#: ../../../CHANGELOG.md:3550 +#: ../../../CHANGELOG.md:3558 msgid "Breaking change matrix-sms-bridge" msgstr "" -#: ../../../CHANGELOG.md:3521 +#: ../../../CHANGELOG.md:3552 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:3523 +#: ../../../CHANGELOG.md:3554 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:3525 +#: ../../../CHANGELOG.md:3556 msgid "2020-11-13" msgstr "" -#: ../../../CHANGELOG.md:3529 +#: ../../../CHANGELOG.md:3560 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:3531 +#: ../../../CHANGELOG.md:3562 msgid "Add the following to your `vars.yml` file: `matrix_sms_bridge_container_extra_arguments=['--env SPRING_PROFILES_ACTIVE=initialsync']`" msgstr "" -#: ../../../CHANGELOG.md:3532 +#: ../../../CHANGELOG.md:3563 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:3533 +#: ../../../CHANGELOG.md:3564 msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-matrix-sms-bridge,start`" msgstr "" -#: ../../../CHANGELOG.md:3534 +#: ../../../CHANGELOG.md:3565 msgid "Login to your host shell and check the logs with `journalctl -u matrix-sms-bridge` until the sync finished." msgstr "" -#: ../../../CHANGELOG.md:3535 +#: ../../../CHANGELOG.md:3566 msgid "Remove the var from the first step." msgstr "" -#: ../../../CHANGELOG.md:3536 +#: ../../../CHANGELOG.md:3567 msgid "Run `ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start`." msgstr "" -#: ../../../CHANGELOG.md:3538 +#: ../../../CHANGELOG.md:3569 msgid "2020-11-10" msgstr "" -#: ../../../CHANGELOG.md:3540 +#: ../../../CHANGELOG.md:3571 msgid "Dynamic DNS support" msgstr "" -#: ../../../CHANGELOG.md:3542 +#: ../../../CHANGELOG.md:3573 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:3544 +#: ../../../CHANGELOG.md:3575 msgid "To learn more, follow our [Dynamic DNS docs page](docs/configuring-playbook-dynamic-dns.md)." msgstr "" -#: ../../../CHANGELOG.md:3547 +#: ../../../CHANGELOG.md:3578 msgid "2020-10-28" msgstr "" -#: ../../../CHANGELOG.md:3549 +#: ../../../CHANGELOG.md:3580 msgid "(Compatibility Break) https://matrix.example.com/ now redirects to https://element.example.com/" msgstr "" -#: ../../../CHANGELOG.md:3551 +#: ../../../CHANGELOG.md:3582 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:3553 +#: ../../../CHANGELOG.md:3584 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:3555 +#: ../../../CHANGELOG.md:3586 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:3557 +#: ../../../CHANGELOG.md:3588 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:3560 +#: ../../../CHANGELOG.md:3591 msgid "2020-10-26" msgstr "" -#: ../../../CHANGELOG.md:3562 +#: ../../../CHANGELOG.md:3593 msgid "(Compatibility Break) /_synapse/admin is no longer publicly exposed by default" msgstr "" -#: ../../../CHANGELOG.md:3564 +#: ../../../CHANGELOG.md:3595 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:3566 +#: ../../../CHANGELOG.md:3597 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:3568 +#: ../../../CHANGELOG.md:3599 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:3575 +#: ../../../CHANGELOG.md:3606 msgid "2020-10-02" msgstr "" -#: ../../../CHANGELOG.md:3577 +#: ../../../CHANGELOG.md:3608 msgid "Minimum Ansible version raised to v2.7.0" msgstr "" -#: ../../../CHANGELOG.md:3579 +#: ../../../CHANGELOG.md:3610 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:3581 +#: ../../../CHANGELOG.md:3612 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:3583 +#: ../../../CHANGELOG.md:3614 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:3586 +#: ../../../CHANGELOG.md:3617 msgid "2020-10-01" msgstr "" -#: ../../../CHANGELOG.md:3588 +#: ../../../CHANGELOG.md:3619 msgid "Postgres 13 support" msgstr "" -#: ../../../CHANGELOG.md:3590 +#: ../../../CHANGELOG.md:3621 msgid "The playbook now installs [Postgres 13](https://www.postgresql.org/about/news/postgresql-13-released-2077/) by default." msgstr "" -#: ../../../CHANGELOG.md:3592 +#: ../../../CHANGELOG.md:3623 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:3594 +#: ../../../CHANGELOG.md:3625 msgid "2020-09-01" msgstr "" -#: ../../../CHANGELOG.md:3596 +#: ../../../CHANGELOG.md:3627 msgid "matrix-registration support" msgstr "" -#: ../../../CHANGELOG.md:3598 +#: ../../../CHANGELOG.md:3629 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:3600 +#: ../../../CHANGELOG.md:3631 msgid "See our [Setting up matrix-registration](docs/configuring-playbook-matrix-registration.md) documentation page to get started." msgstr "" -#: ../../../CHANGELOG.md:3603 +#: ../../../CHANGELOG.md:3634 msgid "2020-08-21" msgstr "" -#: ../../../CHANGELOG.md:3605 +#: ../../../CHANGELOG.md:3636 msgid "rust-synapse-compress-state support" msgstr "" -#: ../../../CHANGELOG.md:3607 +#: ../../../CHANGELOG.md:3638 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:3609 +#: ../../../CHANGELOG.md:3640 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:3612 +#: ../../../CHANGELOG.md:3643 msgid "2020-07-22" msgstr "" -#: ../../../CHANGELOG.md:3614 +#: ../../../CHANGELOG.md:3645 msgid "Synapse Admin support" msgstr "" -#: ../../../CHANGELOG.md:3616 +#: ../../../CHANGELOG.md:3647 msgid "The playbook can now help you set up [synapse-admin](https://github.com/Awesome-Technologies/synapse-admin)." msgstr "" -#: ../../../CHANGELOG.md:3618 +#: ../../../CHANGELOG.md:3649 msgid "See our [Setting up Synapse Admin](docs/configuring-playbook-synapse-admin.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:3621 +#: ../../../CHANGELOG.md:3652 msgid "2020-07-20" msgstr "" -#: ../../../CHANGELOG.md:3623 +#: ../../../CHANGELOG.md:3654 msgid "matrix-reminder-bot support" msgstr "" -#: ../../../CHANGELOG.md:3625 +#: ../../../CHANGELOG.md:3656 msgid "The playbook can now help you set up [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot)." msgstr "" -#: ../../../CHANGELOG.md:3627 +#: ../../../CHANGELOG.md:3658 msgid "See our [Setting up matrix-reminder-bot](docs/configuring-playbook-bot-matrix-reminder-bot.md) documentation to get started." msgstr "" -#: ../../../CHANGELOG.md:3630 +#: ../../../CHANGELOG.md:3661 msgid "2020-07-17" msgstr "" -#: ../../../CHANGELOG.md:3632 +#: ../../../CHANGELOG.md:3663 msgid "(Compatibility Break) Riot is now Element" msgstr "" -#: ../../../CHANGELOG.md:3634 +#: ../../../CHANGELOG.md:3665 msgid "As per the official announcement, [Riot has been rebraned to Element](https://element.io/blog/welcome-to-element/)." msgstr "" -#: ../../../CHANGELOG.md:3636 +#: ../../../CHANGELOG.md:3667 msgid "The playbook follows suit. Existing installations have a few options for how to handle this." msgstr "" -#: ../../../CHANGELOG.md:3638 +#: ../../../CHANGELOG.md:3669 msgid "See our [Migrating to Element Web](docs/configuring-playbook-riot-web.md#migrating-to-element) documentation page for more details." msgstr "" -#: ../../../CHANGELOG.md:3641 +#: ../../../CHANGELOG.md:3672 msgid "2020-07-03" msgstr "" -#: ../../../CHANGELOG.md:3643 +#: ../../../CHANGELOG.md:3674 msgid "Steam bridging support via mx-puppet-steam" msgstr "" -#: ../../../CHANGELOG.md:3645 +#: ../../../CHANGELOG.md:3676 msgid "Thanks to [Hugues Morisset](https://github.com/izissise)'s efforts, the playbook now supports bridging to [Steam](https://steamapp.com/) via the [mx-puppet-steam](https://codeberg.org/icewind/mx-puppet-steam) bridge. See our [Setting up MX Puppet Steam bridging](docs/configuring-playbook-bridge-mx-puppet-steam.md) documentation page for getting started." msgstr "" -#: ../../../CHANGELOG.md:3648 +#: ../../../CHANGELOG.md:3679 msgid "2020-07-01" msgstr "" -#: ../../../CHANGELOG.md:3650 +#: ../../../CHANGELOG.md:3681 msgid "Discord bridging support via mx-puppet-discord" msgstr "" -#: ../../../CHANGELOG.md:3652 +#: ../../../CHANGELOG.md:3683 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:3654 +#: ../../../CHANGELOG.md:3685 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:3657 +#: ../../../CHANGELOG.md:3688 msgid "2020-06-30" msgstr "" -#: ../../../CHANGELOG.md:3659 +#: ../../../CHANGELOG.md:3690 msgid "Instagram and Twitter bridging support" msgstr "" -#: ../../../CHANGELOG.md:3661 +#: ../../../CHANGELOG.md:3692 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:3663 +#: ../../../CHANGELOG.md:3694 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:3666 +#: ../../../CHANGELOG.md:3697 msgid "2020-06-28" msgstr "" -#: ../../../CHANGELOG.md:3668 +#: ../../../CHANGELOG.md:3699 msgid "(Post Mortem / fixed Security Issue) Re-enabling User Directory search powered by the ma1sd Identity Server" msgstr "" -#: ../../../CHANGELOG.md:3670 -#: ../../../CHANGELOG.md:3699 +#: ../../../CHANGELOG.md:3701 +#: ../../../CHANGELOG.md:3730 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:3672 +#: ../../../CHANGELOG.md:3703 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:3674 +#: ../../../CHANGELOG.md:3705 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:3676 +#: ../../../CHANGELOG.md:3707 msgid "As always, re-running the playbook is enough to get the updated bits." msgstr "" -#: ../../../CHANGELOG.md:3678 +#: ../../../CHANGELOG.md:3709 msgid "2020-06-11" msgstr "" -#: ../../../CHANGELOG.md:3680 +#: ../../../CHANGELOG.md:3711 msgid "SMS bridging requires db reset" msgstr "" -#: ../../../CHANGELOG.md:3682 +#: ../../../CHANGELOG.md:3713 msgid "The current version of [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) needs you to delete the database to work as expected. Just remove `/matrix/matrix-sms-bridge/database/*`. It also adds a new required var `matrix_sms_bridge_default_region`." msgstr "" -#: ../../../CHANGELOG.md:3684 +#: ../../../CHANGELOG.md:3715 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:3686 +#: ../../../CHANGELOG.md:3717 msgid "2020-06-05" msgstr "" -#: ../../../CHANGELOG.md:3688 +#: ../../../CHANGELOG.md:3719 msgid "SMS bridging support" msgstr "" -#: ../../../CHANGELOG.md:3690 +#: ../../../CHANGELOG.md:3721 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:3692 +#: ../../../CHANGELOG.md:3723 msgid "See our [Setting up Matrix SMS bridging](docs/configuring-playbook-bridge-matrix-bridge-sms.md) documentation page for getting started." msgstr "" -#: ../../../CHANGELOG.md:3695 +#: ../../../CHANGELOG.md:3726 msgid "2020-05-19" msgstr "" -#: ../../../CHANGELOG.md:3697 +#: ../../../CHANGELOG.md:3728 msgid "(Compatibility Break / Security Issue) Disabling User Directory search powered by the ma1sd Identity Server" msgstr "" -#: ../../../CHANGELOG.md:3701 +#: ../../../CHANGELOG.md:3732 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:3703 +#: ../../../CHANGELOG.md:3734 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:3705 +#: ../../../CHANGELOG.md:3736 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:3708 +#: ../../../CHANGELOG.md:3739 msgid "2020-04-28" msgstr "" -#: ../../../CHANGELOG.md:3710 +#: ../../../CHANGELOG.md:3741 msgid "Newer IRC bridge (with potential breaking change)" msgstr "" -#: ../../../CHANGELOG.md:3712 +#: ../../../CHANGELOG.md:3743 msgid "This upgrades matrix-appservice-irc from 0.14.1 to 0.16.0. Upstream made a change to how you define manual mappings. If you added a `mapping` to your configuration, you will need to update it according to the [upstream instructions](https://github.com/matrix-org/matrix-appservice-irc/blob/master/CHANGELOG.md#0150-2020-02-05). If you did not include `mappings` in your configuration for IRC, no change is necessary. `mappings` is not part of the default configuration." msgstr "" -#: ../../../CHANGELOG.md:3721 +#: ../../../CHANGELOG.md:3752 msgid "2020-04-23" msgstr "" -#: ../../../CHANGELOG.md:3723 -#: ../../../CHANGELOG.md:3954 +#: ../../../CHANGELOG.md:3754 +#: ../../../CHANGELOG.md:3985 msgid "Slack bridging support" msgstr "" -#: ../../../CHANGELOG.md:3725 +#: ../../../CHANGELOG.md:3756 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:3727 +#: ../../../CHANGELOG.md:3758 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:3730 +#: ../../../CHANGELOG.md:3761 msgid "2020-04-09" msgstr "" -#: ../../../CHANGELOG.md:3732 +#: ../../../CHANGELOG.md:3763 msgid "Skype bridging support" msgstr "" -#: ../../../CHANGELOG.md:3734 +#: ../../../CHANGELOG.md:3765 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:3736 +#: ../../../CHANGELOG.md:3767 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:3739 +#: ../../../CHANGELOG.md:3770 msgid "2020-04-05" msgstr "" -#: ../../../CHANGELOG.md:3741 +#: ../../../CHANGELOG.md:3772 msgid "Private Jitsi support" msgstr "" -#: ../../../CHANGELOG.md:3743 +#: ../../../CHANGELOG.md:3774 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:3745 +#: ../../../CHANGELOG.md:3776 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:3747 +#: ../../../CHANGELOG.md:3778 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:3750 +#: ../../../CHANGELOG.md:3781 msgid "2020-04-03" msgstr "" -#: ../../../CHANGELOG.md:3752 +#: ../../../CHANGELOG.md:3783 msgid "(Potential Backward Compatibility Break) ma1sd replaces mxisd" msgstr "" -#: ../../../CHANGELOG.md:3754 +#: ../../../CHANGELOG.md:3785 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:3756 +#: ../../../CHANGELOG.md:3787 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:3758 +#: ../../../CHANGELOG.md:3789 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:3761 +#: ../../../CHANGELOG.md:3792 msgid "2020-03-29" msgstr "" -#: ../../../CHANGELOG.md:3763 +#: ../../../CHANGELOG.md:3794 msgid "Archlinux support" msgstr "" -#: ../../../CHANGELOG.md:3765 +#: ../../../CHANGELOG.md:3796 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:3768 +#: ../../../CHANGELOG.md:3799 msgid "2020-03-24" msgstr "" -#: ../../../CHANGELOG.md:3770 +#: ../../../CHANGELOG.md:3801 msgid "Jitsi support" msgstr "" -#: ../../../CHANGELOG.md:3772 +#: ../../../CHANGELOG.md:3803 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:3774 +#: ../../../CHANGELOG.md:3805 msgid "See our [Jitsi documentation page](docs/configuring-playbook-jitsi.md) to get started." msgstr "" -#: ../../../CHANGELOG.md:3777 +#: ../../../CHANGELOG.md:3808 msgid "2020-03-15" msgstr "" -#: ../../../CHANGELOG.md:3779 +#: ../../../CHANGELOG.md:3810 msgid "Raspberry Pi support" msgstr "" -#: ../../../CHANGELOG.md:3781 +#: ../../../CHANGELOG.md:3812 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:3783 +#: ../../../CHANGELOG.md:3814 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:3786 +#: ../../../CHANGELOG.md:3817 msgid "2020-02-26" msgstr "" -#: ../../../CHANGELOG.md:3788 +#: ../../../CHANGELOG.md:3819 msgid "Riot-web themes are here" msgstr "" -#: ../../../CHANGELOG.md:3790 +#: ../../../CHANGELOG.md:3821 msgid "The playbook now makes it easy to install custom riot-web themes." msgstr "" -#: ../../../CHANGELOG.md:3792 +#: ../../../CHANGELOG.md:3823 msgid "To learn more, take a look at our [riot-web documentation on Themes](docs/configuring-playbook-riot-web.md#themes)." msgstr "" -#: ../../../CHANGELOG.md:3795 +#: ../../../CHANGELOG.md:3826 msgid "2020-02-24" msgstr "" -#: ../../../CHANGELOG.md:3797 +#: ../../../CHANGELOG.md:3828 msgid "Customize the server name in Riot's login page" msgstr "" -#: ../../../CHANGELOG.md:3799 +#: ../../../CHANGELOG.md:3830 msgid "You can now customize the server name string that Riot-web displays in its login page." msgstr "" -#: ../../../CHANGELOG.md:3801 +#: ../../../CHANGELOG.md:3832 msgid "These playbook variables, with these default values, have been added:" msgstr "" -#: ../../../CHANGELOG.md:3807 +#: ../../../CHANGELOG.md:3838 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:3809 +#: ../../../CHANGELOG.md:3840 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:3812 +#: ../../../CHANGELOG.md:3843 msgid "2020-01-30" msgstr "" -#: ../../../CHANGELOG.md:3814 +#: ../../../CHANGELOG.md:3845 msgid "Disabling TLSv1.1" msgstr "" -#: ../../../CHANGELOG.md:3816 +#: ../../../CHANGELOG.md:3847 msgid "To improve security, we've removed TLSv1.1 support from our default matrix-nginx-proxy configuration." msgstr "" -#: ../../../CHANGELOG.md:3818 +#: ../../../CHANGELOG.md:3849 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:3821 +#: ../../../CHANGELOG.md:3852 msgid "2020-01-21" msgstr "" -#: ../../../CHANGELOG.md:3823 +#: ../../../CHANGELOG.md:3854 msgid "Postgres collation changes (action required!)" msgstr "" -#: ../../../CHANGELOG.md:3825 +#: ../../../CHANGELOG.md:3856 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:3827 +#: ../../../CHANGELOG.md:3858 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:3829 +#: ../../../CHANGELOG.md:3860 msgid "To avoid future problems, we recommend that you run the following command:" msgstr "" -#: ../../../CHANGELOG.md:3835 +#: ../../../CHANGELOG.md:3866 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:3838 +#: ../../../CHANGELOG.md:3869 msgid "2020-01-14" msgstr "" -#: ../../../CHANGELOG.md:3840 +#: ../../../CHANGELOG.md:3871 msgid "Added support for Appservice Webhooks" msgstr "" -#: ../../../CHANGELOG.md:3842 +#: ../../../CHANGELOG.md:3873 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:3844 +#: ../../../CHANGELOG.md:3875 msgid "Learn more in [Setting up Appservice Webhooks bridging](docs/configuring-playbook-bridge-appservice-webhooks.md)." msgstr "" -#: ../../../CHANGELOG.md:3847 +#: ../../../CHANGELOG.md:3878 msgid "2020-01-12" msgstr "" -#: ../../../CHANGELOG.md:3849 +#: ../../../CHANGELOG.md:3880 msgid "Added support for automatic Double Puppeting for all Mautrix bridges" msgstr "" -#: ../../../CHANGELOG.md:3851 +#: ../../../CHANGELOG.md:3882 msgid "Double Puppeting can now be easily enabled for all Mautrix bridges supported by the playbook (Facebook, Hangouts, Whatsapp, Telegram)." msgstr "" -#: ../../../CHANGELOG.md:3853 +#: ../../../CHANGELOG.md:3884 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:3855 +#: ../../../CHANGELOG.md:3886 msgid "To get started, following the playbook's documentation for the bridge you'd like to configure." msgstr "" -#: ../../../CHANGELOG.md:3858 +#: ../../../CHANGELOG.md:3889 msgid "2019-12-06" msgstr "" -#: ../../../CHANGELOG.md:3860 +#: ../../../CHANGELOG.md:3891 msgid "Added support for an alternative method for using another webserver" msgstr "" -#: ../../../CHANGELOG.md:3862 +#: ../../../CHANGELOG.md:3893 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:3864 +#: ../../../CHANGELOG.md:3895 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:3866 +#: ../../../CHANGELOG.md:3897 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:3869 +#: ../../../CHANGELOG.md:3900 msgid "2019-11-10" msgstr "" -#: ../../../CHANGELOG.md:3871 +#: ../../../CHANGELOG.md:3902 msgid "Tightened security around room directory publishing" msgstr "" -#: ../../../CHANGELOG.md:3873 +#: ../../../CHANGELOG.md:3904 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:3875 +#: ../../../CHANGELOG.md:3906 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:3877 +#: ../../../CHANGELOG.md:3908 msgid "As with anything else, these new defaults can be overridden by changing the `matrix_synapse_allow_public_rooms_without_auth` and `matrix_synapse_allow_public_rooms_over_federation` variables, respectively." msgstr "" -#: ../../../CHANGELOG.md:3880 +#: ../../../CHANGELOG.md:3911 msgid "2019-10-05" msgstr "" -#: ../../../CHANGELOG.md:3882 +#: ../../../CHANGELOG.md:3913 msgid "Improved Postgres upgrading/importing" msgstr "" -#: ../../../CHANGELOG.md:3884 +#: ../../../CHANGELOG.md:3915 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:3886 +#: ../../../CHANGELOG.md:3917 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:3888 +#: ../../../CHANGELOG.md:3919 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:3890 +#: ../../../CHANGELOG.md:3921 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:3893 +#: ../../../CHANGELOG.md:3924 msgid "2019-10-04" msgstr "" -#: ../../../CHANGELOG.md:3895 +#: ../../../CHANGELOG.md:3926 msgid "Postgres 12 support" msgstr "" -#: ../../../CHANGELOG.md:3897 +#: ../../../CHANGELOG.md:3928 msgid "The playbook now installs [Postgres 12](https://www.postgresql.org/about/news/1976/) by default." msgstr "" -#: ../../../CHANGELOG.md:3899 +#: ../../../CHANGELOG.md:3930 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:3902 +#: ../../../CHANGELOG.md:3933 msgid "2019-10-03" msgstr "" -#: ../../../CHANGELOG.md:3904 +#: ../../../CHANGELOG.md:3935 msgid "Synapse 1.4.0" msgstr "" -#: ../../../CHANGELOG.md:3906 +#: ../../../CHANGELOG.md:3937 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:3908 +#: ../../../CHANGELOG.md:3939 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:3910 +#: ../../../CHANGELOG.md:3941 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:3912 +#: ../../../CHANGELOG.md:3943 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:3915 +#: ../../../CHANGELOG.md:3946 msgid "2019-09-09" msgstr "" -#: ../../../CHANGELOG.md:3917 +#: ../../../CHANGELOG.md:3948 msgid "Synapse Simple Antispam support" msgstr "" -#: ../../../CHANGELOG.md:3919 +#: ../../../CHANGELOG.md:3950 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:3921 +#: ../../../CHANGELOG.md:3952 msgid "From now on, you can easily install and configure this spam checker module through the playbook." msgstr "" -#: ../../../CHANGELOG.md:3923 +#: ../../../CHANGELOG.md:3954 msgid "Learn more in [Setting up Synapse Simple Antispam](docs/configuring-playbook-synapse-simple-antispam.md)." msgstr "" -#: ../../../CHANGELOG.md:3926 +#: ../../../CHANGELOG.md:3957 msgid "2019-08-25" msgstr "" -#: ../../../CHANGELOG.md:3928 +#: ../../../CHANGELOG.md:3959 msgid "Extensible Riot-web configuration" msgstr "" -#: ../../../CHANGELOG.md:3930 +#: ../../../CHANGELOG.md:3961 msgid "Similarly to [Extensible Synapse configuration](#extensible-synapse-configuration) (below), Riot-web configuration is also extensible now." msgstr "" -#: ../../../CHANGELOG.md:3932 +#: ../../../CHANGELOG.md:3963 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:3934 +#: ../../../CHANGELOG.md:3965 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:3936 +#: ../../../CHANGELOG.md:3967 msgid "Learn more in [Configuring Riot-web](docs/configuring-playbook-riot-web.md)." msgstr "" -#: ../../../CHANGELOG.md:3939 +#: ../../../CHANGELOG.md:3970 msgid "2019-08-22" msgstr "" -#: ../../../CHANGELOG.md:3941 +#: ../../../CHANGELOG.md:3972 msgid "Extensible Synapse configuration" msgstr "" -#: ../../../CHANGELOG.md:3943 +#: ../../../CHANGELOG.md:3974 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:3945 +#: ../../../CHANGELOG.md:3976 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:3947 +#: ../../../CHANGELOG.md:3978 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:3949 +#: ../../../CHANGELOG.md:3980 msgid "Learn more here in [Configuring Synapse](docs/configuring-playbook-synapse.md)." msgstr "" -#: ../../../CHANGELOG.md:3952 +#: ../../../CHANGELOG.md:3983 msgid "2019-08-21" msgstr "" -#: ../../../CHANGELOG.md:3956 +#: ../../../CHANGELOG.md:3987 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:3958 +#: ../../../CHANGELOG.md:3989 msgid "Additional details are available in [Setting up Appservice Slack bridging](docs/configuring-playbook-bridge-appservice-slack.md)." msgstr "" -#: ../../../CHANGELOG.md:3960 +#: ../../../CHANGELOG.md:3991 msgid "Google Hangouts bridging support" msgstr "" -#: ../../../CHANGELOG.md:3962 +#: ../../../CHANGELOG.md:3993 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:3964 +#: ../../../CHANGELOG.md:3995 msgid "Additional details are available in [Setting up Mautrix Hangouts bridging](docs/configuring-playbook-bridge-mautrix-hangouts.md)." msgstr "" -#: ../../../CHANGELOG.md:3967 +#: ../../../CHANGELOG.md:3998 msgid "2019-08-05" msgstr "" -#: ../../../CHANGELOG.md:3969 +#: ../../../CHANGELOG.md:4000 msgid "Email2Matrix support" msgstr "" -#: ../../../CHANGELOG.md:3971 +#: ../../../CHANGELOG.md:4002 msgid "Support for [Email2Matrix](https://github.com/devture/email2matrix) has been added." msgstr "" -#: ../../../CHANGELOG.md:3973 +#: ../../../CHANGELOG.md:4004 msgid "It's an optional feature that you can enable via the playbook." msgstr "" -#: ../../../CHANGELOG.md:3975 +#: ../../../CHANGELOG.md:4006 msgid "To learn more, see the [playbook's documentation on Email2Matrix](./docs/configuring-playbook-email2matrix.md)." msgstr "" -#: ../../../CHANGELOG.md:3978 +#: ../../../CHANGELOG.md:4009 msgid "2019-08-03" msgstr "" -#: ../../../CHANGELOG.md:3980 +#: ../../../CHANGELOG.md:4011 msgid "Synapse logging level has been reduced to WARNING" msgstr "" -#: ../../../CHANGELOG.md:3982 +#: ../../../CHANGELOG.md:4013 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:3984 +#: ../../../CHANGELOG.md:4015 msgid "This greatly reduces the number of log messages that are being logged, leading to:" msgstr "" -#: ../../../CHANGELOG.md:3986 +#: ../../../CHANGELOG.md:4017 msgid "much less disk space dedicated to Synapse and thus, logs kept for longer" msgstr "" -#: ../../../CHANGELOG.md:3987 +#: ../../../CHANGELOG.md:4018 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:3989 +#: ../../../CHANGELOG.md:4020 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:3992 +#: ../../../CHANGELOG.md:4023 msgid "2019-07-08" msgstr "" -#: ../../../CHANGELOG.md:3994 +#: ../../../CHANGELOG.md:4025 msgid "Synapse Maintenance docs and synapse-janitor support are available" msgstr "" -#: ../../../CHANGELOG.md:3996 +#: ../../../CHANGELOG.md:4027 msgid "The playbook can now help you with Synapse's maintenance." msgstr "" -#: ../../../CHANGELOG.md:3998 +#: ../../../CHANGELOG.md:4029 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:4000 +#: ../../../CHANGELOG.md:4031 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:4002 +#: ../../../CHANGELOG.md:4033 msgid "(BC Break) Rename run control variables" msgstr "" -#: ../../../CHANGELOG.md:4004 +#: ../../../CHANGELOG.md:4035 msgid "Some internal playbook control variables have been renamed." msgstr "" -#: ../../../CHANGELOG.md:4006 +#: ../../../CHANGELOG.md:4037 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:4008 +#: ../../../CHANGELOG.md:4039 msgid "The following variables have been renamed:" msgstr "" -#: ../../../CHANGELOG.md:4010 +#: ../../../CHANGELOG.md:4041 msgid "from `run_import_postgres` to `run_postgres_import`" msgstr "" -#: ../../../CHANGELOG.md:4011 +#: ../../../CHANGELOG.md:4042 msgid "from `run_import_sqlite_db` to `run_postgres_import_sqlite_db`" msgstr "" -#: ../../../CHANGELOG.md:4012 +#: ../../../CHANGELOG.md:4043 msgid "from `run_upgrade_postgres` to `run_postgres_upgrade`" msgstr "" -#: ../../../CHANGELOG.md:4013 +#: ../../../CHANGELOG.md:4044 msgid "from `run_import_media_store` to `run_synapse_import_media_store`" msgstr "" -#: ../../../CHANGELOG.md:4014 +#: ../../../CHANGELOG.md:4045 msgid "from `run_register_user` to `run_synapse_register_user`" msgstr "" -#: ../../../CHANGELOG.md:4015 +#: ../../../CHANGELOG.md:4046 msgid "from `run_update_user_password` to `run_synapse_update_user_password`" msgstr "" -#: ../../../CHANGELOG.md:4018 +#: ../../../CHANGELOG.md:4049 msgid "2019-07-04" msgstr "" -#: ../../../CHANGELOG.md:4020 +#: ../../../CHANGELOG.md:4051 msgid "Synapse no longer logs to text files" msgstr "" -#: ../../../CHANGELOG.md:4022 +#: ../../../CHANGELOG.md:4053 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:4024 +#: ../../../CHANGELOG.md:4055 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:4026 +#: ../../../CHANGELOG.md:4057 msgid "Because of this, the following variables have become obsolete and were removed:" msgstr "" -#: ../../../CHANGELOG.md:4028 +#: ../../../CHANGELOG.md:4059 msgid "`matrix_synapse_max_log_file_size_mb`" msgstr "" -#: ../../../CHANGELOG.md:4029 +#: ../../../CHANGELOG.md:4060 msgid "`matrix_synapse_max_log_files_count`" msgstr "" -#: ../../../CHANGELOG.md:4031 +#: ../../../CHANGELOG.md:4062 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:4033 +#: ../../../CHANGELOG.md:4064 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:4036 +#: ../../../CHANGELOG.md:4067 msgid "2019-06-27" msgstr "" -#: ../../../CHANGELOG.md:4038 +#: ../../../CHANGELOG.md:4069 msgid "(BC Break) Discord bridge configuration is now entirely managed by the playbook" msgstr "" -#: ../../../CHANGELOG.md:4040 +#: ../../../CHANGELOG.md:4071 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:4042 +#: ../../../CHANGELOG.md:4073 msgid "From now on, the playbook will keep both configuration files sync for you." msgstr "" -#: ../../../CHANGELOG.md:4044 +#: ../../../CHANGELOG.md:4075 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:4046 +#: ../../../CHANGELOG.md:4077 msgid "The bridge now stores configuration in a subdirectory (`/matrix/appservice-discord/config`)." msgstr "" -#: ../../../CHANGELOG.md:4048 +#: ../../../CHANGELOG.md:4079 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:4050 +#: ../../../CHANGELOG.md:4081 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:4052 +#: ../../../CHANGELOG.md:4083 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:4055 +#: ../../../CHANGELOG.md:4086 msgid "2019-06-24" msgstr "" -#: ../../../CHANGELOG.md:4057 +#: ../../../CHANGELOG.md:4088 msgid "(BC Break) WhatsApp bridge configuration is now entirely managed by the playbook" msgstr "" -#: ../../../CHANGELOG.md:4059 +#: ../../../CHANGELOG.md:4090 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:4061 -#: ../../../CHANGELOG.md:4078 -#: ../../../CHANGELOG.md:4097 -#: ../../../CHANGELOG.md:4136 +#: ../../../CHANGELOG.md:4092 +#: ../../../CHANGELOG.md:4109 +#: ../../../CHANGELOG.md:4128 +#: ../../../CHANGELOG.md:4167 msgid "From now on, the playbook will keep the configuration in sync for you." msgstr "" -#: ../../../CHANGELOG.md:4063 +#: ../../../CHANGELOG.md:4094 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:4065 +#: ../../../CHANGELOG.md:4096 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:4067 +#: ../../../CHANGELOG.md:4098 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:4069 +#: ../../../CHANGELOG.md:4100 msgid "We're now following the default configuration for the WhatsApp bridge." msgstr "" -#: ../../../CHANGELOG.md:4072 +#: ../../../CHANGELOG.md:4103 msgid "2019-06-20" msgstr "" -#: ../../../CHANGELOG.md:4074 +#: ../../../CHANGELOG.md:4105 msgid "(BC Break) IRC bridge configuration is now entirely managed by the playbook" msgstr "" -#: ../../../CHANGELOG.md:4076 +#: ../../../CHANGELOG.md:4107 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:4080 +#: ../../../CHANGELOG.md:4111 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:4082 +#: ../../../CHANGELOG.md:4113 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:4084 +#: ../../../CHANGELOG.md:4115 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:4086 +#: ../../../CHANGELOG.md:4117 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:4088 +#: ../../../CHANGELOG.md:4119 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:4091 +#: ../../../CHANGELOG.md:4122 msgid "2019-06-15" msgstr "" -#: ../../../CHANGELOG.md:4093 +#: ../../../CHANGELOG.md:4124 msgid "(BC Break) Telegram bridge configuration is now entirely managed by the playbook" msgstr "" -#: ../../../CHANGELOG.md:4095 +#: ../../../CHANGELOG.md:4126 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:4099 +#: ../../../CHANGELOG.md:4130 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:4101 +#: ../../../CHANGELOG.md:4132 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:4103 +#: ../../../CHANGELOG.md:4134 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:4105 +#: ../../../CHANGELOG.md:4136 msgid "Also, we're now following the default configuration for the Telegram bridge, so some default configuration values are different:" msgstr "" -#: ../../../CHANGELOG.md:4107 +#: ../../../CHANGELOG.md:4138 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:4108 +#: ../../../CHANGELOG.md:4139 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:4109 +#: ../../../CHANGELOG.md:4140 msgid "`authless_portals` (used to be `false`, now `true`) — creating portals from the Telegram side is now possible" msgstr "" -#: ../../../CHANGELOG.md:4110 +#: ../../../CHANGELOG.md:4141 msgid "`whitelist_group_admins` (used to be `false`, now `true`) — allows Telegram group admins to use the bot commands" msgstr "" -#: ../../../CHANGELOG.md:4112 +#: ../../../CHANGELOG.md:4143 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:4115 +#: ../../../CHANGELOG.md:4146 msgid "2019-06-12" msgstr "" -#: ../../../CHANGELOG.md:4117 +#: ../../../CHANGELOG.md:4148 msgid "Synapse v1.0" msgstr "" -#: ../../../CHANGELOG.md:4119 +#: ../../../CHANGELOG.md:4150 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:4121 +#: ../../../CHANGELOG.md:4152 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:4123 +#: ../../../CHANGELOG.md:4154 msgid "**Note**: don't confuse the `_matrix._tcp` and `_matrix-identity._tcp` DNS SRV records. The latter, **must not** be removed." msgstr "" -#: ../../../CHANGELOG.md:4125 +#: ../../../CHANGELOG.md:4156 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:4127 +#: ../../../CHANGELOG.md:4158 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:4130 +#: ../../../CHANGELOG.md:4161 msgid "2019-06-07" msgstr "" -#: ../../../CHANGELOG.md:4132 +#: ../../../CHANGELOG.md:4163 msgid "(BC Break) Facebook bridge configuration is now entirely managed by the playbook" msgstr "" -#: ../../../CHANGELOG.md:4134 +#: ../../../CHANGELOG.md:4165 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:4138 +#: ../../../CHANGELOG.md:4169 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:4140 +#: ../../../CHANGELOG.md:4171 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:4142 +#: ../../../CHANGELOG.md:4173 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:4145 +#: ../../../CHANGELOG.md:4176 msgid "2019-05-25" msgstr "" -#: ../../../CHANGELOG.md:4147 +#: ../../../CHANGELOG.md:4178 msgid "Support for exposing container ports publicly (not just to the host)" msgstr "" -#: ../../../CHANGELOG.md:4149 +#: ../../../CHANGELOG.md:4180 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:4151 +#: ../../../CHANGELOG.md:4182 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:4153 +#: ../../../CHANGELOG.md:4184 msgid "All such variables have been superseded by a better (more flexible) way to do it." msgstr "" -#: ../../../CHANGELOG.md:4155 +#: ../../../CHANGELOG.md:4186 msgid "**Most** people (including those not using `matrix-nginx-proxy`), **don't need** to bother with this." msgstr "" -#: ../../../CHANGELOG.md:4157 +#: ../../../CHANGELOG.md:4188 msgid "Porting examples follow for people having more customized setups:" msgstr "" -#: ../../../CHANGELOG.md:4159 +#: ../../../CHANGELOG.md:4190 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:4161 +#: ../../../CHANGELOG.md:4192 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:4163 +#: ../../../CHANGELOG.md:4194 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:4165 +#: ../../../CHANGELOG.md:4196 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:4167 +#: ../../../CHANGELOG.md:4198 msgid "**from** `matrix_mxisd_container_expose_port: true` **to** `matrix_mxisd_container_http_host_bind_port: '127.0.0.1:8090'`" msgstr "" -#: ../../../CHANGELOG.md:4169 +#: ../../../CHANGELOG.md:4200 msgid "**from** `matrix_dimension_container_expose_port: true` **to** `matrix_dimension_container_http_host_bind_port: '127.0.0.1:8184'`" msgstr "" -#: ../../../CHANGELOG.md:4171 +#: ../../../CHANGELOG.md:4202 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:4173 +#: ../../../CHANGELOG.md:4204 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:4175 +#: ../../../CHANGELOG.md:4206 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:4177 +#: ../../../CHANGELOG.md:4208 msgid "As always, if you forget to remove usage of some outdated variable, the playbook will warn you." msgstr "" -#: ../../../CHANGELOG.md:4180 +#: ../../../CHANGELOG.md:4211 msgid "2019-05-23" msgstr "" -#: ../../../CHANGELOG.md:4182 +#: ../../../CHANGELOG.md:4213 msgid "(BC Break) Ansible 2.8 compatibility" msgstr "" -#: ../../../CHANGELOG.md:4184 +#: ../../../CHANGELOG.md:4215 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:4186 +#: ../../../CHANGELOG.md:4217 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:4188 +#: ../../../CHANGELOG.md:4219 msgid "To avoid doing it manually, run this:" msgstr "" -#: ../../../CHANGELOG.md:4189 +#: ../../../CHANGELOG.md:4220 msgid "Linux: `sed -i 's/matrix-servers/matrix_servers/g' inventory/hosts`" msgstr "" -#: ../../../CHANGELOG.md:4190 +#: ../../../CHANGELOG.md:4221 msgid "Mac: `sed -i '' 's/matrix-servers/matrix_servers/g' inventory/hosts`" msgstr "" -#: ../../../CHANGELOG.md:4193 +#: ../../../CHANGELOG.md:4224 msgid "2019-05-21" msgstr "" -#: ../../../CHANGELOG.md:4195 +#: ../../../CHANGELOG.md:4226 msgid "Synapse no longer required" msgstr "" -#: ../../../CHANGELOG.md:4197 +#: ../../../CHANGELOG.md:4228 msgid "The playbook no longer insists on installing [Synapse](https://github.com/element-hq/synapse) via the `matrix-synapse` role." msgstr "" -#: ../../../CHANGELOG.md:4199 +#: ../../../CHANGELOG.md:4230 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:4201 +#: ../../../CHANGELOG.md:4232 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:4203 +#: ../../../CHANGELOG.md:4234 msgid "Having Synapse not be a required component potentially opens the door for installing alternative Matrix homeservers." msgstr "" -#: ../../../CHANGELOG.md:4205 +#: ../../../CHANGELOG.md:4236 msgid "Bridges are now separate from the Synapse role" msgstr "" -#: ../../../CHANGELOG.md:4207 +#: ../../../CHANGELOG.md:4238 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:4209 +#: ../../../CHANGELOG.md:4240 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:4211 +#: ../../../CHANGELOG.md:4242 msgid "Renaming inconsistently-named Synapse variables" msgstr "" -#: ../../../CHANGELOG.md:4213 +#: ../../../CHANGELOG.md:4244 msgid "For better consistency, the following variables have been renamed:" msgstr "" -#: ../../../CHANGELOG.md:4215 +#: ../../../CHANGELOG.md:4246 msgid "`matrix_enable_room_list_search` was renamed to `matrix_synapse_enable_room_list_search`" msgstr "" -#: ../../../CHANGELOG.md:4216 +#: ../../../CHANGELOG.md:4247 msgid "`matrix_alias_creation_rules` was renamed to `matrix_synapse_alias_creation_rules`" msgstr "" -#: ../../../CHANGELOG.md:4217 +#: ../../../CHANGELOG.md:4248 msgid "`matrix_nginx_proxy_matrix_room_list_publication_rulesdata_path` was renamed to `matrix_synapse_room_list_publication_rules`" msgstr "" -#: ../../../CHANGELOG.md:4220 +#: ../../../CHANGELOG.md:4251 msgid "2019-05-09" msgstr "" -#: ../../../CHANGELOG.md:4222 +#: ../../../CHANGELOG.md:4253 msgid "Besides a myriad of bug fixes and minor improvements, here are the more notable (bigger) features we can announce today." msgstr "" -#: ../../../CHANGELOG.md:4224 +#: ../../../CHANGELOG.md:4255 msgid "Mautrix Facebook/Messenger bridging support" msgstr "" -#: ../../../CHANGELOG.md:4226 +#: ../../../CHANGELOG.md:4257 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:4228 +#: ../../../CHANGELOG.md:4259 msgid "Additional details are available in [Setting up Mautrix Facebook bridging](docs/configuring-playbook-bridge-mautrix-facebook.md)." msgstr "" -#: ../../../CHANGELOG.md:4230 +#: ../../../CHANGELOG.md:4261 msgid "mxisd Registration feature integration" msgstr "" -#: ../../../CHANGELOG.md:4232 +#: ../../../CHANGELOG.md:4263 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:4234 +#: ../../../CHANGELOG.md:4265 msgid "Learn more in [mxisd-controlled Registration](docs/configuring-playbook-mxisd.md#mxisd-controlled-registration)." msgstr "" -#: ../../../CHANGELOG.md:4237 +#: ../../../CHANGELOG.md:4268 msgid "2019-04-16" msgstr "" -#: ../../../CHANGELOG.md:4239 +#: ../../../CHANGELOG.md:4270 msgid "Caddy webserver examples" msgstr "" -#: ../../../CHANGELOG.md:4241 +#: ../../../CHANGELOG.md:4272 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:4243 +#: ../../../CHANGELOG.md:4274 msgid "2019-04-10" msgstr "" -#: ../../../CHANGELOG.md:4245 +#: ../../../CHANGELOG.md:4276 msgid "Goofys support for other S3-compatible object stores" msgstr "" -#: ../../../CHANGELOG.md:4247 +#: ../../../CHANGELOG.md:4278 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:4250 +#: ../../../CHANGELOG.md:4281 msgid "2019-04-03" msgstr "" -#: ../../../CHANGELOG.md:4252 +#: ../../../CHANGELOG.md:4283 msgid "Ansible >= 2.5 is required" msgstr "" -#: ../../../CHANGELOG.md:4254 +#: ../../../CHANGELOG.md:4285 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:4256 +#: ../../../CHANGELOG.md:4287 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:4259 +#: ../../../CHANGELOG.md:4290 msgid "2019-03-19" msgstr "" -#: ../../../CHANGELOG.md:4261 +#: ../../../CHANGELOG.md:4292 msgid "TLS support for coturn" msgstr "" -#: ../../../CHANGELOG.md:4263 +#: ../../../CHANGELOG.md:4294 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:4265 +#: ../../../CHANGELOG.md:4296 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:4271 +#: ../../../CHANGELOG.md:4302 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:4273 +#: ../../../CHANGELOG.md:4304 msgid "People who build their own custom playbook from our roles should be aware that:" msgstr "" -#: ../../../CHANGELOG.md:4275 +#: ../../../CHANGELOG.md:4306 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:4277 +#: ../../../CHANGELOG.md:4308 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:4280 +#: ../../../CHANGELOG.md:4311 msgid "2019-03-12" msgstr "" -#: ../../../CHANGELOG.md:4282 +#: ../../../CHANGELOG.md:4313 msgid "matrix-nginx-proxy support for serving the base domain" msgstr "" -#: ../../../CHANGELOG.md:4284 +#: ../../../CHANGELOG.md:4315 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:4286 +#: ../../../CHANGELOG.md:4317 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:4288 +#: ../../../CHANGELOG.md:4319 msgid "(BC break) matrix-nginx-proxy data variable renamed" msgstr "" -#: ../../../CHANGELOG.md:4290 +#: ../../../CHANGELOG.md:4321 msgid "`matrix_nginx_proxy_data_path` was renamed to `matrix_nginx_proxy_base_path`." msgstr "" -#: ../../../CHANGELOG.md:4292 +#: ../../../CHANGELOG.md:4323 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:4295 +#: ../../../CHANGELOG.md:4326 msgid "2019-03-10" msgstr "" -#: ../../../CHANGELOG.md:4297 +#: ../../../CHANGELOG.md:4328 msgid "Dimension integration manager support" msgstr "" -#: ../../../CHANGELOG.md:4299 +#: ../../../CHANGELOG.md:4330 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:4302 +#: ../../../CHANGELOG.md:4333 msgid "2019-03-07" msgstr "" -#: ../../../CHANGELOG.md:4304 +#: ../../../CHANGELOG.md:4335 msgid "Ability to customize mxisd's email templates" msgstr "" -#: ../../../CHANGELOG.md:4306 +#: ../../../CHANGELOG.md:4337 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:4309 +#: ../../../CHANGELOG.md:4340 msgid "2019-03-05" msgstr "" -#: ../../../CHANGELOG.md:4311 +#: ../../../CHANGELOG.md:4342 msgid "Discord bridging support" msgstr "" -#: ../../../CHANGELOG.md:4313 +#: ../../../CHANGELOG.md:4344 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:4316 +#: ../../../CHANGELOG.md:4347 msgid "2019-02-19" msgstr "" -#: ../../../CHANGELOG.md:4318 +#: ../../../CHANGELOG.md:4349 msgid "Renaming variables" msgstr "" -#: ../../../CHANGELOG.md:4320 -#: ../../../CHANGELOG.md:4637 -#: ../../../CHANGELOG.md:4722 -#: ../../../CHANGELOG.md:4842 +#: ../../../CHANGELOG.md:4351 +#: ../../../CHANGELOG.md:4668 +#: ../../../CHANGELOG.md:4753 +#: ../../../CHANGELOG.md:4873 msgid "The following playbook variables were renamed:" msgstr "" -#: ../../../CHANGELOG.md:4322 +#: ../../../CHANGELOG.md:4353 msgid "from `host_specific_hostname_identity` to `matrix_domain`" msgstr "" -#: ../../../CHANGELOG.md:4323 +#: ../../../CHANGELOG.md:4354 msgid "from `hostname_identity` to `matrix_domain`" msgstr "" -#: ../../../CHANGELOG.md:4324 +#: ../../../CHANGELOG.md:4355 msgid "from `hostname_matrix` to `matrix_server_fqn_matrix`" msgstr "" -#: ../../../CHANGELOG.md:4325 +#: ../../../CHANGELOG.md:4356 msgid "from `hostname_riot` to `matrix_server_fqn_riot`" msgstr "" -#: ../../../CHANGELOG.md:4326 +#: ../../../CHANGELOG.md:4357 msgid "from `host_specific_matrix_ssl_lets_encrypt_support_email` to `matrix_ssl_lets_encrypt_support_email`" msgstr "" -#: ../../../CHANGELOG.md:4328 +#: ../../../CHANGELOG.md:4359 msgid "Doing that, we've simplified things, made names less confusing (hopefully) and moved all variable names under the `matrix_` prefix." msgstr "" -#: ../../../CHANGELOG.md:4331 +#: ../../../CHANGELOG.md:4362 msgid "2019-02-16" msgstr "" -#: ../../../CHANGELOG.md:4333 +#: ../../../CHANGELOG.md:4364 msgid "Riot v1.0.1 support" msgstr "" -#: ../../../CHANGELOG.md:4335 +#: ../../../CHANGELOG.md:4366 msgid "You can now use the brand new and redesigned Riot." msgstr "" -#: ../../../CHANGELOG.md:4337 +#: ../../../CHANGELOG.md:4368 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:4339 +#: ../../../CHANGELOG.md:4370 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:4342 +#: ../../../CHANGELOG.md:4373 msgid "2019-02-14" msgstr "" -#: ../../../CHANGELOG.md:4344 +#: ../../../CHANGELOG.md:4375 msgid "Synapse v0.99.1" msgstr "" -#: ../../../CHANGELOG.md:4346 +#: ../../../CHANGELOG.md:4377 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:4348 +#: ../../../CHANGELOG.md:4379 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:4351 +#: ../../../CHANGELOG.md:4382 msgid "2019-02-06" msgstr "" -#: ../../../CHANGELOG.md:4353 +#: ../../../CHANGELOG.md:4384 msgid "Synapse v0.99 support and preparation for Synapse v1.0" msgstr "" -#: ../../../CHANGELOG.md:4355 +#: ../../../CHANGELOG.md:4386 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:4357 +#: ../../../CHANGELOG.md:4388 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:4359 +#: ../../../CHANGELOG.md:4390 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:4361 +#: ../../../CHANGELOG.md:4392 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:4363 +#: ../../../CHANGELOG.md:4394 msgid "(recommended) set up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file), unless you are affected by the [Downsides of well-known-based Server Delegation](docs/howto-server-delegation.md#downsides-of-well-known-based-server-delegation). If you had previously set up the well-known `client` file, depending on how you've done it, it may be that there is nothing new required of you (besides [upgrading](docs/maintenance-upgrading-services.md)). After upgrading, you can [run a self-check](docs/maintenance-and-troubleshooting.md#how-to-check-if-services-work), which will tell you if you need to do anything extra with regard to setting up [Server Delegation via a well-known file](docs/howto-server-delegation.md#server-delegation-via-a-well-known-file). After some time, when most people have upgraded to Synapse v0.99 and older releases have disappeared, be prepared to drop your `_matrix._tcp` SRV record." msgstr "" -#: ../../../CHANGELOG.md:4365 +#: ../../../CHANGELOG.md:4396 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:4368 +#: ../../../CHANGELOG.md:4399 msgid "2019-02-01" msgstr "" -#: ../../../CHANGELOG.md:4370 +#: ../../../CHANGELOG.md:4401 msgid "TLS v1.3 support" msgstr "" -#: ../../../CHANGELOG.md:4372 +#: ../../../CHANGELOG.md:4403 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:4374 +#: ../../../CHANGELOG.md:4405 msgid "When using:" msgstr "" -#: ../../../CHANGELOG.md:4376 +#: ../../../CHANGELOG.md:4407 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:4378 +#: ../../../CHANGELOG.md:4409 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:4380 +#: ../../../CHANGELOG.md:4411 msgid "**another web server**: you don't need to do anything to accommodate this change" msgstr "" -#: ../../../CHANGELOG.md:4383 +#: ../../../CHANGELOG.md:4414 msgid "2019-01-31" msgstr "" -#: ../../../CHANGELOG.md:4385 +#: ../../../CHANGELOG.md:4416 msgid "IRC bridging support" msgstr "" -#: ../../../CHANGELOG.md:4387 +#: ../../../CHANGELOG.md:4418 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:4390 +#: ../../../CHANGELOG.md:4421 msgid "2019-01-29" msgstr "" -#: ../../../CHANGELOG.md:4392 +#: ../../../CHANGELOG.md:4423 msgid "Running container processes as non-root, without capabilities and read-only" msgstr "" -#: ../../../CHANGELOG.md:4394 +#: ../../../CHANGELOG.md:4425 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:4396 +#: ../../../CHANGELOG.md:4427 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:4398 +#: ../../../CHANGELOG.md:4429 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:4400 +#: ../../../CHANGELOG.md:4431 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:4402 +#: ../../../CHANGELOG.md:4433 msgid "matrix-mailer is now based on Exim, not Postfix" msgstr "" -#: ../../../CHANGELOG.md:4404 +#: ../../../CHANGELOG.md:4435 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:4406 +#: ../../../CHANGELOG.md:4437 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:4408 +#: ../../../CHANGELOG.md:4439 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:4411 +#: ../../../CHANGELOG.md:4442 msgid "2019-01-17" msgstr "" -#: ../../../CHANGELOG.md:4413 +#: ../../../CHANGELOG.md:4444 msgid "(BC Break) Making the playbook's roles more independent of one another" msgstr "" -#: ../../../CHANGELOG.md:4415 +#: ../../../CHANGELOG.md:4446 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:4418 +#: ../../../CHANGELOG.md:4449 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:4420 +#: ../../../CHANGELOG.md:4451 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:4422 +#: ../../../CHANGELOG.md:4453 msgid "In addition, the following components can now be completely disabled (for those who want/need to):" msgstr "" -#: ../../../CHANGELOG.md:4423 +#: ../../../CHANGELOG.md:4454 msgid "`matrix-coturn` by using `coturn_enabled: false`" msgstr "" -#: ../../../CHANGELOG.md:4424 +#: ../../../CHANGELOG.md:4455 msgid "`matrix-mailer` by using `matrix_mailer_enabled: false`" msgstr "" -#: ../../../CHANGELOG.md:4425 +#: ../../../CHANGELOG.md:4456 msgid "`matrix-postgres` by using `matrix_postgres_enabled: false`" msgstr "" -#: ../../../CHANGELOG.md:4427 +#: ../../../CHANGELOG.md:4458 msgid "The following changes had to be done:" msgstr "" -#: ../../../CHANGELOG.md:4429 +#: ../../../CHANGELOG.md:4460 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:4431 +#: ../../../CHANGELOG.md:4462 msgid "`matrix_postgres_use_external` has been superseded by the more consistently named `matrix_postgres_enabled` variable and a few other `matrix_synapse_database_` variables. See the [Using an external PostgreSQL server (optional)](docs/configuring-playbook-external-postgres.md) documentation page for an up-to-date replacement." msgstr "" -#: ../../../CHANGELOG.md:4433 +#: ../../../CHANGELOG.md:4464 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:4435 +#: ../../../CHANGELOG.md:4466 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:4438 +#: ../../../CHANGELOG.md:4469 msgid "2019-01-16" msgstr "" -#: ../../../CHANGELOG.md:4440 +#: ../../../CHANGELOG.md:4471 msgid "Splitting the playbook into multiple roles" msgstr "" -#: ../../../CHANGELOG.md:4442 +#: ../../../CHANGELOG.md:4473 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:4445 +#: ../../../CHANGELOG.md:4476 msgid "To keep the filesystem more consistent with this separation, the **Postgres data had to be relocated**." msgstr "" -#: ../../../CHANGELOG.md:4447 +#: ../../../CHANGELOG.md:4478 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:4450 +#: ../../../CHANGELOG.md:4481 msgid "2019-01-11" msgstr "" -#: ../../../CHANGELOG.md:4452 +#: ../../../CHANGELOG.md:4483 msgid "(BC Break) mxisd configuration changes" msgstr "" -#: ../../../CHANGELOG.md:4454 +#: ../../../CHANGELOG.md:4485 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:4457 +#: ../../../CHANGELOG.md:4488 msgid "The following variables are no longer supported by this playbook:" msgstr "" -#: ../../../CHANGELOG.md:4459 +#: ../../../CHANGELOG.md:4490 msgid "`matrix_mxisd_ldap_enabled`" msgstr "" -#: ../../../CHANGELOG.md:4460 +#: ../../../CHANGELOG.md:4491 msgid "`matrix_mxisd_ldap_connection_host`" msgstr "" -#: ../../../CHANGELOG.md:4461 +#: ../../../CHANGELOG.md:4492 msgid "`matrix_mxisd_ldap_connection_tls`" msgstr "" -#: ../../../CHANGELOG.md:4462 +#: ../../../CHANGELOG.md:4493 msgid "`matrix_mxisd_ldap_connection_port`" msgstr "" -#: ../../../CHANGELOG.md:4463 +#: ../../../CHANGELOG.md:4494 msgid "`matrix_mxisd_ldap_connection_baseDn`" msgstr "" -#: ../../../CHANGELOG.md:4464 +#: ../../../CHANGELOG.md:4495 msgid "`matrix_mxisd_ldap_connection_baseDns`" msgstr "" -#: ../../../CHANGELOG.md:4465 -#: ../../../CHANGELOG.md:4466 +#: ../../../CHANGELOG.md:4496 +#: ../../../CHANGELOG.md:4497 msgid "`matrix_mxisd_ldap_connection_bindDn`" msgstr "" -#: ../../../CHANGELOG.md:4467 -#: ../../../CHANGELOG.md:4471 +#: ../../../CHANGELOG.md:4498 +#: ../../../CHANGELOG.md:4502 msgid "`matrix_mxisd_ldap_connection_bindPassword`" msgstr "" -#: ../../../CHANGELOG.md:4468 +#: ../../../CHANGELOG.md:4499 msgid "`matrix_mxisd_ldap_filter`" msgstr "" -#: ../../../CHANGELOG.md:4469 +#: ../../../CHANGELOG.md:4500 msgid "`matrix_mxisd_ldap_attribute_uid_type`" msgstr "" -#: ../../../CHANGELOG.md:4470 +#: ../../../CHANGELOG.md:4501 msgid "`matrix_mxisd_ldap_attribute_uid_value`" msgstr "" -#: ../../../CHANGELOG.md:4472 +#: ../../../CHANGELOG.md:4503 msgid "`matrix_mxisd_ldap_attribute_name`" msgstr "" -#: ../../../CHANGELOG.md:4473 +#: ../../../CHANGELOG.md:4504 msgid "`matrix_mxisd_ldap_attribute_threepid_email`" msgstr "" -#: ../../../CHANGELOG.md:4474 +#: ../../../CHANGELOG.md:4505 msgid "`matrix_mxisd_ldap_attribute_threepid_msisdn`" msgstr "" -#: ../../../CHANGELOG.md:4475 +#: ../../../CHANGELOG.md:4506 msgid "`matrix_mxisd_ldap_identity_filter`" msgstr "" -#: ../../../CHANGELOG.md:4476 +#: ../../../CHANGELOG.md:4507 msgid "`matrix_mxisd_ldap_identity_medium`" msgstr "" -#: ../../../CHANGELOG.md:4477 +#: ../../../CHANGELOG.md:4508 msgid "`matrix_mxisd_ldap_auth_filter`" msgstr "" -#: ../../../CHANGELOG.md:4478 +#: ../../../CHANGELOG.md:4509 msgid "`matrix_mxisd_ldap_directory_filter`" msgstr "" -#: ../../../CHANGELOG.md:4479 +#: ../../../CHANGELOG.md:4510 msgid "`matrix_mxisd_template_config`" msgstr "" -#: ../../../CHANGELOG.md:4481 +#: ../../../CHANGELOG.md:4512 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:4483 +#: ../../../CHANGELOG.md:4514 msgid "This new way of configuring mxisd is beneficial because:" msgstr "" -#: ../../../CHANGELOG.md:4485 +#: ../../../CHANGELOG.md:4516 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:4486 +#: ../../../CHANGELOG.md:4517 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:4489 +#: ../../../CHANGELOG.md:4520 msgid "2019-01-08" msgstr "" -#: ../../../CHANGELOG.md:4491 +#: ../../../CHANGELOG.md:4522 msgid "(BC Break) Cronjob schedule no longer configurable" msgstr "" -#: ../../../CHANGELOG.md:4493 +#: ../../../CHANGELOG.md:4524 msgid "Due to the way we manage cronjobs now, you can no longer configure the schedule they're invoked at." msgstr "" -#: ../../../CHANGELOG.md:4495 +#: ../../../CHANGELOG.md:4526 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:4498 +#: ../../../CHANGELOG.md:4529 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:4501 +#: ../../../CHANGELOG.md:4532 msgid "2018-12-23" msgstr "" -#: ../../../CHANGELOG.md:4503 +#: ../../../CHANGELOG.md:4534 msgid "(BC Break) More SSL certificate retrieval methods" msgstr "" -#: ../../../CHANGELOG.md:4505 +#: ../../../CHANGELOG.md:4536 msgid "The playbook now lets you decide between 3 different SSL certificate retrieval methods:" msgstr "" -#: ../../../CHANGELOG.md:4506 +#: ../../../CHANGELOG.md:4537 msgid "(default) obtaining free SSL certificates from Let's Encrypt" msgstr "" -#: ../../../CHANGELOG.md:4507 +#: ../../../CHANGELOG.md:4538 msgid "generating self-signed SSL certificates" msgstr "" -#: ../../../CHANGELOG.md:4508 +#: ../../../CHANGELOG.md:4539 msgid "managing SSL certificates manually" msgstr "" -#: ../../../CHANGELOG.md:4510 +#: ../../../CHANGELOG.md:4541 msgid "Learn more in [Adjusting SSL certificate retrieval](docs/configuring-playbook-ssl-certificates.md)." msgstr "" -#: ../../../CHANGELOG.md:4512 +#: ../../../CHANGELOG.md:4543 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:4514 +#: ../../../CHANGELOG.md:4545 msgid "before: `host_specific_matrix_ssl_support_email`" msgstr "" -#: ../../../CHANGELOG.md:4515 +#: ../../../CHANGELOG.md:4546 msgid "after: `host_specific_matrix_ssl_lets_encrypt_support_email`" msgstr "" -#: ../../../CHANGELOG.md:4517 +#: ../../../CHANGELOG.md:4548 msgid "(BC Break) mxisd upgrade with multiple base DN support" msgstr "" -#: ../../../CHANGELOG.md:4519 +#: ../../../CHANGELOG.md:4550 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:4521 +#: ../../../CHANGELOG.md:4552 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:4523 +#: ../../../CHANGELOG.md:4554 msgid "Example change:" msgstr "" -#: ../../../CHANGELOG.md:4525 +#: ../../../CHANGELOG.md:4556 msgid "before: `matrix_mxisd_ldap_connection_baseDn: OU=Users,DC=example,DC=org`" msgstr "" -#: ../../../CHANGELOG.md:4526 +#: ../../../CHANGELOG.md:4557 msgid "after: `matrix_mxisd_ldap_connection_baseDns: ['OU=Users,DC=example,DC=org']`" msgstr "" -#: ../../../CHANGELOG.md:4529 +#: ../../../CHANGELOG.md:4560 msgid "2018-12-21" msgstr "" -#: ../../../CHANGELOG.md:4531 +#: ../../../CHANGELOG.md:4562 msgid "Synapse 0.34.0 and Python 3" msgstr "" -#: ../../../CHANGELOG.md:4533 +#: ../../../CHANGELOG.md:4564 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:4536 +#: ../../../CHANGELOG.md:4567 msgid "2018-12-12" msgstr "" -#: ../../../CHANGELOG.md:4538 +#: ../../../CHANGELOG.md:4569 msgid "Riot homepage customization" msgstr "" -#: ../../../CHANGELOG.md:4540 +#: ../../../CHANGELOG.md:4571 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:4543 +#: ../../../CHANGELOG.md:4574 msgid "2018-12-04" msgstr "" -#: ../../../CHANGELOG.md:4545 +#: ../../../CHANGELOG.md:4576 msgid "mxisd extensibility" msgstr "" -#: ../../../CHANGELOG.md:4547 +#: ../../../CHANGELOG.md:4578 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:4550 +#: ../../../CHANGELOG.md:4581 msgid "2018-11-28" msgstr "" -#: ../../../CHANGELOG.md:4552 +#: ../../../CHANGELOG.md:4583 msgid "More scripts" msgstr "" -#: ../../../CHANGELOG.md:4554 +#: ../../../CHANGELOG.md:4585 msgid "matrix-remove-all allows to uninstall everything with a single command" msgstr "" -#: ../../../CHANGELOG.md:4555 +#: ../../../CHANGELOG.md:4586 msgid "matrix-make-user-admin allows to upgrade a user's privileges" msgstr "" -#: ../../../CHANGELOG.md:4557 +#: ../../../CHANGELOG.md:4588 msgid "LDAP auth support via matrix-synapse-ldap3" msgstr "" -#: ../../../CHANGELOG.md:4559 +#: ../../../CHANGELOG.md:4590 msgid "The playbook can now install and configure [LDAP auth support](https://github.com/matrix-org/matrix-synapse-ldap3) for you." msgstr "" -#: ../../../CHANGELOG.md:4561 +#: ../../../CHANGELOG.md:4592 msgid "Additional details are available in [Setting up the LDAP authentication password provider module](docs/configuring-playbook-ldap-auth.md)." msgstr "" -#: ../../../CHANGELOG.md:4564 +#: ../../../CHANGELOG.md:4595 msgid "2018-11-23" msgstr "" -#: ../../../CHANGELOG.md:4566 +#: ../../../CHANGELOG.md:4597 msgid "Support for controlling public registration and room auto-join" msgstr "" -#: ../../../CHANGELOG.md:4568 +#: ../../../CHANGELOG.md:4599 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:4570 +#: ../../../CHANGELOG.md:4601 msgid "You can also make people automatically get auto-joined to rooms (controlled via `matrix_synapse_auto_join_rooms`)." msgstr "" -#: ../../../CHANGELOG.md:4572 +#: ../../../CHANGELOG.md:4603 msgid "Support for changing the welcome user ID (welcome bot)" msgstr "" -#: ../../../CHANGELOG.md:4574 +#: ../../../CHANGELOG.md:4605 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:4577 +#: ../../../CHANGELOG.md:4608 msgid "2018-11-14" msgstr "" -#: ../../../CHANGELOG.md:4579 +#: ../../../CHANGELOG.md:4610 msgid "Ability to set Synapse log levels" msgstr "" -#: ../../../CHANGELOG.md:4581 +#: ../../../CHANGELOG.md:4612 msgid "The playbook now allows you to set the log levels used by Synapse. The default logging levels remain the same." msgstr "" -#: ../../../CHANGELOG.md:4583 +#: ../../../CHANGELOG.md:4614 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:4592 +#: ../../../CHANGELOG.md:4623 msgid "2018-11-03" msgstr "" -#: ../../../CHANGELOG.md:4594 +#: ../../../CHANGELOG.md:4625 msgid "Customize parts of Riot's config" msgstr "" -#: ../../../CHANGELOG.md:4596 +#: ../../../CHANGELOG.md:4627 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:4607 +#: ../../../CHANGELOG.md:4638 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:4616 +#: ../../../CHANGELOG.md:4647 msgid "SSL protocols used to serve Riot and Synapse" msgstr "" -#: ../../../CHANGELOG.md:4618 +#: ../../../CHANGELOG.md:4649 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:4620 +#: ../../../CHANGELOG.md:4651 msgid "You may wish to re-enable TLSv1 if you need to access Riot in older browsers." msgstr "" -#: ../../../CHANGELOG.md:4622 +#: ../../../CHANGELOG.md:4653 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:4625 +#: ../../../CHANGELOG.md:4656 msgid "2018-11-01" msgstr "" -#: ../../../CHANGELOG.md:4627 +#: ../../../CHANGELOG.md:4658 msgid "Postgres 11 support" msgstr "" -#: ../../../CHANGELOG.md:4629 +#: ../../../CHANGELOG.md:4660 msgid "The playbook now installs [Postgres 11](https://www.postgresql.org/about/news/1894/) by default." msgstr "" -#: ../../../CHANGELOG.md:4631 +#: ../../../CHANGELOG.md:4662 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:4633 -#: ../../../CHANGELOG.md:4720 -#: ../../../CHANGELOG.md:4840 +#: ../../../CHANGELOG.md:4664 +#: ../../../CHANGELOG.md:4751 +#: ../../../CHANGELOG.md:4871 msgid "(BC Break) Renaming playbook variables" msgstr "" -#: ../../../CHANGELOG.md:4635 +#: ../../../CHANGELOG.md:4666 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:4639 +#: ../../../CHANGELOG.md:4670 msgid "from `matrix_docker_image_mxisd` to `matrix_mxisd_docker_image`" msgstr "" -#: ../../../CHANGELOG.md:4640 +#: ../../../CHANGELOG.md:4671 msgid "from `matrix_docker_image_mautrix_telegram` to `matrix_mautrix_telegram_docker_image`" msgstr "" -#: ../../../CHANGELOG.md:4641 +#: ../../../CHANGELOG.md:4672 msgid "from `matrix_docker_image_mautrix_whatsapp` to `matrix_mautrix_whatsapp_docker_image`" msgstr "" -#: ../../../CHANGELOG.md:4642 +#: ../../../CHANGELOG.md:4673 msgid "from `matrix_docker_image_mailer` to `matrix_mailer_docker_image`" msgstr "" -#: ../../../CHANGELOG.md:4643 +#: ../../../CHANGELOG.md:4674 msgid "from `matrix_docker_image_coturn` to `coturn_container_image`" msgstr "" -#: ../../../CHANGELOG.md:4644 +#: ../../../CHANGELOG.md:4675 msgid "from `matrix_docker_image_goofys` to `matrix_s3_goofys_docker_image`" msgstr "" -#: ../../../CHANGELOG.md:4645 +#: ../../../CHANGELOG.md:4676 msgid "from `matrix_docker_image_riot` to `matrix_riot_web_docker_image`" msgstr "" -#: ../../../CHANGELOG.md:4646 +#: ../../../CHANGELOG.md:4677 msgid "from `matrix_docker_image_nginx` to `matrix_nginx_proxy_docker_image`" msgstr "" -#: ../../../CHANGELOG.md:4647 +#: ../../../CHANGELOG.md:4678 msgid "from `matrix_docker_image_synapse` to `matrix_synapse_docker_image`" msgstr "" -#: ../../../CHANGELOG.md:4648 +#: ../../../CHANGELOG.md:4679 msgid "from `matrix_docker_image_postgres_v9` to `matrix_postgres_docker_image_v9`" msgstr "" -#: ../../../CHANGELOG.md:4649 +#: ../../../CHANGELOG.md:4680 msgid "from `matrix_docker_image_postgres_v10` to `matrix_postgres_docker_image_v10`" msgstr "" -#: ../../../CHANGELOG.md:4650 +#: ../../../CHANGELOG.md:4681 msgid "from `matrix_docker_image_postgres_latest` to `matrix_postgres_docker_image_latest`" msgstr "" -#: ../../../CHANGELOG.md:4653 +#: ../../../CHANGELOG.md:4684 msgid "2018-10-26" msgstr "" -#: ../../../CHANGELOG.md:4655 +#: ../../../CHANGELOG.md:4686 msgid "Mautrix Whatsapp bridging support" msgstr "" -#: ../../../CHANGELOG.md:4657 +#: ../../../CHANGELOG.md:4688 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:4659 +#: ../../../CHANGELOG.md:4690 msgid "Additional details are available in [Setting up Mautrix Whatsapp bridging](docs/configuring-playbook-bridge-mautrix-whatsapp.md)." msgstr "" -#: ../../../CHANGELOG.md:4662 +#: ../../../CHANGELOG.md:4693 msgid "2018-10-25" msgstr "" -#: ../../../CHANGELOG.md:4664 +#: ../../../CHANGELOG.md:4695 msgid "Support for controlling Matrix federation" msgstr "" -#: ../../../CHANGELOG.md:4666 +#: ../../../CHANGELOG.md:4697 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:4669 +#: ../../../CHANGELOG.md:4700 msgid "2018-10-24" msgstr "" -#: ../../../CHANGELOG.md:4671 +#: ../../../CHANGELOG.md:4702 msgid "Disabling riot-web guests" msgstr "" -#: ../../../CHANGELOG.md:4673 +#: ../../../CHANGELOG.md:4704 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:4676 +#: ../../../CHANGELOG.md:4707 msgid "2018-10-21" msgstr "" -#: ../../../CHANGELOG.md:4678 +#: ../../../CHANGELOG.md:4709 msgid "Self-check maintenance command" msgstr "" -#: ../../../CHANGELOG.md:4680 +#: ../../../CHANGELOG.md:4711 msgid "The playbook can now [check if services are configured correctly](docs/maintenance-and-troubleshooting.md#how-to-check-if-services-work)." msgstr "" -#: ../../../CHANGELOG.md:4683 +#: ../../../CHANGELOG.md:4714 msgid "2018-10-05" msgstr "" -#: ../../../CHANGELOG.md:4685 +#: ../../../CHANGELOG.md:4716 msgid "Presence tracking made configurable" msgstr "" -#: ../../../CHANGELOG.md:4687 +#: ../../../CHANGELOG.md:4718 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:4689 +#: ../../../CHANGELOG.md:4720 msgid "If users participate in large rooms with many other servers, disabling presence will decrease server load significantly." msgstr "" -#: ../../../CHANGELOG.md:4692 +#: ../../../CHANGELOG.md:4723 msgid "2018-09-27" msgstr "" -#: ../../../CHANGELOG.md:4694 +#: ../../../CHANGELOG.md:4725 msgid "Synapse Cache Factor made configurable" msgstr "" -#: ../../../CHANGELOG.md:4696 +#: ../../../CHANGELOG.md:4727 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:4698 +#: ../../../CHANGELOG.md:4729 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:4701 +#: ../../../CHANGELOG.md:4732 msgid "2018-09-26" msgstr "" -#: ../../../CHANGELOG.md:4703 +#: ../../../CHANGELOG.md:4734 msgid "Disabling Docker container logging" msgstr "" -#: ../../../CHANGELOG.md:4705 +#: ../../../CHANGELOG.md:4736 msgid "`--log-driver=none` is used for all Docker containers now." msgstr "" -#: ../../../CHANGELOG.md:4707 +#: ../../../CHANGELOG.md:4738 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:4709 +#: ../../../CHANGELOG.md:4740 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:4712 +#: ../../../CHANGELOG.md:4743 msgid "2018-09-17" msgstr "" -#: ../../../CHANGELOG.md:4714 +#: ../../../CHANGELOG.md:4745 msgid "Service discovery support" msgstr "" -#: ../../../CHANGELOG.md:4716 +#: ../../../CHANGELOG.md:4747 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:4718 +#: ../../../CHANGELOG.md:4749 msgid "Additional details are available in [Configuring service discovery via .well-known](docs/configuring-well-known.md)." msgstr "" -#: ../../../CHANGELOG.md:4724 +#: ../../../CHANGELOG.md:4755 msgid "from `matrix_nginx_riot_web_data_path` to `matrix_riot_web_data_path`" msgstr "" -#: ../../../CHANGELOG.md:4725 +#: ../../../CHANGELOG.md:4756 msgid "from `matrix_riot_web_default_identity_server_url` to `matrix_identity_server_url`" msgstr "" -#: ../../../CHANGELOG.md:4728 +#: ../../../CHANGELOG.md:4759 msgid "2018-09-07" msgstr "" -#: ../../../CHANGELOG.md:4730 +#: ../../../CHANGELOG.md:4761 msgid "Mautrix Telegram bridging support" msgstr "" -#: ../../../CHANGELOG.md:4732 +#: ../../../CHANGELOG.md:4763 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:4734 +#: ../../../CHANGELOG.md:4765 msgid "Additional details are available in [Setting up Mautrix Telegram bridging](docs/configuring-playbook-bridge-mautrix-telegram.md)." msgstr "" -#: ../../../CHANGELOG.md:4736 +#: ../../../CHANGELOG.md:4767 msgid "Events cache size increase and configurability for Matrix Synapse" msgstr "" -#: ../../../CHANGELOG.md:4738 +#: ../../../CHANGELOG.md:4769 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:4740 +#: ../../../CHANGELOG.md:4771 msgid "Previously, this value was hardcoded to `\"10K\"`. From now on, a more reasonable default of `\"100K\"` is used." msgstr "" -#: ../../../CHANGELOG.md:4742 +#: ../../../CHANGELOG.md:4773 msgid "Password-peppering support for Matrix Synapse" msgstr "" -#: ../../../CHANGELOG.md:4744 +#: ../../../CHANGELOG.md:4775 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:4746 +#: ../../../CHANGELOG.md:4777 msgid "Statistics-reporting support for Matrix Synapse" msgstr "" -#: ../../../CHANGELOG.md:4748 +#: ../../../CHANGELOG.md:4779 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:4750 +#: ../../../CHANGELOG.md:4781 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:4753 +#: ../../../CHANGELOG.md:4784 msgid "2018-08-29" msgstr "" -#: ../../../CHANGELOG.md:4755 +#: ../../../CHANGELOG.md:4786 msgid "Changing the way SSL certificates are retrieved" msgstr "" -#: ../../../CHANGELOG.md:4757 +#: ../../../CHANGELOG.md:4788 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:4759 +#: ../../../CHANGELOG.md:4790 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:4761 +#: ../../../CHANGELOG.md:4792 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:4763 +#: ../../../CHANGELOG.md:4794 msgid "`systemctl stop 'matrix*'`" msgstr "" -#: ../../../CHANGELOG.md:4764 +#: ../../../CHANGELOG.md:4795 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:4765 +#: ../../../CHANGELOG.md:4796 msgid "`mv /matrix/ssl /matrix/ssl-acmetool-delete-later`" msgstr "" -#: ../../../CHANGELOG.md:4766 +#: ../../../CHANGELOG.md:4797 msgid "re-run the playbook's [installation](docs/installing.md)" msgstr "" -#: ../../../CHANGELOG.md:4767 +#: ../../../CHANGELOG.md:4798 msgid "possibly delete `/matrix/ssl-acmetool-delete-later`" msgstr "" -#: ../../../CHANGELOG.md:4770 +#: ../../../CHANGELOG.md:4801 msgid "2018-08-21" msgstr "" -#: ../../../CHANGELOG.md:4772 +#: ../../../CHANGELOG.md:4803 msgid "Matrix Corporal support" msgstr "" -#: ../../../CHANGELOG.md:4774 +#: ../../../CHANGELOG.md:4805 msgid "The playbook can now install and configure [matrix-corporal](https://github.com/devture/matrix-corporal) for you." msgstr "" -#: ../../../CHANGELOG.md:4776 +#: ../../../CHANGELOG.md:4807 msgid "Additional details are available in [Setting up Matrix Corporal](docs/configuring-playbook-matrix-corporal.md)." msgstr "" -#: ../../../CHANGELOG.md:4779 +#: ../../../CHANGELOG.md:4810 msgid "2018-08-20" msgstr "" -#: ../../../CHANGELOG.md:4781 +#: ../../../CHANGELOG.md:4812 msgid "Matrix Synapse rate limit control variables" msgstr "" -#: ../../../CHANGELOG.md:4783 +#: ../../../CHANGELOG.md:4814 msgid "The following new variables can now be configured to control Matrix Synapse's rate-limiting (default values are shown below)." msgstr "" -#: ../../../CHANGELOG.md:4790 +#: ../../../CHANGELOG.md:4821 msgid "Shared Secret Auth support via matrix-synapse-shared-secret-auth" msgstr "" -#: ../../../CHANGELOG.md:4792 +#: ../../../CHANGELOG.md:4823 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:4794 +#: ../../../CHANGELOG.md:4825 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:4797 +#: ../../../CHANGELOG.md:4828 msgid "2018-08-17" msgstr "" -#: ../../../CHANGELOG.md:4799 +#: ../../../CHANGELOG.md:4830 msgid "REST auth support via matrix-synapse-rest-auth" msgstr "" -#: ../../../CHANGELOG.md:4801 +#: ../../../CHANGELOG.md:4832 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:4803 +#: ../../../CHANGELOG.md:4834 msgid "Additional details are available in [Setting up the REST authentication password provider module](docs/configuring-playbook-rest-auth.md)." msgstr "" -#: ../../../CHANGELOG.md:4805 +#: ../../../CHANGELOG.md:4836 msgid "Compression improvements" msgstr "" -#: ../../../CHANGELOG.md:4807 +#: ../../../CHANGELOG.md:4838 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:4810 +#: ../../../CHANGELOG.md:4841 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:4813 +#: ../../../CHANGELOG.md:4844 msgid "Disabling some unnecessary Synapse services" msgstr "" -#: ../../../CHANGELOG.md:4815 +#: ../../../CHANGELOG.md:4846 msgid "The following services are not necessary, so they have been disabled:" msgstr "" -#: ../../../CHANGELOG.md:4816 +#: ../../../CHANGELOG.md:4847 msgid "on the federation port (8448): the `client` service" msgstr "" -#: ../../../CHANGELOG.md:4817 +#: ../../../CHANGELOG.md:4848 msgid "on the http port (8008, exposed over 443): the old Angular `webclient` and the `federation` service" msgstr "" -#: ../../../CHANGELOG.md:4819 +#: ../../../CHANGELOG.md:4850 msgid "Federation runs only on the federation port (8448) now. The Client APIs run only on the http port (8008) now." msgstr "" -#: ../../../CHANGELOG.md:4822 +#: ../../../CHANGELOG.md:4853 msgid "2018-08-15" msgstr "" -#: ../../../CHANGELOG.md:4824 +#: ../../../CHANGELOG.md:4855 msgid "mxisd Identity Server support" msgstr "" -#: ../../../CHANGELOG.md:4826 +#: ../../../CHANGELOG.md:4857 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:4829 +#: ../../../CHANGELOG.md:4860 msgid "2018-08-14" msgstr "" -#: ../../../CHANGELOG.md:4831 +#: ../../../CHANGELOG.md:4862 msgid "Email-sending support" msgstr "" -#: ../../../CHANGELOG.md:4833 +#: ../../../CHANGELOG.md:4864 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:4835 +#: ../../../CHANGELOG.md:4866 msgid "With this, Matrix Synapse is able to send email notifications for missed messages, etc." msgstr "" -#: ../../../CHANGELOG.md:4838 +#: ../../../CHANGELOG.md:4869 msgid "2018-08-08" msgstr "" -#: ../../../CHANGELOG.md:4844 +#: ../../../CHANGELOG.md:4875 msgid "from `matrix_max_upload_size_mb` to `matrix_synapse_max_upload_size_mb`" msgstr "" -#: ../../../CHANGELOG.md:4845 +#: ../../../CHANGELOG.md:4876 msgid "from `matrix_max_log_file_size_mb` to `matrix_synapse_max_log_file_size_mb`" msgstr "" -#: ../../../CHANGELOG.md:4846 +#: ../../../CHANGELOG.md:4877 msgid "from `matrix_max_log_files_count` to `matrix_synapse_max_log_files_count`" msgstr "" -#: ../../../CHANGELOG.md:4847 +#: ../../../CHANGELOG.md:4878 msgid "from `docker_matrix_image` to `matrix_docker_image_synapse`" msgstr "" -#: ../../../CHANGELOG.md:4848 +#: ../../../CHANGELOG.md:4879 msgid "from `docker_nginx_image` to `matrix_docker_image_nginx`" msgstr "" -#: ../../../CHANGELOG.md:4849 +#: ../../../CHANGELOG.md:4880 msgid "from `docker_riot_image` to `matrix_docker_image_riot`" msgstr "" -#: ../../../CHANGELOG.md:4850 +#: ../../../CHANGELOG.md:4881 msgid "from `docker_goofys_image` to `matrix_docker_image_goofys`" msgstr "" -#: ../../../CHANGELOG.md:4851 +#: ../../../CHANGELOG.md:4882 msgid "from `docker_coturn_image` to `matrix_docker_image_coturn`" msgstr "" -#: ../../../CHANGELOG.md:4853 +#: ../../../CHANGELOG.md:4884 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:4855 +#: ../../../CHANGELOG.md:4886 msgid "Renaming Ansible playbook tag" msgstr "" -#: ../../../CHANGELOG.md:4857 +#: ../../../CHANGELOG.md:4888 msgid "The command for executing the whole playbook has changed. The `setup-main` tag got renamed to `setup-all`." msgstr "" -#: ../../../CHANGELOG.md:4859 +#: ../../../CHANGELOG.md:4890 msgid "Docker container linking" msgstr "" -#: ../../../CHANGELOG.md:4861 +#: ../../../CHANGELOG.md:4892 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 index afd1debf4..28f4ee198 100644 --- a/i18n/translation-templates/README.pot +++ b/i18n/translation-templates/README.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-01 17:14+0000\n" +"POT-Creation-Date: 2026-08-13 05:03+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -900,6 +900,18 @@ msgstr "" msgid "[Link](docs/configuring-playbook-bot-draupnir.md) (for [appservice mode](docs/configuring-playbook-appservice-draupnir-for-all.md))" msgstr "" +#: ../../../README.md:0 +msgid "[Meowlnir](https://github.com/maunium/meowlnir)" +msgstr "" + +#: ../../../README.md:0 +msgid "Moderation tool for Matrix, running in appservice mode" +msgstr "" + +#: ../../../README.md:0 +msgid "[Link](docs/configuring-playbook-bot-meowlnir.md)" +msgstr "" + #: ../../../README.md:0 msgid "[Buscarron](https://github.com/etkecc/buscarron)" msgstr "" @@ -912,11 +924,11 @@ msgstr "" msgid "[Link](docs/configuring-playbook-bot-buscarron.md)" msgstr "" -#: ../../../README.md:156 +#: ../../../README.md:157 msgid "Administration" msgstr "" -#: ../../../README.md:158 +#: ../../../README.md:159 msgid "Services that help you in administrating and monitoring your Matrix installation." msgstr "" @@ -1004,11 +1016,11 @@ msgstr "" msgid "[Link](docs/configuring-playbook-synapse-usage-exporter.md)" msgstr "" -#: ../../../README.md:170 +#: ../../../README.md:171 msgid "Misc" msgstr "" -#: ../../../README.md:172 +#: ../../../README.md:173 msgid "Various services that don't fit any other categories." msgstr "" @@ -1132,54 +1144,54 @@ msgstr "" msgid "[Link](docs/configuring-playbook-element-call.md)" msgstr "" -#: ../../../README.md:187 +#: ../../../README.md:188 msgid "🆕 Changes" msgstr "" -#: ../../../README.md:189 +#: ../../../README.md:190 msgid "This playbook evolves over time, sometimes with backward-incompatible changes." msgstr "" -#: ../../../README.md:191 +#: ../../../README.md:192 msgid "When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up with what's new." msgstr "" -#: ../../../README.md:193 +#: ../../../README.md:194 msgid "🆘 Support" msgstr "" -#: ../../../README.md:195 +#: ../../../README.md:196 msgid "Matrix room: [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)" msgstr "" -#: ../../../README.md:197 +#: ../../../README.md:198 msgid "IRC channel: `#matrix-docker-ansible-deploy` on the [Libera Chat](https://libera.chat/) IRC network (irc.libera.chat:6697)" msgstr "" -#: ../../../README.md:199 +#: ../../../README.md:200 msgid "GitHub issues: [spantaleev/matrix-docker-ansible-deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues)" msgstr "" -#: ../../../README.md:201 +#: ../../../README.md:202 msgid "🌐 Translation" msgstr "" -#: ../../../README.md:203 +#: ../../../README.md:204 msgid "See the [i18n/README.md](i18n/README.md) file for more information about translation." msgstr "" -#: ../../../README.md:205 +#: ../../../README.md:206 msgid "Translations are still work in progress." msgstr "" -#: ../../../README.md:207 +#: ../../../README.md:208 msgid "🤝 Related" msgstr "" -#: ../../../README.md:209 +#: ../../../README.md:210 msgid "You may also be interested in [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) - another Ansible playbook for self-hosting non-Matrix services (see its [List of supported services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md))." msgstr "" -#: ../../../README.md:211 +#: ../../../README.md:212 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/docs/configuring-playbook-bot-draupnir.pot b/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot index 393716606..5c747eb71 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.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-19 07:40+0000\n" +"POT-Creation-Date: 2026-08-13 05:03+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -33,470 +33,474 @@ msgid "This documentation page is about installing Draupnir in bot mode. As an a msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:19 -msgid "If your migrating from [Mjolnir](configuring-playbook-bot-mjolnir.md), skip to [this section](#migrating-from-mjolnir-only-required-if-migrating)." +msgid "**Note**: you can also use the [Meowlnir](configuring-playbook-bot-meowlnir.md) or [Mjolnir](configuring-playbook-bot-mjolnir.md) bots, which speak the same [policy list](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists) protocol." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:21 -msgid "Prerequisites" +msgid "When migrating from [Mjolnir](configuring-playbook-bot-mjolnir.md), skip to [this section](#migrating-from-mjolnir-only-required-if-migrating)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:23 -msgid "Prerequisites for Zero Touch Deployment (recommended)" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:25 -msgid "As of Draupnir 3.1.0, Zero Touch Deployment of Draupnir bot mode requires you to supply the following:" +msgid "Prerequisites for Zero Touch Deployment (recommended)" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:27 -msgid "MXID of the first person who gets invited to the management room that the bot creates for you." -msgstr "" - -#: ../../../docs/configuring-playbook-bot-draupnir.md:28 -msgid "A permanent access token for authentication. Instructions for obtaining one can be found at [obtain an access token via curl](obtaining-access-tokens.md#obtain-an-access-token-via-curl)." +msgid "As of Draupnir 3.1.0, Zero Touch Deployment of Draupnir bot mode requires you to supply the following:" msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:29 -msgid "A user account for Draupnir." +msgid "MXID of the first person who gets invited to the management room that the bot creates for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:30 +msgid "A permanent access token for authentication. Instructions for obtaining one can be found at [obtain an access token via curl](obtaining-access-tokens.md#obtain-an-access-token-via-curl)." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:31 -msgid "Zero Touch Deployment is the officially preferred installation method for new deployments of Draupnir as of 3.1.0." +msgid "A user account for Draupnir." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:33 -msgid "Create a management room (optional)" +msgid "Zero Touch Deployment is the officially preferred installation method for new deployments of Draupnir as of 3.1.0." msgstr "" #: ../../../docs/configuring-playbook-bot-draupnir.md:35 +msgid "Create a management room (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-draupnir.md:37 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." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:38 +#: ../../../docs/configuring-playbook-bot-draupnir.md:40 msgid "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:40 +#: ../../../docs/configuring-playbook-bot-draupnir.md:42 msgid "It is possible to make the management room encrypted (E2EE). If doing so, then you need to enable the native E2EE support (see [below](#native-e2ee-support))." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:42 +#: ../../../docs/configuring-playbook-bot-draupnir.md:44 msgid "E2EE support for the management room is mutually exclusive with Zero Touch Deployment of Draupnir." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:44 +#: ../../../docs/configuring-playbook-bot-draupnir.md:46 msgid "Once you have created the room you need to copy the room ID so you can specify it on your `inventory/host_vars/matrix.example.com/vars.yml` file. In Element Web you can check the ID by going to the room's settings and clicking \"Advanced\". The room ID will look something like `!qporfwt:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:46 +#: ../../../docs/configuring-playbook-bot-draupnir.md:48 msgid "End-to-End Encryption support" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:48 +#: ../../../docs/configuring-playbook-bot-draupnir.md:50 msgid "Decide whether you want to support having an encrypted management room or not. Draupnir can still protect encrypted rooms without encryption support enabled." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:50 +#: ../../../docs/configuring-playbook-bot-draupnir.md:52 msgid "Refer to Draupnir's [documentation](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#protecting-encrypted-rooms) for more details about why you might want to care about encryption support for protected rooms." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:52 +#: ../../../docs/configuring-playbook-bot-draupnir.md:54 msgid "Disable Pantalaimon for Draupnir (since v2.0.0; optional)" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:54 +#: ../../../docs/configuring-playbook-bot-draupnir.md:56 msgid "It is known that running Draupnir along with Pantalaimon breaks all workflows that involve answering prompts with reactions." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:56 +#: ../../../docs/configuring-playbook-bot-draupnir.md:58 msgid "If you are updating Draupnir from v1.x.x and have enabled Pantalaimon for it, you can disable Pantalaimon in favor of the native E2EE support. To disable Pantalaimon, remove the configuration `matrix_bot_draupnir_pantalaimon_use: true` from your `vars.yml` file." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:58 +#: ../../../docs/configuring-playbook-bot-draupnir.md:60 msgid "**Note**: because the management room is still encrypted, disabling it without enabling the native E2EE support will break the management room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:60 +#: ../../../docs/configuring-playbook-bot-draupnir.md:62 msgid "Native E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:62 +#: ../../../docs/configuring-playbook-bot-draupnir.md:64 msgid "To enable the native E2EE support, you need to obtain an access token for Draupnir and set it on your `vars.yml` file." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:64 +#: ../../../docs/configuring-playbook-bot-draupnir.md:66 msgid "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)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:66 +#: ../../../docs/configuring-playbook-bot-draupnir.md:68 msgid "To enable the native E2EE support, add the following configuration to your `vars.yml` file. Make sure to replace `CLEAN_ACCESS_TOKEN_HERE` with the access token you obtained just now." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:77 +#: ../../../docs/configuring-playbook-bot-draupnir.md:79 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:79 +#: ../../../docs/configuring-playbook-bot-draupnir.md:81 msgid "Configuration for Zero Touch Deployment (recommended)" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:81 +#: ../../../docs/configuring-playbook-bot-draupnir.md:83 msgid "To enable the bot using Zero Touch Deployment, add the following configuration to your `vars.yml` file. Make sure to replace `INITIAL_MANAGER_MXID_HERE` with the MXID of the user who should be invited to the management room first, and `CLEAN_ACCESS_TOKEN_HERE` with the access token you obtained." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:95 +#: ../../../docs/configuring-playbook-bot-draupnir.md:97 msgid "Configuration without Zero Touch Deployment" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:97 +#: ../../../docs/configuring-playbook-bot-draupnir.md:99 msgid "If you'd prefer to have the bot manage its own login at the cost of having to create the management room manually, you can use native login with the configuration block below. Make sure to replace `MANAGEMENT_ROOM_ID_HERE` with the ID of the management room you have created earlier." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:116 +#: ../../../docs/configuring-playbook-bot-draupnir.md:118 msgid "Running both bot mode and appservice mode" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:118 +#: ../../../docs/configuring-playbook-bot-draupnir.md:120 msgid "When running both bot mode and [appservice mode (Draupnir for all)](./configuring-playbook-appservice-draupnir-for-all.md), the playbook will force-restart the bot if running a non-release tag like `latest` or `main` or a development build. This is due to the conditional restart logic not being able to reliably tell when an update happened." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:122 +#: ../../../docs/configuring-playbook-bot-draupnir.md:124 msgid "Conditional restarts work correctly for all tags when running only one of these two operating modes." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:124 +#: ../../../docs/configuring-playbook-bot-draupnir.md:126 msgid "Create and invite the bot to the management room (only when using native login without Zero Touch Deployment)" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:126 +#: ../../../docs/configuring-playbook-bot-draupnir.md:128 msgid "Before proceeding to the next step, run the playbook with the following command to create the bot user." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:132 +#: ../../../docs/configuring-playbook-bot-draupnir.md:134 msgid "**Note**: the `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:134 +#: ../../../docs/configuring-playbook-bot-draupnir.md:136 msgid "Then, invite the bot (`@bot.draupnir:example.com`) to its management room which you have created earlier." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:136 +#: ../../../docs/configuring-playbook-bot-draupnir.md:138 msgid "Creating a user account for the bot (when using Zero Touch Deployment)" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:138 +#: ../../../docs/configuring-playbook-bot-draupnir.md:140 msgid "Since Zero Touch Deployment is not validated with native login, you will need to create the user account manually." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:140 +#: ../../../docs/configuring-playbook-bot-draupnir.md:142 msgid "Refer to [registering users](registering-users.md) for documentation on how to configure the user account." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:142 +#: ../../../docs/configuring-playbook-bot-draupnir.md:144 msgid "Make sure the account is free from rate limiting (optional, recommended)" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:144 +#: ../../../docs/configuring-playbook-bot-draupnir.md:146 msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a highly recommended step. If you do not configure it, Draupnir performance will be degraded.**" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:146 +#: ../../../docs/configuring-playbook-bot-draupnir.md:148 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:148 +#: ../../../docs/configuring-playbook-bot-draupnir.md:150 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:150 +#: ../../../docs/configuring-playbook-bot-draupnir.md:152 msgid "The APIs can also be accessed via [Ketesa](https://github.com/etkecc/ketesa), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Ketesa for you. For details about it, see [this page](configuring-playbook-ketesa.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:152 +#: ../../../docs/configuring-playbook-bot-draupnir.md:154 msgid "Add the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:154 +#: ../../../docs/configuring-playbook-bot-draupnir.md:156 msgid "This is automatically done if Ketesa is enabled. Otherwise, to expose the APIs publicly, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:160 +#: ../../../docs/configuring-playbook-bot-draupnir.md:162 msgid "Obtain an access token for admin account" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:162 +#: ../../../docs/configuring-playbook-bot-draupnir.md:164 msgid "Manual access to Synapse's Admin APIs requires an access token for a homeserver admin account. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:165 +#: ../../../docs/configuring-playbook-bot-draupnir.md:167 msgid "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:167 +#: ../../../docs/configuring-playbook-bot-draupnir.md:169 msgid "Run the `curl` command" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:169 +#: ../../../docs/configuring-playbook-bot-draupnir.md:171 msgid "To disable rate limiting, run the following command on systems that ship curl. Before running it, make sure to replace:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:171 +#: ../../../docs/configuring-playbook-bot-draupnir.md:173 msgid "`ADMIN_ACCESS_TOKEN_HERE` with the access token of the admin account" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:172 +#: ../../../docs/configuring-playbook-bot-draupnir.md:174 msgid "`example.com` with your base domain" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:173 +#: ../../../docs/configuring-playbook-bot-draupnir.md:175 msgid "`@bot.draupnir:example.com` with the MXID of your Draupnir bot user" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:179 -#: ../../../docs/configuring-playbook-bot-draupnir.md:254 +#: ../../../docs/configuring-playbook-bot-draupnir.md:181 +#: ../../../docs/configuring-playbook-bot-draupnir.md:256 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:181 +#: ../../../docs/configuring-playbook-bot-draupnir.md:183 msgid "This does not work on outdated Windows 10 as curl is not available there." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:182 +#: ../../../docs/configuring-playbook-bot-draupnir.md:184 msgid "Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:184 +#: ../../../docs/configuring-playbook-bot-draupnir.md:186 msgid "Abuse Reports" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:186 +#: ../../../docs/configuring-playbook-bot-draupnir.md:188 msgid "Draupnir can receive reports in the management room." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:188 +#: ../../../docs/configuring-playbook-bot-draupnir.md:190 msgid "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:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:194 +#: ../../../docs/configuring-playbook-bot-draupnir.md:196 msgid "Enabling synapse-http-antispam support" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:196 +#: ../../../docs/configuring-playbook-bot-draupnir.md:198 msgid "Certain protections in Draupnir require the [synapse-http-antispam](https://github.com/maunium/synapse-http-antispam) module and a Synapse homeserver plus homeserver admin status to function. This module can be enabled in the playbook via setting `matrix_bot_draupnir_config_web_synapseHTTPAntispam_enabled` to `true` and making sure that Draupnir admin API access is enabled." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:206 +#: ../../../docs/configuring-playbook-bot-draupnir.md:208 msgid "These protections need to be manually activated. Consulting the [enabling protections](#enabling-built-in-protections) guide and/or upstream documentation can be helpful." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:208 +#: ../../../docs/configuring-playbook-bot-draupnir.md:210 msgid "The other method polls a Synapse Admin API endpoint, hence it is available only if using Synapse and if the Draupnir user is an admin. To enable it, set `pollReports: true` in your `vars.yml` file as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:215 +#: ../../../docs/configuring-playbook-bot-draupnir.md:217 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:217 +#: ../../../docs/configuring-playbook-bot-draupnir.md:219 msgid "There are some additional things you may wish to configure about the bot." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:219 +#: ../../../docs/configuring-playbook-bot-draupnir.md:221 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:221 +#: ../../../docs/configuring-playbook-bot-draupnir.md:223 msgid "`roles/custom/matrix-bot-draupnir/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_bot_draupnir_configuration_extension_yaml` variable" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:223 +#: ../../../docs/configuring-playbook-bot-draupnir.md:225 msgid "For example, to change Draupnir's `acceptInvitesFromSpace` option to `!qporfwt:example.com`, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:237 +#: ../../../docs/configuring-playbook-bot-draupnir.md:239 msgid "Migrating from Mjolnir (Only required if migrating)" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:239 +#: ../../../docs/configuring-playbook-bot-draupnir.md:241 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:241 +#: ../../../docs/configuring-playbook-bot-draupnir.md:243 msgid "Note that Draupnir supports E2EE natively, so you can enable it instead of Pantalaimon. It is recommended to consult the instruction [here](#native-e2ee-support)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:243 +#: ../../../docs/configuring-playbook-bot-draupnir.md:245 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:245 +#: ../../../docs/configuring-playbook-bot-draupnir.md:247 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:247 +#: ../../../docs/configuring-playbook-bot-draupnir.md:249 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:256 +#: ../../../docs/configuring-playbook-bot-draupnir.md:258 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:258 +#: ../../../docs/configuring-playbook-bot-draupnir.md:260 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:260 +#: ../../../docs/configuring-playbook-bot-draupnir.md:262 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:262 +#: ../../../docs/configuring-playbook-bot-draupnir.md:264 msgid "If you change the bot password (`matrix_bot_draupnir_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 [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_draupnir_password` to let the bot know its new password." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:264 +#: ../../../docs/configuring-playbook-bot-draupnir.md:266 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:266 +#: ../../../docs/configuring-playbook-bot-draupnir.md:268 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:268 +#: ../../../docs/configuring-playbook-bot-draupnir.md:270 msgid "Below is a **non-exhaustive quick-start guide** for the impatient." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:270 +#: ../../../docs/configuring-playbook-bot-draupnir.md:272 msgid "Making Draupnir join and protect a room" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:272 +#: ../../../docs/configuring-playbook-bot-draupnir.md:274 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:274 +#: ../../../docs/configuring-playbook-bot-draupnir.md:276 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:276 +#: ../../../docs/configuring-playbook-bot-draupnir.md:278 msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:278 +#: ../../../docs/configuring-playbook-bot-draupnir.md:280 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:280 +#: ../../../docs/configuring-playbook-bot-draupnir.md:282 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:282 +#: ../../../docs/configuring-playbook-bot-draupnir.md:284 msgid "Giving Draupnir permissions to do its job" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:284 +#: ../../../docs/configuring-playbook-bot-draupnir.md:286 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:286 +#: ../../../docs/configuring-playbook-bot-draupnir.md:288 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:288 +#: ../../../docs/configuring-playbook-bot-draupnir.md:290 msgid "Subscribing to a public policy list" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:290 +#: ../../../docs/configuring-playbook-bot-draupnir.md:292 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:292 +#: ../../../docs/configuring-playbook-bot-draupnir.md:294 msgid "Policy lists are maintained in Matrix rooms. Popular ones maintained in the public are:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:294 +#: ../../../docs/configuring-playbook-bot-draupnir.md:296 msgid "`#community-moderation-effort-bl:neko.dev`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:295 +#: ../../../docs/configuring-playbook-bot-draupnir.md:297 msgid "`#huginn-muninn-active-threats:feline.support`" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:297 +#: ../../../docs/configuring-playbook-bot-draupnir.md:299 msgid "You can tell Draupnir to subscribe to each of these by sending the following command to the Management Room: `!draupnir watch POLICY_LIST_ADDRESS_HERE` (e.g. `!draupnir watch #community-moderation-effort-bl:neko.dev`)" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:299 +#: ../../../docs/configuring-playbook-bot-draupnir.md:301 msgid "Creating your own policy lists and rules" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:301 +#: ../../../docs/configuring-playbook-bot-draupnir.md:303 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:303 +#: ../../../docs/configuring-playbook-bot-draupnir.md:305 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:305 +#: ../../../docs/configuring-playbook-bot-draupnir.md:307 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:307 +#: ../../../docs/configuring-playbook-bot-draupnir.md:309 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:309 +#: ../../../docs/configuring-playbook-bot-draupnir.md:311 msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:311 +#: ../../../docs/configuring-playbook-bot-draupnir.md:313 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:312 +#: ../../../docs/configuring-playbook-bot-draupnir.md:314 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:314 +#: ../../../docs/configuring-playbook-bot-draupnir.md:316 msgid "As a result of running these commands, you may observe:" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:316 +#: ../../../docs/configuring-playbook-bot-draupnir.md:318 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:317 +#: ../../../docs/configuring-playbook-bot-draupnir.md:319 msgid "applying these rules against all rooms that Draupnir is an Administrator in" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:319 +#: ../../../docs/configuring-playbook-bot-draupnir.md:321 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:321 +#: ../../../docs/configuring-playbook-bot-draupnir.md:323 msgid "Enabling built-in protections" msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:323 +#: ../../../docs/configuring-playbook-bot-draupnir.md:325 msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuitProtection` (\"If X amount of users join in Y time, set the room to invite-only\")." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:325 +#: ../../../docs/configuring-playbook-bot-draupnir.md:327 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:327 +#: ../../../docs/configuring-playbook-bot-draupnir.md:329 msgid "To [**see the configuration options for a given protection**](https://the-draupnir-project.github.io/draupnir-documentation/protections/configuring-protections#displaying-the-protection-settings), send a `!draupnir protections show PROTECTION_NAME` (e.g. `!draupnir protections show JoinWaveShortCircuitProtection`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:329 +#: ../../../docs/configuring-playbook-bot-draupnir.md:331 msgid "To [**set a specific option for a given protection**](https://the-draupnir-project.github.io/draupnir-documentation/protections/configuring-protections#changing-protection-settings), send a command like this: `!draupnir protections config set PROTECTION_NAME OPTION VALUE` (e.g. `!draupnir protections config set JoinWaveShortCircuitProtection timescaleMinutes 30`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:331 +#: ../../../docs/configuring-playbook-bot-draupnir.md:333 msgid "To [**enable a given protection**](https://the-draupnir-project.github.io/draupnir-documentation/protections/block-invitations-on-server-protection#enabling-the-protection), send a command like this: `!draupnir protections enable PROTECTION_NAME` (e.g. `!draupnir protections enable JoinWaveShortCircuitProtection`)." msgstr "" -#: ../../../docs/configuring-playbook-bot-draupnir.md:333 +#: ../../../docs/configuring-playbook-bot-draupnir.md:335 msgid "To **disable a given protection**, send a command like this: `!draupnir protections disable PROTECTION_NAME` (e.g. `!draupnir protections disable JoinWaveShortCircuitProtection`)." msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-meowlnir.pot b/i18n/translation-templates/docs/configuring-playbook-bot-meowlnir.pot new file mode 100644 index 000000000..453d4c965 --- /dev/null +++ b/i18n/translation-templates/docs/configuring-playbook-bot-meowlnir.pot @@ -0,0 +1,581 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2018-2026, Slavi Pantaleev, Aine Etke, MDAD community members +# This file is distributed under the same license as the matrix-docker-ansible-deploy package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: matrix-docker-ansible-deploy \n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2026-08-13 05:03+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:7 +msgid "Setting up Meowlnir (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:9 +msgid "The playbook can install and configure the [Meowlnir](https://github.com/maunium/meowlnir) moderation bot for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:11 +msgid "See the project's [documentation](https://docs.mau.fi/meowlnir/) to learn what it does and why it might be useful to you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:13 +msgid "Meowlnir is an alternative to [Draupnir](configuring-playbook-bot-draupnir.md) and [Mjolnir](configuring-playbook-bot-mjolnir.md). It speaks the same [policy list](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists) protocol, so it can subscribe to the same community ban lists, but it differs from them in a few ways that may matter to you:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:15 +msgid "It runs as an **appservice** and hosts **multiple bots**, each with its own management room. They live in Meowlnir's database, not its configuration file, but you still [declare them in your `vars.yml` file](#declaring-bots)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:16 +msgid "It can **override a policy coming from a list you do not control**, via unban policies combined with the ordering of your watched lists. See [Overriding a policy from someone else's list](#overriding-a-policy-from-someone-elses-list)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:17 +msgid "It is written in Go and is optimized for Synapse, using its database and admin APIs directly." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:19 +msgid "Meowlnir and Draupnir can run side by side, but not usefully in the *same* room: whichever bot you are migrating away from still watches the same community lists, so it re-applies the very bans your unban policies remove. Migrate room by room. See [Trialling Meowlnir alongside another bot](#trialling-meowlnir-alongside-another-bot)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:21 +msgid "Prerequisites" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:23 +msgid "Postgres" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:25 +msgid "Meowlnir stores its state in a Postgres database. The playbook creates one for you automatically when using the integrated Postgres server." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:27 +msgid "Adjusting DNS records" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:29 +msgid "**No DNS changes are necessary.** Meowlnir is reached by the homeserver over the container network, and the paths it optionally serves publicly (abuse reports and the policy server) are routed on your existing `matrix.example.com` domain." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:31 +msgid "Adjusting the playbook configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:33 +msgid "To enable Meowlnir, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:39 +msgid "Declaring bots" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:41 +msgid "That gets the service running, but Meowlnir does nothing until it has at least one bot. Declare the ones you want and the playbook creates them for you:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "Field" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "Required" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "Notes" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "`username`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "yes" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "The localpart of the bot's Matrix user. Awkward to change later, so choose it carefully." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "`displayname`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "The name shown in rooms. Safe to change at any time." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "`avatar_url`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "An `mxc://` URI, or `\"\"` for no avatar." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "`management_room_auto_create`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "Whether the playbook creates the bot's management room. Mutually exclusive with a non-empty `management_rooms`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "`management_rooms`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "Rooms you have created yourself, `[]` when auto-creating. See [Supplying your own management room](#supplying-your-own-management-room)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "`initial_managers`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "no" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:0 +msgid "Who to invite to an auto-created room. Defaults to the instance-wide list below." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:67 +msgid "Usernames have to start with `meowlnir_` (the value of `matrix_bot_meowlnir_user_prefix`), so that bots fall inside the user namespace the homeserver lets Meowlnir operate." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:69 +msgid "Changing `displayname` or `avatar_url` and re-running updates the bot in place. The comparison is against Meowlnir's own record, so profile edits made directly from a Matrix client are not reverted." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:71 +msgid "Initial managers" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:73 +msgid "With `management_room_auto_create: true`, the playbook creates each bot's management room and invites its initial managers to it. You only need to accept the room invitation." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:75 +msgid "`matrix_admin` is a single playbook variable which affects all bridges and bots, so setting it is usually a better move than setting anything specific to this role — **if it is already configured in your `vars.yml` file, there is nothing to do here**. If neither `matrix_admin` nor `matrix_bot_meowlnir_initial_managers` are set, the playbook would tell you about it." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:77 +msgid "A per-bot `initial_managers` replaces the instance-wide list. Declaring it empty means nobody, which fails the run for a bot relying on `management_room_auto_create`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:79 +msgid "The list is consulted only while the room is being created. Adding a name to it later invites nobody, because the room already exists — invite and promote further moderators from inside the room instead, as described in [Who can command a bot](#who-can-command-a-bot)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:81 +msgid "Rooms the playbook creates" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:83 +msgid "The bot creates the room with the `trusted_private_chat` preset, which gives every invitee the standing to command it. This is an additional room creator on room versions supporting [MSC4289](https://github.com/matrix-org/matrix-spec-proposals/pull/4289) (like v12) and power level 100 on older room versions. Creator status cannot be revoked subsequently." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:85 +msgid "The room's encryption follows `matrix_bot_meowlnir_config_encryption_enable`, and its name and topic come from `matrix_bot_meowlnir_management_room_name` and `matrix_bot_meowlnir_management_room_topic`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:87 +msgid "Supplying your own management room" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:89 +msgid "If you would rather own the room outright, create it yourself and declare it instead. The bot is then merely an administrator in a room you created:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:102 +msgid "An empty, invite-only room is fine. The order matters, because **each step depends on the one before it**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:104 +msgid "Declare the room and run the playbook. Do not invite the bot beforehand." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:105 +msgid "The playbook creates the bot and tells Meowlnir about the room. Meowlnir would try to join right away, but will fail for invite-only rooms (a harmless error in the log)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:106 +msgid "Invite the bot. It accepts the invitation, because the room is already marked as a management room for it." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:107 +msgid "Give it power level 50 or more (ideally 100), so that it can store its protected rooms and watched lists there." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:109 +msgid "Meowlnir supports several management rooms per bot, and `encrypted` is set per room. Marking a room encrypted only means something when [End-to-End Encryption support](#end-to-end-encryption-support) is switched on, which it is not by default." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:111 +msgid "Who can command a bot" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:113 +msgid "**Management room membership alone is not enough**, which is different from what [Draupnir](configuring-playbook-bot-draupnir.md) does, where everyone in the management room can issue commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:115 +msgid "Meowlnir decides who may drive a bot from power levels in its management room: anyone who can send the `fi.mau.meowlnir.watched_lists` state event (power level 50 by default), plus the room's creators." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:117 +msgid "Bots which are no longer declared" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:119 +msgid "The bot list (`matrix_bot_meowlnir_bots_custom`) is authoritative. Removing entries from there will make the playbook unregister them with the Meowlnir instance." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:121 +msgid "Removal only adjusts Meowlnir's own records. A removed bot's Matrix user remains activated and stays in the rooms it had joined. A removed management room leaves the room and the bot's membership in it intact - it's just that Meowlnir stops taking commands there." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:123 +msgid "Removal happens under the same `ensure-matrix-users-created` tag that creates bots. It's one Ansible tag for \"synchronizing the bots state\" (creation, changes, and removal)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:125 +msgid "To turn removal off entirely, set `matrix_bot_meowlnir_bots_pruning_enabled: false`. As a safety measure, the playbook refuses to prune when *no* bots are declared at all; override that with `matrix_bot_meowlnir_bots_pruning_on_empty_roster_enabled: true`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:127 +msgid "Trialling Meowlnir alongside another bot" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:129 +msgid "Meowlnir has a dry-run mode in which it does everything except take moderation actions:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:136 +msgid "Dry run does not cover the [synapse-http-antispam](#enabling-synapse-http-antispam-support) integration. It suppresses actions Meowlnir takes itself (bans, server ACLs, rejecting pending invites), but the verdicts it hands back to Synapse still block invites and joins. Leave that integration off while trialling." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:138 +msgid "Do not expect dry run to preview what Meowlnir would do in rooms another policy-list bot already moderates. Meowlnir only acts on users who are *in* a room, and the other bot has already removed everyone its lists match, so the preview comes out empty. Dry run also skips the power level check described under [Protecting a room](#protecting-a-room), so it will not surface a permissions problem either." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:140 +msgid "Abuse reports" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:142 +msgid "Meowlnir can intercept the report endpoints of the client-server API, so that abuse reports are delivered to a management room. This requires integration with the reverse proxy in front of the homeserver, which the playbook sets up for you when using Traefik:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:151 +msgid "Only the `v3` report endpoints are routed to Meowlnir. Requests to the legacy `r0` endpoints continue to reach the homeserver, because Meowlnir does not serve them." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:153 +msgid "Enabling synapse-http-antispam support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:155 +msgid "Meowlnir can block invites and joins before they happen. This requires the [synapse-http-antispam](https://github.com/maunium/synapse-http-antispam) module, which the playbook can enable for you:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:165 +msgid "The playbook wires the module up to a single consumer, so this cannot be enabled at the same time as `matrix_bot_draupnir_config_web_synapseHTTPAntispam_enabled`. The playbook fails the run if both are enabled." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:167 +msgid "With the module in place, you can also block invitations to specific users outright, which is useful for accounts that attract spam:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:174 +msgid "Such an invitation can still be let through case by case with the `!allow-invite` command." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:176 +msgid "End-to-End Encryption support" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:178 +msgid "To let Meowlnir's bots participate in encrypted rooms:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:184 +msgid "When using Synapse, the playbook turns on the experimental features this depends on (`msc2409_to_device_messages_enabled` and `msc3202_transaction_extensions`) for you." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:186 +msgid "Policy server (MSC4284)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:188 +msgid "Meowlnir can act as a [policy server](https://github.com/matrix-org/matrix-spec-proposals/pull/4284), letting rooms ask it to vet events before they are accepted:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:194 +msgid "This exposes `/_matrix/policy` on your Matrix federation endpoint, so that other servers participating in a room can reach it." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:196 +msgid "That only stands the policy server up, though — no room is put behind it until you say so from the management room:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:202 +msgid "Given no room, `enable` applies to every protected room. Rooms which are not protected are skipped, with `Skipped ... as it is not a protected room`, so [protect a room](#protecting-a-room) before enabling it here. `!policyserver` on its own reports whether the policy server is available and prints its public key, and `!policyserver disable` reverses the change." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:204 +msgid "The playbook derives a stable signing key for you from `matrix_homeserver_generic_secret_key`. If you would rather use an independently generated one, produce it with the command below and set it as `matrix_bot_meowlnir_config_policy_server_signing_key`:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:210 +msgid "Synapse admin API access (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:212 +msgid "A few of Meowlnir's features go through Synapse's admin API, not the client-server API — suspending or deactivating users, and deleting rooms during a takedown. Those calls require the caller to be a Synapse **server admin**, which bots are not by default, so they come back as `M_FORBIDDEN` (\"You are not a server admin\"). Nothing else is affected: bans, server ACLs, protecting rooms and watching policy lists all go through the client-server API, where a sufficient power level is the only requirement." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:214 +msgid "To grant that access, point each bot at a token belonging to a server admin:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:221 +msgid "The key is the bot the token is used for; the token itself belongs to an administrator account, not to the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:223 +msgid "If you have more than one management room, note that room bans are only processed in the one named by `matrix_bot_meowlnir_config_meowlnir_room_ban_room`, and ignored elsewhere." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:225 +msgid "Where the token comes from depends on how your homeserver authenticates. Ordinarily you [obtain an access token](obtaining-access-tokens.md) for an account which is a Synapse server admin. When [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) is enabled, Synapse no longer decides who is an admin, so the token has to be issued by MAS with admin privileges:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:231 +msgid "Note that bot users are created by the appservice and are not known to Matrix Authentication Service, so the token cannot be issued for the bot itself — use an administrator account." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:233 +msgid "Access to the Synapse database (optional)" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:235 +msgid "Some room takedown features rely on Meowlnir reading room IDs directly from the Synapse database. Upstream expects a user with read-only permissions, which the playbook does not create. Enabling the integration below hands Meowlnir the same credentials Synapse itself uses, which also grant write access:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:241 +msgid "If you would rather not do that, create a read-only Postgres user yourself and point Meowlnir at it with `matrix_bot_meowlnir_synapse_database_uri`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:243 +msgid "Adopting an existing Meowlnir installation" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:245 +msgid "If you already run Meowlnir outside the playbook and want to bring it under this role, two things need attention before the first run." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:247 +msgid "Your bots exist in Meowlnir's database but not in your `vars.yml` file, and [pruning](#bots-which-are-no-longer-declared) is on by default, so the first run would remove them. Declare them in `matrix_bot_meowlnir_bots_custom` — with `management_room_auto_create: false` and their existing rooms under `management_rooms` — or set `matrix_bot_meowlnir_bots_pruning_enabled: false`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:249 +msgid "If the installation uses encryption, also copy the `pickle_key` from its old configuration file into `matrix_bot_meowlnir_config_encryption_pickle_key`. The crypto store cannot be read with a different key than it was written with, so leaving the playbook's default in place costs your bots their existing encryption sessions." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:251 +msgid "Extending the configuration" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:253 +msgid "There are some additional things you may wish to configure about the bot." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:255 +msgid "Take a look at:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:257 +msgid "`roles/custom/matrix-bot-meowlnir/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_bot_meowlnir_configuration_extension_yaml` variable" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:260 +msgid "Do not set any of Meowlnir's secrets to the literal value `generate`. Meowlnir re-runs its configuration upgrader on every start, so a `generate` placeholder would produce a brand new secret on every restart. The playbook derives stable values for you, and fails the run if it finds a `generate` placeholder." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:262 +msgid "Installing" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:264 +msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:270 +msgid "With `management_room_auto_create`, you then have an invitation waiting for you — accept it and start sending commands. If you supplied the management room yourself, carry on from step 3 of [Supplying your own management room](#supplying-your-own-management-room): invite the bot, then give it power level 50 or more." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:272 +msgid "**Notes**:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:274 +msgid "The `ensure-matrix-users-created` tag is what creates the bots declared in `matrix_bot_meowlnir_bots_custom`, registers their management rooms, and removes the ones you no longer declare. It deliberately does not run as part of `setup-all`, so that installing onto a server whose database you are about to restore from a backup does not write anything." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:276 +msgid "Re-running is safe and idempotent, so adding a bot later is a matter of extending the list and running the same command again." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:278 +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-meowlnir.md:280 +msgid "Usage" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:282 +msgid "You can refer to the upstream [documentation](https://docs.mau.fi/meowlnir/) for a more detailed usage guide." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:284 +msgid "Below is a **non-exhaustive quick-start guide** for the impatient." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:286 +msgid "Inspecting and driving Meowlnir directly" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:288 +msgid "The playbook drives Meowlnir's management API for you based on `matrix_bot_meowlnir_bots_custom`, which is the recommended way. For anything it does not cover, helper scripts are installed under `/matrix/meowlnir/bin`, which find the management secret and reach the API inside the container:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:301 +msgid "`meowlnir-create-management-room` prints the new room's ID, which you then register with `meowlnir-api PUT /_meowlnir/v1/management_room/`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:303 +msgid "See the upstream [bot creation documentation](https://docs.mau.fi/meowlnir/bot-create.html) for the full set of endpoints. Bear in mind that bots you create this way are not declared in your `vars.yml` file, so the next playbook run will remove them again (see [Bots which are no longer declared](#bots-which-are-no-longer-declared))." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:305 +msgid "If you have enabled encryption, each bot also needs verifying once. That step is left manual because it returns a recovery key you need to store somewhere safe:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:311 +msgid "Protecting a room" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:313 +msgid "Invite the bot to a room, give it a power level high enough to act (see below), and then tell it to protect the room by sending this command to its management room:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:319 +msgid "Meowlnir refuses to protect a room unless its power level reaches that room's own `ban` and `redact` levels (50 in a default room). That is only enough for user bans, though: writing `m.room.server_acl` usually requires 100, and without it the server rules in your watched lists have no effect — which is most of what a list like [CME](https://matrix.to/#/%23community-moderation-effort-bl:neko.dev) carries. **Give the bot power level 100** unless you only care about user bans." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:321 +msgid "Set the power level *before* protecting the room. Meowlnir re-sends server ACLs when it starts and when a watched list changes, but not when its own power level goes up subsequently, so raising it afterwards leaves the room without ACLs until you restart the bot (`systemctl restart matrix-bot-meowlnir` or via the playbook's Ansible `start` tag)." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:323 +msgid "Subscribing to a policy list" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:325 +msgid "Policy lists are maintained in Matrix rooms. Popular public ones are:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:327 +msgid "`#community-moderation-effort-bl:neko.dev`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:328 +msgid "`#huginn-muninn-active-threats:feline.support`" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:330 +msgid "Subscribe to one by sending the following command to the management room:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:336 +msgid "The last argument is a shortcode, which you use to refer to the list in later commands." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:338 +msgid "Overriding a policy from someone else's list" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:340 +msgid "This is the main capability Meowlnir has that Draupnir does not." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:342 +msgid "When several watched lists carry a policy for the same user, **the first match wins**, and \"first\" means the order in which the lists are watched. So to be able to override a community list's ban, your own list has to come before it." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:344 +msgid "`!lists subscribe` appends, which makes subscription order the precedence order. Subscribe to your own list first, and to community lists afterwards:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:352 +msgid "If you have already subscribed in the wrong order, fixing it means editing the `fi.mau.meowlnir.watched_lists` state event in the management room by hand. Newer Meowlnir releases (than `v0.2606.0`) add `!lists subscribe … --insert-before `, which will make reordering a single command." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:354 +msgid "You can then publish an unban policy into your own list, which takes precedence over the community list's ban:" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:361 +msgid "Unlike `!ban`, the `!add-unban` command does not treat its reason as a trailing argument, so a reason containing spaces is discarded. Use a single word (or hyphenate) until that is fixed upstream." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:364 +msgid "An unban policy stops a ban from being **re-applied**; it does not undo one that is already in place unless Meowlnir applied it itself and still has it on record. A ban placed by a human moderator, or by the Draupnir or Mjolnir you are migrating away from, stays. Unban such a user once by hand — from then on the policy keeps them unbanned, while you remain subscribed to the list that banned them." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:366 +msgid "Use `!match @alice:example.com` to see which policies currently apply to a user and which list each came from." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:369 +msgid "Unban policies use a Meowlnir-specific recommendation (`fi.mau.meowlnir.unban`) which is not part of the Matrix specification. If you publish your policy list for other people to subscribe to, subscribers running Draupnir or Mjolnir will ignore your unban policies." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:371 +msgid "There is also a blunter, server-wide escape hatch for policies that are too wide to tolerate at all — `matrix_bot_meowlnir_config_meowlnir_hacky_rule_filter_custom`, which makes Meowlnir ignore any policy matching the listed entities." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:373 +msgid "Troubleshooting" +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:375 +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 running a command like `journalctl -fu matrix-bot-meowlnir`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:377 +msgid "If bots appear to do nothing, check that they have an Administrator power level in the rooms they are meant to protect, and that the room has been added with `!rooms protect`." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:379 +msgid "If commands in a management room get no reply at all, check the bot's power level *there* too — it needs at least 50 to record its own configuration." +msgstr "" + +#: ../../../docs/configuring-playbook-bot-meowlnir.md:381 +msgid "A bare `!lists` returns nothing in a management room which has never had a policy list. That is an upstream bug and it clears as soon as you subscribe to one; `!lists subscribe` works from the start." +msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot b/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot index 9bdd8e877..bb903e444 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bot-mjolnir.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-19 07:40+0000\n" +"POT-Creation-Date: 2026-08-13 05:03+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -29,251 +29,255 @@ msgid "See the project's [documentation](https://github.com/matrix-org/mjolnir/b msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:18 -msgid "Prerequisites" +msgid "**Note**: you can also use the [Draupnir](configuring-playbook-bot-draupnir.md) or [Meowlnir](configuring-playbook-bot-meowlnir.md) bots, which speak the same [policy list](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists) protocol." msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:20 -msgid "Register the bot account" +msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:22 -msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot." +msgid "Register the bot account" msgstr "" #: ../../../docs/configuring-playbook-bot-mjolnir.md:24 -msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`." +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:26 +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:28 msgid "You can use the playbook to [register a new user](registering-users.md):" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:32 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:34 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:34 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:36 msgid "Obtain an access token" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:36 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:38 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:39 -#: ../../../docs/configuring-playbook-bot-mjolnir.md:64 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:41 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:66 msgid "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:41 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:43 msgid "Make sure the account is free from rate limiting" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:43 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:45 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:45 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:47 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:47 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:49 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:49 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:51 msgid "The APIs can also be accessed via [Ketesa](https://github.com/etkecc/ketesa), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Ketesa for you. For details about it, see [this page](configuring-playbook-ketesa.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:51 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:53 msgid "Add the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:53 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:55 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:59 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:61 msgid "Obtain an access token for admin account" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:61 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:63 msgid "Manual access to Synapse's Admin APIs requires an access token for a homeserver admin account. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). If you have made Mjolnir an admin, you can just use the Mjolnir token." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:66 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:68 msgid "Run the `curl` command" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:68 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:70 msgid "To disable rate limiting, run the following command on systems that ship curl. Before running it, make sure to replace:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:70 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:72 msgid "`ADMIN_ACCESS_TOKEN_HERE` with the access token of the admin account" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:71 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:73 msgid "`example.com` with your base domain" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:72 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:74 msgid "`@bot.mjolnir:example.com` with the MXID of your Mjolnir bot user" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:78 -#: ../../../docs/configuring-playbook-bot-mjolnir.md:195 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:80 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:197 msgid "**Notes**:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:79 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:81 msgid "This does not work on outdated Windows 10 as curl is not available there." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:80 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:82 msgid "Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:82 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:84 msgid "Create a management room" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:84 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:86 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." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:87 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:89 msgid "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:89 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:91 msgid "It is possible to make the management room encrypted (E2EE). If doing so, then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:91 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:93 msgid "Once you have created the room you need to copy the room ID so you can specify it on your `vars.yml` file. In Element Web you can check the ID by going to the room's settings and clicking \"Advanced\". The room ID will look something like `!qporfwt:example.com`." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:93 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:95 msgid "Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:95 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:97 msgid "Adjusting the playbook configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:97 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:99 msgid "To enable the bot, add the following configuration to your `vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE` with the one of the room which you have created just now." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:106 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:108 msgid "End-to-End Encryption support" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:108 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:110 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:110 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 msgid "To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:112 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:114 msgid "Configuration with E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:114 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:116 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:116 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:118 msgid "Add the following configuration to your `vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:130 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:132 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:142 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:144 msgid "Configuration without E2EE support" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:144 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:146 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:146 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:148 msgid "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)." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:152 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:154 msgid "Adding Mjolnir synapse antispam module (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:154 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:156 msgid "To enable Mjolnir synapse antispam module, add the following configuration to your `vars.yml` file (adapt to your needs):" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:164 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:166 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:166 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:168 msgid "There are some additional things you may wish to configure about the bot." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:168 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:170 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:170 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:172 msgid "`roles/custom/matrix-bot-mjolnir/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_bot_mjolnir_configuration_extension_yaml` variable" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:172 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:174 msgid "For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:186 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:188 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:188 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:190 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:197 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:199 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:199 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:201 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:201 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:203 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 [Ketesa](configuring-playbook-ketesa.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:203 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:205 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:205 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:207 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 "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:207 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:209 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:209 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:211 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-bot-mjolnir`." msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:211 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:213 msgid "Increase logging verbosity" msgstr "" -#: ../../../docs/configuring-playbook-bot-mjolnir.md:213 +#: ../../../docs/configuring-playbook-bot-mjolnir.md:215 msgid "The default logging level for this component is `INFO`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot b/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot index 210e79847..c6b3fcef6 100644 --- a/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot +++ b/i18n/translation-templates/docs/configuring-playbook-bridge-hookshot.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-07-16 13:47+0000\n" +"POT-Creation-Date: 2026-08-13 05:03+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -57,102 +57,98 @@ msgid "Add the following configuration to your `inventory/host_vars/matrix.examp msgstr "" #: ../../../docs/configuring-playbook-bridge-hookshot.md:44 -msgid "End-to-bridge encryption also requires the homeserver to support (and have enabled) [MSC2409](https://github.com/matrix-org/matrix-spec-proposals/pull/2409) and [MSC3202](https://github.com/matrix-org/matrix-spec-proposals/pull/3202). If you are using Synapse, enable them by also adding this to your `vars.yml` file:" +msgid "End-to-bridge encryption requires the homeserver to support (and have enabled) [MSC2409](https://github.com/matrix-org/matrix-spec-proposals/pull/2409) and [MSC3202](https://github.com/matrix-org/matrix-spec-proposals/pull/3202). When using Synapse, the playbook turns on the experimental features this depends on (`msc2409_to_device_messages_enabled` and `msc3202_transaction_extensions`) for you. On other homeserver implementations, you need to arrange for this yourself." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:51 -msgid "These are experimental homeserver-wide features (as is Hookshot's encryption support itself), so enable them deliberately." -msgstr "" - -#: ../../../docs/configuring-playbook-bridge-hookshot.md:53 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:46 msgid "For each of the services (GitHub, GitLab, Jira, Figma, and generic webhooks) fill in the respective variables `matrix_bridge_hookshot_service_*` listed in [main.yml](../roles/custom/matrix-bridge-hookshot/defaults/main.yml) as required." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:55 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:48 msgid "Take special note of the `matrix_bridge_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:57 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:50 msgid "Extending the configuration" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:59 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:52 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:61 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:54 msgid "Take a look at:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:63 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:56 msgid "`roles/custom/matrix-bridge-hookshot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:64 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:57 msgid "`roles/custom/matrix-bridge-hookshot/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_bridge_hookshot_configuration_extension_yaml` and `matrix_bridge_hookshot_registration_extension_yaml` variables" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:66 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:59 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:68 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:61 msgid "Installing" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:70 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:63 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:77 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:70 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:79 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:72 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:81 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:74 msgid "Usage" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:83 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:76 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:85 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:78 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:87 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:80 msgid "Send `!hookshot help` to the bot to see the available commands." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:89 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:82 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:91 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:84 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:93 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:86 msgid "Reset crypto store" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:95 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:88 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:101 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:94 msgid "More setup documentation" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:103 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:96 msgid "URLs for bridges setup" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:105 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:98 msgid "Unless indicated otherwise, the following endpoints are reachable on your `matrix.` subdomain (if the feature is enabled)." msgstr "" @@ -284,98 +280,98 @@ msgstr "" msgid "Widgets" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:117 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:110 msgid "Also see the various `matrix_bridge_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:119 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:112 msgid "The different listeners are also reachable *internally* in the docker-network via the container's name (configured by `matrix_bridge_hookshot_container_url`) and on different ports (e.g. `matrix_bridge_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:121 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:114 msgid "Manage GitHub Private Key with aux role" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:123 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:116 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:125 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:118 msgid "copy the *contents* of the downloaded file and set the variable `matrix_bridge_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:126 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:119 msgid "somehow copy the file to the path `{{ matrix_bridge_hookshot_base_path }}/{{ matrix_bridge_hookshot_github_private_key_file }}` (default: `/matrix/hookshot/private-key.pem`) on the server manually." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:127 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:120 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:129 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:122 msgid "To use the `aux` role, make sure the `matrix_bridge_hookshot_github_private_key` variable is empty. Then add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:140 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:133 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:142 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:135 msgid "Enable metrics" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:144 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:137 msgid "The playbook can enable and configure the metrics of the service for you." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:146 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:139 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:148 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:141 msgid "To enable the metrics, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:155 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:148 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 adding the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:161 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:154 msgid "By default metrics are exposed publicly **without** password-protection. To password-protect the metrics with dedicated credentials, add the following configuration to your `vars.yml` file:" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:168 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:161 msgid "To `matrix_bridge_hookshot_container_labels_metrics_middleware_basic_auth_users`, set the Basic Authentication credentials (raw `htpasswd` file content) used to protect the endpoint. See https://doc.traefik.io/traefik/middlewares/http/basicauth/#users for details about it." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:170 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:163 msgid "**Note**: alternatively, you can use `matrix_metrics_exposure_enabled` to expose all services on this `/metrics/*` feature, and you can use `matrix_metrics_exposure_http_basic_auth_enabled` and `matrix_metrics_exposure_http_basic_auth_users` to password-protect the metrics of them. See [this section](configuring-playbook-prometheus-grafana.md#collecting-metrics-to-an-external-prometheus-server) for more information." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:172 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:165 msgid "Enable Grafana (optional)" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:174 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:167 msgid "Probably you wish to enable Grafana along with Prometheus for generating graphs of the metrics." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:176 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:169 msgid "To enable Grafana, see [this section](configuring-playbook-prometheus-grafana.md#adjusting-the-playbook-configuration-grafana) for instructions." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:178 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:171 msgid "Troubleshooting" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:180 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:173 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-hookshot`." msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:182 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:175 msgid "Increase logging verbosity" msgstr "" -#: ../../../docs/configuring-playbook-bridge-hookshot.md:184 +#: ../../../docs/configuring-playbook-bridge-hookshot.md:177 msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:" msgstr "" diff --git a/i18n/translation-templates/docs/configuring-playbook.pot b/i18n/translation-templates/docs/configuring-playbook.pot index 346c992c8..f6ac8307d 100644 --- a/i18n/translation-templates/docs/configuring-playbook.pot +++ b/i18n/translation-templates/docs/configuring-playbook.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-01 17:14+0000\n" +"POT-Creation-Date: 2026-08-13 05:03+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -409,201 +409,205 @@ msgid "[Setting up Draupnir for all/D4A](configuring-playbook-appservice-draupni msgstr "" #: ../../../docs/configuring-playbook.md:211 -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" +msgid "[Setting up Meowlnir](configuring-playbook-bot-meowlnir.md) — a moderation tool/bot which speaks the same policy list protocol as Draupnir and Mjolnir, but runs in appservice mode and can override policies coming from lists you do not control" msgstr "" #: ../../../docs/configuring-playbook.md:213 -msgid "Administration" +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:215 -msgid "Services that help you in administrating and monitoring your Matrix installation." +msgid "Administration" msgstr "" #: ../../../docs/configuring-playbook.md:217 -msgid "[Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)" +msgid "Services that help you in administrating and monitoring your Matrix installation." msgstr "" #: ../../../docs/configuring-playbook.md:219 -msgid "[Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)" +msgid "[Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)" msgstr "" #: ../../../docs/configuring-playbook.md:221 -msgid "[Setting up the rageshake bug report server](configuring-playbook-rageshake.md)" +msgid "[Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)" msgstr "" #: ../../../docs/configuring-playbook.md:223 -msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)" +msgid "[Setting up the rageshake bug report server](configuring-playbook-rageshake.md)" msgstr "" #: ../../../docs/configuring-playbook.md:225 +msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)" +msgstr "" + +#: ../../../docs/configuring-playbook.md:227 msgid "Backups:" msgstr "" -#: ../../../docs/configuring-playbook.md:226 +#: ../../../docs/configuring-playbook.md:228 msgid "[Setting up BorgBackup](configuring-playbook-backup-borg.md) — a full Matrix server backup solution, including the Postgres database" msgstr "" -#: ../../../docs/configuring-playbook.md:228 +#: ../../../docs/configuring-playbook.md:230 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:230 +#: ../../../docs/configuring-playbook.md:232 msgid "Other specialized services" msgstr "" -#: ../../../docs/configuring-playbook.md:232 +#: ../../../docs/configuring-playbook.md:234 msgid "Various services that don't fit any other categories." msgstr "" -#: ../../../docs/configuring-playbook.md:234 +#: ../../../docs/configuring-playbook.md:236 msgid "[Setting up Element Call](configuring-playbook-element-call.md) — a native Matrix video conferencing application, built on top of the [Matrix RTC stack](configuring-playbook-matrix-rtc.md) (optional)" msgstr "" -#: ../../../docs/configuring-playbook.md:236 +#: ../../../docs/configuring-playbook.md:238 msgid "[Setting up LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md) - a component of the [Matrix RTC stack](configuring-playbook-matrix-rtc.md) (optional)" msgstr "" -#: ../../../docs/configuring-playbook.md:238 +#: ../../../docs/configuring-playbook.md:240 msgid "[Setting up LiveKit Server](configuring-playbook-livekit-server.md) - a component of the [Matrix RTC stack](configuring-playbook-matrix-rtc.md) (optional)" msgstr "" -#: ../../../docs/configuring-playbook.md:240 +#: ../../../docs/configuring-playbook.md:242 msgid "[Setting up Matrix RTC](configuring-playbook-matrix-rtc.md) (optional)" msgstr "" -#: ../../../docs/configuring-playbook.md:242 +#: ../../../docs/configuring-playbook.md:244 msgid "[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers" msgstr "" -#: ../../../docs/configuring-playbook.md:244 +#: ../../../docs/configuring-playbook.md:246 msgid "[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)" msgstr "" -#: ../../../docs/configuring-playbook.md:246 +#: ../../../docs/configuring-playbook.md:248 msgid "[Setting up Matrix.to](configuring-playbook-matrixto.md)" msgstr "" -#: ../../../docs/configuring-playbook.md:248 +#: ../../../docs/configuring-playbook.md:250 msgid "[Setting up Etherpad](configuring-playbook-etherpad.md)" msgstr "" -#: ../../../docs/configuring-playbook.md:250 +#: ../../../docs/configuring-playbook.md:252 msgid "[Setting up the Jitsi video-conferencing platform](configuring-playbook-jitsi.md)" msgstr "" -#: ../../../docs/configuring-playbook.md:252 +#: ../../../docs/configuring-playbook.md:254 msgid "[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) — a federated comment system built on Matrix" msgstr "" -#: ../../../docs/configuring-playbook.md:254 +#: ../../../docs/configuring-playbook.md:256 msgid "[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-pantalaimon.md) (advanced)" msgstr "" -#: ../../../docs/configuring-playbook.md:256 +#: ../../../docs/configuring-playbook.md:258 msgid "[Setting up the Sygnal push gateway](configuring-playbook-sygnal.md)" msgstr "" -#: ../../../docs/configuring-playbook.md:258 +#: ../../../docs/configuring-playbook.md:260 msgid "[Setting up the ntfy push notifications server](configuring-playbook-ntfy.md)" msgstr "" -#: ../../../docs/configuring-playbook.md:260 +#: ../../../docs/configuring-playbook.md:262 msgid "Deprecated / unmaintained / removed services" msgstr "" -#: ../../../docs/configuring-playbook.md:262 +#: ../../../docs/configuring-playbook.md:264 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:264 +#: ../../../docs/configuring-playbook.md:266 msgid "[Configuring conduwuit](configuring-playbook-conduwuit.md) (removed; this component has been abandoned and unmaintained)" msgstr "" -#: ../../../docs/configuring-playbook.md:266 +#: ../../../docs/configuring-playbook.md:268 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:268 +#: ../../../docs/configuring-playbook.md:270 msgid "[Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-appservice-kakaotalk.md) (removed; the upstream repository has become unreachable and the component could only be installed by self-building it)" msgstr "" -#: ../../../docs/configuring-playbook.md:270 +#: ../../../docs/configuring-playbook.md:272 msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md) (removed; this component has been discontinued)" msgstr "" -#: ../../../docs/configuring-playbook.md:272 +#: ../../../docs/configuring-playbook.md:274 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:274 +#: ../../../docs/configuring-playbook.md:276 msgid "[Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-linkedin.md) (unmaintained; the [upstream repository](https://github.com/beeper/linkedin) has been archived. Consider [setting up Mautrix LinkedIn bridging](configuring-playbook-bridge-mautrix-linkedin.md))" msgstr "" -#: ../../../docs/configuring-playbook.md:276 +#: ../../../docs/configuring-playbook.md:278 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:278 +#: ../../../docs/configuring-playbook.md:280 msgid "[Setting up Email2Matrix](configuring-playbook-email2matrix.md) (removed; the author suggests taking a look at [Postmoogle](https://github.com/etkecc/postmoogle) as a replacement, which can also be [installed using this playbook](configuring-playbook-bridge-postmoogle.md))" msgstr "" -#: ../../../docs/configuring-playbook.md:280 +#: ../../../docs/configuring-playbook.md:282 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:282 +#: ../../../docs/configuring-playbook.md:284 msgid "[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md) (removed; Skype has been discontinued since May 2025)" msgstr "" -#: ../../../docs/configuring-playbook.md:284 +#: ../../../docs/configuring-playbook.md:286 msgid "[Setting up ma1sd Identity Server](configuring-playbook-ma1sd.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook.)" msgstr "" -#: ../../../docs/configuring-playbook.md:286 +#: ../../../docs/configuring-playbook.md:288 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:288 +#: ../../../docs/configuring-playbook.md:290 msgid "[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) (removed; the repository of the source code has been removed)" msgstr "" -#: ../../../docs/configuring-playbook.md:290 +#: ../../../docs/configuring-playbook.md:292 msgid "[Setting up matrix-registration](configuring-playbook-matrix-registration.md) (removed; this component has been unmaintained)" msgstr "" -#: ../../../docs/configuring-playbook.md:292 +#: ../../../docs/configuring-playbook.md:294 msgid "[Setting up matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) (removed; this component has been unmaintained)" msgstr "" -#: ../../../docs/configuring-playbook.md:294 +#: ../../../docs/configuring-playbook.md:296 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:296 +#: ../../../docs/configuring-playbook.md:298 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:298 +#: ../../../docs/configuring-playbook.md:300 msgid "[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-puppet-discord.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md))" msgstr "" -#: ../../../docs/configuring-playbook.md:300 +#: ../../../docs/configuring-playbook.md:302 msgid "[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-puppet-instagram.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md))" msgstr "" -#: ../../../docs/configuring-playbook.md:302 +#: ../../../docs/configuring-playbook.md:304 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 "" -#: ../../../docs/configuring-playbook.md:304 +#: ../../../docs/configuring-playbook.md:306 msgid "[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md))" msgstr "" -#: ../../../docs/configuring-playbook.md:306 +#: ../../../docs/configuring-playbook.md:308 msgid "[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md))" msgstr "" -#: ../../../docs/configuring-playbook.md:308 +#: ../../../docs/configuring-playbook.md:310 msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md) (removed; since Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0) the same feature is available natively.)" msgstr "" diff --git a/i18n/translation-templates/docs/container-images.pot b/i18n/translation-templates/docs/container-images.pot index b719b6368..503adb47f 100644 --- a/i18n/translation-templates/docs/container-images.pot +++ b/i18n/translation-templates/docs/container-images.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-01 17:14+0000\n" +"POT-Creation-Date: 2026-08-13 05:03+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -772,6 +772,18 @@ msgstr "" msgid "Moderation tool for Matrix (Fork of Mjolnir)" msgstr "" +#: ../../../docs/container-images.md:0 +msgid "[Meowlnir](configuring-playbook-bot-meowlnir.md)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "[maunium/meowlnir](https://mau.dev/maunium/meowlnir/container_registry)" +msgstr "" + +#: ../../../docs/container-images.md:0 +msgid "Moderation tool for Matrix, running in appservice mode" +msgstr "" + #: ../../../docs/container-images.md:0 msgid "[Buscarron](configuring-playbook-bot-buscarron.md)" msgstr "" @@ -784,11 +796,11 @@ msgstr "" msgid "Web forms (HTTP POST) to Matrix" msgstr "" -#: ../../../docs/container-images.md:130 +#: ../../../docs/container-images.md:131 msgid "Administration" msgstr "" -#: ../../../docs/container-images.md:132 +#: ../../../docs/container-images.md:133 msgid "Services that help you in administrating and monitoring your Matrix installation." msgstr "" @@ -912,11 +924,11 @@ msgstr "" msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus." msgstr "" -#: ../../../docs/container-images.md:148 +#: ../../../docs/container-images.md:149 msgid "Misc" msgstr "" -#: ../../../docs/container-images.md:150 +#: ../../../docs/container-images.md:151 msgid "Various services that don't fit any other categories." msgstr "" @@ -961,7 +973,7 @@ msgid "[Jitsi](configuring-playbook-jitsi.md)" msgstr "" #: ../../../docs/container-images.md:0 -msgid "[jitsi/web](https://hub.docker.com/r/jitsi/web)" +msgid "[jitsi/web](https://github.com/jitsi/docker-jitsi-meet/pkgs/container/web)" msgstr "" #: ../../../docs/container-images.md:0 @@ -969,7 +981,7 @@ msgid "[Jitsi](https://jitsi.org/) web UI" msgstr "" #: ../../../docs/container-images.md:0 -msgid "[jitsi/jicofo](https://hub.docker.com/r/jitsi/jicofo)" +msgid "[jitsi/jicofo](https://github.com/jitsi/docker-jitsi-meet/pkgs/container/jicofo)" msgstr "" #: ../../../docs/container-images.md:0 @@ -977,7 +989,7 @@ msgid "[Jitsi](https://jitsi.org/) Focus component" msgstr "" #: ../../../docs/container-images.md:0 -msgid "[jitsi/prosody](https://hub.docker.com/r/jitsi/prosody)" +msgid "[jitsi/prosody](https://github.com/jitsi/docker-jitsi-meet/pkgs/container/prosody)" msgstr "" #: ../../../docs/container-images.md:0 @@ -985,7 +997,7 @@ msgid "[Jitsi](https://jitsi.org/) Prosody XMPP server component" msgstr "" #: ../../../docs/container-images.md:0 -msgid "[jitsi/jvb](https://hub.docker.com/r/jitsi/jvb)" +msgid "[jitsi/jvb](https://github.com/jitsi/docker-jitsi-meet/pkgs/container/jvb)" msgstr "" #: ../../../docs/container-images.md:0 @@ -1056,11 +1068,11 @@ msgstr "" msgid "A native Matrix video conferencing application" msgstr "" -#: ../../../docs/container-images.md:168 +#: ../../../docs/container-images.md:169 msgid "Container images of deprecated / unmaintained services" msgstr "" -#: ../../../docs/container-images.md:170 +#: ../../../docs/container-images.md:171 msgid "The list of the deprecated or unmaintained services is available [here](configuring-playbook.md#deprecated--unmaintained--removed-services)." msgstr ""